Database Users

Masonry at it's finest, Sierra Beautiful Foothills Brick

It is with great humility and panic that i request the god's to bestow upon me the greatest of the Beautiful Sierra Foothill's treasures of the two.two variety. I too have been taken captive by the new bootloader's key's. Is there a gentle soul willing to help one in need.
in all seriousness i can find much less expensive paperweights, any help would be extremely appreciated. ill be looking at that PM box.

Suchanicebrickihave said:
It is with great humility and panic that i request the god's to bestow upon me the greatest of the Beautiful Sierra Foothill's treasures of the two.two variety. I too have been taken captive by the new bootloader's key's. Is there a gentle soul willing to help one in need.
in all seriousness i can find much less expensive paperweights, any help would be extremely appreciated. ill be looking at that PM box.
Click to expand...
Click to collapse
Did u try the /system 2.2 "SBF" with RSDlite 4.8 on mydroidworld.com?
It works as long as you did not update to the 2.2 OTA, and THEN try the 2.1 SBF first.

Unfortunately, i was tinkering with the 2.2 OTA, botched it and was recovering to 2.1, hey I've done it about three hundred times, no big deal right. *sigh* I also have tried the partial image to no avail. I'm pretty much toast unless someone takes pity upon me.
I can play the "OTA killed my phone" routine at Verizon and exploit their internal memo but i would rather be able to fix my problems and stay under the radar. no reason to become a statistic supporting why moto wanted to keep us out anyway.
on the bright side i finally got a user name for the XDA forum. Always carrying the name to remind me not to be too quick to do things. Measure once and cut twice right...
Edit:
the droid 2 uses the OMAP3630 chip as well. Does anyone think the hardware is similar enough to use firmware from the D2?
Edit2:
thank you for the quick response.

Suchanicebrickihave said:
Unfortunately, i was tinkering with the 2.2 OTA, botched it and was recovering to 2.1, hey I've done it about three hundred times, no big deal right. *sigh* I also have tried the partial image to no avail. I'm pretty much toast unless someone takes pity upon me.
I can play the "OTA killed my phone" routine at Verizon and exploit their internal memo but i would rather be able to fix my problems and stay under the radar. no reason to become a statistic supporting why moto wanted to keep us out anyway.
on the bright side i finally got a user name for the XDA forum. Always carrying the name to remind me not to be too quick to do things. Measure once and cut twice right...
Edit:
the droid 2 uses the OMAP3630 chip as well. Does anyone think the hardware is similar enough to use firmware from the D2?
Edit2:
thank you for the quick response.
Click to expand...
Click to collapse
I would stay away from the Droid 2 firmware, imo.

yeah, but what i do i end up with a more bricked phone
there's only one step down from motobrick as long as it's not on fire i dont think i've gone to far back. i probably wont but I've literally been searching for the sexy beautiful fantasy since the first post... I'm determined the closest I've found is a dead RS link.... i wish moto would supply me with the tools to fix my phone without costing them money and my time.
seriously though the Droid "Motobrick" model is sweet...
sleek sexy and just enough to hold my physics homework down... seriously that what its doing right now... that ampad paper likes to fly away.
edit:
well i dont think ill find a valid SBF on the internets so i might as well try before i try to bring it back to Verizon... i called a random store asking if they the SBF on site and the tech on the phone... well lacked the required knowledge to be of help. I'm sure they wont have the wherewithal to know what happened to that poor droid of mine . I'll let you guys know how the droid2 flash works and/or the Verizon visit

[WIP] Porting Clockwork Mod to Bravo

