Database Info

Rom help and recovery

I'm extremely new to this and this website, sort of. So if any of this is wrong impression already sorry. A few weeks ago I rooted my myTouch_4G_Slide, using s-off. I'm pretty sure that went OK as my phone is still currently rootly rooted. Next I tried using a custom rom, i am not exactly sure what I did wrong but, I cannot boot into recovery and when i go into Hboot I get multiple "no image" popping up. I can't factory reset and when i try to boot into recovery my phone gets stuck at the mt4gs screen and i have to take out the battery. Is there anyway to fix this, easily hopefully.
Sent from my myTouch_4G_Slide using XDA App

You said your phone is s-off and "rootly rooted". I assume you meant "permanently rooted"? Did you use the right version of superuser (2.3.6.3 or above) and clockwork recovery image (4.0.0.9)? You can ignore the "no image" message, I get them all the time and I can still boot into recovery no problem.

I have the right superhero version but i don't think I have the right clockwork. How could I fix it, without having to boot into recovery.
Sent from my myTouch_4G_Slide using XDA App

imjames said:
I'm extremely new to this and this website, sort of. So if any of this is wrong impression already sorry. A few weeks ago I rooted my myTouch_4G_Slide, using s-off. I'm pretty sure that went OK as my phone is still currently rootly rooted. Next I tried using a custom rom, i am not exactly sure what I did wrong but, I cannot boot into recovery and when i go into Hboot I get multiple "no image" popping up. I can't factory reset and when i try to boot into recovery my phone gets stuck at the mt4gs screen and i have to take out the battery. Is there anyway to fix this, easily hopefully.
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
Sounds like you need to reflash your recovery. Since you can get into fastboot still, this is an easy fix.
Just download the recovery image from here -
http://android.modaco.com/topic/343...e-mytouch-4g-slide-unofficial-modaco-edition/
once downloaded, enter hboot and select fastboot. Once your phone says "fastboot usb" on it enter the following command into fastboot -
Fastboot flash recovery c:/android/tools/recovery.img
The "c:/android/tools/recovery" portion of that command will be variable based on where the downloaded recovery image is contained on your computer.
Id say that has a pretty good chance of fixing your prollem =). Keep me posted
Sent from my myTouch_4G_Slide using xda premium

do i have to have adb to do it, because thats learning in progress

imjames said:
do i have to have adb to do it, because thats learning in progress
Click to expand...
Click to collapse
um, yeah. Fastboot is like ADB, but a different tool included in the SDK. Do you have the SDK? It's relatively simple, let me just break it down to maximize simplicity.
1) If you don't have the SDK, download it (in zip format) here. If you do have the SDK,
2) for simplicity's sake, create a Directory on your computer (the hard drive root) entitled "Android" (so that it's c:\Android).
3) If you didn't previously have the SDK, once it is is downloaded, extract the files.
4) assuming you run windows, navigate to the SDK, there's a subdirectory called "tools". Move that folder into the Android folder you created.
5) Now. take that recovery.img that you downloaded... (if you haven't done so yet, look to the link I provided in my previous post) move IT to the Android folder as well
6) open a command prompt and change the directory to the tools subdirectory of the Android folder (type cd c:android\tools), You'll now see a command prompt beginning with C:\Android\tools
7) make sure your phone is connected to your computer and in fastboot mode (select "fastboot" from the Hboot screen, it'll then say "fastboot usb" on the screen). I"m assuming your drivers are already properly installed since you were able to root your phone.
8) type in the following command into the commmand prompt - "fastboot flash recovery c:\android\recovery.img
That should do it =)

Sorry this took awhile, I am having trouble with the command prompt I can't get it to change
Sent from my myTouch_4G_Slide using XDA App

imjames said:
Sorry this took awhile, I am having trouble with the command prompt I can't get it to change
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
Because:
AndroidAutobot said:
... (type cd/c:android/tools) ...
Click to expand...
Click to collapse
Should be:
cd c:\android\tools
if you installed the SDK to a folder in your C: drive called android. That's what I did too because it makes life easier.
The rest of AndroidAutobots post is what you need to do, this one command was just typed wrong.

Blue6IX said:
Because:
Should be:
cd c:\android\tools
if you installed the SDK to a folder in your C: drive called android. That's what I did too because it makes life easier.
The rest of AndroidAutobots post is what you need to do, this one command was just typed wrong.
Click to expand...
Click to collapse
Oops lol. I cant believe i did that ha ha. Thanks for spotting that =)
I've corrected all the command lines in that particular post. Should be able to follow it step by step without any trouble now.
Sent from my HTC Doubleshot using xda premium

[TIP] How to install Clockworkmod Recovery (detailed instructions)

