Database Develop

Failed Root - Boot Loop

Hello everyone, about five hours ago I was going through the process of rooting my Moto X 2014 Pure (UK). Unfortunately it seems to be stuck in a boot loop. I've crawled through forums but to no avail. Now it's 6:00am and I'm having a slight mental breakdown and would really appreciate some help.
notes:
-The phone stays stuck on the watery 'M' logo that appears after the boot animation.
-Unlocking the bootloader went fine
-had trouble installing the android SDK since I ran out of space on my hard-drive, however the installation log notes that the necessary files were successfully downloaded after I made some space.
-I'm not running TWRP or any equivalent. The only thing I can access is the standard fastboot screen thing.
-I think made two errors with my first attempt at rooting: I forgot to type 'boot' after fastboot and I also hadn't uncompressed the zip folder that the img was contained in (it was CF Root incidentally). The command terminal came back with information alluding to it having done something but the device didn't reboot, so i'm unsure if it did.
-I tried to rectify this by installing different root imgs but the phone still won't boot.
I'm really unsure as to what to do. My guess is that I need to sideload a factory img of some sort. I've sent of for the official img from the Motorola website and am anxiously awaiting a reply but I wondered if anyone knew of any alternatives? All this hassle just so I could run some xposed modules :crying:

SexyEgg said:
Hello everyone, about five hours ago I was going through the process of rooting my Moto X 2014 Pure (UK). Unfortunately it seems to be stuck in a boot loop. I've crawled through forums but to no avail. Now it's 6:00am and I'm having a slight mental breakdown and would really appreciate some help.
notes:
-The phone stays stuck on the watery 'M' logo that appears after the boot animation.
-Unlocking the bootloader went fine
-had trouble installing the android SDK since I ran out of space on my hard-drive, however the installation log notes that the necessary files were successfully downloaded after I made some space.
-I'm not running TWRP or any equivalent. The only thing I can access is the standard fastboot screen thing.
-I think made two errors with my first attempt at rooting: I forgot to type 'boot' after fastboot and I also hadn't uncompressed the zip folder that the img was contained in (it was CF Root incidentally). The command terminal came back with information alluding to it having done something but the device didn't reboot, so i'm unsure if it did.
-I tried to rectify this by installing different root imgs but the phone still won't boot.
I'm really unsure as to what to do. My guess is that I need to sideload a factory img of some sort. I've sent of for the official img from the Motorola website and am anxiously awaiting a reply but I wondered if anyone knew of any alternatives? All this hassle just so I could run some xposed modules :crying:
Click to expand...
Click to collapse
First thing I guess is installing a custom recovery. I recommend TWRP. Try this link to get the zip http://www64.zippyshare.com/v/HPPiFhly/file.html
Unzip the file on your pc.
Take the device to fastboot screen and plug it on pc.
Open the Instalador.bat file and click Enter until it's fully installed.
Then, get back to the fastboot screen and try to open the recovery.
---------- Post added at 01:36 PM ---------- Previous post was at 01:36 PM ----------
Let me know it that works for you.

So I've solved the problem but just figured I'd share the solution; basically don't use the terminal just run the bat file (assuming the img has one). Having rooted all my previous phones I hastily emulated the same process neglecting to notice the extremely convenient bat file included in the folder. Never could get TWRP to flash though. Although I could boot into it using: fastboot boot 'recovery'.img A little tedious but certainly functional. Once I had a working phone again I flashed TWRP using the Flashify App which I was a bit dubious about but it seems to have worked absolutely fine.
So yeah, silly oversight really but at least my phone turns on now; so that's nice. Cheers for the help though fhreire, although I couldn't get that recovery you linked to to work the fact it installed via a bat file is what lead me to find the solution I needed.

Help needed! Cannot boot into either Flash mode or Fastboot mode