Hey all, I talked to koush and he said he was ok with me porting his Droid2/X/Pro bootstrap to the motorola bravo.
Basically it will work the same way as on those devices, you load the bootstrap app on the phone, and reboot into recovery. the phone reboots and clockwork mod then loads and you can install .zip's (like the gb keyboard, etc) do nandroids, install rom's etc.
you cant install custom kernels because of the locked bootloaders on these devices, this is the only drawback.
I am going to need some testers and even better if someone could get me the SBF file for this phone that would be so awesome. Its gotta be easy to find, its been out for a while and its an old software 2.1-update1 that i think is the same since release. Please let me know!
if you want to follow my work or help my github is :
https ://git hub.com/bandroidx - put the space back between git and hub i cant post links either
This should work with 2.2 so even if it drops soon, that is a ok. That wont make this project any less important, we need a way to get a custom recovery booted no matter what.
Update 2/19/11 - I hope to have a testable version done by the end of my long weekend (have off monday) will need testers very soon so keep in touch if your serious about testing. Anything I release will be a confirmed working on atleast 1 device (my gf's) build hopefully.
4-20-11: In final development, release imminent.

Ok i am almost ready for testers. You will need android sdk tools w/ adb and your phone must be rooted.
I need to finalize a few things, a sbf would really help, doesnt someone work for at&t and can get this?

Sent you a PM, but I can't tell if it actually was delivered. Please let me know if you got it. I am interested in testing my Bravo, but naturally, have some reservations. Thanks.

i am so limited by this 10 post thing, hopefully i get out of it fast.
i am trying to test it on a bravo emulation i got going in the simulator too, its being problematic but my gf has a real bravo for me to test on
an sbf would be nice, anyone?

i am asking some people for a sbf, maybe i can see about making a system only sbf like they did for the dx, that might work too.
MODERATOR please approve me so i can post in dev forums! argh!

I have talked to some people about an SBF and havent found anything yet. Someone must work for at&t or moto and can get this, all their stores have it probably to reflash phones.
But until then I need someone who is willing to risk bricking their phone because they are sending it back for warranty work. Yes it could void your warranty but I have never heard of this, we bricked a **** ton of droid x's before we had an sbf and had no problems.
Even better would be someone who is sending it to insurance to rpelace it because of a broken screen or something, that would be a great test unit.
So ask around, find someone for me, I should have a working test very soon.

bandroidx said:
I have talked to some people about an SBF and havent found anything yet. Someone must work for at&t or moto and can get this, all their stores have it probably to reflash phones.
But until then I need someone who is willing to risk bricking their phone because they are sending it back for warranty work. Yes it could void your warranty but I have never heard of this, we bricked a **** ton of droid x's before we had an sbf and had no problems.
Even better would be someone who is sending it to insurance to rpelace it because of a broken screen or something, that would be a great test unit.
So ask around, find someone for me, I should have a working test very soon.
Click to expand...
Click to collapse
P3Droid seems to be really good at getting his hands on leaked Motorola files. I've asked if he could get a Bravo SBF but was ignored. Since you are actually doing something productive, maybe he would be more apt to respond to you.

bandroidx said:
Ok i am almost ready for testers. You will need android sdk tools w/ adb and your phone must be rooted.
I need to finalize a few things, a sbf would really help, doesnt someone work for at&t and can get this?
Click to expand...
Click to collapse
Ok, I am willing and able to aid you in any way I can with my bravo. it is rooted and ready to go. I do work for AT&T but only in sales and customer service, so I don't have hands on access to the .sbf for the phone. But if you know of any means for me to get it or request it, i.e. the rout or channel I should attempt to get it, that would be great. Thanks so much for your effort in this and let me know if there is anything I can do.

MisterKrispy said:
P3Droid seems to be really good at getting his hands on leaked Motorola files. I've asked if he could get a Bravo SBF but was ignored. Since you are actually doing something productive, maybe he would be more apt to respond to you.
Click to expand...
Click to collapse
Thanks its a good idea, as I already tried it
He cant get it, he only gets vzw.
his reply "@bandroidx I doubt it, no connects outside of VZW/Moto"
if you want to follow me on twitter i am @bandroidx

MCFarmfresh said:
Ok, I am willing and able to aid you in any way I can with my bravo. it is rooted and ready to go. I do work for AT&T but only in sales and customer service, so I don't have hands on access to the .sbf for the phone. But if you know of any means for me to get it or request it, i.e. the rout or channel I should attempt to get it, that would be great. Thanks so much for your effort in this and let me know if there is anything I can do.
Click to expand...
Click to collapse
Thanks, I am not sure how At&t is but with verizon they have tech support in the stores so someone can bring a bricked phone in and get it fixed (or replaced) while they wait, etc. Does AT&T work the same way? In that case, you could contact someone at the store and get it with a good story to the tech guys. they usually are underpaid and younger kids at vzw and will easily obey any request from corporate imo. I am fairly sure this how most sbf's get out, unless its from like an inside engineering dept or from the manfucaturer themselves but those are problably more rare.
Thanks a million if you can get this that would be great. Otherwise i think we need to hope for someone with a broken screen ,etc that is getting a replacement. I would not want to brick someones perfectly good phone with no way to recover. It happens, even with the best testing and coding.

bandroidx said:
Thanks, I am not sure how At&t is but with verizon they have tech support in the stores so someone can bring a bricked phone in and get it fixed (or replaced) while they wait, etc. Does AT&T work the same way? In that case, you could contact someone at the store and get it with a good story to the tech guys. they usually are underpaid and younger kids at vzw and will easily obey any request from corporate imo. I am fairly sure this how most sbf's get out, unless its from like an inside engineering dept or from the manfucaturer themselves but those problably more rare.
Thanks a million if you can get this that would be great. Otherwise i think we need to hope for someone with a broken screen ,etc that is getting a replacement. I would not want to brick someones perfectly good phone with no way to recover. It happens, even with the best testing and coding.
Click to expand...
Click to collapse
I think I know a way to get it. Now att does warranty exchanges is they send you a new or refurbished device and you send the broken one back to them when you get it. However, there is one store in my state that doubles as a warranty device exchange center. Basically if you don't want to wait on your device in the mail you can get it replaced there. I think that would be the only store that would have the files. I just need to think of a good excuse for them to put it on a flash drive for me or to email it to me. I think they would be more about to do it if they new I worked for att and I had a good enough excuse. I'll let ya know what I can find out.

MCFarmfresh said:
I think I know a way to get it. Now att does warranty exchanges is they send you a new or refurbished device and you send the broken one back to them when you get it. However, there is one store in my state that doubles as a warranty device exchange center. Basically if you don't want to wait on your device in the mail you can get it replaced there. I think that would be the only store that would have the files. I just need to think of a good excuse for them to put it on a flash drive for me or to email it to me. I think they would be more about to do it if they new I worked for att and I had a good enough excuse. I'll let ya know what I can find out.
Click to expand...
Click to collapse
Awesome let me know, that is def. a good idea. On a phone that has been out for so long and the SBF is for released software so even though they dont let them go out in the wild openly, they are quite available. [mbm] was surprised that its not out yet for a phone released that long.
Some other good news just incase, i talekd to p3droid again and explained what i was doing in better detail and he is going to try to find this for us. He said he will shake the tree and see what falls out or something to that effect. But its at&t and not vzw, so def. still try to get it if you can without getting fired!
Just never admit you want it to release it or that you released it. I will help you release it to cover you and insulate you further if you want. I will load it up on my french seed box

Ok good news people, I have made great progress on this and hope to have a testable copy ready as soon as this weekend! If i can spend enough time to work out a few things then I could have it ready to test sunday or monday. I am working out ways to test it as safely as possible.
Tenfar who ported CWM to the Defy is helping me on the project, we have found the phones are more alike on the inside than anything else, so his help has been invaluable and thanks to him this is really looking to be something that will work out.

bandroidx said:
Ok good news people, I have made great progress on this and hope to have a testable copy ready as soon as this weekend! If i can spend enough time to work out a few things then I could have it ready to test sunday or monday. I am working out ways to test it as safely as possible.
Tenfar who ported CWM to the Defy is helping me on the project, we have found the phones are more alike on the inside than anything else, so his help has been invaluable and thanks to him this is really looking to be something that will work out.
Click to expand...
Click to collapse
If you have a system SBF to test at some point, please let me know. I'll be happy to test it for you.

bandroidx said:
Ok good news people, I have made great progress on this and hope to have a testable copy ready as soon as this weekend! If i can spend enough time to work out a few things then I could have it ready to test sunday or monday. I am working out ways to test it as safely as possible.
Tenfar who ported CWM to the Defy is helping me on the project, we have found the phones are more alike on the inside than anything else, so his help has been invaluable and thanks to him this is really looking to be something that will work out.
Click to expand...
Click to collapse
bandroidx, was just checking in to see if you got my PM. I actually sent two because after I sent each one it said I had 0 sent messages. If not I'll shoot ya an email. Thanks.

Yes i got your pm and just replied.
I have a testable apk but it hasnt been tested yet. I am unable test it on the emulator but am working on other ways to test it.
the good news is i built the whole thing with help from the guy who ported CWM to the defy which is very similar and he thinks it looks good.
basically waiting on a sbf or someone with a device going back for replacement that can boot into the os and run an app (broken scren probably would be good)

OK i have the recovery ready to testi it will be first come first serve for testers. I will be back online around 10pm EST monday night to find some testers. send me your gtalk around then if your interedted.
bandroidx

CWM port to Moto Bravo
I too work at At&t and have an able and willing Bravo to put on the line for the sake of testing, if you still need help, I did use the CW for my Aria, so I have a little experience with it. Good luck, and I hope you guys get this thing going. I'm ready to throw Cyanogenmod on this baby!

apples2droids said:
I too work at At&t and have an able and willing Bravo to put on the line for the sake of testing, if you still need help, I did use the CW for my Aria, so I have a little experience with it. Good luck, and I hope you guys get this thing going. I'm ready to throw Cyanogenmod on this baby!
Click to expand...
Click to collapse
I have a testable copy that is using code confirmed working on the defy so should be good.
If you want to try it, there is some risk of bricking or needing sbf (which we dont have) but it should be recoverable in most scenarios because of the way the hijack works, all you need is a rooted phone.
if someone goes wrong it should go back to normal on next reboot.

bandroidx said:
I have a testable copy that is using code confirmed working on the defy so should be good.
If you want to try it, there is some risk of bricking or needing sbf (which we dont have) but it should be recoverable in most scenarios because of the way the hijack works, all you need is a rooted phone.
if someone goes wrong it should go back to normal on next reboot.
Click to expand...
Click to collapse
Hi , I have a bricked Moto Bravo, that is boot looping
So...
I'll be happy to test the sbf and report back
got a link for DL ?

Simple Un-Root!

Un-root And update download the file from here: http://forum.xda-developers.com/showthread.php?t=975888 and apply. This will give you stock and S-on.
That simple!

Thanks for the info, but the fun is just beginning. This is always good to have just in case you have to return it.

You should be able to load any stock RUU. As long as the hboot and the recovery exist in the RUU, it should return you to a stock condition.

Jaywan, how about a simple root and s-off?

It's simple to make a app run the commands needed to make a one click rooter. And easier to edit a already working rooter to work for this phone. Idk why he don't want the one click released. Took me 30 minutes to root.. maybe he only want people to root using his method. I not gonna step on his toes by posting one tho...
Sent from my ADR6400L using XDA Premium App

ok ok, I hear yah. I will just bite the bullet and type in all 90 of the commands tomorrow when I get off work.

BTW, I left the MT4G and came over to verizon also. I went to the SGS4G before I left tmobile. Lack of dev support for that phone made me give it up. Thanks for coming over to the Thunderbolt.

also, take a look at this thread I started. Somethings up with this one click unroot deal.
http://forum.xda-developers.com/showthread.php?t=1004567

Jaywan said:
It's simple to make a app run the commands needed to make a one click rooter. And easier to edit a already working rooter to work for this phone. Idk why he don't want the one click released. Took me 30 minutes to root.. maybe he only want people to root using his method. I not gonna step on his toes by posting one tho...
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I heard him meantion he wants people to learn adb so if something happens further down the line they can use it
Seriously I'm with him, the hardest part about adb for me was getting it installed. The root was easy and took 30 min
sent from my Thunderbolt

For what its worth, he said feel free to post the one clicks, just give credit. I dont honestly care however, copy, paste, seemed simple enough. Was no where near as hard as the original root method for the DInc.
Sent from my ADR6400L using XDA App

The only legitimate reason I could buy about not wanting a one click released, is if SOMEHOW it would make our phones vulnerable to some sort if attack.
As background, I've ben using custom roms since my old g1 was new and JesusFreke was just getting started and I dont ever recall ANY dev with holding something that would make the users lives easier. In recent history I've done a ton of flashing roms with both mine and my wifes old vibrants and the only time I used adb was if I wanted to push a file to the phone without mounting it on my computer.
PERSONALLY, this whole mess sounds of ego and elitism. I am incredibly greatful to the devs who have paved the way, but fearful of what they are trying to do. No one should have the right to prevent another from releasing something, it's in gross violation of the gpl. If a dev wants to code something under a different license, fine. However it needs to be clearly annotated as such, and devoid of any gpl work itself. In other words, it basically can't contain anything related to android unless it was developed 100% blind through an emulator.
Sent from my ADR6400L using Tapatalk

Can't step on my toes, I got stealtoe boots...
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
I want proper md5sum verifications, I want proper warnings, etc.
I already stopped the release (until fixed) of one 1click root that would of been REALLY bad for the community and anyone using it.
Ppl need to stop blaming me for this crud.

ShanDestromp said:
The only legitimate reason I could buy about not wanting a one click released, is if SOMEHOW it would make our phones vulnerable to some sort if attack.
As background, I've ben using custom roms since my old g1 was new and JesusFreke was just getting started and I dont ever recall ANY dev with holding something that would make the users lives easier. In recent history I've done a ton of flashing roms with both mine and my wifes old vibrants and the only time I used adb was if I wanted to push a file to the phone without mounting it on my computer.
PERSONALLY, this whole mess sounds of ego and elitism. I am incredibly greatful to the devs who have paved the way, but fearful of what they are trying to do. No one should have the right to prevent another from releasing something, it's in gross violation of the gpl. If a dev wants to code something under a different license, fine. However it needs to be clearly annotated as such, and devoid of any gpl work itself. In other words, it basically can't contain anything related to android unless it was developed 100% blind through an emulator.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Are you a troll or do you really believe all that crock you just posted?
The issue with one clicks was an increased risk of bricking with this method. And where does the GPL even come in here at, any GPL code we used as released before the root was even up.?
I stopped a one click from being released today that not only left your phone vulnerable to an attack, but also left you with an outdated, faulty radio and other faulty firmware.
Either you are a troll, have a personal issue with me, or have a seriously problem.

jcase said:
Can't step on my toes, I got stealtoe boots...
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
I want proper md5sum verifications, I want proper warnings, etc.
I already stopped the release (until fixed) of one 1click root that would of been REALLY bad for the community and anyone using it.
Ppl need to stop blaming me for this crud.
Click to expand...
Click to collapse
omfg most of us been rooting since g1 came out THE FIRST DAY come on if modaco was working on this aka paul. like his app visionary he would have it out.... who cares most of us know adb... but i dont want to turn s off i just want root access to remove **** and do a couple mods. why is this such a big fuc88ing deal just release the app and we will all be grateful of who release one click root

jesemalave1 said:
omfg most of us been rooting since g1 came out THE FIRST DAY come on if modaco was working on this aka paul. like his app visionary he would have it out.... who cares most of us know adb... but i dont want to turn s off i just want root access to remove **** and do a couple mods. why is this such a big fuc88ing deal just release the app and we will all be grateful of who release one click root
Click to expand...
Click to collapse
o.m.g.
Dude it doesn't work that way on this phone. It is not the G1, z4/visionary/anyonphoneroot does not work, root REQUIRES adb (even with one click).
Fact is, you can't root this phone, temp or perm, one click or not, without ad.
If you can find a way, please do. We are awaiting your one click, root that does not use adb, and is not dangerous.
fyi one click has been released, hours before your post.
Code:
while (true) {
facepalm();
}

I'm going to cut out all your attacks, because you've clearly missed my point in its entirety and decided to get defensive.
jcase said:
The issue with one clicks was an increased risk of bricking with this method. And where does the GPL even come in here at, any GPL code we used as released before the root was even up.?
Click to expand...
Click to collapse
I brought the GPL in because like it or not, you don't have the right to say who can and cannot release anything regarding "one click" roots UNLESS you yourself made an essential piece of the current rooting method, that is in its entirety your own. To make an analogy, you can't patent (and thus control the distribution) to a Toyota Carolla, simply because you assembled the whole thing from spare parts. If you were to completely design and fabricate a motor vehicle without using off-the-shelf parts you WOULD have that right.
There is nothing personal in my view of this against you, I don't hold any grudges against anyone; but its the mentality here that irritates me, and it just happens that you're the one that posted it:
jcase said:
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
Click to expand...
Click to collapse
I understand you want people to learn; I really do. I've done enough work with computers that I too get really irritated at people who demand answers to questions answered much faster by doing a quick search. I also understand why you want to avoid screw ups because of a poorly made one click. HOWEVER, just because you WANT people to get them cleared through you first; does not mean they HAVE to or that you have a right to demand that they do.
jcase said:
I stopped a one click from being released today that not only left your phone vulnerable to an attack, but also left you with an outdated, faulty radio and other faulty firmware.
Click to expand...
Click to collapse
And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault.
The whole purpose of OSS is to allow freedom of ideas and development. I don't know how old you are, or what your experience with OSS outside of Android phones are; but I personally have seen PLENTY of OSS software that started out as utter crap, turn into wonderful software packages. Maybe you're old enough to remember KDE2 vs KDE4, or how about pre v1 Mozilla vs modern versions of Firefox.
I'm not some OSS nutter; I've got no problem with closed source or proprietary software; just a problem with others trying to control things they have no right to.
All that having been said, maybe you DO hold software rights related to some piece of the current rooting method. If so I've seen nothing indicating so, nor anything indicating that any part of the rooting method is not OSS; however if you DO, then you have my apologies, as you would indeed have control over distribution of that specific piece. You still would not be able to prevent distribution of any one click that were released provided they simply had users download your piece separately.

You are missing the point, and obviously did not read anything. This will be my last time wasting time with you until then.
I never said THEY CANT release, I asked them not to, until we had a safer way and time to check it out. Big difference. I stopped one from going out today that would of more or less ruined phones until someone fixed them.
Fact is, MOST of the one clicks I have seen lately, violate the GPL, why don't you go after them, or hell even better we could really use you to go after HTC (in all seriousness).
ShanDestromp said:
I'm going to cut out all your attacks, because you've clearly missed my point in its entirety and decided to get defensive.
I brought the GPL in because like it or not, you don't have the right to say who can and cannot release anything regarding "one click" roots UNLESS you yourself made an essential piece of the current rooting method, that is in its entirety your own. To make an analogy, you can't patent (and thus control the distribution) to a Toyota Carolla, simply because you assembled the whole thing from spare parts. If you were to completely design and fabricate a motor vehicle without using off-the-shelf parts you WOULD have that right.
There is nothing personal in my view of this against you, I don't hold any grudges against anyone; but its the mentality here that irritates me, and it just happens that you're the one that posted it:
I understand you want people to learn; I really do. I've done enough work with computers that I too get really irritated at people who demand answers to questions answered much faster by doing a quick search. I also understand why you want to avoid screw ups because of a poorly made one click. HOWEVER, just because you WANT people to get them cleared through you first; does not mean they HAVE to or that you have a right to demand that they do.
And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault.
The whole purpose of OSS is to allow freedom of ideas and development. I don't know how old you are, or what your experience with OSS outside of Android phones are; but I personally have seen PLENTY of OSS software that started out as utter crap, turn into wonderful software packages. Maybe you're old enough to remember KDE2 vs KDE4, or how about pre v1 Mozilla vs modern versions of Firefox.
I'm not some OSS nutter; I've got no problem with closed source or proprietary software; just a problem with others trying to control things they have no right to.
All that having been said, maybe you DO hold software rights related to some piece of the current rooting method. If so I've seen nothing indicating so, nor anything indicating that any part of the rooting method is not OSS; however if you DO, then you have my apologies, as you would indeed have control over distribution of that specific piece. You still would not be able to prevent distribution of any one click that were released provided they simply had users download your piece separately.
Click to expand...
Click to collapse

I agree!! If anyone is in violation of GPL license it is HTC.
And once we have that kernel source in the hands of the community amazing things will happen!!
Once the custom kernels start flying you will see the TB doing crazy things. I can only imagine 2GHz speeds or insanely efficient battery life (to name a few)!

ShanDestromp says "And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault. "
This has got to be the stupidest statement I have read in a long time, I can guarantee, If you used a 1-click method and it bricked your phone you would be screaming " where's the oversight in this forum, I cant' believe that that mods would allow faulty programming to be posted."
Jcase I for one am glad you are stepping up and doing what needs to be done to prevent a potential $750 brick, thank you sir.

jcase said:
I never said THEY CANT release, I asked them not to, until we had a safer way and time to check it out. Big difference. I stopped one from going out today that would of more or less ruined phones until someone fixed them.
Click to expand...
Click to collapse
I'm not privy to any private conversations, nor do I read every thread here on XDA, so my general impression, which I'm sure is shared based upon what others have said, was of a more explicit "No you cannot," not a "do you mind if I take a peek first". Furthermore, I did not name any one individual "responsible" for any blockade; I only began to interact with you once you brought yourself into the thread. Beyond that, if you go back to my original post, I explicitly thank the people who made root possible at all.
jcase said:
Fact is, MOST of the one clicks I have seen lately, violate the GPL, why don't you go after them
Click to expand...
Click to collapse
For starters I don't know much, if anything about them other than they exist. Unless I personally see something that I think is in violation, I assume good faith. I certainly don't seeking violations.
jcase said:
or hell even better we could really use you to go after HTC (in all seriousness).
Click to expand...
Click to collapse
I'm guessing you're referring to the fact that they didn't release the kernel source as expected this week? I'd mentioned it in another thread, though I don't recall which anymore; but from what I recall of GPLv2 developers have 60 days from the "official" binary release to provide source. To expand on that, HTC has 60 days from when the phone officially went on sale, to provide upon request the source code to any GPL licensed software, however it is version specific. That is to say 60 days from March 17th to make available the source to the firmware that was on the phone when released (since to the best of my knowledge there have been no other OFFICIAL firmware versions released).
Of course any such source will inherently exclude any third party proprietary software, for example if HTC used a closed-source bluetooth stack (not saying they did, just a hypothetical example). Additionally, there isn't any specific method to release stipulated. If HTC wishes they could mail out copies of the source on 3.5" floppies and still be within the rules; and all this assumes GPLv2 is how Android is licensed. If its v3 then I honestly have no clue if any time provisions exist.
I just want to reiterate, I have no ill-will to you nor anyone else. It appears as though the whole issue stems from miscommunication.

Kindle Fire OTA software update coming in less than two weeks

In the wake of many user complaints about web browsing speeds and other performance issues, Amazon has told the New York Times that it will be releasing a software update for the Kindle Fire "in less than two weeks." That timeframe would put this new software update about a month after the 6.2 update released at the end of November.
http://www.theverge.com/2011/12/11/...ta-software-update-coming-less-than-two-weeks

Oh God lol, now I have to root again....
Sent from my Kindle Fire using xda premium

Well hopefully this time it will be at least a worthwhile update. instead of a no visible difference update like the last one or take away a feature like the one before that.
Sent from my Kindle Fire using Tapatalk

Let's hope the Development get a solid kernel and Rom by then...I don't want to be stock when they update the bootloader and lock it down after all the returned rooted and bricked fires due to people testing kernels that didn't know what they were doing and then returning them.....
Sent from my ADR6400L using Tapatalk

Lets hope some concrete updates...... But wht about some hardware issues......
http://mirolta.com/2011/12/12/amazo...for-kindle-fire-to-encounter-critical-issues/

The OTA will be a non-issue as much as the 6.2 update was. Sure you might have to reroot but Big Deal! That took all of a 30 seconds to do again.
Stuff about Amazon changing to a locked bootloader ignores the fact that most people never root or modify their device. The ones that do are a very miniscule minority of the total users that have the unit. Besides, has any device manufacturer locked a bootloader for a device that was originally released as unlocked? I don't think so.
I bet a lot more units are returned due to some malfunction than due to some someone screwing up their unit trying to modify it.
My wife has her unit stock... no mods, no tweaks, just uses it the way it came. I have mine rooted, different launcher and tons of apps that I have loaded from Android Market or side loaded via other means. I think the device is great for the price.
People who use forums like this have a very skewed idea of how many people actually modify their devices... most never do, never know about it and don't even know forums like this.

krelvinaz said:
The OTA will be a non-issue as much as the 6.2 update was. Sure you might have to reroot but Big Deal! That took all of a 30 seconds to do again.
Stuff about Amazon changing to a locked bootloader ignores the fact that most people never root or modify their device. The ones that do are a very miniscule minority of the total users that have the unit. Besides, has any device manufacturer locked a bootloader for a device that was originally released as unlocked? I don't think so.
I bet a lot more units are returned due to some malfunction than due to some someone screwing up their unit trying to modify it.
My wife has her unit stock... no mods, no tweaks, just uses it the way it came. I have mine rooted, different launcher and tons of apps that I have loaded from Android Market or side loaded via other means. I think the device is great for the price.
People who use forums like this have a very skewed idea of how many people actually modify their devices... most never do, never know about it and don't even know forums like this.
Click to expand...
Click to collapse
Exactly ... That's a well explained post

Yeah, companies lock bootloaders for concrete reasons. They are not going to all of a sudden lock the device down a month after it was released just to mess with modders. Because that is literally the only thing it would do.
The Nook Tablet, for instance... I believe the reason the bootloader is locked is because they had to as part of an agreement with Netflix to provide higher quality streaming to the device. B&N decided that annoying the tiny minority of modders was worth it in exchange for high quality Netflix streaming - something that a much larger percentage of users can benefit from and of course an extra marketing bullet point for them to use.
I'm fine with them updating the device. Look at all the Android phones that don't get regular updates. All people do is whine about NOT getting updated! The KF is some great hardware for the price but it still has issues. Touchscreen responsiveness still needs to be improved, battery life REALLY needs to be improved, and they have to fix the sleep of death as well. I will GLADLY go through the hassle of re-rooting and re-installing the market if these things are fixed.
Of course I'd prefer to have a custom ROM so I can get updates without having to redo all that stuff, but it's only a matter of time.

please, dear god, let non-rooted users change the lockscreen wallpaper

Is there a way yet to block OTA updates (that is also easy to reverse)?
Don't want to be caught with my pants down by this update if it does more than anticipated ....

andTab said:
Is there a way yet to block OTA updates (that is also easy to reverse)?
Don't want to be caught with my pants down by this update if it does more than anticipated ....
Click to expand...
Click to collapse
Haven't read through it, but this post seems to cover it.

ryanlbowen said:
please, dear god, let non-rooted users change the lockscreen wallpaper
Click to expand...
Click to collapse
This. 10char

Also hoping for a clean re-root-only response to this update... I have it stowed away as a gift for my wife, and take it out at night to perform nerd-surgery. It would be great to not have issues right before holiday, as it's going to be enough fun explaining the different launchers, etc.

ReverseWolf said:
Also hoping for a clean re-root-only response to this update... I have it stowed away as a gift for my wife, and take it out at night to perform nerd-surgery. It would be great to not have issues right before holiday, as it's going to be enough fun explaining the different launchers, etc.
Click to expand...
Click to collapse
I have nothing to contribute to this, just lmfao at your analogy of what you do late at night. ;-)
Sent from my MB860 using XDA App

