Database Info

[Q] Can't reboot system without going through fast boot.

Like the title says, my Nexus 5 won't boot unless I manually plug it in, hold down volume buttons and power, then wait 15 seconds for fast boot to appear, and then select "start."
Thats the problem. Now for some more information:
1. Nexus 5 32 gb
2. ROM: CM 11 Dec 13s Nightly
3. Kernel: Bricked 3.4.0
4. The phone is totally functional. The only thing wrong with it is that it can't reboot. From the system, TWRP recover, or anything, it simply will not reboot. Every time I must go into fast boot then press the power button when it says "start." After this, the phone works just as I would expect it to. I can still flash kernels and backups through recovery, it just must be restarted manually through the fast boot. This is a problem for me because I don't always want to have to plug it in when I want to reboot it.
When did it start:
Let me start off by saying that I thing the root of all my problems was the TouchControl app that allows the knock to wake function to work. I downloaded the app and was told to install the developers custom kernel. I did and not only did the app not work, it also seemed to brick my phone. I was scared, but, after doing some research, I found the method of plugging it in and holding down all buttons for about 15 seconds and my phone was saved. Ever since then there has been the problem. I must always do this to reboot my phone. Since the app didn't work I decided to install the Bricked Kernel and everything went fine except that I wasn't prompted with the interactive installer. The kernel works fine and I am now using the Knock to wake feature built into the kernel and am very happy.
Seems to be caused by swipe2wake aka knock 2 wake aka knock knock (but not totally sure)
What I've Tried (don't assume I've tried something I haven't. I could have missed something obvious.):
1. Resetting permissions through TWRP (just thought I'd try)
2. Putting back CM 11 Kernel
3. Restoring to a time when my phone did restart
Any help would be greatly appreciated. I will try to keep the original post updated with everything I try.
FIXED with the help of jd1639 and meangreenie
------------------------------------------------------------------
1.Follow jd1639's link in 3rd comment to the page and
A. Install adb and flashboot drivers
B. Install your version of factory images from google (if you are running 4.4.2 get the image for 4.4.2)
2. Plug in phone to AC CHARGER and hold down power and volume buttons for up to 20 seconds. This should put it into fast boot mode
3. After getting phone in fast boot mode, plug it into your mac or pc.
4. Out of all the instructions in the "How to flash a factory image" thread go to method 2 and ONLY DO THE FIRST TWO LINES OF CODE. All that needs to be flashed is the bootloader.img
5. After it says complete and your phone restarts you should be able to push "start" on your phone and be good!

I would try and fastboot flash boot boot.img. where boot.img is the boot image from the factory image.

jd1639 said:
I would try and fastboot flash boot boot.img. where boot.img is the boot image from the factory image.
Click to expand...
Click to collapse
So that's essentially flashing the stock ROM?

benaside said:
So that's essentially flashing the stock ROM?
Click to expand...
Click to collapse
No just the boot.img
Edit, look at method #2 but only flash the boot.img nothing else http://forum.xda-developers.com/showthread.php?p=47156064

jd1639 said:
No just the boot.img
Edit, look at method #2 but only flash the boot.img nothing else http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
Thanks so much for trying to help. I installed all the things and flashed Boot.img from fast boot, but once I restarted my phone everything was messed up (booted to home screen but basically the system started failing). After this, I retried but deleted my cache and delvik cache. This time the system simply wouldn't boot. Luckily I backed up and restored to my previous version. Thanks for trying, but this did not work.

benaside said:
Thanks so much for trying to help. I installed all the things and flashed Boot.img from fast boot, but once I restarted my phone everything was messed up (booted to home screen but basically the system started failing). After this, I retried but deleted my cache and delvik cache. This time the system simply wouldn't boot. Luckily I backed up and restored to my previous version. Thanks for trying, but this did not work.
Click to expand...
Click to collapse
Were you on 4.4 or 4.4.2. Sounds like 4.4.2. The factory image in the link was 4.4

jd1639 said:
Were you on 4.4 or 4.4.2. Sounds like 4.4.2. The factory image in the link was 4.4
Click to expand...
Click to collapse
I downloaded the folder for 4.4.2 from the link developers.google .com/android/nexus/images#hammerhead

try reflashing via custom recovery or fastboot.. bootloader, recovery and suitable boot.img for your rom, maybe give the radio a reflash too

meangreenie said:
try reflashing via custom recovery or fastboot.. bootloader, recovery and suitable boot.img for your rom, maybe give the radio a reflash too
Click to expand...
Click to collapse
Will this'd elite all my files and unroot?
Btw thanks so much for the help

benaside said:
Will this'd elite all my files and unroot?
Btw thanks so much for the help
Click to expand...
Click to collapse
no it won't delete your data.. but please triple check your files and fastboot commands before executing
the last resort is to format data if all else fails

Thank you both so much. I have (with both of your help fixed it). I will post how in the original post. Thanks again.

Bricked my phone need help please!

Today I accidently wiped my internal and external sd card from twrp recovery mode. I was on Lolipop 5.1.
As I wanted to install Cyanogenmod Rom I tried to reflash CWM recovery. Ater doing that I was not able to enter the twrp recovery anymore. I had accecs to the unlocked bootloader and tried to reinstall the boot, recovery and system via fastboot but without any success. The phone did not boot and I couldnt enter recovery mode anymrore.
Now I accidently flashed via fastboot a wrong boot and recovery firmware (4.1) and since that I can not even enter fastboot. The pictre shows where I am stuck. On the bootloader page it says:
Error
Func NO: 10 (FUNC_BOOT_RECOVERY)
Error NO: 2
Can somebody help me to repair my device? Its brandnew.
What can I do without a recovery, without a system and without fastboot.
Here is the picture:
hxxp://s21.postimg.org/tqzu1wlhj/IMG_0191.jpg

balpem said:
Today I accidently wiped my internal and external sd card from twrp recovery mode. I was on Lolipop 5.1.
As I wanted to install Cyanogenmod Rom I tried to reflash CWM recovery. Ater doing that I was not able to enter the twrp recovery anymore. I had accecs to the unlocked bootloader and tried to reinstall the boot, recovery and system via fastboot but without any success. The phone did not boot and I couldnt enter recovery mode anymrore.
Now I accidently flashed via fastboot a wrong boot and recovery firmware (4.1) and since that I can not even enter fastboot. The pictre shows where I am stuck. On the bootloader page it says:
Error
Func NO: 10 (FUNC_BOOT_RECOVERY)
Error NO: 2
Can somebody help me to repair my device? Its brandnew.
What can I do without a recovery, without a system and without fastboot.
Here is the picture:
hxxp://s21.postimg.org/tqzu1wlhj/IMG_0191.jpg
Click to expand...
Click to collapse
So (Vol-) + (Power) w/ usb plugged in doesn't bring it to recovery mode? Have you tried with HiSuite?

jfer671 said:
So (Vol-) + (Power) w/ usb plugged in doesn't bring it to recovery mode? Have you tried with HiSuite?
Click to expand...
Click to collapse
No because I had twrp recovery installed and tried to flash cwm over it. After that I had no recovery at all. But I made some progress now... I am able to flash the same newest twrp 2.8.7.0 recovery to the phone and I managed also to flash the 5.1 stock recovery. I flashed BOOT.img from 5.1 and SYSTEM.img from 5.1 and I got rid of the error in fastboot menu.
Stock recovery I can flash via installer_r24.4.1-windows from acbka.
http://forum.xda-developers.com/mate-7/orig-development/tool-android-4-4-5-1-pc-t3186984
And these two recoveries seems to be the only one that work on my phone....? Currently I have stock recovery installed and i put MT7-L09C900B324 on my sd card (dload/UPDATE.app) and did the three buttons rescue. It seemed to work but It stoped at 90% and still no luck. What am I doing wrong this time?
Hi Suite does not recognitze the phone. When I abort the istallation and reboot the phone starts with the Huawei Logo and goes black and starts to the Huawei logo and goes black and so on...
Here is a picture of where i am stuck at 90% right now, so close...:
hxxp://s13.postimg.org/p093toz5z/IMG_0192.jpg

SOLVED
After a 36 hour marathon my mate 7 is back and working. the trick was to flash the stock recovery for all Lollipop versions wich can be foudn here: http://forum.xda-developers.com/mat...8-7-0-mate7-android-5-1-t3156779/post61958212 via linux. I somehow seem to have had trouble over wndows.
And after that do the three button rescue with the newest B 324 firmware which I have had installed before I destroyed my OS..
and my camera is now running normaly which was the initial reason i tried to install a other firmare.
:laugh:

balpem said:
...the trick was to flash the stock recovery for all Lollipop versions
Click to expand...
Click to collapse
When you say flash stock recovery for all LP versions, did you flash and then reboot each time? or flash over and when complete, flash over again still on fastboot?
Can you briefly describe in steps? Tnx! and Glad you were able to recover

jfer671 said:
When you say flash stock recovery for all LP versions, did you flash and then reboot each time? or flash over and when complete, flash over again still on fastboot?
Can you briefly describe in steps? Tnx! and Glad you were able to recover
Click to expand...
Click to collapse
I flashed via fastboot the stock recovery which you can download via the link above. the provider (user rowihel2012) claims, that this recovery works for all lolipop stock roms.
After that I made a reboot and pressed (power button and volume+) to check if its installed.
Than I downloaded the lollipop version I have had previously installed. In my case this was the B324 European version.
I put it on my sd card (dload/UPDATE.app) and launched the phone with the three button rescue method. The recovery recognized the rom on the sdcard and started to flash the OS.
After less than 5 min, my phone was restored.
I have made the experience, when using certain roms (B324, B308 etc..) with certain stock recoveries, I was not able to flash the OS and the recovery stoped always at 90%.
The recovery linked above seems to work great for the B324 version, I haven't tried any other stock roms with it.

I wonder if this will work for B327? Seems the actual last update for LP was B324, now I can't seem to get out of this firmware to go back to KK. When I flash transition B300, it's successful...but for some odd reason, when I flash 137, 143, 145 or 148...I auto go back to B327. This, after the fact I'm flashing those firmware's recoveries. Any ideas what I might do to get out of 327?
---------- Post added at 01:42 PM ---------- Previous post was at 01:38 PM ----------
Also, what's this Vol+ and Power technique?, all I get is the three menu screen (reboot, factory reset and format cache).

jfer671 said:
I wonder if this will work for B327? Seems the actual last update for LP was B324, now I can't seem to get out of this firmware to go back to KK. When I flash transition B300, it's successful...but for some odd reason, when I flash 137, 143, 145 or 148...I auto go back to B327. This, after the fact I'm flashing those firmware's recoveries. Any ideas what I might do to get out of 327?
---------- Post added at 01:42 PM ---------- Previous post was at 01:38 PM ----------
Also, what's this Vol+ and Power technique?, all I get is the three menu screen (reboot, factory reset and format cache).
Click to expand...
Click to collapse
You can try this recovery above which should work for all lollipop roms but I have no better idea as I have had basicly the same problem and could only flash the former rom i had installed whch was B324.
The Vol+ and Power i do to get into the recovery menu (the three menu screen) to check if the recovery was flashed successfully. I have had often the problem after flashing a recovery that it did not work. this is to check if the recovery works.
When i tried to flash a cwm recovery, i couldnt enter any recovery mode after that anymore. I panicked at this point but than i realised that not all recoveries did work for me. For example I could never flash a CWM recovery, not sure why. Maybe because I tried to flash a 4.4 recovery and I had a 5.1 BOOT.img installed?

balpem said:
After a 36 hour marathon my mate 7 is back and working. the trick was to flash the stock recovery for all Lollipop versions wich can be foudn here: http://forum.xda-developers.com/mat...8-7-0-mate7-android-5-1-t3156779/post61958212 via linux. I somehow seem to have had trouble over wndows.
And after that do the three button rescue with the newest B 324 firmware which I have had installed before I destroyed my OS..
and my camera is now running normaly which was the initial reason i tried to install a other firmare.
:laugh:
Click to expand...
Click to collapse
balpem said:
You can try this recovery above which should work for all lollipop roms but I have no better idea as I have had basicly the same problem and could only flash the former rom i had installed whch was B324.
The Vol+ and Power i do to get into the recovery menu (the three menu screen) to check if the recovery was flashed successfully. I have had often the problem after flashing a recovery that it did not work. this is to check if the recovery works.
When i tried to flash a cwm recovery, i couldnt enter any recovery mode after that anymore. I panicked at this point but than i realised that not all recoveries did work for me. For example I could never flash a CWM recovery, not sure why. Maybe because I tried to flash a 4.4 recovery and I had a 5.1 BOOT.img installed?
Click to expand...
Click to collapse
I see, so then it seems like some recoveries did in fact work with fastboot on me, because the Vol+ and Power worked, but it either only put me in V100R001C900B300 OR MT7-L09C900B300. I've read that I can't just flash KK over LP, that I needed to flash the B300 which is why I flashed transition package first. Should I not have done this?
Once in transition mode though (I booted up and checked, then went back into recovery), if I flashed 4.4 (recovery), it oddly put me back to B327...strange even though the recovery flashed was B137 or B145.
Let me see this link above. I'm back again at 5.1.1 LP B327. I'll do instead fastboot and flash above the recovery and so on, and I'll post the results, if any. Oddly enough, if I flashed boot, recovery and system images of 4.4, I get an "Android" boot screen that hangs, no Huawei.
I really like LP because of some of the features not found in KK like the dual windows, camera tweaks, etc. But no root yet available. TWRP doesn't seem to work as well, fails in fastboot.

balpem said:
After a 36 hour marathon my mate 7 is back and working. the trick was to flash the stock recovery for all Lollipop versions wich can be foudn here: http://forum.xda-developers.com/mat...8-7-0-mate7-android-5-1-t3156779/post61958212 via linux. I somehow seem to have had trouble over wndows.
And after that do the three button rescue with the newest B 324 firmware which I have had installed before I destroyed my OS..
and my camera is now running normaly which was the initial reason i tried to install a other firmare.
:laugh:
Click to expand...
Click to collapse
Okay...so I was able to flash down to B324, but not via the link provided. What I did was, flash B300 cust.img on (fastboot) then flash boot/recovery/cust/system.img (fastboot). Rebooted with VolumeUp + Power to check for recovery (success), performed a wipe and done! Back to B324.
Now I gotta figure how to go back down to B145, which is where I was at with Root and with no problems at all. If I flash B300 again and then B145...I get the "Android" logo (instead of Huawei) and then the HAM7 reboots and recovers itself back to B324.

stuck in loop, possibly a different kind of loop

I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.

atomkrieg said:
I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.
Click to expand...
Click to collapse
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk

soupysoup said:
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.

atomkrieg said:
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.
Click to expand...
Click to collapse
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk

soupysoup said:
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
in the end fastboot, since i coulndt see how i could copy the img over to install via twrp
im pretty sure the button is fine, since it was cycling from the ota update install, then was working fine unlocking the bootloader, but after the flash, it crapped the bed.

Different problem
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go

siddhu007 said:
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go
Click to expand...
Click to collapse
ok, took it into a shop, got the power button fixed. It must have been on the way out because literally one minute it worked and the second it didnt. now i think ive got it narrowed down. it's saying it's unable to mount /persist. ive tried the various fixes:
e2fsck/dev/block/platform/msm_sdcc.1/by-name/persist
and
make_ext4fs/dev/block/platform/msm_sdcc.1/by-name/persist
but all i get is a not found error. not sure what to do from here on.

success!! i ended up stumbling on a bit how to restore the persist partition i didnt try. got a custom rom installs and everything works. thanks to everyone who tried to help!!

stuck in bootloop while flashing cataclysm rom
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..

When it was stuck in the loop, I had to hold vol up and down with the power button (wait a few secs until it was completely off) then reboot holding down + power till it opened the bootloader. if that doesnt work, try reflashing the bootloader via fastboot. I only found out i couldnt mount the persist partition by looking at the terminal window in twrp after trying to install a rom which kept it in the boot loop. I then used the cmd: make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist to rebuild it.

jpau11 said:
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..
Click to expand...
Click to collapse
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.

audit13 said:
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.
Click to expand...
Click to collapse
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!

jpau11 said:
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!
Click to expand...
Click to collapse
Great to hear it. Congratulations:good:

My moto G3 is stuck on the "warning, bootloader unlocked" page, please help !

My moto G3 is stuck on the "warning, bootloader unlocked" page, please help !
I recently rooted my Motorola Moto G3 and it worked.... ish, when I opened my phone from it being turned off I was greeted with the message telling me that it was super duper dangerous to root your phone and I could damage my phone, that normally goes as it is just a mandatory thing that they have to say, I waited for a while and it didn't go, I waited for a day and it didn't go. So I let it run out of charge and tried to boot it again, this didn't work, I was still seeing the same white screen with red and black writing. I then let it run out of charge and open it in fast boot mode by pressing the power button and volume down, this did work and from there I have managed to open the team win recovery project but whenever I do anything from then, it will go back to the error page and then will never load. I have even reset the phone to factory settings. If I hold the power button it will turn off the phone but very shortly after automatically turn itself back on to this same image.... please help!

How did you end up rooting it? Have you tried flashing a factory image?

If I were you, I would try to reflash stock firmware with factory reset

@Artyb52
hi, what did you do to Root ??
check these , if you have done evrything :
1) USB debugging enabled, allow OEM unlocking Enable ( developer options )
2) install ADB and fastboot. ( in PC)
3) Unlock bootloader in Fastboot mode .. (After unlocking did you PowerOn your phone, and check ? did it ON with out any problems? )
4) Installing a recovery , by following proper commands and choosing right version ..
5) flashing SuperSU with that Recovery.
If you have done everything Right, then Do onething.. Change CustomRecovery Version ( if on TWRP ) ,
else Goto Fastboot.. press POWER OFF, so that your phone gets SHUT DOWN, then On it normally ..
i have seen a problem where REBOOT function causes Bootloops..

