I got home from work plugged my phone in and went to sleep. When I woke up the phone was on the bootloader screen. It wont do anything but switch screens from bootloader to hboot. I have trying installing the stock rom from here http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103 it fails to load from an micro sdcard.
This is a Verizon One M8 phone that has been rooted since release. I have been running Venom http://forum.xda-developers.com/showthread.php?t=2715225 4.3.0 for verizon users.
On the hboot screen it says:
** software statusffical ***
*** Unlocked ***
M8_mlv pvt ship s-offf
cid-vzw__001
hboot-3.19.0.0000
radio-invalid_ver_info
opendsp-invalid_ver_info
os-4.17.605.5
emmc-boot 2048mb
(time and date)
Also when it reboots it shows the android guy in the middle of the screen. It never show the HTC logo.
Try flashing a kernel http://forum.xda-developers.com/showthread.php?t=3152454
Kernels for One M8 AOSP Roms Discussion
Sent from my One using XDA Premium 4 mobile app
How do I flash a kernel? I can only get into fastboot.
I tired this:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Shannon>cd\
C:\>cd Android
C:\Android>cd com
C:\Android\com>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 5.035s
C:\Android\com>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.003s
C:\Android\com>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.003s
C:\Android\com>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 10.075s]
finished. total time: 10.075s
C:\Android\com>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 10.071s]
finished. total time: 10.071s
C:\Android\com>fastboot oem rebootRUU
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 0
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.081s]
finished. total time: 10.081s
C:\Android\com>fastboot flash zip rom.zip
target reported max download size of 1826336768 bytes
sending 'zip' (1726320 KB)...
OKAY [ 47.915s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 47.920s
It does not work
I tried this http://www.droidviews.com/restore-verizon-htc-one-m8-to-stock-rom-with-ruu/
It never gives me the HTC logo screen.
C:\Android\com>fastboot flash recovery twrp-2.8.6.1-m8.img
target reported max download size of 1826336768 bytes
sending 'recovery' (17006 KB)...
OKAY [ 1.573s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 11.713s
C:\Android\com>fastboot flash boot boot.img
target reported max download size of 1826336768 bytes
sending 'boot' (10066 KB)...
OKAY [ 1.001s]
writing 'boot'...
FAILED (remote: image update error)
Sorry I've been busy all day,but try to reboot your phone
Sent from my One using XDA Premium 4 mobile app
That brings me back to the fastboot screen
tjamscad said:
That brings me back to the fastboot screen
Click to expand...
Click to collapse
Ok try a dirty flash of a different rom
Sent from my One using XDA Premium 4 mobile app
I can't flash anything. Everything fails.
tjamscad said:
I can't flash anything. Everything fails.
Click to expand...
Click to collapse
What ROM did you have installed when this happened?
Sent from my One M8 using XDA Premium 4 mobile app
Venom 4.3 for Verizon
SD card method should work always as long as you are using fat32 and have the file name exact. If it's not working too aren't doing one of the two above correct.
Sent from my HTC6535LVW using Tapatalk
Like this?
tjamscad said:
Like this?
Click to expand...
Click to collapse
Does it do that everytime you flash it? The same exact output?
Sent from my HTC6535LVW using Tapatalk
Yes
I get this when I do factory reset from the hboot screen. I never see the HTC logo like I should.
Like thi
Related
i have problem in my sensation ,when do unlock for bootloader then make lock bootloader i forget and do lock bootloader twice ,and now apeear to me <relocked bootloader> with <s-on>and now i make unlock bootloader toooooo much times and bad result and when install recovery write it <<<<FAILED (remote: signature verify fail)>>>>please help me to unlock it again
gawgaw said:
i have problem in my sensation ,when do unlock for bootloader then make lock bootloader i forget and do lock bootloader twice ,and now apeear to me <relocked bootloader> with <s-on>and now i make unlock bootloader toooooo much times and bad result and when install recovery write it <<<<FAILED (remote: signature verify fail)>>>>please help me to unlock it again
Click to expand...
Click to collapse
did you try to use unlocked bin code again?if not then do it again
i do it tooo much,and using many tools
now i can think only one thing.flash the specific ruu.exe for your device and start from the beginning
see here
http://forum.xda-developers.com/showthread.php?t=1672425
otherwise if you have patience wait for someone else to provide you a solution
i do all of this and install <RUU FILES>and the problem not fixed ,i copy this information to help you and indicate my problem
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\george>cd C:\Program Files\Android\android\platform-tools
C:\Program Files\Android\android\platform-tools>Unlock_code.bin
C:\Program Files\Android\android\platform-tools>fastboot flash unlocktoken Unloc
k_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.160s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.192s
C:\Program Files\Android\android\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 3.243s]
finished. total time: 3.250s
C:\Program Files\Android\android\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
OKAY [ 3.190s]
finished. total time: 3.195s
C:\Program Files\Android\android\platform-tools>fastboot flash zip PG58IMG.zip
sending 'zip' (23984 KB)...
OKAY [ 4.164s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 9.370s
C:\Program Files\Android\android\platform-tools>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.431s]
finished. total time: 0.435s
confirm something
when you use the ruu.exe did you have successful result for flashing it?
yes,the result successful but the problem not fixed ,bootloader relocked
gawgaw said:
yes,the result successful but the problem not fixed ,bootloader relocked
Click to expand...
Click to collapse
ok then
the only thing that i can tell you is to follow the whole process for unlocking the bootloader
start from the beginning.if that don't work too then i am out of ideas
best wishes
if i think something else i will tell you
thank you tooo much ,im sorry to tired you
Can you boot the phone now?
Also did the phone came from a repair with motherboard replaced?
Sent from my HTC Sensation using xda premium
Hi Mates!
Ive got a soft bricked moto g, it says bl is locked, i cant flash retail firmware (hab check fail error), ive got the unlock code, but if i try to unlock the bl with fastboot oem unlock, it says
(bootloader) fastboot oem unlock disabled!
FAILED (remote failure)
finished. total time: 0.025s
Any suggestions?
Here is my fastboot prompt:
d:\MotoG\442>fastboot.exe flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1940 KB)...
OKAY [ 0.147s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.565s]
finished. total time: 1.714s
d:\MotoG\442>fastboot.exe flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (619 KB)...
OKAY [ 0.125s]
writing 'logo'...
OKAY [ 0.125s]
finished. total time: 0.252s
d:\MotoG\442>fastboot.exe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.429s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.485s
d:\MotoG\442>fastboot.exe flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.395s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.426s
d:\MotoG\442>fastboot.exe flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (255768 KB)...
OKAY [ 8.714s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.851s
d:\MotoG\442>fastboot.exe flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (244360 KB)...
OKAY [ 8.304s]
writing 'system'...
OKAY [ 10.235s]
finished. total time: 18.541s
d:\MotoG\442>fastboot.exe flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (220989 KB)...
OKAY [ 7.533s]
writing 'system'...
(bootloader) Failed to validate sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.965s
d:\MotoG\442>
d:\MotoG\442>fastboot.exe flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (47476 KB)...
OKAY [ 1.648s]
writing 'modem'...
OKAY [ 1.479s]
finished. total time: 3.128s
d:\MotoG\442>fastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.066s]
finished. total time: 0.067s
d:\MotoG\442>fastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.067s
d:\MotoG\442>fastboot.exe flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.104s]
writing 'fsg'...
OKAY [ 0.076s]
finished. total time: 0.181s
d:\MotoG\442>fastboot.exe reboot
rebooting...
finished. total time: 0.001s
Try using "mfastboot" it could maybe work... Just a thought.
Destr0y3r said:
Try using "mfastboot" it could maybe work... Just a thought.
Click to expand...
Click to collapse
I already tried it with no luck...if you look at getvar data you will see cid is 0xDEAD thats why i am worried.
Try to use another firmware using mfastboot manually and relock your boot loader
Sent from my Moto G using XDA Premium 4 mobile app
pfufle said:
Try to use another firmware using mfastboot manually and relock your boot loader
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried many firmware without luck, the problem is in the BL i see devices locked status 0, but the unlock command doesn't work.
You must be making a mistake...request for the unlock code again
Sent from my Moto G using XDA Premium 4 mobile app
pfufle said:
You must be making a mistake...request for the unlock code again
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is the message i've got after fastboot oem unlock "unlockcode"
(bootloader) fastboot oem unlock disabled!
FAILED (remote failure)
finished. total time: 0.025s
This is the story: the former owner tried to root the phone, as he said he unlocked the bootloader, then something went wrong. He tried to install CM, and he softbricked the phone. It has the IMEI but there is some problem with CID and UID as a look at the prompt from fastboot getvar all. Somehow the unlock commands doesnt work, and i ve got preflash vaildation faild errors, when i try to flash boot or recovery or system img. The phone wont boot if i turn it on it goes to bootloader.
Ask for the unlock code again
Sent from my Moto G using XDA Premium 4 mobile app
pfufle said:
Ask for the unlock code again
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried it last week, but if i enter the command fastboot oem get_unlock_data it won't post the unlock token.
Well I think you are the first person who has faced this problem...I think there is something wrong with the commands you are typing....
Sent from my Moto G using XDA Premium 4 mobile app
my theory
I think your gonna need to wipe the device filly like its partions and such. ThTs all I can think off
Found this http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html?m=1
Awesomeslayerg said:
I think your gonna need to wipe the device filly like its partions and such. ThTs all I can think off
Found this http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html?m=1
Click to expand...
Click to collapse
I was wondering if the former owner unlocked the bl than flashed a stock image with a bl which doesn't support unlock and that why I am getting 0xdead Cid and can't reopen bl...
Wipe simply everything from your phone and then restore the stock firmware
Sent from my XT1032 using XDA Premium 4 mobile app
randras83 said:
I was wondering if the former owner unlocked the bl than flashed a stock image with a bl which doesn't support unlock and that why I am getting 0xdead Cid and can't reopen bl...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2623587
Found this you could try this.
I came across a similar situation after writing an emmc image taken from one XT1032 to a second XT1032.
After rebooting, the second XT1032 (which was already unlocked) behaved just like your device (reported as LOCKED, and when trying to unlock, gave the 'fastboot oem unlock disabled!' error message).
Eventually, and with some trickery, I was able to resolve the issue by restoring the 'cid' and 'sp' partitions to their original state.
check device manager on windows and see if you have unknow devices on your phone and change adb from there
tal.aloni said:
I came across a similar situation after writing an emmc image taken from one XT1032 to a second XT1032.
After rebooting, the second XT1032 (which was already unlocked) behaved just like your device (reported as LOCKED, and when trying to unlock, gave the 'fastboot oem unlock disabled!' error message).
Eventually, and with some trickery, I was able to resolve the issue by restoring the 'cid' and 'sp' partitions to their original state.
Click to expand...
Click to collapse
It has been quite a while since you posted this, but I have the same problem where I overwrote the cid partition and I am unsure how to get it back. Any chance you remember this trickery?
Thanks,
Nathan
I have the same problem. Any fix?
ISSue XT0133
randras83 said:
I tried it last week, but if i enter the command fastboot oem get_unlock_data it won't post the unlock token.
Click to expand...
Click to collapse
same issue, i'm also facing bro any solutions?
Dear all,
I own a XT1541 and updated to Marhsmallow via OTA few weeks ago. I encountered some troubles with the performance. I also had the issue that a single app was attempted to be optimized on every boot. Therefore, I decided to reset it to factory settings. However, it seemed that this process failed (waited nearly for an hour to complete but nothing happened).
After rebooting then manually, I am stuck in a fastboot message
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from charger boot mode
CID Read Failure
Invalid CID status 0x69
I can access the device via my Linux using fastboot command. What do you propose to recover from my problem.
Thanks
IK1981 said:
Dear all,
I own a XT1541 and updated to Marhsmallow via OTA few weeks ago. I encountered some troubles with the performance. I also had the issue that a single app was attempted to be optimized on every boot. Therefore, I decided to reset it to factory settings. However, it seemed that this process failed (waited nearly for an hour to complete but nothing happened).
After rebooting then manually, I am stuck in a fastboot message
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from charger boot mode
CID Read Failure
Invalid CID status 0x69
I can access the device via my Linux using fastboot command. What do you propose to recover from my problem.
Thanks
Click to expand...
Click to collapse
Try flashing the factory image here are the instructions
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
bobby0724 said:
Try flashing the factory image here are the instructions
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Click to expand...
Click to collapse
Already tried this. Already fails at first command... When doing this for the first time, it takes up to one minute to get a response. When retrying, it fails immediately
Code:
~/Downloads/XT1541_OSPREY_RETEU_6.0_MPI24.65-33.1_cid7_subsidy-DEFAULT_CFC__v2.xml# fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 55.425
Try usuing my Motorola downgrade tool , or Motorola utility , created by me , to try and fix problems like this. Links can be found in the general section of Moto g 3 forums , or in Moto g 3 devdb. Therealduff1 is the username you are looking for . I am happy to try and help you with this !
therealduff1 said:
Try usuing my Motorola downgrade tool , or Motorola utility , created by me , to try and fix problems like this. Links can be found in the general section of Moto g 3 forums , or in Moto g 3 devdb. Therealduff1 is the username you are looking for . I am happy to try and help you with this !
Click to expand...
Click to collapse
Thanks for your help. Tried it with your tool but as far as I could see I land in the same troubles.
Code:
OSPREY_RETEU_6.0_MPI24.65-33_cid7_subsidy
please move all of the firmware files into the moto toolkit directory (the same folder containing toolkit.py)
Please make sure usb debugging is turned on in developer settings, then type 'done' into this promptdone
error: device '(null)' not found
Has your device successfully loaded bootloader mode ? please type 'yes' if it has successfully loadedyes
Press enter to confirm you would like to upgrade to android marshmallow ;)
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 55.795s
Partition table has been flashed
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 1.438s
Bootloader has been flashed
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.062s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.172s
boot logo has been flashed
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.530s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.093s
boot.img has been flashed
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.094s
Stock marshmallow recovery has now been flashed
target reported max download size of 268435456 bytes
sending 'system' (238438 KB)...
OKAY [ 7.500s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 15.891s
System part 1 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (238552 KB)...
OKAY [ 7.492s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 9.608s
System part 2 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (256695 KB)...
One thing that confuses me is the fact that the tool tells me that I shall turn on the USB debug mode. However, since Android does not boot any longer, I have no chance to do this in the Settings. Is there any way to enable this debug mode in another way?
Moto G3 is Bricked,
Device is Locked Status Code:0
XT1550
Tried recovery Mode gives error:
==========
Your Status didn't startup successfully. Use the Software Repair Assistant on Computer to repair your device.
==========
Tried Fastboot it says
C:\Users\admin\Downloads\ADB\ADB and Fastboot>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.048s
Please help.
radnam said:
Moto G3 is Bricked,
Device is Locked Status Code:0
XT1550
Tried recovery Mode gives error:
==========
Your Status didn't startup successfully. Use the Software Repair Assistant on Computer to repair your device.
==========
Tried Fastboot it says
C:\Users\admin\Downloads\ADB\ADB and Fastboot>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.048s
Please help.
Click to expand...
Click to collapse
Flash stock firmware from here : https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Download links and FAQ are present in that thread.
adityak1303 said:
Flash stock firmware from here : https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Download links and FAQ are present in that thread.
Click to expand...
Click to collapse
I have tired doing the steps given. However it gives the following error:
C:\Users\admin\Downloads\ADB and Fastboot\ADB and Fastboot>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.031s
C:\Users\admin\Downloads\ADB and Fastboot\ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.459s
C:\Users\admin\Downloads\ADB and Fastboot\ADB and Fastboot>astboot flash bootloader bootloader.img
'astboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\admin\Downloads\ADB and Fastboot\ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 1.424s
Just to be sure, you are running this in as an Administrator command window, correct?
It's bricked... Nothing is writing to the internal storage and everything is coming back FAILED. Seen a few of these recently, if it was a different error we might be able to do something but doing 'fastboot oem fb_mode_set' should never give an error.
acejavelin said:
Just to be sure, you are running this in as an Administrator command window, correct?
It's bricked... Nothing is writing to the internal storage and everything is coming back FAILED. Seen a few of these recently, if it was a different error we might be able to do something but doing 'fastboot oem fb_mode_set' should never give an error.
Click to expand...
Click to collapse
That's what I was wondering. And yes I am running Administrator Command Window.
I am just keeping my fingers crossed that someone can help me resolve the issue.
My story goes.
Had happy running TugaPower Rom
Decided to install MultiRom and Ubuntu.
Then after running for a week or so, decided to wipe and install TugaPower alone.
All has run well for a while. Decided to wipe and make a fresh install.
MultiRom I am unable to fully remove, even trying to replace with original TWRP.
When I try to flash the ROM, I get reported that this cant be installed as the model is . not bacon or A0001. error 7
I have edited the updater-script to not make a check on the model and it then installs.
When i reboot it goes straight back to the recovery!!!
I have tried reinstalling multirom and then flashing but again it keeps going to the recovery.
Ive tried to fastboot the original OS via https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541, but fastboot reports `FAILED (remote: Device not unlocked cannot flash or erase)`
(Full output at bottom)
The install all end with 1 and multirom could see the roms
ive tried extracting just the .img and flashing to get going
im at a loss, any help much appreciated
Code:
[email protected]:sudo fastboot oem unlock
...
OKAY [ 0.009s]
finished. total time: 0.009s
[email protected]:/home/steve/Downloads/cm# ./flash-all.sh
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.805s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 1.806s
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.011s]
writing 'sbl1'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.013s
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.004s]
writing 'dbi'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.006s
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.015s]
writing 'aboot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.017s
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.008s]
writing 'rpm'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.012s]
writing 'tz'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.015s
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.013s]
writing 'LOGO'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.015s
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.322s]
writing 'oppostanvbk'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.323s
target reported max download size of 1073741824 bytes
sending 'recovery' (9968 KB)...
OKAY [ 0.314s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.315s
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
sending 'boot' (7274 KB)...
OKAY [ 0.231s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.232s
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
erasing 'userdata'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.000s
rebooting...
finished. total time: 0.050s
Boot the phone into fastboot mode and open cmd with administrative rights and go into the adb platform tools folder and enter in cmd fastboot OEM -device info
kallum7 said:
Boot the phone into fastboot mode and open cmd with administrative rights and go into the adb platform tools folder and enter in cmd fastboot OEM -device info
Click to expand...
Click to collapse
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.016s]
finished. total time: 0.016s
now run script
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Windows\system32>fastboot boot C:\Users\Steve\Downloads\twrp-3.2.3-0-bacon.img
downloading 'boot.img'...
OKAY [ 0.438s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.438s
C:\Windows\system32>fastboot oem unlock
...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Windows\system32>fastboot boot C:\Users\Steve\Downloads\twrp-3.2.3-0-bacon.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.438s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.438s
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.016s]
finished. total time: 0.016s
Try another USB micro cable
Thank you for your reply.
I have tried two other cables I have and still having the same issues
Are you using Linux or windows
kallum7 said:
Are you using Linux or windows
Click to expand...
Click to collapse
I have both available,
I am trying each OS at each new try
Ran all three of the files on here to get the triggers to true / true
https://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I then ran `fastboot boot twrp.img`
This gave me twrp and i then installed a rom as normal...
im back up and running
thanks for all your patience and help
stevieag said:
Ran all three of the files on here to get the triggers to true / true
https://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I then ran `fastboot boot twrp.img`
This gave me twrp and i then installed a rom as normal...
im back up and running
thanks for all your patience and help
Click to expand...
Click to collapse
Im having problems again..
OTA lineage update came up..
i clicked to install.
Phone restarted and immediately went to the multirom twrp screen.
I have had this in the past and have needed to install from this screen but i couldnt find the file to install
So on phone restart it loops back to the multirom twrp
I can still adb and fastboot see below
Code:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
on fastboot boot twrp.img
it seems to restart but sits on fastboot screen
story:
on fastboot
send command
fastboot screen goes brighter
Any ideas
I have tried windows and linux plus 2 cables
What would be ideal would to completely clear multirom from my phone and get back to stock or stock twrp so i can flash as normal
stevieag said:
Im having problems again..
OTA lineage update came up..
i clicked to install.
Phone restarted and immediately went to the multirom twrp screen.
I have had this in the past and have needed to install from this screen but i couldnt find the file to install
So on phone restart it loops back to the multirom twrp
I can still adb and fastboot see below
Code:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
on fastboot boot twrp.img
it seems to restart but sits on fastboot screen
story:
on fastboot
send command
fastboot screen goes brighter
Any ideas
I have tried windows and linux plus 2 cables
What would be ideal would to completely clear multirom from my phone and get back to stock or stock twrp so i can flash as normal
Click to expand...
Click to collapse
sorted
https://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Ultimate fix
Right, i ended with a boot loop i couldnt sort
so
i downloaded - cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot.zip (to big for upload)
This contains all the files you need including os
Once in fastboot
volume up and power or in recovery
Code:
adb reboot bootloader
In windows in a terminal (search next to start menu for cmd, right click on the pop up cmd and choose open as admin)
Run each of these
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64G.img
fastboot reboot
THIS IS FOR 64GB ONLY with 16GB change userdata_64.img to the file userdata.img
In Linux open terminal, drop to root
Code:
sudo su -
you can then run above files or run flash-radio.sh
Code:
./flash-radio.sh
weirly may still need sudo!!!
This will install the os etc and you are back to stock (although old)
Now you can install twrp as normal
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot
here you should be back to normal twrp recovery
Copy over your ROM and Gapps
Install as normal twrp and done
im now on pie with 3.2.2 twrp and gapps 9
This installed ROMs that were complaining of not the right model, error 7, error 255 ........ and on
All sorted, in fact ive installed 3 different roms now without fails