okay i was helping a friend across continent
i helped him unlcok his mini and now he decided to do on his own for his sibling's neo v and i was overseeing and he seemed to forgot to unlock to bootloader for neo V but we went straight to installing clockwork mod...
now we are trying to unlock but we cannot get past the fastbook getvar command !!!
when connected holding the menu button we get an error about disk something and its an XP machine cause all the other machines have been updated too windows 8 and we cannot find windows 8 driverds!
we get this error while attaching while menu pressed!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you have windows 8 drivvers let us know
1) XDA-> Neo general section-> search :"windows 8"
2) google.com-> search: "windows 8 fastboot drivers neo V"
both of them searched in less then 15 seconds. good luck..
Related
Hello together,
as you can see on my screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
adb driver should be installed properly but my ARC 7 HD doesnt get recognized. When I try to do a manual driver installation (with boot options) my google driver still gets rejected because of it incompatiblity to x64 systems.
Can you recommend me another driver or installation routine?! My Kobo is rooted and in debug mode.
edit: my asus tf101 gets recognized
edit edit: when the kobo pad is in recovery mode it gets regognized, but not booted
Thanks and regards
solved: Installed the recovery with Rashr, also got adb over wifi running. Sadly there is no Kitkat or cyanogen mod available for this pad. I would like to get rid of these reader tools....
hope this helps!
http://forum.xda-developers.com/showthread.php?p=65499511
Sent from my MI 2SC using Tapatalk
Hi everybody,
A few days ago my RN2 died, I tried to unlock it but it has no response I thought the battery drained down but it didn't.
I am trying keep it back and go out from this brick thing but I can't by myself.
Apparently, drivers are installed but I am not completely sure.
When I plug the mobile to the PC it goes enable and disable like a loop from the device manager window. Although, when Flashtool tries to install the recovery send me an error 'BROM S_FT_GET_MENORY_FAIL, as I read, it means Flashtool can't find the partition where it has to write the recovery, but then I don't know if it is a driver trouble or it is a hardware problem, what do you think?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance!!
PS. I tried from win 7, 8 and 10, and always the same, it sounds like it is recognizing the phone but it turns back and disable the COM port every minute :s
hi
my windows 10 64x
on test mode (bcdedit) for integrity and signing i
only one driver failed to install here screenshot its
i want to flash new kernel and twrp recovery (stay with stock)
btw
flashtool can see its Z5 compact and also seems to see bootloader mode and flashmode , its like nothing missing
but i dont want to break my device
i going to flash with flashtool like my old sony (debug mode on and OEM unlock
and via ADB command line unlock the boot loader ( i got the code from sony)
the missing driver is important? maybe i just got better version that why it failed?
ps i can only run flashtool 64x somewhat
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi All,
This is my first post here so please let me know any other detail I should have included in my post. While trying to lock my bootloader which I had unlocked while trying to downgrade from buggy Android 10, I have ruined my phone. There is no OS now in my phone and I can't boot to recovery mode either. Only screen I can get on is Fastboot mode (image attached), volume keys work but on pressing power button to select a mode does not do anything. This has been the state for last 3 days.
Situation has got worse since yesterday that it has started to show no sign of charging, even fastboot commands have started to fail with below error.
'FAILED (remote: 'Warning: battery's capacity is very low')
Please help
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, yes like the Titel says.
I was playing around with the MTK Tool on the PC and did Manage to Format my whole Partition there. on a Olefone Armor 7.
So de Charge LED is working but i got no reaction on the adb devices commands and also no reaction on the Power UP Button.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
my question now. …is there any solution around to fix this?
Lovely greats
Richard
ADB is integral part of Android OS, hence it can't work if Android device's OS got erased.
Try to re-flash device's Stock ROM by means of ODIN.
thank you very much, so I have start W10 in a Virtualbox an use the MTK Tool that's recognize my Phone again,
I was use the MT6779 Scatter-file what I was found to reflash on the Armor 7. But the Pulgin show's me that it is a MT6227.
So I guess i have to find a MT6337 Scatter-file first.