Related
hi guys! I'm new at this forum, so if i'm doing something wrong about rules and regulation, even if i've read them, correct me please! However, i just bough an At&T Atrix HD with stock 4.1.1 and i wanted to install a CM11; i obtained root privileges and unlocked the bootloader, and when i try to flash the clockwork recovery, apparently everything goes fine in fact i get no errors, but when i turn off the device and try to reboot in recovery it displays the "dead" droid with a red explanation mark. I've read in the cyanogen wiki that some firmwares during the reboot overwrite the custom recovery, is this the case? Which is the command or the procedure to reboot the cell in recovery then?
PS: I flash it through the command line by the PC, i got OSx and i tried with the clockwork posted in cyanogen wiki and the one posted here http://forum.xda-developers.com/showthread.php?t=2421418
Hi, first of all, did you installed the recovery with: fastboot flash recovery recovery.img right??
If you did so, you just need to turn off your phone, hold volume up button and power button and wait until it enters to recovery mode. From there you can flash a new ROM if you have it on your SD card or internal storage.
sliker90 said:
hi guys! I'm new at this forum, so if i'm doing something wrong about rules and regulation, even if i've read them, correct me please! However, i just bough an At&T Atrix HD with stock 4.1.1 and i wanted to install a CM11; i obtained root privileges and unlocked the bootloader, and when i try to flash the clockwork recovery, apparently everything goes fine in fact i get no errors, but when i turn off the device and try to reboot in recovery it displays the "dead" droid with a red explanation mark. I've read in the cyanogen wiki that some firmwares during the reboot overwrite the custom recovery, is this the case? Which is the command or the procedure to reboot the cell in recovery then?
PS: I flash it through the command line by the PC, i got OSx and i tried with the clockwork posted in cyanogen wiki and the one posted here http://forum.xda-developers.com/showthread.php?t=2421418
Click to expand...
Click to collapse
1. You're rooted so go to /system/etc and rename "install-recovery.sh" to "install-recovery.sh.bak"
2. Use Myth Tools to flash recovery (CWM or PhizTouch is included in the tool)
3. Check and Test
thanks to both of you guys!! i've solved with the solution in the second post, just deleting the "install-recovery.sh" script, i was going crazy!! i hope this post will help someone else!
PS: i don't understand why they do not put these solutions in the first posts in important threads like that one i've linked....
devilsking said:
1. You're rooted so go to /system/etc and rename "install-recovery.sh" to "install-recovery.sh.bak"
2. Use Myth Tools to flash recovery (CWM or PhizTouch is included in the tool)
3. Check and Test
Click to expand...
Click to collapse
I thought mythtools removed the .sh file by itself?
jaweinre said:
I thought mythtools removed the .sh file by itself?
Click to expand...
Click to collapse
Nope. You need to do it manually.
I tried to put that function into Myth Tools but it's impossible to do it via adb commands if the kernel is not enabled "insecure".
That's why I put a guide line in Myth Tools to remind user rename that file manually before flashing recovery.
devilsking said:
Nope. You need to do it manually.
I tried to put that function into Myth Tools but it's impossible to do it via adb commands if the kernel is not enabled "insecure".
That's why I put a guide line in Myth Tools to remind user rename that file manually before flashing recovery.
Click to expand...
Click to collapse
Not necessarily. You don't HAVE to rename that file before flashing. The newer CWM's detect that file and will fix it for you. All you gotta do is enter recovery and exit it through the menu, it'll prompt about the file, and say yes to it. Problem solved. It's what I do along with flashing a root zip with every stock flash I do; haven't had a problem yet.
"Enter and exit CWM" is a lot easier to describe than renaming or deleting a file on the /system partition...less error prone too.
skeevydude said:
Not necessarily. You don't HAVE to rename that file before flashing. The newer CWM's detect that file and will fix it for you. All you gotta do is enter recovery and exit it through the menu, it'll prompt about the file, and say yes to it. Problem solved. It's what I do along with flashing a root zip with every stock flash I do; haven't had a problem yet.
"Enter and exit CWM" is a lot easier to describe than renaming or deleting a file on the /system partition...less error prone too.
Click to expand...
Click to collapse
We are 2, never had problems
Here're the official links for Cherry Mobile One H940:
For fastboot flashable images:
Builds Available: LBY29G, LMY47O
Download: here
For OTAs:
Build: LBY29G -> LMY47O
Android Version: 5.1 (Beta) -> 5.1 Official
Download: here
Flashing Instructions:
A. Using ADB sideload (for recovery flashable update zips):
1.) Flash stock recovery.
2.) Boot to stock recovery.
3.) Perform up + power button to show menu.
4.) Select Apply update from ADB.
5.) Install ADB drivers if on Windows and not yet installed.
6.) Open cmd prompt.
7.) Change directory to where you downloaded the update zip.
8.) Issue cmd: adb sideload <update.zip filename>
9.) Wait until completed.
10.) Select reboot.
B. Using fastboot:
1.) Boot into bootloader.
2.) Flash image using fastboot flash <partition name> <image filename>.img command.
3.) Reboot using fastboot reboot command.
C. Using DD (for flashing images like system.img):
1.) Boot into custom recovery. (you could use fastboot boot custom-recovery.img so that you don't overwrite your existing one)
2.) Push image file to /sdcard using adb push command. (you might have to mount the sdcard partition before doing this)
3.) Open an ADB command shell.
4.) Go to /sdcard.
5.) Find the system partition by issuing a cat /proc/partitions command. It should be the one sized exactly 1GB (1,024,000 shown).
6.) Use dd if=/sdcard/<image filename>.img of=/dev/block/<name of partition> .
7.) Reboot either using custom recovery or just issuing an adb reboot after exiting from ADB command shell.
do you have another working file for LMY47O system.img? i'm getting a fastboot flash fail (chunk unkown) error. thanks
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
intersectRaven said:
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
Click to expand...
Click to collapse
same problem here
thank you
Uploaded. If it still fails, you might have to use dd to restore. Odd that it fails now when it was fine before. :/
OTA Flashing Error
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
erickho0407 said:
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
Click to expand...
Click to collapse
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
intersectRaven said:
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
Click to expand...
Click to collapse
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
erickho0407 said:
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
Click to expand...
Click to collapse
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
intersectRaven said:
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
Click to expand...
Click to collapse
Ok. So this means that I reflash boot.img right (would probably use fastboot). Thank you very much for assistance
Sir
can you capture ota for myphone uno
gabisonfire98 said:
Sir
can you capture ota for myphone uno
Click to expand...
Click to collapse
Unfortunately, I don't have an Uno so no.
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Working internal detect for pc and file ?
marjoejoejoe said:
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Click to expand...
Click to collapse
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
intersectRaven said:
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
Click to expand...
Click to collapse
I'll have another go at it later today. Was able to flash my own backup using CWM
marjoejoejoe said:
I'll have another go at it later today. Was able to flash my own backup using CWM
Click to expand...
Click to collapse
Still, it should be foolproof. I already checked and double-checked the system image I uploaded and it's mountable in Linux so it should restore correctly like the previous LBY image. I can't think of any other reason aside from some sort of protection that would disallow flashing of the system image through both fastboot and dd.
*On second thought, I'm reupping the image. I just flashed it using dd on my device and it works perfectly.
success, was running a windows 7 virtual machine in OSX. it must have been a protection, you are right...ran it using OSX instead (stupid me, why i didn't use it in the first place for fastboot).
files are good to go thanks man
Need help in Flashing the Stock Recovery.
Hi Guys,
I need help in flashing the stock recovery.
I've used the ALL-IN-ONE TOOL to unlock my phone's bootloader, flash the PhilZ Touch Customer recovery and Root my CM1
[http://forum.xda-developers.com/cro.../tool-master-tool-unlock-bootloader-t2997696]
However I'm unsuccessful flashing the stock recovery from the ALL-IN-ONE TOOL so I can update my phone's software to Android 5.1.1.
Can I flash the stock recovery using one of the files here? If yes, can someone please teach me how.
Thanks in advance!
OTG
Hi,
Just a quick question, after flashing using this ROM, will CM One support OTG? Or do I need to root the phone first? Is there a way to add support for OTG?
Pardon me if this may not be much related to the topic.
P/S: Im sorry if im against this XDA or forums rules. Its my first time to post something. If i done something wrong kindly let me know.
Condition: You have Official Marshmallow WW_V21.40.1220.1698 installed on your ZE601KL (I forgot to mention that Im coming from CM13, that makes it need bootloader unlock n root probably?)
TWRP install:
-go into fastboot mode (shut down your phone. press VOL UP + POWER at the same time until it vibrates and release)
-download and install adb (can get it here i guess. credit to @snoop005 )
-download twrp here (credit to maintainer @LuK1337) and put it in the ADB folder
-in ur pc hold shift + right click and click "open command window here" in ADB folder
-type in "fastboot device" and make sure ur device is detected
-type in "fastboot flash recovery recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot flash recovery twrp-3.0.2-4-Z00T.img )
-type in "fastboot boot recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot boot twrp-3.0.2-4-Z00T.img )
-look at ur phone and it should be installed
Root install
-download SuperSU (credit to @Chainfire) (thanks to @Cr0ssL1nk for notify me about the updated SuperSU! )
-boot to recovery (shut down your phone. press VOL DOWN + POWER at the same time until it vibrates and release)
-select install and browse for the .zip file location
-wait for the installation done and ure good to go
It works on my ZE601KL!!!
Thank you very much xyexiaoyuer in your first post
I would assume this process is the same for any of the variants for which the bootloader is already unlocked and assuming you use the correct TWRP image.
If nothing else, it should work for any Z00T phone. I'll try it on my ZE551KL tonight.
xyexiaoyuer said:
P/S: Im sorry if im against this XDA or forums rules. Its my first time to post something. If i done something wrong kindly let me know.
Condition: You have Official Marshmallow WW_V21.40.1220.1698 installed on your ZE601KL
TWRP install:
-go into fastboot mode (shut down your phone. press VOL UP + POWER at the same time until it vibrates and release)
-download and install adb (can get it here i guess. credit to @snoop005 )
-download twrp here (credit to maintainer @LuK1337) and put it in the ADB folder
-in ur pc hold shift + right click and click "open command window here" in ADB folder
-type in "fastboot device" and make sure ur device is detected
-type in "fastboot flash recovery recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot flash recovery twrp-3.0.2-4-Z00T.img )
-type in "fastboot boot recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot boot twrp-3.0.2-4-Z00T.img )
-look at ur phone and it should be installed
Root install
-download SuperSU ive tested SuperSU Root BETA v2.67.zip credit to them (help me credit them as i dont know who to tag)
-boot to recovery (shut down your phone. press VOL DOWN + POWER at the same time until it vibrates and release)
-select install and browse for the .zip file location
-wait for the installation done and ure good to go
Click to expand...
Click to collapse
On the "fastboot boot recovery.img", I first got it to successfully transfer over something, then the second line said that it failed.
I continually did this and got the same results and my phone continued to say "fastboot" in the corner, so I wasn't sure if anything had happened.
I finally "gave up" and pulled the battery but I booted into the Recovery (Vol down + Power) and found that TWRP actually was installed and from there I flashed over SuperSU and was rooted in minutes.
Great job, and thanks! I may be a bit rusty with all this since this is my first Android device in about 3 years.
Joxefo said:
It works on my ZE601KL!!!
Thank you very much xyexiaoyuer in your first post
Click to expand...
Click to collapse
wooot~ npnp bro..thank god it works for you too!!
rczrider said:
I would assume this process is the same for any of the variants for which the bootloader is already unlocked and assuming you use the correct TWRP image.
If nothing else, it should work for any Z00T phone. I'll try it on my ZE551KL tonight.
Click to expand...
Click to collapse
i forgot to mention the bootloader bro. sorry about that. already edited in my 1st post. So how was ur phone? does the method work on your ZE551KL?
ndh777 said:
On the "fastboot boot recovery.img", I first got it to successfully transfer over something, then the second line said that it failed.
I continually did this and got the same results and my phone continued to say "fastboot" in the corner, so I wasn't sure if anything had happened.
I finally "gave up" and pulled the battery but I booted into the Recovery (Vol down + Power) and found that TWRP actually was installed and from there I flashed over SuperSU and was rooted in minutes.
Great job, and thanks! I may be a bit rusty with all this since this is my first Android device in about 3 years.
Click to expand...
Click to collapse
good to hear that bro!! probably it failed because of bootloader? hv u unlock it before? im sorry didnt mention it on my first post. my bad my bad
Boot twrp, not flash it to root?
Does anyone know if it his possible to just boot twrp from adb/ fasboot( not actually flash it), flash SuperSU to root my device, then reboot to stock to keep stock recovery ? My bootloader is unlocked.
long2ski said:
Does anyone know if it his possible to just boot twrp from adb/ fasboot( not actually flash it), flash SuperSU to root my device, then reboot to stock to keep stock recovery ? My bootloader is unlocked.
Click to expand...
Click to collapse
hi broo..you can always flash stock recovery after u flash superSU using twrp =)
xyexiaoyuer said:
hi broo..you can always flash stock recovery after u flash superSU using twrp =)
Click to expand...
Click to collapse
Thanks, but I am pretty sure Flashing twrp writes over stock recovery and unless someone else has the stock image, you can't get it back. I don't know how to make a backup of stock recovery, that's why I wondered if only booting twrp will work.
long2ski said:
Thanks, but I am pretty sure Flashing twrp writes over stock recovery and unless someone else has the stock image, you can't get it back. I don't know how to make a backup of stock recovery, that's why I wondered if only booting twrp will work.
Click to expand...
Click to collapse
if ure using ze601kl, i think the stock recovery can be downloaded here .. download according to your version of firmware of course =) let me know if its work for you. the last time im coming from cm13 to Lollipop im using recovery from there to write off twrp. hope this helps =)
Thanks, that's a great resource! I kind of hijacked this thread since I have the ze551kl. Even though its a zoot model, I'm reluctant to flash anything that is not the exact model firmware. Will the 601 image work for the 551?
long2ski said:
Thanks, that's a great resource! I kind of hijacked this thread since I have the ze551kl. Even though its a zoot model, I'm reluctant to flash anything that is not the exact model firmware. Will the 601 image work for the 551?
Click to expand...
Click to collapse
i dont think so..better dont as i only tested this with ze601kl =( buttttt the stock recovery for your model probably can be downloaded here not sure it will work though..proceed at ur own risk.
sorry bro if its not being helpful
xyexiaoyuer said:
i forgot to mention the bootloader bro. sorry about that. already edited in my 1st post. So how was ur phone? does the method work on your ZE551KL?
Click to expand...
Click to collapse
Yep, worked fine on the ZE551KL.
long2ski said:
Does anyone know if it his possible to just boot twrp from adb/ fasboot( not actually flash it), flash SuperSU to root my device, then reboot to stock to keep stock recovery ? My bootloader is unlocked.
Click to expand...
Click to collapse
long2ski said:
Thanks, that's a great resource! I kind of hijacked this thread since I have the ze551kl. Even though its a zoot model, I'm reluctant to flash anything that is not the exact model firmware. Will the 601 image work for the 551?
Click to expand...
Click to collapse
You can boot into TWRP without overwriting your stock recovery using:
HTML:
fastboot boot twrp.img
That would allow you to install SuperSU without actually installing TWRP. If you want to replace stock recovery with TWRP, you would use:
HTML:
fastboot flash recovery twrp.img
xyexiaoyuer said:
P/S: Im sorry if im against this XDA or forums rules. Its my first time to post something. If i done something wrong kindly let me know.
Condition: You have Official Marshmallow WW_V21.40.1220.1698 installed on your ZE601KL (I forgot to mention that Im coming from CM13, that makes it need bootloader unlock n root probably?)
TWRP install:
-go into fastboot mode (shut down your phone. press VOL UP + POWER at the same time until it vibrates and release)
-download and install adb (can get it here i guess. credit to @snoop005 )
-download twrp here (credit to maintainer @LuK1337) and put it in the ADB folder
-in ur pc hold shift + right click and click "open command window here" in ADB folder
-type in "fastboot device" and make sure ur device is detected
-type in "fastboot flash recovery recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot flash recovery twrp-3.0.2-4-Z00T.img )
-type in "fastboot boot recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot boot twrp-3.0.2-4-Z00T.img )
-look at ur phone and it should be installed
Root install
-download SuperSU ive tested SuperSU Root BETA v2.67.zip credit to them (help me credit them as i dont know who to tag)
-boot to recovery (shut down your phone. press VOL DOWN + POWER at the same time until it vibrates and release)
-select install and browse for the .zip file location
-wait for the installation done and ure good to go
Click to expand...
Click to collapse
Are you sure your phone is truely rooted and that apps needing root really works ?
Because in the official SuperSU page on XDA: http://forum.xda-developers.com/showthread.php?t=1538053 , the developpers says your phone must already be rooted before flashing SuperSU.
Also, change the 2.76 Beta's link you gived for SuperSU in your tutorial to the 2.76 Stable version from my link to the official SuperSU XDA page.
Cr0ssL1nk said:
Are you sure your phone is truely rooted and that apps needing root really works ?
Because in the official SuperSU page on XDA: http://forum.xda-developers.com/showthread.php?t=1538053 , the developpers says your phone must already be rooted before flashing SuperSU.
Also, change the 2.76 Beta's link you gived for SuperSU in your tutorial to the 2.76 Stable version from my link to the official SuperSU XDA page.
Click to expand...
Click to collapse
Welp! now that i check back using "root check" apps it seems that the app hv some trouble to detect whether the phone is rooted. the last time everything was okay except for busybox. Perhaps because i rebooted the device? nvrtheless i will update the link and test the stable supersu given in the link
xyexiaoyuer said:
Welp! now that i check back using "root check" apps it seems that the app hv some trouble to detect whether the phone is rooted. the last time everything was okay except for busybox. Perhaps because i rebooted the device? nvrtheless i will update the link and test the stable supersu given in the link
Click to expand...
Click to collapse
I don't think rebooting caused this.
The thing that makes me worry is that Busybox was not okay the first time you rooted your phone, because it must be one of the first thing that must be ok when you root a phone.
Have you got any updates on your side about making root really working ?
Cr0ssL1nk said:
I don't think rebooting caused this.
The thing that makes me worry is that Busybox was not okay the first time you rooted your phone, because it must be one of the first thing that must be ok when you root a phone.
Have you got any updates on your side about making root really working ?
Click to expand...
Click to collapse
Hi Brooooo, im happy to report that the SuperSU is still intact even if the device has been rebooted several times. thx a lot broooo and busybox is installed correctly toooo. already put thumbnails attachment at the 1st post for proof
xyexiaoyuer said:
Hi Brooooo, im happy to report that the SuperSU is still intact even if the device has been rebooted several times. thx a lot broooo and busybox is installed correctly toooo. already put thumbnails attachment at the 1st post for proof
Click to expand...
Click to collapse
No problem, proofs are just great ! :highfive:
Also, check this post: http://forum.xda-developers.com/showpost.php?p=67978015&postcount=8
Because you also must allow SuperSU in ASUS' Autostart Manager, that may be the problem you also got.
But please remember: Do not post something that seems to work but is not, a Beta or something not stable to other people without a lot of checking first
rczrider said:
Yep, worked fine on the ZE551KL.
You can boot into TWRP without overwriting your stock recovery using:
HTML:
fastboot boot twrp.img
That would allow you to install SuperSU without actually installing TWRP. [/HTML]
Click to expand...
Click to collapse
Thanks to everyone's help and ideas and especially to @rczrider. On my ze551kl, I successfully booted the twrp.img in fastboot, did a backup through twrp, then installed supersu zip, and successfully rooted. No overwrite of stock recovery with all the root privileges. Perfect.
Download
v3.2.1-0
Sauce: Github
Fixed /system mounting issues
let me know if you have any issues and I will do what I can to fix them.
Credit: @Josh1x for having the h870 device tree put together for me to clone and update. I will fix the original author on my master branch as soon as I get some time
Thank you!
Works like a charm. No issues here, thanks bro.
---------- Post added at 02:27 PM ---------- Previous post was at 01:42 PM ----------
Also this recovery also fixes the error messages apon flashing mods and what not
How can we apply it if no fastboot commands work
Trippyy Doee said:
How can we apply it if no fastboot commands work
Click to expand...
Click to collapse
Follow the steps exactly in this guide https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 afterwards flash the image provided here in recovery
MudaTrucka said:
Follow the steps exactly in this guide https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 afterwards flash the image provided here in recovery
Click to expand...
Click to collapse
So this is all we've been waiting for ?! Finally can haz root ? ?
MudaTrucka said:
Follow the steps exactly in this guide https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 afterwards flash the image provided here in recovery
Click to expand...
Click to collapse
when i go into recovery mode all i get is no command. what should i do?
purplekushDGK said:
when i go into recovery mode all i get is no command. what should i do?
Click to expand...
Click to collapse
I think you might have to reflash recovery but idk I'm not the best with this
MudaTrucka said:
I think you might have to reflash recovery but idk I'm not the best with this
Click to expand...
Click to collapse
Opemilekan's method actually worked, had to flash supersu then used flashify to flash h872 twrp. thanks for the response man
purplekushDGK said:
Opemilekan's method actually worked, had to flash supersu then used flashify to flash h872 twrp. thanks for the response man
Click to expand...
Click to collapse
No problem, I thought I'd at least try to help
@KAsp3rd W00T -- glad to see that you built this.
The new version of the lafsploit will be out later today, and with it you can use any recovery your want. It handles all the hash verifications internally. It is about as automated as I can make it.
It will be:
./flash-h918-laf.py # Flashes the h918 laf without the need of LG UP, so no brick risks if people aren't paying attention
./root-h872.sh <recovery.img> # If specified, it will use the recovery.img passed, if not, then it will use this version which will be included in the repo
./post-root.sh # This takes care of all the final steps.
So three commands, and that is it. If I could force a reboot back into download mode, it would be one command, but a reboot into download mode is required between each command..
-- Brian
MudaTrucka said:
No problem, I thought I'd at least try to help
Click to expand...
Click to collapse
Can you tell me this method? I cannot get this image to stick, it always reverts back to H870, meaning I cannot flash anything custom (guess I could run Remix H870-would that work?)
agmyers76259 said:
Can you tell me this method? I cannot get this image to stick, it always reverts back to H870, meaning I cannot flash anything custom (guess I could run Remix H870-would that work?)
Click to expand...
Click to collapse
Flash the image to recovery, use the steps in the root thread to get it to stick and make sure you're actually booting into recovery and not laf
runningnak3d said:
@KAsp3rd W00T -- glad to see that you built this.
The new version of the lafsploit will be out later today, and with it you can use any recovery your want. It handles all the hash verifications internally. It is about as automated as I can make it.
It will be:
./flash-h918-laf.py # Flashes the h918 laf without the need of LG UP, so no brick risks if people aren't paying attention
./root-h872.sh <recovery.img> # If specified, it will use the recovery.img passed, if not, then it will use this version which will be included in the repo
./post-root.sh # This takes care of all the final steps.
So three commands, and that is it. If I could force a reboot back into download mode, it would be one command, but a reboot into download mode is required between each command..
-- Brian
Click to expand...
Click to collapse
Any idea when this might be ready good sir? I am not in a good place right now with my G6, could really use these commands---stuck in TWRP and can boot a rom, but somehow didnt follow your Step 3 in the Root guide, and my misc.img didnt get moved over, thus I have a rom that cannot connect to Wifi due to lack of MAC--this update would be huge, as I would go back to stock and restart this mess.
TIA
That won't help you now. Hopefully you still have the backup of your misc partition that was made in step 2. If so, boot to TWRP, and run:
adb push misc.img /sdcard/
adb shell dd if=/sdcard/misc.img of=/dev/block/bootdevice/by-name/misc
-- Brian
how do you flash the update
how do you flash the update? its not a option in the system app
purplekushDGK said:
Opemilekan's method actually worked, had to flash supersu then used flashify to flash h872 twrp. thanks for the response man
Click to expand...
Click to collapse
I used flashify and was promted for a decryption password upon booting recovery. Am I doing something wrong?
(Note that I can still access storage on the original download mode twrp, but not on this one)
Like everyone else I'm also confused as to how I can get the h872 recovery to work without breaking anything since I have the h870 recovery on laf
Stupid question I think, but I get a "Traceback (most recent call last):" after entering ./partitions.py --restoremisc twrp-3.2.1-0-h870.img .
Is there a specific place to put the TWRP ing file ? I think when I run the command its not finding the img.
MudaTrucka said:
Follow the steps exactly in this guide https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 afterwards flash the image provided here in recovery
Click to expand...
Click to collapse
Hey so I already followed this tut last week and have been on root but having issues that this recovery fixes, how can I flash to this TWRP?
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.
235anders15 said:
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
Click to expand...
Click to collapse
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
sam_htc_touch said:
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
Click to expand...
Click to collapse
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
235anders15 said:
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
Click to expand...
Click to collapse
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
sam_htc_touch said:
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
Click to expand...
Click to collapse
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
sam_htc_touch said:
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
Click to expand...
Click to collapse
Just for the benefit of all (if it matters), noticed that Magisk wasn't passing the Safety Net check and was showing failed for all 3. Used this fix and all is well now (Used the Sept 13 update on the page)
previously patching with stable 11.1.1.1 and broke some major functionality (eg: wifi crash, mess up video player and codec), now try to patch with magisk version, will update later
abhi0039 said:
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.
Click to expand...
Click to collapse
stable.img from there (and the other ones) dont fastboot boot on my OSS 1.1.1.1 fastboot mode.
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
F5:ed said:
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
Click to expand...
Click to collapse
Press and hold vol up, down , power at the same time for a while it will boot to fastboot.
I got boot loop after updating to 11.1.2.2
Any new boot img?
izik.avi said:
I got boot loop after updating to 11.1.2.2
Any new boot img?
Click to expand...
Click to collapse
Haven't tested yet but here you go
rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
This one works great. Thank you.
The attached file in #13 above worked, thank you!
In case someone would like to now "How to do it" until next time this is how I did it:
How to install OOS update and root via created patch.img file in the Magisk app
1. Download the full version eg the OOS 11.x.x.x.zip file on the computer, and copy the file to the phone's internal memory as well.
2. Run the payload_dump program (https://androidfilehost.com/?fid=1899786940962605222) to extract a boot.img from the computer. You have to extract the payload.bin file from the OOS 11.x.x.x.zip file and place it in the Input folder, then run the exe-file and wait for payload to complete, then copy over the boot.img file found in the Output folder to the phone.
3. Go to Magisk app on the phone, click on the top install "Magisk", click "Select and patch a file", search for the boot.img file you created.
4. Now, Magisk will create a patched magic.img file from the boot.img file (can be called eg magic_patched-23000_xt8QR.img)
5. Copy the magisk_patched-xxxxxxx.img to your computer's "Root folder" where you have stored ADB files, etc
6. Now install the OOS 11.x.x.x zip file (should be in the mobile's Internal memory) via Settings> System> System updates and the "gear"> Local upgrade
7. When done, DO NOT reboot but go directly to Fastboot mode + connect cable to the computer
8. On the computer, type from your "Root folder":
fastboot flash boot magisk_patched-xxxxxxx.img
9. Reboot the phone - you are rooted!
rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
raymund08 said:
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
Click to expand...
Click to collapse
Yes
rippledrums said:
Yes
Click to expand...
Click to collapse
Thank you
Can confirm OP fastboot commands and patched boot img are working for 11.1.1.1.I uninstalled magisk by mistake and could regain root, quick and painless
Can anyone help me? flashed patched boot to A and B Slot. But Magisk is N/A. Any idea?