Database Develop

Unable to find device in RSDLite

Hi guys, I'm using Motorola Milestone and my bootloader is 90.78. I opened RSDLite and plug in the phone in bootloader mode but my RSDLite is unable to detect my device.
I have already installed the motorola drivers. Anyone has any ideas?

bryant_16 said:
Hi guys, I'm using Motorola Milestone and my bootloader is 90.78. I opened RSDLite and plug in the phone in bootloader mode but my RSDLite is unable to detect my device.
I have already installed the motorola drivers. Anyone has any ideas?
Click to expand...
Click to collapse
Same issue here. I have bootloader 90.74. On my Windows 7 there's no way...
Drivers 4.1 and 4.6 tested...but no way...

Anyone has any ideas about this issue?

Weird problem :s Works fine on my Win 7 VM. You could maybe try to uninstall and reinstall the driver :/

Some people have issues with RSDLite on Windows 7 64 bits.
I used to have the same problem and finally I had to install it on my netbook which has W7 32 bits and it worked fine.
Did you managed to install it in an other computer ?

The latest RSDLite versions didn't worked for either but version 4.5.3 works good under Windows 7 for me!

I found a solution
Like the rest, I too had the same problem. Then I found out how to make it work by accident.
I am using RSDlite version 4.5.7 on Windows 7 (32-bit version).
This is what you must do.
Step 1:
Download Open Recovery Version 1.46 for Milestone from http://www.modmymobile.com/forums/downloads.php?do=file&id=28089
Step 2:
It is a rar file, so use any free software to extract out the contents of this OpenRecovery_v1_46_SHOLS.rar file to a new folder on your desktop.
After u have extracted it, look for a file called vulnerable_recovery.sbf. Copy out this vulnerable_recovery.sbf file to somewhere on your pc for example to the root of your C drive on your PC.
Step 3:
Download from this script to disable the recovery check for signed recovery menu (so that we can apply update.zip later) from
http://modmymobile.com/forums/attac...le-recovery-disable_recovery_check_by_ota.zip.
Unzip the file and there should be a file called Disable_recovery_check_by_OTA.sh
Step 4:
Copy the Disable_recovery_check_by_OTA.sh file to a sub folder called scripts that is within the OpenRecovery folder (which we have already extracted earlier) (eg. OpenRecovery\scripts).
Step 5:
Boot up the phone as per normal and then connect the phone to PC via USB cable
Step 6:
Change the USB Connection to Memory Card Accessl
Step 7:
Go to the desktop of your PC and open up the folder where the contents of the extracted OpenRecovery_v1_46_SHOLS.rar file is. You should then copy the update.zip to the root of your phone's SD card (eg. SDcard\update.zip).
Also copy the whole OpenRecovery folder also to the root level of your SD card (eg. SDcard\OpenRecovery)
Step 8:
Change the USB Connection to Portal & Tool. This is the trick that will allow RSDLite to detect your phone.
Step 9:
Launch RSDLite ver.4.5.7
Step 10:
It will take a few seconds for your phone to appear in the device list of RSDLite
Step 11:
Click on the "..." button and locate and open the vulnerable_recovery.sbf file which we have extracted earlier and had copied out to somewhere (eg. root of C drive).
Step 12:
Click on the "Start" button.
Step 13:
Immediately you would see something in the status progress of RSDlite. RSDlite will switch your phone to the Bootloader mode by itself.
Step 14: - Very Important Step
Pay attention to the status of the Bootloader on your phone. Halfway thru the progress of flashing the vulnerable_recovery.sbf, RSDlite will initiate a reboot of your phone.
When that happens, you must prevent the phone from rebooting into the normal Android mode and get it to boot into the Bootloader mode by quickly pressing & holding up on your D-pad in horizontal (landscape) position.
I would suggest that b4 RSDlite initiate the reboot, you should be prepared for it by sliding out the keyboard first and hold it in the horizontal (landscape) position and get ready to press up on the D-Pad.
by quickly turning your phone to the horizontal position (landscape) and press and hold up on the D-Pad of your phone. Hold the up key of your D-pad for about 3 to 4 seconds before release it and it should be now back in the bootloader mode.
Do not do anything yet. You will know when the flashing of the vulnerable_recovery.sbf is completed and successful when the result in RSDLite device list window says "PASS".
Step 15: - Also very important step
Once the flashing of the vulnerable_recovery.sbf is complete (after you see "PASS" in RSDlite), you may close RSDlite and then unplug the phone from the USB cable.
The phone is still in the bootloader mode. Now be prepared to boot into the recovery mode. This is very important. If you fail to boot into the recovery mode then you will have to repeat from Step 8
The technique that I use on my Motorola Milestone to boot into the recovery mode is by using the 3 button technique. I press the "x" key + power button + camera button together at the same time and hold it until the recovery mode icon appears which is a an exclamation mark within a triangle.
Step 16:
While in the recovery mode, slide the keyboard back in. Then press and hold the volume up button first and then press the camera button once and when you see the recovery menu you can quickly release the volume up button.
Step 17:
Slide the keyboard out. Use the D-pad to navigate. If you are holding the phone in vertical position, then to navigate up and down the recovery menu, just press up or down on the D-pad. To confirm your selection, press down on the middle of your D-Pad.
Using your D-Pad, scroll down to the part it says "apply sdcard:update.zip" and press the middle of your D-Pad to select it.
You should see something packages being downloaded to your phone which is part of the installation process of the Motorola Milestone Open Recovery Menu which is not the stock Recovery Menu.
Step 18:
Once you are in the Motorola Milestone Open Recovery Menu, scroll down to the option that says "Run Script". Select that option.
Step 19:
Then you should be able to see a list of scripts and one of them should be "Disable_recovery_check_by_OTA.sh". Select that script.
Step 20:
Once that "Disable_recovery_check_by_OTA.sh" has been applied, the phone will no longer check for signed recovery menus like this Motorola Milestone Open Recovery Menu when ever you go into the stock recovery menu to "apply sdcard:update.zip". This means you can install different types of "Open Recovery Menu" for different custom roms for Motorola Milestone.
Besides using this Motorola Milestone Open Recovery Menu, I have also tried the following 2 "Open Recovery Menu" on my Milestone:
1) Androidiani OpenRecovery 3.3 - http://forum.xda-developers.com/showthread.php?t=796679
2) G.O.T OpenRecovery (for installing G.O.T custom FROYO rom) - http://groupoften.wordpress.com/g-o-t-s-openrecovery/
Important Note:
Before you start to install custom roms please do a Nandroid back up of your phone in case something goes wrong during the installation of the custom rom, you can restore your phone back to stock rom.
The Nandroid back up and restore option is available within all 3 "Open Recovery Menu" mentioned above.

