Hello
I have downoaded "DooMLoRD_v4_ROOT-zergRush-busybox-su" from
http://forum.xda-developers.com/showthread.php?p=18777723&highlight=rooting#post18777723
I extracted the archive on my pc's desktop, instaled adb drivers, run "runme" which is a windows batch file.
Before I run "runme" I:
1. Installed adb drivers
2. Enabled usb debugging
3. Enabled installing applications from unknown sources
4. Increased screen timeout
5. Plugged in the phone to my pc with an usb cable.
Then I run "runme"
pressed enter, then it did something, the phone rebooted and nothing was changed, apparently.
Please help me root my phone, I would be really grateful
This is an screen shot of the process.
{
"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"
}
Thank you in advance
P.S. My pc's operating system is Windows 7 Ultimate, my Xperia mini's OS is Android 2.1 I think.
Related
i was flashing this custom rom @ HTC_One_S_-_MaximusHD_10.0.0 AND during the aroma installer step it took too long @SamE display without any progress for more than 1 hour a so i force rebooted.....managed to get to the recovery again....now here is the problem....i had wiped +factory reset previously and wipe cache....now i wanted to flash again this rom bt it wasnt detected in sd card which i had put inside android folder which got deleted....and now i want to put the zip file back iva PC...BT PC GIVES [email protected] not installed properly CODE 10....WHAT DO I DO....this was my first ever experience ...so please reply in easy way....as i plug the phone with pc it connects the immediately disconnects and goes on again and again like this
{
"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, Im trying to finally flash Android M on my Xperia M2, but when i write the command to flash, it stays forever with `waiting for device´. I have searched and created a file to determine the access to my device when its in fastboot mode. Concretly, the file is called androidrules (not exactly, but it is his main name). I created the file with vi editor because it is the only tool that can be used to create it, and i have added the `rules´ for an xperia device with each id vendor and my user name, but it stays the same.
However, i have fastboot drivers installed and it detects my phone when i type sudo fastboot devices. I don know what happens....
Im using Ubuntu 14.04 LTS 64-bit on VmWare Workstation.
CAN SOMEONE HELP ME PLEASE? :crying:
{
"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.
Hi,
I tried every way and guides shown here. Even disabling driver integrity checks et cetera.
Currently, there's a default stock ROM on my Xperia Z2.
I install the adb-setup-1.4.2.exe installer which installs adb / fastboot + the drivers for my X64 Win10.
Alright.
Reboot.
Then I plug in the USB cord into my turned off phone and hold Volume Up.
My phone vibrates.
I release the button.
Then in tthe Device Manager, this shows up:
{
"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"
}
Everytime.the.same.****ing.THING!
Anybody had the same problem?
One time, through some curious wonder, it worked. S1boot showed up and even the correct driver was instaled (back then via the adb-setup by a XDA user).
Well, what am I doing wrong?
I would be glad for any help. I've tried any troubleshooting guide there is by now and I am at the end of my knowledge.
Thanks for any help,
Michael
Hi, I'm trying to install my flashboot drivers. But everytime i do that, they dissapear from folder. I tried different versions of flashtool drivers ( 0.9, 1.3, 1.5 ) Always same result. I disable driver signature verification but it didnt work. Tried to replace some USB files in windows 32 / drivers but it only created another issue. I know there are couples post how to fix it for windows 8 but I'm using windows 7 but nothing seems to work. I'm out of idea. I followed this guide http://forum.xda-developers.com/showthread.php?t=2354721 but my windows wont start driver installation because for some reason they wont stay in my computer.
Trying to unlock Bootloader for Sony Xperia SP C5303
{
"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"
}
Hey guys,
I've a problem with my OPO not being seen as a adb device, the file transfer protocol works fine (MTD) the problem is I need to debug an app on it and in this case the UE4 can't recognize the OPO as a adb device.
I think the situation is being caused by my computer installing the adb diver in a strange way, picture:
{
"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"
}
To note that Universal Serial Bus Devices only shows up when the phone is in USB Debugging Mode.
Infos:
Windows 10 Pro x64
LineageOS Nightly (Oct9 - 14.1-20171009)
Tried:
Installing Samsung adb Drivers
Google adb Drivers
Force driver overwrite ( doesn't allow me to find the drivers even if I uncheck compatible drivers, it only shows like 7 drivers even when unchecked)
Wide google search, haven't seen this problem any where else ><
Any one has an idea of what is happening here? Or how could I solve this situation?