Reflash bootloader?!? - General Questions and Answers

Hello, I'm using HUAWEI Y300-0100, and I installed CM11 on it. The thing is I cant enter bootloader at all and I get often random reboots. Tried to enter bootloader via adb command, via apps that give that option, and button combination, still nothing. Is there a way to flash bootloader only, via recovery or adb perhaps? Thank you anyway!

mr_techno said:
Hello, I'm using HUAWEI Y300-0100, and I installed CM11 on it. The thing is I cant enter bootloader at all and I get often random reboots. Tried to enter bootloader via adb command, via apps that give that option, and button combination, still nothing. Is there a way to flash bootloader only, via recovery or adb perhaps? Thank you anyway!
Click to expand...
Click to collapse
Hi, when you enter command does it get stuck at the Huawei splash. If so this is the boot loader. I know it is strange but the boot loaders on these devices are very minimalistic and rely on ADB/Fastboot commands from the PC

No, it just does normal reboot. I think it is somehow connected with random phone rebooting.

mr_techno said:
No, it just does normal reboot. I think it is somehow connected with random phone rebooting.
Click to expand...
Click to collapse
Can you still enter the custom recovery?

I can enter into recovery. Btw, latest TWRP installed.

Related

Not brick but nothing i can do

Hello everyone, it's my first time that I'm stuck in this stupid way. now I'm with JB not-root and Team Win recovery in boot loop. he asks for the password to decrypt data and you can not wipe or mount anything. I can do reboot but he goes right into recovery without being able to get into fastboot. what i can do now for return to stock. boot loader are unlocked.thz for all help.:highfive:
What bootloader & what recovery?
Ti2 said:
What bootloader & what recovery?
Click to expand...
Click to collapse
Team Win 2,4,4,0 boot loader version i cant see
4.2.1 rom?
Ti2 said:
4.2.1 rom?
Click to expand...
Click to collapse
the last JB official from site.
pierpa86 said:
Team Win 2,4,4,0 boot loader version i cant see
Click to expand...
Click to collapse
if you cant mount the sdcard mean probably you need twrp 2.4.4.0-4.2
lk2l said:
if you cant mount the sdcard mean probably you need twrp 2.4.4.0-4.2
Click to expand...
Click to collapse
i can't
i only need to stop recovery loop for have FastBoot or Adb... and HOW ?
pierpa86 said:
i only need to stop recovery loop for have FastBoot or Adb... and HOW ?
Click to expand...
Click to collapse
?? if you hold the power button until switch off and immediatly push the volume down button, you should have the RCK screen to use fastboot right??
lk2l said:
?? if you hold the power button until switch off and immediatly push the volume down button, you should have the RCK screen to use fastboot right??
Click to expand...
Click to collapse
no i can't i push power + up or down nothing same story. stupid error:silly:
pierpa86 said:
no i can't i push power + up or down nothing same story. stupid error:silly:
Click to expand...
Click to collapse
try to reed this
http://forum.xda-developers.com/showthread.php?p=31842894
I hope can help you
lk2l said:
try to reed this
http://forum.xda-developers.com/showthread.php?p=31842894
I hope can help you
Click to expand...
Click to collapse
It will only work on UNLOCKED devices
It requires access to Fastboot to prepare device first time
It won’t work on fully bricked devices (See 2.)
You need to keep files safe!
If you upgraded to Offiical JB it *won’t* work!
i'm not have fastboot and i'm on Official JB
i have try to enter on APX mode but i can't
did you try to install the asus pc sync (it shoul install the driver for use adb & fastboot) and after boot into recovery
from prompt you should be able to use adb
write adb devices
and if you can see the code of the devices may you can still have a possibility to flash troght adb
ok man i understand the problem today
i have flashed the last TeamWin Recovery but not compatible with 4.2.1 but 4.1 stock rom and now all partition can't be mounted in recovery, i have found adb in broken recovery and push recovery img for flash with dd command and all done in shell but nothing flashed !! then "adb reboot bootloader" for try to reflash with fastboot, same story all done in shell but nothing flashed !! ok no problem i try to boot android in boot menu and damn partition is ok and android booting !!!!!!! :laugh:
ok remain 2 way. use dd in terminal emulator but can't without root permission and use nvflash but it's not work with JB confirm ?
waiting for a tool using an exploit for root from internal android and try dd or next update for nvflash.
any idea ? and sorry for my very bad english
Key driver not found.. Booting OS
Android cardhU-User bootloader (1.00 e) released by "WW_epad-10.6.1.8-20130225" A03
Starting Fastboot USB download protocol
[RCK] [ANDROID] [WIPE DATA]
when try flash in fast boot get freeze !!
Same issue here. I'm able to use Adb reboot bootloader command. And get to boot loader. From there I can cold boot Linux. So I have my i
Os but if it reboots. It goes back to the twrp locked.
Sent from my Galaxy Nexus using xda app-developers app
klownin5643 said:
Same issue here. I'm able to use Adb reboot bootloader command. And get to boot loader. From there I can cold boot Linux. So I have my i
Os but if it reboots. It goes back to the twrp locked.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
and what do you think about ?
if you can boot the system may you can verify again the bootloader whit asus tool from the website maybe for any unsense reason it's locked....
ops wrong tread
Ok, I just tried some stuff and:
1. I can also access fastboot and OS.
2. Trying to flash modified TWRP with fastboot freezes bootloader.
3. In-system can't open .RAR files.
4. After manually transfering unpacked V8 unlocker from PC it says there's an "unknown problem" when trying to install unlocker. It supposedly upgraded from V7 to V8 app without problem.
In bootloader it says at the top of the screen that "Key driver not found... Booting OS". After that it lists bootloader info ( v. 1.00 e ).
Looks like recovery's bricked with some further issues in the OS itself.
EDIT:
Bricked the OS. Tried reflashing stock system and now bootloader freezes when trying to boot OS. My guess would be that fastboot can still erase stuff but most likely can't write ( at least not properly ). Google/Asus probably know of a way to restore our tablets but Asus clearly prefers to replace motherboards.
I have to think whether it's worth it for me to replace the MB but most likely will just sell the thing for parts.
whan you try to re-flash the system somthing goes in the wrong way? do you still have fastbooy access? was the usb debug on?
sorry but which rar you can't open?

