Database Info

[Q] Cant load Reovery from fastboot

I "attempted" to root my NS following these directions:
I. Before You Begin
1. This will unlock your phone’s bootloader (so you can flash recoveries and ROMs), and can be undone very easily (unlike the Nexus One).
2. This WILL ERASE all your information on the phone.
II. Setup ADB
1. Head to our How To Setup ADB procedure, once you can see your phone’s serial number after typing adb devices then come back to this procedure and continue.
(MAKE SURE YOU FOLLOW ALL THE STEPS IN THE WRITTEN PROCEDURE AS THERE HAVE BEEN UPDATES ADDED).
III. Unlock the Bootloader
1. Turn off your phone.
2. Turn it on by holding Volume Up and Power until fastboot mode comes up.
3. Plug the phone in via USB cable to your computer while it is in fastboot mode.
4. Open a command prompt on your computer by clicking on the Start menu button and typing cmd and hitting enter in the search box.
5. In the command prompt that pops up, type the following with hitting enter at the end of each line:
cd c:\androidsdk\tools\
fastboot oem unlock
6. At this point the phone will ask you to confirm, select yes. You now have an unlocked bootloader.
IV. Flash a Custom Recovery Image
1. Download the custom recovery image and save it to your computer:
ClockworkMod Recovery for Nexus S
2. Copy the recovery.img file inside the tools folder of the sdk (so it is in the same folder as fastboot.exe)
3. Then in the command prompt that should still be open, type the following with hitting enter at the end of each line:
fastboot flash recovery recovery.img
4. Once it is flashed, leave the phone in plugged in and in fastboot mode.
V. Root the Phone
1. In fastboot mode, select Recovery using the volume buttons and power button and wait for it to boot into recovery mode.
2. Download the Superuser flashable zip file and save it to your computer.
Superuser for Android 2.0 and Up Flashable Zip
3. Once in recovery mode, select Mounts and Storage then select Mount USB Storage so we can transfer files to the sd while it is in recovery mode.
4. Copy the Superuser.zip file to the root of your internal storage (do NOT extract it, do NOT put it in any folders, just on the phone’s storage itself).
5. Select Unmount on the phone.
6. Select Mount System, then select Go Back to get back to the main menu.
7. Then scroll to flash zip from sdcard and then choose zip from sd card and select the superuser.zip file and wait for it to finish flashing.
8. Once it is done, select Go Back then Reboot System and wait for the phone to reboot.
VI. Stop the Phone from Uninstalling the Custom Recovery Image
1. Once the phone is booted up, plug it in via USB cable and do NOT mount the storage.
2. Open a command prompt on the computer and type the following with hitting enter at the end of each line:
adb shell
cd etc
mount -o rw,remount /dev/block/mtdblock3 /system
mv install-recovery.sh install-recovery-no.sh
3. That will mount the system as writable and rename the file that overwrites the recovery image on reboot so that our custom recovery will stay.
4. Turn off the phone and turn it back on by holding down Volume Up and Power to get into fastboot mode.
5. Plug the phone in via USB cable while in fastboot mode and open the command prompt again and type the following with hitting enter at the end of each line:
cd\
cd c:\androidsdk\tools\
adb reboot bootloader
fastboot flash recovery recovery.img
5. Once it is done, you have just reflashed the recovery image and it will now stick. You are all done! You have an unlocked bootloader, a custom recovery image, and root access! If you want to now load a custom ROM head to the next procedure linked below.
I ran into an issue near the end with this step under VI:
2. Open a command prompt on the computer and type the following with hitting enter at the end of each line:
adb shell
cd etc
mount -o rw,remount /dev/block/mtdblock3 /system
mv install-recovery.sh install-recovery-no.sh
I used root explorer to mount and rename the file since I couldnt get it to mount with adb shell. My issue now is that when I boot into fastboot mode and go to recovery, I get the error icon (The android with the triangle with the ! in the middle). I cant for the life of me figure out how to get recovery back. It also does not recognize my device in fastboot mode with adb devices but does recognize it when its booted into the regular os. Any ideas?
This is solved. Apparently the directions are a little sketchy.
When it got to this step:
5. Plug the phone in via USB cable while in fastboot mode and open the command prompt again and type the following with hitting enter at the end of each line:
cd\
cd c:\androidsdk\tools\
adb reboot bootloader
fastboot flash recovery recovery.img
the adb reboot bootloader command would not work. Skipping it solved my problem.

Need help preparing Xoom for official updates