andTab said:
Is there a way yet to block OTA updates (that is also easy to reverse)?
Don't want to be caught with my pants down by this update if it does more than anticipated ....
Click to expand...
Click to collapse
Not the best solution, but it's easy: turn off wireless.
You don't need a widget for this, but it's nice. I recently installed a power control widget ( I used Widgetsoid ) to allow me to turn off wireless ( as well as adjust brightness, volume, toggle USB, and turn off GPS ).
Since I'm mostly content with my setup for now, I leave the wireless turned off to conserve battery and avoid the next update. I'd rather wait until I hear from the good folks here that the next update is OKAY before I turn on wireless and let it update. In the meantime, if I need wireless, I can check here just to be sure there is no update waiting to be pushed, flip on the wireless, do what I need, then turn it back off.
Like I said, it's not the best solution, but it works for me, and it's really simple.

ReverseWolf said:
Also hoping for a clean re-root-only response to this update... I have it stowed away as a gift for my wife, and take it out at night to perform nerd-surgery. It would be great to not have issues right before holiday, as it's going to be enough fun explaining the different launchers, etc.
Click to expand...
Click to collapse
Let me ask you something- same situation here.. My wife's just came in the mail today. I'd like to know more about device setup before said "nerd surgery" as I want to do a similar thing.. Did you login with your own amazon account or hers? If I login w/ hers I don't want her to get a "Congrats on your Kindle registration" type of email- as this is a surprise after all.. But- I'm also thinking that if I go ahead and login w/ mine- anything I do as far as loading apps, etc will be wiped out when she has to login w/ hers?
Sorry to be long winded- overall my main question is- Whats the best way to tinker/root/play with this thing w/o giving away any surprises or having to re-do work?

