Database Info

Unable to root after OTA update

Hi.
Has any one been able to flash custom recovery after installing OTA and upgrading to 23.72-47?
I upgraded to stock version 23.72-47 via the OTA update way. And after that I tried using the fastboot method to flash twrp in bootloader mode. The command is execuded successfully but rebootin to recovery opens the stock recovery and not twrp. Any one was successful in flashing twrp after OTA update?

arunhebbare said:
Hi.
Has any one been able to flash custom recovery after installing OTA and upgrading to 23.72-47?
I upgraded to stock version 23.72-47 via the OTA update way. And after that I tried using the fastboot method to flash twrp in bootloader mode. The command is execuded successfully but rebootin to recovery opens the stock recovery and not twrp. Any one was successful in flashing twrp after OTA update?
Click to expand...
Click to collapse
Just for the heck of it, have you tried just booting into TWRP instead of permanently installing, to see if TWRP will even load ok?

No. Will try.....
Aaaaah, yes. Now I recall why I was wondering the first time I tried to root the fastboot command was 'fastboot boot recovery recovery.img'.
I still wonder why the flash command does not work.. There is a clear 'OKAY' indicating successful flashing of the recovery. It surprises me as to where the recovery was flashed or written (if I have understood flashing correctly).

arunhebbare said:
No. Will try.....
Aaaaah, yes. Now I recall why I was wondering the first time I tried to root the fastboot command was 'fastboot boot recovery recovery.img'.
I still wonder why the flash command does not work.. There is a clear 'OKAY' indicating successful flashing of the recovery. It surprises me as to where the recovery was flashed or written (if I have understood flashing correctly).
Click to expand...
Click to collapse
I had no problems flashing TWRP with "flash" command afterwards. My notes... http://forum.xda-developers.com/2015-moto-g/general/manual-ota-update-process-step-step-t3206049

Boot command worked
As an update I tried the fastboot boot recovery.img command and I could reboot and adb reboot onto twrp recovery mode. But when resorting to the volume button mode to recovery I again was presented with stock recovery.
I tried using the fastboot flash recovery command and it seems to have done the job. Now I am able to reboot to twrp recovery using both software and hardware ways.
What still bugs me is that why did not the flash commands work?
Any insight into this will help me understand the nuances of differences between booton and flashing o I have misunderstood them.

fastboot boot recovery.img=boot into recovery once
fastboot flash recovery=flash it permanently
Sent from my Nexus 6 using Tapatalk

Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation

arunhebbare said:
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
Click to expand...
Click to collapse
I don't know if it's same in Moto devices too or not but in Samsung there's a file named installrecovery.sh which replaces custom recoveries with stock on boot.
But once the device has been rooted it can be stopped from doing so.
Maybe this same thing happend with you.
Again this is just mere assumption keeping a samsung device in mind and may be completely wrong logic.
Sent from my SM-A800F using XDA Free mobile app

arunhebbare said:
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
Click to expand...
Click to collapse
Try using a new usb cable. I have no idea WTF motorola was thinking, including that god-awful charger without a detachable usb. I've seen this problem happen several times, though. When the cable goes bad but still has the actual connection it may not transfer data properly...but since it's connected fastboot doesn't know the file never actually transferred so it reports that it's done.
I bought a 6-pack of Tronsmart USB cables from amazon for $10, and they're absolutely amazing!!! They're made with 20-gauge wires, which are far thicker than those that will come with the phone, no matter what OEM it's from. Fat cable means fast transfer speeds and a longer life, since it will take longer to fray due to its heft.
*** the deal I got is actually back. Last time it only lasted a day, so if you want it, I'd recommend hurrying!!
http://www.amazon.com/Tronsmart-Cha...YYK0/ref=sr_1_7?ie=UTF8&qid=1442849948&sr=8-7

No OS... TWRP won't display files on otg/sd

I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?

emmpii said:
I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?
Click to expand...
Click to collapse
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.

sdembiske said:
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.
Click to expand...
Click to collapse
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work

ive managed to get the latest twrp on.. now I cant seem to adb sideload the rom nor does it show via otg.. ADB sideload disconnects and says invalid zip file

emmpii said:
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work
Click to expand...
Click to collapse
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.

sdembiske said:
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.
Click to expand...
Click to collapse
shows up in device manager as android usb device, Still not showing on adb

I managed to get the device to finally track on with adb. It tracks fine now. However I can't seem to flash a rom on regardless of whether its OTG or sideload...

emmpii said:
shows up in device manager as android usb device, Still not showing on adb
Click to expand...
Click to collapse
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.

