Develop Bugs

[Q] Extracting ROM/Firmware from the OS Update. Possible?

I'm sure a lot of you must have thought about this. Since the NoDo update would supposedly start rolling out anytime this week, I'm wondering if it would be possible to extract the ROM from the update?
Assuming that the update process is similar to iOS (since we have to update through Zune) and all the files are downloaded to the PC first, it is possible that the ROM is also downloaded to the PC from where it can be extracted.
If this works, will it be possible to use that ROM/Firmware and flash it on other devices? Say a NoDo update ROM from an AT&T Focus could be used to revive (mine and a lot of other) Samsung Focus devices.
Someone might have to play with the Microsoft Windows Update Service Protocol a bit to get this idea to work, but I'm sure it would be worth the effort.
I would have given it a shot myself but I recently had to return the HD7 review unit I had and my personal Samsung Focus is laying dead.

actualy update could have OEM SOFTWARE PARTS .. like new kernel or driver update .. also - RRUU counts as FFU ( full flash update ) and could not flash partial update .... since ms distribute updates in packages for corresponding os parts . not full image

I think WP7 update process is more complicated than iOS. WP and its build system support differential update, not only full flash update. So the update file could be just part of system files.

There is a com dll you can look into ZuneWmdu.dll, but i was not able to create a com instance in c#. (Maybe i was quiet stupid yesterday or there is really a problem). You should be able with the api to make your own update tool, but since the phone does the request for the firmware/update/rom this could be a little bit complicated.

Flow WP7 said:
There is a com dll you can look into ZuneWmdu.dll, but i was not able to create a com instance in c#. (Maybe i was quiet stupid yesterday or there is really a problem). You should be able with the api to make your own update tool, but since the phone does the request for the firmware/update/rom this could be a little bit complicated.
Click to expand...
Click to collapse
Hmm from what I've heard, the Zune client uses the Zune pass through connection to the phone which checks for updates on its own.
The problem is that if it is a delta update then it would be impossible to build a complete system image from the update.
I wonder if it still would be possible to use ROMs from another similar device but replace driver and device specific files from the original device. That would be sort of a custom ROM.

4.3 update on a Mac: using Kies INSTEAD of Odin?

Like many people who heard the news, I really want to get the 4.3 update on my note 2. I've downloaded the firmware but as a mac user, I cannot simply install it with Odin (since it's windows only) and I haven't found any Heimdall packages ready for flashing.
I have tried the wine bundled Odin-for-mac, but this doesn't detect my phone via USB.
I may have to install Win 8 on a bootcamp partition JUST for this, but before I go that far I'd like to pose the question: is it possible to fool kies into thinking the ROM I have is official - so that it installs like the real thing?
Just throwing it out there, interested in what responses I get...
Thanks.

You can also flash a firmware using heimdall on a mac.
Instructions:http://forum.xda-developers.com/showthread.php?t=2118100 and http://forum.xda-developers.com/showthread.php?t=878686

New Nexus Owner Seeking Advice

Hi folks! Just received a 2013 Nexus 7 from my fiancé as a birthday gift. I wanted it for quite specific purposes so was hoping I could ask a few questions here and get pointed in the right direction before I start using this thing
I intend to mainly use the tablet for remote play with my PS4 and emulating old console games. Since I want to connect a PS4 controller to it wirelessly I'm told I need to root the device. I'm guessing this is an easy process and there are some guides on the site here?
The main thing I was after advice about is firmware updates. The system came on 4.3 and has already downloaded an update for 4.4.2 but I haven't installed that yet. Is this firmware fine to upgrade to? Any performance issues? I've heard people saying that upgrading their Nexus to 5+ (Lollipop?) has created a load of performance issues and this should be avoided? Also, if I upgrade to a certain firmware version can I lock myself out of being able to root the device? I'm pretty sure all of the apps I was planning on using work no 4.3 so I have no reason to upgrade at all but if I can go safely to a higher firmware that is reliable with no performance issues I may as well?
First time using an Android device so sorry if my questions come off as a little stupid. Also, wasn't sure if I should post this here or if it should be on the Q&A board so sorry if I've got that wrong!

