Related
Hi all, :
Ive owned a defy since january, and after a lot of lurking here decided to take the plunge and have a play with it.
It was a stock unbranded uk defy with 2.51 blur rom, it rooted no problem with super one click, i then installed thi version of recovery : http://forum.xda-developers.com/showthread.php?t=875233
I then botted it into recovey and am now stuck in a bootloop.
I can access stock recovery (vol down and power) then touch bottom right of screen. I wiped cache and user data from here.
I can enter bootloader (vol up and power) and rsd lite can detect the phone.
My question is what is the easiest way to bring my phone back to life ? Im not sure if i need to flash sbf or rom.
Not to fussed about having the latest roms or mods, just a working phone before the battery gives out.
Thanks in advance, Sam
This happened to me a few days ago the way you should do it is download the 2.51 uk sbf file and flash it over using rsd lite and it should boot straight back Into the operating system and by the way how come that version did that to your phone I've installed recovery on 2 defys and they both worked
One more question did it boot up into recovery or not ?
No it didnt boot into recovery, just the boot loop. Any idea where i can get the uk sbf ? the link here seems to be dead
So you installed system recovery and then once again in the program installed it and then you clicked boot into recovery right ?
http://and-developers.com/sbf:defy
This website has all the sbfs your one should be the second on the list
RSD lite that one into your phone and it should be good to go
so.. is the usb debugging on?
when tap install recovery button, you should turn off usb debugging.
memz180 said:
So you installed system recovery and then once again in the program installed it and then you clicked boot into recovery right ?
http://and-developers.com/sbf:defy
This website has all the sbfs your one should be the second on the list
RSD lite that one into your phone and it should be good to go
Click to expand...
Click to collapse
mannn you save my life, i was looking for a stock rom from Latin America, and i got it from that link.
Thanks for the link memz180. Downloaded sbf and flashed sbf and phone is now working. Next question is what is the idiot proof way to install recovery ?
You installed the correct recovery just make sure you click into the program and install the system recovery within the program and then click on boot to recovery make sure i would make sure superuser is allowing it so check that out to and also as stated above turn off your debugging in development and then click on recovery see if it works.
Goodluck
Rerooted phone and reinstalled recovery, no problems this time. Thanks all for your help.
Sam
No problem here at xda we do our best to help our fellow android mates lol
Another Noob with an almost bricked Defy!
sammitch said:
Hi all, :
Ive owned a defy since january, and after a lot of lurking here decided to take the plunge and have a play with it.
It was a stock unbranded uk defy with 2.51 blur rom, it rooted no problem with super one click, i then installed thi version of recovery : http://forum.xda-developers.com/showthread.php?t=875233
I then botted it into recovey and am now stuck in a bootloop.
I can access stock recovery (vol down and power) then touch bottom right of screen. I wiped cache and user data from here.
I can enter bootloader (vol up and power) and rsd lite can detect the phone.
My question is what is the easiest way to bring my phone back to life ? Im not sure if i need to flash sbf or rom.
Not to fussed about having the latest roms or mods, just a working phone before the battery gives out.
Thanks in advance, Sam
Click to expand...
Click to collapse
I have the same problem on my T-mobile US branded Defy + when I try to flash the sbf file, on RSDlite It gives me this error
"Failed flashing process. Failed flashing process. Error processing flash file. (0x700F); phone conected"
What am I doing wrong? I tried RSDlite ver 4.9 and 5.0 to no avail! Please help! Thank you!
SOLVED!
NrikeCalderon said:
I have the same problem on my T-mobile US branded Defy + when I try to flash the sbf file, on RSDlite It gives me this error
"Failed flashing process. Failed flashing process. Error processing flash file. (0x700F); phone conected"
What am I doing wrong? I tried RSDlite ver 4.9 and 5.0 to no avail! Please help! Thank you!
Click to expand...
Click to collapse
So, I was using my laptop with W7 to flash my Defy, I tried RSD lite 4.9 and 5.0 and kept getting the error message. I decided to give my desktop with Vista a shot and installed RSD lite 4.9 and the motorola drivers; i don't know why but immediately after plugging the phone in it started flashing! Awesome! After that I rooted again and installed 2ndInit (Wich is awesome!).
I backed up and flashed CM7 from the custom recovery mode. Everything started working excellent until I decided to re install 2ndInit!!! BIG MISTAKE! Never do that! I nearly bricked my phone again and couldn't load into recovery mode anymore! I had to re flash JRDNEM_U3_2.51.1. After that I had to repeat the whole process with the exemption of reinstalling 2ndInit after CM7.
Since 2ndinit is already installed you don't need to re install even if you don't have the app in your tray.
I'm in the same boat, my phone is in a reboot loop, and I can't seem to flash it...
RSD Lite 4.9 on win7
Error:
Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected
/me bangs head against the wall...
read somewhere else it has to do with where RSD Lite is installed, on my win 7 32bit that was c:\Program Files\Motorola\RSD Lite...
uninstalled, reinstalled in c:\Motorola\RSD Lite and copied the sbf to that dir too... seems to be working... hope this helps someone else!
NrikeCalderon said:
So, I was using my laptop with W7 to flash my Defy, I tried RSD lite 4.9 and 5.0 and kept getting the error message. I decided to give my desktop with Vista a shot and installed RSD lite 4.9 and the motorola drivers; i don't know why but immediately after plugging the phone in it started flashing! Awesome! After that I rooted again and installed 2ndInit (Wich is awesome!).
I backed up and flashed CM7 from the custom recovery mode. Everything started working excellent until I decided to re install 2ndInit!!! BIG MISTAKE! Never do that! I nearly bricked my phone again and couldn't load into recovery mode anymore! I had to re flash JRDNEM_U3_2.51.1. After that I had to repeat the whole process with the exemption of reinstalling 2ndInit after CM7.
Since 2ndinit is already installed you don't need to re install even if you don't have the app in your tray.
Click to expand...
Click to collapse
Yer cm7 comes with it pre installed it would flash blue at bootup you should of seen it I think on the installation instruction it's written dont install 2ndinit
just rename the .sbf file to smaller name and try again
Rooting and updating your MotoActv is about to get significantly easier! No more waiting games for developers to update their ROMs or tools when Motorola pushes a new OTA; now you can do it yourself! I honestly have not seen these types of files ANYWHERE else, so I had to create these myself (with quite a bit of help from [mbm]). But enough blabbing, here are the files and how to use them:
(Note: all these methods assume we have full fastboot access! -- Which we still have at this point)
- Stock Images:
These are not just mere update.zips that you might be accustomed to elsewhere in Android. Nor are these mere fxzs that you might be accustomed to elsewhere with newer Motorola devices. They are in fact both and more. There are 3 main ways to flash these files onto your device, giving you options based on what OS you run and how comfortable you are flashing files to your device.
1) FXZ:
- Operating System: Windows
- Requires: RSD Lite with FXZ Support
- Instructions: Simply load up the file as any standard fxz (it is very straight-forward)
2) Recovery:
- Operating System: Anything that can mount your device
- Requires: The ability to get into recovery
- Instructions: Place the file on the sdcard, boot into recovery, flash as normal
- Note: Recovery does not wipe your device, it is suggested that you do so before flashing stock images
3) Fastboot:
- Operating System: Windows/Linux/Mac
- Instructions (Windows): Unpack the zip, run flash-all.bat (if it fails, run as administrator)
- Instructions (Linux/Mac): Unpack the zip, run flash-all.sh (it should already have proper permissions)
Miscellaneous Images:
These miscellaneous images are nothing you haven't seen before at this point, but their purposes are new, so they too require explanation.
1) AnyRoot:
AnyRoot is based on koush's AnyKernel in the sense that it unpacks and repacks the boot.img on the fly. However, as the name suggests, AnyKernel is meant for kernels, while AnyRoot, actually roots the device on the fly. This will work on any MotoActv device. It is flashed as a normal update.zip and everything is done in the background so you won't noticed much. However, for ease of access, the stock and rooted boot.img is exported to your sdcard in /sdcard/recovery/. Also note, that if you happen to flash AnyRoot over an already rooted device, nothing will happen as it has built-in error checking.
2) rebootRecovery:
rebootRecovery is another fxz type zip, the same as the stock and rooted images, except it can't be flashed in recovery (would be a little redundant don't you think?). This flashes a specially made misc.img by [mbm] that tells the device to reboot into recovery from boot. This means you can flash AnyRoot on any stock device.
How Tos / FAQs:
Now that you know what the files do, I can explain in short steps how to use these files to get what you want:
1) How to Return the Device to Stock?
- flash a stock image using any of the 3 methods
- you can now update via Motocast if you so wish
2) How to Root a Stock Device?
- update your device via Motocast to the latest version (suggested)
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
3) How do I update my Rooted Device?
- flash a stock image using any of the 3 methods
- update your device via Motocast to the latest version
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
Q: After using rebootRecovery I can't get out of recovery!?
A: You are using an old recovery that doesn't clear the 'reboot-recovery' command; use the newer recovery: https://dl.dropbox.com/u/5849675/android/f100/CWMR5x_F100_recoveryB2.img
Q: What do these ROM offer over other custom ROMs?
A: Nothing, they are simply stock images, but you can upgrade with them.
Q: How much battery should I have when I flash?
A: Performing any kind of these flashes will drain at least 10% of your battery, I wouldn't suggest you flash below 60% ESPECIALLY IF YOU FLASH rebootRecovery!
Q: What happens if I flash a 16gb zip on my 8gb or visa-versa?
A: Don't freak, it will still boot, but it's not the best thing in the world to do, just go back and flash the correct model zip.
Q: Can I extract the images from your zips and flash them my own way?
A: yep (couldn't really think of anything else to say)
Q: I manually flashed the stock-boot.img from AnyRoot, and now I can't update. Why?!
A: The boot.imgs need to be truncated before they can be flashed to correctly work with Motorola's updates, just use the stock images.
Q: What's next?
A: HyprActv -- What's this?
Stock Images (w/ md5sums):
8gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_NA.zip (5e228bf56a67aced012c8cbb2d7f7c76)
16gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_16GB_NA.zip (21b067dc629f7ccd18b43799d8d5fb17)
8gb-EU: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_EU.zip (5b79a46d87728303fc2c920eec71c2e8)
Miscellaneous Images (w/ md5sums:
AnyRoot: https://dl.dropbox.com/u/5849675/android/f100/MA_AnyRoot.zip (2f867b006da42865ef861094db0eb6e6)
Reboot Recovery: https://dl.dropbox.com/u/5849675/android/f100/MA_RebootRecovery.zip (1623c9c61462db9bb20b55bc8f1144aa)
Mirror (thanks Iownox!): http://www.androtransfer.com/?developer=lownox&folder=MotoACTV
This is Reserved.
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Moose8106 said:
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Click to expand...
Click to collapse
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
CEnnis91 said:
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
Click to expand...
Click to collapse
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Moose8106 said:
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Click to expand...
Click to collapse
Yes, any and all tools that exist so far will need to be updated.
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
innovatelife said:
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
Click to expand...
Click to collapse
Did you end up doing any restore of some kind after you flashed?
Update
There are "new" instructions that might fix the issue where the rooted 4.55.97 appears to not flash. Simply wipe the boot.img image before you flash. And don't use the root tools until they are updated.
Also, if you have success, please post it. Usually "Thanks, it works" is annoying, but in this case where I don't have the device, I need to make sure this is working on some level.
I formated everything from recovery, now I got stuck with Moto logo with no animation when it starts, how to get out of this?
NA
Is there any mirrors for the download of these roms? the dropbox links are down
NORCALkID said:
Is there any mirrors for the download of these roms? the dropbox links are down
Click to expand...
Click to collapse
They were pulled, they're not working. There has been some form of mis-communication when I did my testing. I am not working on these until I can get the device from utkanos. Check Update 2, in the initial post.
Success
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Man I can't wait till this is perfect, you guys are fricken awesome. I raped your thanks buttons op lol
MoPhoACTV Initiative
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
ClearD said:
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
Click to expand...
Click to collapse
All recoveries will now use edify, amend is old and depreciated, you will only find that on old devices.
Corrupt Kernel...
innovatelife said:
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Click to expand...
Click to collapse
This is a classical case of a corrupt Kernel. Not that the images are corrupt, but somewhere along your update, your boot.img did not install the kernel properly and now you have a broken power manager within kernel.
What I would do is the following:
Hook your watch to the charger and let the M sign show up.
Even if it hangs on the M, leave your watch hooked over night.
Try downloading an older image and use fastboot to erase everything and then flash everything back again. This should return your watch to a working state again.
You may then choose to customize it as you see fit.
Root tool > "return to stock"
Sent from my HTC Inspire 4G using XDA-funded carrier pigeons
simx said:
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
Click to expand...
Click to collapse
I'm about to try this.. but it's making me think... Do you think the updater-script doesn't correctly format system? Think about it... our devices say 4.55.97 (mine changed to that after a reboot or two), and we only had partial features... sounds like something isn't wiping correctly.
Greetings,
Quick history of the problem:
*I have a Defy, with stock rom, rooted, and TWRP 2.1. I have a full android backup with TWRP.
*I flash CM9-NIGHTLY-120716-Defy.zip. I reboot, everything is fine.
*I reboot into new CWM recovery, make another android backup with CWM.
*I install TWRP 2.1 again.
*I flash CM10-20120924-NIGHTLY-mb525.zip.
*But then, I immediately flash again TWRP 2.1 (I think that was a mistake).
*I reboot, CM10 works fine.
*But when trying to boot into recovery from (new) bootmenu, TWRP immediately crashes and phone reboots I have no recovery mode available.
*At this time, phone still boots into CM10 just fine.
*I spend many hours trying to find how to flash a proper recovery, but to no avail. In desperation, I then follow the same recovery install procedure I followed many time ago after rooting the phone (see for example "wiki.cyanogenmod.org/w/Install_CM_for_jordan"). So bootmenu 0.61 is installed.
*And now the phone always reboots into bootmenu 0.61; recovery cannot be accessed ("recovery.sh not found"); CM10 does not boot.
So the phone is (probably soft) bricked.
At this point, after reading different posts, the only solution I have in mind is to flash a stock sbf file. However, since most of my previous actions have resulted in worse and worse situation, I am not sure this is the best solution.
What would you advise?
Thank you,
Colinou
EDIT: after reading different posts, finally flashed stock rom with sbf file following tutorial in forums. No problem encountered, apart from starting over everything.
EDIT2: I now realise that the reason for always booting to bootmenu, was that bootmenu 0.61 was set to always boot to bootmenu! There is an option in the bootmenu to start phone to "default" instead of "bootmenu". Anyway, the recovery was still broken, so I needed to flash a SBF file anyway.
Help with SBF
ColinouRussie said:
Greetings,
Quick history of the problem:
*I have a Defy, with stock rom, rooted, and TWRP 2.1. I have a full android backup with TWRP.
*I flash CM9-NIGHTLY-120716-Defy.zip. I reboot, everything is fine.
*I reboot into new CWM recovery, make another android backup with CWM.
*I install TWRP 2.1 again.
*I flash CM10-20120924-NIGHTLY-mb525.zip.
*But then, I immediately flash again TWRP 2.1 (I think that was a mistake).
*I reboot, CM10 works fine.
*But when trying to boot into recovery from (new) bootmenu, TWRP immediately crashes and phone reboots I have no recovery mode available.
*At this time, phone still boots into CM10 just fine.
*I spend many hours trying to find how to flash a proper recovery, but to no avail. In desperation, I then follow the same recovery install procedure I followed many time ago after rooting the phone (see for example "wiki.cyanogenmod.org/w/Install_CM_for_jordan"). So bootmenu 0.61 is installed.
*And now the phone always reboots into bootmenu 0.61; recovery cannot be accessed ("recovery.sh not found"); CM10 does not boot.
So the phone is (probably soft) bricked.
At this point, after reading different posts, the only solution I have in mind is to flash a stock sbf file. However, since most of my previous actions have resulted in worse and worse situation, I am not sure this is the best solution.
What would you advise?
Thank you,
Colinou
EDIT: after reading different posts, finally flashed stock rom with sbf file following tutorial in forums. No problem encountered, apart from starting over everything.
EDIT2: I now realise that the reason for always booting to bootmenu, was that bootmenu 0.61 was set to always boot to bootmenu! There is an option in the bootmenu to start phone to "default" instead of "bootmenu". Anyway, the recovery was still broken, so I needed to flash a SBF file anyway.
Click to expand...
Click to collapse
Hi, can you please send a link for SBF, because I am having hard time searching.It seams that default link for SBF-s doesent work.
Thanks
Matija28 said:
Hi, can you please send a link for SBF, because I am having hard time searching.It seams that default link for SBF-s doesent work.
Thanks
Click to expand...
Click to collapse
Hi, Can you send me how to add twrp to stock sbf like which file will work from Motorola recovery menu or any apk ?
Hello,
Could you help me? The site sbf.droid-developers.org is offline. I need any retail sbf file to unbrick my defy mb526. Does anyone have a mirror for a stock rom of this device?
gabrielms26 said:
Hello,
Could you help me? The site sbf.droid-developers.org is offline. I need any retail sbf file to unbrick my defy mb526. Does anyone have a mirror for a stock rom of this device?
Click to expand...
Click to collapse
There is a link on quarx page,i used this to unbrick & root mine,if it helps ,i cannot post links so find it own.
Hai,
I don't remember where I downloaded the stock sbf file from, most likely from sbf.droid-developers.org, which is down now
However I kept a copy of the sbf file on my computer , it is a french retail version (but langage can be changed later), in case of desperate need, I can post it somewhere.
Nr
ColinouRussie said:
Hai,
I don't remember where I downloaded the stock sbf file from, most likely from sbf.droid-developers.org, which is down now
However I kept a copy of the sbf file on my computer , it is a french retail version (but langage can be changed later), in case of desperate need, I can post it somewhere.
Nr
Click to expand...
Click to collapse
I'm in need of an sbf file. I have a tmobile us defy will this work with it? my phone is in a bootloop. I searched high and low in this forum and on the internet all the links point to sbf.droid-developers.org or multiupload both are down. If anyone has any sbf files please upload them. thanks in advance.
axel2230 said:
I'm in need of an sbf file. I have a tmobile us defy will this work with it? my phone is in a bootloop. I searched high and low in this forum and on the internet all the links point to sbf.droid-developers.org or multiupload both are down. If anyone has any sbf files please upload them. thanks in advance.
Click to expand...
Click to collapse
I will send you a link by private message. I don't know if it will work with Tmobile, but at least you can boot your phone and flash another rom afterwards. At start it will ask you to login to motoblur, just cancel the requests, change language to english, and you're set.
Nr
defy stuck on CMR
hi guys i defy was stuck on boot it keeps on showing motorola logo then i think there is a problem i think i did a mistake that i nstalled Cynogen 7 and after using it for some time i again installed a back up from miui rom there i did a mistake and when iam on the recovery menu i cant select any option touchscreen is not working..pls help me guys
ONE Click Warranty Back
hello Friends This My First Thread on G 2014(Titan)
Now Get Yours Warranty Back In just one Click
No need to rememberer all this such big commands of FastBoot
i gonna present the simplest way to revert back to stock official Roms with both locked and unlocked Boatloader(after flash) which r Provided in the below links
Pls do press thanks If u really liked my work i need it :good:
best simple way in simple one click (action performed)
!!Disclaimer!!
NOTE: I am not responsible for any kind of boot-logo, corrupt partition,bricked devices, dead SD cards,other Issue etc As I am just new to android developing
This process have been tested personally on my device moto g 2104
NOTE :This Will wipe all your data so pls take all yours useful databackup
INSTRUCTION
1) Download and install the Basic Moto Drives in this http://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97326/p/30,6720,9050
2)Download the required Official Firmware(KitKat,Lollipop) form here https://mega.nz/#F!Q9YHCQzY!dgyvAJ8eNA3t7az4vizwOQ which i have taken Through Original Motorola Firmware Collection[Thread] thanks to @gregor160300
all the Firmware are Official images and are uploaded Recently
3)Download the OneClick Tool zip according to yours need a(locked) and b(Unlocked) form Here
a)restore with locked Boatloader Here https://drive.google.com/open?id=0By-2WiK-9wJqfmlMT3BoMmxqakU0M0lJdDk0OGF3UmVJZWN5eW90a0pIdUtSU3BRb0pxbms
b)restore with unlocked Boatloader Here https://drive.google.com/open?id=0By-2WiK-9wJqfktRWG1wbFJ6S2JnLU5FTFBNUWp2ckRZWnZmMUVfV1hiX3JjUGw0am1LR2s
4)Now Extract the Firmware zip to a Particular Folder at your given location on your PC/Laptop
5)After That Extract the OneClick zip to a Same Folder (Where U have the Extracted the Firmware Files)
6)Boot your Moto G 2014 into FastBoot Mode and plug your Device into your computer (pls Make sure u have all the proper device drivers are installed)
6)Finally Go To the Extracted Folder and u will see OneClick .bat file just click on OneClick
U r done Njoy till its gets Completed
All the Firmware are Official images Your warranty may not Void also u may get Yours Warrenty Back
hope u Enjoy this
PLS DON'T MIRROR THE LINKS
sry for my bad english i will improve
special Thanks to both @ archies20 @gregor160300,Shawn5162 for their thread:laugh::laugh:
Please Do press Thanks button if u really liked My Work i really need it :good:
It's For Indian Version ?
yes u can check this according to the indian baseband
Tried it today and it worked flawlessly, thanks!
heeey thanks 4 the reveiw hope i will come with other thread
so hey guys. i have a moto g 2014 xt1068 dual sim variant. for some reason after unlocking bootloader, flashing TWRP, and flashing an other ROM(blisspop 5.1.1) for some reason my first sim card slot was like not working at all and my second sim doesnt have mobile data only calls. So I flashed stock firmware 5.0.2(RETAILDSDSALL_XT1068_5.0.2_LXB22.46-28_cid7_CFC.xml) but the problem still exists. I dont know what to do :'( any help?
Mike20017 said:
so hey guys. i have a moto g 2014 xt1068 dual sim variant. for some reason after unlocking bootloader, flashing TWRP, and flashing an other ROM(blisspop 5.1.1) for some reason my first sim card slot was like not working at all and my second sim doesnt have mobile data only calls. So I flashed stock firmware 5.0.2(RETAILDSDSALL_XT1068_5.0.2_LXB22.46-28_cid7_CFC.xml) but the problem still exists. I dont know what to do :'( any help?
Click to expand...
Click to collapse
Change both sim slots?
do a clean Install make a try if still not working change the baseband version and check out again if still not working den hope a hardware fix will resolve it
Hello,
First things first: thanks for this great tool! I needed to restore the original firmware and didn't know how to do that. With this tool it's quite simple.
I had only two small problems:
- the first time I've run tour .bat file I seen several commands being executed, all of the m with an OK in the end, but after all process the phone didn't boot, no recovery also. I ran the .bat file a second time and it's OK now.
- another strange thing happened: the boot logo screen reverted to the "unlocked bootloader" screen.
A question: can I flash only the bootlogo screen via adb?
Moto bootloop struck help help
Hello can any senior member plz help me out.
I have unlocked and rooted moto g2 2014 mobile it was working fine.
But I done a stupid thing by editing system file and overwriting it.
Then my phone stuck in boot loader
I can access recovery TWRP i tried to wipe Delvic and cache and factory resetting but it did'nt worked.
Therefore buy following the link i tried to flash with orginal frimware
www droidviewsmoto g 2014 to stock and lock the bootloader
it was not successful again it strucked in boot loop with Android dead symbol in recovery
------>> Then tried to install TWRP recovery it was successful, but unable to install super user.
There fore I tried to repeat the process buy using both sdk windows platfom tools and vfastboot
buy typing command in cmd as mfastboot.exe oem lock begin
and noticed error saying
hab check failed for boot
failed to verity hab image boot
failed to validate boot image
Plz sir can any one help me out plz
yes
yes u can using the img file
follow this instructions to remove the warning instruction
http://www.bhudroid.com/2015/08/remove-unlocked-bootloader-warning-on.html
Kindly First Update yours boot loader Version
Kindly First Update yours boot loader Version
this can be the an issue
and after that cleanly flash the latest TWRP recovery
and Finally any Latest Build Custom Rom
this may Works
Marcelo_RJ said:
Hello,
First things first: thanks for this great tool! I needed to restore the original firmware and didn't know how to do that. With this tool it's quite simple.
I had only two small problems:
- the first time I've run tour .bat file I seen several commands being executed, all of the m with an OK in the end, but after all process the phone didn't boot, no recovery also. I ran the .bat file a second time and it's OK now.
- another strange thing happened: the boot logo screen reverted to the "unlocked bootloader" screen.
A question: can I flash only the bootlogo screen via adb?
Click to expand...
Click to collapse
yes u can using the img file
follow this instructions to remove the warning instruction
http://www.bhudroid.com/2015/08/remove-unlocked-bootloader-warning-on.html
Kindly First Update yours boot loader Version
sudheerkk87 said:
Hello can any senior member plz help me out.
I have unlocked and rooted moto g2 2014 mobile it was working fine.
But I done a stupid thing by editing system file and overwriting it.
Then my phone stuck in boot loader
I can access recovery TWRP i tried to wipe Delvic and cache and factory resetting but it did'nt worked.
Therefore buy following the link i tried to flash with orginal frimware
www droidviewsmoto g 2014 to stock and lock the bootloader
it was not successful again it strucked in boot loop with Android dead symbol in recovery
------>> Then tried to install TWRP recovery it was successful, but unable to install super user.
There fore I tried to repeat the process buy using both sdk windows platfom tools and vfastboot
buy typing command in cmd as mfastboot.exe oem lock begin
and noticed error saying
hab check failed for boot
failed to verity hab image boot
failed to validate boot image
Plz sir can any one help me out plz
Click to expand...
Click to collapse
Kindly First Update yours boot loader Version
this can be the an issue
and after that cleanly flash the latest TWRP recovery
and Finally any Latest Build Custom Rom
this may Works
thnks .......
woow its working great . very simplest way thank u so much
bhu999 said:
heeey thanks 4 the reveiw hope i will come with other thread
Click to expand...
Click to collapse
Can I get OTA update after this ?
I just want to know can I get OTA update after this if Motorola roll out any update in the near future.
mudit56 said:
I just want to know can I get OTA update after this if Motorola roll out any update in the near future.
Click to expand...
Click to collapse
Yes
woow...
wow its working great for me... very simply to use ... am not face any bugs.......... thanks for your work:good:
@bhu999 Thanks it worked awesome.
one question can i get official OTA update from Motorola if i root my device now ??? Because for rooting custom recovery is required and it is impossible to get OTA while on custom recovery. Right ??
yes u can but with stock recovery
just flash the stock recovery to get the available update also
In One Click method u can get the official available update after completing the whole procedure
Hey people,
I've updated to the unofficial Nougat leak here and ever since I can't get into the recovery. The ROM is OK but no matter what I do I can't get into the recovery. After "adb reboot recovery" I just get stuck in a boot loop and I must get into the upgrade utility and restart phone into the system from there. I've tried to flash few other recovery but nothing works. So far I'm fine with the system and I'd like to also try LineageOS but I have no way to flash the ROM. I have tried "Fastboot flash zip xx.zip" from the bootloader to flash LineageOS but it told me I don't have permissions so it was no good.
So do you folks here have any idea what I did wrong and how to make the recovery work again? I'm kind of learn from the tutorial guy so I'll post the sources I've been using to do the flash.
Unlocking bootloader and flashing new recovery
I've only used the unlock bootloader and flash twrp sections with their provided recovery. I've also tried to flash THIS recovery by Meticulus after the nougat update.
Flashing the ROM + used ROM
Used the old process because upgrade with system utility kept giving me errors.
Model number - VNS-L21
Also if this issue can't be (yet) fixed do you know any way to safely flash ROMs without recovery?
Thanks for any kind of help
You cannot flash any ROM in the nougat recovery, because it does not support /data mounting. Downgrade to MM and install the ROM you want from there.
@SALVO9
Ok, thank you for the reply. I'll probably try to downgrade and flash it afterwards to know which ROM suits me better. All I need to do is find the stock ROM copy it to the phone and restart with all buttons pushed right? Also, do you have any info about when there will be a nougat recovery that can mount /data?
TheAstaros said:
@SALVO9
All I need to do is find the stock ROM copy it to the phone and restart with all buttons pushed right?
Click to expand...
Click to collapse
No.
Flash proper OEMinfo first!
@Schlengge
Thanks for the advice. I did my research because I didn't know a thing about oeminfo and I have hit a wall since my phone is not rooted(Should have mentioned that earlier I know) and I'm supposed to replace custom.bin and then flash the img. So afterwards I searched how to root this nougat ROM and found nothing no app was working and everything I found was just using the phone's recovery which I can't access. Does anything come to mind? I will continue getting through the pages of google but I don't think I'll find anything useful.
EDIT> After some searching I found the official rollback package. I have yet to test it (downloading on slow connection atm) and I hope it will work.
Ok it's finally done and I'm back at old stock ROM(EMUI 4.1.1 VNS-L21C432B160) after hours of searching I gave up on the oeminfo or rooting the phone. I searched for the stock firmware and found some rollback packages on the Huawei site. I will post the links in there you even have instructions packed with the zip.
LINK1
LINK2
Download both start with the smaller one because it's flashing first and follow the instructions in the pdf. Worked for me so hope it also helps you.
Also as I found out just now this rollback also locks back your bootloader so be sure to unlock it back again with the code.