Related
Hello,
I updated my UK Xoom 3G (MZ601) via OTA to 3.2 (H.6.5-17-3) last year.
Since I got interested in rooting the device I read I have to install CWM first.
However, when going into recovery mode (for testing) all I get is a green android bot.
Thanks to some googling I found some website that mentions to hold the power button (while the green android bot is shown) and press volume up, then release the power key. Now I see the stock 3e recovery menu.
Is it safe to simply unlock the bootloader and flash CWM via ADB? Or am I required to flash back to the xoom dev stock rom because of the green fella? My question refers to this part:
Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Not sure why I would have to do that? In the end, I'd want to have a rooted stock 3.2.
First unlock it indeed while seeing the green bot in recovery.
(using the commands you posted yourself)
Then, you back into recovery, and push the new cwm recovery using adb
(look on the xda xoom's section: you'll find the right tutorial; should start with downloading adb, downloading cwm into the same directory as where you put the adb drivers for the xoom. Then open command as administrator, etc.)
After that, you should have CWM (or I recommend the touch Rogue recovery! ) on your Xoom, instead of the ugly little green bot, now allowing you to flash many, many ROMs, zips and many other to your device!
Enjoy. Hope this is clear enough and helps you towards the right direction! (if so, please do thank me, since I only just made an XDA account and would like at least one thanked post lol.
If not, please PM me or ask further explanations in this thread! )
adelancker said:
First unlock it indeed while seeing the green bot in recovery.
(using the commands you posted yourself)
Click to expand...
Click to collapse
I suppose you only refer to the adb commands without flashing the img files, right?
I still don't know why that other thread suggested to flash back to an older version first (see quote in my first posting)? Can anyone tell me if I have to downgrade at all?
Landorin said:
I suppose you only refer to the adb commands without flashing the img files, right?
I still don't know why that other thread suggested to flash back to an older version first (see quote in my first posting)? Can anyone tell me if I have to downgrade at all?
Click to expand...
Click to collapse
First unlock it using those fastboot commands you posted. You should in this series of commands not flash anything yet. Just unlock it first. When rebooting and showing the Moto logo:
Get back into recovery and then push the new recovery.img using adb commands
As far as I know, there is not one reason to downgrade. Should work just fine.
---------- Post added at 01:23 PM ---------- Previous post was at 01:05 PM ----------
adelancker said:
First unlock it using those fastboot commands you posted. You should in this series of commands not flash anything yet. Just unlock it first. When rebooting and showing the Moto logo:
Get back into recovery and then push the new recovery.img using adb commands
As far as I know, there is not one reason to downgrade. Should work just fine.
Click to expand...
Click to collapse
Otherwise, use this as your guideline and you should be fine:
http://forum.xda-developers.com/showthread.php?t=1249798
Thank you! All worked out fine. I followed the guide step by step, I did not downgrade the existing ROM.
In case someone else gets into the same situation and wonders how to do it:
once everything is set up for ADB and the device is found (command adb devices) type this in your command prompt window:
Code:
adb reboot bootloader
waited for fastboot protocol text to show up on Xoom device, then:
Code:
fastboot oem unlock
Confirmed the warning. Then had the device booting up normally to re-enable USB debugging. Then continued:
Code:
adb reboot bootloader
again waited for fastboot protocol text to show up on Xoom device, then:
Code:
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
When it said flashing done I restarted the Xoom (holding power button + volume up). About 3-4 sec after seeing the Motorola pic I hit volume down ("android recovery" is displayed), then volume up and CWM showed up.
Since I was already in CWM I also applied the universal root method ("install zip from sdcard" -> "choose zip from sdcard", then selected the actual file on the sd card, installed it, rebooted). Root works.
P.S.: just realized silly me forgot to do a nanddump before rooting.
something like forgetting a nanddump only happens once!
Glad to see it worked for you!
Even happier to see you didn't need to downgrade.
Once you flash a custom ROM, you'll have 3G and ICS!
I did the same a couple of months ago, and my device felt brand new!
EDIT - UPDATED INSTRUCTIONS 12th May 2014
Due to the partition sizes being different in the GPE RUU it is not simply a case of flashing a sense rom in recovery. You will experience problems if you do this. This might involve getting the storage encrption message, bootloops, freezing etc etc.
This thread is specifically for users who have problems getting back to sense. Solution is below. If you have alternative solutions that have worked without issues please post.
I have tried to make them as simple as possible. This guide assumes you are S-Off otherwise how did you get here. (
This does not apply if you have installed a GPE ROM. You can flash as normal through recovery. (using instructions of new rom)
Thanks to @exad for his continuing support/assistance throughout the thread, as well as @graffixnyc for the GPE RUU and both he and @navalynt for finding the initial fixes.
It will be much easier if you have your new Rom on your external sdcard prior to starting this. It will also stop a number of problems if you have SuperCID (11111111) If you don't know how to - FASTBOOT Commands
1. Enter the command "fastboot oem readcid". Make and KEEP a note of your original CID.
2. Enter the command "fastboot oem writecid 11111111"
3. Enter the command "fastboot read cid" [it should confirm your CID is 11111111]
4. Press the volume down button twice on your phone and navigate to reboot bootloader, then hit power button to reboot the bootloader.
5. Bootloader will also say "CID-11111111" now to confirm (Thanks to @xl VipeR lx ) Also to @umjammerlammy for the GENTLE reminders to include this
Make sure the firmware file and twrp recovery are in your Android directory on your PC - Mine is
C:\Users\Grentuu\AppData\Local\Android\android-sdk\platform-tools\
During this process you may find that when you reboot the phone starts to boot into android. Mine did but simply had the GPE animated logo but never entered GPE. All you do is press Vol up and power for about 10 seconds to reset. As soon as it resets press vol down and power to get back to bootloader.
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Some users have stated this firmware (1.54.401.5) did not work for them as they weren't GSM and reboots just threw them back to recovery. If this happens try a stock (your original e.g. T-mobile) firmware then follow the rest of the process.
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
These have worked for me everytime (Change count =19)
Thanks for this. I'm about to give it a shot now.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 05:08 PM ---------- Previous post was at 04:40 PM ----------
For some reason the firmware wont flash in twrp. Should I sideload the firmware?
Sent from my GT-P5210 using XDA Premium 4 mobile app
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firnwarefilename.zip
Then again
Fastboot flash zip firnwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks. Understood, I was just reviewing my steps for the conversion. I really just want to try out that new Sense rom and then I'll probably revert back. BRB...I'll let you know how it goes.
Bear in mind you must have S-off to flash a firmware that way.
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Those are the instructions in post 1 the original thread.
The issue is with people wanting to go back to sense
This thread is about returning to sense. Flashing a firmware is always the same. It's the firmware itself that's different...
Here is where I am at..
I converted to GP easily and it worked well.. I wanted to convert back so I installed twrp first, then through twrp installed the 1.54.401.5 firmware.
Installing that firmware removed twrp and the rom. So I am without an OS at all, and have stock recovery.
Is there anyway I can flash a custom recovery or a rom via the stock firmware/recovery?
My computer will not recognize adb devices. But it used to obviously.
I have an SD card.
Any help and I will be sooo grateful. (maybe even donate)
Thanks!
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Thanks will try it out.
exad said:
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Click to expand...
Click to collapse
So what do I do in this situation with no rom installed only 1.54 firmware and stock recovery.
Flash twrp
exad said:
Flash twrp
Click to expand...
Click to collapse
I have no rom installed, so it wont show in adb devices.
PunchLick said:
I have no rom installed, so it wont show in adb devices.
Click to expand...
Click to collapse
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Dmaxon said:
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Click to expand...
Click to collapse
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
PunchLick said:
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
Click to expand...
Click to collapse
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Why post steps if your not willing to help?
The steps in the OP can still cause issues for some people.
Sent from my HTC One_M8 using Tapatalk
Ideas4ya said:
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Click to expand...
Click to collapse
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
PunchLick said:
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
Click to expand...
Click to collapse
When you open the all in one...the 3rd option on the top right is what you need. Follow the step, even if fastboot says device is not connected, this will still send the recovery to your device as long as you're in the bootloader.
I will never understand why people play with there phones and have no understanding of adb and fastboot commands with the bootloader. if people would learn that first there wouldn't be so many threads when they get stuck. tool kits are bad it makes people lazy. but I appreciate the devs who make them
I am trying to update my Bootloader. I am on version 3.51. When I go into fastboot, fastboot devices lists my device. When I attempt to flash anything, it hangs at <waiting for device>.
Not sure exactly what to do. SDK is updated, along with tools.
I am on Ubuntu 16.04.
EDIT: Issue resolved after installing eclipse, and redownloading latest SDK
Thread closed per OP request.
New device new rules/tricks
The main purpose for this thread is to post info that doesn't real justify it's own thread.
Most of what is posted is what interests me, usually in no particular order.
If you think something is missing, please share (include links or as much info you can)
General Info
Index
Have a question? Please consider asking in the
Help Thread
How to Check if you have a Verizon or Google Model from CID info
Custom Recovery info
FAQs
USB Drivers
Using ADB and Fastboot commands
Unlocking the Bootloader
Rooting
WiFi Tether
Installing new security update with fastboot.exe for a bootloader-unlocked Pixel
[GUIDE] Restore to stock after soft BRICKED Written for XL version, but a good reference
Set/Change Active System Partition with Fastboot Command in Bootloader Mode
[Re]Activate Google Voice on Pixel
46 Google Pixel XL & Google Pixel Tips and Tricks (www.droidviews.com)
https://www.androidpit.com/google-pixel-tips-and-tricks
USB Drivers for using ADB/Fastboot commands
If using Mac or Linux drivers should not be an issue.
If using Windows 10 correct drivers should already be installed but you likely will need to select them in Device manager
If drivers are correct the Pixel should be listed in Device Manager as
Android Phone
adb composite interface
An easy way to install correct drivers on a Windows PC is using
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05
Official Google Drivers
Unlocking the Bootloader - 06 Nov 2016
If it's a pure Google device just run
Code:
fastboot oem unlock
If you bought the Pixel from Verizon, Best Buy.... dePixel8 method will be required to unlock the bootloader
Note: Verizon, Build Version NDE63X, Nov 2016 can be unlocked,Builds after that cannot.
Using dePixel8
Be sure Drivers are correct
Change screen timeout to 30 mins in settings/display options
Enable Developer Options
In Settings/About Phone >Tap build version until it says "you are developer"
go back to main Settings screen
Open Developer Options
Enable ADB Debugging (in Developer Options)
Be sure ADB and Fastboot commands are working
Download dePixel8
Run in Command prompt
Code:
adb push dePixel8 /data/local/tmp
Code:
adb shell chmod 755 /data/local/tmp/dePixel8
then
Code:
adb shell /data/local/tmp/dePixel8
when you see
Code:
[+] getting there, about 20 more seconds please
open the Chrome app on the phone
then you should see
Code:
[+] done
[+] rebooting your device to bootloader mode
[+] run "fastboot oem unlock" to unlock your bootloader
[+] P.S. Pixel is made by HTC, and dePixel8 was made by beaups
[+] cheers jcase - copyright Streamlined Mobile Solutions, LLC
Discussion Thread: BL unlock for Verizon Pixel just released by murryrulz
Do not relock the bootloader
[PSA] Read before relocking your bootloader by jcase
Rooting
Requires Unlocked Bootloader
[ROOT] SuperSU by Chainfire
Hotspot/WiFi Tether
Hotspot should work out of the box for most data plans except Unlimited Data plans
Verizon Unlimited Data Plans
Rooted method
Make sure your bootloader is unlocked and you are rooted.
Instal a Root File Manager (Root Browser / ES File Explorer)
enable root access in File Manager (it's off by default in some)
browse to /System > Long press build.prop > Open in Text Editor
Scroll all the way to the bottom. Type in "
Code:
net.tethering.noprovisioning=true
.. Then save and exit. Reboot the phone and you're good to go.
Discussion Thread: Pixel Hotspot by polo2883
[Mod][Systemless Root][Pixel/Pixel XL] TetherMod - Bypass provisioning checks. by Fenny
http://forum.xda-developers.com/pixel-xl/themes/mod-tethermod-systemless-install-guide-t3501448
Non Root method
Verizon native tether subscription bypass A Pixel XL thread
Sprint WiFi Tethering Thread
[ROOT/Guide] Native Hotspot Working by stuntnmore A Pixel XL thread
Setting up and Using ADB/Fastboot (Android Debugging Bridge)
For Mac or Linux: see Can ADB/Fastboot be used on Linux and Mac?
Setting up ADB/Fastboot (Windows)
[Index] Setting up and Using ADB/Fastboot
Using ADB/Fastboot
adb commands are used in normal boot/OS or in Recovery
fastboot commands are used in fastboot/bootloader mode
Set/Change Active System Partition with Fastboot Command in Bootloader Mode
Code:
Fastboot set_active _a
Code:
Fastboot set_active _b
Installing new security update with fastboot for a bootloader-unlocked Pixel.
Note: This is a work in progress, but it should be correct.
Even if it works for the Nov update, it may need to be written for future updates
Problem:
If you have modified the stock firmware (hosts file, root, kernel, etc.), the OTA update likely will fail
Solution:
This does not factory reset, user apps and data are not removed.
This will remove your custom kernel/root/hosts/recovery...
Install Verify Drivers
see post #2
Setup ADB.exe see
[Index] Setting up and Using ADB/Fastboot
[INFO] How I restored to stock after soft bricking, then flashed new kernel & rooted by CZ Eddie
Download the system image for Sailfish (Pixel) from google
For November update, there are 3 versions:
NDE63U Europe
NDE63V US, except Verizon
NDE63X Verizon
Unzip the file
Unzip xxxxxxnde63v.zip from inside the new directory/folder
Copy files to same folder as adb.exe files (unnecessary if adb is setup as global)
Open open Command Prompt (with same directory path as firmware files)
Reboot into bootloader
Code:
adb reboot bootloader
or
Power off, Hold volume down button, power on
check your boot slot (_a or _b) and following line may need to be adjusted?
Code:
system_b system_other.img
Execute fastboot commands
Code:
fastboot flash bootloader bootloader-sailfish-*.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
Custom Kernel, Root, and other mods will need to be reflashed
Credit
[GUIDE] Update with fastboot by @firewave
Custom Recovery
Twrp links
TWRP RC1 for Pixel Devices
https://plus.google.com/+DeesTroy
Thanks a lot for this thread. Very helpful for updating my pixel. Have linked it a few times to help out. This thread should be stickied.
GeekMcLeod said:
Thanks a lot for this thread. Very helpful for updating my pixel. Have linked it a few times to help out. This thread should be stickied.
Click to expand...
Click to collapse
Thanks, hope it helps.
It is linked in the index
sd_shadow said:
check your boot slot (_a or _b) and following line may need to be adjusted?
Code:
system_b system_other.img
Click to expand...
Click to collapse
To be clear, you want the one used to match the one you're currently set to right? (My bootloader specifies boot slot a.)
sturmeh said:
To be clear, you want the one used to match the one you're currently set to right? (My bootloader specifies boot slot a.)
Click to expand...
Click to collapse
I did it the other way. System other seemed like it shouldnt be your boot slot. I updated it already and it's working so I think I got it right.
GeekMcLeod said:
I did it the other way. System other seemed like it shouldnt be your boot slot. I updated it already and it's working so I think I got it right.
Click to expand...
Click to collapse
so boot slot was a in bootloader?
you use b command?
is it now b in bootloader?
Sent from my XT1254 using XDA Labs
the Pixel has 2 system slots/partitions,
in theory you could have 2 different roms to choose from, that maybe an option in a future version of twrp
Sent from my XT1254 using XDA Labs
sd_shadow said:
so boot slot was a in bootloader?
you use b command?
is it now b in bootloader?
Sent from my XT1254 using XDA Labs
Click to expand...
Click to collapse
No, my bootloader still says my bootslot is a.
GeekMcLeod said:
No, my bootloader still says my bootslot is a.
Click to expand...
Click to collapse
thanks, sounds good
Sent from my XT1254 using XDA Labs
new
[Mod][Systemless Root][Pixel/Pixel XL] TetherMod - Bypass provisioning checks. by Fenny
http://forum.xda-developers.com/pixel-xl/themes/mod-tethermod-systemless-install-guide-t3501448
Sent from my sailfish using XDA Labs
I just tried reverting to stock and my phone is stuck in a bootloop and then eventually gets stuck on dead android with No command text. I followed all directions to the dot and I'm on boot slot b. Any ideas?
---------- Post added at 11:04 AM ---------- Previous post was at 10:43 AM ----------
Ok so I followed GeekMcLeod's advice about flashing system-other to the opposite partition. Since I was on boot_b I change the line in the OP to flash system_a and now my phone is booting. @sd_shadow I'm not sure if this is the case for everyone.
Just a short story about my experience so far with the Pixel.
When i first got my device it wanted to update. I let it update (OTA) and rebooted. Once that was done, I unlocked the bootloader, booted TWRP flashed it, rebooted TWRP and then flashed root. All was awesome, I went to reboot and noticed that TWRP shows which boot slot you're in (I was in B). I rebooted anyway and everything works as expected.
I was curious, so I booted back into TWRP, went to reboot and changed the boot slot to A, got an error but checked it again and it shows I was in fact in boot slot A. So i rebooted... it booted into non rooted, pre update android... so it looks to me that this seamless update system applies the update the opposite partition that your in. So if you're in A and take an OTA it applies it to B and then reboots into B (updated) and the opposite will happen if you take the OTA while in B. All apps and data you've collected is shared with either system partition.
So, in theory we could take the OTA as long as we flash the recovery and (possibly) boot images before downloading and applying it. We would only have to flash TWRP and root again.
And I agree, it looks like we should be able to dual boot two different ROMS, maybe even kernels without too much messing around.
I'm sure this is not new news but I just wanted to share and maybe someone will correct me or learn from it.
thanks for the replies, good stuff
Sent from my sailfish using XDA Labs
Not even going to keep this for the learning experience, it's not worth it.
Hi! Tks for you suport.
I have 2 questions if you can help me. I´m a noob for this phone, but i used to update mu Xperia with Remix and i unsdestand a little bit of installing costum firmware.
1- Do we need after this to install again stock boot.img? Because i read in were and MIUI forum that patch boot.img will not give OTA updates.
But installing stock will not remove Camera2api also?
2- I Have V9.6.13.0.ODIMIFE ( second september update) i try to seach for patch boot.img for A2 in were, but i only find the full stock image
in https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
I read what you said about teaching to fishing rather give a fish, but if for this thime you could put the link, in future updates we all will be more confortable do do other updates.
Kind regards
ki69 said:
1- Do we need after this to install again stock boot.img? Because i read in were and MIUI forum that patch boot.img will not give OTA updates.
But installing stock will not remove Camera2api also?
Click to expand...
Click to collapse
Ki, this is a great example of where one needs to look carefully at the command, and do some research. If you look closely the code says "boot" patched_boot. The point there is that it doesn't say "flash". Booting it won't flash it. That command will read it from your hard drive into rom memory of the device, and NOT write it to the flash memory of the device. I.E. The boot.img on the device will not change, so no reason to flash it again.
ki69 said:
2- I Have V9.6.13.0.ODIMIFE ( second september update) i try to seach for patch boot.img for A2 in were, but i only find the full stock image
in https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
Click to expand...
Click to collapse
Bring up all the topics in the MiA2 Guide(s) forum. At the top right is "Search This Forum". So... obviously... type in; patched_boot.
The first thread, OTA Jasmine (etc) has many posts with links to specific versions of (magisk) patched_boot images. (hint; search that thread also if you don't want to page through the posts!) - and don't forget to thank (use thank button!) cpkv5 for his efforts of extracting the boot.img and patching it for everyone, and making it available for easy download!
AsItLies said:
So to enable Cam2API w/out root, and continue to get OTA updates;
1) You need to be familiar with using ADB and FASTBOOT. Pls look at easily searchable documentation for them. Have them installed and usable on your pc / laptop. Try some of the commands out before using this guide, to get use to them / verify working.
2) You have to unlock the bootloader, which will wipe the device. It will also have to stay unlocked, which means your phone will be considered 'uncertified' in Play Store. Because we don't have NFC, and I don't do any banking apps on my phone... no worries for me.
3) You need the patched_boot.img for your current software version. The patched image (and the original boot image) are readily available. Just search the MiA2 forums and you'll find numerous links to new and previous images for the various software versions that have existed for our MiA2's.
So, you should already know how to enable adb and to OEM unlock in developer options (pls SEARCH if not!). So make an adb connection to do:
Code:
adb devices
The above will verify your pc sees the phone, obviously.
Code:
adb reboot bootloader
The above is an easy way to get to fastboot mode.
Code:
fastboot devices
The above will verify fastboot sees our device
Code:
fastboot oem unlock
The above unlocks the bootloader and wipes / reboots device. Again recheck to be sure in Dev options adb is on.
Code:
adb reboot bootloader
Above to get back to fastboot mode.
Code:
fastboot boot patched_boot.img
The above will now boot the device. Be sure the patched boot image is in the directory you are issuing the command from, and again, it needs to be the patched image that corresponds to the current software version you are using.
At this point, I'd recommend to not do anything with the device. It should be booted and appear normal. Back at our command prompt;
Code:
adb devices
Assuming we still see our device:
Code:
adb shell
The above will now put our command prompt into a linux shell, and then type the following:
Code:
setprop persist.camera.HAL3.enabled 1
and then
Code:
setprop persist.camera.eis.enable 1
At this point, it's about done. The above settings will get propagated to the appropriate tables after rebooting the device. They won't change system settings. So OTA updates should work.
Next, we just type 'exit' in the command prompt to exit the adb shell. Lastly we again issue 'adb reboot bootloader' and once we're back into fastboot, just issue 'fastboot reboot'.
That's it. We never flashed anything, only booted the patched image. So nothing really gets touched, that could inhibit OTA updates. When we do the reboot, it will read the original (untouched) boot image and boot as normal. This also keeps us from touching the other 'Slot' (not really needed). This is much simpler than using TWRP imho.
Click to expand...
Click to collapse
THANKS MATE, I REACHED TO FINAL STAGE & BOOTED IN TO THE PATCHED IMAGE BUT
AFTER putting command prompt into a linux shell it gives error failed to set property. please help i am awiting your reply.
Abbey Bhatt said:
THANKS MATE, I REACHED TO FINAL STAGE & BOOTED IN TO THE PATCHED IMAGE BUT
AFTER putting command prompt into a linux shell it gives error failed to set property. please help i am awiting your reply.
Click to expand...
Click to collapse
Yes I saw that Abbey, just updated the original post. At this point pls use the TWRP method I mentioned in similar thread. That works for sure.
I thought the Magisk patched boot image would have the same abilities (in this sense) as twrp, but it seems it does not. Will update if I find a solution.
Abbey Bhatt said:
THANKS MATE, I REACHED TO FINAL STAGE & BOOTED IN TO THE PATCHED IMAGE BUT
AFTER putting command prompt into a linux shell it gives error failed to set property. please help i am awiting your reply.
Click to expand...
Click to collapse
hey mate after rebooting, magisk appeared in app drawer, did i flashed patched boot image. by using this code? please advise
AsItLies said:
Ki, this is a great example of where one needs to look carefully at the command, and do some research. If you look closely the code says "boot" patched_boot. The point there is that it doesn't say "flash". Booting it won't flash it. That command will read it from your hard drive into rom memory of the device, and NOT write it to the flash memory of the device. I.E. The boot.img on the device will not change, so no reason to flash it again.
Click to expand...
Click to collapse
Yes, i didn´t read carefully, but my question has because i read that we need magisk after put patche boot.img, then enable, then remove magisk then flash stock boot.img
I read that you update the firt post informing of the need of that.
AsItLies said:
Bring up all the topics in the MiA2 Guide(s) forum. At the top right is "Search This Forum". So... obviously... type in; patched_boot.
The first thread, OTA Jasmine (etc) has many posts with links to specific versions of (magisk) patched_boot images. (hint; search that thread also if you don't want to page through the posts!) - and don't forget to thank (use thank button!) cpkv5 for his efforts of extracting the boot.img and patching it for everyone, and making it available for easy download!
Click to expand...
Click to collapse
Sorry, i only find this one:
https://forum.xda-developers.com/showpost.php?p=77295065&postcount=22
that have magisk, but with that like i said before i will mess with system/root, the thing i did´t want. so for me is not the path i want to take. I prefer the patch you give in:
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058
And because is a diferente path i think that that thread should be reopen by mods.
Abbey Bhatt said:
hey mate after rebooting, magisk appeared in app drawer, did i flashed patched boot image. by using this code? please advise
Click to expand...
Click to collapse
It shouldn't have flashed it, should have just booted it. I just uninstalled the magisk in app drawer myself. It looks as though a part of the magisk patched boot image installs that 'stub' part of magisk, to then allow a full install I'm sure. So that seems to happen whether you flash it or boot it.
ki69 said:
Yes, i didn´t read carefully,
Sorry, i only find this one:
Click to expand...
Click to collapse
You're looking in the ROM forums, not the indicated GUIDES forum.
AsItLies said:
It shouldn't have flashed it, should have just booted it. I just uninstalled the magisk in app drawer myself. It looks as though a part of the magisk patched boot image installs that 'stub' part of magisk, to then allow a full install I'm sure. So that seems to happen whether you flash it or boot it.
Click to expand...
Click to collapse
hey i am now wish to follow method presented in this thread
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058
but at stage of fastboot getvar currdent-slot
it showing failed. no any partition showed
Abbey Bhatt said:
hey i am now wish to follow method presented in this thread
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058
but at stage of fastboot getvar currdent-slot
it showing failed. no any partition showed
Click to expand...
Click to collapse
Not sure what's going on. When I do the same the result is:
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.000s
Did you flash it by mistake instead of boot it? Have you tried to do a 'fastboot set_active' ?
AsItLies said:
Not sure what's going on. When I do the same the result is:
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.000s
Did you flash it by mistake instead of boot it? Have you tried to do a 'fastboot set_active' ?
Click to expand...
Click to collapse
Humble request,
If you don't know about device or appropriate procedure don't post irrelevant things. As I know this device is tricky and more chances for hard brick if something goes wrong.
Abbey Bhatt said:
Humble request,
If you don't know about device or appropriate procedure don't post irrelevant things. As I know this device is tricky and more chances for hard brick if something goes wrong.
Click to expand...
Click to collapse
out and out flagrant request, if you can't follow directions, don't even try what is suggested.
There's no way anything I indicated would brick a phone. I've done it. Mine is not bricked. As indicated the setprop commands won't work with patched boot image. Then all you have to do is exactly what the procedure says and it's back to normal.
You're the reason people don't bother to post guides.
I do know about device and relevant procedure, it's not irrelevant. Your inability is what's irrelevant.
AsItLies said:
out and out flagrant request, if you can't follow directions, don't even try what is suggested.
There's no way anything I indicated would brick a phone. I've done it. Mine is not bricked. As indicated the setprop commands won't work with patched boot image. Then all you have to do is exactly what the procedure says and it's back to normal.
You're the reason people don't bother to post guides.
I do know about device and relevant procedure, it's not irrelevant. Your inability is what's irrelevant.
Click to expand...
Click to collapse
Hero how's your age how long been in this you are the people who doesn't know things and phones and wage all around being as op. Now cut this crappy out and first learn and then come for advice.
Abbey Bhatt said:
Hero how's your age how long been in this you are the people who doesn't know things and phones and wage all around being as op. Now cut this crappy out and first learn and then come for advice.
Click to expand...
Click to collapse
I'm sorry you screwed up your device. But it's not my fault. Nothing I indicated, if followed, would have caused that.
I'd suggest quitting the childish attempts at personal attacks. Your problems are not my fault.
@oka1 Hi again, sorry, this is the 2nd time! Please close this thread, and delete if possible. It' no longer provides any benefit.
Thanks! Won't happen again.