Subject says it all. No luck with Google. Don't want to update until I know what's being updated.
Sent from my HTC first using xda app-developers app
not sure but...
jonslice said:
Subject says it all. No luck with Google. Don't want to update until I know what's being updated.
Sent from my HTC first using xda app-developers app
Click to expand...
Click to collapse
I installed the update last night. I honestly don't know what all the changes are, but I'm pretty sure it is a bugfix release. Still android 4.1.2. The only thing that I have noticed is that after the update my led will actually flash green for a text message or email. Before the update, my led only worked for charging, so I would have no idea whether I had email or messages without turning my screen on.
I have not noticed any other changes. No noticable speedups or slowdowns. Haven't discovered any issues. None of my apps have ever forced closed on this phone, and that has not changed after the update.
So...not a bad upgrade, although it might be pointless if you don't have any issues.
19.8MB update. Can't be too much going on in there, but I'd also think it's more than a few lines of code being updated...
Ooh, fun. Looks like I can't install the OTA with CWM or TWRP. Jonslice, are you rooted?
EDIT:
Weird. Now my phone says the software is up to date. What's the Build info under About Phone for you guys? Wondering if it did actually update even though it said it failed...
The OTA zip is on my dropbox in case anyone is curious to look at it. [1] Looks to me like it's updating a handful of system files, as well as the boot and recovery images. With clockworkmod installed, I was prompted to confirm installing the update because its signature wasn't verified, but I haven't yet attempted to let it install it. This should definitely give us an "official" image for the boot and recovery partitions though, which never hurts.
1: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/OTAPkg.zip
nuclear_eclipse said:
The OTA zip is on my dropbox in case anyone is curious to look at it. [1] Looks to me like it's updating a handful of system files, as well as the boot and recovery images. With clockworkmod installed, I was prompted to confirm installing the update because its signature wasn't verified, but I haven't yet attempted to let it install it. This should definitely give us an "official" image for the boot and recovery partitions though, which never hurts.
1: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/OTAPkg.zip
Click to expand...
Click to collapse
It'll fail if you try to install it. I'm thinking it needs the official bootloader to work. Someone will need to make this flashable. I was trying to extract it from my phone, but you beat me to it. Thanks!
chrisliphart said:
It'll fail if you try to install it. I'm thinking it needs the official bootloader to work. Someone will need to make this flashable. I was trying to extract it from my phone, but you beat me to it. Thanks!
Click to expand...
Click to collapse
I pulled this recovery.img from the firmware.zip that's included inside OTAPkg.zip: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.img
I would assume that a simple `fastboot flash recovery recovery.img` should suffice.
nuclear_eclipse said:
I pulled this recovery.img from the firmware.zip that's included inside OTAPkg.zip: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.img
I would assume that a simple `fastboot flash recovery recovery.img` should suffice.
Click to expand...
Click to collapse
Huh. I couldn't get the Firmware.zip to open on my system. Thanks for doing that. Now I'm gonna go be an idiot and possibly brick my device by pushing this recovery to my phone to try and install the OTA. lol
I did also manage to snag the recovery.log from clockwork recovery when the update first tried to run, just in case that actually proves useful to anyone... https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.log
nuclear_eclipse said:
I did also manage to snag the recovery.log from clockwork recovery when the update first tried to run, just in case that actually proves useful to anyone... https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.log
Click to expand...
Click to collapse
Thanks. I posted both the update and your log to the development forum to see if someone with more knowledge can do anything with them.
For the record, pushing that recovery doesn't work. Well, pushing it works, but you can't get into it on the phone. I repushed TWRP to my phone in the interim.
chrisliphart said:
19.8MB update. Can't be too much going on in there, but I'd also think it's more than a few lines of code being updated...
Ooh, fun. Looks like I can't install the OTA with CWM or TWRP. Jonslice, are you rooted?
EDIT:
Weird. Now my phone says the software is up to date. What's the Build info under About Phone for you guys? Wondering if it did actually update even though it said it failed...
Click to expand...
Click to collapse
I got failed update with CWM also. I'll try to post a build info screen shot once I'm on my desktop when my work week is over. Manual check for update says I still need update.
Note: unlocked boot loader, CWM and rooted.
Sent from my HTC first using xda app-developers app
As long as this doesn't remove the ability to disable Facebook Home, I'll probably update it. Can anyone confirm that this is the case?
Daman09 said:
As long as this doesn't remove the ability to disable Facebook Home, I'll probably update it. Can anyone confirm that this is the case?
Click to expand...
Click to collapse
That's a feature of Home, not the firmware. So yeah, you can still disable it. I don't ever see even Facebook changing that.
Related
so i used odin to revert completely back to stock jf6 firmware, everytime i try and update it goes thru the process of updating and stops during reboot at 50 percent and says download failed, can anyone help me troubleshoot this issue. im all ears, thanks in advance...
this seems to be happening to all of us who had been rooted at one point or another
yea this will be my fourth try. this time im going to do a factory reset and sign into the market and see what happens. i wonder if this has something to do with the jf6 zip that all of us are flashing back to....
interesting. ive been seeing a fail message as well but 3-button recovery is working now.
beazie0885 said:
yea this will be my fourth try. this time im going to do a factory reset and sign into the market and see what happens. i wonder if this has something to do with the jf6 zip that all of us are flashing back to....
Click to expand...
Click to collapse
please update us after the factory reset
no go on factory reset hopefully someone will post the zip after they get it to work.
[edit] im on the phone with dumbass at&t customer service right now working my way up to level 3 tech support.
[EDIT again..] he found some errors on their side of things that he just corrected and pushed a new update directly to my phone via OTA.
ouch, live long and prosper and may the force be with you
life2monkeys said:
ouch, live long and prosper and may the force be with you
Click to expand...
Click to collapse
lol, just rebooted and.... fucx... no good still but hes gonna give me a call back in about a half hour.. will rpost then
still a no go, he said to try again tonight when he sends me another update. then again tomorrow, looks like till then, SOL
Can you use File Explorer or USB debug to see if there's an update.zip in /sdcard on your device?
same here. i've tried everything.
Also I should mention that you can cheat the 24 hour system by changing the clock manually to a day later... lol
brunson said:
Can you use File Explorer or USB debug to see if there's an update.zip in /sdcard on your device?
Click to expand...
Click to collapse
i checked and nothing...
having the same problem
Guys.. chill out - the Samsung official announcement said
"An update to improve the Samsung Captivate's GPS performance is now available. Captivate customers will receive a notification on their device that an update is available and will simply need to download the file to update their phone. The updates will be pushed to customers' devices over the next few weeks."
You do not need to check for the update yourself.
not the point. the point is, it is possible to get it now, and it's not working for us rooters :/
Eschmacher said:
not the point. the point is, it is possible to get it now, and it's not working for us rooters :/
Click to expand...
Click to collapse
Well said... I'm not even worried about the jh7 update, we've had that for a while now, I'm more worried about my phone being ABLE to receive updates than anything else.
Sent from my SAMSUNG-SGH-I897 using XDA App
well... i backed up my contacts with kies... i'm going to completely clear everything and go back to stock...
after that i'll re-root. but i'll be sure to use the adb shell to backup the stock kernel...
Its working now for me, I also got the updated failed message and have rebooted my phones several times through the day and just verified on google maps twice that it zoomed in accurately
My phone is rooted and have every setting in ryans lag fix set...oh yeah I got the beast unleashed installed.
Sent from my SAMSUNG-SGH-I897
TheRealXenu said:
Stock rom with update is ready here http://www.megaupload.com/?d=RZXMUXY4
Click to expand...
Click to collapse
From the General section. Good luck all.
cappysw10 said:
From the General section. Good luck all.
Click to expand...
Click to collapse
call me stupid, but how would I go about installing this?
All I would like to do is get my (not unlocked, but un-rooted) back to a stock recovery (I think?) and a stock OS. I want to be able to do updates OTA as they arrive on my phone, and the only reason I rooted in the first place was to get Gingerbread from CM7 and they didn't work. It got stuck in a endless boot loop and once I finally got a nightly working, it wasn't even worth it to me anymore.
I have used this thread: http://forum.xda-developers.com/showthread.php?t=614850
and done hours and days of research to try and solve my problem and get me to where I would like to be. I'd like to think I am not a noob to Android but clearly I am and I can't achieve 100% of my goal.
Where I am currently: Stock image, not sure of recovery, unrooted, bootloader unlocked.
Where I would like to be: Stock everything (I know I cannot relock the bootloader) just like when I bought it, so I can patiently wait for Gingerbread to push OTA whenever Google solves the issues.
Thank you and I apologize.
That guide has pretty much all the information you need. Flashing the stock HTC images and stock recovery will enable you to get OTA updates.
Read my signature, find "Unroot/restore" guide, look for the part for unlocked bootloaders.
Clearly that did not work for me or I would not have posted my concern.
@Jack_R1 I will attempt this again, thanks.
rynstphn said:
Clearly that did not work for me or I would not have posted my concern.
@Jack_R1 I will attempt this again, thanks.
Click to expand...
Click to collapse
You didn't explain where you got stuck, what you attempted, what went wrong and couldn't even state your recovery image. The guide you linked to is there for a reason, it works, however onlyif you follow it correctly without jumping in with 2 feet. If in future you require more precise help perhaps you should give precise information.
Perhaps the OP has encountered some of the issues i've posted about HERE?
Don't mean to kind of hi-jack this thread...
Don't mean to kind of hi-jack this thread but on the related topic of rooting the N1...is there some way to root it and still receive the OTA update for gingerbread(whenever it will come out)?
I did look through the threads and found nothing related unless it was further discussed on page x of 25, for example.
Also, are all wallpapers 960/980 by 800 for the N1 and other android phones? Is this so that when you scroll through screens you will still be able to see the image? That was the only possible answer I could think of.
Thanks in advance.
CTR01 said:
Don't mean to kind of hi-jack this thread but on the related topic of rooting the N1...is there some way to root it and still receive the OTA update for gingerbread(whenever it will come out)?
I did look through the threads and found nothing related unless it was further discussed on page x of 25, for example.
Also, are all wallpapers 960/980 by 800 for the N1 and other android phones? Is this so that when you scroll through screens you will still be able to see the image? That was the only possible answer I could think of.
Thanks in advance.
Click to expand...
Click to collapse
Yes and yes.
You can root using SuperOneClick and still recieve OTA updates. You only lose that ability once you've installed a custom recovery.
Thanks!
DirkGently1 said:
Yes and yes.
You can root using SuperOneClick and still recieve OTA updates. You only lose that ability once you've installed a custom recovery.
Click to expand...
Click to collapse
Awesome! Thanks for the reply and details.
DirkGently1 said:
Yes and yes.
You can root using SuperOneClick and still recieve OTA updates. You only lose that ability once you've installed a custom recovery.
Click to expand...
Click to collapse
Having a custom recovery has NOTHING to do with your ROM's ability to receive OTA updates... it has to do with you ROM, not your recovery.
And, as mentioned, rooting or unlocking has no impact on you being able to receive OTA updates.
Sent from my Nexus One using XDA App
efrant said:
Having a custom recovery has NOTHING to do with your ROM's ability to receive OTA updates... it has to do with you ROM, not your recovery.
And, as mentioned, rooting or unlocking has no impact on you being able to receive OTA updates.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Sorry, but that is wrong.
http://forum.xda-developers.com/showpost.php?p=10871795&postcount=1
Read that post. There is a stock recovery supplied in case anybody wishes to recieve future OTA updates.
DirkGently1 said:
Sorry, but that is wrong.
http://forum.xda-developers.com/showpost.php?p=10871795&postcount=1
Read that post. There is a stock recovery supplied in case anybody wishes to recieve future OTA updates.
Click to expand...
Click to collapse
Uh, sorry, but NO. What he says in that post is incorrect.
I have been using a custom recovery since I first got my Nexus One, and I have received EVERY OTA update.
EDIT: But hey, don't take my word for it. Try it yourself.
efrant, for clarification, do the OTAs auto install, or do you have to manually flash them?
Sent from my Nexus One using XDA App
danger-rat said:
efrant, for clarification, do the OTAs auto install, or do you have to manually flash them?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
So, in my setup (which is a rooted-but-otherwise-stock ROM and Amon_RA's 1.9.0 recovery), I receive OTA updates, and they auto-install with no problem (as Amon_RA's 1.9 recovery does not verify signatures). Note, however, that every OTA update also does two things: 1) it removes the permissions on the su binary (which obviously disables root access), and 2) it copies two files (/system/recovery-from-boot.p and /system/etc/install-recovery.sh) back onto the system partition, which will flash the stock recovery back to your devices as soon as you reboot. You will need to root first (either manually or by flashing ChainsDD su update before you reboot, or use SOC), then delete the two files, then reflash the custom recovery you want.
This is true only for Amon_Ra's 1.9 and later recoveries that either don't verify signatures at all, or allow turning verification off.
Jack_R1 said:
This is true only for Amon_Ra's 1.9 and later recoveries that either don't verify signatures at all, or allow turning verification off.
Click to expand...
Click to collapse
Yes, you are correct for the installation part of the update. However, you can have any recovery whatsoever, and it will not impact you receiving OTA update notifications.
efrant said:
Yes, you are correct for the installation part of the update. However, you can have any recovery whatsoever, and it will not impact you receiving OTA update notifications.
Click to expand...
Click to collapse
Yep, that's correct.
Cool
thanks for all the other responses to my question! I will look into this further when i have more time
Of course you can still 'receive' OTA but what's the point if you can't install them? I'm pretty sure that everybody understands the distinction!
DirkGently1 said:
Of course you can still 'receive' OTA but what's the point if you can't install them? I'm pretty sure that everybody understands the distinction!
Click to expand...
Click to collapse
If you read post 14, you will see that you CAN install them with a custom recovery...
Here is the update that the test phones(4.0.19915 to 4.1.26) received right before the launch of the retail unit. You might think this is useless, but it paints a very clear picture of how Moto updates work on the Atrix.
For each file that is being updated it hash checks and then applies the binary patch. This means changing the file permissions, mounting the system as rw will not cause this to fail as someone else had mentioned before. When it comes time to update, we can extract it and run the patch against the retail dump to create an updated dump.
This also tells us we can use recovery to flash update.zip files, we just need to figure it out. This would be very helpful when creating an updated dump.
This file is downloaded to /cache/tmp. A simple script was used to capture it before it was deleted.
Download the file here:
http://www.ponack.net/designgears/atrix/update.7z
This is very good news.
does this also mean that an OTA can be packaged as a zip and "flashed" to a phone?
verrry nice
Thanks DG!
and please stay
we will miss you
GSeeker said:
Thanks DG!
and please stay
we will miss you
Click to expand...
Click to collapse
I will still be around doing things here and there
Anyway to unbrick my atrix with this?
hassanjanjua2002 said:
Anyway to unbrick my atrix with this?
Click to expand...
Click to collapse
What kind of brick do you have on your hands?
Also, thanks dg
Very informative!
Hmmm, tried to flash it as an update.zip through recovery and signature check failed. I'm guessing since this was prior to release it was test signed? Had to try since I need something via RSD, Recovery, or Fastboot to get my phone up and running again.
navalynt said:
Hmmm, tried to flash it as an update.zip through recovery and signature check failed. I'm guessing since this was prior to release it was test signed? Had to try since I need something via RSD, Recovery, or Fastboot to get my phone up and running again.
Click to expand...
Click to collapse
If you look in there you can see that it updates recovery, I am assuming it signs it and requires a signature now.
might want to try one with a test signature and see if that works.
Im on my tablet no computer. . . Is there a boot.bin in therr if so id like to run it through my keyfind program see if i can find the same aes key in it
t0dbld said:
Im on my tablet no computer. . . Is there a boot.bin in therr if so id like to run it through my keyfind program see if i can find the same aes key in it
Click to expand...
Click to collapse
baseband_ota.img and mbm_combo.bin
I want Update.zip signed for this orginal files from /system/lib
libskia.so
libskiagl.so
libwebcore.so
Because I changed these files to make the device read Arabic, but the device stops working and Restart
Now I want to push this and return the original files
designgears said:
baseband_ota.img and mbm_combo.bin
Click to expand...
Click to collapse
Lol damnit lying in bed so tired , but so tempted by what ever mbm_combo.bin is but linux machine and keyfind back at my store only cr-48 and mac air here not enough processing power :-( anyhow thanks so much for post i cant wait to check it out. On side note you sure you going to leave dg ? I mean ever sense we got dock hack figured out im more leaning twoards keeping it . . Also because this is first cheep device i have bought $150 small invesment payed $500 or more for most my devices and cause i think we will get bootloader now and something seems weird abiut that dev dump of gb being vanilla. Maybe an option they will offer to quiet the devs anyhow at least keep posting us the leaks if you wont stay
designgears said:
If you look in there you can see that it updates recovery, I am assuming it signs it and requires a signature now.
might want to try one with a test signature and see if that works.
Same situation here, as you already know. is there a forum for one with a test signature?
Click to expand...
Click to collapse
Im not a dev far from one but from what i am reading this sounds like some pretty good information has been gathered just from this old update.....Also you dont have to stay just keep the leaks and any others a coming....Thanks
it seems as they signed all of the partitions... have you guys looked at the odexed version.... under recoveryand overall... what are they trying to patch... BZIP2 is attached and renamed "updater"??? Also traces of BSDIFF just like in other moto images... .
Also this is from the radio_baseband image...
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_mc.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_error_handler.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_flash.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_configure.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_partition.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_loader.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_auth.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_target_accessor.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_parser.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_target.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_flash_nand.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_flash_onenand.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_flash_shared.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_clk.c
OLYMPUSBP_N_01.61.01P.dbl
hassanjanjua2002 said:
designgears said:
If you look in there you can see that it updates recovery, I am assuming it signs it and requires a signature now.
might want to try one with a test signature and see if that works.
Same situation here, as you already know. is there a forum for one with a test signature?
Click to expand...
Click to collapse
are you brave enough to flash the engineering bootloader from the other tread.... ?
It might circumvent the signature checks...
Click to expand...
Click to collapse
zambezy said:
are you brave enough to flash the engineering bootloader from the other tread.... ?
It might circumvent the signature checks...
Click to expand...
Click to collapse
Not saying that I will do it, but; How would we flash those *.bin files to the phone?
mp2ning said:
Not saying that I will do it, but; How would we flash those *.bin files to the phone?
Click to expand...
Click to collapse
I'm guessing with NVFlasher
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
atquick said:
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
Click to expand...
Click to collapse
http://goo.gl/7NoAv
Androidsims said:
http://goo.gl/7NoAv
Click to expand...
Click to collapse
Tried that. It keeps failing saying something about size was not as expected or something like that.
Redownload?
Avelnan said:
Redownload?
Click to expand...
Click to collapse
I have. MD5 sums match up each time. Should I try removing the ext sd card?
I would redownload everything and try agian
littleneutrino said:
I would redownload everything and try agian
Click to expand...
Click to collapse
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
atquick said:
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
Click to expand...
Click to collapse
Downloading the sbf's again. Went over to check and see if the phone was still on, The charging led is on, however the screen is off..
Held power, nothing. Held M + Power. Still nothing... Any thoughts on whats going on now?
I didn't see if you have pulled the SD card but yeah it can't hurt.
Sent from my DROID3 using XDA App
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
wattnxt said:
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
It keeps failing.
Step 3 mbmloader.bin
Step 4 mbm.bin
Step 8 logo.bin
Step 9 'lbl'
I'm stuck.
Let me do some looking when I get home tonight. I remember there being a file for certain versions of XP that helped some people and they couldn't flash without it.
I never had it happen personally, but I know those that did were terribly frustrated.
I also hear the 959 version is easier to flash for some reason. Never flashed that version, so this is only hear-say. But I know it did flash easier according to posts.
I will try to dig up a link for you.
i am getting the same thing also getting the bad CG boot.. now this may be a fix but idk how this guy got it it.. i have been asking eveywhere maybe you guys could help me... here is the thread http://forum.xda-developers.com/showthread.php?t=1248721
I found this by Psouza. He is likely the foremost expert on making things easy as far as unbricking your D3. Rumor has it he has a set of unbrick tools floating around this forum somewhere, though I haven't found it yet. Try in the Development thread, for sure it has to be there somewhere.
Post number 84
psouza4 said:
For those of you having problems flashing this and/or are suspicious of flashing ebr, mbr, and parts of the bootloader, you can selectively just flash the rest of it.
See attachment.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=715510&d=1315657647
Hope this helps.
I also saw that flashing the pre-installs file alone first helped someone. That file borked on me once, but I was able to adb it over and then execute it via adb to get my phone unbricked.
Please let us know what works for you, as all of this is a work in progress right now.
Good luck!
i don't know to much about adb and are looking for help on pre-installed files. I don't understand what that means or how to go about it? i also cant get past the bootloader screen, "invalid CG version". i can not boot up at all.
How bricked are you? can you boot into CWM? Are you able to boot into tools, or how far can you get?
What version were you running? 5.959 (stock) or 6.890 OTA or Leaked OTA or Soak test (all the same as far as 6.890 goes).
i can get into boot tools and just tryed another flash got to step 6 till it failed instead of 3.. I'm running stock. Cannot get passed boot tools... scratch all that just tried to flash again just on the off chance it mnight work and i got it. Going to try and re-root and CWN recovery with sdteel froids rom... will keep you in the loop
Awesome!!
Here is the link about the adb commands for preinstall.sh
http://forum.xda-developers.com/showpost.php?p=17196391&postcount=88
It helped me when I borked my leaked update. I ran into the same problem as limaxray did with too many files in /system. So make sure you clean out any apps you made into system apps before trying the update via the standard update route, and that all stock system apps are in place and properly named.
I had to remove some that updated partially with the leaked update when mine borked. I used the posted system dump to push them to the phone and then the update ran properly and updated them anyhow.
If for some reason re-rooting doesn't work for you. Go to /system/bin and remove su, busybox. Do the same in /system/xbin. For some reason if you already have them in there when you run the process, it will say success but no root after reboot. My 2c as it happened to me. You do not need to remove superuser.apk, but you will have to update it in the market after you re-root.
Congrats!!
I see now too there is a fastboot and moto-fastboot. moto-fastboot has worked for some who had issues from what I've found.
Keep us posted, and smile knowing you've recovered from a bork; none of us got where we are without doing it at least once, so you're in good company.
re-rooted and installed bootstrap, just got steel droid all loaded up and all is good.... thanks for your speedy responses and detailed instructions and links. I realy think all that happened was i took everything aet it sone last time tried to flash and it went threw. All i used was RSD lite and flashed the 8.6.590 fast boot file and after a several retries it went threw. If anyone needs help on this i will post the file links if you need the ones i used
Hi,
I have the non-Taiwan Butterfly S. I unlocked it via HTC Dev, and installed Clockwork Recovery.
This week, the 4.2 update was released for Singapore. It seems to have been in two parts, one which was a minor upgrade (235MB), and after that was applied, I got the option of the larger, 4.3, 700MB, OTA.
Applying the OTA seems to have left me, at boot time, with a blank screen (there is some backlight visible, after the HTC splash). I read tonight that OTA should not be used with custom recoveries, so I have (using fastboot) been able to flash the stock recovery.
I can now go into Fastboot, HBoot, and even Recovery. But I think I may no longer have an actual "system".
How can I flash either a custom ROM, or investigate the situation?
And also, after I see the Recovery screen (the battery icon), what can I do there?
Thanks,
ghane0 said:
Hi,
I have the non-Taiwan Butterfly S. I unlocked it via HTC Dev, and installed Clockwork Recovery.
This week, the 4.2 update was released for Singapore. It seems to have been in two parts, one which was a minor upgrade (235MB), and after that was applied, I got the option of the larger, 4.3, 700MB, OTA.
Applying the OTA seems to have left me, at boot time, with a blank screen (there is some backlight visible, after the HTC splash). I read tonight that OTA should not be used with custom recoveries, so I have (using fastboot) been able to flash the stock recovery.
I can now go into Fastboot, HBoot, and even Recovery. But I think I may no longer have an actual "system".
How can I flash either a custom ROM, or investigate the situation?
And also, after I see the Recovery screen (the battery icon), what can I do there?
Thanks,
Click to expand...
Click to collapse
What I would do is get TWRP Recovery (Just a matter of personal preference you can get clockwormod too) do a full wipe, clear the cache, dalvik cache and install a custom ROM hope I helped somehow
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Also, did the CWM recovery actually succeed to install the smaller OTA? I find that somewhat weird, but then again, I haven't tried to install OTAs using CWM, only TWRP and that did fail early.
If it was a 901S, I'd suggest installing the stock ROM from scratch, but since your phone is 901E (as far as I understand) and my stock ZIPs are for 901S, that's not guaranteed to work. Still, you might try to do that, but make sure to make a backup of the current state first, just in case it only gets worse. If it does work, it's probably going to be the easiest way out.
Another option would be to get someone else with the 901E to post a backup of their /system, I could turn that into a ZIP, which would solve your problem.
koniiiik said:
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Also, did the CWM recovery actually succeed to install the smaller OTA? I find that somewhat weird, but then again, I haven't tried to install OTAs using CWM, only TWRP and that did fail early.
If it was a 901S, I'd suggest installing the stock ROM from scratch, but since your phone is 901E (as far as I understand) and my stock ZIPs are for 901S, that's not guaranteed to work. Still, you might try to do that, but make sure to make a backup of the current state first, just in case it only gets worse. If it does work, it's probably going to be the easiest way out.
Another option would be to get someone else with the 901E to post a backup of their /system, I could turn that into a ZIP, which would solve your problem.
Click to expand...
Click to collapse
It is a 901s he said non Taiwan
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
seyidaga said:
What I would do is get TWRP Recovery (Just a matter of personal preference you can get clockwormod too) do a full wipe, clear the cache, dalvik cache and install a custom ROM hope I helped somehow
Click to expand...
Click to collapse
I have downloaded the Maximus ROM. I am open to doing this, but I cannot figure out how to use the stock recovery (there seem to be no controls).
koniiiik said:
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Click to expand...
Click to collapse
I think so, too, but at this stage, I am willing to go clean-slate and restart with a stock, factory, look.
koniiiik said:
If it was a 901S, I'd suggest installing the stock ROM from scratch
Click to expand...
Click to collapse
I have downloaded the stock zip from your website. How do i flash that in stock recovery?
I have access to fastboot from my laptop, I can see the device.
Thanks,
daorderdillon said:
It is a 901s he said non Taiwan
Click to expand...
Click to collapse
Oh, okay, I think I'm getting lost in which area has which version of the phone. Never mind then and thanks for the correction.
ghane0 said:
I think so, too, but at this stage, I am willing to go clean-slate and restart with a stock, factory, look.
I have downloaded the stock zip from your website. How do i flash that in stock recovery?
I have access to fastboot from my laptop, I can see the device.
Thanks,
Click to expand...
Click to collapse
Well, to install custom ROMs, you'll have to use either TWRP or CWM, I don't know about a way to do that using stock recovery.
Ok, I did this:
Installed CWM Recovery
Flashed the Stock zip from koniiiik's archive
Rebooted successfully. Lots and lots of force closes, Everything from android.core to ...
Used Rom Manager to restore a backup made a month ago
Rebooted. All OK now
Flashed Stock Recovery (again, thanks koniiiik)
Booted. Checked OTA. Got a small update (1.x)
Applied. Rebooted, Checked OTA again
Got the 4.3 package. Applied.
All is well
Between Step #3 and #4, I got my entire backlog of SMS delivered, which I lost in the next step. But that is a small price to pay.
Thanks to all of you helped,
ghane0 said:
Used Rom Manager to restore a backup made a month ago
Click to expand...
Click to collapse
Would you mind uploading somewhere the /system part of that backup? I'd be interested in comparing it to the builds I have at hand.
Backup of /system, nearly stock
I say nearly stock, because it was taken after HTC Unlock, Clockwork Recovery was installed, and root flashed
koniiiik said:
Would you mind uploading somewhere the /system part of that backup? I'd be interested in comparing it to the builds I have at hand.
Click to expand...
Click to collapse
I have three files in the directory:
system.ext4.tar (0B)
system.ext4.tar.a (954MB)
system.ext4.tar.b (500MB)
Is the split to avoid files greater than 1GB?
Will upload starting a few hours. Dropbox will do?
ghane0 said:
I say nearly stock, because it was taken after HTC Unlock, Clockwork Recovery was installed, and root flashed
Click to expand...
Click to collapse
Don't worry about that, of these three, only root affects /system and it should be not too difficult to revert.
ghane0 said:
Is the split to avoid files greater than 1GB?
Click to expand...
Click to collapse
Most likely – FAT filesystems, depending on inode size and other factors, only support file sizes up to a certain limit. Sometimes it's 2 GB, sometimes 4 GB, sometimes probably as little as 1 GB.
ghane0 said:
Will upload starting a few hours. Dropbox will do?
Click to expand...
Click to collapse
That would be most helpful. Thanks.
Dropbox is back up, I have sent you a link.
Thanks