Hi all,
A few years ago (well when the devices has pretty much just come out), I ran a mod which i found on the XDA website that allowed me to root my partners Xperia T (LT30P),
Everything has been fine until recently, where I've wanted to upgrade the ROM on the phone, but this is where i'm having some major problems.!
Essentially I cant get the phone to boot into either Flash mode (green LED) or Fastboot mode (Blue LED). I've tried the volume down and then connecting the USB cable to my PC (on which the correct drivers are installed via Flashtool). and also the volume up for Fastboot. Neither work. Unsure if the phone has an unlocked bootloader or if that matters (im a Samsung man and used to working with that, so all the Xperia modding is totally new to me... :/
So far ive tried the following:
-Volume down key and plugging into USB port - Result: Phone remains switched off.
-Volume up key pressed in and then plugging into USB port. - Result: Phone remains switched off
-Enabled USB debugging and attempted to boot the phone into flash mode via ADB (Flashtool option). Phone simply reboots.
-Attempted inbuilt software update - Update downloads, but fails at 25% approx when it reboots and attempts the install.
-PC companion equally unsuccessful on my PC, as cant enable flash mode.
I'm totally at a loss at how to flash a fresh complete build (using a ftf file) to the phone without access to flash mode or fastboot mode. Anyone got any idea or know of any tools that might allow me to to completely rebuild the phone so all partitions are present and correct?
One idea i had was to flash a recovery to the phone using FlashR or alike, but cant seem to get it to work either. Flashr looks to install the twrp recovery, but when i attempt to reboot into recovery via Flashr or Rom Manager (another tool i use but not sure if useable on xperia phones?), the phone simply reboots. SOunds like a damaged or wiped partition perhaps?
Anyhoo , any ideas would be welcome guys! Too good a phone to just leave in the drawer
Cheers
Craig.

Cant you flash a boot.img (maybe from cm11 or something) with inbuilt recovery? You can use this for flashing

