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

Why do I get this icon when trying to root my N4 ?

So I followed the instructions in this link so I could root my N4:
http://www.androidrootz.com/2012/11/how-to-root-nexus-4-on-mac.html
I get this when I reach the point in the video where he instructs me to enter recovery mode.. why ?
{
"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"
}

You aren't flashing your recovery properly in bootloader mode.
fastboot flash recovery <nameofrecovery>.img
Choose either: Clockwork Recovery of Team Win Recovery Project (TWRP) as your recovery. Put the .img file in the same folder as fastboot.exe.
I recommend TWRP.
So for example,
http://teamw.in/project/twrp2/129 Scroll down to recovery image method
Place the .img file in the same as fastboot
go into bootloader mode on your phone
fastboot flash recovery openrecovery-twrp-2.3.3.2-mako.img
it should say sending.... then done!
then use vol keys and you should be able to get into bootloader and the android with red ! isnt there.
And thank you for not using the toolkit <3

zephiK said:
You aren't flashing your recovery properly in bootloader mode.
fastboot flash recovery <nameofrecovery>.img
Choose either: Clockwork Recovery of Team Win Recovery Project (TWRP) as your recovery. Put the .img file in the same folder as fastboot.exe.
I recommend TWRP.
So for example,
http://teamw.in/project/twrp2/129 Scroll down to recovery image method
Place the .img file in the same as fastboot
go into bootloader mode on your phone
fastboot flash recovery openrecovery-twrp-2.3.3.2-mako.img
it should say sending.... then done!
then use vol keys and you should be able to get into bootloader and the android with red ! isnt there.
And thank you for not using the toolkit <3
Click to expand...
Click to collapse
This did not work

You have the latest version of Android Fastboot Binary? Bootloader unlocked?
.img file in the fastboot-mac folder
The error is pipe properties. Whatever that is.

