Related
Hello everyone,
I've just tried installing twrp-3.0.2-3-thea.img (md5sum: 35c37561f0c22bfe23cd01b5c388e8b5) and BETA-SuperSU-v2.62-3-20151211162651.zip (md5sum: 7fcb30bcbcd18b5f0b0f5848a096d4ed) on a Moto G LTE 2014 "Thea".
Unfortunately something didn't work. The device first was stuck in the boot animation, then started booting correctly a few times, but now it's completely bricked:
I've been unable to turn the phone on using either pressing power+button down for 10 secs or just pressing the power button for 2 mins while being connected to an usb charger. Obviously it won't connect to adb/fastboot/etc.
I'm really puzzled. Is it even possible to brick a device like this just by trying to root it? Any suggestions?
Alright, found the issue - it seems that for some reason or another flashing TWRP or SuperSu caused fastboot to stop working, hence the hard brick. Now It shows up as "qhsusb_bulk" - unfrotunately there's no way to fix this by myself given that the only fastboot images ( "MBM-CI") available are for Android 4.4.4.
If your bootloader is unlocked you shouldn't have any problems reflashing. You do however have to make sure you are flashing the correct recovery IMG for your phone there are a very large number of ROMS and each is device specific. Try leaving LTE out of your search criteria when searching for images to flash with, rather just Moto G 2nd gen 2014 and you will be on your way to finding the correct IMG. I found a Titan IMG that works with my XT1072 and believe you me that was after the 5th/6th time of reflashing! Another handy tip is that in order to enter into fast boot or recovery mode there's are a few things to consider, namely
The version of fastboot adb you have installed on your PC, some versions behave strangely? Don't ask me I know nothing!
Secondly and very importantly you need to have latest drivers for your make and model of phone installed on your PC.
Thirdly before you connect your phone via its USB cable to PC you must first start up fastboot if you are just using fastboot. I have mine sitting as shortcut on desktop right next to adb shortcut for convenience.
Fourth: hold power button plus vol down for about 3-5 seconds, continue to hold vol- button but let go of power button (this is an important detail that many people on the forum forget to mention) with Motorola specifically!!!! Trust me do it this way and you will almost certainly always boot into recovery/fastboot mode
5th connect your phone to your PC ( not to teach your grama how to suck eggs but don't forget to select USB debugging under dev options on your phone) hopefully you did this??? Otherwise I don't know what the work around is for that, other than factory reset and start over?!
Anyway after connect to PC in the shell terminal run the adb devices command if you are in adb or
run the fastboot devices if you are in fastboot to see if your computer can detect your device? This is a clear indication of whether or not your bootloader is unlocked and/or whether USB Debugging is selected, shouldn't be hard to work out which device is yours as only one device should then show up. There are threads on XDA about how to unlock BL. Aquire root and flash recovery images, obviously, but I couldn't begin to tell you how to do that as each scenario is so different from the next, best of luck!:good:
None of those solutions would obviously work, considering the bootloader/fastboot partition has been altered to the point the device won't boot at all, forget about Drivers or USB Debugging.
By the way, I've just got my device from motorola, after roughly two months since they took it to the repair centre. Their official response has been "We won't fix devices who had been tampered with".
Oh well. When I got it back the clerk could only congratulate me for my really nice new paperweight.
The phone isn't starting at all? It shows something on the screen or acts just like powered off?
Now It shows up as "qhsusb_bulk"
Click to expand...
Click to collapse
You mean the PC isn't recognizing the phone at all and just shows an USB device with that identifier?
LuuchoRocha said:
The phone isn't starting at all? It shows something on the screen or acts just like powered off?
Click to expand...
Click to collapse
Completely blank screen. No response whatsoever.
You mean the PC isn't recognizing the phone at all and just shows an USB device with that identifier?
Click to expand...
Click to collapse
That's right. It's the same error which occurs on some MSM89xx SoCs when the bootloader/blankflash gets steamrolled. But contrary to what happens to some devices like the Galaxy SIII, there are no available bootloader image files available anywhere, and it looks like the SoC used on mot g devices does not provide any failsafe boot mode from sd.
In other words, it's a really nice paper weight until a disgruntled Lenovo employee leaks the required files somewhere. Actually, according to the Motorola tech guy I've spoken to, there's the chance that clearing the bootloader triggers an efuse making it impossible to recover from altogether, but I really hope this is not the case.
So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks
jgro1976 said:
So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks
Click to expand...
Click to collapse
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.
Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
MDV106 said:
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.
Click to expand...
Click to collapse
Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
jgro1976 said:
Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
Click to expand...
Click to collapse
Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
jgro1976 said:
Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
Click to expand...
Click to collapse
jgro1976 said:
Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
Click to expand...
Click to collapse
Im guessing you finally realised they after getting the android icon with the red triangle u have to press volume up and hold it then tap the power key to enter the recovery. Good to know you managed to unlock the bootloader eventually.
A lot of people have been having issues with fastboot, especially on Windows machines . Try restarting the shell or use a different USB port on your computer?also maybe try a different driver version and see if it helps.
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
blkair445 said:
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
Click to expand...
Click to collapse
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
blkair446 said:
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
Click to expand...
Click to collapse
The blue light is fastboot mode. There is no ui interface in fastboot for sony devices. Just a blue light and black screen.
R800x_user said:
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Click to expand...
Click to collapse
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
blkair446 said:
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
Click to expand...
Click to collapse
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
jepher said:
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in ?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
Click to expand...
Click to collapse
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
blkair446 said:
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
Click to expand...
Click to collapse
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
jepher said:
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
Click to expand...
Click to collapse
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
blkair446 said:
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
Click to expand...
Click to collapse
Yes I am using w10. Will try linux later. I have searched everywhere and stucked at the same step. Thank you.
I have managed to unlock the bootloader and root the phone. But problem is. I can't write on the root folder.
More to this I think I might have located the boot file boot_X-flash-all-2396.sin but using magisk it returns no boot image found. I see the guide says use the canary built but that seems to have been shut down, so at an impasse here and am still reaching out for help - damn op phone were never this funky
I might as well put this one out there then -- Is there anyway to flash a op 8 pro in2025 to dual sim - it's the cause of this painful trip
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
jepher said:
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
Click to expand...
Click to collapse
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
cd993 said:
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
Click to expand...
Click to collapse
Yes. Relock it using fastboot command.
I use ubuntu to do it. If you can run fastboot commands in windows10 lucky you.
In the past I have unlocked the boot loaders for Pixel, Pixel 2 and Pixel 3 always on first try and I know how to do it. But my new Pixel 5, US unlocked version, arrived today, will not boot loader unlock. I have dev options enabled, USB debugging on, and allow OEM unlock set on. I'm using a Mac so my fastboot commands are ./fastboot___. With the Pixel 5 in fastboot mode, ./fastboot devices gives a correct response, the device responds with its serial number. But then with ./fastboot flashing unlock nothing happens. Just sits there. When I give the command the terminal cursor moves down to the next line but there is no response from the device. I've turned off, rebooted, repeated multiple times, same result. I tried the old ./fastboot oem unlock and that does not work either (as expected).
Has anyone else encountered this? Advice?
Using latest adb/fastboot? I had problems flashing/unlocking the device because I tried it with an old adb/fastboot version.
If that doesn't help then try using another computer. Often windows doesn't (I know you're probably using mac) correctly recognize devices in fastboot mode, which is why you have to manually add google drivers in windows device manager if 'fastboot devices' doesn't detect the device.
Good luck!
Michael1200 said:
Using latest adb/fastboot? I had problems flashing/unlocking the device because I tried it with an old adb/fastboot version.
If that doesn't help then try using another computer. Often windows doesn't (I know you're probably using mac) correctly recognize devices in fastboot mode, which is why you have to manually add google drivers in windows device manager if 'fastboot devices' doesn't detect the device.
Good luck!
Click to expand...
Click to collapse
Thanks, Michael. I am using the latest SDK with current platform-tools, and don't have another computer. Tried several different cables, no luck. However, I've decided to forgo unlocking the BL and just set it up locked. I no longer use root nor custom ROMs and future TWRP is very unlikely so I'm going to stay boot loader locked for the first time in many years. Will see how it goes. I really have not needed/used it since OS10.
Thanks again.
I've ran into the following problem:
came home and try to open my phone, code doesn't work to unlock screen. Unless I'm going insane was sure the code was correct twice.
Restart phone, stuck on enjoy.now for a long time, goes to alcatel logo, then goes into an Android Recovery message saying "can't load Android system. Your data may be corrupt."
Then 2 options: try again or Factory data reset.
I've managed to find the following possible solution: https://glebovdev.medium.com/how-to-fix-cant-load-android-system-issue-8a5b0ead5a15
..but I can't even get to recovery screen with more than 2 options. It would be a huge pain if I have to factory reset.. should it be possible to get to recovery mode on my phone as well?
Is there any possible way to get the data off the phone (mainly Google Authenticator to which I'm not sure I have the codes anymore)?
Thanks
BrickAlcatel said:
I've ran into the following problem:
came home and try to open my phone, code doesn't work to unlock screen. Unless I'm going insane was sure the code was correct twice.
Restart phone, stuck on enjoy.now for a long time, goes to alcatel logo, then goes into an Android Recovery message saying "can't load Android system. Your data may be corrupt."
Then 2 options: try again or Factory data reset.
I've managed to find the following possible solution: https://glebovdev.medium.com/how-to-fix-cant-load-android-system-issue-8a5b0ead5a15
..but I can't even get to recovery screen with more than 2 options. It would be a huge pain if I have to factory reset.. should it be possible to get to recovery mode on my phone as well?
Is there any possible way to get the data off the phone (mainly Google Authenticator to which I'm not sure I have the codes anymore)?
Thanks
Click to expand...
Click to collapse
It could be that your device is trying to boot to the inactive slot, verify in fastboot mode which slot is marked as active and try to boot either in A and/or in B slot.
Idk if I'm doing something wrong but holding volume up or down as it restarts, the only boot screen I get is:
Android Recovery
TCL/5003d_EEEA/Curie
8.1.0/OPM2.171019.012/5003d_ALWE_EEA_V3
user/release-keys
(aforementioned error)
Try again
Factory data reset
fastboot mode should show other options right?
BrickAlcatel said:
Idk if I'm doing something wrong but holding volume up or down as it restarts, the only boot screen I get is:
Android Recovery
TCL/5003d_EEEA/Curie
8.1.0/OPM2.171019.012/5003d_ALWE_EEA_V3
user/release-keys
(aforementioned error)
Try again
Factory data reset
fastboot mode should show other options right?
Click to expand...
Click to collapse
Well, fastboot is to interact through fastboot commands and you can check from there the slot that is active with
Code:
fastboot getvar all
and you see something like slot_active xx
When I run adb devices in powershell it does not show any devices connected (although the device does show as connected in Windows device management).
In device management it does show as "MTP USB device".
Is this likely to be a driver issue?
BrickAlcatel said:
When I run adb devices in powershell it does not show any devices connected (although the device does show as connected in Windows device management).
In device management it does show as "MTP USB device".
Is this likely to be a driver issue?
Click to expand...
Click to collapse
Device has to be power on to respond to adb commands and from what you were telling your device is bricked..
It's technically powered on but yes still does nothing but bootloop and try again/factory reset screen. There's no possible other way to get to Android recovery mode when the volume down+power option doesn't seem to be working?
BrickAlcatel said:
It's technically powered on but yes still does nothing but bootloop and try again/factory reset screen. There's no possible other way to get to Android recovery mode when the volume down+power option doesn't seem to be working?
Click to expand...
Click to collapse
Device has to be strongly and consistently on so adb commands can work, they can't work while in bootloop so forget it this way.
What you can try is tipically pwr + vol. up and pwr + vol. dwn, one of them will take you to fastboot mode where you can give it a try to what I pointed out in previous outputs.
OK some progress.. apparently you have to let go of power button and volume up right as the alcatel logo appears, the timing seems to matter. I'm now able to see Android recovery with more options at least so will try from there.
Thanks again for taking time to reply.
I've tried
Code:
fastboot getvar all
this results in <waiting for any device>
adb devices still shows no list of devices even though in Device Manager it shows as "Fastboot gadget" under other devices
I've downloaded drivers from Alcatel website in case it's a driver issue but on the list of model numbers during setup mine (5003D_EEA according to recovery screen) doesn't show.
I do see a bunch of websites allegedly offering these specific drivers but assume it's risky to download from anywhere other than Alcatel official site.
BrickAlcatel said:
I've tried
Code:
fastboot getvar all
this results in <waiting for any device>
adb devices still shows no list of devices even though in Device Manager it shows as "Fastboot gadget" under other devices
I've downloaded drivers from Alcatel website in case it's a driver issue but on the list of model numbers during setup mine (5003D_EEA according to recovery screen) doesn't show.
I do see a bunch of websites allegedly offering these specific drivers but assume it's risky to download from anywhere other than Alcatel official site.
Click to expand...
Click to collapse
It seems to be a reliable site https://www.androidusbdrivers.com/alcatel-1-usb-drivers/ it offers the 4 different drivers needed covering all the modes that your device can enter to.
I would recommend mainly two things:
- Uninstall/remove firstly all the drivers that you don't use, it could be something for an old android/tablet that you don't use anymore.
- Don't swap the cable data from/for other device, any of them have its own type of connection, use the same proper cable data for only one device.
From there the typical first step in fastboot is just typing
Code:
fastboot devices
], if the message is "waiting for device" then it's not working.
hi im having the exact same problem, but cant get out of this. Could somebody maybe help me? How did you eventually fixed it? kindregards