Develop Bugs

[Q] Nexus 7 stuck in Fastboot

I was loading up my Nexus 7 (2013) with the Project L rom and ran into a problem. At the end of the install, I got an error that it could not erase the cache. I can boot into Bootloader but nothing else. It won't boot into recovery or launch the system OS. When I try to launch the system OS, I just get that updating animation that sits there for hours. Fastboot does recognize the device though, but when I try to do a fastboot erase of a partition, it just hangs. Anyone know how I can get out of this?

Try a complete reflash of 4.4.4 or 5 from fastboot.
Sent from my Nexus 7 using Tapatalk

ritchea said:
Try a complete reflash of 4.4.4 or 5 from fastboot.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I tried the process again. Whether I am trying to erase a partition, re-format a partition, or flash a partition, I get write errors. It is almost as if the rom is write-protected or something. It will copy partition images to whatever partition the bootloader is using, but just won't write them to the proper partitions.

So you are saying when you give the command [fastboot flash system system.img], you get a write error. I'm obviously not an expert, but i thought a new flash would do a complete wipe and create new partitions. If that is not the case (meaning flashing requires that partitions be in place), then you need someone who can tell you if/how to code for partitions or send it in for repair.
Is adb working? If so, you might want to try Wug's toolkit. (see android development).
When you try to start recovery from fastboot, do you get Andy with the red triangle, or what?
Sent from my Nexus 7 using Tapatalk

Check if your Android SDK is up to date

