Database Info

[Q] IMEI 0 needs to recovery WHO CAN HELP?

Hi everyone,
i recieved yesterday my Moto G, 16GB,Retailversion, bought and live in Germany, bought used. Everything works well on it. This phone comes with KITKAT 4.4.2 with an unlocked bootloader, CMW and Superuser.
The phone is resettet, all clear. The only thing is, that the IMEI=0
The phone is on the latest german 175.44.1.falcon_umts.RETAIL.en.DE
Build Number: KLB20.9.10-1.9.1
If i am move with this phone the signal will be 1 to 5 or loss. If this phone is placed on my desk it chows the whole day 3 to 5 signalbars.
I tried to use this command in terminal or adb: echo 'AT +EGMR=1,7,"XXXXXXXXXXXXXXXX"> /dev/pttycmd1 but no success.
I have currently no backup from this phone, i have the IMEI of this phone.
Who can help me to write my original IMEI back to phone? This is quite urgent. PLEASE HELP ME OUT.
Thanks

How much did you pay for it you can try flashing stock ROM or firmware to see if you can recover imei
Sent from my XT1034 using xda app-developers app

serophia said:
How much did you pay for it you can try flashing stock ROM or firmware to see if you can recover imei
Sent from my XT1034 using xda app-developers app
Click to expand...
Click to collapse
I got quite the same problem, tried that many times, flashed different stock and custom roms, radio images, nothing worked..
Quite bad to have such a great "Tablet".. I'd really need to use the normal phone functions..

i think we need a imei backup from someone and change the imei to our original one. WHO can help us please?
Some files are missing in root, same was with wifi before, i found a file, that changes the state, but phone signal doesn't comming back without help.

From fastoboot you can get:
Fastboot getvar imei (you can view you imei)
Fastoboot oem writeimei your imei. (Take original imei from box)
You must have bootloader unlocked

cicciocant said:
From fastoboot you can get:
Fastboot getvar imei (you can view you imei)
Fastoboot oem writeimei your imei. (Take original imei from box)
You must have bootloader unlocked
Click to expand...
Click to collapse
If I try this it just gets out
FAILED (remote failure)
finished. total time: 0.020s

RestlessScreams said:
If I try this it just gets out
FAILED (remote failure)
finished. total time: 0.020s
Click to expand...
Click to collapse
hi, i did this command: Fastboot getvar imei
IMEI is listed correctly , but i can't do this command after too: Fastoboot oem writeimei "your imei"
Same problem as user "RestlessScreams"
FAILED (remote failure)
finished. total time: 0.016s

Jerome-X said:
hi, i did this command: Fastboot getvar imei
IMEI is listed correctly , but i can't do this command after too: Fastoboot oem writeimei "your imei"
Same problem as user "RestlessScreams"
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
Try using :
fastboot oem writeimei "your imei".... I think "cicciocant" made a typo, if i'm not mistaken.

mardobloom said:
Try using :
fastboot oem writeimei "your imei".... I think "cicciocant" made a typo, if i'm not mistaken.
Click to expand...
Click to collapse
This is what i got in fastboot: (fastboot.exe getvar all)
(bootloader) version: 0.5
(bootloader) version-bootloader: 4105
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA8900FI4F
(bootloader) cid: 0x0007
(bootloader) uid: 28F911020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 3X5XX2X5XX16XX7 (the IMEI is shown correctly)
(bootloader) meid:
(bootloader) date: 12-26-2013
(bootloader) sku: XT1032
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Feb 24 8:58:15 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retde/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.2/KLB20.9-1.10-1.24-1.1/1:user
(bootloader) ro.build.fingerprint[2]: /release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.176.44.1.falcon_umts
(bootloader) ro.build.version.full[1]: .Retail.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2.3.04.03.0
(bootloader) ro.build.version.qcom[1]: 0.166.006
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-gc6fc9e1-00001-gf3bf
(bootloader) kernel.version[1]: 628 ([email protected]) (gcc version 4.
(bootloader) kernel.version[2]: 7 (GCC) ) #1 SMP PREEMPT Thu Feb 6 23:07
(bootloader) kernel.version[3]: :13 CST 2014
(bootloader) sdi.git: git=MBM-NG-V41.05-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V41.05-0-g6863770
(bootloader) rpm.git: git=MBM-NG-V41.05-0-g4018bbe
(bootloader) tz.git: git=MBM-NG-V41.05-0-g11658be
(bootloader) aboot.git: git=MBM-NG-V41.05-0-gf4ab363
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
all: listed above
finished. total time: 0.062s
but IMEI shows 0 while running system.
No signal, no provider, only WIFI is useable

