Related
Hi,
I'm on the process of installing ClockWorkMod Recovery, stupid of me i forgot to enable USB Debugging option on my phone. Now I'm stuck on Command Prompt saying...
C:\Fastboot>fastboot flash boot recovery-nozomi.img
< waiting for device >
It has been sitting for more than 5 minutes as I am typing now. Should I disconnect the USB cord? Would this action brick my phone?
Sorry for my stupidity!
cybrkada said:
Hi,
I'm on the process of installing ClockWorkMod Recovery, stupid of me i forgot to enable USB Debugging option on my phone. Now I'm stuck on Command Prompt saying...
C:\Fastboot>fastboot flash boot recovery-nozomi.img
< waiting for device >
It has been sitting for more than 5 minutes as I am typing now. Should I disconnect the USB cord? Would this action brick my phone?
Sorry for my stupidity!
Click to expand...
Click to collapse
How are you installing it ???
Via flash tool??
And nope your phone won't brick
I disconnected the cord. Turned on the phone and noticed that USB Debugging is ticked/checked. So I repeated the process but I am still getting..
< waiting for device >
What should I do?
soulhackereborn said:
How are you installing it ???
Via flash tool??
And nope your phone won't brick
Click to expand...
Click to collapse
Yes, via Flastool. Yeah my phone did not get bricked! :good:
cybrkada said:
Yes, via Flastool. Yeah my phone did not get bricked! :good:
Click to expand...
Click to collapse
can u give the link for this recovery you triein to push through flashtool and the turorial if possible...
soulhackereborn said:
can u give the link for this recovery you triein to push through flashtool and the turorial if possible...
Click to expand...
Click to collapse
Hi soulhackereborn!
Sorry for the late reply! Sorry the forum prevented me from posting the URL as I am just a new user here.
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Anyway the tutorial says (copy&paste):
Use the computer for downloading the CWM file from here.
Then, on the same computer download fastboot from here.
Extract fastboot on C:\ drive.
Then, copy the downloaded “ecovery-nozomi.img” file to the Fastboot folder from your computer.
Now you must connect the phone in fastboot mode with the computer.
In order to do so you must plug the USB cord to the PC, then on your phone press and hold the Volume Up button and while doing this connect the USB cable to your Xperia S.
Up next, on the PC click on “Start -> Accessories -> on Command prompt right click -> Run as administrator”.
The command prompt window will now be displayed.
Now, enter the following commands (press enter after each one): “cd c:\Fastboot” and “fastboot flash boot recovery-nozomi.img”.
CWM will now be flashed.
In the end the “finished / OKAY” message should be displayed.
In command prompt enter “fastboot reboot”.
Your handset should now reboot into ClockworkMod recovery.
Remove the USB cord and disconnect the Xperia S from the computer.
cybrkada said:
Hi soulhackereborn!
Sorry for the late reply! Sorry the forum prevented me from posting the URL as I am just a new user here.
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Anyway the tutorial says (copy&paste):
Use the computer for downloading the CWM file from here.
Then, on the same computer download fastboot from here.
Extract fastboot on C:\ drive.
Then, copy the downloaded “ecovery-nozomi.img” file to the Fastboot folder from your computer.
Now you must connect the phone in fastboot mode with the computer.
In order to do so you must plug the USB cord to the PC, then on your phone press and hold the Volume Up button and while doing this connect the USB cable to your Xperia S.
Up next, on the PC click on “Start -> Accessories -> on Command prompt right click -> Run as administrator”.
The command prompt window will now be displayed.
Now, enter the following commands (press enter after each one): “cd c:\Fastboot” and “fastboot flash boot recovery-nozomi.img”.
CWM will now be flashed.
In the end the “finished / OKAY” message should be displayed.
In command prompt enter “fastboot reboot”.
Your handset should now reboot into ClockworkMod recovery.
Remove the USB cord and disconnect the Xperia S from the computer.
Click to expand...
Click to collapse
everything seems to be good in the tutorial though..
But what is it a kernel, rom or an CWM image file ???
if still it says waiting for device then here's a couple things you should check :-
1) Fastboot ie; S1 Boot driver installed or no
2) Switch off phone and connect it to the PC via usb holding Volume + button (this is fastboot mode)
3) Check does your device remain in fastboot mode or no i mean purple led light glows stays on continuously or no until u execute the command, if not reinstall the driver and try again
4) If everything well till now try flashing with the given commands without the quotes ie; fastboot flash boot recovery-nozomi.img
soulhackereborn said:
everything seems to be good in the tutorial though..
But what is it a kernel, rom or an CWM image file ???
if still it says waiting for device then here's a couple things you should check :-
1) Fastboot ie; S1 Boot driver installed or no
2) Switch off phone and connect it to the PC via usb holding Volume + button (this is fastboot mode)
3) Check does your device remain in fastboot mode or no i mean purple led light glows stays on continuously or no until u execute the command, if not reinstall the driver and try again
4) If everything well till now try flashing with the given commands without the quotes ie; fastboot flash boot recovery-nozomi.img
Click to expand...
Click to collapse
1. I dont know how to check, it should be installed as i unlock the bootloader yesterday. I actually manually updated it on Device Manager.
2. I understand this.
3. On my case, it's a blue LED lit steadily after doing step 2. I am using Sony Xperia S.
4. Yes, i flashed them without the quotes.
cybrkada said:
1. I dont know how to check, it should be installed as i unlock the bootloader yesterday. I actually manually updated it on Device Manager.
2. I understand this.
3. On my case, it's a blue LED lit steadily after doing step 2. I am using Sony Xperia S.
4. Yes, i flashed them without the quotes.
Click to expand...
Click to collapse
Try rebooting both your PC and phone... This is a small thing but always helps and one more thing after switching off the phone n before connecting it in fastboot mode let der be a gap of alteat a min or two
Is this tutorial on xda or some other forum if on xda then try messaging me the link or tel me forum sub forum topic and title
Usually <waiting for device> can show up when you don't have proper drivers installed. Double check them if you haven't done so.
soulhackereborn said:
Try rebooting both your PC and phone... This is a small thing but always helps and one more thing after switching off the phone n before connecting it in fastboot mode let der be a gap of alteat a min or two
Is this tutorial on xda or some other forum if on xda then try messaging me the link or tel me forum sub forum topic and title
Click to expand...
Click to collapse
I dont see PM here, i think I am still restricted.
see if the link helps, i removed w w w
android.gs/install-clockworkmod-recovery-sony-xperia-s
i'm rebooting them after this.. thanks
LiveSquare said:
Usually <waiting for device> can show up when you don't have proper drivers installed. Double check them if you haven't done so.
Click to expand...
Click to collapse
Which drivers? I have already downloaded SDK and I believe the S1 driver is installed yesterday when i unlock the bootloader.
i rebooted both the PC and the CP, but i am still getting < waiting for device >...
by the way is the ADB from tutorial the SDK one?
cybrkada said:
i rebooted both the PC and the CP, but i am still getting < waiting for device >...
by the way is the ADB from tutorial the SDK one?
Click to expand...
Click to collapse
Dude as far as I know there is no need to check/ tick USB debugging for fastboot... It's just for flashtool..
Try re -installing the drivers again manually or let windows search over internet...
Finally, i made it! thanks to both of you!
fastboot.exe seems to be corrupted!
Problem solved!
Just last one question, now that i have CWM recovery on my phone, is it already rooted? sorry i am beginner...
cybrkada said:
Just last one question, now that i have CWM recovery on my phone, is it already rooted? sorry i am beginner...
Click to expand...
Click to collapse
Yes ur rooted!!
Thanks!
I'm currently downloading Cyanogenmod ver 9.1. Hopefully it works! Thank you so much buddy! You have been very helpful! If I get problems on flashing CM9.1, i'll contact you , hehe
One of the reminders on isntalling CM9 is:
Make sure that your Xperia S is already running a rooted firmware, and that it has the ClockworkMod Recovery properly installed.
How do I know I have a rooted firmware? Do I still need to flash FTF file?
By the way, I am getting a boot loop from CWM recovery, I cant go to the homescreen, no option to turn off! It only reboots the CWM.
(Still downloading CM9 as of the moment)
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Download mfastboot and redownload the recovery img
hetor99 said:
Download mfastboot and redownload the recovery img
Click to expand...
Click to collapse
Thanks.
Decided to install it on my desktop. While trying various files, my laptop accidentally got hit with Chromium virus. It looked like all required files were there, but kept having problems with a couple of those sdk files (tools/platform tools).
I'm still getting the following error:
( bootloader) has-slot :recovery: not found
And once again the Android SDK Tools and Android SKD Platform-tools that are under Tools (preview channel) are unchecked. Not sure if they are needed.
Follow the instructions of how to install on the general section
hetor99 said:
Follow the instructions of how to install on the general section
Click to expand...
Click to collapse
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
L8Show said:
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
Click to expand...
Click to collapse
How to Install TWRP Recovery and Root MOTO E
https://www.youtube.com/watch?v=9Jh-O2LGL3Y
OK, it is done.
Took a couple days with several hours of clicking, and checking settings, and reading and researching, and watching videos, and downloading, and installing/uninstalling, and restarting, but it's now rooted! Way too much time wasted even though it was raining and the gf and I were just watching movies for a lot of it. She kept asking me why I'd waste so much time and remind me I had a perfectly fine iphone nearby. Today I finally got to the point where I had given up. I figured something was screwed up with the phone after that reset on my computer.
Some highlights that may or may not be helpful for the next moto e rooter:
USB debugging was somehow switched to off a few times after I turned it on. Might have been after resetting phone, but who knows exactly.
I set screen to stay while connected via USB.
I removed all the apps I could and took out the sd card.
Kingoroot stuck at 66% many, many times, and then phone would restart. Research showed it may be accessing the wrong ADB instance or something. So I uninstalled SDK, fastboot, Minimal, etc. Anywhere it could have been hiding. Even did a system restore to last week the day I reinstalled windows. Didn't help one bit. Which is to also say... there are a half dozen or more legit options. Try different ones if you are relatively confident you followed directions the 1st 10 times.
Ministro didn't have moto e in their data base.
Finally back to XDA after checking a dozen videos (I have to admit I was completely dumbfounded and was mad at the whole process). I found XDA Kingroot and right away it worked, but it needed permission to allow apps that were not certified or some thing. I can see how people would think this is so easy. If I had started with this, I'd never have had to ask for help here. Btw, was this my problem all along? Did I miss that in the instructions or was it something else possibly? I don't remember if I did that before since it was 3 days ago.
So far I am thoroughly impressed with the this moto e. I paid $40 for it on a whim and now that I can remove a bunch of bloatware and customize it a bit, I think it may be a good gateway into android devices.
Thanks for looking and all your suggestions.
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
faheyd said:
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
Click to expand...
Click to collapse
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
L8Show said:
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
Click to expand...
Click to collapse
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
-z3r0- said:
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
Click to expand...
Click to collapse
Thanks for that information. I thought I saw adb devices command working in fastboot mode in one of the videos so I thought that was the problem. I thought adb needed to root the phone.
In order of what I've done with the phone so far:
Sent/got codes and unlocked moto e.
Turned on developer options and USB debugging.
Was then unable to get TWRP or the other cw something to work using the command fastboot flash recovery (file name) or fastboot boot... commands.
Gave up and installed Kingroot and everything worked fine.
Decided to try to install TWRP and superSU since kingroot had worked. I read that the phone needed to be flashed back to stock to do this and watched/read a couple of guides. http://forum.xda-developers.com/showthread.php?t=2759495
I used the following named file:
SURNIA_ACG_LTE_5.1_LPI23.29-30_cid9_subsidy-DEFAULT_CFC
The phone was changed back, but data doesn't work. I can't access wifi because as soon as I switch it on, it switches back off. 4G, etc is not working either. So after trying to figure that out I decided to just proceed and put TWRP/superSU on the phone.
I powered off the phone. Powered into fastboot mode connected the phone to my computer.
I opened Minimal fastboot folder and shift/right click to bring up the command prompt.
In the command promt i typed fastboot devices and it shows my phone.
I then type fastboot flash recovery (file name or renamed to recovery or renamed to TWRP or I click the actual file and drag it to the command prompt) and then hit enter.
It says it's doing stuff in so many seconds, but after nothing happens. The phone doesn't reset like some of the videos. If I reset it, it powers on, but not into the TWRP screen.
After that I did more reading and found out that adb doesn't always play nice with windows 8.1 and that you might need to force other drivers to make it work right. I did this next and was going to try all the available options from universal naked driver later, but there were no motorola drivers.
Then I came here and learned something new. ADB devices command doesn't work when the phone is in fastboot mode so that has no effect on installing twrp...
Right now I am considering trying to install the other stock files I have access to:
SURNIA_ACG_LTE_5.1_LPI23.29-20_cid9_subsidy-DEFAULT_CFC (20 instead of 30).
After that I am out of ideas if it's not the adb problem. Might kingroot again and go from there.
Ok after researching, it seems that LTE file may not work on sprint and there was success using the boost file from
http://www.filefactory.com/file/6be...XI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml.zip
(2 hour dl make that 5+ lol)
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'll try that next to get the wifi working and then figure out why it won't root.
Thx!
L8Show said:
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Click to expand...
Click to collapse
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
---------- Post added at 05:30 AM ---------- Previous post was at 05:29 AM ----------
rakeshwipr said:
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
Click to expand...
Click to collapse
and open the command prompt with admin rights
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
d
Thanks! The devices shows up when on as ADB and in fastboot too. I had to take a break when the kernel download took 8 hours, but I think I got the file that will work to fix the wifi issue. I can't mess with it til I get home tomorrow, but I will read and follow all advice.
For the previous poster, I did do the admin rights and did rename TWRP file to recovery... I aslo tried many other combinations, but will keep it in mind for all further attempts.
Appreciate the help so far. I almost left it with the kingroot, but it was bugging me that I couldn't get it to go. Hopefully I'll have good new tomorrow.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
Device shows up in both instances.
It's stock now and the wifi works. Flashed it back to stock by following Mdkcheatz guide here:
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'm stuck where I was when I first started this thread. I've set my account up as administrator. Developer is enabled and so is USB debugging. I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
I confirmed the connection:
fastboot devices
I try to flash it with the:
fastboot flash recovery recovery.img
It says:
target reported max download size of 268435456 bytes
sending 'recovery' (6928 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.359s]
finished total time: 0.578s
C: |Program Files (x86)\Minial ADB and Fastboot>
I'm running windows 8.1 (64 bit). I read that some people had had problems with windows 8. Kingroot worked through the app store. It has been flashed with various stock kernels and that usually takes a few minutes so I don't think it's doing much in half a second. I'll research a bit more, but I think it just a bad combination of this version phone and windows 8.1.
I started the phone after this last attempt. Are there any files in internal storage that I should look for?
L8Show said:
I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
Click to expand...
Click to collapse
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
-z3r0- said:
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
Click to expand...
Click to collapse
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
L8Show said:
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
Click to expand...
Click to collapse
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
-z3r0- said:
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
I am on v2.65. Should I use this version? I checked root and it's rooted, but I needed to use no bloat app (instead of free titanium) to remove some apps. Is that normal? I thought once rooted and set up, I would have complete control. Some apps seem very invasive so I haven't grabbed many yet. I have some questions about apps, etc., but will probably research and ask in another forum if needed.
Thx again for all the help and pointing out my mistake.
Hey guys, i need your help
I've unlocked the bootloader the unofficial way and now i want to go back.
I tried to flash the fastboot 7.1.8.0 global stable in edl mode according to this guide:
*sorry, not allowed to post outside links*
The max buffer size error occured, i followed the steps, replaced the files and wanted to flash again, now the error "error: receiving hello packet" occurs...
I'm stuck in edl mode right now and i cant flash. what to do now?
Thanks in advance!
//edit: okay it looks like the flash process was not completed, so i could get into fastboot and then "fastboot reboot". previous rom is still booting, what the hell ...
Try rebooting into edl mode again and flash back the rom
neme2k said:
Hey guys, i need your help
I've unlocked the bootloader the unofficial way and now i want to go back.
I tried to flash the fastboot 7.1.8.0 global stable in edl mode according to this guide:
*sorry, not allowed to post outside links*
The max buffer size error occured, i followed the steps, replaced the files and wanted to flash again, now the error "error: receiving hello packet" occurs...
I'm stuck in edl mode right now and i cant flash. what to do now?
Thanks in advance!
//edit: okay it looks like the flash process was not completed, so i could get into fastboot and then "fastboot reboot". previous rom is still booting, what the hell ...
Click to expand...
Click to collapse
Hi gus! have you solved your problem
Provide me your solution please, i'm in the same situation now with my Redmi note 3 Dual Sim
@mofazar
Hi,
Have you tried to reboot your computer? If you're not, then just try to reboot it without disconnecting your device.
And then just try it again.
Thanks.
karkand said:
@mofazar
Hi,
Have you tried to reboot your computer? If you're not, then just try to reboot it without disconnecting your device.
And then just try it again.
Thanks.
Click to expand...
Click to collapse
already try this step but still same error.
Windows must be 64bit (windows 7 or later),connect your phone to rear usb ports. In my case this was the problem (same error as yours).
Sent from my Redmi Note 3 using Tapatalk
I've the same problem. There is a solution? I've the virtualisation of Windows 7 64bit on linux, i don't know if this is the problem or not.
Got the solution....
I got the solution for all xiaomi users...
You just have to factory reset the device an then you are ready to go
if your device doesn't start then go to the fastboot menu and open cmd in the pc after connecting the phone to the pc...
then follow my steps
1. go to the adb folder.......
2. Then hold shift and right click there and click on "Open Command Prompt Here" it will open cmd .
3. The check if the device is detected or not if not the go to device manager and update the driver...
to check type : fastboot devices
4. then type fastboot -w it will wipe your whole data and do not start the phone firstly just flash the stock rom and then turn it on...
5. hurray i hope your problem will be solved.....
Thank you............
So, i installed Xposed, and like many people, i got stuck in the logo... No big deal there... Went to look for some help, and it said to go to fastboot, so I went, but it got stuck in the fastboot logo. Then I connected it to the computer and when I try to list the ADB devices I Ialways get an error saying the server is outdated...
I really need some help! I can't find anything online to help me!
Thanks in advance!
Edit: I submitted a bootloader unlock request to Xiaomi earlier today, but I can't see if its approved or not because phone doesn't work
well,
if you are in fastboot mode then the command is "Fastboot Devices", Not "adb Devices"
_____________________________________________
and about boot loop problem try to flash miui fastboot rom.
_____________________________________________
And about bootloader request problem you can go to edl mode and flash miui without any permissions
Thanks:good::good:
nishant2222 said:
well,
if you are in fastboot mode then the command is "Fastboot Devices", Not "adb Devices"
_____________________________________________
and about boot loop problem try to flash miui fastboot rom.
_____________________________________________
And about bootloader request problem you can go to edl mode and flash miui without any permissions
Thanks:good::good:
Click to expand...
Click to collapse
I tried, but i cant seem to go to edl mode through fastboot, any tips? and because of bootloader lock i cant flash fastboot rom with MI Flash
Edl mode needs a specific fastboot version.
For the Redmi Note 3 Pro / Special Edition
Download and extract this package on your PC.
Enter fastboot mode by holding Power and Vol- at the same time. Wait until the Mi Bunny appears, then connect the phone to the PC.
Run reboot.bat in the extracted package. A command prompt will appear. Press a key to reboot the phone to EDL mode.
Upon entering EDL mode, the screen should turn blank. The notification LED might be blinking red. Done.
To get out of EDL mode, hold the Power button for about 10 seconds.
Click to expand...
Click to collapse
Above quote taken from xiaomi reddit wiki.
If the above doesn't work, see the link for deep flash cable, shouldn't be need for kenzo/kate.
How you flashed/installed xposed on locked bootloader is another question?
You may need to update your adb/fastboot version + device drivers(adb)
corkiejp said:
Above quote taken from xiaomi reddit wiki.
If the above doesn't work, see the link for deep flash cable, shouldn't be need for kenzo/kate.
How you flashed/installed xposed on locked bootloader is another question?
You may need to update your adb/fastboot version + device drivers(adb)
Click to expand...
Click to collapse
Ok, so when i try to reboot in edl, it just reboots as normal after screen goes blank...
I installed Xposed with an APK
Sorry if i'm being annoying, but I just want this fixed
KaiZix said:
Ok, so when i try to reboot in edl, it just reboots as normal after screen goes blank...
I installed Xposed with an APK
Sorry if i'm being annoying, but I just want this fixed
Click to expand...
Click to collapse
Mate, watch any video on YouTube. You're not understanding from text instructions.
AtomR said:
Mate, watch any video on YouTube. You're not understanding from text instructions.
Click to expand...
Click to collapse
Can't find any... Recommendations?
EDL Mode: - https://www.youtube.com/watch?v=LDGViyDYPbU
If you can't get into EDL mode, you may need to use the deep flash cable method.
corkiejp said:
EDL Mode: - https://www.youtube.com/watch?v=LDGViyDYPbU
If you can't get into EDL mode, you may need to use the deep flash cable method.
Click to expand...
Click to collapse
I can't get into EDL mode, and I can't make/buy a deep flash cable... I'm getting really scared now...
About ADB, how can I fix it?
KaiZix said:
I can't get into EDL mode, and I can't make/buy a deep flash cable... I'm getting really scared now...
About ADB, how can I fix it?
Click to expand...
Click to collapse
Installing Mi Flash should have put the correct drivers on your PC.
But can be got from here: - https://xiaomifirmware.com/downloads/download-pc-drivers-xiaomi-redmi-note-3/
And I already linked adb/fastboot tools.
IF your comfortable opening your device, there is also a test point method you could try.
http://en.miui.com/thread-244814-1-1.html
Could not find a English video, so maybe try googling more and you might find one.
If not, you could ask at local repair shop, if they would fix it for you. Using Cable/ TP method.
Note for other readers:- MIUI roms need a special version of xposed, for it to work. And installing from an app would more than likely would have use the wrong version. Should never be done on a locked bootloader, only asking for trouble. (Rovo89 is currently trying to bring MIUI support to the official version for nougat roms)
Hello friends,
Apologies if I posted in wrong section.
I successfully installed Lineage 8.1 (along with gapps) on my Redmi Note 4 and is working perfectly fine (without any crashes/hangs for last couple of days. But there're some issues like
1) I tried to install TWRP multiple ways but it doesn't enter TWRP recovery mode on its own (when I press volume down+power) but instead it always stuck up at "Fastboot". So I use laptop to do that job every time I want to go TWRP recovery mode, by running 2 command at "cmd prompt" from laptop (this method works fine) =
fastboot flash recovery recovery.img
fastboot boot recovery.img
IF I try to install TWRP using xiomitool it throws "Error 1006: The device is offline or unauthorized" but from cmd prompt I see device list with "adb command" without any issue.
How can I solve this issue to make my phone to TWRP (without using laptop) when I press "vol-down + power"?
2) Now that I'm running custom ROM 8.1 on my redmi note 4, how to update it regularly, Does it get updates on its own OR should I manually download Lineage 8.1 updates/apply them?
3) I did NOT root my device and am not interested to do that unless its of great advantage. Please advise if I should do that. If yes, which method is the best one (Magiks/Supersu etc.)
Thanks!
prvnrk said:
Hello friends,
Apologies if I posted in wrong section.
I successfully installed Lineage 8.1 (along with gapps) on my Redmi Note 4 and is working perfectly fine (without any crashes/hangs for last couple of days. But there're some issues like
1) I tried to install TWRP multiple ways but it doesn't enter TWRP recovery mode on its own (when I press volume down+power) but instead it always stuck up at "Fastboot". So I use laptop to do that job every time I want to go TWRP recovery mode, by running 2 command at "cmd prompt" from laptop (this method works fine) =
fastboot flash recovery recovery.img
fastboot boot recovery.img
IF I try to install TWRP using xiomitool it throws "Error 1006: The device is offline or unauthorized" but from cmd prompt I see device list with "adb command" without any issue.
How can I solve this issue to make my phone to TWRP (without using laptop) when I press "vol-down + power"?
2) Now that I'm running custom ROM 8.1 on my redmi note 4, how to update it regularly, Does it get updates on its own OR should I manually download Lineage 8.1 updates/apply them?
3) I did NOT root my device and am not interested to do that unless its of great advantage. Please advise if I should do that. If yes, which method is the best one (Magiks/Supersu etc.)
Thanks!
Click to expand...
Click to collapse
So basically your doing wrong press volume up+ power for twrp recovery
And best method for root is Magisk
mbangi said:
So basically your doing wrong press volume up+ power for twrp recovery
And best method for root is Magisk
Click to expand...
Click to collapse
Silly me Yes volume up+power worked
Thanks for your reply.
Could anyone please reply on "Now that I'm running custom ROM 8.1 on my redmi note 4, how to update it regularly, Does it get updates on its own OR should I manually download Lineage 8.1 updates/apply them?"
prvnrk said:
Silly me Yes volume up+power worked
Thanks for your reply.
Could anyone please reply on "Now that I'm running custom ROM 8.1 on my redmi note 4, how to update it regularly, Does it get updates on its own OR should I manually download Lineage 8.1 updates/apply them?"
Click to expand...
Click to collapse
You have to install manually
And updates are weekly basis
mbangi said:
You have to install manually
And updates are weekly basis
Click to expand...
Click to collapse
Could you please provide me the link/location from where I can get download the updates manually? Thanks!!
prvnrk said:
Could you please provide me the link/location from where I can get download the updates manually? Thanks!!
Click to expand...
Click to collapse
https://download.lineageos.org/mido