[Q] No boot 3840 after root process (not the same as the other guy)

[Q] No boot 3840 after root process (not the same as the other guy) - Dell Venue

OK so I followed thread:
http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
Now I get
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and
http://imgur.com/oCR0VqC,r9FmCXd#0
and
http://imgur.com/r9FmCXd
SO I figured there was a recovery option from http://opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/Doc/OSS_A150&A195.pdf
When I download YTD802A519500-2014-07-16-16.tgz CRC error upon unpacking. Downloaded twice on Windows and Linux machines. Doesn't matter cause xFSTK-Downloader doesn't see it. I have iSocUSB 1.0.4 drivers installed.
This thread didn't seem to apply: http://forum.xda-developers.com/showthread.php?t=1416537 since I don't have a custom recovery.
And all the links are dead in this thread which I think would have worked : http://forum.xda-developers.com/showthread.php?t=1219566
Oh and I can still get into recovery mode.
Fastboot is seen Windows
Any ideas? Any help?
Thanks in advance.

P_Link said:
OK so I followed thread:
http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
Now I get
and
http://imgur.com/oCR0VqC,r9FmCXd#0
and
http://imgur.com/r9FmCXd
SO I figured there was a recovery option from http://opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/Doc/OSS_A150&A195.pdf
When I download YTD802A519500-2014-07-16-16.tgz CRC error upon unpacking. Downloaded twice on Windows and Linux machines. Doesn't matter cause xFSTK-Downloader doesn't see it. I have iSocUSB 1.0.4 drivers installed.
This thread didn't seem to apply: http://forum.xda-developers.com/showthread.php?t=1416537 since I don't have a custom recovery.
And all the links are dead in this thread which I think would have worked : http://forum.xda-developers.com/showthread.php?t=1219566
Oh and I can still get into recovery mode.
Fastboot is seen Windows
Any ideas? Any help?
Thanks in advance.
Click to expand...
Click to collapse
You may need to post your help questions in this thread, http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
Most likely just downloading and flashing the stock boot.img should allow the tablet to boot.

vampirefo said:
You may need to post your help questions in this thread, http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
Most likely just downloading and flashing the stock boot.img should allow the tablet to boot.
Click to expand...
Click to collapse
I can't post in the section due to low post count. Sucks being a lurker sometimes.
Also if you know where to find stock 3840 images please link.

P_Link said:
Also if you know where to find stock 3840 images please link.
Click to expand...
Click to collapse
Same post you got the boot.img from, hharte has uploaded stock system, boot.img and recovery.img

vampirefo said:
You may need to post your help questions in this thread, http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
Most likely just downloading and flashing the stock boot.img should allow the tablet to boot.
Click to expand...
Click to collapse
vampirefo said:
Same post you got the boot.img from, hharte has uploaded stock system, boot.img and recovery.img
Click to expand...
Click to collapse
Holy crap I was searching and looking everywhere else I didn't even see that. Thank you. I should be able to flash this.

vampirefo said:
Same post you got the boot.img from, hharte has uploaded stock system, boot.img and recovery.img
Click to expand...
Click to collapse
Did not work, Fastboot crashes. I tried other system images and I just get a failed error after about 30 seconds, I've tried img and .gz formats as I believe it's suspose to be .gz since it's Intel

P_Link said:
Did not work, Fastboot crashes. I tried other system images and I just get a failed error after about 30 seconds, I've tried img and .gz formats as I believe it's suspose to be .gz since it's Intel
Click to expand...
Click to collapse
Why would you flash system? you should have only flashed stock boot.img
Most likely now you need to read complete thread and follow the unbricking procedures.
Get enough posts, and post in other thread..

vampirefo said:
Same post you got the boot.img from, hharte has uploaded stock system, boot.img and recovery.img
Click to expand...
Click to collapse
vampirefo said:
Why would you flash system? you should have only flashed stock boot.img
Most likely now you need to read complete thread and follow the unbricking procedures.
Get enough posts, and post in other thread..
Click to expand...
Click to collapse
Thought is was supposed to be system? Also the unbricking guide from Dell pdf has corrupted files. But I will try and do boot and see what happens.
Edit: no change. Flashed boot.img and then did a factory restore. Now it's boots to a black screen, like it's looking for an OS. I guess I really screwed it with the flashing the system.img.gz.
Thanks for the help

P_Link said:
Thought is was supposed to be system? Also the unbricking guide from Dell pdf has corrupted files. But I will try and do boot and see what happens.
Edit: no change. Flashed boot.img and then did a factory restore. Now it's boots to a black screen, like it's looking for an OS. I guess I really screwed it with the flashing the system.img.gz.
Thanks for the help
Click to expand...
Click to collapse
You need to download this .tgz from Dell to unbrick A150:
YTP802A115030-2014-06-23-30.tgz 28-Aug-2014 12:35 755M
http://opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/A150/Unbrick/
When you untar it (tar xfvz YTP802A115030-2014-06-23-30.tgz) you will get a bunch of files:
Code:
images-YTP802A115030/
images-YTP802A115030/oemlogo_8.bin
images-YTP802A115030/P802_flash_device_wifi_only.bat
images-YTP802A115030/oemlogo_7.bin
images-YTP802A115030/recovery.img
images-YTP802A115030/system.img
images-YTP802A115030/boot.img
images-YTP802A115030/dnx_fwr_0005_10CD_PRQ.bin
images-YTP802A115030/droidboot.img
images-YTP802A115030/partition.tbl
images-YTP802A115030/droidboot.img.POS.bin
images-YTP802A115030/dnx_osr_0005_10CD_PRQ.bin
images-YTP802A115030/for_product_ifwi_PRQ.bin
images-YTP802A115030/ifwi_0005_10CD_PRQ.bin
There are some other unbrick files (for A195 I think) that are broken. I emailed Dell about it, but got no reply so far. Just start completely over, following the Unbrick guide. I've done it many times on my Venue 8 3840, and it works fine.
In order for the rooted boot.img to work, you need to end up with your tablet having the IWFI, DNX, and droidboot from the Linux kernel package that Dell provided. You also need the 4.4.4 system.img, which can be obtained by following the unbrick process, and then letting the tablet OTA to 4.4.4. If the unlocked IFWI, DNX, or droidboot are not flashed, then the tablet will not run fastboot, and you'll either get a black screen with a USB symbol on it, or it will boot into recovery.

