Database Info

If I can get into the Fastboot screen I am not fully bricked??

I can boot with volume up and get to the recovery screen. I am combing threads and doing all I can now. Any help is greatly appreciated. Downloading the SDK on slow work internet now and attempting to get all files I think I might need as we speak.

give members more details [what did u flash etc], so they can help u.

No, if you have recovery mode available nothing is lost.
Just download a ROM you like, and try flashing it. If it doesn't work, try formatting and then flashing again.

I flashed one click stock and I saw that SYSTEM failed while it was running. Now I get no boot but I can get to the stock recovery.
How do I get a rom onto the phone in its current state?
when I boot with the vol up / power combination I get a small menu for reboot bootloader, reboot, recovery or power off. If I select recovery I get the triangle icon with the ! and then after a minute or so I can get to what looks like a very small clockwork menu with: reboot system now, apply update from /sdcard, wipe data/factory reset or wipe cache partition. I have tried to apply a rom I had on in the list but it failed verification and the list is only partital it does not let me go all the way down.

In recovery you can still use adb to transfer files to the device.
Code:
adb push update.zip /sdcard

I am having trouble getting adb to work. I am following these instructions but something seems to be wonky?
http://androidadvices.com/how-to-install-set-up-and-use-adb-for-android-devices/#.UAWbt7Sm_Nk
can you point me in a better direction to get adb access

I just noticed at the bottom of my screen in slightly greyed out copy it reads: FASTBOOT STATUS - FAILINVALID COMMAND

magicwands said:
I flashed one click stock and I saw that SYSTEM failed while it was running. Now I get no boot but I can get to the stock recovery.
How do I get a rom onto the phone in its current state?
when I boot with the vol up / power combination I get a small menu for reboot bootloader, reboot, recovery or power off. If I select recovery I get the triangle icon with the ! and then after a minute or so I can get to what looks like a very small clockwork menu with: reboot system now, apply update from /sdcard, wipe data/factory reset or wipe cache partition. I have tried to apply a rom I had on in the list but it failed verification and the list is only partital it does not let me go all the way down.
Click to expand...
Click to collapse
That small menu as you called it is fastboot.
That recovery is stock recovery.
Connect to phone to computer and use fastboot to flash a custom recovery. Boot into said recovery. Mount usb storage. Transfer rom over to phone. factory reset/format system and flash new rom.
If you don't know how set up and use fastboot. Look it up.

I got the bootloader unlocked and TWRP installed but whenever I try to flash a rom I get the error message " E:error in /tmp/sideload/package.zip (status 7)
Any thoughts?

magicwands said:
I got the bootloader unlocked and TWRP installed but whenever I try to flash a rom I get the error message " E:error in /tmp/sideload/package.zip (status 7)
Any thoughts?
Click to expand...
Click to collapse
Do a full wipe, re-download the rom ( make sure its the correct rom for your device) and try again.
If it still fails. Flash the official stock images and make sure that at least works

I am fully wiped but I am going through the process again just to be sure, all I have on the device right now is TWRP its unlocked and boots into TWRP recovery fine. But everytime I flash, I have tried 3 roms and one was the NS4G_IMM76d_deodexed it hits me with the same error as before: e:error in /tmp/sideload/package.zip (status 7)
I am searching frantically for a fix, any help is appreciated.

magicwands said:
I am fully wiped but I am going through the process again just to be sure, all I have on the device right now is TWRP its unlocked and boots into TWRP recovery fine. But everytime I flash, I have tried 3 roms and one was the NS4G_IMM76d_deodexed it hits me with the same error as before: e:error in /tmp/sideload/package.zip (status 7)
I am searching frantically for a fix, any help is appreciated.
Click to expand...
Click to collapse
Download the following files:
7-Zip from http://www.7-zip.org
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
http://android.kcomputerzone.com/stock/sojus-imm76d-factory_windows-scripts.zip
http://android.kcomputerzone.com/extras/crespo-drivers.zip (just in case you need them)
Install 7-Zip
Extract sojus-imm76d from sojus-imm76d-factory-10660f4c.tgz (You will need to go in multiple levels deep to get to folder) to your desktop.
Extract contents of sojus-imm76d-factory_windows-scripts.zip to the sojus-imm76d on your the desktop.
With phone in bootloader mode run flash-all.cmd in the sojus-imm76d folder.
If all worked it should be boot and be working.
That should restore yours to default firmware all using fastboot. Hope this helps.

This site (http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/) got me up and running with TWRP then I been having issues flashing roms, I am able to get a Peter Alfonso stock rom to boot but then if I try to flash I get the same error. I was able to ODIN the stock 4.0.4 but nothing seems willing to flash via clockwork or TWRP.

