Database Users

Stuck in BootLoop and Factory Wiping doesn't actually wipe anything

Nexus 7 (2012)
4.4.4 Stock
KTU84P
HW Version - ER3
Bootloader Version - 4.23
Locked Bootloader
Not Rooted
I have a Nexus 7 sitting in front of me that was dropped off by my aunt in hopes that I could repair it for her. It doesn't look too promising, but I thought I'd consult the mighty fine people here on XDA before I give her the bad news. Here's what she says happened. Yesterday, while preforming day to day activities on it (browsing internet, Skyping, Facebook, etc), the device completely froze. After holding down the Power Button and forcing it to shutdown, she booted it back up. Everything seemed to functioned properly for about 30s - 1min when, at that time, the device turned off and rebooted on its own. After booting back up, it started to repeat this cycle. Basically getting stuck in a bootloop. I personally have never witnessed a bootloop like this before, where the device successfully boots up completely into the OS before turning off and repeating. I'm more used to dealing with ones where it might go as far as the manufacturer logo and then repeats. So anway, as I stated, I only have a 30s - 1min window where I can make changes in order to troubleshoot. The first thing I figured I should do was to go into "About Device", turn Developer Mode on and get USB Debugging enabled. I was able to do this and used "adb devices" to confirm its connection to my computer before it looped again. After its next bootloop I headed back into settings because I wanted to take note of the Android version she was running. As I was navigating there, I noticed that the Developer Options were no longer active. Basically as if I hadn't enabled them yet. This made me start thinking that changes being made on the device weren't sticking. I decided to make a few visual changes to the home screen and see if they were still there after the next bootloop. I uninstalled an app, rearranged icon placement, and changed the wallpaper. Once it shutdown and booted back up again, everything was back to the way it was before the changes had been made. The app I had uninstalled was still there, the wallpaper reverted back, and the icons were back in their original location. At this point I decided to see if I could reboot into Safe Mode. Unfortunately, this doesn't work. I am able to get the reboot to Safe Mode confirmation box and tap "Ok" but it remains in Normal mode when it boots back up. I eventually tried to boot into recovery and preform a Factory Reset. I was able to get into recovery and reset the Nexus. Or so I thought. Instead of seeing a Device Setup screen after it wiped, like I assumed I would, it booted up and still had all the data on it. There were no errors during the wipe and it was confirmed with "Data wipe complete." afterwards.
I am absolutely lost. I've never dealt with such an unusual issue before. Especially with it not even reacting to a complete data wipe. So, just to recap . . . I only have 30s - 1min available to interact with the OS before it reboots itself, any changes made during that time don't stick, Device is successful booting into Stock Recovery, and I can successfully get a Fastboot connection when booting to the Bootloader.
Luckily she has come to terms that this might not get fixed and has decided to go a head an order a newer 2013 model. I'd still like to try any solutions that you all might have. Just in case there is a slight glimmer of hope.
Oh, and one last thing I should mention. I tried to see if I could get the bootloader unlocked but it didn't work. This is the first Nexus I've ever had in my possesion, so I'm not really familiar with the tools available for it. I found WugFresh's Root Toolkit and attempted to Unlock with it. The process seemed to go as it should and I didn't receive any errors on the tablet or in the software. However, in the end, it didn't make any changes to the bootloader.

same problem
I have the same problem as you.
Did you find a solution?
Can anybody help us?
Thanks.

I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?

eawooten said:
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
Click to expand...
Click to collapse
I have tried factory reset from recovery, no errors while wiping but when device restarts nothing has happened: I only have a 30s-1min of old system with all my data and apps or directly bootloop.
Also I have tried flash factory images with Nexus Tool Kit and directly from bootloader. No errors while flashing, apparently has flashed new image system. When device restarts nothing has happened: bootloop or my old system with data and apps for 30s before restart.

Myself and a few others are having the same problem... please keep us updated if you find anything out.
http://forum.xda-developers.com/showthread.php?t=2588911

[Q] Tried reverting to Kitkat, screwed something up

After a whole 24 hours of using Lollipop and found the phone was unusable (phone would ring, but not give any other indication of an incoming call) in some ways, and lacking in other features, I decided it was time to go back to 4.4.4.
So I followed the instructions from Google(/android/nexus/images) , downloaded the 4.4.4 Occam factory image, and installed Minimal ADB and Fastboot. It took a while playing with drivers to get the device to show properly with the adb devices command, but it finally did, and was able to command it to reboot bootloader.
Everything still looking good. Still following the instructions, did the oem unlock, wiping it to factory settings, and then ran flash-all.bat. It went through that, the phone restarted into the bootloader, this time showing the Kitkat loading images instead of Lollipop, I think I'm home free.
I'm in the bootloader again now and notice adb devices is no longer showing the phone, so I try oem lock, and the phone screen updates to show locked. Odd, but it worked. I now used the volume buttons to select power off, and power off the device.
Powering on, the phone shows the Kitkat white "Google" on the screen, but that's it. I try powering it off again, and it restarts itself. I try getting it to display in adb devices, and nothing. The phone has been sitting at this screen for half an hour now with no change.
Using volume down+power I'm able to get it back into fastboot mode, but nothing will work from there. Start, recovery mode, and power off all result in the same thing: phone looks like it's turning on, but sits forever just showing the white "Google" on the screen. Abd devices still shows no devices attached, yet the phone still accepts oem lock and unlock commands, so I tried to run flash-all.bat again, but it just gives a 'command write failed(unknown error)'.
I'm kinda stumped now, and I haven't been able to find anything on this kind of issue. I'm hoping someone might have some experience or be able to suggest something my limited experience hasn't exposed me to before.

