Database Info

[Q] [noob] Multi-problems 4ext, CWM, superuser - Advice?

I'm posting this in a single thread to minimize clutter.
I recently ran Easy Ace Root tool as instructed on my inspire. The bootloader unlocked, CWM flashed, but there was an error during superuser flash.
After a reflash of superuser things looked okay, but superuser began not responding. I re-flashed superuser twice in attempt to fix it using the Easy Ace Root Tool.
EDIT: I have discovered that superuser will only function with "USB debug mode" enabled. I've tried it on and off several times, and each time it malfunctions but function returns without a problem.
The backup I have been restoring seems to work because it was created with the debug mode enabled. Took a while to see it.
Second, CWM started to exhibit the "power off, charge" recovery bug where CWM opens.
Last, I attempted to install/flash 4ext Recovery Touch twice to address the CWM bug. Both times it hung at "flashing recovery" (approx 20 mins. both times). Eventually, it indicated that 4ext was installed. However, booting into recovery shows that I still have CWM. I used two different versions (RC8 & RC 7) in the attempt.
I'm now using the restored and working ROM. Solutions to the superuser debug issue I haven't seen posted
The failure to flash 4ext is troubling.
Questions
1. Could these issues be related? Or, what should I be looking for?
2. The recovery issue seems to be the most important. What might be the cause of 4ext to fail in this manner?
3. Can the Easy Ace Root Tool be rerun on the unlocked bootloader, and would that fix anything?
4. Is there reason to worry about flashing with CWM?
I see a number of possible solutions, the main one is to flash a new ROM, which I have already downloaded a couple, but doesn't adress the recovery problems.
The issue with CWM and 4ext leave me less than confident in using it to flash with, although CWM seems okay. The other item is that some ROMs indicate that S-off in required, but many of the threads are a couple years old.
5. Is it correct that S-off is not required to flash ROMs (I read it somewhere)?
I found an answer: NO, YOU DON'T NEED S-OFF TO FLASH ROMS....
Solving the issues are good lessons
Stock AT&T ROM
Android 2.3.5, Sense 3.0
Bootloader screen indicates-
UNLOCKED
S_ON
I know that's a lot for one thread but I'm just looking for a direction and I'll do the search.
If anyone has suggestions, directions, or ideas fire away.
Thanks

I think the fact that you are still S-ON is causing problems with the recovery flashing, since S-ON basically means that the recovery partition is not-writeable.
Have you tried using fastboot to flash a new recovery? Plug your phone into a computer, get into the bootloader, select "fastboot" (if not already selected), wait for "FASTBOOT USB" to appear, and then run the following on the computer:
Code:
fastboot flash recovery <path to recovery.img>
However that S-ON still worries me. You might have to do things manually:
Code:
androidforums.com/desire-hd-all-things-root/702100-how-manually-achieve-s-off-simunlock-supercid-inspire-4g-dhd.html
(Sorry for the broken URL - I had to disguise it. Blargh, I hate being a n00b.)

Evil_ryan said:
I think the fact that you are still S-OFF is causing problems with the recovery flashing, since S-OFF basically means that the recovery partition is not-writeable.
Have you tried using fastboot to flash a new recovery? Plug your phone into a computer, get into the bootloader, select "fastboot" (if not already selected), wait for "FASTBOOT USB" to appear, and then run the following on the computer:
Code:
fastboot flash recovery <path to recovery.img>
However that S-OFF still worries me. You might have to do things manually:
Code:
androidforums.com/desire-hd-all-things-root/702100-how-manually-achieve-s-off-simunlock-supercid-inspire-4g-dhd.html
(Sorry for the broken URL - I had to disguise it. Blargh, I hate being a n00b.)
Click to expand...
Click to collapse
Thanks, I think you meant to say the fact that I am still S-ON? The S_ON part shouldn't be an issue from all that I've gathered. In fact, that's how I have CWM. The Easy Ace Root Tool does CWM, with an unlocked bootloader S_ON. Nothing I have come across states that S_OFF is required to flash 4ext recovery.
Other noobs might find this other thread useful as there is some info and links to recovery images. http://forum.xda-developers.com/showthread.php?p=22489317#post22489317
No I haven't tried the fastboot yet. That is an option, I've got it and adb setup on my computer already. I have looked at AAHK, but as it says its no longer supported, and I don't think I need of S_OFF. Taking it slow to sort out the problems so I don't do sumthin stooopid.

How are you flashing 4ext? From fastboot?