i tried that and it didnt work :/
@nandakis4 shame it didn't work. Do you have any other tips, I would be really grateful

@Acetyloaceton how do you do that ? sorry for sounding like such a noob, i'm new to the game

l3ones said:
How did you end up rooting it? Have you tried flashing a factory image?
Click to expand...
Click to collapse
@13ones I tried flashing the TWRP image, is that different to the factory image ?

The same thing happened me when I rooted my phone. To fix it I downloaded cm 13 then placed it on internal storage and flashed it (and gapps) from twrp and it worked fine.

Acetyloaceton said:
If I were you, I would try to reflash stock firmware with factory reset
Click to expand...
Click to collapse
"Factory Reset" Doesn't reflash stock firmware, it just wipes /data /cache and internal storage.
---------- Post added at 10:20 PM ---------- Previous post was at 10:19 PM ----------
Artyb52 said:
@13ones I tried flashing the TWRP image, is that different to the factory image ?
Click to expand...
Click to collapse
Yes, you'd need to download it from the stock firmware page and flash the whole thing through fastboot.

l3ones said:
"Factory Reset" Doesn't reflash stock firmware, it just wipes /data /cache and internal storage.
---------- Post added at 10:20 PM ---------- Previous post was at 10:19 PM ----------
Yes, you'd need to download it from the stock firmware page and flash the whole thing through fastboot.
Click to expand...
Click to collapse
@l3ones i have tried this 2 times now, and i must be doing something wrong, i dont want to hassle you but could you walk me through the exact procedure needed to do this

