Moto G6 Plus - No bootable A/B slot, device not detected with adb. - Moto G6 Plus Questions & Answers

Hi,
I installed the PPW29.116-20 FIRMWARE for pie 9, it was working fine until I uninstalled magisk and now it will only boot to Fastboot mode saying "No bootable A/B slot".
The problem however it the device it no longer detected in adb to reinstall. adb devices returns no devices. This is odd as it was working fine before.
I have tried with both moto and universal adb drivers, changed cables and even changed computers - nothing it making it appear.
Any help would be much appreciated

Use Fastboot!
Ezcorpia said:
Hi,
I installed the PPW29.116-20 FIRMWARE for pie 9, it was working fine until I uninstalled magisk and now it will only boot to Fastboot mode saying "No bootable A/B slot".
The problem however it the device it no longer detected in adb to reinstall. adb devices returns no devices. This is odd as it was working fine before.
I have tried with both moto and universal adb drivers, changed cables and even changed computers - nothing it making it appear.
Any help would be much appreciated
Click to expand...
Click to collapse
Requirements:
Fastboot (because you're in Fastboot mode, lol) download links for Windows, Linux, Mac.
fastboot images for your ROM e.g. from this thread
fastboot flash file (contains flash commands, see in thread above)
Just unpack the zip file then open cmd/terminal, navigate to that folder and enter:
Code:
fastboot devices
When output looks like this your phone is detected:
Code:
XXXXXXXXX fastboot
'XXXXXXXXX' is your phone's serial number.
Unpack and copy the images and flash file into the same folder as fastboot. The folder contains following files:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On Windows double-click 'flashfileNoErase.bat' (ROM thread).
Check for errors, press enter and the phone will reboot.

had the same issue before
i had the same issue happen to me i about freaked out because i thought i had really jacked my phone up but i found this app called Lenovo Moto Smart Assistant it is a life saver trust me. if this happens to you then just download this app and it will walk you through the rest it has a upgrade and a rescue option the rescue option reinstalls the stock rom and and restores evrything back to normal on your phone. definite must have when flashing roms to your phone. :good:

lassemacchiato said:
Requirements:
Fastboot (because you're in Fastboot mode, lol) download links for Windows, Linux, Mac.
fastboot images for your ROM e.g. from this thread
fastboot flash file (contains flash commands, see in thread above)
Just unpack the zip file then open cmd/terminal, navigate to that folder and enter:
Code:
fastboot devices
When output looks like this your phone is detected:
Code:
XXXXXXXXX fastboot
'XXXXXXXXX' is your phone's serial number.
Unpack and copy the images and flash file into the same folder as fastboot. The folder contains following files:
On Windows double-click 'flashfileNoErase.bat' (ROM thread).
Check for errors, press enter and the phone will reboot.
Click to expand...
Click to collapse
I just want to thank you for this, I have been crying all night because I bricked my phone just a few hours before buying it, please know that you helped a stranger greatly-

#Starlord37# said:
i had the same issue happen to me i about freaked out because i thought i had really jacked my phone up but i found this app called Lenovo Moto Smart Assistant it is a life saver trust me. if this happens to you then just download this app and it will walk you through the rest it has a upgrade and a rescue option the rescue option reinstalls the stock rom and and restores evrything back to normal on your phone. definite must have when flashing roms to your phone. :good:
Click to expand...
Click to collapse
Phone of a friend suddenly died without any reason and wouldn't boot anymore. Tried this software out and it worked straight away. Requires a quick account registration however, but no biggie.
Thank you so much!

lassemacchiato said:
Requirements:
Fastboot (because you're in Fastboot mode, lol) download links for Windows, Linux, Mac.
fastboot images for your ROM e.g. from this thread
fastboot flash file (contains flash commands, see in thread above)
Just unpack the zip file then open cmd/terminal, navigate to that folder and enter:
Code:
fastboot devices
When output looks like this your phone is detected:
Code:
XXXXXXXXX fastboot
'XXXXXXXXX' is your phone's serial number.
Unpack and copy the images and flash file into the same folder as fastboot. The folder contains following files:
On Windows double-click 'flashfileNoErase.bat' (ROM thread).
Check for errors, press enter and the phone will reboot.
Click to expand...
Click to collapse
I dont finding the flashfilenoeraser.bat
But i found...
see bellow
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase ddr
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit

flashfileNoErase.bat
chptr0 said:
I dont finding the file "Flashfilenoeraser". Can u help me?
Click to expand...
Click to collapse
It's an attachment to the ROM thread I linked to.
Here's the direct link (download G6PlusFlashPieOfficial_NoErase.zip, just unpack and you have the right file):
G6PlusFlashPieOfficial.zip
G6PlusFlashPieOfficial_NoErase.zip

lassemacchiato said:
It's an attachment to the ROM thread I linked to.
Here's the direct link (download G6PlusFlashPieOfficial_NoErase.zip, just unpack and you have the right file):
G6PlusFlashPieOfficial.zip
G6PlusFlashPieOfficial_NoErase.zip
Click to expand...
Click to collapse
Thanks for your help!!!

Related

Android 5.0.2 Factory image[BR]

hello all today i am going to share factory images of Lollipop 5.0.2​
xt1033[Dual Sim]: Download Link
xt1032[Single Sim]: Download Link
Mfastboot: link
Steps to restore stock firmware:
1) Reboot the phone into bootloader mode. There are 2 ways to do this.
I) The 'hardware' way.
a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.
II) The 'software' way.
a) Enable developer mode on the Moto G (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB, you should see a new ADB device detected and drivers installed.
d) Open "Minimal ADB and Fastboot". Type:
Fastboot commands:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
have attached batch file for easy flashing
Happy flashing
xt1032 mirror by @likurik : Download link
reserved 1
Can you show the contents of the file?
Sent from my Nexus 5
three hours to download one zip.file.Nice!
Mirror for xt1032 https://mega.co.nz/#!rNASwDhJ!aFGvFF0atLS2QisasQYhchxig718AUW6wU2CpeufK1Y
uhm... ooookkk... you know there are factory images already available for about 2 weeks ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone knows a Recovery, which is compatible with the new bootloader?
Go to development section and check recovery threads, it's clearly mentioned there with what it's compatible. Small hint, latest TWRP for example.
brainscollector said:
Go to development section and check recovery threads, it's clearly mentioned there with what it's compatible. Small hint, latest TWRP for example.
Click to expand...
Click to collapse
No, New TWRP isnt compartible with this update. I have tested it! I think the Problem is the partition, with the update the partition is smaller
I downloded it, i was GPE 5.0.1, tryed to flash via fastboot but the phone dont boot, its blocked @ bootloder unlocked image. the install seems to have no errors... any ideas?
ROOT FOR MOTO G LOLLIPOP 5.0.x
jonas210678 said:
No, New TWRP isnt compartible with this update. I have tested it! I think the Problem is the partition, with the update the partition is smaller
Click to expand...
Click to collapse
http://techerrata.com/file/twrp2/xt1032/openrecovery-twrp-2.8.1.0-xt1032.img
Also you don't need to use superuser flashable by custom recovery,
http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
For all Moto G variants, and works fine. Just turn on into fastboot mode, plug in phone (remember to have enabled USB Debuging in developer options), unzip archive and run windows bat to root device. I can confirm it's working as tested by myself. No custom recovery needed, just unlocked bootloader (obviously) and it's done.
I'm proposing to follow this guide for theaking
http://forum.xda-developers.com/moto-g/general/tweaks-motorola-stock-5-0-2-basic-tweaks-t3012488
And use greenify with donation pack to maintain full control over running apps
jonas210678 said:
No, New TWRP isnt compartible with this update. I have tested it! I think the Problem is the partition, with the update the partition is smaller
Click to expand...
Click to collapse
Lastest TWRP is as compatible as on GPE 5.0.1. Tried myself 3 days ago, rooted from there.
stock!!!???
excuse me for asking but I am new here , so I want to Know , is this an official firmware from google and can I get future updates after flashing this rom ??
abd8030 said:
excuse me for asking but I am new here , so I want to Know , is this an official firmware from google and can I get future updates after flashing this rom ??
Click to expand...
Click to collapse
It's Official Firmware from Motorola and yes, you will recieve future updates.
pico hackr said:
hello all today i am going to share factory images of Lollipop 5.0.2
Click to expand...
Click to collapse
please share your links in the existing thread in the development section.
Thread closed