You van try this:
http://forum.xda-developers.com/showthread.php?t=2623587
Inviato dal mio XT1032 utilizzando Tapatalk

doesent work, how to get my imei back? any possible solution here let me not write my imei back to phone. Why do i see my imei in fastbootmode and not in Android OS?
Gesendet von meinem LG-D802 mit Tapatalk

Got same problem since three weeks.
Tried re flashing stock, changing radio, break fastboot... Nothing worked, i was going to give it back to Motorola but i see many people got same problem so I think i'll wait a bit for a potential solution.
Getvar all gave me correct imei, system shows 0.
Sent from my XT1032 using Tapatalk
---------- Post added at 08:09 AM ---------- Previous post was at 07:39 AM ----------
sorry to add more to my previous reply:
"AT +EGMR=1,7,"XXXXXXXXXXXXXXXX"> /dev/pttycmd1" only works for MTK based phones.
And
writeimei isn't supported in fastboot
I was thinking if there is a way to physically remove battery from Moto G, haven't found any in google

Did you flash your phone without Sim Card?
If i understand this statement right, he had the same problem while flashing his phone without sim card.
herbesi01 said:
I solved the problem, place to charge the phone, let him take some of the load and flash the original ROM, after that flash CM11, and run perfectmente, I think at first it was because I had done without the SIM, the second time you make with the SIM sunset ...
Click to expand...
Click to collapse

mokkami said:
Did you flash your phone without Sim Card?
If i understand this statement right, he had the same problem while flashing his phone without sim card.
Click to expand...
Click to collapse
I tried flashing always with SIM Card on it, i even changed Cards but still 0 imei.

Maybe this is compatible with Moto G?!

The go back to stock without SIM, skip all and going home, boot off, reinsert another SIM isn't working.
will try other solutions, i hope

any news, about restore IMEI?

Jerome-X said:
any news, about restore IMEI?
Click to expand...
Click to collapse
Not yet unluckly...

Edit

mokkami said:
Maybe this is compatible with Moto G?!
Click to expand...
Click to collapse
DId someone try ?

[Q] Is unlocking Photon Q possible?

I have Photon Q from Sprint with Android 4.1.2 (9.8.2Q-122_XT897_FFW-5), bootloader 109B(*)
log
Code:
C:\>fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [ 0.016s]
finished. total time: 0.016s
Can I unlock this Photon Q?

a good data cable is key!
carl0 said:
I have Photon Q from Sprint with Android 4.1.2 (9.8.2Q-122_XT897_FFW-5), bootloader 109B(*)
log
Code:
C:\>fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [ 0.016s]
finished. total time: 0.016s
Can I unlock this Photon Q?
Click to expand...
Click to collapse
Make sure that you have a bone fide data cable. I encountered similar errors and wasted a lot of time early in my unlocking/rooting efforts.
I bought this cable from Amazon for around $5: "Motorola SKN6238 MicroUSB Data Cable", and it has been great.
Good luck ...

I have Motorola SKN6378A MicroUSB Data Cable.
Code:
C:\>fastboot getvar all
(bootloader) version-bootloader: 109B(*)
(bootloader) product: asanti_c
(bootloader) secure: yes
(bootloader) mid: 0057
(bootloader) version: 0.5
(bootloader) serialno: T0********
(bootloader) qe: qe 0/0
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 31457280
(bootloader) emmc-size: 8GB
(bootloader) reason: Reboot to bootloader
(bootloader) revision-hardware: 0x82B0
(bootloader) cpu: MSM8960 CS
(bootloader) uid: 4302D30302000100000000000000
(bootloader) cid: 0x00
all:
finished. total time: 0.016s
Could it be the fault of the cable?
Has anyone else met this problem?

It's been a very long time since I unlocked my Q, but are you putting in the proper code? From your command prompt output above, it seems like you did not put in the unlock code.

