yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy 5 I5500] CurtisAndroid5:
768 MHz is very unstable on my device. Just letting you know.
[Samsung Galaxy 5 I5500] Multiburatino:
i was on 2.3.5 and i was running only at 768 but i want more:)) . So i was bored with the 2.3 and turned to 2.2 :) so now i know the best is 768 so i want that kernel to run on my 2.2
[Samsung Galaxy 5 I5500] Jordanooo:
If you want more, buy a new phone.

Just sayin'
[Samsung Galaxy 5 I5500] sasi8998vv:
Buy a new one? ****, no way!!!!

THIS phone, is the best ive ever seen. Functionality wise, its better than a S2.

Maybe thats cuz im running, CM7.1.

Either way, im not getting a new one.

I need a faster kernel too.

either give it to me, or BURN IN HELL FOR SACRILEGE!

hey, just kiddin.
[Sony Ericsson Xperia Neo, Pro] MaxMedia:
I use google map version 6.0.2, but after using and return to idle mode, the device drain battery quickly, about 5% for 1 hour.

If restarted, all back to normal, about 1% for 2 hours.

I'm not using Google Latitude. And "Use wireless networks" always checked

Plz help me.
[Sony Ericsson Xperia Neo, Pro] electrash:
That is cuz mapps stay in you RAM.

Kill it in manage application in settings.
[Sony Ericsson Xperia Neo, Pro] LenAsh:
That's how Android works... apps stay in RAM - killing apps is NOT the answer unless they are misbehaving, which Maps doesn't. There is a reason for unusual battery drain, and that ain't it. Needs more methodical investigation.
[Sony Ericsson Xperia Neo, Pro] electrash:
please post screen shoot only if you using Sony ericsson.

Other brands we dont interest in to.
[Sony Ericsson Xperia Neo, Pro] MaxMedia:
of course, i use xperia neo.
[Sony Ericsson Xperia Neo, Pro] LenAsh:
Not a stock ROM, so you're on your own. The Stock SE .42 ROM and Maps are fine.
[Sony Ericsson Xperia Neo, Pro] electrash:
which ROM do you use?
[Sony Ericsson Xperia Neo, Pro] MaxMedia:
I use stock room .42 + themes GS2.

//stock room .42 use google map 5.6. No "download arena map" feature.
[Sony Ericsson Xperia Neo, Pro] LenAsh:
6.0.3 is the latest Maps version by the way
[Sony Ericsson Xperia Neo, Pro] tinyXperia:
How often does that happen? Had that a couple of times, because maps couldn't find my location by GPS.
[Motorola Droid Bionic] open1your1eyes0:
*****DO NOT DO THIS (See why here)*****​

Hey guys,

I currently have a very messed up 5.7.893 (webtop missing, forever root, unable to get to 5.8.894 from cheesecake, etc...).

I'm looking to get back to completely factory stock image that accepts OTA's properly. Seems like there are a lot of mixed messages in the threads. Does anyone have a method that is confirmed working?
[Motorola Droid Bionic] rumpy:
I was able to get to the OTA update using the following. Not sure if I got lucky or if it works for everyone.

I was able to get from the leaked 5.7 update to the official Verizon 893 Ota update.

1 – I used the R3L3AS3DRoot program and restored back to stock.

2 – Using the same program I 4RVRRooted the phone

3 – started up phone and did not sign into anything (google, etc). Did the bare minimum to get the phone up and running.

4 – Restarted in stock recovery and flashed radio.zip file that puts the radio back to stock. http://xdaforums.com/showpost.php?p=19680673&postcount=40

5- Downloaded the OTA update and attempted to install. Phone rebooted and said that the update failed.

6- Copied the OTA update from http://www.multiupload.com/0ZEN69NGO2

7 – Installed the OTA update – SUCCESS!!

8 – Root is still there.

I am now at:

System version – 5.7.893.xt875.Verizon.en.US

Baseband Version – CDMA_n_03.1C.57r LTEDC_U_05.15.02

Webtop – WT-1.3.0-108_dbn-21

Kernel – 2.6.35.7-g68606e6 vwm736@il93lnxdroid43 #1

Build number – 5.5.1_84_dbn-62
[Motorola Droid Bionic] open1your1eyes0:
Links for #4 and #6 are no good. You have dots in that link "..."
[Motorola Droid Bionic] rumpy:
hopefully I fixed them. Sorry about that
[Motorola Droid Bionic] open1your1eyes0:
Thank you very much. I will try it out tonight and let you know.
[Motorola Droid Bionic] dB Zac:
but system # 5.7.893 is a cheesecake leak, not the OTA. The OTA is 5.5.893