Ok just to bring some closure to this, thanks for all the help. My problem with the status 7 error was that I was using the wrong clockwork recovery. It was bundled in a one click root for Nexus Galaxy and Nexus S, the Root worked great but the recovery was the incorrect version. In any event I am now 100% functional. Thanks to all that helped out.

magicwands said:
Ok just to bring some closure to this, thanks for all the help. My problem with the status 7 error was that I was using the wrong clockwork recovery. It was bundled in a one click root for Nexus Galaxy and Nexus S, the Root worked great but the recovery was the incorrect version. In any event I am now 100% functional. Thanks to all that helped out.
Click to expand...
Click to collapse
That is the problem with One click root/unroot. I know the simplicity is awesome but the end user is learning nothing. Doing it the ol' fashion way teaches the user how to use SDK, ADB, and other important simple things. I always say use the guide and do it yourself. Problems happen and instead of having to start a new thread you can trouble shoot it yourself. :good:

4.4.1 Update failing because of android.policy.odex

Hey, I tried flashing the new Android version 4.4.1 and this is what happens:
Code:
Updating partition details...
Starting ADB sideload feature...
Installing '/data/media/0/sideload.zip' ...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying current system...
"/system/framework/android.policy.odex" has une
E:Error executing updater binary in zip '/data/
And at the top of the screen there's a red colored "Failed" notification.
I'm guessing it's because the phone is rooted? Or what should I be doing to fix the problem? thanks.

sneak310 said:
Hey, I tried flashing the new Android version 4.4.1 and this is what happens:
Code:
Updating partition details...
Starting ADB sideload feature...
Installing '/data/media/0/sideload.zip' ...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying current system...
"/system/framework/android.policy.odex" has une
E:Error executing updater binary in zip '/data/
And at the top of the screen there's a red colored "Failed" notification.
I'm guessing it's because the phone is rooted? Or what should I be doing to fix the problem? thanks.
Click to expand...
Click to collapse
Rooting is not the problem. If you made changes to the system the ota won't work. Fastboot flash the system and boot image from 4.4

jd1639 said:
Rooting is not the problem. If you made changes to the system the ota won't work. Fastboot flash the system and boot image from 4.4
Click to expand...
Click to collapse
So I need to go into TWRP and "Install" then choose the zip and flash it?

sneak310 said:
So I need to go into TWRP and "Install" then choose the zip and flash it?
Click to expand...
Click to collapse
No, that will fail too.
You have made changes to the system. Whether its the dalvik mod, camera mod, center clock mod, etc or change build.prop.
You need to use fastboot to flash the stock system.img from here
http://forum.xda-developers.com/showthread.php?t=2513701

Synyster06Gates said:
No, that will fail too.
You have made changes to the system. Whether its the dalvik mod, camera mod, center clock mod, etc or change build.prop.
You need to use fastboot to flash the stock system.img from here
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Yep, it was the camera mod. Thankyou. I'll try that out.

I let it finish and it started the phone in normal mode, I went through the prompts about google's initial setup and let the phone sit a couple minutes. I turned it off and used volume down + power and selected recovery mode and now there's an android icon with a red warning sign and a black "!" on the sign and I can't do anything at all.
What now?
Edit: the phone randomly booted normally now..
I did try volume up and power but it doesn't do anything..
This step:
"After everything finished, select "Recovery" using the volume buttons."
Is incorrect, since the phone boots up as soon as the flash is finished.
Edit 2: I found it wasn't doing anything because I was "holding" instead of "pressing". Instead of following directions I assumed it was a typo and should be done the way all the other volume/power button combos are done. Big nub mistake, sorry.

4.4.1 was so yesterdays news....

BCSC said:
4.4.1 was so yesterdays news....
Click to expand...
Click to collapse
lol.. going to install 4.4.2 in a moment but lesson still learned and a thread left over for people who have the same question in the future.:good:

[Q] Moto G keeps on rebooting and updating

This morning my device was asking if it could do a firmware (?) update. I confirmed and of that moment it keeps on rebooting and trying to install an update. Whatever I try I can't get through the loop of updating/rebooting. I thought that maybe via the bootloader (which is working) I can install a new ROM or restore the stock firmware, but nothing is helping. When in the bootloader, the PC can find the device although it is connected (USB connected)
What I see when it's rebooting:
Install untrusted package?
this can not be undone
- no
- yes
- go back
CWM based recovery v6.0.4.5
E: invalid command argument
finding update package
opening update package
verifying update package
e: failed to verify whole-file signature
e:signature verification failed
what ever I choose it goes to the next screen:
root access possibly lost. Fix?
this can not be undone
CWM based recovery v6.0.4.5
E: invalid command argument
finding update package
opening update package
verifying update package
e: failed to verify whole-file signature
e:signature verification failed
Installation aborted
rebooting...
...and it starts all over again...it boots normally but after 10 sec it reboots again...
Has somebody any idea what the problem is and how it can be solved. As it is, I can't do anything with this mobile.
Thanks for your help!

