Related
This is my situation...
I recently rooted for my Wildfire using Unrevoked3, have no installed any custom roms whatsoever.
To install the new firmware (Update 1.25.405.1) i followed a guide which involved renaming it to update.zip and used clockmodrecovery to install update.zip from the SD card.
Update was successful however i lost the root (as expected)
I tried to rerun unrevoked 3 to reroot but all it does is reboot my device and it remains unrooted.
On the HBOOT recovery menu i now get a red triangle with an exclamation mark against a black background. i do power + volume up and it says android system recovery and in yellow 'E: Cant open/cache/recovery command'
How can i reroot my phone so i can use apps such as titanium backup once again? (and yes ive tried to install busybox and i get a failed error message)
I have looked around the forums and made lots of searches some of which address this question but i am yet to find a solution which works... Im sorry if this question is redundant as i am new to this sorta thing.
Thanks.
Did you follow this guide?
Update: What I did to succesfully install the update on a rooted phone
- unplug phone from USB, let it download update (it's about 13 Mb in size)
- phone will ask to reboot -> update will fail, you will be dumped in clockworkmod
- As always, do a Nandroid backup before doing anything that might possibly render your phone unusable.
- Select update from zip/sdcard (or similar), navigate to zip in downloads folder
- the update process will start
- reboot (this can be a longer boot than usual, took 10 minutes on my phone)
- phone will notify you that the update has succeeded! If you've upgraded from your stock ROM (like I did), the phone info screen should look similar to that in the attached image.
- (reflash needed for root)
It doesn't say to rename the file though.
I'm going to do this now (im guessing youre on TM too?)
thanks for the info, i'm just about to do the same thing, after trying [ROM][04/10] WildPuzzleROM v8.0.5; until i realised there are still problems, got scared and restroed nandroid backup Couldn't get marketplace to load?
when phone reboots after downloading the update, i guess its supposed to be installed by the recovery program, but i have clockworkmod, I tried apply sdcard:update; get error back with failed to open update.zip and sig veri failed.
Not sure what to do? Will try booting normally, checking sd theres a file called 'OTA_Buzz_TMO_UK_1.25.110.1_R-1.14.110.1_R_release31o90ome6fwgje76.zip' on the sd card under download folder. will try renaming to update.zip and placing in \sdcard root folder
otherwise i'm thinking rom manager to install, but mobilism is down it seems and can't get hold of it
EDIT: Just rename the update put it in the \sdroot. Boot into recovery and install update.zip. works fine, takes ages, very scarey process.
Will try going back to puzzle when i have more time! Lets hope 1.25 don't crash as frequently!
Yes, i did follow all those instructions and it still didnt work. However i have managed to reroot my wildfire haha so problem is resolved. It was a stupid problem, after i rooted the first time, i reinstalled htc sync to sync some stuff but forgot to uninstall. After uninstalling it again i was able to reroot.
Sorry guys... very silly mistake by me.
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.
Ok... I have also used Z4root. I got the update, it failed. I unrooted with Z4root. Re-downloaded the update, it failed. I tried to reinstall the kindle and blockbuster app. Re-downloaded the update, it failed. I reset to factory. Re-downloaded the update, it failed. Downloaded root checker, ran root checker, it said that I am not rooted. Re-downloaded the update, it failed.
This is the Detailed Results I got from the Advanced Root Checker:
Root Access is not properly configured or was not granted.
Superuser.apk - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your DROID2 device by Root Checker version 3.7 from joeykrim in the Android Market -
___________________________________________
Have I done something wrong??? I don`t understand why I can not get the update. Please help.
This process should un root and put you back on stock Froyo. This is a complete factory wipe, so if you're wanting to back anything up, do it before any of these following steps. Once complete, go to Settings > About Phone > Check for Updates and report back.
WARNING: Only run the first set of instructions, do not flash the Gingerbread leak, you can get the official after running RSDlite.
To get back to stock: http://www.mydroidworld.com/forums/...id-2-gingerbread-2-3-3-release-prerooted.html
1. Grab the SBF File
You must start the process with your phone running the official 2.3.20. If you have already upgraded to gingerbread grab this 2.3.20 sbf file .... Download
2. Grab RSDlite
You must use RSDLite to use the sbf file from step 1 .... RSDLite
3. Grab the Drivers Drivers ....Download now
4. Run RSDLite and sbf your phone back to 2.3.20
Didn't work
I was unable to get the OTA to work. I was rooted using OneClickRoot and unable to update like everyone else (FAILED). I tried to sideload from a post on another page, but that didn't work either (not even sure that was the correct file). So I followed the direction as mentioned above, SBFing to a stock 2.3.20, but only after I did a complete wipe of the phone. Now that I have SBFed I don't have any phone signal and cant get it to work with anything I have tried. I don't want to go crazy trying stuff and brick my phone. So at this point, how do I get my phone working again. Screw GB for now, I just need my phone to work. HELP!
It's pretty hard to brick a D2 unless you happen to flush it down the toilet. SBF again to 2.2, do NOT root. Go to the about phone menu and run the OTA update to GB. After that run the one click root for Droid 3.
working
I don't know why, but after re-installing (SBF) 2.3.20 the phone decided to stop working. I thought it could have been a bad SBF file, and it could have been. The step that seemed to work was wiping the phone after the install. Once I did this step, of course you have to set the phon up again, but it prompted me to "Activate" the phone. So I hit activate and the phone called Verzon and run a programming function. Once that completed the phone worked fine. I am currently downloading the OTA, so here's hoping!
I did actually get the sideload (update.zip) file to work before going back to 2.3.20 as mentioned above, but I still didn't have phone. At this point I was going to do a wipe but could not get the phone to enter recovery, I'm thinking there must be some other method that's different to get it there. If anyone know, that would be good info to have.
Still downloading.....
I believe if you dial *228 it will activate for you.
I am also unable to get the OTA GB update to work. It gets all the way to re-boot and about 1/3 of progress bar after accepting to install the 4.5.601.A955. Just like mentioned in one of these other posts. I have tried everything - uninstalling and reinstalling z4 root, deleting SU, Bootstrap recovery, root explorer etc. All of which were not done properly or in the right order. I have been working on this the last 2 days. Yesterday, I even called tech support at Verizon, they helped me do a factory reset, and when it failed again, offered to send me a new D2 because my phone is still under warranty and won't accept the update, so I took their offer.
But then I got nervous because my clockwork mod was still showing up on power up, so I finally figured out how to remove that. I have SBF'd at least a couple of times since I got clockwork removed and update still fails.
My memory is not to good, but I think I first rooted in late Dec 2010. It seems like the 2.3.2 OTA update came out in Jan or Feb 2011. I don't believe I had to unroot to get that update. My current System Version is 2.3.20 A955 - Android version 2.2, and that is what it goes to after doing the factory reset on the phone. The Verizon tech didn't act like it should have gone back to an earlier version.
I have only one other issue - a week ago the phone took a bath when I fell in the water. Dried it off quickly and the only thing wrong other than barely-noticeble water damage to the display, is that the power button now requires exactly 3 pushes every time to boot the display to the unlock screen.
Sorry for the long post. Here are my questions: I no longer have clockwork at power up, it boots like a normal out of the box D2, am I missing something? Will Verizon be able to tell that I had rooted my phone? Could the water and resulting power button issue be the cause of it not accepting the update? TIA
Im having a similar problem. I can get the ota update just fine, but it will install aboutt 1/3 of it and just stop and reboot. All i did was root. I unrooted and same thing happpens. Downloaded this thing like 6 times already and same thing each time. Although a long time ago i did uninstall nfs, blockbuster, and i think kindle but i cant remember...
Are you doing a full factory wipe back to 2.3.2 when you do this or are you just "wipe data/factory reset" in recovery? Because if you only do that in recovery you're just wiping data. There's another thread here with a .zip you can run in stock recovery, not clockwork. Rename to update.zip, put it on the main directory of SD, boot holding X and power, then press the volume buttons. Hit install update.zip.
On the D2 - I am doing Settings<Privacy<Factory Data Reset<Reset Phone< Confirm.
How do you get into stock recovery? Do I need to be rooted again?
I would imagine but I don't know. Boot up holding the X key and power, should bring you to a droid guy with a !. Hit the volume buttons, if you get a blue and red recovery menu, you're in. It's not going to ask you for superuser so it's worth a shot at least.
Thanks for your help idefiler6. I got into stock recovery, but when I did the update it also failed - some logwrapper error. I am now having difficulty getting back in to stock recovery.
I had deleted system/bin/hijack and renamed system/bin/logwrapper.zip to system/bin/logwrapper to remove or stop the clockwork mod from booting up, which did make clockwork go away using Root Explorer. I found a post here to do this droidxforums.com/forum/droid-x-help/22080-im-begging-help-please-help-3.html
Anyway, my new phone is supposed to get here Wed. So I guess I'll just take my chances of whether Verizon cares or figures out I had rooted my phone. Regardless, the power button failing to work properly, should qualify for warranty coverage.
Crossing my fingers for you.
im getting mine replaced under warranty due to it cannot install the update no matter, how many times we have wiped it with tech support.
I also was very lucky since I got my 2nd warranty phone right before the one year mark so it extened the phone i have now another 90 days.
Problems all around
I too am having the OTA update problem. Downloads fine and gets about 1/3 of the way before rebooting and giving me an update failed message.
Current Device info:
D2G
System Version: 2.4.330.A956
Android Version: 2.2
Unrooted using Z4Root
Current logwrapper from November 12, 2010. No hijack or recovery .bin files in place.
I have tried RSDlite 4.8 and 4.9 using two separate downloads of the 2.3.20.A955 SBF from the link provided in this thread. Motorola Drivers are up to date and no errors are showing up in my Device Manager on my W7 PC.
The error I get when flashing in RSD is;
critical error febe 0047
Any thoughts? I'd like to try Gingerbread but haven't had any luck no matter what I try.
When in Doubt Go Linux!
Here's how I fixed the problem. I'm not a big Windows guy and the issues I was having were frustrating me because I had to update drivers, download new versions, blah, blah, blah.
I found a solution that allowed me to use my Fedora OS and it took me 10 minutes, no hassles, no errors. The incredible thing is, it kept ALL of my data, apps and settings on the phone! I had to upgrade from 2.29 (the flash from below) to 2.30 OTA and then to Gingerbread OTA Awesome stuff.
Here are the steps provided by hwertz from modmymobile.
"Download sbf_flash (just goggle it)
Download DROID2WE_X6_2.4.29_FULL.sbf.zip" (google this too)
(You would download these with firefox, make sure Firefox saves in the directory "Download".)
Open a terminal (Applications->Terminal)
Plug in your phone via USB, turn it off. Flip open the keyboard and turn it on WHILE holding down the up arrow. You'll see this screen with blocky white text, like right away -- it doesn't even get to the Motorola logo."
-----
OK, so in the terminal, you will
type "cd Download"
(If you saved somewhere else, cd to there. For instance if you saved to "Desktop" you would "cd Desktop" instead.)
Type "gunzip sbf_flash.gz"
If this gives an error, it's ok, it means you already had "sbf_flash" instead of "sbf_flash.gz"
type in "chmod +x sbf_flash"
Type in "unzip DROID2WE_X6_2.4.29_FULL.sbf.zip"
Then type in "sudo ./sbf_flash DROID2WE_X6_2.4.29_FULL.sbf"
If you are running a "real" copy of Ubuntu this'll ask for your password. The LiveCD has no password so it won't.
That's it! It'll appear to do nothing for a few seconds while it loads the flash, then it'll start flashing your phone which takes 5 or 10 minutes.
Good luck!
Thank you hwertz and thank you Linux!
cbotd said:
I too am having the OTA update problem. Downloads fine and gets about 1/3 of the way before rebooting and giving me an update failed message.
Current Device info:
D2G
System Version: 2.4.330.A956
Android Version: 2.2
Unrooted using Z4Root
Current logwrapper from November 12, 2010. No hijack or recovery .bin files in place.
I have tried RSDlite 4.8 and 4.9 using two separate downloads of the 2.3.20.A955 SBF from the link provided in this thread. Motorola Drivers are up to date and no errors are showing up in my Device Manager on my W7 PC.
The error I get when flashing in RSD is;
critical error febe 0047
Any thoughts? I'd like to try Gingerbread but haven't had any luck no matter what I try.
Click to expand...
Click to collapse
I don't particularly know how much of a difference this is, but the D2G and the D2 are two different phones, everything I have posted is for the OG D2. Might want to check the threads in the D2G forum because the files you need to SBF must differ in some way. I could be wrong...
that would explain it
idefiler6 said:
I don't particularly know how much of a difference this is, but the D2G and the D2 are two different phones, everything I have posted is for the OG D2. Might want to check the threads in the D2G forum because the files you need to SBF must differ in some way. I could be wrong...
Click to expand...
Click to collapse
That makes sense. Either way, I'm happy as can be and in love with my phone all over again. GB is fast and smooth on my D2G and after gaining root access again last night all my SU apps are back in working order.
Droid 2 updated
I had to revert back to stock 2.3.20 using the RSDLite flashing method, I let it do its thing, then performed a factory reset.
Powered the phone on, activated it, then just downloaded the OTA update over wi-fi to make it faster, installed like a charm, then ran the rooting utility.
Phone is rooted, deBloated, and rockin steady already.
Gotta say, I love my D2 again.
A955 & A957 Gingerbread sbf
On September 15th an official Gingerbread sbf was released from Motorola for the Droid 2 (not the Global). Here are the exact file names in case anyone has access:
A955:
1FF-p2a_droid2_r2d2_cdma_droid2_r2d2-user-2.3.3-4.5.1_57_DR2-32-110726-release-keyssigned-Verizon-US.sbf.gz
A957 (R2D2):
1FF-p2a_droid2_cdma_droid2-user-2.3.3-4.5.1_57_DR2-31-110719-release-keyssigned-Verizon-US.sbf.gz
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!
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.