the only things that don't match the leak I am on are the Webtop version ( WT-1.3.0-105_DBN-1) and the build # on my phone has an added MR-11 to the end of it
[Motorola Droid Bionic] open1your1eyes0:
This is correct. I won't need to do that part, just get to stock, flash stock radios, and then check for updates and install the OTA when it shows up.
[Motorola Droid Bionic] dB Zac:
what part? I am saying that the post above did not get him to the OTA according to his own final information.
[Motorola Droid Bionic] open1your1eyes0:
That's right because he flashed 5.7.893 instead of the OTA. I'm just stating that I won't be flashing 5.7.893 and will just update the actual OTA (5.5.893). I'm aware he was mistaken.
[Motorola Droid Bionic] dagostin:
If you applied the leaked 5.7.893 update there is no way at all to apply the official ota of 5.5.893. the leak updates your kernel and that makes the ota fail. at this time there is absolutely nothing you can do to work around the kernel mismatch.
[Motorola Droid Bionic] Terri M:
You can find your way back so that you can take the OTA. Follow the instructions that p3droid has posted here: http://www.mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path.html

I can personally testify that this works, because that is what I did to my phone last night. You can also use the forever root method from here: http://droidmodderx.com/bionic/too-easy-unbrick-bionic-with-oneclick-fastboot-restore/

Remember to hit the "Thanks" button when someone helps you!
[Motorola Droid Bionic] audiomixman:
Are there any advantages to "downgrading" to 5.5.893 OTA from leaked 5.7.893?
[Motorola Droid Bionic] skullvet:
How did you get the OTA to install from multiupload? I tried via stock recovery and cwm. I got my radio back to stock, but cannot get the ota flashed.
[Motorola Droid Bionic] open1your1eyes0:
Can anyone else confirm if this is true?
[Motorola Droid Bionic] skullvet:
If Rumpy will post how he was able to get the OTA to flash manually after rolling back the radio, then I should be able to do the same thing. I am back to stock from the leak, with the stock radio and leaked kernel. My OTA fails via the auto method, CWM method and stock recovery method. I am rooted and haven't messed with any .apks or my webtop.
[Motorola Droid Bionic] open1your1eyes0:
It seems like the kernel is the only thing that can't be returned to stock (which is why the OTA fails). I want to see if anyone else can confirm this first.
[Motorola Droid Bionic] SamuriHL:
What I'd like to find is the radio from 5.5.893. I think if we had that, we could find a way to get back on the upgrade path going forward. But so far, I've not been able to find it.

Baseband 5.5.893: CDMA_n_03.1C.57r LTEDC_U_05.15.01

Baseband 5.7.893: CDMA_n_03.1C.57r LTEDC_U_05.15.02

The kernel and webtop appear to be the same. My theory is if we could downgrade the radio, we could then use one of the 5.5.893 CWR images floating around to get back on the upgrade path. There's a signed radio for 886 to get back to stock, but, that won't help us. We need the kernel and radio to match 5.5.893 to guarantee being able to upgrade in the future.
[Motorola Droid Bionic] skullvet:
Has anyone else been able to get the OTA to take after going back to stock with the leak?
[Motorola Droid Bionic] smokedkill:
I used R3L3AS3DRoot and was then able to download the ota.
[Motorola Droid Bionic] dagostin:
If you applied the 5.7.893 leak there is no way to apply the officially released update. the update fails on checking the kernel and there is no current way to revert the kernel. for now just have to wait it out.
[Motorola Droid Bionic] open1your1eyes0:
Why do I feel like this is just not true? What is preventing the kernel from being flashed?
[Motorola Droid Bionic] wseyller:
The locked bootloader
[Motorola Droid Bionic] open1your1eyes0:
Why are we able to flash system and boot images then using fastboot? And what about the stock FXZ?
[Motorola Droid Bionic] open1your1eyes0:
***DO NOT DO THIS AT ALL I HAVE LEARNED THE HARD WAY***

See here​

The kernel is located in the boot partition (boot.img). Which is indeed flashable even if the bootloader is locked (shows how much certain don't know). The only thing is you can't do because of the bootloader is flash custom kernels (you must use stock Motorola ones). Not a problem here :)

Flashing the FXZ + fastboot files (located here) + the radio files posted here should bring everyone back to a completely stock build and will then enable you to recieve OTA updates that should not fail. (FYI, start with radio files first by using CWM).

