Database Users

For Clarification Purposes Only-NaNdRoId

-------due to the brick phones-------(and im not talking nokia)
I have started this thread to get some clarification on Nandroid back ups. Now i know there is already a thread with step by step instructions in the sticky's. But with all these G1 ones getting bricked due to the new spl incompatibility with the old radio is it safe to use. I ask this only because one of the steps is to have a recovery.img and the only recovery image i can find is for jf1.43 and one other. But none for the adp 1.5 builds. I am worried that if i were to flash a old recovery image, and it down grades my radio i may get bricked. I'm not really sure if that's how it works (if not please correct) and thats why i want to recovery image from the new builds ( i am using Dudes Cupcake 1.1)
Do they exist and if they do and i just haven't search hard enough please tell me. Or is the recovery image what i create when i do the back up. I ask all these perceivable noob questions because i really like my G1 and would hate to brick it.....
Please post some useful Replies... I think this thread could be potentially useful

Doing a nandroid backup creates a boot.img, data.img, and system.img of your phone. Flashing those three, restores your phone exactly as it was when you created the backup. As long as you do a backup of your system when it's stable, then it doesn't matter what you do to your phone. As long as you can get into fastboot, then it can be fixed in less than 5 minutes.
Dunno if that was the answer you were lookin for, but that's how I understand it. And it works....I did a nand backup of my Dude build just yesterday, and flashed over to haykuro's 6.0 to check it out...test drive it. I didn't like it, so I flashed the nandroid backup, and was back up and running in minutes.
You mentioned recovery.img....I don't know what that is or what you do with it.
Assuming you have fastboot setup, just do the steps in this post and you're golden-
http://forum.xda-developers.com/showpost.php?p=3311708&postcount=2

the recovery.img is what the phone boots in recovery mode... the recovery.img that your referring to allows you to create NAnd backups easily with NANDroid... the recovery img is totally independent from your SPL (bootloader), Radio, and Firmware

ESKIMOn00b said:
the recovery.img is what the phone boots in recovery mode... the recovery.img that your referring to allows you to create NAnd backups easily with NANDroid... the recovery img is totally independent from your SPL (bootloader), Radio, and Firmware
Click to expand...
Click to collapse
Right on, thanks for that. Knowledge is power.
So the op says that he found the JF1.43 recover.img....That's the one we all have and the one he needs, right?

yep, they're all the same
All the recent ROMs EXCEPT for the official HTC ADP use the same recovery.img found in the previous JF ROMs (1.42, etc.). You can safely reflash the recovery image from fastboot without touching the radio, the SPL or even data, boot or system if you want and it won't hurt anything.

remember when you orig rooted your phone and the recovery mode didnt have the fractal background and you had to press alt+l to show the text? thats the OLD recovery img, the fractal bkgrnd (v1.43) one is the new one, and so far the latest "cooked" recovery.img

Like i said im kinda noobish. So after i downloaded the drivers, and the sdk for 1.5 i still need to download fastboot (to my pc) as well.

Great post. +1

pshadey said:
Like i said im kinda noobish. So after i downloaded the drivers, and the sdk for 1.5 i still need to download fastboot (to my pc) as well.
Click to expand...
Click to collapse
correct...
the fastboot.exe is how your PC will interface with the FASTBOOT mode in the SPL
if you didnt have it DL'ed when you tried to fastboot, your computer would kickback that fastboot isnt a valid command or the like (depending on os)

so im reading all these tutorials, and im getting confused a little... to use fast boot through adb does my phone need to be at the boot loader (skateDroids) or are there commands that i would need to enter in order to get there....
I appriciate every answer i am trying to learn as much as i can. This has really spark a interest in my life and i really enjoy it.

fastboot is not part of adb, and yes your phone needs to be in bootloader to FASTBOOT, after entering bootloader plug in the usb cable and press the back button, your phone should read FASTBOOT rather than serial0
adb works almost anywhere (after splash1/g1 logo) except bootloader...
for reference ADB stands for Android Debug Bridge

I am still slightly confused how do i create a nandroid back up, i am using dudes cupcake 1.1. Is it the same as JF's alt-b

pshadey said:
I am still slightly confused how do i create a nandroid back up, i am using dudes cupcake 1.1. Is it the same as JF's alt-b
Click to expand...
Click to collapse
Yep. Boot your phone with home+power, then Alt+B. It'll create a folder on your sdcard called nandroid. All the .img files will be in there.

i dont think i have the right recovery image though do i just download the zip file. and do the whole rename to update.zip and install alt-s.
I only ask because i opened the file and found a recovery.img which made me ponder.

