Basically if I was to flash the leaked Jelly Bean to my Razr M and then the OTA comes a few weeks later will I still get the OTA (unrooted btw)?
Thanks,
YourGoodFriend
YourGoodFriend said:
Basically if I was to flash the leaked Jelly Bean to my Razr M and then the OTA comes a few weeks later will I still get the OTA (unrooted btw)?
YourGoodFriend
Click to expand...
Click to collapse
i read some where it does not allow ota but when it does come out u can fastboot flash w rsd back to stock nd recieve the ota...ive been back and forth from ics to jb multiple times already lol idk why
livefastdiefun07 said:
i read some where it does not allow ota but when it does come out u can fastboot flash w rsd back to stock nd recieve the ota...ive been back and forth from ics to jb multiple times already lol idk why
Click to expand...
Click to collapse
that was my question. So Im on the JB leak now, and have downloaded the stock ICS that came with the phone on my SD card now. So do I just do the same procedure put in recovery and flash to ics as I did the jb rom, or is there a different procedure? Or will that way work as well?
emaculant29 said:
that was my question. So Im on the JB leak now, and have downloaded the stock ICS that came with the phone on my SD card now. So do I just do the same procedure put in recovery and flash to ics as I did the jb rom, or is there a different procedure? Or will that way work as well?
Click to expand...
Click to collapse
Everything you need can be found here: http://www.phonearena.com/news/How-to-restore-your-Motorola-DROID-RAZR-M-back-to-stock-ICS-from-the-JB-leak_id35580
hokieputter said:
Everything you need can be found here: http://www.phonearena.com/news/How-to-restore-your-Motorola-DROID-RAZR-M-back-to-stock-ICS-from-the-JB-leak_id35580
Click to expand...
Click to collapse
ok thanks
Related
phone has been working crappy and i want to revert back to ics for the time being until google works it out. what's the easiest way to do so. can i just put a zip file and apply it through recovery like i did to update to ics?
wasya152 said:
phone has been working crappy and i want to revert back to ics for the time being until google works it out. what's the easiest way to do so. can i just put a zip file and apply it through recovery like i did to update to ics?
Click to expand...
Click to collapse
Yep. via your file manager try the recovery trick
I've already seen a thread about that here but I can't find it quickly now. Anyway, you will need cwm recovery to revert back to Gingerbread from ICS because stock recovery won't allow you to do so.
EDIT : Here is the thread [Q] Downgrading Nexus S from ICS to Gingerbread.
EDIT 2 : If your phone is not unlocked you will need this to proceed... It looks like a pretty good and comprehensive tutorial to me Downgrade Nexus S from 4.0.3 To 2.3.6
You wanna go back to stock? Go on Peter Alfonso's web site. He has a stock rooted gwk74 zip you can just flash through cwm with a wipe.
Sent from my Nexus S 4G using xda premium
yeah, just wipe then flash gb rom
Caution: I have tried this method with my S3 and successfully flash back to old bootloader XXALEF. But we always have to be careful when flash bootloader. According to sammobile, Samsung updated new bootloader to fix suddend death error of S3. Every update of the manufacture should be better. So I don't advise you to downgrade bootloader back to previous version. JUST ALWAY FLASH AS OUR OWN RISK !
And If you try and successfully please report here and let me know if it works 100% on another S3.
Hey guys,
After flashed stock XXELLA rom or flash new XXELLA bootloader. You can't not flash back to old previous version of bootloader anymore via PC Odin. And after every S3 reboot, it will show red exclamation mark at boot logo and always check flash counter =1 in download mode if you user custom kernel or custom CWM. This is 3 method to flash back to old bootloader:
>>> METHOD 1: You can use Sboot Checker to check which bootloader is backlisted. Then use some basic terminal commands to downgrade your bootloader. This is more simple and safer. Please visit @Odia's topic http://forum.xda-developers.com/showthread.php?t=2081748. Credit to him.
>>> METHOD 2: This is the most simple and fast method for lazy guys ! Just download the following .zip file and flash via CWM Recovery. You will be restored to old ICS bootloader XXBLFB. This is download link http://forum.xda-developers.com/showpost.php?p=36433966&postcount=105. Credit to @fbatti73 he has ported @Odia's command to CWM flashable zip file. So many thanks to @fbatti73 and @Odia.
>>> METHOD 3: This is the first method I've found but far too much work involved and take alot of time. But if you like this' also another choosing:
1. Always backup first, full wipe yor S3 and flash back to lastest stock ICS 4.0.4 rom not included old bootloader in it or you can fash via Mobile Odin and don't care it include a bootloader or not because Mobile Odin doesn't flash bootloader. I''m in Vietnam and I choose this ICS 4.0.4 rom I9300XXBLH1_I9300OLBBLH1_XEV.zip http://www.hotfile.com/dl/166926386/6a0e52a/I9300XXBLH1_I9300OLBBLH1_XEV.zip.html
2. After flashed ICS 4.04 rom don't root or do another work on it, Just check OTA update on S3 by Go to Settings > About device > Software update > Click Update. Let OTA update your S3 to JB 4.1.1. In my case the OTA will update to JB 4.1.1 XXDLJ1 and it takes about 2xx MB size. Yes, it's here. The processing of OTA update from ICS 4.0.4 to JB 4.1.1 can break the protect of new bootloader XXELLA . And after OTA updated to JB 4.1.1 you would have the old version of JB 4.1.1 bootloader. In my case it's bootloader XXDLJ1.
3. But although our S3 has old bootloader XXDLJ1 but it's still a JB bootloader version. Every S3 reboot you will still get red exclamation mark and counter =1 if you use custom kernel or custom CWM. To make red exlamation mark and counter =1 disappear totally. You only have to flash back to old ICS version bootloader XXALEF. And now you can flash back to XXALEF bootloader via PC Odin.
4. Just install a custom kernel and a custom CWM Recovery. Wa wa, red exclamation mark and counter =1 have already dissapeared totally.
This is the link of ICS old bootloader XXALEF can flash via Odin: http://www.mediafire.com/?dlruvz9fib6c046
>>> Many thanks to XDA members of the following threads. Yours'' replys helped me accidental found this way )
http://forum.xda-developers.com/showthread.php?t=2077844
http://forum.xda-developers.com/showthread.php?t=1918667
http://forum.xda-developers.com/showthread.php?t=1993044
http://forum.xda-developers.com/showthread.php?t=1646610
Dr.Love said:
Hey guys,
After flashed stock XXELLA rom or flash new XXELLA bootloader. You can't not flash back to old previous version of bootloader anymore. And after every S3 reboot, it will show red exlamation mark at boot logo and always check flash counter =1 in download mode if you user custom kernel or custom CWM. This is the way I found to flashed back to old bootloader.
1. Flash back to lastest stock ICS 4.0.4 rom not included old bootloader in it. I''m in Vietnam and I choose this rom I9300XXBLH1_I9300OLBBLH1_XEV.zip http://www.hotfile.com/dl/166926386/6a0e52a/I9300XXBLH1_I9300OLBBLH1_XEV.zip.html
2. After flashed ICS 4.04 rom. You let OTA update check and let OTA update your S3 to JB 4.1.1. In my case the OTA will update to JB 4.1.1 XXDLJ1. Yes, it's here. The processing of OTA update from ICS 4.0.4 to JB 4.1.1 can break the protect of new bootloader XXELLA . And after OTA updated to JB 4.1.1 you would have the old version of JB 4.1.1 bootloader. In my case it''s bootloader XXDLJ1.
3. But although our S3 has old bootloader XXDLJ1 but it''s still a JB bootloader version. Every S3 reboot you will still get red exlamation mark and counter =1 if you use custom kernel or custom CWM.
4. To make red exlamation mark and counter =1 disappear totally. You only have to flash back to old ICS version bootloader XXALEF. And now you can flash back to XXALEF bootloader via Odin.
5. Just install a custom kernel and a custom CWM Recovery. Wa wa, red exlamation mark and counter =1 have already dissapered totally.
This is the link of ICS old bootloader XXALEF can flash via Odin: http://www.mediafire.com/?dlruvz9fib6c046
>>> Many thanks to XDA members of the following threads. Yours'' replys helped me accidental found this way )
http://forum.xda-developers.com/showthread.php?t=2077844
http://forum.xda-developers.com/showthread.php?t=1918667
http://forum.xda-developers.com/showthread.php?t=1993044
http://forum.xda-developers.com/showthread.php?t=1646610
Click to expand...
Click to collapse
Did you even tried it or you need other members to beta test it 4 u,post a video of u making this ACTUALLY work !
Dr Love. In the OTA step- how much is the size of 4.1.1 ?
Pretty nice, will give it a try on the S3 of my mom
nhariamine said:
Did you even tried it or you need other members to beta test it 4 u,post a video of u making this ACTUALLY work !
Click to expand...
Click to collapse
Oh, I have tried it with my S3 and successfully flash back to old bootloader. Sorry, I can't make a video. I will add caution in post 1 because always have to be carefully when flash bootloader. You can try as your own risk.
thekoRngear said:
Dr Love. In the OTA step- how much is the size of 4.1.1 ?
Click to expand...
Click to collapse
About 2xx MB.
sangosnip69 said:
Pretty nice, will give it a try on the S3 of my mom
Click to expand...
Click to collapse
I'm downloading everything I need, I'll get a try and come back later to tell you if it's work with French Firmware.
Why there is red mark when phone boot? I'm running CM10.1 I got afraid because of that.
Sent from my GT-I9300 using xda app-developers app
how the new bootloader looks like ?
eranda84 said:
Why there is red mark when phone boot? I'm running CM10.1 I got afraid because of that.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
It appear because you use custom kernel or custom CWM with new bootloader.
F.M.K said:
how the new bootloader looks like ?
Click to expand...
Click to collapse
Go to google play, find app Android System Info. Install and run it you will see current version of your S3's bootloader in System Tab.
SUCCESS!!!!!!!!!!!!!!!!!!!!!!!!
Bootloader changed to XXDLJ1.
Update: Changed to ICS XXALEF.
Thanks a lot!!!
The trick is to download a full fledged ICS firmware of a country that yet no been updated to 4.1.2. After flash, let the OTA update according to that or any country that has not been updated to JB 4.1.2. I downloaded OP's Vietnamese firmware and flashed but chosen India on OTA update. It's a 285.07 MB file.
Voila you are done. The OTA does the trick.
thank you for the information, I'll try
If I flash old nandroid backup from ics, would it flash old bootloader?
Sent from a better Galaxy designed for humans!
zadusimple said:
If I flash old nandroid backup from ics, would it flash old bootloader?
Sent from a better Galaxy designed for humans!
Click to expand...
Click to collapse
no
thekoRngear said:
SUCCESS!!!!!!!!!!!!!!!!!!!!!!!!
Bootloader changed to XXDLJ1.
Update: Changed to ICS XXALEF.
Thanks a lot!!!
The trick is to download a full fledged firmware of a country that yet no been updated to 4.1.2. After flash, let the OTA update according to that or any country that has not been updated to JB 4.1.2. I downloaded OP's vietnamese firmware but in the SW settings chose India.
Voila you are done. The OTA does the trick.
Click to expand...
Click to collapse
thanks have you used mobile odin?thanks for reply
uberto.costanzo said:
thanks have you used mobile odin?thanks for reply
Click to expand...
Click to collapse
It will work with kies?
uberto.costanzo said:
thanks have you used mobile odin?thanks for reply
Click to expand...
Click to collapse
Nope.
Done with PC Odin.
thekoRngear said:
Nope.
Done with PC Odin.
Click to expand...
Click to collapse
and factory reset after flash or before? thanks
uberto.costanzo said:
and factory reset after flash or before? thanks
Click to expand...
Click to collapse
Hmm..just before I flashed the full firmware I had fully wiped device with cwm recovery.
uberto.costanzo said:
and factory reset after flash or before? thanks
Click to expand...
Click to collapse
Before
Hi guys , I'm currently on Nightlies 4.1.2 JB (unlocked and rooted) and I want to install a 4.3 JB rom onto my tf300t. BUT I need to update my bootloader to 4.2 as stated by the instructions . How do I go about this? I've looked at multiple threads but cant seem to find a SOLID answer/procedure to do so.
Thank you for your time.
HellRaiser9101 said:
Hi guys , I'm currently on Nightlies 4.1.2 JB (unlocked and rooted) and I want to install a 4.3 JB rom onto my tf300t. BUT I need to update my bootloader to 4.2 as stated by the instructions . How do I go about this? I've looked at multiple threads but cant seem to find a SOLID answer/procedure to do so.
Thank you for your time.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2187982
Use the instructions for
[UNLOCKED BL] Method 2: Update using fastboot
Click to expand...
Click to collapse
I'm running rooted w/stock OTA 4.3. Are there any special upgrade procedures to update to 4.4 when rooted via Koush superuser and using the stock OTA?
Was able to update to 4.3 OTA w/o incident (see thread below)
http://forum.xda-developers.com/showthread.php?p=45183403#post45183403
Bump...any info on whether or not its possible would be appreciated.
It should work as long as everything is stock (including recovery and kernel). You will however lose root, but that can easily be reobtained by flashing it after updating.
mrlad said:
I'm running rooted w/stock OTA 4.3. Are there any special upgrade procedures to update to 4.4 when rooted via Koush superuser and using the stock OTA?
Was able to update to 4.3 OTA w/o incident (see thread below)
http://forum.xda-developers.com/showthread.php?p=45183403#post45183403
Click to expand...
Click to collapse
If you are rooted why not just flash a rooted stock rom? Confused why you wait for answers from others... I am just curious since I see people do this and it confuses me... Just askin and sorry if you think I may be flamin'.
Do people think the OTA is different somehow or works better somehow
playya said:
If you are rooted why not just flash a rooted stock rom? Confused why you wait for answers from others... I am just curious since I see people do this and it confuses me... Just askin and sorry if you think I may be flamin'.
Do people think the OTA is different somehow or works better somehow
Click to expand...
Click to collapse
Pretty sure that if I flash stock ROM I'm going to lose my settings. I've had VERY bad results backing up and restoring going from 4.2 to 4.3 and really don't want to go through that hassle unless absolutely required.
To answer your other question, I just prefer to be on the OTA.
mrlad said:
Pretty sure that if I flash stock ROM I'm going to lose my settings. I've had VERY bad results backing up and restoring going from 4.2 to 4.3 and really don't want to go through that hassle unless absolutely required.
To answer your other question, I just prefer to be on the OTA.
Click to expand...
Click to collapse
If you are on a stock rom and flash the upgraded version you wont lose your settings. Flashing one rom over another can be done its just frowned up in some cases. Lets be honest though there are quite a few back up tools out there for you to achieve a duplicated look going from one rom to another within the hour.
I hear ya if you had issues but you sure its not in your procedure. Be glad to help you if you need it. Thanks for answering the question though but I believe your route is more cumbersome than just a simple flash but what ever makes you more comfortable is best I get that
mrlad said:
I'm running rooted w/stock OTA 4.3. Are there any special upgrade procedures to update to 4.4 when rooted via Koush superuser and using the stock OTA?
Was able to update to 4.3 OTA w/o incident (see thread below)
http://forum.xda-developers.com/showthread.php?p=45183403#post45183403
Click to expand...
Click to collapse
Mine was same specs like yours (stock 4.3 - rooted by Koush superuser) and updated to 4.4 through OTA just fine :good:
Never had any problem with Koush superuser and OTAs on both Nexus 4 & Galaxy Nexus (can't say the same with supersu)
Tried to upgrade to 4.4. The upgrade failed and the phone reports no command when I reboot. Still on stock recovery.
Any suggestions on what I should try next to recover?
Note: I do have TWRP available while running fastboot.
I installed the factory stock image (and formatted the cache but didn't wipe out the userdata image). I know the first boot should take an extended amount of time, but its been showing the rotating circles for about 8 minutes now. What is a reasonable amount of time for the initial boot?
Wiping the cache and the Dalvik cache from TWRP solved it. I'm rooted again and things appear to be back to normal.
playya said:
If you are rooted why not just flash a rooted stock rom? Confused why you wait for answers from others...
Click to expand...
Click to collapse
Well....I'm on the stock ROM now (Google forced my hand).
mrlad said:
Well....I'm on the stock ROM now (Google forced my hand).
Click to expand...
Click to collapse
what does that mean?
playya said:
what does that mean?
Click to expand...
Click to collapse
The 4.4 OTA upgrade failed and wouldn't boot. A poor attempt at humor I guess.
mrlad said:
The 4.4 OTA upgrade failed and wouldn't boot. A poor attempt at humor I guess.
Click to expand...
Click to collapse
root it and flash anything you want my friend... take control of your phone back...
Iv managed to softbrick my phone by flashing incorrect firmware im now trying to get back to 4.2.2 on my GT-I9506 but keeps failing in Odin.
Any ideas anyone ?
mikeylaw81 said:
Iv managed to softbrick my phone by flashing incorrect firmware im now trying to get back to 4.2.2 on my GT-I9506 but keeps failing in Odin.
Any ideas anyone ?
Click to expand...
Click to collapse
If u were flashing android 4.3 you cant come back to android 4.2.2. If u were flashing 4.4.2 you cant come back to 4.3 or 4.2.2 :highfive:
I don't know how iv done it but have managed to get 4.3 working but keeps coming up with keyboard has stopped working.
So I can not get back to stock 4.2.2 ?
mikeylaw81 said:
I don't know how iv done it but have managed to get 4.3 working but keeps coming up with keyboard has stopped working.
So I can not get back to stock 4.2.2 ?
Click to expand...
Click to collapse
No.
Thanks so can I get back to stock 4.3 then and receive ota updates etc ?
Yes go back to 4.3 then u can have ota updates
aayushkhajuria2842 said:
Yes go back to 4.3 then u can have ota updates
Click to expand...
Click to collapse
So iv tried flashing a stock version of 4.3 and its failing in odin on size !
Also may I need a pit file which I cannot find any where for the i9506
mikeylaw81 said:
So iv tried flashing a stock version of 4.3 and its failing in odin on size !
Also may I need a pit file which I cannot find any where for the i9506
Click to expand...
Click to collapse
What android was the incorrect firmware u flashed?
Joku1981 said:
What android was the incorrect firmware u flashed?
Click to expand...
Click to collapse
It was 4.4 kitkat for the s330s the other version of the i9506 but didn't work at all
mikeylaw81 said:
It was 4.4 kitkat for the s330s the other version of the i9506 but didn't work at all
Click to expand...
Click to collapse
Samsung didnt release android 4.4.2 for the GT-i9506 still. I think the unique you can do is wait till they release it. You flashed new bootloader & you can't come back to android 4.3 :highfive:
Joku1981 said:
Samsung didnt release android 4.4.2 for the GT-i9506 still. I think the unique you can do is wait till they release it. You flashed new bootloader & you can't come back to android 4.3 :highfive:
Click to expand...
Click to collapse
My phones working now managed to install google keyboard and its on 4.3 just want to go back to stock rom not rooted etc but im stuck on odin when it fails on size
Is there a way to get back to stock to receive ota updates I know Knox can't be undone
Sent from my GT-I9506 using xda app-developers app