imgur screenshot: KB4810j.png
So I got lineageOs on my xiaomi redmi note 3 kenzo about 3 weeks ago and I've been having a few problems ever since such as the camera constantly crashing and not being able to focus when it does work and recently, the phone has only been able to charge after reboot but when it is plugged into my pc, it does not prompt for usb connection method and the pc does not recognize it but it does charge after reboot. I tried updating it through the phone but when I try, it says "could not verify or file may be corrupted". Any ideas on how i might be able to fix this?
Try to reinstall it by wiping Dalvik cache / System / Data / Cache
Check the MD5 of your .zip files also
Related
Hello everyone,
First and foremost, please forgive me if an answer to this has already been posted somewhere; I have searched several different forums extensively, and while I have found several similar problems, I have tried their solutions and come up empty-handed. Here's my dilemma:
1. My phone simply refuses to be detected/recognized by my PC via USB connection, through Kies/Odin/Windows Explorer, though I can be detected and connect through AirDroid.
2. I have updated my Samsung USB Drivers for Mobile Phones, and reinstalled those drivers multiple times.
3. I have tried multiple different USB cords, as well as multiple different USB ports.
4. I have been successful in connecting my wife's Note 1 to my PC.
5. I have tried dialing the "*#0808#" code into the dialer, and it always tells me that the signal is weak.
6. I have done a factory reset, both through the settings menu and through the recovery mode.
7. After having done the factory reset, I have been able to get the phone to download updates, but when the phone tries to install them, it only gets to 25% every time and then shows "Error", after which it tells me that the firmware was unable to update.
8. I have downloaded, installed, and tried every app I can find that claims to be able to root a phone without a PC, and they have all failed.
9. I am simply unable to find the "USB Connections" menu, the one where the MTP or PTP modes are, and have only been able to access it through Samsung's "Smart Care" app.
10. I have also tried to get Odin to recognize my phone by resetting my SIM card, and by using the battery removal trick: neither worked for me.
I think that pretty much covers everything right now.... I am COMPLETELY dumbfounded, and have NO idea what to do, NOR do I have any idea if this is a hardware or software problem. ANY help would be MOST appreciated.
I have an SM-P607T with an active T-Mobile plan - though I bought it from a third party then added it to my account. Previously everything worked fine, as I tried CM and a few ROMs on it, but ultimately went back to stock TMo ROM, 4.4.2, and just rooted it. Hadn't used it in awhile, grabbed it and thought I'd update to official Lollipop build.
First off, I disabled SuperSU and tried to apply the 4.4.4 update, assuming after that it'd offer me 5.1.1. Applying the 4.4.4 update failed. I factory reset the device in recovery mode (stock recovery), which of course fully removed SuperSU. Still fails updating. I downloaded the Lollipop ODIN tar, and that's where I started running into showstopper issues.
When I plug in a USB cable from a PC, the tablet starts charging, and that's it. There is no sign in windows that a device has been connected, no ding that something has been attached, no driver search. I tried this on 3 Win10 PCs. On all of them I installed Samsung Drivers, and even installed Samsung Easy Switch (new KIES). It would never register that it was plugged into a PC. I tried plugging my Note 4 in, registers and works fine (I read a thread on here by someone saying Win10 wouldn't recognize Samsung devices - not the case for me, phones work fine, just the tablet that won't show up). There is NO driver issue because the system never acknowledges anything is connected at all. I tried 3 PCs and 4 USB cables. I tried Samsung Easy Switch/KIES device recovery - tried putting tablet in download mode and tried putting it in recovery mode; neither ever shows up on PC. I tried using ADB, does not show up in devices (I have USB Debugging checked, Unknown Sources checked, etc etc).
I downloaded the Lollipop ODIN tar.md5 and put it on the microSD card. I loaded stock recovery, chose to flash from external storage, selected the .tar.md5, it said it was flashing it, said it flashed successfully even. Rebooted and it hadn't flashed at all.
Does ANYONE have ANY idea how to get my tablet updated? I can handle not being able to connect to PC, but I want to at least get OTA updates working. Factory reset, apply 4.4.4 OTA, fails after reboot every time.
Help?!
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Hi i have a similar problem as you, my Note is the SM-P600 that I rooted and has TWRP v2.8.7.0 and last time I went into recovery, the thing came up with a stock red upper left hand side text say "recovery in not seandroind enforcing" then ended up with the "Firmware upgrade encountered an issue please select recovery mode in kies and try again" but the damn thing will not connect. 2 usb 3 ports and 2 usb 2 ports multiplecables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- yet my the usb drivers see my note 4 just fine, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If you have any suggestions and can let me know I'd appreciate it.
bigillz said:
I have an SM-P607T with an active T-Mobile plan - though I bought it from a third party then added it to my account. Previously everything worked fine, as I tried CM and a few ROMs on it, but ultimately went back to stock TMo ROM, 4.4.2, and just rooted it. Hadn't used it in awhile, grabbed it and thought I'd update to official Lollipop build.
First off, I disabled SuperSU and tried to apply the 4.4.4 update, assuming after that it'd offer me 5.1.1. Applying the 4.4.4 update failed. I factory reset the device in recovery mode (stock recovery), which of course fully removed SuperSU. Still fails updating. I downloaded the Lollipop ODIN tar, and that's where I started running into showstopper issues.
When I plug in a USB cable from a PC, the tablet starts charging, and that's it. There is no sign in windows that a device has been connected, no ding that something has been attached, no driver search. I tried this on 3 Win10 PCs. On all of them I installed Samsung Drivers, and even installed Samsung Easy Switch (new KIES). It would never register that it was plugged into a PC. I tried plugging my Note 4 in, registers and works fine (I read a thread on here by someone saying Win10 wouldn't recognize Samsung devices - not the case for me, phones work fine, just the tablet that won't show up). There is NO driver issue because the system never acknowledges anything is connected at all. I tried 3 PCs and 4 USB cables. I tried Samsung Easy Switch/KIES device recovery - tried putting tablet in download mode and tried putting it in recovery mode; neither ever shows up on PC. I tried using ADB, does not show up in devices (I have USB Debugging checked, Unknown Sources checked, etc etc).
I downloaded the Lollipop ODIN tar.md5 and put it on the microSD card. I loaded stock recovery, chose to flash from external storage, selected the .tar.md5, it said it was flashing it, said it flashed successfully even. Rebooted and it hadn't flashed at all.
Does ANYONE have ANY idea how to get my tablet updated? I can handle not being able to connect to PC, but I want to at least get OTA updates working. Factory reset, apply 4.4.4 OTA, fails after reboot every time.
Help?!
Click to expand...
Click to collapse
---------- Post added at 11:04 AM ---------- Previous post was at 11:02 AM ----------
I am confused what you mean by calculator, I am on Win 10 and have a similar problem, my Note is the SM-P600 that I rooted and has TWRP v2.8.7.0 and last time I went into recovery, the thing came up with a stock red upper left hand side text say "recovery in not seandroind enforcing" then ended up with the "Firmware upgrade encountered an issue please select recovery mode in kies and try again" but the damn thing will not connect. 2 usb 3 ports and 2 usb 2 ports multiplecables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- yet my the usb drivers see my note 4 just fine, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If you have any suggestions and can let me know I'd appreciate it.
shineliu said:
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Click to expand...
Click to collapse
shineliu said:
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Click to expand...
Click to collapse
thank you very much. it worked.
Hi all,
I got given this Tab3 because the smd power socket connection guts were physically broken inside socket.
Fitted new power socket (I'm an electronics repair engineer by trade) and checked all pcb (printed circuit board) tracks leading from new fitted socket to ensure there were no hidden breaks ...... new socket refit was 100% successful .....with no solder shorts / bridges and no broken tracks leading to mainboard.
I left Tab3 on charge overnight and next day switched Tab3 on only to be greeted with dreaded .PBL and .PIT failed issue.
After extensive (days!) research I gathered together all necessary firmware and tools and decided that its an easy firmware fix if flashed to an original Samsung SM-T210 UK firmware.
(Please note I dont know past history of this Tab3 .... I dont know if it was rooted / upgraded firmware etc ..... I doubt it though as it belonged to a 7 year old)
Big issue ..... Odin flash tool won't show coms port connection on PC via USB (have tried 3 different laptops one with XP, one with Win7 32bit and another with Win7 64 bit. I've installed / uninstalled / reinstalled multiple Samsung usb drivers that were verified to work with my Tab3 SM-T210 model on each PC .... no joy. Even installed / uninstalled / reinstalled Kies from Samsung .... still wont connect when Tab3 is in download mode. Have kept PC device manager open and nothing appears in device manager. Also have tried 6 different makes of Usb A to micro Usb cables. Have disabled all antivirus, UAC, firewall and Win defender etc ... still no go!
When I go into download mode (power + Vol- +Home buttons) a warning screen does appear BUT it only shows right hand side of graphic warning ..... left hand side is totally grey from top to bottom. (LCD screen is not faulty as it displays full screen info on failed .pbl / .pit flash memory checks) When I then select Vol+ this vertical half graphic info and half grey screen disappears just leaving the backlight on .... which I assume means Tab3 is in proper download mode?
I can go to all recovery modes which allows me to factory reset and delete user cache etc .... it seems to go through the proper routines of reset but upon restart .pbl and .pit failed error in red memory check list is still there.
I can also try and flash firmware file from external sd micro card .... Tab 3 recognises firmware OK and shows Install ..../SD, but then after approx 5 minutes it restarts to failed .pbl /.pit error list again.
Apologies for long post, but from reading above issues can anyone please confirm ....
1) Is half graphic normal when going into download mode? .... or does this point to a previous incorrect or unfinished flash issue?
2) I have downloaded proper .pit flash (LT02) file and original firmware flash for my Tab3 ..... can I flash this any other way other than using Odin ....eg is there any bdm flash method (direct hard wired) flash method to motherboard from external programmer ....like they use for car ecu flash recovery?
3) As I dont know exactly whether Tab3 was rooted / flashed with wrong firmware / incomplete flash upgrade, is there a software tool that can attempt to list what firmware is on my Tab3 at present?
4) I can get into ADB recovery within recovery mode but havent a clue how to use this method .... is this a possible recovery method to use, as I can see SMT210 ADB device in PC device manager when going into recovery mode?
many thanks in advance for help, :good:
Tab3SMD
OK all, here's more info .......AND another additional issue!
I got stuck back in again tonight because not knowing anything about Tab3 ADB recovery mode was bugging me, so here's what extra I've done so far
While "poking my nose" into tonnes more Xda forum troubleshooting guides I discovered I might need PitMagic tool to try and sort my .Pit partition error via ADB recovery mode.
I tried to find Pitmagic but discovered this is now part of EFS Professional, so downloaded EFS Pro and found this got me nowhere as I needed to also install Android SDK .... which also requires Java Development kit, so I downloaded the full Android Studio and Java JDK 8u91 and installed all (about 1.2Gb and requires ~ 4.2Gb hard drive space!)
Anyway, I now ran Android Studio and then ran EFS Professional, opened my Tab3 into ADB recovery mode and connected Tab3 and PC via usb .....
All looking good EFS reported
Initialising ADB server ..... Okay.
ADB server is running!
Searching for device..... OK
Connecting to device .....OK
Checking device status .....
THEN BAMMMM ....popup from EFS
Connected device is currently UNKNOWN
Please ensure ADB server has been authorised by the connected device by confirming your PC's RSA fingerprint, then press OK to continue
like, wtf! .... one step forward and 6 back!
Can anyone please tell me what this means or better still how to proceed from here?
Anyone?
Anyone??? .....Tab3 is still soft-bricked
I did figure out how to use ADB flash recovery mode using PC.
Unfortunately this also did not allow me to flash any firmware (original or custom) due to admin permissions
(I think this is due to USB debugging not activated within Developer options).
I'm sorta banging my head off the wall with this one .... a bit like what came first? egg or chicken?, because since Odin isn't being recognised by the PC, I cannot flash rom and even though the PC fully communicates with Tab 3 in ADB mode, it won't allow me permission to sideload any flash files because I reckon I need root based permissions, and since the darn thing isn't booting fully, I cannot manually change anything!
I then started thinking about trying to sneak around this permissions issue by flashing CWM or TWRP, but again flash fails due to no permission.
All in all, for me this has been a great learning experience tackling the multiple Android recovery modes, and since I feel so close to cracking this non boot issue, I hate to give up and bin it.
Perhaps someone with much more experience can please help me here?
Is there any way of forcing superuser status on this Tab 3 SM-T210, so as to allow me to flash stock rom via ADB recovery mode?
many thanks in advance for your help,
Tab3SMD
I don't know how this happened, I tried to update to MIUI 10 and now TWRP says I don't have an OS and fastboot just boots on & off, on & off for eternity.
How can I reset it? When I tried updating with TWRP I got some weird error and now this happened. Is it possible to do an ordinary factory reset from TWRP or fastboot? Also, I can't plug my Xiaomi MI6 into the computer with USB-C. Some time ago I dropped it with headphones connected to the USB-C and the connection ONLY works for charging. Headphones don't work, and I don't think it works on the PC either. UNLESS, there's so program I need for the computer to connect to the Xiaomi, but plugging it in to the PC it doesn't react or the computer says it doesn't know what it is.
download fastboot rom, and flash it with mi flash.
zilan said:
download fastboot rom, and flash it with mi flash.
Click to expand...
Click to collapse
Hi! I have the Mi Flash program, but when I connect my Xiaomi MI 6 to the computer, my computer keeps saying it doesn't recognize the device and I can't refresh in Mi Flash to find my phone
Bump.
Well I could not wait anymore, I bought a new phone but I still wanna try fix this phone to sell it.
Is this forum dead?
Similar problem here. Help guys!
Download a custom ROM and put it into a flash or sd card then connect it to your device through OTG and wipe system vendor cash data but DO NOT WIPE INTERNAL STORAGE, then just flash the rom and reboot .
Hey, I guess i've bricked my beloved Mi6.
Here is the facts.
I was using global beta 9.6.27 and as Xiaomi said they won't update it anymore I decided to go back to Stable Rom.
As always I used XiaomiTools V2 and everything worked perfect until my phone starts for the first time.
As soon as it started it showed the following message:
"Find Device storage corrupted. Your device is unsafe now"
Well, it seems the system is here
But as I follow the steps I can't connect to network (wifi)
I can login at google accounts using 4g.
But when I reach the screen for Mi cloud account login
It shows the following message:
"Could'nt check device security info. Can't get device status, wait a minute or two and try again"
And I can't go over it.
Please, do someone know what can I do?
A few more information.
My bootloader is unlocked.
I can use TWRP but I can't transfer a custom rom to storage.
When I try to use miflash it returns the message: "can not found file flash_all.bat"
I saw something about a problem on persist.img, but when I try to install the file trought adb it shows the memory is locked.
malakobakko said:
Hey, I guess i've bricked my beloved Mi6.
Here is the facts.
I was using global beta 9.6.27 and as Xiaomi said they won't update it anymore I decided to go back to Stable Rom.
As always I used XiaomiTools V2 and everything worked perfect until my phone starts for the first time.
As soon as it started it showed the following message:
"Find Device storage corrupted. Your device is unsafe now"
Well, it seems the system is here
But as I follow the steps I can't connect to network (wifi)
I can login at google accounts using 4g.
But when I reach the screen for Mi cloud account login
It shows the following message:
"Could'nt check device security info. Can't get device status, wait a minute or two and try again"
And I can't go over it.
Please, do someone know what can I do?
A few more information.
My bootloader is unlocked.
I can use TWRP but I can't transfer a custom rom to storage.
When I try to use miflash it returns the message: "can not found file flash_all.bat"
I saw something about a problem on persist.img, but when I try to install the file trought adb it shows the memory is locked.
Click to expand...
Click to collapse
You can use an USB memory stick (with an usb c otg) to flash custom rom from it.
mArIuS% said:
You can use an USB memory stick (with an usb c otg) to flash custom rom from it.
Click to expand...
Click to collapse
I have to buy one, as soon as i buy one.
mArIuS% said:
You can use an USB memory stick (with an usb c otg) to flash custom rom from it.
Click to expand...
Click to collapse
I tried it but the device do not recognize the otg conection. I tryed other versions of twrp but it still didn't recognize.
Any other ideas?
malakobakko said:
I tried it but the device do not recognize the otg conection. I tryed other versions of twrp but it still didn't recognize.
Any other ideas?
Click to expand...
Click to collapse
Did you mounted otg from twrp menu? It's strage that it doesn't see the otg....have you wiped data storage? If you can't wipe from TWRP you can wipe it via fastboot.
-Edit- Do a factory reset, wipe dalvik cache, cache, vendor, system and internal storage, wipe data, restart to recovery and try to put a file on internal storage.
Hello guys.
As my last option before EDL I had the idea to try a miui 9 rom and it flashed.
Phone is working as it had never happened.
Thanks for all the help.