Related
Hi guys, I'd just like to know whether or not your Nexus 7 can still update normally i.e Settings>About Tablet>System Updates if it has a unlocked bootloader and custom recovery. Just like to know in advance before I install Clockwork Mod. Thanks in advance.
Once unlocked & rooted- install the app OTA RootKeeper- it's free in the Google Play store.
It's lets you temporarily un-root for OTA updates- then easily re-root after the update's done.
root keeper only works on minor updates. And does not work correctly for all devices . I do not see why google would root app checks before allowing a update. and have the updates to skip the apps you removed. I hope anyway. Acer is a basket case when it comes to ota updates. everything has to be exact as it was bought no frozen removed apps no root .
grrrrr its mine let me do what i wish with it .
Anything right now is only a guess as the device is quite new.
robdroyd said:
Once unlocked & rooted- install the app OTA RootKeeper- it's free in the Google Play store.
It's lets you temporarily un-root for OTA updates- then easily re-root after the update's done.
Click to expand...
Click to collapse
Thanks, but would an ota update install through a custom recovery normally, or would I have to get the zip file off xda manually and do it myself
Sent from my Nexus 7 using XDA Premium HD app
mmmcfc said:
Thanks, but would an ota update install through a custom recovery normally, or would I have to get the zip file off xda manually and do it myself
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
This method would allow you to get the updates over the air like normal through settings, about phone. But you may need to install a custom recovery afterwards.
However since you're rooted you'll have the opportunity of getting software before the OTA stuff comes out most likely.
My advice would be that even though you can do it that way, you don't have a reason too and you're better off not doing it that way unless a specific reason that you need to comes up.
Deciding whether or not I will dev on this ... liking the stock experience on this device. Probably will root so I can make a custom kernel and ROM. Thanks for your help guys!
Sent from my Nexus 7 using XDA Premium HD app
Basically is this possible, to go from 4.2 to 4.1.2? Mine is fine but my friend's Nexus 7 keeps shutting down.
Will a factory reset restore 4.1.2? Is there another way? Been googling for an hour, & I'm thinking it mustn't be possible with unrooted devices.
Thanks for any help
Mrs Hedgehog
P.S Please don't yell.
Not that I am aware of--I think you'll need to unlock the boot loader to then push the 4.1.2 image to it, but don't worry, its pretty straightforward with a little reading. Check the stickies for guides.
did the move to 4.2 occur via ota update?
Sent from my Nexus 7 using xda app-developers app
kboya said:
Not that I am aware of--I think you'll need to unlock the boot loader to then push the 4.1.2 image to it, but don't worry, its pretty straightforward with a little reading. Check the stickies for guides.
did the move to 4.2 occur via ota update?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes it was via OTA update. Bottom, she isn't going to want to unlock her device. Is there no way to put it back to how it was when she pulled it out of the box brand new? Even if she loses everything she would prefer that.
P.S Thanks for answering, appreciated.
Maybe she needs to think again. You can relock it as if nothing had happened!
Sent from my Nexus 7 using xda app-developers app
Ok would Google know if she did that. Would it be like it was when she first got it? Say if she had to send it back under the guarantee? I'm shocked actually. I thought a factory reset would take it back to basics. I don't think she'll agree somehow.
Nope, it is like nothing ever happened. No-one shall know (nor care,quite frankly).
Factory reset is more like delete data and settings (and also all your photos etc, if you choose SD card) and return to factory state (I.e. the base OS, which is now 4.2 after the update). It does not roll back to the original OS from the factory, which could be several iterations back.
Sent from my Nexus 7 using xda app-developers app
Wug's Nexus Root Toolkit is what you need.
Unlock, flash back to stock 4.1.2 and then re-lock.
Spannaa said:
Wug's Nexus Root Toolkit is what you need.
Unlock, flash back to stock 4.1.2 and then re-lock.
Click to expand...
Click to collapse
Think I may just do this. But, will it keep trying to force the update on me?
Sent from my Nexus 7 using xda app-developers app
tu3218 said:
Think I may just do this. But, will it keep trying to force the update on me?
Click to expand...
Click to collapse
It's Google that pushes the updates.
I've had no problems with 4.2 but if I do, I'll roll back to 4.1.2 and wait...
Spannaa said:
It's Google that pushes the updates.
I've had no problems with 4.2 but if I do, I'll roll back to 4.1.2 and wait...
Click to expand...
Click to collapse
So I'd still get the notification to update to 4.2 if I reverted back.
But yeah, 4.2 isn't that bad. I do notice some unresponsiveness when clicking icons but other than that, pretty good.
Sent from my SCH-I535 using xda app-developers app
Install the FOTAKill app to stop OTA Notifications
tu3218 said:
Think I may just do this. But, will it keep trying to force the update on me?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I had to roll back to 4.1.2 on my Nexus 7. The tablet would not charge (didn't recognize the high-current charger) under 4.2. To stop the update notifications I installed FOTAKill (tablet must be rooted). .doc file with FOTAKill installation instructions is attached.
Really wish that Google would have an option for "Never" when it asks for permission to install an update.
Spannaa said:
Wug's Nexus Root Toolkit is what you need.
Unlock, flash back to stock 4.1.2 and then re-lock.
Click to expand...
Click to collapse
Hi, I have a question, If I flash back to stock with Wug's toolkit would I receive the 4.1.2 update OTA or would I have to flash it manually?
Sent from my Nexus 7 using XDA Premium HD app
Cee_Pee_Three said:
Hi, I have a question, If I flash back to stock with Wug's toolkit would I receive the 4.1.2 update OTA or would I have to flash it manually?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
If "stock" is before 4.1.2 then yes, you'd get the OTA update notification (which would unroot the tablet. You might as well manually flash 4.1.2.
My Nexus 7 "bricked" when I allowed the update from 4.1.2 to 4.2, requiring a complicated procedure to unbrick it. I suspect that the problem was caused by a "rootkeeper" app.
SMS888 said:
If "stock" is before 4.1.2 then yes, you'd get the OTA update notification (which would unroot the tablet. You might as well manually flash 4.1.2.
My Nexus 7 "bricked" when I allowed the update from 4.1.2 to 4.2, requiring a complicated procedure to unbrick it. I suspect that the problem was caused by a "rootkeeper" app.
Click to expand...
Click to collapse
I wrote that wrong, I meant if I'm on 4.2 and flash back to the 4.1 original that first came with the device, would the 4.1.2 update come up OTA or would I have to flash 4.1.2 manually?
Sent from my Nexus 7 using XDA Premium HD app
I think you have to update manually. OTA will offer 4.2.
telexer said:
I think you have to update manually. OTA will offer 4.2.
Click to expand...
Click to collapse
Correct. The FOTA update would offer only the latest version.
On my new Nexus two separate updates were sent in sequence. First an update to 4.1.2 then another update (declined) to 4.2 a few minutes later. It was not a single update from 4.1.1 to 4.2.
Thank u for sharing this info, this saves me the trouble from updating to 4.1.2 manually.
UPDATE: So I went back to the initial ROM the device came with (JB 4.1.1) and Google quickly prompted to update to 4.1.2 (which is what I wanted) and now it asks me to update to 4.2 but I ignore that
Long story short, my Nexus 7 is back up and working flawlessly again!!
Sent from my Nexus 7 using XDA Premium HD app
SMS888 said:
I had to roll back to 4.1.2 on my Nexus 7. The tablet would not charge (didn't recognize the high-current charger) under 4.2. To stop the update notifications I installed FOTAKill (tablet must be rooted). .doc file with FOTAKill installation instructions is attached.
Really wish that Google would have an option for "Never" when it asks for permission to install an update.
Click to expand...
Click to collapse
What if I want to update my Nexus 7 later, how do I take off the fotakill.apk?
Sent from my Nexus 7 using XDA Premium HD app
4.2..> 4.1.2 Without rooting
Have Nexus 7, stock, has been upgraded OTA to 4.2.1. Have an $80 app (Anywhere Map) which company is working on a fix to operate with 4.2. I use Linux and it appears you can upgrade manually with 'adb reboot recovery' then Power & Vol to get recovery menu. Posts have said simply use 'adb sidload upgrade_img.zip' or 'adb install upgrade_img.zip'. Simple enough. I've only gotten to the menu from which I can choose 'apply update from adb', but have done nothing. Posts have said simply issue the command and select reboot from menu after it installs. This should install new os version without removing apps nor sdcard info. (I have backed up the whole sdcard with 'adb pull' to my computer.)
I have 4.1.2, 4.2, and 4.2.1 images. What I would like to do is put the 4.1.2 on to use until Anywhere Map gets their act together for 4.2. But 4.1.2 seems like a minor update to 4.1 and I can't find that image at Google nor anywhere else.
So the question is as to whether updating with the 4.1.2 image will work or not. I have the material to root the machine manually but would prefer not to do it. This all looks rather straightforward from the many posts I've read, except with my reservations on the 4.1.2 update. Thanks for any comments.
I was wondering if it will be safe if you update via OTA with a custom Open script Recovery such has TWRP would be safe, I do not want to get any issues while updating to Android 4.3 when it is available like soft bricking.
andyabc said:
I was wondering if it will be safe if you update via OTA with a custom Open script Recovery such has TWRP would be safe, I do not want to get any issues while updating to Android 4.3 when it is available like soft bricking.
Click to expand...
Click to collapse
You have to be stock to get the google updates. No custom recovery at all.
zelendel said:
You have to be stock to get the google updates. No custom recovery at all.
Click to expand...
Click to collapse
Have you tested it?, I am not sure if it could be possible since TWRP is OpenScriptRecovery so the system should be able to just get the OTA update to flash like nothing is wrong or anything.
I can restore the stock recovery using the Nexus Toolkit.
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Have you tested it?, I am not sure if it could be possible since TWRP is OpenScriptRecovery so the system should be able to just get the OTA update to flash like nothing is wrong or anything.
I can restore the stock recovery using the Nexus Toolkit.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It is well known that it will not work on none official recoveries. It will also not work if you are rooted. There are threads around about this.
zelendel said:
It is well known that it will not work on none official recoveries. It will also not work if you are rooted. There are threads around about this.
Click to expand...
Click to collapse
What do you mean that it will not work if your rooted?, will it give you some error or something on the stock recovery?
Sent from my Nexus 4 using xda app-developers app
andyabc said:
What do you mean that it will not work if your rooted?, will it give you some error or something on the stock recovery?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Ok it seems it will flash but you will lose root.
http://forum.xda-developers.com/showthread.php?t=2145848
zelendel said:
Ok it seems it will flash but you will lose root.
http://forum.xda-developers.com/showthread.php?t=2145848
Click to expand...
Click to collapse
Will OTA Rootkeeper help?, I have that installed just in case there is an update has I am fully aware that the update will replace the system partition.
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Will OTA Rootkeeper help?, I have that installed just in case there is an update has I am fully aware that the update will replace the system partition.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
To be honest I have no idea as I never do OTA updates. No real point.
zelendel said:
To be honest I have no idea as I never do OTA updates. No real point.
Click to expand...
Click to collapse
Ok, I found a really useful thread though: http://forums.androidcentral.com/htc-one/282447-install-ota-update-twrp-recovery.html
Looks like that stock recovery is the first thing to do.
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Ok, I found a really useful thread though: http://forums.androidcentral.com/htc-one/282447-install-ota-update-twrp-recovery.html
Looks like that stock recovery is the first thing to do.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Even though that is for a different device and a completely different OTA set up. Being fully stock is always the best bet. Like I said I never do OTA and on a nexus it is almost completely pointless as the 4.3 update will be available in a flashable zip file with in a matter of hours in not less.
zelendel said:
Even though that is for a different device and a completely different OTA set up. Being fully stock is always the best bet. Like I said I never do OTA and on a nexus it is almost completely pointless as the 4.3 update will be available in a flashable zip file with in a matter of hours in not less.
Click to expand...
Click to collapse
So you can just flash the zip 100% on a custom recovery?
Sent from my Nexus 4 using xda app-developers app
andyabc said:
So you can just flash the zip 100% on a custom recovery?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah. Once the devs have gotten their hands on it there will be a rooted zip in a matter of hours of release that can be flashed like a normal custom rom
zelendel said:
Yeah. Once the devs have gotten their hands on it there will be a rooted zip in a matter of hours of release that can be flashed like a normal custom rom
Click to expand...
Click to collapse
Awesome, I am just going to flash the stock recovery so when the update is available the data will not get wiped.
Sent from my Nexus 4 using xda app-developers app
If your using twrp v2.5.0.0 when we get the ota update you can use it to update and it will flash it fine it will also detect that you don't have root and will ask you if you want it restored
From my BLACKED OUT N4
spaceman860 said:
If your using twrp v2.5.0.0 when we get the ota update you can use it to update and it will flash it fine it will also detect that you don't have root and will ask you if you want it restored
From my BLACKED OUT N4
Click to expand...
Click to collapse
So the OTA update would just work?, all well I have the stock recovery flashed at the moment anyway so when the OTA updates stop I will flash the recovery back and then install a custom rom with 4G and USB Host supported also having all the good tweaks like the camera tweak.
Sent from my Nexus 4 using xda app-developers app
I had CWM on my rooted Nexus 4, and the OTA for android 4.3 came along, and worked fine! Android asked to reboot to install the update, so I agreed, and the reboot loaded CWM which flashed the update. I lost root however, but it was easy to put back.
Has anyone done the OTA to 4.3 while having TWRP recovery? I wonder which of the two recoveries is better at handling OTA updates ... some folks say never attempt OTA with a custom recovery, but CWM has always handled it fine on my Nexus 4 (I've done different over-the-air updates around 3 times now).
sordna said:
Has anyone done the OTA to 4.3 while having TWRP recovery? I wonder which of the two recoveries is better at handling OTA updates ... some folks say never attempt OTA with a custom recovery, but CWM has always handled it fine on my Nexus 4 (I've done different over-the-air updates around 3 times now).
Click to expand...
Click to collapse
I am also interested about doing an update to 4.3 with everything stock except for TWRP, and am waiting to hear other people experiences before I try it. I see that the following shows one recommended method (Scenario #2), although I am not sure exactly how to do it. I am curious as to why this is any different than doing it OTA:
http://forum.xda-developers.com/show....php?t=2145848
pjc123 said:
I am also interested about doing an update to 4.3 with everything stock except for TWRP, and am waiting to hear other people experiences before I try it. I see that the following shows one recommended method (Scenario #2), although I am not sure exactly how to do it. I am curious as to why this is any different than doing it OTA:
http://forum.xda-developers.com/show....php?t=2145848
Click to expand...
Click to collapse
From what I am reading now, it's going to work. You will loose root and might loose TWRP, but if you have unlocked bootloader you can flash them both again. I'd say go ahead and let us know if you lost both root and TWRP or just root.
sordna said:
From what I am reading now, it's going to work. You will loose root and might loose TWRP, but if you have unlocked bootloader you can flash them both again. I'd say go ahead and let us know if you lost both root and TWRP or just root.
Click to expand...
Click to collapse
Actually, what I am reading now from a lot of people is that it is not necessary to download the file, and just do the OTA, as there is no difference. If I were to lose TWRP it is an easy enough process to get it back. As far as rooting, I am waiting for Koush to upgrade his superuser app, as I switched from SuperSU a while back (Both developers are having a tough time with 4.3). I am also waiting for things to settle down with all the 4.3 bugs and app upgrades. Maybe in a few weeks; there is just way too many issues.
pjc123 said:
Actually, what I am reading now from a lot of people is that it is not necessary to download the file, and just do the OTA, as there is no difference. If I were to lose TWRP it is an easy enough process to get it back. As far as rooting, I am waiting for Koush to upgrade his superuser app, as I switched from SuperSU a while back (Both developers are having a tough time with 4.3). I am also waiting for things to settle down with all the 4.3 bugs and app upgrades. Maybe in a few weeks; there is just way too many issues.
Click to expand...
Click to collapse
No need to wait, you can switch back to SuperSU, the latest version (1.51) has been working perfectly with 4.3 for me.
BTW I just installed BootUnlocker for nexus devices, a great app that can lock/unlock your boot loader from within android without wiping your data!
I'm getting a Nexus 4. My question is if I root but keep stock, will I still receive updates?
Sent from my SAMSUNG-SGH-I717 using xda premium
Yes
Note that you want to keep your device as close to stock as possible if you want to install the OTAs. Rooting is no issue but you will encounter errors if you flash custom radios for example.
Sent from my Nexus 4 using xda app-developers app
briand.mooreg said:
I'm getting a Nexus 4. My question is if I root but keep stock, will I still receive updates?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Yes, and no if you're like me, I flash custom kernel, digs out nearly 50% of the system app replacing them with something to greenify them.
briand.mooreg said:
I'm getting a Nexus 4. My question is if I root but keep stock, will I still receive updates?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Not sure if this is your first android phone but its generally the same with all of them. If you root and alter files that the update checks for it will not update. Although there is not a big deal to update then flash the updated rom. Not sure why so many people worry about updates when a custom rom update will show up.
You also can get an app call otarootkeeper and lastly google is full of methods to achieve your goal its always good to google prior to posting a question... Never know what you may find
playya said:
Not sure if this is your first android phone but its generally the same with all of them. If you root and alter files that the update checks for it will not update. Although there is not a big deal to update then flash the updated rom. Not sure why so many people worry about updates when a custom rom update will show up.
You also can get an app call otarootkeeper and lastly google is full of methods to achieve your goal its always good to google prior to posting a question... Never know what you may find
Click to expand...
Click to collapse
OTA RootKeeper no longer works as of 4.3. The way to get root back now is by installing SuperSU through recovery.
Acuity said:
OTA RootKeeper no longer works as of 4.3. The way to get root back now is by installing SuperSU through recovery.
Click to expand...
Click to collapse
Yea but flashing Su would mean installing a custom recovery. He is trying to stay stock
Sent from my Nexus 4 using Tapatalk 4
playya said:
Yea but flashing Su would mean installing a custom recovery. He is trying to stay stock
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
You can revert back to stock recovery by downloading the factory image and flashing recovery.img buried deep within it:
fastboot flash recovery C:/recovery.img
OTA RootKeeper has served its purpose, and had done so for a long time; however, it is currently no longer functional.
Acuity said:
You can revert back to stock recovery by downloading the factory image and flashing recovery.img buried deep within it:
fastboot flash recovery C:/recovery.img
OTA RootKeeper has served its purpose, and had done so for a long time; however, it is currently no longer functional.
Click to expand...
Click to collapse
I agree with you but saying a person that wants stock normally is trying to do as little as possible to their phone. Flashing a recovery via fastboot may not be an option. If thats the case you can simply just flash the stock recovery via zipfile and use SuperSu and it has an uninstall root function
briand.mooreg said:
I'm getting a Nexus 4. My question is if I root but keep stock, will I still receive updates?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I did just that.. When I bought my phone it had 4.2.2. Flashed a custom recovery, then rooted it as well.. When 4.3 OTA was out, mine also downloaded it.. I unrooted my phone using the unroot option in SuperSu and flashed stock recovery back and installed OTA just like a layman would, and , well, 4.3..
Later I read in this forum that few ppl who had custom recovery also were able to update normally to 4.3 through OTA.. But I didn't do that , so I can't give my word on that.
In case you don't get the ota or if it is unsuccessful, you can always do this
http://forum.xda-developers.com/showthread.php?t=2010312
Happy rooting !
Sent from my Nexus 4 using Tapatalk 4
I was wondering if there was any work being done with a pure AOSP rom or any other roms that will theme with a locked bootloader.
The answer is sort-of...
No, you cannot unlock the boot loader if you the latest ota.
Yes, you can root and install safestrap, then look for a desirable ROM.
The third option I played with is replace as many of the Motorola apps as you can with the aosp versions. It is dangerous, I only tried it with email and that worked great, but I moved on to contacts and totally screwed up the ROM forcing me to flash back to stock and redo everything.
Sent from my Nexus 10 using Tapatalk 2
There is a work around for the latest OTA hehehe
Flash the stock.IMG in fastboot with the toolkit. It will flash a compatible version where you can unlock and root from there.
If you want AOSP... Carbon ROM is the closest in my opinion so far...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Can you elaborate more on this process? What do you mean unlock, I thought that was impossible now? Which toolkit? So confused.
Sent from my Nexus 10 using Tapatalk 2
lukkypuggy said:
There is a work around for the latest OTA hehehe
Flash the stock.IMG in fastboot with the toolkit. It will flash a compatible version where you can unlock and root from there.
If you want AOSP... Carbon ROM is the closest in my opinion so far...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Has this method been tested and confirmed?
CrocadileUT78 said:
Can you elaborate more on this process? What do you mean unlock, I thought that was impossible now? Which toolkit? So confused.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
There is a Root Toolkit here in one of the forums, look for version 1.20
By unlock I mean unlocking the bootloader. It is only impossible if you don't flash an earlier version of the stock.img.
Yes it is confirmed, that is how I am running Carbon right now
Sent from my XT907 using XDA Premium 4 mobile app
So you had the 78 update, and downgraded, then unlocked bootloader? Everything else I read said that doesn't work. I'm so confused.
Sent from my XT907 using Tapatalk 4
I didnt think one could downgrade if they had a locked boot loader?! Anyone who had actually achieved this please chime in here.
lukkypuggy said:
There is a Root Toolkit here in one of the forums, look for version 1.20
By unlock I mean unlocking the bootloader. It is only impossible if you don't flash an earlier version of the stock.img.
Yes it is confirmed, that is how I am running Carbon right now
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Curious as well how did you go about this? I thought it was impossible to unlock on latest ota. If this is the case, why has this not been brought up earlier?
Sent from my XT907 using Tapatalk 2
CrocadileUT78 said:
So you had the 78 update, and downgraded, then unlocked bootloader? Everything else I read said that doesn't work. I'm so confused.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
lukkypuggy said:
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I might be able to test this, but can you explain, by steps, how you did this?
Sent from my XT907 using Tapatalk 2
lukkypuggy said:
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you buy it used? If so, when? If you did, it may have already been unlocked...
Sent from my XT907 using Tapatalk 4
Here is the kit I use: http://forum.xda-developers.com/showthread.php?t=2249773
"Number 1 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 System, Kernel, and Radio as well we wipe your data.
Number 2 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 Stock Recovery.
Number 3 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash TWRP Recovery by Hashcode.
Number 4 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash CWM Recovery by Hashcode.
Number 5 Explained -- This is Dan Rosenberg's root exploit called 'Motochopper'. This option requires your phone to be booted normally, with USB Debugging enabled.
Number 6 Explained -- This option requires your phone to be booted normally, with USB Debugging enabled. It will install an App version of Dan Rosenberg's Motopocalypse exploit for unlocking the bootloader.
Remember, do not run this utility unless your phone is at 100% battery OR you have bought yourself one of Team Black Hat's Factory-Style Programming Adapters."
Click to expand...
Click to collapse
First backup your data and im not responsible if you cause the apocalypse
OK. chose option #1. It will flash a rootable version.
Next to root, choose option #5.
Next chose option #6 to ULOCK your bootloader.
Next chose either option 3 or 4 for a custom recovery. (I like CWM)
Have fun. that is exactly What I Did.
lukkypuggy said:
Here is the kit I use: http://forum.xda-developers.com/showthread.php?t=2249773
First backup your data and im not responsible if you cause the apocalypse
OK. chose option #1. It will flash a rootable version.
Next to root, choose option #5.
Next chose option #6 to ULOCK your bootloader.
Next chose either option 3 or 4 for a custom recovery. (I like CWM)
Have fun. that is exactly What I Did.
Click to expand...
Click to collapse
So just making sure, you were on the 4.1.2 ota prior to doing this right? Based on the notice posted on that utility thread, you are not suppose to use it if you were on the latest ota, which is the same one that locked the bootloader (unless stood corrected). So did you take a leap of faith and went ahead and did it even though it was warned to not do it, and did you ended up succeeding?
Was your phone bought new, or do you know if it's previous owner unlocked it before you got a hold of it, which would explain how you were able to, IF it wasn't used and modified prior?
Also, when you flashed the "compatible version" was it that you flashed the 4.1.2 update found in the utility or did you change it out to another image found here: http://sbf.droid-developers.org/scorpion_mini_xt907/list.php
Just wandering, because if so, this is phenomenal news for those who have do not possess the ability to unlock normally because they took the recent ota. I am sure that like everyone else, including myself, we just want to know if this is safe to follow or not, no pointing fingers or bad accusations.
Thanks
MistPhoenix said:
So just making sure, you were on the 4.1.2 ota prior to doing this right? Based on the notice posted on that utility thread, you are not suppose to use it if you were on the latest ota, which is the same one that locked the bootloader (unless stood corrected). So did you take a leap of faith and went ahead and did it even though it was warned to not do it, and did you ended up succeeding?
Was your phone bought new, or do you know if it's previous owner unlocked it before you got a hold of it, which would explain how you were able to, IF it wasn't used and modified prior?
Also, when you flashed the "compatible version" was it that you flashed the 4.1.2 update found in the utility or did you change it out to another image found here: http://sbf.droid-developers.org/scorpion_mini_xt907/list.php
Just wandering, because if so, this is phenomenal news for those who have do not possess the ability to unlock normally because they took the recent ota. I am sure that like everyone else, including myself, we just want to know if this is safe to follow or not, no pointing fingers or bad accusations.
Thanks
Click to expand...
Click to collapse
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
lukkypuggy said:
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
Click to expand...
Click to collapse
I believe you... Now the question is who is brave enough to take a leap of faith? I would love to unlock by boot loader to ensure I will get the latest Android versions moving forward. I don't trust Verizon to let an upgrade thru beyond 4.1.2. I would test your procedure myself, but I'm too dependent on my phone for work right now.
So... Anyone? Anyone? Be a hero folks, somebody take the plunge! Pretty please?
Sent from my Nexus 10 using Tapatalk 2
---------- Post added at 01:06 AM ---------- Previous post was at 12:51 AM ----------
Also, I feel obligated to mention this, and i do it with a heavy heart... A few weeks ago I seriously screwed up my phone playing with the contacts apk, breaking my ability to view my contacts or dial a number. I got desperate enough that even though I was on .78, used the utility and stock image to revert back everything fresh. I was so relieved when I saw it worked despite the warnings and being a slightly older rom version. Once I did that, I'm 75% sure I did trying unlocking the BL before installing .78 OTA, and it did not work. I figured I had nothing to lose at that point, and when it failed I just shrugged and continued getting my phone back to normal. Sorry if this discourages any brave souls, but again I am not 100% sure I followed the same steps Mentioned in this thread.
Sent from my Nexus 10 using Tapatalk 2
lukkypuggy said:
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
Click to expand...
Click to collapse
Thank you for the response. I do plan on testing this later on today on a locked, new M so I will be able to verify completely. Everyone sit tight
Sent from my XT907 using Tapatalk 2
CrocadileUT78 said:
I believe you... Now the question is who is brave enough to take a leap of faith? I would love to unlock by boot loader to ensure I will get the latest Android versions moving forward. I don't trust Verizon to let an upgrade thru beyond 4.1.2. I would test your procedure myself, but I'm too dependent on my phone for work right now.
So... Anyone? Anyone? Be a hero folks, somebody take the plunge! Pretty please?
Sent from my Nexus 10 using Tapatalk 2
---------- Post added at 01:06 AM ---------- Previous post was at 12:51 AM ----------
Also, I feel obligated to mention this, and i do it with a heavy heart... A few weeks ago I seriously screwed up my phone playing with the contacts apk, breaking my ability to view my contacts or dial a number. I got desperate enough that even though I was on .78, used the utility and stock image to revert back everything fresh. I was so relieved when I saw it worked despite the warnings and being a slightly older rom version. Once I did that, I'm 75% sure I did trying unlocking the BL before installing .78 OTA, and it did not work. I figured I had nothing to lose at that point, and when it failed I just shrugged and continued getting my phone back to normal. Sorry if this discourages any brave souls, but again I am not 100% sure I followed the same steps Mentioned in this thread.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
BTW I never did get the unlock app to actually work (just remembered).
http://forum.xda-developers.com/showthread.php?t=2226729
http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
Download this .zip file once you have flashed the compatible stock version and have root.
As long as it says status code: 3 in the bootloader you are unlocked
Ok guys here are the results, sadly I could not achieve unlock with a unmodified, unrooted Razr M :
1. Turned off and started AP Fastboot mode. Used mattlgroff's Razr M Utility to flash to Android 4.1.2 98.15.66.XT907.Verizon.en.US system image. The flash worked perfectly I was able to downgrade to ota prior before the locked bootloader.
2. Used mattlgroff's Utility to root my device (step 5). I was able to root the device with SuperSU.
3. Used the seperate motopocalypse program by Dan Rosenberg found here http://forum.xda-developers.com/showthread.php?t=2226729. It ran and rebooted to AP fastboot mode. I received the folowing errors:
"TrustZone target address resolved to 2a020a02"
"TrustZone write failed: -11"
This indicated that the bootloader TrustZone which is needed to unlock, was still locked and that it couldn't make changes to properly unlock the device.
So for the time being, this method to unlock the bootloader does not work. I am thinking about trying the 4.1.1 system image instead, but I fear that since the bootloader is its own entity, that those that took the recent OTA had the TrustZone patched to the point where it cannot be written to period, even on a lower firmware. The best thing that could happen is for a miracle to occur and an exploit to be found to write to the TrustZone again.
MistPhoenix said:
Ok guys here are the results, sadly I could not achieve unlock with a unmodified, unrooted Razr M :
1. Turned off and started AP Fastboot mode. Used mattlgroff's Razr M Utility to flash to Android 4.1.2 98.15.66.XT907.Verizon.en.US system image. The flash worked perfectly I was able to downgrade to ota prior before the locked bootloader.
2. Used mattlgroff's Utility to root my device (step 5). I was able to root the device with SuperSU.
3. Used the seperate motopocalypse program by Dan Rosenberg found here http://forum.xda-developers.com/showthread.php?t=2226729. It ran and rebooted to AP fastboot mode. I received the folowing errors:
"TrustZone target address resolved to 2a020a02"
"TrustZone write failed: -11"
This indicated that the bootloader TrustZone which is needed to unlock, was still locked and that it couldn't make changes to properly unlock the device.
So for the time being, this method to unlock the bootloader does not work. I am thinking about trying the 4.1.1 system image instead, but I fear that since the bootloader is its own entity, that those that took the recent OTA had the TrustZone patched to the point where it cannot be written to period, even on a lower firmware. The best thing that could happen is for a miracle to occur and an exploit to be found to write to the TrustZone again.
Click to expand...
Click to collapse
Mine had the -11 error also but it also said status code 3 in the actually bootloader, Then I flashed CWM and that was it, now I have CM10.1.3 STABLE.
Maybe double check?