Hey folks,
I´ve ran my MZ601 xoom on EOS builds over the last 1,5 years.
Obviously its unlocked and rooted. Currently its running CWM Recovery 4.0.0.4
Now I want to go back to stock to install the latest official updates to get the updated drivers for the UMTS radio/modem module.
After that I want to unlock and get root again to use any of the lastest custom Roms again.
Switching to a touch based recovery would be nice too.
I surfed around a bit and I´m rather confused which steps I need to perform in order to do this.
I guess I need to remove root and lock the bootloader again before I can install official updates ?
Could someone please toss me in the right direction? Maybe some step-by step list?

You'll presumably want Build H.6.1-38-1 for Retail Europe from here.
Returning to stock:
Extract the files from the link above to your adb/fastboot directory if you have one. If you don't have one I've uploaded them for you here.
Connect your Xoom to your PC then open command prompt from your adb folder. (Hold shift > right click on adb-fastboot folder > click Open Command Window Here)
Type adb devices and hit enter, if no devices are listed then ensure USB debugging is switched on in Settings > Development > and tick USB Debugging, then try again.
If it still doesn't appear then download Motorola USB drivers here and try again.
If fine then run:
adb reboot bootloader​Then run the following to flash the stock image:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock​
Flashing userdata.img is going to remove all your files so back everything up first.
This should unroot your Xoom anyway, not entirely sure if the lock is required to receive updates, but it's simple to unlock again.
Once booted and through initial setup you should receive several over the air updates. (I believe the stock image is Android 3.2)
Unlock:
Connect your Xoom again and open command window in the adb-fastboot folder as before.
Run:
adb reboot bootloader
fastboot oem unlock
fastboot reboot​You'll now be unlocked.
Install Touch Recovery and Root:
Next download ClockworkMod Touch recovery from here, rename it to just recovery.img for simplicity, and copy the image to the adb-fasboot folder.
Download Xoom Universal Root from here.
Copy that file to your sdcard.
Then run:
adb reboot bootloader
fastboot flash recovery recovery.img​(assuming you renamed it)
Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Important: When you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery.
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old​Then select reboot in ClockworkMod recovery and boot as normal.
If you are unable to use adb in recovery, then you can enable this through Windows by doing the following:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Finally, run:
adb reboot recovery​If ClockworkMod touch recovery is still there then all is good!
Hopefully I've made sense! Any questions, just ask.
Repeat of downloads:
Download Motorola USB Drivers (Device Manager) here.
Download ClockworkMod Touch recovery here.
Download Xoom Universal Root here.

Wow, what a detailed guide
Thank you sir

No problem!
Let me know how it goes, hopefully shouldn't have any problems.

Resetting worked great :good:
Right now I´m in an OTA marathon
all that unlock, root and recovery stuff sounds familiar so I don´t expect any problems.
Thanks so far :good:

alecbond said:
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old​Then select reboot in ClockworkMod recovery and boot as normal.
Finally, run:
adb reboot recovery​If ClockworkMod touch recovery is still there then all is good!
Click to expand...
Click to collapse
Ok, so this is not working
after I flash touch recovery and do thta reboot thing I can enter touch recovery, thats fine.
Flashing universal root, fine.
THEN,
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
gives me error since in recovery mode there ist no adb connection
Whatever when I choose to reboot the system, recovery warns me that it will get overwritten by boot and ask me to disable this.
Shall I do this?
EDIT: Nevermind, I decided to be a little brave and just confirmed that message.
Now touch clockwork seems to be persistent and I´m a happy Xoomer again

