Hi All,
My son brought his Tablet to me yesterday and told me "It's not working". I looked at it and it was stuck on the Lenovo screen. I booted into recovery but it looks like its messed up 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"
}
image of issue -> ibb.co/1zCLyYr
After some probing my son tried to unlock it and load a rom, then restore stock rom and it was the last that caused the issue.
Now generally being able to get to recovery is a good thing but in this case it looks completely messed up and nothing will mount including the SD card.
It looks like adb is no longer enabled, it is not rooted and USB debugging is no longer enabled.
So it says
E:failed to mount block devices /dev/block/mmcblk1p1
E:remount block devices /dev/block/mmcblk1
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /cache
And so on.
This means I can't actually get to the SD Card with any update on it if I go to apply update from sdcard there is nothing showing in the sdcard directory
Have tried the following
- Apply from ADB (Device does not connect)
- wipe/factory reset,
- wipe cache
- reboot to bootloader
I can't get into any download mode either.
I did get it at least to make a mounting noise temporarily in Windows 10 but couldn't actually get to it or browse from there and haven't been able to repeat this.
Just wondering if there is anything I can do, or whether I should just forget it, surely there is some way to connect to it.
Cheers
Dan
Interestingly I plugged it into my mac and first it booted to a charging screen which hadn't happened last night.
Also if I leave it plugged into my mac for a little while Android file transfer eventually pops up and tries to connect but then says "Could not connect" but there is some life there at least.
A little more probing and I plug it into my Ubuntu rig and it starts to be recognized as Android but then get "Cant load MTP Device" if I try to browse it.
Looking into dmesg gives me
idProduct=78e8 (This is a Qualcomm powered device)
It then tries to mount it all but ends up mounting it as a Lenovo CD-ROM.
I can't seem to probe it past that, thinking its a futile effort but hoping for a miracle
Further update got it to the point where if I go to "apply update from ADB" the device is recognized and I try sideload but it just fails out on xfer 0.0
Silvertails said:
Further update got it to the point where if I go to "apply update from ADB" the device is recognized and I try sideload but it just fails out on xfer 0.0
Click to expand...
Click to collapse
You CAN NOT sideload an official ROM / OTA update with a modified device. You must have stock recovery and be non-rooted or it will fail every single time.
jwoegerbauer said:
You CAN NOT sideload an official ROM / OTA update with a modified device. You must have stock recovery and be non-rooted or it will fail every single time.
Click to expand...
Click to collapse
I cant do any kind of stock recovery, sideload is the closest I can get to anything, I think he must have put a different rom in there that has stuffed it up.
Is there anything I can do any steps I can take?
Windows won't recognise it so the QPST/QFIL method won't work
any steps or help would be appreaciated I have trawled every thread I can find here an across the internet
@Silvertails
ADB Sideload is a special mode that internally makes use of / runs Android's recovery binary ( AKA Stock Recovery ).
You test whether this mode is ready or not by simply running on PC the commands
Code:
adb devices
adb reboot recovery
If successful then you in Recovery select option "adb sideload" and on PC run
Code:
adb sideload <FILE-NAME.ZIP>
There's a very good thread on XDA here that deals with this model and recovering from bricks.
https://forum.xda-developers.com/thinkpad-tablet/general
Finally got this to work.
Ordered a cable that could get me into deep download mode as jumping the pins on the mobo was not working, the cable didnt get me into download mode, but what i discovered was that if I uninstall it being recognized as a CD ROM and messing about a bit I eventually got it to recognize as an Android Bootlader Interface using the lenovo drivers. I managed to use fastboot even though the device wasn't properly recognized to install TWRP. I got a success message and managed to reboot into TWRP recovery. The device then mounted as Lenovo but a different one, but at least it was mounting.
I still couldn't copy anything over to it, so I put the OTA default ROM on an SDCard and managed to get it to install from there and update to latest versions, and now its all working again.
Related
Ok im New to the whole Android thing , but i am excited to finally get on board with a Google phone. I like the iphone, i have no problems with it, its just the new carrier wont work with it. I have 2 macs, Macbook and MacPro (hackintosh) Im am very familiar with computer and how stuff works, I understand 70% of the commands i have to copy and paste from forums to make things work. Right now i am stuck (and im 100% sure its not due to the fact my Desktop isnt legit)
I got this phone used last week, fresh install with a certain rom (i dont know wich one, not sure how to tell, have no ideal how to get factory roms etc.) the phone is unlocked.
Before i plug in the usb to my phone, i enable debugging, then i select, USB mass storage.
WHen i connect i get the " Mac os X can't repair the disk "NO NAME"
{
"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"
}
then the External will mount, (so will the internal) here is what disk Util shows
It says the internal is 2.36 gb with 12.74 gb avail and only 980mb used, 0 number of files..
Now when i try to unmount the external, its fine, when i try to unmount the Internal, (NO NAME) all hell breaks loose, i wont let me, sometimes i get an error saying i cant unmount etc.. when i unplug it from the computer its still on my desktop, DiskUtil goes crazy and doesnt respond, then eventually any program that can see the drive will not respond (finder, activity Monitor)
anyone know a way around this? do i need to put a differnt install on it? its a t-mobile phone, should i just dl their newest update? how do i actually do that? their webpage? thanks for the help
j
I do not think Apple wants ppl to use Android..... Jealousy I guess, You can try a couple of things one would be Downloading this software from: Salling Media sync app for mac This usually works but not all the time and I do not know why.
This will work until you find a real fix from TMO, Samsung. It takes a few steps but works:
First open Terminal (applications - utilities - terminal), then type in "gpt show /dev/disk1" without the quotes. Make sure USB Debugging is turned on. Plug in the phone, it will be detected in Finder as a TMO CD, after a minute that will disappear, you can eject it to get there faster. Then mount the USB device, wait for the disk error message and select "Ignore" then unmount the card then remount it. Then in the Terminal hit Enter to run the "gpt show /dev/disk1 command". You may have to run the command more than once. It should recognize your card at that point. Then you can access the card as usual.
BTW, THIS IS WHY I HATE APPLE, they are excellent at making thing compatible for their products but, give little support to others......
yeah i tried that, but when i plug in the phone Network settings pop up no TMO CD
you think it could be because of the custom rom that was installed? I tried to find out wich one i had, but no luck..
it seems like there is somethign wrong with the 16gb partition... maybe a fresh install?
Yes when All else fails fresh install also you might find someone with a windows based computer to check it it amke sure the phone is not the problem
Yeah thats my next option.. VM wont work because OSX see's the phone 1st.. i cant just get win7 to take control without osx getting their hands on it..
now being familiar with the iphone. i would just find a stable version open itunes and select what version i want to install.. seeing how i bought my phone rooted and unlocked. and not knowing what ROM i have installed, do i just goto t-mobile's site and get the latest software from there?
connected fine on a windows machine.. this really sucks.
3/4/15 NEW HOWTO ROOT & install TWRP on DL701Q/DigiLand 7" Tablet 4.4.2 KitKat
Ok, So you got your new Super Cheapo MTK8127 quad core Tablet from BestBuy or some other overpriced electronics emporium and want to install root and a custom recovery So it won't suck nearly as bad
Feeling hungry but don't wanna feed yourself??? Open wide......Here comes the airplane requesting permission to land
The Following procedure may "BRICK" your tablet and wipe your porn....You do so at your own risk, Neither Kneee or his lawyer claim to know ANYTHING about android....or anything else for that matter
THIS GUIDE WILL WIPE YOUR PORN!!!
If you've ever seen THIS:http://forum.xda-developers.com/chef-central/android/root-dl701q-install-twrp-touch-recovery-t2980339thread, You know that "iRoot/vRoot no longer works since updating to kitkat. I've BUNGLED my way into a solution, Hope it helps you too.....
THIS GUIDE ASSUMES YOU KNOW HOW TO USE ADB AND FASTBOOT (ENABLE USB DEBUGGING)OR AT LEAST KNOW WHAT THEY ARE AND DON'T SUFFER FROM GOOGLEPHOBIA
#1 Making a backup of this crap software when ADB , FASTBOOT and SP flash tool are working correctly is pointless (IMHO) (inm
Here's Everything you should need:
Stock ROM COURTESY...THIS DUMBASS https://drive.google.com/file/d/0B9DmzLnUt5tuaUtJS1FHcjNyX1U/view?usp=sharing
ADB_&_FASTBOOT_executables, no need to install, just extract the .zip to the directory of your choice and execute openCMD.bat with a right click + run as administrator. it will open a terminal window, you can run all your ADVB & FASTBOOT commands from there:https://drive.google.com/file/d/0B9DmzLnUt5tuM29vOTNHNEZya2s/view?usp=sharing
Driver installer & MTK_SP_FLASH_TOOL for MT8127 use this to install the drivers and flash the stock rom + custom recovery.img https://drive.google.com/file/d/0B9DmzLnUt5tudVlrSEtzSE1tWHc/view?usp=sharing
UBIFS_Modified_CWM FOR FLASHING UPDATE-SuperSU-v2.46.zip COURTESY Vampirefo: https://drive.google.com/file/d/0B9DmzLnUt5tueC04RDFVX3plTVk/view?usp=sharing
UPDATE-SuperSu-v2.46.zipflash this with vampirefo's modified CWM recovery image UBIFSRecovery4SuperSu.img" https://drive.google.com/file/d/0B9DmzLnUt5tuZjlmVm1Wc2tFUTA/view?usp=sharing
TWRP Setup.exe...Used to install TWRP recovery after flashing Stock ROM + Custom recoveryCOURTESY TWRP team & Protocol 9https://drive.google.com/file/d/0B9DmzLnUt5tuTVVJS2d2RERpbVk/view?usp=sharing
STEP 1: INSTALL THE DRIVERS INSIDE THE MT8127 SP_FLASH_TOOL.zip" file you downloaded It will install the mtk usb vCOM driver we need for the mtk8127. if u have questions PM vampirefo. after that, turn your tablet upside down, FIND THE reset hole and jam the nearest tiny object in there until the screen does something different (like go black) release the reset button, hold VOLUME DOWN and plug in the USB cord and the tablet should be reconized as a preloader USB VCOM Port device under "Ports" in Device Manager
{
"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"
}
So, the necessary driver to save this POS is at hand. after it's done installing the tablet will probably reboot and the remaining drivers will install. (EVEN WITHOUT THE OTHER DRIVER YOU CAN ROOT AND FLASH NOW)
Fire up the MT8127 SP flash tool (run as administrator) you downloaded and you should see this:
Click "Scatter-Loading" and select the scatter file located in the stock rom folder you downloaded and unzipped (you DID unzip it right?) and click the "RECOVERY" FIELD LOCATED HERE:
and select the recovery image you downloaded called "UBIFSRecovery4SuperSu.img......yay, you should be all set up and ready to go!
Make sure youve already unplugged the USB cable AND hit the reset button. HIT THE DOWNLOAD BUTTON (the program is now waiting for your device...no rush) HOLD VOLUME DOWN AND PLUG IN THE USB CABLE, the computer will detect the device, the program will proceed to shove a bunch of ones and zeros down the the tablets throat and it will reboot (hopefully to a mediatek logo).
If so, youre not as stupid as everyone says when u leave the room
Toss "UPDATE-SuperSU-2.46.zip" on a microSD, Power off the device, shove the SD in his home and hold POWER + VOLUME UP until you get prompted to select either RECOVERY OR FASTBOOT, we want recovery so make sure it's selected and press VOLUME DOWN to boot into recovery & install your SuperSU.zip and reboot
once the OS is fully running, run TWRP.exe as ADMINISTRATOR in AUTO mode, TWRP recovery should be installed and u should still have root, if not, you'll need to go into advanced, then mount system before re-installing from zip.
NOW learn ADB and fastboot so I can save my breath next time:
PS, all your GAPPS are gone....quit *****ing, I've got em here: htpa_gapps-modular-micro-4.4.2-20140608-signed.zip(pa_gapps-modular-micro-4.4.2-20140608-signed.zip 85.3MB) & HERE: https://drive.google.com/file/d/0B9DmzLnUt5tuSl9lME9VZnFJTU0/view?usp=sharing(pa_gapps-stock-4.4.2-20140608-signed.zip 267MB))
I have requested this thread be removed, you are using my stuff without permission, and even crediting yourself with the firmware, I took the time to download, you yourself have done nothing but take others work including mine without permission.
Long story short:-
My device is locked usnig "surelock" so i don't have access to anything on it. I want to remove it and put any OS which will let me use my tab in normal way. I don't want any data from my tab, i just want it to function like a normal tablet. Due to this lock i almost can't do anything on my tablet. I am stuck only on one screen.
ABOUT DEVICE:-
TABLET - Lenovo Tab 4 10 TB-X304L
I don't know the android version but it was manufactured in 2018. and is now out of warranty.
WHAT I HAVE DONE TILL NOW
Tried Hard Reset:-
Ofcourse i tried doing a hard reset on it but in fastboot mode it didn't had any hard reset option. (since images are not allowed or maybe i don't know how to put my image using url i will type what it showed to me in italics.)
FASTBOOT MODE
PRODUCT_NAME -
VARIANT - QRD eMMC
BOOTLOADER VERSION-
BASEBAND NUMBER-
SECUREBOOT - enabled
DEVICE STATE - locked
now when i went in recovery mode it showed
REBOOT SYSTEM NOW
REBOOT TO BOOTLOADER
APPLY UPDATE FROM ADB
APPLY UPDATE FROM SD CARD
MOUNT/SYSTEM
VIEW RECOVERY LOGS
RUN GRAPHICS TEST
POWER OFF
2. Now since there is no hard reset so i tried to update the firmware using adb. After a lot of work i was able to find the firmware file for my tablet (still not sure if it is perfect for my tablet) other sites claimed to have it but asked for money.
Ok then i tried to flash the device it with the firmware using both adb and sd card but it showed this error in tablet. This error came while using sd card
E:footer is wrong
E: signature verification failed
E: error: 21
Installation aborted
While using adb from pc it detected the sideload but it showed this error
Total xfer: 0.00x
and Installation Aborted was showed in tablet.
FINALLY
I am finally posting it here to know what possible solutions are left for me. This tablet is quite expensive for me so i want to make it work badly. Please help if you can. I am okay with any operation system.
@Serjeel_Ranjan
Take note that with tablet's Stock Recovery you can only flash a Stock ROM / OTA - means a ROM / Patch that is signed by tablet's OEM/Carrier.
To get rid off of SureLock app you can try this
Code:
adb devices
adb shell "am kill com.gears42.surelock"
adb shell "am start -a android.intent.action.MAIN"
adb reboot
2nd command kills SureLock. 3rd command ask you for home app: a window comes up, select TouchWiz Home and select Always, Android home screen will come up.
Finally uninstall the SureLock app.
its shows this single error.
error-closed
{
"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"
}
plese tell if you are able to view the image.
@Serjeel_Ranjan
Screenshots provided shows you are running in wrong ADB mode.: Sideload mode.
To leave Sideload mode enter
Code:
adb devices
adb reboot
Then run the command sequence as previously listed
see when i do type the commands in fastboot mode. my device is not detected in adb mode but detected as fastboot device
how ever in sideload mode device is detected but no commands are running
@Serjeel_Ranjan
The "error:closed" you are receiving is most likely due to outdated and/or not-matching ADB driver.
Download the official Lenovo driver matching your device from here.
Good luck.
I installed the exact driver for my device from the website but that didn't made any difference.
Hello. I recently brought back my x820 to life. I need a phone.
It had TWRP and a custom rom. I tried to wipe and I actually wiped too much. So I had to install stock rom again because for some reason, lineage gave me an error at install (like it wasn't the right rom but it really was since I found it here https://download.lineageos.org/x2).
So I try to install TWRP again: twrp-3.7.0_9-0-x2.img found here: https://eu.dl.twrp.me/x2/
I launch ADB on a cmd prompt
- adb devices (List of devices attached e816a730 device). Super it's working and recognized
- adb reboot bootloader (phone miraculousely reboots in fastboot mode - YAY)
- fastboot devices ....... goes back to c:\ADB .... no devices found
So I reinstall ADB (from here: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/). Y to all, reinstall drivers and everything. Reboot PC. Do everything again.....still the same weird fastboot < waiting for devices >.
Devloper options are enabled.
OEM is unlocked.
USB debugging is ON.
Cable has been changed.
Cables have been plugged on USB 2.0 ports (in the back), on 2 different computers.....still the same thing.
*#*#76937#*#* typed in and AT ports enabled.
Could someone have the kindness to help me figure out what's wrong with what I'm doing? I'm usually pretty comfortable with rooting, flashing etc....but I'm clueless here.
Thanks for any help or input.
First off, please install the Android SDK Platform Tools [instead of 15 seconds ADB installer]
Once done, install the Fastboot Drivers on your PC.
The ADB Tools [Platform Tools, 15 seconds installer, etc] don't have Fastboot binaries, so you will only be able to execute ADB-related commands and not the Fastboot ones.
Thanks.
I downloaded the fastboot drivers. But I can't seem to install them. In fastboot mode, I see this in my device manager:
{
"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"
}
I follow instructions from here: https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/ (your link). Although I'm on windows 10.
When I try to update driver, whatever I do, I get this error:
Which means "the folder doesn't contain any compatible driver for your device. If it contains a driver, make sure it can work for x64 computers".
So I'm pretty sure it's a driver problem. Is there a way to completely uninstall previous drivers and go from scratch again? Or any cleverer solution?
Try removing the faulty device then disable driver signature enforcement and install drivers.
https://avalonsciences.com/wp-conte...Signature-Verification-on-Windows-8-or-10.pdf
Thanks to both of you. Especially to you binary who pointed me on the right tutorial. I was doing something wrong when updating drivers in fastboot mode. I chose a device before locating the .inf file.
YES
NOOOOOOOOOOOOOOOOOOO
The bottom screen was taken from here: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
"Show all devices" MUST be selected before going a step further apparently. All 3 drivers were installed flawlessly. TWRP was flashed successfully. I just need to figure out why it's still the old stock recovery showing up when I VOL+ and POWER start.
Cheers guys.
lucky24i said:
I just need to figure out why it's still the old stock recovery showing up when I VOL+ and POWER start.
Click to expand...
Click to collapse
Glad that you were able to rectify the driver issue. As far as TWRP is concerned, as soon as you flash it, boot straight to it [without booting to the system] and then check out the result.
In some instances, the device tends to replace TWRP with stock recovery upon boot. So avoid booting to the OS and use fastboot reboot recovery to straightaway boot to TWRP after flashing it.
Thanks. Working great
disclaimer - sorry i really have no idea what i am doing and my goal is to just go back to my normal phone
my phone is poco f1 and now i can only access fastboot and this "powered by android" screen. fastboot into twrp doesnt work because of "boot command is not allowed in lock state" error
hello all so i tried rooting my phone and then realized that its going really badly (i have a more details about it down) so i decided to flash stock rom using techno treatment's tutorial on it but along the way i have faced a couple of problems - when trying to install drivers, program crashes, and others below
first time i flashed i got an error (timeout error in logs) , so i tried to flash again but this time i left it open for some time (at around 500 seconds i pressed flash again, in logs it shows that flashing already started) and when i came back it was at 12000 seconds still flashing so i closed miflash and am flashing once again but with a shorter folder path (desktop\xiaomi\firmware).
after this i deleted 2 lines in flash_all.bat because i kept getting stuck on echo mismatching image and device. after this everytime i try to flash i get this error - error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State')
and also error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State') in the other log file
and after this i tried to go into fastboot but noticed that the fastboot logo is different, it was a bunny with a hat repairing android robot but now it is android robot repairing itself
{
"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"
}
(this is what it looks now)
what i did before flashing stock - sorry my memory isnt the best this is all in a span of around 5 hours and my phone is pocophone f1. so at first i followed munchys tutorial on how to root, i succesfully enabled bootloader then in twrp i flashed recovery with some errors like failed to mount /system and 3 others like this but i ignored and continued then i installed magisk and after that in the video he goes into his phone no problem but i had "no os" and i think i just clicked around like backing up, restoring and wiping. then i thought i need a rom because its an os right? so i installed lineage and that was the last time when i could put files into my phone through usb. then i flashed the zip and after that rebooted and got "cant load android system, your data may be corrupt" so i pressed format something like that and did it a few times (i think this is when i couldnt put my files) until eventually saw that its no use so i went back to twrp and again clicked around until eventually wiping everything now i have no os and i cant transfer anything through usb.
Hi @medioqre
Seems like you are in locked bootloader state. You can not flash any ROM with locked bootloader unless you are enter EDL mode. See youtube tutorial to access edl mode for Beryllium
khusika said:
Hi @medioqre
Seems like you are in locked bootloader state. You can not flash any ROM with locked bootloader unless you are enter EDL mode. See youtube tutorial to access edl mode for Beryllium
Click to expand...
Click to collapse
Hi, to confirm - entering edl mode requires me to open up my phone right? how would i do that and how would i close it up after?
Thank you!
medioqre said:
Hi, to confirm - entering edl mode requires me to open up my phone right? how would i do that and how would i close it up after?
Thank you!
Click to expand...
Click to collapse
That's right, but i recommend go to the service center if you aren't able to do it.
khusika said:
That's right, but i recommend go to the service center if you aren't able to do it.
Click to expand...
Click to collapse
Hi again, its been 10 days.
so i have not went to a service center yet, because my city is too small for that. But i have a question. i didnt do anything else with my phone but today i decided i could do something and i booted it and i found out i can access fastboot mode and recovery mode, and in here i can see -
main menu, mi-recovery 3.0
and this one option
"connect with miassistant" which just gives me a picture of a phone if its plugged or unplugged with usb and under theres is a link to this website pcsuite.mi.com which doesnt work.
does this change my situation?
medioqre said:
Hi again, its been 10 days.
so i have not went to a service center yet, because my city is too small for that. But i have a question. i didnt do anything else with my phone but today i decided i could do something and i booted it and i found out i can access fastboot mode and recovery mode, and in here i can see -
main menu, mi-recovery 3.0
and this one option
"connect with miassistant" which just gives me a picture of a phone if its plugged or unplugged with usb and under theres is a link to this website pcsuite.mi.com which doesnt work.
does this change my situation?
Click to expand...
Click to collapse
If you are still in locked bootloader, you can't write firmware through fastboot or recovery
Why don't you try unlocking the bootloader officially?