Related
I have tried updating OTA to 4.3 with an unlocked bootloader and motley kernel. To my understanding I need to restore the stock kernel to update OTA without loosing data. How do I do this?
Jordydaman said:
I have tried updating OTA to 4.3 with an unlocked bootloader and motley kernel. To my understanding I need to restore the stock kernel to update OTA without loosing data. How do I do this?
Click to expand...
Click to collapse
Extract the BOOT.IMG from the factory stock version of 4.2.2, and fastboot flash it with...
Code:
fastboot flash boot boot.img
Rgrds,
Ged.
How do I fastboot,
GedBlake said:
Extract the BOOT.IMG from the factory stock version of 4.2.2, and fastboot flash it with...
Code:
fastboot flash boot boot.img
Rgrds,
Ged.
Click to expand...
Click to collapse
I rooted the cheap way using a toolkit how do I fastboot
Normally you'd install the Android SDK to run fastboot coomands.... but if you're running a 32bit version of Windows, here is all you need...
https://dl.dropboxusercontent.com/u/37483979/FastBootAdb-MD5-576cec93330fe1dfedd170f5f704b35f.zip
I've also included the BOOT.IMG extracted from nakasi-jdq39 factory image for 'grouper' (WiFi) Nexus 7.
---------------------------------
Download from the above link and extract to some location on your PC.
Boot your Nexus 7 into Bootloader mode (Shut down, then Vol Down+Power On).
Hook it up to your PC via USB.
Open a command prompt window on the folder which contains the files you just unzipped.
Type...
Code:
fastboot devices
You should see something like this... (a serial number followed by the word 'fastboot').
Code:
015d2d425b67s234 fastboot
This indicates if you have a viable Fastboot connection.... if you don't see a serial number, then you have a driver problem.
If you do see a serial number, you can proceed with...
Code:
fastboot flash boot boot.img
...which will flash the stock kernel to the boot partition.
Good luck.
Rgrds,
Ged.
Im using 64 bit window and using the SDK
GedBlake said:
Normally you'd install the Android SDK to run fastboot coomands.... but if you're running a 32bit version of Windows, here is all you need...
https://dl.dropboxusercontent.com/u/37483979/FastBootAdb-MD5-576cec93330fe1dfedd170f5f704b35f.zip
I've also included the BOOT.IMG extracted from nakasi-jdq39 factory image for 'grouper' (WiFi) Nexus 7.
---------------------------------
Download from the above link and extract to some location on your PC.
Boot your Nexus 7 into Bootloader mode (Shut down, then Vol Down+Power On).
Hook it up to your PC via USB.
Open a command prompt window on the folder which contains the files you just unzipped.
Type...
Code:
fastboot devices
You should see something like this... (a serial number followed by the word 'fastboot').
Code:
015d2d425b67s234 fastboot
This indicates if you have a viable Fastboot connection.... if you don't see a serial number, then you have a driver problem.
If you do see a serial number, you can proceed with...
Code:
fastboot flash boot boot.img
...which will flash the stock kernel to the boot partition.
Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
I am using the SDK on 64bit, do I need to place the boot.img in a certain place?
Jordydaman said:
I am using the SDK on 64bit, do I need to place the boot.img in a certain place?
Click to expand...
Click to collapse
Easiest way is to just copy it into the same folder as FASTBOOT.EXE
And then run fastboot flash boot boot.img in a command prompt window opened on that folder.
Rgrds,
Ged.
If you're facing issues with mobile connectivity, you can reinstall the modem files, as follows:
1. Download the factory image for your device from http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
2. Extract NON-HLOS.bin and fsg.mbn to a folder of your choice.
3. Download and install fastboot (or place the executable in the folder where you extracted the files), if not installed.
If you're using Windows you'll need to install the needed drivers
4. In the file manager, navigate to the folder where you extracted the files.
5. Right click > (Actions) > Open terminal (or CMD) here...
6. Reboot to bootloader (hold power and volume down buttons until you can read "AP Fastboot Flash Mode")
7. Type in the following commands:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
If it fails, try running the commands with administratives privileges (for Mac and Linux use sudo fastboot instead of fastboot, for Windows right click CMD and open with admin privilege).
8. Reboot your phone (power button)
Cellular Data is still not working
Hi ,
I am new to this forum and have tried your method of flashing only the network related files on Moto G 2015 Osprey, but still the cellular data does not work properly.
I am able to browse the internet but downloads using Google Play Store is not possible using cellular data.
Have tried your method and some others suggested on youtube on the following Roms:
1. AOSCP CypherOs 7.1
2. AOSPExtended 7.0 v1.2
3. AOSPExtended 7.1.1 v2.0
4. GZ Rom Tesla
No issues are seen in the following roms:
1. Stock Marshmallow 6.0.1 (after the update few months ago)
2. Stock Marshmallow optimized rom on xda
3. Nexus Experience Rom 6.0.1 from nxroms.
Kindly suggest a method to get cellular data working for downloads too.
Thanks.
chinchin85 said:
Hi ,
I am new to this forum and have tried your method of flashing only the network related files on Moto G 2015 Osprey, but still the cellular data does not work properly.
I am able to browse the internet but downloads using Google Play Store is not possible using cellular data.
Have tried your method and some others suggested on youtube on the following Roms:
1. AOSCP CypherOs 7.1
2. AOSPExtended 7.0 v1.2
3. AOSPExtended 7.1.1 v2.0
4. GZ Rom Tesla
No issues are seen in the following roms:
1. Stock Marshmallow 6.0.1 (after the update few months ago)
2. Stock Marshmallow optimized rom on xda
3. Nexus Experience Rom 6.0.1 from nxroms.
Kindly suggest a method to get cellular data working for downloads too.
Thanks.
Click to expand...
Click to collapse
Have you tried contacting your carrier or checking if you didn't disable anything related to mobile network downloads on your Google account?
Henriquefeira said:
Have you tried contacting your carrier or checking if you didn't disable anything related to mobile network downloads on your Google account?
Click to expand...
Click to collapse
Hi Henriquefeira,
I am on roaming on all the roms which i have mentioned above. I have not contacted my carrier for any such issues. Also in the roms which are working (both in home and roaming locations), I did not change any settings. They just work out of the box. Even in the roms which have issues, basic browsing works after few reboots to the phone, but downloads from Google Play or even elsewhere just dont happen.
I have tried changing Apn , registering to the wireless carrier etc. in the settings but these changes did not work.
Also a feature which was working out of the box in the previous android versions and custom roms is broken now.
Hope we all get a solution so that 7.1.1 can be used as a daily driver...till then on NxRom 10.4.
Found a link which descibes the issue:https://productforums.google.com/forum/#!topic/nexus/21wGieItCik
Hi all,
For any one who stumbles across this issue....it is indeed a bug in Nougat 7.0, 7.1, 7.1.1 even on the Nexus and Pixel line of phones. It is not a problem specific to any custom rom.Solution is to use alternate app stores: Appbrain, Amazon Appstore, Apkpure,
Thanks to all for their roms and answers.
I did this with the newest Lineage rom and now I face constant reboots. So be warned...
If anyone knows how to fix this, I'm open for suggestions.
xMotoDA said:
If you're facing issues with mobile connectivity, you can reinstall the modem files, as follows:
1. Download the factory image for your device from http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
2. Extract NON-HLOS.bin and fsg.mbn to a folder of your choice.
3. Download and install fastboot (or place the executable in the folder where you extracted the files), if not installed.
If you're using Windows you'll need to install the needed drivers
4. In the file manager, navigate to the folder where you extracted the files.
5. Right click > (Actions) > Open terminal (or CMD) here...
6. Reboot to bootloader (hold power and volume down buttons until you can read "AP Fastboot Flash Mode")
7. Type in the following commands:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
If it fails, try running the commands with administratives privileges (for Mac and Linux use sudo fastboot instead of fastboot, for Windows right click CMD and open with admin privilege).
8. Reboot your phone (power button)
Click to expand...
Click to collapse
Do you have the modem files of the old firmware ? .. i dont want to download a full rom for getting the modem. If you have please upload them here . XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107-55_cid7 is the firmware for which i need the modem.
chinchin85 said:
Hi ,
I am new to this forum and have tried your method of flashing only the network related files on Moto G 2015 Osprey, but still the cellular data does not work properly.
I am able to browse the internet but downloads using Google Play Store is not possible using cellular data.
Have tried your method and some others suggested on youtube on the following Roms:
1. AOSCP CypherOs 7.1
2. AOSPExtended 7.0 v1.2
3. AOSPExtended 7.1.1 v2.0
4. GZ Rom Tesla
No issues are seen in the following roms:
1. Stock Marshmallow 6.0.1 (after the update few months ago)
2. Stock Marshmallow optimized rom on xda
3. Nexus Experience Rom 6.0.1 from nxroms.
Kindly suggest a method to get cellular data working for downloads too.
Thanks.
Click to expand...
Click to collapse
where i can find the Stock Marshmallow optimized rom? i search, but I can't find anything. :/
leonardo.teseyra said:
where i can find the Stock Marshmallow optimized rom? i search, but I can't find anything. :/
Click to expand...
Click to collapse
Hi Leonardo,
The stock 6.0.1 rom optimized for Moto G 2015 XT1550 2Gb version is here:
https://forum.xda-developers.com/20...m-stock-motorola-6-0-1-rom-optimized-t3355938
chinchin85 said:
Hi Leonardo,
The stock 6.0.1 rom optimized for Moto G 2015 XT1550 2Gb version is here:
https://forum.xda-developers.com/20...m-stock-motorola-6-0-1-rom-optimized-t3355938
Click to expand...
Click to collapse
oh :/, i have the osprey (1 gb version) haha, thanks for the reply
chinchin85 said:
Hi ,
I am new to this forum and have tried your method of flashing only the network related files on Moto G 2015 Osprey, but still the cellular data does not work properly.
I am able to browse the internet but downloads using Google Play Store is not possible using cellular data.
Have tried your method and some others suggested on youtube on the following Roms:
1. AOSCP CypherOs 7.1
2. AOSPExtended 7.0 v1.2
3. AOSPExtended 7.1.1 v2.0
4. GZ Rom Tesla
No issues are seen in the following roms:
1. Stock Marshmallow 6.0.1 (after the update few months ago)
2. Stock Marshmallow optimized rom on xda
3. Nexus Experience Rom 6.0.1 from nxroms.
Kindly suggest a method to get cellular data working for downloads too.
Thanks.
Click to expand...
Click to collapse
you are must be in Roaming network. ... on 7.x.x playstore doesn't allow download on roaming.
Hey !
I have a XT1541, completly unlocked with "modem" from Europe. My network is "Free" from France.
I'm in Canada now but only have Edge network. Can I flash modem files from another ROM or is it useless/dangerous ?
Thanks !
mohindar72 said:
you are must be in Roaming network. ... on 7.x.x playstore doesn't allow download on roaming.
Click to expand...
Click to collapse
Really? Can someone else confirm it?
Is there anyway to bypass that?
I knew about this bug in N but i thought it was fixed
xMotoDA said:
If you're facing issues with mobile connectivity, you can reinstall the modem files, as follows:
1. Download the factory image for your device from http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
2. Extract NON-HLOS.bin and fsg.mbn to a folder of your choice.
3. Download and install fastboot (or place the executable in the folder where you extracted the files), if not installed.
If you're using Windows you'll need to install the needed drivers
4. In the file manager, navigate to the folder where you extracted the files.
5. Right click > (Actions) > Open terminal (or CMD) here...
6. Reboot to bootloader (hold power and volume down buttons until you can read "AP Fastboot Flash Mode")
7. Type in the following commands:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
If it fails, try running the commands with administratives privileges (for Mac and Linux use sudo fastboot instead of fastboot, for Windows right click CMD and open with admin privilege).
8. Reboot your phone (power button)
Click to expand...
Click to collapse
After flahed a custom recovery I was in trouble with H+ and 4G connections, just 3G works.
I did what you described and it works fine, but when I turn off the phone the previous problems happen again.
Any suggestion?
giuliusxda said:
After flahed a custom recovery I was in trouble with H+ and 4G connections, just 3G works.
I did what you described and it works fine, but when I turn off the phone the previous problems happen again.
Any suggestion?
Click to expand...
Click to collapse
Try running just the second and third commands. If the problem persists, check your preferred network type under Settings or under Phone info in the testing menu (dial *#*#4636*#*# to get there).
My brother and I both have an Osprey and I unlocked both device's bootloader in order to flash some good old ROMs but he started toying with the device flashing files he found I don't know where (also don't know why) and now his phone won't connect to 4G.
I've been using RR Oreo on my XT1542 and he was on stock so I though that maybe flashing the same ROM that I'm using on his device the issue would resolve itself but to my surprise it didn't.
What can I do to fix this? The phone is connecting only to 3G networks. I've even tried changing the options using #*#*4636*#*# with no success. If I choose any other option than WCDMA the phone goes to "Emergency calls only"
giuliusxda said:
If it fails, try running the commands with administratives privileges (for Mac and Linux use sudo fastboot instead of fastboot, for Windows right click CMD and open with admin privilege).
8. Reboot your phone (power button)
After flahed a custom recovery I was in trouble with H+ and 4G connections, just 3G works.
I did what you described and it works fine, but when I turn off the phone the previous problems happen again.
Any suggestion?
Click to expand...
Click to collapse
I had tried but it don't work
After i struck in to the problem i created a simple way to all my friends who are using moto x and thinking about back to stock rom 100% here you go
Downloads:
I assume you already have adb drivers if you're even here.....otherwise get them from the latest sdk here
Moto Drivers (Motorola Device Manager):
Stock Firmware: click here
Moto Fastboot exe: mfastboot
My Setup: Windows 8 machine <--obvious driver issues as usual
download all the files required
step 1: install adb files
Step 2: Install Motorola Drivers
Step 3: Extract Downloaded Stock Rom in the local folder
Step 4: Now extract mfastboot Moto X ghost manual to automation command file.rar
step 5: Now copy the extracted stock rom then paste it in mfastboot folder, now all the mfastboot and stock rom are all in same folder
Step 6: Hope you know how to get in to bootloader , go to boot loader connect your mobile to pc through data cable
Step 7: Now we reached the last step now you simply double click flash_modem file over now the files will automatically loaded in your phone and once finished reboot it you be in 100% stock rom
have fun guys
XDA:DevDB Information
Moto X - Return to 100% stock using one click flash file, Tool/Utility for the Moto X
Contributors
gowtham3834
Version Information
Status: Stable
Created 2017-02-07
Last Updated 2017-02-07
after updating into kitkat from throw your method or when i update my mobile it comes in bootloader mode or says load kernel (boot) failed or boot up failed any idea how to recovery it
KadirDvl said:
after updating into kitkat from throw your method or when i update my mobile it comes in bootloader mode or says load kernel (boot) failed or boot up failed any idea how to recovery it
Click to expand...
Click to collapse
You should be very cautious when flash anything into Motorola phone, because it's based on Qualcomm system-on-chip, that has many security checks.
Looks like wrong model was flashed. Execute command fastboot getvar all - that is needed to know the exact model of your Moto X.
Will this allow/prepare a phone to take OTA?
The prior owner of this AT&T Gen 1 Moto X (XT1058) had used some roms, but he advised he had returned it to stock. It never prompts for an OTA.
It is running 4.4.4
baseband MSM8960PRO_BP_2323.038.123.00R
System Version 212.44.26.ghost_att.ATT.en.US
Build KXA21.12-L1.26
Is there any way to go back?
I mean, i did this method like 1 year ago... but now I don't remember what I did...
My phone doesn't have recovery and I can't format it
Thoyito said:
I don't remember what I did...
Click to expand...
Click to collapse
Execute command fastboot getvar all to know the exact model of your Moto X, and ROM installed.
Hi there,
I tried to update my Moto G4 Plus and I think I made some big mistakes..
I can only start into Bootloader with the following text shown below:
AP Fastboot Flash Mode (Secure)
BL: B0.0E (sha-4986429, 2016-104-13 14:23:47)
Baseband: [bla] ATHENE_EMEA_DSDS_CUST
Product/Variant: athene_16mp XT1642 16GB P2A
Serial Number: [bla]
CPU: MSM8952
eMMC: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000007
DRAM: 2GB SAMSUNG LP3 DIE=8GB M5=01 M6=05 M7=00 M8=5f
Console [NULL]: null
Battery OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
Click to expand...
Click to collapse
- No TWRP or other Recovery
- No OS
- No Fastboot connection to my Win10 64bit anymore (
I think the problem is the "AP Fastboot Flash Mode (Secure)" Mode.
Any ideas how to solve it?!
thanks alot anyway
The AP Fastboot Flash mode(secure) seems okay to me. However it is highly possible that your drivers aren't installed on the phone. So in this case try to first connect the phone to the computer and see if it get's detected or not, and then you should manually install the fastboot USB driver. Download the driver zip from Google's repository and extract it, later choose the .inf file and then the Android Bootloader Interface.
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
PS: This driver and the fastboot adb binaries are completely different thing. fastboot won't work unless you have this USB driver.
Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.
I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But I get the same message in cmd as always. < waiting for device > I dont know what to do..
edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!
Tanks alot!
Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".
Do I have to install anything else like a boot.img? I made a full wipe..
Can I use the ElementalX Kernel?
stefanhanz said:
Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.
I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But I get the same message in cmd as always. < waiting for device > I dont know what to do..
edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!
Tanks alot!
Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".
Do I have to install anything else like a boot.img? I made a full wipe..
Can I use the ElementalX Kernel?
Click to expand...
Click to collapse
The latest stock ROM is the NPJS25.93-14-10 (Sept 2017 security patch) build https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
You'll have to flash the stock ROM in fastboot, which would wipe TWRP off your device again. You cannot properly flash stock firmware in TWRP (only can flash the system in TWRP).
Once you've flashed the stock ROM and TWRP, you can use ElementalX, I'm using the 1.0.4 stock version on the NPJS25.93-14-10 build with magisk 13.3 (to root) and it's running stably on my XT1642.
Thank you! Now its working as it should with the newest updates!
Thread can be closed. Thanks
stefanhanz said:
Thank you! Now its working as it should with the newest updates!
Thread can be closed. Thanks
Click to expand...
Click to collapse
Hello Friend
I would like to know if you can explain how to fix it is that the same happens to me the ap fastboot flash mode * secure * because before I had already used the blanckflash to revive it because first soo turned on the white led
sersrendon said:
Hello Friend
I would like to know if you can explain how to fix it is that the same happens to me the ap fastboot flash mode * secure * because before I had already used the blanckflash to revive it because first soo turned on the white led
Click to expand...
Click to collapse
Does anyone know what happened?
I updated the rom appeared this message.
Cell Phone: Moto g 4
Please help me :crying: :crying:
Imagens:
h t t p s:/ /goo.gl/nupYsT
h t t p s:/ /goo.gl/G8KNNV
Rog Ballester said:
Does anyone know what happened?
I updated the rom appeared this message.
Cell Phone: Moto g 4
Please help me :crying: :crying:
Imagens:
h t t p s:/ /goo.gl/nupYsT
h t t p s:/ /goo.gl/G8KNNV
Click to expand...
Click to collapse
Looks like you've used the blankflash and your device is in the temporary bootloader, waiting for a stock firmware flash to repair.
You could flash the latest December 2017 stock firmware here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
You do not have to use the OEM lock commands whilst flashing. Also, be aware this flashing procedure will erase your device. As always, if this works please do not flash older stock firmwares if you can, else you may hard brick again.
echo92 said:
Looks like you've used the blankflash and your device is in the temporary bootloader, waiting for a stock firmware flash to repair.
You could flash the latest December 2017 stock firmware here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
You do not have to use the OEM lock commands whilst flashing. Also, be aware this flashing procedure will erase your device. As always, if this works please do not flash older stock firmwares if you can, else you may hard brick again.
Click to expand...
Click to collapse
Não estou conseguindo, de uma olhada nessas imagens por favor
https: / /goo.gl/nupYsT
https: / /goo.gl/G8KNNV
Rog Ballester said:
Não estou conseguindo, de uma olhada nessas imagens por favor
https: / /goo.gl/nupYsT
https: / /goo.gl/G8KNNV
Click to expand...
Click to collapse
1) please post in English in these forums.
2) the images load up okay, you may require a Facebook account to access after removing the spaces in the link.
3) again, from what I see in the pictures, it appears your device has been flashed with a temporary bootloader and requires a full firmware flash. The above stock ROM should work with XT1626 devices, you may wish to check the stock ROM thread to confirm.
Edit: here are a couple of reports suggesting the ROM works on XT1626 devices. https://forum.xda-developers.com/showpost.php?p=75139620&postcount=538 https://forum.xda-developers.com/showpost.php?p=75263192&postcount=573
echo92 said:
1) please post in English in these forums.
2) the images load up okay, you may require a Facebook account to access after removing the spaces in the link.
3) again, from what I see in the pictures, it appears your device has been flashed with a temporary bootloader and requires a full firmware flash. The above stock ROM should work with XT1626 devices, you may wish to check the stock ROM thread to confirm.
Edit: here are a couple of reports suggesting the ROM works on XT1626 devices. https://forum.xda-developers.com/showpost.php?p=75139620&postcount=538 https://forum.xda-developers.com/showpost.php?p=75263192&postcount=573
Click to expand...
Click to collapse
When I pass the firmware flash, it comes back on the same screen
Gets stuck
:crying::crying:
Rog Ballester said:
When I pass the firmware flash, it comes back on the same screen
Gets stuck
:crying::crying:
Click to expand...
Click to collapse
Can I ask how you're flashing the firmware?
Have you got your device connected to your computer via USB?
Does your device show on your computer, and do you have the stock ROM downloaded and extracted to your ADB folder?
When you flash, do you see [okay] after each command?
I'd like to see a copy of the flashing output if possible please
echo92 said:
Can I ask how you're flashing the firmware?
Have you got your device connected to your computer via USB?
Does your device show on your computer, and do you have the stock ROM downloaded and extracted to your ADB folder?
When you flash, do you see [okay] after each command?
I'd like to see a copy of the flashing output if possible please
Click to expand...
Click to collapse
Yes, I have the room files.
Yes, my computer recognizes
I had the bootloader unlocked, I went to update and it caught
please look at the pictures:
https://goo.gl/q7AHhL
https://goo.gl/QstpTS
https://goo.gl/JSz8r2
Rog Ballester said:
Yes, I have the room files.
Yes, my computer recognizes
I had the bootloader unlocked, I went to update and it caught
please look at the pictures:
https://goo.gl/q7AHhL
https://goo.gl/QstpTS
https://goo.gl/JSz8r2
Click to expand...
Click to collapse
Okay, what about the rest of the flashing output, from starting with the fastboot flash partition gpt... command? I only see the end of the commands with fastboot OEM lock and fastboot reboot, where's the important section?
Also, you may wish to replace the NPJS25.93-14-8 stock ROM you have with the NPJS25.93-14-13 stock ROM if you see pre flash validation or security downgrade errors.
echo92 said:
Okay, what about the rest of the flashing output, from starting with the fastboot flash partition gpt... command? I only see the end of the commands with fastboot OEM lock and fastboot reboot, where's the important section?
Also, you may wish to replace the NPJS25.93-14-8 stock ROM you have with the NPJS25.93-14-13 stock ROM if you see pre flash validation or security downgrade errors.
Click to expand...
Click to collapse
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
Do you believe you can recover your cell phone?
Rog Ballester said:
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
Do you believe you can recover your cell phone?
Click to expand...
Click to collapse
I saw security downgrade errors, suggesting the stock ROM you are trying to flash is too old. Pre flash validation errors indicate the same thing, your downloaded stock ROM is not new enough to repair your device.
Please download the newest NPJS25.93-14-13 stock ROM as linked previously, delete the old stock ROM you have and replace with the newer stock ROM. Then try again. With a locked bootloader, especially, this is crucial. The bootloaders will block any attempts to flash old firmware if locked, hence why your device is still not working.
I've not bricked my phone, this process has been shown to work for others though. In some cases, flashing newer firmware than what you had could work. You have the June 2017 build, the NPJS25.93-14-13 build is December 2017.
echo92 said:
I saw security downgrade errors, suggesting the stock ROM you are trying to flash is too old. Pre flash validation errors indicate the same thing, your downloaded stock ROM is not new enough to repair your device.
Please download the newest NPJS25.93-14-13 stock ROM as linked previously, delete the old stock ROM you have and replace with the newer stock ROM. Then try again. With a locked bootloader, especially, this is crucial. The bootloaders will block any attempts to flash old firmware if locked, hence why your device is still not working.
I've not bricked my phone, this process has been shown to work for others though. In some cases, flashing newer firmware than what you had could work. You have the June 2017 build, the NPJS25.93-14-13 build is December 2017.
Click to expand...
Click to collapse
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
I wanted to thank you from the bottom of my heart. I got it sorted. Thank you so much for helping me. :good::fingers-crossed:
Rog Ballester said:
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
I wanted to thank you from the bottom of my heart. I got it sorted. Thank you so much for helping me. :good::fingers-crossed:
Click to expand...
Click to collapse
You're welcome
Please, in future, avoid downgrading your stock firmware if you can. If you do downgrade stock firmware, avoid OTA updates. Custom ROMs do not appear to matter in this regard.
I do not know if blankflashes will keep working as Motorola keeps updating the stock firmware. We may eventually need a new blankflash. Blankflashes are also rare as Motorola does not formally release them (luckily, we have a working one). So, do not rely on a blankflash to always bail you out of trouble.
stefanhanz said:
Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.
I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But I get the same message in cmd as always. < waiting for device > I dont know what to do..
edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!
Tanks alot!
Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".
Do I have to install anything else like a boot.img? I made a full wipe..
Can I use the ElementalX Kernel?
Click to expand...
Click to collapse
How did you installed twrp can you help me out please i am stuck on ap fastboot flash mode (secure)
with no rom and no recovery can you please help me? how will i get out of this situation? Please!
ILLUSORYINK said:
How did you installed twrp can you help me out please i am stuck on ap fastboot flash mode (secure)
with no rom and no recovery can you please help me? how will i get out of this situation? Please!
Click to expand...
Click to collapse
How did you get into this state in the first place?
I see from your other post you installed AICP, so you must have TWRP on your device already?
If you need to re-flash TWRP, then boot your device to the bootloader.
Connect your device to your computer, preferably with the original USB cable.
Open the ADB terminal on your computer, and ensure you have the TWRP flashable image on your computer, in your ADB folder.
In the ADB terminal, type 'fastboot devices' without quotes, ensure you get a serial number response from your device.
If you get a response, then type 'fastboot flash recovery <name of TWRP image>' without quotes, where the <name of TWRP image> is the TWRP image file name as on your computer. Ensure the file name is the same, taking into account file name extensions.
You should have flashed TWRP to your recovery partition on your device - use the volume keys on your device to select 'Recovery' then press the power button to boot to recovery. You should be booting to TWRP recovery.
In there, you should be able to copy a custom ROM and flash that within TWRP. Alternatively, you could download a fastboot stock ROM and flash that within fastboot (not TWRP) to restore your device, but ensure it's the correct and latest stock ROM for your device.
Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode
REQUIREMENTS -
1 - Setup adb and fastboot on your PC.
2- Stock boot image (boot.img) of your device (extract file from factory image android P)
3 - Last Magisk Manager (v 5.8.3)
4 - Active Internet connection
5 - Active mind and patience.
6 - Devices must is unlock bl.
This Boot-Image is for boot android P PPR1.180610.009:
https://drive.google.com/open?id=166pE9aMk-jqns3JM74enFhsaDY6-c3yJ
Magisk Manager
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
==================================================
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta
7- Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk
CREDITS
@topjohnwu (Magisk)
Sadly goes into a bootloop for me - no idea why though
This worked for me. I had magisk installed and took the pie update. No more root. D/l the factory image and extracted the boot image to the files folder...pissmeoff they changed the name of the icon... and magisk patched the image and saved it in its folder. Found the file, moved it to the laptop then flashed it.
reawo said:
Sadly goes into a bootloop for me - no idea why though
Click to expand...
Click to collapse
I think you made a mistake.
I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide
reawo said:
I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide
Click to expand...
Click to collapse
I think you use my file(boot.img) for patch_boot.img from magisk manager.
I think you must check your build number devices.
You must use file boot.img from your factory image for root.
9.0.0 (PPR1.180610.009, Aug 2018) >This is version for my devices
9.0.0 (PPR1.180610.011, Aug 2018, Telstra) >?
hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?
reawo said:
hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?
Click to expand...
Click to collapse
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin
newyesor said:
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin
Click to expand...
Click to collapse
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?
I receive also a bootloop and I didnt make any mistake. I also used this method pre Pie, I read that alot of users have problems with rooting Pie atm, even with TWRP
reawo said:
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?
Click to expand...
Click to collapse
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.
newyesor said:
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.
Click to expand...
Click to collapse
I downloaded all the latest adb and fastboot. Never touched kernel or did custom recovery, always used the magisk method since i am on a pixel device. i also got the issue that my pc doesnt recognize my pixel from time to time, you think i should do a complete wipe?
I don't sure.
You are use platfrom-tool from sdk lastversion?(for flash via fastboot mode)
@reawo
I think you should flash factory image new again and factory reset your devices.
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta ,and close this app.****
7- Open app again and Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching (This process is not failed)***
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk
Will work on the verizon variant (bootloader locked)?
sabi95190 said:
Will work on the verizon variant (bootloader locked)?
Click to expand...
Click to collapse
Nope. If it were that easy for bootloader locked Verizon phones, it would have been done months ago.
What happens if you lock the bootloader after all of this?
DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
You'll wipe the phone, lose root, and be stock.
DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.
TonikJDK said:
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.
Click to expand...
Click to collapse
"Borderline"???? More like certifiably insane! ?