P_Link said:
OK so I am using file YTP802A115030-2014-06-23-30.tgz that you suggested and it's content with xFSTK Downloader 1.5.1 and using iSocUSB Drivers 1.0.4. Following the Dell guide for bricking . I get to page 3 of http://opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/Doc/OSS_A150&A195.pdf
I get the following error XFSTK-LOG-Windriver Error: 0x20000015. Timeout expirded.
The tab is seen as a target
Thank you
OS 8.1
Click to expand...
Click to collapse
I've seen that many times as well. One of the most frustrating parts for me working with this tablet was that error! The following seemed to work for me, but I figured it out towards the end of my adventure with this device, so I didn't get to try it repeatedly to see if the behavior is consistent:
Note on XFSTK: if you have trouble getting XFSTK to download properly, try:
Turn off the device (hold power button for 10 seconds.)
Press the Start Download button in XFSTK.
With USB cable connected, turn tablet on with Power + Volume Up.
I'm also using Windows 8.1 64-bit (on a Surface Pro 3.) I've tried both the built-in USB port and also each of the ports (USB 2.0 and USB 3.0) on the Surface docking station. The port doesn't seem to matter, nor do the cables. What definitely doesn't help is rebooting your PC, reinstalling the drivers/xFSTK, etc. I tried those things too. The Power+Vol UP was what I tried last time I went through the Unbrick, and it worked, but perhaps it was a coincidence. Please report back if you find that it works for you.
For what it's worth, I tried flashing the boot image on mine again using the one downloaded from the other post, and it worked fine.
Code:
H:\rooted_4.4.4_images>md5sum Dell_Venue_8_3840_rooted_4.4.4_boot.img
2bfefbaa81e78e90d78a5869987ee82f *Dell_Venue_8_3840_rooted_4.4.4_boot.img
H:\rooted_4.4.4_images>fastboot flash boot Dell_Venue_8_3840_rooted_4.4.4_boot.img
target reported max download size of 577456810 bytes
sending 'boot' (9604 KB)...
OKAY [ 1.271s]
writing 'boot'...
OKAY [ 1.447s]
finished. total time: 2.718s
H:\rooted_4.4.4_images>fastboot reboot
rebooting...
finished. total time: 0.516s
H:\rooted_4.4.4_images>adb devices
List of devices attached
Medfield317A5CF8 device
H:\rooted_4.4.4_images>adb shell
[email protected]:/ #

hharte said:
You need to download this .tgz from Dell to unbrick A150:
YTP802A115030-2014-06-23-30.tgz 28-Aug-2014 12:35 755M
http://opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/A150/Unbrick/
When you untar it (tar xfvz YTP802A115030-2014-06-23-30.tgz) you will get a bunch of files:
Code:
images-YTP802A115030/
images-YTP802A115030/oemlogo_8.bin
images-YTP802A115030/P802_flash_device_wifi_only.bat
images-YTP802A115030/oemlogo_7.bin
images-YTP802A115030/recovery.img
images-YTP802A115030/system.img
images-YTP802A115030/boot.img
images-YTP802A115030/dnx_fwr_0005_10CD_PRQ.bin
images-YTP802A115030/droidboot.img
images-YTP802A115030/partition.tbl
images-YTP802A115030/droidboot.img.POS.bin
images-YTP802A115030/dnx_osr_0005_10CD_PRQ.bin
images-YTP802A115030/for_product_ifwi_PRQ.bin
images-YTP802A115030/ifwi_0005_10CD_PRQ.bin
There are some other unbrick files (for A195 I think) that are broken. I emailed Dell about it, but got no reply so far. Just start completely over, following the Unbrick guide. I've done it many times on my Venue 8 3840, and it works fine.
In order for the rooted boot.img to work, you need to end up with your tablet having the IWFI, DNX, and droidboot from the Linux kernel package that Dell provided. You also need the 4.4.4 system.img, which can be obtained by following the unbrick process, and then letting the tablet OTA to 4.4.4. If the unlocked IFWI, DNX, or droidboot are not flashed, then the tablet will not run fastboot, and you'll either get a black screen with a USB symbol on it, or it will boot into recovery.
Click to expand...
Click to collapse
hharte said:
I've seen that many times as well. One of the most frustrating parts for me working with this tablet was that error! The following seemed to work for me, but I figured it out towards the end of my adventure with this device, so I didn't get to try it repeatedly to see if the behavior is consistent:
Note on XFSTK: if you have trouble getting XFSTK to download properly, try:
Turn off the device (hold power button for 10 seconds.)
Press the Start Download button in XFSTK.
With USB cable connected, turn tablet on with Power + Volume Up.
I'm also using Windows 8.1 64-bit (on a Surface Pro 3.) I've tried both the built-in USB port and also each of the ports (USB 2.0 and USB 3.0) on the Surface docking station. The port doesn't seem to matter, nor do the cables. What definitely doesn't help is rebooting your PC, reinstalling the drivers/xFSTK, etc. I tried those things too. The Power+Vol UP was what I tried last time I went through the Unbrick, and it worked, but perhaps it was a coincidence. Please report back if you find that it works for you.
For what it's worth, I tried flashing the boot image on mine again using the one downloaded from the other post, and it worked fine.
Code:
H:\rooted_4.4.4_images>md5sum Dell_Venue_8_3840_rooted_4.4.4_boot.img
2bfefbaa81e78e90d78a5869987ee82f *Dell_Venue_8_3840_rooted_4.4.4_boot.img
H:\rooted_4.4.4_images>fastboot flash boot Dell_Venue_8_3840_rooted_4.4.4_boot.img
target reported max download size of 577456810 bytes
sending 'boot' (9604 KB)...
OKAY [ 1.271s]
writing 'boot'...
OKAY [ 1.447s]
finished. total time: 2.718s
H:\rooted_4.4.4_images>fastboot reboot
rebooting...
finished. total time: 0.516s
H:\rooted_4.4.4_images>adb devices
List of devices attached
Medfield317A5CF8 device
H:\rooted_4.4.4_images>adb shell
[email protected]:/ #
Click to expand...
Click to collapse
Ok making some headway. The Power+Volume up was able to FW and OS Complete it says... However I can not boot. I can enter Droidboot but there is no Fastboot running, even tho it says it is. ADB device is seen.
I have no idea.
Thank you for your time.

P_Link said:
Ok making some headway. The Power+Volume up was able to FW and OS Complete it says... However I can not boot. I can enter Droidboot but there is no Fastboot running, even tho it says it is. ADB device is seen.
I have no idea.
Thank you for your time.
Click to expand...
Click to collapse
I'm pretty sure what's going on is that the driver loaded on the Fastboot device is the ADB driver. To fix this, when the tablet is in Droidboot:
1. open Device Manager (from Windows command prompt, type devmgmt.msc)
2. Find the device (it probably is under Android Devices.)
3. RIght click on the device, choose "Update Driver" and then "Browse My Computer..." and then "Let me pick from a list of device drivers on my computer."
4. You might have to unclick "Show Compatible Hardware"
5. In the Manufacturer section, pick Google or Intel.
6. Under Model, pick "Android Bootloader Interface."
7. Click Next, and then Ok to Ignore scary warnings.
After you get Fastboot running (fastboot devices should show some output) then you can proceed with the rest of the unbricking process, which is basically running a batch file that re-partitions the device, and then writes each of the partition images one by one. After the reboot you will be back to 4.4.2 stock, and you need to let the OTA happen. There should be one large (~200MB+) OTA.
Then you can continue with rooting...

hharte said:
I'm pretty sure what's going on is that the driver loaded on the Fastboot device is the ADB driver. To fix this, when the tablet is in Droidboot:
1. open Device Manager (from Windows command prompt, type devmgmt.msc)
2. Find the device (it probably is under Android Devices.)
3. RIght click on the device, choose "Update Driver" and then "Browse My Computer..." and then "Let me pick from a list of device drivers on my computer."
4. You might have to unclick "Show Compatible Hardware"
5. In the Manufacturer section, pick Google or Intel.
6. Under Model, pick "Android Bootloader Interface."
7. Click Next, and then Ok to Ignore scary warnings.
After you get Fastboot running (fastboot devices should show some output) then you can proceed with the rest of the unbricking process, which is basically running a batch file that re-partitions the device, and then writes each of the partition images one by one. After the reboot you will be back to 4.4.2 stock, and you need to let the OTA happen. There should be one large (~200MB+) OTA.
Then you can continue with rooting...
Click to expand...
Click to collapse
Thanks for all the info. I got the driver loaded with no issues. SO I was able to access Fastboot. Used the files from Dell FTP no go. Just got Intel logo? Any how I read on another post that he had to cobble to together file from the user social-design-concepts post and the files from Dell. That didn't work either but it did bring back the Dell splash screen.
I really hope the development goes further with this tablet. I returned it to Dell got a new one on the way. Thanks again for your help, sorry I couldn't follow directions.

