Database Users

[GUIDE] How to reboot in recovery

Update
Flash this to have working combo
[HOW-TO] Enable Three Button Combo [RECOVERY]
Since our phone doesnt have any button combination go enter the recovery we have to use workarounds
Other methods:
ADB method
If you are running on non rooted ROM
1. Download and install Android SDK
2. Connect the phone to the PC via USB
3. Press Win key+ r and type cmd
4. Type adb reboot recovery
5. Done. Phone should reboot into recovery
Terminal method
If running rooted ROM
1.Download and install
Terminal Emulator app ( https://play.google.com/store/apps/details?id=jackpal.androidterm )
2. Open the app
3. Type su
4. Accept SuperUser permission
5. Type reboot recovery
6. Press enter
7. Done. Phone should reboot into recovery
App method
Requires root
1. Download and install this app: https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot
2. Open the app
3. Click recovery
4. It should reboot
This guide may be updated once the cwm comes out!

Thank you for this!

ppero196 said:
Since our phone doesnt have any button combination go enter the recovery we have to use workarounds.
ADB method
If you are running on non rooted ROM
1. Download and install Android SDK
2. Connect the phone to the PC via USB
3. Press Win key+ r and type cmd
4. Type adb reboot reccocery
5. Done. Phone should reboot into recovery
Terminal method
If running rooted ROM
1.Download and install
Terminal Emulator app ( https://play.google.com/store/apps/details?id=jackpal.androidterm )
2. Open the app
3. Type su
4. Accept SuperUser permission
5. Type reboot recovery
6. Press enter
7. Done. Phone should reboot into recovery
This guide may be updated once the cwm comes out!
Click to expand...
Click to collapse
And one more way, if you have rooted your phone, you can install an app like quick boot and use it for booting into recovery.
Пратено со Tapatalk 2 од мојот SGSIII mini

vonuzu said:
And one more way, if you have rooted your phone, you can install an app like quick boot and use it for booting into recovery.
Пратено со Tapatalk 2 од мојот SGSIII mini
Click to expand...
Click to collapse
Added
Sent from my GT-I8190 using xda app-developers app

I dont understand how to do it with adb
Sent from my GT-I8190 using xda app-developers app

Sn0w0nS said:
I dont understand how to do it with adb
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Hi, I`m not ppero196 but how it works. Download this rar and extract on your PC. I always take the path to C:\Android\ . Then activate USB-Debugging on your device and connect your device to the PC. Open the cmd on your windows machine and type:
For download mode:
Code:
cd\
cd Android
adb reboot download
or for the recovery mode:
Code:
cd\
cd Android
adb reboot recovery
Have fun by the trying.
@ ppero196:
You write in the first post that:
Type adb reboot reccocery
Click to expand...
Click to collapse
Can you please fixed the command for reboot recovery? Thanks in advance.
Regards leather.face

Thx it worked.
Sent from my GT-I8190 using xda app-developers app

leather.face said:
Hi, I`m not ppero196 but how it works. Download this rar and extract on your PC. I always take the path to C:\Android\ . Then activate USB-Debugging on your device and connect your device to the PC. Open the cmd on your windows machine and type:
For download mode:
Code:
cd\
cd Android
adb reboot download
or for the recovery mode:
Code:
cd\
cd Android
adb reboot recovery
Have fun by the trying.
@ ppero196:
You write in the first post that:
Can you please fixed the command for reboot recovery? Thanks in advance.
Regards leather.face
Click to expand...
Click to collapse
All fixed
Sent from my GT-I8190 using xda app-developers app

No button combination?
Hello guys,
I can boot into recovery, pressing, up, home and power for a long time. The "Samsung Galaxy S3 Mini"-logo comes two times, and I press the three buttons all the time, until an "Android" comes. Than I am in Recovery mode. I haven't flashed or rooted my phone now, but is it not easier root and flash it via cutsom recovery mode?
Sorry for my bad English :/ If you habe some questions about my phone ask

What firmware are you running ??

It is the Original Samsung 4.1.1.

Can you post screenshot of "Settings->About device" page? Because on some devices (maybe from first batch) key combination just does not work.

Here is the Screenshot. I hope it helps.
{
"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 :good:

This is a great guide! In theory you can also do this:
- backup your lfs partition (/dev/block/mmcblk0p19) with adb+dd when the phone has booted normally, backup that file
- backup your lfs partition (/dev/block/mmcblk0p19) with adb+dd inside CWM, have the file on your PC as well
Now you can reflash the partition with Odin/Heimdall and have the phone boot into either mode. The reason is because this partition contains params.blk which itself contains the boot mode (along other important parameters). It is always a good idea to have a backup of this partition, as well as other partitions (notably efs = mmcblk0p11 and modemfs = mmcblk0p12).

xd.bx said:
This is a great guide! In theory you can also do this:
- backup your lfs partition (/dev/block/mmcblk0p19) with adb+dd when the phone has booted normally, backup that file
- backup your lfs partition (/dev/block/mmcblk0p19) with adb+dd inside CWM, have the file on your PC as well
Now you can reflash the partition with Odin/Heimdall and have the phone boot into either mode. The reason is because this partition contains params.blk which itself contains the boot mode (along other important parameters). It is always a good idea to have a backup of this partition, as well as other partitions (notably efs = mmcblk0p11 and modemfs = mmcblk0p12).
Click to expand...
Click to collapse
Yeah.
But some user may find it too complicated.
I may add this in the future
Sent from my GT-I8190 using xda app-developers app

Just want to confirm the same
tux95 said:
Hello guys,
I can boot into recovery, pressing, up, home and power for a long time. The "Samsung Galaxy S3 Mini"-logo comes two times, and I press the three buttons all the time, until an "Android" comes. Than I am in Recovery mode. I haven't flashed or rooted my phone now, but is it not easier root and flash it via cutsom recovery mode?
Click to expand...
Click to collapse
Pictures attached

Thanks for this guide very helpfull

didinn1, what firmware version was preinstalled on your phone when you bought it ?

b_henry said:
didinn1, what firmware version was preinstalled on your phone when you bought it ?
Click to expand...
Click to collapse
b_henry it was 4.1.1

Flashing a custom recovery

Hello! I know I have already posted a few threads about this, but I want to be 100% right, that's the only way to learn Android!
So I want to flash CWM touch recovery to my device, and I don't want to use any toolkits like I did before. The only thing I want to have from the toolkit now are drivers, because I won't uninstall them, seems pointless.
This is how I think you have to flash a recovery, but please correct me if I'm wrong!
1.Download fastboot files and place them in any directory (how many files are they? Do I have to extract them?
2.download customrecovery.img and place the file in the same directory as the fastboot files.
3.Open command prompt in that directory and type "fastboot flash recovery customrecovery.img"
Is this the full guide on how to install a recovery? Thanks in advance!
Sent from my Nexus 4 using xda app-developers app

In a nutshell, yes, you are correct. For more detailed answers:
1. Yes, place them in the same directory as your ADB drivers, that way you won't have to CD when switching between the two.
2. correct
3. this is correct, but you HAVE to be in bootloader mode.
So the order would be:
adb reboot bootloader
fastboot flash recovery customrecovery.img
Easy, and +1 for wanting to learn how to do things the proper way.

rickbosch said:
In a nutshell, yes, you are correct. For more detailed answers:
1. Yes, place them in the same directory as your ADB drivers, that way you won't have to CD when switching between the two.
2. correct
3. this is correct, but you HAVE to be in bootloader mode.
So the order would be:
adb reboot bootloader
fastboot flash recovery customrecovery.img
Easy, and +1 for wanting to learn how to do things the proper way.
Click to expand...
Click to collapse
Ok so the only files I need are adb drivers, fastboot drivers and the recovery. But do I have to extract any of them? Or just download and place them in the directory without changing the files?
Sent from my Nexus 4 using xda app-developers app

that would depend where you got them. I use this, because I don't want to download and install the SDK. Download the zip at the bottom of this post (http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1) named "platform-tools-v16.zip". Extract the contents to an easy to reach folder, I use C:\Android. Then when you want to use terminal commands shift+right click "open command window here", connect your device, ensure USB Debugging is on and that you've given ADB permissions when it asks for the RSA key. Then you can run "adb devices" to see if they work properly.

rickbosch said:
that would depend where you got them. I use this, because I don't want to download and install the SDK. Download the zip at the bottom of this post (http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1) named "platform-tools-v16.zip". Extract the contents to an easy to reach folder, I use C:\Android. Then when you want to use terminal commands shift+right click "open command window here", connect your device, ensure USB Debugging is on and that you've given ADB permissions when it asks for the RSA key. Then you can run "adb devices" to see if they work properly.
Click to expand...
Click to collapse
And when I've done all that I just have to reboot in bootloader mode and I can flash the recovery?
Sent from my Nexus 4 using xda app-developers app

Thibaultvw said:
And when I've done all that I just have to reboot in bootloader mode and I can flash the recovery?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Sent from my Nexus 4 using xda app-developers app

Thibaultvw said:
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
yessir.

Are ADB and fastboot correctly set up now? From now on I just have to download the recovery and I'm good to go?
{
"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"
}

Thibaultvw said:
Are ADB and fastboot correctly set up now? From now on I just have to download the recovery and I'm good to go?
Click to expand...
Click to collapse
Boot your phone into bootloader mode, connect your phone to your PC with USB cable, run command "fastboot devices" to check if the driver is properly setup. If you can see your device ID then it is good to go.
Else, download google usb drivers here: http://developer.android.com/sdk/win-usb.html

This guy says you have to wipe data/factory reset. I dont think thats needed right? Cause he actually wipes his OS right?
http://youtu.be/nb_MweQpGbQ

You don't have to flash the user data image, but it could result in not getting past the boot screen on initial boot.

http://forum.xda-developers.com/showthread.php?t=2266654
Install Custom Recovery
We’ve 2 custom recoveries available yet for our Nexus 4 viz ClockworkMod and TWRP. ClockworkMod or CWM (in short) comes in 2 variants (Touch UI based & Non-Touch UI based). Below I have mentioned on how to flash each one of them using fastboot. For more info about these two recoveries, visit ClockworkMod and TeamWin websites.
Reboot your device into bootloader mode. Either manually, by powering off and then pressing Volume Down + Power buttons simultaneously or using the following command in CMD/Terminal.
Code:
adb reboot bootloader
Download the latest build of your desired recovery [CWM | TWRP]
Place the downloaded recovery image (.img) file on your desktop.
If in Windows, open CMD and cd it to the desktop using the following command
Code:
cd Desktop
If in OS X or Linux, open terminal and cd it to the desktop using the following command
Code:
cd ~/Desktop
To flash ClockworkMod Non-Touch, type in the following command:
Code:
fastboot flash recovery recovery-clockwork-x.x.x.x-mako.img
Replace x.x.x.x with the recovery build no. that you downloaded.
To flash ClockworkMod Touch, type in the following command:
Code:
fastboot flash recovery recovery-clockwork-touch-x.x.x.x-mako.img
Replace x.x.x.x with the recovery build no. that you downloaded.
To flash TWRP, type in the following command:
Code:
fastboot flash recovery openrecovery-twrp-x.x.x.x-mako.img
Replace x.x.x.x with the recovery build no. that you downloaded.
Once flashed, you will prompted on the CMD/Terminal itself.
Now, either reboot your device by using volume keys to highlight Reboot and select using Power button or reboot into the recovery by selecting Recovery mode.
Voila! The next to follow is to root or directly flash a Custom ROM, which is already rooted

And do I have to do a factory reset when that is done?

Thibaultvw said:
And do I have to do a factory reset when that is done?
Click to expand...
Click to collapse
Nope.
If you boot into recovery and see an android lying out with exclamation mark, use "fastboot format cache" in bootloader mode.

ksilver89 said:
Nope.
If you boot into recovery and see an android lying out with exclamation mark, use "fastboot format cache" in bootloader mode.
Click to expand...
Click to collapse
You mean if it boots in stock recovery?
Sent from my Nexus 4 using xda app-developers app

Thibaultvw said:
You mean if it boots in stock recovery?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
That will only happens when you use stock rom with install-recovery.sh. if you plan to use custom ROM, safely ignore it.

ksilver89 said:
That will only happens when you use stock rom with install-recovery.sh. if you plan to use custom ROM, safely ignore it.
Click to expand...
Click to collapse
I am currently running the stock rom without any mods, so CWM will stick?
And yes I'm planning to get back my old love CM as soon as it updates to 4.3
Sent from my Nexus 4 using xda app-developers app

Thibaultvw said:
I am currently running the stock rom without any mods, so CWM will stick?
And yes I'm planning to get back my old love CM as soon as it updates to 4.3
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This is getting complication since the introduction of new rooting method for 4.3.....
A: You don't want root
Answer yes if CWM ask you to rename install-recovery.sh, otherwise it won't stick.
B: You want to root with SuperSU
After flashing SuperSU zip, answer No if CWM ask you to rename install-recovery.sh, because the file is modified by SuperSU and it is needed for the root to work.

ksilver89 said:
This is getting complication since the introduction of new rooting method for 4.3.....
A: You don't want root
Answer yes if CWM ask you to rename install-recovery.sh, otherwise it won't stick.
B: You want to root with SuperSU
After flashing SuperSU zip, answer No if CWM ask you to rename install-recovery.sh, because the file is modified by SuperSU and it is needed for the root to work.
Click to expand...
Click to collapse
I want root, so after flashing the supersu zip CWM will ask me? All right!
Will it ask me always after flashing something?
Sent from my Nexus 4 using xda app-developers app

Thibaultvw said:
I want root, so after flashing the supersu zip CWM will ask me? All right!
Will it ask me always after flashing something?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It will ask every time when you want to reboot from CWM. Alternatively, you can use twrp.

[Q] Cannot flash recovery or rsd anything on unlocked xt907

I flashed the fxz gpe(after flashing the official first) a few weeks ago on my daughter's phone. It worked well until one night she said there were issues. It would not stop force closing just about every app. I did not have a custom recovery on it at that time. I have since attempted to rsd the gpe, the official fxz, a custom recovery. I have used fastboot commands to attempt to wipe userdata etc. All of these say successful, but it reboots back to the broken gpe each time. When I try to use adb shell to mount system it tells me permission denied. Note, this phone is being used as a media and game device, so no sim card and is in airplane mode with wifi on generally. Any ideas guys?

What does rsdlite say when you attempt to flash the official from the Motorola firmware It doesn't make sense that (if it does) when you rsd the official that it boots back to the broken gpe... You could try house of moto and see if it works any better
Sent from my XT907 using XDA Premium 4 mobile app

ezknives said:
What does rsdlite say when you attempt to flash the official from the Motorola firmware It doesn't make sense that (if it does) when you rsd the official that it boots back to the broken gpe... You could try house of moto and see if it works any better
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
After rebooting it back to the bootloader it says pass. House of Moto did not work either unfortunately. I also used his RSD flasher. You are absolutely right when you say it doesn't make sense. That is why I am baffled at this point. I am able only to get in to settings if I am quick enough(launcher crashes if I hit home), I just tried to switch to dalvic as I noticed it was on Art. However when it rebooted, it went back to Art still...

Try booting to recovery as its stock recovery factory reset and clear cache partition then when you select reboot immediately hold the volume up n down then go straight to the fastboot screen from that menu and rsd the official from there... Let us know (I know how important it is to get it working I have a 2 year old with a droid 4 and its the end of the world when it dies I can't imagine if I were in your position...)
Sent from my XT907 using XDA Premium 4 mobile app

Custom Recovery
jamminjon82 said:
I flashed the fxz gpe(after flashing the official first) a few weeks ago on my daughter's phone. It worked well until one night she said there were issues. It would not stop force closing just about every app. I did not have a custom recovery on it at that time. I have since attempted to rsd the gpe, the official fxz, a custom recovery. I have used fastboot commands to attempt to wipe userdata etc. All of these say successful, but it reboots back to the broken gpe each time. When I try to use adb shell to mount system it tells me permission denied. Note, this phone is being used as a media and game device, so no sim card and is in airplane mode with wifi on generally. Any ideas guys?
Click to expand...
Click to collapse
When you're flashing anything, it's a good idea to return to factory settings first & flash a clean stock rom. But when you flash a custom recovery, you need to make sure that it doesn't boot up normally after it's done. If it boots normally it will replace your custom recovery with stock recovery. To avoid this, as soon as its done flashing and begins the normal boot process, press power&volumeup&down simultaneously and scroll down to recovery and go into this. After you do this once, you shouldn't face anymore problems.:good:

ezknives said:
Try booting to recovery as its stock recovery factory reset and clear cache partition then when you select reboot immediately hold the volume up n down then go straight to the fastboot screen from that menu and rsd the official from there... Let us know (I know how important it is to get it working I have a 2 year old with a droid 4 and its the end of the world when it dies I can't imagine if I were in your position...)
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
PrankCallPimp said:
When you're flashing anything, it's a good idea to return to factory settings first & flash a clean stock rom. But when you flash a custom recovery, you need to make sure that it doesn't boot up normally after it's done. If it boots normally it will replace your custom recovery with stock recovery. To avoid this, as soon as its done flashing and begins the normal boot process, press power&volumeup&down simultaneously and scroll down to recovery and go into this. After you do this once, you shouldn't face anymore problems.:good:
Click to expand...
Click to collapse
Just tried all of these suggestions and still have stock recovery and rebooting back to the same busted google play edition rom.

OK...just to be clear your using the 6.1.6 rsd lite and the 183.46.10 from sbf devoplers.org... Booting into fastboot letting rsd do its thing then allowing rsd boot the device and when it does it boots to the broken gpe?... let's see if more experienced individuals have an idea @RikRong @ATTACK
Sent from my XT907 using XDA Premium 4 mobile app

That's correct, also have redownloaded numerous times to verify that it didn't happen to be corrupt
Sent from my VS980 4G using Tapatalk

jamminjon82 said:
That's correct, also have redownloaded numerous times to verify that it didn't happen to be corrupt
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Try and flash recovery with mfastboot but boot straight into recovery, then try and flash CM11 nightly.
Type
Code:
mfastboot flash recovery <recovery name>.img
Then
Code:
mfastboot reboot
as soon as you hit enter, press & hold volume up (+) which will take you into recovery.

{
"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"
}
still takes me back to this after following those commands
Sent from my VS980 4G using Tapatalk

commands I'm putting in
Sent from my VS980 4G using Tapatalk

jamminjon82 said:
still takes me back to this after following those commands
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Did you run CMD with administrator rights?

ATTACK said:
Did you run CMD with administrator rights?
Click to expand...
Click to collapse
Just did and no luck
Sent from my VS980 4G using Tapatalk

jamminjon82 said:
Just did and no luck
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Have you tried to mfastboot the images separately?
Code:
mfastboot flash...
Code:
modem NON-HLOS.bin
erase modemst1
erase modemst2
boot boot.img
recovery recovery.img
system system.img
erase cache
erase userdata

Just did and still booting into the same gpe Rom
Is there any more info that I can give you that would help us figure out what the heck is going on with this thing?
Sent from my VS980 4G using Tapatalk

jamminjon82 said:
Just did and still booting into the same gpe Rom
Is there any more info that I can give you that would help us figure out what the heck is going on with this thing?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
When you did mfastboot reboot, did it reboot?
Have you tried other USB ports?
Did you get any errors with mfastboot?

Yes it reboots,zero errors reported
Sent from my VS980 4G using Tapatalk

Switched ports
Same as before
Sent from my VS980 4G using Tapatalk

Don't know if this info helps
Sent from my VS980 4G using Tapatalk

jamminjon82 said:
Don't know if this info helps
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
If you could would you please try this, I would like to see if ADB reads your partitions.
Boot to the OS and make sure ADB is on.
In CMD type
Code:
adb shell
Except the dialog that pops up on your phone.
Then Type
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name

Can't sideload anything (No rom installed; Tried everything)

Hello people, basically I'm experiencing a problem in which no ROMS will install and I have nothing on the phone itself to fall back on (all partitions wiped.)
I'm using the latest drivers, but the phone has a problem receiving commands via the bootloader for some reason. I've tried side-loading, flashing a zip normally, using the "Flash stock+unroot option" all via the "Nexus Root Tool-kit"; I've tried using the command prompt through Android SDK's ADB flashing tool, but it didn't work.
While trying to side-load via the Nexus root tool-kit it doesn't work, however while sending the command to boot into stock recovery it does show "downloading..." text at the bottom of the screen, but it freezes up and I have to hold power+volume down to get back into the bootloader successfully.
While trying to side-load via the command prompt through ADB side-loading (SDK) however, it recognizes my device and tries to install zip files but says at 1%, 2%, and 4% (depending on the file) and nothing really happens and after I cancel the sideload it says "can't open /tmp/update.zip (bad)", I then tried finding an update.zip file for the recovery but that didn't side-load either (nor TWRP; my preferred recovery)
This all happened after I stupidly downloaded+installed a previous version of CyanogenMod in which afterwards no processes would work, so I factory reset it and nothing's working (here I am.) Early on I hit root on the clockwork mod since it said it wasn't rooted (I hit it anyway, hence it already being rooted), that may be why I can't do anything in the first place (I did this before I even tried flashing a zip); I then wiped all of the partitions this morning, and no changes. I've also tried all 3 drivers for the Google bootloader (Naked drivers)
I'm using Clockwork recovery 6.0.5.0 legacy (non-touch) and have a Nexus 4 that's unlocked+rooted.
Please help, I've tried everything and have spent hours on end with Google searches and troubleshooting to try to fix this.

Have you tried the flash-all.bat file in the factory image while booted into fastboot?
Sent from my Nexus 5 using XDA Free mobile app

Don't see it
jd1639 said:
Have you tried the flash-all.bat file in the factory image while booted into fastboot?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I don't see a .bat file in either the the stock or liquidsmooth rom. Could you point me to a rom that has one so I may try this? Thanks

xXDustinoXx said:
I don't see a .bat file in either the the stock or liquidsmooth rom. Could you point me to a rom that has one so I may try this? Thanks
Click to expand...
Click to collapse
Google nexus 4 factory image. Download that and extract it using winrar or 7-zip
Sent from my Nexus 5 using XDA Free mobile app

Nothing...
jd1639 said:
Google nexus 4 factory image. Download that and extract it using winrar or 7-zip
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Darn, I was hoping it was going to work; On my phone in the command line it says:
(Before I sent the file)
sideload started...
Now send the package you want to apply
to the device with "adb sideload <filename>
(after I sent the file):
Restarting adbd...
Finding update package...
Opening update package...
E:/can't open /ta[/update.zip
(bad) (there's that error again, except it almost worked)
Installation aborted.

xXDustinoXx said:
Darn, I was hoping it was going to work; On my phone in the command line it says:
(Before I sent the file)
sideload started...
Now send the package you want to apply
to the device with "adb sideload <filename>
(after I sent the file):
Restarting adbd...
Finding update package...
Opening update package...
E:/can't open /ta[/update.zip
(bad) (there's that error again, except it almost worked)
Installation aborted.
Click to expand...
Click to collapse
Just boot into the bootloader with your device connected and double click the bat file. Don't boot into recovery and try to side load it
Sent from my Nexus 5 using XDA Free mobile app

"Downloading"
jd1639 said:
Just boot into the bootloader with your device connected and double click the bat file. Don't boot into recovery and try to side load it
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The bootloader freezes up and shows "downloading..." on the screen
{
"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"
}

xXDustinoXx said:
The bootloader freezes up and shows "downloading..." on the screen
Click to expand...
Click to collapse
image url attatched for command prompt picture
What should I do?

xXDustinoXx said:
image url attatched for command prompt picture
What should I do?
Click to expand...
Click to collapse
I'm on my phone and can't see your image. What does it say?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I'm on my phone and can't see your image. What does it say?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It says:
sending 'bootloader; <2500KB>...
FAILED <data transfer failure <unknown error>>
finsihed. total time:5.007s
rebooting into bootloader...
All the while the device is trying to download the data but freezes up as if it can't accept unsigned code (unrooted)?

xXDustinoXx said:
It says:
sending 'bootloader; <2500KB>...
FAILED <data transfer failure <unknown error>>
finsihed. total time:5.007s
rebooting into bootloader...
All the while the device is trying to download the data but freezes up as if it can't accept unsigned code (unrooted)?
Click to expand...
Click to collapse
Are you trying to flash while booted into recovery? You don't want to be in recovery, just the bootloader, vol down + power
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Are you trying to flash while booted into recovery? You don't want to be in recovery, just the bootloader, vol down + power
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I was doing it with the bootloader, and I did try it via the adb side load just to see if that'd work after the bootloader wouldn't work

xXDustinoXx said:
Yes, I was doing it with the bootloader, and I did try it via the adb side load just to see if that'd work after the bootloader wouldn't work
Click to expand...
Click to collapse
Then you have something wrong with your device. If you try to relock the boot loader does it stay locked or does it remain unlocked?
fastboot oem lock
Then
fastboot oem device-info
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Then you have something wrong with your device. If you try to relock the boot loader does it stay locked or does it remain unlocked?
fastboot oem lock
Then
fastboot oem device-info
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It was the cord the entire time, that was it! Can't believe that after all of these hours! It's now booting into android! Thanks so much for your help, greatly appreciated

xXDustinoXx said:
It was the cord the entire time, that was it! Can't believe that after all of these hours! It's now booting into android! Thanks so much for your help, greatly appreciated
Click to expand...
Click to collapse
Glad you got it working. Go figure, the cord
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Glad you got it working. Go figure, the cord
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, I know right! Thanks again

[SOLVED SEEING RELINK INSTEAD OF QUALCOM] HELP!! OS GONE and NO TWRP

UPDATE: SOLVED THE RELINK PROBLEM AND UNBRICKED MY PHONE
Hi can someone help..
my phone was rooted and I was trying to flash the latest OTA but I accidentally deleted the partition or something idk... so TWRP said no OS installed so I couldn't boot my phone.
And then i followed some guides around and then that turns into me cant access the TWRP anymore.
What I can do left now is get it into fastboot. Can anyone help how to get my OPT alive?
From what I've been reading I need to use 'fastboot flash update ____". is this right? but i don't have the file. or at least i think i don't. i downloaded 2.2.0 signed flashable zip but when i tried to c:adb> fastboot flash update OnePlus2Oxygen_14_OTA_011_all_1512111634.zip it said "error: cannot determine image"
All help appreciated!! I'm sorry if this problem has been asked before but I tried to search solutions myself but ended getting one problem after another so i decided to ask.. thank you.

first flash twrp
then boot into twrp
connect your phone to pc you will able to see your internal storage
copy your OS to internal storage
flash it

sudhakarstoopy said:
first flash twrp
then boot into twrp
connect your phone to pc you will able to see your internal storage
copy your OS to internal storage
flash it
Click to expand...
Click to collapse
This looks very promising but when i tried "fastboot flash recovery twrp-2.8.7.0-oneplus2.img" it "FAILED: device is locked. cannot flash images"

Did you try to unlock the boot loader again?
Sent from my ONE A2003 using Tapatalk

sudhakarstoopy said:
Did you try to unlock the boot loader again?
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Is it the "fastboot oem unlock"? it didn't work "remote: oem unlock is disabled" is there another way?

Okay now tell me what you did after you wiped your OS unknowingly ? ..
Sent from my ONE A2003 using Tapatalk

sudhakarstoopy said:
Okay now tell me what you did after you wiped your OS unknowingly ? ..
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
I can't remember for certain but I think I went into TWRP and tried to flash the OTA update ONLY and not the full OS version (but by now there is already "No OS installed" message on TWRP) and when it didn't work i reboot system and couldn't get into twrp anymore.

https://forums.oneplus.net/threads/...-of-oxygen-os-2-0-for-oneplus-2.378300/page-2
Check this thread ... In 2nd page that guy have fastboot image get from him and try to flash the system image from fastboot ... All the best
Sent from my ONE A2003 using Tapatalk

sudhakarstoopy said:
https://forums.oneplus.net/threads/...-of-oxygen-os-2-0-for-oneplus-2.378300/page-2
Check this thread ... In 2nd page that guy have fastboot image get from him and try to flash the system image from fastboot ... All the best
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Thank you so much. Hopefully they see my message.
In the meantime, anyone has other fix to recommend? T_T

skarfy said:
Thank you so much. Hopefully they see my message.
In the meantime, anyone has other fix to recommend? T_T
Click to expand...
Click to collapse
With pleasure
Sent from my ONE A2003 using Tapatalk

sudhakarstoopy said:
With pleasure
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Apparently it's already uploaded here. Do you know how to fix it now?

http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Dont know if this could work?

skarfy said:
Apparently it's already uploaded here. Do you know how to fix it now?
Click to expand...
Click to collapse
This will work... Download every file. extract them and put it in a single folder .. Connect your mobile in a fastboot and try to flash every single file individually
Refer these commands but these are not for oxygen os just for reference
''fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64G.img"
Sent from my ONE A2003 using Tapatalk

oediv said:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Dont know if this could work?
Click to expand...
Click to collapse
I tried this, got stuck at step 7. Hoping for a reply on the thread.
sudhakarstoopy said:
This will work... Download every file. extract them and put it in a single folder .. Connect your mobile in a fastboot and try to flash every single file individually
Refer these commands but these are not for oxygen os just for reference
''fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64G.img"
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Does the sequence matter or I can flash in any way I can?

skarfy said:
I tried this, got stuck at step 7. Hoping for a reply on the thread.
Does the sequence matter or I can flash in any way I can?
Click to expand...
Click to collapse
What happened at Step 7?
I unbricked my phone using that same guide.

tarun123t said:
What happened at Step 7?
I unbricked my phone using that same guide.
Click to expand...
Click to collapse
"7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install."
It said "the best driver is already installed" but I still can't find my phone in "MSM8994DownloadTool.exe".

skarfy said:
"7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install."
It said "the best driver is already installed" but I still can't find my phone in "MSM8994DownloadTool.exe".
Click to expand...
Click to collapse
have you tried manually updating the driver by selecting the file from QC folder?
---------- Post added at 07:53 PM ---------- Previous post was at 07:51 PM ----------
Step 6. Connect your OnePlus 2 to PC with USB cable. Then open ‘Device manager’. Hold volume + and power until your PC finds a new hardware (if it doesn’t work, try hold volume+ and volume- together). Now, find the item by the name of ‘QUALCOMM-HS USB Diagnostics 9006’. That’s your OnePlus 2.
Step 7. Now right click on it, and select ‘update driver’. Select ‘browse’ button and go to and select the folder where you extracted driver file’s in step 1. Update its driver using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder). Now this will install the new drivers for your Oneplus 2.

tarun123t said:
have you tried manually updating the driver by selecting the file from QC folder?
---------- Post added at 07:53 PM ---------- Previous post was at 07:51 PM ----------
Step 6. Connect your OnePlus 2 to PC with USB cable. Then open ‘Device manager’. Hold volume + and power until your PC finds a new hardware (if it doesn’t work, try hold volume+ and volume- together). Now, find the item by the name of ‘QUALCOMM-HS USB Diagnostics 9006’. That’s your OnePlus 2.
Step 7. Now right click on it, and select ‘update driver’. Select ‘browse’ button and go to and select the folder where you extracted driver file’s in step 1. Update its driver using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder). Now this will install the new drivers for your Oneplus 2.
Click to expand...
Click to collapse
Is this it?
{
"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"
}
and then I browse here "C:\Users\skrfy\Desktop\qc" and ticked "include subfolders". Is this right?
I did that step and it said already have the best driver installed. But my phone still doesn't appear in MSM8994DownloadTool

skarfy said:
I tried this, got stuck at step 7. Hoping for a reply on the thread.
Does the sequence matter or I can flash in any way I can?
Click to expand...
Click to collapse
Sequence doesn't matter
Sent from my ONE A2003 using Tapatalk

skarfy said:
Is this it?
and then I browse here "C:\Users\skrfy\Desktop\qc" and ticked "include subfolders". Is this right?
I did that step and it said already have the best driver installed. But my phone still doesn't appear in MSM8994DownloadTool
Click to expand...
Click to collapse
That's weird. Same thing worked for me a week ago.