I thin its bricked - G 2014 Q&A, Help & Troubleshooting

I have custom ROM 5.x.x pacman edition I think, I pressed factory reset or something like this from settings. It was having problem because I didnt have gaps. I flashed gaps, but after this the phone is stucked at bootloader. My phone is xt1068 but pc doesnt recognize it.

Now I think I have even bigger problem I was playing with the custom recovery and wiped all the data on sdcard folder. The PC recognize Titan Fastboot device or something like this. Is it possible to transfer to sd card new rom using other device, and then use the sd card on the Moto G?

Can you access twrp recovery?

I can access philz recovery.
Edit: mfastboot has access but it gives error when mfastboot update retail.zip, "Failed to load"... when mfastboot devices it says, ZX1D22D9T8 fastboot. Gives error when trying to flash twrp recovery too.
Edit 2: target max-sparse-size: 256MB
error: cannot load 'twrp.img': No error after trying.

ffup57 said:
I can access philz recovery.
Edit: mfastboot has access but it gives error when mfastboot update retail.zip, "Failed to load"... when mfastboot devices it says, ZX1D22D9T8 fastboot. Gives error when trying to flash twrp recovery too.
Edit 2: target max-sparse-size: 256MB
error: cannot load 'twrp.img': No error after trying.
Click to expand...
Click to collapse
Then flash latest twrp and then ROM+gapps.
Dont wipe anything with fastboot.
You have to unzip the file and mfastboot every file inside.

It worked but after I rooted with kango root then ota update, the phone reboot into stock recovery and it says no command.

Fail don't use kingo.
To root just flash SuperSU.
Check the return to stock guide follow all steps.
Flash twrp then flash SuperSU.
Stick to the proven guides
Pd. I think stock recovery is always empty there is some kind of key combination to bring up the command

Related

Factory reset won't finish and keeps trying to erase in a loop.

