hello i know maybe it is a stupid question but i there are some devices capable to update after editing the build prop like the g2 or flex.
it's my first time with a samsung device,when try to update it ,it will show that my device has some edit and won't let me download the file.
i can update it or return it to stock by odin,but i would like to keep the build.prop i one certain way for my purposses.
is there one way i could achieve the OTAS without returning the build.prop to stock??
sorry for my english,not my first language.
Try flashing with stock 5.1.1 ROM via odin.
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.
Yes I super one clicked, and odin to intall an unrooted version via the facebook Mesmerize fan page so im rooted.
Phone is now running firmware 2.3.4 Kernel 2.6.35.7, and eho9
All I want to do is change my Sounds and animations at start up and shut down and Every program I get does not allow me to edit the rootfiles. I have all the files I need just cant get them in the right place.
Maybe on a related note, the CWM update.zip gets the signature failure as i have seen soo soo much on here. none of the so called fixes work. manually through oden or through cwm direstly.
Any input or am I going to have to dump this turd and get another carrier?
Feel free to answer as much or as little of this post as possible. My desire is to learn. First, let me phrase my question in general terms:
1. Is it possible to download a stock android firmware rom, extract the rom, and change it, and repackage it in a way that is still accepted by the device as an original factory ROM? In other words, is it possible to take a factory rom (such as an update.zip or in my case 1.0.7.zip) and change it and reinstall it in the stock android system recovery (3e)?
Now that I have asked the general question, I will explain to you why I want to do this (if possible)
I have a tablet that recently stopped booting. I have never rooted it or used a custom rom before. However, the device still powers on and I can access the stock android recovery system. I can even use ADB (though I know very little about it's capabilities). I will explain my logic below. Please feel free to show me if I am wrong on the following points.
1. It is impossible to install a custom rom without FIRST installing a custom recovery.
2. It is impossible to install a custom recovery without FIRST rooting the device.
3. It is impossible to root a device that won't boot if you do not have USB Debugging enabled (via Android Developer Options).
The manufacturer of my device (RCA RCT6378W2) has not released the source code or original factory firmware for this device. I have attempted to install various roms that seem to be compatible via ADB SIDELOAD, but they have always been rejected immediately after the device says:
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
However, I have managed to located 3 firmware updates from RCA. These updates are called 1.0.2.zip , 1.0.3.zip, and 1.0.7.zip. These updates are all accepted by the android system recovery. When I ADB Sideload these updates, the tablet says this:
Finding update package...
Opening update package...
Verifying update package...
Removing unneeded files...
Unpacking new files...
Install from ADB complete.
Although these firmware updates are installed properly, my tablet still does not boot. Upon closer examination of these updates, they are not full android OS firmwares, but mere updates to the existing system. So, this got me to thinking... These updates are the only firmwares that can manage to pass update verification. Is it possible to alter these updates in a way that will still pass this verification process? If this is possible, then I might be able to reflash the rest of the android operating system by altering these updates to include the full OS. Does anyone know if this is possible? What would be the difficulty level of doing so? I have managed to locate nearly all of the files from another user who has the same device in working condition. For example, I have the following from a working device:
Backup.img
boot.img
cache.img
kernel.img
kpanic.img
misc.img
parameter.img
parameter.txt
recovery.img
system.img
Would it be possible to take the files from these images and add them to the firmware updates and repackage it in a way that passes system verification? And my last question is: Is there any other way I can get this device to a working version of android (stock, custom, I don't care!). Thanks!
There is unfortunately no way currently to modify a manufacturer signed zip and still have it signed unless you have friends within the company who can get you that signature. If you want to root your phone first you need to unlock the bootloader then use fastboot while in bootloader/odin/download mode and flash a recovery then you can use a custom rom.
dreamwave said:
There is unfortunately no way currently to modify a manufacturer signed zip and still have it signed unless you have friends within the company who can get you that signature. If you want to root your phone first you need to unlock the bootloader then use fastboot while in bootloader/odin/download mode and flash a recovery then you can use a custom rom.
Click to expand...
Click to collapse
Thanks for the info. If there is no way to alter a manufacturer rom in a way that is accepted by the system, then I might be out of luck. I don't know much about bootloaders. I feel like I heard someone say that this device did not have one. I've also heard that this device doesn't support fastboot and that Nexus is one of the few that does (that might have been an old statement... not sure). Anyways, it might be time for me to give up on this device. Thanks for the clarification.
jeremyb234 said:
Thanks for the info. If there is no way to alter a manufacturer rom in a way that is accepted by the system, then I might be out of luck. I don't know much about bootloaders. I feel like I heard someone say that this device did not have one. I've also heard that this device doesn't support fastboot and that Nexus is one of the few that does (that might have been an old statement... not sure). Anyways, it might be time for me to give up on this device. Thanks for the clarification.
Click to expand...
Click to collapse
what device is it? I'll see if I can find a guide
dreamwave said:
what device is it? I'll see if I can find a guide
Click to expand...
Click to collapse
Thanks for the help. It is a RCA RCT6378W2. It is 7" and 8GB. Lots of info on the following link:
http://specdevice.com/showspec.php?id=0893-5af7-0033-c58700000000
How about this question- On a non-rooted device with standard android recovery system, is there any way to install another rom... perhaps one from a very similar device?
jeremyb234 said:
Thanks for the help. It is a RCA RCT6378W2. It is 7" and 8GB. Lots of info on the following link:
http://specdevice.com/showspec.php?id=0893-5af7-0033-c58700000000
How about this question- On a non-rooted device with standard android recovery system, is there any way to install another rom... perhaps one from a very similar device?
Click to expand...
Click to collapse
no, as it has to be signed by the manufacturer to be accepted by the recovery, and I don't see any roms or even recoveries for your device...
dreamwave said:
no, as it has to be signed by the manufacturer to be accepted by the recovery, and I don't see any roms or even recoveries for your device...
Click to expand...
Click to collapse
Thanks for checking up on that for me. I've learned alot in my process of trying to fix my tablet, but I think it's about time to call it quits
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.
Good day everyone, just got my note pro WiFi version? Already rooted and has custom kernel civz, tablet feels slow so I'm planning on changing rom maybe lineageOS but I'm concerned about the procedure because I'm not sure where I'm standing with every change done to this device, any help is appreciated I just don't want to brick this device trying to flash a new rom.
Currently it's running stock rom 5.0.2, 3.4.39 civz kernel and knox 2.3, if someone could provide a step by step on what should I do or check in this device to be on the safe road id really appreciate it. Btw I don't even know what recovery I have or how do I access it.
Bump
honestly most samsung devices are the same so id suggest getting the full stock system and using odin to revert to stock, from there start by getting a custom recovery and seeing what else you need to set up your rom
someone correct me if im wrong
heres the page for official stock "images"
https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P900/
xxjahasotoxx said:
honestly most samsung devices are the same so id suggest getting the full stock system and using odin to revert to stock, from there start by getting a custom recovery and seeing what else you need to set up your rom
someone correct me if im wrong
heres the page for official stock "images"
https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P900/
Click to expand...
Click to collapse
someone told me that I just need to install twrp as it is and start flashing roms, dont know if this the best way to do it what do you think?
It could work just keep in mind that you don't know exactly what the previous owner did to it so if they installed a custom kernel you'll be stuck with that, could be a good thing could be a bad thing
You could always give it a shot and if it gives you problems go back to stock then TWRP then start rom-ing