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
Related
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
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.
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
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
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
Get TWRP and root after updating to Nougat
This method worked for me, but be aware, it might not work for your specific device. in a worst-case scenario, you'll brick your device - proceed at your own risk!
For devices with UNLOCKED BOOTLOADER! This guide does not show you how to unlock the bootloader
BIG thanks to @tamahouse02, @bkores, @S0wL and @tron1 for the help they gave me when trying to do this on my own device. This post is just a compilation of everything we tested over the old questions/answers post.
How To:
Set up axon7tool and download TWRP
Download axon7tool from here. Thanks tennear for the awesome tool
Download TWRP for ailsa_ii, newest one available. I used 3.1.0.0
Download Zadig and throw the exe somewhere
I asume that you already have adb installed, if not install it with 15 seconds installer
Put axon7tool on your adb folder, rename it to axon7tool.exe
Put TWRP image on the same folder, rename it to recovery.img (you NEED TO BE ABLE TO SEE THE FILE EXTENSION! Google how to enable that)
Duplicate the recovery.img, rename it recovery.bin, keep it in the same place
Connect your phone, enable USB debugging, open CMD and run adb reboot edl
Open Device Manager once your phone looks like it's off. You should see a Qualcomm HS-USB QDLoader 9008 under Ports - COM & LPT, uninstall it AND TICK DELETE DRIVER SOFTWARE TOO and hold the three buttons of your phone (vol buttons and power) for quite a lot of time, until you see that the device manager list refreshes. If Windows attempts to install the driver cancel it at once, repeat the process if it did install it (it appears as a Qualcomm thing again). After holding the 3 buttons you should see an unidentified device named QUSB_BULK
After you have the QUSB_BULK device fire up Zadig and Install the driver.
Flash TWRP using axon7tool
Hold the 3 buttons of your phone again until device manager refreshes
Open CMD on your adb folder (go to the folder, SHIFT+right click anywhere, open command window here)
run axon7tool -r recovery gpt boot
Leave CMD open. Go to the folder where the tool is and make a folder named backups or whatever, put all the backups there (recovery_backup.bin for example)
You should have made a recovery.img and recovery.bin there before. Check that you left them there, just to be sure
Finally, on the CMD window, run axon7tool -w recovery. If it fails try holding the three buttons, opening cmd again and trying this step again. otherwise post your error here
If it succeeds disconnect your usb cable from the phone BEFORE THE COUNTDOWN ENDS, then hold the power button for like an eternity until the phone reboots. If you don't do this your TWRP will be replaced by the stock recovery. you only have to do the previous step again in that case, don't worry.
Either while the phone is booting or with adb after it gets to system, get to the recovery and test if it boots. Congrats if it does!
Install SuperSU
You probably know how to do this if you came this far. If you don't:
Download SuperSU 2.79 from somewhere on the internet
Get to TWRP
Flash SuperSU
Avoid the inherent nervous breakdown that the initial bootloop causes (in layman's terms, don't freak out, let it do its thing)
Done
Get Fastboot
Download this ZIP (thanks @sToRm1nG) and put it in the root of your phone's storage
Go to TWRP and flash the ZIP
Boot system and adb reboot edl
Now we need to replace the Zadig driver, sorry you'll find QUSB_BULK under USB devices (bottom of the list in English), uninstall and check Delete driver software too
Hold the 3 keys
Windows might attempt to install the driver. Leave it, hopefully it will. You need to get Qualcomm HS-USB QDLoader 9008. If it appears as an unknown device google for the driver (just google Qualcomm HS-USB QDLoader 9008 driver and you'll get it) and install it, then hold the 3 buttons and check if the QDLoader 9008 appears under Ports COM&LPT
Download MiFlash from here, and the fastboot package from here
Unpack the fastboot package somewhere, be careful not to unpack it like a folder with another one inside, but rather one folder directly with all the stuff inside
Open MiFlash and select the folder that you unpacked
Select Refresh, then your device should appear. if it doesn't then you didn't reload EDL or you didn't install the Qualcomm drivers, simply do that again. If it appears go ahead and choose Flash
Reboot and try if it worked, by selecting Fastboot from the 5 sec menu or using adb once you're booted
All done. I'm not a developer of any kind, so I'm afraid i won't be able to help with specific errors. But most simple errors you could have are described here, so you should have little trouble doing the procedure.
Hope the best of luck to y'all while doing this
I just tested unfortunately with the much less easy to read original problem thread that described process works fine! Thanks!
Thanks for the Guide!
My Axon 7 (G-Modell - Nougat 7.1.1) is located in the EDL and is under Device Manager as
"Qualcomm HS-USB QDLoader 9008" detected, but MiFlash does not recognize it. The latest drivers from Qualcomm are installed and I use the original cable from ZTE, but it does not want to be recognized ;-(
Thank you man!I'm already Rooted in Nougat 7.0 in my A2017G..... But AdAway can't write the host file, do you have the same issue?
No idea, I never use AdAway. BTW can you cut down the quote a little bit? A lot of people complain about the huge quotes
jorgex said:
Thank you man!I'm already Rooted in Nougat 7.0 in my A2017G..... But AdAway can't write the host file, do you have the same issue?
Click to expand...
Click to collapse
Download any terminal emulator app and execute:
Code:
su
then
Code:
reboot disemmcwp
it seems that i soft bricked my device.. after i flashed TWRP my A2017G only shows me the Bootscreen.. what to do now?
4ert said:
it seems that i soft bricked my device.. after i flashed TWRP my A2017G only shows me the Bootscreen.. what to do now?
Click to expand...
Click to collapse
Did you try to get to TWRP? Does it show the BL unlocked screen, or just the boot logo?
Otherwise try to get to fastboot however you can, then flash TWRP again, or you can try getting to EDL and restoring the backups that you hopefully made. I have no idea how the DFU mode thing is, but I would do some research on that. I'm no dev
Thanks for this guide saved my day.
do i need an unlocked bootloader for this to work?
DarkShadowSwE said:
do i need an unlocked bootloader for this to work?
Click to expand...
Click to collapse
I assume you do. Try the method in here. I have no idea if that will work for Android 7.1.1 though, so I hope you still have android 6
Please help, I have the same problem as logimowl:
My Axon 7 (G-Modell - Nougat 7.1.1) is located in the EDL and is under Device Manager as
"Qualcomm HS-USB QDLoader 9008" detected, but MiFlash does not recognize it. The latest drivers from Qualcomm are installed and I use the original cable from ZTE, but it does not want to be recognized
@icaros1530 Huh I've just installed 7.1.1 official today, so I have to do the process again. I've just opened MiFlash and it detects stuff nicely. The device appears as COM5 on MiFlash and the driver is under Ports (COM & LPT) with the name Qualcomm HS-USB QDLoader 9008 (COM5)
Choose an username... said:
@icaros1530 Huh I've just installed 7.1.1 official today, so I have to do the process again. I've just opened MiFlash and it detects stuff nicely. Look
{
"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"
}
Click to expand...
Click to collapse
Thanks for checking and posting the screenie. I've been on the issue since yesterday now and found a suggestion to try on a different computer, so I tried again and it worked on my win10 notebook. So issue is insofar solved as my smartphone is now running 7.1.1 and rooted and all. Why miflash just can't connect on my win10 pc.. I have no clue. I've rebooted device and pc tons of time with different drivers, even trying the old root methods, used zadig whatever. Everything looks the way it should - but some minor thing hiding somewhere just won't let it work.
td;dr: if miflash can't connect try different computer..
---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------
bkores said:
Download any terminal emulator app and execute:
Code:
su
then
Code:
reboot disemmcwp
Click to expand...
Click to collapse
That doesn't work for me. The command reboots the device, but Adaway keeps saying host files couldn't be copied.
SOLVED: for 7.1.1. we seem to need the systemless version of adaway. I picked up version 3.2 from here and it works perfectly: https://forum.xda-developers.com/showthread.php?t=2190753
@icaros1530 lol I'm gonna add that to the OP (try different computers if it doesn't work)
All these programs are extremely nitpicky it seems!
And I uploaded 2 pictures, but only one showed up, so I just deleted them and added some text. That's why i edited, i just wanted to make that clear
Thanks dude! Clear and simple instructions, got TWRP and root running on my A2017G 7.1.1
Anyone get the 'can't receive hello packet' when flashing?
lesterp said:
Anyone get the 'can't receive hello packet' when flashing?
Click to expand...
Click to collapse
flashing what? with miflash?
Choose an username... said:
flashing what? with miflash?
Click to expand...
Click to collapse
Yes using Miflash
A few reboots of phone and laptop and it flashed.
Hi there,
Having an issue rooting this phone.
rmx2202_11_A.25
At the moment ive got to a point where ive got it setup with adb and i put in " adb reboot fastboot ". I then boot into the fast boot ( ive seen in places people suggesting putting in " adb reboot bootloader " however in that mode my pc cant see my phone as a fastboot or adb device so ive given up on that atm )
Everythign seems good im in a mode called fastbootd and the phone is listed as a Fastboot device. However when i type in " fastboot flasthing unlocked ( also tried fastboot flashing unlocked critical ( with and without _ between words ) also tried a few other i get the error:
"FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed"
Cant get any further than this. I did wonder if this command is actually wrong and there is a hidden command for this function
ive done adb help which shows this command and a list of other commands however not many of them seem to work for some reason.
additional info
. usb debugging is enabled and the oem unlock setting is on.
. i've installed android studio and im using the adp tools from that.
. ive installed the google usb drivers from the android studios.
. ive also installed specific usb drivers for my phone ( or so i think )
. ive installed the testing app which i used get into the bootloader originally
Ive already tried
. Many but not all the app based ways of rooting. Unfortunately every one i have tried so far ..... the phone has stopped me installing it due to it being a rooting app. I tried installaing an app to clone the app which ive seen online however this didnt seem to wor
. Ive tried kingo root on the Pc but it gets stuck on the part where it says to enable usb debugging.
Any help would be amazing !
Thank you
i had lots of issues trying to do this.
are you
A) in fastbootd - you need to use the deeptest.apk to install twrp
B) did you open up powershell, I was trying to use cmd as that's what i had used before, but wouldn't do it until it was done through powershell.
unparalleled82 said:
i had lots of issues trying to do this.
are you
A) in fastbootd - you need to use the deeptest.apk to install twrp
B) did you open up powershell, I was trying to use cmd as that's what i had used before, but wouldn't do it until it was done through powershell.
Click to expand...
Click to collapse
Hi Unparalleled82,
So i think i was actually using "adb reboot bootloader " instead of the app at times so ive just tried it using the app however it still doesnt come up as a fastboot device. When i put in the command " fastboot flashing unlocked " i just get " waiting for any device " for ever.
Few things im wondering do you have exacly the same phone as me RealmeGT 5G rmx2202_11_A.25. Its good to know you have done it and the way you did it. Because mines not working the same way ( assuming the models are the same ) im thinking now its a driver issue perhaps .
So when im just doing adb sideload or something when the phone is booted into the OS i dont have the yellow triangles however in this fastboot mode i see this...
{
"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"
}
Which does indicated a driver issue however when i try to manually install the correct drivers windows tells me its already has the best driver. ( im browsing to the folder where ive downloaded the drivers here )
Ive tried installing them through the legacy hardware option which does install them but phone still doesnt show up in fastboot devices.
Ive also installed the driver using android studios ... you can see google usb drivers ticked.
Ive also googled how to stop windows from automatically installing drivers from windows update then uninstalled my device .. plugged it back in ... then installed them. However thinking now perhaps i should uninstall ... then install the drivers before plugging in the phone ? any ideas ?
Some more info this has reminded me of. Ive tried a different usb cable, a different usb port ( both usb 2.0 ) and a different computer already.
As for the powershell I'm certain i'm using it not the cmd line. I'm holding shift in the correct folder then right click, then open the power shell window.
Any more help would be amazing. Im going to have a look more into fastboot driver problems
I know you said you'd changed your cables, but that's another one of the issues i faced.
The phone would show just like yours, but wouldn't show in fastboot. I changed for a different one and then it actually worked. You won't get anywhere until within powershell it shows under the command
adb devices
unparalleled82 said:
I know you said you'd changed your cables, but that's another one of the issues i faced.
The phone would show just like yours, but wouldn't show in fastboot. I changed for a different one and then it actually worked. You won't get anywhere until within powershell it shows under the command
adb devices
Click to expand...
Click to collapse
Ill try another cable now for sure see what happens. About the powershell im confused what you mean sorry. Im definitely in the power shell.... the phone lists as an adb device ... when its not in fastboot mode that is ... its just it wont list as a fastboot device in fastboot mode.
Piefrag said:
Ill try another cable now for sure see what happens. About the powershell im confused what you mean sorry. Im definitely in the power shell.... the phone lists as an adb device ... when its not in fastboot mode that is ... its just it wont list as a fastboot device in fastboot mode.
Click to expand...
Click to collapse
sorry, what i mean is, mine showed in adb but not in fastboot until i changed for a better cable
unparalleled82 said:
sorry, what i mean is, mine showed in adb but not in fastboot until i changed for
Click to expand...
Click to collapse
Ahh got you now. So ive tried the cable sent with the phone and now 2 other cables and all of them have the same issue so im thinking its not the cable atm.
Ive seen on youtube a method for rooting it from anotehr phone.... i have no idea if it works but ive bought a usb c too usb c cable to give it a try at least !
Thinking now i may buy another usb A too usb C cable of good quality too make absolute sure its not the cable messing it up.
Piefrag said:
Hi there,
Having an issue rooting this phone.
rmx2202_11_A.25
At the moment ive got to a point where ive got it setup with adb and i put in " adb reboot fastboot ". I then boot into the fast boot ( ive seen in places people suggesting putting in " adb reboot bootloader " however in that mode my pc cant see my phone as a fastboot or adb device so ive given up on that atm )
Everythign seems good im in a mode called fastbootd and the phone is listed as a Fastboot device. However when i type in " fastboot flasthing unlocked ( also tried fastboot flashing unlocked critical ( with and without _ between words ) also tried a few other i get the error:
"FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed"
Cant get any further than this. I did wonder if this command is actually wrong and there is a hidden command for this function
ive done adb help which shows this command and a list of other commands however not many of them seem to work for some reason.
additional info
. usb debugging is enabled and the oem unlock setting is on.
. i've installed android studio and im using the adp tools from that.
. ive installed the google usb drivers from the android studios.
. ive also installed specific usb drivers for my phone ( or so i think )
. ive installed the testing app which i used get into the bootloader originally
Ive already tried
. Many but not all the app based ways of rooting. Unfortunately every one i have tried so far ..... the phone has stopped me installing it due to it being a rooting app. I tried installaing an app to clone the app which ive seen online however this didnt seem to wor
. Ive tried kingo root on the Pc but it gets stuck on the part where it says to enable usb debugging.
Any help would be amazing !
Thank you
Click to expand...
Click to collapse
did you use deep app and press "start the in-depth test" because i forgot to do and i spent 2 days to understand whats the problem
grown_man said:
did you use deep app and press "start the in-depth test" because i forgot to do and i spent 2 days to understand whats the problem
Click to expand...
Click to collapse
Yes i did but thank you. Ive done that and it boots into the fastboot mode. Problem is my phone doesn't list as a fastboot device when in fastboot mode.
Piefrag said:
Yes i did but thank you. Ive done that and it boots into the fastboot mode. Problem is my phone doesn't list as a fastboot device when in fastboot mode.
Click to expand...
Click to collapse
another solution mighte be to try https://forum.xda-developers.com/t/rmx2202-realme-gt-5g-ui2-0-ui3-0-all-root.4377165/ link - one click root. theres their own usb drivers installation. its in chinese but theres only one place to click for installation of drivers
grown_man said:
another solution mighte be to try https://forum.xda-developers.com/t/rmx2202-realme-gt-5g-ui2-0-ui3-0-all-root.4377165/ link - one click root. theres their own usb drivers installation. its in chinese but theres only one place to click for installation of drivers
Click to expand...
Click to collapse
Thats it ! Thank you so much
Hello all, I've been trying to install /e/ os GSI on my Redmi Note 11S. I already unlocked the bootloader.
Whenever i tried flashing system.img, (with boot.img patched manually via fastboot, not via a custom recovery), the phone would only boot fastboot. So I tried installing this custom recovery, and patch boot.img from there, but that still wouldn't work (though the recovery at least worked). So I tried installing the stock ROM, and try something else.
I went with latest fastboot EEA image and ran flash_all.sh (worked last time I tried), but this time I got an error (something about partition preloader not found). So I restarted the phone after which it got stuck in this bootloop. Can't boot into fastboot, nor recovery. Instead, the phone keeps flashing the mi logo on and off every 5 seconds. fastboot on my Linux install can't detect the phone. My Windows 10 install can't find it either, though it plays the "device connected" sound followed by the "device disconnected" sound shortly after. I can't turn the phone off either. Windows 10 USB drivers worked, or at least when I was unlocking the bootloader, so I don't think the issue is there. Any idea how to fix this?
Thank you in advance
Edit: Typos. Also I noticed that it only plays the "device connected" and "disconnected" sounds on Windows 10 only when i hold down the power and vol- buttons.
UPDATE: This tool can at least detect the phone, though I do get this error afterwards:
{
"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"
}
UPDATE: Managed to get FASTBOOT back, thanks to this kind stranger (system is still unbootable).
UPDATE: IT'S ALIVE! Did a quick install_all.sh on the stock ROM, and it's working again! Thank you all for helping me resolve this problem
no idea
Normally you use flashall.bat and not .sh, try using flashall.bat and hopefully you'll get out of the bootloop.
Try following my "how to fix bootloop" guide again, atleast till step 4 when you get the fastboot mode back up again.
warhead1721972 said:
Normally you use flashall.bat and not .sh, try using flashall.bat and hopefully you'll get out of the bootloop.
Try following my "how to fix bootloop" guide again, atleast till step 4 when you get the fastboot mode back up again.
Click to expand...
Click to collapse
Could you send a link to the guide please? The only guide I could find on your profile is the one with the rooting, which is among the first guides I tried and it was the one to get me into this situation. Note that in your guide, it appears that you can at least get to the FASTBOOT screen, which I can't. My phone just stays on the logo for 5 seconds before rebooting, and no matter which buttons I press or hold, I can't get it to go to the FASTBOOT screen.
Also, what's the difference between flash_all.bat, and flash_all.sh, aside of one being for Linux and the other for Windows?
UPDATE: This tool can at least detect the phone, though I do get this error afterwards:
kritomas said:
Could you send a link to the guide please? The only guide I could find on your profile is the one with the rooting, which is among the first guides I tried and it was the one to get me into this situation. Note that in your guide, it appears that you can at least get to the FASTBOOT screen, which I can't. My phone just stays on the logo for 5 seconds before rebooting, and no matter which buttons I press or hold, I can't get it to go to the FASTBOOT screen.
Also, what's the difference between flash_all.bat, and flash_all.sh, aside of one being for Linux and the other for Windows?
Click to expand...
Click to collapse
Press and hold all the 3 buttons, vol +, vol - and power button at the same time, till you see the phone switched off for a few seconds.
Then press the power and vol - button to get to the fastboot mode.
About the flashall.bat, I completely forgot that you were using Linux my bad.
Also sometimes some drivers don't work well in Linux try using windows.
Did you follow the guide which was at the end of this?
warhead1721972 said:
Press and hold all the 3 buttons, vol +, vol - and power button at the same time, till you see the phone switched off for a few seconds.
Then press the power and vol - button to get to the fastboot mode.
About the flashall.bat, I completely forgot that you were using Linux my bad.
Also sometimes some drivers don't work well in Linux try using windows.
Did you follow the guide which was at the end of this?
Click to expand...
Click to collapse
Yes, that's the one, and it won't go into fastboot.
Isn't /e/ Murena GSI just android 10? I am pretty sure it won't work. I had the same problem, but I fixed it by installing stock ROM..
And that /e/ GSI is not actively developed and not even in beta stage (not usable at most cases)
Don't use SP Flash tool for full flash this phone seriously, Sp flash tool will make your phone stuck in recovery miui and show Nvdata Corrupted even you choose download only mode.
for now try to use mtkclient to flash boot.img only to both side A&B.
move your boot.img to mtk client folder
open cmd on that folder
type this command:
Code:
python mtk w boot_a,boot_b boot.img,boot.img
and try turn on your phone.
if still can't boot try to flash one by one img from your firmware
I has your same problem. Just hold the vol- for more than your usually Need and should boot into fastboot and than you flash with flashall.bat
I've sucessfully restore my phone and work as normal.
soutaminori said:
Don't use SP Flash tool for full flash this phone seriously, Sp flash tool will make your phone stuck in recovery miui and show Nvdata Corrupted even you choose download only mode.
for now try to use mtkclient to flash boot.img only to both side A&B.
move your boot.img to mtk client folder
open cmd on that folder
type this command:
Code:
python mtk w boot_a,boot_b boot.img,boot.img
and try turn on your phone.
if still can't boot try to flash one by one img from your firmware
Click to expand...
Click to collapse
Thank you so much, it worked!!!
I think. It's now at least on the FASTBOOT screen, which is progress. And the MIUI recovery is now back as well. While the system is still unbootable, I think I can take it from here. Thank you
Hypeka said:
I has your same problem. Just hold the vol- for more than your usually Need and should boot into fastboot and than you flash with flashall.bat
I've sucessfully restore my phone and work as normal.
Click to expand...
Click to collapse
That's the first thing I tried, and no luck. But I fixed it now (I think).
Very welcome, Glad to hear that
Note for everyone:
Backup this partition it's very important.
nvcfg.img, nvdata.img, nvram.img, persist.img, proinfo.img, protect1.img, protect2.img, md1img.img
Thats all partition about imei, security and network configuration for ur device. CMIW.
mtkclient also can do that,
and it's the clue:
Code:
python mtk r nvcfg,nvdata,nvram,persist,proinfo,protect1,protect2,md1img nvcfg.img,nvdata.img,nvram.img,persist.img,proinfo.img,protect1.img,protect2.img,md1img.img
Check ur mtk client folder, now you got the back up.
u can also use this Partitions Backup & Restore this tool don,t need PC for backup and restore, but i'm not really sure can be work perfectly. i just try for boot partition and its worked.
cheeerrss
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
alzhuks said:
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
Click to expand...
Click to collapse
i can't see mtk client log. but maybe driver problem or try to unlock BL again with THIS TOOL
alzhuks said:
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
Click to expand...
Click to collapse
I myself did it with the terminal and on Linux. I didn't use the GUI, so I can't help with that. Could you send a higher res picture of the terminal please? We can't really see anything.
If you're doing this on Windows, then my guess is a driver issue (I did have to install a special driver for Windows to work with Fastboot, could be that mtk needs it too).
Hi All,
I unbricked my phone by using fresh release of mtkclient (https://github.com/bkerler/mtkclient).