Try this
Using adb sideload on twrp
1. Flash supersu 2.62, then
2. Flash supersu 2.65
Command : adb sideload supersu.xx.zip
In my case, it works.

Artyb52 said:
@l3ones i have tried this 2 times now, and i must be doing something wrong, i dont want to hassle you but could you walk me through the exact procedure needed to do this
Click to expand...
Click to collapse
If I'm not too late, sure. What model do you have?

question about particular stock firmware ?

so i went to this website:
https://romfirmware.com/2017/07/28/huawei-honor-6x-bln-l24/
and it has some different firmware things for the honor 6x BLN L24 model.. and one of them is a point version variant that says can be flashed through twrp?
will this work should i trust this?
edit// on the site it says the version for it is BLN-L24C567B360 however mine is BLN-L24C567B366 (5.0.1 EMUI..i think B360 is EMUI 5.0?)

Rommco05 said:
You have a newer firmware on your phone. Yes point version can be flash over twrp in some situations, same like over dload
Click to expand...
Click to collapse
can you explain what dload is to me? this phon is my first phone ive had that i could really do something with in the rooting community.. my other one was a galaxy grand prime with no rom support or any img files and it got bricked cause i of course had to screw with the build.prop file XD

Rommco05 said:
You must turn off the phone before installing. You need to turn it on with holding all 3 buttons ... vol + + down + power button, after that will start installation
Click to expand...
Click to collapse
okay... so after i extract the particular recovery image i need.. i reboot to the fastboot menu, use adb to flash over the img, like i did with twrp... and reboot into the stock recovery menu?

