HTC oneM9 Sprint - Downgrade / Can I downgrade directly from recovery twrp? - General Questions and Answers

Hello evebody!
So , I own a HTC one m9 Sprint, and last friday suddenlty restarts and after it reboots, my signal (carrier/network) was gone!
Everything else is working (Blutooth, Wifi, etc).
At that moment, the phone was stock rom Android Nougat
The actual state of the phone is:
*Unlock
*Custom recovery twrp
*Custom rom Nougat
So, my question is: Can I just install a rom based on Marshmallow directly to a Nougat (via Custom recovery twrp) phone in order to downgrade it?
I already check:
✓ IMEI is correct
✓ Sim (work in other cellphones)
✓ Carrier/network do not have a lock in to my number
Hope someone can take a lookor have any tip in order to recover the signal in my mobile .
Thank you very much in advance guys!:laugh:

FerZG said:
Hello evebody!
So , I own a HTC one m9 Sprint, and last friday suddenlty restarts and after it reboots, my signal (carrier/network) was gone!
Everything else is working (Blutooth, Wifi, etc).
At that moment, the phone was stock rom Android Nougat
The actual state of the phone is:
*Unlock
*Custom recovery twrp
*Custom rom Nougat
So, my question is: Can I just install a rom based on Marshmallow directly to a Nougat (via Custom recovery twrp) phone in order to downgrade it?
I already check:
✓ IMEI is correct
✓ Sim (work in other cellphones)
✓ Carrier/network do not have a lock in to my number
Hope someone can take a lookor have any tip in order to recover the signal in my mobile .
Thank you very much in advance guys!:laugh:
Click to expand...
Click to collapse
Unless you're running official Nougat, I don't think it will be an issue to downgrade to a custom marshmallow via TWRP.
You, however, can't downgrade to official Marshmallow from TWRP. You'll need stock recovery for that.
In case you're downgrading to a custom marshmallow rom i.e LOS 13/CM13, it's better to check the corresponding thread for installation instructions.

Nonta72 said:
Unless you're running official Nougat, I don't think it will be an issue to downgrade to a custom marshmallow via TWRP.
You, however, can't downgrade to official Marshmallow from TWRP. You'll need stock recovery for that.
In case you're downgrading to a custom marshmallow rom i.e LOS 13/CM13, it's better to check the corresponding thread for installation instructions.
Click to expand...
Click to collapse
Now it works, i was able to downgrade it to a custom Android 6 directly and it fix the carrier issue,thank you very much.

FerZG said:
Now it works, i was able to downgrade it to a custom Android 6 directly and it fix the carrier issue,thank you very much.
Click to expand...
Click to collapse
Glad it worked!

Related

[Solved]Need help,mess up with L09