Please confirm if this works for you.
[Motorola Droid Bionic] filthy1:
Has anyone tried this to see if it works?
[Motorola Droid Bionic] superdan2481:
Oh wow who's brave enough to try this? The radio is confirmed to flash back to stock, who's willing to try this? I'd like to try this but I'm at work right now, i know RSD lite wouldn't work maybe fastboot?
[Motorola Droid Bionic] open1your1eyes0:
You'll have to use all three. Radio first through Clockwork flash, then full FXZ with RSDLite, then fastboot system.img and boot.img files. I currently don't have my Bionic on me at the moment but I will do so tonight if no one wants to beat me to it first.
[Motorola Droid Bionic] Character Zero:
I wonder if you would want to try the fastboot flash of the boot first, that way you aren't stuck with the old radio if that fails. We know the radio flash does work.
[Motorola Droid Bionic] open1your1eyes0:
This is true but if it does work then once you're done with the FXZ and fastboot you would have to reroot and install the bootstrapper and CWM just to flash the old radios again. This save you the steps afterwords if you flash the radios first.
[Motorola Droid Bionic] Character Zero:
Ahh I see what you are saying. Well I hope this works, and if it does can you post instructions just to be sure?
[Motorola Droid Bionic] open1your1eyes0:
Will do! I will try so tonight. :)
[Motorola Droid Bionic] SamuriHL:
I'm not trying to rain on anyone's parade, especially since I'm in the same boat (5.7.893), but, I can promise you that you don't want to do this. I've already tried. It's a bad, BAD idea. The FXZ will fail, and leave you in an AWESOME state of booting to a "flash failed" message every time you turn on the phone. I was lucky enough to get rid of that annoyance by restoring system using fastboot and then recovering my CWR image back to 5.7.893. However, it will *NOT* downgrade a kernel for you. No one has been successful in this yet.

My mission is to find the darn radio from 5.5.893 so I can flash that and system. Since they use the same kernel and webtop, this SHOULD put us back on the upgrade path going forward. The radio from 5.7.893 is one version higher than from 5.5.893, but, the kernel and webtop are the same.

In any case, I HIGHLY advise people against trying this. You will not succeed in downgrading the kernel and will simply cause yourself a massive headache.
[Motorola Droid Bionic] cellzealot:
The radio images are right in the update.zips, but the problem is you can only flash the radio with a signed file even if the image itself is the same.

The reason that you can revert to the original radio with the zip that has been posted is because that is the signed update.zip file from inside the radio.img contained in the full XML.zip(FXZ). That file runs after the rest of the images are flashed in fastboot, then it reboots into recovery to flash the radios.

We don't have such a file for just the radios for 5.5.893 or the subsequent MR-1 update and will likely have to wait until another full XML.zip of the current OTA is released or another update that does not assert those components in the same way as previous updates have.

This is the only way I can see that will allow those of us on the leaked files to get back on the official path.

Fixing the boot failure(S) error is a simple matter of flashing the device_tree.bin with fastboot and then rebooting. The phone will then boot normally again.

I completely agree with the above warning to not bother trying this unless you want to go all the way through the process to get back to 5.7.893, which actually seems to have the best performance for me.

It has been tried by many users many different ways and reverting the boot.img has not been successful by anyone.

YMMV.
[Motorola Droid Bionic] open1your1eyes0:
So the skeptic in me decided to take the plunge (extremely foolishly thinking this is an HTC device and I will be able to revert anything I mess up).

