Related
Hi guys, after a year and a half of running custom roms, I am sick of it. My main problem is that I do not receive SMS messages when they should arrive. I receive them hours after they have been sent. Another problem is that sometimes, I can't be called. My phone doesn't display a call, or being called at all. But somebody is calling me and my phone doesn't say anything. So this is very frustrating because you can miss important calls without you even knowing. And this has been happening to me almost on every rom tried. They all work well for some time, but after they start to screw around and not be consistent.
My question is, how can I install the stock rom from Orange Reyo Romanian (ZTE BLADE Q MAXI) so that my issues will go away? I have cwm, but it seems that the firmware at the zte site is only installable with the stock recovery, not with a custom recovery like CWM or TWRP.
So yeah, any help would be much appreciated.
just copy the update .zip from zte syte on your sdcard and then install with twrprecovery!
i test it and it work
or you can download a stok backup for spflashtool posted by me on xda for restoring the phone stok rom
search it 2-3 pages back
it has a recovery stok too included
http:// http://forum.xda-developers.com/zte-blade/general/orange-reyo-stok-rom-backup-t3154351
Thank you! But what drivers do I need to install? SP flash tool does nothing when I connect the phone to te pc
Can I install it with CWM? As i have not installed TWRP on my phone
deepside_dj said:
Thank you! But what drivers do I need to install? SP flash tool does nothing when I connect the phone to te pc
Click to expand...
Click to collapse
did you conect the phone OFF?
and the spflash tool doesnt start ?
Sent from my ZTE Blade Q Maxi using Tapatalk
The phone is off. The sp flash tool starts. But after I click download, and connect the phone to the pc, nothing happens. The SP flash tool says nothing.
deepside_dj said:
The phone is off. The sp flash tool starts. But after I click download, and connect the phone to the pc, nothing happens. The SP flash tool says nothing.
Click to expand...
Click to collapse
yea! loks like a drivers problem.
make a serch on google after "Zte handset usb driver" and install it.
the pc see your phone if turned it ON?
what windows do you have?
Sent from my ZTE Blade Q Maxi using Tapatalk
I have installed the drivers. But still doesn't work. Even when the phone is on, SP flash tool doesnt see it. I have windows 8.1. I run your zingerone rom. Maybe it is the problem that even when my phone is on, when I connect the phone, the pc doesnt see it? The pc doesnt see it at all, when i have the zingerone rom installed. SHould I install other rom and then try SP flash tool?
The backup cannot be installed with CWM?
Now, after installing drivers, i get another error. After i click download and connect my phone to pc, SP flash tool sees my phone, but de download bar is red, and after 3 seconds my phone disconects and i receive the error: PMT has changed; it must be downloaded. I have no idea what this means.
EDIT: IT WORKS! I managed to make SP flash tool see my device by flashing it. But, by flashing it, it bricked my phone. So I thought I'm screwed. But I installed the stock recovery from @vaserbanix and at least got the phone to boot, but it was stuck in bootloop. So i downloaded the update.zip from ZTE site and put it on my sd card, got into the stock recovery and managed to install the update.zip. And now my phone has the stock rom and is working flawlessly.
Thank you @vaserbanix my friend for your help. Also, how is your health? Are you feeling well, my friend?
Hi @deepside_dj,
Glad to know that you solved out your problem. I want to ask you, if you don't mind, do you have that problems regarding SMS messages and phone calls before you start installing customs ROM's? I have to ask you this because I received a Orange Reyo(Blade Q Maxi) branded by Orange, with exactly the same issue. In the company were I work, the phone was used internally, for GSM testing especially. And I understand from the test user that was using the phone, that, even if the phone was having the stock ROM on it, was having exactly the same issues sometimes.
For examples, some text messages were received just only when the phone receive a call, even if the message have been send with a few hours before, or something like this.
So, in this case, I'm wondering if actually the custom ROM's are the root cause.
Right now, I'm using the phone for test software development and also as a spare phone. And because of this, even if @vaserbanix have done a great job porting other ROM's for this phone, I already start working on a custom ROM for me to use that is going to be based on the stock one, but much more smaller and without that bloatware preinstalled on it. So I have to know at what to look after. Maybe is not the custom ROM's fault, but just an update or a wrong placed internal command that is interfering with the RIL normal execution with the radio hardware.
Best Regards,
DarKay
DarKay said:
Hi @deepside_dj,
Glad to know that you solved out your problem. I want to ask you, if you don't mind, do you have that problems regarding SMS messages and phone calls before you start installing customs ROM's? I have to ask you this because I received a Orange Reyo(Blade Q Maxi) branded by Orange, with exactly the same issue. In the company were I work, the phone was used internally, for GSM testing especially. And I understand from the test user that was using the phone, that, even if the phone was having the stock ROM on it, was having exactly the same issues sometimes.
For examples, some text messages were received just only when the phone receive a call, even if the message have been send with a few hours before, or something like this.
So, in this case, I'm wondering if actually the custom ROM's are the root cause.
Right now, I'm using the phone for test software development and also as a spare phone. And because of this, even if @vaserbanix have done a great job porting other ROM's for this phone, I already start working on a custom ROM for me to use that is going to be based on the stock one, but much more smaller and without that bloatware preinstalled on it. So I have to know at what to look after. Maybe is not the custom ROM's fault, but just an update or a wrong placed internal command that is interfering with the RIL normal execution with the radio hardware.
Best Regards,
DarKay
Click to expand...
Click to collapse
When I first got the phone, obviously, it had the stock rom. I used the stock rom for months on end, up until @vaserbanix ported the first rom for this device. While using a fresh stock rom, fresh as in directly from the factory, I didn't have any issues with calls/SMS. All came when they were supposed to. Even after using custom roms, for some time, i haven't encountered deal-breaking issues. Clearly not something as big as missing calls, that don't appear when they should etc. Well, all went good until all of a sudden I didn't receive calls. I was using the MIUI v5 rom, which is my favorite rom. I thought it might be a bug, so I flashed the rom again, but nope, the problem still persisted. Which was odd, since I was using that specific rom for months. After that, I tried many other roms ported by the one and only @vaserbanix until i settled on the Zingerone rom. This was the fastest and most clean looking rom for me, and I was happy that it ran good. Until, the issue with calls/sms not being received reappered. Which really frustrated me, because I lost an important call, without me even knowing it. That is when I had enough, so I installed the stock rom again, with a bit of work, but in the end the install was good.
So now I am using the stock rom, it has been only a day since I installed it, but it seems solid. Only time will tell. If I encounter the same issues, be sure I will report it here!
OK, thanks for the information. I wanted today to take the SIM card from the test operator to make some tests on the phone, to see if I can find something wrong with the card or the phone or at least, reproduce the issues, and found out that the SIM card was replaced. It looks like on another phone was still having the same issues. So in this case, it seems that the problem was with the SIM. I will make some logs on the phone to see if the problems resides also on it, especially now, because I modified and installed one of the custom ROM's build by @vaserbanix. Only the time will tell.
In the mean time, I have a new "toy" (Blade Q Maxi ) so I have to play with it a little bit, but I will let you know if the problems returns, or at list found the root cause of this, because I think you are going to get bored real soon of the stock ROM. See you soon.
I find Stock rom for ZTE Blade Q Maxi on this Site
kinotube.info/channel/watch/lOg52L-wBsQ
----
mega.nz/#!w8x3iADC!OsNuOELkG5SE9z5cu-gvyaIQxqFCssMmc4_GxR1W-BI
pass __ gem-flash
----
There is stock rom for ZTE Blade Q Maxi with which can move apps from phone to SD card.
But it's a full of Viruses, adware, malware and hijacking trojans.
If someone know how to remove viruses and others stufs. Or find what was change in android to be able move to SD Card, and put that change in regular clear stock rom?
Hello,
I really need to update my Galaxy S4 i9505.
I rooted it 2 years ago with help. Now I have an really old custom Recovery (PhilZ) and the old Radio/Bootloader from the last original Samsung Software I had.
I want to update my phone to Lollipop (CM12.1).
I'm a bit confused what I need to do because of the new formating that comes with Android 5.x.x.
I know, that I need to update my Recovery.
I'm a bit scared to do this with my PC and Odin because I fear a connection error because of whatever ( a bit paranoid I know...).
So I know I am able to flash a new Recovery as a Zip from my old one. BUT: How do I create a flashable .zip from an .img-File of TWRP ?
Another question is: Do I need to update my radio/bootloader? My phone does work. Sometimes the connection isn't that good but I didn't care before.
I would do the following:
- Update recovery (how ever...)
- Backup my System
- Full wipe &Install as always
Did I forget something when I came from KitKat 4.4.4 (Cm11)?
My PhoneData:
CM 11-20150330-NIGHTLY
Baseband: i9505XXUEMJ5
Kernel: CM
Can somebody help me so that I do not miss anything? I don't wanna have a Bootloop or a bricked phone... I love my phone
Greetz Yessica
https://www.androidfilehost.com/?fid=24269982086988952 - TWRP flashable zip.
Roms should work without updating bootloader and modem. But it's not that hard to update them. As long as Odin detects your phone and you follow a good guide. It should be simple. I updated mine twice and worked every time.
Thank you for the link!
Where did you find this one? In case I need to flash a Zip again?
The rest of my to do list is okay I think?
Alright! That sounds really good!
Thanks
EDIT:
Modem update: is this really necessary? I mean what happens If I don't?^^ Yeah I am Lazy
The zip can be found in the Optimized CyanogenMod 12.1 thread by AntaresOne, located in the original android development section.
It is generally recommended to update modem only if you have signal issues or other network problems. You know, if it ain't broken don't fix it.
I was trying to flash my ZTE Blade B112 with SP Flash tool and I decided to use an A110 rom, since they are identical in specifications but not model number (oops). Well that didn't go well, now I get the DRAM_FAIL error (4032). Wondering if anyone at all managed to save a backup of the stock rom this phone came with?.
Phone is detected in SP Flash Tool, red LED is on when plugged in and it connects and disconnects constantly.
Can't find it anywhere, and if that's the case, then I need to consider this phone dead and move on.
ZTE B112 (Boost Zume 5) Stock ROM
I have an almost-new B112 BZ5 that I want to root, so perhaps we could help each other.
I'm an Android noob, so please forgive dumb questions & assumptions - and enlighten me.
AFAIK, a phone has to be rooted before one can copy the ROM.
I can't find a recovery for the B112, so I think a one-click root app is the only way to go.
I tried iRoot but it failed.
I installed and ran the OneClickRoot APK. It scanned the phone, and said that it could root the phone, but it would cost me $30 (US I assume), which is more than the phone cost brand-new. The developers' website looks very professional, with promises of support incl online chat, so maybe that's the best way to go.
Recently I used KingRoot on a Moto E v1 Condor. It worked but installed some crap apps, and the phone seemed unstable, so I uninstalled it, then used ADB to flash CWM and install SuperSu.zip from the SD card. But I don't think I can do that with the B112 as I can't find a matching recovery for it. Is Kingroot OK on the B112?
So how did you root your B112?
If I can root mine, I could copy off the stock ROM for you. (Please tell me the steps ... Nandroid backup?? ... and the best way of getting it to you.)
[Edit: I have a ZTE A110 (Optus Zip) as well , and I'd like to root that too. Will the same method that roots a B112 work for A110 as well?]
Hi
When I wipe devik, data, cache and system partition using TWRP and reboot, the phone take forever to boot it stuck in LG logo. I don't understand why it stuck when I wipe those partitions. I've tried combination keys to boot in TWRP recovery but it doesn't work. Now I'm stuck. I don't know what to do. My phone is LG G3 (F460L) Android 4.4.2. Please see the photo.
EDIT: I didn't read the system partition thing before answering below... If I'm not completely wrong, your phone can't boot, because there is no system which could be loaded, so your phone is more or less empty, when you wiped the system partition. No more Android 4.4.2 :/ I don't know, why booting into TWRP doesn't work. Maybe you carefully could try to unbrick your phone and reinstall stock rom again.
Hej,
have you ever had booting problems with your phone? I'm in constant bootloop trouble with my D855. Some say it's a battery issue, which I can not confirm since I've tried 4 different ones (including 2 brand new ones). Some others say my mainboard has kind of an unrepairable defect. As I go with this possible explanation, I ordered a new used mainboard from China, hoping for it to arrive in Europe and not beeing fished by the authorities...
I can't say for sure what is the exact issue with my or your phone, the only thing I can tell is that there are tons of posts that can be found on the internet about the G3 having bootloop issues after a couple of years of normal usage. And for most users this came all of a sudden. Believe me, I've invested days of research, uncounted attempts of unbricking my phone (I thought I bricked it somehow, but it wasn't the case) and flashed stock rom and LOS as hard as I could. All ended up in my phone not running stable, crashing and then bootlooping. Sometimes (most of the times) if it's shut down and I want to turn it on, it gets stuck on the LG boot splash screen. It seems that somehow the energy management is not capable of running the phone stable under low voltage, since at least for me the probability of successfull boots slightly rises with a higher state of charge. But I can't take it for granted...
Good luck for you, I will keep reading this thread.
I wipe System Partition which contains Kitkat 4.4.2 but I already flash new ROM (CM13 Unofficial f460) after. There should be CM13 in system partition. I don't know why it can't boot. On the other hand, I can't find official firmware 4.4.2 for F460L (3hours search still no luck). I found only official firmware 6 Marshmallow which I'm afraid I won't be able to root forever if I flash it. I'm really appreciated if you can find one somewhere.
Rexkh said:
I wipe System Partition which contains Kitkat 4.4.2 but I already flash new ROM (CM13 Unofficial f460) after. There should be CM13 in system partition. I don't know why it can't boot. On the other hand, I can't find official firmware 4.4.2 for F460L (3hours search still no luck). I found only official firmware 6 Marshmallow which I'm afraid I won't be able to root forever if I flash it. I'm really appreciated if you can find one somewhere.
Click to expand...
Click to collapse
You could follow the link in this post which leads to a russian site. I saw a 4.4.2 version of Android in there. Good luck!
Thanks. I found official firmware lollipop and flash it. I've been searching for a way to root it but most of the method is for D855. Do you know if F460L Lollipop is rootable?
Rexkh said:
Thanks. I found official firmware lollipop and flash it. I've been searching for a way to root it but most of the method is for D855. Do you know if F460L Lollipop is rootable?
Click to expand...
Click to collapse
You can use the search function within the forums or search engines like startpage. I don't actually own a F460L and I'm not an expert either, so I don't know, how it works exactly. Punchin the keywords "F460L Lollipop root" into startpage.com brought me the following link as first result:
https://forum.xda-developers.com/lg-g3/general/guide-everything-lg-g3-cat-6-f460s-t3542542
Just follow the guide in OPs post
I already try LG One Click Root. It doesn't work. When it reach 45% (Looking for LG Serial Port), the phone restart (normal reboot) and it stay at 45% definitely. I manually reboot to Download Mode, still, 45%. Any suggestion?
Rexkh said:
I already try LG One Click Root. It doesn't work. When it reach 45% (Looking for LG Serial Port), the phone restart (normal reboot) and it stay at 45% definitely. I manually reboot to Download Mode, still, 45%. Any suggestion?
Click to expand...
Click to collapse
Sorry, as I'm on a D855, I don't really know. I rooted via King Root which only works with a specific Android version. I used this guide which helped me a lot: https://www.youtube.com/watch?v=8VOgM3jLas4
It's for the D855 but it could work with the F460 too. In the video description, there is a download link to the specific stock rom version for F400 models. The guide tells you where and what to download and how to install. You could try this and I'll keep reading Good Luck!
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.