BLL00 said:
This did not work
Click to expand...
Click to collapse
Check my post (#13) in this thread. http://forum.xda-developers.com/showthread.php?t=1997684
If you received an ota you have to delete a couple files to get the recovery to stick.
Edit: the pic I quoted didn't show up in the app. I'm not sure what that error means.
Sent from my Nexus 7 using Tapatalk HD

my problem is that after i flash recovery-clockwork-6.0.1.9-mako.img, it refuses to enter cmw and shows the icon I showed in my picture.

BLL00 said:
my problem is that after i flash recovery-clockwork-6.0.1.9-mako.img, it refuses to enter cmw and shows the icon I showed in my picture.
Click to expand...
Click to collapse
When you type fastboot-mac devices... your device shows up right?

zephiK said:
When you type fastboot-mac devices... your device shows up right?
Click to expand...
Click to collapse

BLL00 said:
Click to expand...
Click to collapse
Hmm okay well I don't know how a mac works. I know that you don't need drivers. I'm going to say that it's something wrong with the fastboot binary file. It's the error that you're seeing there. On the guide you used, the error is nonexistant in his picture. Bootloader is unlocked right?
You have the latest version of Android Fastboot Binary? Bootloader unlocked?
.img file in the fastboot-mac folder
The error is pipe properties. Whatever that is.
Click to expand...
Click to collapse
ensure USB debugging is enabled as well.

zephiK said:
Hmm okay well I don't know how a mac works. I know that you don't need drivers. I'm going to say that it's something wrong with the fastboot binary file. It's the error that you're seeing there. On the guide you used, the error is nonexistant in his picture. Bootloader is unlocked right?
Click to expand...
Click to collapse
-Yeah I unlocked my bootloader.
-The pipe properties error is gone, it was just a matter of switching usb ports!
I need to mention that when I flashed the cmw img and hit start on the fastboot menu, IT DID in fact enter cmw, but somewhere in there, I think I've done something wrong and my phone restarted normally. Now, I upload the zip file into the sdcard path and restart my phone into fastboot again, when I hit recovery mode, it then shows that icon!

BLL00 said:
-Yeah I unlocked my bootloader.
-The pipe properties error is gone, it was just a matter of switching usb ports!
I need to mention that when I flashed the cmw img and hit start on the fastboot menu, IT DID in fact enter cmw, but somewhere in there, I think I've done something wrong and my phone restarted normally. Now, I upload the zip file into the sdcard path and restart my phone into fastboot again, when I hit recovery mode, it then shows that icon!
Click to expand...
Click to collapse
Did you read my post?
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Click to expand...
Click to collapse

El Daddy said:
Did you read my post?
Click to expand...
Click to collapse
yes i did and if you noticed in the photo i uploaded, there's an iphone under my nexus 4 so I'm VERY new to this. I couldn't find the system path ???

BLL00 said:
yes i did and if you noticed in the photo i uploaded, there's an iphone under my nexus 4 so I'm VERY new to this. I couldn't find the system path ???
Click to expand...
Click to collapse
You have to use a app that has root functionality. Go outside of the /sdcard/ folder and go into /system/
So basically here's what you want to do. By the way good job at switching USB port and having that work.
- Flash CWR
- Flash the superuser zip file to obtain root
- download a file manager that lets you go outside /sdcard/ and then go to the path el daddy mentioned and delete those files.
https://play.google.com/store/apps/...yLDEsImNvbS5qcnVtbXkucm9vdC5icm93c2VyZnJlZSJd here is a file manager you can use.
basically press "..." and go into /system/etc/ find file install-recovery.sh
and/or /system/ and find file recovery-from-boot.p
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
@El Daddy: He's just a little new. Don't be so harsh (you probably weren't and thought he didn't see it), I mean after all he didn't use the toolkit so, I have respect for him.

the first path is /system/etc/ delete install-recovery.sh
the path to the other file is /system/ find recovery-from-boot.p and delete that
You'll need root access first.
So basically, flash the custom recovery then boot into recovery.
Flash the su.zip file.
Boot into the OS and use a file explorer and delete those files.
Then the custom recovery will stick.
---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------
zephiK said:
@El Daddy: He's just a little new. Don't be so harsh (you probably weren't and thought he didn't see it), I mean after all he didn't use the toolkit so, I have respect for him.
Click to expand...
Click to collapse
I didn't mean to come off harsh. Sometimes demeanor doesn't translate well through text.

El Daddy said:
the first path is /system/etc/ delete install-recovery.sh
the path to the other file is /system/ find recovery-from-boot.p and delete that
You'll need root access first.
So basically, flash the custom recovery then boot into recovery.
Flash the su.zip file.
Boot into the OS and use a file explorer and delete those files.
Then the custom recovery will stick.
---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------
I didn't mean to come off harsh. Sometimes demeanor doesn't translate well through text.
Click to expand...
Click to collapse
Yeah agreed. Same goes with sarcasm in text. Just takes some patience with the new people, but I honestly don't mind as this is the Q&A section after all. As long as they're not using the toolkit I won't be upset hehe

zephiK said:
Yeah agreed. Same goes with sarcasm in text. Just takes some patience with the new people, but I honestly don't mind as this is the Q&A section after all. As long as they're not using the toolkit I won't be upset hehe
Click to expand...
Click to collapse
Yep. I'm willing to help anyone, (for as long as it takes) who wants to put the time in and learn. Anyone not using a toolkit is a win for me. :laugh:

El Daddy said:
Yep. I'm willing to help anyone, (for as long as it takes) who wants to put the time in and learn. Anyone not using a toolkit is a win for me. :laugh:
Click to expand...
Click to collapse
Amen, amen. Free training for these people to help others the non-toolkit way so people like us can take a break and relax

Thanks everybody for helping out. I managed to root my phone and this is what I have done to bypass that android logo with it chest open and a "!" floating on top of it:
1-Restarted phone into fastboot mode
2-Flashed CWR's .img
3-Went straight into recovery mode after flashing and was able to enter CMW and complete the procedure.

Next thing you wanna do is GET RID OF THAT TASK MANAGER! Let android work its magic... Enjoy !
Sent from my Nexus 4 using Tapatalk 2

Just to mention when you fastboot flash or use goo manager for twrp recovery it will automatically add .bak to the recovery- from-boot.p file
Sent from my Nexus 4

Root 4.3

TWRP for flo has been released! http://forum.xda-developers.com/showthread.php?t=2380100
{
"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"
}
Root
1.) Download TWRP http://www.teamw.in/project/twrp2/193
2.) Download SuperSu for 4.3 here BUT SAVE ON DEVICE: https://plus.google.com/113517319477420052449/posts/GjbpgDdF6Fq
3.) Reboot to bootloader with either turning device on and holding POWER + VOL DOWN or under "About Tablet" > Tap "Build Number" 7 times > Back out > "Developer Options" > Check USB Debugging. Then in CMD Prompt/Terminal, type "adb reboot bootloader" without quotes
4.) In CMD prompt/Terminal type fastboot boot openrecovery-twrp-2.6.0.0-flo.img
5.) Click Backup - Backup boot, recovery, system and data
6.) Install > Download > UPDATE-SuperSU-v1.43.zip
7.) Reboot system
OPTIONAL
8.) Go back to bootloader after root and fully flash recovery with fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
Or alternatively via ADB,
1.) Download TWRP http://www.teamw.in/project/twrp2/193
2.) Download SuperSu for 4.3 here: https://plus.google.com/113517319477420052449/posts/GjbpgDdF6Fq
3.) Reboot to bootloader with either turning device on and holding POWER + VOL DOWN or under "About Tablet" > Tap "Build Number" 7 times > Back out > "Developer Options" > Check USB Debugging. Then in CMD Prompt/Terminal, type "adb reboot bootloader" without quotes
4.) In CMD prompt/Terminal type fastboot boot openrecovery-twrp-2.6.0.0-flo.img
5.) Click Backup - Backup boot, recovery, system and data
6.) Advanced > ADB Sideload > Wipe both caches > Swipe to start ADB
7.) On desktop in cmd prompt > adb sideload /blah/blah/blah/UPDATE-SuperSU-v.1.43.zip
8.) Reboot system
OPTIONAL
9.) Go back to bootloader after root and fully flash recovery with fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img

