Database Info

Bootloop after changing font

hi i have a taiwanese phone , the nextab nexus 2 chipset is mt6575(mediatek). i had it rooted and recently i tried changing fonts and got stuck in a bootloop. anyone can help me? or at least tell me how to factory reset it using hardware keys. or enter recovery mode. any help is appreciated thanks

PokMahPok said:
hi i have a taiwanese phone , the nextab nexus 2 chipset is mt6575(mediatek). i had it rooted and recently i tried changing fonts and got stuck in a bootloop. anyone can help me? or at least tell me how to factory reset it using hardware keys. or enter recovery mode. any help is appreciated thanks
Click to expand...
Click to collapse
bump! is anyone reading this?
anyways can anyone at least tell me how to use adb to restore or push back the stock ics fonts. without switching on the phone(preferably)

Have you enabled USB debugging.?
You can try "adb reboot recovery" (without quotes to get into recovery)
adb tutorial thread
LIFE! It's what you make out of it!

Lifehacker7 said:
Have you enabled USB debugging.?
You can try "adb reboot recovery" (without quotes to get into recovery)
LIFE! It's what you make out of it!
Click to expand...
Click to collapse
as i said my phone has gone into a bootloop so there is absolutely no way for me to use the usb debugging, although its already enabled .

PokMahPok said:
as i said my phone has gone into a bootloop so there is absolutely no way for me to use the usb debugging, although its already enabled .
Click to expand...
Click to collapse
Try different combination of hardware buttons. There will be different sequence for different phones.
Try power+volume up or down
Or all 3 together or so to get into recovery.
LIFE! It's what you make out of it!

Lifehacker7 said:
Try different combination of hardware buttons. There will be different sequence for different phones.
Try power+volume up or down
Or all 3 together or so to get into recovery.
LIFE! It's what you make out of it!
Click to expand...
Click to collapse
okay so i did it and managed to get a logo of an android with its back open with a red warning sign. but no recovery. any ideas??

PokMahPok said:
okay so i did it and managed to get a logo of an android with its back open with a red warning sign. but no recovery. any ideas??
Click to expand...
Click to collapse
Press Power + Vol Down + Home Keys
Select Clear eMC
This will factory reset your phone

[Q] Hard Bricked Nexus 5

HI, I probably hard bricked my new Nexus 5.... I am very sorry for this.
Turning on with the volume button i log in bootloader but the recovery does not work and crashes in "Google" screen.
The charging doesn't work, and the battery is about to end (2% i think).
I noticed that by connecting the device to the PC, the PC recognizes it as Andorid .... I can do something before calling google?

Not a hard brick, hard bricks don't power on or anything as far as I know
Sent from my Nexus 7 using XDA Premium 4 mobile app

maaaaars said:
HI, I probably hard bricked my new Nexus 5.... I am very sorry for this.
Turning on with the volume button i log in bootloader but the recovery does not work and crashes in "Google" screen.
The charging doesn't work, and the battery is about to end (2% i think).
I noticed that by connecting the device to the PC, the PC recognizes it as Andorid .... I can do something before calling google?
Click to expand...
Click to collapse
Wait until the end of the battery... or push the power button 10 seconds...

Power it off and charge it up, then use the factory image to restore it.
This is definately not a hard brick.

UP Now the charging works... i try to fix it. I will notice eventually updates. Thanks.

You can reach bootloader? // Yes -> Nothing is bricked
It is a Nexus and not some toy-phone

fireproofrev said:
You can reach bootloader? // Yes -> Nothing is bricked
It is a Nexus and not some toy-phone
Click to expand...
Click to collapse
Yes, i can reach bootloader, but if I turn the phone in recovery mode, it remain blocked in Google screen.
Can someone give me pointers on how I should operate? Sorry, it's the first time that I run into a similar problem...

maaaaars said:
Yes, i can reach bootloader, but if I turn the phone in recovery mode, it remain blocked in Google screen.
Can someone give me pointers on how I should operate? Sorry, it's the first time that I run into a similar problem...
Click to expand...
Click to collapse
Did you flash a custom recovery?

EkimPadd said:
Did you flash a custom recovery?
Click to expand...
Click to collapse
No.

maaaaars said:
Yes, i can reach bootloader, but if I turn the phone in recovery mode, it remain blocked in Google screen.
Can someone give me pointers on how I should operate? Sorry, it's the first time that I run into a similar problem...
Click to expand...
Click to collapse
I already did:
Rusty! said:
Power it off and charge it up, then use the factory image to restore it.
This is definately not a hard brick.
Click to expand...
Click to collapse