Can someone help me with these -
1)
Where do I download 'droidboot.img'
(for these steps
Go to the directory contains “boot.img” and run these commands
\> fastboot flash boot boot.img
\> fastboot flash fastboot droidboot.img )
2) I have put my Venue 3840 in fastboot mode, and plugged in usb and run fastboot on command prompt. But on fastboot devices command it does not show my dell venue. I have installed all the drivers in the steps 1-4 on the dell reference pdf.
Neole
---------- Post added at 03:31 PM ---------- Previous post was at 03:16 PM ----------
Ok I got the dell venue to show as 'Medfield32715DD2' on fastboot devices command after doing this (thanks to who posted this!) -
1. open Device Manager (from Windows command prompt, type devmgmt.msc)
2. Find the device (it probably is under Android Devices.)
3. RIght click on the device, choose "Update Driver" and then "Browse My Computer..." and then "Let me pick from a list of device drivers on my computer."
4. You might have to unclick "Show Compatible Hardware"
5. In the Manufacturer section, pick Google or Intel.
6. Under Model, pick "Android Bootloader Interface."
7. Click Next, and then Ok to Ignore scary warnings.
Still haven't found droidboot.img - where do I download this?

I managed to find it here -
opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/
Now starting the root process.
Neole
Neole said:
Can someone help me with these -
1)
Still haven't found droidboot.img - where do I download this?
Click to expand...
Click to collapse
---------- Post added at 05:36 PM ---------- Previous post was at 04:50 PM ----------
Oh no! Now I've got the dead android same as posted by OP -
imgur.com/oCR0VqC,r9FmCXd#0
What's the solution??

btw I get a strange USB symbol when I boot in recovery mode (volume down + power button). When I boot normally I get the dead android with red triangle exclamation mark.
Here is the USB icon I see in recovery mode, there is nothing else and fastboot doesnt recognize the Dell Venue -
s29.postimg.org/t789qze07/Dell_Venue3840_Bricked.jpg
(Sorry for weird crop on the pic)
Please advise!!
Neole

I am doing the unbricking on the usb logo. Tablet is getting detected on xFSTK downloader and on Downloading I keep getting the same error as OP -
XFSTK-LOG-Windriver Error: 0x20000015. Timeout expired.
Will try again to see if it resolves later.
---------- Post added at 10:37 PM ---------- Previous post was at 09:58 PM ----------
Hurrah - I got it unbricked again! hharte's method worked -
Turn off the device (hold power button for 10 seconds.)
Press the Start Download button in XFSTK.
With USB cable connected, turn tablet on with Power + Volume Up.
Now to figure out why I couldn't root it in the first place? I'm sure I followed all the instructions correctly.

Neole said:
I am doing the unbricking on the usb logo. Tablet is getting detected on xFSTK downloader and on Downloading I keep getting the same error as OP -
XFSTK-LOG-Windriver Error: 0x20000015. Timeout expired.
Will try again to see if it resolves later.
---------- Post added at 10:37 PM ---------- Previous post was at 09:58 PM ----------
Hurrah - I got it unbricked again! hharte's method worked -
Turn off the device (hold power button for 10 seconds.)
Press the Start Download button in XFSTK.
With USB cable connected, turn tablet on with Power + Volume Up.
Now to figure out why I couldn't root it in the first place? I'm sure I followed all the instructions correctly.
Click to expand...
Click to collapse
Have you tried sdc's lastest method to root with recovery? he changed activation point.

vampirefo - "Have you tried sdc's lastest method to root with recovery? he changed activation point."
No I haven't tried that.. is it for Venue 3840? I couldn't find any more rooting threads for Venue 3840, could you point me to the thread with the instructions?
Thanks!
Neole

Related

Tutorial: Un-Bricking Padfone 2 (and possibly other android devices)

Earlier today I bricked my Padfone 2 by installing 3rd part font. After a reboot to apply the changes, it got to the boot logo but never any further.
I got it up and running again, :victory: and to those out there in same or similar situation, here's a tutorial on what I did:
Before we start, there's a few things you need;
1.1 Latest ADB version (I used 1.0.31) [ATTACHED]
1.2 Latest Fastboot version [ATTACHED]
1.3 CWM Recovery [ATTACHED]
1.4 Latest ASUS USB Drivers (available from ASUS Support site) [ATTACHED]
1.5 Padfone 2 Firmware (available from ASUS Support site)
*** NOTE: For ease of use, place extract and place all of the above to the same folder.
*** NOTE: Inside the Padfone 2 Firmware ZIP file, there's another ZIP file. This is the one we need! The one I used was called "WWE_A68-10.4.15.1-0-ota-user.zip"
*** NOTE: This method does not install CWM Recovery on your phone, it only boots it temporarily.
If you have all of the above, continue to step 2;
2.1 Booting your Padfone 2 into Fastboot mode
2.2 Press and hold Power + Volume up buttons
In Fastboot mode, connect your phone to your computer and launch cmd. Wait for windows to install necessary drivers if needed.
3.1 Navigate your CMD to the folder containing ADB, Fastboot and CWM Recovery (recovery.img)
3.2 In CMD type:
Code:
fastboot boot recovery.img
In the CWM Recovery on your phone, select the option titled "Install ZIP from sideload".
Use the volume keys to navigate and select by pressing the power button.
4.1 In CMD, transfer the Padfone 2 Firmware by typing
Code:
adb sideload [firmware-file-name.zip]
- Example from my case, I wrote:
Code:
adb sideload WWE_A68-10.4.15.1-0-ota-user.zip
4.2 When it is done, you'll be presented with CWM Recovery's screen again, select "Reboot system now".
4.3 CWM Recovery will present you with a warning saying: "ROM may flash stock recovery on boot. Fix?" - Select "NO".
If you are experiencing problems with driver installation, you can fix it manually. If windows installed the drivers correctly, skip this step. To solve this, go to device manager by entering the Start menu, right-click Computer and select “Manage”. Select the Device Manager.
You should see a failed device named A68. Right-click it and select “Update device software”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “Have Disk”
Now browse and navigate to the folder you extracted your ASUS USB Drivers to and select the file named “android_winusb.inf”
Select “ASUS Android ADB Interface” and install.
All done! You should have a working Padfone 2 again!
Please note that you may need to root your phone again.
Please credit if used
/HelmerN