As far as I know, the problems with lollipop were the standard number of complaints that come with any new release. Well, I'm not really positive, but lollipop seems fine to me and I think most people have upgraded by now. I would go for it because I think it's really fun to use.... Plus you can always revert if you choose.
As far as rooting, you never need to worry about not being able to do it... Rooting your Nexus 7 will always be easy. The by-hand method is fun and relatively simple, or you can just use the toolkit in the forum to do it even easier.

^Yeah I'll echo that. Lollipop is good. The people having problems don't know what they're doing. Flash the factory image.
If you want root you can use cfautoroot or simply flash twrp with fastboot then flash the su.zip

Personally, I'd stick go for 4.4.4, as 5, 5.0.1 & 5.0.2 all have a memory leak issue. You may also find more emulator compatability as Kit Kat has been around a year longer than Lollipop. The only downside to KK over L is the battery life is a little worse IMO.
I dont think the memory leak issue is a result of someone not knowing what they are doing etc.

Thanks for all the advice everyone
yosmokinman said:
^Yeah I'll echo that. Lollipop is good. The people having problems don't know what they're doing. Flash the factory image.
If you want root you can use cfautoroot or simply flash twrp with fastboot then flash the su.zip
Click to expand...
Click to collapse
I'm fairly competent with computers (as I should be with a degree in computer science!) but this is all like a foreign language to me. I guess I'm better sticking with the toolkit for now until I'm familiar with all the lingo?
Masteryates said:
Personally, I'd stick go for 4.4.4, as 5, 5.0.1 & 5.0.2 all have a memory leak issue. You may also find more emulator compatability as Kit Kat has been around a year longer than Lollipop. The only downside to KK over L is the battery life is a little worse IMO.
I dont think the memory leak issue is a result of someone not knowing what they are doing etc.
Click to expand...
Click to collapse
Thanks. This is the sort of advice I was after and is why I mentioned what I was planning on using it for. The device has already downloaded 4.4.2 and wants to update to that. Is there a way I can manually go to 4.4.4? I'm worried it will just request an update from the Google server and try to jump straight to a version of 5

chunk3rvd said:
Thanks. This is the sort of advice I was after and is why I mentioned what I was planning on using it for. The device has already downloaded 4.4.2 and wants to update to that. Is there a way I can manually go to 4.4.4? I'm worried it will just request an update from the Google server and try to jump straight to a version of 5
Click to expand...
Click to collapse
If you unlock the bootloader then familiarise yourself with ADB and flashing factory images, you can manually flash any version of Android (That has been availible for your device,) manually. You dont need to be rooted to do this.
It also allows you to go back when you've made the mistake of updating, (but does wipe all of your data!)

It ended up offering me the updates incrementally anyway. I went from 4.3 > 4.4.2 > 4.4.3 > 4.4.4 which I'm currently on and will leave it there for now. It's downloaded 5.0.2 but I've skipped the install for the time being
Think I need to do a little reading up before I root the device as I haven't got a clue what some of you are talking about haha. Thanks for all the advice so far though

No problems.
I've had a few Nexus devices and never felt the need to root them. :angel:

yosmokinman said:
^Yeah I'll echo that. Lollipop is good. The people having problems don't know what they're doing. Flash the factory image.
If you want root you can use cfautoroot or simply flash twrp with fastboot then flash the su.zip
Click to expand...
Click to collapse
The majority of problems stem from Qualcomms crappy broken mess Adreno gpu drivers, hence the delayed
rollouts of Android for the Nexus 4 and 7 that both use the Adreno 320, don't be suprised if the Nexus 4 and 7 get a
Android 5.1.1 release instead.

For ppl new to nexus devices, wugfresh nexus root toolkit is a great tool until you get the hang of adb and fastboot. With a nexus you can always switch between android versions. You can always root, or go back to older versions of android. Updating to newer versions never hurts anything because you can always go back. Its a developers device so its very versatile. Try lollipop if you like, (I love it) and if its not your thing, just flash back to 4.4.4. I love this tablet.

