I've been wanting to root my phone because I have Tasker And TiBa pro. The last two S3s I've had hard bricked so I'm hesitant to attempt to root again. I've been looking around and saw somewhere that the boot loader can't be unlocked on 4.3, and I was wondering if I could still root my phone. Considering they did not brick until I rebooted once, I think I might be able to but want confirmation before I attempt it again. Also, since I will just have root with an unlocked boot loader I won't be able to flash CWM or custom ROMs, right? Not even via mobile Odin? Thinks that's all I have to ask right now, thanks for your help in advance!
Sent from my SCH-I535 using Tapatalk
treyonator56 said:
I've been wanting to root my phone because I have Tasker And TiBa pro. The last two S3s I've had hard bricked so I'm hesitant to attempt to root again. I've been looking around and saw somewhere that the boot loader can't be unlocked on 4.3, and I was wondering if I could still root my phone. Considering they did not brick until I rebooted once, I think I might be able to but want confirmation before I attempt it again. Also, since I will just have root with an unlocked boot loader I won't be able to flash CWM or custom ROMs, right? Not even via mobile Odin? Thinks that's all I have to ask right now, thanks for your help in advance!
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Which OS do you have on your phone? Please provide this info.
If you are on the VRUCML1 4.3 OTA, it has a locked bootloader and prevents you from Odin flashing any firmware that pre-dates 4.3 VRUCML1. Flashing anything in Odin will lead to a hard brick unless it is explicitly the VRUCML1 4.3 stock image. Do not attempt to install CWM or TWRP, this will lead to a hard brick. Do not use anything to unlock your bootloader, you will also hardbrick. You can not unlock the bootloader on VRUCML1 4.3 ota, it is permanently locked. You should understand by now that you can flash one thing in Odin and that is the VRUCML1 4.3 stock image.
If you are on the VRUCML1 update, use Saferoot to gain root access. Then use Safestrap to be able to flash VRUCML1 4.3 based custom roms. Only VRUCML1 or "ML1" roms are compatible with Safestrap. AOSP is incompatible with Safestrap, there is no timetable or even the hint of future compatibility. Also, if you want working wifi then you need to flash the VRUCML1 kernel modules after each clean flash of a VRUCML1 rom. These kernel modules are linked in the Safestrap thread as well. Good luck and read up!
Thanks very much! I'll attempt to root with the saferoot method to root my phone. I'll report back if anything goes wrong.
Sent from my SCH-I535 using Tapatalk
treyonator56 said:
Thanks very much! I'll attempt to root with the saferoot method to root my phone. I'll report back if anything goes wrong.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Cool! Let me know how it goes.
Well, I successfully rooted and backed up my imei. Next step is to install a custom ROM. Do you have any you recommend from the 4.3 sticky thread?
Sent from my SCH-I535 using Tapatalk
treyonator56 said:
Well, I successfully rooted and backed up my imei. Next step is to install a custom ROM. Do you have any you recommend from the 4.3 sticky thread?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Everything should go pretty simply once you use SafeStrap now. I operate with the "try before you buy" mentality. Everyone has different tastes and you should try what's available. CleanRom 8 Core and MOAR are a good way to start and I think each VRUCML1 rom available only gets better once you see what they have to offer.
Related
Hello guys I just got may galaxy S3 from a friend. I think the bootloader is still unlocked after I received an OTA today. I don't have root or recovery. I just want to be sure I use the correct root and recovery method. Could someone point me to the one they used on this build with success? I would be greatly appreciated. I did look but none are specific enough for me to be sure I'm using the correct one.
Is my bootloader still unlocked if it says (custom)?
Again I appreciate any help
Sent from my SCH-I535 using xda premium
mike216 said:
Hello guys I just got may galaxy S3 from a friend. I think the bootloader is still unlocked after I received an OTA today. I don't have root or recovery. I just want to be sure I use the correct root and recovery method. Could someone point me to the one they used on this build with success? I would be greatly appreciated. I did look but none are specific enough for me to be sure I'm using the correct one.
Is my bootloader still unlocked if it says (custom)?
Again I appreciate any help
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Welcome! In order to unlock your BL in the first place you must have had root. This is a good thread on rooting, unlocking, and flashing recovery/ROMs/kernels:
http://forum.xda-developers.com/showthread.php?t=1762709
nghtrain88 said:
Welcome! In order to unlock your BL in the first place you must have had root. This is a good thread on rooting, unlocking, and flashing recovery/ROMs/kernels:
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
Thanks so much bud! Will I be all good on the updated build I received today?
My bootloader is unlocked if it says custom on boot?
Again I really appreciate it!
Sent from my SCH-I535 using xda premium
mike216 said:
Thanks so much bud! Will I be all good on the updated build I received today?
My bootloader is unlocked if it says custom on boot?
Again I really appreciate it!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
As long as you have one of the stock builds listed in section 2 of that thread you should be good. The EZ-unlock app should be able to tell you if you're BL is unlocked.. also if you reboot the phone, if the samsung splash flashes for a split second (the one before you see Samsung Galaxy SIII), then you're prob unlocked.. if you see it for a few seconds then you're prob locked
Man I rooted flashed recovery in rom manager. (recovery wouldn't stick) so I flashed it again after making a nandroid and ended up having to recover a soft brick at 4am. Thank God for puremotive's guide on how to recover from it I was able to be back up. I don't know what went wrong. Because I didn't have busy box. Maybe I shouldn't have used the latest recovery rom manager flashes? I'm on stock with root and afraid to move anywhere! Anyone know how to make recovery stick on stock rom? I've never had this happen. Usually I would be OK and on to try AOSP on other devices uve had. Right now I'm rooted on stock rom with bootloader unlocked and have OTA root keeper in case I get another OTA. Any help would be greatly appreciated! Take care
Sent from my SCH-I535 using xda premium
How did you unlock your bootloader?
annoyingduck said:
How did you unlock your bootloader?
Click to expand...
Click to collapse
With the app
Sent from my SCH-I535 using xda premium
Ok, issue is probably that you used the current version 1.4 I think. In the app description in the playstore is a link to older versions, you want 1.2. The new ones are unlocking, but it's not sticking. There is also a link in the current root guide somewhere, but direct from the play store is fine.
annoyingduck said:
Ok, issue is probably that you used the current version 1.4 I think. In the app description in the playstore is a link to older versions, you want 1.2. The new ones are unlocking, but it's not sticking. There is also a link in the current root guide somewhere, but direct from the play store is fine.
Click to expand...
Click to collapse
link for ez-unlock 1.2
annoyingduck said:
How did you unlock your bootloader?
Click to expand...
Click to collapse
Let me be more specific because I may have had a locked bootloader.
I received the phone yesterday from my friend. He did unlock the bootloader with the app. I installed the official OTA from Verizon as soon as I got it. I rooted it. I didn't bother trying to unlock the bootloader because after the OTA when it booted it said custom with a lock symbol on boot up. I rooted and flashed the latest recovery from rom manager. I'm sure I picked the right phone. I made a nandroid but my recovery wouldn't stick. I remember it saying something about Co firming something about a recovery and I could have chosen yes. It sounded like CWM wouldn't stick if I choose yes?
I don't know if the OTA locked my bootloader back up?
I would like to try again. Any of you guys no how to make recovery stick on stock rom? I would like to try paranoid android. What recovery should I be on to flash this jelly bean based rom? I would really appreciate anyone who knows how I screwed up or has went straight to JB from a specific CWM recovery. I'm also not sure if I should said yes or know when in CWM when asking me that recovery question. I wish I remember what the question was
Sent from my SCH-I535 using xda premium
nghtrain88 said:
As long as you have one of the stock builds listed in section 2 of that thread you should be good. The EZ-unlock app should be able to tell you if you're BL is unlocked.. also if you reboot the phone, if the samsung splash flashes for a split second (the one before you see Samsung Galaxy SIII), then you're prob unlocked.. if you see it for a few seconds then you're prob locked
Click to expand...
Click to collapse
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
mike216 said:
Man I rooted flashed recovery in rom manager. (recovery wouldn't stick) so I flashed it again after making a nandroid and ended up having to recover a soft brick at 4am. Thank God for puremotive's guide on how to recover from it I was able to be back up. I don't know what went wrong. Because I didn't have busy box. Maybe I shouldn't have used the latest recovery rom manager flashes? I'm on stock with root and afraid to move anywhere! Anyone know how to make recovery stick on stock rom? I've never had this happen. Usually I would be OK and on to try AOSP on other devices uve had. Right now I'm rooted on stock rom with bootloader unlocked and have OTA root keeper in case I get another OTA. Any help would be greatly appreciated! Take care
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
mike216 said:
Let me be more specific because I may have had a locked bootloader.
I received the phone yesterday from my friend. He did unlock the bootloader with the app. I installed the official OTA from Verizon as soon as I got it. I rooted it. I didn't bother trying to unlock the bootloader because after the OTA when it booted it said custom with a lock symbol on boot up. I rooted and flashed the latest recovery from rom manager. I'm sure I picked the right phone. I made a nandroid but my recovery wouldn't stick. I remember it saying something about Co firming something about a recovery and I could have chosen yes. It sounded like CWM wouldn't stick if I choose yes?
I don't know if the OTA locked my bootloader back up?
I would like to try again. Any of you guys no how to make recovery stick on stock rom? I would like to try paranoid android. What recovery should I be on to flash this jelly bean based rom? I would really appreciate anyone who knows how I screwed up or has went straight to JB from a specific CWM recovery. I'm also not sure if I should said yes or know when in CWM when asking me that recovery question. I wish I remember what the question was
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Brian Gove said:
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Click to expand...
Click to collapse
Thanks for everything Boss! That probably was the reason my recovery wouldn't stick. I used the link to grab easy unlock 1.2. I'm now unlocked, rooted. I want to flash an AOSP based rom (paranoid android) what recovery should I flash? The newest in rom manager or the slightly older one EZ-Recovery has to offer?
Thanks once again!
Sent from my SCH-I535 using xda premium
Cwm 6.0.1.2 for aosp jb, do not use the old 5 . something touch in ez recovery
mike216 said:
Thanks for everything Boss! That probably was the reason my recovery wouldn't stick. I used the link to grab easy unlock 1.2. I'm now unlocked, rooted. I want to flash an AOSP based rom (paranoid android) what recovery should I flash? The newest in rom manager or the slightly older one EZ-Recovery has to offer?
Thanks once again!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Which is the recovery that you want to use? I have the latest CWM touch on my Dropbox if that's the one you want. The regular CWM in the app is fine to use and twrp recovery has a thread in the development forum.
Brian Gove said:
Which is the recovery that you want to use? I have the latest CWM touch on my Dropbox if that's the one you want. The regular CWM in the app is fine to use and twrp recovery has a thread in the development forum.
Click to expand...
Click to collapse
I'm on stock ICS in want to go to paranoid android. Sorry guys but after last night I'm paranoid myself!
Sent from my SCH-I535 using xda premium
Brian Gove said:
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Click to expand...
Click to collapse
Thanks once again! I'm now on PA after a pack of smokes! Appreciate all your help. You were absolutely right ! Recovery stuck and it flashed with no problem. I used the current recovery straight from ROM manager
Sent from my SCH-I535 using xda premium
Good, glad to hear you got it rolling.
I feel stupid for asking this, but I just wanna make sure. Gonna be downloading LiquidSmooth and I'm supposed to download d2vzw , correct? Answered
Queston 2 - I'm gonna be backing up my IMEI. I know I flash it before a custom ROM, but do I do it before or after I unlock my bootloader? I'm sure it's after, but I just wanna be 100% sure on this stuff. - Answered
Question 3 - What's a bootchain? And should I worry about it after rooting and unlocking?
I don't have a Verizon s3, I have sprint s3, can't say I know how to install the rom or the instructions, but I can say that d2vzw is the Verizon model. (my friend has one)
Sent from my SPH-L710 using XDA Premium 4 mobile app
Yes d2vzw is the Verizon version of the ROM
Sent from my SCH-I535 using Tapatalk 4
Another question , I'm gonna be backing up my IMEI. I know I flash it before a custom ROM, but do I do it before or after I unlock my bootloader? I'm sure it's after, but I just wanna be 100% sure on this stuff.
EDIT - I know I put flash. I'm gonna be using Synergy method where you flash it and it grabs the images and makes them into a flashable zip.
DubleJayJ said:
Another question , I'm gonna be backing up my IMEI. I know I flash it before a custom ROM, but do I do it before or after I unlock my bootloader? I'm sure it's after, but I just wanna be 100% sure on this stuff.
EDIT - I know I put flash. I'm gonna be using Synergy method where you flash it and it grabs the images and makes them into a flashable zip.
Click to expand...
Click to collapse
I backed up my IMEI AFTER I unlocked and rooted my S3 but BEFORE I flashed anything. Don't even flash a kernel before backing up your IMEI.
Sent from my SCH-I535 using Tapatalk 4
Sandman-007 said:
I backed up my IMEI AFTER I unlocked and rooted my S3 but BEFORE I flashed anything. Don't even flash a kernel before backing up your IMEI.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Alright. I just wanted to make sure. If I got any more, I'll just post them.
What's a bootchain? And should I worry about it after rooting and unlocking?
DubleJayJ said:
What's a bootchain? And should I worry about it after rooting and unlocking?
Click to expand...
Click to collapse
You need the appropriate bootchain for your variant and firmware version. It is flashed during the unlocking bootloader phase
Sent from my SCH-I535 using Tapatalk 4
Sandman-007 said:
You need the appropriate bootchain for your variant and firmware version. It is flashed during the unlocking bootloader phase
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
So whenever I OTA 4.1.1 I need to download the bootchain to unlock the phone? Or is it already in Casual Tool?
DubleJayJ said:
What's a bootchain? And should I worry about it after rooting and unlocking?
Click to expand...
Click to collapse
A bootchain is exactly what it sounds like, a sequence of booting steps to boot your phone. It looks something like this:
Modem > sbl1 > sbl2 > sbl3 > aboot > boot(kernel)
After unlocking the bootloader on the phone, you are only changing the aboot step to a very old version that allows the phone to run custom roms. When you change the bootchain in the original step, you are changing the entire bootchain. So to answer your question, you don't have to worry too much with changing the bootchain to the mf1 base because as long as all the bootchain steps trust each other, your phone will have no problem booting up.
The reason the OP wants you to flash another bootchain is simply because of how old it is, and it is generally a good idea to be on the same base for everything on your phone.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
A bootchain is exactly what it sounds like, a sequence of booting steps to boot your phone. It looks something like this:
Modem > sbl1 > sbl2 > sbl3 > aboot > boot(kernel)
After unlocking the bootloader on the phone, you are only changing the aboot step to a very old version that allows the phone to run custom roms. When you change the bootchain in the original step, you are changing the entire bootchain. So to answer your question, you don't have to worry too much with changing the bootchain to the mf1 base because as long as all the bootchain steps trust each other, your phone will have no problem booting up.
The reason the OP wants you to flash another bootchain is simply because of how old it is, and it is generally a good idea to be on the same base for everything on your phone.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
So unless I'm going to something before 4.1 I shouldn't have to worry about the bootchain?
DubleJayJ said:
So unless I'm going to something before 4.1 I shouldn't have to worry about the bootchain?
Click to expand...
Click to collapse
I think you're missing the point of how the rooting procedure works. The reason the older bootchain needs to be flashed in the first place is so root can be achieved. Jellybean blocks the rooting process used on Ics, so the only way to achieve root on jellybean is to flash an ICS bootchain to allow the su binary to be placed.
The bootchain shouldn't matter so much because it's only involved with booting the phone. It really shouldn't matter what kind of bootchain you're using because the software version isn't dependant on the bootchain used. It is always a good idea to change the bootchain to the base you are on when you root the phone.
Additionally, if you flash a firmware located in the development section, you will be able to change your modem, tz, and sbl files. This puts you mostly on the correct base.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I think you're missing the point of how the rooting procedure works. The reason the older bootchain needs to be flashed in the first place is so root can be achieved. Jellybean blocks the rooting process used on Ics, so the only way to achieve root on jellybean is to flash an ICS bootchain to allow the su binary to be placed.
The bootchain shouldn't matter so much because it's only involved with booting the phone. It really shouldn't matter what kind of bootchain you're using because the software version isn't dependant on the bootchain used. It is always a good idea to change the bootchain to the base you are on when you root the phone.
Additionally, if you flash a firmware located in the development section, you will be able to change your modem, tz, and sbl files. This puts you mostly on the correct base.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
My mind = blown
Alright, let me see if I got this. Whenever I OTA to JB, I won't be able to root, so I'll have to flash the older boot chain, right? I honestly feel stupid, all this stuff is just killing my mind.
DubleJayJ said:
My mind = blown
Alright, let me see if I got this. Whenever I OTA to JB, I won't be able to root, so I'll have to flash the older boot chain, right? I honestly feel stupid, all this stuff is just killing my mind.
Click to expand...
Click to collapse
Yup! You're getting it.
But all that work is packaged into casual, or done in the manual root method.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Yup! You're getting it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Does Casual Toolkit automatically flash the old bootchain when I go to root on 4.1.1? Or do I have to flash it manually through Casual?
DubleJayJ said:
Does Casual Toolkit automatically flash the old bootchain when I go to root on 4.1.1? Or do I have to flash it manually through Casual?
Click to expand...
Click to collapse
I just edited my post, but casual will do all that work for you.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I just edited my post, but casual will do all that work for you.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Sweet. So should I root, unlock then root and have it flash TWRP at the same time? Or after unlocking just root then flash recovery separately.
And do I have to root before unlocking?
DubleJayJ said:
Sweet. So should I root, unlock then root and have it flash TWRP at the same time? Or after unlocking just root then flash recovery separately.
And do I have to root before unlocking?
Click to expand...
Click to collapse
Casual will root, install a custom recovery, and unlock your Bootloader. Just follow the directions in the thread. Can't give you too many exact answers because I've never used it.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Casual will root, install a custom recovery, and unlock your Bootloader. Just follow the directions in the thread. Can't give you too many exact answers because I've never used it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Good work filling in for me I couldn't have said it better myself. Even learned a few things. I got slammed with customers so I didn't get to respond :/
Sent from my SCH-I535 using Tapatalk 4
BadUsername said:
Casual will root, install a custom recovery, and unlock your Bootloader. Just follow the directions in the thread. Can't give you too many exact answers because I've never used it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the help man!
Just unlocked the bootloader on my MAXX and installed TWRP/Root. I haven't tried upgrading or downgrading versions yet. I'm hoping someone can give me some insight to doing this.
My MAXX is still on 4.2.2(Jellybean) cause I didn't want to risk losing root when my bootloader was locked. Now that that's a non-issue can someone answer these question?
1) Since I'm still on 4.2.2 can I take the 4.4 OTA update even with TWRP installed?
2) If I can't take the update, then I would have to RSD up to 4.4?
3) Once on 4.4 can I go back to 4.2.2 (jellybean)? Seems I've read you can but you can't downgrade the bootloader or a bin file?
I've read differing opinions when it come to this and would like to try 4.4, even though it sounds pretty buggy (email active display, home button double, battery life, etc.) but I'd like to be able to go back if I didn't like it. I've seen a lot of people regretting that they went to KitKat because of these issues.
Thanks,
Mike
runner1717 said:
Just unlocked the bootloader on my MAXX and installed TWRP/Root. I haven't tried upgrading or downgrading versions yet. I'm hoping someone can give me some insight to doing this.
My MAXX is still on 4.2.2(Jellybean) cause I didn't want to risk losing root when my bootloader was locked. Now that that's a non-issue can someone answer these question?
1) Since I'm still on 4.2.2 can I take the 4.4 OTA update even with TWRP installed?
2) If I can't take the update, then I would have to RSD up to 4.4?
3) Once on 4.4 can I go back to 4.2.2 (jellybean)? Seems I've read you can but you can't downgrade the bootloader or a bin file?
I've read differing opinions when it come to this and would like to try 4.4, even though it sounds pretty buggy (email active display, home button double, battery life, etc.) but I'd like to be able to go back if I didn't like it. I've seen a lot of people regretting that they went to KitKat because of these issues.
Thanks,
Mike
Click to expand...
Click to collapse
1) no, you need to be completely stock with stock recovery
2) RSD is an option
3) you can "downgrade" from 4.4 to 4.2.2 by flashing all the files except the motoboot.img and the gpt.bin. just don't downgrade to the pre-camera update (12.7.7) and then take an OTA because you will hard brick
Thanks for the info!
Mike
I also had a similar question. I unlocked the bootloader and am on 4.4 stock rom. If i want to relock the bootloader and return to stock 4.4 without root can i just rsd lite using the 4.4 fxz? Hoping that brings the recovery to stock as well, in case there are future otas
An fxz will bring you back to stock and you are ready ri take an ota but it does not relock the bootloader
Sent from my XT1080 using Tapatalk
BladeRunner said:
An fxz will bring you back to stock and you are ready ri take an ota but it does not relock the bootloader
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Thanks for the fast response, will the fxz restore stock recovery and unroot the deivce? Can i relock my bootloader if i wanted to in future?
italysfinest327 said:
Thanks for the fast response, will the fxz restore stock recovery and unroot the deivce? Can i relock my bootloader if i wanted to in future?
Click to expand...
Click to collapse
Yes, a full fxz will restore the stock recovery and unroot you. You can relock just not sure why you would want to plus it will always show that the device as status code 2 which means it has been unlocked at some point
Sent from my XT1080 using Tapatalk
Those that unlocked and rooted, could you post your steps please?
Sent from my XT1080 using xda app-developers app
Can we run the 4.4.2 firmware (Topsnakes ported from X) on our maxx with 4.2.2 gpt and bootloader and motoboot? I know we can go backwards but not sure if you can go newer software and older boot and so forth.
Thanks
1080xt root 12.15.15
Was also wondering if we were to load the 4.4.2 ported from the Moto X if we can roll back to 4.2.2 12.15.15 if we just don't try to load the motoboot.bin and the gpt.bin.
1080xt root 12.15.15
AreOh said:
Those that unlocked and rooted, could you post your steps please?
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
Not sure how far you've gotten but here is the place to start... http://forum.xda-developers.com/showthread.php?t=2645122
Sent from my Unlocked Droid Maxx using xda app-developers app
Since I'm still on 4.2.2 should I just leave my bootloader and the bin file alone and just upgrade the rest to kit Kat? Can I do that?
Mike
I just got my m8 and want to s-off but I'm traveling and won't be able to figure that out until I'm back on my pc next week. The update keeps prompting me to take it. Is it safe to do so? Sorry if this was already answered trying to figure out the best way to browse with tapatalk.
I don't have root or anything yet...
Sent from my HTC6525LVW using Tapatalk
I used Firewater's method for permanent root, s-off and custom recovery. If I allow my phone to update will I mess things up or lose root?
Same boat here... s-off, permanent root, TWRP
The update to 1.55 downloaded but when I tried to let it install it just rebooted my phone into TWRP and that was it. Rebooted back to system and I'm still on the 1.12.605.11 software. Checking software update status shows "Result: Update Failed,410"
N00bs. Lol. You need a stock recovery to flash an OTA. Also, I am s-off and I had a flashback to a stock recovery to flash the OTA . Everything is still fine and then I flashed back to a custom recovery no problem
Sent from my HTC One M8
Totally a noob here, How do you flash to a stock recovery?
Sent from my HTC6525LVW using Tapatalk
You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
http://www.megafileupload.com/en/file/520717/stockrecovery-img.html
There are also videos on YouTube on flashing recoveries to the m8 if you need more help.
Sent from my HTC6525LVW using Tapatalk
Justintoxicated said:
I just got my m8 and want to s-off but I'm traveling and won't be able to figure that out until I'm back on my pc next week. The update keeps prompting me to take it. Is it safe to do so? Sorry if this was already answered trying to figure out the best way to browse with tapatalk.
I don't have root or anything yet...
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
You can install the update, and when you have the chance you can s-off using the weaksauce/supersu/firewater method. I picked up a new M8 a couple nights ago and took the update, and afterwards did the temproot/firewater method and it worked just fine. Hope this helps.
I flashed stock recovery and tried the OTA and it failed twice. I can't seem to get it on my phone through any of the methods for some reason.
In order to install update, you need to have STOCK recovery and STOCK Rom....NOT debloated or with mods....STOCK.
Again, you need STOCK recovery using a STOCK Rom.
If you have modified the system in anyway, it WONT work until you put it back to STOCK.
Sent from my HTC6525LVW using xda app-developers app
^you can have bloatware frozen and it'll work, just can't be removed.
Sent from my HTC6525LVW
dadams312 said:
I flashed stock recovery and tried the OTA and it failed twice. I can't seem to get it on my phone through any of the methods for some reason.
Click to expand...
Click to collapse
z-man79 said:
Totally a noob here, How do you flash to a stock recovery?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
KnightDavid said:
Same boat here... s-off, permanent root, TWRP
The update to 1.55 downloaded but when I tried to let it install it just rebooted my phone into TWRP and that was it. Rebooted back to system and I'm still on the 1.12.605.11 software. Checking software update status shows "Result: Update Failed,410"
Click to expand...
Click to collapse
z-man79 said:
I used Firewater's method for permanent root, s-off and custom recovery. If I allow my phone to update will I mess things up or lose root?
Click to expand...
Click to collapse
No need to take ota. Ota us our enemy. Lol. The ota has been pulled an you can simply flash the firmware an that's half of the ota an then flash a stock Rom based off 1.55 or install the backup that was posted of a pure stock 1.55 Rom. After those 2 things you will have the full ota. New radios everything.. flashing a stock recovery taking ota flashing back is not needed.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Thanks guys it was annoying having that update keep popping up and no real computer to lookup info or soff. As for getting updates after roming the phone usually just wait for authors to incorporate the updates. But I did not realize you can't have two recoveries like you can on Motorola phones which is good to know.
Sent from my HTC6525LVW using Tapatalk
New to android here.
I rooted the device with WeakSauce and use Firewater for S-Off. I didn't flash any custom recoveries. I did freeze some apps with Titanium Backup. If I do the OTA, 1) will it work? and 2) will it remove my root and/or s-off?
NoFanboy said:
You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
megafileupload.com/en/file/520717/stockrecovery-img.html
Click to expand...
Click to collapse
For clarification, after flashing the stockrecovery.img you posted and installing the update, there should be no problem flashing back to CWM recovery after the fact?
Thank you for your help and your time!
skivvies said:
For clarification, after flashing the stockrecovery.img you posted and installing the update, there should be no problem flashing back to CWM recovery after the fact?
Thank you for your help and your time!
Click to expand...
Click to collapse
Nope there will be no problem.
Sent from my HTC6525LVW using Tapatalk
richii0207 said:
In order to install update, you need to have STOCK recovery and STOCK Rom....NOT debloated or with mods....STOCK.
Again, you need STOCK recovery using a STOCK Rom.
If you have modified the system in anyway, it WONT work until you put it back to STOCK.
Sent from my HTC6525LVW using xda app-developers app
Click to expand...
Click to collapse
All your big words confuse me...will it work with custom rom's and recoveries?
I don't remember ever having to have stock recovery and stock rom for my old DNA to take an update. Normally devs would update their rom with the updates and all we had to do was fastboot flash the new radio.
NoFanboy said:
You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
http://www.megafileupload.com/en/file/520717/stockrecovery-img.html
There are also videos on YouTube on flashing recoveries to the m8 if you need more help.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So I flash the file you linked to, thank you but when I try to get into recovery I get a red triangle with an exclamation point in it. Seemed pretty straight forward.
sfreemanoh said:
All your big words confuse me...will it work with custom rom's and recoveries?
Click to expand...
Click to collapse
Lol, I had to. I just know someone is going to start a thread saying "update won't work, it just boots into twrp"
Sent from my HTC6525LVW using xda app-developers app
z-man79 said:
So I flash the file you linked to, thank you but when I try to get into recovery I get a red triangle with an exclamation point in it. Seemed pretty straight forward.
Click to expand...
Click to collapse
Hold the volume up button and pressed the power button to get to the recovery menu.
So I have unlocked my bootloader now. I have not installed any custom recovery and rooted...just yet. I want to be sure that I can still get the OTA and as I have understand I will have to still use the stock recovery and unfreeze app and disable Xposed. The first part is the hard part.
So this is what I want to do: Flash TWRP>Flash root zip>Flash stock Recovery
Anyone know where I can find the stock recovery for 4.4.4 for the Pergerine model?
Another question: Let's say I install TWRP now and then when Lollipop is realesed, could I just flash the stock rom via TWRP?
I mean I will not be able to update OTA but I have to do it manually, would that work?
If it does then I would just stick with a custom recovery instead.
Anyone? I really want to root this phone but I want to make sure that I can revert to stock so I can upgrade to Lollipop.
My advice is to wait some time, I'm sure there will be all sorts of guides for getting the OTA even if rooted and such..
Sent from my XT1032 using XDA Free mobile app
hekomat said:
My advice is to wait some time, I'm sure there will be all sorts of guides for getting the OTA even if rooted and such..
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I probably have to do that.