I just used casual to root and unlock my note 2.i have root and it booted up on twrp but I want to check if I am unlocked bootloader. Is there a way I can check? In my about phone my status says normal
If the bootloader was not unlocked it would overwrite any changes you make to recovery and system files. So as long as you can reboot without losing TWRP or any custom ROM you've installed you're golden.
Unlocked Bootloader?
Jiggabitties said:
If the bootloader was not unlocked it would overwrite any changes you make to recovery and system files. So as long as you can reboot without losing TWRP or any custom ROM you've installed you're golden.
Click to expand...
Click to collapse
It's been a while for me since I rooted my phone, and I don't know if I unlocked my bootloader either... I have never installed a custom ROM, I only rooted so I could tether. But now that the new OTA update keeps trying to install itself, I need to fix this because it's extremely annoying. I read a thread that said I need to flash this: http://forum.xda-developers.com/showthread.php?t=2578458, but it said that I need my bootloader to be unloacked, and therein lies my question...
Am I thinking this through the correct way?
If you just want to stop the update notification fteeze SDM 1.0
James Mac said:
It's been a while for me since I rooted my phone, and I don't know if I unlocked my bootloader either... I have never installed a custom ROM, I only rooted so I could tether. But now that the new OTA update keeps trying to install itself, I need to fix this because it's extremely annoying. I read a thread that said I need to flash this: http://forum.xda-developers.com/showthread.php?t=2578458, but it said that I need my bootloader to be unloacked, and therein lies my question...
Am I thinking this through the correct way?
Click to expand...
Click to collapse
That is the correct thread. Easy way to check is to boot into recovery and see if there is a custom recovery installed. Power down your device, hold down the volume up + verizon button, then power up. Hold volume up + verizon button until you see the galaxy note 2 splash screen. If it boots into TWRP than you're still good. But you will probably want to update to the latest version of TWRP before you go installing any new roms.
Jiggabitties said:
That is the correct thread. Easy way to check is to boot into recovery and see if there is a custom recovery installed. Power down your device, hold down the volume up + verizon button, then power up. Hold volume up + verizon button until you see the galaxy note 2 splash screen. If it boots into TWRP than you're still good. But you will probably want to update to the latest version of TWRP before you go installing any new roms.
Click to expand...
Click to collapse
Thanks Jiggabitties, I updated TWRP and downloaded official firmware.md5 file and the Mj9 DeOdex file to my pc. Should I transfer those files to the sd card in my phone and install from the TWRP menu? If so, I do the official firmware file first, right? Then the deodex...?
Thanks for all your help man
James Mac said:
Thanks Jiggabitties, I updated TWRP and downloaded official firmware.md5 file and the Mj9 DeOdex file to my pc. Should I transfer those files to the sd card in my phone and install from the TWRP menu? If so, I do the official firmware file first, right? Then the deodex...?
Thanks for all your help man
Click to expand...
Click to collapse
The firmware update is done in ODIN and the ROM is done in TWRP.
James Mac said:
Thanks Jiggabitties, I updated TWRP and downloaded official firmware.md5 file and the Mj9 DeOdex file to my pc. Should I transfer those files to the sd card in my phone and install from the TWRP menu? If so, I do the official firmware file first, right? Then the deodex...?
Thanks for all your help man
Click to expand...
Click to collapse
Yes start by transferring the files to your SD card.
The firmware package from that thread is meant to be flashed via ODIN. If you are not comfortable in flashing firmware via ODIN then use this in it's place... https://www.dropbox.com/s/lz29kvrvzfttfpu/MJ9ModemParams.zip This is a TWRP flashable version of the firmware.
Place the MJ9 Deodex and the modemparam.zip I linked to above on your SD card. Flash the ROM file first, then the modemparam.zip. Then clear cache/ dalvik and reboot. That should be all you need to do. If when you boot you don't get service, then you will need to go ahead and flash the firmware vid ODIN. Some users have no issues with the flashable version that I linked above, some users do.
Related
I'm trying to get into the bootloader to flash an older version of TWRP. I'm holding various combinations of buttons down when rebooting but the phone either goes to Recovery, Odin, or normal boot. The "bootloader" boot option in TWRP doesn't work either, it just goes to normal boot. What am I missing? I know for many phones the bootloader is accessed by holding VOL Down + Power when rebooting but that's not working on the Note 2.
Thanks.
slicknick27 said:
I'm trying to get into the bootloader to flash an older version of TWRP. I'm holding various combinations of buttons down when rebooting but the phone either goes to Recovery, Odin, or normal boot. The "bootloader" boot option in TWRP doesn't work either, it just goes to normal boot. What am I missing? I know for many phones the bootloader is accessed by holding VOL Down + Power when rebooting but that's not working on the Note 2.
Thanks.
Click to expand...
Click to collapse
I believe the reason why you can't boot into bootloader is because it has something to do with the Unlock Bootloader method/exploit. I'm going to take a shot in the dark and say the exploit is not the standard unlock method so therefore you can't boot into the bootloader.
Also, you can flash a recovery a different way. Download the Goo.im Manager app in the Google Play Store and when you go in the app, you can search the recoveries and it will flash them from the app for you.
DroidOnRoids said:
I believe the reason why you can't boot into bootloader is because it has something to do with the Unlock Bootloader method/exploit. I'm going to take a shot in the dark and say the exploit is not the standard unlock method so therefore you can't boot into the bootloader.
Also, you can flash a recovery a different way. Download the Goo.im Manager app in the Google Play Store and when you go in the app, you can search the recoveries and it will flash them from the app for you.
Click to expand...
Click to collapse
Hey, thanks for shedding some light on this. And I'm going to try flashing from the Goo.im manager, that sounds easier at this point, too.
slicknick27 said:
Hey, thanks for shedding some light on this. And I'm going to try flashing from the Goo.im manager, that sounds easier at this point, too.
Click to expand...
Click to collapse
No problem, man. Just make sure you flash the right recovery file because if you are broad on your search, it will give you a list of different recoveries for different devices. Search the version of TWRP you want with 'i605'.
DroidOnRoids said:
No problem, man. Just make sure you flash the right recovery file because if you are broad on your search, it will give you a list of different recoveries for different devices. Search the version of TWRP you want with 'i605'.
Click to expand...
Click to collapse
Unfortunately there are no older versions of TWRP in the Goo.im manager app. This is off-topic from my original question but it's the reason I was trying to get into the bootloader in the first place. Do you know of any way to downgrade TWRP to a previous version on this phone other than the flashing from bootloader method?
slicknick27 said:
Unfortunately there are no older versions of TWRP in the Goo.im manager app. This is off-topic from my original question but it's the reason I was trying to get into the bootloader in the first place. Do you know of any way to downgrade TWRP to a previous version on this phone other than the flashing from bootloader method?
Click to expand...
Click to collapse
Hm, you searched with i605, right? Well, I searched and found that on Goo.im, it is actually t0ltevzw.
Here are all the TWRP builds for the VZW Note 2 from Goo.im: http://goo.im/devs/OpenRecovery/t0ltevzw/
EDIT: Here's our device page on the TWRP website: http://teamw.in/project/twrp2/133
EDIT 2: If I were you, try not to flash a recovery using Odin. I wouldn't risk screwing up the unlocked bootloader exploit. Lastly, if you didn't know, do NOT in any way flash a custom rom using Odin. It's bad news for your phone.
Edited again because I forgot fastboot requires bootloader access lol
Hmm yes, searching the exact name "t0ltevzw" brought up TWRP 2.4.0.0, however it did not work and TWRP still reports as 2.4.1.0. I am trying to downgrade because this latest version is apparently giving me trouble with an MD5 checksum on the L4 modem zip. (the zip verifies correctly on the SDCard when checked from my PC).
I was thinking of just bypassing the MD5 check in TWRP since I'm able to verify that MD5 is correct through my PC, but I don't want to risk anything with a modem flash...it worries me that TWRP keeps saying the md5 is wrong.
I don't have adb set up yet so it seems now is going to be a good time. And thanks for the tips about Odin, I already knew this from the sticky in the Android forum, but it probably bears (a lot) of repeating haha
DroidOnRoids said:
Hm, you searched with i605, right? Well, I searched and found that on Goo.im, it is actually t0ltevzw.
Here are all the TWRP builds for the VZW Note 2 from Goo.im: http://goo.im/devs/OpenRecovery/t0ltevzw/
EDIT: Here's our device page on the TWRP website: http://teamw.in/project/twrp2/133
EDIT 2: If I were you, try not to flash a recovery using Odin. I wouldn't risk screwing up the unlocked bootloader exploit. Lastly, if you didn't know, do NOT in any way flash a custom rom using Odin. It's bad news for your phone.
Edited again because I forgot fastboot requires bootloader access lol
Click to expand...
Click to collapse
Hmm yes, searching the exact name "t0ltevzw" brought up TWRP 2.4.0.0, however it did not work and TWRP still reports as 2.4.1.0. I am trying to downgrade because this latest version is apparently giving me trouble with an MD5 checksum on the L4 modem zip. (the zip verifies correctly on the SDCard when checked from my PC).
I was thinking of just bypassing the MD5 check in TWRP since I'm able to verify that MD5 is correct through my PC, but I don't want to risk anything with a modem flash...it worries me that TWRP keeps saying the md5 is wrong.
I don't have adb set up yet so it seems now is going to be a good time. And thanks for the tips about Odin, I already knew this from the sticky in the Android forum, but it probably bears (a lot) of repeating haha
slicknick27 said:
Hmm yes, searching the exact name "t0ltevzw" brought up TWRP 2.4.0.0, however it did not work and TWRP still reports as 2.4.1.0. I am trying to downgrade because this latest version is apparently giving me trouble with an MD5 checksum on the L4 modem zip. (the zip verifies correctly on the SDCard when checked from my PC).
I was thinking of just bypassing the MD5 check in TWRP since I'm able to verify that MD5 is correct through my PC, but I don't want to risk anything with a modem flash...it worries me that TWRP keeps saying the md5 is wrong.
I don't have adb set up yet so it seems now is going to be a good time. And thanks for the tips about Odin, I already knew this from the sticky in the Android forum, but it probably bears (a lot) of repeating haha
Click to expand...
Click to collapse
So the 2.4.0.0 is the version you want, correct? And which file of this recovery version did you download? If you tried downloading and installing using the Goo.im app, try downloading the zip file from your computer and transferring it over to your SD Card. From there you can reboot to the existing recovery, install it, and reboot the recovery.
If that doesn't work either, tell me and I can figure out a different option.
DroidOnRoids said:
So the 2.4.0.0 is the version you want, correct? And which file of this recovery version did you download? If you tried downloading and installing using the Goo.im app, try downloading the zip file from your computer and transferring it over to your SD Card. From there you can reboot to the existing recovery, install it, and reboot the recovery.
If that doesn't work either, tell me and I can figure out a different option.
Click to expand...
Click to collapse
Actually, if I can I'd like to downgrade to TWRP 2.3.3.1, which was the version I installed back when I got the phone in December.
On Goo.im web site it is:
openrecovery-twrp-2.3.3.1-t0ltevzw.zip
It is my understanding though that you can't flash TWRP from within TWRP?
slicknick27 said:
Actually, if I can I'd like to downgrade to TWRP 2.3.3.1, which was the version I installed back when I got the phone in December.
On Goo.im web site it is:
openrecovery-twrp-2.3.3.1-t0ltevzw.zip
It is my understanding though that you can't flash TWRP from within TWRP?
Click to expand...
Click to collapse
You can flash CWM in TWRP, TWRP in CWM, TWRP in TWRP, or CWM in CWM. All you need to do is flash it and then go to the recovery options and hit Reboot Recovery.
Where did you hear that you can't flash TWRP in TWRP?
DroidOnRoids said:
You can flash CWM in TWRP, TWRP in CWM, TWRP in TWRP, or CWM in CWM. All you need to do is flash it and then go to the recovery options and hit Reboot Recovery.
Where did you hear that you can't flash TWRP in TWRP?
Click to expand...
Click to collapse
OK, yeah, I was told in another thread that I couldn't flash TWRP with TWRP.
So, I just want to clarify, I can flash an older version of TWRP over an newer version of TWRP already installed -- as if I was flashing any regular .zip?
slicknick27 said:
OK, yeah, I was told in another thread that I couldn't flash TWRP with TWRP.
So, I just want to clarify, I can flash an older version of TWRP over an newer version of TWRP already installed -- as if I would flash any regular .zip?
Click to expand...
Click to collapse
Yes, you can do that because it's going to completely overwrite the other version of TWRP. It doesn't matter what version you flash because it's going to be all on its own. The previous recovery doesn't benefit from a newer version of a recovery. You're safe to do it
EDIT: When I had my Galaxy Nexus, TWRP was brand spanking new so I had to downgrade a lot because of all the bugs presented in the later releases.
DroidOnRoids said:
Yes, you can do that because it's going to completely overwrite the other version of TWRP. It doesn't matter what version you flash because it's going to be all on it's own. The previous recovery doesn't benefit from a newer version of a recovery. You're safe to do it
EDIT: When I had my Galaxy Nexus, TWRP was brand spanking new so I had to downgrade a lot because of all the bugs presented in the later releases.
Click to expand...
Click to collapse
Phew. OK. Well again I thank you for sticking with me and clearing this up. I suspected I could do that in the first place but was confused by information I was given otherwise. Off I go to recovery!
slicknick27 said:
Phew. OK. Well again I thank you for sticking with me and clearing this up. I suspected I could do that in the first place but was confused by information I was given otherwise. Off I go to recovery!
Click to expand...
Click to collapse
Good luck! Let me know when it's a success.
DroidOnRoids said:
Good luck! Let me know when it's a success.
Click to expand...
Click to collapse
Well, TWRP verified the checksum and the modem installed successfully. But apparently it turns out the problem was not as it originally seemed.
When I downloaded the older version of TWRP, I opened its .MD5 file again just to check, and I noticed that the .MD5 files for the zips on Goo.im (or at least OpenRecovery's ZIPS) omitted the asterisk that precedes the filename:
Code:
d4624c4f8c9427b6137b2b97902e76b3 openrecovery-twrp-2.4.1.0-t0ltevzw.zip
Whereas with other .MD5 files that I've created (including the .MD5 file for the modem zip that was failing verification in TWRP), I've used an asterisk before the filename:
Code:
d4624c4f8c9427b6137b2b97902e76b3 [B][COLOR="Red"]*[/COLOR][/B]openrecovery-twrp-2.4.1.0-t0ltevzw.zip
So after the modem flashed successfully on TWRP 2.3, I decided to try flashing it again (with the asterisk omitted from the MD5 file) on the latest TWRP 2.4.1.0. It flashed just fine. So the issue seems to be TWRP getting hung up on the asterisk that precedes the filename in MD5 files -- though this doesn't happen all the time because I've flashed many MD5 files with the asterisk successfully.
A bug in TWRP? Or maybe I shouldn't be using the asterisk at all. In any case, I'm back on TWRP 2.4.1.0 with the modem flashed.
EDIT: And I learned that you can flash TWRP in TWRP
slicknick27 said:
Well, TWRP verified the checksum and the modem installed successfully. But apparently it turns out the problem was not as it originally seemed.
When I downloaded the older version of TWRP, I opened its .MD5 file again just to check, and I noticed that the .MD5 files for the zips on Goo.im (or at least OpenRecovery's ZIPS) omitted the asterisk that precedes the filename:
d4624c4f8c9427b6137b2b97902e76b3 openrecovery-twrp-2.4.1.0-t0ltevzw.zip
Whereas with other .MD5 files that I've created (including the .MD5 file for the modem zip that was failing verification in TWRP), I've used an asterisk before the filename:
d4624c4f8c9427b6137b2b97902e76b3 *openrecovery-twrp-2.4.1.0-t0ltevzw.zip
So after the modem flashed successfully on TWRP 2.3, I decided to try flashing it again (with the asterisk omitted from the MD5 file) on the latest TWRP 2.4.1.0. It flashed just fine. So the issue seems to be TWRP getting hung up on the asterisk that precedes the filename in MD5 files -- though this doesn't happen all the time because I've flashed many MD5 files with the asterisk successfully.
A bug in TWRP? Or maybe I shouldn't be using the asterisk at all. In any case, I'm back on TWRP 2.4.1.0 with the modem flashed.
EDIT: And I learned that you can flash TWRP in TWRP
Click to expand...
Click to collapse
I would bring that to their attention and see why that's the case on their recovery. Anyway, glad that everything is figured out and running perfectly. :good:
DroidOnRoids said:
I would bring that to their attention and see why that's the case on their recovery. Anyway, glad that everything is figured out and running perfectly. :good:
Click to expand...
Click to collapse
Yes I'm going to report it.
Take it easy.
Really didn't want to make a new thread about this but honestly people just jumped to conclusions without being helpful in my previous thread.
Long story short I'm trying to manually get 4.4.2: http://forum.xda-developers.com/showthread.php?t=2664561
I saw that I needed to get s-off, which requires root. Bootloader was already unlocked and so did everything here: http://forum.xda-developers.com/showthread.php?t=2273376
I installed CWM. It said to install a superuser tool so I installed SuperSU.
"You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead." was the next line. <-- I saw that message. Installed a kernel that he recommended: http://forum.xda-developers.com/showthread.php?t=2255900
After reboot I get SuperSU error: There is no SU binary installed and SuperSU cannot install it. If you just upgraded to Android 4.3, you need to manually re-root- consult the relevant forums for your device etc.
Can anyone help me get the proper SU Binary installed? Not a beginner to rooting as I've had had several previous phones before. Never encountered something as annoying as this.
On 4.3, 3.17.502.3.
I had the same issue when I installed 4.4.2 on my international One.
What I done to root was;
- downloaded SuperSU v1.80 zip from here.
- download SuperSu from the Play Store
- in SuperSU, select the option to install binaries via TWRP/CWM. (If it doesn't reboot to recovery, manually enter recovery)
- flash the supersu v1.80 zip and reboot
- open SuperSu and install the binaries using the normal option.
That then enabled my root. I'd tried quite a few different variations and this was the only method that worked for me.
Sent from my HTC One or Note 3 via XDA Premium 4
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
mch277 said:
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
Click to expand...
Click to collapse
You seem very confused about the whole rooting process ... what was the point in flashing the stock recovery ? Are you trying to install the OTAPkg.zip ?
what Rom are you wanting to install and whats flashing stock recovery have to do with it ?
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
mch277 said:
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
Click to expand...
Click to collapse
I wrote the thread you linked too
http://forum.xda-developers.com/showthread.php?t=2659374
and yes it is necessary to have stock recovery to take an OTA, but your post didn't mention taking OTA it said you had no SU installed.
to get into stock recovery
boot to bootloader
choose recovery
wait for black screen, hold vol up and then power
you will see something about sdcard fail .. ignore it till the menu comes up
then choose to flash OTAPkg.zip from sdcard
I have converted my padfone x to a padfone s
The basic way I did it was follow the directions for installing cm12 boot cm12 using fastboot boot cwm6.img instead of flashing unlocking the bl using cwm6 ( I was not running a tested version of att software) then flashing the flash the newest ww padfone s firmware from their webpage then doinf a data format then rebooting to stock recovery and flashing the asus firmware a second time then factory reset.. I kept BL unlock and did not flash new recovery because I will unroot when 5.0 is released. second bonus is incall recording. but the minus is the mobile net connection is based on strongest signal not fastest and LTE band 17 needs to be enabled on each boot using anycut But in my opinion the benefits are way better the the lte thing HSPA is really fast enough. IF these instructions dont make any sense to you dont ask for help they are to advanced for you
Update
LTE has worked it self out. this conversion is 100% and my device is still unlocked BL and SIM
Very good. Thank you for posting this. Currently on tmo running CM12 and will be attempting this
magiconthetire said:
Very good. Thank you for posting this. Currently on tmo running CM12 and will be attempting this
Click to expand...
Click to collapse
good luck first boot takes along time
also flash stock recovery then in fastboot boot to cwm6 using fastboot boot cwm6.img and when it loads do a data and system format flash the update from asus padfone s support page. i used the WW one then power off not reboot then reboot into stock recovery (took some time) then flash the update with stock and factory reset
This is the firmware package i used.
http://dlcdnet.asus.com/pub/ASUS/Mobile_Phone/PadFone_S/UL-ASUS_T00N-WW-11.10.7.11-user.zip
After root with this
A new thing I've noticed with this waw firmware it supports incall call recording
an interesting thing. the zip file from asus does not update the modem.
tjsooley said:
I have converted my padfone x to a padfone s
Click to expand...
Click to collapse
Can you please be more specific?
Did you install an original firmware to your AT&T Padfone X?
I am trying to do so with WW original firmware, but I keep getting an error about signature.
atinkrios said:
Can you please be more specific?
Did you install an original firmware to your AT&T Padfone X?
I am trying to do so with WW original firmware, but I keep getting an error about signature.
Click to expand...
Click to collapse
I installed ww firmware follow the directions in this thread
start with this http://forum.xda-developers.com/showpost.php?p=59623876&postcount=167
then copy the ww firmware to your sd then boot into recovery and format system and data not media and install the ww firmware after that reboot recovery a second time and flash the firmware with the stock recovery it took a few reboots to get it to boot but its golden afer
tjsooley said:
I installed ww firmware follow the directions in this thread
start with this http://forum.xda-developers.com/showpost.php?p=59623876&postcount=167
then copy the ww firmware to your sd then boot into recovery and format system and data not media and install the ww firmware after that reboot recovery a second time and flash the firmware with the stock recovery it took a few reboots to get it to boot but its golden afer
Click to expand...
Click to collapse
After bricking my phone, I managed to push the zip file into recovery mode. However, I cannot update my phone to WW version as it states that Padfone X is a T00D instead of T00N!!!
How did you manage to push the files into it?
Or you just installed the CM12?
atinkrios said:
After bricking my phone, I managed to push the zip file into recovery mode. However, I cannot update my phone to WW version as it states that Padfone X is a T00D instead of T00N!!!
How did you manage to push the files into it?
Or you just installed the CM12?
Click to expand...
Click to collapse
I copied the files to sd first and did not factory reset I just formatted data without media
I installed cm12 first and got that booting then formatted my phone and installed the WW you need to use cwm6 to unlock the BL and system MUST be empty when flashing the zip
tjsooley said:
I copied the files to sd first and did not factory reset I just formatted data without media
I installed cm12 first and got that booting then formatted my phone and installed the WW you need to use cwm6 to unlock the BL and system MUST be empty when flashing the zip
Click to expand...
Click to collapse
I managed to get the phone on.
However I have a hard time to install CWM6. It turns black and doesn't answer to any touch.
Did it happen to you too?
I didn't install I did a fast boot boot and booted the image
Sent from my ASUS_T00N using Tapatalk
tjsooley said:
I didn't install I did a fast boot boot and booted the image
Sent from my ASUS_T00N using Tapatalk
Click to expand...
Click to collapse
I was doing the same mistake again. I rebooting with me CABLE ON!!!!
I managed to install the new T00N version from ASUS website.
First boot had some issues. I did a second install and waiting for the result.
Thank you for your support.
atinkrios said:
I was doing the same mistake again. I rebooting with me CABLE ON!!!!
I managed to install the new T00N version from ASUS website.
First boot had some issues. I did a second install and waiting for the result.
Thank you for your support.
Click to expand...
Click to collapse
Welcome. We most likely wont get OTA's even unrooted because the BL is now unlocked and we cannot relock them because of the way the BL is unlocked so we just need to wait till the DL is posted by ASUS
tjsooley said:
Welcome. We most likely wont get OTA's even unrooted because the BL is now unlocked and we cannot relock them because of the way the BL is unlocked so we just need to wait till the DL is posted by ASUS
Click to expand...
Click to collapse
Are you using the new update from the Asus website or the Nightly Cyogen?
I am using the one from Asus and the phone keeps rebooting.
Asus and no reboots do a factory reset them reflash from stock recovery
Sent from my ASUS_T00N using Tapatalk
Did mobile hotspot work okay after moving to Padfone S?
Hi
Yesterday I received the OTA update (LMY48I stagefright-fix) on my unlocked and rooted Nexus 9. When I tried to install it update the tablet rebooted and I ended up with a dead android on screen and the message: "Error". I was able to reboot but the update was not installed. I assume it is because it is rooted that I can't use OTA update.
How do I properly update to LMY48I without risking bricking my device? I have been searching around a bit but I can't seem to find a safe way to do it.
Has anyone experienced similar problems?
Any help is appreciated.
Thanks
Kenneth Andreasen said:
Hi
How do I properly update to LMY48I without risking bricking my device? I have been searching around a bit but I can't seem to find a safe way to do it.
Click to expand...
Click to collapse
OTA failed to install because you were rooted, as you suspected.
I assume that by "unlocked", you mean your bootloader is unlocked?
If so, follow the "Long Method" in the following tutorial (short method, flash_all doesn't work) > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Download your factory image from here > https://developers.google.com/android/nexus/images
cam30era said:
OTA failed to install because you were rooted, as you suspected.
I assume that by "unlocked", you mean your bootloader is unlocked?
If so, follow the "Long Method" in the following tutorial (short method, flash_all doesn't work) > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Download your factory image from here > https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
can i do all that and still keep all my apps and data? im thinking of going to LMy48l too
cobyman7035 said:
can i do all that and still keep all my apps and data? im thinking of going to LMy48l too
Click to expand...
Click to collapse
Yes. Only flash the following files:
bootloader.img
system.img
vendor.img
boot.img.
Note the following:
1) Make sure your Android SDK is reasonable up to date. Google updated fastboot in November 2014, to allow flashing these very large system.img files for Lollipop.
2) IF you are unencrypted, you will need to flash an unencrypted kernel.
3) IF you want to keep root and TWRP, do the following:
- after you fastboot flash the last .img file, stop using your PC/terminal.
- pick up your N9 and using the volume buttons, navigate to hboot and select it with power button.
- once in hboot, use buttons to navigate to and select Recovery
- TWRP will boot. Flash your SuperSU .zip and then reboot from recovery
cobyman7035 said:
can i do all that and still keep all my apps and data? im thinking of going to LMy48l too
Click to expand...
Click to collapse
Have the same situation as you wherein I am unlocked and am rooted. Follow this guide for the respective LMY48I build and you should be fine with no data loss. Just remember to reroot with CF-Auto root afterwards as you will loose root.
http://forum.xda-developers.com/showpost.php?p=60697487&postcount=26
Just wanted to say that I used the Nexus Toolkit (http://www.wugfresh.com/nrt/) to easily flash the stock lmy48i upgrade, then re-root & re-flash my custom recovery. All while preserving my data and apps.
The process was super simple, and the toolkit program even downloads and verifies the stock images for you.
So the OFFICIAL 6.0.1 is already out and this is not the BETA version. It's for consumer release.
So how do you get to this eh?
NOTES: Flashtool can be used for both LB/UB. You won't lose DRM keys or unlock bootloader if you flash via flashtool.
1. Install Flashtool (get it here: http://www.flashtool.net/downloads.php).
2. There is a XperiFirm option there which would allow you to download official FTF files.
3. Navigate your way to Z3 Compact and grab the D5803 version US Variant (since this is configured for GLOBAL-LTE but i might still need to test bands). Or just grab anything you want there as long as it's version: 23.5.A.0.570
3. Flash using flashmode (hit the lightning icon there).
Now there's this "WIPE" Box, you have 2 options!
- Check User data and App logs and hit flash -- this will factory reset phone so you better have a backup!
- Leave them UNCHECKED if you want to retain your apps from your previous STOCK ROM. (might automatically uninstall incompatible apps in the process).
Once it asks for your device to be connected. Do as it says (power down, then hold the vol. down button as you plug the phone in).
-- this should start flashing.
4. After the process you may now boot the phone and there you have it!
-- Things below require unlocked BL --
If you want root, you can use fastboot and TWRP 3.X (I've tested the TWRP version 3.0.2 on the 6.0.1 beta before)
send this command on fastboot:
Code:
fastboot flash recovery <your twrp img here>
and hit enter. It must return 'OKAY'.
Unplug phone then boot into recovery and flash your SuperSU.zip
https://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
MINE!
Give a link to proper TWRP image please
tRippinthehead said:
Give a link to proper TWRP image please
Click to expand...
Click to collapse
If you have a locked BL, then root and install DualRecovery. There is an excellent thread here on XDA and you'll be on TWRP in no time. It also makes sure you'll have the drivers and flash tool and everything that you'll need for this already configured and ready to go.
If you have an unlocked BL, just go find TWRP and flash through fastboot.
Thanks OP!
P.S. I'm guessing for those with locked BLs, we can use PRFCreator and that FTF from Xperifirm to create a flashable, pre-rooted MM ROM...anyone tried? My Z3c is currently bricked (hopefully fixable) so I can't test at the moment.
Another DEV published a root method, both for the LB and UB:
http://forum.xda-developers.com/z3/general/wip-sony-android-6-0-mm-t3337357/page1
Keep in mind that that method was used for the BETA version of the rom, but yeah it's more likely that it would work with the consumer release. I'll update the OP once I relock my BL and successfully gain root with it.
The UB method there has the same effect as mine
I could not get root with the method, i would get boot img failure on flashing superSU in twrp with unlocked BL but to solve the issue i just flashed the advanced kernel for 6.0.1 and superSU flashed fine..not sure if anyone else is having this problem but this method did not work for me.
Do I keep root with locked bootloader with this method ?
Title of this topic is confusing, it seems that you need BL unlocked to get root.
hayatesan said:
Do I keep root with locked bootloader with this method ?
Title of this topic is confusing, it seems that you need BL unlocked to get root.
Click to expand...
Click to collapse
No you will lose root if you flash ftf on locked BL, you will need to root again using whichever method you used previously. If you flash an ftf file on ANY bootloader locked or unlocked it resets your phone to the contents of the ftf file.
Fictional Reality said:
No you will lose root if you flash ftf on locked BL, you will need to root again using whichever method you used previously. If you flash an ftf file on ANY bootloader locked or unlocked it resets your phone to the contents of the ftf file.
Click to expand...
Click to collapse
And which is the method to root this version with BL??
hv6478 said:
P.S. I'm guessing for those with locked BLs, we can use PRFCreator and that FTF from Xperifirm to create a flashable, pre-rooted MM ROM...anyone tried? My Z3c is currently bricked (hopefully fixable) so I can't test at the moment.
Click to expand...
Click to collapse
I'm giving it a try so I'll let you know.
EDIT: Admittedly I haven't got a clue how to use prfcreator but I tried and whilst it flashed there was no root or recovery.
2nd EDIT: XDR doesn't work on MM yet. I'll give TWRP a try.
TWRP 3.0.2 for Z3C https://dl.twrp.me/z3c/twrp-3.0.2-0-z3c.img.html
Buleste said:
I'm giving it a try so I'll let you know.
EDIT: Admittedly I haven't got a clue how to use prfcreator but I tried and whilst it flashed there was no root or recovery.
2nd EDIT: XDR doesn't work on MM yet. I'll give TWRP a try.
TWRP 3.0.2 for Z3C https://dl.twrp.me/z3c/twrp-3.0.2-0-z3c.img.html
Click to expand...
Click to collapse
Nice that sounds promising, at least it worked with the .zip that you created!
Which version of SuperSU are you using?
Thanks,
hv
hv6478 said:
Nice that sounds promising, at least it worked with the .zip that you created!
Which version of SuperSU are you using?
Thanks,
hv
Click to expand...
Click to collapse
I'm using BETA-SuperSU-v2.71-20160331103524.zip
However I was looking at the PRFCreator thread and it looks like if you add Recroot v2 as the SuperSU it should work. Not sure if it will give a recovery though.
EDIT: Okay. Didn't install the SuperSU binary properly but Kingroot could install the root though. Tried to remove it and replace with SuperSU and got a bootloop. However I have a cunning plan.
Xperia Z3 Compact - UB
I could not get TWRP recovery with the fastboot method.
I tried to install several "recoverys" but none are installed.
Help me please.
Buleste said:
I'm using BETA-SuperSU-v2.71-20160331103524.zip
However I was looking at the PRFCreator thread and it looks like if you add Recroot v2 as the SuperSU it should work. Not sure if it will give a recovery though.
EDIT: Okay. Didn't install the SuperSU binary properly but Kingroot could install the root though. Tried to remove it and replace with SuperSU and got a bootloop. However I have a cunning plan.
Click to expand...
Click to collapse
I love the sound of progress!
rvnlvrz said:
So the OFFICIAL 6.0.1 is already out and this is not the BETA version. It's for consumer release.
So how do you get to this eh?
NOTES: Flashtool can be used for both LB/UB. You won't lose DRM keys or unlock bootloader if you flash via flashtool.
1. Install Flashtool (get it here: http://www.flashtool.net/downloads.php).
2. There is a XperiFirm option there which would allow you to download official FTF files.
3. Navigate your way to Z3 Compact and grab the D5803 version US Variant (since this is configured for GLOBAL-LTE but i might still need to test bands). Or just grab anything you want there as long as it's version: 23.5.A.0.570
3. Flash using flashmode (hit the lightning icon there).
Now there's this "WIPE" Box, you have 2 options!
- Check User data and App logs and hit flash -- this will factory reset phone so you better have a backup!
- Leave them UNCHECKED if you want to retain your apps from your previous STOCK ROM. (might automatically uninstall incompatible apps in the process).
Once it asks for your device to be connected. Do as it says (power down, then hold the vol. down button as you plug the phone in).
-- this should start flashing.
4. After the process you may now boot the phone and there you have it!
-- Things below require unlocked BL --
If you want root, you can use fastboot and TWRP 3.X (I've tested the TWRP version 3.0.2 on the 6.0.1 beta before)
send this command on fastboot:
Code:
fastboot flash recovery <your twrp img here>
and hit enter. It must return 'OKAY'.
Unplug phone then boot into recovery and flash your SuperSU.zip
https://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
Click to expand...
Click to collapse
It doesn't work, I have trying out for a while, but fastboot doesn't flash anything
hv6478 said:
I love the sound of progress!
Click to expand...
Click to collapse
We have progress of sorts.
With prf creator add superSU and create the prerooted ROM.
In TWRP Wipe everything but SDcard and OTG
Install pre rooted ROM
Then Install RICDefieat.zip, byeselinux_flashable.zip, and BusyBox-v1.24.1-Stericson.zip
Power off the phone.
Open Flashtool
Load ftf of .570 and check the Exclude System box and flash the phone
Install TWRP using Z3C_MM_TWRP_Recovery_V2_By_Serajr
And that should be it.
Managed to get everything working bar the TWRP but I think that was my fault.
A download file of everything you need bar the ROM.
Buleste said:
We have progress of sorts.
With prf creator add superSU and create the prerooted ROM.
In TWRP Wipe everything but SDcard and OTG
Install pre rooted ROM
Then Install RICDefieat.zip, byeselinux_flashable.zip, and BusyBox-v1.24.1-Stericson.zip
Power off the phone.
Open Flashtool
Load ftf of .570 and check the Exclude System box and flash the phone
Install TWRP using Z3C_MM_TWRP_Recovery_V2_By_Serajr
And that should be it.
Managed to get everything working bar the TWRP but I think that was my fault.
A download file of everything you need bar the ROM.
Click to expand...
Click to collapse
Worked?
marlontravagli said:
Worked?
Click to expand...
Click to collapse
It seems to be working for me at the moment. Even TWRP.
Edit: TWRP is unstable and sometimes becomes unavailable . If that happens just find SGP621-RICDefeat.zip to enable R/W again and reinstall.
Buleste said:
We have progress of sorts.
With prf creator add superSU and create the prerooted ROM.
In TWRP Wipe everything but SDcard and OTG
Install pre rooted ROM
Then Install RICDefieat.zip, byeselinux_flashable.zip, and BusyBox-v1.24.1-Stericson.zip
Power off the phone.
Open Flashtool
Load ftf of .570 and check the Exclude System box and flash the phone
Install TWRP using Z3C_MM_TWRP_Recovery_V2_By_Serajr
And that should be it.
Managed to get everything working bar the TWRP but I think that was my fault.
A download file of everything you need bar the ROM.
Click to expand...
Click to collapse
ok...this sims to be right, thanks
superpipo said:
ok...this sims to be right, thanks
Click to expand...
Click to collapse
It seems that updating busybox to 1.24.1 stericson stops R/W permissions and the ability to access TWRP however it is easily fixed.