Database Users

Nexus 7 Stuck in Boot Loop After Font change

So to make a long story short, I've been stuck on android 4.2.2 for a while now because I changed the Roboto fonts (Roboto Bold, Roboto Italic, and Roboto) After discovering this I went and re-rooted my tablet to put the fonts back on so I could OTA update. I couldn't find the fonts on any font applications that matched the SHA1 checksum, so I plugged my device into the computer to put the files on manually I downloaded earlier. This is where some problems arise. My computer has having some problems with the drivers for some reason, so the only way to move the files on was if I turned USB debugging off. So thats off, and my computer won't register that the device is plugged in. Well now we get to the part of the story where I was using ROM toolbox lite and tried installing all three of the new fonts all at once. Bad idea, I now know. So my device is stuck in a bootloop, and when I try to go into recovery mode it gives me the error: No command set. I have no idea what to do guys. Any help is very much appreciated. It is kind of upsetting how a change in fonts can brick your device.

1. Download and install Nexus Root Toolkit v1.8.0: Nexus Root Toolkit v1.8.0 | WugFresh
2.. Connect to PC and Boot in Fastboot Mode: VOL DOWN + POWER ON
3. In the toolkit, under "Back to stock" tick "Soft-Bricked/Bootloop"
4. Click "Flash Stock + Unroot"
5. When done you will (should) have a working Nexus again.

jase33 said:
1. Download and install Nexus Root Toolkit v1.8.0: Nexus Root Toolkit v1.8.0 | WugFresh[/URL]
2.. Connect to PC and Boot in Fastboot Mode: VOL DOWN + POWER ON
3. In the toolkit, under "Back to stock" tick "Soft-Bricked/Bootloop"
4. Click "Flash Stock + Unroot"
5. When done you will (should) have a working Nexus again.
Click to expand...
Click to collapse
Hello, Thank you for the helpful tip on how to fix this. I tried what you said but a problem appeared making the device fail to apply the factory image. What I am assuming is it was because the root that I used did not make me unlock the bootloader. so i'm doing that now. It should let me flash a factory image after that, right?
UPDATE: I tried unlocking the bootloader, but it didn't work. my device is not being recognized via ADB because I think the drivers are not properly installed, or it could be because USB debugging is not on. So I cannot get to the point where I can unlock my device.

JakeTheOneDude said:
Hello, Thank you for the helpful tip on how to fix this. I tried what you said but a problem appeared making the device fail to apply the factory image. What I am assuming is it was because the root that I used did not make me unlock the bootloader. so i'm doing that now. It should let me flash a factory image after that, right?
UPDATE: I tried unlocking the bootloader, but it didn't work. my device is not being recognized via ADB because I think the drivers are not properly installed, or it could be because USB debugging is not on. So I cannot get to the point where I can unlock my device.
Click to expand...
Click to collapse
I have the same kind of problem. Did you manage to unlock it?

Another Can't boot after unlock and twrp install

