Database Develop

Couple questions after unlocking bootloader (XT1096)

Ok, here's the rundown - I have a VZW Moto X (XT1096). I previously ran mofo on it had flashed the 5.1 img files to it and so had 5.1 rooted, but with a locked bootloader. After learning that JCase had gotten sunshine to work on it I unlocked my boot loader. I then decided that because I was worried about having the a kind of mish-mash of systems on it, i.e., 5.0 bootloader (unlocked) with hacked and modded 5.1 system files flashed from mofo, that I wanted to start fresh. I then used the XT1096 flash to stock script and flashed back to 5.0 (there were a bunch of problems and bootloops and force closes, but I am happy to report I am now on a fully stock 5.0 with unlocked BL). Following being stock I have tried to take the OTA but have been unable to do so. When I try it OTA on my device it just sits at 0%. When I tried using MDM it gave me an error message that it failed to install the update - on the device it said getjar: unlocked.
So, now that I am on 5.0 with an unlocked bootloader I am not sure how to proceed with my priorities, Root, WiFi tethering and upgrading to 5.1. My questions are this:
(1) How can I upgrade to 5.1 or does my bootloader unlock preclude that?
(2) How best can I achieve root?
(3) Once I am rooted what do I need to do in order to enable wifi tethering?
Thank you so much!

Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot and flash the stock system.img and recovery.img before doing the update.
3. I don't have experience with Verizon network. I use T-Mobile on this Verizon device and I just enable WiFi Hotspot. In the APN settings, in the "APN type" field, I add the value "dun". And set everything to IPv4.

Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot to flash the stock system.img and recovery.img before doing the update.
Can't help you with tethering since I don't have experience with Verizon network.

eksasol said:
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot to flash the stock system.img and recovery.img before doing the update.
Can't help you with tethering since I don't have experience with Verizon network.
Click to expand...
Click to collapse
Thank you for the reply - got the update to take and have gotten the device rooted properly.
Now I just need to enable wifi tether - anyone know what is done in the Mofo images that allows it - can i do the same here?

I am interested in this question as well. I am in the exact same boat as the OP, except I am still on a Mofo 5.1 img that is giving me issues. I'd like to flash back to stock and take the OTA. But wifi tether will be a must.

Thanks to mikeoswego we have the tethering answer.
http://forum.xda-developers.com/showthread.php?p=62379151

eksasol said:
Okay I can't help with all your issues since I didn't get that problem. It seems like whatever you did to install your phone back to 5.0 it wasn't a clean install or you didn't do a clean data wipe to remove errors, which caused it to not able to receive OTA. I do not believe unlocking bootloader preclude you from receiving OTAs because it worked for me.
1. What you should try to do is download this stock 5.0 firmware package, run the bat file with the latest adb/fastboot, then boot into recovery after that and do a data/cache wipe just to make sure. Then boot in the phone and try to do the OTA again.
2. To get root, I use TWRP recovery to flash SuperSU. This is the standard way in fact.
Download SuperSU.zip and put it in the phone: http://download.chainfire.eu/supersu
Get the latest TWRP image here for the Moto X 2014: https://dl.twrp.me/victara/
Flash the recovery using the command: fastboot flash recovery twrp-2.x.x.x-victara.img
Boot into recovery and flash the SuperSu.zip.
Note that now you have made changes to the recovery and system partition, so in order to receive future OTA updates, you need to use fastboot to flash the stock system.img and recovery.img before doing the update.
Can't help you with tethering since I don't have experience with Verizon network.
Click to expand...
Click to collapse
I tried this but after I flash TWRP I can't boot to recovery. If I choose recovery from the bootloader it just turns off the phone (charging icon). If I send it adb reboot recovery I get error android "No Command."
Flashed it multiple times, tried mfastboot, no luck. Any ideas?
Edit: I feel dumb. I was using power button to try to select, it's volume up. Good to go.

GatorsUF said:
Thanks to mikeoswego we have the tethering answer.
http://forum.xda-developers.com/showthread.php?p=62379151
Click to expand...
Click to collapse
The other method (the one I used) was to install the Xtether xposed module for the 2013 Moto X - worked perfectly for me.

I feel like a complete noob for asking this in regards to my XT1096, but, how would I get rid of the unlocked bootloader warning message?

SargeStryker said:
I feel like a complete noob for asking this in regards to my XT1096, but, how would I get rid of the unlocked bootloader warning message?
Click to expand...
Click to collapse
Flashing this
http://forum.xda-developers.com/showthread.php?t=2871478

juliospinoza said:
Flashing this
http://forum.xda-developers.com/showthread.php?t=2871478
Click to expand...
Click to collapse
Thanks!

recovery will not stick on 6.0.1

I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks

jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse
Never trust a recovery installed by a tool kit. Grab the recovery img from the site and flash it manually.

