It seems after I do any Rooting process , I get stuck with " Custom " in status of the phone , instead of " Official " , and hence , no OTA official updates .
I want to keep Root while still receiving the latest updates from samsung as I see , Samsung makes updates almost every month .
so how this can be done ?
now I have the XXCMA5 4.1.2 JB installed and rooted with CF-root .
Thanks in advance.
Worked Solution is down there
sertorio10 said:
View attachment 1720489
I did it with triangle away, the option above.
Click to expand...
Click to collapse
1- Root with keeping Stock Recovery
2- with triangle away installed enable option " enable modified system workaround "
3- Reboot the device , wait untill root gets back again .
4- congrats , now system official , and you can receive updates
Big thanks to
sertorio10 http://forum.xda-developers.com/member.php?u=4514413 for posting this help
chainfire for his great app http://forum.xda-developers.com/member.php?u=631273
triangle away http://forum.xda-developers.com/showthread.php?t=1494114
at least worked for me , Sorry if this solution was known before , But it is new for me .
asalah0923 said:
It seems after I do any Rooting process , I get stuck with " Custom " in status of the phone , instead of " Official " , and hence , no OTA official updates .
I want to keep Root while still receiving the latest updates from samsung as I see , Samsung makes updates almost every month .
so how this can be done ?
now I have the XXCMA5 4.1.2 JB installed and rooted with CF-root .
Thanks in advance.
Click to expand...
Click to collapse
Have you ever heard the phrase "have your cake and eat it too"?
What it means is that you want two incompatible things, where the selection of one precludes the other.
You can receive and apply an OTA update while you're rooted, but the OTA update flashes a new ROM to the device and in the process erases the rooting that was applied.
You need to root again
You need to decide why you need root and is it worth your effort to maintain it or is it less hassle to just keep the device stock and receive the OTAs
Personally I chose root and then downloaded and installed Mobile Odin, Triangle Away etc so that I can decide what to download and flash and Mobile Odin will automatically root it for me as it applies.
Bulbous said:
Have you ever heard the phrase "have your cake and eat it too"?
What it means is that you want two incompatible things, where the selection of one precludes the other.
You can receive and apply an OTA update while you're rooted, but the OTA update flashes a new ROM to the device and in the process erases the rooting that was applied.
You need to root again
You need to decide why you need root and is it worth your effort to maintain it or is it less hassle to just keep the device stock and receive the OTAs
Personally I chose root and then downloaded and installed Mobile Odin, Triangle Away etc so that I can decide what to download and flash and Mobile Odin will automatically root it for me as it applies.
Click to expand...
Click to collapse
:laugh: I didn't know that , I don't actually konw what Root does except some permissions that give me some cool features and control over my device , that is the extend of my knowledge :laugh: , actually I think it worth it , to keep root rather having the stock ,I need it for adblock and marketenabler , titanuim backup etc ...
what matters for me , is the risk and the 1 GB Rom that I have to download every time I want to update , and also sometimes if something goes wrong I have todo a full wipe and then a clean flash ,
but with the stock Rom I only download a 20 to 40 Mb each update ( for me it is more safe update ) and less time
Thanks
Well you can use the cf root method where in you do not install custom recovery yet root your device that way you can have the both worlds
asalah0923 said:
:laugh: I didn't know that , I don't actually konw what Root does except some permissions that give me some cool features and control over my device , that is the extend of my knowledge :laugh: , actually I think it worth it , to keep root rather having the stock ,I need it for adblock and marketenabler , titanuim backup etc ...
what matters for me , is the risk and the 1 GB Rom that I have to download every time I want to update , and also sometimes if something goes wrong I have todo a full wipe and then a clean flash ,
but with the stock Rom I only download a 20 to 40 Mb each update ( for me it is more safe update ) and less time
Thanks
Click to expand...
Click to collapse
Yeah Titanium Backup is a pretty good reason. It's one of my main reasons for rooting.
As you say, you want to keep root so really the decision is made. You accept the work load of re-rooting because you want OTAs at 40 - 50 MB a pop. You spend your time re-rooting
I, on the other hand, don't accept the re-rooting workload. I'm not bothered by the OTA updates, since I often flash another regions newer ROM, hence the Mobile Odin. I spend my time downloading
Incidentally, I've only found that you need to do the full wipe if you're going backwards in Android Versions.
From 4.0.X to 4.1.X no wipe required, from 4.1.1 to 4.1.2 no wipe required. But revert to 4.0.X from 4.1.X means that the upgraded programs MUST be wiped so that the older ones can be used.
samir_a said:
Well you can use the cf root method where in you do not install custom recovery yet root your device that way you can have the both worlds
Click to expand...
Click to collapse
cf root don't change stock recovery okay , keep me close as possible to stock and keeps the Rom clean , but it does make the device status Custom , so no updates are there
triangle away!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did it with triangle away, the option above.
I belive ZedoMax has a "Method 1" which involves downloading a root injected Rom which flashes over using ODIN. I'm in the OP's same boat. I want to keep mine pretty much stock, not wanting to mess with Custom Roms too much but having the ability to have ROOT apps. I actually got my NOTE yesterday and it OTAd to 4.1.2. My plan today is to flash the older ROM back from August that has the root injected ROM and apparently that will let you have OTA updates while keeping root.
Can anyone confirm this?
Another question, is there any difference in, say, Europes stock rom versus United States. It seems that I can find every country's ROM EXCEPT for United States'.
sertorio10 said:
View attachment 1720489
I did it with triangle away, the option above.
Click to expand...
Click to collapse
I've tried this option , only disables the Root for a while , still when connecting to software update , it tells me I 'm modified and that I can't receive updates
deeselcyde said:
I belive ZedoMax has a "Method 1" which involves downloading a root injected Rom which flashes over using ODIN. I'm in the OP's same boat. I want to keep mine pretty much stock, not wanting to mess with Custom Roms too much but having the ability to have ROOT apps. I actually got my NOTE yesterday and it OTAd to 4.1.2. My plan today is to flash the older ROM back from August that has the root injected ROM and apparently that will let you have OTA updates while keeping root.
Can anyone confirm this?
Another question, is there any difference in, say, Europes stock rom versus United States. It seems that I can find every country's ROM EXCEPT for United States'.
Click to expand...
Click to collapse
I have installed a Rom then rooted it ( without custom recovery ) , and then flashed other one over it Via Odin Pc , the Root was gone , and I 'm official again
So I Rooted it again , and with superSU pro survival mode on , I flashed a new ROM over it via Odin mobile , and the Root was still there , and I'm modified and can't get updates
So apparently till now there is no way to keep your device Rooted with OTA updates , If you flashed an old ROM with Root injected you will lose updates ,
and For the US , apparently , only n8010 or n013 or n8020 are there , to my knowledge N8000 didn't hit the market there officially ,
only wifi versions are official
It Worked ( updated in the next post )
sertorio10 said:
View attachment 1720489
I did it with triangle away, the option above.
Click to expand...
Click to collapse
Actually it works , thanks alot :good:
At first I did try it , while the Root was disabled ,didn't work
I did try it again after a couple of Reboots , and after the Root is enbaled again ( a couple minutes after Booting ) , the Device was Official and I 'm able to get Updates
Thanks
asalah0923 said:
It seems after I do any Rooting process , I get stuck with " Custom " in status of the phone , instead of " Official " , and hence , no OTA official updates .
Click to expand...
Click to collapse
OTA do not depend on status "official" in the settings app. OTA require the original recovery, but I have a rooted N8000, which status is "custom" in settings app and "official" with flash counter 0 in recoverey.
And I am offered OTAs.
Nevertheless, I download the firmware updates from sammobile and flash them with Mobile Odin on the device to maintain root even through the upgrade to avoid the hassle to flash/reflash recovery.
akxak said:
OTA do not depend on status "official" in the settings app. OTA require the original recovery, but I have a rooted N8000, which status is "custom" in settings app and "official" with flash counter 0 in recoverey.
And I am offered OTAs.
Nevertheless, I download the firmware updates from sammobile and flash them with Mobile Odin on the device to maintain root even through the upgrade to avoid the hassle to flash/reflash recovery.
Click to expand...
Click to collapse
I 've read somewhere here in this forum that to receive official updates from Samsung , it depends on a lot of factors , one of them is the stock recovery for sure , actually I 've tried a lot to get updates with status set to "custom" to receive updates , although having stock recovery , but still receive that my Software is modified and that I can't receive updates .
I think that after the last updates that Samsung has done , it is not allowed to have software update when you are modified ( custom on status ) ,
as I used to update my SII on GB and ICS , with Root injected normally , and also exynosabuse app works perfectly , and I didn't face any problems there , and yes it was dependent on the recovery .
as for now I think things have changed a bit , at least for me ,
the only way that worked for me , to keep Root and Updates together , is with the triangle away app option that was mentioned in a previous post by sertorio10 .
Since several versions, I flashed the full firmware with Mobile Odin from sammobile. After having had rooted the device (which I obtained the day after it became available) with the CWM-method, I used Triangle Away to reset the flash counter.
As I said, the status in recovery of my device is "official", in the settings app it is custom. For all recent updates, I received the OTA (but to avoid trouble, I installed the full firmwarwe and kept root with Mobile Odin's root injection when flashing).
So if i have siyah kernel it wouldn't work
Related
This is getting frustrating!
Once a full uk rom became available I did a full, clean install using Mobile Odin to retain root. When I check status immediately the report is 'official'. Now the problems begin. I have tried a restore from Titanium Backup, a manual install of all my apps one by one and also just letting Google Play do its stuff, and after each sometimes within a couple of hours, this last time I managed overnight, my status is reported as 'custom'.
Any ideas as to what is causing this please?
Which status you're talking from? The one in the settings? That happens sooner or later when the Note is rooted, the systems seems to check this from time to time and set the status to "Custom". But why bothering, it does not harm. Even OTA do work with that.
The status custom in Odin download mode is a different store (but it remains official as long as not recovery or other non-Samsung flash is done).
Yes, the one in settings. Once the status changes to custom if I tap 'software update' then do a check I get a message saying my device has been modified so updates unavailable.
Then you did anything else, my status there is also custom, but I was offered the latest OTA without problems. Nevertheless, I downloaded the latest update from sammobile and flashed it with Mobile Odin. So I don't care about that status.
You are rooted ??
If so run Triangle away to reset rom counter .
Flash stock rom via Odin then factory reset should put device to normal status .
Root can interfere with or prevent OTA use Kies and reroot .
jje
Why so complicate?
Get the update/rom from sammobile or here, use Mobile Odin and flash the update on the tablet. With the pro version, the tablet remains rooted and everything is fine. Mobile Odin is an excellent tool and worth the few bucks to get the pro version.
Odp: [Q] 'custom' status with official rom
I have the same problem. I tryied to install script sd2internalsd and Iinstall busybox and i think that orogram change my status to custom. Now - my note cant take an update.
I try use Triangal away but das not work. Any idea?
tapnięte z mojego Note'a 10.1 3G
Hi guys, a couple of months ago I've rooted my new S2+ and after Alex posted the new 4.2.2 I've flashed my device with RDS_GT-I9105P-XEO-I9105PXXAMC2 (topic here GT-I9105/I9105P Stock Prerooted Firmware Without loss of warranty(4.2.2) http://forum.xda-developers.com/showthread.php?t=2334103).
So far it is working perfect! This week I've received a notification, that there is a new update available OTA for my device, so I've decided to download and install it. I've downloaded it, the phone restarts and starts to install the "new update", but at 25% shows an error (the Android guy wearing the red triangle etc. and reboots automatically).
After the restart the OS boots normally and is working OK as previous.
My question is: Since my phone has a prerooted stock FW (4.2.2) and is rooted at the same time running CWM, why I can't install the latest updates OTA?
If CW is causing this, why am I able to get the OTA update notification?
Thanks for the replies.
boyansky78 said:
Hi guys, a couple of months ago I've rooted my new S2+ and after Alex posted the new 4.2.2 I've flashed my device with RDS_GT-I9105P-XEO-I9105PXXAMC2 (topic here GT-I9105/I9105P Stock Prerooted Firmware Without loss of warranty(4.2.2) http://forum.xda-developers.com/showthread.php?t=2334103).
So far it is working perfect! This week I've received a notification, that there is a new update available OTA for my device, so I've decided to download and install it. I've downloaded it, the phone restarts and starts to install the "new update", but at 25% shows an error (the Android guy wearing the red triangle etc. and reboots automatically).
After the restart the OS boots normally and is working OK as previous.
My question is: Since my phone has a prerooted stock FW (4.2.2) and is rooted at the same time running CWM, why I can't install the latest updates OTA?
If CW is causing this, why am I able to get the OTA update notification?
Thanks for the replies.
Click to expand...
Click to collapse
that is because it is a modded firmware
safariking said:
that is because it is a modded firmware
Click to expand...
Click to collapse
I understand that the FW is modded, as the previous one (4.1.2), which I've downloaded from here and installed on my G2+. But with 4.1.2 at that time I wasn't able to check for any updates for my OS. Every time I've checked manually for updates, the OS gave me error message, that this is not possible. And now with 4.2.2 I am not only able to check if my FW is the latest, but also to download and install 1/4 of the updates. I am trying to find the algorithm here.
boyansky78 said:
I understand that the FW is modded, as the previous one (4.1.2), which I've downloaded from here and installed on my G2+. But with 4.1.2 at that time I wasn't able to check for any updates for my OS. Every time I've checked manually for updates, the OS gave me error message, that this is not possible. And now with 4.2.2 I am not only able to check if my FW is the latest, but also to download and install 1/4 of the updates. I am trying to find the algorithm here.
Click to expand...
Click to collapse
I will say it again
It is not possible to check for updates because the Firmware is modded and not original anymore that's why!!!
Hi "safariking",
In the current situation we have two identically modded FWs, but a different outcome.
It's very nice of you to take the time to answer my question so fully That's why I'd like to thank you for the effort. Herewith I am closing the topic.
Cheers.
No probs guy i will repeat myself 100 times no problem
Verstuurd van mijn GT-I9105P
safariking said:
No probs guy i will repeat myself 100 times no problem
Verstuurd van mijn GT-I9105P
Click to expand...
Click to collapse
chill down everyone safari bro,this guy trying to say he got updated with mod fw,just when reach certain percent,the downloaded file seems corrupted. Now i understand mod fw can't even received the ota file,but how this process is allowed, and what happened with the ota file he downloaded?
either way,it's pointless,1st the phone fail to update completely(stuck at 25%), 2nd i don't think this problem can be solved.
cheers everyone~ :highfive:
nickchk said:
chill down everyone safari bro,this guy trying to say he got updated with mod fw,just when reach certain percent,the downloaded file seems corrupted. Now i understand mod fw can't even received the ota file,but how this process is allowed, and what happened with the ota file he downloaded?
either way,it's pointless,1st the phone fail to update completely(stuck at 25%), 2nd i don't think this problem can be solved.
cheers everyone~ :highfive:
Click to expand...
Click to collapse
Hi Nick,
Thanks for your reply. You are reading my mind. The issue is really interesting & I think it is worth discussing this.
Safari is right, when he says that FW upgrade OTA for customized ROM is not possible. This is of course true and no one has ever doubted it. This is why when I had the 4.1.2 installed on my G2+ no update was even possible. Droid detects immediately, that the OS has been modified and that you are not running stock ROM.
Okay, so far so good.
Now I have pre-rooted 4.2.2 installed on my phone. When I hit the "Check for update button" it detects that my OS is genuine (although it is not), downloads the whole update package (see screenshot), restarts the phone (part of the update process) and starts installing the update. When the installation reaches 25%, an error message appears saying, that an error has occurred. The phone restarts and loads the "old" OS.
I have tested this a several times and it always hangs on 25%.
The question is NOT why I CAN'T install OTA updates on modified ROM. The question is why I CAN download and install OTA updates on modified ROM.
My suggestion is that:
ROM 1 (4.1.2) had a modified kernel. That's why the OTA updates were not possible.
ROM 2 (4.2.2) is pre-rooted. And I assume it is just stock FW (kernel not modified) with few modifications in the user permissions. This would explain the OTA update and why it reaches download mode and hangs on 25% of the installation.
I hope this brings more clarification to the situation and this would be useful to all members of the forum.
Cheers!:highfive:
I have randomly come across and read posts and topics on this in the other devices' forum.
If I remember correctly, it is the custom recovery, i.e Cwm or twrp that blocks or interrupts the OTA process. 2 reasons why: you'll lose root access if the update went through. Secondly, if a user freezes or uninstalls stock apps like S Voice, Chat On etc, there will be trouble.
There are some ways of allowing an OTA to get pass a custom recovery. I think TWRP has this feature. Again, I stand corrected here lol.
Heard of OTA Root Keeper but no idea how it works
Sent from my GT-I9105 using xda app-developers app
I have a Sprint Galaxy S5 that was up to the latest and greatest version of Android (Sprint's version, anyway) the other day (5/19/15). I decided to root and flash a variant of CyanogenMod 12.1 that was highly recommended by some others. The root and ROM flash were successful and uneventful. However, this ROM and many others based on CyanogenMod 12.1 are all experiencing issues with Bluetooth and skipping of audio. This has been mentioned in several other posts recently. Rather than suffer any more with this, I decided to download the latest stock firmware for Sprint S5 and get it back to the way it was before I rooted and flashed it. I downloaded Odin 3.07 and the stock ROM file. I followed what was shown in this post. I csn't seem to get this to work.
Here is the error I get in Odin:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is the error I see on my phone:
I've been able to flash lots of other ROMs (although they are all based on CM 12.1 with the same Bluetooth bug, so they are not usable for me). I've been able to put MOAR on, and that is working OK, but I would really like to get this back to the way it was. What am I doing wrong? Did I miss something? Have I missed something I should be doing?
Forgot to mention that I am currently running on MOAR v 6.2 OA6.
So moar rom is working? You can't downgrade the firmware if you took the od3 update or whatever the revision is that just came out. They locked out flashing back to previous builds in the latest firmware I've heard.
Interesting. Yes, MOAR is working just fine. I guess, since it's basically the same as stock Samsung, I should just use it. I like the extra tweaks and tools built in to it. But I really liked CM 12.1 (except for the stupid issues with Bluetooth). I guess I'll stick with MOAR until some gets a stable ROM for CM 12.1 or later out. Hopefully that won't be too far off.
What is your baseband version? As @tdunham stated the latest ota killed it from downgrading. So if you arent on OA6 you wont be able to odin that Stock firmware or any other earlier versions. You will have to find the full OC3 tar
May is Motorcycle Awareness Month Sent from my Galaxy Note 3
I have baseband version G900PVPU2BOD3. Does the baseband remain intact, regardless of the ROMs I have flashed?
Baseband changes, but bootloader doesn't. That is why you get a fail in Odin trying to install stock. Its kind of like a locked bootloader per say. Not really locked, but not able to downgrade. All in all the update to OD3 did what it was suppose to do by preventing a "thief" from factory resetting your device. Although that doesnt matter to people like us because we root for reasons and need that option to downgrade
May is Motorcycle Awareness Month Sent from my Galaxy Note 3
So is there any option to get my phone back to the stock ROM I had on it before I started all of this? Is that ROM available somewhere? I don't think I've seen it. I don't mind using MOAR. I had plans for doing some phone swaps after getting a new phone, and my wife will probably end up with mine. I don't necessarily want to give her a phone that has too much tweaking and settings that she won't understand how to use.
grberk said:
So is there any option to get my phone back to the stock ROM I had on it before I started all of this? Is that ROM available somewhere? I don't think I've seen it. I don't mind using MOAR. I had plans for doing some phone swaps after getting a new phone, and my wife will probably end up with mine. I don't necessarily want to give her a phone that has too much tweaking and settings that she won't understand how to use.
Click to expand...
Click to collapse
You've taken the OTA to OD3 if I read that right. As I understand it, as of now at least, you can't downgrade the firmware with OD3.
Edit: What @elwood says. I better go get some coffee
grberk said:
I have a Sprint Galaxy S5 that was up to the latest and greatest version of Android (Sprint's version, anyway) the other day (5/19/15). I decided to root and flash a variant of CyanogenMod 12.1 that was highly recommended by some others. The root and ROM flash were successful and uneventful. However, this ROM and many others based on CyanogenMod 12.1 are all experiencing issues with Bluetooth and skipping of audio. This has been mentioned in several other posts recently. Rather than suffer any more with this, I decided to download the latest stock firmware for Sprint S5 and get it back to the way it was before I rooted and flashed it. I downloaded Odin 3.07 and the stock ROM file. I followed what was shown in this post. I csn't seem to get this to work.
Here is the error I get in Odin:
Here is the error I see on my phone:
I've been able to flash lots of other ROMs (although they are all based on CM 12.1 with the same Bluetooth bug, so they are not usable for me). I've been able to put MOAR on, and that is working OK, but I would really like to get this back to the way it was. What am I doing wrong? Did I miss something? Have I missed something I should be doing?
Click to expand...
Click to collapse
i have same problem i cant restore to stock rom in odin says aboot error no work with OA6,NDK
i havre installed custom recovery and root i can a install a custom rom OA6 ??WIth bootloader OD3 or i need the OD3 restore !!
ENSENADAS said:
i have same problem i cant restore to stock rom in odin says aboot error no work with OA6,NDK
i havre installed custom recovery and root i can a install a custom rom OA6 ??WIth bootloader OD3 or i need the OD3 restore !!
Click to expand...
Click to collapse
There's only 9 other posts here. Didn't you read them to get your Answer?
Ramer said:
There's only 9 other posts here. Didn't you read them to get your Answer?
Click to expand...
Click to collapse
no!!!
ENSENADAS said:
no!!!
Click to expand...
Click to collapse
Oh, ok.
Can we fix this?
Ramer said:
You've taken the OTA to OD3 if I read that right. As I understand it, as of now at least, you can't downgrade the firmware with OD3.
Edit: What @elwood says. I better go get some coffee
Click to expand...
Click to collapse
As I have this exact same issue and would like my phone back on a stock firmware. Is there anyway to flash the current firmware that the sprint device is on and not downgrade? or am i stuck for a while ? ( I'm also on the moar rom and have tried stupidly all the older firmwares... i also tried the s5 sprint oa6 with no luck. Do i need to go even further forward?
Much Appreciated
-Colin
oreo8631 said:
As I have this exact same issue and would like my phone back on a stock firmware. Is there anyway to flash the current firmware that the sprint device is on and not downgrade? or am i stuck for a while ? ( I'm also on the moar rom and have tried stupidly all the older firmwares... i also tried the s5 sprint oa6 with no luck. Do i need to go even further forward?
Much Appreciated
-Colin
Click to expand...
Click to collapse
If you're already on OD3, you can't do anything about it. You can however flash any custom rom from OA6, MOAR 6.2 works just fine with OD3.
Ramer said:
If you're already on OD3, you can't do anything about it. You can however flash any custom rom from OA6, MOAR 6.2 works just fine with OD3.
Click to expand...
Click to collapse
Thank you. Presuming that there is going to be a fix and or firmware update in the future ?
oreo8631 said:
Thank you. Presuming that there is going to be a fix and or firmware update in the future ?
Click to expand...
Click to collapse
No way of knowing, since I was already rooted and on MOAR, I'm still on OA6 firmware and don't plan to change that.
help s5 back to stock
i have a sprint s5 that im trying to flash back to stock. none of the ## codes work on it. so im hoping going back to stock can fix. im rooted on (i think) a stock rom. already factory reset and still im rooted and ## codes dont work. please help me restore this with odin. not sure on odin use either but i gotta try lol
videokid14 said:
i have a sprint s5 that im trying to flash back to stock. none of the ## codes work on it. so im hoping going back to stock can fix. im rooted on (i think) a stock rom. already factory reset and still im rooted and ## codes dont work. please help me restore this with odin. not sure on odin use either but i gotta try lol
Click to expand...
Click to collapse
what baseband are you on?
youdoofus said:
what baseband are you on?
Click to expand...
Click to collapse
hi. sorry i forgot to update this post. i was able to go back to stock by downloading the stock odin file and used odin to flash back and it worked. however now that im stock and rooted again im looking to load moar rom on my s5. if u want to help me??
I have successfully rooted my note 12.2 - thanks to this awesome forum.
With that I can't do OTA or use Kies to stay up to date. So I'd like to know how I can stay up to date as Samsung releases new firmwares? For example I just downloaded the newly released 5.0.2 from Samobile and flashed it with Odin 3.09. That went well but of course it wiped my machine so I'm starting fresh again. I'd like to be able to stay up to date with out a complete re-wipe each time if possible. Thoughts?
As a long time root user I can tell you that the cardinal rule is that one should give up the notion of getting OTA updates for good once one roots for the simple fact that with each major OTA update comes the risk of losing root forever should the update lock the doors on the exploit used to gain root to begin with.
Casual root users are best served by watching forum threads after updates are released to see how more experienced users are fairing with getting their devices up to date. The exception to this is if a custom ROM is installed and the developer updates the ROM periodically to integrate the updated software or features that the device manufacturer releases. Even then, if a major update is released that let's say jumps to a new system like kitkat to lollipop there's a chance that a full wipe can't be avoided. ROM developers typically warn users when clean installs are required, and some even distribute their own OTAs.
I'm a religious user of titanium backup, and I will often dirty flash a ROM update or use prior titanium backups to restore data but this can be risky business when major updates are released because if software or drivers change from one major firmware release to another a backup of a particular application may no longer be compatible and stability may be affected upon restore.
Bottom line, if you want lollipop on your note pro, rooted, can live with the current bluetooth issues and want to be able to update further easily while retaining root then go with a custom ROM like civs and just monitor the thread of that ROM for updates.
Hope this helps.
Thanks for the excellent advice. One two more more question on the topic. I had root on KitKat, but after flashing the new stock Lollipop via Odin, I lost root. So after installing the stock Lollipop I had to re-do the root flash via Odin to get root back, thankfully it all worked out. (Lollipop is awesome BTW).
Questions:
1. Was I in danger of forever losing root as you state above or was this a safe route? I understand that OTA and even Kies can make me lose root forever, but what about flashing a stock via Odin?
2. Are you saying that next time there's an update I could try to dirty flash the ROM via TWM (after doing a good backup via Titanium of course)? Basically find ROM on samobile, download, copy to SD card and dirty flash away using these suggestions: https://www.reddit.com/r/Android/comments/sthr8/dirty_flashing_what_it_is_and_is_not_lets_set_the/
Typically to keep root the stock recovery is replaced with a custom one, TWRP is the main one used for our device. Stock updates from Samsung downloaded as OTA will typically fail to flash in TWRP. Odin flashing stock images will erase everything including the custom recovery, thus causing loss of root. In other words you'll typically lose root one way or another and the key to retaining it is to not blindly update until a root method is ensured for the next version of firmware. Resign to the fact that with each update you will temporarily lose root and need to redo it. Plan ahead, wait for root confirmation and then update with a plan of how to get root again.
I typically don't TWRP flash stock so I don't know if it works but in the distant past I recall that it wouldn't so thus I never try. Maybe someone can confirm. For me I haven't updated firmware on my note pro for a year now and I am not missing anything. ..
Sent from my SM-N910T using Tapatalk
The last thing I remember flashing was Clockword Mod 11 last year, ever since then I have been running Firmware build 18.3.1.C.1.15. Upon seeing an update for my phone for Firmware build 18.3.1.C.1.17 I attemted to download it and kept getting the message "Cannot Verify" so after trying this out on PC Companion and relocking my bootloader I was still running into problems. So the simplest thing I could think of is to use Flashtool and flash the latest ftf from there (Firmware 18.6.A.0.182 - obtained from XperiFirm), at first I didnt think it was a problem to not wipe USER_DATA as I just thought of it as an upgrade, if that failed I persumed I would have to wipe everything (this didnt matter much anyway). So I went ahead and flashed the rom however when I went to boot my mobile I got a bootloop "Android is optimising apps xxx of xxx" this went on forever untill I cut the power using a pin. So I tried it again this time wiping everything and still the same problem :crying: . Then I came across people on the forums to use the older FlashTool verison 0.9.18.6 since the new FSC feature can cause probelms, this time I tried it again however I used the older Firmware 18.6.A.0.172 just to be failsafe. Still the same problem. Right then I was thinking Emma would save my phone so I went and applied the 4.4.4 Firmware 18.3.1.C.1.15 service (Which I had to begin with) but for some reason this seemed to have little effect despite trying it twice and reciving a "Sucessful Flash" message. Now I am left very confused as it is still booting in the lollipop style (optimising apps loop) even though I flashed a KitKat rom. I have been left without my phone all day because of this, any help would be STRONGLY APPRICIATED! . Thanks for your time
#1 Open your bootloader again
#2 Install TWRP (See 5.1.1 root topic for installation/guide)
#3 Open TWRP Wipe all data
#4 Reboot into recovery
#5 Flash any custom rom like Cyanogenmod through TWRP
Post results please this is fixable It's seems It's a soft brick which is an easy fix
What i think is you had corrupt data/left over data and after you relocked bootloader something went wrong after flashing. Though flashing should wipe all data let's see
Re-flash ftf wiping data and caches, you must do this if going from 4.4.4 to 5.1 and From 5.1 to 4.4.4 due to changes in runtime from dalvik to art and other changes.
How to get near enough stock?
Thanks for your replies, when I flashed the ftf's I did tick all the boxes under 'Wipe' on FlashTool, when that failed so did emma. I can try flashing CWM however the main purpose of this was for me to upgrade to Lollipop as I wanted a near enough stock experiance (Considering Z5 Rom) with root. When I tried CWM before there were a few things that I just coulnt get used to. Is there any way that I could use recovery to flash a stock rom with the lastest Lollipop releese or Z5 experiance as I have backups on PCC that I have to restore (Important contacts, media etc...) and I dont really want to use a CWM based rom . I wouldnt mind to flash Z5 however I dont know if this is possiable could you guys comfirm this? Thanks for your time .
[Update] TWRP recovery is working!
I have followed this thread to update my Recovery - TWRP 2.8.7.0 .
Many Thanks to @linuxct for the straight forward instructions and @ARandomIndian for putting me in the correct direction :highfive: .
Im just unsure if I can flash Z5 Experiance Rom now. Is it possiable despite my android being messed? I have already wiped data, is it okay to just go and flash? .
Zane Finch said:
I have followed this thread to update my Recovery - TWRP 2.8.7.0 .
Many Thanks to @linuxct for the straight forward instructions and @ARandomIndian for putting me in the correct direction :highfive: .
Im just unsure if I can flash Z5 Experiance Rom now. Is it possiable despite my android being messed? I have already wiped data, is it okay to just go and flash? .
Click to expand...
Click to collapse
Don't worry you're android is not messed up, let's do this to fix it back to regular :-
Before starting i highly recommend you charge your phone to have atleast 50+% battery and use the official cable provided also make sure the cable is firmly inplace,
#1 Enter Recovery, wipe all data
#2 Download Stock 5.1.1 i think you like that so get that (Make sure it is for your D2303 or whatever your model is)
#3 Install latest flashtools with latest patch (Or later versions if you don't want to risk it)
#4 Go to the location of flashtools (installation directory) for me it is C:\Flashtool\drivers Open the exe file there, select the 2 Flashmode and Fastboot drivers install them.
#5 Flash the ftf using flashtools
Post results
Somehow...
Using TWRP I wiped Dalvik Cache, Cache, System and Data. Using the same 18.6.A.0.182 Customization UK FTF from yesterday I flashed my phone but somehow I am stuck with the same bootloop again?! "Android is optimising Apps XXX of XXX" I really dont understand this. . Thanks for your help .
Zane Finch said:
Using TWRP I wiped Dalvik Cache, Cache, System and Data. Using the same 18.6.A.0.182 Customization UK FTF from yesterday I flashed my phone but somehow I am stuck with the same bootloop again?! "Android is optimising Apps XXX of XXX" I really dont understand this. . Thanks for your help .
Click to expand...
Click to collapse
Hey man Android is optimizing means everything is working just fine it takes about 30+ minutes sometime,
Just leave it charging for atleast 2 hours and see what the progression is and post results please, thank you
Optimising
ARandomIndian said:
Hey man Android is optimizing means everything is working just fine it takes about 30+ minutes sometime,
Just leave it charging for atleast 2 hours and see what the progression is and post results please, thank you
Click to expand...
Click to collapse
Yes but this does not seem normal, the first boot always freezes on the wave animation. It then restarts by itsself and optimises upto so many for example 64 of 200 and then freezes and restarts with a different ammount like 90 of 194. This didnt seem normal to me, is this okay?
Edit: I have left it running for almost 40 min now. Every time just before it seems to freeze and reboot it never reaches the end of the ammount say 60 of 200. I'm becoming very doubtful that it is going to work . But I just remembered a while back that I flashed a custom boot img to get recovery and root in my last working state. Maybe this has somthing to do with it?
Really need my phone working now :| If anyone can help please do! Thanks!
Zane Finch said:
Yes but this does not seem normal, the first boot always freezes on the wave animation. It then restarts by itsself and optimises upto so many for example 64 of 200 and then freezes and restarts with a different ammount like 90 of 194. This didnt seem normal to me, is this okay?
Edit: I have left it running for almost 40 min now. Every time just before it seems to freeze and reboot it never reaches the end of the ammount say 60 of 200. I'm becoming very doubtful that it is going to work . But I just remembered a while back that I flashed a custom boot img to get recovery and root in my last working state. Maybe this has somthing to do with it?
Really need my phone working now :| If anyone can help please do! Thanks!
Click to expand...
Click to collapse
Hi okay, try flashing the Z5 style rom please then we'll move forward I think you've a corrupted ftf
Please redownload latest Z5 style rom make sure it's not interrupted during download. Restart router if needed for stability before download
ARandomIndian said:
Hi okay, try flashing the Z5 style rom please then we'll move forward I think you've a corrupted ftf
Please redownload latest Z5 style rom make sure it's not interrupted during download. Restart router if needed for stability before download
Click to expand...
Click to collapse
I tried flashing the Z5 experiance rom, I followed the instructions on the rom page (Used TWRP). However this time when it booted it did not say "Optimising Android" but it still did boot loop after the wave animation. I also tried flashing the older firmware but that did the same loop again, I also have been looking for alternative ftf's online becuase I also had the suspicion of a corroupted ftf however there are no Customized UK roms availble. I really am stuck now, my phone seems to be more messed up than I thought. . Any more Ideas?
If your bootloader is unlocked did you update it before flashing anything? If not this is why
Zane Finch said:
I tried flashing the Z5 experiance rom, I followed the instructions on the rom page (Used TWRP). However this time when it booted it did not say "Optimising Android" but it still did boot loop after the wave animation. I also tried flashing the older firmware but that did the same loop again, I also have been looking for alternative ftf's online becuase I also had the suspicion of a corroupted ftf however there are no Customized UK roms availble. I really am stuck now, my phone seems to be more messed up than I thought. . Any more Ideas?
Click to expand...
Click to collapse
You updated your bootloader before flashing right? If not do that like Andy said,
Also i would give you my Nandroid but It's the D2305.
[email protected] said:
If your bootloader is unlocked did you update it before flashing anything? If not this is why
Click to expand...
Click to collapse
ARandomIndian said:
You updated your bootloader before flashing right? If not do that like Andy said,
Also i would give you my Nandroid but It's the D2305.
Click to expand...
Click to collapse
Okay, you mean the same one I flashed to be able to update my bootloader to TWRP? I'll give it a shot! Thanks!
Zane Finch said:
Okay, you mean the same one I flashed to be able to update my bootloader to TWRP? I'll give it a shot! Thanks!
Click to expand...
Click to collapse
Okay nice post the results
ARandomIndian said:
Okay nice post the results
Click to expand...
Click to collapse
I flashed that very bootloder before I flashed the Lollipop ftf I booted my phone and the same thing happend, so I tried it again this time flashing afterwards an still booting with the same damn screen . Was I definatly using the correct bootloader or am I missing out anything when flashing? My phones rebooted like 5 times now for the 'optimisation' and its getting nowhere .
Shall I fire up my classic Nokia 5230 with custom Symbian to record a video so you guys can see what happens when it boots?
Did you wipe user data and cache when flashing the ftf
[email protected] said:
Did you wipe user data and cache when flashing the ftf
Click to expand...
Click to collapse
Yes, everything in the 'Wipe' section was ticked, infact before I flashed it again I also wiped Dalvik, cache, data and system in TWRP.
So I just flashed CWM 12.1 and its all running fine for some reason the Wifi doesnt work but atleast I can use this untill we find what the problem is. Do you guys know why my WiFi isnt working? But more importantly why does CWM work and stock rom doesnt?!
Edit: The reason the WiFi isnt working has to be a problem with the kernal as far as I can see, this also suggests that the kernal could be incompatable with Lollipop as it wasnt designed to support it? Correct me if im wrong but if this is the case where can I download the official latest kernal? If someone could confirm this by checking my kernal version above that would be great! Thanks!
I previously updated my kernal here the one that says [new]. If you look at post #8 you will see that this kernal has a problem with WiFi in CWM "As I suspected, in kernel modules there's no WiFi module (wlan.ko), I think that that's the reason why WiFi is not working.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Okay flash this version of Cyanogen http://forum.xda-developers.com/xperia-m2/orig-development/rom-cyanogenmod-12-developement-t2971213 choose the latest one
We'll see what the issue can be any ideas @linuxtt
---------- Post added at 03:18 PM ---------- Previous post was at 03:14 PM ----------
Zane Finch said:
So I just flashed CWM 12.1 and its all running fine for some reason the Wifi doesnt work but atleast I can use this untill we find what the problem is. Do you guys know why my WiFi isnt working? But more importantly why does CWM work and stock rom doesnt?!
Edit: The reason the WiFi isnt working has to be a problem with the kernal as far as I can see, this also suggests that the kernal could be incompatable with Lollipop as it wasnt designed to support it? Correct me if im wrong but if this is the case where can I download the official latest kernal? If someone could confirm this by checking my kernal version above that would be great! Thanks!
I previously updated my kernal here the one that says [new]. If you look at post #8 you will see that this kernal has a problem with WiFi in CWM "As I suspected, in kernel modules there's no WiFi module (wlan.ko), I think that that's the reason why WiFi is not working.
Click to expand...
Click to collapse
Okay can you please flash another FTF? First try a new 5.1.1 ftf from another source for your model and then try older versions like Kitkat and post results please