Moderator Edit 12/8/12
Do not use this this method twrp is officially supported for the one x. Download goo manager from the market or check the dev section.
It is not my intention to step on the toes of other people who have been more than helpful when it comes to questions relating to the installation of this or that.
Although I am reasonably familiar with many of the installation procedures when it comes to ROMs and Kernels, including Clockworkmod Recovery, etc., I am still a bit hesitant because I simply want to make sure that I am not making a mistake. After all, we spend lots of money on our phones, and the slightest error can be permanent.
I respect and admire all the developers who work tirelessly to make our lives a little bit better, and who often fulfill our ongoing need to “fiddle” with our phones. Thank you!
That being said, here is a detailed explanation of how to install Clockworkmod Recovery.
First, your bootloader must be unlocked. It doesn’t matter if you have the “TAMPERED” entry; this procedure will still work. Second, you must also have all necessary mobile phone drivers installed, including ADB, ADB drivers, and fastboot. From this point forward, I will call all these files your “Fastboot” files. If you don’t have these files, you can download them by clicking on the link at the end of this post.
At this point I’m assuming you’ve placed your Fastboot files in a separate folder within the root directory of your PC (the “C” drive?). I put these files in a folder called fastboot, but it really doesn’t matter, as long as you remember the location.
Here’s an image from my Windows Explorer screen to give you an idea of what I did:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, here we go …
Download the Clockworkmod Recovery image file and change the name to CWM.img. This is an easy name to remember, which will help further along in these instructions.
Place your newly-named CWM.img file in the directory where your Fastboot files are located.
Power down your device.
While holding VOLUME DOWN, press and hold the POWER button for a few seconds. Continue to hold VOLUME DOWN until your bootloader screen appears.
Somewhere in the middle of your bootloader screen will be seven entries entitled FASTBOOT, RECOVERY, FACTORY RESET, CLEAR STORAGE, SIMLOCK, IMAGE CRC, and POWER DOWN.
Using your VOLUME keys, make sure FASTBOOT is highlighted, and then press the POWER button once.
You should now be in the FASTBOOT Bootloader screen. On my ONE X, and I’m assuming the same for everyone, the word FASTBOOT will be highlighted with a RED background. Either way, it should be highlighted.
Connect device to your PC via USB cable.
If all is going well, the word FASTBOOT should now say FASTBOOT USB. From this point forward, do not touch the device.
Open a Command Prompt window on your PC (Press the Start button, and in the search field type cmd, and then press Enter). Here’s an example of how your Command Prompt window may look:
You must now change the directory to where your Fastboot files are located. As I mentioned above, mine are in the directory c:\fastboot. Therefore, I would need to type the following command in the Command Prompt window: cd c:\fastboot
The “cd” refers to “change directory,” while the rest is where your Fastboot files are located. Here’s how your Command Prompt window will look like after you’ve typed the above, and BEFORE you press the Enter key.
Here’s an example of how your Command Prompt window will appear AFTER you press the Enter key:
Next you need to type the following: fastboot flash recovery CWM.img
Renaming the file to CWM.img simplifies the above entry because this name is easy to remember.
Here’s how your Command Prompt window will appear BEFORE you press the Enter key:
Now press the Enter key and let the program run.
The entire installation/flash will take only a few seconds. When complete, your Command Prompt window will return to your fastboot directory (see image below).
Ignore the error in my image above, the line called error: cannot load ‘CWM.img’
This error message appeared ONLY because I didn’t want to install Clockworkmod Recovery on my device a second time. Hey, if it ain’t broke, don’t fix it, right?
Reboot your device.
DONE! You now have Clockworkmod Recovery on your phone.
These instructions are available in PDF format by clicking on the link at the end of this post.
Peter
Here's the link to the Clockworkmod Recovery file:
Clockworkmod Recovery Image
Detailed Instructions
Fastboot Files

Thanks for the excellent guide, Peter!
We were all hardcore newbies at one point and while it's annoying to see them ask redundant questions or ones that have been answered in the first post of a thread, you have to have some sympathy for them. Especially when they do something like get a soft-bricked device and begin to panic.

Thanks a lot for this!!
Would this work similarly on Linux or Mac?
Cheers!

THANK YOU this was very helpfull

Mac or Linux, I simply don't know ...
zmanw330 said:
Thanks a lot for this!!
Would this work similarly on Linux or Mac?
Cheers!
Click to expand...
Click to collapse
Regretfully, I have little to no knowledge concerning Mac and Linux, so I don't know if it would work. Sorry.
Perhaps others can answer this question.
Peter

zmanw330 said:
Thanks a lot for this!!
Would this work similarly on Linux or Mac?
Cheers!
Click to expand...
Click to collapse
Almost identical. On my Ubuntu machine I just need to type "sudo fastboot flash recovery xxx.img" and boom!
I can't see Macs being too different.

PeterHTC said:
First, your bootloader must be unlocked.
Click to expand...
Click to collapse
has this been done? have I missed something in the past day?

So far this is only for Rogers version

Peter i am following your instructions to a tee but when i try to push cwm i get the same error that shows up on your screen, i am rooted and bootloader unlocked. Can someone help
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott> cd c:\fastboot
c:\fastboot>fastboot flash recovery CWM.img
error: cannot load 'CWM.img'
c:\fastboot>

fastboot flash recovery recovery.img
Sent from my HTC One XL using xda premium

No, you didn't miss anything ... so far
fionic said:
has this been done? have I missed something in the past day?
Click to expand...
Click to collapse
No, you didn't miss anything so far. The bootloader on AT&T units cannot yet be unlocked, but I'm sure it's only time. Once unlocked, then you can follow the installation instructions.
Peter

Peter said change the file name to CWM

