Hello,
PC Companion says that i have a new update, but i've unlocked and rooted my phone, so when the install should begin, an error pops up saying that i have a modded firmware and i cannot update it.
So, i think the same issue will go on when next week or next year ICS will be released.
The question is: what i have to do to update my XS? I've to flash the ftf loosing the recovery and then reinstall it? Doing that, i will lost all the apps and everything on my phone?
Thank You very much
If you have unlocked bootloader, you cannot update using the official method, but only through flashtool.
If for some reason you want to use the official way, you should relock the bootloader, here is the guide http://forum.xda-developers.com/showthread.php?t=1527159
As far as my knowledge goes: You could backup your apps, lock your bootloader, upgrade to ICS, unlock bootloader, achieve root, restore apps. You'll probably have to wait for root for ICS though, shouldn't take long at all.
Or at least that's how I hope it will work.
So, the faster way is to wait for a custom rom correctly packed to be flashed via recovery
Thank guys
Related
Ok Iv noticed that things are getting really really confusing around here with people saying one thing then someone else saying something else. I want to have a thread that is straight forward coming from people that know what they are talking about and not just assuming.
Now my phone has never had an unlocked bootloader. Before I updated to GB OTA i was on .83 rooted with all the mods added to it (webtop dock, blah, blah blah) I RSD back to .26 (that very old file) and just started doing OTA updates one by one once i logged in with my blurr account. I updated to GB via the official OTA update that was pushed to my phone when i selected to system update under settings.
I was able to Root this ATT OFFICIAL version pushed to my phone using This Pre-install method and that is all that i have done.
What i want to do now is Unlock the bootloader. From what i have read Pudding is the best way of doing this.
Q1: Does this method (Pudding) work with the Official ATT OTA version pushed to phones and not Kenns modded version, and is it the only way to unlock the bootloader?
Q2: Once unlocked what version of CWR do I install to be able to flash ROMs? Would i be able to just install ROM Manager and do the installation from there, Or possibly both ROM Manager and CWR?
Q3: Since RSD is out of the picture for me, if for some reason I'm to soft brick my phone and can still get into Recovery mode, what .sbf do i flash, would it have to be the same one that was pushed to phones that if not already available on here will be really soon?
Thanks for all the help if anyone helps out.
StyleUkno
Q2, if you unlock your phone, cwM of tenfars, the 2nd version for unlocked. Rom manager with official CWM have released before some days, but yet it doesn't support external sd.
As for question 1, and the unlocking pudding. The OTA gb you installed, might updated you bootloader, and maybe can't use that pudding.
For that be very carefull of your next steps.. Personally I would have send a pm to the2dcour, or another dev that knows as much..
Sent from my MB860 using XDA App
Bump to see if any other responses come.
Q1: Does this method (Pudding) work with the Official ATT OTA version pushed to phones and not Kenns modded version, and is it the only way to unlock the bootloader?
Yes, pudding works and is the only way. Have to Flash pudding and run OEM unlock command in fastboot. Because you are already on OTA, there's a high chance you will need an extra couple steps. It will likely soft brick with 0x1000 error but wit fastboot option. From there you need to fastboot and re do the oem unlock command another time. Then you are fine.
Q2: Once unlocked what version of CWR do I install to be able to flash ROMs? Would i be able to just install ROM Manager and do the installation from there, Or possibly both ROM Manager and CWR?
Tenfar's 6/30 unlocked CWM. ROM Manager version doesn't properly wipe as of yet. You can update if you dont' care about wiping, but that usually leads to boot loops when installing roms. Also most devs here are using update scripts tailored for tenfars version
Q3: Since RSD is out of the picture for me, if for some reason I'm to soft brick my phone and can still get into Recovery mode, what .sbf do i flash, would it have to be the same one that was pushed to phones that if not already available on here will be really soon?
if you softbrick (other than the initial unlock soft brick where you just run oem unlock again) then depends on what you want to get to. CWM a rom.zip/fruitcake for the version you want would be ideal. If not then a fastboot version if available. I'd RSD the GB 4.5 with pudding sbf as a last resort.
StyleUkno said:
Ok Iv noticed that things are getting really really confusing around here with people saying one thing then someone else saying something else. I want to have a thread that is straight forward coming from people that know what they are talking about and not just assuming.
Now my phone has never had an unlocked bootloader. Before I updated to GB OTA i was on .83 rooted with all the mods added to it (webtop dock, blah, blah blah) I RSD back to .26 (that very old file) and just started doing OTA updates one by one once i logged in with my blurr account. I updated to GB via the official OTA update that was pushed to my phone when i selected to system update under settings.
I was able to Root this ATT OFFICIAL version pushed to my phone using This Pre-install method and that is all that i have done.
What i want to do now is Unlock the bootloader. From what i have read Pudding is the best way of doing this.
Q1: Does this method (Pudding) work with the Official ATT OTA version pushed to phones and not Kenns modded version, and is it the only way to unlock the bootloader?
If you use the pudding you will hard brick on the OTA (from what people have been saying)
Q2: Once unlocked what version of CWR do I install to be able to flash ROMs? Would i be able to just install ROM Manager and do the installation from there, Or possibly both ROM Manager and CWR?
Out of the picture becuase you cant unlock I think
Q3: Since RSD is out of the picture for me, if for some reason I'm to soft brick my phone and can still get into Recovery mode, what .sbf do i flash, would it have to be the same one that was pushed to phones that if not already available on here will be really soon?
Thanks for all the help if anyone helps out.
StyleUkno
Click to expand...
Click to collapse
asldkjghaa
I just got the Note 2 from Newegg (for verizon) and after reading through a lot of the threads on this forum like:
How to Unlock Your Bootloader - Firmware Version VRALJB
and
[Q] Stock restore Fail at sboot.bin
and
Questions about Unlocking or Recovering from a Soft Brick
I guess there's issues with the OTA verizon pushed out and the first guide won't work if you have the OTA. Well long story short, how can I tell for sure if the phone I've received had the latest updates put on it before I got it?
My build says VRALJB, does that mean I'm good and I still have the older version? Would it say VRALL4 if the OTA had been applied?
In a related question, would it be wise to simply update to VRALL4 now, use the new method to jailbreak, and then continue on my merry way? Would this alleviate any worries of the OTA getting applied and breaking my root / possibly bricking my phone??
Thanks for any help for a noob. I tried to do research first!
You do not have the ota..... Use original method!!
Sent from my most awesome phone EVER!!!!
As stated above you are on the original baseband VRAJB so you can use the original root and unlock method. Once you are unlocked, do not take a OTA ever as you may get relocked and who knows if there will be a future unlock method. Most of the custom ROMs block the updates, but just in case don't take it if you ever get the message.
Once you are unlocked you will use TWRP custom recovery (which is the screen that will appear at the end of the unlock process). You can flash the VRALL4 baseband when you flash a ROM if you want to be on the latest baseband (flash ROM first then immediately flash VRALL4, no reboot in between). The download can be found here: http://forum.xda-developers.com/showthread.php?t=2108510
Thanks for the replies.
There's a video on the Adam Outler Jailbreak Guide that actually suggest getting the OTA first and then just doing the CASUAL thing afterwards. Personal preference or is there some advantage?
The video in question is the first one in the thread, it is titled "Jailbreak video for Windows users only!
This video desmonstrates CASUAL used with Odin to flash the Galaxy Note 2 firmware Thanks to DroidModderX" and the timeframe in question is 00:50 to 01:10
Just wondering, thanks!
No real advantage either way (the update to VRALL4 was very minor but did relock the bootloader). If you want to be on the latest update you either need to take it OTA or flash it yourself. I was on VRAJB and unlocked before the update so I only had the original method to work with. I updated to VRALL4 manually by flashing it.
Bottom line, either way will work, just make sure if you take the OTA before doing anything that you use the correct unlock method (the "new" one). The whole thing will take you maybe 10 minutes, its really easy. The video is a great guide.
Greetings
I foolishly upgraded my tablet to the latest version (4.2.2) before rooting my device. I understand that 4.2.2 cannot be rooted at this time. If I am wrong, please let me know.
So....I downloaded EMMA, unlocked my tablet, installed EMMA and proceeded to (as I though) downgrade to 4.1.2, in order to root the tablet and then upgrade.
EMMA happily installed the downgrade and indicated it was successful. Upon restarting my tablet, I noticed that I still had 4.2.2. I tried to again install the downgrade, but no luck.
I did do a complete backup of my data, so after reinstalling my apps, I was able to restore data and get my tablet back to its original (4.2.2) state. Of course, I am sitting with an unlocked device. I did not see any way on EMMA to relock the bootloader.
Without overly trying the patience of those who have far more knowledge of these matters than I, here are a few questions:
-why didn't the downgrade take?
-given I have an unlocked device, is there an alternate method to downgrade, root, protect root, upgrade and relock device?
-if number 2 is not possible what is the easiest and quickest way to relock the bootloader.
-is rooting 4.2.2 a question of when or if?
I would like to thank you all for reading this and any help you have to offer.
Have a good day.
gderreck said:
Without overly trying the patience of those who have far more knowledge of these matters than I, here are a few questions:
-why didn't the downgrade take?
-given I have an unlocked device, is there an alternate method to downgrade, root, protect root, upgrade and relock device?
-if number 2 is not possible what is the easiest and quickest way to relock the bootloader.
-is rooting 4.2.2 a question of when or if?
I would like to thank you all for reading this and any help you have to offer.
Have a good day.
Click to expand...
Click to collapse
Emma does not downgrade. It only installs the latest ROM ("service") for your device. It wrongly shows you the previous version in the list of services available (.370 for example for my 311). If you view the ''service" details in the bottom of the right-hand panel in Emma, you will see it actually refers to the latest ROM, not the previous.
Also, as far as I know, you cannot re-lock your bootloader with Emma. You will have to use Flashtool - search these forums or Google it for a "how to". Why do you want to re-lock?
There is a way to get root on 4.2.2 if you have an unlocked bootloader, see here :
http://forum.xda-developers.com/showthread.php?t=2392092&page=24 , post #232. I have not tried this myself, so I can't say if it works.
A little tip for you - when asking a question here, please state your device version (311, 312 or 321).
gderreck said:
Greetings
I foolishly upgraded my tablet to the latest version (4.2.2) before rooting my device. I understand that 4.2.2 cannot be rooted at this time. If I am wrong, please let me know.
So....I downloaded EMMA, unlocked my tablet, installed EMMA and proceeded to (as I though) downgrade to 4.1.2, in order to root the tablet and then upgrade.
EMMA happily installed the downgrade and indicated it was successful. Upon restarting my tablet, I noticed that I still had 4.2.2. I tried to again install the downgrade, but no luck.
I did do a complete backup of my data, so after reinstalling my apps, I was able to restore data and get my tablet back to its original (4.2.2) state. Of course, I am sitting with an unlocked device. I did not see any way on EMMA to relock the bootloader.
Without overly trying the patience of those who have far more knowledge of these matters than I, here are a few questions:
-why didn't the downgrade take?
-given I have an unlocked device, is there an alternate method to downgrade, root, protect root, upgrade and relock device?
-if number 2 is not possible what is the easiest and quickest way to relock the bootloader.
-is rooting 4.2.2 a question of when or if?
I would like to thank you all for reading this and any help you have to offer.
Have a good day.
Click to expand...
Click to collapse
Have a look here for downgrade instructions:
http://forum.xda-developers.com/showthread.php?t=2427256
I've done it yesterday and am glad i got rid of that dreadful phablet UI.
Thank you both for your replies. Mode is SGP311. I bought it from Sony Canada. I'm not sure if that is significant. Would I be correct in guessing that the US firmware is different from the Canadian version?
Thanks
gderreck said:
Thank you both for your replies. Mode is SGP311. I bought it from Sony Canada. I'm not sure if that is significant. Would I be correct in guessing that the US firmware is different from the Canadian version?
Thanks
Click to expand...
Click to collapse
Take a look here:
"http://forum.xda-developers.com/showthread.php?t=2433466"
Given that you have a SGP311, you should be able to root stock 4.2.2 using this.
Hi,
As we all know unless we downgrade and stuff, or install custom recoveries (which require some hackeries) we can't root the latest firmware.
I came across this method: http://whiteboard.ping.se/Android/Rooting
It uses the original boot.img and edits it then using fastboot it flashes it with the su binaries and security turned off.
Would this work on our Xperia?
Thanks
Probably, but you'd need to unlock your bootloader...
That kind of defeats the purpose. I'm trying to not do that
I want to be able to install OTA updates and support.
You can alway relock back once rooted. By that, you can OTA update safely and keep rooting
Sent from my little big badass boy!
worf_1977 said:
You can alway relock back once rooted. By that, you can OTA update safely and keep rooting
Sent from my little big badass boy!
Click to expand...
Click to collapse
Ok so if I follow that guide to get root, unlock bootloader, flash the new boot, and relock bootloader, I will be able to install OTA?
Won't that brick my device since I have a modified boot.img?
In order to relock the bootloader you must firdt change back to a stock kernel, otherwise you will brick the phone, wich luckily is recoverable...
Even if yo relock on custom kernel, you will also can enter in fastboot mode to flash stock one
Sent from my little big badass boy!
(SOLVED)
Im in stock 4.1.2 whit S-OFF, unlocked bootloader (1.55) and then RELOCKED.
¿Can i take the last OTA?
Im not rooted, and i dont have custom recoverys (i recently flashed a RUU.zip to return to stock, but i could not remove the S-OFF and RELOCKED status because the hboot 1.55).
I have economic (health) problems and I'll really need to sell my phone, but I'm afraid that the new owner will come out error when trying to update.
conquesoextra said:
Im in stock 4.1.2 whit S-OFF, unlocked bootloader (1.55) and then RELOCKED.
¿Can i take the last OTA?
Im not rooted, and i dont have custom recoverys (i recently flashed a RUU.zip to return to stock, but i could not remove the S-OFF and RELOCKED status because the hboot 1.55).
I have economic (health) problems and I'll really need to sell my phone, but I'm afraid that the new owner will come out error when trying to update.
Click to expand...
Click to collapse
Yes. You can get OTAs while S-OFF. And assuming you haven't unlocked the bootloader since flashing the RUU, all the system files it verifies should be in place to accept OTAs. However, considering you are currently on 4.1.2, you'll need to run through a progression of OTAs to get up to the latest version, 4.4.2 w/ Sense 6. Might be better to just run the latest RUU to bring it up to 4.4.2 w/ Sense 5.5 then OTA to Sense 6. Be aware that you'll need to be on the AT&T network in order to get the updates OTA. If you're not on AT&T, you'll need to flash the updates manually, in which case you'll need to be S_OFF.
Also, once the phone is S-OFF there is no good reason to change that back to S-ON. There's the potential of bricking the phone by doing so. And even if it doesn't brick, the updates in firmware may make it more difficult to obtain S-OFF again.
Thank you very much.
At the begining i did this:
1- Unlocked bootloader and flashed TWRP.
2- Root
3- Gained S-Off
When i decide to sell it i did this:
1- Removed xposed and root.
2 - Relocked bootloader.
3 - Flashed RUU.zip (4.1.2)
¿What do you mean whit AT&T network? I unlocked the phone vía imei (using it in mexico whit Telcel) and still have the update appearing.
Sorry for my terrible english
conquesoextra said:
Thank you very much.
At the begining i did this:
1- Unlocked bootloader and flashed TWRP.
2- Root
3- Gained S-Off
When i decide to sell it i did this:
1- Removed xposed and root.
2 - Relocked bootloader.
3 - Flashed RUU.zip (4.1.2)
¿What do you mean whit AT&T network? I unlocked the phone vía imei (using it in mexico whit Telcel) and still have the update appearing.
Sorry for my terrible english
Click to expand...
Click to collapse
First off, since you are S-OFF there is no need to relock the bootloader in order to flash an RUU. It will run just fine with an unlocked bootloader. Also when you flash an RUU, all the partitions get wiped so there is no need to do anything within the ROM such as remove xposed & root prior to flashing. The RUU will set the device essentially in a factory state.
As far as I understand it, the OTAs for carrier specific devices are served up by the carrier. So if the phone has been SIM unlocked and is being used on another network, if you go into Settings>AT&T software update, it will not receive any available OTA update. You will need to flash the update file manually using the information in this thread, http://forum.xda-developers.com/showthread.php?t=2659374.
Since you are still on 4.1.2, you will need to run one of the recent RUUs in order to manually flash the OTA updates in that thread. The latest RUU available for AT&T devices is KK4.4.2 w/Sense 5.5.
http://androidruu.com/getdownload.p...09_10.26.1718.01L_release_356565_signed_2.exe
Flash that then you can manually flash the OTA update to get Sense 6.
You are the man.
THANK YOU SO MUCH!