thats the Nand dump of your recovery partition... you figured it out...
if you made the backup you have the right recovery img.... the old one doesnt have it...

~edit~
I see I misunderstood the question. Duh

ESKIMOn00b said:
thats the Nand dump of your recovery partition... you figured it out...
if you made the backup you have the right recovery img.... the old one doesnt have it...
Click to expand...
Click to collapse
and when i booted in recovery mode i dont have the option alt-b. so i must have the old recovery image.
so now i need to (already have) download the recovery image zip file from jfs blog, rename it update.zip and flash it....right????

This is what your recovery mode will look like after you update 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"
}
I can't answer your question about how to update to it though. Mine's been this way since waaay back when I flashed JF's RC33.

yea, thanks bro. mine definitely does not look like that. but now i need to know for sure how to update it.

pshadey said:
and when i booted in recovery mode i dont have the option alt-b. so i must have the old recovery image.
so now i need to (already have) download the recovery image zip file from jfs blog, rename it update.zip and flash it....right????
Click to expand...
Click to collapse
I am having the same problem... I am on the Dude's Cupcake 1.1a but I dont see ant Alt-B option...
Android system recovery utility
E:Can't open /cache/recovery/command
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset
Click to expand...
Click to collapse
Thats all i have on my screen.

booting failed

Help.
Booting failed. After downloading "[LINUX] Universal Nexus Linux Toolkit v1.0 (Unlock, Lock, Root, CWM, Factory Reset)" and ran Unlock the bootloader, Flash CWM recovery (Standard or Touch), Root the phone, I didn't foud anything change (not like my cellphone, I can select recovery mode when long push the powerbutton off button), so I made a decision (I beleve that's a huge mistake), I did lock the bootloader and flash Google Factory Image. Finally I realised I couldn't boot OS, but I found at the begining of power on, I could choose "start" "restart bootloader" "recovery mode" "power off" , It said booting faild if I select start or recovery mode.
Is there any way to rescue my tablet?

I have not used that tool.. But i believe you were to have a rom on your data/ media partition on your tablet then boot into recovery and flash the rom.. Sounds like your tablet just has no rom on it.. Try to adb push a rom to data /media then go into cwm and flash it .. you can use the nexus tool kit to do this if you do not know how..
Good Luck...
---------- Post added at 06:48 PM ---------- Previous post was at 06:43 PM ----------
oops misread . your saying you can not get to recovery.. Try holding both vol up and down together and then power button from a off state . Before i would say 20 seconds you should get a hard reset.. if not the recovery/ rom flash failed.. You will need to use a Nexus tool kit to put the recovery and rom back.. or use fastboot to push recovery.. boot into recovery and install flash rom....
Sorry

can't see device with usb or adb
I have the same problem. Unforunately, I can't see my device with adb or in windows via the usb port. Without these I can't use the Nexus 7 toolkit. Any idea what I should try next?