HelmerN said:
Earlier today I bricked my Padfone 2 by installing 3rd part font. After a reboot to apply the changes, it got to the boot logo but never any further.
I got it up and running again, :victory: and to those out there in same or similar situation, here's a tutorial on what I did:
Before we start, there's a few things you need;
1.1 Latest ADB version (I used 1.0.31) [ATTACHED]
1.2 Latest Fastboot version [ATTACHED]
1.3 CWM Recovery [ATTACHED]
1.4 Latest ASUS USB Drivers (available from ASUS Support site) [ATTACHED]
1.5 Padfone 2 Firmware (available from ASUS Support site)
*** NOTE: For ease of use, place extract and place all of the above to the same folder.
*** NOTE: Inside the Padfone 2 Firmware ZIP file, there's another ZIP file. This is the one we need! The one I used was called "WWE_A68-10.4.15.1-0-ota-user.zip"
*** NOTE: This method does not install CWM Recovery on your phone, it only boots it temporarily.
If you have all of the above, continue to step 2;
2.1 Booting your Padfone 2 into Fastboot mode
2.2 Press and hold Power + Volume up buttons
In Fastboot mode, connect your phone to your computer and launch cmd. Wait for windows to install necessary drivers if needed.
3.1 Navigate your CMD to the folder containing ADB, Fastboot and CWM Recovery (recovery.img)
3.2 In CMD type:
Code:
fastboot boot recovery.img
In the CWM Recovery on your phone, select the option titled "Install ZIP from sideload".
Use the volume keys to navigate and select by pressing the power button.
4.1 In CMD, transfer the Padfone 2 Firmware by typing
Code:
adb sideload [firmware-file-name.zip]
- Example from my case, I wrote:
Code:
adb sideload WWE_A68-10.4.15.1-0-ota-user.zip
4.2 When it is done, you'll be presented with CWM Recovery's screen again, select "Reboot system now".
4.3 CWM Recovery will present you with a warning saying: "ROM may flash stock recovery on boot. Fix?" - Select "NO".
If you are experiencing problems with driver installation, you can fix it manually. If windows installed the drivers correctly, skip this step. To solve this, go to device manager by entering the Start menu, right-click Computer and select “Manage”. Select the Device Manager.
You should see a failed device named A68. Right-click it and select “Update device software”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “Have Disk”
Now browse and navigate to the folder you extracted your ASUS USB Drivers to and select the file named “android_winusb.inf”
Select “ASUS Android ADB Interface” and install.
All done! You should have a working Padfone 2 again!
Please note that you may need to root your phone again.
Please credit if used
/HelmerN
Click to expand...
Click to collapse
The f.cking windows not found my phone when try to install drivers windows give my cannot install .....
please tell me what i do to install drivers other drivers or what please help me?
thanks!

I wish I could enter into Fastboot mode.
I have two Padfone 2 bricked (by unknow reason) with QHSUSB_DLOAD error (Qualcomm High Speed USB Download).
the whole case: http://forum.xda-developers.com/showthread.php?t=2220775
Do you have any ideas?

Hi,
I have the same problem like you rafael_mfr .
Is there any solution to unbrick my padfone 2 ?

Bricked?
I have now joined the club
Not sure if it's bricked or not but the phone is stuck on loading (silver Asus with circulating loading) unstopping for more than an hour.
Tried your technique and all other possible ways but no luck any ideas?

charlykayo said:
The f.cking windows not found my phone when try to install drivers windows give my cannot install .....
please tell me what i do to install drivers other drivers or what please help me?
thanks!
Click to expand...
Click to collapse
Have you tried the last step? I mention issues with windows drivers and how to manually install them.

rafael_mfr said:
I wish I could enter into Fastboot mode.
I have two Padfone 2 bricked (by unknow reason) with QHSUSB_DLOAD error (Qualcomm High Speed USB Download).
the whole case: http://forum.xda-developers.com/showthread.php?t=2220775
Do you have any ideas?
Click to expand...
Click to collapse
Tamsabodi said:
Hi,
I have the same problem like you rafael_mfr .
Is there any solution to unbrick my padfone 2 ?
Click to expand...
Click to collapse
As far as I know, the QHSUSB_DLOAD error is hardware related and cannot be fixed by normal means. I believe it requires some special hardware or flash tool or something.
You could try manually installing the Asus USB drivers by following the last step and see if that works?
In any case, the tutorial only fixes software based issues.
Mine got totally bricked some time ago. Somehow the mainboard was fried and needed replacement.
It didn't react in any way when trying to power it on. If i plugged in the charger, it would get pancake-making hot!
Asus dispatched a UPS guy to pick it up and send it for repair. When the mainboard is fried like mine was, they can't tell if it were rooted or not, so they had to repair it.
All in all, I had a great experience with ASUS warranty

droidace said:
I have now joined the club
Not sure if it's bricked or not but the phone is stuck on loading (silver Asus with circulating loading) unstopping for more than an hour.
Tried your technique and all other possible ways but no luck any ideas?
Click to expand...
Click to collapse
Your issue should be fixable!
I'm assuming your bootloader is unlocked?
Was the
Code:
adb sideload WWE_A68-10.4.15.1-0-ota-user.zip
successfull?

HelmerN said:
Your issue should be fixable!
I'm assuming your bootloader is unlocked?
Was the
Code:
adb sideload WWE_A68-10.4.15.1-0-ota-user.zip
successfull?
Click to expand...
Click to collapse
Yes, bootloader is unlocked
Yes, adb sideload is working via CWM but tried it with the latest firmware update (WWE_A68-10.4.17.7-0-ota-user.zip) from asus.com after renaming the file to "WWE.zip" for shorter cmd lines
Anything else needs to be checked?

droidace said:
Yes, bootloader is unlocked
Yes, adb sideload is working via CWM but tried it with the latest firmware update (WWE_A68-10.4.17.7-0-ota-user.zip) from asus.com after renaming the file to "WWE.zip" for shorter cmd lines
Anything else needs to be checked?
Click to expand...
Click to collapse
Did you extract the zip file?
Within the zip file, theres another zip. That's the one you need.
Yo dawg! We heard you like zip's, so we put a zip within your zip, so you can zip while zipping
Click to expand...
Click to collapse

HelmerN said:
Did you extract the zip file?
Within the zip file, theres another zip. That's the one you need.
Click to expand...
Click to collapse
Yeah, I had that covered. it's the final zip level ..

droidace said:
Yeah, I had that covered. it's the final zip level ..
Click to expand...
Click to collapse
Very surprised it didn't work.
Have you tried factory restore through the recovery boot?

HelmerN said:
Very surprised it didn't work.
Have you tried factory restore through the recovery boot?
Click to expand...
Click to collapse
Tried that at the very beginning.
That issue has started after I installed GPS Status - Test and Fix https://play.google.com/store/apps/details?id=com.cochibo.gpsstatus&hl=en as part of getting a better GPS performance I have reset GPS and then Get Xtra data but after restarting, it never loaded the system. I hope this helps identifying the issue
I might try this way as a final try

droidace said:
Tried that at the very beginning.
That issue has started after I installed GPS Status - Test and Fix https://play.google.com/store/apps/details?id=com.cochibo.gpsstatus&hl=en as part of getting a better GPS performance I have reset GPS and then Get Xtra data but after restarting, it never loaded the system. I hope this helps identifying the issue
I might try this way as a final try
Click to expand...
Click to collapse
I wouldn't recommend doing an SKU conversion. There might be (not sure) a slight difference in hardware in the different areas. I know products sold in China sometimes aren't up to spec with the rest of the world in order to keep prices down and sales up, for an example.
So if the voltage settings are a little off in comparison to your hardware, it might get fried.
That being said, your issue is a weird one. It sounds like software malfunction, easily solvable with a reset or sideloading firmware, forcing me to wonder if your device have been flashed with a different SKU or, perhaps, have a hardware malfunction.
For now all I can come up with is; repeat the process. Give it reasonable time to boot up, 10 mins. should be more than enough. If there's still no progress, enter recovery and clear the cache and try booting up again.
Otherwise I'm stumped.
Might be time to consider the RMA option?
A lot of Padfone 2's are born with a eMMC fault - so it could be related?