Your post says 'PC can find the device' but I assume you mean 'PC cant find the device'.
So you have a custom recovery, are you also rooted? A custom recovery means an OTA update wont work. You need the stock recovery. I assume the custom recovery has caused the update to fail in such a way that it just keeps rebooting.
Can you manage to get into CWM via the bootloader (ie choose recovery from bootloader options using volume buttons), if so then wipe cache as this will remove the update file and you should be OK then.
If not then I think you need to get the phone seen by the PC when in the bootloader as otherwise you are stuck. I assume at some point it was seen by the PC for you to install CWM?
If running Windows do you still have the drivers installed (I run linux so Im unsure what you would need). I assume a 'fastboot devices' shows no device at all from what you say?
If you can get fastboot working you can then flash back the stock recovery and this may then allow the update to get past the point its failing at, it may still fail but then you can take it from there.
But first try getting to CWM via bootloader and wiping cache and then reboot.

scott_doyland said:
Your post says 'PC can find the device' but I assume you mean 'PC cant find the device'.
So you have a custom recovery, are you also rooted? A custom recovery means an OTA update wont work. You need the stock recovery. I assume the custom recovery has caused the update to fail in such a way that it just keeps rebooting.
Can you manage to get into CWM via the bootloader (ie choose recovery from bootloader options using volume buttons), if so then wipe cache as this will remove the update file and you should be OK then.
If not then I think you need to get the phone seen by the PC when in the bootloader as otherwise you are stuck. I assume at some point it was seen by the PC for you to install CWM?
If running Windows do you still have the drivers installed (I run linux so Im unsure what you would need). I assume a 'fastboot devices' shows no device at all from what you say?
If you can get fastboot working you can then flash back the stock recovery and this may then allow the update to get past the point its failing at, it may still fail but then you can take it from there.
But first try getting to CWM via bootloader and wiping cache and then reboot.
Click to expand...
Click to collapse
Thank you for your quick reply.
Correct. I mean the PC can't find the device. However via Motorola Device Manager it can.
Yes the phone is rooted
I can't get into the CWM. If I choose recovery from the bootloader, it reboots normally...and the loop starts again...
will try the fastboot.

How are you trying to choose the recovery option from the bootloader?
You MUST select recovery option using the VOLUME UP button (volume down to move between options and volume UP to pick an option).
Do NOT use the power button.

scott_doyland said:
How are you trying to choose the recovery option from the bootloader?
You MUST select recovery option using the VOLUME UP button (volume down to move between options and volume UP to pick an option).
Do NOT use the power button.
Click to expand...
Click to collapse
This is very good advice, regarding selecting recovery from Bootloader....
it happened to me, for days I was puzzled, even after flashing stock recovery, 4.3 Recovery, I could not enter Recovery, until I actually read what was written in the BL screen.
Use Vol down to scroll to option, then use Vol up to select that option......(Recovery)
As you say, important not to use power button.....as would come naturally, and its what we use in Recovery......
but not in Bootloader!!!!!!
I panicked so much, but just be calm!!!
Sent from my Moto G using Tapatalk
---------- Post added at 12:33 PM ---------- Previous post was at 12:30 PM ----------
irishpancake said:
This is very good advice, regarding selecting recovery from Bootloader....
it happened to me, for days I was puzzled, even after flashing stock recovery, 4.3 Recovery, I could not enter Recovery, until I actually read what was written in the BL screen.
Use Vol down to scroll to option, then use Vol up to select that option......(Recovery)
As you say, important not to use power button.....as would come naturally, and its what we use in Recovery......
but not in Bootloader!!!!!!
I panicked so much, but just be calm!!!
I think its also important in Windows, to use the Moto fastboot.....when flashing recovery from BL!!!
(search forum for mfastboot.....)
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Sent from my Moto G using Tapatalk

...I think I found the problem or better the solution...
As soon as I added AdbWinUsbApi.dll my PC could find the device...at the moment I'm flashing stock recovery. Hopefully this will help. Keep you posted guys! :good:

