i have an unlocked bootloader tf700t waiting for spare cable to install twrp
can someone please answer these questions
will i brick my tablet if i update?
do i update through manual or OTA?
should i install twrp first?
will i lose unlock?
if you could tell me then it would be great. the last thing i want is a brick
hasrussian said:
i have an unlocked bootloader tf700t waiting for spare cable to install twrp
can someone please answer these questions
will i brick my tablet if i update?
do i update through manual or OTA?
should i install twrp first?
will i lose unlock?
if you could tell me then it would be great. the last thing i want is a brick
Click to expand...
Click to collapse
If you do everything correctly, you won't brick your tablet.
Since your bootloader is unlocked, you won't get the OTA update, so you'd have to install it manually. AFAIK you need root to manually install an OTA update (by copying the dlkpkgfile to /cache and creating the corresponding command file), so it's easier to install TWRP first.
The bootloader stays unlocked when you do all this.
thanks
_that said:
If you do everything correctly, you won't brick your tablet.
Since your bootloader is unlocked, you won't get the OTA update, so you'd have to install it manually. AFAIK you need root to manually install an OTA update (by copying the dlkpkgfile to /cache and creating the corresponding command file), so it's easier to install TWRP first.
The bootloader stays unlocked when you do all this.
Click to expand...
Click to collapse
cable arrived and i now have twrp installed
thanks anyway
New to me tablet and I'm new to rooting/etc.
Factory tablet on 4.1.1, build 10.4.2.20-20121228
I downloaded and ran the Asus unlock utility, then ran motochopper to root. I then loaded TWRP 2.2.2.0 (I realized the mistake later). Made stock backup using twrp ok. Wiped cache/dalvik/etc and tried to recover to CM.10.0.0. Boots to cyanogenmod logo and just sits and spins. I can reboot back into recovery and restore from backup ok.
I realize now that I've loaded an early version of twrp, would that affect the cm bootup? If so, how do I upgrade twrp? Or should I try CM10.1 exp using twrp 2.2.2.0?
kbud123 said:
New to me tablet and I'm new to rooting/etc.
Factory tablet on 4.1.1, build 10.4.2.20-20121228
I downloaded and ran the Asus unlock utility, then ran motochopper to root. I then loaded TWRP 2.2.2.0 (I realized the mistake later). Made stock backup using twrp ok. Wiped cache/dalvik/etc and tried to recover to CM.10.0.0. Boots to cyanogenmod logo and just sits and spins. I can reboot back into recovery and restore from backup ok.
I realize now that I've loaded an early version of twrp, would that affect the cm bootup? If so, how do I upgrade twrp? Or should I try CM10.1 exp using twrp 2.2.2.0?
Click to expand...
Click to collapse
I can see you are on the 4.1 BL. I would suggest upgrading to the 4.2 bootloader and the using the most recent versions of TWRP and CM. You would do that by flashing the stock 4.2 Asus firmware, then the latest TWRP from their website with -42 and then the latest cyanogen mod ROM which is compatible with that bootloader.
cmendonc2 said:
I can see you are on the 4.1 BL. I would suggest upgrading to the 4.2 bootloader and the using the most recent versions of TWRP and CM. You would do that by flashing the stock 4.2 Asus firmware, then the latest TWRP from their website with -42 and then the latest cyanogen mod ROM which is compatible with that bootloader.
Click to expand...
Click to collapse
First off, thank you for the assistance. Here are the steps I believe I should take. Please correct me if I'm wrong.
1. Download and install latest 4.2 bootloader from Asus= US_epad-10.6.1.27.5
2. Would I need to download and install the unlocker from Asus? = Unlock_v8 for 4.2JB
3. Download and install TWRP for 4.2= TWRP 2.6.3.0-tf300t-4.2 blob
4. Then I should be able to run any of the CM 10.0.0 and up on the 4.2 bootloader, right?
kbud123 said:
First off, thank you for the assistance. Here are the steps I believe I should take. Please correct me if I'm wrong.
1. Download and install latest 4.2 bootloader from Asus= US_epad-10.6.1.27.5
2. Would I need to download and install the unlocker from Asus? = Unlock_v8 for 4.2JB
3. Download and install TWRP for 4.2= TWRP 2.6.3.0-tf300t-4.2 blob
4. Then I should be able to run any of the CM 10.0.0 and up on the 4.2 bootloader, right?
Click to expand...
Click to collapse
Lots of ppl are having problems with the V8 unlocker. Since you are already on 4.1, you could just unlock now with the V7 tool.
1. Unlock with V7 tool (http://forum.xda-developers.com/showthread.php?t=1949758)
2. Flash Latest Asus Stock (http://forum.xda-developers.com/showthread.php?t=1949758)
3. Download and install TWRP for 4.2= TWRP 2.6.3.0-tf300t-4.2 blob (http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.6.3.0-tf300t-4.2.blob)
4. Flash Latest CM (http://forum.xda-developers.com/showthread.php?t=2413878)
Personally, I would also make NvFlash Backups so you can restore your tablet just in case anything bad happens. Link is in my sig
cmendonc2 said:
Lots of ppl are having problems with the V8 unlocker. Since you are already on 4.1, you could just unlock now with the V7 tool.
1. Unlock with V7 tool (http://forum.xda-developers.com/showthread.php?t=1949758) Why would I use this now? Shouldn't I already be unlocked?
2. Flash Latest Asus Stock (http://forum.xda-developers.com/showthread.php?t=1949758)Will this put a locked or unlocked version on the tablet?
3. Download and install TWRP for 4.2= TWRP 2.6.3.0-tf300t-4.2 blob (http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.6.3.0-tf300t-4.2.blob)
4. Flash Latest CM (http://forum.xda-developers.com/showthread.php?t=2413878)
Personally, I would also make NvFlash Backups so you can restore your tablet just in case anything bad happens. Link is in my sig From what I'm reading, I can only do this after updating to 10.6.?.? So I would have to update to the latest Asus stock, then run this procedure.
Thanks again, and I appreciate your patience.
Click to expand...
Click to collapse
Ok, been reading until my eyes are bleeding.
From what I've read, Motochopper doesn't work for 10.6.1.27.x versions, so I would have to load 10.6.1.15.3. I should be able to download it and unzip it the first time on my pc. Then transfer it to the root directory of the tablet and run TWRP to install the .zip file. This would overwrite everything and bring it up to 4.2. I would then run the unlocker_v8 and install twrp for 4.2 using adb. If all that works, I should be rooted and unlocked and allowed to install CM 10 and above.
Please, anyone, check me on this. And thanks for the help.
kbud123 said:
Ok, been reading until my eyes are bleeding.
From what I've read, Motochopper doesn't work for 10.6.1.27.x versions, so I would have to load 10.6.1.15.3. I should be able to download it and unzip it the first time on my pc. Then transfer it to the root directory of the tablet and run TWRP to install the .zip file. This would overwrite everything and bring it up to 4.2. I would then run the unlocker_v8 and install twrp for 4.2 using adb. If all that works, I should be rooted and unlocked and allowed to install CM 10 and above.
Please, anyone, check me on this. And thanks for the help.
Click to expand...
Click to collapse
Oh sorry, I thought you meant that it had failed to unlock and flash.
Flashing a stock ROM will not relock your bootloader. Asus doesn't want people relocking their bootloader .
I'm not sure why you are using motochopper if you are going to install a custom ROM anyways. Almost all custom ROMs have the SU binaries in them.
Once you have unlocked your tablet, you will never need to run another unlocker, so dont worry about v8. The NvFlash backups need you to be on the 10.6.x.x bootloader, so you would flash the stock ROM then do the nvflash procedure.
cmendonc2 said:
Oh sorry, I thought you meant that it had failed to unlock and flash.
Flashing a stock ROM will not relock your bootloader. Asus doesn't want people relocking their bootloader .
I'm not sure why you are using motochopper if you are going to install a custom ROM anyways. Almost all custom ROMs have the SU binaries in them.
Once you have unlocked your tablet, you will never need to run another unlocker, so dont worry about v8. The NvFlash backups need you to be on the 10.6.x.x bootloader, so you would flash the stock ROM then do the nvflash procedure.
Click to expand...
Click to collapse
Just so I'm clear, I should be able to flash the stock rom w/ the TWRP I have now, using the install command for the zip file, right?
kbud123 said:
Just so I'm clear, I should be able to flash the stock rom w/ the TWRP I have now, using the install command for the zip file, right?
Click to expand...
Click to collapse
I'm not sure if you can flash the stock from the TWRP, to be safe I'd fastboot it from a computer. Once you flash the stock, it will upgrade the bootloader and erase TWRP. You would use the install command.
Success so far! I got it updated to 4.2.1 /10.6.1.27.5 using http://forum.xda-developers.com/showpost.php?p=35294881&postcount=1.
Moto G4 Plus US Variant XT1644
Build# MPJ24.139-64 Android 6.0.1
Stock Unmodified TWRP Backup
Stock Recovery.img & Logo.bin
Description:
I could not find ANY stock images for the US XT1644 variant so I made my own for others that have modified their system partition and wish to restore to a factory state and take the 7.0 update. Backup created on a factory reset unmodified stock build (not previously rooted/xposed/modified in any way) via fastboot booting TWRP w/system write disabled. Stock recovery and logo extracted via DD from stock rooted rom after TWRP backup was made. I pulled the recovery and logo images as these are the most commonly modified partitions (other than the system). This backup will work if you stayed on 6.0.1 and rooted/exposed/changed boot logo/etc. If you played with the 7.0 updates made for other variants, I honestly don't know if this will work for you to take the OTA as the bootloader/modem were likely modified - Test and let us know.
Directions:
-Have ADB working on your PC (google it, not getting into that here)
-Download TWRP backup here: https://mega.nz/#F!vBgU3QJB!R5J5RgZkvUiWHwmIfN6BkA
-Move backup to your proper TWRP backup location on your sd or external sd
-Restore backup via TWRP and reboot
-Download stock recovery & logo images here: https://mega.nz/#F!eBpB3Z5C!J6hoLKdfcObSLavWCsLnyw
-Power off device/plug into pc/hold volume down for 5 seconds/press and hold power & volume down until fastboot appears
-Move files to adb location (Windows) or open terminal where you downloaded the files (Linux) on your pc
-Verify connection
Code:
fastboot devices
-Restore stock recovery:
Code:
fastboot flash recovery recovery.img
-Restore stock logo (if you changed it previously to get rid of warning):
Code:
fastboot flash logo logo.bin
-Reboot and enjoy stock 6.0.1 and be able to take OTA
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Click to expand...
Click to collapse
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Sent from my XT1575 using Tapatalk
annoyingduck said:
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Click to expand...
Click to collapse
I Will flash stock xt1644 firmware 64, then i restore your backup
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
pupamonkey said:
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
Click to expand...
Click to collapse
It's not available, we're still waiting for it, that's why we flashing stock firmware again
Thanks for doing this! It's essentially what I did to get the marshmallow update (restore stock system & boot via TWRP, then recovery & logo via fastboot).
Please let us know when you see moto/Lenovo push out the nougat update via OTA!
Sent from my Moto G4 Plus using Tapatalk
you are the champ!! i have exact same model but i am yet to update to 64 release as i just got the phone today. Just doing some research before i grease my hands! thanks man!
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
bmeek said:
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
Click to expand...
Click to collapse
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
where to check?
i have the us variant from best buy as well , but i twicked it a lot .
How can i know when a nougat release is available? where can i check .
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
Click to expand...
Click to collapse
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Hymizzle said:
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Click to expand...
Click to collapse
If you flash a XT1625-XT1644 firmware and you use it "normally" on a XT1644, at some point you will have ghost touch even with low brightness, but...
For upgrading, I'll recommend flashing XT1625-XT1644, (cause there's no
...139-64 XT1644 firmware, just a firmware for both)
Flash it via fastboot, boot it up, flash TWRP recovery, wipe the full system with it, download the TWRP backup that was posted here, restore it, then via fastboot flash the stock recovery (for removing TWRP) and stock logo, then you will have MPJ24.139-64 with no problems, just waiting for nougat OTA for retus version.
Here's the link for retus firmwares: https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
TheDude1998 said:
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
Click to expand...
Click to collapse
Yeah I wouldn't think so, but thanks for letting us know.
Sent from my XT1575 using Tapatalk
getting the Nougat OTA
annoyingduck said:
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
Click to expand...
Click to collapse
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Click to expand...
Click to collapse
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
dedik46 said:
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
Click to expand...
Click to collapse
Yes your bootloader will still be unlocked unless you specifically enter the oem lock command. Read the tutorials, they all explain how to keep your bootloader unlocked.
Sent from my XT1575 using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
vishnureddy17 said:
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
Click to expand...
Click to collapse
Which of these 5 download? .
I've got my FRD-L14 (64GB US honor 8) running stable with B360 firmware (released 02-13-17) bootloader unlocked, SU flashed via TWRP.
I wanted to try the latest B385 OTA firmware flash so I used fastboot to flash my current stock B360 System.img, boot.img, and recovery.img to be sure I am running all stock boot/system files before flashing the B360 OTA.
I rebooted from fastboot successfully and continued with the OTA interface to install latest system update, it rebooted into Huawei recovery interface, verifying, installing, and then fails to verify and install.
Do I really have to lock the bootloader and wipe the entire phone in order to install latest OTA and then re-unlock bootloader, reflash twrp, and restore data ?
Thanks !
Well, that wasn't hard.
I used the "download latest full package" in the top-right menu of the OTA updates screen. This successfully installed B385 OTA update package for me without failure, while bootloader unlocked. Imagine that. I hope this helps someone else! Now, to figure out how to use magisk rather than supersu....
[remove, accidental doublepost]
I have the FRD-L04 32GB US model and im wondering why I havent had the update yet
I did revert to stock boot loader and unrooted im on 360 at the moment but no updates.
crowruin said:
I have the FRD-L04 32GB US model and im wondering why I havent had the update yet
I did revert to stock boot loader and unrooted im on 360 at the moment but no updates.
Click to expand...
Click to collapse
I just got the new update
mine26135 said:
I just got the new update
Click to expand...
Click to collapse
same here hahaha updating now.
I have the original Android 8.0 system and software version 2.33.401.19. Two days ago, my HTC announced that there is a new update to android 9.0. It downloads it and tries to install it. After reboot, TWRP starts and I choose to restart the system. Nothing is updated, and after a while I see a message that the update file is damaged.
A few weeks ago I unlocked the bootloader, ripped the phone and installed TWRP and MagiskManager. I suspect that the unlocked bootloader causes these problems. What should I do to install this update?
Szturwal said:
I have the original Android 8.0 system and software version 2.33.401.19. Two days ago, my HTC announced that there is a new update to android 9.0. It downloads it and tries to install it. After reboot, TWRP starts and I choose to restart the system. Nothing is updated, and after a while I see a message that the update file is damaged.
A few weeks ago I unlocked the bootloader, ripped the phone and installed TWRP and MagiskManager. I suspect that the unlocked bootloader causes these problems. What should I do to install this update?
Click to expand...
Click to collapse
not the unlocked boot loader, it's because you have twrp installed. you need stock recovery(and what ever you do don't relock your bootloader)you can get back to stock by flashing the oreo ruu, then you'll recieve the ota and it will install.you need the ruu for your phone.that's it.
this will wipe your internal, so if you have something on there you want to keep, back it up to your pc, then you can restore, also, you'll need to reinstall twrp and magisk after you install the ota.
Thanks for answer. I'm going to do this ....
Hi,
Is there a way I can just flash the stock recovery and try to OTA? Really don't want to backup 80GB and restore back.