Related
As we now have functional recovery options on our tablets, and people will inevitably mess things up with their device, we need to get a way to get your tablets back to factory condition. But I need your help with this!
What do you want?
Here's my idea: We have all seen various ZIPs floating around, most of them leaked from somewhere. The problem with these is that you can't use OTA updates, and I'm not sure what Acer Service Center thinks of custom ROM installs. What I want is to build a list of software that is officially distributed by Acer, is OTA-updateable, etc. For this reason, I want people that have not yet modified their tablets (except root) to provide image dumps of their /system, /boot, /flexrom, and /recovery partition. It's really easy to do, and you'll help yourself and others when they get into trouble.
Can I help?
Answer all of the following questions. If at one point the answer is "Sorry, you can't help", well... You can't help
Is your device unlocked and rooted? Yes - You can help! / No - You can still help, but you need to unlock and root your device.
Do you have the original Acer ROM installed on your device? Yes - You can help! / No - Sorry, you can't help
Have you received the latest OTA updates for your device? Yes - You can help! / No - You can help as well!
Have you removed any apps or files from the /system or /flexrom partition? Yes - Sorry, you can't help / No - You can help!
Have you installed a custom recovery image? Yes - You can still help, as long as everything else is still original / No - You can help!
Okay, so I can help, now what?
If you can and are willing to help (remember, it could save your own ass one day), follow the instructions below. If you get stuck or simply don't know where to start but are willing to help, let us know in this thread and I'm sure we can all help eachother out.
This will not gather any personal data from you. Personal data is stored on the /data partition, which we don't need, so: No worries!
Root your device, if you haven't already.
Connect your tablet to your computer via ADB
Type the following command: adb shell. You are now logged into your tablet. You can exit at any time by typing exit and hitting ENTER.
Type the following command: dd if=/dev/block/mmcblk0p2 of=/sdcard/boot.img. This will copy your /boot partition to a file called boot.img on your internal storage. This one will be fast, it only has about 8MB to copy.
This step can be skipped if you have a custom recovery! Type the following command: dd if=/dev/block/mmcblk0p1 of=/sdcard/recovery.img. This will copy your /recovery partition to a file called recovery.img on your internal storage. This one will be fast as well, it only has about 6MB to copy.
Type the following command: dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img. This will copy your /system partition to a file called system.img on your internal storage. This one will take a bit longer, it has about 360MB to copy.
Type the following command: dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img. This will copy your /flexrom partition to a file called flexrom.img on your internal storage. This one will take a bit longer as well, it has about 360MB to copy.
Type exit to exit the ADB shell. Copy the four .img files from your tablet (internal storage) to your computer. You might have to reboot your tablet if the files don't show up.
ZIP or RAR these files, and upload them somewhere. If you can't find a place to store them: send me a private message or reply in this thread and we'll arrange something else. If you have uploaded the files somewhere: again, send me a private message or reply in this thread.
So now what?
When I receive your files, I will package them into an update.zip that can be flashed from custom recoveries. This will then restore everything (including the custom recovery) to factory state, which can help you in getting your device back to stock.
What versions do you have already?
Acer_AV041_A510_1.044.00_WW_GEN1 (download links will follow shortly)
Acer_AV041_A510_1.098.00_EMEA_CUS1 (download links will follow shortly)
Acer_AV041_A510_1.099.00_EMEA_DE (download links will follow shortly)
The idea sounds great so far. But I have a small problem to make a complete backup for my a511.
Your linked root tutorial for the procedure is only for a100/a510 and doesn't work for a511, as I understand.
The tutorial for rooting the a511 needs first to flash a CWM.
http://forum.xda-developers.com/showthread.php?t=1729432
So it isn't possible for us to backup the recovery partition, right ?
I have the stock Acer_AV041_511_1.028.00_EMEA_DE on my device.
Is it even possible to backup and recover the baseband ?
I'm very interested in your CWM recovery for a511 too, but since many guys f++++d up their device now, I want to make sure that my device will not goes the same way.
i can help, n my tab is rooted.
but i don understand the first step: Connect your tablet to your computer via ADB
What about if we have removed system apps (such as the antivirus that comes with the tablet). It wouldn't be a complete dump if it didn't include those.
I have root and am happy to provide a dump, but I did uninstall several of the crappier pre-installed apps that came with my tablet.
scorpio16v said:
The idea sounds great so far. But I have a small problem to make a complete backup for my a511.
Your linked root tutorial for the procedure is only for a100/a510 and doesn't work for a511, as I understand.
The tutorial for rooting the a511 needs first to flash a CWM.
http://forum.xda-developers.com/showthread.php?t=1729432
So it isn't possible for us to backup the recovery partition, right ?
I have the stock Acer_AV041_511_1.028.00_EMEA_DE on my device.
Is it even possible to backup and recover the baseband ?
I'm very interested in your CWM recovery for a511 too, but since many guys f++++d up their device now, I want to make sure that my device will not goes the same way.
Click to expand...
Click to collapse
Hi, your device will not brick, I can send you a test A511 recovery if you want. Worst that can happen is that recovery won't boot, but in that case you can simply put back recovery. Send me a private message and we can work something out.
scae said:
What about if we have removed system apps (such as the antivirus that comes with the tablet). It wouldn't be a complete dump if it didn't include those.
I have root and am happy to provide a dump, but I did uninstall several of the crappier pre-installed apps that came with my tablet.
Click to expand...
Click to collapse
Then it's of no use, unless you have a backup of your pre-installed apps. Removing apps from the /system or /flexrom partition is not recommended, and you gain nothing by it: You only gain space on read-only filesystems which you won't use in 99% of situations, and you've now broken OTA's for yourself as well, as OTA's will only install when apps are present unless you start modifying OTA files.
The 'correct' way to get rid of pre-installed apps is simply freezing them, either from the settings menu or with an app like Titanium Backup. This will make it seem like they're not there (so they don't use resources at all), but the APKs don't get removed.
So unfortunately, we can't use your dumps to restore devices to factory state. Unless, ofcourse, you've made a backup of the apps somewhere.
skymario said:
i can help, n my tab is rooted.
but i don understand the first step: Connect your tablet to your computer via ADB
Click to expand...
Click to collapse
Do you have ADB or the Android SDK installed?
NoThrills said:
Do you have ADB or the Android SDK installed?
Click to expand...
Click to collapse
I just learned ADB, n successful install ur CWM, later will try to dump my stock Rom to u.
My stock Rom version 1.073 ww gen1
does it matter if the system apps have been frozen or do they need to be unfrozen first?
I have flashed that remove stock recovery mod so the stock rom doesn't keep overwriting cwm on reboot. Does that disqualify me? If not I'll dump my rom for you when I get home.
I'm on this rom version:
ro.build.pandora.id=Acer_AV041_A510_RV28RC04_PA_CUS1
ro.build.flexrom.id=Acer_AV041_A510_1.076.00_PA_CUS1
I unlocked bootloader,rooted,installed cwm then backed up my stock rom.Could i restore my stock rom then be able to send you those fills
and return to total stock.
NoThrills said:
Hi, your device will not brick, I can send you a test A511 recovery if you want. Worst that can happen is that recovery won't boot, but in that case you can simply put back recovery. Send me a private message and we can work something out.
Click to expand...
Click to collapse
i think he mean that the a511 recovery doesn't work properly....you can flash a zip, but nearly all other options brick the device
i have a a511 too with Acer_AV041_A511_1.028.00.EMEA_DE and can help with testing or something else
I have Acer AV041_A510_1.079.00_PA_CA. (Canada)
I have not done a thing to it because it is a replacement for the Galaxy Note I bricked trying to upgrade from GB to ICS, too early.
I might try again if I was sure I could get back to where I am, using your process.
I assume that your Root link is comprehensive but I also need reassurance on how to ADB.
[email protected]
Sent from my A510
blgblade said:
i think he mean that the a511 recovery doesn't work properly....you can flash a zip, but nearly all other options brick the device
Click to expand...
Click to collapse
No, as I understand, the only working methode to root the a511 is to bootloader unlock, flash the custom recovery and then the root.zip.
Maybe I'm wrong and there is another working way to root the device ?
The problem is simply, that we lost the stock recovery before we have a backup from it.
If we have another root way for a511, the backup of stock firmware is done in a few minutes and from this point we can test the a511 custom recovery from NoThrills.
To the A511 owners: Technically, if you have a install-recovery.sh file on your device, the device will always flash recovery back from the boot.img.
In theory: To test, one could simply overwrite the stock recovery with my Recovery (not the other ones, they will brick your device) and then when you reboot, your device will overwrite the recovery with the stock one again. So you really don't need a backup of the recovery partition.
As long as you don't let your device fully boot (so, stay in recovery) there's plenty of time to test if the recovery works or not. If it doesn't, simply reset your device and it will flash back the original recovery (again: provided there is a install-recovery.sh in your /system partition).
So again, if anyone is willing to test, let me know
NoThrills said:
To the A511 owners: Technically, if you have a install-recovery.sh file on your device, the device will always flash recovery back from the boot.img.
Click to expand...
Click to collapse
I can't find a install-recovery.sh in /system partition on my a511. Search on root-explorer can't find one on the device.
Even NOT on /system/etc like on other devices.
NoThrills said:
So unfortunately, we can't use your dumps to restore devices to factory state. Unless, ofcourse, you've made a backup of the apps somewhere.
Click to expand...
Click to collapse
Ah damn, I did back them up via titanium but it doesn't seem to want to restore them - it just sits there say restoring app.
scorpio16v said:
I can't find a install-recovery.sh in /system partition on my a511. Search on root-explorer can't find one on the device.
Even NOT on /system/etc like on other devices.
Click to expand...
Click to collapse
Yeah, I meant /system/etc... That's weird, I'd figure Acer would use the same system on the A511... Let me check one of the leaked ROMs...
Hello,
I have an stock Acer_AV041_A510_1.098.00_EMEA_CUS1, there we go for the files
Host file is not the stock version, it was edited by AdAway.
Can you make a version without recovery overwritting ?
I thinks a lot of people want to try some roms... just for testing...
Acer_AV041_A510_1.098.00_EMEA_CUS1 boot && system && flexroom:
http :// dl.free.fr/jDEmTNSD4
Have Fun
Hello,
I have the same rom without root or unlocked bootloader or moded recovery so if the above on does not make it I'll upload mine.
Sent from my A510 using xda app-developers app
I bought a chinese phone Telsda/TSD A198 . The firmware reports it as an MT6589 CPU but the computer reports it as a spreadtrum phone. I need to root the phone to get rid of some apps on this to make space. Also without rooting is there anyway to backup the stock rom on my phone before I mess up to root? I have seen a method on XDA but that requires root. Now I am trying to backup to get to rooot !!!! Also I have also researched researchdownload but without a ROM backup and not knowing which CPU model to flash its impossible to it right. I also looked into mtkdroidtools and it tells me "unstructured rom backup not possible" , so I am guessing its a fake MTK CPU that is being reported by tweaking the firmware.
This is the link to the phone
http://www.aliexpress.com/item/New-...3-MTK6589-4-0-INCH-smart-phone/879312434.html
Any help is appreciated.
Thanks
I also interesting for this phone, but I have some doubt about the specs of this item. If you could clear some important properties for me, such as:
Does it have GPS functionality?
If not, this indirectly indicates that CPU is not MTK-based (likely Spreadtrum SC6820 if 3G functionality is absent or Spreadtrum SC8810 if it is present)
What is the real width of the phone?
It seems to me it is about 64mm, not 60.8 (as described in seller specs)
What is the RAM size?
Does it have 256 or 512MB RAM?
What is the real Andriod version?
Does it have Android 2.3.X disguised as Android 4.X.X?
I will be grateful for your response.
Villis1251 said:
I also interesting for this phone, but I have some doubt about the specs of this item. If you could clear some important properties for me, such as:
Does it have GPS functionality?
If not, this indirectly indicates that CPU is not MTK-based (likely Spreadtrum SC6820 if 3G functionality is absent or Spreadtrum SC8810 if it is present)
What is the real width of the phone?
It seems to me it is about 64mm, not 60.8 (as described in seller specs)
What is the RAM size?
Does it have 256 or 512MB RAM?
What is the real Andriod version?
Does it have Android 2.3.X disguised as Android 4.X.X?
I will be grateful for your response.
Click to expand...
Click to collapse
Ok, first my honest suggestion dont buy this phone it has pathetic performance. For the same price go for a real MTK6577 dual core. ANyways below are the answers to your question
> Real CPU frequence seems to be 1GHZ
>Mali 300 GPU
>no 3G
>no GPS
>256MB RAM and 256 MB ROM
>I am not sure if its real JB and I cant figure it out but it says JB 4.2.1 and the kernel is 2.6.35.7 and hence I guess its a fake JB. The funny part is under baseband version it says "MT6589 1.5GHZ quad cores" !!!! offcourse it means the firmware/build.prop has been tweaked and is reporting false values. Also when I ran Antutu it gives a score of about 3500 which is useless when compared to what is required to run games ..etc. I hope I have helped.
Thank you much - you helped me to avoid hasty purchase. And good luck in rooting your device.
custom recovery
Villis1251 said:
Thank you much - you helped me to avoid hasty purchase. And good luck in rooting your device.
Click to expand...
Click to collapse
Finally I was able to stitch a ROM, using bits and pieces from different sources and its perfectly working. I only need to build a CWM recovery image based on the recovery image I have attached. Can someone help me do that? so that I can do a nandroid and ump my rom in case someone needs to recover their telsda A198
I need help. I have the same smartphone. But I need it to flash. Do You have the firmware for it?
aspirus said:
I need help. I have the same smartphone. But I need it to flash. Do You have the firmware for it?
Click to expand...
Click to collapse
I have stitched firmware which works perfectly and is rooted. I also got google play store installed. Its not original firmware, the original one is supposedly 4.2.1 (I think its fake), what I have got installed is 4.0.4 if that works for you let me know.
hel me please!!!
braindia said:
I have stitched firmware which works perfectly and is rooted. I also got google play store installed. Its not original firmware, the original one is supposedly 4.2.1 (I think its fake), what I have got installed is 4.0.4 if that works for you let me know.
Click to expand...
Click to collapse
braindia hello ... I bought the same phone and I have problems with the sims do not have to call or receive coverage ..... could you explain you did and how you did it?
there say that you put android 4.0 not work quite right? ... greetings from chile
Braindia hello...I have a bad microphone works, but only when you call. So there are 2 options: trash or firmware.I need a firmware that works correctly works. So 4.2.1 or 4.0.4 for me is not important. I am new in the firmware of the phone (did the firmware only the tablet). Thankful for step by step instructions from the specialist. While I couldn't even get the root.:silly:
aspirus said:
Braindia hello...I have a bad microphone works, but only when you call. So there are 2 options: trash or firmware.I need a firmware that works correctly works. So 4.2.1 or 4.0.4 for me is not important. I am new in the firmware of the phone (did the firmware only the tablet). Thankful for step by step instructions from the specialist. While I couldn't even get the root.:silly:
Click to expand...
Click to collapse
ok looks like lot of people have issues with this phone. Its a junk phone, all fake stuff on it. ANyways I will upload the firmware images and then you guys can use those to flash on your phones. Below is what I have done
1> Patched a 4.0.4 ROM which works perfectly
2>Removed useless preinstalled apps
3>rooted
4>Perfectly working dual sim,GPRS,WIFI,Camera,Camcorder .,..etc etc
4>The issue is with the IMEI, because of the way its stored you guys will need to use your own NV files.
The only thing I havent been able to do is get a working CWM, but you dont need it as you can flash the firmware images using researchdownload.
Braindia, you even pierced smartphone using researchdownload? Maybe I need a USB driver or researchdownload? What have you used? I can't understand how to enable the firmware on this phone: food & + -test menu; food & - picture with your phone and the triangle, but windows does not find the device driver.
working firmware files
aspirus said:
Braindia, you even pierced smartphone using researchdownload? Maybe I need a USB driver or researchdownload? What have you used? I can't understand how to enable the firmware on this phone: food & + -test menu; food & - picture with your phone and the triangle, but windows does not find the device driver.
Click to expand...
Click to collapse
Here you go, you flash at your own risk. If there are bricks/issues you are responsible for your own device.(Standard disclaimer) . I have uploaded all the files except system and NV, system image is kind of big and I am trying to figure it out where to upload it.. You dont need to worry about NV unless you completely erased the flash(never erase the complete flash or format it). If you havent done so then you are good to go.
Please google to find researchdownload and use it to flash the attached files. I wont be able to write the tutorial on using researchdownload so google is your friend.
I have also uploaded the gapps zip which will get you up and running with google play store. You need root to copy these files directly into system/apps folder.
I will be able to upload a system file which works, not the patched one with google play store, root ...etc etc . You do that on your own, I will help you do it.
Thanks !
Tutorial researchdownload not needed. I installed the USB driver and researchdownload. When the phone is loaded, I can connect it to your computer . BUT when I try to flash the phone with the help of researchdownload I need to enable firmware on your phone. In the mode of firmware (if I understand it correctly) phone is not detected by Windows. I wanted to know what USB drivers and version researchdownload used you, and as included mode firmware on your phone.
I have the original firmware.
aspirus said:
Tutorial researchdownload not needed. I installed the USB driver and researchdownload. When the phone is loaded, I can connect it to your computer . BUT when I try to flash the phone with the help of researchdownload I need to enable firmware on your phone. In the mode of firmware (if I understand it correctly) phone is not detected by Windows. I wanted to know what USB drivers and version researchdownload used you, and as included mode firmware on your phone.
I have the original firmware.
Click to expand...
Click to collapse
your phone is probably not detected due to 2 reasons
1> windows disabling non signed driver.. if thats the issue while you start the PC keep hitting F8 you will be shown various options
Select disable windows driver signature enforcement
2> Second reason is you need to add an entry in adb_usb.ini file I think its 0x1782 which is for SPRD enumerator. There are tons of links for this one of which is
http://forum.xda-developers.com/showthread.php?p=37271476
Possible causes checked. NO 1 and NO 2 Everything correctly, but still not working.To go the other way, I've tried about 10 of options to get the root, but the result is zero. You got root?
aspirus said:
Possible causes checked. NO 1 and NO 2 Everything correctly, but still not working.To go the other way, I've tried about 10 of options to get the root, but the result is zero. You got root?
Click to expand...
Click to collapse
getting root is simple, flash a CWM I have attached one, please note this does not work but it works enough to get you root. follow the below steps
1> Flash attached recovery
2> boot into recovery ... this will not show the normal CWM options but dont worry just connect to your pc
3> run ADB shell, you will be automatically in root mode
4> perform mount /system and then exit shell
5> push su binary & busybox directly to /system/bin (from the command prompt using adb push)
6>change permissions for su & busybox to make them runnable
7> exit from the shell and reboot
8> do adb install superuser.apk(optional this can be done later)
thats it you have su, and then you can sideload the superuser apk or you can do step 8 as above. Once you have rebooted and verified that you indeed have superuser you can flash the stock recovery back on the phone.
Note note note : The CWM recovery image is only for you to get root and it doesnt work and doesnt show the normal CWM options... you have been warned. You should flash your old recovery/stock recovery after you have achieved root.
Also can you give me the stock recovery image so that I can build a working CWM out of it. I overwrote mine and now stuck with another recovery which works but is not for this phone.
Thanks
:cyclops:
1> Flash attached recovery
2> boot into recovery ... this will not show the normal CWM options but dont worry just connect to your pc
3> run ADB shell, you will be automatically in root mode
error:device not fround
TADAN
I have a magic smartphone. In recovery he annihilated.
aspirus said:
:cyclops:
1> Flash attached recovery
2> boot into recovery ... this will not show the normal CWM options but dont worry just connect to your pc
3> run ADB shell, you will be automatically in root mode
error:device not fround
TADAN
I have a magic smartphone. In recovery he annihilated.
Click to expand...
Click to collapse
Hmm... I am not sure what is the issue please try attached drivers and pray that they work . use either 64bit or 32bit depending on your OS.
Also you said you have the firmware can you upload it ? I can do something more with the stock/original firmware, so please upload it
I installed a different driver for windowsXP and windows7, but the result is the same. Too much time for 54$. I buried this smartphone. So good luck to you on the path to custom firmware. One month firmware will be available my personal archive: http://files.mail.ru/A9FBE04381094135959559784E5F49A4
aspirus said:
I installed a different driver for windowsXP and windows7, but the result is the same. Too much time for 54$. I buried this smartphone. So good luck to you on the path to custom firmware. One month firmware will be available my personal archive: http://files.mail.ru/A9FBE04381094135959559784E5F49A4
Click to expand...
Click to collapse
Thanks ... I know this phone is a waste of time and money both. I am just using this phone as an experiment platform knowing fully well that this piece of junk will die anytime.
Hi,
I want to download the current firmware from a device. (in this case SM-A125F/DSN )
After hours of searching I gave up. All I got are guides etc. to download firmwares from WEB.
I need it as a backup for my experiments. But if, by any chance, someone can point me to a place where I can download this exact firmware, I'd be happy too.
I also tried to find that specific firmware as an alternative to downloading. But no luck after another 60 minutes. (beside some dubious sites that claimed to have everything but wanted money first, so I was obviously digging deep already - maybe I'm just asking the wrong questions (search terms))
Ofc. I'd prefer to download it from device.
SM-A125F/DSN
[ QP1A.190711.020. ] A125FXXU1AUC3
4.9.190-20270726
If you mean backing up / extracting phone's firmware then - if phone's Android is rooted - you may use ADB to achieve this.
Example extracting boot.img
Method 1
Code:
adb devices
adb root
adb pull "<NAME-OF-RELATED-BLOCK-DEVICE-HERE>" > C:\boot.img
Method 2
Code:
adb devices
adb root
adb exec-out "dd if=<NAME_OF_RELATED_BLOCK_DEVICE_HERE> bs=4096" > C:\boot.img
tyvm for the input!
it is not rooted (but the bootloader is unlocked but I fear this won't help, would it ?)
I guess same applies to the other partitions? (root requirement)
further I guess, there is no way to do this without root (you would have mentioned it, even if obscure, right? :] )
i focus on alternative now (search for firmware)
EDIT: yes, I mean "backing up / extracting phone's firmware"
jwoegerbauer said:
If you mean backing up / extracting phone's firmware then - if phone's Android is rooted - you may use ADB to achieve this.
Click to expand...
Click to collapse
Tell me please if it has sense to backup literally all partitions?
asq81:
ADB doesn't know much about rooting as far as I know, especially in download mode.
It wants only USB debug activated.
asq81 said:
Hi,
I want to download the current firmware from a device. (in this case SM-A125F/DSN )
After hours of searching I gave up. All I got are guides etc. to download firmwares from WEB.
I need it as a backup for my experiments. But if, by any chance, someone can point me to a place where I can download this exact firmware, I'd be happy too.
I also tried to find that specific firmware as an alternative to downloading. But no luck after another 60 minutes. (beside some dubious sites that claimed to have everything but wanted money first, so I was obviously digging deep already - maybe I'm just asking the wrong questions (search terms))
Ofc. I'd prefer to download it from device.
SM-A125F/DSN
[ QP1A.190711.020. ] A125FXXU1AUC3
4.9.190-20270726
Click to expand...
Click to collapse
I don't know much about tech, but it seem to me that you would make your life easy if you would:
1. Look at the exact firmware you have at about phone. I guess you have a Samsung Galaxy A12.
2. Use a reliable Samsung firmware website, for example https://www.sammobile.com.
3. Click browse firmware archive
4. Enter your model: SM-A125F
You should have there the firmware specific for numerous countries, as far as the last 2-3 firmwares for your device. I think on sammobile they might ask you to create an account.
F308 said:
Tell me please if it has sense to backup literally all partitions?
asq81:
ADB doesn't know much about rooting as far as I know, especially in download mode.
It wants only USB debug activated.
Click to expand...
Click to collapse
Don't confuse the Android images like
boot.img, system.img,recovery.img,vendor.img,vbmeta.img, etc.pp
and Android partitions.
The described 'pull' method works well! Thank you jwoegerbauer!
(did not try 'dd' - there was no reason to do so for me)
For me it was ok to flash a boot image and leave everything else untouched. (yay, finally found one and let magisk patch it to have root)
In my case I did not plan to do anything to boot image, just had to find a working one (with root) and backup this. BUs from everything else is what I really need. Not a perfect but totally adequate solution!
I own some old samsung Galaxy models like J7 Prime and had tried good Custom ROMs on them but up recent I purchased this Samsung Galaxy M21 2021 Edition (SM-M215G/DS) a few days ago thinking that it's going to be same as Galaxy M21 2019 (SM-M215F) model, to my horor its bootloader & recovery seems to work differently from J7 prime (with bar codes in download mode) . So it's a differrent model. The bootloader unlock process on this Galaxy M21 2021 Edition is same as mentioned in Galaxy M21 2019 thread ( https://forum.xda-developers.com/t/rom-full-oneui-10-totsukaos-q-for-galaxy-m21.4219975/ ) but none of the unofficial TWRP recoveries work nor does Magisk boot.img patch method work for rooting this model. Samsung does not support Fastboot as I understand & everything ends with Error : Signature verification failed. The only option left to me is sell off this phone but its so new.
If any developer can help me with some Custom Recovery that could install itself for rooting and perhaps custom ROM (I know I'm asking for too much ) for this device (SM-M215/DS), I will gladly donate $20.00/month for a year (Pls consider the bad times of pandemic we all are in). As right now I've put up this device (SM-M215G/DS) for sale. I've attached a few screenshots of the device maybe it could help any Dev who's interested (Hopefully ).
To root Android a Custom Recovery isn't required at all.
jwoegerbauer said:
To root Android a Custom Recovery isn't required at all.
Click to expand...
Click to collapse
jwoegerbauer said:
Firstly, I THANK YOU for replying to my desperate post. I'm delighted that Dev (jwoegerbauer) wanted to help.
Coming to the topic, Yes I was aware that rooting didnt require Custom Recovery.
1> I had tried to install Magisk_V23.zip via command [adb sideload magisk.zip] but the
response I had got was [Error: Signature verification failed, Error: Aborted.] on this device
(SM-M215G/DS).
2> When I flashed couple of TWRPs (one official for Galaxy M20 from www.twrp.me & few
unofficial TWRP builds from the net) via latest ODINv14.3 , ODIN displayed PASS! and
rebooted as I had kept Auto Reboot & F.Reset Time ON. But Native Android revovery came
on with Custom Binary Error. Again, I did the same with F.Reset Time & Auto Reboot OFF this
time and when I manually rebooted to recovery (Vol UP + Power) it was back to native
android recovery. I had to factrory reset to get the samsung logo then booted into welcome
screen.
3> I have checked the link ( https://forum.xda-developers.com/t/...al-adb-fastboot-
drivers.4185535/post-83851013 ) you provided. Awesome work! My questions are will it
enable FASTBOOT on SAMSUNG? Because when I select Reboot to Bootloader option in Anroid Recovery the phone does go into Fastboot Mode but apparently Fastboot seems
disabled by Samsung because from the PC it does not recognise the Fastboot Devices. So,
as a noob if I've understood whats mentioned in the link you provided is that Samsung didnt
provide the Native Samsung Fastboot Drivers for the Galaxy M21 2021 DELIBERATELY? So,
the link you provided will help me install the required Fastboot Drivers? & then I can flash
TWRP.img or Magisk.img?
Thanks in advance
Click to expand...
Click to collapse
jwoegerbauer said:
To root Android a Custom Recovery isn't required at all.
Click to expand...
Click to collapse
Followup 1:
Hi, I tried your ADB-FASTBOOT-Installer but it doesnt seem to go beyond "Waiting for devices" screen.
1> I tried installing magisk v.19.3.zip (renamed to just "OTA") using command (adb sideload OTA)
first error i got was (adb: failed to read command: No error)
2> second time i tried installing from another folder belonging to 15-seconds-adb and it showed [ (0.01x) success ] something like that
3> I installed magisk manager 2021.4.9 Magisk v22.1 by Package Installer method not sideload method. When i rebooted & checked magisk manager it wasnt rooted so I tried boot.img patch method and got error: unable to unpack boot.img
I have attched some screenshots of the errors but what I understand from this is that the new Samsung devices might have img files written in some new format i guess because why else would magisk manager fail to unpack and patch a boot.img file, ususally it does fine.
I have also attached a copy of the device stock boot image file (hope i'm not breaking some xda rules here about posting img files , i just joined yesterday so )
Maybe its of some help to some Dev who might need these to find a workable solution.
The stock firmware I downloaded is flashing well on the device (SM-M215G/DS), the link is here- https://samfrew.com/download/Galaxy__M21__2021__Edition__/lOg2/INS/M215GDDU1AUG2/M215GODM1AUF3/
Also Magisk isn't needed to root a phone's Android: that's a widespread misconception,1000 times reported on the Internet and also here on XDA .
jwoegerbauer said:
Also Magisk isn't needed to root a phone's Android: that's a widespread misconception,1000 times reported on the Internet and also here on XDA .
Click to expand...
Click to collapse
Well what necessarily needed for rooting an android phone is just modifying some files in /system? I have seen the phrase 'toybox 0.8.5' a multiple times in your posts, not sure what is that.
LR7875 said:
Well what necessarily needed for rooting an android phone is just modifying some files in /system? I have seen the phrase 'toybox 0.8.5' a multiple times in your posts, not sure what is that.
Click to expand...
Click to collapse
Toybox is a replacement for many Linux command-line utilities that is targeted at embedded systems - similar to BusyBox. It was created by Rob Landley, who is also a former BusyBox maintainer. Toybox is merged into any Android starting with version 6.
jwoegerbauer said:
Toybox is a replacement for many Linux command-line utilities that is targeted at embedded systems - similar to BusyBox. It was created by Rob Landley, who is also a former BusyBox maintainer. Toybox is merged into any Android starting with version 6.
Click to expand...
Click to collapse
Oh learned something more.
Well what is the definition of root then?
LR7875 said:
Oh learned something more.
Well what is the definition of root then?
Click to expand...
Click to collapse
Sorry to barge in LR7875, to my knowledge (I have rooted & installed Roms on some older Samsung/Redmi/Laptops etc.) rooting is the process through which we gain Admin Rights / Super User on Linux devices. Correct me if I'm wrong. Im not a programmer by any means so.
jwoegerbauer said:
Also Magisk isn't needed to root a phone's Android: that's a widespread misconception,1000 times reported on the Internet and also here on XDA .
Click to expand...
Click to collapse
Hi there jwoegerbauer, thanks for responding. If im not being bothersome , I'll need to stalk you on XDA for some help on this issue of rooting this device, if it s okay with you . Pray tell me what else other than magisk could root this stubborn Samsung model ? Im getting some good offers for this device on the local online market but i really didnt want to sell it off just wanted to root & install roms like before.. Other than magisk I just know of SuperSU by chainfire which I think stopped working well post android 8 oreo but will it work for Android 11? No way any changes to /system/Priv-app and the phones factory reset themselves. One-Click Root only takes calls & they charge $50 for rooting, but whats the guarantee if we pay up that theyll root it properly & taht too it would be just root not Recovery or ROMs. I'm lost.
Installing Magisk DOESN'T ROOT Android. Installing SuperSU DOESN'T ROOT Android. POV.
To have said it:
Magisk is successor to XPosed, means a software framework what once get added to Android allows you to systemless apply modules, means some functionalities modders are missing on standard Android. The crux with Magisk is it patches device's bootloader.
SuperSU simply is a per-app root-access management tool, nothing else: it requires Android got rooted.
OldNoobOne said:
...
The stock firmware I downloaded is flashing well on the device (SM-M215G/DS), the link is here- https://samfrew.com/download/Galaxy__M21__2021__Edition__/lOg2/INS/M215GDDU1AUG2/M215GODM1AUF3/
Click to expand...
Click to collapse
How are you "flashing"?
Why do you say it "is flashing well"?
As far as I know, you need to use Odin (on a PC) to "flash" a Samsung device. Samsung does not support fastboot -- no amount of updating drivers on your PC will make a Samsung device start supporting fastboot.
Magisk is much more than just a way to root, but a side effect of installing Magisk is that you will be rooted.
If you have installed the Magisk Manager app and tried to patch the AP.tar of the stock firmware, and you are getting an error, you should look through the main Magisk thread, and maybe ask there.
J.Michael said:
Magisk is much more than just a way to root, but a side effect of installing Magisk is that you will be rooted.
Click to expand...
Click to collapse
IMO you're WRONG: Magisk DOESN'T ROOT Android, but you additionally can install MagiskSU app what grants elevated rights ( AKA SU ) to Magisk.
jwoegerbauer said:
Magisk is successor to XPosed, means a software framework what once get added to Android allows you to systemless apply modules, means some functionalities modders are missing on standard Android. The crux with Magisk is it patches device's bootloader.
Click to expand...
Click to collapse
I need to hop on and correct a few details here...
Magisk is not a successor to Xposed. That's like comparing apples and oranges. If you want to know how Magisk came to be John has written about that in a couple of places, here for example:
Spoiler
https://www.reddit.com/r/Android/comments/7oem7o
And Magisk does not patch the bootloader, but the ramdisk which can be found in either the boot or recovery image depending on your device. Details about that here:
https://topjohnwu.github.io/Magisk/boot.html
OldNoobOne said:
Sorry to barge in LR7875, to my knowledge (I have rooted & installed Roms on some older Samsung/Redmi/Laptops etc.) rooting is the process through which we gain Admin Rights / Super User on Linux devices. Correct me if I'm wrong. Im not a programmer by any means so.
Click to expand...
Click to collapse
Oh I see, it is used to do something that are restricted originally, e.g. access system files, delete system apps, etc.
Didgeridoohan said:
I need to hop on and correct a few details here...
And Magisk does not patch the bootloader, but the ramdisk which can be found in either the boot or recovery image depending on your device.
Click to expand...
Click to collapse
Correct: it should also have been called boot.img instead of bootloader. Sorry for this.
LR7875 said:
Oh I see, it is used to do something that are restricted originally, e.g. access system files, delete system apps, etc.
Click to expand...
Click to collapse
True . Don't quote me, (In a nut shell ) up from Andoid 9 (Pie) modification to /system /app etc. is difficult per my knowledge, thats why probably magisk sits in the boot partition, no one dare touches the system partition anymore while the gadget is ON. Only Gugle stays in the system partition im sure. The Custom Recoveries do wipe the device but are unable to erase the core andoid OS inside . Even 'Fastboot Erase' command cant get andoid out completely (exception Linux-phones i think). So practically Andoid devices are just gadgets that are 'leased' to the so-called 'owner' of the device (without explicitly mentioning the term 'leased' by gugle). The cost of the smart-gadget is practically the 'Down Payment' we pay to Gugle & OEMs then the rest of the revenue they make from Ads etc. which goes as 'Rent/lease payment' to them ultimaately & we never get to own the devices we purchase EVER! .
My sixth-sense says The chinese OEMs allowing Fastboot Mode only for now but only to make inroads into the smart-gadget market, once they have made everyones profile Gugle & pentgon might just make the softwares on these smart-gadgets wholly tamper-proof & focus more on 'managing' or keeping an eye on their 'subjects' [given that the whole gugle business,- 'search-engine', 'smart-device' etc. started officially in 2004 which was POST the 9.11 ATTACK].
So they're probably maintaining the Big-Data on everyone who uses their devices & 2014 is when data-warehousing became the need if i remember correctly; so, it was all about compressing the Big-data gathered & then Analytecs took the spotlight by 2016-17 coz they needed to analyize all the data collected & remove the junk from it then home in on pentgons targets. It's Obvious . No wonder they're pushing PX-Xperience ROMs through the ROM channels to cover the gap created by chinese OEMs eating into their market share. Why else do they charge other OEMs $2 for OTG-support while Shamshung (and now MYUI) already had native OTG-support on their devices shipped? so that's what Sekure-folder all about, YOUR DATA LOADED & LOCKED real-time then SHIPPED back to Gugle-Analytecs. Obvious.
Well so root is basically... Removing those ads and trackware up to the bare bones of the phone, to ensure all your data isn't used to make the spammy advertisements?
Android is nothing else then a derivated Linux. In the world of Linux the Root User is the user that has all rights esp. accessing / modifying system files, it's comparable to the Administrator in the world of Windows.
In the world of Linux this Root User typically is called superuser ( commonly abbreviated: SU ). In the world of Android such a superuser isn't in general implemented by default: it must get added to Android by modding it, means adding a SU ( read: Switch User ) binary - in whatever form - to Android what is systemwide accessible. In the world of Android an user root exists what is the user with user ID 0.
[ deleted ]
I've got the ZTE Blade V Smart (2050) that uses the MT6771 processors. It had been rooted on Android 9 which caused me to lose my IMEI, but I removed root, and then updated the phone to Android 10. After updating I received the NVRAM ERROR in my wifi settings. What did I do? I did a data factory reset thinking it would update properly the next time. Wrong! I tried over 20 times at least. I have searched high and low online for a backup of the firmware to download so I can achieve root again and fix the wifi error. No success unless I wanna pay. Then, I attempted to do a ROM dump using Wwr and SPFT. No success there either. After that I began downloading the crack box programs to see if I could possibly get one to root me or do anything. In doing so, I discovered that the MT6771_scatter.txt for Android 10 is not the same as on Android 9. So my question is, how can I dump my ROM if the scatter files from Android 9 & 10 are different? I would really like to have root again also so I can fix the NVRAM wifi issue, as well as use some of the perks of having Magisk and it's modules on my phone. Thank you in advance for any assistance.
finnroth69 said:
I've got the ZTE Blade V Smart (2050) that uses the MT6771 processors. It had been rooted on Android 9 which caused me to lose my IMEI, but I removed root, and then updated the phone to Android 10. After updating I received the NVRAM ERROR in my wifi settings. What did I do? I did a data factory reset thinking it would update properly the next time. Wrong! I tried over 20 times at least. I have searched high and low online for a backup of the firmware to download so I can achieve root again and fix the wifi error. No success unless I wanna pay. Then, I attempted to do a ROM dump using Wwr and SPFT. No success there either. After that I began downloading the crack box programs to see if I could possibly get one to root me or do anything. In doing so, I discovered that the MT6771_scatter.txt for Android 10 is not the same as on Android 9. So my question is, how can I dump my ROM if the scatter files from Android 9 & 10 are different? I would really like to have root again also so I can fix the NVRAM wifi issue, as well as use some of the perks of having Magisk and it's modules on my phone. Thank you in advance for any assistance.
Click to expand...
Click to collapse
Use Mtkclient to Backup/flash any Partition wanted. You won't need a scatter.txt for this. You can make your own by using Mtkclient to read/pull the GPT table only (partition info) using:
Code:
python mtk printgpt
then manually creating a scatter file on your own by editing the old Android 9 scatter (and changing differences). Hope I helped
Slim K said:
Use Mtkclient to Backup/flash any Partition wanted. You won't need a scatter.txt for this. You can make your own by using Mtkclient to read/pull the GPT table only (partition info) using:
Code:
python mtk printgpt
then manually creating a scatter file on your own by editing the old Android 9 scatter (and changing differences). Hope I helped
Click to expand...
Click to collapse
I ended up being able to pull the scatter using mtk deauthorization tool. Still having trouble with Wwr, SPFT, Meta, and MTK Tool all reading my phone though. They ask get to a certain point in the process and just stop. Then the apps usually crash. I checked and rechecked my drivers, I've uninstalled and reinstalled everything several times. It only happens with those apps. This is the same as it was doing before when I was running Android 9 also. I can get any other apps to read my phone, but the ones I need to actually read... No so much.
finnroth69 said:
I've got the ZTE Blade V Smart (2050) that uses the MT6771 processors. It had been rooted on Android 9 which caused me to lose my IMEI, but I removed root, and then updated the phone to Android 10. After updating I received the NVRAM ERROR in my wifi settings. What did I do? I did a data factory reset thinking it would update properly the next time. Wrong! I tried over 20 times at least. I have searched high and low online for a backup of the firmware to download so I can achieve root again and fix the wifi error. No success unless I wanna pay. Then, I attempted to do a ROM dump using Wwr and SPFT. No success there either. After that I began downloading the crack box programs to see if I could possibly get one to root me or do anything. In doing so, I discovered that the MT6771_scatter.txt for Android 10 is not the same as on Android 9. So my question is, how can I dump my ROM if the scatter files from Android 9 & 10 are different? I would really like to have root again also so I can fix the NVRAM wifi issue, as well as use some of the perks of having Magisk and it's modules on my phone. Thank you in advance for any assistance.
Click to expand...
Click to collapse
And where did you get it 10 Android ?