Hi everyone, so i bricked my phone after rooting it and trying new ROM. Unfortunately i'm a noob and didnt make a backup before.. So now the phone is on loop mode and basically i've tried almost every guide that is out there to unbrick it, still no luck
It gives me installation aborted error message and even if the installation of new rom succeeds, it still keeps on looping :S
Is there a way unbricking it or should i use it as a hammer from now on..
Any help is appreciated, tnx!
EDIT: Maybe it helps to answer, if i write what i've done so far and describe the problem.
It's on the loop mode, which means it doesnt go further than the screen with green htc text. I can bootload and hit recovery with pressing power and down button on same time. Before Fastboot, recovery, factory sheet, simlock and image crc it tells sd checking and "no image". PB31IMG.zip is also on the sdcard and have tried to install that, still abort message..
I've tried with update.zip file, it gives me following error and the end:
file_getprop: failed to stat ''/system/build.prop'' no such file or directory
E:Error in /sdcard/update.zip
Status 7
Installation aborted.
Wiped cache, data and etc
Disabled signature verification
Tried with RUU, turned off unnessecary programs, disabled firewall and antivirus.
It gives error [170]:usb connection error.
Yes usb is connected to the pc and phone.
Phone has Revolutionary cwm
HBOOT-1.49.1187
RADIO-10.13.9020.08_2M
eMMC-boot
Jul 12 2011, 15:29:51
What else should i try ? I certanly can't think of anything
Fixed it myself after a 2 day marathon..
1. Put PG86IMG.zip and Virtuous_shooter-v.1.0.1 file on the sdcard..
2. Rebooted to recovery, PG86IMG image started the update.
3. Deleted the zip file from card and rebooted again.
4. Installed Virtuous_Shooter zip file and it started to update system and booted itself
Thats it!
Worked for me
PG86IMG should work almost every time.
mimmus said:
PG86IMG should work almost every time.
Click to expand...
Click to collapse
Well it did't many many many times.. maybe the file was corrupted or smth
awesome lol.
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:
I am super excited to see an official cyanogenmod for the photon Q 4G LTE. I quickly installed the motorola drivers for the phone, android sdk, unlocked the bootloader with motorola's unlocker, installed ClockworldMod Recovery 6.0.1.3 using fastboot.
Now using cw recovery I am trying to flash cm-10.1.3-RC2-xt897c.zip off my external SD card. The process starts fine buts ends up giving an error.
Code:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
E:Error in /external_sd/cm-10.1.3-RC2-xt897c.zip
(Status 7)
Installation aborted.
I get the same result regardless if I "wipe data/factory reset", "wipe cache partition", and "advanced/wipe dalvik cache".
According to a google search, the status 7 means the rom does not think it is compatible with the phone its being installed to. Well, I checked META-INF/com/google/android/updater-script.txt as described and it contains an entry for
Code:
getprop("ro.product.device") == "xt897c" || getprop("ro.build.product") == "xt897c");
.
It seems like everything checks out. Any ideas why the install is failing?
nezzer said:
I am super excited to see an official cyanogenmod for the photon Q 4G LTE. I quickly installed the motorola drivers for the phone, android sdk, unlocked the bootloader with motorola's unlocker, installed ClockworldMod Recovery 6.0.1.3 using fastboot.
Now using cw recovery I am trying to flash cm-10.1.3-RC2-xt897c.zip off my external SD card. The process starts fine buts ends up giving an error.
Code:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
E:Error in /external_sd/cm-10.1.3-RC2-xt897c.zip
(Status 7)
Installation aborted.
I get the same result regardless if I "wipe data/factory reset", "wipe cache partition", and "advanced/wipe dalvik cache".
According to a google search, the status 7 means the rom does not think it is compatible with the phone its being installed to. Well, I checked META-INF/com/google/android/updater-script.txt as described and it contains an entry for
Code:
getprop("ro.product.device") == "xt897c" || getprop("ro.build.product") == "xt897c");
.
It seems like everything checks out. Any ideas why the install is failing?
Click to expand...
Click to collapse
If it was not compatible, you would get an "assert failed", not "status 7" (I would think?)
If you think it is the assert that is failing, remove that line. Also, that updater-script file shouldn't be a .txt file - it should have no file extension.
In googling that error, everyone does seem to agree tho that status 7 is a mismatch, so I spose try removing that line. I usually would get an 'assert failed' message if these didn't match up - but I use TWRP, maybe that's the difference.
Bad to worse. I had booted the phone multiple times into recovery trying to apply the firmware. No matter what, when I later try to boot the OS, it just stayed stuck at the "boot loader unlocked" warning message, presumably because the firmware was never applied successfully. I left the phone at that screen overnight connected to the computer via USB.
Today I figured I would go ahead and try flashing TWRP to see if that changed anything. Now I am unable to get the phone to power on at all. Pressing the power button has no effect. Same for pressing vol down + pwr. When I plug it into USB the LED turns green but nothing happens on the display. Running adb devices or fastboot devices both say nothing is connected.
The thing appears completely dead. I took the case off and unscrewed the battery terminals for 5 minutes before screwing them back on. Still nothing. The display backlight never powers on.
This is a real bummer. Anyone run across anything like this before?
*Update* It would appear that the phone was not charging when stuck at the bootloader unlocked warning screen despite being connected to my PC. I left my phone on the charger for about 10 minutes and it popped back on to the bootloader unlocked screen. I was able to reboot to the fast boot screen. Since the state is reported as "battery low" I cant flash anything. I will report back once I can flash TWRP.
Mystery solved.
I flashed openrecovery-twrp-2.6.3.0-asanti_c.img and tried installing cm-10.1.3-RC2-xt897c.zip again. No go. Thankfully twrp has some nice features including a great file manager. I tried chmod 777 on the cm zip. No change. I then copied the cm zip from my external sd card to the internal memory. This failed a number of times before it went through successfully. That was my first clue.
I was able to flash cm from the internal sd card no problem. My guess is that my external SD card is experiencing read errors which caused the prior flash attempts to fail. Its working now.
I thought those problems have been solved and/or are nearly not existent.
My SD-Card became defective a few month after using it with my Photon Q. (Got a replacement within warranty.)
I guess that the Photon Q is kind of sensible which mSD's are working and which not.
My current mSD is working flawlessly.
But I flash nearly everytime over the internal storage, just to be sure that I don't get "invisible read errors" during flashing.
You should check your file, a hash may be the way to go.
I had problems with TWRP and CWM with my old mSD. (The flash process was terribly long.)
OpenRecovery was much faster but some flashes were still with issues.
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.