I'd leave it in the box. When my wife's came, she wanted it right away. It auto registered to MY account, not hers. Didn't add anything to it, it just happened.
I had to deregister it and then reregister it to her account. Doing so is like a default reset.
Also, it is going to auto update at least once as they come with 6.1 and 6.2 is the current. Might even be 6.3 or whatever the new OTA is by the time she opens it.

Do you remember if she got an email when you deregistered and assigned it to her account?

Dont recall. I don't read her email so I don't know and I did a quick check of my email and don't see anything either...

I definitely got an email when I registered mine.
Sent from my BAMForever Thunderbolt

[Q] Stock Recovery Image SGH-I437 Samsung Galaxy Express

Hello, I have a samsung galaxy express sgh-I437 with AT&T that I've somehow managed to eliminate the recovery image on. I've tried to create my own CWM recovery image, but as I have no idea how to create one didn't succeed, i did however create an image through CWM that Odin pushes through fine and it raises my counter, but still no recovery image, and I have scoured the world looking for even a stock recovery image and can't find one anywhere. If some one could help me or even point me into the right direction on how to create the image or where to find one I would be greatly appreciative. All of this because I deleted some stock apps and now I can't update to JB, even after reinstalling missing apps (ChatOn)
Thanks guys and everyone here is awesome, this is and has been my go to site since i started in the android world with my HTC Inspire