I have Windows 7 Ultimate 64-bit and I use Motorola USB Drivers 4.7.1 and RSD Lite 4.9. So it would be good to download these versions, which are the latest. If this wont work, do a factory reset on your Milestone.

[Stock][HC][3.2.1] Ideapad K1 + 3rd party apps (Bootloader fix)

This is a completely a stock Rom for the Lenovo Ideapad K1 Tablet. This is the latest update Honeycomb version 3.2.1, update 14_14_120109.
This will work for those lucky few who are plagued by the bootloader error when trying to apply the latest OTA.
Unsupported menu option selected: 1
Unrecoverable bootloader error (0x00000002)
It does include all the original third party apps.
If you do not want the third party apps
Before flashing
1. Open the 'files' directory
2. Rename userdata.img to userdata.img.bak
3. Rename userdata_blank.img to userdata.img
This Rom is NOT rooted
Nvflash Windows Drivers
md5sum: 9aa3a4814ca63366329d85a22ed01f64
To boot into APX mode
1. Power off
2. Hold down the Vol - and the Vol +
3. While holding the Volume keys down, Power on
4. The display should go black, and both LED's on either side of the home button should light up. This is APX mode. If using Windows make sure the drivers are installed
Instructions
Windows
1. Extract the K1_Stock_120109.zip contents to a directory
2. Double click the "flash-windows.bat" file
3. After the flash completes if you get any force closes you may have to do a factory reset. Settings > Privacy > Factory data reset
Linux
1. Extract the K1_Stock_120109.zip contents to a directory
2. Open a terminal and cd into the extracted directory
3. Copy and paste the following command
Code:
chmod a+x ./flash-linux.sh && chmod a+x ./files/nvflash
4. Run either
Code:
sudo ./flash-linux.sh
or from a root prompt
Code:
./flash-linux.sh
5. After the flash completes if you get any force closes you may have to do a factory reset. Settings > Privacy > Factory data reset
Download
K1_Stock_120109.zip
md5sum: 1ba3c55b4bfbd50495aeb22e66617629
Mirror - androidfileshare.com
Thanks to Whitesnake for being the Guinea Pig while we figured out what was causing the bootloader issue.

