Database Info

[Q] Bricked Xoom, flashing not working. HELP!

I believe I'm bricked, and when I installed the moto stock .img and tried to flash them, I get an <unknown error> in command prompt. Please help me! can anyone give me some step by step instructions for a fix? thanks!

This may be a dumb question but I need to ask, are you using adb and can you get into fastboot?
Sent from my Xoom using Tapatalk

This is how I unbricked my xoom it will take you back to stock 3.0, then you will have to wait for the over the air updates before you can root again. Any questions, please ask. I have bricked my xoom a few times. Lol.
tabletroms.com/forums/xoom-general-discussion/1268-how-unbrick-your-moto-xoom.html
Sent from my Xoom using Tapatalk

johnny0911 said:
This may be a dumb question but I need to ask, are you using adb and can you get into fastboot?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Yes I'm using adb, and yes, I'm in fastboot.

you must be in bootloader for fastboot commands(adb reboot bootloader)
put 4 stock .img files in platform-tools or tools(from where you are running fastboot)
that should do it.
needless to say your your bootloader must be unlocked for fastboot commands.
.................
the commands are given at motodev website.

rohit3192 said:
you must be in bootloader for fastboot commands(adb reboot bootloader)
put 4 stock .img files in platform-tools or tools(from where you are running fastboot)
that should do it.
needless to say your your bootloader must be unlocked for fastboot commands.
.................
the commands are given at motodev website.
Click to expand...
Click to collapse
I am in Fastboot protocol support. I try flashing the 4 stock .img in platform-tools, and I get errors.
C:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
FAILED (status read failed (Too many links))
finished. total time: 0.253s
C:\AndroidSDK\platform-tools>fastboot flash system system.img
sending 'system' (262144 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
See, it isn't working. any advice! I really hope I didn't pay $700 for a paper weight!!

I also get the OK, then it fails and says this...
C:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 0.727s]
writing 'boot'...
FAILED (status read failed (Too many links))
finished. total time: 1.319s
C:\AndroidSDK\platform-tools>fastboot flash system system.img
sending 'system' (262144 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (12288 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
C:\AndroidSDK\platform-tools>fastboot flash userdata userdata.img

I expect that you have copied all contents of "tools" folder to platform-tools folder.
Your bootloader must be unlocked to accept commands.
check the result of fastboot oem unlock.
Second : when xoom is not in bootloader mode type adb devices and check whether serial no of xoom is displayed.
Also recheck that you have java dev kit.
You may uninstall and then reinstall android sdk.
More than that I can not think of problem.
May be someone else.

rohit3192 said:
I expect that you have copied all contents of "tools" folder to platform-tools folder.
Your bootloader must be unlocked to accept commands.
check the result of fastboot oem unlock.
Second : when xoom is not in bootloader mode type adb devices and check whether serial no of xoom is displayed.
Also recheck that you have java dev kit.
You may uninstall and then reinstall android sdk.
More than that I can not think of problem.
May be someone else.
Click to expand...
Click to collapse
I have copied all of "tools" into platform tools. However, I cannot check adb devices, because I cannot leave the "Dual Core technology" screen. It's stuck on that. I cannot even enter recovery mode! I will attempt to reinstal java dev kit, and android SDK. And I will post my reply on how that works. Thanks for your patience with me. I'm just quite frustrated nothing has worked so far...

V0nice said:
I have copied all of "tools" into platform tools. However, I cannot check adb devices, because I cannot leave the "Dual Core technology" screen. It's stuck on that. I cannot even enter recovery mode! I will attempt to reinstal java dev kit, and android SDK. And I will post my reply on how that works. Thanks for your patience with me. I'm just quite frustrated nothing has worked so far...
Click to expand...
Click to collapse
I'm in the same boat as you, and with no good help. I'm getting the same answers, although my errors are a bit different than yours. If you somehow find an answer, PLEASE let me know.

hocplyr98 said:
I'm in the same boat as you, and with no good help. I'm getting the same answers, although my errors are a bit different than yours. If you somehow find an answer, PLEASE let me know.
Click to expand...
Click to collapse
Got it to work. I Google'd my issue, and I came up with a few possible issues. 1 being the usb cable, and the other being the usb port. Mine was a stock cable, so that wasn't the issue. But when I plugged the usb cable into the back of my pc (directly to the motherboards usb's) it worked, and I did not encounter the "command write failed"! successfully flashed the boot and system... ect img. and now my xoom is working!

[Q] [SOLVED] Cannot Flash Recovery/Root

Hey all,
I bought a Factor Refurbished TF700t with the intention of getting CROM-i flashed on it. I was able to get it unlocked with no issue, however, whenever I try to flash twrp to it, I get this.
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6948 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s
and sometimes this
PS E:\Program Files (x86)\Minimal ADB and Fastboot> fastboot -i 0x0B05 flash recovery twrp.blob
(bootloader) Received Data of Bad Length.
sending 'recovery' (6292 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.009s
I am running the naked USB drivers, usb debugging is enabled and rooting with motochopper does not work. I also downgraded to the 10.6.1.14.8 build. It should be noted that I was on 10.6.1.14.10 build when I did the unlocking, but that didn't seem to effect anything. Lastly, fastboot does see the device as I get this output:
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot devices
015d2d43004bfc01 fastboot
My fear is this may be an issue with the factory referb I got, but hopfully that's not the case! If anyone can help me, it would be greatly appreciated!
Edit: Solved! The answer was to do it in Linux. Grab a distro of Mint and get to it! =D

Highsight said:
Hey all,
I bought a Factor Refurbished TF700t with the intention of getting CROM-i flashed on it. I was able to get it unlocked with no issue, however, whenever I try to flash twrp to it, I get this.
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6948 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s
and sometimes this
PS E:\Program Files (x86)\Minimal ADB and Fastboot> fastboot -i 0x0B05 flash recovery twrp.blob
(bootloader) Received Data of Bad Length.
sending 'recovery' (6292 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.009s
I am running the naked USB drivers, usb debugging is enabled and rooting with motochopper does not work. I also downgraded to the 10.6.1.14.8 build. It should be noted that I was on 10.6.1.14.10 build when I did the unlocking, but that didn't seem to effect anything. Lastly, fastboot does see the device as I get this output:
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot devices
015d2d43004bfc01 fastboot
My fear is this may be an issue with the factory referb I got, but hopfully that's not the case! If anyone can help me, it would be greatly appreciated!
Click to expand...
Click to collapse
It looks like that you have a bad download. Check the md5 to ensure that it is not corrupted..:fingers-crossed:

LetMeKnow said:
It looks like that you have a bad download. Check the md5 to ensure that it is not corrupted..:fingers-crossed:
Click to expand...
Click to collapse
Yeah - and also: which TWRP version are you trying to flash?

LetMeKnow said:
It looks like that you have a bad download. Check the md5 to ensure that it is not corrupted..:fingers-crossed:
Click to expand...
Click to collapse
Can confirm, the hash is correct. Confirmed using the MD5 Check Util.
berndblb said:
Yeah - and also: which TWRP version are you trying to flash?
Click to expand...
Click to collapse
I've tried multiple different ones with the same result sadly, but mostly I've tried 2.7.0.0.

Highsight said:
Can confirm, the hash is correct. Confirmed using the MD5 Check Util.
I've tried multiple different ones with the same result sadly, but mostly I've tried 2.7.0.0.
Click to expand...
Click to collapse
Try a different USB port...
Try to wait to plug your device into your PC until your tablet is already in fastboot...
Let me know if this helps... Thx lj

lj50036 said:
Try a different USB port...
Try to wait to plug your device into your PC until your tablet is already in fastboot...
Let me know if this helps... Thx lj
Click to expand...
Click to collapse
Still no luck. I've been at this for a couple days now. I've tried different cords (one from my dad who also has a TF700 and also my old TF100 cords) and different USB ports, same result for all of them. I read somewhere about USB 3.0 possibly causing problems, is this true? I tried my USB 2.0 ports, but the result seemed the same.

Try "fastboot flash staging twrp.blob", maybe this works better. If not, it can't break anything.

_that said:
Try "fastboot flash staging twrp.blob", maybe this works better. If not, it can't break anything.
Click to expand...
Click to collapse
Same result:
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot flash staging twrp.blob
sending 'staging' (6292 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.007s

OK, then I can only think of "try a different operating system (Linux)" or "try a different computer".

Highsight said:
Can confirm, the hash is correct. Confirmed using the MD5 Check Util.
Click to expand...
Click to collapse
So your file is good..
Highsight said:
I've tried multiple different ones with the same result sadly, but mostly I've tried 2.7.0.0.
Click to expand...
Click to collapse
I just flashed twrp v2.7 yesterday and went fast and done.. So the v2.7 is working on the tf700. I think that this might be causing the problem.
Copy your fastboot folder and put it here c:\platform_tools> fastboot -i 0x0B05 flash recovery twrp.blob. I think that android is a unix/linux base so they don't like special characters which means no "space".
Please try that and report back for other users have the same issue, thanks..

LetMeKnow said:
So your file is good..
I just flashed twrp v2.7 yesterday and went fast and done.. So the v2.7 is working on the tf700. I think that this might be causing the problem.
Copy your fastboot folder and put it here c:\platform_tools> fastboot -i 0x0B05 flash recovery twrp.blob. I think that android is a unix/linux base so they don't like special characters which means no "space".
Please try that and report back for other users have the same issue, thanks..
Click to expand...
Click to collapse
Same results...
C:\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6292 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.018s
C:\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
(bootloader) Received Data of Bad Length.
sending 'recovery' (6292 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.000s
C:\platform-tools>
I'm going to try sterilizing my drivers and installing the naked ones again.

I just have to ask.. Your bootloader is unlocked yes ???

Highsight said:
Same results...
C:\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6292 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.018s
C:\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
(bootloader) Received Data of Bad Length.
sending 'recovery' (6292 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.000s
C:\platform-tools>
I'm going to try sterilizing my drivers and installing the naked ones again.
Click to expand...
Click to collapse
I am sorry for a stupid question but do you see "the device is unlocked" in the upper left corner?
Update: Oops, I am slower than you, @lj50036.

lj50036 said:
I just have to ask.. Your bootloader is unlocked yes ???
Click to expand...
Click to collapse
Supposdly.
Whenever I boot the device it says right on the top left "Device is Unlocked".
When going into the bootloader it says the following on the top left.
"Key driver not found... booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.8-20130514" A03
Starting Fastboot USB download protocol"

LetMeKnow said:
I am sorry for a stupid question but do you see "the device is unlocked" in the upper left corner?
Click to expand...
Click to collapse
Beat you too It.. @LetMeKnow
---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------
Highsight said:
Supposdly.
Whenever I boot the device it says right on the top left "Device is Unlocked".
When going into the bootloader it says the following on the top left.
"Key driver not found... booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.8-20130514" A03
Starting Fastboot USB download protocol"
Click to expand...
Click to collapse
Yes I agree with @_that.... New OS 'Linux' Thats what I would try...

lj50036 said:
Beat you too It.. @LetMeKnow
---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------
Yes I agree with @_that.... New OS 'Linux' Thats what I would try...
Click to expand...
Click to collapse
Lemme see what I can do about setting up a dual-boot for my computer and trying on that. To be honest I'm not great with Linux, especially when it comes to drivers, but I'll see what I can do...

Highsight said:
Lemme see what I can do about setting up a dual-boot for my computer and trying on that. To be honest I'm not great with Linux, especially when it comes to drivers, but I'll see what I can do...
Click to expand...
Click to collapse
O there are no drivers....:good: At least not for your android devices...
I would recommend Mint 16... Here is a link
Mint Download Page
Go for cinnamon desktop....
Shoot me a email if you need any help at all... There is an option to shoot me an email on my user page.....

lj50036 said:
O there are no driver....:good:
I would recommend Mint 16... Here is a link
Mint Download Page
Click to expand...
Click to collapse
Well that's pretty sweet. I assume a live USB will do?

Highsight said:
Supposdly.
Whenever I boot the device it says right on the top left "Device is Unlocked".
When going into the bootloader it says the following on the top left.
"Key driver not found... booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.8-20130514" A03
Starting Fastboot USB download protocol"
Click to expand...
Click to collapse
Everything is looking good and you said that your device is communicating with the fastboot command "fastboot devices" with a return of your device serial number. I don't know why that it refuses to write to your recovery partition. Maybe there are some bad blocks in your partition but you just reinstall the stock firmware. I am sorry that I don't have a clue what is going on...

Highsight said:
Well that's pretty sweet. I assume a live USB will do?
Click to expand...
Click to collapse
It will but I would install it native to a hard drive, as we are talking about a 400 dollar tablet.. Your call :fingers-crossed:

[Q] OnePlus One - Unable to unlock bootloader again after relocking

Hi Guys,
Hope to get some help here.
So i unlocked the bootloader of my one plus one and installed supersu + Twrp recovery. All worked fine until i decided to relock the bootloader.
I've put the device into fastboot mode and executed "fastboot oem lock" with twrp recovery still in there.
Now i am trying to unlock the bootloader again using "fastboot oem unlock" to be able to flash the stock recovery and having issues.
output of commands:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>
After this it boots straight to twrp recovery. I then hit reboot system and go back to fastboot mode and run the below:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (12260 KB)...
OKAY [ 0.389s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.404s
Anyone has an idea how i can unlock the bootloader again ?
Thanks
Vik

Would it let you reflash the stock factory image thru fastboot? Maybe if you could do that it would let you unlock again. And it would give you stock recovery.
Or else what about the option in developer settings to update the stock cm recovery when installing an update. Maybe you could install an official update thru TWRP and get stock recovery back?
Just throwing out ideas, hope you figure it out

I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.

lemonspeakers said:
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
Click to expand...
Click to collapse
Thanks i'll give that a try as soon as am home..

YrrchSebor said:
Would it let you reflash the stock factory image thru fastboot? Maybe if you could do that it would let you unlock again. And it would give you stock recovery.
Or else what about the option in developer settings to update the stock cm recovery when installing an update. Maybe you could install an official update thru TWRP and get stock recovery back?
Just throwing out ideas, hope you figure it out
Click to expand...
Click to collapse
Hi YrrchSebor,
Thanks for the reply.. I already tried all that, even using adb sideload and keep getting same error as mentioned above. I'll try the solution lemonspeakers suggested later today and post the outcome.
Thanks

Vikmeister said:
Hi YrrchSebor,
Thanks for the reply.. I already tried all that, even using adb sideload and keep getting same error as mentioned above. I'll try the solution lemonspeakers suggested later today and post the outcome.
Thanks
Click to expand...
Click to collapse
Be careful if you updated your phone to XNPH30O OTA,
!!! Warning !!!
In the NEW OTA CM11S XNPH30O, the bootloader (aboot) img size changed....
We request all not to apply the unlocker scripts on the new bootloader , until we confirm/find the new bit position.
It might brick your phone and corrupt bootloader...
Click to expand...
Click to collapse
It won't work.. do not try it if you updated to XNPH30O using the OTA.

zephiK said:
Be careful if you updated your phone to XNPH30O OTA,
It won't work.. do not try it if you updated to XNPH30O using the OTA.
Click to expand...
Click to collapse
Thanks for letting me know ZephiK i haven't updated to that version yet. I still have XNPH25R. I should all good.

Fantastic.. Thanks a lot guys.. That worked like a treat.. Bootloader is now unlocked.
:laugh::good:

lemonspeakers said:
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
Click to expand...
Click to collapse
I ran this command:
Code:
fastboot.exe boot TWRP-2.7.1.0.img
But the next step does not work:
Code:
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or from sdcard...
I got:
downloading 'boot.img'...
OKAY [ 0.484s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.487s

That's because you can't boot a recovery with the recent bootloader unless you're unlocked.
Transmitted via Bacon

Hello,
so how to unlock the bootloader when:
- i can only access to fastboot and i have connectivity to pc;
- command 'fastboot oem unlock' doesn't work( FAILED (remote: oem unlock is disabled) )
- command 'fastboot flash recovery firmware.zip' doesn't work (FAILED (remote: Device not unlocked cannot flash or erase))
- all adb commands say: "error: device not found"
- i can't access recovery for use adb sideload (phone freezes with 1+ icon in screen)
- i can't access Android (phone freezes with 1+ icon in screen)
What can i do?
Thanks in advance!
Gustavo

Im have the same issue but I have no recovery installed..Anyway to do this

i have same issue plz give me any solution if you found any???plz let me know plzzzzz
​
piriri007 said:
Hello,
so how to unlock the bootloader when:
- i can only access to fastboot and i have connectivity to pc;
- command 'fastboot oem unlock' doesn't work( FAILED (remote: oem unlock is disabled) )
- command 'fastboot flash recovery firmware.zip' doesn't work (FAILED (remote: Device not unlocked cannot flash or erase))
- all adb commands say: "error: device not found"
- i can't access recovery for use adb sideload (phone freezes with 1+ icon in screen)
- i can't access Android (phone freezes with 1+ icon in screen)
What can i do?
Thanks in advance!
Gustavo
Click to expand...
Click to collapse
plz help same issue

Can't unlock bootloader

I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?

aroshlakshan said:
I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
Click to expand...
Click to collapse
There are How-to's on this site. It's probably unlocked now. Try flashing a custum recovery in fastboot.

aroshlakshan said:
I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
Click to expand...
Click to collapse
That means that the device was already unlocked. Where did you buy yours? Ali Express? Mine's from there and I have gone through what you're going through right now. No worries. Bootloader is already unlocked so you can root it already.

ken_alpha24 said:
That means that the device was already unlocked. Where did you buy yours? Ali Express? Mine's from there and I have gone through what you're going through right now. No worries. Bootloader is already unlocked so you can root it already.
Click to expand...
Click to collapse
I bought that off of eBay. I have tried to flash a custom recovery but it doesn't seem to get installed as well. After I do it, I only see the stock recovery but when I run the command fastboot flash recovery recovery.img it gives me the following message.
target reported max download size of 536870912 bytes
sending 'recovery' (8134 KB)...
OKAY [ 0.264s]
writing 'recovery'...
OKAY [ 0.179s]
finished. total time: 0.445s
But when I go to recovery, I only see the stock recovery. It seems like even-though the command are executed successfully on the computer, they are not applied to the phone. Any ideas?

Any ideas guys?

aroshlakshan said:
Any ideas guys?
Click to expand...
Click to collapse
Settings > Developer Options > Update CM Recovery (untick)
Then flash your recovery via fastboot and it'll stick.

zephiK said:
Settings > Developer Options > Update CM Recovery (untick)
Then flash your recovery via fastboot and it'll stick.
Click to expand...
Click to collapse
I was able to flash a custom recovery. Thank you. I'm now about to CLEAN INSTALL XNPH38R on my phone. Any ideas on how to do that?

aroshlakshan said:
I was able to flash a custom recovery. Thank you. I'm now about to CLEAN INSTALL XNPH38R on my phone. Any ideas on how to do that?
Click to expand...
Click to collapse
Download the factory stock images on cyngn. Find it online and fastboot flash it. There's a good guide online in the general forums that shows you how to go back to stock
Sent from my One A0001 using Tapatalk

zephiK said:
Download the factory stock images on cyngn. Find it online and fastboot flash it. There's a good guide online in the general forums that shows you how to go back to stock
Sent from my One A0001 using Tapatalk
Click to expand...
Click to collapse
I got it working. I flashed TWRP on my phone and wiped the phone. Downloaded http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH38R-bacon-signed-fastboot.zip , extracted the contents and flashed it with fastboot using the following commands.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img
fastboot reboot
Hope this helps a newcomer like me. Thanks guys.

Cannot Boot into TWRP

Whenever I try to use the command
fastboot boot [whatever].img
I get this message
downloading '[whatever].img'...
OKAY [ 0.699s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.699s
This is a brand new (to me) device from Amazon, listed as renewed. No idea if that makes a difference or not.
My goal is to set TWRP as my recovery and then install LineageOS, however I am stuck at this stage, and everything I've found to try has achieved nothing. I always get stuck at this portion.

OpieServus said:
Whenever I try to use the command
fastboot boot [whatever].img
I get this message
downloading '[whatever].img'...
OKAY [ 0.699s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.699s
This is a brand new (to me) device from Amazon, listed as renewed. No idea if that makes a difference or not.
My goal is to set TWRP as my recovery and then install LineageOS, however I am stuck at this stage, and everything I've found to try has achieved nothing. I always get stuck at this portion.
Click to expand...
Click to collapse
Check to see if 'oem unlocking' is still checked.

0x0null said:
Check to see if 'oem unlocking' is still checked.
Click to expand...
Click to collapse
I'm not sure what you mean by 'checked' but yes, the bootloader is unlocked.

OpieServus said:
I'm not sure what you mean by 'checked' but yes, the bootloader is unlocked.
Click to expand...
Click to collapse
Hi bro, can help me?

Which twrp version and which android version are being tried?

Which fastboot version are you using? (Type fastboot --version)
I had an issue two weeks ago with an outdated fastboot (v.28), updating to the latest one (v.33) solved the problem.
--ks