First he needs the "oem_unlock_code" from the PQ, before he gets the correct unlock code from Motorola.
I think that the first thing already fails and he is not able to continue with the Motorola site.
I remember hardly that there was another way of unlocking the bootloader, but I don't remember the name.
Something only for Motorola devices I think.
edit: Was it "motochopper"? I've never used it, so I'm not sure.

Loader009 said:
First he needs the "oem_unlock_code" from the PQ, before he gets the correct unlock code from Motorola.
I think that the first thing already fails and he is not able to continue with the Motorola site.
I remember hardly that there was another way of unlocking the bootloader, but I don't remember the name.
Something only for Motorola devices I think.
edit: Was it "motochopper"? I've never used it, so I'm not sure.
Click to expand...
Click to collapse
Yes, motochopper. You could try that OP, as a way to unlock the device - albeit unofficially.

Since the OP is running 4.1.2, my guess is that motochopper won't work (because that exploit was probably repaired in 4.1.2), but one if its successors might.
Sent from my XT897 using Tapatalk

carl0 said:
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
Click to expand...
Click to collapse
This is weird.
When and where did you get this device?

@carl0 : It's indeed very strange that get_unlock_data doesn't work on your device.
But I'm pretty sure that the unofficial bootloader unlock tool Motopocalypse by Dan Rosenberg will work: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
Motopocalypse requires the device to be rooted, which can be easily achieved e.g. by geohot's towelroot: https://towelroot.com/

mrvek said:
This is weird.
When and where did you get this device?
Click to expand...
Click to collapse
ebay :laugh:
kabaldan said:
@carl0 : It's indeed very strange that get_unlock_data doesn't work on your device.
But I'm pretty sure that the unofficial bootloader unlock tool Motopocalypse by Dan Rosenberg will work: h**p://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
Motopocalypse requires the device to be rooted, which can be easily achieved e.g. by geohot's towelroot: h**ps://towelroot.com/
Click to expand...
Click to collapse
I've tried this another way of unlocking the bootloader and it works well. :fingers-crossed:
Thanks for all!

[ Unlocked BL] [DS] Need help in root/recovery investigations (Solved)

Hi all,
I recently bought this phone and I really love it, unfortunaly no root/recovery methode available for now :crying:
With my little knowledge (I'm not a dev) I have successfully ported TWRP on the Archos Platinum 50 and rooted it.
and now i'm trying to do the same with the XA.
The bootloader was unlocked with official procedure but now I have a problem when trying to hotboot in fasboot mode: FAILED (remote: oem unlock is false)
When trying :
C:\Flashtool\x10flasher_lib>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.496s]
booting...
FAILED (remote: oem unlock is false)
finished. total time: 0.505s
Click to expand...
Click to collapse
Maybe a bad unlocked Bootlader?
C:\Flashtool\x10flasher_lib>fastboot oem unlock
...
FAILED (remote: Not necessary)
finished. total time: 0.002s
Click to expand...
Click to collapse
and
C:\Flashtool\x10flasher_lib>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:system: d7000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: c800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-sizeem: 12800000
(bootloader) partition-typeem: ext4
(bootloader) partition-size:diag: 1000000
(bootloader) partition-type:diag: ext4
(bootloader) partition-size:apps_log: 1000000
(bootloader) partition-type:apps_log: ext4
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:boot: 2800000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk2: 100000
(bootloader) partition-type:lk2: raw data
(bootloader) partition-size:lk: 100000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:md3img: 500000
(bootloader) partition-type:md3img: raw data
(bootloader) partition-size:md1arm7: 400000
(bootloader) partition-type:md1arm7: raw data
(bootloader) partition-size:md1dsp: 4c0000
(bootloader) partition-type:md1dsp: raw data
(bootloader) partition-size:md1img: 1800000
(bootloader) partition-type:md1img: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizeemkeystore: 800000
(bootloader) partition-typeemkeystore: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-sizepl: 40000
(bootloader) partition-typepl: raw data
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:fotakernel: 2800000
(bootloader) partition-type:fotakernel: raw data
(bootloader) partition-size:ltalabel: 1000000
(bootloader) partition-type:ltalabel: ext4
(bootloader) partition-sizerotect2: b80000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:ta: 200000
(bootloader) partition-type:ta: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) version-preloader:
(bootloader) version: 0.5
(bootloader) secure: no
(bootloader) version-baseband: 1300-9504_33.2.B.2.35
(bootloader) version-bootloader: 1298-9241 S1_Boot_MT6755_M0.MP6_13
(bootloader) serialno: RQ3000TNHH
(bootloader) product: F3112
all: Done!!
finished. total time: 0.062s
Click to expand...
Click to collapse
Under Android , the OEM unlock switch is ON in dev settings and in the hidden service menu:
Bootloader unlocked: Yes
Remote Lock State: Unlocked
I never tryed with flash commands because I don't know which tool to use for reflash if needed (Flashtool, WMshua, any MTK tools, ...)
If someone could shed some light on the fastboot error and tell me which flash tool to use, may be that I can share something with the community
Thanks
07/07/2016: You can flash stock firmware with Flashtool V0.9.22.3
10/07/2016: It seem that Sony removed hotboot ability on Unlocked BL. Now I need headers offsets for repacking .elf or a way to find them
14/07/2016: Finally I found offsets with "readelf" command, but no way for building new boot image.
I can't find correct commands with "mkbootimg" or "mkelf".
17/07/2016: For now I will wait for Sony to give us the good commands for compiling with mkbootimg
24/07/2016: Can't wait for Sony... After having sweated blood, I successfully compiled,repacked, flashed and... booted with
persistent changes a new boot.img !!! Rooted device is for soon
24/07/2016 MAJ 2: Finally rooted !!! (see screenshot) Will release as soon as possible !