Fixed, wipe data partition (from stock recovery ONLY) what an intermittent issue

Thanks..... it was wery usefull

There's another way to un-brick.
The first day I received my Padfone 2, after only 6 hours I got it really badly bricked. No button combination would work, all I got was "invalid kernel"
On Modaco there's a thread http://www.modaco.com/topic/365818-padfone-2-invalid-kernel/?p=2191432 that worked very well, even a self-proclaimed noob as myself could finally get it together. It was amazing as I thought I had to send the Phone back to Germany (from Portugal)
For those who prefer the German language: http://www.android-hilfe.de/asus-padfone-2-forum/531509-bricked-invalid-kernel-2.html
credits go to Paul O'brien and manu7irl who posted this solution on MoDaCo and Vakilando on Android-Hilfe who inspired me to give it a second try.

HelmerN said:
Earlier today I bricked my Padfone 2 by installing 3rd part font. After a reboot to apply the changes, it got to the boot logo but never any further.
I got it up and running again, :victory: and to those out there in same or similar situation, here's a tutorial on what I did:
Before we start, there's a few things you need;
1.1 Latest ADB version (I used 1.0.31) [ATTACHED]
1.2 Latest Fastboot version [ATTACHED]
1.3 CWM Recovery [ATTACHED]
1.4 Latest ASUS USB Drivers (available from ASUS Support site) [ATTACHED]
1.5 Padfone 2 Firmware (available from ASUS Support site)
*** NOTE: For ease of use, place extract and place all of the above to the same folder.
*** NOTE: Inside the Padfone 2 Firmware ZIP file, there's another ZIP file. This is the one we need! The one I used was called "WWE_A68-10.4.15.1-0-ota-user.zip"
*** NOTE: This method does not install CWM Recovery on your phone, it only boots it temporarily.
If you have all of the above, continue to step 2;
2.1 Booting your Padfone 2 into Fastboot mode
2.2 Press and hold Power + Volume up buttons
In Fastboot mode, connect your phone to your computer and launch cmd. Wait for windows to install necessary drivers if needed.
3.1 Navigate your CMD to the folder containing ADB, Fastboot and CWM Recovery (recovery.img)
3.2 In CMD type:
Code:
fastboot boot recovery.img
In the CWM Recovery on your phone, select the option titled "Install ZIP from sideload".
Use the volume keys to navigate and select by pressing the power button.
4.1 In CMD, transfer the Padfone 2 Firmware by typing
Code:
adb sideload [firmware-file-name.zip]
- Example from my case, I wrote:
Code:
adb sideload WWE_A68-10.4.15.1-0-ota-user.zip
4.2 When it is done, you'll be presented with CWM Recovery's screen again, select "Reboot system now".
4.3 CWM Recovery will present you with a warning saying: "ROM may flash stock recovery on boot. Fix?" - Select "NO".
If you are experiencing problems with driver installation, you can fix it manually. If windows installed the drivers correctly, skip this step. To solve this, go to device manager by entering the Start menu, right-click Computer and select “Manage”. Select the Device Manager.
You should see a failed device named A68. Right-click it and select “Update device software”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “Have Disk”
Now browse and navigate to the folder you extracted your ASUS USB Drivers to and select the file named “android_winusb.inf”
Select “ASUS Android ADB Interface” and install.
All done! You should have a working Padfone 2 again!
Please note that you may need to root your phone again.
Please credit if used
/HelmerN
Click to expand...
Click to collapse
please helmern , help me!
MY PADFONE 2 is bloked after istalling a rom.
after, I have istalled from sideload (with cwm v.6) the ufficial rom but it ,after rebooting is always bloked on the screen of logo ''asus'' and not rebooting. why ?
this is the log report :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
help me , please!

agent-06 said:
please helmern , help me!
MY PADFONE 2 is bloked after istalling a rom.
after, I have istalled from sideload (with cwm v.6) the ufficial rom but it ,after rebooting is always bloked on the screen of logo ''asus'' and not rebooting. why ?
this is the log report :
View attachment 2575590
help me , please!
Click to expand...
Click to collapse
hi i have the same problem , only asus logo no rebooting.........helpppppppppppppppppp
i tried your solution all ok but bloked on asus logo

famonaco said:
hi i have the same problem , only asus logo no rebooting.........helpppppppppppppppppp
i tried your solution all ok but bloked on asus logo
Click to expand...
Click to collapse
before installing a firmware you have to do all three wipes For three times.
Inviato dal mio PadFone 2 utilizzando Tapatalk

[Q] TF201 stuck at ASUS splash screen after..

So my Transformer Prime is stuck at ASUS logo splash screen..
Please let me explain what I have done to cause this.
0. Using Transformer Prime on the original Android system (4.1??) - I took the following steps to install android kit kat 4.4.?
1. I rooted it then unlocked it
2. I installed the recovery system - http://forum.xda-developers.com/devdb/project/?id=2229#downloads
following the instruction below =>
original thread - http://www.transformerforums.com/forum/transformer-prime-roms/41446-re-install-using-nvflash.html
If you haven't already found a recovery flasH the one found here
Cyanogenmod 11.0 Unofficial TF201 - xda-developers DevDB - http://forum.xda-developers.com/devdb/project/?id=2229#downloads
Place it in your fastboot folder. Open a command prompt in the fastboot folder by right-clicking in the folder and choosing "open command prompt here"
Reboot tablet into fastboot and connect to pc. Then type:
fastboot devices
You should see your tablet listed.
If so type:
fastboot -i 0xb05 flash recovery recovery.img.SOS
You should see a blue progress bar under an Asus logo.
Once done, reboot tablet into recovery and you should be good to go.
Click to expand...
Click to collapse
3. I used the recovery system to successfully install the followings
* cm-11-20131229-UNOFFICIAL-tf201.zip (kit kat android system 4.4?)
* gapps-kk-20131119.zip
4. After this I rebooted the tablet then now it''s stuck at the ASUS screen.
I have found that quite a few people have experienced this... but I'm not very certain of what I need to do so I would appreciate if any of you can help me to resolve this issue. My ultimate goal now is to be able to boot the tablet to a usable state(with apps).
Currently,
* fastboot cannot be done
* can connect to PC in APX(?) mode
* downloaded rom(?) US_epad-user-10.4.2.18.zip from http://www.asus.com/Tablets/Eee_Pad_Transformer_Prime_TF201/HelpDesk_Download/ but I hae no idea how i can use this.
* i have 'nvflash' folder on pc, in the folder I have blob.bin.... I have attached a screenshot of what's in the folder
Thank you in advance.

You have to flash the correct version of TWRP for the bootloader you are on. Flashing any random TWRP without knowing is a sure way to brick the machine.
Please show me the link to the instructions you were following. I don't think you can tell me your exact bootloader version from what you can see so please also tell me where the Tegra logo is on your screen. Bottom center or bottom right ?
Edit. I forgot to say the good news is you have nvflash backups so you should be able to fix it anyway. If you just want to go ahead and try and recover it yourself start here. http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash

flumpster said:
You have to flash the correct version of TWRP for the bootloader you are on. Flashing any random TWRP without knowing is a sure way to brick the machine.
Please show me the link to the instructions you were following. I don't think you can tell me your exact bootloader version from what you can see so please also tell me where the Tegra logo is on your screen. Bottom center or bottom right ?
Edit. I forgot to say the good news is you have nvflash backups so you should be able to fix it anyway. If you just want to go ahead and try and recover it yourself start here. http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Click to expand...
Click to collapse
Hi flumpster, thank you so much for trying to help me.
Initially I followed this tutorial to unlock my TF201 and backed up Blobs and Enabling Nvflash access.
https://matthill.eu/android/transformer-prime-tf201-jellybean-nvflash/
this flatline recovery? was what I had and it did NOT install cm-11-20131229-UNOFFICIAL-tf201.zip (kit kat android system 4.4?)
Then I found this thread to find another user having the same installation error problem - http://www.transformerforums.com/forum/transformer-prime-roms/41446-re-install-using-nvflash.html
In the thread above, I followed a post by a guy named 'mediadriven'' to re-install another recovery(?).
File: recovery.img - http://forum.xda-developers.com/devdb/project/?id=2229#downloads
With the recovery tool, I was able to install
* cm-11-20131229-UNOFFICIAL-tf201.zip (kit kat android system 4.4?) - http://www.mediafire.com/download/xdwpk61crqttmib/cm-11-20131229-UNOFFICIAL-tf201.zip
* gapps-kk-20131119.zip - https://www.androidfilehost.com/?fid=23252070760974567
After the installation, I rebooted the tablet then now it''s stuck at the ASUS screen.
---
You have to flash the correct version of TWRP for the bootloader you are on. Flashing any random TWRP without knowing is a sure way to brick the machine.
Click to expand...
Click to collapse
>> where could I download a correct version of TWRP for the bootloader and how may I install this..?
I don't think you can tell me your exact bootloader version from what you can see so please also tell me where the Tegra logo is on your screen. Bottom center or bottom right ?
Click to expand...
Click to collapse
>> i'm sorry, im not sure which version of bootloader im using. Tegra logo is on bottom right screen. (image attached)
I forgot to say the good news is you have nvflash backups so you should be able to fix it anyway. If you just want to go ahead and try and recover it yourself start here. http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Click to expand...
Click to collapse
Thank you for the link, before posting this thread here I have attempted to follow the thread above to unbrick my tf201. I was able to follow up to step 5 to be in nvflash mode.
I was not able to follow from step 6.. perhaps that is because I do not have these files - blob.EBT, blob.SOS, blob.LNX, and blob.APP
List of files that I have in nvflash is in the picture attached in my first post.
Thank you.

The files you are missing for step 6 are all in a zip file at the bottom of the link I gave you. Here is the direct link.
https://goo.im/devs/craigacgomez/prime/TF201-JB-10.4.2.15-Unblobed.zip/

flumpster said:
The files you are missing for step 6 are all in a zip file at the bottom of the link I gave you. Here is the direct link.
Click to expand...
Click to collapse
thanks flumpster, ill try the guide again with the zip file tonight. Will let you know how it goes!

flumpster said:
The files you are missing for step 6 are all in a zip file at the bottom of the link I gave you. Here is the direct link.
Click to expand...
Click to collapse
so each time i ran a nvflash command it successfully completes then rebooted itself to the Asus splash logo screen.. I have to reboot my device into apx mode then wheelie back into nvflash before being able to go to the next step..
When I ran the last command below it did not seem like it did anything.. output i got from the nvflash was "[resume mode]".
nvflash.exe -r --go
Rebooting the tablet makes the system stuck at ASUS splash logo screen..
I can reboot my device into APX mode.. and can also use nvflash but I may not have been follow the steps in the guide properly as it rebooted itself each time I ran nvflash commands.
What could I do?

jinseiichido said:
so each time i ran a nvflash command it successfully completes then rebooted itself to the Asus splash logo screen.. I have to reboot my device into apx mode then wheelie back into nvflash before being able to go to the next step..
When I ran the last command below it did not seem like it did anything.. output i got from the nvflash was "[resume mode]".
nvflash.exe -r --go
Rebooting the tablet makes the system stuck at ASUS splash logo screen..
I can reboot my device into APX mode.. and can also use nvflash but I may not have been follow the steps in the guide properly as it rebooted itself each time I ran nvflash commands.
What could I do?
Click to expand...
Click to collapse
I'm not sure what you are doing wrong mate. I would do it all again from scratch starting from the beginning of the instructions.
Also while you are on the Asus splash screen try holding down the volume down button and the power button for 10 seconds until it restarts and then keep holding them. Do you end up in the bootloader screen now ?

flumpster said:
I'm not sure what you are doing wrong mate. I would do it all again from scratch starting from the beginning of the instructions.
Also while you are on the Asus splash screen try holding down the volume down button and the power button for 10 seconds until it restarts and then keep holding them. Do you end up in the bootloader screen now ?
Click to expand...
Click to collapse
flumpster, unfortunately it does not show the bootloader screen. posted this problem to - http://forum.xda-developers.com/showpost.php?p=60640712&postcount=211

I'm still needing help to get my tablet working again..
If you could help me to get the tablet working again.. i will donate you $20(US) either paypal or via this forum.
Thank you.

jinseiichido said:
I'm still needing help to get my tablet working again..
If you could help me to get the tablet working again.. i will donate you $20(US) either paypal or via this forum.
Thank you.
Click to expand...
Click to collapse
Unfortunately the money doesn't help, I cannot see what you are doing wrong. Everything I have said should work for you and if I had the machine here I am pretty sure I could get it working in under an hour.
If you was in the UK I would offer to let you send it to me as long as you paid the return postage but from the US that is just way too expensive. The only thing I can advise at this point is to try and find someone on here from the US who is willing to take a look at it for you.
If I had been you I would have tested multiple PCs with the universal drivers and also tried different usb ports (2 and 3) then if all that failed I would have booted off a live linux cd and tried it in there. If that still failed I would have used the script from the end of craigs nvflash post that puts the machines partitions and everything else back to stock but this has to be done in linux also.

Have you solved this problem now ?

In case you haven't, I found a possible solution for the 'stuck at Asus logo problem'
My prime was suffering the same problem; except that hadn't done an nvflash backup. What worked for me was a pressing the of the power and reset button (with a needle) and volume up button (I believe) at the same time. I don't know what combination exactly since I was trying some things with the reset button and boom it worked

Moto E unlocked, but won't get to TWRP screen.

Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA

Download mfastboot and redownload the recovery img

hetor99 said:
Download mfastboot and redownload the recovery img
Click to expand...
Click to collapse
Thanks.
Decided to install it on my desktop. While trying various files, my laptop accidentally got hit with Chromium virus. It looked like all required files were there, but kept having problems with a couple of those sdk files (tools/platform tools).

I'm still getting the following error:
( bootloader) has-slot :recovery: not found
And once again the Android SDK Tools and Android SKD Platform-tools that are under Tools (preview channel) are unchecked. Not sure if they are needed.

Follow the instructions of how to install on the general section

hetor99 said:
Follow the instructions of how to install on the general section
Click to expand...
Click to collapse
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.

L8Show said:
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
Click to expand...
Click to collapse
How to Install TWRP Recovery and Root MOTO E
https://www.youtube.com/watch?v=9Jh-O2LGL3Y

