first I rooted my device following this http://en.miui.com/thread-30617-1-1.html
then I started super SU and selected normal.
then I opened GLtools i downloaded from here http://forum.xda-developers.com/ ... tools-1-29-t2828630
I installed the GLtools apk and opened it, it asked me to select TEX(DE)coder and install, I did that, super SU asked for root permission, I granted. Mipad rebooted, I opened GLtools nothing changed, it still asks me to install texdecoder, weird, so I installed that again and rebooted and now mipad is bricked and stuck at the MI logo.
I can go into fastboot, however when I tried to use mi pc suite or miflash they do not detect the device so I cant flash fastboot.
when in fastboot device manager shows "android phone fastboot" and it says no drivers are installed for this device, I tried installing drivers like adb driver and fastboot driver etc but it doesnt help.
I am able to boot up the device by using system two, but I need to unbrick system one in case system two gets screwed up.
when in system two, device manager shows android composite device and mi pad and says drivers are up to date. however I still cant anything in fastboot.
I have tried installing android SDK to flash from command prompt but again it doesnt detect hte device and is stuck on waiting for device.
Similar Issue
Without installing TWRP or CWM , I Selected TWRP/CWM in Supersu Binary Installation. Now my MI Pad is stuck at a blank screen
Any help with rebooting the device and flash it
Intall from fastboot
Related
Hello,
I am having a big issue with my Sony Xperia Z2 Tablet. I tried to install a new rom on it and I am stuck in the recovery step.
I achieved to unlock the phone, install the fastboot drivers and flash the boot of my device. I can access to the CWM-based Recovery v6.0.5.1 menu but I just can't put the new rom in my /sdcard/xx directory.
I've tried to use the "adb push cm-11-....-windy.zip /sdcard/0/" command line, but I receive the message: "error: device not found".
I then check the command "adb devices" and indeed the device is not listed even though the device is connected. I then tried to reboot the device (after wiping the data/factory reset, cache partition and dalvyk cache, but my tab is not rebooting on anything. I have nothing but the wave background. Once the device got at that stage, the "adb devices" commande shows the following message: CB51xxxxxx unauthorized. It looks like I have a driver problem or something similar, but I tried to install different drivers and nothing worked so far.
So from there, I am lost, I can't boot my system with the original rom and I can't transfer any new rom in the memory to install a new one.
I would appreciate it a lot if anyone could give me some leads on how I could transfer the new rom on my device or at least recover the original sony firmware so that I can use my tablet again.
Thank you for your answers and time
P.S. I also tried the slideloader option, but since it seems to work on the adb program, it's not working either.
Solved
¨Djyinks said:
Hello,
I am having a big issue with my Sony Xperia Z2 Tablet. I tried to install a new rom on it and I am stuck in the recovery step.
I achieved to unlock the phone, install the fastboot drivers and flash the boot of my device. I can access to the CWM-based Recovery v6.0.5.1 menu but I just can't put the new rom in my /sdcard/xx directory.
I've tried to use the "adb push cm-11-....-windy.zip /sdcard/0/" command line, but I receive the message: "error: device not found".
I then check the command "adb devices" and indeed the device is not listed even though the device is connected. I then tried to reboot the device (after wiping the data/factory reset, cache partition and dalvyk cache, but my tab is not rebooting on anything. I have nothing but the wave background. Once the device got at that stage, the "adb devices" commande shows the following message: CB51xxxxxx unauthorized. It looks like I have a driver problem or something similar, but I tried to install different drivers and nothing worked so far.
So from there, I am lost, I can't boot my system with the original rom and I can't transfer any new rom in the memory to install a new one.
I would appreciate it a lot if anyone could give me some leads on how I could transfer the new rom on my device or at least recover the original sony firmware so that I can use my tablet again.
Thank you for your answers and time
P.S. I also tried the slideloader option, but since it seems to work on the adb program, it's not working either.
Click to expand...
Click to collapse
I found a solution, I flashed my tablet with flashtool and a working ftf file. Then I could have my tablet running the original sony rom and finally I could transfer the cyanogen rom into the tab. Everything is running fine now.
I was upgrading the current Stock rom on my ZTE Nubia Z5s Mini, I went through the recovery mode to load the new rom and got a message saying that the rom installed correctly, I rebooted the device and now its stuck at the MIUI logo or if I try to load the recovery mode I get the Nubia logo just to load back to the miui logo again. I got the rom from the MIUI site its v5.
I've left the phone for over an hour hoping it was just loading up but no change, the phone heats up and even has a charger screen when plugged in.
Anyway to get back into the recovery mode to load the original rom again or any other way of fixing this? help :crying:
I've no idea how to help you with this but I'm bumping the thread because I know how you feel.
Sent from my HUAWEI Y536A1
I'm trying to flush the rom by using adb but with an issue, even thou my device is recognized as Nubia Z5s Mini in device manager it still gives a driver error "these have been installed" and in cmd adb it does not see the device.
Update : Got drivers for install from Clockwordmod website but it will only accept the drivers if I set the phone as a modem in device manager when installing them, still not recognized by adb using CMD.
Solved driver issue and qusb_download issue, ADB drivers are done through all drives in device manager pointing to the Google USB drivers and select adb interface then run CMD from within the Google SDK program folder in platform-tools to read the device.
Now using emmc but need to generate EMMCBLD.HEX & 7x30_msimage.mbn if anyone can help, I can enter adb using recovery mode but blocked from making changes in fastboot mode, currently in download mode which can see a drive H but need the two files to proceed any further.
I had TWRP installed and all was good. Then I tried an OTA update. Update failed and now I can't get into recovery or fastboot. When I try it stops at the 1+ logo with Fastboot Mode written under the logo. This happens if I try Volum Up + power button or adb reboot-bootloader. Device is listed with ADB but won't show up for fastboot.
How do I get back to stock recovery and get the update installed?
Thanks!
Is fastboot installed properly on your PC?
Drivers?
If not and you get it working, you can use fastboot to flash a new recovery. Otherwise read ahead.
Does your phone boot? Is it rooted?
If so, you can try to flash a new recovery via tools like FlashFire, Flashify, Rashr, etc.
If none of those work for you, you can try the un-bricking methods.
I've had my Oneplus 2 hardbrick 3 times on me so far. The solution was to put the phone into a Qualcomm QHUSB_BULK mode, installing unsigned drivers in Windows, and using Chinese software to push recovery files to your phone.
For my first two hard bricks (My phone wasn't responding to anything - it would just show up in the device manager when plugged into the PC). I was able to write the stock recovery and boot files onto my phone by using Method 1 from this OnePlus Forums thread: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/.
I was then able to boot to recovery and dirty flash my OS without any data loss this way.
The last hard brick was much worse and required me to completely reinstall everything on my phone via one of the other methods (I used this link: http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449 and ended up with H2OS, which I then replaced with OOS 3.1.0) - if it comes to that I would recommend checking out the other methods in the OnePlus Forum link below to hopefully avoid going through H2OS - but if not, this one worked.
Also, for updates: You'll need to to reflash (dirty flash) your rom first (this is to unroot/undo any modifications you made to the system, otherwise the OTA will fail) and then flash the OTA. You should be able to use TWRP for this.
Thanks for the reply. Got fastboot working on a different computer.
Phone boots just fine. Not rooted. Just can't access recovery mode or install updates
I tried loading stock recovery (as per this thread) with no change. Thinking I'll have to treat it like it's bricked. Would rather not have to wipe phone though, but doesn't look like I have much choice .
For the past two days I had faced the issue of connecting the device in fastboot mode. Mobile is working fine, loaded with latest firmware OTA updates from OnePlus.
I would like to install TWRP on my mobile but the device is getting detected in the fastboot mode. Tried various steps, reinstalled adb & fastboot as well as OnePlus drivers nothing works. However my mobile is being detected in the adb mode. If I run the command adb devices, it displays my mobile serial number but in fastboot it just sits at the waiting for the device screen.
After a lot of googling, xda search & Oneplus forums search, nothing found. Then I tried reinstalling the adb interface drivers manually, where I have noticed that Win10 installed the latest drivers adb drivers updated in the month of Sep16. Here I have selected the older version driver which was released in the year 2014 and installed it successfully. I run the fastboot devices command again Voila... It worked. no restart, no rebooting the phone. Immediately worked.
Lesson learnt : - Always do not use latest drivers, sometimes try the older drivers if something is not working in your phone.
CrazyArjun said:
For the past two days I had faced the issue of connecting the device in fastboot mode. Mobile is working fine, loaded with latest firmware OTA updates from OnePlus.
I would like to install TWRP on my mobile but the device is getting detected in the fastboot mode. Tried various steps, reinstalled adb & fastboot as well as OnePlus drivers nothing works. However my mobile is being detected in the adb mode. If I run the command adb devices, it displays my mobile serial number but in fastboot it just sits at the waiting for the device screen.
After a lot of googling, xda search & Oneplus forums search, nothing found. Then I tried reinstalling the adb interface drivers manually, where I have noticed that Win10 installed the latest drivers adb drivers updated in the month of Sep16. Here I have selected the older version driver which was released in the year 2014 and installed it successfully. I run the fastboot devices command again Voila... It worked. no restart, no rebooting the phone. Immediately worked.
Lesson learnt : - Always do not use latest drivers, sometimes try the older drivers if something is not working in your phone.
Click to expand...
Click to collapse
can you share those drivers,,facing same issue actually
Yesterday I tried to flash a a new rom on my Xperia Z2 (unlocked bootloader).
From TWRP I did an advanced wipe and selected basically everything except my mircoSD (because it has the new files).
After a long time of waiting I tried to flash the ZIP file and it gave me an error. I thought this had to do with the wipe so I decided to reboot my phone.
As you can imagine, it got stuck on the Sony logo (because system would be empty).
From this moment I couldn't do anything with my phone, except from the tool Emma.
I now have some clean installation of Sony their Android 6.0.1 for the Z2 (23.5.A.0.570) but Im unable to flash TWRP through fastboot.
The command adb devices shows my phone, fastboot devices gives an empty response.
When I restart to the bootloader from adb and try to flash TWRP I get the message "< waiting for device >".
I tried on three different PCs including a clean install of Windows with all kind of different drivers, yet I cant get fastboot to work.
Am I stuck with this unrooted version of Android now or do you guys have any suggestions for me?
Thanks in advance!
Install drivers correctly
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
As I said I've tried all kind of different drivers (Android tools, Sony drivers and flahstool drivers). So for me it's hard to tell what I'm doing wrong.
My computer notices the phone (if I hold volume up and attach the charger), it just doesn't show up under fastboot devices.
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
PaulusE said:
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
Click to expand...
Click to collapse
Manually boot into recovery by booting up your device normally and when you see a violet LED, press vol+.
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Ur device's bootloader still unlocked?
T0B3R said:
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Click to expand...
Click to collapse
You should flash China factory rom, if you can.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com