Related
Hey guys, I've rooted, installed CWM Recovery, Unlocked Bootloader, and installed CyanogenMod on another phone before.
The thing is, I've had this phone for about 6 months and wanted to do the same. However, after browsing through the forums, man are there a lot of scary sh*t going down. I would like the request the procedure to install CyanogenMod safely, without losing any Keys/IMEI/XReality/DRMkeys/Etcetera.
I dont know if the method given by FXP is supposed to be this straight forward, but I too like others, do not want to risk losing important stuff if it can be avoided (Keys/IMEI/XReality/DRMkeys/Etcetera).
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
Click to expand...
Click to collapse
Frankly speaking, the forums is pretty much jumbled up, and the existing [Guide] Threads are either incomplete (Lacking important steps), or Unclear (Non-Specific steps).
Perhaps someone could do me a favour by using the template that I have below to help me, and possibly others, to install CM 10.2 on our beast of a phone.
Template:
1. Backup TA and DRMkeys and stuff: http://forum-xda-developers-com/backup
2. Root: http://forum-xda-developers-com/root
3. Recovery : http://forum-xda-developers-com/recovery
4: Unlock Bootloader: http://forum-xda-developers-com/ulbl
5: Install FXP's CM 10.2 :http://forum.xda-developers.com/showthread.php?t=2461286
Something like that would suffice I think, as long as no important steps are missing that would cause me to lose stuff unique to my phone, that cannot be recovered if I didn't back it up.
P.S. My version is 14.1.B.2.257
P.P.S. Thank you in advance.
1. Root
2. Backup TA (VERY IMPORTANT)
3. Install Recovery and unlock the bootloader, or the other way around. Both ways work.
4. Install ROM by following the "guide" that you quoted above.
Sent from my C6833 using Tapatalk
I'm on 14.1.B.2.257, I believe reverting to the previous version causes data to be lost unless you back it up right. *Sighs* How troublesome.
Xenogenics said:
I'm on 14.1.B.2.257, I believe reverting to the previous version causes data to be lost unless you back it up right. *Sighs* How troublesome.
Click to expand...
Click to collapse
you will have to back up the data anyways. I think unlocking the bootloader does a factory reset, as well one is needed going from stock to CM if i unforget correctly
I am also wondering about this. I'm currently running firmware .257.
I understand that I need to back up the TA partition first (though I'm not exactly sure on what I will loose if I don't). I also understand that to do this I need to root the stock rom. I understand that in order to root, I'll need to first downgrade to an earlier firmware using flashtool. However, after that I'm not so sure what I need to do. As far as I can see, the only method of gaining root currently is to use vRoot, which is currently under investigation for IMEI mining.
How else can I root the device? I was thinking of maybe using the recovery for locked bootloaders here: http://forum.xda-developers.com/showthread.php?t=2426739
Following by flashing SuperSU from recovery as per usual.
Will this work, keeping the TA partition intact so that I can back it up before flashing CM? Assuming so, would I even need to downgrade from the .257 firmware at all?
Thanks,
i have CWM now so can flash custom roms like i did on other phones right?
what does unlocking the bootloader give me? unless i'm wrong and i have to unlock to flash?
all i've done so far is do a backup is all. (did a TA backup a while back though)
stiggy2012 said:
I am also wondering about this. I'm currently running firmware .257.
I understand that I need to back up the TA partition first (though I'm not exactly sure on what I will loose if I don't). I also understand that to do this I need to root the stock rom. I understand that in order to root, I'll need to first downgrade to an earlier firmware using flashtool. However, after that I'm not so sure what I need to do. As far as I can see, the only method of gaining root currently is to use vRoot, which is currently under investigation for IMEI mining.
How else can I root the device? I was thinking of maybe using the recovery for locked bootloaders here: http://forum.xda-developers.com/showthread.php?t=2426739
Following by flashing SuperSU from recovery as per usual.
Will this work, keeping the TA partition intact so that I can back it up before flashing CM? Assuming so, would I even need to downgrade from the .257 firmware at all?
Thanks,
Click to expand...
Click to collapse
OK, so looking into this further, you already need to have root to be able to flash the "CWM for locked bootloader" rocovery. So as far as I can see, the only way to get root in order to back up the TA partition is to give your IMEI to the Chinese via vRoot?
Thank god the stock rom is so good.
tommo123 said:
i have CWM now so can flash custom roms like i did on other phones right?
what does unlocking the bootloader give me? unless i'm wrong and i have to unlock to flash?
all i've done so far is do a backup is all. (did a TA backup a while back though)
Click to expand...
Click to collapse
You have to unlock the bootloader to flash custom ROMs. You can flash stock ROMs without unlocking it, but you have to unlock it if you want CM, PAC, PA etc.
Sent from my C6833 using Tapatalk
really, so what would happen if i tried to flash an aosp rom now? would the system partition essentially be read only?
sorry for the Qs but haven't had a locked bootloader since the htc desire (although the s-off for that one was to remap the partitions to allow more room for data) and the reasons for unlocking don't seem to be the same.
tommo123 said:
really, so what would happen if i tried to flash an aosp rom now? would the system partition essentially be read only?
sorry for the Qs but haven't had a locked bootloader since the htc desire (although the s-off for that one was to remap the partitions to allow more room for data) and the reasons for unlocking don't seem to be the same.
Click to expand...
Click to collapse
Nothing will happen if you try it now. You can easily unlock the bootloader by going to Sony's Dev site, request your key and use Flashtool to unlock it. It takes a couple of minutes once you have Flashtool and the drivers installed. It's also perfectly safe to unlock it and you will lose your warranty. BUT you can easily relock it again if something happens to your ZU and the warrenty will be back.
Remember to backup your TA before you unlock your bootloader. It contains a lot if device info and your unique DRM keys. Unlocking the bootloader will wipe the system partition, but you will still have root, photos, music etc. (But do a backup of those just in case).
Sent from my C6833 using Tapatalk
i think that's where i got confused with drivers - unlocking.
i have already done a backup of my TA part so that side of it is ok. i'll leave unlocking until there's a rom i want to try. possibly a complete 4.4 or something.
cheers LM
tommo123 said:
i think that's where i got confused with drivers - unlocking.
i have already done a backup of my TA part so that side of it is ok. i'll leave unlocking until there's a rom i want to try. possibly a complete 4.4 or something.
cheers LM
Click to expand...
Click to collapse
If you've already backed up your TA, it means that you have the drivers installed, so job done All you have to do is to install Flashtool and get your key from Sony (which you will get on your email straight away). Either way, just ask here if/when you want to unlock it so we can guide you through it (it's very easy though).
ran flashtool but gave me driver errors - missing. unable to install the drivers included (i guess due to windows 8 driver signing)
This place has gotten a bit messy with all of the threads out there and it's especially confusing for those who are new to unlocking and rooting. Or, heck, to those who weren't around as the threads were being written and referenced. I've reposted my consolidated step-by-step list half a dozen times so far - and the steps seem to be working for folks - so I'm going to post it here. You're still going to have to visit the original threads, but hopefully this will serve as a clear outline for you.
Maybe we can also try to keep general unlocking and rooting questions ("I don't know where to start, help me!") to this thread to avoid cluttering up the other ones. Reserve questions in those threads for those specifically related to the OP ("I received ABC error after doing XYZ, what does it mean?"). If anyone sees general unlocking or rooting questions in other threads, maybe direct them here as a place to start. Make sense?
A list of FAQs can be found here in the second post.
Many thanks to @tenfar and @DrakenFX (among others with their help and suggestions!) for the tools and files they provided to make all of this happen.
Unlocking and Rooting your Axon 7
This set of steps has worked successfully for multiple folks (including myself) on the US/NA variant (A2017U) and stock B29. Folks with EU/global variant (A2017G) may have issues and as of right now, should proceed with caution. If you see any problems and/or have a different variant and need additional (or different) steps added, let me know. I will update the thread as necessary.
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Backup your boot and recovery (just in case) using the tool found here: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Using the same tool as above, flash TWRP (recovery) found in that thread. You do not need to flash the boot image!
Unlock the bootloader: http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash the bootstack and ROM for your variant: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Boot phone, set it up, whatever
Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, fully functioning TWRP (no data encryption issue), and a rooted phone. You will no longer be able to receive OTAs!
Putting Your Axon 7 Back to Stock
If you want to revert back to stock and re-lock your bootloader (eg. sending the phone in for warranty work or are selling it), you should be able to do that using the steps below. It worked for me, anyway, exactly as written below.
Copy everything off your internal storage that you don't want to lose. If you're not rooted (so already stock, but with unlocked bootloader), skip to step 6 below. Otherwise, continue.
Grab the "StockSystem" zip for your variant from this thread and place on your microSD card: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Reboot into TWRP and wipe system, data, dalvik, and cache
Flash the StockSystem zip and power off (doing so will restore stock boot but does not appear to restore recovery)
Boot into EDL mode and flash stock recovery only: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Power off the phone, plug from computer, and then boot into stock recovery (hold Vol+ and press Pwr, continue holding Vol+ until recovery comes up)
Select "Wipe data / factory reset" and then "Yes"
After that finishes, select "Reboot to bootloader"
Plug in your phone into your computer and do: fastboot oem lock (see second post if this doesn't work and says <waiting for device>)
Your phone will reboot and should have been totally wiped (including internal storage) by doing the above
This should leave you with a stock, locked, and unrooted phone that can take OTAs. Note: it's possible (in fact, likely) that an OTA could break the ability to unlock your bootloader and gain root again, so be careful about going back to stock if you think you'll want to unlock/root later on!
If you need any stock files for B20 or B27 (stock recovery for re-locking, for example), you can get them here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
What does disemmcwp do and why should I do it?
disable emmc (internal storage) write protection is what allows changes to system (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
I only see B27 files and not B29. Help!
If you're in any of the threads referenced in the OP that only have files marked as B27, you can use those even if you're on or upgrading to B29. If the thread has B29 files, use those.
Fastboot can't find my device.
If fastboot oem lock returns <waiting for device> or fastboot devices doesn't show anything, the most likely culprit is that Windows is using updated ADB drivers and you need to roll back. You can do this via Device Manager > right-click Android Device (or Kedacom USB device) / Android Bootloader Interface > Update driver > Browse my computer for driver software > Let me pick... > Choose older version (in this case, v9)
For #3, you might want to emphasize that only TWRP is needed, and that people can skip flashing a boot.img. I've seen people who want to unlock their bootloader asking where to find the modified boot.img for B29, which isn't needed.
And of course, thanks for the guide!
xtermmin said:
For #3, you might want to emphasize that only TWRP is needed, and that people can skip flashing a boot.img. I've seen people who want to unlock their bootloader asking where to find the modified boot.img for B29, which isn't needed.
And of course, thanks for the guide!
Click to expand...
Click to collapse
Excellent point. Done!
It would be nice if someone can post a video on YouTube. That would make it that much easier.
Thanks for your guide.
It will be good to post also the steps to lock it again, in case that we need to send the phone for warranty. Because this method does not void warranty, does it?
I think that it is only to push the backup fastboot and 'fastboot oem lock'
I have set up my phone now (with fingerprint security) and want to make a full backup in twrp. Is it true, that i must disable fingerpint and/or pin before i make an backup because when i restore backup with security enabled, that the phone was locked?
Also it would be nice a guide how to go back to stock and update to latest OTA.
Sent from my ZTE A2017G using Tapatalk
tasar said:
I have set up my phone now (with fingerprint security) and want to make a full backup in twrp. Is it true, that i must disable fingerpint and/or pin before i make an backup because when i restore backup with security enabled, that the phone was locked?
Click to expand...
Click to collapse
Yes you must disable your screen lock due to the encryption issue in MiFavor. If you do not disable your screen lock and restore your data, your pin/password/pattern would become wrong and your only option would be to factory reset. Fingerprint would still work but I wouldn't risk it.
dejikocv said:
Thanks for your guide.
It will be good to post also the steps to lock it again, in case that we need to send the phone for warranty. Because this method does not void warranty, does it?
I think that it is only to push the backup fastboot and 'fastboot oem lock'
Click to expand...
Click to collapse
razorsbk said:
Also it would be nice a guide how to go back to stock and update to latest OTA.
Click to expand...
Click to collapse
I've updated the OP with the relevant information. I haven't done it myself so I can't say what the exact screens are, but the steps should be pretty close and you should be able to figure it out.
If no one confirms (or corrects) the steps as I've written them, I'll go through the process before installing CM and update the steps to more accurately describe the process.
@rczrider
I'll updating my sticky thread/guide/info to direct everyone who want to unlock/root their devices, here to your thread....instead of having an outdated one with old info.
Can you also make a guide for g model with 05 update for unlocking and rooting and istalling twrp.
kodrnusa said:
Can you also make a guide for g model with 05 update for unlocking and rooting and istalling twrp.
Click to expand...
Click to collapse
This will be very helpful
Do I have to rollback to B20 or B27 to unlock bootloader?
@rczrider
I have tested the back to stock steps for you on the US model and for now those steps do not get you back to stock. I have wiped the right things and flashed the StockSystem zip multiple times but twrp lives through the wipe and StockSystem install. I'll try to get it working and report back.
Thanks for the great guide!
So, if I do this, no OTA updates. Can I just download the updates and flash them? Are they available anywhere? Or no updates, period, right now?
Orlando1193 said:
I have tested the back to stock steps for you on the US model and for now those steps do not get you back to stock. I have wiped the right things and flashed the StockSystem zip multiple times but twrp lives through the wipe and StockSystem install. I'll try to get it working and report back.
Click to expand...
Click to collapse
I was under the impression that @DrakenFX's StockSystem zip would overwrite boot, but I could be wrong in that. Have you tried doing the same process, but manually replacing recovery using @tenfar's tool and your own original recovery image?
If you don't have your original recovery, it (among other files for B20 and B27) can be found here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
baconboy said:
Thanks for the great guide!
So, if I do this, no OTA updates. Can I just download the updates and flash them? Are they available anywhere? Or no updates, period, right now?
Click to expand...
Click to collapse
Correct, no updates at all for the moment. As it stands, I believe we would need a modified/merged full zip that included the OTA's content. You definitely won't be able to receive OTAs officially.
Everytime i want unlock bootloader i get this error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Great thread. Just wish this post was up 2 days ago. I just flashed B29 to my Axon from B20_Boot (which I now have read was a bad move. I just found out call audio & mic arent working). Good thing you put this post up. I have been scrambling through the threads to figure a solution. Just gonna flash back to B20 stock using TWRP :good:
Kevinkuensken said:
Everytime i want unlock bootloader i get this error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
You probably haven't enabled OEM Unlock in Developer Options.
Hello, I just got my Redmi Note 9 pro And i want to root! I've rooted my samsung note 4 and s3 before. I don't want to use a custom recovery i don't want a custom rom. and i want to keep geting updates if possiable.
https://forum.xda-developers.com/redmi-note-9-pro/development/gsi-t4105121
kalehrl said:
https://forum.xda-developers.com/redmi-note-9-pro/development/gsi-t4105121
Click to expand...
Click to collapse
I don't want to install a rom i want to keep miui
At the beginning of the instructions there is a short description how to root.
So, I'm Kinda Confused "If you want to root then copy the stock boot from the latest stock rom into internal and use magisk to patch it, then flash the patched boot in bootloader (fastboot flash boot patched_boot.img)"
So i take the miui boot and flash it after i installed this rom and restore a backup without restoring the boot.img ?
and we don't get updates foing that (we don't get updates when we unlock bootloader but why ? ) I Guess we just gotta accept the L here
Cilekcigs said:
and we don't get updates foing that (we don't get updates when we unlock bootloader but why ? ) I Guess we just gotta accept the L here
Click to expand...
Click to collapse
With unlocked bootloader and root you will still get OTA Updates with Miui, you just need to root again after installing the update.
Cilekcigs said:
So, I'm Kinda Confused "If you want to root then copy the stock boot from the latest stock rom into internal and use magisk to patch it, then flash the patched boot in bootloader (fastboot flash boot patched_boot.img)"
So i take the miui boot and flash it after i installed this rom and restore a backup without restoring the boot.img ?
Click to expand...
Click to collapse
You don't have to install custom ROM to get root. If you are currently on MIUI 11.0.10, you download that exact ROM, unpack it and copy boot.img to your phone. Then you install Magisk manager and use it to patch boot.img. You will get a patched boot.img which you flash in fastboot.
Ok, Is there a way to backup 'cause it says "Unlock will erase user data"
EDIT: OK I found a way to backup using MIAssistant
EDIT 2: MIAssistant is outdated any way to backup ?
I don't know. I didn't have anything important to backup.
kalehrl said:
I don't know. I didn't have anything important to backup.
Click to expand...
Click to collapse
Ok I found that you can local backup from settings but what I'm worried is losing my efs partition hope it goes right I have joyuse (9 pro)
I have 9s and all went fine.
However, I installed the custom ROM from that thread and root as well.
Now, I have to wait 168 hours (one week) to unlock
That's normal but annoying.
Yea BUT *sniff* BUT *sniff* *sniff* WHY
(ded meme)
EDIT:. BTW what does oem unlocking in developer setting mean ?
And thanks a lot man I couldn't have done this without you.
Enable it to be on the safe side when you apply for unlocking even though I don't think it's necessary for official Xiaomi unlocking. I think it's for unofficial unlocking 'oem-unlock go' which I don't think works.
Is there Twrp For joyuse (9 pro ?) i searched the fornm and i couldn't find it.
The Only One i could find was https://forum.xda-developers.com/re...nt/recovery-unofficial-pbrp-recovery-t4137753
And is this what you exactly mean ? https://forum.xda-developers.com/re.../how-to-unlock-root-redmi-9-9s-9-pro-t4108913
Cilekcigs said:
Ok, Is there a way to backup 'cause it says "Unlock will erase user data"
EDIT: OK I found a way to backup using MIAssistant
EDIT 2: MIAssistant is outdated any way to backup ?
Click to expand...
Click to collapse
Just transfer the files you want to backup from your phone to PC and later copy back. Apps, SMS, call log, wifi passwords etc. are backed up to your Google account (if you have enabled backup/restore), you can backup some extra stuff in MiCloud too (I don't use it, don't wanna give em my data lol, it's enough that google has it).
FYI local backup will get wiped after unlocking.
I'd recommend you stay away from TWRP because there is no official version and it's unstable. I've read reports of people bricking their devices and losing widevine L1 after installing it. Just use Xiaomi's recovery and fastboot because they're enough for both rooting and installing custom ROMs.
manpildo said:
Just transfer the files you want to backup from your phone to PC and later copy back. Apps, SMS, call log, wifi passwords etc. are backed up to your Google account (if you have enabled backup/restore), you can backup some extra stuff in MiCloud too (I don't use it, don't wanna give em my data lol, it's enough that google has it).
FYI local backup will get wiped after unlocking.
Click to expand...
Click to collapse
No i just want to make sure i don't lose my efs
Hey folks,
So somehow when unlocking my bootloader with the unlock_key/code from OnePlus, I switched the ROM from the T-Mobile variant to the stock OnePlus variant. I may have corrupted/wiped one of the two slots and gotten lucky, that was months ago and I've forgotten.
Mostly I wanted to confirm an unlocked bootloader in the event there is a stable and up-to-date ROM made available on this device. It's my primary phone and I don't want to be alpha testing updates, so I'm happy with the stock OnePlus OS.
However, my device won't apply updates. I'm NOT rooted, though the bootloader is unlocked. What are my options for applying updates?
Do I need to re-enable bootloader via adb, which will likely wipe the OS and require re-configuration of all my apps and settings? If I apply root (and wipe-OS), can the root receive updates easily?
Been about two months now without the latest security patch, things could be worse but I definitely want to update!
ANy thoughts are appreciated, thanks!
lifebringer123 said:
Hey folks,
So somehow when unlocking my bootloader with the unlock_key/code from OnePlus, I switched the ROM from the T-Mobile variant to the stock OnePlus variant. I may have corrupted/wiped one of the two slots and gotten lucky, that was months ago and I've forgotten.
Mostly I wanted to confirm an unlocked bootloader in the event there is a stable and up-to-date ROM made available on this device. It's my primary phone and I don't want to be alpha testing updates, so I'm happy with the stock OnePlus OS.
However, my device won't apply updates. I'm NOT rooted, though the bootloader is unlocked. What are my options for applying updates?
Do I need to re-enable bootloader via adb, which will likely wipe the OS and require re-configuration of all my apps and settings? If I apply root (and wipe-OS), can the root receive updates easily?
Been about two months now without the latest security patch, things could be worse but I definitely want to update!
ANy thoughts are appreciated, thanks!
Click to expand...
Click to collapse
If you do a factory reset with the MSM tool you will get the T-Mobile ROM back and it will also relock the bootloader (and of course wipe all your apps and settings). You will definitely be able to get updates that way. I don't know if there is a way to get updates without wiping all of your data.
towardsdawn said:
If you do a factory reset with the MSM tool you will get the T-Mobile ROM back and it will also relock the bootloader (and of course wipe all your apps and settings). You will definitely be able to get updates that way. I don't know if there is a way to get updates without wiping all of your data.
Click to expand...
Click to collapse
OK, thank you! I will give it a try eventually...
Any recommended ROMS that are lightweight but super stable and also regularly updated? Like LineageOS (which I believe is not updated for this phone)...
nothing beats stock in stability period. yes you can update vs stock OTA on unlocked bootloader
You can also update and receive OTA while rooted with magisk, my current method is here:
1) click "try again." click "resume" which may or may not reboot the device.
2) adb reboot fastboot
3) fastboot boot previous_magiskpatched_boot.img
4) find active slot with adb shell /bin/getprop ro.boot.slot_suffix
5) dd
if=/dev/block/bootdevice/by-name/boot_a_or_b of=/sdcard/Download/boot.img to backup stock boot.img
6) direct install magisk, reboot
7) repeat step 5 to backup patched boot.img
8) adb pull sdcard/Download patched and stock.img
towardsdawn said:
You can also update and receive OTA while rooted with magisk, my current method is here:
1) click "try again." click "resume" which may or may not reboot the device.
2) adb reboot fastboot
3) fastboot boot previous_magiskpatched_boot.img
4) find active slot with adb shell /bin/getprop ro.boot.slot_suffix
5) dd
if=/dev/block/bootdevice/by-name/boot_a_or_b of=/sdcard/Download/boot.img to backup stock boot.img
6) direct install magisk, reboot
7) repeat step 5 to backup patched boot.img
8) adb pull sdcard/Download patched and stock.img
Click to expand...
Click to collapse
thanks!
Ytube21 said:
nothing beats stock in stability period. yes you can update vs stock OTA on unlocked bootloader
Click to expand...
Click to collapse
Are you saying that if I re-lock my bootloader, it will NOT wipe my OS/factory reset, and I'll be able to update the OS via OTA updates?
Remember, bootloader is unlocked but I'm on the stock ROM (not the T-Mobile ROM, though this is the physical T-Mobile variant).
lifebringer123 said:
Are you saying that if I re-lock my bootloader, it will NOT wipe my OS/factory reset, and I'll be able to update the OS via OTA updates?
Remember, bootloader is unlocked but I'm on the stock ROM (not the T-Mobile ROM, though this is the physical T-Mobile variant).
Click to expand...
Click to collapse
Hello there, lifebringer123.
I believe Ytube21 made a grammatical error in his response to you. I believe what he intended to imply was that, with an unlocked bootloader, you can install OTA updates on the stock ROM.
Because the phone will be transitioning from a non-assured software integrity state and unprotected personal data condition to a guaranteed software integrity state and protected data condition, relocking the bootloader will result in a factory reset to ensure no trace of a root related process capable of accessing /data.
Since I assume you don't have unlocked firmware, I'm guessing you don't have the "Local upgrade" option in settings (Settings -> System -> System update -> Gear settings icon in top right corner -> Local upgrade), which means you're missing out on the most direct and authentic way of installing OTA updates.
However, I have another idea in mind, which I'm not sure will work, but could if your circumstances allow it. Is it possible to install the most recent OnePlus Nord N200 OTA update after flashing TWRP?
Here's what I'm thinking:
1. Download the most appropriate TWRP image (Current most recent TWRP for OnePlus Nord N200)
2. Boot OnePlus Nord N200 into bootloader (adb reboot bootloader while the device is on, or, while the device is off, hold the volume down and power key for a while, release the power button when the OnePlus logo comes up (but keep pressing the volume down button), go appropriately through the menu (select suitable language, then choose Advanced -> Reboot to fastboot)
3. Ensure that fastboot detects your OnePlus Nord N200 (fastboot devices)
4. Momentarily boot into recovery (fastboot boot NameOfRecoveryHere.img (This will only boot the recovery, not install it)
5. Flash the desired OTA update .zip file using the recovery and reboot
Note: Your build number will be useful for me to point you in the right direction for finding the appropriate .zip for the OTA update (Step 5)
Apart from the way described above, I'm very confident you won't be able to properly apply updates without wiping your phone. I would suggest just backing up your phone (Save anything you want to preserve) to a secure location and then following the procedures mentioned by towardsdawn of utilizing MSM tools to restore the T-Mobile ROM.
If you have any questions or issues, please let me know.
Aselloph said:
Hello there, lifebringer123.
I believe Ytube21 made a grammatical error in his response to you. I believe what he intended to imply was that, with an unlocked bootloader, you can install OTA updates on the stock ROM.
Click to expand...
Click to collapse
The OS notices the OTA updates, but it cannot apply/install them no matter what I do to try.
Aselloph said:
Because the phone will be transitioning from a non-assured software integrity state and unprotected personal data condition to a guaranteed software integrity state and protected data condition, relocking the bootloader will result in a factory reset to ensure no trace of a root related process capable of accessing /data.
Click to expand...
Click to collapse
Makes sense; thanks.
Aselloph said:
Since I assume you don't have unlocked firmware, I'm guessing you don't have the "Local upgrade" option in settings (Settings -> System -> System update -> Gear settings icon in top right corner -> Local upgrade), which means you're missing out on the most direct and authentic way of installing OTA updates.
Click to expand...
Click to collapse
That is correct; I don't have that option. I also no longer have the "T-Mobile" Splash sceen on startup, my assumption since doing this earlier this year was that I may have wiped the t-mobile branded ROM variant, and the phone reverted to the "slot B" stock variant. But I could be wrong. In any case...
Aselloph said:
However, I have another idea in mind, which I'm not sure will work, but could if your circumstances allow it. Is it possible to install the most recent OnePlus Nord N200 OTA update after flashing TWRP?
Here's what I'm thinking:
1. Download the most appropriate TWRP image (Current most recent TWRP for OnePlus Nord N200)
2. Boot OnePlus Nord N200 into bootloader (adb reboot bootloader while the device is on, or, while the device is off, hold the volume down and power key for a while, release the power button when the OnePlus logo comes up (but keep pressing the volume down button), go appropriately through the menu (select suitable language, then choose Advanced -> Reboot to fastboot)
3. Ensure that fastboot detects your OnePlus Nord N200 (fastboot devices)
4. Momentarily boot into recovery (fastboot boot NameOfRecoveryHere.img (This will only boot the recovery, not install it)
5. Flash the desired OTA update .zip file using the recovery and reboot
Note: Your build number will be useful for me to point you in the right direction for finding the appropriate .zip for the OTA update (Step 5)
Apart from the way described above, I'm very confident you won't be able to properly apply updates without wiping your phone. I would suggest just backing up your phone (Save anything you want to preserve) to a secure location and then following the procedures mentioned by towardsdawn of utilizing MSM tools to restore the T-Mobile ROM.
If you have any questions or issues, please let me know.
Click to expand...
Click to collapse
Model DE2118
Build 11.0.1.9.DE18CB
ONE PLUS Nord N200 5G
(dre8t, but unlocked bootloader via unlock_code.bin)
I would give that a whirl if you could point me to the current OTA update .zip package. However, I bookmarked that TWRP thread months ago, but it still hasn't been updated, and I never did get it working correctly. But I'll try it. If it works and the manual OTA update .zip is only monthly/quarterly, the inconvenience is not severe. Still, I'm not using root or any custom ROM at the moment, so I should really go back to a locked bootloader so I can receive OTA updates, and suck up the loss of a few hours of restoring settings/apps...
Again (for all on thread), if there is a solid Custom ROM which regularly gets security updates, please point me to that thread/ROM! The
Thank you so much for your time!
Successful conversion of N200 5G from T-Mo to OEM without MSM tool! (Credit to Summersofar)
Hey there. i'm a new XDA Member myself. i've been mostly stalking these forums for the N200 Ever since people started the root phase and twrp projects for codename HOLI. but i'm here to convert @summersofar's guide in order to make it more...
forum.xda-developers.com
Try re-doing it. First, use MSM tool to return to Tmo, then unlock the bootloader again, then follow that guide.
It should completely fix your broken slots. And yes, my phone is rebranded, and it can apply updates perfectly.
I'm even rooted.
justauserthatusesaphone said:
Successful conversion of N200 5G from T-Mo to OEM without MSM tool! (Credit to Summersofar)
Hey there. i'm a new XDA Member myself. i've been mostly stalking these forums for the N200 Ever since people started the root phase and twrp projects for codename HOLI. but i'm here to convert @summersofar's guide in order to make it more...
forum.xda-developers.com
Try re-doing it. First, use MSM tool to return to Tmo, then unlock the bootloader again, then follow that guide.
It should completely fix your broken slots. And yes, my phone is rebranded, and it can apply updates perfectly.
I'm even rooted.
Click to expand...
Click to collapse
Thanks! When OTA updates end for our OS, in 1-2 years, what will you do? Switch phones, or do you think you have a custom ROM/OS that sounds stable enough?
I'll try the MSM tool, debate rooted or not, then report back...
Thanks again all!
lifebringer123 said:
Thanks! When OTA updates end for our OS, in 1-2 years, what will you do? Switch phones, or do you think you have a custom ROM/OS that sounds stable enough?
I'll try the MSM tool, debate rooted or not, then report back...
Thanks again all!
Click to expand...
Click to collapse
you're welcome, sorry for being late lol
after 2-3 years, ill probably keep this phone and install lineageos or pixel experience (that is, if it gets support)
although by that time, the trade in value is probably 2 dollars so I'll use it if i ever get into android development.
Any word on custom ROMs for this like Lineage OS or Pixel Experience?
Yesterday, decided to remove bloatware(mostly Google) on my Huawei p8 lite using ADB. And somehow removed this.
:/ $ pm uninstall -k --user 0 com.android.location.fused
Restarted.
Boot Loop.
Before I rebooted my phone usb debugging was on.
Phone boots into eRecovery with 4 options
1)Download latest version and recovery(usuless gives my an "Getting package info failed")
2)Wipe data/factory reset
3)Reboot
4)Shutdown
When I'm connected to pc I allways get a message "Unable to open MTP device".
I don't have the root privalage so I can't folow these steps in this guide below.
Bootloop after removing com.android.location.fused [SOLVED]My questions is:
1. Any method of saving data on bootloop phone without root?
2. Should I try factory reset?
I don't understand what you want, but you can't root in boot loop.
But I hear you will root, it's really easy to root Huawei!
Guide.
1. Get your firmware, with hisuite, after install downgrade or update, will firmware file be saved in document folder on PC.
2. Extract files inside the firmware file, and find the boot.img, system.img or boot.img and opened it and modified, some you will and repack it again.
3. Update hash's for partition controller.
4. Make a form of server and port forward your device to think this is the server there get updating from and see request some your phone ask for or read source of Huaweis update.apk.
4. Configure your server, with coding and upload the firmware to your server.
5. Now just install your update and you have custom os
JonasHS said:
But I hear you will root, it's really easy to root Huawei!
Click to expand...
Click to collapse
This guide is missing most important predecessor step: unlocking bootloader (and therefore useless)
JonasHS said:
I don't understand what you want, but you can't root in boot loop.
Click to expand...
Click to collapse
Thanks for reply. Sorry that I not spicified. My problem is that I unistalled com.android.location.fused witch resulted in boot loop. My phone is not rooted and I don't know what to do next. Only think I can is factory reset, becouse eRecovery gives me an error. I just looking right now for any way to save my data. I found a similar problem solved, but person rooted phone before boot loop. So I guess I only have 1 option then?
You can try to start you Huawei in back up mode,
JonasHS said:
You can try to start you Huawei in back up mode,
Click to expand...
Click to collapse
Yes my phone in recovery mode. Should I try "Wipe data/factory reset"? Because "Download latest version and recovery" option gives me an error"Getting package info failed".
You don't need to unlock bootloader for edit system, i making my own exploit and do it.
O just look at this:
We say you can't edit Any software file on your device, because you don't has permission, like Linux nonroot user.
There are only 1 way to get this permission, it's unlocking bootloader and add your code to software.
NOT TRUE.
if we put this together with a door that's locked and you don't have the key, what do you do?
I will find another way to open the door.
so to show what i mean: update.apk ask server for download the update and send it back too your phone, and your phone will install. Inside an update package, where are boot.img and system.img, what if we edit this file before update, and put a code some will give your user on system the highest privilege. But we can't edit this file, because they are saved on folder, we don't has permission too?
For do this, can we manipulate the data server send back too us.
Prot forwarding.
JonasHS said:
You don't need to unlock bootloader for edit system, i making my own exploit and do it.
Click to expand...
Click to collapse
So you're a hacker and found method to properly sign system.img with huawei's private oem key? you're a genius!
https://android.googlesource.com/platform/external/avb/+/master/README.md#The-VBMeta-struct
Unfortunately the repair has to be done in /data/system/users/0/package-restrictions.xml and requires root access. Furthermore /data is encrypted therefore that modification can't be done offline, it requires booted android to stage where we can enter screen unlock pin (or at least to stage where /data/system is decrypted)
JonasHS said:
You don't need to unlock bootloader for edit system, i making my own exploit and do it.
O just look at this:
We say you can't edit Any software file on your device, because you don't has permission, like Linux nonroot user.
There are only 1 way to get this permission, it's unlocking bootloader and add your code to software.
NOT TRUE.
if we put this together with a door that's locked and you don't have the key, what do you do?
I will find another way to open the door.
so to show what i mean: update.apk ask server for download the update and send it back too your phone, and your phone will install. Inside an update package, where are boot.img and system.img, what if we edit this file before update, and put a code some will give your user on system the highest privilege. But we can't edit this file, because they are saved on folder, we don't has permission too?
For do this, can we manipulate the data server send back too us.
Prot forwarding.
Click to expand...
Click to collapse
That sounds awesome. I guess we can try.
aIecxs said:
So you're a hacker and found method to properly sign system.img with huawei's private oem key? you're a genius!
https://android.googlesource.com/platform/external/avb/+/master/README.md#The-VBMeta-struct
Unfortunately the repair has to be done in /data/system/users/0/package-restrictions.xml and requires root access. Furthermore /data is encrypted therefore that modification can't be done offline, it requires booted android to stage where we can enter screen unlock pin (or at least to stage where /data/system is decrypted)
Click to expand...
Click to collapse
Dahm.
The easiest way to fix bootloop is factory reset. There is no way to safe userdata without fixing bootloop, sorry. it's a hen and egg dilemma.
aIecxs said:
The easiest way to fix bootloop is factory reset. There is no way to safe userdata without fixing bootloop, sorry. it's a hen and egg dilemma.
Click to expand...
Click to collapse
I agree.
Just reset its easiest.
Think about this here: your PC has SSD or HDD and you can take it off and take it into new pc, and edit everythiny on the disk without admin and make a backup.
The true is, you can do the same with a phones chip, but it's hard to do
Next time, before playing with packages, do a backup of your pictures.
Btw you can unlock bootloader with PotatoNV and root with Magisk. rooted devices you can backup with Migrate or TWRP.
New to said:
Yes
Huawei don't store theres OEM keys on devices chip, so they will never could control if i replaced it with my own, and avb will still work in offline mode, so I can just read vbmeta.img with avbtool.py and generate the same vbmeta.img with different size or hash of partitions, some is benn modified.
Click to expand...
Click to collapse
You could me a hacker, i am not a hacker, i have just a good kwoning of code and dissembling
JonasHS said:
Just reset its easiest.
Think about this here: your PC has SSD or HDD and you can take it off and take it into new pc, and edit everythiny on the disk without admin and make a backup.
The true is, you can do the same with a phones chip, but it's hard to do
Click to expand...
Click to collapse
aIecxs said:
Next time, before playing with packages, do a backup of your pictures.
Btw you can unlock bootloader with PotatoNV and root with Magisk. rooted devices you can backup with Migrate or TWRP.
Click to expand...
Click to collapse
Thanks for replys(they gived me alot of ideas what I can learn about phone and hacking).I will be more careful about deleting packages in future.
I just did Factory reset and my phone is working fine again.
JonasHS said:
Huawei don't store theres OEM keys on devices chip, so they will never could control if i replaced it with my own, and avb will still work in offline mode, so I can just read vbmeta.img with avbtool.py and generate the same vbmeta.img with different size or hash of partitions, some is benn modified.
Click to expand...
Click to collapse
Of course they don't. No, you can't flash own vbmeta.img on locked bootloader as the bootloader verifies the hash of vbmeta which is oem signed (you don't have key).
If you know about any flash tool for HiSilicon Kirin exist (IDT?) it would probably easier to flash magisk patched (properly avb signed) ramdisk.img to get root access and adb (osm0sis AIK is capable of signing AVBv2) instead of modifying system.
Nevertheless this won't fix bootloop therefore it's pointless, as the culprit lies in package-restrictions.xml. it's impossible to decrypt userdata partition offline, so there is no hope sorry.
Who has told you this here, i am developer and has readers the source code, yes you can make your own sign keys with openssl
yes, that is called user-settable root of trust and requires you to compile own complete ROM, for example LineageOS. In any case that is impossible with stock EMUI as again you can't cheat Android Verified Boot chain of trust per design. That's the whole purpose of locked bootloader.