Hi Everyone,
First of alI, I will try to give a brief anamnesis of my situation. I flashed my W 3 months ago with arcco68's [ROM][ICS][4.0.4][IMM76L] CyanogenMod 9 Final Release that is founded here. Everything is going "ok" within in this time. But two weeks ago, My W is decided to go into boot loop without any reason (May be it has, but I did nothing for this). It always stucks at the boot animation logo. Since my home button was broken, I could not switch back to recovery mode, with conventional way. So, I went to recovery mode by using ADB tools, and made a full backup of the W with my TWRP recovery that is version 2.8.3.
The big problem is that it starts from now on. I gathered my Contacts2.db file from the backup, but I could not convert it to vcf file format with any ways that I have found on the internet.
1. https://askubuntu.com/questions/445997/how-to-convert-androids-contacts2-db-to-vcf
2. https://stackoverflow.com/questions/18955512/converting-db-to-vcf
These two scripts also fail at some point in the process. And I do not have code knowledge to solve the issue. And I also know, some site like this is giving free conversation service for this. But I do not want to share my contacts with them and I want to learn fishing, not eating fish. I would be very grateful to anyone who could contribute to solving my problem.
Related
I recently rooted my Galaxy Note 2 (GT-N7100) - following 'High on Android' web site instructions.
Everything went well and I installed Clockwork Mod Recovery (CMR) and I backed up then current ROM successful.
Recently, I got a new update to Gmail so, I decided to backup the ROM again. I ran CMR and I was prompted to name the backup file and I was prompted the phone would reboot and complete the backup.. The result was the phone went into a loop constantly displaying the boot logo.
I overcame the problem by re-rooting the phone using ODIN - the download mode was accessible on the phone.
However I spoke to soon: the phone became increasingly unstable and, it eventual Froze. I tried to do a factory wipe & re-root the phone - That left me in exactly the same position - at the boot logo, dead. I have written an email CMR & High on Android but, they have not replied.
I quickly realised I would have re-flash the phone completely and I sourced the correct files from 'SamsFirmware'.
That's the first question: the file I download was compressed and when it was decompressed it gave me two files;
N7100XXALJ3_N7100OXXALJ4_N7100XXALJ2_HOME.tar.md5 & SS_DL.dll
Q1. Can I run this tar.md5 using ODIN (PDA) function?
Q2. I have read that a file like this need to be further spilt? If so, How?
Q3. If spilt the file into component parts, how will I identify / set up the files to ODIN ?
Mild panic is breaking out here - it's the last time I will ever flash a perfectly working phone again. Any advice or practical instructions you can provide to recovery the situation will be warmly welcomed!
Solved - http://www.lockermike.com/how-tos/a.../unbrick-a-galaxy-note-2-with-stock-firmware/
Thanks for sharing your solution, it's always good to know should anything go wrong. I'm about to flash new custom rom in an attempt to unlock the phone too
Hello,
I was recently attempting to flash the new Cyanogenmod 10 ROM to my phone and I've found myself in a bootloop (the logo just continuously circles). I actually know what error I made to cause this, but the problem is, I have no access to any recovery menus anymore. All I can access is download mode. I can still use Odin and connect to the phone, but other than that I'm at a loss for what to do. I have backups of everything, I just need to get the phone wiped and back to factory set and start over. Unfortunately, without a recovery menu I don't know what to do.
What should I do from here?
Solved it.
For anyone that has this issue in the future, I plugged into the computer and ran Odin and was able to have it install a stock ICS ROM and I just started over.
Good job with solving the issue on your own! :good:
Your issue and solution had been discussed on these forums already. As a tip for the next time you have an issue, make sure to use the search bar first. Cheers!
New to XDA, so hopefully this is in the right place!
My problem
I tried to install a new ROM and it's gone badly wrong. First, I couldn't get the recovery bootloader to launch or to re-install. Then suddenly ADB wasn't working any more, and I was unable to boot up into the system.
Now I get boot loops with the Oppo logo. If I hold down volume up + power, I have access to Fastboot. I can use my Mac to send commands with Fastboot, but I cannot get ADB to find my device. Typing Fastboot getvar all gives me 'All: ' in response, which is not a good sign.
Attempted solutions
I've tried installing TWP and CWM, but both of them just end up booting to a black screen. At one point I tried to flash stock Oppo recovery and got a black and white flickering recovery screen for my trouble, which was unresponsive..so I wiped it and started over. I suspect it was not the correct recovery file, as I really struggle to find what are definitely the correct files now the OppoStyle Forums where I used to download recovery files no longer seem to be active.
After two days of reading various threads and trying solutions, I am really out of ideas now. So any help would be greatly appreciated!
Before embarking on this journey I cleared my phone of anything important, made sure it was rooted and enabled USB debugging. I also wipe everything from Fastboot whenever attempting any fresh flashes.
More context
I've had problems with my Find7 ever since I tried to unify my storage a couple of years back. In the end, I got unified storage to work but on a very old version of ColorOS. I had a lot of problems getting to that point, so from then I decided to just live with the outdated OS. But finally, the frustration of apps not being compatible got to me a few days ago and so I decided to try and install a new ROM. That's when my recent troubles began! I think legacy issues from my initial problems years ago may have contributed to the mess my phone is in now.
So what next?
Ideally, I'd love to get my Find7 completely wiped clean and a modern, stable ROM with unified storage working on it. But at this point, I'd settle for original ColorOS with non-unified storage again if I had to!
Hoping someone here has some suggestions I can try! Can't get worse surely
So my phone has been this way since Nov 2017, there are files that I need access to and would truly appreciate some guidance
I was experiencing issues with the bluetooth on nextbit previously so I installed a new rom after flashing the device. Once the rom also gave issues I decided to revert back to the Nextbit 7 OS and one fine day when the phone restarted it wouldnt go past the "nextbit" splash screen. Tried installing the OS again however the PC wouldnt recognize the phone anymore, switched laptop to a Mac and got the same issue
Any help would be greatly appreciated
It wont let me post a URL link. I have taken www out hopefully it allows to view the video, shows exactly whats wrong
youtube.com/watch?v=ImIk5CErWf0
It looks there's something wrong with the system boot, since it's reaching the blue boot-animation and it stays there (probably before loading the adb stuff). Fortunately u did unlock the bootloader and that annoying initial screen may be helpful this time, did u try to reach recovery or fastboot mode from there (pressing some volume key)? It's pretty hard for it to be broken there too and in such a case I would think about some hardware fault. Anyway from the recovery (I hope u have TWRP, if not install it with fastboot) you should be able to do whatever u want, including recovering your files or (re)installing a rom
Hello guys,
I am looking a solution almost everywhere and did not find yet.
My son received an update on his phone OTA on December 26th and launched its installation.
Phone is now booting in loop to the Main Menu.
I tried to flashed again the ROM that I downloaded on Xiaomi web site, but after the flash is done, it is back to the boot loop...
miui_BEGONIAEEAGlobal_V12.0.2.0.QGGEUXM_7b0e08bd84_10.0.zip
found here https://c.mi.com/oc/miuidownload/detail?device=1900375
I tried to flash a previous version of the system, but it is refused, thinking it is coming from an ant roll back system.
The only solution proposed is to send the phone to Xiaomi but data will be wiped out.
He used Xiaomi application note to write many things, but of course it is not saved anywhere, at least not by android.
Xiaomi does not provide any solutions.
Lesson for my son is huge… Always back up your data somewhere.
From what I found there are experts here who might have some ideas, solution …
Thanks a lot for any answers, comments.
You may try to boot the phone in Safe Mode if the boot loop lets you.
FivEawE said:
You may try to boot the phone in Safe Mode if the boot loop lets you.
Click to expand...
Click to collapse
I tried to push volume down while rebooting, but it is putting device in fastboot mode.
Thanks for the proposal.