Right, S-ON, that's what I get for writing this at 12 AM.
Don't bother with AAHK, it's discontinued, and even if you still had a copy it couldn't download the necessary files.

bananagranola said:
How are you flashing 4ext? From fastboot?
Click to expand...
Click to collapse
bananagranola,
I used the 4Ext Recovery Updater for both attempts. As I said in the OP, both attempts hung at "flashing recovery" approx 20 mins, and eventually indicated that 4ext was installed. In Recovery Updater it listed/highlighted the version I thought I had installed, but CWM was still the recovery that booted.

Cremnomaniac said:
bananagranola,
I used the 4Ext Recovery Updater for both attempts. As I said in the OP, both attempts hung at "flashing recovery" approx 20 mins, and eventually indicated that 4ext was installed. In Recovery Updater it listed/highlighted the version I thought I had installed, but CWM was still the recovery that booted.
Click to expand...
Click to collapse
Try doing it from fastboot.

bananagranola said:
Try doing it from fastboot.
Click to expand...
Click to collapse
I thought that would be next.
Can you confirm for me that the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=1848846 are correct for the Inspire 4G?
It's the EVO 3D forum. And I have some other links to using fastboot I'll check before doing it.

Yes, those instructions will work. If you can't boot into fastboot through the GUI, you can also power on the phone while holding the volume down button, and that will get you into the bootloader.

Evil_ryan said:
Yes, those instructions will work. If you can't boot into fastboot through the GUI, you can also power on the phone while holding the volume down button, and that will get you into the bootloader.
Click to expand...
Click to collapse
Okay, great. This is the only recovery .img that I have found 4EXT-recovery-2.2.7_RC5.img - 3.33 MB
If I install the 4ext recovery Updater after flashing it should work okay?
And, Will I be able to update once I have flashed it (assuming it works) and have installed the recovery Updater?

Cremnomaniac said:
If I install the 4ext recovery Updater after flashing it should work okay?
Click to expand...
Click to collapse
Probably. But I don't think it really matters, since if you can flash a recovery using fastboot, you can do everything that 4ext updater otherwise would.
Cremnomaniac said:
And, Will I be able to update once I have flashed it (assuming it works) and have installed the recovery Updater?
Click to expand...
Click to collapse
See above.
If 4ext doesn't work, you can also try CWM and TWRP (TeamWin Recovery Project). I use the latter with my Inspire 4g.

I strongly advise you use the app to download the recovery, unzip, and then flash it from fastboot.

bananagranola said:
I strongly advise you use the app to download the recovery, unzip, and then flash it from fastboot.
Click to expand...
Click to collapse
I'll take "strongly" as more than a suggestion. Thanks, it had not occurred to me to get the recovery.img from the updater.
I had actually found several other images and was trying to figure out what was what. That saved me some time, but I did read a lot about 4ext.
I was considering trying the Recovery Updater one more time. Bad Idea?

Cremnomaniac said:
I'll take "strongly" as more than a suggestion. Thanks, it had not occurred to me to get the recovery.img from the updater.
I had actually found several other images and was trying to figure out what was what. That saved me some time, but I did read a lot about 4ext.
I was considering trying the Recovery Updater one more time. Bad Idea?
Click to expand...
Click to collapse
I have a hunch that if you are S-On, you can only write to the recovery partition from fastboot.

bananagranola said:
I have a hunch that if you are S-On, you can only write to the recovery partition from fastboot.
Click to expand...
Click to collapse
I am S-ON. Does that present an issue with fastboot of the recovery.img?
I'm just going to overwrite the current recovery. Nothing else needs to be done does it?

Cremnomaniac said:
I am S-ON. Does that present an issue with fastboot of the recovery.img?
I'm just going to overwrite the current recovery. Nothing else needs to be done does it?
Click to expand...
Click to collapse
No.

bananagranola said:
No.
Click to expand...
Click to collapse
Solved the 4EXT flashing issue. Looks like 4ext flashed okay with fastboot, and the 4EXT Recovery Control works. Rebooted into recovery a couple times just to be sure. That kills 2 birds the CWM bug and the recovery flash.
Thanks for the help and suggestions all.
Some notes from a noobs experience -
Setting up ADB and Fastboot is very easy.
If your cautious as I am run some basic commands in ADB and Fastboot that won't do damage [devices, reboot, reboot-bootloader, etc.]
If you get "error: cannot load 'recovery.img" make sure you navigate to folder that recovery.img is located. Then run "Fastboot flash recovery [Filename]." Even though I set system variables on my desktop to point to adb and fastboot, it won't find the recovery image if you start from the wrong directory in terminal (i.e., C:\)
If you're in ADB and you use the command "adb reboot-bootloader" it will boot the device straight to "Fastboot USB".