all i have now is stock recovery. whats the best way to manually install twrp

go into fastboot and flash it. you have to be in your bootloader to flash via fastboot. you put the file in the same window as your fastboot program, then type.. fastboot flash recovery recoveryname.img, and that will flash twrp. if you type fastboot boot recovery recoveryname.img then itll only boot into recovery one time, thats what your toolkit did.

Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse

Don't use toolkits. I recommend yoiu follow @simms22's solution.
Sent from my Nexus 6 running cyosp using Tapatalk

when you have root, you can always use an app, like flashify, to flash twrp recovery. but you need to have root first.

arcane spade said:
Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
Click to expand...
Click to collapse
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp

jdpeck said:
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp
Click to expand...
Click to collapse
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.

This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.

scryan said:
This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.
Click to expand...
Click to collapse
well, thats how you should flash recovery. but its not the reason that we dont use toolkits. we dont use toolkits for several reasons.. 1. they mess up 2. doing it properly is just as fast if not faster 3. newbs think that toolkits are made for them to use. well, they are wrong. toolkits teach you absolutely nothing, which is the worst for beginners.

simms22 said:
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.
Click to expand...
Click to collapse
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help

jdpeck said:
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help
Click to expand...
Click to collapse
if you skipped the recovery.img, your recovery should have stayed.. oh, never mind, i just remembered a file that you need to remove after the first boot, or itll install the stock recovery after the first reboot. its called recovery-from-boot.bak. if you remove that on first boot, youll be fine

Stuck in recovery after 4.0.1 OTA