dutchxl said:
...I think I found the problem or better the solution...
As soon as I added AdbWinUsbApi.dll my PC could find the device...at the moment I'm flashing stock recovery. Hopefully this will help. Keep you posted guys! :good:
Click to expand...
Click to collapse
If you are rooted it will still fail to update. You are best off just clearing cache via recovery. Or delete zip file (if you get booted up) from /cache using a root file explorer.
---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------
irishpancake said:
This is very good advice, regarding selecting recovery from Bootloader....
it happened to me, for days I was puzzled, even after flashing stock recovery, 4.3 Recovery, I could not enter Recovery, until I actually read what was written in the BL screen.
Use Vol down to scroll to option, then use Vol up to select that option......(Recovery)
As you say, important not to use power button.....as would come naturally, and its what we use in Recovery......
but not in Bootloader!!!!!!
I panicked so much, but just be calm!!!
Sent from my Moto G using Tapatalk
---------- Post added at 12:33 PM ---------- Previous post was at 12:30 PM ----------
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
motofastboot is a modified fastboot that allows larger images to be flashed. Normal fastboot will work fine for recovery AFAIK.

scott_doyland said:
If you are rooted it will still fail to update. You are best off just clearing cache via recovery. Or delete zip file (if you get booted up) from /cache using a root file explorer.
---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------
motofastboot is a modified fastboot that allows larger images to be flashed. Normal fastboot will work fine for recovery AFAIK.
Click to expand...
Click to collapse
It's just that mfastboot is recommended by most devs, including Paul O'Brien and flibblesan, on Modaco, and loads of ppl here on XDA, for flashing FW to Motorola devices from BL, so I'd go with it, as it is widely available on either Modaco or XDA.
I don't think an OTA will fail due to root, just if you have modified or removed any system files, or are using a custom recovery.
I think you have to re-root after OTA is applied.
Rooting at 4.4 is easy with Chainfire's SuperSU CWM flasable zip, as explained by flibblesan here:
http://www.modaco.com/topic/368168-how-do-i-root-android-44-kitkat/#entry2188450
flibblesan, on 11 Jan 2014 - 5:05 PM, said:
Easiest way to root would be to boot a custom recovery and flash Superuser through that.
A new build of CWM recovery compatible with 4.4 bootloaders can be found here http://forum.xda-developers.com/showpost.php?p=49333040&postcount=123
Download superuser from http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip
flash recovery with the special motorola fastboot like
Code:
mfastboot flash recovery recovery.img
Click to expand...
Click to collapse

irishpancake said:
It's just that mfastboot is recommended by most devs, including Paul O'Brien and flibblesan, on Modaco, and loads of ppl here on XDA, for flashing FW to Motorola devices from BL, so I'd go with it, as it is widely available on either Modaco or XDA.
I don't think an OTA will fail due to root, just if you have modified or removed any system files, or are using a custom recovery.
I think you have to re-root after OTA is applied.
Rooting at 4.4 is easy with Chainfire's SuperSU CWM flasable zip, as explained by flibblesan here:
http://www.modaco.com/topic/368168-how-do-i-root-android-44-kitkat/#entry2188450
Click to expand...
Click to collapse
superSU updates /system/etc/install-recovery.sh
This file is checked for a hash by the script (updater-script) that installs the update. As the file is different then the script bombs out with an error.
I know this because I am rooted and I by mistake attempted to install the OTA when I got the OTA notification. It failed.
There is a line in the updater-script like this:
apply_patch_check("/system/etc/install-recovery.sh", "b54528cf9ebba39534b768ad9108a4732e1eff4a", "99ffe4a3d0e6612e87cd3f6a62dad642094f0169") || abort("\"/system/etc/install-recovery.sh\" has unexpected contents.");
This is basically checking that file and seeing if it has the expected hash (one/both of those long numbers are the hash).
Interestingly the ORIGINAL install-recovery.sh file has these comments at the start of the file:
# File Name: install-recovery.sh
#
# General Description: This script is used to install software update for
# recovery mode after OTA update. This is modified
# from original Google code to split the code into
# a fixed program while putting the dynamic data
# into a config file.
After superSU is flashed it says stuff about superSU in it and the file is completely different hence why if you are rooted (at least if using superSU) then the update fails. Whether there are also other /system files also updated by rooting I dont know.
I dont know why superSU modifies the file, the file once modified kicks off a daemon called daemonsu. Why it has to be this file to start that deamon I dont know - but obviously there must be some reason its rooted in this way.