Rommco05 said:
Basically yes. What you need to do after?
Click to expand...
Click to collapse
put the update.app file in a folder on my sd card called dload. and update from sd card?
also i got two files.. recovery.img and recovery2.img... which do i use ?

okay so i read on a thread for the honor 7 having two recovery images... one being the stupid erecovery crap and the other being normal recovery menu? and i guess im able to get both regular and twrp running together on two different partitions somehow?

Rommco05 said:
You can not have two recovery on your phone. For you, only recovery.img is important. Why do you need to replace twrp for stock recovery?
Click to expand...
Click to collapse
i ****ed up my phone... the good backups i had with twrp got ****ed up and are some messed up rooted version running a stock rom where the sound doesnt work at all, speakers headphone, blue tooth calls, apps, etc and camera doesnt work (front and back and camera app doesnt run) and i cant watch any videos on any app.. so i was going to restore the stock firmware

i still use adb reboot recovery to boot into the regular recovery menu ? (not erecov)

alright.. im stuck again.. i rebooted to recovery and it gave me 3 options. reboot, wipe data/factory reset, and wipe cache partition... what do i do to install the firmware??

see its almsot 4 am for me right now.. if you could just talk me through this i would be okay..

never mindd i looked at your previous reply

and i believe its stuck at 5%

