A few days ago decided to flash back my one plus one to Cyaonogenmod11S kitkat because I could not stand 5.02 lollipop (huge battery drain, nova launcher bugs, touch screen issues etc.)
I did this following a guide (can't post the url )
Everything went fine, and I got my phone up to kitkat 44s
But, I'm having a huge issue that when I try to call someone, the screen turns black straight away and there is no way for me to get back from the black screen except for using the power button to end the conversation.
I read that most likely it's an issue with the proximity sensor that needs recalibration but I have no clue how I would go about doing that.
For your information I flashed the files from this guide onto my phone: Three signed flashables zips for 33R 38R and 44S
(seems that I can't use URLS yet)
Plus two files for the 44s firmware (modem file and another file). I also tried the modem firmware of 33r but this also didn't fix it.
I've also download a proximity sensor app which showed the following values for my sensor:
It shows the following values for my sensor:
0: 0.0
1: 32767.0
2: -0.047822422
Just to be clear, before I flashed back to 44s I did not have this problem, so I'm pretty sure its software and not hardware related (sensor is not broken).
Any help would be greatly appreciated! :good:
I just wanted to let you know I fixed the issue by flashing a fastbootimage.
Now the screen no longer turns black during calls!
Rixxos said:
I just wanted to let you know I fixed the issue by flashing a fastbootimage.
Now the screen no longer turns black during calls!
Click to expand...
Click to collapse
Which fastboot image did you flash? Having the same problem.
Me too - what did you flash?
toohsieh said:
Which fastboot image did you flash? Having the same problem.
Click to expand...
Click to collapse
therealgiblet said:
Me too - what did you flash?
Click to expand...
Click to collapse
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Thanks but that is no help whatsoever.
I've read through the REF thread - I've flashed 241 - have data and signal back now but screen black during calls, proximity sensor test shows fixed values, gestures don't work (V for light etc).
Tried reflashing 241 twice - cleared Dalvic - still not working. There doesn't seem to be a fix for everyone - it just seems like some people have been lucky and most haven't.
Going to try older version of TWRP now but slowly thinking that this phone is going back to 11S with all its bugs (the keyboard one was the worst). TBH I'm getting rid of this phone as soon as I get a chance as I'm fed up with it. One Plus can have a video of me smashing their phone - even though didn't agree with their dumb marketing campaign this is one phone I'll enjoy smashing.
No more One Plus for me.
therealgiblet said:
Thanks but that is no help whatsoever.
I've read through the REF thread - I've flashed 241 - have data and signal back now but screen black during calls, proximity sensor test shows fixed values, gestures don't work (V for light etc).
Tried reflashing 241 twice - cleared Dalvic - still not working. There doesn't seem to be a fix for everyone - it just seems like some people have been lucky and most haven't.
Going to try older version of TWRP now but slowly thinking that this phone is going back to 11S with all its bugs (the keyboard one was the worst). TBH I'm getting rid of this phone as soon as I get a chance as I'm fed up with it. One Plus can have a video of me smashing their phone - even though didn't agree with their dumb marketing campaign this is one phone I'll enjoy smashing.
No more One Plus for me.
Click to expand...
Click to collapse
Well, if you had given all of that information in the first place...
TBH I wasn't actually asking you the question - I wanted the OP to tell us what file he flashed to fix the problem.
Annoyingly - he probably won't as he posted quite a while ago... never mind he probably just got lucky - I'll just assume this phone is doomed to fail as One Plus and Cynagoen aren't going to bother fixing anything - priorities lie elsewhere for both companies.
Just can't understand how such an important part of the phone (the actual bit that makes phone calls and receives data) is so broken. Poor show.
therealgiblet said:
TBH I wasn't actually asking you the question - I wanted the OP to tell us what file he flashed to fix the problem.
Annoyingly - he probably won't as he posted quite a while ago... never mind he probably just got lucky - I'll just assume this phone is doomed to fail as One Plus and Cynagoen aren't going to bother fixing anything - priorities lie elsewhere for both companies.
Just can't understand how such an important part of the phone (the actual bit that makes phone calls and receives data) is so broken. Poor show.
Click to expand...
Click to collapse
I'm fairly confident that the problem here isn't due to a naturally occurring bug caused by CM or OnePlus, it's most likely you just have the wrong firmware/modem for whatever ROM you're on. 99% of the time this "bug" is caused by user error. It isn't their fault that users flash away and end up with misaligned firmware, causing this to happen. And no, I'm not trying to defend either company, I really don't like either. You mention using TWRP to flash which is probably half your problem. I'm assuming you're on a Lollipop ROM, the best idea is to download the latest stock images from here:
https://www.androidfilehost.com/?fid=24052804347802352
Then flash only the firmware components with fastboot:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash rpm rpm.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot reboot
Heisenberg said:
I'm fairly confident that the problem here isn't due to a naturally occurring bug caused by CM or OnePlus, it's most likely you just have the wrong firmware/modem for whatever ROM you're on. 99% of the time this "bug" is caused by user error. It isn't their fault that users flash away and end up with misaligned firmware, causing this to happen. And no, I'm not trying to defend either company, I really don't like either. You mention using TWRP to flash which is probably half your problem. I'm assuming you're on a Lollipop ROM, the best idea is to download the latest stock images from here:
https://www.androidfilehost.com/?fid=24052804347802352
Then flash only the firmware components with fastboot:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash rpm rpm.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot reboot
Click to expand...
Click to collapse
I had completley stock 11S with lots of xposed modules that weren't initially supported on 12.1.
Eventually about a couple of weeks ago after nearly going insane due to the bug with the keyboard I thought sod it - I'll 'upgrade' to 12.1
I upgrade to 12.1 and didn't notice the data issue (constant ! by signal bars and sporadic data connection) - just thought my network provider had problems.
A few days ago I got so annoyed with the data issue I looked online and saw various threads detailing 'issues' with the 12.1 modem.
The fix people were quoting was to install an older modem. I installed 241 and this fixed my mobile data issues. Unfortunately a side effect was that the proximity sensor was broken.
This is what I'm trying to fix.
I've just reflashed the 241 modem with TWRP 2.8.60 after downgrading from 2.8.7.0 and now my screen is not black in phone calls - so that's a great success.
Gestures are the only thing that aren't working (not the end of the world but I used the light shortcut 'V' on screen a lot).
If I could fix that I'd be very happy. I still think the proximity sensor isn't quite right as when I run a test on it the values remain static no matter how close I place my hand or how I touch the screen.
Thanks anyway
therealgiblet said:
I had completley stock 11S with lots of xposed modules that weren't initially supported on 12.1.
Eventually about a couple of weeks ago after nearly going insane due to the bug with the keyboard I thought sod it - I'll 'upgrade' to 12.1
I upgrade to 12.1 and didn't notice the data issue (constant ! by signal bars) - just thought my network provider had problems.
A few days ago I got so annoyed with the data issue I looked online and saw various threads detailing 'issues' with the 12.1 modem.
The fix people were quoting was to install an older modem. I installed 241 and this fixed my mobile data issues. Unfortunately a side effect was that the proximity sensor was broken.
This is what I'm trying to fix.
I've just reflashed the 241 modem with TWRP 2.8.60 after downgrading from 2.8.7.0 and now my screen is not black in phone calls - so that's a great success.
Gestures are the only thing that aren't working (not the end of the world but I used the light shortcut 'V' on screen a lot).
If I could fix that I'd be very happy. I still think the proximity sensor isn't quite right as when I run a test on it the values remain static no matter how close I place my hand or how I touch the screen.
Thanks anyway
Click to expand...
Click to collapse
How did you upgrade from CM11S to COS 12.1? Via TWRP? Via fastboot?
Uninstalled Xposed and all modules then followed the OTA update process including all incremental updates and patches.
You're going to tell me to do a clean install aren't you? I still don't think that will fix the issue with the modem as both these threads
http://forum.xda-developers.com/one...dio-updated-modem-radio-files-oxygen-t3072516
http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
have multiple reports of the same problems irespective of installation method... and they still require you to downgrade or revert to previous modem to fix the data and signal problems with the modem.
This is turn messes up the proximity and gestures sensor.
But I might be wrong (probably am )...
therealgiblet said:
Uninstalled Xposed and all modules then followed the OTA update process including all incremental updates and patches.
You're going to tell me to do a clean install aren't you? I still don't think that will fix the issue with the modem as both these threads
http://forum.xda-developers.com/one...dio-updated-modem-radio-files-oxygen-t3072516
http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
have multiple reports of the same problems irespective of installation method... and they still require you to downgrade or revert to previous modem to fix the data and signal problems with the modem.
This is turn messes up the proximity and gestures sensor.
But I might be wrong (probably am )...
Click to expand...
Click to collapse
Ok, but did you flash the update with TWRP or with the stock recovery? There may not be a need for a clean flash, I need to diagnose the cause in order to determine that though.
Heisenberg said:
Ok, but did you flash the update with TWRP or with the stock recovery? There may not be a need for a clean flash, I need to diagnose the cause in order to determine that though.
Click to expand...
Click to collapse
TBH - I didn't pay much attention to the whole upgrade process whilst it was happening.
I had TWRP installed on 11S but I don't how the system automated the update or what recovery it used.
I did have to reinstall TWRP after the update to 12.1 as I noticed the TWRP recovery had been overwritten and had reverted to the stock one...
Sorry not much help.
therealgiblet said:
TBH - I didn't pay much attention to the whole upgrade process whilst it was happening.
I had TWRP installed on 11S but I don't how the system automated the update or what recovery it used.
I did have to reinstall TWRP after the update to 12.1 as I noticed the TWRP recovery had been overwritten and had reverted to the stock one...
Sorry not much help.
Click to expand...
Click to collapse
TWRP would have installed the update, and because you were on 2.8.7.0 it was unable to flash the modem (that version can't flash modems). That's almost definitely what caused your initial problem, you were left with a KitKat modem while on a Lollipop ROM. The update did flash the stock recovery but that occurred during the boot afterwards. So the people who advised you to flash an older modem were incorrect, they were assuming you were on the latest modem and that that modem was causing the problem, when really it was the leftover KitKat modem causing the problem. At this stage you can go ahead and flash the files I mentioned earlier, and you can do so without having to wipe anything, this should ensure that everything is in line as it's meant to be.
Ok thanks a lot - I'll give it a go later when I'm not at work. Thanks again
therealgiblet said:
Ok thanks a lot - I'll give it a go later when I'm not at work. Thanks again
Click to expand...
Click to collapse
No problems, let me know how you go.
Heisenberg said:
No problems, let me know how you go.
Click to expand...
Click to collapse
Code:
C:\CM12>fastboot devices
9b612b68 fastboot
C:\CM12>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.018s]
writing 'aboot'...
OKAY [ 0.023s]
finished. total time: 0.044s
C:\CM12>fastboot flash LOGO logo.bin
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.015s]
writing 'LOGO'...
OKAY [ 0.022s]
finished. total time: 0.039s
C:\CM12>fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.827s]
writing 'modem'...
OKAY [ 0.717s]
finished. total time: 2.548s
C:\CM12>fastboot flash sbl1 sbl1.mbn
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.023s]
finished. total time: 0.039s
C:\CM12>fastboot flash dbi sdi.mbn
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.005s]
writing 'dbi'...
OKAY [ 0.015s]
finished. total time: 0.024s
C:\CM12>fastboot flash rpm rpm.mbn
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.011s]
writing 'rpm'...
OKAY [ 0.021s]
finished. total time: 0.035s
C:\CM12>fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.330s]
writing 'oppostanvbk'...
OKAY [ 0.149s]
finished. total time: 0.484s
C:\CM12>fastboot flash tz tz.mbn
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.017s]
writing 'tz'...
OKAY [ 0.022s]
finished. total time: 0.041s
C:\CM12>fastboot reboot
rebooting...
finished. total time: 0.008s
Right - done the above with the 'cm-12.1-YOG4PAS1N0-bacon-signed' firmware.
Nothing has changed - in fact the phone has reverted to having a black screen again in a phone call and gestures still do not work.
I checked 'About Device' in the settings and they seem no different from the ones previous to the fastboot flashing. I have screenshots but I just thought I'd clear Dalvic and phone is currently optimizing apps.
Sensor test - showed all sensors working except the Proximity/Gesture sensor - values remained static.
---------- Post added at 02:52 PM ---------- Previous post was at 02:29 PM ----------
Sensors
therealgiblet said:
Code:
C:\CM12>fastboot devices
9b612b68 fastboot
C:\CM12>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.018s]
writing 'aboot'...
OKAY [ 0.023s]
finished. total time: 0.044s
C:\CM12>fastboot flash LOGO logo.bin
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.015s]
writing 'LOGO'...
OKAY [ 0.022s]
finished. total time: 0.039s
C:\CM12>fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.827s]
writing 'modem'...
OKAY [ 0.717s]
finished. total time: 2.548s
C:\CM12>fastboot flash sbl1 sbl1.mbn
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.023s]
finished. total time: 0.039s
C:\CM12>fastboot flash dbi sdi.mbn
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.005s]
writing 'dbi'...
OKAY [ 0.015s]
finished. total time: 0.024s
C:\CM12>fastboot flash rpm rpm.mbn
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.011s]
writing 'rpm'...
OKAY [ 0.021s]
finished. total time: 0.035s
C:\CM12>fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.330s]
writing 'oppostanvbk'...
OKAY [ 0.149s]
finished. total time: 0.484s
C:\CM12>fastboot flash tz tz.mbn
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.017s]
writing 'tz'...
OKAY [ 0.022s]
finished. total time: 0.041s
C:\CM12>fastboot reboot
rebooting...
finished. total time: 0.008s
Right - done the above with the 'cm-12.1-YOG4PAS1N0-bacon-signed' firmware.
Nothing has changed - in fact the phone has reverted to having a black screen again in a phone call and gestures still do not work.
I checked 'About Device' in the settings and they seem no different from the ones previous to the fastboot flashing. I have screenshots but I just thought I'd clear Dalvic and phone is currently optimizing apps.
Sensor test - showed all sensors working except the Proximity/Gesture sensor - values remained static.
---------- Post added at 02:52 PM ---------- Previous post was at 02:29 PM ----------
Sensors
Click to expand...
Click to collapse
Gave up with a fix and installed 12.1 from scratch after wiping all partitions.
Everything is fine now... data, signal and gestures!
Thanks anyway
therealgiblet said:
Code:
C:\CM12>fastboot devices
9b612b68 fastboot
C:\CM12>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.018s]
writing 'aboot'...
OKAY [ 0.023s]
finished. total time: 0.044s
C:\CM12>fastboot flash LOGO logo.bin
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.015s]
writing 'LOGO'...
OKAY [ 0.022s]
finished. total time: 0.039s
C:\CM12>fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.827s]
writing 'modem'...
OKAY [ 0.717s]
finished. total time: 2.548s
C:\CM12>fastboot flash sbl1 sbl1.mbn
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.023s]
finished. total time: 0.039s
C:\CM12>fastboot flash dbi sdi.mbn
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.005s]
writing 'dbi'...
OKAY [ 0.015s]
finished. total time: 0.024s
C:\CM12>fastboot flash rpm rpm.mbn
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.011s]
writing 'rpm'...
OKAY [ 0.021s]
finished. total time: 0.035s
C:\CM12>fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.330s]
writing 'oppostanvbk'...
OKAY [ 0.149s]
finished. total time: 0.484s
C:\CM12>fastboot flash tz tz.mbn
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.017s]
writing 'tz'...
OKAY [ 0.022s]
finished. total time: 0.041s
C:\CM12>fastboot reboot
rebooting...
finished. total time: 0.008s
Right - done the above with the 'cm-12.1-YOG4PAS1N0-bacon-signed' firmware.
Nothing has changed - in fact the phone has reverted to having a black screen again in a phone call and gestures still do not work.
I checked 'About Device' in the settings and they seem no different from the ones previous to the fastboot flashing. I have screenshots but I just thought I'd clear Dalvic and phone is currently optimizing apps.
Sensor test - showed all sensors working except the Proximity/Gesture sensor - values remained static.
---------- Post added at 02:52 PM ---------- Previous post was at 02:29 PM ----------
Sensors
Click to expand...
Click to collapse
Out of interest, which build were you on at this point?
Related
Hello there guys! I'll resume my history.
So this was me one month after buying the Motorola Moto G XT1032 8GB, unlocking the bootloader without any problems So I wasn't really into the device info and didn't know about a GPE. So I downloaded a folder with a couple of images and .bin files and excuted a .bat inside the folder that turned my Stock 4.4.4 into Stock 4.4.2 GPE. After first reboot I just installed Paranoid Android and didn't come back to stock since then (a few months back).
Now I tried to go back to stock NON-GPE flashing "Android 4.3 Blur_Version.14.71.8.falcon_umts.Latam.en.AR" and "Android 4.4.2 Blur_Version.173.44.9.falcon_umts.Latam.en.AR" with this method GUIDE] Moto G - Restore stock firmware and I got this two errors in both of the cases:
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.030s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.363s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1940 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.405s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (619 KB)...
OKAY [ 0.079s]
writing 'logo'...
OKAY [ 0.161s]
finished. total time: 0.240s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.378s]
writing 'boot'...
OKAY [ 1.124s]
finished. total time: 1.502s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.379s]
writing 'recovery'...
OKAY [ 1.237s]
finished. total time: 1.617s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
sending 'system' (256840 KB)...
OKAY [ 8.098s]
writing 'system'...
OKAY [ 17.707s]
finished. total time: 25.805s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash system system.img_sparsechunk2
target reported max download size of 536870912 bytes
sending 'system' (243300 KB)...
OKAY [ 7.668s]
writing 'system'...
OKAY [ 14.775s]
finished. total time: 22.443s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash system system.img_sparsechunk3
target reported max download size of 536870912 bytes
sending 'system' (219577 KB)...
OKAY [ 6.920s]
writing 'system'...
OKAY [ 23.237s]
finished. total time: 30.157s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (47104 KB)...
OKAY [ 1.526s]
writing 'modem'...
OKAY [ 2.332s]
finished. total time: 3.859s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.070s]
finished. total time: 0.070s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.137s]
finished. total time: 0.137s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (107 KB)...
OKAY [ 0.082s]
writing 'fsg'...
OKAY [ 5.303s]
finished. total time: 5.385s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml#
Click to expand...
Click to collapse
You see? I got error with gtp.bin and motoboot.img but I kept flashing to see where that would take me. It turned out to take me witha bootloop Never going further than logo.
So what did I do? I ran that GPE 4.4.2 I flashed the first time I unlocked my bootloader. And it was alive again, booting like a charm. Now on crDroid again.
And my question is: what happened? Why am I able to flash a GPE 4.4.2 but not a Latam stock Retail for my country (Argentina)? I don't get it. I flashed from Windows and Ubuntu, with differents fastboot files, with mfasboot given in that Tutorial but nothing worked except turning it into a GPE Moto G.
Any contribution will be helpful, still want to go to stock Moto G. Cheers.
XXtremiXX said:
Hello there guys! I'll resume my history.
So this was me one month after buying the Motorola Moto G XT1032 8GB, unlocking the bootloader without any problems So I wasn't really into the device info and didn't know about a GPE. So I downloaded a folder with a couple of images and .bin files and excuted a .bat inside the folder that turned my Stock 4.4.4 into Stock 4.4.2 GPE. After first reboot I just installed Paranoid Android and didn't come back to stock since then (a few months back).
Now I tried to go back to stock NON-GPE flashing "Android 4.3 Blur_Version.14.71.8.falcon_umts.Latam.en.AR" and "Android 4.4.2 Blur_Version.173.44.9.falcon_umts.Latam.en.AR" with this method GUIDE] Moto G - Restore stock firmware and I got this two errors in both of the cases:
You see? I got error with gtp.bin and motoboot.img but I kept flashing to see where that would take me. It turned out to take me witha bootloop Never going further than logo.
So what did I do? I ran that GPE 4.4.2 I flashed the first time I unlocked my bootloader. And it was alive again, booting like a charm. Now on crDroid again.
And my question is: what happened? Why am I able to flash a GPE 4.4.2 but not a Latam stock Retail for my country (Argentina)? I don't get it. I flashed from Windows and Ubuntu, with differents fastboot files, with mfasboot given in that Tutorial but nothing worked except turning it into a GPE Moto G.
Any contribution will be helpful, still want to go to stock Moto G. Cheers.
Click to expand...
Click to collapse
Do this at your own risk:
If your phone is a gsm xt1032 then grab a EU(european) 4.4.4 stock firmware and flash that via fastboot. Should work...
If not then try flashing a custom recovery like twrp or clockworkmod. Grab the EU or US 4.4.4 untouched from this link: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and flash it via recovery.
I received my OnePlus One a few days ago and attempted install the 05q OTA update, however when the phone rebooted it was stuck in a bootloop where various artifacts would appear on screen before rebooting. I managed to flash back to the 44s firmware via fastboot and install TWRP and root the device.
I have tried to update the firmware via fastboot and TWRP but each time it ends up bootlooping. I have also tried to flash the CM12 nightlys, and although the install is successful, the same issue is present when trying to boot. Attempting to flash different kernels (eg. Franco kernel) has the same issues.
I'm not sure if this is a common problem or if I've just managed to get a dud phone. The phone I received seems to be the Chinese variant (Missing LTE bands), but it arrived with CM11S installed. Not sure if that would affect the ability to update?
Any help or information would be much appreciated
You shouldn't have any problems flashing regardless of which variant you have. Are you checking the md5 of downloaded files before flashing? Which firmware did you try to update? Saying "the firmware" is like saying nothing at all. Are you remembering to wipe properly before flashing CM12? Which version of which kernel was flashed on which ROM? There's a theme here, please provide more detailed information.
My first attempt was the OTA update from XNPH44S to XNPH05Q. This caused the device to get stuck at the OnePlus logo.
Then I proceeded to unlock the bootloader and attempt to flash the 05Q fastboot image located at http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746. It's appears to have successfully installed, but again, bootloops.
Flashing the 44S update from the link above worked.
As for CM12, a factory reset was performed before attempting to flash the cm-12-20150121-UNOFFICIAL-bacon.zip found here https://basketbuild.com/devs/klvnhng/cm-12.0_bacon. Successful install, but bootlooping persists.
Attempted to flash Franco kernel r35 found here http://kernels.franco-lnx.net/OnePlusOne/4.4/ over stock XNPH44S firmware. No luck.
If any more information is required do not hesitate to ask.
That all looks fine, except for the factory reset before flashing CM12. You really need a full wipe when changing ROMs like that, a full wipe consists of wiping system, data, cache, and dalvik cache. It seems odd that after flashing the stock images you'd end up in a bootloop. So when you say flashing the 44S update worked, you mean you flashed the 44S stock images with fastboot and the phone booted up and operated normally?
timmaaa said:
That all looks fine, except for the factory reset before flashing CM12. You really need a full wipe when changing ROMs like that, a full wipe consists of wiping system, data, cache, and dalvik cache. It seems odd that after flashing the stock images you'd end up in a bootloop. So when you say flashing the 44S update worked, you mean you flashed the 44S stock images with fastboot and the phone booted up and operated normally?
Click to expand...
Click to collapse
Correct. If I flash 44S the phone will boot normally, but if I try any other images (eg 05Q) it gets stuck.
samskies1 said:
Correct. If I flash 44S the phone will boot normally, but if I try any other images (eg 05Q) it gets stuck.
Click to expand...
Click to collapse
If you decide to make another attempt to flash the 05Q stock images, please copy/paste the text from the command prompt here do I can see.
Transmitted via Bacon
timmaaa said:
If you decide to make another attempt to flash the 05Q stock images, please copy/paste the text from the command prompt here do I can see.
Transmitted via Bacon
Click to expand...
Click to collapse
C:\Users\Samus\Desktop\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56369 KB)...
OKAY [ 1.782s]
writing 'modem'...
OKAY [ 1.243s]
finished. total time: 3.025s
C:\Users\Samus\Desktop\adb>fastboot flash sbl1 sbl1.mbn
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ -0.000s]
writing 'sbl1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash dbi sdi.mbn
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ -0.000s]
writing 'dbi'...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Samus\Desktop\adb>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\Samus\Desktop\adb>fastboot flash rpm rpm.mbn
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.000s]
writing 'rpm'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash tz tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ -0.000s]
writing 'tz'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash LOGO logo.bin
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.313s]
writing 'LOGO'...
OKAY [ 0.212s]
finished. total time: 0.525s
C:\Users\Samus\Desktop\adb>fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 536870912 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.328s]
writing 'oppostanvbk'...
OKAY [ 0.234s]
finished. total time: 0.563s
C:\Users\Samus\Desktop\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (5956 KB)...
OKAY [ 0.203s]
writing 'boot'...
OKAY [ 0.125s]
finished. total time: 0.328s
C:\Users\Samus\Desktop\adb>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (10432 KB)...
OKAY [ 0.328s]
writing 'cache'...
OKAY [ 0.500s]
finished. total time: 0.954s
C:\Users\Samus\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (7854 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.172s]
finished. total time: 0.422s
C:\Users\Samus\Desktop\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.332s]
sending sparse 'system' (524108 KB)...
OKAY [ 18.747s]
writing 'system'...
OKAY [ 23.967s]
sending sparse 'system' (320781 KB)...
OKAY [ 11.519s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 70.597s
C:\Users\Samus\Desktop\adb>fastboot flash userdata userdata_64G.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 3.751s]
sending 'userdata' (141075 KB)...
OKAY [ 4.436s]
writing 'userdata'...
OKAY [ 13.012s]
finished. total time: 21.199s
C:\Users\Samus\Desktop\adb>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\Samus\Desktop\adb>
samskies1 said:
C:\Users\Samus\Desktop\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56369 KB)...
OKAY [ 1.782s]
writing 'modem'...
OKAY [ 1.243s]
finished. total time: 3.025s
C:\Users\Samus\Desktop\adb>fastboot flash sbl1 sbl1.mbn
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ -0.000s]
writing 'sbl1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash dbi sdi.mbn
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ -0.000s]
writing 'dbi'...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Samus\Desktop\adb>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\Samus\Desktop\adb>fastboot flash rpm rpm.mbn
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.000s]
writing 'rpm'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash tz tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ -0.000s]
writing 'tz'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash LOGO logo.bin
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.313s]
writing 'LOGO'...
OKAY [ 0.212s]
finished. total time: 0.525s
C:\Users\Samus\Desktop\adb>fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 536870912 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.328s]
writing 'oppostanvbk'...
OKAY [ 0.234s]
finished. total time: 0.563s
C:\Users\Samus\Desktop\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (5956 KB)...
OKAY [ 0.203s]
writing 'boot'...
OKAY [ 0.125s]
finished. total time: 0.328s
C:\Users\Samus\Desktop\adb>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (10432 KB)...
OKAY [ 0.328s]
writing 'cache'...
OKAY [ 0.500s]
finished. total time: 0.954s
C:\Users\Samus\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (7854 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.172s]
finished. total time: 0.422s
C:\Users\Samus\Desktop\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.332s]
sending sparse 'system' (524108 KB)...
OKAY [ 18.747s]
writing 'system'...
OKAY [ 23.967s]
sending sparse 'system' (320781 KB)...
OKAY [ 11.519s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 70.597s
C:\Users\Samus\Desktop\adb>fastboot flash userdata userdata_64G.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 3.751s]
sending 'userdata' (141075 KB)...
OKAY [ 4.436s]
writing 'userdata'...
OKAY [ 13.012s]
finished. total time: 21.199s
C:\Users\Samus\Desktop\adb>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\Samus\Desktop\adb>
Click to expand...
Click to collapse
That all looks fine. But it's not booting correctly still?
Transmitted via Bacon
timmaaa said:
That all looks fine. But it's not booting correctly still?
Transmitted via Bacon
Click to expand...
Click to collapse
Still no luck unfortunately. This is it attempting to boot imgur.com/LIT8i5S (Apologies for the low quality. Using old phone)
samskies1 said:
Still no luck unfortunately. This is it attempting to boot imgur.com/LIT8i5S (Apologies for the low quality. Using old phone)
Click to expand...
Click to collapse
Well I'm stumped, usually the stock images are the thing that revive a One from issues like this. I think it's time to contact the seller and claim warranty.
Transmitted via Bacon
---------- Post added at 07:29 ---------- Previous post was at 07:13 ----------
Edit:
Actually, it's early, I forgot about these, give them a try:
http://forum.xda-developers.com/showthread.php?t=2991851
Unbrick Tool
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
And then try flashing 05Q.
Transmitted via Bacon
timmaaa said:
Well I'm stumped, usually the stock images are the thing that revive a One from issues like this. I think it's time to contact the seller and claim warranty.
Transmitted via Bacon
---------- Post added at 07:29 ---------- Previous post was at 07:13 ----------
Edit:
Actually, it's early, I forgot about these, give them a try:
http://forum.xda-developers.com/showthread.php?t=2991851
Unbrick Tool
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
And then try flashing 05Q.
Transmitted via Bacon
Click to expand...
Click to collapse
Tried the second method you linked. No luck I'm afraid. Attempted the OTA and via fastboot.
samskies1 said:
Tried the second method you linked. No luck I'm afraid. Attempted the OTA and via fastboot.
Click to expand...
Click to collapse
I can't think of why that's happening, you might need to RMA.
Transmitted via Bacon
timmaaa said:
I can't think of why that's happening, you might need to RMA.
Transmitted via Bacon
Click to expand...
Click to collapse
I've sent in a return request.
If you don't mind me asking, did you acquire your phone from OnePlus directly? Or buy through a third party seller?
I only ask because I am also an Australian, and I am unable to purchase from the OnePlus website, due to a lack of shipping to Australia.
samskies1 said:
I've sent in a return request.
If you don't mind me asking, did you acquire your phone from OnePlus directly? Or buy through a third party seller?
I only ask because I am also an Australian, and I am unable to purchase from the OnePlus website, due to a lack of shipping to Australia.
Click to expand...
Click to collapse
I purchased directly from OnePlus, and I know dozens of other Australians who did so. We used freight forwarding companies like Shipito, they provide you with an American mailing address and then forward it on to you. I think it cost me an extra $35 on top of the cost of the phone.
Transmitted via Bacon
timmaaa said:
I purchased directly from OnePlus, and I know dozens of other Australians who did so. We used freight forwarding companies like Shipito, they provide you with an American mailing address and then forward it on to you. I think it cost me an extra $35 on top of the cost of the phone.
Transmitted via Bacon
Click to expand...
Click to collapse
If this return to a third party seller goes though I think I may use that method to buy one directly from OnePlus.
I have similar problem, can't update official firmware through ota or manually installation, but my phone still manage to flash 3rd party roms and Calculkin's rooted 05q rom...??
johnsin5393 said:
I have similar problem, can't update official firmware through ota or manually installation, but my phone still manage to flash 3rd party roms and Calculkin's rooted 05q rom...
Click to expand...
Click to collapse
What happens when you try to flash official firmware?
Yeah I'm going to give Calkulin's rom a try when I get home from work.
samskies1 said:
What happens when you try to flash official firmware?
Yeah I'm going to give Calkulin's rom a try when I get home from work.
Click to expand...
Click to collapse
In cyanogen recovery, I couldn't flash firmware update or others zip file... Only after flashed Calkulin's packed zip, then I could flash to 05q
johnsin5393 said:
In cyanogen recovery, I couldn't flash firmware update or others zip file... Only after flashed Calkulin's packed zip, then I could flash to 05q
Click to expand...
Click to collapse
Would you happen to have a link to what you flashed?
HI.
recently ive want to install ubuntu touch on my opo but i cant. then i want to roll back into the cyanogen os and its stuck on cyanogen boot animation. i just can install oxygen os that i hate it!
please help me to roll back into the cyanogen os 12.1
files i have download
modem :YNG1TAS0YL_Extras.zip
Full-oxygen-04-04-15-Bacon-modem-flashable.zip
XNPH33R_Extras.zip
roms : cm-12.0-YNG1TAS17L-bacon-signed.zip
cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip
oxygenos_1.0.0
i use ubuntu on my pc
my recovery is twrp
dirtylife2011 said:
HI.
recently ive want to install ubuntu touch on my opo but i cant. then i want to roll back into the cyanogen os and its stuck on cyanogen boot animation. i just can install oxygen os that i hate it!
please help me to roll back into the cyanogen os 12.1
files i have download
modem :YNG1TAS0YL_Extras.zip
Full-oxygen-04-04-15-Bacon-modem-flashable.zip
XNPH33R_Extras.zip
roms : cm-12.0-YNG1TAS17L-bacon-signed.zip
cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip
oxygenos_1.0.0
i use ubuntu on my pc
my recovery is twrp
Click to expand...
Click to collapse
Flash the stock images with fastboot. See section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
PS. It's the "cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip" one that you'll use.
Heisenberg said:
Flash the stock images with fastboot. See section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
PS. It's the "cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip" one that you'll use.
Click to expand...
Click to collapse
I use that thread to flash my phone and install both of YNG1TAS2I3 and next ver YOG...-fastboot.ZIP and its stuck on logo . then i flash both version for recovery and its stuck on logi again. Help me
dirtylife2011 said:
I use that thread to flash my phone and install both of YNG1TAS2I3 and next ver YOG...-fastboot.ZIP and its stuck on logo . then i flash both version for recovery and its stuck on logi again. Help me
Click to expand...
Click to collapse
Please try again and copy/paste the text from the command prompt here so I can see.
Heisenberg said:
Please try again and copy/paste the text from the command prompt here so I can see.
Click to expand...
Click to collapse
here you are.
Code:
~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 2.682s]
writing 'modem'...
OKAY [ 0.962s]
finished. total time: 3.644s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash sbl1 sbl1.mbn
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.018s]
finished. total time: 0.031s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash dbi sdi.mbn
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.003s]
writing 'dbi'...
OKAY [ 0.011s]
finished. total time: 0.014s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.020s]
writing 'aboot'...
OKAY [ 0.015s]
finished. total time: 0.035s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash rpm rpm.mbn
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.017s]
finished. total time: 0.026s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash tz tz.mbn
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.015s]
writing 'tz'...
OKAY [ 0.014s]
finished. total time: 0.029s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash LOGO logo.bin
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.015s]
writing 'LOGO'...
OKAY [ 0.028s]
finished. total time: 0.043s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.476s]
writing 'oppostanvbk'...
OKAY [ 0.188s]
finished. total time: 0.665s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (6494 KB)...
OKAY [ 0.301s]
writing 'boot'...
OKAY [ 0.121s]
finished. total time: 0.422s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.107s]
sending 'cache' (10432 KB)...
OKAY [ 0.485s]
writing 'cache'...
OKAY [ 0.217s]
finished. total time: 0.810s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9120 KB)...
OKAY [ 0.425s]
writing 'recovery'...
OKAY [ 0.169s]
finished. total time: 0.594s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.402s]
sending 'system' (1034756 KB)...
OKAY [ 47.980s]
writing 'system'...
OKAY [ 22.148s]
finished. total time: 70.530s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash userdata userdata_64G.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 3.516s]
sending 'userdata' (141075 KB)...
OKAY [ 6.575s]
writing 'userdata'...
OKAY [ 3.205s]
finished. total time: 13.297s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot reboot
rebooting...
dirtylife2011 said:
here you are.
Code:
~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 2.682s]
writing 'modem'...
OKAY [ 0.962s]
finished. total time: 3.644s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash sbl1 sbl1.mbn
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.018s]
finished. total time: 0.031s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash dbi sdi.mbn
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.003s]
writing 'dbi'...
OKAY [ 0.011s]
finished. total time: 0.014s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.020s]
writing 'aboot'...
OKAY [ 0.015s]
finished. total time: 0.035s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash rpm rpm.mbn
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.017s]
finished. total time: 0.026s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash tz tz.mbn
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.015s]
writing 'tz'...
OKAY [ 0.014s]
finished. total time: 0.029s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash LOGO logo.bin
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.015s]
writing 'LOGO'...
OKAY [ 0.028s]
finished. total time: 0.043s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.476s]
writing 'oppostanvbk'...
OKAY [ 0.188s]
finished. total time: 0.665s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (6494 KB)...
OKAY [ 0.301s]
writing 'boot'...
OKAY [ 0.121s]
finished. total time: 0.422s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.107s]
sending 'cache' (10432 KB)...
OKAY [ 0.485s]
writing 'cache'...
OKAY [ 0.217s]
finished. total time: 0.810s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9120 KB)...
OKAY [ 0.425s]
writing 'recovery'...
OKAY [ 0.169s]
finished. total time: 0.594s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.402s]
sending 'system' (1034756 KB)...
OKAY [ 47.980s]
writing 'system'...
OKAY [ 22.148s]
finished. total time: 70.530s
[email protected]alihk-VPCEB3MFX:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot flash userdata userdata_64G.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 3.516s]
sending 'userdata' (141075 KB)...
OKAY [ 6.575s]
writing 'userdata'...
OKAY [ 3.205s]
finished. total time: 13.297s
[email protected]:~/Desktop/cm-12.1-YOG4PAS1N0-bacon-signed-fastboot$ fastboot reboot
rebooting...
Click to expand...
Click to collapse
Hmm, can you boot into recovery?
Heisenberg said:
Hmm, can you boot into recovery?
Click to expand...
Click to collapse
yes .now its boot to cyanogen recovery
dirtylife2011 said:
yes .now its boot to cyanogen recovery
Click to expand...
Click to collapse
Ok, you can flash one of the official zips. You already have this one:
cm-12.0-YNG1TAS17L-bacon-signed.zip
So flash that with the stock recovery.
Heisenberg said:
Ok, you can flash one of the official zips. You already have this one:
cm-12.0-YNG1TAS17L-bacon-signed.zip
So flash that with the stock recovery.
Click to expand...
Click to collapse
only when i install cyanogen it says "patching system unconditionaly...."
is that okay??
and its not work again.
dirtylife2011 said:
only when i install cyanogen it says "patching system unconditionaly...."
is that okay??
and its not work again.
Click to expand...
Click to collapse
Yes that message is normal. Did the flash succeed or fail?
deleted
Heisenberg said:
Yes that message is normal. Did the flash succeed or fail?
Click to expand...
Click to collapse
in cyanogen recovery there is no message that its succeed or failed
but in twrp its succeed.
but all of installation section is already up to date. and its done very fast!
dirtylife2011 said:
in cyanogen recovery there is no message that its succeed or failed
but in twrp its succeed.
but all of installation section is already up to date. and its done very fast!
Click to expand...
Click to collapse
Ok, your persist partition might be corrupt. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/edit?usp=docslist_api
Use fastboot to do the following:
Code:
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
If it still doesn't boot after that, try flashing the stock images again with fastboot. If it still won't boot after that I'm out of ideas and you'll need to start the RMA process with OnePlus.
Heisenberg said:
Ok, your persist partition might be corrupt. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/edit?usp=docslist_api
Use fastboot to do the following:
Code:
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
If it still doesn't boot after that, try flashing the stock images again with fastboot. If it still won't boot after that I'm out of ideas and you'll need to start the RMA process with OnePlus.
Click to expand...
Click to collapse
thank you for step by step help....
and sorry for my bad English language
Heisenberg said:
Ok, your persist partition might be corrupt. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/edit?usp=docslist_api
Use fastboot to do the following:
Code:
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
If it still doesn't boot after that, try flashing the stock images again with fastboot. If it still won't boot after that I'm out of ideas and you'll need to start the RMA process with OnePlus.
Click to expand...
Click to collapse
Its Worked!!!
Thanks!!!
Its The final Way
In my country We call adept final impact
dirtylife2011 said:
Its Worked!!!
Thanks!!!
Its The final Way
In my country We call adept final impact
Click to expand...
Click to collapse
Oh hell yeah!! Awesome news
Thank you so much for this guide to fixing a corrupt persist.img. I just learned how to use cmd.exe and fastboot to flash this to my phone that was messed up. This guide saved my phone!!
Hi there!
Before I flashed these I had 5.1.1 Retail UK stock, rooted, xposed installed with gravitybox, disabled the softkeys with the build.prop command & turned the volume up with rx_mixerpaths
I downloaded XT1541_OSPREY_RETGB_5.1.1_LPI23.72-47_cid7_subsidy-DEFAULT_CFC.xml.zip from this thread & used this guide http://forum.xda-developers.com/2015...ctory-t3187750 to flash the phone to complete stock before I pass it down the family.
Upon booting it won't turn on the WiFi, I try to turn it on & it flicks off straight away. I had a quick search & came across this thread http://forum.xda-developers.com/moto...tooth-t2813308 I have checked the /persist folder & its empty unlike those guys in that thread.
I was wondering if someone could be generous enough to share these files with me? Unless there is another way to get the WiFi working again?
Many many thanks!
Below is a copy of the fastboot commands.
C:\adb>fastboot devices
ZY2223RTMH fastboot
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing '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...
OKAY [ 0.713s]
finished. total time: 0.720s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.085s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.596s]
finished. total time: 1.683s
C:\adb>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (917 KB)...
OKAY [ 0.033s]
writing 'logo'...
OKAY [ 0.074s]
finished. total time: 0.108s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.524s]
writing 'recovery'...
OKAY [ 0.446s]
finished. total time: 0.971s
C:\adb>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (262140 KB)...
OKAY [ 8.236s]
writing 'system'...
OKAY [ 6.949s]
finished. total time: 15.187s
C:\adb>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (262143 KB)...
OKAY [ 8.223s]
writing 'system'...
OKAY [ 6.777s]
finished. total time: 15.003s
C:\adb>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (232608 KB)...
OKAY [ 7.297s]
writing 'system'...
OKAY [ 6.221s]
finished. total time: 13.519s
C:\adb>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (233343 KB)...
OKAY [ 7.332s]
writing 'system'...
OKAY [ 6.012s]
finished. total time: 13.348s
C:\adb>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (257130 KB)...
OKAY [ 8.067s]
writing 'system'...
OKAY [ 6.554s]
finished. total time: 14.623s
C:\adb>fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (228585 KB)...
OKAY [ 7.171s]
writing 'system'...
OKAY [ 5.850s]
finished. total time: 13.024s
C:\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36940 KB)...
OKAY [ 1.165s]
writing 'modem'...
OKAY [ 1.006s]
finished. total time: 2.172s
C:\adb>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\adb>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.014s]
finished. total time: 0.015s
C:\adb>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (2031 KB)...
OKAY [ 0.068s]
writing 'fsg'...
OKAY [ 0.081s]
finished. total time: 0.151s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.019s
C:\adb>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.795s]
finished. total time: 0.796s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.007s
I had the exact same problem when trying to flash the generic Canadian firmware. I flashed three times to no avail. Then I downloaded and flashed a carrier-specific version of the Canadian firmware and suddenly wifi worked.
Sevael said:
I had the exact same problem when trying to flash the generic Canadian firmware. I flashed three times to no avail. Then I downloaded and flashed a carrier-specific version of the Canadian firmware and suddenly wifi worked.
Click to expand...
Click to collapse
Any chance you'd be able to share your files in /persist folder if you are rooted?
I think this will sort it. The phone was a simfree one I don't really want to flash carrier-specific software if possible.
Powereh said:
I think this will sort it. The phone was a simfree one I don't really want to flash carrier-specific software if possible.
Click to expand...
Click to collapse
The carrier-specific one won't lock your phone or put any bloatware on it. It's simply one that was taken from a phone that somebody bought from that carrier. The one I used was from a different carrier than the one I bought the phone from originally.
Powereh said:
Any chance you'd be able to share your files in /persist folder if you are rooted?
Click to expand...
Click to collapse
I can't from where I am right now. Hopefully you can find someone who can upload it, otherwise I recommend giving a different firmware download a try.
Here ya go, keep in mind this is from XT1540 Canadian retail.
https://drive.google.com/file/d/0B4Gyz91x5k7gdUoxQUtldEZ3Wmc/view?usp=docslist_api
Sent from my MotoG3 using XDA Free mobile app
Cheers for the help guys, I will try those files out once i get home from work later.
I'll let you know the outcome in due course.
christopherrrg said:
Here ya go, keep in mind this is from XT1540 Canadian retail.
https://drive.google.com/file/d/0B4Gyz91x5k7gdUoxQUtldEZ3Wmc/view?usp=docslist_api
Sent from my MotoG3 using XDA Free mobile app
Click to expand...
Click to collapse
OK tried your files & it just keeps force closing every thing upon boot an endless amount.
I think I need XT1541 specific files.
Thank you so much for taking the time to upload those though! I really appreciate it.
Fixed it I had to flash this one instead Retail Great Britain (1GB) - XT1541_OSPREY_RETGB_5.1.1_LPI23.72-22_cid7
Cheers for the guys who tried to help
Powereh said:
Fixed it I had to flash this one instead Retail Great Britain (1GB) - XT1541_OSPREY_RETGB_5.1.1_LPI23.72-22_cid7
Cheers for the guys who tried to help
Click to expand...
Click to collapse
Glad you're back up! Change thread to solved in case passer bys need the information.
Sent from my MotoG3 using XDA Free mobile app
christopherrrg said:
Glad you're back up! Change thread to solved in case passer bys need the information.
Sent from my MotoG3 using XDA Free mobile app
Click to expand...
Click to collapse
I don't think the issue is solved, he just returned to the previous factory image, I'm having the same issue with the US model. I posted in the factory image thread on general and I'm not the only one
at least for some people if you try to upgrade via fastboot, wifi is broken
sgloki77 said:
I don't think the issue is solved, he just returned to the previous factory image, I'm having the same issue with the US model. I posted in the factory image thread on general and I'm not the only one
at least for some people if you try to upgrade via fastboot, wifi is broken
Click to expand...
Click to collapse
Agreed - I have this problem as well. I've searched through the threads, but haven't found a solution yet.
cdluck said:
Agreed - I have this problem as well. I've searched through the threads, but haven't found a solution yet.
Click to expand...
Click to collapse
you need to flash back to the original factory image and then take the OTA , do NOT try to upgrade directly with the latest factory image, or you will find yourself in brick city
Sent from my Nexus 6 using Tapatalk
sgloki77 said:
you need to flash back to the original factory image and then take the OTA , do NOT try to upgrade directly with the latest factory image, or you will find yourself in brick city
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I'll try that, thanks - is flashing back to the original factory image the same process, just with a different zip (e.g. XT1540_OSPREY_RETUS_2GB_5.1.1_LPI23.72-44_cid9_subsidy-DEFAULT_CFC)?
Also, this wifi thing is weird - I was able to connect to my home wifi without issue, but my work wifi causes the shutdown problem (if I try to fiddle with it and get it to connect, it just crashes and reboots the phone).
cdluck said:
I'll try that, thanks - is flashing back to the original factory image the same process, just with a different zip (e.g. XT1540_OSPREY_RETUS_2GB_5.1.1_LPI23.72-44_cid9_subsidy-DEFAULT_CFC)?
Also, this wifi thing is weird - I was able to connect to my home wifi without issue, but my work wifi causes the shutdown problem (if I try to fiddle with it and get it to connect, it just crashes and reboots the phone).
Click to expand...
Click to collapse
no man [emoji33] that one you quoted is the bad apple, when I said "original" I meant the one your phone shipped with(16.3)
Sent from my Nexus 6 using Tapatalk
sgloki77 said:
no man [emoji33] that one you quoted is the bad apple, when I said "original" I meant the one your phone shipped with(16.3)
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
My mistake, I copied the name from the wrong file - thanks for catching that for me!
sgloki77 said:
you need to flash back to the original factory image and then take the OTA , do NOT try to upgrade directly with the latest factory image, or you will find yourself in brick city
Click to expand...
Click to collapse
:crying: really!?, I was thinking about update directly with latest firmware to avoid OTA
El_Nuevo said:
:crying: really!?, I was thinking about update directly with latest firmware to avoid OTA
Click to expand...
Click to collapse
by my experience
-flashing 16.3 image was ok,
-flashing 44 image (I only flashed system and radio) resulted in broken wifi
by other users' experiences I read
-flashing 44 image(all partitions) resulted in a brick
-flashing 47 image was ok at least by one user
my device is XT1540 US 1GB RAM at this point I would suggest you research your particular model/factory images compatible with your model and decide for yourself what factory image to flash, there's been a few bricks already so beware of dragons...
Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide
IMPORTANT NOTICE:
Because there are reports of devices becoming bricked due to downgrading, please disregard this thread and firmware. This is a link to the newly added factory firmware package for the most current build version for the xt1766 SPerry. Please go here:
https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
DISCLAIMER: Please take note that the following stock firmware package is not the official Motorola firmware package, nor is it signed by Motorola. This is a package I have compiled with partition dumps from a pure stock & unmodified Android OS. I have tested this procedure, as have other members, and no adverse issues have arisen upon installing the firmware. However, I am not responsible for devices bricked or otherwise rendered inoperable as a result of installing this firmware or using this guide. You and you alone are responsible for your device. Because this guide does involve fastboot flashing bootloader and other sensitive partitions, follow the instructions to the letter. One mishap while flashing a bootloader partition can leave a device fully inoperable. Also, I have only used this guide on Virgin Mobile variants of the xt1766. It should work on the Sprint and Boost Mobile variants as well, but I cannot personally confirm that at this time.
SPECIFICATIONS:
Hardware SKU: xt1766
Carrier/Provider: Sprint, Virgin Mobile, Boost Mobile
Android Version: 7.1.1 Nougat
Build No. NCQ26.69-64
Radio: M8920_15000.280.06.58.02R
Kernel Version: 3.18.31
Security Patch Level: January 1, 2018
NOTES: This firmware is the most recent version of the stock Android OS. It is completely unmodified.
REQUIREMENTS:
--An unlocked bootloader;
--A PC or laptop running Windows 7 or later;
--Motorola Device Manager: https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222;
--Minimal ADB & Fastboot (v1.4.3 or later): https://drive.google.com/file/d/0B1Sfod4HWfk2T0hia0k3Y3pIczA/view?usp=drivesdk;;
--Rudimentary knowledge of fastboot flashing;
--Device charged to at least 60%.
INSTRUCTIONS:
Download the stock firmware package from the link below and save the files in your ADB/Fastboot directory on your PC. Boot your device into fastboot/bootloader mode and connect your device and PC with a suitable data sync cable. Open a command window within the ADB/Fastboot directory and execute the following set of commands:
NOTE: The larger image files (system.img & oem.img) will be automatically dissected into individual sparsechunks and incrementally flashed by fastboot. You will initially receive a "header size" error, but just be patient and wait. Fastboot will resolve this and flash the images.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash aboot aboot.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash dsp dsp.img
fastboot flash modem modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.img
fastboot flash keymaster keymaster.mbn
fastboot flash oem oem.img
fastboot flash prov prov.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot erase system
fastboot flash system system.img
fastboot erase DDR
fastboot erase userdata
fastboot erase cache
fastboot oem fb_mode_clear
Now boot your device normally. You should now be updated to the most recent pure stock Android build, and your device will be fully capable of installing future OTA updates.
DOWNLOAD LINK:
LINK HAS BEEN REMOVED: Please go here: https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
this is useful. :good:
but please it would be more good if you move this to the Qualcomm section, because seems you posted it in the MediaTek section.
Please do move it so other users don't come wondering what to do and bricking their devices.
iykeDROID™ said:
this is useful. :good:
but please it would be more good if you move this to the Qualcomm section, because seems you posted it in the MediaTek section.
Please do move it so other users don't come wondering what to do and bricking their devices.
Click to expand...
Click to collapse
Yes I see your point. My bad. How can I move this over? Do I need to contact a moderator to get it moved? Thanks much for pointing that out. :good:
MotoJunkie01 said:
Yes I see your point. My bad. How can I move this over? Do I need to contact a moderator to get it moved? Thanks much for pointing that out. :good:
Click to expand...
Click to collapse
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411
iykeDROID™ said:
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411
Click to expand...
Click to collapse
Thank you. I sent the thread link and a PM to Az Biker.
Update: The Sperry xt1766 received an OTA update today for minor bug fixes, stability improvements, and security patches for March 1, 2018. The OTA is Bkur_Version 26.11.68.sperry_sprint.en.US. I will be updating this thread to the new build updated by the OTA. In the meantime, should you wish to revert to pure stock and install the OTA update package, the above fastboot firmware package will put your xt1766 in a pure stock state, and thus capable of installing the OTA update. NOTE: Many people skip recovery.img in order to retain TWRP custom recovery. Here, flashing stock recovery is necessary in order to successfully install the OTA update package.
iykeDROID™ said:
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411
Click to expand...
Click to collapse
Hey friend, thanks again for pointing out my oversight. Moderator Az Biker helped me out and moved the thread.
Ok guys, on a positive note, I just successfully flashed a modified OTA update package with TWRP. I think I figured out the bug that was giving me Error 7 previously. So I am working on both recent OTA packages, for patch level January 1, 2018 and March 1, 2018. Hopefully now I can get these fixed and posted and make for a simple means to update stock firmware, without having to gruel out 25 fastboot commands and without having to download large files. Wish me luck. I thank you all for your support and encouragement.
MotoJunkie01 said:
Ok guys, on a positive note, I just successfully flashed a modified OTA update package with TWRP. I think I figured out the bug that was giving me Error 7 previously. So I am working on both recent OTA packages, for patch level January 1, 2018 and March 1, 2018. Hopefully now I can get these fixed and posted and make for a simple means to update stock firmware, without having to gruel out 25 fastboot commands and without having to download large files. Wish me luck. I thank you all for your support and encouragement.
Click to expand...
Click to collapse
Rock on bro! Good luck.
Hard brick
My device is bricked flashing update on custom rom AICP
Please help
---------- Post added at 08:42 AM ---------- Previous post was at 08:40 AM ----------
Hard brick
My device is bricked flashing update on custom rom AICP
Please help
Restore in emergency mode
Greetings.
I would like your help to restore a MOTO E4 XT1766. It does not start with fastboot, because the bootloader is corrupt. The phone connects in emergency mode. I need the file "prog_emmc_firehose_8920.mbn" to be able to restore it. Any idea where I can find it?
error cannot load gpt.bin
I have my phone in fastboot/bootloader mode. Should I be in recovery? I can run the command "fastboot oem fb_mode_set" but I cant run the command "fastboot flash partition gpt.bin" I get "error cannot load gpt.bin". Moto E4 XT1766 Qualcomm any help?
Edit: I am sure I have the files in the same folder as adb and fastboot.
UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry bricked my phone
Hey,
I flashed my phone using the zip from the "UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry" thread and bricked my phone.
Won't even power on and is not recognized by adb/fastboot. "waiting for device"
Is there anyway of unbricking it.
Tried holding the down+power button for 10 seconds
Tried holding the up+power button for 10 seconds.
Charging it for 10 minutes and holding the power button for 10 seconds.
Removed battery and reinserted holding for 10 seconds and plug it in my laptop.
Nothing.
Please help if you can, is there another trick I can do.
[email protected] said:
Hey,
I flashed my phone using the zip from the "UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry" thread and bricked my phone.
Won't even power on and is not recognized by adb/fastboot. "waiting for device"
Is there anyway of unbricking it.
Tried holding the down+power button for 10 seconds
Tried holding the up+power button for 10 seconds.
Charging it for 10 minutes and holding the power button for 10 seconds.
Removed battery and reinserted holding for 10 seconds and plug it in my laptop.
Nothing.
Please help if you can, is there another trick I can do.
Click to expand...
Click to collapse
Nope its dead u flash bootloader partitions that were older then your current version that edl'd you're phone
MotoJunkie01 said:
Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide
Click to expand...
Click to collapse
Thanks man, worked perfectly.
Got some errors along the way, which I ignored (permissions on Erase Data, etc).
MotoJunkie01 said:
Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide
Click to expand...
Click to collapse
After successfully using this method, a few days later I was prompted to install May Security Update NCQS26.69-64-5.
I said ok, it downloaded and prompted me to restart. I did.
I rebooted into the initial boot screen, with "bad key" text.
Then it proceeded to "Installing system update"
Then came the Android on his back, with the error! (red exclamation)
Had to power off/on. It restarted and then showed the screen "Software Update Unsuccessful"
Any idea on how I could successfully install the may update?
Thanks!
mike
resarfekim said:
After successfully using this method, a few days later I was prompted to install May Security Update NCQS26.69-64-5.
I said ok, it downloaded and prompted me to restart. I did.
I rebooted into the initial boot screen, with "bad key" text.
Then it proceeded to "Installing system update"
Then came the Android on his back, with the error! (red exclamation)
Had to power off/on. It restarted and then showed the screen "Software Update Unsuccessful"
Any idea on how I could successfully install the may update?
Thanks!
mike
Click to expand...
Click to collapse
The bad key is just because the bootloader is unlocked. No big deal. Not sure why the ota failed. I just flash the firmware with rsdlite. Just downloaded the latest firmware available, which was not May's patch, then took the update after I booted up and set up the device. What carrier are you on? Mine is virgin mobile, same as op.
Check in "about phone" and see which software version you're on. My wife's failed once, but when I checked, it had updated.
madbat99 said:
The bad key is just because the bootloader is unlocked. No big deal. Not sure why the ota failed. I just flash the firmware with rsdlite. Just downloaded the latest firmware available, which was not May's patch, then took the update after I booted up and set up the device. What carrier are you on? Mine is virgin mobile, same as op.
Check in "about phone" and see which software version you're on. My wife's failed once, but when I checked, it had updated.
Click to expand...
Click to collapse
Thanks for the reply.
I am currently on the March 1 Security Patch, NCQS26.69-64-2
On Sprint network.
I can't figure out how to create a screenshot with this phone, but here is the link from the Update popup: https://support.motorola.com/us/en/solution/MS128968
resarfekim said:
Thanks for the reply.
I am currently on the March 1 Security Patch, NCQS26.69-64-2
On Sprint network.
I can't figure out how to create a screenshot with this phone, but here is the link from the Update popup: https://support.motorola.com/us/en/solution/MS128968
Click to expand...
Click to collapse
Screenshot is just like any vanilla Android device. Power + volume down.
Did you root or modify the system in any way? That will cause an ota to fail.
madbat99 said:
Screenshot is just like any vanilla Android device. Power + volume down.
Did you root or modify the system in any way? That will cause an ota to fail.
Click to expand...
Click to collapse
I was originally rooted, but after running the commands in this OP, I did nothing else.
I did save the results of all the Fastboot commands, please see below. A couple commands toward the end gave errors.
______________________________________________
E:\Phone\E4\Factory_restore_image>fastboot devices
ZY224PTXGW fastboot
E:\Phone\E4\Factory_restore_image> fastboot oem fb_mode_set
...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.125s]
finished. total time: 0.140s
E:\Phone\E4\Factory_restore_image>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.515s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.655s]
finished. total time: 1.186s
E:\Phone\E4\Factory_restore_image> fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 1.970s]
finished. total time: 2.517s
E:\Phone\E4\Factory_restore_image> fastboot flash aboot aboot.mbn
(bootloader) has-slot:aboot: not found
target reported max download size of 536870912 bytes
sending 'aboot' (1536 KB)...
OKAY [ 0.047s]
writing 'aboot'...
OKAY [ 0.203s]
finished. total time: 0.265s
E:\Phone\E4\Factory_restore_image>fastboot flash cmnlib cmnlib.mbn
(bootloader) has-slot:cmnlib: not found
target reported max download size of 536870912 bytes
sending 'cmnlib' (251 KB)...
OKAY [ 0.001s]
writing 'cmnlib'...
OKAY [ 0.078s]
finished. total time: 0.079s
E:\Phone\E4\Factory_restore_image>fastboot flash cmnlib64 cmnlib64.mbn
(bootloader) has-slot:cmnlib64: not found
target reported max download size of 536870912 bytes
sending 'cmnlib64' (251 KB)...
OKAY [ 0.016s]
writing 'cmnlib64'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash devcfg devcfg.mbn
(bootloader) has-slot:devcfg: not found
target reported max download size of 536870912 bytes
sending 'devcfg' (128 KB)...
OKAY [ 0.016s]
writing 'devcfg'...
OKAY [ 0.062s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image> fastboot flash dsp dsp.img
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.531s]
writing 'dsp'...
OKAY [ 1.686s]
finished. total time: 2.217s
E:\Phone\E4\Factory_restore_image>fastboot flash modem modem.img
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (102400 KB)...
OKAY [ 3.247s]
writing 'modem'...
OKAY [ 4.921s]
finished. total time: 8.168s
E:\Phone\E4\Factory_restore_image>fastboot erase modemst1
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.062s]
finished. total time: 0.062s
E:\Phone\E4\Factory_restore_image>fastboot erase modemst2
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.062s]
finished. total time: 0.062s
E:\Phone\E4\Factory_restore_image> fastboot flash fsg fsg.img
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (8192 KB)...
OKAY [ 0.266s]
writing 'fsg'...
OKAY [ 2.795s]
finished. total time: 3.062s
E:\Phone\E4\Factory_restore_image>fastboot flash keymaster keymaster.mbn
(bootloader) has-slot:keymaster: not found
target reported max download size of 536870912 bytes
sending 'keymaster' (251 KB)...
OKAY [ 0.016s]
writing 'keymaster'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash oem oem.img
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'oem' 1/2 (507490 KB)...
OKAY [ 17.457s]
writing 'oem' 1/2...
OKAY [ 28.001s]
sending sparse 'oem' 2/2 (59511 KB)...
OKAY [ 2.081s]
writing 'oem' 2/2...
OKAY [ 6.231s]
finished. total time: 53.804s
E:\Phone\E4\Factory_restore_image> fastboot flash prov prov.mbn
(bootloader) has-slotrov: not found
target reported max download size of 536870912 bytes
sending 'prov' (187 KB)...
OKAY [ 0.016s]
writing 'prov'...
OKAY [ 0.062s]
finished. total time: 0.078s
E:\Phone\E4\Factory_restore_image>fastboot flash rpm rpm.mbn
(bootloader) has-slot:rpm: not found
target reported max download size of 536870912 bytes
sending 'rpm' (256 KB)...
OKAY [ 0.016s]
writing 'rpm'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash sbl1 sbl1.mbn
(bootloader) has-slot:sbl1: not found
target reported max download size of 536870912 bytes
sending 'sbl1' (507 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
OKAY [ 0.047s]
finished. total time: 0.078s
E:\Phone\E4\Factory_restore_image> fastboot flash tz tz.mbn
(bootloader) has-slot:tz: not found
target reported max download size of 536870912 bytes
sending 'tz' (1792 KB)...
OKAY [ 0.062s]
writing 'tz'...
OKAY [ 0.265s]
finished. total time: 0.328s
E:\Phone\E4\Factory_restore_image>fastboot erase system
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot erase system
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image> fastboot flash system system.img
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/5 (509553 KB)...
OKAY [ 17.319s]
writing 'system' 1/5...
OKAY [ 12.350s]
sending sparse 'system' 2/5 (523636 KB)...
OKAY [ 17.753s]
writing 'system' 2/5...
OKAY [ 11.928s]
sending sparse 'system' 3/5 (519086 KB)...
OKAY [ 17.869s]
writing 'system' 3/5...
OKAY [ 11.983s]
sending sparse 'system' 4/5 (521399 KB)...
OKAY [ 17.949s]
writing 'system' 4/5...
OKAY [ 20.356s]
sending sparse 'system' 5/5 (411602 KB)...
OKAY [ 14.302s]
writing 'system' 5/5...
OKAY [ 35.077s]
finished. total time: 176.895s
E:\Phone\E4\Factory_restore_image> fastboot erase DDR
(bootloader) has-slotDR: not found
erasing 'DDR'...
OKAY [ 0.000s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 1.267s]
finished. total time: 1.267s
E:\Phone\E4\Factory_restore_image>fastboot erase cache
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
E:\Phone\E4\Factory_restore_image> fastboot oem fb_mode_clear
...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>