maaaaars said:
Yes, i can reach bootloader, but if I turn the phone in recovery mode, it remain blocked in Google screen.
Can someone give me pointers on how I should operate? Sorry, it's the first time that I run into a similar problem...
Click to expand...
Click to collapse
Reflash stock image via fastboot. No need for recovery. Just search for it, I am at lunch right know and dont have the time to explain

fireproofrev said:
Reflash stock image via fastboot. No need for recovery. Just search for it, I am at lunch right know and dont have the time to explain
Click to expand...
Click to collapse
Follow this link - https://dl.google.com/dl/android/aosp/hammerhead-krt16m-factory-bd9c39de.tgz
Then follow these instructions as per Google:
You will find these files useful if you have used the Android Open-Source Project, flashed custom builds on your device, and wish to return that device to its factory state.
In order to use these files, you need to have the fastboot tool in your PATH. That tool is compiled as part of every configuration of the Android Open-Source Project and is the tool used to flash custom builds on your device. On GNU/Linux systems, this also implies that you have configured USB access as mentioned in the machine setup instructions.
Your device needs to be in fastboot mode, with the bootloader unlocked. The relevant key combinations and commands are documented on the page about building for devices.
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default.

Is reborn, thanks very much.

Last night my nexus 5 had died ... this morning, after a sleepless night has begun to recharge ... The God of smartphones has saved my 400 euro from an hard brick!!!!

I think I bricked my N5.
I can't boot - I can't see Google logo, I can't reach bootloader or recovery.
If I hold down volume up+down and power button for a while I can see in drivers "Qualcomm HS-USB QDLoader 9008". But I can't see anythink on display.

kecinzer said:
I think I bricked my N5.
I can't boot - I can't see Google logo, I can't reach bootloader or recovery.
If I hold down volume up+down and power button for a while I can see in drivers "Qualcomm HS-USB QDLoader 9008". But I can't see anythink on display.
Click to expand...
Click to collapse
I think yours is hard brick, send it back to google.

kecinzer said:
I think I bricked my N5.
I can't boot - I can't see Google logo, I can't reach bootloader or recovery.
If I hold down volume up+down and power button for a while I can see in drivers "Qualcomm HS-USB QDLoader 9008". But I can't see anythink on display.
Click to expand...
Click to collapse
You are hard bricked. How did you manage to do that?
Sent from my Nexus 5

@jd1639
I can send you zip to flash. Do you wanna try it too? D

kecinzer said:
@jd1639
I can send you zip to flash. Do you wanna try it too? D
Click to expand...
Click to collapse
No thanks just curious
Sent from my Nexus 5

I want to try flash my franco.Kernel test zImage. So I found faux kernel for mako with anykernel flash method. And replaced zImage inside.

I broke mit Pixel 3 !?

Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags

MMoes said:
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
Click to expand...
Click to collapse
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.

MMoes said:
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
Click to expand...
Click to collapse
FilthyFord said:
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
Click to expand...
Click to collapse
You can also edit the flash-all file to remove the -w and not completely wipe your phone. This way, your data will remain and it still resets the important factory stuff.

FilthyFord said:
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
Click to expand...
Click to collapse
Thanks, I‘ve tried with adb devices & no device found. So obviously my computer doesn‘t recognize the Pixel

sliding_billy said:
You can also edit the flash-all file to remove the -w and not completely wipe your phone. This way, your data will remain and it still resets the important factory stuff.
Click to expand...
Click to collapse
Thanks. Loosing my data isn‘t the Problem. Actually I‘m even not able to connect to the phone and flash anything.

MMoes said:
Thanks. Loosing my data isn‘t the Problem. Actually I‘m even not able to connect to the phone and flash anything.
Click to expand...
Click to collapse
Have you hard powered the device down and then rebooted to BL with key combo to check connectivity?

sliding_billy said:
Have you hard powered the device down and then rebooted to BL with key combo to check connectivity?
Click to expand...
Click to collapse
No, could you please descripe the process what to do exactly. Would love to give it a try. Thank you