Join the crowd of Galaxy Express owners hoping that someone is able to delve into this somewhat decent device and make some magic with it (recovery, stock ROMs, custom ROMs, whatever). So far it just doesn't seem to have much interest sadly, but there are quite a few searches I've noted (right now the advanced search showed 40, yesterday when I checked there were over 70, the day before over 115, etc).
It'll either get some support or it won't - I'm considering selling mine already and I've only had it for 2+ days. My worry is that if I do decide to sell the thing that 5 minutes later someone will announce they're going to develop for it or already have some custom ROM ready, I don't know but I've had that happen in the past: get a device, nobody cared about it, sold it, then literally the same day someone starts working on it and it turns out to be a fantastically capable device for experimentation and development.
Oh well, such is the flux of Android devices and development I guess. :silly:
As for your issue(s), I upgraded mine to Jelly Bean on Saturday night and I've had issues with GPS and the CPU not downclocking as it should (sticks at about 1.1 GHz and won't go lower) so if you're still on ICS, stick with it - that's my suggestion.
(and hope someone takes an interest in the Galaxy Express, soon)

Respectfully request some help on the Express...
br0adband said:
Join the crowd of Galaxy Express owners hoping that someone is able to delve into this somewhat decent device and make some magic with it (recovery, stock ROMs, custom ROMs, whatever). So far it just doesn't seem to have much interest sadly, but there are quite a few searches I've noted (right now the advanced search showed 40, yesterday when I checked there were over 70, the day before over 115, etc).
It'll either get some support or it won't - I'm considering selling mine already and I've only had it for 2+ days. My worry is that if I do decide to sell the thing that 5 minutes later someone will announce they're going to develop for it or already have some custom ROM ready, I don't know but I've had that happen in the past: get a device, nobody cared about it, sold it, then literally the same day someone starts working on it and it turns out to be a fantastically capable device for experimentation and development.
Oh well, such is the flux of Android devices and development I guess. :silly:
As for your issue(s), I upgraded mine to Jelly Bean on Saturday night and I've had issues with GPS and the CPU not downclocking as it should (sticks at about 1.1 GHz and won't go lower) so if you're still on ICS, stick with it - that's my suggestion.
(and hope someone takes an interest in the Galaxy Express, soon)
Click to expand...
Click to collapse
I noted in your sig that your Express is unlocked.What about rooting? Can you tell a very new noobie, what method can be used to root the Express? And can you tell me if it is possible to root it now AFTER I have let it update to Jellybean 4.1.2? I would really appreciate the information. I noticed your post and noted that you are the one person I have found that can hopefully tell me something about rooting the Express. I keep searching the internet and I can find nothing definitive. It seems it was an easy matter to root it when it was still on ICS, but now that I have updated I found one video of rooting an S3 with 4.1.2 and he says in the video that it should work on any Jellybean 4.1.2 device. But the rooting method used is with ODIN using a rooted img file (I looked inside the tar file). My gut tells me that I don't want to use an image file for an S3 to root my Express, but as I said, I am a noobie and maybe this is possible. Any help is greatly appreciated.

