Database Develop

[Q] XT1092 in bootloop after lollipop update

So this is a bit of a comedy of errors on my part...
I took the OTA update to lollipop and (foolishly) followed the same method as on KK to get root, putting myself in a bootloop. I got myself out of it by clearing the userdata and the cache.
I went about sorting everything and achieved root using the chainfire method, that was fine and I then went about reinstalling the xposed modules I had before. Foolishly, I didn't double check the status of xposed on Lollipop and consequently put myself back in a bootloop (idiot). I redid what had worked earlier, clearing the userdata and the cache to no avail.
Obviously, the problem was not the same as before and I needed to disable xposed, but in clearing the userdata I not only removed the xposed_disable.zip file to do this and also turned off adb so I can't push it.
The bootloader is fine and I can use fastboot, but can't push anything across. I hadn't replaced the recovery but can boot into twrp. However, I cannot flash it because I cannot push it over using adb.
I can't work out exactly how far I need to go back/what exactly I need to flash in order to put this all back together again.
I would be very grateful for any help that people can give on this.

Oh man.... This post made me giggle.
Right first of all what device do you have?
Anyway to connect a flash drive to the USB or a Micro SD and flash a new ROM in recovery?
Sent From N5

All you need is ability to enter fastboot. Using Multitool or manual fastboot flash commands, you should be able to go back to stock KK. From there on you can flash stock L. Root it.
Do not have access to Multitool runme.cmd file at the moment to confirm that all you need is ability to issue fastboot command. adb is not needed. But am almost certain that this is the case.