It's actually much easier than doing all that.
1) Download Chainfires latest root and copy to SD card
2) Download TWRP
3) With tablet on, all drivers installed and Android SDK, and tablet plugged into PC... "ADB reboot bootloader"
4) rename the recovery you downloaded from TWRP to "recovery.img" and make sure you've copied it to your ADB folder
5) Type "fastboot flash recovery recovery.img" minus the quotes
6) use volume and power keys to select "recovery"
7) Once in TWRP flash SuperSU/UPDATE-SuperSU-v1.43.zip
8) when you reboot Superuser will be updated automatically by the Play Store
Nice tut btw!

ATGAdmin said:
-snip
Click to expand...
Click to collapse
That's the same thing just with renaming mate. I also prefer not to flash recovery fully until factory images are out, hence why I ask to backup first.

Nburnes said:
That's the same thing just with renaming mate. I also prefer not to flash recovery fully until factory images are out, hence why I ask to backup first.
Click to expand...
Click to collapse
yeah and minus the sideload...whatever floats your boat.
Thanks for posting it!

ATGAdmin said:
It's actually much easier than doing all that.
1) Download Chainfires latest root and copy to SD card
2) Download TWRP
3) With tablet on, all drivers installed and Android SDK, and tablet plugged into PC... "ADB reboot bootloader"
4) rename the recovery you downloaded from TWRP to "recovery.img" and make sure you've copied it to your ADB folder
5) Type fastboot flash recovery recovery.img
6) use volume and power keys to select "recovery"
7) Once in TWRP flash SuperSU/UPDATE-SuperSU-v1.43.zip
8) when you reboot Superuser will be updated automatically by the Play Store
Nice tut btw!
Click to expand...
Click to collapse
worked perfectly for mine, way easier and thanks!

Hope to see a video on this soon, I like to watch it being done as I do it!
Sent from my Nexus 7 using Tapatalk HD

Hell yes. Got my tablet today...unlocked, rooted, and have TWRP installed by dinner time.

Nburnes, thank you for your contribution. Any, and all help is appreciated. However, ATG's instructions are a little clearer, and easier. I have had my new Nexus for less then 12 hours, and it is already unlocked, and rooted. Yee-Haw! :good: Now bring on those ROMs!
Thanks, guys.

Thank you so much!
Rooted now and was able to get OTG to recognize 2 flashdrives simultaneously.