[Q] Bootloop and Broken Power Button

My phone is bootlooping and the power button has been broken for a while. I've tried various things posted in other threads, just wondering if anyone has any solutions or ideas.
I can't seem to get it to connect with usb in the bootloader but it does connect while bootlooping. Can I fix it while connected in the bootloop?
edit: Actually, now that I've researched more, I'm pretty sure the problem is that my bootloader is frozen. That's why neither my functioning volume keys or adb works in the bootloader.
ekovv said:
My phone is bootlooping and the power button has been broken for a while. I've tried various things posted in other threads, just wondering if anyone has any solutions or ideas.
I can't seem to get it to connect with usb in the bootloader but it does connect while bootlooping. Can I fix it while connected in the bootloop?
Click to expand...
Click to collapse
Try Nexus root toolkit to boot custom recovery temporarily (or another option like that), while looping, ?may? work??
Setting.Out said:
Try Nexus root toolkit to boot custom recovery temporarily (or another option like that), while looping, ?may? work??
Click to expand...
Click to collapse
I can't seem to get anything in the Nexus Root Toolkit to work while it's bootlooping or while it's in the bootloader even though it comes up in my device manager as Google Nexus S ADB Interface while in the bootloop.
Is there a way to fix it in the command line, or is that just the same thing as using the root toolkit?
ekovv said:
I can't seem to get anything in the Nexus Root Toolkit to work while it's bootlooping or while it's in the bootloader even though it comes up in my device manager as Google Nexus S ADB Interface while in the bootloop.
Is there a way to fix it in the command line, or is that just the same thing as using the root toolkit?
Click to expand...
Click to collapse
Can you get into recovery?
No I can't get into recovery because my volume buttons won't let me navigate the bootloader options. They aren't broken, they just don't work in the bootloader for some reason. My power button is physically broken though so I don't know how to get to recovery or if I can even use recovery without the power button...
I think fastboot will work without a power button?
This command...
adb reboot bootloader
Click to expand...
Click to collapse
ekovv said:
My phone is bootlooping and the power button has been broken for a while. I've tried various things posted in other threads, just wondering if anyone has any solutions or ideas.
I can't seem to get it to connect with usb in the bootloader but it does connect while bootlooping. Can I fix it while connected in the bootloop?
Click to expand...
Click to collapse
1) Download latest CWM Touch.
2) Follow steps from here to install CWM.
3) Boot in recovery using the command in the above link.
4) Download a flashable touch recovery from here.
5) Mount USB in the recovery and copy this zip and flash it. This will make your custom recovery permanent. Reboot to recovery again just to verify.
Now, you have a touch recovery accessible through fastboot and can install custom ROMs
smit.sanghavi said:
1) Download latest CWM Touch.
2) Follow steps from here to install CWM.
3) Boot in recovery using the command in the above link.
4) Download a flashable touch recovery from here.
5) Mount USB in the recovery and copy this zip and flash it. This will make your custom recovery permanent. Reboot to recovery again just to verify.
Now, you have a touch recovery accessible through fastboot and can install custom ROMs
Click to expand...
Click to collapse
Thanks for the step by step! The problem is I still can't get the adb working in the bootloader to install CWM Touch. When I type adb reboot bootloader it says "no device connected." If I type the same command while the phone is bootlooping it says "device unauthorized."
edit: Actually, now that I've researched more, I'm pretty sure the problem is that my bootloader is frozen. That's why neither my functioning volume keys or adb works in the bootloader.
ekovv said:
Thanks for the step by step! The problem is I still can't get the adb working in the bootloader to install CWM Touch. When I type adb reboot bootloader it says "no device connected." If I type the same command while the phone is bootlooping it says "device unauthorized."
edit: Actually, now that I've researched more, I'm pretty sure the problem is that my bootloader is frozen. That's why neither my functioning volume keys or adb works in the bootloader.
Click to expand...
Click to collapse
You can't use adb in fastboot. There are fastboot commands for that.
Step 2 has fastboot commands to install custom recovery.
Very similar problem on Nexus 4
https://forum.xda-developers.com/nexus-4/general/nexus-4-bootloop-adb-unauthorized-t3540874
ekovv said:
My phone is bootlooping and the power button has been broken for a while. I've tried various things posted in other threads, just wondering if anyone has any solutions or ideas.
I can't seem to get it to connect with usb in the bootloader but it does connect while bootlooping. Can I fix it while connected in the bootloop?
edit: Actually, now that I've researched more, I'm pretty sure the problem is that my bootloader is frozen. That's why neither my functioning volume keys or adb works in the bootloader.
Click to expand...
Click to collapse
You can wait till the battery drain and then connect your phone to PC holding the volume button to enter bootloader and then using Nexus Root Toolkit flash your stock rom.
Kiranarul2000 said:
You can wait till the battery drain and then connect your phone to PC holding the volume button to enter bootloader and then using Nexus Root Toolkit flash your stock rom.
Click to expand...
Click to collapse
it doesnt work because if the phone gets charged up it goes into the loop again