Umm.. Whitesnake.. not whitehawk LOL

Looks like you put together a super package...
But I've got problems:
NVflash isn't working for me...
I just get an error:
Code:
C:\Adb\K1\NVFlash>nvflash -w
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
My device is stuck in bootloops from flashing direct to K1_A301_13_13_111209_US.zip by renaming it update.zip and putting it in the Downloads folder.
Any idea what's going on? Should I just try to return it straight away?
EDIT: I'm bulled a bone head move. I was testing out nvflash, but in a directory without the files it needs! ha! All's well...

Is this tools can applied to umts model?

Hey broo I really apreciatte your work but the links are down and I really need this because I got that Famous Bootloop.
Thanks

thanks for the mirror, but a little cuestion: the nvflash drivers are the same for all the tegra 2 devices?... cause the link of the nvflash driver is down...
thanks¡¡

I want to use this w/o the 3rd party apps but there is no userdata_blank.img file to rename. Sorry if it's a noob question.

Links dead
Please reupload.

Just get Kaschemme NVflash, his are current.
Sent from my Touchpad using XDA Premium HD app

is there a similar solution for thinkpad ?
mine boots directly to "Booting Kernel Recovery Image" and hangs for a few second then powers down.

hello,
plz update download links

[Q] Tough time going back to stock

I've been running CM 11 for a little more than a month and have been really enjoying it. So, I have no idea why I decided to download the MythTools and revert back to stock At&t. Doing so, I messed something up on my phone.
To start, I'm using Windows 7 64bit and when selecting option 1 (install ADB-fastboot-apkTools) I get the new cmd window that states "please select install button after new window is opened press any key to continue...." when I press any key the cmd window would just close. Hoping it would help, I then chose option 6 to update my Motorola drivers. When my browser window opened I got the ADB installer window and clicked install. It seemed to have installed fine. I then updated my moto drivers. Thinking I was all set I went for option 2 to flash the stock firmware which I had put in the firmware folder. With my phone in fastboot I started the process and it failed. Reading through the cmd prompts I had noticed it said something like 'you selected 2- instal cwm.img cannot load cwm.img' . I unplugged my phone and tried to restart it and it was stuck on the bootloader screen. I then restarted into recovery and my PhilZ recovery did start up. However it displays "E: could not mount /data to setup /data/media path!" . I was still able to go through the process of a clean re-install of CM 11 but am stuck on the startup splash screen for CM.
I definitely got myself in way too deep and am clueless on how to fix this. Would someone mind instructing me on what to try next? Many thanks in advance.

I am not sure if it would make a difference in your situation but I do everything for my phone on an x86 system. I have had issues with LG and Samsung phones in the past when trying things on an x64 computer.

ifixgse said:
I've been running CM 11 for a little more than a month and have been really enjoying it. So, I have no idea why I decided to download the MythTools and revert back to stock At&t. Doing so, I messed something up on my phone.
To start, I'm using Windows 7 64bit and when selecting option 1 (install ADB-fastboot-apkTools) I get the new cmd window that states "please select install button after new window is opened press any key to continue...." when I press any key the cmd window would just close. Hoping it would help, I then chose option 6 to update my Motorola drivers. When my browser window opened I got the ADB installer window and clicked install. It seemed to have installed fine. I then updated my moto drivers. Thinking I was all set I went for option 2 to flash the stock firmware which I had put in the firmware folder. With my phone in fastboot I started the process and it failed. Reading through the cmd prompts I had noticed it said something like 'you selected 2- instal cwm.img cannot load cwm.img' . I unplugged my phone and tried to restart it and it was stuck on the bootloader screen. I then restarted into recovery and my PhilZ recovery did start up. However it displays "E: could not mount /data to setup /data/media path!" . I was still able to go through the process of a clean re-install of CM 11 but am stuck on the startup splash screen for CM.
I definitely got myself in way too deep and am clueless on how to fix this. Would someone mind instructing me on what to try next? Many thanks in advance.
Click to expand...
Click to collapse
you said you are stuck on startup splash meaning bootloop? if it is you should try again with rsd lite.
else you may lose all your data in the memory but do a format media/data and sdcard, so that it can mount /data, it worked for me. then format system mount everyting and do a fresh install of any rom you can sideload or just have it in the sdcard.

