Hi,
Does anyone have a root for the Honor 6 Plus and/or way to install GAPPS?
Thanks in advance...
mikejasonsmith said:
Hi,
Does anyone have a root for the Honor 6 Plus and/or way to install GAPPS?
Thanks in advance...
Click to expand...
Click to collapse
You can look here: http://forum.xda-developers.com/android/general/huawei-honor-6-plus-root-tutorial-t2991788
Thanks but it looks like that account and link have been disabled
Use the inbuilt app center to download google play services, once installed, you can then access google play and off you go. The Chinese inbuilt app center does seem to be really good and enables you to download all Google apps and also it's app updates are ahead of Google play.
I just need to root mine now. Anyone managed it yet?
Thanks mate but it keeps saying its not supported by my device...am I downloading the wrong one?
Go to the in built app center, the blue icon, Huawei app center, Open it and the first tab should have a search page. Type in that Google play services and it should find it, if not search and then install from the link.
It installed fine on my PE-TL10 version that arrived yesterday.
Once that was installed, I could install play and the rest using the same method. No root access required to get them installed. It comes up with the accoun, new or existing page and once that's done, you can use it as normal as well as all your other Google apps.
Don't know why your having problems, this went well on mine. Just need to root it now.
I've done that but it only gives me the option to 'open' it rather than 'install' ????
Open it, it won't work without.
still can't get gmail to work. That's the on,y app that won't work.
Will have to wait for a root I guess then install GAPPS...
That should work shouldn't it?
Check out this guide to install Google apps. This exactly what I did: http://www.huaweimobileshop.com/blog/huawei-honor-6-install-google-account/
I hope it helps. I have now unlocked my boot loader but need cwm recovery for 6 plus to get root sorted as I cannot find any standalone root kit that works, so my task goes on still.
Thanks mate.
How did you get your boot loader unlocked? Will you let me know? And let me know if you find a root and GAPPS ?
Thanks
I am a bit busy today with Sunday jobs at homes but will send you all the guides I follwed and I will get the files on to a web site to download for you. The guide is around but the problem was getting the product code. All good now, so will let you have it all later today.
Sathelp said:
Check out this guide to install Google apps. This exactly what I did: http://www.huaweimobileshop.com/blog/huawei-honor-6-install-google-account/
I hope it helps. I have now unlocked my boot loader but need cwm recovery for 6 plus to get root sorted as I cannot find any standalone root kit that works, so my task goes on still.
Click to expand...
Click to collapse
Sathelp said:
I am a bit busy today with Sunday jobs at homes but will send you all the guides I follwed and I will get the files on to a web site to download for you. The guide is around but the problem was getting the product code. All good now, so will let you have it all later today.
Click to expand...
Click to collapse
Thanks mate :good:
I still do not have root as I need a valid EMUI 3.0 CWM or TWRP recovery but I do have an extracted EMUI stock recovery that I have been using while testing various supposedly Honor 6 Plus Recoveries!
So here is the Bootloader unlocking instructions taken and modified from here
Introduction
Bootloader unlocking works by using the fastboot command line utility and executing a specific command containing a ‘bootloader unlock code,’ which is unique to each specific device and must be generated based on the IMEI and serial number of the device. Once the bootloader is ‘unlocked,’ this gives us permission to flash (or overwrite) sections of the phone memory with code of our own choosing – allowing us to install recoveries, gain root access, and utilise custom ROMs (once they are available).
Huawei provide a website to generate bootloader unlock codes , but this unfortunately does not list the entirety of the Honor 6 Plus, so we have to get creative. Fortunately, there are resources available us to generate a ‘fake’ product ID for an existing model number which can trick the unlock code generator into providing us a valid code for our Honor 6 Plus, and therefore allow us to execute the bootloader unlock successfully.
Generating a Product ID
If you visit the bootloader unlock generator page (this is a page setup by Huawei themselves), you can see there are a number of required fields; namely product model, product serial number, product IMEI and product ID.
However, after selecting smartphone, you will notice that there are no Honor 6 Plus devices present in the model list – and therefore we need to generate our own product ID. To do this, download the Huawei_Product_ID_Generator (Windows only, I’m afraid) file and extract it to your machine. Please note that we did not develop this application and have no knowledge of any malware it may contain – please use your best judgement and always use antivirus when installing unknown software.
Once you have extracted the application, execute it by double clicking the .exe file. When the window appears, select Y300-0000 from the model list, and enter your devices IMEI in the field below the selection box. You can find your device IMEI on the box your Honor 6 Plus came in, or alternatively navigate on the device to Settings > About Phone > Status and your IMEI will be listed.
{
"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"
}
Selecting Y3000-000
After selecting Y300-0000 and entering your IMEI code, your newly generated product code will be visible in the lower box. Save this number or write it down somewhere safe, and move on to the next step, getting hold of the bootloader unlock code itself.
Getting a Bootloader Unlock Code
At this point, we need to go back to the official Huawei bootloader unlock code generator page. Now that we have a product ID, we are able to generate an unlock code quite easily. First of all, select Smartphone for device type, then select Y300-0000 (about halfway down) for the product model. The remaining fields should be fairly straightforward – fill in your IMEI and serial number (either from the box or on your phone in Settings > About Phone > Status) into the appropriate boxes.
For the product ID, enter the one you generated with the generator earlier – not the one of your actual device. Once all fields have been filled, complete the CAPTCHA at the bottom of the field and click ‘submit.’
If everything has been completed successfully, you will now be in possession of your unlock code. Congratulations!
Driver Installation
Now that you have an unlock code, we can move forward with unlocking the bootloader. First of all, you’ll need to download the package containing required drivers and utilities for the phone, extract it to your computer, and navigate to the resultant directory.
You will likely need to install drivers for your device, so do this now – extract the Drivers file and navigation within, then execute DriverSetup.exe and allow it to complete. When this installation has completed, restart your computer as advised by the driver installation wizard. The requisite software for the bootloader unlock and recovery installation should now be prepared and active on your computer.
Bootloader Unlock
You will need to get and down and dirty with a bit of command line magic in order to actually unlock your bootloader. The simplest way to open a command prompt in the correct place is to navigate into the adb_tools folder or somewhere you have them, and open a command line window and cd ****** to this folder. Your should have fastboot etc in this folder if correct.
The first thing to check is whether or not our device has been detected. Within the command prompt in the tools directory, enter the following command and then hit enter:
adb devices
If you don’t see any output after this, you probably need to install drivers. Install the included driver package, restart your machine, then try again. On the other hand, if you see a device listed, then everything has been detected correctly and you will be able to unlock your bootloader straight away. You then need to put your Mate 7 device into bootloader mode. The easiest way to do this is to enter the following command into the command prompt and hit enter:
adb reboot bootloader
This will get you into the bootloader mode of your device. You may have to press ‘okay’ on a phone screen popup to allow the adb command to connect properly. Once in the bootloader, we can perform the bootloader unlock. To do this, simply enter the following command and hit the enter key – replacing YOURUNLOCKCODE with the code we generated earlier:
fastboot oem unlock YOURUNLOCKCODE
If everything works correctly, you will be given a message in the command prompt, and the phone bootloader screen will now stated ‘PHONE Unlocked.’ Congratulations! You now have an unlocked bootloader.
I have added the adb set up file to get your tools folder and also a copy of the generator file
Can those with the 6 plus tell me what the pros and cons of this phone? is the camera really good or not?
Sathelp said:
I still do not have root as I need a valid EMUI 3.0 CWM or TWRP recovery but I do have an extracted EMUI stock recovery that I have been using while testing various supposedly Honor 6 Plus Recoveries!
So here is the Bootloader unlocking instructions taken and modified from here
Introduction
Bootloader unlocking works by using the fastboot command line utility and executing a specific command containing a ‘bootloader unlock code,’ which is unique to each specific device and must be generated based on the IMEI and serial number of the device. Once the bootloader is ‘unlocked,’ this gives us permission to flash (or overwrite) sections of the phone memory with code of our own choosing – allowing us to install recoveries, gain root access, and utilise custom ROMs (once they are available).
Huawei provide a website to generate bootloader unlock codes , but this unfortunately does not list the entirety of the Honor 6 Plus, so we have to get creative. Fortunately, there are resources available us to generate a ‘fake’ product ID for an existing model number which can trick the unlock code generator into providing us a valid code for our Honor 6 Plus, and therefore allow us to execute the bootloader unlock successfully.
Generating a Product ID
If you visit the bootloader unlock generator page (this is a page setup by Huawei themselves), you can see there are a number of required fields; namely product model, product serial number, product IMEI and product ID.
However, after selecting smartphone, you will notice that there are no Honor 6 Plus devices present in the model list – and therefore we need to generate our own product ID. To do this, download the Huawei_Product_ID_Generator (Windows only, I’m afraid) file and extract it to your machine. Please note that we did not develop this application and have no knowledge of any malware it may contain – please use your best judgement and always use antivirus when installing unknown software.
Once you have extracted the application, execute it by double clicking the .exe file. When the window appears, select Y300-0000 from the model list, and enter your devices IMEI in the field below the selection box. You can find your device IMEI on the box your Honor 6 Plus came in, or alternatively navigate on the device to Settings > About Phone > Status and your IMEI will be listed.
Selecting Y3000-000
After selecting Y300-0000 and entering your IMEI code, your newly generated product code will be visible in the lower box. Save this number or write it down somewhere safe, and move on to the next step, getting hold of the bootloader unlock code itself.
Getting a Bootloader Unlock Code
At this point, we need to go back to the official Huawei bootloader unlock code generator page. Now that we have a product ID, we are able to generate an unlock code quite easily. First of all, select Smartphone for device type, then select Y300-0000 (about halfway down) for the product model. The remaining fields should be fairly straightforward – fill in your IMEI and serial number (either from the box or on your phone in Settings > About Phone > Status) into the appropriate boxes.
For the product ID, enter the one you generated with the generator earlier – not the one of your actual device. Once all fields have been filled, complete the CAPTCHA at the bottom of the field and click ‘submit.’
If everything has been completed successfully, you will now be in possession of your unlock code. Congratulations!
Driver Installation
Now that you have an unlock code, we can move forward with unlocking the bootloader. First of all, you’ll need to download the package containing required drivers and utilities for the phone, extract it to your computer, and navigate to the resultant directory.
You will likely need to install drivers for your device, so do this now – extract the Drivers file and navigation within, then execute DriverSetup.exe and allow it to complete. When this installation has completed, restart your computer as advised by the driver installation wizard. The requisite software for the bootloader unlock and recovery installation should now be prepared and active on your computer.
Bootloader Unlock
You will need to get and down and dirty with a bit of command line magic in order to actually unlock your bootloader. The simplest way to open a command prompt in the correct place is to navigate into the adb_tools folder or somewhere you have them, and open a command line window and cd ****** to this folder. Your should have fastboot etc in this folder if correct.
The first thing to check is whether or not our device has been detected. Within the command prompt in the tools directory, enter the following command and then hit enter:
adb devices
If you don’t see any output after this, you probably need to install drivers. Install the included driver package, restart your machine, then try again. On the other hand, if you see a device listed, then everything has been detected correctly and you will be able to unlock your bootloader straight away. You then need to put your Mate 7 device into bootloader mode. The easiest way to do this is to enter the following command into the command prompt and hit enter:
adb reboot bootloader
This will get you into the bootloader mode of your device. You may have to press ‘okay’ on a phone screen popup to allow the adb command to connect properly. Once in the bootloader, we can perform the bootloader unlock. To do this, simply enter the following command and hit the enter key – replacing YOURUNLOCKCODE with the code we generated earlier:
fastboot oem unlock YOURUNLOCKCODE
If everything works correctly, you will be given a message in the command prompt, and the phone bootloader screen will now stated ‘PHONE Unlocked.’ Congratulations! You now have an unlocked bootloader.
I have added the adb set up file to get your tools folder and also a copy of the generator file
Click to expand...
Click to collapse
Cheers mate.
This is awesome - absolutely awesome.
I will give it a go and report back . Ive managed to load Nova on it and get it running so things are moving ahead slowly. But this will help.
Cheers
Mike
I have found a that now roots the 6Plus. Mine is now rooted and original recovery back on.
I used the Honor 6 Multi-tool from this thread in the XDA pages.
I am not sure if the bootloader unlock works or not, so if you can get it unlocked as above or try this tool.
The tool is for the 6 not especially the 6Plus but using the install CWM recovery works, then I used the boot to recovery and then selected root by sidelobe (install zip/install zip by sidelobe menus). SU was installed permissions set. As I wanted to ensure that the correct stock recovery was used (my EMUI3.0 extracted before) I selected to reboot the phone by exiting the (recovery) and it then asked me if I wanted to fix root, I selected yes, rebooted the phone. Checked that root was working and then went back to bootloader and fastboot flash recovery (my recovery) to get it back to stock.
I am now a happy Man, bootloader unlocked and rooted. Hopefully you will be able to as well mikejasonsmith.
Sathelp said:
I have found a that now roots the 6Plus. Mine is now rooted and original recovery back on.
I used the Honor 6 Multi-tool from this thread in the XDA pages.
I am not sure if the bootloader unlock works or not, so if you can get it unlocked as above or try this tool.
The tool is for the 6 not especially the 6Plus but using the install CWM recovery works, then I used the boot to recovery and then selected root by sidelobe (install zip/install zip by sidelobe menus). SU was installed permissions set. As I wanted to ensure that the correct stock recovery was used (my EMUI3.0 extracted before) I selected to reboot the phone by exiting the (recovery) and it then asked me if I wanted to fix root, I selected yes, rebooted the phone. Checked that root was working and then went back to bootloader and fastboot flash recovery (my recovery) to get it back to stock.
I am now a happy Man, bootloader unlocked and rooted. Hopefully you will be able to as well mikejasonsmith.
Click to expand...
Click to collapse
This is cool mate - thanks so much!
Going to try and do it over the next day or so. Really appreciate your hard work on this.
What ROM are you going to stick on it?
I am using the ROM that came with the phone from Pompmall and it updated a small update once turned on. The current ROM is marked as CUSTCHNC00D112SP05, Build Number: PE-TL10V100R001CHNC00B112SP05.
I take it that you are going to put GAPPS on while you have CWM recovery fitted? Don't forget that unless you flash back the stock recovery, you wont be able to use their update files and have to get a zip file of the ROM. But now we have a working CWM Recovery, it can be flashed easy by using fastboot if needed.
The owner of that multitool has said that he will add the 6Plus to it, so that will be good. I have provided him with my stock EMUI3.0 recovery to add in to the process.
Sathelp said:
I am using the ROM that came with the phone from Pompmall and it updated a small update once turned on. The current ROM is marked as CUSTCHNC00D112SP05, Build Number: PE-TL10V100R001CHNC00B112SP05.
I take it that you are going to put GAPPS on while you have CWM recovery fitted? Don't forget that unless you flash back the stock recovery, you wont be able to use their update files and have to get a zip file of the ROM. But now we have a working CWM Recovery, it can be flashed easy by using fastboot if needed.
The owner of that multitool has said that he will add the 6Plus to it, so that will be good. I have provided him with my stock EMUI3.0 recovery to add in to the process.
Click to expand...
Click to collapse
Ive already got GAPPS on it via Nova but this now opens up more possibilities.
What are you going to be doing to yours???? Must admit Im liking this phone so far - battery life is awesome.
Related
For those who already have a QUALCOMM BOOTLOADER
1. Enter OSBL MODE.
WARNING: IF YOU GET FORMAT DISK MESSAGE IN WINDOWS - ALWAYS CLICK CANCEL.
2.Switch off the phone.
3. Press Volume UP and Power Key and wait for the short buzz abd release both butons. (To boot into NAND disk mode).
WARNING: IF YOU GET FORMAT DISK MESSAGE IN WINDOWS - ALWAYS CLICK CANCEL.
3. Run the oneClick DOWNLOADER (comes with the latest firmwares)
4. Choose the ROM. FLASH.
5. Once complete take the battery out; Re-Assemble, Switch on
OTHERS follow the following POST
NOTE: I do not take credit for any of the work by respective developers. I'm a lame user and that's my best quality. I would prefer things to be simple enough, if not I find one.
So for those who have been looking around for a Nokia Lumia 710 FULL UNLOCK and are jumbled with programs X, Y and Z and files A, B, C; everything seems right when your are following some steps and then, at some point of time, unfortunately for some it stuck and sucks. I've tried many things and the following is the one I like the most and find the easiest. Best of all, you don't have to worry about the DLOAD.
NOTE: One small mistake and you might brick the phone, so be careful.. I or the developers nor the forum is anyway responsible for your loss. But if you be careful, you won't have to worry.
READ the entire post and understand BEFORE you TRY
Step 1:
Download the required softwares.
( All required files are hyper-linked below )
i)> NSS PRO 0.48 or NSS PRO 0.51
ii)> QUALCOMM BOOTLOADER for Lumia 710
iii)> Depending on your system configuration, Windows USB Drivers either x86 or x64
iv)> Any one of your desired Custom ROM :
A. Rataplan Final, based on Nokia firmware 1600.3037.8862.13170 ,
B. Lumiatrix^8 V 5.1 based on 7.10.8835.35
C. Reality ROM based on 7.10.8858.136
D. fabiode34's Custom ROM
NOTE: You need only one ROM. so pick any. I've been using RATAPLAN's ROM.
Do Not Forget to thanks the Developer, whose ROM you are using.
Step 2:
Once you have all the files with you do prepare the program files for the FLASH.
a. Install the USB driver as per your system.
b. Extract the bootloader to a folder. You will get the following two files
RM803_12w07_prod_generic_nokia_osbl.esco
RM803_11w48_prod_raw_nokia_osbl.binc. Extract the NSS to a folder
Now copy the two bootloader files to the following folder within NSS folder
loaders\special\wp7Extract the Custom ROM to a folder. You should get a .nb file. If not, try another ROM
IF you did the steps as stated, you are all ready.
Now before proceeding, make sure you have Enough battery back up on your phone and for the PC/Laptop (in case there is a powercut and you don't have enough backup, you won't have to but another paperweight.).
Step 3:
Flash your phone:
Did I Miss Something. No. You don't have to check for DLOAD. Not for Lumia 710. I already made it clear.
a. Connect your phone to PC. You don't have to do any button pressing or have to go to recovery mode.
b. Launch the NssPro.exe from the NSS folder in admin mode. Grant all the permissions the application asks for, if any.
When the allpication window is launched, make sure you know what is where. Use the snap for reference
{
"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"
}
Make sure, you select the USB port from port selection and alllow the application to detect the phone.
Once the application detects the phone it will show "Nokia USB connectivity.
Change the application mode to FLASHING
On the right side select WP7 Tools. You will get the Bootloader tools..
c. Now refer the following screenshot and proceed.
i. In Advance Connectivity section select NORMAL Mode and then WP7 Qualcomm, if it does not detect automatically.
ii. In Bootloader tool select the OS file and locate your CUSTOM ROM to it.
Once you proceed further there is no going back. So be careful. Make sure that you have all the files in place as stated earlier and also you have installed all the drivers. Use CUSTOM ROMs for Lumia 710 only (Either your own or reliable developers). When Windows asks for format, ignore it. Do not respond to any pop up from any application other than the NSS. You should not leave the PC unattended for whatsoever reason. NEVER choose YES for FORMAT, simply close it.
iii. Hit the install. When asks for confirmation, select yes.
Wait for a while. Do Not Panic. Phone will go blank and will start in NAND DISK mode in a while. The connectivity mode will switch to NAND DISK DRIVE mode.. If Format option pop-ups, Select NO.
iv. Check the advance connectivity mode, and set as stated earlier to NORMAL and WP7 Qualcomm.
v. Hit the Write OS in the Bootloader tools. Wait for a while (usually 5 to 10 mins) Be patient. NSS will ask to restart the phone.
You cannot restart the phone. Take the battery out. Then again put it back and boot the phone.Close the NSS tool and any other pop-ups.
Your phone is now unlocked and loaded with a custom ROM
Step 4.
REACTIVATION of phone.
Your phone is ready to be used if you have used a correct ROM.
Sometimes, if you install a locked ROM or on on a Locked phone, your phone will be locked for LIVE ID usage. you'll have to ACTIVATE the phone to use LIVE login. You can still use other features though. Do not worry, as activation is as simple as chatting with a buddy. Just CLICK HERE and use chat and ask the customer care executive for activation code. They will need few of the details of the phone, and they will give the code. use this code to unlock LIVE usage.
Once again, I take no credit for the work. I'm just sharing the info in a clean manner. I use the method and works for me. Your Phone Your responsibility.
All links were alive when posting. If any link is dead, PM me. Response will not be prompt, but I'll make sure I respond to your requests.
Error flashing
Hi, good guide thanks!
When I press write OS in the final stage i get this mesage:
Checking file selection...Done.
Looking for NAND disk...Not found.
Are you sure you have development Qcom loader ?
Click to expand...
Click to collapse
What should i do?
Lumia 710 RM-803 flashing Lumiatrix
Whenever i plug in my phone it comes up as a qualcomm device, and the first part of your instructions went perfectly
Check prerequisite files.
Hi,
If the first part went right, you should have no problem for the second part. First part is the critical part here.
(Even I Had faced the same problem many times. Downloading and replacing the files should do it.)
Here are the possibilities:
If the first part went right; the phone will go to service mode; the USB should disconnect and reconnect automatically. You'll get the FORMAT disk message and you should select NO or simply close it.
If you accidentally click on YES, your phone is a gonner
If everything is correct, NOKIA USB CONNECTIVITY should change to NAND DISK. And you can p[roceed with second part.
NOTE1. If first part is not pass, the second part cannot be initiated.
2. If first part is pass, the second part MUST be completed.
What if I just want to unlock the phone and not to install the custom rom...thus it will work i mean it'll unlock my phone using the qualcomm loader files only.
Hmmmm... Just the UNLOCK....
mobileplazza said:
What if I just want to unlock the phone and not to install the custom rom...thus it will work i mean it'll unlock my phone using the qualcomm loader files only.
Click to expand...
Click to collapse
Well, That is completely upto you. But consider the following scenarios, b'cause I have no idea what your UNLOCK mode means.
Case 1: If phone software is not hacked, you cannot install YOUR own softwares without having to purchase from the MarketPlace. You'll have to install applications only through MarketPlace.
Case 2: If you think, installing the Qualcomm bootloader will unlock your phone, then you are mistaking; it will only enable your phone to install any firmware on it (simply saying it will be a dumb rock until you install a firmware).
Case 3: If your phone is carrier locked, and you want to use it on any other network: Simply insert the new SIM card and follow the LAST LINK IN THE ORIGINAL POST. But use it only after a fresh ROM installation or Phone Hard Reset.
psquicker said:
Well, That is completely upto you. But consider the following scenarios, b'cause I have no idea what your UNLOCK mode means.
Case 1: If phone software is not hacked, you cannot install YOUR own softwares without having to purchase from the MarketPlace. You'll have to install applications only through MarketPlace.
Case 2: If you think, installing the Qualcomm bootloader will unlock your phone, then you are mistaking; it will only enable your phone to install any firmware on it (simply saying it will be a dumb rock until you install a firmware).
Case 3: If your phone is carrier locked, and you want to use it on any other network: Simply insert the new SIM card and follow the LAST LINK IN THE ORIGINAL POST. But use it only after a fresh ROM installation or Phone Hard Reset.
Click to expand...
Click to collapse
thnx for ur reply i understand it..and mine is case 3 i just want to unlock the carrier locked phone i have two phones with me but i dont have clear tutorial to unlock it if you know please guide me thnx in adv.
thanks for the tutorial
Howver for some reason NSS Pro doesnt detect my phone, (RUN as Administrator)
Phone Detect
Jigneshg said:
thanks for the tutorial
Howver for some reason NSS Pro doesnt detect my phone, (RUN as Administrator)
Click to expand...
Click to collapse
Hi,
Have you downloaded and installed all the files as needed. (All the required files are hyperlinked within the description).
It works for me on Win7, both 32 and 64 bit.
Make sure you have installed the proper USB driver for your system (from Step 1 / sub step iii). This is mainly the reason for phone detection.
Check if it helps.
psquicker said:
Hi,
Have you downloaded and installed all the files as needed. (All the required files are hyperlinked within the description).
It works for me on Win7, both 32 and 64 bit.
Make sure you have installed the proper USB driver for your system (from Step 1 / sub step iii). This is mainly the reason for phone detection.
Check if it helps.
Click to expand...
Click to collapse
Ya managed to realise afterwards, I have flashed Rataplan's 6.0 ROM
Carrier Unlock
mobileplazza said:
thnx for ur reply i understand it..and mine is case 3 i just want to unlock the carrier locked phone i have two phones with me but i dont have clear tutorial to unlock it if you know please guide me thnx in adv.
Click to expand...
Click to collapse
Installing the custom rom should debrand the phone.... Nothing more to be done.
Else use NSS PRO 0.51 in original post. There is a section to unlock the SIM.
Everything went well until...
hi bro
thanks for the post
very good
everything went well until i came to reboot my phone
it does not start up now
what shall i do?
i done all the steps and they matched yours perectly. all the messages were the same.
the nss said to reboot the phone
i unplugged the usb and took battery out and rebooted it.
nothing, it doesnt start up
help
Thanks... If i install custom rom... will i be able to install xap file manually?? let me know plz.....
Phenominal post!
I've successfully unlocked my Lumia 710 and flashed Rataplan V6.0 to my phone! Everything's working great, except I need to figure out my APN settings to get MMS working again. :L
The only suggestion I'd make for your Layman's guide is to make sure to let everyone know that they will lose anything that isn't backed up! Pictures, SMS, some contacts that aren't on your SIM etc. It may be common knowledge to some, but I didn't know. It's no big deal for me though.
Anyways, thanks a bunch! Great post!
Successfully installed custom rom
I have installed custom roms perfectly by using this method.Goto the post of IonutZuker on 14th May 2013, 06:40 PM
http://forum.xda-developers.com/showthread.php?t=2267334&page=2
Earlier, i was facing problem after completing 1st step.NSS Pro was not recognizing my phone completly.NSS Pro was showing the problem of NAND disk not found.
Press Volume + and power button
shams1924 said:
hi bro
thanks for the post
very good
everything went well until i came to reboot my phone
it does not start up now
what shall i do?
i done all the steps and they matched yours perectly. all the messages were the same.
the nss said to reboot the phone
i unplugged the usb and took battery out and rebooted it.
nothing, it doesnt start up
help
Click to expand...
Click to collapse
Press Volume + and power button at same time then try to repeat the process.
---------- Post added at 09:54 PM ---------- Previous post was at 09:42 PM ----------
saddambuet said:
Thanks... If i install custom rom... will i be able to install xap file manually?? let me know plz.....
Click to expand...
Click to collapse
Yeah, use WPAppPatcher.
And who is pressed FORMAT DISK when connected device what should i do? The phone isn't turn on ever since
Sorry but i try the other descreption to install custom rom, but i mistake in this
I am about to flash my girl 710, is there any info of the phone I sould check before flash?, or this will work anyhow?. Thanks for any advice you can give me!
PD: DONE, half your guide and half other that I found here in xda. Thanks Both.
Installing Custom ROMs help!!!!
So i downloaded rainbow mod 2.1 and the downloader.exe. I also have fully unlocked my Lumia 710 with Nokia Care suite 5.0. The porblem is, when i launch downloader.exe and click download ROM, it says "Lumia Disks not founded!" and tells me to put my phone in osbl bode, which i did. HELP ME PLZ!!!
Hi at all,
I have a Lumia 710 with DLOAD bootloader version 7.33.0 and OS version 7.10.8862.144.
Can I install a Custom ROM (Rataplan V7.0) with this method?
Guys, I have a nokia Lumia 510 with a DLOAD bootloader. Any Ideas how I can get a custom Firmware on to it? And will the process of changing the bootloader as specified above work for my phone? Please work on a custom ROM for it!! :crying:
Basic device info
Model Number : PB1009
Android Version : 7.0
Kernel Version: 4.4.22
Build Number : PB1009_20170912
Hey so i need literally any way to root this tablet, ive been able to unlock the bootloader (easiest bootloader on the planet) but havent been able to find a compatable twrp.
i just need a custom recovery that will work or p much any root ideas, i would consider a full custom firmware as well.
i considered compiling a twrp but i dont know how i would get the source files for it...
Kenvarus said:
Basic device info
Model Number : PB1009
Android Version : 7.0
Kernel Version: 4.4.22
Build Number : PB1009_20170912
Hey so i need literally any way to root this tablet, ive been able to unlock the bootloader (easiest bootloader on the planet) but havent been able to find a compatable twrp.
i just need a custom recovery that will work or p much any root ideas, i would consider a full custom firmware as well.
i considered compiling a twrp but i dont know how i would get the source files for it...
Click to expand...
Click to collapse
how did you unlock bootloader and did you ever figure out how to root it? going through same thing now.
Kind of an old thread and old device now, but I own one myself (branded Packard Bell) and just figured this all out, so here goes:
Root
This one is really easy now thanks to a MediaTek flaw. Just go to https://github.com/JunioJsv/mtk-easy-su, download the latest release, install the APK on the device, and run it by opening the app and pressing the button in the lower-right corner (still works on this since the latest security patch level AFAIK is from 2017). Note that this gives root temporarily, so you will need to run it again after reboot if you want root again.
Bootloader Unlock
When Kenvarus said "easiest bootloader on the planet", I took a guess at the method and it worked:
Back up any important data on your tablet, as this will factory reset it.
Install ADB and Fastboot on your computer if they are not installed, including drivers. For Fastboot (as that can be tricky sometimes), it "just worked" for me and I think Windows used an Amazon driver I had installed for my KF2. YMMV.
If you haven't already, enable Development Settings by going to Settings->About tablet and tapping the build number 7 times.
Go to Settings->Developer options (switch them on if they're off) and enable the "OEM unlocking" toggle.
In the same menu, enable "USB debugging" if it is not enabled already.
Connect the tablet to your computer, confirming the authorization prompt that pops up if it wasn't connected before. Check whether the connection is good with the "adb devices" command if needed.
Run the command "adb reboot bootloader", this gave me a blank screen.
Use the "fastboot devices" command to make sure the Fastboot connection works.
Run the command "fastboot oem unlock".
Press Volume Up when the text-mode confirmation screen pops up on the tablet.
Once the unlock procedure is complete, reset the tablet. You should see text on your bootscreen saying "Orange State" and a factory reset on the first reboot if it worked.
WARNING: I highly recommend charging your battery to be at least 10-20% filled before doing this. I stupidly did this at 1% battery thinking "it's plugged in anyway" and had quite the time rebooting after unlocking the bootloader (I thought it was bricked for a good hour or so, only after walking away for 20 minutes to eat dinner did I see that the battery was now at 20% and I could boot the tablet).
After unlocking the bootloader and temp-rooting it with the above app, I was able to use Magisk to patch the boot image (using dd to shuttle the files to and from /dev/block/mmcblk0p10, use "strings saved_boot_partition_name|head -n1" and check for "ANDROID!" to make sure it's the right partition) and I now have persistent root after all these years (note that Direct Install in Magisk doesn't work here). I'd definitely be interested in a custom recovery and/or ROMs for this device, but I'm not holding my breath (I'd take a crack at it if I knew better how to do it, but I have near-zero experience with ROM development and so far have only recompiled existing ROMs for a few phones).
hello please advice! How do I unlock the bootloader at this point and do root with magisk? please describe step by step instructions or link to instructions. sorry because this thread must be here, but I didn't find anything current. I think it's better to get advice than to do wrong and then look for how to restore your phone from a broken state.
my build: Andoid 8.0.0 Emui 8.0.0 PRA-LX1 8.0.0.401 (C432)
Phone locked, FRP unlocked
Thank you very much
niki.rsb said:
hello please advice! How do I unlock the bootloader at this point and do root with magisk? please describe step by step instructions or link to instructions. sorry because this thread must be here, but I didn't find anything current. I think it's better to get advice than to do wrong and then look for how to restore your phone from a broken state.
my build: Andoid 8.0.0 Emui 8.0.0 PRA-LX1 8.0.0.401 (C432)
Phone locked, FRP unlocked
Thank you very much
Click to expand...
Click to collapse
Huawei doesn't unlock bootloader's any more.
You'll have to find a pay service that supports your model.
Sent from my HD1907 using Tapatalk
@niki.rsb
In order to root device's Android unlocking device's boot-loader isn't a pre-requisite.
Rooting a phone's Android means giving user and/or applications administrative rights, will say unrestricted access to Android's system files.
jwoegerbauer said:
@niki.rsb
In order to root device's Android unlocking device's boot-loader isn't a pre-requisite.
Rooting a phone's Android means giving user and/or applications administrative rights, will say unrestricted access to Android's system files.
Click to expand...
Click to collapse
Wrong... you can't flash a patched boot.img without an unlocked bootloader
the only way to root the device is with a Magisk_patched boot.img
clsA said:
Wrong... you can't flash a patched boot.img without an unlocked bootloader
the only way to root the device is with a Magisk_patched boot.img
Click to expand...
Click to collapse
You should carefully read instead of replying nonsense.
I don't understand English well. I don't understand it now. I think everyone writes something different. i need root via magisk to be able to connect google pay with credit card. so the bootloader only goes through the paid service? and then proceed to root?
niki.rsb said:
I don't understand English well. I don't understand it now. I think everyone writes something different. i need root via magisk to be able to connect google pay with credit card. so the bootloader only goes through the paid service? and then proceed to root?
Click to expand...
Click to collapse
You can only unlock bootloader with a paid service.
Once the bootloader is unlocked you can use magisk and patch and then flash a rooted boot.img
Instructions for making the patched boot.img are here > https://topjohnwu.github.io/Magisk/install.html
you get the correct stock boot.img from a full firmware update.zip for your version
Bootloader Unlock Instructions found here > https://techelucid.com/unlock-bootloader-huawei/
Pre-Requisites for unlocking bootloader
Enable USB Debugging
Install USB Drivers for Huawei 98 Lite:
USB Debugging:
Goto Settings> About Phone Tap 7 Times on Build Number
Then In Settings>Developer Options and enable USB Debugging
Tick The “Oem Unlock” Checkbox
Download the following things for Huawei Device
Get and Install USB Drivers on your computer from here
Download DC Huawei Bootloader Codes from here.
Get DC Unlocker client app from here.
Buy Dc Unlocker Credit With Android App
Download and install “DC Huawei Bootloader Codes Android app“ from the link given above in downloads section.
Open the downloaded apk file and install it on your device.
Click on DC Unlocker Account.
Type your email id and complete the payment processes.
After successful payment; save the user password. You will need this while using DC unlocker pc app.
Get Huawei Bootloader Unlock Code With Dc Unlocker
Extract the downloaded DC Unlocker client app zip file.
Double click or Run dc-unlocker2client.exe.
Move to the server tab and log in. use the user password which you got in DC Huawei Bootloader Codes Android app.
Connect your device to pc and enable Manufacturer Mode (You can easily enable manufacturer mode by Typing *#*#2846579#*#* in the dial pad. After that click on Background settings > USB port settings > Manufacturer Mode).
Select the Manufacturer type “Huawei Phones” Model “Auto Detect”. After that click on the search button.
Click on Unlocking Tab. After that choose Read Bootloader Code.
Wait for some time to Unlock code to arrive. When it does, copy the data and save it in a notepad file.
Last step to Unlock Bootloader
Turn off your device.
Put it in Fastboot mode by pressing Volume down + Power button at the same time.
Connect your device to a PC with the USB cable.
Enter The Unlock Code In Code In Command prompt Window and press Enter.
Wait for a few seconds and your device will restart.
You can now go ahead and customize your device by installing TWRP or then flash SuperSu Magisk to root it. So you have succeeded to unlock your Huawei bootloader. .
Click to expand...
Click to collapse
with the bootloader unlocked you don't actually need TWRP
you can fastboot flash the patch_boot.img
just use the command
fastboot flash boot patched_boot.img
thank you for the instructions. But unfortunately the bootloader is still locked. I followed the instructions. it wrote me the bootloader number. But when I opened the command line and wrote the number, then nothing did. where should i open the dashboard? classic C: \ Windows \ system32>?
I will also provide a transcript of the dc unlocker
Check account status
User: bl21816
Credits left: 4
Activated features:
Software debugger
=============================================== ================
Before detection Huawei Android phones, enable 'Manufacture' mode:
in dial pad type * # * # 2846579 # * # * for Qualcomm and Kirin based models, or * # * # 14789632 # * # * for MTK, then select
'ProjectMenu',
'Background settings',
'USB ports settings',
'Manufacture mode'.
Step by step guide for other Huawei phone unlock:
https://www.dc-unlocker.com/huawei_phones_detect_unlock_tutorials
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM7
=============================================== ================
Check account status
User: bl21816
Credits left: 4
Activated features:
Software debugger
Unlock Auto detect (recommended) cost 4 Cr
Service text tutorial: https://www.dc-unlocker.com/huawei-android-hisilicon-unlock-guide
=============================================== ================
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM7
=============================================== ================
Reading bootloader code ...
Bootloader code: 9x9x2x2x2x8x5x3x
=============================================== ================
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone: PRA-LX1
Model: Huawei phone in fastboot mode
IMEI: 866386030063396
Serial NR. : 9DC7N17728006152
Firmware: PRA-LX1 8.0.0.401 (C432
IMEI1: 866386030090407
FB LockState: LOCKED
USER LockState: LOCKED
locked
Battery state: 4068mv
=============================================== ================
Check account status
User: bl21816
Credits left: 0
Activated features:
Software debugger
Unlock Huawei phone in fastboot mode (866386030063396) cost 15 cr
Server message:
Check prices at: https://www.dc-unlocker.com/buy/user_prices
Insufficient credits!
=============================================== ================
niki.rsb said:
i need root via magisk to be able to connect google pay with credit card. so the bootloader only goes through the paid service? and then proceed to root?
Click to expand...
Click to collapse
Right after you root Android OS, Google Pay will stop working. How to bypass this in detail is explained here.
Again:
It's a misconception if people like you think the bootloader of a device has to be unlocked in order to root device's Android OS. These people just don't know what role the bootloader has, just don't know what rooting Android OS means.
niki.rsb said:
I will also provide a transcript of the dc unlocker
Check account status
User: bl21816
Credits left: 4
Activated features:
Software debugger
=============================================== ================
Before detection Huawei Android phones, enable 'Manufacture' mode:
in dial pad type * # * # 2846579 # * # * for Qualcomm and Kirin based models, or * # * # 14789632 # * # * for MTK, then select
'ProjectMenu',
'Background settings',
'USB ports settings',
'Manufacture mode'.
Step by step guide for other Huawei phone unlock:
https://www.dc-unlocker.com/huawei_phones_detect_unlock_tutorials
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM7
=============================================== ================
Check account status
User: bl21816
Credits left: 4
Activated features:
Software debugger
Unlock Auto detect (recommended) cost 4 Cr
Service text tutorial: https://www.dc-unlocker.com/huawei-android-hisilicon-unlock-guide
=============================================== ================
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM7
=============================================== ================
Reading bootloader code ...
Bootloader code: 9x9x2x2x2x8x5x3x
=============================================== ================
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone: PRA-LX1
Model: Huawei phone in fastboot mode
IMEI: 866386030063396
Serial NR. : 9DC7N17728006152
Firmware: PRA-LX1 8.0.0.401 (C432
IMEI1: 866386030090407
FB LockState: LOCKED
USER LockState: LOCKED
locked
Battery state: 4068mv
=============================================== ================
Check account status
User: bl21816
Credits left: 0
Activated features:
Software debugger
Unlock Huawei phone in fastboot mode (866386030063396) cost 15 cr
Server message:
Check prices at: https://www.dc-unlocker.com/buy/user_prices
Insufficient credits!
=============================================== ================
Click to expand...
Click to collapse
Simply getting the code isn't enough you have to flash it see below and see the tutorial for dc unlocker here > https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
Using your Unlock Code:
1. Turn off your phone, Boot your device into Fastboot mode with Vol down and power button.
2. CD to where you downloaded ADB/Fastboot Tools
Run these commands when inside ADB tools directory
a) fastboot devices. (your device should bee listed. If not reinstall drivers/reboot)
b) fastboot oem get-bootinfo (just to confirm everything is detected correctly
c) fastboot oem unlock 9x9x2x2x2x8x5x3x
3. Acknowledge the prompt on your phone. Device will be WIPED!
4. Once the wipe finishes it will take several minutes for phone to boot up. Do not panic. Once you See Huawei logo you are OK!
Click to expand...
Click to collapse
Note: I just read that whole thread (below) and the tutorial is out of date.
it's much easier to root now using the magisk patched_boot.img
see my post earlier on how it's done
instructions for unlocking and rooting your phone here > https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
He even has a free method to get the bootloader unlock code (Seems you already have yours above)
Other useful links I found during my search
HiSuite 5.0.2.300 - https://androidmtk.com/download-huawei-hisuite
Multi-Tool for Huawei - https://pro-teammt.ru/multi-tool-for-huawei-honor/
Firmware Database > https://pro-teammt.ru/en/online-firmware-database-ru/
Huawei update extractor > https://firmwarecare.com/huawei-update-extractor-v0-9-9-5
How to extract Huawei firmware and its UPDATE.APP > https://nerdschalk.com/extract-huawei-firmware-update-app/
jwoegerbauer said:
Right after you root Android OS, Google Pay will stop working. How to bypass this in detail is explained here.
Again:
It's a misconception if people like you think the bootloader of a device has to be unlocked in order to root device's Android OS. These people just don't know what role the bootloader has, just don't know what rooting Android OS means.
Click to expand...
Click to collapse
Yes you're right. I don't know exactly how it works and I don't understand it. But that's why I turned here and ask for advice on how to proceed. If I had knowledge, I wouldn't bother anyone to help me. I don't think this is anything new.
clsA said:
Simply getting the code isn't enough you have to flash it see below and see the tutorial for dc unlocker here > https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
Note: I just read that whole thread (below) and the tutorial is out of date.
it's much easier to root now using the magisk patched_boot.img
see my post earlier on how it's done
instructions for unlocking and rooting your phone here > https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
He even has a free method to get the bootloader unlock code (Seems you already have yours above)
Other useful links I found during my search
HiSuite 5.0.2.300 - https://androidmtk.com/download-huawei-hisuite
Multi-Tool for Huawei - https://pro-teammt.ru/multi-tool-for-huawei-honor/
Firmware Database > https://pro-teammt.ru/en/online-firmware-database-ru/
Huawei update extractor > https://firmwarecare.com/huawei-update-extractor-v0-9-9-5
How to extract Huawei firmware and its UPDATE.APP > https://nerdschalk.com/extract-huawei-firmware-update-app/
Click to expand...
Click to collapse
Yes there are a lot of versions and procedures for how to root them on the internet. Some don't work, others worked, but currently they don't either. Or there may be new better practices. For a person who does not have much knowledge, it is very difficult to choose the right one. If what you are saying is new and mainly functional, I will look and try to proceed
niki.rsb said:
Yes there are a lot of versions and procedures for how to root them on the internet. Some don't work, others worked, but currently they don't either. Or there may be new better practices. For a person who does not have much knowledge, it is very difficult to choose the right one. If what you are saying is new and mainly functional, I will look and try to proceed
Click to expand...
Click to collapse
first just get the bootloader unlocked
I'll show you how to extract and create a rooted boot.img
clsA said:
first just get the bootloader unlocked
I'll show you how to extract and create a rooted boot.img
Click to expand...
Click to collapse
I have the bootloader unlocked. Is it now necessary to install twrp for magisk? and how do you please proceed?
niki.rsb said:
I have the bootloader unlocked. Is it now necessary to install twrp for magisk? and how do you please proceed?
Click to expand...
Click to collapse
Excellent !!
We need your firmware version to get the correct ramdisk.img
look in settings / about phone for the firmware version or just post a screen shot of that screen
this is your file (I got it from your first post) > PRA-LX1 8.0.0.401 (C432) FullOTA-MF > https://pro-teammt.ru/en/online-fir...mware_model=PRA-LX1+8.0.0.401&firmware_page=0
download the update.zip (I'm downloading it also)
Next download the Huawei update extractor > https://firmwarecare.com/huawei-update-extractor-v0-9-9-5
I posted the guide here for using the extraction tool > https://nerdschalk.com/extract-huawei-firmware-update-app/
and then follow this guide to root the ramdisk.img
Huawei
Huawei devices using Kirin processors have a different partitioning method from most common devices. Magisk is usually installed to the boot partition of the device, however Huawei devices do not have this partition. Depending on what EMUI version your device is running, the instructions will be slightly different.
Obtain Stock Images
Huawei does not release official factory images, however most firmware zips can be downloaded from the Huawei Firmware Database. To extract images from UPDATE.APP in the zip, you have to use Huawei Update Extractor (Windows only!)
EMUI 8
For EMUI 8 devices, your device has a partition named ramdisk, which is where Magisk is going to be installed.
If you plan to use custom recoveries, simply follow the instructions for custom recovery and you’re all set.
If you plan not to use custom recoveries, you will have to extract RAMDISK.img from your firmware. Follow the instructions for boot image patching above, but use the RAMDISK.img file instead of a boot image.
To flash the patched image to your device, here is the fastboot command:
fastboot flash ramdisk /path/to/magisk_patched.img
Be aware you are flashing to ramdisk, not boot!
Click to expand...
Click to collapse
Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don’t want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock RAMDISK.img, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet. The following instructions will guide you through the process after you have the copy of boot/recovery image.
Copy the RAMDISK.img to your device
Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock RAMDISK.img file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched image from your device to your PC. If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched RAMDISK.img to your device and reboot. For most devices, here is the fastboot command:
fastboot flash ramdisk magisk_patched.img
fastboot flash boot /path/to/magisk_patched.img or
fastboot flash recovery /path/to/magisk_patched.img if you are patching a recovery image
Click to expand...
Click to collapse
now use fastboot reboot
at this point your phone should be rooted
I uploaded the patched ramdisk.img here if you have trouble > https://www.androidfilehost.com/?fid=8889791610682890848
the unpatched RAMDISK.IMG is also their > https://www.androidfilehost.com/?w=files&flid=314978
You also have TWRP 3.11 available for your phone > https://androidfilehost.com/?fid=1899786940962602140
it's ease to flash TWRP and then root your phone with a Magisk.zip in TWRP
it's also nice if you like to flash roms or make backups of your system and data
clsA said:
this is your file (I got it from your first post) > PRA-LX1 8.0.0.401 (C432) FullOTA-MF > https://pro-teammt.ru/en/online-fir...mware_model=PRA-LX1+8.0.0.401&firmware_page=0
download the update.zip (I'm downloading it also)
Click to expand...
Click to collapse
I did not find a download file or a link where I can download, so I download here
https://androidhost.ru/1iXE is it ok?
yes build number is PRA-LX1 8.0.0.401 (C432) Emui 8, Android 8
And what is the difference between when I run through that ramdisk.img or when I make a flash twrp and install magisk.zip??
niki.rsb said:
I did not find a download file or a link where I can download, so I download here
https://androidhost.ru/1iXE is it ok?
yes build number is PRA-LX1 8.0.0.401 (C432) Emui 8, Android 8
And what is the difference between when I run through that ramdisk.img or when I make a flash twrp and install magisk.zip??
Click to expand...
Click to collapse
I posted the patched ramdisk.img for you
all you need to do is copy it to your adb/fastboot folder and reboot your phone to fastboot mode and flash it
fastboot flash ramdisk magisk_patched.img
their is no difference in the end result, either method will work to Root your phone
clsA said:
I posted the patched ramdisk.img for you
all you need to do is copy it to your adb/fastboot folder and reboot your phone to fastboot mode and flash it
fastboot flash ramdisk magisk_patched.img
their is no difference in the end result, either method will work to Root your phone
Click to expand...
Click to collapse
I did exactly and just what you wrote. the flash completed without error, but I don't know what the result should have been. I don't even have root, magisk, I didn't know the change.
niki.rsb said:
I did exactly and just what you wrote. the flash completed without error, but I don't know what the result should have been. I don't even have root, magisk, I didn't know the change.
Click to expand...
Click to collapse
Install magisk manager if it's not in your app drawer
CHANGELOG:
Guide v1.0 - Warn that Lineage cannot be flashed on A12 firmware.
Guide v1.1 - Update guide for flashing Lineage after complete conversion and updates so phone is fully converted first.
There are THREE firmware versions for the N200.
DE2118 - Carrier infected phones for T-Mobile and MetroPCS in US.
DE2117 - Retail US OEM firmware that is 100% compatible with US carriers and fully supports 5G, 4G, 3G (gone), 2G, VoLTE, and VoWIFI.
This guide is intended to remove the carrier virusware that the carrier uses to wipe/spy on the user as well as branding bloat like the bootup/shutdown graphic/sound.
DE2117AA - International version of the phone. This has a different modem/firmware, supports 2 sim cards, and is NOT compatible with US N200 hardware.
WARNINGS:
1. Do NOT flash Intl. DE2117AA firmware or use msmtool for DE2117AA on any US phone or you will no longer make/receive voice or text calls until you flash back to US firmware with Fastboot Enhance!
2. You must NOT stop the guide after you flash DE2117 onto the first slot as the phone will NOT be fully converted until it takes the OTA update to Android 12 and one more to C_17.
If you go to the about screen before the Android 12 OTA update, you will still see DE2118.
3. A You should take ALL OTA updates to Android 12 C_17 and then follow the root guide for Dummies if you want to test drive the latest and very stable current OEM firmware.
B Flash back to DE2117 Android 11 final with my downgrade guide to go back to the final Android 11 DE2117 US before you install current N200 Lineage.
Lineage requires you to be on Android 11 or it will soft brick when you flash Lineage boot.img.
4. Finally, I have had enough people use my N200 guides that they are proven to work very well, but I take no responsibility if you abort the flashing process or skip parts of the guide and manage to boot loop/brick your phone!
However, I will work with you to get you going again. This phone cannot be fully bricked with the Qualcomm chipset and EDL recovery mode. You will create a full backup of your phone in the guide, so you can restore it 100% even if you walk away and your cat manages to fully wipe the entire firmware area of the phone with Fastboot Enhance.
PREREQUISITES: (see other guides)
1. You must have your boot loader unlocked.
2. Request and receive your unlock token from OP website to unlock boot loader.
(This takes exactly one week from requesting on Oneplus Website until OnePlus delivers the unlock token.)
If your phone is still sim subsidy locked and you cannot move the "OEM unlocking in dev options to on as it's greyed out, follow steps (20-24) to bypass this and turn on OEM unlocking so you can get unlocking code without being sim unlocked.
3. Install latest Android Platform Tools installed on PC. Currently v33.0.3
Old versions platform tools will cause fastboot commands to FAIL!!
4. Fastboot Enhance tool
Download and unzip folder into working directory.
This tool is Windows only and requires .net framework 4.5 (can be ran in VM with enough free ram for experienced linux users) This tool also needs a good amount of ram as someone with a old Windows 7 machine with very limited ram had the program hang when unpacking the firmware. They then switched to a newer machine resolved the issue.
5. Backup your phone data as this guide will wipe your phone in the process.
I recommend you put a MicroSD card in your N200 and select MicroSD card as backup location in Swift/APP Manager as all data on MicroSD will survive a phone wipe/reset.
A. The most simple backup tool is Swift Backup with a rooted phone to save all your app, data, phonebook, texts, and wifi passwords for easy restore after you are converted, upgraded and re-rooted.
B. For power users I highly recommend using App Manager to back up your apps.
The App Manager instructions are worth reading like a book as this tool is very complex and powerful.
This tool will backup APK source files/splits, internal/ext data/obb and media/cache, app permissions, battery savings,data usage, Magis khide status, SSAID, rules set up in App Manager. It will also import backups fromOAndBackup, Titanium and Swift (3.0-3.2) and keep multiple version backups of same app.
It's also an Interceptor, Manifest viewer, Scanner (API key from virus total), Enhanced Package installer with version upgrade/downgrade information and library add/remove info on install, Usage, Log viewer with colors/filters, App explore and much more.
-----------------------------------------------------------------------------------------
Begin GUIDE
-----------------------------------------------------------------------------------------
1. Place your phones unlock key into Platform Tools directory.
(You can download it again by logging into OnePlus site and going to this page.)
2. Download Tmobile/MetroPCS OnePlus MSMtool for V11.0.1.7 and unzip to working folder of your choice.
3A. Download FINAL Android V11 Update Image .
If installing Lineage,You MUST flash Lineage boot.ini from Android 11 or you WILL go into a soft boot loop from Android 12!
3B. If you are going to re-flash your phone that is already flashed to DE2117 and on A12 due to a bad update (in a soft boot loop) or installed other A12 rom and need to flash back, Download Full US OEM A12 C_16 Update Image and keep as .zip file and place in working folder instead.
(See Downgrade Guide if you are already running US OEM A12 and want to go back to A11 to install Lineage.)
4. Go to working folder you unzipped msmtool and open folder "dre8t_10_O.07_211014_repack"
5. A. Execute program as Administrator "MsmDownloadTool V4.0.exe" if your running Windows 10 or 11.
B. Execute program as administrator "MsmDownloadTool V4.0_Win7.exe" if your running Windows 7.
6. At login prompt, change user type to:
"User Type: Others" & Hit Next button.
7. At main page of MsmDownload Tool hit "F8"
A new window will pop-up that is called Firehose Readback:
(Ignore my crazy Windows theme colors - Yours will look different)
{
"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"
}
8. Locate Password box at bottom of pop-up and enter lowercase password: oneplus
9. Make sure the box is still active window and hit <cntrl-a> and every box in the list will then become checked.
10. hit OK to close box.
11. Click new "Read Back" button.
13. Place phone in special EDL recovery mode:
A. Since ADB is working, it is easier to simply open your Android Platform tools folder in Explorer and type cmd in location box to open dos prompt and type:
C:\platform-tools>adb reboot edl
B. You can turn phone off and then hold both volume buttons down and power on to force phone into EDL mode if phone is not working properly.
NOTE: When phone is in EDL mode the screen on the phone will be BLANK.
This is NORMAL.
14. As soon as the command is entered switch back to MSMtool window and watch it make a FULL backup of your phone including all firmware (slot a/b) and phone identifying information areas. When this is complete your phone will reboot.
15. Go to root of system drive (Default C:\) in explorer and sort files by date (Double Click on the Date Modified) and move all the new files just created ending in .bin, .img, .elf, and .mbn to a folder and name it to identify this exact phone if you have more than one N200 and store in a safe place like a USB flash drive. You can zip the folder first to save space.
See: Firehose backup files.txt attached for full list.
Do NOT share this backup with anyone online as they can clone your phones IMEI/SN with this PRIVATE backup data!
16. Re-run msmtool again. It will remember user type option: others. Click Next.
17. This time at main screen simply press start. and place phone in EDL mode as in step 13.
18. Watch the tool flash V11.0.1.7 firmware and most importantly the older fastbootd that is proven to perform the conversion firmware flash.
(Phone will reboot wiped/locked and in out of box condition.)
19. Do phone setup offline without entering wifi and as soon as you are out of setup turn off data to prevent phone from starting to download firmware update from OTA.
20. Goto Settings -> About Device -> Version -> build number and click until developer again.
21. Goto Settings -> System Settings -> Developer Options and turn on USB debugging and then exit settings.
22. Go back to dos box and send command to remove software that prevents OEM Unlock from being turned on:
C:\platform-tools>adb shell pm uninstall --user 0 com.qualcomm.qti.uim
23. On Phone: Go to Settings -> System Settings -> Developer Options
Turn ON "OEM Unlocking"
24. Go back to dos box and type:
C:\platform-tools>adb reboot fastboot
25. Send your unlock code to phone again.
(Assuming the file is called unlock_code.bin)
C:\platform-tools>fastboot flash cust-unlock unlock_code.bin
26. Unlock Bootloader:
C:\platform-tools>fastboot oem unlock
27. Follow on screen directions and phone will unlock bootloader, erase data and enter new phone setup again.
Do steps 19-21 again (developer/adb debugging on) and step 24 (Reboot to fastboot)
Now visually verify your phone is in Fastboot mode and unlocked.
28. Go to working folder in explorer and open folder "Fastboot_EnhanceV1.3.0" and execute "FastbootEnhance.exe"
29. On Fastboot Visualization tab, Double click on your device that will be shown.
30. Now you have two tabs, "Basic Properties" and Partitions.
31. Click on Partitions tab and scroll to bottom of the partitions list and verify that there are none that end in "_cow"
(They are creeated when you do OTA upgrades. They are left over and need to be deleted if present otherwise there may not be enough room to write new image.)
32. Highlight EVERY file ending in "_cow" and click the erase button.
They are always at the bottom of the list.
Repeat until there are NO files ending in "_cow"
33. Click the button bottom left corner called "Reboot to Fastbootd"
34. Your phone willl now reboot into special fastbootd mode.
35. Click English on phone to see this. Do NOT click any other options on phone.
36. Tick the box on right Show Logs to watch it's progress. A log box will pop up. Drag it over to the side to watch.
37. Tick the box Ignore Unknown Partitions
(fastbootd will NOT flash over newer modem firmware with older, if flashing older firmware and required for flash to still work)
38A. Click Flash Payload Bin box and select file "DE2117-A11-Final-OnePlusN200Oxygen_10.O.11_OTA_011_all_2203021426_downgrade_66cde69fe1e342db.zip" from working directory.
38B. For Android 12 USS OEM Reflash-Restore, Select file "(US_RETAIL_A12_C_16_FULL_ROM)DE2117_11.C.15_0150_202205192325.zip"
39. Click Flash Payload bin button.
It will unpack all the partitions from the .zip file first.
It will then delete old partitions and re-create partition with new required size and flash each .bin file of firmware one at a time automatically.
40. WAIT.....Watch the log output window and DO NOTHING until complete.
A. Fastboot Enhance will unpack all the partitions from the .zip file first.
B. It will then delete old partitions and re-create partition with new required size and flash each .bin file of firmware one at a time automatically.
41. When process is finished click "Reboot to recovery" button.
42. on phone, tap English.
43. on phone, tap "wipe data" and follow prompts to wipe and restart.
You will now boot up on US OEM DE2117 Android 11 Final.
WARNING: Do NOT stop the guide at this point, as your phone is not fully converted yet!
If you go to about info you will still see DE2118 and the boot area and other slot is still on carrier firmware! (Even if you are going to install Lineage, you must continue OTA upgrades to Android 12 C_17 and then downgrade to Android 11 afterwards)
44. Perform system setup with wifi and go to settings -> about device and perform system update and you will update to A12 (C_16) and proceed to second partial OTA update to latest OTA (C_17) before following the root guide for dummies
WELL DONE MY GOOD SIR!
Thanks for the thorough write-up for this dummy! So once this procedure is completed I can assume that everything that works for the DE2117 (like LineageOS) will be OK for a DE2118?
My fastboot enhance keeps stopping once i select the payload.bin to flash
I have all the correct files but it seems like windows keeps stopping the program from continuing further...
So say you run through this guide, everything goes correctly and you end up with a DE2117. Is it for all intents and purposes a DE2117 or would you still run the DE2118 MSM Tool should you run into a problem and need to reset?
Maatt_OG said:
My fastboot enhance keeps stopping once i select the payload.bin to flash
I have all the correct files but it seems like windows keeps stopping the program from continuing further...
Click to expand...
Click to collapse
Are you seeing anything in the log window?
What is the error message Windows is giving you, and how is it stopping the program?
It sounds like you have Windows issues.
Are you running this in a VM or under very low memory conditions?
You may want to refresh your Windows installation.
Link575 said:
So say you run through this guide, everything goes correctly and you end up with a DE2117. Is it for all intents and purposes a DE2117 or would you still run the DE2118 MSM Tool should you run into a problem and need to reset?
Click to expand...
Click to collapse
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone is for all practical reason a US OEM. Your IMEI is still in the T-mobile/MetroPCS range so the OP will not give you credits for registering a new OEM phone at Red Cable Club and will say that IMEI is invalid.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
scanman0 said:
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone s for alll practical reason a US OEM. Your IMEI is still in the Tmobile range so OP site login will not give you register credit for registering new phone at store.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
Click to expand...
Click to collapse
it says extracting files in the log but i have eeven waited and ignored the windows pop up error saying , Program has stopped working, we will let you know if theres a solution, but it doesnt proceed any further.
AND... DO NOT USE MSM TOOL AFTER CONVERTING. modem and core-nhlos and a few other partitions are a bit different along with the hardware versions and all and youll bootloop.
scanman0 said:
Are you seeing anything in the log window?
What is the error message Windows is giving you, and how is it stopping the program?
It sounds like you have Windows issues.
Are you running this in a VM or under very low memory conditions?
You may want to refresh your Windows installation.
Click to expand...
Click to collapse
as for memory, i am running pretty low tbh....
scanman0 said:
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone s for alll practical reason a US OEM. Your IMEI is still in the Tmobile range so OP site login will not give you register credit for registering new phone at store.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
Click to expand...
Click to collapse
I see thanks for that. So one more follow up, I'm not even sure if you would know this but I installed Lineage 19 on my DE2118 and after that About phone states its a 2117. I'm assuming this is just because that's what this ROM was made for and it's not actually converting to a DE2117. I did MSM after Lineage and had no problems going back to stock DE2118.
scanman0 said:
13. Place phone in special EDL recovery mode:
Click to expand...
Click to collapse
This dummy had never seen EDL mode before and because my MSMDownload tool for Win7 seemed to require running as administrator the tool did not automatically connect so all I saw was a black screen in Step 14.
We shall not talk about how long nor how many different reboot combinations were required for me to understand that I needed to run the tool as administrator and that the black screen was normal. Really funny.
Even funnier was that I never did find the backup files after the Download was complete. Not on C:, not on D:, none found with the Explorer search function. Somehow I made them vanish even after your careful description.
katooom said:
Even funnier was that I never did find the backup files after the Download was complete.
Click to expand...
Click to collapse
And the only reasonable explanation for this is that among my many confused attempts to make things work this was the time that I did not actually do the backup, just pressed the start button. I would hate to think that I made such a ridiculous blunder but what else could it be. Oh my .....
Maatt_OG said:
as for memory, i am running pretty low tbh....
Click to expand...
Click to collapse
You need to have enough memory free for the program to unpack the .zip file in ram. If Windows is crashing the process with "program is not responding" then your pc (or is it a vm?) does not have enough memory.
Link575 said:
I see thanks for that. So one more follow up, I'm not even sure if you would know this but I installed Lineage 19 on my DE2118 and after that About phone states its a 2117. I'm assuming this is just because that's what this ROM was made for and it's not actually converting to a DE2117. I did MSM after Lineage and had no problems going back to stock DE2118.
Click to expand...
Click to collapse
Lineage has one build that is compatible with both versions and reports that either is DE2117.
katooom said:
This dummy had never seen EDL mode before and because my MSMDownload tool for Win7 seemed to require running as administrator the tool did not automatically connect so all I saw was a black screen in Step 14.
We shall not talk about how long nor how many different reboot combinations were required for me to understand that I needed to run the tool as administrator and that the black screen was normal. Really funny.
Even funnier was that I never did find the backup files after the Download was complete. Not on C:, not on D:, none found with the Explorer search function. Somehow I made them vanish even after your careful description.
Click to expand...
Click to collapse
I have updated the guide to reflect that you need to run as administrator on Windows 7 and to run the windows 7 .exe file.
I have only tested under Windows 10 and Windows 11 and the program demanded administrator mode to run.
The msmtool always dumps to the root of the working system boot drive that is usually C:
I made a screen shot of the F8 windows as you must select the boxes and place the password to place the tool in the backup mode.
I never said in the guide to look at the phone when in EDL mode as the screen is black.
I have updated the guide to inform people that are not familiar with EDL mode to expect that it is blank.
This is the reason I had people go to EDL mode with the pc with adb is the fact that it is a blank screen mode and people can be confused if the phone is in EDL or off.
I cannot tell by your condescending comments if you actually did the F8 procedure correctly to place msmtool in backup mode.
There is no indicator before it starts (other than the window closing without an error) and the tool will indicate as shown in the screenshot that it is "Reading back <Partition name>" as it reads the partitions from the phone.
If you simply press start as you implied you "tried" the tool will flash the phone to default factory state and NOT do a backup.
You do realize I wrote this guide to try to help people and cannot test every possible configuration as I don't have Windows 7 anymore.
People with your poor attitude is the reason there are fewer hand holding guides present on XDA.
scanman0 said:
Lineage has one build that is compatible with both versions and reports that either is DE2117.
Click to expand...
Click to collapse
Got it, thanks.
scanman0 said:
People with your poor attitude is the reason there are fewer hand holding guides present on XDA.
Click to expand...
Click to collapse
Whoa, I have to apologize for making you think that I was in any way critical or dissatisfied! I was merely making fun of myself for messing up the process in spite of how well you explained it. I actually hoped that you would be amused by my errors and the silly reasons that I made them. It is deeply upsetting to me to have offended someone who puts so much effort into helping. I can only apologize again for expressing myself so poorly.
@scanman0 Dumb question probably, but after completing this, would it be possible to downgrade to Android 11 OEM?
rcartaz09 said:
@scanman0 Dumb question probably, but after completing this, would it be possible to downgrade to Android 11 OEM?
Click to expand...
Click to collapse
Nothing dumb about this question!
I have updated the guide to INCLUDE converting to last Android 11 US OEM Firmware
And put warning to only install Lineage with Android 11 firmware.
I also posted a separate downgrade guide so people will not miss this fact if they already upgraded to Android 12 and want to install Lineage:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
After completing this, would it be possible
scanman0 said:
Nothing dumb about this question!
I have updated the guide to INCLUDE converting to last Android 11 US OEM Firmware
And put warning to only install Lineage with Android 11 firmware.
I also posted a separate downgrade guide so people will not miss this fact if they already upgraded to Android 12 and want to install Lineage:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
Click to expand...
Click to collapse
You are awesome! Thank you!
Hello everyone!
I recently had the pleasure(pain) of flashing my Ace Pro and I wanted to share the steps I took in doing so. This post will act a as guide/discussion area regarding flashing the Ace Pro(Chinese Release) into the OnePlus 10T 5G(Global Release).
Henceforth, I will refer to the OnePlus Ace Pro as Ace Pro, and the OnePlus 10T 5G as 10T.
A little bit of backstory:
I currently live in China and have no way of purchasing a device overseas and having it shipped in. Instead, I did a little bit of research and decided to purchase an Ace Pro and have a go at flashing it myself. As far as I can tell, the Ace Pro and 10T are identical hardware-wise and flashing between the 2 different market varients can be done with a little bit of effort and headache.
Before we go any further, let me link some useful articles and resources I've found along the way in order to successfully flash your own Ace Pro:
Fastboot Enhance, a powerful tool that will allow you to flash your device with your desired OS
ADB Platform Tools, a tool used to unlock your bootloader
OnePlus USB Drivers, an USB driver used to allow for your phone to communicate with your computer seamlessly(Even though not officially supported, the Ace Pro and 10T work with the 1.0 Release of the USB Drivers)
2415_11_C.22 Update, a stable release of Oxygen 13 that I personally recommend to be flashed on your 10T
Daxiaamu Tools and ROMs, a Chinese enthusiast that has developed his own tools to aid in unlocking, flashing and relocking of devices.
Disclaimer: I am not responsible for any damage that you may inflict upon your own device, proceed with caution and at your own risk! Back up all data before proceeding!!
We begin our journey by first unlocking the Ace Pro's bootloader, unlocking the bootloader is an essential step in flashing your device.
To do this, we need to first enable Developer Tools by going into: Settings > About Device > Version > And tapping the Build Number box until you have become a developer.
After this, navigate to Developer Options. If you cannot find this option, I recommend using the search bar at the top of the settings menu to find this option. Once you're in this menu, enable OEM Unlocking and USB Debugging. This allows for our computer to communicate with our Ace Pro.
Here I recommend installing your Oneplus USB Driver. This will allow your phone to communicate with your PC for the upcoming step.
After installing the drivers, plug your phone into your computer using either the USB cable that came in the box, or a reliable cable that you know will carry data.
Press on Transfer Files/Android Auto when prompted.
Allow for debugging on your device after plugging it into your computer with the prompt that shows up.
Once you are sure that both OEM Unlocking and USB debugging have been enabled, run your ADB Platform Tools by performing the following steps:
Unzip your ADB Platform Tools and have it placed in a memorable place(preferably the desktop)
{
"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"
}
Holding Shift + Right Click in an empty space brings up this option menu. Click on Open PowerShell window here.
This brings up a Windows Powershell terminal that allows you to enter commands that will directly affect your Ace Pro.
Run the command
Code:
adb devices
This show bring up an entry with a mess of both numbers and characters. This shows you that both your computer and ADB tool recognizes your device and you can move forward.
Now we want to put the device into the bootloader by using:
Code:
adb reboot booloader
This will now run on your device putting it into the bootloader state.
Note: DO NOT UNPLUG YOUR DEVICE IN THIS STATE
After making sure that your device is in the bootloader, run the command:
Code:
fastboot flashing unlock
You will be presented with a prompt asking you if you are sure that you want to unlock your bootloader. Using the volume rocker as a selector and the power button as a confirmation button, highlight the UNLOCK THE BOOTLOADER option using the volume rocker and confirm it by pressing the power button.
Your Ace Pro's bootloader is now unlocked.
NOTE: YOUR DEVICE WILL BE FORMATTED ONCE YOU UNLOCK THE BOOTLOADER! ALL EXISTING DATA WILL BE LOST!
Once unlocking your bootloader, your phone will enter 'Orange State' where it lets you know that your device is untrusted due to its unlocked nature. Do not be alarmed by this.
Proceed by setting your phone up as normal and repeat the earlier step where you become a developer and enable USB Debugging.
This time, OEM unlocking will be enabled by default, this is due to the nature of your device being unlocked.
We now want to put our device into fastboot mode by using ADB. In the Powershell window, type:
Code:
adb reboot fastboot
This will once again change the state of your phone and put it in fastboot mode where 3 language options are available. Do not configure your phone in this state, we will come back to it later.
Now, run Fastboot Enhance as an administrator on your PC. The window should open up and you should be able to see your device with the device name being labeled as 'fastboot'.
Double click this option and another Window should show up.
Make sure that the status of the device is as follows:
Secure Boot: Disabled
Seamless Update: Yes
Current Slot: a
In Fastbootd: Yes
System Update Status: None
Once in this state, we want to click on the partitions tab above and search for 'cow' in the search bar. Results will pop up if you have used/updated your device in ColorOS. You want to highlight these results and press delete on the right hand side. Having them remain in your device will have the possibility of bricking your device when flashing the new OxygenOS ROM.
Once done deleting, return to the Basic Properties tab and press Flash Payload.bin. This will open a browser in where you need to find the zip file containing the ROM that you want to flash.
Find your payload.bin file and open.
Your device will now begin to flash, it took me around 10 minutes before the device was done flashing.
Once flashed, go to your phone and select your language of choice. For most of us, it will be English. This option can be selected like earlier, using the volume rocker as a selector and the power button as a confirmation switch.
Select the option to format your phone once again. Enter the pass code that is present on the screen and confirm the formatting procedure.
The device should still be in Orange State since we have not relocked our bootloader, instead we will now see the OxygenOS boot animation before proceeding to set up our device.
From this point onward, your device is now flashed with OxygenOS.
If you would like to relock your bootloader, read on.
The benefits of relocking your bootloader is that you will be able to receive OxygenOS updates as normal and be able to use NFC functions such as Google Wallet.
Once again, enable developer options and make sure that both OEM Unlocking and USB Debugging is enabled.
Open the ADB Powershell window mentioned before and make sure that your device is still recognized by using the command:
Code:
adb devices
Once your device shows up, put it back into the bootloader state by using the command:
Code:
adb reboot bootloader
Your phone will now enter the bootloader state once again.
We can now relock our bootloader by using the command:
Code:
fastboot flashing lock
This will prompt you to use your volume rocker and power button one more time. Select the option LOCK THE BOOTLOADER and press the power button to confirm. Your device will now format for the last time and load you into OxygenOS 13.
Note: I personally had an issue where after flashing and relocking the bootloader, my phone decided to bootloop(device stuck at OnePlus logo and keeps on turning on and off again), I solved this by holding the volume down and power button and setting it to restart. After loading into the operating system, I updated my device by using OTA updates and installing C4515_11_C.23. This allowed for my device to install the latest update and it seemed to have fixed the bootlooping problem for me.
Another method to fix the bootlooping issue after flashing your phone if you already have the latest update installed is to enable developer options after flashing and applying the same update using the local update feature.
To do this, enable developer options first, the instructions to do that were described earlier in this guide. Transfer the .bin file by drag and dropping your .bin file to a location on the device that you are familiar with. (Placing the .bin file in the downloads folder is a foolproof method)
From there onwards, you want to go into Settings > About Device > Tap on the blue OxygenOS banner > 3 dots menu in the top right corner > Local Install > Select your .bin file you used to flash the device with earlier. Your device should then update with said .bin file and the bootlooping issue should be solved.
Credit to thegreatn_ for this discovery.
Edit: Some of you may experience that your OEM unlocking is still enabled even after flashing your device and relocking your booloader. Remember earlier when your bootloader was in an unlocked state, the OEM unlocking option would be on by default and greyed out so that you could not turn it off which may present a security risk.
Rest assured that you can turn off OEM unlocking once your device has been relocked and everything will function as intended. YOUR DEVICE SHOULD NOT BE ROOTED IF YOU INTEND TO TURN THIS OFF! ONLY DO THIS WITH THE OFFICIAL FIRMWARE INSTALLED! Not having the official firmware installed and turning off OEM unlocking can brick your device!
Credit to Adly1991 for this information.
Please let me know if there's any questions you'd like to ask. This is my first time flashing and it may seem daunting at first, but I believe with a little bit of confidence, you too will be able to successfully flash your Ace Pro.
Good luck!
I'm 8T user , but thanks for sharing your experience and the information.
Abdo Ismail said:
I'm 8T user , but thanks for sharing your experience and the information.
Click to expand...
Click to collapse
It was really hard for me to find a place where I could get all the information I needed about flashing my phone as a noob. If this post helps even just a single person I'd be over the moon. Thanks for the feedback!
Thanks so much. Followed the instructions and worked perfectly!
breadsnack said:
Hello everyone!
I recently had the pleasure(pain) of flashing my Ace Pro and I wanted to share the steps I took in doing so. This post will act a as guide/discussion area regarding flashing the Ace Pro(Chinese Release) into the OnePlus 10T 5G(Global Release).
Henceforth, I will refer to the OnePlus Ace Pro as Ace Pro, and the OnePlus 10T 5G as 10T.
A little bit of backstory:
I currently live in China and have no way of purchasing a device overseas and having it shipped in. Instead, I did a little bit of research and decided to purchase an Ace Pro and have a go at flashing it myself. As far as I can tell, the Ace Pro and 10T are identical hardware-wise and flashing between the 2 different market varients can be done with a little bit of effort and headache.
Before we go any further, let me link some useful articles and resources I've found along the way in order to successfully flash your own Ace Pro:
Fastboot Enhance, a powerful tool that will allow you to flash your device with your desired OS
ADB Platform Tools, a tool used to unlock your bootloader
OnePlus USB Drivers, an USB driver used to allow for your phone to communicate with your computer seamlessly(Even though not officially supported, the Ace Pro and 10T work with the 1.0 Release of the USB Drivers)
2415_11_C.22 Update, a stable release of Oxygen 13 that I personally recommend to be flashed on your 10T
Daxiaamu Tools and ROMs, a Chinese enthusiast that has developed his own tools to aid in unlocking, flashing and relocking of devices.
Disclaimer: I am not responsible for any damage that you may inflict upon your own device, proceed with caution and at your own risk! Back up all data before proceeding!!
We begin our journey by first unlocking the Ace Pro's bootloader, unlocking the bootloader is an essential step in flashing your device.
To do this, we need to first enable Developer Tools by going into: Settings > About Device > Version > And tapping the Build Number box until you have become a developer.
After this, navigate to Developer Options. If you cannot find this option, I recommend using the search bar at the top of the settings menu to find this option. Once you're in this menu, enable OEM Unlocking and USB Debugging. This allows for our computer to communicate with our Ace Pro.
Here I recommend installing your Oneplus USB Driver. This will allow your phone to communicate with your PC for the upcoming step.
After installing the drivers, plug your phone into your computer using either the USB cable that came in the box, or a reliable cable that you know will carry data.
Press on Transfer Files/Android Auto when prompted.
Allow for debugging on your device after plugging it into your computer with the prompt that shows up.
Once you are sure that both OEM Unlocking and USB debugging have been enabled, run your ADB Platform Tools by performing the following steps:
Unzip your ADB Platform Tools and have it placed in a memorable place(preferably the desktop)
View attachment 5844957
Holding Shift + Right Click in an empty space brings up this option menu. Click on Open PowerShell window here.
This brings up a Windows Powershell terminal that allows you to enter commands that will directly affect your Ace Pro.
Run the command
Code:
adb devices
This show bring up an entry with a mess of both numbers and characters. This shows you that both your computer and ADB tool recognizes your device and you can move forward.
Now we want to put the device into the bootloader by using:
Code:
adb reboot booloader
This will now run on your device putting it into the bootloader state.
Note: DO NOT UNPLUG YOUR DEVICE IN THIS STATE
After making sure that your device is in the bootloader, run the command:
Code:
fastboot flashing unlock
You will be presented with a prompt asking you if you are sure that you want to unlock your bootloader. Using the volume rocker as a selector and the power button as a confirmation button, highlight the UNLOCK THE BOOTLOADER option using the volume rocker and confirm it by pressing the power button.
Your Ace Pro's bootloader is now unlocked.
NOTE: YOUR DEVICE WILL BE FORMATTED ONCE YOU UNLOCK THE BOOTLOADER! ALL EXISTING DATA WILL BE LOST!
Once unlocking your bootloader, your phone will enter 'Orange State' where it lets you know that your device is untrusted due to its unlocked nature. Do not be alarmed by this.
Proceed by setting your phone up as normal and repeat the earlier step where you become a developer and enable USB Debugging.
This time, OEM unlocking will be enabled by default, this is due to the nature of your device being unlocked.
We now want to put our device into fastboot mode by using ADB. In the Powershell window, type:
Code:
adb reboot fastboot
This will once again change the state of your phone and put it in fastboot mode where 3 language options are available. Do not configure your phone in this state, we will come back to it later.
Now, run Fastboot Enhance as an administrator on your PC. The window should open up and you should be able to see your device with the device name being labeled as 'fastboot'.
Double click this option and another Window should show up.
Make sure that the status of the device is as follows:
Secure Boot: Disabled
Seamless Update: Yes
Current Slot: a
In Fastbootd: Yes
System Update Status: None
Once in this state, we want to click on the partitions tab above and search for 'cow' in the search bar. Results will pop up if you have used/updated your device in ColorOS. You want to highlight these results and press delete on the right hand side. Having them remain in your device will have the possibility of bricking your device when flashing the new OxygenOS ROM.
Once done deleting, return to the Basic Properties tab and press Flash Payload.bin. This will open a browser in where you need to find the zip file containing the ROM that you want to flash.
Find your payload.bin file and open.
Your device will now begin to flash, it took me around 10 minutes before the device was done flashing.
Once flashed, go to your phone and select your language of choice. For most of us, it will be English. This option can be selected like earlier, using the volume rocker as a selector and the power button as a confirmation switch.
Select the option to format your phone once again. Enter the pass code that is present on the screen and confirm the formatting procedure.
The device should still be in Orange State since we have not relocked our bootloader, instead we will now see the OxygenOS boot animation before proceeding to set up our device.
From this point onward, your device is now flashed with OxygenOS.
If you would like to relock your bootloader, read on.
The benefits of relocking your bootloader is that you will be able to receive OxygenOS updates as normal and be able to use NFC functions such as Google Wallet.
مرة أخرى ، قم بتمكين خيارات المطور وتأكد من تمكين كل من إلغاء تأمين OEM وتصحيح أخطاء USB.
افتح نافذة ADB Powershell المذكورة من قبل وتأكد من أنه لا يزال يتم التعرف على جهازك باستخدام الأمر:
Code:
أجهزة adb [/ CODE]
بمجرد ظهور جهازك ، أعده إلى حالة أداة تحميل التشغيل باستخدام الأمر:
[كود] adb reboot bootloader [/ CODE]
سيدخل هاتفك الآن في حالة أداة تحميل التشغيل مرة أخرى.
يمكننا الآن إعادة توصيل محمل الإقلاع الخاص بنا باستخدام الأمر:
[كود] قفل وميض fastboot [/ CODE]
سيطالبك هذا باستخدام زر التحكم في الصوت وزر الطاقة مرة أخرى. حدد الخيار LOCK THE BOOTLOADER واضغط على زر الطاقة للتأكيد. سيتم الآن تنسيق جهازك لآخر مرة وتحميلك إلى OxygenOS 13.
ملاحظة: لقد واجهت شخصيًا مشكلة حيث بعد وميض أداة تحميل التشغيل ، قرر هاتفي تشغيل bootloop (الجهاز عالق على شعار OnePlus ويستمر في التشغيل وإيقاف التشغيل مرة أخرى) ، لقد قمت بحل هذه المشكلة عن طريق الضغط على زر خفض الصوت وزر الطاقة وتعيينه لإعادة التشغيل. بعد التحميل في نظام التشغيل ، قمت بتحديث جهازي باستخدام تحديثات OTA وتثبيت C4515_11_C.23. سمح ذلك لجهازي بتثبيت آخر تحديث ويبدو أنه قد أصلح مشكلة bootlooping بالنسبة لي.
يُرجى إعلامي إذا كان هناك أي أسئلة تود طرحها. هذه هي المرة الأولى التي تومض فيها وقد يبدو الأمر شاقًا في البداية ، لكنني أعتقد بقليل من الثقة ، أنك أيضًا ستكون قادرًا على وميض Ace Pro بنجاح.
حظ سعيد!
[/QUOTE]
أ Do you provide phone costum recovery Oneplus 10T
Click to expand...
Click to collapse
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
thk202 said:
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
View attachment 5856125
Click to expand...
Click to collapse
Hey there, I'm not 100% sure on how to solve this issue but I'll try my best.
First of all, please ensure that your phone is plugged into your computer at all times.
Make sure that your cable supports data transfer and try other cables and see if this problem persists.
The fact that ADB is recognizing your device tells me that your cable is probably not to blame.
Make sure that your phone is on beforehand and that USB debugging and OEM Unlocking are both enabled in the developer settings.
You have to also make sure to select allow on your phone when it asks whether the connected computer is allowed to debug your phone. This is important since it allows your computer to run commands on your phone itself.
Does your phone go into the fastboot screen when you run the adb reboot bootloader command?
Let me know so I can narrow your problems down further and solve the issue!
@thk202 I'm not a vendor of any type. This was just my personal experiences. Can you describe what's gone wrong?
thank you, i finally did it following your steps .. and i think recommendation of 2415 version solved my problem and also instantly got C.26 update through OTA
since i tried 2413 before and alwayes got modem issue.
Adly1991 said:
thank you, i finally did it following your steps .. and i think recommendation of 2415 version solved my problem and also instantly got C.26 update through OTA
since i tried 2413 before and alwayes got modem issue.
Click to expand...
Click to collapse
I remember reading somewhere that 2413 gets updates quicker than 2415 for some reason. But I for one was used to the slow update schedule from Samsung for years so it never affected me. 2415 C22 was a stable OxygenOS 13 release that allowed for OTA to C26 to fix any sort booting issues after relocking your bootloader. I remember relocking my bootloader and having it go into a constant bootloop/soft brick after the C22 flash but after OTA to C26, the bootlooping fixed itself and everything was stable again.
breadsnack said:
I remember reading somewhere that 2413 gets updates quicker than 2415 for some reason. But I for one was used to the slow update schedule from Samsung for years so it never affected me. 2415 C22 was a stable OxygenOS 13 release that allowed for OTA to C26 to fix any sort booting issues after relocking your bootloader. I remember relocking my bootloader and having it go into a constant bootloop/soft brick after the C22 flash but after OTA to C26, the bootlooping fixed itself and everything was stable again.
Click to expand...
Click to collapse
shall i disable OEM option in developer option after relock .. already locked the device but i am afraid to disable OEM option since a read somewhere that it bricked someone device ..
Adly1991 said:
shall i disable OEM option in developer option after relock .. already locked the device but i am afraid to disable OEM option since a read somewhere that it bricked someone device ..
Click to expand...
Click to collapse
Erm I've actually got no clue, I know for a fact that if your bootloader is unlocked, OEM unlocking is on by default and greyed out so you cannot turn it off while the bootloader is in it's unlocked state. I did re-enable developer options after locking my phone again and OEM unlocking was turned off by default. This hasn't bricked my phone and I'm assuming that if it had the potential chance to, OnePlus would have greyed it out. See below:
How I fixed my "bootloop" problem:
I flashed C.26 through Fastbootd and wiped data, and... bootloop!
Looks like device is trying to access wrong slot A or B and unable to.
You need to hold power button + volume up, it should reboot normally. It's a temporary solution, you will face it again after another reboot.
Then you need to transfer the same zip you used to flash into root directory of the phone (where all the folders are living). Go to settings -> About device -> Status -> Tap 7 times on build number to unlock local update feature.
Next, tap on big OxygenOS banner -> Three-dots menu at the top right -> Local install. After, select the zip file you previously copied. Confirm and wait for phone to update itself.
Update will be installed and bootloop issue should be fixed.
breadsnack said:
Erm I've actually got no clue, I know for a fact that if your bootloader is unlocked, OEM unlocking is on by default and greyed out so you cannot turn it off while the bootloader is in it's unlocked state. I did re-enable developer options after locking my phone again and OEM unlocking was turned off by default. This hasn't bricked my phone and I'm assuming that if it had the potential chance to, OnePlus would have greyed it out. See below:
View attachment 5859683
Click to expand...
Click to collapse
for my case OEM did not turn off by default, however, i did it and there is no issues .. thanks
thegreatn_ said:
How I fixed my "bootloop" problem:
I flashed C.26 through Fastbootd and wiped data, and... bootloop!
Looks like device is trying to access wrong slot A or B and unable to.
You need to hold power button + volume up, it should reboot normally. It's a temporary solution, you will face it again after another reboot.
Then you need to transfer the same zip you used to flash into root directory of the phone (where all the folders are living). Go to settings -> About device -> Status -> Tap 7 times on build number to unlock local update feature.
Next, tap on big OxygenOS banner -> Three-dots menu at the top right -> Local install. After, select the zip file you previously copied. Confirm and wait for phone to update itself.
Update will be installed and bootloop issue should be fixed.
Click to expand...
Click to collapse
This is another method of solving the bootlooping issue. I'm assuming that the device just automatically unscrews itself when it receives an update through within the OS. The bootlooping issue is probably because its trying to find a bootable OS through both slot A and B until it manages to fix itself. I personally just flashed C22 and updated to C26 and it had the same effect as flashing C26 and flashing C26 again in local updates.
Thanks for the info! I'll append it to the guide in a bit...
Adly1991 said:
for my case OEM did not turn off by default, however, i did it and there is no issues .. thanks
Click to expand...
Click to collapse
Sweet, will append this information to the guide!
breadsnack said:
This is another method of solving the bootlooping issue. I'm assuming that the device just automatically unscrews itself when it receives an update through within the OS. The bootlooping issue is probably because its trying to find a bootable OS through both slot A and B until it manages to fix itself. I personally just flashed C22 and updated to C26 and it had the same effect as flashing C26 and flashing C26 again in local updates.
Thanks for the info! I'll append it to the guide in a bit...
Click to expand...
Click to collapse
I'd like to point out that there is no need to unpack the zip file, Updater will do everything automatically.
This is to inform that i got update c.26 and c.27 through OTA with no issue ..
Wonderful lemme know if you run into any more issues and I'll be glad to help
Adly1991 said:
This is to inform that i got update c.26 and c.27 through OTA with no issue ..
View attachment 5882617
Click to expand...
Click to collapse
thk202 said:
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
View attachment 5856125
Click to expand...
Click to collapse
how you fixed this issue ? i got same problem .