ritchea said:
So you are saying when you give the command [fastboot flash system system.img], you get a write error. I'm obviously not an expert, but i thought a new flash would do a complete wipe and create new partitions. If that is not the case (meaning flashing requires that partitions be in place), then you need someone who can tell you if/how to code for partitions or send it in for repair.
Is adb working? If so, you might want to try Wug's toolkit. (see android development).
When you try to start recovery from fastboot, do you get Andy with the red triangle, or what?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
ADB doesn't find the device any longer, although it did when I started the process. So I am left with using Fastboot. When I try to go into recovery, the screen goes black, then I get the Google logo, and it just sits there. When I try to launch into the system, I get they Andy lying down with the rotating geometric shape in his belly - forever. All that seems to work is the bootloader, and it's not really working. This is the kind of results that I am getting.
Code:
C:\Users\Daniel\Downloads\Nexus 7>fastboot devices
07b8be03 fastboot
C:\Users\Daniel\Downloads\Nexus 7>fastboot flash recovery openrecovery-twrp-2.8.
0.1-flo.img
sending 'recovery' (7878 KB)...
OKAY [ 0.254s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 90.015s
C:\Users\Daniel\Downloads\Nexus 7>fastboot flash bootloader bootloader-flo-flo-0
4.04.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 1.067s
C:\Users\Daniel\Downloads\Nexus 7>

What happens when you do [fastboot reboot recovery]? I wish I understood more about this. First, lying down Andy with the red triangle is the recovery "pre" screen for stock recovery. The fact that system reboots to it may indicate you have no OS. Once you get to that screen, have you tried to get to the next screen (holding vol+/- and power at the same time for a few seconds)? It's tricky and directions say vol+ plus power, but it seems I've always had to press vol in middle. I've read it both ways. Try this first.
[When Stock Recovery starts you will see the Android fallen down screen
To bring up the Recovery menu
Power+VolUp to show recovery menu
Must be this sequence Press/Hold Power, THEN Press/Release VolUp, release Power]
Although I've found many instances of the write write failure you describe, no definitive answers. It does seem that Wug's Toolkit is worth a try. I read the following on his site. I realize it's about unlocking, but the point is you don't need adb to run commands from fastboot.
"WugFresh Mod Carey Parks • 4 days ago
You don't need to be connected via ADB (on with usb-debug enabled) to unlock. You just be connected via FASTBOOT (bootloader mode). Just use the "Unlock" button, and follow the instructions it gives you to MANUALLY boot your device into bootloader mode, then proceed from there. Its fine that your device is messed up.. you just have to get the bootloader unlocked. Once its unlocked you can use "Flash Stock + Unroot" with softbrick/bootloop mode to get your device back to normal. Cheers!"
Using the toolkit from fastboot without adb might help. (In fact, I didn't know this.) He further brought up these commands: You could also try to issue the commands (NRT advanced utilities > launch cmd prompt):
fastboot format system
fastboot format data
fastboot format cache
Of course this clears everything. But from this point, you could try the "Flash Stock+Unroot" step on the first page of the toolkit.
Have you tried to flash a totally different set of files (like the official 4.4.4 decompressed and placed into the fastboot folder)?
It is possible that your SD card has become corrupted. I'm pretty sure you can't issue any mount commands without adb so you can't set the card to write.
For the 15-20 minutes it will take to set up the toolkit and use it (it has to download files for your device, too). it may be worth the effort. Also, Wug is very good about helping. If you can provide him with a copy of what's happening (while using the toolkit), he will try to help. He really understands this stuff. If you're a "toolkit snob" (my term for those who deny usefulness of toolkits), then ignore that suggestion. You already understand how to use fastboot (which is why some say don't use toolkits). My personal experience is that the kit has helped me get out of bootloops a few times.

ritchea said:
What happens when you do [fastboot reboot recovery]? I wish I understood more about this. First, lying down Andy with the red triangle is the recovery "pre" screen for stock recovery. The fact that system reboots to it may indicate you have no OS. Once you get to that screen, have you tried to get to the next screen (holding vol+/- and power at the same time for a few seconds)? It's tricky and directions say vol+ plus power, but it seems I've always had to press vol in middle. I've read it both ways. Try this first.
[When Stock Recovery starts you will see the Android fallen down screen.
Click to expand...
Click to collapse
The Android logo I get when trying to boot into the OS is the animated one with the spinning wire-mesh ball thingy that one generally sees when the OS is updating itself. It just doesn't stop. I'll give the toolkit thing a try, but am about to head out for the day. Won't have a chance until later tonight or tomorrow.

djeaton said:
The Android logo I get when trying to boot into the OS is the animated one with the spinning wire-mesh ball thingy that one generally sees when the OS is updating itself. It just doesn't stop. I'll give the toolkit thing a try, but am about to head out for the day. Won't have a chance until later tonight or tomorrow.
Click to expand...
Click to collapse
Oh, I understand on the Andy. OK. Have a great day.
Kinda weird-- http://forum.xda-developers.com/showthread.php?t=2917463different circumstances but same problem. No one responding there, either.
I don't know why this would work when wug's does not, but some claim it did http://forum.xda-developers.com/showthread.php?t=2381582. You would download, extract, click Dead_Nexus7.bat file and run from fastboot.

H815: No recovery mode (bootloader unlocked, TWRP 3.0.1 installed)

Hey guys,
I'm trying to root my G4 loaded with MM 6.0. I cannot get into Recovery Mode no matter what I do.
I have tried the key combo (power+down, etc) - it does nothing. If I use adb reboot recovery, I just get the dead Android guy with the exclamation in red triangle. (which is perhaps a hint as to why the key combo doesn't work.)
I followed steps to unlock the phone's bootloader via LG's dev site (success) and I've installed TWRP 3.0.2-0-H815.img but I can't get into Recovery mode. **The phone continues to work fine** and I can get it into Download Mode.
After having no success with TWRP, I thought, f*ck it, since I've gone this far, let's go with CyanogenMod instead of stock, so I installed cm-13.0-20160415-NIGHTLY-h815-recovery.img
I was also able to use adb to push CM 13 (nightly build 20160415) and Gapps (arm64 6.0 20160416) successfully to phone, but it's obviously no use since I can't get to Recovery Mode.
I'm wondering if someone can please suggest a solution or at least a next step.
When I use fastboot flash recovery twrp-3.0.2-0-h815.img it takes 0.718s 'send recovery' and 0.282s 'writing recovery'.
[solved - probably Win10's no-ask driver update policy] New problem: After going back to TWRP, fastboot devices shows nothing and my device is showing up in Device Manager as LGE Mobile USB Composite Device, whereas I specifically changed it from the LG drivers I installed to Android ADB drivers. The device doesn't even list the Android ADB driver as an available option now. WTAF?!? Maybe this is more Win10 driver-auto-update malarkey?
OS = Win10x64
Kernal = 3.10.84
Build number = MRA58K
Software version = V20d-EUR-XX
Developer options are available
USB debug is enabled
OEM unlock is enabled
I'm using the stock USB cable
Additional question - tutorials say to back up NVRAM and IMEI before doing anything risky, but I can't get those without root. How does this make sense?
EDIT: NOTE: You should be using the arm64 version of Gapps on LG G4 H815.
Thank you very much to everyone who stops in to take a look at my questions.
All the best,
Dax.

Hi
I had the same problem with Win 10 not seeing my H815 properly (same device name in Device Mgr as yours) I reverted to the older Lge drivers, 4.0.3 if I remember correctly and the phone showed up properly and I was able to use LG UP to update/downgrade etc.
Like you I have since tried to install TWRP but I cannot new get root with Kingroot 480 although it worked previously on V81520D it does not now.
Sent from my iPad using Tapatalk

try fastboot boot recovery twrp-3.0.2-0-h815.img
then tap IMG instead of ZIP (bottom) -> install img and flash the twrp img

Hi Stransky, I reinstalled the adb-setup-1.4.2.exe package which also contains drivers and now ADB will see the phone (which is good), but Fastboot still says waiting for devices (bad). Thanks!
I also changed the default driver from 'LGE Mobile ADB Interface' to 'Android ADB Interface' (as per tutorial instructions).
Hi Bender_007, thanks so much for the tip, I'll try it as soon as I can get Fastboot working again. Cheers!

Okay, so I learned ADB is for Android or Recovery mode, Fastboot is for 'HBOOT' (bootloader) mode.
As expected:
adb devices returns "List of attached devices: LGH81579d3bc56 device".
If I use the command adb reboot-bootloader, phone restarts in bootloader mode.
Then adb devices does nothing, but fastboot devices returns "79d3bc56 fastboot".
When device is in bootloader mode, it shows up in Windows Device Manager as 'Marshall London Bootloader Device'.
Bender_007, the command "fastboot boot recovery twrp-3.0.2-0-h815.img" doesn't work. It's invalid syntax. "fastboot flash recovery twrp-3.0.2-0-h815.img" works as per original post.
Any other suggestions?

Hm, put the twrp inside the same folder where your fastboot and adb are. Then start command prompt in the very same folder and type fastboot boot twrp... And that should be it. That means if everything is normal and the system is bootable.
Pardon, fastboot boot twrp(whatever the name is)
Not: fastboot boot recovery twrp..
Sent from my LG-H815 using Tapatalk

Hi Bender_007, that's exactly where the .IMG files are already. No dice. :/

May I see this via teamviewer please ? (teamviewerQS via private message)
I´ll gladly help you (if it´s in my possibilities ofc)
@daxliniere
EDIT: 21.04.2016 - we have fixed this, had a nice talk, almost a beer. It´s nice to meet new cool people , keep it up my friend

I am stuck probably on the same issue with win10. It seams like I was able to flash twrp recovery but I can't enter it. Already factory reseted it 3 times while trying to enter into custom recovery.
Any advices what to do?

madik_ said:
I am stuck probably on the same issue with win10. It seams like I was able to flash twrp recovery but I can't enter it. Already factory reseted it 3 times while trying to enter into custom recovery.
Any advices what to do?
Click to expand...
Click to collapse
The best solution there is:
1. put adb, fastboot into a directory (let´s say c:\adb), put the twrp-3......img into the same folder
2. adb reboot bootloader
3. open command prompt, cd c:\adb
4. fastboot boot twrp-3.....img (where twrp-3....img is the actual name of the twrp img)
it will boot to twrp, now you can either copy the twrp img to the phone and flash it(it will ask where to flash - tap on recovery--don´t tap on boot)
You might have to tap on zip/img toggle to enable img flashing first
should you need more help just post in here

Yep that did the trick. thank you! I was able to load recovery with the fastboot boot twrp.. but didnt realize that i can install it by the loaded twrp lol. Now I can finally confirm 2x YES and it gets me into TWRP. thanks again!

Can I make one little tip for everyone else? Follow this guide to the end: http://www.technobuzz.net/unlock-lg-g4-bootloader/
Step 1 is the easiest way to install adb, fastboot and drivers in one go.

Same problem here:
Software version = V20d-EUR-XX, Developer options are available, USB debug is enabled, OEM unlock is enabled
I can boot into recovery via bootloader: fastboot boot twrp-3.0.2-0-h815.img but:
1. had I to allow to modify system partition modifications?
2. how can I boot in recovery from system? with adb I always get the red-triangle Android on its back und with hardwarekeys after shut down the devise, I#m coming to stock recovery: factory restet no/yes

1. Yes
2. While you are in twrp just flash the twrp IMG again via twrp itself. It has the option to flash img instead of zip.
Poslano sa mog SM-G930F koristeći Tapatalk

thx, a lot...
Now im running a full system update to exsdcard and afterwards I try to "re-"install the twrp in twrp-applikation.
When i boot into recovery at the moment, the "modify-dialog" is away...
But I will see after "re-"install the twrp how it works...
---------- Post added at 03:48 PM ---------- Previous post was at 03:00 PM ----------
UPDATE:
Did it, worked!!!
on system: "adb reboot recovery" leads to twrp!
there are no hardware-key-solutions to get to recovery...
with the hardware-keys (after shutdown -> power + vol down -> release power for a second when LG-logo pops up) I get to the factory reset no/yes dialog...

On the factory reset choose yes twice. Normal for lg
Poslano sa mog SM-G930F koristeći Tapatalk

I got nervous to choose yes the second time....

sejmand said:
I got nervous to choose yes the second time....
Click to expand...
Click to collapse
Install Quick Boot from the Play Store,you can boot straight to Twrp with it

fastboot erase recovery
fastboot flash recovery xxx.img (xxx=twrp.img)

Hello,
I am still struggling with my h815 on 7.0:
I am getting the error sign with "no commands".
I cannot force it to boot to the twrp but I can flash it (unknown command):
HTML:
student:~/Downloads$ sudo fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (32992 KB)...
OKAY [ 1.106s]
writing 'recovery'...
OKAY [ 0.931s]
finished. total time: 2.037s
student:~/Downloads$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.104s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.121s
using ubuntu 16.04.
Thanks for your feedback in advance.

Oppo Find 7 V1.2.8i Won't boot into TWRP recovery after booting into stock recovery

long story short, incase any of these are the reason why my phone can't get twrp recovery.
History:
Around 3-4 months ago I updated my phone to Color os 2.0.8i(if not mistaken). Not sure if I did root my phone or not. My phone screen broke, and touch screen spoiled, not using it until I repaired it few days ago. After repair decided to use CM13 and took me awhile to figure out how to flash TWRP and took me quite sometime to root my phone. After successfully rooting my phone, I started to install CM13 snapshot bcos i tot the nightly is not stable. But it failed. My phone can't turn on and can't go to recovery. Keeps boot to fastboot. Figured out i need to use some code like fastboot oem unlock(can't really rmb if this was the code I used) then flash my recovery again and my recovery works. But my phone still can't turn on. I use TWRP recovery to flash the same rom again to see if it works this time, but no it doesn't. i think i did try the CM13 nightly rom but it doesn't work too so i searched a lot about how to install CM13 on Find7. This link(http://forum.xda-developers.com/fin...0-marshmallow-unofficial-cm13-oppo-7-t3227311) said that Color OS 2 &2.1 needs to flash Color OS 1.2.8 and i did it. I did not flash the stock recovery. I use fastboot boot stockrecovery.img. Then, I install the stock rom using the stock recovery. The link says let it boot, and after that reboot back to TWRP recovery. After successfully booting into Color OS 1.2.8i, I switch off my phone and press down button + power button but the stock recovery came out. From that onwards i keep trying to flash TWRP recovery to my phone but it failed. I used fastboot flash recovery twrp.img and press volume down button + power button, fastboot boot twrp.img, fastboot erase recovery and fasboot flash recovery twrp.img and fastboot boot twrp.img all that doesn't work even the cmd said okay twice. All it does just either boot up the oppo logo and turn back off and turn on again with the logo and turn on the phone normally. OR it just boot up the stock recovery. I have read it some where that some stock rom will overwrite the custom recovery with its stock recovery so needs to delete some recovery file and edit the updater script. I did it and try to install the rom again after editing, but it failed. I tried installing another 1.2 color os(without editing the inside hoping this rom doesn't have the ability to overwrite the custom recovery) it did tried to install but up to about 40% of the loading bar, it says fail. I tried many times, I even factory reset my phone and try installing again but TWRP just can't be booted.
Problem:
- I can't get to TWRP recovery.
- Without TWRP I can't install custom rom or root my phone
Please help me. I have wasted about 4 days time just to install the CM13...

ron8899 said:
long story short, incase any of these are the reason why my phone can't get twrp recovery.
History:
Around 3-4 months ago I updated my phone to Color os 2.0.8i(if not mistaken). Not sure if I did root my phone or not. My phone screen broke, and touch screen spoiled, not using it until I repaired it few days ago. After repair decided to use CM13 and took me awhile to figure out how to flash TWRP and took me quite sometime to root my phone. After successfully rooting my phone, I started to install CM13 snapshot bcos i tot the nightly is not stable. But it failed. My phone can't turn on and can't go to recovery. Keeps boot to fastboot. Figured out i need to use some code like fastboot oem unlock(can't really rmb if this was the code I used) then flash my recovery again and my recovery works. But my phone still can't turn on. I use TWRP recovery to flash the same rom again to see if it works this time, but no it doesn't. i think i did try the CM13 nightly rom but it doesn't work too so i searched a lot about how to install CM13 on Find7. This link(http://forum.xda-developers.com/fin...0-marshmallow-unofficial-cm13-oppo-7-t3227311) said that Color OS 2 &2.1 needs to flash Color OS 1.2.8 and i did it. I did not flash the stock recovery. I use fastboot boot stockrecovery.img. Then, I install the stock rom using the stock recovery. The link says let it boot, and after that reboot back to TWRP recovery. After successfully booting into Color OS 1.2.8i, I switch off my phone and press down button + power button but the stock recovery came out. From that onwards i keep trying to flash TWRP recovery to my phone but it failed. I used fastboot flash recovery twrp.img and press volume down button + power button, fastboot boot twrp.img, fastboot erase recovery and fasboot flash recovery twrp.img and fastboot boot twrp.img all that doesn't work even the cmd said okay twice. All it does just either boot up the oppo logo and turn back off and turn on again with the logo and turn on the phone normally. OR it just boot up the stock recovery. I have read it some where that some stock rom will overwrite the custom recovery with its stock recovery so needs to delete some recovery file and edit the updater script. I did it and try to install the rom again after editing, but it failed. I tried installing another 1.2 color os(without editing the inside hoping this rom doesn't have the ability to overwrite the custom recovery) it did tried to install but up to about 40% of the loading bar, it says fail. I tried many times, I even factory reset my phone and try installing again but TWRP just can't be booted.
Problem:
- I can't get to TWRP recovery.
- Without TWRP I can't install custom rom or root my phone
Please help me. I have wasted about 4 days time just to install the CM13...
Click to expand...
Click to collapse
You forgot fastboot oem unlock. Also not all twrp versions work. Try and see. Recap: fastboot erase cache, fastboot oem unlock and fastboot flash recovery followed by twrp. img. After that press and hold power and volume down simultaneously and you should be in twrp.

My steps with fastboot oem unlock
tropical cactus said:
You forgot fastboot oem unlock. Also not all twrp versions work. Try and see. Recap: fastboot erase cache, fastboot oem unlock and fastboot flash recovery followed by twrp. img. After that press and hold power and volume down simultaneously and you should be in twrp.
Click to expand...
Click to collapse
Hi, thanks for your reply. It didn't work again. Here is what I did maybe you can see what mistake i made:
1) volume up + power button get to fastboot.
2) plug my phone in to computer
3) right click in platform-tools folder + shift and choose open command window here
4) fastboot erase cache
result
5)******* Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.029s]
finished. total time: 0.029s
i continued
6) fastboot oem unlock
result
7)...
OKAY [ 0.003s]
finished. total time: 0.003s
i continued
8) fastboot flash recovery twrp-3.0.2-0-find7.img
result
9) target reported max download size of 536870912 bytes
sending 'recovery' <10894 KB>...
OKAY [ 0.344s]
writing 'recovery'
OKAY [ 0.163s]
finished. total time: 0.507s
10) i unplug the phone from computer
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.