I haven't even attempted to root it. There are several threads mentioned here (in those searches I talked about) and several methods are talked about but it doesn't appear to have a proper working root at this time. That might change if someone takes an interest in this phone but, since none of the methods I've read about are confirmed to work - one person says method A worked for them, another person says method B worked, five other people say none worked at all, etc - I'm not taking any chances on bricking this thing since it's in pristine shape and I can (hopefully) sell it. I've got it listed on craigslist at the moment actually, so...
Unlocking it was cake, it uses the same method the Samsung Galaxy S3 does: enter the code to get to the hidden menu, bring up one or two of the menu options, wait 30 seconds or so, go back a step, wait a minute or so, then reboot, that's it, unlocked. Doesn't get much simpler than that, and it works with T-Mobile's recently activated (just last week) 4G LTE network here in Las Vegas without a hitch too.
But while I wouldn't mind rooting it (have a few apps that need root) I'll wait, or I'll end up selling it with the first good offer from the craigslist ad. At this point it doesn't matter I suppose, it just seems like a decent device that's getting ignored, but there could be a reason for it (some screwy new protection mechanism from Samsung, who knows, I did read that the recovery partition isn't where it should be or it's hidden, something to that effect).
Bleh... my advice for the present time: leave it alone, with ICS, unrooted, until someone potentially comes up with a breakthrough that gets things rolling.

Unlocking and it's already updated....
br0adband said:
I haven't even attempted to root it. There are several threads mentioned here (in those searches I talked about) and several methods are talked about but it doesn't appear to have a proper working root at this time. That might change if someone takes an interest in this phone but, since none of the methods I've read about are confirmed to work - one person says method A worked for them, another person says method B worked, five other people say none worked at all, etc - I'm not taking any chances on bricking this thing since it's in pristine shape and I can (hopefully) sell it. I've got it listed on craigslist at the moment actually, so...
Unlocking it was cake, it uses the same method the Samsung Galaxy S3 does: enter the code to get to the hidden menu, bring up one or two of the menu options, wait 30 seconds or so, go back a step, wait a minute or so, then reboot, that's it, unlocked. Doesn't get much simpler than that, and it works with T-Mobile's recently activated (just last week) 4G LTE network here in Las Vegas without a hitch too.
But while I wouldn't mind rooting it (have a few apps that need root) I'll wait, or I'll end up selling it with the first good offer from the craigslist ad. At this point it doesn't matter I suppose, it just seems like a decent device that's getting ignored, but there could be a reason for it (some screwy new protection mechanism from Samsung, who knows, I did read that the recovery partition isn't where it should be or it's hidden, something to that effect).
Bleh... my advice for the present time: leave it alone, with ICS, unrooted, until someone potentially comes up with a breakthrough that gets things rolling.
Click to expand...
Click to collapse
Too late for ICS. I already let it update to Jellybean 4.1.2 and I really like it. It is much more responsive and accurate even with the voice-to-text feature in messaging. But, you sound very wise as far as the rooting subject goes, so I will wait for a while to see what happens. But as far as the unlocking, can you give me a link to how to do this? Or can you be more specific, please? I am such a noobie that I don't even know how to get to this "hidden" menu that you are talking about. Can you help me with more specific instructions please? I have a much better chance to sell it if it is unlocked than if it is tied to AT&T. Thank you.