jackjsa said:
How Unbrick nexus 7!!
1) Download the factory. image of nexus 7 before by this https://developers.google.com/android/nexus/images.
2) nexus 7 root toolkit for the advanced. utilities it. (Lower left corner of the application), then click Launch.
3) mode is advanced tool you see Quick tools (on the left), select Fastboot-Bootloader me. The middle section (Boot / Flash image) to Flash (Permanent).
4) the file you downloaded from the first) is to run it using 7zip. Do not have a zip file. Recommend that if you are exhausted. The file extension. . Img me into the same folder (for ease of flash. And protection against flash files!) 7zip app and all programs in the community. Reload this App Play Store: https://play.google.com/store/apps/details?id=org.joa.zipperplus7.
Computer loaded from this link. http://www.7-zip.org/download.html.
5) flash file system before the first Boot Click Boot and select the file from 4) the file named boot.img it.
6) flash the Bootloader on file bootloader-tilapia-4.18.img. (The grouper tilapia could be it. If you use the nexus 7 Wifi only).
7) flash the Radio / Baseband file name. radio-tilapia-1231_0.17.0_1205.img it.
8) flash File Recovery file name. recovery.img it.
9) flash file system on the order Userdata System and select the file system.img userdata select userdata.img.
10) completed it. Your machine will reboot. I do not drink coffee.
11) Enjoy! ^ _ ^.
You. Ban flash the wrong files here. I need the name of the file. The only way to tell!
I flash rom 0.2 the risk. I should be very careful.
0.3 If this is the case, you Softbrick it. (Hardbrick may not), then I try this method worked 100%.
There is a 0.4 credit, I thought I was the way I make them up. I want to share with. Please add credit to it. If one on me. Help bring this up with the group, thank you.
0.5 If there is another one your way. The mind of the South. (I have yet to try it as I work) and I like that we do not have information on the nexus (the brick that we do not backup data).
Ways.
First. Downloaded SDK from this link.
http://developer.android.com/sdk/index.html.
Two. Then double-click. Extract the files placed on the desktop.
Three. Downloaded Factory Image (create a new folder and then extract the files to put in it).
. 4 Factory Image extracted successfully, look for a file named flash-all, right-click the file and select edit, then go to delete off-w, then Save and come out.
5. Adt-bundle up to see two folders. Click to select the sdk folder and then uncompress the Factory Image files Copy all (6 files) and put it in a folder. platform-tools.
6th. Then double click the flash-all then lay in wait for a while to update it back to Factory Image kosher by the data is lost. Mod it to disappear, they are only dancing, etc. (it's new to flash).
Note: Do not forget to delete off-w, otherwise everything totally disappeared.
Suggested: do not open a cmd without the headache type. Not faced with the annoying Waiting for device.
0.6 Read carefully and understand it before doing it. Because many steps too. And all the way I say. In the computer, you must install the drivers and I!
It's .7 stock rom nexus 7 Wifi version, select nakasi (grouper) it. The Model 3G or 3G + Wifi. Select nakasig (tilapia).
0.8 I thank everyone. And all the comments too. I suggest that the nexus 7 brick.
0.9 If a brick at me because I was pushed to the nexus 7 root tool v 5.0 to flash stock rom just to watch a lot of this toolkit. + audio bug bit orchestrated. I recommend the use of or nexus root toolkit v1.6.3 wugfresh it.
Click to expand...
Click to collapse
Please stop posting the same thing in every thread; it's not helpful.
{
"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"
}
Sent from my Nexus 7 using Tapatalk HD

korockinout13 said:
Please stop posting the same thing in every thread; it's not helpful.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Sorry, I just want to help!

boot failed
tuuss said:
Help.
Booting failed. After downloading "[LINUX] Universal Nexus Linux Toolkit v1.0 (Unlock, Lock, Root, CWM, Factory Reset)" and ran Unlock the bootloader, Flash CWM recovery (Standard or Touch), Root the phone, I didn't foud anything change (not like my cellphone, I can select recovery mode when long push the powerbutton off button), so I made a decision (I beleve that's a huge mistake), I did lock the bootloader and flash Google Factory Image. Finally I realised I couldn't boot OS, but I found at the begining of power on, I could choose "start" "restart bootloader" "recovery mode" "power off" , It said booting faild if I select start or recovery mode.
Is there any way to rescue my tablet?
Click to expand...
Click to collapse
I got error while flashing and then after power up git little note "boot failed"
I tried to get into fastboot mode, few times i got fastboot but it was not responding and adb saw no devices. after few attemps i got working fastboot mode and then flashed it as normal.

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.

GUIDE - Install TWRP Recovery and Root MOTO E Phone

WARNING!
Your warranty is void if you follow the given instruction in this guide. Read all the instruction very carefully and Perform everything at your own risk.
This guide is only for the MOTO E android smartphone. Don’t try this method on any of other Android devices, It may hard brick your device. So, first confirm your phone model number in your android phone settings. To do this Go the Settings page of your device and check out the “About Device” option.
PRE-REQUISITES AND REQUIREMENTS
1. BACKUP YOUR ANDROID DATA
2. INSTALL MOTO E DRIVERS
3. ENABLE USB DEBUGGING MODE
4. CHARGE YOU ANDROID
If your device switched off during this process, it could damage or brick the device. Make sure that your Android battery is full charge or near about 50-70% battery level.
HOW TO INSTALL TWRP & ROOT MOTO E
Step 1. Download the Fastboot files for MOTE E and extract the folder on your desktop.
Step 2. Download The TWRP recovery from here (Rename the file to recovery.img) and extract in the same folder as of step 1.
Step 3. Download The SuperSU from here and copy it into the root of your internal memory,
Step 4. Now all the important files are with your. First you have to unlock the bootloader of your device. Read here.
Step 5. Connect your phone to PC and Reboot to bootloader by pressing VolumeDown + Power button for about 6-7 seconds.
{
"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"
}
Step 6. Go to the Fastboot folder in step 1, Do Shift + RightClick in empty space in the folder without selecting anything, Select Open a command window here.
Step 7. Now you will see the command prompt window on your screen. In the command prompt window, you need to enter the below mentioned command;
fastboot flash recovery recovery.img
Step 8. Press Volume Down to select recovery on fastboot menu, then press Volume Up to confirm your choice to boot into recovery
Step 9. Now touch doesn’t work in recovery straight away, so wait 60 seconds without touching the phone, The phone screen will go blank.
Step 10. Press power button and do swipe to unlock to get your touch working again! Select Install, scroll down and find the SuperSU Zip downloaded in step 3.
Step 11. Swipe to confirm, wait untill the flash is complete and then select reboot. First reboot will take some time, so no need to worry.
Now check your MOTO E app drawer, There should be SuperSU installed. Congratulations you are rooted!
via @howtorootmobile