Wifi not working X1575

Hi, I have the X1575 stock firm 6.0, I recently rooted the phone and I think I used a logo.bin for another version and my Wifi its not working, the switch wont stay ON.
I dont have a backup, What can I do? PS. The options in my bootloader screen looks different now.
salvadorposse said:
Hi, I have the X1575 stock firm 6.0, I recently rooted the phone and I think I used a logo.bin for another version and my Wifi its not working, the switch wont stay ON.
I dont have a backup, What can I do? PS. The options in my bootloader screen looks different now.
Click to expand...
Click to collapse
just replace the logo.bin with the correct 1from stock
the-light said:
just replace the logo.bin with the correct 1from stock
Click to expand...
Click to collapse
Thanks, but I'm afraid that hasn't worked.
I think is something else, I'm getting this error in the log:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
salvadorposse said:
Hi, I have the X1575 stock firm 6.0, I recently rooted the phone and I think I used a logo.bin for another version and my Wifi its not working, the switch wont stay ON.
I dont have a backup, What can I do? PS. The options in my bootloader screen looks different now.
Click to expand...
Click to collapse
logo.bin has nothing to do with WiFi working/not-working, at all.
Flash NON-HLOS.bin from the stock image using fastboot. If SuperSU got installed as system root, backup everything, re-flash the stock MPHS24.49-18-4 firmware, flash TWRP, then SuperSU as systemless.
And since that firmware thread is discombobulated and somewhat outdated, the correct commands to flash the firmware is
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
Thanks, I re-flashed the stock and its working just fine, however, twrp its not been installed, Im flashing it using fastboot flash recovery twrp.img and its seems OK but when I try to go to the recovery mode its the android recovery what I find.
Any other suggestion on how can I install the twrp and then supersu?
Spasticdroid said:
logo.bin has nothing to do with WiFi working/not-working, at all.
Flash NON-HLOS.bin from the stock image using fastboot. If SuperSU got installed as system root, backup everything, re-flash the stock MPHS24.49-18-4 firmware, flash TWRP, then SuperSU as systemless.
And since that firmware thread is discombobulated and somewhat outdated, the correct commands to flash the firmware is
Click to expand...
Click to collapse
salvadorposse said:
Thanks, I re-flashed the stock and its working just fine, however, twrp its not been installed, Im flashing it using fastboot flash recovery twrp.img and its seems OK but when I try to go to the recovery mode its the android recovery what I find.
Any other suggestion on how can I install the twrp and then supersu?
Click to expand...
Click to collapse
If TWRP doesn't stick after trying Reboot > Recovery, flash it once more. While in there, go to Mount and checkmark System. Then go back to Advanced > File Manager and either delete, or add ".bak" to the following files:
/system/recovery-from-boot.p
/system/etc/install-recovery.cfg
/system/etc/recovery-resource.dat
That should make it stick.
Thank you very much Sir!
TWRP will fix itself... Once you flash TWRP and start it, go to Reboot in TWRP and select Recovery, the device will restart and TWRP will load, it will stay from now on.

