Welcome Guest ( Log In | Register )

Bump Topic Topic Closed RSS Feed

Outline · [ Standard ] · Linear+

Xiaomi Xiaomi Redmi Note 3 Discussion V7, MIUI 8 Android 6 available now!

views
     
mastermindsos
post Oct 14 2016, 11:55 AM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


QUOTE(seanlss @ Oct 14 2016, 10:15 AM)
NEED HELP!!!

I failed to flash twrp recovery.
I already unlocked bootloader, follow the step by step in the guide.
however when i adb devices in cmd, the list of devices is empty.

Anyone can help?!!  cry.gif  cry.gif
*
Make sure you have already enabled usb debugging in developer option.
Then once you have plugged your phone to the pc, there will be a pop up message in your phone.
You must accept it, only then you will see the adb device when you run the command.
mastermindsos
post Nov 7 2016, 03:22 PM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


Need help.
Today I attempted to install twrp to my kenzo.
Adb devices is successful.
But the following step failed.
fastboot flash recovery recoveryAlkaUpdate.img
It says "waiting for any devices".

mastermindsos
post Nov 7 2016, 03:31 PM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


QUOTE(abubin @ Nov 7 2016, 03:26 PM)
have you unlocked the bootloader?
*
Yes, I did via official way and I believed it was successful.
Do you know any command to check this?
mastermindsos
post Nov 7 2016, 03:59 PM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


QUOTE(GameSky @ Nov 7 2016, 03:43 PM)
did you closed mi flash tool? or mi unlock tool? try reboot your computer and retry again.
*
I unlocked my phone a few weeks ago.
I will reboot my pc and try again.


QUOTE(patdidi @ Nov 7 2016, 03:55 PM)
boot phone into fastboot mode,
*
Yes, I went to fastboot mode once to test the "fastboot reboot" command.
It was successful.
But I did not try the fastboot flash recovery because the "steps" in the first page did not say that I have to go to fastboot mode.
Furthermore, while in fastboot mode, the adb command is not recognized (adb devices not working).
mastermindsos
post Nov 7 2016, 04:06 PM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


QUOTE(GameSky @ Nov 7 2016, 04:03 PM)
for flashing twrp you'll need to use fastboot mode. adb only works when phone is booted and usb debugging enabled.
*
I see, so inbetween these 2 steps below, I need to go to fastboot mode, correct?
5. You should see connected devices in the list.
5.1 Boot to fastboot mode
6. Then to flash twrp, type
mastermindsos
post Nov 7 2016, 04:21 PM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


QUOTE(GameSky @ Nov 7 2016, 04:16 PM)
you'll need to reboot your phone in fastboot mode, then use the command
CODE
fastboot flash recovery name.img

*
I did this just now. I guess it went fine.
But then when I used Vol Up + Power Button, I did not go into TWRP.
Instead I reached to a black page with a smartphone picture.
Any idea?

I ran
CODE
fastboot oem device-info
in fastboot mode, it showed device unlocked true.

Here is the steps I took.
user posted image

This post has been edited by mastermindsos: Nov 7 2016, 04:29 PM
mastermindsos
post Nov 7 2016, 05:15 PM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


QUOTE(patdidi @ Nov 7 2016, 04:58 PM)
try this,

after finished flashing custom recovery,
- do not boot the phone yet
- instead unplug the usb cable
- press and hold  vol+ and power button until device reboot. On Mi logo release power button until and release vol+ after it booted into  custom recovery.
*
Glad to report, your method works fine.
Thanks a lot.
mastermindsos
post Nov 7 2016, 08:11 PM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


QUOTE(patdidi @ Nov 7 2016, 06:37 PM)
Happy to help. Are planning on installing custom rom? I myself currently running resurrection remix rom.
*
Yes. Currently running Mokee
mastermindsos
post Nov 8 2016, 07:09 PM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


Anyone knows what could be the reason when fingerprint option not found in lock screen setting?
I am using mokee.
I saw others in XDA have the same issue in pac man rom but no one replies.
mastermindsos
post Nov 8 2016, 09:50 PM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


QUOTE(GameSky @ Nov 8 2016, 07:21 PM)
goodix sensor? tried flash cmradios zip? or was it firmware (get it from cm 13 by thestrix thread)
*
I tried just now, but my phone does not want to boot.
Stuck at "loading" screen for about 25 minutes.
I gave up and gave it a reboot to recovery and reflashed my rom again without goodix patch.

