ok, saw this on another forum
here is the link:
http://www.droidforums.com.ar/forum/motorola-droid-bionic/219266-new-ics-leak-238-a.html
and no one knows if it can be fxz back to 235 or even previous fxz pack.
for those who franzy about new updates only and try it at your own risk.
I'll stick with .232 for now!
seems someone already flashed it and i quote
'thanx to samuri making the jump from 235 to 238 was painless
so far have it for about a hour and its been running very smooth and it do feel much more responsive than when i was on 235
glad tosee improvements on every new ics leak
wonder how the battery life gonna be tho
also both eclipse bootstrap and safestrap 2.0 working
havent flash any roms yet but will try tmr
flashed googlenow v6 through bs and its been very solid and fast, voice reconition is good but not great yet
youtube is flawless even on hd
flash works good on dolphin hd stock browser havent try chrome yet
bluetooth working fine with jawbone prime , platronic stereo bt , and in car bt
webtop working fine on lapdock havent find any issue yet
gps seems to lock in faster now
foxfi still working great after a reboot but still cant get wifi tether for root user to play nice
so far so good'
seems it's different flashing upto 238 from 235 to from 232 and below.
SO IF ANYONE INTERESTED, PLEASE BE MORE CAUSTION
feyWANG said:
and no one knows if it can be fxz back to 235 or even previous fxz pack.
Click to expand...
Click to collapse
It's been reported on other sites you can go back to .235 and that's all.
Sir_Eagle said:
It's been reported on other sites you can go back to .235 and that's all.
Click to expand...
Click to collapse
really? that's good news.
and then use the special way to go back 905 from 235?
feyWANG said:
really? that's good news.
and then use the special way to go back 905 from 235?
Click to expand...
Click to collapse
No. There is no returning to 905 from 235. 232 was the last leak that will allow you to return to 905.
Just want to make things clear for people. 238 uses the same security version as 235. The same rules apply. You can't ever go back to 905 from 235 or 238. You may downgrade from 238 to 235. My script allows moving from 232 or lower to 238 and has a method for updating from 235 to 238 as well. It is recommended that most people stay on 232 until the ota is released.
Sent from my Xoom using Tapatalk 2
I can't seem to find a dl link anywhere for 238... anybody?
puckalicious said:
I can't seem to find a dl link anywhere for 238... anybody?
Click to expand...
Click to collapse
get SamuriHL`s House of Bionic
has all you need
sound is still not adjustable with low end lapdock
ghettobilly said:
get SamuriHL`s House of Bionic
has all you need
sound is still not adjustable with low end lapdock
Click to expand...
Click to collapse
I was afraid someone would say this. I rather like the very simple guide in this forum that explains how to install 905 then load up the ICS leak but it only has a link to the 232. Is there a simple link to 238? I really don't want to download and install 3 different HoB files at over a gigabyte when I just need this one file. It seems overly complex for such a straight forward task. I just want the latest ICS and have no desire to ever go back to GB.
well as long as your on 232 and not 235 you can go back to 905 now keep in mind if and when you do get a link for 238 you can never go back to 905 or 902 once you install 238.
But they have NO DESIRE to go back to 905! It doesn't matter that all ics updates require you to be on 905 in order to install. So when the ota comes out it'll be FINE. SIGH. Do people not get what "you can't go back" means? A simple guide and an update file ain't gonna move you from 238 to the next build if there is one. I'm not trying to be rude or mean but you really need should heed the warnings.
Sent from my Xoom using Tapatalk 2
Right. I don't think 235 or 238 really gets you much more than 232 to justify the hassle. Some are gluttons for punishment!
SamuriHL said:
But they have NO DESIRE to go back to 905! It doesn't matter that all ics updates require you to be on 905 in order to install. So when the ota comes out it'll be FINE. SIGH. Do people not get what "you can't go back" means? A simple guide and an update file ain't gonna move you from 238 to the next build if there is one. I'm not trying to be rude or mean but you really need should heed the warnings.
Sent from my Xoom using Tapatalk 2
Click to expand...
Click to collapse
So the script by Matt to revert to the OTA path no longer works? Are you saying it's not possible to go forward from 238, but it is possible from 235? I don't get it.
puckalicious said:
So the script by Matt to revert to the OTA path no longer works? Are you saying it's not possible to go forward from 238, but it is possible from 235? I don't get it.
Click to expand...
Click to collapse
That's not what I said at all. Matt's script nor my own allow you to go back. The process to move forward requires you have the boot.img of the update you're trying to install and then soft bricking your phone until you can apply the update successfully. It's certainly not as simple as FXZ'ing back to 905 and taking the update. So yea, you can move forward so long as you can either make or find the boot.img for the next update and don't mind soft bricking yourself until you're able to apply the update.
---------- Post added at 09:15 AM ---------- Previous post was at 09:01 AM ----------
Let me clarify my post a bit so you have full disclosure....Let's say you move to 238. In a week or two 241 comes out as OTA, for example. You CAN move forward to it using Matt's unstick, but, you MUST have the boot.img for it. This is the process:
o) Push "241" to the sdcard-ext
o) Reboot to AP Fastboot
o) Flash system and preinstall from 905
o) Flash boot.img from "241"
o) Reboot into recovery (MUST NOT try to boot the phone as it will brick)
o) Flash the "241" update
So it's not difficult, but, it's not without risk. Once you flash system and preinstall from 905, you MUST get an update to flash or you won't have a working phone. Both Matt's and my script automate this process.
Understood. Thx for clarifying !!
I have finished dev work on HoB 4.0 which will hopefully be the last major version of the HoB. It adds support for adding new releases as they get leaked. So if you manage to get ahold of the mythical 241 release, you can update your own copy of HoB by following a few simple steps. That will then add 241 to the HoB menus and allow you to move to it from any release. All without me having to do anything.
heard 238 is smooth.
ax562 said:
heard 238 is smooth.
Click to expand...
Click to collapse
Anyone have a download link? I am struggling to find one through all the various forums and forums topics.
What version are you on now?
Related
Check out the changelog in the link.
http://www.droid-life.com/2012/02/07/new-droid-bionic-update-5-9-902-is-ready-here-is-the-changelog/
Post up if you got it.
Sent from my DROID BIONIC using Tapatalk
What if i am on the 901 leak unrooted should I still receive update or do I have to use pathsaver to revert yo 893
Sent from my DROID BIONIC using XDA App
bfitzpatrickd2d said:
What if i am on the 901 leak unrooted should I still receive update or do I have to use pathsaver to revert yo 893
Click to expand...
Click to collapse
If someone can grab/post the 5.9.902 update file, You can try it first while still on .901, and see what happens. It shouldn't hurt.. either it will work, or the "assert" check will fail and not proceed.
currently on 5.901 should I fxz back 5.893 or use p3's one click? will I still get cdt bin errors if I fxz?
ROB281 said:
currently on 5.901 should I fxz back 5.893 or use p3's one click? will I still get cdt bin errors if I fxz?
Click to expand...
Click to collapse
I was on 5.9.901 as of last night.
Following P3's posts on MDW (http://www.mydroidworld.com/topic/9906-bionic-path-saver-1-click-method/ )... and what CellZealot posted later in that thread (post #440 to be exact)... I unzipped the 5.5.893 full flash xml, replaced the CDT.BIN file, then flashed back to 5.5.893 via RSDLite successfully.
---------- Post added at 03:48 PM ---------- Previous post was at 03:46 PM ----------
Based on the screen shots from when Droid-Life posted about 5.9.901, and the screen shot someone posted in the comments of their 5.9.902 story, the base band in .902 is updated.
I'm hoping that means a possible fix for the data dropping.
Only time will tell.
KidJoe said:
I was on 5.9.901 as of last night.
Following P3's posts on MDW (http://www.mydroidworld.com/topic/9906-bionic-path-saver-1-click-method/ )... and what CellZealot posted later in that thread (post #440 to be exact)... I unzipped the 5.5.893 full flash xml, replaced the CDT.BIN file, then flashed back to 5.5.893 via RSDLite successfully.
---------- Post added at 03:48 PM ---------- Previous post was at 03:46 PM ----------
Based on the screen shots from when Droid-Life posted about 5.9.901, and the screen shot someone posted in the comments of their 5.9.902 story, the base band in .902 is updated.
I'm hoping that means a possible fix for the data dropping.
Only time will tell.
Click to expand...
Click to collapse
i'm about to use the same xml to flash back to 5.5.893. i can't find the CDT.BIN file to replace. can you provide me with a link?
edit: nevermind. is it the same cdt.bin file that is inside the 901fix.zip?
envizion58 said:
i'm about to use the same xml to flash back to 5.5.893. i can't find the CDT.BIN file to replace. can you provide me with a link?
edit: nevermind. is it the same cdt.bin file that is inside the 901fix.zip?
Click to expand...
Click to collapse
Yes. That is the one I used.
but since I'm assuming its hitting soak testers (since Moto posted something about invites), its going to be a few days until VZW pushes, assuming soak goes well?
So maybe you should wait until we see more posts of people getting the OTA first?
(My bionic has been sitting on the shelf idle, while I use my TB... so rolling it back early, in anticipation, doesn't impact me at all)
Why not just sit tight and see what they screwed up in this OTA BEFORE you get all giggly.
RMD
rduckwor said:
Why not just sit tight and see what they screwed up in this OTA BEFORE you get all giggly.
RMD
Click to expand...
Click to collapse
No faith huh? Make sure you decline it then. I'm willing to take the gamble (though I'm going to guess there is not much risk).
Other than a new radio and some app differences, it looks very similar to 901. I doubt they will have made anything worse so I for one am looking forward to getting ahold of 902. However, I'm not jazzed about the concept of moving back to 893. We'll see how patient I am to see if a 901->902 update is released to those who OFFICIALLY got the 901 update accidentally pushed to them. I'll PROBABLY go back. I have a nandroid of 893, so, I just need to FXZ my phone back to it (with the proper cdt.bin, of course), restore the nandroid, and then update it to 902. Oh so fun. Of course, we have to get our hands on 902 for that to happen, so, right now patience is forced.
I may be missing something here, but if I unzip the fxz file all I can click on in rsd is the xml file out of the zip
do I need to recompress the file or anything like that?
ROB281 said:
I may be missing something here, but if I unzip the fxz file all I can click on in rsd is the xml file out of the zip
do I need to recompress the file or anything like that?
Click to expand...
Click to collapse
if you're looking to get back onto 5.5.893 so you can update to .902... then...
See -> http://www.mydroidworld.com/topic/9...-click-method/page__view__findpost__p__112340
in particular...
...To flash with RSD Lite you download the full xml.zip and extract it to a directory and then open RSD Lite and connect the phone and then drag the .xml file from that directory into the right pane of RSD Lite and hit the start button. It will do the rest and switch the phone into fastboot flash mode and run all the component flashes and then reboot into recovery to complete the radio flashes and then reboot again. The entire process will take about 20 min. depending on your PC.
Click to expand...
Click to collapse
Only caveat being, if you are on 5.9.901 right now, BEFORE YOU FLASH the Full 893 XML, you need to overwrite the cdt.bin that is in the DIR where you extracted the full xml zip to, with the one from the 901fix.zip... or you will get errors.
do not re-compress, or anything.
And if you want root 893, then here is the info I used -> http://www.mydroidworld.com/topic/9...-upgrade-path/page__view__findpost__p__103640 and then did the manual steps at -> http://www.mydroidworld.com/topic/9...ot-through-any-upgrade-motorola-devices-only/ to keep ROOT after updates.
For more specific details/steps, see -> http://forum.xda-developers.com/showpost.php?p=22286991&postcount=50
got 902 this am in wyo. ready for ics now. the update seems to be ok xcept for added unness bloat 3 or so...blutooth working better and still have tether.
Dropped from 901 to 593, but it's not seeing the update. Yay...
done, and back on 5.893 thanks
If they're doing a soak test, dropping back to 893 unless you're part of the soak test is a tad premature.
SamuriHL said:
If they're doing a soak test, dropping back to 893 unless you're part of the soak test is a tad premature.
Click to expand...
Click to collapse
Right. If I'm not mistaken, Moto said the soak would roll out to about 1000 testers who they did NDA with, and requested feed back, as well as a couple thousand that they were not soliciting feed back from.
So unless you're from that small group, OR your Bionic is sitting on the shelf collecting dust (like mine), there isn't reason to roll back yet... at least, not until/unless one of the soak testers breaks the NDA and leaks, or one of the non-soak/feedback participants (and therefore not under NDA) grabs and posts.
KidJoe said:
Right. If I'm not mistaken, Moto said the soak would roll out to about 1000 testers who they did NDA with, and requested feed back, as well as a couple thousand that they were not soliciting feed back from.
So unless you're from that small group, OR your Bionic is sitting on the shelf collecting dust (like mine), there isn't reason to roll back yet... at least, not until/unless one of the soak testers breaks the NDA and leaks, or one of the non-soak/feedback participants (and therefore not under NDA) grabs and posts.
Click to expand...
Click to collapse
That's exactly right. Hence why I'm not jumping to move back to 893 just yet. With all the soak testers who've claimed to get it, not one of them has released it. (Which is as it should be, tbh, as they did sign an NDA). I'm sure it WILL get leaked eventually, but, until then, just leave the poor Bionic alone.
Can someone post the update.zip please
SamuriHL said:
That's exactly right. Hence why I'm not jumping to move back to 893 just yet. With all the soak testers who've claimed to get it, not one of them has released it. (Which is as it should be, tbh, as they did sign an NDA). I'm sure it WILL get leaked eventually, but, until then, just leave the poor Bionic alone.
Click to expand...
Click to collapse
I got it earlier today via soak, installed over stock but rooted 893 (with 4everroot) and kept root. 902 seems fine for me, no issues. I did of course grab a copy of it before updating. Figured someone else would have posted it by now...
Just saw this thread at droidforums: http://www.droidforums.net/forum/droid-4-roms/208767-stock-motoblur-ics-droid4.html
Can anyone confirm if this is legit?
EDIT: Removed link to the update file for everyone's safety. This is not an update you want to install. It will take you off the update path and attempting to flash one of the currently available fastboot files will result in a brick.
I pulled the same thing by the cake method earlier today but was afraid to flash a unknown.
I tried, based on the instructions on the page, and as usual, cheesecake won't work for me. I get the "account needed" prompt. I'll try again tomorrow.
Thanks!
I'm downloading it now. I hope this works with Safestrap and I get to keep root. Or at least be able to re-root again. Have to be carefull. Need GSM to work
The day after I sold my T-Mo Sensation, and the day before I get my VZW Droid 4. Looks like the gods have decided not to smite me today.
Booted Safestrap. Flashed stock 215.
Can't update to 219 So no wonder I couldn't update to ICS... Here I go again...
It sounds like a couple of people over on DroidForums HAVE gotten this to load. To paraphrase what hashcode said over there, be very very careful with this guys. There are quite a few Razr owners now stuck outside of the upgrade path and unable to use fastboot to restore after flashing an ICS leak. I think I am going to hold off on this one personally. What I am REALLY hoping to see is some improvements to CM9, AOKP, and Gummy come out of this. Particularly the data issues.
Trying it the Cheesecake way and its downloading. Anyone tried it yet? Curious if Safestrap survived. As long as it works I'll be glad. Hope the different baseband fixed audio over UMTS/HSDPA.
Die Bruine said:
Trying it the Cheesecake way and its downloading. Anyone tried it yet? Curious if Safestrap survived. As long as it works I'll be glad. Hope the different baseband fixed audio over UMTS/HSDPA.
Click to expand...
Click to collapse
You are a brave man Try using OTA RootKeeper. It worked with the last update. I would be very interested to see if it works with the ICS update as well.
Ok guys, I installed it. Voodoo OTA RootKeeper did NOT work for me, and attempting to flash the 6.13.219 fastboot file resulted in a brick.
I would strongly advise not installing this update.
SGMD1 said:
Ok guys, I installed it. Voodoo OTA RootKeeper did NOT work for me, and attempting to flash the 6.13.219 fastboot file resulted in a brick.
I would strongly advise not installing this update.
Click to expand...
Click to collapse
Really sorry to hear that. Thanks so much for the information though. Did you try the .215 fastboot file? I'm guessing the result would be the same but might be worth a shot.
Can you tell us why you tried to install the fastboot file? You didn't like ICS or is it because of root priviliges? I've tried like 15 times. It just won't update. So now I temp unrooted, uninstalled Safestrap and hope for the best. Next step woul be to fastboot 219 and try on a fresh clean install. The only thing I can think of is that my build.prop gets in the way. Anyone mind posting a stock .219 build.prop?
XDA app on XT894
kwyrt said:
Really sorry to hear that. Thanks so much for the information though. Did you try the .215 fastboot file? I'm guessing the result would be the same but might be worth a shot.
Click to expand...
Click to collapse
Downloading .215 as we speak, but I'm not getting my hopes up. No big deal though, VZW is overnighting me a warranty replacement and I've got an old phone I'm using for the day.
EDIT: .215 failed at 6/18 as well.
Die Bruine said:
Can you tell us why you tried to install the fastboot file? You didn't like ICS or is it because of root priviliges? I've tried like 15 times. It just won't update. So now I temp unrooted, uninstalled Safestrap and hope for the best. Next step woul be to fastboot 219 and try on a fresh clean install. The only thing I can think of is that my build.prop gets in the way. Anyone mind posting a stock .219 build.prop?
Click to expand...
Click to collapse
There were a several things with this ICS build that were a bit disappointing (native ICS screenshot function didn't work, no "Charge only" mode when connected via USB to PC) but no root access was the dealbreaker. I knew flashing the .219 file was a risk based on what happened with the RAZR ICS leaks but I just figured I'd be the guinea pig
I had the same problem you did when attempting to install it, so I flashed the clean .219 fastboot file and then the ICS update was successful.
build.prop
Die Bruine said:
Can you tell us why you tried to install the fastboot file? You didn't like ICS or is it because of root priviliges? I've tried like 15 times. It just won't update. So now I temp unrooted, uninstalled Safestrap and hope for the best. Next step woul be to fastboot 219 and try on a fresh clean install. The only thing I can think of is that my build.prop gets in the way. Anyone mind posting a stock .219 build.prop?
XDA app on XT894
Click to expand...
Click to collapse
Here is the build.prop file... it is compressed into a zip archive since .prop cannot be attached.
****EDIT: THIS IS THE .215 build.prop
build.prop 219
rumgool said:
Here is the build.prop file... it is compressed into a zip archive since .prop cannot be attached.
****EDIT: THIS IS THE .215 build.prop
Click to expand...
Click to collapse
Okay... here is the 219 build.prop zipped
You gotta be kidding me pffffff. Those guys at Motorola check eeeeeeverything. Thnaks for the build.prop btw rumgool. But now it hangs on Motorola_XT894....3gp. Unbelievable...
Finally got it going. But like you said, had to flash SBF. That's some pretty scary **** . I'm used to Milestone / Droid 1 flashing and I've flashed a Razr before. This one takes twice as long. So for you wanting to flash SBF, don't be alarmed. It takes a while, a very loooong while.
Question: Why would the update prevent flashing via fastboot? I'm only familiar with SBFs, but the point of those were that no matter how bad things got, you could wipe everything out and start over. Is that no longer the case
GSM working!!!!!!
Yes!!!! audio over 3G GSM!!!!
Finally. Don't know what works and what doesn't. But audio works and you have GSM settings right from the get go. Now I'm gonna eat, then I'm gonna play and after that I'll tell you what I think of it.
Thanks guys!
podspi said:
Question: Why would the update prevent flashing via fastboot? I'm only familiar with SBFs, but the point of those were that no matter how bad things got, you could wipe everything out and start over. Is that no longer the case
Click to expand...
Click to collapse
The new fastboot files are nothing like the old sbf's. Wrong radio, different build number and many other things can cause it to fail. Then your stuck in fastboot mode with a soft brick.
Sent from my DROID4 using Tapatalk
This is a really nice build! I am not at all sorry to have risked being stuck, to be honest.
Everything appears to work very well so far and I am posting from Chrome Beta.
Still looking for the downside...
Master qa1 and 2 got updated at 8:30. Same with master qa300 and sdc100. I don't wanna have to FXZ back to check and be let down.
Edit: spoke too soon. qa200 was updated today, the 12th. Please check! D:
Ugh, whatever. I'm gonna test out the shell script I just wrote to do a full restore, OTA to 905, then check cheesecake. I may do it tonight, but if I don't, I will tomorrow. Maybe someone who's already on 905 will beat me to it
Edit: damn thing won't boot. fml. Trying to FXZ to 902. Not working. Um uh er uh. Great.
bionic cheesecake
I've check those servers today and only have .232 showing up from a few servers. I also see a bunch of "simpsons" servers named after simpsons characters. So I'm about to check those but i've already checked the rest without seeing anything other than .232
.235?
I saw on droid hive that .235 is out. Can anyone here check?
josdad00 said:
I saw on droid hive that .235 is out. Can anyone here check?
Click to expand...
Click to collapse
Where did you see that? I'm not finding anything about it over there.
fastpakr said:
Where did you see that? I'm not finding anything about it over there.
Click to expand...
Click to collapse
I can't find anything there either. Can you post a link?
cromanorn said:
I can't find anything there either. Can you post a link?
Click to expand...
Click to collapse
Someone mentioned it in the Droidhive Shoutbox without any details, and never provided a link. Since then, they haven't been in the Shoutbox and never did create a thread. You might find it digging through the Shoutbox archive, but with no details provided, the only way to know for sure is if someone else checks cheesecake.
They're talking about it on droid hive in the shout box but no links for download. Several people are saying they are downloading.
Noooooooooooooooooooooooo
There's a guy on Droid Hive uploading it right now.
Yes indeed. I'm going to check it once we have a link and see if they updated the security to disallow going back to 902 from it. So far it's unlikely but never hurts to check.
http://www.megashare.com/4392491
I was reading on DroidHive that if you flash .235 you can't go back to gingerbread.
WOA WOA WOA. A big word of caution guys. If you do 235 you will *NOT* be able to FXZ back to 902! The security has been updated. This is a one way trip forward if you do this one.
SamuriHL said:
WOA WOA WOA. A big word of caution guys. If you do 235 you will *NOT* be able to FXZ back to 902! The security has been updated. This is a one way trip forward if you do this one.
Click to expand...
Click to collapse
So, over on the Droid 3 forums, there was a similar situation with the .906 update, you couldn't revert back to .890. They figured out that there were certain .img and .bin files that couldn't be written over, but someone managed to put together a modified fxz replacing the files that couldn't be changed with ones from the update, and a modified xml file. Once this was done, you could install the modified .890, and then update to the newer software. It turned out that the .906 leak was in fact what would become the OTA. Does anyone think that something like this is possible for the .235 leak? Thanks to these guys for originally figuring it out on the D3 Q9nap, Redsox985, Psouza4, and Ovelayer.
Here's a link to the D3 thread: http://forum.xda-developers.com/showthread.php?t=1686911
I'm aware. NOT going to happen in our unique situation. The reason is that the leaks require 905. The method they used on the D4 and RAZR require FXZ files from the version you're updating from. We only have one for 902. And there's no way to get back to 905 from that once you install 235+. Hence, if you install 235, you're stuck there for a long time. Unless an FXZ comes out for 905 or the OTA ICS build. IOW, stick to 232 until the OTA comes out.
Pretty sure I know the answer to this already... Is there any chance the .235 update can be reached from both .902 and .905? I'm aware the previous updates didn't allow that.
No chance at all. Updates well, um, update files on the system they were designed to update from. 902 != 905 so when patching files you'd be left with a mess. lol
No. You have to be on 905.
Fair enough. Noticed the new update was slightly larger than the previous ones, hoped it might have been designed to allow more than one upgrade path. Oh well.
In an attempt to go from ICS 206 to 215, I followed the instructions step by step and using the utility, when I get to the step where it says instill zip file from SD card, I navigate to "D4.6.16.215.zip", apply it, and it says update aborted.
My phone will now no longer boot beyond the M Dual Core screen. It is simply blank. Does anyone have any ideas?
i was about 5mins away from doing the same thing you did before glad i saw this gonna, i'm gonna wait until you find a fix (im on .213)
icebear8 said:
i was about 5mins away from doing the same thing you did before glad i saw this gonna, i'm gonna wait until you find a fix (im on .213)
Click to expand...
Click to collapse
Well I'm back working again, but it's still on 206 even though I went through the flashing process to 215. I haven't even thought about updating my phone since installing 206 when it came out. I have read many threads that talk about "unsticking" to get from 206 to 208, but they're over a month old. I can't follow the instructions associated with unsticking because a) they're written for the razr and thus are ridiculously confusing, and b) the one thread that tries to explain how to use unstuckICS for D4 users makes even less sense.
I posted about where to get unstuckICS on another forum and someone directed me back to the Droid4withICSfix-rootLITE tool, which I already had. Step 16 seems to flash (with a TON of error that are supposedly to be expected) but then I can't apply any zip updates. All attempts abort.
This is all so maddening because nothing I try is working. At least my phone isn't a paper weigh. So I have that going for me... which is nice.
strakajagr said:
Well I'm back working again, but it's still on 206 even though I went through the flashing process to 215. I haven't even thought about updating my phone since installing 206 when it came out. I have read many threads that talk about "unsticking" to get from 206 to 208, but they're over a month old. I can't follow the instructions associated with unsticking because a) they're written for the razr and thus are ridiculously confusing, and b) the one thread that tries to explain how to use unstuckICS for D4 users makes even less sense.
I posted about where to get unstuckICS on another forum and someone directed me back to the Droid4withICSfix-rootLITE tool, which I already had. Step 16 seems to flash (with a TON of error that are supposedly to be expected) but then I can't apply any zip updates. All attempts abort.
This is all so maddening because nothing I try is working. At least my phone isn't a paper weigh. So I have that going for me... which is nice.
Click to expand...
Click to collapse
Literally the tool does nothing. I run it. Everything in step 16 essentially errors out. Ultimately the phone reboots having accomplished zero. I am "stuck" on 206.
strakajagr said:
Literally the tool does nothing. I run it. Everything in step 16 essentially errors out. Ultimately the phone reboots having accomplished zero. I am "stuck" on 206.
Click to expand...
Click to collapse
here is a boot.img i got from Droid forums https://www.dropbox.com/s/zwl0e6jx767aksb/boot-6-16-215.img try using this one and rename it to ICSFIX
icebear8 said:
here is a boot.img i got from Droid forums https://www.dropbox.com/s/zwl0e6jx767aksb/boot-6-16-215.img try using this one and rename it to ICSFIX
Click to expand...
Click to collapse
Tried that. Same result. I have to believe this has something to do with the 206 build that I'm on, though I don't know why that latest utility doesn't address this since the 206 sticking thing seems to be a problem that was addressed so long ago.
\how did you get back to normal when you soft bricked? so i know i can get back if i get the same problem. i might try this just to see if it works for me
---------- Post added at 12:34 AM ---------- Previous post was at 12:22 AM ----------
icebear8 said:
\how did you get back to normal when you soft bricked? so i know i can get back if i get the same problem. i might try this just to see if it works for me
Click to expand...
Click to collapse
VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01.xml.zip this is the fastboot GB 219 files correct? my files are all over the place lol
I just booted to recovery and did a data wipe/factory reset, and I was back to stock 206. I didn't use that xml file because I'm not upgrading from GB.
well i just bricked my self on the update lol
Not sure why you guys are having trouble. I used the tool yesterday to go from 213 to 215. Basically we are flashing the GB files, then the boot.img for 215, letting it reboot and attempt to update, it will stick at the moto boot logo, then flashing the update in stock recovery. The only thing that might be of issue is if you are running safestrap, menu 16 is designed to not over write your data. I haven't tried running safestrap and using menu 16 to update. You can try the old method of flashing the GB files, Flashing the boot.img and then recovery update flash.
jsnweitzel said:
Not sure why you guys are having trouble. I used the tool yesterday to go from 213 to 215. Basically we are flashing the GB files, then the boot.img for 215, letting it reboot and attempt to update, it will stick at the moto boot logo, then flashing the update in stock recovery. The only thing that might be of issue is if you are running safestrap, menu 16 is designed to not over write your data. I haven't tried running safestrap and using menu 16 to update. You can try the old method of flashing the GB files, Flashing the boot.img and then recovery update flash.
Click to expand...
Click to collapse
In terms of names - are you using boot.img or ICSFIX.img for the name of boot on .215?
Right, but you're not dealing with upgrading from 206, which is supposedly the pain in the ass build to upgrade from.
strakajagr said:
Right, but you're not dealing with upgrading from 206, which is supposedly the pain in the ass build to upgrade from.
Click to expand...
Click to collapse
I`m going to update from 213 to 215, and still need an anwer: ICFIX.img or boot.img?
Thanks in advance.
mrAdvo said:
I`m going to update from 213 to 215, and still need an anwer: ICFIX.img or boot.img?
Thanks in advance.
Click to expand...
Click to collapse
You should be able to rename to boot.img and upgrade from .213 to .215. As for the .206 upgrade you may have to follow the full upgrade process outlined in the ics upgrade thread in which you have to flash the gb fastboot before upgrading to the next build. It seems to have worked for most people going from leak to leak.
Sent from my DROID4 using xda app-developers app
If your using the modified D4 tool I made then you should name it ICSFIX. However I think we can shorten the process further and will try to work on that tonight.
Sent from my DROID4 using Tapatalk 2
azrael293 said:
You should be able to rename to boot.img and upgrade from .213 to .215. As for the .206 upgrade you may have to follow the full upgrade process outlined in the ics upgrade thread in which you have to flash the gb fastboot before upgrading to the next build. It seems to have worked for most people going from leak to leak.
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Wait, are you saying that you can just flash the boot.img without having to fastboot GB?! Cause if that is the case, I wasted a ton of time last night going from 213 --> 215
podspi said:
Wait, are you saying that you can just flash the boot.img without having to fastboot GB?! Cause if that is the case, I wasted a ton of time last night going from 213 --> 215
Click to expand...
Click to collapse
Going by the tool you would have to flash the fastboot of the GB files then proceed to flash the current leak. Same as with all the previous leaks. What I meant by flashing it as boot.img is that name format should work, tho jsnweitzel said that with his tool it should be named as icsfix.img instead. he replied right after I had posted and I'd go with his response since it is his code/tool. lol
azrael293 said:
Going by the tool you would have to flash the fastboot of the GB files then proceed to flash the current leak. Same as with all the previous leaks. What I meant by flashing it as boot.img is that name format should work, tho jsnweitzel said that with his tool it should be named as icsfix.img instead. he replied right after I had posted and I'd go with his response since it is his code/tool. lol
Click to expand...
Click to collapse
Ok, I was just afraid for a moment I had wasted a bunch of nail-biting time or something
I think a lot of people get tripped up at the boot.img --> ICSFIX.img step. Especially because the instructions tell you to rename it to ICSFIX, not ICSFIX.img (which Windows may or may not do for you automatically, depending on your settings).
That being said, it is still incredibly easy to move from one leak to the other with the utility, it is incredibly awesome.(Thanks jsnweitzel!)
I'm looking to upgrade to JB or another rom as my current version is starting to act up. My phone has gotten ridiculously slow and I struggle with switching tasks and random reboots. I'm currently running 6.7.232, I flashed this version last year before the official ICS release came out. Can I flash straight to JB from my current version or do I have to go back to GB then doing the OTA upgrades? I'm very confused on what order I should follow when trying to get JB. I've been trying to find a guide but I'm afraid of bricking my phone if I try to go back to GB or straight to JB.
Thanks for the help!
jradicle11 said:
I'm looking to upgrade to JB or another rom as my current version is starting to act up. My phone has gotten ridiculously slow and I struggle with switching tasks and random reboots. I'm currently running 6.7.232, I flashed this version last year before the official ICS release came out. Can I flash straight to JB from my current version or do I have to go back to GB then doing the OTA upgrades? I'm very confused on what order I should follow when trying to get JB. I've been trying to find a guide but I'm afraid of bricking my phone if I try to go back to GB or straight to JB.
Thanks for the help!
Click to expand...
Click to collapse
My suggestion is don't touch the Jelly Bean leak. I check the thread out every couple days and nothing but problems. If you want to try Jelly Bean download Liquid Smooth 2.3. The only thing not working is Bluetooth (apparently, have no use for bluetooth).
I believe you must be on .246 to update to JB. No frozen, deleted, or altered system files either. I took the update and am very happy with it.
mikemikemikexxx said:
My suggestion is don't touch the Jelly Bean leak. I check the thread out every couple days and nothing but problems. If you want to try Jelly Bean download Liquid Smooth 2.3. The only thing not working is Bluetooth (apparently, have no use for bluetooth).
Click to expand...
Click to collapse
Even with it being an official upgrade?
Can't you flash to 246 using RSD then OTA to JB? I'm not sure you can flash to GB from 232 or whatever u said u are on. I tried doing that and got an error each time, but I was trying to go from 246 to GB. I flashed 246 over my installed 246 then OTA to JB and my device has been stellar since.
Sent from my DROID BIONIC using xda app-developers app
flyfisher7 said:
Can't you flash to 246 using RSD then OTA to JB? I'm not sure you can flash to GB from 232 or whatever u said u are on. I tried doing that and got an error each time, but I was trying to go from 246 to GB. I flashed 246 over my installed 246 then OTA to JB and my device has been stellar since.
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
That's exactly what I ended up doing. I flashed to 246 and OTA'd to JB. It ended up working quite well. I want to put on CM10.1, hopefully I don't have to flash back to 246.
A couple things here. First you could have saved time and effort by just fxz'ing to jb directly using the 98.72.22 fxz. Yes, even over 232. Second, your comment about "hoping you don't have to downgrade" is frightening. Simple solution to that one. You can't. Period.
Sent from my Xoom using Tapatalk HD
SamuriHL said:
A couple things here. First you could have saved time and effort by just fxz'ing to jb directly using the 98.72.22 fxz. Yes, even over 232. Second, your comment about "hoping you don't have to downgrade" is frightening. Simple solution to that one. You can't. Period.
Sent from my Xoom using Tapatalk HD
Click to expand...
Click to collapse
So if you've taken the OTA JB update then you're screwed? No possible way to go back to ICS?
My phone worked great on ICS but since the forced OTA JB update it has become a complete piece of crap. I lose Verizon signal constantly and have to reboot my phone to get it back. This happens probably 6-7 times a day. Text messages hang and don't send, I get strange UI FC's, etc.
Has anyone else run into these issues? Any suggestions on how to fix?
Thanks,
Michael
Correct, there is no possible way to downgrade to ICS once you've taken the JB update. The security mechanism behind this inability to downgrade has been well understood since the ICS days. Given that you couldn't downgrade to GB from ICS, I'm not sure why so many people are surprised to find the same situation with JB.
Anyway, to fix your issues you should probably do a Factory Data Reset (FDR). This will wipe your data partition so you will have to reinstall your apps and setup the phone as if it were brand new out of the box. However, this will give it a fresh start and will likely fix the issues you're seeing with the phone.
SamuriHL said:
Correct, there is no possible way to downgrade to ICS once you've taken the JB update. The security mechanism behind this inability to downgrade has been well understood since the ICS days. Given that you couldn't downgrade to GB from ICS, I'm not sure why so many people are surprised to find the same situation with JB.
Click to expand...
Click to collapse
Honestly I am not surprised. I am the idiot who clicked OK without researching what the update was first. If I had, I wouldn't have taken it.
SamuriHL said:
Anyway, to fix your issues you should probably do a Factory Data Reset (FDR). This will wipe your data partition so you will have to reinstall your apps and setup the phone as if it were brand new out of the box. However, this will give it a fresh start and will likely fix the issues you're seeing with the phone.
Click to expand...
Click to collapse
I thought about doing that, but I was hoping not to have to do so.
Since I was also dumb enough to not have OTA root keeper installed of course I lost root too. I see there is another post about rooting stock JB using Linux, etc. Has anyone developed another method yet? I have searched but haven't found anything. I used the motofail method to get root on ICS, but no posts as to whether that works on JB or not.
Thanks,
Michael
No possibility of root without using the Linux exploit. Don't bother waiting for a windows version as it's not coming. There are "easy root" solutions out there that are basically a virtualbox image that you can just load up and run the script.
As for an FDR, you're needing to if you're having those problems. Nothing else is going to fix it.
SamuriHL said:
No possibility of root without using the Linux exploit. Don't bother waiting for a windows version as it's not coming. There are "easy root" solutions out there that are basically a virtualbox image that you can just load up and run the script.
As for an FDR, you're needing to if you're having those problems. Nothing else is going to fix it.
Click to expand...
Click to collapse
Ok so be it. I saw that post on the Easy Root using a virtualbox image.
I also saw this post: http://forum.xda-developers.com/showpost.php?p=40430047&postcount=73
Since I previously had root on ICS, will this work for me?
Thanks for patiently answering my questions, I appreciate it.
Michael
It's worth a shot. FDR won't affect the system partition at all so if it works you won't lose root doing the FDR.
SamuriHL said:
It's worth a shot. FDR won't affect the system partition at all so if it works you won't lose root doing the FDR.
Click to expand...
Click to collapse
Ok I will give it a try and go from there..
Hopefully with root restored and FDR my phone will return to what it was and I will be happy with it once again.
Thanks again,
Michael