ron8899 said:
Hi, thanks for your reply. It didn't work again. Here is what I did maybe you can see what mistake i made:
1) volume up + power button get to fastboot.
2) plug my phone in to computer
3) right click in platform-tools folder + shift and choose open command window here
4) fastboot erase cache
result
5)******* Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.029s]
finished. total time: 0.029s
i continued
6) fastboot oem unlock
result
7)...
OKAY [ 0.003s]
finished. total time: 0.003s
i continued
8) fastboot flash recovery twrp-3.0.2-0-find7.img
result
9) target reported max download size of 536870912 bytes
sending 'recovery' <10894 KB>...
OKAY [ 0.344s]
writing 'recovery'
OKAY [ 0.163s]
finished. total time: 0.507s
10) i unplug the phone from computer
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.
Click to expand...
Click to collapse
All steps correct. Try earlier twrp versions. I remember 2.8.6.0 works.

tropical cactus said:
You forgot fastboot oem unlock. Also not all twrp versions work. Try and see. Recap: fastboot erase cache, fastboot oem unlock and fastboot flash recovery followed by twrp. img. After that press and hold power and volume down simultaneously and you should be in twrp.
Click to expand...
Click to collapse
i realise something different this time. i switch off my phone and hold volume down + power button to go to the recovery. Usually it goes to the stock recovery but this time it doesn't it just turn on the phone like just now. it repeat these steps.
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.