Hi,
I was running Oxygen 4.0.0 and a beta build of TWRP 3.0.3 which works with new encryption. I used the android update mechanics to get the 4.0.1 OTA. System rebooted to recovery, recovery threw an error (zip file corrputed) and since then I am not able to boot the system. Whatever I do I land in TWRP recovery.
Things I did so far:
- Tried installing the full 4.0.1 zip. Install worked without errors, device still boots to recovery.
- Tried to get stock recovery, since another post (https://forum.xda-developers.com/oneplus-3t/help/stuck-recovery-mode-t3532524) indicates stock recovery might fix the problem
--> stock recovery is not obtainable anymore. Seems deleted from all the download links I could find. Example is here: https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
- Wipe cache and dalvik cache in the hopes, the instruction to boot to recovery is there somewhere.
I did not do the unbrick tool, since I run linux and didnt want to fiddle with windows yet.
I did make a nandroid backup, so once my system boots again I should be fine.
Any Idea where to either get a mirror of stock recovery or how to fix this problem otherwise?

I had this same problem, and I solved downloading the unbrick tool and extracting the recovery from there. Here is the file
https://drive.google.com/file/d/0BwaafKaXbak3d1RFblFOWVd5eGs/view?usp=sharing

Also locking the bootloader worked for me. Booted into system then unlocked again.

Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.

mad-murdock said:
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
Click to expand...
Click to collapse
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.

mariospizza said:
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
Click to expand...
Click to collapse
Yeah, worked totally normal as it should.
My educated guess about this whole dilemma is, the system sets a flag to boot to recovery which TWRP doesn't clear and only stock recovery clears. Usually those flags should be in cache partition, but in this case isn't.
Tldr: don't use build in update mechanisms if you modified Rom and recovery.

[SOLVED] EMUI 9 + Magisk, but no fastboot and erecovery factory reset does nothing

Got official notification and have installed Pie (9.0.1.163) on my VTR-L09C432 P10.
Downloaded the Full OTA (9.0.1.163), extracted the RECOVERY_RAMDIS.img, patched with Magisk 7.1.1 and flashed using fastboot to the recovery_ramdisk partition. When rebooted with Vol+ have root. Played around with Pie and have decided to revert back to Oreo.
HiSuite (v9.0.3.300_OVE) did offer me rollback to 8.0.0.365. So I have decided to pursue this option. The firmware download went OK (100%), the programing went OK (100%) and the phone rebooted, as said the popup, but ... it was still on Pie as before.
Decided to try to "upgrade" via eRecovery. It wasn't able to determine and download any package. So I tried factory reset. No error, but it seems to do nothing. The phone rebooted and the situation is: Pie works, Magisk reports root 18.1 and root apps work.
From this moment I am unable to enter fastboot. The phone just boots normally with Magisk root. As I have just written eRecovery is present but is useless (can't download an upgrade package and can'r factory reset).
Advice?
Should I try writing from a term using dd the extracted RECOVERY_RANDISK.img and ERECOVERY_RAMDISK.img ? This way will loose root (Magisk) but don't know if it "resolve" access to fastboot and "fix" eRecovery.
EDIT:
No reply so decided to go ahead with what I thought was happening. I didn't know that a firmware upgrade (or downgrade) needs recovery to complete. I thought erecovery was the key.
So when I used HiSuite to rollback to Oreo what happened was it downloaded the Oreo firmware, uploaded it to the phone, prepared for a firmware flash and did a reboot. The firmware downgrade was supposed to happen in recovery but since the recovery code was changed by Magisk the flashing was never happening.
The same when from erecovery I tried to do a factory reset. Seems that erecovery just prepares things but recovery code does the actual reset. And once again I was observing that nothing was happening. The phone was simply root booting exactly as the Magisk code is supposed to do.
So I just flashed (from a term) the original recovery_ramdisk.img. After reboot got the factory reset welcome screen.
Of course got back fastboot.
Hope this can be of of help someone is a similar situation

Dude can you please guide us how to actually use DD command.
edit: I did this a different way. much easier & safer for less experienced users.
1. Open magisk manager. At the bottom of the first screen there is a button "UNINSTALL". Press uninstall & click "restore images".
2. Magisk will remove itself and restore your original boot image. Worked for me

Moto G7+ Flashing Lineage fails -> Touch doesn't work anymore - Brick?

Hello guys!
Yesterday I tried to flash the newest Lineage-built to my new G7+ (XT1965-3, bought in Germany via Amazon), but something went wrong and now I'm afraid, I bricked my phone.
It's not my first flash of Lineage, as I did this in the past already on some older Phones (SII, SIII, S5), but it's the first time, that I have a major issue.
So I followed all the steps on the Lineage-Wiki (on Win10).
After flashing the recovery (the lineage-recovery, not TWRP) I wasn't able to enter the recovery-mode, so the phone booted to StockRom. And probably this was the problem: As it didn't react to VolumeDown+Power, I reflashed the recovery a second time. After that the touch-screen is not working any more.
I am able to enter the recovery-mode and I can boot to Stock-Rom, but in both modes the phone does not react to touch, so I can only use the Volume- and Power-Buttons.
Probably I made more mistakes after that: I thought, that a factory-reset would help, but It didn't. I also relocked the bootloader, but as I saw, that it also did not bring any solution, I unlocked it a second time.
Conclusion: I have a brand new phone, with lineage-recovery, an unlocked bootloader but without touch working.
I also tried to flash Lineage, but the sideload got stuck at 47%. So Lineage is not installed and it boots into Stock, where I can not get any further without touch.
Has anyone any idea, what could be the issue and how I can fix it? I would like to start from scratch, but I don't know, what is the exact problem and if i can for example return to stock recovery.
Thank you!
---- EDIT ----
If it helps: I am able to boot TWRP via "fastboot boot twrp-xxx.img". And in TWRP the touch works!
I could flash lineage directly via TWRP from external sd-card, but i am afraid that after that I won't be able to return if something goes wron.

probably your best bet is to go right back to stock using the LMSA tool and starting fresh. I've seen others encounter similar issues on different devices and always the cleaneast solution was just to role back everything and start over.

Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.

joglxv said:
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
Click to expand...
Click to collapse
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.

digitaljeff said:
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
Click to expand...
Click to collapse
I'm having a similar problem. At first touch was fubar but I was able to return to stock using LMSA and now touch works. I can load TWRP with fastboot and even install a custom ROM and TWRP, but installing any custom ROM results in a boot loop during the finding and installing updates part of the phone setup during first boot. I'm tried Evolution X which I was running previously(for about a month, and then a boot loop started yesterday), PixelOS 10, and AncientOS, but all result in the boot loop on first boot after connecting to wifi.

Fixed
I fixed this somehow by manually flashing the latest stock firmware to slot a, and then extracting the evolution x Rom and manually extracting the IMG files inside and manually fastboot flashing those to slot b. I then set b as the active slot and booted up, patched the boot image with magisk, flashed that, and everything works. Not sure why twrp wouldn't do the trick.

Finally had the time to install Lineage. Now everything works.
I followed the instructions someone posted in the [ROM][OFFICIAL] LineageOS 17.1 [nightlies]-thread and the instructions of the lineage-wiki:
1. fastboot boot TWRP
2. sideload the copy-partitions.zip from lineage-wiki
3. factory reset via TWRP (wipe cache, dalvik and data)
4. sideload lineage
5. reboot bootloader
6. fastboot boot TWRP
7. sideload magisk
8. reboot system
Had a little bootloop the first time rebooting the system, but that was because I forgot to wipe data-partition in step 3. Wiping data and rebooting did it for me.
So I have a working Lineage17.1 with root via Magisk.
Thank you for the help!

I had exactly the same problem like you had. Bought a brand new moto g7 plus and after recovery flash, Touchscreen was not working anymore. I could manage to go back to the bootloader, sideloaded TWRP, but side loading lineage worked for me then. It seemed to be stuck on 47 percent, but this seems to be a normal issue, the file was there and after installing, touchscreen worked normally.