EyebrowZing said:
After a whole 24 hours of using Lollipop and found the phone was unusable (phone would ring, but not give any other indication of an incoming call) in some ways, and lacking in other features, I decided it was time to go back to 4.4.4.
So I followed the instructions from Google(/android/nexus/images) , downloaded the 4.4.4 Occam factory image, and installed Minimal ADB and Fastboot. It took a while playing with drivers to get the device to show properly with the adb devices command, but it finally did, and was able to command it to reboot bootloader.
Everything still looking good. Still following the instructions, did the oem unlock, wiping it to factory settings, and then ran flash-all.bat. It went through that, the phone restarted into the bootloader, this time showing the Kitkat loading images instead of Lollipop, I think I'm home free.
I'm in the bootloader again now and notice adb devices is no longer showing the phone, so I try oem lock, and the phone screen updates to show locked. Odd, but it worked. I now used the volume buttons to select power off, and power off the device.
Powering on, the phone shows the Kitkat white "Google" on the screen, but that's it. I try powering it off again, and it restarts itself. I try getting it to display in adb devices, and nothing. The phone has been sitting at this screen for half an hour now with no change.
Using volume down+power I'm able to get it back into fastboot mode, but nothing will work from there. Start, recovery mode, and power off all result in the same thing: phone looks like it's turning on, but sits forever just showing the white "Google" on the screen. Abd devices still shows no devices attached, yet the phone still accepts oem lock and unlock commands, so I tried to run flash-all.bat again, but it just gives a 'command write failed(unknown error)'.
I'm kinda stumped now, and I haven't been able to find anything on this kind of issue. I'm hoping someone might have some experience or be able to suggest something my limited experience hasn't exposed me to before.
Click to expand...
Click to collapse
ADB needs a booted up android to work, it wont work in bootloader mode. Another requirement is that usb debugging must be enabled in dev options. Fastboot works only in bootloader mode and doesnt need usb debugging.

Download wugfresh toolkit.. Use it to restore your device and DISABLE FORCE FLASH
Sent from my Nexus 4 using XDA Free mobile app

How to boot LG Leon into recovery?

I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.

Yeah, it was because the stock recovery doesn't exist as a menu, when you're running stock and enter the adb command "adb reboot recovery" it will reboot to the "factory reset mode" and the actual file of this mode is stored on partition named "recovery". Choosing the factory reset option boots the custom recovery because it replaces the said " factory reset mode" and that's the trick.

You can access recovery from the powered off state by holding volume down and power on until you see the lg sign. Without letting go of volume down, depress on the power button before clicking it back in and holding both buttons in until you see twrp pop up.

If you reboot to recovery now, it''ll probally say secure booting error. Simply go to the Developer options and enable OEM Unlock and that'll make you boot to it

You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha

kruc Ire said:
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
Click to expand...
Click to collapse
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.

kruc Ire said:
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
Click to expand...
Click to collapse
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.

duffycop said:
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
Click to expand...
Click to collapse
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?

kruc Ire said:
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
Click to expand...
Click to collapse
I dunno, I have the H340AR, with this phones happens the same that with the Samsung Galaxy Ace 3, there are, 3G versions, 4G versions, regional versions, etc.. GA3 have 7275R, 7275B, 7272L, 7272T, I dunno, maybe if we could get a device tree for a H340 and an H320 we could make some TWRP and CM compiling, but I just can't figure it out how to make a device tree or even where to begin..
I successfully rooted my H340AR with Kingroot, it works like a charm. I haven't tried fastboot and I tried to install TWRP in this link https://dl.twrp.me/c50/ but I get that F error "Secure booting error". I guess I have my bootloader locked, so I'm trying to figure out how to unlock my bootloader.
I'm trying to contact with some developers and see if anyone can help me build a device tree.

]
Hi, I have that same phone H340AR LTE. I rooted it with Kingroot and also tried to use TWRP to gen into recovery and got that Security error. I only pulled out the baterry and turn it on again so it booted normally. I made a factory reset because I read that it could be a problem of OTA firmware update. Then I installed TWRP and BusyBox again and tried to get into recovery from TWRP option. When I did that, it showed up the Android lying in his back with a red triangle. I pulled a out the battery again and yes, it seems very dumb and simple but it worked and could reboot the phone.
However, I can't get into recovery from TWRP yet. I read that the problem with us not being able to unlock the bootloader(we don't have the OEM option) is because Leon has Lollipop 5.0.1 and OEM is for 5.1.1

