Hi there,
tl;dr:
Basically, my problem seems to be, that any write-operation on my filesytems is refused:
C:\Users\cxx\Programme\adb-1.0.32>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
Click to expand...
Click to collapse
I found threads about the same problem on Moto G 2013, where "Philz Recovery" was able to fix the partitioning and filesystems, but it seems that this does not exist vor Moto G 2014. And I don't even get any other than stock-recovery working.
TWRP site states: "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. " But I could not find any key combo to enter the recovery I just flashed (at least fastboot tells me so) Using "fastboot boot recovery.img" just shows a shortly flickering Motorola-logo every 10 seconds or so.
---
I am having severe issues with my Moto G (2014).
I found some reports of similar issues, but no solution described worked, and it seems I am the only one experiencing this on a stock device.
First some facts:
Device in use since 2 months
Encyption activated about a month ago, no problems
Yesterday, I used screen pinning feature to let my son play a game.
While he was playing, the battery drained until the device shut down.
I connected the device to a charger
After charging 30%, everything first seems normal, I have to enter my encryption PIN and boot process goes on, showing boot animation.
The problem:
At the point, where it would normally finish, the screen just gets black (while still being lit up). Nothing more will happen. The device will remain in this state forever or until the battery is completely drained again.
I first tried using the official methods for (factory) reset described on Motorolas website, they did not work (I am not allowed to post links here yet, google "/prod_answer_detail/a_id/99825/p/30,6720,9151" will show the URL)
Pressing 7-8 seconds restarts the phone, same situation.
Pressing 120 seconds restarts the phone several times, still not working.
I wanted to perform a factory reset, but starting recovery from bootloader only displayed "Boot Up Failed". Choosing "factory" or "bp tools" just started normal boot process. Barcodes seems to work, it shows barcodes.
So next step was unlocking the device to install TWRP. Fastboot displayed no errors, but then not TWRP, but normal recovery starts. Well, better than "Boot Up Failed".
When now performing a factory reset, this is displayed:
Code:
-- Wiping data...
Formatting /data...
E:
blkdiscard on partition /dev/block/pla
form/msm_sdcc.1/by-name/userdata failed
E:
blkdiscard on partition /dev/block/pla
form/msm_sdcc.1/by-name/cache failed
-- Wiping clogo...
Data wipe complete
Obviously, the partitions are untouched (or not there?), and the problem remains.
I also tried to erase cache and userdata using fastboot, there are no error messages, but after rebooting, I am still asked for encryption PIN, so it's basically the same.
I then tried to use adb sideload to flash cm12 nightly. But the device complains that the signature verification failed.
Now, I am not even able to lock the device again, while fastboot states, it would have succeeded.
I wanted to reinstall stock images as described on thetechrism.com (Google: restore-moto-g-2and-generation-2014-stock-lock-bootloader) but I have problems downloading as I only have mobile internet connection at this moment and the download from filefactory stopped two times at 200 MB and I have only about 1 GB traffic for the rest of the month.
I am stuck here, and getting desperate. Did my device brick itself?
I have CM12 and TWRP here, but just cannot get it flashed. This would be my preferred solution, but a reliable source for stock images would also be very nice.
Did anyone experience similar problems when the battery completely drained with a pinned app on an encrypted device?
Thanks in advance for any hint.
Regards
cxxxx
I was now able to download the original firmware.
But...it's the same :'(
I did every step to reinstall stock firmware. No error-messages, neither on console nor on device, everything seems to be fine.
But when I finally reboot, the device again asks for my encryption PIN and will fail to startup!
I still cannot wipe my userdata, still cannot flash a custom recovery...nothing. It's just a ******* brick.
I found one interesting error:
Code:
C:\Users\cxx\Programme\adb-1.0.32>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.066s]
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.133s
How can I manually reformat my partitions in internal storage or how can I force automatically formatting?
Code:
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.041s]
writing 'partition'...
OKAY [ 0.304s]
finished. total time: 0.347s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.134s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.954s]
finished. total time: 1.091s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.087s]
writing 'logo'...
OKAY [ 0.044s]
finished. total time: 0.134s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.458s]
writing 'boot'...
OKAY [ 0.599s]
finished. total time: 1.060s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.464s]
writing 'recovery'...
OKAY [ 0.607s]
finished. total time: 1.075s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 9.899s]
writing 'system'...
OKAY [ 8.160s]
finished. total time: 18.063s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256626 KB)...
OKAY [ 9.860s]
writing 'system'...
OKAY [ 8.230s]
finished. total time: 18.094s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (257136 KB)...
OKAY [ 9.874s]
writing 'system'...
OKAY [ 7.975s]
finished. total time: 17.853s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (230052 KB)...
OKAY [ 8.841s]
writing 'system'...
OKAY [ 7.559s]
finished. total time: 16.402s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.941s]
writing 'modem'...
OKAY [ 0.854s]
finished. total time: 2.798s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.015s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.013s]
finished. total time: 0.014s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.014s]
finished. total time: 0.015s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.018s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot reboot
rebooting...
finished. total time: 0.002s
I'm having the same problem...in fastboot mode, none of the actions that i've been made gave me no results... and the stock recovery give me the "blkdiscard on partition" message and the phone still no bootup
izaiasfilho said:
I'm having the same problem...in fastboot mode, none of the actions that i've been made gave me no results... and the stock recovery give me the "blkdiscard on partition" message and the phone still no bootup
Click to expand...
Click to collapse
We are not alone, see here:
http://forum.xda-developers.com/mot...ttery-left-t3085322/post60312526#post60312526
Bad news is, that the problem has not been solved and probably will not as it seems that it's hardware-failure of the flash-storage-(controller).
@cxxxx
I read about it on the moto forums, with users having lost write operations on their phone. And all had one thing in common, they had let the battery die out .
Lesson to be learnt : Never let Li ion batteries totally get drained.
One of the moto moderator told it on their forum to never let your battery totally die. I dont know how much of it rings true as I've let my phone discharged till death many times without any issues.
Same problem here.
After the battery gone once i did't manage to enter. Services errors at android home screen and i can't do recovery - wipe data - cache (all failed). The only thing that i manage is to unlock bootloader.
My question: I 'm thinking to send device for warranty (buying one month ago). Do you think that i 'll have problem with unlock bootloader at service. Somewhere i read that motorola have 2 year warranty for software no matter what. Is that real???
HardBricked unlocked stock lollipop xt1068
Same problem here. But no enconding is on thou.
Can't flash anything - stuck on black screen after boot animation.
XT1068 Unlocked bootloader, stock lollipop, no root, no Motorola service in my country.
Once this devices gone hardbrick, after freaky TWRP could not backup or do anything else. Just could not turn in on at all.
Recovered with jtag riff drivers, but this seems to help bootup, not to flash firmwares - so its not applicable for this case.
RSD Lite 6.1.6 can't see phone, ADB sideload form stock recovery gives no device for adb or windows device manager, but fastboot is okay.
Tryed different computers, different drivers, different stock roms, different fastboot\mfastboot tools, recover scripts.
Hi, guys. I'd face the same problem, but I can boot up, using a Nokia phone charger. Don't know how to explain, but the moto g 2014 charger can't charge enough to boot, when the battery is 0%, then come back to the black screen. With the nokia charger, my moto g boot up normally.
Sorry for my bad english.
Nico
For all those users with soft-bricked "nothing changes after any actions", what if we try to use:
Fastboot erase all
If this would work - bootloader will be dead. We will get the hard brick.
But I have experience of successful recovering xt1068(exactly this one) from hard-brick state, when decice does not turn on at all in any way or mode since bootloader is missing or corrupted.
But PC still can see it over USB cable as QBULC_USB. This one would not work with Motorola drivers nor with any other, but JTAG Riff drivers for QUALCOMM.
Then special low-level tool will load up bootloader.
So? Any suggestions about this?
I think it is not good idea. With fastboot erase all you will erase your imei along with psd partition and your phone will be unrecoverable.
Sent from my XT1068 using XDA Free mobile app
Tonal4Nagual said:
I think it is not good idea. With fastboot erase all you will erase your imei along with psd partition and your phone will be unrecoverable.
Click to expand...
Click to collapse
No way of backing up this data?
I remember some of mine old RAZR - I had some backup of unique data for it.
BTW I have the box with IMEI on it, CID saved in notepad, what else...
Stock fw with no root and THIS with no reason.
Also - right before stucked - phone has drained battery from 60% to 0% in pretty short time, then this happened.
Maybe there is some hardware problem with electric circuit..
Tonal4Nagual said:
I think it is not good idea. With fastboot erase all you will erase your imei along with psd partition and your phone will be unrecoverable.
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
With my device bricked like this I have tried, CHMOD which has unable to alter the partitions, as well as CHOWN & CHGRP(in both TWRP & ADB), Fastboot erase does nothing along with ADB wipe, TWRP does nothing and no changes can be made as nothing is overwritten, as well as with using Fastboot flash, there have been rumors that Philz can fix it but since nothing can be flashed I cannot try (Unless someone has a way to flash it to SD and let it boot from there, Let me know)
Now with my limited knowledge of android and its partitions and since none of the above methods having any effect I believe that this issue is in fact a hardware one not software related, therefore I think 'Fastboot erase all" will have no effect, that is my opinion gathered from more than two weeks testing, wiping & hoping, if there are any senior users/devs who want to correct me they may, Also if they have any other options I will be glad to try it out.
EDIT: This is purely a hardware fault and no software changes can do anything, I ran Fastboot erase all
...and a reboot later and my device is exactly the same, even boots into recovery fine and fastboot barcodes still shows my original IMEI and Serial number, ADB getvar_cid still also shows the correct CID for my device.
I would upload pictures but I haven't got enough posts to link to tinypic
Related
I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.
GuardianUSMC said:
I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.
Click to expand...
Click to collapse
No, you cannot ad root to the image before flashing.
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.
gee2012 said:
No, you cannot ad root to the image before flashing.
Click to expand...
Click to collapse
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.
Click to expand...
Click to collapse
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.
GuardianUSMC said:
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.
Click to expand...
Click to collapse
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.
gee2012 said:
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.
Click to expand...
Click to collapse
Got it, thank you very much for your assistance.
Too bad the Factory Images from Google are not already rooted.
GuardianUSMC said:
So the factory images provided directly by Google are NOT at root already either?
Click to expand...
Click to collapse
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
So for example on a linux machine you will have the root directory:
/
Within root, you will have other directories such as:
/bin
/etc
/usr
See here for more information:
http://www.thegeekstuff.com/2010/09/linux-file-system-structure/
So root is kind of like the C:\ drive on a Windows PC. Everything to do with the OS and User directories are within there.
Your Android device is the same, however, /bin, /etc (etc) are not at the root of the device. They sit within the system partition, which sits within root. so /system/bin, /system/etc. When you flash a factory image, it flashes the images to /system, /cache, /userdata (and a few other places) where as the root of the device remains largely untouched.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.
@rootSU,
Excellent mini tutorial. I wish this could be stickied on the General roll up thread. Thank you very much.
rootSU said:
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
Click to expand...
Click to collapse
I appreciate that and forgive me I know I used the terms interchangeably and that's my bad.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
Click to expand...
Click to collapse
yes I am familiar with that and I was using the term to mean having root privileges, again my bad.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
Click to expand...
Click to collapse
Understood, I have done that and my device is currently rooted. I was more looking into making an image that is already rooted, to borrow a term from Windows, slipstream the root functionality pre-flashing. I was told not going to happen, that's fine. Although when I had my HTC Evo 4G, I had pre-rooted images that I had created with the bloat removed and I was flashing them with root functionality out of the box, but that's another story, I guess Nexus 6 is a different animal and dealing with Lollipop probably more difficult than Gingerbread.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.
Click to expand...
Click to collapse
No but I appreciate you taking the time, thank you.
Right now mostly I am frustrated with the fact that the factory images provided by google will not flash right and keep *****ing about missing .sig files. I have tried flashing them individually by taking the root, system, recovery images out of the zip file and doing them individually as been suggested all over the place but no luck there there, keeps *****ing about the partitions instead, makes no sense. The bootloader and radio images go through without a hitch but the rest is just a mess.
Just to share, I am trying to flash the factory image that I mentioned in my original post, so I won't repost it. Here is what did so far to no avail, so any assistance would be greatly appreciated:
I issue the command adb reboot bootloader and it successful reboots the phone into the bootloader
Extracting the folder shamu-lmy47i containing the following files:
bootloader-shamu-moto-apq8084-71.08.img
flash-all.bat
flash-all.sh
flash-base.sh
image-shamu-lmy47i.zip
radio-shamu-d4.0-9625-02.95.img
Opening the batch file you see the following (I have removed the copyright header for sake of brevity)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip
echo Press any key to exit...
pause >nul
exit
Since the only thing I want to add to this is root, I add this after the image update:
Code:
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
So we let it rip and this is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.548s]
finished. total time: 0.674s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.720s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.102s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
downloading 'boot.img'...
OKAY [ 0.393s]
booting...
OKAY [ 0.024s]
finished. total time: 0.419s
Press any key to exit...
As we can see, bootloader image flashes just fine
The radio image flashes just fine
System image on the other hand does not update complaining about missing .sig files:
fastboot -w update image-shamu-lmy47i.zip said:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
Click to expand...
Click to collapse
The files inside this system zip are:
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
Ironically the SuperSU image flashes just fine and reboots the phone
I am frustrated by the fact that the system image update step fails and nothing out there explains why? I have even tried to extract each of those images from the zip file and flashing them individually using the fastboot flashall but getting the same error as well as other errors.
Can anyone lend an assist on this and help me figure out how to overcome that hurdle PLEASE?
Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.
Evolution_Freak said:
Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.
Click to expand...
Click to collapse
I did provide everything step by step the only thing I didn't provide was the errors on the individual images that are within the update zip file. Which I suppose is my bad:
Code:
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
and I have tried flashall last because documentation states it will do boot, recovery and system but I have also done them using individual commands too. But more on that after I take a look at what you posted in the link. Stay tuned. Thank you.
Alright, good news, it worked and thank you for pointing to the resource that allowed me to figure out why I was getting the partition errors, now I know.
I modified the batch file as follows:
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
adb reboot bootloader
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
echo Press any key to exit...
pause >nul
exit
it went through the whole process and here is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
< waiting for device >
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.508s]
finished. total time: 0.632s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.722s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.110s]
finished. total time: 3.834s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
target reported max download size of 536870912 bytes
sending sparse 'system' (522196 KB)...
OKAY [ 22.442s]
writing 'system'...
OKAY [ 7.691s]
sending sparse 'system' (510114 KB)...
OKAY [ 21.723s]
writing 'system'...
OKAY [ 6.674s]
sending sparse 'system' (514997 KB)...
OKAY [ 21.128s]
writing 'system'...
OKAY [ 7.778s]
sending sparse 'system' (189177 KB)...
OKAY [ 7.652s]
writing 'system'...
OKAY [ 2.328s]
finished. total time: 97.428s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 11.844s]
sending 'userdata' (138868 KB)...
OKAY [ 4.518s]
writing 'userdata'...
OKAY [ 1.949s]
finished. total time: 18.315s
target reported max download size of 536870912 bytes
sending 'boot' (7681 KB)...
OKAY [ 0.247s]
writing 'boot'...
OKAY [ 0.110s]
finished. total time: 0.359s
target reported max download size of 536870912 bytes
sending 'recovery' (8273 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.116s]
finished. total time: 0.384s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.045s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.013s]
sending 'cache' (6248 KB)...
OKAY [ 0.204s]
writing 'cache'...
OKAY [ 0.097s]
finished. total time: 0.318s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.399s]
booting...
OKAY [ 0.035s]
finished. total time: 0.436s
Thank you for everyone's input and assistance here, you rock.
Hello, I got the MotoG 2014 from Amazon in the US, it came with Kitcat and in the first week it installed the OTA for Lollipop, and I was very happy with my purchase then after a couple of months it started to update something while on low battery and then the phone died, I was out of the US so turning it back to Amazon was not possible. I couldn't do anything from the recovery so I unlocked it and found some RETUSGLB Lollipop ROM and flashed it using fastboot and it came back to life. After two weeks, while I was using it, the screen went black, it would boot up and stay on the Motorola animated logo, again the recovery wouldn't work, so I decided to flash the same Llollipop again, but this time the fastboot flash command only worked with the "fastboot flash partition gpt.bin" all the others (motoboot, boot, logo, recovery, etc) gave me an error:
(bootloader) Failed to flash
FAILED (remote failure)
I've tried many of the recommendations of the forum to no avail, right now when I try to boot up the MotoG normally, it stays in a garbled screen, I guess the logo image is corrupt. Tried to flash a different Lollipop ROM, but it fails to flash also. I can boot to fastboot and use some commands like "fastboot oem partition" and "fastboot getvar all". I don't say the MotoG is hardbricked because when is in fastboot the pc recognizes it as Moto g 2014 . I cannot install any of the custom recoverys because the flash into recovery fails, but I can boot up Cyanogenmod recovery into ram. Tried to install an update from the external SD card using CM but it gives error messages about being unable to mount files and directories, which leads me to think that the Linux file system is corrupted. Cannot use ADB because fastboot nor CM recovery have the option. Using ADB sideload from CM gives error about being unable to mount files and directories too.
Since the MotoG is useless now, and I'm loosing hope about this phone, and I'm mad at Motorora for the cheap quality of their engineering that allowed the phone to fail in the first place. I'm thinking about the procedure I've seen on the forum, but used on the Moto G 2013, the one that wipes the bootloader and then blankflash the phone, risking a Hardbrick. Some people in the forum says that blankflash for 2013 wouldn't work on the 2014, others say it would, from the emmc standpoit both devices seems the same to me.
Sorry for the long story. Any suggestion to recover the MotoG is appreciated.
Thanks in advance.
Don't know exactly what wrong.
Try this : http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
It should fix your problem (There is bootloader files included in the zip file so try flashing that.)
If you think my solution isn't good enough,, wait for someone who can tell you a proper answer. Peace.
I tried your suggestion but it failed to flash as other Roms did:
Code:
Easy Installer - Lollipop 5.x.x Moto G (2nd Gen) 2014
For XT1063, XT1064, XT1068 and XT1069
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel choose option 6
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 1
RETURNING TO STOCK ROM - FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.029s]
writing 'partition'...
OKAY [ 0.319s]
finished. total time: 0.356s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.106s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 100.145s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.024s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 19.989s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.351s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.377s
linuxtron said:
I tried your suggestion but it failed to flash as other Roms did:
Code:
Easy Installer - Lollipop 5.x.x Moto G (2nd Gen) 2014
For XT1063, XT1064, XT1068 and XT1069
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel choose option 6
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 1
RETURNING TO STOCK ROM - FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.029s]
writing 'partition'...
OKAY [ 0.319s]
finished. total time: 0.356s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.106s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 100.145s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.024s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 19.989s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.351s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.377s
Click to expand...
Click to collapse
Add me on Hangouts ( https://plus.google.com/108108436166506337243 ) or join #titandev at freenode.
im stuck with this piece of sh*t phone and "waiting for any device". I flashed TWRP 142314 times on my phone, and today this bloody problem comes out and i cant f*king solve it. My drivers and everything is up to date, expect something named "S1 Boot Fastboot" (warning sing near that in device manager). I have no idea what the hell is that and i cant flash twrp and install custom rom. Any ideas, excpet that one about uninstalling win10 )))
yey, a new problem:
C:\Users\nevas\Desktop\sony\ADB\platform-tools-latest-windows\platform-tools>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.350s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.356s
nevenx said:
yey, a new problem:
C:\Users\nevas\Desktop\sony\ADB\platform-tools-latest-windows\platform-tools>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.350s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.356s
Click to expand...
Click to collapse
You can't flash TWRP to the recovery partition on the Xperia Z. It doesn't use the recovery partition; instead, it uses the FOTAKernel partition, which is inaccessible by Fastboot. If you want to destroy your old stock firmware and install custom ROM, flash TWRP to boot partition. The phone should not boot to the firmware and boots straight to TWRP.
Hello everyone! I'm in a panic...
I have a Owens E4+ US model, bought retail with no carrier branding. A couple weeks ago I unlocked the bootloader and installed TWRP and Magisk and got root. Eventually, all was well - except I couldn't get into banking apps and Snapchat due to being rooted.
So I thought I would start over just now, by flashing back to stock - using this thread:
https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-qualcomm-owens-completely-to-t3743441
I downloaded the "OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" and performed the fastboot commands listed in post #10 of the thread. Everything seemed to go fine, rebooted and whatnot, get to the normal "welcome to Android" setup... however, I can't make phone calls and have no data (I use Pageplus, a Verizon MVNO). I have had to tweak the APN settings before, but they aren't even available...which led me to check out the IMEI info in "about phone" - everything is listed as "unknown".....
AAAARRRRGGGGHHH!!!! What do I do????
jdsmn21 said:
Hello everyone! I'm in a panic...
I have a Owens E4+ US model, bought retail with no carrier branding. A couple weeks ago I unlocked the bootloader and installed TWRP and Magisk and got root. Eventually, all was well - except I couldn't get into banking apps and Snapchat due to being rooted.
So I thought I would start over just now, by flashing back to stock - using this thread:
https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-qualcomm-owens-completely-to-t3743441
I downloaded the "OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" and performed the fastboot commands listed in post #10 of the thread. Everything seemed to go fine, rebooted and whatnot, get to the normal "welcome to Android" setup... however, I can't make phone calls and have no data (I use Pageplus, a Verizon MVNO). I have had to tweak the APN settings before, but they aren't even available...which led me to check out the IMEI info in "about phone" - everything is listed as "unknown".....
AAAARRRRGGGGHHH!!!! What do I do????
Click to expand...
Click to collapse
There is a small possibility you may have either flashed the wrong one for your device or the fastboot cmd for your oem.img was slightly incorrect. Look into the folder containing your firmware and see what's there for oem images..
The original cmd was:
fastboot flash oem oem.img
But when I opened my firmware, I actually had 2 oem files with different names. So I had to change my fastboot cmds to:
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
After that, everything was fine. Hope that helps
bcrichster said:
There is a small possibility you may have either flashed the wrong one for your device or the fastboot cmd for your oem.img was slightly incorrect. Look into the folder containing your firmware and see what's there for oem images..
The original cmd was:
fastboot flash oem oem.img
But when I opened my firmware, I actually had 2 oem files with different names. So I had to change my fastboot cmds to:
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
After that, everything was fine. Hope that helps
Click to expand...
Click to collapse
It seems to match what's in the folder. I just don't know what to do or try next?
For some reason I think I was on Android 7.1.2, and this is 7.1.1 - would that have done anything?
I did take backups with TWRP before doing this - will those do me any good?
I did copy the command prompt text - not sure if any of this makes sense...
Code:
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot devices
ZY224BRJFZ fastboot
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot oem fb_mode_set
...
OKAY [ 0.005s]
finished. total time: 0.009s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot flash gpt gpt.bin
target reported max download size of 536870912 bytes
sending 'gpt' (45 KB)...
OKAY [ 0.011s]
writing 'gpt'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.090s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (5179 KB)...
OKAY [ 0.220s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 1.040s]
finished. total time: 1.267s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (73891 KB)...
OKAY [ 2.948s]
writing 'modem'...
OKAY [ 2.844s]
finished. total time: 5.799s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (1120 KB)...
OKAY [ 0.048s]
writing 'fsg'...
OKAY [ 0.151s]
finished. total time: 0.205s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.061s]
finished. total time: 0.065s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.065s]
finished. total time: 0.068s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.653s]
writing 'dsp'...
OKAY [ 0.707s]
finished. total time: 1.367s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1386 KB)...
OKAY [ 0.066s]
writing 'logo'...
OKAY [ 0.173s]
finished. total time: 0.244s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.674s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.610s]
finished. total time: 1.290s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.681s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 1.034s]
finished. total time: 1.722s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (511914 KB)...
OKAY [ 20.268s]
writing 'system'...
OKAY [ 11.902s]
finished. total time: 32.182s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (508182 KB)...
OKAY [ 19.675s]
writing 'system'...
OKAY [ 11.703s]
finished. total time: 31.386s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (510802 KB)...
OKAY [ 20.083s]
writing 'system'...
OKAY [ 11.703s]
finished. total time: 31.791s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (512872 KB)...
OKAY [ 19.424s]
writing 'system'...
OKAY [ 11.350s]
finished. total time: 30.782s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (524286 KB)...
OKAY [ 20.619s]
writing 'system'...
OKAY [ 12.082s]
finished. total time: 32.709s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (100156 KB)...
OKAY [ 3.888s]
writing 'system'...
OKAY [ 3.319s]
finished. total time: 7.213s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (42317 KB)...
OKAY [ 1.493s]
writing 'oem'...
OKAY [ 1.046s]
finished. total time: 2.546s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot erase cache
erasing 'cache'...
OKAY [ 0.028s]
finished. total time: 0.030s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot erase userdata
erasing 'userdata'...
OKAY [ 1.171s]
finished. total time: 1.174s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot erase ddr
erasing 'ddr'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.008s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot oem fb_mode_clear
...
OKAY [ 0.150s]
finished. total time: 0.154s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>fastboot reboot
rebooting...
finished. total time: 0.008s
C:\Users\Jon\Downloads\OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml\OWENS_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAUL
T_CFC.xml>
The magic fix - go to Settings->About Phone->System Updates and you'd find an update. Update it and everything would work like a charm again. Thank me later :laugh::laugh::laugh:
Baseband fix
Bro I think you have erased your baseband hence you do not have IMEI and can't place calls and use data!
The same has happened with me, so i can help you out. however I am using Indian version (mediatek processor). You have to flash baseband first go search on YouTube there is nothing on XDA after you flash baseband, then you have to write IMEI to your device, there many software available for writing IMEI use that and you will be getting signal and data....
But now since you have flashed stock ROM from 3rd party so don't expect battery life as before, however you will be getting great Dolby Atmos effect.
***SB51 post above -- has a solution I would suggest you try first
a similiar thing happened to me. From your text, it shows the gpt command failed. I assume you were already on the nprs26.58-45 firmware. so i am under the impression that there is really no way to downgrade to the npr26.58-25 retail firmware.
Anyway, maybe somebody can link/post a nprs26.58-45 retail firmware and I think everything will be back to normal. However, it does not seem to be available. So if and when the firmware or modem become available, you will be fine.
Anyway, I restored my imei info and got my phone working again to make calls, by flashing the modem and only the modem from the sprint owen NCR26.58-44 firmware file. I am still hope hoping to get my phone back to stock someday. I am not sure if this will work for you, but it worked for me.
I honestly would wait for the more experienced users to chime in.
-E
Regarding the reason why you tried to go back to stock in the first place... couldn't you have just uninstalled Magisk? Or better yet, use Magisk to hide itself from those apps?
Unless you relock your bootloader going back to stock will not fix your problem because stock will report you have an unlocked bootloader which means you will fail safetynet. You can use Magisk hide and enable the specific apps to hide it from. Also to get your data and sim functions back all you need to do is take the OTA update from moto and you will get that function back as when I used that zip to flash back that is what I did to get it back.
SB581240 said:
The magic fix - go to Settings->About Phone->System Updates and you'd find an update. Update it and everything would work like a charm again. Thank me later :laugh::laugh::laugh:
Click to expand...
Click to collapse
That did it!!! Thank you!!
Sizzlechest said:
Regarding the reason why you tried to go back to stock in the first place... couldn't you have just uninstalled Magisk? Or better yet, use Magisk to hide itself from those apps?
Click to expand...
Click to collapse
Honestly, I don't know. I guess I was thinking the TWRP/Magisk/Adaway changing the hosts file all added up to my problems, and decided to start from scratch. The thread made it sound easy and harmless...
I did try Magiskhide, but it didn't seem to work for me. Any tips? Does it work for you?
soaringowl2145 said:
Unless you relock your bootloader going back to stock will not fix your problem because stock will report you have an unlocked bootloader which means you will fail safetynet. You can use Magisk hide and enable the specific apps to hide it from. Also to get your data and sim functions back all you need to do is take the OTA update from moto and you will get that function back as when I used that zip to flash back that is what I did to get it back.
Click to expand...
Click to collapse
So with my stock unrooted rom (but unlocked bootloader) I can install Snapchat and Chase Pay (banking app) - both of which I couldn't install before when rooted. However, I still can't download Netflix (had to sideload the apk and it works) and installed Google Pay, however it recognizes the phone as having an unlocked bootloader and boots me out.
I downloaded "Root Checker", which includes a SafetyNet checker; it says "CTS Profile Match: Failed". Will Magisk get me past SafetyNet?
Does Magisk Hide work for you? I couldn't get it to work before...
jdsmn21 said:
That did it!!! Thank you!!
Click to expand...
Click to collapse
I created an account to help you! Show me some love although I have no idea how that might possibly help me, nevertheless...
jdsmn21 said:
So with my stock unrooted rom (but unlocked bootloader) I can install Snapchat and Chase Pay (banking app) - both of which I couldn't install before when rooted. However, I still can't download Netflix (had to sideload the apk and it works) and installed Google Pay, however it recognizes the phone as having an unlocked bootloader and boots me out.
I downloaded "Root Checker", which includes a SafetyNet checker; it says "CTS Profile Match: Failed". Will Magisk get me past SafetyNet?
Does Magisk Hide work for you? I couldn't get it to work before...
Click to expand...
Click to collapse
Yes it does work. Flash Magisk, make sure hide is enabled. Then go install your apps like Snapchat. Before logging into Snapchat go into Magisk hide settings and check the box for Snachat Netflix, chase, and pay.
soaringowl2145 said:
Yes it does work. Flash Magisk, make sure hide is enabled. Then go install your apps like Snapchat. Before logging into Snapchat go into Magisk hide settings and check the box for Snachat Netflix, chase, and pay.
Click to expand...
Click to collapse
Can I get your advice on my next steps?
So right now, my phone is stock w/ unlocked bootloader. I did go home at lunch and BOOT (ie: not flash) TWRP via ADB, and performed a backup of all available partitions. I did notice that my phone is in encrypted status. Does that matter to anything I'm doing? (ie: TWRP, Magisk, etc).
jdsmn21 said:
Can I get your advice on my next steps?
So right now, my phone is stock w/ unlocked bootloader. I did go home at lunch and BOOT (ie: not flash) TWRP via ADB, and performed a backup of all available partitions. I did notice that my phone is in encrypted status. Does that matter to anything I'm doing? (ie: TWRP, Magisk, etc).
Click to expand...
Click to collapse
Try to install Magisk through twrp. Mount sysystem as write access. If that does not work you may need to format data to make it mount to flash.
soaringowl2145 said:
Try to install Magisk through twrp. Mount sysystem as write access. If that does not work you may need to format data to make it mount to flash.
Click to expand...
Click to collapse
I just flashed TWRP, and installed Magisk through that. It passes SafetyNet! I put some apps on the hide list in Magisk, like Chase Pay and Android Pay (pointless as we have no NFC, but seemed like a good test for Safetynet) and seem to work fine with mods undetected.
What I'd like to do (the main reason for rooting) is to install a system wide adblocker like AdAway - but before attempting I thought I'd discuss. I ticked the switch for "systemless hosts" in Magisk, exited, and rebooted. But the switch doesn't seem to stick. Does this phone have a problem with systemless hosts, or am I not doing it right?
If I just installed Adaway without the systemless hosts, would I trip Safetynet?
In the state my phone is in right now - if I did a full backup in TWRP and then screwed something up in Magisk (playing with modules, etc), would a TWRP restore bring me back? Or does Magisk install/modify partitions that are not backed up with TWRP?
jdsmn21 said:
I just flashed TWRP, and installed Magisk through that. It passes SafetyNet! I put some apps on the hide list in Magisk, like Chase Pay and Android Pay (pointless as we have no NFC, but seemed like a good test for Safetynet) and seem to work fine with mods undetected.
What I'd like to do (the main reason for rooting) is to install a system wide adblocker like AdAway - but before attempting I thought I'd discuss. I ticked the switch for "systemless hosts" in Magisk, exited, and rebooted. But the switch doesn't seem to stick. Does this phone have a problem with systemless hosts, or am I not doing it right?
If I just installed Adaway without the systemless hosts, would I trip Safetynet?
In the state my phone is in right now - if I did a full backup in TWRP and then screwed something up in Magisk (playing with modules, etc), would a TWRP restore bring me back? Or does Magisk install/modify partitions that are not backed up with TWRP?
Click to expand...
Click to collapse
I do not use the systemless hosts option. If you use AdAway without systemless support you will NOT trip safetynet. Also I would think that a backup would be able to bring you back as you can still backup your modified boot partition. You may or may not lose the original boot partition that magisk backed up.
Also is magisk hide getting disabled when you reboot? It does for me.
Edit. Also this type of thread belongs in the question forum since this is a question
jdsmn21 said:
So with my stock unrooted rom (but unlocked bootloader) I can install Snapchat and Chase Pay (banking app) - both of which I couldn't install before when rooted. However, I still can't download Netflix (had to sideload the apk and it works) and installed Google Pay, however it recognizes the phone as having an unlocked bootloader and boots me out.
I downloaded "Root Checker", which includes a SafetyNet checker; it says "CTS Profile Match: Failed". Will Magisk get me past SafetyNet?
Does Magisk Hide work for you? I couldn't get it to work before...
Click to expand...
Click to collapse
Yes, My safetynet says it is 100% w/Magisk.
Running an Xp3r!meπt with my XT1776
Hi,
I was trying to reflash everything on my phone and wipe. When I boot into fastboot and run fastboot -w, I get an error saying Download is not allowed on locked device. Im using platform tools 29.05.
ahsank128 said:
Hi,
I was trying to reflash everything on my phone and wipe. When I boot into fastboot and run fastboot -w, I get an error saying Download is not allowed on locked device. Im using platform tools 29.05.
Click to expand...
Click to collapse
Does the bootloader screen show unlocked?
Have you tried to run the flashing unlock again?
Mackay53 said:
Does the bootloader screen show unlocked?
Have you tried to run the flashing unlock again?
Click to expand...
Click to collapse
Okay, so I locked the bootloader, and unlocked it again. Successfully flashed. But I am geting the following message
"Erase successful, but not automatically formatting. File system type raw not supported"
I cant run the fastboot format (partition) command. I am on latest platform tools and latest factory image
ahsank128 said:
Okay, so I locked the bootloader, and unlocked it again. Successfully flashed. But I am geting the following message
"Erase successful, but not automatically formatting. File system type raw not supported"
I cant run the fastboot format (partition) command. I am on latest platform tools and latest factory image
Click to expand...
Click to collapse
Does your phone boot up? If so, I would check to see if your still getting good recognition from your pc. What does adb devices show when you enter that with your phone in transfer data mode?
Badger50 said:
Does your phone boot up? If so, I would check to see if your still getting good recognition from your pc. What does adb devices show when you enter that with your phone in transfer data mode?
Click to expand...
Click to collapse
Yes, the factory image gets flashed, but now everything seems to be on partition B as opposed to A. I believe everything was going to A when I first got the phone and did the unlock. ADB working fine, managed to root the phone. i enter ADB devices and shows serial. I can boot to fastboot. I wanted to see what would happen if I run fastboot flashing unlock again, and it said device is unlocked
ahsank128 said:
Yes, the factory image gets flashed, but now everything seems to be on partition B as opposed to A. I believe everything was going to A when I first got the phone and did the unlock. ADB working fine, managed to root the phone. i enter ADB devices and shows serial. I can boot to fastboot. I wanted to see what would happen if I run fastboot flashing unlock again, and it said device is unlocked
Click to expand...
Click to collapse
Well, then I guess all is well for you again. Just FYI going forward, when you fastboot the factory image without the -w, it only flashes to your active slot, whereas, if you leave the -w, it'll flash to both slots, but wipe your device. This is why when I update the factory images every month without the -w, I manually change slots so I get a full flash to both slots. Many think this is overkill, however, I have never had any wonky problems for the last 2+ years with my P2XL, and now my P4XL by using this methodology :good:
Badger50 said:
Well, then I guess all is well for you again. Just FYI going forward, when you fastboot the factory image without the -w, it only flashes to your active slot, whereas, if you leave the -w, it'll flash to both slots, but wipe your device. This is why when I update the factory images every month without the -w, I manually change slots so I get a full flash to both slots. Many think this is overkill, however, I have never had any wonky problems for the last 2+ years with my P2XL, and now my P4XL by using this methodology :good:
Click to expand...
Click to collapse
Right, but the thing is I left the -w in the bat file. Even so it only flashed to b, saying device is locked. I think there is some internal issue going. Im the same guy who cant get the blackenedmod script to run properly lol
ahsank128 said:
Right, but the thing is I left the -w in the bat file. Even so it only flashed to b, saying device is locked. I think there is some internal issue going. Im the same guy who cant get the blackenedmod script to run properly lol
Click to expand...
Click to collapse
I know who you are? At least your up and running again. But yeah, sounds like your internals might be a little wonky for sure. ?
Badger50 said:
I know who you are At least your up and running again. But yeah, sounds like your internals might be a little wonky for sure. ?
Click to expand...
Click to collapse
Any idea on the best way to completely wipe the internals and flash again? This would be easy with TWRP or custom recovery, but we've some time before that is made for Android10
ahsank128 said:
Any idea on the best way to completely wipe the internals and flash again? This would be easy with TWRP or custom recovery, but we've some time before that is made for Android10
Click to expand...
Click to collapse
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:
Badger50 said:
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:
Click to expand...
Click to collapse
Will attempt this, my attempt last night was to do factory reset within the settings (when phone is booted up) and then flashed with -w. But I will try again using the stock recovery. I even changed computers, this stuff is wonky sometimes
Badger50 said:
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:
Click to expand...
Click to collapse
Code:
C:\Users\akhan37\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 5.477s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.203s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.178s
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Code:
Sending 'bootloader_b' (8761 KB) OKAY [ 0.349s]
Writing 'bootloader_b' (bootloader) Flashing Pack version c2f2-0.2-5940465
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition logfs
OKAY [ 0.435s]
Finished. Total time: 1.046s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
Sending 'radio_b' (82676 KB)
DELETED
ahsank128 said:
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Click to expand...
Click to collapse
Interesting. Just a simple experiment if your willing. Go into your platform-tools, and just double click the flash-all.bat file and see if you get the same result, or if it even initializes
ahsank128 said:
Code:
C:\Users\akhan37\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 5.477s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.203s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.178s
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Code:
Sending 'bootloader_b' (8761 KB) OKAY [ 0.349s]
Writing 'bootloader_b' (bootloader) Flashing Pack version c2f2-0.2-5940465
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition logfs
OKAY [ 0.435s]
Finished. Total time: 1.046s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
Sending 'radio_b' (82676 KB)
Click to expand...
Click to collapse
If you have done a factory reset, you also need to make sure you enable "oem unlocking" in Developer options and usb debugging before you do anything else. Flashing a factory stock image which includes the '-w' in your flash-all.bat file would come afterwards.
I am assuming you are not flashing any kernals on top? Check to make sure you are flashing the correct image, Nov and December had 3 different images each month.
Badger50 said:
Interesting. Just a simple experiment if your willing. Go into your platform-tools, and just double click the flash-all.bat file and see if you get the same result, or if it even initializes
Click to expand...
Click to collapse
Wont work from home screen (this is fine? should be in fastboot)
Looks like it flashed this time from the fastbootd screen (so damn strange)
from fastbootd screen:
Code:
Sending 'bootloader' (8761 KB) OKAY [ 0.218s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
Sending 'radio_b' (82676 KB) OKAY [ 2.180s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g8150-00041-191016-B-5945070
(bootloader) Flashing partition modem_b
OKAY [ 0.650s]
Finished. Total time: 3.090s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.051s
--------------------------------------------
Bootloader Version...: c2f2-0.2-5940465
Baseband Version.....: g8150-00041-191016-B-5945070
Serial Number........: 99171FFAZ006J5
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.069s]
Checking 'version-bootloader' OKAY [ 0.069s]
Checking 'version-baseband' OKAY [ 0.068s]
Setting current slot to 'b' OKAY [ 0.077s]
extracting boot.img (64 MB) to disk... took 0.387s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.139s]
Writing 'boot_b' OKAY [ 0.455s]
extracting dtbo.img (8 MB) to disk... took 0.025s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.310s]
Writing 'dtbo_b' OKAY [ 0.117s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB) OKAY [ 0.138s]
Writing 'vbmeta_b' OKAY [ 0.072s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.101s]
Writing 'vbmeta_system_b' OKAY [ 0.072s]
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.069s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_b' OKAY [ 0.004s]
Resizing 'system_b' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.004s]
Resizing 'vendor_b' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.004s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (2127 MB) to disk... took 15.801s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.005s]
and got stuck there
One more thing: When on stock boot image, OEM Unlock frozen on bootloader already unlock. But after flashing magsik, I can switch between allow and not allow. This is normal?
bb709394 said:
If you have done a factory reset, you also need to make sure you enable "oem unlocking" in Developer options and usb debugging before you do anything else. Flashing a factory stock image which includes the '-w' in your flash-all.bat file would come afterwards.
I am assuming you are not flashing any kernals on top? Check to make sure you are flashing the correct image, Nov and December had 3 different images each month.
Click to expand...
Click to collapse
No, this issue happens on stock kernel. And yes USB debugging and OEM Unlock both are checked. I believe the image is correct. US Unlocked Pixel from google store. file ends in 011
ahsank128 said:
Wont work from home screen (this is fine? should be in fastboot)
Looks like it flashed this time from the fastbootd screen (so damn strange)
from fastbootd screen:
and got stuck there
One more thing: When on stock boot image, OEM Unlock frozen on bootloader already unlock. But after flashing magsik, I can switch between allow and not allow. This is normal?
Click to expand...
Click to collapse
Yes, it only works in fastboot mode.
I don't think it's strange at all. I've never come across the..fastboot -w..command that you were using, which is why I suggested what I did.
Sometimes it takes a while for the script to finish. You might no have been stuck per-se, but just not patient enough. December was a big update, so it takes a little longer.
Yes, this is normal for OEM unlocking while rooted.
So...are you up and running now?
Badger50 said:
Yes, it only works in fastboot mode.
I don't think it's strange at all. I've never come across the..fastboot -w..command that you were using, which is why I suggested what I did.
Sometimes it takes a while for the script to finish. You might no have been stuck per-se, but just not patient enough. December was a big update, so it takes a little longer.
Yes, this is normal for OEM unlocking while rooted.
So...are you up and running now?
Click to expand...
Click to collapse
I am up and running, I'll check to see if I can get that script running later on
ahsank128 said:
I am up and running, I'll check to see if I can get that script running later on
Click to expand...
Click to collapse
Kinda sounds like you already got the script to work