I have done everything by the book
i have windows 8.1 installed it did not work , then i did a dual boot and installed windows 7 , still not working
Debugging also activated
I have installed the driver that came with flashtool and the z ultra driver
But whenever I hold the up vol key all it says is flash mode
Pls someone help me , I just got the phone , Never had this problem with all my old samsung !
Also i manage to downgrade they phone to 4.2.2 Build 14.1.B.1.532 C6833,
Also its rooted
and its say my bootloader is safe to unlock
Vol up is fast boot, vol down is flash mode.
After rooting the next step should be to back up the TA partition
Sent from my Xperia Z Ultra using Tapatalk
blueether said:
Vol up is fast boot, vol down is flash mode.
After rooting the next step should be to back up the TA partition
Sent from my Xperia Z Ultra using Tapatalk
Click to expand...
Click to collapse
I already pressed the vol up button , its not going into fastboot mode
At the moment what are you trying to do that needs fastboot?
What steeps have you done
Can you post the output from flashtool when you have the phone powered off then connect it to the pc holding the vol up key
Sent from my Xperia Z Ultra using Tapatalk
blueether said:
At the moment what are you trying to do that needs fastboot?
What steeps have you done
Can you post the output from flashtool when you have the phone powered off then connect it to the pc holding the vol up key
Sent from my Xperia Z Ultra using Tapatalk
Click to expand...
Click to collapse
Here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it never goes into fastboot , I need to flash kernel
Try like this:
Turn off your phone with the cable disconnected, open the Flashtoll, go to "flash device" and choose "fastboot mode" when the dialog box open press the Volume Up and connect the phone to usb cable, a blue light will appears, choose "Select kernel to flash" go and get the kernel..
i have done like this lots of time and always worked...
Hope this help...
Lc1975 said:
Try like this:
Turn off your phone with the cable disconnected, open the Flashtoll, go to "flash device" and choose "fastboot mode" when the dialog box open press the Volume Up and connect the phone to usb cable, a blue light will appears, choose "Select kernel to flash" go and get the kernel..
i have done like this lots of time and always worked...
Hope this help...
Click to expand...
Click to collapse
still not working I have tried every single thing i know ?
Open ADB and type "adb reboot bootloader". It should kick it into fastboot.
Sent from my C6833 using Tapatalk
When you press the Volume Key Up and plug the Usb cable what happen with the phone?
Does the phone turns On normally or do nothing? What colour appears on the led?
LordManhattan said:
Open ADB and type "adb reboot bootloader". It should kick it into fastboot.
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
I tried what you said and it still did not work !!! here is a screenshot
I just turned of the dvice but never took it to fastboot mode , it stayed on flashboot mode
Lc1975 said:
When you press the Volume Key Up and plug the Usb cable what happen with the phone?
Does the phone turns On normally or do nothing? What colour appears on the led?
Click to expand...
Click to collapse
When i press the volume up the it goes to flashmode mode no matter what , The greenlight comes up instead of a blue light
Also the phone keeps going ofd and on back into flashmode
flashmode the LED will go orange -> green -> off Yes?
Does the phone stay in flashmode, the last line of your last post confuses me...
At this point I would try to flash a new FTF incase the bootloader is corrupt. Have you tryed to do a factory restore from Sony PCC?
sigmaphi said:
I tried what you said and it still did not work !!! here is a screenshot
I just turned of the dvice but never took it to fastboot mode , it stayed on flashboot mode
Click to expand...
Click to collapse
ADB doesn't even recognize your device. Have you given ADB acceess to your device? When you connect your Ultra to your computer and type "ADB devices" it should ask you for permission on your Ultra. Grant it access and type "adb devices" again. Do you see a string of numbers etc.? If yes, that's your Ultra.
Navigate to the ADB folder where fastboot.exe is. Hold SHIFT and right click the space around the files (not on the files) and click "open command window here" or whatever it says. Then type "fastboot reboot bootloader". BOOM (in theory)
LordManhattan said:
ADB doesn't even recognize your device. Have you given ADB acceess to your device? When you connect your Ultra to your computer and type "ADB devices" it should ask you for permission on your Ultra. Grant it access and type "adb devices" again. Do you see a string of numbers etc.? If yes, that's your Ultra.
Navigate to the ADB folder where fastboot.exe is. Hold SHIFT and right click the space around the files (not on the files) and click "open command window here" or whatever it says. Then type "fastboot reboot bootloader". BOOM (in theory)
Click to expand...
Click to collapse
Its does see my my phone but it will never go into fastboot , it goes to flashmode
it just stay at waiting for device
blueether said:
flashmode the LED will go orange -> green -> off Yes?
Does the phone stay in flashmode, the last line of your last post confuses me...
At this point I would try to flash a new FTF incase the bootloader is corrupt. Have you tryed to do a factory restore from Sony PCC?
Click to expand...
Click to collapse
I think you might be right with the bootloader been corrupt , but i did a full factory reset today and it still will not go into bootloader
and the phone keep going off and on when it in flashboot mode
sigmaphi said:
Its does see my my phone but it will never go into fastboot , it goes to flashmode
it just stay at waiting for device
Click to expand...
Click to collapse
That is weird... It should work, but it doesn't...
Sent from my Desire HD using Tapatalk
Any tip guys ? Would be nice , Thanks
sigmaphi said:
Any tip guys ? Would be nice , Thanks
Click to expand...
Click to collapse
I'm really grinding my brain here, but I can't think of any other ways of doing it. If only we were neighbours!
Sent from my Desire HD using Tapatalk
LordManhattan said:
I'm really grinding my brain here, but I can't think of any other ways of doing it. If only we were neighbours!
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Thanks , Also there is something i notced about the phone , if its off and i plug the usb to the pc , it goes on & off every few seconds into flashmode on its own without me free the up or down vol button ,
and since i cannot get into fastboot i cannot even unlock the bootloader
I have fresh install stock rom and repaired with Sony companion , No luck at all
Am thinkin of retuning the phone to the shop where i bought it and tell them I want a new phone,
If you know any tip to tell them so i get a new one it would be nice
sigmaphi said:
Thanks , Also there is something i notced about the phone , if its off and i plug the usb to the pc , it goes on & off every few seconds into flashmode on its own without me free the up or down vol button ,
and since i cannot get into fastboot i cannot even unlock the bootloader
I have fresh install stock rom and repaired with Sony companion , No luck at all
Am thinkin of retuning the phone to the shop where i bought it and tell them I want a new phone,
If you know any tip to tell them so i get a new one it would be nice
Click to expand...
Click to collapse
I would definitely try to get a new one, but that'll depend when you bought it. They'll also try to get it repaired instead of giving you a new one, but i'm not updated on German consumer laws, so i can't really tell you what rights you have, but again, time is important here, so you'll need to tell me how long it has been since you bought it. Also, it might be a little tricky to tell them that you were trying to enter fastboot so you could unlock the bootloader and void your warranty, lol. You can either go down that road and act like a pro, or you can act stupid and see how far that takes you
Related
Hi,
First of all, i have no credit for almost things i'm gonna say here, thanks must go to who realy worked in the mentioned things.
I created this thread because of the large numbers of people in [Q&A, Help & Troubleshooting] and realized that the most of these problems could be solved with a simple guide. I repplied this in a thread but now i'm creating in general with hope that people sees this before asking again.
This guide can be used in these cases:
- Phone is not recognized by KDZ offline flashing
- Phone enters in SECURITY ERROR screen and doesn't boots up
- Fail trying to flash a new ROM and the phone doesn't starts
- You tried to install custom ROM via CWM and your phone have a LOCKED bootloader
- You tried to install a custom recovery via fastboot/adb and your phone have a LOCKED bootloader
- Anyway, if you think your phone is dead, give a try here
When you try to install a custom recovery with your bootloader locked (for example), the phone system detects it and give you a message of an error in security. To solve this, you'll need to reflash your rom. By doing this, the KDZ will reflash the original recovery and you will be able to access your phone/recovery again.
Step by step:
1. You need to install fastboot drivers: http://forum.xda-developers.com/showthread.php?t=2119090
Turn off the phone and remove the battery. Download THIS and exctract it to C:/. Open device manager in windows (Rigt click on Computer > Manage > Device manager) and connect your phone without the battery to pc via USB cable. Look in device manager for a new hardware connected, right click on it and click in update drivers. In the window open, select "Search for software driver in the computer" and in the window open select insert C:\fastboot\usb_drv_windows, tick the option "include subfolders" and advance. A pop up window may appear asking you if you do want to install the driver, choose YES and the drivers will install.
1.1 - If you're having some badtimes installing fastboot drivers, follow THIS, it will probably solve the most of the problems - thanks @kuma82 for catching it
2. Navigate to the folder you extracted (C:/fastboot) and double click on start.bat. It will ask you for administrator privileges, just say yes.
3. Select your phone model (2 for P760, 3 for P765, 4 for P768 and 5 for P769). It will ask you to turn off your phone and remove battery. When you done with that, press enter. It will now ask you to insert USB cable with the phone without the battery and after 4 seconds re-insert the battery. Onde you done with that, it wil return a message to press any key. In this step the fastboot drivers may be installed again. Don't worry, it's normal
4. Remove the battery again, wait a few seconds and re-insert it.
5. Plug the USB cable in the phone with the battery in and let VOL UP pressed. The phone will enter in SW Update mode.
6. Follow THIS to reflash your rom. A list of avaiable official roms of different models is HERE. Remember to only flash roms made for your phone model or you may get some issues.
7. You're all done I recommend using THIS TWEAK, the phone becomes more responsive.
*** If you flashed a JellyBean rom (V20X.kdz) you can easily root with THIS and if you want CWM recovery use THIS CWM FOR LOCKED BOOTLOADER ------ REMEMBER NOT TO FLASH ANY CUSTOM ROM WITH THIS RECOVERY BECAUSE I'M CONSIDERING YOUR BOOTLOADER IS LOCKED AND FOR THIS REASON, YOU CANNOT FLASH CUSTOM ROMS WITH CWM, IT JUST DOESNT WORK!!!
People who deserve thanks:
@sguerrini97
@cmahendra
@Dragusdrake
@captaincrook
@artas182x
@Lelus
thanks for getting this together im sure it will help some people in need.
Not to hate or anything, but you should go into more details. I had a hard time at first because my computer wouldn't give me a chance to install the drivers (it kept disconnecting and connecting). Not every computer is the same, some people have to disable driver enforcement at boot to install omap4430 drivers. Just saying, but thanks for helping :thumbup:
Sent from my LGMS769 using xda app-developers app
kuma82 said:
Not to hate or anything, but you should go into more details. I had a hard time at first because my computer wouldn't give me a chance to install the drivers (it kept disconnecting and connecting). Not every computer is the same, some people have to disable driver enforcement at boot to install omap4430 drivers. Just saying, but thanks for helping :thumbup:
Sent from my LGMS769 using xda app-developers app
Click to expand...
Click to collapse
saw your post regarding this in one of the threads but lsot it.... mind sharing that?...i am getting unkown device in device manager whrn i try to install usb driver for omap
N3Ti said:
saw your post regarding this in one of the threads but lsot it.... mind sharing that?...i am getting unkown device in device manager whrn i try to install usb driver for omap
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
http://forum.xda-developers.com/showpost.php?p=44653501&postcount=55 @Shutcrut you are welcome to use this info in your OP.
I wish some moderator will sticky this stuff.
Sent from my LGMS769 using xda app-developers app
kuma82 said:
http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
http://forum.xda-developers.com/showpost.php?p=44653501&postcount=55 @Shutcrut you are welcome to use this info in your OP.
I wish some moderator will sticky this stuff.
Sent from my LGMS769 using xda app-developers app
Click to expand...
Click to collapse
Thanks kuma, i already put it into the thread.
Sorry i didn't go into details, i just took the information i gave to someone in asks threads and put it in here.
If you guys have problems in some point feel free to post here or send me a pm, i prefer post here your problems so other people can help us too
This guide will be helpful to many I'm sure. I think you should combine in wonky touch screen fix with v6 and cwm ts fix I've softbricked this phone so many times I'm back up and running in 15-20 mins but my bootloader is still locked
Sent from my LG-P769 using xda app-developers app
omgbossis21 said:
This guide will be helpful to many I'm sure. I think you should combine in wonky touch screen fix with v6 and cwm ts fix I've softbricked this phone so many times I'm back up and running in 15-20 mins but my bootloader is still locked
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
I will add more info about P769, i forgot because i don't have this model
Probably tomorrow i'll do this. I've soft bricked my phone a hundred times trying to unlock BL but no success.
@omgbossis21 if you need someone to test anything, i'm your man. I want to help with the ublocking process but i dont have much knowledge in these deep things
Thanks, but this method does not work for my p769.
Background info on device in question:
I tried rooting my LGP-769 (originally 20f) using a bin and KDZ for 20d. Halfway through, the software (on the PC) crashed, and now my phone is stuck at "S/W Upgrade" screen. It no longer appears in device manager, and the LG software used for flashing does not see it as connected, so I can't flash anything back that way. Things that I've tried:
Hard boot: no change, still stuck at S/W upgrade
Leave battery out for 15 min: no change
Can't flash because device no longer exists in Dev Manager
Do I have any options here? What went wrong?
Thanks in advance. I've only been a smartphone owner for a week and I'm worried that I've already ruined my device.
Click to expand...
Click to collapse
I can fastboot, but after doing so and attempting to flash the KDZ I get an error that the phone is not connected:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Even though the OMAP device (fastboot) is visible in device manager:
Is there any way to rescue the device? I keep reading that p769 is almost always recoverable from soft-brick but I seem to be completely stuck. Thanks in advance.
quickfastgoninja said:
Thanks, but this method does not work for my p769.
Background info on device in question:
I can fastboot, but after doing so and attempting to flash the KDZ I get an error that the phone is not connected:
View attachment 2211271
Even though the OMAP device (fastboot) is visible in device manager: View attachment 2211272
Is there any way to rescue the device? I keep reading that p769 is almost always recoverable from soft-brick but I seem to be completely stuck. Thanks in advance.
Click to expand...
Click to collapse
Using the lelus fastboot script flash the 769 ics x and u. Problem solved everytime
Sent from my LG-P769 using xda app-developers app
Hi. I'm able to install the drivers, and when using option 7 for jelly bean, the app gets stuck at <waiting for device> and the phone's screen shows a grey lg logo and the word fastboot in the corner, and there are strange vertical stripes at the bottom of the screen that don;t seem to go away anymore. I would appreciate any help
Hi. I'm able to install the drivers, and when using option 7 for jelly bean, the app gets stuck at <waiting for device> and the phone's screen shows a grey lg logo and the word fastboot in the corner, and there are strange vertical stripes at the bottom of the screen that don;t seem to go away anymore. I would appreciate any help
Click to expand...
Click to collapse
The strange vertical lines will go away after awhile. Did you look at my my second post in this thread. You should check them out. Another thing, you need to use x & u for ice, if your are trying to use the offline flash method.
CM 10.1 P769
---------- Post added at 10:30 PM ---------- Previous post was at 10:25 PM ----------
quickfastgoninja said:
Thanks, but this method does not work for my p769.
Background info on device in question:
I can fastboot, but after doing so and attempting to flash the KDZ I get an error that the phone is not connected:
View attachment 2211271
Even though the OMAP device (fastboot) is visible in device manager: View attachment 2211272
Is there any way to rescue the device? I keep reading that p769 is almost always recoverable from soft-brick but I seem to be completely stuck. Thanks in advance.
Click to expand...
Click to collapse
You did not state if you flashed ice cream x&u, you have it installed properly.
Another thing, how did your phone get into this state? What did you?
CM 10.1 P769
cubemike99 said:
Hi. I'm able to install the drivers, and when using option 7 for jelly bean, the app gets stuck at <waiting for device> and the phone's screen shows a grey lg logo and the word fastboot in the corner, and there are strange vertical stripes at the bottom of the screen that don;t seem to go away anymore. I would appreciate any help
Click to expand...
Click to collapse
What model is yours? Mine is a P768 and its only recognized by KDZ offline method if i choose P768 ICS x loader and uboot
But seems like the drivers are not installed in windows, are you using Windows 7 ? If yes, try reinstall the fastboot drivers following the thread i link in first post, pluging the phone in another USB port of your PC. kuma82 wrote a very good thing about installing the drivers, they are also linked in first post, take a look there and tell us if problem persists
I get to the fastboot on my l9 tmobile but it just keeps telling me to select phone model over and over again. it never gets me in fastboot on the computer.
i flashed a wrong rom and it just keeps telling me security error. it wont boot at all. i dont know what to do. Phone boots up into fastboot but doesnt show up on computer as fastboot. ive been trying to fix this for 2 weeks now.
Edit: i can get into sw upgrade on my phon but it shuts off in a while it never stays on.
fastboot is to only allow the PC to format a partition after that you can go to sw mode make sure with the fast boot program you choose ICS u-boot xloader. after that completes flash using sw mode
I'd try a new PC if had to. I know on mine I had to use another PC. Ideally windows 7
Sent from my LG-P769 using xda app-developers app
suicidalerik said:
I get to the fastboot on my l9 tmobile but it just keeps telling me to select phone model over and over again. it never gets me in fastboot on the computer.
i flashed a wrong rom and it just keeps telling me security error. it wont boot at all. i dont know what to do. Phone boots up into fastboot but doesnt show up on computer as fastboot. ive been trying to fix this for 2 weeks now.
Edit: i can get into sw upgrade on my phon but it shuts off in a while it never stays on.
Click to expand...
Click to collapse
You dont need to enter in fastboot. Run lelus fastboot script, select ics xloader and uboot for your phone model. It will say to you remove the battery and press enter, remove it and press enter. Then insert usb cable (im assuming you have fastboot drivers installed) and after about 2 seconds re insert the battery.
Now your sw update mode should stay on until your kdz update finish
And dont forget to run lelus script as administrator
have followed all the steps stated but am having trouble getting into s/w upgrade mode.. in the last 5 hours ive managed to go into it twice by sheer dumb luck. am now very frustrated. another question- do i have to use the lelus script everytime i try to go into upgrade mode?
suicidalerik said:
I get to the fastboot on my l9 tmobile but it just keeps telling me to select phone model over and over again. it never gets me in fastboot on the computer.
i flashed a wrong rom and it just keeps telling me security error. it wont boot at all. i dont know what to do. Phone boots up into fastboot but doesnt show up on computer as fastboot. ive been trying to fix this for 2 weeks now.
Edit: i can get into sw upgrade on my phon but it shuts off in a while it never stays on.
Click to expand...
Click to collapse
Try holding vol up and power with battery out. Hold it even after the s/w appears.
Sent from my LG-P769 using XDA Premium 4 mobile app
diod66 said:
have followed all the steps stated but am having trouble getting into s/w upgrade mode.. in the last 5 hours ive managed to go into it twice by sheer dumb luck. am now very frustrated. another question- do i have to use the lelus script everytime i try to go into upgrade mode?
Click to expand...
Click to collapse
Try installing ICS xloader and uboot with lelus script instead of JB ones and try again
will0899 said:
Try holding vol up and power with battery out. Hold it even after the s/w appears.
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I Recommend the same for you, try installing ICS xloader and uboot with lelus script and try again
(used unofficial way to unlock) .please anyone help only fastboot screen is accessible not edl and nothing other,bricked by flashing 7.2.3 recovery rom through twrp-cofface recovery.
please help as soon as possible not able to access device
when i try to switch on the phone then mi logo blinks fro two times then gets off.
when tried miflash it says device is locked .
in device manager this shows when connected in fastboot modeView attachment 3736364
this shows when connected for chargingView attachment 3736365
and when try to flash with miflash tool this error comes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
shubham tech said:
please anyone help only fastboot screen is accessible not edl and nothing other,bricked by flashing 7.2.3 recovery rom through twrp-cofface recovery.
please help as soon as possible not able to access device
when i try to switch on the phone then mi logo blinks fro two times then gets off.
when tried miflash it says device is locked .
in device manager this shows when connected in fastboot modeView attachment 3736364
this shows when connected for chargingView attachment 3736365
Click to expand...
Click to collapse
Are you able to access recovery (Power + Vol Up)?
If not:
Marshall London Bootloader Interface gave me some problems before. Try this:
1. Right-click "Marshall London Bootloader Interface" in your Device Manager and click "Update Driver Software..."
2. Select "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. In the list you should be able to find "Android" (or something like that) and in the sub-menu "ADB" (again, something like that), provided you have adb drivers installed on your computer.
5. Select "ADB" drivers to replace "Marshall London Bootloader Interface"
You should be able to use ADB in a command window to reapply Cofface's TWRP recovery and access it. If it's in Chinese see my comment here.
Hope this helps solve at least some of the problem.
Does your bootloader officially unlocked? If yes, just download a miui fastboot rom, and flash it through miflash
Edit: oops I didn't read the whole post. sorry
shubham tech said:
please anyone help only fastboot screen is accessible not edl and nothing other,bricked by flashing 7.2.3 recovery rom through twrp-cofface recovery.
please help as soon as possible not able to access device
when i try to switch on the phone then mi logo blinks fro two times then gets off.
when tried miflash it says device is locked .
in device manager this shows when connected in fastboot modeView attachment 3736364
this shows when connected for chargingView attachment 3736365
Click to expand...
Click to collapse
Hello..
I too faced such situation...
I tried to root my redmi note 3 pro..(SD)
I followed the unofficial method which I found here in XDA.. Don't know ,where I missed any step...
My phone gets in same situation as yours..
It can boot into fastboot mode ( volume - and power ),
If I turn on it flashes mi logo two times and .. Gets into diagnostic mode ...
Searched a lot.. But.. Can't find my exact situation in any thread..
Somewhere in some forum I found that.. Let the battery be fully drain.. And.. Without turning on.. Charge the phone to at least 30% .. And den enter edl mode by pressing and holding two volume buttons...( + & -).
My mobile is at 97 % of charge when it got bricked .
Which means... A few days to drain it fully..
Omg... I can't wait..
So.. I decided to open the back cover..
Gently opened it.. And.. Removed battery strip.. And.. Placed it again ...
Den..
While connecting to PC through USB cable..
I pressed and hold the two volume buttons..
Connected cable..and.. Pressed both volume buttons as fast as I can after connecting cable.. And holded for two secs..
There. U can enter edl mode...
So that u can flash.. Global stable ROM..via mi flash tool...
If u failed...
Remove the battery connector . and.. Put it again..
Close mi flash.. Open it again.. Try to put the phone in edl again...
I don't know .this can be done in another easy way..
But.. I have done this way...
Tell me if u succeed..
can you execute "adb devices" and "adb reboot edl" in command window when connecting your phone to PC? if so, you might use latest MiFlash (20160330 or 20160401) to flash rom.
MIUI forum has a guide to rescue bricked redmi note 3, you should have a look at it.
The posts are http://en.miui.com/thread-274589-1-1.html and http://en.miui.com/thread-235865-1-1.html
If the vol + and - trick does not work, I was in the same situation and I ended up doing this: http://forum.xda-developers.com/redmi-note-3/how-to/redmi-note-3-pro-snapdragon-650-edition-t3367774
if you unlock official way, just run the unlock tools again
Immortal68 said:
Are you able to access recovery (Power + Vol Up)?
If not:
Marshall London Bootloader Interface gave me some problems before. Try this:
1. Right-click "Marshall London Bootloader Interface" in your Device Manager and click "Update Driver Software..."
2. Select "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. In the list you should be able to find "Android" (or something like that) and in the sub-menu "ADB" (again, something like that), provided you have adb drivers installed on your computer.
5. Select "ADB" drivers to replace "Marshall London Bootloader Interface"
You should be able to use ADB in a command window to reapply Cofface's TWRP recovery and access it. If it's in Chinese see my comment here.
can you tell about this in some brief from where to select which driver please help?
Hope this helps solve at least some of the problem.
Click to expand...
Click to collapse
can you tell about this in some brief from where to select which driver please help?
shubham tech said:
can you tell about this in some brief from where to select which driver please help?
Click to expand...
Click to collapse
Created a short slide show. Hope this helps.
If you don't see "Android ADB Interface you have to install ADB/fastboot first. Minimal ADB and fastboot drivers
Best of luck. Let me know if anything else is still unclear to you.
Abhi45 said:
Hello..
I too faced such situation...
I tried to root my redmi note 3 pro..(SD)
I followed the unofficial method which I found here in XDA.. Don't know ,where I missed any step...
My phone gets in same situation as yours..
It can boot into fastboot mode ( volume - and power ),
If I turn on it flashes mi logo two times and .. Gets into diagnostic mode ...
Searched a lot.. But.. Can't find my exact situation in any thread..
Somewhere in some forum I found that.. Let the battery be fully drain.. And.. Without turning on.. Charge the phone to at least 30% .. And den enter edl mode by pressing and holding two volume buttons...( + & -).
My mobile is at 97 % of charge when it got bricked .
Which means... A few days to drain it fully..
Omg... I can't wait..
So.. I decided to open the back cover..
Gently opened it.. And.. Removed battery strip.. And.. Placed it again ...
Den..
While connecting to PC through USB cable..
I pressed and hold the two volume buttons..
Connected cable..and.. Pressed both volume buttons as fast as I can after connecting cable.. And holded for two secs..
There. U can enter edl mode...
So that u can flash.. Global stable ROM..via mi flash tool...
If u failed...
Remove the battery connector . and.. Put it again..
Close mi flash.. Open it again.. Try to put the phone in edl again...
I don't know .this can be done in another easy way..
But.. I have done this way...
Tell me if u succeed..
Click to expand...
Click to collapse
thanks for help but didnt succeed.
Immortal68 said:
Created a short slide show. Hope this helps.
If you don't see "Android ADB Interface you have to install ADB/fastboot first. Minimal ADB and fastboot drivers
Best of luck. Let me know if anything else is still unclear to you.
Click to expand...
Click to collapse
thanks for help but none of above worked for me.
adb things will not work if phone just got to fastboot.
you must look on 'ports' section on device manager.
it will detect qcom hs-usb qloader 9008 if you're on edl mode (you can use miflash on this situation).
but on bricked phone it will show qcom hs-usb diagnostic 900e if you try to enter edl. here you can't do anything.
the only working solution known is by disassembling the phone and use test-point method.
but luckily I don't have to do it. mine works just by re-unlock using unlock tool.
just apply the unlock code with your last entered mi account on phone. when you got the sms, go unlock it
aabenroi said:
adb things will not work if phone just got to fastboot.
you must look on 'ports' section on device manager.
it will detect qcom hs-usb qloader 9008 if you're on edl mode (you can use miflash on this situation).
but on bricked phone it will show qcom hs-usb diagnostic 900e if you try to enter edl. here you can't do anything.
the only working solution known is by disassembling the phone and use test-point method.
but luckily I don't have to do it. mine works just by re-unlock using unlock tool.
just apply the unlock code with your last entered mi account on phone. when you got the sms, go unlock it
Click to expand...
Click to collapse
even unlock tool says cant verify device, this is really a xiaomi,dont expect anything better from xiaomi.
shubham tech said:
even unlock tool says cant verify device, this is really a xiaomi,dont expect anything better from xiaomi.
Click to expand...
Click to collapse
If u had not opened ur phone and tried test point method , take it to service center ASAP.
sanjib734 said:
If u had not opened ur phone and tried test point method , take it to service center ASAP.
Click to expand...
Click to collapse
yes i am going to service center on tomorrow .
shubham tech said:
yes i am going to service center on tomorrow .
Click to expand...
Click to collapse
best of luck.
sanjib734 said:
best of luck.
Click to expand...
Click to collapse
got my phone repaired from mi service center.
Immortal68 said:
Are you able to access recovery (Power + Vol Up)?
If not:
Marshall London Bootloader Interface gave me some problems before. Try this:
1. Right-click "Marshall London Bootloader Interface" in your Device Manager and click "Update Driver Software..."
2. Select "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. In the list you should be able to find "Android" (or something like that) and in the sub-menu "ADB" (again, something like that), provided you have adb drivers installed on your computer.
5. Select "ADB" drivers to replace "Marshall London Bootloader Interface"
You should be able to use ADB in a command window to reapply Cofface's TWRP recovery and access it. If it's in Chinese see my comment here.
Hope this helps solve at least some of the problem.
Click to expand...
Click to collapse
Sorry to chime in (and open up this discussion) months later, but: I have marshall london bootloader interface Here's the thread with my issue http://en.miui.com/thread-362628-1-1.html (if you don't mind). My phone has finally powered off after bootlooping for hours (was able to switch between fastboot mode and mi logo bootloop). Waiting to recharge and try and enter recovery or try this (http://xiaomitips.com/guide/how-to-put-redmi-note-3-into-edl-mode/). Maybe you have some other pointers for me? Please? :laugh: I'm nearing my wits end
Hope this isn't rude and all and hope you have some ideas. Thanks in advance!
shubham tech said:
got my phone repaired from mi service center.
Click to expand...
Click to collapse
how much time they take to repair it
devsc said:
how much time they take to repair it
Click to expand...
Click to collapse
½ an hour
Sent from my Redmi Note 3 using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Power off the phone .
Press vol down and power button and it will boot into boot loader
Connect the USB cable .
Go to ed300's post and download the twrp recovery for lollipop and KitKat.
If the base ROM on which u have flashed the new ROM was KitKat use the KitKat twrp.
Else use the lollipop twrp.
Extract the required zip file.
After connecting the USB , click on the file named Flash . after its completed click on Boot file .after that's also done again click the Flash file .
After that it will show (waiting for device )
And the phone will boot to the recovery mode and u can flash the ED300's ROM I prefer CM12.1
Good luck.
bro Iam getting waiting for device now itself but Iam not able to move any furthur after that . It is just showing "waiting for device "
bvsbrk said:
bro Iam getting waiting for device now itself but Iam not able to move any furthur after that . It is just showing "waiting for device "
Click to expand...
Click to collapse
Did u follow as I mentioned?
Which was the base rom on which u flashed CM
Its lollipop and I followed steps exactly as you mentioned . I replaced the recovery of adb and fastboot folder with the recovery you suggested . But the thing is fastboot driver which was gone after flashing cm.
bvsbrk said:
Its lollipop and I followed steps exactly as you mentioned . I replaced the recovery of adb and fastboot folder with the recovery you suggested . But the thing is fastboot driver which was gone after flashing cm.
Click to expand...
Click to collapse
Replaced? I didn't get that.
Just download this https://userscloud.com/a25aszfwkn2z
Put the phone to fastboot by pressing vol down and power .
Connect the USB to phone . Unzip the file mentioned above. Open the file.
Double click on flash.bat then after that's done , boot.dat after that's also done then flash.bat and ur phone will boot to recovery.
aravindmj said:
Replaced? I didn't get that.
Just download this https://userscloud.com/a25aszfwkn2z
Put the phone to fastboot by pressing vol down and power .
Connect the USB to phone . Unzip the file mentioned above. Open the file.
Double click on flash.bat then after that's done , boot.dat after that's also done then flash.bat and ur phone will boot to recovery.
Click to expand...
Click to collapse
The link is downloading a file which is invalid. I cant open the zip file that you asked to download from the zip file . Pls send some other link
bvsbrk said:
The link is downloading a file which is invalid. I cant open the zip file that you asked to download from the zip file . Pls send some other link
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3yAzE4FH2e7RkNQbUk2b0g1T0E/view?usp=drivesdk
aravindmj said:
https://drive.google.com/file/d/0B3yAzE4FH2e7RkNQbUk2b0g1T0E/view?usp=drivesdk
Click to expand...
Click to collapse
that is not working every command window stopped at "waiting for device" anyway thanks a lot
bvsbrk said:
that is not working every command window stopped at "waiting for device" anyway thanks a lot
Click to expand...
Click to collapse
Try this https://drive.google.com/file/d/0B3yAzE4FH2e7RkNQbUk2b0g1T0E/view?usp=drivesdk
aravindmj said:
Try this https://drive.google.com/file/d/0B3yAzE4FH2e7RkNQbUk2b0g1T0E/view?usp=drivesdk
Click to expand...
Click to collapse
This I had tried already as you posted it before. Some one said my device data is completely lost while I flashed cm.
bvsbrk said:
This I had tried already as you posted it before. Some one said my device data is completely lost while I flashed cm.
Click to expand...
Click to collapse
Sorry the link was wrong try this it's a different one https://drive.google.com/file/d/0B3yAzE4FH2e7RU5helVWd0dBUGM/view?usp=drivesdk
App data excluding what's app will be lost but the data in the internal storage will.be present.
aravindmj said:
Sorry the link was wrong try this it's a different one https://drive.google.com/file/d/0B3yAzE4FH2e7RU5helVWd0dBUGM/view?usp=drivesdk
App data excluding what's app will be lost but the data in the internal storage will.be present.
Click to expand...
Click to collapse
Same thing bro the problem is something related to fastboot drivers which were gone from my phone
It worked for me . Can you send me a link where i can find CM12.1
Mahesh0001 said:
It worked for me . Can you send me a link where i can find CM12.1
Click to expand...
Click to collapse
https://forum.xda-developers.com/le...t-cm12-1-rom-lenovo-a6000-plus-withe-t3288805
My phone went into bootloop , i was using ResurrectionRemix 5.8.3 , i cant go into recovery mode. but can start bootloader.
I have installed Minimal fastboot , its showing no devices found when used "adb devices"
But shows the devices for command "fastboot devices"
I also tried flashing twrp.img using "fastboot flash recovery twrp.img"
But still phone not starting just stuck on looping the startup..Please helpppp
i get error when i hit flash.bat that device not found but it write the img file
What should i do?
My Lenovo A6000 Kitkat 4.4 struck on logo after phone switched off after hang. Phone when switched lenovo logo comes with display down saying press power button long for fastboot but does not enter fastboot. Whenever i press power button it says the same press power button long for fastboot but does not enter fastboot. nothing works I guess the OS crashed tried to enter into boot menu using volume +- powerbutton nothing works tried different combination nothing works.
i have downloaded kitkat 4.4 stock ROM but dont know how to flash and install using pc. If anyone knows how then let me know.
johnwell4u said:
My Lenovo A6000 Kitkat 4.4 struck on logo after phone switched off after hang. Phone when switched lenovo logo comes with display down saying press power button long for fastboot but does not enter fastboot. Whenever i press power button it says the same press power button long for fastboot but does not enter fastboot. nothing works I guess the OS crashed tried to enter into boot menu using volume +- powerbutton nothing works tried different combination nothing works.
i have downloaded kitkat 4.4 stock ROM but dont know how to flash and install using pc. If anyone knows how then let me know.
Click to expand...
Click to collapse
Flashing via phone is easy.
Just go to recovery wipe entire thing and then flash.
Mahesh0001 said:
i get error when i hit flash.bat that device not found but it write the img file
What should i do?
Click to expand...
Click to collapse
Make sure to use the recovery based on the rom that you where on before this thing happened.
And try executing the boot.bat file also. Do it simultaneously
aravindmj said:
Replaced? I didn't get that.
Just download this https://userscloud.com/a25aszfwkn2z
Put the phone to fastboot by pressing vol down and power .
Connect the USB to phone . Unzip the file mentioned above. Open the file.
Double click on flash.bat then after that's done , boot.dat after that's also done then flash.bat and ur phone will boot to recovery.
Click to expand...
Click to collapse
worked for me to open recovery again.. i am now trying to reflash MIUI8 android 5.1.1.:good::good::good:
Used the tablet for the first time in years, was working fine, rooted, unlocked bootloader, opened goomanager and clicked reboot into recovery and when my tablet rebooted it got stuck on the Asus splash screen.
I can however get the tablet recognized by my laptop in device manager as Asus Transformer Prime APX Interface.
Is it bricked for good? No I don't have a copy of the NVflash or whatever it is. I did at some point but the computer that was on is long gone....
I'm not sure if this will work for you...but you can try using the small pinhole reset button that's near the micro sd card. Just use a needle or paperclip to press down the reset button until the tablet restarts. I believe it just forces a soft reset...which will hopefully let you get past the splash screen.
The person in this post, (http://forum.xda-developers.com/showpost.php?p=61779883&postcount=12), said it worked for him in a similar sounding situation. Hope it works for you.
mattnmag said:
I'm not sure if this will work for you...but you can try using the small pinhole reset button that's near the micro sd card. Just use a needle or paperclip to press down the reset button until the tablet restarts. I believe it just forces a soft reset...which will hopefully let you get past the splash screen.
The person in this post, (http://forum.xda-developers.com/showpost.php?p=61779883&postcount=12), said it worked for him in a similar sounding situation. Hope it works for you.
Click to expand...
Click to collapse
No luck but thanks for trying
scottrod said:
Used the tablet for the first time in years, was working fine, rooted, unlocked bootloader, opened goomanager and clicked reboot into recovery and when my tablet rebooted it got stuck on the Asus splash screen.
I can however get the tablet recognized by my laptop in device manager as Asus Transformer Prime APX Interface.
Is it bricked for good? No I don't have a copy of the NVflash or whatever it is. I did at some point but the computer that was on is long gone....
Click to expand...
Click to collapse
You should be able to format the tablet and then flash a new recovery console using 'Minimal ADB and Fastboot' and then flash a new ramp via the newly installed recovery console.
NP
Nektopoli said:
You should be able to format the tablet and then flash a new recovery console using 'Minimal ADB and Fastboot' and then flash a new ramp via the newly installed recovery console.
NP
Click to expand...
Click to collapse
But how am I supposed to get Minimal adb/fastboot to see my device if I can't get to the fastbootscreen? the only way my laptop detects the tablet is by pressing power+volume up and that just detects in APX interface
scottrod said:
But how am I supposed to get Minimal adb/fastboot to see my device if I can't get to the fastbootscreen? the only way my laptop detects the tablet is by pressing power+volume up and that just detects in APX interface
Click to expand...
Click to collapse
Ok at this point you send it the command: adb reboot-bootloader
to see if it will 1)get the command and 2)execute the command
we know it's bricked but being about to send it command and have it attempted to execute them allowed me to wipe the recovery partition and flash a new TWRP recovery console.
Once you get a working recover console on the tablet you can flash a new ROM.
I am assuming you are on the correct bootloader and the device is unlocked and rooted.
NP
Nektopoli said:
Ok at this point you send it the command: adb reboot-bootloader
to see if it will 1)get the command and 2)execute the command
we know it's bricked but being about to send it command and have it attempted to execute them allowed me to wipe the recovery partition and flash a new TWRP recovery console.
Once you get a working recover console on the tablet you can flash a new ROM.
I am assuming you are on the correct bootloader and the device is unlocked and rooted.
NP
Click to expand...
Click to collapse
But the problem is I can't get into ADB or fastboot. Only APX mode. If I hold power+Volume up my pc detects the tablet in apx, if I reboot normally the tablet like stated before gets stuck on the ASUS logo screen. Sending this command does nothing and also adb devices does not list the tablet.
I was however running into issues getting my laptop to detect my tablet even before this issue and it wouldn't show up under adb devices then aswell.
I was still able to send commands with out the USB symbol on my tablet, you so have to get your laptop to see the tablet, are you running Window 7 or 8 or 10?
NP
Nektopoli said:
I was still able to send commands with out the USB symbol on my tablet, you so have to get your laptop to see the tablet, are you running Window 7 or 8 or 10?
NP
Click to expand...
Click to collapse
Windows 10, so when you say you were still able to send commands what was displayed on the screen on your tablet? Was it the black screen in APX mode?
I send the 'adb reboot bootloader' command, it rebooted the tablet which was bricked at the time. I got the 'unrecoverable boot error'.
I then held the VOL button down while holding the POWER button until it displayed the bootloader screen [The one with the green 'RCK, Android & Wipe Data' symbols in the center].
From there I was able to send fastboot commands erasing the RECOVERY partition and then flashed the correct TWRP recover console.
Once you get a working recovery console you can use it to flash a new ROM and associated ZIP files.
NP
Yes but when you sent the adb command what state was your tablet in? What was on the screen?
It was a few months ago but I believe it was the bootloader screen, this one;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NP
Nektopoli said:
It was a few months ago but I believe it was the bootloader screen, this one;
NP
Click to expand...
Click to collapse
Yeah it can't get that screen....
Do you get the fallen over dead android with the red exclamation triangle?
NP
Nektopoli said:
Do you get the fallen over dead android with the red exclamation triangle?
NP
Click to expand...
Click to collapse
No these are the only 2 screens I get....
1. Volume Up+ Power: Black screen. Detected by PC in APX mode
2. Volume Down+ Power: Asus Splash Screen. Not detected under device manager as far as I can tell.
Sorry but I don't know what 'APX mode' is and when I hold [VOL UP] & [PWR] the tablet vibrates and then nothing, blank screen.
NP
---------- Post added at 06:44 PM ---------- Previous post was at 06:38 PM ----------
Did you determent if the command: adb reboot bootloader
will reboot the tablet in APX mode?
NP
Hi everyone, I'm in need of some help ASAP. I unlocked my ANE-LX1 phone's bootloader so that I could root it, but things went wrong. My phone is stuck on TWRP logo screen (No TWRP menu, only logo) and my PC doesn't recognize it no matter what. I can only access the fastboot screen but it means nothing when you can't use ADB commands. I really don't know what to do, please help!
@-Alf- Hope that you'd help
soslusos said:
@-Alf- Hope that you'd help
Click to expand...
Click to collapse
Hi, try to explain what exactly happened, step by step.
soslusos said:
when you can't use ADB commands
Click to expand...
Click to collapse
For what reason?
-Alf- said:
Hi, try to explain what exactly happened, step by step.
For what reason?
Click to expand...
Click to collapse
Ok so I unlocked the bootloader, then I tried to root with Magisk by using adb but somehow it didn't work so I decided to install TWRP. I was on 9.1 but TWRP version was 9.0. I installed it and phone started to boot into TWRP only. PC recognized the phone but there were a bunch of folders with weird names. So I pressed on Format Data in TWRP but it didn't progress so I had to force-shut down my phone. Now PC doesn't recognize the phone at all. It's stuck on TWRP logo screen. Since my PC can't read the phone, I'm unable to use adb commands.
soslusos said:
Ok so I unlocked the bootloader, then I tried to root with Magisk by using adb but somehow it didn't work so I decided to install TWRP. I was on 9.1 but TWRP version was 9.0. I installed it and phone started to boot into TWRP only. PC recognized the phone but there were a bunch of folders with weird names. So I pressed on Format Data in TWRP but it didn't progress so I had to force-shut down my phone. Now PC doesn't recognize the phone at all. It's stuck on TWRP logo screen. Since my PC can't read the phone, I'm unable to use adb commands.
Click to expand...
Click to collapse
Format Data in incompatible TWRP? Really not good idea...
Okay, try the following:
- install on PC "Minimal ADB and fastboot" , open it, run command
fastboot devices <enter>
You'll get message 'waiting for any device'.
- Turn off the phone, hold Volume Down and connect to PC. Post the result.
What is region? (Cxxx)
-Alf- said:
Format Data in incompatible TWRP? Really not good idea...
Okay, try the following:
- install on PC "Minimal ADB and fastboot" , open it, run command
fastboot devices <enter>
You'll get message 'waiting for any device'.
- Turn off the phone, hold Volume Down and connect to PC. Post the result.
What is region? (Cxxx)
Click to expand...
Click to collapse
First of all, thank you man. It was suggested by someone on XDA, I shouldn't have done it.
I think the regional code is C121, I bought it in Turkey.
The thing is my phone doesn't turn off. Even when I force it by holding the button, it just turns back on. It stays like that until the battery dies.
I can open the fastboot screen by holding the vol down button and it says:
ap_s_abnormal 64
phone unlocked
frp unlocked
Have you tried connect to PC, then press and hold Power + Vol Down for 10-12 sec?
soslusos said:
It was suggested by someone on XDA
Click to expand...
Click to collapse
I bet I know who it was
Yeah I tried that, it just opens fastboot mode after phone restarts.
soslusos said:
Yeah I tried that, it just opens fastboot mode after phone restarts.
Click to expand...
Click to collapse
Game over . Test point method & board SW or DC-Phenix is your friend (maybe...). Unfortunately, I can't help you with this, I've never done it.
Damn. I don't even know what they are Can customer services do anything with this? I guess I'll have to pay.
soslusos said:
Can customer services do anything with this?
Click to expand...
Click to collapse
I guess so. It's all a matter of money .
Haha yeah but some stuff you do on your phone might be irreversible, that's what I'm afraid of.
So do you actually know what caused my device to boot into TWRP menu only? Is it because TWRP is incompatible with Android 9.1? (Or is it?)
soslusos said:
some stuff you do on your phone might be irreversible
Click to expand...
Click to collapse
Yes, e.g. damaged motherboard...
soslusos said:
So do you actually know what caused my device to boot into TWRP menu only? Is it because TWRP is incompatible with Android 9.1? (
Click to expand...
Click to collapse
Of course I cannot say that for sure. But I can say for sure that doing 'data format' (running stock EMUI) on some TWRP 3.4. and above can brick Kirin 659 device.
@-Alf- Hey, my phone is finally fixed. Do you know what's the latest firmware for 9.1 and where to download it? I'll install that one after rooting my phone.
soslusos said:
what's the latest firmware for 9.1
Click to expand...
Click to collapse
Hi, .401 (for C432 region)
soslusos said:
where to download it?
Click to expand...
Click to collapse
via OTA update
soslusos said:
I'll install that one after rooting my phone.
Click to expand...
Click to collapse
I would suggest updating first and then root
OTA says 9.1.0.208 is the latest version but I highly doubt that, something must be wrong with this ROM because the customer service guy installed it. My phone is C121 by the way.
soslusos said:
OTA says 9.1.0.208 is the latest version but I highly doubt that, something must be wrong with this ROM because the customer service guy installed it. My phone is C121 by the way.
Click to expand...
Click to collapse
Try to update via HiSuite or using option "Download latest version etc." in eRecovery. Maybe .208 is really the latest version for regional variant C121, idk...
-Alf- said:
Try to update via HiSuite or using option "Download latest version etc." in eRecovery. Maybe .208 is really the latest version for regional variant C121, idk...
Click to expand...
Click to collapse
So I was gonna roll back to EMUI 8 to unlock the bootloader but this time there's no "Switch to previous versions" option... In phone settings it says LGRP_OVS 9.1.0.208, is that the cause? How am I gonna unlock the bootloader now? So confused, I don't want to mess things up this time
soslusos said:
LGRP_OVS 9.1.0.208, is that the cause?
Click to expand...
Click to collapse
Yes, it is. Incompatible or incomplete FW .
In fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}