I'm pretty sure I am doing something wrong with MythTools. When I select option 2 in the tool to install stock firmware the following happens,
- asks for fimware folder example and I select "N"
- asks if firmware files are finished copying.. I press enter and continue
-then it says "the system cannot find the path specified
the system cannot find the path specified
the system cannot find the path specified
'7z' is not recognized as an internal or external command
operable program or batch file
Are you ready to flash stock fimware...
at this point i stupidly hit enter and that was it with my phone. I'm guessing the tool could not locate the firmware .xml file for extracting and I have no idea why. The compressed folder is IN the firmware folder.
One other question with Mythtools, when installing the tools what path do you want them installed in? I did them in the same file the Myth tools are in.

ifixgse said:
I'm pretty sure I am doing something wrong with MythTools. When I select option 2 in the tool to install stock firmware the following happens,
- asks for fimware folder example and I select "N"
- asks if firmware files are finished copying.. I press enter and continue
-then it says "the system cannot find the path specified
the system cannot find the path specified
the system cannot find the path specified
'7z' is not recognized as an internal or external command
operable program or batch file
Are you ready to flash stock fimware...
at this point i stupidly hit enter and that was it with my phone. I'm guessing the tool could not locate the firmware .xml file for extracting and I have no idea why. The compressed folder is IN the firmware folder.
One other question with Mythtools, when installing the tools what path do you want them installed in? I did them in the same file the Myth tools are in.
Click to expand...
Click to collapse
Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock. Any questions don't hesitate to ask.
If this helps you hit that thanks button!

Micromax canvas A1 bricked, pls help!!!

hi,
my micromax a1 was runnning marshmallow 6.0.1 when during a security patch update installation got stuck and failed to boot again. now just booting into "dead android with exclamation mark". upon pressing power button and volume up and going into recovery(Android stock recovery) menu , cant wipe partition or data as it throws error "E: failed to mount/ cache" errors..
upon trying to install with any SD card also throws same error.
then i tried to install through ADB, while connecting to PC , PC not detecting mobile in recovery mode but detecting in bootloader mode. with fastboot flash command (for installing TWRP/CWM) in bootloader mode, error coming as "sending recovery failed(unknown status code)" .
Kindly help...

same happened to me yesterday . do you find any solution ??

