Related
I everyone!
I just tried to connect my Nexus 4 to my windows 8.1 laptop and the phone is not recognised by the PC. It gives me Code 43 error, I tried everything, form fresh driver install to cable change. I also tried on another W7 laptop and nothing pops up there. The phone charges but in Device Manager it is not listed under Google ADB devices but appears with an exclamation mark under USB controllers saying Device Descriptor Request Failed. I fear it is an hardware problem and RMA is the only option left. However, my phone is Rooted, Stock but with modified build.prop, with TW touch recovery and unlocked. Since I have no access to ADB I cannot use the Android SDK tools or anything to flash the factory img. Is there any way in which I could flash back the sock image and lock the bootloader via recovery only?
Thanks everyone :crying::crying:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was what I was thinking, however, the main issue would be locking the bootloader again
simms22 said:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Click to expand...
Click to collapse
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
c0sk said:
This was what I was thinking, however, the main issue would be locking the bootloader again
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
Click to expand...
Click to collapse
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
mrhiab said:
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
Click to expand...
Click to collapse
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
c0sk said:
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
Click to expand...
Click to collapse
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
efrant said:
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
Click to expand...
Click to collapse
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
c0sk said:
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
Click to expand...
Click to collapse
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
efrant said:
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
c0sk said:
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
Click to expand...
Click to collapse
The way you removed SuperSU must have not worked properly. (I've never tried doing it from the SuperSU settings.) In any case, there's nothing more you can do now, so might as well send it in for RMA.
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
gjjh25 said:
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
Click to expand...
Click to collapse
you will need to unlock to flash custom zip, but u can relock after
gjjh25 said:
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
Click to expand...
Click to collapse
Question - why? What do you want to root your phone for if not to use the wonderful tools of root. Why do you think fully rooting your phone will harm something. Locked or unlocked bootloader is not going to affect your phone. Rooted stock rom with recovery will not make it act funny.... Sorry not putting you out there but just asking why? Feel free to ignore me if you must...
Edit: Sorry to answer your question like the post above said you can root and then lock it right back up if that is your preference
playya said:
Question - why? What do you want to root your phone for if not to use the wonderful tools of root. Why do you think fully rooting your phone will harm something. Locked or unlocked bootloader is not going to affect your phone. Rooted stock rom with recovery will not make it act funny.... Sorry not putting you out there but just asking why? Feel free to ignore me if you must...
Edit: Sorry to answer your question like the post above said you can root and then lock it right back up if that is your preference
Click to expand...
Click to collapse
I have come from an HTC Desire, which I rooted and had a custom rom (Cyganonmod) on and was very happy with it.
I am still not sure of what I would gain by doing the same with my Nexus 4 ?
any advice is much appreciated.
Is this new Cyganonmod installer the best way to go?
gjjh25 said:
I have come from an HTC Desire, which I rooted and had a custom rom (Cyganonmod) on and was very happy with it.
I am still not sure of what I would gain by doing the same with my Nexus 4 ?
any advice is much appreciated.
Is this new Cyganonmod installer the best way to go?
Click to expand...
Click to collapse
This phone is built for rooting and modding. You wont know what benefit you have until you either read up and see if the mods are ones you want or actually flash a rom. Sure try the CM installer but if you dont toolkits or just basic knowledge of android can get this phone roooted in minutes.
the CM rom on your HTC will give you the same benefits on your Nexus 4
playya said:
This phone is built for rooting and modding. You wont know what benefit you have until you either read up and see if the mods are ones you want or actually flash a rom. Sure try the CM installer but if you dont toolkits or just basic knowledge of android can get this phone roooted in minutes.
the CM rom on your HTC will give you the same benefits on your Nexus 4
Click to expand...
Click to collapse
Thanks, what do you recommend for the easiest way to unlock and root then?
gjjh25 said:
Thanks, what do you recommend for the easiest way to unlock and root then?
Click to expand...
Click to collapse
I used a toolkit but honestly you can unlock manually by just booting into bootloader mode. Go into development and try Wugs Toolkit.... Rooting the phone is easy and all methods are relatively the same.
I do not see anything wrong with giving CM a try as well
gjjh25 said:
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
Click to expand...
Click to collapse
I recommend you to stick to your original plan, its your phone, do what you like, you don't need to flash custom roms if you don't want to. I am using stock kernel and stock KitKat right now and the performance is excellent.
Follow these instructions to unlock bootloader, install latest kitkat factory image, install custom TWRP recovery, and root. http://forum.xda-developers.com/showthread.php?t=2010312
The links to fastboot package and driver required is in my signature.
Link to download factory image: https://developers.google.com/android/nexus/images
Link for latest TWRP: TWRP recovery
Link for latest SuperSU package: SuperSU package
After you do all that, in bootloader menu, you can flash back the stock recovery (recovery.img), which is location in the "image-occam-******.zip" of the factory image. (fastboot flash recovery recovery.img)
Then lock your bootloader by "fastboot oem lock". You can also use BootUnlocker to lock and unlock your bootloader on the fly while in the phone, without losing your data, since everytime you do fastboot oem unlock, it will wipe the entire device.
By using stock rom, stock recovery, stock kernel and temporarily unroot (SuperSU) or hide root (SuperSU paid version), it allows you to receive future OTA updates from Google. If you want to modify your phones more while staying with stock, read up on Xposed Framework and its module Gravity Box, which is not yet compatible with Android 4.4 but will be eventually.
Just remember if you don't have custom recovery, once something goes wrong and your phone can't boot, its very hard to save the data inside. Once you have custom recovery like TWRP, you can make a backup of your stock image (which also backup your stock kernel) and try out other custom roms and easily go back to stock, then you can flash stock recovery again to receive OTA updates.
Thanks for advice everyone.
I rooted and unlocked with Wugfresh over the weekend. A lot easier than I thought it would be
Hey XDA,
My Nexus ha been a dream. Though I've hit a few bumps, I don't expect to waste money on other flagships again.
I don't need to be able to right this instant, but wiping cache is one of my regular troubleshooting tools. Upon troubleshooting an MMS issue I was having, I discovered my recovery wasn't working properly. Though I fixed the MMS issue by resetting APN settings, the recovery thing has been bothering me.
I am running stock and locked. I have done nothing to this phone to warrant it being my fault. The problem is simple (and a Google search indicated, common). When you get to Recovery, you get a droid on its back, a red exclamation mark and "NO COMMAND". Doesn't matter if you hold up and power, tap up, or get there from the bootloader. The recovery software is seemingly missing completely.
I have an extended warranty through the retailer I bought from, but the phone is otherwise fine, so this is a last resort.
My dilemma is that I want to use Android pay. My understanding is that even unlocking the bootloader breaks Android pay. Is this correct? If so, can one reliably reset the phones security trips to allow Android pay after flashing the recovery back on?
Thanks for the help.
No, unlocking the boot loader does not block Android Pay.
There is a systemless root method for the Nexus that allows you to use Android Pay while rooted, there are also a couple of ROMS that have it working currently as well.
celsian said:
No, unlocking the boot loader does not block Android Pay.
There is a systemless root method for the Nexus that allows you to use Android Pay while rooted, there are also a couple of ROMS that have it working currently as well.
Click to expand...
Click to collapse
Quite so? Can you provide links to the root method and mayhaps the roms? Does this mean I could slap TWRP on here with no consequence?
Android pay already patched systemless root. If you want Android pay don't root. You can unlock though. That will not affect Android pay.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Android pay already patched systemless root. If you want Android pay don't root. You can unlock though. That will not affect Android pay.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Does this mean that I can't flash at least a stock recovery?
Download your system image, unzip it, unlock your bootloader and flash only the recovery.IMG in fastboot, then relock your bootloader again. Android Pay will work fine and your warranty won't be affected so long as you relock your bootloader
Arcaed said:
Does this mean that I can't flash at least a stock recovery?
Click to expand...
Click to collapse
Yes. Myself I would flash full image and start over fresh. But you can go with just recovery if you want. Also do not forget to check allow oem unlock in dev settings before attempting to unlock. If you want twrp you will need modified stock boot image with DM verity removed. Or else it won't boot. I can link you to one from the newest image if you'd like. But if you only want stock recovery you don't need anything other than stock Google image.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Yes. Myself I would flash full image and start over fresh. But you can go with just recovery if you want. Also do not forget to check allow oem unlock in dev settings before attempting to unlock. If you want twrp you will need modified stock boot image with DM verity removed. Or else it won't boot. I can link you to one from the newest image if you'd like. But if you only want stock recovery you don't need anything other than stock Google image.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Sorry, but are you saying if I wanted to install twrp I would need a modified stock boot img?
The Stig 04 said:
Sorry, but are you saying if I wanted to install twrp I would need a modified stock boot img?
Click to expand...
Click to collapse
Yes.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Yes. Myself I would flash full image and start over fresh. But you can go with just recovery if you want. Also do not forget to check allow oem unlock in dev settings before attempting to unlock. If you want twrp you will need modified stock boot image with DM verity removed. Or else it won't boot. I can link you to one from the newest image if you'd like. But if you only want stock recovery you don't need anything other than stock Google image.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
In that case, where do I get a full system flash?
Arcaed said:
In that case, where do I get a full system flash?
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
Sent from my Nexus 6P using Tapatalk
There are quite a few errors in the information given in this thread.
1. Unlocking the bootloader does not break Android Pay.
2. Android Pay has been patched so you can't have root with Android Pay, even systemless.
3. TWRP recovery does not require a modified boot.img.
4. Flashing any recovery (Stock or TWRP) will not affect Android Pay at all.
If you need directions on unlocking or flashing check my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
There are quite a few errors in the information given in this thread.
1. Unlocking the bootloader does not break Android Pay.
2. Android Pay has been patched so you can't have root with Android Pay, even systemless.
3. TWRP recovery does not require a modified boot.img.
4. Flashing any recovery (Stock or TWRP) will not affect Android Pay at all.
If you need directions on unlocking or flashing check my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
You beat me to it with #3. Unfortunately I'm at work and couldn't come back to this thread quickly enough.
toknitup420 said:
Android pay already patched systemless root. If you want Android pay don't root. You can unlock though. That will not affect Android pay.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Actually AP now works with systemless root again. I have AP working (yes actually making purchases), currently running the latest Chroma Rom with Supersu 2.61
Found the workaround in this thread.
I'm sure Google will patch it again though.
Arcaed said:
Quite so? Can you provide links to the root method and mayhaps the roms? Does this mean I could slap TWRP on here with no consequence?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=65188325
Heisenberg said:
There are quite a few errors in the information given in this thread.
1. Unlocking the bootloader does not break Android Pay.
2. Android Pay has been patched so you can't have root with Android Pay, even systemless.
3. TWRP recovery does not require a modified boot.img.
4. Flashing any recovery (Stock or TWRP) will not affect Android Pay at all.
If you need directions on unlocking or flashing check my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I've always been under the impression that the device will not boot with twrp installed unless you have DM verity checks removed. Has something changed with that.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
I've always been under the impression that the device will not boot with twrp installed unless you have DM verity checks removed. Has something changed with that.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It isn't necessary. I'm on my eighth Nexus 6P and I haven't flashed any modified boot.img prior to flashing TWRP.
83097markcynt said:
Actually AP now works with systemless root again. I have AP working (yes actually making purchases), currently running the latest Chroma Rom with Supersu 2.61
Found the workaround in this thread.
I'm sure Google will patch it again though.
Click to expand...
Click to collapse
I can second this. I have systemless root, and AP working, confirmed with purchases. Just a note, if you can successfully add a card, that means it has to contact your bank for approval, therefore it should confirm AP is working.
What is the easiest way to completely reset my rooted android?
jdugery said:
What is the easiest way to completely reset my rooted android?
Click to expand...
Click to collapse
By reset do you mean restore it to "out of box" state? Then you need to restore your pre-root backup or flash stock via fastboot. But at this time locking the bootloader is not possible since we do not have the latest firmware, unless your device has older firmware installed (only the output of "fastboot getvar all" would tell us for sure)
acejavelin said:
By reset do you mean restore it to "out of box" state? Then you need to restore your pre-root backup or flash stock via fastboot. But at this time locking the bootloader is not possible since we do not have the latest firmware, unless your device has older firmware installed (only the output of "fastboot getvar all" would tell us for sure)
Click to expand...
Click to collapse
I just mean remove root and reset the phone so it is practically brand new. I don't care about locking the bootloader.
jdugery said:
I just mean remove root and reset the phone so it is practically brand new. I don't care about locking the bootloader.
Click to expand...
Click to collapse
What model xt15?? and version android do you have?
Twrp ver.?
Rooted with supersu or magisk?
Have you backup before rooting?
jdugery said:
I just mean remove root and reset the phone so it is practically brand new. I don't care about locking the bootloader.
Click to expand...
Click to collapse
Then you can chose the option that fit's best...
1) Unroot in the SuperSU app's Setting's menu with Full Unroot option. This will remove root but not restore the original recovery, most likely leaving TWRP in place, then boot into the bootloader, start recovery (TWRP most likely) and perform an advanced wipe including caches, user data, and internal storage
2) Boot into TWRP and restore your pre-root backup, then perform a factory reset. This may or may not remove TWRP depending on how you did the backup. If you booted TWRP and performed the backup, it should be essentially back to factory state including stock recovery, if you flashed TWRP first then backed up then TWRP will remain.
3) Restore to stock via fastboot with the latest factory image.
Your choice of which is most appropriate for your circumstances.
acejavelin said:
Then you can chose the option that fit's best...
1) Unroot in the SuperSU app's Setting's menu with Full Unroot option. This will remove root but not restore the original recovery, most likely leaving TWRP in place, then boot into the bootloader, start recovery (TWRP most likely) and perform an advanced wipe including caches, user data, and internal storage
2) Boot into TWRP and restore your pre-root backup, then perform a factory reset. This may or may not remove TWRP depending on how you did the backup. If you booted TWRP and performed the backup, it should be essentially back to factory state including stock recovery, if you flashed TWRP first then backed up then TWRP will remain.
3) Restore to stock via fastboot with the latest factory image.
Your choice of which is most appropriate for your circumstances.
Click to expand...
Click to collapse
I unrooted in SuperSU and wiped in TWRP but Snapchat still won't let me login. Root checker confirms I'm not rooted.
jdugery said:
I unrooted in SuperSU and wiped in TWRP but Snapchat still won't let me login. Root checker confirms I'm not rooted.
Click to expand...
Click to collapse
After you have unrooted, clear data on Snapchat and then log in again (or uninstall and reinstall Snapchat).
I don't use Snapchat or Whatsapp, but my understanding is that you have to login before you root... if you have tried to login, it remembers you were rooted until you clear data.
acejavelin said:
After you have unrooted, clear data on Snapchat and then log in again (or uninstall and reinstall Snapchat).
I don't use Snapchat or Whatsapp, but my understanding is that you have to login before you root... if you have tried to login, it remembers you were rooted until you clear data.
Click to expand...
Click to collapse
I did this still no luck. Apparently if you even have an unlocked bootloader you can't log into Snapchat. So I'm gonna have to lock my bootloader. Any ideas on the easiest method of doing that?
jdugery said:
I did this still no luck. Apparently if you even have an unlocked bootloader you can't log into Snapchat. So I'm gonna have to lock my bootloader. Any ideas on the easiest method of doing that?
Click to expand...
Click to collapse
Well, that shouldn't be it... but locking the bootloader is difficult depending on what version you are on now. The problem is you must flash a complete factory image to lock and we don't have the latest images.
jdugery said:
I did this still no luck. Apparently if you even have an unlocked bootloader you can't log into Snapchat. So I'm gonna have to lock my bootloader. Any ideas on the easiest method of doing that?
Click to expand...
Click to collapse
No I'm almost 99% positive that that's wrong you don't need a locked bootloader to log into snapchat? Where did you read this??
@acejavelin is extremely knowledgeable and will be able to help you with any problem you come across, but you should not need to lock bootloader...anything I find says snap blocks root...and safety net is tripped by an unlocked bootloader. The two don't go hand in hand though. Snapchat doesn't use safety net.
Edit: if you're able to make a backup of a snapchat that is logged in using Titanium backup, and then install that backup onto your phone. Don't know if you have an extra device around though. But really confused as to why reinstalling didn't even work? Is there a chance that the unroot option in superSU did not remove root fully??
acejavelin said:
Well, that shouldn't be it... but locking the bootloader is difficult depending on what version you are on now. The problem is you must flash a complete factory image to lock and we don't have the latest images.
Click to expand...
Click to collapse
Are you sure you don't need a locked bootloader to log into snapchat?
jdugery said:
Are you sure you don't need a locked bootloader to log into snapchat?
Click to expand...
Click to collapse
About 95% sure... Like I said, I don't use SnapChat, but to my knowledge the SafetyNet API doesn't check the bootloader status on Marshmallow devices, only on devices that shipped with Nougat (not that were upgraded).
There has to be some left-overs from root that are causing it to fail.
acejavelin said:
About 95% sure... Like I said, I don't use SnapChat, but to my knowledge the SafetyNet API doesn't check the bootloader status on Marshmallow devices, only on devices that shipped with Nougat (not that were upgraded).
There has to be some left-overs from root that are causing it to fail.
Click to expand...
Click to collapse
But I completely reset my device. Should I wipe everything in TWRP?
jdugery said:
But I completely reset my device. Should I wipe everything in TWRP?
Click to expand...
Click to collapse
I doubt it will help, but you can backup and try it... Most likely something is still in /system, you need to restore your pre-root backup for system and boot and wipe caches. If you don't have that backup then reflash the stock image.
acejavelin said:
I doubt it will help, but you can backup and try it... Most likely something is still in /system, you need to restore your pre-root backup for system and boot and wipe caches. If you don't have that backup then reflash the stock image.
Click to expand...
Click to collapse
Where can I find the stock image. And can I flash it using TWRP?
jdugery said:
Where can I find the stock image. And can I flash it using TWRP?
Click to expand...
Click to collapse
Hmm... maybe one of the links in my sig would help.
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
acejavelin said:
Hmm... maybe one of the links in my sig would help.
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Click to expand...
Click to collapse
Couldn't see your signature because I'm on mobile lol
But just wondering can I flash these using TWRP
jdugery said:
Couldn't see your signature because I'm on mobile lol
But just wondering can I flash these using TWRP
Click to expand...
Click to collapse
You can see a users signature and stats by tapping their icon.
No, they cannot be flashed in TWRP, must be done with fastboot.
acejavelin said:
You can see a users signature and stats by tapping their icon.
No, they cannot be flashed in TWRP, must be done with fastboot.
Click to expand...
Click to collapse
Finally that's how you do it!! Now I can see what the legend listens to for music?
Spencervb256 said:
Is there a chance that the unroot option in superSU did not remove root fully??
Click to expand...
Click to collapse
Yes it is.
Sometimes you need to flash stock/custom kernel. @jdugery
What is your version of system. Full numbers. Info about phone. 24...?
Hey
I have question about firmware flashing,
I am currently using pe and i want to go back miui
Am i need flash firmware before flashing miui
or just flashing miui enough ?
Download fastboot rom from miui website and install through fastboot
Visit this link for instructions
ammaralidj said:
Download fastboot rom from miui website and install through fastboot
Visit this link for instructions
Click to expand...
Click to collapse
Can i flash rom via twrp? Will it work ?
No fastboot roms for fastboot mode only and you will loose root. It means you need to reroot your device if you wish
TWRP is for custom roms only.
Ded Moroza said:
Hey
I have question about firmware flashing,
I am currently using pe and i want to go back miui
Am i need flash firmware before flashing miui
or just flashing miui enough ?
Click to expand...
Click to collapse
You can either do a clean flash with TWRP/ORANGE or do flash with MIFlashTool with Fastboot ROM. (Depends of what you want to keep or lose, eg. the bootloader unlocked) with Fastboot ROM it will reset and relock the bootloader (of course you can unlocked it again with unlock tool without problem), with MIUI recovery ROMS will be the same steps as flashing a custom ROM, it might re-write the stock recovery after the reboot but the bootloader will remain unlocked.
BlackGarnett said:
You can either do a clean flash with TWRP/ORANGE or do flash with MIFlashTool with Fastboot ROM. (Depends of what you want to keep or lose, eg. the bootloader unlocked) with Fastboot ROM it will reset and relock the bootloader (of course you can unlocked it again with unlock tool without problem), with MIUI recovery ROMS will be the same steps as flashing a custom ROM, it might re-write the stock recovery after the reboot but the bootloader will remain unlocked.
Click to expand...
Click to collapse
Is unlocked bootloader disadvantageous for an ordinary, blah phone ?
Should I flash via fastboot and lock bootloader ?
Ded Moroza said:
Is unlocked bootloader disadvantageous for an ordinary, blah phone ?
Should I flash via fastboot and lock bootloader ?
Click to expand...
Click to collapse
Some apps doesn't work properly, like Netflix for example.
If you're just using regular MIUI without root or any mods like magisk better leave it locked.
You don't have to lock the bootloader when using Miflashtool, just choose "Clean all" and not "Clean all and lock" at the bottom of the ui.
Gonime said:
Some apps doesn't work properly, like Netflix for example.
If you're just using regular MIUI without root or any mods like magisk better leave it locked.
Click to expand...
Click to collapse
Last question
While bootloader locked, can i flash twrp and magisk ?
CGA1 said:
You don't have to lock the bootloader when using Miflashtool, just choose "Clean all" and not "Clean all and lock" at the bottom of the ui.
Click to expand...
Click to collapse
Ok thanks but im gonna lock it
Ded Moroza said:
Last question
While bootloader locked, can i flash twrp and magisk ?
Click to expand...
Click to collapse
No, you can't when you lock bootloader you can't flash any recovery, etc.
BlackGarnett said:
No, you can't when you lock bootloader you can't flash any recovery, etc.
Click to expand...
Click to collapse
Alright thanks much
Ded Moroza said:
Last question
While bootloader locked, can i flash twrp and magisk ?
Click to expand...
Click to collapse
No, definitely not. Unless you want to brick your device.