tropical cactus said:
All steps correct. Try earlier twrp versions. I remember 2.8.6.0 works.
Click to expand...
Click to collapse
alright thanks i'll go and try

tropical cactus said:
All steps correct. Try earlier twrp versions. I remember 2.8.6.0 works.
Click to expand...
Click to collapse
I tried the 2.8.6.0 twrp. i repeated all the steps. erase cache, oem unlock, flash twrp and hold the volume down + power. this time it shows oppo logo. after awhile at the oppo logo screen, it glitch a little. Then it shows a black screen with light. but there is nothing. I tried to touch the screen nothing seems to happen...
i also tried 2.8.5.0 and it repeat this
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.

ron8899 said:
I tried the 2.8.6.0 twrp. i repeated all the steps. erase cache, oem unlock, flash twrp and hold the volume down + power. this time it shows oppo logo. after awhile at the oppo logo screen, it glitch a little. Then it shows a black screen with light. but there is nothing. I tried to touch the screen nothing seems to happen...
i also tried 2.8.5.0 and it repeat this
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.
Click to expand...
Click to collapse
Well, sorry to hear that. I'm out of ideas.

tropical cactus said:
Well, sorry to hear that. I'm out of ideas.
Click to expand...
Click to collapse
Alright thanks anyway. Hopefully someone out there can help?

ron8899 said:
Alright thanks anyway. Hopefully someone out there can help
Click to expand...
Click to collapse
Have you tried CWM recovery?

tropical cactus said:
Have you tried CWM recovery?
Click to expand...
Click to collapse
I haven't tried cwm yet. Cos i have used twrp on this phone before... wondering why i can't use twrp now...

ron8899 said:
I haven't tried cwm yet. Cos i have used twrp on this phone before... wondering why i can't use twrp now...
Click to expand...
Click to collapse
Try it. It might work. Does the same thing anyway.

tropical cactus said:
Try it. It might work. Does the same thing anyway.
Click to expand...
Click to collapse
i tried. using the X9007_CWM_recovery.img.
OKAY twice.
used volume down + power button.
logo showed up and stuck at the logo for a long time
the 3 buttons(back, home & menu buttons) light up
if i used fastboot boot method, the fastboot screen lightup brightly, and stuck there. and the three buttons light up too...