OK, it is done.
Took a couple days with several hours of clicking, and checking settings, and reading and researching, and watching videos, and downloading, and installing/uninstalling, and restarting, but it's now rooted! Way too much time wasted even though it was raining and the gf and I were just watching movies for a lot of it. She kept asking me why I'd waste so much time and remind me I had a perfectly fine iphone nearby. Today I finally got to the point where I had given up. I figured something was screwed up with the phone after that reset on my computer.
Some highlights that may or may not be helpful for the next moto e rooter:
USB debugging was somehow switched to off a few times after I turned it on. Might have been after resetting phone, but who knows exactly.
I set screen to stay while connected via USB.
I removed all the apps I could and took out the sd card.
Kingoroot stuck at 66% many, many times, and then phone would restart. Research showed it may be accessing the wrong ADB instance or something. So I uninstalled SDK, fastboot, Minimal, etc. Anywhere it could have been hiding. Even did a system restore to last week the day I reinstalled windows. Didn't help one bit. Which is to also say... there are a half dozen or more legit options. Try different ones if you are relatively confident you followed directions the 1st 10 times.
Ministro didn't have moto e in their data base.
Finally back to XDA after checking a dozen videos (I have to admit I was completely dumbfounded and was mad at the whole process). I found XDA Kingroot and right away it worked, but it needed permission to allow apps that were not certified or some thing. I can see how people would think this is so easy. If I had started with this, I'd never have had to ask for help here. Btw, was this my problem all along? Did I miss that in the instructions or was it something else possibly? I don't remember if I did that before since it was 3 days ago.
So far I am thoroughly impressed with the this moto e. I paid $40 for it on a whim and now that I can remove a bunch of bloatware and customize it a bit, I think it may be a good gateway into android devices.
Thanks for looking and all your suggestions.

I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.

faheyd said:
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
Click to expand...
Click to collapse
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!

L8Show said:
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
Click to expand...
Click to collapse
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.

-z3r0- said:
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
Click to expand...
Click to collapse
Thanks for that information. I thought I saw adb devices command working in fastboot mode in one of the videos so I thought that was the problem. I thought adb needed to root the phone.
In order of what I've done with the phone so far:
Sent/got codes and unlocked moto e.
Turned on developer options and USB debugging.
Was then unable to get TWRP or the other cw something to work using the command fastboot flash recovery (file name) or fastboot boot... commands.
Gave up and installed Kingroot and everything worked fine.
Decided to try to install TWRP and superSU since kingroot had worked. I read that the phone needed to be flashed back to stock to do this and watched/read a couple of guides. http://forum.xda-developers.com/showthread.php?t=2759495
I used the following named file:
SURNIA_ACG_LTE_5.1_LPI23.29-30_cid9_subsidy-DEFAULT_CFC
The phone was changed back, but data doesn't work. I can't access wifi because as soon as I switch it on, it switches back off. 4G, etc is not working either. So after trying to figure that out I decided to just proceed and put TWRP/superSU on the phone.
I powered off the phone. Powered into fastboot mode connected the phone to my computer.
I opened Minimal fastboot folder and shift/right click to bring up the command prompt.
In the command promt i typed fastboot devices and it shows my phone.
I then type fastboot flash recovery (file name or renamed to recovery or renamed to TWRP or I click the actual file and drag it to the command prompt) and then hit enter.
It says it's doing stuff in so many seconds, but after nothing happens. The phone doesn't reset like some of the videos. If I reset it, it powers on, but not into the TWRP screen.
After that I did more reading and found out that adb doesn't always play nice with windows 8.1 and that you might need to force other drivers to make it work right. I did this next and was going to try all the available options from universal naked driver later, but there were no motorola drivers.
Then I came here and learned something new. ADB devices command doesn't work when the phone is in fastboot mode so that has no effect on installing twrp...
Right now I am considering trying to install the other stock files I have access to:
SURNIA_ACG_LTE_5.1_LPI23.29-20_cid9_subsidy-DEFAULT_CFC (20 instead of 30).
After that I am out of ideas if it's not the adb problem. Might kingroot again and go from there.
Ok after researching, it seems that LTE file may not work on sprint and there was success using the boost file from
http://www.filefactory.com/file/6be...XI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml.zip
(2 hour dl make that 5+ lol)
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'll try that next to get the wifi working and then figure out why it won't root.
Thx!

L8Show said:
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Click to expand...
Click to collapse
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
---------- Post added at 05:30 AM ---------- Previous post was at 05:29 AM ----------
rakeshwipr said:
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
Click to expand...
Click to collapse
and open the command prompt with admin rights

Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.

-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
d
Thanks! The devices shows up when on as ADB and in fastboot too. I had to take a break when the kernel download took 8 hours, but I think I got the file that will work to fix the wifi issue. I can't mess with it til I get home tomorrow, but I will read and follow all advice.
For the previous poster, I did do the admin rights and did rename TWRP file to recovery... I aslo tried many other combinations, but will keep it in mind for all further attempts.
Appreciate the help so far. I almost left it with the kingroot, but it was bugging me that I couldn't get it to go. Hopefully I'll have good new tomorrow.

-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
Device shows up in both instances.
It's stock now and the wifi works. Flashed it back to stock by following Mdkcheatz guide here:
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'm stuck where I was when I first started this thread. I've set my account up as administrator. Developer is enabled and so is USB debugging. I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
I confirmed the connection:
fastboot devices
I try to flash it with the:
fastboot flash recovery recovery.img
It says:
target reported max download size of 268435456 bytes
sending 'recovery' (6928 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.359s]
finished total time: 0.578s
C: |Program Files (x86)\Minial ADB and Fastboot>
I'm running windows 8.1 (64 bit). I read that some people had had problems with windows 8. Kingroot worked through the app store. It has been flashed with various stock kernels and that usually takes a few minutes so I don't think it's doing much in half a second. I'll research a bit more, but I think it just a bad combination of this version phone and windows 8.1.
I started the phone after this last attempt. Are there any files in internal storage that I should look for?

L8Show said:
I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
Click to expand...
Click to collapse
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.

-z3r0- said:
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
Click to expand...
Click to collapse
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.

L8Show said:
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
Click to expand...
Click to collapse
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu

-z3r0- said:
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
I am on v2.65. Should I use this version? I checked root and it's rooted, but I needed to use no bloat app (instead of free titanium) to remove some apps. Is that normal? I thought once rooted and set up, I would have complete control. Some apps seem very invasive so I haven't grabbed many yet. I have some questions about apps, etc., but will probably research and ask in another forum if needed.
Thx again for all the help and pointing out my mistake.

Wileyfox 2 corrupted after update to Android 7.1.2

Updated my phone to Android 7.1.2 today, using the built in updater.
Now when I restart, I get the following on the bootloader: "Your device is corrupt. It can't be trusted and may not work properly"
It still boots normally. But Android Pay doesn't work.
Any suggestions for fixing this?

I can't help, but I can confirm that the same has happened to me so you're not alone...

I had the same problem. I couldn't even start twrp anymore. I fixed it by flashing the full tos118c rom from fastboot. After that I let the ota install. I then reinstalled twrp and flashed magisk to root the phone. Now it boots without dm verity or corrupt message. Even the play store is now certified, so I can install Netflix without problem.
Also you can hide root so you can use Android pay.

WileyFox customer support?
I have the exact same issue.
My device started off by saying:
The dm-verity is not started in enforcing mode and may not work properly
Now after the update, I get the error message saying that the phone is corrupt and will power off if I dont press power within 30 seconds.
I contacted WileyFox when the first issue occurred and was told that I needed to send the phone back. I sent on my details and never heard back.
Ideally I would like to get the phone sorted without flashing a custom rom or recovery.
Has anyone else had issues with their support? Is it just my case they are managing badly, or is it an ongoing thing?

