Related
Hi everyone
I've just received my Honor 8 and I would like to root it without installing TWRP (or any other recovery than stock one) to receive further OTAs.
Is there any way? I tried Kingroot but did not work.
Thanks
I haven't tried this, but you should be able to do a systemless install of TWRP, root the phone, then re-install the stock recovery.
Hi, thank you for your answer.
I tried this. I reinstalled stock recovery (found in a UPDATE.APP file). But now, my device fails to do OTAs.
Does it notify you they're available, but fail to install? Or is it not seeing any updates?
I haven't been able to do much experimentation because there's not TWRP backup for my L04 yet, and I don't want to leave myself in a bad state without a restore option. I'm probably going to hold off on any updates (I'm on b140 now) until I have a fully working TWRP.
I had a notification and, when it did reboot, it failed. Now, it doesn't see any update. I am on b101.
Finally, I downloaded frd-L09c432b120 from here.
I followed these instructions: (http://forum.xda-developers.com/showpost.php?p=68695798&postcount=2)
DigiGoon said:
Steps are below, follow them.
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
...
Click to expand...
Click to collapse
I stopped there!
Rebooted my phone (no wipe done) and got a notification for an update.
The update succeeded (I'm now on B120).
But now, bootloader is locked again. So, it will wipe my phone when I will root it (locking bootloader first). So, I'm really looking for a solution to get OTAs on a rooted phone. Even if I will have to root it again, but without loosing lock on bootloader.
Isn't it possible to disable the device encryption so that you can avoid having to wipe it every time?
evilpaul13 said:
Isn't it possible to disable the device encryption so that you can avoid having to wipe it every time?
Click to expand...
Click to collapse
How can I do this?
Florent06 said:
Finally, I downloaded frd-L09c432b120 from here.
I followed these instructions: (http://forum.xda-developers.com/showpost.php?p=68695798&postcount=2)
Flash all other extracted files similarly firing these commands.
...
I stopped there!
Rebooted my phone (no wipe done) and got a notification for an update.
The update succeeded (I'm now on B120).
But now, bootloader is locked again. So, it will wipe my phone when I will root it (locking bootloader first). So, I'm really looking for a solution to get OTAs on a rooted phone. Even if I will have to root it again, but without loosing lock on bootloader.
Click to expand...
Click to collapse
I suggest to not do any OTA's. For all we know, an OTA can make it harder to root.
The thing might not work with a new official release is the recovery. And looking to other devices that has not been the case.
Just don´t encrypt the phone as it makes much harder to update. Also might mess up the timed on/off function.
Rooting without TWRP must be really hard.
Sent from my honor 5X using XDA Labs
I know only one way of rooting without twrp and that is to use KingRoot or a similar app/software.
It messes up the phone pretty bad and makes it a headache to get OTA in the future.
muradulislam said:
I know only one way of rooting without twrp and that is to use KingRoot or a similar app/software.
It messes up the phone pretty bad and makes it a headache to get OTA in the future.
Click to expand...
Click to collapse
Well root itself will cripple OTA updates. Using Kingroot is really not recommended due to compatibility issues. So SuperSU is the best choice.
Sent from my honor 5X using XDA Labs
adriansticoid said:
Well root itself will cripple OTA updates. Using Kingroot is really not recommended due to compatibility issues. So SuperSU is the best choice.
Click to expand...
Click to collapse
I should have highlighted HEADACHE in the above post. With SuperSU or magisk, it's super easy to enable/get OTA again but not the same with KingRoot.
And the bootloader unlocked by KingRoot has to be unlocked again, using official method, to be able to flash desired images for a complete unroot.
muradulislam said:
I should have highlighted HEADACHE in the above post. With SuperSU or magisk, it's super easy to enable/get OTA again but not the same with KingRoot.
And the bootloader unlocked by KingRoot has to be unlocked again, using official method, to be able to flash desired images for a complete unroot.
Click to expand...
Click to collapse
I once rooted my father's Honor Holly with Kingroot. Damn. Never again. Haha.
Sent from my honor 5X using XDA Labs
adriansticoid said:
I once rooted my father's Honor Holly with Kingroot. Damn. Never again. Haha.
Click to expand...
Click to collapse
Messed up partitions didn't it?
Tmobilefan906 said:
Messed up partitions didn't it?
Click to expand...
Click to collapse
Yes! I rooted it with Kingroot and tried to flash a custom recovery through Flashify. The recovery partition got corrupted and I can't flash anything to it anymore.
adriansticoid said:
Yes! I rooted it with Kingroot and tried to flash a custom recovery through Flashify. The recovery partition got corrupted and I can't flash anything to it anymore.
Click to expand...
Click to collapse
You can fix it
I think i can help you
You should use FRAMAROOT
link to download this is given below :
https://framarootappdownload.net/;);)
Tmobilefan906 said:
You can fix it
Click to expand...
Click to collapse
How?
Sent from my honor 5X using XDA Labs
---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------
kbhatia1 said:
You should use FRAMAROOT
link to download this is given below :
https://framarootappdownload.net/;);)
Click to expand...
Click to collapse
Framaroot isn't updated anymore.
Sent from my honor 5X using XDA Labs
Here's a stupid question(s). How do we backup the stock firmware, and are the fastboot commands for ADB?
---------- Post added at 02:00 PM ---------- Previous post was at 01:41 PM ----------
Is this systemless root?
Darkscan said:
Here's a stupid question(s). How do we backup the stock firmware, and are the fastboot commands for ADB?
---------- Post added at 02:00 PM ---------- Previous post was at 01:41 PM ----------
Is this systemless root?
Click to expand...
Click to collapse
Adb = Android debug bridge and is used when the phone is booted into the OS and connected to a PC
Fastboot = when the phone is booted into the bootloader and is connected to a PC
Yes it is systemless root
You can backup stock firmware with twrp RC1
Sent from my Pixel using Tapatalk
joetheshmo said:
Adb = Android debug bridge and is used when the phone is booted into the OS and connected to a PC
Fastboot = when the phone is booted into the bootloader and is connected to a PC
Yes it is systemless root
You can backup stock firmware with twrp RC1
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Why is the current version for TWRP and the previous not? Is the bootloader download mode?
Darkscan said:
Why is the current version for TWRP and the previous not? Is the bootloader download mode?
Click to expand...
Click to collapse
Current version of root for twrp and the previous not? If that's what you're asking SuperSU was developed before a working twrp was released so we had to use the boot-to-root.img
I guess bootloader mode could be considered download mode but I've never heard it called that.
Sent from my Pixel using Tapatalk
joetheshmo said:
Current version of root for twrp and the previous not? If that's what you're asking SuperSU was developed before a working twrp was released so we had to use the boot-to-root.img
I guess bootloader mode could be considered download mode but I've never heard it called that.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
I come from using only Samsung devices, I'm not sure what carries over and what doesn't. The extent of my experience is loading a ROM with download mode and flashing it with recovery. Speaking of which, why does the stock recovery just say no command when I try to launch it from fastboot?
Darkscan said:
I come from using only Samsung devices, I'm not sure what carries over and what doesn't. The extent of my experience is loading a ROM with download mode and flashing it with recovery. Speaking of which, why does the stock recovery just say no command when I try to launch it from fastboot?
Click to expand...
Click to collapse
Because you have to hit power button and volume up at the same time to get the commands to show up now
Sent from my Pixel using Tapatalk
joetheshmo said:
Because you have to hit power button and volume up at the same time to get the commands to show up now
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Well that's silly.
Darkscan said:
Here's a stupid question(s). How do we backup the stock firmware, and are the fastboot commands for ADB?
Click to expand...
Click to collapse
Why would you need to back-up the stock firmware? It is available here: https://developers.google.com/android/images
efrant said:
Why would you need to back-up the stock firmware? It is available here: https://developers.google.com/android/images
Click to expand...
Click to collapse
I suppose "where can we download the stock image" was the real question. Thanks.
Should I flash to stock first? I don't see why it would matter. All I've done is update Android and install a couple apps.
Darkscan said:
I suppose "where can we download the stock image" was the real question. Thanks.
Should I flash to stock first? I don't see why it would matter. All I've done is update Android and install a couple apps.
Click to expand...
Click to collapse
No need.
Would this be an acceptable way for me to downgrade my version? I am currently 100% stock and would like to downgrade so I can root, install TWRP, and start flashing custom ROMs.
This thread is like the twilight zone.
chadhoard said:
Would this be an acceptable way for me to downgrade my version? I am currently 100% stock and would like to downgrade so I can root, install TWRP, and start flashing custom ROMs.
Click to expand...
Click to collapse
Verizon phone? If you are on 7.1.1 you are done.
Google phone? You don't need to downgrade to do any of that.
Hi there,
I tried to flash the patched boot.img and it bricked my phone, I managed to fix it by flashing the official boot.img. Now, I REALLY want full access root, so does someone know what needs to be altered in the boot.img for this to work? I want to alter my boot.img from my firmware.
Tigas001 said:
Hi there,
I tried to flash the patched boot.img and it bricked my phone, I managed to fix it by flashing the official boot.img. Now, I REALLY want full access root, so does someone know what needs to be altered in the boot.img for this to work? I want to alter my boot.img from my firmware.
Click to expand...
Click to collapse
Hey Tigas,
some users are able to get full root with this patched boot.img from this post:
raimondomartire said:
For kindly request in MAte 9 thread
https://www.androidfilehost.com/?fid=529152257862700042 ---> Patched Mate 9 image. Use only supersu.apk to see root (Don't flash any zip with supersu before)
https://www.androidfilehost.com/?fid=529152257862700052 ---> Clean mate 9 image to patch with my zip in first thread
Click to expand...
Click to collapse
Unfortunately, this method using SuperSU will break your fingerprint/PIN protection.
If you want to try, simply flash the patched img over the stock img (in TWRP) and install SuperSU from the Play store.
Tigas001 said:
Hi there,
[skipped]
Now, I REALLY want full access root...
Click to expand...
Click to collapse
Do you have option to restore your device in case of hardbrick? Obtaining full root on Mate 9 must be done with knowledge what are you doing and what tools are doing...
There is full root. Here are the steps for the regular Mate 9
1) Download TWRP 3.0.2-2 from here and fastboot flash it:
https://www.androidfilehost.com/?fid=745425885120697579
2) Boot into TWRP (volume up+power) Go to Wipe, Format Data, then type in yes. Then reboot recovery.
3) Flash my decrypted boot.img from here:
https://www.androidfilehost.com/?w=files&flid=152685
4) Flash Superuser from here:
https://www.androidfilehost.com/?fid=817550096634746024
5) Boot up fully. Go into the Play Store and download PHH Superuser. Or you can download the newer beta here. Install it like any other apk:
https://www.androidfilehost.com/?fid=673368273298931027
6) Congratulations, you no longer are encrypted, twrp will see your internal storage and data properly and you have full root. Now do a backup of your current rom in TWRP.
ajsmsg78 said:
There is full root. Here are the steps for the regular Mate 9
1) Download TWRP 3.0.2-2 from here and fastboot flash it:
https://www.androidfilehost.com/?fid=745425885120697579
2) Boot into TWRP (volume up+power) Go to Wipe, Format Data, then type in yes. Then reboot recovery.
3) Flash my decrypted boot.img from here:
https://www.androidfilehost.com/?w=files&flid=152685
4) Flash Superuser from here:
https://www.androidfilehost.com/?fid=817550096634746024
5) Boot up fully. Go into the Play Store and download PHH Superuser. Or you can download the newer beta here. Install it like any other apk:
https://www.androidfilehost.com/?fid=673368273298931027
6) Congratulations, you no longer are encrypted, twrp will see your internal storage and data properly and you have full root. Now do a backup of your current rom in TWRP.
Click to expand...
Click to collapse
Just to discuss.
Steps 2 and 3 can be merged, if using modified script changes.sh inside of superuser.zip.
Sure, flashing decrypted boot does not require clean stock boot, so we have right boot before installing superuser
But on other side there will be unexpected problems if we will use prepared boot.
I noticed that boot images are different by version. One has additional code to thermal sensors, other doesn't.
Hi also wanted to clarify that this boot image can be flashed on any regular mate 9 and any firmware. Or is it only for a specific version of mate 9 with the same firmware as the boot.img. Thanks for any advice
Sent from my MHA-L09 using XDA-Developers Legacy app
Hi just to update I followed the instructions by ajsmsp78 and gained full root and was able to install meefik busybox and also uninstall system apps which I couldn't do before. When I flashed the boot.img and superuser and booted up some of my apps were missing. I then flashed the public and hw zips for my region and most of them were back. I now have decrypted data and full root. Thanks a lot
Sent from my MHA-L09 using XDA-Developers Legacy app
ajsmsg78 said:
There is full root. Here are the steps for the regular Mate 9
1) Download TWRP 3.0.2-2 from here and fastboot flash it:
https://www.androidfilehost.com/?fid=745425885120697579
2) Boot into TWRP (volume up+power) Go to Wipe, Format Data, then type in yes. Then reboot recovery.
3) Flash my decrypted boot.img from here:
https://www.androidfilehost.com/?w=files&flid=152685
4) Flash Superuser from here:
https://www.androidfilehost.com/?fid=817550096634746024
5) Boot up fully. Go into the Play Store and download PHH Superuser. Or you can download the newer beta here. Install it like any other apk:
https://www.androidfilehost.com/?fid=673368273298931027
6) Congratulations, you no longer are encrypted, twrp will see your internal storage and data properly and you have full root. Now do a backup of your current rom in TWRP.
Click to expand...
Click to collapse
so is that means we can backup n restore thru twrp??
---------- Post added at 03:11 PM ---------- Previous post was at 03:11 PM ----------
JATCHUHAN said:
Hi just to update I followed the instructions by ajsmsp78 and gained full root and was able to install meefik busybox and also uninstall system apps which I couldn't do before. When I flashed the boot.img and superuser and booted up some of my apps were missing. I then flashed the public and hw zips for my region and most of them were back. I now have decrypted data and full root. Thanks a lot
Click to expand...
Click to collapse
did you tried to back up n restore in twrp?
If I flash that boot.img it will brick my phone, I've tried it and had to flash the original boot.img as of now I have the phh superuser root. The flash method I used was fastboot and yes, I have my bootloader unlocked. Been rooting android phones for 5 - 6 years
Do I really need to wipe the data partition? Will the fingerprint sensor remain working?
eddmecha said:
so is that means we can backup n restore thru twrp??
Click to expand...
Click to collapse
Yeah, you can. When you are formatting data, encryption is going off. Then need use modified boot to prevent encryption back.
---------- Post added at 06:00 PM ---------- Previous post was at 05:57 PM ----------
Tigas001 said:
Do I really need to wipe the data partition? Will the fingerprint sensor remain working?
Click to expand...
Click to collapse
Not really need. If you are interesting only root and writeable system, then don't format data.
Can't say anything about fingerprint sensor - I never used it.
I haven't tried backing up in twrp yet. Will do so later today. When I flashed the public and hw zips all my huawei apps came back but not the extra bloat like Facebook or todoist etc. Not to bothered as I don't need them. The only thing missing was the magazine lock wallpapers but I downloaded replacements from the theme app. All good now. Thanks
Sent from my MHA-L09 using XDA-Developers Legacy app
---------- Post added at 03:27 PM ---------- Previous post was at 03:17 PM ----------
Tigas001 said:
If I flash that boot.img it will brick my phone, I've tried it and had to flash the original boot.img as of now I have the phh superuser root. The flash method I used was fastboot and yes, I have my bootloader unlocked. Been rooting android phones for 5 - 6 years
Do I really need to wipe the data partition? Will the fingerprint sensor remain working?
Click to expand...
Click to collapse
I also flashed that boot.img previously and bricked my phone. However this time it worked, the only thing I did different was to wipe data in twrp. Don't know if this made any difference but it worked
Sent from my MHA-L09 using XDA-Developers Legacy app
---------- Post added at 03:35 PM ---------- Previous post was at 03:27 PM ----------
Sent from my MHA-L09 using XDA-Developers Legacy app
If you don't wipe data first to decrypt and then flssh the decrypted boot you'll probably end up in a bootloop. I'll have to make a decrypted boot thread with a few different boot images for those still on older systems (B112, B029 etc)
Thanks that would be great and very helpful to others
Sent from my MHA-L09 using XDA-Developers Legacy app
Someone state that one of the root methods broke the finger print scanner, does this method from @ajsmsg78 correct that issue? And is there any other side effects or "broke" items after the process?
phillymade said:
Someone state that one of the root methods broke the finger print scanner, does this method from @ajsmsg78 correct that issue? And is there any other side effects or "broke" items after the process?
Click to expand...
Click to collapse
Fingerprint works fine for me after rooting.
Have you tried android pay? TiBU works without issues? Any chance OTA updates could still work? Thanks.
For all models...?
Just to be clear; which model do you have? Would the boot.img work for all models? I have the AL00.
ajsmsg78 said:
There is full root. Here are the steps for the regular Mate 9
1) Download TWRP 3.0.2-2 from here and fastboot flash it:
https://www.androidfilehost.com/?fid=745425885120697579
2) Boot into TWRP (volume up+power) Go to Wipe, Format Data, then type in yes. Then reboot recovery.
3) Flash my decrypted boot.img from here:
https://www.androidfilehost.com/?w=files&flid=152685
4) Flash Superuser from here:
https://www.androidfilehost.com/?fid=817550096634746024
5) Boot up fully. Go into the Play Store and download PHH Superuser. Or you can download the newer beta here. Install it like any other apk:
https://www.androidfilehost.com/?fid=673368273298931027
6) Congratulations, you no longer are encrypted, twrp will see your internal storage and data properly and you have full root. Now do a backup of your current rom in TWRP.
Click to expand...
Click to collapse
xfive420 said:
Have you tried android pay? TiBU works without issues? Any chance OTA updates could still work? Thanks.
Click to expand...
Click to collapse
I don't use Android pay but the fingerprint scanner works fine so far for me after rooting. OTA should work fine but I need confirmation of it working by someone.
rbt001 said:
Just to be clear; which model do you have? Would the boot.img work for all models? I have the AL00.
Click to expand...
Click to collapse
I have the MHA-L29C567 US version. I made a boot image thread you can go to for a link to the different boot images.
5[Strogino] said:
Yeah, you can. When you are formatting data, encryption is going off. Then need use modified boot to prevent encryption back..
Click to expand...
Click to collapse
Are you saying that if you just flash superuser to gain root but do not decrypt, you can't do backups and restores with TiBU? And remove system apps? I was under the impression from another thread that decrypting was only necessary for TWRP data access, and would not prevent TiBU features from working.
deleted sorry wrong thread
I was using Mokee without any issue. earlier last week i tried Lineage OS and t was not loading it was just showing boot animation.
I tried to get Mokee back but it ended up with the same issue. Also on other OS. I tried with Android 6 OS and it loaded up but without SIM detection and sometimes no WIFI as well. Please Help!! Urgent
Jseven123 said:
I was using Mokee without any issue. earlier last week i tried Lineage OS and t was not loading it was just showing boot animation.
I tried to get Mokee back but it ended up with the same issue. Also on other OS. I tried with Android 6 OS and it loaded up but without SIM detection and sometimes no WIFI as well. Please Help!! Urgent
Click to expand...
Click to collapse
Are you using things that were made specifically for your model number redmi note 3? Or are you flashing things that were made for a different model number than yours?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Are you using things that were made specifically for your model number redmi note 3? Or are you flashing things that were made for a different model number than yours?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I am using the ones specific to my model. Lineage OS, Mokee, RR etc.. All seem to be stuck in boot animation
Jseven123 said:
I am using the ones specific to my model. Lineage OS, Mokee, RR etc.. All seem to be stuck in boot animation
Click to expand...
Click to collapse
Have you tried using the advanced wipes to wipe system partition and data partition before you flash, then flash ROM+Gapps, then do the normal wipes(factory reset, wipe cache and wipe Dalvik/ART cache), then reboot?
The advanced wipes I'm talking about are not the normal wipes (factory reset, wipe cache and dalvik/ART cache) that are usually done when flashing ROMs.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Have you tried using the advanced wipes to wipe system partition and data partition before you flash, then flash ROM+Gapps, then do the normal wipes(factory reset, wipe cache and wipe Dalvik/ART cache), then reboot?
The advanced wipes I'm talking about are not the normal wipes (factory reset, wipe cache and dalvik/ART cache) that are usually done when flashing ROMs.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yes i have completely removed even the internal, Copied the zip file to the phone and flashed . Still bootloop. Never had this issue before
U need to unlock bootloader
lululul said:
U need to unlock bootloader
Click to expand...
Click to collapse
I have unlocked bootloader long back. Without that you cant have TWRP to install Custom OS. I need experts please
Jseven123 said:
I am using the ones specific to my model. Lineage OS, Mokee, RR etc.. All seem to be stuck in boot animation
Click to expand...
Click to collapse
What is your model number? Are you sure the ROMs you are flashing are for your specific model number? I'm not asking if they were made for Redmi Note 3, I'm asking if they were built specifically for your specific model number.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 01:34 PM ---------- Previous post was at 01:29 PM ----------
Jseven123 said:
I have unlocked bootloader long back. Without that you cant have TWRP to install Custom OS. I need experts please
Click to expand...
Click to collapse
You will get experts, we just have to establish exactly what you have or haven't done and then figure out what you messed up, then we can help you fix this.
You can't just come and say
"I flashed "this" ROM or "that" ROM but it won't work"
There is a lot more to it than that. We need more information to understand exactly where your issue is, then you'll get an expert answer.
Are you sure that the Gapps you're flashing is the correct ones for your device? Have you tried flashing a smaller Gapps package? The one you used might not be correct for your hardware or might be too big to fit in your system partition. These are common causes of bootloop, especially considering the fact that all of your ROMs so far have bootlooped, are you flashing the same Gapps with each of those ROMs? If so, that could possibly explain your bootloop.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
What is your model number? Are you sure the ROMs you are flashing are for your specific model number? I'm not asking if they were made for Redmi Note 3, I'm asking if they were built specifically for your specific model number.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 01:34 PM ---------- Previous post was at 01:29 PM ----------
You will get experts, we just have to establish exactly what you have or haven't done and then figure out what you messed up, then we can help you fix this.
You can't just come and say
"I flashed "this" ROM or "that" ROM but it won't work"
There is a lot more to it than that. We need more information to understand exactly where your issue is, then you'll get an expert answer.
Are you sure that the Gapps you're flashing is the correct ones for your device? Have you tried flashing a smaller Gapps package? The one you used might not be correct for your hardware or might be too big to fit in your system partition. These are common causes of bootloop, especially considering the fact that all of your ROMs so far have bootlooped, are you flashing the same Gapps with each of those ROMs? If so, that could possibly explain your bootloop.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I have clean wiped everything and downloaded the official custom rom for my Redmi Note 3 and I have tried installing with/without GAPPS. Same issue. If i am not wrong , it boots android v6 and not v7(assuming) since i am using my miui 8 again. and it loaded RR v6 for me but i never had this issue before I was able to to put any Custom Rom. I use Pico GAPP btw.
Jseven123 said:
I have clean wiped everything and downloaded the official custom rom for my Redmi Note 3 and I have tried installing with/without GAPPS. Same issue. If i am not wrong , it boots android v6 and not v7(assuming) since i am using my miui 8 again. and it loaded RR v6 for me but i never had this issue before I was able to to put any Custom Rom. I use Pico GAPP btw.
Click to expand...
Click to collapse
Either you've got something really strange going on or its something in the ROMs. Given that the issue is present with more than one ROM, I doubt it's a ROM issue. Have you looked through the Redmi Note 3 threads to see if anyone has had the same issue? It is probably some setting you changed or some mod that you applied before you tried the new ROMs, what that could be, I don't know.
I know you said you did a full wipe but strangely, sometimes settings/variables that were changed in one ROM causes issues when flashing other ROMs and it doesnt wipe that changed setting. I've exprienced this myself on my Galaxy S3 when going from one ROM to another even with full wipes.
Can I get a link to the ROM or ROMs you're having issues with?
Sent from my SM-S903VL using Tapatalk
https://download.lineageos.org/kenzo
https://download.mokeedev.com/?device=kenzo
If you give me links from unlocking bootloader to installation of OS, I will give a try again for the last time. ( No phone OS=no contacts/calls r= people worried )
Jseven123 said:
https://download.lineageos.org/kenzo
https://download.mokeedev.com/?device=kenzo
If you give me links from unlocking bootloader to installation of OS, I will give a try again for the last time. ( No phone OS=no contacts/calls r= people worried [emoji14] )
Click to expand...
Click to collapse
I'm not finding anything there that would tell me what other users are experiencing with this ROM. Have you tried contacting the developers to see if they understand your issue?
Sent from my SM-S903VL using Tapatalk
---------- Post added at 12:05 PM ---------- Previous post was at 11:54 AM ----------
Jseven123 said:
https://download.lineageos.org/kenzo
https://download.mokeedev.com/?device=kenzo
If you give me links from unlocking bootloader to installation of OS, I will give a try again for the last time. ( No phone OS=no contacts/calls r= people worried [emoji14] )
Click to expand...
Click to collapse
This should be your unlock method
http://xiaomitips.com/guide/unlock-redmi-note-3-bootloader/
Download this TWRP file:
https://dl.twrp.me/kenzo/twrp-3.1.0-0-kenzo.img.html
Use these instructions to flash TWRP (use the TWRP file you downloaded above instead of the one from this guide, also, find and download the newest version of SuperSU.zip and use it with these instructions instead of the SuperSU.zip linked in this guide)
http://xiaomiadvices.com/install-twrp-recovery-root-redmi-note-3/
Then you should be ready to flash your ROMs.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
I'm not finding anything there that would tell me what other users are experiencing with this ROM. Have you tried contacting the developers to see if they understand your issue?
Sent from my SM-S903VL using Tapatalk
---------- Post added at 12:05 PM ---------- Previous post was at 11:54 AM ----------
This should be your unlock method
http://xiaomitips.com/guide/unlock-redmi-note-3-bootloader/
Download this TWRP file:
https://dl.twrp.me/kenzo/twrp-3.1.0-0-kenzo.img.html
Use these instructions to flash TWRP (use the TWRP file you downloaded above instead of the one from this guide, also, find and download the newest version of SuperSU.zip and use it with these instructions instead of the SuperSU.zip linked in this guide)
http://xiaomiadvices.com/install-twrp-recovery-root-redmi-note-3/
Then you should be ready to flash your ROMs.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Is SuperSu necessary ? I didn't install SuperSu
Jseven123 said:
Is SuperSu necessary ? I didn't install SuperSu
Click to expand...
Click to collapse
It is typical for users to root the device for the first time by flashing SuperSU via TWRP.
I suppose it isn't necessary if you're going to flash a custom ROM that has root built in, if the ROM doesn't gave root built in them you'll have to flash SuperSU.zip to root the device before or after flashing that ROM.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Either you've got something really strange going on or its something in the ROMs. Given that the issue is present with more than one ROM, I doubt it's a ROM issue. Have you looked through the Redmi Note 3 threads to see if anyone has had the same issue? It is probably some setting you changed or some mod that you applied before you tried the new ROMs, what that could be, I don't know.
I know you said you did a full wipe but strangely, sometimes settings/variables that were changed in one ROM causes issues when flashing other ROMs and it doesnt wipe that changed setting. I've exprienced this myself on my Galaxy S3 when going from one ROM to another even with full wipes.
Can I get a link to the ROM or ROMs you're having issues with?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Can I do this?? I want to install Lineage OS
Jseven123 said:
Can I do this?? I want to install Lineage OS
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
Jseven123 said:
Can I do this?? I want to install Lineage OS
Click to expand...
Click to collapse
If you do all the steps to get unlocked, TWRP and root installed then there shouldn't be an issue. Have you asked other members that have your device about anything about this? They would know if there were something extra that might have missed.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
If you do all the steps to get unlocked, TWRP and root installed then there shouldn't be an issue. Have you asked other members that have your device about anything about this? They would know if there were something extra that might have missed.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I got the confirmation to unlock but my i am getting COULDN’T VERIFY DEVICE” ERROR DURING BOOTLOADER UNLOCK PROCESS
What to do??
Jseven123 said:
I got the confirmation to unlock but my i am getting COULDN’T VERIFY DEVICE” ERROR DURING BOOTLOADER UNLOCK PROCESS
What to do??
Click to expand...
Click to collapse
I'm not familiar enough with your device to help you with that.
It might be because you've already made an unlock attempt before this and whatever you did then is interfering.
You need to look around in your device forum Q&A or find other users that have your device that have done what you are doing.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
I'm not familiar enough with your device to help you with that.
It might be because you've already made an unlock attempt before this and whatever you did then is interfering.
You need to look around in your device forum Q&A or find other users that have your device that have done what you are doing.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
One more thing, Do I need to install different firmware to install Lineage OS?
Hey, guys. So I've been messing with my phone all day after a soft brick after having BlissROM since Feb. Long story short, something with the ROM update and it messed with my phone. I wiped EVERYTHING thinking it would solve the problem. I was able to use the All-In-One tool to save my phone through the bootloader (Thank goodness!). I finally got it to boot up to stock this morning. I've been trying all morning to gain root, but once I do, I lose WiFi and Network connections. So my question is:
What is the most current version of TWRP and Magisk that will allow me to be on stock and have root without any problems?
This is my setup.
OnePlus 7 Pro
Android version: Android 10
Build: Oxygen OS 10.0.3.GM21AA (now updated to 10.3.1)
Model: GM1917
Unlocked OEM
Unlocked Bootloader
This is the method I am using to push TWRP though the bootloader.
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
These are the files that flash through adb/fastboot and lose Wifi and Network connectivity.
TWRP 3.3.1-79-guacamole-unified-Q: https://sourceforge.net/projects/ma...-guacamole-unified-Q-mauronofrio.img/download
Magisk v20.4: https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
Since I don't have any connectivity at this point, I attempt to flash BlissROM with the following steps.
BlissROM version that last worked for me: https://downloads.blissroms.com/BlissRoms/Q/guacamole/Bliss-v12.6-guacamole-OFFICIAL-20200425.zip
STEPS
Boot into recovery
Backup your current ROM
Perform a factory reset
Flash Bliss Rom
Reboot recovery
Flash OpenGapps--NANO PACKAGE!!
*Flash magisk* optional
Reboot to system
Also, as I've previously stated, I have attempted to flash BlissROM through TWRP and with root (without WiFi and Data), but it hangs on the boot screen. When I go to TWRP and try to reflash the ROM, it gives me the error "cannot mount storage". I follow the instructions as stated in the original post, so I figured it has to be something with the TWRP or Magisk versions not being compatible. Since that does not work, I have since flashed stock and am currently on that without problems. Any links to the most current TWRP/Magisk/rooting methods are greatly appreciated. And if someone could help with getting BlissROM back on my phone afterwards, that would be great. Thanks!
Pretty sure you need to update to 10.3.2 to get it working right.
Sent from my GM1915 using Tapatalk
mjdavis871 said:
Pretty sure you need to update to 10.3.2 to get it working right.
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
I just realized I could update past the first update. I figured it would update to the most recent version version after the flash back to stock, not that it would be incremental. Thank you so much for the heads up!
I have the most recent version of Magisk downloaded. What is the best for 10.3.2?
knightsriot said:
I just realized I could update past the first update. I figured it would update to the most recent version version after the flash back to stock, not that it would be incremental. Thank you so much for the heads up!
I have the most recent version of Magisk downloaded. What is the best for 10.3.2?
Click to expand...
Click to collapse
That I could not say for sure, but my guess is that it would work fine.
Sent from my GM1915 using Tapatalk
mjdavis871 said:
That I could not say for sure, but my guess is that it would work fine.
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
Got it. Does the same goes for TWRP? I read somewhere that the unofficial one might work better with Android Q (I'm assuming that's Android 10?)
I always use the unofficial version, works fine for me.
Sent from my GM1915 using Tapatalk
mjdavis871 said:
I always use the unofficial version, works fine for me.
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
Got it. Okay, so it looks like I'll be giving BlissROM one last shot!
Before I flash TWRP and Magisk, I looked on the Oneplus website for the 10.3.2 update and it looks like the most current posted is 10.3.1. Should I update to 10.3.2 for the latest ROMS, or will 10.3.1 work fine? If so, where can I find it?
I used the oxygen updater app to download the update and sideloaded it.
Sent from my GM1915 using Tapatalk
mjdavis871 said:
I used the oxygen updater app to download the update and sideloaded it.
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
So it looks like that didn't work. I got stuck on a bootloop again and had to revert back to stock.
I can't seem to find what the problem is. Here is what I am flashing:
TWRP 3.3.1-79-guacamole-unified-Q: https://sourceforge.net/projects/mau...o.img/download
Magisk v20.4: https://github.com/topjohnwu/Magisk/...gisk-v20.4.zip
This is the method I am using flash TWRP to the bootloader.
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
When I flash both of those, I lose Wifi and Network on my stock ROM. I'm assuming one of them is also the reason why I can't flash BlissROM.
You don't need to flash magisk before you flash the ROM, just twrp. I do know when I bootlooped, it was because I missed a step, usually because I didnt wipe data.
Follow the flash instructions step by step or you will for sure bootloop. Read them over and over until you think you have a grasp of how to flash the ROM.
You can always get back into fastboot by holding power and both volume keys...then you can reflash twrp and start over. No need to go back to stock unless you want to or need to.
Just make sure you follow the instructions step by step. This device is a bit different to flash from the devices I have used before ...so it took me a few tries to get it done right.
Sent from my GM1915 using Tapatalk
mjdavis871 said:
You don't need to flash magisk before you flash the ROM, just twrp. I do know when I bootlooped, it was because I missed a step, usually because I didnt wipe data.
Follow the flash instructions step by step or you will for sure bootloop. Read them over and over until you think you have a grasp of how to flash the ROM.
You can always get back into fastboot by holding power and both volume keys...then you can reflash twrp and start over. No need to go back to stock unless you want to or need to.
Just make sure you follow the instructions step by step. This device is a bit different to flash from the devices I have used before ...so it took me a few tries to get it done right.
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
I've been following the steps exactly as written. Take a look at step 5 on the TWRP thread. (https://forum.xda-developers.com/on...covery-unofficial-twrp-recovery-t3931322/amp/)
Install guide (Reccomended):
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line (if you want to have it permanently you should flash the installer)
5. If you will flash the installer and you are stock you need also to flash magisk or your phone will not boot again
6. Enjoy it
Click to expand...
Click to collapse
Furthermore, this is also reiterated in the BlissROM thread. https://forum.xda-developers.com/oneplus-7-pro/development/rom-blissroms-v11-9-t3957341/page138
Make sure you are rooted
Make sure you have a custom recovery installed
For Q-BETA- Make sure you are on Q firmware, is currently set to use OOS 10.3.0 Stable firmware- CLEAN INSTALL!!
Click to expand...
Click to collapse
I also noted that in that previous quote, having the original 10.0.3 I had installed shouldn't have cause any problems. I wiped data (factory reset) every time I flashed BlissROM, as it is the third step in the process.
The reason why I go back to stock using the all-in-one tool is because I don't have anything else to flash. The whole reason I even had a soft brick was because I tried to go back to stock after my BlissROM update and flashed a OTA from the oneplus site. I probably did that incorrectly, however. Idk how what sideload is or how it functions. So that all-in-one tool is my only safety net.