ron8899 said:
i tried. using the X9007_CWM_recovery.img.
OKAY twice.
used volume down + power button.
logo showed up and stuck at the logo for a long time
the 3 buttons(back, home & menu buttons) light up
if i used fastboot boot method, the fastboot screen lightup brightly, and stuck there. and the three buttons light up too...
Click to expand...
Click to collapse
Okay. Last one. Since you have unlocked bootloader i. e. Fastboot oem unlock, try using flashify from play to install twrp and see if that works. Try a few versions of twrp.
Edit. Go back to stock recovery first and start again. Good luck.

tropical cactus said:
Okay. Last one. Since you have unlocked bootloader i. e. Fastboot oem unlock, try using flashify from play to install twrp and see if that works. Try a few versions of twrp.
Edit. Go back to stock recovery first and start again. Good luck.
Click to expand...
Click to collapse
U mean I should try flashing stock recovery using cmd, after that then I use flashify flash twrp?

ron8899 said:
U mean I should try flashing stock recovery using cmd, after that then I use flashify flash twrp?
Click to expand...
Click to collapse
Yes, so you have a working recovery. Check that it is installed first. Then fastboot erase cache and fastboot oem unlock. Reboot, download flashify and flash twrp. img and then try to enter recovery.

tropical cactus said:
Yes, so you have a working recovery. Check that it is installed first. Then fastboot erase cache and fastboot oem unlock. Reboot, download flashify and flash twrp. img and then try to enter recovery.
Click to expand...
Click to collapse
Alright, I saw two flashify in play. Which one is it? The one with the requires root?

ron8899 said:
Alright, I saw two flashify in play. Which one is it? The one with the requires root?
Click to expand...
Click to collapse
Yes, the one from rashr. Skip all warnings and proceed. Put your twrp.img on sd card first.

tropical cactus said:
Yes, the one from rashr. Skip all warnings and proceed. Put your twrp.img on sd card first.
Click to expand...
Click to collapse
oh.... i can't get my stock recovery work... it always shows half of the reocvery screen only.... and the recovery screen keeps glitch. what should i do?
this is where i download the stock recovery
http://community.oppo.com/en/forum.php?mod=viewthread&tid=17397

ron8899 said:
oh.... i can't get my stock recovery work... it always shows half of the reocvery screen only.... and the recovery screen keeps glitch. what should i do?
this is where i download the stock recovery
http://community.oppo.com/en/forum.php?mod=viewthread&tid=17397
Click to expand...
Click to collapse
Now we know where the problem is. I re-read your post. New LCD screen. Flash this stock recovery. Once you see it can work, then proceed with the erase cache, oem unlock and twrp 3.0.0.0.
The links here: https://drive.google.com/file/d/0B_5WCvt_2elTU0pKR0V1Mm1jWk0/view?usp=sharing
https://drive.google.com/open?id=0B_5WCvt_2elTbmZ5MERKTzVPQTQ
---------- Post added at 06:36 AM ---------- Previous post was at 06:26 AM ----------
Oh, and by the way, CM 13 not compatible with our LCD screen. Omni supports new screen. Read before flashing rom. If not you'll have more problems.
There's a snapshot CM 13 for new LCD in oppo forum. The links are dead but if you ask someone there, they might upload. I've erased mine. Again, there's some requirements there, so read up.
---------- Post added at 06:46 AM ---------- Previous post was at 06:36 AM ----------
community.oppo.com/en/forum.php?mod=viewthread&tid=46578&extra=
Crap, link incomplete. Nevertheless, go to find 7 third party development section. It's all there.

LG G7 - Fastboot bootloop [SOLVED]

After trying to flash Pie my G7 stuck in fastboot mode. Download mode is unavailable so I not can reset the stock ROM.
After it reboots it boots into only to fastboot mode and is stuck in a loop now.
An even bigger problem is that now the bootloader is locked and the unlock.bin file can not unlock the bootloader.
ADB mode is not working!
DOWNLOAD mode is not working!
SYSTEM mod does not work!
There is only FASTBOOT mode that is in the loop
Does anyone have any suggestions?

Prosjak said:
After trying to flash Pie my G7 stuck in fastboot mode. Download mode is unavailable so I not can reset the stock ROM.
After it reboots it boots into only to fastboot mode and is stuck in a loop now.
An even bigger problem is that now the bootloader is locked and the unlock.bin file can not unlock the bootloader.
ADB mode is not working!
DOWNLOAD mode is not working!
SYSTEM mod does not work!
There is only FASTBOOT mode that is in the loop
Does anyone have any suggestions?
Click to expand...
Click to collapse
Try to get into lgup to flash a kdz, if you cant do that you might be SOL

LGUP does not detect phone, download mode is not working

hi
Prosjak said:
LGUP does not detect phone, download mode is not working
Click to expand...
Click to collapse
Please contact me, I can help you recover the device

PjLyTam said:
Please contact me, I can help you recover the device
Click to expand...
Click to collapse
How to contact you and how you can help me.
If you want to help write this here to help this benefit to anyone who has this or similar problem
Thank you

Prosjak said:
After trying to flash Pie my G7 stuck in fastboot mode. Download mode is unavailable so I not can reset the stock ROM.
After it reboots it boots into only to fastboot mode and is stuck in a loop now.
An even bigger problem is that now the bootloader is locked and the unlock.bin file can not unlock the bootloader.
ADB mode is not working!
DOWNLOAD mode is not working!
SYSTEM mod does not work!
There is only FASTBOOT mode that is in the loop
Does anyone have any suggestions?
Click to expand...
Click to collapse
Fastboot --set-active=a

LameMonster82 said:
Fastboot --set-active=a
Click to expand...
Click to collapse
Thank you for your reply
The problem is that the bootloader is locked
C:\ADB>Fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: Slot Change is not allowed in Lock State)
finished. total time: 0.003s

