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.
`Dear Admin,
Hi my Name is Zaki.... i am using HTC Rezound which i purchased in U.A.E
After installing whatsapp i got continious restart problem so i downloaded stock firmware of ICS version. all was good but by mistake i clear internal storage in fastboot mode. and after that i am unable to get into TWRP Recovery mode, it is showing phone with with arrow circle and after few second it converted into phone with triangle (attached screens 2 and 3) please explain me with links how to get TWRP again. and the links for TWRP versions i am not sure which is ok.
Please Reply.
syedzakiabidi said:
`Dear Admin,
Hi my Name is Zaki.... i am using HTC Rezound which i purchased in U.A.E
After installing whatsapp i got continious restart problem so i downloaded stock firmware of ICS version. all was good but by mistake i clear internal storage in fastboot mode. and after that i am unable to get into TWRP Recovery mode, it is showing phone with with arrow circle and after few second it converted into phone with triangle (attached screens 2 and 3) please explain me with links how to get TWRP again. and the links for TWRP versions i am not sure which is ok.
Please Reply.
Click to expand...
Click to collapse
You can't access TWRP because you over-wrote it with the factory RUU firmware image, it isn't there anymore...
Download TWRP image from TWRP official site at https://dl.twrp.me/vigor/ or Flyhalf's build at http://forum.xda-developers.com/showthread.php?t=1902381
Either one is good... then start fastboot, connect usb and flash recovery with the command:
fastboot flash recovery <path/filename of TWRP IMG file>
give it a minute or so, reboot into Hboot and start TWRP.
im having a similar issue but my computer always says waiting for device in command prompt. I have all the drivers installed and the phone says "usb fastboot" or "fastboot usb" (cant recall what order those 2 words are in LoL)
youdoofus said:
im having a similar issue but my computer always says waiting for device in command prompt. I have all the drivers installed and the phone says "usb fastboot" or "fastboot usb" (cant recall what order those 2 words are in LoL)
Click to expand...
Click to collapse
You probably have a driver issue then... Install HTC Sync, connect the phone, then disconnect it, remove HTC Sync and it should work. If that doesn't work, try a different USB port.
Honestly, I switched to Linux a long time ago... I don't have driver issues. If you were running Linux, even a live or USB key distro, you would access it easily.
acejavelin said:
You probably have a driver issue then... Install HTC Sync, connect the phone, then disconnect it, remove HTC Sync and it should work. If that doesn't work, try a different USB port.
Honestly, I switched to Linux a long time ago... I don't have driver issues. If you were running Linux, even a live or USB key distro, you would access it easily.
Click to expand...
Click to collapse
fair point, and i do have ubuntu (of differing flavor dates) on 3 of my machines, so i might just do that. Thanks!! Ill also try the goofy htcsynch (which i forgot about, as im a Sammy guy now) Thanks again!!
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+.
I read much forum here, but I can't figure it out going to Indian or Chinese stock Rom...
Has the X829 an encrypted partition?
I read about TWRP update.zjp and recovery.zip
What is difference?
How to backup full system, so I can restore it when something go wrong?
Is there a clear guide for X829 for updating to Indian/Chinese Rom?
TWRP has a update/recovery zip, what does it does?
Must the x829 rooted for updating to Indian/Chinese Rom?
Thank you very much!
Bobenjanneke said:
How to backup full system, so I can restore it when something go wrong?
Is there a clear guide for X829 for updating to Indian/Chinese Rom?
Click to expand...
Click to collapse
Here
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
Bobenjanneke said:
Must the x829 rooted for updating to Indian/Chinese Rom?
Click to expand...
Click to collapse
No.
Me was told, that the X820 only has to rename a Rom to update.zip?
The guide for the **X829** , do I have to follow it every time when updating, or only 1 time, and every next time is renaming to update.zip enough?
Bobenjanneke said:
Me was told, that the X820 only has to rename a Rom to update.zip?
The guide for the **X829** , do I have to follow it every time when updating, or only 1 time, and every next time is renaming to update.zip enough?
Click to expand...
Click to collapse
Whenever you going to update official rom manually, you need to rename it 'update.zip'.
X829, x820, x821 etc...all are same device.
Bobenjanneke said:
Me was told, that the X820 only has to rename a Rom to update.zip?
The guide for the **X829** , do I have to follow it every time when updating, or only 1 time, and every next time is renaming to update.zip enough?
Click to expand...
Click to collapse
No, only one time to move from Vendor rom (the one comes with phone ), then you can normally update it OTA or local.
Bobenjanneke said:
I read much forum here, but I can't figure it out going to Indian or Chinese stock Rom...
Has the X829 an encrypted partition?
I read about TWRP update.zjp and recovery.zip
What is difference?
How to backup full system, so I can restore it when something go wrong?
Is there a clear guide for X829 for updating to Indian/Chinese Rom?
TWRP has a update/recovery zip, what does it does?
Must the x829 rooted for updating to Indian/Chinese Rom?
Thank you very much!
Click to expand...
Click to collapse
I think install TWRP is the easiest way. I bought X829 few weeks ago, installed TWRP and backup the system that come with the phone and can flash any custom rom. I did try flashed Official Indian 5.8.019S, China 5.9.020S,5.9.023S. You can flash any official stock rom with TWRP I tested it worked fine.
I don't find much different between the roms except Chinese rom have some Chinese apps and don't have Google service/Player store but can download and install after rom is installed.
For backup normally there is system image in internal storage maybe it's the system/rom that come with the phone. I have not try to restore this system image though I not sure its only install the rom or wipe internal storage too.
---------- Post added at 05:29 AM ---------- Previous post was at 05:28 AM ----------
Note I installed TWRP 3.0.2 from official website. Try this one if other version don't work.
Hi,
I just started with ADB.
In "cmd", when I enter "ADB usb" it answers "null"..
When I enter "ADB devices" it answers "listof devices attached" with nothing else...
In ezplorer, is Le Max 2 showed under the hdd's...
Who can help?
-----------
I tried it, when plugging in the USB port, selecting "USB media device" and "charger only" with USB debugging checked on...
At me, ADB is installed automatically in C:\adb so I am working from that path....
Bobenjanneke said:
Hi,
I just started with ADB.
In "cmd", when I enter "ADB usb" it answers "null"..
When I enter "ADB devices" it answers "listof devices attached" with nothing else...
In ezplorer, is Le Max 2 showed under the hdd's...
Who can help?
-----------
I tried it, when plugging in the USB port, selecting "USB media device" and "charger only" with USB debugging checked on...
At me, ADB is installed automatically in C:\adb so I am working from that path....
Click to expand...
Click to collapse
it is Driver issue, go here and follow the instructions
AhmadSant said:
it is Driver issue, go here and follow the instructions
Click to expand...
Click to collapse
Thank you! That worked!
I only checked the "Google usb driver" , everything else I unchecked...
But when I run ADB usb, $adb_vendor_keys is not set...
ADB reboot bootloader gives same message, both are talking about ADB kill server?
When I command ADB kill server, and run ADB usb, it says
*Daemon not running, starting it etc etc"
I have Daemon tools installed, but is not active on the right bottom in the task bar....
ADB devices gives a number with "unauthorised"...
I think, I know myself the problem...
I only downloaded the software package, unchecked everything ( so also the mainpackage ) and installed only the extras/usb driver...
But know, it is 11pm, to late for me know....
X829 have problem phone not detect under Fastboot mode, Fix is in below link with description:
https://forum.xda-developers.com/showpost.php?p=72154309&postcount=72
So far I used your tips...
-adb kill-server
-adb start-server
-adb usb
->restarting in USB mode
-adb devices
->list of devices attached
-ADB reboot bootloader
->on theb phone "you have entered fastbootmode"
-Fastboot OEM device-info
-> waiting for device ( already an hour)
Ctrl-c
Fastboot OEM unlock
->waiting for device
It is still waiting......
Test TWRP Recovery before flashing internal
Hi,
After you install the drivers and Android Tools all starts to make sense
careful when flashing TWRP into the recovery partition, test with adb and the recovery reboot the file you have, I downloaded by mistake a lower version and all it did was show some lines like it was in a higher screen resolution after a while downloaded the latest and worked, flashed that one into recovery. This makes flashing anything again possible without connecting the phone to the pc other than to copy the file.
In my opinion the stock ROMs are heavy and make the phone work slower but if you want to stick to Official LeEco ROMs than I should advise the Chinese ROM, I've read it doesn't encrypt the Data mount points.
Make a backup of your current installation as mentioned in the link posted earlier, I'm not an expert also and am still learning stuff (forced by the low quality ROMs and the fact that it is an unofficial phone).
Lineage Nougat (new and tested in my phone) and Remix (from what I've heard) are pretty good and make phone light and working fast.
Don't Forget to install Google Apps afterwards (GApps as they call it).
There isn't really the need to rename the file to upgrade.zip just click the zip file and swipe to flash the new ROM.
I haven't rooted my phone, heard that Apps like Home Bank ones don't work so nvm that unless you need it but maybe in a few months you think otherwise, gain some experience first. It's not needed to do any of the things mentioned, only for changing Kernel settings and other stuff... I'm not there yet...
Tried Dolby Atmos from XDA but only one works, test it from the top and see if the app works. Install a Icon builder App to create the icon because it won't show in the settings like in the custom ROM. Other than that improves the sound quality.
Regards,
Pedro
Bobenjanneke said:
So far I used your tips...
-adb kill-server
-adb start-server
-adb usb
->restarting in USB mode
-adb devices
->list of devices attached
-ADB reboot bootloader
->on theb phone "you have entered fastbootmode"
-Fastboot OEM device-info
-> waiting for device ( already an hour)
Ctrl-c
Fastboot OEM unlock
->waiting for device
It is still waiting......
Click to expand...
Click to collapse
Repeat again but skip this one:
-Fastboot OEM device-info
Seems drivers are not loading
Hi,
After you connect the device it should start to work if the drivers are correct, this may take a while at first but I used the info cmd to check if it was working
adb reboot bootloader
(will reboot device into bootloader)
fastboot oem device-info
(should return an ID for you phone)
fastboot boot twrp-3.1.0-0-x2.img
(should start TWRP in the phone)
-- flashing only
fastboot flash recovery twrp-3.1.0-0-x2.img
(Make sure the last command worked correctly before flashing recovery, it doesn't have to be renamed to recovery.zip)
Install Android tools, after that the drivers should start to work. Let us know.
Regards,
Pedro
Thank you all for your help already!
Sorry for my next question, but i am really f*cked up...
Does someone has Skype or Whatsapp for instant help?
I deleted and reinstalling ASDK Manager.
The driver for Le Max 2 is older then Google USB driver, so I cant update the Google USB Driver...
Do I have to do Fastboot OEM unlock?
What is difference between "fastboot FLASH" and "fastboot BOOT"?
Thank you very much again!!!
Bobenjanneke said:
The driver for Le Max 2 is older then Google USB driver, so I cant update the Google USB Driver...
Do I have to do Fastboot OEM unlock?
What is difference between "fastboot FLASH" and "fastboot BOOT"?
Thank you very much again!!!
Click to expand...
Click to collapse
Hi,
Can't remember if the older drivers worked but I can test at home.
The phone should be unlocked already (x829) but you can issue the unlock cmd any time, it will say already unlocked or do it, but the phone needs to connect.
Did you allow USB debugging and did all the other steps they say in the forum? Switch on the phone to media option instead of just charging or it will not allow the connection.
fastboot boot twrp-3.1.0-0-x2.img
-- After the reboot with "adb reboot bootloader" cmd is successful if you issue this it will upload TWRP into the phone using adb and start it, I suggest to use this method at first.
the flash cmd will replace the recovery of the phone with TWRP Recovery, so everytime you enter recovery mode by pressing Vol. Up + Power it will go to TWRP TeamWin instead. Do a backup just in case of the phone using the "fastboot boot twrp-3.1.0-0-x2.img" cmd.
Let us know how it goes...
Regards,
Pedro.
My steps:
-Connected via Media Connection
-Allow USB debugging
-OEM unlocked
-Gave permission on phone screen
Installed ASDK from the guide R24.4.1 ( installed all checked boxes )
ADB start-server
ADB USB
ADB DEVICES
ADB REBOOT BOOTLOADER
and then it hang both on OEM DEVICE-INFO & OEM UNLOCK...
-------------------------
I am installing Universal ADB drivers, maybe that workx....
BTW, I am working with Windows7 64Bit Ultimate...
What was yours both OS?
Thank you very much!
I searched myself on Google, and tried some solutions, but nothing worked...
Installing the Universal ADB driver didn't bring any solution....
I read that after ADB REBOOT BOOTLOADER or FASTBOOT OEM UNLOCK, I have to press the volume up? I didn't read that in the guide ( and it didn't work even )...
I have an old laptop, which I can down/upgrade with XP SP3 or W10...
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