I did a factory reset from within the settings of the phone, it shows the erasing android and then flickers with and image of an android with triangle. Does this several times and then just stops on the android with red triangle. I can get into stock recovery, tried resetting from there but same thing happens. Also, if I just leave the phone it reboots and then tries to erase and then I get the same loop of it trying and failing.
Any ideas how to fix this? Phone is on the stock 5.0 rom and I have the pure edition.
Thanks
Raistlin1 said:
I did a factory reset from within the settings of the phone, it shows the erasing android and then flickers with and image of an android with triangle. Does this several times and then just stops on the android with red triangle. I can get into stock recovery, tried resetting from there but same thing happens. Also, if I just leave the phone it reboots and then tries to erase and then I get the same loop of it trying and failing.
Any ideas how to fix this? Phone is on the stock 5.0 rom and I have the pure edition.
Thanks
Click to expand...
Click to collapse
I would get into bootloader mode and reflash the system.img.
JulesJam said:
I would get into bootloader mode and reflash the system.img.
Click to expand...
Click to collapse
I am having a hard time trying to flash system.img. I found the system.img for my rom version and tried using ms fast boot v2 but it just hangs in the command window. I have installed the moto drivers and computer recognizes phone when it's in fast boot mode.
I even tried using someone's toolkit to return completely stock u rooted 4.4 but that doesn't work either.
Been reading tons of threads on here but can't seem to get it to flash.
Raistlin1 said:
I am having a hard time trying to flash system.img. I found the system.img for my rom version and tried using ms fast boot v2 but it just hangs in the command window. I have installed the moto drivers and computer recognizes phone when it's in fast boot mode.
Click to expand...
Click to collapse
Are you flashing a single file system.img or sparsechunks? Do you have mfastboot version 2?
Also, you can install Motorola Device Manager on your computer and when your phone is connected in fastboot mode, run MDM and see if it detects it.
JulesJam said:
Are you flashing a single file system.img or sparsechunks? Do you have mfastboot version 2?
Also, you can install Motorola Device Manager on your computer and when your phone is connected in fastboot mode, run MDM and see if it detects it.
Click to expand...
Click to collapse
System img is a single file, I also have a zip that has sparse chunks but haven't tried them. I am pretty sure I downloaded version 2 of mfastboot.
MDM saw my phone and said it had the most recent version.
Raistlin1 said:
System img is a single file, I also have a zip that has sparse chunks but haven't tried them. I am pretty sure I downloaded version 2 of mfastboot.
MDM saw my phone and said it had the most recent version.
Click to expand...
Click to collapse
I would try flashing the sparsechunks if you can't flash the single file image.
JulesJam said:
I would try flashing the sparsechunks if you can't flash the single file image.
Click to expand...
Click to collapse
Tried them using fastboot and only the first sparsechunk worked, they rest gave some error about bootloader.
I then tried in the mfastboot folder I created and it just hangs saying waiting for device, that's why I tried using fastboot.
I am really screwing myself, now while in bootloader and I try to boot or recovery I get failed to validate. Never had these problems flashing my N5, oh well.
Raistlin1 said:
Tried them using fastboot and only the first sparsechunk worked, they rest gave some error about bootloader.
I then tried in the mfastboot folder I created and it just hangs saying waiting for device, that's why I tried using fastboot.
Click to expand...
Click to collapse
How large is your mfastboot? It should be 521KB. If it is smaller than that, you don't have the right one.
What was the bootloader error?
Also now that you have flashed 1 sparsechunk, try MDM again.
You also can try flashing the 4.4.4 system.img if you can find it and then run MDM again b/c it will try to update you.
JulesJam said:
How large is your mfastboot? It should be 521KB. If it is smaller than that, you don't have the right one.
What was the bootloader error?
Also now that you have flashed 1 sparsechunk, try MDM again.
You also can try flashing the 4.4.4 system.img if you can find it and then run MDM again b/c it will try to update you.
Click to expand...
Click to collapse
I am getting bootloader failed to erase partition, failed remote failure.
MDM says phone is on latest version. mfastboot is the size you stated.
Raistlin1 said:
I am getting bootloader failed to erase partition, failed remote failure.
Click to expand...
Click to collapse
This happened to others. One guy had an unlocked bootloader and TWRP installed as recovery and was able to format the data partition through TWRP and that solved the problem for him:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-fastboot-flash-img-failed-t3098727
Can you get into recovery from the bootloader mode? I would get into recovery and wipe cache and then do a wipe data/factory reset and see what happens.
JulesJam said:
This happened to others. One guy had an unlocked bootloader and TWRP installed as recovery and was able to format the data partition through TWRP and that solved the problem for him:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-fastboot-flash-img-failed-t3098727
Can you get into recovery from the bootloader mode? I would get into recovery and wipe cache and then do a wipe data/factory reset and see what happens.
Click to expand...
Click to collapse
I will check out that thread, thanks. I cannot get into recovery from bootloader because it reboots into the erasing android which fails and then I get android with triangle and then I can get into recovery. But wiping cache and factory resetting from there does nothing, it reboots into the erasing android and then it fails to erase again.
Raistlin1 said:
I will check out that thread, thanks. I cannot get into recovery from bootloader because it reboots into the erasing android which fails and then I get android with triangle and then I can get into recovery. But wiping cache and factory resetting from there does nothing, it reboots into the erasing android and then it fails to erase again.
Click to expand...
Click to collapse
Can you reflash stock recovery?
Your bootloader is locked correct?
JulesJam said:
Can you reflash stock recovery?
Your bootloader is locked correct?
Click to expand...
Click to collapse
Reflashing recovery fails like systemail and my bootloader was unlocked prior to all of this happening.
Any way I can flash TWRP in the state I am in?
Raistlin1 said:
Reflashing recovery fails like systemail and my bootloader was unlocked prior to all of this happening.
Any way I can flash TWRP in the state I am in?
Click to expand...
Click to collapse
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
JulesJam said:
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
Click to expand...
Click to collapse
I am spent, going to bed and will pick up again tomorrow. Thanks for helping out.
JulesJam said:
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
Click to expand...
Click to collapse
Tried fastboot boot twrp.img but it won't boot, then tried flashing using fastboot and mfastboot but twrp won't install. Nothing will finish installing, tried flashing everything I can but it keeps failing.
Got the 4.4 image and started with flash partition gpt.bin but got bootloader failed to write primary GPT, bootloader failed to progra partition table, failed remote failure.
On phone I see incomplete boot image for booting, mismatched partition size (recovery). MDM sees my phone and says it is on the current version but I cannot get out of this factory erase looping. Nothing is flashing successfully, I remember seeing something about RSD Lite, will that help me in any way?
Thanks
Raistlin1 said:
Tried fastboot boot twrp.img but it won't boot, then tried flashing using fastboot and mfastboot but twrp won't install. Nothing will finish installing, tried flashing everything I can but it keeps failing.
Got the 4.4 image and started with flash partition gpt.bin but got bootloader failed to write primary GPT, bootloader failed to progra partition table, failed remote failure.
On phone I see incomplete boot image for booting, mismatched partition size (recovery). MDM sees my phone and says it is on the current version but I cannot get out of this factory erase looping. Nothing is flashing successfully, I remember seeing something about RSD Lite, will that help me in any way?
Thanks
Click to expand...
Click to collapse
RSDLite will just use mfastboot to flash. You definitely CANNOT downgrade the partition table - it would leave you with a bootloader partition table version mismatch. So don't attempt that.
You are on the 5.0 bootloader (60.11) correct? If so, did you try flashing the 5.0 partition table (gpt.bin)?
Is your device recognized when you are in recovery and you type in the commad:
adb devices
JulesJam said:
RSDLite will just use mfastboot to flash. You definitely CANNOT downgrade the partition table - it would leave you with a bootloader partition table version mismatch. So don't attempt that.
You are on the 5.0 bootloader (60.11) correct? If so, did you try flashing the 5.0 partition table (gpt.bin)?
Is your device recognized when you are in recovery and you type in the commad:
adb devices
Click to expand...
Click to collapse
As of now I can only get into fastboot mode, I don't believe the phone can even cycle through trying to boot any more. I tried rebooting from fastboot mode but there was an error and it failed.
I tried finding the exact image for 5.0 but I was only able to find the thread that had system, recovery and boot. Do you know a link to find the 5.0 partition table?
Raistlin1 said:
I tried finding the exact image for 5.0 but I was only able to find the thread that had system, recovery and boot. Do you know a link to find the 5.0 partition table?
Click to expand...
Click to collapse
http://www.graffixnyc.com/motox.php
JulesJam said:
http://www.graffixnyc.com/motox.php
Click to expand...
Click to collapse
Downloaded the 5.0 file from there, started flashing those files and it worked up until recovery, then I got the same bootloader message I was getting previously. Tried them over again and they all failed.
When in recovery adb devices starts the daemon and then says list of devices attached but I don't see anything after that.
I think it is fubar`d, going to have to file a warrant claim or use the moto care I purchased.

Trying to ROOT my MotoG on Marshmallow

Hi to all, I had some problems with the battery life on my MotoG (2nd gen) running Lollipop and after a few tries I decided to wipe anything and flash the stock Marshmallow image.
First, I downloaded this image
XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34_cid7_CFC.xml.zip
and flashed correctly, step by step, as wrote here:
http://forum.xda-developers.com/showthread.php?t=2542219
I also downloaded this "Universal MotoG Toolkit" from here:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
But it doesn't work as it should.
For example, if I connect the device and say to "Rebbot to Recovery from Phone" the Phone just reboot, not in recovery.
Also I found out that a new "Warnning bootloader unlocked" screen appears now, on startup.
Then, I tried to flash TWRP into recovery to Root my device but it keeps going on error "Mismatched partition size", any TWRP I try to flash (2.8.6.0,3.0.0.1).
Also, after this error, If I try to "normal powerup" from Fastboot, I have another error "UTAG flashfile configured as fastboot" so no normal powerup.
What I have to do to power up is flash again motoboot with this command:
fastboot flash motoboot motoboot.img
andf then
fastboot restart
And so, the phone restarts normally.
What's wrong with this?
Well this was happening to me and then instead of going for fastboot restart,, i gone to recovery and then its done ...
How go to recovery?

Solved with Corrections: Unable to flash TWRP, Failed (Remote: command not allowed)

Hi,
I just purchased a used Xperia Z1 C6903 and I am trying to put the latest Nougat Resurrection Remix on it. I need to get TWRP going first which I got stuck at trying to flash it.
I was able to get the phone downgraded to 14.1.G.1.534 using flash tool (ver 0.9.24.3). I did this following the guide here https://forum.xda-developers.com/showthread.php?t=2439328.
I was able to root it using Kingoroot.
I was able to unlock the bootloader using flashtool. Using *#*#7378423#*#*, the phone now reports Bootloader Unlocked: yes. See attached screenshot.
The part that I got stuck at is trying to flash TWRP in Fastboot. The command lines and error are below. The main error being "FAILED (remote: Command not allowed)"
I don't have an option in developer's options to "Unlock OEM bootloader". I read some other Xperia users being able to fix this problem by checking this.
I am running Windows 8.1. I am relatively sure that my drivers are correct. I had gotten a "drivers too old" error before in Flashtools but I was able to correct it by reinstalling new drivers.
I tried having debugging checked and unchecked before going into Fastboot and made no difference.
Tried both twrp-2.8.7.0-honami and twrp-3.0.2.0-honami with no success. Tried shortening file name to trp.img with no success.
Tried different 2 different adb files around the web with no success.
I read somewhere someone mentioned briefly that TWRP can be flashed using Flashtools. Is that true? I wasn't able to find a full guide for it.
Any help would be appreciated!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery trp.img
target didn't report max-download-size
sending 'recovery' (13672 KB)...
OKAY [ 0.433s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.439s
Well I was able to get TWRP on there by installing the XY Dual Recovery. The problem with it is that the Resurrection Remix's installation instruction says to use TWRP 3x or higher. TWRP on XY is only at 2.8.7.0. I couldn't find a TWRP 3x flashable zip file for Honami and TWRP wouldn't flash TWRP 3x IMG file I found. Fastboot is still giving me the same Command Not Allowed error.
Any ways, I went ahead and flashed RR with 2.8.7.0. When I tried to flash GAPPs after it says there is insufficient space. I have at least 9GB+ internal storage. So not sure what the deal is there.
I also lost Dual Recovery and root after first RR boot.
Looking into getting re-rooted and reinstalling XY Dual Recovery now.. And then flashing GAPPS after.
Anyone know what the consequences are for installing RR with a lower rev of TWRP?
So the RR Rom does have root but it just doesn't have apps root. Only ADB root. I cant flash the su add on from Lineage's site since I lost recovery. I ended up FTF back to stock and then reflashed everything, the ROM then pico version of GAPPs (pico worked) and then the su addon. The su addon had an error when flashing in TWRP.
Any ways, long story short the whole thing didn't work. Still stuck with RR Without recovery. Su addon didnt work from the flash. And for whatever reason my SIM is not detected and I lost my IMEI in RR. I read that this is a known issue with C6902 but I have the C6903 and I had confirmed this through the service menu before ROM flash. Maybe problems with flashing RR without the latest TWRP.
The Command Not Allowed is still an issue that I dont know how to resolve. So I still can't flash newer version of TWRP.
Any help would be appreciated....
I guess I will try to find a ROM that 's compatible with TWRP 2.8.7.0.
OK! I figured out what the Command Not Allowed problem is!
I've been following the flash guides from a few websites. And they all reference this syntax for flashing TWRP.
Fastboot flash recovery twrp.img.
This syntax didn't work for me. All those websites properly copycat each other.
That syntax is either incorrect or just didnt work for my setup for some reason. I kept searching for ways to flash TWRP and found another website that uses a different syntax. I gave it a go and TWRP flashed right away. This is the syntax that worked for me.
Fastboot flash boot twrp.img
At least that part of the problem is resolved.
Even after flashing RR with TWRP 3.0.20, the SIM/IMEI is still not showing. Recovery is still lost on first boot. Reinstalling TWRP on top of RR causes RR to not boot any more. I will have to look into the RR thread to investigate more.
I will mark this thread as Solved for the Command Not Allowed.
Crossed out everything cause that was not the correct solution. Striked them out to keep them as part of the troubleshooting steps history.
Oops duplicated post.
OK! So it looks like I have to correct myself here on my previous solution.
My solution from earlier for using "Fastboot flash boot twrp.img" is incorrect apparently. Don't use this!
That was the reason why my TWRP was lost after RR boot. The recovery partition comes after the boot and system partition. By flashing the recovery into boot, it screws up the order.
Nevertheless, the Command Not Allowed was still a problem if I tried to use "Fastboot flash recovery twrp.img"
Any ways I was still looking into this problem and started looking into the boot.img stuff and saw someone uses this command line: "fastboot erase boot". This helps someone being able to flash a boot.img when the user was having the Command not Allowed problem trying to flash a different img for the boot partition.
This gave me an idea to try and use "fastboot erase recovery".
I gave it a try and I was able to use "fastboot flash recovery twrp.img" afterwards! It was done in a second.
Then I went through the normal steps of flashing RR and TWRP stayed this time. So now all is good with everything!
Any ways to recap, my full steps used for my RR Installation:
1. Flashtool to flash an Android 5.1.1 stock rom. I used C6903_14.6.A.1.236_1276. (obtained through Flashtool, Xperifirm) Your phone has to run in 5.1.1 for the SIM and IMEI to work in RR. Don't need to flash modem.zip, that's for C6902 only.
2. Fastboot flash erase recovery
3. Fastboot flash recovery twrp.img
4. Follow instructions to flash RR normally.
5. Resize system partition size (for flashing GAPPS micro size or larger).
6. Flash GAPPS.
7. Flash su addon from Lineage's website to allow root for apps and ADB.
I hope this helps someone with similar problems in the future. Thanks to those who stop in to see me ramble to myself about silly stuff
I had the same error message and was able to successfully flash using the phone and the Android Studio Emulator app.
I was already rooted and had an unlocked bootloader.
I tried this solution and it said error: cannot "recovery": No such file or directory LOL even though it's right here and I use it all the time..........I just can't figure it out.

Troubles reinstalling TWRP [Failed to load/authenticate boot image: Load Error]

I dirty flashed a new version of xiaomi.eu stable build, and it caused TWRP to uninstall itself.
Whenever I hold power on and volume up it just goes to fastboot.
Now I tried reinstalling TWRP like I've done many times before, but it keeps throwing an error. The error I get is when trying to boot without flashing the img. When I do this, I get the error:
Code:
fastboot boot TWRP.img"
downloading 'boot.img'...
OKAY [ 1.609s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.675s
Anyone gotten any ideas on what could be going on here? I'm scared to try anything as my phone currently works, but I need TWRP back to update my phone to a different versions and to install the clock mod again.
Thanks!
Got it to load once, but now back to square one. Throwing same error.
Now when running the command fastboot reboot recovery it's saying
Code:
fastboot: usage: unknown reboot target recovery
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Try on a computer with a USB 2.0 port, or a different usb cable, had the same issue once
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
I have the same error. How can I fix this pls?
MrkoZino said:
I have the same error. How can I fix this pls?
Click to expand...
Click to collapse
Flash the latest official rom then start all over again. Follow the post above you about miflash.
Hello, I've had the same problem, then flashed latest dev rom via MiFlash and it booted, but now after I flash any custom ROM in TWRP i have this issue again and need to reflash chinese ROM. How can I flash any custom rom?
i'm stuck in the same issue. stuck in fastboot and it would not load recovery. any fix?
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
greendra8 said:
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Click to expand...
Click to collapse
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
DJPlaya said:
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
Click to expand...
Click to collapse
long time ago now. but i remember at one point having to flash the stock firmware using the mi unlock tool. i also remember trying every single version of twrp and rom until one finally worked. sorry i can't help much but i believe that's how i eventually fixed it.
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Marihot said:
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Click to expand...
Click to collapse
Where do you get these .img files?
iconoclasthero said:
Where do you get these .img files?
Click to expand...
Click to collapse
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Marihot said:
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Click to expand...
Click to collapse
Please tell the details for this method
greendra8 said:
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
Click to expand...
Click to collapse
BROOOOOOOOOO HAHAHAHAHAHA I LITERALLY JUST READ YOUR COMMENT AND 10 SECONDS LATER I FLASH THE ROM WITH "CLEAN ALL AND LOCK" Im a f-king dumb bro
Marihot said:
你好,我也经历过同样的事情。
这个方法帮助我摆脱它。
尝试使用 adb 从要在 hh 中安装的 rom 中重新刷新一些文件映像。
将下面的文件从 rom 映像复制到 adb 文件夹
1.system.img(adb >> fastboot flash system system.img中的命令)
2. boot.img(adb 中的命令,如#1,更改 img 文件的名称)直到 #6
3. 供应商.img
4.dtbo.img
5. 自定义.img
6. 杂项.img
7. 现在用adb刷twrp/recovery.img(选择twrp与你要安装的rom兼容)
8. adb 的“fastboot boot recovery.img”
9. twrp刷入rom
Click to expand...
Click to collapse
Thank you, brother
try fastboot set_active a
or fastboot set_active b

accidentally wiped complete device - what to do now?

after unlocking, falshind twrp and wipeing the complete device I can't do anything at all now.
I can boot in twrp or to fastboot but the device can't be found in either modes.
I tried to mount the sd card or MTP but they don't do anything either. Also tried to sideload onto the device but of course it doesn't work.
I'm all out of ideas what to do now. Anybody got some ideas what I could try?
Extract system from fastboot firmware and flash in fastboot with command fastboot flash system system.img after flashing system flash twrp and install rom or simply just flash fastboot firmware with Miflash
yes, thank you very much. this was the trick!
you get everything bacc up and running ok?

Categories

Resources