Related
I was excited that I received a message to update my firmware to 2.2 Froyo, but when I tried doing so I kept getting errors at the installation screen. It would download then go to the installation screen and give me an error.
I'm not sure if I bricked the phone without knowing or something, but I get the following error message when trying to upgrade:
E:Can't open /cache/recovery/command
I have no idea what that is/where it is. I checked my SD Card, but I didn't see anything like that there. I'm guessing I'm missing that folder/file, but I don't know where it would have went or if I can get it back.
I've tried to do the update both through my Bravo and downloading a ZIP file and trying to do it through the Recovery screen. I tried everything Motorola suggests on their website as well as searched Google a lot, but came up with nothing.
I should add that even when I click "applysdcard:update.zip" it gives me a few errors and aborts the installation.
I'm just wondering if there's any way to fix this so I can upgrade my firmware?
Thanks to anyone that can help.
GeNiO426 said:
I was excited that I received a message to update my firmware to 2.2 Froyo, but when I tried doing so I kept getting errors at the installation screen. It would download then go to the installation screen and give me an error.
I'm not sure if I bricked the phone without knowing or something, but I get the following error message when trying to upgrade:
E:Can't open /cache/recovery/command
I have no idea what that is/where it is. I checked my SD Card, but I didn't see anything like that there. I'm guessing I'm missing that folder/file, but I don't know where it would have went or if I can get it back.
I've tried to do the update both through my Bravo and downloading a ZIP file and trying to do it through the Recovery screen. I tried everything Motorola suggests on their website as well as searched Google a lot, but came up with nothing.
I should add that even when I click "applysdcard:update.zip" it gives me a few errors and aborts the installation.
I'm just wondering if there's any way to fix this so I can upgrade my firmware?
Thanks to anyone that can help.
Click to expand...
Click to collapse
Have you done any sort of modding using SQLite Editor or Root Explorer to your phone?
i have the same error, but i do have modified the bravo with sqlite editor en root explorer. Does somedoby has the original build.prop please? i cant remember what i have changed in mine so i can not update
gosunta said:
i have the same error, but i do have modified the bravo with sqlite editor en root explorer. Does somedoby has the original build.prop please? i cant remember what i have changed in mine so i can not update
Click to expand...
Click to collapse
Just emailed you the original build.prop you need in order to get the update to work. Let me know how it goes.
Finally working , i replace the file and i did upgrade my phone. Thanks a lot for all the info
I get a the update downloaded but when it restarts I am getting a white triangle with a yellow explination point.
If I pop the battery I can get past the error and back to the phone
I have it rooted with one click
Any info?
seraphielx said:
I get a the update downloaded but when it restarts I am getting a white triangle with a yellow explination point.
If I pop the battery I can get past the error and back to the phone
I have it rooted with one click
Any info?
Click to expand...
Click to collapse
touch the screen at right-bottom and you will see a list. Select update.zip and touch ok
hippyman said:
Have you done any sort of modding using SQLite Editor or Root Explorer to your phone?
Click to expand...
Click to collapse
I'm sure there is a solution, but just forget it and install 2.2 SBF.
hippyman said:
Have you done any sort of modding using SQLite Editor or Root Explorer to your phone?
Click to expand...
Click to collapse
Yes, I used Root Explorer. I'm guessing by MCFarmfresh's post that there issome sort of original build for the phone? I've looked everywhere for hours all night last night before resorting to asking somewhere, but I couldn't find anything and the "solutions" I've seen all did not work. I kept getting the same errors.
Thank you for replying. If you can help, it'll be very much appreciated.
I have a rooted Bravo and I deleted some of the bloatware, and I received the Froyo update and everytime I download and the system resets I get an error and the update stops. Selecting from memory card doesnt work for me, and I dont have a backup of the original settings to re-install (which I'm not sure how to do that either). If anyone has any suggestions I'm open.
its checking for att apps
if you renamed them name them back to apk
I didn't rename them, I deleted them off my phone.
Sent from my MB520 using XDA App
I don't know much about these things but I would think that would be a bad thing to do...
I was able to get the update to install to my phone but now it is running slow
Any more info on how to fix this issue?
OK, so I tried everything that's suggested pretty much everywhere and I'm still unable to update. I'm not sure if I'm doing something wrong or what, but I've tried resetting the phone via the phone/recovery screen, tried updating via the phone, and I also tried replacing the original build, but nothing worked so far.
I have no idea what else I can do, but any help would be appreciated.
GeNiO426 said:
OK, so I tried everything that's suggested pretty much everywhere and I'm still unable to update. I'm not sure if I'm doing something wrong or what, but I've tried resetting the phone via the phone/recovery screen, tried updating via the phone, and I also tried replacing the original build, but nothing worked so far.
I have no idea what else I can do, but any help would be appreciated.
Click to expand...
Click to collapse
If nothing else works, you can always sbf. It sounds scarier than it really is, actually it is pretty easy. Just make sure you follow the directions. I've done several sbf's and they have all turned out perfectly.
jorgonv said:
If nothing else works, you can always sbf. It sounds scarier than it really is, actually it is pretty easy. Just make sure you follow the directions. I've done several sbf's and they have all turned out perfectly.
Click to expand...
Click to collapse
Thanks. I'm not sure what it was, but I switched to my Windows XP desktop (from my Windows 7 Home 64-bit laptop) and the SBF Flash worked perfectly, thanks bandroid, yourself, and others. I really appreciate all of the help given. 2.2 looks and feels a lot better than 2.1 so I'm really happy about that.
MCFarmfresh said:
Just emailed you the original build.prop you need in order to get the update to work. Let me know how it goes.
Click to expand...
Click to collapse
please send me one too and where do i put it.????
mismisgh said:
please send me one too and where do i put it.????
Click to expand...
Click to collapse
If you will give me your email I can get it to you. For the life of me I cannot figure out hhow to attach files through pm using my phone lol. You can also use the .sbf method to upgrade but I'll definitely get the files to you if you send me your email.
SBF'in it...
Okay....so one of your gentleman above (I'm new to the forum ish) stated that he had deleted some apps off of his OS. I did the same thing with AT&T Hotspot Locator (unfortunately, AT&T was quick on merging this standalone app into MyAT&T so I couldn't get the atthotspotlocator.apk back). I fixed this using the SBF file.
I won't give you the step by step but I can tell you RSD Lite is a free program from Motorola. It's basically the program they use to flash boot SW onto an otherwise dead device.
Don't be intimidated by it because it really is rather easy to facilitate. Just do like I did and YouTube how to load an SBF into a motorola device. You can pause and replay as you go along to assure no errors. Takes like 15 minutes once you've got all the necessary files downloaded.
Well, that lasted long...
Everything was going fairly well until this morning when I clicked on the phone button (default launcher) and tried to go into the dialer, then it just closed every time I tried doing so.
To try to fix this I rebooted my phone, nothing; restored, nothing; factory reset, nothing; re-installed 2.2.1 FroYo via flashing the SBF with RSD Lite and 'apply:sdcard:update.zip' through Android's Recovery Screen, nothing.
When I tried doing the last 2, however, I received these errors (the first one I had with the first problem and the other 2 are new):
E:Can't mount CACHE: recovery/command
E:Can't mount CACHE: recovery/caller
E:Can't mount CACHE: recovery/log
Now, with the "caller" error, I did NOT touch anything having to do with the dialer and whatnot. That I know.
The last time I had problems with my laptop so I tried it on my desktop and it worked, but now I tried the desktop and it still isn't working properly. Some of the features that I had with the update are now gone such as the "third party apps" option and the sliding "lock screen" is now permanently present.
Any help with this is appreciated.
I just recently performed an "Over the air" update on my Motorola Atrix in hopes of upgrading to 2.3.
The 200mb file downloaded so I selected "install".
I walked away and then came back to the following error screen:
www [DOT] hardreset.eu/images/nexus_one_android_hard_reset_3 [DOT] jpg
Upon resetting the handset it appears that not only did I experience an error during the update, but now I also will have to re-download the entire file.
Can anyone please advise if there is anyway to manually install 2.3? Surely it's still on the phone somewhere.
**Update:**
I tried downloading the file again but this time backed it up just incase.
It failed a second time so I tried renaming it and doing a manual update.
I received the following errors:
Verifying current system...
assert failed: apply_patch_check("/system/app/MagicSmokeWallpapers.apk", "9870b02dba63f6f0047e4d104329cf4c1d0a48a5", "9870b02dba63f6f0047e4d104329cf4c1d0a48a5", "94389fda652df9e0eaaddf25bbbac0b0dececa1c")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted...
Click to expand...
Click to collapse
I hope someone can shed some light on this!
humanix said:
**Update:**
I tried downloading the file again but this time backed it up just incase.
It failed a second time so I tried renaming it and doing a manual update.
I received the following errors:
I hope someone can shed some light on this!
Click to expand...
Click to collapse
Is the the Telstra over the air update? (as I just did mine yesterday)
It basically means that the update is doing a check to make sure certain files are still in place - in other words somehow or someone has deleted that .apk (is your phone rooted?!) and since the update cannot find it it aborts the process.
I ended up just re-flashing with RSDLite back to stock as I had exactly the same drama (I had removed helpcentre.apk), downloaded the update yet again (third time lucky...) and it worked perfectly.
I also did a full factory reset as well as formatted my internal SD card prior to updating.
Hope this helps
the key question is, have you done any modding to your phone? webtop hack, rooting, anything that would change system files?
geekygrl said:
Is the the Telstra over the air update? (as I just did mine yesterday)
It basically means that the update is doing a check to make sure certain files are still in place - in other words somehow or someone has deleted that .apk (is your phone rooted?!) and since the update cannot find it it aborts the process.
I ended up just re-flashing with RSDLite back to stock as I had exactly the same drama (I had removed helpcentre.apk), downloaded the update yet again (third time lucky...) and it worked perfectly.
I also did a full factory reset as well as formatted my internal SD card prior to updating.
Hope this helps
Click to expand...
Click to collapse
Yes, it's a rooted Telstra Atrix.
I did a re-flash using RSDlite and it did the trick. Thanks!
Twice, actually. After the second download (courtesy of the now-warned-against 'Framework Services forcing' trick) I got the identical error message via CWM Recovery:
Code:
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
Any suggestions about the next move, please?
You can't install the update from Google the natural way if you have a custom recovery. Just download the update, boot into recovery, and run the zip.
Visa Declined said:
You can't install the update from Google the natural way if you have a custom recovery. Just download the update, boot into recovery, and run the zip.
Click to expand...
Click to collapse
Thanks, I know that. I did not use CWMR for updating - The update ran - 'Installed' - conventionally both times... It made the trip into Recovery on its own where the resident tool is CWMR. Is this a known issue?
I do have a copy of the update elsewhere than in /cache in case I need to copy it back there for some possible next move.
It would be great to hear of a way to get this update to install successfully.
pofadda said:
Thanks, I know that. I did not use CWMR for updating - The update ran - 'Installed' - conventionally both times... It made the trip into Recovery on its own where the resident tool is CWMR. Is this a known issue?
I do have a copy of the update elsewhere than in /cache in case I need to copy it back there for some possible next move.
It would be great to hear of a way to get this update to install successfully.
Click to expand...
Click to collapse
This seems to be a known issue. When the update installs, it boots into recovery to install the update. If you're using a custom recovery instead of the default one, the install will fail.
The same thing happened to me. I simply copied the update .zip from /cache into a folder on /sdcard, rebooted into CWMR, backed up and installed the .zip from there. Easy peasy.
ahoyland said:
I simply copied the update .zip from /cache into a folder on /sdcard, rebooted into CWMR, backed up and installed the .zip from there. Easy peasy.
Click to expand...
Click to collapse
That's what I was trying to get the op to do in the second post of this thread, I'm not really sure if it's working for him or not
Visa Declined said:
That's what I was trying to get the op to do in the second post of this thread, I'm not really sure if it's working for him or not
Click to expand...
Click to collapse
Thank you for that, VisaDeclined & Ahoyland! I quite misread the intent of your message. 'Normal' reboot is problematic, I read, so I have downloaded 'Quick Boot (reboot)' from here (Play Store seemed to be having difficulty - maybe because I had done the 'Framework' hack earlier?) and the little thing is now done and saying 'Build No. JZ054K' . I am now a much happier bunny!
Thanks is on its way, folks.
Happiness can be so short-lived... (but good things come to those who try)
Life took a turn for the worse when I noticed that updates and downloads from Play were not getting through. The errors are:
DF-BPA-13 'trying to install',
RPC-AEC-0 'Error while retrieving information on server' &
923 (dunno)
However - THE GOOD NEWS! - I tried these two actions and all is well now:
(ex Google, the poster said)
First Make sure you're signed into Talk.
Go to setting>apps>all>Google play store
Then clear data and uninstall updates.
Then go to Google account manager, clear data and force stop.
Power off and leave it off for a minute or two, re-boot and it should work, if not go to talk and make sure you're still signed in.
Tr
y updating or downloading one thing at a time to see if it works.
Still 'RPC etc.', so
I went Settings>Accounts>Google>(account name)>(Menu)>Remove account.
Ran PlayStore,
was prompted for and re-entered my (existing) account.
Thereafter all was as before and updates were working again! :laugh::laugh:
HTH
Yesterday I rebooted my Nexus 7 after it froze while transferring some files onto the NAND, and the OS failed to load. I went into recovery and attempted to reflash the ROM I've been using for a few months, only to have it fail. I tried to revert to stock with the Nexus Toolkit, which failed, so I attempted a fastboot flash bootloader bootloader-group 4.23.img as my first step toward getting it back to stock. I tried with the copy I had, and got "InvalidState", so I google'd and discovered there were two versions of the 4.23 bootloader. Trying with the one that everyone was reporting to work, I got "Unknown Error Code", followed by "BadParameter" and then "Invalid argument". I then "fastboot reboot-bootloader", to try again after a reboot as I was getting nowhere, only to get a black screen. In Device Manager, my tablet shows up as "Unknown USB Device (Device Descriptor Request Failed)".
Is there anything I can do to revive it? I'm up for breaking it open and replacing parts.
Bump
Up!
Bump
N140945296
Eckyx said:
Yesterday I rebooted my Nexus 7 after it froze while transferring some files onto the NAND, and the OS failed to load. I went into recovery and attempted to reflash the ROM I've been using for a few months, only to have it fail. I tried to revert to stock with the Nexus Toolkit, which failed, so I attempted a fastboot flash bootloader bootloader-group 4.23.img as my first step toward getting it back to stock. I tried with the copy I had, and got "InvalidState", so I google'd and discovered there were two versions of the 4.23 bootloader. Trying with the one that everyone was reporting to work, I got "Unknown Error Code", followed by "BadParameter" and then "Invalid argument". I then "fastboot reboot-bootloader", to try again after a reboot as I was getting nowhere, only to get a black screen. In Device Manager, my tablet shows up as "Unknown USB Device (Device Descriptor Request Failed)".
Is there anything I can do to revive it? I'm up for breaking it open and replacing parts.
Click to expand...
Click to collapse
Hello,
It sounds like your Nexus 7 may be hard bricked. If your Bootloader is no longer showing up you may need to send in your device to be repaired. At this time I do not know of a solution to the issue you are experiencing except to have it repaired. If you would like to proceed email me at [email protected]. Please place case number N140945296 in the subject line for reference.
[email protected] said:
Hello,
It sounds like your Nexus 7 may be hard bricked. If your Bootloader is no longer showing up you may need to send in your device to be repaired. At this time I do not know of a solution to the issue you are experiencing except to have it repaired. If you would like to proceed email me at [email protected]. Please place case number N140945296 in the subject line for reference.
Click to expand...
Click to collapse
Sent you an email about a week ago, hoping to hear back soon!
Eckyx said:
Sent you an email about a week ago, hoping to hear back soon!
Click to expand...
Click to collapse
Got any solution my N7 shows exact the same symptom..
//Mathias
Fastboot will help you get everything back. Don't have the steps but did it myself with my Nexus 10. Google the info like I did.
Sent from my Nexus 10 using XDA Free mobile app
striker59 said:
Fastboot will help you get everything back. Don't have the steps but did it myself with my Nexus 10. Google the info like I did.
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
Striker there seems to be a case where the flash gets corrupt and gets write protected... Which seems to have happend to our nexus 7..
To bad ASUS havent released a APX tool to fix this.
/M
Hello,
I'm looking for help. I wish I could ask on the development page, but I don't have access to do so because of my low post count.
I've had a problem with my HTC Bolt screen. I made a video of the problem and put it on youtube:
https://www.youtube.com/watch?v=1eR5NFDcnvU
I thought it may be a problem with the firmware/stock rom that is loaded with bloatware, so I decided to tinker with rooting, etc...
First thing I did was gain root using this method:
https://forum.xda-developers.com/bolt/how-to/root-supersu-v2-78-sr5-s-off-sunshine-t3513048
Then I downloaded and ran Sunshing to get S-off.
I then tried to install a new Rom, but it wouldn't install, giving the " E:footer is wrong .. E: signature failed" on the android recover.
The phone on my screen continued to glitch, so I tried to go back to stock using the RUU as described here:
https://forum.xda-developers.com/bo...t-htc-bolt-1-17-651-11-updated-t3502778/page4
but the process hung when trying to install a new rom using the RUU . I assume this happens because of the same "E:footer is wrong .. E: signature failed" problem when I try to flash a ROM.
Please help. I can't boot up into the system and am new to this. Also, if you can point my problem to the developers, that would be great.
recovery screen shows this:
*** Software status: Official ***
*** Unlocked ***
*** S-Off ***
This looks good to me to give me access to flashing, but the error keeps getting in the way.
Thanks,
Marc
what recovery are you using?
when you reboot to download mode and use fastboot, type fastboot devices. Does the serial number and fastboot show up?
what method are you using to RUU?
I tried all of the recoveries I could find, but I guess most were close to stock . I still can't figure out why I couldn't install rom from SD card.
UPDATE: I was able to reflash with RUU exe from my computer. Problem ended up being available disk space on C: drive. The RUU .exe needed about 7 gb free to run all the way through. First try I only had 2gb, which wasn't enough and caused. Exe to hang.
I just updated to latest software, 22 and screen problem still happening. Someone else commented that they have had the same problem on two different Bolts. Guess there are some manufacturing or software issues with the bolt, so be ready for screen issues. Hopefully it is software or firmware rather than hardware.
After running RUU, I assume I'm stock, but how do I lock and get s-on again?
marcram said:
I tried all of the recoveries I could find, but I guess most were close to stock . I still can't figure out why I couldn't install rom from SD card.
UPDATE: I was able to reflash with RUU exe from my computer. Problem ended up being available disk space on C: drive. The RUU .exe needed about 7 gb free to run all the way through. First try I only had 2gb, which wasn't enough and caused. Exe to hang.
I just updated to latest software, 22 and screen problem still happening. Someone else commented that they have had the same problem on two different Bolts. Guess there are some manufacturing or software issues with the bolt, so be ready for screen issues. Hopefully it is software or firmware rather than hardware.
After running RUU, I assume I'm stock, but how do I lock and get s-on again?
Click to expand...
Click to collapse
Is the screen always black, or intermitting?
in download mode
fastboot oem lock( it will say relocked and not Locked though)
OK, thanks. Maybe some chmod can solve it. Sprint is charging since it is more than 20 days old. Going to HTC instead since under their warranty.
The problem is intermittent, but is getting worse with each hour. Others are having the same issue.
I've been seeing the same issue with the display not waking since the .22 update...it's very intermittent on mine though, maybe 10% of the time...I haven't been able to narrow it down.
did u flash twrp recovery before flashing a ROM?
Thought I replied to this, but guess not. I didn't flash twrp. I thought that was only available through app, where one touch operations could be performed. I previously couldn't boot into system.
marcram said:
Thought I replied to this, but guess not. I didn't flash twrp. I thought that was only available through app, where one touch operations could be performed. I previously couldn't boot into system.
Click to expand...
Click to collapse
no, twrp is best installed by flashing it in download mode, u cannot flash a ROM via stock recovery, only custom recovery(twrp)...https://forum.xda-developers.com/devdb/project/?id=18340#downloads
Thanks, twrp did the trick. But with 3 different roms, I'm still having screen blackout issues. Going to need help getting back to locked and s on after RUU. Guess I'll start a new thread for that.