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?
Related
Now I know what you are thinking: Well you need to install the drivers. Well that's all said and good, except the problem is when I boot int ADB (hboot? Unsure of what to call it.) There is no hardware at all being installed. At all. There isn't any devices that are connected and the computer doesn't detect anything. My problem is that my power button is broken, and I'm not quite able to get a new phone yet. Because of this, I cannot boot into recovery to flash a new rom, nor can I install Blackrose to use the trackball to avoid this problem. I'm just basically stuck because my phone is now a useless brick because I cannot flash a rom since I wiped my phone. Ideas?
try PASSIMG method?
will this help getting to recovery to flash rom without pwr button
http://forum.xda-developers.com/showthread.php?t=1419813
rugmankc said:
will this help getting to recovery to flash rom without pwr button
http://forum.xda-developers.com/showthread.php?t=1419813
Click to expand...
Click to collapse
Ha the ironic thing is I bought this and used it to wipe my phones rom because I was planning on installing blackrose and then QND. Sadly nope, because I can't get to the recovery itself because I can't press recovery on the bootloader bit.
////////////////
I'm unfamilliar with the Passimg method..got any links? I did a search but couldn't find anything.
Passimg is in wiki under nexus one, never used it--yet
So, not sure if it will help
Yeah not sure if it will work. If I read it correctly the OP wipe his phone clean, no OS or anything on it and can't get into recovery. I only suggest PASSIMG hopefully the phone pick it up upon reboot while holding down the VOL DOWN button.
ADB is a daemon that runs in OS, after the kernel boots.
You're booting into HBOOT. So you won't get anything but fastboot. This is normal and how it should be.
You can either use PASSIMG method, or open your phone and fix the power button for $30-something + having good hands, or even for $0 + thin wire + soldering equipment + very good hands, and optional microscope.
in this case would you be able to use fastboot boot recovery.img and restore a backup or flash a rom?
If you have unlocked bootloader - yes, by all means. But not without it.
The problem is that if power button failed, and bootloader isn't unlocked - you can't unlock it anymore, the procedure requires pressing power button to confirm.
did you try this tut on nexus one wiki?
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Unroot/restore
cheers
Question: If your power button doesn't work - how do you currently turn ON your phone?
Let's keep it simple and try the obvious first. Is USB Debugging turned on in the phone?
Go to Menu -> Settings -> Applications -> Development -> (check) USB Debugging.
2nd, make sure you have the android SDK installed on your computer (if so, download the usb drivers with the androidsdk app that's included).
You can also right click My Computer -> Manage -> Device Manager -> Make sure under Android Devices yours is listed and that there are no yellow question marks. If there is, do the android sdk drivers step and then right-click the icon in device manager, choose Update Driver and point it to the android sdk drivers folder.
Finally, ADB works in recovery and when phone it booted but NOT in Bootloader mode.
If you can get ADB working then you can install a custom recovery using Fastboot (in bootloader mode) then click Recovery to boot into the new recovery. Also, while in the recovery or ROM you can use "adb reboot recovery" to boot into recovery menu.
Hit Thanks if this helped.
I'm not new to clockwork recovery, and I have flashed many Roms on my Nexus 7........ today I did a full back up of my latest ROM and I downloaded the latest version of the bug less beast .....I let rom manager do the back up and flash......then there was an error flashing the new rom and an abort and a reboot.......no im stuck on the google screen with the little un-locked lock at the bottom of the screen......if I reboot and go into recovery it just goes back to the google screen and stays there.....any clue as what I should do ??
Search around the forums for solutions.
Use the Wugs toolkit to make your work easier.
It's not bricked its standard procedure you just need to plug it in
Sent from my ADR6425LVW using xda premium
download .zip from google and restore it to your tablet (this is full wipe)
a1exus said:
download .zip from google and restore it to your tablet (this is full wipe)
Click to expand...
Click to collapse
To manually enter recovery from the bootloader on devices prior to 4.1.2 (don't know if it was fixed. its a glitch from google in the bootloader) you must have the USB (OEM of course) connected to a USB port on the computer. Then you can boot to bootloader and use the volume buttons to enter recovery. It may take trying a few times, like connect to usb port before powering on, connect to USB port once you're in the bootloader, etc, but that's your only issue unless when you panicked you tried some other solutions.
CharliesTheMan said:
To manually enter recovery from the bootloader on devices prior to 4.1.2 (don't know if it was fixed. its a glitch from google in the bootloader) you must have the USB (OEM of course) connected to a USB port on the computer. Then you can boot to bootloader and use the volume buttons to enter recovery. It may take trying a few times, like connect to usb port before powering on, connect to USB port once you're in the bootloader, etc, but that's your only issue unless when you panicked you tried some other solutions.
Click to expand...
Click to collapse
My recovery is not working I flashed clockwork mod and something happened to the recovery.....its like it not there....there is an option for it but when I enter it it just goes back to the google screen
GCSM said:
My recovery is not working I flashed clockwork mod and something happened to the recovery.....its like it not there....there is an option for it but when I enter it it just goes back to the google screen
Click to expand...
Click to collapse
dude, i'm told you what you need to do, i had erased manually my bootloader,recover,system,data and i was able to restore w/ what i told you it worked w/out any issues
Get fastboot. plug into your computer and do these:
fastboot flash recovery recovery.img (recovery.img is whatever file you have for recovery. IMO, get the newest touch recovery from CWM and have it in the same directory as fastboot)
fastboot reboot-bootloader
From there, leave it PLUGGED IN and get back into recovery. Worked for me.
My rooted N7 has stopped starting on. It will stay stuck on the Google screen with the unlocked icon and remain so until the battery dies. My only option is hard reset and choose recovery. Any other option will bring me back to the Google screen. The recovery will allow me to be in the ClockworkMod. When I went to the "apply update from sdcard" option, there are no more root folders. The N7 has been wiped. This causes it to not connect to the computer, Mac or PC. PC will detect a device, but it will list it as Grouper and not finish the installation of the drivers. I cannot push recovery images into the device because I cannot connect to the device. I tried pushing images using ADB, but my terminal states that there are no devices. I tried using Wug's toolkit, but it cannot connect to the device to reboot it or carry on to any steps.
I am stuck. What can I do to fix this? How can I just get it to just start up?
Download the drivers (link is somewhere around here, don't have it ATM) if it only shows up as grouper.
And/Or go to bootloader/fastboot mode and flash a factory image via fastboot.
Download drivers as above mentioned then use Odin or fastboot method to flash stock (now available on Google devs). I recommend Odin just because that method has worked for me before when my device wouldn't even turn on. It also also possible to use wugs "flash stock+unroot" button in his toolkit after installing the drivers, just boot into boot loader from powered off state and press flash stock and unroot with the soft brick option selected. This method is my usual unbrick method.
Sent from my Nexus 7 using xda app-developers app
Hi, I accidentally formatted my phone yesterday night. Trying to flash the factory image from command prompt using this guide http://forum.xda-developers.com/showthread.php?t=2010312 but I am stuck on Google logo and cant enable the USB debugging mode under settings. I think i did install the driver using Root Toolkit as it shows under device manager but toolkit says adb device not found (see attached).
Please advise how can I bring back my phone to normal.
vineet381 said:
Hi, I accidentally formatted my phone yesterday night. Trying to flash the factory image from command prompt using this guide http://forum.xda-developers.com/showthread.php?t=2010312 but I am stuck on Google logo and cant enable the USB debugging mode under settings. I think i did install the driver using Root Toolkit as it shows under device manager but toolkit says adb device not found (see attached).
Please advise how can I bring back my phone to normal.
Click to expand...
Click to collapse
Boot device into boot loader and in the toolkit tick the current status as "soft-bricked/bootloop" and do a "back to stock"
*hint* You don't need ADB; you need fastboot.
Have, same issue, but in bootloader mode, windows not seen device.
Only what I have chance to fix it, write some from usb-otg thru twrp?
In download mode too several computers with different cables not see device. Only one pc with windows xp reconize unkown device with pid vid 0000
Could someone please help.
I've just updated from KK 4.4.4. to Lp 5.0.1 via OTA updates.
Then I tried to install TWRP 2.8.6.0 using Odin 3.10.6 (and 3.09), but I can't boot into TWRP, it just goes into Android System Recovery (or whatever it's called).
Before I updated, I could successfully use TWRP, root and create/restore backups etc. But, since the OS update I can't (plus I will have lost root, as I downloaded/installed the KK ROM as a "clean install".
From looking around various sites and watching videos. I think I need to side load TWRP using ADB.
But, I've visited the Dev. site, downloaded the SDK zip files. Extracted them, but the folder that should contain the files (platforms) is empty.
So, I downloaded the exe file. It wouldn't allow me to install it as I don't have Java installed.
I downloaded and tried to install Java, but it fails to install. Just F typical.
Could someone offer an easy to follow step by step advice and maybe post the files I need to use (if I do need to use ADB).
I'm using 910F and USB debugging is allowed.
Thank you.
************ EDIT ************
Never mind. I had to flash the Lp 5.0.1 stock ROM to fix the problem and now TWRP works.
******************************
Is reactivation lock enabled? If yes, disable and try again
abdyasar said:
Is reactivation lock enabled? If yes, disable and try again
Click to expand...
Click to collapse
abdyasar said:
Is reactivation lock enabled? If yes, disable and try again
Click to expand...
Click to collapse
Thank you for your help.
The reactivation lock is disabled.
To update my OP, other things I've tried:
I've downloaded and installed the basic files for ADB as well as the full SDK.
Some site say to update the ADB files to the Google USB Drivers (found in the SDK). It just says I'm up to date when I try to find newer drivers via Device Manager.
Tried flashing CWM instead of TWRP using Odin.
Tried installing TWRP (zip) when in the Android System Recovery mode via SD card.
When using ADB. My device is listed when I type "adb devices".
But when I type "fastboot flash recovery <the name of the TWRP file .IMG> I just get "waiting for device".
I get this message if I'm in Bootloader mode or using the phone "normally".
Hopefully it works out
Firstly download TWRP from the website : https://dl.twrp.me/trltexx/twrp-2.8.6.0-trltexx.img.tar.html
Then turn your device off and remove the battery for around 10 seconds (make sure the device isn't connected to any charger or anything via the USB cable).
Then after the 10 seconds put the battery back into the device and hold the home, volume down and power button.
Once you are in download mode and it says 'Downloading', plug your device into computer using the USB cable.
Open up Odin as admin and make sure no security software is interfering; once your device shows up in Odin select 'PDA' and then browse to the directory of the recovery file.
Then press start, however while it's flashing press the volume up and home button and this should boot the device directly into recovery. This is important as sometimes stock firmware might revert to stock recovery if you don't boot into recovery at least once.
I hope this helps you out.
UPDATE:
Crap, I didn't read that it worked out XD Ignore me ;P
Battlehero said:
Firstly download TWRP from the website : https://dl.twrp.me/trltexx/twrp-2.8.6.0-trltexx.img.tar.html
Then turn your device off and remove the battery for around 10 seconds (make sure the device isn't connected to any charger or anything via the USB cable).
Then after the 10 seconds put the battery back into the device and hold the home, volume down and power button.
Once you are in download mode and it says 'Downloading', plug your device into computer using the USB cable.
Open up Odin as admin and make sure no security software is interfering; once your device shows up in Odin select 'PDA' and then browse to the directory of the recovery file.
Then press start, however while it's flashing press the volume up and home button and this should boot the device directly into recovery. This is important as sometimes stock firmware might revert to stock recovery if you don't boot into recovery at least once.
I hope this helps you out.
UPDATE:
Crap, I didn't read that it worked out XD Ignore me ;P
Click to expand...
Click to collapse
Thanks for the reply.
Yes, I did fix it by re-flashing.
But, the info will be useful if I get into a similar situation again. Or will help anyone else who's stuck.