hello guys. i've recently bought a M7_UL (i believe it's the unlocked, international version) that has S-OFF with locked bootloader. some people say you still can flash recovery since you're S-OFF, others, that even if when S-OFF, you still have to unlock bootloader in order to flash a recovery. well, i can't do none of these. everything is properly installed (device drivers, most recent Mini ADB and Fastboot and TWRP) but some commands such as "adb devices" (though changing "adb" to "fastboot" actually shows my device) and "fastboot flash recovery xxx.img", simply doesn't work. i've also tried the HTCdev method but "fastboot oem get_identifier_token" command gives me nothing. also tried this tutorial here --> https://forum.xda-developers.com/showthread.php?t=2470340 but the cmd doesn't even recognize this "echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 " line. what am i doing wrong?
i really didn't want to create this topic and did quite a research, but every tutorial i've found so far didn't work for me. heeelppp :crying:
manofawker said:
hello guys. i've recently bought a M7_UL (i believe it's the unlocked, international version) that has S-OFF with locked bootloader. some people say you still can flash recovery since you're S-OFF, others, that even if when S-OFF, you still have to unlock bootloader in order to flash a recovery. well, i can't do none of these. everything is properly installed (device drivers, most recent Mini ADB and Fastboot and TWRP) but some commands such as "adb devices" (though changing "adb" to "fastboot" actually shows my device) and "fastboot flash recovery xxx.img", simply doesn't work. i've also tried the HTCdev method but "fastboot oem get_identifier_token" command gives me nothing. also tried this tutorial here --> https://forum.xda-developers.com/showthread.php?t=2470340 but the cmd doesn't even recognize this "echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 " line. what am i doing wrong?
i really didn't want to create this topic and did quite a research, but every tutorial i've found so far didn't work for me. heeelppp :crying:
Click to expand...
Click to collapse
The first thing you need to know is that adb commands will only works when the phone is booted in a custom recovery or when booted in the rom (the "USB debugging" option must be turned on to use adb from the rom, not required when using from a custom recovery).
When the phone is booted in bootloader mode, only fastboot commands will work (and fastboot commands will not works when in recovery or when in the rom).
If your phone is S-OFF you can definitively flash a recovery even if the bootloader is locked. But the method used to flash it is different then the usual method (the "fastboot flash recovery name_of_recovery.img" command will only work with an unlocked bootloader). You'll need to zip the custom recovery .img file with an android-info.txt file matching your phone info and flash that zip file from RUU mode.
i.e:
Code:
fastboot oem rebootRUU
phone will reboot in ruu mode, a black screen with silver HTC logo
Code:
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
where "firmware.zip" is the file containing your recovery .img file and the android-info.txt file
Code:
fastboot reboot-bootloader
I can make you a "firmware.zip" file if you're unsure how to do it. If you need it just reply what custom recovery version you need and post your "fastboot getvar all" output so I know your phone info (hide your imei)
Once the recovery is flashed, you can boot in recovery and unlock the bootloader using the tutorial you've linked. This method of unlocking the bootloader will not wipe your phone.
alray said:
The first thing you need to know is that adb commands will only works when the phone is booted in a custom recovery or when booted in the rom (the "USB debugging" option must be turned on to use adb from the rom, not required when using from a custom recovery).
When the phone is booted in bootloader mode, only fastboot commands will work (and fastboot commands will not works when in recovery or when in the rom).
If your phone is S-OFF you can definitively flash a recovery even if the bootloader is locked. But the method used to flash it is different then the usual method (the "fastboot flash recovery name_of_recovery.img" command will only work with an unlocked bootloader). You'll need to zip the custom recovery .img file with an android-info.txt file matching your phone info and flash that zip file from RUU mode.
i.e:
Code:
fastboot oem rebootRUU
phone will reboot in ruu mode, a black screen with silver HTC logo
Code:
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
where "firmware.zip" is the file containing your recovery .img file and the android-info.txt file
Code:
fastboot reboot-bootloader
I can make you a "firmware.zip" file if you're unsure how to do it. If you need it just reply what custom recovery version you need and post your "fastboot getvar all" output so I know your phone info (hide your imei)
Once the recovery is flashed, you can boot in recovery and unlock the bootloader using the tutorial you've linked. This method of unlocking the bootloader will not wipe your phone.
Click to expand...
Click to collapse
hi, alray, thanks for taking the time to answer me. i'd like you to make this firmware.zip for me but "fastboot getvar all" gives me this
Code:
C:\miniadb_m7>fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 0.005s
what's wrong?
manofawker said:
The first thing you need to know is that adb commands will only works when the phone is booted in a custom recovery or when booted in the rom (the "USB debugging" option must be turned on to use adb from the rom, not required when using from a custom recovery).
When the phone is booted in bootloader mode, only fastboot commands will work (and fastboot commands will not works when in recovery or when in the rom).
If your phone is S-OFF you can definitively flash a recovery even if the bootloader is locked. But the method used to flash it is different then the usual method (the "fastboot flash recovery name_of_recovery.img" command will only work with an unlocked bootloader). You'll need to zip the custom recovery .img file with an android-info.txt file matching your phone info and flash that zip file from RUU mode.
i.e:
phone will reboot in ruu mode, a black screen with silver HTC logo
where "firmware.zip" is the file containing your recovery .img file and the android-info.txt file
hi, alray, thanks for taking the time to answer me. i'd like you to make this firmware.zip for me but "fastboot getvar all" gives me this
what's wrong?
Click to expand...
Click to collapse
Are there only one android device connected to your computer ("fastboot devices" listing only your phone?)
alray said:
Are there only one android device connected to your computer ("fastboot devices" listing only your phone?)
Click to expand...
Click to collapse
yes, just the one i'm trying to flash recovery
manofawker said:
yes, just the one i'm trying to flash recovery
Click to expand...
Click to collapse
what about:
Code:
fastboot oem dmesg
and
Code:
fastboot oem last_dmesg
Tried on another computer?
alray said:
what about:
Code:
fastboot oem dmesg
and
Code:
fastboot oem last_dmesg
Tried on another computer?
Click to expand...
Click to collapse
none of these worked. strangely enough, commands like "fastboot reboot" and "fastboot devices" actually do something... i've tried to execute the cmd in compatibility mode, but it was in vain. tomorrow i'm gonna try all of this on my friend's PC and let you know if i have any success.
Related
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
*UPDATE* - Sorry, forgot to mention that I've idiotically re-locked the bootloader. Unlocking the bootloader would probably get rid of the "signature verify fail" message. I'm unable to flash the recovery because the bootloader is locked and I can't get into the filesystem because the phone needs to go into the OS for that.
When I try to unlock the bootlader by using "fastboot flash unlocktoken Unlock_code.bin" it gives me the error: "cannot open 'Unlock_code.bin'."
I need to be able to access and make changes to the file system by using fastboot commands and I have no idea how to do this.
*UPDATE #2* - I've managed to re-unlock the bootlader (I didn't have the Unlock_code.bin file in the same directory as the current directory in my cmd window). I've re-flashed the recovery successfully. Now when I reboot, it goes into recovery mode (still can't boot into the OS). I'm using ClockWorks for the recovery.
Now I'm unable to root the phone. I'm trying to write SuperSU v1.65 to the phone by using the command: "fastboot flash zip UPDATE-SuperSU-v1.65.zp" and I get the error message: "remote: not allowed."
I can flash the recovery.img and boot.img (can't flash system.img because there's "not enough space"), but I can't flash .zip files
When I try flashing another boot.img, I still get the same thing. The phone goes to the boot screen and can't boot. Then, it reboots and goes automatically into recovery (I can still get into the bootloader and recovery).
Any suggestions to get past these permissions?
bkhosh2 said:
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
Click to expand...
Click to collapse
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
superbellefleche said:
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
Click to expand...
Click to collapse
I'm sorry, but I'm kind of a noob. How exactly do I re-flash a recovery. do I do this using the command: "fastboot flash recovery recovery.img" or should I try "fastboot flash zip filname.zip" (RUU.zip) again?
*UPDATE* - I've tried erasing the cache and re-flashing the recovery and I still get the error message: "signature verify fail."
I'm still waiting for someone to help me. Is anyone going to help me fix my problem or is my HTC One doomed?
If you are on Telus
Download http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
SaHiLzZ said:
If you are on Telus
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
Click to expand...
Click to collapse
I've already tried that. When the bootloader is locked, I get the error: "signature verify fail."
OK.. Unlock bootloader, flash custom recovery, adb push this file: http://www.htc1guru.com/2013/11/guru-reset-3-22-661-1/, and install it from recovery.
SaHiLzZ said:
OK.. Unlock bootloader, flash custom recovery, adb push this file
Click to expand...
Click to collapse
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
bkhosh2 said:
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
Click to expand...
Click to collapse
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
clsA said:
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Click to expand...
Click to collapse
I Installed the TWRP recovery instead of the ClockWorkMod and adb command work! Never using ClockWork ever again!
SaHiLzZ said:
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
Click to expand...
Click to collapse
I Installed TWRP and went into the TWRP recovery and noticed the adb commands work.
That file didn't work, however the Guru file you mentioned earlier did (with the "adb push" command)! Thanks so much for your help! Everything is working perfectly again!
Thanks for posting back. Edit your title to [SOLVED]! and enjoy!
I want to return to stock so I can take an OTA. I am currently running Sprint 4.3, rooted, unlocked bootloader, S-ON, software version 3.04.651.2.
I have been reading up on the proper way to return to stock and just want to double check that I have the right information before i break something.
1. Download 3.04.651.2 RUU (or do I want 4.06.651.4 or 4.06.651.2?)
2. USB debugging turned on
3. nandriod
4. go into fastboot
5. Connect phone to computer and go to Andriod SDK folder platform-tools and open a command window
6. type fastboot oem lock in the command window
7. go back to fastboot and run the RUU (how exactly do I run the RUU?)
8. Am I done now? Will these steps give me the stock rom, locked bootloader and stock recovery?
is this how I flash the RUU from the command window?
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip (if filename = firmware.zip)
Fastboot reboot
Thanks for the clarification.
Kev1jm2 said:
I want to return to stock so I can take an OTA. I am currently running Sprint 4.3, rooted, unlocked bootloader, S-ON, software version 3.04.651.2.
I have been reading up on the proper way to return to stock and just want to double check that I have the right information before i break something.
1. Download 3.04.651.2 RUU (or do I want 4.06.651.4 or 4.06.651.2?)
2. USB debugging turned on
3. nandriod
4. go into fastboot
5. Connect phone to computer and go to Andriod SDK folder platform-tools and open a command window
6. type fastboot oem lock in the command window
7. go back to fastboot and run the RUU (how exactly do I run the RUU?)
8. Am I done now? Will these steps give me the stock rom, locked bootloader and stock recovery?
is this how I flash the RUU from the command window?
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip (if filename = firmware.zip)
Fastboot reboot
Thanks for the clarification.
Click to expand...
Click to collapse
If you have a (S-ON) device you can go to OMJ's thread and run the RUU.exe for instructions:
http://forum.xda-developers.com/showthread.php?t=2658910
read the instructions under the image on the page...
If you want to flash the modified firmware you need (S-OFF), then you would follow these instructions:
I downloaded 4.06.651.4..
then renamed 4.06.651.4.zip to "firmware.zip"..
then moved firmware.zip to 'where-ever fastboot & adb are installed'..
then open command prompt in that folder..
then rebooted to bootloader..
plug phone through USB port, phone should say FASTBOOT USB
cmd: "fastboot oem rebootRUU" (without quotes of course)
cmd: "fastboot flash zip firmware.zip"
cmd: "fastboot reboot" (to reboot)
Hope this helps!
predator1584 said:
If you have a (S-ON) device you can go to OMJ's thread and run the RUU.exe for instructions:
http://forum.xda-developers.com/showthread.php?t=2658910
read the instructions under the image on the page...
If you want to flash the modified firmware you need (S-OFF), then you would follow these instructions:
I downloaded 4.06.651.4..
then renamed 4.06.651.4.zip to "firmware.zip"..
then moved firmware.zip to 'where-ever fastboot & adb are installed'..
then open command prompt in that folder..
then rebooted to bootloader..
plug phone through USB port, phone should say FASTBOOT USB
cmd: "fastboot oem rebootRUU" (without quotes of course)
cmd: "fastboot flash zip firmware.zip"
cmd: "fastboot reboot" (to reboot)
Hope this helps!
Click to expand...
Click to collapse
The OMJ thread says its for 4.06.651.4. I have 3.04.651.2. Is that a problem or can I still use it?
Kev1jm2 said:
The OMJ thread says its for 4.06.651.4. I have 3.04.651.2. Is that a problem or can I still use it?
Click to expand...
Click to collapse
The 4.06.651.4 RUU is the same as taking the OTA but...it will wipe your device
I would suggest getting s-off before you go any further it will save you headaches down the road.
Kev1jm2 said:
The OMJ thread says its for 4.06.651.4. I have 3.04.651.2. Is that a problem or can I still use it?
Click to expand...
Click to collapse
no luck with the s-off way. got a file size error in cmd. trying the s-on version now.
Nope, got another error. Something about using an incorrect ruu. Bootloader is locked now though...And now its unlocked again. going to try OMJ's tool with the 3.04.651.2 ruu
OMJ's tool worked when my software version matched the tool's version. getting the OTA now. Apparently you cant jump software versions.
Thanks for your help.
Kev1jm2 said:
no luck with the s-off way. got a file size error in cmd. trying the s-on version now.
Nope, got another error. Something about using an incorrect ruu. Bootloader is locked now though...And now its unlocked again. going to try OMJ's tool with the 3.04.651.2 ruu
OMJ's tool worked when my software version matched the tool's version. getting the OTA now. Apparently you cant jump software versions.
Thanks for your help.
Click to expand...
Click to collapse
I did not have to relock my phone to RUU it for a repair at HTC. If you run into trouble just reapply your token.bin file to re unlock dev mode and try again. I agree though S-OFF is the way to go if you can sort it out.
I've accidentally erased everything on my HTC One, including the ROM I had on there and the ROM install file. I am now stuck in the Bootloader screen and only options I have are to enter TWRP v2.6.3.3. Is there a way that I can flash a ROM via USB in the Bootloader? I've tried resetting my phone and it comes up with the HTC logo on the white screen and won't boot.
return to stock rom
Chaos Water2 said:
I've accidentally erased everything on my HTC One, including the ROM I had on there and the ROM install file. I am now stuck in the Bootloader screen and only options I have are to enter TWRP v2.6.3.3. Is there a way that I can flash a ROM via USB in the Bootloader? I've tried resetting my phone and it comes up with the HTC logo on the white screen and won't boot.
Click to expand...
Click to collapse
Restart from scratch find the ruu.exe for your phone make sure it has the right specs of your phone (android,sense,and service provider) once found follow these instructions
1.) Go to Fastboot
2.) Run the commands
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
3.) Run the RUU
The first command locks your bootloader (allowing RUU), the third command allows the RUU to run on your phone without having to actually boot all the way (normally it just boots into this screen for you).
This will put you back to ur stock Rom when rooting again make sure to make backups of everything or you will have same problem again
Make sure you have all the updated drivers for your computer
Chaos Water2 said:
I've accidentally erased everything on my HTC One, including the ROM I had on there and the ROM install file. I am now stuck in the Bootloader screen and only options I have are to enter TWRP v2.6.3.3. Is there a way that I can flash a ROM via USB in the Bootloader? I've tried resetting my phone and it comes up with the HTC logo on the white screen and won't boot.
Click to expand...
Click to collapse
adb works in custom recovery, you can push, sideload, or OTG a ROM to your phone,
check the Frequently Asked Question sticky page 3
smokeytime420 said:
Restart from scratch find the ruu.exe for your phone make sure it has the right specs of your phone (android,sense,and service provider) once found follow these instructions
1.) Go to Fastboot
2.) Run the commands
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
3.) Run the RUU
The first command locks your bootloader (allowing RUU), the third command allows the RUU to run on your phone without having to actually boot all the way (normally it just boots into this screen for you).
This will put you back to ur stock Rom when rooting again make sure to make backups of everything or you will have same problem again
Make sure you have all the updated drivers for your computer
Click to expand...
Click to collapse
A RUU.exe file only requires the bootloader locked if S-ON. When the bootloader is locked, the RUU is executed with a double click in Windows. There is no need to do the other steps in 2, they are only needed if the RUU is a zip file. Here are the steps for flashing RUU.zip:
In bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader
that is true
majmoz said:
A RUU.exe file only requires the bootloader locked if S-ON. When the bootloader is locked, the RUU is executed with a double click in Windows. There is no need to do the other steps in 2, they are only needed if the RUU is a zip file. Here are the steps for flashing RUU.zip:
In bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader
Click to expand...
Click to collapse
That is true method is similar but this is how I got my phone to return to stock be for I could go anywhere else I tryed reflashing a recovery it didn't take I even tryed flashing the ruu.zip through fastboot it always failed on me since I couldn't go any further than that I searched other methods of flashing ruu that's what I came across and it worked for me also if you have s-off this usually turns it back on it did for me on step 2 not all of those steps are needed but the last one is what gets the phone ready to receive the info from the ruu.exe being run on a computer
Hi,
I'm in desperate need of some help and am not sure what to do. My HTC One m7 got stuck in Cyanogenmod Simple Recovery after the latest update. It will keep rebooting back into Simple Recovery. Is there any way to get my phone back either to stock or to Cyanogenmod?
I always just left it on Cyanogenmod so I'm not very familiar with flashing or other programs. If anyone has any advice, could you please point me to the correct tutorials and downloads?
I am at a complete loss with how to get my phone to its original state.
Perez92 said:
Hi,
I'm in desperate need of some help and am not sure what to do. My HTC One m7 got stuck in Cyanogenmod Simple Recovery after the latest update. It will keep rebooting back into Simple Recovery. Is there any way to get my phone back either to stock or to Cyanogenmod?
I always just left it on Cyanogenmod so I'm not very familiar with flashing or other programs. If anyone has any advice, could you please point me to the correct tutorials and downloads?
I am at a complete loss with how to get my phone to its original state.
Click to expand...
Click to collapse
Follow this nkk71's Return to 100% Stock Guide!
majmoz said:
Follow this nkk71's Return to 100% Stock Guide!
Click to expand...
Click to collapse
Thank you for the response, however my biggest issue is getting out of simple recovery. How do I install a new recovery, such as TWRP or CWM at the simple recovery screen and how do I flash the latest cyanogenmod rom?
Perez92 said:
Thank you for the response, however my biggest issue is getting out of simple recovery. How do I install a new recovery, such as TWRP or CWM at the simple recovery screen and how do I flash the latest cyanogenmod rom?
Click to expand...
Click to collapse
You will have to flash CWM recovery in bootloader/FASTBOOT USB. You can get the recovery from http://www.clockworkmod.com/rommanager find your phone then download the recovery.
In bootloader/FASTBOOT USB, flash CWM recovery (either rename the file CWM.img or type the whole name in place of CWM):
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
majmoz said:
You will have to flash CWM recovery in bootloader/FASTBOOT USB. You can get the recovery from http://www.clockworkmod.com/rommanager find your phone then download the recovery.
In bootloader/FASTBOOT USB, flash CWM recovery (either rename the file CWM.img or type the whole name in place of CWM):
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Thank you for replying.
So from what I'm understanding is that I will need to use ADB to sideload the recovery onto my phone, correct?
I'm not sure what the bootloader/FASTBOOT USB you refer to, I feel like I need it to be ELI5. My brain is melting when trying to read this.
P.S. I am STUCK in Cyanogenmod Simple Recovery. I am not able to power down the device or get to any other screen.
Perez92 said:
Thank you for replying.
So from what I'm understanding is that I will need to use ADB to sideload the recovery onto my phone, correct?
I'm not sure what the bootloader/FASTBOOT USB you refer to, I feel like I need it to be ELI5. My brain is melting when trying to read this.
Click to expand...
Click to collapse
No, you can not load the recovery with sideload. Have ADB & Fastboot installed on your computer, place the recovery file in the same folder and connect your phone to the computer.
Open a command window in the folder where ADB & fastboot reside.
Type: adb reboot bootloader
When the screen on your phone shows the white bootloader screen in blue will be FASTBOOT USB
Type one line at a time waiting until the cmd screen states OK or something similiar:
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
Here is a guide on fastboot commands.
majmoz said:
No, you can not load the recovery with sideload. Have ADB & Fastboot installed on your computer, place the recovery file in the same folder and connect your phone to the computer.
Open a command window in the folder where ADB & fastboot reside.
Type: adb reboot bootloader
When the screen on your phone shows the white bootloader screen in blue will be FASTBOOT USB
Type one line at a time waiting until the cmd screen states OK or something similiar:
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
Here is a guide on fastboot commands.
Click to expand...
Click to collapse
So I was able to get my device past the first prompt. I now see the white bootloader screen and it does say "FASTBOOT USB". I downloaded the latest TWRP and placed it in the same folder as ADB and Fastboot. I did the second command to flash it, however I keep getting the error "error: cannot open 'TWRP.img'. Any idea as to what I could be doing wrong?
majmoz said:
No, you can not load the recovery with sideload. Have ADB & Fastboot installed on your computer, place the recovery file in the same folder and connect your phone to the computer.
Open a command window in the folder where ADB & fastboot reside.
Type: adb reboot bootloader
When the screen on your phone shows the white bootloader screen in blue will be FASTBOOT USB
Type one line at a time waiting until the cmd screen states OK or something similiar:
fastboot flash recovery CWM.img
fastboot erase cache
fastboot reboot-bootloader
Here is a guide on fastboot commands.
Click to expand...
Click to collapse
Got it to work. Used adb to get into fastboot. Then opened up the CM installer and let it redownload cyanogenmod onto my phone.
Thanks for the help!
I unlocked the bootloader, when I boot my phone it gives a warning saying that the bootloader is unlocked and I need to press the power button to proceed, when I go into fastboot it shows the status as unlocked.
That said, any fastboot commands I issue, apart from reboot, returns the remote: unknown command error. ADB works fine, it's just fastboot.
To be more specific, I tried the following commands with no success:
fastboot erase system
fastboot oem unlock
fastboot flashing unlock
fastboot flash system file.img
fastboot -u flash system file.img
Samsung phones don't have normal fastboot
3mel said:
Samsung phones don't have normal fastboot
Click to expand...
Click to collapse
So how do I flash an image on them?
senpi0 said:
So how do I flash an image on them?
Click to expand...
Click to collapse
depends on what you wanna flash I guess, Odin is used mostly, but that's .tar archives. if you have TWRP there's that. if you're rooted kernels and recoveries can be flashed from a booted system.