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.
Related
So I was trying to set up the old OneX+ with a new ROM.
Phone already had TWRP 2.7.1, unlocked.
When in Fastboot USB my system does not recognize the phone, it is simply listed as "Fastboot" under "Other Devices" in Device manager... I can't set the drivers manually as I did last time.
The main reason why I need Fastboot working is because I keep getting "error executing updater binary in zip" when trying to install a new rom, I read somewhere TWRP 2.3.3 may be the solution, would appreciate if anyone could confirm this as well.
sens1r said:
So I was trying to set up the old OneX+ with a new ROM.
Phone already had TWRP 2.7.1, unlocked.
When in Fastboot USB my system does not recognize the phone, it is simply listed as "Fastboot" under "Other Devices" in Device manager... I can't set the drivers manually as I did last time.
The main reason why I need Fastboot working is because I keep getting "error executing updater binary in zip" when trying to install a new rom, I read somewhere TWRP 2.3.3 may be the solution, would appreciate if anyone could confirm this as well.
Click to expand...
Click to collapse
Sometimes I am having this problem too. Try to replug your usb when the phone is in Fastboot mode. It works for me.
Hello, I'm a little bit new to all this, so any help and detailed instructions are very very helpfull.
So I have Gigabyte GSmart Aku A1 device (MediaTek 6589), I don't know if it's bricked or what but apparently is not working quite well.
When I turn on my phone, it just loads and loads and loads and nothing happens (waited for about 4-5 hours), that was starting to happen after I somehow installed CWM on my device with some tutorial, CWM worked for the first time and after next reboot, it disappeared and stock recovery came back (and the problem with infinite loading screen - only showing logo).
I have ADB drivers installed, SDK aswell, tried to put stock firmware (got it from official site) and in like 1/4 of installation it says:
Code:
symlink: some symlinks failed
After that, I tried to install few versions that I downloaded from that official site, but same error again and again. (I tried to install with SD card and with ADB too. ADB is only working when I go to "apply update from ADB" in recovery. I have also used 2 different types of SD cards.)
That didn't worked either, so I got to some russian forum, and using google translator I downloaded 5-6 types of custom ROM's / Firmwares. That didn't worked either, one time when installing one of those ROM's - it said something about signature..
After that I was trying to install those ROM's with ADB and with SD Cards aswell, but turns out that every single time I get error saying: "Installation aborted.".
I have ofcourse tried to wipe data/factory and to wipe cache too, but nothing helps..
Also, when I'm in ADB console, when I type any command besides adb sideload or adb devices, I get error saying: "error: closed". I cant get into fastboot with adb console.
I really don't know what to do anymore, so any help would be very very appreciated. Thank you for your help in advance, if you need any videos, pictures or something, just tell me.
Edit: When I go to "wipe data/factory reset" in recovery, it says: "Mount /data error.".
BUMP!
BUMP^2!
luuksa said:
BUMP^2!
Click to expand...
Click to collapse
i would look for stock rom in form of full mtkdroidtools backup and preloader drivers for your mtk chipset
and flash it using flashtool (it uses preloader[you can determine if it's available/undamaged by turning phone off and opening device manager on pc and plugging phone to pc if there will be a flash in device manager before the charging starts it will flash ])
hi, i work helping my classmates when they stuck on their phones... ok, i'm apologize for my bad english but here is the thing, i now have one Huawei G610-U00 and the phone say "Encryption unsuccessful", i notice that him install the twrp recovery so i try flashing a new recovery using fastboot and the fastboot only say "sending 'recovery'" and nothing else happens(i left all the night, the phone only discharge the battery,), make a search on google and find info related and try them, try using sp flash, try installing a new zip, even try a force-update but when press the vol + and - and the power key, the phone go to recovery, also in the bootloader mode it only say "recovery_status:UPDATED" nothing else, the "adb devices" comand shows '0123456789ABCDEF' the "fastboot devices" show "mt6589_phone_720pv2", please need help i use the adb comand and try to format but only receive error messages, this is that i get on the recovery:
https://drive.google.com/file/d/0B_NnURitRMg-ZUZCUC1WaXVIQkdPSGRCaE90NUFUVUZodnBr/view?usp=sharing
https://drive.google.com/file/d/0B_NnURitRMg-RUN5ZjhWbklDUVRNeThFbXRMLUdfUUNoVkFJ/view?usp=sharing
https://drive.google.com/file/d/0B_NnURitRMg-ZGxqYlhMeTBhbVVXbERHWXNoN0xXYlgxTFdV/view?usp=sharing
https://drive.google.com/file/d/0B_NnURitRMg-bVJRODB1N3hXckxNbnhMZFBpajdhekxhaUc4/view?usp=sharing
Click to expand...
Click to collapse
goluisgerardo said:
hi, i work helping my classmates when they stuck on their phones... ok, i'm apologize for my bad english but here is the thing, i now have one Huawei G610-U00 and the phone say "Encryption unsuccessful", i notice that him install the twrp recovery so i try flashing a new recovery using fastboot and the fastboot only say "sending 'recovery'" and nothing else happens(i left all the night, the phone only discharge the battery,), make a search on google and find info related and try them, try using sp flash, try installing a new zip, even try a force-update but when press the vol + and - and the power key, the phone go to recovery, also in the bootloader mode it only say "recovery_status:UPDATED" nothing else, the "adb devices" comand shows '0123456789ABCDEF' the "fastboot devices" show "mt6589_phone_720pv2", please need help i use the adb comand and try to format but only receive error messages, this is that i get on the recovery:
Click to expand...
Click to collapse
I have a similar problem with Huawei Y320-U030, MTK 6572, Android 4.2.2 with many malware infections. Almost all applications keep crashing, Factory Reset from Settings does not work, but I can do it from the recovery and it seems to complete successfully but when the devices boots, all user applications and files are there. I have flashed it with stock ROM and backup ROM from an other working similar phone, the flashing process completed successfully but when the device boots all user files and applications are untouched, even after formatting the whole flash with Sp flashtool, Volcano box and Miracle box! An applications called DU Speed Booster is set as device administrator with a pattern lock which cannot be deactivated. Uninstalling the imo application makes the device reboot and hang on Huawei logo untill the battery is pulled out. I can't install any new apk or root the device even using PC. Music, videos, and photos in the internal memory can be copied with a computer but cannot be deleted. Formatting the internal memory with a PC seems successful but all files on the device are intact. Very interesting case indeed.
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