[Solved] I had the l09-c636b191 official version no new ota updates with that version,
Then I did the following:
1.Download l09-c636b210 and install with dload method(works without problem)and download b321 and dload inst..(no problems).
Then I came up with the idea to install nougat beta,downlod l09c636b521:
2.Unlock bootloader and install twrp recovery and doo factory reset...
3.Flash update.zip(only that,it`s mistake,I did not know that need hw update_data.zip ) got errors during flashing after finish restart phone and phone boot with nougat...
4.First no kayboord only google voice,I went through anyway from setup,second many apps missing like clock...settings crashes,and THEMES NOT WORK,MAGAZIN UNLOCK does not exist no wallpapers.In about phone said test kay..
Then I decided to back on b321,then I realized that it was all because I did not flash data.zip(I did not have)
5.Back to b321 with dload and install phone boot and goot with Blinking screen asking for password,I switched off phone and boot in stock recovery doo factory reset after that phone on and setup start(with kayboord)...
6.On home screen the first thing I noticed icons and wallpaper are stock google no emui look,and go to change thames same problem no stock themes(any other not work) and unlock magazine does not exist no wallpapers.But is stable 6.0
I decided to try again to flash android 7.0,just this time with data.zip(download from one xda user)
7.I did everything like at the beginning 2.
Flash update.zip and hw_update.spsceas.zip got errors during installition,after finish installation,it was all the same no kayboord...etc
8.Back to b321 again with dload(this time no password or blinking screen)but is same like latest time themes not work ickons and wallpapers stock android.
Now system is stabile but not 100% have some bugs.
9.Try to register on Malesya beta test progaram for nougat I succeeded in that said got my ota update on december 31. But still no update in settings and notphing in hicare.
Need help for this,would like everything to be like when I bought the phone(system fully functional)
What I doo,any suggestion?
Thanks
Solved problem:
Unlock bootloader+install twpr+root
Go to srk tool,until and install hw_init.
Now themes and magazine unlock work agine,also new notification like sms,viber...tourn screen on when is locked.
interesting. i have L09 C636 (single sim 32GB model) too, in australia.
but not really keen to root yet, can i just unlock bootloader and then install nougat beta,downlod l09c636b521 ????
erwinsie said:
interesting. i have L09 C636 (single sim 32GB model) too, in australia.
but not really keen to root yet, can i just unlock bootloader and then install nougat beta,downlod l09c636b521 ????
Click to expand...
Click to collapse
Yes you cant install nougat without root,need to flash with twrp.Nougat for my not work good.I am nou on android 6.0 b321 emui 4.1
So you are staying away from Nougat ok

How to get Rooted, TWRP'd Sprint A9 to Nougat? (Edited)

(From later on in this thread)
Jaxas said:
Hello again, sorry to bother you guys but I'm seeing a surprising amount of conflicting information about this...
So I'm trying to upgrade to Nougat, but I'm having some troubles figuring out what I need to do for that.
I know I need to get my phone back to stock so I can accept the OTA update, but I'm not sure how to go about that.
My phone currently:
- Phone Model: HTC One A9 (Sprint - 2PQ93)
- Android Version: 6.0.1
- Software Version: 1.60.651.4
- Root: Yes
- Recovery: TWRP v2.8.8.2_CPTB-TEST2
- S: ON
- Bootloader: Unlocked
- Software Status: Modified
So as far as I'm aware, I need to restore the Stock recovery (how?), re-flash the RUU for my current software version, and then... relock the bootloader? Maybe?
So my questions are...
- How do I actually restore the stock recovery?
- Are there any steps I'm missing?
- Do I need to re-lock the bootloader, or does that not matter?
(- Is there anything I need to do once I get Nougat to root besides flash TWRP 3.0.3 & SuperSU through that?)
Thanks!
Click to expand...
Click to collapse
=============== ORIGINAL POST ===============
Hello,
I'm basically at my wit's end and I'd just like to see if anyone knows whether it's actually possible to get Android 7.0 Nougat on my phone?
I currently have a rooted, RUU-updated 6.0.1 build of Android (Version Number: 1.60.651.4) running on a Sprint (so CDMA) HTC One A9 (Model Number: 2PQ9300). My phone is still S-On (I'm willing to pay for Sunshine if it'll actually work for me, but I'd like to confirm that first), and due to the updating process I do not currently have TWRP - that's easily fixed, however.
Mostly, I'd just like to know if there's a way to get Android 7.0 on my phone, as it is not the International version, while also retaining things like mobile data and calling.
So far, I've looked into simply flashing the RUU (seems to be both not compatible with my phone version, and also has the signing issue mentioned Here), however with the signing issue I'd have to OTA update first so that's not relevant.
I've looked into Sunshine for S-OFF as well as This thread to convert to the "Unlocked" version that has the update, however I'm seeing comments about it not being compatible with the Sprint edition.
I've most recently tried to follow This guide, however I've had no luck and I'm still seeing talk of random reboots, dropped calls, and the like.
Basically, if there's any way I can get Android 7.0 Nougat on my phone, I would love to know how - if I can't (reasonably), then I'd also like to know that so I can stop beating my head into the wall, so to speak
Thanks!
Jaxas said:
Basically, if there's any way I can get Android 7.0 Nougat on my phone, I would love to know how - if I can't (reasonably), then I'd also like to know that so I can stop beating my head into the wall, so to speak
Thanks!
Click to expand...
Click to collapse
So far, the CDMA versions of the A9 can't run Nougat. As you know, HTC hasn't updated it for Nougat, and our phones run different enough firmware from the GSM-Locked and Dev versions that we can't use theirs. And so far, HTC's Dev Nougat requires Nougat firmware. So... we're boned.
Hopefully this won't be forever; HTC should eventually update American phones, so we'll just have to factory reset from system image (and maybe RUU) and OTA. For now, we can only hope guys like Captain_Throwback figure out how to backport Nougat to the 1.60.651.4 firmware.
Jaxas said:
Hello,
I'm basically at my wit's end and I'd just like to see if anyone knows whether it's actually possible to get Android 7.0 Nougat on my phone?
I currently have a rooted, RUU-updated 6.0.1 build of Android (Version Number: 1.60.651.4) running on a Sprint (so CDMA) HTC One A9 (Model Number: 2PQ9300). My phone is still S-On (I'm willing to pay for Sunshine if it'll actually work for me, but I'd like to confirm that first), and due to the updating process I do not currently have TWRP - that's easily fixed, however.
Mostly, I'd just like to know if there's a way to get Android 7.0 on my phone, as it is not the International version, while also retaining things like mobile data and calling.
So far, I've looked into simply flashing the RUU (seems to be both not compatible with my phone version, and also has the signing issue mentioned Here), however with the signing issue I'd have to OTA update first so that's not relevant.
I've looked into Sunshine for S-OFF as well as This thread to convert to the "Unlocked" version that has the update, however I'm seeing comments about it not being compatible with the Sprint edition.
I've most recently tried to follow This guide, however I've had no luck and I'm still seeing talk of random reboots, dropped calls, and the like.
Basically, if there's any way I can get Android 7.0 Nougat on my phone, I would love to know how - if I can't (reasonably), then I'd also like to know that so I can stop beating my head into the wall, so to speak
Thanks!
Click to expand...
Click to collapse
hey,
can you try this ...
https://forum.xda-developers.com/one-a9/general/htc-one-a9-android-7-nougat-t3546557
New info: Nougat is now available via OTA. Now we just need to... get back to full stock.
Woo! Just saw the notification. So now the question is if TWRP will work with 7.0 on our phones.. I think I'd rather keep root than upgrade and lose it if there's a choice.
JohnRogers23 said:
Woo! Just saw the notification. So now the question is if TWRP will work with 7.0 on our phones.. I think I'd rather keep root than upgrade and lose it if there's a choice.
Click to expand...
Click to collapse
TWRP 3.0.3 beta is available for nougat
MGfusion said:
TWRP 3.0.3 beta is available for nougat
Click to expand...
Click to collapse
I saw, but I'm not sure what's going on in the thread right now. It seems it sometimes bootloops? I'm hesitant to upgrade until there's either an RUU for 2.whatever out or I'm sure TWRP is reliable. I'm resigning myself to living without Xposed, but I at least need root and Magisk.
JohnRogers23 said:
Woo! Just saw the notification. So now the question is if TWRP will work with 7.0 on our phones.. I think I'd rather keep root than upgrade and lose it if there's a choice.
Click to expand...
Click to collapse
Whelp.
I'm upset, lol.
Time to re-reset my phone (finally got it set back up the way I wanted it yesterday on 6.0.1)
Oh well, thanks for the heads up!
I have the Sprint a9. I flashed the ruu and flashed TWRP 3.0.3-1 I believe, with no issues
Okay, so before I go re-wipe my phone and upgrade, I have a few quick questions...
1) Can this update be flashed with S-ON? (I'm assuming so, but always good to check) and
2) Can the Sprint A9 be rooted on Nougat yet?
Thanks!
I used TWRP 3.0.3.-4 and root with Magisk. Still miss Xposed, but the N features are pretty nice too. All seems to be working well.
Hello again, sorry to bother you guys but I'm seeing a surprising amount of conflicting information about this...
So I'm trying to upgrade to Nougat, but I'm having some troubles figuring out what I need to do for that.
I know I need to get my phone back to stock so I can accept the OTA update, but I'm not sure how to go about that.
My phone currently:
- Phone Model: HTC One A9 (Sprint - 2PQ93)
- Android Version: 6.0.1
- Software Version: 1.60.651.4
- Root: Yes
- Recovery: TWRP v2.8.8.2_CPTB-TEST2
- S: ON
- Bootloader: Unlocked
- Software Status: Modified
So as far as I'm aware, I need to restore the Stock recovery (how?), re-flash the RUU for my current software version, and then... relock the bootloader? Maybe?
So my questions are...
- How do I actually restore the stock recovery?
- Are there any steps I'm missing?
- Do I need to re-lock the bootloader, or does that not matter?
(- Is there anything I need to do once I get Nougat to root besides flash TWRP 3.0.3 & SuperSU through that?)
Thanks!
Jaxas said:
So as far as I'm aware, I need to restore the Stock recovery (how?), re-flash the RUU for my current software version, and then... relock the bootloader? Maybe?
So my questions are...
- How do I actually restore the stock recovery?
- Are there any steps I'm missing?
- Do I need to re-lock the bootloader, or does that not matter?
(- Is there anything I need to do once I get Nougat to root besides flash TWRP 3.0.3 & SuperSU through that?)
Thanks!
Click to expand...
Click to collapse
If you don't have an unmodified system image from before you mounted the system partition then yes, you do have to use an RUU, which will also give you stock recovery. No, you don't need to do anything with the bootloader.
Flash the RUU for the version you're on now, start up normally and take the OTA. No, I didn't have to do anything special besides making double checking /system is mounted read-only in TWRP. Personally I like using Magisk for root, etc, but I've heard SuperSU works fine. too. I'm S-on as well and it was all very easy.
I have a modified htc one a9 sprint, i want to get back to fully stock so i can update my device by using RUU side load. Please help
samweli benjamin said:
I have a modified htc one a9 sprint, i want to get back to fully stock so i can update my device by using RUU side load. Please help
Click to expand...
Click to collapse
What is your CID, MID and version-main? Is your bootloader locked or unlocked? S-ON or S-OFF?
I have attached a screenshot of getvar all for my device, when i was attemping to update it by using RUU its status was LOCKED and S-OFF but currently its status is **RE-LOCKED** and S-OFF
samweli benjamin said:
I have attached a screenshot of getvar all for my device, when i was attemping to update it by using RUU its status was LOCKED and S-OFF but currently its status is **RE-LOCKED** and S-OFF
Click to expand...
Click to collapse
What ruu version were you trying to flash and what was the error?
It was RUU_HIA_AERO_WHL_N70_SENSE80GP_SPCS_MR_Sprint_WWE_2.18.651.2 and the ERROR that I received was SIGNARURE ERROR: 132
samweli benjamin said:
It was RUU_HIA_AERO_WHL_N70_SENSE80GP_SPCS_MR_Sprint_WWE_2.18.651.2 and the ERROR that I received was SIGNARURE ERROR: 132
Click to expand...
Click to collapse
You can't flash a nougat ruu (2.xx.xxx.x) on a phone running the marshmallow firmware (1.xx.xxx.x). You need to manually update your firmware to 2.xx.651.x before being able to flash the 2.18.651.2 RUU. This is because the new signature key implemented in all 2.xx.xxx.x ruu, explained here at faq #4
Or you can flash the older 1.60.651.4 ruu and after, update your phone using OTA updates. Probably the easiest way for you :good:
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.60.651.4.exe
This seems to be of great help to me, but am afraid i can't install the OTA in my device, b'se I received it and i did downloaded it but when i click to install it finish unzipping file and then fail and the phone boots in TWRP recovery so i thought i can update it by running a RUU side load

Inquiry about OPPO R7plusf update!

Hi guys,
I hope all of you are fine, now after more than one year of usage of OPPO R7Plusf which was really amazing, it seems like OPPO has no plans to upgrade our phones, when I purchased my device a ColorOS version 2.0 was installed already and recently, it was upgraded to ColorOS version 2.1.0i (based on 5.1.1 Android Lollipop). Nowadays, all of us heard about the Nougat upgrade when we still dreaming with Marshmallow!!
So please, any suggestions for a custom ROM (tested) to upgrade my OPPO phone to Nougat version with no usual known errors or bugs. I will be grateful.
Notice: I contacted both customer support (the local one and the international) and I received the usual formal disappointed answer: "we will inform you when the update is available", which I think it will not be.
So thanks
Anybody here!?
Depends what you like
I currently use Resurrection remix on mine however there are some issues with apps force closing is my main one. Lineage OS also had issues for me with bluetooth causing the phone the reboot over and over. CM 13 was the best but I can't find any download links for it any more (rip CM) I think they both have updates coming outside but I recommend trying some out and then making a decision. Also if your phone is on one of the latest oppo updates (one of the 2016 updates) you'll have to downgrade to a 2015 software as they locked the bootloader so you won't be able to root! It's easy to do just find an old firmware from the internet (I would post links but I can't, also has to be a 2015 one) turn off the phone and turn it back on whilst holding down the volume down button and then go install and install the old firmware and then follow any guides on the internet for installing custom ROMs
Hope this helped
Meroslave said:
Anybody here!?
Click to expand...
Click to collapse
Lol, yeah. There is not much traffic here, but the R7Plusf is still awesome and up to date. Mainly due to good people at LineageOS keeping the device fresh.
I don't have serious issues with AICP on Nougat. No reboots. It is build "on top of" LineageOS, but have more features plus a working theming system. Latest build uploaded today.
Try RR, AICP and LineageOS and see what you like. Wait with Lineage untill the next release (current is Feb 14), if you want to avoid reboots.
ccrocks426 said:
I currently use Resurrection remix on mine however there are some issues with apps force closing is my main one. Lineage OS also had issues for me with bluetooth causing the phone the reboot over and over. CM 13 was the best but I can't find any download links for it any more (rip CM) I think they both have updates coming outside but I recommend trying some out and then making a decision. Also if your phone is on one of the latest oppo updates (one of the 2016 updates) you'll have to downgrade to a 2015 software as they locked the bootloader so you won't be able to root! It's easy to do just find an old firmware from the internet (I would post links but I can't, also has to be a 2015 one) turn off the phone and turn it back on whilst holding down the volume down button and then go install and install the old firmware and then follow any guides on the internet for installing custom ROMs
Hope this helped
Click to expand...
Click to collapse
So, you recommend the CM13 in case it's available?
And what's the cons and pros?
teemo said:
Lol, yeah. There is not much traffic here, but the R7Plusf is still awesome and up to date. Mainly due to good people at LineageOS keeping the device fresh.
I don't have serious issues with AICP on Nougat. No reboots. It is build "on top of" LineageOS, but have more features plus a working theming system. Latest build uploaded today.
Try RR, AICP and LineageOS and see what you like. Wait with Lineage untill the next release (current is Feb 14), if you want to avoid reboots.
Click to expand...
Click to collapse
Sure I will try one of your recommendations, but all I was afraid of was the disappointed bugs after updat such as battery drain, camera errors, wifi issues ... etc. Of course my ColorOS became boring to me, but still stable with no errors
Any pros or cons for those above I will be great full
Meroslave said:
Sure I will try one of your recommendations, but all I was afraid of was the disappointed bugs after updat such as battery drain, camera errors, wifi issues ... etc. Of course my ColorOS became boring to me, but still stable with no errors
Any pros or cons for those above I will be great full
Click to expand...
Click to collapse
Battery drain on MM has improved compared to Lollipop and N has improved over MM. With 4 email accounts running (on Aqua Mail) and Location on "High accuracy", Viber messenger and other stuff running, I had not much drain on AICP 11 (MM). Drain during night with Location on "Device" was 0.5% per hour. On MM and especially N, you have many ways in settings you can fine tune battery drain. Many apps are automatically shut down when not in use. You can decide which to limit and which to keep running when phone is off. Without extra apps (as ColorOS has), you can limit what apps are allowed to do and see. All built into the system.
A final word on drain: With Googles and others services running all the time, tracking everything you do, some drain is expected. Luckily this can be turned off by you
The number one reason to upgrade in these hacker friendly times: N is updated with much improved security. Updated every month with the latest security patches.
For me, AICP 11 is error free. The latest MM builds are complete in features and practically error free. Features are still being merged one at the time on N, but is useable as is now with only some minor issues.
I have not tried RR. My guess is that it has more features than AICP, but also more issues.
Lineage is the mother of all, I expect it to be stable with a good set of features.
All the N builds have more or less issues with speaker-phone. It may or may not bother you (or the person in the other end). MM was not affected as much as N, for some unknown reason.
I use Resurrection Rom and very happy with this rom!
i am beginer
i have oppo r7 plus f. tried the auto root tool but ended up hard bricking my phone. i am a beginer and i do not have much knowledge .
want to install lineage os on my oppo r7 plus f please tell me some easy ways.
Meroslave said:
Hi guys,
I hope all of you are fine, now after more than one year of usage of OPPO R7Plusf which was really amazing, it seems like OPPO has no plans to upgrade our phones, when I purchased my device a ColorOS version 2.0 was installed already and recently, it was upgraded to ColorOS version 2.1.0i (based on 5.1.1 Android Lollipop). Nowadays, all of us heard about the Nougat upgrade when we still dreaming with Marshmallow!!
So please, any suggestions for a custom ROM (tested) to upgrade my OPPO phone to Nougat version with no usual known errors or bugs. I will be grateful.
Notice: I contacted both customer support (the local one and the international) and I received the usual formal disappointed answer: "we will inform you when the update is available", which I think it will not be.
So thanks
Click to expand...
Click to collapse
supriyo_rana said:
i have oppo r7 plus f. tried the auto root tool but ended up hard bricking my phone. i am a beginer and i do not have much knowledge .
want to install lineage os on my oppo r7 plus f please tell me some easy ways.
Click to expand...
Click to collapse
Rana, first I'm sure you have been a good phone user and your Oppo R7 plus is upto date, unfortunately this is a problem. So first thing you need to do (Assuming you have unbricked your phone) is find a older version of the genuine R7+ firmware. Preferably some time between 2015- mid2016. The reason for this is OPPO locked the bootloader on later versions, these earlier versions are what the autoroot tool was designed to work on. Once you have this firmware, flash through recovery (provided you still have genuine OPPO recovery), if not you also need to flash this. Once you have the older firmware on your phone you should be able to proceed as usual steps to install lineage on your phone using typical walkthroughs.
what to do next?
DooganAU said:
Rana, first I'm sure you have been a good phone user and your Oppo R7 plus is upto date, unfortunately this is a problem. So first thing you need to do (Assuming you have unbricked your phone) is find a older version of the genuine R7+ firmware. Preferably some time between 2015- mid2016. The reason for this is OPPO locked the bootloader on later versions, these earlier versions are what the autoroot tool was designed to work on. Once you have this firmware, flash through recovery (provided you still have genuine OPPO recovery), if not you also need to flash this. Once you have the older firmware on your phone you should be able to proceed as usual steps to install lineage on your phone using typical walkthroughs.
Click to expand...
Click to collapse
thanks for your reply
yeah i went to the ofiicial service centre for the unbricking , noy it is working fine with letest firmware . now according to you i should downgrade the firmware . but how to do it ? should i do it via oppo stock recovery? or via the local update option of system updater in the menu?
supriyo_rana said:
thanks for your reply
yeah i went to the ofiicial service centre for the unbricking , noy it is working fine with letest firmware . now according to you i should downgrade the firmware . but how to do it ? should i do it via oppo stock recovery? or via the local update option of system updater in the menu?
Click to expand...
Click to collapse
i have the same concern also. Can someone please provide a step by step instruction on how to downgrade the firmware to the old version?
supriyo_rana said:
thanks for your reply
yeah i went to the ofiicial service centre for the unbricking , noy it is working fine with letest firmware . now according to you i should downgrade the firmware . but how to do it ? should i do it via oppo stock recovery? or via the local update option of system updater in the menu?
Click to expand...
Click to collapse
bu11et said:
i have the same concern also. Can someone please provide a step by step instruction on how to downgrade the firmware to the old version?
Click to expand...
Click to collapse
Try here: https://forum.xda-developers.com/showpost.php?p=73786100&postcount=139
unlock bootloader still stuck..
Hi Guys..
First i don't know if i am posting this in right thread or not... but I need help... after lots of search i couldn't find anything to unlock my oppo R7 plus running r7plusEx_11_160922 on color os 2.1.o1 android 5.1.1.. As per my study the first thing I need to do it unlock bootloader, then do TWRP, then install any custom rom. (Please correct me if m wrong). Now please tell me how can i unlock my bootloader when I dont have access to fastboot by pressing power and Volume + key. Is there some other way. I have also tried the adb version 1.4.3 to get to the fastboot mode but it restarts my mobile to lock screen.
x_master1987 said:
Hi Guys..
First i don't know if i am posting this in right thread or not... but I need help... after lots of search i couldn't find anything to unlock my oppo R7 plus running r7plusEx_11_160922 on color os 2.1.o1 android 5.1.1.. As per my study the first thing I need to do it unlock bootloader, then do TWRP, then install any custom rom. (Please correct me if m wrong). Now please tell me how can i unlock my bootloader when I dont have access to fastboot by pressing power and Volume + key. Is there some other way. I have also tried the adb version 1.4.3 to get to the fastboot mode but it restarts my mobile to lock screen.
Click to expand...
Click to collapse
Download this rom https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0. Place it in your internal drive and flash it. It will install the ColorOS with an unlockable bootloader.
Even I'm facing the same issue. There are no such methods available on internet. I have ended bricking phone several times. Because since the last update oppo had limited tho access to bootloader. And the phone OPPO r7 plus f is quite old now so there's no people dealing with the issue. The only methods remain is to downgrade the firmware and repay the process again. Better look for some firmware version around mid 2015-2016early. I read somewhere that has access to bootloader. I haven't tried it personally but I hope the methods will work. Please let me know whatever the result is..
need your help badly
ccrocks426 said:
I currently use Resurrection remix on mine however there are some issues with apps force closing is my main one. Lineage OS also had issues for me with bluetooth causing the phone the reboot over and over. CM 13 was the best but I can't find any download links for it any more (rip CM) I think they both have updates coming outside but I recommend trying some out and then making a decision. Also if your phone is on one of the latest oppo updates (one of the 2016 updates) you'll have to downgrade to a 2015 software as they locked the bootloader so you won't be able to root! It's easy to do just find an old firmware from the internet (I would post links but I can't, also has to be a 2015 one) turn off the phone and turn it back on whilst holding down the volume down button and then go install and install the old firmware and then follow any guides on the internet for installing custom ROMs
Hope this helped
Click to expand...
Click to collapse
please pm me your email . i have an oppo r7 plus f (the international version ) and i do not have much knowledge about the rooting and installing custom recovery. and since oppo has closed the bootloader now please tell me which rom to download for downgrading( if possible please provide the link) and then how to flash the custom roms and which rom is best for oppo r7 plus? which one are you using?
DooganAU said:
Rana, first I'm sure you have been a good phone user and your Oppo R7 plus is upto date, unfortunately this is a problem. So first thing you need to do (Assuming you have unbricked your phone) is find a older version of the genuine R7+ firmware. Preferably some time between 2015- mid2016. The reason for this is OPPO locked the bootloader on later versions, these earlier versions are what the autoroot tool was designed to work on. Once you have this firmware, flash through recovery (provided you still have genuine OPPO recovery), if not you also need to flash this. Once you have the older firmware on your phone you should be able to proceed as usual steps to install lineage on your phone using typical walkthroughs.
Click to expand...
Click to collapse
Where can i find the 2015 firmware for oppo r7 plus f
Just check the link in my post above.
kishd said:
Just check the link in my post above.
Click to expand...
Click to collapse
Don't know why but the link is not working

HTC M10 (HTV32) Japan Oreo TWRP backup

Hello mates,
I recently got a used HTC M10 device with boot-loader unlock and s-off I'm using this device outside japan with different network carrier this device have currently 6.0 installed and i want to update it to Oreo but can't update it through settings, I have attached a screenshot of my device info, i'm confuse if i flash this device with other version will it lock the network? or can my device convert to international and receive updates? please help me as i don't want to brick my device.
timimalik said:
Hello mates,
I recently got a used HTC M10 device with boot-loader unlock and s-off I'm using this device outside japan with different network carrier this device have currently 6.0 installed and i want to update it to Oreo but can't update it through settings, I have attached a screenshot of my device info, i'm confuse if i flash this device with other version will it lock the network? or can my device convert to international and receive updates? please help me as i don't want to brick my device.
Click to expand...
Click to collapse
Did you get any solution.I am having a m10 au version too. Want to flash custom rom.But afraid of bricking my device.
dr.estiack said:
Did you get any solution.I am having a m10 au version too. Want to flash custom rom.But afraid of bricking my device.
Click to expand...
Click to collapse
Hello mate, i found a solution and successfully update my device to Oreo officially i just changed the CID and MID back to KIDDI japan au and downloaded the marshmallow official flash zip file (https://drive.google.com/open?id=1noyAV4mGLTRNGaXqbdweRHsARWZ9J6LH) and install it by placing it to Mirco SD card after installation i went to software update and updated to Oreo. PS: my device were network locked while i were trying to convert it to international version but after flashing it unlocked automatically probably i flashed the wrong version. let me know in case of any problem.

Firmware partitions question???

i've never flashed firmware partitions before on my other 2 moto devices, i understand having read the install of lineage that this step is req'd for this model.
i'll be using the lineage recovery to install the rom flash, this is the method ive done before. My question is once i sideload the firmware partitions, will this automatically asign which partion the rom will be written too or do i have to tell it which one, im understanding that it will be either A or B partition??
I'd like to wipe/erase as much of the stock rom off the phone, remove everything and then flash the operating rom to a clean phone. Am i understanding this correctly or missing anything? Is there anything that i need or should know or do when at this step? any help/advice would be greatly appreciated.
This is a brand new phone out of the box, is there other ways that any of you would approach this phone to totally wipe it, i'm hoping that ill get the android 11 update immediatley over ota, i understand that i will have to go through intial setup, to get to unlocking the bootloader, wish i didnt have to do that, also i dont believe kiev has an official android 12 oem/factory rom but lineage has 19.1, im thinking install 18.1 and then later reflash android 12 when it comes out. Im talking to much.... any advice be great. TIA
First things first, know your device. Is it an XT2113-2 RETUS variant or something else? As long as the bootloader can be unlocked, it seems any kiev (qualcom) variant should work with lineageos - just best to know what you started with in the event you need to ask for assistance or you want to revert back to stock.
My suggestion assuming you are starting from a new phone out of the box with the plan of putting official lineageos (either 18.1 - android 11 or 19.1 - android 12) on it:
Have the phone ota update to the most recent stock firmware. For XT2113-2 RETUS at the time of this post, this is android 11 version RZKS31.Q3-45-16-8-3 released 2022.06.30. Lineageos currently uses the binary blobs from this version. I suspect having the latest stock radios and bootloader on your device will result in fewer issues and may likely make your life easier later.
After updating to the most current stock version, request the bootloader unlock key from the moto www site. You may need to wait 24-72 hours or longer before the phone will allow unlocking. Leave the phone on, connected to your (primary) carrier, and use your carrier data (i.e. not wifi) during this time.
After updating to the most current stock version, put all the sims in the phone for the carriers you plan to use and let the phone provision the carriers (I've read this can only be done on stock firmware - switching carriers without having done this step apparently requires going back to stock). Test that you can swap sims and use the phone as you need to (e.g. wifi calling, try visual voice mail, try 5 G, etc).
Unlock the bootloader. Be sure to leave the oem unlocking toggle to allow after unlocking the bootloader.
Most important: when coming from stock (either now or in the future), follow the instructions on the lineageos www site. In particular, flash the copy-partitions.zip following the sequence described in the lineageos instructions. Don't worry about the A/B partitions for now, the device will take care of itself. You only need to flash the copy-partions.zip when comming from stock (either now or if you reflash stock in the future and then want to go back to lineageos).
Flash official linageos 18.1, android 11 (not 19.1- android 12). 19.1 is the newest version; however it may have issues. 18.1 works great (for me) and it will likely be easier for you to check if everthing is working as you expect. Upgrade (via ota) to lineageos 19.1 in a month or two.
Updating official lineageos via ota, the device will flash to the appropriate A or B partition. You should not need to do anything unless there is an issue.
I'd like to wipe/erase as much of the stock rom off the phone ...
Click to expand...
Click to collapse
Following the lineageos installation instructions will accomplish that.
Good luck.
notmyrealhandle, thanks for your time and reply, perfect write, i understood everything you said. i never thought of doing ota via data as opposed to wifi, thanks. perfect​

Categories

Resources