Related
Hello everyone! I didn't want to root my new MOTO G 2015 but I need more storage if I want to install more app's, I saw with root permissions we can transfer full sized app's to the sd, is it true? and how? I've seen already a guide how to root moto g 2015, but know I want to know how to transfer full sized app's to the SD and then i'll decide if I want to root or not.
Do you think I should root? It will be better If i want more storage?
Is it safe? The Lollipop will be automatically installed after the root? I have no need on install other Android OS.
Thank you!
Hey! I can see that you are new here, but rooting your phone isnt gonna delete anything of your data if you search on this forum for Link2sd than you will find a tuturial for how to do that. But if you dont understand any of the words "Brick" or "fastboot" you should do some research first.
success!
HelpMeruth said:
Hey! I can see that you are new here, but rooting your phone isnt gonna delete anything of your data if you search on this forum for Link2sd than you will find a tuturial for how to do that. But if you dont understand any of the words "Brick" or "fastboot" you should do some research first.
success!
Click to expand...
Click to collapse
Hello HelpMeruth! And thank you for replying my question!
Here's what I already searched this is , i've got alot of information already but the information I got says my phone will be formatted I think. Brick I remember that word a long time ago when the PSP Scene I know it's not android but I remember it, it's like having a non funcional phone, bricked.
Here's the guide I saw: (I can't post links, if you can search on the youtube : "Moto G 3rd Gen(2015) - How to Root - Unlock Bootloader & Custom Recovery") and tell me if that guide will not brick or format my moto g 3
Any chance of getting bricked? It will remove my SIM Service? I have the phone just for a week and the warranty it's 2 here's, If I root the warranty goes out, is it worth rooting?
Thanks for the reply sir and yes i'm really new in the android scene, just came from the iOS one, got mad at iOS
I can confirm that your phone will not be formatted
The word brick means that your phone wont start up.
Its a gamble for everyone to root, so when you are gonna do it try just booting Twrp. That is the safest way to test it.
But strart with unlocking your bootloader thats already a big step for rooting (unlocking bootloader will format your data!)
If you got any questions send me message!
Its your choise to root or not
HelpMeruth said:
I can confirm that your phone will not be formatted
The word brick means that your phone wont start up.
Its a gamble for everyone to root, so when you are gonna do it try just booting Twrp. That is the safest way to test it.
But strart with unlocking your bootloader thats already a big step for rooting (unlocking bootloader will format your data!)
If you got any questions send me message!
Its your choise to root or not
Click to expand...
Click to collapse
You do NOT need to unlock bootloader in order to root.
You DO need to unlock your bootloader for TWRP, unless booted temporarily.
Sent from my MotoG3
christopherrrg said:
You do NOT need to unlock bootloader in order to root.
You DO need to unlock your bootloader for TWRP, unless booted temporarily.
Sent from my MotoG3
Click to expand...
Click to collapse
What? you have to unlock the bootloader in order to boot/flash twrp.
and with twrp you can root, how do you root with locked bootloader?
HelpMeruth said:
What? you have to unlock the bootloader in order to boot/flash twrp.
and with twrp you can root, how do you root with locked bootloader?
Click to expand...
Click to collapse
Root toolkit
http://forum.xda-developers.com/showthread.php?p=62922929
Sent from my MotoG3
christopherrrg said:
Root toolkit
http://forum.xda-developers.com/showthread.php?p=62922929
Sent from my MotoG3
Click to expand...
Click to collapse
You shouldnt be able to root with a locked bootloader, i quote: 'A locked bootloader locks write access to several partitions like the system partition. This is the reason why rooting is not able without unlocked bootloader.' found on this site https://www.quora.com/What-are-the-main-differences-between-Rooting-and-Unlocking-Bootloader
that tool just has a build in fastboot/adb and automate things for you.
(sorry for my bad english)
HelpMeruth said:
You shouldnt be able to root with a locked bootloader, i quote: 'A locked bootloader locks write access to several partitions like the system partition. This is the reason why rooting is not able without unlocked bootloader.' found on this site https://www.quora.com/What-are-the-main-differences-between-Rooting-and-Unlocking-Bootloader
that tool just has a build in fastboot/adb and automate things for you.
(sorry for my bad english)
Click to expand...
Click to collapse
Yeah after doing some research motorola devices seem to have that in place. I was speaking generally from a vanilla aosp aspect. Good find.
Sent from my MotoG3
Btw, If I install CyanogenMod it will reset my moto g firmware? Or install another firmware version? Thanks
M05K said:
Btw, If I install CyanogenMod it will reset my moto g firmware? Or install another firmware version? Thanks
Click to expand...
Click to collapse
Installing cyanogenmod will still keep you on 5.1.1 your device will just be modified (custom tweaks etc..) so if you have to unlock your bootloader it will void any warranties you have. If you don't have one or don't care just make sure to read carefully as you sound relatively new to CM and you don't want to brick your device.
Sent from my MotoG3
christopherrrg said:
Installing cyanogenmod will still keep you on 5.1.1 your device will just be modified (custom tweaks etc..) so if you have to unlock your bootloader it will void any warranties you have. If you don't have one or don't care just make sure to read carefully as you sound relatively new to CM and you don't want to brick your device.
Sent from my MotoG3
Click to expand...
Click to collapse
Yes it will be modified to cyanogenmod firmware right? So the firmware updates from MOTO G 3 I had installed will go resetted to the cyanogenmod firmware right?
M05K said:
Yes it will be modified to cyanogenmod firmware right? So the firmware updates from MOTO G 3 I had installed will go resetted to the cyanogenmod firmware right?
Click to expand...
Click to collapse
Correct.
Cm12.1 is just 5.1.1 that's why I said it would.
You may see custom aosp 6.0 ROMs before any real factory builds.
Sent from my MotoG3
Hi peps,
I just switched from my crappy HTC One X to my new Moto G3 and I'm in love!
I don't really want a custom ROM, but I'd like to undervolt this babe. But since a root requires unlocking the bootloader = voiding the manufacturers warranty, I don't really wanna do that..
I've bought it over Amazon and I live in the EU, so I technically still have the retailer's warranty and Amazon would replace it without a hassle, but yeah.. it's new and all.
But I know there are apps like towelroot, KingRoot and what not, do they work with the Moto G3? I'm on 5.1.1.
Jut install SuperSU ZIP using TWRP recovery
Osid said:
Jut install SuperSU ZIP using TWRP recovery
Click to expand...
Click to collapse
Could you read my post first?
squid2 said:
Your bootloader must be unlocked to use this recovery.
Click to expand...
Click to collapse
unlocking bootloader = voiding warranty.
shawly said:
Could you read my post first?
unlocking bootloader = voiding warranty.
Click to expand...
Click to collapse
If you're worried about voiding the warranty, you're on the wrong site.
Ragarianok said:
If you're worried about voiding the warranty, you're on the wrong site.
Click to expand...
Click to collapse
Thanks for this unnecessary input. :good:
On previous versions of Android there were exploits that allowed rooting the phone without unlocking the bootloader, which means you could keep your warranty and I just asked if it works on the current Moto G3 with Lollipop 5.1, why do you have to be such a smartass? It's a normal question, why can't I have a normal answer?
I used to root in one click in just one method on my previous phone xperia sp but i dont know this phone have any toll which will work or not?
shawly said:
Thanks for this unnecessary input. :good:
On previous versions of Android there were exploits that allowed rooting the phone without unlocking the bootloader, which means you could keep your warranty and I just asked if it works on the current Moto G3 with Lollipop 5.1, why do you have to be such a smartass? It's a normal question, why can't I have a normal answer?
Click to expand...
Click to collapse
Being a smartass is kind of my thing.
You're afraid to unlock your device's bootloader because you'll lose the warranty, but you're perfectly fine with risking the security of your device by rooting it, right? Seems odd to me, but whatever.
Generally speaking, both KingRoot and TowelRoot are used on devices where using those two methods are the only way to root those devices.
Unlocking the bootloader will have no ill effect on your device other than voiding the warranty, and, if you're worried about voiding your warranty, you shouldn't be trying to modify your device.
In the words of the always optimistic Ms. Frizzle: "Take chances, make mistakes, and get messy!"
---------- Post added at 10:39 AM ---------- Previous post was at 10:33 AM ----------
zephiK said:
Just unlock the bootloader and root. You're making it too difficult for yourself, the whole point of the bootloader being locked is to prevent changes being made to the system.
Its like saying, you're going to break your windows to get into your house when you can just unlock the door.
Just unlock the bootloader and flash supersu for root.
Click to expand...
Click to collapse
Also this.
Ragarianok said:
Being a smartass is kind of my thing.
You're afraid to unlock your device's bootloader because you'll lose the warranty, but you're perfectly fine with risking the security of your device by rooting it, right? Seems odd to me, but whatever.
Generally speaking, both KingRoot and TowelRoot are used on devices where using those two methods are the only way to root those devices.
Unlocking the bootloader will have no ill effect on your device other than voiding the warranty, and, if you're worried about voiding your warranty, you shouldn't be trying to modify your device.
In the words of the always optimistic Ms. Frizzle: "Take chances, make mistakes, and get messy!"
Click to expand...
Click to collapse
Who said I'm afraid of unlocking the bootloader? Who said I never unlocked the bootloader of other phones before?
I just don't wanna lose my warranty in the first two or three months, in case my phone breaks unexpectedly, I also don't plan on using custom roms, I just want the root features so I can undervolt like I said and IF I could root it permanently without unlocking the bootloader, why not?
I'm not worried, it would just be convenient to have root without losing the warranty, that's it.
As far as I know you may be able to do it search kingroot in Google then download the apk and install it then open in and follow the instructions
shawly said:
Who said I'm afraid of unlocking the bootloader? Who said I never unlocked the bootloader of other phones before?
I just don't wanna lose my warranty in the first two or three months, in case my phone breaks unexpectedly, ...
Click to expand...
Click to collapse
Then leave the device stock ...
If you want the best of both worlds (root & warranty), then go buy a Nexus. Motorola drew a line in the sand as to what they will support, while still empowering owners with the option to unlock the bootloader.
Sent from my MotoG3 using Tapatalk
Ragarianok said:
If you're worried about voiding the warranty, you're on the wrong site.
Click to expand...
Click to collapse
Not really. While I've unlocked my previous phones, my new g3 I'm leaving locked for the first year, while the warranty lasts. But this site still has a few helpful stuff.
Ragarianok said:
...You're afraid to unlock your device's bootloader because you'll lose the warranty, but you're perfectly fine with risking the security of your device by rooting it, right? Seems odd to me, but whatever...if you're worried about voiding your warranty, you shouldn't be trying to modify your device...
Click to expand...
Click to collapse
He just wants the warranty, but he doesn't care about rooting it because there's not really anything wrong with rooting if you know what you're doing and how to fix it.
Sent from my MotoG3 using XDA Free mobile app
---------- Post added at 01:03 PM ---------- Previous post was at 01:03 PM ----------
And to answer the question; you need to unlock the bootloader to root
Sent from my MotoG3 using XDA Free mobile app
Question, I attempted to use towelroot on my stock g3 and got a message saying my phone is not supported. Any help is greatly appreciated. Also, fairly newbish, so be gentle!!
Jdwright0819 said:
Question, I attempted to use towelroot on my stock g3 and got a message saying my phone is not supported. Any help is greatly appreciated. Also, fairly newbish, so be gentle!!
Click to expand...
Click to collapse
Towelroot is exploiting a bug in the Linux Kernel in order to root a device. This bug was already fixed in June 2014.
On all Kernels with a later build date Towelroot will most likely not work.
For sure it will not work on the Moto G3 with a kernel build date more than one year after this bug was fixed.
Thanks!
shawly said:
Hi peps,
I just switched from my crappy HTC One X to my new Moto G3 and I'm in love!
I don't really want a custom ROM, but I'd like to undervolt this babe. But since a root requires unlocking the bootloader = voiding the manufacturers warranty, I don't really wanna do that..
I've bought it over Amazon and I live in the EU, so I technically still have the retailer's warranty and Amazon would replace it without a hassle, but yeah.. it's new and all.
But I know there are apps like towelroot, KingRoot and what not, do they work with the Moto G3? I'm on 5.1.1.
Click to expand...
Click to collapse
It's probably been answered already but those exploits are security flaws with the SE Linux system and so with each release of android these have been patched, by 5.1 these security holes have been fixed and now by locking the bootloader
It's like just locking down and modifications to the system partition so unfortunately you can't root without unlocking, unless you have android versions lower down
shawly said:
Thanks for this unnecessary input. :good:
On previous versions of Android there were exploits that allowed rooting the phone without unlocking the bootloader, which means you could keep your warranty and I just asked if it works on the current Moto G3 with Lollipop 5.1, why do you have to be such a smartass? It's a normal question, why can't I have a normal answer?
Click to expand...
Click to collapse
I have unlocked bootloader and i m on stock recovery amd on stock rom without rooted. Can i install twrp without pc
Are you root yet
I have moto g 3, its bootloader is unlpcked but when I tried to root it using SuperSU and twrp recovery then I ended up corrupting it software. Can anybody tell me how to safely root it...?
Ankur1 said:
I have moto g 3, its bootloader is unlpcked but when I tried to root it using SuperSU and twrp recovery then I ended up corrupting it software. Can anybody tell me how to safely root it...?
Click to expand...
Click to collapse
What version of TWRP did you use coz I know there were some bugs on the moto range with TWRP 2.X.
I would completely wipe device using stock recovery, including dalvic/cache/data everything just to be on the safe side, then download the TWRP zip to your computer and flash it on using ADB.
Boot up normally and move the superSU zip from the link to your phones internal storage. Then reboot to TWRP, select install and pick the zip file.
superSU.zip:
http://dl-1.va.us.xda-developers.com/3/6/5/5/4/0/1/BETA-SuperSU-v2.62-3-20151211162651.zip?key=u0OeGV4-4s02KJXqrXJ-gg&ts=1466705675
If you get stuck this might help:
https://motog3.com/unlock-bootloader-install-twrp-root-moto-g3/
No longer works
Osid said:
Jut install SuperSU ZIP using TWRP recovery
Click to expand...
Click to collapse
Perhaps you can offer wisdom on this? I rooted my Moto G 3rd Gen once, wrecked something and had to go back to factory, then try to reroot again. Problem. No matter what I do in setting the device back to factory, the bootloader stays unlocked and reads the system software as "modified" which then seems to bork installing SuperSU. I install SuperSU via twrp and it goes fine, no errors, but when I reboot the system is lost in a loop of the "bootloader unlocked" screen.
So I cannot RE-lock the bootloader (ala setting the phone back to true factory) and after I flash SuperSU the phone refuses to successfully bootup.
Any aid? Ideas?
I had failed to backup my phone the first time with twrp and so to set to factory I downloaded the stock retail xml.zip for my phone and reflashed the entire thing via fastboot. Reinstall twrp, and try to root and the endless boot loop begins.
So I came to this thread to look into the possibility rooting my phone via another means that MIGHT work.
Hi guys i want to share with you this methode to unlock bootloader on Oreo for Nokia 3 go to this thread and requests the files from @bigrammy
This is the thread link : https://forum.xda-developers.com/no...-t3708129/post76293046?nocache=1#post76293046
Don't forget to hit thank's to him and me 12 thanks is not enough ??
This methode work with So Flashtool ?
I'm going to make SPflashTool working. I have some issue
Riadh300 said:
Hi guys i want to share with you this methode to unlock bootloader on Oreo for Nokia 3 go to this thread and requests the files from @bigrammy
This is the thread link : https://forum.xda-developers.com/no...-t3708129/post76293046?nocache=1#post76293046
Don't forget to hit thank's to him and me 12 thanks is not enough ?
Click to expand...
Click to collapse
Thanks for your enthusiasm but my method does not Unlock the bootloader so you should change your thread title.
As I told you I will open a thread when the method is fully tested by a few advanced user's who are testing it now and you will be given full credit for all your help.
I do not want to risk anyone bricking their phones due to rushing. Many none advanced users bricked their sony c4 phones by Not following my instructions so I need this to be 100% clear and fully tested I hope you understand.
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Riadh300 said:
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Click to expand...
Click to collapse
If the bootloader was unlocked fully you would be able to use fastboot to flash the device but we cannot so the bootloader is still locked to all intense purposes.
The secure boot chain does appear to be broken so we can use SPFlashTool to flash and boot our TWRP recovery but the secure boot chain may still be working if you have never unlocked the bootloader before like on Android 7.x. This means TWRP may Not boot up for everyone. Like I said it needs to be fully tested.
bigrammy said:
If the bootloader was unlocked fully you would be able to use fastboot to flash the device but we cannot so the bootloader is still locked to all intense purposes.
The secure boot chain does appear to be broken so we can use SPFlashTool to flash and boot our TWRP recovery but the secure boot chain may still be working if you have never unlocked the bootloader before like on Android 7.x. This means TWRP may Not boot up for everyone. Like I said it needs to be fully tested.
Click to expand...
Click to collapse
Thanks for this informations ! ?
Riadh300 said:
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Click to expand...
Click to collapse
Actually, spflashtool bypasses the bootloader in this instance, so the bootloader is untouched and you still flash twrp
---------- Post added at 08:35 AM ---------- Previous post was at 08:02 AM ----------
bigrammy said:
I do not want to risk anyone bricking their phones due to rushing. Many none advanced users bricked their sony c4 phones by Not following my instructions so I need this to be 100% clear and fully tested I hope you understand.
Click to expand...
Click to collapse
Not to be pessimistic, but you do realise that even with all your precautions,people will still not read properly and will still brick their phones, no matter how many precautions you take. Even if you had an app that requires you to click one button to do everything,there are still people who will do it wrong. That said I think I know of one or 2 people in this Nokia 3 forum who were able to recover their phones using spflashtool AFTER the phone couldn't even be detected by their pc, even OST flashing was not possible .
Another thing is, all the Nokia 3 is last year's phone, I wonder how many experienced users will be buying the phone now, and experienced people are probably not the best way to get something 100% tested, because they know the right steps to take.
I think you should make your method public after you hear from SkaboXD
redweaver said:
Another thing is, all the Nokia 3 is last year's phone, I wonder how many experienced users will be buying the phone now, and experienced people are probably not the best way to get something 100% tested, because they know the right steps to take.
I think you should make your method public after you hear from SkaboXD
Click to expand...
Click to collapse
Sorry I replied to your PM before seeing this.
True there is no accounting for people but I don't want to get bogged down by noob's. If you and maybe SkaboXD would like to open a thread and manage it using the method then that would be fine by me as long as credit is give to Riadh300 the original tester and who informed me SPFlashTool still worked and myself of course.
Please read my PM about the bootloader condition as I recommend only previously unlocked devices try this for now until tested by Advanced user able to recover the device should anything go wrong (EFuse Blown).
bigrammy said:
Sorry I replied to your PM before seeing this.
True there is no accounting for people but I don't want to get bogged down by noob's. If you and maybe SkaboXD would like to open a thread and manage it using the method then that would be fine by me as long as credit is give to Riadh300 the original tester and who informed me SPFlashTool still worked and myself of course.
Please read my PM about the bootloader condition as I recommend only previously unlocked devices try this for now until tested by Advanced user able to recover the device should anything go wrong (EFuse Blown).
Click to expand...
Click to collapse
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
redweaver said:
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
Click to expand...
Click to collapse
Before on 7.0 I flashed a TWRP I was working on via SPFlashTool bootloader locked and ended up in a never ending recovery bootloop which none advanced users may find difficult to get out of now this may of been because I screwed up the TWRP or more likely because the bootloader was Locked.
I did not try any other TWRP's until I was bootloader Unlocked and I have not had the recovery bootloop since.
Not sure about OST as SPFlashTool is by far the best tool for MediaTek devices and recovery of said devices remember the SoC manufacturer knows best and I only ever see problems when the OEM's try to move away from it like Sony did.
Happy for you to take the lead I am too busy in other threads to worry about it
bigrammy said:
Before on 7.0 I flashed a TWRP I was working on via SPFlashTool bootloader locked and ended up in a never ending recovery bootloop which none advanced users may find difficult to get out of now this may of been because I screwed up the TWRP or more likely because the bootloader was Locked.
I did not try any other TWRP's until I was bootloader Unlocked and I have not had the recovery bootloop since.
Not sure about OST as SPFlashTool is by far the best tool for MediaTek devices and recovery of said devices remember the SoC manufacturer knows best and I only ever see problems when the OEM's try to move away from it like Sony did.
Happy for you to take the lead I am too busy in other threads to worry about it
Click to expand...
Click to collapse
So how did you get your phone back anyway?
redweaver said:
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
Click to expand...
Click to collapse
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
redweaver said:
So how did you get your phone back anyway?
Click to expand...
Click to collapse
:laugh: Sorry mate this is what I mean. I simply don't have the time to sit answering every single question as there is no short answers
I hope you understand.
SkaboXD said:
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
Click to expand...
Click to collapse
OK, one thing though, before flashing the recovery you might want to do a backup of the stock recovery if you don't already have one. That's what I did, so after I got root, flashed back my stock recovery. Magisk is the root manager ,
---------- Post added at 12:17 PM ---------- Previous post was at 12:12 PM ----------
bigrammy said:
:laugh: Sorry mate this is what I mean. I simply don't have the time to sit answering every single question as there is no short answers
I hope you understand.
Click to expand...
Click to collapse
oh you mean you went through hoops to get your phone back? I thought you would say you got a stock recovery somewhere and flashed using spflashtool or used the ost method. I didn't actually expect you to outline the steps you used. BTW, first time I flashed twrp AFTER unlocking bootloader, I got stuck in a recovery bootloop too. I had to flash my phone with OST then retry the process again.
One other thing, I think OST is actually a propriety software that is supposed to work for lots of phones, at least I know that users of other non mediatek Nokia phones also use it to recover their phones (with the corresponding stock images of course)
SkaboXD said:
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
Click to expand...
Click to collapse
Magisk hide allows you get OTA's see the Magisk thread and yes it will work on any android version.
@redweaver
I am glad you got out of the loop but your clearly a more advanced user hence why I ask you to test. :good:
The OST is very convoluted for use on MediaTek devices and is very unnecessary it also requires unnecessary FIH software to be installed on the phone to work properly.
They likely choose this method to work across different SoC's but it's not what MediaTek use SPFlashTool is MediaTeks own software.
EDIT: Sorry lost internet for a while then.
I continue: Good news is I do not think they will be able to remove SPFlashTool use as it's binary on device which lives on a none volatile area ram chip or radio chip and is loaded at the factory so I doubt it can be updated via a OTA. :fingers-crossed:
Sony actually replaced this and this is the only device I have been unable to recover and even Sony were replacing the boards of bricked devices but if they had left the Mediatek binary in there it would not of been a issue as SPFlashTool would of been able to recover them. :good:
guys, old thread, i know, different device, i know, but ive been in the dark and this is what most resembles my issue.
any hints would be appreciated, read all 2 pages, can you believe it? im a very average xda enthusiast.
worries out of the way, my sincere thanks beforehand follow.
issue
carrier doesnt get in the way
oem doesnt get in the way
oem unlock toggle, check, adb debugging, you and i know the drill, no driver/cable issues
cannot for the life of me unlock bootloader, this one would take the newer command, however i tried them all ive come accross to no avail
output encourages me to unlock first, howwever not a clue is given as to how to accomplish it. this isnt the flash a file type of unlocking, either, at least not oem provided. going nuts.
go ahead and feel free to issue "advanced" directions (meaning, like your voicemail, instead of "for voicemail configurations press 8" and just "configurations 8"
spreatrum, not mtk
x120c
came with oreo go, treble enabled per getprop
i dont know what else, please
So today i decided to downgrade from V10.2.1.0.PEEMIXM to V10.0.11.0.PEEMIFH because i was having serious battery issues on V10.2.1.0.
I should have looked into it more carefully but nope, my dumb ass decided to install the older ROM version via the Updater in Settings and it bricked my device in the process.
Now my device is stuck on boot with the message "The system has been destroyed. Press power button to shutdown".
I have the global version with the bootloader locked. The only thing i have access to now is fastboot.
Any ways i can recover from this? Any help is greatlyyy appreciated.
You can try to unlock bootloader with fastboot mode, but i'm not sure that works because the system has been destroyed and your account has been destryed too. I think, the best for you, is to send it in warranty for repair. I have bricked a Redmi Note 4 like that and even with the test point method, he has never work again.
boxof said:
So today i decided to downgrade from V10.2.1.0.PEEMIXM to V10.0.11.0.PEEMIFH because i was having serious battery issues on V10.2.1.0.
I should have looked into it more carefully but nope, my dumb ass decided to install the older ROM version via the Updater in Settings and it bricked my device in the process.
Now my device is stuck on boot with the message "The system has been destroyed. Press power button to shutdown".
I have the global version with the bootloader locked. The only thing i have access to now is fastboot.
Any ways i can recover from this? Any help is greatlyyy appreciated.
Click to expand...
Click to collapse
If you can find the fastboot version of the ROM you were on before downgrading just flash it with miflash
Azev said:
You can try to unlock bootloader with fastboot mode, but i'm not sure that works because the system has been destroyed and your account has been destryed too. I think, the best for you, is to send it in warranty for repair. I have bricked a Redmi Note 4 like that and even with the test point method, he has never work again.
Click to expand...
Click to collapse
Fortunately for me i was able to unlock the bootloader. Likely because i registered my device since i first got it (about 1 month now), so i think i must have met the wait time requirement and it was fine that i couldn't access the system.
Mackay53 said:
If you can find the fastboot version of the ROM you were on before downgrading just flash it with miflash
Click to expand...
Click to collapse
I tried miflash the first time with my bootloader still locked but miflash refused to work with a locked bootloader.
So i tried again with my bootlocker unlocked and it worked as expected.
Lesson learnt. All is well again and i'm able to keep my bootloader locked with the "flash_all_lock" option.
Thank you so much for all the help!
boxof said:
Fortunately for me i was able to unlock the bootloader. Likely because i registered my device since i first got it (about 1 month now), so i think i must have met the wait time requirement and it was fine that i couldn't access the system.
I tried miflash the first time with my bootloader still locked but miflash refused to work with a locked bootloader.
So i tried again with my bootlocker unlocked and it worked as expected.
Lesson learnt. All is well again and i'm able to keep my bootloader locked with the "flash_all_lock" option.
Thank you so much for all the help!
Click to expand...
Click to collapse
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
nsynsy said:
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
Click to expand...
Click to collapse
Unless you have got unlock permission and linked phone to account you can't unlock.
Unlock like how you would normally - put the phone into fastboot, connect it to your PC, and run the mi unlock tool. For this to work, hopefully you have associated your device to a mi account and have met the unlock requirements ie. surpassed the waiting period. Otherwise you're out of luck as there is no other ways (that i know of) to register the device now as you can't get into the system.
As a last resort you can try opening up the back of the phone and flash new firmware using the test point if unlocking is not possible. I'm not sure how or where the testing point is located exactly, but it's a possible solution that i found while researching when my device was bricked. Good luck!
nsynsy said:
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
Click to expand...
Click to collapse
u say u can only access to fastboot..
How about pressing volume up and power button? can u enter in stock mi recovery with mi assistant options?
Hello there
I just ordered my V50 European model to replace my V30, which suddenly had a modem problem it seems cause it stoped reading any sim card without any damage, humidity or obvious short circuit it seems even after meticulously checking the insides abd trials and errors.
Ok I just wanted to ask because I am kind of confused. In the unlocked bootloader versions, isn't it possible to install a custom recovery and get root that way just like with any phone that I unlocked in the past? Meaning I always thought that if you have an unlocked bootloader you can always get root access easily. But is it not this way for now and so we have to wait for a root or custom recovery exploit even if we have an unlocked bootloader from lg?
Just wanted to clarify that and thank you for your time.
Greetings from Greece
skydogis said:
Hello there
I just ordered my V50 European model to replace my V30, which suddenly had a modem problem it seems cause it stoped reading any sim card without any damage, humidity or obvious short circuit it seems even after meticulously checking the insides abd trials and errors.
Ok I just wanted to ask because I am kind of confused. In the unlocked bootloader versions, isn't it possible to install a custom recovery and get root that way just like with any phone that I unlocked in the past? Meaning I always thought that if you have an unlocked bootloader you can always get root access easily. But is it not this way for now and so we have to wait for a root or custom recovery exploit even if we have an unlocked bootloader from lg?
Just wanted to clarify that and thank you for your time.
Greetings from Greece
Click to expand...
Click to collapse
There is no custom recovery yet, but rooting with fastboot and some other stuff is not a very device specific task in general. The guide to root the g8s should be exactly what you need.
Any progress with the root?
G0bl1n said:
Any progress with the root?
Click to expand...
Click to collapse
Dude the g8s people have already managed to root it just look at their guide and use kdztools to get the boot img to patch with magisk
I was wondering if the original poster succeeded with the root. I was also considering to buy the European version but it's nowhere to find here in US.