The situation is a little complicated, so I'll explain step by step. I appreciate any help, idea what what caused this or if I can do anything to fix. Please, write if you have even a little clue.
- The top speaker (earpiece) was faulty. I wanted to change it.
- I damaged signal antenna port on motherboard while changing the speaker.
- Anyway, phone was working in all this process. Just no signal.
- After, removing motherboard for a second time, phone didn't boot up.
- I flashed a custom rom via TWRP. (phone was already unlocked.). Didn't boot.
- I flashed MIUI via TWRP. Didn't boot.
- I flashed MIUI via Xiaomi Flash Tool. Didn't boot.
- I am able to enter fastboot and recovery.
- It's charging, without problem.
- It doesn't stuck on kernel phase (It passes the MI screen).
- It stuck on boot screen. I have waited really long times, more than 30 minutes.
Do you think, I f***ed up the motherboard? Why it doesn't boot? Please, share if you have any idea.
@baggord
If the motherboard was dead, you'd not be able to turn on your phone.
Sounds like software to me at the moment.
Some ideas:
Are you on the latest twrp version (3.2.3-0)?
Did you try reflashing latest twrp via fastboot (not from within twrp)
and then wiped all partitions (including mounting and also wiping vendor) following a formatting of the data partition (where you need to type "yes") following a reboot to recovery?
Did you try restoring the efs partition from a backup where everything worked?
Would also rather try a stable custom ROM to test.
Hi,
If nothing worked, follow the instruction of this video. It worked for me after dropping my phone in water.
Sorry for my poor English?
Phil_Smith said:
@baggord
If the motherboard was dead, you'd not be able to turn on your phone.
Sounds like software to me at the moment.
Some ideas:
Are you on the latest twrp version (3.2.3-0)?
Did you try reflashing latest twrp via fastboot (not from within twrp)
and then wiped all partitions (including mounting and also wiping vendor) following a formatting of the data partition (where you need to type "yes") following a reboot to recovery?
Did you try restoring the efs partition from a backup where everything worked?
Would also rather try a stable custom ROM to test.
Click to expand...
Click to collapse
I tried flashing twrp via fastboot. I've also tried stable custom rom and stock rom.
I'll try to format all partitions then re flash a rom. I don't have an efs partition backup. Can I backup in this situation or do you think it's already gone?
Thanks for the reply!
Kabula2000 said:
Hi,
If nothing worked, follow the instruction of this video. It worked for me after dropping my phone in water.
Sorry for my poor English?
Click to expand...
Click to collapse
Hi, thanks for the reply. I'll check it out.
baggord said:
I don't have an efs partition backup. Can I backup in this situation or do you think it's already gone?
Click to expand...
Click to collapse
An old efs backup could have been of use, as sometimes important things like the imei get lost and you would only be able to restore it via this partition.
Next time better make an efs backup right away and store it at a safe external place in case you one day might need it.
In this scenario it's too late.
If it's faulty you only backup something that doesn't help you later.
Might still be that your problem has another source.
Then, if we found out a solution and everything is working well again, of course you could make that backup.
Please tell us if the wiping and formatting changed anything.
Good luck!
Phil_Smith said:
An old efs backup could have been of use, as sometimes important things like the imei get lost and you would only be able to restore it via this partition.
Next time better make an efs backup right away and store it at a safe external place in case you one day might need it.
In this scenario it's too late.
If it's faulty you only backup something that doesn't help you later.
Might still be that your problem has another source.
Then, if we found out a solution and everything is working well again, of course you could make that backup.
Please tell us if the wiping and formatting changed anything.
Good luck!
Click to expand...
Click to collapse
I am out of my home town, currently. I will inform you when I get back to town.
Thanks for the replies.
@Phil_Smith
I talked to my brother since I'm out of town.
He wiped all partitions including vendor.
Reboot into recovery. (format data returned error, before reboot)
Then format data. (worked fine)
Reboot into recovery.
Flashed a custom rom.
It boot up!
Thanks.
IMEI stays by the way. Now we need to fix the antenna somehow. Phone is still alive, at least. Thanks again!
baggord said:
@Phil_Smith
I talked to my brother since I'm out of town.
He wiped all partitions including vendor.
Reboot into recovery. (format data returned error, before reboot)
Then format data. (worked fine)
Reboot into recovery.
Flashed a custom rom.
It boot up!
Thanks.
IMEI stays by the way. Now we need to fix the antenna somehow. Phone is still alive, at least. Thanks again!
Click to expand...
Click to collapse
Nice, glad that you're good again!
Related
i rooted my milestone a few months ago (g.o.t.) and recently i tried to install the shadowsmod gingerbread rom onto it. when i restart the phone it stuck at the Motorola boot logo (M). i can enter recovery mode and do a factory reset but the problem still remains. maybe i just have to flash the stock sbf to fix the issue but the problem is that my battery is almost deplete and that the phone wont charge itself so if i enter the bootloader it'll say: battery Low cannot Program. please help me, i searched hours long for solutions but nothing worked.
Thanks in advance
Srinath
Have you done a nandroid backup? If so, you must be able to nandroid restore the Milestone, if you still have some batery left. It is usually pretty quick the restore. And if done correctly, your "stone" will be back. Next time flash the phone only when you have a fully charged battery. That would be what I would do.
Hope it helps.
YESS thank you ! i am so stupid : i DID do a nandroid backup but for some reason i forgot it! it works it really works! thanks alot your a lifesaver
Glad I could help . But you went lucky. As soon as I send the reply I though to myself, if the flash is done through .sbfs it must erase the open recovery partition. So, no nandroid restore option. But I guess you where trying to flash the roms from within the open recovery itself. So that way i believe the open recovery partition still remais untoutched. Not shure though.
Anyway, it still worked. And that´s the most important thing.
See you around.
normally if you have this problem after install a new rom, you just need to clear the cache / dalvik cache and it'll fix it
i have the same problem but i installed a rom with Droid 2 recovery bootstrap. before flashing i maked a nandroid backup but i cant get acces to restore. anyone can help me?
just reflash stock firmware. i have Droid2 Global and haved same problem but, reflashed stock firmware, root and after install bootstrap recovery, worked for me. may be helped you?
Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?
isketch93 said:
Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?
Click to expand...
Click to collapse
I had 70% similar scenario ,but different error. i could boot into mokkee rom but crashed during initial setup ,below were the steps i used to fix it
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
got perfectly working Mokee ROM in MI3
bluethilak said:
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
Click to expand...
Click to collapse
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?
A nandroid backup is to be used in case of failure (and as a backup... but you should have backups anyway so data loss isn't the end of the world) - an app backup is so you can reinstall the apps with settings in Mokee.
isketch93 said:
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?
Click to expand...
Click to collapse
Nandroid backup is nothing but a complete backup of both Rom and Data.It will in a zip format ad gets saved in your internal memory
[Clockworkmod for CWM/TWRP for TWRP recovery]
http://www.makeuseof.com/tag/what-is-a-nandroid-backup-and-how-exactly-does-it-work/
Let me tell you How I handle my backup plans for my device because at least per week i will be changing the ROM.
1) I always save my contacts in Google contacts(So a normal sync will do)
2)I backup all app data and Message data using EasyBackup
:good::good:
I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?
bluethilak said:
...got perfectly working Mokee ROM in MI3
Click to expand...
Click to collapse
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps
isketch93 said:
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps
Click to expand...
Click to collapse
Dude banks gapps latest is for 5.1.0 lolipop ,mokkee is still in 5.0.x try other gapps ,PA or MInimal or get old Bank Gapps of correct lolipop version.:good:
---------- Post added at 10:06 AM ---------- Previous post was at 09:59 AM ----------
isketch93 said:
I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?
Click to expand...
Click to collapse
Clear some space at least 2gb temporarily in you Internal Memory ,Since you will be backing up your App Data,it definitely requires a lot of space .
So I decided to try out Ivan's Marshmallow ROM, knowing it would be a bad idea... I backed everything but the photos which were 2.5GBs and was too lazy to copy over. I wiped cache, but not user data, copied ROM to phone, rename to update.zip and updated through recovery(stock). Now it's stuck on booting and want to know if there is any way to recover my photos.
Keep in mind there is a functional MIUI ROM inside but it is named differently than update.zip so I don't know how to flash it. It turns on, boots on fastboot and recovery but can't do much... I could wipe it, but I need the photos....
Thanks in advance.
eXtrimist said:
So I decided to try out Ivan's Marshmallow ROM, knowing it would be a bad idea... I backed everything but the photos which were 2.5GBs and was too lazy to copy over. I wiped cache, but not user data, copied ROM to phone, rename to update.zip and updated through recovery(stock). Now it's stuck on booting and want to know if there is any way to recover my photos.
Keep in mind there is a functional MIUI ROM inside but it is named differently than update.zip so I don't know how to flash it. It turns on, boots on fastboot and recovery but can't do much... I could wipe it, but I need the photos....
Thanks in advance.
Click to expand...
Click to collapse
Assuming that you haven't yet extended partitions, stock phone has 2 system partitions. So if you're using system 1, boot using system 2 and vice versa. AFAIK, if you flash stock miui using MiTools, it wouldn't erase the storage on the phone.
The second partition seems unable to boot as well...
Anyway, if found out I could install twpr through fastboot, from where I could mount the sdcard.
As far as MiTools are concerned, last time I tried it, I think it erased everything.
The thread can be closed. Thanks!
eXtrimist said:
The second partition seems unable to boot as well...
Anyway, if found out I could install twpr through fastboot, from where I could mount the sdcard.
As far as MiTools are concerned, last time I tried it, I think it erased everything.
The thread can be closed. Thanks!
Click to expand...
Click to collapse
Glad you could work it out. Don't be lazy next time
I don't think I can edit the title so I'll write it here for anyone who wants to help: This problem is SOLVED. (Y)
So the matter is a bit complicated and I can't guarantee I even remeber everything I did but I'll try to include as much detail as I can:
I had the Stock Rom (OOS4.0.0) running, OEM unlocked & rooted when the OOS4.0.1 OTA notification kept nagging in the back of mind. I thought I should just leave it ago because I already had a feeling it would go wrong...
So I download the Full .zip and flashed it through TWRP 3.03-1 and after that it was stuck on the boot screen for more than 15 minutes or so. So I restarted it again and this time it booted butall my data was deleted and it gave me an error about the encryption having failed. But as you probably know, one can't flash anything on an encrypted phone so I checked back in TWRP and it was really encrypted. Checked back in the phone's settings: Also encrypted. I then used a tool to force decryption (it also wipes all the data) and I was back to square one.
From that moment on I tried: 1. restore nandroid (all partitions included [that includes EFS]). It got me to the booting screen, but when I unplugged it shut down and a reboot got me to the battery screen. I had 72% left so at this moment I thought it had nothing to do with it not booting at 72%. Then I wiped everything (checked every box in TWRP) and was left without any OS. Then I let my phone charge to 100% and re-restored the nandroid OOS4.00 and it worked but I had the Unlock-Bug, I was able to fix that. Then it booted but it wasn't able to recognize any SIM cards, so I fixed that by re-re-restoring with TWRP 3.03-0 (which automatically replaced 3.0.3-1 after the nandroid) and everything worked fine. until I went out today and realized I had no mobile data. I doubt it has something to do with EFS because everything else is working fine (calling, checking IMEI wih *#06#).
I then proceeded to check the APN and it looked ok, I then tried another SIM card (from the same provider) and it didn't change anything.
My provider is the german company 1&1 (1und1) but it uses vodafone APN.
I have no clue what to do right now so I am asking you guys for help.
Thanks in advance!
Well, first things first. On rooted devices with stock rom always flash a full/complete zipped image - never, never, never use an official partial image. And always wipe Dalvik/Art and common cache before reboot.
In your case now I would probably try to clean re-flash the current OOS image version (4.0.1). You'll find guides and downloads in the guides and rom section of this forum. Clean flashing your device requires you to completly wipe the data partition before flashing (the internal partition remains untouched). Don't forget to wipe Dalvik/Art and cache before rebooting. This will hopefully completly reset your device.
Inciter said:
Well, first things first. On rooted devices with stock rom always flash a full/complete zipped image - never, never, never use an official partial image. And always wipe Dalvik/Art and common cache before reboot.
In your case now I would probably try to clean re-flash the current OOS image version (4.0.1). You'll find guides and downloads in the guides and rom section of this forum. Clean flashing your device requires you to completly wipe the data partition before flashing (the internal partition remains untouched). Don't forget to wipe Dalvik/Art and cache before rebooting. This will hopefully completly reset your device.
Click to expand...
Click to collapse
First of all: Thanks for your reply.
I don't know if there was a misunderstanding but I only ever flashed the full 1,4gb .zips.
Also I am running 4.00, because I had to restore it as the 4.0.1 flash ruined my phone. Just now I flashed 3.03-1, wiped dalvik & cache and flashed the 4.02 .zip which I got from this [https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074] thread but it left me stuck on "patching image uncoditionally" or something and then I rebooted and now I am stuck on the +1 booting screen (not even the animation, just the +1 logo witht he "powered by android" signature in the bottom).
I have the feeling it's a software bug not related to what I did with my phone. it was just luck that I did not havfe that problem prior to my nandroid restore or something. I mean: Looking at it from a logical perspective: When you restore your phone with a full nandroid backup it should be exactly the same phone, shouldn't it?
Well, flashing the TugaPower rom might break the alert slider. To fix this you have to simply backup and recover the data partition. I don't know why this is happening but I believe that sometimes permissions to files and folders remain untouched in certain situations. Maybe someone else knows more details on this topic.
If you are absolutly sure that your nandroid contains all required partitions just try to wipe all cashes, data and system partition before recovery. But like I said before I would then clean re-flash your current OOS image version. In your case the error might possibly be some error resulting from faulty permission on configuration data. If it was a common bug more people would have reported it already.
If something broke and it can't be easily fixed... trying to return to point zero and resetting everything to defaults will possibly your best chance.
Inciter said:
Well, flashing the TugaPower rom might break the alert slider. To fix this you have to simply backup and recover the data partition. I don't know why this is happening but I believe that sometimes permissions to files and folders remain untouched in certain situations. Maybe someone else knows more details on this topic.
If you are absolutly sure that your nandroid contains all required partitions just try to wipe all cashes, data and system partition before recovery. But like I said before I would then clean re-flash your current OOS image version. In your case the error might possibly be some error resulting from faulty permission on configuration data. If it was a common bug more people would have reported it already.
If something broke and it can't be easily fixed... trying to return to point zero and resetting everything to defaults will possibly your best chance.
Click to expand...
Click to collapse
I have no problem with that, but my device does.
I can't flash anything because TWRP (bot 3.03-0 and 3.03-1) will be stuck at "patching system image unconditionally", ( I tried the full 4.02 .zip and the ful 3.54 .zip that I am 10000% sure used to work, because I used it before the Nougat release).
Wiping everything but Internal and USB OTG changes nothing.
If you have any idea how I can get to a fresh start, I would really appreciate it.
EDIT: I am sorry, I don't know what you mean by TugaPower Rom. I never installed anything like that - atleast not knowingly.
Due to encryption returning to OOS 3.X after having upgraded to Nougat is difficult. Just flashing wouldn't do. There's still an option to format data - not just to wipe it. Was boot, EFS and firmware partition included in your nandroid? Does the recovery still work now? Another Approach would be to use the Unbrick Tool.
Inciter said:
Due to encryption returning to OOS 3.X after having upgraded to Nougat is difficult. Just flashing wouldn't do. There's still an option to format data - not just to wipe it. Was boot, EFS and firmware partition included in your nandroid? Does the recovery still work now? Another Approach would be to use the Unbrick Tool.
Click to expand...
Click to collapse
So, I have the means to decrypt my device through a tool I found here on the forums last month. It does wipe all your data, though. Anyways: I was able to restore mobile data through an older nandroid backup (and yes: all my back ups include all partitions; glad I was smart enough to do that haha). That worked for me and made me come to the conclusion that the back up I used first was somehow corrupted. Then I restored the data partition using my most recent nandroid back up and now I am back in the game. Thanks for all your help so far!
The only thing that kind of makes me worry is that I only get ~60mbit/s through speedtest even though I should get 200. I know I was able to get 200Mbit/s at some point using that phone, but I don't remember if it was with OOS 3xx or the OOS 4.00 update. So I can't tell whether it has something to do with me restoring the phone, my WiFi connection (a speedtest with my lan-connected desktop gave me 200) or just an android bug.
I'll wait until weekend when I have the means to test it with another 200k connection - and imho 60k is enough for anything I do with my phone anyways and I don't plan on reselling the phone in the future, so it won't kill me even if it is nandroid-related.
Linux/Android backups aren't always that satisfying. I often experienced diffences between what was saved and what or how it was restored. Most problems resulted in faulty permissions or missing file execution attributes.
Nevertheless, I'm glad your devices is working again. Keep that backup save, you'll might need it again... or hopefully not.
Inciter said:
Linux/Android backups aren't always that satisfying. I often experienced diffences between what was saved and what or how it was restored. Most problems resulted in faulty permissions or missing file execution attributes.
Nevertheless, I'm glad your devices is working again. Keep that backup save, you'll might need it again... or hopefully not.
Click to expand...
Click to collapse
Thank you, I just checked the wifi-speed with an iPhone 6 and it even got lower results (>30k) so I assume it has something to do with the WiFi itself at the moment and not with the OP3t.
And even if the backups are not always satisfying: I want to quote someone I read on some forums doing my research to fix this phone: "The seasoned user knows: A backup makes the difference between an awesome phone and a beautiful brick." That is a most evident truth to me now haha.
Hi everyone,
I really need help, I have tried everything I could think of and nothing works. So if someone more knowledgeable could help me, that would be great.
I followed the instructions in this thread https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
and everything went ok until I flashed a new ROM.
Current situation : Bootloop when I power up. Can still access TWRP recovery. Phone is recognized by flashtool/xperia companion/emma.
Tried to flash a new ROM with flashtool->error (can't read byte value), I tried de/re-installing flashtool and the drivers and different ROMs, always the same result
Tried to repair with xperia companion->error, can't complete
Tried emma->phone is locked
Tried sideloading ROM to flash through TWRP-> error
I don't understand how, even if I flashed a corrupted ROM, it could prevent me from flashing a new one over it?
Any ideas?
Thank you.
You can try xflasher tool as well.
https://forum.xda-developers.com/crossdevice-dev/sony/dev-xflasher-command-line-flasher-t2986634
But be warned - this is for more experienced users. I never tried it but it sounds like to be very powerfull.
For questions ask in xflasher thread... I never used it up to now...
But sometimes it helps to wipe cache/dalvik AND data from TWRP. Yes - all your data is away then!
Not nice to loose data but a bootable phone is even better...
Or flash again full ftf via flashtool. Wipe APPS_LOG/USERDATA (check boxes) but do not flash simlock.ta (if its there) !!!
This will wipe all your data as well..... While flashing, say NO to "fcs-script" popup.
. .
Thanks for the replies.
I tried different USB cable/port, no change.
I always selected to wipe everything in flashtool. I just got the phone so there was none of my data to save.
I will look at xflasher although, as you said, it looks intimidating...
. .