Good morning folks,
My knowledge is very limited but I'm hoping to soak up information here.
I have an old galaxy s5/s6 that my child destroyed quiet a few yrs ago. Lately I've been tempted to try and fix it myself, and recover the data off it.
It would require me to physically transfer the circuit boards onto a donor phone which I'm semi confident in doing.
Ive searched on here, found the guide on TWRP and I'm trying to understand it all.
My query is this, will I be able to recover my data when I'm finished or will I be spending hours upon hours on this, just to wipe the data regardless.
Ps: once the phone is functioning, I'm assuming it will still have a screen lock enabled, which is why I am unsure if I can recover the data
Thank you in advance for your input
Related
I have a 6 or 7 month old Kaiser branded by AT&T. I got seperated from it late last week, so it ran it battery down till failure. When I went to recharge the phone, it started attempting to boot, staying at the AT&T globe screen and then appearing to boot again, (black screen and momentary vibrate.) With a bit of searching I found the suggestion of boot to loading screen and leave it there to charge. After 6 hours, the battery has a measured voltage of 4.17V so that should be enough, but the phone continues the booting loop.
I tried hard resetting with the two keys and stylus. The phone acted like a normal hard reset with the questions, but when it tried to boot, it continued the reboot loop.
My question, do you think I should attempt to reload the stock AT&T ROM?
I'm new at this so there's a large learning curve. If you guys think this is a low probably solution, then I'll sent it back / buy another one and save the long learning curve. I use this for business so I could spead the learning curve time writing software I get paid for writing.
Thanks,
Bernie
your phone got damaged from battery drain? is that possible?
i think your phone has another problem... i really dont think the battery drain was the reason...
can you go to bootloader if so try flashing new ROM (you will loose data) but again you said you have performed hard reset (partial HR) so your phone is clean!
if you want send your phone back - yes you need to get stocked ROM and stocked SPL back
BernieHunt said:
I have a 6 or 7 month old Kaiser branded by AT&T. I got seperated from it late last week, so it ran it battery down till failure. When I went to recharge the phone, it started attempting to boot, staying at the AT&T globe screen and then appearing to boot again, (black screen and momentary vibrate.) With a bit of searching I found the suggestion of boot to loading screen and leave it there to charge. After 6 hours, the battery has a measured voltage of 4.17V so that should be enough, but the phone continues the booting loop.
I tried hard resetting with the two keys and stylus. The phone acted like a normal hard reset with the questions, but when it tried to boot, it continued the reboot loop.
My question, do you think I should attempt to reload the stock AT&T ROM?
I'm new at this so there's a large learning curve. If you guys think this is a low probably solution, then I'll sent it back / buy another one and save the long learning curve. I use this for business so I could spead the learning curve time writing software I get paid for writing.
Thanks,
Bernie
Click to expand...
Click to collapse
If you already have Hard-SPL installed and it is a version capable, you may try to put the Rom with a Radio onto the Micro-SD card and re-flash the phone that way. I had an issue where i got a boot loop and it turned out that flashing the radio fixed the issue. I hope you at least had a current backup prior to the hard reset because as of now, there is no way to retrieve it
No worries on the backup, it's backed up daily and I only use it as a data carrier. The only drag of the reset is the time of reloading apps.
I agree it may be more than just software issue due to dead battery, but I have to try everything I can. I've back on my old Moto smart phone and it's just not the same, hahahaha.
Now back to studying Kaiser ROMs and how to.
Bernie
As a follow up for anyone who runs across this in the future. I flashed the original AT&T rom and the problem still exists. I spoke to tech support yesterday and they are mailing out a new/reman replacement. So the problem appears to be terminal.
Thanks guys for trying to help.
Bernie
i will be recieving my new at&t tilt on tues. i have been reading alot about it over the last few days and i have noticed alot of chatter about having a bunch of un-necessary software pre loaded onto the device. i was wondering if anyone had any good ideas on how to optimize mine in the easiest way possible.. this will be my first smartphone running windows mobile so plz forgive me if i dont understand some stuff. thanks in advance for any ideas..
The first thing you should do is read all the wiki's that you can on this site. I came to this site many months ago and through using the wiki's I managed to learn how to flash a new rom (think of it as an altered version of windows mobile), how to change spl's (the equivalent of a computer's BIOS), flashing new radio's (The phone's parameters for call quality, signal acquiring, and gps capability), and now I'm cooking my own rom and hope to have it ready by the end of the month. Search for answers to your questions first so you don't get flamed, but if you need to post, know that these are probably the most knowledgable people around for this and they will go out of their way to help you. HOWEVER, know this, after you become accustomed to flashing your phone, it's a nonstop never ending addiction to reach perfection.
thanks so much, i found the wiki's now and am reading thru them..
Don't get overwhelmed when you try this stuff. Follow the directions and and don't try to do too much at once. Have fun, Welcome to the forum
One quick way to get rid of a lot of the bloat is to do a hard reset of the software ( hold down both soft keys and hit reset button by USB port with stylus, when prompted hit green button. If no prompt to"hit send button" then you did it wrong) then as soon as the customization screen comes on do a soft reset (same as hard reset without holding soft keys.)
This won't do much but keep a lot of ATT specific software from being installed. IT is a start until you are comfortable with flashing.
Also you might need to reset ATT settings for internet if you do this. I am not sure though.
I'm still blown away at the amount of people that are posting questions concerning some problem they have with the flex. Mostly soft brick questions. And 8 out of 10 of those questions have been answered and asked in another thread already.
I mean I get that when we fumble up we panic and just want the quick fix and the answer right now... But come on people unless you're a seasoned developer don't flash, push, fast boot, sideload, delete, add, change permission to, use as a floatation device, or modify anything on your phone without first taking the time to research, ask, and or get a little bit of a grasp on the theory of what it is you are wanting / about to do to your lifeline and main source of communication.
I am in no way a seasoned developer or even claim to be a developer, I'm a themer. I can decompile and modify then recompile deodexed apks to be themed the way I like. Or modify other themes to be compatible with different theme engines. And I've bricked my flex a fair share of times. But I did it testing for others work or for my own attempts at getting recovery imgs working for the flex. So for the love of not being so stressed and filling up the forums with repetitive questions, please do your homework and take the time to find out if someone has tried it already or asked some of the developers why or why wouldn't "your idea" work. I think you'll be amazed at how much you'll actually learn about logic that is Linux and android. I know I have more so with this phone than any other and from PLAYFULGOD, DFUSE, AND KINTWOFAN than I have anywhere else.
Well I´'m guilty as charged.
The problem to me, is that even for a fairly experienced flasher like myself (I too, have decompiled and recompiled apps ((just a few times though)), the G-Flex can be tricky like no other phone I've had. I've never had to ask for help with my HTC One M7 or M8, Nexus 5, LG G2 and the list goes on.
The G-Flex is simply more prone to soft bricking in my experience and thanks to the unpopularity and little documentation about the phone as a result makes it hard to find specific solutions sometimes. Different scenarios that differs from others and they all need different solutions at times and stuff works randomly too at times making it even more tricky.
I can only speak for myself but that is my experience. I don't use it as an excuse though =)
I feel ya. Especially on the stuff working randomly. Like the "offline method" to return to stock. And I seem to be the only one that is having any luck returning from soft brick using the LG PC Suite software that comes on the phone. The last 10-15 times I've soft bricked, be it on 4.2.2 or 4.4.2, I've been able to plug up in download mode and restore UPGRADE ERRORS with it. Puts it back to stock kit Kat uprooted and wiped clean. But that's fine I keep a twrp backup on my pc and thumb drive w/otg cable so I can restore as soon as I'm back up and running.
First, I will say that i'm not a developer. I am familiar with backups, rooting and custom roms. I'm just at a total loss with a total loss phone :/
So here's the rundown of my issue/s with my Moto Turbo (XT1254)
The phone is completely "unmolested." My phone is stuck in boot loop, currently. I did bust my screen a few weeks back but it had been working just fine. I picked up my phone to check texts, and I saw the "updating 24 of .... apps." Once finished, it's been stuck in a boot loop since. (Odd thing, my screen now shows split Moto image when trying to boot. Ex: a slot machine with only 2 roller wheels that wont match up)
I have tried to clear the cache several times with no luck of it booting up correctly. I do have files that I was trying to recover since they are not linked to a cloud account, and was trying to avoid a full on reset. I did, however, get frustrated and even tried to reset it back to full factory settings. That did not work either. So, all this being said, I'm back to trying to recover my files (my daughter's first year of life, family stuff, etc), since I cannot get it to even preform a factory reset. Does anyone have some guidance or same issue on this matter? Again, I am trying to salvage my files now while stuck in soft brick / boot loop status.
Thanks any and all who can help me with this!
******* Solved********
I have better diagnosed and fixed my own issue. I'm sorry I don't have pictures or video to better document what I did, but in short, it was as simple as replacing my damaged screen/digitizer, with a new one.
My theory was that during the update, the phone checked over it's systems and found that the digitizer was non-responsive in a few very small areas (this I already knew from using it a couple weeks with the screen damaged) and it somehow caused it to go into a boot-loop. My experience with fixing Playstations 3's, helped shed some light on this for me. I had a PS3 i thought was in good working order, updated firmware to it, and it bricked the system. Come to find out, the blu-ray laser head was no good. Upon the firmware doing system checks, it found that was bad and ended up bricked.
I did replicate the problem by switching the broken screen and new screen back and forth 2 more times after the initial fix. Upon disassembly, (youtube for teardown vidoes) you disconnect the battery from the logic board anyways, so when you boot the phone up, it does a app check and system check again. Every time the damaged screen was connected to the logic board and then powered on, it would end up in boot loop. The new, undamaged screen, would do the required checks, then boot up like normal.
I will do my best to borrow/rent a camera soon, so I can make a short video to show this works.
I'm not going to promise this will work for everyone but with replicated results, hopefully it's a fix for someone!
I hope
Hi guys, I have a situation, I have a tmo S6, few months ago i started having problems with my usb port, I could charge my phone but my pc wouldn't recognize my phone to transfer data, i had a message "USB device not recognized". as i said I could charge. My problem got worse because last week i received tmo's upgrade to MM (I was in LL). I took the bad decision to take the upgrade, because once the installation was done, my phone tried to reboot and it got stuck on the "Galaxy S6" logo. I have already wiped factory reset and cache, but it's still stuck.
I cannot re-install with Odin because pc does not recognize my phone. Before upgrade I was on Lollipo OJ7 stock and rooted, but now when I go to recovery, I get PD1 recovery menu, I guess PD1 got installed but don't know why it got stuck.
Please, is there a way to rescue my phone??
Thank you
When i bricked my s4 i had the same issues you speak of. Your pretty much helpless to bringing your phone back. There is a solution though. Its called jtag and if things havent changed recently you should be able to find someone on ebay or amazon who you can send your phone to that will take it apart and solder wires to the motherboard. In doing so it bypasses the usb port altogether. Then they can load firmware back onto the phone. I was lucky enough to still have my hard drive intact with all photos, songs, and apps. It cost around 30$ and its usually all done within a week. I wish i could tell you a simple way but unfortunately its the only solution i found when i had this problem. Make sure they have a good rating and just look up your phone followed by jtag repair. Good luck i hope you find a more simple way of fixing. If not give it a shot. I mean you really only have 30$ to lose.
Hey, thanks for your answer, that's a good option, i will search for this jtag service online, I hope i can get it fixed. Just like you i'm running out of options and as you said it's on 30 dlls to try. Thnaks man.
No problem glad i can help. Hope all goes well and your back with our s6 family shortly.