Hi there !
STEP 1: DOWNLOAD the FLASH TOOL from this this link :LINK TO DOWNLOAD FILE
It is almost 30 MB in Size. And EXTRACT / UNZIP it to Desktop ( OR SOMEWHERE ) of your computer.
STEP 2: DOWNLOAD LOLLIPOP FLASH FILE
DOWNLOAD LINK FOR LOLLIPOP: HERE
After downloading this flash file EXTRACT / UNZIP it to Desktop ( OR SOMEWHERE ) on your computer.
STEP 3: NOW INSTALL DRIVERS:
YOU NEED TO BE ON WINDOWS 7 TO INSTALL DRIVERS (WINDOWS 8 DOESN'T SUPPORT THIS DRIVER / PHONE IS NOT DETECTED)
DOWNLOAD DRIVERS from this link : HERE
EXTRACT AND INSTALL THE DRIVERS : Next next next and finish If you see an security warning ( a red coloured pop up ) choose INSTALL IT ANYWAY
IT IS RECOMMENDED YOU TO RESTART YOUR PC.
STEP 4:
Now we have Extrated /unziped 2 files. One is FLASHTOOLS and other is FLASH FILE and Extracted it or unziped it to Desktop or Somewhere.
One of it having the name SP_Flash_Tool_exe_windows_v5.1424.00 or open both folders then one of it having the flashing tool. OPEN THE FOLDER NAMED SP_Flash_Tool_exe_windows_v5.1424.00
it contains an application named fashtool.exe OPEN IT
NOW THE APPLICATION IS ASKING FOR SCATTER LOADING FILE
its a txt file which is on the extracted flash file folder
BROWSE it by clicking Button named Scatter Loading
click OPEN
STEP 5:
HERE IN THE DROPDOWN BOX, IT SAYS DOWNLOAD ONLY, CLICK ON IT AND SELECT FIRMWARE UPDATE ONLY.
IF YOU SELECT FORMAT + DOWNLOAD, THEN YOU WILL LOOSE IMEI NUMBER.
NOW CLICK DOWNLOAD BUTTON ( GREEN ARROWED BUTTON NAMED DOWNLOAD )
IN CASE YOU LOOSE IMEI NUMBER, THEN REFER HERE
STEP 6:
Now SWITCH OFF your PHONE and REMOVE BATTERY
STEP 7:
CONNECT your PC via USB CABLE
wait for the driver Detection.
THE FLASHING PROCESS WILL START AUTOMATICALLY you can See the progress in progress bar which is on bottom of flashing tool Application.
WHEN IT IS FINISHED DISCONNECT USB AND RESTART YOUR PHONE.
NOW YOU WILL GET LOLLIPOP UPDATE IMMEDIATELY.
NOW REFER HERE TO ROOT MARSHMALLOW
HIT THANKS IF HELPED
if link do not work here properly then just google 'canvas a1 stuck on startup' ... and follow link in associated with xda

Device is dead
My phone is neither switching on, nor charging.
I flashed the stock ROM due to some problem with the rooted device through SP Flash tools. It completed successfully, but the device is not switching on or charging.
KIndly help

Redmi 9 Brick

I installed a custom rom and it gave me bootloop, I tried flashing a new recovery and it didn't work, and now I don't have fastboot and recovery, the bootloop has a message:
dn-verity corruption
your device is corrupt
it can't be trusted and may not work properly
press power button to confirm
or, device will power off in 5s
(when I am connected to a usb in the computer the mobile restarts constantly after this message)

Hello, I've had this problem yesterday and after some fidgeting around I found a solution,
first you follow the instructions in this link https://telegra.ph/MTK-Authorisation-Bypass-08-25
then follow the instructions in this link https://t.me/HelioG85_Unified/12709
note that you don't need to install the engineering rom you can do with any stock rom image also dont set the sp flash tool to format all + download, set it to ugrade firmware option and you'll be good to go.
One last thing if the phone isnt connecting hold the power button + vol down and you will find that your pc detected the phone.

i have this error
omartzy said:
Hello, I've had this problem yesterday and after some fidgeting around I found a solution,
first you follow the instructions in this link https://telegra.ph/MTK-Authorisation-Bypass-08-25
then follow the instructions in this link https://t.me/HelioG85_Unified/12709
note that you don't need to install the engineering rom you can do with any stock rom image also dont set the sp flash tool to format all + download, set it to ugrade firmware option and you'll be good to go.
One last thing if the phone isnt connecting hold the power button + vol down and you will find that your pc detected the phone.
Click to expand...
Click to collapse
i have this error
C:\Users\tripp\Desktop\VD171_MTK-bypass-v1.5\bypass_utility-v.1.4.2>py main.py
Unable to create process using '/bin/python3 main.py'

Make sure python is installed correctly on your pc by typing "python" in the command prompt

omartzy said:
Make sure python is installed correctly on your pc by typing "python" in the command prompt
Click to expand...
Click to collapse
and now:
Traceback (most recent call last):
File "C:\Users\tripp\Desktop\VD171_MTK-bypass-v1.5\bypass_utility-v.1.4.2\main.py", line 3, in <module>
from src.exploit import exploit
File "C:\Users\tripp\Desktop\VD171_MTK-bypass-v1.5\bypass_utility-v.1.4.2\src\exploit.py", line 2, in <module>
from serial.serialutil import SerialException
ModuleNotFoundError: No module named 'serial'