Long story short, hopped over to android following years and years of using IOS.
Bought a nexus 6p, learnt about root, gained root access to the 6p, and began installed root apps.
This morning, i installed Gsam battery monitor root companion, found out it broke the normal Gsam battery monitor app, tried to uninstall the gsam root companion several times. Everytime i uninstalled it and rebooted, it would just reappear on the phone and wouldn't actually uninstall properly at all.
On the third go, it rebooted into the red triangle " Your device is corrupt. It can't be trusted and may not work properly." and is stuck on the google logo.
Accessed recovery and tried to restore the nandroid backup, no luck, still boots up to red triangle and is stuck on google logo.
Accessed recovery and tried to restore to factory default, no luck, still boots up to red triangle and is stuck on google logo.
How do i fix my phone now? Any help would be greatly appreciated.
red triangle with the android mascot logo?
if so, put it into fastboot and reinstall recovery and see if that worked
gd6noob said:
red triangle with the android mascot logo?
if so, put it into fastboot and reinstall recovery and see if that worked
Click to expand...
Click to collapse
Its just a red triangle with an exclamation mark inside.
I can't post an image because i am a new member and need at least 10 posts.
https://support.google.com/nexus/answer/6185381?hl=en - It says it should dismiss by itself.
chichu_9 said:
- It says it should dismiss by itself.
Click to expand...
Click to collapse
The red logo does disappear and the device transitions to the black and white google boot logo.
It is here where the device becomes hung, i assume it is because the boot.img or boot files have been damaged, but i'm just guessing. What i am confused about is if the boot files are damaged, the nandroid restore should fix this problem (shouldn't it?), but it doesn't.
radaga5t said:
Long story short, hopped over to android following years and years of using IOS.
Bought a nexus 6p, learnt about root, gained root access to the 6p, and began installed root apps.
This morning, i installed Gsam battery monitor root companion, found out it broke the normal Gsam battery monitor app, tried to uninstall the gsam root companion several times. Everytime i uninstalled it and rebooted, it would just reappear on the phone and wouldn't actually uninstall properly at all.
On the third go, it rebooted into the red triangle " Your device is corrupt. It can't be trusted and may not work properly." and is stuck on the google logo.
Accessed recovery and tried to restore the nandroid backup, no luck, still boots up to red triangle and is stuck on google logo.
Accessed recovery and tried to restore to factory default, no luck, still boots up to red triangle and is stuck on google logo.
How do i fix my phone now? Any help would be greatly appreciated.
Click to expand...
Click to collapse
After a root went bad I had the same thing happen. I just used SkipSoft ToolKit and restored back to a stock image (MDB08L).
The corruption message disappeared.
Take a look at this guide By Heisenberg as it will help with some details.
The few times I flashed/reset the phone, I accidentally muddled up some steps. Specifically the flashing the boot and bootloader images.
Code:
[U]fastboot flash bootloader X:/bootloader.img[/U]
fastboot reboot bootloader
fastboot flash radio X:/radio.img
fastboot reboot bootloader
[U]fastboot flash boot X:/boot.img[/U]
fastboot erase cache
fastboot flash cache X:/cache.img
fastboot flash recovery X:/recovery.img
fastboot flash system X:/system.img
fastboot flash vendor X:/vendor.img
I would accidentally flash the bootloader.img image over the boot.img and cause the error, specifically the one you mentioned. I had to go through the flashing process VERY carefully again, and when flashing .imgs for root acess over to the stock ones.
I know is sounds trivial and I'm not saying you don't understand it, but give it a try and see if this resolves the issue. double check your lines and triple check your images (make sure there are NO spaces in the bootloader/boot img file directories. or_replace_spaces_with_underscores). I don't know how many times I have screwed up and it was because of a dash in the wrong spot or space in the .img directory. Let us know how you go.
Awesome!
Thank you very much everyone. I will try once i get home from work.
You have all been so helpful. Such a good community.
I hoped it worked out for you
urbanpitch said:
I hoped it worked out for you
Click to expand...
Click to collapse
Yep i was able to restore the phone via the heisenberg guide. Thanks!
radaga5t said:
Yep i was able to restore the phone via the heisenberg guide. Thanks!
Click to expand...
Click to collapse
Was just about to post a link to my guide but it looks as though you already got everything sorted out. I'm glad my little guide was able to assist you.
Heisenberg said:
Was just about to post a link to my guide but it looks as though you already got everything sorted out. I'm glad my little guide was able to assist you.
Click to expand...
Click to collapse
I'm having the very same issue and I don't understand what I'm supposed to do. Exact same issue a OP. I use the Mskip toolkit to the letter and that got me a bootloop. I have TWRP installed and I can access it. How can I recover my phone? Thanks in advance
---------- Post added at 11:24 PM ---------- Previous post was at 11:17 PM ----------
radaga5t said:
Awesome!
Thank you very much everyone. I will try once i get home from work.
You have all been so helpful. Such a good community.
Click to expand...
Click to collapse
Hey man, could you tell me the exact steps you took to fix yours? I'm having the same exact issue after having use that toolkit.
barondebxl said:
I'm having the very same issue and I don't understand what I'm supposed to do. Exact same issue a OP. I use the Mskip toolkit to the letter and that got me a bootloop. I have TWRP installed and I can access it. How can I recover my phone? Thanks in advance
Click to expand...
Click to collapse
Just go to my guide and follow the instructions in section 9. You'll need to look at the prerequisites section at the beginning of the OP first so you can install the latest version of adb/fastboot via the SDK.
Heisenberg said:
Just go to my guide and follow the instructions in section 9. You'll need to look at the prerequisites section at the beginning of the OP first so you can install the latest version of adb/fastboot via the SDK.
Click to expand...
Click to collapse
Cool ill give it a shot. Thank you. I'm all out of thanks for today
---------- Post added at 11:53 PM ---------- Previous post was at 11:35 PM ----------
Heisenberg said:
Just go to my guide and follow the instructions in section 9. You'll need to look at the prerequisites section at the beginning of the OP first so you can install the latest version of adb/fastboot via the SDK.
Click to expand...
Click to collapse
Im sorry but I'm completely lost. I have downloaded the factory images of my build, I have extracted the files but there isn't any bootloader.img and radio.img. When I click the extracted file it asks me if I want to download a windows application to open it.
barondebxl said:
Cool ill give it a shot. Thank you. I'm all out of thanks for today
---------- Post added at 11:53 PM ---------- Previous post was at 11:35 PM ----------
Im sorry but I'm completely lost. I have downloaded the factory images of my build, I have extracted the files but there isn't any bootloader.img and radio.img. When I click the extracted file it asks me if I want to download a windows application to open it.
Click to expand...
Click to collapse
You'll need to find a program that can extract the "tar.gz" compression format.
Heisenberg said:
You'll need to find a program that can extract the "tar.gz" compression format.
Click to expand...
Click to collapse
Ok thank you. 7zip works
barondebxl said:
I'm having the very same issue and I don't understand what I'm supposed to do. Exact same issue a OP. I use the Mskip toolkit to the letter and that got me a bootloop. I have TWRP installed and I can access it. How can I recover my phone? Thanks in advance
---------- Post added at 11:24 PM ---------- Previous post was at 11:17 PM ----------
Hey man, could you tell me the exact steps you took to fix yours? I'm having the same exact issue after having use that toolkit.
Click to expand...
Click to collapse
Basically i followed step 9 of Heisenberg's guide.
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
So i flashed all of the above minus the user data and re-locking the bootloader.
Let me know if you need any more info.
radaga5t said:
Basically i followed step 9 of Heisenberg's guide.
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
So i flashed all of the above minus the user data and re-locking the bootloader.
Let me know if you need any more info.
Click to expand...
Click to collapse
Thanks bud. I'm lost still. I have all the files needed in a folder I called " images" on my desktop. Do I have to write these commands you posted word for word? I mean I know I have to replace with my file name but for example I have the MDB08L so do I do : fastboot flash bootloader C:\angler\images\bootloader-angler-angler-02.01.img ( in my case) even though the folder is on my desktop?
Edit: I tried and it gave me an error saying it cant load it. So frustrating
barondebxl said:
Thanks bud. I'm lost still. I have all the files needed in a folder I called " images" on my desktop. Do I have to write these commands you posted word for word? I mean I know I have to replace with my file name but for example I have the MDB08L so do I do : fastboot flash bootloader C:\angler\images\bootloader-angler-angler-02.01.img ( in my case) even though the folder is on my desktop?
Edit: I tried and it gave me an error saying it cant load it. So frustrating
Click to expand...
Click to collapse
You got an error because you're pointing fastboot to a location where the file doesn't exist. If you had followed my guide and placed the files in C:\angler\images\ then the command would be correct, but you've placed the files in a different location, therefore you need to type the commands so that they include the path to where the files are actually located on your PC.
There's an easy way to do it, type the first portion of the command, for example "fastboot flash bootloader " (make sure there's a space after the last character), then you can grab the appropriate file with your mouse and drag/drop it into the command terminal window and the file path will be completed automatically for you, then just hit enter to execute the command.
Heisenberg said:
You got an error because you're pointing fastboot to a location where the file doesn't exist. If you had followed my guide and placed the files in C:\angler\images\ then the command would be correct, but you've placed the files in a different location.
You need to type the commands so that they include the path to where the files are actually located on your PC. There's an easy way to do it, type the first portion of the command, for example "fastboot flash bootloader " (make sure there's a space after the last character), then you can grab the appropriate file with your mouse and drag/drop it into the command terminal window and the file path will be completed automatically for you, then just hit enter to execute the command.
Click to expand...
Click to collapse
Thanks guys I finally figured it out. I'm at flashing the system and its taking a while obviously. Its actually easy...when you know what youre doing. Thank you so very much to the both of you!
Edit: back up and running! I was just frustrated cause I just got the phone this afternoon that's why. You guys are awesome
---------- Post added at 01:48 AM ---------- Previous post was at 01:36 AM ----------
barondebxl said:
Thanks guys I finally figured it out. I'm at flashing the system and its taking a while obviously. Its actually easy...when you know what youre doing. Thank you so very much to the both of you!
Edit: back up and running! I was just frustrated cause I just got the phone this afternoon that's why. You guys are awesome
Click to expand...
Click to collapse
One last question, whats the best method to root MDB08L? I want that chroma rom
Related
i used nexus root tool kit to update nexus 4 from 4.4 to 5.0... all done in pc but mobile is stuck in boot loop. can anyone tell me how can i restore my phone to normal working...
Please help me i am noob here
is there any one who can help me here
i thought i will get ans with in 1hr... still waiting if someone can help
letsnexus said:
i thought i will get ans with in 1hr... still waiting if someone can help
Click to expand...
Click to collapse
This is why we don't recommended using tool kits. You should try flashing the factory image using fastboot.
Sent from my Nexus 9 using XDA Free mobile app
Same here, i tried re-flashing many times. Darn that nexus root toolkit
any suggetion or link which can help me to use fastboot use and install stock rom
thank alot for help
I am currently in the same position ! Used a toolkit too, always have.
This is why you never use a Toolkit, it's always been mentioned around in XDA that this has always been a developer website of learning and knowledge. You must always know what goes on behind than just blindly flashing things. It's a rule of thumb that you're more likely to brick your phone with a Toolkit than by yourself. Easiest step as follows.
1. Download factory image
2. Download ADB files
3. Make a folder and extract the adb files and factory image inside the same folder.
4. Plug the phone in bootloader mode or simply type adb reboot bootloader (Developer options must be enabled and USB Debugging) by exiting the folder, holding shift, right clicking the folder and pressing open command window and typing the command.
5. Every factory image comes with a flashall.bat, double click it and voila. Updates like it should. (User data will be wiped)
If you don't want your userdata to be wiped, simply open flashall.bat with notepad++, erase the '-w' in "fastboot -w update image" and save the file and launch it again.
Sent from my HTC One_M8 using Tapatalk
I will try that way later when I get in, I would have assumed that the toolkit did exactly those steps though, just an easy to use frontend
hazwheel said:
I will try that way later when I get in, I would have assumed that the toolkit did exactly those steps though, just an easy to use frontend
Click to expand...
Click to collapse
Go to stock recovery and do factory data reset and reboot phone. First time boot takes very long time (around 10 to 15 minutes). After successfully boot into android L check for the storage space. If it says only 5 GB available instead of 12 GB (My nexus is 16GB) then Go to Settings > Backup & Reset and select Factory data reset.
I had experienced these issues when upgrading to Lollypop and solved them on my own.
Note: If you were not able to boot into stock recovery, try twrp recovery. you have to install it using fastboot
fastboot flash recovery <filename.img>
letsnexus said:
any suggetion or link which can help me to use fastboot use and install stock rom
thank alot for help
Click to expand...
Click to collapse
although the link is for kitkat but the same method applies to flashing lollipop
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
moorthidaniel said:
Go to stock recovery and do factory data reset and reboot phone. First time boot takes very long time (around 10 to 15 minutes). After successfully boot into android L check for the storage space. If it says only 5 GB available instead of 12 GB (My nexus is 16GB) then Go to Settings > Backup & Reset and select Factory data reset.
I had experienced these issues when upgrading to Lollypop and solved them on my own.
Note: If you were not able to boot into stock recovery, try twrp recovery. you have to install it using fastboot
fastboot flash recovery <filename.img>
Click to expand...
Click to collapse
OK, I was able to get into recovery with this method, and wipe but I get can't mount cache errors during the wipe , waiting for the phone to reboot now, hopefully it will and get out of the bootloop. stupid thing is I'm not a noob, but stumped by this. Good excuse to upgrade to the N5 I guess
---------- Post added at 03:14 PM ---------- Previous post was at 02:55 PM ----------
Wow, this method worked! Brilliant! Thanks, and dammit, it worked, 10 minutes after she agreed to me getting am upgrade !
For all of you whom are stuck in bootloop a fastboot oem lock comand when in fastboot will solve the problem.
So go into bootloader and run "fastboot oem lock" for some reason on some devices Android 5.0 won't boot with unlocked bootloader.
hazwheel said:
OK, I was able to get into recovery with this method, and wipe but I get can't mount cache errors during the wipe , waiting for the phone to reboot now, hopefully it will and get out of the bootloop. stupid thing is I'm not a noob, but stumped by this. Good excuse to upgrade to the N5 I guess
---------- Post added at 03:14 PM ---------- Previous post was at 02:55 PM ----------
Wow, this method worked! Brilliant! Thanks, and dammit, it worked, 10 minutes after she agreed to me getting am upgrade !
Click to expand...
Click to collapse
OK great. Cheers, I helped someone today in this forum.
bett3rthan said:
For all of you whom are stuck in bootloop a fastboot oem lock comand when in fastboot will solve the problem.
So go into bootloader and run "fastboot oem lock" for some reason on some devices Android 5.0 won't boot with unlocked bootloader.
Click to expand...
Click to collapse
That did NOT work for me, the getting into recovery and wiping the device DID work though.
---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------
moorthidaniel said:
OK great. Cheers, I helped someone today in this forum.
Click to expand...
Click to collapse
Yes, Thanks, unfortunately, she has withdrawn the offer of an early upgrade :silly:
thax
Misledz said:
This is why you never use a Toolkit, it's always been mentioned around in XDA that this has always been a developer website of learning and knowledge. You must always know what goes on behind than just blindly flashing things. It's a rule of thumb that you're more likely to brick your phone with a Toolkit than by yourself. Easiest step as follow
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thank you alot, you help in really good manner
and teached us not to use toolkit
will learn more abt rooting and flashing thank you once again
I am hitting this problem now, I got a OTA. After restarting its keep on looping waiting for more than 20mins still it's looping.
Tried going to boot-menu and did factory reset and it booted good after ~10 mins.
sububack said:
I am hitting this problem now, I got a OTA. After restarting its keep on looping waiting for more than 20mins still it's looping.
Click to expand...
Click to collapse
Power off, hold Vol Down + Power, when you get to the Android laying down, press volume up + pwr, then wipe the /cache from the menu (you do not need to do a full factory wipe, just wiping cache will do), and then reboot and wait. It will boot this time properly. @WugFresh is aware of the issue and said will put a fix in 1.9.9 for the N4
Thanks , I have tried clearing the cache and started waiting for an hour. Since it was still looping tried after factory reset/wiping user data. And then after 10min it came good.
I post this on Google Product Forum 2 days ago. Hope it helps
https://productforums.google.com/fo...ce=footer#!msg/nexus/Lv8fHtyJOPQ/wDzRUm4b2UsJ
(updated 29/11/2014)[not perfect but it is a SOLUTION]
The idea of this is to downgrade your nexus 4 without wiping your data, which means stuff you will need includes:
1. adb and fastboot on your computer (I am using mac but you can find it on windows as well. There are tones of website and forums telling you the latest method of getting it onto your computer)
2. factory image of nexus 4(I use 4.4.4, since that's what it was. I don't have the time and energy to try to do the same thing with lollipop. you can try can leave a comment).
update: do NOT try to flash 5.0 rom using this method. You will be stuck at boot loop again
3. usb cable
4. nexus 4 with unlocked bootloader(the process of unlocking bootloader will wipe your device)
5. computer
steps
1. unzip the factory image (something.tgz)
2. for me, after unzipping the .tgz, I still find another .zip inside. unzip that too.
3. hold vol+, vol-, and power button simultaneously to enter fastboot mode
4. open terminal(mac)(it would probably be cmd for windows)
5. connect your nexus 4(in fastboot)
6. to make sure it connect successfully, type "fastboot devices". if something like "005040c0d54bb291 fastboot" appears, you are good. Otherwise, try reconnect your device/boot to fastboot again/use another usb cable
7.now we need to tell the terminal to navigate to the location of the unzipped factory image. to do that, i suggest you put the unzipped folder to somewhere easy to find, like desktop. these are some commands to help you navigate:
"ls" allows you to look at whats inside the current directory of the terminal. For example, this is the output after typing "ls" for me:
some folder Photos
nexus4image.tgz how many folders do you have
5.zip occam-ktu84p
more folder occam-ktu84p.zip
after knowing where you are, use "cd" (below) to go to your folder
"cd" means change directory. For example. "cd Photos" will brings me to the "Photos" folder. And then if I type ls, I will see a whole bunch of photos in my photos. If you go to the wrong folder, type "cd ..", and it will bring you back to the previous folder.
8. flash bootloader.
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash bootloader bootloader-mako-makoz30d.img
9. reboot bootloader. just copy and paste
fastboot reboot-bootloader
10. flash radio
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
11. reboot bootloader. just copy and paste
fastboot reboot-bootloader
12. flash system
system.img is located inside the zip, use ls to help you navigate. This steps takes the longest time, total time on this step is 87 seconds while the others are less then 1 second
fastboot flash system system.img
13. flash boot
boot.img is located inside the zip, use ls to help you navigate.
fastboot flash boot boot.img
14. flash recovery
fastboot.img is located inside the zip, use ls to help you navigate.
fastboot flash recovery recovery.img
15. format cache(not the memory, so everything should be fine)
fastboot format cache
16. reboot and wait
this will reboot your device. You probably have to wait for a while to initialise all the apps. after than you are good to go!
fastboot reboot
credit: my friend for giving me this idea + http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 + HelpMyNexus
So yeah I accidentally wiped my partitions as if I were installing a rom. Am I screwed until I get to a pc?
P.s. Out of all days to delete my backup rom file ?
Just set it to boot loader mode and flash stock images...I'm sure there's a tutorial on how to do it..I have the program installed on my computer ready for any time I brick my phone lol but I don't remember the name of the program right now
Edit: heres the link to the method I use http://forum.xda-developers.com/showthread.php?t=3258493
I'm assuming the OP doesn't have a PC due to the last statement he made. I would say yes, nothing you can do until you can get to a PC and flash stock images via Fastboot. Unless you have a ROM zip on your phone that is....which I'm assuming you don't.
You're kinda stuck, you need a PC to flash the factory images. TWRP can't flash OTA's anyway, so don't try that again either. I'd strongly recommend not using a toolkit to flash the factory images too. I have a detailed guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Hey guys, having a similar issue than zachbuilds. While rooting my nexus 6p on NRD9M, I formatted to system partition for root to stick and noticed twrp stated I have no OS installed. At that point I was going to flash stock image file when my nexus reverted from default MTP to charge only and now my Mac is unable to recognize my device Ann's now adb is non operable. I tried to fastboot adb commands but that isn't working either. Any one have any suggestions. I'm on stock with twrp custom recovery, no other changes were made to my device. Also, recovery and bootloader are accessible. Thanks for any help given.
Snakielols1984 said:
Hey guys, having a similar issue than zachbuilds. While rooting my nexus 6p on NRD9M, I formatted to system partition for root to stick and noticed twrp stated I have no OS installed. At that point I was going to flash stock image file when my nexus reverted from default MTP to charge only and now my Mac is unable to recognize my device Ann's now adb is non operable. I tried to fastboot adb commands but that isn't working either. Any one have any suggestions. I'm on stock with twrp custom recovery, no other changes were made to my device. Also, recovery and bootloader are accessible. Thanks for any help given.
Click to expand...
Click to collapse
Can fastboot see your device when you're in bootloader?
Yes fastboot is able to reconize my device.
Snakielols1984 said:
Yes fastboot is able to reconize my device.
Click to expand...
Click to collapse
Best just to flash back to factory images. Be cautious if you've flashed the Android N OTA though, there are some strange things going on with people trying to flash back to M. Read up before you flash.
I've actually tried flashing stock images but every time I tried to run fastboot command I get these errors, "command not found" and I believe the other erro is "file path not found". There's another error that I can't remember off the top of my head what it. When I get home I'll try to run the commands again and see what errors I get
---------- Post added at 11:09 PM ---------- Previous post was at 11:08 PM ----------
elfrosto said:
Best just to flash back to factory images. Be cautious if you've flashed the Android N OTA though, there are some strange things going on with people trying to flash back to M. Read up before you flash.
Click to expand...
Click to collapse
on another note I have not flashed Android N OTA. I downloaded that and install via OTA.
wrong thread
so just attempted to flash stock images and I get an error "cannot load bootloader-angler-angler-03.54.img". the tutorial I am using is Heisenberg's How-To Guide For Beginners. I followed the instructions step by step. Please is anyone can chime in, please do. Greatly appreciated!
Snakielols1984 said:
so just attempted to flash stock images and I get an error "cannot load bootloader-angler-angler-03.54.img". the tutorial I am using is Heisenberg's How-To Guide For Beginners. I followed the instructions step by step. Please is anyone can chime in, please do. Greatly appreciated!
Click to expand...
Click to collapse
What bootloader version are you on currently? Although updated bootloader is recommend, you should be able to skip this step without any issues.
Sorry for late response but currently I am bootloader: angler-3.58
---------- Post added at 12:27 AM ---------- Previous post was at 12:19 AM ----------
This is the error I get when using fastboot commands to flash stock images "error: cannot load 'MacintoshHD/angler/images/radio-angler-angler-03.61.img'". I received same error when trying to flash bootloader
Snakielols1984 said:
Sorry for late response but currently I am bootloader: angler-3.58
---------- Post added at 12:27 AM ---------- Previous post was at 12:19 AM ----------
This is the error I get when using fastboot commands to flash stock images "error: cannot load 'MacintoshHD/angler/images/radio-angler-angler-03.61.img'". I received same error when trying to flash bootloader
Click to expand...
Click to collapse
Please post the entire command you are using, as written in your terminal prompt. "No command" sounds like an unrecognized command is being issued. We must use ./ in addition to the fastboot or adb command in order for OSX to execute the action. If following Heisenberg's guide for fastboot, the lone change you need to make for OSX is:
./fastboot devices
./fastboot flash
./fastboot reboot
./ADB devices
Try this out and post your results.
Sent from my Nexus 5X using Tapatalk
Just throwing this out there, it is possible to flash an OTA in TWRP. You still need a PC but its do-able.... I flashed Android N Final to my 6P yesterday by copying the OTA zip (uploaded thanks to another member) to SD, Wiped device as I normally would with any other ROM (left SD intact obviously), Flashed OTA ZIP, rebooted straight to bootloader after flash, fastboot erase boot, fastboot erase recovery, fastboot flashed DECRYPTED BOOT.img (which can be found easily), fastboot flashed TWRP 3.0.2-1 (version just released for N), fastboot format userdata, fastboot format cache, reboot from bootloader directly into TWRP, flashed superSU 2.74, reboot system..... Phone runs beautifully. Not a single issue. Entire process from start to finish was less than 10 minutes.
Its not the most practical route but it does indeed work. OTA just hes to contain the entire Image. I should also mention that this was a jump from a Marshmallow based rom (RR) so you don't have to be on an N preview in order to do this....
For those in custom recovery land just flash the system and vendor img to upgrade
now in May flavor!
https://developers.google.com/android/nexus/images#instructions
Well it should be great IF our TWRP could mount vendor / system correctly
Only boot / recovery partitions are selectable for .img files :/
Edit: I´ve flashed the files via ADB - all went fine
redukt said:
Well it should be great IF our TWRP could mount vendor / system correctly
Only boot / recovery partitions are selectable for .img files :/
Edit: I´ve flashed the files via ADB - all went fine
Click to expand...
Click to collapse
The value of this posting would increase exponentially if you took it upon yourself to share what and how you flashed the files with ADB.
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
redukt said:
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
Click to expand...
Click to collapse
No chance of losing root either, is that correct?
Well I assume that you have TWRP? Reboot into recovery and flash supersu again. That´s all If not you can sideload it via ADB.
In my case I have reflash supersu & xposed framework in TWRP
redukt said:
Well I assume that you have TWRP? Reboot into recovery and flash supersu again. That´s all If not you can sideload it via ADB.
In my case I have reflash supersu & xposed framework in TWRP
Click to expand...
Click to collapse
Yes, I will need to reflash both, too (I have TWRP).
Thanks!
Than you´re device is rooted again. With this method you lose no data or wipe anything (ok.... some cache *g)
And... we have a thanks button in XDA So you don´t have to thank mate
Change log ? Or its just a security update
Hello there,
so I am in a little conundrum here.
I flashed the system.img and vendor.img following the instructions, but the pixel was just stuck at the plain Google logo.
After giving it something like 30 minutes, I had to power it off.
I am using TWRP and dragon-boot-encryptable-rooted-MXB48T-02102016-1.img stock kernel.
Another boot went without success.
my next thought was to downgrade to MXC14G but trying to do so resulted in:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
FAILED (remote: unsupported command)
finished. total time: 0.004s
So far TWRP is working and I can operate within it.
Any ideas what went wrong? Should I format system and vendor in TWRP? I don't think this is a good idea... (Last time I tried to do so in this experimental version of TWRP I had to fight a long fight to revive it, because the formatting tool in TWRP was stuck. But that's another story.) Any way to flash the system.img and vendor.img from within TWRP?
Any help would be much appreciated, m8s.
After playing around in TWRP and using the fix fastboot option I am finally able to flash system and vendor in fastboot.
I don't know if the fix fastboot was really the solution, maybe just some sort of placebo, but nevertheless I am able to flash. Problem with the bootloop remains:
Google logo, reboot recovery.
My data partition is alright. What do I need to flash to get it going?
Going in circles here...
rambobo said:
After playing around in TWRP and using the fix fastboot option I am finally able to flash system and vendor in fastboot.
I don't know if the fix fastboot was really the solution, maybe just some sort of placebo, but nevertheless I am able to flash. Problem with the bootloop remains:
Google logo, reboot recovery.
My data partition is alright. What do I need to flash to get it going?
Going in circles here...
Click to expand...
Click to collapse
Just asking, did you verify your download to make sure not corrupted?
Sent from my Pixel C using Tapatalk
houtx2 said:
Just asking, did you verify your download to make sure not corrupted?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Yes, it is verified. I am using all kinds of ways to restore the pixel.
I am positive: fastboot won't write or format partitions unless it is fixed by twrp.
I am trying out to flash the newest factory image with the skipsoft android toolkit. I could have done it manually, but spent already too much of my free Saturday on flashing. I'll report back if and what works out.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
:/ After 'successful' flashing of the stock firmware, now there is the laying android with the red exclamation sign... help...
---------- Post added at 04:54 PM ---------- Previous post was at 04:19 PM ----------
I redownloaded the official factory image grom google servers.
Then I followed the instruction, means i started the flash-all.bat.
The Tablet boot into the android on the back with the red exclamation mark symbol.
The flashing process went without warnings.
Is it bricked now? Do I have to relock the bootloader to boot it?
rambobo said:
Yes, it is verified. I am using all kinds of ways to restore the pixel.
I am positive: fastboot won't write or format partitions unless it is fixed by twrp.
I am trying out to flash the newest factory image with the skipsoft android toolkit. I could have done it manually, but spent already too much of my free Saturday on flashing. I'll report back if and what works out.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
:/ After 'successful' flashing of the stock firmware, now there is the laying android with the red exclamation sign... help...
---------- Post added at 04:54 PM ---------- Previous post was at 04:19 PM ----------
I redownloaded the official factory image grom google servers.
Then I followed the instruction, means i started the flash-all.bat.
The Tablet boot into the android on the back with the red exclamation mark symbol.
The flashing process went without warnings.
Is it bricked now? Do I have to relock the bootloader to boot it?
Click to expand...
Click to collapse
Pleas try to reinstall right drivers, change the cable / USB ports. I think your main problem is your system configuration. Good luck
m8... so glad I wasn't too tired to listen to your tip. Awesome! Redid all the steps on my freshly installed laptop, and voila!
Seems either my main PCs USB-connection is flunky or I am damned to reinstall my Windows soon. Scary...
I used the following software to revive the Pixel:
official Google USB Drivers
You have to unzip the file and right-click and install it
then you have to go to your device manager in windows and after connecting the tablet with the PC and getting into fastboot
Find the Android device on the top, select to change driver and go straight to manual selection of the driver, select android and bootloader driver
unpack the official Factory Image with 7Zip until you get to the folder with the flash-all.bat
get the minimal adb fastboot and unpack it in the same folder as the flash-all file
wait until you see the sweet booting animation
I think I didn't forget anything important. My Pixel is alive and ready for prime time.
Big thanks redukt, may the warp speed not pass you!
rambobo said:
Big thanks redukt, may the warp speed not pass you!
Click to expand...
Click to collapse
Enjoy your device
Next time simply hit the thanks button
redukt said:
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
Click to expand...
Click to collapse
rambobo said:
Hello there,
so I am in a little conundrum here.
I flashed the system.img and vendor.img following the instructions, but the pixel was just stuck at the plain Google logo.
After giving it something like 30 minutes, I had to power it off.
I am using TWRP and dragon-boot-encryptable-rooted-MXB48T-02102016-1.img stock kernel.
Another boot went without success.
my next thought was to downgrade to MXC14G but trying to do so resulted in:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
FAILED (remote: unsupported command)
finished. total time: 0.004s
So far TWRP is working and I can operate within it.
Any ideas what went wrong? Should I format system and vendor in TWRP? I don't think this is a good idea... (Last time I tried to do so in this experimental version of TWRP I had to fight a long fight to revive it, because the formatting tool in TWRP was stuck. But that's another story.) Any way to flash the system.img and vendor.img from within TWRP?
Any help would be much appreciated, m8s.
Click to expand...
Click to collapse
Following redukt's instructions, I got the same error that rambobo saw. I rebooted into TWRP and executed the "Fix fastboot" option, then rebooted back to the bootloader. System & Vendor image flashing via ADB worked fine
I am now running M5C14J without loss of data, root, or recovery.
The OTA update reminder disappeared on it's own after 5-10 minutes.
Thanks yall!
hugehead83 said:
Following redukt's instructions, I got the same error that rambobo saw. I rebooted into TWRP and executed the "Fix fastboot" option, then rebooted back to the bootloader. System & Vendor image flashing via ADB worked fine
I am now running M5C14J without loss of data, root, or recovery.
The OTA update reminder disappeared on it's own after 5-10 minutes.
Thanks yall!
Click to expand...
Click to collapse
You didn't have to apply root again via ADB or TWRP?
dmnhnterz said:
You didn't have to apply root again via ADB or TWRP?
Click to expand...
Click to collapse
Mates, the may-factory-image is available. Same procedure as ever
https://developers.google.com/android/nexus/images#instructions
Happy flashing
dmnhnterz said:
You didn't have to apply root again via ADB or TWRP?
Click to expand...
Click to collapse
Correct
But judging from others' experiences here, YMMV. I tried the latest FlashFire build too, but that got me nowhere.
Originally posted by: Azpre
Hello
A while ago, I tried to root my Essential Phone using magisk. I unlocked the bootloader, flashed twrp, but when I tried to install the magisk zip file, it failed, and I was stuck in a bootloop.
Easy problem to solve right? I wiped everything from my phone (including the ROM), downloaded a stock ROM (.ZIP file, and I think that’s what ****ed everything up) and when I tried to install it, it failed once again. Therefore, I downloaded another stock ROM file (this time as a .img file) and tried to installed it.
But what I ended up doing, was installing some other .img file as the boot image (on twrp), and after that, my phone kept restarting endlessly. I couldn’t access the recovery mode (if I tried to press the vol down + start buttons, or just the start button, the process would repeat, so I leaved my phone there until it run out of battery, now its off).
I was despaired and tried to search every inch of the internet for a solution, and obviously, I could not find it.
Any help would be greatly appreciated
Thanks for your attention.
(Im not sure if this is really a soft brick, I named this thread wit my basic knowlage, sorry if Im wrong)
Use
fastboot unlock_critical
Then flash your full stock formware to both slots
You can get in the bootloader right?
Azpre said:
Originally posted by: Azpre
Hello
A while ago, I tried to root my Essential Phone using magisk. I unlocked the bootloader, flashed twrp, but when I tried to install the magisk zip file, it failed, and I was stuck in a bootloop.
Easy problem to solve right? I wiped everything from my phone (including the ROM), downloaded a stock ROM (.ZIP file, and I think that’s what ****ed everything up) and when I tried to install it, it failed once again. Therefore, I downloaded another stock ROM file (this time as a .img file) and tried to installed it.
But what I ended up doing, was installing some other .img file as the boot image (on twrp), and after that, my phone kept restarting endlessly. I couldn’t access the recovery mode (if I tried to press the vol down + start buttons, or just the start button, the process would repeat, so I leaved my phone there until it run out of battery, now its off).
I was despaired and tried to search every inch of the internet for a solution, and obviously, I could not find it.
Any help would be greatly appreciated
Thanks for your attention.
(Im not sure if this is really a soft brick, I named this thread wit my basic knowlage, sorry if Im wrong)
Click to expand...
Click to collapse
From my understanding ... After you get the bootloader unlocked and the critical partition as the poster above stated. Pretty sure, Magisk, when booted into the android OS should be installed.. After that you can patch the boot image(to include root) without root! And then, fastboot flash boot (path/to/boot.img).
For not being able to boot into TWRP .... Did you use the command fastboot boot twrp.img? Or fastboot flash recovery twrp.img ?
If you used the boot command - TWRP will not stick.
If you used the flash command and cannot access TWRP, IDK, you may be on the wrong partition. I personally had a bit of difficulty with there being two partitions. Just made it a bit confusing...
As the above poster asked, .... Are you able to get to the bootloader? If so, I don't think all is lost... I'm thinking you'll just have to do some fastboot commands again, like, fastboot boot TWRP.img . Then you should be able to just press the volume a time or two to boot to recovery. As @BakedTator asked
---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------
BakedTator said:
Use
fastboot unlock_critical
Then flash your full stock formware to both slots
You can get in the bootloader right?
Click to expand...
Click to collapse
Was that advise sound enough???
---------- Post added at 05:49 PM ---------- Previous post was at 05:44 PM ----------
Azpre said:
Originally posted by: Azpre
Hello
A while ago, I tried to root my Essential Phone using magisk. I unlocked the bootloader, flashed twrp, but when I tried to install the magisk zip file, it failed, and I was stuck in a bootloop.
Easy problem to solve right? I wiped everything from my phone (including the ROM), downloaded a stock ROM (.ZIP file, and I think that’s what ****ed everything up) and when I tried to install it, it failed once again. Therefore, I downloaded another stock ROM file (this time as a .img file) and tried to installed it.
But what I ended up doing, was installing some other .img file as the boot image (on twrp), and after that, my phone kept restarting endlessly. I couldn’t access the recovery mode (if I tried to press the vol down + start buttons, or just the start button, the process would repeat, so I leaved my phone there until it run out of battery, now its off).
I was despaired and tried to search every inch of the internet for a solution, and obviously, I could not find it.
Any help would be greatly appreciated
Thanks for your attention.
(Im not sure if this is really a soft brick, I named this thread wit my basic knowlage, sorry if Im wrong)
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/help/partition-t3733811. Check out this thread, it may help or give you some understanding.
BakedTator said:
Use
fastboot unlock_critical
Then flash your full stock formware to both slots
You can get in the bootloader right?
Click to expand...
Click to collapse
This is what I got when I tried to use this command
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock_critical
fastboot: usage: unknown command unlock_critical
yesterday I couldn't find a way to access the bootloader, but for some reason when I gave another shot today it worked
going to try flash twrp once again
Azpre said:
This is what I got when I tried to use this command
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock_critical
fastboot: usage: unknown command unlock_critical
yesterday I couldn't find a way to access the bootloader, but for some reason when I gave another shot today it worked
going to try flash twrp once again
Click to expand...
Click to collapse
fastboot flashing!!! fastboot flashing unlock_critical
From HERE - !!!
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
dirtyreturn said:
From my understanding ... After you get the bootloader unlocked and the critical partition as the poster above stated. Pretty sure, Magisk, when booted into the android OS should be installed.. After that you can patch the boot image(to include root) without root! And then, fastboot flash boot (path/to/boot.img).
For not being able to boot into TWRP .... Did you use the command fastboot boot twrp.img? Or fastboot flash recovery twrp.img ?
If you used the boot command - TWRP will not stick.
If you used the flash command and cannot access TWRP, IDK, you may be on the wrong partition. I personally had a bit of difficulty with there being two partitions. Just made it a bit confusing...
As the above poster asked, .... Are you able to get to the bootloader? If so, I don't think all is lost... I'm thinking you'll just have to do some fastboot commands again, like, fastboot boot TWRP.img . Then you should be able to just press the volume a time or two to boot to recovery. As @BakedTator asked
---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------
Was that advise sound enough???
---------- Post added at 05:49 PM ---------- Previous post was at 05:44 PM ----------
https://forum.xda-developers.com/essential-phone/help/partition-t3733811. Check out this thread, it may help or give you some understanding.
Click to expand...
Click to collapse
thanks for the thread man, helped alot
I managed to flash twrp by some miracle, I remember my device entering a bootloop once I tried to access the bootloader menu, but now its all good. I waited for the Essential run out of battery, then I plugged-in my pc the fastboot commands were working once again
going to try install a boot image now
dirtyreturn said:
fastboot flashing!!! fastboot flashing unlock_critical
From HERE - !!!
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Click to expand...
Click to collapse
oh my god Im such a dumbass, sorry
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.
mod please remove this thread
oh hell, i've followed every step exactly and got a bootloop. 1922-5 brazilian model. is it because of the last update?
---------- Post added at 07:20 PM ---------- Previous post was at 07:18 PM ----------
and why does my phone show as a moto e4 now????
---------- Post added at 07:26 PM ---------- Previous post was at 07:20 PM ----------
just a thing: i obviously got some backups and i could revert the bootloop by just flashing the stock boot back into the phone.
if you took the update you have to reflash the updated stock firmware after the update. if need be ill walk you through it ive already done it with one person over facebook messenger and after that they were successful. unfortunately they havent commented on saying so lol or thanked the post. sorry for the late reply also i just got off work lol also if links are dead i got dev access on afh now so ill be putting the new links on here ina bit . also tbh i have no clue why it says moto e4 when we put the twrp recovery on but it doesnt affect anything. it would be nice if we had an official twrp
blowingoff said:
oh hell, i've followed every step exactly and got a bootloop. 1922-5 brazilian model. is it because of the last update?
---------- Post added at 07:20 PM ---------- Previous post was at 07:18 PM ----------
and why does my phone show as a moto e4 now????
---------- Post added at 07:26 PM ---------- Previous post was at 07:20 PM ----------
just a thing: i obviously got some backups and i could revert the bootloop by just flashing the stock boot back into the phone.
Click to expand...
Click to collapse
Moto G6 Play XT1922-3
ninjakira said:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections, ligma,
* thermonuclear war, or your mom getting upset with you for being on the computer all day
Please
* Ensure you have an advanced understanding of this device before flashing it! YOU are choosing to make these modifications or your own free will.
*/
I've decided to make a new guide for our jeter devices because the other guide is a little sloppy now lol. I have no problem with having this taking down if the op for the original guide decides to clean theirs up. this one should help clear up stuff now at least lol
This has been confirmed to work on:
XT1922-3 Model
XT1922-4 Model
XT1922-5 Brazilian Model
XT1922-7 Boost Mobile
XT1922-9 Model
Please make backups using TWRP IN CASE OF FAILURE.
Original stock firmware can be found here. https://mirrors.lolinet.com/firmware/moto/jeter/official/
The steps listed in this process WILL wipe your userdata. If you have anything you need to save back it up first.
Prerequisites:
Unlocked bootloader.
ADB/Fastboot installed on your machine ( https://developer.android.com/studio...platform-tools ) If you have issues with commands make sure you have a current build of ADB and fastboot.
Minimal adb/fastboot v1.4.3 installer can be found here. https://androidfilehost.com/?fid=746010030569952951
Step 1.) Download twrp image to the ADB/Fastboot folder on your computer. https://www.androidfilehost.com/?fid=1322778262904017969
Step 2.) Reboot to your bootloader. You can do this by turning on your device and holding power and both volume buttons at the same time.
Step 3.) Once the device reboots to the bootloader type the following from your computer with your phone connected via USB.
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Step 4.) Once TWRP boots from your computer type (it may take a bit to boot because it is trying to decrypt your userdata, but it will fail and prompt for a password. Just click cancel):
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
This will backup your stock boot and recovery images if you to revert to stock later.
Step 5.) Code:
adb reboot bootloader
Step 6.) Run the following command from your computer to install the TWRP image to your device.
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
Step 7.) Use the volume keys on the device to select boot to recovery and TWRP will boot up again. When it prompts for a decryption password select cancel again.
Step 8.) From your computer type the following into your command prompt/terminal from your adb/fastboot folder:
Code:
adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor
Step 9.) Download and extract https://www.androidfilehost.com/?fid=1322778262904017972 this patched fstab.qcom boot image into the ADB/Fastboot folder on your PC.
Step 10.) Run the following command from command prompt/terminal on your computer:
Code:
adb push fstab.qcom /vendor/etc/fstab.qcom
Step 11.) Next click the "Wipe" button in TWRP and slide "Swipe to Factory Reset" THIS WILL WIPE YOUR DATA ON YOUR PHONE. Ensure you have backup.
Step 12.) Download the Magisk Beta 17.2 zip file from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 to your ADB/Fastboot folder.
Step 13.) Run the following command to push the boot image to your device
Code:
adb push Magisk-v17.2.zip /tmp
This will push the Magisk-v17.2.zip to your /tmp folder
Step 14.) Flash Magisk-v17.2.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 15.) Reboot your device
Step 16.) It will say N/A in the top corner of your device for a few seconds. Then it will boot the the Motorola boot screen and you can setup your device as a new phone.
Step 17.) Verify Magisk Manager is installed and the root functionality works. if force encrytion is checked just uncheck it, click install then whatever option magisk recommends then reboot.
step 18.) have fun.
Step 19.)DOWNLOAD STOCK FIRMWARE HERE https://mirrors.lolinet.com/firmware/moto/jeter/official/ UNZIP STOCK FIRMWARE TO YOUR ADB/FASTBOOT FOLDER TO FLASH IT. TO REVERT BACK TO STOCK YOU HAVE TO REFLASH STOCK FIRMWARE FROM THE BOOTLOADER if your device is bootlooped or bricked or not working right you have to reflash the stock firmware your device came with. PLEASE INPUT THESE COMMANDS ONE AT A TIME DO NOT DO THEM ALL AT ONCE. I KNOW ITS A HASSLE BUT IT GUARANTEES A SUCCESSFUL REFLASH. I CANNOT EMPHASIZE THIS ENOUGH
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
if you guys think anything should be edited from this let me know and ill fix it. like im not 100% sure if we still have to use the modified fstabs.qcom i just used it still after i took the update and re-rooted. so if someone can tell me they didnt use the fstabs.qcom and still got the same results please let me know
Credits: @kwiksi1ver for making the original guide. and @topjohnwu for magisk. and @shimp208 for minimal adb/fastboot.
Click to expand...
Click to collapse
It still doesn`t work,i flashed the stock JETER_RETAIL_8.0.0_OPPS27.91-35-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml,code by code with fastboot and gpt.bin,bootloader.img and oem.img fail flashing.
What should i do?
Every time i boot the phone normally or into bootloader it says bad key,and i also dont see my baseband anymore.
Help me!
ninjakira said:
if you took the update you have to reflash the updated stock firmware after the update. if need be ill walk you through it ive already done it with one person over facebook messenger and after that they were successful. unfortunately they havent commented on saying so lol or thanked the post. sorry for the late reply also i just got off work lol also if links are dead i got dev access on afh now so ill be putting the new links on here ina bit . also tbh i have no clue why it says moto e4 when we put the twrp recovery on but it doesnt affect anything. it would be nice if we had an official twrp
Click to expand...
Click to collapse
I could imagine it was because we have no official twrp. what do you mean by updated stock image? I'm oj build opp27.91-87.
You sir need to also use this https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETAIL/. Go to step 19 and follow the reflashing stock firmware instructions. Use the most recent firmware. You can tell which one is new by dates
blowingoff said:
I could imagine it was because we have no official twrp. what do you mean by updated stock image? I'm oj build opp27.91-87.
Click to expand...
Click to collapse
ninjakira said:
You sir need to also use this https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETAIL/. Go to step 19 and follow the reflashing stock firmware instructions. Use the most recent firmware. You can tell which one is new by dates
Click to expand...
Click to collapse
mine is the brazilian one, xt1922-5. the downloads are for the 1922-2. can i use it?
---------- Post added at 05:49 PM ---------- Previous post was at 05:45 PM ----------
oh, I think you didn't understand me. I've already reverted the bootloop, my phone is working. but if I flash magisk, it goes to bootloop
I just got off the phone with Moto they confirm your device is also the aljeter so those firmwares should work for you.
blowingoff said:
mine is the brazilian one, xt1922-5. the downloads are for the 1922-2. can i use it?
---------- Post added at 05:49 PM ---------- Previous post was at 05:45 PM ----------
oh, I think you didn't understand me. I've already reverted the bootloop, my phone is working. but if I flash magisk, it goes to bootloop
Click to expand...
Click to collapse
ninjakira said:
I just got off the phone with Moto they confirm your device is also the aljeter so those firmwares should work for you.
Click to expand...
Click to collapse
great. so i'll flash the firmware and try to root from it
---------- Post added at 06:40 PM ---------- Previous post was at 06:25 PM ----------
well. i got an update. I just flash magisk with no modified boot image, no fstab.qcom and such. just flash twrp and then magisk.
phone rooted, safetynet passed. wow!!!!!!!!!!
blowingoff said:
great. so i'll flash the firmware and try to root from it
---------- Post added at 06:40 PM ---------- Previous post was at 06:25 PM ----------
well. i got an update. I just flash magisk with no modified boot image, no fstab.qcom and such. just flash twrp and then magisk.
phone rooted, safetynet passed. wow!!!!!!!!!!
Click to expand...
Click to collapse
Awesome you just helped confirm a couple things on my end to lol like the fstabs.qcom. I'm glad I could be of assistance to you and I'm glad the guide worked. I'll be removing the fstabs.qcom link since they are no longer needed now
I'm pretty sure there's already a Jeter root guide. What's the point in creating a new one?
Dadud said:
I'm pretty sure there's already a Jeter root guide. What's the point in creating a new one?
Click to expand...
Click to collapse
The other one was confusing people, and starting to cause more harm than anything. I've already helped a couple people in bootloop that tried to use the old guide and couldn't.
ninjakira said:
The other one was confusing people, and starting to cause more harm than anything. I've already helped a couple people in bootloop that tried to use the old guide and couldn't.
Click to expand...
Click to collapse
Seems like those people weren't following the the guide TO A T (very important) /skimming thinking it works the old way. I've seen those types of people all over these forums. You're adding more unnecessary clutter to these already cluttered and poorly moderated forums. I'm also pretty sure you don't have permission from kwiksilver to use his files
I've already talked to a mod about this there looking Into it and trust me man I literally have gone on rants to the people about not skimming before I helped fox there devices. I'm just trying to help everyone the best way I can think of all at once. People before the OTA and after no longer need a patched boot.img because the latest magisk does it. Furthermore we don't need the patched fstabs.qcom as I've recently learned. The device can be unencrypted without all that now thanks to magisk. I've already also told quiksi1ver I'm willing to have mine taking down if he cleans his up and updates it.also a couple devices like the xt1922-3 and 5 are aljeter not Jeter but it seems the xt1922-5 still apply to this guide.
Dadud said:
Seems like those people weren't following the the guide TO A T (very important) /skimming thinking it works the old way. I've seen those types of people all over these forums. You're adding more unnecessary clutter to these already cluttered and poorly moderated forums.
Click to expand...
Click to collapse
Also in my post I put the link for the stock firmware along with the proper adb commands to flash said stock firmware from bootloader which ALOT of people also need
lol this thread is much clearer than the earliest. and also: i've followed the steps from the original thread but i got no response from anyone there. hehhe
blowingoff said:
lol this thread is much clearer than the earliest. and also: i've followed the steps from the original thread but i got no response from anyone there. hehhe
Click to expand...
Click to collapse
Thank you for that lol I just wanna actually try to help out our fellow g6 play users lol
Thanks for creating this new thread, it really is cleaner than before.
Got it working on XT1922-5, brazilian model. Managed to get root and everything is working fine.
But just for curiosity, is there a way to revert it to stock with locked bootloader at all? Already flashed stock rom, my only problem is not being able to relock it.
Hope to see some new roms coming for our device soon!
AcTSkull said:
Thanks for creating this new thread, it really is cleaner than before.
Got it working on XT1922-5, brazilian model. Managed to get root and everything is working fine.
But just for curiosity, is there a way to revert it to stock with locked bootloader at all? Already flashed stock rom, my only problem is not being able to relock it.
Hope to see some new roms coming for our device soon!
Click to expand...
Click to collapse
Removed commands for bootloader relock because they don't work ignore this post
ninjakira said:
I personally have not used this yet to relock my bootloader so I cannot say 100% this will work. So please don't get mad at me if not. If it works for you please let me know and I'll add it to the post
Click to expand...
Click to collapse
Of course not! We are all here to learn, share and have fun with it.
Anyway, it didn't work. Still boots up with the Bad Key at the top and grayed out "unlocked oem" at developer options.
Let's wait and see if (when available around here, not OTA) flashing a new firmware will fix it, perhaps, as it updates the version to 27.91-147 (will confirm it later).