What about Treble support on this device? Is TWRP (or another custom recovery) avialiable? What wouldn't work in GSI?
This device is both treble and seamless update compatible/supported.
So how to run GSI firmwares on this device?
How to create /vendor, flash it and etc?
aaa.bbb111222 said:
So how to run GSI firmwares on this device?
How to create /vendor, flash it and etc?
Click to expand...
Click to collapse
Try out the official instructions from the XDA Treble thread, and report back. If it works, I'm sure we can get together a few people here and try to tweak the development further.
I had pixel experience running on it. Worked pretty well, except no aod, and vibrator didn't work.
suzook said:
I had pixel experience running on it. Worked pretty well, except no aod, and vibrator didn't work.
Click to expand...
Click to collapse
Could you give the steps on how you did it? is it just fastboot flash img? do we have to disable verity or something
suzook said:
I had pixel experience running on it. Worked pretty well, except no aod, and vibrator didn't work.
Click to expand...
Click to collapse
hi, may i know did you try phh aosp recent build? i try before and it bootloop.
atoyu said:
hi, may i know did you try phh aosp recent build? i try before and it bootloop.
Click to expand...
Click to collapse
1) You need a vbmeta.img from fastboot ROM.
2) Flash the vbmeta.img using the command, fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img, this is done to disable dm-verity to let the GSI boot.
3) Download the latest A/B GSI
4) Extract and flash the GSI using the command, fastboot flash system filename.img, replace filename with the name of the image.
suzook said:
1) You need a vbmeta.img from fastboot ROM.
2) Flash the vbmeta.img using the command, fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img, this is done to disable dm-verity to let the GSI boot.
3) Download the latest A/B GSI
4) Extract and flash the GSI using the command, fastboot flash system filename.img, replace filename with the name of the image.
Click to expand...
Click to collapse
Wow nice!
We should try to make a step by step thread in the ROMS forums to get more people to try out custom roms.
stealthj said:
Wow nice!
We should try to make a step by step thread in the ROMS forums to get more people to try out custom roms.
Click to expand...
Click to collapse
Just copy and paste my instructions.
I wish we had multi rom
---------- Post added at 06:57 PM ---------- Previous post was at 06:40 PM ----------
suzook said:
Just copy and paste my instructions.
Click to expand...
Click to collapse
Sounds good! I'll give credit where its due. Let me go ahead and try it out later on this week first.
So how was the rom running? Was it at full 120hz? Battery was ok?
stealthj said:
I wish we had multi rom
---------- Post added at 06:57 PM ---------- Previous post was at 06:40 PM ----------
Sounds good! I'll give credit where its due. Let me go ahead and try it out later on this week first.
So how was the rom running? Was it at full 120hz? Battery was ok?
Click to expand...
Click to collapse
Did it / does it work well? Any help going from full stock WW model to gsi?
I assume the unlock tool on https://www.asus.com/tw/Phone/ROG-Phone-II/HelpDesk_Download/ is universal WW/CN?
Please advise in eli5 detail.
@suzook
Thanks in advance
All sorted I will post a tutorial now
MANICX100 said:
All sorted I will post a tutorial now
Click to expand...
Click to collapse
Looking forward to this.
On a second note.
1. Does the official unlocking tool need internet to work i.e will forward IMEI and other identifiers to Asus.
2. Is there a way we can figure out how to unlock the bootloader without using the Asus official tool?
gorgorven said:
Looking forward to this.
On a second note.
1. Does the official unlocking tool need internet to work i.e will forward IMEI and other identifiers to Asus.
2. Is there a way we can figure out how to unlock the bootloader without using the Asus official tool?
Click to expand...
Click to collapse
1.) Yes, Internet is needed and yes it transmits the IMEI
2.) Not at this time
3.) My tutorial is live here: https://forum.xda-developers.com/rog-phone-2/how-to/guide-install-gsi-image-google-apps-t3998133
MANICX100 said:
1.) Yes, Internet is needed and yes it transmits the IMEI
2.) Not at this time
3.) My tutorial is live here: https://forum.xda-developers.com/rog-phone-2/how-to/guide-install-gsi-image-google-apps-t3998133
Click to expand...
Click to collapse
I checked out the link. Thanks for the guide and this reply.
If anyone knows of a forum thread trying to unlock without the official tool (haven't found a thread dedicated to this as of yet) or any resource threads which can help me learn and try it myself, please do point me in that direction.
Thanks again.
gorgorven said:
unlock without the official tool
Click to expand...
Click to collapse
I think that it's possible to reverse engineer way tool works using Something like apktool (if code is Java) or disassembler (if it's C/C++/etc).
Also, what about change IMEI to your old phone's one before using the tool and changing it back after that? (Any ID codes that device maybe are needed to be changed too)
aaa.bbb111222 said:
I think that it's possible to reverse engineer way tool works using Something like apktool (if code is Java) or disassembler (if it's C/C++/etc).
Also, what about change IMEI to your old phone's one before using the tool and changing it back after that? (Any ID codes that device maybe are needed to be changed too)
Click to expand...
Click to collapse
Even I believe that we should be able to do something, however my experience in this is modest at best. I am a nweeb.
Though the way I believe the official tool would work is.... And please correct me if am wrong...
1. It should send the IMEI no to the server.
2. The server sends a code to unlock the bootloader.
3. The tool unlocks the boot loader.
Now steps one and three can be reverse engineered. But unless step two is something like a MD5 hash of the IMEI etc, we might need to figure a way to do the unlocking in a new way.
I don't know if we even can change the IMEI without access to the root folder. I never had a phone since my Galaxy S2 which wasn't unlocked and rooted. I will do some research.
If anyone has any idea.... Kindly let us know.
Just curious - anyone here who tried GSI's stayed with them? I wonder how many bugs are there out of the box. There are some annoying bugs with recent WW ASUS software (like some SMS not being saved, but delivered to my wristband, touchscreen getting freezed with fingerprint unlock on after some phone locks) that really makes me wanna change that soft.
I do not care about gaming functions missing (like 60+Hz refresh rate, back LEDs).
Maczuga said:
Just curious - anyone here who tried GSI's stayed with them? I wonder how many bugs are there out of the box. There are some annoying bugs with recent WW ASUS software (like some SMS not being saved, but delivered to my wristband, touchscreen getting freezed with fingerprint unlock on after some phone locks) that really makes me wanna change that soft.
I do not care about gaming functions missing (like 60+Hz refresh rate, back LEDs).
Click to expand...
Click to collapse
I have stayed with phhussons GSI. As you say no 90/120Hz or back LED. Only other quirk is that apps think the fingerprint scanner is on the back , not in the screen. The fingerprint scanner still works, but makes it awkward to press 0 on your pin pad.
FYI: If you use the gapps build you can flash over an earlier months without losing any data!
Related
Hello everyone.
Unfortunately my lg g4 bootlooped. And after extensive Google search, i see that most models have a tot file which disables big cores so u can run the phone on the small cores
Does the T-Mobile variant have such a tot file? if yes then can somebody give me the link? if no then can somebody create one using the following info?
Agimax said:
Why not just edit the files below for the two large cores (if you have root):
/sys/devices/system/cpu/cpu4/online (open file and change from a one to a zero)
/sys/devices/system/cpu/cpu5/online (open file and change from a one to a zero)
You could also just have the startup file do it (can modify the ripped system partition & put back on phone):
etc/dir/init.qcom.post_boot.sh (find your processor code - 8992 and add echo lines there with the rest of the cpu commands)
Click to expand...
Click to collapse
Please I'd be highly thankful if someone can help
XeniX_Force said:
Hello everyone.
Unfortunately my lg g4 bootlooped. And after extensive Google search, i see that most models have a tot file which disables big cores so u can run the phone on the small cores
Does the T-Mobile variant have such a tot file? if yes then can somebody give me the link? if no then can somebody create one using the following info?
Please I'd be highly thankful if someone can help
Click to expand...
Click to collapse
no such thing for any american variant
raptorddd said:
no such thing for any american variant
Click to expand...
Click to collapse
Cant someone with a working G4 crate one? i quoted a person who has given the way how to...
XeniX_Force said:
Cant someone with a working G4 crate one? i quoted a person who has given the way how to...
Click to expand...
Click to collapse
not sure . i cant...
sort of read this quickly does this help.? https://www.xda-developers.com/nexus-6p-bootloop-fix/
raptorddd said:
not sure . i cant...
sort of read this quickly does this help.? https://www.xda-developers.com/nexus-6p-bootloop-fix/
Click to expand...
Click to collapse
Well he also created modified boot images which disable the big cores. Can't someone create that for our device?
maybe @steadfasterX can
XeniX_Force said:
Well he also created modified boot images which disable the big cores. Can't someone create that for our device?
maybe @steadfasterX can
Click to expand...
Click to collapse
TWRP installed?
Then u could just modify the init file but I believe its too late. once bootlooping the run is over afaik.
.
steadfasterX said:
TWRP installed?
Then u could just modify the init file but I believe its too late. once bootlooping the run is over afaik.
.
Click to expand...
Click to collapse
yeah I'm bootlooped
Someone also fixed the Nexus 6 bootloop by creating modified images which disable the big cores.
Can't we(mostly you, you're the big dev) create a similar modified image that we can flash through LGUP?
XeniX_Force said:
yeah I'm bootlooped
Someone also fixed the Nexus 6 bootloop by creating modified images which disable the big cores.
Can't we(mostly you, you're the big dev) create a similar modified image that we can flash through LGUP?
Click to expand...
Click to collapse
you may have overseen it but I asked: TWRP installed?
and new question: bootloader unlocked?
I can't create TOT files
.
steadfasterX said:
you may have overseen it but I asked: TWRP installed?
and new question: bootloader unlocked?
I can't create TOT files
.
Click to expand...
Click to collapse
I'm bootlooped. can't reach anything except download mode
and yeah bootloader was unlocked.
oh you can't create tot files? aren't they just system images?
XeniX_Force said:
I'm bootlooped. can't reach anything except download mode
and yeah bootloader was unlocked.
oh you can't create tot files? aren't they just system images?
Click to expand...
Click to collapse
Afaik you need a box to create tot files.
Besides this I have never created any big core disabling but I know @the_naxhoo has.
if you can reach the download mode you could flash with the lglaf shell a modified boot image which is doing the job. If you do not have Linux get your copy of FWUL which has everything on board (like the lglaf shell).
The modded boot image has to disable the cores either by the cmdline or the sys echo or both. I saw that cmdline thing during my unlock attempts and think those are much better then the echo to sys..
Creating a kdz would be maybe possible
creating a TWRP zip for sure but I'm very very busy at the moment...
So just one more time (as still not answered.. ) do you had TWRP installed before the bootloop occurs?
...and If so what happens when you try to get into it?
.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Afaik you need a box to create tot files.
Besides this I have never created any big core disabling but I know @the_naxhoo has.
if you can reach the download mode you could flash with the lglaf shell a modified boot image which is doing the job. If you do not have Linux get your copy of FWUL which has everything on board (like the lglaf shell).
The modded boot image has to disable the cores either by the cmdline or the sys echo or both. I saw that cmdline thing during my unlock attempts and think those are much better then the echo to sys..
Creating a kdz would be maybe possible
creating a TWRP zip for sure but I'm very very busy at the moment...
So just one more time (as still not answered.. ) do you had TWRP installed before the bootloop occurs?
...and If so what happens when you try to get into it?
.
Click to expand...
Click to collapse
i had twrp but now when i try to access twrp i get to wipe everything screen which then hangs when I choose yes
yeah I can get FWUL but i need steps to know what to do....
I even asked @XCnathan32 who just fixed the Nexus 6p bootloop to have a look into our device maybe he can benefit from this information u just posted.
XeniX_Force said:
i had twrp but now when i try to access twrp i get to wipe everything screen which then hangs when I choose yes
yeah I can get FWUL but i need steps to know what to do....
I even asked @XCnathan32 who just fixed the Nexus 6p bootloop to have a look into our device maybe he can benefit from this information u just posted.
Click to expand...
Click to collapse
Cmdline is how I disabled the cores on the Nexus, the fix is easy to do on a boot.img, but LG uses the KDZ files, which use a totally different file structure, and I'm not sure if the LG flash tool has file checks, even on unlocked bootloaders. I will do some research and see what I can do. If anyone has any knowledge on modifying kdz files, please tell me.
XCnathan32 said:
Cmdline is how I disabled the cores on the Nexus, the fix is easy to do on a boot.img, but LG uses the KDZ files, which use a totally different file structure, and I'm not sure if the LG flash tool has file checks, even on unlocked bootloaders. I will do some research and see what I can do. If anyone has any knowledge on modifying kdz files, please tell me.
Click to expand...
Click to collapse
asked steadfasterx about kdz and his reply is as follows
steadfasterX said:
me too. never created KDZs yet but there are tools for it - afaik.
My first approach would have been to flash the boot image in the download mode with the lglaf shell (https://github.com/steadfasterX/lglaf/tree/g4) .
requires to do a flash of a modified boot image with dd on /dev/block/mmcblk0 with the correct seek ..
.
Click to expand...
Click to collapse
XCnathan32 said:
Cmdline is how I disabled the cores on the Nexus, the fix is easy to do on a boot.img, but LG uses the KDZ files, which use a totally different file structure, and I'm not sure if the LG flash tool has file checks, even on unlocked bootloaders. I will do some research and see what I can do. If anyone has any knowledge on modifying kdz files, please tell me.
Click to expand...
Click to collapse
you may take a look on this: https://forum.xda-developers.com/showthread.php?t=2179431
not sure if that works though.. (quite old)
.
steadfasterX said:
you may take a look on this: https://forum.xda-developers.com/showthread.php?t=2179431
not sure if that works though..
.
Click to expand...
Click to collapse
But cant we just create a modified boot img and twrp img and flash through lglaf. then flash a rom zip though twrp?
XeniX_Force said:
But cant we just create a modified boot img and twrp img and flash through lglaf. then flash a rom zip though twrp?
Click to expand...
Click to collapse
sure thats what I said before
.
steadfasterX said:
sure thats what I said before
.
Click to expand...
Click to collapse
can u provide a stock boot img for Nathan to edit?
XeniX_Force said:
can u provide a stock boot img for Nathan to edit?
Click to expand...
Click to collapse
sure what was your installed ROM and version? best would be a link to it as well..
.
steadfasterX said:
sure what was your installed ROM and version? best would be a link to it as well..
.
Click to expand...
Click to collapse
stock. i was using lineage but I returned to stock and got bootloop after some days.
XeniX_Force said:
stock. i was using lineage but I returned to stock and got bootloop after some days.
Click to expand...
Click to collapse
tell me the exact version. v10h, v10n, v20g, v20o .. there are dozens of versions out there..
.
Hello!
I have a Huawei Mate 9 (MHA-L29C432B190). Yesterday I tried to root my Phone to play Pokemon Go with fake gps. After I managed to root my phone, I couldn't boot into TWRP Recovery Mode anymore.
Because I still had some files I needed to flash I installed Flashfire from the PlayStore. I think after I flashed the newest Magisk version(The flash failed because of Error:1), my device got unrooted. But I think my device is still partly rooted because I can't get into Pokemon Go. Everytime I try to start it I get stuck the loading screen. So right now I can't flash anything to get my root back and I don't have the root to use alternative flash applications. I also tried to start return my phone to stock back with a update.app But it can't be installed. I also can't use "fastboot flash recovery twrp.img" I always get " Writing 'recovery'...FAILED (remote:command can't be used/allowed)". And also after some reboots my oem unlock got turned off and I can't turn it on anymore.
I don't have any ideas anymore what to do. I thought I could root my device, so I could unroot properly with superuser. I tried some other application like KingRoot oder OneClickRoot but both of them don't have a rooting method for the Huawei Mate 9 yet. Btw I don't have a backup because of my naivety.
I hope you guys can help me . I appreciate any ideas
Thanks in advance
In summary what do u want???
Sent from my iPhone using Tapatalk Pro
abuk91 said:
In summary what do u want???
Sent from my iPhone using Tapatalk Pro
Click to expand...
Click to collapse
Either way I want a method to root my phone without some flash application or I want a way to return my phone to stock. Or a method to fix TWRP would be fine too.
Kyranix said:
Either way I want a method to root my phone without some flash application or I want a way to return my phone to stock. Or a method to fix TWRP would be fine too.
Click to expand...
Click to collapse
Do a Google search for:
"Return to stock (your model number)"
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Do a Google search for:
"Return to stock (your model number)"
I already did and everything I found didn't work
Kyranix said:
Do a Google search for:
"Return to stock (your model number)"
I already did and everything I found didn't work
Click to expand...
Click to collapse
What did you find? What have you tried?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
What did you find? What have you tried?
I tried to do Upgrades with many different stock firmwares for my model
Kyranix said:
What did you find? What have you tried?
I tried to do Upgrades with many different stock firmwares for my model
Click to expand...
Click to collapse
That doesn't tell me anything. That just tells me that you tried flashing.
It doesn't tell me anything about exactly what you tried to flash or what errors you got when you flashed. I need more precise information to help you. Your simple answers aren't helping me understand anything about what you have going on with your device.
What tools have you used? What guide/instructions did you use? What files have you used? What errors did you get? What results did you get. What do mean "didn't work"? "Didn't work" can mean many things.
I might be able to help you fix your device but I can't fix ignorance.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
That doesn't tell me anything. That just tells me that you tried flashing.
It doesn't tell me anything about exactly what you tried to flash or what errors you got when you flashed. I need more precise information to help you. Your simple answers aren't helping me understand anything about what you have going on with your device.
What tools have you used? What guide/instructions did you use? What files have you used? What errors did you get? What results did you get. What do mean "didn't work"? "Didn't work" can mean many things.
I might be able to help you fix your device but I can't fix ignorance.
First I tried to do a force upgrade with a "dload" folder with a update.app file on my sdcard . After booting into this upgrade mode by pressing vol up + vol down + power button my device starts to install the stock firmware, but after it reaches 5% I get the message "Error with installing" and a Link to the same site when you boot into twrp. This always happens no matter which file I use. Next I tried to do a normal upgrade by calling this number "*#*#2846579#*#*" (The dload folder is still on my sdcard). But when I start the software upgrade I get booted into twrp and like I said in my post, always when I try to get into twrp I get stuck on the "Your device is booting screen". This is what I tried and basicly every site on google is saying I should try to do one of these two methods
(Here a guide for example: https://www.getdroidtips.com/full-guide-install-stock-firmware-huawei-smartphone/)
(My file in my last try: https://www.getdroidtips.com/huawei-mate-9-stock-firmware-collections/)
Kyranix said:
That doesn't tell me anything. That just tells me that you tried flashing.
It doesn't tell me anything about exactly what you tried to flash or what errors you got when you flashed. I need more precise information to help you. Your simple answers aren't helping me understand anything about what you have going on with your device.
What tools have you used? What guide/instructions did you use? What files have you used? What errors did you get? What results did you get. What do mean "didn't work"? "Didn't work" can mean many things.
I might be able to help you fix your device but I can't fix ignorance.
First I tried to do a force upgrade with a "dload" folder with a update.app file on my sdcard . After booting into this upgrade mode by pressing vol up + vol down + power button my device starts to install the stock firmware, but after it reaches 5% I get the message "Error with installing" and a Link to the same site when you boot into twrp. This always happens no matter which file I use. Next I tried to do a normal upgrade by calling this number "*#*#2846579#*#*" (The dload folder is still on my sdcard). But when I start the software upgrade I get booted into twrp and like I said in my post, always when I try to get into twrp I get stuck on the "Your device is booting screen". This is what I tried and basicly every site on google is saying I should try to do one of these two methods
(Here a guide for example: https://www.getdroidtips.com/full-guide-install-stock-firmware-huawei-smartphone/)
(My file in my last try: https://www.getdroidtips.com/huawei-mate-9-stock-firmware-collections/)
Click to expand...
Click to collapse
Stock upgrades are not going to work if you are rooted and have TWRP.
Stock updates require stock recovery and an unmodified system partition(no root).
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Stock upgrades are not going to work if you are rooted and have TWRP.
Stock updates require stock recovery and an unmodified system partition(no root).
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Yeah I have already seen, but I can't find an other method to return my Huawei Mate 9 to stock and I don't really have an root.
Kyranix said:
Yeah I have already seen, but I can't find an other method to return my Huawei Mate 9 to stock and I don't really have an root.
Click to expand...
Click to collapse
But you have TWRP, that won't work. You need stock recovery, custom recovery can't flash stock updates.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
But you have TWRP, that won't work. You need stock recovery, custom recovery can't flash stock updates.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
And can you please tell me how to do it then. You can also send me a guide
Kyranix said:
And can you please tell me how to do it then. You can also send me a guide
Click to expand...
Click to collapse
I am not sure why you are not doing this in your device forum?
https://forum.xda-developers.com/mate-9
It seems that there would be more assistance specific to your device.
or did I miss something?
Moscow Desire said:
I am not sure why you are not doing this in your device forum?
https://forum.xda-developers.com/mate-9
It seems that there would be more assistance specific to your device.
or did I miss something?
Click to expand...
Click to collapse
Well thats because I already had problems to post this thread because I am new to xda
Moscow Desire said:
I am not sure why you are not doing this in your device forum?
https://forum.xda-developers.com/mate-9
It seems that there would be more assistance specific to your device.
or did I miss something?
Click to expand...
Click to collapse
Well thats because I already had problems to post this thread because I am new to xda But thanks for pointing it out, I will probably try it there again. Maybe there I will have more luck
Kyranix said:
Well thats because I already had problems to post this thread because I am new to xda [emoji14] But thanks for pointing it out, I will probably try it there again. Maybe there I will have more luck
Click to expand...
Click to collapse
Even new members(less than 10 posts) can post in device specific Q&A fora, new members are only blocked from posting in "development" fora and threads.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Are there already a root method or do I need to wait a little more?
DKzVeNgEnS said:
Are there already a root method or do I need to wait a little more?
Click to expand...
Click to collapse
up for this
available twrp 3.2.1 & Root
https://romprovider.com/2018/07/sm-a605fn-root-twrp/
mark332 said:
available twrp 3.2.1 & Root
https://romprovider.com/2018/07/sm-a605fn-root-twrp/
Click to expand...
Click to collapse
that method too simple for 2018++ samsung phones, i don't think that will work/proper method.
Doesnt work at all
an-_-dro said:
that method too simple for 2018++ samsung phones, i don't think that will work/proper method.
Click to expand...
Click to collapse
not only that method dont work but also there is this thread
http s://w ww.cyanogenmods.org/forums/topic/twrp-root-galaxy-a6-plus-twrp-and-root-guide/
about flashing twrp for A6plus both threads provide img or tar files to be flashed on the phone and guess what??? when you try to flash them you get the uspport dev_type .
NOTE the serial number on the post is for an A6 phone not an A6 PLus
so my question is, is there an official twrp image that can be flashed on this model ???
ponto2002 said:
not only that method dont work but also there is this thread
http s://w ww.cyanogenmods.org/forums/topic/twrp-root-galaxy-a6-plus-twrp-and-root-guide/
about flashing twrp for A6plus both threads provide img or tar files to be flashed on the phone and guess what??? when you try to flash them you get the uspport dev_type .
NOTE the serial number on the post is for an A6 phone not an A6 PLus
so my question is, is there an official twrp image that can be flashed on this model ???
Click to expand...
Click to collapse
don't trust other site... for me it's better wait for a bit until here in xda or video from youtube. if only article and providing download link that's too dangerous.
can't wait to root,,and unlock the fully potential of this device. especially the batter...superb battery!!! SOT average always above 7 hours ++ with 2 days charging interval
an-_-dro said:
don't trust other site... for me it's better wait for a bit until here in xda or video from youtube. if only article and providing download link that's too dangerous.
can't wait to root,,and unlock the fully potential of this device. especially the batter...superb battery!!! SOT average always above 7 hours ++ with 2 days charging interval
Click to expand...
Click to collapse
well i took the risk and when i tried to flash TWRP i got the message unsport dev_type, just need anyone with the knowledge to compile twrp for this device
Sad
Hey guys !
Any news for A6+ rooting process ?
Thanks !
I have tried everything on my A605FN... nothing works...
SubGenius said:
I have tried everything on my A605FN... nothing works...
Click to expand...
Click to collapse
Please test the recovery image below. Compiled from latest source.
ODIN
https://androidfilehost.com/?fid=962187416754463924
TWRP
https://androidfilehost.com/?fid=11410963190603852329
Device must be OEM_UNLOCKED first. If this device supports RMM then the RMM patch will need to be applied before booting to Android.
.
ashyx said:
Please test the recovery image below. Compiled from latest source.
ODIN
https://androidfilehost.com/?fid=962187416754463924
TWRP
https://androidfilehost.com/?fid=11410963190603852329
.
Click to expand...
Click to collapse
Super, at least adb works on that build. Will try to export recovery.log and go into it.
Please, can you fix the font size in the next build, its tooooo small
nebkas said:
Super, at least adb works on that build. Will try to export recovery.log and go into it.
Please, can you fix the font size in the next build, its tooooo small
Click to expand...
Click to collapse
Can you post screen shots as well as the log?
ashyx said:
Can you post screen shots as well as the log?
Click to expand...
Click to collapse
here is the log
I had to use a macro lens for the screenshot :laugh:
nebkas said:
I had to use a macro lens for the screenshot :laugh:
Click to expand...
Click to collapse
Odd, log reports no issues with resolution. Correctly detected as 1080x2220.
Never seen this small font before.
Are all pages the same, how do the buttons appear?
I looked into ui.xml. its set there:
-<recovery>
-<details>
<resolution height="1200" width="1920"/>
---------- Post added at 00:21 ---------- Previous post was at 00:10 ----------
Picture upload on xda is broken now. will try it later or do you have something where to put them?
nebkas said:
I looked into ui.xml. its set there:
-<recovery>
-<details>
<resolution height="1200" width="1920"/>
---------- Post added at 00:21 ---------- Previous post was at 00:10 ----------
Picture upload on xda is broken now. will try it later or do you have something where to put them?
Click to expand...
Click to collapse
TWRP scales the resolution depending on what it detects from the framebuffer which is why we no longer need to use resolution flags. There are no longer set themes only portrait or landscape.
It seems the resolution has been correctly detected.
You can upload images below:
https://postimages.org
ashyx said:
TWRP scales the resolution depending on what it detects from the framebuffer which is why we no longer need to use resolution flags. There are no longer set themes only portrait or landscape.
It seems the resolution has been correctly detected.
You can upload images below:
https://postimages.org
Click to expand...
Click to collapse
and what is with the not working mount points? I tried to manually mount them, even edited the fstab like from original recovery, but didn't worked, still "invalid argument"
I never build a twrp by myself. But we could open a thred for it and I will support you do find the bugs etc.
nebkas said:
and what is with the not working mount points? I tried to manually mount them, even edited the fstab like from original recovery, but didn't worked, still "invalid argument"
I never build a twrp by myself. But we could open a thred for it and I will support you do find the bugs etc.
Click to expand...
Click to collapse
The UI is really messed up.
The mount issues are because your data partition is encrypted.
Twrp cannot decrypt Samsung encrypted partitions. You need to FORMAT (not wipe) the data partition to be able to mount it.
However unless the fstab is patched it will re-encrypt at boot.
ashyx said:
The UI is really messed up.
The mount issues are because your data partition is encrypted.
Twrp cannot decrypt Samsung encrypted partitions. You need to FORMAT (not wipe) the data partition to be able to mount it.
However unless the fstab is patched it will re-encrypt at boot.
Click to expand...
Click to collapse
Alright, will make a backup of my data partition and try out more.
How is Huawei handling root? Is it suspected to work or will this be a problem?
I guess the rooting process may be a bit similar to the Mate 20s. It took a while before root became available for Mate and the process relies on a somewhat compilicated procedure involving FunkeyHuawei and buying credits. If you really want to have root then probably better to wait or to buy a phone which is easier to root.
Hi,
Somewhat agree. Root might take time.
What I can confirm is that oem unlock is not greyed out.
P30 Pro dev options https://imgur.com/a/unJy0ZX
So do you think that someone will cook TWRP and magisk?
I already extracted the ram disk and tried patching it with Magisk.
It didn't boot.
Any other bright ideas?
JazonX said:
I already extracted the ram disk and tried patching it with Magisk.
It didn't boot.
Any other bright ideas?
Click to expand...
Click to collapse
Hope that someone will find a solution, maybe on chinese forums. I can't buy a non-rootable phone.
JazonX said:
I already extracted the ram disk and tried patching it with Magisk.
It didn't boot.
Any other bright ideas?
Click to expand...
Click to collapse
Is not ramdisk that you need to patch, try patch stock Recovery, at least works with EMUI 9.
kilroystyx said:
Is not ramdisk that you need to patch, try patch stock Recovery, at least works with EMUI 9.
Click to expand...
Click to collapse
Yeah, It was called Ramdisk_recovery
That's the one, isn't it?
JazonX said:
Yeah, It was called Ramdisk_recovery
That's the one, isn't it?
Click to expand...
Click to collapse
Is "RECOVERY_RAMDIS.img", in the tool is missing the "K". You can rename it to "RECOVERY_RAMDISK.img"
If you need to flash in the fastboot use this command:
fastboot flash recovery_ramdisk recovery_ramdisk.img
My p30 pro arrive today and i thought i can root it with this tutorial
https://myphoneupdate.com/root-huawei-p30-pro-unlock-bootloader-install-twrp-recovery/
And now i read here that its not possible? That is very Bad if this is so :/
Sorry for Bad English
Edit: oh... Yes now i See no Service sells this Codes at the Moment..
kilroystyx said:
Is "RECOVERY_RAMDIS.img", in the tool is missing the "K". You can rename it to "RECOVERY_RAMDISK.img"
If you need to flash in the fastboot use this command:
fastboot flash recovery_ramdisk recovery_ramdisk.img
Click to expand...
Click to collapse
Yeah, I figured it. Output was patched_boot img. It flashed without any issues. But couldn't reboot afterwards. Went into bootloop, and then back to eRecovery. Normal boot is fine. Patched boot didn't work.
JazonX said:
Yeah, I figured it. Output was patched_boot img. It flashed without any issues. But couldn't reboot afterwards. Went into bootloop, and then back to eRecovery. Normal boot is fine. Patched boot didn't work.
Click to expand...
Click to collapse
:crying::crying::crying:
JazonX said:
Yeah, I figured it. Output was patched_boot img. It flashed without any issues. But couldn't reboot afterwards. Went into bootloop, and then back to eRecovery. Normal boot is fine. Patched boot didn't work.
Click to expand...
Click to collapse
Unfortunately this means that Magisk is not ready to patch EMUI9.1
Has anyone tried the process ?
I might be doing it wrong, Please give it a try from your end as well!
JazonX said:
Has anyone tried the process ?
I might be doing it wrong, Please give it a try from your end as well!
Click to expand...
Click to collapse
Can you upload your stock img RECOVERY_RAMDISK?
I'll patch for you and then if the CRC/SHA is different you can try mine.
kilroystyx said:
Can you upload your stock img RECOVERY_RAMDISK?
I'll patch for you and then if the CRC/SHA is different you can try mine.
Click to expand...
Click to collapse
I have uploaded it here.
JazonX said:
I have uploaded it here.
Click to expand...
Click to collapse
Patched by me is different from yours.
Link:
https://mega.nz/#!ZZgHgapa!NO5_2VxavqN7v9RNwTlxjNTmKR40rOyWIW6k18LRJ-w
You can check the MD5, first is one that you patched and second is the one patched by me
Enclosed you can find the Magisk version used by my.
Check mine and let me know if it works.
kilroystyx said:
Patched by me is different from yours.
Link:
https://mega.nz/#!ZZgHgapa!NO5_2VxavqN7v9RNwTlxjNTmKR40rOyWIW6k18LRJ-w
You can check the MD5, first is one that you patched and second is the one patched by me
Enclosed you can find the Magisk version used by my.
Check mine and let me know if it works.
Click to expand...
Click to collapse
How to flash? Don't we need to unlock the bootloader first, if so I have to buy a unlock code right? I'm om 0.124
Puksom said:
How to flash? Don't we need to unlock the bootloader first, if so I have to buy a unlock code right? I'm om 0.124
Click to expand...
Click to collapse
Yes, to flash you need bootloader unlocked.
Don't waste your money yet, let's first JazonX test the recovery_ramdisk.img patched by me.
JazonX, have you tried? I hope it works
First of all i want to make clear that, i am new to this community, so for any inconvenience please forgive me.
I was curious about what will be the safest way to root my Android 11 devices running on MIUI Global 12.5.2 .
i watched a lot of YouTube videos but didn't come up with an answer i am looking for, i got confused a lot some people suggest doing without pc and some with some apps.
I would be glad if someone can explain to me, the best way to root Android device and do's and dont's before and after rooting the device. And how can i prevent my device from:
Getting hard/soft Brick.
Losing Data.
Data encryption.
And the things i should get familiar with before rooting.
Thanks to everyone in advance
akram0010 said:
First of all i want to make clear that, i am new to this community, so for any inconvenience please forgive me.
I was curious about what will be the safest way to root my Android devices running on MIUI Global 12.5.2 .
i watched a lot of YouTube videos but didn't come up with an answer i am looking for, i got confused a lot some people suggest doing without pc and some with some apps.
I would be glad if someone can explain to me, the best way to root Android device and do's and dont's before and after rooting the device. And how can i prevent my device from:
Getting hard/soft Brick.
Losing Data.
Data encryption.
And the things i should get familiar with before rooting.
Thanks to everyone in advance
Click to expand...
Click to collapse
You can not root without losing data, unlocking Xiaomi bootloader wipe all your data. For rooting, take a look Magisk instruction https://topjohnwu.github.io/Magisk/install.html very easy
akram0010 said:
Thanks for letting me know, it means i would have to backup my data first.
Click to expand...
Click to collapse
Make backup of data,apps, unlock bootloader then you can root your phone with magisk. Unlocking bootloader wiping all data.
DungxCt said:
You can not root without losing data, unlocking Xiaomi bootloader wipe all your data. For rooting, take a look Magisk instruction https://topjohnwu.github.io/Magisk/install.html very easy
Click to expand...
Click to collapse
In this page it tells, if you plan to install custom kernels install it after magisk, is it necessary to install custom kernel.
What if i don't install any kernel, will the default kernel be still there?
akram0010 said:
In this page it tells, if you plan to install custom kernels install it after magisk, is it necessary to install custom kernel.
What if i don't install any kernel, will the default kernel be still there?
Click to expand...
Click to collapse
You miss understand it, it doesn't mean you HAVE TO install custom kernel after root. Just mean: "If you WANT to, just do it after intall Magisk"
DungxCt said:
You miss understand it, it doesn't mean you HAVE TO install custom kernel after root. Just mean: "If you WANT to, just do it after intall Magisk"
Click to expand...
Click to collapse
Can i follow this , because i have the same device and also both have Android 11 however the miui is miui global 12.5.1where mine is miui global 12.5.2
akram0010 said:
Can i follow this , because i have the same device and also both have Android 11 however the miui is miui global 12.5.1where mine is miui global 12.5.2
Click to expand...
Click to collapse
Yes, If you want your device to become a brick.
Use https://play.google.com/store/apps/details?id=com.xiaomiui.downloader&hl=en_US&gl=US to download ur using version and extract the boot.img ur own
DungxCt said:
Yes, If you want your device to become a brick.
Use https://play.google.com/store/apps/details?id=com.xiaomiui.downloader&hl=en_US&gl=US to download ur using version and extract the boot.img ur own
Click to expand...
Click to collapse
First of all, i want to thank you for helping me so far.
I downloaded the App as you said and selected my version, now ita shows me three options to download OTA, RECOVERY, FASTBOOT.
which one should i download, and what am i gonna do with them after downloading?
akram0010 said:
First of all, i want to thank you for helping me so far.
I downloaded the App as you said and selected my version, now ita shows me three options to download OTA, RECOVERY, FASTBOOT.
which one should i download, and what am i gonna do with them after downloading?
Click to expand...
Click to collapse
Also it shows the version:
V12.5.4xxxxxxxxxxx
Click to expand...
Click to collapse
However mine is:
V12.5.2xxxxxxxxx
Click to expand...
Click to collapse
akram0010 said:
Also it shows the version:
However mine is:
Click to expand...
Click to collapse
Tap older version and download the recovery. Use https://github.com/ssut/payload-dumper-go to extract boot.img from payload.bin. Look how here https://www.xda-developers.com/how-to-install-magisk/
DungxCt said:
Tap older version and download the recovery. Use https://github.com/ssut/payload-dumper-go to extract boot.img from payload.bin. Look how here https://www.xda-developers.com/how-to-install-magisk/
Click to expand...
Click to collapse
I tapped on the older version, however mine version, i.e (12.5.2.0 RJCINXM ), is not listed.
I checked a couple of websites too, on them only this version is not listed others are like 12.5.3.0 etc
akram0010 said:
I tapped on the older version, however mine version, i.e (12.5.2.0 RJCINXM ), is not listed.
I checked a couple of websites too, on them only this version is not listed others are like 12.5.3.0 etc
Click to expand...
Click to collapse
I want to know, would it matter if i go for 12.5.4.0 version? cause the device model is same in both versions.
akram0010 said:
I want to know, would it matter if i go for 12.5.4.0 version? cause the device model is same in both versions.
Click to expand...
Click to collapse
Yea no prob, just the get boot.img from it
DungxCt said:
Yea no prob, just the get boot.img from it
Click to expand...
Click to collapse
Let me get it straight, you mean the ROM version doesn't matter, however the ROM should be same as that of the device model.
akram0010 said:
Let me get it straight, you mean the ROM version doesn't matter, however the ROM should be same as that of the device model.
Click to expand...
Click to collapse
Yea, just get the boot.img from the ROM you are using then all good.
DungxCt said:
Yea, just get the boot.img from the ROM you are using then all good.
Click to expand...
Click to collapse
Sure, from where would i get this boot.img, i mean from recovery ROM or FASTBOOT ROM?
akram0010 said:
Sure, from where would i get this boot.img, i mean from recovery ROM or FASTBOOT ROM?
Click to expand...
Click to collapse
Recovery ROM, unzip and extract from payload.bin.
Use https://github.com/ssut/payload-dumper-go to extract boot.img from payload.bin. Look how here https://www.xda-developers.com/how-to-install-magisk/.
I said it already, at #10
DungxCt said:
Recovery ROM, unzip and extract from payload.bin.
Use https://github.com/ssut/payload-dumper-go to extract boot.img from payload.bin. Look how here https://www.xda-developers.com/how-to-install-magisk/.
I said it already, at #10
Click to expand...
Click to collapse
Yes you said, problem is i am using Linux Ubuntu, i have adb and fastboot setup, however this payload dumper would it work on Linux
akram0010 said:
Yes you said, problem is i am using Linux Ubuntu, i have adb and fastboot setup, however this payload dumper would it work on Linux
Click to expand...
Click to collapse
can you even check and see?
akram0010 said:
Yes you said, problem is i am using Linux Ubuntu, i have adb and fastboot setup, however this payload dumper would it work on Linux
Click to expand...
Click to collapse
Can i do it manually? i mean extracting the boot.img from the recovery ROM manually.