This is the root method I used on my A21s.
Must Have: Unlocked Bootloader.
YOU CAN FIND THE FIRMWARE YOU NEED ON SAMMOBILE OR FRIJA. SAMMOBILE WILL SEVERAL VERSIONS FOR YOUR DEVICE, FRIJA WILL ONLY HAVE THE LATEST VERSION.
1. Download the firmware for your device.
2.Load Zarchiver from playstore.
3.Open Zarchiver and locate the firmware you downloaded.
4.Click on the firmware, a menu will appear at the bottom. You will then have option to extract.
5. The only file we need is .AP
6.Click on AP file and rename AP_xxx.md5 to AP_.tar so your just highlighting the file and removing md5 so it only says .tar at the end.
7.Once you have renamed AP file click and again you will be given the option to extract. Once extracted, locate boot.img.lz4
8.Then extract boot.img.lz4 leaving you with boot.img
9.You should have Magisk manager installed on device. Use Magisk to patch the boot.img. once patched locate magisk_patched.img and rename to boot.img
10.Return to Zarchiver locate the patched boot.img and compress to boot.tar.
11. Move compressed boot.tar to computer and rename to boot.img.tar
12.Put device in download mode, open odin 3.14.4 and put the boot.img.tar in AP and click start. Once odin says pass, your device will boot to stock recovery and you will have to do a factory reset so save anything you need before doing this.
13.once device boots reinstall Magisk manager and follow prompts. You should now have a rooted device.
Have Fun.
Can you verify if usb connection is working with this method...i did follow a thread titled "root possibility" and someone succeeded but usb was not working when connected to computer was the only catch.
cldkrs said:
This is the root method I used on my A21s.
Must Have: Unlocked Bootloader.
YOU CAN FIND THE FIRMWARE YOU NEED ON SAMMOBILE OR FRIJA. SAMMOBILE WILL SEVERAL VERSIONS FOR YOUR DEVICE, FRIJA WILL ONLY HAVE THE LATEST VERSION.
1. Download the firmware for your device.
2.Load Zarchiver from playstore.
3.Open Zarchiver and locate the firmware you downloaded.
4.Click on the firmware, a menu will appear at the bottom. You will then have option to extract.
5. The only file we need is .AP
6.Click on AP file and rename AP_xxx.md5 to AP_.tar so your just highlighting the file and removing md5 so it only says .tar at the end.
7.Once you have renamed AP file click and again you will be given the option to extract. Once extracted, locate boot.img.lz4
8.Then extract boot.img.lz4 leaving you with boot.img
9.You should have Magisk manager installed on device. Use Magisk to patch the boot.img. once patched locate magisk_patched.img and rename to boot.img
10.Return to Zarchiver locate the patched boot.img and compress to boot.tar.
11. Move compressed boot.tar to computer and rename to boot.img.tar
12.Put device in download mode, open odin 3.14.4 and put the boot.img.tar in AP and click start. Once odin says pass, your device will boot to stock recovery and you will have to do a factory reset so save anything you need before doing this.
13.once device boots reinstall Magisk manager and follow prompts. You should now have a rooted device.
Have Fun.
Click to expand...
Click to collapse
Since you stressed that need an unlock boot loader device, you can include links of tutorials how unlock the boot loader or how to tell if our bootloader is unlocked. Is it as simple as toggling "OEM UNLOCK" in developer settings? A21s runs Android 10. What version of magisk you recommend to download and to flash? Pics? Screenshots? Videos?
You said magisk manager should be installed in the device to patch the boot, isn't the app will say magisk not installed when we open the manager app? Or we need to do this step using another phone thats rooted with magisk installed?
Thanks a lot for posting this have a nice day
Bro can you post boot.img.tar. Root patched which you are flshed in your phone
And also plz send AP of your phone
Plz bro upload root file.
Jbazt_katuforzs said:
Since you stressed that need an unlock boot loader device, you can include links of tutorials how unlock the boot loader or how to tell if our bootloader is unlocked. Is it as simple as toggling "OEM UNLOCK" in developer settings? A21s runs Android 10. What version of magisk you recommend to download and to flash? Pics? Screenshots? Videos?
You said magisk manager should be installed in the device to patch the boot, isn't the app will say magisk not installed when we open the manager app? Or we need to do this step using another phone thats rooted with magisk installed?
Thanks a lot for posting this have a nice day
Click to expand...
Click to collapse
Bro can you upload boot.img.tar Root file on xda plz and don't forget to mention AP version
Plz bro plz upload
cldkrs said:
This is the root method I used on my A21s.
Must Have: Unlocked Bootloader.
YOU CAN FIND THE FIRMWARE YOU NEED ON SAMMOBILE OR FRIJA. SAMMOBILE WILL SEVERAL VERSIONS FOR YOUR DEVICE, FRIJA WILL ONLY HAVE THE LATEST VERSION.
1. Download the firmware for your device.
2.Load Zarchiver from playstore.
3.Open Zarchiver and locate the firmware you downloaded.
4.Click on the firmware, a menu will appear at the bottom. You will then have option to extract.
5. The only file we need is .AP
6.Click on AP file and rename AP_xxx.md5 to AP_.tar so your just highlighting the file and removing md5 so it only says .tar at the end.
7.Once you have renamed AP file click and again you will be given the option to extract. Once extracted, locate boot.img.lz4
8.Then extract boot.img.lz4 leaving you with boot.img
9.You should have Magisk manager installed on device. Use Magisk to patch the boot.img. once patched locate magisk_patched.img and rename to boot.img
10.Return to Zarchiver locate the patched boot.img and compress to boot.tar.
11. Move compressed boot.tar to computer and rename to boot.img.tar
12.Put device in download mode, open odin 3.14.4 and put the boot.img.tar in AP and click start. Once odin says pass, your device will boot to stock recovery and you will have to do a factory reset so save anything you need before doing this.
13.once device boots reinstall Magisk manager and follow prompts. You should now have a rooted device.
Have Fun.
Click to expand...
Click to collapse
Bro can you post boot.img.tar. Root patched which you are flshed in your phone
And also plz send AP of your phone
Plz bro upload root file.
Jbazt_katuforzs said:
Since you stressed that need an unlock boot loader device, you can include links of tutorials how unlock the boot loader or how to tell if our bootloader is unlocked. Is it as simple as toggling "OEM UNLOCK" in developer settings? A21s runs Android 10. What version of magisk you recommend to download and to flash? Pics? Screenshots? Videos?
You said magisk manager should be installed in the device to patch the boot, isn't the app will say magisk not installed when we open the manager app? Or we need to do this step using another phone thats rooted with magisk installed?
Thanks a lot for posting this have a nice day
Click to expand...
Click to collapse
I post another tutorial how to unlock bootloader.
nikhilsony91 said:
Bro can you post boot.img.tar. Root patched which you are flshed in your phone
And also plz send AP of your phone
Plz bro upload root file.
Click to expand...
Click to collapse
Download the firmware and Follow the tutorial!
Can you post what magisk manager you used? I followed the procedure exactly amd to be sure that its my firmware i flashed a full sammobile firmware that went smoothly and patched the AP from that. But I end up on a loop of red msg like an error. Is the something i missing ?
what magisk manager version did you use? also why not post the patched file directly here, can you post screenshots that show magisk saying it works?
cldkrs said:
This is the root method I used on my A21s.
Click to expand...
Click to collapse
DONT use this RootMethod.
It is NOT possible until NOW, to root the A21s.
There is NO compatible Magisk and / or TWRP - Version out for the A21s.
This Methode is Bull**** ... There are many Methods on other Websites and YT - Video: ALL are NOT working ... They want only Visitors and Followers.
!!! U CANT ROOT THE A21s NOW !!!
MaBo2020 said:
DONT use this RootMethod.
It is NOT possible until NOW, to root the A21s.
There is NO compatible Magisk and / or TWRP - Version out for the A21s.
This Methode is Bull**** ... There are many Methods on other Websites and YT - Video: ALL are NOT working ... They want only Visitors and Followers.
!!! U CANT ROOT THE A21s NOW !!!
Click to expand...
Click to collapse
honestly i'd agree with you, but again, i don't think this person is asking for any sort of visitors or views, plus he's not linking anything ( like a youtube video or wesbite)
I private messaged him to ask for further explanation and awaiting his reply on the matter
Throwaway97 said:
honestly i'd agree with you, but again, i don't think this person is asking for any sort of visitors or views, plus he's not linking anything ( like a youtube video or wesbite)
I private messaged him to ask for further explanation and awaiting his reply on the matter
Click to expand...
Click to collapse
... again: CURRENTLY U CANT WITH ANY METHODE ROOT A "SAMSUNG - A21S", because there is NO working Magisk and / or TWRP - Version, same with SuperUser etc.
Go on the MAGISK or TWRP Website, u doesnt find a working Version for the A21s. He will send u nothing or Bull**** !
If u try his Methode or use his Bull****, u risk a Break !
U will find many Methodes in WWW, but this all are NOT working Methodes.
If u find one, u will be a Hero for ALL A21s User
Jbazt_katuforzs said:
Can you post what magisk manager you used? I followed the procedure exactly amd to be sure that its my firmware i flashed a full sammobile firmware that went smoothly and patched the AP from that. But I end up on a loop of red msg like an error. Is the something i missing ?
Click to expand...
Click to collapse
he can not ... Go on the MAGISK or TWRP Website, u doesnt find a working Version for the A21s.
Throwaway97 said:
what magisk manager version did you use? also why not post the patched file directly here, can you post screenshots that show magisk saying it works?
Click to expand...
Click to collapse
Go on the MAGISK or TWRP Website, u doesnt find a working Version for the A21s. he tells bull****
MaBo2020 said:
Go on the MAGISK or TWRP Website, u doesnt find a working Version for the A21s. he tells bull****
Click to expand...
Click to collapse
Wenn du meinst.
Translation: If you think.
cldkrs said:
Wenn du meinst.
Translation: If you think.
Click to expand...
Click to collapse
... ach, du bist deutscher, moin !
ich erzähle dir hier keinen mist, selbst XDA hat in Moment keine erfolgreiche Methode, um das A21s zu rooten. Und es gibt auch keine Version von TWRP, SuperUser und MAGISK, die auf dem A21s laufen. Die Anleitungen, die du überall siehst, sind NICHT für das aktuelle A21s, schon garnicht für die EuropaVersion des SmartPhones.
Das ist nicht bös gemeint, sondern die Wahrheit. Du wirst keine Methode finden, die zum RootErfolg führt ...
Bleib gesund
TRANSLATION:
... oh, you are German, moin!
I'm not telling you a crap here, even XDA currently has no successful method to root the A21s. And there are also no versions of TWRP, SuperUser and MAGISK that run on the A21s. The instructions that you see everywhere are NOT for the current A21s, certainly not for the European version of the smartphone.
That is not meant badly, but the truth. You will not find a method that leads to root success ...
Stay healthy
cldkrs said:
Wenn du meinst.
Translation: If you think.
Click to expand...
Click to collapse
hello, i want to tell you that i got a A20 phone a year or so ago and back then it had no root, but i managed to root it with without TWRP ( i never had TWRP on the phone ) and i also rooted it despite everyone saying no method worked, just by patching some files
im going to be honesty with you, i have already forgotten how i did it but i think it can work
i'll try soon
MaBo2020 said:
... ach, du bist deutscher, moin !
ich erzähle dir hier keinen mist, selbst XDA hat in Moment keine erfolgreiche Methode, um das A21s zu rooten. Und es gibt auch keine Version von TWRP, SuperUser und MAGISK, die auf dem A21s laufen. Die Anleitungen, die du überall siehst, sind NICHT für das aktuelle A21s, schon garnicht für die EuropaVersion des SmartPhones.
Das ist nicht bös gemeint, sondern die Wahrheit. Du wirst keine Methode finden, die zum RootErfolg führt ...
Bleib gesund
TRANSLATION:
... oh, you are German, moin!
I'm not telling you a crap here, even XDA currently has no successful method to root the A21s. And there are also no versions of TWRP, SuperUser and MAGISK that run on the A21s. The instructions that you see everywhere are NOT for the current A21s, certainly not for the European version of the smartphone.
That is not meant badly, but the truth. You will not find a method that leads to root success ...
Stay healthy
Click to expand...
Click to collapse
darum hab ich meins auch gerootet, Europa Version - MediaMarkt.
Translation: that's why I rooted mine, Europe Version - MediaMarkt.
cldkrs said:
darum hab ich meins auch gerootet, Europa Version - MediaMarkt.
Translation: that's why I rooted mine, Europe Version - MediaMarkt.
Click to expand...
Click to collapse
... wenn du deins ANGEBLICH gerootet hast, mach doch mal eine genauen Beschreibung für Alle hier, Schritt-für-Schritt mit exakter FirmwareVersion, welche Version von MAGISK und TWRP (am besten alles mit DownloadLink) gepachter MagiskDatei und am besten noch Screenshots von deinem gerooteten Handy.
Das kannst Du aber nicht, weils Bull**** ist, was Du hier erzählst oder es ein SmartPhone ist, welches Du vor Jahren gekauft hast. Die heutigen A21s lassen sich NICHT rooten, egal, welcher angebliche RootBlödsinn hier oder woanders erzählt wird.
KEINER bietet auch deswegen Links (exakter Firmware zB. exackte Version von TWRP, MAGISK, SU) zum direkten runterladen an, weils auch garnicht geht sondern und sie das wohl auchs elber genau wissen. Sie wollen sich nur interesssant machen und Viewer, Likes auf deren Seiten erreichen usw. Immer nur irgendwelche dummen Beschreibungen, wie man es angeblich machen soll, aber Beweise, das es auch wirklich zum Erfolg führt, hat noch keiner im gesamten Internet gezeigt. Alles LaberTaschen ...
Denn komischerweise schreiben immer viele, das sie es gerrotet haben oder eine Methode die klappt, aber nie sendet einer auch irgendeinen Beweis dazu.
Translation: if you allegedly have rooted yours, make a detailed description for everyone here, step-by-step with the exact firmware version, which version of MARGISK and TWRP (preferably everything with a download link) leased Magisk file and screenshots from your rooted mobile phone. Because strangely enough, many always write that they have redeemed it or a method that works, but nobody ever sends any proof.
Related
So guys, here I am, after hours of desperated tentatives and giving up on hope. Today I manually applied an OTA file to update my system to v4.1.2, and it succeeded. Everything worked fine, I restored my protected root with Voodoo OTA RootKeeper, reinstalled Boot Menu and backed everything up.
So I started playing with it and modified some system files. Now I got into a bootloop and somehow it seems that my system partition has been formated, cause I lost access to Boot Menu. I can acess stock recovery, but cannot apply the OTA file again cause I deleted a system *.apk and the asserting fails, so the update cannot be applied. I tried to modify the patching files in the OTA *.zip file, but it also fails, probably due to signature or integrity checking.
My phone already got into low battery status, so I'll spend the rest of the night trying to charge it, but I need help figuring out how to restore my system. I think I have left two possibilites:
1. Restoring system partition from a v4.0.4 fasboot file using moto-fastboot commands - I know cdt.bin was updated to a higher version so I can't flash a lower version, but perhaps I can grab the cdt.bin_signed from the OTA file to replace the one within the fastboot file, or something like this, so I can flash the package. It doesn't need to boot, I just need to restore the system partition so I can apply the OTA file again to get a working v4.1.2 system.
2. Erasing my cid. Some weeks ago I made a backup of my cid. Perhaps I can erase it through fastboot so I can flash a fastboot file for v4.1.2, cause here in LATAM region we currently only have an OTA avaliable. That's my last option, cause I'm assuming I'll no longer be able to have root access for now, so I won't be able to install Boot Menu. Handling a system without cid this way might get painful... But at least it's an option, it may work.
Any help would be really appreciated. Right now I'm trying to fastboot flash system system_signed, but it's failing, due to low battery and something related to preflash validation failure, which I can't exactly tell the reason. The same happened to fastboot flash boot. In the other hand, fastboot flash preinstall preinstall and fastboot flash recovery recovery_signed worked fine. But I'm kinda lost here...
Thanks in advance.
Here's what you need to do:
You need the system_signed out of the necessary Latam ICS Fastboot to flash this Leak.
Do it similar to this Thread
http://forum.xda-developers.com/showthread.php?p=39247094
Your Boot. img should still be on Latam JB. If it's damaged, someone who's running the Latam JB with Root & BMM installed should backup his Boot. img and upload it for you.
So:
Fastboot the Latam ICS system_signed
Fastboot the Latam JB Boot. img (if needed)
wipe Data / Cache & apply the OTA in the Recovery again.
To charge your Phone, try to turn it off > connect your Wall charger > Boot in AP and let it sit there while still connected to your Wall Charger for about an hour. If you got luck it will charge.
Gesendet von meinem XT890 mit Tapatalk 2
---------- Post added at 06:52 AM ---------- Previous post was at 06:46 AM ----------
BTW: Use the eternity project Moto - fastboot to flash the system_signed, when you fixed your Battery!
Gesendet von meinem XT890 mit Tapatalk 2
HSD-Pilot said:
Here's what you need to do:
You need the system_signed out of the necessary Latam ICS Fastboot to flash this Leak.
Do it similar to this Thread
http://forum.xda-developers.com/showthread.php?p=39247094
Your Boot. img should still be on Latam JB. If it's damaged, someone who's running the Latam JB with Root & BMM installed should backup his Boot. img and upload it for you.
So:
Fastboot the Latam ICS system_signed
Fastboot the Latam JB Boot. img (if needed)
wipe Data / Cache & apply the OTA in the Recovery again.
To charge your Phone, try to turn it off > connect your Wall charger > Boot in AP and let it sit there while still connected to your Wall Charger for about an hour. If you got luck it will charge.
Gesendet von meinem XT890 mit Tapatalk 2
---------- Post added at 06:52 AM ---------- Previous post was at 06:46 AM ----------
BTW: Use the eternity project Moto - fastboot to flash the system_signed, when you fixed your Battery!
Gesendet von meinem XT890 mit Tapatalk 2
Click to expand...
Click to collapse
I will never be able to thank you enough! You saved my phone. It took a whole day to charge it through the universal charger, but now I just flashed everything as you described and flashing the update file within stock recovery worked fine. Now my phone works perfectly. Too bad I lost root and there's no root procedure working on LATAM update yet, but at least I have a phone and let's hope a root method will pop up soon.
I took the script tool you posted earlier and replaced the files with the ones suitable for LATAM region phones so I could use it myself. As it finally worked, would be okay if I uploaded it as a bundle so others around me can use it if they need to? Of course all credits will be given to you.
Thanks in advance.
Ricardo Gonçalves.
Sure, this will help other Guys, like him
http://forum.xda-developers.com/showthread.php?p=40266883
Gesendet von meinem XT890 mit Tapatalk 2
ricardofago said:
I will never be able to thank you enough! You saved my phone. It took a whole day to charge it through the universal charger, but now I just flashed everything as you described and flashing the update file within stock recovery worked fine. Now my phone works perfectly. Too bad I lost root and there's no root procedure working on LATAM update yet, but at least I have a phone and let's hope a root method will pop up soon.
I took the script tool you posted earlier and replaced the files with the ones suitable for LATAM region phones so I could use it myself. As it finally worked, would be okay if I uploaded it as a bundle so others around me can use it if they need to? Of course all credits will be given to you.
Thanks in advance.
Ricardo Gonçalves.
Click to expand...
Click to collapse
friend what were the steps you took? I can send the files you flasheaste your phone, I agredeceria quite as no match for any side and the Latam JB System_signed Boot. img! and my cell takes days in disrepair, you help me a lot if you would send me those files
Esto.Vir said:
friend what were the steps you took? I can send the files you flasheaste your phone, I agredeceria quite as no match for any side and the Latam JB System_signed Boot. img! and my cell takes days in disrepair, you help me a lot if you would send me those files
Click to expand...
Click to collapse
Connect your phone to your PC in AP Fastboot mode and run the unbrick.bat from this package. It will flash the v4.0.4 system and v4.1.2 boot (this requires a LATAM device). Then restart your phone into stock recovery and you'll be able to apply again the update file for v4.1.2 that's supposed to be on your external microSD card (a factory reset and a wipe cache might be appropriated before doing so). When it finishes, reboot and your phone should boot fine, but you will lose all user data and root access.
ricardofago said:
Connect your phone to your PC in AP Fastboot mode and run the unbrick.bat from this package. It will flash the v4.0.4 system and v4.1.2 boot (this requires a LATAM device). Then restart your phone into stock recovery and you'll be able to apply again the update file for v4.1.2 that's supposed to be on your external microSD card (a factory reset and a wipe cache might be appropriated before doing so). When it finishes, reboot and your phone should boot fine, but you will lose all user data and root access.
Click to expand...
Click to collapse
thank you very much friend, I realize all the procedure correctly but when I enter the stock recovery restarts select it, as if there is recovery my phone.
You select Recovery with Vol. up? Don't use Power, this will just restart your Device.
When the Android is shown, hold Vol. down and press Vol. up to enter the Recovery.
Gesendet von meinem XT890
HSD-Pilot said:
You select Recovery with Vol. up? Don't use Power, this will just restart your Device.
When the Android is shown, hold Vol. down and press Vol. up to enter the Recovery.
Gesendet von meinem XT890
Click to expand...
Click to collapse
of how it will restart the phone, I get only the Motorola logo and when I try to enter recovery restarts: Crying:: Crying:: Crying:
Try to fastboot the ICS Recovery back
fastboot flash recovery recovery_signed
Sent from my XT890 using Tapatalk 4 Beta 2
HSD-Pilot said:
Try to fastboot the ICS Recovery back
fastboot flash recovery recovery_signed
Sent from my XT890 using Tapatalk 4 Beta 2
Click to expand...
Click to collapse
lo realize en varias ocaciones y flashea bien , pero al momento de reiniciar el celular muestra el primer logo de motorola dual core y se reinicia , puedo entrar solamente a las opciones de flash mode , pero al momento de seleccionar recovery se reinicia el celular : Crying:: Crying:: Crying:: Crying:: Crying:: Crying:
I did as u said but. On boot i says infopreflash validitation failed........pls help moto razr xt910k
I want to root my desire x and install most stable and good looking ROM. I rooted a sony erricson device but it was real easy unlike HTC. I was reading guides on this forum and got confused regarding recovery, s-off, RUU, kernel, CID etc etc.
Please help me with simple guide and minimum chance to brick my device.
ShivaPower said:
I want to root my desire x and install most stable and good looking ROM. I rooted a sony erricson device but it was real easy unlike HTC. I was reading guides on this forum and got confused regarding recovery, s-off, RUU, kernel, CID etc etc.
Please help me with simple guide and minimum chance to brick my device.
Click to expand...
Click to collapse
I see that u r an xperia survivor, so im gonna explain a few steps.
In HTC, the recovery is not part of the kernel, like sony. HTC has a separate partition where recovery.img is flashed.
Kernel for ROM/OS booting is contained in boot.img and it is flashed in boot partition.
Recovery also contains a copy of kernel (zImage) so it is independant of the boot.img.
To root it, you have to somehow accomplish below steps.
1. Unlock Bootloader for your phone. Go to htcdev.com and search and follow instructions from main page.
2. Reboot phone in "FASTBOOT MODE" and Flash a custom recovery through fastboot.exe tool. Syntax is "fastboot flash recovery recovery.img". Use any available CWM or TWRP (mine). Take care whether you want ICS or JB compatible recovery becoz they work is different.
3. Take a nandroid backup through recovery. (You probably know this as it is same in all phones)
4. Flash a custom ics/jb rom.
5. Reboot phone in FASTBOOT MODE and flash the recommended "boot.img" mentioned in ROMs thread.
Use a little common sense and soon you'll learn doing things the HTC way.
Regards
Yasir
neXus PRIME said:
I see that u r an xperia survivor, so im gonna explain a few steps.
In HTC, the recovery is not part of the kernel, like sony. HTC has a separate partition where recovery.img is flashed.
Kernel for ROM/OS booting is contained in boot.img and it is flashed in boot partition.
Recovery also contains a copy of kernel (zImage) so it is independant of the boot.img.
To root it, you have to somehow accomplish below steps.
1. Unlock Bootloader for your phone. Go to htcdev.com and search and follow instructions from main page.
2. Reboot phone in "FASTBOOT MODE" and Flash a custom recovery through fastboot.exe tool. Syntax is "fastboot flash recovery recovery.img". Use any available CWM or TWRP (mine). Take care whether you want ICS or JB compatible recovery becoz they work is different.
3. Take a nandroid backup through recovery. (You probably know this as it is same in all phones)
4. Flash a custom ics/jb rom.
5. Reboot phone in FASTBOOT MODE and flash the recommended "boot.img" mentioned in ROMs thread.
Use a little common sense and soon you'll learn doing things the HTC way.
Regards
Yasir
Click to expand...
Click to collapse
ThankYou,
I have more questions. Currently i am downloading softwares to unlock bootloader. Sorry if i seem noobish.
On your 2) How to flash a custom recovery and what is flashtool.exe.? any links? Please explain in detail. It was a Shoib akhtar bouncer for me.
3) How to take nandroid backup
4) any links to a functional/stable JB ROM with pure android funcionality?
5) no clue again...any links?
I cant unlock via htc dev it say invalid code lenght? Im on jelly bean 405
Sent from my HTC Desire X using Xparent ICS Tapatalk 2
Cant flash the recovery
When i issue command fastboot flash recovery c:\recovery.img
it is saying cannot flash, unknown error.
I am using cmw6.can you guys give me a latest recovery and also tell how to take nandroid backup of recovery
ShivaPower said:
When i issue command fastboot flash recovery c:\recovery.img
it is saying cannot flash, unknown error.
Click to expand...
Click to collapse
Maybe this help you
http://forum.xda-developers.com/showthread.php?t=2076675
Thats a step by step tutorial from nlooooo
I think you're not in Fastboot mode but I'm not sure.
I am using cmw6.can you guys give me a latest recovery and also tell how to take nandroid backup of recovery
Click to expand...
Click to collapse
If you flashed the recovery, you will find easily the option to make a backup
I use TWRP, so i can't tell you in detail, sorry
0zura
0zura said:
Maybe this help you
http://forum.xda-developers.com/showthread.php?t=2076675
Thats a step by step tutorial from nlooooo
I think you're not in Fastboot mode but I'm not sure.
If you flashed the recovery, you will find easily the option to make a backup
I use TWRP, so i can't tell you in detail, sorry
0zura
Click to expand...
Click to collapse
yea i chose back up from bootloader ans got two files on my phone, recovery.img and boot.img. are they enough to backup. is this backup for stock revovery or cwm ??? the phone is running very good.
but i havnt rooted .i want to install a full sense or any beautiful n stable rom. can you link it here???
ShivaPower said:
yea i chose back up from bootloader ans got two files on my phone, recovery.img and boot.img. are they enough to backup. is this backup for stock revovery or cwm ??? the phone is running very good.
but i havnt rooted .i want to install a full sense or any beautiful n stable rom. can you link it here???
Click to expand...
Click to collapse
You have to chose in bootloader "Recovery"- in Recovery mode (CWM) can you make a backup, not in bootloader
The backup is for cwm
i don't know how many files the backup with cwm had, with TWRP it has 7 files with 1.5 GB
http://tech-lounge.de/nandroid-backup-das-wichtigste-backup-fuer-gerootete-android-geraete/ (german site)
Gesichert wird im Ordner “clockworkmod/backup” auf der SD-Karte und der Dateiname setzt sich aus dem Datum und der aktuellen Uhrzeit zusammen, so dass mehrere Backups parallel abgelegt werden können. Backups haben bei mir allerdings eine Größe von ungefähr 400 MB, also solltet ihr darauf achten, dass ihr genügend internen Speicher zur Verfügung habt.
Click to expand...
Click to collapse
In directory clockworkmod/backup on your SD-Card is the backup file (ca. 400MB) and the name of this file is the date and the time you have create the backup.
The Rom in my signature is a full sense rom. mySENSE-dx RC3.5
So now i have rooted my device. Please point me towards a suitable ROM to install and also the procedure...Waiting for reply.
Thanks to @ScrewTSW he found at http://www.htcmania.com a working TWRP Recovery from totmakina
found : http://www.htcmania.com/showthread.php?p=27398885
to reboot into recovery most elephones works with hold vol+ and power at the same time.
this method dont work for the S8 and i did not found a working method yet.
but its not a problem if you follow this:
for people with stock rom /unrooted
1. download all files and place them on your desktop
2. flash my modified boot.img (magisk root) with flashtools
3. flash TWRP recovery with flashtools
4. reboot the Phone and install magisk manager app (link https://www.apkmirror.com/apk/topjohnwu/magisk-manager/)
5. start magisk manager , it will tell you that your phone has root
6. go to playstore and download the app called reboot recovery ( its a very small app)
7. reboot to recovery.
8. done
9. Now you have twrp and you are able to flash zips or custom roms
TWRP S8 : https://androidfilehost.com/?fid=889964283620766601
Patched Boot.img : https://androidfilehost.com/?fid=673791459329061887
For better and more versatile management, I recommend ROM Manager from ClockWorkMod
skeleton1911 said:
6. go to playstore and download the app called reboot recovery ( its a very small app)
7. reboot to recovery.
8. done
TWRP S8 : https://androidfilehost.com/?fid=889964283620766601
Patched Boot.img : https://androidfilehost.com/?fid=673791459329061887
Click to expand...
Click to collapse
so we need this TWRP S8 only to flash or both ,and i mean this one to Patched Boot.img?
You only need the boot.img if you are not rooted. Because if you flash twrp s8 how would you boot into it?
Hardkeys don't work. So you need to be rooted and download an advanced power menu from playstore like "reboot recovery" to boot into it
Gesendet von meinem S8 mit Tapatalk
skeleton1911 said:
You only need the boot.img if you are not rooted. Because if you flash twrp s8 how would you boot into it?
Hardkeys don't work. So you need to be rooted and download an advanced power menu from playstore like "reboot recovery" to boot into it
Gesendet von meinem S8 mit Tapatalk
Click to expand...
Click to collapse
true..
If I'm rooted and I'm using dragon ROM v2.0, do I just boot into recovery and flash the zips?
OldMidnight said:
If I'm rooted and I'm using dragon ROM v2.0, do I just boot into recovery and flash the zips?
Click to expand...
Click to collapse
Yes .
After you flashed the recovery via flashtools
You can reboot to recovery and flash the rom.zip v2.2 of eragon.
Gesendet von meinem S8 mit Tapatalk
Will flashing TWRP wipe the phone?
Morphior said:
Will flashing TWRP wipe the phone?
Click to expand...
Click to collapse
No
Gesendet von meinem S8 mit Tapatalk
skeleton1911 said:
Thanks to @ScrewTSW he found at http://www.htcmania.com a working TWRP Recovery from totmakina
found : http://www.htcmania.com/showthread.php?p=27398885
to reboot into recovery most elephones works with hold vol+ and power at the same time.
this method dont work for the S8 and i did not found a working method yet.
but its not a problem if you follow this:
for people with stock rom /unrooted
1. download all files and place them on your desktop
2. flash my modified boot.img (magisk root) with flashtools
3. flash TWRP recovery with flashtools
4. reboot the Phone and install magisk manager app (link https://www.apkmirror.com/apk/topjohnwu/magisk-manager/)
5. start magisk manager , it will tell you that your phone has root
6. go to playstore and download the app called reboot recovery ( its a very small app)
7. reboot to recovery.
8. done
9. Now you have twrp and you are able to flash zips or custom roms
TWRP S8 : https://androidfilehost.com/?fid=889964283620766601
Patched Boot.img : https://androidfilehost.com/?fid=673791459329061887
Click to expand...
Click to collapse
To go into the recovery menu, hold down power + volume up+ volume down...it is in chinese tho so not really useful
Nikolay1243D said:
To go into the recovery menu, hold down power + volume up+ volume down...it is in chinese tho so not really useful
Click to expand...
Click to collapse
You enter the test mode with that.
We don't have a solution ATM to enter in recovery mode.
So you have to flash the patched boot.img etc..
Gesendet von meinem S8 mit Tapatalk
skeleton1911 said:
You enter the test mode with that.
We don't have a solution ATM to enter in recovery mode.
So you have to flash the patched boot.img etc..
Gesendet von meinem S8 mit Tapatalk
Click to expand...
Click to collapse
Ah ok..didnt know it was the test mode
Can you help me with the flashtool?
I've "installed" the drivers(it runs the program but then at the end says 3 things failed)
Now I'm in the flash tool and loaded the scatter file but it isnt detecting the phone as connected(probably because of the above)
Nikolay1243D said:
Ah ok..didnt know it was the test mode [emoji14]
Can you help me with the flashtool?
I've "installed" the drivers(it runs the program but then at the end says 3 things failed)
Now I'm in the flash tool and loaded the scatter file but it isnt detecting the phone as connected(probably because of the above)
Click to expand...
Click to collapse
Did you disabled the signature verification of windows?
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
And use / hold vol+ while you plug the phone in (in flashtools)
Gesendet von meinem S8 mit Tapatalk
You can reboot to recovery and flash the rom.zip v2.2 of eragon. Quoted.
Cool, that worked
Magisk isnt passing the ctsProfile on safetynet... do you know how to fix this if at all possible?
Nikolay1243D said:
Cool, that worked
Magisk isnt passing the ctsProfile on safetynet... do you know how to fix this if at all possible?
Click to expand...
Click to collapse
Not possible ATM. But it isn't a problem at all
Gesendet von meinem S8 mit Tapatalk
Yeah I guess I dont use any of the root banned apps/banking apps
You should consider uploading eragon to google drive... I've been downloading it from androidfilehost for the past 45 minutes and there are still about 15 minutes left
Nikolay1243D said:
Yeah I guess I dont use any of the root banned apps/banking apps [emoji14]
You should consider uploading eragon to google drive... I've been downloading it from androidfilehost for the past 45 minutes and there are still about 15 minutes left
Click to expand...
Click to collapse
Next time I will upload it also to Google drive .
But I am counting the download. I can't see them in gdrive
In afh you could also use another mirror.. some of them are slow
Gesendet von meinem S8 mit Tapatalk
Thanks again Skeleton!
Just rooted my phone and flashed TWRP !!!
Works like a charm !!!
Thank you for everything.
Hello,
I am having global MI9 device. I just want to install SuperSU / root on this device with keeping stock ROM, Recovery, Kernel and Firmware alongwith Encryption and Warranty.
Kindly point me the steps which gives a root + stock things i.e. I don't want to install custom Recovery, ROM, Kernel and Firmware, I just want to live root with stock items.
Boot into twrp via fastboot, just don't install it.
https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/
badaas said:
Boot into twrp via fastboot, just don't install it.
https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/
Click to expand...
Click to collapse
You mean if I boot in recovery by this way and flashes SuperSU.zip, it means device is rooted or not? Bootloader must be unlocked before it or no need?
Unlock bootloader, boot twrp, flash magisk/supersu, reboot as normal. Do not install twrp.
Or unlock and extract ROM boot.img, then reboot system install magisk app, and use to patch boot.img.
Then flash boot.img via fastboot.
---------- Post added at 10:15 PM ---------- Previous post was at 10:15 PM ----------
GirishSharma said:
You mean if I boot in recovery by this way and flashes SuperSU.zip, it means device is rooted or not? Bootloader must be unlocked before it or no need?
Click to expand...
Click to collapse
Yes rooted
---------- Post added at 10:18 PM ---------- Previous post was at 10:15 PM ----------
https://forum.xda-developers.com/Mi-9/how-to/tuto-complete-tutorial-to-root-mi9-twrp-t3923765
Do we need to flash a no opt verify script anywhere
GirishSharma said:
Hello,
I am having global MI9 device. I just want to install SuperSU / root on this device with keeping stock ROM, Recovery, Kernel and Firmware alongwith Encryption and Warranty.
Kindly point me the steps which gives a root + stock things i.e. I don't want to install custom Recovery, ROM, Kernel and Firmware, I just want to live root with stock items.
Click to expand...
Click to collapse
You can keep stock ROM, Kernel and Firmware along with Encryption, it won't change if you flash TWRP, you can also flash stock Recovery after rooting the device, just flash it like TWRP. But any way you need to unlock bootloader and after unlocking bootloader, i think warranty will void
with Magisk there a tutorial how to root it, but you need to have unlocked bootloader.
If you can't manage to find the tutorial, PM me and I can advise you.
catalindobre said:
Mit Magisk gibt es ein Tutorial, wie man es rootet, aber Sie müssen einen entsperrten Bootloader haben.
Wenn Sie das Tutorial nicht finden können, senden Sie mir eine PN, und ich kann Sie beraten.
Click to expand...
Click to collapse
Bitte um Hilfe. Ich habe "ALEXNDR N960FXXU9FVH1" im TWRP installiert, ist Android10 und bin total zufrieden damit. Will alles so lassen aber Root brauchen. Habe auch Magisk installiert und brauche Root für Chimera Tool. Ich brauche eine einfache Anleitung für Dummis.
Freundliche Grüße S.G.
Siegfried Göring said:
Bitte um Hilfe. Ich habe "ALEXNDR N960FXXU9FVH1" im TWRP installiert, ist Android10 und bin total zufrieden damit. Will alles so lassen aber Root brauchen. Habe auch Magisk installiert und brauche Root für Chimera Tool. Ich brauche eine einfache Anleitung für Dummis.
Freundliche Grüße S.G.
Click to expand...
Click to collapse
Please post in English
Anyway, TWRP is not needed to install Magisk. Patch your boot.img and flash through Fastboot
Search about this method on the Forum. Read official Installation instructions on Magisk GitHub page (that's the recommended method, not TWRP)
Of course, Bootloader must be unlocked. No other way to flash anything (TWRP, patched boot img, custom ROM, etc)
However, once you unlock the BL (will do Factory reset), you can also flash TWRP and use it to install Magisk
Ie, unlocked BL is the key-point
So you have a notification telling you that MIUI has an update available - great! Unfortunately the process in the Magisk OTA Upgrade Guide doesn't work for this phone, for some reason even after "uninstalling" Magisk the updater still refuses to apply the OTA update.
If you have installed a custom recovery then you may be able to apply the update through that, but I'll assume that you've followed this guide to root and are still using the stock recovery.
Updating is a 3 step process:
- Flash updated firmware.
- Patch new boot.img.
- Flash patched boot.img.
We'll be doing a "dirty" flash, which keeps your device storage intact. This should be fine for minor updates, however if the phone won't boot then you'll need to do a clean flash which will wipe your phone, so you should backup your data using a tool like Titanium Backup before proceeding.
Flash updated firmware:
- In the Updater app find the MIUI version that it wants to install (e.g. MIUI-V13.0.8.0.RKEEUXM).- visit the MIUI Updates Tracker and download the matching Stable Fastboot update (if you can't find it read Extract boot.img from Payload below).- unzip the TGZ and the TAR that it contains.- connect your phone and run adb reboot bootloader to enter fastboot.- run the flash_all_except_data_storage.bat script to flash the updated firmware. Your phone will reboot when it's done.- (optional) if your phone won't boot then you'll need to perform a "clean" flash. Enter fastboot again and run the flash_all.bat script (this will wipe your data).
Patch new boot.img
- push the new boot.img to the phone using adb push .\images\boot.img /sdcard (you'll need to have selected "File transfer/Android Auto" in the "Use USB for" prompt on the phone).- in the Magisk App click Install in the Magisk tile, tap Select and Patch a File, select the boot.img file, and tap Let's Go.- pull the magisk_patched-*.img from the phone using adb pull /sdcard/Download/magisk_patched-*.img .\.
Flash patched boot.img
- boot into fastboot mode once again using adb reboot bootloader.- flash the patched image using fastboot flash boot magisk_patched-*.img- reboot using fastboot reboot
Happy hacking!
Extract boot.img from PayloadIf you can't find a fastboot image (boot.img) for your version then you might be able to extract it from the full firmware package. This will require the use of a third party tool such as payload-dumper (python) or payload-dumper-go. Note that you may be better off just waiting for the fastboot image to be released to the public.
I found only zip file but where i found the fastboot rom for V13.0.6.0.SKEMIXM?
xn0live said:
I found only zip file but where i found the fastboot rom for V13.0.6.0.SKEMIXM?
Click to expand...
Click to collapse
As mentioned on the other thread, this isn't available yet. I've updated the post to note how you can extract it from the payload file of full firmware .zips, but personally I'd just wait.
I managed to updated to (V13.0.6.0.SKEMIXM) while rooted using the updater app. You are not able to download the update but you can apply the update by choosing the file from local storage and you need to obtain the file from a third party. If you follow Magisk's guide you can keep the root and you don't need a PC
weim1 said:
Ich habe es geschafft, auf (V13.0.6.0.SKEMIXM) zu aktualisieren, während ich mit der Updater-App gerootet war. Sie können das Update nicht herunterladen, aber Sie können das Update anwenden, indem Sie die Datei aus dem lokalen Speicher auswählen, und Sie müssen die Datei von einem Drittanbieter beziehen. Wenn Sie der Anleitung von Magisk folgen, können Sie das Stammverzeichnis behalten und benötigen keinen PC
Click to expand...
Click to collapse
Ich habe die ZIP-Datei V13.0.6.0.SKEMIXM und root.
How do u install it, can u said?
xn0live said:
Ich habe die ZIP-Datei V13.0.6.0.SKEMIXM und root.
How do u install it, can u said?
Click to expand...
Click to collapse
After the update some apps weren't working right so I don't know how successful my method was that's why I haven't respond. It could be that I updated with the de-bloater module on and it may be the reason that everything was messed up. If you want I can tell you what to do but no guarantees
weim1 said:
After the update some apps weren't working right so I don't know how successful my method was that's why I haven't respond. It could be that I updated with the de-bloater module on and it may be the reason that everything was messed up. If you want I can tell you what to do but no guarantees
Click to expand...
Click to collapse
yeah it would be nice
xn0live said:
yeah it would be nice
Click to expand...
Click to collapse
First you need to download the update zip. I used the MIUI Downloader app from play store. Disable all the magisk modules from magisk manager and reboot. Then follow the official Magisk Ota upgrade guide but don't uninstall magisk. You need to enable a secret menu in the updater app to be able to install zips from storage. Just tap the MIUI 13 logo in the middle of the screen multiple times an you are ready. Load the file by opening the menu in the top right corner. Wait for the installation to finish and do not reboot the phone. Go to magisk and install to inactive slot then you can reboot.
Ps. Please backup all your data just in case something goes wrong.
aricooperdavis said:
As mentioned on the other thread, this isn't available yet. I've updated the post to note how you can extract it from the payload file of full firmware .zips, but personally I'd just wait.
Click to expand...
Click to collapse
V13.0.6.0.SKEMIXM fastboot is there
i have root, is it possible to flash it, but i do not want lost my data or other spaces, possible?
xn0live said:
V13.0.6.0.SKEMIXM fastboot is there
i have root, is it possible to flash it, but i do not want lost my data or other spaces, possible?
Click to expand...
Click to collapse
You may be able to "dirty" flash it by following the instructions in the OP, but you should back-up your data in case it doesn't work and you need to fully "clean" flash afterwards.
I started bootlooping (at this point its become a joke to me lol) again right after flashing the patched boot img. Then I remembered from your magisk installation tutorial about this step :
flash vbmeta --disable-verity --disable-verification vbmeta.img
I entered this command and boom I booted back to miui and it has been updated along with magisk running just fine.
I don't know if this happened just to me, but you can add that vbmeta flashing step in your tutorial.
Thanks again!
That's certainly unusual, I have no idea why you'd get a bootloop that can be fixed by flashing the vbmeta! Glad you got it sorted though
Miui 14 has been released for our phones. I was wondering if its the same process for flashing Miui 14, as it's basically flashing a different o.s, from android 12 to android 13.
I'm afraid if my magisk modules may interfere with the update process, which may result in a bootloop and loss of data.
Any insight on this?
Major updates are more likely to fail if you do them "dirty". Just back up your data partition before you start, then you can always flash the old OS and your old data partition if something goes wrong.