MMoes said:
No, could you please descripe the process what to do exactly. Would love to give it a try. Thank you
Click to expand...
Click to collapse
Hold down the power button until the phone completely shuts off. Hold power while holding the volume down button (start by holding the volume down and then immediately start holding the power button - it's is technically holding both at the same time but starting with volume down just a moment before keeps you from pressing power first). That should get you to fastboot.

MMoes said:
Thanks, I‘ve tried with adb devices & no device found. So obviously my computer doesn‘t recognize the Pixel
Click to expand...
Click to collapse
ADB doesn't work when booted to the bootloader. It only works when you're booted to the OS. To see if the computer recognizes the phone when in the bootloader, use fastboot devices instead of adb devices.

sliding_billy said:
Hold down the power button until the phone completely shuts off. Hold power while holding the volume down button (start by holding the volume down and then immediately start holding the power button - it's is technically holding both at the same time but starting with volume down just a moment before keeps you from pressing power first). That should get you to fastboot.
Click to expand...
Click to collapse
Holding the power button didn't had any effect, but holding volume - and holding power button at the same time was starting the bootloader and so I was now able to start TWRP Manager.
So if you could help me from here to fix the OS would be great, e.g. is there any chance to copy the original OS from Google or an custom ROM from my computer (e.g. I wotk on MAC and is there a way to copy via Terminal?) or does TWRP offers any way to reset/ reinstall?

robocuff said:
ADB doesn't work when booted to the bootloader. It only works when you're booted to the OS. To see if the computer recognizes the phone when in the bootloader, use fastboot devices instead of adb devices.
Click to expand...
Click to collapse
Yes, the computer recognizes the phone (via Terminal on my MAC)

MMoes said:
Holding the power button didn't had any effect, but holding volume - and holding power button at the same time was starting the bootloader and so I was now able to start TWRP Manager.
So if you could help me from here to fix the OS would be great, e.g. is there any chance to copy the original OS from Google or an custom ROM from my computer (e.g. I wotk on MAC and is there a way to copy via Terminal?) or does TWRP offers any way to reset/ reinstall?
Click to expand...
Click to collapse
Sorry, but I do not know the Mac commands, but if you are in Fastboot and the device shows/connects it is just a matter of running the flash-all and resetting. If you are not connecting in Fastboot but can get into TWRP, I would start with a reset in TWRP.

sliding_billy said:
Sorry, but I do not know the Mac commands, but if you are in Fastboot and the device shows/connects it is just a matter of running the flash-all and resetting. If you are not connecting in Fastboot but can get into TWRP, I would start with a reset in TWRP.
Click to expand...
Click to collapse
The commands on the MAC are almost the same and with your flash-all (flash.all.sh Mac Command) it worked very well with the factory image from google. Now I'm back in the race and my P3 is running again.
Thank you all guys!

MMoes said:
The commands on the MAC are almost the same and with your flash-all (flash.all.sh Mac Command) it worked very well with the factory image from google. Now I'm back in the race and my P3 is running again.
Thank you all guys!
Click to expand...
Click to collapse
Excellent news. On another note... if all you need from TWRP is to install Magisk to root, you do not need to permanently install TWRP. Just fastboot boot the [twrp].img file, install the Magisk .zip and keep stock recovery.

From messing around, it seems that trying to restore system from twrp is messed up. Data backup works fine. The only other way I got bootlooped was by messing with boot, vbmata, and vendor partitions. Out of those three, I think boot is the most likely to get messed up by normal users. I know this is sorted now, but in the future try to just reflash boot.img and see if it boots.
-The vbmeta and vendor thing is specific because I need to get the radio to work here.

[Solved] P20 Pro Bricked... Anyone can help me?

First, I was doing a full wipe in TWRP, But I realize I didn't back up my photos/Documents.
So I long pressed the power button to restart.
And now, i got a bricked phone...
Any one can help me?
I'd try this
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
But, I got stuck on the TWRP boot screen.
Also, I'm still available to use the fastboot mode.
Finally, I solve the problem by flashing the e recovery image,and then low level forma data.
Hope it helps for someone have the same issue like me.

zhu911203 said:
First, I was doing a full wipe in TWRP, But I realize I didn't back up my photos/Documents.
So I long pressed the power button to restart.
And now, i got a bricked phone...
Click to expand...
Click to collapse
I have exactly the same Problem. Did you solve it already?

zhu911203 said:
First, I was doing a full wipe in TWRP, But I realize I didn't back up my photos/Documents.
So I long pressed the power button to restart.
And now, i got a bricked phone...
Any one can help me?
I'd try this
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
But, I got stuck on the TWRP boot screen.
Also, I'm still available to use the fastboot mode.
Click to expand...
Click to collapse
Can you still have access to erecovery : volup at power with USB cable plugged. If yes you can try a recovery but you will loose all your data
Can you have access to fastboot : vol down at power up. If yes you can try to flash by adb by following instruction from discussions in the forums.

zhu911203 said:
First, I was doing a full wipe in TWRP, But I realize I didn't back up my photos/Documents.
So I long pressed the power button to restart.
And now, i got a bricked phone...
Any one can help me?
I'd try this
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
But, I got stuck on the TWRP boot screen.
Also, I'm still available to use the fastboot mode.
Click to expand...
Click to collapse
Can you still have access to erecovery : volup at power with USB cable plugged. If yes you can try a recovery but you will loose all your data
Can you have access to fastboot : vol down at power up. If yes you can try to flash by adb by following instruction from discussions in the forums.

Schuchi said:
I have exactly the same Problem. Did you solve it already?
Click to expand...
Click to collapse
yes, I solved the problem, hope it will help you.

Possible or Not? Factory reset bricked Pixel 2.

I've spent hours searching and cannot find a definite answer to my question. I see others have asked HOW to fix this issue, I just want to know if it is possible.
Is it possible to factory reset my device or not?
Bootloader is NOT UNLOCKED, and I am stuck on bootloader screen.
"Bootlinux Failed: Not started" when trying recovery mode.
"Slot Unbootable: Load Error" when trying to start.
My device is obviously not found under adb devices as it is locked, but does show up in fastboot devices.
My computer does recognize the android device as well.
Is it possible to factory reset my device or not?
Is there any way to flash a custom ROM and get it operational?

I'd say you're out of luck, I've had the slot unbootable error/ authload error and both usually require re flashing the bootloader, radio, boot.img or a full factory image restore via flash-all to restore via an unlocked BL. I haven't seen any other methods available for the walleye with a locked bootloader I can offer either.

junglism93 said:
I'd say you're out of luck, I've had the slot unbootable error/ authload error and both usually require re flashing the bootloader, radio, boot.img or a full factory image restore via flash-all to restore via an unlocked BL. I haven't seen any other methods available for the walleye with a locked bootloader I can offer either.
Click to expand...
Click to collapse
Thanks for your reply,
Surely Google or some super nerd would know how? But I think I am also out of luck.
Thanks though.

Hi! I don't know if could helps, but did you try to sideload full OTA through recovery mode? This should be go with locked BL too, but I am not sure if you have to have enable usb debuging...

somin.n said:
Hi! I don't know if could helps, but did you try to sideload full OTA through recovery mode? This should be go with locked BL too, but I am not sure if you have to have enable usb debuging...
Click to expand...
Click to collapse
Hey Somin,
I haven't fully looked into that option yet, started to give up. But I can't access recovery mode or even get out of bootloader, and usb debugging is not enabled, oem is locked.
If you have any further information or ideas I would be really keen to hear.
Thanks,
Alex

OilyBigMac said:
Hey Somin,
I haven't fully looked into that option yet, started to give up. But I can't access recovery mode or even get out of bootloader, and usb debugging is not enabled, oem is locked.
If you have any further information or ideas I would be really keen to hear.
Thanks,
Alex
Click to expand...
Click to collapse
Did you tried to get to recovery from bootloader screen or with key combination too?

somin.n said:
Hi! I don't know if could helps, but did you try to sideload full OTA through recovery mode? This should be go with locked BL too, but I am not sure if you have to have enable usb debuging...
Click to expand...
Click to collapse
Hey Somin,
I haven't fully looked into that option yet, started to give up. But I can't access recovery mode or even get out of bootloader, and usb debugging is not enabled, oem is locked.
If you have any further information or ideas I would be really keen to hear.
Thanks,
Alex
somin.n said:
Did you tried to get to recovery from bootloader screen or with key combination too?
Click to expand...
Click to collapse
I do appreciate your help, but as I just mentioned, I am stuck in bootloader screen and get errors when trying to access recovery, download, start or any other option. Obviously using the hard reset only brings me to bootloader where I am stuck.
Is this what you're referring to with key combination?

OilyBigMac said:
Is this what you're referring to with key combination?
Click to expand...
Click to collapse
Hi! No Shut down your phone and try "the game" with power button and vol+ btn... I didn't find any tutorial and it is slightly lottery, but you could get directly to recovery mode if you will press this btns in correct way:
- try to hold them for long time
- try to hold power btn and quick pushing vol+
If you will get to "no command" screen, press again pwr+vol up and you should be in recovery mode. Good luck

somin.n said:
Hi! No Shut down your phone and try "the game" with power button and vol+ btn... I didn't find any tutorial and it is slightly lottery, but you could get directly to recovery mode if you will press this btns in correct way:
- try to hold them for long time
- try to hold power btn and quick pushing vol+
If you will get to "no command" screen, press again pwr+vol up and you should be in recovery mode. Good luck
Click to expand...
Click to collapse
Interesting, I get the same error message as I do when I try to enter Download Mode. So this is different than the power and volume down, and different than just restarting it.
So far I just keep getting back to bootloader screen saying operation denied. But might keep trying it here and there haha.
Thanks for your help.

I had the same problem. I was able to solve it by selecting the download mode in the bootloader. There was an error message. Then I fastboot flashing unlock on the console. Then the bootloader is unlocked. No idea why this worked.
Maybe this will help someone who encountered the same problem.