hey guys....well i downgraded my nexus s 9020T for 4.0.3 to 2.3.6...however but while switching it on the 2.3.6..im getting a lock symbol while switching it on..and when i insert my sim onto the phone ..it is recognising the network but not catching the signal
kindly help me out
The lock symbol at the bottom means your bootloader is unlocked. This means you can replace your recovery partition to CWM or the likes, as well as flash superuser to the OS and flash custom ROMs. You would have achieved this through the "fastboot oem unlock" command.
The signal issue may be related to a bad flash. I would be going into recovery, doing a factory/data reset, formatting /system and /boot, and then flash the 2.3.6 file you have again. Remembering of course to backup anything currently on the phone, and doing a NANDROID backup if you don't have a working one already.
thank so much for the information...after doing this..can my phone still OTA official updates from google once they are released??
roshan567 said:
thank so much for the information...after doing this..can my phone still OTA official updates from google once they are released??
Click to expand...
Click to collapse
As long as you flash a official update
Sent from my ice cream powered Nexus S
a friend of mine is doing the flashing...any idea as to how can i know whether he has flashed an official update or not?
also what is the different between flashable roms n the increamental updates given in this link??
http://forum.xda-developers.com/showthread.php?t=1063664
are both official versions given out by google?
Yes, all of the links in that thread are official Google builds. The full/flashable ROMs are the full operating system in one file. You can install this over any Android version/ROM since the zip will contain all of the files necessary to get the system working.
The incremental updates should only be used if you have a specific (official) Android version and wish to only install the updated files. For example, if you have the official Google release of 2.3.6 and wish to upgrade to 4.0.3, you can use the 2.3.6 -> 4.0.3 incremental update. Otherwise, if don't have one of the supported incremental update versions or if you're using a non-stock ROM then you'll need to download the full ROM.
thank you so much for the information....
i am downgrading my OS to 2.3.6 from 4.0.3..how can i find out whether the 2.3.6 OS ive installed is the original OS???
You can find out BEFORE flashing the rom by comparing checksums, the zip file should have the exact same checksum as indicated in the filename of the files in that thread. Also, that thread just links to files from googles servers used for official updates.
Once it's installed there is no point trying to finding out if it is 100% stock.
Harbb said:
You can find out BEFORE flashing the rom by comparing checksums, the zip file should have the exact same checksum as indicated in the filename of the files in that thread. Also, that thread just links to files from googles servers used for official updates.
Once it's installed there is no point trying to finding out if it is 100% stock.
Click to expand...
Click to collapse
thanks for the information...i didn understand properly how do u do checksums..can you pls explain it??im a noob..
Checksum (or hash) is a way to verify a file. It will create a word/number/pattern/etc according to an algorithm based on all the data in the file. With MD5, SHA1, etc we have a practically guaranteed chance of comparing the two files. Those files there are straight from google and google has provided the checksums in the filename (part of the checksum, at least). If you have any file at all and it has the same code as that, we can be happy that it's the exact same file - thus 100% stock
You can use software such as Checksum or my personal favourite HashTab to find the various comparing techniques.
hey thanks a lot for your information..it really helps....
when i upgraded to ICS my phone stopped receiving reception after 2 days..when i downgraded it after unlocking the bootloader it still wasnt receiving recepetion...why does this happen?
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.
I have updated my non rooted I9020t from stock 2.3.6 to 4.0.3 using file VQ8PQk_V.zip in android stock recovery. Then tried to apply the update patch for 4.0.4 hR7QFEtn.zip which gave me status error 7. I then tried to re-apply 4.0.3 on top of my already flashed 4.0.3 VQ8PQk_V.zip and also got the same status error 7.
Please post in detail your Phone Type as well as the exact procedures you have tried and what files you have used.
Please keep this post as Non Rooted Phones only.
Let's work together to see if we can get a solution from trial and error
people it's not rocket science !!!
Required :
1.Stock ICS 4.0.3
2.Unlocked bootloader
3.Custom recovery installed (like CWM recovery)
4.The update zip (~18 mb) copied to root of /sd card
Choose install update from zip on sd card
Have fun !!
c0de2 said:
I have updated my non rooted I9020t from stock 2.3.6 to 4.0.3 using file VQ8PQk_V.zip in android stock recovery. Then tried to apply the update patch for 4.0.4 hR7QFEtn.zip which gave me status error 7. I then tried to re-apply 4.0.3 on top of my already flashed 4.0.3 VQ8PQk_V.zip and also got the same status error 7.
Please post in detail your Phone Type as well as the exact procedures you have tried and what files you have used.
Please keep this post as Non Rooted Phones only.
Let's work together to see if we can get a solution from trial and error
Click to expand...
Click to collapse
I see Your point; sitting in the same boat; i9023, SLCD, unrooted; 4.0.3 ->4.0.4, giving me the same error message.. Do NOT want to root/ unlock, etc, want to keep stock; but do hope for a solution -especially as OTA upgrade in Europe can take several weeks..
Please beware if you Unlock your bootloader you invalidate your warrently. I'm assuming thats why c0de2 wanted this post to be kept to unrooted phones.
You could try downloading the complete 4.0.4 firmware rather than the update. Thats what I did with no issues. Unfortunately I don't have a link to hand.
Ur warranty will be fine... all u will have to do is unroot it back to stock.
So open ur world to the "root" world.
U will not regret it
ICS is good, but better when its customized.
Vs Nexus S 4G
Look at your download history please!!!
madgibbon said:
Please beware if you Unlock your bootloader you invalidate your warrently. I'm assuming thats why c0de2 wanted this post to be kept to unrooted phones.
You could try downloading the complete 4.0.4 firmware rather than the update. Thats what I did with no issues. Unfortunately I don't have a link to hand.
Click to expand...
Click to collapse
that would be the link we're all waiting for!
madgibbon said:
You could try downloading the complete 4.0.4 factory firmware rather than the update. Thats what I did with no issues. Unfortunately I don't have a link to hand.
Click to expand...
Click to collapse
Is it possible to load the complete firmware in Android Recovery UNrooted?
Here is the link to the factory firmware 4.0.4 if anyone needs it. This is Factory Complete Images for 4.0.4 not incremental updates.
I have not tried it please be careful not tested by me yet (not sure if it's possible to load it on Factory Android Recovery) paste this url into your browser for factory 4.0.4 code.google.com/android/nexus/images.html
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
hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.
OTA updates will require a stock recovery. I'm in the process of getting an Idol 3 but I used to have an Idol 2 and, to return to a completely stock ROM, I had to use the Alcatel Mobile upgrade too which identified my phone, downloaded the correct firmware, and restored the phone. Prior to restoring back to stock, I had cwm and root.
Thanks for the reply I tried the software update but its not working keep saying I have the latest even when I did a full wipe. Using the latest 4.9.2 version...is there a way to make a twrp flashable ota zip from the downloaded update file in the ota cache..
lude86 said:
hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.
Click to expand...
Click to collapse
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.
famewolf said:
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.
Click to expand...
Click to collapse
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?
tekka-maki said:
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?
Click to expand...
Click to collapse
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.
famewolf said:
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.
Click to expand...
Click to collapse
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:
tekka-maki said:
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:
Click to expand...
Click to collapse
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.
famewolf said:
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.
Click to expand...
Click to collapse
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.
tekka-maki said:
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.
Click to expand...
Click to collapse
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.
famewolf said:
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.
Click to expand...
Click to collapse
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao
tekka-maki said:
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao
Click to expand...
Click to collapse
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.
famewolf said:
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.
Click to expand...
Click to collapse
Omfg buddy, you said, '... you CAN install an OTA update with twrp' ; all I did was point out that I flashed previous updates (presumably the same way you're talking about), TWRP remained in tact afterward, & asked you to follow through with that point with, you know, the actual update in question here that defies many of your assertions. One of your recommendations is broken (Q), the other is hindsight (full backup) & last (update via TWRP) seemingly not feasible (unless someone were to submit updated /system) . Anyway it's all a moot point now since we're just measuring our junk.
I'm tickled you're running 5.1.1, as you've said repeatedly... I tried it briefly on Shamu & was happy to leave the LP quagmire all together & get to 6.0.1. Sufficed to say, there isn't anything perfect about this device or 5.1.1, which is why I'll leave as is & sell it. :good:
Thanks anyway.
I had been an iphone user for 10 years and I used to often update via ipsw files for complete updates and not OTA updates. It used to resolve many issues sometimes introduced with OTA updates.
What is the equivalent for android and Samsung N20U? Also, where do you download these files from?
Thank you.
On Samsung devices there is a flash tool called Odin with which you could flash full official firmwares. Those you can either download from Sammobile (which I don't recommend unless you have a premium account as the download speeds sucks big time for free accounts) OR you could use a download alternative program that takes the files from proved, safe storage locations. I personally use SamFirm and/or Frija (this one proved to be a bit better than SamFirm lately).
After you get the download tool, query the database for your model/type and get the results, then you have option to download it. After that, flash it via Odin.
These are just general guidance rules, you'll find specific usage manuals/steps for each of the above by an easy search on Google
Sent from nowhere over the air...
Thank you so much for the explanation. I really appreciate it. Is there a belief amongst community that full updates re better than ota in android too. It definitely was the case with iOS.
enjoylife1788 said:
Thank you so much for the explanation. I really appreciate it. Is there a belief amongst community that full updates re better than ota in android too. It definitely was the case with iOS.
Click to expand...
Click to collapse
I'm not familiar with what is considered "full updates" in comparison to OTA.
But if you are using a device with a Snapdragon processor there is really only the option for updates that are "Officially" released, the bootloaders are locked and don't give the opportunity for a modified firmware. If you happen to be using a device that will allow for a modified firmware (I'm not up to speed on the current availability of them) they may become available soon if not already.
While the modified firmware can be very good, I don't think I could honestly say that only one might be better than the OTA.
He was referring to a "full firmware" that contains the entire Android OS and all the apps as they originally come on the phone. Opposed to an "OTA update" which is a smaller file that contains just the changes and are flashed on top of an existing firmware.
Each OTA has a corresponding full firmware release and someone could flash that one instead of just updating via OTA, resulting in an updated phone having an official firmware on it. This does not void warranty or break things (ofc if done properly and without error).
I won't detail the reason for which someone would prefer to flash a full firmware instead of just updating from an OTA, but there are some...changing CSC for ex or having a newer compatible firmware in case the one for the owner's country has not been released yet and so on...
This is not about custom ROMs that are a different thing.
Sent from nowhere over the air...
Rapier said:
He was referring to a "full firmware" that contains the entire Android OS and all the apps as they originally come on the phone. Opposed to an "OTA update" which is a smaller file that contains just the changes and are flashed on top of an existing firmware.
Each OTA has a corresponding full firmware release and someone could flash that one instead of just updating via OTA, resulting in an updated phone having an official firmware on it. This does not void warranty or break things (ofc if done properly and without error).
I won't detail the reason for which someone would prefer to flash a full firmware instead of just updating from an OTA, but there are some...changing CSC for ex or having a newer compatible firmware in case the one for the owner's country has not been released yet and so on...
This is not about custom ROMs that are a different thing.
Sent from nowhere over the air...
Click to expand...
Click to collapse
Yes that's what I am talking about.
enjoylife1788 said:
Is there a belief amongst community that full updates re better than ota in android too[?]
Click to expand...
Click to collapse
I rarely have difficulty with either. I only flash an update manually if the firmware is available that way but the OTA version has been delayed. (You can preserve all your data and settings even if you flash manually.)
Gary02468 said:
I rarely have difficulty with either. I only flash an update manually if the firmware is available that way but the OTA version has been delayed. (You can preserve all your data and settings even if you flash manually.)
Click to expand...
Click to collapse
Ok. Thank you
enjoylife1788 said:
Thank you so much for the explanation. I really appreciate it. Is there a belief amongst community that full updates re better than ota in android too. It definitely was the case with iOS.
Click to expand...
Click to collapse
OTA 's are generally solid. I haven't used Odin since the note 4. I keep backed up on Samsung account, and if I do experience an issue, a reset will clear it up. All of my media is stored on SD card.
How do you store everything on an SD card. Sorry but coming from an iPhone. Thabk you .