Same one for all the Galaxy S3 models:
http://forum.xda-developers.com/showthread.php?t=2023709
My suggestion: change the timer on the backlight to 5 minutes when you're doing this so it doesn't keep dropping back to sleep mode, and then get started.
Pretty simple stuff, just pay attention to the 3rd step (as soon as you choose that option, wait for at least 30-40 seconds before continuing - don't do anything, just sit there holding the phone in your hand or whatever for 30-40 seconds, then go to the next step.
When you get to the last step, definitely wait at least 60 seconds before you do a reboot of the phone (JB now offers the restart option, so restart directly from there - don't back out of any of the menus, just wait the 60+ seconds, hold Power for the menu, choose Restart and when it reboots you should be unlocked.
Just to ask, did you do any testing of the GPS in ICS? I did, and as I noted in another post in another thread, I was pulling in 22 satellites from inside my apartment in under 10 seconds and a fix in 3-5, now with JB I can't get more than 6-8 satellites in the same exact spot and it takes nearly 4 or 5 minutes to get a solid fix so I'm positive there's something going on with Jelly Bean on this device but, alas, I can't roll back to ICS now.

GPS and thank you...
br0adband said:
Same one for all the Galaxy S3 models:
http://forum.xda-developers.com/showthread.php?t=2023709
My suggestion: change the timer on the backlight to 5 minutes when you're doing this so it doesn't keep dropping back to sleep mode, and then get started.
Pretty simple stuff, just pay attention to the 3rd step (as soon as you choose that option, wait for at least 30-40 seconds before continuing - don't do anything, just sit there holding the phone in your hand or whatever for 30-40 seconds, then go to the next step.
When you get to the last step, definitely wait at least 60 seconds before you do a reboot of the phone (JB now offers the restart option, so restart directly from there - don't back out of any of the menus, just wait the 60+ seconds, hold Power for the menu, choose Restart and when it reboots you should be unlocked.
Just to ask, did you do any testing of the GPS in ICS? I did, and as I noted in another post in another thread, I was pulling in 22 satellites from inside my apartment in under 10 seconds and a fix in 3-5, now with JB I can't get more than 6-8 satellites in the same exact spot and it takes nearly 4 or 5 minutes to get a solid fix so I'm positive there's something going on with Jelly Bean on this device but, alas, I can't roll back to ICS now.
Click to expand...
Click to collapse
Both on ICS and on Jellybean it can't seem to get a good lock on any satellite, it has to go through the wifi for its location services. It even took forever to get a lock outside when I was on ICS. I will try it now on Jellybean and report back. BTW, how do you note the number of satellites that you are pulling from and how do you get the GPS to manually start. It just seems to do it randomly on my phone. I've got a navigation device (TomTom) that pulls about 16 satellites here at home but it reports it right on the screen. So, how do I force the Express to do a GPS locating and how do I find out how many satellites it is pulling from? Do I need a special app? You have really made me curious and I am learning a lot from you, so thank you. If you can just be bothered one more time to answer these questions, I will immediately test it inside and outside the house. Thank you again for all your help so far.
---------- Post added at 04:19 PM ---------- Previous post was at 03:28 PM ----------
caine0001 said:
Both on ICS and on Jellybean it can't seem to get a good lock on any satellite, it has to go through the wifi for its location services. It even took forever to get a lock outside when I was on ICS. I will try it now on Jellybean and report back. BTW, how do you note the number of satellites that you are pulling from and how do you get the GPS to manually start. It just seems to do it randomly on my phone. I've got a navigation device (TomTom) that pulls about 16 satellites here at home but it reports it right on the screen. So, how do I force the Express to do a GPS locating and how do I find out how many satellites it is pulling from? Do I need a special app? You have really made me curious and I am learning a lot from you, so thank you. If you can just be bothered one more time to answer these questions, I will immediately test it inside and outside the house. Thank you again for all your help so far.
Click to expand...
Click to collapse
I tested its ability to use GPS on Jellybean by turning off location by wifi. I used the yp app and it pulled an address within 30 feet of my house... When I used the AT&T Navigator Diagnostic tool I got 10 satellites outside with accuracy of 26 ft. Inside I get 5 satellites. So it works pretty good (not as good as my TomTom). Now I need to cancel that Navigator before they charge me. Hope this information helps you. Jellybean seems to give me an almost instant GPS lock, so I have to say, that's pretty good. Again, I hope this helps you in diagnosing your problems somehow. If I had more money I would upgrade to a better phone, but for the $49 I paid, this thing is pretty darned good. I understand how someone who is used to high-end phones might be disappointed, but if you want a good bang for the buck, I think the Express is a pretty good choice:good: (certainly better than my wife's IPhone 4S).

I use GPS Status & Toolbox from Google Play more than anything else for basic GPS duties, I don't own a car anymore (gave that up years ago) so the only real purpose I have for GPS is using it with Wigle for Wi-Fi access point mapping. Having said that, I still expect GPS to work as designed so whenever I have issues it's one of the first things I notice.
I just rebooted the phone since it's been running JB for about 2 days now and should be "settled in" as Android has a tendency to do. Remarkably I just pulled in 21 satellites from inside my apartment - something it wasn't doing on Saturday night right after I did the upgrade to JB but now it is, and got a fix in a matter of seconds so, I suppose the settling in helped (?!?!?!)
Mind you, that's pure GPS in the screenshot below: no Wi-Fi assistance, no location awareness, and no carrier assistance either, everything is disabled except the GPS itself so, yeah, I'm somewhat satisfied now since it seems to be working pretty much as well as it did on ICS the other day before the JB upgrade.
Anyway, when I enabled the Power Saving mode, the CPU finally started clocking itself up and down as expected so I suppose that too is also now working as designed, we'll see what happens. So far so good is all I can say at the moment.

Here is a copy of the stock recovery. Have fun =)
This is not a flashable zip. It only a copy of the mmcblk0p18 (Recovery) partition from ICS 4.0.4 of the Samsung Galaxy Express I437

BlindArtisan said:
Here is a copy of the stock recovery. Have fun =)
This is not a flashable zip. It only a copy of the mmcblk0p18 (Recovery) partition from ICS 4.0.4 of the Samsung Galaxy Express I437
Click to expand...
Click to collapse
Awesome thank you...now...
I'm a newb at stock recoveries, unless Theyve already been Made, so pay no attention If my next question seems dumb but what do I do with it now? How do I create a flashable recovery from that?

br0adband said:
Join the crowd of Galaxy Express owners hoping that someone is able to delve into this somewhat decent device and make some magic with it (recovery, stock ROMs, custom ROMs, whatever). So far it just doesn't seem to have much interest sadly, but there are quite a few searches I've noted (right now the advanced search showed 40, yesterday when I checked there were over 70, the day before over 115, etc).
It'll either get some support or it won't - I'm considering selling mine already and I've only had it for 2+ days. My worry is that if I do decide to sell the thing that 5 minutes later someone will announce they're going to develop for it or already have some custom ROM ready, I don't know but I've had that happen in the past: get a device, nobody cared about it, sold it, then literally the same day someone starts working on it and it turns out to be a fantastically capable device for experimentation and development.
Oh well, such is the flux of Android devices and development I guess. :silly:
As for your issue(s), I upgraded mine to Jelly Bean on Saturday night and I've had issues with GPS and the CPU not downclocking as it should (sticks at about 1.1 GHz and won't go lower) so if you're still on ICS, stick with it - that's my suggestion.
(and hope someone takes an interest in the Galaxy Express, soon)
Click to expand...
Click to collapse
I have managed to get root on this device well at least with 4.0.4 ICS, that part was relatively easy with unlock root and It let you unlock root without paying for It lol and I agree I hope someone takes interest in this device soon when you compare it to the s3 the specs arent that far apart lol

