Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
All you will need link, at the end of the post. I don't know for how long it will be up, but you can use it for now.
By the way.... Should you find something useful here... please hit the thanks button in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00 (or any latest version).
Steps:
1. Install the windows drivers you downloaded
Note : If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
2. Open the folder you extracted SP Flashtool and run it as administrator.
3. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet. (should work with holding the power key down for a little longer than 10 seconds. If not hold down volume key and power button for the same amount of time - tested and working)
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a. adb reboot bootloader
b. fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10. Choose reboot to system and allow complete boot cycle! Essential!
11. Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version).
12. Once installed back to the windows terminal and issue:
a. adb reboot bootloader
b. fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note : Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
All you will need and credits:
https://drive.google.com/drive/fold...ourcekey=0-SDvJaXtWWk-TY9B53ct8dw&usp=sharing (thanks button, thanks button, thanks button!!! )
Results:
(it is in Greek, but you get the idea )
Hope I have helped! Happy playing with the commands and whole process! :good:
Lastly, if you get stuck at any point, you can either use this thread or PM me for further advice, explanation and/or any kind of assistance.
Note: Special thanks to @MotoJunkie01 for actually taking the time to further help people on this thread, as unfortunately I do not currently have the time to do so myself. It is worth checking out @MotoJunkie01 's threads also. There, you can find very useful and updated information.
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
If you find it useful, just hit thanks in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00
Steps:
1. Install the windows drivers you downloaded
2. Open the folder you extracted SP Flashtool and run it as administrator.
4. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet.
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a.adb reboot bootloader
b.fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10.Choose reboot to system and allow complete boot cycle! Essential!
11.Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version.
12.Once installed back to the windows terminal and issue:
a.adb reboot bootloader
b.fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note 1: Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
Note 2: If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
I apologize for not being able to post links, but I believe the required software is not particularly hard to find.
Hope I have helped! Happy playing with the commands and whole process! I will continue to help as much as I can :good:
Click to expand...
Click to collapse
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
MotoJunkie01 said:
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
Click to expand...
Click to collapse
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
r&xp said:
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
Click to expand...
Click to collapse
Thank you for the encouragement. I am in hopes that we can eventually get a dedicated device forum for the tb3-850f. I truly believe this tablet has the potential for plenty of future development.
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Rimmir said:
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Click to expand...
Click to collapse
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
r&xp said:
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Click to expand...
Click to collapse
Lol yessir, thanked!
MotoJunkie01 said:
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
Click to expand...
Click to collapse
Looking forward to it. I picked mine up from walmart just yesterday for using as a google maps/car media center
My Lenovo Tab 3 replacement finally arrived in the mail. I'll be picking up where I left off on compiling both unmodified stock and custom stock-based ROMs for this tablet.
On my modified stock based ROM, I'm considering the implementation of Substratum (Root Ver) for theming, but I would like to get the input of other device owners first. So far, I have debloated, deodexed and zipaligned the OS. I am including the modified/patched boot image with SuperSU v2.79 SR3 binaries installed for systemless root, Nova Launcher, Pixel Icon Pack, BusyBox v1.26.2 binaries pre-injected in /su/xbin/, and Kernel Adiutor-Mod installed in /system/apps/ for user defined adjustments to the stock kernel and governors.
You guys please give me input on what you would like included in the ROM. Thanks
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
Click to expand...
Click to collapse
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
chienfou said:
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
Click to expand...
Click to collapse
Really glad it worked for you!!!
Thumbs up! :good::good:
load the scatter file .txt in SP Flashrom is OK ... it show me purple color until finish loading the file.
but how come when I hit the green button Download, it seems like nothing downloading,
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
yiukiang said:
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
Click to expand...
Click to collapse
Try again to get TWRP installed to your /recovery partition or, alternatively, try to simply boot into TWRP from fastboot with the fastboot boot twrp.img command. It is common for members to experience some difficulty in installing custom recovery on this device. It has been my experience that most members are successful the second time around.
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
yiukiang said:
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
Click to expand...
Click to collapse
System updates (OTAs) won't install on rooted operating systems. To install an OTA, you must have unmodified stock /boot, /system, and /recovery partitions installed. On the GPS issue, go to Settings, Apps, and ensure Google Maps has been granted location access permission.
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
xavier234 said:
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
Click to expand...
Click to collapse
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
MotoJunkie01 said:
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
Click to expand...
Click to collapse
Hello, I'll weigh in on this one. There are multiple threads above the TB3-850F on this forum and also another forum.
I initially followed a different thread and instructions which caused my problem. Notably do not allow TWRP write access !!! This mistake caused the soft-brick.
Anyone following any other advice about TB3-850F or downloading any other image BEWARe. Only follow the advice in this thread by r&xp:
https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
Following this advice I now restored original image and then rooted in just a few hours.. Thank you r&xp for the good advice. :laugh:
Related
OFFICIAL ONEPLUS 2 STOCK RESET
SOURCE : OnePlus L2 Support Team
VERSION : OxygenOS 3.0.2
DOWNLOADS
1. OnePlus2 Stock Reset Oxygen 3.0.2 Google Drive | Mediafire
2. Qualcomm Drivers Version 1.00.14 Google Drive | Mediafire
INSTRUCTIONS
You are doing this on your own responsibility. I take no responsibility whatsoever.
(THIS WILL WIPE YOUR ONEPLUS INCLUDING INTERNAL SD)
Download both the files from above and extract them (WinRAR, WinZIP, 7ZIP etc). You should have 2 folders: "OnePlus2_14_A.19_160604" and "qc"
A. Install the Certificates followed by the Qualcomm drivers.
1. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
2. Run the Qualcomm setup wizard (also located in the qc folder)
3. When setup completes, launch Command Prompt as an Administrator and type bcdedit /set testsigning on
4. Restart your computer. (Once it gets on, you should see a watermark stating Test Mode in the bottom right corner. If not, type bcdedit in Command Prompt as an Administrator to check if testsigning shows on. If not, repeat step 3.)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.19_160604 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 3).
3. First click the right square Chinese button. This will perform an integrity check on the downloaded files by verifying the MD5 hash values.
4. The system will seem to hang for a bit but should give you a pop up with the results of the above verification. When everything is ok. Press the start button. and let the progress finish. (If something is not ok, you will have to re-download the images. Google Drive can help extract only the necessary files.)
5. When it's done. Disconnect the USB cable and turn on the device.
6. Launch Command Prompt as an Administrator and type bcdedit /set testsigning off and reboot. Your system should no longer be in Test Mode.
C. Reset TAMPER Flag (Optional)
(This may potentially change your SmartPhone to a rather large paperweight and I will just laugh at you bearing no responsibility)
+ This part of the guide is not an Official Procedure and is in no way affiliated to OnePlus.
+ It is advisable to do this before any of the above mentioned operations.
+ Prerequisites:
Root
HEX Editor with root features
Root File Manager
+ BEWARE: You are modifying partitions which cannot be restored regardless of what you flash. You have been warned AGAIN
1. In File Manager browse to the devinfo partition (dev/block/bootdevice/by-name/)
2. Open devinfo using the HEX Editor.
3. Modify the TamperBit (attached screenshot) from 01 to 00.
4. Save and reboot to fastboot.
5. Type fastboot oem device-info to confirm.
CREDITS
OnePlus Team for the Files.
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Finally Managed to get a hand on this after a late night session with OnePlus. Great that we now have the MM Stock Reset which should theoretically help to get back to stock regardless of the ROM, customizations etc.
I believe this is the best option to use to return to stock from CM.
fareed_xtreme said:
OFFICIAL ONEPLUS 2 STOCK RESET
CREDITS
OnePlus Team for the Files.
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Click to expand...
Click to collapse
Thank you for mentioning me, Great Work
Is it recommended to do this to make sure that the installation is well made?
I installed 3.0.2 via OTA but my battery life is mediocre(3 hours). I know that in my Samsung devices it was better to clean flash the room yourself rather than doing it via OTA but I don't know about oneplus 2.
Should I just factory reset it or maybe do this whole procedure ?(except step C)
mantiyeah said:
Is it recommended to do this to make sure that the installation is well made?
I installed 3.0.2 via OTA but my battery life is mediocre(3 hours). I know that in my Samsung devices it was better to clean flash the room yourself rather than doing it via OTA but I don't know about oneplus 2.
Should I just factory reset it or maybe do this whole procedure ?(except step C)
Click to expand...
Click to collapse
You have a few options.
1. This threads Stock Reset option guarantees your phone will be Stock OnePlus, just as a new phone (Bootloader Locked, Recovery Stock, Kernel Stock etc). However, it requires some time and effort. [Recommended]
2. Factory Reset may fix your Battery issue (not sure) but it is the quickest method.
3. You could use @Spannaa 's Fastboot images to flash all the images in this thread but via fastboot which is quicker and requires minimal setup. [Recommended]
Hello , after b3 command of the tools I FAILED appears . Tips ?
---------- Post added at 02:43 PM ---------- Previous post was at 02:14 PM ----------
Thank you. Solved !!
fareed_xtreme said:
You have a few options.
1. This threads Stock Reset option guarantees your phone will be Stock OnePlus, just as a new phone (Bootloader Locked, Recovery Stock, Kernel Stock etc). However, it requires some time and effort. [Recommended]
2. Factory Reset may fix your Battery issue (not sure) but it is the quickest method.
3. You could use @Spannaa 's Fastboot images to flash all the images in this thread but via fastboot which is quicker and requires minimal setup. [Recommended]
Click to expand...
Click to collapse
Hello again,
When you say ''to flash all the images in this thread'' do you mean the 1. OnePlus2 Stock Reset Oxygen OS 3.0.2 and the 2. Qualcomm Drivers Version 1.00.14 ???
Or does it mean that flashing via fastboot the spanna image I am flashing everything at once?
Thank you very much
mantiyeah said:
Hello again,
When you say ''to flash all the images in this thread'' do you mean the 1. OnePlus2 Stock Reset Oxygen OS 3.0.2 and the 2. Qualcomm Drivers Version 1.00.14 ???
Or does it mean that flashing via fastboot the spanna image I am flashing everything at once?
Thank you very much
Click to expand...
Click to collapse
My Friend, you need to do any one of the above 3 mentioned methods. You could:
1. Follow this guide, the first post which has all the details. This is the method used by OnePlus to restore your phone when you have issues.
3. You could alternatively flash via Fastboot using the images from the mentioned thread.
You chose either one of the above mentioned procedures. Not both. If you run into issues do let is know. The procedure is detailed and if you follow my guide to the dot, you should be all set in the first attempt itself (for Flashing method 1)
Thanks fareed_xtreme, everything went well. Good job !
Sim and wifi not detected!!
fareed_xtreme said:
OFFICIAL ONEPLUS 2 STOCK RESET
SOURCE : OnePlus L2 Support Team
VERSION : OxygenOS 3.0.2
DOWNLOADS
1. OnePlus2 Stock Reset Oxygen 3.0.2 Google Drive | Mediafire
2. Qualcomm Drivers Version 1.00.14 Google Drive | Mediafire
INSTRUCTIONS
You are doing this on your own responsibility. I take no responsibility whatsoever.
(THIS WILL WIPE YOUR ONEPLUS INCLUDING INTERNAL SD)
Download both the files from above and extract them (WinRAR, WinZIP, 7ZIP etc). You should have 2 folders: "OnePlus2_14_A.19_160604" and "qc"
A. Install the Certificates followed by the Qualcomm drivers.
1. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
2. Run the Qualcomm setup wizard (also located in the qc folder)
3. When setup completes, launch Command Prompt as an Administrator and type bcdedit /set testsigning on
4. Restart your computer. (Once it gets on, you should see a watermark stating Test Mode in the bottom right corner. If not, type bcdedit in Command Prompt as an Administrator to check if testsigning shows on. If not, repeat step 3.)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.19_160604 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 3).
3. First click the right square Chinese button. This will perform an integrity check on the downloaded files by verifying the MD5 hash values.
4. The system will seem to hang for a bit but should give you a pop up with the results of the above verification. When everything is ok. Press the start button. and let the progress finish. (If something is not ok, you will have to re-download the images. Google Drive can help extract only the necessary files.)
5. When it's done. Disconnect the USB cable and turn on the device.
6. Launch Command Prompt as an Administrator and type bcdedit /set testsigning off and reboot. Your system should no longer be in Test Mode.
C. Reset TAMPER Flag (Optional)
(This may potentially change your SmartPhone to a rather large paperweight and I will just laugh at you bearing no responsibility)
+ This part of the guide is not an Official Procedure and is in no way affiliated to OnePlus.
+ It is advisable to do this before any of the above mentioned operations.
+ Prerequisites:
Root
HEX Editor with root features
Root File Manager
+ BEWARE: You are modifying partitions which cannot be restored regardless of what you flash. You have been warned AGAIN
1. In File Manager browse to the devinfo partition (dev/block/bootdevice/by-name/)
2. Open devinfo using the HEX Editor.
3. Modify the TamperBit (attached screenshot) from 01 to 00.
4. Save and reboot to fastboot.
5. Type fastboot oem device-info to confirm.
CREDITS
OnePlus Team for the Files.
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Click to expand...
Click to collapse
I did as told and was able to boot up successfully. But unfortunately the sim and wifi are not getting detected...do you have any solution for this? Also the phone keeps rebooting at random...would be really thankful for a quick solution to this.
Thx!! My OnePlus 2 is almost dead. Fastboot recovery only works for CM recovery, and there is no ROM inside sdcard. I flash TWRP, but no working. ADB sideload, TZ version problem - no luck. Thank you for sharing this thread.
Now is back and alive again
muthukumarc said:
I did as told and was able to boot up successfully. But unfortunately the sim and wifi are not getting detected...do you have any solution for this? Also the phone keeps rebooting at random...would be really thankful for a quick solution to this.
Click to expand...
Click to collapse
Which version of OnePlus 2 do you have? I have tested this on the European version.
Try this, Re-Flash the whole package AGAIN. After the first boot, reboot into recovery and reset to factory defaults. If it still does not work out, then let me know.
fareed_xtreme said:
Which version of OnePlus 2 do you have? I have tested this on the European version.
Try this, Re-Flash the whole package AGAIN. After the first boot, reboot into recovery and reset to factory defaults. If it still does not work out, then let me know.
Click to expand...
Click to collapse
Thank you for the fast response...i have the A2003 that i bought in india...I am still having the same problem...flashed the os again and did a hard reset...but still sim and wifi are not detected.
Tryed this one but when i upgrade to 3.0.2or clean flash this my camera stays black. Any help for this?
muthukumarc said:
Thank you for the fast response...i have the A2003 that i bought in india...I am still having the same problem...flashed the os again and did a hard reset...but still sim and wifi are not detected.
Click to expand...
Click to collapse
Even I have an A2003, European version and Indian version are the same. Have you pressed the square button to verify if the Package you have downloaded is in good shape and not corrupted? Do check that.
Alternatively head over to this thread and try flashing through TWRP using the Fastboot package of 3.0.2.
Or you could flash the modem file manually if you know how it's done.
Also as a last resort, try flashing an older version of the stock reset (there will be a version 2.2.0 in the general section or through Fastboot using the thread provided above).
If after all this it still does not work, please open a ticket with OnePlus. Sorry for the inconvenience.
C.H.T.J. said:
Tryed this one but when i upgrade to 3.0.2or clean flash this my camera stays black. Any help for this?
Click to expand...
Click to collapse
Do follow the above recommendations. However, if it did not work for you with other ROMs, Resets or Fastboot Zips, then I am very sure, none of the above steps will be of much use. Maybe CM might help but again, it's a longshot. Best option for you is to open a Ticket with OnePlus as this looks more inclined towards a driver or hardware issue.
fareed_xtreme said:
Even I have an A2003, European version and Indian version are the same. Have you pressed the square button to verify if the Package you have downloaded is in good shape and not corrupted? Do check that.
Alternatively head over to this thread and try flashing through TWRP using the Fastboot package of 3.0.2.
Or you could flash the modem file manually if you know how it's done.
Also as a last resort, try flashing an older version of the stock reset (there will be a version 2.2.0 in the general section or through Fastboot using the thread provided above).
If after all this it still does not work, please open a ticket with OnePlus. Sorry for the inconvenience.
Do follow the above recommendations. However, if it did not work for you with other ROMs, Resets or Fastboot Zips, then I am very sure, none of the above steps will be of much use. Maybe CM might help but again, it's a longshot. Best option for you is to open a Ticket with OnePlus as this looks more inclined towards a driver or hardware issue.
Click to expand...
Click to collapse
Sorry for the delayed response...i tried the fastboot method as well i have wifi now but no sim yet... i think i found out the problem. The IMEI number seems to be missing... and i read that would be the case for sim not detected.... i tried lots of methods (trying to get into engineering mode & using terminal emulator) to rectify it but was unsuccessful... I think the methods i saw were all for mediatek phones...couldnt find one for qualcomm....do you know any right way for fixing the IMEI issue? Thank you so much for your help so far on this.
muthukumarc said:
Sorry for the delayed response...i tried the fastboot method as well i have wifi now but no sim yet... i think i found out the problem. The IMEI number seems to be missing... and i read that would be the case for sim not detected.... i tried lots of methods (trying to get into engineering mode & using terminal emulator) to rectify it but was unsuccessful... I think the methods i saw were all for mediatek phones...couldnt find one for qualcomm....do you know any right way for fixing the IMEI issue? Thank you so much for your help so far on this.
Click to expand...
Click to collapse
I don't have much information on this. If your IMEI doesn't show, it means that one of your device specific partition is corrupted (I guess it's EFS, not sure). If you have a nandroid backup of all your partitions, then you could use them to recover. Else, your options are limited and your only friend is Google search. This doesn't usually happen.
When everything is ok. Press the start button. and let the progress finish.
Click to expand...
Click to collapse
How much time it can take? Mine is going on for almost two hours now
Only Stop button is clickable and the square button too. Start,Enum, Exit are grayed out.(not clickable)
Btw i did press the stop button after getting frustrated for more than half an hour.
And then again performed integrity check. And then again pressed the start button.
When it finish, does it show some notification?
Chhatrapal said:
When everything is ok. Press the start button. and let the progress finish.
How much time it can take? Mine is going on for almost two hours now
Only Stop button is clickable and the square button too. Start,Enum, Exit are grayed out.(not clickable)
Btw i did press the stop button after getting frustrated for more than half an hour.
And then again performed integrity check. And then again pressed the start button.
When it finish, does it show some notification?
Click to expand...
Click to collapse
This could mean that it is still waiting for your device to connect. Have you double checked your drivers and have you found the different line in the flashing app? You will need to restart the process and follow it step by step again.
It will usually take between 8 - 12 minutes max to finish flashing in the app. Also once it's done, in the app all lines will turn green (if I recall correctly).
So i've tried this and various other methods along similar lines. The flashing tool finishes and goes green but then also goes red.
On the reboot, recovery is still missing and i have fastboot.
If i use 'fastboot continue', I boot into the rom for setup and everything starts to work. However, I don't have any recovery, so the phone does not boot. Bootloader is now locked too so I can't try to flash recovery.
hi folks,
tomorow should be getting my hands on the Ulephone power 2.
its the 5.5 screen 4gb ram 64gb rom.
all looks good until i have seen that the normal duel sim is one is hybrid for sdcard which is the norm right,
ant
but............
usually its sim 1 is for 4g cards and the hybrid is for 2g/3g/sdcard. yeah?
well the power 2 looks like its sim slot 1 is a 2g/3g slot and the hybrid is 4g or sdcard??????????
so will have to choose 4g or sdcard??? that cant be right?
I don't try this device with sim.
I know you can use the older power (1) have a sim 4g and SD card
So i believe the power 2 have the same method.
My first steps: How to root this device? i don't find a twrp.
I try to root with kingroot kingoroot, no results
Please?
The power 2 is the same as the power wrt the sim/memory card tray; both sim slots support 4g, but only one at a time. So if you put two 4g sims in, only one of them will have 4g (you choose which one), with a sim and a memory card the 4g should default to the inserted sim, but you might have to check this in settings.
Received my power 2 a couple of weeks ago after having it on pre-order for a month and I love it (sold the original power towards the cost).
I haven't tried rooting it yet, but was thinking of trying to flash twrp for the original power and seeing if that works. The great thing about these phones is that they're very hard to brick as you can always flash them as long as they still switch on.
Slàinte
mmidders
Hello my friends. I just bought the ulefone power 2 and i try to root it. Can anyone help me pls ???
mmidders said:
The power 2 is the same as the power wrt the sim/memory card tray; both sim slots support 4g, but only one at a time. So if you put two 4g sims in, only one of them will have 4g (you choose which one), with a sim and a memory card the 4g should default to the inserted sim, but you might have to check this in settings.
Received my power 2 a couple of weeks ago after having it on pre-order for a month and I love it (sold the original power towards the cost).
I haven't tried rooting it yet, but was thinking of trying to flash twrp for the original power and seeing if that works. The great thing about these phones is that they're very hard to brick as you can always flash them as long as they still switch on.
Slàinte
mmidders
Click to expand...
Click to collapse
I'm sure it's not working the twrp from the power (1).
If you have troubles with bootloops you can flash again the facatory rom and SP flash tools.
Press the power volume + and - and SP flash tools gonna flash.
The only way is to made a twrp from the k6000 http://fvknl.pro/k6000-plus-root-guide/
I don't know how, that device is almost the same...
There has been 2 ulefone Updates since launch
Android 8.0 is scheduled for end of the year.
Updates are fine, who can create a TWRP? So we can finally root the device
geheimke said:
Updates are fine, who can create a TWRP? So we can finally root the device
Click to expand...
Click to collapse
up
TWRP please!
Not so easy to do it. It will take very long time to port or build twrp
It sucks that power 2 still doesn't have root or twrp. I refuse to touch unrooted phones. I just received it as gift. I will keep it in a drawer and check next month or so.
I find that it lacks optimisation, kinda laggy in 3D/games ..
On Antutu, scores is 44000. I tested a galaxy S5 of a friend, it was 72000. For a phone that is several years older than Power 2.
I understand that it comes not with high end cpu/gpu but still..
I will copy my post from needrom website.
I have successfully rooted my two Power 2 phones. I had to port the TWRP recovery from Oukitel k6000 plus using Carliv Image Kitchen and following some online tutorials.
The only issue is, TWRP is semi functional, that is, touch doesn't work. I had to connect a mouse to my phone via OTG usb port and using some dongle to make USB smaller to fit the port. Also it comes with Russian language as default, but can be changed to English or any other as the original TWRP from Oukitel k6000+ (3rd button from second column, then click on Globe tab at the top right then choose English and the only button at the bottom to accept the change).
I am trying to fix this with no luck so far. But at least I am rooted and I was able to flash "SR1-SuperSU-v2.82-SR1-20170608224931.zip" which is the latest as of writing this. SuperSu functions properly and I am able to use AdAway.
If anyone is interested in the recovery image, I will post it. I flashed it using fastboot though after unlocking the bootloader using "fastboot oem unlock"
Click to expand...
Click to collapse
Rebel_X said:
I will copy my post from needrom website.
Click to expand...
Click to collapse
I would very much like to give this a go with my ulefone power 2!
Here you go, TWRP for Ulefone Power 2
What you need to do before you start flashing:
0) You need to have ADB installed on your computer, if you have Windows, the easiest way is by using 15 Seconds ADB Installer v1.4.3.
1) Your bootloader must be unlocked, otherwise flashing recovery will fail using fastboot command. PLEASE NOTE: When unlocking the bootloader, your phone will do a factory reset automatically, so backup all your important files beforehand.
To unlock the bootloader:
a) Go to Settings -> About Phone -> Build number (tap on it 7 times to unlock Developer Options) -> Tap on back to Settings menu then Developer Options.
b) Now move the slider for "OEM Unlocking" to enable it, say yes to the warning message.
c) Enable "USB Debugging"
d) Connect your phone to your computer via USB cable, say Yes for the dialog on your phone to trust your computer for debugging using USB.
e) Run command prompt and type
Code:
adb reboot bootloader
Then press enter
f) Once in bootloader, type
Code:
fastboot oem unlock
Then press Volume UP on your phone to allow OEM Unlock. It shouldn't take long, just few seconds and a message will appear on command prompt saying success or OK.
g) Type
Code:
fastboot reboot
To reboot your phone, it might reboot twice, it will do a factory reset and you will have to "Enable Developer Options and USB Debugging" again. As a side note, you will also notice that OEM Unlocking is grayed out. It will remain like that unless you do "fastboot oem lock" or erase the entire phone (might erase imei, but can be restored using SN Writer Tool) and/or flash bootloader using SP_FLASH_TOOL, but I digress.
2) Before you flash TWRP recovery, you must have SuperSu zip file on your phone beforehand, otherwise, your phone will not boot to Android. It has to do with something about the original TWRP for Oukitel k6000+, since the author of that TWRP port said so in the instructions about how to flash the recovery.
So download SR1-SuperSU-v2.82-SR1-20170608224931.zip from this link or the original SuperSu thread on XDA, and copy the file into your phone, say inside the Download folder in the internal memory of your phone.
3) Open command prompt again if it is not already open, type
Code:
adb reboot bootloader
4) Once in bootloader, type
Code:
fastboot flash recovery C:\TWRP-recovery-20170618-1340.img
Note: You replace the path for the TWRP recovery to where you have the file, to make it easier, just put it in the root of C drive.
Also, if you don't already know, while in command prompt, you can type C:\TWRP then press TAB to auto-complete the file name for you, so you don't have to type lengthy file names. Keep pressing TAB to cycle between similar occurrences, that is, if you have more than one file that their names start with TWRP
5) Press power button until phone shuts down. Then press Volume UP + Power and keep holding until you see super tiny text with 3 options to cycle between. Release your fingers from Volume Up + Power, then cycle between the options using Volume Up only, choose "RECOVERY" which is the first in the menu, then press Volume DOWN to select.
6) Wait a few seconds, you will be inside TWRP, connect your phone with a mouse since touch doesn't work here. Once you do, you will see a mouse pointer appear. I used a wireless mouse with bluetooth dongle, with an adapter to change USB port size.
7) Slide the slider to the right, to enable modifications to System partition. Don't press anything else, unless you know Russian, I don't .
8) To change the language to English or your own language, click on the third button of the second column. Then click on the Globe tab on the top right corner, change language, then press the only button at the bottom to accept. Language of the UI is changed.
9) Click "Install", browse for the SuperSu zip file you have downloaded to your phone, for example inside the Download folder. And then select it.
10) Slide to the right to flash SuperSu.
11) From the TWRP menus, you can reboot your phone.
12) Enjoy your rooted Power 2 phone. :good:
---------- Post added at 04:47 AM ---------- Previous post was at 04:47 AM ----------
alpsayin said:
I would very much like to give this a go with my ulefone power 2!
Click to expand...
Click to collapse
Check the post above :good:
hello , i got a ulefone power 2 but unfortunately its not powering on. As i am from india and returning or replacing is costly and timetaking process, i need you guys to help me. I tried to flash it with software available on the website but stuck. I need some checksum.ini file which is not there in the firmware file provided. So anyone please help me. the phone doesnt even show the ulefone logo. i can just see the charging percentage when the charger is connected, then keeping it connected i tried to turn on but didnt work. keeping the charger connected ,after some time the display goes off and no mater how long you press the power button , the display doesnt show up. I can only see the notification bulb.
Soft bricked :laugh: trying to recover the phone, official ulefone guide is useless. Getting some error about a missing checksum.ini file. Will keep this thread updated
All went well until step 9, where I realised factory reset deleted the supersu zip. So I tried to reboot into system to download it again. It never booted. Doesnt even go into adb mode.
Fastboot mode and TWRP intact (TWRP needs a mouse). I was able to flash original recovery via fastboot, getting "cannot load system.img" error when I try to flash system (it appears I might need to update my adb/fastboot version).
UPDATE: was able to flash the stock rom. And tried to follow the guide again, and faced the same symptoms. If i have working TWRP, then the system doesnt boot. And vice-versa. Will keep updated, i'm a persistent mf
Rebel_X said:
Here you go, TWRP for Ulefone Power 2
What you need to do before you start flashing:
0) You need to have ADB installed on your computer, if you have Windows, the easiest way is by using 15 Seconds ADB Installer v1.4.3.
1) Your bootloader must be unlocked, otherwise flashing recovery will fail using fastboot command. PLEASE NOTE: When unlocking the bootloader, your phone will do a factory reset automatically, so backup all your important files beforehand.
To unlock the bootloader:
a) Go to Settings -> About Phone -> Build number (tap on it 7 times to unlock Developer Options) -> Tap on back to Settings menu then Developer Options.
b) Now move the slider for "OEM Unlocking" to enable it, say yes to the warning message.
c) Enable "USB Debugging"
d) Connect your phone to your computer via USB cable, say Yes for the dialog on your phone to trust your computer for debugging using USB.
e) Run command prompt and type
Code:
adb reboot bootloader
Then press enter
f) Once in bootloader, type
Code:
fastboot oem unlock
Then press Volume UP on your phone to allow OEM Unlock. It shouldn't take long, just few seconds and a message will appear on command prompt saying success or OK.
g) Type
Code:
fastboot reboot
To reboot your phone, it might reboot twice, it will do a factory reset and you will have to "Enable Developer Options and USB Debugging" again. As a side note, you will also notice that OEM Unlocking is grayed out. It will remain like that unless you do "fastboot oem lock" or erase the entire phone (might erase imei, but can be restored using SN Writer Tool) and/or flash bootloader using SP_FLASH_TOOL, but I digress.
2) Before you flash TWRP recovery, you must have SuperSu zip file on your phone beforehand, otherwise, your phone will not boot to Android. It has to do with something about the original TWRP for Oukitel k6000+, since the author of that TWRP port said so in the instructions about how to flash the recovery.
So download SR1-SuperSU-v2.82-SR1-20170608224931.zip from this link or the original SuperSu thread on XDA, and copy the file into your phone, say inside the Download folder in the internal memory of your phone.
3) Open command prompt again if it is not already open, type
Code:
adb reboot bootloader
4) Once in bootloader, type
Code:
fastboot flash recovery C:\TWRP-recovery-20170618-1340.img
Note: You replace the path for the TWRP recovery to where you have the file, to make it easier, just put it in the root of C drive.
Also, if you don't already know, while in command prompt, you can type C:\TWRP then press TAB to auto-complete the file name for you, so you don't have to type lengthy file names. Keep pressing TAB to cycle between similar occurrences, that is, if you have more than one file that their names start with TWRP
5) Press power button until phone shuts down. Then press Volume UP + Power and keep holding until you see super tiny text with 3 options to cycle between. Release your fingers from Volume Up + Power, then cycle between the options using Volume Up only, choose "RECOVERY" which is the first in the menu, then press Volume DOWN to select.
6) Wait a few seconds, you will be inside TWRP, connect your phone with a mouse since touch doesn't work here. Once you do, you will see a mouse pointer appear. I used a wireless mouse with bluetooth dongle, with an adapter to change USB port size.
7) Slide the slider to the right, to enable modifications to System partition. Don't press anything else, unless you know Russian, I don't .
8) To change the language to English or your own language, click on the third button of the second column. Then click on the Globe tab on the top right corner, change language, then press the only button at the bottom to accept. Language of the UI is changed.
9) Click "Install", browse for the SuperSu zip file you have downloaded to your phone, for example inside the Download folder. And then select it.
10) Slide to the right to flash SuperSu.
11) From the TWRP menus, you can reboot your phone.
12) Enjoy your rooted Power 2 phone. :good:
---------- Post added at 04:47 AM ---------- Previous post was at 04:47 AM ----------
Check the post above :good:
Click to expand...
Click to collapse
mbs.yaswanth said:
hello , i got a ulefone power 2 but unfortunately its not powering on. As i am from india and returning or replacing is costly and timetaking process, i need you guys to help me. I tried to flash it with software available on the website but stuck. I need some checksum.ini file which is not there in the firmware file provided. So anyone please help me. the phone doesnt even show the ulefone logo. i can just see the charging percentage when the charger is connected, then keeping it connected i tried to turn on but didnt work. keeping the charger connected ,after some time the display goes off and no mater how long you press the power button , the display doesnt show up. I can only see the notification bulb.
Click to expand...
Click to collapse
Yeah, I had the same issue with the software that comes from Ulefone, it was asking for Checksum Generator that I have to download separately, it was like 150kb stand alone executable, you put it in the same folder of your stock ROM and wait forever for it to build the Checksum, which unfortunately didn't work since it complains about multiple RECOVRY images. So scratch that.
What you need to do, is as I did, download SP FLASH TOOL, it works great, no shinanigans or bullsh!t. It flashed the stock ROM in less than 2 minutes (around 1:30 seconds, to be exact) and revived my phone. There are plenty of youtube tutorials on how to use it. It is easy, just load the scatter file, for the other file, you can use the same all in one mtk file that comes with SP FLash Tool (I did this) or use the one from your STOCK ROM.
I hope that helps :good:
---------- Post added at 02:33 PM ---------- Previous post was at 02:27 PM ----------
alpsayin said:
Soft bricked :laugh: trying to recover the phone, official ulefone guide is useless. Getting some error about a missing checksum.ini file. Will keep this thread updated
All went well until step 9, where I realised factory reset deleted the supersu zip. So I tried to reboot into system to download it again. It never booted. Doesnt even go into adb mode.
Fastboot mode and TWRP intact (TWRP needs a mouse). I was able to flash original recovery via fastboot, getting "cannot load system.img" error when I try to flash system (it appears I might need to update my adb/fastboot version).
UPDATE: was able to flash the stock rom. And tried to follow the guide again, and faced the same symptoms. If i have working TWRP, then the system doesnt boot. And vice-versa. Will keep updated, i'm a persistent mf
Click to expand...
Click to collapse
All I can think of, you did something wrong. Initially, while I was trying to port TWRP, I had the same issue, I was trying to save some steps by flashing the recovery after I unlocked the bootloader without rebooting, the result was TWRP was not able to see any partitions.
Flash Stock-ROM and redo the steps. If you flash the preloader you might have to OEM Unlock your phone again.
I mentioned that if you "do not flash SuperSu, the system will NOT boot to Android". Also mentioned that after you unlock the bootloader, you have to RE-ENABLE USB Debugging, and while you are at it, check to see if your bootloader is unlocked inside Developer Options.
Edit: BTW, try not to unlock the bootloader if it is already unlocked. If it is unlocked, then skip the steps for unlocking the bootloader. It might cause an issue.
These are the steps I used to flash TWRP and I was able to flash SuperSu, all rooted apps are working fine, AdAway, Lucky Patcher...etc!
This:
Rebel_X said:
Here you go, TWRP for Ulefone Power 2
2) Before you flash TWRP recovery, you must have SuperSu zip file on your phone beforehand, otherwise, your phone will not boot to Android. It has to do with something about the original TWRP for Oukitel k6000+, since the author of that TWRP port said so in the instructions about how to flash the recovery.
Click to expand...
Click to collapse
And this combined:
Rebel_X said:
Here you go, TWRP for Ulefone Power 2
9) Click "Install", browse for the SuperSu zip file you have downloaded to your phone, for example inside the Download folder. And then select it.
Click to expand...
Click to collapse
Apparently if you dont flash the supersu first time you go into TWRP then it gets messy. Got the root working now. Thank you for the help and of course for the TWRP build!
Also if anyone's wondering it's possible to restore the system via fastboot. Extract the rom zip (can be downloaded from http:/ulefone.com/download/power2.html ) and flash boot, recovery and system;
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
link for sp flash tool u used.
Rebel_X said:
Yeah, I had the same issue with the software that comes from Ulefone, it was asking for Checksum Generator that I have to download separately, it was like 150kb stand alone executable, you put it in the same folder of your stock ROM and wait forever for it to build the Checksum, which unfortunately didn't work since it complains about multiple RECOVRY images. So scratch that.
What you need to do, is as I did, download SP FLASH TOOL, it works great, no shinanigans or bullsh!t. It flashed the stock ROM in less than 2 minutes (around 1:30 seconds, to be exact) and revived my phone. There are plenty of youtube tutorials on how to use it. It is easy, just load the scatter file, for the other file, you can use the same all in one mtk file that comes with SP FLash Tool (I did this) or use the one from your STOCK ROM.
I hope that helps :good:
---------- Post added at 02:33 PM ---------- Previous post was at 02:27 PM ----------
All I can think of, you did something wrong. Initially, while I was trying to port TWRP, I had the same issue, I was trying to save some steps by flashing the recovery after I unlocked the bootloader without rebooting, the result was TWRP was not able to see any partitions.
Flash Stock-ROM and redo the steps. If you flash the preloader you might have to OEM Unlock your phone again.
I mentioned that if you "do not flash SuperSu, the system will NOT boot to Android". Also mentioned that after you unlock the bootloader, you have to RE-ENABLE USB Debugging, and while you are at it, check to see if your bootloader is unlocked inside Developer Options.
Edit: BTW, try not to unlock the bootloader if it is already unlocked. If it is unlocked, then skip the steps for unlocking the bootloader. It might cause an issue.
These are the steps I used to flash TWRP and I was able to flash SuperSu, all rooted apps are working fine, AdAway, Lucky Patcher...etc!
Click to expand...
Click to collapse
ok what should i select there? formal all+download or download only or firmware upgarade???
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step
lets get to it
place the magisk.apk and the stock boot.img
in the internal memory of your phone (downloads)
if you like to keep stuff organized :good:
3-step
follow the vídeo tutorial and use magisk manager
to patch your stock boot.img it will output a new
boot.img that includes magisk Root (patched_boot.img)
https://www.youtube.com/watch?v=BF4_hnKgjFA
ps: major ty to hovatek team for this great tutorial
step-4 use Google drive or usb OTG to get the patched_
boot.img to your PC and place it in the ADB folder
once you have oem(bootloader) unlocked just
rename the patched_boot.img to boot.img
step-5
unlock oem, these qilive devices wont unlock
the bootloader even if you enable it in DEV options
enable USB debug in dev options
you will need to use ADB commands
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot oem unlock
(MAJOR WARNING the fastboot
oem unlock will wipe/reset/factoryreset/delete your data)
after you give the command small letters will appear
on the phone screen(yes or no) hard to read dont be hasty plz
use VOLUME+ to select and VOLUME - to confirm
note: when my phone ended the unlock it whent back to
that black screen where you choose fastboot-recovery-restart
and was stuck there, side keys did nothing if this happens
just long press the power key for 10 sec it will shutdown
then press power again to turn on
first boot after unlock will take longer then normal dont freakout
after you unlock small letters will appear during boot up saying the device
is not safe unlocked ,you can later use ( fastboot oem lock )
step-6
flash the patched boot.img with ADB
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot flash boot boot.img
finished/ok
command- fastboot reboot
and voila you should now have magisk
installed in the app drawer, open it!!
step-7 run the install one final time from the
magisk manager and install magisk V16 using
recomended option it will verify/patch the boot image
Do NOT select the AVB 2.0 BOX it will bootloop the phone
and your done, enjoy your qilive rooted phone.
from this point on you can use the fastboot
command- fastboot oem lock
to remove the letters in boot up about the
device not safe unlocked
WARNING oem lock
will WIPE/FACTORY RESET again (god damn it!!)
ps: i had to install twice in a row,major pain in the ....
Repeat step 7 after Wipe/Reset
here is the stock boot for 2 qilive models
you can get the stock firmware for any qilive
at this site www.doc-doapi.com/EM/qilive/smartph...te_3m-fdd-cs_mul_20170818-110645_songlixin_PC
and get the recovery or boot from the unpacked firmware file
ps:my phone is the Q8SIN4GP AND ITS WORKING FINE
A VERY SPECIAL TY to topjohnwu (magisk creator), this man is nothing
short of a God damn genius!! , and if you can donate to him.
hope this helps other qilive users to root:highfive:
quick note on the qilive models, they have two model names
the cliente name in my case Q8SIN4GP
and the factory name in my model its 882912
in order to download the right firmware for your model
you need the factory model witch is what appears in the qilive
site above, it will be in the back of the phone or the original
box on a sticker just bellow the bar code, full model exempl
:Q8SIN4GP/882912 my firmware serves several models,
these Q8 models all start with 88xxxx WARNING
dont try this using the wrong firmware/boot file or you will DAMAGE your phone
Help with BOOTLOOP problems, if you find your self stuck in a bootloop
the phone wont go past the qilive logo and just stays there, dont freak out
you will loose your data but there is a way out
just keep pressing power + Volume up until a black screen with 3 options appears
when it does let go, use Volume + to select option and Volume - to confirm
select Fastboot or alternative select recovery and then select reboot to bootloader
both option will place your phone in Fastboot mode, once in fastboot mode
connect your phone to PC and use ADB commands to fix/bootloop
command- fastboot devices
serial appears
command- fastboot oem unlock (skip this if you use phone unlocked)
a confirm action option appears on the phones screen
use Volume up to say YES / or Volume Down to say NO
Warning oem unlock will WIPE/Factory reset your phone
once it finishes the phone will be stuck on the
Recovery/fastboot/restart screen just long press the power key
until the phone shuts down
start the phone again using Power + Volume up when the black
screen with the 3 options come up, let go and use Volume up to
select Fastboot mode and confirm using Volume Down
Once in fastboot connect your phone to PC and use ADB commands
command- fastboot devices
serial apears
Here you will flash the magisk patched_boot.img
the same image you used to root your phone
command- fastboot flash boot boot.img
it will say finished-ok (or similar)
command- fastboot reboot
the boot up time will be longer than normal
but the phone should now complete the boot
and present the inicial setup screen, select language
enter your mail, the usual bla bla...
any way at this point just repeat step 7
to get root running again
sp flash tools v5.1716.
phonedriller said:
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step....
Click to expand...
Click to collapse
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
Awsome work congrats, as for the recovery so far no luck so try not to go 2 crazy until a working recovery is up and working , install stericsons busy box this is always the first root app i install
If possible buy sterics busybox pro and titaniumbackup pro if you want to install apps to sd card apps2sd pro all of these can be tested in free
Version,again nice work congrats enjoy you rooted phone :highfive:
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
phonedriller said:
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
Click to expand...
Click to collapse
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
xdacktheresianum said:
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
Click to expand...
Click to collapse
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
phonedriller said:
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
Click to expand...
Click to collapse
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
xdacktheresianum said:
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
phonedriller said:
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
Click to expand...
Click to collapse
thank you, phonedriller
everything worked perfectly via SPFlash Tool.
and, referring back to our above questions re the possibility of getting TWRP onto the phones, a developer friend of mine writes me this:
>try to flash TWRP:
>Download following files from this link:
>https://mega.nz/#F!qZIgnJRK!5apBfYo1je0ytg-wmA6JMQ
>- Odin3 v3.12.3 (Complete folder)
>- twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>1. Start your Phone into download mode
>2. Start Odin (Odin3 v3.12.3\Odin3.exe)
>3. Click on Options and unmark Auto Reboot
>4. Click AP and select twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>5. Press Start and wait until finished (Reset or OK!)
>6. Restart your phone immediatly to recovery mode
>7. In TWRP Recovery click on mount
>8. Set the checkbox checked at system (that system is mounted)
>9. go back and click on advanced
>10. Open file manager
>11. navigate to system/build.prop and click on build.prop
>12. Click on chmod
>13. type: 0644 and hit the accept button on screen or at the virtual
>keyboard on your phone
>14. restart your phone
i haven't tried this, but am wondering whether it might seem "reasonably possible" when reading through it.
thanks
ckth
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
tommo1982 said:
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
Click to expand...
Click to collapse
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
I had issues with adds being displayed at home screen and I was not able to close them. I had to use NetGuard to find that FOTA talks to 'adsup' and it is a known malware provider. I learned that some of the system apps try to talk with Alibaba servers and AdOppo (whatever it's called). Kaspersky might not be wrong, actually.
I'm trying to download stock firmware, but I don't know the file name. The website with it is locked, so unless I know exactly what I need, I cannot download it.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
phonedriller said:
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
Click to expand...
Click to collapse
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
Ps use root + apps2sd or titaniumbackup to stop/disable the bad apps and replace them with playS app,not possible on all apps of course
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
tommo1982 said:
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
Click to expand...
Click to collapse
Flashing is super easy use spflashtools or. Odin compiling a Rom is not , were you able to get the original firmware? You will need the original firware to get the boot and partition info from what i read so far
Unfortunately not. I will ask at the shop where I bought it how to contact tech. It should be freely available. I don't understand why Qilive restricted access to firmware.
I'll post when I learn anything.
Well, you can download the firmware if you know the file name. The bad news is, it seems the stock firmware has malware preinstalled. If there is anyone who could help confirm it. I have the ROM, and I can upload it to Google Drive if needed.
Hi all,
I'm coming back to a question lingering since the very first post here and mentioned again in post #9:
Is there a successful way to install TWRP on this Qilive model?
Re this topic:
- has anybody tried/has anybody been successful with the procedure described in post #9?
and
- has anybody seen the following TWRP builders' version (do an in-page search on Q8S55IN4G2)
https://twrpbuilder.github.io/fr/downloads/twrp/
with the download belonging to it
https://androidfilehost.com/?fid=890129502657591798
???
any successful installations to report???
Wouldn't THAT be great!!??
thanks
xdack
Hi !
I've attempted to deal with the devil by trying to root my Pioneer XDP-300R resulting in a bootloop problem (device is stuck on "Powered by Android" screen).
I attempted to flash a boot.img for a Onkyo DX-P1 (which is the same firmware), and still I haven't progressed.
No firmware, update or imgs are provided on Pioneer's website.
I still have access to fastboot (OEM is LOCKED, so I can't boot TWRP and such) in bootloader mode and adb push (no shell) in recovery mode.
Do you guys have any idea how to sort it out ?
Edit :
I managed to make my device go into Qualcomm's emergency download mode.
Here's how to :
1 - Make sure the device is completely off and unplugged from USB.
2 - Install QPST V2.7.474 (not enough posts to share url, but I can PM it).
3 - Install QDLoader Drivers (same as #2).
4 - Simply press and hold the "Play" button while connecting it to your computer, the device manager should see a "Qualcomm 9008 port" listed in Ports while the player's screen stays black.
5 - Do the Carlton (important step !)
Now, if anyone possessing a FUNCTIONAL AND ROOTED Pioneer XDP-300r is reading this and willing to help, can you get in touch with me ?
Together, we could manage to save all the other devices from soft-bricking.
All I would need from you is some time, hard disk space and patience to sort it out.
Please <insert_your_name_here>, you're my only hope !
Edit #2 :
Thanks to minotauri's great help, we managed to get a FULL rom backup, split the partitions to files and generate all the files needed for QFIL.
ErrOzz has been given access to this, hoping that he'll try it out soon.
If that works, I'll link you the files and write the walkthrough to bring you DAP back to life.
minotauri's contributions are not in rest tho, he managed to also successfuly patch TWRP for the device, so anyone can securely flash things from there now.
For anyone reading this thread : you're not the only one who screwed things up, we did too but we might have the cure. Hang in there !
grogcw said:
Hi !
I've attempted to deal with the devil by trying to root my Pioneer XDP-300R resulting in a bootloop problem (device is stuck on "Powered by Android" screen).
I attempted to flash a boot.img for a Onkyo DX-P1 (which is the same firmware), and still I haven't progressed.
No firmware, update or imgs are provided on Pioneer's website.
I still have access to fastboot (OEM is LOCKED, so I can't boot TWRP and such) in bootloader mode and adb push (no shell) in recovery mode.
Do you guys have any idea how to sort it out ?
Edit :
I managed to make my device go into Qualcomm's emergency download mode.
Here's how to :
1 - Make sure the device is completely off and unplugged from USB.
2 - Install QPST V2.7.474 (not enough posts to share url, but I can PM it).
3 - Install QDLoader Drivers (same as #2).
4 - Simply press and hold the "Play" button while connecting it to your computer, the device manager should see a "Qualcomm 9008 port" listed in Ports while the player's screen stays black.
5 - Do the Carlton (important step !)
Now, if anyone possessing a FUNCTIONAL AND ROOTED Pioneer XDP-300r is reading this and willing to help, can you get in touch with me ?
Together, we could manage to save all the other devices from soft-bricking.
All I would need from you is some time, hard disk space and patience to sort it out.
Please <insert_your_name_here>, you're my only hope !
Click to expand...
Click to collapse
Hi - I saw your post on Head-Fi (antdroid over there). Let me look into this!
Here is a bunch of system dump images and qcn files: https://drive.google.com/drive/folders/1diqQ8LE-yG4b-WZFB_OPcQp2rDUp9BbV?usp=drive_open
Hello.
How can I write boot from qdload 9008 state?
Hi !
From the edl / qdload 9008 state, you can't afaik.
Here's how I think you can :
1 - Unplug your device from USB and power it off from whatever state it is.
2 - Power it on pressing Power + Previous button (keep holding, you should be "stuck" on the penguin logo).
3 - Connect your USB.
4 - Check that you have a Android ADB Device in your device manager (install drivers manually if you have an Unknown device).
5 - Grab any fastboot from the internet if you don't already have it (I'll PM you my gdrive, it's there for exemple).
6 - From CMD, go to fastboot directory. (cd <my_folder_with_fastboot>).
7 - Type in : fastboot devices
If fastboot sees your device, you're on the good path, else, check your driver / connection / reboot to fastboot "penguin" state.
8 - Type in : fastboot oem device-info
If it replies
(bootloader) Device unlocked: true
among others, you're in a good, good way, else, you're screwed by now, but we are working on it.
9 - If all the precedent are fulfilled type :
fastboot flash boot <my_boot_image.img>
10 - Mandatory Carlton.
I hope you'll be in the right path all the way, if you're stuck somewhere or if your bootloader is locked, please let me know.
Cheers !
ErrOzz said:
Hello.
How can I write boot from qdload 9008 state?
Click to expand...
Click to collapse
I was successful in creating a recovery (twrp) for this device.
https://www.antdroid.net/2019/02/pioneer-xdp-300r-root-twrp-recovery.html?m=1
also created a XDA thread here: https://forum.xda-developers.com/android/development/pioneer-xdp-300r-digital-audio-player-t3902949
Feel free to PM me if you have questions or we can work it through here
Hi,
I have the same problem. I am able to get qdload 9008 state from here now. However, after unplug and followed grogcw's hints, the device is not recognized again. Also, the device hasn't ennobled debug mode before too. All the adb and fastboot commands return no device.
Hopefully can get more help here.
---------- Post added 28th February 2019 at 12:16 AM ---------- Previous post was 27th February 2019 at 11:58 PM ----------
minotauri said:
I was successful in creating a recovery (twrp) for this device.
https://www.antdroid.net/2019/02/pioneer-xdp-300r-root-twrp-recovery.html?m=1
also created a XDA thread here: https://forum.xda-developers.com/android/development/pioneer-xdp-300r-digital-audio-player-t3902949
Feel free to PM me if you have questions or we can work it through here
Click to expand...
Click to collapse
Is there anyway to flash TWRP and so with QDLoader?
I believe he is on vacation for another week and half. If you haven't enabled the bootloader unlock option within Android, then my recovery method may not work since it may not let you flash the recovery.
You can try to fastboot boot recovery.img though
Hi ! I'm back from vacation, but I still haven't my device around.
Any user willing to test are welcome to reply or PM me !
Let's have all the bricked units working, shall we
grogcw said:
Hi ! I'm back from vacation, but I still haven't my device around.
Any user willing to test are welcome to reply or PM me !
Let's have all the bricked units working, shall we
Click to expand...
Click to collapse
How can we get started?
We actually did start probing stuff around, and we are missing something in the "full restoration process", so we're stuck for now.
Sahara protocol still is a mystery for us, and we can't get pass an error.
I think we don't actually have the right programmer_firehose.mbn for our device, but if it's not this, I'm basically out of ideas. (we might need an "QFIL expert" on this)
I still don't have my device around and feeling dumb about this.
Anyway, all the files and tools required to try probing around are in my gdrive and I can PM the link (as I still can't post it right away) if anyone is interested.
Thanks for trying to help or actually help everyone !
Cheers !
Hello,
I try to root my xdp-300r,after reboot have bootloop result.
I don't know how to reflash systme.img.
can suggest any repair plan,thank you~
Was able to unbrick device. Here are the steps TO DO IT
grogcw said:
hi !
I've attempted to deal with the devil by trying to root my pioneer xdp-300r resulting in a bootloop problem (device is stuck on "powered by android" screen).
I attempted to flash a boot.img for a onkyo dx-p1 (which is the same firmware), and still i haven't progressed.
No firmware, update or imgs are provided on pioneer's website.
I still have access to fastboot (oem is locked, so i can't boot twrp and such) in bootloader mode and adb push (no shell) in recovery mode.
Do you guys have any idea how to sort it out ?
edit :
i managed to make my device go into qualcomm's emergency download mode.
Here's how to :
1 - make sure the device is completely off and unplugged from usb.
2 - install qpst v2.7.474 (not enough posts to share url, but i can pm it).
3 - install qdloader drivers (same as #2).
4 - simply press and hold the "play" button while connecting it to your computer, the device manager should see a "qualcomm 9008 port" listed in ports while the player's screen stays black.
5 - do the carlton (important step !)
now, if anyone possessing a functional and rooted pioneer xdp-300r is reading this and willing to help, can you get in touch with me ?
Together, we could manage to save all the other devices from soft-bricking.
All i would need from you is some time, hard disk space and patience to sort it out.
please <insert_your_name_here>, you're my only hope !
edit #2 :
thanks to minotauri's great help, we managed to get a full rom backup, split the partitions to files and generate all the files needed for qfil.
Errozz has been given access to this, hoping that he'll try it out soon.
If that works, i'll link you the files and write the walkthrough to bring you dap back to life.
Minotauri's contributions are not in rest tho, he managed to also successfuly patch twrp for the device, so anyone can securely flash things from there now.
For anyone reading this thread : You're not the only one who screwed things up, we did too but we might have the cure. Hang in there !
Click to expand...
Click to collapse
i was able to unbrick my device
dantuko said:
all credits go to anthony nguyen aka minotauri. Thank you!
requirements:
samsung drivers installed
windows 10 (i have the windows 10 pro installed)
oem unlock
usb debbuging selected prior to brick
install the latest samsung drivers
install fastboot/adb drivers
stock-boot.img provided by minotauri
the steps are as follows:
the device must be in recovery mode an plugged to the computer. I was on stock recovery
open device manager in windows, look for anything android and delete it and choose to delete the drivers
refresh device manager for new devices (keep only the xdp-300 android connected)
right click on the android device and click on update drivers
select browse my computer for driver software
click on let me pick from a list of available drivers
unselect show compatible drivers (if you see a samsumg driver here, select it. If not try generic windows adb drivers)
seletct google adb drivers (this is the one that worked and it's under samsung drivers)
i performed the steps 1 through 8 a few times until the computer categorized the device as adb
open a command prompt, navigate to the directory where fastboot is installed and type: Fastboot devices (you should have a device listed here)
type: Fastboot oem unlock (this unlocks the bootloader)
after copying stock-boot.img to the root of the your fastboot directory, type: Fastboot flash boot stock-boot.img (reboot)
after the reboot you should see normal boot
if you want twrp and root follow the instructions here: https://forum.xda-developers.com/android/development/pioneer-xdp-300r-digital-audio-player-t3902949 all credits go to anthony nguyen.
i installed twrp the latest supersu pro, viper4android, root browser, busy box pro and everything works perfectly.
:fingers-crossed::fingers-crossed::fingers-crossed:good luck to you e n j o y ! ! !:fingers-crossed::fingers-crossed::fingers-crossed:
i am not an android programmer so i won't be able to help you from that perspective, but i a software engineer so i maybe able to answer some questions.
There is no guarantee this method will work for you but it did work for me
I can provide a TWRP backup file for you to restore your device
Click to expand...
Click to collapse
I have a rooted xdp300r rooted
ralf05 said:
Hello,
I try to root my xdp-300r,after reboot have bootloop result.
I don't know how to reflash systme.img.
can suggest any repair plan,thank you~
Click to expand...
Click to collapse
It was bricked and I was able to fix it and root it
Help !!!
Hello
Gentlemen, help me! I've broken my device
I hit the whole system on my xdp300r. What can I do in this case ??? Only I can turn on TWRP and nothing more.
[email protected]
---------- Post added at 05:55 PM ---------- Previous post was at 05:51 PM ----------
dantuko said:
i was able to unbrick my device
Click to expand...
Click to collapse
Help !!!
dantuko said:
i was able to unbrick my device
Click to expand...
Click to collapse
Hello
Could I ask you for a backup file? Unfortunately, I lost the systemThank you very much.
Greetings.
[email protected]
stefan999 said:
Hello
Could I ask you for a backup file? Unfortunately, I lost the systemThank you very much.
Greetings.
[email protected]
Click to expand...
Click to collapse
I UPLOADED THE BACKUP FILE TO MY GOOGLE DRIVE
https://drive.google.com/drive/folders/1vM7Z12w3CsbutSr54lY4tTdzyN1jurpp?usp=sharing
dantuko said:
I UPLOADED THE BACKUP FILE TO MY GOOGLE DRIVE
https://drive.google.com/drive/folders/1vM7Z12w3CsbutSr54lY4tTdzyN1jurpp?usp=sharing
Click to expand...
Click to collapse
Here is a few items to note about the image:
You must have twrp installed and accessible in order to restore this image.
First time booting after the restore will take a long time, so have a cup of coffee and let it do it's thing.
Every time you boot the OS will perform application optimization, it doesn't bother me so I have not even looked into it.
After you boot connect to your WIFI and open Google Play to set up your account
If you want to use Viper4Android, download and install busybox, then open settings, go to apps and disable Musicfx, then reboot and turn Viper4Android on.
Good luck
dantuko said:
Here is a few items to note about the image:
You must have twrp installed and accessible in order to restore this image.
First time booting after the restore will take a long time, so have a cup of coffee and let it do it's thing.
Every time you boot the OS will perform application optimization, it doesn't bother me so I have not even looked into it.
After you boot connect to your WIFI and open Google Play to set up your account
If you want to use Viper4Android, download and install busybox, then open settings, go to apps and disable Musicfx, then reboot and turn Viper4Android on.
Good luck
Click to expand...
Click to collapse
Thanks for answer and sharing your files. Unfortunately, there is some error when trying to restore in TWRP.
I packed all the items from your disk in ZIP and downloaded to the SD card .
I'm getting an error about the content: no MD5 file found Failed to map file'/external_sdxxxxxx-Full BACKUP.zip'
Error instaling zip file
. Do you have an idea why this is happening?
twrp settings
stefan999 said:
Thanks for answer and sharing your files. Unfortunately, there is some error when trying to restore in TWRP.
I packed all the items from your disk in ZIP and downloaded to the SD card .
I'm getting an error about the content: no MD5 file found Failed to map file'/external_sdxxxxxx-Full BACKUP.zip'
Error instaling zip file
. Do you have an idea why this is happening?
Click to expand...
Click to collapse
You need to change settings in twrp not to check md5 checksum, if it doesn't work then i'll create one with checksum.
Hello everyone! This is my first post, I'm very very new here If I somehow missed a rule or two and shouldn't have posted here or etc DO TELL ME, Im open to anything and I appreciate it! To the point, I won't stretch the topic, I'll tell you how I rooted my Gionee x1 device, and the problems I faced and their solutions. You may ask yourselves or just come reply here, Who even owns that device, Well I own one and I wasn't able to root this device it was hard, so for the other mates out their having bought this piece of brick.
and, there's a reason to why Im writing this topic, do read to the end.
So, to start I first of all researched alot both on google and xda forums for any way of doing it, most of which either didn't work or were not supporting my device(f.e. One Click Root Methods didn't work at all).
1. This post has a reply by ZedLens, which is awesome but to my surprise it didn't work for me.
2. This post BusinessKid is a great tutorial for any MTK Device, but the 3rd step of "The Download Stuff:" I couldn't find the scatter for my device.
3. I've a strict download limit for my internet, so I couldn't download the Stock ROM, so I somehow had to extract it from my device, which I failed why? MTK Droid Tool wasn't able to recognize my device. I diagnosed for all possible reasons for this, bad USB check, bad device port check, wrong process check nothing worked, so at the end of the day I somehow managed to download the Stock ROM of Gionee X1 and EVERYONE HAS TO DO IT IN THE END, you'll really need it anyhow.
Now the rooting process,
Tools/Stuff I used:
1. SP Flash Tool(This thing here, is like your hand during examination)
2. MTK Drivers(Important)
3. Stock Gionee X1 ROM
4. Magisk Manager App
I'll attach the Magisk Patched boot.img here along with the scatter so that you can directly flash the boot img instead of wasting time to download the stock rom and etc etc. also you can reply down here if you need any other file, I'll send it to you somehow :3
NOTE: All the images, links, tools, programs and everything belong to their respective owners!! Everything you are doing with the steps above are STIRCTLY your responsibility, if you do it wrong and brick your device you can't charge me for bricking your device, only you and you will be held responsible for any damage/sucess/etc to your device.
Steps to install:
1. Get Stock boot img
2. Install Magisk Manager (DON'T DOWNLOAD IT FROM ANYWHERE use TopJohnWu's Github)
3. Somehow get the Stock boot img into your Internal Storage or anywhere, where Magisk Manager can find and Patch it, Use adb push, connect usb and copy it to the Internal Storage, ANYHOW.
4. After copying, Open Magisk Manager, you'll find two things on the main screen, one is Magisk which has status infos such as (Installed: ), (SAR: ), (A/B: ) and (RAMDISK: ). Within the same square which contains those status info you'll find a Install click on it.
4.1. After clicking on install you'll get a new menu, select next in the Options Square ignoring the choices there(Preserve AVB 2.0 blah blah) and click Next. Now you'll be in the Methods Square here, you select "Select and Patch a File", now locate to the Image and after successfully locating and selecting it click on Let's Go on the right cornor.
4.2. If your image is patched successfully your log in front of you will look something like this:
- Device platform: armeabi-v7a
- Installing: 23.0 (23000)
- Copying image to cache
- Boot image is signed with AVB 1.0
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
- Repacking boot image
- Signing boot image with verity keys
****************************
Output file is written to
/storage/emulated/0/Download/magisk_patched-buildno_abcde.img
****************************
- All done!
Click to expand...
Click to collapse
4.3. You have your patched boot image!!
5. Now get the patched image back to your pc -.-
6. Prepare yourself to focus, Im not responsible for your bricked device!
7. Goto This XDA Post for Tutorial and Information about SP Flash Tool, MTK Drivers ADB Drivers, etc etc.
8. Download and Install MTK Drivers(Link Credit: Bovirus' this post)
1. You'll find a exe, just execute it and it'll be installed automatically.
Click to expand...
Click to collapse
9. Download and open SP Flash Tool and select Scatter-loading file.
10. Now After you've selected the scatter loading file you'll find there are various selections in front of you, Preloader, lk, boot, recovery and etc etc
10.1. DESELECT or UNSELECT (OR WHATEVER YOU CALL IT) every selection other than boot.
10.2. In the row of boot/bootimg, (remember the patched boot image?) click on LOCATION you'll get a explorer window to locate to the patched boot image, locate and select it. In the last it should look something like this:
https://imgur.com/a/WMbTTAC
10.3. Click on Download in SP Flash Tool and connect the device, see next step.
11. Power Off the device and Remove the battery(See 3. in Issues I faced).
12. Now while pressing the Volume UP and Down Button together, connect the M-USB to your device port. I can't explain this but, firstly connect the USB cable to your pc then to your device haha.
13. You'll hear the device connected sound of Windows(If windows user) and the flashing will start
14. Reboot to OS and Voila! Check your Magisk Manager, your device is now rooted! Do remember to install the Magisk App just below the Magisk Root Check!
Now, issues I faced:
1. Device wasn't connecting to the SP Flash Tool, I reinstalled the MTK Drivers but it didn't do any change.
2. FastBoot flashing didn't work, I opted for SP Flash Tool later.
3. Device was starting into Factory mode and/or Recovery mode whenever I pressed Volume UP/Down and then connecting the device through USB, removable battery came to my rescue. Removed the battery, pressed both volume Up and Down button and then connected the USB.
NOTE: Again, all the images, links, tools, programs and everything belong to their respective owners!! Everything you are doing with the steps above are STIRCTLY your responsibility, if you do it wrong and brick your device you can't charge me for bricking your device, only you and you will be held responsible for any damage/success/etc to your device.
Links for boot.img and scatter file: Here is the MediaFire link, I've scanned the files with my Quick Heal Total Security I'm not those multidadoffspring who likes to spread virus/malware etc. and Here is the VirusTotal Link.
Feel free to tell me my errors and mark how can I improve, I appreciate it
And also, if you need any other file from the Stock ROM of the same device, do tell me here or DM at my insta: heartwastaken
Sorry for my bad English.
Thank you!!
Have a great Day
-Vish