alright well it just rebooted and it didnt restore the stock firmware..i still have all my apps and **** and nothing has changed

do i have to factory reset it now? or..

xSpartacusx said:
do i have to factory reset it now? or..
Click to expand...
Click to collapse
If all working then dont go for factory reset. let it be like this.

shashank1320 said:
If all working then dont go for factory reset. let it be like this.
Click to expand...
Click to collapse
nothings working still . camera, sound videos, etc.. still broken.. phone still rooted.. i followed this other ugie i saw on here where you wipe all partitions and things and then do the file from dload and things, and it still stuck at 5%?

heres another question.. when i went through the firmware finder i got 3 files.. update.zip, update_data_full_public.zip, and update_full_BLN-L24_hw_usa.zip they all contain a update.app file... am i using the right one? im using the one from update.zip

now it appears to be stuck at the boot animation screen.. fml
//edt: standby... i actually havent finished the guide..

yup.. i dun ****ed up.... i cant use adb to reboot to recovery.. say null device not found..
i can go into fastboot by doing power and vol down... if i do vol up and power to try to get into recovery/twrp/whatever, it does nothing and does the normal booting process.. holding all three down just does the automatic sd card install thing that doesnt work... what do i do? i think i ****ed it up

well as far as i can tell my phone is bricked cant boot into recovery via key presses or adb.. i get device not found on adb..
fastboot works and i can flash still but i cant get into twrp or anythin i dont know why..
if i let it boot it just stays at the bootloading animation..
am i able to do factory reset from fastboot?
//edit: i did fastboot erase userdata accoring to some websites online.. no success in booting... is there anything i can do at this point?

Rommco05 said:
Disconnect the phone from the usb and switch off. Turn on and hold the power button + vol up when you see the Honor logo release power button but still hold the vol. Now you should be in recovery, perform factory reset
Click to expand...
Click to collapse
thank you so much for that little tip i thought i ****ed something up that was preventing it from going into recovery..
omg thank you so much it booted to the set up menu... thank you... ill report back with the status of camera and sounds and things