scott_doyland said:
superSU updates /system/etc/install-recovery.sh
This file is checked for a hash by the script (updater-script) that installs the update. As the file is different then the script bombs out with an error.
I know this because I am rooted and I by mistake attempted to install the OTA when I got the OTA notification. It failed.
There is a line in the updater-script like this:
apply_patch_check("/system/etc/install-recovery.sh", "b54528cf9ebba39534b768ad9108a4732e1eff4a", "99ffe4a3d0e6612e87cd3f6a62dad642094f0169") || abort("\"/system/etc/install-recovery.sh\" has unexpected contents.");
This is basically checking that file and seeing if it has the expected hash (one/both of those long numbers are the hash).
Interestingly the ORIGINAL install-recovery.sh file has these comments at the start of the file:
# File Name: install-recovery.sh
#
# General Description: This script is used to install software update for
# recovery mode after OTA update. This is modified
# from original Google code to split the code into
# a fixed program while putting the dynamic data
# into a config file.
After superSU is flashed it says stuff about superSU in it and the file is completely different hence why if you are rooted (at least if using superSU) then the update fails. Whether there are also other /system files also updated by rooting I dont know.
I dont know why superSU modifies the file, the file once modified kicks off a daemon called daemonsu. Why it has to be this file to start that deamon I dont know - but obviously there must be some reason its rooted in this way.
Click to expand...
Click to collapse
Thanks for that info......a bit complicated, but I get the gist of why OTA will fail, if rooted using the SuperSU Recovery zip.
I suppose, as you will be un-rooted in any case, unrooting prior to OTA is advisable, I can see that....
when I rooted originally, I used Superboot, as per Paul's Option 1
However, as per the OP, and my attempted OTA, with CWM Recovery intact, and the bootloop problem, etc, etc...and my panic, and not reading what is written in BL....
I never got to flash the OTA, and I just went ahead and learned how to use fastboot, and downloaded the American ROM, flashed it, and CWM Recovery, which works with 4.4 now, and flashed the root zip, as above, and some other zip to give back the H+ for HSPA+ logo, and now I'm happy.....
I'll never have another OTA to deal with now......

When stuff goes wrong we all learn a lot more than if it always went to plan, so its good we have learnt some new things today.
When 4.4.3 is out it'll all be easy now

Everything is working again! With AdbWinUsbApi.dll I could find my device and flash it. And with the help of this topic http://forum.xda-developers.com/showthread.php?t=2542219 I was able to restore the firmware as it was...nearly...I had a Dutch (EU) version, now it's US...no big deal.

dutchxl said:
Everything is working again! With AdbWinUsbApi.dll I could find my device and flash it. And with the help of this topic http://forum.xda-developers.com/showthread.php?t=2542219 I was able to restore the firmware as it was...nearly...I had a Dutch (EU) version, now it's US...no big deal.
Click to expand...
Click to collapse
Man....you did what I did, and ended up with US 4.4.....
I had UK Tesco 4.3, with an OTA sitting in \cache, but tried to flash with CWM Recovery, messed up, panicked, but things are good now, latest CWM, rooted with SuperSU.
There is also a CWM zip to restore your H indicator for HSPA mobile speed, as US ROM only has 3G for this, and it also modifies the cell signal bars back to normal Android width.....
SystemUI_AOSP_Statusbar-signed.zip
Thanks to tilaz and flibbelsan on Modaco
Good luck from here on,

dutchxl said:
This morning my device was asking if it could do a firmware (?) update. I confirmed and of that moment it keeps on rebooting and trying to install an update. Whatever I try I can't get through the loop of updating/rebooting. I thought that maybe via the bootloader (which is working) I can install a new ROM or restore the stock firmware, but nothing is helping. When in the bootloader, the PC can find the device although it is connected (USB connected)
What I see when it's rebooting:
Install untrusted package?
this can not be undone
- no
- yes
- go back
CWM based recovery v6.0.4.5
E: invalid command argument
finding update package
opening update package
verifying update package
e: failed to verify whole-file signature
e:signature verification failed
what ever I choose it goes to the next screen:
root access possibly lost. Fix?
this can not be undone
CWM based recovery v6.0.4.5
E: invalid command argument
finding update package
opening update package
verifying update package
e: failed to verify whole-file signature
e:signature verification failed
Installation aborted
rebooting...
...and it starts all over again...it boots normally but after 10 sec it reboots again...
Has somebody any idea what the problem is and how it can be solved. As it is, I can't do anything with this mobile.
Thanks for your help!
Click to expand...
Click to collapse
I had the same situation just now. Accidentally confirmed the OTA update prompt, then the phone goes bootloop. After fiddling here and there, turns out the solution was simple. Reboot to bootloader, connect usb to PC, then wipe the cache using fastboot (fastboot erase cache). It will remove the OTA update zip file and stops the bootloop. Now I need to disable OTA update prompt.

