If any questions or need some open discussion regarding the rom feel free to ask.
Q: Is this ROM really S-OFF only? No option for S-On phones?
Click to expand...
Click to collapse
If flashing the aroma build, say no to reboot in aroma. If using twrp and reboot to bootloader manually. The installer forces s on ph98img creation.
You also have the option of using flashify to flash the boot.IMG prior and then reboot to recovery to finish flash. The installer will detect you as s off.
Is this ROM really S-OFF only? No option for S-On phones?
If not I guess I'll go learn how to S-OFF my phone.
Also TWRP is not a supported recovery? The only recovery that works is Philz?
Most recoveries should work fine. S-on flashing process is to extract the boot.IMG from the ROM.zip, flash the ROM.zip, reboot to fastboot, plug into computer, then "fastboot flash boot.img"
signupstuffid said:
Is this ROM really S-OFF only? No option for S-On phones?
If not I guess I'll go learn how to S-OFF my phone.
Also TWRP is not a supported recovery? The only recovery that works is Philz?
Click to expand...
Click to collapse
If using twrp, say no to reboot in aroma and reboot to bootloader. The installer forces s on ph98img creation.
And no, I've done quite a bit of updates and this works with all the custom recoveries available. You also have the option of using flashify to flash the boot.IMG prior and then reboot to recovery to finish flash. The installer will detect you as s off.
Snuzzo said:
If using twrp, say no to reboot in aroma and reboot to bootloader. The installer forces s on ph98img creation.
And no, I've done quite a bit of updates and this works with all the custom recoveries available. You also have the option of using flashify to flash the boot.IMG prior and then reboot to recovery to finish flash. The installer will detect you as s off.
Click to expand...
Click to collapse
Cool, Thanks for the tips.
Flashify is usually what I use, unless I forget then I just fastboot flash the boot.img.
One last question, does this ROM have the camcorder bug where you can only take about 3 videos before it requires a reboot to take more?
signupstuffid said:
Cool, Thanks for the tips.
Flashify is usually what I use, unless I forget then I just fastboot flash the boot.img.
One last question, does this ROM have the camcorder bug where you can only take about 3 videos before it requires a reboot to take more?
Click to expand...
Click to collapse
Yes. Its a device wide bug. It either records 3, 6, or none at all. Please if none, let me know, I only test for boot since this is no longer my daily device.
Yw on the few tips.
i made a mistake ....help
i think that i made a mistake. i installed from recovery => install from sc card a zip, directly. for the first zip: Plain-Andy-4.4.4-20141001-vigor-EXPERIMENTAL ...... after gapps-ds-ERE36B-signed
result; no gsm service (no signal)
second zip: Release-v14.2-vigor ................ the phone dont start to android systeme after booting => many msg of errors
if someone can save me from this probleme.....please
thankkkks
I'll have to get you some good gapps for 14.2
CamCorder and Camera no works
Hi ,
I have installed yesterday Plain-Andy, that's it's great job, so smooth and so fast
I like it.
The only problem is camera and camcorder doesn't work
how can I fix this
Thanks for answer
NilkNarf80 said:
Hi ,
I have installed yesterday Plain-Andy, that's it's great job, so smooth and so fast
I like it.
The only problem is camera and camcorder doesn't work
how can I fix this
Thanks for answer
Click to expand...
Click to collapse
The ROM will need rebuilt but unfortunately I no longer have the ROM source available locally.
Related
Key Features:
Ability to save custom recovery settings
Default partitions to back up
Default zip folder location
Default color theme (lots to choose from) (Thanks to ffolkes!)
Default Time Zone (for more accurate time stamps)
Zip Signature Verification
Zip md5 Verification (looks for file with zipname.zip.md5)
Ability to flash multiple zips in one go
Ability to select which individual partitions to backup, and restore.
Ability to choose compression or no compression backups.
Compression takes longer of course, but you save roughly half the space. EVO3D's stock system uncompressed is ~800mb, 380mb compressed. You choose.
Ability to auto restore GAPPS on zip flash (for CM based ROMS)
Ability to auto reboot after successful flashes (for the lazy)
Some devices utilize their capacitive buttons in recovery.
Home - Main Menu
Menu - Advanced Menu
Back - Up a Menu Level
Search - Select Current Selection
Battery Level and Timestamp (Better safe than sorry)
HTC Dumlock Instructions:
Install the build of TWRP using your method of choice, but you must actually flash TWRP to recovery. No fastboot booting it. We need it in recovery so that this build of TWRP will be flashed to your boot. This new build of TWRP has features in it to easily restore your original boot.
Reboot into recovery.
Make a backup of your phone.
Tap Advanced.
Tap HTC Dumlock. (If you don't see HTC Dumlock then you need to remove any custom TWRP theme that you might be using.)
Tap Install HTC Dumlock. This will install the app and binaries needed to make everything work nicely.
Reboot your device.
Find and open the HTC Dumlock app.
If/when prompted, give the app root (SuperUser) permissions.
Tap the Execute HTC Dumlock button.
Wait patiently for a couple of minutes. It takes a little while.
If your device doesn't reboot automatically, reboot it manually. Reboot it normally. DO NOT reboot it to recovery.
You should now be in your recovery, but your recovery is flashed into boot.
Tap Advanced.
Tap HTC Dumlock.
Tap Restore Original Boot.
Use your recovery like normal. Flash a new kernel. Restore a backup with a different kernel. Do whatever you please!
Consider donating!
Note, you must repeat steps 8 through 17 EVERY TIME you need to flash boot.
Installation:
Unlock bootloader at http://www.htcdev.com/bootloader/
Make sure fastboot is unchecked in power options and turn phone completely off
Boot into HBOOT then Fastboot
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
Video Tutorials:
How To Unlock The Bootloader EASIEST Method - https://www.youtube.com/watch?v=r0gzJdwCxX0
How To ROOT EASIEST METHOD - https://www.youtube.com/watch?v=S1KmsxO84UU
PC USB Mass Storage:
You can't! http://teamw.in/DataMedia
Downloads:
If rooted. You can flash using GooManager in the Play Store
http://techerrata.com/browse/twrp2/m7/
Thanks..
I have a buddy who is picking one up this week.. We all have the "one" from sprint and it works great.
Just ordered mine
Sent from my HTC One S
and you continue to pop up everywhere! lol. I can see it's the same recovery for the int'l/at&t models. I'll just mirror my toolkit here as well!
hasoon2000 said:
and you continue to pop up everywhere! lol. I can see it's the same recovery for the int'l/at&t models. I'll just mirror my toolkit here as well!
Click to expand...
Click to collapse
hahahaha I'll try to pop up on every new HTC device. :laugh:
hasoon2000 said:
and you continue to pop up everywhere! lol. I can see it's the same recovery for the int'l/at&t models. I'll just mirror my toolkit here as well!
Click to expand...
Click to collapse
Great! I used your Toolkit for my girlfriends One S! Keep up the great work. I should be going to the Tmo Store soon to decide if I want it or not.
Weird I am unable to have any zips show up here so I can flash them.. any idea why nothing shows up in TWRP?
Sent from my HTC One
I just tried using adb sideload and it transferred the rom zip, and the rom looked like it was installing, it even said it was installed. However, when I went to reboot, TWRP says 'are you sure no OS installed?' sure enough, i got stuck at the HTC One screen for a long time afterwards. The rom installed fine with adb push, then installing it. Just wondering if this is me or other people experience it.
Billyvnilly said:
I just tried using adb sideload and it transferred the rom zip, and the rom looked like it was installing, it even said it was installed. However, when I went to reboot, TWRP says 'are you sure no OS installed?' sure enough, i got stuck at the HTC One screen for a long time afterwards. The rom installed fine with adb push, then installing it. Just wondering if this is me or other people experience it.
Click to expand...
Click to collapse
Idk about this phone but did you make sure the boot.img was installed. Try flashing manually the boot.img.
Can anyone help please.I flashed twrp v 2.5.0.0 but I think I checked fast boot in power for some reason . Now twrp is giving me some problems like it doesn't recognise my internal storage and can't flash supersu or superu ,so my device is still unrooted. Could anybody tell me what should I do now? Thanks in advance and sorry guys if I'm using the wrong thread.
Sent from my HTC One using xda app-developers app
Delete.
Hello everyone... I really like the way TWRP works even though the backup files seem to be proprietary. I especially like the way the wipe area allows you to select other specific items under "advanced." One question I have though is this... is the "fix permissions" option working for everyone? Would this not work on certain ROMs? I am just curious. Thanks for your insight!
cant flash the recovery. it says out of memory :/
help pls
Could someone please link me to a flashable zip? No OS installed. outdated TWRP >_<
i want to ask that if i can flash that recovery then rooted my phone then back to stock recovery my HTC GPE works or not ??
sadeg111 said:
i want to ask that if i can flash that recovery then rooted my phone then back to stock recovery my HTC GPE works or not ??
Click to expand...
Click to collapse
It should work as long your bootloader is unlock.
Currently, all official CyanogenMod ROMs use loki tool to install the kernel on the LG G Pad 8.3 v500. Unfortunately, using loki tool causes a benign "secure boot error message" upon startup.
Here are some scripts that can be flashed in the recovery to convert a loki kernel to a bumped (permissive) kernel. The kernel will remain permissive until a new ROM or kernel is flashed again.
When making a kernel permissive, the following commands will be appended to the kernel boot command line:
Code:
androidboot.selinux=permissive selinux=0
Note: Only apply these scripts one time when setting the kernel to permissive mode or the command line above will be appended twice.
Instructions:
1) Flash ROM
2) Flash one of the scripts below, depending on what you want.
1) Convert a loki kernel to a bumped kernel
v500-loki-kernel-to-bumped-kernel-signed.zip
2) Convert a loki kernel to a bumped permissive kernel (turns off selinux)
v500-loki-kernel-to-bumped-permissive-kernel-signed.zip
3) Convert an already bumped kernel to a permissive bumped kernel (turns off selinux)
v500-bumped-kernel-to-bumped-permissive-kernel-signed.zip
Thanks to @Skin1980 for the bash bump code.
Thanks to @aicjofs for the script base.
This is amazing, thanks for your work.
This is really great, we all love what your doing for us - thanks again. I'm gonna take a stab in the dark and guess that its probably a bad idea to use the CM updater due to these having to be flashed along with an update?
annoyingduck said:
This is really great, we all love what your doing for us - thanks again. I'm gonna take a stab in the dark and guess that its probably a bad idea to use the CM updater due to these having to be flashed along with an update?
Click to expand...
Click to collapse
It's fine to use the cm updater, but you will have to reboot into the recovery twice to apply the patch. Also, if you want your Bluetooth pairings to remain intact, then you want to keep the kernel in permissive mode and never let it boot with selinux enabled (at least until the selinux denials are fixed).
@annoyingduck
You can let cm updater download and verify the update and then hit cancel when it asks to install it. Then manually reboot to recovery and install from the cm updater download directory.
Amazing job @Deltadroid! I applied the first patch, rebooted and the warning message was gone!
Thank you very much for your outstanding work!
[]'s
So... This just removes the warning message when booting?
jesuita said:
So... This just removes the warning message when booting?
Click to expand...
Click to collapse
Yes
jesuita said:
So... This just removes the warning message when booting?
Click to expand...
Click to collapse
That is the only visible effect. It provides a cleaner way of mounting the boot.img
Ok thanks
Works fine with last Infected build.
I assume we have to flash this script after each update.
ledabe974 said:
Works fine with last Infected build.
I assume we have to flash this script after each update.
Click to expand...
Click to collapse
Yes, after each rom or kernel you flash.
Yay! thanks to the permissive script, SuperSU works on CM13! =)
nytral said:
Yay! thanks to the permissive script, SuperSU works on CM13! =)
Click to expand...
Click to collapse
That is good to hear.
The reason systemless supersu does not work with our device is because it breaks the signature on our bumped boot image.
If you choose option #1 on the op after flashing supersu, you should be able to keep selinux in enforcing mode and just rebump the boot image to fix the signature that supersu breaks.
Edit: you will need to dirty flash the rom again to put the device back into enforcing mode.. Then flash supersu and finally the script to bump the boot image over again.
Deltadroid said:
That is good to hear.
The reason systemless supersu does not work with our device is because it breaks the signature on our bumped boot image.
If you choose option #1 on the op after flashing supersu, you should be able to keep selinux in enforcing mode and just rebump the boot image to fix the signature that supersu breaks.
Edit: you will need to dirty flash the rom again to put the device back into enforcing mode.. Then flash supersu and finally the script to bump the boot image over again.
Click to expand...
Click to collapse
Well, that's what I thought and what I did first, but actually latest beta SuperSU (2.68) is not breaking the boot sig for some reason (no bootloader error as with previous builds). Looking at logcat during the stuck boot I noticed some zygote process failing because of selinux and that's when I decided to try to disable it -> success! Now a cleaner way would probably be to give the logs to @Chainfire so he can have a look but given the non-popularity of V500 he probably won't care/not be able to fix it without one. Oh well, at least I have something working although not as secure as it should be. So thank you for this :good:
Thank you for this great job!!! I was stuck on the LG logo with the know loki message... I though that my v500 was bricked for good.
I used the first file after cleaning everything in twrp 3.0.0 (not usb and external) and installing a)6.0 mmb29v, b) su v2.65 and c) your 1st file.
2 questions. 1) whenever I flash and update should I flash it through twrp with the above mentioned order? 2) Should I flash other version (older like 2..8.7.x) and philz zip?
Thank you again for your great job!!!
glyrakos said:
Thank you for this great job!!! I was stuck on the LG logo with the know loki message... I though that my v500 was bricked for good.
I used the first file after cleaning everything in twrp 3.0.0 (not usb and external) and installing a)6.0 mmb29v, b) su v2.65 and c) your 1st file.
2 questions. 1) whenever I flash and update should I flash it through twrp with the above mentioned order? 2) Should I flash other version (older like 2..8.7.x) and philz zip?
Thank you again for your great job!!!
Click to expand...
Click to collapse
You did it correctly. Every time you flash SuperSU over again, you will need to flash this script directly after that to bump the kernel over again and fix the boot signature. Any recovery should work, but I recommend using the latest official TWRP.
Deltadroid said:
You did it correctly. Every time you flash SuperSU over again, you will need to flash this script directly after that to bump the kernel over again and fix the boot signature. Any recovery should work, but I recommend using the latest official TWRP.
Click to expand...
Click to collapse
Sorry, but as a nobbie let me ask you something more. Do you have a link for the latest official TWRP. How to flash it? Through TWRP 3.0.0 that I have now, or through sideload? Also I cannot enter TWRP with the combination of the 3 buttons. I get Factory Reset menu.
Thank you.
glyrakos said:
Sorry, but as a nobbie let me ask you something more. Do you have a link for the latest official TWRP. How to flash it? Through TWRP 3.0.0 that I have now, or through sideload? Also I cannot enter TWRP with the combination of the 3 buttons. I get Factory Reset menu.
Thank you.
Click to expand...
Click to collapse
The official TWRP for device is here
http://forum.xda-developers.com/showthread.php?p=61363260
You can flash the new recovery image from within TWRP.
When you use the 3 buttons to get to recovery, it asks to factory reset, but it goes to TWRP instead. It is a hack because our recoveries were never actually unlocked. Just say, yes and TWRP will open.
Deltadroid said:
The official TWRP for device is here
http://forum.xda-developers.com/showthread.php?p=61363260
You can flash the new recovery image from within TWRP.
When you use the 3 buttons to get to recovery, it asks to factory reset, but it goes to TWRP instead. It is a hack because our recoveries were never actually unlocked. Just say, yes and TWRP will open.
Click to expand...
Click to collapse
Maybe I am not doing something good but when using the 3 button method it goes to factory reset and stays there endless if I do not press something .... but power whipes everything (i've re-setup my v500 for about 15 times already....) ... and volume up/down exits the menu and reboots......
https://dl.twrp.me/angler/
So flash, much excite, such new. Wow.
Edit - I know I sound weird but I don't like dirty flashes. I always reboot into bootloader, fastboot erase recovery and then fastboot flash recovery twrp.img ( I rename it twrp.img for short) then boot into it. I have done this for years on BL unlocked devices and never had a problem flashing twrp. It's just ME, but I think it is fun typing the stuff, and it assures me that I have a clean state and am not dirty flashing anything! Also, on others phones I use RASHR instead of flashify. Once again, personal preference but have had better luck.
XDA Thread updated
And backs up with finger print
^ That's great news.
I tried flashed this but after trying to reboot into recovery got the broken android icon. Reflashed back to older version and it worked. Not sure if I had a corrupt come. Do you have to reboot the bootloader after flashing from fastboot for it to take? I just rebooted to system after flashing.
synnyster said:
I tried flashed this but after trying to reboot into recovery got the broken android icon. Reflashed back to older version and it worked. Not sure if I had a corrupt come. Do you have to reboot the bootloader after flashing from fastboot for it to take? I just rebooted to system after flashing.
Click to expand...
Click to collapse
Just out of curiosity, did you use flashify? I know two other people that it borked the flash also. I recommend rashr. But I also flash via otg cable and usb drive. I'd say you most likely had a bork download. Delete the img, run trimmer, redownload it. And flash via rashr and reboot and respond if it fixed it. Good luck!
Gytole said:
Just out of curiosity, did you use flashify? I know two other people that it borked the flash also. I recommend rashr. But I also flash via otg cable and usb drive. I'd say you most likely had a bork download. Delete the img, run trimmer, redownload it. And flash via rashr and reboot and respond if it fixed it. Good luck!
Click to expand...
Click to collapse
I flashed via fastboot after I updated to the newest android February security patch.
synnyster said:
I flashed via fastboot after I updated to the newest android February security patch.
Click to expand...
Click to collapse
Okay you're on stock?
Gytole said:
Just out of curiosity, did you use flashify? I know two other people that it borked the flash also. I recommend rashr. But I also flash via otg cable and usb drive. I'd say you most likely had a bork download. Delete the img, run trimmer, redownload it. And flash via rashr and reboot and respond if it fixed it. Good luck!
Click to expand...
Click to collapse
Gytole said:
Okay you're on stock?
Click to expand...
Click to collapse
Stock systemless root. Used Heisenberg's guide step 10 to update. Saw TWRP 3.0 so decided to try that.
synnyster said:
Stock systemless root. Used Heisenberg's guide step 10 to update. Saw TWRP 3.0 so decided to try that.
Click to expand...
Click to collapse
Fastboot erase recovery, then reflash twrp recovery, boot into recovery and reflash systemless root.
No problem dirty flashing here, but the process is a little different than it was on my previous phone where you would just flash it like a ROM...
You gotta:
"Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash."
OP's method seems like the best bet though...
Sent from my Nexus 6P using Tapatalk
"No problem dirty flashing here, but the process is a little different than it was on my previous phone where you would just flash it like a ROM..."
That's cause you're use to flashing zips people make flashable, i'm old school and use img's hahaha "LET'S MAKE FLASHING FUN!" Shutup Gytole...
Just out of curiosity has anyone tried flashing twrp as boot? I also have a thread in the tmobile G3 section and I almost wonder if thats why they bork their phone...lol
Just did it on my girlfriends G3 through twrp and was like, "they totally flashed it as boot...."
Used twrp manager from Google store was simple and easy
ROADKING17 said:
Used twrp manager from Google store was simple and easy
Click to expand...
Click to collapse
Way to deviate from the norm! Haha
Gytole said:
Way to deviate from the norm! Haha
Click to expand...
Click to collapse
Takes all kinds...
Sent from my Nexus 6P using Tapatalk
No need for this thread, as there is a TWRP thread in the development forum.
Thread closed.
hi Guys!
I just wanted to share my work with you.
I created a working TWRP recovery for the Pixel on Android O developer preview 4, that can boot and decrypt the /data partition. I don't own a Pixel XL, so I can't test, but @Chainfire did a few quick tests and it seems to be working on his Pixel XL too. So I would say you can try and see if it works for you. Please keep in mind, that I didn't test it, and neither Chainfire, or myself or anyone else can be blamed if it doesn't work, or damages your phone (shouldn't actually, but who knows..).
If you are still not scared enough, please follow this link to the Pixel forums and check out my work:
https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896
Good luck!
I test it on my pixel xl， working well.
Thank you very much.
But it seems to not be able to flash supersu
When I try to flash it via fastboot it says file is not signed. What am I doing wrong here? I wanted to be rooted and I am on Android op4 preview. Please guide me how to root. Thank you everyone.
sahilarora2003 said:
When I try to flash it via fastboot it says file is not signed. What am I doing wrong here? I wanted to be rooted and I am on Android op4 preview. Please guide me how to root. Thank you everyone.
Click to expand...
Click to collapse
Its in the instructions but here is the command and you shouldn't flash it but instead fastboot it.
fastboot boot trwp.img
flash the latest supersu 2.82 sr1
NVM. Mission accomplished. Thank you for help.
feimummy said:
I test it on my pixel xl， working well.
Thank you very much.
But it seems to not be able to flash supersu
Click to expand...
Click to collapse
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
SR2 flash fine
gubacsek said:
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
Click to expand...
Click to collapse
You can try SR2 flash fine.
gubacsek said:
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
Click to expand...
Click to collapse
Thank you for your answer.
Thank Chainfire.
But my phone Pixel XL is at home now,I will try it later.
Is it this one?
https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
feimummy said:
Thank you for your answer.
Thank Chainfire.
But my phone Pixel XL is at home now,I will try it later.
Is it this one?
https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
Click to expand...
Click to collapse
Yes, that should be it!
Although Chainfire has released a new version in zip format, with a lot of pixel (XL) related fixes. You can also try to flash that one using my modded TWRP.
gubacsek said:
Yes, that should be it!
Although Chainfire has released a new version in zip format, with a lot of pixel (XL) related fixes. You can also try to flash that one using my modded TWRP.
Click to expand...
Click to collapse
I have used your modded TWRP to flash SuperSU zip,but there was nothing happened after rebooting the phone.
And I also try "fastboot boot boot-to-root.img" just now,there was still nothing happened...
View attachment 4236828
I mean,it was so strange that SuperSU can not be flashed into my Pixel XL with these two methods.
——————————The final outcome——————————
I have solved the problem with this SuperSU version:
https://forum.xda-developers.com/showpost.php?p=72686197&postcount=10481
Thanks a lot.
feimummy said:
I have used your modded TWRP to flash SuperSU zip,but there was nothing happened after rebooting the phone.
And I also try "fastboot boot boot-to-root.img" just now,there was still nothing happened...
View attachment 4236828
I mean,it was so strange that SuperSU can not be flashed into my Pixel XL with these two methods.
Click to expand...
Click to collapse
Try to flash the original boot.img first.
1. reboot to bootloader
2. fastboot flash boot.img from the factory image zip
3. fastboot boot recovery.img
4. in the recovery, flash supersu
Or you can skip points 3 and 4, and fastboot boot boot-to-root.img
gubacsek said:
Try to flash the original boot.img first.
1. reboot to bootloader
2. fastboot flash boot.img from the factory image zip
3. fastboot boot recovery.img
4. in the recovery, flash supersu
Or you can skip points 3 and 4, and fastboot boot boot-to-root.img
Click to expand...
Click to collapse
Sr2 flash fine!
caballon said:
Sr2 flash fine!
Click to expand...
Click to collapse
Great! Nice to see that everything is working I had this itching, you know, when something is not as it should be, because I wanted to have Android O, but there was no recovery to do what I want... Now this feeling is gone, and I'm relaxed again
The only thing missing is a flashable zip. Is my current "itch"
Very nice. I booted into TWRP with no issue. I had already used boot-to-root so I did not have to flash SR2 in TWRP but nice knowing we have it working for the XL.
Thank you for making this sir.
Work like a charm in Final Android O!!! Thanks man.
caballon said:
Work like a charm in Final Android O!!! Thanks man.
Click to expand...
Click to collapse
Same here!
People have successfully rooted O Final? I used the img but I can't flash zips or access any folders they all have weird names is that due to Encryption?
liam_davenport said:
People have successfully rooted O Final? I used the img but I can't flash zips or access any folders they all have weird names is that due to Encryption?
Click to expand...
Click to collapse
Had this already sometimes on 7.1.2 with twrp rc 1 and 2. Must be an encryption error. Only way for me to use the phone again was to start all over with flashing factory image with flash-all.bat.
liam_davenport said:
People have successfully rooted O Final?
Click to expand...
Click to collapse
Reboot until you get prompted for your PIN in recovery, then flash SuperSU v2.82 SR3 from here.
The TWRP for the HD1910 works perfectly on the HD1925. Decryption works too. Install TWRP by using the installer.
Exact the img from the installer zip.
Boot to fastboot
Open a CMD within the extracted TWRP installer folder and type in
"fastboot boot recovery.img"
Once TWRP boots, then install the TWRP installer zip file.
I flashed magisk and it flashed with no issues. I used the latest version here.
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
dl.twrp.me
NOTE: I did it on the latest version, 11.0.1.18 So I'm not sure if it works on any older versions but I would assume so.
Yep, been out a while now. Works perfectly! However I highly highly recommend not using the twrp installer zip on our phones nor installing it by doing "fastboot flash recovery name_of_twrp.img"
Just download the latest .img and do "fastboot boot name_of_twrp.img" whenever you need to go into twrp recovery. Or you're just asking for trouble with OTA updates definitely no longer working (until you restore the stock recovery that matches the exact version of OOS that you are running) and a good possibility of getting a Qualcomm Crash-dump and losing or breaking all kinds of stuff.
starcms said:
Yep, been out a while now. Works perfectly! However I highly highly recommend not using the twrp installer zip on our phones nor installing it by doing "fastboot flash recovery name_of_twrp.img"
Just download the latest .img and do "fastboot boot name_of_twrp.img" whenever you need to go into twrp recovery. Or you're just asking for trouble with OTA updates definitely no longer working (until you restore the stock recovery that matches the exact version of OOS that you are running) and a good possibility of getting a Qualcomm Crash-dump and losing or breaking all kinds of stuff.
Click to expand...
Click to collapse
I already know about all that. I've had this phone over a year, so I'm familiar with the hidden "secrets".
starcms said:
Yep, been out a while now. Works perfectly! However I highly highly recommend not using the twrp installer zip on our phones nor installing it by doing "fastboot flash recovery name_of_twrp.img"
Just download the latest .img and do "fastboot boot name_of_twrp.img" whenever you need to go into twrp recovery. Or you're just asking for trouble with OTA updates definitely no longer working (until you restore the stock recovery that matches the exact version of OOS that you are running) and a good possibility of getting a Qualcomm Crash-dump and losing or breaking all kinds of stuff.
Click to expand...
Click to collapse
BTW, with unlocked bootloader OTA's are not available no matter what type of recovery you have installed. Unless you have reinstalled the reserve.img after unlocking the bootloader
AntiSocialSingh said:
@BobbyLynn I followed your tutorial to install the CrDroid recovery. Can you tell me how to flash TWRP? Bit of a noob for this phone.
Click to expand...
Click to collapse
Exact (Unzip) the zip folder. Within the extracted folder you'll see some other files. One of them is a recovery.img file. Open a command or PowerShell in the extracted folder. Reboot to fastboot.
Boot to fastboot and run this command
"fastboot boot recovery.img"
Once it boots into TWRP, then click on "install" and locate the TWRP installer zip and select it. It'll most likely be in the download folder. Just make sure you know where the TWRP installer zip is located before you even boot into TWRP
BobbyLynn said:
Exact (Unzip) the zip folder. Within the extracted folder you'll see some other files. One of them is an .img file (recovery). Open a command or PowerShell in the extracted folder. Reboot to fastboot.
Boot to fastboot and run this command
"fastboot boot recovery.img"
Once it boots into TWRP, then click on "install" and locate the TWRP installer zip and select it. It'll most likely be in the download folder. Just make sure you know where the TWRP installer zip is located before you even boot into TWRP
Click to expand...
Click to collapse
BTW download this TWRP from the link in my thread "twrp-installer-3.6.1_11-0-hotdog.zip"
AntiSocialSingh said:
@BobbyLynn Do i need to flash both a & b like i did in the case of crDroid?
Click to expand...
Click to collapse
Not at all. The installer will take care of all that once you boot into TWRP
AntiSocialSingh said:
@BobbyLynn Should I take a backup? Would it wipe my storage? or it would be as it is?
Click to expand...
Click to collapse
No it won't wipe data or anything else. But it's always good to have a backup just in case anything goes sour.
AntiSocialSingh said:
@BobbyLynn I am on the screen which says Install, Wipe, Backup, restore...... what should i do to install the zip file now?
Click to expand...
Click to collapse
Just click on "install" then located the installer zip file then select it and install it
AntiSocialSingh said:
I copied the .zip file on my phone but cannot navigate to it since all it shows is (Up A level), does not show the directories inside the storage
Click to expand...
Click to collapse
Select up a level then scroll down until you see a file called "storage" that'll take you to your storage. If it doesn't, the go back and click on "sdcard" But I'm almost certain it's in the storage folder
AntiSocialSingh said:
I think i need to flash it once via TWRP, i'll try it later, but thank you, it means that this TWRP works!
Click to expand...
Click to collapse
I just checked..... The "sdcard" folder is the one that takes you to the internal storage where the download folder is located. But as soon as you hit 'install" it should've taken you straight to the internal storage. If it didn't, then it sounds like it's still encrypted. If that's the case, then remove any screen locks on your phone before flashing TWRP
AntiSocialSingh said:
@BobbyLynn Let me try once again with the screen lock removed.
Click to expand...
Click to collapse
When I installed TWRP I didn't have a screen lock. But after installing TWRP I set a screen lock and TWRP decrypted just fine. So I'm guessing if you install TWRP while you have a screen lock it doesn't install properly so it can't decrypt. It appears that any screen locks must be removed before installing and after installing reapply a screen lock
AntiSocialSingh said:
@BobbyLynn It worked! So basically, I had to remove both fingerprint and pattern locks to get it to work. Thanks a ton!!
Click to expand...
Click to collapse
No problem
BobbyLynn said:
No problem
Click to expand...
Click to collapse
I'm kinda curious, why did you install TWRP? Are you fixing to "test drive" some custom ROM's or flash some mods? Or did you install TWRP just for the hell of it?
AntiSocialSingh said:
@BobbyLynn The latter yes, test driving some mods, and I am used to the interface of TWRP, not crDroid much, personal preference hahahaha....Thank you so much once again. you're a legend.
Click to expand...
Click to collapse
I'm more use to TWRP myself. I started using TWRP about 10 years ago, it was and still is the best recovery out there. I just happened to install crDroid the other day just to test something. And that test turned out to be a great discovery of a simple way to root the stock firmware. Since I have a extra McLaren, I do quite a bit of testing and modding and experimental stuff. I'm currently working on installing the global firmware (unbranding) it. No luck yet, but I might be getting close.
AntiSocialSingh said:
@BobbyLynn I will be the first one to follow your tutorial if you manage to flash the Global ROM on it sir. I promise haha!
Click to expand...
Click to collapse
You can bet your ass that if I pull off that trick it'll get LOT'S of comments from people thanking me lol. We've been wanting to install the global firmware on this phone, but nobody can figure out how to mod the ROM to make it flash on this phone. There's some very smart developers that own this phone, so I'm surprised that none of them have figured it out yet. So I've been tinkering around with trying to install it. It's looking like I'm going to have to make some modifications to the global ROM and/or the phone too to make the MSM tool see the phone as a comparable device
BobbyLynn said:
BTW, with unlocked bootloader OTA's are not available no matter what type of recovery you have installed. Unless you have reinstalled the reserve.img after unlocking the bootloader
Click to expand...
Click to collapse
Well, yeah, restoring reserve.img is a prerequisite to get OTAs with the bootloader unlocked, but it only has to be done once. After that, for each ota, just restore the boot image to stock (uninstall magisk) and you're good to go
starcms said:
Well, yeah, restoring reserve.img is a prerequisite to get OTAs with the bootloader unlocked, but it only has to be done once. After that, for each ota, just restore the boot image to stock (uninstall magisk) and you're good to go
Click to expand...
Click to collapse
I wanted to do OTA how should I restore my reserve.img?