I think so this guide is already available!!

TheStrix said:
I think so this guide is already available!!
Click to expand...
Click to collapse
Yeah I did that guide earlier!

recovery flash error
hey dude, i was trying to flash twrp n root but i have got an error. i have posted a ss, pls do help. thanks

5644red said:
hey dude, i was trying to flash twrp n root but i have got an error. i have posted a ss, pls do help. thanks
Click to expand...
Click to collapse
Write
Code:
mfastboot flash recovery recovery.img
it will work!

deej_roamer said:
Write
Code:
mfastboot flash recovery recovery.img
it will work!
Click to expand...
Click to collapse
Thanks for the help buddy but still it isnt working.

5644red said:
Thanks for the help buddy but still it isnt working.
Click to expand...
Click to collapse
Download another version of mfastboot, or simply just fastboot, or try from scratch again!
I saw earlier your mfastboot folder has recovery.img, so cannot be a misplace error!
Still check again it is there! Otherwise, do what i wrote in first line!

deej_roamer said:
Download another version of mfastboot, or simply just fastboot, or try from scratch again!
I saw earlier your mfastboot folder has recovery.img, so cannot be a misplace error!
Still check again it is there! Otherwise, do what i wrote in first line!
Click to expand...
Click to collapse
tried like 5 or 6 times buddy.. still no use.. i was able to unlock bootlocker without any trouble so i hope there is no trouble with moto drivers, i feel it might be due to fastboot file.. ill try again soon.. thanks

Can you please tell me if i will be able to install the 4.4.3 update after flashing custom recovery. Thanks in advance

Ccceenu said:
Can you please tell me if i will be able to install the 4.4.3 update after flashing custom recovery. Thanks in advance
Click to expand...
Click to collapse
No you need stock recovery!
But its alright you can revert back to custom recovery from here
So go back and enjoy custom recovery,
And if you still prefer not to change your recovery, you can try this guide!

deej_roamer said:
No you need stock recovery!
But its alright you can revert back to custom recovery from here
So go back and enjoy custom recovery,
And if you still prefer not to change your recovery, you can try this guide!
Click to expand...
Click to collapse
Thanks for your reply..I read that somewhere that during updates it checks for stock recovery..so i refrained from flashing custom recovery ... there is another question if you can answer...will the procedure of rooting will change in the 4.4.3 version. Thanks in advance

Ccceenu said:
Thanks for your reply..I read that somewhere that during updates it checks for stock recovery..so i refrained from flashing custom recovery ... there is another question if you can answer...will the procedure of rooting will change in the 4.4.3 version. Thanks in advance
Click to expand...
Click to collapse
No it wouldn't

moto e
i unlocked my bootloader can i directly install supersu from recovery without flashing custom recovery?

I guess....
5644red said:
hey dude, i was trying to flash twrp n root but i have got an error. i have posted a ss, pls do help. thanks
Click to expand...
Click to collapse
Did you make sure that you actually 'Opened' the 'fastboot' folder and then press shift and right click....?

having same problem
5644red said:
Thanks for the help buddy but still it isnt working.
Click to expand...
Click to collapse
Hey did u problem got sorted as I am having the same problem as u, kindly help me if anyone can

I tried to install twrp recovery but in cmd its shows an error
Error while loading recovery.img

Can I change my recovery from cwm to twrp
Sent from my Moto E using XDA Free mobile app

I am getting "partition size mismatch" error when i try to flash the TWRP recovery.

Magisk for Android 12/OOS12 global ( magisk_patched)

Magisk for Android 12/OOS12 global ( magisk_patched)
IN2015_11.C.11 (Global)
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

suhuf said:
Magisk for Android 12/OOS12 global ( magisk_patched)
IN2015_11.C.11 (Global)
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
How exactly do we
suhuf said:
Magisk for Android 12/OOS12 global ( magisk_patched)
IN2015_11.C.11 (Global)
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Just flash this via fastboot?

scorpio76r said:
How exactly do we
Just flash this via fastboot?
Click to expand...
Click to collapse
fastboot flash boot boot.img

suhuf said:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw

scorpio76r said:
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw
Click to expand...
Click to collapse
If you're sure the version is global, it should work.

{
"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"
}

scorpio76r said:
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw
Click to expand...
Click to collapse
Read the explanation and remove the original boot file and fastboot, the phone will boot.
Put the same boot file in the download section of the phone and patch it with magisk, then upload the patched file to the phone with fastboot process.
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com

Apologies but I'm confused by the steps in the posts above... Can someone post a brief step-by-step guide for this? Thanks!
[EDIT] nevermind, extracted and patched on my own, thanks!

scorpio76r said:
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw
Click to expand...
Click to collapse
I also got stuck on fastboot. Any solution will be appreciated.
Edit: Had to restore device with MSM Download Tool.

Hi, just updated to official OOS12 and hate it, it appears it also re locked my bootloader which was unlocked, how do I unlock it again? do I follow the same steps? I want to go back to OOS11 and start flashing custom roms
edit: just checked on fastboot mode. it says unlocked in red letters. would still like to flash magisk!

cjvzla said:
Hi, just updated to official OOS12 and hate it, it appears it also re locked my bootloader which was unlocked, how do I unlock it again? do I follow the same steps? I want to go back to OOS11 and start flashing custom roms
Click to expand...
Click to collapse
You sound like me a week ago. Best bet is to msm your phone and start from scratch. Bring your phone up to 11.10.10 then go with the Jaguar rom. It has March security patch, call record and developers literally responds within a few minutes of a post or question.

scorpio76r said:
You sound like me a week ago. Best bet is to msm your phone and start from scratch. Bring your phone up to 11.10.10 then go with the Jaguar rom. It has March security patch, call record and developers literally responds within a few minutes of a post or question.
Click to expand...
Click to collapse
hi, just checked and I still have the bootloader unlocked, which means I could flash a recovery right? I haven't flashed stuff in android phones in a while and I'm a bit rusty, where should I go first?

cjvzla said:
hi, just checked and I still have the bootloader unlocked, which means I could flash a recovery right? I haven't flashed stuff in android phones in a while and I'm a bit rusty, where should I go first?
Click to expand...
Click to collapse
Yes use fastboot twrp image from the official twrp thread. Then install twrp installer.

krakout said:
Apologies but I'm confused by the steps in the posts above... Can someone post a brief step-by-step guide for this? Thanks!
[EDIT] nevermind, extracted and patched on my own, thanks!
Click to expand...
Click to collapse
hi! how did you extracted and patched? did you follow the video? cause I can't understand what hes saying. can you leave me a step-by-step? thanks. I'm on OOS12, bootloader unlocked

cjvzla said:
hi! how did you extracted and patched? did you follow the video? cause I can't understand what hes saying. can you leave me a step-by-step? thanks. I'm on OOS12, bootloader unlocked
Click to expand...
Click to collapse
I just sent you a personal message with a link that will help you out.

Sorry, couldn't reply earlier.
Higher in this thread there's a link for a very useful program. Use that program to rip everything from the official download update package (have you downloaded that?). Then move boot.img to your phone, and let Magisk Manager patch it. Then copy the patched file over to your PC and use adb to flash it.

krakout said:
Sorry, couldn't reply earlier.
Higher in this thread there's a link for a very useful program. Use that program to rip everything from the official download update package (have you downloaded that?). Then move boot.img to your phone, and let Magisk Manager patch it. Then copy the patched file over to your PC and use adb to flash it.
Click to expand...
Click to collapse
Yes, using windows 10 pc.

krakout said:
Sorry, couldn't reply earlier.
Higher in this thread there's a link for a very useful program. Use that program to rip everything from the official download update package (have you downloaded that?). Then move boot.img to your phone, and let Magisk Manager patch it. Then copy the patched file over to your PC and use adb to flash it.
Click to expand...
Click to collapse
hi thanks for the tutorial, managed to extract the OOS12 stock boot img and patched it with magisk 24, but when I connect in fastboot mode and check with the fastboot devices command I get nothing, and nothing on device manager either. even tho my bootloader is unlocked and fastboot drivers are installed, the pc doesnt seem to "see" my phone?
the adb devices command does show my phone when connected and turned on.

That's a bit tricky and I'm not sure why it would do that, never encountered it... Tried restarting adb?

krakout said:
That's a bit tricky and I'm not sure why it would do that, never encountered it... Tried restarting adb?
Click to expand...
Click to collapse
looked for the latest drivers and installed those, now my devices does show up with the fastboot devices command! do I test the patched boot img first? and did you flash it normally or did you use fastboot flash boot_a and fastboot flash boot_b for the a/b partitions?