Hi everyone,
I have a Xiaomi Mi4w, and I had to repair my flex cable because it broke.
After that, it started to charge normally, but it was very very slow the performance, all of it. I hardly reset the phone, change the ROM... even I cleaned all the photos and personal data, but the problem persist.
What can I do?
Regards
Up
any idea?
Maybe contact Xiaomi support or go to the store where you replace it
Sent from my Xiaomi MI 4 using XDA Labs
Okay, I went to the store and they only could fix flashing and old chinese ROM, it worked but when I tried to flash a new ROM (previously i did the partition union) it gets sooooo slow, and I have tried everything:
- Flashing with Miflash an old an a new fastbootROM, (official)
- Flashing with TWRP, new and old CROMs
- Tried to restore with a nandroid backup of my mother's phone (its the same as me)
- Flashed with MiPcsuite, and nothing
What can I do? Maybe sell by pieces , hope not
Related
Hi Guys...
I got a Galaxy Note GT-N7000, and its been more than a week i tried to revived it using the any method i've found in this great forum.
So let me tell u guys the stories of my Note :
1. It was always updated OTA so the last ROM i used is Indonesian Note ICS 4.0.4
2. One day (last Friday) while i was browsing Internet using it, it suddenly got very hot, and the battery seems like draining very fast
3. In the mid day it reboot by its self, and entering countless reboot... a never ending reboot
4. So i tried to enter recovery, and yes sadly i've might triggered the emmc bugs by doing factory reset. But i'm not sure i've done it or not, coz i've a CWM recovery installed.
5. Anyway then i tried to flash stock room found in dr.ketan's thread...many thanks to him for those collection using PC ODIN and i got the "factoryfs" stuck problem
6. I also tried to flash countless kernel over and over, tried install Stock GB and ICS, tried RocketROM, CM10 and it all failed. In dowload mode i still got a Stock Firmware installed. So any ROM i've tried to install using Kernel didn't succed.
7. So i decided to take it to Samsung Service Center nearby, and i found that my battery is BAD, it wont charge (wonder would it because of the battery i got that problem in the first place). Since i got this Note for around 8 months, and the warranty for the battery is 6, the make me bought the new one, ordered and available in 2 days.
8. So I get back to the service center, put the new battery restarted the phone, and it stop on samsung logo (no yellow triangle there). So I complained, and they look into it, and said we may try to install new software, but there's a risk that your Note got damaged. They said the risk is mine and they wont have any responsible for it.
9. So furiously i bargain about my Warranty (12 month), coz the said that i've updated the ROM my self, so i explained to them that it was OTA's update, all i do was press YES, and they said even OTA official update will cancel my warranty. Its getting weird, i got angrier and they just said its their company procedure so there's nothing they can do to help me. So Samsung Indonesia will cancel warranty for every attempt to update the ROM OTA's, only their service center is allowed to do so. Wasted my valuable working hours there...
10. So i get back, determined i officially will do anything to get this Note life back. So i started to look at Forrest1971 (many thanks to him) thread about bricked note and tried many kernel and got one working with adb (T-Kernel V0.9) doing the checking and found faulty partition 9 and 10 and doing the step and finally got the partition fixed. Lost 3GB of space.
Then here came the real problem :
1. Still wont work with ODIN, stuck at Factoryfs with stock ROM GB N7000DXLC2_N7000OLBLC2_N7000DXLC1_HOME.tar and ICS N7000DXLR5_N7000OLBLR2_N7000DXLR1_HOME.tar. But working fine flashing Kernel so my guess it is not the connection problem. I've tried on 1 PC, 2 Laptops, 2 OS (Win7 32bit and WinXP 32 bit) still the same.
2. Then i tried to flashing via Kernel (CWM, Abyss, T-Kernel, CM9 Safe Kernel) i got to do trial and error coz not all ROM can be installed using any given Kernel. Seems that T-Kernel v0.9 is working for most of the ROM. Sorry i didn't keep note about the kernel-rom coupling. Here is the list of ROM i've tried :
cm-9.1.0-n7000 + gapps-ics-20120429-signed
cm-10-20121209-NIGHTLY-n7000 + gapps-ics-20120429-signed
RocketROM v2 XXLS7_stock_odexed
SuperNexus-N7000-BUILD5-20121017 + gapps-jb-20121011-signed
RocketROM_ICS_XXLPY_v1
3. All of those ROM came out with the same problem :
- Freezing on the Samsung/Mod Logo Screen (Got very HOT)
- Entering the "Andoid is Upgrading" and then updating Apps but stuck at random number (# of ###) (Got very HOT), i've tried to wait overnight but stay on the same number
- Succeeded boot up but Freeze after couple of minute (Got very HOT)
4.All those problem seems happened randomly, but most of the time it happened like this :
Stuck and Logo Screen - Reboot by me - Stuck and Upgrading - Reboot by me - Boot fine, but freeze very soon - Reboot by me, and back to the Logo stuck... (but still sometime its just random), the only thing same that it got very hot.
5. This is my last resort, i'll try to flash Supernexus, CM9 or CM10 without the GApps. Now i'm on Supernexus ROM, not yet freeze while i'm typing this. But without the GApps i wont have G-Play, and cant reinstall Apps that i bought in G-Play. Dilemma...
So any thoughts or advices will be greatly appreciated...
I really like this phone, wish i can revived this phone... :fingers-crossed:
Thanks B4 for any comment...
Well, i guess no one have the same problem here...
I'm running the rocket ROM ICS right now, this is the one ROM that got me closer to "STABLE" state.
Still got self reboot, most of the time when i'm using browser (Android, FF, Chrome), or after a long run on youtube or downloading something.
I've also tried the PA Experia ROM by AmniX : http://forum.xda-developers.com/showthread.php?t=2100083
But it was worse than rocket ROM ICS, more likely have the same symptom with the CM9/10 i've tried.
So seems like i've to manage to use this defect/handicapped gadget... :fingers-crossed:
diasdroid said:
Well, i guess no one have the same problem here...
I'm running the rocket ROM ICS right now, this is the one ROM that got me closer to "STABLE" state.
Still got self reboot, most of the time when i'm using browser (Android, FF, Chrome), or after a long run on youtube or downloading something.
I've also tried the PA Experia ROM by AmniX : http://forum.xda-developers.com/showthread.php?t=2100083
But it was worse than rocket ROM ICS, more likely have the same symptom with the CM9/10 i've tried.
So seems like i've to manage to use this defect/handicapped gadget... :fingers-crossed:
Click to expand...
Click to collapse
I would complain to the service center. It's absolutely rubbish that an ota update voids warranty, they're lying through their teeth and I wouldn't stand for it. So long as you have no trace of custom rom or root, they are required by law to fix the phone or replace it within 12 month warranty. If you'd left traces of root or Cwm that's a different story.
Try a second repartition, often a first scan will not find all bad sectors, run through it again just to be safe. Also, after repartitioning its usually the case that stock or tw based Roms won't work without freezes and reboots because they occupy too much space on the emmc. You're best with cm or aokp Roms.
Sent from my GT-N7000 using xda premium
Hi guys. First post. Made an account after struggling to fix my phone.
Here's what happend.
Bootloader unlocked, rooted and flashed couple of roms multiple times with no issue. the last rom i flashed was Infected Rom 5.0.2 YUGA , worked fine. i tried to UV the phone but the UV app said that the kernel was not supported. now after reading that , i googled and found a kernel that said it was UVable and for 5.0.2.. (maybe i made a mistake here)
so i downloaded and it said i have to whipe dalvik cache and install via recovery. so i did that and well... the phone never booted afterwards.
When i plug via usb to pc , i hear the usb detecting sound and thats it. even in flashboot / fastboot mode, it just makes sound and thats it. no vibrations. no led. i tried power + volume up. etc. ADB cmd does not detect either.
battery was around 40% around that time... maybe that was the issue ? what are my options here.
i got it used and so theres no warrenty. is it done for good ? do i need to charge it overnight ? will replacing maybe the motherboard fix the issue?
please help. ive tried searching every where for a solution.
If you flashed a kernel meant for a different device, it may have written the boot.img to the bootloader partition, causing an irrecoverable hard brick
I flashed this "Forest-LP-Kernel-V5"
oh man ... will replacing some internal parts help .. like motherboard ?
Forest - that's a Samsung kernel I believe. Need to replace mobo bro
shoey63 said:
Forest - that's a Samsung kernel I believe. Need to replace mobo bro
Click to expand...
Click to collapse
yep its fixed now . albiet now its a c6602.
Yes, its repairable by changing the nand memory its expensive but ive done it un samsung handsets so can be done un son y aswell
Sent from my Galaxy S3 R530x Cyanogenmod 11 using XDA Free mobile app
Hi all,
I downloaded the latest TWRP from https://dl.twrp.me/i9305/ - twrp-2.8.7.0-i9305.img.tar 8.1M
I installed it with ODIN. The flash was a success and when the phone rebooted the touchscreen was unresponsive.
I have tried another version of twrp for this phone and I can get into twrp, but the touchscreen doens't work. I tried replugging in the ribbon lead for the digitiser and that made no difference.
Do you think its a software problem or that I have fried something?
Many Thanks
Andrew
Hi,
there are plenty of issues with TWRP and 2.8.7.0. I'm actually surprised you could even boot up your phone. The new recovery messes up with partition sizes and some other things.
I hope you have a backup of the current ROM as I suggest you to install Stock ROM again and stay on TWRP 2.8.5.0 and see if your phones works normally again
Hi,
thanks so much for replying. I still have the stock rom. All I have done is install twrp. I have tried doing a factory reset and it made no difference. I can still use the buttons on the phone, but the touchscreen remains unresponsive.
So if I download the stock rom for the phone and install you think it might make a difference?
Andy
Update:
Downloaded and installed stock rom from samsung (4.4) ... installed with success via odin. The phone boots and the screen is still unresponsive. I just cant believe I have broken the digitiser by installing twrp?!
Andy
Hi,
sorry for the late reply. I didn't get a notification via tapatalk. But anyway to come back to your issue: it's the first time I hear that a "corrupted" recovery could break the digitizer. I did the same mistake with the broken recovery but fortunately no issues afterwards. But apparently it's possible judging by some google search results.
I never had such issues and I don't know how to help you. Maybe there is a possibility to fix it.
Thanks for your reply
I hope there is a way of fixing it. It doesn't seem economical to fix this phone? The digitiser kit is around £60 ... Plus because I can't be 100% why this happened in the first place, it might happen again with a new digitiser?
Thanks
Andrew
I was looking here in Germany right now what I would have to pay for fixing the digitizer - between £50 and £60 as well, some even charging a little more. For £80 I could get a decent looking used S3 4G.
If I were you I'd rather buy another S3 again (or any other device) instead of trying to fix the broken one.
Did you tried to Flash stock recovery
So I did a big mistake,I tried too many custom roms and I think I messed up my phone. My current custom rom is Resurrection Remix.
Few days ago my phone was having a weird problem,my recovery was gone,and the phone's screen turned black after 2 mins of booting up.However this issue solved automatically,I reinstalled recovery. ( I should have reflashed the custom rom,but I didn't:crying The settings was still missing,but I ignored it as there was not much use of settings.
Fast forward to today's morning , the phone was at 7% I don't know what I thought but I decided to give it a reboot.AND now my phone is not starting(It's not bootloop ,the phone is not even starting up).The battery is not charging up(It's very difficult to get new battery for Nokia X2,that would be the last thing I'd want to do,that or either buying a new phone)
.There is no light,no vibration whenever I connect my charger.I got my charging socket changed but nothing is working.I think it's a software issue.
Please is there anything I can do to recover my phone? Anything?:crying:
make sure your battery is ok and charged.
then try to flash the phone using pc with "nokia x2 tools" and a custom ROM and recovery
hello everybody
this redmi note 9 global 3/64 gb was working just fine.
one day the screen became so lagy so i tried to factory reset it then the screen became totaly not responding so i took it to repair shop he said the touch screen was the problem so he replace it, and didn't work so the problem was not in touch screen.
then suddenly the phone got hard bricked i give it to many repair shop and they can't fix it, every repair shop said different storys, one said the problem is in motherboard's circuit, another one said the phone is global but the manufacturer put an Indian motherboard...
i lost a lot of money but the phone is not fixed
then this week i tried to check if the motherboard stills alive so i plug it on my pc then i saw the usb port of this phone on device manager, so i tried to flash it with sp flash tool,, i downloaded miui 13 fastboot rom (the phone was on miui12 before he got hard brick), i install drivers and bypass and i run sp flash tool i load all the settings, when i press start it says "STATUS_DA_HASH_MISMATCH".
i tried everything to solve this, but nothing, i saw many people who got this error message and i tried there solutions but NOTHING!
i'm not going to more repair shops because one of them stole my selfie camera, so this is my last hope.
i hope someone who has experience to help me.
rz_q said:
hello everybody
this redmi note 9 global 3/64 gb was working just fine.
one day the screen became so lagy so i tried to factory reset it then the screen became totaly not responding so i took it to repair shop he said the touch screen was the problem so he replace it, and didn't work so the problem was not in touch screen.
then suddenly the phone got hard bricked i give it to many repair shop and they can't fix it, every repair shop said different storys, one said the problem is in motherboard's circuit, another one said the phone is global but the manufacturer put an Indian motherboard...
i lost a lot of money but the phone is not fixed
then this week i tried to check if the motherboard stills alive so i plug it on my pc then i saw the usb port of this phone on device manager, so i tried to flash it with sp flash tool,, i downloaded miui 13 fastboot rom (the phone was on miui12 before he got hard brick), i install drivers and bypass and i run sp flash tool i load all the settings, when i press start it says "STATUS_DA_HASH_MISMATCH".
i tried everything to solve this, but nothing, i saw many people who got this error message and i tried there solutions but NOTHING!
i'm not going to more repair shops because one of them stole my selfie camera, so this is my last hope.
i hope someone who has experience to help me.
Click to expand...
Click to collapse
Try mtk auth bypass tutorials on YouTube
the DA file was not compatible with your device, mostly it just work fine with MTK_AllInOne_DA.bin, try looking for DA file that compatible with your device and try flashing it again. or here, https://m929.ru/_pages/mtk_bypass.html
loftheaven said:
the DA file was not compatible with your device, mostly it just work fine with MTK_AllInOne_DA.bin, try looking for DA file that compatible with your device and try flashing it again. or here, https://m929.ru/_pages/mtk_bypass.html
Click to expand...
Click to collapse
i installed the baypass tool on this link and i tried to flash using MTK_AllInOne_DA and DA_6765_6785_6768_6873_6885_6853 but didn't work