How to install and use ADB and fastboot

1.
Connect your Android device to computer via USB.
2.
Ensure USB Debugging mode is ENABLED on Android device.
Settings > About Phone > Build number > Tap it 7 times to become developer;
Settings > Developer Options > USB Debugging.
3.
download adb driver
http://adbdriver.com/downloads/
download Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
4.
unzip adb driver and instal it
http://adbdriver.com/documentation/...river-installer-for-windows-xp-vista-7-8.html
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
5.
Extract the Minimal ADB and Fastboot Tool file to your PC
6.
Download your RecoveryFile.img file or full fastboot Rom file
and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ”
so all files will be in single folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7.
open folder Minimal ADB and Fastboot
in the folder , On your keyboard press SHIFT and right click with your mouse " Shift + right click "
click on " open command window here "
8.
Now type following command
adb fastboot
Unlocking the bootloader
Note: Using the fastboot command
When the fastboot command is used on the Storm, the vendor id command option must be added.
The vendor id for the Storm is 0x2970. For example, fastboot devices, would be fastboot -i 0x2970 devices.
Enable OEM unlock in the Developer options settings on the device.
(Note: Not all devices have this setting, so continue with next step if yours does not.)
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
If you see "no permissions fastboot", try running fastboot as root.
From the same terminal, type the following command to unlock the bootloader:
fastboot -i 0x2970 oem unlock-go
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
fastboot reboot
Installing a custom recovery using fastboot
Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.img
where the latter part is the filename of the recovery image.
fastboot reboot
full rom fastboot
adb reboot bootloader
fastboot devices
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot reboot
Thanks for the great step by step tutorial.
I've tried to instal the Fastboot Image via the above guidem
1. Connect your Android device to computer via USB.
2. Ensure USB Debugging mode is ENABLED on Android device.
3. download adb driver
4. unzip adb driver and instal it
5. Extract the Minimal ADB and Fastboot Tool file to your PC
6. Download your RecoveryFile.img file or full fastboot Rom file and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ” so all files will be in single folder. (Which I've done with TOS319I Fastboot Image file)
7. open folder Minimal ADB and Fastboot, click on " open command window here "
8. Now type following command
adb fastboot
Unlocking the bootloader
adb reboot bootloader
fastboot reboot
Then, adb reboot bootloader
fastboot devices
*** But when I use the fastboot flash recovery TOS319I.img and to use the downloaded and renamed recover image, it says unable to load file TOS319I.img
Can you please let me know what should I do?
Thanks in advance
sellfy said:
Thanks for the great step by step tutorial.
I've tried to instal the Fastboot Image via the above guidem
1. Connect your Android device to computer via USB.
2. Ensure USB Debugging mode is ENABLED on Android device.
3. download adb driver
4. unzip adb driver and instal it
5. Extract the Minimal ADB and Fastboot Tool file to your PC
6. Download your RecoveryFile.img file or full fastboot Rom file and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ” so all files will be in single folder. (Which I've done with TOS319I Fastboot Image file)
7. open folder Minimal ADB and Fastboot, click on " open command window here "
8. Now type following command
adb fastboot
Unlocking the bootloader
adb reboot bootloader
fastboot reboot
Then, adb reboot bootloader
fastboot devices
*** But when I use the fastboot flash recovery TOS319I.img and to use the downloaded and renamed recover image, it says unable to load file TOS319I.img
Can you please let me know what should I do?
Thanks in advance
Click to expand...
Click to collapse
i know that you should use cyanogen os version rom of wileyfox storm (FIRST)
then you can flash custom rom or upgrade to official android 7 rom
that means , first you should downgrade to cyanogen 13
Again bootloop
ghertas said:
1.
Connect your Android device to computer via USB.
2.
Ensure USB Debugging mode is ENABLED on Android device.
Settings > About Phone > Build number > Tap it 7 times to become developer;
Settings > Developer Options > USB Debugging.
3.
download adb driver
http://adbdriver.com/downloads/
download Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
4.
unzip adb driver and instal it
http://adbdriver.com/documentation/...river-installer-for-windows-xp-vista-7-8.html
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
5.
Extract the Minimal ADB and Fastboot Tool file to your PC
6.
Download your RecoveryFile.img file or full fastboot Rom file
and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ”
so all files will be in single folder
7.
open folder Minimal ADB and Fastboot
in the folder , On your keyboard press SHIFT and right click with your mouse " Shift + right click "
click on " open command window here "
8.
Now type following command
adb fastboot
Unlocking the bootloader
Note: Using the fastboot command
When the fastboot command is used on the Storm, the vendor id command option must be added.
The vendor id for the Storm is 0x2970. For example, fastboot devices, would be fastboot -i 0x2970 devices.
Enable OEM unlock in the Developer options settings on the device.
(Note: Not all devices have this setting, so continue with next step if yours does not.)
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
If you see "no permissions fastboot", try running fastboot as root.
From the same terminal, type the following command to unlock the bootloader:
fastboot -i 0x2970 oem unlock-go
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
fastboot reboot
Installing a custom recovery using fastboot
Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.img
where the latter part is the filename of the recovery image.
fastboot reboot
full rom fastboot
adb reboot bootloader
fastboot devices
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
I've exactly followed your instructions for *"full rom fastboot"*, and all was done 'OK'. But Still the device is in bootloop and not going into recovery OR andriod system
ghertas said:
"full rom" was a zip file of cyanogen version
cyanogen realised two files of each rom
recovery version and fastboot version
if you want to install a custom rom on your device
Yes, I've download cyanogen Fastboot version, The only problem i've got is that my phone doesn't go into recovery mode although I've flashed TWRP also cn 13, but still the device only boots in fastboot only
When I select Recovery mode in Fastboot menu the device goes into bootloop.
Click to expand...
Click to collapse
idforpc said:
ghertas said:
"full rom" was a zip file of cyanogen version
cyanogen realised two files of each rom
recovery version and fastboot version
if you want to install a custom rom on your device
Yes, I've download cyanogen Fastboot version, The only problem i've got is that my phone doesn't go into recovery mode although I've flashed TWRP also cn 13, but still the device only boots in fastboot only
When I select Recovery mode in Fastboot menu the device goes into bootloop.
Click to expand...
Click to collapse
"fastboot reboot"
after boot the device , "Power off" the device and press volume down and power at the same time until you see the recovery on screen
"TWRP" is a custome recovery for install custom rom s
did you do all of those on " lineage wiki " ?
https://wiki.lineageos.org/devices/kipper/install
download the last version of twrp recovery
https://androidfilehost.com/?fid=1395089523397922500
Click to expand...
Click to collapse

Need some advice for my xt1562

I'm new here, so sorry if this is a duff post.
I've done searches to no avail.
I bought my x play second hand. It's been rooted to a none stock android 7.0. I'm having issues with sd card being unrecognised. I've read that this could be a motherboard problem. I've checked it with a number of different cards that all work absolutely fine on other devices.
My question is, would it help if I returned my phone to stock then upgraded to the proper versions of android via the download direct to phone?
If so, is there an updated method? The one I tried to follow uses SDK but the instructions seem to be for an old version (it's a 2015 post) as the version of Android Studio I installed seems to be unrecognisable from what is being described. I'm not savvy enough with these systems to work out what I need to do instead.
Thanks in advance.
Another thought, would it be worth installing a different none stock ROM?
if you are rooted, install twrp and try other custom rom
if you need install marshmallow with fastboot:
marshmallow pack with update 1 october 2016 update
Code:
https://my.pcloud.com/publink/show?code=XZ7WHdZJvy0fTbyYKuY5rtBpSzQD79KkAey
adb fastboot app:
Code:
https://my.pcloud.com/publink/show?code=XZcmHdZk8WW37zD64Q158z63w8dFyNGH8zX
extract marshmallow pack in adb fastboot folder like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
install 6.0.1 with adb commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
or faster - put this file in adb folder and use it:
Code:
https://my.pcloud.com/publink/show?code=XZv1HdZNploxJptYcYB2gNS28m2y5v8eqkX
wiemar said:
if you are rooted, install twrp and try other custom rom
if you need install marshmallow with fastboot:
marshmallow pack with update 1 october 2016 update
Code:
https://my.pcloud.com/publink/show?code=XZcmHdZk8WW37zD64Q158z63w8dFyNGH8zX
adb fastboot app:
Code:
https://my.pcloud.com/publink/show?code=XZcmHdZk8WW37zD64Q158z63w8dFyNGH8zX
extract marshmallow pack in adb fastboot folder like this:
install 6.0.1 with adb commands:
or faster - put this file in adb folder and use it:
Code:
https://my.pcloud.com/publink/show?code=XZv1HdZNploxJptYcYB2gNS28m2y5v8eqkX
Click to expand...
Click to collapse
Thanks for replying, I really appreciate the effort.
A lot of this is just words on my screen. I may be able to work out what some of this means given time. Which folders am I putting stuff in? On phone or PC? Also the top 2 http adresses are the same, is this intentional?
Thanks again.
my mistake. edited links. fastboot on pc and extract marshmallow pack inside adb folder. look at screen
Will LTE work on this MM 6.0.1 ROM?
wiemar said:
if you are rooted, install twrp and try other custom rom
if you need install marshmallow with fastboot:
marshmallow pack with update 1 october 2016 update
Will LTE work fine with this MM 1-Oct-2016 ROM?
Also instead of running all these commands one after another, can you please point me to a .zip file, which i can directly flash it from TWRP like other ROMs? Thats much easier for me than running all these commands manually.
Click to expand...
Click to collapse
lte works normaly.
you need find backup from stock that can be installed from twrp. i don't have it. adb fastboot method is faster. and you don't read all my answers. you don't need use commands, just 1 file.
Really appreciate the links and steps!!! Thanks.
wiemar said:
lte works normaly.
you need find backup from stock that can be installed from twrp. i don't have it. adb fastboot method is faster. and you don't read all my answers. you don't need use commands, just 1 file.
Click to expand...
Click to collapse
Currently I am running on LIneageOS Nougat 7.1.1. I am planning to do this downgrade to MM if I really don't like the battery backup on Nougat 7.1.1.
Really appreciate the links and steps!!! Thanks.
---------- Post added at 09:08 AM ---------- Previous post was at 08:46 AM ----------
wiemar said:
lte works normaly.
you need find backup from stock that can be installed from twrp. i don't have it. adb fastboot method is faster. and you don't read all my answers. you don't need use commands, just 1 file.
Click to expand...
Click to collapse
BTW, one question. How do you run that single batch file?
... restart phone to bootloader, connect to pc, and run this file.
Okay, I've now discovered that TWRP is already installed. Can I use any xt1562 zipped Rom or does it need to be specific to TWRP. I've put the zip on my phone ready to go and done a nandroid backup but wanted to check first before I hit install.
Thanks again

Bootloader broken? Npn25.137-83 xt1687 help!

Hi, I have a problem with the "Unlock OEM" option
I already have unlocked the bootloader does not let me do a RE-LOCK Since it does not let me activate the option in developer options, I am currently in stock without modifications, I need to know how to activate the option "Unlock OEM" Having the bootloader unlocked
I already tried to block it again but it tells me that I need to activate the option in fastboot
HEEEELP:crying::crying:
SCREENSHOT OF THE OPTION DISABLED
View attachment 4335329
You need to run the same command twice in a row.
Karlinski said:
You need to run the same command twice in a row.
Click to expand...
Click to collapse
What command, the option in dev options is buged?
Fastboot: "You need activate Unlock Oem in Dev Options" but i can't because the options is not available
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To relock you need to reflash the stock image... I don't think we have that version yet.
acejavelin said:
To relock you need to reflash the stock image... I don't think we have that version yet.
Click to expand...
Click to collapse
I have the full firmware of this version, i tried with Npn 35-5 and 35 and not luck for me, the option are Disabled ever :crying:
JassyelZ said:
I have the full firmware of this version, i tried with Npn 35-5 and 35 and not luck for me, the option are Disabled ever :crying:
Click to expand...
Click to collapse
I had that same issue and was able to relock by flashing NPN25.137-67-5 (Indian variant) on my XT1687 with the first line of commands. Then you can flash .35, .35-5 or -83 with the second line of commands. Although POTTER_RETAIL_7.0_NPNS25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip should flash same as NPN25.137-67-5 to relock the bootloader. The system remembers the most recent security patch and won't allow earlier patch updates to be flashed in that manner. 137-83 being the most recent. Hope this helps.
Be sure have drivers and ADB/Fastboot installed. Extract files into a folder containing adb/fastboot (I make copies of them to drop each set of files into) Run the relock commands one by one. But you can drag'n'drop the OTA update files into cmd and they'll auto-run. I just flashed to 137-83 that way.
Bootloader relock commands
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
Full flashing for OTA Update
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
JassyelZ said:
I have the full firmware of this version, i tried with Npn 35-5 and 35 and not luck for me, the option are Disabled ever :crying:
Click to expand...
Click to collapse
POTTER_RETAIL_7.0_NPNS25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from 'firmware center' will relock your bootloader. I just tested it on mine and no errors.
Here's the process:
i imgur com /HkJzfKp png (cause I can't post links ) Periods in the first 2 and last space, move the forward slash over.

Categories

Resources