Problem solved
Octoplus/Octopus LG 2.9.3
Reset FRP Lock
1. Attach testpoint, and connect phone with Micro USB cable (don´t use USB hubs!).
2. Check PC Device Manager, a new device should appear "Qualcomm HS-USB QDLoader 9008" or "Unknown Device" if you hadn´t installed a driver.
3. Release testpoint and press "Reset FRP Lock" button.
Emergency mode
To enter emergency mode, disconnect cable, disconnect battery, press and hold "Vol+" button and connect USB cable.
My lucky day

What version of G7 use?
Sent from my LM-G710 using Tapatalk

PjLyTam said:
Please contact me, I can help you recover the device
Click to expand...
Click to collapse
i got this problem too.. please help with that

Prosjak said:
Octoplus/Octopus LG 2.9.3
Reset FRP Lock
1. Attach testpoint, and connect phone with Micro USB cable (don´t use USB hubs!).
2. Check PC Device Manager, a new device should appear "Qualcomm HS-USB QDLoader 9008" or "Unknown Device" if you hadn´t installed a driver.
3. Release testpoint and press "Reset FRP Lock" button.
Emergency mode
To enter emergency mode, disconnect cable, disconnect battery, press and hold "Vol+" button and connect USB cable.
My lucky day
Click to expand...
Click to collapse
how i can do this?

My G710EM has a problem with my lockback BL. I can't boot the system and it will prompt "Your device has failed a routine safety check and will not boot. This may be a temporary problem. If this message occurs repeatedly, visit this link on Another device and refer to the red case:g.co/ABH Your device will power off automatically after a while.” With LGup brush kdz brush does not go in, fastboot “fastboot flash unlock unlock.bin” prompt is invalid
* Target reported max download size of 536870912 bytes
Sending 'unlock' (1 KB)...
OKAY [ 0.004s]
Writing 'unlock'...
FAILED (remote: Flashing Unlock is not allowed
)
Finished. total time: 0.011s
I don't know what to do.

