Related
I bought a tablet lenovo a3500-hv with android version 4.2.2
I wanna root it ,, pls.
I used framaroot but no way the problem still and it failed
Pls help me and thank alot
Rooting and backup or lenovo a35000
MidoTayel said:
I bought a tablet lenovo a3500-hv with android version 4.2.2
I wanna root it ,, pls.
I used framaroot but no way the problem still and it failed
Pls help me and thank alot
Click to expand...
Click to collapse
Hi @MidoTayel i have also bought a Lenovo a3500-HV less than a week ago i know of two goo tools that can help you root they are:-
Farmaroot- http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
ROOT Genius- http://www.shuame.com/en/root/
But i would recommend that you WAIT A FEW DAYS as you know that after rooting the system can get corrupted (Based upon the app you install) thus you would send it to the service center and they would charge a lot of money(root void your warrenty). Apparently i am researching how to create and flash scattle files (Backup images of all system files,recovery.img,boot.img........) in Lenovo a3500-HV(Companies use this method to install android after the tablet is made).
Also i am researching how to create a clockworkmod recovery which will help in flashing updates and flash.zip modification and will also create nandroid backup of your entire system
If you can wait a few more days (5-6) days i will email you a set of tutorials from backuping imei numbers to creating scatter files(Right now i am sorting the best tutorial and good information from the junk in the different forums and blogs). With this information you do not need to go to the service center for any software issue anymore all you would need is an computer and a OTG cable (the cable used to connect phone to computer) and if you install custom recovery you would not need that also (Saved over Rs6000 in my previous tablet software problems)
I am also planning to make a thread upon the LENOVO a3500-HV
Also i have a few QUESTION i want to know if you are facing these problems as i want to know if it is only in my tablet or the entire firmware
-Does the tablet restart between every 4-5-6 hours
-The GPS does not work Test using GPS TEST app ( https://play.google.com/store/apps/details?id=com.chartcross.gpstest&hl=en ) Already found some fixes but it needs root
-Can you boot into recovery mode or does it get stuck in the boot logo
-Can you install CPU-Z ( https://play.google.com/store/apps/details?id=com.cpuid.cpu_z&hl=en ) and check if the hardware is the mt6582 model (Picture given below)
LAST of all can you give me your email id as yau are the only other Lenovo A3500-HV (Model is new) member i could find and i will first email all the tutorials i.e. doc,vedios,pdf to you and help you through email and chat
And if you only want to root and don't care it goes to the service center please atleast tell me if the root is working or not THANL YOU
Email ID - [email protected]
:victory:
anandisrocking007 said:
Hi @MidoTayel i have also bought a Lenovo a3500-HV less than a week ago i know of two goo tools that can help you root they are:-
Farmaroot- http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
ROOT Genius- http://www.shuame.com/en/root/
But i would recommend that you WAIT A FEW DAYS as you know that after rooting the system can get corrupted (Based upon the app you install) thus you would send it to the service center and they would charge a lot of money(root void your warrenty). Apparently i am researching how to create and flash scattle files (Backup images of all system files,recovery.img,boot.img........) in Lenovo a3500-HV(Companies use this method to install android after the tablet is made).
Also i am researching how to create a clockworkmod recovery which will help in flashing updates and flash.zip modification and will also create nandroid backup of your entire system
If you can wait a few more days (5-6) days i will email you a set of tutorials from backuping imei numbers to creating scatter files(Right now i am sorting the best tutorial and good information from the junk in the different forums and blogs). With this information you do not need to go to the service center for any software issue anymore all you would need is an computer and a OTG cable (the cable used to connect phone to computer) and if you install custom recovery you would not need that also (Saved over Rs6000 in my previous tablet software problems)
I am also planning to make a thread upon the LENOVO a3500-HV
Also i have a few QUESTION i want to know if you are facing these problems as i want to know if it is only in my tablet or the entire firmware
-Does the tablet restart between every 4-5-6 hours
-The GPS does not work Test using GPS TEST app ( https://play.google.com/store/apps/details?id=com.chartcross.gpstest&hl=en ) Already found some fixes but it needs root
-Can you boot into recovery mode or does it get stuck in the boot logo
-Can you install CPU-Z ( https://play.google.com/store/apps/details?id=com.cpuid.cpu_z&hl=en ) and check if the hardware is the mt6582 model (Picture given below)
LAST of all can you give me your email id as yau are the only other Lenovo A3500-HV (Model is new) member i could find and i will first email all the tutorials i.e. doc,vedios,pdf to you and help you through email and chat
And if you only want to root and don't care it goes to the service center please atleast tell me if the root is working or not THANL YOU
Email ID - [email protected]
:victory:
Click to expand...
Click to collapse
Thanks for reply and that's my email [email protected]
GREAT !!
I finally found other guys having Lenovo A3500-HV
@MidoTayel
I guess you can use vRoot to root this model of lenovo (A3500).
But as @anandisrocking007 mentioned, I also recommend that you wait. Because the root may be dangerous without CWM recovery to make backup image of your system.
@anandisrocking007
I am happpy with your researching and waiting you…
I have some answers of your questions:
1- My tablet doesn't restart automatically ever from I bought it.
2- You can boot into recovery mode by holding the three buttons together (Vol. up + Vol. down + Power) after shutting down the device.
Other problems I will check them later.
Thanks.
ibraheem_alex said:
GREAT !!
I finally found other guys having Lenovo A3500-HV
@MidoTayel
I guess you can use vRoot to root this model of lenovo (A3500).
But as @anandisrocking007 mentioned, I also recommend that you wait. Because the root may be dangerous without CWM recovery to make backup image of your system.
@anandisrocking007
I am happpy with your researching and waiting you…
I have some answers of your questions:
1- My tablet doesn't restart automatically ever from I bought it.
2- You can boot into recovery mode by holding the three buttons together (Vol. up + Vol. down + Power) after shutting down the device.
Other problems I will check them later.
Thanks.
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU i had thought that i had bought a tablet with a corrupted recovery as the previous model a3000 had a different set of command to go to recovery take a look at it yourself
http://forum.xda-developers.com/lenovo-a3000/general/lenovo-a3000-startup-modes-t2656140
So are you rooted by vroot
ok and one more thing power+vol up =Factory mode(Dangerous if you do not know what you are doing)
and if you can not understand the chinese this is the translation
工厂模式
Factory Mode
感应器校准 Sensor Calibration
自动测试 Automatic Test
单项测试 Individual Tests
测试报告 Test Report
调试测试项 Debugging Test Items
浦除e MMC Format e-MMC
版本信息 Version Information
重启手机 Restart The Phone
and again thank you also tonight/tomorrow morning i will send a set of ussd(you just have to press call after typing the code) code to check if the bootloader of the phone is locked like asus(Then i can not flash and root as it will brick th phone[though the chances of this happening in lenovo is 2% as all the previous model's bootloader is unlocked but better safe than sorry])
MidoTayel said:
I bought a tablet lenovo a3500-hv with android version 4.2.2
I wanna root it ,, pls.
I used framaroot but no way the problem still and it failed
Pls help me and thank alot
Click to expand...
Click to collapse
Hi @divergent and @ibraheem_alex can you type the following USSD codes in your device
Dial *#*#7378423#*#* . Then go to -> "Service Info" -> "Configuration". If there is:
Bootloader unlock allowed - Yes << this means that your Bootloader is Locked
Bootloader Unlocked - Yes << this means that your bootloader is unlocked
Please give me a feedback... i can make the tutorials and instructions but i also need you the give feedback and help it can incrase my work speed i shall try to publish everything by this wednesday-thusday......
anandisrocking007 said:
THANK YOU THANK YOU THANK YOU i had thought that i had bought a tablet with a corrupted recovery as the previous model a3000 had a different set of command to go to recovery take a look at it yourself
http://forum.xda-developers.com/lenovo-a3000/general/lenovo-a3000-startup-modes-t2656140
So are you rooted by vroot
ok and one more thing power+vol up =Factory mode(Dangerous if you do not know what you are doing)
and if you can not understand the chinese this is the translation
工厂模式
Factory Mode
感应器校准 Sensor Calibration
自动测试 Automatic Test
单项测试 Individual Tests
测试报告 Test Report
调试测试项 Debugging Test Items
浦除e MMC Format e-MMC
版本信息 Version Information
重启手机 Restart The Phone
and again thank you also tonight/tomorrow morning i will send a set of ussd(you just have to press call after typing the code) code to check if the bootloader of the phone is locked like asus(Then i can not flash and root as it will brick th phone[though the chances of this happening in lenovo is 2% as all the previous model's bootloader is unlocked but better safe than sorry])
Click to expand...
Click to collapse
Hi @anandisrocking007
I am sorry for the late reply .. I was very busy.
I still not rooted my Lenovo A3500
I just suggest to use vRoot but I didn't know the result.
Thank you for your chinese translation of Factory Mode .. I accedently format my device first time when I trying to boot into recovery mode
……… .
---------- Post added at 05:00 PM ---------- Previous post was at 04:43 PM ----------
anandisrocking007 said:
Hi @divergent and @ibraheem_alex can you type the following USSD codes in your device
Dial *#*#7378423#*#* . Then go to -> "Service Info" -> "Configuration". If there is:
Bootloader unlock allowed - Yes << this means that your Bootloader is Locked
Bootloader Unlocked - Yes << this means that your bootloader is unlocked
Please give me a feedback... i can make the tutorials and instructions but i also need you the give feedback and help it can incrase my work speed i shall try to publish everything by this wednesday-thusday......
Click to expand...
Click to collapse
After I typing USSD code the code is gone after latest star "*" and nothing happen !!!
What should I do after that ?? .. How to go to Service info ?!!
Thanks for all and I wanna know if it's dangerous to root it or no ??
ibraheem_alex said:
Hi @anandisrocking007
I am sorry for the late reply .. I was very busy.
I still not rooted my Lenovo A3500
I just suggest to use vRoot but I didn't know the result.
Thank you for your chinese translation of Factory Mode .. I accedently format my device first time when I trying to boot into recovery mode
……… .
---------- Post added at 05:00 PM ---------- Previous post was at 04:43 PM ----------
After I typing USSD code the code is gone after latest star "*" and nothing happen !!!
What should I do after that ?? .. How to go to Service info ?!!
Click to expand...
Click to collapse
Hi @ibraheem_alex so the USSD anomaly is not only for my phone its ok not to worry i am 95% sure that lenovo does not have locked bootloader also did you check the GPS is it working also use CPU-Z to check the chipset model mine is MT6582 when everything is over i would be uploading the scatterfile backup for everyone to use i just want to know if more than one type of model is released as different countries have different chipset but the same model (Pss..It won't have an impact on the tutorials that i shall post as you shall make a backup of your own phone :highfive
Tutorial Update- i have managed to download some vedios from sites and found a lot of tutorials that i have saved in .docx format just 1-2 more sites are left i shall then sort out the best one and if require will merge some to make a better one all and all i shall post it within a few days the tablet is an huge investment i think its fine to be a little patient....... (Pss...i shall be uploading it in google drive and will publish the link...:good
---------- Post added at 12:26 PM ---------- Previous post was at 11:59 AM ----------
MidoTayel said:
Thanks for all and I wanna know if it's dangerous to root it or no ??
Click to expand...
Click to collapse
Hi @MidoTayel let me put this in simple words take windows for example where there is a guest account and there is a admin account in guest you can use the software but can not write anything in the C Drive(Also can't install software which are stored in C Drive) in that way Windows's C Drive=System Partition on android so when you get a phone its always in guest mode when you root it it gives you admin access. Some apps require to write or change file for it to work eg ROMtoolbox , Xposed module etc when you are not rooted the apps save all files into the data partition and if any problem occurs you can do a factory reset (i.e deleting the data partition) and it will be the same but if you are rooted and have some problem in the system partition even factory reset won't it goes to the service centre and they charge. Scatter file backup and nandroid backup are ways to backup an entire android OS ie system,data partition along with others its like you are creating an entire android installation setup and when your phone is bricked you can reinstall it. Overall i can tell you that the privilages of root outweigh the risk a lot what every you do try to research a little (I took 2 months to root my last tablet) and always make a scatter file and/or nandroid backup as soon as you root (First backup then check the cool device i.e ASAP) you root to be 100% safe
I am making tutorial to hep you root or create a backup....
Hope this helps i was confused for weeks thinking what is root when i started android..hope you don't face the same problem
PRESS THANKS IF IT HELPS.....:victory:
My chipset model is MT6582 .. It is same as your chipset.
I couldn't determine if my GPS working or not...
I used the GPS Test as you mention but also I can't know if it working correctly or not .. May I will make another test while moving in car.
But I captured this photo from the app .. May it help you.
See the photo in attachments.
Hi, I have a model A3500-FL (without back camera).
GPS works, locks in about a minute out in the open. Tablet lacks AGPS (no data connection). It's MT6582 which can use Mediatek's proprietary EPO to speed up positioning, but due to no root I cannot verfy if it is working or not.
Anyone tried backing up A3500 via SPFlash or MTKdroid tools or rooting?
Hey i wanna install the kali linux on my tab so if there is other way to do it without root it pls tell me
Hi
Me to .. I need to run Linux Ubuntu on my tablet.
But I think NO way to run linux without rooting your tablet.
This is how I rooted my A3500-FL under Xubuntu 14.04 (i have win 7 in VM):
1. install Virtualbox, not the OSE edition - get the full version from Oracle website and also the extesion pack (it enables direct access to USB devices)
2. Install windows (XP or 7, don't know about later versions)
3. Grab a copy of RootGenius from here
4. Enable usb debugging on tablet Connect your tablet via usb, make sure it is recognized by ubuntu, there is no need to mount it
lsusb for my device:
Code:
Bus 002 Device 004: ID 17ef:7738 Lenovo
5. Start your windows installation and mount the USB in virtualbox (there is a button for that at the bottom of a windows running your VM), make sure windows sees your device, it will probably fail to install the drivers
6. Start RootGenius, it should download and install drivers for this phone. Tutorial including usb debugging here. Click root a wait for a minute. Done
If yu are running windows skip steps 1-2.
Optional: make full system backup here
I did a backup before rooting. MTK tools somehow sneaked su binary past the android defences and got shell root after backing up.
MidoTayel said:
I bought a tablet lenovo a3500-hv with android version 4.2.2
I wanna root it ,, pls.
I used framaroot but no way the problem still and it failed
Pls help me and thank alot
Click to expand...
Click to collapse
use kingo android root .i tested it,but use it with your responsibility
anyone has stock rom for a3500 .plz i need it :crying:
hi, friends
i am going to buy this device shortly after my galaxy wonder had been theft.
i love cyanogenmod roms and i think that we can port CM11 or CM12 to this device in the near future.
i know that the device is really new but nothing impossible.
we can work together fro the project and i will inform you the day i will by the device.
cheers
piuma said:
use kingo android root .i tested it,but use it with your responsibility
anyone has stock rom for a3500 .plz i need it :crying:
Click to expand...
Click to collapse
So did you screw up your device using kingo
Thanks very much
doesn't work anymore
after upgrading to kitkat(official) i've lost root permission, i've tried to root it again with Root Genius but this time it doesn't work.
cshadow said:
This is how I rooted my A3500-FL under Xubuntu 14.04 (i have win 7 in VM):
1. install Virtualbox, not the OSE edition - get the full version from Oracle website and also the extesion pack (it enables direct access to USB devices)
2. Install windows (XP or 7, don't know about later versions)
3. Grab a copy of RootGenius from here
4. Enable usb debugging on tablet Connect your tablet via usb, make sure it is recognized by ubuntu, there is no need to mount it
lsusb for my device:
Code:
Bus 002 Device 004: ID 17ef:7738 Lenovo
5. Start your windows installation and mount the USB in virtualbox (there is a button for that at the bottom of a windows running your VM), make sure windows sees your device, it will probably fail to install the drivers
6. Start RootGenius, it should download and install drivers for this phone. Tutorial including usb debugging here. Click root a wait for a minute. Done
If yu are running windows skip steps 1-2.
Optional: make full system backup here
I did a backup before rooting. MTK tools somehow sneaked su binary past the android defences and got shell root after backing up.
Click to expand...
Click to collapse
How did you upgrade? OTA updater shows me only some minor version upgrade.
I'm not seeming to find coherent instructions to get back to stock 11.0.2.2IN11AA
I have the 8 Pro, rooted, newest magisk and I installed a magisk module that is now causing System UI crash at startup. I have tried a couple things: 1) tried the "adb wait-for-device shell magisk --remove-modules" --> nothing happens when starting back up except System UI error. 2) I've flashed back to stock boot.img (hoping to get to safe mode to disable magisk)...all I get is System UI error again.
So...what I want to do is start all over and end up with 11.0.2.2IN11AA rooted. Once I'm back to "factory" I'm pretty sure I can get back to magisk and root.
Can anyone help me with some decent instructions please?
Thanks
I can. So last week I managed go back from a rooted situation to stock rom with LOCKED bootloader. This means that you're phone will be as you bought it and you're gonna lose everything of course.
This video on YT helped me.
***REMEMBER TO CHOOSE YOUR FIRMWARE BECAUSE I THINK THIS VIDEO IS FOR ASIA, IF IT IS THE SAME FOR YOU THEN YOU SHOULD FOLLOW THIS VIDEO***
I provide you a link with a thread on xda where I found the version for my oneplus 8 pro (EU)
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS | XDA Developers Forums (xda-developers.com)
Thanks I'll check it out and report back
glhelinski said:
Thanks I'll check it out and report back
Click to expand...
Click to collapse
Let me know
glhelinski said:
I'm not seeming to find coherent instructions to get back to stock 11.0.2.2IN11AA
I have the 8 Pro, rooted, newest magisk and I installed a magisk module that is now causing System UI crash at startup. I have tried a couple things: 1) tried the "adb wait-for-device shell magisk --remove-modules" --> nothing happens when starting back up except System UI error. 2) I've flashed back to stock boot.img (hoping to get to safe mode to disable magisk)...all I get is System UI error again.
So...what I want to do is start all over and end up with 11.0.2.2IN11AA rooted. Once I'm back to "factory" I'm pretty sure I can get back to magisk and root.
Can anyone help me with some decent instructions please?
Thanks
Click to expand...
Click to collapse
Visit the MSM thread, that's it
Sneakdovi said:
Let me know
Click to expand...
Click to collapse
Good site and instructions. They sure don't make it clear that msmtool is packaged inside the image download file
glhelinski said:
Good site and instructions. They sure don't make it clear that msmtool is packaged inside the image download file
Click to expand...
Click to collapse
I only donwloaded the EU verision (because i'm in Italy), went to qualcom recovery, and started the process
Sneakdovi said:
I only donwloaded the EU verision (because i'm in Italy), went to qualcom recovery, and started the process
Click to expand...
Click to collapse
Please help me, i'm bricked my new device. I want that ****** monocrome filter and make to many bull**** ! :-( I need my phone.
The MSM-Tool is give me always "Sahara" errors. Make the same misstake then you! I locked the bootloader!
Please.
chr_rocke808 said:
Please help me, i'm bricked my new device. I want that ****** monocrome filter and make to many bull**** ! :-( I need my phone.
The MSM-Tool is give me always "Sahara" errors. Make the same misstake then you! I locked the bootloader!
Please.
Click to expand...
Click to collapse
First off, you may want to edit your language in here, no need to swear. Secondly you should check out the thread regarding the MSM tool.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Post #2 above has a video and also links to the same place that freshlybaked420 referenced... Should be enough to get you back on track
FreshlyBaked 420 said:
First off, you may want to edit your language in here, no need to swear. Secondly you should check out the thread regarding the MSM tool.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, it's all true. Sorry for that i have now working for many days on this. Not sleeping enought. One more question that could bring me a step foward...
I was on IN11.0.2.2 before i locked the bootloader and bricked the device.
Now i downladed the Decrypted OxygenOS 11.0.0 IN21BA Version. I have now the error: Param Preload Device not match image. Question: Must i habe the Decrypted OxygenOS 11.0..2.2 IN21BA Version that it goes to work?
I can't the use the link for the right version, it is password protected.!
Thanks
The password is listed in the OP
glhelinski said:
The password is listed in the OP
Click to expand...
Click to collapse
Thank you, but I didn't find it.
One point I have forgotten to tell. Before the hard brick happened, I used Magistik and Patch a new boot.img then I flashed this with fastboot command. My failure was to make this 2. times. with different patches. The horrible thing is now that I must delete these files on my Laptop to get more space. When this the Problem of the MSMTOOL error is I had not really a chance to unbrick my device. Have anyone Downgrade with MSMTOOL the Stock Rom?
Thx for your help. I download now from OP the latest ROM. I will try it. I feel really scared. Maybe my device is not unbricked anymore.
The other Tool that I have (last chance) is the original Qualcomm flashing Tool QPST.
described here:
Download QPST Flash Tool & How to Use it to Flash Firmware on Qualcomm Android Devices
Download all versions of QPST Flash tool and learn how to use the QFIL and Software Download programs to flash firmware files on Qualcomm Android devices.
www.thecustomdroid.com
-- > But I found nothing here, that this tool was used. There is no special Rom here to found.
chr_rocke808 said:
Thank, but i didn't find it.
One point i forgotten to tell. Before the hard brick happend, i used Magistik and Patch a new boot.img then i flashed this with fastboot comand. My failure was to make this 2. times. with diffred pachtes. The horrible thing is now that i must delete this files on my Laptop to get more space. When this the Problem of the MSMTOOL error is i had not realy a chance to unbrick my device. Habe anyone Donwgrade with MSMTOOL the Stock Rom?
Thx for your help. I download now from OP the latest ROM. I will try. i feel realy scared. Mabye my device is not unbricked anymore.
The other Tool that i have (last chance) is the orginal Qulacomm flashing Tool QPST.
described here:
Download QPST Flash Tool & How to Use it to Flash Firmware on Qualcomm Android Devices
Download all versions of QPST Flash tool and learn how to use the QFIL and Software Download programs to flash firmware files on Qualcomm Android devices.
www.thecustomdroid.com
-- > But i found nothing here, that this tool was used. There is noch spezial Rom here to found.
Click to expand...
Click to collapse
None of that matters.
1st identify your device!
What region is it?
If you have BA then don't flash AA you'll mess things up.
2nd visit the MSM thread!
Download the tool 'for your device!'
3rd boot to EDL (I responded to you in the romaur thread how to do this)
4th as soon as it's connected to your pc in edl, flash the device
5th MSM will relock your bootloader.
6th don't do something if you're not sure, just ask.
Oh and lol chill on the swearing also on posting everywhere, just make 1 thread and stick with it, people will help
Hey, my Phone is working like a charm. Thx for the great work !!!. I'm so happy !!!
It is better to come here to real developers, I had to get bad download links and bad Software! This was the only problem. For many years I have the first Samsung Galaxy and I'm knowing that I can get all the problems for not booting devices back. But I was scared that many Devices like Huwai bring their bootloaders with cryptographic methods in a safe trunk.
Best wishes to you, and the people that I'm working for the android project!
regardless,
chr_rocke808
chr_rocke808 said:
Hey, my Phone is working like a charm. Thx for the great work !!!. I'm so happy !!!
It is better to come here to real developers, I had to get bad download links and bad Software! This was the only problem. For many years I have the first Samsung Galaxy and I'm knowing that I can get all the problems for not booting devices back. But I was scared that many Devices like Huwai bring their bootloaders with cryptographic methods in a safe trunk.
Best wishes to you, and the people that I'm working for the android project!
regardless,
chr_rocke808
Click to expand...
Click to collapse
Lol no worries pal, but trust me, always make a thread unless one exists, it'll work out.
Glad you're sorted.
Hi All
Looking for a best tutorial to follow and the right one for my phone really don't want to brick it, obviously :/. as there seems to be a few versions for the S7
I have the following: S7 android 8.0.0 SM-G930F not sure what else I need to know! I'm in the UK so I assume UK phones come with Exynos cpu's
and as far as I am aware android 8 is Oreo! but when they say Stock Rom I assume they mean the same as what came with the phone the original rom?
if so is there an alternative stable rom without the crap included or is it just as simple to delete every thing you don't want now it's rooted! and does that mean if I reset the phone its back to normal with all the crap included! or is there a way to keep it rooted even after reset! and should anything be disabled I.e prepare the phone before attempting to root like any kind of auto encryption that needs disabling and just one more question
if at anytime the rooting process hangs for a ridiculous amount of time when should I throw in the towel! and what are the chances of retrieving the phone back to original state! or does a dirty shutdown brick it?.
I started the root process but failed at first hurdle!, followed instructions install Odin3_v3.13.1 but when I connected the phone nothing showed up in Odin? though I will have another go just to confirm I followed it correctly, I'll update this when it's done.
this was the tutorial I followed:
Easy 4 Newbie [Root Guide]SM-G930F, G935F, G930FD, G935FD (Samsung Galaxy S7 Edge)
Warning ! Please note that the official TWRP for Nougat on Galaxy S7/ S7 Edge is not available yet but based on my experience the Marshmallow version is working on Nougat. By installing a custom recovery on your S7 and S7 Edge and rooting it...
forum.xda-developers.com
I know alot of questions I would really appreciate any help and clarification on the above.
many thanks
Regards
Daz
Look pal, rooting the phone is just like being an adult, it means you will get rid of Samsung's "Child Care".
Yes, UK models use Exynos chip, but you have to be sure, look at your baseband version, if it is G930FXXX, then you are good.
ROMs are in two shapes:
Stock-based: These are just like the one you are using, or other Samsung phones does, like Samsung Experience, One UI, TouchWiz. Maybe MIUI and FlymeOS will come into account, as there are ROMs based on them + Samsung's.
AOSP: These are pure Android ROMs, with few modifications to the core, but keeping the UI as close to the source as possible, Google & OnePlus phones come with a near-to-pure operating systems.
Changing a ROM is not risky, as long as you follow the instructions, without any unaccounted improvising.
Before you install a ROM, read the working and bug list, to make sure you are installing something you have an idea of.
You need to install TWRP recovery (or any other one you like), and format data, in order to be able to travel among ROMs and/or root your device.
Formatting is only required because the phone is forcibly encrypted, and TWRP can not decrypt it, at least not for this device.
Rooting is simply about flashing a 5-MB file, Magisk, then rebooting to system, no need to wipe data.
No need to do any additional steps, unless you are trying to hide root from some apps and/or pass SafetyNet.
Mohamedkam000 said:
Look pal, rooting the phone is just like being an adult, it means you will get rid of Samsung's "Child Care".
Yes, UK models use Exynos chip, but you have to be sure, look at your baseband version, if it is G930FXXX, then you are good.
ROMs are in two shapes:
Stock-based: These are just like the one you are using, or other Samsung phones does, like Samsung Experience, One UI, TouchWiz. Maybe MIUI and FlymeOS will come into account, as there are ROMs based on them + Samsung's.
AOSP: These are pure Android ROMs, with few modifications to the core, but keeping the UI as close to the source as possible, Google & OnePlus phones come with a near-to-pure operating systems.
Changing a ROM is not risky, as long as you follow the instructions, without any unaccounted improvising.
Before you install a ROM, read the working and bug list, to make sure you are installing something you have an idea of.
You need to install TWRP recovery (or any other one you like), and format data, in order to be able to travel among ROMs and/or root your device.
Formatting is only required because the phone is forcibly encrypted, and TWRP can not decrypt it, at least not for this device.
Rooting is simply about flashing a 5-MB file, Magisk, then rebooting to system, no need to wipe data.
No need to do any additional steps, unless you are trying to hide root from some apps and/or pass SafetyNet.
Click to expand...
Click to collapse
Hi Mohamedkam000
Thanks for replying. I'm not confused about why I want to root the phone. I'm just trying to understand the inner workings and the risks as I'm not as clued up with phone OS's as I am windows. I don't care about warrantees or hiding the the fact it's rooted I just want a clean rooted phone free of big brother well inside at least I know you will never completely keep them out but making it hard is a start lol.
Thank you very much for all the above especially on clarifying about the roms and the reason TWRP formats due to encryption nice one
My Baseband version slightly different though it's G930FXXU8ETI3 not sure if having a U instead of a third X makes any difference!
and I posted wrong tutorial I'm actually following this one below again not sure if that matters.
Guide How to root Android 8.0 Oreo Stock ROM on Galaxy S7 ( 100% Working )
Hi . i see too many peoples have problem on rooting Android 8.0 Oreo Stock Rom on Galaxy S7 ( edge ) and they cant get passed from the verification field error ! ok its bcuz they do only 1 step wrong , here i just wanna tell you all the steps 1...
forum.xda-developers.com
Again many thanks for clarifying that lot up very informative and much appreciated.
Kind regards
Daz
CitizenSmith said:
Hi Mohamedkam000
Thanks for replying. I'm not confused about why I want to root the phone. I'm just trying to understand the inner workings and the risks as I'm not as clued up with phone OS's as I am windows. I don't care about warrantees or hiding the the fact it's rooted I just want a clean rooted phone free of big brother well inside at least I know you will never completely keep them out but making it hard is a start lol.
Thank you very much for all the above especially on clarifying about the roms and the reason TWRP formats due to encryption nice one
My Baseband version slightly different though it's G930FXXU8ETI3 not sure if having a U instead of a third X makes any difference!
and I posted wrong tutorial I'm actually following this one below again not sure if that matters.
Guide How to root Android 8.0 Oreo Stock ROM on Galaxy S7 ( 100% Working )
Hi . i see too many peoples have problem on rooting Android 8.0 Oreo Stock Rom on Galaxy S7 ( edge ) and they cant get passed from the verification field error ! ok its bcuz they do only 1 step wrong , here i just wanna tell you all the steps 1...
forum.xda-developers.com
Again many thanks for clarifying that lot up very informative and much appreciated.
Kind regards
Daz
Click to expand...
Click to collapse
It doesn't matter which version of Android you are using, root is the same.
However, on stock ROMs, it might sometimes get rough, as you may end up with Wi-Fi not working (happened to me Q1 2020).
If you really want to learn how Android OS works, then rooting the stock ROM is not your way.
Try AOSP ROMs, preferably start with Oreo ones, you can root in 3 common way, LineageOS SU Add-on, Magisk, Super SU.
But before you tickle your phone, you have to make a backup of your current device, of every partition, EFS is the most important partition, so make sure it is safe.
Baseband version doesn't matter a lot, unless you're paranoid with updates, it is sorted alphabetically, each string on its own.
The phone is more similar to a linux machine than to a Windows PC.
Edit: To root stock ROM, you have to flash dm verity, so you don't end up encrypted again.
Mohamedkam000 said:
It doesn't matter which version of Android you are using, root is the same.
However, on stock ROMs, it might sometimes get rough, as you may end up with Wi-Fi not working (happened to me Q1 2020).
If you really want to learn how Android OS works, then rooting the stock ROM is not your way.
Try AOSP ROMs, preferably start with Oreo ones, you can root in 3 common way, LineageOS SU Add-on, Magisk, Super SU.
But before you tickle your phone, you have to make a backup of your current device, of every partition, EFS is the most important partition, so make sure it is safe.
Baseband version doesn't matter a lot, unless you're paranoid with updates, it is sorted alphabetically, each string on its own.
The phone is more similar to a linux machine than to a Windows PC.
Edit: To root stock ROM, you have to flash dm verity, so you don't end up encrypted again.
Click to expand...
Click to collapse
Thanks again for clearing quite a few things up I thought rooting stock rom would have been far safer way forward wow how wrong was I! but I guess I am just trying to find any kind simile to windows in any way but as you pointed out again it's more like Linux which again I've only played around with ubuntu and mint for a short period so again not to up on Linux lol.
It's funny I was just reading up on AOSP ROMs then got your message. I see they have a stable but not complete! Android 10 not that I would consider it need as I need a stable OS so Oreo is fine for me.
I have backed up phone using Smart Switch on the PC I assume that copy's every thing that's needed, I reset the phone in anticipation all be it prematurely but at least it restored all my data so if anything that was a good test of the back up at least .
I will have look at some AOSP ROMs and see what's involved there, I'll check out their tutorial hopefully it will include the whole process including root.
I gather by your comment using a AOSP ROM you don't need to use dm-verity or will that still be needed!.
The first thing to do is to flash (install) TWRP, it's a custom recovery (think of it as a mini OS that can boot before Android), that will be the base for any of your future tinkering.
Here is the thread, read the FP carefully: [Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
Once TWRP installed, you can do many things:
Install addons like Magisk. Magisk is the tool you use to obtain root. Forget SuperSU, its outdated, and don't works in modern versions of Android.
Install a custom ROM (this subforum is the perfect place to find them).
Backup & restore an image of your current ROM (very useful).
mooms said:
The first thing to do is to flash (install) TWRP, it's a custom recovery (think of it as a mini OS that can boot before Android), that will be the base for any of your future tinkering.
Here is the thread, read the FP carefully: [Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
Once TWRP installed, you can do many things:
Install addons like Magisk. Magisk is the tool you use to obtain root. Forget SuperSU, its outdated, and don't works in modern versions of Android.
Install a custom ROM (this subforum is the perfect place to find them).
Backup & restore an image of your current ROM (very useful).
Click to expand...
Click to collapse
Thanks Mooms for the input
I tried to follow your links tutorial which he gives three options only one is any good to me and that was installing twrp using Odin but I'm having issues at every turn!. I can't even get Odin to recognise my phone it just wont pick it up I have Samsung driver installed and I have reinstalled many times I found an article claim to have a workaround but that was BS just selling some other app I even change the driver as described on there page,
7 Tips to Fix Odin Not Detecting Phone
Are you using Odin flash tool to flash your Samsung phone but it is not recognized by Odin? Here are 7 tips to fix Odin not detecting phone.
www.imyfone.com
.
but that did nothing so reinstall normal driver again.
feels like it's just not meant to be :/
Thanks again.
CitizenSmith said:
Thanks again for clearing quite a few things up I thought rooting stock rom would have been far safer way forward wow how wrong was I! but I guess I am just trying to find any kind simile to windows in any way but as you pointed out again it's more like Linux which again I've only played around with ubuntu and mint for a short period so again not to up on Linux lol.
It's funny I was just reading up on AOSP ROMs then got your message. I see they have a stable but not complete! Android 10 not that I would consider it need as I need a stable OS so Oreo is fine for me.
I have backed up phone using Smart Switch on the PC I assume that copy's every thing that's needed, I reset the phone in anticipation all be it prematurely but at least it restored all my data so if anything that was a good test of the back up at least .
I will have look at some AOSP ROMs and see what's involved there, I'll check out their tutorial hopefully it will include the whole process including root.
I gather by your comment using a AOSP ROM you don't need to use dm-verity or will that still be needed!.
Click to expand...
Click to collapse
AOSP ROMs are pure, you can't say they are not complete. They are complete, and what OEMs do, like Samsung and Xiaomi is just a customization that you can do, too.
It is preferred that when you take a backup, take it with TWRP, just to ensure you backed up phone's partitions, along with "EFS".
The root procedure on Android 6+ is done by patching the Kernel (boot.img), so unless you take backup of that, you cannot keep root.
There are stable custom ROMs, custom ROMs are meant for custom adjustments, however the stability depends on your phone, and the way you use it, you can compare AOSP vs. Stock and see the difference.
AOSP ROMs doesn't need dm verity, well, at least not if the developer did not mention the encryption part.
Mohamedkam000 said:
AOSP ROMs are pure, you can't say they are not complete. They are complete, and what OEMs do, like Samsung and Xiaomi is just a customization that you can do, too.
It is preferred that when you take a backup, take it with TWRP, just to ensure you backed up phone's partitions, along with "EFS".
The root procedure on Android 6+ is done by patching the Kernel (boot.img), so unless you take backup of that, you cannot keep root.
There are stable custom ROMs, custom ROMs are meant for custom adjustments, however the stability depends on your phone, and the way you use it, you can compare AOSP vs. Stock and see the difference.
AOSP ROMs doesn't need dm verity, well, at least not if the developer did not mention the encryption part.
Click to expand...
Click to collapse
Some of the roms I have looked at mention external touch buttons at bottom of phone do not work or something else in the phone I'm just reading their comments.
I understand about the stock & custom rom's now that's not my problem at least not at the moment as I am miles away from choosing a rom! as I can't even get out the starting gate!. I can not get TWRP on my phone as the only way I can see to get it on a unrooted! phone is to use Odin but as I said Odin doesn't work at least not for me it does not see my phone. I would love to take a back up using twrp but that won't happen until I find a way to get TWRP on a unrooted phone. what crazy paradox is this!. you can't root phone without twrp installed and twrp won't install on a unrooted phone!. that makes perfect sense.
CitizenSmith said:
Some of the roms I have looked at mention external touch buttons at bottom of phone do not work or something else in the phone I'm just reading their comments.
I understand about the stock & custom rom's now that's not my problem at least not at the moment as I am miles away from choosing a rom! as I can't even get out the starting gate!. I can not get TWRP on my phone as the only way I can see to get it on a unrooted! phone is to use Odin but as I said Odin doesn't work at least not for me it does not see my phone. I would love to take a back up using twrp but that won't happen until I find a way to get TWRP on a unrooted phone. what crazy paradox is this!. you can't root phone without twrp installed and twrp won't install on a unrooted phone!. that makes perfect sense.
Click to expand...
Click to collapse
Does your phone allow MTP communication? I mean can you transfer files when the phone is turned on?
Does the phone show any notification about a usb connection?
If not, then you have probably a bad USB cable, at least, or you have a hardware issue that can go as deep as a burned charging port.
If yes, then either your USB cable is not as fast as the phone requires, or you haven't installed the Samsung USB Drivers on your PC.
Unfortunately, you cannot root your device without PC, at least not since Lollipop.
CitizenSmith said:
Thanks Mooms for the input
I tried to follow your links tutorial which he gives three options only one is any good to me and that was installing twrp using Odin but I'm having issues at every turn!. I can't even get Odin to recognise my phone it just wont pick it up I have Samsung driver installed and I have reinstalled many times I found an article claim to have a workaround but that was BS just selling some other app I even change the driver as described on there page,
7 Tips to Fix Odin Not Detecting Phone
Are you using Odin flash tool to flash your Samsung phone but it is not recognized by Odin? Here are 7 tips to fix Odin not detecting phone.
www.imyfone.com
.
but that did nothing so reinstall normal driver again.
feels like it's just not meant to be :/
Thanks again.
Click to expand...
Click to collapse
Which version of Odin are you using ?
Use this version (latest): Odin v3.14.4
Which version of the Samsung USB drivers are you using ?
Use this version (latest): https://developer.samsung.com/mobile/android-usb-driver.html
Mohamedkam000 said:
Does your phone allow MTP communication? I mean can you transfer files when the phone is turned on?
Does the phone show any notification about a usb connection?
If not, then you have probably a bad USB cable, at least, or you have a hardware issue that can go as deep as a burned charging port.
If yes, then either your USB cable is not as fast as the phone requires, or you haven't installed the Samsung USB Drivers on your PC.
Unfortunately, you cannot root your device without PC, at least not since Lollipop.
Click to expand...
Click to collapse
Hi
Yes I can transfer files.
Yes phone asks to allow or block file transfer and it ohone shows up in Devices and Drives list and I can access the phone directory and shows up as Samsung s7 icon.
I will try another USB lead but the one I'm using is new and wasn't cheap but still a possibility I have had leads that weren't suitable for other things I was trying so it is worth a try.
Thanks
mooms said:
Which version of Odin are you using ?
Use this version (latest): Odin v3.14.4
Which version of the Samsung USB drivers are you using ?
Use this version (latest): https://developer.samsung.com/mobile/android-usb-driver.html
Click to expand...
Click to collapse
When I downloaded Odin this was latest one Odin3_v3.13.1 though I have doubts that one version update will fix this issue as I did not see many if any people having my issue so they all used Odin and I believe theirs are fine even with older versions! but as I said Mohamedkam it's worth a try I will down load that version and give it a try.
As for the Samsung usb driver I believe that is where I got mine
SAMSUNG_USB_Driver_for_Mobile_Phones no version visible under properties on file version 1.7.23.0.
The USB connection seems to be fine I have uninstalled then re-download and reinstalled a couple of times.
I can transfer files no problem it shows up as Galaxy S7 Icon with card and phone drive inside.
I'll update shortly thank you.
Update:
I just went to try new Odin and whilst checking my phone have seen I have Offical TWRP app installed? I have no clue as to how that's got in there! as Odin did not show phone so I could select nothing!.
In the phone I open app and if i select backup existing recovery it opens and Select Folder tab and under that Selected Folder: /sdcard Filename: Recovery .img and at the bottom of screen Root access required.
I just hope it's installed correctly!. it is showing in playstore my apps as well just to confirm. if this is now installed what should I do next Now not sure what tutorial to start following.
I am just going to try the new odin and see if it picks up the phone back soon.
OK Seem that it now shows up in the new Odin. at least I think it has! in the log window I see this: <ID:0/004> Added!!
I didn't see that before.
Would be grateful if you could tell me how to proceed from here!
Correct, you don't need he latst version of Odin or the Samsung drivers, bit it was just to be sure.
You need to be in download mode, but before, you must have checked OEM unlock & USB debug in developer options (mandatory).
I've written a tutorial with images here (in French):
Samsung Galaxy S7 (edge) - Mangez un Oreo! [Topic Unique] - Page : 487 - Téléphone Android - Technologies Mobiles - FORUM HardWare.fr
mooms said:
Correct, you don't need he latst version of Odin or the Samsung drivers, bit it was just to be sure.
You need to be in download mode, but before, you must have checked OEM unlock & USB debug in developer options (mandatory).
I've written a tutorial with images here (in French):
Samsung Galaxy S7 (edge) - Mangez un Oreo! [Topic Unique] - Page : 487 - Téléphone Android - Technologies Mobiles - FORUM HardWare.fr
Click to expand...
Click to collapse
As I said the older version did not show any kind of data what's so ever and the phone was in download mode. phone displayed "Downloading" which I believe it says that even if it's not doing anything! so a tutorial explained. I think it must have installed the Official TWRP app even though phone did not show up in Odin everything was blank however when I installed the new version of Odin like you suggested it then showed up as <ID:0/004> Added!!. so your suggestion work thanks for that and I did enable OEM unlock & USB debug I did long time ago.
I would check out your tutorial but unfortunately I don't speak French and translating instructions is too risky but thank you for the offer but I'll carry on look around still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
CitizenSmith said:
As I said the older version did not show any kind of data what's so ever and the phone was in download mode. phone displayed "Downloading" which I believe it says that even if it's not doing anything! so a tutorial explained. I think it must have installed the Official TWRP app even though phone did not show up in Odin everything was blank however when I installed the new version of Odin like you suggested it then showed up as <ID:0/004> Added!!. so your suggestion work thanks for that and I did enable OEM unlock & USB debug I did long time ago.
I would check out your tutorial but unfortunately I don't speak French and translating instructions is too risky but thank you for the offer but I'll carry on look around still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
Click to expand...
Click to collapse
Take a note that, when you flash TWRP, you have to boot immediately to the recovery, so as to enforce its existence, cause I remember they phone has an original recovery backed up somewhere, and gets triggered when you reboot directly to system instead of the unofficial binary.
I advise you to watch guides on YouTube, it's more .. understandable.
CitizenSmith said:
still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
Click to expand...
Click to collapse
I recommend to go with ALEXNDR ROM: zero bugs, everything works perfectly (it's based on stock ROM).
[ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4 * Encryption support [Jul-10]
Important notes for Developers / Chefs !!! This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it...
forum.xda-developers.com
Mohamedkam000 said:
Take a note that, when you flash TWRP, you have to boot immediately to the recovery, so as to enforce its existence, cause I remember they phone has an original recovery backed up somewhere, and gets triggered when you reboot directly to system instead of the unofficial binary.
I advise you to watch guides on YouTube, it's more .. understandable.
Click to expand...
Click to collapse
Yer I read that but I've ended up with TWRP installed and did not do that process because I was unaware it installed until it showed up.
As I said I'll just keep looking for now I know I'll find one that works for me from start to finish.
and I've been checking youtube but wouldn't want to use any links their providing but it may help familurise myself with the whole process if i watch enough of them.
Thanks again for your help.
mooms said:
I recommend to go with ALEXNDR ROM: zero bugs, everything works perfectly (it's based on stock ROM).
[ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4 * Encryption support [Jul-10]
Important notes for Developers / Chefs !!! This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi Mooms
I will check that out many thanks. I wonder if you could help me here. I am in the middle of the rooting process but have hit a snag. again!
I have now installed TWRP successfully then no-verity-opt-encrypt-3.1 all went fine and I'm at point of flashing Magisk but have an issue when I swipe to flash is gives me a error in red saying "invalid zip file format !"
I downloaded it from github here.
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
I click on "code" tab and then "download zip" and I placed that in a download folder on my sd card when I select it I get the above error any ideas as to why I am getting this am I downloaded the correct file?
thanks for any assistance you could give.
Hi,
I have a SM-T380, and I tried to root it using magisk, It patched the boot.img file and I flashed it via odin, but for some odd reason when I open Magisk it says installed N/A.
I have the latest security patch (T380DXS4CUD3) (Android 9) and I already tried using the preserve AVB / preserve force encryption options.
I was wondering, there's no way to root this device on Android 9?I'm just trying out of fun since the tablet was laying around there.
any suggestions really appreciate it,
Waiting for someone to shed some light in to this matter. I tried all the possible procedure I found on google, but no luck.
Barto604 said:
Hi,
I have a SM-T380, and I tried to root it using magisk, It patched the boot.img file and I flashed it via odin, but for some odd reason when I open Magisk it says installed N/A.
I have the latest security patch (T380DXS4CUD3) (Android 9) and I already tried using the preserve AVB / preserve force encryption options.
I was wondering, there's no way to root this device on Android 9?I'm just trying out of fun since the tablet was laying around there.
any suggestions really appreciate it,
Click to expand...
Click to collapse
If your still interested in rooting this device go to @Austcool post it worked for me.
custom-sm-t380-sm-t385-boot
Edit: 2022 I have tested it it fully works as of this year!!!. 😁 disclaimer, I am in no way responsible for this kernel screwing up you tablet so use at your own risk. to flash it simply open up settings enable developer options and enable OEM...
forum.xda-developers.com
Barto604 said:
Hi,
I have a SM-T380, and I tried to root it using magisk, It patched the boot.img file and I flashed it via odin, but for some odd reason when I open Magisk it says installed N/A.
I have the latest security patch (T380DXS4CUD3) (Android 9) and I already tried using the preserve AVB / preserve force encryption options.
I was wondering, there's no way to root this device on Android 9?I'm just trying out of fun since the tablet was laying around there.
any suggestions really appreciate it,
Click to expand...
Click to collapse
Its Defex use my boot.img it's related to Samsungs new Defex anti root privileges security feature you must build the kernel from source; I already built Defex disabled kernel Prerooted with magisk.
Thank you, I already installed a Custom Rom ( I think it was made by you) using the January 2020 Security Patch, I think the latest software update is also a security patch so is redundant.
My question is, is it possible that you can provide me a .zip with the original Samsung Galaxy Boot Logo animations from this tablet? the Rom has custom ones and it didn't had a backup of the originals, I need the:
bootup.qmg
bootloop.qmg
shutdown.qmg
also if you have the original PowerOn.ogg and ShutDown.ogg I would really appreciate it. Thanks for replying this old threat it really means a lot.
Barto604 said:
Thank you, I already installed a Custom Rom ( I think it was made by you) using the January 2020 Security Patch, I think the latest software update is also a security patch so is redundant.
My question is, is it possible that you can provide me a .zip with the original Samsung Galaxy Boot Logo animations from this tablet? the Rom has custom ones and it didn't had a backup of the originals, I need the:
bootup.qmg
bootloop.qmg
shutdown.qmg
also if you have the original PowerOn.ogg and ShutDown.ogg I would really appreciate it. Thanks for replying this old threat it really means a lot.
Click to expand...
Click to collapse
Sure I'll pull them from my device on pie.
Austcool said:
Sure I'll pull them from my device on pie.
Click to expand...
Click to collapse
Barto604 said:
Thank you, I already installed a Custom Rom ( I think it was made by you) using the January 2020 Security Patch, I think the latest software update is also a security patch so is redundant.
My question is, is it possible that you can provide me a .zip with the original Samsung Galaxy Boot Logo animations from this tablet? the Rom has custom ones and it didn't had a backup of the originals, I need the:
bootup.qmg
bootloop.qmg
shutdown.qmg
also if you have the original PowerOn.ogg and ShutDown.ogg I would really appreciate it. Thanks for replying this old threat it really means a lot.
Click to expand...
Click to collapse
Was this my Oreo rom I cannot seem to find the download for it do you mind sharing the download link I was trying to grab some files from the old Oreo rom but I couldn't find it. Also I can get you the pie copys of the bootup.qmg and the bootloop.qmg shutdown.qmg but the files called PowerOn.ogg and ShutDown.ogg don't exist by default on the SM-T380 they are custom added by me you can ether add your own bootsounds files or remove them to boot without a poweron/shutdown sound.
Austcool said:
Was this my Oreo rom I cannot seem to find the download for it do you mind sharing the download link I was trying to grab some files from the old Oreo rom but I couldn't find it. Also I can get you the pie copys of the bootup.qmg and the bootloop.qmg shutdown.qmg but the files called PowerOn.ogg and ShutDown.ogg don't exist by default on the SM-T380 they are custom added by me you can ether add your own bootsounds files or remove them to boot without a poweron/shutdown sound.
Click to expand...
Click to collapse
Thank you so much!!!
And sorry it wasn't your build it was zfk110's build https://forum.xda-developers.com/t/...android-9-bloatware-free-twrp-backup.4243589/
Barto604 said:
Hi,
I have a SM-T380, and I tried to root it using magisk, It patched the boot.img file and I flashed it via odin, but for some odd reason when I open Magisk it says installed N/A.
I have the latest security patch (T380DXS4CUD3) (Android 9) and I already tried using the preserve AVB / preserve force encryption options.
I was wondering, there's no way to root this device on Android 9?I'm just trying out of fun since the tablet was laying around there.
any suggestions really appreciate it,
Click to expand...
Click to collapse
I want to piggyback off of this thread because I'm experiencing the same problem...if anyone can help by giving a step-by-step instruction as to what worked that would be most appreciated
allanseth23 wrote that "this worked," but what did? You follow that link and there are six files, I tried it out and the following screens which I've never seen before showed up (see attached images)
I'm not new to this and I've rooted a wide variety of devices (including using firehose/engineering mode) so I'm really having some trouble understanding why rooting this ancient device five years after its release and almost a year past it's final update is so difficult
if someone can be so kind as to write a step by step "step one, load this via odin (file attached); step two load this via twrp (file attached)" that would be great because the information for this device is scattered across tens of pages and the posts are incomplete (they mention it's for Pie but don't mention on which build they were successful) - no one has collated all of this info to say what works and it would help lots of people, not just myself
I think that's the most frustrating part, the piecemeal information from posters regarding this device--I don't think I've ever waded in an XDA thread that was this broken before (it also doesn't help that all the Tab A models are pushed together into one subforum).
To be clear I'm running the very last software update for this device (AP T380DXS4CUD3) for SM-T380, device is OEM unlocked.
I just want the version rooted, I don't need any TWRP backups that contain additional mods.
Thanks to anyone that can help
cliffswallow said:
I want to piggyback off of this thread because I'm experiencing the same problem...if anyone can help by giving a step-by-step instruction as to what worked that would be most appreciated
allanseth23 wrote that "this worked," but what did? You follow that link and there are six files, I tried it out and the following screens which I've never seen before showed up (see attached images)
I'm not new to this and I've rooted a wide variety of devices (including using firehose/engineering mode) so I'm really having some trouble understanding why rooting this ancient device five years after its release and almost a year past it's final update is so difficult
if someone can be so kind as to write a step by step "step one, load this via odin (file attached); step two load this via twrp (file attached)" that would be great because the information for this device is scattered across tens of pages and the posts are incomplete (they mention it's for Pie but don't mention on which build they were successful) - no one has collated all of this info to say what works and it would help lots of people, not just myself
I think that's the most frustrating part, the piecemeal information from posters regarding this device--I don't think I've ever waded in an XDA thread that was this broken before (it also doesn't help that all the Tab A models are pushed together into one subforum).
To be clear I'm running the very last software update for this device (AP T380DXS4CUD3) for SM-T380, device is OEM unlocked.
I just want the version rooted, I don't need any TWRP backups that contain additional mods.
Thanks to anyone that can help
Click to expand...
Click to collapse
I am piggy backing too because you are someone recently (last week) were messing with this thing too...
I was given a SM-T380 and am trying to make it "useful"
So far I have had fine luck with both oreo and pie (using the build you mentioned T380DXS4CUD3 via twrp restore... and it is fine, but seems slower than I recalled 8.1 being...
Anyway, I have been flashing the v19.0 of magisk (and a v7.1 of magisk manager) and then flashed v21.4 (and v8.x of manager).
Anyway, if you install a newer magisk manager it will show the device as unrooted (N/A) but updating further seems like I would need to extract the boot.img from the twrp backup (which is above my head...) and patch it with newer magisk...
I am not sure that it's needed for what I will be using the tablet for.. but I haven't had luck with safetynet (using magiskhide props) so I am looking into other methods.
Anyway, I'm not sure if I sould go back to oreo 8.1 or not just because pie 9 seems sluggish in comparison..
Anyway, I am going to tinker with it in my spare time over the next few days, so if you want to connect about anything particular I am around.
-g
cliffswallow said:
I want to piggyback off of this thread because I'm experiencing the same problem...if anyone can help by giving a step-by-step instruction as to what worked that would be most appreciated
allanseth23 wrote that "this worked," but what did? You follow that link and there are six files, I tried it out and the following screens which I've never seen before showed up (see attached images)
I'm not new to this and I've rooted a wide variety of devices (including using firehose/engineering mode) so I'm really having some trouble understanding why rooting this ancient device five years after its release and almost a year past it's final update is so difficult
if someone can be so kind as to write a step by step "step one, load this via odin (file attached); step two load this via twrp (file attached)" that would be great because the information for this device is scattered across tens of pages and the posts are incomplete (they mention it's for Pie but don't mention on which build they were successful) - no one has collated all of this info to say what works and it would help lots of people, not just myself
I think that's the most frustrating part, the piecemeal information from posters regarding this device--I don't think I've ever waded in an XDA thread that was this broken before (it also doesn't help that all the Tab A models are pushed together into one subforum).
To be clear I'm running the very last software update for this device (AP T380DXS4CUD3) for SM-T380, device is OEM unlocked.
I just want the version rooted, I don't need any TWRP backups that contain additional mods.
Thanks to anyone that can help
Click to expand...
Click to collapse
I root mine by just loading pie.tar from @Austcool post on odin. We have the same build no.
Alrighty... So I'm in the weeds here after going through three variants of the Samsung JPop (Which have bootloaders locked up like Fort Knox) and decided today to break down and dish out $59 for this bargain device. First thing I did upon getting it home was fastbooting it, and was able to unlock the bootloader with no issue. (So easy, a caveman could do it)
I've read just about every thread in here and though there seems to be TWRP support for quite a few models of the Onn tablets, I didn't see this one in here. Right now I have a throwaway laptop which is installing ubuntu for building TWRP for this device. Now, I have NEVER built TWRP. But I have plenty of free time, ambition, and am willing to learn. I have the basic guide to building TWRP open elsewhere. I will take whatever help I can get on doing this, big or small. Building a basic TWRP image should be easy enough, but the guides don't really go into device specific details (as expected), so this is where I could use some veteran help.
Device Specs:
Model: 100026191
Out-of-the-box Android Version: 11
Display: 7" 1024 x 600 Resolution
Processor: 2.0 GHz Quad-core CPU
RAM: 2GB
Cameras: 2MP front & back
USB: Type-C
Ubuntu just finished, and I am getting the build environment ready as we speak. Will keep this thread updated with progress and hickups that may occur along the way. Wish this noob some luck!!!!
Alrighty, so here's what I've been able to come up with as far as more detailed system information. Sorry for the late post, had trouble getting wifi working on ubuntu but got it going.
I suspected a MediaTek CPU and was eager to do a readback with SP Flash Tool, but as you can tell from the provided screenshots, it's actually a Cortex-A53 CPU. my goal here is to some how pull my stock recovery out of here. I thought about dd'ing it but someone in another thread advised against it. Does Onn have stock firmwares hidden away in the internet somewhere? Or is there another tool I can use to pull recovery?
Good evening guys and gals. New day, new opportunity. So i'm still stuck at pulling off boot and recovery from this tablet. I used
Code:
/adb shell cat /proc/mtd
to no avail. Permission denied just like with dd.
Today, I got the MTK droid tool and hooked the tablet to it and got these results. Still no scatter file, still no progress on pulling these partitions. (I apologize for my dumbness yesterday, this device is in fact MediaTek)
Alright. Eighty of you have clicked in this thread, zero of you show any motivation to do anything to contribute. You guys must hate this tablet because I went through this entire board, and each thread that even mentioned this model were left with no response. I just want the boot and recovery partitions off of the stock tablet. I am willing to do the rest. I said before, I'd take any help I could get but since this device is "so" insignificant, I'm not trying anything else on it.
I don't know if you guys dodge this device because it's Android 11, or what. But the least you veterans could do is either tell us it's not going to happen (given that you tried), or give us some other ideas we could try. Hell I'll paypal you enough for you to have the device in your hands in order to help. But that's where I stand. Moderator can lock this thread if he wishes. There's nothing else I can do for this device at the moment.
guess i'll return it to walmart
was hoping to root it easily with twrp
just gonna go grab the 8' if this is how it ended for the 7'
thanks for the help though!
I need a firmware for the 100026191
TWRPN00b said:
Alright. Eighty of you have clicked in this thread, zero of you show any motivation to do anything to contribute. You guys must hate this tablet because I went through this entire board, and each thread that even mentioned this model were left with no response. I just want the boot and recovery partitions off of the stock tablet. I am willing to do the rest. I said before, I'd take any help I could get but since this device is "so" insignificant, I'm not trying anything else on it.
I don't know if you guys dodge this device because it's Android 11, or what. But the least you veterans could do is either tell us it's not going to happen (given that you tried), or give us some other ideas we could try. Hell I'll paypal you enough for you to have the device in your hands in order to help. But that's where I stand. Moderator can lock this thread if he wishes. There's nothing else I can do for this device at the moment.
Click to expand...
Click to collapse
I have the boot and recovery images if you want them.
I unfortunately accidentally deleted the original boot image, but I have a magisk patched image still present.
I can walk you through the process of extracting the original if you would prefer that, it's quite simple, I just don't feel like buying a second Onn tablet at the moment.
Just note that if you want to extract the original boot image, do NOT flash the Magisk image, it will permanently erase the original boot image. There is another way, I can walk you through it.
PseudoDistant said:
I have the boot and recovery images if you want them.
I unfortunately accidentally deleted the original boot image, but I have a magisk patched image still present.
I can walk you through the process of extracting the original if you would prefer that, it's quite simple, I just don't feel like buying a second Onn tablet at the moment.
Click to expand...
Click to collapse
I oicked up one of the gen3 tablets. Do you think your way of pulling the boot image would work on it?
alarmdude9 said:
I oicked up one of the gen3 tablets. Do you think your way of pulling the boot image would work on it?
Click to expand...
Click to collapse
My way of pulling the images should work on any Android device that ships Android 8.0+, however if you got it brand new, don't update it.
Factory reset it if it downloaded an update, then disable OTA updates before enabling Wi-Fi.
You can run `adb logcat` while the update is downloading to find out where to download the OTA, and dump the boot partition from that.
From there, if you install Magisk, you can dump the recovery partition with `adb shell`.
PseudoDistant said:
Factory reset it if it downloaded an update, then disable OTA updates before enabling Wi-Fi.
You can run `adb logcat` while the update is downloading to find out where to download the OTA, and dump the boot partition from that.
From there, if you install Magisk, you can dump the recovery partition with `adb shell`.
Click to expand...
Click to collapse
Ok I will have to reset it then go from there. Do you have a guide on how to pull the image?
alarmdude9 said:
Ok I will have to reset it then go from there. Do you have a guide on how to pull the image?
Click to expand...
Click to collapse
When doing first time setup, don't connect to Wi-Fi.
Enable Developer Settings
Disable OTA Updates
Enable USB Debugging
Connect to Wi-Fi
Connect the device to your computer
Run `adb logcat > ota.txt`
Reenable OTA Updates
Go to Software Updates and start downloading the Android 12 update (If it's not the Android 12 update, disable OTA updates again after this one finishes installing, then try logcat again after rebooting)
Search for a link that looks like `https://android.googleapis.com/packages/ota-api/package/827ee737174e0e8f761bcaeb12738221a924c810.zip` in the logcat.
Put the update link in your browser, and download the zip file.
Extract the zip file
There's your boot.img, very conveniently.
The update link I have provided is for the 100074181, the 3rd gen Onn 7, if you happen to have that one then go ahead and just use my link.
Though update to Android 12 before actually using that boot.img with Magisk, it won't work with Android 11.
After you're done with that, and you're rooted.
`adb shell`
`su`
`dd if=/dev/block/by-name/recovery of=/storage/emulated/0/recovery.img`
Then connect your tablet to your PC and enable file transfer in USB settings, then just pull recovery.img out of your tablet and you have the recovery image.
PseudoDistant said:
When doing first time setup, don't connect to Wi-Fi.
Enable Developer Settings
Disable OTA Updates
Enable USB Debugging
Connect to Wi-Fi
Connect the device to your computer
Run `adb logcat > ota.txt`
Reenable OTA Updates
Go to Software Updates and start downloading the Android 12 update (If it's not the Android 12 update, disable OTA updates again after this one finishes installing, then try logcat again after rebooting)
Search for a link that looks like `https://android.googleapis.com/packages/ota-api/package/827ee737174e0e8f761bcaeb12738221a924c810.zip` in the logcat.
Put the update link in your browser, and download the zip file.
Extract the zip file
There's your boot.img, very conveniently.
The update link I have provided is for the 100074181, the 3rd gen Onn 7, if you happen to have that one then go ahead and just use my link.
Though update to Android 12 before actually using that boot.img with Magisk, it won't work with Android 11.
Click to expand...
Click to collapse
Awesome. Thank you so much I do appreciate it. Going to download the zip file because I have a 100071481. You sir are awesome!
alarmdude9 said:
Awesome. Thank you so much I do appreciate it. Going to download the zip file because I have a 100071481. You sir are awesome!
Click to expand...
Click to collapse
Update to Android 12 before using Magisk, just in case.
alarmdude9 said:
Awesome. Thank you so much I do appreciate it. Going to download the zip file because I have a 100071481. You sir are awesome!
Click to expand...
Click to collapse
Could you share the ota? This is the same model I'm using but its bricked rn
MoistSpoon said:
Could you share the ota? This is the same model I'm using but its bricked rn
Click to expand...
Click to collapse
I will look for it. Saved it to a USB drive and of course it decided to be stupid and it is repairing now. Slow going but as soon as it gets done I will look to see if it survived and if so I will get it uploaded.
MoistSpoon said:
Could you share the ota? This is the same model I'm using but its bricked rn
Click to expand...
Click to collapse
Sorry just noticed that the file that PseudoDistant posted is still good. I used this one....
https://forum.xda-developers.com/attachments/magisk_patched-25200_fvdeh-img.5794395/