I'm trying to set a up a device for a relative of mine who, whilst not the most tech savvy of people, has a habit of breaking things accidentally and likes to push buttons. I've boot unlocked their device, flashed on a custom recovery and rooted their device for them, but when trying to stick a stock recovery back on (as a .img file) I keep getting a "Preflash validation failed" error when I fire off the flash command from Moto-Fastboot.
Has anyone got a version of the KK stock recovery that works via this method or who knows of a guide to doing this (preferably via the moto-fastboot or adb tools as I'd rather not install anything else on my laptop)?
Related
I'm having trouble getting back to a regular non locked down firmware. I flashed whispercore without fully understanding that it was actually in fact changing my entire rom.
I didnt even think to try and install CWM first to create a recovery image I need help getting out of this mess. I've used the Whispercore installer to unlock fastboot because whispercore relocks your fastboot after it does its thing.
Seems as though the stock sdk tools hated me for a while there and wouldnt detect my device than I later realised it was just because the sdk downloads itself all fragmented it basically took fastboot and adb and separated the two even though fastboot requires adb to function properly. I wont even begin to speculate as to why that happened, as thats beyond the scope of my question.
I basically have gotten to the point where i have Clock work mod (CWM) installed on my droid and the fastboot oem unlocked but am currently stuck at trying to get Cyanogenmod 7 stable on here.
***UPDATE**
Ok. This situation has been resolved. If you are having trouble with leaving whisper core and you've flashed a bunch of stuff trying desperately trying to fix this issue. Recognize the nexus S is a very easy device to fix. Fastboot is your saviour and the WhisperCore installer will even be kind enough to install all the drivers required to OEM unlock fastboot and do it for you.
Anyways the solution was: Re run the whispercore installer. Let it do its automagic.
Than flash a new Clockwork Mod recovery image this thread provided some clean Clockwork Mod images for flashing with fastboot that link is also for rooting but provides a good example for how to flash a new recovery.
Than Just reboot into recovery and use it to mount your phone via the Clockwork Mod recovery console to your computer, upload your favorite flavor of rom and than unmount the device. Once unmounted go back to the main menu in Clockwork mod and "Flash zip from SD" look for your rom in my case it was update-cm-7.0.3-NS-signed.zip Latest stable at the time. let it do its job.
Basically my issue was a combination of several factors. A bad Clockwork mod and a semi corrupt installation of SDK tools and Whispercore.
Possibly a stock firmware might be required first I just know that trying to straight flash cm7 stable from cwm is not working out.
you can get adb and the 2 dll files and fastboot in the same folder and cd to that directory. fastboot oem unlock should unlock your bootloader. then you should be able to flash a recovery if you want. might also want to check out the 1 click stock thread to see if that works.
I will probably have trouble finding this thread but I will look and if i come up with anything I will certainly post my findings.
This should work. But we shall see I will update the original post if I find a full solution.
Just flash a stock full rom (for i9023 you can use the one in my signature, don't forget get to use the wipe options in cwm recovery before) and the root should be gone. Afterwards, boot into bootloader and use fastboot command "fastboot oem lock" to lock the bootloader again. Than you can do a factory reset (and delete usb storage) to fully restore stock "experience".
__________________
Nexus S running Official 2.3.4 ROM (for i9023) with XTEUV92 Trinity kernel
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1214705&highlight=one+click+stock
I'm getting an error in the zip files no matter what one I use and its "Status 7" whatever that means.
chamunks said:
***UPDATE**
Ok. This situation has been resolved. If you are having trouble with leaving whisper core and you've flashed a bunch of stuff trying desperately trying to fix this issue. Recognize the nexus S is a very easy device to fix. Fastboot is your saviour and the WhisperCore installer will even be kind enough to install all the drivers required to OEM unlock fastboot and do it for you.
Anyways the solution was: Re run the whispercore installer. Let it do its automagic.
Than flash a new Clockwork Mod recovery image this thread provided some clean Clockwork Mod images for flashing with fastboot that link is also for rooting but provides a good example for how to flash a new recovery.
Than Just reboot into recovery and use it to mount your phone via the Clockwork Mod recovery console to your computer, upload your favorite flavor of rom and than unmount the device. Once unmounted go back to the main menu in Clockwork mod and "Flash zip from SD" look for your rom in my case it was update-cm-7.0.3-NS-signed.zip Latest stable at the time. let it do its job.
Basically my issue was a combination of several factors. A bad Clockwork mod and a semi corrupt installation of SDK tools and Whispercore.
Click to expand...
Click to collapse
I am trying to follow what you did and i am completely lost... I have a nexus s g that i am trying to get whispercore off it!
The "Automagic" you talk about. Isnt that just whispercore putting it in fast boot??? If so then then how do you use the recover image?
Hi all,
I have flashed numerous roms onto my TF300 over the months, and decided to have a go at the new Jelly Bean Hydro by seanzscreams. After flashing the US 400mb standard rom from ASUS, I followed the steps and went into fastboot. From there I used Imraans method of copying my fastboot.exe and the others onto a folder called Recovery1 in my Program Files (x86). However, my device does not seem to respond to any files that I am sending through to it..as in on my cmd it is just stuck at the 'sending 'recovery' <7304KB>. After being unable to send anything to my device and it not being able to boot (btw I did not receive any sort of signature flash confirmation) I decided to wipe my data from the bootloader. I was then able to boot into the ASUS JB rom (the US version, my tf300 is WW) , which I am currently using. Now, as twrp goo imanager is not up yet the only way I can flash any recovery is via my cmd..so what can I do? My bootloader is obviously unlocked, as I tap onto the USB icon and hit volume up my computer recognizes the fastboot device..but I am unable to send anything (or flash) into the device from fastboot..(to clarify this is the "fastboot -i 0x0B05 flash recovery twrp.blob" command.) This is most likely something very simple that I have not realized but if anyone can help, please respond!
Thanks in advance.
because Idsera
Von Clausewitz said:
Hi all,
I have flashed numerous roms onto my TF300 over the months, and decided to have a go at the new Jelly Bean Hydro by seanzscreams. After flashing the US 400mb standard rom from ASUS, I followed the steps and went into fastboot. From there I used Imraans method of copying my fastboot.exe and the others onto a folder called Recovery1 in my Program Files (x86). However, my device does not seem to respond to any files that I am sending through to it..as in on my cmd it is just stuck at the 'sending 'recovery' <7304KB>. After being unable to send anything to my device and it not being able to boot (btw I did not receive any sort of signature flash confirmation) I decided to wipe my data from the bootloader. I was then able to boot into the ASUS JB rom (the US version, my tf300 is WW) , which I am currently using. Now, as twrp goo imanager is not up yet the only way I can flash any recovery is via my cmd..so what can I do? My bootloader is obviously unlocked, as I tap onto the USB icon and hit volume up my computer recognizes the fastboot device..but I am unable to send anything (or flash) into the device from fastboot..(to clarify this is the "fastboot -i 0x0B05 flash recovery twrp.blob" command.) This is most likely something very simple that I have not realized but if anyone can help, please respond!
Thanks in advance.
Click to expand...
Click to collapse
EDIT: Seemed to fix it by changing to USB 2.0 port instead of 3.0..not sure why it would do that. In case anyone else had the same issue, try switching to an USB 3.0 Port.
Hey,
I'm new to all of this so I really don't know what I'm doing wrong.
I got the normal Moto G running on 4.4.4, unlocked bootloader and rooted.
I've read that if no system files are changed I can just normally update the phone. So I flashed stock recovery (I had CWM before) using MotoTool AiO. But when I want to enter recovery it just gives me the "No Command." screen.
Only other thing I have different is, that I deleted some preinstalled Google and Motorola apps.
When I try to update the phone it just reboots after about 10 seconds telling me the update failed. (I always have to download the update again.)
I hope you guys can help me get to 5.0.2.
Thanks
You need certain Motorola Apps on your phone before the OTA update will work. Also, it's best to be unrooted.
Is there a way to restore the Motorola Apps? With the app i deleted them I can't, because I deleted them completely. (I didn't thought I would need them again.)
I'm not sure if you can find the proper APKs.
It may be easier to just flash back to stock and take the OTA update.
Okay, so I tried to get back a custom recovery so I can flash 4.4.4, but the problem is I still only get the no command screen when entering the recovery.
First I tried flashing CWM with the MotoTool AiO, but I still couldn't enter recovery, so I tried Philz Recovery, but I got the same problem there.
How the hell can I get a recovery, so I can flash 4.4.4?
You need to flash a completely stock ROM, including recovery.
You should download the stock 4.4.4 ROM for your phone and manually flash each partition using fastboot or mfasboot commands.
I tried it with help of this thread.
But it always says i can't find the command mfastboot and with the command fastboot it tells me it can't find the files and when I'm entering the folder it says it can't find the command. And even if I move the extracted files to the same folder (Where the fastboot.exe is) it tells me the files can't be found...
Like I said I'm new to all of this and little more detailed help would be appreciated
PS:
I still got the same .zip with the stock 4.4.4 I used to flash the first time (After that I deleted the system apps)
And in this .zip is an app folder with all the apks, so is there a fast way to just reinstall all of them?
Enable USB debugging and use the Moto AIO tool's Utilities tab to flash APKs to your phone.
http://forum.xda-developers.com/showthread.php?t=2635706
In MotoTool when I'm in fastboot it tells me device not found (Minimal ADB and Fastboot can find my device, and yestery MotoTool could find it, too. USB-Debugging is active.) and when the phone is normally stared in the cmd window it tells me [failed] ... (Can't read the rest, because the window closes instantly), but MotoTool says the installation worked
You need to be booted into ROM in order to use the APK installer.
When installing an APK, you may be prompted on the phone screen to allow your computer to have access to the phone.
Okay I managed to flash 4.4.4 and then I could update to 5.0.2, thanks for the help.
That's great. Glad I could be of some help.
Hello Everyone,
My moto g phone suddenly started giving errors saying "unfortunately "xxxxx" not working. xxxx is like google play and many more system services. I cannot do anything as it gives the error continuously.
I was trying to factory reset the mobile and I got the error of "boot up failed". I searched for this and found out that I need to go for custom recovery(I'm new to this) to avoid this error and get my phone back to normal.
I found that I need to unlock boot loader to for custom recovery. After trying and searching a lot I managed to do that finally with the help of a thread in this forum.
From that time I tried with many img files like TWRP, CWM and philz. But, still I could not manage to get my phone back to work.
Last 3 days I was fully in to this searching and finding solution and finally thought to write here(I'm not feeling to give up on this). I can provide you with any information needed.
I read in some guidance of CWM recovery that I need to get CWM model to process further after the below command.
Code:
fastboot flash recovery recoveryimage.img
Instead my screen stays with the below content for whatever .img file I pass for the above command
"Android system recovery <3e>
LXB22. 46-28. 1"
Appreciate any help or support on this to get my phone back to work. Thanks in advance
Nazneen said:
Hello Everyone,
My moto g phone suddenly started giving errors saying "unfortunately "xxxxx" not working. xxxx is like google play and many more system services. I cannot do anything as it gives the error continuously.
I was trying to factory reset the mobile and I got the error of "boot up failed". I searched for this and found out that I need to go for custom recovery(I'm new to this) to avoid this error and get my phone back to normal.
I found that I need to unlock boot loader to for custom recovery. After trying and searching a lot I managed to do that finally with the help of a thread in this forum.
From that time I tried with many img files like TWRP, CWM and philz. But, still I could not manage to get my phone back to work.
Last 3 days I was fully in to this searching and finding solution and finally thought to write here(I'm not feeling to give up on this). I can provide you with any information needed.
I read in some guidance of CWM recovery that I need to get CWM model to process further after the below command.
Code:
fastboot flash recovery recoveryimage.img
Instead my screen stays with the below content for whatever .img file I pass for the above command
"Android system recovery
LXB22. 46-28. 1"
Appreciate any help or support on this to get my phone back to work. Thanks in advance
Click to expand...
Click to collapse
Rename the twrp or cwrecovery as recovery and copy to adb folder. Fastboot command is
fastboot flash recovery recovery.img, (not fastboot flash recovery recovery image .img)
pradeeppk said:
Rename the twrp or cwrecovery as recovery and copy to adb folder. Fastboot command is
fastboot flash recovery recovery.img, (not fastboot flash recovery recovery image .img)
Click to expand...
Click to collapse
it is not "recoveryimage". I just used it for this question. I tried with many files. So, I gave the name of the file and used the command and I got the success message also in CLI saying "Okay" and finished. But no file made any difference to device.
I had a pass code to unlock my screen. Two times I was able to get the screen (Other times it become dark after loading M) and it required the authentication code I gave to enter unlock screen. and I was filled with errors showing continuously "unfortunately not loaded 'system files' ". I suspect that whether the flash worked properly because it was asking for the screen unlock code.
After Lollipop Update of my phone (Lava iris icon), I had to root in again and while trying to root it from custom recovery, I bricked it ( may be the recovery is not compatible). So,it stuck in the bootloop and by pressing Power and volume buttons, I am only able to access Fastboot mode. I downloaded the stock rom of device and tried to flash recovery , boot etc. with fastboot commands, but it is still in bootloop. I also tried to flash cwm recovery (though it is not available for device, I chose the nearest one), but in vain.
When I try to flash system partition, it gives error while erasing system <unknown command> (may be due to fact that phone is not rooted as of now). Also, SP flash tools are not recognizing the device and I cant use adb commands also. So, I am stuck with only fastboot in hand and I have stock rom as well as lollipop update, but i am unable to use these due to errors. Can anyone help? I will be very thankful for an advice. Thanks in advance.
rishab951 said:
After Lollipop Update of my phone (Lava iris icon), I had to root in again and while trying to root it from custom recovery, I bricked it ( may be the recovery is not compatible). So,it stuck in the bootloop and by pressing Power and volume buttons, I am only able to access Fastboot mode. I downloaded the stock rom of device and tried to flash recovery , boot etc. with fastboot commands, but it is still in bootloop. I also tried to flash cwm recovery (though it is not available for device, I chose the nearest one), but in vain.
When I try to flash system partition, it gives error while erasing system <unknown command> (may be due to fact that phone is not rooted as of now). Also, SP flash tools are not recognizing the device and I cant use adb commands also. So, I am stuck with only fastboot in hand and I have stock rom as well as lollipop update, but i am unable to use these due to errors. Can anyone help? I will be very thankful for an advice. Thanks in advance.
Click to expand...
Click to collapse
is there a partition file with the stock rom you downloaded?
if so, try to flash that first with fastboot.