madbat99 said:
For ppl new to nexus devices, wugfresh nexus root toolkit is a great tool until you get the hang of adb and fastboot. With a nexus you can always switch between android versions. You can always root, or go back to older versions of android. Updating to newer versions never hurts anything because you can always go back. Its a developers device so its very versatile. Try lollipop if you like, (I love it) and if its not your thing, just flash back to 4.4.4. I love this tablet.
Click to expand...
Click to collapse
You for got to mention the disclaimer if your tab came with 5.x.x out of box you cant go back to KK. Also a lot of us who recently bought Nexus 7, I have 3 that I have acquired, came with 5.0.1 installed are having issues with partitions/memory mounting in recovery. Some sort of revision done in the latest batch sent out. If his tab came with 5.0.1 or higher and has his bootloader at FLO 4.04 he may have problems trying to go back with either bootloops and what not.

masterchiefb117 said:
... with 5.0.1 installed are having issues with partitions/memory mounting in recovery...
Click to expand...
Click to collapse
Seems to be solved in TWRP_multirom_(flo|deb)_20150328 (updated to 2.8.6.0)
See http://forum.xda-developers.com/showpost.php?p=45886569&postcount=1

Help - Updating s4 mini i9192

I have an s4 mini i9192 4.2.2 and I want to upgrade it to 4.4.2. My current csc country is in Saudi Arabia and I cant find any updated firmware for that. How to update and which firmware can i use?

atnasan said:
I have an s4 mini i9192 4.2.2 and I want to upgrade it to 4.4.2. My current csc country is in Saudi Arabia and I cant find any updated firmware for that. How to update and which firmware can i use?
Click to expand...
Click to collapse
The only way to update is to use a Custom ROM.

Same problem for my Devise S4 mini Dous GT-I9192, Officially you will not find any Samsung Stock Rom higher than 4.2.2 the only way to look for Custom Roms the only problem you will face both Sims are on always as all Custom Roms based on CM. other problems are minor specially when you use Stable Custom Rom

Alaioby79 said:
Same problem for my Devise S4 mini Dous GT-I9192, Officially you will not find any Samsung Stock Rom higher than 4.2.2 the only way to look for Custom Roms the only problem you will face both Sims are on always as all Custom Roms based on CM. other problems are minor specially when you use Stable Custom Rom
Click to expand...
Click to collapse
I'm pretty sure the sim problem is in Nougat roms. You can turn off sims in Marshmallow.

Help
I tried to update it using the odin way and it had an error. What to do now? The other methods aren't working either.

atnasan said:
I tried to update it using the odin way and it had an error. What to do now? The other methods aren't working either.
Click to expand...
Click to collapse
which instructions are you following?
what rom are you flashing?
What was the error msg?

atnasan said:
I tried to update it using the odin way and it had an error. What to do now? The other methods aren't working either.
Click to expand...
Click to collapse
Cna you be more specific. Please?

help
android(dot)gs how to manually update galaxy s4 mini duos to android 4.4.2 kitkat
This is the site I used.
I cant remember the error msg but it popped up when I pressed start.
I have no idea what I am doing. I never tinkered with my phone before so I don't know what you mean when you say flashing a rom. I just googled how to update and I found this site. I'm a complete novice at these things.
The other methods I used are Kies and the normal way in settings.

atnasan said:
android(dot)gs how to manually update galaxy s4 mini duos to android 4.4.2 kitkat
This is the site I used.
I cant remember the error msg but it popped up when I pressed start.
I have no idea what I am doing. I never tinkered with my phone before so I don't know what you mean when you say flashing a rom. I just googled how to update and I found this site. I'm a complete novice at these things.
The other methods I used are Kies and the normal way in settings.
Click to expand...
Click to collapse
First you need to take some time to learn all about "flashing" (writing new software [firmware really] onto hardware ie chip in your phone), as doing it wrong can "brick" your phone (turn phone into a brick, yes never work again!), eg flashing wrong model number eg I9190 firmware to your phone.
I couldn't find the tutorial you mention in first 5 pages of search, do you mean this one?
http://android.sc/update-android-4-4-2-i9192xxucng2-kitkat-on-samsung-galaxy-s4-mini-duos/
strictly speaking you should not flash firmware from another region as it can stop your phone working properly. But it is possible, though I don't know about your phone or these tutorials as I haven't read them and checked all files etc
This tutorial has more info, that may help you if you decide to continue (at your own risk!)
http://techbeasts.com/update-galaxy-s4-mini-duos-i9192-to-android-4-4-2-kitkat-official-firmware/
in particular it says back up your EFS which is particular important when flashing different region in case you mess up (save to external SD & copy to PC also)
by flashing you will wipe all your personal data stored on internal SD eg photos, msg, notes, calendars etc so you need to back them up to PC (or external SD)
Kies wont let you flash that ROM as it's from wrong region (I think). Odin will though.
Nobody can help unless you give us the exact error msg + other info like Odin ver, file names etc
If you are going to flash a new ROM you might want to flash a newer custom ROM, like Cyanogenmod 13, Linage 13 or 14 (Android versions 6 & 7 respectively), you'll get new features, much better battery life, security and privacy though you will lose Samsung apps like notes etc

