Related
Code:
Mi4c Flash TWRP‘s recovery and CM’s ROW without unlock BL
How：
1. From the high version down to a low version with root permission.
rom: libra_images_6.1.7_20151221.0000.11_5.1_cn
2. We can get root permission at the vertion of libra-6.1.7
a)So We can use dd command.
b)And the version can use fastboot command.
I tested it. It was ok.
Steps：
一．Prepare
1. Download miflash
bigota。d.miui。com/tools/MiFlash20150601_win10.exe
2.Download libra_images_6.1.7
bigota。d.miui。com/6.1.7/libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0.tgz
3.Download recovery
www。teamsuperluminal。org/recovery
二．TODO
1. Goto 9008 : adb reboot edl
2. To flash libra_6.1.7 with miflash tool
3. Reboot; adb push recovery.img /storage/emulated/legacy/
4. 130|[email protected]:/ $ su
5. 130|[email protected]:/ # dd if=/storage/emulated/legacy/recovery.img of=/dev/block/bootdevice/by-name/recovery
6. Enjoy yourself.
BY Eismog
Thanks qimuzhi!
Is it recommended to backup the IMEI / efs before replacing the recovery?
If so, can you point to (or add) relevant instructions?
Thanks!
I have no idea what this is about. Is this a way to install TWRP on a rooted mi4c by dd even though bootloader is locked? Doesn't this work only when bootloader is unlocked?
What does qimuzhi want to tell us??
qtotter said:
What does qimuzhi want to tell us??
Click to expand...
Click to collapse
Basically, you can roll back to an older developer version with an unlocked bootloader and then install TWRP.
This is a complicated way for anyone with a working locked bootloader Mi4c to downgrade the rom and flash TWRP:
You need to reboot to EDL ( Emergency DownLoad) mode, you can only do this from adb with working phone
Then flash an old unlocked rom with MIflash Tool (not sure this work with locked BL)
Then boot the phone, gain su right, and flash recovery whit dd command
You can save time after flashing the rom with unlocked bootloader, simply shut down the phone and boot in fastboot before the rom inizialization
With an unlocked phone you can simply push recovery from fastboot with " fastboot flash recovery recovery.img" command then boot into recovery
I see. It was known that you can go back to unlocked bootloader by flashing the stable 7.0.16.0 over the latest locked dev ROM, but this is a way to roll back to an older dev ROM with unlocked bootloader from the latest dev ROM as long as it's working (not boot-looping or softbricked.)
Is my understanding correct?
---------- Post added at 08:04 AM ---------- Previous post was at 07:41 AM ----------
ice-it said:
This is a complicated way for anyone with a working locked bootloader Mi4c to downgrade the rom and flash TWRP:
Click to expand...
Click to collapse
So, it doesn't have to be dev ROM 6.1.7, and you can also use stable 7.0.16.0 ROM instead?
qtotter said:
I see. It was known that you can go back to unlocked bootloader by flashing the stable 7.0.16.0 over the latest locked dev ROM, but this is a way to roll back to an older dev ROM with unlocked bootloader from the latest dev ROM as long as it's working (not boot-looping or softbricked.)
Is my understanding correct?
---------- Post added at 08:04 AM ---------- Previous post was at 07:41 AM ----------
So, it doesn't have to be dev ROM 6.1.7, and you can also use stable 7.0.16.0 ROM instead?
Click to expand...
Click to collapse
I think the stable build is the only possible to use from updater app...
He is using dev rom because he need su right to flash recovery in his way...
Itamar01 said:
Is it recommended to backup the IMEI / efs before replacing the recovery?
Click to expand...
Click to collapse
The recovery partition is totally different from the area where efs is stored... You also asked the same question at miui.com, and someone already answered...
http://forum.xda-developers.com/android/apps-games/app-partitions-backup-t3003599
---------- Post added at 09:25 AM ---------- Previous post was at 08:32 AM ----------
ice-it said:
I think the stable build is the only possible to use from updater app...
Click to expand...
Click to collapse
There are two kinds of ROM formats. One is recovery compatible ROM which you can flash from recovery or from updater app. You need to use full ROMs, not incremental ROMs (patch files) to switch between ROMs.
The other is what they call fastboot ROM which you can flash from bootloader or from miflash. Basically, fastboot ROMs are simply a zipped file containing all the partition images and scripts. miflash simply extracts images from a zipped file and automatically flashes the images in order. You can do it manually, using the bat or sh scripts in the same zipped file.
ice-it said:
He is using dev rom because he need su right to flash recovery in his way...
Click to expand...
Click to collapse
I think the point here is you can roll back to older ROMs using edl mode. Obviously, bootloader ignores the lock/unlock flag or ROM versions in edl mode at the moment until Xiaomi fixes this hole. (I suppose Xiaomi will disable edl mode soon...)
Once you are back on unlocked ROMs, I don't think you need su just for flashing recovery. You can simply go to bootloader and flash recovery by 'fastboot flash recovery recovery.img', can't you?
qtotter said:
There are two kinds of ROM formats. One is recovery compatible ROM which you can flash from recovery or from updater app. The other is what they call fastboot ROM which you can flash from bootloader or from miflash.
Click to expand...
Click to collapse
yeah sure, i was not clear before, i mean you cant roll back from updater app with an old dev rom, but you can move to stable and this will unlock your bootloader
fastboot version is useless because the locked bootloader
qtotter said:
I think the point here is you can roll back to older ROMs using edl mode. Obviously, bootloader ignores the lock/unlock flag or ROM versions in edl mode at the moment until Xiaomi fixes this hole. (I suppose Xiaomi will disable edl mode soon...)
Once you are back on unlocked ROMs, I don't think you need su just for flashing recovery. You can simply go to bootloader and flash recovery by 'fastboot flash recovery recovery.img', can't you?
Click to expand...
Click to collapse
I hope EDL will ignore the locked bl, but i cant verify with mi4c, in the past this worked with other manufacturer
like i said in a post earlier, if your phone is working there's no need to follow the procedure written by op, just flash stable through updater app and recovery from fastboot like you said
if they disable EDL mode then they could have trouble repairing phone in less than an hour like they do in china
ice-it said:
fastboot version is useless because the locked bootloader
Click to expand...
Click to collapse
No, it's opposite. Fastboot ROMs are useful because it was found that you can flash any fastboot ROMs locked or unlocked in edl mode at the moment!
Again, as you said, this method only works on a working phone. Not a savior for those who got their phones bootlooped...
---------- Post added at 10:10 AM ---------- Previous post was at 10:00 AM ----------
ice-it said:
like i said in a post earlier, if your phone is working there's no need to follow the procedure written by op, just flash stable through updater app and recovery from fastboot like you said
Click to expand...
Click to collapse
I saw some people got bootloop while switching from dev ROM to stable 7.0.16.0 by updater app in order to regain unlocked bootloader. This method seems safer to me...
Partitions Backup & Restore
qtotter said:
The recovery partition is totally different from the area where efs is stored... You also asked the same question at miui.com, and someone already answered...
http://forum.xda-developers.com/android/apps-games/app-partitions-backup-t3003599
Click to expand...
Click to collapse
Thanks for the link! Partitions Backup & Restore looks like a very useful app!
BTW, I managed to run TWRP from fastboot and make a backup of the system but it did not have the option to backup the EFS and the Modems
Itamar01 said:
Thanks for the link! Partitions Backup & Restore looks like a very useful app!
BTW, I managed to run TWRP from fastboot and make a backup of the system but it did not have the option to backup the EFS and the Modems
Click to expand...
Click to collapse
TWRP does not always come with efs backup option. It's dev's choice whether it's included or not. The method is all the same as Partitions Backup & Restore, anyway.
qtotter said:
I saw some people got bootloop while switching from dev ROM to stable 7.0.16.0 by updater app in order to regain unlocked bootloader. This method seems safer to me...
Click to expand...
Click to collapse
Maybe it's because the rom version? I know people who use the 7.1.6.0 to roll back...
If it's working could be safer, we need someone who can try and report back
ice-it said:
Maybe it's because the rom version? I know people who use the 7.1.6.0 to roll back...
If it's working could be safer, we need someone who can try and report back
Click to expand...
Click to collapse
True. Personally, I'd stay away from any ROMs with locked bootloader, and only use fastboot to flash images. Flashing ROMs including bootloader (locked or unlocked) via recovery or updater app seems kinda risky to me.
It looks like too many people who don't know what they're doing are playing with ROMs and bricking their Xiaomi phones. There are guides introducing flashing dev ROMs only for rooting. It's rather shocking...
qtotter said:
It looks like too many people who don't know what they're doing are playing with ROMs and bricking their Xiaomi phones. There are guides introducing flashing dev ROMs only for rooting. It's rather shocking...
Click to expand...
Click to collapse
Yeah I know, people actually don't know what they're doing and why, they read but they can't understand what's written, and take all for absolute truth...
Then they open a post here and there, crying and complaining
I have my mi4c locked. There is any method to put the device in EDL mode? I only can put him in fastboot and I can't run adb commands.
n1k3z0n3 said:
I have my mi4c locked. There is any method to put the device in EDL mode? I only can put him in fastboot and I can't run adb commands.
Click to expand...
Click to collapse
Hello and welcome to XDA! ( I'm Fede91 from en.miui )
Sorry, but it seems that adb is the only way, I've searched the net for days but every method I tried doesn't work...
I think we need to tamper with the hardware to put the phone in edl...
ice-it said:
Hello and welcome to XDA! ( I'm Fede91 from en.miui )
Sorry, but it seems that adb is the only way, I've searched the net for days but every method I tried doesn't work...
I think we need to tamper with the hardware to put the phone in edl...
Click to expand...
Click to collapse
Hi Fede91 .
Yeah I did the same without any result :S. This is frustating . I allready created another account and I'm trying to get to diamond to see if I get an unlock code. I'm tired of waiting for another solution
Can you install a custom rom after doing this?
//EDIT:
Well this was to easy, I started out on 7.1.6.0 Global Stable (locked Bootlader), then I just flashed the 7.0.16.0 Global Stable, installed twrp via fastboot, then did "/fastboot oem unlock" which worked (don't know if it was necessary) and after all that installed sMIUI after doing a full wipe. sMIUI up and running!
二．TODO
1. Goto 9008 : adb reboot edl
2. To flash libra_6.1.7 with miflash tool
3. Reboot; adb push recovery.img /storage/emulated/legacy/
4. 130|[email protected]:/ $ su
5. 130|[email protected]:/ # dd if=/storage/emulated/legacy/recovery.img of=/dev/block/bootdevice/by-name/recovery
6. Enjoy yourself.
Can someone provide a step by step tutorial for this?
WARNING: THIS HAS BRICKED PHONES! It is suspected that having an encrypted phone causes these bricks, but that has not been confirmed. If your data partition is encrypted, it is extra important that you perform a factory reset before taking this OTA. Doing this will remove the encryption.
WARNING: INSTALLING THIS ON A LOCKED BOOTLOADER WILL ELIMINATE ALL CHANCE OF YOU EVER UNLOCKING YOUR BOOTLOADER.
If your bootloader is unlocked, it will not be re-locked after this update.
Do NOT flash this using TWRP. If you want to do that, use this version: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
So if you're a bad enough dude to flash this anyway, follow these instructions:
1. Backup all data on your phone. It will be lost.
2. If your bootloader is locked, make sure you are on SU4TL-49. If you aren't, take all available OTAs until you are.
3. If your bootloader is unlocked and you have TWRP installed, flash SU4TL-49 using this package: https://mega.nz/#!3xRhiaSR!KxH2Ya_BYK4zBjrxmej7dqaaDJVT1coTFJVJ5Fvb2WM
4. If you have TWRP installed on your phone, download the stock SU4TL-49 recovery here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8 and install it using the install image option in the install menu in TWRP. Reboot to recovery.
3. Perform a factory reset using the stock recovery menu. This will wipe all data and ensure that everything is formatted exactly as it should be.
4. Boot the phone normally and place the marshmallow update on the root of the directory that pops up when you plug in your phone.
5. Boot to recovery and at the stock recovery menu, select "apply update from sdcard."
6. Select the update and cross your fingers.
Get the update here: https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
TheSt33v said:
WARNING: THIS HAS BRICKED PHONES! Do not use this unless you know what you're doing.
I will do my best to provide more detailed instructions later today. Good luck.
https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
Click to expand...
Click to collapse
Are you sure that that file is the right one? It has the same version number as su4tl-49.
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
I'm positive. I seem to remember they did the same thing with SU4TL-49. The OTA was named after SU4TL-44 for some reason.
This is the stock recovery version, correct?
koftheworld said:
This is the stock recovery version, correct?
Click to expand...
Click to collapse
Correct. You install this using the sideload option in the stock recovery.
TheSt33v said:
Correct. You install this using the sideload option in the stock recovery.
Click to expand...
Click to collapse
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Thank you, now we can see what can be done with the new modem, kernel, etc...
Looking forward to a plethora of improvements to our phones
koftheworld said:
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Click to expand...
Click to collapse
I'm testing the TWRP version now. It should be up shortly.
EDIT: I flashed it and it seems to work fine. Uploading now. Should be up in a few hours. I'll check on it after I go run some errands real quick.
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Sweet. I am going to wait till it is more stable. I do have a bad esn Turbo but I will need to unlock to bootloader to test.
Mirror for people having "quota exceeded" error at Mega
https://yadi.sk/d/AhmhE-yX32E84p
Rename to Blur_Version.24.81.5.quark_verizon.verizon.en.US.zip before use, throw in internal storage, and check for updates.
PS: I have 64Gb Employee Edition, and still had not receive update by air. What a shame, VZ! )
kitcostantino said:
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Click to expand...
Click to collapse
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
TheSt33v said:
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
Click to expand...
Click to collapse
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
kitcostantino said:
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
Click to expand...
Click to collapse
Strange. Try reflashing SU4TL-49. If my TWRP package doesn't do it for you, use the full firmware package and do it manually with fastboot.
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
s5610 said:
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
Click to expand...
Click to collapse
lol. lawd, No. Ive been rocking status 3 for over a year.
As a tip, if anyone else with an unlocked bootloader runs into this,
what i had to do was restore my su-44 unmodified backup, OTA to SU-49, and then, after confirming my
q/e status was 0/1 i was able to update via the file in my Mega download folder. all is well now. they even added the newer version of command center. sweet. thank you all!!
It works in LOCKED BOOTLOADER??? .-.
square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Um, I couldn't tell you.i be been unlocked since the day Sunshine could unlocked our bootloader's. What I can tell you is you should absolutely unlock that via Sunshine before you even dream of applying this update. There will never be another opportunity.
Just my
.02. This is likely the last update for this phone, and your only chance of seeing N is via custom Roms.
TWRP version up now: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Yes it should. See instructions in OP.
Hey everyone, I've been lurking around for about two months, from when I picked up this phone. It's still completely stock. Unrooted, S-ON, all that. Well, after the update to Nougat, I've been searching for a way to unlock the bootloader & root. Is it safe for me to use WinDroid Toolkit for the process? Just need a guide for the process, for the most part. I appreciate any help that anyone is willing to offer.
acesavant00 said:
Is it safe for me to use WinDroid Toolkit for the process? Just need a guide for the process, for the most part. I appreciate any help that anyone is willing to offer.
Click to expand...
Click to collapse
Go to http://htcdev.com and make an account, then follow the steps and unlock your bootloader from there. After that you fastboot flash TWRP using ADB, and then use TWRP to flash a root solution. I prefer Magisk.
Alright, just unlocked the bootloader, going through the process of setting up my phone once again. Do you have a link to the Magisk & TWRP programs that I can use? Also, should I put the TWRP file in the same folder as the fastboot files?
I greatly appreciate the assistance you've given me so far, I'm deeply grateful man.
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
acesavant00 said:
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
Click to expand...
Click to collapse
try this step by step.. :good:
1.Flash TWRP 3.0.3-8 via Fastboot.. Do not reboot into system, enter into recovery..
2.Do a factory Reset via TWRP.. Do not reboot into system
3.Now flash SuperSU 2.79 SR3.. Reboot into system..
couple of bootloops are common, do not give up for at least 3 bootloops..
It will take a long time to boot as you have done a factory reset..
So be patient and wait for at least half hour..
acesavant00 said:
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
Click to expand...
Click to collapse
Sorry about this - I updated the TWRP thread with the current/preferred root method: MagiskSU.
You need to flash a stock boot.img and then flash the Magisk zip from the linked thread.
Captain_Throwback said:
Sorry about this - I updated the TWRP thread with the current/preferred root method: MagiskSU.
You need to flash a stock boot.img and then flash the Magisk zip from the linked thread.
Click to expand...
Click to collapse
Aw crap, I wish I would have seen this yesterday. I tried to format data & flash one of the stock rooted roms for marshmallow roms for my sprint one a9... now it just hangs at the HTC One logo. I'm gonna assume that I'm screwed until a stock rooted Nougat rom is released for sprint.
acesavant00 said:
Aw crap, I wish I would have seen this yesterday. I tried to format data & flash one of the stock rooted roms for marshmallow roms for my sprint one a9... now it just hangs at the HTC One logo. I'm gonna assume that I'm screwed until a stock rooted Nougat rom is released for sprint.
Click to expand...
Click to collapse
Can't you just flash the Nougat RUU?
Captain_Throwback said:
Can't you just flash the Nougat RUU?
Click to expand...
Click to collapse
I found the post about the Nougat RUU, but the program won't recognize my phone cause it won't boot. I'm gonna try & flash the firmware through TWRP.
acesavant00 said:
I found the post about the Nougat RUU, but the program won't recognize my phone cause it won't boot. I'm gonna try & flash the firmware through TWRP.
Click to expand...
Click to collapse
You don't flash firmware with TWRP. But you can use the SD card method to flash the RUU, which doesn't require a computer.
Captain_Throwback said:
You don't flash firmware with TWRP. But you can use the SD card method to flash the RUU, which doesn't require a computer.
Click to expand...
Click to collapse
Sorry to bother you again, but you wouldn't happen to know a method of extracting the rom.zip from the exe file, would you?
acesavant00 said:
Sorry to bother you again, but you wouldn't happen to know a method of extracting the rom.zip from the exe file, would you?
Click to expand...
Click to collapse
[TOOL][LINUX|WIN|MAC][64bit][29-SEP-2016]Universal HTC RUU/ROM Decryption Tool 3.1.0
Run the tool with the -z flag to output a zip to the "OUT" folder.
Captain_Throwback said:
[TOOL][LINUX|WIN|MAC][64bit][29-SEP-2016]Universal HTC RUU/ROM Decryption Tool 3.1.0
Run the tool with the -z flag to output a zip to the "OUT" folder.
Click to expand...
Click to collapse
Thank you so much, man. The zip is prepped, just gotta charge my phone again to 30%. But afterwards, will I have to go through the unlock bootloader process? If I do, I don't wanna mess up on the rooting process.
acesavant00 said:
Thank you so much, man. The zip is prepped, just gotta charge my phone again to 30%. But afterwards, will I have to go through the unlock bootloader process? If I do, I don't wanna mess up on the rooting process.
Click to expand...
Click to collapse
Your bootloader will stay unlocked.
Captain_Throwback said:
Your bootloader will stay unlocked.
Click to expand...
Click to collapse
Awesome, I appreciate all of the help, man. Sorry again if I annoyed you with all of my incessant questions. Just didn't wanna mess up my phone even further.
Hello Guys,
I Have an HTC one a9 with 7.0, s-off, bootloader locked
I have some concerns before I root my phone
If I unlock the bootloader and root the phone, Will I have the option of phone encryption as it used to be ?
If I unlock the bootloader with HTCDev and flash the TWRP with SuperSu and boot file, it is a MUST to do a data factory reset? or I`m able to do all the process without loosing my data?
Thank you in advance
rilley said:
Hello Guys,
I Have an HTC one a9 with 7.0, s-off, bootloader locked
I have some concerns before I root my phone
If I unlock the bootloader and root the phone, Will I have the option of phone encryption as it used to be ?
If I unlock the bootloader with HTCDev and flash the TWRP with SuperSu and boot file, it is a MUST to do a data factory reset? or I`m able to do all the process without loosing my data?
Thank you in advance
Click to expand...
Click to collapse
Unlocking your bootloader will wipe the device.
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
sandreas said:
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
Click to expand...
Click to collapse
+1 I`m interested on this question, I have Nougat installed
sandreas said:
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
Click to expand...
Click to collapse
rilley said:
+1 I`m interested on this question, I have Nougat installed
Click to expand...
Click to collapse
Yes, you can root and debloat Nougat. Though you should make a stock system image backup first of you ever want to receive an OTA again. The TWRP thread FAQ has a lot of information about this.
Problem: After a standard update(flash bootloader & radio, then update image) and standard rooting process(boot twrp, flash supersu), the device will keep rebooting
Possible reason: the latest bootloader(8996-012001-1703151359) may verify the system image in the phone to ensure it unchanged
Solution: after installing supersu in TWRP, flash the previous bootloader(8996-012001-1702151126) back and the device will start normally
If we sideload the ota and then flash old bootloader works?
Or we need to flash the entire factory image?
TENN3R said:
If we sideload the ota and then flash old bootloader works?
Or we need to flash the entire factory image?
Click to expand...
Click to collapse
Just old bootloader afterwards
Great, works for me.
Can you post specific instructions I really would like to unlock and root my phone
Any side effect of using old bootloader? Thank you.
[email protected] said:
Can you post specific instructions I really would like to unlock and root my phone
Click to expand...
Click to collapse
In fact, there are a lot of articles teaching you that.
For example, you can click here to know how to root.
vibranze said:
Any side effect of using old bootloader? Thank you.
Click to expand...
Click to collapse
No more side effects than not verifying the system image found yet.
Steven_Yang said:
Problem: After a standard update(flash bootloader & radio, then update image) and standard rooting process(boot twrp, flash supersu), the device will keep rebooting
Possible reason: the latest bootloader(8996-012001-1703151359) may verify the system image in the phone to ensure it unchanged
Solution: after installing supersu in TWRP, flash the previous bootloader(8996-012001-1702151126) back and the device will start normally
Click to expand...
Click to collapse
THANK YOU!! i have the bootloop issue that was driving me crazy and was unable to root properly, until i flashed the old bootloader
Read here. There is a fix that does not require downgrading the BL.
https://forum.xda-developers.com/showthread.php?t=3600606
Dear members plz suggest me a best solution for this problem plz
I have a pixel 2 (walleye) and few days ago i am unlocked my bootloader and i used sum custom os like linage os on my device this yesterday I have changed my mind and i flashed a stock factory images
But i do a mistake is i am flashed a Android 8.0 factory images that is walleyes first release frimware or factory images after i am flashed my device flashing process is susessful and it is booted normally and work fine but when I am now trying to flash latest version factory images that's besed on Android 11 it is showing me sum errors on flashing time what i do now
Theracerlucky said:
Dear members plz suggest me a best solution for this problem plz
I have a pixel 2 (walleye) and few days ago i am unlocked my bootloader and i used sum custom os like linage os on my device this yesterday I have changed my mind and i flashed a stock factory images
But i do a mistake is i am flashed a Android 8.0 factory images that is walleyes first release frimware or factory images after i am flashed my device flashing process is susessful and it is booted normally and work fine but when I am now trying to flash latest version factory images that's besed on Android 11 it is showing me sum errors on flashing time what i do now
Click to expand...
Click to collapse
The error is telling you exactly what you need to do - you need to update bootloader to the required version. If you are attempting to flash the factory firmware, the required bootloader and baseband files should be included in the zip file.
V0latyle said:
The error is telling you exactly what you need to do - you need to update bootloader to the required version. If you are attempting to flash the factory firmware, the required bootloader and baseband files should be included in the zip file.
Click to expand...
Click to collapse
I don't understand properly can you brother tell me with more details plz i tried already to flash sum upper versions bootloader factory images but showing this errors continue
Theracerlucky said:
I don't understand properly can you brother tell me with more details plz i tried already to flash sum upper versions bootloader factory images but showing this errors continue
Click to expand...
Click to collapse
The screenshot you posted describes the problem. When you flash a factory image, it first checks the device bootloader and baseband versions to make sure they are up to date. If they are out of date, you get the error as shown:
Device bootloader version is 'mw8998-002.0059.00'
Update requires 'mw8998-002.0076.00'
You need to update the bootloader and possibly the baseband version.
The absolute easiest way to flash the factory firmware is with the Android Flash Tool. Leave your device connected to your computer, and go to this link. Allow ADB keys access when requested. Before you flash, make sure you click the pencil icon to choose options, as the tool selects Wipe Device and Lock Bootloader by default.
If you are still trying to flash your device manually, make sure your Platform Tools are up to date.
V0latyle said:
The screenshot you posted describes the problem. When you flash a factory image, it first checks the device bootloader and baseband versions to make sure they are up to date. If they are out of date, you get the error as shown:
Device bootloader version is 'mw8998-002.0059.00'
Update requires 'mw8998-002.0076.00'
You need to update the bootloader and possibly the baseband version.
The absolute easiest way to flash the factory firmware is with the Android Flash Tool. Leave your device connected to your computer, and go to this link. Allow ADB keys access when requested. Before you flash, make sure you click the pencil icon to choose options, as the tool selects Wipe Device and Lock Bootloader by default.
If you are still trying to flash your device manually, make sure your Platform Tools are up to date.
Click to expand...
Click to collapse
But bro when I trying to flash with Android flash tool showing this errors
Theracerlucky said:
But bro when I trying to flash with Android flash tool showing this errors
Click to expand...
Click to collapse
I haven't seen that error before. Your bootloader is unlocked, right?
Theracerlucky said:
But bro when I trying to flash with Android flash tool showing this errors
Click to expand...
Click to collapse
"FAILED (remote: Command Flash Error)" -- When flashing bootloader
When I was flashing factory updates on my Pixel 2 last night, I got an error at the first step (using the flash-all.sh method), when it flashes the bootloader: sending 'bootloader_a' (38728 KB)... OKAY [ 2.095s] writing 'bootloader_a'...
forum.xda-developers.com
V0latyle said:
I haven't seen that error before. Your bootloader is unlocked, right?
Click to expand...
Click to collapse
Yes properly unlocked bro
Theracerlucky said:
"FAILED (remote: Command Flash Error)" -- When flashing bootloader
When I was flashing factory updates on my Pixel 2 last night, I got an error at the first step (using the flash-all.sh method), when it flashes the bootloader: sending 'bootloader_a' (38728 KB)... OKAY [ 2.095s] writing 'bootloader_a'...
forum.xda-developers.com
Yes properly unlocked bro
Click to expand...
Click to collapse
Bro can you please read this post for me i think it's the same like my issues but i don't understand this things properly what i do
Theracerlucky said:
Bro can you please read this post for me i think it's the same like my issues but i don't understand this things properly what i do
Click to expand...
Click to collapse
I don't say this to be rude, but if you don't know what you're doing, nor understand the basic concepts at play here, you shouldn't be tinkering with your phone.
It looks like the user who posted that thread was able to fix his issue by sideloading the OTA. Do you have a custom recovery such as TWRP installed, or is everything stock?
I can provide instructions on how to sideload the OTA later today, but I must emphasize how important it is for you to understand what you are doing, because doing something wrong could result in bricking your device.
Lastly, please don't call me "bro".
V0latyle said:
I don't say this to be rude, but if you don't know what you're doing, nor understand the basic concepts at play here, you shouldn't be tinkering with your phone.
It looks like the user who posted that thread was able to fix his issue by sideloading the OTA. Do you have a custom recovery such as TWRP installed, or is everything stock?
I can provide instructions on how to sideload the OTA later today, but I must emphasize how important it is for you to understand what you are doing, because doing something wrong could result in bricking your device.
Lastly, please don't call me "bro".
Click to expand...
Click to collapse
Ok sir i don't installed any custom recovery now my devices all things is stock
Alright. Here's how to sideload the OTA.
Connect your device to your PC.
Download Pixel 2 December 2017 OTA. You can also try the December 2020 OTA. Do not unzip or extract these files, you will use them as-is.
In bootloader mode, use the Volume + and - buttons to select Recovery Mode, then press the Power button.
You will arrive at a screen with a green Android and "No command". Hold down the Power button and click the Volume Up button.
You will now be in the recovery menu. Use the Volume buttons to select Apply update from ADB, then press the Power button.
On your PC, open a command window in Platform Tools. Use this command: adb sideload, insert a space, then drag and drop the OTA file you just downloaded into the command window.
Press Enter. The sideload process will begin. Once it finishes, you will be taken back to Recovery Mode. Select Reboot now.
Your device should boot into Android. At this point you should be able to reboot to bootloader and use the Android Flash Tool to flash your desired update.
V0latyle said:
Alright. Here's how to sideload the OTA.
Connect your device to your PC.
Download Pixel 2 December 2017 OTA. You can also try the December 2020 OTA. Do not unzip or extract these files, you will use them as-is.
In bootloader mode, use the Volume + and - buttons to select Recovery Mode, then press the Power button.
You will arrive at a screen with a green Android and "No command". Hold down the Power button and click the Volume Up button.
You will now be in the recovery menu. Use the Volume buttons to select Apply update from ADB, then press the Power button.
On your PC, open a command window in Platform Tools. Use this command: adb sideload, insert a space, then drag and drop the OTA file you just downloaded into the command window.
Press Enter. The sideload process will begin. Once it finishes, you will be taken back to Recovery Mode. Select Reboot now.
Your device should boot into Android. At this point you should be able to reboot to bootloader and use the Android Flash Tool to flash your desired update.
Click to expand...
Click to collapse
Sir i know this process but my tension is this process work properly or i brick my device
Theracerlucky said:
Sir i know this process but my tension is this process work properly or i brick my device
Click to expand...
Click to collapse
Sideloading the OTA is actually the safest way to update, and the least likely of bricking your device.
As long as you're able to access bootloader, your device isn't truly bricked.
I understand your consternation, especially as it appears you're fairly inexperienced regarding this. Simply follow my instructions and you'll be fine. I'm trying to make this as easy and foolproof as possible for you.
V0latyle said:
Sideloading the OTA is actually the safest way to update, and the least likely of bricking your device.
As long as you're able to access bootloader, your device isn't truly bricked.
I understand your consternation, especially as it appears you're fairly inexperienced regarding this. Simply follow my instructions and you'll be fine. I'm trying to make this as easy and foolproof as possible for you.
Click to expand...
Click to collapse
Sir can I download this ota file for sideload or other versions
Theracerlucky said:
Sir can I download this ota file for sideload or other versions
Click to expand...
Click to collapse
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Sir you busy now ??
When you free sir reply me i have one more last question answer me plz after that i try to sideload the ota
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Click to expand...
Click to collapse
I see a video on YouTube ithink that is the same issues
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Click to expand...
Click to collapse
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Click to expand...
Click to collapse
Whe
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you
Click to expand...
Click to collapse
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Click to expand...
Click to collapse
When I comented this Youtuber brothers he told me to sideload the latest ota file he created the video on 4 year ago but the latest ota is now Android 11 what can I do sir plz help i am confused he doesn't reply me after this comment reply