Thanks for the instructions ATGAdmin. Successfully unlocked, installed TWRP, and rooted in a matter of minutes!

Nburnes said:
TWRP for flo has been released! http://forum.xda-developers.com/showthread.php?t=2380100
Root
1.) Download TWRP http://www.teamw.in/project/twrp2/193
2.) Download SuperSu for 4.3 here BUT SAVE ON DEVICE: https://plus.google.com/+Chainfire/posts/Jkuu84odnx6
3.) fastboot boot recovery openrecovery-twrp-2.6.0.0-flo.img
4.) Click Backup - Backup boot, recovery, system and data
5.) Install > Download > UPDATE-SuperSU-v1.43.zip
6.) Reboot system
OPTIONAL
7.) Go back to bootloader after root and fully flash recovery with fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
Or alternatively via ADB,
1.) Download TWRP http://www.teamw.in/project/twrp2/193
2.) Download SuperSu for 4.3 here: https://plus.google.com/+Chainfire/posts/Jkuu84odnx6
3.) fastboot boot recovery openrecovery-twrp-2.6.0.0-flo.img
4.) Click Backup - Backup boot, recovery, system and data
5.) Advanced > ADB Sideload > Wipe both caches > Swipe to start ADB
6.) On desktop in cmd prompt > adb sideload /blah/blah/blah/UPDATE-SuperSU-v.1.43.zip
7.) Reboot system
OPTIONAL
8.) Go back to bootloader after root and fully flash recovery with fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
Click to expand...
Click to collapse
ATGAdmin said:
It's actually much easier than doing all that.
1) Download Chainfires latest root and copy to SD card
2) Download TWRP
3) With tablet on, all drivers installed and Android SDK, and tablet plugged into PC... "ADB reboot bootloader"
4) rename the recovery you downloaded from TWRP to "recovery.img" and make sure you've copied it to your ADB folder
5) Type fastboot flash recovery recovery.img
6) use volume and power keys to select "recovery"
7) Once in TWRP flash SuperSU/UPDATE-SuperSU-v1.43.zip
8) when you reboot Superuser will be updated automatically by the Play Store
Nice tut btw!
Click to expand...
Click to collapse
either way, anyone will appreciate the step by step procedure, so thanks to you both!

Got it rooted and working great thanks, let me use titanium backup now
Sent from my Nexus 7 using xda app-developers app

bring on the custom roms!!!!

Thanks guys everything worked flawlessly and tb worked great
Sent from my Nexus 7 using Tapatalk 2

got it, stupid filename crap, needed to add .img to the .img

dems86 said:
got it, stupid filename crap, needed to add .img to the .img
Click to expand...
Click to collapse
D'oh!

Mine is still giving me the error saying "error: cannot load 'recovery.img': No Error"
Nevermind I'm an idiot! I didn't put the recovery file in the right area!