Ok, I've started writing this reply and lost everything near the end, started freaking out, calmed down and decided to do it again, cause I know what it's like to have a phone that's not behaving as it should. So here goes the shorter-ish version cause I really can't type everything again...
Make sure your volume buttons are working at all (I mean when the phone is booted). They work? good, procced. They don't? we can bypass that, but you, should get them fixed.
Got to this thread and download the latest build of the ROM http://forum.xda-developers.com/xperia-t-v/orig-development/rom-cyanogenmod-12-neo-s-homebuilds-t2984988
Extract the boot.img file from the zip and copy it to the root of your external micro sdcard, NOT IN A FOLDER. If you don't have an sdcard, put in on the internal storage, again, not in a folder.
Root your phone if you haven't. There are plenty of threads on that here on xda
Download an app called Terminal Emulator from the Play Store
Open the app and type su into the prompt.
Grant the app superuser/root access
The following step is the dangerous one where you can seriously break your phone forever. I'm not responsible for anything you mess up. You alone chose to do this
Run the following command in the terminal (be sure that the $ at the end of the line changed to a # (That means you're in root shell, but it's not important))
If you don't have an external sdcard type sdcard0 instead of sdcard1
Code:
dd if=/storage/sdcard1/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/Kernel
Connect the phone to a PC with fastboot drivers installed
Next execute this command and your phone should now boot into fastboot
Code:
reboot bootloader
If a blue LED lights up, you can happily continue flashing kernels and ROMs, if not report back and I'll see if I can help you

Cheers gents. Going to give this a shot tonight. I read last night that some builds out there where you cannot unlock the bootloader (which you can check via service menu)? Is that now bypassable?

crstephenson said:
Cheers gents. Going to give this a shot tonight. I read last night that some builds out there where you cannot unlock the bootloader (which you can check via service menu)? Is that now bypassable?
Click to expand...
Click to collapse
No and it probably never will be. It's hardcoded on the chip. If your phone is bought with a contract binding or it's limited to a single provider, then chances are that you will never be able to unlock the bootloader and flash kernels. It could be that you not being able to get into fastboot is because it's restricted on the device itself [citation needed]. In that case you're screwed and can pretty much forget the whole custom kernel thing. Only ROMs for locked bootloaders

[GUIDE][HOW-TO] Fully root Huawei Ascend P7 L10 B133SP01 EMUI2.3

After years fo relying on the XDA community, I thought I'd give something back. I've been for a few days now trying to get the phone properly rooted, however being a bit cautious due to completely screwing up my last phone, was being very careful.
Obviously - This guide carries all the T&Cs you'd expect... will void your warranty, could brick your phone, could fry all electronic devices within a 50 meter radius and such... USE AT YOUR OWN RISK.
Also, credit goes to the people for their hard work in making this possible. I'm only responsible for writing this post.
I'm not sure if you could have gotten away with not doing any of the steps below, but it's this sequence that I followed.. so feel free to play about.
To start off, you need the following
Ingredients
HiSuite software. I used what came with the device. If you put it in HiSuite mode, you should get a folder mounted that contains this software.
USB developer mode needs to be enabled (follow HiSuite's guide as even IT needs debugging mode enabled).
ADB - I used the latest version of Minimal ADB and Fastboot
Download TWRP from here
P7 Easy Update and Adjust from here
King Root from here (I've tried the lot and is the only one I found that actually worked).
Super SU from here. Put it on your phone storage for later.
Preparation
Install ADB, HiSuite and King Root.
Connect the phone to the pc via the USB, turning on PC Suite (HiSuite) mode and USB Debugging enabled. HiSuite should automatically load.. close it
Run King Root and start the rooting process. This should cause your phone to reboot a few times. now, following the application - towards the end of the process it says something about installing a recovery, but (at least on mine) didn't seem to install correctly. Never mind though - phone will still boot as normal, and we'll take care of the recovery next
place the Easy update and adjust excecutable in the folder where you installed ADB and run it (make sure phone is in pc Suite mode with USB debugging again and close the HiSuite app if it pops up on your PC). Note that in the ADB folder you will find a new /recovery/ folder, as well as a stock recovery image. Place the TWRP recovery image we downloaded earlier in this folder as well.
From within the Easy update, select [3] - Delete set_immutable.list / Full root.
After that Select [2] - Flash Recovery (Stock or custom)
Select the TWRP recovery. This will reboot your phone and flash the recovery image, loading back up as normal.
Go back to the Easy update app and select to reboot into recovery. If you attempted this before the last step (7), you'd just see two boot cycles, back into the normal boot up.
flash the Super SU zip and reboot
the next time you boot up, you will get a notification that king user needs something... you need to disable (or uninstall via titanium backup).
And that's it! You have root!

Hi there, just out of curiosity, do you think this method will work for b135?

Cryonisis said:
Hi there, just out of curiosity, do you think this method will work for b135?
Click to expand...
Click to collapse
Everything bar the set_immutable part worked for me.. for that i followed the below:
http://forum.xda-developers.com/ascend-p7/general/rooted-p7-l10-609-t3003605
hope that helped

Wrong thread guys soz.

TWRP recovery version?
Hi,
Will I have to download TWRP version compatible with EMUI 3.1 (which is mine case) or I can use TWRP 2.8.1.0 link that is in your post?
Thank you in advance!

TELUS Moto X (XT1097) doesn't boot after last OTA. Help!

Hey guys,
I have rooted my Moto X 2014 (XT1097) with Chainfire auto root method about 6 months ago and I decided to accept the OTA update I got today from TELUS (22.121.11.en.CA). If I remember correctly I was on 5.0.1 before accepting this OTA.
Now the phone is stuck in the custom boot logo screen that I installed after rooting and even if I try to shut it down, it just boots up and gets stuck in the logo screen.
What should I do? I can access the bootup screen by holding power and volume down.

bobitza said:
What should I do?
Click to expand...
Click to collapse
Let me reply myself so that maybe others can use this info to fix their devices as well.
Step 1: You need to install the ADB platform tools (should be plenty of threads about that)
Step 2: You need to find a system.img and a boot.img to match your needs. I have a XT1097 with TELUS in Canada, so I have found this thread and downloaded the big .zip file (big thanks to Steve-x!). For US people the graffixnyc site has images for XT1095 that you can use. Move those .img files where your fastboot.exe file is found
Step 3: Boot your device in bootloader mode (hold power and volume down) and connect it to your PC
Step 4: Install the images with the fastboot command by typing this in a cmd window
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
Or in the case of the TELUS image, the system image is split into 7 files ... just flash system them one after the other. Steve mentioned something about the recovery.img, but wasn't sure how to flash that so I did it this way.
Step 5: (Optional) If you had something else installed you will get some errors, here's how to fix them. Boot back in the bootloader and choose Recovery, then when you see the screen with the "sick" Android, keep Power pressed and tap on Vol Up to enter Recovery Menu. Choose to delete data and delete cache. Reboot.
If you used Steve's image you should be booting into TELUS Android 5.0.1, just before the cursed update. You can even do now the 5.0.1+ update OTA. You're back in stock ROMs world

Glad you got it fired up again. I haven't taken the OTA yet myself with my Moto X's, was hoping to get the entire image with Motorola Device Manager.

Le sigh
Man i'm having nothing but issues. I've done everything that i was supposed to do, but i cant get the files to load.

How to unlock BOOTLOADER and Install any zip file on your LG NEXUS 5 D820 using CWM

************
First, I am not responsible if you damage your phone in any way.
Also you might back up your phone's data completely because after unlocking bootloader you can lose all your installed data.
*************
So, first step is unlock the bootloader. First go into
Setiing> About Phone > Press Build Number A couple of time until it shows you are a developer now > go back > Developer Options > Turn on USB debugging.
After that, go to your bootloader, by powering off your phone and once it is powered off press the Volume down key + Power button until something appears with a vibration.
Now download adb and fastboot from this link:
http://*******/1Zsyme
After downloading it, install it. And you can install it easily with no problem. Just make a folder in your windows drive of :
C:\Android-adb\
And you are good to go.
Now goto that folder (C:\Android-adb\) and press SHIFT+CTRL+RIGHT-CLICK together or just SHIFT+CTRL first and then RIGHT-CLICK and then click "open command window here".
Now connect your nexus 5 and check if your PC makes a sound like when you connect a external device.
If yes, then you are good to go. Else try connecting it several times to automatically make the PC install any drivers.
After this, go to that DOS type window and write:
fastboot devices
(press enter to activate any command)
If you it shows a serial number then you are doing fine.
After this, write this command in that CMD.exe window:
fastboot oem unlock
and wait until something pop-ups in your phone. It might be a warning, read it carefully and using your volume up or down key cycle through the options and using power button select yes. And it might reboot on it's own else restart manually by pressing the power button for 10 or 15 sec until you see your screen with a unlocked lock which means you have successfully unlocked the device.
Now after that, it's finally time to FLASH recovery file.
For this to happen you need to download CWM latest version from here:
http://*******/1Zt1Fs
It's latest for HAMMERHEAD or NEXUS 5!!!!
Now, again go to the bootloader as described in the beginning.
Now you can also copy the recovery zip file by your data cable of your phone by turning in on normally and also from bootloader.
How to do it from bootloader? Here's how too.
Now you have to be on the bootloader screen. Now goto the same CMD.exe and write:
adb push filename.zip /storage/emulated/0/
adb push filename.img /storage/emulated/0/
If you get any error ask me.
Now it might get some time to be moved to that.
(Data Cable should be attached to do so, also the RECOVERY img file should be in C:\Android-adb\ this folder to be moved to PHONE)
Now, you might have successfully moved the zip file to your phone. So now write this command to flash Recovery.img file:
fastboot flash recovery your_recovery_image_name.img
After this, it will FLASH the recovery file. Until it's installed successfully wait till then.
Once it is FLASHED, now cycle to recovery mode using volume buttons from the BOOTLOADER and wait till it gets there:
Now you will see some options, but you need to flash a zip file so cycle again using volume buttons and select anyone using power button. So select:
install zip
Now select choose zip from /sdcard
Now you are in your internal storage's directory where you moved your zip files from CMD.exe. Just select it and you are done. go back and reboot system now. And you are done.
Don't forget to say thanks if you find it helpful in any way.
Also report to me if you get any errors between in it. By the way, I didn't have any errors in my journey to do this in first time.

You should point out and highlight that unlocking the bootloader will wipe all data.
Sent from my Nexus 5 using Tapatalk 2

You do not need USB debugging for fastboot, you do not need to open fastboot or adb within the directory they are install in, you...
There are already guides, which are more accurate and up to date, to direct people through the process. Who uses CWM?

wangdaning said:
You do not need USB debugging for fastboot, you do not need to open fastboot or adb within the directory they are install in, you...
There are already guides, which are more accurate and up to date, to direct people through the process. Who uses CWM?
Click to expand...
Click to collapse
TWRP not worked for me. I use and recommend CWM. TWRP is full of bugs and does not show errors and hangs. But CWM is the best.

ddimple4 said:
You should point out and highlight that unlocking the bootloader will wipe all data.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I did mentioned but didn't highlight.

Except for the fact that CWM is out of date and not maintained for our device.
---------- Post added at 05:53 AM ---------- Previous post was at 05:52 AM ----------
Except CWM is out of date and not maintained for our device. TWRP is not full of bugs.

What is the point of this thread? Isn't this all common knowledge?

Google says you need to hold VOL UP, VOL DOWN, and POWER to boot into fastboot, but I've used just VOL DOWN and POWER on my N5.
fastboot oem unlock has been superseded by fastboot flashing unlock, though it still works for the N5.
You can download the Android ADK CLI tools from https://developer.android.com/sdk/index.html . Always point to the authoritative source.
You'll need to be in the \platform-tools directory UNLESS you add it to the PATH.
So far's I know, ADB will not push a file while you're in fastboot. You can just flash the recovery file from the directory you have it, e.g. fastboot flash recovery .\your_recovery_image.img.
Very nice of you to post, OP, but you've got a few things wrong in your guide. Read some others to find your errors, and keep writing, Android needs informed enthusiasts and writers.

Yeah, it's 2016. Why was this thread even made? It's either common knowledge, or there are a hundred other guides about doing this.
Plus, who the hell uses cwm these days? Twrp or don't waste your time.
This whole post feels like something from 4 years ago.

GldRush98 said:
Yeah, it's 2016. Why was this thread even made? It's either common knowledge, or there are a hundred other guides about doing this.
Plus, who the hell uses cwm these days? Twrp or don't waste your time.
This whole post feels like something from 4 years ago.
Click to expand...
Click to collapse
I'm still using CWM. What's wrong with that?
// Tapatalk on Nexus 4/5 //

ChromeJob said:
I'm still using CWM. What's wrong with that?
// Tapatalk on Nexus 4/5 //
Click to expand...
Click to collapse
Outdated for years.

ChromeJob said:
I'm still using CWM. What's wrong with that?
// Tapatalk on Nexus 4/5 //
Click to expand...
Click to collapse
It's outdated, no updates. Last I heard some of the CWM team are now contributing to TWRP. It's pretty much the official unofficial Android custom recovery at this point. You will also have a lot of issues trying to flash or update on older versions of TWRP or other recoveries that aren't updated due to file structure changes in newer Android versions.

RoyJ said:
It's outdated, no updates. Last I heard some of the CWM team are now contributing to TWRP. It's pretty much the official unofficial Android custom recovery at this point. You will also have a lot of issues trying to flash or update on older versions of TWRP or other recoveries that aren't updated due to file structure changes in newer Android versions.
Click to expand...
Click to collapse
I see the light. CWM team seem to have abandoned Helium, too; no longer works on systemless root. That's second or third app they've simply gotten bored with and not continued development.