Don't forget that each time you flash a ROM from recovery, you still need to fastboot flash its boot.img separately.

bananagranola said:
Don't forget that each time you flash a ROM from recovery, you still need to fastboot flash its boot.img separately.
Click to expand...
Click to collapse
Thanks for the reminder. I just spent an hour looking at 4EXT "smartflash no available". I hav some links for doing fastboot flash of the boot.img. I think I'm good there.
One question from my OP remains. Superuser only works (i.e., grants root access) when I have USB debug mode selected. When it's off superuser says the app (e.g., Titanium BU) is granted permission but just hangs until I force close it and re-enable USB debug. i can't find anything on this problem.
Is it an issue to run my phone in USB debug mode all the time? Or, any clue to the problem?

Recovery failing to flash

So I flash the stock rom on it without thinking and now it wont let me flash a recovery to the tablet threw fastboot or goomanager and it wont update throguh asus update but its booting fine and wont take any updates at all i need help being pointed in the right direction!

I flashed the wrong bootloader i think and how do i flash the correct bootloader without a recover?

in fastboot im getting the error: cannot load 'file name' :no error weather its cm or twrp it wont load it and i dont know what to do please help

First of all it would be important to know what bootloader you are actually on. You do not want to flash a recovery that is not compatible with your bootloader!
So boot into the bootloader with Volume Down and POWER and read the tiny script. From there select the Android with Volume Down and boot back to system with Volume Up.
And then please report in detail what you are trying to do in fastboot, which commands you use etc.
Without knowing what you are doing we cannot tell you what you are doing wrong.....
First step: In fastboot command: fastboot devices - Do you see the serial number of your tab?

berndblb said:
First of all it would be important to know what bootloader you are actually on. You do not want to flash a recovery that is not compatible with your bootloader!
So boot into the bootloader with Volume Down and POWER and read the tiny script. From there select the Android with Volume Down and boot back to system with Volume Up.
And then please report in detail what you are trying to do in fastboot, which commands you use etc.
Without knowing what you are doing we cannot tell you what you are doing wrong.....
First step: In fastboot command: fastboot devices - Do you see the serial number of your tab?
Click to expand...
Click to collapse
bootloader version is us_epad-10.4.4.20-20121026
with a stock rom of 4.1.1
and trying to undo the rom cause im trying to put a stock 4.2.2 on it to get the drivers back on it from the stock rom.
in fastboot i just need to get a twrp installed and i can undo my mess

Skittleskitty said:
bootloader version is us_epad-10.4.4.20-20121026
with a stock rom of 4.1.1
and trying to undo the rom cause im trying to put a stock 4.2.2 on it to get the drivers back on it from the stock rom.
in fastboot i just need to get a twrp installed and i can undo my mess
Click to expand...
Click to collapse
So you are on an ICS bootloader with a JB rom... How the hell did you manage to do that?
You did not answer my question about fastboot. What you tried and what did not work.
But anyway, how I would proceed, just to get you back into safe territory, is to download the latest Asus firmware 10.6.1.14.10, unzip the downloaded file once and copy the resulting zip to the root of your internal SD.
Reboot, and hopefully the stock recovery will recognize the update file and flash you to JB 4.2.1 (which BTW is the latest version for our tabs - there never was, and probably never will be a 4.2.2). Flashing the stock firmware will replace the bootloader.
So from there you just have to get fastboot working, flash the latest TWRP and then the custom rom of your choice COMPATIBLE with your bootloader and recovery.
If that doesn't work we have to try something else. But try this first and report.

berndblb said:
So you are on an ICS bootloader with a JB rom... How the hell did you manage to do that?
You did not answer my question about fastboot. What you tried and what did not work.
But anyway, how I would proceed, just to get you back into safe territory, is to download the latest Asus firmware 10.6.1.14.10, unzip the downloaded file once and copy the resulting zip to the root of your internal SD.
Reboot, and hopefully the stock recovery will recognize the update file and flash you to JB 4.2.1 (which BTW is the latest version for our tabs - there never was, and probably never will be a 4.2.2). Flashing the stock firmware will replace the bootloader.
So from there you just have to get fastboot working, flash the latest TWRP and then the custom rom of your choice COMPATIBLE with your bootloader and recovery.
If that doesn't work we have to try something else. But try this first and report.
Click to expand...
Click to collapse
thank you so much that fixed it!!