I am seeking clarification.
What does it means by rom requirement to have unlocked bootloader?
Is it required to install the rom or is it only required to install custom recovery(TWRP)?
Since I have TWRP installed, I no longer need the bootloader to be unlocked to install other roms right?
mastermindsos
post Nov 8 2016, 10:21 PM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


QUOTE(GameSky @ Nov 8 2016, 10:04 PM)
so use the fastboot oem info something (check first page) to see ur bootloader is locked or not.

also flashing which cm rom? santosh or thestrix?
*
I mean, after TWRP is installed, I can still install any other roms even if the booloader status is locked, correct?
mastermindsos
post Nov 9 2016, 09:05 AM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


QUOTE(GameSky @ Nov 8 2016, 11:03 PM)
never risked myself, incase bricked.
*
Ah I see.
Actually I accidentally did this.
My bootloader was locked again after installing mokee(or was it because of goodix I am not sure either).
Then I still proceed with installing mokee again and it was successful. hmm.gif

mastermindsos
post Nov 9 2016, 09:17 AM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


May I request if you could find some time to update/re-arrange the first page (Guides).
Some of them are duplicates, possibly old, confusing and redundant to newbies.
Thank you for your great work. notworthy.gif
mastermindsos
post Nov 17 2016, 10:13 PM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


QUOTE(matt_rix @ Nov 17 2016, 06:40 PM)
Seriously no one had scroll lag problem with latest chrome? I dont see anyone else complaining.

I have TWO redmi note 3 pro and i can duplicate the problem. Confirm caused by chrome version higher than 53.
*
Seriously,............................. I have.
I've noticed this around the same time when you report this problem.
I thought this was caused by MIUI.
So, I've changed my rom.
Now, it doesn't feel that much stuttering anymore.

mastermindsos
post Nov 17 2016, 11:56 PM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


QUOTE(matt_rix @ Nov 17 2016, 10:42 PM)
What rom u use now? I dont really want to get into changing rom as it will certainly affect the camera quality
*
Mokee
mastermindsos
post Nov 18 2016, 09:20 AM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


QUOTE(matt_rix @ Nov 18 2016, 12:25 AM)
do u like it so far?
*
Everything works except fingerprint(mine is goodix).
Can't comment on camera, i didn't test the camera on miui beforehand.
mastermindsos
post Nov 23 2016, 08:26 PM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


Wow, I just want to say I am very happy with custom rom running on android 7.1.
It is currently 2 days 20 hr but I still have more than 50% battery left.
Wifi and data always on.
I used the phone to read light novel.
Screen on time is currently 9h.


mastermindsos
post Nov 23 2016, 10:11 PM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


QUOTE(AMDAthlon @ Nov 23 2016, 08:43 PM)
You used which version of custom ROM? CM 14.1? AOSP?
How is the stability?
Im keen to try but has yet to find any stable rom yet for Nougat
*
I am currently using CleanRom.
But none of the Nougat roms are stable yet.
Sometimes the camera apps crashed, and also the torchlight too.
But if you can live with it, you may try.
mastermindsos
post Nov 26 2016, 07:25 PM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


As far as I am aware, bootloader status is not important as long as you have custom recovery installed.
mastermindsos
post Nov 27 2016, 01:51 PM

Casual
***
Junior Member
373 posts

Joined: Jan 2009


QUOTE(bizness @ Nov 27 2016, 03:18 AM)
Owh, so his issue has nothing to do with the bank then.

Mine previously when I changed from Umobile to DiGi, the bank require me to wait for 48hrs to refresh the number in their system. It's weird because it's the same number but dunno why they require to refresh the number.  hmm.gif
*
Well no worries there.
If you did not explain it first, I would have explained the same.

I've experienced that too in the past.
In my case, it was an issue with CIMB Clicks.
I contacted the CIMB customer support, explained them I have changed my telco and they "fixed" the issue right away.

2 Pages  1 2 >Top
Topic ClosedOptions
 

Change to:
| Lo-Fi Version
0.0231sec    0.27    7 queries    GZIP Disabled
Time is now: 5th December 2025 - 10:33 PM