jamesmcd05 said:
I have the exact same issue.
My device started off by saying:
The dm-verity is not started in enforcing mode and may not work properly
Now after the update, I get the error message saying that the phone is corrupt and will power off if I dont press power within 30 seconds.
I contacted WileyFox when the first issue occurred and was told that I needed to send the phone back. I sent on my details and never heard back.
Ideally I would like to get the phone sorted without flashing a custom rom or recovery.
Has anyone else had issues with their support? Is it just my case they are managing badly, or is it an ongoing thing?
Click to expand...
Click to collapse
You can try reflashing using fastboot. That fixed it for me.
Start the phone into fastboot mode.
If you don't have fastboot on your pc download and install this: https://forum.xda-developers.com/showthread.php?t=2317790
Download the fastboot image from https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101
Connect your phone to the pc.
Flash the image using the following command: Fastboot update "path to the update zip"
That fixed the phone for me.
good luck!

RedNas74 said:
You can try reflashing using fastboot. That fixed it for me.
Start the phone into fastboot mode.
If you don't have fastboot on your pc download and install this: https://forum.xda-developers.com/showthread.php?t=2317790
Download the fastboot image from https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101
Connect your phone to the pc.
Flash the image using the following command: Fastboot update "path to the update zip"
That fixed the phone for me.
good luck!
Click to expand...
Click to collapse
Brilliant, thanks.
Didn't realise there were offical wileyFox builds available.
Much appreciated. I will give that a try
:fingers-crossed:
EDIT:
I got an error saying that:
target reported max download size of 535822336 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
Also my phone was OEM locked.
I unlocked the device and tried again, but got the same error.
So I unzipped the contents and manually flashed each img,. which seems to have worked fine
I re-enabled OEM lock and now the phone boots without errors.
Thanks a million

Just wanted to say thank you very much for the thread info.
I also got the error messages, but realised that I was just being a bit hasty. Waiting a further 20 seconds gives a couple of other messages about other .sig files missing, but then the update continues and the flash is completed. The 'corrupted' and 'dm-verity' messages have now gone and the phone appears to be functioning properly.
Hopefully it will now update OTA to the next version and do so without corruption.
Thanks again
David

Wait a minute.
I'm a almost complete newbie but perhaps you guys can help me out.
Like davids-h I also got the errors and after over seven (!) minutes I get:
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished.
What can I do or should I do?
Thanks in advance!

I have the same issue as Razorblattor above - please could someone chime in with any suggestions. Would be appreciated. Thanks

rjl_12345 said:
I have the same issue as Razorblattor above - please could someone chime in with any suggestions. Would be appreciated. Thanks
Click to expand...
Click to collapse
Update: I managed to get the ROM flashed by removing the SD card and SIM. I have no idea why this would have been an issue but it was. I could then flash the ROM. Thanks

I was able to solve this issue with the following steps:
If not installed already install USB drivers (//dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip) and ADB (//dl.google.com/android/repository/platform-tools-latest-windows.zip). Unzip ADB
- enable USB debugging (under Developer options)
- connect phone to Windows machine, open a dos box and type 'adb devices' (you should see your WileyFox)
- enter the command: adb reboot "dm-verity enforcing" (incl. quotes)
Issue solved!

The steps documented by asg1977 have also worked for me.
I had the issue on a Swift2X that was delivered factory standard with a Nougat image. It occured while taking the phone out of its cover, pressing the power button in the process. After that the phone rebooted consistently with the corrupted warning. (Even tough the phone worked fine once past that screen.)

asg1977 said:
I was able to solve this issue with the following steps:
If not installed already install USB drivers (//dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip) and ADB (//dl.google.com/android/repository/platform-tools-latest-windows.zip). Unzip ADB
- enable USB debugging (under Developer options)
- connect phone to Windows machine, open a dos box and type 'adb devices' (you should see your WileyFox)
- enter the command: adb reboot "dm-verity enforcing" (incl. quotes)
Issue solved!
Click to expand...
Click to collapse
Thanks for this, but when I open a command prompt, and type in adb devices, I get a message saying that
'adb' is not recognized as an internal or external command,
operable program or batch file. I have developer options activated and usb mode is switched on and set to mtp devices. I have downloaded the 2 sets of files (USB drivers and ADB, and unzipped them to the desktop. Where am I going wrong?
EDIT - SOLVED IT! The command prompt needs to be opened inside the platform tools folder, whereupon it will find the phone, and the adb reboot "dm-verity enforcing" command will work. Prior to this, I had to revoke usb debugging authorisation between the phone and computer, then reconnect the phone the computer, so the phone could be seen by the computer. Command prompts can be very finicky about how they work, but I got there in the end.

RedNas74 said:
You can try reflashing using fastboot. That fixed it for me.
Start the phone into fastboot mode.
If you don't have fastboot on your pc download and install this: https://forum.xda-developers.com/showthread.php?t=2317790
Download the fastboot image from https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101
Connect your phone to the pc.
Flash the image using the following command: Fastboot update "path to the update zip"
That fixed the phone for me.
good luck!
Click to expand...
Click to collapse
Hi sorry I have the same problem but I am new to all this, could someone send me a link to/write out a step by step instructions on how to do this?
Thanks in advance!
Louise
---------- Post added at 02:33 PM ---------- Previous post was at 02:06 PM ----------
louisew92 said:
Hi sorry I have the same problem but I am new to all this, could someone send me a link to/write out a step by step instructions on how to do this?
Thanks in advance!
Louise
Click to expand...
Click to collapse
Sorted now thanks!

I had the same issue and WF support fixed it for me
I had this issue previously when Wileyfox support was still active and they gave me this PDF file as a solution
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

3LzW said:
I had this issue previously when Wileyfox support was still active and they gave me this PDF file as a solution
Click to expand...
Click to collapse
FTFY:
Something weird about posting links makes me fail posting the correct link: https:// imgur.com/a/NHjGV

asg1977 said:
I was able to solve this issue with the following steps:
If not installed already install USB drivers (//dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip) and ADB (//dl.google.com/android/repository/platform-tools-latest-windows.zip). Unzip ADB
- enable USB debugging (under Developer options)
- connect phone to Windows machine, open a dos box and type 'adb devices' (you should see your WileyFox)
- enter the command: adb reboot "dm-verity enforcing" (incl. quotes)
Issue solved!
Click to expand...
Click to collapse
Thanks from Poland, genius! It works

My phone has developed this problem after I flashed TWRP, I've tried to follow instructions so I can enforce the DM verity reboot in a command line interface but if I select fastboot my phone stays on a load up screen and doesn't change. The only other thing I can access is TWRP, will I be able to use the terminal in that to solve this problem?

asg1977 said:
I was able to solve this issue with the following steps:
If not installed already install USB drivers (//dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip) and ADB (//dl.google.com/android/repository/platform-tools-latest-windows.zip). Unzip ADB
- enable USB debugging (under Developer options)
- connect phone to Windows machine, open a dos box and type 'adb devices' (you should see your WileyFox)
- enter the command: adb reboot "dm-verity enforcing" (incl. quotes)
Issue solved!
Click to expand...
Click to collapse
I know this is old.. but just wanted to say I wasn't able to do this from my laptop via adb - but used the terminal via TWRP and it worked.
Thanks a lot from Wales

Any help on Pioneer XDP-300R bootloop ?

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.

Better Mobile App

welcome