Database Info

How to write in android sdk tool

I`m trying to flash new recovery,but i can`t write in sdk tool command line=(
I have to type fastboot flash recovery recovery.img but I can`t(offcourse I start my device in fastboot protocol)
where to write and in which folder I have to put `recovery.img`
sorry for my noob question
I found anything what I want, but now it says that device not found

Put the recovery image in the same folder as fastboot
Sent from my Nexus S using XDA App

but
were is mine fastboot?
I have to flash only recovery
upd
I found anything what I want, but now it says that device not found

Fastboot is either in the tools folder. Go read the quides on how to use fastboot/adb root restore etc. You clearly are currently over your head. All the info is here on the forums the stickies.

ok
but what about error : devices not found ?
I`ve tryed to change usb ports,re-installing drivers what to do?

TechnoManiac97 said:
ok
but what about error : devices not found ?
I`ve tryed to change usb ports,re-installing drivers what to do?
Click to expand...
Click to collapse
Make sure that usb debugging is checked off in settings.

You have two threads and you're just confusing your self.
First you can't flash recovery with just adb without root.
In order to flash a recover you need to use fastboot. The device itself needs to be in fastboot mode/protocol or whatever it is called. It also needs to be unlocked which yours is not.
So forget adb for now. Get the device to show up with the command fastboot devices. Then unlock ( will wipe everything) . Device will reboot. Put it back in fastboot and flash recovery.

My xoom is rooted

[Softbricked Phone] Help needed

Hi everyone.
3 days ago, my OPO has gone softbricked during the night while charging. Don't know why, i haven't make any change during the past days.
Anyway, it's current state:
- Stuck on boot screen (screen with "Cyanogen Mod Ready")
- Can access fastboot
- Can access TWRP recovery
- Bootloader is unlocked
- Phone is found in the PC "Device Manager"
- No change if using an other cable or USB port
And what i can't do:
- with adb tools : phone is not found with cmd adb devices (no answer in "list of devices attached"), changing drivers multiple times don't change that
- during recovery : can't wipe data / cache / factory reset (it says "Unable to mount /data" "Unable to mount /cache", "Unable to mount storage")
- during fastboot : can't flash anything (for instance with the OPO Toolbox, the answer is always "FAILED (remote : flash write failure)", or with command fastboot flash XXXX get the same FAILED answer)
After reading internet threads and sites, it seems that the problem is a corrupted partition, but i can't find something which can solve my problem.
Any advises?
Thx in advance!

3th3lk4 said:
Hi everyone.
3 days ago, my OPO has gone softbricked during the night while charging. Don't know why, i haven't make any change during the past days.
Anyway, it's current state:
- Stuck on boot screen (screen with "Cyanogen Mod Ready")
- Can access fastboot
- Can access TWRP recovery
- Bootloader is unlocked
- Phone is found in the PC "Device Manager"
- No change if using an other cable or USB port
And what i can't do:
- with adb tools : phone is not found with cmd adb devices (no answer in "list of devices attached"), changing drivers multiple times don't change that
- during recovery : can't wipe data / cache / factory reset (it says "Unable to mount /data" "Unable to mount /cache", "Unable to mount storage")
- during fastboot : can't flash anything (for instance with the OPO Toolbox, the answer is always "FAILED (remote : flash write failure)", or with command fastboot flash XXXX get the same FAILED answer)
After reading internet threads and sites, it seems that the problem is a corrupted partition, but i can't find something which can solve my problem.
Any advises?
Thx in advance!
Click to expand...
Click to collapse
Is your bootloader unlocked?If not try it with this command:
fastboot oem unlock
Click to expand...
Click to collapse
After that try wiping your partitions via fastboot for ex.
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
Click to expand...
Click to collapse
And then try flashing again.
Hope it helps:good:
Regards,
acervenky

Hi acervenky,
Bootloader is unlocked, yes.
Unfortunately, wiping partitions with those commands didn't work.
For the 5 commands, i have the answer : FAILED (remote : failed to erase partition).
This phone is going to drive me insane!

So a little update status of my phone.
I have sent a question at request at the oneplus one support.
They have answered quite fast. They made a "rendez-vous" to try to unbrick it by phone but all that was tried have been already done.
They send me instructions for sending the phone to a factory in a foreign contry.
I have received the phone this afternoon, 1 week after it was sent.
Seems to work perfectely fine.
They say that they have changed the Motherboard, which is the problem here.
So if u have the same problem, don't hesitate to use the oneplus one support.
Is there a way to change the title to show that it was a motherboard problem?

TWRP 3.1.0-0 for V3961 (Cloudfone Excite Prime 2, Wiko U Pulse, Qmobile CS1 Plus)

(Can't put the [RECOVERY][PORT] in title because it exceeds character limit)
Bugs:
- MTP (or just my driver?)
- The rest is just working fine (including adb)
How to boot?
Due to how this device works, we can only flash a stock recovery or else it won't boot with custom recovery at all
Click to expand...
Click to collapse
Download TWRP here: https://androidfilehost.com/?fid=818070582850505557
& (skip if already installed) install adb & fastboot drivers here: https://forum.xda-developers.com/showthread.php?t=2588979
1. Enable OEM unlocking & USB debugging via Settings > Developer Options
2. Open Command Prompt & "cd" where you downloaded the image & type:
Code:
adb reboot bootloader
Allow it when a prompt shows up then try again if it doesn't work
Code:
fastboot oem unlock
SKIP THIS STEP WHEN ALREADY UNLOCKED!
When a warning about unlocking bootloader shows up, press volume up (will factory reset your device after rebooting)
Code:
fastboot boot TWRP-3.1.0-0_v3961.img
There! Enjoy TWRP & READ NOTES!
NOTES:
- If this is the first time you booted TWRP, install SuperSU zip (or use "adb reboot") or else the device won't boot to Android after rebooting using TWRP's reboot option! (modifies /system partition, renames recovery-from-boot.p to recovery-from-boot.bak, causing dm-verity to invalidate system partition)
- If your /data partition is throwing errors, you need to reboot it using "adb reboot", since you've just unlocked the bootloader & needs to be formatted via stock recovery
- Since it's just "fastboot boot", it won't stay on your device (don't even try to "fastboot flash" it)

Help me Please
Pls help. My Cloudfone Excite Prime 2 got bootlopp in orange state after trying to fastboot unlock oem and flashed twrp. is there any fix please. I cant turn off my phone its always restarting on orange state on repeat.

Bootloop (
My wiko u pluse got bootloop too :crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:

Fixed - Forgot to read note LOL
I fastboot flash it lol :v

Hello,
Does it work on U-pulse lite ?
Thanks
Laurent

link for download twrp not working
pls provide link for download twrp u pulse v3961, that one not working anymore

twrp?
pls provide twrp for u pulse v3961, thanks

Update the twrp link please, i need it for my wiko u pulse

3DMapPlayer said:
(Can't put the [RECOVERY][PORT] in title because it exceeds character limit)
Bugs:
- MTP (or just my driver?)
- The rest is just working fine (including adb)
How to boot?
Download TWRP here: https://androidfilehost.com/?fid=818070582850505557
& (skip if already installed) install adb & fastboot drivers here: https://forum.xda-developers.com/showthread.php?t=2588979
1. Enable OEM unlocking & USB debugging via Settings > Developer Options
2. Open Command Prompt & "cd" where you downloaded the image & type:
Code:
adb reboot bootloader
Allow it when a prompt shows up then try again if it doesn't work
Code:
fastboot oem unlock
SKIP THIS STEP WHEN ALREADY UNLOCKED!
When a warning about unlocking bootloader shows up, press volume up (will factory reset your device after rebooting)
Code:
fastboot boot TWRP-3.1.0-0_v3961.img
There! Enjoy TWRP & READ NOTES!
NOTES:
- If this is the first time you booted TWRP, install SuperSU zip (or use "adb reboot") or else the device won't boot to Android after rebooting using TWRP's reboot option! (modifies /system partition, renames recovery-from-boot.p to recovery-from-boot.bak, causing dm-verity to invalidate system partition)
- If your /data partition is throwing errors, you need to reboot it using "adb reboot", since you've just unlocked the bootloader & needs to be formatted via stock recovery
- Since it's just "fastboot boot", it won't stay on your device (don't even try to "fastboot flash" it)
Click to expand...
Click to collapse

I have old phone here which is Cloudfone next lite. I want to root this phone, but I need twrp first but I don't see twrp for my phone. Is there somebody can help me 🥹

The Ultimate guide to flash and root Xperia L (aka, taoshan)

This thread will guide you to flash a custom recovery, Root the device, flash custom ROMs. Firstly, read the entire post and then start your work.
I am a noob. But I have a little experience of rooting and flashing. This device gave me nightmares which are less than as compared to the Xperia Sola which I bricked some years back.
My device has a problem. It does not help install twrp with the traditional ways we know like we can see in the Official TWRP website using "dd" method, the Cyanogenmod link using fastboot commands, the Flashify method, the RecoveryApp method whose apk I never found and the Recovery Installer Utility.
I came to know that either my phone don't have the recovery partition or the phone is overriding all the commands.
Using fastboot commands would give the error like in this post.
Using Flashify would tell me there's no recovery partition found. Rashr would complete the flash process but after booting to recovery, there was no TWRP, just the stock Android recovery.
If you read carefully on the twrp page of XL, there's a line which caught my attention late enough.
It means that TWRP may not work on your device unless you install other custom software as well.
Click to expand...
Click to collapse
Flashing custom kernels with flashtool is easy and they come with recovery pre-installed and lots of amazing stuff, but they won't do any good with the stock ROM. I've tried the Extended stock kernel, the Phantom Kernel and the Thunderzap 4.15.
After surfing the web and forums of other devices, I found that there is a chance I can fix things by updating/repairing software via PC Companion. But something happened and repair also failed.
I can't tell the reason why this happened. And I didn't store the logs. But with trial and error I found some workarounds.
Actual Methods start here
Rooting the device
If you only want to root your device for various reasons, then you will need nothing but a Rootkit. Check out this post about Rooting Xperia L.
But if you are planning to install custom ROMs for your device, then skip this rooting step. It won't be necessary for this condition.
Flashing custom recovery
*Try this method only if above-mentioned method fails*
1. Download TWRP 3.2.1 img. The 3.2.2 and 3.2.3 versions work perfectly but they caused the screen to flicker like hell on my device. Rename the file to 'twrp.img'
2. Download and install adb and fastboot drivers system-wide.
3. Connect your device to PC via USB cable and enabling USB-debugging mode.
4. Open Windows Powershell/Command Prompt in the twrp download directory by pressing Shift and clicking right mouse button.
5. Use fastboot command on stock ROM without root and Unlocked Bootloader. Instead of flashing twrp image to recovery, flash to boot. Use the code:
Code:
adb devices
adb reboot fastboot
Wait for device to boot into fastboot mode. A blue LED will flash when connected.​
Code:
fastboot flash boot twrp.img
fastboot reboot
After reboot, don't boot to system. Boot to recovery by pressing volume up repeatedly when pink LED glows. Stop when device vibrates and LED color changes
Flashing custom ROMs
Once the recovery is installed, everything becomes easy. you can find different custom ROMs on the device page here on XDA.
My favorite one is The resurrection Remix Nougat. It is stable enough to be your daily driver. You can head to that page and follow their instructions. But I will also provide steps here.
When in TWRP after the last step, move the downloaded zip file of the ROM and GApps you want to install to the storage of the device by simply connecting via USB.
After that, in TWRP click on Wipe->Advanced->Tick on System, Cache, Dalvik cache. Then Do swipe to begin wipe.
After wipe, go back to main menu. Tap on install, select from the list the ROM zip. then tap on Add more zips and select the GApps zip and then Swipe to start flashing.
After flashing, reboot to system. The first boot takes time. Don't panic if it won't boot.
Install TWRP to FOTAKernel
After booting to your new ROM, you can install the TWRP to your FOTAKernel.
This can be done as following:
Get the downloaded TWRP img file and push it to the device using command line. Open command prompt in the TWRP directory and type,
Code:
adb root
adb wait-for-device
adb push twrp.img /tmp/twrp.img
Now extract the TWRP image to the FOTA partition code,
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now reboot to recovery
Code:
adb reboot recovery
Note that custom ROMs often come with Root access inbuilt. If your ROM happened to be not, and your ROM is based on Lollipop or later version of Android, you can root with Magisk. Just read carefully before proceeding.
Comments are welcome!

Hi.
I'm following this thread and I'm stuck on the fifth step "... flash to boot. Use the code:
adb devices​adb reboot fastboot "​
I think my Sony Xperia L C2105 does not have the fastboot mode.
Here's what I did:
Drivers for Xpleria L are installed.
The bootloader is unlocked (I think!)
1 - installed 15-second ADB
2 - open Windows power shell
3 - Command: adb devices
Response is: "List of devices attached: ZH8001ADB3 device"​
4 - Command: adb reboot fastboot
Response is: long pause, phone booted but in normal mode, and light is red ...!​
5 - Command: fastboot flash boot twrp.img;
Response is: "<waiting for device>";
- phone still running in normal mode and the light is red.
- few minutes later, the phone is charging with green light present.​
I think the phone is rooted.
I used the code provided by the Sony website to unlock the bootloader.
Using the Root Checker Basic app, I get the info: "Congratulations! Root access is properly installed on this device!"
But if I type in the dialer *#*#7378423#*#*, and go to Service info > Configuration > Rooting status is "Boootloader unlock allowed" !!
Is that why it does not work?
I tried switching it off and doing Boot into Xperia L Fastboot Mode Using HARDWARE BUTTONS, but the phone is dark, with no picture, and the led turns blue.
Using the command:
PS C: \ adb> adb devices
List of devices attached
PS C: \ adb>
I've been trying to do that for a few days now and I still have not managed it, even using other advice.
Can someone tell me what to do?
Thank you in advance.

Everterra said:
Hi.
I'm following this thread and I'm stuck on the fifth step "... flash to boot. Use the code:
adb devices​adb reboot fastboot "​
I think my Sony Xperia L C2105 does not have the fastboot mode.
.......
Click to expand...
Click to collapse
1. When in fastboot mode, you should type in cmd "fastboot devices" to check the device connectivity. If you can't, then connect using hardware keys.
2. Blue light indicates that you are in fastboot mode. If list of attached devices are blank, that means drivers are not installed (properly). Connect your phone again in fastboot mode and check your drivers page, Win+X > M (I am assuming you must be on windows). There must be a tiny yellow triangle on your device's name. Right click on it and uninstall it and remove device. Try again installing drivers from the flashtool's folder. Disable driver signature enforcement if you are having trouble going the straight way.
3. Your bootloader is still locked because if it had unlocked then the message displayed would have been, "Bootloader Unlocked: Yes" or something like that. Try flashing your stock ROM via Flashtool. Wipe cache and data while flashing. After flashing stock Rom, try unlocking bootloader again. I believe you are using Flashtool.
4. If you are rooted, then you must have any SuperSU app installed on your device. And it's all good even if you are rooted.

Beginner's guide to the Moto E5 Play since the E5 devs are kind of mean and lazy

Well, here's what I did to get Lineage and Project Treble working:
Enable Developer Options on stock rom and unlock BootLoader
-Go to Settings and find Build Number, tap that 7 times
-Developer Options now enabled
-Enable USB debugging
-install ADB and Fastboot drivers if you already havent
-Plug phone in, open CMD, type "adb reboot bootloader"
-Once in bootloader, type "fastboot oem get_unlock_data"
-Bunch of numbers will show, copy those
-Follow instructions on this page: https://support.motorola.com/us/en/bootloader
Congrats, bootloader is unlocked. Now for TWRP:
-go to this thread and grab TWRP and the no-verity kernel DO NOT FOLLOW THOSE INSTRUCTIONS: https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323
-paste into C:\ drive root
-type cd C:\ in CMD
-type "fastboot flash recovery twrp_james.img" it is okay to show some error here
-type "fastboot flash boot boot-e5-noverity.img" it is okay to show some error here
you now have noverity and TWRP, it is advised to boot into TWRP straight from bootloader once to make it stick
You can use TWRP to flash Lineage, but flash the noverity kernel afterwards, I had boot problems when I didn't.
Now to flash the generic system image (GSI):
-Download GSI, if it's already an image leave it, if it's a zip, extract the IMG
-Factory reset
-reboot into TWRP if you already aren't
-Move GSI image from computer to phone
-tap "install" and change type from Zip to Image
-Install Image, once done factory reset
-reboot should be okay, you can now do the Uncertified Device fix found here: https://forum.xda-developers.com/moto-e5/how-to/uncertified-device-custom-rom-fix-t3856318
Have fun, this quick little guide will hopefully help, as I am kind of an idiot and didn't make a backup of stock.
STOCK FIRMWARE CAN BE FOUND HERE: https://mirrors.lolinet.com/firmware/moto/james/official/
giv thanks plox if dis halp u

SiberianLeopard said:
Well, here's what I did to get Lineage and Project Treble working:
Enable Developer Options on stock rom and unlock BootLoader
-Go to Settings and find Build Number, tap that 7 times
-Developer Options now enabled
-Enable USB debugging
-install ADB and Fastboot drivers if you already havent
-Plug phone in, open CMD, type "adb reboot bootloader"
-Once in bootloader, type "fastboot oem get_unlock_data"
-Bunch of numbers will show, copy those
-Follow instructions on this page: https://support.motorola.com/us/en/bootloader
Congrats, bootloader is unlocked. Now for TWRP:
-go to this thread and grab TWRP and the no-verity kernel DO NOT FOLLOW THOSE INSTRUCTIONS: https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323
-paste into C:\ drive root
-type cd C:\ in CMD
-type "fastboot flash recovery twrp_james.img" it is okay to show some error here
-type "fastboot flash boot boot-e5-noverity.img" it is okay to show some error here
you now have noverity and TWRP, it is advised to boot into TWRP straight from bootloader once to make it stick
You can use TWRP to flash Lineage, but flash the noverity kernel afterwards, I had boot problems when I didn't.
Now to flash the generic system image (GSI):
-Download GSI
-Factory reset
-reboot into TWRP if you already aren't
-Move GSI image from computer to phone
-tap "install" and change type from Zip to Image
-Install Image, once done factory reset
-reboot should be okay, you can now do the Uncertified Device fix found here: https://forum.xda-developers.com/moto-e5/how-to/uncertified-device-custom-rom-fix-t3856318
Have fun, this quick little guide will hopefully help, as I am kind of an idiot and didn't make a backup of stock.
STOCK FIRMWARE CAN BE FOUND HERE: https://mirrors.lolinet.com/firmware/moto/james/official/
Click to expand...
Click to collapse
Just I tip extract IMG from zip don't change zip to IMG but goodluck

skullkid383 said:
Just I tip extract IMG from zip don't change zip to IMG but goodluck
Click to expand...
Click to collapse
some downloads are already in IMG form, the GDI I am using was just a plain IMG file

SiberianLeopard said:
some downloads are already in IMG form, the GDI I am using was just a plain IMG file
Click to expand...
Click to collapse
True had to post cause I seen others try using zips as IMG and then complained it wouldn't boot lol

skullkid383 said:
True had to post cause I seen others try using zips as IMG and then complained it wouldn't boot lol
Click to expand...
Click to collapse
I'll update the OP. I should really start getting in the habit of reserving posts
It's been a while since I've done anything with Android as I've been using a bone stock Revvl which has been discontinued since last year and never got root or an unlocked bootloader because Alcatel is a bunch of sissies who'd rather have OnePlus change their diapers than allow a bootloader to be unlocked.

How long does it normally take Moto to respond once you submit the bootloader unlock request? It's been 2 days and no response email yet.

AUSTIN3:16 said:
How long does it normally take Moto to respond once you submit the bootloader unlock request? It's been 2 days and no response email yet.
Click to expand...
Click to collapse
Minutes

bad key
SiberianLeopard said:
Well, here's what I did to get Lineage and Project Treble working:
Enable Developer Options on stock rom and unlock BootLoader
-Go to Settings and find Build Number, tap that 7 times
-Developer Options now enabled
-Enable USB debugging
-install ADB and Fastboot drivers if you already havent
-Plug phone in, open CMD, type "adb reboot bootloader"
-Once in bootloader, type "fastboot oem get_unlock_data"
-Bunch of numbers will show, copy those
-Follow instructions on this page: https://support.motorola.com/us/en/bootloader
Congrats, bootloader is unlocked. Now for TWRP:
-go to this thread and grab TWRP and the no-verity kernel DO NOT FOLLOW THOSE INSTRUCTIONS: https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323
-paste into C:\ drive root
-type cd C:\ in CMD
-type "fastboot flash recovery twrp_james.img" it is okay to show some error here
-type "fastboot flash boot boot-e5-noverity.img" it is okay to show some error here
you now have noverity and TWRP, it is advised to boot into TWRP straight from bootloader once to make it stick
You can use TWRP to flash Lineage, but flash the noverity kernel afterwards, I had boot problems when I didn't.
Now to flash the generic system image (GSI):
-Download GSI, if it's already an image leave it, if it's a zip, extract the IMG
-Factory reset
-reboot into TWRP if you already aren't
-Move GSI image from computer to phone
-tap "install" and change type from Zip to Image
-Install Image, once done factory reset
-reboot should be okay, you can now do the Uncertified Device fix found here: https://forum.xda-developers.com/moto-e5/how-to/uncertified-device-custom-rom-fix-t3856318
Have fun, this quick little guide will hopefully help, as I am kind of an idiot and didn't make a backup of stock.
STOCK FIRMWARE CAN BE FOUND HERE: https://mirrors.lolinet.com/firmware/moto/james/official/
Click to expand...
Click to collapse
I keep getting "bad key" writen on top left of blank screen when I boot.... then it boots straight to the bootloader... any ideas?
Yes,.. TWRP does work.

BadRx said:
I keep getting "bad key" writen on top left of blank screen when I boot.... then it boots straight to the bootloader... any ideas?
Yes,.. TWRP does work.
Click to expand...
Click to collapse
that happens. Mine says "N/A". I'm pretty sure that the stock recovery has the "hello moto" BS, kind of like a BIOS splash, and TWRP overwrites that so the BIOS has no image to display so it shows an error instead.
But, if everything else works there should not be any other issue with Bad Key.

AUSTIN3:16 said:
How long does it normally take Moto to respond once you submit the bootloader unlock request? It's been 2 days and no response email yet.
Click to expand...
Click to collapse
Mine was instant. Make sure you follow the steps as I've written them.

SiberianLeopard said:
Mine was instant. Make sure you follow the steps as I've written them.
Click to expand...
Click to collapse
Sorry for the late response but my issue was my own fault by having an O where a 0 should have been. Thanks for the responses!

Ed

Jojo_Y said:
Ed
Click to expand...
Click to collapse
wot