Op6t international Pls help! - OnePlus 6T Questions & Answers

hi guys!pls help a noob!!
Does anyone really knows how to properly edit build.prop op6t international rooted version oxygen os 9.0.16 without getting softbricked? To edit it, guess any beginner knows how..but when it comes on saving..thats a big prb...not only that the build.prop it erase itself.you can't paste back the original copied file into the system folder..it lets you to paste it but after shows 0 KB(same after saving error)
Got softbricked twice trying to modify the
ro.product.brand
ro.product.manufacturer
(couple lines up also) ro.build.product.device
//
I wonder if i try to edit/save anything gettin same bootloop:silly:
I didn't try with system_root folder (buil.prop its the same as original)...
// also need some info how to do a clean backup on the build.prop and system.cuz nandroid backup failed
//
extra info: tried with plenty prop editors same prb
twrp vers: 3.3.1 latest
magisk 19.3 latest
oxygen os up to date ...
pls check screenshots as well!!

Related

[Q] [Help] Problem with NAND Kitchen

Hello
I would like to use Android on my HD2. I was searching and testing many ROMS but I didn´t find any rom which is usable for me. I would like to have a ROM that is without Sense, has Multilanguage support and is on Android 2.2 version.
So I decided that I would make my own.
0) I was reading
HTML:
http://forum.xda-developers.com/showpost.php?p=10291851&postcount=1
and made this procedure.
1)downloaded some ROM from here
2)unpacked this rom in linux with :
Code:
unyaffs system.img
then I got this directories:
Code:
app bin build.prop etc fonts framework lib media usr xbin
3)I downloaded update-cm-6.1.1-N1-signed.zip from CyanogenMod Forum > Downloads > Stable Mod > Nexus One and unpacked. I got : META-INF system boot.img.
4)I copied everything what was described step 0 from directories from step 2 to directory system from step 3
5)I downloaded and copied build.prop from step 0 to system
6) I updated permition like it is described in step 0
7) I created system.img with command : mkyaffs2image . ../system.img
Then I copied this system.img from linux to my windows and put this file in directory in which was different NAND rom. (replaced system.img). After that I flashed my phone and it did not work. Screen was frozen after booting and only green HTC was on display.
Can somebody please help me and give me some advice or some small howto. Does anybody know what can be wrong?
UPDATE: If I unpacking any nand roms and packing back everything is ok They must by any problem in me procedure of creating.
Thank you
Michal Fichtner

kitchen rom