[Q] Where has recovery gone?

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!

OPO won't boot past boot logo, can't reach recovery

Hey guys.
Some issues right now....
I can't get the phone to boot. It gets stuck on boot logo. I can get it into fastboot, but not recovery.
If I try to enter recovery, it shows boot logo, then change brightness level a little bit for some reason, then nothing. Back to boot logo after screen goes black.
So it appears that the TWRP isn't installed correctly, but I've reinstalled it several times, but it never actually seems to work.
I can see the device in fastboot. Bootloader is also unlocked.
So, does anyone have a solution for this issue?
I can get it into fastboot
Click to expand...
Click to collapse
This is good news as it means you should be able to just flash the recovery from fastboot.
1. Download the latest TWRP Recovery: http://twrp.me/devices/bacon (I believe this is the link, it's blocked at school )
2. type the command
fastboot flash recovery /location/of/twrp/img
Click to expand...
Click to collapse
3. Wait for it to complete and then reboot the device by holding down power and volume down.
4. Then if it boots into TWRP you should be able to mount it on the computer you plug it into and then carry over a ROM and/or GApps files.
I'm in the exact same boat, happened after I tried an OTA update. I can't flash anything into the phone via ADB because my phone isn't recognised. isn't recognised in ADB. This is while I am in Fastboot. I'm on OSX.
Rorys-MBP:~ Rory$ adb devices
List of devices attached
Click to expand...
Click to collapse

[SOLVED] I need an urgent help!

