Related
Welcome.
I have the following problem with my HTC. When you turn on the phone immediately turns on fastboot and can not control buttons Vol + / - on the menu. Can I come in hboot, but there did not respond to my commands.
It is a chance to solve the problem?
*** UNLOCKED ***
BUZZ PVT SHIP S-ON
HBOOT-1002.0000
MICROP-0622
TOUCH PANEL-ATMELC03_16ac
RADIO-3.35.20.10
Click to expand...
Click to collapse
BukeR00 said:
Welcome.
I have the following problem with my HTC. When you turn on the phone immediately turns on fastboot and can not control buttons Vol + / - on the menu. Can I come in hboot, but there did not respond to my commands.
It is a chance to solve the problem?
Click to expand...
Click to collapse
Does it boot Into hboot or fastboot specifically? Also do you have an sdcard in the phone? And lastly when you plug in the usb cable to issue commands does the phone change to hbootUSB or fastbootUSB at all and does Windows detect and Install drivers?
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
When I push the power button, phone starts in FASTBOOT. I can run it in hboot by pressing Vol-+ PWR.
In both modes, the buttons are not working. When I connect the USB cable changes as FASTBOOT USB / HBOOT USB or something like that. I have a card in your phone, I try without the card.
BukeR00 said:
When I push the power button, phone starts in FASTBOOT. I can run it in hboot by pressing Vol-+ PWR.
In both modes, the buttons are not working. When I connect the USB cable changes as FASTBOOT USB / HBOOT USB or something like that. I have a card in your phone, I try without the card.
Click to expand...
Click to collapse
OK please try without the card in also when you are in fastboot USB can you issue the command fastboot getvar all please and see if it works.
Sent from my Nexus 7 using Tapatalk 4
Code:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.02.0000
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.46.0.0
INFOserialno: ###########
INFOimei: ###########
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC4910000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 3955mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 42e5cc47
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.053s
Without the card the same problems. Keys are not working. When I'm try to upload RUU crashes. 155 ERROR. I tried to many versions, as last RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed
Thanks for your reply
BukeR00 said:
Code:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.02.0000
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.46.0.0
INFOserialno: ##########
INFOimei: ###############
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC4910000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 3955mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 42e5cc47
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.053s
Without the card the same problems. Keys are not working. When I'm try to upload RUU crashes. 155 ERROR. I tried to many versions, as last RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed
Thanks for your reply
Click to expand...
Click to collapse
I should have said, block out your imei and HTC serial number like I have. You never know whos watching...
Anyway, your bootloader is still unlocked so ruus wont flash. You can use the command fastboot oem lock to relock the bootloader. But, it's unlikely that it will work as you have an upgraded hboot. If I was you I would I would extract the Rom.zip from the ruu. Then extract that Rom.zip and you should end up with several images and some .nbh files. place the boot.img, system.img, data.img Into your fastboot folder. Then you going to want to format the phone with fastboot and then flash the phone with fastboot. http://androidforums.com/one-s-all-things-root/714676-list-fastboot-command.html here is a command list but I will tell you what I think it should be, and if you hit a snag refer to the link. So the commands should be in this order assuming you are CD'd to your fastboot folder
fastboot format boot
fastboot format system
fastboot format data
fastboot format cache
Then assuming it all goes well then issue these commands
fastboot flash system.img
fastboot flash data.img
fastboot flash boot.img
fastboot flash boot.img
fastboot reboot
Yes that flash the boot.img twice is not a typo all going well after this you should able to boot up. if you hit any big problems just hit the thread pal
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Code:
C:\adb>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.015s
In FASTBOOT shows now - *** RELOCKED ***
Code:
fastboot format boot
fastboot format system
fastboot format data
fastboot format cache
It does not work. There is no these commands
Code:
C:\adb>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb> fastboot erase data
erasing 'data'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.002s
Code:
C:\adb>fastboot flash system.img
unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
C:\adb>\fastboot flash data.img
'\fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\adb>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
C:\adb>fastboot flash system system.img
sending 'system' (212163 KB)... OKAY [ 44.854s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 98.833s
C:\adb>fastboot flash boot boot.img
sending 'boot' (2476 KB)... OKAY [ 1.050s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.689s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.012s
In my rom.zip there is no data.img
After the command fastboot reboot the phone hangs on the white HTC boot screen.
BukeR00 said:
Code:
C:\adb>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.015s
In FASTBOOT shows now - *** RELOCKED ***
Code:
fastboot format boot
fastboot format system
fastboot format data
fastboot format cache
It does not work. There is no these commands
Code:
C:\adb>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb> fastboot erase data
erasing 'data'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.002s
Code:
C:\adb>fastboot flash system.img
unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
C:\adb>\fastboot flash data.img
'\fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\adb>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
C:\adb>fastboot flash system system.img
sending 'system' (212163 KB)... OKAY [ 44.854s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 98.833s
C:\adb>fastboot flash boot boot.img
sending 'boot' (2476 KB)... OKAY [ 1.050s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.689s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.012s
In my rom.zip there is no data.img
After the command fastboot reboot the phone hangs on the white HTC boot screen.
Click to expand...
Click to collapse
Ah. This could be problematic. I should have been clearer, I didn't mean for you to lock your bootloader again, I was simply informing you it would need to be locked for an ruu to run. None of those commands will work while the bootloader is locked. If you were the one to unlock the device the you can unlock it again assuming you have the unlock_token.bin, using the same fastboot command again. If you didn't you will have to go to www.htcdev.com and make an account, then go to bootloader unlock, select wildfire buzz and ignore the bootloader update, as you already have it. (Skip should be near the bottom.) Then follow the instructions and get the bootloader unlocked again. Then issue the commands excluding the lock bootloader one and the flash data data.img as you don't have it. Its not a problem though, I was just covering all bases, incase it did have a data.img in there make sure you still do the data format though!
Sorry for the confusion
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
What version of RUU I must use? I tested 3 versions and none of them has data.img
I have uploaded the files system.img, recovery.img, userdata.img and the phone still does not work. How can I delete the data. Fastboot format command does not work, there is no such command.
And after the command fastboot erase still:
Code:
C:\adb>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb> fastboot erase data
erasing 'data'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.002s
BukeR00 said:
What version of RUU I must use? I tested 3 versions and none of them has data.img
I have uploaded the files system.img, recovery.img, userdata.img and the phone still does not work. How can I delete the data. Fastboot format command does not work, there is no such command.
And after the command fastboot erase still:
Code:
C:\adb>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb> fastboot erase data
erasing 'data'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.002s
Click to expand...
Click to collapse
did you get the bootloader unlocked again? fastboot commands will only work on unlocked bootloaders.
Dont worry about the data.img, you do not need it. i simply added it incase the ruu had it and you got confused. again, it is not required.
Yes, I have unlocked bootloader, but comands still don't work.
//edit:
C:\sdk\sdk\platform-tools>fastboot format boot
formatting 'boot' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.006s
C:\sdk\sdk\platform-tools>fastboot format system\
formatting 'system\' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.006s
C:\sdk\sdk\platform-tools>fastboot format userdata
formatting 'userdata' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.006s
Click to expand...
Click to collapse
BukeR00 said:
Yes, I have unlocked bootloader, but comands still don't work.
//edit:
Click to expand...
Click to collapse
hmmm. well if we cannot format the partitions then we are not going to have much luck :/
ok lets try a different tactic. download this and rename it to just recovery.img . then place it into your adb folder and then issue the following command via fastboot.
Code:
fastboot boot recovery.img
hopefully this will allow you to boot into clockworkmod recovery. when you enter clockworkmod recovery use the volume buttons to move and the trackball to select, power is back. format everything. then try to mount your sdcard using advanced/mount storage or sdcard, something to that effect. then place this file onto it. all going well you should be able to then flash this rom. dismount the usb storage, then go back to the main menu (power button) then go to flash/install, select choose zip and then the zip file we placed there. hopefully the recovery will install without issue. then, open the copy of the rom you downloaded on your pc and extract the boot.img. reboot the phone into fastboot and then use the command fastboot flash boot boot.img
all going well this rom will boot and you will have a working phone again.
Unfortunately, it does not change anything. I can not enter into Clockworkmod recovery. The keys are not working
BukeR00 said:
Unfortunately, it does not change anything. I can not enter into Clockworkmod recovery. The keys are not working
Click to expand...
Click to collapse
it should boot into cwm automatically, no button intervention required.
Unfortunately does not turn ClockworkMod. Phone lay two days without batteries, has launched today as normal. Everything worked. I wanted to do S-OFF by unrevoked, entered into hboot, the phone resets and hung on the HTC screen. After removing the battery turns on hboot again. In Unrevoked I saw that wrote "ClockworMode Recovery"
BukeR00 said:
Unfortunately does not turn ClockworkMod. Phone lay two days without batteries, has launched today as normal. Everything worked. I wanted to do S-OFF by unrevoked, entered into hboot, the phone resets and hung on the HTC screen. After removing the battery turns on hboot again. In Unrevoked I saw that wrote "ClockworMode Recovery"
Click to expand...
Click to collapse
Unrevoked doesnt s-off it only roots and flashes a recovery.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Hi,
Short story:
My One X won't boot to Android anymore. I can only enter boot / fastboot modes.
And when trying to apply modifications (fastboot flash or fastboot unlock), it shows various errors, not always the same.
Long story:
I bought this phone second hand quite a while ago, soon after its market launch. It was already unlocked and rooted, but I don't know what method had been used.
RUU says it runs release 1.28.
Boot says:
- S-On
- HBoot-0.94.0000
- Radio 1.1204.103.14
- Apr 11 2012,02:27:11
Given that it was unlocked / rooted it never received an OTA.
I recently decided to perform a full wipe, and by the way a full upgrade.
So:
- I did a CWM Recovery backup
- I flashed a «semi-stock» image, the stock de-odexed 4.18.401.3 from android-revolution (URL forbidden here, I'm a newbie!) .
- I performed a full wipe / factory reset / cache cleaning / Dalvik cache cleaning.
It didn't boot, and I learnt about the ICS / JB hboot incompatibility.
I tried to flash the boot from the android-revolution page, with no improvements.
So, I decided to revert to my Nandroid backup, from the recovery.
Didn't boot either.
Then I found a Windows computer, relocked the bootloader, and tried RUUs (3.14 and 1.26) with no success.
CID is HTC__203, so I used .401 RUU or OTA files.
RUU application stops each time at a different moment, either for usb connexion error, wrong RUU for my phone, not enough battery, or unknown error.
I read about a battery charge issue, and tried this method to charge it:
Code:
while : ; do fastboot getvar battery-voltage; fastboot reboot-bootloader; sleep 6; done
(as you may see, my main workstation is running Linux)
After a 9 hours long night:
Code:
< waiting for device >
battery-voltage: 3610mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.177s]
finished. total time: 0.177s
< waiting for device >
battery-voltage: 3610mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.177s]
finished. total time: 0.177s
It seems that it couldn't go farther than 3.6V.
But if I tried to unlock my phone after that:
Code:
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.353s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 1.140s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 1.140s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] htc_one_x]#
You can see error message is not always the same.
Same for my firmware.zip flash attempts:
Code:
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot oem rebootRUU
...
FAILED (remote: unknown command)
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot oem rebootRUU
...
FAILED (command write failed (Cannot send after transport endpoint shutdown))
finished. total time: 5.928s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
OKAY [ 1.419s]
writing 'zip'...
FAILED (remote: 13 battery low)
finished. total time: 1.629s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (remote: unknown command)
finished. total time: 1.005s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (remote: unknown command)
finished. total time: 1.005s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]#
What is the real issue? Why can't it give me a consistent error ?
What else could I try?
Thanks for reading this long post and trying to help me!
hervenicol said:
Hi,
What is the real issue? Why can't it give me a consistent error ?
What else could I try?
Thanks for reading this long post and trying to help me!
Click to expand...
Click to collapse
Give me result from command fastboot getvar version-main
Download this fastboot.zip and extract it to a folder fastboot rename the file fastboot-linux to fastboot. The file fastboot only is for windows and if you want to keep it rename fastboot to fastboot-windows
Thant said:
Give me result from command fastboot getvar version-main
Click to expand...
Click to collapse
Here it is, with both versions of fastboot:
1 - my one, from the Android SDK
2 - yours
Code:
[[email protected] fastboot]# fastboot getvar version-main
version-main: 1.28.401.9
finished. total time: 0.006s
[[email protected] fastboot]# ./fastboot getvar version-main
version-main: 1.28.401.9
[[email protected] fastboot]#
hervenicol said:
Here it is, with both versions of fastboot:
1 - my one, from the Android SDK
2 - yours
Code:
[[email protected] fastboot]# fastboot getvar version-main
version-main: 1.28.401.9
finished. total time: 0.006s
[[email protected] fastboot]# ./fastboot getvar version-main
version-main: 1.28.401.9
[[email protected] fastboot]#
Click to expand...
Click to collapse
1. Charge your phone
2. Download this RUU 1.28.401.9
3. Lock your bootloader with command fastboot oem lock
4. Run the RUU as administrator
5. Aplly all update to latest JB from Settings/Software update
Thant said:
1. Charge your phone
2. Download RUU 1.28.401.9 (link removed from quote)
3. Lock your bootloader with command fastboot oem lock
4. Run the RUU as administrator
5. Aplly all update to latest JB from Settings/Software update
Click to expand...
Click to collapse
That's exactly what I was trying to do.
I finally succeeded, few minutes ago, after charging to 3920mv.
It looks like the USB cable quality has a big impact on the charging capabilities:
- with a cheap cable I couldn't go farther than 3.6xx V.
- When I changed my cable, it was charging much faster, up to 3.9xx V.
…then at this level of charge the RUU*worked.
Thanks anyway for your help! :good:
Now it's doing OTA*updates…
hervenicol said:
That's exactly what I was trying to do.
I finally succeeded, few minutes ago, after charging to 3920mv.
It looks like the USB cable quality has a big impact on the charging capabilities:
- with a cheap cable I couldn't go farther than 3.6xx V.
- When I changed my cable, it was charging much faster, up to 3.9xx V.
…then at this level of charge the RUU*worked.
Thanks anyway for your help! :good:
Now it's doing OTA*updates…
Click to expand...
Click to collapse
Good to hear that:good:
All upgrades applied, works like a charm
I set the title for this answer with [SOLVED], I hope it applies to the thread as well.
Now let's look for a way to root this rom!
Hi,
i unlocked my bootloader using the original LG tool (unlock.bin).
fastboot getvar unlocked:
[[email protected] Desktop]# fastboot getvar unlocked
unlocked: yes
finished. total time: 0.004s
[[email protected] Desktop]#
Then i booted into bootloader using adb reboot bootloader.
fastboot flash recovery twrp-2.8.6.1-h815.img
gave me no error.
[[email protected] Desktop]# fastboot flash recovery twrp-2.8.6.1-h815.img
target reported max download size of 536870912 bytes
sending 'recovery' (32060 KB)...
OKAY [ 1.022s]
writing 'recovery'...
OKAY [ 0.287s]
finished. total time: 1.309s
[[email protected] Desktop]#
Now when i restart the phone using adb reboot recovery i get the "dead android" logo. No key combination works.
When booting using the Power+Vol-Down, the phone enters the reset menu. I select twice "YES", but TWRP is not started, and the phone is empty
Any idea?
Thanks
i went through the exact scenario, and found the solution myself, you're typing the wrong command, take the battery out, plug your phone into bootloader/fastboot mode or do it via adb
adb reboot bootloader
then flash the recovery again just to be safe
then either type fastboot boot twrp-2.8.6.1-h815.img
or adb boot twrp-2.8.6.1-h815.img
Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech
Latest = DP2
Manual:
Unlock bootloader
Install TWRP
Install OEM
Download OEM oem.img
Enter commands into fastboot
Code:
fastboot -i 0x2970 erase oem
Code:
fastboot -i 0x2970 flash oem oem.img
Download files from here (Only System and Boot)
Flash files
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Reboot into TWRP
Make wipe data & wipe cache
Reboot phone
All works fine.
Sorry for my bad english and russian site server.
FindYanot said:
Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech/ANDROIDN
Manual:
Wipe data
Bot into fastboot
Use this commands:
fastboot flash boot boot.img
fastboot flash oem oem.img
fastboot flash system system.img
All works fine.
Sorry for my bad english and russian site server.
Click to expand...
Click to collapse
IFlashed. Works fine so far. Gapps are included in preview. Many thanks
FindYanot said:
Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech
Manual:
Wipe data
Bot into fastboot
Use this commands:
fastboot flash boot boot.img
fastboot flash oem oem.img
fastboot flash system system.img
All works fine.
Sorry for my bad english and russian site server.
Click to expand...
Click to collapse
Just curious. Does it have root? I am going to flash if in an hour or 2
---------- Post added at 05:55 AM ---------- Previous post was at 05:33 AM ----------
yasteellutch said:
Just curious. Does it have root? I am going to flash if in an hour or 2
Click to expand...
Click to collapse
Does it have OTA?
---------- Post added at 06:32 AM ---------- Previous post was at 05:55 AM ----------
yasteellutch said:
Just curious. Does it have root? I am going to flash if in an hour or 2
---------- Post added at 05:55 AM ---------- Previous post was at 05:33 AM ----------
Does it have OTA?
Click to expand...
Click to collapse
I am having an issue flashing. I flash using TWRP and when I reboot it says "No OS Installed". Also when I tried via fastboot. Is there any thing I am missing?
No root and OTA.
Before flashing via fastboot wipe data through twrp.
mermigas said:
No root and OTA.
Before flashing via fastboot wipe data through twrp.
Click to expand...
Click to collapse
Could you upload a screenshot?
mermigas said:
No root and OTA.
Before flashing via fastboot wipe data through twrp.
Click to expand...
Click to collapse
I did exactly that and still stuck in boot
http://4pda.ru/forum/index.php?showtopic=730213&st=120#entry47858392
Use Google translate to see instructions
Phew! some development on the Crackling!
:good:
Very impressed... TWRP method didn't wrk, fastboot worked fine! thankyou for bringing it here too, my Russian is non existent
My 1st impressions:
Very good, I haven't encountered any major issues..... I'll keep testing
Well, I just installed on my trusty Wileyfox Swift.
Overall I'm impressed, however the sensors are not working- gyro/ accelerometer/ proximity. There is some conflict with libraries when starting a game.
With a few more updates (fingers crossed) I can see myself using it as a daily driver
Everything else works and works really well. The phone seems a lot faster, the SDcard was formatted (haven't tested using an app from it but games are out of the question anyway), dual-window will be neat and is fine at the moment.
There is a lot to like here with few issues.
PS: After reading a bit from the older threads on XDA and from 4pda.ru , it seems the sensor issue is connected to the bridge to enable Android One roms with FindYanot's oem image on our crackling. Really impressive thus far. I wonder if we can flash General Mobile 4G firmware with QFIL?
I've tried this firmware on my phone and I'd like to share both experience and expressions.
Main laptop is MacBook Air, so it was quite hard to find working fastboot, adb ot GUI utilities.
Finally, I've installed them with command:
Code:
bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
Then I tried to unlock the bootloader and flash images:
Code:
Sergeys-MacBook-Air:tools cleversokol$ adb devices
List of devices attached
adb server is out of date. killing...
adb I 4550 408520 usb_osx.cpp:259] Found vid=2970 pid=2282 serial=bf2ecad9
adb I 4550 408520 usb_osx.cpp:259]
* daemon started successfully *
bf2ecad9 unauthorized
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
As you can see, I had failed unlocking the bootloader and I did not install TWRP. Also, without TWRP I had not done wipe.
Code:
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.002s
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (18457 KB)...
OKAY [ 0.667s]
writing 'boot'...
OKAY [ 1.835s]
finished. total time: 2.502s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash oem oem.img
target reported max download size of 268435456 bytes
sending 'oem' (6128 KB)...
OKAY [ 0.224s]
writing 'oem'...
OKAY [ 0.734s]
finished. total time: 0.958s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.131s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.011s]
writing 'system'...
OKAY [ 21.393s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.789s]
writing 'system'...
OKAY [ 20.547s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.854s]
writing 'system'...
OKAY [ 20.591s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.522s]
writing 'system'...
OKAY [ 20.518s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.106s]
writing 'system'...
OKAY [ 21.263s]
sending sparse 'system' (23028 KB)...
OKAY [ 0.978s]
writing 'system'...
OKAY [ 1.729s]
finished. total time: 165.433s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.001s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
< waiting for any device >
After flashing this three images I got a brick. Phone showed Wileyfox logo once and turned off. After ejecting/inserting battery, it responsed (once) to Power button, but showed only logo and turned off again.
Eject/insert battery again and pressing Power + VolDown took me to some menu. From it I've reached fastboot menu.
With windows-laptop and WileyFox Tool utility I pressed Check bootloader status button. Phone restarted and I got Android N boot animation. Then restarted again and finally I'm in Android N First Setup Utility.
Working:
— screen, touchscreen, brightness ajustment (manual)
— mic, speaker
— charging
— GPS
— 4G
— Wi-Fi
— camera (video does not work)
— night mode
— multi-window mode
Not working:
— sensors
— some apps show library mismatch
Also, Power + VolDown button now does not take me to recovery menu. It shows android with red exclamation point. I think it's not right.
cleversokol said:
I've tried this firmware on my phone and I'd like to share both experience and expressions.
Main laptop is MacBook Air, so it was quite hard to find working fastboot, adb ot GUI utilities.
Finally, I've installed them with command:
Code:
bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
Then I tried to unlock the bootloader and flash images:
Code:
Sergeys-MacBook-Air:tools cleversokol$ adb devices
List of devices attached
adb server is out of date. killing...
adb I 4550 408520 usb_osx.cpp:259] Found vid=2970 pid=2282 serial=bf2ecad9
adb I 4550 408520 usb_osx.cpp:259]
* daemon started successfully *
bf2ecad9 unauthorized
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
As you can see, I had failed unlocking the bootloader and I did not install TWRP. Also, without TWRP I had not done wipe.
Code:
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.002s
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (18457 KB)...
OKAY [ 0.667s]
writing 'boot'...
OKAY [ 1.835s]
finished. total time: 2.502s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash oem oem.img
target reported max download size of 268435456 bytes
sending 'oem' (6128 KB)...
OKAY [ 0.224s]
writing 'oem'...
OKAY [ 0.734s]
finished. total time: 0.958s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.131s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.011s]
writing 'system'...
OKAY [ 21.393s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.789s]
writing 'system'...
OKAY [ 20.547s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.854s]
writing 'system'...
OKAY [ 20.591s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.522s]
writing 'system'...
OKAY [ 20.518s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.106s]
writing 'system'...
OKAY [ 21.263s]
sending sparse 'system' (23028 KB)...
OKAY [ 0.978s]
writing 'system'...
OKAY [ 1.729s]
finished. total time: 165.433s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.001s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
< waiting for any device >
After flashing this three images I got a brick. Phone showed Wileyfox logo once and turned off. After ejecting/inserting battery, it responsed (once) to Power button, but showed only logo and turned off again.
Eject/insert battery again and pressing Power + VolDown took me to some menu. From it I've reached fastboot menu.
With windows-laptop and WileyFox Tool utility I pressed Check bootloader status button. Phone restarted and I got Android N boot animation. Then restarted again and finally I'm in Android N First Setup Utility.
Working:
— screen, touchscreen, brightness ajustment (manual)
— mic, speaker
— charging
— GPS
— 4G
— Wi-Fi
— camera (video does not work)
— night mode
— multi-window mode
Not working:
— sensors
— some apps show library mismatch
Also, Power + VolDown button now does not take me to recovery menu. It shows android with red exclamation point. I think it's not right.
Click to expand...
Click to collapse
I've had the opposite experience. Fastboot works without fail on Mac and Linux. Windows- not so much with the Swift.
Flash TWRP manually - fastboot flash recovery your_recovery_image.img (replace with the file name for TWRP)
You've just installed the patched oem.img (to allow code name "seed" images) along with boot and system. Can't boot to recovery if you don't have one
Steer away from flashing other files from the Android One stock image (it will be even messier hardbrick and you would have to follow the instructions from the other thread).
If you want to return to stock COS, follow the instructions from these awesome people : http://forum.cyanogenmod.org/topic/118287-manual-flashing-of-stock-cyanogenos/
PS: For some reason, unlocking the bootloader for me worked with: fastboot oem unlock-go
but not with:
fastboot -i 0x2970 oem unlock-go
Locking with: fastboot oem lock-go , worked as expected
Can I use this TWRP? I did not found Wileyfox Swift among supported devices.
cleversokol said:
Can I use this TWRP? I did not found Wileyfox Swift among supported devices.
Click to expand...
Click to collapse
I believe this is the one I've used.
In case the Windows tool for Wileyfox works for you (I'm missing some C# utilities on mine and can't deal with it atm), you can add TWRP from there as well.
PS: I used it only to install initially this preview. I haven't used it after.
Sucessfully installed TWRP3.0 (CM13-nightly-recovery did not work for me. Keep getting image of Android with red exclamation mark), wiped cache, data and installed CM13-nightly + GAPPS Mini. Booted into CM, did basic setup. After that I wanted to re-lock the bootloader.
With
Code:
fastboot oem lock-go
it worked, but after this command I got brick-phone again.
Only replacing the battery + re-unlocking the device helped to restore it.
Is there a way to keep device working with locked bootloader?
Lock the bootloader only if you'll be using stock signed images of CyanogenOS. That is in case you will have to return the device due to hardware fault- dead pixels, non functioning microphones/ speakers, etc. Another reason as of why you might want to relock, is to ensure that you'll be using CyanogenOS recovery and no problems with future OTAs (no guarantee there as encrypted devices had problems with first official update but things are looking nice for future official OTAs).
If you want to use custom recovery- TWRP/CMRecovery by itself or along with CyanogenMod13 or any other custom ROM- do not lock the bootloader.
These are your options Keep the bootloader unlocked unless you have the need/ desire to return it to true stock.
I tried to install it again and it doesn't work. I flashed stock and unlocked my bootloader. I managed to flash OEM and BOOT but it doesn't want to flash the system partition at all. I tried everything. I tried 4pda method too. Am I missing something?
yasteellutch said:
I tried to install it again and it doesn't work. I flashed stock and unlocked my bootloader. I managed to flash OEM and BOOT but it doesn't want to flash the system partition at all. I tried everything. I tried 4pda method too. Am I missing something?
Click to expand...
Click to collapse
System img is big and post propably your fastboot installer cannot handle it.
Try this fastboot installer
http://forum.xda-developers.com/showthread.php?t=2588979
This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
yasteellutch said:
This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
Click to expand...
Click to collapse
It keeps on saying sending sparse system img(0kb)
yasteellutch said:
This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
It keeps on saying sending sparse system img(0kb)
Click to expand...
Click to collapse
Just try this
http://androidhost.org/P2XKs
unzip to your root directory - copy Android N images to this directory and give it a try.
mermigas said:
Just try this
http://androidhost.org/P2XKs
unzip to your root directory - copy Android N images to this directory and give it a try.
Click to expand...
Click to collapse
This is what I get
Hello,
I am asking here is there a way to unlock bootloader?
The situation is:
- the phone is in boot loop.
- the phone boots to download mode every time.
- cannot access to recovery mode from fastmode.
- cannot apply LG tot to refurbish in download mode. It now deads at 4% of the process.
- and the last, I didn't enable OEM unlocking when the phone was still functioning.
Adb, fastboot, I tried all the commands that I know so far, but no help.
I know that I have to enable OEM unlocking to be able to unlock bootloader. But again, I cannot boot in to do it.
So just hope that some experts might know a way.
You don't have a possibility to unlock it!
The only way is by settings from working phone.
S C:\Android\platform-tools> .\fastboot.exe devices
0171046759b8474f fastboot
PS C:\Android\platform-tools> fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 1
OKAY [ 0.020s]
finished. total time: 0.021s
PS C:\Android\platform-tools> fastboot.exe flashing unlock
...
OKAY [ 9.244s]
finished. total time: 9.247s
PS C:\Android\platform-tools> fastboot.exe flashing unlock
...
FAILED (remote: Already unlocked)
finished. total time: 0.008s
PS C:\Android\platform-tools> fastboot flash boot boot-fixed.img
target reported max download size of 536870912 bytes
sending 'boot' (11797 KB)...
OKAY [ 0.321s]
writing 'boot'...
OKAY [ 0.137s]
finished. total time: 0.461s
PS C:\Android\platform-tools> fastboot flash recovery recovery-fixed.img
target reported max download size of 536870912 bytes
sending 'recovery' (17437 KB)...
OKAY [ 0.459s]
writing 'recovery'...
OKAY [ 0.209s]
finished. total time: 0.671s
PS C:\Android\platform-tools>
Sigh,
So no more hope.
Thank you ^_^
Try the battery discharge trick described by sd_cb on the page Fix-a-Brick: Fighting the Nexus 5X Bootloop:
"One trick I learned for my bootlooped 5X is that first you let the phone completely drain of battery (boot into recovery and let it sit). Then, plug in the phone and boot up. I would get ~1 minute in the phone before it would reset. What did this do for me? It allowed me to recover my 2 factor codes that I was stupid enough not to print or save to begin with. Lesson learned"