I hope I'm not patronizing, but ...
sm625614 said:
Peter i am following your instructions to a tee but when i try to push cwm i get the same error that shows up on your screen, i am rooted and bootloader unlocked. Can someone help
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott> cd c:\fastboot
c:\fastboot>fastboot flash recovery CWM.img
error: cannot load 'CWM.img'
c:\fastboot>
Click to expand...
Click to collapse
I hope I don't insult you, but did you connect the phone to your PC via USB? The reason I ask is that I got my error message because I disconnected my phone prior to hitting the Enter key. As I mentioned, I didn't want to install it a second time and risk doing something harmful.
Did you also get FASTBOOT USB highlighted on your device after you plugged it in?
Peter
Addendum: Don't forget that these entries in your Command Prompt are case sensitive. Capital letters must remain as capitals, and small letters as small ... exactly as shown in my instructions. Again, I hope I'm not patronizing anyone. That's not my intention.

Of course your not insulting me, your just being detailed lol. The phone is 100% connected to the computer via USB. I am in fastboot mode with FASTBOOT USE highlighted in red. I am following you instructions perfectly and i got the same error. Do you think i should reinstall htc sync to reinstall the drivers. I am quite lost here on why this is not working.

Did you ...
sm625614 said:
Of course your not insulting me, your just being detailed lol. The phone is 100% connected to the computer via USB. I am in fastboot mode with FASTBOOT USE highlighted in red. I am following you instructions perfectly and i got the same error. Do you think i should reinstall htc sync to reinstall the drivers. I am quite lost here on why this is not working.
Click to expand...
Click to collapse
One thing I should have included in my first post (I will amend it shortly), is a link to the actual Clockworkmod Recovery file, which is currently available on another thread.
Did you download THAT file?
Peter
Addendum: Clockworkmod Recovery Files link now included in original post
Addendum 2: Re-installing HTC Sync might be helpful. It's what I would eventually do.

YES i have that file and i renamed it to the CWM.img name that you recommended. What do you think i should do?

I changed the first image in the original post ...
I changed the first image in the original post. It now includes the Clockworkmod Recovery file, marked as CWM.
Peter

Hmm, I would ...
sm625614 said:
YES i have that file and i renamed it to the CWM.img name that you recommended. What do you think i should do?
Click to expand...
Click to collapse
Well, I'm not entirely sure. What I would do is start all over again after restarting your PC and Phone. If it does not work then, uninstall and reinstall HTC sync. After that, I'm stumped. Sorry.
Peter

sm625614 said:
Of course your not insulting me, your just being detailed lol. The phone is 100% connected to the computer via USB. I am in fastboot mode with FASTBOOT USE highlighted in red. I am following you instructions perfectly and i got the same error. Do you think i should reinstall htc sync to reinstall the drivers. I am quite lost here on why this is not working.
Click to expand...
Click to collapse
Do you have a file named "CWM.img" in the same folder as fastboot? That part of the command is telling fastboot which file to install. Make sure the image file is named correctly, or you can alter the command to reflect the name of the file.

I think you should write it into the title and the post saying for now this is only for Rogers users. It might cause a problem bbecause you said even if the bootloader ssays tampered it'll work. And I'm on att and it says tampered bbut this won't work for ATT HOX.
Just a precaution
Sent from my HTC Vivid 4G LTE using Tapatalk 2

[Need Serious Quick HELP!!!]One S stuck.on bootup

im on my one s, found out that my volume wasnt working an so i tried to fix it by reflashing the rom, but by accident i did a factory reset and the rom was gone, i already wiped the davlik and all that then i barely remembered that i already deleted the rom (was flashing T-Mobile noble series 7.5 for USA version) so now i tried to reboot the phone and im stuck on the bootup and it stays there for a GOOD while..im freaking out right now, anyway i can still get into the bootloader and fastboot but i cant get the rom back into my phone, i did no back ups and im really scared, if anyone can help it would be totally awesome. And if it helps I used the hasoon toolkit 1.0 to unlock my phone and Paul o Brian method to root it.

search for adb and push.
You schould be able to push the rom zip via ADB onto the sdcard and afterwards you can normaly flash it via cwm recovery

HighRoIIer said:
search for adb and push.
You schould be able to push the rom zip via ADB onto the sdcard and afterwards you can normaly flash it via cwm recovery
Click to expand...
Click to collapse
can you post a link to get it, i'd look through the whole place but i have to get to school and the last weeks of it are keeping me busy..i would really appreciate it if you could find me a link

Nice descriptive title of this thread...
Anyways http://lmgtfy.com/?q=adb+push+rom if youre in a hurry, and http://www.catb.org/~esr/faqs/smart-questions.html for when you have more time again, good luck m8
Sent from my HTC One S using xda premium

any help making this easier, idk what the hell im doing, im just trying to push my rom into the phone, this is confusing, im going insane!!!! ok i need this alittle easier im a noob at this, i got my phone rooted with cwm and i accidentallly erase the rom now im trying to put it back in. is there a certain adb fastboot that im missing cuz i tried it and it gives me the correct prompt file....this is really starting to irritate me, it doesnt even push the rom in......i would really appreciate some step by step process on how to do this today.this is my first phone and i really dont want it to brick at all.

let's assume you have adb and fastboot files on pc, if not you need to either install them to a folder of your choice ie Android or install android sdk and set them up that way:
These are the files that need to be in that folder--
http://dl.dropbox.com/u/28338566/adb_fastboot_win32.zip
but if you have them on pc and can connect phone and open command window, cd to your folder where the adb and fastboot files are, maybe something like cd/ hit enter then cd android/android-sdk-windows/tools, or whatever the path is
when you are there and right after the whatever your path is type adb devices and you should get your phone id #
you can google some of this stuff and see videos
if you can get that far do this: download the same rom to your pc and extract it with winrar. open it and you should see a system.img and boot.img file. copy them to the folder where you have the adb/fastboot files
then after you have the adb devices command recognizing your phone type this:
adb reboot bootloader which will put you into fastboot, to verify that before you proceed you can type fastboot devices and see the phone ID # again--then
fastboot erase system
fastboot erase boot
fastboot -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
not sure if you need fastboot -w since you already wiped userdata
you should then be able to get rom booted back up and reset things up again--then nandroid and you should always have an sdcard bu also
if you don't have a recovery anymore you can fastboot it same way by typing
fastboot flash recovery "exact name of recovery.img"
fastboot reboot
I am no expert and you can research this stuff till you feel comfortable or someone can confirm

Yes still no.luck, I'm still stuck on boot up...
Sent from my YP-G1 using XDA

You seem to be able to use adb from what you post. So
1) Boot the phone into CWM
2) Put the rom into the same folder on your pc as the adb program
3) Open a command prompt on the pc, and navigate to the folder with the rom and adb in it, eg "cd c:\adb"
4) Push the rom to the phone: "adb push rom.zip /mnt/sdcard" (if it doesn't work, try it again and change "mnt/sdcard" to just "sdcard"
5) In CWM, choose flash zip file. The zip file should be in the root of your sd card.

rugmankc said:
let's assume you have adb and fastboot files on pc, if not you need to either install them to a folder of your choice ie Android or install android sdk and set them up that way:
These are the files that need to be in that folder--
http://dl.dropbox.com/u/28338566/adb_fastboot_win32.zip
but if you have them on pc and can connect phone and open command window, cd to your folder where the adb and fastboot files are, maybe something like cd/ hit enter then cd android/android-sdk-windows/tools, or whatever the path is
when you are there and right after the whatever your path is type adb devices and you should get your phone id #
you can google some of this stuff and see videos
if you can get that far do this: download the same rom to your pc and extract it with winrar. open it and you should see a system.img and boot.img file. copy them to the folder where you have the adb/fastboot files
then after you have the adb devices command recognizing your phone type this:
adb reboot bootloader which will put you into fastboot, to verify that before you proceed you can type fastboot devices and see the phone ID # again--then
fastboot erase system
fastboot erase boot
fastboot -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
not sure if you need fastboot -w since you already wiped userdata
you should then be able to get rom booted back up and reset things up again--then nandroid and you should always have an sdcard bu also
if you don't have a recovery anymore you can fastboot it same way by typing
fastboot flash recovery "exact name of recovery.img"
fastboot reboot
I am no expert and you can research this stuff till you feel comfortable or someone can confirm
Click to expand...
Click to collapse
Yea I'm still stuck and after a long time of seeing a couple of people not being able to fix my issue, I'm wondering of someone can confirm if this works or if it's possible to flash a ROM without putting it in the phone just flash it from adb? Been a while since I got on and I'm just gonna dedicated time on fixing my one s.... I really appreciate the feedback
Sent from my YP-G1 using xda app-developers app

Yes you can push it thru adb as mentioned above
i have to call it a nite. Just google pushing a Rom thru adb for more Info if needed
---------- Post added at 05:21 AM ---------- Previous post was at 05:12 AM ----------
You never mentioned just downloading Rom to pc and copying to sd card. Then thru recovery wipe and flash rom.
---------- Post added at 05:26 AM ---------- Previous post was at 05:21 AM ----------
Never mind guess you can't connect phone pc and mount to copy files

This thread show how to ADB push a file to your phone
http://forum.xda-developers.com/showthread.php?p=26430276

Yea I'm gonna try that today but I was wondering if somehow we can make the computer flash it onto the phone for us (you know technology now a days) for situations like this for people who can't get access to their sd cards since the sd cards are non removable and make it a little more simpler to fix phones in this type of situation....just a thought put out there, I'm just thinking alot of things to make situations like this easier for people who are trying to get the best of their phone.
Sent from my samsung galaxy player

leohdz148 said:
Yea I'm gonna try that today but I was wondering if somehow we can make the computer flash it onto the phone for us (you know technology now a days) for situations like this for people who can't get access to their sd cards since the sd cards are non removable and make it a little more simpler to fix phones in this type of situation....just a thought put out there, I'm just thinking alot of things to make situations like this easier for people who are trying to get the best of their phone.
Sent from my samsung galaxy player
Click to expand...
Click to collapse
Yeah with a removable SD card it would have been as easy to just take the sdcard and stick it in the computer.
Just be patient and learn to use adb. In the long run it will make things easier for you. Plus you earn some valuable info and upgrade from noob status.
Good luck!
Sent from my HTC One S using Xparent ICS Tapatalk 2

ok....I will give this a try until I get my phone restored, most of my time is dedicated to my phone. Will update later on on progress
Sent from my samsung galaxy player

Just go on bootloader, install CWM recovery (adb is working on it) and send a rom by adb : adb push rom.zip /sdcard
copy the rom in adb folder first and replace "rom.zip" by the name of your rom.
Next go to recovery and flash your rom !
I already have he same problem like you, I was scared too, but don't panic you can install a rom

Ok I just got my phone back and it gets stuck on the boot on the way to the bootloader I can't get into Fastboot or the recovery, any ideas?
Nvm I got it back now it's only the recovery it goes to right away I try to go into bootloader but it gets stuck.on the HTC boot with red text displaying on it. Ok another thing I got into the bootloader and flashed the stock recovery but it got stuck on the boot again....ok another edit, I got the other recovery flashed but it won't boot into recovery it stays on the boot screen with red text.
Sent from my samsung galaxy player

I get back into the bootloader and flashed the recovery again and then try to go into recovery but it stays stuck On boot up with red text for a little bit then turns off black then turns on again in bootup with red text and stays there, any clues?
Edit: I'm in recovery now but it won't push the ROM and I keep trying but it says
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my samsung galaxy player

Not sure what all you have done by now--so--
First off did you unlock again, as HTC may have locked it--even though you have red letters? (You said you just got it back--assume from HTC)
If unlocked confirmed--
Can you turn phone on and have it just boot into the homescreen
If so, can you connect to pc and have phone with usb debugging on and fastboot off (fastboot is under settings/power). Open command window and cd to your adb/fastboot folder and type adb devices then fastboot devices
if they work put latest cwm recovery image in the adb/fastboot folder and flash it by--
type adb reboot bootloader
then fastboot flash recovery recovery.img of course use exact recovery image name
if adb devices and fastboot devices don't work verify your sdk is set up and drivers are installed--
you may have already done this--sorry, just trying to start at the beginning

Ok so I'm at the point where I'm in recovery and the command prompt is open but idk how to do this...some help would sure be nice this is what I get when. I try to push something
Note: I kinda modified the name to just ROM so I won't have to type so much
Sent from my samsung galaxy player

what is x86 Mac? i just do a cd/ [enter] then cd android/android-sdk-windows/tools [enter]. that is my path. If on windows and sdk, you need the environmental variable path set to that path i just typed, or whatever your's is. not sure on a mac.
on windows I use forward slashes--not sure it matters
at the prompt you show type adb devices, if it doesn't come back with # followed by numbers you are not set up with adb, reinstall htc drivers and make sure whatever you are fastbooting, is in your tools folder

[Guide] Root on Linux Mint

Rooting a Xiaomi Mi 4i on Linux Mint 17.1 Rebecca
- This guide might also be relevant for users of Debian and Ubuntu
Disclaimer: I accept no responsibility for any damage you do to your phone, body, life or anything else in the past present or future.
This has been written as I had so much difficulty in getting my Mi 4i rooted. I kept trying to do it in Windows through Virtual Box but kept failing.
1. Enable Developer Options
- On your phone, go to Settings
- About phone
- Keep tapping on the Android version until the message at the bottom says that you are a developer
2. Enable USB debugging
- On your phone, go to Settings
- Additional settings
- Developer options
- USB debugging
3. Install the tools
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
4. Try and see the devices
- Connect the phone to your computer
- Run the following command at the terminal
Code:
adb devices
- It will now say List of devices attached.
- If you see another line with an 8 character identifier such as bf1b6529 then you can skip step 5
5. Add phone to known devices
- Run the following command on the terminal
Code:
echo 0x2717 >> ~/.android/adb_usb.ini
6. Add your computer to trusted devices on your phone
- Enter the following command on the terminal:
Code:
adb devices
- Look on your phone, it should now be asking you if it can add the machine to the trusted devices, or something like that. I'm writing this from memory.
7. Check that adb devices is working
- Enter the following command on the terminal:
Code:
adb devices
- Check that the device ID is there (8 characters such as bf1b6529)
- Check that it says device after it
8. Kill adb
- Enter the following command on the terminal
Code:
adb kill-server
9. Now for the fun. You will need sudo access for this stage.
- Download boot.img to your computer.
- At the terminal, navigate to the directory where you downloaded boot.img, this will probably be ~/Downloads
- At the terminal:
Code:
adb reboot bootloader
- You will now see a screen like the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- At the terminal:
Code:
sudo su
fastboot devices
- You will now see your device ID followed by fastboot
Code:
fastboot boot boot.img
- You will now see something like the following:
Code:
downloading 'boot.img'...
OKAY [ 1.022s]
booting...
OKAY [ 0.259s]
finished. total time: 1.281s
10. Restart
- At the terminal enter:
Code:
fastboot reboot
- You should now see a textual boot screen wher you can see it actually carrying out the rooting with boot.img
- Then it should boot as normal into Android
- Check your apps. You should now have SuperSU

Thanks for step no 5. After trying all kind of 51-android.rules guide from stackoverflow and your solution work. Now I can detect my device in Linux Mint.
5. Add phone to known devices
- Run the following command on the terminal
Code:
echo 0x2717 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse

thanks....
finally i can connect my mi4i to my linux desktop

Thank you for your guide. I assume this will work on Ubuntu 14.04 as well.
Question to step no.9: "Download boot.img to your current dir" => Which directory do you mean? The root of the phone or on my laptop? Sorry for being newbie. Many thanks.

rmsinaga said:
Which directory do you mean? The root of the phone or on my laptop?
Click to expand...
Click to collapse
You need to download boot.img to your laptop. I've updated Step 9 with the following:
- Download boot.img to your computer.
- At the command line, navigate to the directory where you downloaded boot.img, this will probably be ~/Downloads
Click to expand...
Click to collapse

Step one on the path to rooting my m4i was getting adb to work.
kblade29m said:
Thanks for step no 5. After trying all kind of 51-android.rules guide from stackoverflow and your solution work. Now I can detect my device in Linux Mint.
Click to expand...
Click to collapse
After much googling, much time, and trial and error, I had reached this point. Then I come here and here it is! All made simple.
The next hurdle is that adb devices shows the phone with the word "offline," and that is where...
aembleton said:
- Look on your phone, it should now be asking you if it can add the machine to the trusted devices, or something like that. I'm writing this from memory.
Click to expand...
Click to collapse
...I find I wasn't even seeing the message because the flip cover was closed. Doh.
This is my second Android phone, and I rooted and installed CM on the previous one, a Defy+. Still feel very much a novice, and approaching the rooting is quite scary. Among my worries...
Does this method change the recovery?
Does this method, with boot.img, install a new rom, or does it root the exisiting one?
Will everything else be reset/wiped? (well, backups anyway. Of course).
Will Xiaomi updates still work and be installable?
I am considering using method 1 from "Root/Unroot V6.5.x W/out Losing Stock Recovery [Simplified]" (new member: cannot make that a link) . Any comments?
It is so nice to see the Linux, and especially mint-specific, advice here. Thank you!
(My first post here: usual forum-novice disclaimers apply )

I have used this method to root my mi4i.
Quick answer:
1. No
2. It only roots the existing ROM
3. No
4. You need to full unroot 1st from SuperSU before updating, otherwise it will be bootloop
5. Never tried before

rmsinaga said:
I have used this method to root my mi4i.
Quick answer:
... ... ...
Click to expand...
Click to collapse
Great answer! :good:
Thank you very much for attention to every detail. The only thing putting me off going for this straight away is that I am travelling in just over a week, which doesn't give me any margin for making mistakes (if they can be made, I will make them!).
You mentioned having failed to make stuff work in a virtual machine. Did you try Wine? I failed to make the Mi PC manager software run in Wine.

Simple, painless and absolutely effective
aembleton said:
10. Restart[/B]
- At the terminal enter:
Code:
fastboot reboot
Click to expand...
Click to collapse
(response typed from memory)
Code:
# fastboot reboot
<Waiting for Device>
...amd it goes on waiting. Does anybody get any other response on the terminal screen after this?
Anyway, Be Patient! Probably better to make tea or something away from the screen. After several minutes of Fastboot screen on the phone, the process continues as premised...
aembleton said:
- You should now see a textual boot screen wher you can see it actually carrying out the rooting with boot.img
- Then it should boot as normal into Android
- Check your apps. You should now have SuperSU
Click to expand...
Click to collapse
...and all is well.
After the phone had rebooted, I just ctrl-c-ed the fastboot process and exited from the terminal.

Works wonders, thanks!
Could only find ****ty .exe rooting tools that seemed sketchy and don't have windows installed anymore, so this saved me hours.
My computer could find the phone through adb and got authorized, the phone couldn't find my computer through adb though which was strange but it still worked fine. Thanks alot!

Thad E Ginathom said:
4. Will Xiaomi updates still work and be installable?)
Click to expand...
Click to collapse
rmsinaga said:
4. You need to full unroot 1st from SuperSU before updating, otherwise it will be bootloop
Click to expand...
Click to collapse
Just tried this, it does not work.
Disabled root from SuperSU and updated to the newest weekly developer rom, and my device is now in a boot loop.
I'm currently trying to download the stable fastboot rom from the MIUI forums, but their servers are both incredibly slow and unstable. Doesn't go past 100kb/s and the download loses connection after a while and fails to continue the download. If someone could provide a alternative download link that would be great.
EDIT: Found a hidden link on the rom page for the fastboot rom from the miui page. Go to this page and Ctrl-F Mi4i

zenolijo said:
Found a hidden link on the rom page for the fastboot rom from the miui page. Go to this page and Ctrl-F Mi4i
Click to expand...
Click to collapse
Did this work for you?
I also got into a boot loop after installing the latest update. I installed the latest stable version. This worked, but the Play Store won't start.

aembleton said:
Did this work for you?
I also got into a boot loop after installing the latest update. I installed the latest stable version. This worked, but the Play Store won't start.
Click to expand...
Click to collapse
Well, the stable fastboot rom isn't the global version, so i only used it to get my phone running again and then flashed the stable global version. Everything works as expected now.

How to update ROM using fastboot in Linux?
Do you know how to update ROM using fastboot in Linux?
Sorry to bother you as I'm new in this Linux world.
Thank you.

Thank you man, you have guided us to the land of light, you are our moses, krishna, muhammad and so on and so forth. We can flash left and right without second thoughts. Please keep up your efforts. Thank you one more time.

My phone is, as per previous posts, rooted, using this method.
Can I now flash TWRP recovery from Linux?

Hey, this is a method only for Xiaomi Mi4i? I have an Estar Crystal-clearview and wondering if I can root it by this method? I run the terminal with the adb install and then for the list of devices attached, and I started thinking about!
P.s. Just searched ''root with mint'' and your post was first!

Thad E Ginathom said:
Can I now flash TWRP recovery from Linux?
Click to expand...
Click to collapse
Eventually I got around to doing this using Flashify. I followed the instructions here on the MIUI forum. It was simple and straightforward and I now have TWRP recovery.
However, when I tried to use it to do a backup, it said there was not enough space. But it was long past bedtime, and that is another story that I have yet to investigate. There is probably a simple answer, err... make more space! The absence of SD card slot and the limited internal memory is the big frustration about this phone.
But I want to upgrade MIUI --- and I don't want to do it without an easy backtrack to the previous ROM.

[Solved] Step 9 not working
Goto developer options
Check if 'fastboot mode' is enabled

Thanks
Hi aembleton,
Thanks a lot. it worked just fine.
does this replace recovery too ?

[GUIDE] Install Android SDK Standalone [ADB][30 Dec 2015]

Android SDK - Powerful tool and easy to set up for use with your Android Device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am putting this together for some who may be confused on how to set this up. I love Android SDK, have been using it for ever and once it is setup, maintenance is extra easy. There are 100 ways to skin a cat with ADB tools and development tools. This is my personal choice, go about it how ever you want. This tool is well maintained and always updated so its a big reason I use it. Great support and a great and powerful tool
Click to expand...
Click to collapse
Part 1. Follow These Steps Below - (Preparation)
Download Links For Tools
1. Java SE Development Kit (JDK)
2. Android SDK Tools Only - Download Only, Do Not Install yet
If You Choose Windows for example
3. Universal ADB Drivers - Instructions Here
Click to expand...
Click to collapse
How to Install and Set-up
1. Install Java SE Development Kit (JDK) from Start Here section if you have not yet
2. Launch Android SDK installer you downloaded up above in Download Links
3. During install - Set Installation Path to
Code:
C:\Android\
4. After Installation is Complete, run SDK Manager.exe
5. Install 5.1.1 and 6.0 since these are the APIs for all current Devices. Should not really see anything less than 5.1.1
Note* - Just put a check box where you see the red circles in the picture. The reason I have Tools (Preview Channel) is because I updated to the 25.0.1 RC2 SDK Tools, however, that is not required. You can choose 24.4.1 and it will be fine. It will say installed where as mine does not in the picture because I chose to use 25.0.1 RC2
6. Let all updates install to completion - This could take a while depending on your internet connection
Click to expand...
Click to collapse
The Computer and Phone are now prepped for you to start the whole ADB Process
Click to expand...
Click to collapse
Part 2. Verifying ADB is set up properly and Working
IMPORTANT - Make sure you have already enabled developer options and USB Debugging or you will not see the below results
1. Open Command Prompt and Change directories to your platform-tools folder. This is where all the adb files are located. See Below
In Command Prompt Type - Refer to Part 3 so you no longer need to Change Directory
Code:
cd c:\Android\platform-tools
2. In Command prompt type
Code:
adb devices
You Should get Prompted to Allow USB debugging - Ignore if You Already Have Done This
3. If your output shows your device attached like below, then you are good to go!!!
and
YOU ARE FINISHED!!! Below is a command to get into the bootloader if interested!! Good Luck
Click to expand...
Click to collapse
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
1. Press Win+R, then type
Code:
sysdm.cpl
2. Click Advanced Tab
3. Click Environment Variables Button
4. Under System Variables, find Path, click to highlight it and then hit the edit button
Windows 8
Windows 10
5. Go to the end of the Variable Value and add the following exactly as you see it in the code box below
Code:
;C:\Android\platform-tools
Windows 8
Windows 10
6. Click OK to accept the changes you just added
7. Open Command Prompt again to verify by pressing Win+R and type cmd and hit enter
8. Once Command Prompt is open -> Simply type adb devices with your device connected with USB Debugging already enabled
9. If you did everything correctly, there is no need to change paths anymore
Click to expand...
Click to collapse
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
@Ashraf - Images used for Environment Variables - Not all were his since the guide was modified
@[B]Snoop05[/B] - ADB Drivers and Fastboot

Reserve if Needed

Thank you so much for this - can i ask what's the size of the SDK manager files which we are supposed to download? For some reason it downloads in 86 kb/s speed (normaly 5-6 mb/s) so I just wanted to know if i'm going to wait a long time

Peccoskaify said:
Thank you so much for this - can i ask what's the size of the SDK manager files which we are supposed to download? For some reason it downloads in 86 kb/s speed (normaly 5-6 mb/s) so I just wanted to know if i'm going to wait a long time
Click to expand...
Click to collapse
Hey the installer size is 145mb. I was able to download it in 15 seconds
Updating sdk manager will take a while. I am not sure of the file size... It will take a while... You only have to do this once. Updates after this will be quick
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Hey the installer size is 145mb. I was able to download it in 15 seconds
Updating sdk manager will take a while. I am not sure of the file size... It will take a while... You only have to do this once. Updates after this will be quick
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
I've tried it many times.... i have enough space on my drive, but everytime i try to download this one and only part, prints out this error message....why do i always have so many problems with it

Peccoskaify said:
I've tried it many times.... i have enough space on mi drive, everytime i try to download this one and only part it prints out this error message....why do i always have to have so many problems with it
Click to expand...
Click to collapse
Lol you and me both bro, but you don't have to install that, that is optional, the rest looks good. You should be able to use it now
Edit: looks like a network issue or the repository is down... That will work itself out.. Right now, it is not required
Sent from my LG-H901 using Tapatalk

This is seriously getting ridicolous - Now everything is downloaded, cmd sees the device I have every stupid thing set-up and still....phone only reboots when i type - adb reboot bootloader -
Shell I record it for you?
Edit:
I did record it -

Peccoskaify said:
This is seriously getting ridicolous - Now everything is downloaded, cmd sees the device I have every stupid thing set-up and still....phone only reboots when i type - adb reboot bootloader -
Shell I record it for you?
Edit:
I did record it -
Click to expand...
Click to collapse
Sounds like your bootloader is borked, you should always be able to get into...Were you able to flash TWRP successfully? Not sure where you went wrong, I would try to push boot.img again, you should have a recovery
Go Here

bdorr1105 said:
Sounds like your bootloader is borked, you should always be able to get into...Were you able to flash TWRP successfully? Not sure where you went wrong, I would try to push boot.img again, you should have a recovery
Go Here
Click to expand...
Click to collapse
I followed steps till the one i got stuck in, so no i did not flash TWRP :/ or anything else. - It's weird that it is broken because it's new phone and i did not do anything to it, expect for right now :/ But sure I'll try

Peccoskaify said:
I followed steps till the one i got stuck in, so no i did not flash TWRP :/ or anything else. - It's weird that it is broken because it's new phone and i did not do anything to it, expect for right now :/ But sure I'll try
Click to expand...
Click to collapse
I think your bootloader may still be locked
Have you done this? Make sure USB Debugging is enabled, OEM Unlock is checked, You are in PTP, type adb devices and verify it sees your device then do the following Next:
nvm edited out got ahead of myself

bdorr1105 said:
I think your bootloader may still be locked
Have you done this? Make sure USB Debugging is enabled, OEM Unlock is checked, You are in PTP, type adb devices and verify it sees your device then do the following Next:
nvm edited out got ahead of myself
Click to expand...
Click to collapse
If you look at the video you can see that i have both on and PTP too - without PTP cmd won't see my device...i think
oh sorry

Peccoskaify said:
If you look at the video you can see that i have both on and PTP too - without PTP cmd won't see my device...i think
oh sorry
Click to expand...
Click to collapse
Have you had any luck?
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Have you had any luck?
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Nope :/

Is there way to flash some LG stock android in my phone so it will have bootloader? :/ - I'm not very good in english so i don't even know what to search for :/

Peccoskaify said:
Is there way to flash some LG stock android in my phone so it will have bootloader? :/ - I'm not very good in english so i don't even know what to search for :/
Click to expand...
Click to collapse
Yea I am looking into it the v10 is hard to find anything
Sent from my LG-H901 using Tapatalk

Peccoskaify said:
Is there way to flash some LG stock android in my phone so it will have bootloader? :/ - I'm not very good in english so i don't even know what to search for :/
Click to expand...
Click to collapse
Ok try this
1. Power phone off
2. Hold volume down and power together 3. Once LG Logo appears, let go of power for 1 second and press power again.. Never let go of volume down
4. Then chose to factory reset
This may resolve the issue so you can retry again
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Ok try this
1. Power phone off
2. Hold volume down and power together 3. Once LG Logo appears, let go of power for 1 second and press power again.. Never let go of volume down
4. Then chose to factory reset
This may resolve the issue so you can retry again
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Did it, nothing changed, is this reason for refund?

Peccoskaify said:
Did it, nothing changed, is this reason for refund?
Click to expand...
Click to collapse
Ok another method
1. Install Terminal Emulator
2. Open the Terminal
3. Type# su
4. Type# reboot-bootloader
This should go straight to the bootloader, if it doesn't, I am at a loss

bdorr1105 said:
Ok another method
1. Install Terminal Emulator
2. Open the Terminal
3. Type# su
4. Type# reboot-bootloader
This should go straight to the bootloader, if it doesn't, I am at a loss
Click to expand...
Click to collapse
I just can't anymore - so far thank you for your help, even though it's never year you are willing to help, not many people would waste time with me

Peccoskaify said:
I just can't anymore - so far thank you for your help, even though it's never year you are willing to help, not many people would waste time with me
Click to expand...
Click to collapse
Thats not correct, su did not work, you should have a # symbol before the command, guess not being rooted doesn't help
edit: connect your phone to the computer and type the same command
I think strangely it is just recognizing adb reboot and omitting the bootloader, so try adb reboot-bootlader when connected to the computer