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.
Related
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
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?
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.
So what happened was that I tried to install the update of paranoid android's latest version. Since TWRP cannot install it, I used CWM. All my back-ups are in TWRP so I had no chance to restore. Now, my device is stuck in recovery mode. I could enter the fast boot mode. Now I don't know what to do since all guides in restoration say that I have to enable USB debugging, something impossible in a device which cannot enter the interface.
Please help. Thanks
You only need fastboot access so you don't need usb debugging, but you will need the Android SDK.
1) Read this guide.
2) Download the latest factory image from here.
3) Follow the guide from the "Flashing the Factory Image" section's 4th point.
Good luck.
Hey Guys. This guide will help you if
1. If Using Custom Rom and want to revert to latest stock rom.
2. If Stock Rom got corrupted or became laggy.
3. You want to reinstall stock rom.
Warning:
1. Method 1 require unlocked bootloader. If you want to unlock then go Here . Method 2 doesn't. Don't worry.
2. This will clean your phone just like new phone.
3. First read the post twice carefully then proceed.
4. ALL .bat FILES TO BE RUN IN FASTBOOT MODE ONLY, IF YOU DON'T KNOW ABOUT FASTBOOT MODE THEN GOOGLE "HOW TO GET FASTBOOT MODE IN ASUS ZENFONE 2
5. I may change name of files in folder. Use common sense to identify them.
Pre-requisites:
1. Charge your phone atleast 60%.
2. Backup any important data you might not wanna loose to either sd card or usb drive or pc.
3. Copy the rom zip in the sd card of your phone. (The one with size in GB)
4. Android USB Driver should be installed already, if it is not then install all drivers in the "Drivers Folder".
5. Enable USB Debugging.
For that go to "Settings" ,Scroll to bottom goto "about", goto "Software Information", tap "Build number" upto 7 times or till it
says "You are a developer now". Then go to "Settings" you will find "Developer Options", open it and enable "USB Debugging"
4. Common sense, patience.
Download Link:
For Method 1
Click here Android Filehost
Download these folders: TWRP, STOCK RECOVERY, STOCK ROM, DRIVERS
For Method 2
https://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
Procedure:
METHOD 1Step 1. Flash TWRP recovery if not installed by using "TWRP.bat" (Given in twrp folder) in fastboot mode or bootloader mode whatever you call it.
Step 2. Go to Twrp recovery then choose "wipe" then choose "Advance wipe" and tick everything except "SD card or external sd card". then swipe to wipe.
Step 3. Go to fastboot/bootloader mode and flash stock recovery running appropriate .bat file. It is given in "Stock Recovery" folder.
Step 4. When the command executes from the above step, Go to "recovery" by pressing volume down button, then press "power" button.
Step 5. You will see a dead android logo. Nothing else. Then go to stock recovery options.
If you don't know how then use following methods
Method 1:
When you see a dead android bot with an error press and hold power button, then (while holding power button) quickly press Vol up and release and then release power button..
Method 2:
Go to fastboot mode. Connect your device and open command prompt there. Then Type
Code:
fastboot erase cache
Step 6: You should see stock recovery options. Then choose "Update from sd card" and select the rom zip you pasted in SD card.
(If you don't have sd card, then paste rom in internal memory and don't tick "internal storage" in twrp in step 2) But micro
sd is preferable.
Step 7: Wait. Your phone may take 20-30 or more minutes. So leave it on charging.
METHOD 2Step 1: Download and Install all drivers given in download folder. Download RAW firmware for your phone. See above in download links.
Step 2: Install "ASUS FLASH TOOL"
Step 3: Go to fastboot/bootloader mode on your phone. Run asus flash tool, select your phone model and browse for the raw firmware. Check wipe all data. And start the process.
Step 4: Wait for program to say successful. If it takes more than 30 minutes. Disconnect your phone and check phone if rom installed or not.
If this process does not work. Then switch methods.
If you have any questions, problems .. Just Comment it.
Every Suggestion welcomed. Also you can join telegram group to get help and help others.
MOD EDIT: LINK REMOVED
If the guide works for you or you want to thank me for development of tools then you can donate me via
Paypal paypal.me/KapilTapsi (You can donate any amount, It will be of great help)
FAQ
1. Having problems with device connection? like waiting for device.
Sol. Make sure you have enabled USB Debugging (Not applicable for BL Unlocking and TWRP Flashing)
Uninstall all drivers previously installed on computer(every driver of any device)
Reboot your computer. And then install all drivers given in the driver folder.
If the problem persists, try different computer and different usb cable.
2. Facing permission denied in fastboot mode or while running script files.
Sol. Try disabling your lock screen security to none.
File Credits:
1. RealYoti
Would it not be easier to get the stock raw image and just flash it with the asus flash tool?
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
Would it not be easier to get the stock raw image and just flash it with the asus flash tool?
Click to expand...
Click to collapse
Thanks for suggestion. But the reasons are
First thing is stock raw image of latest version is very difficult to find.
Second thing sometime asus flash tool stops responding. So you have to wait again for 30 minutes. Also it doesn't show progress sometimes.
Kapil Tapsi said:
Thanks for suggestion. But the reasons are
First thing is stock raw image of latest version is very difficult to find.
Second thing sometime asus flash tool stops responding. So you have to wait again for 30 minutes. Also it doesn't show progress sometimes.
Click to expand...
Click to collapse
No offense meant. But the entire collection of raw files are here: https://forum.xda-developers.com/showthread.php?t=3448966
As long as you have the correct drivers (which you need for your process too) the AFT will get the job done in one easy step.
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
No offense meant. But the entire collection of raw files are here: https://forum.xda-developers.com/showthread.php?t=3448966
As long as you have the correct drivers (which you need for your process too) the AFT will get the job done in one easy step.
Click to expand...
Click to collapse
It is a guide only. Users are free to choose from where to download. Thats it. I only shared my collection.
E: footer wrong
E: footer wrong
Installation aborted
I need your help!
I follow the instructions in Method 1 but the device give me this error message when I try to update via SD-card...
May I know whats the solution?
Rom used: Fastboot Rom WW-4.21.40.327
Thank you very much!
kenbo111 said:
No offense meant. But the entire collection of raw files are here: https://forum.xda-developers.com/showthread.php?t=3448966
As long as you have the correct drivers (which you need for your process too) the AFT will get the job done in one easy step.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thanks, finally got it
Hey...when I get to part 6 I get this Error >>
footer is wrong
signature verification failed
installation aborted
Hey..I also Tried Flashing with the method 2 it was installing but i got an error after
Man, this thread saved my ass. thank you for all your time all!
I have the Asus Zenfone 2 ZE551ML with sound issues, (it's only when the phone rings that the speaker works) and I put it into recovery mode to wipe cache/data, but it got stuck while doing that and I forced it off. But now, it's stuck at the Asus Boot logo with the rotating icon underneath.
Please help!!!!
Hello, my 551ml has stock LP, it's rooted with bootloader unlocked and Xposed installed. If I want to install the latest MM with through the raw flashing tool, should I install the MM bootloader first or it is included into the raw file? Thank
just trying to revert back to locked bootloader and stock recovery once I have wiped all data with twrp and go to bootloader how do I actually flash stock rom noob thanks
stevegtrlmk said:
just trying to revert back to locked bootloader and stock recovery once I have wiped all data with twrp and go to bootloader how do I actually flash stock rom noob thanks
Click to expand...
Click to collapse
use asus flash tool
damn my asus flash tool says error flashing image failure.... (remote not allowed to flash this partion)
ow btw i already bricked it cause it only does boot fastboot lol no more android
how do i flash it back again i need to send the phone back to amazon by 18/05 lol i mean i can just send it back and say also that it wouldnt boot cause i tried to reset it to get my touchscreen to work but yeah lol dont want them to refuse my retour
No way to simple flash the stock rom through/keeping twrp in the device, like I do with other Custom Roms?
Ok. humm, in AFT, it recognize my phone. (there is no OS on it), i choose the good model, i choose the good firmware, but i got this error in a box
"Can't open file 'SERIALNUMBER_frp_request_server_log.txt' (error 5:denied access)" i can only press OK
and now the button under "state" is red and under description, it's " check the detected serial number failure (not found the device of "SERIALNUMBER") "
you understand the i've replace the real serial number by SERIALNUMBER in those lines.
Anyone ever had this problem?
euphrodil said:
Ok. humm, in AFT, it recognize my phone. (there is no OS on it), i choose the good model, i choose the good firmware, but i got this error in a box
"Can't open file 'SERIALNUMBER_frp_request_server_log.txt' (error 5:denied access)" i can only press OK
and now the button under "state" is red and under description, it's " check the detected serial number failure (not found the device of "SERIALNUMBER") "
you understand the i've replace the real serial number by SERIALNUMBER in those lines.
Anyone ever had this problem?
Click to expand...
Click to collapse
Try manual flashing then. Not the aft flashing
Sent from my MI MAX 2 using Tapatalk
Kapil Tapsi said:
Try manual flashing then. Not the aft flashing
Sent from my MI MAX 2 using Tapatalk
Click to expand...
Click to collapse
Ok thanks, i'll look for a thread that explain this.
euphrodil said:
Ok thanks, i'll look for a thread that explain this.
Click to expand...
Click to collapse
did you find any?
i want to remove the lineageos and install latest stock LP but i have no clue how to do it