So, after searching and asking to no avail, I decided to test it myself, and it works!
After you unlocks your android one device, your warranty bit is set to no, even if you lock it again afterwards.
This may or may not affects your real warranty service. But better safe than sorry.
This will also locks your bootloader once again.
Download
http://goo.gl/CPTQOf
How to use
1. Download file seccfg.img above
2. Download TWRP or CWM or PhilZ, if you don't already have it
3. Enter fastboot mode
4. Boot custom recovery
Code:
fastboot boot <path/to/custom/recovery/file.img>
5. After entering custom recovery, push my seccfg.img to internal memory:
Code:
adb push seccfg.img /sdcard/
6. (Optional) Do a backup to your original seccfg before overwriting it:
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/by-name/seccfg of=/sdcard/seccfg_original.img
7. Overwrite the seccfg:
Code:
adb shell dd if=/sdcard/seccfg.img of=/dev/block/platform/mtk-msdc.0/by-name/seccfg
8. And you are done.
To check wether your warranty bit is back or not, back to fastboot and type this command:
Code:
fastboot getvar all
Alternative method using fastboot
After downloading, enter fastboot mode, and flash the file from there by using:
Code:
fastboot flash seccfg <path/to/seccfg.img>
and you're done.
Yet another alternative method using custom recovery
Just flash attached flashable zip via custom recovery, and you are done.
awaaas said:
So, after searching and asking to no avail, I decided to test it myself, and it works!
After you unlocks your android one device, your warranty bit is set to no, even if you lock it again afterwards.
This may or may not affects your real warranty service. But better safe than sorry.
Download
http://goo.gl/CPTQOf
How to use
1. Download file seccfg.img above
2. Download TWRP or CWM or PhilZ, if you don't already have it
3. Enter fastboot mode
4. Boot custom recovery
Code:
fastboot boot <path/to/custom/recovery/file.img>
5. After entering custom recovery, push my seccfg.img to internal memory:
Code:
adb push seccfg.img /sdcard/
6. (Optional) Do a backup to your original seccfg before overwriting it:
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/by-name/seccfg of=/sdcard/seccfg_original.img
7. Overwrite the seccfg:
Code:
adb shell dd if=/sdcard/seccfg.img of=/dev/block/platform/mtk-msdc.0/by-name/seccfg
8. And you are done.
To check wether your warranty bit is back or not, back to fastboot and type this command:
Code:
fastboot getvar all
Click to expand...
Click to collapse
Yea It Works!
help
can any one help me how to do this process..icant understand how to proceed
rahuldasari12 said:
can any one help me how to do this process..icant understand how to proceed
Click to expand...
Click to collapse
I thiink its not that important to get the warranty back (at least on Indian variants) as flashing the stock ROM via SP flash tools of fastboot does the job. Interesting procedure by the way.......
rahuldasari12 said:
can any one help me how to do this process..icant understand how to proceed
Click to expand...
Click to collapse
I think it is pretty straightforward
Saurabh K said:
I thiink its not that important to get the warranty back (at least on Indian variants) as flashing the stock ROM via SP flash tools of fastboot does the job. Interesting procedure by the way.......
Click to expand...
Click to collapse
There's currently no checking either here in Indonesia, but better safe than sorry
Again, why would you want your warranty, there is a solution of any problem on XDA ....
Sent from my Sparkle V
Saurabh K said:
Again, why would you want your warranty, there is a solution of any problem on XDA ....
Sent from my Sparkle V
Click to expand...
Click to collapse
Some problems are simply not resolvable by us, for example, in this video, the phone's light sensor is broken, can you repair it by yourself? No, and reflashing the phone doesn't help. You still needs the warranty service for something that outside your reach/knowledge.
Any manufacturing defect is always the responsibility of the company and any hardware damage done intentionally is not covered under warranty if I'm right. I appreciate your work and of course I'm not arguing.
Sent from my Sparkle V
Will it work for 8 gb devices too ?
DarkHeart Z said:
Will it work for 8 gb devices too ?
Click to expand...
Click to collapse
Yes, I personally tested this on 8 GB device.
awaaas said:
Yes, I personally tested this on 8 GB device.
Click to expand...
Click to collapse
Thanks a lot lot much more bro you guys have made our day easier than ever
awaaas said:
Yes, I personally tested this on 8 GB device.
Click to expand...
Click to collapse
And one last thing I need to know . I booted into twrp but adb is not working can I know why ?
DarkHeart Z said:
And one last thing I need to know . I booted into twrp but adb is not working can I know why ?
Click to expand...
Click to collapse
Check your device manager, maybe your device isn't yet installed properly. Install the driver manually if that actually the case.
awaaas said:
Check your device manager, maybe your device isn't yet installed properly. Install the driver manually if that actually the case.
Click to expand...
Click to collapse
Checked . No missing driver showed . same thing happened with sp flash tool too . but later after 1st unlocking bootloader driver got recognized . I am wondering if it is the cause .
DarkHeart Z said:
Checked . No missing driver showed . same thing happened with sp flash tool too . but later after 1st unlocking bootloader driver got recognized . I am wondering if it is the cause .
Click to expand...
Click to collapse
I have updated the original post with flashable zip, just flash it via your custom recovery, and you should be done.
awaaas said:
I have updated the original post with flashable zip, just flash it via your custom recovery, and you should be done.
Click to expand...
Click to collapse
Thanks bro . Will you create a flashable zip for backing up orginal seccfg ? please . since I cannot access adb from recovery so it will be really helpful for all of us
Edit : Latest twrp has this kickass feature called terminal command . this fixed my problem . I backed up my original seccfg with it .
Edit : Bro the the person who modified the recovery actually broked the adb and many other features too . I used @1cefire 's recovery and everything is perfect there . just like mini android os in recovery .
Thank you very much for this, I made my own seccfg backup after reading this thread, and I'm glad I did. I managed to restore it as well. No need to worry anymore about warranty
Related
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.
Hello everyone,
I'm in a little trouble. I need to install custom recovery on my Xperia SP C5302 but I have no PC.
How can I install TWRP ( preferred ) / CWM/Philz on my device ? Is there any way ?
Thank You.
Note : There's a cyber cafe beside my house. But all their computers are running Windows XP.
If there's no way to install without PC then can I be able to install custom recovery on my device with Win XP ?
Thanks again.
Do you have root?
TechnoSparks said:
Do you have root?
Click to expand...
Click to collapse
Yes I'm rooted and my bootloader is unlocked.
Are you ready to bear any risks?
TechnoSparks said:
Are you ready to bear any risks?
Click to expand...
Click to collapse
Yes I'm. but what kinda risk ? soft brick ? or something else ?
rhrokib said:
Yes I'm. but what kinda risk ? soft brick ? or something else ?
Click to expand...
Click to collapse
Most likely soft brick. But who knows, hard bricks even happen when they never touched anything for some people.
TechnoSparks said:
Most likely soft brick. But who knows, hard bricks even happen when they never touched anything for some people.
Click to expand...
Click to collapse
okay. Is there any way to install TWRP without PC then ?
or any custom recovery. philz, CWM anything
Install a terminal emulator by Jake Pelvich from Play store.
Extract the official TWRP img from the TWRP fota zip, or, if you already downloaded an official img, put it into the root of your internal storage.
For ease of access, but still mnemonic, rename the img into "twrp.img"
Open your terminal emulator, and enter "su" and run. This will make the terminal to request root, as you're elevating the shell into root.
Now, we "dd" the TWRP image into your FOTA partition. Copy and run the following:
Code:
dd if=/storage/emulated/0/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel bs=4096
Reboot to check if recovery is accessible after hitting volume up when LED lights up
TechnoSparks said:
Install a terminal emulator by Jake Pelvich from Play store.
Extract the official TWRP img from the TWRP fota zip, or, if you already downloaded an official img, put it into the root of your internal storage.
For ease of access, but still mnemonic, rename the img into "twrp.img"
Open your terminal emulator, and enter "su" and run. This will make the terminal to request root, as you're elevating the shell into root.
Now, we "dd" the TWRP image into your FOTA partition. Copy and run the following:
Reboot to check if recovery is accessible after hitting volume up when LED lights up
Click to expand...
Click to collapse
Thanks a lot. Maybe it works. But how to boot into recovery ?
explain me please.
rhrokib said:
Thanks a lot. Maybe it works. But how to boot into recovery ?
explain me please.
Click to expand...
Click to collapse
Like already mentioned, press volume button UP when the LED lights up during your XSP bootup
TechnoSparks said:
Like already mentioned, press volume button UP when the LED lights up during your XSP bootup
Click to expand...
Click to collapse
There is no LED during bootup. Either I didn't understand. I tried with software to boot into recovery. But my device just complete a reboot everytime. What to do ?
rhrokib said:
There is no LED during bootup. Either I didn't understand. I tried with software to boot into recovery. But my device just complete a reboot everytime. What to do ?
Click to expand...
Click to collapse
What ROM are you using? You need a ROM that can boot a FOTAKernel recovery, and not all of them can (especially stock based ones, since stock by default doesn't allow this).
Ditto.
If you are not using a ROM that supports booting from TWRP, then I can't suggest a method to install other recoveries without a PC.
I do not say it is impossible though, but it'll take a lot of brain power, and moderate understanding of shell scripting in order to reverse engineer the other recoveries provided in the dev subforum.
TechnoSparks said:
Ditto.
If you are not using a ROM that supports booting from TWRP, then I can't suggest a method to install other recoveries without a PC.
I do not say it is impossible though, but it'll take a lot of brain power, and moderate understanding of shell scripting in order to reverse engineer the other recoveries provided in the dev subforum.
Click to expand...
Click to collapse
I tried with Terminal Emulator and it seems okay. But I can't boot into recovery. Tried a lot of process. Doesn't work. Now can I install TWRP with pc ? or I need to flash my stock back to install from PC as I replaced my stock img file ?
Again if I flash stock now, will my bootloader be locked again ?
rhrokib said:
I tried with Terminal Emulator and it seems okay. But I can't boot into recovery. Tried a lot of process. Doesn't work. Now can I install TWRP with pc ? or I need to flash my stock back to install from PC as I replaced my stock img file ?
Again if I flash stock now, will my bootloader be locked again ?
Click to expand...
Click to collapse
Like already explained by Tomoms and me, you need a ROM that supports booting recovery from the FOTA partition in order for my explained method to work. You didn't also tell us which ROM you are using.
No, you dont need to flash your stock back. Leaving the FOTA partition replaced does no absolute harm at all.
If you flash stock, your bootloader will still remain unlocked. In order to relock, you will need to explicitly relock it, by using the relock bootloader option provided by flashtool. If you backed up your TA partition, restoring it will automatically relock your bootloader.
TechnoSparks said:
Like already explained by Tomoms and me, you need a ROM that supports booting recovery from the FOTA partition in order for my explained method to work. You didn't also tell us which ROM you are using.
No, you dont need to flash your stock back. Leaving the FOTA partition replaced does no absolute harm at all.
If you flash stock, your bootloader will still remain unlocked. In order to relock, you will need to explicitly relock it, by using the relock bootloader option provided by flashtool. If you backed up your TA partition, restoring it will automatically relock your bootloader.
Click to expand...
Click to collapse
Okay thanks everyone. I finally installed TWRP, CWM as well as Philz.
I was using 4.3 Stock. Finally installed those from Doomlord's thread. That was really handy to use.
again thank you all for supporting me.
rhrokib said:
Okay thanks everyone. I finally installed TWRP, CWM as well as Philz.
I was using 4.3 Stock. Finally installed those from Doomlord's thread. That was really handy to use.
again thank you all for supporting me.
Click to expand...
Click to collapse
Alright, good to know you finally installed the recoveries. 4.3 Stock ROM does not support my method explained in my recent post. And no problem!
So, I have decided on rooting my Xperia Z3 Compact so that I can finally move OBB to SD card, however I have no knowledge of how roots work (not a programmer much), or which one to pick. I have seen quite a few options for different roots, and previously used Kingo root, but seeing the post about it I am avoiding it like a forest fire. Anyone got good suggestions on which one to pick for my Xperia z3 compact?
In modern Android the phone's security systems prevent rooting via one click apps unless the device is unlocked. The best/safest way to root is to flash custom recovery such as TWRP and then install SuperSU.zip from TWRP. Make sure you make a backup first just in case.
You will most likely have to unlock your bootloader before you can flash TWRP. SONY devices are usually pretty Dev friendly, so you shouldn't have too much trouble finding everything you need. Good luck.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
In modern Android the phone's security systems prevent rooting via one click apps unless the device is unlocked. The best/safest way to root is to flash custom recovery such as TWRP and then install SuperSU.zip from TWRP. Make sure you make a backup first just in case.
You will most likely have to unlock your bootloader before you can flash TWRP. SONY devices are usually pretty Dev friendly, so you shouldn't have too much trouble finding everything you need. Good luck.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Erm can you explain it so that I will understand it? XD
I kind of understand what you mean but I am still confused here and there....
GarrusN7 said:
Erm can you explain it so that I will understand it? XD
I kind of understand what you mean but I am still confused here and there....
Click to expand...
Click to collapse
Your phone has a recovery. When you bought it, it came with the factory (or stock) recovery. Stock recoveries will only let you flash certain signed zip files and not all (for example - your ota updates). So you need to shift to a custom recovery that will let you flash any file you want. Custom recoveries are device specific. Search how to flash it in your phone. Common ones are - TWRP, cwm, philz.
Once you have your new recovery set up, you are ready to root it. All you have to do is use the recovery to flash the supersu file (i recommend chainfire). If you have twrp installed, the flashable su file is a part of it, and it will guide you.
Reboot after done, and supersu will prompt you to update your su binaries, done. you are all set. Dont forget to unlock the bootloader.
Your warranty will be void unless you revert all changes. Not at all complicated, you do it once and get the hang of it.
A short note on flashing: Flashing is replacing (or installing) certain system files. You can tweak your system in any way you like (overclocking, changing animations, installing apps or scripts, changing the os, etcetera ). Just make sure the zips you flash are compatible.
RealWelder said:
In modern Android the phone's security systems prevent rooting via one click apps unless the device is unlocked. The best/safest way to root is to flash custom recovery such as TWRP and then install SuperSU.zip from TWRP. Make sure you make a backup first just in case.
You will most likely have to unlock your bootloader before you can flash TWRP. SONY devices are usually pretty Dev friendly, so you shouldn't have too much trouble finding everything you need. Good luck.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
dev.kasibhatla said:
Your phone has a recovery. When you bought it, it came with the factory (or stock) recovery. Stock recoveries will only let you flash certain signed zip files and not all (for example - your ota updates). So you need to shift to a custom recovery that will let you flash any file you want. Custom recoveries are device specific. Search how to flash it in your phone. Common ones are - TWRP, cwm, philz.
Once you have your new recovery set up, you are ready to root it. All you have to do is use the recovery to flash the supersu file (i recommend chainfire). If you have twrp installed, the flashable su file is a part of it, and it will guide you.
Reboot after done, and supersu will prompt you to update your su binaries, done. you are all set. Dont forget to unlock the bootloader.
Your warranty will be void unless you revert all changes. Not at all complicated, you do it once and get the hang of it.
A short note on flashing: Flashing is replacing (or installing) certain system files. You can tweak your system in any way you like (overclocking, changing animations, installing apps or scripts, changing the os, etcetera ). Just make sure the zips you flash are compatible.
Click to expand...
Click to collapse
Is chain fire part of Super Su or do you mean instead of it? And what do you mean unlock bootloader???
GarrusN7 said:
Is chain fire part of Super Su or do you mean instead of it? And what do you mean unlock bootloader???
Click to expand...
Click to collapse
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the maximum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
dev.kasibhatla said:
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the mazimum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
Click to expand...
Click to collapse
Thanks. Tho I am sure once I get hands on to it, I will know what to do. Can't wait to move those damned OBB Xd
Just be aware that by unlocking the bootloader you are going to lose camera quality. That's because the keys for image processing are deleted. I think it's only noticeable in low light situations, but still important to know, because once lost those keys will never come back. Therefore I'd rather recommend this rooting method:
https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
fab_ben said:
Just be aware that by unlocking the bootloader you are going to lose camera quality. That's because the keys for image processing are deleted. I think it's only noticeable in low light situations, but still important to know, because once lost those keys will never come back. Therefore I'd rather recommend this rooting method:
https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Click to expand...
Click to collapse
I woundn't recommend this anymore...
Use this one from russel5 - this is for stock rom and locked bootloader - and for staying at looked bootloader...
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This is an noob-save tut which uses russel5's way...
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
fluffi444 said:
I woundn't recommend this anymore...
Use this one from russel5 - this is for stock rom and locked bootloader - and for staying at looked bootloader...
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This is an noob-save tut which uses russel5's way...
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
Click to expand...
Click to collapse
What he/she says. Sorry, I totally forgot about that method, it's much easier, thank you!
dev.kasibhatla said:
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the maximum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
Click to expand...
Click to collapse
Well ****....my root doesn't work. I am using SuperSu and TWRP but for some reason a ram disk extraction fails and no install...is it because I have systemless version of my phone or whatever keeps popping up???? And how do I fix that crap???
dev.kasibhatla said:
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the maximum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
Click to expand...
Click to collapse
fluffi444 said:
I woundn't recommend this anymore...
Use this one from russel5 - this is for stock rom and locked bootloader - and for staying at looked bootloader...
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This is an noob-save tut which uses russel5's way...
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
Click to expand...
Click to collapse
I unlocked the boot loader the official way (Sony guide and ****). I didn't want to brick my phone accidently.
GarrusN7 said:
I unlocked the boot loader the official way (Sony guide and ****). I didn't want to brick my phone accidently.
Click to expand...
Click to collapse
You wouldn't have bricked your phone
If you followed instructions on their site and contacted them, like unlocking htc bootloader, congratulations, your warranty is officially void.
If you didn't contact them in any wau or uploaded your phone's mac/imei, if you re lock, warranty valid again.
dev.kasibhatla said:
You wouldn't have bricked your phone
If you followed instructions on their site and contacted them, like unlocking htc bootloader, congratulations, your warranty is officially void.
If you didn't contact them in any wau or uploaded your phone's mac/imei, if you re lock, warranty valid again.
Click to expand...
Click to collapse
At least I did this the safe way. Oh well, I never send my phones for repairs as the repairs are always overpriced, my dad fixes everything himself if actually fixable XD.
But my root issue still remains!
GarrusN7 said:
At least I did this the safe way. Oh well, I never send my phones for repairs as the repairs are always overpriced, my dad fixes everything himself if actually fixable XD.
But my root issue still remains!
Click to expand...
Click to collapse
Here's a link from another post. Follow it and check. It should work.
(you've already performed a few of those steps)
link
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?
hello everyone
Buy a Chinese mi8, unlock it waiting for the days that xiaomi tells you.
I installed the global version, and everything works correctly, but I want to change the rom.
I've tried to install TWRP with adb and it's impossible, it tells me the ADB template that OKEY, but never restarts in recovery mode with TWRP, so I can not install magisk, or any rom that is not official.
Is there any way to install a ROM (.zip) without TWRP?, how do I do Root without magisk? Has it happened to anyone?
thanks!
First of all, you're in the wrong section.
Second you should install via fastboot as described a thousand times AND reboot directly to your TWRP image via fastboot command.
The you can flash another from and root it.
Third, I'd like to strongly advice you to do some research about android, flashing etc to make sure that you know what you are doing.... So many people are moaning about bricked devices....
trahzebuck said:
First of all, you're in the wrong section.
Second you should install via fastboot as described a thousand times AND reboot directly to your TWRP image via fastboot command.
The you can flash another from and root it.
Third, I'd like to strongly advice you to do some research about android, flashing etc to make sure that you know what you are doing.... So many people are moaning about bricked devices....
Click to expand...
Click to collapse
Thanks for your help
It's not the first cell phone I've flashed that you're not smart.
I have followed the steps as they are, and as you can see in the image, everything seems to be installed correctly. But whenever I restart in recovery mode, I get the xiaomi no twrp.
Do you know why?
cheteuk said:
Thanks for your help
It's not the first cell phone I've flashed that you're not smart.
I have followed the steps as they are, and as you can see in the image, everything seems to be installed correctly. But whenever I restart in recovery mode, I get the xiaomi no twrp.
Do you know why?
Click to expand...
Click to collapse
You are trying to be smart? Well...
Why didn't you post your exact steps with fastboot in the first post?
Now it's clear what you did wrong. I already expected it. And you did NOT read what I wrote:
You are rebooting your device with fastboot reboot. In this case your twrp is wiped out by the XIAOMI recovery. Use: fastboot boot yourimagename.
btw, why are you using such an old TWRP? You won't be able to flash actual roms.
So I'd like to come back to my advice in the first answer....
cheteuk said:
Thanks for your help
It's not the first cell phone I've flashed that you're not smart.
I have followed the steps as they are, and as you can see in the image, everything seems to be installed correctly. But whenever I restart in recovery mode, I get the xiaomi no twrp.
Do you know why?
Click to expand...
Click to collapse
fastboot boot recovery.img
not fastboot reboot
Sent from my MI 8 using Tapatalk
Vuska said:
fastboot boot recovery.img
not fastboot reboot
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
I've tried twrp-3.3.1-0-dipper too, and fastboot boot xxxx.img.
And it hasn't been restarted either.
cheteuk said:
I've tried twrp-3.3.1-0-dipper too, and fastboot boot xxxx.img.
And it hasn't been restarted either.
Click to expand...
Click to collapse
Use the all in one tool, to remove encryption and flash a compatible TWRP.
tsongming said:
Use the all in one tool, to remove encryption and flash a compatible TWRP.
Click to expand...
Click to collapse
What is the all in one tool?
cheteuk said:
What is the all in one tool?
Click to expand...
Click to collapse
Try this. There is all you need.
https://tradingshenzhen.com/de/cont...sh-tutorial-global-firmware-xiaomieu-firmware
Upps, in German. You can choose English.
Goalach said:
Try this. There is all you need.
https://tradingshenzhen.com/de/cont...sh-tutorial-global-firmware-xiaomieu-firmware
Upps, in German. You can choose English.
Click to expand...
Click to collapse
Thanks for the help.
But all the steps that indicate, I have passed them and I never install the TWRP correctly.
1. my mobile phone is unlocked (with the padlock open)
2. I have the official rom installed
3. I try to install twrp with all the commands you have told me, and I never restart the mobile with twrp. I've tried new, intermediate and older versions. and nothing
Is there any way to install an unofficial rom without TWRP?
cheteuk said:
Thanks for the help.
But all the steps that indicate, I have passed them and I never install the TWRP correctly.
1. my mobile phone is unlocked (with the padlock open)
2. I have the official rom installed
3. I try to install twrp with all the commands you have told me, and I never restart the mobile with twrp. I've tried new, intermediate and older versions. and nothing
Is there any way to install an unofficial rom without TWRP?
Click to expand...
Click to collapse
You can't flash a ROM without TWRP and Magisk is the only way you can root your phone that I know of. If you don't even know these simple things/haven't done simple research you might risk to softbrick or even hardbrick your new and shiny phone. There are many guides on how to flash TWRP but you can PM me if you want more help.
Also you don't install TWRP with adb, you need to use fastboot...
cheteuk said:
What is the all in one tool?
Click to expand...
Click to collapse
The number 1 result
http://bfy.tw/Nvtb
You can try this
Make sure you have activated the usb debugging in developer options.
1. Download the tools from here: bit.ly/FlashToolMi8
2. Install the minimal_adb_fastboot_v1.3.1_setup
3. Copy the twrp-3.2.3-0-dipper.img to Minimal ADB and Fastboot Folder
4. Turn off your phone completely. then press power button + volume down to boot in fastboot mode.
5. Run CMD as Administrator then cd to the installed Minimal ADB and Fastboot folder. (Ex: cd C:\Program Files (x86)\Minimal ADB and Fastboot)
6. Use this command on your cmd: fastboot flash recovery twrp-3.2.3-0-dipper.img
7. Then: fastboot boot twrp-3.2.3-0-dipper
8. And: fastboot reboot recovery
9. You're now in twrp recovery mode
10. Copy Disable_Dm-Verity_FEC_v1.1 and Magisk-v18.1 to your phone
11. Install Disable_Dm-Verity_FEC_v1.1 from twrp
12. Then install Magisk-v18.1
13. Reboot, Your phone now rooted