Related
*I'm not responsible for anything you do with this. I'm just trying to contribute back to the community*
Prerequisites
1. YOU MUST BE ON THE FACTORY IMAGE (NO MODIFICATIONS that means no custom recovery, kernels, radios, etc)
**User Impo5sible says its possible with custom recovery and kernels I'm not 100% sure so YMMV*** *ANOTHER EDIT - USERS REPORT GETTING STUCK ON NEXUS LOGO if you have a custom rom/kernel and not using the -w command to wipe DATA)
2. YOU MUST HAVE ADB & USB Driver for the device (I used the SDK file from google and PDAnet)
SDK /w adb & fastboot Link: http://developer.android.com/sdk/index.html
PDAnet Link:http://pdanet.co/
3. ENABLE USB Debugging via Developer settings
(press the build button 7 times to activate it the "settings --> about phone --> Build Number --> go back --> Developer Settings --> Check USB Debugging)
4. Android 4.3 Image can be obtained from Google
Image Link: https://developers.google.com/android/nexus/images
When you have all of this installed... you may proceed
Step 1: Use 7zip or compression program equivalent to extract the stock image file that is .TGZ
Step 2: You should see a stock image file that is .TAR...extract this once again with any compression program (you should see a butt load of flash files)
Step 3: Plug your device in the computer (USB debugging should be enabled & I recommend switching the transfer type to PTP/Camera)
Step 4: Launch command prompt (start --> run --> "cmd")
Step 5: type in command prompt "cd directory where you have the adb & fast boot"
for example here is mine "cd C:\Users\MC704\Desktop\adt-bundle-windows-x86_64-20130717\adt-bundle-windows-x86_64-20130717\sdk\platform-tools"
Step 6: Verify that it is detecting your device by typing in command prompt "adb devices" (YOU SHOULD SEE YOUR DEVICE HERE ) if not recheck usb debugging & camera ptp... unplug and replug the phone back into your comp
**take a breather we are almost done**
Step 7: Turn your device off and go into fastboot mode (Hold Power Button + Volume Up & Down)
Step 8: Unlock your bootloader by typing in command prompt "fastboot oem unlock" [THIS WILL DELETE ALL YOUR DATA]
It will prompt you to unlock the Device
Step 9: Remember all those files you extracted from the ".TAR"? Copy them to the same folder where your adb and fastboot files are
Step 10: ****************VERY IMPORTANT************* DO THIS IN ORDER
I got these commands from the flash-all.sh file
Type in the command prompt each step one at a time and wait for it to complete
"fastboot flash bootloader bootloader-mako-makoz20i.img"
"fastboot reboot-bootloader"
"fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"fastboot reboot-bootloader"
"fastboot -w update image-occam-jwr66v.zip"
***NOTES FOR THIS STEP***
*REMOVE the -w from the last step if you want to keep your data (assuming your bootloader was already unlocked)*
***User chrisjcks noted you can use the flash-all.bat file that was in the zip to make life easier***
Step 11: Enjoy! If you do not plan on putting any custom roms or rooting etc. I recommend rebooting into fastboot mode (Hold Power Button + Volume Up & Down) when the phone is unlocked and type in the command prompt "fastboot oem lock" (you have to have USB debugging & PTP camera enabled)
If I missed out on any steps, please do let me know I will update the OP.
MISC info.
1. People who are using custom recoveries & root & would like to KEEP ROOT... Check this post out it should help you fellars
http://forum.xda-developers.com/showpost.php?p=43917716&postcount=56
2. STUCK ON BOOT LOGO? Check this post out for the fix
http://forum.xda-developers.com/showpost.php?p=43920888&postcount=85
3. NEW ROOT BY CHAINFIRE
http://forum.xda-developers.com/showthread.php?t=2025274
mc704 said:
*I'm not responsible for anything you do with this. I'm just trying to contribute back to the community*
FIRST
1. YOU MUST BE ON THE FACTORY IMAGE (NO MODIFICATIONS that means no custom recovery, kernels, radios, etc)
2. YOU MUST HAVE ADB & USB Driver for the device (I used the SDK file from google and PDAnet)
3. ENABLE USB Debugging via Developer settings (press the build button 7 times to activate it the "settings --> about phone --> Build Number"
4. 4.3 Image from Google (https://developers.google.com/android/nexus/images)
When you have all of this installed... you may proceed
Step 1: Use 7zip or compression program equivalent to extract the stock image file that is .TGZ
Step 2: You should see a stock image file that is .TAR...extract this once again with any compression program (you should see a butt load of flash files)
Step 3: Plug your device in the computer (USB debugging should be enabled & I recommend switching the transfer type to MTP/Camera)
Step 4: Launch command prompt (start --> run --> "cmd")
Step 5: type in command prompt "cd directory where you have the adb & fast boot" for example here is mine "cd C:\Users\MC704\Desktop\adt-bundle-windows-x86_64-20130717\adt-bundle-windows-x86_64-20130717\sdk\platform-tools"
Step 6: Verify that it is detecting your device by typing in command prompt "adb devices" (YOU SHOULD SEE YOUR DEVICE HERE ) if not recheck usb debugging & camera mtp... unplug and replug the phone back into your comp
* take a breather we are almost done
Step 7: Turn your device off and go into fastboot mode (Hold Power Button + Volume Up & Down)
Step 8: Unlock your bootloader by typing in command prompt "fastboot oem unlock" [THIS WILL DELETE ALL YOUR DATA]
It will prompt you to unlock yadda yadda
Step 9: Remember all those files you extracted from the ".TAR"? Copy them to the same folder where your adb and fastboot files are
Step 10: ****************VERY IMPORTANT************* DO THIS IN ORDER
I got these commands from the flash-all.sh file
Type in the command prompt each step one at a time and wait for it to complete
"fastboot flash bootloader bootloader-mako-makoz20i.img"
"fastboot reboot-bootloader"
"fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"fastboot reboot-bootloader"
"fastboot -w update image-occam-jwr66v.zip"
Step 11: Enjoy! If you do not plan on putting any custom roms or rooting etc I recommend rebooting into fastboot mode (Hold Power Button + Volume Up & Down) when the phone is locked and type in the command prompt "fastboot oem lock" (you have to have USB debugging & MTP camera enabled)
If I missed out on any steps, please do let me know I will update the OP.
Click to expand...
Click to collapse
or you could just unzip it, and double click the Flash All bat file. :laugh:
My bootloader is already unlocked so I would skip step 8. In this case, would it still wipe all of my data since this is not an OTA or will it just upgrade my OS leaving the apps/data/etc intact? I've done this process many times before with the factory images, but I thought it always wiped the system.
chrisjcks said:
or you could just unzip it, and double click the Flash All bat file. :laugh:
Click to expand...
Click to collapse
I'm old school I'm not too familiar with it . If you want to write a mini guide to consolidate all of this for everyone, I'll update the OP.
mbwelch said:
My bootloader is already unlocked so I would skip step 8. In this case, would it still wipe all of my data since this is not an OTA or will it just upgrade my OS leaving the apps/data/etc intact? I've done this process many times before with the factory images, but I thought it always wiped the system.
Click to expand...
Click to collapse
It wipes the system. or atleast it did for me
If you remove the "-w" from the last step it won't wipe data
Sent from my Nexus 7
mc704 said:
.... no custom recovery, kernels, radios, etc)
Click to expand...
Click to collapse
I had custom kernel and recovery - still Im able to flash factory image from google with no problem, at all..
Is there a easier alternative?
Sent from my HTC One using Tapatalk 4 Beta
chrisjcks said:
or you could just unzip it, and double click the Flash All bat file. :laugh:
Click to expand...
Click to collapse
Impo5sible said:
I had custom kernel and recovery - still Im able to flash factory image from google with no problem, at all..
Click to expand...
Click to collapse
There are always exceptions but I'll note that in the OP for people to see. I'd wrote the guide with the intention of a no failure rate or possible errors.
mc704 - in most cases that would be true - but the Flash-All.bat file is inside the ROM itself.
its as safe as you can get.
I'm on stock 4.2.2, but with custom recovery and kernel.
If I want to get those back to stock, can I just connect my device in fastboot mode, go to command prompt and type:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
?
I have the JDQ39 factory image, and will make sure everything is in the right directory.
LOVE ME PLEASE said:
Is there a easier alternative?
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
They are pushing the OTA I believe for a short time
chrisjcks said:
mc704 - in most cases that would be true - but the Flash-All.bat file is inside the ROM itself.
its as safe as you can get.
Click to expand...
Click to collapse
Sure thing I'll update it in the OP:good: thanks for the contribution
To avoid losing data, unzip image-occam-jwr66v.zip with 7 zip.
Now use fastboot to flash bootloader, boot, radio, recovery and system. everything except userdata.
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
dan in la said:
I'm on stock 4.2.2, but with custom recovery and kernel.
If I want to get those back to stock, can I just connect my device in fastboot mode, go to command prompt and type:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
?
I have the JDQ39 factory image, and will make sure everything is in the right directory.
Click to expand...
Click to collapse
yup. and system.img if you want to remove root
delete - misread the previous question.
(sure i used to be able to delete my own posts.....)
how can we check which radio version is currently on device
mangomonkey00 said:
how can we check which radio version is currently on device
Click to expand...
Click to collapse
Settings > about phone > baseband version (last 2 numbers)
Sent from my Nexus 4 using xda app-developers app
Look in Settings => About
easy way
For me, All i did was extract the package and edit the .bat file and remove the -w in the code. Then ran it under fastboot. It updated my apps and updated to 4.3, no data wipe.
thanks OP got mine updated to 4.3 without -w
vickpick said:
To avoid losing data, unzip image-occam-jwr66v.zip with 7 zip.
Now use fastboot to flash bootloader, boot, radio, recovery and system. everything except userdata.
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
yup. and system.img if you want to remove root
Click to expand...
Click to collapse
Who would like to remove root?
And to summarize:
If someone has stock rom, rooted, with custom kernel, all he has to to do in order not to lose his data and rooting is to flash everything except: system.img and userdata.img?
After that, he will have the update with all data still available?
otariq said:
Settings > about phone > baseband version (last 2 numbers)
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
mine says 84 i suppose the latest was 83 have i done something wrong and also in quick system info pro in properties its opengl es cm 1.1 which i think should be 3.0
what should i do
checked it has to be 84 but what about opengl es
You will find other versions but this is how I did it and how I solved a few common problems. If you do it exactly following the instructions, you should not loose data. I flashed from Android 4.2.2 rooted.
1.You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html. You will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
2. Download the factory image 4.3 for your Nexus 4: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
3. Unzip the file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are).
3. Plug your Nexus phone or tablet into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate a "Developer Options" menu where you will be able to activate "USB debugging")
4. Verify ADB is working. Open a terminal, move the platform-tools folder and type "./adb devices". If it doesn't work (says offline), look here: http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
5. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
6. - Type in the command prompt each step one at a time
"./fastboot flash bootloader bootloader-mako-makoz20i.img"
"./fastboot reboot-bootloader"
"./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"./fastboot reboot-bootloader"
"./fastboot update image-occam-jwr66v.zip"
It will then reboot (takes a while) and then you will be in Android 4.3 with all your data preserved.
Then if you want to root:
1. On your Mac, download TWRP recovery from here: http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img
2. Connect your Nexus 4 (debug mode) and put it in fastboot mode (point 5 above)
3. In terminal mode enter: ./fastboot flash recovery FILENAME.img (replace FILENAME by the file name of TWRP file you just downloaded)
4. Reboot your phone
5. Download directly from your phone this file (SuperSU): http://download.chainfire.eu/340/SuperSU/SuperSU-JWR66N-S005-130625-1.41.zip
6. Shut down your phone and boot it in recovery mode (Once off, push vol+, vol-, and power all together). Choose recovery mode with vol-
7. Once you are in TWRP recovery mode push "Install", look for SuperSU file you just downloaded and follow instructions to flash the zip file.
That's it! You are now root. All your data are intact.
Thanks to XDA and http://www.androidauthority.com/how...s-4-nexus-7-nexus-10-and-galaxy-nexus-248358/ and http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
jipi said:
You will find other versions but this is how I did it and how I solved a few common problems.
1.You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html. You will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
2. Download the factory image 4.3 for your Nexus 4: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
3. Unzip the file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are).
3. Plug your Nexus phone or tablet into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate a "Developer Options" menu where you will be able to activate "USB debugging")
4. Verify ADB is working. Open a terminal, move the platform-tools folder and type "./adb devices". If it doesn't work (says offline), look here: http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
5. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
6. - Type in the command prompt each step one at a time
"./fastboot flash bootloader bootloader-mako-makoz20i.img"
"./fastboot reboot-bootloader"
"./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"./fastboot reboot-bootloader"
"./fastboot update image-occam-jwr66v.zip"
It will then reboot (takes a while) and then you will be in Android 4.3 with all your data preserved.
Thanks to XDA and http://www.androidauthority.com/how...s-4-nexus-7-nexus-10-and-galaxy-nexus-248358/
Click to expand...
Click to collapse
I have the OTA file ... Will this work?
Sent from my Nexus 4 using Tapatalk 2
veteran_troller said:
I have the OTA file ... Will this work?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I have no idea but it takes only a few minutes to download the original factory file.
jipi said:
You will find other versions but this is how I did it and how I solved a few common problems.
1.You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html. You will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
2. Download the factory image 4.3 for your Nexus 4: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
3. Unzip the file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are).
3. Plug your Nexus phone or tablet into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate a "Developer Options" menu where you will be able to activate "USB debugging")
4. Verify ADB is working. Open a terminal, move the platform-tools folder and type "./adb devices". If it doesn't work (says offline), look here: http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
5. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
6. - Type in the command prompt each step one at a time
"./fastboot flash bootloader bootloader-mako-makoz20i.img"
"./fastboot reboot-bootloader"
"./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"./fastboot reboot-bootloader"
"./fastboot update image-occam-jwr66v.zip"
It will then reboot (takes a while) and then you will be in Android 4.3 with all your data preserved.
Thanks to XDA and http://www.androidauthority.com/how...s-4-nexus-7-nexus-10-and-galaxy-nexus-248358/
Click to expand...
Click to collapse
this procedure wipe everything...I updated in this way yesterday
Works
Nice post. Works exactly as described.
Thanks!!
Matt
jipi said:
You will find other versions but this is how I did it and how I solved a few common problems.
1.You must have Android SDK installed. Download it here: http://developer.android.com/sdk/index.html. You will see a bunch of folders. The one we are interested in is the subfolder "platform-tools". You may copy it to an easier location if you want.
2. Download the factory image 4.3 for your Nexus 4: https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
3. Unzip the file you downloaded and copy all its content to your "platform-tools" folder (where adb and fastboot are).
3. Plug your Nexus phone or tablet into your computer with USB debugging (activate it in "About Phone" and touch "Build number" 6 times, it will activate a "Developer Options" menu where you will be able to activate "USB debugging")
4. Verify ADB is working. Open a terminal, move the platform-tools folder and type "./adb devices". If it doesn't work (says offline), look here: http://www.thekirankumar.com/blog/2...ce-offline-issue-after-android-4-2-2-upgrade/
5. Reboot your device into fastboot mode: type in terminal "./adb reboot-bootloader"
6. - Type in the command prompt each step one at a time
"./fastboot flash bootloader bootloader-mako-makoz20i.img"
"./fastboot reboot-bootloader"
"./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"./fastboot reboot-bootloader"
"./fastboot update image-occam-jwr66v.zip"
It will then reboot (takes a while) and then you will be in Android 4.3 with all your data preserved.
Thanks to XDA and http://www.androidauthority.com/how...s-4-nexus-7-nexus-10-and-galaxy-nexus-248358/
Click to expand...
Click to collapse
alakyr said:
this procedure wipe everything...I updated in this way yesterday
Click to expand...
Click to collapse
If you did exactly like this it shouldn't have wiped your phone. I did it myself exactly as I describe it!
jipi said:
If you did exactly like this it shouldn't have wiped your phone. I did it myself exactly as I describe it!
Click to expand...
Click to collapse
If you delete userdata.img from zipfile it will not wipe your data.
My data wiped too
I followed everything precisely on a completely stock Nexus 4 and it wiped my data too.. Not to critical for me since I dont do much with my phone so its not a bother but just for reference for others...
Well this method will keep your SD card contents, but will wipe your data/data on internal storage. So depends on what you mean by wipe
Remoteconcern said:
Well this method will keep your SD card contents, but will wipe your data/data on internal storage. So depends on what you mean by wipe
Click to expand...
Click to collapse
My Nexus 4 doesnt have an sd card..
I am sorry for those who have lost data but I did exactly what I have said and preserved all my data without any other manipulation. All my apps are still there, gmail accounts, WiFi passwords, etc... I am not an expert, maybe somebody will be able to explain when data are deleted and when not.
For anyone having trouble flashing on a mac, I kept getting a usb_write error when I tried to flash the system.img. Bootloader and radio flashed just fine, but not the actual rom. I got it working in windows and narrowed the problem down to either the version of adb and fastboot I was using ( they came from a zip in another thread called rootnexus4.zip) or the archive app I was using on macOS (The Unarchiver). Hope this helps someone.
Sent from my Nexus 4 using xda premium
Is the root okay?
Thanks
Root is fine. Using SuperSU 1.43
Sent from my Nexus 4 using xda premium
this didnt wipe /data for me either.
jipi said:
If you did exactly like this it shouldn't have wiped your phone. I did it myself exactly as I describe it!
Click to expand...
Click to collapse
sirry my bad...i used also the -w flag that wipe everything
Sent from my Nexus 4 using Tapatalk 4 Beta
alakyr said:
sirry my bad...i used also the -w flag that wipe everything
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, that was the problem, you didn't follow exactly the process. If you use -w flag it will wipe your data. I am sorry for you.
Noiseboy1176 said:
For anyone having trouble flashing on a mac, I kept getting a usb_write error when I tried to flash the system.img. Bootloader and radio flashed just fine, but not the actual rom. I got it working in windows and narrowed the problem down to either the version of adb and fastboot I was using ( they came from a zip in another thread called rootnexus4.zip) or the archive app I was using on macOS (The Unarchiver). Hope this helps someone.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
It is better to download a fresh version of Android SDK (link on the first post) and then upgrade it following the method as described in the link in point 4. It seems that ADB has to be upgraded to work with 4.2.2 because 4.2.2 implemented a new security feature with certificate.
So, if ADB works fine, don't change anything but if it doesn't, upgrade to the newest version. If you don't know how to do it follow the procedure, it is easy.
jipi said:
It is better to download a fresh version of Android SDK (link on the first post) and then upgrade it following the method as described in the link in point 4. It seems that ADB has to be upgraded to work with 4.2.2 because 4.2.2 implemented a new security feature with certificate.
So, if ADB works fine, don't change anything but if it doesn't, upgrade to the newest version. If you don't know how to do it follow the procedure, it is easy.
Click to expand...
Click to collapse
Agreed. That's what I usually do, but was feeling lazy and the version of adb I had works for everything I've tried so far... Unlocking boot loader on 4.2.2, flashing numerous recoveries, radios etc. So I thought it would be fine. Of course, it is possible that my problem was the archive utility I used to extract the ROM and not adb related at all. Either way, I figured ppl should know in case it happens to them.
Must the bootloader be unlocked to do this flash? Have flash many roms with Windows PC but now Im a mac user and never flashed roms with mac and yesterday i tried and didnt get it is the an video tutorial on this?
Hi all,
I have an HTC One M8. I bought it used and run a AT&T sim on Straight Talk. Previous owner had rooted it. I was trying to get the 4.4 updates and Sense 6.0.
The phone was already running HD Revolution 12.1 and Android 4.2.2 with TeamWin Recovery Partition v2.5.0.0
I downloaded and installed Android_Revolution_HD-One_71.1.zip.
I've run it several ways:
1. First w/o wiping from TWRP. (Factory reset settings)
2. Installed w/o "Wiping Userdata Partition" and then tried "Wiping Userdata Partition" from the HD Revolution installer.
3. SuperUser by Koush checked.
4. Stops at setting permissions "set_metsdata_recusrsive: some changes failed."
5. Finish
6, Zip Install details say "no MD5 file found".
7. Reboot System and it tells me "Root permissions appear to be lost. Fix root permissions now?" Yes....
Then reboots into white Bootloader screen. Anything selected here takes me to the Recovery page. Anything selected from the REBOOT menu in TWRP takes me to the Bootloader screen.
When this is done it reboots into the white bootloader screen. Any option I pick there takes me to the TWRP recovery.
I'm stumped. Any help /bread crumbs would be appreciated.
Bootloader shows:
**TAMPERED**
**UNLOCKED **
M7_UL pvt ship s-on rh
HBOOT-1.44.0000
RADIO-4A.14.3250.15
OPENDSP-v26.120.274.0202
eMMC-BOOT
May 3 2013, 20:01:28-1
Thanks
TJB
fastboot erase cache
Then flash TWRP 2.6.3.3
Then reflash the ROM.
TWRP 2.6
BenPope said:
fastboot erase cache
Then flash TWRP 2.6.3.3
Click to expand...
Click to collapse
I'm actually trying to mount the phone so I can see it from the PC update the TWRP. I downloaded openrecovery-twrp-2.7.1.1-m7.img but can't see how to load it to the phone.
PC sees the phone from Device Manager as a Disk Drive but it doesn't show up as a drive under My Computer.
I have Minimal ADB and Fastboot. Am I on the right track?
TJB
BenPope said:
fastboot erase cache
Then flash TWRP 2.6.3.3
Then reflash the ROM.
Click to expand...
Click to collapse
I tried to install openrecovery-twrp-2.7.1.1-m7.img but I can't see HTC from my PC. It shows up as in Device Manager but there's no way to write to it. I have Minimal ADB and Fastboot. Do I need a USB OTG cable. What else can I do from the PC side to see the phone?
Right now I'm just trying to get files to the phone. Am I on the right track?
THB
teebright said:
I tried to install openrecovery-twrp-2.7.1.1-m7.img but I can't see HTC from my PC. It shows up as in Device Manager but there's no way to write to it. I have Minimal ADB and Fastboot. Do I need a USB OTG cable. What else can I do from the PC side to see the phone?
Right now I'm just trying to get files to the phone. Am I on the right track?
THB
Click to expand...
Click to collapse
You cannot install like that, they have to be flashed via bootloader.
Do you have ABD installed on your PC?
If not you have two options.
OPTION 1
This guide for Windows 7 machine, this is the quickest way IMHO
Download the adb files for your respective PC from here : http://developer.android.com/sdk/index.html
Once you have downloaded the correct one for your PC (i.e. 32 or 64bit) you will be left with a zip FOLDER named something like this adt-bundle-windows-x86_64-20130522.zip (this is for 64 bit machine), Unzip it somewhere on your pc
Locate the unzipped folder and you should have/see the following inside
• Eclipse
• Sdk
• SDFK manager .exe
Open up the sdk folder and you will find 6 folders inside, cut the 'platform-tools’ folder , then double click my computer and then enter the C: drive of your PC. Paste this folder here in the C: drive and rename it Andriod-adb.
Then right mouse click my computer and go properties, then go and click Advance system settings located on left hand side this will bring up system properties box, click the Environment Variables… tab (it will open further details) and locate the Environment Variables list scroll down until you find path, highlight this then click edit.
Click mouse in here and scroll right to the end after the last entry
Type the following ;C:\Android-adb (noting only adding the first ; if not already there), if it is already there just type C:\Android-adb. Then hit Ok then OK again and your ADB should now be successfully setup.
To test this
From the windows start button, and in the search programs and files box type cmd and enter, this should bring up a command window.
Plug in your device and type adb devices, you should see it locate your phone
OPTION 2
Or try this, extract the attached file to your desk. place your recovery img in here and in a blank spot here hold the shift key down and right mouse click this should bring up list allowing you to "open command prompt here" then follow instructions below..View attachment 2850273
------------------------------------------------------------------------------------------------------------------------------------------------------
Once you have ADB working via either of the above sorted from a
1. Command prompt you should be able to type adb reboot boatloader, if you phone reboots into bootloader go to next step
2. Place the recovery image "openrecovery-twrp-2.7.1.1-m7.img " in the same adb folder as downloaded in option 2
3. Open a command prompt from within this folder and then type fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img
4. Once sent it should com back to prompt
5. Type fastboot erase cache, then when completed type fastboot reboot
Good luck
fixed!
I fixed it! Per the recommendation I was trying to upgrade TWRP to 2.6.3.3.
I plugged in the phone to the PC via USB and made sure the phone is in FASTBOOT USB mode from the bootloader menu.
I installed "Minimal ADB and Fastboot" on the PC. Running that from the command line (cmd.exe) you type "fastboot flash recovery " then drag the file in. (watch the youtube video "How to install TWRP recovery on the HTC One M8" by ROOTJUNKIE-it will make more sense). In my case it was the 2.6.3 TWRP.img file. That pushes the update to the phone. I already had the HD 71.1 zip on the phone. I installed that via the TWRP install and from there it booted up normally. Had to setup the phone again but my music/pics were still there. Thanks all for the help!
Alright, I got out of that issue, now its time to tell you how I did this.
Key:
- equals Start of Section
= Equals End of Section
-------------------------------------------- Fixing ADB Recognition (Optional But Vital) ------------------------------------------
First of all, follow my other thread on fixing bootloader being recognized as an android bootloader interface or do this
1. Do steps in this thread up to step 5,1
2. Delete the drivers for the child of Android Device by right clicking the device and press Uninstall Driver, then check the box Delete Driver for this Device. Don't worry, the drivers you installed will not go, it will just delete the watch from being recognized
3. Disconnect your watch then reconnect it
4. You're computer will not recognize this device and it will be placed under the category, in the device manager, as 'other Devices'
5.---- 'Copied from my other thread and changed'------
5,1. Right click on the children of the unknown device
5,2. Go to Drivers and press Update Driver
5,3. Press Browse my computer for driver
5,4. You will be prompted a directory, instead press the button below it called 'Let me pick from a list of Drivers installed on my computer'
6. Locate to ADB Devices or Similar
7. Select any one of the drivers listed inside there
8. Done.
=============================================================================================================
----------------------------------------------------- Installing System and Boot and Recovery (VERY IMPORTANT) -----------------------------------------------
This is where, if you do not change your TWRP to factory recovery, your watch will re boot into TWRP because it cannot mount /data. By flashing the factory Recovery, you will eliminate this and you will have a fresh start into the system.
Prerequisites ( If you Do not have it, which you should):
simple adb here
1. Get the system, boot and recovery from this thread by IntersectRaven
http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
2. Once you have downloaded those, assuming you have done the optional procedure before this, boot/stay into fastboot
3. Place the files into the location where the simple adb is located
{{{ THIS IS THE PROCEDURE YOU SHOULD FOLLOW IN THE FOLLOWING STEPS BECAUSE THAT IS HOW I DID IT }}}
4. first check your device is seen in fastboot by typing
Code:
fastboot devices
5. once your device is seen, active and has a tag fastboot. follow on.
6. Flash the stock system first by using this code
Code:
fastboot flash system yoursystemfilename.img
replacing 'yoursystemfilename' only with the name inside the simple adb
7. Flash your boot by using this code
Code:
[CODE]fastboot flash boot boot.img
[/CODE] where 'boot' is a defined variable in your simple adb folder
8. lastly, flash the STOCK recovery by using this code
Code:
fastboot flash recovery recovery.img
where 'recovery' is a respectable variable in your simple adb folder
9. disconnect and start your system!
=====================================================================================================================
References (for the past 4 weeks):
Emergency Guide
Stock boot,sys and rec
Click to expand...
Click to collapse
Please like and upvote if it helped, as I had to take time off my studies to do this.
Also tell me if there were any mistakes.
I have successfully rooted my OnePlus Nord N100 (BE2011) using stock boot.img file patched with Magisk.
Here I will attempt to provide a detailed guide.
This is for OnePlus Nord N100 version BE2011 (Carrier unlocked) bought in the US at Best Buy. The build number is 10.5.8.BE81AA (As of today June 29, 2021)
Carrier locked versions will not work with this method because the bootloader is locked.
NOTE: Please follow the details as I had soft bricked the phone a few times by installing the wrong version of boot.img In which case the phone would not work for calls / txt
**MAKE SURE THE EXTRACTED boot.img FILE IS FROM THE EXACT OTA .zip file that is installed with the "Local Upgrade" method as described in STEP 3)***
Luckily I was able to get it to factory default by using the MSM method posted here:
[OPN100][OOS 81AA/83BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
STEP 1- On a new phone the user may have to use the automatic update either through wifi or mobile data BEFORE using "Local Upgrade" method as the 'settings' icon (gear wheel) under 'Settings' - 'system update', may not be displayed.
STEP 2- Install OnePlus Drivers on PC. USB setting should be set to file transfer.
STEP 3- Download and Update to latest firmware from OnePlus using "Local Upgrade Method"
This will be the full firmware (About 2GB file) not the smaller "update file"
This is from and email from support at OnePlus which includes the link to the latest firmware
(As of today June 6, 2021):
Check this link:
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Download the software build for your device from the above page. Please back up your data before flashing your device.
**KEEP A COPY of the .zip file on the PC as it will be needed to extract the bootloader boot.img file**
Plug your phone into your computer and copy the downloaded .zip to your phone’s storage.
(At the root of Internal storage: BE2011>Internal shared storage) see below picture.
If you’re using a Mac, you can install Android File Transfer Android File Transfer for this operation.
After the .zip file is copied to your phone, go to 'Settings' - 'system update', click the 'settings' icon on the top right corner, choose 'Local upgrade', find the .zip file and click on 'Install' to confirm.
The update takes about a minute (depending upon the file size), once done reboot your device to boot into the latest Oxygen OS.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
STEP 4- Extract boot.img file from payload.bin
The firmware download is a .zip file. When unzipped on the PC there will be a large file called "payload.bin" In order to extract boot.img from payload.bin the user will need to use a python script called payload_dumper.py
In order to use the tools, there should be no proxy server and use "Administrator" account. (I had errors when using proxy server and my windows user account.)
4a - Install the latest Python from here: https://www.python.org/downloads/
On Python install select "Add Python 3.xx to PATH"
4b - Download payload dumper from here :
https://www.mediafire.com/file/pslxh616isribx6/payload_dumper.zip/file
4c Upon successful download, extract all the files inside the ZIP folder to the same location where you have installed Python.
4d Unzip the OnePlus firmware file .zip and copy payload.bin to the python folder ( This means that the folder will have Python, the Payload Dumper Tool, and the payload.bin file in the same place.)
4e- Open the folder in CMD and use command: python -m pip install protobuf
(this will download and install Protocol Buffers Google’s data interchange format)
4f- execute the following command: python payload_dumper.py payload.bin
The .img files should now be extracted to the "output" folder
STEP 5- Install Android SDK Platform-Tools on Your PC
5a - Enable developer options on phone in settings>about phone. tap on "build number" several times until it displays "you are now a developer"
5b - On phone go to settings>system>developer options and Enable USB debugging (in Windows Device manager there should show "ADB Interface" under USB devices. If not the OnePlus ADB drivers need to be installed)
5c - Install ADB on Windows
Download the platform-tools package for Windows from Google:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
We are going to need a location on the PC where the files could remain untouched, yet easily accessible. So extract the content of the downloaded “platform-tools-latest-windows.zip” file to C:\adb
5d- Connect phone with ADB
Go to the folder where the files are present (Example: C:\adb).
On an empty space inside this folder, press the SHIFT key and right-click. Select “Open command window here” or “Open PowerShell window here” from the menu that appears.
With the Android device connected to the PC using USB cable enter the following command to initiate the ADB connection:
adb devices
The phone will ask for permission. Select allow and click ok
enter the command again:
adb devices
This will show that the device is connected with ADB.
STEP 6- Unlock Bootloader ****THIS WILL WIPE ALL DATA FROM PHONE****
6a- On phone go to settings>system>developer options and enable "OEM unlocking"
NOTE OPTION WILL ONLY BE AVAILABLE WITH CARRIER UNLOCKED PHONE
6b- In CMD or Powershell use command : adb reboot bootloader
This will reboot the phone into fastboot mode
6c- enter command: fastboot devices
The phone should be displayed. This verifies the connection with fastboot driver
6d- enter command: fastboot oem unlock
The phone will now ask to confirm. Use the vol +/- numbers to navigate and power button to select "unlock bootloader"
6e- if the phone doesnt automatically reset use command : fastboot reboot
6f- on reboot the user will have to go through the factory "setup" again and enable developer options and USB debugging again (Steps 5a, 5b from above)
STEP 7- Install Magisk and patch boot.img file
7a- Download Magisk APK file from here: https://magiskmanager.com/go/download
7b- Copy the .apk file to phone and use file manager to run. (it will ask for permission)
7c- copy the file "boot.img" from the PC to the phone internal storage (output folder under Python Step 4f above)
7d- run Magisk app on phone
7e- Click "install" under the Magisk heading and check "select and patch a file"
7f- choose the boot.img file that was just copied to the phone
Magisk will now patch the boot.img file and show the file location. This may be in "Downloads" folder.
7g- Copy the patched magisk boot.img file back to the PC in the \adb folder. File name should be something like "magisk_patched-23000_XXXXX.img"
STEP 8 - Boot with magisk patched boot.img file
8a - use command prompt and enter command: adb devices
the device should be displayed
8b - enter command: adb reboot bootloader
phone will reboot in fastboot mode
8c - ensure connnetion with command : fastboot devices
device should be displayed
8d - Test boot image by executing command:
fastboot boot magisk_patched-XXXXXXX.img
This will only boot the image once! Make sure everything is working (e.g. WiFi, PHone Messaging doesn't work on wrong image)
Call your phone and txt and use WIFI to make sure all the communication features are working
Open the Magisk APP. It should show Magisk installed.
The device is now temporarily rooted.
STEP 9 - Flash Bootloader
9a - use command prompt and enter command: adb devices
the device should be displayed
9b - enter command: adb reboot bootloader
phone will reboot in fastboot mode
9c - ensure connnetion with command : fastboot devices
device should be displayed
9d - Flash boot image by entering command:
fastboot flash boot magisk_patched-XXXXXX.img
Did you have an issue with the phone updating itself recently? Mine auto installed without any prompts this morning, so I went through the process again of unbricking to 10.5.5, manually updating to 10.5.8, patching, rooting, and tried blocking all oneplus domains to prevent any updates. Then a couple hours later it randomly rebooted and installed an update again without any prompt. I check OnePlus's website and the most recent update is from June.
If only someone would post the OTA zip file! Please! My n100 updated overnight without warning and I lost root. I'd really like to get a hold of it so I could patch boot.img and get root back.
Does anyone know how to get the OTA zip file after the update has run? Any other ways to re-obtain root without flashing back to android 10? Any advice would be greatly appreciated!
I contacted one plus support and they asked me for IMEI number and proof of purchase. Then they sent me the link for the current firmware download (the complete zip not the update this file should be about 2GB).
I have posted the link that they sent me in the instructions above.
For this to work you have to let the unrooted stock phone download the OTA update the normal way in systemm settings.
Once it does that you will be able to flash it with the firmware from the zip file manually.
I have disabled all automatic updates and ever since i rooted it the update option in system settings is greyed out.
Hope this helps
alexspecht said:
I have successfully rooted my OnePlus Nord N100 (BE2011) using stock boot.img file patched with Magisk.
Here I will attempt to provide a detailed guide.
This is for OnePlus Nord N100 version BE2011 (Carrier unlocked) bought in the US at Best Buy. The build number is 10.5.8.BE81AA (As of today June 29, 2021)
Carrier locked versions will not work with this method because the bootloader is locked.
NOTE: Please follow the details as I had soft bricked the phone a few times by installing the wrong version of boot.img In which case the phone would not work for calls / txt
**MAKE SURE THE EXTRACTED boot.img FILE IS FROM THE EXACT OTA .zip file that is installed with the "Local Upgrade" method as described in STEP 3)***
Luckily I was able to get it to factory default by using the MSM method posted here:
[OPN100][OOS 81AA/83BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
STEP 1- On a new phone the user may have to use the automatic update either through wifi or mobile data BEFORE using "Local Upgrade" method as the 'settings' icon (gear wheel) under 'Settings' - 'system update', may not be displayed.
STEP 2- Install OnePlus Drivers on PC. USB setting should be set to file transfer.
STEP 3- Download and Update to latest firmware from OnePlus using "Local Upgrade Method"
This will be the full firmware (About 2GB file) not the smaller "update file"
This is from and email from support at OnePlus which includes the link to the latest firmware
(As of today June 6, 2021):
Check this link:
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Download the software build for your device from the above page. Please back up your data before flashing your device.
**KEEP A COPY of the .zip file on the PC as it will be needed to extract the bootloader boot.img file**
Plug your phone into your computer and copy the downloaded .zip to your phone’s storage.
(At the root of Internal storage: BE2011>Internal shared storage) see below picture.
If you’re using a Mac, you can install Android File Transfer Android File Transfer for this operation.
After the .zip file is copied to your phone, go to 'Settings' - 'system update', click the 'settings' icon on the top right corner, choose 'Local upgrade', find the .zip file and click on 'Install' to confirm.
The update takes about a minute (depending upon the file size), once done reboot your device to boot into the latest Oxygen OS.
View attachment 5351013
STEP 4- Extract boot.img file from payload.bin
The firmware download is a .zip file. When unzipped on the PC there will be a large file called "payload.bin" In order to extract boot.img from payload.bin the user will need to use a python script called payload_dumper.py
In order to use the tools, there should be no proxy server and use "Administrator" account. (I had errors when using proxy server and my windows user account.)
4a - Install the latest Python from here: https://www.python.org/downloads/
On Python install select "Add Python 3.xx to PATH"
4b - Download payload dumper from here :
https://www.mediafire.com/file/pslxh616isribx6/payload_dumper.zip/file
4c Upon successful download, extract all the files inside the ZIP folder to the same location where you have installed Python.
4d Unzip the OnePlus firmware file .zip and copy payload.bin to the python folder ( This means that the folder will have Python, the Payload Dumper Tool, and the payload.bin file in the same place.)
4e- Open the folder in CMD and use command: python -m pip install protobuf
(this will download and install Protocol Buffers Google’s data interchange format)
4f- execute the following command: python payload_dumper.py payload.bin
The .img files should now be extracted to the "output" folder
View attachment 5351027
STEP 5- Install Android SDK Platform-Tools on Your PC
5a - Enable developer options on phone in settings>about phone. tap on "build number" several times until it displays "you are now a developer"
5b - On phone go to settings>system>developer options and Enable USB debugging (in Windows Device manager there should show "ADB Interface" under USB devices. If not the OnePlus ADB drivers need to be installed)
5c - Install ADB on Windows
Download the platform-tools package for Windows from Google:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
We are going to need a location on the PC where the files could remain untouched, yet easily accessible. So extract the content of the downloaded “platform-tools-latest-windows.zip” file to C:\adb
5d- Connect phone with ADB
Go to the folder where the files are present (Example: C:\adb).
On an empty space inside this folder, press the SHIFT key and right-click. Select “Open command window here” or “Open PowerShell window here” from the menu that appears.
With the Android device connected to the PC using USB cable enter the following command to initiate the ADB connection:
adb devices
The phone will ask for permission. Select allow and click ok
enter the command again:
adb devices
This will show that the device is connected with ADB.
STEP 6- Unlock Bootloader ****THIS WILL WIPE ALL DATA FROM PHONE****
6a- On phone go to settings>system>developer options and enable "OEM unlocking"
NOTE OPTION WILL ONLY BE AVAILABLE WITH CARRIER UNLOCKED PHONE
6b- In CMD or Powershell use command : adb reboot bootloader
This will reboot the phone into fastboot mode
6c- enter command: fastboot devices
The phone should be displayed. This verifies the connection with fastboot driver
6d- enter command: fastboot oem unlock
The phone will now ask to confirm. Use the vol +/- numbers to navigate and power button to select "unlock bootloader"
6e- if the phone doesnt automatically reset use command : fastboot reboot
6f- on reboot the user will have to go through the factory "setup" again and enable developer options and USB debugging again (Steps 5a, 5b from above)
STEP 7- Install Magisk and patch boot.img file
7a- Download Magisk APK file from here: https://magiskmanager.com/go/download
7b- Copy the .apk file to phone and use file manager to run. (it will ask for permission)
7c- copy the file "boot.img" from the PC to the phone internal storage (output folder under Python Step 4f above)
7d- run Magisk app on phone
7e- Click "install" under the Magisk heading and check "select and patch a file"
7f- choose the boot.img file that was just copied to the phone
Magisk will now patch the boot.img file and show the file location. This may be in "Downloads" folder.
7g- Copy the patched magisk boot.img file back to the PC in the \adb folder. File name should be something like "magisk_patched-23000_XXXXX.img"
STEP 8 - Boot with magisk patched boot.img file
8a - use command prompt and enter command: adb devices
the device should be displayed
8b - enter command: adb reboot bootloader
phone will reboot in fastboot mode
8c - ensure connnetion with command : fastboot devices
device should be displayed
8d - Test boot image by executing command:
fastboot boot magisk_patched-XXXXXXX.img
This will only boot the image once! Make sure everything is working (e.g. WiFi, PHone Messaging doesn't work on wrong image)
Call your phone and txt and use WIFI to make sure all the communication features are working
Open the Magisk APP. It should show Magisk installed.
The device is now temporarily rooted.
STEP 9 - Flash Bootloader
9a - use command prompt and enter command: adb devices
the device should be displayed
9b - enter command: adb reboot bootloader
phone will reboot in fastboot mode
9c - ensure connnetion with command : fastboot devices
device should be displayed
9d - Flash boot image by entering command:
fastboot flash boot magisk_patched-XXXXXX.img
Click to expand...
Click to collapse
Bro ..This is too much am lost,why don't they have this phone listed on Twrp sites?Can't i install twrp recovery on this N100
alexspecht said:
I have successfully rooted my OnePlus Nord N100 (BE2011) using stock boot.img file patched with Magisk.
Here I will attempt to provide a detailed guide.
This is for OnePlus Nord N100 version BE2011 (Carrier unlocked) bought in the US at Best Buy. The build number is 10.5.8.BE81AA (As of today June 29, 2021)
Carrier locked versions will not work with this method because the bootloader is locked.
NOTE: Please follow the details as I had soft bricked the phone a few times by installing the wrong version of boot.img In which case the phone would not work for calls / txt
**MAKE SURE THE EXTRACTED boot.img FILE IS FROM THE EXACT OTA .zip file that is installed with the "Local Upgrade" method as described in STEP 3)***
Luckily I was able to get it to factory default by using the MSM method posted here:
[OPN100][OOS 81AA/83BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
STEP 1- On a new phone the user may have to use the automatic update either through wifi or mobile data BEFORE using "Local Upgrade" method as the 'settings' icon (gear wheel) under 'Settings' - 'system update', may not be displayed.
STEP 2- Install OnePlus Drivers on PC. USB setting should be set to file transfer.
STEP 3- Download and Update to latest firmware from OnePlus using "Local Upgrade Method"
This will be the full firmware (About 2GB file) not the smaller "update file"
This is from and email from support at OnePlus which includes the link to the latest firmware
(As of today June 6, 2021):
Check this link:
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Download the software build for your device from the above page. Please back up your data before flashing your device.
**KEEP A COPY of the .zip file on the PC as it will be needed to extract the bootloader boot.img file**
Plug your phone into your computer and copy the downloaded .zip to your phone’s storage.
(At the root of Internal storage: BE2011>Internal shared storage) see below picture.
If you’re using a Mac, you can install Android File Transfer Android File Transfer for this operation.
After the .zip file is copied to your phone, go to 'Settings' - 'system update', click the 'settings' icon on the top right corner, choose 'Local upgrade', find the .zip file and click on 'Install' to confirm.
The update takes about a minute (depending upon the file size), once done reboot your device to boot into the latest Oxygen OS.
View attachment 5351013
STEP 4- Extract boot.img file from payload.bin
The firmware download is a .zip file. When unzipped on the PC there will be a large file called "payload.bin" In order to extract boot.img from payload.bin the user will need to use a python script called payload_dumper.py
In order to use the tools, there should be no proxy server and use "Administrator" account. (I had errors when using proxy server and my windows user account.)
4a - Install the latest Python from here: https://www.python.org/downloads/
On Python install select "Add Python 3.xx to PATH"
4b - Download payload dumper from here :
https://www.mediafire.com/file/pslxh616isribx6/payload_dumper.zip/file
4c Upon successful download, extract all the files inside the ZIP folder to the same location where you have installed Python.
4d Unzip the OnePlus firmware file .zip and copy payload.bin to the python folder ( This means that the folder will have Python, the Payload Dumper Tool, and the payload.bin file in the same place.)
4e- Open the folder in CMD and use command: python -m pip install protobuf
(this will download and install Protocol Buffers Google’s data interchange format)
4f- execute the following command: python payload_dumper.py payload.bin
The .img files should now be extracted to the "output" folder
View attachment 5351027
STEP 5- Install Android SDK Platform-Tools on Your PC
5a - Enable developer options on phone in settings>about phone. tap on "build number" several times until it displays "you are now a developer"
5b - On phone go to settings>system>developer options and Enable USB debugging (in Windows Device manager there should show "ADB Interface" under USB devices. If not the OnePlus ADB drivers need to be installed)
5c - Install ADB on Windows
Download the platform-tools package for Windows from Google:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
We are going to need a location on the PC where the files could remain untouched, yet easily accessible. So extract the content of the downloaded “platform-tools-latest-windows.zip” file to C:\adb
5d- Connect phone with ADB
Go to the folder where the files are present (Example: C:\adb).
On an empty space inside this folder, press the SHIFT key and right-click. Select “Open command window here” or “Open PowerShell window here” from the menu that appears.
With the Android device connected to the PC using USB cable enter the following command to initiate the ADB connection:
adb devices
The phone will ask for permission. Select allow and click ok
enter the command again:
adb devices
This will show that the device is connected with ADB.
STEP 6- Unlock Bootloader ****THIS WILL WIPE ALL DATA FROM PHONE****
6a- On phone go to settings>system>developer options and enable "OEM unlocking"
NOTE OPTION WILL ONLY BE AVAILABLE WITH CARRIER UNLOCKED PHONE
6b- In CMD or Powershell use command : adb reboot bootloader
This will reboot the phone into fastboot mode
6c- enter command: fastboot devices
The phone should be displayed. This verifies the connection with fastboot driver
6d- enter command: fastboot oem unlock
The phone will now ask to confirm. Use the vol +/- numbers to navigate and power button to select "unlock bootloader"
6e- if the phone doesnt automatically reset use command : fastboot reboot
6f- on reboot the user will have to go through the factory "setup" again and enable developer options and USB debugging again (Steps 5a, 5b from above)
STEP 7- Install Magisk and patch boot.img file
7a- Download Magisk APK file from here: https://magiskmanager.com/go/download
7b- Copy the .apk file to phone and use file manager to run. (it will ask for permission)
7c- copy the file "boot.img" from the PC to the phone internal storage (output folder under Python Step 4f above)
7d- run Magisk app on phone
7e- Click "install" under the Magisk heading and check "select and patch a file"
7f- choose the boot.img file that was just copied to the phone
Magisk will now patch the boot.img file and show the file location. This may be in "Downloads" folder.
7g- Copy the patched magisk boot.img file back to the PC in the \adb folder. File name should be something like "magisk_patched-23000_XXXXX.img"
STEP 8 - Boot with magisk patched boot.img file
8a - use command prompt and enter command: adb devices
the device should be displayed
8b - enter command: adb reboot bootloader
phone will reboot in fastboot mode
8c - ensure connnetion with command : fastboot devices
device should be displayed
8d - Test boot image by executing command:
fastboot boot magisk_patched-XXXXXXX.img
This will only boot the image once! Make sure everything is working (e.g. WiFi, PHone Messaging doesn't work on wrong image)
Call your phone and txt and use WIFI to make sure all the communication features are working
Open the Magisk APP. It should show Magisk installed.
The device is now temporarily rooted.
STEP 9 - Flash Bootloader
9a - use command prompt and enter command: adb devices
the device should be displayed
9b - enter command: adb reboot bootloader
phone will reboot in fastboot mode
9c - ensure connnetion with command : fastboot devices
device should be displayed
9d - Flash boot image by entering command:
fastboot flash boot magisk_patched-XXXXXX.img
Click to expand...
Click to collapse
My N100 build no. is Oxygen Os 10.5.10.BE83BA can i update and root my phone with the same firmware?
Wanted to drop in and thank the OP for this. The steps worked like a charm. I even powered off the phone and booted back up to insure Root was successfully implemented.
I installed Package Manager and successfully removed all the bloatware and tracking apps phone manufacturers love to refuse to allow to you remove. I'm not a power user like alot of root people, I just want a clean and private experience on my phone. I don't even sign into a Google account with my phones, that's how privacy conscious I am.
My last few phones were HTC because they made is very easy to unlock the bootloader and play around. It's sad they're not making phones anymore, but when I heard OnePlus was bootloader friendly, I decided to check them out and I'm glad I did.
So, thank you again!
So for anyone like me who had a mini panic attack when they got the notice to update to build 11.0.1.BE81AA, it did not break root, deactivate developer options, or lock the bootloader. The update was successful, and as far as I can tell, I still have root.
Though, I wouldn't mind re-locking the bootloader now that I'm rooted. The option is greyed out in Developer options. It's not a big deal, except for the annoying warning message and a few seconds delay when rebooting.
jtl2dotnet said:
So for anyone like me who had a mini panic attack when they got the notice to update to build 11.0.1.BE81AA, it did not break root, deactivate developer options, or lock the bootloader. The update was successful, and as far as I can tell, I still have root.
Though, I wouldn't mind re-locking the bootloader now that I'm rooted. The option is greyed out in Developer options. It's not a big deal, except for the annoying warning message and a few seconds delay when rebooting.
Click to expand...
Click to collapse
Amigo,como le hiciste?
Yo tengo la misma actualización pero no logro sacar el boot.img
Okay, time for an update. I can officially confirm that upgrading to 11.0.1.BE81AA does break root. One of the apps I used appeared to be working in fact, but it really wasn't. It didn't give any error messages that I could see, the app appeared to work as normal but actually wasn't doing anything. Thinking it must be broken root, I downloaded a root checker and that confirmed it.
Again: upgrading to 11.0.1.BE81AA breaks root.
I checked OnePlus' website and they not released the zip file for this release yet. I am hoping that once they do, these steps will work by simply using the boot.img from the 11.0.1.BE81AA zip, but until it's officially released I don't know of way to test it.
If anyone has gotten 11.0.1.BE81AA rooted, I would be interested to know.
My device automatically upgraded to 11.0.1.BE81AA. It is in android 11. Please help me. I want to Root.
OK, for those of you that had a problem with One Plus pushing the 11.0.1.BE81AA android 11 update to your phone and are still struggling, I will post what I did. Just follow the instructions from the previous several messages above, and use the boot.img file you can find at link to repo . I used the file named "OnePlusN100Oxygen_14.O.21_GLO_0210_2107241056" (AKA "f0ca210dff1c162c3c4a68f2560ef50898ac1797.zip" and the tool "payload_dumper-win64.zip". ISInce I already had Magisk on my phone and just just lost root, I followed the instructions posted in post #1 in this thread (thanks, alexspecht for the detailed instructions!) starting with step 7.
To summarize: WARNING, I BEAR NO RESPONSIBILITY IF YOU DAMAGE OR RENDER YOUR DEVICE UNUSABLE:
1. I unpacked the boot.img, and copied it to my phone.
2. I used Magisk to patch it
3. I copied the patched boot.img file to my platform tools folder on my windows PC.
4. I skipped step 8 and jumped right to step 9
5. I used a command window to send "adb devices" to my phone to verify connection
5. I then issued the "adb boot bootloader" command, and authorized my device when asked.
6. Next, i entered "fastboot devices"
7. And finally I issued the "fastboot flash boot magisk_patched-XXXXXX.img" command
8. and rebooted by selecting "Start" on my phone screen.
I knew it was working when I saw the live boot screen I use instead of the standard oneplus boot sequence.
Once again, thank you, @alexspecht !
Glad to see people found this useful. They dont make it easy anymore.
As far as the OTA push thats been breaking peoples phone:
If you disable google play services the update will not come through.
The update uses wifi to download, so luckily I was not connected to wifi when the update came in.
so if you need google play services make sure your not on wifi. So far they havent broken my phone, sorry thats the best I could do.
I can confirm that repeating the steps in the OP with the EU 11.0.0.0 ROM (OnePlusN100Oxygen_14.E.20_GLO_0200_2106222205) successfully resulted in root.
I was able to successfully root my oneplus N100 BE2011 i checked my text messages and they work but my calls dont come in, when i try to make a phone call the phone freezes up, i completed the root process and disabled auto updates. Sucks the phone does not work i cant make any calls but atleast im rooted ?
Is there a way to update to 10.5.8.BE81AA using the downloaded payload with an MSM tool?
This would save all the time of updating via auto-downlaod update, then moving the file to the phone, then doing manual local update.
alexspecht said:
STEP 1- On a new phone the user may have to use the automatic update either through wifi or mobile data BEFORE using "Local Upgrade" method as the 'settings' icon (gear wheel) under 'Settings' - 'system update', may not be displayed.
Click to expand...
Click to collapse
This is correct, there's no `settings` icon unless you do the update. BUT when you do the update, now you're in android 11 and they won't let you downgrade: "The version of your selected package is lower than that of the current system. To avoid booting up failure, downgrading is not allowed."
So I'm not sure how to make your guide work, given this.
.
Wish the n200 had this much development
I did this and have root access verified. But now everytime I try to get SU in adb it automatically denies access. Any ideas?