Related
Hey guys i have this old HTC Tattoo i would like to use for a while i need to test things on.
HTC Tattoo (Orange)
S-on
1.6.61.43 custom firmware
rooted
But i have a problem, i need to get a custom ROM on it.
so far:
1. Would not accept sim unlock code
1. Rooted it once
2. used RUU_Click_Orange_UK_1.67.61.43_release_signed_NoDriver becouse it was needed to accept the simunlock code
3. Lost root, rooted it again with Universal root becouse old method didn't work anymore.
4. Everytime i tried to open recovery menu, it shows a picture with a orange triangle and the phone next to it
5. Installed ROM manager and put Clockwork, nothing.
6. Tried to back up, install rom from ROM Manager, still nothing =(
HELP D:!
Question: How do i fix it so i don't get this trinagle thing and i can go into the recovery menu
EDIT: I forgot to add, i THINK i made the SDCard a Goldcard, but i'm not sure... how do i cheak?
still no reply? kay:
I am going to help you
I am going to help you when I come home from school I know what you have to do and how.
Shaumaaa said:
I am going to help you when I come home from school I know what you have to do and how.
Click to expand...
Click to collapse
=0 i'm back from school
Shaumaaa said:
I am going to help you when I come home from school I know what you have to do and how.
Click to expand...
Click to collapse
Are you back D: ? i still need help
answer
1. That triangle is stock recovery which isn't useful for installing custom roms.
2. You need custom recovery.
3. You need adb.
4 You can install recovery like this one click http://forum.xda-developers.com/showthread.php?t=950759 or manualy using cmd(adb needed).
If installing manualy: You need flash_image and recovery.img .
For cmd, commands are:
adb push recovery.img /sdcard/recovery.img
adb shell
su
flash_image recovery /sdcard/recovery.img
exit
exit
Hope this was helpful for you
Sorry if you waited too much, I didn't have time to answer you.
Shaumaaa said:
1. That triangle is stock recovery which isn't useful for installing custom roms.
2. You need custom recovery.
3. You need adb.
4 You can install recovery like this one click http://forum.xda-developers.com/showthread.php?t=950759 or manualy using cmd(adb needed).
If installing manualy: You need flash_image and recovery.img .
For cmd, commands are:
adb push recovery.img /sdcard/recovery.img
adb shell
su
flash_image recovery /sdcard/recovery.img
exit
exit
Hope this was helpful for you
Sorry if you waited too much, I didn't have time to answer you.
Click to expand...
Click to collapse
I followed the instructions it didn't help, still same problem
no errors with the .exe, but no dice either
flashpermission denied with manual cmd
not enough memory on the device
in rom manager it says i have clockworkmod 5.0.2.0, might be the the problem that my phone is on orange or that it is S-on ? becouse i'm pretty sure it has custom recovery and it is rooted
i was able to root with this method before i used "RUU_Click_Orange_UK_1.67.61.43_release_signed_NoDriver" update
Now i am not able to use that root method, maybe it would have worked before i used it...
How do i downgrade or whatever from this RUU ?
Adb
Do you have adb drivers installed?
Shaumaaa said:
Do you have adb drivers installed?
Click to expand...
Click to collapse
Yes
Don't know then, I had site with better commands which helped me but it's dead now so I can't access them..
I've been looking for an insecure stock boot.img for about two hours now and I can't find one. I also tried modifying the one included in the factory image by unpacking and setting the ro.secure value in default.prop to 0 but it doesn't seem to work.
So my question is really split in two:
1) Am I just bad at searching? If so, could you link me to a working insecure stock boot.img?
2) What am I missing? I found something about adbd binaries or so, saying that this method doesn't work since 4.2.2, but I didn't quite understand it to be honest... What more modifications do I need to make in order for it to work?
Basically, all I want to be able to do is use adb remount and adb push.
Huge thanks in advance! :good:
fritzhy said:
I've been looking for an insecure stock boot.img for about two hours now and I can't find one. I also tried modifying the one included in the factory image by unpacking and setting the ro.secure value in default.prop to 0 but it doesn't seem to work.
So my question is really split in two:
1) Am I just bad at searching? If so, could you link me to a working insecure stock boot.img?
2) What am I missing? I found something about adbd binaries or so, saying that this method doesn't work since 4.2.2, but I didn't quite understand it to be honest... What more modifications do I need to make in order for it to work?
Basically, all I want to be able to do is use adb remount and adb push.
Huge thanks in advance! :good:
Click to expand...
Click to collapse
as far i know to do adb remount / push u just need to unlock bootloader doing fastboot oem unlock(with phone in fastboot mode)those 2 command work here using that.
opssemnik said:
as far i know to do adb remount / push u just need to unlock bootloader doing fastboot oem unlock(with phone in fastboot mode)those 2 command work here using that.
Click to expand...
Click to collapse
My bootloader is unlocked alright, also I'm pretty sure that the only thing the bootloader has to do with it, is that it has to be unlocked if you want to be able to flash a new kernel (independent on if it's insecure or not).
fritzhy said:
My bootloader is unlocked alright, also I'm pretty sure that the only thing the bootloader has to do with it, is that it has to be unlocked if you want to be able to flash a new kernel (independent on if it's insecure or not).
Click to expand...
Click to collapse
weird, i have never seen security boot off even with custom, now im on stock 4.3 with google kernel and i can do those 2 commands, i just flashed ak now and still security boot on, franco is the same thing, so i guess there is not security boot off for n4.
Hello there users. I'm currently a dev for Nokia X but I would love to help you guys out.
So, I'll be giving out ways on how you can try to get Root on your device. This is a discussion thread.
As I don't have the device myself, I'm counting on people who have purchased it.
So lets start. In order to get development for your device, you need to get a system dump of your whole/entire device.
But for that, you need Root. Heres an app that I think might root the device. http://www.cydiaimpactor.com/
Goto the link, download it and test it out. Give feedback.
And nothing happens. Maybe I`ve done somthing wrong...
So, in a dev options i`ve point usb debuging.
On my pc i got two new devices - Nokia composite adb interface and nokia 2 with yellow mark.
Then run cidia from admin name - usb - driver scan - no device found.
I tried with rooted nokia xl - just to see what happens - error - no such device.
stutofa aregercisr are
Thanks for your help, I tried it out and got this error all the time
Altivex said:
And nothing happens. Maybe I`ve done somthing wrong...
So, in a dev options i`ve point usb debuging.
On my pc i got two new devices - Nokia composite adb interface and nokia 2 with yellow mark.
Then run cidia from admin name - usb - driver scan - no device found.
I tried with rooted nokia xl - just to see what happens - error - no such device.
Click to expand...
Click to collapse
tdiddy.2 said:
Thanks for your help, I tried it out and got this error all the time
Click to expand...
Click to collapse
Okay, so that didnt work.
Now, goto this link and download the adb and fastboot drivers for Nokia X and install them.
After that, go HERE and flash CWM Recovery for Nokia X using the instructions given in the thread.
DONT DO THE ABOVE METHOD! As there is no backup, if something goes wrong, you'll lose the device. For now, wait and let me find more exploits. Till then, do install the adb and fastboot divers.
After that, goto ADB folder and Open command prompt from there (Shift + Right mouse button). Then type this:
Code:
adb reboot bootloader
fastboot -i 0x0421 devices
And see if the device gets recognized.
Then type:
Code:
fastboot -i 0x0421 reboot
You can try this method too: http://forum.xda-developers.com/showthread.php?t=803682
Okay will try. For the recovery, I tried both Nokia X's CWM and TWRP already, none of them worked However it's not going to brick my device haha
On fastboot - nothing. I coudn`t install adb from this tread
http://forum.xda-developers.com/showthread.php?t=2744191
Installer told me-unsupported language and close)
I used cmd.exe ,and path to android tools - on fastboot i got nothing. No list of devices. But.
On reboot or others command - answer is - Waiting for device
Super one click - runs adb server around 3 times, then program freez on - Waiting for device =)
If i click on button driver chek - no issues found.
Maybe i`ve got some trouble with drivers ?
I got them from here
http://developer.nokia.com/resources/library/nokia-x/getting-started/device-setup.html
But i haven`t adb_usb.ini where it should be...
Altivex said:
On fastboot - nothing. I coudn`t install adb from this tread
http://forum.xda-developers.com/showthread.php?t=2744191
Installer told me-unsupported language and close)
I used cmd.exe ,and path to android tools - on fastboot i got nothing. No list of devices. But.
On reboot or others command - answer is - Waiting for device
Super one click - runs adb server around 3 times, then program freez on - Waiting for device =)
If i click on button driver chek - no issues found.
Maybe i`ve got some trouble with drivers ?
I got them from here
http://developer.nokia.com/resources/library/nokia-x/getting-started/device-setup.html
But i haven`t adb_usb.ini where it should be...
Click to expand...
Click to collapse
adb_usb.ini is important as it is the key that recognizes the adb device to the computer.
Do all the above steps in the guide fully including the adb_usb.ini step.
mmmm, Nokia XL got connected without this file...
I tried all instructions on 3 different pc - this file is missed....
So,i just created this file.
on ADB devices i got answer - 188bde4a device
on command fastboot -i 0x0421 devices-
188bde4a fastboot
then i reboot device.
i`ve try out some comands - i lost recovery....
fastboot -i 0x0421 oem unlock
unlocked
fastboot -i 0x0421 flash recovery recovery img.
7seconds flash - and i coud not boot recovery....
i tyed this one
http://forum.xda-developers.com/showthread.php?t=2704379
but - phone boots up in normal mode...
ok,good news - got stock firmware from navifirm!
Just need stock recovery)
Okay, i tried superoneclick, not work :crying:
---------- Post added at 11:02 AM ---------- Previous post was at 10:58 AM ----------
And for the Fastboot...
Code:
Tungs-MacBook-Air:~ md232llaoption$ fastboot -i 0x0421 devices
f901c863 fastboot
Tungs-MacBook-Air:~ md232llaoption$
I think i goot rooted my device....
with root_backup
or towelroot.
So, if I`ll install gaps- that would be great. But i really need custom recovery)
http://forum.xda-developers.com/showthread.php?t=2783157
or in attach.
Copy all data to phone, then go to folder "1" install tr.apk
Make shure you`ve got internet connection.
in folder "2" is SUpersu apk.
In folder"3" - root explorer.
Also you`ll find apk for backup phone.
Altivex said:
mmmm, Nokia XL got connected without this file...
I tried all instructions on 3 different pc - this file is missed....
So,i just created this file.
on ADB devices i got answer - 188bde4a device
on command fastboot -i 0x0421 devices-
188bde4a fastboot
then i reboot device.
i`ve try out some comands - i lost recovery....
fastboot -i 0x0421 oem unlock
unlocked
fastboot -i 0x0421 flash recovery recovery img.
7seconds flash - and i coud not boot recovery....
i tyed this one
http://forum.xda-developers.com/showthread.php?t=2704379
but - phone boots up in normal mode...
ok,good news - got stock firmware from navifirm!
Just need stock recovery)
Click to expand...
Click to collapse
Thats it. You got the fastboot recognized. Now try Bin4ry Root Method and see if it'll work.
tdiddy.2 said:
Okay, i tried superoneclick, not work :crying:
---------- Post added at 11:02 AM ---------- Previous post was at 10:58 AM ----------
And for the Fastboot...
Code:
Tungs-MacBook-Air:~ md232llaoption$ fastboot -i 0x0421 devices
f901c863 fastboot
Tungs-MacBook-Air:~ md232llaoption$
Click to expand...
Click to collapse
You also got fastboot recognized. f901c863 is your fastboot device number.
Try Bin4ry root method.
Altivex said:
I think i goot rooted my device....
with root_backup
or towelroot.
So, if I`ll install gaps- that would be great. But i really need custom recovery)
Click to expand...
Click to collapse
Wait. Did you get Root? HOWWW?! Share if you did. Cause this is what the thread is about.
Dom3616 said:
Wait. Did you get Root? HOWWW?! Share if you did. Cause this is what the thread is about.
Click to expand...
Click to collapse
Towelroot in attach. Idk will it work on clear device,or you need to unlock bootloader. Cos on oem unlock- unlocked something=)
Altivex said:
Towelroot in attach. Idk will it work on clear device,or you need to unlock bootloader. Cos on oem unlock- unlocked something=)
Click to expand...
Click to collapse
Very good. I'll be updating this thread soon.
Now, next step is to goto this thread and make a full dump of your device: http://forum.xda-developers.com/showthread.php?t=2450045
Dom3616 said:
Very good. I'll be updating this thread soon.
Now, next step is to goto this thread and make a full dump of your device: http://forum.xda-developers.com/showthread.php?t=2450045
Click to expand...
Click to collapse
Yes yes!!
Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?
Altivex said:
Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?
Click to expand...
Click to collapse
Yes, you can use this also: http://forum.xda-developers.com/showthread.php?t=1620255
After creating the backup, upload it to Google Drive or any other server.
Altivex said:
Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?
Click to expand...
Click to collapse
I tried to pull and got the recovery img for ya hope this work
Native recovery or custom?)
native I`ve restored yesterday from navifirm. And custom will make our life a bit easyer)
I`ve made a twrp backup, with nandroid . Backup have files with .win extension....
Nothing
Wow, thanks for this useful info...
Can I make a system.img using this Terminal Command:
dd if=/dev/block/mmcblk0p18 of=/sdcard/system.img
After Customizing my ROM as I like it...?
ponnuvelpandian said:
Wow, thanks for this useful info...
Can I make a system.img using this Terminal Command:
dd if=/dev/block/mmcblk0p18 of=/sdcard/system.img
After Customizing my ROM as I like it...?
Click to expand...
Click to collapse
Yes you can just like that but you will need to be rooted before using dd command.
Thank you so much for the new recovery images. Saved me a lot of hassle. But the link for .160 recovery is down
ImjuzCY said:
Thank you so much for the new recovery images. Saved me a lot of hassle. But the link for .160 recovery is down
Click to expand...
Click to collapse
Sorry about that, found a better place. Go ahead and use the new link for the stock recovery.
how can i do this ?
gamsheer said:
how can i do this ?
Click to expand...
Click to collapse
You need to be rooted 1st. The attach to a computer using linux or Windows. Then do a adb shell command, then su and you can use the dd command like I have written at the top.
Sent from my SM-T230NU using Tapatalk
mikerowes69 said:
You need to be rooted 1st. The attach to a computer using linux or Windows. Then do a adb shell command, then su and you can use the dd command like I have written at the top.
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
my device rooted but
it is show me permissions denied
im sorry can you show me some images learn me how can i do this
sorry for my bad english
Can I backup partitions on an unrooted device but unlocked bootloader using fastboot?
I'll explain what I want. Currently, whenever there's a new Firmware, I have to find and then flash stock recovery, unroot, update firmware, flash TWRP, flash SuperSU, and then I can use the device again (to me ann unrooted device is barely useable ). What I'm trying to solve is having to find and download the stock recovery everytime. However, If I have to be rooted then I'll need to temporarily flash recovery, root the device, get the recovery partition using this method, and then flash TWRP. Obviously, this is a pretty big hassle that I'd prefer to avoid.
gamsheer said:
my device rooted but
it is show me permissions denied
im sorry can you show me some images learn me how can i do this
sorry for my bad english
Click to expand...
Click to collapse
Ok guy. His is a beginner session.
1. Make sure that adb debugging is turned on.
2. Make sure you have a cable connected with drivers installed
3. In a terminal or command prompt type the following adb devices. If nothing is returned adb debugging is not turned on. If a serial number returns you have a connection.
4. Only proceed if you have a connection. Type the command adb shell
5. Now if you have root installed type su. No su, means no root. Download a one click root for asus zenfone 2 ze551ml.
6. Now that you are root type the following command if to retrieve all of your fastboot partitions ls -la /dev/block/pci/pci0000:00/0000:00:01.0/by-name
7. This will tell you the location of the partition for recovery.
8. This command will package your stock recovery for your current firmware dd if=/dev/block/mmcblk0p2 of=/sdcard/recovery.img
9. This command will restore your stock recovery any custom recovery you choose.
dd if=/sdcard/recovery.img of= /dev/block/mmcblk0p2
dd if=/sdcard/twrp.img of /dev/block/mmcblk0p2
It can even be a bin file or whatever you choose to name it. But the partition has to be correct and that is why it is important to find what the fasboot partitions names are and locations.
10. If using fastboot type adb reboot bootloader. Then type fastboot flash recovery recovery.img and it will say failed but it didn't fail if your bootloader is unlocked.
Sent from my SM-T230NU using Tapatalk
BobboVilla said:
Can I backup partitions on an unrooted device but unlocked bootloader using fastboot?
I'll explain what I want. Currently, whenever there's a new Firmware, I have to find and then flash stock recovery, unroot, update firmware, flash TWRP, flash SuperSU, and then I can use the device again (to me ann unrooted device is barely useable ). What I'm trying to solve is having to find and download the stock recovery everytime. However, If I have to be rooted then I'll need to temporarily flash recovery, root the device, get the recovery partition using this method, and then flash TWRP. Obviously, this is a pretty big hassle that I'd prefer to avoid.
Click to expand...
Click to collapse
This device you and all of choose only allows us to do find the vulnerability in the bootloader, and this is how it is packaged. Any other way would like a nexus or oneplus model is much easier. However asus choose to lock their bootloader and package their partitions. Now if you can rewrite their fasboot and that would be great. So root with a one click root. Then use the dd commands to package your stock recovery and life will go a lot easier, with future firmware updates, just remember to uninstall root for a ota and replace your custom recovery with your stock first before doing a adb sideload
Sent from my SM-T230NU using Tapatalk
mikerowes69 said:
Ok guy. His is a beginner session.
1. Make sure that adb debugging is turned on.
2. Make sure you have a cable connected with drivers installed
3. In a terminal or command prompt type the following adb devices. If nothing is returned adb debugging is not turned on. If a serial number returns you have a connection.
4. Only proceed if you have a connection. Type the command adb shell
5. Now if you have root installed type su. No su, means no root. Download a one click root for asus zenfone 2 ze551ml.
6. Now that you are root type the following command if to retrieve all of your fastboot partitions ls -la /dev/block/pci/pci0000:00/0000:00:01.0/by-name
7. This will tell you the location of the partition for recovery.
8. This command will package your stock recovery for your current firmware dd if=/dev/block/mmcblk0p2 of=/sdcard/recovery.img
9. This command will restore your stock recovery any custom recovery you choose.
dd if=/sdcard/recovery.img of= /dev/block/mmcblk0p2
dd if=/sdcard/twrp.img of /dev/block/mmcblk0p2
It can even be a bin file or whatever you choose to name it. But the partition has to be correct and that is why it is important to find what the fasboot partitions names are and locations.
10. If using fastboot type adb reboot bootloader. Then type fastboot flash recovery recovery.img and it will say failed but it didn't fail if your bootloader is unlocked.
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
thank you very much its work fine my pro
gamsheer said:
thank you very much its work fine my pro
Click to expand...
Click to collapse
Your welcome
Sent from my SM-T230NU using Tapatalk
Thanks a lot
Can someone with a ZE551ML WW dump his factory.img and post it? I try to enable LTE bands on a ZE551ML TW and I want to compare this partition to find some possible differences...
Thanks
NicoAu said:
Can someone with a ZE551ML WW dump his factory.img and post it? I try to enable LTE bands on a ZE551ML TW and I want to compare this partition to find some possible differences...
Thanks
Click to expand...
Click to collapse
There was a new factory.img and droidboot.img in the last full firmware build.
Sent from my SM-T230NU using Tapatalk
Did any notice that there was a new fastboot with the latest build? I wrote to Asus Tech support that they need to change their bootloader to easily unlocked and relocked. If a lot more people write they will change the bootloader. So please write tech support and ask that the bootloader be changed or replaced and that your email goes out to everyone in support and writing the software.
Sent from my SM-T230NU using Tapatalk
mikerowes69 said:
There was a new factory.img and droidboot.img in the last full firmware build.
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
Can you tell me where I can find this build?!? On asus website, I only see "UL-Z00A-WW-2.20.40.164-user.zip" with boot.img and droidboot.img in the archive...
Thanks
mikerowes69 said:
Did any notice that there was a new fastboot with the latest build? I wrote to Asus Tech support that they need to change their bootloader to easily unlocked and relocked. If a lot more people write they will change the bootloader. So please write tech support and ask that the bootloader be changed or replaced and that your email goes out to everyone in support and writing the software.
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
You do realize there would then be no more unofficial bootloader unlocker and your warranty would be instantly voided. It's really not that hard to unlock the bootloader the way it is and you can retain warranty unofficially unlocking it as they don't check for it while being serviced if you flash the black splashscreen. Plus it's only a matter of time until somebody figures out how to relock it.
P.S. If you can't figure out or take the time to learn how to unlock the bootloader, you're better off not modding your phone in the first place as your most likely going to do more harm than good.
Sent from my ASUS_Z00AD using Tapatalk
i snort flour said:
You do realize there would then be no more unofficial bootloader unlocker and your warranty would be instantly voided. It's really not that hard to unlock the bootloader the way it is and you can retain warranty unofficially unlocking it as they don't check for it while being serviced if you flash the black splashscreen. Plus it's only a matter of time until somebody figures out how to relock it.
P.S. If you can't figure out or take the time to learn how to unlock the bootloader, you're better off not modding your phone in the first place as your most likely going to do more harm than good.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Thanks guy for wasting my time as well as anyone else. If your on here you don't really care about warranty. You assume I don't know about unlocking or anything else. Please go bother someone else. Assuming makes an ass out of you.
Sent from my SM-T230NU using Tapatalk
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.