Hello. I have a Poco X3 NFC and this is my problem:
I had OrangeFox recovery on it. I wanted to install another rom (from Arow OS because it wasn't work well), and one of the requirements was a decrypted device. I've flashed a file which is said it can decrypt it (and it did). After the flash, I rebooted my phone and everything was fine until I rebooted my phone again. Now the recovery bootlooped, the phone can't boot the system and adb doesn't recognize my phone in fastboot mode. It's weird that when the phone stucks at OrangeFox logo, adb recognizes my device (as in recovery mode). So I type the command "adb reboot fastboot" and it loops at the recovery again. I can go fastboot mode but fastboot doesn't recognize my phone, so I can't flash anything either. It's 4:20 a.m. in here and I can't sleep because of this.
Can u restore a backup?
Arealhooman said:
Can u restore a backup?
Click to expand...
Click to collapse
No. I can't reach anything in my phone. Currently I am waiting for the battery run out maybe something would change
Can you access orange fox itself?
Your battery can take weeks to run out. But try it.
Arealhooman said:
Do you have stock recovery?
Click to expand...
Click to collapse
No. I think it's not impossible to find in somewhere but my main problem is my PC won't recognize my phone in the fastboot mode. If it would, I can flash twrp or anything.
You need fastboot to access fastbootd right?
Arealhooman said:
You need fastboot to access fastbootd right?
Click to expand...
Click to collapse
I do not understand what you mean but I can go into the fastboot mode in my phone, the problem is adb doesn't recognize my phone.
Your PC sees your device though?
Arealhooman said:
Your PC sees your device though?
Click to expand...
Click to collapse
When I plug in my cable, I can hear that "something is plugged in" voice in my pc. When I look device manager, it shows the phone as "Android Composite ADB Interface". When it stucks in recovery, it doesn't quickly boot so I can see my device in adb:
List of devices attached
940ab842 recovery
this is showed in adb when my phone stucks at recovery, but I can give commands like "reboot".
But when I type " reboot system", it doesn't reboot it system and just tries to open recovery mode, and recovery mode doesn't open, just loops.
I type ''reboot fastboot", but it still tries to open recovery and again, it loops.
I type "reboot bootloader", at this time, it can boot to the fastboot mode, there is an orange "fastboot" word at the middle. When I go back to adb and type "adb devices", it shows nothing.
Arealhooman said:
Can you access orange fox itself?
Click to expand...
Click to collapse
No, I cannot. It is looped. This is the another problem prevents me to recover my phone.
Arealhooman said:
Can u restore a backup?
Click to expand...
Click to collapse
I think Arrow OS files still in my phone but somehow it pretends like it can't detect them. And it wants to boot directly to the recovery mode but the another problem is recovery mode stuck in loop. When I want to flash a new recovery, this time I can't connect my phone to my pc when it's in the fastboot mode. It's like a problems chain and I couldn't find any exit.
sorry, no idea
Arealhooman said:
sorry, no idea
Click to expand...
Click to collapse
Guess so, I'll go to a phone repair shop to see if they can do something about it (maybe their pc can detect my phone and they can flash another recovery), and if not then I am ****ed.
Arealhooman said:
sorry, no idea
Click to expand...
Click to collapse
DUDE I ****ING SOLVED IT!
FIRSTLY, **** ORANGEFOX, if anybody see this do not use orangefox.
Secondly, actually I still have the same problem. TWRP is also stucks at the loop, but there is an interesting difference that TWRP tries to loop one time and after the fail, it suddenly boots the system.
And since I can flash something with fastboot, now I think i can save my phone. Now I'm trying to install stock rom, i'll update after.
How I solved:
Installing the Google Universal USB Drivers. It has a weird method to install, and I wasn't know you can install a driver even the phone is in the fastboot mode. So thanks to that I was able to install usb drivers and finally I could get fastboot to recognize my device. The first thing I did was installing TWRP.
My problem was not solved even I installed TWRP because TWRP was doing the same thing, but one thing was different: TWRP was trying to boot recovery, it couldn't and after it was booting to the system. So I've realized how amazing TWRP is. But it wasn't solved my problem completely though, I think its problem is related to that decryption file.
Currently, I've managed to install stock rom and I haven't encountered any problem.
And I'm happy because my mother won't beat me with her slippers.

Categories

Resources