Hello i know it's not the topic but i want to know what is the battery life of your xperia xa in use on facebook YouTube phone and message because i have the same phone but i don't finish the day With
Sorry for my bas english and thank you for your answer
Sent from my LT18i using XDA-Developers mobile app

hassan1999 said:
Hello i know it's not the topic but i want to know what is the battery life of your xperia xa in use on facebook YouTube phone and message because i have the same phone but i don't finish the day With
Sorry for my bas english and thank you for your answer
Click to expand...
Click to collapse
You need to turn off always scanning in wifi settings there is a software problem that Sony know about and are going to release a update it's stopping the device from into deep sleep.

aidy.lucas said:
You need to turn off always scanning in wifi settings there is a software problem that Sony know about and are going to release a update it's stopping the device from into deep sleep.
Click to expand...
Click to collapse
Thank you for the answer and I want to Know from where this information come to you please
Thank you !
Sent from my LT18i using XDA-Developers mobile app

hassan1999 said:
Thank you for the answer and I want to Know from where this information come to you please
Thank you !
Click to expand...
Click to collapse
See Sony support forum there's a message/reply on a thread in the xa section stating that Sony know about the software problem and they will fix it in the next update though there's no eta on it yet. Following everything closely as I going to replace my trusty m2 with a xa in a couple of weeks.

hassan1999 said:
Thank you for the answer and I want to Know from where this information come to you please
Thank you !
Sent from my LT18i using XDA-Developers mobile app
Click to expand...
Click to collapse
See this, about the wifi scanning bug.

any news ?

I am looking for working method.

hp6830s said:
I am looking for working method.
Click to expand...
Click to collapse
Everyone is, but our hands are tied at the moment...

SDee96 said:
Everyone is, but our hands are tied at the moment...
Click to expand...
Click to collapse
I think it'll be unlocked Bootloader root only due to drm-verity introduced by Sony on z3+. I'll know more when I get mine

I found working method to unlock it,even without DATA wipe.
https://www.youtube.com/watch?v=nSNDSyeys2g&authuser=0
PS : KingRoot PC and app ,KingoRoot,+ few more stuck or failed on 30 % while rooting.

I will release new boot and TWRP recovery before this week-end, all is working fine but I need more time to check all one more time. Your will need unlocked bootloader and 33.2.B.2.35 firmware.
Edit: Sony released 33.2.B.2.73 open source archive yesterday, will update my work before release.