Sorry, I had meant to reply during my lunch break.
Edit: Realised the time on the second of your posts, so wouldn't have been much help on my lunch anyway
Well I believe I just learned something new!
Either that or I'd forgotten it asked.
I assume it disables the action rather than deletes those files.
My method was just so you can use the reverse rename in future to re-enable the overwrite on boot.
In future, not that you'll necessarily ever need this information, you can enable adb in recovery through windows by doing the following
When in recovery and connected to your PC, open Device Manager, find your phone, usually under 'Other Devices'.
Then right click > Update driver > Browse my computer > Let me pick from list > Pick your phone (either one if there's two shown)
Should confirm driver installed then adb should work.
I didn't include the above previously as I couldn't remember having to do it personally.
Glad to hear all is well though!

alecbond said:
You'll presumably want Build H.6.1-38-1 for Retail Europe from here.
Returning to stock:
Extract the files from the link above to your adb/fastboot directory if you have one. If you don't have one I've uploaded them for you here.
Connect your Xoom to your PC then open command prompt from your adb folder. (Hold shift > right click on adb-fastboot folder > click Open Command Window Here)
Type adb devices and hit enter, if no devices are listed then ensure USB debugging is switched on in Settings > Development > and tick USB Debugging, then try again.
If it still doesn't appear then download Motorola USB drivers here and try again.
If fine then run:
adb reboot bootloader​Then run the following to flash the stock image:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock​
Flashing userdata.img is going to remove all your files so back everything up first.
This should unroot your Xoom anyway, not entirely sure if the lock is required to receive updates, but it's simple to unlock again.
Once booted and through initial setup you should receive several over the air updates. (I believe the stock image is Android 3.2)
Unlock:
Connect your Xoom again and open command window in the adb-fastboot folder as before.
Run:
adb reboot bootloader
fastboot oem unlock
fastboot reboot​You'll now be unlocked.
Install Touch Recovery and Root:
Next download ClockworkMod Touch recovery from here, rename it to just recovery.img for simplicity, and copy the image to the adb-fasboot folder.
Download Xoom Universal Root from here.
Copy that file to your sdcard.
Then run:
adb reboot bootloader
fastboot flash recovery recovery.img​(assuming you renamed it)
Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Important: When you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery.
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old​Then select reboot in ClockworkMod recovery and boot as normal.
Finally, run:
adb reboot recovery​If ClockworkMod touch recovery is still there then all is good!
Hopefully I've made sense! Any questions, just ask.
Repeat of downloads:
Download Motorola USB Drivers (Device Manager) here.
Download ClockworkMod Touch recovery here.
Download Xoom Universal Root here.
Click to expand...
Click to collapse
Hey, you did a great guide! Would you mind if I put that in the FAQ Thread?
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD

XxLordxX said:
Hey, you did a great guide! Would you mind if I put that in the FAQ Thread?
Click to expand...
Click to collapse
No problem, I'd be honored!

How to fix a soft bricked device from a flash that failed due to missing files

This guide is meant to less techie people, and written in detail. Please don't mind me if I overexplain. If you have any questions, feel free to comment them.
Also, I am not responsible for anything you do to your phone; you assume your responsibility for anything you do because of this guide.
Scenario:
So, lets say that you tried to flash an zip file on your android using sideload, but the zip required another file to be in the same directory as it, in order to work.
After flashing the zip and getting an error, your phone may not get pass the logo of the brand and be soft bricked.
Also, you formatted your external sd as internal, and cant access your usual location with files in the recovery.
In this case, don't worry, as I'm here to help you unbrick your phone without reinstalling the rom.
Things you will need:
your phone
a computer connected to your phone with an usb cable
the proper drivers for your phone
a custom recovery like cwm or twrp installed on your phone
probably root, although I'm not sure
and finally the adb (android development bridge) utility
Where to get a custom recovery?
- https://www.xda-developers.com/how-to-install-clockworkmod/
or search on xda under at your device's forum
Where to download adb from?
- https://forum.xda-developers.com/showthread.php?t=2588979 (this one comes with the drivers)
- https://dl.google.com/android/repository/platform-tools-latest-windows.zip (just the adb files)
So lets get started:
First, get your phone into Recovery mode (on samsung hold power button volume up and home button), and connect it to your pc with a usb cable.
Open ADB by shift + right clicking the folder platform-tools in witch it is located. Click on "Open Command Prompt window here" or "Open Powershell window here" (depends on your windows settings).
You need to find a location on your phone that is accessible through the flash zip menu from your recovery. (from sdcard / from sdcard1 or whatever your external sd is called)
In my case, i could get to see folder 0 and obb from "flash zip from sdcard".
To find a suitable folder:
In the window, type
Code:
adb.exe shell
if you opened cmd, or
Code:
./adb.exe shell
if you opened powershell.
This will open a terminal that will run commands on your phone.
(Now you can type commands in the cmd window that will be run on your phone.)
Type in
Code:
cd /sdcard/0
to go to the main sd card location that is accessible in recovery when you go to flash a zip from there. (if you can get to another folder where you could a flash a zip from, change the location to that place)
You can use here the command
Code:
ls
to view objects in the folder you are in.
After you are done, type
Code:
exit
to exit.
To solve the soft-brick, you need to reflash the zip, but with the files it needed in the same directory.
Type in the ADB window
Code:
./adb.exe push "location of the file you are sending" "location of the folder you are sending to (eg. /sdcard/0)"
if you are in powershell, or without the ./ if you are in cmd.
Use this until you have sent all the files needed for a successful flash.
Then just use the "flash zip" utility from your recovery with the location you have sent the files to, on your phone, to complete the flash, and solve the half-brick.
Restart your phone and you should be good to go.
Thanks to the following threads, that helped me put this together, and solve this problem on my phone:
https://forum.xda-developers.com/showthread.php?t=1927198
https://forum.xda-developers.com/showthread.php?t=2588979​

[ROOT] Coolad Modena 2 / Sky 2 (E502)

Recently, I successfully ported TWRP from Coolpad Note 3 Lite to Modena 2. After testing, everything works fine, on both devices. Since this device has locked bootloader, we need to bypass this by enabling fastmmi mode and factory mode to enable temporary root access and make initial backup and flashing. So, let´s get started.
Remember to read this post carefully. I am not resposible for any damage to your device. If you brick your device while flashing the TWRP you can *almost* always recover it using SP Flash Tool and YGDP Tool
IF YOU ACCIDENTALY BRICK YOUR DEVICE AND YOU WANT TO FLASH IT VIA SPFT, DO NOT FORMAT THE DEVICE IN SPFT!!! If you´ll format partitions in TWRP, that´s fine, but don´t do FORMAT ALL + DOWNLOAD or FIRMWARE UPGRADE! This will brick your device, like mine This tutorial will not (hopefully) brick it, but just in case something goes wrong, now you know what not to do.
Preparing the environment on your computer
Windows
Download ADB and Fastboot from this link
Open it
Install it system-wide
Also, install the drivers
GNU/Linux (Ubuntu / Debian based distros)
Open terminal
Type "sudo apt install adb fastboot libusb-dev" without the quotes (")
Other things, that are required
Since the file size of the recovery exceeds the maximum 8MB of allowed upload size, you can download it from DataFileHost.
Preparing the device
First, you need to remeber that this could render your device unbootable and will void warranty.
Enable developer options
Go to Settings -> About phone
Tap the build number 7 times
Go back
Go to Developer options
Make sure OEM unlocking and USB Debugging is enabled
Enabling factory mode
Open dialer app
Dial *#9527*#
Click on "DM"
You will be prompted to insert RD personnel password. Enter: 54321
Click cancel button
DM button should change colour to RED
Exit the app by clicking home button
Installing and setting up openrp app
Open terminal / command prompt
Type:
Code:
adb start-server
Type:
Code:
adb devices
Now, click on your phone allow debugging and make sure to tick the radiobutton to remember / always trust this computer
Type:
Code:
adb install
Press spacebar after the install word and drag and drop the downloaded openrp.apk file to terminal
Hit enter
After it´s done, type:
Code:
adb shell monkey -p com.yulong.openrp -v 500
Now, the fun part. ROOTING the device
But before that, BACKUP
Now, keep your phone plugged in, and do a normal reboot by pressing and holding the power button and clicking reboot
When it vibrates, press and hold the Volume down key (Vol-)
You will see these lines on the screen:
Code:
=>[Factory mode]
Code:
=>VolumeDown key is pressed
Code:
=>[fastmmi mode]
After that, you´ll see the LED turns green and "Up Down" text on the screen
Now, back to your computer, type in the command prompt
Code:
adb devices
You should see XXXXXXXXXXXXXX device listed (where XXXX... is the serial number)
Type in the command prompt:
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery of=/storage/self/primary/stock_recovery.img
and
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot of=/storage/self/primary/stock_bootimg.img
Flashing the TWRP Image
Type in the command prompt:
Code:
adb push (drag and drop the recovery image file here, like you did with the openrp.apk file) /storage/self/primary/
Type:
Code:
adb reboot
Press and hold VolumeDown key (Vol-) to boot to fastmmi mode
Type:
Code:
adb shell dd if=/storage/self/primary/recovery_twrp_e502.img of=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery
Type
Code:
adb reboot
Press and hold the VolumeUp key (Vol+) to boot into recovery. If you see white screen with "Recovery" text in it, congrats. Everything is working. If not, try again.
Flashing the SuperSU package
Download the zip from SuperSU website
Copy the zip over to the device, with TWRP running
In TWRP, click install, click the zip and confirm the installation.
Factory reset is not required, but you should at least wipe the cache
If this post was useful for you, hit the thanks button

RESERVED

Hi i have a problem here. at the part to drag and drop the openrp file. When i have downloaded the file a drag it and drop it after the install word. The problem is that if I want to drop it there it will do nothing, nothing there shows or anything. Please respond.

I guess you can type the path to the installation file instead of dragging.

Hello,
Very helpful thread, my coolpad Modena 2 (E502) is now rooted.
Don't forget to disable the factory mode once everything is done, or you won't be able to access the storage to usb anymore.
Thanks.

helo, can i get help, when i try to install openrp on abd and fastboot, it printed this message "Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]"
can anyone help me on that step, so i can root my e502

TCRakt said:
Hello,
Very helpful thread, my coolpad Modena 2 (E502) is now rooted.
Don't forget to disable the factory mode once everything is done, or you won't be able to access the storage to usb anymore.
Thanks.
Click to expand...
Click to collapse
how to disable the factory mode ?? :crying:

Firefa23 said:
how to disable the factory mode ?? :crying:
Click to expand...
Click to collapse
Hello,
If I recall correctly (I don't have the phone anymore, just touched it once to root it at the time), you basically undo the "Enabling factory mode" step.
I think if you dial the number, you'll be back in the menu where you have the option to disable the factory mode.
Factory mode should be disabled when 'DM' is green.
Good luck

very good

Need Custom rom please
nougat / pie

Hello, could you resend the twrp recovery file for this phone again?. old links not work!.
(sorry for my bad english)

I need help with ADB/Fastboot commands from a powers shell window

i am very new so please speak to me like i have 50 IQ points (im actually not far off). i can get the powershell to open on my pc then when i try
PS C:\platform-tools> adb devices
List of devices attached
R9WN113HXVJ device
it works, but when i try any commands that start with fastboot, the window just hangs. Do i need to be in the bootloader for fastboot? does TWRP need to be installed first?
#2. I am trying to get an image off of my tablet and the tutorial says i need to enter....
" adb pull /sdcard/Download/magisk_patched.img " I am assuming its supposed to mean....
"adb pull /sdcard/Download/NAME OF FILE ON TABLET.tar"... which is "magisk_patched_ZRwve.tar"
if i am trying to "pull" from the tablet, where does it put this file on my PC?

scampo77 said:
i am very new so please speak to me like i have 50 IQ points (im actually not far off). i can get the powershell to open on my pc then when i try
PS C:\platform-tools> adb devices
List of devices attached
R9WN113HXVJ device
it works, but when i try any commands that start with fastboot, the window just hangs. Do i need to be in the bootloader for fastboot? does TWRP need to be installed first?
#2. I am trying to get an image off of my tablet and the tutorial says i need to enter....
" adb pull /sdcard/Download/magisk_patched.img " I am assuming its supposed to mean....
"adb pull /sdcard/Download/NAME OF FILE ON TABLET.tar"... which is "magisk_patched_ZRwve.tar"
if i am trying to "pull" from the tablet, where does it put this file on my PC?
Click to expand...
Click to collapse
No worries friend, everyone starts somewhere and IQ is not a real scientific measurement. Now let's clear some things:
You're not in fastboot mode if you didn't recognize it immediately. To enter fastboot from adb, use:
Code:
adb reboot fastboot
and no you don't need twrp to access fastboot mode.
The correct way to use pull looks like this:
Code:
adb pull <path of file to pull> <path of destination on pc>
for example:
Code:
adb pull /sdcard/Download/YOURFILENAME C:\platform-tools\
Also from context of your question, i assume you want to root your phone. Something helpful to remember, you don't need to flash TWRP to root, you can just boot into it without permanently changing your recovery by using this command in fastboot:
Code:
fastboot boot nameoftwrp.img
from there flash magisk and you're done

Slim K said:
No worries friend, everyone starts somewhere and IQ is not a real scientific measurement. Now let's clear some things:
You're not in fastboot mode if you didn't recognize it immediately. To enter fastboot from adb, use:
Code:
adb reboot fastboot
and no you don't need twrp to access fastboot mode.
The correct way to use pull looks like this:
Code:
adb pull <path of file to pull> <path of destination on pc>
for example:
Code:
adb pull /sdcard/Download/YOURFILENAME C:\platform-tools\
Also from context of your question, i assume you want to root your phone. Something helpful to remember, you don't need to flash TWRP to root, you can just boot into it without permanently changing your recovery by using this command in fastboot:
Code:
fastboot boot nameoftwrp.img
from there flash magisk and you're done
Click to expand...
Click to collapse
i am being told that there is no fastboot for Samsung devices, however your commands within powershell all worked, i managed to drag my file over. thank you!
you said "now flash magisk" like its something everyone knows. I have magisk manager on my tablet now and I have a magisk.zip on my PC. I am using a program called ODIN for flashing Samsung devices but i cant seem to put all of these pieces together to root or flash my phone.
any advice?