sdembiske said:
Try this command: fastboot boot recovery.img or fastboot boot twrp.img
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.
Click to expand...
Click to collapse
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:

emmpii said:
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:
Click to expand...
Click to collapse
The problem with CM roms is they're not really being updated anymore - just one of the problems I have with a lot of custom roms besides the bugs, etc., etc.
If you're hell bent on a custom rom, I would check out this one: [ROM][OFFICIAL][Peregrine][7.X] LineageOS 14.1 at https://forum.xda-developers.com/moto-g/4g-development/rom-cyanogenmod-14-0-t3469103
Lineage is the new go-to from CM. I personally would go back to stock first, however, to ensure everything is restored properly before installing it.
It's being updated regularly currently.

I just had a old CM rom downloaded from before hence I went to that lol. I'm trying lineage for now but I've also downloads the stock ROM. Whatever will keep the phone going

erased os on mi mux 2s

Hi ppl. I need help bad! I accidentally erased my os. So when I try to flash a rom using the mi flash tool(which is amazing) it won't work because I have no operating system to enable USB debugging.so it says enable USB debugging but I can't. Any help would be appreciated TW RP installed unlock bootloader. Thanks in advance!!

just flash recovery rom using twrp then.

Way ahead of you..I tried to transfer several times,files,etc from my PC for some reason two stops halfway and doesn't copy them or move them. Only thing I haven't tried it is ADB sideload.. for some reason that never seems to work for me or work out the way I wanted to.

So twrp is flashed? Then yes try sideload. Also make sure your ADB is up to date as I've had that cause issues with large files and sideload before.
M.

dirtyrott3njb said:
Way ahead of you..I tried to transfer several times,files,etc from my PC for some reason two stops halfway and doesn't copy them or move them. Only thing I haven't tried it is ADB sideload.. for some reason that never seems to work for me or work out the way I wanted to.
Click to expand...
Click to collapse
Miflash doesn't need for usb debugging to flash rom I believe. It's all fastboot. If ur phone is not detected by pc, it means drivers.

It does indicate USB debuging not on. So yes it does . I've used it before to flash TWRP. The flash will also install the drivers before you use it so I can understand why it won't let me transfer anything from PC to phone when fastboot mode. It won't let me get past that stuff in this USB debugging is enabled. Frustrating brand new phone to only a couple weeks old.

Have you booted to twrp and format data (the one where you have to type "yes")?
Mi flash only required adb because it needs to run adb reboot fastboot. I'm in the States as well, PM me and maybe we can get this guy working over remote support. I haven't seen this issue myself, so I can't comment much.
Sent from my Mi MIX 2S using Tapatalk

@noobtoob,thx man. I can't format data because no keyboard is available for some reason. How can I pm you?

dirtyrott3njb said:
@noobtoob,thx man. I can't format data because no keyboard is available for some reason. How can I pm you?
Click to expand...
Click to collapse
Its all good. I'm about to pick up my kids from school, so let me head home, I'll PM you in a bit. We can use TeamViewer or something. If it comes down to it, I also have my work login to use for remote assist. You just need a semi up to date laptop or desktop computer.
Hopefully we can get this solved quickly. I'm unfortunately not in your immediate area, otherwise much easier hands on. The company I work for is down the street from your location however, I'm just a remote systems guy.
Sent from my Mi MIX 2S using Tapatalk

How do u know where I'm at?? Ok sounds good. Where do I look for you msg at?

dirtyrott3njb said:
How do u know where I'm at?? Ok sounds good. Where do I look for you msg at?
Click to expand...
Click to collapse
Tried to pm you but msg sent failed.

Only thing is for some reason I can't transfer anything for my PC to TW RP or my internal storage some reason just doesn't accept it and it's not my computer

