I have unlocked my boot loader which doesn't allow you to use recovery mode. Is there a way to completely wipe the phone and undo the bootloader thing? What program can you use. Also, how can you hide the bootloader unlocked start up screen? Thanks
I want to be sure you have all your ideas straight. How comfortable are you with working from the bootloader or from recovery? What tools do you use? Can you access recovery by this method?: Hold "Power" and "Volume Down" for ten seconds and release. This takes you to the bootloader. Then press "Volume Down" once to select the recovery, then press "Volume Up" to activate that option. This should then boot into the recovery. If that is not what happens, let us know what happens instead.
I have unlocked my boot loader which doesn't allow you to use recovery mode.
Click to expand...
Click to collapse
There should be no problem using any of the various recovery modes with an unlocked bootloader. Stock, TWRP, and CWM should all work fine. Can you describe what you did, what happened, and what you expected to happen?
Is there a way to completely wipe the phone and undo the bootloader thing?
Click to expand...
Click to collapse
There are several things here. You can wipe the phone and return it to factory defaults by using "fastboot -w". This does not change your bootloader or recovery. You can re-lock you bootloader, but it will always register that the bootloader was once unlocked. There is no real benefit to relocking the bootloader so I won't put instructions here, but let me know if that's what you want to do. Finally, you can flash a new recovery image onto your device, which will wipe out whatever recovery image you had on there. The command looks like "fastboot flash recovery recovery.img".
Also, how can you hide the bootloader unlocked start up screen?
Click to expand...
Click to collapse
This is simple as flashing a new logo. The command is "fastboot flash logo logo.bin". This will overwrite the stock logo (which checks if the phone is unlocked) with a modified one which looks the same whether it is unlocked or not.
See here for details and downloads: http://forum.xda-developers.com/showthread.php?t=2548530
FaultyFirmware said:
There should be no problem using any of the various recovery modes with an unlocked bootloader. Stock, TWRP, and CWM should all work fine.
You can wipe the phone and return it to factory defaults by using "fastboot -w". Finally, you can flash a new recovery image onto your device, which will wipe out whatever recovery image you had on there. The command looks like "fastboot flash recovery recovery.img".
The command is "fastboot flash logo logo.bin". http://forum.xda-developers.com/showthread.php?t=2548530
Click to expand...
Click to collapse
I mean fastboot recovery thing if that's what you didnt think.
I can get into the recovery screen fine. Selecting recovery puts me into a no command screen and then just boots up as normally. I was expecting to get another menu with factory reset and cache reset, and factory just boots up normally. Is factory reset from the fastboot screen just the same as the reset in the settings menu? Is it that you cant use those settings with a unlocked bootloader.
Are TWRP and CWN both apps you get for/through rooting in which you can restore back up etc? I have heard about CWN but havent really used it.
Would doing "fastboot -w" just do the same as reset from settings menu? Also I'm not sure what you mean by flash a new recovery image?
Also, I dont understand how to remove the boot loader unlocked screen. You have to start a command prompt and type in that with your phone in fastboot mode?
Is recovery
Sorry for being such stupid noob pleb :good:
I think I understand the problem. The first screen you come to says "Fastboot flash mode" or something like that and has a boot mode selection menu with "Recovery" as one option. This screen is the bootloader. When you are in the bootloader, you use the fastboot command on the computer to do things to the phone.
When you select and activate the "Recovery" option, you get a screen that says "No Command". This is actually the stock recovery. TWRP is TeamWin Recovery Project and CWM is Clockwork Mod. They're both roughly the same in terms to capabilities. Both have far more features than the stock recovery. You can use adb to communicate with your phone in recovery mode.
Here is a program that will help you install the recovery. USB debugging should be turned on on your phone, and you should be booted into the system. Also be sure that the proper USB drivers are installed on your computer.
http://forum.xda-developers.com/showthread.php?t=2635706
Here is the latest version of TWRP. You should download this image and use the above application to flash it.
http://forum.xda-developers.com/showthread.php?t=2561757
As always, ready everything carefully.
Could you explain the remove bootloader screen or how to relock bootloader?
Which one would you recommend: TWRP or CWN? Thanks! :good:
Banana4Life said:
Could you explain the remove bootloader screen or how to relock bootloader?
Which one would you recommend: TWRP or CWN? Thanks! :good:
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2548530
Why you need relock bootloader ?
Use philz recovery based on last cwm. It's amazing.
Could you explain the remove bootloader screen or how to relock bootloader?
Click to expand...
Click to collapse
Here is a thread about removing the warning screen: http://forum.xda-developers.com/showthread.php?t=2548530
In summary, you can either download "logo.zip" and install it from recovery, or you can download "original_logo.zip", extract "logo.bin" and use "fastboot flash logo logo.bin" when you are booted into the bootloader. I am assuming you do not have a "Google Play Edition" or "GPE". If you do, there is a different logo for you in that thread.
The bootloader can be relocked, but it will not change the warning screen. Locking the bootloader will only make it so you cannot flash custom recoveries and such. Can you explain what you hope to achieve by relocking the phone? Again, it can be done, but I want to make sure it is really what you want.
Which one would you recommend: TWRP or CWN? Thanks!
Click to expand...
Click to collapse
You can't go wrong with either TWRP or PhilZ. PhilZ is based on CWM. It has added features and touch capabilities. Because a recovery is so easy to switch, if you make your best guess for which you will like more, and if you are not happy with it, you can switch. I like both, and most users will find all the features they need in either one.
TWRP looks like this: https://www.xda-developers.com/wp-content/uploads/2013/11/AgsV.png
It can be downloaded here: http://forum.xda-developers.com/showthread.php?t=2561757
PhilZ can be downloaded here: http://forum.xda-developers.com/showthread.php?t=2639583
Its features and screenshots are here: http://forum.xda-developers.com/showthread.php?t=2201860
Related
I've followed the rooting instruction for 2.20 and got confirmation that my CID is at 11111111. I got an unlock token and followed the instructions at htcdev.com I chose "unlock bootloader" and the phone rebooted. I installed a terminal app to see if I was rooted, and I'm not. No "su" command was available. So, I went through the root process again, from the beginning, generating a new code. This time, when I ran "fastboot flash unlocktoken Unlock_code.bin" I got confirmation in the command prompt that it worked, but nothing happened on my phone, i.e. there's no "Unlock bootloader?" screen. I can still use the volume rocker to highlight options, but I don't know what to do from here.
Does anyone have any ideas?
ctennenh said:
I've followed the rooting instruction for 2.20 and got confirmation that my CID is at 11111111. I got an unlock token and followed the instructions at htcdev.com I chose "unlock bootloader" and the phone rebooted. I installed a terminal app to see if I was rooted, and I'm not. No "su" command was available. So, I went through the root process again, from the beginning, generating a new code. This time, when I ran "fastboot flash unlocktoken Unlock_code.bin" I got confirmation in the command prompt that it worked, but nothing happened on my phone, i.e. there's no "Unlock bootloader?" screen. I can still use the volume rocker to highlight options, but I don't know what to do from here.
Does anyone have any ideas?
Click to expand...
Click to collapse
You need to flash a rooted Rom. you were on 2.20, it is a temp.root to change your cid so you can unlock your boot loader.
Did you flash teamwin recovery yet?
Sent from my HTC One XL using xda app-developers app
Not yet. I was following the instruction here: http://forum.xda-developers.com/showthread.php?t=1952038 and in this thread: http://forum.xda-developers.com/showthread.php?t=1954458 which say to get the unlock token and proceed to htcdev right after changing the CID. I thought that teamwin recovery got installed after that. Did I do something out of order? What should I do differently? Thanks.
ctennenh said:
Not yet. I was following the instruction here: http://forum.xda-developers.com/showthread.php?t=1952038 and in this thread: http://forum.xda-developers.com/showthread.php?t=1954458 which say to get the unlock token and proceed to htcdev right after changing the CID. I thought that teamwin recovery got installed after that. Did I do something out of order? What should I do differently? Thanks.
Click to expand...
Click to collapse
After you unlock your bootloader you need to flash TWRP from ADB, since you don't have SU installed.
You have to flash TWRP before doing anything on 2.20
Is your bootloader not unlocked? Retry it, make sure the unlock token is in the PRECISE format that they ask for
absolutelygrim said:
After you unlock your bootloader you need to flash TWRP from ADB, since you don't have SU installed.
You have to flash TWRP before doing anything on 2.20
Is your bootloader not unlocked? Retry it, make sure the unlock token is in the PRECISE format that they ask for
Click to expand...
Click to collapse
Retry what part? I'm sorry. Do you mean I should do the whole process from the start, or just part of it? It actually says "unlocked" at the top of the bootloader screen right now. Should I just go ahead and flash the TW openrecovery?
I downloaded the latest CM10 and ran fastboot on the boot.img. After flashing openrecovery should I be good to flash the ROM and gapps? Thanks for your help.
ctennenh said:
Retry what part? I'm sorry. Do you mean I should generate a new token?
Click to expand...
Click to collapse
Use the same token, but retry the process
Ok, I re-ran "fastboot flash unlocktoken Unlock_code.bin" with the same file. It still says "unlocked" at the top. Then I ran "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img". According to the instructions in the thread on installing custom ROMs I should do a "fastboot reboot" now before installing the ROM, but I don't want to reboot yet if it will undo the root.
ctennenh said:
Ok, I re-ran "fastboot flash unlocktoken Unlock_code.bin" with the same file. It still says "unlocked" at the top. Then I ran "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img". According to the instructions in the thread on installing custom ROMs I should do a "fastboot reboot" now before installing the ROM, but I don't want to reboot yet if it will undo the root.
Click to expand...
Click to collapse
go into adb and type "adb reboot recovery" if TWRP shows up, mount your SD and drag a ROM into your SD and the boot.img from the ROM, and then unmount your SD card. Full Wipe, flash the boot.img and the ROM and reboot.
you never really *had* root.
The 2.20 exploit is a temporary root to change your CID to 1111111, so you can permanently unlock your boot loader at anytime.
absolutelygrim said:
go into adb and type "adb reboot recovery" if TWRP shows up, mount your SD and drag a ROM into your SD and the boot.img from the ROM, and then unmount your SD card. Full Wipe, flash the boot.img and the ROM and reboot.
you never really *had* root.
The 2.20 exploit is a temporary root to change your CID to 1111111, so you can permanently unlock your boot loader at anytime.
Click to expand...
Click to collapse
I'm getting "error: device not found". Can I do the same thing through bootloader-recovery on the phone itself?
ctennenh said:
I'm getting "error: device not found". Can I do the same thing through bootloader-recovery on the phone itself?
Click to expand...
Click to collapse
Yea, you don't have to do it through adb. You know how to get into recovery?
Power off the phone, power it on, then continue to hold Volume Down and you will be at the hboot screen, then go to recovery from there
Edit: If you are already at the hboot screen you don't need to turn off your phone, just go to recovery
absolutelygrim said:
Yea, you don't have to do it through adb. You know how to get into recovery?
Power off the phone, power it on, then continue to hold Volume Down and you will be at the hboot screen, then go to recovery from there
Edit: If you are already at the hboot screen you don't need to turn off your phone, just go to recovery
Click to expand...
Click to collapse
Ok, so this is where I am on the instructions for installing a new ROM.
2. Run the following command:
'fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img' (make sure img file is in same folder as your adb stuff)
then 'fastboot reboot'
3. Run the following command after the phone is rebooted:
'adb reboot recovery'
4. You should be in the new TWRP recovery. From there it is recommended to do a factory reset before flashing the new ROM.
I've flashed twrp. Should I run "fastboot reboot" from the command line, or choose "recovery"? I appreciate your patience with me!
ctennenh said:
Ok, so this is where I am on the instructions for installing a new ROM.
2. Run the following command:
'fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img' (make sure img file is in same folder as your adb stuff)
then 'fastboot reboot'
3. Run the following command after the phone is rebooted:
'adb reboot recovery'
4. You should be in the new TWRP recovery. From there it is recommended to do a factory reset before flashing the new ROM.
I've flashed twrp. Should I run "fastboot reboot" from the command line, or choose "recovery"? I appreciate your patience with me!
Click to expand...
Click to collapse
Recovery. if you can't use adb reboot recovery use fastboot reboot instead and hold volume down until you get into the boot loader, then scroll down to reboot, hit the power button, scroll down to recovery and hit the power button again. That should put you in TWRP
After choosing recovery I get the HTC loading screen with "This build is for development purposes only..." It's rebooted a couple times on its own to this screen, so I'm concerned I'm on a reboot loop.
ctennenh said:
After choosing recovery I get the HTC loading screen with "This build is for development purposes only..." It's rebooted a couple times on its own to this screen, so I'm concerned I'm on a reboot loop.
Click to expand...
Click to collapse
Hold the power button and volume down until the phone turns off. When the screen turns off let go of the power button but not volume down. Continue holding volume down until you see your bootloader screen. It will say UNLOCKED at the top
edit: btw, when flashing boot.img, use the following command fastboot flash boot boot.img so put the boot.img in the folder with fasboot.exe and use that command. When it flashes, then you can flash your ROM
Sent from my HTC One XL using xda app-developers app
Awesome. So I've mounted my SD card and copied my gapps.zip, the ROM zip, and the flashed boot.img into the Download folder. Then I unmount, wipe, and flash the boot.img and the ROM?
ctennenh said:
Awesome. So I've mounted my SD card and copied my gapps.zip, the ROM zip, and the flashed boot.img into the Download folder. Then I unmount, wipe, and flash the boot.img and the ROM?
Click to expand...
Click to collapse
Unmount.
Wipe System
Factory Reset (wipes /data and /cache)
Flash your boot.img from fastboot using "fastboot flash boot boot.img"
Flash your ROM
Flash gapps
Reboot and enjoy
Gah! I've wiped and factory reset, and now it's "waiting for device" when I try to fastboot the boot.img. Is there some option I need to choose on TW recovery in order to run fastboot on the boot.img? I don't see a "flash" option anywhere, but the instruction on flashing new ROMs doesn't say what to do to actually flash something.
ctennenh said:
Gah! I've wiped and factory reset, and now it's "waiting for device" when I try to fastboot the boot.img. Is there some option I need to choose on TW recovery in order to run fastboot on the boot.img? I don't see a "flash" option anywhere, but the instruction on flashing new ROMs doesn't say what to do to actually flash something.
Click to expand...
Click to collapse
Reboot back into bootloader. and then boot into fastboot from your boot loader, then try the command again.
You are a fabulous human being. Thanks so much for being patient with me and helping me through this. It's been a lot tougher than I expected. Now to get to bed. I have to get up early in the morning
ctennenh said:
You are a fabulous human being. Thanks so much for being patient with me and helping me through this. It's been a lot tougher than I expected. Now to get to bed. I have to get up early in the morning
Click to expand...
Click to collapse
You got everything working? Enjoy your root, unlock, and ROM, and good night
I'm trying to load the CM ROM to my HTC One S device. I was able to unlock and root the device. Next, I flashed the boot.img (fastboot flash boot.img) from the ROM zip file to the device and restarted it (cm-10.1-20130304-EXPERIMENTAL-ville-M2). Now my device just cycles through the HTC splash screen with the red letters "this build is for development purposes only..." -> Android Splash Screen. Phone does not properly boot up. I think I missed a step in the flashing process. Any ideas on how to proceed?
fastboot flash boot boot.img
just in case you typed it the way you wrote in your post.
what recovery are you using? what version?
maybe try twrp 2.3.3
get into bootloader and flash again, go to recovery do a full wipe and install the cm zip again.
tivofool said:
fastboot flash boot boot.img
just in case you typed it the way you wrote in your post.
what recovery are you using? what version?
maybe try twrp 2.3.3
get into bootloader and flash again, go to recovery do a full wipe and install the cm zip again.
Click to expand...
Click to collapse
Sorry, the command I used was "fastboot flash boot boot.img" The CM boot.img definitely got written to the device. I missed the step of copying the ROM to a folder on my device. I wasn't clear on this step since I'm not sure how to view folders on the device. Is there a way to load the ROM from my PC instead of copying the files to the device first?
I'm using TWRP 2.6.0.0. I'm also not clear on the back up portion since there is no SD card on this device. Is it possible to perform a backup? I thought I did one during the initial step, but now that I'm trying to restore, I don't see a backup available.
yes, the "sd card" is there as a partition or whatever. But it works the same way. Backups do work.
So in twrp mount the sd card (usb storage, whatever twrp calls it), then you can transfer the rom to your phone from your computer. Then just wipe your caches and install zip.
You can get into recovery from your bootloader, hold volume down and press power (don't hold)
tivofool said:
yes, the "sd card" is there as a partition or whatever. But it works the same way. Backups do work.
So in twrp mount the sd card (usb storage, whatever twrp calls it), then you can transfer the rom to your phone from your computer. Then just wipe your caches and install zip.
You can get into recovery from your bootloader, hold volume down and press power (don't hold)
Click to expand...
Click to collapse
Thanks for clarifying. I successfully loaded the ROM on my device.
My workflow stopped at the same spot, screen is locked in the HTC logo and the warning about the build being development purpose only, but trying again to get into bootloader and the phone doesn't load it up, it just turns off and nothing else happens
Mhord said:
My workflow stopped at the same spot, screen is locked in the HTC logo and the warning about the build being development purpose only, but trying again to get into bootloader and the phone doesn't load it up, it just turns off and nothing else happens
Click to expand...
Click to collapse
Was your battery too low?
Hopefully you can get into bootloader, that's pretty important to fix anything.
someone could correct me, but can't you hold power down until the buttons flash, then hold both power and volume down button until bootloader starts.
tivofool said:
Was your battery too low?
Hopefully you can get into bootloader, that's pretty important to fix anything.
someone could correct me, but can't you hold power down until the buttons flash, then hold both power and volume down button until bootloader starts.
Click to expand...
Click to collapse
It had like 75% charge. Buttons don't flash like normal... Got to load the bootloader flashed the recovery, reboot, same screen
Mhord said:
It had like 75% charge. Buttons don't flash like normal... Got to load the bootloader flashed the recovery, reboot, same screen
Click to expand...
Click to collapse
So you are trying to get into recovery. When you go into the bootloader, you choose recovery and it doesn't work.
you could go back to bootloader, fastboot usb.
from there open a command terminal on your computer. From your fastboot folder press shift and right mouse click <open command terminal here>
type
fastboot erase cache
then you can press power button to select hboot, then volume down to recovery.
You could try to flash a different recovery if that doesnt work. Make sure you are using the correct recovery for your device. S4 version or the S3 international type devices.
tivofool said:
So you are trying to get into recovery. When you go into the bootloader, you choose recovery and it doesn't work.
you could go back to bootloader, fastboot usb.
from there open a command terminal on your computer. From your fastboot folder press shift and right mouse click <open command terminal here>
type
fastboot erase cache
then you can press power button to select hboot, then volume down to recovery.
You could try to flash a different recovery if that doesnt work. Make sure you are using the correct recovery for your device. S4 version or the S3 international type devices.
Click to expand...
Click to collapse
mmm yeah tried what you said, and still got stuck in "entering recovery".
I used eyeballer recovery which is the one CM recommends on their wiki
EDIT: My HBOOT says VilleC2 in that case S3 recovery would be the correct one?
EDIT: Yep found the correct recovery back in business, many thanks Tivofool
no access to recovery
I've got big problem. My One Mini is fine until I try to go into recovery. It refuses to go there.
I get fastboot and bootloader menus fine. It enters bootloader, but if I try to go into recovery, it just goes back to the main bootloader menu.
The problem started when I flashed CWMRecovery. Fastboot and adb recognise my phone, and accept commands, but when I try to fastboot flash recovery in it sends an error message. File not found.
I tried " fastboot boot recovery.img" but that just froze the machine .
When I try to get into recovery from rom manager or ROM toolbox pro, it takes me to the fastboot menu, not into recovery, and we're back to square one, as above.
Running android 4.3 Sense 5.5 software 2.12.401.1 Supercid 11111111
rooted and unlocked
To get the phone to work again, I have to hold power down for about 10 secs direct from fastboot/bootloader...may have to do this several times before it boots into Android.
If I turn power off from bootloader, it returns to bootloader when I power up again.
If I don't turn the phone off, once in main application, it's all OK.
Ho hum.
As I say , it works like a dream until I want to go into recovery.
Any ideas, please?
Thanks
Hi
Boblud said:
I tried " fastboot boot recovery.img" but that just froze the machine .
Click to expand...
Click to collapse
The correct command to flash the recovery is
Code:
fastboot flash recovery your_recovery_image.img
see also: wiki.cyanogenmod.org/w/Doc:_fastboot_intro
Booting into recovery should be possible with
Code:
adb reboot recovery
I didnt tried CWM on the Mini, but used it on my old Marvel. I'm satisfied with TWRP for the Mini.
greetings
Yes, thanks. I know the commands should work...but that's the trouble..they don't!
I can get into the recovery menu...HBOOT /FASTBOOT / RECOVERY and so on, but selecting "RECOVERY" simply sends me back to HBOOT menu.
I can't flash anything under FASTBOOT, either. I've been doing this sort of thing for several years without trouble....until now!
So come on chaps..thinking caps on , please.
Boblud said:
Yes, thanks. I know the commands should work...but that's the trouble..they don't!
I can get into the recovery menu...HBOOT /FASTBOOT / RECOVERY and so on, but selecting "RECOVERY" simply sends me back to HBOOT menu.
I can't flash anything under FASTBOOT, either. I've been doing this sort of thing for several years without trouble....until now!
So come on chaps..thinking caps on , please.
Click to expand...
Click to collapse
lock the bootloader RUU back to stock and start over ?
clsA said:
lock the bootloader RUU back to stock and start over ?
Click to expand...
Click to collapse
Thanks, will do when I can find ruu to download! Any pointers, please?
Uhm.... have u read Frequently Asked Questions by @KidCarter93 ?
KidCarter93 said:
[SIZE=+1]Q11: I have a custom recovery installed but I can't boot into it.[/SIZE]
Use the command - fastboot erase cache.
You should now be able to boot into recovery.
Click to expand...
Click to collapse
Maybe it helps.
Boblud said:
Thanks, will do when I can find ruu to download! Any pointers, please?
Click to expand...
Click to collapse
here's the RUU
http://www.androidruu.com/getdownlo...14_10.20.40.4408L_release_333483_signed_2.exe
clsA said:
here's the RUU
http://www.androidruu.com/getdownlo...14_10.20.40.4408L_release_333483_signed_2.exe
Click to expand...
Click to collapse
Thanks for help all round.
The RUU wouldn't run: it reported an unknown error, but having done so, it must have done something, as when I rebooted, I had access to recovery once again...briefly! Then it went again.
Anyway, I re locked / unlocked , locked a few times, and hey presto, it's sprung back into life!
I was trying to install a ROM and things got a bit messed up. I wiped system/cache/dalvik/data via TWRP. I then went to install the ROM but it failed due to only supporting hhz12h bootloader.
So now I'm kind of stuck. I can't update the bootloader because fastboot/ADB won't list the device in TWRP. Is there any way to launch an ADB server in TWRP so I can fastboot the bootloader? Doesn't look like there is.
If there's not:
Is there a TWRP zip-install hhz12h bootloader I can use? Looked around, couldn't find one.
If not I'll have to try and find/flash the original image..but fastboot is not going to happen so I have to find a zip installable one that'll work with hhz12d bootloader...which hopefully is around. Otherwise I could install literally anything just to get an ADB server so I can fastboot the hhz12h bootloader in there. Stupid problem to have right here, lol.
Any thoughts/help is appreciated. TIA.
Okay, so I got around the issue. I'm not sure if TWRP is supposed to be able to fastboot or ADB but mine would not, I was under the impression that I could fastboot or ADB in recovery. Maybe that was just a mistake on my part thinking that.
My workaround:
- Reboot into the bootloader (not TWRP recovery), 3 finger reset, power off, then power button + vol up + vol down until you get the OEM Android bootloader screen (unplug if plugged in, it didn't seem to want to go into bootloader when it was plugged in - maybe I just didn't wait long enough, but unplug if it doesn't want to go into the bootloader).
- From here I was able to fastboot, "fastboot devices" listed it
- I then flashed the bootloader: "fastboot flash bootloader bootloader-hammerhead-hhz12h.img" (may differ if you wan to flash different bootloader)
- I then rebooted into bootloader: "fastboot reboot-bootloader"
- I then flashed recovery: "fastboot flash recovery openrecovery-twrp-2.8.5.2-hammerhead.img" (may differ for different version of recovery)
- I then used vol up/vol down to select "reboot recovery", and hit the power button
- TWRP booted and from there, now that I have the hhz12h.img bootloader flashed I could install the ROM, so I wiped data/dalvik/cache/system again, installed the ROM, installed Gapps, and rebooted, good to go.
FYI ADB works into recovery mode (TWRP) and Android. Fastboot can only be used when you are in the bootloader.
You did the right thing except that it wasn't necessary to flash TWRP. Flashing a bootloader.img only erases the boot partition so the recovery isn't concerned.
Primokorn said:
FYI ADB works into recovery mode (TWRP) and Android. Fastboot can only be used when you are in the bootloader.
You did the right thing except that it wasn't necessary to flash TWRP. Flashing a bootloader.img only erases the boot partition so the recovery isn't concerned.
Click to expand...
Click to collapse
Got it. For whatever reason I could not get ADB to see the device while I was in TWRP. I tried the ADB sideload feature in 'advanced' but it just waited and waited and waited forever. I believe ADB is set up properly on my system because it works fine on ROM. Not sure what the deal is with that, but I don't have much reason to go into ADB in recovery anyway aside from this issue, so it's [hopefully] not a big deal.
As for flashing the recovery, yeah, bad habit I guess. On my old phone (Fascinate Galaxy S 1), if you had custom recovery and had to 3-finger reset to bootloader because your phone wouldn't turn on or was bootlooping or whatever the recovery was boned, had to re-odin flash it. So it's stuck in my memory now that if I had to 3 finger it I better flash recovery. I'll try to knock myself out of that habit .
Thanks!
Syndacate said:
Is there a TWRP zip-install hhz12h bootloader I can use?
Click to expand...
Click to collapse
This one works.
http://forum.xda-developers.com/showpost.php?p=60879785&postcount=1246
EDIT - Looks like the poster took it down. I'll upload and get back to you.
EDIT part deux - http://d-h.st/zEex (includes the last modem)
Also that's a really old version of twrp you flashed...
Sent from my Nexus 5 using Tapatalk
Wakamatsu said:
This one works.
http://forum.xda-developers.com/showpost.php?p=60879785&postcount=1246
EDIT - Looks like the poster took it down. I'll upload and get back to you.
EDIT part deux - http://d-h.st/zEex (includes the last modem)
Click to expand...
Click to collapse
Thanks, I'll snag that just in case I ever have a fastboot outage or I'm on a system w/o ADB/fastboot or something.
ldubs said:
Also that's a really old version of twrp you flashed...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Haha, I didn't even look at the dates, I just went to the "Tools/Utilities" page for the Nexus 5 and it was the top link....I didn't think too much on it, just figured top link = most recent = latest.
http://forum.xda-developers.com/showthread.php?t=2511507
I'll dig around for a thread which has latest and flash that on there, can't expect old versions to work flawlessly, now can we?
EDIT:
That actually might have just been a copy/paste error on my part, as I had the old TWRP lying around for fastboot and copy/pasted the name from that. I used TWRP (ROOT) app to install and I chose latest (or so I thought). Now I have literally NO idea which one I was using -_-.
No worries glad you got it sorted. You can flash an image file in twrp now BTW.
Sent from my Nexus 5 using Tapatalk
Hello everyone, i have an honor 8 frd-l09c432(europe)
so i flashed a wrong kernel in twrp and fastboot
and now the phone can't boot
i can get into fastboot and flash stuff
erecovery works in factory resetting and cache partition cleaning
my bootloader is unlocked
my phone is frp unlocked
when i flash twrp in fastboot and reboot to recovery, it doesn't boot twrp but the stock recovery ( idk why )
so anyone can help ?
and when i put my phone in charge when its off
a message appears to update again
no : 10 ( boot image
no : 2 ( load failed )
which im guessing its because of the wrong kernel flash
so what should i flash in fastboot to unbrick my phone ?
i have update.app extracted and etc ... ( please please if anyone can help )
OPTION 1: MAYBE MIGHT BE WHY FLASHING MIGHT NOT BE WORKING
Make sure that you are not trying to flash the recovery.img on the error fastboot look alike screen, because I dont think you can flash files when on that screen error screen. Try to boot into fastboot without the errors on the screen.
OPTION 2: FLASH STOCK KERNEL IMAGE
You can flash kernel images using adb:
"fastboot flash kernel [KERNEL.IMG]"
Make sure that you are not trying to flash the recovery.img on the error fastboot look alike screen, because I dont think you can flash files when on that screen error screen.
OPTION 3: IF YOU WANT TO BOOT INTO TWRP WITHOUT FLASHING
1. Connect device to computer and boot into fastboot, make sure that you are not on the error fastboot look alike screen because I dont think you can flash files when on that screen error screen.
2. On adb, do "fastboot boot [Recovery File]"
3. It should boot into the recovery file you put in there
OPTION 4:: RESET DEVICE FROM ERECOVERY FROM "recovery2"
If those did not work, restart you device and when it says "Your device has been unlocked and can't be trusted", quickly hold volume up until you have booted into a stock recovery look alike "recovery2", which has an extra button.If you do not have the button, you need to hold the volume up button faster on the "Your device has been unlocked and can't be trusted" screen. When on the stock recovery look alike screen,, click the option that says something about download latest firmware. Select your wifi and it should download stock oreo and fix device, but though, it will factory reset device.
The Honor 8 has 2 recoveries called maybe "recovery" where you usually flash twrp and "recovery2" when you hold the volume button up on "Your device has been unlocked and can't be trusted"
The bootloader should relock after this
if you manage to boot into twrp and reflash back to the kernel then you dont have to do this.
CHECK_123 said:
OPTION 1: MAYBE MIGHT BE WHY FLASHING MIGHT NOT BE WORKING
Make sure that you are not trying to flash the recovery.img on the error fastboot look alike screen, because I dont think you can flash files when on that screen error screen. Try to boot into fastboot without the errors on the screen.
OPTION 2: FLASH STOCK KERNEL IMAGE
You can flash kernel images using adb:
"fastboot flash kernel [KERNEL.IMG]"
Make sure that you are not trying to flash the recovery.img on the error fastboot look alike screen, because I dont think you can flash files when on that screen error screen.
OPTION 3: IF YOU WANT TO BOOT INTO TWRP WITHOUT FLASHING
1. Connect device to computer and boot into fastboot, make sure that you are not on the error fastboot look alike screen because I dont think you can flash files when on that screen error screen.
2. On adb, do "fastboot boot [Recovery File]"
3. It should boot into the recovery file you put in there
OPTION 4:: RESET DEVICE FROM ERECOVERY FROM "recovery2"
If those did not work, restart you device and when it says "Your device has been unlocked and can't be trusted", quickly hold volume up until you have booted into a stock recovery look alike "recovery2", which has an extra button.If you do not have the button, you need to hold the volume up button faster on the "Your device has been unlocked and can't be trusted" screen. When on the stock recovery look alike screen,, click the option that says something about download latest firmware. Select your wifi and it should download stock oreo and fix device, but though, it will factory reset device.
The Honor 8 has 2 recoveries called maybe "recovery" where you usually flash twrp and "recovery2" when you hold the volume button up on "Your device has been unlocked and can't be trusted"
The bootloader should relock after this
if you manage to boot into twrp and reflash back to the kernel then you dont have to do this.
Click to expand...
Click to collapse
Hi, Thanks for the fully informative reply
I got my phone unbricked a week after this thread but somehow i completely forgot to close the thread
so, sorry about my mistake, I'm new to xda
have a nice day