Related
I flashed HPSGill's rom on Friday which is Sense 5 themed, It didn't boot up. So I went back to recovery, wiped everything down, and proceeded to flash the stock ROM. The RUU installation failed, giving me a 150 Error. I have used the same RUU for a year now. I then tried running some fastboot commands but most of them give me "REMOTE: NOT ALLOWED".
The phone goes into fastboot mode as when I execute "fastboot devices" i see my phone serial number on the command line. I can't however access adb. On removing the cable it takes me to the bootloader white screen, only now, the options for reboot, reset factory settings, recovery, etc, are not visible.
It just shows me my phone information, bootloader as relocked, and RUU highlighted. I have tried flashing the RUU multiple times, after each flash attempt, all partitions, except the userdata partition shows userdata FAIL-PU, which as I understand is the partition update failing, bootloader shows - BYPASSED. I have also tried downloading the same RUU just in case somehow the one I had was corrupted. But same result.
HTC service center says since I have rooted my phone, I will have to pay 6000 rs. for a 7000rs. phone to get it repaired. Is there any way back from this ? I have sent it to the service center and will get it back tomorrow, So I can only post screenshots if needed tomorrow. I have scoured the internet for the solution and I have read some odd success stories, but none of them for the explorer, mostly for desires. Any help appreciated.
I will be trying bortak's guide in the meanwhile which is again for htc desire.
Well from what I get so far you're stuck in the middle of a bad RUU flash, idea is you need to complete an RUU flash before you can do anything else, from this I get only try flashing several times this RUU or try with some another RUU else, if there is no fastboot this is hard to be fixed, try sending pm to @legen_dary , he experimented for a while to find some s-off way, so he should know a little bit more about this stuff. I'll continue the search, if find something will share, you also, do share what have you discovered, and if something works what is it.
shortyoko said:
Well from what I get so far you're stuck in the middle of a bad RUU flash, idea is you need to complete an RUU flash before you can do anything else, from this I get only try flashing several times this RUU or try with some another RUU else, if there is no fastboot this is hard to be fixed, try sending pm to @legen_dary , he experimented for a while to find some s-off way, so he should know a little bit more about this stuff. I'll continue the search, if find something will share, you also, do share what have you discovered, and if something works what is it.
Click to expand...
Click to collapse
Thanks for the reply. As I mentioned, the moment i connect the phone via the USB cable, it automatically goes into fastboot mode as when i run "fastboot devices", my device shows up. So I'm considering, not all hope is lost. I have to get to work, will be getting my phone back today, will experiment some and get back here at night.
forgot to mention a couple of things.
1. the bootloader shows relocked. On running the fastboot flash unlocktoken Unlock_code.bin, the command completes successfully but the bootloader still shows relocked. And because it constantly shows relocked, I'm not able to install a custom recovery as well.
2. tried putting the rom in the RUU on sdcard and renaming it as PBsomething.zip. but it wont read the sd card. So flashed it manually via fastboot flash zip zipname.zip runs upto a certain point then gives me something like this
RUU: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" So I tried reflashing it, but keeps giving the same error.
So since the sd card is not being read at all, I guess bortak's method of creating a goldcard goes out the window.
Hmmm.. This is the second such case i've seen..
Have you tried getting the unlock token again from htcdev??
Also, try updating your hboot version...
Or, get any hboot from an ruu, and do a
Code:
fastboot boot hboot.img
If it wrks, you'll atleast be able to unlock the bootloader, and put a recovery on it..
If, however, your original bootloader remains locked, then you wont be able to access the recovery as well..
In fact, it wouldnt go past the hboot...
ғг๏๓ ҭђє ғเรђ™
---------- Post added at 08:19 AM ---------- Previous post was at 08:15 AM ----------
legen_dary said:
hmmm.. This is the second such case i've seen..
Have you tried getting the unlock token again from htcdev??
Also, try updating your hboot version...
Or, get any hboot from an ruu, and do a
Code:
fastboot boot hboot.img
if it wrks, you'll atleast be able to unlock the bootloader, and put a recovery on it..
If, however, your original bootloader remains locked, then you wont be able to access the recovery as well..
In fact, it wouldnt go past the hboot...
Edit : The correct filename is pj03img.zip(or something)..
When the phone first starts in the hboot, you should see a series of filenames, along with "not found" errors.. If you do, then it does scan the sdcard...
ғг๏๓ ҭђє ғเรђ™
Click to expand...
Click to collapse
ғг๏๓ ҭђє ғเรђ™
legen_dary said:
Hmmm.. This is the second such case i've seen..
Have you tried getting the unlock token again from htcdev??
Also, try updating your hboot version...
Or, get any hboot from an ruu, and do a
Code:
fastboot boot hboot.img
If it wrks, you'll atleast be able to unlock the bootloader, and put a recovery on it..
If, however, your original bootloader remains locked, then you wont be able to access the recovery as well..
In fact, it wouldnt go past the hboot...
ғг๏๓ ҭђє ғเรђ™
---------- Post added at 08:19 AM ---------- Previous post was at 08:15 AM ----------
ғг๏๓ ҭђє ғเรђ™
Click to expand...
Click to collapse
Thanks. will try it out and get back to you but after about 12 hours, I am yet to get back my phone and gotta get to work.
burnt nand
your nand is burnt.you should use cute_prince's method.
Steps of solution
1.flash twrp via fastboot -------fastboot flash recovery twrp.img
2.boot recovery via fastboot------fastboot boot twrp.img
3.apply cute prince method -------http://forum.xda-developers.com/showpost.php?p=36868966&postcount=2367
4.re lock bootloader via fastboot ------fastboot oem lock
5.run compatible ruu
6[optional ] unlock bootloader and Flash favourite rom
juristokrat said:
your nand is burnt.you should use cute_prince's method.
Steps of solution
1.flash twrp via fastboot -------fastboot flash recovery twrp.img
2.boot recovery via fastboot------fastboot boot twrp.img
3.apply cute prince method -------http://forum.xda-developers.com/showpost.php?p=36868966&postcount=2367
4.re lock bootloader via fastboot ------fastboot oem lock
5.run compatible ruu
6[optional ] unlock bootloader and Flash favourite rom
Click to expand...
Click to collapse
He's unable to unlock the bootloader so it's impossible to flash a custom recovery
You can't use fastboot boot or fastboot flash with a locked bootloader. Can you get into HBOOT mode by holding volume down and power while switching on the device? Or does it go straight into FASTBOOT mode?
i tried
1) unlocking bootloader, and now its unlocked.
2) fastboot getvar all gives me
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.03.0000
(bootloader) version-baseband: 1.11.82.17
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.720.3
(bootloader) serialno: ********
(bootloader) imei: *******
(bootloader) product: pico
(bootloader) platform: HBOOT-7225A
(bootloader) modelid: PJ0310000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3673mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 30d3dcb5
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.032s
3) fastboot oem boot boots up the phone and is now stuck in a bootloop. gives me the htc jingle and restarts. tried pulling the battery and volume down + power combination to get to the hboot menu, but brings me back to the black htc screen with 4 triangles. At least there is some progress. Now I somehow just need to get that menu back that comes up after the volume down + power combination.
4) tried fastboot oem resetRUUflag and it gave me this -
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
5) tried fastboot boot hboot.img with the boot.img from the RUU
it gave me -
creating boot image...
creating boot image - 788480 bytes
downloading 'boot.img'...
OKAY [ 0.263s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 0.300s
Can you get into recovery?
The boot.img file is the kernel bro.. Not the hboot..
The file you're looking for is hboot -something-something.img
ғг๏๓ ҭђє ғเรђ™
@sachin thomas - No I can't get into recovery
@legen_dary - hboot_1.03.0000_30d3dcb5_1129_signed this one right ? i just renamed it to hboot.img to avoid typing or copying the whole name
EDIT : i find this flag out of place . (bootloader) boot-mode: RUU. should it be RUU ? i think this is the one causing all the problem, though of course i may be wrong.
salil_1337 said:
@sachin thomas - No I can't get into recovery
@legen_dary - hboot_1.03.0000_30d3dcb5_1129_signed this one right ? i just renamed it to hboot.img to avoid typing or copying the whole name
EDIT : i find this flag out of place . (bootloader) boot-mode: RUU. should it be RUU ? i think this is the one causing all the problem, though of course i may be wrong.
Click to expand...
Click to collapse
You can't boot from a signed HBOOT image because it's a plain binary file and not an android boot image. As you have unlocked the bootloader try fastboot boot with any recovery.img file (CWM or TWRP)
Sachin Thomas said:
You can't boot from a signed HBOOT image because it's a plain binary file and not an android boot image. As you have unlocked the bootloader try fastboot boot with any recovery.img file (CWM or TWRP)
Click to expand...
Click to collapse
EXCELLENT !
did this -
I:\Android Rooting\Flash>fastboot boot recovery-clockwork-5.0.2.8-pico.img
downloading 'boot.img'...
OKAY [ 0.810s]
booting...
OKAY [ 0.014s]
finished. total time: 0.834s
and now I am in CWM recovery screen.
EDIT 1: wiped all partitions.
EDIT 2 : rebooted the phone to check if it let me into the hboot menu, but it comes back to the black htc screen with 4 exclamation marks
salil_1337 said:
EXCELLENT !
did this -
I:\Android Rooting\Flash>fastboot boot recovery-clockwork-5.0.2.8-pico.img
downloading 'boot.img'...
OKAY [ 0.810s]
booting...
OKAY [ 0.014s]
finished. total time: 0.834s
and now I am in CWM recovery screen.
EDIT : wiped all partitions.
Click to expand...
Click to collapse
To be on the safer side do cute_prince's nand recovery procedure as juristokrat suggested
Sachin Thomas said:
To be on the safer side do cute_prince's nand recovery procedure as juristokrat suggested
Click to expand...
Click to collapse
i did that when i got my nand burned after installing cm10 beta 6. But AFAIK and as far as I understand, i need to place the flash_erase file into system/xbin. I am right now stuck in recovery. How am I supposed to do it from there ? is there a flashable zip for it which will run the commands via recovery ?
EDIT : this is FAR better than i expected. since I'm in recovery, adb devices spits this out -
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH1BJVN07184 recovery
salil_1337 said:
i did that when i got my nand burned after installing cm10 beta 6. But AFAIK and as far as I understand, i need to place the flash_erase file into system/xbin. I am right now stuck in recovery. How am I supposed to do it from there ? is there a flashable zip for it which will run the commands via recovery ?
Click to expand...
Click to collapse
Mount your SD card in recovery and place the file in the root of the SD card. Now, if you have TWRP you can use its file manager to move it into system/xbin and set permissions to 755
If you have CWM you can type the following in adb shell:
cd /
mv /sdcard/flash_erase /system/xbin
cd system/xbin
chmod 755 flash_erase
Click to expand...
Click to collapse
Then find a newer RUU and run it
Sachin Thomas said:
Mount your SD card in recovery and place the file in the root of the SD card. Now, if you have TWRP you can use its file manager to move it into system/xbin and set permissions to 755
If you have CWM you can type the following in adb shell:
Click to expand...
Click to collapse
OK. booted via twrp, copied file from sd card, but there seems to be no xbin folder in system
EDIT : ran it directly from the sd card via the terminal in twrp, it ran without errors. rebooted the phone, still comes up to the black htc screen
salil_1337 said:
OK. booted via twrp, copied file from sd card, but there seems to be no xbin folder in system
Click to expand...
Click to collapse
Mount system
Sachin Thomas said:
Mount system
Click to expand...
Click to collapse
after mounting system, its still showing only one folder in system . lost+found. nothing else.
ran it directly from the sd card via the terminal in twrp, it ran without errors. rebooted the phone, still comes up to the black htc screen
salil_1337 said:
after mounting system, its still showing only one folder in system . lost+found. nothing else.
ran it directly from the sd card via the terminal in twrp, it ran without errors. rebooted the phone, still comes up to the black htc screen
Click to expand...
Click to collapse
Oh, the xbin folder should have got deleted when you formatted system. I don't think you can't get rid of the HTC screen without successfully flashing an RUU. Our aim is to get rid of bad blocks which prevents the RUU from getting flashed
Are you sure that it ran without errors? Move it into /system and change permission to 755 and re-run it before attempting to flash another RUU
It all started yesterday where i was trying to update (InsertCoin) which for some reason made my phone shut down mid-way through the installation process...
I had to reboot my phone back into recovery to wipe system/cache/data to reinstall...For some reason this wiped/damaged everything but the bootloader ofc.
(Bye go all my pictures, whatsapp conversations etc...)
This made me not being able to boot into my recovery aswell
I still can't get back into my recovery, and i've tried flashing the recovery over and over again via fastboot flash recovery twrp.img
When i try to flash the recovery, it succeeds but when i try to boot into it, it blinks the splash screen with odd intervals, i dont know if this means that its trying over and over again...I'm sort of desperate here...any help?
sidenote here: I'm in linux
you should've updated firmware to hboot 2.22 needed for IC, then you need to install the latest recovery 2.7.1.1 from twrp website
twrp here: http://techerrata.com/browse/twrp2/m4ul
new firmware here :http://forum.xda-developers.com/showthread.php?t=2759131
I have not updated it, will go and do that now,
Code:
[email protected]:/media/leon/*censor*/Android/ROMS/Millium$ sudo fastboot flash zip firmware.zip
[sudo] password for leon:
target reported max download size of 800227328 bytes
sending 'zip' (19549 KB)...
OKAY [ 2.466s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 4.305s
Right.....!?
I really don't want to reboot to bootloader at the moment...since the update failed...
Apparently i am S-ON and therefor need to obtain s-off, but i don't have an android system installed..how
s-off required to flash firmware or if s-on, bootloader needs to be re-locked, sorry i assumed you knew that! maybe create a signature giving details of your device for future, it does help.
If you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
Code:
FAILED (remote: 12 signature verify fail)
This ahappens when flashing the firmware
*edit: I have fixed that, but i cannot flash the 2.22 included y you because it has a different modelid, presumably because my m4 isn't the at&t variant.
Will this work?
`leon said:
Code:
FAILED (remote: 12 signature verify fail)
This ahappens when flashing the firmware
Click to expand...
Click to collapse
not work ?? ok, then you will need to s-off the device, unlock first,you need SUPERCID also
Braddison said:
not work ?? ok, then you will need to s-off the device, unlock first
Click to expand...
Click to collapse
It did, sorry, didnt edit the post quick enough
`leon said:
Code:
FAILED (remote: 12 signature verify fail)
*edit: I have fixed that, but i cannot flash the 2.22 included y you because it has a different modelid, presumably because my m4 isn't the at&t variant.
Will this work?
Click to expand...
Click to collapse
no that firmware will not update everything that is required, use the firmware zip in the link i gave previously.
you need to change your cid to supercid,,,,very simple to do
Enter the command "fastboot oem readcid". Make a note of your original CID.
enter the command "fastboot oem writecid 11111111" make sure it is 8 ones (1)
enter the command "fastboot read cid" [it should confirm your CID is 11111111]
Braddison said:
no that firmware will not update everything that is required, use the firmware zip in the link i gave previously.
you need to change your cid to supercid,,,,very simple to do
Enter the command "fastboot oem readcid". Make a note of your original CID.
enter the command "fastboot oem writecid 11111111" make sure it is 8 ones (1)
enter the command "fastboot read cid" [it should confirm your CID is 11111111]
Click to expand...
Click to collapse
Yeah, i just tried that 5 minutes ago, though...:
Code:
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
Gosh...my device doesn't like me..
oh, wait, don't i have to unlock bootloader?
i'll try that now
OMG IM IN RECOVERY
cant seem to do anything with my data partition, same goes for internal storage
well you've done everything that i done when i tried out Insertcoin rom for a few days and never had any of your issues. so not sure whats going on.
- unlocked bootloader
- get s-off
- get supercid
- update firmware
- get latest twrp recoverry
- install Insert Coin
use the fix miniwhooper posted on her firmware thread ....Flash stock recovery and factory reset from boot loader. It will fix you /data partition.. then flash custom recovery and it should be fixed
`leon said:
Yeah, i just tried that 5 minutes ago, though...:
Code:
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
Gosh...my device doesn't like me..
oh, wait, don't i have to unlock bootloader?
i'll try that now
OMG IM IN RECOVERY
cant seem to do anything with my data partition, same goes for internal storage
Click to expand...
Click to collapse
Make sure you are in the folder your rom zip is located.
Run the command...
adb push filename.zip /sdcard
Wait around 10 minutes as it will not give you progress
go back to TWRP main page and install, choose SDcard and the zip file you just uploaded should be there.
hello @AnGrY sCoTsMaN
i have the exact same problem but i flashed cm.12.1 cant boot in recovery or flash anything using adb
hboot os 2.22 it says unlocked but it seems not
can you please help me out
Edit: problem solved without doing anything
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
GriechischerYoghurt said:
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
Click to expand...
Click to collapse
Hi
Trying to help.
Your device might be tampered as the "fastboot oem device-info" result shows.
Follow the steps and see if it helps (all commands below are to be entered without quotes)
1. Download latest cm13 nightly or the cm12.1-snapshot and extract the "boot.img" from it.
2. Connect the phone in fastboot mode and check connection by "fastboot devices."
3. Enter the command "fastboot flash recovery boot.img" (the one extracted above).
4. Then enter "fastboot format cache".
5. After the boot.img is flashed, enter "fastboot reboot" to reboot the phone and the let the phone boot fully to homescreen. If stuck on bootscreen( i assume rom is not tampered with) try entering stock recovery and clear cache and dalvik-cache.
6. Now again enter bootloader by reboot or using combo and check connection by "fastboot devices".
7. Now enter "fastboot oem unlock".
8. Now check "fastboot oem device-info".
It should be unlocked like:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
Please do reply if it helped.
e1forall said:
Hi
Trying to help.
Your device might be tampered as the "fastboot oem device-info" result shows.
Follow the steps and see if it helps (all commands below are to be entered without quotes)
1. Download latest cm13 nightly or the cm12.1-snapshot and extract the "boot.img" from it.
2. Connect the phone in fastboot mode and check connection by "fastboot devices."
3. Enter the command "fastboot flash recovery boot.img" (the one extracted above).
4. Then enter "fastboot format cache".
5. After the boot.img is flashed, enter "fastboot reboot" to reboot the phone and the let the phone boot fully to homescreen. If stuck on bootscreen( i assume rom is not tampered with) try entering stock recovery and clear cache and dalvik-cache.
6. Now again enter bootloader by reboot or using combo and check connection by "fastboot devices".
7. Now enter "fastboot oem unlock".
8. Now check "fastboot oem device-info".
It should be unlocked like:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
Please do reply if it helped.
Click to expand...
Click to collapse
Thanks for the reply! I tried the steps but sadly it did not work.
I downloaded cm13, extracted it to my fastboot.exe folder and did enter the commands.
"c:\unlock>fastboot devices
9c50d771 fastboot"
So my device does show up which means drivers are properly installed aren't they?
"c:\unlock>fastboot flash recovery boot.img
target reported max download size of 1073741824 bytes
sending 'recovery' (7254 KB)...
OKAY [ 0.232s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.254s"
There is the error message again, I can't flash the stock recovery becaue the bootloader is not unlocked I think but I don't know what else to do.
then:
"c:\unlock>fastboot format cache
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.068s"
I did that too, I can't tell if it formatted cache or not, I dunnoooo
and then i entered the two commands to unlock and then check the bootloader:
"c:\unlock>fastboot reboot
rebooting...
finished. total time: 0.005s
c:\unlock>fastboot devices
9c50d771 fastboot
c:\unlock>fastboot oem unlock
...
OKAY [ 10.102s]
finished. total time: 10.106s
c:\unlock>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.013s]
finished. total time: 0.014s"
sooooo it sadly did not work
GriechischerYoghurt said:
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
Click to expand...
Click to collapse
Hi I had the same problem a couple of weeks ago, if you're able to boot into a custom recovery, flash this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 it's an alternative way of getting bootloader unlocked. Hope it helps
smarttmd said:
Hi I had the same problem a couple of weeks ago, if you're able to boot into a custom recovery, flash this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 it's an alternative way of getting bootloader unlocked. Hope it helps
Click to expand...
Click to collapse
I have looked into that but how do I flash it?
I tried the commands "fastboot boot -image file-" but it says i cant do that cause once again the bootloader is locked
then there is "fastboot boot recovery -image file-" but then it says " cant find directory" or something like that..
could you please give me step by stepe instruction how you solved the issue?
I am getting very frustrated here.. beginning to think it's unsolveable.
sadly i can't boot into a custom recovery :C
GriechischerYoghurt said:
I have looked into that but how do I flash it?
I tried the commands "fastboot boot -image file-" but it says i cant do that cause once again the bootloader is locked
then there is "fastboot boot recovery -image file-" but then it says " cant find directory" or something like that..
could you please give me step by stepe instruction how you solved the issue?
I am getting very frustrated here.. beginning to think it's unsolveable.
sadly i can't boot into a custom recovery :C
Click to expand...
Click to collapse
You flash this zip in a custom recovery like any other mod. Luckily for me I still had my twrp installed so I managed to do it, but you should be able to temporarily boot from it. Is your custom recovery image in the active directory?
smarttmd said:
You flash this zip in a custom recovery like any other mod. Luckily for me I still had my twrp installed so I managed to do it, but you should be able to temporarily boot from it. Is your custom recovery image in the active directory?
Click to expand...
Click to collapse
yes it's in the directory from where i start command prompt
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
meekrawb said:
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
Click to expand...
Click to collapse
I tried that too. Here i
GriechischerYoghurt said:
I tried that too. Here i
Click to expand...
Click to collapse
Rough spot to be in then. Hopefully someone has some other ideas for you to try. Good luck bud.
meekrawb said:
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
Click to expand...
Click to collapse
I tried that too.. Spoiler.. it did not work.
The drivers seem to work. I have my windows 10 set to testmode. The OPO is recognized by the Msm8974DownloadTool,, when I click on "start" the bar moves to 3/4 of the bar but then something happens and I get a "sahara" message". I tried it maybe over 10 times now. Sometimes it shows me the message immediately. Sometimes the green bar gets to 1/4 of the bar and then the "sahara" message. But sometimes the bar gets to 4/4 one time and then it says "(somethinsomething)usb(somethingsomething in chinese i guess)" and thats it. Only bootloop as a result. Maaaaan this is getting annoying.
I think where something might have gone wrong was trying to use a toolkit. Try this:
Download latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Scroll down to #8 and follow the instructions to flash all of the images using fastboot. Hopefully, you will be able to boot the phone after that. Good luck!
GriechischerYoghurt said:
I tried that too.. Spoiler.. it did not work.
The drivers seem to work. I have my windows 10 set to testmode. The OPO is recognized by the Msm8974DownloadTool,, when I click on "start" the bar moves to 3/4 of the bar but then something happens and I get a "sahara" message". I tried it maybe over 10 times now. Sometimes it shows me the message immediately. Sometimes the green bar gets to 1/4 of the bar and then the "sahara" message. But sometimes the bar gets to 4/4 one time and then it says "(somethinsomething)usb(somethingsomething in chinese i guess)" and thats it. Only bootloop as a result. Maaaaan this is getting annoying.
Click to expand...
Click to collapse
I think the last time I used the ColorOS tool was on Windows 7. Windows 8/10 seems to be a real nightmare.
ryanmat said:
I think where something might have gone wrong was trying to use a toolkit. Try this:
Download latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Scroll down to #8 and follow the instructions to flash all of the images using fastboot. Hopefully, you will be able to boot the phone after that. Good luck!
Click to expand...
Click to collapse
Thanks for the reply and trying to help! but as I stated in the title my bootloader is LOCKED so i can't write anything to it. The guide of Heisenberg states clearly "Prerequisites: unlocked bootloader." so I knew it would not work but I tried it anyway.. sadly it did not work.. this is what it's giving me:
"C:\Users\Abdulla\Desktop\cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18>fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.804s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 1.804s
C:\Users\Abdulla\Desktop\cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18>"
funny thing is, it's "only" a softbrick but behaves like a hardbrick. I can't do anything and I don't know what to do at this point.
meekrawb said:
I think the last time I used the ColorOS tool was on Windows 7. Windows 8/10 seems to be a real nightmare.
Click to expand...
Click to collapse
I will try the ColorOS hardbrick method on a virtual XP machine and report back.
I tried it on a virtual XP machine but i can't get to mount the OPO, i get this error message.. now the first sentence is german and its says " the usb device Qualcomm CDMA Technologies MSM QHSUSB__BULK could not be mounted on the virtual mashine windows xp."
"Das USB-Gerät Qualcomm CDMA Technologies MSM QHSUSB__BULK konnte nicht an die virtuelle Maschine windows xp gebunden werden.
USB device 'Qualcomm CDMA Technologies MSM QHSUSB__BULK' with UUID {cdedf1ad-9235-40ef-80cf-efc72ba7678c} is busy with a previous request. Please try again later."
I don't even know if it's worth the effort trying to find a XP system and try it.. my hopes that it would work are very low at this point.. please let me know if you know a solution to this nightmare.
GriechischerYoghurt said:
I tried it on a virtual XP machine but i can't get to mount the OPO, i get this error message.. now the first sentence is german and its says " the usb device Qualcomm CDMA Technologies MSM QHSUSB__BULK could not be mounted on the virtual mashine windows xp."
"Das USB-Gerät Qualcomm CDMA Technologies MSM QHSUSB__BULK konnte nicht an die virtuelle Maschine windows xp gebunden werden.
USB device 'Qualcomm CDMA Technologies MSM QHSUSB__BULK' with UUID {cdedf1ad-9235-40ef-80cf-efc72ba7678c} is busy with a previous request. Please try again later."
I don't even know if it's worth the effort trying to find a XP system and try it.. my hopes that it would work are very low at this point.. please let me know if you know a solution to this nightmare.
Click to expand...
Click to collapse
When you do a fastboot oem unlock does it reboot you back into recovery?
I used HighOnAndroid's guide to unlock bootloader, flash a custom recovery, and root.
Tutorial Video
https://www.youtube.com/watch?v=vPv2DYnH3S8&index=9&list=PLB86F041EAFE4F3E5
Step-By-Step and Downloads
http://highonandroid.com/android-smartphones/how-to-root-oneplus-one/
Why don't you flash firmware in unlocked bootloader, if possible ( please refer in the forum, as i think there's a way to flash firmware and then you can unlock bootloader )
Go to an independent repair shop. They have the equipment to flash on the motherboard.
Hi everyone,
I hope someone can. Help. Unfortunately I flashed a bad firmware and therefore have the problem, that download mode doesn't work (power button + vol down --> gets to the dark screen with htc logo but then goes completely off) AND bootloader also doesn't work (power + vol up --> gets to white screen with green HTC logo but also goes completely off)! Any chance to get my A9 back to life? Any ideas? Thanks!
Original cid/mid
cid: HTC__034
mid: 2PQ910000
Now on super cid, s-off
SpeziesTR said:
Hi everyone,
I hope someone can. Help. Unfortunately I flashed a bad firmware and therefore have the problem, that download mode doesn't work (power button + vol down --> gets to the dark screen with htc logo but then goes completely off) AND bootloader also doesn't work (power + vol up --> gets to white screen with green HTC logo but also goes completely off)! Any chance to get my A9 back to life? Any ideas? Thanks!
Original cid/mid
cid: HTC__034
mid: 2PQ910000
Now on super cid, s-off
Click to expand...
Click to collapse
You flash which version of firmware? A9 original version of what? now you can into bootloader mode?
Hi thanks for answering. I flashed 1.57.617.20 firmware, but saw too late thats not for my model...
I cannot enter bootloader. When I press Power + Vol up, white screen and green HTC logo shows for 1-2 seconds and then the phone turns off completely...
SpeziesTR said:
Hi thanks for answering. I flashed 1.57.617.20 firmware, but saw too late thats not for my model...
I cannot enter bootloader. When I press Power + Vol up, white screen and green HTC logo shows for 1-2 seconds and then the phone turns off completely...
Click to expand...
Click to collapse
When you at the "dark screen with htc logo" . enter cmd command "fastboot reboot-bootloader" can you into bootloader mode?
Hi, the dark screen is also only there for 1-2 seconds, then device turns off again...
SpeziesTR said:
Hi, the dark screen is also only there for 1-2 seconds, then device turns off again...
Click to expand...
Click to collapse
You need to flash 1.56.401.70 of aboot_signed.img & hosd_signed.img.but this must be in bootloader mode .
A9_1.56.401.70.rar
HTC SYNC adb tools
Code:
fastboot flash aboot aboot_signed.img
fastboot flash hosd hosd_signed.img
fastboot reboot
Now unable into bootloader mode is the biggest problem.
@ nenebear: Thanks for your help so far!
Has anyone else a clue how to start into bootloader?
i have almost the same problem. my screen is black all the way but all the buttons work and i can hear it boot but the screen does not turn on
I managed to get into bootloader and from there into recovery. I had to press vol up + vol down + power so the device would boot into bootloader. Very strange as this is not the normal combination. I restored my previous image, it will boot but is somehow slow and sluggish.
Nevertheless I did flash
fastboot flash aboot aboot_signed.img
fastboot flash hosd hosd_signed.img
fastboot reboot
but I'm still not able to go to download mode. Furthermore beeing in bootloader reading basic information is not possible. For example:
...\HTC One A9\mini-sdk>fastboot devices
HT******** fastboot
...\HTC One A9\mini-sdk>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x29b000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc6000000
(bootloader) serialno:HT********
all:
finished. total time: 0.080s
...\HTC One A9\mini-sdk>fastboot oem readcid
...
FAILED (remote: unknown command)
finished. total time: 0.004s
...\HTC One A9\mini-sdk>fastboot oem readmid
...
FAILED (remote: unknown command)
finished. total time: 0.011s
Anyone a clue how to fix my A9 completely?
Hi,
i just tried to flash system.img (which I decrypted from 1.56.401.70 ROM.zip) but unfortunately got the following error.
Code:
fastboot flash system system.img
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
htc_fastboot finished. total time: 134.464s
Flashing Boot.img, aboot.img etc. is working....
Has someone a clue?
I fixed the problem. I flashed firmware and rom from 1.27.401.5. After that download mode was working again and I could flash 1.56.401.70 without a problem.
Now I'm on Icanas ROM and my A9 is working better than ever...
I did the same flashed a bad firmware. I can access bootloader but not download mode. I have restored a backup I had in twrp so I am running a rooted stock rom but I still can't update my phone thru RUU or Download mode. I have tried flashing the 2p9qimg ( firmware img/ zip ) thru fastboot thru bootloader but no go. All I want to do is flash the correct file so I can access download mode
S-Off
At&T converted to Unlocked
CID & MID changed
nenebear said:
You need to flash 1.56.401.70 of aboot_signed.img & hosd_signed.img.but this must be in bootloader mode .
A9_1.56.401.70.rar
HTC SYNC adb tools
Code:
fastboot flash aboot aboot_signed.img
fastboot flash hosd hosd_signed.img
fastboot reboot
Click to expand...
Click to collapse
which img files do I need to flash if I'm on 1.12.617.6 S- off US Unlocked converted from S-On At&t. I can't get into download mode, it turns off after the HTC logo with black background. Bootloader, recovery and my phone work though.
Nevermind figured it out! =)
Good day guys,
This is my first post in xda, and i'm a little bit nervous. and please bear with my english and i am a noob to some terms too. anyway, my unit is htc one a9. it was sent to me by my brother here in philippines. it is a sprint htc and i think it is a cdma with a sim slot and memory on the side. after reading some of your topics in some forums, i manage to unlock the the network. i can make outgoing and incoming calls and sms. but GPRS is disconnected. i then found another topic by jianC on how to Convert Sprint/Boost HTC One A9 to Dev Unlock. for it says that it can solve No mobile data (but have voice/sms) on sprint firmware after sim unlock. i followed the instructions but unfortunately it brick my phone. i flashed the 2PQ9IMG_HIA_AERO_UL_M60_SENSE7GP_ATT_NA_Gen_Unlock_1.12.617.6_signed.zip, to my phone. My old firmware was 2PQ9IMG_HIA_AERO[email protected]51002_15.00_F_CNV_CNV_HIAE_SPCS_1.15_003_release_453002_signed.zip. Now my problem is that i can get in to bootloader mode by pressing power+vol up+vol down together which is awkward.......but i cannot get in to download mode and recovery mode. the phone can still display the htc logo but 15 seconds later it shutsdown. i tried your advice to type fastboot erase system but it says FAILED<remote:device is locked. cannot erase. But my phone is Bootloader Unlocked and S-Off from sunshine. CID/MID (SPCS_001/2PQ93000) before. I change it to (11111111/2PQ912000) after. Then i tried to flash. I really don't know where to start until i found this forum. I hope somebody could help me in this problem i have.
Thanks and sincerely yours,
kramned
¡ I need help please !
I have a HTC Desire 10 pro (From Aliexpress, yes warranty avoid), it was working fine (more than a year) until a few days ago. One morning I took it and it was off but the notification led was not on despite charging. I tried to turn it on and enter to recovery but it was not responding. I decided to open the phone to remove the battery and verify that it was not damaged. Mysteriously the battery was in good condition, and once I removed it and plugged it back in, the phone responded again when connecting the USB and the charger.
But there is a problem, when the system is going to boot, after showing the HTC logo, the phone turns off together with the notification led and returns to the state in which I found it at first.
I removed and placed the battery again so that it would respond again, but now I entered to recovery to make a reset, but the problem is that the recovery is very outdated, so it does not have the "wipe data" options.
It should be said that i can enter into a "recovery mode" that shows:
"
hTC download mode
*** LOCKED ***
htc_a56dj_pro_dtwl PVT S-ON
LK-1.01.0000(8804eff8)
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-1.18.400.22
Aug 1 2017,13:15:24(929341)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
Security Warranty
If you flash this phone with any ROM
that was not officially released by HTC
you take the risk of
releasing your personal and financial
information to unknown sources.
SD NOT MOUNTED
OTG NOT MOUNTED
FILE NOT FOUND
"
Where the blue txt is the actual menu.
In this "recovery mode" I can't use ADB commands, i only can execute some fastboot commands (PC recognizes my device because of fastboot drivers) as "reboot", but for example:
* I can't use the "erase" command because my current recovery is not supported:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.022s
"
* Nor I can directly install the TWRP recovery because it tells me:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1596000000 bytes
sending 'recovery' (14320 KB)...
OKAY [ 1.507s]
writing 'recovery'...
(bootloader) HOSD CL#929341
FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)
finished. total time: 2.550s
"
* And I can't use the "oem unlock" command either because it just says:
"
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.062s]
finished. total time: 0.062s
"
Finally "getvar all" command shows this (i think could be useful):
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC68B1000101
(bootloader) current-slot:
(bootloader) imei: ( here shows IMEI correctly )
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA1****
(bootloader) cid: 11111111
all:
finished. total time: 0.061s
"
Well, this is the situation, and i think the solution is:
Install the TWRP recovery to do a factory reset and if necessary install a ROM (official or not).
Buuut, to install the recovery I need to activate USB debugging (MANUALLY in the android options) and activate the OEM unlock option to unlock the bootloader, which is impossible for me since the phone "turns off" before starting.
My question is:
How to activate OEM unlock option without having to access to android settings? I mean, with commands in fastboot or in some software.
I have searched a LOT on the internet and I can't find anything about it, all the tutorials have the device fully functional, not like me that my device does not start.
Hmmm ill help you with your answer if u can get help for me with mine
Zaq1xsw222 said:
Hmmm ill help you with your answer if u can get help for me with mine
Click to expand...
Click to collapse
So help me and give me your answer, let me see if i can help you
CheckS86 said:
So help me and give me your answer, let me see if i can help you
Click to expand...
Click to collapse
Ok so you was saying you need a command right to type into linux shell. But hold on did you put a custom rom onto the phone yourself
Also, if your phone randomly stopped working by its self, our issues may be related........
Zaq1xsw222 said:
Ok so you was saying you need a command right to type into linux shell. But hold on did you put a custom rom onto the phone yourself
Also, if your phone randomly stopped working by its self, our issues may be related........
Click to expand...
Click to collapse
No, i dont flash nothing in this phone, it just stopped working by itself.
I have a Windows 10 pc and i only can use some fastboot commands, so, i already tried various commands but my outdated recovery only letme run some of them!
CheckS86 said:
No, i dont flash nothing in this phone, it just stopped working by itself.
I have a Windows 10 pc and i only can use some fastboot commands, so, i already tried various commands but my outdated recovery only letme run some of them!
Click to expand...
Click to collapse
What was the last thing you done on your phone?
The last setting you changed?
Have you tried turning the phone on with the battery out?
Zaq1xsw222 said:
What was the last thing you done on your phone?
The last setting you changed?
Have you tried turning the phone on with the battery out?
Click to expand...
Click to collapse
I was playing or using whatsapp maybe, and yes, i tried that, but never start (because of the volt needed), only the LED is on
CheckS86 said:
I was playing or using whatsapp maybe, and yes, i tried that, but never start (because of the volt needed), only the LED is on
Click to expand...
Click to collapse
Here u go.
Hard Reset HTC Desire 10 Pro, how to - HardReset.info
www.hardreset.info
Ok now its your turn
Zaq1xsw222 said:
Here u go.
Hard Reset HTC Desire 10 Pro, how to - HardReset.info
www.hardreset.info
Click to expand...
Click to collapse
The phone make exatly the same, after set the HTC logo the screen and LED turn down (like an animation when lock your screen), i dont know why, but making this led mi to the begining :/
(tell me your question btw)
CheckS86 said:
The phone make exatly the same, after set the HTC logo the screen and LED turn down (like an animation when lock your screen), i dont know why, but making this led mi to the begining :/
(tell me your question btw)
Click to expand...
Click to collapse
Have you tried to restart your phone in safety mode?
Zaq1xsw222 said:
Have you tried to restart your phone in safety mode?
Click to expand...
Click to collapse
It doesn't work, this just led me to de begining too.
The phone can't start, so maybe re-install his firmware is the best option. I already search the firmware for this phone (to try flash it with SP Flashtool), even here in XDA there is an RUU Collection for this phone, but none of them is compatible with mine. This is the firmware compatible:
2PYAIMG_A56DJ_PRO_DTWL_M60_SENSE80GP_HTC_India_SEA_1.18.400.22_Radio_0.A56DJPV1P32.7900.0216.A56T_release_508642_combined_signed_2_4.zip
but is only available to buy... here for example:
2PYAIMG_A56DJ_PRO_DTWL_M60_SENSE80GP_HTC_India_SEA_1.18.400.22_Radio_0.A56DJPV1P32.7900.0216.A56T_release_508642_combined_signed_2_4.zip | Easy Firmware
easy-firmware.com
IDK why this firmware is not in other pages .
Reinstall stock firmware so you can boot into system. Then follow instructions to unlock with unlock code