Related
Hi, about 6 months ago bought a rogers htc raider, upon receipt procedures to perform the unlock bootloader and s-off procedure, it will change back to a stock rom and I gave it to my brother, I recently comes for saying that when you turn the phone just stays on the logo screen, entering volume down menu and power, try to do a factory reset and get stuck, also download a stock rom and extracted the rom.zip file so renowned as ph39img.zip and try to run and do the updating also remains stalled, also try to lock the bootloader with fastboot oem lock and also stuck.
please i need help.
axel_johnson said:
Hi, about 6 months ago bought a rogers htc raider, upon receipt procedures to perform the unlock bootloader and s-off procedure, it will change back to a stock rom and I gave it to my brother, I recently comes for saying that when you turn the phone just stays on the logo screen, entering volume down menu and power, try to do a factory reset and get stuck, also download a stock rom and extracted the rom.zip file so renowned as ph39img.zip and try to run and do the updating also remains stalled, also try to lock the bootloader with fastboot oem lock and also stuck.
please i need help.
Click to expand...
Click to collapse
1. This should not be in the development section......
2. Boot to bootloader.
3. Does it say Locked, Relocked, or Unlocked?
4. Does it say S-On or S-Off?
5. Do you have v1.83 or 1.85 bootloader?
6. Select Recovery, what happens?
1. This should not be in the development section......
2. Boot to bootloader.
yes boot with volumen - and power
3. Does it say Locked, Relocked, or Unlocked?
Unlocked, i try locked again but nothing the phone still stuck, running the command fastboot oem lock.
4. Does it say S-On or S-Off?
s-off along a few months with the method juonot... with wire.
5. Do you have v1.83 or 1.85 bootloader?
show the version 1.85
6.- recovery
don't work when selected the option recovery the phone show the screen logo along 1 second and back to screen boot.
Next step would be fast boot flashing a custom recovery. I recommend wcx or twrp. Once youve done that, youll be set to properly wipe and flash the ROM of your choice
wcxjb hello and try but I can not, I get the following error.
C: \ Useful HTC One X \ WCXJB_ROOT_PACK \ WCXJB_ROOT_PACK> fastboot flash zip jb_hboot.
zip
******** sending 'zip' (379 KB) ... OKAY [0.318s]
***************** writing 'zip' ... FAILED (remote: not allowed)
finished. total time: 0.642s
please what else I can do ... I need to operate this phone.
Extract the wcxrecovery.IMG from the zip..
Fastboot flash recovery wcxrecovery.IMG
You can't fastboot flash a zip
I tried to do that and I get the following error.
C:\Utiles HTC One X\WCXJB_ROOT_PACK\WCXJB_ROOT_PACK>fastboot flash recovery wcxr
ecovery.img
sending 'recovery' (6996 KB)... OKAY [ 1.720s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 3.178s
please help me.
Is your Boot loader unlocked?
yes the bootloader is unlocked, i try locked o relocked but not possibly, the phone was stuck.
please help what steps should I follow ... I want to retrieve the phone.
axel_johnson said:
please help what steps should I follow ... I want to retrieve the phone.
Click to expand...
Click to collapse
The only things I can think of that would cause this "writing 'recovery'... FAILED (remote: image update error)" would be:
1. You got a bad download
2. Bootloader is not properly unlocked
3. Your recovery partition got borked somehow
Things I would try next:
1. Redownload the recovery image and try again
2. fastboot oem lock to lock the bootloader, then go through the unlock process again
3. fastboot oem lock, run your carrier's RUU, reunlock bootloader, fastboot flash recovery wcxrecovery.img, fastboot flash boot boot.img (from ROM), boot to recovery, wipe data, system, dalvik, and cache, and flash ROM
pleas help me my htc rider
My phone refuse to boot up to normal background it is stuck on the htc logo hv tried factry reset bt still no progress it was caused by an apps I installed phone name htc rider vrsn 4.0 pls help me
nexus 6 can not run the system, only the logo on the screen does not move
I tried to brush oem unlock firmware but failed.
I guess I broke the Recovery partition.
How can I do it? Help me!:angel::angel:
Please give a bit more detail about your setup and what happened before this
rootSU said:
Please give a bit more detail about your setup and what happened before this
Click to expand...
Click to collapse
I installed android 5.1.
root
Installed TWRP Recovery
Then I run "fastboot oem lock" this time we can not normally enter the system.
I found that running fastboot -w can enter the system, so I entered the "TWRP Recovery" to restore the backup method used to restore a backup Recovery partition.
So, let me get it straight...
You unlocked the bootloader
You then rooted
Installed recovery
THEN relocked the boot loader?
...why?
You won't be able to do anything to any partition until the boot loader is unlocked again - try that. Unlock the boot loader (make sure to enable it in Dev settings) and then it should all work again.
Good job, I think you bricked yourself.
Not sure if anyone found a work around for this.
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497
Leo D said:
nexus 6 can not run the system, only the logo on the screen does not move
I tried to brush oem unlock firmware but failed.
I guess I broke the Recovery partition.
How can I do it? Help me!:angel::angel:
Click to expand...
Click to collapse
If you have TWRP recovery installed and ONLY if you have TWRP installed, boot into bootloader. Issue the fastboot commands:
fastboot format userdata
fastboot format cache
If you do have TWRP installed, this should allow you to boot to TWRP recovery.
See if you can accomplish this and let us know.
Evolution_Freak said:
If you have TWRP recovery installed and ONLY if you have TWRP installed, boot into bootloader. Issue the fastboot commands:
fastboot format userdata
fastboot format cache
If you do have TWRP installed, this should allow you to boot to TWRP recovery.
See if you can accomplish this and let us know.
Click to expand...
Click to collapse
I went into recovery mode, nothing happens.
View Bootloader logs
Invalid boot image size!
failed to validate recovery image
Boot up failed
iRub1Out said:
So, let me get it straight...
You unlocked the bootloader
You then rooted
Installed recovery
THEN relocked the boot loader?
...why?
You won't be able to do anything to any partition until the boot loader is unlocked again - try that. Unlock the boot loader (make sure to enable it in Dev settings) and then it should all work again.
Click to expand...
Click to collapse
fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.028s
Options appear before acceptance and rejection does not appear on the phone screen.
You probably bricked it.
It's been known to happen after 5.1 if you're not careful (or, in this case, relock the BL after modifying)
Why did you relock it? I still can't wrap my head around any reason for doing that?
Sent from my Nexus 6
Leo D said:
fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.028s
Options appear before acceptance and rejection does not appear on the phone screen.
Click to expand...
Click to collapse
The phone is bricked. RMA to Motorola
Or if you're feeling adventurous: http://forum.xda-developers.com/showthread.php?t=3059518
brando56894 said:
Or if you're feeling adventurous: http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
Thanks for your help. But there are some questions I still do not understand.
Now the phone connected to the computer and did not see QHSUSB_BULK in Device Manager. In the Device Manager to see BootLoader interface or adb interfaces.
How can I make the phone run QHSUSB_BULK state?
I have the Moto Nexus 6 (xt1100) with TRWP installed no backup saved, OEM bootloader locked and no OS currently on the phone and i cant reflash nethunter or any stock roms through TRWP or fastboot. PLZ HELP ME OUT.
You could to install by adb sideload some full ota.
There is a Android N preview that could be applied by adb sideload, once you have access to your phone, you could unlock bootloader and apply any other rom
lulzwolf said:
I have the Moto Nexus 6 (xt1100) with TRWP installed no backup saved, OEM bootloader locked and no OS currently on the phone and i cant reflash nethunter or any stock roms through TRWP or fastboot. PLZ HELP ME OUT.
Click to expand...
Click to collapse
Push a custom rom to your phone and flash it in TWRP. Command: adb push namerom.zip /sdcard/, or sideload a custom rom in also in TWRP recovery. And don`t ever relock your bootloader again if you are flasher If you have enabled ENABLE OEM UNLOCK in developer options its best to unlock it first
gee2012 said:
Push a custom rom to your phone and flash it in TWRP. Command: adb push namerom.zip /sdcard/, or sideload a custom rom in also in TWRP recovery. And don`t ever relock your bootloader again if you are flasher If you have enabled ENABLE OEM UNLOCK in developer options its best to unlock it first
Click to expand...
Click to collapse
He can't flash any ROM with a locked bootloader.
You should be able to fastboot flash a stock image, but if your fastboot isn't working then you're kinda screwed.
All I can say is give the fastboot flash another try, maybe from a different PC. Use method 2 in this guide to return to stock, then use the stock recovery to factory reset and boot it up
noidea24 said:
He can't flash any ROM with a locked bootloader.
You should be able to fastboot flash a stock image, but if your fastboot isn't working then you're kinda screwed.
All I can say is give the fastboot flash another try, maybe from a different PC. Use method 2 in this guide to return to stock, then use the stock recovery to factory reset and boot it up
Click to expand...
Click to collapse
I tried Macon's method but i am still unable to flash the phone back to stock. The OEM bootloader is locked and i cant access it without an OS installed. Is there a way i can bypass the OEM bootloader aka hack/root the phone to reflash it?
It should work if you run these commands (with the phone in bootloader) prior to flashing the custom rom zip in TWRP:
Fastboot format cache
Fastboot format userdata
Didgeridoohan said:
It should work if you run these commands (with the phone in bootloader) prior to flashing the custom rom zip in TWRP:
Fastboot format cache
Fastboot format userdata
Click to expand...
Click to collapse
"""
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'cache' (6248 KB)...
writing 'cache'...
(bootloader) Unlock before flashing
"""
"""
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
sending 'userdata' (139061 KB)...
writing 'userdata'...
(bootloader) Unlock before flashing
"""
Im still locked out of the bootloader. how do i circumvent the OEM bootlock? can i hack pass it? it is password protected somewhere, if it is can i bruteforce the password? how can i get pass it guyz?!?!
The OEM bootloader is locked and i cant gain access to the developer optios because i dont have an OS to boot into. Im looking for a way i can "bypass" "circumvent" "hack" "disable" or any other word you can think of to get around the bootloader lock and flash my phone. i can start an "adb shell" and gain access to the command line on the phone, but i dont know where i can find the "OEM Bootloader" part of the phone for modification. I have also tried running "fastboot oem get_unlock_data" but it says "(bootloader) This command is not needed to unlock. Run fastboot oem unlock" WTF.... DAMMIT FUK FUK FUK FUUUUUUUUUUUUUUUUUUUUUUUUUUJK
"""
The command i used below and its output message.
"""
[email protected]# fastboot oem unlock
"""
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.005s
"""
lulzwolf said:
"""
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'cache' (6248 KB)...
writing 'cache'...
(bootloader) Unlock before flashing
"""
"""
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
sending 'userdata' (139061 KB)...
writing 'userdata'...
(bootloader) Unlock before flashing
"""
Im still locked out of the bootloader. how do i circumvent the OEM bootlock? can i hack pass it? it is password protected somewhere, if it is can i bruteforce the password? how can i get pass it guyz?!?!
Click to expand...
Click to collapse
Sorry to hear that... The suggested method used to work for people unable to unlock their bootloader due to not having the setting checked in developers settings (if they had TWRP installed, of course).
I do believe you are screwed...
@lulzwolf: Contact Motorola and/or Google, because you screwed yourself by not leaving "Enable OEM Unlock" checked after you modified the firmware. There is no way to brute force the lock, unless you happen to be immortal. The encryption on the bootloader is sufficiently strong that you'll be dead long before a computer could successfully unlock it.
Lesson of the day folks: if you modify your Nexus 6, even if only to root it, leave "Enable OEM Unlock" checked! Yes, it will make your device less secure since a knowledgeable person can flash a factory image, but it's better than being permanently locked out of the device.
Just flash any rom trough TWRP. For god's sake, it even supports MTP. What's your problem?
@Lawstorant: Did you read the thread? His bootloader is locked, meaning he cannot flash anything.
@Strephon Alkhalikoi
It doesn't work that way. Locked bootloader only means that he cannot flash anything using fastboot, but he clearly said that he has TWRP. TWRP doesn't relay on fastboot (common knowledge 1) because it's a totally seperate thing, hence locked bootloader doesn't affect TWRP in any way. He can still do anything he likes. The simplest solution is to flash ANY rom trough TWRP and unlock bootloader with "Boot unlocker" app.
Locked bootloader means you cannot use fastboot, partitions are not unaccesible.
1. If you lock your Windows OS with password you can't acces it, but if you have Linux there's nothing that prevents you from browsing filse on windows partition (only encryption, but still, you can wipe it and put in, anything you want).
TL;DR You're wrong, go learn some more.
@Lawstorant, your attitude and tone need a bit of adjustment. If I am wrong, that's one thing. There is however no need to be a smart ass about it, especially with the TL;DR bit. It's juvenile, and uncalled for. That said, you are correct in that lulzwolf may not be totally screwed. Virtually everyone, including myself, has assumed he has to flash a stock image, but he really doesn't. We'll need him to answer one way or another, but the instructions to restore his device are as follows.
Boot into bootloader.
Use fastboot and issue the following commands: fastboot format userdata, fastboot format cache.
Reboot into TWRP.
Flash a custom ROM.
Unlock the bootloader, and leave it unlocked.
lulzwolf did in fact get at least as far as the two fastboot commands, but he does not say whether he got back into TWRP. Now that he has gotten the userdata and cache formatted he should be able to boot into TWRP and install a custom ROM. From there he should be able to unlock the bootloader.
So @lulzwolf, where are you getting stuck? You may not be done yet, as I erroneously assumed.
@Lawstorant: Did you read the thread? His bootloader is locked, meaning he cannot flash anything.
Click to expand...
Click to collapse
no need to be a smart ass about it,
Click to expand...
Click to collapse
formating trough fastboot won't succed, because he needs access to these partitions. Why would anyone even recommend fastboot when bootloader is locked? He's better of formatting them trough TWRP.
TWRP is answer to all questions. I don't even know why he's tinkering with his phone if he can't figure it out on his own.
Ask The_Merovingian. He wrote the guide. I simply copied it from his thread.
However, you and I do agree on one very important thing. If he doesn't know what he's doing he shouldn't be messing about with his phone, period. He did say in his opening post that he couldn't flash ROMs through TWRP, but given what's been posted, there shouldn't be any reason he can't flash a ROM, except he has a bigger issue than not having the OS.
Ok so i have solved my problem by installing a custom ROM called "Cataclysm" through the TRWP recovery tool. My problem was I tried flashing to stock with fastboot when fastboot had no access to the partitions. so i used adb to push a custom ROM and installed it in TRWP.... BOOM it was fixed! so in conclusion we have learned that fastboot cannot access partitions while the OEM bootloader is locked but TRWP can. thank you all for commenting and helping me out, and hopefully this thread can help out others who run across this problem in the future.
lulzwolf said:
I have the Moto Nexus 6 (xt1100) with TRWP installed no backup saved, OEM bootloader locked and no OS currently on the phone and i cant reflash nethunter or any stock roms through TRWP or fastboot. PLZ HELP ME OUT.
Click to expand...
Click to collapse
rofl, way to go
lulzwolf said:
Ok so i have solved my problem by installing a custom ROM called "Cataclysm" through the TRWP recovery tool. My problem was I tried flashing to stock with fastboot when fastboot had no access to the partitions. so i used adb to push a custom ROM and installed it in TRWP.... BOOM it was fixed! so in conclusion we have learned that fastboot cannot access partitions while the OEM bootloader is locked but TRWP can. thank you all for commenting and helping me out, and hopefully this thread can help out others who run across this problem in the future.
Click to expand...
Click to collapse
Which is exactly what gee2012 suggested that you should do in the second reply to your cry for help. (And at least I assumed you had tried without success. Serves me right for assuming...)
Glad it worked out. :good:
I hope you learned more than just that from this exercise. I know I did, namely a reminder to "practice what I preach". I tell people like you to search before posting and I failed to do just that. Mea culpa.
Hello!
I install a Flashify to make my .img files run and I can install a Custom ROM, because always when I try to install it from ADB it shows
Code:
FAILED (remote: Command not allowed)
All files what I want to boot from ADB, shows this line.
When I turn on my phone, blinks red, 2 times green and then again the same. Also Power + Vol Up or Down, doesnt work, even I cant run a update from SD Card, and HiSuite doesn't show my phone as connected...
Similar problem is in this post - http://forum.xda-developers.com/ascend-p7/help/unfortunately-boot-failed-information-t2908514
There's full CMD from my try to run recovery and boot
Code:
The system cannot find message text for message number 0x2350 in the message file for Application.
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Not enough storage is available to process this command.
C:\...\ADB Flash Tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (12510 KB)...
OKAY [ 0.480s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.481s
C:\...\ADB Flash Tools>fastboot boot BOOT.img
creating boot image...
creating boot image - 9660416 bytes
downloading 'boot.img'...
OKAY [ 0.363s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.365s
Whats the problem? And how I can get back my phone to work?
your bootloader os locked..
that is why you fail flashing..
you have to unlock the bootloader first (use search)..
Gesendet von meinem HUAWEI CRR-L09 mit Tapatalk
blueIBI said:
your bootloader os locked..
that is why you fail flashing..
you have to unlock the bootloader first (use search)..
Gesendet von meinem HUAWEI CRR-L09 mit Tapatalk
Click to expand...
Click to collapse
Ok, but how I can get back my phone to system, that I can unlock bootloader?
i cant even turn on my phone, only i can get fastboot
eatmailyo said:
Ok, but how I can get back my phone to system, that I can unlock bootloader?
i cant even turn on my phone, only i can get fastboot
Click to expand...
Click to collapse
Yeah, you're screwed. You need a fully working phone in order to unlock bootloader. Not gonna happen dude.
Milan-XDA said:
Yeah, you're screwed. You need a fully working phone in order to unlock bootloader. Not gonna happen dude.
Click to expand...
Click to collapse
Not that screwed, worst case he can use dc-phoenix to flash a stock rom even with the boot loader locked. Not sure if dc-unlocker can unlock the boot loader with the phone not booting.
If you have your boot loader unlock code you should not need the system working, only the fastboot mode to unlock the bl.
randhackr said:
Not that screwed, worst case he can use dc-phoenix to flash a stock rom even with the boot loader locked. Not sure if dc-unlocker can unlock the boot loader with the phone not booting.
If you have your boot loader unlock code you should not need the system working, only the fastboot mode to unlock the bl.
Click to expand...
Click to collapse
Android versions of Huawei are not supported by DC-Unlocker as you can see here:
https://www.dc-unlocker.com/supported_models_1/huawei_1
As I said, totally screwed.
Milan-XDA said:
Android versions of Huawei are not supported by DC-Unlocker as you can see here:
https://www.dc-unlocker.com/supported_models_1/huawei_1
As I said, totally screwed.
Click to expand...
Click to collapse
Dude, that is not true. I recovered my p9 lite from a hard brick (with locked bootloader) using dc-phoenix. And dc-unlock supports reading the bootloader unlock code for the huawei p7. Do check https://www.dc-unlocker.com/supported_models_1/huawei_phones
How could he even use flashify without root / unlocked bootloader?
Btw
NEVER use flashify to flash partitions...
As I say in the tittle, my phone has not slot b. It means that when I try to flash any .img or .zip I have an error message telling my that "XXX_b not accesible".
How can I create the partition? I have android one and everything locked as I flashed the stock image vía COM because I have no idea how to solve the partition problem.
gfpablo_ said:
As I say in the tittle, my phone has not slot b. It means that when I try to flash any .img or .zip I have an error message telling my that "XXX_b not accesible".
How can I create the partition? I have android one and everything locked as I flashed the stock image vía COM because I have no idea how to solve the partition problem.
Click to expand...
Click to collapse
You say you are trying to flash something but then you also say that everything is locked. You can't flash anything other than the stock firmware (in EDL mode) if your bootloader is locked.
Catsonvi said:
You say you are trying to flash something but then you also say that everything is locked. You can't flash anything other than the stock firmware (in EDL mode) if your bootloader is locked.
Click to expand...
Click to collapse
I tried to flash it when i have everything unlocked. I tried to flash ASOP v6.6 and the result was a bricked phone. However I flashed the android one stock ROM and locked everything with the Xiaomi flash program.
You need to flash stock through EDL
Nebrassy said:
You need to flash stock through EDL
Click to expand...
Click to collapse
That's what i've done. Although, if I try to flash TWRP from fastboot I have an error message telling me that I have no slot b
gfpablo_ said:
That's what i've done. Although, if I try to flash TWRP from fastboot I have an error message telling me that I have no slot b
Click to expand...
Click to collapse
You can't flash the TWRP image from fastboot, since our phone does not have a seperate recovery partition and you also cannot flash ANYTHING (other than stock via EDL) if your phone's bootloader is locked.
Now since it seems that your bootloader is locked, you need to enable developer options first and then in developer options enable the "OEM unlocking" option. After that you need to go to fastboot in order to unlock the bootloader and use these commands one at the time:
fastboot flashing unlock
fastboot flashing unlock_critical
Keep in mind that after using these commands you will get a prompt on your phone to confirm that you want to unlock the bootloader and doing so will erase everything (basically like doing a factory reset).
After you fully unlock the bootloader, in order to flash TWRP with stock you need to go to the official TWRP website and find the .img and the .zip installer for the Mi A2. You need to boot the .img via fastboot with fastboot boot *location to the .img* (without the asterisks) and then transfer and flash the TWRP .zip installer with TWRP. After that you can boot into TWRP normally without fastboot booting.
If you want to flash a custom ROM you will still need to fastboot boot into the TWRP .img because the .zip you flashed is tied to the system, and since you need to wipe the system before flashing a custom ROM you will also wipe the flashed TWRP.
I still recommend reading this guide: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
[SOLVED]
Catsonvi said:
You can't flash the TWRP image from fastboot, since our phone does not have a seperate recovery partition and you also cannot flash ANYTHING (other than stock via EDL) if your phone's bootloader is locked.
Now since it seems that your bootloader is locked, you need to enable developer options first and then in developer options enable the "OEM unlocking" option. After that you need to go to fastboot in order to unlock the bootloader and use these commands one at the time:
fastboot flashing unlock
fastboot flashing unlock_critical
Keep in mind that after using these commands you will get a prompt on your phone to confirm that you want to unlock the bootloader and doing so will erase everything (basically like doing a factory reset).
After you fully unlock the bootloader, in order to flash TWRP with stock you need to go to the official TWRP website and find the .img and the .zip installer for the Mi A2. You need to boot the .img via fastboot with fastboot boot *location to the .img* (without the asterisks) and then transfer and flash the TWRP .zip installer with TWRP. After that you can boot into TWRP normally without fastboot booting.
If you want to flash a custom ROM you will still need to fastboot boot into the TWRP .img because the .zip you flashed is tied to the system, and since you need to wipe the system before flashing a custom ROM you will also wipe the flashed TWRP.
I still recommend reading this guide: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
Thank you! I have to admit that I have no idea of whats wrong earlier. This guide solved the problem tho.