pedrovay2003 said:
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Click to expand...
Click to collapse
when i pressed factory reset all it did was to a factory reset even though i flashed twrp.img successfully... help?
lg leon h345 lollipop 5.1.1

This device has a locked bootloader. If you flash a custom recovery on it, it will not boot into recovery, but will report a security issue. You will lose all recovery functionality, including factory reset, adb, fastboot. If your phone fails to boot, you have a brick.

no OS, no TWRP, no fastboot..... no chance?

when reinstalling a ROM earlier today, I got an error 7 ... no problem. probably TWRP problems... so, i go to reboot phone to recovery to begin fresh, and now, TWRP boots, but the screen flashes blank every couple seconds, for a second, then the TWRP splash screen comes back up. blank screen, then TWRP splash screen again. never gets further than that. because I dont have an OS installed, i cannot access debugging for adb. because i deleted my OS, i cannot allow fastboot, to flash a new recovery and begin again. ..
I am broke, and cannot afford to pay for a new replacement thru insurance or to just go buy a junker phone and make do with that.
am i ****ed, or is this recoverable...? ive been searching the forums, but cannot seem to find the answer, and im starting to get nervous enough that its sorta beginning to compound my problems more than i can deal with.
edited to add again: .... battery removed + volume dn then insert battery will not enter fastboot. im about to paperweight this ****.
again edited - Sprint LS997 is phone model. no TOT'ing for me.

What about if you remove the battery, put it back in, hold volume down and then plug the usb cable?

XblackdemonX said:
What about if you remove the battery, put it back in, hold volume down and then plug the usb cable?
Click to expand...
Click to collapse
tried this. still a no-go. phone screen does not power on when trying this or any other combo of steps. LAF works, which is vol+ and plug in USB cable. odd that vol- and plug in USB cable does nothing. maybe faulty vol+ button? never had a problem with that button functioning before now. i have access to: LAF (download mode), and TWRP. However, TWRP 'flashes' off n on... i see the splash screen for a second, then screen goes blank, but still powered on. then splash screen again. rinse, and repeat. no response to touch or vol/pwr buttons. tried pulling battery upon TWRP splash hoping this clears cache, but still just same story afterwards.
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?

elijah420 said:
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
Click to expand...
Click to collapse
From fastboot you can reflash TWRP which from where you can reflash the OS which would unbrick the phone.
elijah420 said:
i have access to: LAF (download mode)
Click to expand...
Click to collapse
If you have access to download mode, can't you reflash your phone using the LGUP with the backup that did in the first place?(you did a backup of the original OS right?)

elijah420 said:
tried this. still a no-go. phone screen does not power on when trying this or any other combo of steps. LAF works, which is vol+ and plug in USB cable. odd that vol- and plug in USB cable does nothing. maybe faulty vol+ button? never had a problem with that button functioning before now. i have access to: LAF (download mode), and TWRP. However, TWRP 'flashes' off n on... i see the splash screen for a second, then screen goes blank, but still powered on. then splash screen again. rinse, and repeat. no response to touch or vol/pwr buttons. tried pulling battery upon TWRP splash hoping this clears cache, but still just same story afterwards.
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
Click to expand...
Click to collapse
Sounds like empty or bad battery to me. When did your phone start acting up upon ya? Right after root or you had it working with root etc before u ended up into such situation.
Also, as XblackdemonX pointed out, you can still use LGUP to stock.

I'm pretty sure that happened to me. And I fixed my H990DS by flashing kdz file in download mode with LG BRIDGE.
There's a guide about how to unbrick any v20 around here.

@elijah420 What software version were you on before this started? Why does it matter? If you were on ZV7 or earlier, then you can flash a VS995 KDZ in download mode, root it, and then fix your phone. If you were on ZV8 or later, then you still might be able to salvage your phone, but you will have to run firmware from another model since you will not be able to root and flash back to Sprint firmware if you were ARB 1 or later. Better than having a totally busted phone though.
Last possibility is to use the debug firehose that I have, but that is an even bigger unknown than running firmware from another model.
-- Brian

Phone stuck on Bootloader [soft brick]

Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.

GitManMatt said:
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
Click to expand...
Click to collapse
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....

slightly further along...
GitManMatt said:
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
Click to expand...
Click to collapse
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:

GitManMatt said:
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
Click to expand...
Click to collapse
Never try to downgrade using stock firmware.

tyamamoto said:
Never try to downgrade using stock firmware.
Click to expand...
Click to collapse
OK thanks, I read that, but didn't realise it was a thing....should I be able to sideload a custom rom using ADB?