[TUTORIAL] Way to Expand the RAM
There may be few rom that uses ram too much because there is tw50 or other launcher.
This Trick support All Rom
[align=center]TUTORIAL[/align]
1. log out running applications in the background such as Fb, messages, friendcaster, and other
2. use the application as necessary applications you need. Do not install too many applications. use only as needed
3. add this in the build prof
ro.HOME_APP_ADJ = -17
how ?
* Open root explorer
* Find the folder / system / build.prob
* Open with text editor
* Check out everything, if there is no there.
added
ro.HOME_AP P_ADJ = -17
in the bottom
* If you already have a script like that change ends of -01 be -17
4. Restart or Reboot
5. Lastly, check ram
6. Laugh
SPECIAL THANKS TO THE Firman Yoshioka (ADMIN OF GYC)
Hery Cools (Owner of Galaxy Y Community) and All Member of GYC
regards
oppheng uchiha tenseii
Hey guys,
I am running Legacy Xperia latest build (Android 4.3.1) on my Sony LWW. I have installed BBM on my phone...
Today I decided to move back to Real ICS v 6 ROM, but to my surprise my BBM Pin gor changed even though I was using the same user id and password. To solve this I tried CM9 and with the same id I got a another new pin....so now I have 3 BBM PINs with same id & password.
Now I went back to Legacy Xperia (4.3.1) and installed BBM using a new email address(hotmail) and got a PIN...to test again I installed CM9 and used the new email (hotmail) and got a message that the "current android is associated with another username and if I would like to associate it with this username" (the message was referring to old email address used in CM9) and it gave me again a new PIN. (now I have 5 PINS )
Since I have taken backup of my android which I restored and I was back on my original PIN...
PROBLEM: is if in case I change my ROM to Kitkat in future (hopefully in couple of months) or I switch to another android phone (wont go for iphone) I will end up with a new pin which is a big problem and will have to add all contacts again...is there a solution to this? There is something which changes everytime a new ROM is installed, but don't know what it is)...........PLEASE HELP !!!
Every time you flash a new ROM ,your device ID changes ...In fact every time you factory reset the phone ,you change the device ID
I wrote a post on how to maintain the device ID across ROMs and devices !
It requires a little knowledge of SQL though ...
Check it out
Backing up the original ID from the Backup/ROM
Code:
$su
#cd /data/data
#cd com.android.providers.settings
#cd databases
#sqlite3 settings.db
>select * from secure where name='android_id'
xyZ(this is the original android id)
>.exit
#reboot
Note down the xyZ
Restoring the ID on new ROM
Code:
$su
#cd /data/data
#cd com.android.providers.settings
#cd databases
#sqlite3 settings.db
>select * from secure where name='android_id'
ABC(this is the new android id)
>update secure set value='xyZ' where name='android_id'
>select * from secure where name='android_id'
xyZ(Mission accomplished if done correctly :yay:)
>.exit
#reboot
karandpr said:
Every time you flash a new ROM ,your device ID changes ...In fact every time you factory reset the phone ,you change the device ID
I wrote a post on how to maintain the device ID across ROMs and devices !
It requires a little knowledge of SQL though ...
Check it out
Backing up the original ID from the Backup/ROM
Code:
$su
#cd /data/data
#cd com.android.providers.settings
#cd databases
#sqlite3 settings.db
>select * from secure where name='android_id'
xyZ(this is the original android id)
>.exit
#reboot
Note down the xyZ
Restoring the ID on new ROM
Code:
$su
#cd /data/data
#cd com.android.providers.settings
#cd databases
#sqlite3 settings.db
>select * from secure where name='android_id'
ABC(this is the new android id)
>update secure set value='xyZ' where name='android_id'
>select * from secure where name='android_id'
xyZ(Mission accomplished if done correctly :yay:)
>.exit
#reboot
Click to expand...
Click to collapse
Thanks, I will try this and update
karandpr said:
Every time you flash a new ROM ,your device ID changes ...In fact every time you factory reset the phone ,you change the device ID
I wrote a post on how to maintain the device ID across ROMs and devices !
It requires a little knowledge of SQL though ...
Check it out
Backing up the original ID from the Backup/ROM
Code:
$su
#cd /data/data
#cd com.android.providers.settings
#cd databases
#sqlite3 settings.db
>select * from secure where name='android_id'
xyZ(this is the original android id)
>.exit
#reboot
Note down the xyZ
Restoring the ID on new ROM
Code:
$su
#cd /data/data
#cd com.android.providers.settings
#cd databases
#sqlite3 settings.db
>select * from secure where name='android_id'
ABC(this is the new android id)
>update secure set value='xyZ' where name='android_id'
>select * from secure where name='android_id'
xyZ(Mission accomplished if done correctly :yay:)
>.exit
#reboot
Click to expand...
Click to collapse
Hi, I tried this but it somehow didn't show the android id (screenshot attached)...did I do anything wrong?
My mistake ...end the statement with
;
... ...the query is alright ...just sqlite3 has strict rules i guess...
Sent from my SK17i using Tapatalk
karandpr said:
My mistake ...end the statement with
;
... ...the query is alright ...just sqlite3 has strict rules i guess...
Sent from my SK17i using Tapatalk
Click to expand...
Click to collapse
Yes, it did worked this time thanks....Now I will install RealICS and restore backup and see if BBM works with same id
Change id first and install BBm afterwards .. ..
Verify the changed id on boot...
It will work imo ...
Sent from my SK17i using Tapatalk
karandpr said:
Change id first and install BBm afterwards .. ..
Verify the changed id on boot...
It will work imo ...
Sent from my SK17i using Tapatalk
Click to expand...
Click to collapse
Hi karandpr,
Your above method worked perfectly...while installing I got a message "[email protected] email is already associated with BBM on another device. Do you want to switch your BBM information to your current device?" (screenshot attached)...I clicked on "Switch BBM" option and got the same PIN...BUT now all my contacts are gone any clue why this happened?
thanks!
No idea ! ...
I dont even use BBM...
I am just well aware of device authentication techniques used by app developers
Use titanium backup to backup/restore app data ?
Sent from my SK17i using Tapatalk
karandpr said:
No idea ! ...
I dont even use BBM...
I am just well aware of device authentication techniques used by app developers
Use titanium backup to backup/restore app data ?
Sent from my SK17i using Tapatalk
Click to expand...
Click to collapse
I tried to restore from GoBackup & also restored my nandroid back but no use my contacts & groups are deleted
Now it seems whatsapp is better than BBM but only drawback is that anyone having ur phone number can ping u
Thanks for ur help!!!
dexter1123 said:
I tried to restore from GoBackup & also restored my nandroid back but no use my contacts & groups are deleted
Now it seems whatsapp is better than BBM but only drawback is that anyone having ur phone number can ping u
Thanks for ur help!!!
Click to expand...
Click to collapse
That sounds pretty stupid imo ...:/ ...
I could care less about what messaging app one uses...
There are tons of alternatives available ...
Sent from my SK17i using Tapatalk
try backup with titanium backup before changing rom.. and immediately flash rom and restore you're bbm with titanium backup after flash and boot into homescreen.. i have try it yesterday and succes..
friza.inamorta said:
try backup with titanium backup before changing rom.. and immediately flash rom and restore you're bbm with titanium backup after flash and boot into homescreen.. i have try it yesterday and succes..
Click to expand...
Click to collapse
Didn't you restored ur android id after changing the ROM?
Below are the steps which I have understood, is this what you exactly did?
1. Backup BBM using Titanuim backup pro (Do I need to backup anything else?)
2. Flash new ROM
3. Boot into new ROM
4. Install Titanium backup pro as first step (without connecting internet ?)
5. Restore BBM
dexter1123 said:
Didn't you restored ur android id after changing the ROM?
Below are the steps which I have understood, is this what you exactly did?
1. Backup BBM using Titanuim backup pro (Do I need to backup anything else?)
2. Flash new ROM
3. Boot into new ROM
4. Install Titanium backup pro as first step (without connecting internet ?)
5. Restore BBM
Click to expand...
Click to collapse
no.. maybe my android id isn't changing..
yesterday I'm change rom cm10.1 to cm10.2 my pin is changed.. I'm back to cm10.1 and reflash cm10.2 and Im trying this my pin back in cm10.2..
sory for bad english.. hope yu understand.. hehe
karandpr said:
Every time you flash a new ROM ,your device ID changes ...In fact every time you factory reset the phone ,you change the device ID
I wrote a post on how to maintain the device ID across ROMs and devices !
It requires a little knowledge of SQL though ...
Check it out
Backing up the original ID from the Backup/ROM
Code:
$su
#cd /data/data
#cd com.android.providers.settings
#cd databases
#sqlite3 settings.db
>select * from secure where name='android_id'
xyZ(this is the original android id)
>.exit
#reboot
Note down the xyZ
Restoring the ID on new ROM
Code:
$su
#cd /data/data
#cd com.android.providers.settings
#cd databases
#sqlite3 settings.db
>select * from secure where name='android_id'
ABC(this is the new android id)
>update secure set value='xyZ' where name='android_id'
>select * from secure where name='android_id'
xyZ(Mission accomplished if done correctly :yay:)
>.exit
#reboot
Click to expand...
Click to collapse
The simplest method to solve BBM PIN problem ...(i never had this problem though) is to use TITANIUM BACKUP ....
If you want to use another method shown above in QUOTE ...with easily or if u dont want to wrote commands ...then follow steps ...
-DOWNLOAD Sqlite EDITOR from play store or (google it)
-Go to APPS tab
-Find the app named "setting storage" and go to "Settings.db"
-Open it and
-Go to SECURE
-scroll to 26 line named "android_id"
Copy it note down
-Flash new rom
Use same method and goto settings.db and again 26 line and paste it ....or write it down
Reboot ....done ....
http://imgur.com/bgL4Fgj.png
Sent from my Xperia Live with Walkman using XDA Premium 4 mobile app
rahil3108 said:
The simplest method to solve BBM PIN problem ...(i never had this problem though) is to use TITANIUM BACKUP ....
If you want to use another method shown above in QUOTE ...with easily or if u dont want to wrote commands ...then follow steps ...
-DOWNLOAD Sqlite EDITOR from play store or (google it)
-Go to APPS tab
-Find the app named "setting storage" and go to "Settings.db"
-Open it and
-Go to SECURE
-scroll to 26 line named "android_id"
Copy it note down
-Flash new rom
Use same method and goto settings.db and again 26 line and paste it ....or write it down
Reboot ....done ....
http://imgur.com/bgL4Fgj.png
Sent from my Xperia Live with Walkman using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks..thats easy
Returning to oreo GUIDE
We are going to speak about Returning to oreo for Samsung J4 PLUS .
Requirements
- Any archive decompress tool .
WINDOWS : Winrar & 7zip .
LINUX : U can use shell or any archive decompress tool .
ANDROID : Zarchiver .
- Custom recovery .
- LZ4 Tool .
WINDOWS : Here .
LINUX : Package name is liblz4-tool .
ANDROID : Use termux app , pkg update ; pkg install lz4 .
- Oreo stock rom .
Code:
U CAN'T FIND IT FREE ON MOST SITES OR IT WAS DELETED FROM OTHER SITES .
BUT I FOUND THIS SITE PROVIDES STOCK ROM FOR FREE AND WITHOUT SIGN IN , BUT DOWNLOADING SPEED IS SLOW :
[URL="https://samfrew.com/"][COLOR="Red"]SITE LINK[/COLOR][/URL] .
- Patience .
Lets start steps
A - Preparing . . .
Download oreo stock rom .
Unzip stock rom zip .
Rename AP ( tar.md5 to tar ) .
Decompress AP ( system - boot - vendor) & CSC ( odm only ) tar files in a dir (eg work) . ( WINDOWS : 7ZIP )
Decompress lz4.zip in previous dir ( WINDOWS ONLY)
Open cmd ( WINDOWS ) or console ( LINUX ) or termux ( ANDROID , but if u face issue try to move files to termux home dir using com.android.documentsui app , it is in any android system ) in previous dir .
Open as root or administrator write this :
Code:
- lz4 -d system.img.ext4.lz4 --no-sparse . ( [COLOR="red"]WINDOWS : lz4.exe [/COLOR])
Then delete system lz4 compressed file .
- lz4 -d -m *.lz4
Then delete all lz4 compressed file .
Rename all img.ext4 to img .
Copy all ( system - vendor - boot - odm ) img to your phone .
B - Installing . . .
- Reboot recovery
- Wipe data , system , vendor .
- From custom recovery teriminal or adb shell , go to img saved location ( using cd command ) :
Code:
- simg2img odm.img odm.raw
- dd if=odm.raw of=/dev/block/bootdevice/by-name/odm
- Install system .
Notice : With twrp , Better to reboot recovery .
- Install boot , vendor .
- Install custom kernel . (if u want)
- Install security disable stuff :
J6+ J4+ disable encryption : here .
Disable all pie security : here .
- Install magisk .
C - Waiting until it boot . . .
- Done phone booted . :good:
Thanks
• @ashyx for Twrp & J6+ J4+ disable encryption .
• @SebaUbuntu for custom recoveries .
• me for writing this thread .
• @topjohnwu for magisk .
Indonesia region try this mirror https://drive.google.com/file/d/1lGxg2R5HJiBRWvNy1uMBKd-RJ56u49Gt/view
Credit nanda.id
Can I lock the bootloader after this?
btw thanks so much for this guide, I've always wanted to downgrade...
this phone has been flashed with unauthorized software, meh.
If you're running Pie, stay there and be happy.
blackhawk said:
If you're running Pie, stay there and be happy.
Click to expand...
Click to collapse
my touchscreen didn't work after updating to the latest one
How to fix this phone has been flashed with unauthorized software
i have not working face and fingerprint unlock..
nick D1256 said:
i have not working face and fingerprint unlock..
Click to expand...
Click to collapse
i cant register it
zawarud0 said:
this phone has been flashed with unauthorized software, meh.
Click to expand...
Click to collapse
Install medusa Kernel
Hello. I have J6+ and followed all the steps carefully but I have the problem of
"your device has been flashed with unauthorized firmware and is locked"
what can I do? I really want an Android 8 or 8.1 custom ROM
PHP:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
FEATURES
. The first, the one and the only custom vendor for dynamic partition in the world : I challenge you all to show me who did it before !
. If you find any custom rom with similar work since the first release of this one : it is just a copied and a stolen work [fake Google roms +++] !!!
. Compatible with all regions / basebands / firmwares / device variants
. Works with All AOSP/CAF based ROMs [10] & [11], Experimental, Official & Unofficial [TESTED]
. May works on fake Google roms but i don't take any responsibility
. Mount RO/RW available with no bootloop after reboot ! [Magisk/SU required]
. SafetyNet passed
. Full test passed : audio, ril, wifi, bt, fm radio, camera, sensors, fp scanner, nfc, ...
. All known hardware issues on custom roms are fixed : camera, wifi, bt, hdr playback, chrome ... and overheating !
. Custom Kernel with stock zImage [untouched +++]
IMPORTANT !
. NO firmware change is needed from the user side, so don't repeat this question many times ... just read up again !
. Formatting /data is required when you flash this vendor the first time +++
. Never go back to the previous versions due to the possible build.fingerprint change [Old releases are automatically removed] +++
. Dirty Update : always delete with file/root explorer or in TWRP this folder :
/data/property and reboot
You must delete these files & folders in /product partition from your custom rom
[File/Root explorer needed] :
/product/vendor_overlay/29/etc/audio
/product/vendor_overlay/29/etc/audio_policy_configuration.xml
/product/vendor_overlay/29/etc/audio_policy_engine_configuration.xml
/product/vendor_overlay/29/lib/soundfx
/product/vendor_overlay/29/lib64/soundfx
&
/product/vendor_overlay/29/etc/wifi
/product/vendor_overlay/29/overlay
& finally
/product/vendor_overlay/29/etc/qdcm_calib_data_nt36672c_huaxing_fhd_video_mode_dsi_panel.xml
/product/vendor_overlay/29/etc/qdcm_calib_data_nt36672c_tianma_fhd_video_mode_dsi_panel.xml
Already included in this vendor ... and since i'm the original author !
[ OPTIONAL ]
If you have the madness and the paranoia with security like Google, you can still relock /vendor again to the stock RO state ... But you will not be able to mount /vendor RW again even with root until you reflash the provided vendor.zip again !
How to [terminal or adb shell] :
su
tune2fs -O verity /dev/block/dm-1
*******
!!!
MIUI Users : sorry for you, but this is for custom ROMS " ONLY "
TROLLS & NOOBS, stay away ... Please !
!!!
Prerequisite:
POCO X3 NFC = surya
POCO X3 [no NFC] = karna
No matter where you live : india, china, russia, europe, usa or africa ... !
Kernel Source [Prebuilt] : Here
Created : 2021-02-27
Latest Update : 2021-03-21
DOWNLOAD
RESERVED for "Changelog"
Update : [2021-03-21] Highly Recommended !
- overlay folder [/vendor] : secure & total remove ... R.I.P forever !
You can now remove it from here too ... with no issue :
/product/vendor_overlay/29/overlay
[As always : no /data formatting is required if done in the previous builds !]
Update : [2021-03-20]
fix compatibility with all custom roms [10] & [11] +++ :
- build : preserve AVB structure [R/W still available in root mode]
- tune2fs : restore some stock feature flags [dir_index, huge_file, extra_isize]
- fstab [kernel & vendor] : small update
- vendor selinux : property_contexts fix
- build.prop : clean-up
Update : [2021-03-18]
clean-up & rework from scratch :
. all audio config [over 20 files +++]
. all media_codecs config
. new mixer_paths
[=> Exclusive]
- true resampling fix : r.i.p audio crackling and all audio issues in UX, Dialer, emulators ... etc [forever]
- improve audio & camera recording
- audio/video playback [Speaker, Headphones & BT] : Hi-Fi quality, loud & noiseless
[but first, you must delete these files with your File/Root Explorer:
/product/vendor_overlay/29/etc/audio
/product/vendor_overlay/29/etc/audio_policy_configuration.xml
/product/vendor_overlay/29/etc/audio_policy_engine_configuration.xml
/product/vendor_overlay/29/lib/soundfx
/product/vendor_overlay/29/lib64/soundfx]
Update : [2021-03-12]
- move to global 12.0.8.0 as firmware base [boot & vendor]
- ramdisk :
. disable mi_thermald and re-enable again thermal-engine
[on all custom roms : mi_thermald breaks the proximity sensor & suspend service in deepsleep => avoid hand wave gesture & AOD to work properly !]
. clean up & update
- vendor_selinux : add more camera permissions in property_contexts
- media_codecs : remove unused .xml
- ueventd.rc : rework from scratch
Update : [2021-03-07]
- ramdisk :
. update cpuset & schedtune settings
. improve memory multitasking
. make that "damn" fingerprint truly responsive
. enable UFS powersaving
. some clean-up & disable MIUI audio service
- media_profiles :
. rework from scratch
. add slow motion profile support : up to 1080p/120 fps & 720p/960 fps
. front video camera : add 4K support
- build.prop :
=> update parameters for : camera, ril, performance, playback ... and more
Update : [2021-03-05]
- rework from scratch : init.qcom.sh & init.qcom.post_boot.sh
- ramdisk : clean-up and add init.qcom.power.rc
. fix CPU instability : set 300 mHz as CPU minimum frequency for all cores / update schedutil governor parameters
. cpu_boost : improve touch responsiveness
. add built-in display power saving [for both huaxing & tianma panels]
- vendor permissions : rebuild from scratch / fix wronlgy settled paths (by Xiaomi) in some qti.xml
- camera : rework from scratch ISO/lowlight config
- remove dummy hbtp folder ... since there is no binary to load or device specific config
- targetconfig : update CoreCtlCpu to [0,6]
- build.prop : clean up and move NFC parameters to build_surya.prop
- [Bonus] : Wi-Fi signal improved (x2) !!!
. 2.4 Ghz : 144 => 300
. 5 GHz : 433 => 866
[but first, you must delete this folder, with your File/Root Explorer :
/product/vendor_overlay/29/etc/wifi ]
Update : [2021-03-01]
- update msm_irqbalance.conf
- update audio_effects.conf & remove audio_effects.xml
- universal vbmeta & vbmeta_system added
Update : [2021-02-27]
- initial release
- rework all build.prop (vendor & odm) from scratch
- debloated from unused MIUI folders, files & configs
- Kernel :
. enforcing selinux by default
. workqueue enabled in cmdline => better dynamic refresh rate handling by the CPU & stellar deep-sleep
. fstab reworked from scratch
the image you made is for enable rw or not?
my phone is poco x3 nfc surya
janhammer504 said:
To make things clear :
POCO X3 NFC = surya
POCO X3 (no NFC) = karna
No matter where you live (india, china, russia, europe, usa or africa) ... Choose the right vendor.img for your device !
[Both images were tested by me]
Click to expand...
Click to collapse
please share the surya image
aallii2 said:
please share the surya image
Click to expand...
Click to collapse
check the DOWNLOAD link up !
janhammer504 said:
check the DOWNLOAD link up !
Click to expand...
Click to collapse
tnx bro i'm downloading n i'll test
its not working after restart didnt boot n just go to recovry
aallii2 said:
its not working after restart didnt boot n just go to recovry
Click to expand...
Click to collapse
Wich firmware version you had just before flashing ???
The vendor provided must match the firmware version that you have !!!
janhammer504 said:
PREREQUISITE
- adb enabled (developer options)
- root (Magisk/SU)
- adb for Windows (Minimal ADB and Fastboot, provided)
- USB cable always connected
LIVE Flashing :
adb shell
su
dd if=/sdcard/vendor.img of=/dev/block/dm-1
View attachment 5232189
Reboot your phone right away ... then use your File/Root Explorer to test the mount RO/RW option and reboot again to check that there is no bootloop !
(Optional)
If you have the madness and the paranoia with security like Google, you can still re-enable AVB/Verity again ... But you will not be able to mount /vendor RW again even with root until you reflash the provided vendor.img again !
tune2fs -O verity /dev/block/dm-1
Check the full tutorial here to build your own custom vendor ... if you want !
DOWNLOAD
Click to expand...
Click to collapse
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
jeryll said:
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
Click to expand...
Click to collapse
i use adb shell because terminal is too small for me, and for making tutorial.
the benefit ??? well there are a bunch of fixes to do in /vendor... check here for example
(the images i provided are clean with no modification, so i let developers or users doing their own modifications)
janhammer504 said:
Wich firmware version you had just before flashing ???
The vendor provided must match the firmware version that you have !!!
Click to expand...
Click to collapse
india 12.0.9
magisk 21.4
jeryll said:
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
Click to expand...
Click to collapse
hey bro how you flashed in orangefox?
i tried but this happened:
sh: adb: command not found
aallii2 said:
hey bro how you flashed in orangefox?
i tried but this happened:
sh: adb: command not found
Click to expand...
Click to collapse
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
now i cant install any rom :
updater process ended with error 7
pls help
aallii2 said:
now i cant install any rom :
updater process ended with error 7
pls help
Click to expand...
Click to collapse
O.M.G
it looks like you never used terminal
this is not a flashable file, it's a command line.
open terminal in your recovery to do that.
or use adb shell
janhammer504 said:
O.M.G
it looks like you never used terminal
this is not a flashable file, it's a command line.
open terminal in your recovery to do that.
or use adb shell
Click to expand...
Click to collapse
jeryll said:
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
Click to expand...
Click to collapse
Now this came:
write error: Operation not permitted
jeryll said:
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
Click to expand...
Click to collapse
Now this came:
write error: Operation not permitted
Use Minimal ADB and Fastboot.zip, it's the simplest and the fastest way.
Unzip and click on Minimal ADB and Fastboot.exe
type :
adb shell
su
It works like terminal in Windows. You can't go wrong !
Follow the instructions (1 post) !
aallii2 said:
india 12.0.9
magisk 21.4
Click to expand...
Click to collapse
wtf man, you should pick vendor.img from karna folder not surya !
janhammer504 said:
Use Minimal ADB and Fastboot.zip, it's the simplest and the fastest way.
Unzip and click on Minimal ADB and Fastboot.exe
type :
adb shell
su
It works like terminal in Windows. You can't go wrong !
Follow the instructions (1 post) !
Click to expand...
Click to collapse
i installed 12.0.7.0 global with magisk 22.0 then flashed vendor.img v12.0.7.0 but when restarted it stucked n i pressed power .phone boot but root explorer can't mount rw n just added shell in magisk