just got the same problem!
solution that worked with me: booted in recovery, connected to pc, [left shift]+[right klick] on folder that contains mfastboot.exe, open prompt, type "mfastboot erase cache". done!
system update is now stopped
dutchxl said:
This morning my device was asking if it could do a firmware (?) update. I confirmed and of that moment it keeps on rebooting and trying to install an update. Whatever I try I can't get through the loop of updating/rebooting. I thought that maybe via the bootloader (which is working) I can install a new ROM or restore the stock firmware, but nothing is helping. When in the bootloader, the PC can find the device although it is connected (USB connected)
What I see when it's rebooting:
Install untrusted package?
this can not be undone
- no
- yes
- go back
CWM based recovery v6.0.4.5
E: invalid command argument
finding update package
opening update package
verifying update package
e: failed to verify whole-file signature
e:signature verification failed
what ever I choose it goes to the next screen:
root access possibly lost. Fix?
this can not be undone
CWM based recovery v6.0.4.5
E: invalid command argument
finding update package
opening update package
verifying update package
e: failed to verify whole-file signature
e:signature verification failed
Installation aborted
rebooting...
...and it starts all over again...it boots normally but after 10 sec it reboots again...
Has somebody any idea what the problem is and how it can be solved. As it is, I can't do anything with this mobile.
Thanks for your help!
Click to expand...
Click to collapse

dutchxl said:
This morning my device was asking if it could do a firmware (?) update. I confirmed and of that moment it keeps on rebooting and trying to install an update. Whatever I try I can't get through the loop of updating/rebooting. I thought that maybe via the bootloader (which is working) I can install a new ROM or restore the stock firmware, but nothing is helping. When in the bootloader, the PC can find the device although it is connected (USB connected)
What I see when it's rebooting:
Install untrusted package?
this can not be undone
- no
- yes
- go back
CWM based recovery v6.0.4.5
E: invalid command argument
finding update package
opening update package
verifying update package
e: failed to verify whole-file signature
e:signature verification failed
what ever I choose it goes to the next screen:
root access possibly lost. Fix?
this can not be undone
CWM based recovery v6.0.4.5
E: invalid command argument
finding update package
opening update package
verifying update package
e: failed to verify whole-file signature
e:signature verification failed
Installation aborted
rebooting...
...and it starts all over again...it boots normally but after 10 sec it reboots again...
Has somebody any idea what the problem is and how it can be solved. As it is, I can't do anything with this mobile.
Thanks for your help!
Click to expand...
Click to collapse
i repost a solution i have found to install OTA without wiping data, loosing root or flashing stock rom
http://forum.xda-developers.com/showpost.php?p=50513733&postcount=9

black screen after motorola logo
irishpancake said:
This is very good advice, regarding selecting recovery from Bootloader....
it happened to me, for days I was puzzled, even after flashing stock recovery, 4.3 Recovery, I could not enter Recovery, until I actually read what was written in the BL screen.
Use Vol down to scroll to option, then use Vol up to select that option......(Recovery)
As you say, important not to use power button.....as would come naturally, and its what we use in Recovery......
but not in Bootloader!!!!!!
I panicked so much, but just be calm!!!
Sent from my Moto G using Tapatalk
---------- Post added at 12:33 PM ---------- Previous post was at 12:30 PM ----------
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
i am having black screen issue on my MOTO G means i have installed some wrong package.... and it does not start only black screen...after a motorola starting logo so what should i do and my phone is not unlocked bootloader....please i need some serious help im getting error while installing new package via ADB is like " /system/lib/rfsa/adsp/libadsp_denoise_skel.so" has unexpected contents. and then installation aborted"" please help me!!! my phone is on XT1033 dual sim and is on 4.4.4 version when i done all this madness... for unlock bootloader.of this device please help!!! thank you!!!

same problem
bro same problem with me . what should i do now?

I had the exact same problem. Luckily I had the backup and entered the recovery mode of philz touch 6 clockworkmod v6.0.4.7 and recovered.
But I want to know, how to update the unlocked bootloader & rooted moto g xt1033 ? I'm using custom rom, its just unlocked.

[BETA][OFFICIAL] Android 7.0 EMUI 5 (L04C567B320) for FRD-L04C567

Build Number: FRD-L04C567B320 (USA)
Files for DOWNLOAD:
Download link:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1278/g104/v68366/f1/full/update.zip
Region Patch:
http://update.hicloud.com:8180/TDS/...66/f1/full/hw/usa/update_data_full_hw_usa.zip
How to install:
1. Requirements: Your device needs to have TWRP custom recovery installed and has to be rooted.
2. Before proceeding make sure that your device model is FRD-L04 from Settings > About phone.
3. Download the update.zip package from above links and copy it to your Sdcard /dload folder.
4. Turn your phone off and reboot into recovery mode by hold Vol up + Power for a few seconds.
5. Back up all the partitions into the external microSD card (recommended).
6. Now go to Install and select the update.zip package you copied to your Sdcard.
7. Upon installation wipe the cache and reboot your phone.
8. In case you encounter issues with Bluetooth, NFC, etc you can try flashing the region package provided above through TWRP.
Warning: As mentioned earlier, this is a beta update that contains many bugs and has several compatibility issues with hardware and 3rd party apps.
USE IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE FOR ANY BROKEN RELATED TO IT