I had the exact issue two days ago and the only thing that worked was to manually flash to stock. Since you already have the fastboot rom downloaded and extracted the hard work is done. What you need to do is to put all the files from that main folder (images) into a folder that you have adb installed. Then with your phone connected in fastboot open up a command prompt and once you have the directory set to where your fastboot is type the following and wait until each is done and says okay to move on.
fastboot flash modem modem.img
fastboot flash tz tz.img (I can't remember if this one actually flashed. I think it failed but it didn't matter)
fastboot flash logo logo.img
fastboot flash recovery recovery.img
fastboot flash system system.img (this one will take a long time to start flashing, don't worry. Also, there are about 5 files it will flash so be patient)
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot
That puts you back to stock. I spent almost a whole night freaking out because I didn't have an OS and I couldn't get TWRP to reinstall. Once I did that and got things going I downloaded the same versions update on the phone (the one that can be flashed through the update page in settings) and did a flash of that as well.

sg01fc said:
I had the exact issue two days ago and the only thing that worked was to manually flash to stock. Since you already have the fastboot rom downloaded and extracted the hard work is done. What you need to do is to put all the files from that main folder (images) into a folder that you have adb installed. Then with your phone connected in fastboot open up a command prompt and once you have the directory set to where your fastboot is type the following and wait until each is done and says okay to move on.
fastboot flash modem modem.img
fastboot flash tz tz.img (I can't remember if this one actually flashed. I think it failed but it didn't matter)
fastboot flash logo logo.img
fastboot flash recovery recovery.img
fastboot flash system system.img (this one will take a long time to start flashing, don't worry. Also, there are about 5 files it will flash so be patient)
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot
That puts you back to stock. I spent almost a whole night freaking out because I didn't have an OS and I couldn't get TWRP to reinstall. Once I did that and got things going I downloaded the same versions update on the phone (the one that can be flashed through the update page in settings) and did a flash of that as well.
Click to expand...
Click to collapse
The OP's issue was solved by just flashing TWRP, booting to it and sideloading the Stock ROM. I had the OP download the fastboot files as well, but we ended up not needing them.

Badly f*d Op7Pro. Need help to revert to stock

Hi,
First of all, yes, I have checked the other threads that talk about reverting to stock and I am still stuck.
So I installed Kang OS which is Android 11, and now I want to revert to stock. I have tried downloading multiple different versions of the fastboot ROM from the page https://androidfilehost.com/?w=files&flid=294300 and run the flash all batch file and every time I am either getting stuck in a boot loop or getting the Verity Crash Dump Screen. I have managed to reach the fastboot screen, and I am waiting on the fastboot screen, for someone to show me some way.
Thanks in Advance.

If you used a pin then your storage is encrypted and the rom you are trying to flash can't use it, that's why you're most likely stuck at boot.
I ran into the same issue and posted about it in the same thread. I think we will need a new version of TWRP as 3.4.0-0 would not accept my pin which had not changed.
To fix your issue, sadly, you'll need to wipe your storage:
Boot the phone into fastboot mode
Attach your USB cable to the phone/PC
Download and unzip the file I've attached (ADB/Fastboot)
Launch an elevated command window in the folder you extracted the attached zip to
Try the command fastboot devices and ensure that it reports the device correctly, if not then you need to install the latest OnePlus drivers
Type the following in the command window : fastboot -w (This will wipe the storage)
Try your rom again (TWRP should remain as the recovery if you had flashed it already, if not then copy the latest TWRP img file to the same folder as the ADB/Fastboot tools, use fastboot and type boot twrpfilename.img this will make the phone boot into TWRP recovery, you can then copy over the TWRP zip and flash it to recovery using the booted version of TWRP)
Once you've done the above you shouldn't really need to use the fastboot scripts as the latest rom should just flash from TWRP.

Get msm download tool for guacamole which is the codename of the op7p. I know the shorts with the global version I am unsure if this works with T-Mobile or others?

MSM is a bit of a severe fix when they've already confirmed they can still get fastboot, MSM is for completely bricked phones that can't access anything. Wiping the storage and going to fastboot will allow them to just flash recovery then flash the stock rom. Way easier.

Boot into twrp. Then format data. Phone will boot then.

stuck at bootloader , No OS No Recovery :(

hi my oneplus 7 pro 1910 stuck at bootloader and when i press start or recovery it gets back to the bootloader screen i cant even turn off the phone
i accidentally wiped all partitions in twrp and made a format .
anyhelp ? ive tried to do the fastboot rom flash but my pc doesnt detect my phone
i tried almost every solution i found but nothing works

Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?

@soka said:
Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?
Click to expand...
Click to collapse
Yes it’s unlocked , any help

Search on the fast boot rom thread for the fast boot rom version you were last on, i have used this many times and it worked.
One thing to note, after it flashed everything , I ended up in crash dump error. I went into stock recovery and wiped/formatted my device and it boot up great.

https://forum.xda-developers.com/t/msm-tool-guac-for-all.3934691/ - just follow this guide

One thing that worked for me is when your phone is plugged into your pc open a command prompt and type fastboot boot twrp-*.img (make sure it is the .img not .zip), and from there download the twrp installer .zip and flash that, reboot to recovery, and install the OTA for your device (OTAs can be found at this thread).
If it fails to boot and gives you an error, try fastboot getvar all to see which slot is currently active then do fastboot --set-active=*inactive slot letter* then fastboot --set-active=*original active slot letter* then try to boot to the twrp .img from fastboot again. If fastboot doesn't detect your device at all, try seeing if adb devices outputs anything, and if it does type adb reboot bootloader