rrvuhpg said:
I will release new boot and TWRP recovery before this week-end, all is working fine but I need more time to check all one more time. Your will need unlocked bootloader and 33.2.B.2.35 firmware.
Edit: Sony released 33.2.B.2.73 open source archive yesterday, will update my work before release.
Click to expand...
Click to collapse
What about drm restore fix? +ta keys backup? For bravia engine x-reality and probably camera too. Guessing locked Bootloader root days are finished. Hopefully pick mine up tomorrow or Thursday latest firmware includes new kernel+wifi bug fix

I don't see any changes before and after unlock, Bravia engine is present, no visible differences in camera quality, all Sony apps are working like on first day (TrackID too) . Like on other devices you lose Xperia Care, OTA updates and PC Compagnon updates. I'm not a dev and it must be confirmed after release, for now it's just my feedback. Other information, SELinux stay in enforcing mode after root

rrvuhpg said:
I don't see any changes before and after unlock, Bravia engine is present, no visible differences in camera quality, all Sony apps are working like on first day (TrackID too) . Like on other devices you lose Xperia Care, OTA updates and PC Compagnon updates. I'm not a dev and it must be confirmed after release, for now it's just my feedback. Other information, SELinux stay in enforcing mode after root
Click to expand...
Click to collapse
bravia engine x-reality relies on drm/ta keys why I've always left my bootloader locked on my M2 I know updates won't install not a problem i will need to update my flashtool though as I'm still using 9.18.6 as it just seems to work better I take it this device works with Flashtool OK then as with C4 +c5 mediatek powered Xperia devices it hard bricks them. I don't think I'll be able to cope long without root anyway I'll certainly help where I can once I get mine

you have the boot.img for us? how'd you root? i appreciate your work btw but I'm anxious to get this thing rooted lol need xposed and a couple modules ..... uhhhhh nvm just read the previous post lol. ugh ill hold on lol thanks again

Can you give to me link Flashtool V0.9.22.3. I can't find it.
Sorry my bad english

How did you manage to root yours :crying:
I tried mine to no avail had the same "Remote: oem unlock is false" thing at the end my bootloader is unlocked by official method and "allow oem unlock" is on under dev settings plz help

[Xperia XA user said:
;69816547]How did you manage to root yours :crying:
I tried mine to no avail had the same "Remote: oem unlock is false" thing at the end my bootloader is unlocked by official method and "allow oem unlock" is on under dev settings plz help
Click to expand...
Click to collapse
If the "fastboot oem unlock" command end with (not necessary) at the end of the error, you are good and you can continue the guide.

