I am just interested if there are any chances that we soon get flashable new baseband so we don't have to mess with risky LG and clumsy TMo OTA updates? Has anyone had experience with that before and how long did it take for developers to put flashable zips for us up there?
itll happen when it happens. there really is no putting a date on it.
Main thing it DOES happen, if.
Related
Well I switched to S-OFF to get a new splash screen and now I can no longer install OTA updates for my Hero. I get a signature failure every time I try to install. Does anyone know how to switch this back on? I didn't realize this would kill the ability to do updates as the forums I have read before switching didn't have any mention of it.
Sorry if this has been previously posted and I missed it in the forums.
Any help would be greatly appreciated.
awnorwood said:
Well I switched to S-OFF to get a new splash screen and now I can no longer install OTA updates for my Hero. I get a signature failure every time I try to install. Does anyone know how to switch this back on? I didn't realize this would kill the ability to do updates as the forums I have read before switching didn't have any mention of it.
Sorry if this has been previously posted and I missed it in the forums.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
The signature failure isn't from s-off it's from the custom recovery. What you need to do is to resign the zip.
awnorwood said:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Just an added note, as far as I know, you can't switch back to S-ON on this
device, at least, not at the moment.. If they get S-ON to work on these phones,
good, but if not, I'm not overly concerned.
http://forum.xda-developers.com/showthread.php?t=759955
and
http://unrevoked.com/rootwiki/doku.php/public/forever
for details..
Asadullah said:
The signature failure isn't from s-off it's from the custom recovery. What you need to do is to resign the zip.
Click to expand...
Click to collapse
Not sure I'm understanding the question. But, if he means receiving updates directly from Sprint then they don't come as zip files. So, how would signing anything help him?
Not sure why you would want to download something from Sprint directly anyway. Whenever an update comes out, they're usually packaged and ready for you to flash via custom recovery by the end of the day if not sooner.
mercado79 said:
Not sure I'm understanding the question. But, if he means receiving updates directly from Sprint then they don't come as zip files. So, how would signing anything help him?
Not sure why you would want to download something from Sprint directly anyway. Whenever an update comes out, they're usually packaged and ready for you to flash via custom recovery by the end of the day if not sooner.
Click to expand...
Click to collapse
The ota (over the air) updates that sprint pushes out and you download are stored in an update zip in /cache then when you choose to install them they are flashed through the stock recovery... but if you don't have the stock recovery you will have to pull the update from your device resign it and then flash it through custom recovery. Also they won't work on anything but a stock or close to stock rom because of the checks it does in the update scripts and most of everything inside is .p files (patch).
I should know because I took the second to last sprint update rooted it and posted it on here. You can actually test this theory by running the ruu rooting it and then when you get an update download it but don't install it right away. You'll find it in /cache (I believe forgotten exactly) or just take my word for it.
If you do do it like that I suggest the original 2.1 ruu just because you'll get your original radio back in the process
Asadullah said:
The ota (over the air) updates that sprint pushes out and you download are stored in an update zip in /cache then when you choose to install them they are flashed through the stock recovery... but if you don't have the stock recovery you will have to pull the update from your device resign it and then flash it through custom recovery. Also they won't work on anything but a stock or close to stock rom because of the checks it does in the update scripts and most of everything inside is .p files (patch).
I should know because I took the second to last sprint update rooted it and posted it on here. You can actually test this theory by running the ruu rooting it and then when you get an update download it but don't install it right away. You'll find it in /cache (I believe forgotten exactly) or just take my word for it.
If you do do it like that I suggest the original 2.1 ruu just because you'll get your original radio back in the process
Click to expand...
Click to collapse
Good information to know. Thanks Asadullah.
Is there anyway to deodex the Infuse yet?
probably the same as a galaxy s. gtg465x posted one but we are haveing trouble getting a successful odin package to fix the phone when things go wrong so people were not willing to try it.
Thank you for the fast respond, are we gonna lose the phone if something goes wrong. or if something goes wrong is there a way to fix it.
sinan2010 said:
Thank you for the fast respond, are we gonna lose the phone if something goes wrong. or if something goes wrong is there a way to fix it.
Click to expand...
Click to collapse
well with samsung we are lucky enough to have odin which is a factory flash tool. unfortunately it is not working on the infuse 100%, there may be a new build of it just for the infuse but it hasnt been leaked yet as far as we know. there is also an opensource application called heimdall that works in place of odin. there has been some success with heimdall but the one user that restored with it is having random vibrate issues.
there are still things to figure out, but there is no reason you cant flash with cwm, there are just no proven roms or reliable methods to restore if it goes wrong.
Thanks again. I'll just wait since I'm not good in doing these kind of things.
Just to chime in, you can definitely softbrick the phone if you try to deodex the rom and something goes wrong. I know from experience (happened to me yesterday ) As far as I know, I'm the only one who has successfully flashed back to stock using h8rift's original test tar but now there's confusion about whether it's reliable or not due to other testers' experiences. We're gonna get there just hang tight.
beatblaster said:
Just to chime in, you can definitely softbrick the phone if you try to deodex the rom and something goes wrong. I know from experience (happened to me yesterday ) As far as I know, I'm the only one who has successfully flashed back to stock using h8rift's original test tar but now there's confusion about whether it's reliable or not due to other testers' experiences. We're gonna get there just hang tight.
Click to expand...
Click to collapse
So there are already some people brick their devices and good to know that you have successfully flashed it back.
I just have no idea how to do these kind of things this is my first Android device. I had HD2 and was so easy to do anything. I'm just afraid to brick my infuse, so I'll just wait
I just need to deodex it so I can be able to read and write in Arabic.
Thanks
So I have been reading over in the development forums and it seems like a lot of users are having issues restoring backups with jt's recovery.
Most of them have ended up with bricked phones and no way to fix it cuz we are still lacking a full odin package for the charge.
Has anyone had success doing a restore in CWM?
Anyone? Please
This is something I'm going to get with imnuts on to fix. Just waiting for my charge to come in.
boostedjti said:
This is something I'm going to get with imnuts on to fix. Just waiting for my charge to come in.
Click to expand...
Click to collapse
Ok I figured someone would be working on it I just didnt know if everyone was affected by it or just a few people because i havent seen much talk about it. Also I figured maybe we should put a warning up so more people dont attempt to restore just to end up with a bricked phone.
Manjews said:
Ok I figured someone would be working on it I just didnt know if everyone was affected by it or just a few people because i havent seen much talk about it. Also I figured maybe we should put a warning up so more people dont attempt to restore just to end up with a bricked phone.
Click to expand...
Click to collapse
I made a post similar to this in the cwm thread. Thanks for posting it up here too. I have a feeling it's more then just user error, which is the first thing everyone wants to blame something on, and typically the case. Just not feeling like this is the same situation. Good lookin out for everybody!
It sucks for them but we really do need the odin package just in case for future bricks lol
Sent From My VooDood Charge
Based on the one post I saw, it seems like it has to do with restoring /data with the error message that popped up. I'd guess that this is an issue with CWM, but it is hard to say for certain. For now though, I'd just avoid restoring anything, and it's this reason I'd rather use Titanium backup to back up stuff than CWM.
I have read in the past that part of the agreement the mfg's have is they need to release source code, does that actually get us a Stock Odin image or not?
I am used to getting the sbf for Moto or the RUU for HTC, but not familiar with Samsung's willingness and position on this.
Mine bricked from attempting a restore with CWM
But the file that imnuts made fixed it.
Sent from my Droid Supercharge.
RaptorMD said:
I have read in the past that part of the agreement the mfg's have is they need to release source code, does that actually get us a Stock Odin image or not?
I am used to getting the sbf for Moto or the RUU for HTC, but not familiar with Samsung's willingness and position on this.
Click to expand...
Click to collapse
Not sure where the stock ODIN images have come from, but tech support @ verizon should have access to them, should only be a matter of time b4 one gets leaked
RaptorMD said:
I have read in the past that part of the agreement the mfg's have is they need to release source code, does that actually get us a Stock Odin image or not?
I am used to getting the sbf for Moto or the RUU for HTC, but not familiar with Samsung's willingness and position on this.
Click to expand...
Click to collapse
Odin images are not source code, they are binary files. The Odin images come from Samsung, but there are people that have access to them at VZW. Getting a full stock Odin would have to come from one of the two places.
Hey I was wondering if anyone has managed to get their hands on the download URL for the patch. It'd be a small patch that you would be able to flash in the stock recovery since it's signed by Alcatel. It'd be much easier for people to put this on their sd cards and flash rather than reimaging their phones.
Someone had a link to the bin... maybe @famewolf
FBis251 said:
Hey I was wondering if anyone has managed to get their hands on the download URL for the patch. It'd be a small patch that you would be able to flash in the stock recovery since it's signed by Alcatel. It'd be much easier for people to put this on their sd cards and flash rather than reimaging their phones.
Click to expand...
Click to collapse
What exactly are you trying to do with it? The patch was specific to each different model of idol 3 (6045i, 6045Y, 6045K, 6039Y, 6039K, 6039i) and was generated at the time the system checker polled their server...it looked at what firmware level the user was already at and added all patches they didn't yet have installed..the urls last for a limited time so yes I did intercept it via a transparent squid proxy but I doubt the url will do you much good as it's probably expired by now...if you want the FILE this is not a patch that will sideload to well I don't believe since one of the things it does is check the checksum of recovery and if it doesn't match the system default recovery it overwrites it. If you try to install it on a device that has any of the previous patches applied that were not applied to MY device at the time of download the update will fail as patch will not apply to an already updated file. The update will then error out.
So to sum all of that up, what exactly are you trying to do with the file? Oh and the update is 302mb....not exactly "small".
..and no it's not "easier" as if you are rooted and don't fully unroot you risk putting yourself into boot loops that currently cannot be resolved since it wipes out your recovery at the same time. Factory recovery for 6045i and 6045Y does not have reboot to bootloader as an option so you basically have a paperweight. It's easier to deal with an image that is already updated and then just flash the supersu zip right after.
The neat thing is that since the updates are signed by alcatel they're basically the only type of file that will flash with the stock recovery.
It's a shame that they got generated on the fly but it makes sense since it'll be a single download every time for each phone, but that means that as you said it's not reusable.
I haven't messed with Android phones in a bit but I read that as of lollipop that patching mechanism changed to some sort of binary diff patcher instead unlike in the KitKat and older days that an OTA zip would contain the full file to be replaced.
Thanks for the information
FBis251 said:
The neat thing is that since the updates are signed by alcatel they're basically the only type of file that will flash with the stock recovery.
It's a shame that they got generated on the fly but it makes sense since it'll be a single download every time for each phone, but that means that as you said it's not reusable.
I haven't messed with Android phones in a bit but I read that as of lollipop that patching mechanism changed to some sort of binary diff patcher instead unlike in the KitKat and older days that an OTA zip would contain the full file to be replaced.
Thanks for the information
Click to expand...
Click to collapse
Add me to the list that can send you pm's and I'll drop you a link to look at.
Can Someone
Make us a Flashable Update
From sammobile
Its a Wifi & Security UPDATE
But cant update threw our recovery its breaks Update
Or someone explain to us how to do it ourselfs
Just thought about it Really dont need it since Freeza is making us a ROM
But others may want it