Related
the phone was soft-bricked (boot-looping in the huawei initial animation), when i failed to instal correctly the update from b326 to b511, the bootloader was locked and the phone wasn't rooted, but i managed to solve both things, then i tried to restore a twrp backup of b511, since that was the version i tried to update to in the begining, after the restore, it was stuck yet again in boot loop but this time it only shows the initial huawei picture, so my cuestion is if there is some way to reinstall an older firmware, say b326, because when i did a backup so i could use the folder to store the files for the b511, the containing carpet name included b326, or if someone has a twrp backup for b326 that could share, it would be really apreciated
cheers
p.s.: i don't know if i should use some sort of rollback or how to use it, so any guidance would be really helpful
p.s.2: fooling around i just did another backup with twrp an it says that it has the b511 version, but i would love to go back to b326
p.s.3: i tried to run diferent stock recoveries and it only runs MM version, even when i flash recovery, boot, cache, cust, system and userdata from b326, it only let me run the MM recovery, aside of TWRP
nevermind, i finally solved it
so, with the b511 backup, you download it and change the s/n in the recovery txt, restore it with twrp and when you're going to reboot it, don't install the suggested SU, just let it run as it is and it will get into MM, then you flash the stock recovery using "recovery mate7 mobopx v2.1 translate by chudy_85" and follow the steps in this thread
http://forum.xda-developers.com/mate-7/development/finally-rollback-513-331-511-326-t3325803
My device is European L04, currently running North Africa release (the earliest Marshmallow build uploaded) - L04_2016_0316_0900 (B820)
I'd like to unlock the bootloader and root my Honor 6. I've never done it (on this particular device), because I've read enough here to know it's slightly more risky than on other devices, especially when you plan to update the stock rom soon, so I preferred to wait until I have the last important update the device is likely to receive - Android 6.0.
What I want to know (some of the answers are in the topics which I listed below):
MultiTool - I've seen reports of bricks when using MultiTool with EMUI4/Marshmallow - why does it happen? My understanding is that MultiTool is a bundle of adb/fastboot and some recovery images for older Android versions, so my theory is that instead of using MultiTool, I should simply get the proper recovery for Marshmallow and flash it manually with fastboot, right?
unlocking bootloader, rooting, flashing recovery - I think I understand the process; in a nutshell: 'fastboot oem unlock X', 'fastboot flash recovery imagename.img', then flash the proper SU.zip in recovery. Where do I find the code, the Marshmallow recovery image, the SU.zip file?
will recovery backup in TWRP work without any problems?
what is the procedure to go back to stock completely after rooting? Unroot, (then wipe if it's needed?) so I am able to safely flash stock firmware again (since, from what I know, flashing stock on a rooted phone makes itself brick permanently, right? or is it just a soft-brick and it can be fixed?)
is there anything else I should know before proceeding?
What I found so far:
http://forum.xda-developers.com/showpost.php?p=66615082&postcount=502 - two recovery images, TWRP and another one (stock?) for the Marshmallow release
http://forum.xda-developers.com/honor-6/general/honor6-multi-tool-t2963060/page50 some rooting instructions for the L02 beta, see posts 494 and 498; no idea whether this is applicable to final Marshmallow or L04 at all
http://forum.xda-developers.com/honor-6/general/huawei-honor-6-plus-unlock-bootloader-id-t3357259 an app to get the unlock code, seems a bit shady to me though on the first glance
http://forum.xda-developers.com/honor-6/development/honor-6-rooting-method-t2962795 alternate methods for bootloader (through a website or by email), in case the app won't work; also, detailed instructions on unlocking and rooting
Basically, I need to know whether my procedure is more or less right before I proceed. I think the information is quite hard to find and the risks are quite high, so I'd like to make a promise - when I'm done rooting it and I know the correct process, I'm going to make a "Update to Marshmallow, unlock, root" how-to thread for all the people that will need it in the future.
Another two questions...
1. Where do I get proper SuperSU for Marshmallow? I get a boot loop (yeah, I know I have to wait and I did, but it's a pretty obvious bootloop from watching the logcat content, and nothing new happens...) after flashing http://download.chainfire.eu/supersu-stable (2.65).
2. I have unlocked my bootloader and installed TWRP, so recovery and fastboot are functional. I didn't make a backup before flashing the zip and now I'm in a bootloop. How do I restore working Marshmallow? I assume I can either beg somebody to upload a TWRP backup for my H60-L04, or somehow flash the stock over what I have now. Can I simply use manual update from SD? Can I somehow flash Marshmallow again with fastboot? I'm too scared of bricking my device right now so I guess I'll brace myself for a few days without a phone until somebody helps me :/
I just flashed the Marshmallow release I had before the bootloop (I used Huawei Update Extractor and flashed boot, cust, system and recovery with fastboot; then open up Huawei recovery and factory reset for good measure, I'm not sure it was even needed) and the device is working. I'll restore my stuff, install TWRP, make a backup then try out your ZIP. Thanks
edit: thanks again - your zip works indeed. So after the initial hurdles, now I've got working root and a reasonable way of restoring in case I screw something up along the way.
Before making a new topic with the tutorial I have a few more questions.
First of all, why exactly we weren't supposed to update the rooted devices? I'm not currently interested in OTAs (it's pretty obvious that it needs a functional Huawei recovery, and you need to unroot cause an update can make a mess in a rooted system, making it bootloop for example), but can we flash extracted images with fastboot on rooted devices? Logically, we should be able to... How about sdcard update method?
Can we flash Marshmallow on Kitkat? (fastboot, sdcard, local update methods?) Or do we need to update to Lollipop along the way?
Can I flash stock roms in general (evenbetween different Android versions) by using fastboot with {boot, cust, recovery, system} images only? There's a lot of images that you can extract with Huawei Update Extractor - why there's so many if they're not needed?
Hi.
Just recently I rooted my Xperia z3 (D6603) and upgraded the KitKat 4.4.4 into 6.0.1 MM through AROMA (found a link on this website).
After trying to install Xposed Framework, I had to flash it through TWRP recovery, but it said that I had the wrong version (arm)
I then downloaded a different version, however now my TWRP won't launch manually or automatically ( through a reboot app).
It will just jump straight into android instead of coming up with the team win logo etc.
I am confused as to why this is happening, do I need to flash the .img of it into my phone again or is there another sure way of fixing my issue.
Any help would be very appreciated . At the moment I cannot install Xposed framework because I have to flash it via recovery and I can't get into it.
Thank you
P.S Everything else works fine, no bootloop or brick
P.S2 Rebooting to recovery through TWRP Manager didn't work either (straight into Android)
If you cant get into recovery by pressing volume down on reboot. ie when they phone turns on there will be a buzz and a green light, press vol down and it should turn purple and then go to TWRP.
If you didn't unlock the bootloader this should help you fix it.
If this doesn't happen ensure you have SuperSU and that it works ie. you're actually still rooted...
If still rooted:
Find RecRoot v4 by Wolfbreak here: http://forum.xda-developers.com/z3/general/wip-sony-android-6-0-mm-t3337357 and use it from your PC to reinstall recovery.
If this fails it means root is broken.
If root is gone you will need to downgrade again and root and update again. Make sure this time you use a pre-rooted zip or at least flash recroot (works in recovery also) straight after you flash the ROM to keep root. If you use a custom ROM they should always include root (just read the XDA page of that ROM and make sure).
If your bootloader is locked (which I'm assuming it is if you downgraded to root and upgraded after) don't mess around flashing any .img files you will likely mess things up. Recoveries on LB have to be installed carefully.
If anyone says they haven't had an issue like this with root they're probably lying. It's all part of the fun ;P
To flash xposed make sure you download the one for MM which is SDK 23. And for the architecture of the Z3 processor you need ARM. This should work fine for you.
(please correct me if I missed something or got something wrong)
Dobsgw said:
If you cant get into recovery by pressing volume down on reboot. ie when they phone turns on there will be a buzz and a green light, press vol down and it should turn purple and then go to TWRP.
If you didn't unlock the bootloader this should help you fix it.
If this doesn't happen ensure you have SuperSU and that it works ie. you're actually still rooted...
If still rooted:
Find RecRoot v4 by Wolfbreak here: http://forum.xda-developers.com/z3/general/wip-sony-android-6-0-mm-t3337357 and use it from your PC to reinstall recovery.
If this fails it means root is broken.
If root is gone you will need to downgrade again and root and update again. Make sure this time you use a pre-rooted zip or at least flash recroot (works in recovery also) straight after you flash the ROM to keep root. If you use a custom ROM they should always include root (just read the XDA page of that ROM and make sure).
If your bootloader is locked (which I'm assuming it is if you downgraded to root and upgraded after) don't mess around flashing any .img files you will likely mess things up. Recoveries on LB have to be installed carefully.
If anyone says they haven't had an issue like this with root they're probably lying. It's all part of the fun ;P
To flash xposed make sure you download the one for MM which is SDK 23. And for the architecture of the Z3 processor you need ARM. This should work fine for you.
(please correct me if I missed something or got something wrong)
Click to expand...
Click to collapse
Problem is that when I downloaded the SDK23 arm, it said wrong format : ARM in red and gave me an error. After that I couldn't go back to twrp no matter what I did.
- I am now back to 6.0.1 MM rooted, going to try installing Xposed again, hopefully this time nothing will go wrong
[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root
THIS GUIDE IS NOW DEPRECATED. THERE IS NO NEED ANYMORE TO GO THROUGH THE UPDATING PROCESS AS THERE IS A FULL NOUGAT FACTORY IMAGE AVAILABLE (Build NPH25.200-22). FIRMWARE AVAILABLE HERE: https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 BE SURE TO THANK @acejavelin FOR TRACKING DOWN THE FIRMWARE PACKAGE FOR US.
Notes:
-YOU ATTEMPT THIS AT YOUR OWN RISK IF YOU FLASHED ANY FIRMWARE PREVIOUSLY NOT FOR THE XT1575 US VERSION
-This guide will have 2 parts. 1 for those that kept their systems read only/systemless, and 1 for those that did not.
-Whether you live booted TWRP or Installed TWRP, if you chose to allow system modifications your OTA will likely fail (you'll need part 2).
-Restoring a TWRP backup will not work and will cause an OTA to fail due to having to allow system write access in TWRP - You Need Part 2.
-This guide assumes you have basic ADB knowledge and already know what fastboot is and how it works.
-Thanks to @gokart2 for the OTA and @acejavelin for the return to stock guides
Part 1: Those That Tweaked Systemlessly Currently On 24.49-18-16 (Will only work if you kept TWRP read only/used systemless root):
1: Disable & Remove systemless Xposed within Magisk Manager and all other Magisk modules. Reboot and wait for Art cache to rebuild.
2: Remove any adblock hosts within your adblock app if installed, or any other root level system altering apps like Greenify (don't worry, you'll get them back).
3: Remove Magisk by booting into TWRP and flashing the current Magisk Removal zip. Reboot.
4: For systemless SuperSu you need to consult their thread as I do not use it. (I'll update this if someone knows the correct process).
5: ADB reboot bootloader and fastboot flash the stock recovery. Latest MM recovery links at the bottom of this post. (rename file to recovery.img).
6: Move the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip to the root of your internal sd card (NOT in a folder). File links at the bottom of the post. Thanks @gokart2
7: ADB reboot recovery, when "no command" is listed, hold power + tap volume up then release to access recovery options. Choose "apply update from phone storage". Choose the file and wait for the flash. It's a large update so be patient (about 10-20min). Choose reboot manually in recovery after flash succeeds. Enjoy Nougat!
8: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly.
Part 2: Those That Have Done Everything - TWRP Write Access, Custom Roms, On Older Firmware, Etc (XT1572 Build Flashers Do This At Their Own Risk):
1: Flash the latest full factory image available (24.49-18-8) available here: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110. Thank @acejavelin for the thread while your at it. Follow the directions in that guide, it's well detailed and accurate - however read my notes just below first:
NOTES:
-Omit the "fastboot oem lock begin" & "fastboot oem lock" commands to remain bootloader unlocked.
-Omit the "fastboot erase userdata" command if you want to dirty flash and keep all of your data. I recommend clean, you can always root & restore each apps data with Titanium after the Playstore installs everything.
-The "fastboot oem fb_mode_set" instead of "fastboot oem lock begin" & "fastboot oem fb_mode_clear" instead of "fastboot oem lock" I've found to be unnecessary if staying unlocked. Your choice.
-The "fastboot flash partition gpt.bin" & "fastboot flash bootloader bootloader.img" commands will likely fail due to version mismatches. This is ok.
-The "fastboot flash modem NON-HLOS.bin" tends to fail too. For this, just run the command again until it succeeds.
2: After flashing 24.49-18-8 take the OTA to 24.49-18-16. Reboot. OTA zip provided below if you prefer to sideload.
3: Either install the 7.0 OTA the normal way via the update center or just side load it using the directions above. I recommend side loading due to the file size being very close to 1GB.
4: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly!
For Xposed, See My Guide Here: https://forum.xda-developers.com/showpost.php?p=74014516&postcount=96
Stock MM 24.49-18-16 Recovery: https://mega.nz/#!aZpC2RzQ!Fy3GTo_XYPjB1lwuHffCUUERuvnsyvON3kS8kMJ9Cm8
Stock MM 24.49-18-16 Recovery Mirror: https://drive.google.com/file/d/0BxxRfNko9QDKNS1NdnAyZVp6dVU/view?usp=sharing
24.49-18-8 OTA to 24.49-18-16: https://mega.nz/#!yZx2FLzR!cWfKIAYe5VyuadLI55UNHJvwWU98CXUi1g0DO1pDoKg
NPH25.200-22 OTA: https://mega.nz/#!HVhWWLxK!h-8G3vO3Sye_YwypyIJyWb2_79Ow34vNiDnMl2Q8uJg
NPH25.200-22 OTA Mirror: https://drive.google.com/file/d/0B3gPYUZ4nRLwOHJKQnNYczNEMHc/view?usp=sharing
MD5 for NPH25.200-22 OTA: 74d1a4b135200661cc4efd248f99ce33
Stock 7.0 NPH25.200-22 Recovery: https://mega.nz/#!TNoHQAjI!5U2w4p_G7pHlW6Mak7LqFR_PeWUDpSLc7S3OiUs_Qf8
Alrighty. I got back to stock 6.0 with the 18-16 update. I couldn't get the OTA via the system update, so I tried doing it via ADB. That threw up a "status 7 error". I then copied the file to my internal storage and selected update via SD Card in recovery. It hung on "Patching System Files" for a while, but in the end it moved on and worked fine. Thanks for the awesome guide!
Thread updated with downloads for the 24.49-18-8 OTA to 24.49-18-16 zip.
I exctracted the 7.0 Stock recovery to replace if you decide to flash TWRP and want to go back to the stock recovery for future updates (HAHAHA yeah right!). Download link in OP. The 7.0 Recovery is different than the MM recovery. They are not interchangeable. Don't flash the 7.0 recovery on MM.
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Bwangster12 said:
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Click to expand...
Click to collapse
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
annoyingduck said:
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
Click to expand...
Click to collapse
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Here's the recovery before the 7.0 one, just incase.. Was bored. Ok, I won't lie....didn't see u posted the 7.0 recovery....lol.:good::highfive:
Bwangster12 said:
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
Click to expand...
Click to collapse
Yup. TWRP flashes and works, magisk v14 works, and so far systemless xposed api24 is working.
EsteBandido4444 said:
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Click to expand...
Click to collapse
What is everyone's fascination with relocking the bootloader? You do not need to relock your bootloader. You cannot relock the bootloader unless all your system partitions match. Use my part 2 section. Read the notes, skip the bootloader lock commands. Leave your bootloader unlocked, get up and running on nougat, then you can issue the lock commands if you really want a locked bootloader.
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
EDIT nevermind didn't read lol
Amp699435 said:
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
Click to expand...
Click to collapse
Copy the file to the root of your internal storage. Reboot into recovery. Hold power = volume up & release to access menu options. Choose apply update from storage. Select the OTA.zip package and let it install. (Directions are clearly written in OP.)
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
Click to expand...
Click to collapse
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
GrandAdmiral said:
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
Click to expand...
Click to collapse
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
annoyingduck said:
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
Click to expand...
Click to collapse
Gotcha. I know I'm going to root again, but I've never used Magisk before so I wasn't sure of that piece.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
I am running Dirty Unicorns right now and when i looked up what I'm on in fastboot, it showed MPSH24.49-18-16. Would I just follow part 2 and use MPSH24.49-18-8 or something? I thought I had to use at least the version I'm on or newer.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.[/QUOTE
Your issue is that TWRP has modified your
System, any restoring of the stock rom will fail to update. So yes, you'll need to go through part 2 and downgrade and work your way back up.
Click to expand...
Click to collapse
I downloaded the zip (it took a while).
Restored to stock like 3 different ways but still hit a road block. I went the adb sideload route but got status error 7 because my build fingerprint wasn't correct. I tried searching for the right build I need, but I'm not an expert and couldn't find the right set of files that I was sure I knew how to restore. I ended up restoring my AICP backup.
If somebody could PM me and give me a hand (messaging through Hangouts or something) that would be AWESOME!
I'm planning trying to snag an XL 2 pre-order next week, but until then the less headache the better! Plus stock Nougat looks better on a Swappa listing
Trying to sideload via recovery 24.49-18-16 but I keep getting "("unexpected contents:EMMC:/dev/block/bootdevice/by-name/boot...". I've also tried installing from the phone but the same error appears in recovery. Any ideas?
Hello everyone,
First of all, sorry if i post it in the wrong section and if i am not always making sense.
So here is my situation :
i have a HTC U11 which i rooted a long time ago with TWRP & SU.
I then switch SU to Magisk (a year ago), because i needed to hide my root from few apps.
I wanted to update magisk Manager, but i lamely failed
(i went to recovery mode, installed the uninstaller ZIP for Magisk in order to put a version above 18 but then i had a boot.img missing error)
So i did restore an old backup that i had from 2017...
Currently i have :
Version android : 7.1.1
Firmware version : 1.27.400.8
Magisk version : 18.1
Magisk Manager Version : v7.1.1
TWRP Version : 3.3.0.0-ocn
My questions :
I want to update my firmware. I mean, my phone tells me there is an update. Is it what we call OTA ?
After i've downloaded the new firmware version (1.27.400.21), i select install now, and my phone reboots to Recovery mode, but asks me for a password (to decrypt data).
What the hell is that ?
Also, i would like to be able to still install this new version (and the futures ones).
How do i do that ?
Is it possible to upgrade the Android version too ?
I wish not to have to wipe or lose data.
What's the point to wipe data, dalvik, cache ?
When you do it do you lose your personnal data ?
Many thanks for your helps and support
toto_rigolo said:
Hello everyone,
First of all, sorry if i post it in the wrong section and if i am not always making sense.
So here is my situation :
i have a HTC U11 which i rooted a long time ago with TWRP & SU.
I then switch SU to Magisk (a year ago), because i needed to hide my root from few apps.
I wanted to update magisk Manager, but i lamely failed
(i went to recovery mode, installed the uninstaller ZIP for Magisk in order to put a version above 18 but then i had a boot.img missing error)
So i did restore an old backup that i had from 2017...
Currently i have :
Version android : 7.1.1
Firmware version : 1.27.400.8
Magisk version : 18.1
Magisk Manager Version : v7.1.1
TWRP Version : 3.3.0.0-ocn
My questions :
I want to update my firmware. I mean, my phone tells me there is an update. Is it what we call OTA ?
After i've downloaded the new firmware version (1.27.400.21), i select install now, and my phone reboots to Recovery mode, but asks me for a password (to decrypt data).
What the hell is that ?
Also, i would like to be able to still install this new version (and the futures ones).
How do i do that ?
Is it possible to upgrade the Android version too ?
I wish not to have to wipe or lose data.
What's the point to wipe data, dalvik, cache ?
When you do it do you lose your personnal data ?
Many thanks for your helps and support
Click to expand...
Click to collapse
aq
Find out your cid/mid
You will need to flash the appropriate ruu (nougot) for your phone from here (sd card method)
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/htmlview
in order to receive the ota updates. And yes you will lose everything. Backup as much as you can . And once you go to pie there is no going back unless s-off. ( There is another way but more involved) . hth
Thanks for your reply.
How do i find my cid/mid ?
I tried yesterday to use adb, but i could NOT find my device in download mode... The only way i was able to see it was to boot in recovery mode.
Can i still get my cid & mid if can find my device whilst it's in recovery mode ?
So i understood that i need to download the right file, rename it, put it on the root of the SD CARD and then boot my phone in bootlader mode.
Don't i have at some point specify the ZIP file to use ? Does it mean it will detect it automatically ?
Then why doesn't it work if i put it on the root of the internal sotrage of my phone ?
If i flash a RUU, will my phone still be rooted and unlocked ?
toto_rigolo said:
Thanks for your reply.
How do i find my cid/mid ?
I tried yesterday to use adb, but i could NOT find my device in download mode... The only way i was able to see it was to boot in recovery mode.
Can i still get my cid & mid if can find my device whilst it's in recovery mode ?
So i understood that i need to download the right file, rename it, put it on the root of the SD CARD and then boot my phone in bootlader mode.
Don't i have at some point specify the ZIP file to use ? Does it mean it will detect it automatically ?
Then why doesn't it work if i put it on the root of the internal sotrage of my phone ?
If i flash a RUU, will my phone still be rooted and unlocked ?
Click to expand...
Click to collapse
I believe the adb command is "getvar all" while in the download mode. get the cid/ mid number reboot then get matching nougot ruu zip. rename to 2pzcimg. zip place in the root of sd card boot to download mode not bootloader, it will detect automatically, hth
Thanks.
Will my phone still be rooted ?
Will i have to reinstall Magisk & Magisk Manager ?
toto_rigolo said:
Thanks.
Will my phone still be rooted ?
Will i have to reinstall Magisk & Magisk Manager ?
Click to expand...
Click to collapse
Oh no it won't be, you will have to reinstall twrp, Magisk,
fair enough.
but sadly, adb doesn't work on my computer. I can't see my phone.
I only get something when my phone is in recovery mode.
download more & bootloader mode, i can't find it.
toto_rigolo said:
fair enough.
but sadly, adb doesn't work on my computer. I can't see my phone.
I only get something when my phone is in recovery mode.
download more & bootloader mode, i can't find it.
Click to expand...
Click to collapse
Try installing htc sync manager then reboot and run adb. You just may need the right drivers
I have read more about it and you're right it should be something like that.
Also, once i have flashed the RUU, rooted again, installed TWRP & Magisk, will i still be able to update OTA ?
I don't understand when some people say they uninstalled Magisk, intall the OTA and install Magisk back on...
Is it really the way to do it ? To be able to install latest OTAs ?
toto_rigolo said:
I have read more about it and you're right it should be something like that.
Also, once i have flashed the RUU, rooted again, installed TWRP & Magisk, will i still be able to update OTA ?
I don't understand when some people say they uninstalled Magisk, intall the OTA and install Magisk back on...
Is it really the way to do it ? To be able to install latest OTAs ?
Click to expand...
Click to collapse
You will have to install ota before rooting , once rooted or twrp installed Ota will not install. This is my understanding, if someone has a different approach please chime in. Installing just the firmware is a different animal and requires more reading!! Hth
Okay so we are on the same page.
So my question is ow do you keep installing OTAs when your phone rooted or with TWRP ??
also i remember my cid is HTC__060 which i believe is india.
Is there anyway i can change it to Europe ? I mean, is there any interest for me to do so ?
toto_rigolo said:
Okay so we are on the same page.
So my question is ow do you keep installing OTAs when your phone rooted or with TWRP ??
also i remember my cid is HTC__060 which i believe is india.
Is there anyway i can change it to Europe ? I mean, is there any interest for me to do so ?
Click to expand...
Click to collapse
Ota will stop once twrp is installed, I really don't see a benefit changing cid, but that's up to u ?
To install an OTA with twrp you have to:
1. Download the OTA in zip format (search in this forum).
2. Copy it to mobile memory.
3. Reboot to twrp and apply manually the zip.
If you are going to change the Cid, change to Taiwan version (that region has received more updates than the rest of the world).