adb devices
does not show anything, are there specific drivers for the nexus 7 2013, if so where would I locate them, cannot seem to find anything yet via simple searches('nexus 7 2013 driver", "nexus 7 driver", "adb nexus 7 2013", etc...)
anyone got a simple solution to connect adb to the nexus 7 2013?

Did & done! Thanks!
Sent from my Nexus 7²

Thanks a million!

Unbrick method.

So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder.
{
"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"
}
Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.

eg0097 said:
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder. Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
Click to expand...
Click to collapse
Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
pl. help

subodhverma21 said:
Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
pl. help
Click to expand...
Click to collapse
TWRP termnal is just so that your phone will connect as adb to your pc.

eg0097 said:
TWRP termnal is just so that your phone will connect as adb to your pc.
Click to expand...
Click to collapse
my problem got resolved.........
actually driver was the only problem which was not allowing ADB to detect device in RECOVERY mode, though device was detected in FASTBOOT mode
So I reinstall the driver to get ADB Interface installed in system> device manager
and then followed your remaining steps i.e. 6 onwards
Thanks a lot.....

Not really sure about the following, but I hard-bricked my phone while rooting it a few days ago. Black screen, phone wasn't visible in ADB / fastboot, LED didn't change after plugging in the charger etc.
The only thing that helped: holding the power button for at least 2 minutes. The device restarted afterwards w/o any issues.
Can't find the source of it anymore ...

Very useful guide, I revived my soft - bricked Moto G

still not working
on my xt1032 moto g 16gb version I just have the warning screen that the bootloader is unlocked.
followed a lot threads but nothing helped till now.
tried your verswion and from point 1 to 7 all went well.
But I can't flash the rom. i've tried out about 6 various rom's but everything it says fail. on the screen in the twrp always stands unable to mount /data /system /storage
what can I do to fix this problem?

sascha-1102 said:
on my xt1032 moto g 16gb version I just have the warning screen that the bootloader is unlocked.
followed a lot threads but nothing helped till now.
tried your verswion and from point 1 to 7 all went well.
But I can't flash the rom. i've tried out about 6 various rom's but everything it says fail. on the screen in the twrp always stands unable to mount /data /system /storage
what can I do to fix this problem?
Click to expand...
Click to collapse
|Could someone help please? I am in the same boat and when try to run the above command, I also get this error and no file appears in the sdcard hence cant flash it.
Thanks

My Moto G is working again since one week with stock 4.4.2. I had to do it ain a bit different way...
First, I could get into bootloader and recovery. after several hours my pc recognizes my phone again, but till now I don't know why and how.
Wanted to reflash stock 4.4.2 kitkat again, but this won#t work. so I figured out that after unpacking, I had to replace the gpt.bin with the one from the 4.4.4 stock update. (see down as zip file)
Then I flashed the 4.4.2 stock again to my phone and all went well. It started again. (now I'm on stock recovery)
If you want to do the OTA 4.4.4 Update, there have to be a few things on your phone, otherwise update always fails.
1. if you have x-posed frameworks installed - uninstall it completely
2. if rooted, go into super su preferences and activate unroot all
3. do not activate developper options, or if done before, just uncheck the mark
4. you must be on stock recovery!
5. restart your phone
6. now search after update in about phone.
if bootloader is unlocked - doesn't matter - can stay unlocked
with me it first installed the 176.* OTA because my flashed stock was still 175.*
this went well, then again searched for update and 210.* (4.4.4 kitkat) could be downloaded ota. after it was done, click to install and it should work well - took a bit time.
now you are on stock 4.4.4, but without root atm.
if you want root back - now flash the newest twpr recovery 2.7.7.1 to phone, because here an OTG USB stick will be also recognized - OTG cable needed before. (don't need to push files first to phone)
copied before the su.zip to usb stick and sticked it to phone, then go into recovery. here you can install super user or better su.zip. restart phone and you got your root back on 4.4.4 stock kitkat rom

I solved this issue with twrp sideload.It worked great.

Thanks it worked for me..BUT !!!
Hi and thanks a lot.. it worked for me but you have to add some more option for who are still having troubled in unbricking. like i had..
but it can't be done without your method as on OP..
how i got bricked !!! my Moto g dual (indian)
i tried to downgrade from 4.4.4 to 4.4.2 to flash custom Rom and got system partition corrupt.
again i tried to flash stock images but no use, actual problem was System and data was not formatting.
even if you try million times and you can never successfully flash stock images without error..
however i was checking many threads in xda to resolve this problem but couldn't figured it out, as i was not new to XDA i had confidence that i can come out from this issue. until this thread gave me a hint but not a solution but still this thread is a part of the solution
let come to the unbricking method (only for those who cant flash Stock firmware from fastboot)
Reboot to fastboot..
flash Philz recovery first. get it from here.. http://forum.xda-developers.com/showthread.php?t=2639626
better to use Kernel Flasher by my old buddy Ghostfreak NB http://forum.xda-developers.com/showthread.php?t=2214724,
you just need to extract and copy the recovery to extracted kernel Kernel_Flashing_Tool_v2.0 in IMG folder and run kernel Kernel_Flashing_Tool_v2.0.bat.
press 1 and it will flash recovery, press enter it will reboot to Philz recovery,
now format System, data and whatever you can!!\
next reboot to Bootloader from Recovery,
and then follow procedure as OP
if you want to flash stock rom get from here http://forum.xda-developers.com/moto-g/development/4-4-3-moto-g-stock-rom-t2804891 and adb push as advise by OP. now you have stock rom running without any issues
Edit..
You can also flash custom ROMs with ease.
Note you better flash recovery through kernel flasher tool..

Ysharief said:
Hi and thanks a lot.. it worked for me but you have to add some more option for who are still having troubled in unbricking. like i had..
but it can't be done without your method as on OP..
how i got bricked !!! my Moto g dual (indian)
i tried to downgrade from 4.4.4 to 4.4.2 to flash custom Rom and got system partition corrupt.
again i tried to flash stock images but no use, actual problem was System and data was not formatting.
even if you try million times and you can never successfully flash stock images without error..
however i was checking many threads in xda to resolve this problem but couldn't figured it out, as i was not new to XDA i had confidence that i can come out from this issue. until this thread gave me a hint but not a solution but still this thread is a part of the solution
let come to the unbricking method (only for those who cant flash Stock firmware from fastboot)
Reboot to fastboot..
flash Philz recovery first. get it from here.. http://forum.xda-developers.com/showthread.php?t=2639626
better to use Kernel Flasher by my old buddy Ghostfreak NB http://forum.xda-developers.com/showthread.php?t=2214724,
you just need to extract and copy the recovery to extracted kernel Kernel_Flashing_Tool_v2.0 in IMG folder and run kernel Kernel_Flashing_Tool_v2.0.bat.
press 1 and it will flash recovery, press enter it will reboot to Philz recovery,
now format System, data and whatever you can!!\
next reboot to Bootloader from Recovery,
and then follow procedure as OP
if you want to flash stock rom get from here http://forum.xda-developers.com/moto-g/development/4-4-3-moto-g-stock-rom-t2804891 and adb push as advise by OP. now you have stock rom running without any issues
Edit..
You can also flash custom ROMs with ease.
Note you better flash recovery through kernel flasher tool..
Click to expand...
Click to collapse
I get this error

When im typing adb push AOSP ( i renamed to that name ) /sdcard/ attacks me this: not found. Any help?:crying: Plez :c

eg0097 said:
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder.
Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
Click to expand...
Click to collapse
I haven't actually bricked my phone but looks like my ROM.
So, I am trying to make a ROM previously in First Built the ROM didn't even wrote System [That was my fault as I wrote the the 'system' folder in Zip as 'System' and in update scripts 'system' to be extracted in '/system']
But , now the ROM has written /system but remains on Warning Boot loader Locked screen and starts to warm up I have tried Installing Kernels to fix it but no luck please help.
Device->Moto G Falcon XT1033
ROM Details->Custom ROM based on stock 5.1
Priority of problem->5 ,as I use MultiRom and have this Custom ROM as Secondary and CM 13 as primary ,but suggest a fix ASAP .

@Sid_Sun - Flash the latest factory firmware image for your model. Once that boots, proceed to custom ROMs if desired.
Factory Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
@Sid_Sun - Flash the latest factory firmware image for your model. Once that boots, proceed to custom ROMs if desired.
Factory Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
My device is booting up I am trying to make a ROM which is not booting and the booting method is by MultiRom the not booting ROM is as secondary so I can use CM 13 as primary but not boot my Custom ROM I want a fix to that issue.

Sid_Sun said:
My device is booting up I am trying to make a ROM which is not booting and the booting method is by MultiRom the not booting ROM is as secondary so I can use CM 13 as primary but not boot my Custom ROM I want a fix to that issue.
Click to expand...
Click to collapse
The MultiROM thread would be the place to ask:
http://forum.xda-developers.com/moto-g/development/modmultirom-v30wip08-01-2014-t2997071​
I have no experience with MultiROM, but I believe a Kernel with kexec-hardboot support is required.

lost101 said:
The MultiROM thread would be the place to ask:
http://forum.xda-developers.com/moto-g/development/modmultirom-v30wip08-01-2014-t2997071​
I have no experience with MultiROM, but I believe a Kernel with kexec-hardboot support is required.
Click to expand...
Click to collapse
This isn't MiltiRom's Fault probably but nvm I will flash The Custom ROM as primary and see how it goes .

Friend in step 3 you say "Run the adb setup file and press (Y) all 3 times." But what is the file?
In the list there are only 2 to download files
adb-setup-1.3.zip
twrp.zip

Where do i put the command in the 4th step?
Please help

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