I'm creating a cooked rom based on the stock rom ita LT9 4.1.2, you can change the battery in the status bar without Xposed? I would include the circular battery with percentage inside. decompiling an apk? which one?
stefano_te said:
I'm creating a cooked rom based on the stock rom ita LT9 4.1.2, you can change the battery in the status bar without Xposed? I would include the circular battery with percentage inside. decompiling an apk? which one?
Click to expand...
Click to collapse
I think it's enough that you throw it into the SystemUI.apk(have a look inside that apk, if it's not there then it is in secframework.apk) (/res/.../XHDPI). Open the apk in winrar (you might have to rename it from .apk to .zip) and drag and drop the new files. Decompiling isn't necessary for this sort of thing.
Also, check this out:
http://forum.xda-developers.com/showthread.php?t=1918500
I did this a long time ago so some of what I just said might be wrong, if you need more help then just say so.
I would like to use as a basis the stock rom 4.1.2 : N7000XXLT9_N7000ITVLT3_ITV.zip
I used the kitchen to create workfolder following all the steps suggested by the program , I found the following problems:
1 ) during the procedure appeared to me the following warning :
Warning : A valid boot.img is not found . You have the option to add a
' fake ' boot.img So THAT the features of the kitchen can still
function normally.
This boot.img will be automatically removed from your ROM 's
ZIP file When Is It built .
Add boot.img (y / n)? (default: y) "
is this normal? how to solve ?
2 ) Working folder information ( v)
Android OS version: 4.1.2
Device: GT- N7000
Model: GT- N7000
ROM Name : JZO54K.N7000XXLT9
CSC version: It 's normal that there is nothing written here ?
Rooted ( Superuser app + su) : NO
Rooted ( unsecured boot.img ) : UNKNOWN how I fix this ?
BusyBox installed : NO
BusyBox run-parts support: UNKNOWN UNKNOWN how I fix this ?
Apps2SD (Apps to EXT) enabled: NO
/ data / app enabled: NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support: NO
/ system / framework is deodexed : NO
/ system / app is deodexed : NO
modem.bin found: YES
ROM will wipe all data : NO
3) throughout the META-INF folder there are only 2 files: update-script; update-script.bak
4) scripts / get_api_level: line 18: more: command not found
5) I checked the update-script and there are 3 warning in the report:
7/101: copy_dir PACKAGEystem SYSTEM:
8/101: format PRELOAD:
>> WARNING: Partition not recognized
9/101: copy_dir PACKAGEreload PRELOAD:
>> WARNING: PRELOAD: not found in working folder
10/101: symlink dumpstate SYSTEM:bin/dumpcrash
11/101: symlink toolbox SYSTEM:bin/cat
82/101: set_perm_recursive 0 2000 0755 0755 SYSTEM:bin
83/101: run_program PACKAGE:create_preload_symlinks
>> WARNING: create_preload_symlinks not found in working folder
84/101: set_perm 0 3003 06755 SYSTEM:bin/ip
How do I resolve this? I tried a lot of on-line but have not found anything. My goal is to make me a custom rom from the last stock (LT9) ... what should I do?
Check my old tutorial I used myself when cooking Custom Roms for the N7000 with the kitchen. Following the steps should avoid most problems.
ThaiDai said:
Check my old tutorial I used myself when cooking Custom Roms for the N7000 with the kitchen. Following the steps should avoid most problems.
Click to expand...
Click to collapse
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue?
Please wait ...
scripts/choose_rom: line 110: more: command not found
Enter selection number (default=1, cancel=0, r=refresh):
is a problem? I can go on with 1 (default)?
stefano_te said:
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue?
Please wait ...
scripts/choose_rom: line 110: more: command not found
Enter selection number (default=1, cancel=0, r=refresh):
is a problem? I can go on with 1 (default)?
Click to expand...
Click to collapse
Sorry, but only repeating the problems you actually have won't solve anything because it isn't really clear what you did before.
The error here seems to be a hint that your cygwin installation isn't correct.
So please try to follow the steps in my tutorial exactly. Start from scratch.
ThaiDai said:
Sorry, but only repeating the problems you actually have won't solve anything because it isn't really clear what you did before.
The error here seems to be a hint that your cygwin installation isn't correct.
So please try to follow the steps in my tutorial exactly. Start from scratch.
Click to expand...
Click to collapse
It works. I have re-installed windows ...
can you tell me how to add new info in device info? (rom name, rom maker, release date, build version ...)
stefano_te said:
It works. I have re-installed windows ...
can you tell me how to add new info in device info? (rom name, rom maker, release date, build version ...)
Click to expand...
Click to collapse
No. Because you do this partly when using the kitchen step by step. Or when changing your updater-script.
The kitchen is a great help and simplifies cooking a rom - but it still is a little bit more complicated than heating baby food in the microwave. And if you really want your "custom" rom you should start to learn what happens in each step. And this can't be done by revealing everything...

Huawei Y625-U43 "soft" bricked

Hi xda-developers before read my long story sorry for my bad english and I hope you can help me…
I bought this phone recently and because I don't feel comfortable with EMUI I decided to do some modding. I rooted the phone successfully, remove some apps, install a new launcher and at this point everything was fine then i decided to install XPOSED FRAMEWORK.
I didn´t know that Huawei phones has so many problems with Xposed but I took the risk to follow Xposed installation instructions of another Huawei model. I'll write the instructions that I followed.
I changed ro.config.hwtheme in build.prop to 0, reboot and everything was fine
Then I installed a console app to use this commands:
Code:
su
mount -o rw,remount /system
cd system
lsattr
chattr -R -i *
rm –f /system/set_immutable.list
But when i used lsattr and chattr the console display COMMAND NOT FOUND then I read an alternative to that commands.
Code:
chmod –R –i *
I have a little experience with Linux but I had never seen the “-i” modificator on chmod and the console too xD it displays
Code:
“bad mode not valid –i command”
or something similar.
Finally in a moment of stupidity I executed this command
Code:
chmod –R 777 *
I Reboot, Huawei logo then black screen, I remove the baterry, reboot and the same…
Well I only have the default Android recovery on the phone…
I found a ROM but that ROM is for the Huawei Y625-U32 I tried to modify this ROM removing the getprop lines on update-script and resinging the rom with APK SIGN but always trying to flash the signature verification fails.
Finally i read apart of the 3 files that generates APK SIGN in the META-INF folder (cert.rsa, cert.sf and manifest.mf) inside com/android exists other certificates files (otacert and metadata) and this files are related with the file /security/etc/otacerts.zip inside the phone but with Android recovery everything is complicated.
Well after my long story anybody can help me? I thought of these possible solutions:
Anybody can share me a backup ROM (update.App file) of this model (I know is a bit heavy to upload 700MB aprox.)
Help me modifying the Y265-U32 ROM to pass the frustrating signature check of Android Recovery (of course if at the end would be safe to mod that ROM or not )
Or any other suggestion please XDA Friends and thanks in advance.
P.D. I want to try all possibilities before send to technical service besides that the model was released recently (April 2015) and I dont know if they can flash it and sorry for my bad english again.
I'm on Colombia and I have the same model, original firmware can be found here: http://consumer.huawei.com/co/support/downloads/detail/index.htm?id=66735&key4=Y625
This is stock ROM. I recommend you NOT modify your system if you don't know too much.
Hope this helps
Hello guys I have a Huawei Y625-U13 from Mexico. My device is Softbricked, it wont boot up, its stucked at HUAWEI's Logo. I found the firmware to make an update via SD card (dload file). But I can't install it on my device, somebody knows how to?