I'll try to make this brief and to the point as I realize how many people come here seeking help.
I've rooted many android devices (my first was an htc incredible) so I'm not exactly "new" per say, but don't really fully understand what I'm doing either long story short.
Got my nexus 7 today, tested some things with the screen when I first got it (just playing videos to see how bright it is)
I Followed a video suggested (somewhere) on the forums (video here (but I can't post urls))
-Sat down, got the usb drivers from here - Can't post link
-got adb fast boot tools - can't post link
-Downloaded SuperSU
-Enabled usb debugging in settings
-Booted into recovery
-Updated Driver when prompted
-allowed usb debugging after entering adb devices command
-used adb reboot bootloader command
-used fastboot oem unlock command (worked succesfully)
-used flash recovery openrecovery-twrp-2.6.0.0-flo (personally I think it didn't flash correctly because I don't know how to explain issues I will detail below
- (unless this is where I went wrong) rebooted to get into os so I could place supersu.zip on internal storage for rooting
- sticks at glowing X
ADB won't recognize the nexus 7 in recovery or bootloader
Windows only sees the nexus 7 as either
QHSUSB_DLOAD
MTP USB Device
flo
I've tried wiping from recovery, it fails.
I DO seem to be able to get adb to recognize the tablet when it is in recovery mode now.
Adb lists
06d9e78e Recovery
I've tried reflashing Twrp, still can't wipe, Is it possible for me to just install kitkat from recovry straight from adb or fastboot? It's been a while but I was thinking if I could just reset the os it might work. I have razor-krt16s-factory-7235eb0d.tgz ready to go I just don't know how to put it on the tablet without an sd card to transfer with
I have also installed Wugs Nexus Root Kit but since I have no idea what build of 4.3 my n7 is running...it really isn't doing me any good -_-.
any help would be appreciated, I'm stumped but will be continuing to dig for answers.
Thanks

[Q] SO there is no way to enable USB Debugging on a bricked N7?

Rooted my N73G with Clockwork back in 12/12 when I bought it, worked fine for a year and change. Last week it wouldnt boot past the glowy X. Tried resetting cache, Dalvik cache, and factory reset options in Recovery Mode. Nothing
Downloaded the SDK as a couple different tutorials instructed. Tried Skipsoft's toolkit. Why does every bloody recovery tutorial tell you "enable USB Debugging in the Settings menu" when you cant bloody well boot to a working OS???????
Needless to say, everything I try deadends at unable to do whatever because USB Debugging isnt enabled. Now it wont even boot into Recovery Mode, stopping at the bootloader.
Wat do?

aeldergoth said:
Rooted my N73G with Clockwork back in 12/12 when I bought it, worked fine for a year and change. Last week it wouldnt boot past the glowy X. Tried resetting cache, Dalvik cache, and factory reset options in Recovery Mode. Nothing
Downloaded the SDK as a couple different tutorials instructed. Tried Skipsoft's toolkit. Why does every bloody recovery tutorial tell you "enable USB Debugging in the Settings menu" when you cant bloody well boot to a working OS???????
Needless to say, everything I try deadends at unable to do whatever because USB Debugging isnt enabled. Now it wont even boot into Recovery Mode, stopping at the bootloader.
Wat do?
Click to expand...
Click to collapse
BETTER DESCRIPTION....
Rooted my N73G with Clockwork back in 12/12 when I bought it, worked fine for a year and change. Last week it wouldnt boot past the glowy X. Tried resetting cache, Dalvik cache, and factory reset options in Recovery Mode. Nothing
Downloaded the SDK as comminus's tutorial instructed. Installed Java Dev Kit and Android SDK. Got to the command line, but under the right directory when I try "adb devices" it doesnt list my tablet.
Tried Skipsoft's toolkit. Why does every bloody recovery tutorial tell you "enable USB Debugging in the Settings menu" when you cant bloody well boot to a working OS???????
Needless to say, everything I try deadends at unable to do whatever because USB Debugging isnt enabled. Now it wont even boot into Recovery Mode, stopping at the bootloader.
Wat do?

If usb debugging was enabled, one might save the important files from the device before flashing it.
Since you boot into the bootloader, you can flash a factory image. I recommend this guide but all of your data will be gone.

Erovia said:
If usb debugging was enabled, one might save the important files from the device before flashing it.
Since you boot into the bootloader, you can flash a factory image. I recommend this guide but all of your data will be gone.
Click to expand...
Click to collapse
From the linked guide (the one I've been using) "Enable usb debugging on your device (found under Settings > Developer Options)
NOTE: Since Android 4.2 the Developer Options are hidden by default."
How can I enable USB Debugging on a tablet that is bricked? Further, the SDK program doesnt see my tablet connected. I hear a little connection tone in windows when I plug it in, but running adb.exe from the command line and using an "adb devices" command shoes a "List of connected devices" that is empty.
Only the Skipsoft toolkit seems to want to even see my tablet, no matter what USB port I try,

There is no need for adb (it is only used to boot into bootloader). What you will need is the fastboot commands in the "Flashing the Factory Image" part, but be carefull to flash the proper image and to the proper partions.

Erovia said:
There is no need for adb (it is only used to boot into bootloader). What you will need is the fastboot commands in the "Flashing the Factory Image" part, but be carefull to flash the proper image and to the proper partions.
Click to expand...
Click to collapse
Sorted. THanks.

How do you enable usb debugging using fastboot

No idea how to do this.....
I think ive bricked my device...
It keeps saying `booting failed` when i try and either start my device or go into recovery mode.
Im unable to unroot and flash back to stock if my usb debugging is disabled.

This problem is linked to this one..
http://forum.xda-developers.com/showthread.php?p=50466599
thanks

You can't and you won't need it. Read this guide, download the latest factory image from here https://developers.google.com/android/nexus/images (be 100% sure to download the one that is for your device).
Follow the guide from "Extract the Factory Image" and in the "Flashing the Factory Image" section you can skip to 4).
Good luck.

orange state, your device has been unlocked and can't be trusted

I have a old phone that had been stuck at this state for a while,
`orange state, your device has been unlocked and can't be trusted. Your device will boot in 5 seconds`
Should I follow this guide to un-brick it?
https://forum.xda-developers.com/le-2/how-to/repair-hard-bricked-phone-x52x-sd-t3648348

I have tried to follow the guide but after pressing volume up and down button the phone does not boot. Only shows it is in orange state.
Also if I hold the volume down button and the power button, it shows booting in fastboot.
But the FlashOne app cannot detect any phone.
What should I do ??:crying::crying::crying::crying:

mrchow19910319 said:
I have tried to follow the guide but after pressing volume up and down button the phone does not boot. Only shows it is in orange state.
Also if I hold the volume down button and the power button, it shows booting in fastboot.
But the FlashOne app cannot detect any phone.
What should I do ??:crying::crying::crying::crying:
Click to expand...
Click to collapse
What should I do? You need to read, the answers to your questions are here a million times over. Always do your homework first. Also thank someone who helps you. Otherwise they will not continue helping you.
FlashOne: Why are you using FlashOne? You are not bricked. Also FYI, if using FlashOne , you have to be in EDL mode. not fastboot.
Now here is probably good news, since you can enter fastboot then you are very likely just fine,and you are definitely not bricked. However, you will probably end up losing any files that you had on the phone, because the user data( storage ) will most likely need to be formatted, (type yes reboot to recovery)
So my instructions are to help get your phone working again, not to recover data. Unfortunately, you didn't provide much information so I have to assume some things.
Is the bootloader unlocked?
Have you flashed custom roms before?
Which phone do you have? A Leeco X5?? A Leeco X6??
Let guess and say that maybe bootloader is unlocked, you are asking a question on XDA so maybe that is a safe guess?
What you need to do is use ADB or the the Tool all in One and flash Recovery and root. Here comes the reading part again, I can't explain everything or I will be here all day. I assume that you know how what Recovery and root is?
Download the correct TWRP Recovery for your device, if you don't know your way around ADB too well.
You can use Mauronofrio's "TOOL ALL IN ONE" for removing encryption, installing TWRP, Root, your ROM, Gapps, and even to restore to stock Recovery, or to flash a stock Rom
Read that thread for instructions or for any questions.
If your device not recognized it is a usb driver issue, ensure that device drivers are installed and You will need to reinstall the Google USB driver, and while you are at it check to make sure adb is up to date. The All in One tool can do all of this for you, its with the advanced menu section. ** You will need to temporarily disable Windows defender for installation. **
Use the All in One tool to flash Recovery, then boot to recovery.
Ensure that you have TWRP installed permanently by rebooting to Recovery and then rooting the phone.
Always reboot to Recovery and check the boxes to install TWRP when rebooting to recovery
To remove encryption you will always need to format the storage
Not wipe >> Choose Format > type yes> Reboot to Recovery)**
(If you see a message that says there is no OS installed are you sure> Click Yes, then reboot to Recovery, ignore message about no OS)
When you reboot to recovery swipe to be able to read and write to the device.
Use an OTG Usb adapter to connect a USB to your phone and flash your prefered rom, Gapps, and root. Reboot to recovery, thenn reboot to system. If you were successful, the error message will be gone and you will be able to set up the phone.
As mentioned the tool will help you with installing your rom, Gapps, and root.
The All in One Tool can completely restore your phone to stock if absolutely needed. It actually links to Mauronofrio's server and it has all of the significant EUI Stock Roms, in case you want to restore the stock rom.
Hopefully this helps you, Good luck.

tsongming said:
.
Click to expand...
Click to collapse
thank you so much for the in depth explanation.
sorry for the super delayed reply.
I will try to follow the instruction and will update here soon.
again thank you.

I have the same problem with umidigi bison, I tried to root with the mtkroot tool v2.5.8, the process ended correctly but when I turned on it showed orange, the problem is that I cannot enter with any combination of keys, it does not recognize adb, please help