ChronicScribe said:
Awesome thank you...now...
I'm a newb at stock recoveries, unless Theyve already been Made, so pay no attention If my next question seems dumb but what do I do with it now? How do I create a flashable recovery from that?
Click to expand...
Click to collapse
If you are on 4.0.4 and rooted read this post of mine.
http://forum.xda-developers.com/showthread.php?p=39626678#post39626678
ChronicScribe said:
compare it to the s3 the specs arent that far apart
Click to expand...
Click to collapse
The partition layouts are identical, but the kernels and images are different.

Hopefully, we can get somebody with stock ics to do a factory reset then a system dump. I tried flashing my system dump with odin and it seemedto be trying to flash something to boot thus invoking our cursed locked bootloader. I don't know why it would try flashing to boot as it should have been only the /system partition. Maybe something to do with initramfs
? I'm hoping a system dump performed after factory reset might have different results
Now, since we cant flash a zimage that means we're stuck with jb kernel. Would that be an issue, I wonder? If we had jb kernel (and initramfs) with ics /system?
Another thing would be for a rooted ics to use ota rootkeeper for update, then system dump.
Factory reset, root, ota rootkeeper, update, system dump.
If not, then cwm and an insecure kernel would be our best bet. Although we would need the initramfs from the jb zimage. Which we can't get without root...
Sigh.
As to the recovery image. You'll need to use odin 3.07. I don't have a link handy. Also, the file must be prepared in a certain way. I have one at hone. Can upload later.

ChronicScribe said:
Awesome thank you...now...
I'm a newb at stock recoveries, unless Theyve already been Made, so pay no attention If my next question seems dumb but what do I do with it now? How do I create a flashable recovery from that?
Click to expand...
Click to collapse
Of course, you can make your own odin img as follows:
Either in linux or in an android terminal emulator:
First of all, cd to the directory the recovery image is stored.
E.g.
cd /mnt/extSdCard
Then:
tar -c recovery.img > recovery.tar
md5sum -t recovery.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
Note: rename original recovery image to recovery.img. Not sure exactly how odin determines what goes whereand suspect it might be the name.
Easy.
Same procedure for kernel and system, by the way. zimage and factoryfs.rfs respectively.

+1

Alright thanks to BlindArtisan and invert_nexus i was able to create and successfully flash the stock recovery back onto the express. I'll post it here for anyone who might need it :victory: this does not have CWM on it but i'm currently trying to figure that out also I also have a copy of the update to JB that i'm going to attempt to use to get the phone to allow me to update and I'm going to use OTA RootKeeper to see root access will stay.
Once again thanks to everyone here for their expertise and knowledge hopefully we can get the attention of some people to get the galaxy express ball rolling lol
Now my counter is up to 3 and I have triangle away put i'm afraid to use it at the moment because I don't won't to completely screw the phone up, is anyone aware as to whether or not it will work on the express without bricking it?

Well I ended up getting an offer on my Galaxy Express so I offloaded it earlier tonight for a somewhat decent profit, guess I'll move on to the next device and edit the signature yet again.
Good luck to those that pursue development on this device, it sure could use some love.

So apparently i've done something horrible lol my express no longer allows me to install apps, i can't open the play store at all, i can't install apps from the web, unlock root says i have root access but i can't push any files to the system folder because i'm not rooted, nothing opens on the phone, except settings, did a factory reset and still have the same issue...any advice?

ChronicScribe said:
Alright thanks to BlindArtisan and invert_nexus i was able to create and successfully flash the stock recovery back onto the express. I'll post it here for anyone who might need it :victory: this does not have CWM on it but i'm currently trying to figure that out also I also have a copy of the update to JB that i'm going to attempt to use to get the phone to allow me to update and I'm going to use OTA RootKeeper to see root access will stay.
Once again thanks to everyone here for their expertise and knowledge hopefully we can get the attention of some people to get the galaxy express ball rolling lol
Now my counter is up to 3 and I have triangle away put i'm afraid to use it at the moment because I don't won't to completely screw the phone up, is anyone aware as to whether or not it will work on the express without bricking it?
Click to expand...
Click to collapse
i use this recovery image but is like i mess up everything now is not even been recognize by kies software anymore pls i need some help if i can recover this phone at all to original or New firmware

ICS vs JB GPS
br0adband said:
Just to ask, did you do any testing of the GPS in ICS? I did, and as I noted in another post in another thread, I was pulling in 22 satellites from inside my apartment in under 10 seconds and a fix in 3-5, now with JB I can't get more than 6-8 satellites in the same exact spot and it takes nearly 4 or 5 minutes to get a solid fix so I'm positive there's something going on with Jelly Bean on this device but, alas, I can't roll back to ICS now.
Click to expand...
Click to collapse
I was able to do side by side testing of ICS vs JB since mine got upgraded & my wife's didn't and your GPS observation seems spot on. Neither of us had ever used GPS so 1st thing I noticed was mine with JB it took about 10 minutes to get a lock where hers took about 30 seconds. Keep in mind these phones were side by side. Granted indoors but near a window but either way they were next to each other so should get the same signal/sats. I left them both searching for sats for about 1/2 hr then swapped spots & let them go another 1/2 hr. Even after leaving them for awhile the JB one definitely finds less sats & takes longer to lock. A very strange thing to note is for some reason the compasses show completely different direction but not sure why. Funny thing is neither is right but ICS is closer & JB is WAYY off.
I attached pic of them side by side after same amount of time searching and also a video showing them sync. Granted time difference is negligible now, the # of sats is definitely lower for JB. (JB on left & ICS on right. Can see the upgrade nag at the top as it was postponed.)
Hopefully poor GPS doesn't plague this phone if JB is being forced on us.
Bill
EDIT: Apologies to OP, this thread came up searching to compare ICS vs JB & I didn't pay attention I was OT replying. While already OT I'll add a few more observations about JB vs ICS. JB seems to be using 171MB more memory than ICS comparing mine to my wife's with mine @ 494MB used & my wife's @ 323MB. (Some apps are the same, just larger, but there are a few new ones like Simple Alarm Clock 3.5MB, PageBuddyNotiSvc 3.0MB & Stock Daemon(EUR 4.2MB to name a few but many other crapware's I'd love to kill. (I can kill some of them temporarily but they come back) ATT Software Update is using 10MB, Media Hub 4.6MB, S Suggest 3.9MB, AT&T Hot Spots 3.0MB and a few i'm not sure on like Synchonize 5.0MB S Voice 6.3MB com.sec.phone 2.7MB.) They took away the Mobile Data button on the drop-down menu! The new dialer is FUGLY! (Granted I hate the stock dialer because it's so hard to dial & find people so I use Dialer One but still WOW what is up with the white dialer.) On both rom's I miss the Power widget. Really need to get this this ROOTED ASAP to kill some of that crap.