I had the very same problem as OP. I tried to install pie with LGUP (G710EM20b_00_OPEN_EU_OP_0508.kdz) but ended in fastboot loop.
After whole night of trying different things (being a noob means less sleep) I managed to run the phone in download mode. Starting from there I was able to install my previous rom. Both failed update and rescue operations were done on Win 10.
What I tried and didn't work:
- Fastboot --set-active=a
Code:
C:\ADB>Fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: Slot Change is not allowed in Lock State)
finished. total time: 0.003s
- Unlocking with unlock.bin. Didn't save the msg but saw it somewhere in another thread. I needed to install/point drivers first because the device was not recognized in Win.
- Solutions for G6 for going into download mode. The download mode icon was displayed for a second and then going to fastboot again.
- LG Flash Tool 2014 - I just followed a guide for older phones but it didn't work. Didn't try again.
What did work:
1. I found this post on reddit (remove spaces or PM me, I'm not allowed to post links):
Code:
https:// www .reddit. com/r/LGG3/comments/2qe5sr/in_need_of_serious_help_stuck_in_fastbootno/cn5f2qr/?utm_source=share&utm_medium=web2x
Quoting the post
At first, you'll need a working fastboot environment, you'll find out how to set it up on your own. Then you'll need the laf.img, I can upload mine if you want or I could help you extracting one out of a kdz file. Put the laf.img in the same folder like your fastboot.exe, then hold shift and right click, then click on "open command panel here" or however it's called in English. Type "fastboot flash laf laf.img" (Edit: It would probably better to use "fastboot boot laf.img" instead because of the bootloader lock). If that works, you at least have a working download mode.
Click to expand...
Click to collapse
2. I used LG_Firmware_Extract_v1.2.6.1 and extracted dz file from aforementioned pie file. The I extracted two laf files for the kz file. In my case they were: laf.img_180534 and laf.img_81990.
3. I took one of these files (sry, don't remember which one, but they have the same size - didn't check if they're the same) renamed it to laf.img and put a folder where fastboot.exe is.
4. I did
Code:
fastboot boot laf.img
and voila: the phone was in download mode!
5. After that LGUP the previous rom and the phone is working again. Here I needed few tries. At first the were some problems, then I tried different combinations (1.14, 1.15, w/ and w/o uppercut). I think LGUP 1.15 (1.14 with patch) did the work. I was able to "refurbish" the phone.
Hope it's useful for others. If anyone could prepare a guide from this description or/and tell why it worked - please feel free to do so.
I think I will wait some time before trying pie again

Garlikus said:
I had the very same problem as OP. I tried to install pie with LGUP (G710EM20b_00_OPEN_EU_OP_0508.kdz) but ended in fastboot loop.
After whole night of trying different things (being a noob means less sleep) I managed to run the phone in download mode. Starting from there I was able to install my previous rom. Both failed update and rescue operations were done on Win 10.
What I tried and didn't work:
- Fastboot --set-active=a
Code:
C:\ADB>Fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: Slot Change is not allowed in Lock State)
finished. total time: 0.003s
- Unlocking with unlock.bin. Didn't save the msg but saw it somewhere in another thread. I needed to install/point drivers first because the device was not recognized in Win.
- Solutions for G6 for going into download mode. The download mode icon was displayed for a second and then going to fastboot again.
- LG Flash Tool 2014 - I just followed a guide for older phones but it didn't work. Didn't try again.
What did work:
1. I found this post on reddit (remove spaces or PM me, I'm not allowed to post links):
Code:
https:// www .reddit. com/r/LGG3/comments/2qe5sr/in_need_of_serious_help_stuck_in_fastbootno/cn5f2qr/?utm_source=share&utm_medium=web2x
Quoting the post
2. I used LG_Firmware_Extract_v1.2.6.1 and extracted dz file from aforementioned pie file. The I extracted two laf files for the kz file. In my case they were: laf.img_180534 and laf.img_81990.
3. I took one of these files (sry, don't remember which one, but they have the same size - didn't check if they're the same) renamed it to laf.img and put a folder where fastboot.exe is.
4. I did
Code:
fastboot boot laf.img
and voila: the phone was in download mode!
5. After that LGUP the previous rom and the phone is working again. Here I needed few tries. At first the were some problems, then I tried different combinations (1.14, 1.15, w/ and w/o uppercut). I think LGUP 1.15 (1.14 with patch) did the work. I was able to "refurbish" the phone.
Hope it's useful for others. If anyone could prepare a guide from this description or/and tell why it worked - please feel free to do so.
I think I will wait some time before trying pie again
Click to expand...
Click to collapse
Thanks for you guide.. I follow it but unfortunatly after "fastboot boot laf.img" I get this message from my LG:
"Your device has failed a routine safety check.... it will reboot after a while.."

davinik84 said:
Thanks for you guide.. I follow it but unfortunatly after "fastboot boot laf.img" I get this message from my LG:
"Your device has failed a routine safety check.... it will reboot after a while.."
Click to expand...
Click to collapse
I recall I also had some error msg, it could've been the same. Now I don't remember what I exactly did next as most my actions were more or less random. Either I tried the same command but with other laf.img file (from the rom I used before), or I tried to restart the phone into download mode (vol- and power together and then vol+ after screen goes black) or tried the same file again.
Hope it helps.

davinik84 said:
Thanks for you guide.. I follow it but unfortunatly after "fastboot boot laf.img" I get this message from my LG:
"Your device has failed a routine safety check.... it will reboot after a while.."
Click to expand...
Click to collapse
I have the same problem as well. I follow the guide but I received the same error message

domenico.dalpiaz said:
I have the same problem as well. I follow the guide but I received the same error message
Click to expand...
Click to collapse
Check if the phone is recognized in LG Bridge. If so, then choose update error recovery from software update tab. Again, I don't remember if it worked immediately or did I need to reinstall drivers and/or choose a proper driver in device manager (generic ADB vs LG...) and/or restart the phone.

domenico.dalpiaz said:
I have the same problem as well. I follow the guide but I received the same error message
Click to expand...
Click to collapse
I have same error too ...

DenisVelev said:
I have same error too ...
Click to expand...
Click to collapse
Based on other threads, e.g. https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903 and https://www.reddit.com/r/lgg6/comments/axd17d/lg_g6_eu_glh870_bricked_after_update_your_device/
try:
install the LG Bridge updater software on a computer, go to updates, click the "correct update errors" button. Then plug in your turned-off phone while holding down the volume up button. It should switch to download mode and reinstall all software from the PC. Yes, this will erase all data but it should unbrick your phone (unless the hardware's broken I guess)
Click to expand...
Click to collapse

Garlikus said:
Based on other threads, e.g. https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903 and https://www.reddit.com/r/lgg6/comments/axd17d/lg_g6_eu_glh870_bricked_after_update_your_device/
try:
Click to expand...
Click to collapse
Cannot put in download mode. Only Fastboot. For a secound show download mode after that show fastboot mode.

Need Help For switching rom from china to global

hi devs
i flashed accidentially Chinese recovery rom on my whyred now i m unable to switch from Chinese to global version as i tried every method fastboot,recovery,qfil,mi flash and edl mode i mean every possible way but all in vain as every method ended with error and my fastboot command is locked.
so what can i do please suggest me
it's Chinese miui 11

guys please help me i m frustrated tried every available method on internet downloaded tons of file.

aliasgertaj said:
guys please help me i m frustrated tried every available method on internet downloaded tons of file.
Click to expand...
Click to collapse
What you are trying to do? Just switch from Chinese to Global? or your device is bricked now?
What did happen after that you flashed the Chinese recovery ROM?
What modes do you have available?
Did you unlock bootloader previously?

SubwayChamp said:
What you are trying to do? Just switch from Chinese to Global? or your device is bricked now?
What did happen after that you flashed the Chinese recovery ROM?
What modes do you have available?
Did you unlock bootloader previously?
Click to expand...
Click to collapse
i m not bricked as my device is working fine
but now no fastboot command working i m not able to flash custom recovery
i tried fastboot method , used miflash method every miflash from old to newest , qfil edl mode method with miflash and qualcomm flash tool
i m just able to switch between china stable n developer rom
if i m able to unlock ma fastboot command then i can flash atleast custom recovery .
kindly help me as all method ended up every time with diffrent error.

aliasgertaj said:
i m not bricked as my device is working fine
but now no fastboot command working i m not able to flash custom recovery
i tried fastboot method , used miflash method every miflash from old to newest , qfil edl mode method with miflash and qualcomm flash tool
i m just able to switch between china stable n developer rom
if i m able to unlock ma fastboot command then i can flash atleast custom recovery .
kindly help me as all method ended up every time with diffrent error.
Click to expand...
Click to collapse
Fastboot flashing commands won't work if you have bootloader locked.
Did you unlock bootloader previously and probably get locked again?
Did you enable all the proper options on Developer section, i.e. USB debugging and check if device is recogniced on adb commands?
What do you get with "fastboot getvar all"?

subwaychamp said:
fastboot flashing commands won't work if you have bootloader locked.
Did you unlock bootloader previously and probably get locked again?
Did you enable all the proper options on developer section, i.e. Usb debugging and check if device is recogniced on adb commands?
What do you get with "fastboot getvar all"?
Click to expand...
Click to collapse
thanks a lot dude i m on unlock boot loader .
But bootloader some time works means sometimes it shows my device name after available device command it shows only ???????? Fastboot devices
i tried all way possible but none of them worked.
And i m unable to switch from china to global.
Only i can do is switch between china stable to developer.

i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>

aliasgertaj said:
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
Click to expand...
Click to collapse
And you said you enabled USB debuging?!? you didn't. First enable it under development tools.
MAKE SURE YOUR USING RIGHT ADB/FASTBOOT TOOLS AND DRIVERS.
After 'adb reboot bootloader' use 'fastboot devices'. You can change usb cable and if you still get errors try using usb hub.
If all above fails than try it on WIN7 PC.

aliasgertaj said:
thanks a lot dude i m on unlock boot loader .
But bootloader some time works means sometimes it shows my device name after available device command it shows only ???????? Fastboot devices
i tried all way possible but none of them worked.
And i m unable to switch from china to global.
Only i can do is switch between china stable to developer.
Click to expand...
Click to collapse
aliasgertaj said:
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
Click to expand...
Click to collapse
I think you are not properly booted to the proper state while you're trying certain commands. Just to be clear; adb works while your device is power on and fastboot commands will work only while your device is in fastboot mode not while on adb mode. A way to be sure that you are doing properly is enabling USB debugging first but while connected device with PC, a prompt will appear from device screen and then tap on "always allow", then you have to type "adb devices" and follow step by step, if device is recognized you can go to the next step with "adb reboot bootloader" then in fastboot you have to see the bunny otherwise is not properly in fastboot mode, then you can follow with "fastboot devices" and so on, keep in mind that any command will work until device is properly recognized.

SubwayChamp said:
I think you are not properly booted to the proper state while you're trying certain commands. Just to be clear; adb works while your device is power on and fastboot commands will work only while your device is in fastboot mode not while on adb mode. A way to be sure that you are doing properly is enabling USB debugging first but while connected device with PC, a prompt will appear from device screen and then tap on "always allow", then you have to type "adb devices" and follow step by step, if device is recognized you can go to the next step with "adb reboot bootloader" then in fastboot you have to see the bunny otherwise is not properly in fastboot mode, then you can follow with "fastboot devices" and so on, keep in mind that any command will work until device is properly recognized.
Click to expand...
Click to collapse
thanks bro
yesterday i used xiaomitool v2 as it reboot automatically device in fastboot mode but as i said after in fastboot mode it doesn't boot in adb mode.
and what is proper method to open fastboot mode i m doing it by holding power and volume down button.

drnightshadow said:
And you said you enabled USB debuging?!? you didn't. First enable it under development tools.
MAKE SURE YOUR USING RIGHT ADB/FASTBOOT TOOLS AND DRIVERS.
After 'adb reboot bootloader' use 'fastboot devices'. You can change usb cable and if you still get errors try using usb hub.
If all above fails than try it on WIN7 PC.
Click to expand...
Click to collapse
thanks for response bro
i did it under developer option and trusted my computer connection also and install adb fastboot devices many time changed cable and port but nothing happen. i tried fastboot files of china stable rom but it also doesn't worked

aliasgertaj said:
thanks bro
yesterday i used xiaomitool v2 as it reboot automatically device in fastboot mode but as i said after in fastboot mode it doesn't boot in adb mode.
and what is proper method to open fastboot mode i m doing it by holding power and volume down button.
Click to expand...
Click to collapse
Just trying to determine what your words exactly mean when you say "after in fastboot mode it doesn't boot in adb mode." ... without entering in more technical insights adb works when device is on, no sense to boot to fastboot to try to boot to adb after that (?)
If you can boot to fastboot what you have to try firstly is unlock bootloader or be sure that is already unlocked using
Code:
fastboot oem device-info
if your device is or get unlocked then you can try to flash or just boot to a custom recovery but if you can't determine until now if your device is really unlocked then you couldn't go further.
The hardware method to enter to fastboot is from a device off; pressing both pwr and vol down buttons but if the bunny is not displayed probably you didn't really get fastboot mode.

SubwayChamp said:
Just trying to determine what your words exactly mean when you say "after in fastboot mode it doesn't boot in adb mode." ... without entering in more technical insights adb works when device is on, no sense to boot to fastboot to try to boot to adb after that (?)
If you can boot to fastboot what you have to try firstly is unlock bootloader or be sure that is already unlocked using
Code:
fastboot oem device-info
if your device is or get unlocked then you can try to flash or just boot to a custom recovery but if you can't determine until now if your device is really unlocked then you couldn't go further.
The hardware method to enter to fastboot is from a device off; pressing both pwr and vol down buttons but if the bunny is not displayed probably you didn't really get fastboot mode.
Click to expand...
Click to collapse
i m frustrated now tried all the thing tried official flash tool official build but even official build by miflash official latest tool unable to flash image

i bought my device to official xiaomi service center they told it will be done in an hour but after couple of hour they returned my phone that it cant be updated.??????
shame on xiaomi that they implemented a method that they themselves also don't know how to revert it.

aliasgertaj said:
i bought my device to official xiaomi service center they told it will be done in an hour but after couple of hour they returned my phone that it cant be updated.??????
shame on xiaomi that they implemented a method that they themselves also don't know how to revert it.
Click to expand...
Click to collapse
Do yo use WIN10? Find PC with Win7... and install adb/fastboot app and drivers. Than try..
Is your system working now?
Just unlock your bootloader and install OrangeFox recovery than you can flash whatever you need.
Problem solved.

drnightshadow said:
Do yo use WIN10? Find PC with Win7... and install adb/fastboot app and drivers. Than try..
Is your system working now?
Just unlock your bootloader and install OrangeFox recovery than you can flash whatever you need.
Problem solved.
Click to expand...
Click to collapse
ok bro i will try today with another pc and update you

aliasgertaj said:
ok bro i will try today with another pc and update you
Click to expand...
Click to collapse
thanks installed twrp on other pc running on windows 7 but now internal storage goes 0mb unable to mount system

aliasgertaj said:
thanks installed twrp on other pc running on windows 7 but now internal storage goes 0mb unable to mount system
Click to expand...
Click to collapse
Wtf .. what's wrong with you.. you did everything we said wrong... Where and when did I told you to install TWRP????
I'm done with you...
Good luck with china ROM.
Ignorance is a bliss.

drnightshadow said:
Wtf .. what's wrong with you.. you did everything we said wrong... Where and when did I told you to install TWRP????
I'm done with you...
Good luck with china ROM.
Ignorance is a bliss.
Click to expand...
Click to collapse
thanks dude i installed twrp wipe my internal storage there is some error then some tricks goes perfect as i supposed and woohaa i installed masik port edition and now my phone works fine.

aliasgertaj said:
thanks dude i installed twrp wipe my internal storage there is some error then some tricks goes perfect as i supposed and woohaa i installed masik port edition and now my phone works fine.
Click to expand...
Click to collapse
TWRP can't bypass encryption, when you have no access to read data (0mb) then you have to format it, to avoid that is always recommended use OrangeFox, just for future reference, if you understand that you can flash OrangeFox through TWRP for better experience.
Also you can use this tool to help you to automate some stuff https://github.com/Szaki/XiaomiADBFastbootTools