hi guys
my problem is that i can't get any custom kernel to boot on my phone...i tried almost all doomkernels v9 (and v8 also) and darkforest too but no luck....tried on booth stock roms .58 and .62!!!
the only kernel my phone booted with is freexperia project from CM7.2 (2.6.32.9-FXP [email protected]#1) but my wifi isn't working with this kernel
note: i always keep getting this error saying "1 bad blocks encountered" as you can see in this log:
----------------------------
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 1 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.004s]
finished. total time: 1.547s
-----------------------------
after flashing any kernel the only way to get my phone working again is with flashtool>>flashmode>>FW.tft>>>i check only exclude system and exclude baseband and let all others unchecked!
when i flash even a stock kernel with fastboot my phone don't boot up!!!!
help me please!
1 bad block encountered = custom kernel can't fit because it needs all the blocks = the custom kernel won't work.
Sorry, mate.
Logseman said:
1 bad block encountered = custom kernel can't fit because it needs all the blocks = the custom kernel won't work.
Sorry, mate.
Click to expand...
Click to collapse
thanks man for clearing that up!
guess i'm stuck with stock kernels!
just wondering....isn't there anything i can do to fix the bad block???
abdourealcf said:
just wondering....isn't there anything i can do to fix the bad block???
Click to expand...
Click to collapse
Aside from getting a new phone? I don't believe so, but please correct me if I'm wrong
jacklebott said:
Aside from getting a new phone? I don't believe so, but please correct me if I'm wrong
Click to expand...
Click to collapse
i found some people saying that it may be a bootloader problem (corrupted bootloader or something like that!!!)
http://forum.xda-developers.com/showthread.php?t=1314677
i'm new to all this stuff!!!
I am unlocked
fast boot still works
ok I downloaded the OTA
went to root it and everthign went to hell
the recovery dlahed but would nto entere recoivery
tried a couple differnt twrp
tried cwm
tried other 5.1 recovereis after verifying that they had the same sizes
still wont entere recovery
treid to use the kk factoryu image and "most of it flashed
Code:
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.249s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.114s
C:\Users\Zookeeper\Desktop\android_sdk\XT1060 Moto X\VZW_212.56.26.ghost_verizon.Verizon.en.US>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.383s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.137s
flashed a different boot image and moto boot image form 5.1 t mobile
still no joy
there is a brazil 1053 which I am told Mosley works. but I cant find it
no 1060 factory image yet.
so has anybody created a factory type image yet. NOT a flashable zip. unless I can get twrp working that wont help me.
FAST BOOT WORKS
I'm not 100% sure, but you may have to use "mfastboot" which is the motorola version of fastboot. You can find it with a quick search.
So you were on 5.1 and downgraded to Kit Kat? You can't downgrade the bootloader.
dcooterfrog said:
I am unlocked
fast boot still works
ok I downloaded the OTA
went to root it and everthign went to hell
the recovery dlahed but would nto entere recoivery
tried a couple differnt twrp
tried cwm
tried other 5.1 recovereis after verifying that they had the same sizes
still wont entere recovery
Click to expand...
Click to collapse
I'm going to stop you right there,.
To install an OTA, you need STOCK reocvery. If you have a 3rd party recovery like TWRP or CWM, the OTA process might reboot your phone into Recovery but it will fall to install.
If you have 4.4.4 on your phone, you need to get that exact Recovery.img and flash it. You can't use a 5.1 recovery because the pre-flash validation checks that happen as part of the OTA will likely complain that its not the right version.
dcooterfrog said:
treid to use the kk factoryu image and "most of it flashed
Code:
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.249s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.114s
C:\Users\Zookeeper\Desktop\android_sdk\XT1060 Moto X\VZW_212.56.26.ghost_verizon.Verizon.en.US>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.383s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.137s
flashed a different boot image and moto boot image form 5.1 t mobile
still no joy
there is a brazil 1053 which I am told Mosley works. but I cant find it
no 1060 factory image yet.
so has anybody created a factory type image yet. NOT a flashable zip. unless I can get twrp working that wont help me.
FAST BOOT WORKS
Click to expand...
Click to collapse
You can't downgrade from 4.4.4 to 4.4.2 without risking turning your phone into a brick.
What state is your phone in now? WHat bootloader version does it have on it?
If you have bootloader 30.B7, consider downloading the 4.4.4 XT1060 SBF/FXZ moto has on their web site, and visit -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 read post 1 and 2... From Post 2, use the Requirements section, then skip to option 5 to get to stock 4.4.4. then try the OTA
ok lest start over
i was rooted with twrp
i returned to stock and flashed system and recovery from
VZW_212.56.26.ghost_verizon.Verizon.en.US
took both OTAs got onto lolipop seemd to be working
went to flash twrp it said flashed OK
but I could not boot into recovery
tried to laod a cuple differnt recoveries.
then tried to restore the whoel thing
VZW_212.56.26.ghost_verizon.Verizon.en.US
gpt failed
recovery failed
then I tried to install a recovery boot and moto boot frfom a different 5.1. ( after verifying that a couple 5.1 roms had the same size moto boot and boot) flashed but gpt is messed up and wont restore.
either I have broke it or I need a factory image from lollipop
i will try to check my boot loader version. but i bet its updated as a resultof th OTA
got twrp working
does any one have a complete nanadroid of verizon lolipop
got twrp working
does any one have a complete nanadroid of verizon lolipop
slowly am getting back up.
i am not at VZW_212.55.26.ghost_verizon.Verizon.en.US
not 56
Blur_Version.212.166.3.ghost_verizon.Verizon.en.US seems to fail.
ill try flashing system and recovery again.
flashd system, revcovery, boot and motoboot
moto boot failed
update unsuccessful so somthing in moto boot muts ba failing the assert. I think I have a NEWER moto boot.
How did you get TWRP working under 5.1? Someone else had similar issues here:
http://forum.xda-developers.com/moto-x/moto-x-qa/xt1060-recovery-5-1-t3201391
Well that was me... Eventually I got twrp working but I don't know what kind of bastard kitkat lolipop Frankenstein thing it was. Phone will not boot. It is on its way back to motorolla
Sent from my Venue 8 7840 using Tapatalk
Hey bud, when you say the phone won't boot do you mean you can't even boot into the bootloader, or do you mean the screen goes black after the boot animation?
If it's the latter the same thing happened to me today and I know how to fix it.
Won't boot. It went back to Motorola yesterday. Love extended warranty. Backup phone droid incredible 1 with KitKat . loving the 3g
Sent from my ADR6300 using Tapatalk
dcooterfrog said:
Won't boot.
Click to expand...
Click to collapse
I was asking you to clarify what you meant by "won't boot" since that could mean multiple things, but it doesn't matter if you already sent the phone back. Glad you have the extended warranty.
yes extended warranty is great.
sorry by wont boot i meant complete brick, not boot loop. no boo tlogo, no motorolla logo, no bootloader unlocked warning screen. just dark dead, as a doornail.
it wold not even get int eh boot loader.
i have never bricked a phone before. i want trying to downgrade. i have been rooting ( the hard way) since eclair on my lg ally, so not a newb.
I decided to return my Sprint variant. So i needed to s-on and lock the bootloader. Problem is, now I have a 1 sec bootloop. Here's what I did. No idea how to fix the problem now.
Here's what I did in order to get the phone back to 100% stock to return it.
Changed the CID (incorrectly) to spsc_001 instead of spcs_001 but iddn't notice that.
Managed to get s-on but couldn’t get bootloader locked again.
reinstalled twrp and SU
booted up
installed sunshine and successfully s-off'd & locked
rebooted to download mode
Did a s-on using fastboot oem writesecureflag 3
rebooted and got a 1 sec bootloop
booted back into download mode and tried to factory reset via fastboot but can’t write the partition
tried to flash twrp, but got a security warning BL-unlocked
Now I'm stuck in a super short .5 second bootloop and can’t access stock recovery.
I try to install the ruu.exe and I get a Customer ID error. I try to install RUU.zip and I get a load_file: could not allocate -2146013644 bytes (which I assume means the partition is full but I can't even erase the userdata.) I also get a Security checking failed GT_CONNECT_FAIL on the download mode screen. I'm totally clueless as to how to get out of this situation. Anyone been here before or knows how to deal with this?
u failed to mention that you changed the CID at some point & when you changed it back, u set it wrong...
honestly, I think you're screwed...I don't know how you'll be able to fix this w/o being able to boot up, can't unlock bootloader, can't use fastboot to flash anything, can't flash RUU...somehow u need to get your CID back to SPCS_001...u may just have to return it in that condition & act ignorant.
any ideas @dottat @Captain_Throwback
vijn said:
Now, my vars are:
(bootloader) kernel: lk
(bootloader) product: htc_pmewhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: HT64xxxxx6
(bootloader) current-slot:
(bootloader) imei: 99xxxxx1
(bootloader) version-main: 2.42.651.63
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS640000
(bootloader) cid: spsc_001
all:
finished. total time: 0.009s
Click to expand...
Click to collapse
OMJ said:
u failed to mention that you changed the CID at some point & when you changed it back, u set it wrong...
Click to expand...
Click to collapse
You're right, but I had created this post before you guys pointed that out to me in the other thread. So, ya for the record i set the CID as spsc_001 instead of spcs_001 and then locked the bootloader. Great job on my part huh? Anyway, I was afraid you were going to say that I was screwed. I have never made a mistake like this before. So stupid, every letter counts. You'd think I'd have learnt that by now. I'm just hoping there's some really obscure and little-known fix for this that some xda angel will send my way. Hehe. Anyway, thanks for the follow-up OMJ.
vijn said:
You're right, but I had created this post before you guys pointed that out to me in the other thread. So, ya for the record i set the CID as spsc_001 instead of spcs_001 and then locked the bootloader. Great job on my part huh? Anyway, I was afraid you were going to say that I was screwed. I have never made a mistake like this before. So stupid, every letter counts. You'd think I'd have learnt that by now. I'm just hoping there's some really obscure and little-known fix for this that some xda angel will send my way. Hehe. Anyway, thanks for the follow-up OMJ.
Click to expand...
Click to collapse
Well did you attempt to see if HTC dev would give you an unlock token at least?
Sent from my SM-G955U using Tapatalk
---------- Post added at 11:29 PM ---------- Previous post was at 11:28 PM ----------
dottat said:
Well did you attempt to see if HTC dev would give you an unlock token at least?
You might be able manually flash the ruu partitions one by one as well. Have you tried that?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Sent from my SM-G955U using Tapatalk
dottat said:
Well did you attempt to see if HTC dev would give you an unlock token at least?
Click to expand...
Click to collapse
Well, I had already unlocked the phone, rooted, installed other ROMs. When I couldn't unlock the GSM bands, I decided to return the phone so I tried to set the phone back to stock Sprint ROM. I did everything necessary except I put in the wrong CID before relocking the bootloader. So, yes, I had been provided the unlock code by HTC dev. The problem is that I now have a locked bootloader with an incorrect CID, which is why flashing RUUs isn't working.
I don't know if I can flash the RUU partitions with a locked bootloader or if that'll work with an incorrect CID but I'll try anything. Just not sure how to go about doing tht. I'd appreciate any help you can provide. Thanks for the recommendation.
vijn said:
Well, I had already unlocked the phone, rooted, installed other ROMs. When I couldn't unlock the GSM bands, I decided to return the phone so I tried to set the phone back to stock Sprint ROM. I did everything necessary except I put in the wrong CID before relocking the bootloader. So, yes, I had been provided the unlock code by HTC dev. The problem is that I now have a locked bootloader with an incorrect CID, which is why flashing RUUs isn't working.
I don't know if I can flash the RUU partitions with a locked bootloader or if that'll work with an incorrect CID but I'll try anything. Just not sure how to go about doing tht. I'd appreciate any help you can provide. Thanks for the recommendation.
Click to expand...
Click to collapse
Attempt to get a new fresh unlock token and tell me what HTC dev says?
Sent from my SM-G955U using Tapatalk
vijn said:
Well, I had already unlocked the phone, rooted, installed other ROMs. When I couldn't unlock the GSM bands, I decided to return the phone so I tried to set the phone back to stock Sprint ROM. I did everything necessary except I put in the wrong CID before relocking the bootloader. So, yes, I had been provided the unlock code by HTC dev. The problem is that I now have a locked bootloader with an incorrect CID, which is why flashing RUUs isn't working.
I don't know if I can flash the RUU partitions with a locked bootloader or if that'll work with an incorrect CID but I'll try anything. Just not sure how to go about doing tht. I'd appreciate any help you can provide. Thanks for the recommendation.
Click to expand...
Click to collapse
try this, grab the stock boot.img from the firmware zip: https://www.androidfilehost.com/?fid=745425885120723715
copy the boot.img into your sdktools folder
boot into download mode & try to manually flash it
fastboot flash boot boot.img
if that doesn't work, then try this
download the signed firmware: https://www.androidfilehost.com/?fid=745425885120723717
then try one or both of the flashing methods (although I suspect it wont work due to bad CID):
Flash Firmware via download mode (requires micro sd card)....
-rename firmware to 2PS6IMG.zip
-copy 2PS6IMG.zip to ext_sd card
-boot into download mode
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
Flash Firmware via fastboot, no ext sd card needed...
-rename firmware to firmware.zip
-copy firmware.zip to your adb/fastboot/sdk folder
-boot into download mode
-plug in usb
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
dottat said:
Attempt to get a new fresh unlock token and tell me what HTC dev says?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Actually I had tried that since this bootloop issue came up and was given a new .bin file without any problems. The problem is when i tried to flash the .bin file i got this:
sending 'unlocktoken' (0 KB)...
OKAY [ 1.024s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
vijn said:
Actually I had tried that since this bootloop issue came up and was given a new .bin file without any problems. The problem is when i tried to flash the .bin file i got this:
sending 'unlocktoken' (0 KB)...
OKAY [ 1.024s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
Click to expand...
Click to collapse
Ok. So your only hope would be to get the ruu files extracted and to manually flash each partition by name. Get it to boot and enable oem unlock. Then flash new token and flash twrp and root and S-off via sunshine. Then fix the cid and do the rest the correct way.
Sent from my SM-G955U using Tapatalk
OMJ said:
try this, grab the stock boot.img from the firmware zip: https://www.androidfilehost.com/?fid=745425885120723715
copy the boot.img into your sdktools folder
boot into download mode & try to manually flash it
fastboot flash boot boot.img
if that doesn't work, then try this
download the signed firmware: https://www.androidfilehost.com/?fid=745425885120723717
then try one or both of the flashing methods (although I suspect it wont work due to bad CID):
Flash Firmware via download mode (requires micro sd card)....
-rename firmware to 2PS6IMG.zip
-copy 2PS6IMG.zip to ext_sd card
-boot into download mode
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
Flash Firmware via fastboot, no ext sd card needed...
-rename firmware to firmware.zip
-copy firmware.zip to your adb/fastboot/sdk folder
-boot into download mode
-plug in usb
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Click to expand...
Click to collapse
Ok well, I tried these.
The sd card method failed due to the CID mismatch.
The stock boot.img from the firmware zip method gave the following:
sending 'boot' (47977 KB)...
OKAY [ 1.606s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.656s
The Firmware flash via fastboot, no ext sd card needed gave this:
sending 'zip' (66180 KB)...
OKAY [ 3.269s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) ERR CID not matched
(bootloader) ERR [SD_UPDATE_ERR] CID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 7
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 7
(bootloader) [email protected]
FAILED (remote: 7 RU_CID_FAIL cid in android-info mismatched )
finished. total time: 6.456s
I'm screwed aren't I?
dottat said:
Ok. So your only hope would be to get the ruu files extracted and to manually flash each partition by name. Get it to boot and enable oem unlock. Then flash new token and flash twrp and root and S-off via sunshine. Then fix the cid and do the rest the correct way.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
OK, this is slightly above my pay-grade. While I've read up on it it always seemed too complicated to try in the past, but this is as good a time as any to learn. Any way you can point me in the right direction on this? Not sure how to do this. I assume I should use the original sprint RUU.zip?
vijn said:
OK, this is slightly above my pay-grade. While I've read up on it it always seemed too complicated to try in the past, but this is as good a time as any to learn. Any way you can point me in the right direction on this? Not sure how to do this. I assume I should use the original sprint RUU.zip?
Click to expand...
Click to collapse
Use the original zip and the instructions/tools provided here (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928) to extract your RUU into the basic partition files. Then flash each one using fastboot by name (eg fastboot flash system system_1.img etc)
dottat said:
Use the original zip and the instructions/tools provided here (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928) to extract your RUU into the basic partition files. Then flash each one using fastboot by name (eg fastboot flash system system_1.img etc)
Click to expand...
Click to collapse
Ok, will try that. You wouldn't happen to know where I can find the zip would you? I always used the exe cause that's what was on the htc site. Not sure where the actul RUU.zip file can be found. I assume I can use the one found here: https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
And dottat, OMJ, thanks a lot for your help. It's people like you who make this community what it is.
Hey OMJ,
I grabbed one of your RUU.zip files from your repository on xda ( https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257 ). The zip files, when extracted, turn into like 25 zips. When I extract 0.zip (in order to extract the entire array) I get a file corrupt errors for a few of the files. Am I missing something? I don't think the files are actually corrupt but this is a recurring error I've gotten on a number of different .zip files that have the string of multiple zips within them. Got any ideas?
vijn said:
Hey OMJ,
I grabbed one of your RUU.zip files from your repository on xda ( https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257 ). The zip files, when extracted, turn into like 25 zips. When I extract 0.zip (in order to extract the entire array) I get a file corrupt errors for a few of the files. Am I missing something? I don't think the files are actually corrupt but this is a recurring error I've gotten on a number of different .zip files that have the string of multiple zips within them. Got any ideas?
Click to expand...
Click to collapse
u download the 2PS6IMG.zip? If so, u can't extract, it's encrypted. You would need to decrypt using the tool that dottat linked u
BUT, don't waste your time, aint gonna work, u already tried manually flashing the boot.img & u got the failed, s-on error
to confirm, from download mode, u used this cmd? fastboot flash boot boot.img if so, I'm fresh out of ideas....
sending 'boot' (47977 KB)...
OKAY [ 1.606s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.656s
OMJ said:
u download the 2PS6IMG.zip? If so, u can't extract, it's encrypted. You would need to decrypt using the tool that dottat linked u
BUT, don't waste your time, aint gonna work, u already tried manually flashing the boot.img & u got the failed, s-on error
to confirm, from download mode, u used this cmd? fastboot flash boot boot.img if so, I'm fresh out of ideas....
sending 'boot' (47977 KB)...
OKAY [ 1.606s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.656s
Click to expand...
Click to collapse
Ya, that's what I'd done, but strangely this time I got a different error:
sending 'boot' (47977 KB)...
OKAY [ 2.529s]
writing 'boot'...
(bootloader) HOSD CL#857212
FAILED (remote: 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCKED)
finished. total time: 3.551s
vijn said:
Ya, that's what I'd done, but strangely this time I got a different error:
sending 'boot' (47977 KB)...
OKAY [ 2.529s]
writing 'boot'...
(bootloader) HOSD CL#857212
FAILED (remote: 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCKED)
finished. total time: 3.551s
Click to expand...
Click to collapse
odd...u can certainly try to flash the system.img but it will probably give the same error...I can the complete single system.img if u want me to upload or u can use the decrypt tool to decrypt the ruu & flash the individual system imgs
OMJ said:
odd...u can certainly try to flash the system.img but it will probably give the same error...I can the complete single system.img if u want me to upload or u can use the decrypt tool to decrypt the ruu & flash the individual system imgs
Click to expand...
Click to collapse
Would you mind sending the system file? I haven't managed to get the decrypt tool working yet.
vijn said:
Would you mind sending the system file? I haven't managed to get the decrypt tool working yet.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=745425885120734364
Saw your post while looking for an sim unlock for my Japanese HTC 10.
Couldn't resist reading more about your problem tho.
First idea but quite dangerous if done incorrectly..
Try and see if you can change the cid in the ruu.exe with a HEX editor?
If that doesn't work, next try and change the cid of the ruu. zip.
Might be a long shot, but if the files cid's aren't encrypted it might work!
Hi guys finally i managed to unbrick the hard bricked phone ...
now my question is how should i choose the stock firmware for my device which is Indian variant - XT1686 32 GB
Bcoz as there are lots of different variants .... i have tried brazil
XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2017-02-05
this doesnt give IMEI numbers it will make them 0 so can u guys please tell me how should i choose the variants
and also please if some one have the recent boot loader.img, recovery.img and gpt.bin please provide me im stuck in boot loop ... just the sake until we get oreo update - XT1686 is my phone
i am not able to use my phone right now request you guys....
It's normal not to have your IMEI on stock if you've flashed Oreo ROMs before.
You can follow instructions in this thread if you want to get IMEI back.
Happy flashing!
Jrhotrod said:
It's normal not to have your IMEI on stock if you've flashed Oreo ROMs before.
You can follow instructions in this thread if you want to get IMEI back.
Happy flashing!
Click to expand...
Click to collapse
now actually my phone is stuck with Moto Z2 play boot loader so that i need everything to be Moto z2 play's firmware .... to wake up the dead phone it took me around 4 hours .... So my boot loader is not letting me install any other firmwares on my phone
please help me :crying:
This is what i got when i tried to flash Moto g5 plus Boot loader by downloading all the firmwares from official website:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.118s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.405s
praveen Glaxi said:
now actually my phone is stuck with Moto Z2 play boot loader so that i need everything to be Moto z2 play's firmware .... to wake up the dead phone it took me around 4 hours .... So my boot loader is not letting me install any other firmwares on my phone
please help me :crying:
This is what i got when i tried to flash Moto g5 plus Boot loader by downloading all the firmwares from official website:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.118s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.405s
Click to expand...
Click to collapse
What on Earth did you do to get the Z2 bootloader and how did you get it to even flash in the first place?
Jrhotrod said:
What on Earth did you do to get the Z2 bootloader and how did you get it to even flash in the first place?
Click to expand...
Click to collapse
Okay dude .... Let me explain very quickly ....
First off I bought this device like 8 months ago .... 1 week b4 I flashed customs ROM that is lineago os 15.1 which was recent for my device .... Everything was fine until yrstdy.... Yrstdy morning what I did was I planned to flash normal stock ROM to my phone .... Using some brasil version by watching YouTube ... Everything went well I was like thank god and then I inserted the sim but there was not network due to imei issue ....
This is where problem started...
Thinking after I do the OTA update security patch might go back and I might get the signal but then I did ota update and phone restarted ... It showed installing updates in half wat it suddenly switched I realised that I hard bricked my phone ...
Then searched the whole xda forums and found this guide https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457/page6
By Rakesh1b.....
I did the same I used potter blank flash and my phone woke up after trying it several hours....
Then when I tried to flash bootloader of moto g5 plus it showed error like I previously displayed ..... Well there was one more post for all of these 3 files, bootloader.IMG gpt.bin and recovery.IMG well I did flash all of them they seem to be worked ...
Then I tried to flash moto g5 plus twrp recovery which gave me error of failure...
Then I tried moto z2 play twrp ... God damn it got flashed and went into twrp recovery then as I studied as per @Rakesh1b ......
And now I'm stuck here ..... Not able to go front...
I get error like /cache not found when I try to flash custom os ...
What all I need now is moto g5 plus boot loader.IMG recovery.IMG gpt.bin
Of January security patch ... Mine last update was November security patch
I request some one to give those files or give a proper solution for this plzzzzzz
praveen Glaxi said:
I did the same I used potter blank flash and my phone woke up after trying it several hours....
Then when I tried to flash bootloader of moto g5 plus it showed error like I previously displayed ..... Well there was one more post for all of these 3 files, bootloader.IMG gpt.bin and recovery.IMG well I did flash all of them they seem to be worked ...
Then I tried to flash moto g5 plus twrp recovery which gave me error of failure...
Then I tried moto z2 play twrp ... God damn it got flashed and went into twrp recovery then as I studied as per @Rakesh1b ......
And now I'm stuck here ..... Not able to go front...
I get error like /cache not found when I try to flash custom os ...
What all I need now is moto g5 plus boot loader.IMG recovery.IMG gpt.bin
Of January security patch ... Mine last update was November security patch
I request some one to give those files or give a proper solution for this plzzzzzz
Click to expand...
Click to collapse
Thank you for the explanation, your situation seems to (mostly) make sense to me now.
You probably realize this in retrospect, but you should not have accepted an OTA on stock with no IMEI. But enough with that, what exactly do you mean by "my phone woke up"? I'd love to offer you a solution, but to find one, I'll need to know if "waking up" involved booting into Android, booting into the bootloader, or whatever.
u should unlock bootloader first.. the version of bootloader is lower than on ur phone, you should not OTA update, OTA did upgraded ur bootloader ver to latest..
---------- Post added at 06:32 AM ---------- Previous post was at 06:28 AM ----------
Try this firmware for ur model latest from february 2018
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
or
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
---------- Post added at 06:54 AM ---------- Previous post was at 06:32 AM ----------
[/COLOR]if u followed this solution and unbricked ur devices,try this Rom
its debloated and deodexed stock rom
: https://doc-00-6o-docs.googleuserco...2322377&hash=4s4e5hh6kltpi7nthp0actt4434mbjof
Orginal post :
https://forum.xda-developers.com/g5-plus/development/stock-debloated-deodexed-t3619972
THE FIRST THING U SHOULD TO UNLOCK BOOTLOADER before to try and CWM OR TWRP, custom rom..
Hey guys thanks for everyone's assistance here
i have successfully flashed Pixel experience ROM to my phone by using this procedure
1st. Blank flash your phone as per the above procedure..... (disable signature enforcement if u are using windows 10)
press and hold power button you could hear that mobile disconnects and connects once you hear that then press voldown and power with one hand and run blankflash.bat and then release those buttons before u hear them again
2nd. Flash all 3 provided files in MotoG5Plus_addison2Potter in the attachement and it will take you to the boot loader
Using these Commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Fastboot flash recovery recovery.img
fastboot reboot-bootloader
(Flash the files from provided Zip attachment)
3rd. download Moto z2 play or plus twrp recovery as i didnt have time to compress everything i cud nt provide that, then flash the custom recovery, then try to enter into recovery mod and it should enter..... if u have done 1st and 2nd step properly then u will enter into TWRP recvery mod
and here is the link for debolated ROM download version 2 which has november patch on it....
https://forum.xda-developers.com/g5-...dexed-t3619972
then once ur in twrp mount it to ur pc and copy the debolate ROM to ur phone and then flash it though TWRP ....
once it is done reboot ur phone into os and it should successfully boot into ROM...
once done u can flash any custom ROM into ur phone using TWRP
But 1 major issue is that i lost 4g or VoLTE:
Can u guys please help me with that.....