ok i did all that but it removed fastboot what do i do to get it back?

Skittleskitty said:
ok i did all that but it removed fastboot what do i do to get it back?
Click to expand...
Click to collapse
Read the text in the upper left corner - current bootloaders enable fastboot in the bootloader menu automatically.

ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.

Skittleskitty said:
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Click to expand...
Click to collapse
Then maybe it's not in your current directory.

Skittleskitty said:
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Click to expand...
Click to collapse
I think your tablet would be a lot safer if you did some reading here: http://lmgtfy.com/?q=fastboot+tutorial

berndblb said:
I think your tablet would be a lot safer if you did some reading here: http://lmgtfy.com/?q=fastboot+tutorial
Click to expand...
Click to collapse
i found that and have been reading it but fastboot still cant read the twrp.blob even though its in the directory with fastboot.

ok ive re installed fastboot and adb sdk and did the environment variable path and it still wont recognize the blob it wont recognize cwm .img files ether and what does key driver not found..booting os

Skittleskitty said:
i found that and have been reading it but fastboot still cant read the twrp.blob even though its in the directory with fastboot.
Click to expand...
Click to collapse
It has to be in your *current* directory.

_that said:
It has to be in your *current* directory.
Click to expand...
Click to collapse
thankyou it moved directorys on me that was the issue

[Q] Bricked one

os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?

brooklynchildxbc said:
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
Click to expand...
Click to collapse
Push a custom rom via adb and flash in recovery or flash stock images via fastboot

acuicultor said:
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
Click to expand...
Click to collapse
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.

brooklynchildxbc said:
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
Click to expand...
Click to collapse
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?

boober78 said:
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
Click to expand...
Click to collapse
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back

brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
No problem. I'm glad I could help
Sent from my One using Tapatalk

brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
Don't give up.... I was in the same position like you for a couple days....and now is fix by my self..... If you unlock your bootloader try to lock back (fastboot oem lock) now try to flash via fastboot Philz Recovery ( try until is rebooting himself into recovery) .... After that put on a memory stick the new system .... You may need to mount the USB flash drive ..... That's exactly what I have done....Good Luck ...

It is damn near IMPOSSIBLE to actualy, truly "brick" these devices. There are way too many safeguards in place.
Be careful before announcing that you are "bricked". Bootlooping (which is what your device was doing) is not "bricked". As long as you have fastboot, you can always reflash recovery, and then use recovery to reflash your custom ROM (or you can bypass all of that and reflash the factory images from fastboot).
Don't panic, you know more than you think you know. Just don't get freaked out, and read. You'll be fine.

NEXUS 5 stuck at Google logo

Hi Guys,
After some cleanup in CMW i accidently format EVERYTHING. (formatted all single option in CMW, afterall a bad idea) So now i'm stuck at the google logo.
Now i have the 4.4.4 KTU.zip on my computer. Can i flash this via ADB sideload (as a renamed ''update.zip''? Or can i just copy the .zip file to my Nexus from a computer?
I'm @ work so i;m stuck guessing what i must do to get this thing work!
Thanks in advance guys

i dont know what it is, but if its a rom, sideload then flash away. your phine is empty right now, no rom or anything. you need to put something into your phone(sideload) then flash it.

Yes, the whole zip file is the stock ROM in a zip file.
Luckely i can't login as administrator here or else i could get my device working here
Thanks!

Why not just start the bootloader (fastboot mode) and execute the flash-all.bat? It'a the 'official' way to completely restore your phone. I've done it several times and it always worked great

experience7 said:
Why not just start the bootloader (fastboot mode) and execute the flash-all.bat? It'a the 'official' way to completely restore your phone. I've done it several times and it always worked great
Click to expand...
Click to collapse
Thanks! Please tell me where to find the flash all bat. Find nothing specific on google...

Alfa Kenny One said:
Thanks! Please tell me where to find the flash all bat. Find nothing specific on google...
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
get the factory image here, unzip it, and run the flas-all.bat. make sure fastboot works correctly. it will flash your phone back to stock.

Soft bricked shield tablet PLEASE HELP!

So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.

okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?

Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?

Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader

Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"

danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha

Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.

Okay will try that. Thanks man.

Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5

Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?

Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader

Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.

Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.

Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5

Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?

Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.

koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?

Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?

Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.

koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader