This guide is obsoleted, please visit the new updated thread here!
Heloo there , can you post step by step this tutorial , thx before.
Supernyams said:
Heloo there , can you post step by step this tutorial , thx before.
Click to expand...
Click to collapse
That will be much appreciated
Sent from my SKW-A0 using Tapatalk
I have sucessfull flashed in order as below:
1. Backup all your data/media, sms and call log.
2. Dial *#*#1027#*#* then choose Local update.
3. Download SKYW1907040OS01MP3 Stock Factory Image (link above from OP) and move update.zip to “ota” directory in your phone.
4. Press update OTA, after reboot, BS 2 will jump into recovery mode ask for factory reset. Do it or BS 2 won't boot properly.
5. Please allow BS 2 to finish first step of boot up, with least setting up as possible.
6. Go to setting and System update, perform update from S01MP3 to S01MP4, then reboot.
7. Repeat step 5.
8. Repeat step 6 to perform update from S01MP4 to S01MP5, then reboot.
9. Repeat step 5.
10. Turn off the phone and quickly enter Fastboot mode.
11. Perform unlock bootloader by 2 CMD command from above:
Fastboot oem bs_unlock
Fastboot oem bs_unlock_critical
Click to expand...
Click to collapse
12. Restart BS 2, BS 2 will ask for factory reset in Recovery mode. DO IT. (It's very important step cause the BS 2 will stuck at logo if you skip this step).
13. Repeat step 5 (wait until the BS 2 fully operation, enter home launcher, with minimum setting up from beginning). THIS STEP IS ALSO IMPORTANT.
14. Download 2 boot files from OP
Stock_boot.img
boot.img
Click to expand...
Click to collapse
15. Check slot_a or slot_b contain your boot original file by cmd command:
fastboot getvar current-slot
Click to expand...
Click to collapse
- If your SKYW1911121OS01MP5 update is on SLOT A then use this fastboot command:
fastboot flash boot_a boot.img
Click to expand...
Click to collapse
OR
- If your SKYW1911121OS01MP5 update is on SLOT B then use this fastboot command:
fastboot flash boot_b boot.img
Click to expand...
Click to collapse
Restart BS 2 after flash boot.img
16. Go to XDA and download and install Magisk Manager.
In any cases that BS 2 stuck or can not boot, please enter fastboot mode and flash stock_boot.img from above; repeat Step 5, and reflash boot.img.
-----------------------------------------------------------------------------------
Now Black Shark 2 is rooted with magisk. ^_^ .
---------- Post added at 09:30 AM ---------- Previous post was at 08:45 AM ----------
But i've lost the wifi function. Stock_boot has wifi but boot.img doesn't have. Could you provide a fix for that? Thanks
tuannghia1985 said:
I have sucessfull flashed in order as below:
1. Backup all your data/media, sms and call log.
2. Dial *#*#1027#*#* then choose Local update.
...
Click to expand...
Click to collapse
It seems that you just lost your stock rom. If your region is same as his, your phone would be updated to SKYW1911121OS01MP5 already. It seems that it was not, so you flashed the MP3 and updated to MP5, which is not for your region and there could be mismatched functions. And you lost both slots, which contain your stock rom/region info. You need to use the factory image to backup your own stock rom, or need to follow the sequence exactly, not reversed.
wga0 said:
It seems that you just lost your stock rom. If your region is same as his, your phone would be updated to SKYW1911121OS01MP5 already. It seems that it was not, so you flashed the MP3 and updated to MP5, which is not for your region and you lost both slots, which contain your region stock rom. You need to use the factory image to backup your own stock rom, or need to follow the sequence exactly, not reversed.
Click to expand...
Click to collapse
I've figured by myself, use your stock_boot.img and patch manually with Magisk Manager (v7.5). Magisk Manager return for me a "magisk_patched.img" and by flashing that new file, the wifi is return again. I don't know why but it works for me. Thanks for replied.
I can't update mp5 from mp3, I unlock it now. what should I do?
tuannghia1985 said:
I have sucessfull flashed in order as below:
1. Backup all your data/media, sms and call log.
2. Dial *#*#1027#*#* then choose Local update.
3. Download SKYW1907040OS01MP3 Stock Factory Image (link above from OP) and move update.zip to “ota” directory in your phone.
4. Press update OTA, after reboot, BS 2 will jump into recovery mode ask for factory reset. Do it or BS 2 won't boot properly.
5. Please allow BS 2 to finish first step of boot up, with least setting up as possible.
6. Go to setting and System update, perform update from S01MP3 to S01MP4, then reboot.
7. Repeat step 5.
8. Repeat step 6 to perform update from S01MP4 to S01MP5, then reboot.
9. Repeat step 5.
10. Turn off the phone and quickly enter Fastboot mode.
11. Perform unlock bootloader by 2 CMD command from above:
12. Restart BS 2, BS 2 will ask for factory reset in Recovery mode. DO IT. (It's very important step cause the BS 2 will stuck at logo if you skip this step).
13. Repeat step 5 (wait until the BS 2 fully operation, enter home launcher, with minimum setting up from beginning). THIS STEP IS ALSO IMPORTANT.
14. Download 2 boot files from OP
15. Check slot_a or slot_b contain your boot original file by cmd command:
- If your SKYW1911121OS01MP5 update is on SLOT A then use this fastboot command:
OR
- If your SKYW1911121OS01MP5 update is on SLOT B then use this fastboot command:
Restart BS 2 after flash boot.img
16. Go to XDA and download and install Magisk Manager.
In any cases that BS 2 stuck or can not boot, please enter fastboot mode and flash stock_boot.img from above; repeat Step 5, and reflash boot.img.
-----------------------------------------------------------------------------------
Now Black Shark 2 is rooted with magisk. ^_^ .
---------- Post added at 09:30 AM ---------- Previous post was at 08:45 AM ----------
But i've lost the wifi function. Stock_boot has wifi but boot.img doesn't have. Could you provide a fix for that? Thanks
Click to expand...
Click to collapse
Very Nice tutorial.
tuannghia1985 said:
I've figured by myself, use your stock_boot.img and patch manually with Magisk Manager (v7.5). Magisk Manager return for me a "magisk_patched.img" and by flashing that new file, the wifi is return again. I don't know why but it works for me. Thanks for replied.
Click to expand...
Click to collapse
I would've asked you to do the same. Good that it worked for you.
a51711a said:
I can't update mp5 from mp3, I unlock it now. what should I do?
Click to expand...
Click to collapse
reflash update.zip as the above tutorial instruct you.
KM7 said:
Happy new year everyone!
Since many of you have issues with Black Shark 2 Global, I decided to share my findings with you.
Unlock Black Shark 2 Global Bootloader Commands:
Code:
Fastboot oem bs_unlock
Fastboot oem bs_unlock_critical
Root
Important: Update to SKYW1911121OS01MP5 before rooting.
Check current SLOT:
Code:
fastboot getvar current-slot
If your SKYW1911121OS01MP5 update is on SLOT A then use this fastboot command:
Code:
fastboot flash boot_a boot.img
OR
If your SKYW1911121OS01MP5 update is on SLOT B then use this fastboot command:
Code:
fastboot flash boot_b boot.img
Full OTA Global Factory Image - Fix any issues with the phone and restore it to factory state. This also fixes OTA updating issues.
Dial this from your phone
Code:
*#*#1027#*#*
Start updating your device. You might need to this twice!
Enjoy!
Click to expand...
Click to collapse
It works on Chinese Rom? I would like change from CN to global
I have a bs2 pro Chinese version and I am so disappointed I thought this phone could be customized with custom ROMs and kernels and still nothing ...... I'll never but a black shark product again
Black Shark 2 China rom can do?
tuannghia1985 said:
I have sucessfull flashed in order as below:
1. Backup all your data/media, sms and call log.
2. Dial *#*#1027#*#* then choose Local update.
3. Download SKYW1907040OS01MP3 Stock Factory Image (link above from OP) and move update.zip to “ota” directory in your phone.
4. Press update OTA, after reboot, BS 2 will jump into recovery mode ask for factory reset. Do it or BS 2 won't boot properly.
5. Please allow BS 2 to finish first step of boot up, with least setting up as possible.
6. Go to setting and System update, perform update from S01MP3 to S01MP4, then reboot.
7. Repeat step 5.
8. Repeat step 6 to perform update from S01MP4 to S01MP5, then reboot.
9. Repeat step 5.
10. Turn off the phone and quickly enter Fastboot mode.
11. Perform unlock bootloader by 2 CMD command from above:
12. Restart BS 2, BS 2 will ask for factory reset in Recovery mode. DO IT. (It's very important step cause the BS 2 will stuck at logo if you skip this step).
13. Repeat step 5 (wait until the BS 2 fully operation, enter home launcher, with minimum setting up from beginning). THIS STEP IS ALSO IMPORTANT.
14. Download 2 boot files from OP
15. Check slot_a or slot_b contain your boot original file by cmd command:
- If your SKYW1911121OS01MP5 update is on SLOT A then use this fastboot command:
OR
- If your SKYW1911121OS01MP5 update is on SLOT B then use this fastboot command:
Restart BS 2 after flash boot.img
16. Go to XDA and download and install Magisk Manager.
In any cases that BS 2 stuck or can not boot, please enter fastboot mode and flash stock_boot.img from above; repeat Step 5, and reflash boot.img.
-----------------------------------------------------------------------------------
Now Black Shark 2 is rooted with magisk. ^_^ .
---------- Post added at 09:30 AM ---------- Previous post was at 08:45 AM ----------
But i've lost the wifi function. Stock_boot has wifi but boot.img doesn't have. Could you provide a fix for that? Thanks
Click to expand...
Click to collapse
Black Shark 2 China Version can do that?
Anyone know abd command to relock the bootloader for bs 2? For warranty purpose (Just in case). Thanks in advance.
wga0 said:
It seems that you just lost your stock rom. If your region is same as his, your phone would be updated to SKYW1911121OS01MP5 already. It seems that it was not, so you flashed the MP3 and updated to MP5, which is not for your region and there could be mismatched functions. And you lost both slots, which contain your stock rom/region info. You need to use the factory image to backup your own stock rom, or need to follow the sequence exactly, not reversed.
Click to expand...
Click to collapse
Bro can i have your patched boot.img?what is your region?
Flauros7 said:
Bro can i have your patched boot.img?what is your region?
Click to expand...
Click to collapse
You can see my region at this post. If you leave your revision(or ota link is better) at there, I will find the factory images for your region. Recently, Magisk is updated too often, every weeks. It seems that it's better to patch the stock image by yourself.
KM7 said:
reflash update.zip as the above tutorial instruct you.
Click to expand...
Click to collapse
I TRY IT,Still showing the latest system,can't updates
Hi!
I need help to switch r.o.m w from global to china one because the global one has notification issue and it is pale rom no customization no updates. But I noted that the global rom get very high score on benchmarks I got 462,872 points on antutu benchmark . if some one could try this bench mark on the china rom to see what score they will get, also the over clocking is turned off by default, I think I turned on then did the test you have to dial a secret number to allow over clocking apparently.
Thank yo for your time
Anyone have the China ROM I have retail modes ROM that preventing adb fastboot unlock seems hydra may be my only hope
Just made a new account to confirm the rooting process works. Thank you to KM7, tuannghia1985, wga0, and everyone else for discussing this. The steps I've done were a bit different but I'll try to put it here anyway in case anyone is wondering... (for reference, I'm using Black Shark 2 Global Version just bought a few hours ago)
Prerequisites:
- Your Black Shark 2 must be Global Version. (I haven't tried for China Version yet, might make a separate tutorial if I get my hands on one)
- You will need to prepare Android SDK Platform Tools to execute the needed ADB and Fastboot commands for rooting your device.
- You will also need to be familiar with Command Prompt, or at least comfortable with inputting/copy-pasting commands there.
- You must be ready to forfeit your device in the event that you make a mistake from what's written below. Of course, I cannot be held liable for bricked devices. I am merely restating the procedure I've used for rooting my Black Shark 2 device.
Tutorial:
0. Backup all your files, data, media, etc. You will 100% have to do a factory reset at some point during the rooting process, deleting all user data in your phone.
1. Download the SKYW1907040OS01MP3 Stock Factory Image from OP's post (1.4 GB). It should be named update.zip. Then move the downloaded file to the folder named "OTA". You will find it together along with all the major folders in your internal storage such as "Android" and "Downloads".
2. Dial "*#*#1027#*#*" (without the quotes) on your phone app. A System Update interface should show up, giving you options to adjust the OTA server and to do a local update.
3. Click on the Local Update Button and you should see a percentage in red text pop up. Wait for it to reach 100%.
4. After it reaches 100%, it will tell you to reboot your phone. Now reboot your phone normally.
5. After it reboots, it will go back to your home screen (and not to recovery mode, at least for my version). Go to Settings > System > System Updates.
6. Check the build number (e.g. SKYW1907040OS01MP3) your phone will update to. Two things should happen, in order:
i. You update from "S01MP3" to "S01MP4"
ii. You update from "S01MP4" to "S01MP5"
Once you finish updating from "S01MP4" to "S01MP5" (as long as your current version number ends in S01MP5, you're good), proceed to Step 9. Otherwise, repeat Step 7 and 8.
7. Scroll to the bottom of the update notes and click Update. Ensure your phone is connected to the Internet, and let it download the update.
8. Once the phone downloads it, after a short while, you'll be offered to reboot your device to apply the changes. Reboot the phone, and wait til the phone returns to your home screen and finishes applying the system update entirely.
Notes: During my first try, my update notes were first in Japanese and asked to install around 300 MB. After it finished downloading, it told me the update either failed or got corrupted. Afterwards, the update notes were all typed in English.
9. Patch the stock_boot.img downloaded from OP's post using the latest version of Magisk Manager downloaded from the Magisk GitHub page.
10. You will eventually get another image file named "magisk_patched.img" in the same directory as stock_boot.img (assuming you don't change the filename of the patched image file). Transfer the file to your PC with ADB and Fastboot ready, and place the file inside the platform-tools folder.
11. Activate "Developer Mode" (around 8 taps on About Phone > Build number should do the trick) and enable both "OEM unlocking" and "USB debugging".
12. Connect your phone to your PC via MTP (adjust this via the notification that pops up when you connect it), and click OK when a pop-up appears on your phone for USB debugging.
13. Open Command Prompt inside the platform-tools folder (i.e. cd C:\Users\...\platform-tools) and input the following command in your command prompt:
adb reboot bootloader
Click to expand...
Click to collapse
14. Your phone should then turn off then boot up into what's called Fastboot Mode. Input the following command next:
fastboot oem bs_unlock
Click to expand...
Click to collapse
and:
fastboot oem bs_unlock_critical
Click to expand...
Click to collapse
15. Restart the phone normally by inputting this command:
adb reboot
Click to expand...
Click to collapse
16. Your phone should go into the logo like a normal reboot, and then suddenly give you an option to either do a Factory Reset, or Cancel. Choose the Factory Reset, and wait for your phone to boot up normally again.
17. Set up your device minimally, then FULLY repeat Steps 11, 12, and 13. Reopen Command Prompt if necessary.
Note: if you've been doing things correctly up to this point, the "OEM unlocking" option should be unselectable, as it will say "Bootloader has already been unlocked".
18. Your phone will boot up again in Fastboot Mode. This time, input the following command:
fastboot getvar current-slot
Click to expand...
Click to collapse
19. Command Prompt will then respond with the following:
current-slot: a
Click to expand...
Click to collapse
or:
current-slot: b
Click to expand...
Click to collapse
Take note of this for the next step
20. Take note that if you changed the filename of the patched image file in Step 10, you will have to adjust the next set of commands accordingly. If your current slot is at "a", then input the following command:
fastboot flash boot_a magisk_patched.img
Click to expand...
Click to collapse
Otherwise, if your current slot is at "b", then input the following command instead:
fastboot flash boot_b magisk_patched.img
Click to expand...
Click to collapse
21. Restart your phone normally by repeating Step 15.
22. Install Magisk Manager again from Step 9, and confirm that your phone has indeed installed Magisk, and is now rooted.
Congratulations! You've made it to the very end of the tutorial. If you have any questions, feel free to reply to this post and I will respond as soon as I can. Thank you!
Related
This is a tutorial to restore the Nexus One ROM to Original Shipping Image [updated Jan 12, 2010 @ 23:57 CST]
I am assuming you know how to use ADB and Fastboot as well as some basic OS knowledge be it DOS, OSX, or Linux.
This will do the followings to your Nexus One:
1. Reset your system files to the original system files.
2. Reset your kernel/boot image to the original shipping boot image.
3. Reset your recovery to original recovery (if you wish).
This will not relock your Nexus One. Once you unlock your phone, you are stuck for now.
This is for those of you who decided to flash a few different ROMs and want to restart from scratch.
You may get the Original Shipping Image from HERE or thru Modaco HERE. [22607 build]
MD5sum for the images is: bef86698cafc88ca03fff5758571d9d6 (per DroidDrop)
As before, if you mess up your phone or your computer, you are on your own. I take no responsibility on what you do with your phone or your computer.
Brendenk posted a nandroid back of his fresh image here If you don't want to do an actual factory restore, try this first. If you really really want to do it your way then...
Step 1. Disable backup my settings under privacy settings.
Step 2. unzip the original shipping ROM and put it somewhere you can find.
Step 3. Plug in Nexus One with USB to computer (enable usb and debug modes)
Step 4. adb reboot bootloader (which will boot into the bootloader)
Step 5. Confirm fastboot connection fastboot devices
Step 6*. fastboot erase userdata
Step 7*. fastboot erase cache
*If step 6 and 7 does not work, and if you have Amon_RA's recovery installed, you can do a factory data wipe from there.
Alternately, you can also do a factory data wipe within Android. Settings => Privacy Settings => Factory Data Reset.
Thanks to Brian and setzer715.
Step 8. Go to the directory that you stored your unzipped files.
Step 9. fastboot flash userdata userdata.img
Step 10. fastboot flash boot boot.img
Step 11. fastboot flash system system.img
Step 12. Skip to step 13 if you want to keep recovery (assuming you have a modified recovery such as Amon_RA's recovery). If not fastboot flash recovery recovery.img
Step 13. fastboot reboot
Step 14. After the system boots up and while setting up skip setting up with the google account and you can setup accounts later. This will prevent the phone from pulling down the previous settings (downloaded apps, wallpaper etc) from google.
Step 15. You are done. Enjoy.
Source: Modaco for the ROM Image and HTC for the Instructions.
This post can and will be updated without notice. Keep checking here for the up to date details.
The following information came from user tuffCookie (for those with unlocked bootloader):
ok, after researching, i finally figured it out.
If you have a rooted N1 with a LOCKED bootloader and want to bring it back to complete stock, follow my steps below.
DISCLAIMER: I am not responsible for any damages you may cause to your phone. Proceed at your own risk!
BEFORE YOU BEGIN: Just to be safe, make sure your battery is fully charged.
1) Find and download FRG33 IMAGE FORMAT from MoDaCo here: http://android.modaco.com/content/go...root-insecure/
2) Rename the file to PASSIMG.zip
3) Place the zip file on the root of your sdcard
4) Reboot into bootloader (power on your phone while pressing the vol down button)
5) Bootloader will automatically find and check PASSIMG.zip. Give it a minute and it should eventually show "Parsing....[SD ZIP]" and a list showing boot, bootloader, radio, recovery, etc and ask if you want to start the update. Press vol up for yes.
7) The update process will begin and automatically start flashing each item on the list. DO NOT POWER DOWN THE DEVICE DURING THIS PROCESS!!!
8) When it asks to reboot the device, press vol up for yes.
9) Now you're back to complete stock! If you want, you can go into settings and do an OTA system update.
Click to expand...
Click to collapse
Great tutorial, thanks for all your work in the nexus area
thank you!!! exactly what i need!!!
hks18psigst said:
thank you!!! exactly what i need!!!
Click to expand...
Click to collapse
I saw the other post you posted under wifi thread. You're welcome.
system.img should take a while to flash right? i'm getting nervous
took like 20 mins but all done nvm and thanks sooo much
system.img is only 110 odd MB. The whole process took a few minutes (less than 3) for me. But I know what I am doing.
Nice Work.
Does this lock the bootloader?
Edit: Just saw your twitter...fml
seraph1024 said:
This is a tutorial to restore the Nexus One Step 3. adb boot recovery
Step 4. from recovery console, Wipe => Wipe data/factory Reset.
< You may also do step 3 and 4 from Nexus -- Do a search -- Google has it in their FAQs >
Click to expand...
Click to collapse
You can also wipe data using fastboot:
fastboot erase userdata
swetland said:
You can also wipe data using fastboot:
fastboot erase userdata
Click to expand...
Click to collapse
Yes. Thanks Brian. Forgot about that. Probably should clear cache too right?
Yeah, if you're going for that new phone smell, erasing cache too makes sense.
Thanks again.
I've updated the instructions and this should make things more to the "blank slate" status before the ROM is reflashed.
If anyone is stuck etc, feel free to PM or contact me via AIM or twitter
Can we get a mirror and an md5sum? RS and MU are going REALLY slow
Since I did not supply the images, you have to check the thread for the people who supplied the thread. I can upload to a different source or on my own server if there is a major request (pending permission from the original source at modaco).
Nice write up, but on Step 3 I think you meant adb REBOOT bootloader, not BOOT. Save ya a butt load of newb "I cant get step 3 to work" posts.
Also I cannot get fastboot erase userdata to work. I get "erasing 'userdata'... FAILED <remote: not allowed>. I had to erase in recovery.
Anyone have an MD5Sum for the passimg?
Restore your Nexus One to its Original Shipping Image
I have rewritten the above guide..
Restore your Nexus One to its Original Shipping Image - http://www.machackpc.com/headline/restore-your-nexus-one-to-its-original-shipping-image/
Please let me if I am missing anything.
Thanks
MacHackPC
http://www.machackpc.com
machackpc said:
I have rewritten the above guide..
Restore your Nexus One to its Original Shipping Image - http://www.machackpc.com/headline/restore-your-nexus-one-to-its-original-shipping-image/
Please let me if I am missing anything.
Thanks
MacHackPC
http://www.machackpc.com
Click to expand...
Click to collapse
I have no issues with anyone linking to this site. I do have an issue with the people that just want to copy our work here and repost it like they just figured out how to do that. Please link back to XDA and Modaco for the ROMs. The reason why we keep things centralized is so that people do not have miscommunications while updates are not being made on the mirrored sites.
Now for comments.
1. You don't need to download the drivers again. Why? People have already rooted their devices, thus drivers installed. If you have not rooted the N1, no need for restore.
2. Why do you need to download and unzip superboot? (again no credit to the site of where superboot came from).
3. We are still having issue of erase userdata. When I update the instructions, will you update yours or will you leave people in the dark more confused than ever.
Single source of clear direction helps. Multiple source of multiple directions cause chaos.
If I am wrong in my reasoning, please let me know. We are all here to share.
question: why disable backup my settings?
I know there are other threads out there that offer exactly what this does, but even with those, I think it can still be a bit tricky to figure out what to do if you're looking to root and modify your phone. I made this thread to collect everything I've done in one place. This should make everything very straightforward and basically n00b-proof.
I take no credit for any of this work. Please thank all the hardworking devs!
**Following all of these steps will WIPE all data from your phone. Backup before beginning. While these should all be safe, there's always the possibility of bricking your phone. I take no responsibility if you do.**
What you'll need:
USB Cable
USB port
HTC Droid DNA (without the OTA update!)
PC running Windows
Glass of Orange Juice (for the Vitamin C!)
**All of this shouldn't take more than 30 minutes but just in case, make sure your phone has at least a 70% charge.**
Preparing (Installing SDK, Setting PATH, testing ADB)
I highly recommend creating a directory on the root of your C: drive on your PC to hold ALL related files. I called mine "android" but you can call yours whatever you'd like. Whenever issuing any ADB command, make sure you navigate to this folder first.
1. Connect your phone to your computer. One of the pop ups will ask to install HTC Sync. Install this to install the drivers onto your computer. Once installed, you can go into your Add/Remove Programs and uninstall the HTC Sync software if you want.
2. Enable USB Debugging in your HTC Droid DNA from the path “Settings > Applications > Development > USB debugging”. The option of USB Debugging should be ticked.
2. Download the latest version of the Android SDK to your PC here.
3. Extract the files to your PC (I recommend something easy like C:\android)
4. Run the SDK Manager and uncheck everything but the Platform Tools and install
5. Add the SDK tools to your system PATH file by doing the following:1. Simultaneously hold down the Windows Key + R
2. type 'sysdm.cpl' into the run dialogue box and click OK
3. On the system properties window that just opened, click on the 'advanced' tab. Then click on 'Environment Variables'
4. Scroll down through the System variables until you find the PATH. Click 'Edit', then add ';C:\android' (or whatever you named your folder) to the end of the line
5. Click OK and close the open windows.6. Test ADB by connecting your phone to your PC then:1. Open a new command prompt window by pressing Windows+R and typing "cmd" into the box
2. Type 'adb devices' and press enter. You should see your phone's UID listed.
If it says adb devices is not a recognizable command then you didn't setup your PATH correctly
If it says <waiting for device> then your missing the drivers or you didn't enable USB debugging. Try rebooting, and if it still doesn't show, reinstall HTC sync.
Other Tips
You can download all the files necessary at the beginning and do everything through ADB.
Always check the MD5-hash after downloading a file. If they don't match, the download is corrupt and you should try again. I use this simply tiny, no-install MD5 checker.
Always Test after each install to ensure it is working properly. Don't just string all of these together without rebooting once. Bad things might happen and you'd have no idea what's causing it.
You can reboot your phone into the bootloader by either issuing the command "adb reboot bootloader" or pressing and holding the PWR and VOL DN buttons simultaneously when you reboot your phone.
From the bootloader you can enter recovery or you can issue the command "adb reboot recovery"
If your command prompt hangs pressing Ctrl+C will break out of the running command.
Some useful command prompt (DOS) commands:
cd - change directory (ie. 'cd C:\android' will change to the 'C:\android' directory)
cd .. - moves up one directory level
dir /p - lists files within the current directory
Unlocking Bootloader
The next step is to unlock the bootloader. The best method right now is provided by jcase. NOTE: Don't install the OTA update or you won't be able to do this!Step 1: Get SuperCID
Full instructions can be found here.
1. Download .apk from link above.
2. Run the app
3. Run the following Commands via ADB
Code:
adb reboot bootloader
(wait for phone to reboot into bootloader)
fastboot oem readcid
If you see 22222222 you're good to proceed. If you see anything else, reboot the phone and try again.
Step 2: Unlock via HTC Dev site
Go to the HTC Developer website and carefully follow the instructions. They're very straight forward.
When completed you'll have unlocked the bootloader. You'll see a new warning on the splash screen and the bootloader will say *tampered* at the top.Install Custom Recovery
You can choose either ClockworkMod (my preference) or TWRP recoveries.
1. Download the latest version of your preferred recovery. rename it "recovery.img"
2. Using ADB issue the following commands
Code:
adb reboot bootloader
(once the phone reboots into the bootloader)
fastboot flash recovery recovery.img
(once installation is complete)
fastboot reboot
Now you'll have a custom recovery, and can make a full nandroid backup (recommended!).
S-OFF
Full instructions can be found here. beaups did an excellent job writing this up so it would be pointless for me to reproduce here.
Root / Custom ROM
Choose any ROM you'd like. I prefer Team Venom's ViperDNA. I'll use that as the basis for the next steps.
1. Download the full ROM found in the second post in the above link to your phone.
2. Reboot into recovery
3. Select "install zip from sdcard" and choose the ROM .zip file mentioned above. Follow the instructions on screen.
Note: If you choose a different ROM make sure it either includes a kernel that supports system write or you have to install one first by doing the following. Also, if you have WiFi issues after flashing the ROM follow these steps to reinstall the kernel.Installing the Kernel
1. Download a Kernel (such as dsb's Cubed Kernel)
2. Unzip the file and copy the modules.zip file to your phone.
3. Via ADB issue the following commands:
Code:
adb reboot bootloader
(once rebooted)
fastboot flash boot boot.img
(once complete)
fastboot reboot recovery
The phone will reboot into recovery, at which point you should flash the modules.zipENG HBOOT
This is *Optional* and allows for additional ADB commands to be used.
1. Download the HBOOT-8064 file found here. (thanks to fnoji111 and Argumentation)
2. Via ADB issue the following commands:
Code:
adb reboot bootloader
(once rebooted)
fastboot oem rebootRUU
(once rebooted to the black HTC screen)
fastboot flash zip PL83IMG.zip
(once complete)
fastboot reboot
Mods
These are some mods I found to be essential.Remove the Splash Screen disclaimer
Full instructions can be found here.
1. Go to the above link and download the RegawMOD tool (first post) AND the Droid DNA ENG Hboot plugin (2nd post).
2. Make sure the plugin is in the same folder as the tool.
3. Customize it how you'd like. I chose to replace the disclaimer with my own, that basically reads
If Found, Please Return to
*Drumz0rz*
*My Home Phone Number*
Click to expand...
Click to collapse
4. When you're finished press "Create ZIP" and save the file.
5. Via ADB issue the following commands:
Code:
adb reboot bootloader
(once rebooted)
fastboot oem rebootRUU
(once rebooted to black HTC screen)
fastboot flash zip <YourZipName>.zip
(once complete)
fastboot reboot
Now you should have a fully unlocked S-OFF custom ROM, custom Kernel, HBOOT Droid DNA! I hope this helps!
Will this method work for new ota ?
Sent from my HTC6435LVW using xda premium
No, it's just a summary of what's out there. When someone releases a new method to unlock the bootloader I'll update it.
Thank you, when I rooted using the guide linked from one of the sticky posts most of the links were dead, so it is nice to have this.
One suggestion - perhaps include the steps to finish up for those that want to stay on stock rom but be rooted.
drumz0rz said:
No, it's just a summary of what's out there. When someone releases a new method to unlock the bootloader I'll update it.
Click to expand...
Click to collapse
Thanks def look forward to that
Sent from my HTC6435LVW using xda premium
Thanks! Having these steps in a simple guide saved me a good bit of time.
Minor confusion on "Installing the Kernal". I extracted Cubed.Stock.System.Write.zip, flashed boot.img, then flashed Modules.zip in recovery. From the guide, does renaming the package to boot.img work as well?
Lastly, I'm not sure if you want to include flashing/loading ViperDNA's OTA updates.
Is there a way to factory reset phone and eliminate OTA update? I'm assuming no but never hurts to ask....
Sent from my HTC6435LVW using xda app-developers app
John58543 said:
Is there a way to factory reset phone and eliminate OTA update? I'm assuming no but never hurts to ask....
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
No
Sent from my HTC6435LVW using xda app-developers app
steventrev said:
Thanks! Having these steps in a simple guide saved me a good bit of time.
Minor confusion on "Installing the Kernal". I extracted Cubed.Stock.System.Write.zip, flashed boot.img, then flashed Modules.zip in recovery. From the guide, does renaming the package to boot.img work as well?
Lastly, I'm not sure if you want to include flashing/loading ViperDNA's OTA updates.
Click to expand...
Click to collapse
As in renaming the zip? No, you need to do what you said, I left out the flashing the modules. I'll fix that, thanks.
Detailed guide, one question what if you don't have orange juice and want to use Gatorade as a substitute?
Sent from my HTC6435LVW
I'm no nutritionist but I think those two serve very different purposes. Now if you want to substitute it for a glass of say whiskey... that I think is more than acceptable.
Hi. I've been rooted with Magisk ever since I got this phone but now I got tired of having to wipe everything, every time I tried to take OTA.
I've tried unroot and flash stock boot.img, but that wasn't enough to take OTA. I've tried factory reset from within settings and not even that worked.
OTA still failed at step 3.
So this is what I finally did, and it worked.
DISCLAIMER
I AM NOT RESPONSIBLE FOR ANY LOSS OF DATA. IT SHOULD WORK FINE, BUT
IF YOU HAVE INVALUABLE PICS OF YOUR KITTEN, PLEASE MAKE A BACKUP TO BE SAFE
Uninstall any substratum overlays you have installed and unroot from within Magisk Manager.
Reboot your phone.
Unpack your current firmware in the same location where you have adb/fastboot and unzip the "XT-1941-flash_No-wipe.bat" to same directory.
Boot your phone to fastboot mode, plug the cable in, open cmd and drag the "XT-1941-flash_No-wipe.bat" in to the cmd window.
It will automaticly flash all files in the firmware, without wipe. Just wait for it to finish.
Reboot and take the OTA.
After that I booted TWRP and made a backup of boot.
Booted to system, installed Magisk Manager, renamed the backup to boot.img and patched it with Magisk Manager, then flashed it in TWRP. (fastboot works too)
Now I'm updated to PPKS29.68-16-21-3 without having to go through the painfull process of backing up and restoring all data.
Been waiting for something like this. Thanks.
Tested on XT1941-4 DEEN RETEU PPKS29.68-16-21-2, update to PPKS29.68-16-21-3
Used script and update gone past step 3 and rebooted successfully.
Thanks for your guide. Just two questions
1. What's the right fastboot command?
fastboot flash boot_a patched_boot.img
or
fastboot flash boot_b patched_boot.img
2. There is an extra file named "system.img_sparsechunk.9" in the stock firmware PPKS29.68-16-21-2, but there is no command for flashing this file in your .bat file. Is this not important?
vrezaei said:
Thanks for your guide. Just two questions
1. What's the right fastboot command?
fastboot flash boot_a patched_boot.img
or
fastboot flash boot_b patched_boot.img
2. There is an extra file named "system.img_sparsechunk.9" in the stock firmware PPKS29.68-16-21-2, but there is no command for flashing this file in your .bat file. Is this not important?
Click to expand...
Click to collapse
Hmm that's strange. I just had a look at the PPKS29.68-16-21-2 but I don't have any.
View attachment 4782745
For the boot you can just use fastboot flash boot patched_boot.img
It will flash the active slot if you don't specify.
tys0n said:
Hmm that's strange. I just had a look at the PPKS29.68-16-21-2 but I don't have any.
View attachment 4782745
For the boot you can just use fastboot flash boot patched_boot.img
It will flash the active slot if you don't specify.
Click to expand...
Click to collapse
Sorry about my mistake
My current and planing to update build numbers are PPKS29.68-16-36-2 & 3, respectively and the first one (my current stock firmware) contains system.img_sparsechunk.9 file. So, I think I must edit your .bat file and add the appropriate command for flashing this file.
vrezaei said:
Sorry about my mistake
My current and planing to update build numbers are PPKS29.68-16-36-2 & 3, respectively and the first one (my current stock firmware) contains system.img_sparsechunk.9 file. So, I think I must edit your .bat file and add the appropriate command for flashing this file.
Click to expand...
Click to collapse
Oh ok. I'll take another look when I get home, but yeah, you'll have to add the additional file if there is any.
Sent from motorola one.
If I understand correctly, after that step:
tys0n said:
Reboot and take the OTA.
Click to expand...
Click to collapse
Do I just need reinstall Magisk?
damiann69 said:
If I understand correctly, after that step:
Do I just need reinstall Magisk?
Click to expand...
Click to collapse
Ya
tys0n said:
Hi. I've been rooted with Magisk ever since I got this phone but now I got tired of having to wipe everything, every time I tried to take OTA.
I've tried unroot and flash stock boot.img, but that wasn't enough to take OTA. I've tried factory reset from within settings and not even that worked.
OTA still failed at step 3.
So this is what I finally did, and it worked.
DISCLAIMER
I AM NOT RESPONSIBLE FOR ANY LOSS OF DATA. IT SHOULD WORK FINE, BUT
IF YOU HAVE INVALUABLE PICS OF YOUR KITTEN, PLEASE MAKE A BACKUP TO BE SAFE
Uninstall any substratum overlays you have installed and unroot from within Magisk Manager.
Reboot your phone.
Unpack your current firmware in the same location where you have adb/fastboot and unzip the "XT-1941-flash_No-wipe.bat" to same directory.
Boot your phone to fastboot mode, plug the cable in, open cmd and drag the "XT-1941-flash_No-wipe.bat" in to the cmd window.
It will automaticly flash all files in the firmware, without wipe. Just wait for it to finish.
Reboot and take the OTA.
After that I booted TWRP and made a backup of boot.
Booted to system, installed Magisk Manager, renamed the backup to boot.img and patched it with Magisk Manager, then flashed it in TWRP. (fastboot works too)
Now I'm updated to PPKS29.68-16-21-3 without having to go through the painfull process of backing up and restoring all data.
Click to expand...
Click to collapse
I am new to this, could you please give us step by step process or a video will help, Thanks for the efforts
Thanks tys0n for sharing this! I've updated a few times using this way.
But from time to time Motorola is changing files or commands and I had allways to check, if the commands in the bat file match those of the servicefile.xml and to adapt it accordingly.
First I thought about to write a small 'servicefile2bat' converter tool - but since almost everything already exists, I did a search and found this one:
https://sourceforge.net/projects/flashfile2batchfile/
I've tested it with today's update to DEEN_QPKS30.54_22_7 and it works perfectly.
There's a ton of information out there, but finding it can sometimes be a challenge, especially for a newbie. And then there's posts to read through, in case a process has changed and it's only talked about in a single place, buried any number of pages back. So this is my attempt to put all Pixel 3 how-to's into a single thread. Everything below is what worked for me, from start to finish, with a fresh phone directly from Google that was bootloader-locked, unrooted, and running stock Android. Comments are welcome and encouraged: if something doesn't work for you, or you have a better/quicker/more reliable way of doing something, or maybe I made a mistake...let me know!
A few things:
Everything in this guide was tested on a "regular" Pixel 3 (blueline). It should all work exactly the same on a Pixel 3 XL (crosshatch), as long as you download the appropriate files (specifically the factory/OTA images and TWRP). I'm posting this in both blueline and crosshatch forums.
This first post will have links to files and the tools you need, as well as general things (like how to enable debugging and boot into recovery). The second post has how-to's for the big stuff (flashing images, TWRP, unlocking, etc).
I'm not responsible for anything you do. Follow these guides at your own risk. Doing so may also void your warranty.
Files and URLs
Official Android files
Factory (wipes device and requires unlocked bootloader): https://developers.google.com/android/images
Full OTA (leaves data intact, can be done via ADB sideload): https://developers.google.com/android/ota
Preview/beta OTA: https://developer.android.com/preview/download-ota.html
TWRP
XDA thread: https://forum.xda-developers.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622
Download: https://dl.twrp.me/blueline/
Magisk
XDA thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
GitHub: https://github.com/topjohnwu/Magisk/releases
ADB and Fastboot
Google USB drivers: https://developer.android.com/studio/run/win-usb
SDK platform tools: https://developer.android.com/studio/releases/platform-tools
Download the ZIP and open (no need to extract the whole thing)
Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
General
Enable USB debugging
Download Google USB drivers (see above)
Download SDK platform tools and copy required files to their own directory (see above)
Enable USB debugging (Settings > About > tap Build 7 times > back > Developer options)
Plug phone into computer and when "Allow USB debugging" box comes up, check the box and allow (may need to have adb daemon running on the computer already, see below)
Fastboot mode (using hardware keys) aka bootloader
Power off
Hold VOL- and press/hold PWR until bootloader (fastboot) comes up
Recovery mode (using hardware keys)
Get into Fastboot mode (see above)
Use VOL buttons to find Recovery in the list, use PWR to select (should boot to broken android image)
Hold PWR and press VOL+ once to get into recovery
Useful ADB and Fastboot commands
Enable USB debugging (see above)
ADB (used while phone is "on" and booted up):
Use "adb devices" to ensure the computer is authorized
Use "adb reboot bootloader" to get into Fastboot
Fastboot mode
Use "fastboot devices" to verify computer can see your phone
Update #1: Items below marked through were removed since they don't really apply to Android 10.
Update #2: Edited to reflect changes in root with Android 11.
A quick note: everything below is assuming you're using Windows 10. When it says "Type...", this assumes you've opened a command window in the location of adb/fastboot and that all files referenced are in the same directory and (in some cases) renamed as I reference them (short names without spaces simplifies things). If you're using Powershell, you will probably need to change "adb" and "fastboot" to read ".\adb" and ".\fastboot" so Powershell will use the local files.
Unlocking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
In Developer Options, enable OEM unlocking and confirm (it may ask you to input fingerprint or PIN/pattern/password)
Boot into Fastboot mode (see above)
Type to unlock:
Code:
fastboot flashing unlock
Use VOL+ key to get the options on the screen to read "Unlock the bootloader" and use PWR button to select
Type to reboot:
Code:
fastboot reboot
Locking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Boot into Fastboot mode (see above)
IMPORTANT: restore stock recovery if you replaced it with TWRP (this should prevent the "Can't find valid operating system" issue)
Type to lock:
Code:
fastboot flashing lock
Use VOL buttons to find "Lock the bootloader" and use PWR to select
Type to reboot:
Code:
fastboot reboot
Factory reset via fastboot (can also do this without wiping data)
THIS COULD WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Download factory image ZIP and unzip all files into their own folder
Unlock bootloader (see above)
Reboot into Fastboot mode
You have 2 options:
Register the location of fastboot.exe with the PATH system variable and run "flash-all.bat"
Wipe data: just run "flash-all.bat" and call it a day
Do not wipe data: open "flash-all.bat" in a text editor (careful not to double-click and run it!), remove the "-w" from the last line to disable the wiping of data, then save, close, and run
Move the 3 files (bootloader IMG, radio IMG, image ZIP) into the ADB folder, rename for simplicity if you want, launch cmd or Powershell, and run the commands below (which come from "flash-all.bat")
Wipe data: type out commands below, but at last line, add "-w" flag: fastboot -w update image.zip
Do not wipe data: type out commands below as written (no "-w" flag)
The commands:
Code:
fastboot flash bootloader bootloader-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image-blueline-XXXX.zip
Note: The last command (update image) will launch the red "fastbootd" screen, so don't worry and be patient while the command line tells you what's happening. The phone will reboot on its own into the Android system (not fastboot) afterward.
Root Android 10+ using Magisk (Canary channel)
This must be done after every update, and you cannot use the patched file from a different phone!
Unlock bootloader (see above)
Download factory image (not OTA, see link above)
Download and install Magisk Manager Canary (see link above)
In Magisk Manager settings, set Update Channel to "Canary"
Extract boot.img from image-blueline-XXXX.zip found in the factory image you downloaded
Place boot.img on your phone's internal storage
Open Magisk Manager and do:
tap "Install" button (next to "Magisk" in first block on the main screen)
"Select and Patch a File" option
Find boot.img file you just placed on your phone
tap "Let's Go"
When finished, move the newly-created magisk_patched.img file over to your computer's ADB directory
Reboot into bootloader
Type:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Open up Magisk Manager and make sure everything's good!
Note : if you get stuck in fastboot mode or in a boot loop, flash the stock boot.img to both slots and try again
Code:
fastboot flash boot boot.img --slot all
Optional:
for adblocking, tap "Systemless hosts" in Magisk Manager, then install AdAway using F-Droid
install a performance kernel like Kirisakura for Bluecross (R)
Updating Android 10+ while rooted
You can't take an OTA while rooted, so updating Android 10+ (as in monthly updates) can be one of two ways.
Method #1 (faster, but more chance for issues)
Download OTA ZIP and move it to ADB folder (don't unzip it)
This does not require an unlocked bootloader, but does require USB debugging (see above)
Get boot.img from the factory image (see first post on where to download this) and place your ADB directory
Reboot into bootloader / fastboot and type to restore stock boot to both slots:
Code:
fastboot flash boot --slot all boot.img
fastboot reboot bootloader
[wait for reboot]
Use VOL buttons to select "Apply update from ADB"
Type (where filename is the name of the file you want to sideload):
Code:
adb sideload filename.zip
Wait for it to finish, will take you back to Recovery when it's done
Reboot using menu
Method #2 (takes longer, but best bet for minimal issues)
Follow "Factory reset via fastboot" instructions (see above, make sure you don't wipe your data!)
Take the OTA in the official way (through Android)
Follow "Root Android 10+ using Magisk Canary" instructions (see above)
Boot into TWRP (3.3.0-0 or higher)
Download TWRP IMG and place in ADB folder (rename the file to twrp.img)
If not already done, unlock the bootloader (see above)
Reboot into bootloader
Type to boot TWRP (it will restart and should boot into TWRP):
Code:
fastboot boot twrp.img
OPTIONAL: Replace recovery by installing TWRP
Your phone should automatically mount, so move twrp.img from PC to Download folder on phone's internal storage
Advanced > Install Recovery Ramdisk > choose TWRP IMG > Swipe to install
Back > Fix Recovery Bootloop > Reboot System > Do Not Install when asked if TWRP should install app
Root using Magisk (18.1 or higher)
Download Magisk ZIP and move to device
Boot into TWRP (see above)
Enter your PIN/pattern/password to decrypt (unnecessary if you are not using security on your phone)
Swipe to Allow Modifications (to system)
Install > find and select the Magisk ZIP > Slide to install
Wipe cache > Reboot system > Do Not Install when asked if TWRP should install app
Open Magisk Manager to verify latest and to install modules
"Can't find valid operating system" booting issue
Unlock your bootloader again (see above)
Follow steps for "Factory reset via fastboot" (see above) and keep the wipe flag
After it reboots, power off (press PWR and select "Power off" from menu)
Follow steps for "Locking the bootloader" (see above)
After it reboots into Fastboot mode, have it start using the PWR button
Android Recovery / "Cannot load Android system" booting issue
This can happen for a number of reasons, but the fix is the same: "Factory reset via fastboot" (see above). You probably do not need to wipe user data, so you can omit the "-w" flag.
If you still get the error message, select the "Try again" option. If it still doesn't work, try "Factory reset via fastboot" again, as well as "Try again". If it doesn't work this time, you probably have no choice but to do a factory reset (in which you will definitely lose your data).
If it happens after flashing Magisk in TWRP, though, you've got a slightly different issue and the problem will persist no matter how many times you flash the factory images and re-install Magisk. This is probably due to something leftover in the previous Magisk installation that conflicts with the new installation. There are two ways to handle this.
First and easiest: uninstall Magisk Manager app before rebooting into the bootloader and running fastboot commands. Then proceed as usual (sideload OTA or flash factory images via fastboot, boot TWRP, and flash Magisk). All guides for this are above. This method preserves any modules you have installed.
Second and more complete (if the above method still gives you trouble):
download to your phone the Magisk ZIP, Magisk Uninstaller ZIP, and Magisk APK from this XDA thread
uninstall the Magisk Manager app
reboot to bootloader
using fastboot, boot into TWRP using IMG (you don't need to replace boot with TWRP)
flash Magisk Uninstaller ZIP
wipe Dalvik
flash Magisk ZIP
wipe Dalvik
reboot system (do not install TWRP)
install Magisk Manager APK and re-install any modules
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
wangdaning said:
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
Click to expand...
Click to collapse
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
rczrider said:
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
Click to expand...
Click to collapse
Was my misunderstanding. I thought you were implying people should go back to stock recovery to flash ota. You are talking about flashing ota in twrp. You might clear that up a little bit in that section.
Great post.
Unfortunately, if you are writing a process, then writing everything out is a requirement. Especially with item numbers or using an outline format. Not everyone understands shortcuts taken or abbreviated words, unless they are spelled out in the beginning. IMO, wrote and read too many processes. Including software requirement documentation.
Hi,
thanks for the thread :good:
wangdaning said:
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
Click to expand...
Click to collapse
Yes, I think so too.
rczrider said:
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
Click to expand...
Click to collapse
The boot.img is into "image.zip"
Then I suggest to flash into a and b (or both)
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
or
fastboot flash boot --slot all boot.img
Edit
be careful here: Factory reset via ADB sideload (can also do this without wiping data)
bootloader is bootloader, boot is boot, bootloader.img isn't boot.img
so, maybe better to write:
fastboot flash bootloader nameofbootloader.img or if simply renamed fastboot flash bootloader bootloader.img
deleted, bug.
trouble flashing files
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
fyrmd said:
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
Click to expand...
Click to collapse
Please read the instructions carefully. You cannot flash twrp directly. "fastboot boot twrp.img" then when twrp boots you can use it or make it permanent by flashing the install zip or the internal twrp option. I go with the install zip as it seems more stable to me (placebo I suppose).
wangdaning said:
Please read the instructions carefully. You cannot flash twrp directly. "fastboot boot twrp.img" then when twrp boots you can use it or make it permanent by flashing the install zip or the internal twrp option. I go with the install zip as it seems more stable to me (placebo I suppose).
Click to expand...
Click to collapse
Thanks, but still no luck.
fyrmd said:
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
Click to expand...
Click to collapse
Turns out it was the cable, it is an expensive one from Amazon so not sure what I should be purchasing for next time.
fyrmd said:
Turns out it was the cable, it is an expensive one from Amazon so not sure what I should be purchasing for next time.
Click to expand...
Click to collapse
I always buy Anker cables and chargers. All have been good so far.
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
xiaowei666 said:
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
Click to expand...
Click to collapse
Are you able to get into recovery? If so, download the full ota to your pc and side load it with adb.
xiaowei666 said:
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
Click to expand...
Click to collapse
i same issue
rczrider said:
[*]Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
Click to expand...
Click to collapse
why not copy all files?
---------- Post added at 11:58 AM ---------- Previous post was at 11:55 AM ----------
fyrmd said:
Thanks, but still no luck.
Click to expand...
Click to collapse
boot to the twrp.img and flash the twrp.zip, unless you are on android 10 you should have no problem unless you are doing it wrong. not exactly hard to do.
How to enable oem unlock in this case?
pedro5148 said:
How to enable oem unlock in this case?
Click to expand...
Click to collapse
There are a few suggestions at https://www.theandroidsoul.com/how-to-fix-oem-unlock-greyed-out-or-oem-unlock-disabled-problem/
However, if the network carrier has locked the bootloader, you cannot unlock it. In the U.S., Verizon and AT&T phones generally cannot be unlocked due to locked bootloaders.
Devices that started to be received today have Oxygen OS 10.5 out of the box.
No flashable zip for that software release is publicly available, meaning its stock boot.img cannot be extracted.
You then need to update to a newer build first. You can do so from my OxygenOS builds repo thread.
Once done, enable developers options and enable OEM unlock.
Reboot to fastboot (enable USB debugging in dev options and use adb reboot bootloader)
Type fastboot oem unlock and accept to unlock bootloader (warning: as a safety measure Android will wipe your userdata)
Go through OxygenOS setup
Install Magisk Manager from https://github.com/topjohnwu/Magisk/releases/download/manager-v7.5.1/MagiskManager-v7.5.1.apk
Move stock boot.img to your phone internal storage (please open spoiler)
For your convenience, 10.5.2 stock boot.img for EU and India have been extracted
EU download: https://drive.google.com/file/d/18aPqErEMbRqmN4BpdvHE4OKgizDcEbou/view?usp=sharing
India download: https://drive.google.com/file/d/1ZIEYWH2PYkKyojq_S_i_onBstejHKDTJ/view?usp=sharing
For future builds, you can use payload dumper (Windows) , (Linux ) to extract stock boot.img
Click on Install
Choose "Select and patch a file"
Select your stock boot.img
Wait until Magisk patches your boot.img, and once patched it can be found in the Downloads folder
Copy that patched boot.img (which should be named magisk_patched.img) to your computer
Boot into fastboot again
Type fastboot getvar current-slot into your terminal window and press Enter.
If the output is a , type fastboot flash boot_a magisk_patched.img into your terminal window and press Enter.
If the output is b , type fastboot flash boot_b magisk_patched.img into your terminal window and press Enter.
Reboot to OxygenOS
Open Magisk Manager and your device should now be rooted.
TIPS:
- Ensure you got latest platform tools installed from https://developer.android.com/studio/releases/platform-tools
- Backup your /persist once rooted (dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img) and save it somewhere on your cloud/computer, this might save you from a broken fingerprint sensor and an RMA in the future if it turns out this device has same issue as 8-series when it comes to crossflash regional builds of OOS.
Credits:
@topjohnwu for making Magisk
/u/Jisifus for testing on his device and for screenshots
Some_Random_Username said:
TIPS:
- Ensure you got latest platform tools installed from https://developer.android.com/studio/releases/platform-tools
- Backup your /persist once rooted (dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img) and save it somewhere on your cloud/computer, this might save you from a broken fingerprint sensor and an RMA in the future if it turns out this device has same issue as 8-series when it comes to crossflash regional builds of OOS.
Click to expand...
Click to collapse
Great to see it works this way and thanks for the tip.:good:
do u lose all data while rooting?
#edit1
nevermind, cannot read right
OK, will give this a try asap,have the device here now...
I gave it a try, works like a charm! Thanks for this! Small tip, unlock bootload before u copy your files
now my phone is a bit laggy. with magisk on it.. i will test it later if its getting better
Some_Random_Username said:
Type fastboot getvar current-slot into your terminal window and press Enter.
If the output is a , type fastboot flash boot_a magisk_patched.img into your terminal window and press Enter.
If the output is b , type fastboot flash boot_b magisk_patched.img into your terminal window and press Enter.
Click to expand...
Click to collapse
You can simply type "fastboot flash boot magisk_patched.img" - it flash boot to current active slot. Just for note.
Can confirm that it works, just tried it myself
If WiFi/data does not work (usually happens when you flash wrong version, but can also happen if you flash correct one), fastboot boot the image, then do a direct install in Magisk Manager.
Also, big thumbs up for adding tips for persist backup, I see too many people needing to send their device back because they messed it up somehow.
Failed for me
Hi and thanks for the tips.
Running 10.5.2 (latest build) and Bootloader is unlocked.
1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).
Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.
Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.
jmwengineering said:
Hi and thanks for the tips.
Running 10.5.2 (latest build) and Bootloader is unlocked.
1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).
Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.
Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.
Click to expand...
Click to collapse
The size is normal.
When patching your image you have to select "Preserve Force Encryption" and "Preserve AVB 2.0/dm-verity" under advanced settings in the main screen where you patch the image.
jmwengineering said:
Hi and thanks for the tips.
Running 10.5.2 (latest build) and Bootloader is unlocked.
1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).
Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.
Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.
Click to expand...
Click to collapse
And that's why it's recommended to boot the patched image first.
Thanks
Lossyx said:
The size is normal.
When patching your image you have to select "Preserve Force Encryption" and "Preserve AVB 2.0/dm-verity" under advanced settings in the main screen where you patch the image.
Click to expand...
Click to collapse
Thanks for confirming file size - Preserve Force Encryption and Preserve AVB 2.0/dm-verity were ticked during the patching process. Guess I'll have to wait until TWRP is verified as Nord compatible.
---------- Post added at 07:06 PM ---------- Previous post was at 06:59 PM ----------
Kollachi said:
And that's why it's recommended to boot the patched image first.
Click to expand...
Click to collapse
Thanks for the reply. Not sure what you mean by booting the patched image first. You have to create the patched image on the phone first before you can flash and then boot it. Step 7 in my post above details the flashing of the patched image and subsequent attempt to reboot Oxygen OS. I can't boot the patched image until I've created and flashed it!
jmwengineering said:
Thanks for the reply. Not sure what you mean by booting the patched image first. You have to create the patched image on the phone first before you can flash and then boot it. Step 7 in my post above details the flashing of the patched image and subsequent attempt to reboot Oxygen OS. I can't boot the patched image until I've created and flashed it!
Click to expand...
Click to collapse
Nah, instead of flash the patched boot image you can boot it only. Not sure why it's not working for you. But usually it should work.
Command: fastboot boot "patched boot image"
Edit: that's also what lossyx said. Boot image and than install it with magisk manager.
And if you boot the image and something went wrong you aren't bricked or anything. It's a safe way to test something.
Thanks for the advice - will boot the image file on my PC rather than flashing first.
Sent from my AC2003 using Tapatalk
Does unlocking the bootloader break widewine L1 on this device like it did with 7/7T/7P/7TP/8/8P
..
CryllicBuster273 said:
Does unlocking the bootloader break widewine L1 on this device like it did with 7/7T/7P/7TP/8/8P
Click to expand...
Click to collapse
Yeah I guess when you unlock your phone it will break L1 as always.
---------- Post added at 12:17 PM ---------- Previous post was at 12:15 PM ----------
DIR49DNOR0N said:
I will try this unless twrp is cooked on release. Where did you get the OTA zips from actually?
I want to, extract boot.img, save it, patch boot.img, boot it, use some apps that require root and remove some packages, uninstall magisk, power down, use normal image, relock bootloader. Does this work how i expect it to work ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-nord/how-to/oneplus-nord-repo-oxygen-os-builds-t4138085
DIR49DNOR0N said:
I will try this unless twrp is cooked on release. Where did you get the OTA zips from actually?
I want to, extract boot.img, save it, patch boot.img, boot it, use some apps that require root and remove some packages, uninstall magisk, power down, use normal image, relock bootloader. Does this work how i expect it to work ?
Click to expand...
Click to collapse
No, keep the bootloader unlocked if your phone is modified, else it can cause some issues.
Btw when you lock/unlock the bootloader, data will be wiped. apps will be reinstated again so that's useless
The guide worked perfectly and I'm up and running with Root!
One thing I have noticed is that the Google Play store is no longer Play Protect Certified.
I've tried registering my device with Google using this XDA guide but I haven't found any change to the Play Store certification.
I should probably wait for a while to see if the registration takes some time. I also couldn't use the adb commands that Google recommends and I had to use the Device ID app to get the Google Service Framework (GSF).
I've read in a few places that it may be because the Bootloader is unlocked and I'm wondering if I should re-lock it now that I have root. Not sure how/if that will affect my ability to keep root when future updates come out though.
Anyone have any thoughts/experience with this?
Possible TWRP without waiting?
Can anyone use this and try? Might be used as an alternate Method for Rooting via TWRP
https://forum.xda-developers.com/an...g/guide-how-to-port-twrp-to-qualcomm-t3420013