Related
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
cbs2002 said:
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
Click to expand...
Click to collapse
The key piece of information for your symptom is in this line:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
The other lines do help provide background as to the other modes such as recovery and download working properly, which indicates the issue is not *serious*.
The symptom you state, where the device does not boot past the boot logo, usually means the device is not able to boot the kernel or boot past the kernel. The boot logo appears while the kernel is being loaded on the device. Generally, after the boot logo and kernel finish loading a boot animation appears which indicates the kernel has usually handed off to the Android OS to continue booting.
My approach would be to load a completely stock ROM in order to restore a working kernel and ROM to the device. I generally perform this step as a baseline to get everything back in working order.
In many instances the ROM is dependent on the kernel. Your situation requires at least a kernel to be loaded and in order to prevent any further issues, it would be best to load a ROM dependent on the kernel being loaded.
A simple way would be to grab the stock factory images from Google's site and load those back onto the device.
Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode.
Hope that helps!
Since you're rooted I'm going to assume you have ADB and the necessary drivers installed.
1.) Download a ROM. It doesn't have to be stock, you can choose any of the ROMs from the development section for your device. Most of the ROMs are packaged with a kernel already.
2.) Save this ROM file to the same folder where you have ADB installed.
3.) Boot your phone into CWM recovery and plug it into your computer.
4.) Use ADB to push the ROM zip file to your phone (/data/media). For example:
Code:
c:\gnex\>adb push rom.zip /data/media/rom.zip
5.) Use CWM to wipe data, cache, and davlik-cache
6.) Install zip from sdcard and flash the rom.zip.
RMarkwald said:
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
Click to expand...
Click to collapse
1. I am using GSM
2. Whenever I turn on my mobile, the 'Google' and 'Unlock' logo appears and then freeze, with no more respond at all
* I definitely mess up some system files, but don't know how to restore it because my PC do not recognize my mobile.
Thanks
I am seeing more and more of these threads about "bricked" nexus's is this an issue with how new the phone is or people not following instructions properly as they are too eager to root their phones?
All else fails flash back to stock and count yourself lucky.
To silow,
Thanks for your advice, but fail
1. I put adb.exe, adbwinapi.dll and fastboot.exe (3 files) under my PC C drive (i.e. C
2. I also put a stock Rom (rename as rom.zip) under C drive (i.e. C
3. Boot phone into CWM recovery and plug it into computer.
4. Use cmd command and type c:\gnex\>adb push rom.zip /data/media/rom.zip
5. It fails , It say "Access Denied" (in Chinese, but I translate it into English here)
6. How do I use ADB (it is a ADB.exe file, When I double click it, it only flash up a few page very fast and nothing happen)
Please assist!
To Joeykrim,
I agree that
"Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode."
But how? (according to my symptoms)
The command I gave you was just an example. I didn't spell out the exact details because I thought that you would know how to do it considering you rooted the phone.
If you put the adb.exe and AdbWinApi.dll file in your C: drive, make sure you copy the ROM file to your C: drive too. In the follow example I'm going to use "ROM.zip" but use the name of the ROM file that you downloaded. Also I am assuming you are on Windows XP.
1.) Boot your phone into CWM recovery and then plug it in.
2.) Go to your Start Menu and choose Run. Then type in "cmd" without quotes and hit enter to open a command prompt.
3.) Enter:
Code:
cd c:\
4.) Enter the following to make sure ADB can see your phone:
Code:
adb devices
You should see something similiar to this to confirm ADB can see your device:
List of devices attached
019B756F0C018012 device
5.) Enter the following command to copy the ROM file to your phone. Remember to replace ROM.zip with whatever the name of the ROM file is:
Code:
adb push ROM.zip /data/media/ROM.zip
6.) Use CWM to wipe data, cache, and davlik-cache
7.) Install zip from sdcard and flash the rom.zip.
To Silow,
You have been very helpful, but I fail.
"You should see something similiar to this to confirm ADB can see your device:
List of devices attached"
There is NO device number shown after the phrase 'List of devices attached'
To recap:
a) Phone is already plugged in my PC, under the Clockworkmod Recovery 5.5.0.2
b) adb.exe and AdbWinApi.dll file are under C: drive directly
c) Also type cmd in 'Run', a black Dos window shown C:\windows\system32\cmd.exe
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Pls don't give up on me!
: )
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot (edit: wrong!)
Sounds like your ADB USB drivers are not correctly installed. While the phone is under CWM, when you plug it in is your computer attempting to install drivers for a new device?
Download these bare ADB Interface drivers.ADB USB Drivers
Go into Device Manager on your computer and check the device list for any unknown devices or "?" devices. If you need to update those drivers by pointing them to the drivers you downloaded and extracted from that link above.
When the ADB Interface drivers are correctly installed you should see Android Phone listed under under your Device Manager when it's plugged in with CWM recovery loaded.
---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
edit: i did appear to have one missing driver, my mistake. it was listed in device manager as "unknown - full"
its funny cause i never had to use adb from cwm before, never noticed
cbs2002 said:
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Click to expand...
Click to collapse
This symptom generally occurs from not having loaded the drivers for the hardware. As with the majority of hardware devices when being connected to a Windows machine, the drivers need to be loaded. Sometimes these are automatically loaded and other times they have to be manual loaded.
As an alternative and for future reference, the android-sdk package contains general USB drives which usually work for Google Nexus devices.
Generally, as this providers a *cleaner* install, best practice as recommended by Google is to download the whole android-sdk .zip and then from the installer download/install the pieces needed, such as platform-tools (containing adb) and USB drivers as opposed to extracting out the adb.exe and .dll file and installing manually.
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
Agreed. To add greater clarification so there is no confusion: adb can't be used from the bootloader.
The /sbin/adbd daemon on the device is only loaded while in normal android boot mode or in recovery mode as called by the init.rc (or on some older devices, recovery.rc) file in the boot process.
Bootloader mode will only work with fastboot while it is in fastboot usb mode.
On some devices, the bootloader has a separate menu for fastboot and on other devices, the fastboot mode is directly entered when entering the bootloader.
Hope that helps clarify!
To silow (and all other helpers)
1. I fail
2. The ADB USB drivers in my PC should be fine as in Device Manager , I can see Android Phone with Android Composite ADB Interface. (No exclamation mark)
3. On the other hand, whenever I plug my mobile into PC, I can see "Unknown-Full"
4. In DOS, when I first type "adb devices" it shows
* daemon not running. starting it now on port 5037*
*daemon started successfully *
List of devices attached
(but NO device number shown!)
5. When I enter adb devices second time, it shows
List of devices attached (No device number shown)
Thank you so much , but it is Hong Kong time (my place) at 0511 am , I didn't sleep all night and I am very tired.
If you don't mind (especially big helper Silow), please give me email so that I capture screen picture and show you in detail (hope it may help)
my email is
[email protected]
I need to sleep now, I will check my email and see you guys or come back this Forum later (several hours later, as I really need some sleep right now)
Pls don't give up on me as this is an expensive mobile. I think the hardware is fine, just need to figure out a way to unbrick it.
Thanks, and see you!
What you need to do is right click on "Unknown-Full" and click on "Update Driver...". Then choose "Install from a list or specific location". Make sure "Search for the best driver in these locations." is checked and "Include this location in the search:" is check. Click on the Browse button and browse to where you extracted the driver files from the link I posted above. Click Next and this should install the correct drivers for you. Afterwards try "adb devices" again to see if ADB now reconizes your device.
To Silow,
Fail.
1. Already installed the drivers you gave me (and there is no 'Exclamation' Mark) in Device manager
2. Situation is the same , Cannot recognize my mobile (i.e. no Device No. after entering adb devices)
3. "List of devices attached" shown in DOS video but without any number.
No other method?
My mobile is really 'bricked' to death?
To Silow and all,
Something important
1. When choose 'install zip from sd card' under CWM, a list of old folder names remains
(e..g gameloft, DCIM, Pictures, etc). That means almost all old files, folders are STILL in my mobile!
2. I have already use the funcion 'Wipe data/factory reset', 'wipe cache partition', ' Wipe Dalvik Cache'
Perhaps my CWM has problem?
What happens when you update drivers for Unknown-Full?
Boot into fastboot and see if your computer recognizes the phone by checking device manager. The key here is to get your computer to see the phone either in fastboot or CWM.
Perhaps try another cable, USB port, or new computer.
The goal is to get Android Phone ADB Composite Interface to show up in device manager either in Fastboot or CWM. Without that done you cannot use Fastboot to flash nor ADB to push a zip file to the phone.
Sent from my Galaxy Nexus using XDA App
How to USE FASTBOOT commands in case your Device got Soft-Bricked with NO DISPLAY
Click to expand...
Click to collapse
Let's describe Softbrik:-Anything caused to your phone except damage to Hardware of your phone which put your Device into a state where it is not booting up and kept showing White, Gray, Blue or Black Screen or Either It gets stuck at Company logo Screen. This may occur if something goes wrong during Rooting, flashing Recovery or ROMs or during Updating in Recovery Mode or either being caught by some wrong software or VIRUS !!!
Preface to the Guide:
Fastboot is a command line tool used to directly flash the filesystem in Android devices from a host computer via USB. It allows flashing of unsigned partition images and also can erase partitions. Its a part of Android Developement Kit (Android SDK).
Use of FASTBOOT is disabled in production devices since USB support has been disabled in the bootloader. You must have an Engineering SPL, or an SPL that is S-OFF or Unlocked bootloader to use 'fastboot'.
After installing the Android SDK or ADB Standalone you can use 'fastboot' in addition to the more common ADB.
One can use the attached .android folder if u want to skip downloading Android SDK. (Refer Attachment)
Verify SPL S-OFF or Bootloader Unlocked:
Not required for Micromax !! But certain Production Devices like Sony HTC LG etc may need bootloader to be unlocked before carrying out this process. My simple advice to people is.. "If you enjoy experiments on your device, you must be ROOTED and to ROOT you device you may need to have unlock bootloader"
Preparations:
(1) Download attached .android.zip, Extract and place .androidfolder on C:/ drive of your PC. So the path of this folder will look likeC:/.android
(Never remove this ".android" folder from C:/ coz you will require it whenever u want to experiment with you Droid using ADB or FASTBOOT methods. I assure... You can do a lot more with it; if you really explore how to use various commands !!!)
.android folder is containing adb.exe, fastboot.exe and related drivers adb_usb.ini, android_winusb.ini AdbWinApi.dll and AdbWinUsbApi.dll and other files; all together not more than 800KB
(2) Connect Device in 'USB debugging ON' mode.
Ensure Drivers for your Device are already installed on the host computer
Note: I recommend you should always keep USB Debugging opetion 'ON' as it only can help you, in case, your device get SoftBricked and you cant see anything on Device Screen. Remember that with USB debugging 'OFF' your Device can't communicate with your Host Computer.
(3) Host Computer Ability to Launch Command Prompt:
On Windows-XP or earlier, to start ADB (Android Debug Bridge) You need to locate your folder containing adb.exe where as Windows-7/Vista/Other-Latest-OS can directly launch command prompt from the Folder itself by Shift+Right Click on Mouse and Selecting "Open Command Prompt from here".
Hence 'Locating 'adb' folder-steps' are for XP users only, However higher OS users can skip it and can directly start giving 'adb' commands after opening cmd from .android folder.
(4) So now, Open Command Prompt (in Windows XP), it will return like this:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\USERNAME>
(As our adb.exe is in C:/.android.... we will type: Cd C:\.android)
C:\Documents and Settings\USERNAME>Cd C:\.android (Hit Enter)
C:\.android>
Let's give command to detect attached device by writing: 'adb device'. On hitting enter it will list all devices attached to your PC.
Code:
C:\.android>adb devices
List of devices attached
XXXXXXXX-XXXX device
Now u can do a lot while your Device is attached in 'adb mode' e.g.:
Code:
1. Rebooting into Bootloader (FASTBOOT)
2. Installing apps on as /system/app or /data/app
3. Copying Files to/from your SDCARD
4. Pulling Files or Apps already installed on your /system or /data partition
To Understand adb commands and how they work please read:
http://developer.android.com/tools/help/adb.html#commandsummary
Let's come back to ISSUE: "We have a SOFTBRICKED devices !!!"
(1) Booting into FASTBOOT mode:
Let's come back to'fastboot' as we need to flash new ROM or to apply update.zip in a Softbricked deviceNote: Let your device remain connected to PC and don't disconnect untill You finish you job-successfully and get your Device again in working Factory Condition.
""fastboot reboot-bootloader" This command is used to reboot your device into bootloader i.e into fastboot mode) and In this Mode your device will stuck into boot logo only and u cant operate it. ;D Well we are not concerned as we already have a bricked device with no screen display !!!. Lets go ahead...on cmd follow:
Code:
C:\.android>adb reboot-bootloader
C:\.android>fastboot devices
XXXXXXXXXXXX fastboot
(2) Unlocking-ReLocking Bootloader:
(Skip if u working with pre-unlocked devices)
C:\.android>fastboot oem unlock
...
SUCCESSFUL
finished. total time: 118.063s
Click to expand...
Click to collapse
(Accept/Decline warning on your devices screen. Select YES to Unlock)
(Once ROM is flashed) To relock Bootloader use command: fastboot oem lock:
Code:
C:\.android>fastboot oem unlock
...
SUCCESSFULL
finished. total time: 118.063s
(Accept/Decline warning on your devices screen. Select YES to ReLock)]
(Skip if u working with pre-unlocked devices)
(3)Get 'Recovery.img' and 'Update.zip' for your Device:
Lets Wipe the Data and then proceed to Flash new ROM/Update.zip
IMPORTANT: Copy the stock recovery.img and your devices' Update.zip[ in .android folder(You can get it even by searching it in this forum or by Googling for it..) So I assume that you have it....in your .android
Abbreviations:
recovery.img = Stock Recovery of your Device
Update.zip = Update Package/Stock ROM of your Device
Let's start wiping and updating process with following commands:
(4)Wiping Old Data and Flashing new Update.zip:
Code:
C:\.android>fastboot -w
SUCCESSFUL
C:\.android>fastboot update Update.zip
(Here Replace Update with Full Name of your any Update.zip that you copied to .android folder)
Your phone will update and automatically reboot into the Factory State. Cheers !!!
Note: Its important to spell the file name correctly that u want to flash/update. No space between name are allowed. This process will only be successful if your device is still carrying recovery partition 'intact'.
.....If above wiping/updating FAILS....
If you still in "No Display State", extract update.zip to .android folder (U can use 7zip).
You will find following main .img files, each incorporate specific partition on any android device. In our case we can extract following:
boot.img -The main kernel and initrd
recovery.img -A 'backup' kernel, initrd, and OS 4 sysm recovery/maintanance
sytem.img -The main OS
userdata.img -User data and settings
splash.img -Has Boot image. can be splash1 as well.
cache.img -Temp storage
...there can be similar partition names depends on your device type.... but basically these 6 partitions constitute a ROM. Copy all of (6) files to .android folder. (Henceforth, we can use this recovery.img as stock recovery for your device.)
"As your device is bricked/corrupted, we need to erase all old Partitions and flash (rewrite) new partitions that we have extracted from Update zip and placed in .android."
(1) Lets erase all partitions first (one by one)using: fastboot erase <partition>
Code:
C:\.android>fastboot erase system
Successful
C:\.android>fastboot erase recovery
Successful
C:\.android>fastboot erase boot
Successful
C:\.android>fastboot erase userdata
Successful
C:\.android>fastboot erase splash
Successful
C:\.android>fastboot erase cache
Successful
(2) Continuing with Flashing new partionsusing the Images copied in .android:
Command: fastboot flash <partition> <partition_name.img>
Code:
C:\.android>fastboot flash boot boot.img
Successful
C:\.android>fastboot flash recovery recovery.img
Successful
C:\.android>fastboot flash system system.img :(here people gen. get stuck
Successful
C:\.android>fastboot flash userdata userdata.img
Successful
C:\.android>fastboot flash splash splash.img
Successful
C:\.android>fastboot reboot
If all successful, Your phone will update and automatically reboot into the Factory State. Cheers !!!
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
..If you are Unable to flash 'system.img' successfully...
Reason: Your device is not allowing to format and rewrite 'system' partition manually. If your device is Rooted then probably such failure will never occur.
Let's overcome this Issue as well...Try Following...
First, Understand current State of Device...
We Wiped out old partitions and Flashed new partitions except :-\ system :-\ So No System on your Device at present.
What we will do now..
We will now wipe all partitions again
We will then flash only recovery.img saved in .android folder
We will use update.zip saved in .android folder to Flash it using SD Card.
We will copy update.zip on SD Card (using adb). If you can do it manually using a card reader skip step-II in below process.
Step-I: Wiping 'partitions' and Flashing 'recovery.img':Let's wipe all partitions again:
Code:
C:\.android>fastboot -w
C:\.android>fastboot reboot-bootloader
C:\.android>fastboot flash recovery recovery.img
C:\.android>reboot
Step-II: Copy update.zip on SDCARD
Code:
C:\.android>adb push update.zip /data/sdcard
Step-III: As you can't manage to see what is happening on screen(No Display) hence Don't do mistakes here, read carefully and follow exactly:
1.Reboot Device into Recovery Mode:
On cmd type:
Code:
C:\.android>adb reboot recovery
2.Now Press 'Volume(-)' button ONCE. (Once means 'once only'-if you did mistake here repeat the Step-III)
3.Press 'Power' Button TWICEand Leave you Device for some 10 Minutes time.
If phone don't get alive in 10 Minutes Repeat Step-III again.
You may not able to see but Your phone will update and automatically reboot into the Factory State. Cheers !!!
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Explaining Last Step:
We used simple logic in last procedure/ Its nothing but updating using Recovery Mode. Always remember Custom Recovery of Micromax A56/57 has following options: (May be diferent for other devics)
As the default curser in recovery UI remains on Option-1 and we needed to choose Option-2.
Hence to select "Apply update for sdcard" we pressed 'Vol(-)'ONCE and then to Confirm and execute that option Tapped 'POWER' button TWICE.
Hope this Guide helped you or ...will Help you to help others !!!
One quick question...
What if my device detected in fastboot but not in adb devices?
How to enter recovery or solve my softbricked issue?
RmatriX1218 said:
One quick question...
What if my device detected in fastboot but not in adb devices?
How to enter recovery or solve my softbricked issue?
Click to expand...
Click to collapse
bro if your volume + key is not working so how can u say that your device is soft bricked...
i think you should repair your volume keys and than try to move to recovery...
& one more thing without installing all drivers/thing u will not be able to access fastboot mode.....
Hey!!
Please please help me!!
I have MICROMAX a54 ninja 3.5.my mobile stuck in bootloop and soft bricked!!
When I turn on my devices it stuck in logo ninja 3.5.
I also try to go in recovery mode by pressing volume up+home key+lock key!
But it doesn't enter in recovery mod!!
Now what am I do??
Please please help me.
Thank you in advance..
I think for going in recovery:-
1. Press and hold power button.
2. While holding power key, press and hold both volume keys, (vol+ & vol-)
3. When mmx logo comes it will display a message vol(+) for recovery and vol(-) for fast boot then again press vol(+) for once,
And now your in recovery
I lost my recovery.
And I can't go into recovery mod!!
Please help me
Sent from my YU5010 using XDA Free mobile app
What do u mean by, lost your recovery???
I am not able to go to recovery!!
When I m try to gobto recovery mod it doesn't happen only logo ninja 3.5 is there
Sent from my YU5010 using XDA Free mobile app
Ok ok just try flashing your official rom
---------- Post added at 10:35 AM ---------- Previous post was at 10:17 AM ----------
Aakash mehta said:
I am not able to go to recovery!!
When I m try to gobto recovery mod it doesn't happen only logo ninja 3.5 is there
Sent from my YU5010 using XDA Free mobile app
Click to expand...
Click to collapse
Just download your official rom, Your device driver for pc, and install the rom to your device using "sp flash tool"
Please give me steps and link of above method!!!
Thank you for help me
Sent from my YU5010 using XDA Free mobile app
Aakash mehta said:
Please give me steps and link of above method!!!
Thank you for help me
Sent from my YU5010 using XDA Free mobile app
Click to expand...
Click to collapse
1.First download your stock recovery for your mmx a54 from here http://d-h.st/D7G
2. Now download sp flash tool from here https://drive.google.com/file/d/0B9S_ERLSMngHVE9Qc25ObGU1UU0/edit?pli=1 install it to your pc.
3. Download drivers for a54 from here singledrivers.blogspot.in/2013/12/micromax-ninja-a54-usb-driver-for.html?m=1 install the driver to your pc.
4. Download your phone stock rom from here http://d-h.st/fg2 place it in your external sd card(mmc) of your device.
5. Download scatter file from here www.mediafire.com/view/rvz1c5tiifx7yck/MT6575_Android_scatter.txt
6. Now run sp flash tool in your pc, browse to the scatter file.txt, turn off your phone remove the battery and connect it through usb to your pc. (Connect the device without battery)
7. Now select the recovery tab in sp flash tool browse to the recovery.img file (Which we hv downloaded before). Now select the option download in sp flash tool it will Start flashing your stock recovery to the device, A green tick marked will be comes as the flashing complete, now remove your device from pc.
8. Now goto recovery by vol key combination.
9. Now select apply update from sd card and select the stock rom.zip file
10. When flashing done then, Wipe Cache Partition and factory data reset of your device.
Now just select reboot device now it will take around 10min to boot for the first time so wait. Hope this helps you
Thank you for giving me whole information!!
Sent from my YU5010 using XDA Free mobile app
Aakash mehta said:
Thank you for giving me whole information!!
Sent from my YU5010 using XDA Free mobile app
Click to expand...
Click to collapse
Don't say thanks my Buddy just press thanks button.
Hello
I tried sp tool flasher!!
I followed all steps which were given by you!!
BT although not any change in my mobile..
When I tick recovery and then browse recovery.img file and click download button but nothing had happened..
It didn't detect my mobile and didn't go for procedure!!
So now what am I do???
You helped me very much!!
Bu please further help me...
Sent from my YU5010 using XDA Free mobile app
Hv u installed driver properly, just trust me try different usb ports
Yeah i installed drivers properly!!!
Sent from my YU5010 using XDA Free mobile app
So your device is not recognizing by sp flash tool r8
I think so
Sent from my YU5010 using XDA Free mobile app
micromax a210
I have a problem with fastboot stuck on system erasing on adb fastboot mood also userdata and cache only flash recovery and boot img sp flash not working with this phone I do other mtk android with sp tool successfully what I do
What if the device is recongised in adb as : (device name) recovery, but can't actually boot into recovery (twrp) and thus when entering the command : adb reboot fastboot it can never actually boot into fastboot ?
Are there any adb commands that can do the trick or is it game over ?
[RECOVERIES & ROOT] Yureka custom recoveries & Root without Changing Stock Recovery
Note : This tutorial is for YU Yureka based on CM11 (KK 4.4.4) 32bit architecture
and
do it on your own risk, I will not be responsible if you brick your phone
Here is the detailed guide and collection of stock and all custom recoveries for YU Yureka and detailed guide to Root YU Yureka without changing Stock Recovery
Requirements
1. YU Yureka (obviously) with USB Data cable
2. PC / Laptop (Having Windows installed at least Windows 7 or above)
3. Drivers (Windows Automatically detect and install the required drivers)
4. ADB & Fastboot binary package that can be downloaded from XDA 15 seconds ADB Installer v1.4.2']http://forum.xda-developers.com/showthread.php?t=2588979
5. Custom Recovery (Anyone in which you are interested CWM, PhiZ, TWRP)
6. Latest SuperSU.zip file to root your phone
Warning: This process may delete all data stored in internal storage so better backup all the files stored in internal storage.
Step One
Enable USB Debugging on your device you can just follow these steps:
Go to Settings> About phone and keep taping on build number at least 7 times or till it appears "You are a developer now",
Now again go to settings>developer option (only after the previous step it will be enabled)> check/select USB debugging.
Step Two
Unlock your bootloader to flash custom recovery and root.
Here is the process
1. Download the adb & fastboot binary package and install it.
2. Put your phone into FASTBOOT mode by following anyone from below methods :
Method 1 (easiest)
-------------------
a. Power down phone
b. Plug USB cable to your PC
c. Press and hold Vol Up button and plug other end of USB to your device, soon you will see the fastboot screen.
(or without plugging USB Cable, Press and Hold Power and Vol Up buttons simultaneously, until you see the screen
"FASTBOOT MODE"
Method 2
---------
a. While your phone is Power On, plug USB Data Cable with PC and Phone (USB Debuging must be Enable)
b. Open Command Prompt on your PC (with Administartor rights) and type the following command
adb -s 0x1ebf devices
You will get results something like that :
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
3a289c2 device
*Note : If you get "authorization message" then look on your mobile screen and authorize your PC and run the command again.
c. Now note down the device no. (for e.g. in above "3a289c2") and type the following command
adb -s 3a289c2 reboot bootloader
[*Note replace the device id with your id (here 3a289c2), that you got in last command]
Now your phone must be booted into fastboot mode. A screen with "Fastboot Mode" should be appear on your phone.
3. Device drivers will get installed by windows (please wait for the driver installation to complete)
4. After driver installation is done go to the folder where you have extracted the package
5. Now open elevated DOS command prompt (terminal) on your PC and go into the same folder where you saved the recovery file
(*Note : to start command prompt directly from desired folder, while holding the Shift Key Right Click on folder and select start "open command window here")
6. Type the following command to check if the device was detected in fastboot mode
fastboot -i 0x1ebf devices
you should get output like : 2a25d00 fastboot
if you don't get similar output it means that the drivers weren't correctly installed or the device wasn't connected properly
7. If the output is similar to above then run the following command:
fastboot -i 0x1ebf oem unlock
you should get output something like :
.....
OKAY [ 0.003s]
finished. total time: 0.004s
8. Now your bootloader is now unlocked.
*Note : if you want to re-lock your bootloader again (for warranty on any other reason), again boot into fastboot mode and this time type the following command and enter
fastboot -i 0x1ebf oem lock
Step Three
Boot your phone into recovery (temporarily or permanently) and root your phone
1. Download SuperSU.zip and put it on root of your internal or external SD card
2. To load custom recovery (CWM / TWRP / PhiZ) temporarily, now type this command in terminal :
fastboot -i 0x1ebf boot CWM_6.0.5.1_recovery-yu.img
*Note 1 : if you want to flash the custom recovery permanently then us the following command
fastboot -i 0x1ebf flash CWM_6.0.5.1_recovery-yu.img
*Note 2 : if your download custom recovery is named differently (here CWM_6.0.5.1_recovery-yu.img) then while writing the above commands you need to put the name of the recovery same as as your saved file name (anyone CWM / Phiz / TWRP)
3. Done ! You loaded custom recovery temporarily, if command used with "boot" hence to root your phone, proceed to next section (step 5).
or
If you flashed recovery permanently, using command with "flash" then boot your phone into recovery. To do so, you have Two options
i) type the following command and press enter : adb -s 3a289c2 reboot recovery
or
ii) power off your phone, after then press and hold "Vol up+ Vol down + Power" buttons simultaneously to boot into custom recovery.
Now to root your phone proceed with next section (step 5).
Root your phone
5. To gain root access, flash SuperSu.zip that is stored on your internal or external SD card (in step 1)
6. Choose reboot phone and enjoy rooted phone with stock or custom recovery !
Special Note 1
I didn't tested, but came to know that root doesn't effect OTA update on Yureka.
You can get OTA updates with root but after the OTA update is flashed you will loose root access. To keep it or to avoid this please go to System Settings -> Developer Options -> UNTICK -"Update CM Recovery" (update recovery while installing system updates)
Even though if someone want to go back to Stock recovery, then download the official stock recovery (link no. 6 above) and flash it using command in fastboot mode (second command in step 2 under head "STEP THREE")
Downloads
1. 15 seconds ADB Installer v1.4.2 http://forum.xda-developers.com/showthread.php?t=2588979
2. Super SU latest v2.46 http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. CWM 6.0.5.1 https://s.basketbuild.com/devs/vishal_android_freak/yu/yureka
OR http://d-h.st/ElAe
4. PhilZTouch 6.59 based on CWM v6.0.5.1 http://www.androiddevs.net/downloads/
OR http://d-h.st/UqWK
5. TWRP 2.8.5.0 http://techerrata.com/browse/twrp2/tomato
OR https://www.androidfilehost.com/?fid=95916177934528156
OR http://d-h.st/5wDD
6. YU Yureka Official Stock Recovery http://d-h.st/tQ1k
Special Note 2
Without the vendor id, phone will not get detected in fastboot mode.
Like if you want to check fastboot type this :
fastboot -i 0x1ebf devices
therefore, always add "i -0x1ebf" after fastboot and then write your command
aabidhashmi said:
Here is is collection of all custom recoveries for YU Yureka and detailed guide to Root YU Yureka without changing Stock Recovery
Requirements
1. YU Yureka (obviously) with USB Data cable
2. PC / Laptop (Having Windows installed at least Windows 7 or above)
3. Drivers (Windows Automatically detect and install the required drivers)
4. ADB & Fastboot binary package that can be downloaded from XDA 15 seconds ADB Installer v1.4.2']http://forum.xda-developers.com/showthread.php?t=2588979
5. Custom Recovery (Anyone in which you are interested CWM, PhiZ, TWRP)
6. Latest SuperSU.zip file to root your phone
Warning: This process may delete all data stored in internal storage so better backup all the files stored in internal storage.
Step One
Enable USB Debugging on your device you can just follow these steps:
Go to Settings> About phone and keep taping on build number at least 7 times or till it appears "You are a developer now",
Now again go to settings>developer option (only after the previous step it will be enabled)> check/select USB debugging.
Step Two
Unlock your bootloader to flash custom recovery and root.
Here is the process
1. Download the adb & fastboot binary package and install it.
2. Power down phone
3. Plug USB cable to your PC
4. Press and hold Vol Up button and plug other end of USB to your device, soon you will see the fastboot screen.
(or without plugging USB Cable, Press and Hold Power and Vol Up buttons simultaneously, until you see the screen
"FASTBOOT MODE"
5. Device drivers will get installed by windows (please wait for the driver installation to complete)
6. After driver installation is done go to the folder where you have extracted the package
7. Now open elevated DOS command prompt (terminal) on your PC and go into the same folder where you saved the recovery file
* to start command prompt directly from desired folder, while holding the Shift Key Right Click on folder and select start "open command window here"
8. Type the following command to check if the device was detected in fastboot mode
fastboot -i 0x1ebf devices
you should get output like : 2a25d00 fastboot
if you don't get similar output it means that the drivers weren't correctly installed or the device wasn't connected properly
9. If the output is similar to above then run the following command:
fastboot -i 0x1ebf oem unlock
you should get output something like :
.....
OKAY [ 0.003s]
finished. total time: 0.004s
10. Now your bootloader is now unlocked.
Step Three
Root your phone without changing your stock recovery
1. Download SuperSU.zip and put it on root of your internal or external SD card
2. To load custom recovery (CWM / TWRP / PhiZ) temporarily, now type this command in terminal :
fastboot -i 0x1ebf boot recovery CWM_6.0.5.1_recovery-yu.img
*Note : if your download custom recovery is named differently (here CWM_6.0.5.1_recovery-yu.img) then while writing the above command you need to put the name of the recovery same as as your saved file name (anyone CWM / Phiz / TWRP)
Done ! You flashed custom recovery temporarily.
3. Now press and hold "Vol up+ Vol down + Power" buttons simultaneously to boot into custom recovery.
4. To gain root access flash SuperSu.zip that is stored on your internal or external SD card (in step 1)
5. Choose reboot phone and enjoy rooted phone without changing stock recovery !
Downloads
1. 15 seconds ADB Installer v1.4.2 http://forum.xda-developers.com/showthread.php?t=2588979
2. Super SU latest v2.46 http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. CWM 6.0.5.1 https://s.basketbuild.com/devs/vishal_android_freak/yu/yureka
OR http://d-h.st/ElAe
4. PhilZTouch 6.59 based on CWM v6.0.5.1 http://www.androiddevs.net/downloads/
OR http://d-h.st/UqWK
5. TWRP 2.8.5.0 http://techerrata.com/browse/twrp2/tomato
OR https://www.androidfilehost.com/?fid=95916177934528156
OR http://d-h.st/5wDD
Special Note
Without the vendor id, phone will not get detected in fastboot mode.
Like if you want to check fastboot type this :
fastboot -i 0x1ebf devices
therefore, always add "i -0x1ebf" after fastboot and then write your command
Click to expand...
Click to collapse
Few errors noted:
1. You can't say flashing recovery when you are booting it.
2. In step 3 point 3 is not valid because when your command is to boot it will automatically boot into recovery you need not use combination keys.
3. Last point vender id is wrong !!!
Few suggestions:
1. It feels like you have not tested this by yourself
2. There is already a guide for "rooting without flashing recovery". Search before posting.
Regards
aashking
aashking said:
Few errors noted:
1. You can't say flashing recovery when you are booting it.
2. In step 3 point 3 is not valid because when your command is to boot it will automatically boot into recovery you need not use combination keys.
3. Last point vender id is wrong !!!
Few suggestions:
1. It feels like you have not tested this by yourself
2. There is already a guide for "rooting without flashing recovery". Search before posting.
Regards
aashking
Click to expand...
Click to collapse
Dear aaskking
Thanks to inform. Here is the corrections
1 & 2 - Tutorial updated with "boot" and "flash" commands separately.
3 + Vendor ID is correct nothing wrong in it.
4 - I already tested all those procedures and commands. I never post anything without testing.
5 - Yes, I also seen that available guide, but that is not so much detailed and also required files links are not provided.
Anyway, thanks for your suggestions.
aabidhashmi said:
Dear aaskking
Thanks to inform. Here is the corrections
1 & 2 - Tutorial updated with "boot" and "flash" commands separately.
3 + Vendor ID is correct nothing wrong in it.
4 - I already tested all those procedures and commands. I never post anything without testing.
5 - Yes, I also seen that available guide, but that is not so much detailed and also required files links are not provided.
Anyway, thanks for your suggestions.
Click to expand...
Click to collapse
EDIT : You can get OTA updates with root..
After the update is flashed you will loose root access ..
To keep it or to avoid this please write the following step
STEP) In Developer Option UNTICK -"Update CM Recovery".
That's it.. Cheers mate wonderful thread.. @aabidhashmi @aashking
arjunsingh1000 said:
EDIT : You can get OTA updates with root..
After the update is flashed you will loose root access ..
To keep it or to avoid this please write the following step
STEP) In Developer Option UNTICK -"Update CM Recovery".
That's it.. Cheers mate wonderful thread.. @aabidhashmi @aashking
Click to expand...
Click to collapse
Thanks Arjun Singh @arjunsingh1000 for suggestion and appreciation
Post updated ...
aabidhashmi said:
Thanks Arjun Singh @arjunsingh1000 for suggestion and appreciation
Post updated ...
Click to expand...
Click to collapse
Great mate cheers just checked and tried that ota updates are available and work.. On stock recovery... Locked bootloader and with root..
Achieved this by downgrading to the very first cm11 firmware and got then rooted it and locked the bootloader then I just booted it and got the incremental update .. Downloaded and flashed .. Works perfectly.. Root not lost due to the untick in dev options..
Thanks again Arjun Singh, for confirming OTA updates are working.
I am already on Stock ROM & recovery {rooted} and tried the same procedure {locked the bootloader}, but no updates for me.
Is updates are really there, or something wrong with me ?
Sent from my AO5510 using Tapatalk
I am simply unable to get the device listed in command prompt after fastboot mode is enabled. my phone has option to boot into fastboot mode in power options. i tried that option, i tried using command to boot into fastboot. But somehow, when phone is in fastboot mode, it does not get detected by fastboot application (even though windows installs drivers successfully).
I have tried 3 different laptops. All had same problem. No idea how to solve this.
aabidhashmi said:
Thanks again Arjun Singh, for confirming OTA updates are working.
I am already on Stock ROM & recovery {rooted} and tried the same procedure {locked the bootloader}, but no updates for me.
Is updates are really there, or something wrong with me ?
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
Well I guess you are on the latest build XN0PHQ I guess? Another beta update was made but not rolled out it is um XNPH08P I know its a little late but just in case you don't know..
---------- Post added at 05:30 PM ---------- Previous post was at 05:28 PM ----------
jitendragarg said:
I am simply unable to get the device listed in command prompt after fastboot mode is enabled. my phone has option to boot into fastboot mode in power options. i tried that option, i tried using command to boot into fastboot. But somehow, when phone is in fastboot mode, it does not get detected by fastboot application (even though windows installs drivers successfully).
I have tried 3 different laptops. All had same problem. No idea how to solve this.
Click to expand...
Click to collapse
Ahahahaah... I know just the way... Do not reboot via adb ...
Switch off your phone remove your battery and put it back in do not turn it on.. But connect your USB cable and at the same time hold the power up or maybe down button .. Voila your in fastboot which will get detected .. Don't forget to use the vendor id.
arjunsingh1000 said:
Ahahahaah... I know just the way... Do not reboot via adb ...
Switch off your phone remove your battery and put it back in do not turn it on.. But connect your USB cable and at the same time hold the power up or maybe down button .. Voila your in fastboot which will get detected .. Don't forget to use the vendor id.
Click to expand...
Click to collapse
I tried this method but phone does not get detected in fastboot mode at all. I have drivers installed for all different modes I connect my phone as. No luck at all.
Also, weird thing is, I have an option to directly go to fastboot mode from the power menu.
Jitendra Garg
Your driver's are not installed
As there is no special drivers setup, so connect your PC with Internet then plug your phone and let Windows install drivers automatically.
Sent from my AO5510 using Tapatalk
Firstly this is my first helpful post so be gentle.
How to root the Redmi 4x
First off I am not accountable if your fry your device or shut down the power grid etc.
Alright. It took me some research and trial and error but I found the CORRECT way to root the Redmi 4x.
Needed files:
Lasted version of the magisk zip. DO NOT USE ANY VERSION OF SUPER SU. IT CAUSES BOOTLOOP.
TWRP for Redmi 4x
Lazy patcher.
Adb and fastboot files.
Step one:
Ensure your bootloader is unlocked. If not search XDA for a thread there are multiple threads showing you how to do it. Once that's done let's move on.
Step 2:
Alright let's get going with flashing TWRP first.
You need to enable developer options and enable USB debugging on your Redmi. To do that go to settings>about devices>scroll down>continually tap on MIUI version and a toast notification will tell you that you are now a developer>go to developer option under the more options tab and enable USB debugging.
Step 3:
Now that we've got USB debugging we can connect to Adb. Firstly download all aforementioned files and place them in the same folder as your Adb installation for ease of access. Now open up a command prompt in that folder by either typing "cmd" into the address bar or shift+right click and select open command window here. Now you need to connect your phone via USB to your computer and ensure it is connected by entering "adb devices" into the command window.
Step 4: commands
Here are the commands you will need to enter. I recommend making a backup of everything first.
Enter these commands
adb reboot bootloader
Fastboot flash recovery (put TWRPS full file name here including the .zip)
Wait for it to finish.
Now DO NOT BOOT TO SYSTEM.
Enter in fastboot reboot and hold volume up to enter recovery. If you boot to system it will remove twrp and you will have to reflash it.
Once in Twrp check the box to allow modifications and slide right.
Go to advanced and the ADB sideboard.
Now flashing magisk and lazy patcher.
Reconnect your phone to the computer and leave Twrp on sideload mode.
Enter this command
adb sideload (lazy patchers full file name here)
Now I made sure my phone still booted to system after this because every time I flashed SuperSU it would boot loop.
Once your back in sideload mode let's flash magisk.
adb sideload (magisks full file name here).
Once it's done select reboot to system from Twrp and enjoy your root!!
Again I say do not use any flashable root other than magisk. I don't know if I had a specific problem but every single one I tried resulted in bootloop.
Hey guys. Just upgraded to the android 10 October image via the adb flash-all command. Magisk rooted via adb and everything is going great. Want to install Sultan's ported kernel for Android 10. Used adb to flash twrp image and flashed the kernel zip via twrp but it keeps saying it can't mount /system and /vendor upon finishing. Upon rebooting I get stuck at the google G load screen. Have to redo flash-all and instal magisk via adb all over to get back to normal. Anyone have this problem or could offer some help? Would be great.
Bverns88 said:
Hey guys. Just upgraded to the android 10 October image via the adb flash-all command. Magisk rooted via adb and everything is going great. Want to install Sultan's ported kernel for Android 10. Used adb to flash twrp image and flashed the kernel zip via twrp but it keeps saying it can't mount /system and /vendor upon finishing. Upon rebooting I get stuck at the google G load screen. Have to redo flash-all and instal magisk via adb all over to get back to normal. Anyone have this problem or could offer some help? Would be great.
Click to expand...
Click to collapse
As long as the kernel finishes the install it's fine. The mounting errors don't matter if it finishes. The mounting errors are just a bug with Android 10. Everything I flash has those errors after it, but I am good. I am on Oct. with Magisk 20 and Sultan kernel.
Ericarthurc said:
As long as the kernel finishes the install it's fine. The mounting errors don't matter if it finishes. The mounting errors are just a bug with Android 10. Everything I flash has those errors after it, but I am good. I am on Oct. with Magisk 20 and Sultan kernel.
Click to expand...
Click to collapse
So the way I'm seeing it is flash the twrp image file, flash the kernel, reboot. Then adb fastboot to bootloader and reflash patched magisk boot.img?
Bverns88 said:
So the way I'm seeing it is flash the twrp image file, flash the kernel, reboot. Then adb fastboot to bootloader and reflash patched magisk boot.img?
Click to expand...
Click to collapse
Do this:
Setup:
1. Download latest platform tools for your OS
2. Download latest factory image for Pixel 2 XL
3. Download twrp.img and twrp.zip
4. Download the kernel.zip you want
5. Download magisk.zip version 20
(Keep in mind those aren't the actual filenames, I am just shortening them; plus you will want to rename them for easier flashing)
Install:
1. Boot phone to bootloader.
2. Extract factory image into the platform tools folder
3. Run flash-all script
4. After done reboot back to bootloader (dont do the phone setup)
5. Now remove the factory image from platform tools (or just extract a clean platform tools folder)
6. Place twrp.img, twrp.zip, kernel.zip and magisk.zip into the platform tools folder (rename the files to make it easier to type them out when flashing with computer adb)
7. Run: fastboot boot twrp.img (or whatever you named it)
8. When in twrp, go to settings and turn off "screen timeout" there is a bug
9. Go to advanced then "adb sideload"
10. In your computer terminal type: adb sideload twrp.zip
11. Then run: adb sideload kernel.zip
12. Then run: adb sideload magisk.zip
13. Reboot to system
Should be good! Using sideload allows you to pass files from your computer to your phone, it makes it easy. If adb sideload is "hanging" or "freezing" (you should see a kinda progress bar with it's working) then reboot twrp.img and try a different USB port. There is a glitch when it hangs, where when you remove the USB cable the phone goes black; just hold power + volume down for about 10 seconds and it will boot back to bootloader.
Ericarthurc said:
Do this:
Setup:
1. Download latest platform tools for your OS
2. Download latest factory image for Pixel 2 XL
3. Download twrp.img and twrp.zip
4. Download the kernel.zip you want
5. Download magisk.zip version 20
(Keep in mind those aren't the actual filenames, I am just shortening them; plus you will want to rename them for easier flashing)
Install:
1. Boot phone to bootloader.
2. Extract factory image into the platform tools folder
3. Run flash-all script
4. After done reboot back to bootloader (dont do the phone setup)
5. Now remove the factory image from platform tools (or just extract a clean platform tools folder)
6. Place twrp.img, twrp.zip, kernel.zip and magisk.zip into the platform tools folder (rename the files to make it easier to type them out when flashing with computer adb)
7. Run: fastboot boot twrp.img (or whatever you named it)
8. When in twrp, go to settings and turn off "screen timeout" there is a bug
9. Go to advanced then "adb sideload"
10. In your computer terminal type: adb sideload twrp.zip
11. Then run: adb sideload kernel.zip
12. Then run: adb sideload magisk.zip
13. Reboot to system
Should be good! Using sideload allows you to pass files from your computer to your phone, it makes it easy. If adb sideload is "hanging" or "freezing" (you should see a kinda progress bar with it's working) then reboot twrp.img and try a different USB port. There is a glitch when it hangs, where when you remove the USB cable the phone goes black; just hold power + volume down for about 10 seconds and it will boot back to bootloader.
Click to expand...
Click to collapse
Thanks so much. I went and used AZ bikers method and it worked fine. Easy and hassle free. https://forum.xda-developers.com/pixel-2-xl/how-to/quick-2xl-upgrade-reference-8x-oreo-to-t3826330