I managed to brick my ME375CL in my attempt to root it, it only shows the "Intel Inside" logo when I boot it up.
After much driver install/reinstall and cursing at my computer, I managed to get it to be recognized in Intel Phone Flash Tool.
I've read the instructions on doing custom flashes in blank phone mode for other tablets, but for the life of me, I can't figure out which file is supposed to go in which field.
I would greatly appreciate any insight into this that anyone can provide.
I already have the firmware downloaded.
This is where I am at:
{
"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"
}
This is the list of files I have to work with from the firmware download:
Thanks in advance!!!
The link below may be your best bet to reload the system and root it. I would recommend reading the entire thread first.
https://forum.xda-developers.com/memo-pad-7/help/official-rom-att-asus-memo-pad-7-lte-t3554127
johnkirchner said:
The link below may be your best bet to reload the system and root it. I would recommend reading the entire thread first.
https://forum.xda-developers.com/memo-pad-7/help/official-rom-att-asus-memo-pad-7-lte-t3554127
Click to expand...
Click to collapse
Thanks for the reply. I've already read through that post and attempted the steps within. The problem is that I followed those steps and they failed, now it can only be recognized as an Intel SoC by my computer, so ADB, fastboot commands and Asus Flash Tool will not work.
The only programs I've gotten to recognize the tablet is Intel's Phone Flash Tool and Flash Tool Lite.
If you haven't yet, try using the boot, system and recovery images from the firmware you downloaded in the android section of the flash tool and see what happens.
johnkirchner said:
If you haven't yet, try using the boot, system and recovery images from the firmware you downloaded in the android section of the flash tool and see what happens.
Click to expand...
Click to collapse
I've tried all kinds of combinations in this software, but it always fails at either the IFWI step or gives me this error:
10/08/17 14:03:09.468 INFO : Port 5/1/1: Rebooting in Provisonning OS (current state = UNKNOWN_STATUS)
10/08/17 14:03:09.468 INFO : Port 5/1/1: Cannot Reboot android device, status is UNKNOWN_STATUS
Based on the reading I've done in other threads, the only way to correct this is through a firmware flash in blankphone mode, but it won't accept any of the IFWI files that I have found for this tablet.
I appreciate you trying to help, but I can't do what you are suggesting when it's not even being detected as an Android device. Fastboot commands will not work because there's nothing on the tablet for ADB to make a connection to.
Here's what happens when I try:
Here is what my tablet is doing:
When it's detected by Intel Phone Flash Tool, it usually has a blank screen. Otherwise, it just shows that Intel logo for about 15 seconds, reboots and then does it again, endlessly.
Oh, I forgot to mention that Asus support was kind enough to offer a repair or replacement for $155, since it's out of warranty. I'm hoping for a much cheaper option.
I have never seen the intel logo on mine? Have you tried booting the tablet in to fastboot mode by shutting it down and then turn it on by holding the volume up button and the power button? If you can get to fastboot mode, you should be able to use adb commands. Unfortunately, i am not familiar with the flash software you are using.
Related
Hi!
First i want to apologize for my english and if i made a mistake posting a new thread.
I own an ASUS Zenfone GO (ZB452KG) and i tried to root it, now it's bricked it.
The phone it opens and get stuck on the bootloader. The device is seen by fastboot, but i can't flash anything, it get stuck on writting...
The original firmware for device don't contain recovery.img, only boot.img, any suggestion to flash a recovery to use adb sideload to unbrick my phone?
{
"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"
}
anyone?
up
Hello , see here for your Problem ;
https://boycracked.com/tag/unbrick-asus-zenfone-go-zc500tg/?_e_pi_=7,PAGE_ID10,9943662066
If you still wanna root then , see here
http://forum.xda-developers.com/android/help/asus-zenfone-zc500tg-root-request-t3282861
try this
arahmatharh.blogspot. /2016/09/unbrick-asus-zenfone-go-x014d-bootloop.html
completly this space .com
thank you for your help, but my model is an MSM device, not a processor powerd by intel
Search guides by chipset here https://boycracked.com/flashing/
Sent from my Redmi Note 2 using Tapatalk
Asus ZB452KG on Qualcomm HS-USB QDLoader 9008
Does anyone know if this phone can be revived through QPST Software, is powered by a MSM8212 Snapdragon 200, i searched the raw firmware for this phone, but no success.
asus zenfone go x014d can't enter to recovery mode
hello, anyone who can help me,
i use asus zenfone go x014d, i try to flash twrp recovery via rashr aplication from playstore, and then my phone can't enter to twrp or stock recovery again, only asus logo that shown,
but my phon still can booting to OS normaly
i have try to flash my recovery with adb tool and put command "adb devices" it show my device,
boot i can't flash my phone with adb because i never get to enter recovery, fastboot, or bootloader mode, because it always only asus logo that shown
please help me
Sorry for the thread bumping, but I was wondering if it would be possible to root this device (ZB452KG) at the moment. I found ASUS official firmware in case of brick, but I don't know if it would be useful: https://www.asus.com/support/Download/39/2/0/13/QE1YCzvNxiwct6Y7/32/
I have not found any ROM for the devide, but it would be possible to adapt some of the Zenfone 2 to this one?
Thanks in advance!
I have the same problem and still not ok until now.
Friend I'm with the same problem and with the same android device, somehow managed to solve the problem ..? If by chance you can help me..?
Marcos Andrebrbrbr said:
Friend I'm with the same problem and with the same android device, somehow managed to solve the problem ..? If by chance you can help me..?
Click to expand...
Click to collapse
here fixed problem
https://arahmatharh.blogspot.co.id/2016/09/unbrick-asus-zenfone-go-x014d-bootloop.html?m=1
or pm me
Failed
arahmath2010 said:
arahmatharh.blogspot. /2016/09/unbrick-asus-zenfone-go-x014d-bootloop.html
completly this space .com
Click to expand...
Click to collapse
i try to follow steps on that site, but my phone getting worse, before i try those steps i still can see the battery meter while charging, but after follow those steps my phone really dead.
Just download it's latest firmware from ASUS official web, put that zip file to sd card and install it from recovery mode. It's works well without pc.
Ok, so got my brand new shiny Oneplus 3T yesterday after waiting aged for it to come in.
Using it for a bit, noticed an OTA update to nougat came out (about 900mb) which downloaded in the background.
Triggered the upgrade, now the phone won't boot. I'm also having trouble installing any recovery roms on to it, because I was never intending to root the phone in the first place, and as a result didn't unlock the bootloader using the phone interface when it was on.
So now, it appears I'm stuck! My phone won't accept any side-load roms, (fails), full roms don't read (cannot open file) and fastboot won't unlock the bootloader (Not allowed)
....um.. not having a clue what I'm doing here....help???
{
"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"
}
try going to stock oxygen recovery. wipe data and cache there. see if it boots.
try the unbricking thread too.
if all else fail, call OP customer service.
let us know what happens.
To fix it - see "[UNBRICK] Unbrick Tutorial For The OnePlus 3T!!!!!!!! by Harris K". You have to download his two files onto a laptop or desktop computer and install a qualcomm driver (one of the files). The qualcomm driver will open a serial port into the phone's chipset. The other file will download a stock system, recovery, and fastboot to your phone through the qualcomm serial port. Harris is a genius, buy him a beer. This will fix the following problems.
1) It sounds like the OTA patch screwed up your /system where it doesn't even try to boot. You can still boot into /recovery and /fastboot but just not into /system. Since the phone is still "locked" (flashing prohibited) you cannot flash anything to fix it.
2) dm-verity does not allow any changes to /system. dm-verity checks a hash of hashes of /system. If the hash check fails when you boot /system, dm-verity will "brick" your phone (by design) leaving you with a black screen.
The OTA updates the system and downloads a hash key corresponding to that version. After the OTA, everyone has to end up with exactly the same system in order to pass the dm-verity check.
When you enable flashing (called "unlocking the bootloader") dm-verity will wipe /data to prevent someone from flashing a non-stock recovery to access your data.
infamousvincci said:
try going to stock oxygen recovery. wipe data and cache there. see if it boots.
try the unbricking thread too.
if all else fail, call OP customer service.
let us know what happens.
Click to expand...
Click to collapse
Ok, so went to the unbricking thread. The tool worked! I'm back up and running
bunburyist said:
Ok, so went to the unbricking thread. The tool worked! I'm back up and running
Click to expand...
Click to collapse
I deserve a thank you button haha
So I bought my sister a oneplus 3t and after 3 days she told me that the phone had died on her and was charging but wasn't booting up. I took the phone off her and tried using OnePlus' recovery to wipe everything hoping that would fix it. It didn't. Now the phone won't boot up at all. It won't even go into a bootloop. No lights, no anything. It's completely dead. Using the msmdownload tool gives a Sahara communication failed error and I've currently tried everything. Any idea about what I can do?
NotAbdShahid said:
So I bought my sister a oneplus 3t and after 3 days she told me that the phone had died on her and was charging but wasn't booting up. I took the phone off her and tried using OnePlus' recovery to wipe everything hoping that would fix it. It didn't. Now the phone won't boot up at all. It won't even go into a bootloop. No lights, no anything. It's completely dead. Using the msmdownload tool gives a Sahara communication failed error and I've currently tried everything. Any idea about what I can do?
Click to expand...
Click to collapse
Please use the search function before posting here. There are plenty of circumstances where the issue you've described has happened.
thes3usa said:
Please use the search function before posting here. There are plenty of circumstances where the issue you've described has happened.
Click to expand...
Click to collapse
Except that I have and I've not found a solution to the sahara communication failed problem. I've tried different computers, usb ports etc. Still gets stuck at Sahara Communication failed.
ashokmor007 said:
Click to expand...
Click to collapse
Thanks but I've tried this and it still gets stuck at the same flippin error.
Download the current adb ... use the original cable ... there was a process done with cmd as well as signing the certificate in win10, have you done these?
[Oneplu 3t] md5 checksum failed:system and recovery failed
My Oneplus 3T(with android 8.0.0) suddenly turn off and it wouldn't boot or other option, i didn't ever rooted, it was new and updated. I tried to go to recovery, tried a hard boot hold the power button for 30s, connected to pc, and giving a charge... it just stayed dead... so i did a find the OnePlus3 Unbrick Tool, did find the phone on the tool and i run... after that it boot in a cycle where appear the 1+ logo and them the md5 checksum with the system and recovery failed
{
"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"
}
it does that loop, and now i can enter fastboot but can do nothing than going to that cycle and power off
phone apear in the device manager as "Qualcomm HS-USB QDLoader 9008(COM3)"
and using the tool again, goes to a error saying "Sahara Communication Failed£ Please try again after power off phone" and already tried what it said..
please help me, what can i do to boot my device?
PS: I dont know how to put images on the thread...
This method is actually dangerous. Do not try this unless you have a good reason to do so
This method erases IMEI. Backup EFS with official or enhanced TWRP. Do not use any other TWRP as these might not backup EFS correctly and you will lose IMEI
Only use this as a last resort if everything else fails to revive your device.
First open the download tool. I will assume you at least know how to use it in the default upgrade mode
Press the verify button. The unbrick tool will freeze for a bit. Wait until it shows something like 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"
}
After that close the verification window. An SMT download mode option will be unlocked
Yes, red signifies danger. Don't ask
Now press start
You'll see this box
The password is te123
Warnings: type the password exactly as it is. Do not make typos
Select your exact storage size
If you do not do this correctly you'll worsen the situation
Hit ok and the download will start
When the download completes you'll see this screen:
Disconnect your phone. Now exit the program
You might see this message but if it says download complete like in the screenshot above it is safe to press yes
Your device will not auto reboot like it did in the standard download mode. You'll have to press and hold the power button to force a reboot
Boot oxygenos fully and immediately use TWRP to restore your EFS backup
If you get an NV backup warning first restore EFS and then follow the steps given here https://forums.oneplus.com/threads/nv-backup-warning.474643/
I had a person who badly messed up his bootloader. The unbrick tool in upgrade mode didn't help. SMT fixed the issue and thankfully he had an EFS backup so the device was back to normal
Hi, meat I know where is the link to this download tool?
kakrona said:
Hi, meat I know where is the link to this download tool?
Click to expand...
Click to collapse
HERE
Um, hello guys, has anyone been able to unlock bootloader of a T-Mobile OP after SMT download?
Cuz I couldn't as it's giving me an error when flashing unlock_token.bin that says something like "Verify error (3:-2)".
If anyone had experience please report, thx in advance.
anupritaisno1 said:
I had a person who badly messed up his bootloader. The unbrick tool in upgrade mode didn't help. SMT fixed the issue and thankfully he had an EFS backup so the device was back to normal
Click to expand...
Click to collapse
How did you get SMT mode to work?
I have a Nokia 8 model TA-1052 (this is NB1, correct?). It has a locked bootloader and is running Android 9.
I understand the HMD service for unlocking the booloader is no longer available and the only option now is using a Hikari's website.
Before I try Hikari's method I want to make sure that fastboot is working (I understand it is required?).
With the phone connected, the command "adb devices" show the phone listed but any fastboot command seems to not being able to find the phone (e.g. "fastboot devices" returns nothing).
Am I missing anything?
Thank you.
Assuming you are on Windows what does device manager show when you put the phone into fastboot mode?
Obviously you need a working driver for fastboot mode which is separate from the adb driver - how did you install the drivers and which ones did you use?
dt_matthews said:
Assuming you are on Windows what does device manager show when you put the phone into fastboot mode?
Obviously you need a working driver for fastboot mode which is separate from the adb driver - how did you install the drivers and which ones did you use?
Click to expand...
Click to collapse
I don't have any specific Nokia drivers installed. The only USB driver showing (that seem to be related) is "ADB Interface".
I know that for some people the Nokia driver comes on the phone but mine isn't. Where can I get the driver from?
EDIT: in download mode the Win10 Device Manager shows an unknown "Android" device under other devices
There is a free unlock method with a tutorial on how to unlock: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
emufan4568 said:
There is a free unlock method with a tutorial on how to unlock: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
Click to expand...
Click to collapse
Thanks that worked
emufan4568 said:
There is a free unlock method with a tutorial on how to unlock: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
Click to expand...
Click to collapse
This is an essential part of unlocking the bootloader.
emufan4568 said:
There is a free unlock method with a tutorial on how to unlock: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
Click to expand...
Click to collapse
i just unlocked my phone with this tool and somehow it's back to android 8.1 oreo, is that the normal behavior?
Hi, i used the methode in the link above but now my phone is stuck on the Nokia logo and won't boot to OS.
I can let the batterij drain and power it on but then i get this message in the picture.
Manually getting it into download mode is impossible (holding combo keys volume down and power looks like that doesn't work)
{
"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"
}
Some idea how to fix this? Luckely its not my daily driver but a testdevice.
I have it working again, let battery fully drain, then i could get into download mode (holding vol- while plugging usb) then I could run the tool again (had to request new OTP) and now it just boot normally