perzan07 said:
Build Number: FRD-L04C567B320 (USA)
Files for DOWNLOAD:
Download link:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1278/g104/v68366/f1/full/update.zip
Region Patch:
http://update.hicloud.com:8180/TDS/...66/f1/full/hw/usa/update_data_full_hw_usa.zip
How to install:
1. Requirements: Your device needs to have TWRP custom recovery installed and has to be rooted.
2. Before proceeding make sure that your device model is FRD-L04 from Settings > About phone.
3. Download the update.zip package from above links and copy it to your Sdcard /dload folder.
4. Turn your phone off and reboot into recovery mode by hold Vol up + Power for a few seconds.
5. Back up all the partitions into the external microSD card (recommended).
6. Now go to Install and select the update.zip package you copied to your Sdcard.
7. Upon installation wipe the cache and reboot your phone.
8. In case you encounter issues with Bluetooth, NFC, etc you can try flashing the region package provided above through TWRP.
Warning: As mentioned earlier, this is a beta update that contains many bugs and has several compatibility issues with hardware and 3rd party apps.
USE IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE FOR ANY BROKEN RELATED TO IT
Click to expand...
Click to collapse
Thanks ..
I might as well post this here -> -> How to: Root and repair data on the FRD-L04 - B320
https://forum.xda-developers.com/showpost.php?p=70266853&postcount=262

Will android pay stop working even if I use the official beta 7.0?

Thanks man, but is there any successful way to flash B324 so far?

Is Wi-Fi calling enabled in this beta?