Explanation
rrvuhpg said:
Hi all,
I recently bought this phone and I really love it, unfortunaly no root/recovery methode available for now :crying:
With my little knowledge (I'm not a dev) I have successfully ported TWRP on the Archos Platinum 50 and rooted it.
and now i'm trying to do the same with the XA.
The bootloader was unlocked with official procedure but now I have a problem when trying to hotboot in fasboot mode: FAILED (remote: oem unlock is false)
When trying :
Maybe a bad unlocked Bootlader?
and
Under Android , the OEM unlock switch is ON in dev settings and in the hidden service menu:
Bootloader unlocked: Yes
Remote Lock State: Unlocked
I never tryed with flash commands because I don't know which tool to use for reflash if needed (Flashtool, WMshua, any MTK tools, ...)
If someone could shed some light on the fastboot error and tell me which flash tool to use, may be that I can share something with the community
Thanks
07/07/2016: You can flash stock firmware with Flashtool V0.9.22.3
10/07/2016: It seem that Sony removed hotboot ability on Unlocked BL. Now I need headers offsets for repacking .elf or a way to find them
14/07/2016: Finally I found offsets with "readelf" command, but no way for building new boot image.
I can't find correct commands with "mkbootimg" or "mkelf".
17/07/2016: For now I will wait for Sony to give us the good commands for compiling with mkbootimg
24/07/2016: Can't wait for Sony... After having sweated blood, I successfully compiled,repacked, flashed and... booted with
persistent changes a new boot.img !!! Rooted device is for soon
24/07/2016 MAJ 2: Finally rooted !!! (see screenshot) Will release as soon as possible !
Click to expand...
Click to collapse
Embrath,
How did you do it man.Please share.I am stuck with xperia c4 dual without recovery mode.the fastboot gives me a false oem unlock.Shed some light

Messed up installing 5.1.11. now only fastboot boots and can't boot twrp image.

i tried to install the newest 5.1.11 in full ( as i am magisk rooted, twrp installed, and bootloader unlocked). i kept getting system ui crashes over and over and eventually, after so many, the phone just powers down by itself. I had tried clearing cache after going back into twrp. Rebooted. Same ui issue. Then i decided to restore a backup in twrp i had made a few weeks ago stored on internal memory. This was a bad idea. It said it restored successfully but upon reboot, i only get fastboot now. i think it is communicating with fastboot but when i try to fastboot boot twrp-3.2.1-0 (or 3.2.2-0) i get, "remote: Failed to load/authenticate boot image: Load Error". I do not know what to do and am hoping you guys can figure out how to fix this. Any attempt to enter recovery via buttons results in fastboot booting. restart is also fastboot.
This is what my phone says:
FastBoot mode
Product_name- sdm845
variant- sdm ufs
basband version-
serial- it's there
secure boot- yes
device state- unlocked
Don't know if this helps fastboot getvar all reports this:
C:\Adb\OnePlus 6 Files>fastboot getvar all
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3837
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B800B7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xB2C00000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno: omitted
(bootloader) product:sdm845
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.047s
Is there anyone that has had this set of circumstances and got out of it? Any help is appreciated. There are some things i've seen that i can do but don't want to do further damage. Thanks to all for any and all help.

thejase said:
i tried to install the newest 5.1.11 in full ( as i am magisk rooted, twrp installed, and bootloader unlocked). i kept getting system ui crashes over and over and eventually, after so many, the phone just powers down by itself. I had tried clearing cache after going back into twrp. Rebooted. Same ui issue. Then i decided to restore a backup in twrp i had made a few weeks ago stored on internal memory. This was a bad idea. It said it restored successfully but upon reboot, i only get fastboot now. i think it is communicating with fastboot but when i try to fastboot boot twrp-3.2.1-0 (or 3.2.2-0) i get, "remote: Failed to load/authenticate boot image: Load Error". I do not know what to do and am hoping you guys can figure out how to fix this. Any attempt to enter recovery via buttons results in fastboot booting. restart is also fastboot.
This is what my phone says:
FastBoot mode
Product_name- sdm845
variant- sdm ufs
basband version-
serial- it's there
secure boot- yes
device state- unlocked
Don't know if this helps fastboot getvar all reports this:
C:\Adb\OnePlus 6 Files>fastboot getvar all
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3837
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B800B7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xB2C00000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno: omitted
(bootloader) product:sdm845
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.047s
Is there anyone that has had this set of circumstances and got out of it? Any help is appreciated. There are some things i've seen that i can do but don't want to do further damage. Thanks to all for any and all help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 your solution lies here

tabletalker7 said:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 your solution lies here
Click to expand...
Click to collapse
I saw this. Will i keep my data with this method?

thejase said:
I saw this. Will i keep my data with this method?
Click to expand...
Click to collapse
no, but if you can't even boot to TWRP then you have nothing left to save at this point.

Try booting the latest twrp (3.2.3.0) before giving up and wiping. If you can get to fastboot, you're not bricked.

iElvis said:
Try booting the latest twrp (3.2.3.0) before giving up and wiping. If you can get to fastboot, you're not bricked.
Click to expand...
Click to collapse
thanks for the suggestions but no dice.

According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot rom to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.

tabletalker7 said:
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot rom to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
Click to expand...
Click to collapse
That's alright. I appreciate the point in the right direction. Doing that fastboot method bat file that you suggested now... Thanks for the help.

thejase said:
That's alright. I appreciate the point in the right direction. Doing that fastboot method bat file that you suggested now... Thanks for the help.
Click to expand...
Click to collapse
tabletalker7 said:
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot ROM to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
Click to expand...
Click to collapse
So as it turns out that method worked using the bat file flash all fastboot. Though, not at first. When it first rebooted after the bat file finished flashing. system UI was still crashing. When you initially run the bat file at the beginning, it asks if you want to delete your data. First time around i said no, just to see what it would do. Well it booted, but kept getting that system ui crash that I had in the beginning of all this mess. I rebooted and this time chose to erase data and then it re-flashed all again (same bat file). Turns out, when it booted, same deal, system UI crash. So this time i was looking things up while the crashes where happening and then it just rebooted on its own (as it does with a number of system UI crashes in succession). When it came up it was that Chinese menu (which i assume to be download mode or something). Anyway, i chose English and it's a menu to clear dalvik and cache, system settings reset, and one other i can't remember. i did system settings then dalvik and finally, when i rebooted, it was like it was booting for the first time with no crashes. Only thing i can figure is that setting in the bat file at first launch actually didn't erase user data since when it booted, all my icons where there in the background. doing it "on device" in download mode seems to have worked. I am only adding this information as an f.y.i.. Thanks again for all your help, guys.

thejase said:
When it came up it was that Chinese menu (which i assume to be download mode or something).
Click to expand...
Click to collapse
That's stock recovery.

maigre said:
That's stock recovery.
Click to expand...
Click to collapse
Oh, ok. Funny thing is, I had never seen what that looked like as I immediately installed twrp from the time I bought it. Makes sense, though I still wonder why it booted to stock recovery after systemui crashing. Unless it senses the crashes and does that by default to clear system settings and data for a successful boot?

moto one vision hard bricked

i unlocked the bootloader and then unknowingly i gave command " fastboot erase all ".
now the device is not powering on and not even responding,no screen on (even when inserting charger).
can anyone suggest a solution??

D A R K 9 said:
i unlocked the bootloader and then unknowingly i gave command " fastboot erase all ".
now the device is not powering on and not even responding,no screen on (even when inserting charger).
can anyone suggest a solution??
Click to expand...
Click to collapse
Take it to a service center for flashing the firmware?

D A R K 9 said:
i unlocked the bootloader and then unknowingly i gave command " fastboot erase all ".
now the device is not powering on and not even responding,no screen on (even when inserting charger).
can anyone suggest a solution??
Click to expand...
Click to collapse
Don't take strictly right but I've done it some time ago on a Snapdragon phone . For this you absolutely need for Motorola One Vision Qfil files and Flashone app for Windows . The whole process is very simple but finding proper Qfil files ROM is a pain in the butt .
If you find these files somehow , anywhere , anytime don't forget to share .
...............................
Or use this : https://forum.xda-developers.com/moto-z/help/help-moto-z-dead-brick-t3809740
Or this : https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183

muppetz said:
Don't take strictly right but I've done it some time ago on a Snapdragon phone . For this you absolutely need for Motorola One Vision Qfil files and Flashone app for Windows . The whole process is very simple but finding proper Qfil files ROM is a pain in the butt .
If you find these files somehow , anywhere , anytime don't forget to share .
...............................
Or use this : https://forum.xda-developers.com/moto-z/help/help-moto-z-dead-brick-t3809740
Or this : https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183
Click to expand...
Click to collapse
ya but i used to do same cmd for sony and mi mobile but never faced this issue,i didnt expect this thing from a motorola device.now they are saying to change sub board for not power on reason reason at service center.

D A R K 9 said:
ya but i used to do same cmd for sony and mi mobile but never faced this issue,i didnt expect this thing from a motorola device.now they are saying to change sub board for not power on reason reason at service center.
Click to expand...
Click to collapse
You're right . It doesn't explain their proposals if you just did a simple cmd to the phone as you said . Maybe they try to squeeze some extra bucks from you . I'm sorry , man .

hard bricked one vision
its showing as exynos9610 in device manager,any leads from here??

D A R K 9 said:
its showing as exynos9610 in device manager,any leads from here??
Click to expand...
Click to collapse
good news , it seems pc recognize phone , further steps to bring back phone , no clue, but I supose it's primordial to flash partitions . Google it .

D A R K 9 said:
its showing as exynos9610 in device manager,any leads from here??
Click to expand...
Click to collapse
Look in the OP for a rom to flash in fastboot.

gee2012 said:
Look in the OP for a rom to flash in fastboot.
Click to expand...
Click to collapse
sadly its not going to fastboot mode.as of matter still screen not showing anything,only thing just pc shows a device connected in usb as exynos9610

D A R K 9 said:
sadly its not going to fastboot mode.as of matter still screen not showing anything,only thing just pc shows a device connected in usb as exynos9610
Click to expand...
Click to collapse
Try the adb command ` fastboot devices` and see if you get a serial number.

I'm also in this same situation. Been looking all around for solutions but all i come across are fixes for qualcom devices. Even all the blankflashing posts are qualcom. My guess is that we need to find software that'll work with exynos chips that isn't samsung. Adb, fastboot and mfastboot commands don't work because in its current state the device is only recognized as "Exynos9610"

I have the same problema. Im trying to follow this thread:
https://forum.xda-developers.com/galaxy-s6/general/guide-repair-hard-bricked-devices-t3573865/amp/
My problem is that my computer is Windows 10 and it can't load the Exynos drivers, I hope that you have good look with that. You should try to change the cfg archive to load bootloader.

Found something intresting on "lolinet" today. A "blankflash" for kane.
Could be worth a try for sure, if you're hardbricked.
I have not tried it so I've no idea if this is legit.
The procedure would probably be something like:
Unzip all files.
Install drivers (ImageWriterUSBDriver_1113_00.exe).
Open "Multidownloader_64bit_1.4.1.exe".
Connect device to usb and let multidownloader detect it.
In the "box", browse for the "usbbooting.cfg" that is present in the kane_blankflash and hit start.
My guess is that it's supposed to reboot to fastboot once it's done writing the files so that you can reflash full firmware from fastboot, like it is with blankflash for other moto devices.
Let us know how it goes if anyone tries it.

Error
I'm in trouble, too.
I can even enter fastboot but do not accept to update, the following error appears.
target max-sparse-size: 256MB
sending 'fwbl1' (16 KB)...
OKAY [ 0.040s]
writing 'fwbl1'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fwbl1
FAILED (remote failure)
finished. total time: 0.082s
Click to expand...
Click to collapse
My phone get vars
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.2-kane_retail-523afc7-190729
(bootloader) product: kane
(bootloader) board: kane
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: ufs
(bootloader) ufs: 128GB WDC SDINDDH4-128G FV=1268
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: Exynos9609
(bootloader) serialno: 0057049924
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 000003B54E4B96FA0000000000000000
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 354154101426432
(bootloader) meid:
(bootloader) date: 05-09-2019
(bootloader) sku: XT1970-1
(bootloader) carrier_sku: XT1970-1
(bootloader) battid: SB18C43602
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Aug 28 2:48:21 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/kane/kane_sprout:9/PSAS29
(bootloader) ro.build.fingerprint[1]: .137-16-4/fc9db:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.221.4.kane.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.samsung: 20190510
(bootloader) version-baseband: S337AP_KANE_SGCS_QB2190425
(bootloader) kernel.version[0]: Linux version 4.14.56-g1007313 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld115) (Android (4691093 based on
(bootloader) kernel.version[2]: r316199) clang version 6.0.2 (]
(bootloader) kernel.version[3]:
(bootloader) kernel.version[4]: 83abd29fc496f55536e7d904e0abae47888fc7f)
(bootloader) kernel.version[5]: (
(bootloader) kernel.version[6]: hain/llvm 34361f192e41ed6e4e8f9aca80a4ea
(bootloader) kernel.version[7]: 7e9856f327) (based on LLVM 6.0.2svn)) #1
(bootloader) kernel.version[8]: SMP PREEMPT Mon Jul 29 06:52:16 CDT 201
(bootloader) kernel.version[9]: 9
(bootloader) bootloader.git: MBM-2.2-kane_retail-523afc7-190729
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
Click to expand...
Click to collapse
Anyone can helpme?

Okay, I know the last message here was almost 2 years ago, but I'm just here to confirm, that I've tried this blankflash and indeed, it works.
So I've rewritten both bootloader A and B slots with /dev/zero and tried to reboot. Of course, nothing happened, but the device was detected and booted into fastboot. Everything was working there. Than just flashed bootloader_a and bootloader_b and it booted like nothing happened.

danmaya said:
Error
I'm in trouble, too.
I can even enter fastboot but do not accept to update, the following error appears.
My phone get vars
Anyone can helpme?
Click to expand...
Click to collapse
So here you have probably broken UFS (device's internal storage). If the files you try to flash are signed, but you still can't load them, then it means, you have corrupted memory. With this, go to service, they could try to replace UFS chip with another one. From what I can see, your bootloader is locked, so try to unlock it and then flash the firmware, maybe this will work.