Soft-Bricked phone (SM-9005, OS: 4.4.2), problem with /system

So Hello everyone, i got interesting problem...
I bricked my phone
Phone: SM-9005
OS: Android 4.4.2
Firmware: N9005XXUGNG1
Recovery: TWRP 3.0 installed.
Root software installed which may be interesting "Xposed Additions, Lucky Patcher, SuperSu, Greenify"
Step by step.
// maybe helpful - cache / dalvik cache wiped and after reboot i started playing stuff
I used Root Browser (com.jrummy.root.browserfree) to copy 2 directories from my /downloads to /system.
There were /lib & /bin which contained unique libs and one executable so this would not affect system if everything went ok, but i didn't
After i started coping, root explorer asked me that "File already exist, overwrite or make a copy"? i pressed overwrite, in same second all apps in android started to generate "unexpected error", i tried to reboot and got boot into recovery
after i watched /system i found that what i tried to copy actually copied not to /system/lib & /system/app but to /system/system/lib & /system/system/app.
So i think there was some folder or file called system in /system directory which was overwritten. Or any kind of problem with dir / file permissions.
Any ideas of how to fix this / what was in /system/system / where to get bootlog to find after what "kernel panic" takes place or any other help?
Thanks.
// maybe somebody with same model version, same os version can upload zip file of own /system folder without /apps, /priv-apps and build.prop so i can compare whats lost compared to my data?
Fixed myself, root browser set wrong permissions to /system while was coping files... set back to 755 and it works

OP5 upgraded to Android 10 and rooted with Magisk, system changes don't stick

Hi,
Just upgraded my OP5 to Android 10 official stable version. Rooted successfully with Magisk 20.4
Now I'm trying to do some changes to the system folder but they revert back when I reboot.
1- Trying to replace the emoji with another ttf file, as I always did in Pie but the file gets reverted upon restart.
2- Trying to apply hosts file for ad blocking, same issue the file gets reverted as soon as I restart.
it looks like my system partition is reverting itself for some reason, does anyone know why this happens and how to make the changes stick?
PS: I don't want to enable (Systemless hosts in Magisk) because I'm planning to unroot after doing these changes.
thanks..
medo159 said:
Hi,
Just upgraded my OP5 to Android 10 official stable version. Rooted successfully with Magisk 20.4
Now I'm trying to do some changes to the system folder but they revert back when I reboot.
1- Trying to replace the emoji with another ttf file, as I always did in Pie but the file gets reverted upon restart.
2- Trying to apply hosts file for ad blocking, same issue the file gets reverted as soon as I restart.
it looks like my system partition is reverting itself for some reason, does anyone know why this happens and how to make the changes stick?
PS: I don't want to enable (Systemless hosts in Magisk) because I'm planning to unroot after doing these changes.
thanks..
Click to expand...
Click to collapse
Just forget to change hosts file manualy, use the better Adbloacker Rootless, Blokada
medo159 said:
QUOTE
Click to expand...
Click to collapse
Hi Mate,
Ensure to give proper permissions as follows: rw-r--r-- (0644) to the file. If it is a folder, the permissions are: rwxr-xr-x (0755)
medo159 said:
Hi,
Just upgraded my OP5 to Android 10 official stable version. Rooted successfully with Magisk 20.4
Now I'm trying to do some changes to the system folder but they revert back when I reboot.
1- Trying to replace the emoji with another ttf file, as I always did in Pie but the file gets reverted upon restart.
2- Trying to apply hosts file for ad blocking, same issue the file gets reverted as soon as I restart.
it looks like my system partition is reverting itself for some reason, does anyone know why this happens and how to make the changes stick?
PS: I don't want to enable (Systemless hosts in Magisk) because I'm planning to unroot after doing these changes.
thanks..
Click to expand...
Click to collapse
You can't mount the system partition as rw directly in Android 10. Here's a thread by topjohnwu (slightly technical, but give it a read) on why: https://twitter.com/topjohnwu/status/1259039809361739776

Categories

Resources