LiamAtkins90 said:
Oh man.... This post made me giggle.
Right first of all what device do you have?
Anyway to connect a flash drive to the USB or a Micro SD and flash a new ROM in recovery?
Sent From N5
Click to expand...
Click to collapse
It's a 2014 Moto X, the XT1092 (bought straight from Motorola - I think that makes it the pure edition).
prasad.adam said:
All you need is ability to enter fastboot. Using Multitool or manual fastboot flash commands, you should be able to go back to stock KK. From there on you can flash stock L. Root it.
Do not have access to Multitool runme.cmd file at the moment to confirm that all you need is ability to issue fastboot command. adb is not needed. But am almost certain that this is the case.
Click to expand...
Click to collapse
I have tried the Multitool (as in here) but it would always throw me errors and never showed up anything on the fastboot console. I expect I probably need to get the stock image from Motorola (I've requested access to this which is the top option from here) and issue the fastboot commands by hand which seems to work. I'm mostly just unsure about what exact commands I need to give to make sure I don't forget to flash a particular part. I haven't gone this far on other phones and have normally worked from CWM but I can't even flash that/TWRP at the moment.
Thanks for your help guys!

HamRack said:
It's a 2014 Moto X, the XT1092 (bought straight from Motorola - I think that makes it the pure edition).
I have tried the Multitool (as in here) but it would always throw me errors and never showed up anything on the fastboot console. I expect I probably need to get the stock image from Motorola (I've requested access to this which is the top option from here) and issue the fastboot commands by hand which seems to work. I'm mostly just unsure about what exact commands I need to give to make sure I don't forget to flash a particular part. I haven't gone this far on other phones and have normally worked from CWM but I can't even flash that/TWRP at the moment.
Thanks for your help guys!
Click to expand...
Click to collapse
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.

purejoy said:
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
Click to expand...
Click to collapse
Would it need to be an SD card or just a usb stick formatted correctly?
This sounds the best idea yet, now just to track down a USB OTG cable...

HamRack said:
Would it need to be an SD card or just a usb stick formatted correctly?
This sounds the best idea yet, now just to track down a USB OTG cable...
Click to expand...
Click to collapse
SD card is OK. As USB disk,haven't give a try.

Ok, cheers. I'll get a usb otg cable and give it a go.

HamRack said:
Ok, cheers. I'll get a usb otg cable and give it a go.
Click to expand...
Click to collapse
Normally Xposed installer would put a copy of Xposed-Disabler-recovery.zip under directory /sdcard after being installed. You should check the directory first, moreover, that file was released for those KK users. I have no idea whether it would take effect on lollipop or destroy your system. Take your own risk.

purejoy said:
Normally Xposed installer would put a copy of Xposed-Disabler-recovery.zip under directory /sdcard after being installed.
Click to expand...
Click to collapse
So I found, but because my first reaction to the second bootloop was to erase userdata (as had fixed the earlier one) I lost that.

purejoy said:
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
Click to expand...
Click to collapse
Hi,
Tracked down a usbotg cable and have booted into TWRP. When I plug in the sd card using the cable, I don't find anything to mount the sd card in the advanced menu of TWRP, but I do find a 'mount' option on the main menu
(as you can see here). Under there is a tick box for 'USB-OTG' which I have ticked, but I can't find where it actually is in the filemanager/when I select 'install'...
Any suggestions?

Realised what I had done, managed to flash the xposed_disabler zip, but it didn't work.
However, I was pointed in the direction of this where I downgraded to KK 4.4.4. That seems to have done the trick at getting me back to a working device. Out of curiosity, does anyone know a reason why I shouldn't get have the Lollipop OTA come through again in due course? When I check for updates it says I am up to date - is the only way I will get L by way of sideloading?
Finally, thanks for all your help, you've been very patient with my dangerous level of knowledge - enough to do plenty of damage but not enough to fix it!

HamRack said:
Hi,
Tracked down a usbotg cable and have booted into TWRP. When I plug in the sd card using the cable, I don't find anything to mount the sd card in the advanced menu of TWRP, but I do find a 'mount' option on the main menu
(as you can see here). Under there is a tick box for 'USB-OTG' which I have ticked, but I can't find where it actually is in the filemanager/when I select 'install'...
Any suggestions?
Click to expand...
Click to collapse
You were expected to use the latest TWRP which is 2.8+,at least 2.7. Anyway,that's not important.
Did you get an error after issuing "fastboot flash motoboot motoboot.IMG"?
Cuz you succeeded in updating, the OTA has upgraded your bootloader. Although you have downgraded your system, the BL can't be,hence when you try to accept another OTA, there will be a verification error.
Now You need flash a custom OTA pack via a 3rd party recovery. Some verifications must be removed from the official OTA zip.
You can also wait for someone to backup and share the images of the new system.
---------- Post added at 01:29 AM ---------- Previous post was at 01:07 AM ----------
HamRack said:
Realised what I had done, managed to flash the xposed_disabler zip, but it didn't work.
However, I was pointed in the direction of this where I downgraded to KK 4.4.4. That seems to have done the trick at getting me back to a working device. Out of curiosity, does anyone know a reason why I shouldn't get have the Lollipop OTA come through again in due course? When I check for updates it says I am up to date - is the only way I will get L by way of sideloading?
Finally, thanks for all your help, you've been very patient with my dangerous level of knowledge - enough to do plenty of damage but not enough to fix it!
Click to expand...
Click to collapse
I think you can have a try to download the .19 OTA zip and put it under /sdcard, then reboot into stock recovery to apply update from SD card or adb sideload. If there's no errors while verifying, you would get lollipop again.

Sorry for not reading all the reply's in this thread before posting (i'm in a bit of a rush)
I got a bootloop while applying the OTA on a brand new XT 1092 right after taking out of the box. After some digging around the forums (you can tell i'm new by the post count) i managed to get an OTA zip for my DE version and pushed it via ADB using stock recovery, with a few hickups:
- had to manually install the driver in windows
- first time the install via ADB push failed with some assert failure on something related to moto.odex
- the second try went ok and got the bootloop sorted.
So definitely give ADB a shot
Good luck!

First, try to recover as much as of your data stored on the device .
Then reflash the old ROM. You'll need a specific program for that - and a PC Surely! ☺
After that to get easier Back-Ups - i recommend unblocking the bootloader.
All the best☻.

purejoy said:
You were expected to use the latest TWRP which is 2.8+,at least 2.7. Anyway,that's not important.
Click to expand...
Click to collapse
I used TWRP 2.8.1.0, I downloaded it that day. Not sure what else it could have been...
Did you get an error after issuing "fastboot flash motoboot motoboot.IMG"?
Click to expand...
Click to collapse
Not sure when I was supposed to do that, couldn't see that in your directions...? Not a really a problem either way as its now sorted.
Cuz you succeeded in updating, the OTA has upgraded your bootloader. Although you have downgraded your system, the BL can't be,hence when you try to accept another OTA, there will be a verification error.
Now You need flash a custom OTA pack via a 3rd party recovery. Some verifications must be removed from the official OTA zip.
You can also wait for someone to backup and share the images of the new system.
I think you can have a try to download the .19 OTA zip and put it under /sdcard, then reboot into stock recovery to apply update from SD card or adb sideload. If there's no errors while verifying, you would get lollipop again.
Click to expand...
Click to collapse
Ok, thanks for the info. Any idea how to remove those verifications? Would this do the required thing?
Also, what exactly do you mean by the .19 OTA zip? You mean the OTA zip with the new bootloader in with it? If it has an error while trying this, would it give problems or just stop and return as before?
Thanks

Sorry, i have stayed up too late last night. You know there is time difference.
i dunno the differences between GB version and EU version, since you have a system of EU, maybe you should refer to this thread http://forum.xda-developers.com/moto-x-2014/general/ota-zip-moto-x-2014-xt1092-5-0-t2970818
Hmm,there is a better choice. Seems that moto has released the stock 5.0 firmware for GB xt1092. http://forum.xda-developers.com/showpost.php?p=57591807&postcount=36
Download it and make a full recovery.
BTW: Please backup your data first.

purejoy said:
Sorry, i have stayed up too late last night. You know there is time difference.
i dunno the differences between GB version and EU version, since you have a system of EU, maybe you should refer to this thread http://forum.xda-developers.com/moto-x-2014/general/ota-zip-moto-x-2014-xt1092-5-0-t2970818
Hmm,there is a better choice. Seems that moto has released the stock 5.0 firmware for GB xt1092. http://forum.xda-developers.com/showpost.php?p=57591807&postcount=36
Download it and make a full recovery.
BTW: Please backup your data first.
Click to expand...
Click to collapse
I'm not sure of the differences either...
So I'm wanting to make sure I do this correctly this time. I know a couple of ways of backing up but after all the faff recently I want to have an ironclad backup before I piss around with anything else (foolish me for not doing so before). Can you clarify the best way to back up my device and how I would do that? I have a feeling I haven't been doing it correctly/the most ideal way before and it would be good to know.
Also, how would I go about putting that backup you've pointed too (thank you for finding that, I don't think I'd been searching for quite the right thing) on to my device? Would I go through a similar series of steps to how I recovered my phone before (ie here)?
I'm going away for xmas/NY and will probably do this when I get back so I don't risk borking my phone when I need it most. Nonetheless, it would be good to have things ready to roll when I get back.
Thanks for your help, you've been great.

It depends on what you plan to backup and i don't konw what app your are using. If you use Google service, Contacts and some app data are normally synced to Google Cloud Servers. You can get them back in lollipop 5.0 via your Google account. As your pictures and videos,you can also directly copy them on your PC. What you need to backup are private app data and private messages. You can use some 3rd party backup apps like TitaniumBakcup to solve this. If there are not so much user data, you can backup like this.
You can also backup and restore your userdata via TWRP. If you get so many data, you can try this.
As the full stock recovery,you can restore your phone via fastboot utility or RSD lite.
1.Download and Unzip the image.
2.Put your phone in AP Fastboot Mode.
3. $ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot -w (Erase userdata. Optional,maybe unnecessary)
$ fastboot reboot
I would advise you to put off erasing data. If you get any issues while rebooting into new system, then you can erase your data.
Hope these help. Good Luck!

Great, thanks for the tip.
I tend to have minimal important data on my phone that isn't covered by either google or evolvesms/whatsapp. Nonetheless, thanks for the tips. I've been using titanium for a long while and have that backed up to dropbox too.
I tried flashing TWRP after I fixed the clusterbadger that was the last few days, but had no luck. I still don't seem to be able to push the image over using adb nor use adb to issue commands while booted into TWRP through fastboot. Have you experienced that? I guess worst case is that I copy the zip to an sdcard and flash it from usbotg by issuing commands in the TWRP shell they give you...?
Thanks for the tip on the userdata too.

Deleted my OS

ad

Ducky10100 said:
Hello guys. I've got a big problem. I rooted my Nexus 6 and installed TeamWin Recovery, but something wasn't installed correctly so I went to factory reset my phone from TeamWin recovery and completely deleted EVERYTHING, including my OS. Now I cannot do anything, my phone just stays at the Google logo. Just to clear things up:
My phone isn't rooted
Bootloader isn't unlocked
I have no OS.
I need help on how to flash android 5.0 back on my Nexus (Yes I've tried using Toolkit, but since my phone doesn't boot it's no use to me). Help would be much appreciated.
Click to expand...
Click to collapse
I dont mean to sound rude, really, but so what? you can download and transfer a ROM to your twrp recovery via regular file transfer, adb sideload, or adb push. so download what you need, choose a method, then transfer it to your phone. you dont have other options, besides for flashing a factory image.

Why did you install a custom recovery if you haven't unlocked your phone?
It seems to me you should start by downloading the appropriate factory image from Google. And flash everything (with the exception of boot loader) from inside your boot loader. Press and hold the power button while it's on, this will set a reboot. While the screen is black, press and hold power and volume down. This will get into boot loader.
Let us know if you need assistance on how to flash the factory images.

brymaster5000 said:
Why did you install a custom recovery if you haven't unlocked your phone?
It seems to me you should start by downloading the appropriate factory image from Google. And flash everything (with the exception of boot loader) from inside your boot loader. Press and hold the power button while it's on, this will set a reboot. While the screen is black, press and hold power and volume down. This will get into boot loader.
Let us know if you need assistance on how to flash the factory images.
Click to expand...
Click to collapse
I had my phone rooted and unlocked, but I reset everything and that's when it happened.
simms22 said:
I dont mean to sound rude, really, but so what? you can download and transfer a ROM to your twrp recovery via regular file transfer, adb sideload, or adb push. so download what you need, choose a method, then transfer it to your phone. you dont have other options, besides for flashing a factory image.
Click to expand...
Click to collapse
Hey dude if you can point me to where I can download one and a tutorial I will, but I've tried almost everything and nothing seems to work.

Ducky10100 said:
Hey dude if you can point me to where I can download one and a tutorial I will, but I've tried almost everything and nothing seems to work.
Click to expand...
Click to collapse
first off, look at your recovery, you should be able to find a mtp and a adb sideload option. mtp would be the regular file transfer. you can google adb sideload twrp, and youll find instructions on that. or you can try googling adb push, and you will find instructions. thats the one i normally would use(but its been a long time), ive deleted my os before as well :angel:
---------- Post added at 06:35 PM ---------- Previous post was at 06:23 PM ----------
here's something I just found about adb sideload http://www.droidviews.com/sideload-roms-mods-using-adb-sideload/

simms22 said:
first off, look at your recovery, you should be able to find a mtp and a adb sideload option. mtp would be the regular file transfer. you can google adb sideload twrp, and youll find instructions on that. or you can try googling adb push, and you will find instructions. thats the one i normally would use(but its been a long time), ive deleted my os before as well :angel:
---------- Post added at 06:35 PM ---------- Previous post was at 06:23 PM ----------
Click to expand...
Click to collapse
Okay thanks man.

reflashing stock via wugs nexus tool as bricked should help.
(this helped me, just read it didnt help you, did you try as bricked/softbricked? (sorry not sure what it is))

rhystagram said:
reflashing stock via wugs nexus tool as bricked should help.
(this helped me, just read it didnt help you, did you try as bricked/softbricked? (sorry not sure what it is))
Click to expand...
Click to collapse
Overkill. You can just put a ROM zip on the sdcard and flash it via TWRP recovery

danarama said:
Overkill. You can just put a ROM zip on the sdcard and flash it via TWRP recovery
Click to expand...
Click to collapse
sdcard with no sdcard slot & support? lol... you cant put anything on the phone with no internal storage either...

rhystagram said:
sdcard with no sdcard slot & support? lol... you cant put anything on the phone with no internal storage either...
Click to expand...
Click to collapse
Internal storage is called sdcard. All you need to do is boot TWRP and connect to PC. You should see your internal storage on your PC then. Drag and drop your ROM from PC to internal storage. Flash ROM, profit.

rhystagram said:
sdcard with no sdcard slot & support? lol... you cant put anything on the phone with no internal storage either...
Click to expand...
Click to collapse
/sdcard is a common directory mounted at /data/media/0. TWRP has MTP access so like android, you plug it into the computer and drag files across. You don't need to remove it to do that.
...and indeed you are right, if you delete the "internal storage"/as s it shows up as in MTP mode, you would have to flash stock (though we'd recommend using fastboot not toolkits) however that is not the case here. The user said he deleted " everything" via TWRP. Although there is an option to "wipe" internal storage, this only wipes the /sdcard data - NOT deletes "internal storage" as someone can do on a computer. So yeah, the quickest and best way to recover from "deleted OS" is to put a ROM.zip on the sdcard and flash it.

Will someone please refer me to a download for Android 5.0. I've tried some, but all the sites are block by my internet provider.

Ducky10100 said:
Will someone please refer me to a download for Android 5.0. I've tried some, but all the sites are block by my internet provider.
Click to expand...
Click to collapse
There is only one legitimate site for Google factory images, and it's linked below. I don't understand why any provider would block it...
And why do you want 5.0? That is the original, release version for the Nexus 6? What version are you on, today? If you are on 5.1 or higher, and you decide to downgrade, do not downgrade your bootloader, as it could brick your device.
https://developers.google.com/android/nexus/images

cam30era said:
There is only one legitimate site for Google factory images, and it's linked below. I don't understand why any provider would block it...
And why do you want 5.0? That is the original, release version for the Nexus 6? What version are you on, today? If you are on 5.1 or higher, and you decide to downgrade, do not downgrade your bootloader, as it could brick your device.
Click to expand...
Click to collapse
I've only had my Nexus for around 3 weeks and I've not updated from 5.0 yet.

Ducky10100 said:
I've only had my Nexus for around 3 weeks and I've not updated from 5.0 yet.
Click to expand...
Click to collapse
Doesn't matter. You've got NO OS now, so just flash the latest. If you're wanting to keep TWRP and dead set against flashing a ROM.zip from recovery as I've suggested, just flash the system and boot image from the factory images.
Can we get it done already?

danarama said:
Doesn't matter. You've got NO OS now, so just flash the latest. If you're wanting to keep TWRP and dead set against flashing a ROM.zip from recovery as I've suggested, just flash the system and boot image from the factory images.
Can we get it done already?
Click to expand...
Click to collapse
Yeah I've already done it now.

Ducky10100 said:
Yeah I've already done it now.
Click to expand...
Click to collapse
Awesome

Thanks for everyone's help!

Installing OTA on rooted XT1064

My wife's XT1064 has on OTA (22.46.12.en.US) available which is a Stagefright fix. It has downloaded but when it tries to apply the OTA it boots into TWRP and I have no frigging clue where the downloaded file is or if it can be applied through TWRP.
Any help would be greatly appreciated as I am unfamiliar with the Moto G's ins and outs.
Thanks.

You must have stock recovery and full unroot for apply the update

Is there no way to push this update via adb sideload?

woozie.2007 said:
You must have stock recovery and full unroot for apply the update
Click to expand...
Click to collapse
So how do I get stock recovery back? Unrooting shouldn't be too big of an issue I am thinking.
drwierdo said:
Is there no way to push this update via adb sideload?
Click to expand...
Click to collapse
Good question. The next question is if anyone knows and how to do it.

Trotter516 said:
So how do I get stock recovery back? Unrooting shouldn't be too big of an issue I am thinking.
Good question. The next question is if anyone knows and how to do it.
Click to expand...
Click to collapse
- YES - LOL but tbh if you're not sure of ins and outs you could do more damage than good in about phone in settings I need your LXB22.xx-xx version.

reefuge said:
- YES - LOL but tbh if you're not sure of ins and outs you could do more damage than good
Click to expand...
Click to collapse
Well I did pretty good with my Galaxy S, Nitro HD, OGP, and haven't borked my Zenfone 2 yet. I successfully unlocked the bootloader and rooted the phone but I know to take it slow and double-check everything before I click it. As long as I have instructions I am good.

Trotter516 said:
Well I did pretty good with my Galaxy S, Nitro HD, OGP, and haven't borked my Zenfone 2 yet. I successfully unlocked the bootloader and rooted the phone but I know to take it slow and double-check everything before I click it. As long as I have instructions I am good.
Click to expand...
Click to collapse
need your LXB version so i can point you to correct recovery

reefuge said:
need your LXB version so i can point you to correct recovery
Click to expand...
Click to collapse
LXB22.46-28
Thanks.

Trotter516 said:
LXB22.46-28
Thanks.
Click to expand...
Click to collapse
stock recovery and required files with my easy installer
download above zip and extract to pc
in extracted folder run motorla device manage 2.5.4 (installs correct mfastboot drivers) choose repair if already installed
install minimal adb v1.31
put phone into AP FASTBOOT MODE (hold power and volume down for 5 seconds and release )
run the flash stock recovery .bat file
choose option 1 then 2 then 4
IF phone does not reboot (stays black screen)
Go back into AP FASTBOOT mode
choose option 1,2,3,4
hope this helps

reefuge said:
stock recovery and required files with my easy installer
download above zip and extract to pc
in extracted folder run motorla device manage 2.5.4 (installs correct mfastboot drivers) choose repair if already installed
install minimal adb v1.31
put phone into AP FASTBOOT MODE (hold power and volume down for 5 seconds and release )
run the flash stock recovery .bat file
choose option 1 then 2 then 4
IF phone does not reboot (stays black screen)
Go back into AP FASTBOOT mode
choose option 1,2,3,4
hope this helps
Click to expand...
Click to collapse
Question: Will this wipe her phone?

Trotter516 said:
Question: Will this wipe her phone?
Click to expand...
Click to collapse
no unless you select option 3 factory reset - option 1 only wipes cache but NOT userdata

reefuge said:
no unless you select option 3 factory reset - option 1 only wipes cache but NOT userdata
Click to expand...
Click to collapse
So, how the procedure went? I have the same situation as you described (Stagefright available and my phone is rooted and running TWRP) and I'm just wondering if you faced any other trouble following the steps.
Thanks

reefuge said:
[stock recovery and required files with my easy installer[/URL]
download above zip and extract to pc
in extracted folder run motorla device manage 2.5.4 (installs correct mfastboot drivers) choose repair if already installed
install minimal adb v1.31
put phone into AP FASTBOOT MODE (hold power and volume down for 5 seconds and release )
run the flash stock recovery .bat file
choose option 1 then 2 then 4
IF phone does not reboot (stays black screen)
Go back into AP FASTBOOT mode
choose option 1,2,3,4
hope this helps
Click to expand...
Click to collapse
Hi, Will this work with XT1063 version with the same LXB (lxb22.46-28). Thanks in advance.

Rickchard said:
Hi, Will this work with XT1063 version with the same LXB (lxb22.46-28). Thanks in advance.
Click to expand...
Click to collapse
no as its recovery for xt1064 - if you replace the recovery with a xt1063 that would work

Would I lose my data stored in the internal memory if I unroot my moto g 2014?
BTW: I am rooted using the the stock firmware.
EDIT: Do I have to re-lock the boot-loader in other to successfully install last update?

Thanks man!
reefuge said:
stock recovery and required files with my easy installer
download above zip and extract to pc
in extracted folder run motorla device manage 2.5.4 (installs correct mfastboot drivers) choose repair if already installed
install minimal adb v1.31
put phone into AP FASTBOOT MODE (hold power and volume down for 5 seconds and release )
run the flash stock recovery .bat file
choose option 1 then 2 then 4
IF phone does not reboot (stays black screen)
Go back into AP FASTBOOT mode
choose option 1,2,3,4
hope this helps
Click to expand...
Click to collapse
I followed your instructions but update fails. It was rooted and with TWRP.
Will flash CyanogenMod soon so I don't care.

Rickchard said:
Hi, Will this work with XT1063 version with the same LXB (lxb22.46-28). Thanks in advance.
Click to expand...
Click to collapse
See my signature (blue) and posts #1 to #4 for xt106x versions

[Guide][No Root]Enable Camera2API in stock rom with Locked bootloader, OTA compatible

This Guide Can Also Be Used For Unlocking & Relocking Bootloader, Installing TWRP & Rooting
If Any Ota Messes With The Implementation Then Whole Procedure Needs To Be Redone
To mitigate the problem requesting developers for making a hack for Relocking Bootloader Without Wiping Data PM me if Interested
Data Will Be Wiped So Make Backup First
What Will We Be Doing: Unlocking Bootloader, Installing TWRP,Flashing Camera2api Enabler, Installing Back Stock Recovery, Relocking Bootloader
Procedure:
1. Download this rar and you'll get 2 folders namely unlock and ASUS_Android_USB_drivers_for_Windows
2. Install the drivers according to your OS (happens Automatically In Most Cases) and open the unlock folder
3. Reboot your phone to fastboot mode by pressing volume up + power on at the same time.
4. Connect it to pc and open unlock.bat in unlock folder
5. Long Press Power Button & Reboot. A wiping Data screen will appear followed by an encrypting sceen then the phone will reboot (A warning of unlocked bootloader will show up initially)& then the initial setup screen will show up don't add any thing & skip the setup(there will be another wipe).
6. Download Cam2Api & copy it to sd card or internal storage of phone. Then switch off the phone once again & reboot in fastboot mode once more.
7. Download TWRP from here & Install Minimal ADB to root of C drive.
8. Copy the twrp to the adb folder in your C drive.
9. Open the 'cmd-here.exe' the adb window will open
10. With the phone connected in fastboot mode type in adb "fastboot flash recovery twrpasus.img" & press enter then type "fastboot boot twrpasus.img" & hit enter.
11. Switch Off the phone & boot in twrp by pressing vol down+power, opening TWRP will take time
12. A decryption popup will open in twrp skip it.
13. Select Install Zip & slect the storage where you have kept the cam2api.zip & flash it, then select reboot system.
14. Download Gcam from here (Arnova v8 is best) & copy it to phone and install it, check if it works, dont configure it. Reboot your phone to fastboot mode
15. Download stock asus recovery from here & copy it to the adb folder.
16. Again open the adb & type "fastboot flash recovery recovery.img"
17. Download Zenfone_Max_M1_Pro_Relock.zip and extract it.
18. Open the directory where you extracted the file
19. In that directory, open a file named relock_bl.cmd
20. A Command (CMD) prompt will do the rest of the work for you.
Let the phone restart.
21. It will then erase all the data on your phone once again (excluding Micro SD card).
23. Reboot
22. Now the phone won’t show the “bootloader unlocked” warning that was displayed after you unlocked the bootloader. Now setup the phone and install the Gcam downloaded earlier also all manual camera apps will work fine too.
Done! You Have Successfully Relocked Bootloader & Enabled Camera 2 api in stock rom. As the bootloader is locked & we have'nt rotted our phone you have your warranty and ota updates work well. If any kind of future ota breaks the camera2api then you have to redo the procedure once again.
Installing Magisk Or SuperSU while twrp is installed will root your phone (breaks ota updates though)
Credits to:
@Sudeep Duhoon : For Original Unofficial unlock & Camera2api Enabler script
@Shivam Kumar Jha For Unofficial TWRP
@style2345 For Providing ASUS Stock Recovery
@myapky For Relocking Script
Hit Thanks If This Helped You!

Ok, I have got stuck. Have a windows 10 machine so was unable to apply the drivers since they were automatically installed. When I tried to install manually, I got an error message that driver is not compatible. Rest of the steps when fine till Step 10. But thereafter TWRP was not installed and the phone went into default recovery with options and th botton of the screen showing an error showing E: couldn't load bitmap fill_ball (error -7). What could have happened?

mehtasu said:
Ok, I have got stuck. Have a windows 10 machine so was unable to apply the drivers since they were automatically installed. When I tried to install manually, I got an error message that driver is not compatible. Rest of the steps when fine till Step 10. But thereafter TWRP was not installed and the phone went into default recovery with options and th botton of the screen showing an error showing E: couldn't load bitmap fill_ball (error -7). What could have happened?
Click to expand...
Click to collapse
You need to uninstall the drivers & redo the process most times we dont need to manually install the drivers. We install drivers only if flashing doesnt occur(you did the opposite) after installing twrp make sure to clear data(factory reset through it)

AstroBiswas said:
You need to uninstall the drivers & redo the process most times we dont need to manually install the drivers. We install drivers only if flashing doesnt occur(you did the opposite) after installing twrp make sure to clear data(factory reset through it)
Click to expand...
Click to collapse
Oh I found my way into TWRP. Am i supposed to keep it read only or accept swipe to allow modifications?

mehtasu said:
Oh I found my way into TWRP. Am i supposed to keep it read only or accept swipe to allow modifications?
Click to expand...
Click to collapse
Swipe to allow modifications ofcourse how would we change anything without that permission

Thankyou, the guide works perfectly. Just to add when installing twrp, boot directly into recovery, otherwise twrp won't install. Just wanted to put it here so that people don't have to go through other threads.

1. Ask before using someone else's stuff in your guide without providing op links or at least give credits
2. Did you test it before posting if the ota will flash fine? As i highly doubt that

Sudeep Duhoon said:
1. Ask before using someone else's stuff in your guide without providing op links or at least give credits
2. Did you test it before posting if the ota will flash fine? As i highly doubt that
Click to expand...
Click to collapse
Thanks for reminding, credits given to each hardworking dev who made this guide possible
Yup I Did Test May Security Patch arrived via ota & it installed fine, didnt break the api.

AstroBiswas said:
Thanks for reminding, credits given to each hardworking dev who made this guide possible
Yup I Did Test June Security Patch arrived via ota & it installed fine, didnt break the api.
Click to expand...
Click to collapse
The June Security Patch is arrived via OTA now?
Sent from my [device_name] using XDA-Developers Legacy app

The Wolf Dark said:
The June Security Patch is arrived via OTA now?
Click to expand...
Click to collapse
No actually my phone has just arrived I Did this procedure on the day itself

AstroBiswas said:
Thanks for reminding, credits given to each hardworking dev who made this guide possible
Yup I Did Test June Security Patch arrived via ota & it installed fine, didnt break the api.
Click to expand...
Click to collapse
Last update was on june 14 with may security patch. I highly doubt this method works without losing ota

Aftab_khatri said:
Last update was on june 14 with may security patch. I highly doubt this method works without losing ota
Click to expand...
Click to collapse
Oh my bad they provided may patch in june update.
We havent done any kind of detectable large system modification so ota's work

Sudeep Duhoon said:
1. Ask before using someone else's stuff in your guide without providing op links or at least give credits
2. Did you test it before posting if the ota will flash fine? As i highly doubt that
Click to expand...
Click to collapse
Thankyou. I had to search for your thread to take care of some troubleshooting. Also, will surely have to follow the guide to go stock/relock to get furture OTA updates. Never the less a big thank you to you and the other developers for their contributions for this phone. Makes this divice so very worthwhile.

Well its working as mentioned by OP.......
Well done !!!

What if we use the command fastboot boot revovery.img and flash the cam 2 api zip when it boots to twrp or is it necessary to use the command flastboot flash recovery recovery.img

pranavsree00 said:
What if we use the command fastboot boot revovery.img and flash the cam 2 api zip when it boots to twrp or is it necessary to use the command flastboot flash recovery recovery.img
Click to expand...
Click to collapse
I had tried it. It didnt work

AstroBiswas said:
I had tried it. It didnt work
Click to expand...
Click to collapse

pranavsree00 said:
Click to expand...
Click to collapse
if you already have twrp installed then you just have to flash the cam2.zip thats all ...........
& if you don't have twrp then you have to first install twrp using the command by OP & then flash cam2.zip as mentioned it original thread .

Anyone who has done this, please reply to this post if they get the next OTA when released, and installed it without any issues. So that I can perform it without any trouble on updates and warranty...

Amal Prabhakaran said:
Anyone who has done this, please reply to this post if they get the next OTA when released, and installed it without any issues. So that I can perform it without any trouble on updates and warranty...
Click to expand...
Click to collapse
Well just follow the give procedure or steps one by one & relock the bootloader at last and you would be good to go .....
Well I didn't relocked the bootloader & I frequently change my ROMS & regarding updates well there is none after 309 so whenever there would be an update I will give it a try then but for now everything is working fine so you can give it a go .........

[Easy_Root/Unroot][Any_Oreo/Nougat_Firmware_V4_Bootloaders][Tmp_Twrp_Recovery]

EASY ROOT/UNROOT FOR S7 OR S7E ALL NOUGAT OR OREO STOCK ROMS
THANKS @klabit87 FOR OREO ROOT
TEMPORARY TWRP RECOVERY VIA ADB THANKS TO @afaneh92​
This is for AT&T, T-Mobile and Verizon and Sprint running V4 bootloaders only!​
This tool will allow you too easily root any stock rom allowing you to make any modifications you might want then easily unroot for better performance
This will Also give you a fully functional TWRP recovery that can be accessed via adb. TWRP is fully functional on OREO Roms but is limited on Nougat roms
The initial setup does require a data wipe.​
S7 G930T Flat Odin Factory FIrmware Downloads
G930TUVU4CRI2_8.0_4File_USA (T-Mobile).rar
ADB_Root Temporary Twrp Tool Download
S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z
S7 G935 Edge Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G935_EDGE_OREO.7z
SM_G935_EDGE_NOUGAT.7z
S7 G930 Flat Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G930_FLAT_OREO.7z
SM_G930_FLAT_NOUGAT.7z
Instructions
1. Download S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z and your model and version you want from above
2. Unzip S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z to S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
3. Unzip the Model/Version file you downloaded and copy the files to the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and place them in the Odin folder
4. Prepare your phone for a data wipe
5. Reboot your phone to download mode and flash the AP_ROOT_G93*.tar in the Odin AP slot and reboot your phone to recovery
6. Once phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
7. Now in the cmd window make sure your device is connected and choose Option (1) Launch TWRP
8. Your phone should launch TWRP leave phone plugged in and command window open on computer
9. Now In Twrp choose wipe and choose format data. Type yes in the box when it ask
10. Now in cmd window choose Option(8) Push Root.zip to Phone
11. Now in TWRP choose install and select the Root.zip
12. After zip is installed reboot and go through setup.
13. Once through setup make sure you are rooted
To Unroot Your Phone
1. In the Root Control app choose phone settings and unroot phone make sure phone is connected to computer
2. Now depending on the type of root you choose your phone will reboot to download if you chose system root or stock recovery if you chose systemless root. If your phone reboots to download mode skip to number 5
3. If your phone reboots to recovery once your phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
4. In cmd window choose Option(3) Unroot phone will reboot too download mode
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar
To Reroot Your Phone
1. Reboot to download in Odin AP slot flash AP_ROOT_G93***.tar
2. Phone will reboot then will reboot one more time and you will be rerooted
To Enter TWRP When Rooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Manually reboot phone to recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP
2. To Exit TWRP simply choose reboot
To Enter TWRP When Unrooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Put phone in download mode In Odin AP slot flash AP_ROOT_G93***.tar force phone to reboot to recovery. If you let phone boot it will reroot and you will have to run the unroot from the root control app.
2. In recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP.
3. Do whatever you need too do
4. To exit Twrp choose reboot to Download
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar

Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good

jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
I had to look this up so thought I'd share This is for Tmobile Versions
Example: G930TUVS8CRJ1 (5th # from right is 8, BL version - this is found in Settings>About Phone>Software Information>Baseband Version)
Which Oreo versions are safe (ver 4):
G930TUVU4CRI2 Oct 1, 2018
G930TUVU4CRF1 June 28, 2018
Not safe (ver 8):
G930TUVS8CRJ1 Oct 26, 2018 release date
---------- Post added at 02:55 AM ---------- Previous post was at 02:49 AM ----------
BTW nice work as always Jr! Oh, & almost forgot ...your last comment saved my @zz!!! I wasn't aware of the ver 8 issue, and the fact that u can't downgrade!! DAMN Samsung!!!!! I was seriously about to try this latest update just to try & figure out RCS not working on CRF1 & randomly came across this! THANKS! (BTW if you know anything about RCS on s7 or services/apks needed for functionality on CRF1 please pm me!)
On another note, let's have a contest to see who can hold on to the S7 the longest as their primary phone

It works perfectly , I had no problem installing it. But I have a question:
Could I replace the SuperSu with the Magisk?
I am also in the Rom Project L S7 of Lanc-City: 3

FranMLG said:
It works perfectly , I had no problem installing it. But I have a question:
Could I replace the SuperSu with the Magisk?
I am also in the Rom Project L S7 of Lanc-City: 3
Click to expand...
Click to collapse
No magisk requires custom boot.img
Sent using some kind of device I modified

jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
Thanks for the effort and providing root for T-Mobile. Perhaps I am an unlucky person. By the time I discovered this thread, my phone was already updated to G930TUVS8CRJ1 version. I am wondering if there is any hope for V8 bootloader to root their phone in near future. Here is my humble request if you could provide root for V8 update. TIA.

jrkruse said:
No magisk requires custom boot.img
Sent using some kind of device I modified
Click to expand...
Click to collapse
can we do full backup after setting up the phone and then restore it without any bugs and issues?

zfk110 said:
can we do full backup after setting up the phone and then restore it without any bugs and issues?
Click to expand...
Click to collapse
Do a system.img backup
Sent using some kind of device I modified

Thank you. It worked fine on my nougat s7 flat with v4 bootloader. Now I have nougat root. I have a question if I may, Can I use tmp twrp to flash Oreo or one of your, or other roms? Or would I need to upgrade the kernel or something because I can flash Oreo being that I'm on Nougat. Thanks.

boofbatch said:
Thank you. It worked fine on my nougat s7 flat with v4 bootloader. Now I have nougat root. I have a question if I may, Can I use tmp twrp to flash Oreo or one of your, or other roms? Or would I need to upgrade the kernel or something because I can flash Oreo being that I'm on Nougat. Thanks.
Click to expand...
Click to collapse
You have to update bootloaders and firmware as well so its better to update to oreo first
Sent using some kind of device I modified

working fine.
update: gonna have to switch back to u firmware because even when i unroot the phone, certain games wont work or connect to server. i cant install magisk to bypass safetynet or hide magisk after installing so root isnt even seeming worth it on this device. might as well stick to the u firmware and disable the apps I dont need and disable ota update so that i dont get the v8 bootloader update. It was fun while it lasted.

jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
Man, will you update the Recovery for the new security patch (CRJ1) ?, I've run out of Root , and I can no longer go back in the version.
---------- Post added at 04:50 PM ---------- Previous post was at 04:47 PM ----------
jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
That's exactly what happened to me, I did not know

FranMLG said:
Man, will you update the Recovery for the new security patch (CRJ1) ?, I've run out of Root , and I can no longer go back in the version.
---------- Post added at 04:50 PM ---------- Previous post was at 04:47 PM ----------
That's exactly what happened to me, I did not know
Click to expand...
Click to collapse
yikes sorry to hear that

jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
I bought a phone which is already to g930tuvs8crj1 I tried to down grade but it wont let me, what are my options? Thanks

zfk110 said:
I bought a phone which is already to g930tuvs8crj1 I tried to down grade but it wont let me, what are my options? Thanks
Click to expand...
Click to collapse
Enjoy Stock
Sent using some kind of device I modified

jrkruse said:
Enjoy Stock
Sent using some kind of device I modified
Click to expand...
Click to collapse
After looking around for 4 days I was finally able to find G930T U8 ENG ROOT Modem.bin file, but when I'm trying to flash it using odin it wont pass file Analyzing
I hope you can look more into it. if we can flash this then we can able to root U8 bootloaders too
https://drive.google.com/open?id=1dhHeYAPsCqKQ_eFfuzPaYbgFv0y1BSLr
These guys also selling Eng boot for $60
https://support.halabtech.com/index.php?a=downloads&b=file&id=90428

zfk110 said:
After looking around for 4 days I was finally able to find G930T U8 ENG ROOT Modem.bin file, but when I'm trying to flash it using odin it wont pass file Analyzing
I hope you can look more into it. if we can flash this then we can able to root U8 bootloaders too
https://drive.google.com/open?id=1dhHeYAPsCqKQ_eFfuzPaYbgFv0y1BSLr
These guys also selling Eng boot for $60
https://support.halabtech.com/index.php?a=downloads&b=file&id=90428
Click to expand...
Click to collapse
Im just waiting on them to email me the passwords
Sent using some kind of device I modified

Alright guys i really need your help...i just bought a used samsung. galaxy s7 G930T...the problem is it doesnt get any network...thr signal says searching and theres is nl network bar...the issue is i cant tell if it is unlocked or not..because it reads my sim...it displays the right access point....shoes sim tools...but just doesn't get network..i ve tried all sim cards...i tried using the tmobile unlock tool that came with the device butbit says unlock failed reboot device repeatedly....ive tried factory reset....i love this phone and would really like to use it...Pls any suggestions or help...the software version is 8.0. baseband version is G930TUVS8CRL1

marvelv94 said:
Alright guys i really need your help...i just bought a used samsung. galaxy s7 G930T...the problem is it doesnt get any network...thr signal says searching and theres is nl network bar...the issue is i cant tell if it is unlocked or not..because it reads my sim...it displays the right access point....shoes sim tools...but just doesn't get network..i ve tried all sim cards...i tried using the tmobile unlock tool that came with the device butbit says unlock failed reboot device repeatedly....ive tried factory reset....i love this phone and would really like to use it...Pls any suggestions or help...the software version is 8.0. baseband version is G930TUVS8CRL1
Click to expand...
Click to collapse
Sounds like you bought yourself a blacklisted phone
Sent using some kind of device I modified

jrkruse said:
Sounds like you bought yourself a blacklisted phone
Sent using some kind of device I modified
Click to expand...
Click to collapse
It is not blacklisted ...i already checked...any help?