Related
I've always been a bit startled by how the bootloader bootloader is unlocked on my nexus 4. After pushing the unlock command to my device and choosing "yes", the bootloader is unlocked right away. The data isn't wiped before I reboot into the system, while on the nexus 7 the bootloader is not unlocked before after the wipe.
Yesterday i re-locked, rebooted and unlocked my device again as an experiment. I then proceeded to boot a custom recovery without rebooting into the system. I suceded, and was able to boot into TWRP without the bootloader wiping my data. I could then proceed to adb pull/push watever i wished from the data partition or any other partition without the data having been wiped. What? I thought my data was secure after re-locking my bootloader, but it appears it isn't.
If this applies to all nexus 4 devices, I was also able to reboot into the system after wiping cace from TWRP. This means you can oem unlock and root without without my data being wiped simply by booting a custom recovery right after unlocking.
If this applies to all nexus 4 devices, our data is not safe. This means that even normal users with locked bootloaders can have their data stolen easy as pie. We need more confirmations on this issue to confirm it. If you are willing to try, just follow the instructions below. Please report if it works or if it doesn't. WARNING! Do this at your own risk! I'm not responsible if your data is wiped, etc. Please perform a full nandroid or adb backup and copy it to a safe place before performing the following seps:
1. If you're unlocked, re-lock your bootloader and reboot into fastboot:
Code:
fastboot oem lock
fastboot reboot-bootloader
2. Unlock your bootloader:
Code:
fastboot oem unlock
3. There's no need to reboot into bootloader after performing the previous step. It makes no difference. Just do not reboot into the system.
4. Flash or boot a custom recovery:
Code:
fastboot flash recovery custom_recovery.img
OR
Code:
fastboot boot custom_recovery.img
5. Now you're in custom recovery if all goes as expected. Root by flashing SuperSU/whatever or pull data with adb or do some serious damage! :good:
6. If you want to reboot back into your system without loosing data, you'll have to wipe cache in custom recovery. This prevents the bootloader from rebooting back into the stock recovery (if you didn't overwrite it) and wipe your phone. If you flashed a custom recovery and you're stuck in a bootloop or something, this applies to you too.
And again: Please report back if it worked or if it didn't! Good luck! :^)
Edit: This wasn't all my idea. Found out about the last cache wipe step here.
fiskenigaten said:
I've always been a bit startled by how the bootloader bootloader is unlocked on my nexus 4. After pushing the unlock command to my device and choosing "yes", the bootloader is unlocked right away. The data isn't wiped before I reboot into the system, while on the nexus 7 the bootloader is not unlocked before after the wipe.
Yesterday i re-locked, rebooted and unlocked my device again as an experiment. I then proceeded to boot a custom recovery without rebooting into the system. I suceded, and was able to boot into TWRP without the bootloader wiping my data. I could then proceed to adb pull/push watever i wished from the data partition or any other partition without the data having been wiped. What? I thought my data was secure after re-locking my bootloader, but no!
I was also able to reboot into the system after wiping cace from TWRP. This means I can oem unlock and root without without my data being wiped simply by booting a custom recovery right after unlocking.
I want to find out if this applies to all other makos on all bootloaders. If you are willing to try, this is what I did. Please report if it works or if it doesn't. WARNING! Do this at your own risk! I'm not responsible if your data is wiped. Please perform a full nandroid backup and copy it to a safe place before performing the following seps:
1. If you're unlocked, re-lock your bootloader and reboot into fastboot:
Code:
fastboot oem lock
fastboot reboot-bootloader
2. Unlock your bootloader:
Code:
fastboot oem unlock
3. There's no need to reboot into bootloader after performing the previous step. It makes no difference. Just do not reboot into the system.
4. Flash or boot a custom recovery:
Code:
fastboot flash recovery custom_recovery.img
OR
Code:
fastboot boot custom_recovery.img
5. Now you're in custom recovery if all goes as expected. Root by flashing SuperSU/whatever or pull data with adb or do some serious damage! :good:
6. If you want to reboot back into your system without loosing data, you'll have to wipe cache in custom recovery. For some reason this keeps the stock recovery from wiping the phone. If you flashed a custom recovery and you're stuck in a bootloop or something, this applies to you too.
And again: Please report back if it worked or if it didn't! Good luck! :^)
Edit: This wasn't all my idea. Found out about the last cache wipe step here.
Click to expand...
Click to collapse
The upside is, the person who steals or finds your phone is most likely not a developer, an android nerd, or has ever heard of XDA to gain this information.
Semantics said:
The upside is, the person who steals or finds your phone is most likely not a developer, an android nerd, or has ever heard of XDA to gain this information.
Click to expand...
Click to collapse
/deleted I have no idea what I'm talking
Not up for experimenting, but it reminded me of my experience on the N4.
-initial BL unlock via the standard method = data wiped,
-upon relocking, and then unlocking the BL again = no data wipe (same method as above)
Can't recall if the behaviour was the same on my GN.
CMNein said:
Not up for experimenting, but it reminded me of my experience on the N4.
-initial BL unlock via the standard method = data wiped,
-upon relocking, and then unlocking the BL again = no data wipe (same method as above)
Can't recall if the behaviour was the same on my GN.
Click to expand...
Click to collapse
My data is allways wiped after bootloader unlock, but it is only wiped upon reboot. It was like that the first time as well.
I can almost (95%) confirm this, because the first time I unlock my Nexus 4, I fastboot flash cwm directly, and boot into recovery, to flash PA and wipe cache and data. Everything in my sdcard was intact and I was also confused like you did.
Maybe if I ever wanted to full wipe again I will give it a try...
ksilver89 said:
I can almost (95%) confirm this, because the first time I unlock my Nexus 4, I fastboot flash cwm directly, and boot into recovery, to flash PA and wipe cache and data. Everything in my sdcard was intact and I was also confused like you did.
Maybe if I ever wanted to full wipe again I will give it a try...
Click to expand...
Click to collapse
Excactly! This is really careless by Google. It means NO nexus 4 without encryption is safe! I want my data to be safe!
I don't get it. I thought even Samsung's phones you can do that? Just just go flash cf root then yeah done? Are they even trying to protect the data in your internal memory data from getting stolen?
fiskenigaten said:
My data is allways wiped after bootloader unlock, but it is only wiped upon reboot. It was like that the first time as well.
Click to expand...
Click to collapse
Sorry, I should have clarified I was referring to the virtual sdcard side of it.
Yup this is the exact reason I opened a thread about compatibility issues with encryption and CWM recovery. We have to encrypt our phones if we want to secure our data. What are the options once we go the 3rd party recovery route is another question.
http://forum.xda-developers.com/showthread.php?p=41257911
Sent from my Nexus 4 using Tapatalk 2
Excactly! This is really careless by Google. It means NO nexus 4 without encryption is safe! I want my data to be safe!
Click to expand...
Click to collapse
Guess it's time to encrypt your device then...
Seriously, bugs and exploits are going to happen. This is software written by humans, after all.
If you are serious about data security on your device, you would have already encrypted by now.
Can confirm easily. I relocked my boot loader with my phone at its current state. (CMRC1 + Bricked Kernel). Then proceeded to unlock, rebooted boot loader, booted into recovery, wipe cache, data intact
Sent from my Nexus 4 using xda premium
Well if someone steals your phone they most likely don't give a **** about your data (unless there's bank info on it) they probably just wanna resell it for an easy 3-400$
Sent from my Nexus 4 @1.72 GHz on Stock 4.2.2
To be honest if you want your bank info safe never put it on a device that is easily lost or stolen or transmits the info over the air.
Wayne Tech Nexus
Guys, honest question. If someone were to grab your data but you encrypted it via the settings menu, does that mean they can still decipher your contents? For example, the TSA is known to get your electronic items and copy the data for their "Security protocol." Would this allow them to copy the data but not decipher it?
Sent from my Nexus 4
nexicon said:
Guys, honest question. If someone were to grab your data but you encrypted it via the settings menu, does that mean they can still decipher your contents? For example, the TSA is known to get your electronic items and copy the data for their "Security protocol." Would this allow them to copy the data but not decipher it?
Sent from my Nexus 4
Click to expand...
Click to collapse
If the TSA got ahold of your device they would be able to decrypt it easily enough. No amount of encryption would prevent that.
zelendel said:
If the TSA got ahold of your device they would be able to decrypt it easily enough. No amount of encryption would prevent that.
Click to expand...
Click to collapse
Nothing in this country is safe and private anymore. Sigh..
Sent from my Nexus 4
nexicon said:
Nothing in this country is safe and private anymore. Sigh..
Sent from my Nexus 4
Click to expand...
Click to collapse
Not really. The only way to beat Gov hackers is to be a better hacker.
zelendel said:
Not really. The only way to beat Gov hackers is to be a better hacker.
Click to expand...
Click to collapse
Easy for you to say
Sent from my Nexus 4
nexicon said:
Easy for you to say
Sent from my Nexus 4
Click to expand...
Click to collapse
No not really man. Not sure what Country your in but it is most likely not very different here.
i used the all in one kit and had no issues unlocking the bootloader or flashing a recovery....how do i boot into recovery also??? anyways i ran a root check app and being told NO ROOT ACCESS...and i have used this app for all my rooted devices...and real quick, where can i find some nice roms and the steps to flashing....sorry im a bit NEW to the One but A quick learner so please bare with me...any help is appreciated!!
blueizee said:
i used the all in one kit and had no issues unlocking the bootloader or flashing a recovery....how do i boot into recovery also??? anyways i ran a root check app and being told NO ROOT ACCESS...and i have used this app for all my rooted devices...and real quick, where can i find some nice roms and the steps to flashing....sorry im a bit NEW to the One but A quick learner so please bare with me...any help is appreciated!!
Click to expand...
Click to collapse
You can access recovery by the following commands:
fastboot reboot recovery (when booted into the bootloader)
adb reboot recovery (when booted into the phone)
booting the device up while holding down the PWR + VOL DOWN will boot into bootloader, then choose recovery from the menu.
Unlocking your bootloader doesn't not automatically give you root in the ROM. it gives you the ability to flash a custom recovery(which you've done) and various other unsigned(aka non-HTC) files. To fully root your phone, there is another step you need to take in the All-In-One. The options on the lower right hand section called "Perm Root."
Alternatively, at this point, you could just install either A) pre-rooted stock ROM, or B) a fully custom ROM like TrickDroid or ARHD in the Android Development section of this forum. PLEASE NOTE: These ROMs are for the international/T-Mobile/AT&T model. If you have the Sprint model, DO NOT FLASH ANYTHING IN THIS SECTION and go to the Sprint-specific HTC One forums.
Hi Guys
How to install Cyanogenmod on LG 4x HD?
and can we make it without CWM , as I installed that and briked the phone.
Thanks
sheriffmarcos said:
Hi Guys
How to install Cyanogenmod on LG 4x HD?
and can we make it without CWM , as I installed that and briked the phone.
Thanks
Click to expand...
Click to collapse
Okay, you need to first make sure that your bootloader is unlocked, to check this enable USB debugging, go to your adb directory and open a CMD and run adb reboot oem-unlock
If it returns with 'good to go' or something similar then it's unlocked, if not, follow unlocking procedures.
Second you need to download CM, and CWM.img place the cwm image in your fastboot directory and run fastboot flash recovery 'name of file'.img. once that is done do a bat pull and when you put it back in turn on and hold the volume up key. This will boot you to recovery.
Make a back up.
then you need to wipe data/factory reset, wipe cache partition, go to advanced>wipe dalvik cache. Go to mounts and wipe /system
Go to install zip on the main page and locate either on the internal storage or the external storage the zip of CM and install it.
Reboot and wait up to 4-5Minutes for first boot, once booted go to your browser and download the Gapps zip and flash in the same way as you did the Rom without wiping anything. If you would like to use a custom kernel download the correct kernel for your android version and flash in the same way as gapps.
If you have any problems just search for a flashing tutorial or post your problem back in this thread rather then opening a new one.
#Mr.G said:
Okay, you need to first make sure that your bootloader is unlocked, to check this enable USB debugging, go to your adb directory and open a CMD and run adb reboot oem-unlock
If it returns with 'good to go' or something similar then it's unlocked, if not, follow unlocking procedures.
Second you need to download CM, and CWM.img place the cwm image in your fastboot directory and run fastboot flash recovery 'name of file'.img. once that is done do a bat pull and when you put it back in turn on and hold the volume up key. This will boot you to recovery.
Make a back up.
then you need to wipe data/factory reset, wipe cache partition, go to advanced>wipe dalvik cache. Go to mounts and wipe /system
Go to install zip on the main page and locate either on the internal storage or the external storage the zip of CM and install it.
Reboot and wait up to 4-5Minutes for first boot, once booted go to your browser and download the Gapps zip and flash in the same way as you did the Rom without wiping anything. If you would like to use a custom kernel download the correct kernel for your android version and flash in the same way as gapps.
If you have any problems just search for a flashing tutorial or post your problem back in this thread rather then opening a new one.
Click to expand...
Click to collapse
it doesnt return good to go and this isnt a check if the bootloader is unlocked. please use search and read , dont give false instructions cause later he will post "help how do i return back to stock ?"
the answer is yes he can install teamwin recovery instead and install the cyanogenmod rom. use search and read dont ask before u try find the answer. There are tons of instruction of how to install a rom and tons of videos.
can we have easier step by step
hi Guys
thanks but can we have can we have easier step by step tutorial / videos
sheriffmarcos said:
hi Guys
thanks but can we have can we have easier step by step tutorial / videos
Click to expand...
Click to collapse
If you aren't capable of following the current instructions then you should not be attempting to mess around with your phone.
None of it is difficult and all the information is out there - make it your responsibility to read, understand and know what to do if it goes wrong.
sheriffmarcos said:
hi Guys
thanks but can we have can we have easier step by step tutorial / videos
Click to expand...
Click to collapse
people is your weapon. you know how many videos are out there in youtube ? even if its an old one, it will definately help you understand the whole procedure. really it cant be any easier. u need to root the phone so you can install anything. u need to unlock the bootloader so u can change the boot image , you need to format so you have a clean phone and of course you need an os to open up again the phone. like he said it cant be any easier. take for example me. 4 months ago , i start reading and watching videos. it took me 8 days to learn the basic and understand what i have to do and took me one day to do it. 9 days overall. now ? now i can totally mess it up and bring it back to life in 5 minutes... study it a little. you cant mess with linux based os without understanding how it works.
<<EDIT>>
For example ,
Here says u have to do that to unlock.
He says for windows u need the drivers. You can search and find them. For example one place to download them is here.
How to install the drivers has nothing to do with this forum , you must know how to force the drivers in windows , but if u search u will find that too.
To unlock now is only one command in terminal. wait a few seconds and u are done.
The procedure is only one command. the hard part is not something that has to do with the android or the forum. its windows fault if its so lame that cant even recognize properly a simple usb device.
Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to Decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:
ianseer said:
Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to Decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:
Click to expand...
Click to collapse
Flash official recovery from twrp website. If I remember right it will work. But change language to English
If you haven't already find solution you must do factory reset through twrp option to unlock it ,of course this action will wipe all your data.
strakell said:
If you haven't already find solution you must do factory reset through twrp option to unlock it ,of course this action will wipe all your data.
Click to expand...
Click to collapse
Data partition he needs to wipe.
ianseer said:
Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:
Click to expand...
Click to collapse
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!
ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened you appetite!
have fun!
Click to expand...
Click to collapse
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone
ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened you appetite!
have fun!
Click to expand...
Click to collapse
You answering all of my question very nice and clear... Yes i will having fun next week, i hope... (Still in other city now, i need my phone)... But, when the time comes, i will try it and post the update here... big thanks, Appriciate it... Yes i'm hungry now
methuselah said:
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone
Click to expand...
Click to collapse
If only i can help you guys out cooking the rom... I'm only animator and designer... Not chef programmer or coder
methuselah said:
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone
Click to expand...
Click to collapse
YES, at this moment sound is a problem in GSI ROMs. In call you have sound but not in media.
I am still looking for solutions.
ABM30 said:
YES, at this moment sound is a problem in GSI ROMs. In call you have sound but not in media.
I am still looking for solutions.
Click to expand...
Click to collapse
There are logs on phh thread about sound and other issues on gsi. Take a look if you have any knowledge. You don't need to take logs again I guess. But new GSI don't even boot last time this month when I checked. Maybe I was wrong.
It's just my point of view. You should try to bring up lineageOs with Omni sources coz lot of developers are there to help you if you have knowledge. The device tress are there from Omni. Well 8.1 is still there as lineageOs is still updating and giving security fixes. And most of commits are there for ok our phones in Omni GitHub.
ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!
Click to expand...
Click to collapse
Hello, me again...
I'm trying to do the method that you've explained...
there's a new problem... right now, already try to connect my phone to USB on pc, it always says "USB supplying power on attached device" even for fastboot mode it doesn't work the computer still not recognize anything.. already tried different computer, already tried different cables too... no luck...
Now, I can go to emergency recovery with stock nicely but cannot go to the usual recovery cuz i already installed twrp but the phone itself is encrypted device so nothing to do there, I'm thinking about wiping userdata from emergency recovery,... is it okay to do this? cuz maybe I'm thinking after I wiping the userdata and everything I can get my USB connection again (cuz before i've had similar issue but after install new rom it's working nicely almost with every cable),... what do u guys think? thanks in advance
ianseer said:
Hello, me again...
I'm trying to do the method that you've explained...
there's a new problem... right now, already try to connect my phone to USB on pc, it always says "USB supplying power on attached device" even for fastboot mode it doesn't work the computer still not recognize anything.. already tried different computer, already tried different cables too... no luck...
Now, I can go to emergency recovery with stock nicely but cannot go to the usual recovery cuz i already installed twrp but the phone itself is encrypted device so nothing to do there, I'm thinking about wiping userdata from emergency recovery,... is it okay to do this? cuz maybe I'm thinking after I wiping the userdata and everything I can get my USB connection again (cuz before i've had similar issue but after install new rom it's working nicely almost with every cable),... what do u guys think? thanks in advance
Click to expand...
Click to collapse
Well, if you are encrypted you will need to uncrypt your phone.
!!!!!!!But you will lose everithing saved in internal memory!!!!!!!!
Just follow steps 1 to 8 from my previous guide. Then you can reinstall the ROM. If you will install International ROM you will get encrypted again if you don't run Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip right after installing ROM in TWRP!!!!!!!
Wiping everything with original recovery is the best way to clear your phone!!! sometimes is mandatory this, even with advanced wipe in TWRP you wont achieve what you can with original recovery wipe!
Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting
ianseer said:
Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting
Click to expand...
Click to collapse
Why are flashing without any output. Flash phh treble and help in sorting out bugs.
methuselah said:
Why are flashing without any output. Flash phh treble and help in sorting out bugs.
Click to expand...
Click to collapse
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?
ianseer said:
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?
Click to expand...
Click to collapse
well it doesn't work. It's a part of kernel I guess. There are no sounds from loudspeaker. and there are huge issues with pie in phh treble. He needs logs for that. You can't even login into the google account. There are logs with on treble Phh thread. August images are there. Start taking logs after reading the thread. You will be happy to help him.
ianseer said:
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?
Click to expand...
Click to collapse
Did you posted any log?
ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: [url]http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file[/URL]
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : [url]http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file[/URL]
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : [url]http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file[/URL]
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: [url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688[/URL]
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
[url]https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list[/URL] ,
or here:
[url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development[/URL]
About treble experimentation here: [url]https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29[/URL]
For example I like the DESCENDANT 3.1.1 : [url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578[/URL] but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!
Click to expand...
Click to collapse
Hello sir, I followed each and every step, but device ended up in bootloop. Mostly a soft brick. Every time I power on the device, the logo comes and phone turns off.
I even tried to patch the fstab in /vendor/etc. Same results.
By the way, I could not get the V114 stock global rom which you have mentioned but was able to get V109 stock global rom. If you have the link of the stock rom you mentioned, please provide a link for it. I will just revert back to stock and use it that way. Seems like the device doesn't wants to have an unlocked bootloader and a uncrypted data state ?
ianseer said:
Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting
Click to expand...
Click to collapse
I'm facing issues with this. I followed every step as mentioned by ABM30. But the device in now on bootloop. Infact, I do have the twrp as recovery but device state is locked and the system isnt booting up. Help please
Zenith9082 said:
I'm facing issues with this. I followed every step as mentioned by ABM30. But the device in now on bootloop. Infact, I do have the twrp as recovery but device state is locked and the system isnt booting up. Help please
Click to expand...
Click to collapse
you mean twrp mentioned that your device is locked?
I'm thinking of getting a 30 Ultra the next week, as I'm very disappointed with my OnePlus 10 Pro and the way OnePlus is heading.
I've been an OnePlus user since the 6 and never had a Motorola before, but the 30 Ultra really fascinates me.
Before I buy it I only wanted to ask how the modding community for motorola is.
Is Magisk easily installable with Motorola devices? Anything I should keep in mind with unlocking the bootloader / rooting of a motorola?
Thank's in advance
I didn't have any problems rooting my edge 30 ultra. I had to wait about 2-3 days for the OEM unlocking option to be activated in the developer options, but other than that it was smooth sailing.
Unlock bootloader, obtain stock boot image by for example using the Lenovo Rescue and Smart Assistant, patch the boot image in the magisk app, and then flash it.
You should keep in mind that it's extremely dangerous if not impossible to relock the bootloader again. In theory you have to flash the stock firmware and thoroughly delete all data and custom settings but a lot of people end up with bricked devices.
Killuminati91 said:
You should keep in mind that it's extremely dangerous if not impossible to relock the bootloader again. In theory you have to flash the stock firmware and thoroughly delete all data and custom settings but a lot of people end up with bricked devices.
Click to expand...
Click to collapse
Yes, it's true.
But i big problem in poland, because customer write to unlock bootlader code = warranty is out.
I this method broken my Moto G82
Killuminati91 said:
You should keep in mind that it's extremely dangerous if not impossible to relock the bootloader again. In theory you have to flash the stock firmware and thoroughly delete all data and custom settings but a lot of people end up with bricked devices.
Click to expand...
Click to collapse
Ok so once I root my Motorola, I can't go back to unrooted, right? Surely not ideal but I rarely unroot my devices once I rooted. But thanks for mentioning!
I'm guessing custom rom/kernel support for this device isn't really a thing right?
No, you can unroot at any time if you uninstall magisk and flash the stock boot.img. But you can't / shouldn't relock the bootloader. I think times are over when a lot of people developed kernels / Roms / TWRP for specific phones. We need more people to take matters into their own hands, the market is flooded with too many different models.
@Killuminati91 any news on twrp for this phone yet?
_Hinnie_ said:
I didn't have any problems rooting my edge 30 ultra. I had to wait about 2-3 days for the OEM unlocking option to be activated in the developer options, but other than that it was smooth sailing.
Unlock bootloader, obtain stock boot image by for example using the Lenovo Rescue and Smart Assistant, patch the boot image in the magisk app, and then flash it.
Click to expand...
Click to collapse
I'd be very thankful if you could share a guide for this
memocatcher said:
Ok so once I root my Motorola, I can't go back to unrooted, right? Surely not ideal but I rarely unroot my devices once I rooted. But thanks for mentioning!
I'm guessing custom rom/kernel support for this device isn't really a thing right?
Click to expand...
Click to collapse
Custom roms / kernels isn't a thing at the moment. It is confirmed however that Motorola will soon release the kernel source code of the Edge 30 Ultra, which can help with custom rom and kernel development (https://github.com/MotorolaMobilityLLC/kernel-msm/issues/445).
memocatcher said:
I'd be very thankful if you could share a guide for this
Click to expand...
Click to collapse
1. Go to Settings -> Developer Options -> Enable OEM Unlocking
2. Reboot the phone to the bootloader, for example using adb reboot bootloader
3. Follow the steps from here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
To root your phone:
1. Install the Magisk app from here: https://github.com/topjohnwu/Magisk/releases
2. Download the boot image from the official firmware, make sure the firmware corresponds with your device (or grab your own using the Lenovo Rescue and Assist tool) https://forum.xda-developers.com/t/...cn-to-edge-30-ultra-eu.4491699/#post-87424851
3. In Magisk: Home -> Install -> Select and Patch a File ->Select the boot.img -> Click LET'S GO
4. Copy the patched boot image from /storage/emulated/0/Downloaded/magisk_patched-xxxx.img to your computer
5. Boot the phone to the bootloader
6. Flash the patched boot image with fastboot flash boot magisk_patched-xxxx.img, or alternatively, if you want to be sure that the boot image boots before flashing it, use fastboot boot magisk_patched-xxxx.img and if it works fine, repeat from step 5.
7. Reboot
_Hinnie_ said:
Custom roms / kernels isn't a thing at the moment. It is confirmed however that Motorola will soon release the kernel source code of the Edge 30 Ultra, which can help with custom rom and kernel development (https://github.com/MotorolaMobilityLLC/kernel-msm/issues/445).
1. Go to Settings -> Developer Options -> Enable OEM Unlocking
2. Reboot the phone to the bootloader, for example using adb reboot bootloader
3. Follow the steps from here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
To root your phone:
1. Install the Magisk app from here: https://github.com/topjohnwu/Magisk/releases
2. Download the boot image from the official firmware, make sure the firmware corresponds with your device (or grab your own using the Lenovo Rescue and Assist tool) https://forum.xda-developers.com/t/...cn-to-edge-30-ultra-eu.4491699/#post-87424851
3. In Magisk: Home -> Install -> Select and Patch a File ->Select the boot.img -> Click LET'S GO
4. Copy the patched boot image from /storage/emulated/0/Downloaded/magisk_patched-xxxx.img to your computer
5. Boot the phone to the bootloader
6. Flash the patched boot image with fastboot flash boot magisk_patched-xxxx.img, or alternatively, if you want to be sure that the boot image boots before flashing it, use fastboot boot magisk_patched-xxxx.img and if it works fine, repeat from step 5.
7. Reboot
Click to expand...
Click to collapse
Thanks a lot!!
TF1920 said:
@Killuminati91 any news on twrp for this phone yet?
Click to expand...
Click to collapse
No success yet and I currently don't have the time to try, sadly. Device tree can be generated with helpers but the whole Linux compiling part is still gibberish to me.
TF1920 said:
@Killuminati91 any news on twrp for this phone yet?
Click to expand...
Click to collapse
I did a tentative build, here are the results: img / zip
This was built with OrangeFox, using my device tree. Feel free to contribute to the repo, I can rebuilt if it doesn't work out of the box.
A disclaimer: I am a noob, and I don't have the device yet to test it, it is quite unlikely that this recovery works on the first attempt.
The prebuilt kernel I am especially unsure about.
arellewen said:
I did a tentative build, here are the results: img / zip
This was built with OrangeFox, using my device tree. Feel free to contribute to the repo, I can rebuilt if it doesn't work out of the box.
A disclaimer: I am a noob, and I don't have the device yet to test it, it is quite unlikely that this recovery works on the first attempt.
The prebuilt kernel I am especially unsure about.
Click to expand...
Click to collapse
I also tried myself to setup a device tree, but haven't been able to extract the prebuilt kernel. That's also why I asked for the kernel source on their github that will hopefully soon be published.
I'll try in a bit and edit this post to see if the recovery boots.
EDIT: Nope, it doesn't boot. After the usual motorola animation the screen goes black, and afterwards boots into system.
logandavid said:
sorry for an off-topic question: What did you hate about Oneplus 10 Pro in particular?
Click to expand...
Click to collapse
I just don't like the way OnePlus is heading, like many users with the 10 Pro. It feels like using an Oppo device honestly and they made it impossible to unbrick your device by encrypting the popular MSM Tool.
After 5 years with OnePlus it's time for me to try something different
_Hinnie_ said:
I also tried myself to setup a device tree, but haven't been able to extract the prebuilt kernel. That's also why I asked for the kernel source on their github that will hopefully soon be published.
I'll try in a bit and edit this post to see if the recovery boots.
EDIT: Nope, it doesn't boot. After the usual motorola animation the screen goes black, and afterwards boots into system.
Click to expand...
Click to collapse
Yes it didn't work for me either
Nope !! , stay where you are, I had One Plus 9 Pro before, the Edge 30 Pro is much better in all aspects, One plus = Oppo, very bad phone.
A few questions;
Do you need to have a sim card installed in the phone during the 7 day wait period until the oem unlock button is available? Can I just connect the phone to wifi and let it sit for a week?,
Do you need some sort of unlock code from Motorola? I read the unlock directions, but to go any further it's asking for an email address and the need to register and account.,
Also what is the main difference between the pro and the ultra? Is it only the 200MP camera?
_Hinnie_ said:
Custom roms / kernels isn't a thing at the moment. It is confirmed however that Motorola will soon release the kernel source code of the Edge 30 Ultra, which can help with custom rom and kernel development (https://github.com/MotorolaMobilityLLC/kernel-msm/issues/445).
1. Go to Settings -> Developer Options -> Enable OEM Unlocking
2. Reboot the phone to the bootloader, for example using adb reboot bootloader
3. Follow the steps from here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
To root your phone:
1. Install the Magisk app from here: https://github.com/topjohnwu/Magisk/releases
2. Download the boot image from the official firmware, make sure the firmware corresponds with your device (or grab your own using the Lenovo Rescue and Assist tool) https://forum.xda-developers.com/t/...cn-to-edge-30-ultra-eu.4491699/#post-87424851
3. In Magisk: Home -> Install -> Select and Patch a File ->Select the boot.img -> Click LET'S GO
4. Copy the patched boot image from /storage/emulated/0/Downloaded/magisk_patched-xxxx.img to your computer
5. Boot the phone to the bootloader
6. Flash the patched boot image with fastboot flash boot magisk_patched-xxxx.img, or alternatively, if you want to be sure that the boot image boots before flashing it, use fastboot boot magisk_patched-xxxx.img and if it works fine, repeat from step 5.
7. Reboot
Click to expand...
Click to collapse
It works for me, thanks~
And is there any way to remount /system or /vendor directory with r/w permission?
solsolhh said:
It works for me, thanks~
And is there any way to remount /system or /vendor directory with r/w permission?
Click to expand...
Click to collapse
This but for me dosn't work if write something there is 0 bytes, if you make it work let us know
Tools:
- Universal Mount System RW (Guide)
-> Fix for Android 12
arellewen said:
I did a tentative build, here are the results: img / zip
This was built with OrangeFox, using my device tree. Feel free to contribute to the repo, I can rebuilt if it doesn't work out of the box.
A disclaimer: I am a noob, and I don't have the device yet to test it, it is quite unlikely that this recovery works on the first attempt.
The prebuilt kernel I am especially unsure about.
Click to expand...
Click to collapse
Kernel Sources now available, if you got the time:
Release MMI-S3SQ32.16-16-28 ยท MotorolaMobilityLLC/kernel-msm
eqs-g push for android 12
github.com