Hi All,
Hoping you can help I have an xperia tablet which was on Android 5.1.1 and which i tried to upgrade to 7 and think i may have screwed it up.
I was using lineage OS guidance. I am using ADBdriver tool. Currently the table is stuck in twrp recovery. When in fastboot mode I can use the fastboot devices command and see the device. I can use the fastboot flashboot command and flashboot reboot.
When i try to use the adb push (imagefile) command it says adb: error failed to get feature set : no devices/emulators found.
If i use adb devices command it doesn't see anything.
In device manager I have under android device a device called 'google nexus ADB interface'....not sure if this should say xperia, not sure how to change it. Sony website advises using ADB version 26.0.2 I have tried that and version 26.0.0.
At this point I'd be happy to flash the xperia boot on instead in the hope that would fix it but i don't know where to find it.
Just to add, I have installed the sony flashtool. I can see the device, apparently there is way to put back a sony boot using the tool but I don't know where to get one.
Using 'Emma' I have a working device now but its on 4.4.4. which isn't great! Any ideas?
So I'm not sure what to do and would massively appreciate some help
Thanks
evilistix said:
Hi All,
Hoping you can help I have an xperia tablet which was on Android 5.1.1 and which i tried to upgrade to 7 and think i may have screwed it up.
I was using lineage OS guidance. I am using ADBdriver tool. Currently the table is stuck in twrp recovery. When in fastboot mode I can use the fastboot devices command and see the device. I can use the fastboot flashboot command and flashboot reboot.
When i try to use the adb push (imagefile) command it says adb: error failed to get feature set : no devices/emulators found.
If i use adb devices command it doesn't see anything.
In device manager I have under android device a device called 'google nexus ADB interface'....not sure if this should say xperia, not sure how to change it. Sony website advises using ADB version 26.0.2 I have tried that and version 26.0.0.
At this point I'd be happy to flash the xperia boot on instead in the hope that would fix it but i don't know where to find it.
Just to add, I have installed the sony flashtool. I can see the device, apparently there is way to put back a sony boot using the tool but I don't know where to get one.
Using 'Emma' I have a working device now but its on 4.4.4. which isn't great! Any ideas?
So I'm not sure what to do and would massively appreciate some help
Thanks
Click to expand...
Click to collapse
Upgrade via OTA to latest stock 5.1.1 or via xperia-companion app.
Also you can flash 5.1.1 via Flashtool v0.9.18.6.
Great, thanks for your help.
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.
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying:
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'm trying to use SP flash tool to flash TWRP recovery on my tablet. My tablet is a Kindle Fire HDX 3rd generation with fire OS 4.5.5.3. And the this version of fire OS is based on Kit Kat 4.4.4. I have tried a lot of drivers and none of them seem to work quite right. I get stuck on <waiting for device> a lot. And my device just doesn't communicate with my pc well enough for my programs to fully work.
So which driver and adb should I install? Which TWRP scatter file should I download? Should I install any other programs and/files? Should I use a different tool instead of SP? BTW when I tried to use just CMD prompt to install TWRP recovery it usually doesn't recognize the commands I enter. Or it will get stuck on <waiting for device> or something like that.
So am I on the right track to install TWRP recovery? Is there a better easier and or more fool proof way?
Thanks for any and all answers ?
Hi,
I've got a problem where my phone is stuck in bootloop and I cannot go into recovery mode. All I can get into is fastboot mode. I know there's a way to get into recovery from fastboot mode using ADB but I do not know what to do or what steps to follow as I really don't know much about modding phones apart from flashing a ROM that I wan't to use via recovery (which I assume even a ten year old would be able to do effortlessly after seeing it being done once or twice).
I am using the global 4/64 Redmi Note 4 running the latest version of Android Open Source Illusion Project.
Any help would be appreciated. Thank you.
laneofmagic said:
Hi,
I've got a problem where my phone is stuck in bootloop and I cannot go into recovery mode. All I can get into is fastboot mode. I know there's a way to get into recovery from fastboot mode using ADB but I do not know what to do or what steps to follow as I really don't know much about modding phones apart from flashing a ROM that I wan't to use via recovery (which I assume even a ten year old would be able to do effortlessly after seeing it being done once or twice).
I am using the global 4/64 Redmi Note 4 running the latest version of Android Open Source Illusion Project.
Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
Did you try combo key? Holding Power and Volume+ buttons?
If this doesn't works, you have to set up ADB bridge on your PC. Here is the guide: https://www.xda-developers.com/install-adb-windows-macos-linux/
When you do that, type the command via ADB while being in fastboot mode:
fastboot reboot recovery
This should take you into the recovery mode.
Any help please Im stuck in a boot loop and recovery and fastboot are inaccessible, so i cant send any commands? im forking on Mac OS but even ive installed a virtual PC to try some of the countless programs but no seams to work since the phone is not recognized.