So I flashed the 5.5.886 radios first use the stock recovery (CWM doesn't work apparently) and that worked out fine they flashed with success. Next step I tried the FXZ...fail...it wouldn't even flash the first file cdt.bin.

Then I decided to extract every file out of the FXZ and, thinking that fastboot would flash them either way, decided to flash them there......

Oh that I was quite mistaken about.....

Apparently, Motorola are such jerks that they straight up wrote code (aside from the bootloader) to prevent downgrading certain core partitions (like cdt.bin, radio, recovery, and boot.img which has the kernel). However I was able to restore a lot of other minor partitions as well as webtop and system and preinstall partitions.

Now at this point I'm kind of expecting that the OTA would fail since the kernel isn't stock (and I was right). :/

So then I decided to forget the whole thing and go back to 5.7.893.

And here lies my punishment...

Everytime I try to flash the 5.7.893 leak from stock recovery, it fails...because my kernel is already 5.7.893 (even though my radio, system, and most other partitions are still stock).

Now, no matter what I do I can neither go back to full stock 5.5.886 (because the 5.7.893 kernel cannot be downgraded in fastboot), nor can I go back to a full leak 5.7.893 (because there is no file to restore 5.7.893 radios).

Basically, at this point, it appears I am officially screwed, as no OTA (leak or official) will flash since I cannot be on any complete build due to the remaining unflashable partitions.

If anyone seriously has a way to remedy this (at least to revert back to full 5.7.893 including the radios, or the new full 5.8.894), I will more than gladly appreciate it.

Otherwise, current status: royally screwed! :mad:
[Motorola Droid Bionic] SamuriHL:
*SIGH*. No, you are in fact completely screwed for the moment. :( By flashing the radio, there's no getting back to a full OTA *OR* leak unless someone manages to find a signed radio for 5.7.893. And I learned first hand that once we're off the upgrade path, we're pretty much screwed because I can't get 5.9.901 to flash over 5.7.893, either. Basically once you touch the boot image, you're done. :( In your case it's even worse because you're caught in limbo between stock and leak. UGH!!!! I wish I had some advice or you but unfortunately, that's a really nasty place to be right now.
[Motorola Droid Bionic] open1your1eyes0:
I know.....perhaps if I didn't flash those radios I could have reverted back to my 5.7.893 CWM backup and somewhat have gotten on the path again in a future OTA...but yeah...my device is now official an eternal OTA soft brick (until new files arrive at least) (5.7.893 FXZ or newer is needed?).

My question is where did that guy get that 5.5.886 Motorola signed radio.zip file? It's not located in the FXZ and that's the only restore file that I'm aware is available right now.

My theory is maybe we can find a 5.5.886 signed boot.zip (boot.img with kernel) to revert to stock or 5.7.893 signed radio.zip to restore the leak because stock recovery seems to downgrade/upgrade partitions that you can't normally flash with fastboot as long as they are using signed Motorola zip files (this obviously works because you're allowed to downgrade the radios in stock recovery but not fastboot).
[Motorola Droid Bionic] SamuriHL:
Yea, it remains to be seen what's going to happen here on out. I agree that if you can find a signed radio you can get back to full 5.7.893 and STAY THERE until an official solution is found. :) But I haven't seen a signed radio for anything except stock. :(
[Motorola Droid Bionic] open1your1eyes0:
Any idea where that 5.5.886 signed radio originated from?

Sidenote: I wish Motorola didn't stop using SBF's. :(
[Motorola Droid Bionic] SamuriHL:
I have no idea where the radio.zip came from. I found it posted and grabbed a copy. But I have not flashed it nor will I. Without a matching boot image, well, you already know. sigh. :(

The FXZ or whatever it is doesn't quite cut it, no.
[Motorola Droid Bionic] open1your1eyes0:
Well I guess I'll just have to choose what broken OS I want to stay on then.

What do you recommend?

5.5.886 with updated kernel but matching radios

or

5.7.893 with downgraded radios but matching kernel
[Motorola Droid Bionic] wingrider1964:
http://xdaforums.com/showthread.php?t=1279825

Not sure if this helps, noob here, just trying to learn, but I used option 5 here and installed the cheesecake.apk and got the OTA update and now sytem version 5.8.894.
[Motorola Droid Bionic] SamuriHL:
Uhhhh, do I have to choose? :D That's a sucky set of choices!! LOL! Honestly if I found myself in that situation I'd revert back to 5.7.893 if possible. Even with the old radio, it's probably still better matched than stock with an updated kernel.
[Motorola Droid Bionic] cellzealot:
The signed radio.zip came from the FXZ as I explained above. If you look at the FXZ you will see a radio.img in it with the other image files. If you open that radio.img with a hex editor that supports disk images, you will find an ext3 file system that contains an update.zip. That update.zip has a script to run it in recovery after the other image and bin files have been flashed with fastboot. This is because fastboot cannot flash the radios properly so they set it up to run in recovery.

When and if another FXZ is leaked of the current OTA or a later build that contains all of the signed complete images, it will also have current radio images in a signed zip file like the last one. Then we will have all the required components in the right form to restore them with.

Until then, unless they release another update that does NOT assert those components in the script we are stuck with the leaked cheesecake builds.
[Motorola Droid Bionic] open1your1eyes0:
True. At this point I just care about being able to use the OS with as least issues as possible.

You are right. I went back and reread your earlier post. Makes sense to me now. That radio.zip was basically just extracted from inside the radio.img file located in the FXZ.

Oddly enough though you mention that fastboot cannot flash the radios. I was able to flash the radio.img directly in fastboot, didn't give me any errors.
[Motorola Droid Bionic] SamuriHL:
Ahhhh, that makes perfect sense. I looked in the FXZ but didn't see the radio.zip. Now I get how it was found.
[Motorola Droid Bionic] mjforte:
Man this whole situation just sounds horrible. If Motorola didn't lock bootloaders we wouldn't be in this mess.
[Motorola Droid Bionic] SamuriHL:
Completely understandable. That's why I say I would personally go with 5.7.893 if I were in your situation.

Except that if you look at the version after you do that, it won't actually flash it. I've tried and thankfully it said it succeeded but never did anything.
[Motorola Droid Bionic] open1your1eyes0:
Well.....you live and you learn. Just helps reaffirm my choice to move away from Motorola devices. I couldn't be happier using my Galaxy Nexus right now. It's such a beautiful thing when NOTHING is locked down. :)

I just want to restore this Droid Bionic now for selling purposes (and so people don't complain to me when they can't receive an OTA).
[Motorola Droid Bionic] SamuriHL:
Or if we weren't impatient and didn't flash leaked updates we wouldn't be in this mess, either. :) I definitely take responsibility for what I've done to my phone. I'm just looking for a way out of it so I can consider it a lesson learned and not do it again.

"Don't touch the stove it's hot."

Bah, that's crazy talk...."OUCH! That stove is hot!!!"

"Dumb@$$"

:D
[Motorola Droid Bionic] open1your1eyes0:
Oh ok, I never actually checked to confirm in the OS. I just assumed since no errors were given.
[Motorola Droid Bionic] SamuriHL:
Assumption is the mama of all screwups. Or something like that. :D Wait, is that why you think the radio is stock? If so, find a way to get 5.7.893 back on that thing and you should be fine and all matched up. Leaked update, yes, but, no worse off than the rest of us.
[Motorola Droid Bionic] open1your1eyes0:
No no lol, I actually MADE SURE by doubling up and flashing it in stock recovery as well. So yeah, I wish that was all I did was in fastboot. :o
[Motorola Droid Bionic] cellzealot:
Did the phone boot into recovery afterwards to install the radios?

That's how it works, unless I am misunderstanding your post. The radio.img is not the radio itself. I contains both the bp.img and lte.img files in the update.zip.

Again, I am very willing to be proven wrong about this but that is my current understanding of how it works.

Edit: I type too slowly and I see where your confusion arose now...and I also agree that this is entirely our responsibility to deal with having loaded files we basically stole from Motos test servers.

I also believe that they are well aware of that situation and will find some way to tacitly allow us to get back on the official path. It is in their interests to do so and will save them from enduring another outcry over this very troubled device.
[Motorola Droid Bionic] open1your1eyes0:
Nope didn't do anything afterwords.

I just extracted all the files from the FXZ and tried flashing each one manually (some failed and some went through).

Just did "fastboot flash radio radio.img". Said "OKAY" and just stayed in fastboot.

Sidenote: I even tried something crazy to try to restore 5.7.893 radios (although I knew there was no chance it would work, I thought what the hell...). I found bp.img and lte.img in the 5.7.893 update.zip file and manually extracted them and overwrote the ones in the 5.5.886 radio.zip file that was posted. Tried to flash it in stock recovery but yeah....failed because it said it wasn't a signed file now. :/
[Motorola Droid Bionic] SamuriHL:
Oh, HELL! Place your bets! :D Man that sucks.
[Motorola Droid Bionic] open1your1eyes0:
Well whatever...at this point...I've accepted the fate of this device. Going to try to see if I can mess up the OS and play dumb and RMA it with Verizon or Motorola. If they won't take it then I'll just reroot 5.5.886 and flash as much as I can back to 5.7.893.
[Motorola Droid Bionic] SamuriHL:
Stupid question time. Have you tried the full signed 5.7.893 update in stock recovery to see if it will flash? To do that you'd want to put as much back to stock as possible. I'm fairly sure it'll fail because of the boot image, but, hey, it's worth a shot.
[Motorola Droid Bionic] cellzealot:
You can flash the full 5.7.893 update over the hybrid 5.5.886 system with the updated boot.img and radios from 5.7.893. I have done so at least 3 times while attempting various things to revert. You can also flash the 5.7.893 update back over itself. The asserts are setup to accept either the stock release signed components or the updated signed components, but nothing in between.

Edit: You must use stock recovery for the OTA updates, they fail in CWM.
[Motorola Droid Bionic] open1your1eyes0:
This is very strange. I have EXACTLY tried this method to restore 5.7.893 but it fails for me everytime. I assumed it was cause I didn't have a complete 5.5.886 image. Maybe I'm using the wrong file? Can you point me in the right direction here?

Current Status of device

: Everything that was flashable including radios is now 5.5.886.
[Motorola Droid Bionic] SamuriHL:
http://xdaforums.com/showthread.php?t=1327537

See there. Try that first in stock recovery.

If not, I would try going back to stock system with releasedroot and then try updating again in stock recovery. What have you got to lose at this point? :)