Help
I tried it again using the firmware from TT. This was before I saw your reply and I got this message. It was stuck for a while and I plugged in my internet adapter and it said it failed. ( in the pictures)
If you type in this,"manually update i9192 kitkat" on google, it should be the first site to come up which is the one I used.
My phone was made in china, bought in the USA, being used in the Caribbean but has Saudi Arabia codes. I don't understand. The last update from them is 2014. I used the one from Russia and TT. Both of them failed.
Should I stick with updating it to 4.4.2, flash a newer ROM ? Would this 'newer ROM' be able to work on my phone?
Or drop the whole thing because I have no idea what I'm doing?
Is there a low chance of me bricking my phone if I flash a newer ROM?

atnasan said:
I tried it again using the firmware from TT. This was before I saw your reply and I got this message. It was stuck for a while and I plugged in my internet adapter and it said it failed. ( in the pictures)
If you type in this,"manually update i9192 kitkat" on google, it should be the first site to come up which is the one I used.
My phone was made in china, bought in the USA, being used in the Caribbean but has Saudi Arabia codes. I don't understand. The last update from them is 2014. I used the one from Russia and TT. Both of them failed.
Should I stick with updating it to 4.4.2, flash a newer ROM ? Would this 'newer ROM' be able to work on my phone?
Or drop the whole thing because I have no idea what I'm doing?
Is there a low chance of me bricking my phone if I flash a newer ROM?
Click to expand...
Click to collapse
Is your phone connecting properly? There is nothing showing in the id com port window at top left, when connected properly there will be, or does that disappear when error msg shows? I can't remember. Possible it means your drivers are not installed properly, or try newer ones here (though not always better)
https://forum.xda-developers.com/showthread.php?t=961956&page=61
(scan with anti virus first)
You might want to try a newer version of Odin
Though first thing is try another usb cable. Also usb cable must always be connected to usb connectors attached direct to the PC pcb (normally at the back (or side on laptop), not an extra one like at the front and definitely not thought an external usb hub.
Your phone is probably grey market, nothing wrong with that, mine is too (mine is German phone, bought from HK used in Australia). However if pre owned it could have had other roms flashed,
It's entirely up to you which version of Android you want to use, they will all work on your phone, though anything higher than 4.4.2 will be a custom ROM, most of us here run them ie Cyanogenmod (CM) or Linage (LOS) which has recently replaced CM. LOS still has a few little issues but it is already stable, though a couple of small bugs. The good thing is you will get regular updates for many, including the monthly security updates, and they have a many new features too. To flash these you will however need to unlock your bootloader and use TWRP for the recovery.
I suggest you make a nandroid back up as soon as you install TWRP, then you can always go back to your current setup.

Alaioby79 said:
Same problem for my Devise S4 mini Dous GT-I9192, Officially you will not find any Samsung Stock Rom higher than 4.2.2 the only way to look for Custom Roms the only problem you will face both Sims are on always as all Custom Roms based on CM. other problems are minor specially when you use Stable Custom Rom
Click to expand...
Click to collapse
Where we can find samsung official ROMs? There is some 4.4.2 roms available in
http://www.sammobile.com/firmwares/database/GT-I9192/

hnikaein said:
Where we can find samsung official ROMs? There is some 4.4.2 roms available in
http://www.sammobile.com/firmwares/database/GT-I9192/
Click to expand...
Click to collapse
not for S4 mini Dous GT-I9192, all Stock ROMs for our devise is only 4.2.2

Alaioby79 said:
not for S4 mini Dous GT-I9192, all Stock ROMs for our devise is only 4.2.2
Click to expand...
Click to collapse
in this page you can also see we can upgrade to 4.4.2:
http://www.gsmarena.com/samsung_i9190_galaxy_s4_mini-5375.php

hnikaein said:
in this page you can also see we can upgrade to 4.4.2:
http://www.gsmarena.com/samsung_i9190_galaxy_s4_mini-5375.php
Click to expand...
Click to collapse
Samsung said it will update to 4.4.2 but it did not, GSMARENA.COM sometimes not offering or updating to actual status and I had communicated with SAMSUNG but no reply from them however S4 mini is from S-Line which shall be more valuable to SAMSUNG but they did not care.

Alaioby79 said:
not for S4 mini Dous GT-I9192, all Stock ROMs for our devise is only 4.2.2
Click to expand...
Click to collapse
Maybe you mean in some regions. Because otherwise your statement is completely false. I had the 4.4.2 stock firmware on duos for instance.

xdmusicbx said:
Maybe you mean in some regions. Because otherwise your statement is completely false. I had the 4.4.2 stock firmware on duos for instance.
Click to expand...
Click to collapse
Yes for some region only not for all variants

Help me
Yes, it's connected properly. It is highlighted blue by ID:COM before the error occurs. I just installed the drivers you sent me.
I did the update with the latest Odin and I still got the error message.
Only my original cable connects to the computer so I cant try any others. Once it's connected and appears in 'my computer', doesn't that means its connected?
It wasn't pre-owned but how would I know if a ROM is already installed?
I think I want to upgrade to the 4.4.4 and IF I get it to work, I will then upgrade to the latest one. I'm assuming this is easier and since I have no idea what I'm doing or where to go, I should definitely go with the easiest first. Right ? You lost me at Cyanogenmod. This is guy stuff.
Can you direct me where I need to go please with some instructions ?
Thank you

you should quote msg or use @atnasan to be sure your reply is seen by other poster.
If I remember correctly (it's been a long time) when odin gets stuck at get pit it is normally a communication issue even though your phone appears to show up correctly in it. You must run Odin with full admin rights on your pc. Some used to say only the Odin for S4 Mini & ver 3.07 or 3.09 (I think it was) would work (see the S4 mini Odin thread) Some firewalls can cause issues so turn them off (maybe reboot with antivirus off). You need a usb port that connects direct to the motherboard & original usb cable (really just needs a good quality cable in good condition, I think, just not one of those thin $5 ones).
If that doesn't work try to borrow another USB cable or try another PC or laptop.
Luckily I've never had any issues, all Odin ver worked, I just right click on Odin to run as admin from my user account on Windows 7 64bit even with Zonealarm firewall running. But other people have had problems.
No need to update to 4.4.2 etc if you will try to install a custom ROM like Linage or Cyanogenmod or one of the more customised . (in fact on my I9195 updating to 4.4.2 loaded a new bootloader, which had a stronger ver of knox)
If Odin won't flash stock you can try flash TWRP with Odin then use that to try flash a custom ROM from your sd card using TWRP instead of using Odin. Use TWRP from the neozone75 thread, I am using the tryout ver 3.1 which is working perfectly, so I suggest that. (ver 3.0..3 gave me errors checking the md5, though most people don't both with that check, so would work). Linage OS is about to change official version from LOS13 to LOS14 (Android 6 & 7) so you might want to wait a week or so if you choose that ROM, as I don't think there will then be any updates to LOS13 after that as each phone on LinageOS downloads section only has 1 Android version supported.

Question Install pure Android on SM-S901E

Hi! I bought my phone recently and I would like to install pure android on this device. Is this possible? If so, I would also like to know if it would be possible to download this operating system directly from Google's server (just as we download Windows directly from the Microsoft website at https://www.microsoft.com/software-download, for example). The second question is for security reasons.
Thank you!

Since no one else has answered, I'll try:
I'm going to assume what you mean by "pure" Android is the unlocked version of Samsung's firmware for your particular phone model. If you don't have some version of the Samsung Galaxy s22, then you're asking your question in the wrong place.
First you need to find out whether your phone is locked, and if so, whether it can be unlocked.
Then, watch this video for an overview:
If you decide you would like to continue, an easier way of obtaining firmware is from samfw.com.
The video mentioned above includes links to the two different types of Odin, which is the software you would use to flash the firmware onto your phone.
In general, since you haven't done this sort of thing before, I would recommend triple checking every step, as there are certain mistakes you can make that will render your phone unusable.
Good luck!