Managed to do the same using Charles app (see https://forum.xda-developers.com/ho...-to-nougat-t3510275/post69885525#post69885525) without any unlocking and flashing.

I have the FRD-L04B567 phone. I installed the TWRP for the Honor 8. I have installed a different ROM (CM13.1 ROM) successfully. I followed your instructions to the "T" in post #1 . The install of update.zip stopped at /cust with an error. I tried wiping and rebooting but am stuck in the "honor" bootup screen. Unable to force back into TWRP or fastboot or ADB at this time. Still picking up the pieces....
UPDATE: I forced phone into Huawei eRecovery screen and selected factory reset/wipe That got Nougat running but there is no keyboard and Google will only allow voice for any input. Since my wifi is encrypted, I cant give Nougat a password to get on the internet. I am creating a temporary unencrypted network to see if I can get further.
UPDATE: TWRP was wiped so I will reinstall. Then I will try update the regional update (second update mentioned)
UPDATE: Reflashed TWRP 3.0.2.0 for Honor 8, I can get into the bootloader but not recovery, eRecovery works but...(worthless). I cant flash the second update.zip because I cant get TWRP started. Obviously 3.0.2.0 is not compatible with Nougat, I may try 3.0.3.0? why not...
UPDATE - Flashing TWRP 3.0.3.0 was dumb. Now ADB sees the device (good) but I can not get to bootloader or recovery. TWRP flashes (displays) once a second and will not start (bad) . Hopefully someone can learn from my quest.
So, can someone help me proceed from a state where ADB sees the device? thanks Maybe extract update.zip?

thekubiaks said:
So, can someone help me proceed from a state where ADB sees the device? thanks Maybe extract update.zip?
Click to expand...
Click to collapse
This guy
https://forum.xda-developers.com/member.php?u=4210629
Could help you recover, but he will be back only after 15th Jan.
Have you tried Huawei's hisuite? It has a recovery option..

yalokiy said:
This guy
https://forum.xda-developers.com/member.php?u=4210629
Could help you recover, but he will be back only after 15th Jan.
Have you tried Huawei's hisuite? It has a recovery option..
Click to expand...
Click to collapse
Thanks for the reply, I finally got TWRP 3.0.2.0 for Honor 8 flashed (but now it won't work), I believe Nougat and TWRP aren't compatible. Huawei Hisuite said that phone was fine and recovery not necessary??? I disagree. I think I will have to wait for TWRP that is Nougat compatible with FRD-L04

thekubiaks said:
I have the FRD-L04B567 phone. I installed the TWRP for the Honor 8. I have installed a different ROM (CM13.1 ROM) successfully. I followed your instructions to the "T" in post #1 . The install of update.zip stopped at /cust with an error. I tried wiping and rebooting but am stuck in the "honor" bootup screen. Unable to force back into TWRP or fastboot or ADB at this time. Still picking up the pieces....
UPDATE: I forced phone into Huawei eRecovery screen and selected factory reset/wipe That got Nougat running but there is no keyboard and Google will only allow voice for any input. Since my wifi is encrypted, I cant give Nougat a password to get on the internet. I am creating a temporary unencrypted network to see if I can get further.
UPDATE: TWRP was wiped so I will reinstall. Then I will try update the regional update (second update mentioned)
UPDATE: Reflashed TWRP 3.0.2.0 for Honor 8, I can get into the bootloader but not recovery, eRecovery works but...(worthless). I cant flash the second update.zip because I cant get TWRP started. Obviously 3.0.2.0 is not compatible with Nougat, I may try 3.0.3.0? why not...
UPDATE - Flashing TWRP 3.0.3.0 was dumb. Now ADB sees the device (good) but I can not get to bootloader or recovery. TWRP flashes (displays) once a second and will not start (bad) . Hopefully someone can learn from my quest.
So, can someone help me proceed from a state where ADB sees the device? thanks Maybe extract update.zip?
Click to expand...
Click to collapse
If you want to get back to any working state, i recovered from 7.0 unbootable to vanilla 6.0 like so (for frd-l09, but probably still applies):
https://forum.xda-developers.com/honor-8/how-to/honor-8-bricked-t3521813/post70326674#post70326674
// edit, also for completeness, i then flashed twrp 3.0.2 (official) and installed the cm 7.1.1 from the other thread here. All working fine.

fuflo,
thank you for your reply, it helped me get my Honor 8 back up and running.... I am now running CM 14.1 and Nougat 7.1.1 on my FRD-L04
Cheers
---------- Post added at 05:32 AM ---------- Previous post was at 05:31 AM ----------
fuflo,
thank you for your reply, it helped me get my Honor 8 back up and running.... I am now running CM 14.1 and Nougat 7.1.1 on my FRD-L04
Cheers

B320? I used these update files and mine says B317. Am I missing something?

jim262 said:
B320? I used these update files and mine says B317. Am I missing something?
Click to expand...
Click to collapse
Look again in the thread closely, you'll find another script to go to B320

Same problem as above, I could flash the update.zip, but not the USA package, maybe I didn't have the right TWRP version?

Stuck in "Your device has been unlocked and can't be trusted" screen.

Hi everybody, I've been trying to unlock root on my Honor 6x BLN-L21 with Android 7 EMUI 5 (updated from Android 6) and I found myself following this guide. At first something went wrong as I got this error: "failed to mount /system (Invalid argument)", so I went under Advanced Wipe section of TWRP 3.1.1.0 and changed system partition format from EXT4 to FAT and then back to EXT4, and it solved. The installation of SuperSU didn't show any error message but as soon as I reboot my mobile from that screen, I get the screen in the title. Of course it won't let me run any update, meaning Volume UP + Volume Down + Power would just let me stick in the "Honor" blue screen with no progress showing. I need help to solve, thanks in advance.
PS: The only thing I get is: "No OS installed!". I'm astonished....

Use this guide to fix your phone. If you have any questions about the steps just ask.
https://forum.xda-developers.com/showpost.php?p=73954487&postcount=240
TIP: If the version number you download wont flash using dload then try a lower version. For example. Even though my phone was on BLN-L24C567B366 when i messed it up i could only flash the BLN-L24C567B360 files. I updated once the process was complete.
Tip 2: Instead of Super Su. Try magisk instead. It allows you to root your phone and still use apps that refuse to work on rooted devices(pokemon go for example but theres many more.) You simply flash magisk with twrp and install the magisk manager apk. Everything is here. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

This is gonna fail for sure, as every kind of update I try using dload method will permanently stick at 5%.
EDIT: I could solve installing via TWRP this custom ROM.

Baffol2asta said:
Hi everybody, I've been trying to unlock root on my Honor 6x BLN-L21 with Android 7 EMUI 5 (updated from Android 6) and I found myself following this guide. At first something went wrong as I got this error: "failed to mount /system (Invalid argument)", so I went under Advanced Wipe section of TWRP 3.1.1.0 and changed system partition format from EXT4 to FAT and then back to EXT4, and it solved. The installation of SuperSU didn't show any error message but as soon as I reboot my mobile from that screen, I get the screen in the title. Of course it won't let me run any update, meaning Volume UP + Volume Down + Power would just let me stick in the "Honor" blue screen with no progress showing. I need help to solve, thanks in advance.
PS: The only thing I get is: "No OS installed!". I'm astonished....
Click to expand...
Click to collapse
Use team mt multi tool
Provide required file from update.app

siddhrsh said:
Use team mt multi tool
Provide required file from update.app
Click to expand...
Click to collapse
I had solved already (look at the previous EDIT). Thanks anyway.