Database Develop

Freezing problem.

I just got a replacement G1 and I did the one touch root and every rom i loaded kept having freezing problems, even stable 1.6 roms which i ran on my old G1. I even tried unrooting then re rooting via one touch and it just keeps freezing up randomly. Does anyone have any idea why, and a way to fix this?

When exactly does it freeze, after setup or boot?
If one of the above it's just loading and background services are running while sd is being setup too.

Mostly when i am trying to run an app or something like that. If i am switching from screen to screen it is fine. But when i go to like use a message or something. It sometimes freezes, other times it doesnt.

Update: When my phone is plugged in to a power source it has no problems at all. But once i take it off it is a matter of minuets before it freezes. Mainly when I go to the message app and then hit end. I am running the SuperEclair_XxKOLOHExX_v2.3 rom.

Be sure that you are running the latest radio and engineering SPL.

radio:2.22.19.26I
and i am running the danger SPL(1.33.2005) is that the same as the Eng. one?

ttyrawa said:
radio:2.22.19.26I
and i am running the danger SPL(1.33.2005) is that the same as the Eng. one?
Click to expand...
Click to collapse
Yes, Death SPL is fine....you could update your radio to the newest one and not worry about bricking your phone. Though I don't think its going to fix your freezing when off charger problems....it sounds like you have a very messed up phone...I would have called Tmobile as soon as I found out it was doing that and sent it back to get another replacement.

But when i run the original g1 rom(non rooted) it works fine

Have Froyo early what next?

I have put Froyo on my phone early as many others have and there are a few bugs on it, so what I am wondering is when it officially comes out will there be "some" additional updates since it is already on my phone or will I have to reinstall it with the official version from the market? What I am wondering is just update any further updates from the market with the Froyo I have? or with the public release in the next couple weeks install that? does it matter? if this makes any sense what I am saying LOL

I have the exact same question in my mind. Remember the 2.1-update?
-------------------------------------
Sent via the XDA Tapatalk App

My wife and I both have the Nexus One. I decided to stay on CM 5.0.7 Test 3 until he gets the chance to work on his 2.2 rom, I'm in no hurry.
My wife wanted it on hers because she wouldn't allow me to root her phone.
After putting 2.2 on hers there is some pretty bad stability issues. Her phone has straight up frozen at least 8 times since yesterday requiring a battery pull.
When he phone isn't being a temperamental babby its great but when it starts to chug the whole house of cards comes crashing down.
Since I rooted mine I just make nandroid backups and restore from that so life is simple for me but with hers how do I restore back to total stock?
Do I reboot into the bootloader and at the screen where I would typically apply the update.zip just use the restore option or would the restore option in the phones settings work? I.e Factory Default.
While she is semi tech savvy I just don't have the time or patients to deal with her phone issues right now so I guess she'll just need to be on 2.1 until the official release.

[Update] Froyo May Have Been Launched Prematurely
http://phandroid.com/2010/05/24/froyo-may-have-been-launched-prematurely/

rensky said:
I have the exact same question in my mind. Remember the 2.1-update?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
sorry I am a newbie 2.2 is my first update that's why I am posting this to see if I didn't f*** up my phone or something. other than that it seems to be working fine with a few bugs here and there and 2 things updated today from the market, so am wondering leave it be or get rid of it and reinstall the official one? thnx for responses

Enndr said:
My wife and I both have the Nexus One. I decided to stay on CM 5.0.7 Test 3 until he gets the chance to work on his 2.2 rom, I'm in no hurry.
My wife wanted it on hers because she wouldn't allow me to root her phone.
After putting 2.2 on hers there is some pretty bad stability issues. Her phone has straight up frozen at least 8 times since yesterday requiring a battery pull.
When he phone isn't being a temperamental babby its great but when it starts to chug the whole house of cards comes crashing down.
Since I rooted mine I just make nandroid backups and restore from that so life is simple for me but with hers how do I restore back to total stock?
Do I reboot into the bootloader and at the screen where I would typically apply the update.zip just use the restore option or would the restore option in the phones settings work? I.e Factory Default.
While she is semi tech savvy I just don't have the time or patients to deal with her phone issues right now so I guess she'll just need to be on 2.1 until the official release.
Click to expand...
Click to collapse
From what I understand, if you want to go back to ERE27/EPB54, you would need to either restore a Nandroid image that has those ROM's or download an unsigned original ERE27/EPB54 image.
When you say battery pull, are you actually physically pulling the battery whe the phone freezes? I've read a couple of posts/articles where that might be harmful to the phone and so what's recommended instead is to perform a soft-reboot.
You can do so by holding down the power button + volume down key + trackball at the same time. If done so correctly, the phone will automatically reboot in a few seconds.

Enndr said:
but with hers how do I restore back to total stock?
Click to expand...
Click to collapse
No can do. No unlocked bootloader = no regression. You either unlock the bootloader or live with Froyo.
I would consider a factory reset though, as I have no stability problems what so ever.

Phone becoming unresponsive after FRF83 OTA

I received my OTA to FRF83... and now my phone seems to be freezing up every so often while doing basic tasks... even waking up the phone sometimes freezes at the unlock screen. Anyone else getting this? My phone is UNROOTED and official. FRF72 ran fine... not sure whats going on but its REAL annoying.
I even tried factory resetting and still getting the same issues.
Any ideas? Can I manually go back to FRF72 somehow?

Can you clear the cache and dalvik cache via recovery, if you have stock recovery? I know you can if you have a modded recovery.
if not, then maybe it's an app or something hogging memory

stuff said:
Can you clear the cache and dalvik cache via recovery, if you have stock recovery? I know you can if you have a modded recovery.
if not, then maybe it's an app or something hogging memory
Click to expand...
Click to collapse
I just tried "clear user data"... thats about all I get with stock recovery. I don't think its an app considering I deleted everything and it still continued to freeze.
Can I delete Dalvik from ADB even unrooted?

I get frequent lock ups and freezing on an unrooted AT&T with 2.1. Seems too many apps load up and even though they may be in the background not using resources, the overall memory drops to about 25 MB. Go get ProcessManager from the market and kill the apps running. Some will restart but it will cure the lockups. I also disabled a handful of things on startup, stopped using live wallpapers and routinely kill apps to free up memory because of the lockups. Maybe Froyo 2.2 will correct this issue. Seems most of the rooted guys don't have any of these issues, so it must be this version of firmware.

Big_O said:
I get frequent lock ups and freezing on an unrooted AT&T with 2.1. Seems too many apps load up and even though they may be in the background not using resources, the overall memory drops to about 25 MB. Go get ProcessManager from the market and kill the apps running. Some will restart but it will cure the lockups. I also disabled a handful of things on startup, stopped using live wallpapers and routinely kill apps to free up memory because of the lockups. Maybe Froyo 2.2 will correct this issue. Seems most of the rooted guys don't have any of these issues, so it must be this version of firmware.
Click to expand...
Click to collapse
Like I said... I factory data reset so there where NO APPS. and the phone still comes to a screaching hault after a few minutes of jumping in and out of apps. It freezes to the point I have to remove the battery. Becomes completely unresponsive to touch.
As a side note, ive been using android since the first G1 on pre-order... I know how it works and how you need to use a task killer to keep stuff running smoothly... This however is extremely odd as it completely freezes.
again, only started after my OTA update to FRF83.
thanks for the input. I guess i'll have to send back my N1 for the forth time to HTC... getting pretty sick of this. That Iphone 4 or Galaxy S looks better everyday.

You don't need a task killer manager since 2.1. Froyo is even better at handling memory.
Sent from my Nexus One using XDA App

i noticed the same thing on my phone today...unlocked phone went from ERE27 to FRF50 to FRF83 yesterday......
today it seems to freeze...from time to time - i thought it requires a battery pull but if i wait long enough it will be ok again.
anyone know what the issue is?

rensky said:
i noticed the same thing on my phone today...unlocked phone went from ERE27 to FRF50 to FRF83 yesterday......
today it seems to freeze...from time to time - i thought it requires a battery pull but if i wait long enough it will be ok again.
anyone know what the issue is?
Click to expand...
Click to collapse
I'm glad I'm not the only one. Mines also an unlocked phone. Wonder if that has anything to do with it.
Ugh we need frf90 to come along and fix this!

The Same here
It happened to me right now, My phone hanged and I forced reset it, it happened one time when I was on FRF72 and one time now on FRF83. it was after a phone call and I couldn't unlock the phone, touch screen didn't work but it did work for power button menu so it should be a software problem, I thought it should be something incompatible between launcher pro and FRF 72 and FRF83 but it seems it is not the case.

I have the same problem. Went from ere27-frf50-frf83. I thought it was launcherpro so I uninstalled it.
Still getting freezes on unlock...and switching between Apps. Sometimes need battery pull sometimes just some time for the phone to catch up.
I had previously switched from frf50 back to ere27 because I couldn't stand the constant need to pull battery because phone freezes.
issues i have with frf83 is not as serious as frf50 so I think I will still stick with it for a few days and see what happens.
Just really need the official ota.
Sent from my Nexus One using XDA App

I just upgraded to the 2.2 (FRF83) yesterday, already had to pull the battery twice in one morning because it just froze up..
What the fu*k did they do! The 2.2 prerelease was fine hadn't had any crashes at all in the month I used it.
Edit; make that 3 times.. WTF!
Now, I'm extremely tempted to just root the phone but I was sticking with official builds for stability, I really didn't think it would get worse..

Yup having the same problem... Had to pull the battery twice today due to freezing and the same thing yesterday... It just started happening to me. Got 83 when it first came out, and its now starting to freeze. Idk what the deal is..
I still have no idea what these updates do.. What's different? I'm talking about the frf50, 72, and 83.. Froyo by it self seemed fine, what's new??
Sent from my Nexus One using XDA App

[Q] Rollback a Telstra Velocity help please.

Ok, first up I want to apologize for being a huge noob when it comes to smart phones, the Velocity is my first.
Ok, recently upgraded to stock ICS as was told by a Telstra store it would improve battery life.
Suffice to say I now need to charge my phone 2 times during the day, even with all non essential things turned off. Also while my 4g has picked up slighly, my 3g is almost non existent.
I work in a remote town and I usually dont have the luxury of charging the phone at noon, hence a dead phone by 1pm now (used to last all day fine)
Simply, I just want to take it back to the stock gingerbread it came with so I can at least use it again.
I have read through the forums for about 7 hours now, can't find what I need (noob remember)
I did find the holiday shipped rom collection post and D/L the RUU_HOLIDAY_SENSE3_5_Telstra_WWE_2.27.841.6_Radio_3.01.4720.09_3
file.
If I run it it wont do anything because its older than what is on the phone.
Found the instructions on how to turn it into a PH39IMG.zip file and loaded to a SD card. pretty much did the same thing at the hboot menu (older file)
Found out how to turn autoloader to unlock and did that, the sd card method now runs through (every file says missing or something though) till the end, but if you reboot its still ICS.
Yes, I have seen the super guide, but it seemed to be for AT&T phones, and being that i don't know much about them, I didnt want to go through it and be wrong.
I have been told it should be as simple as dl the ruu from HTC and running it, but HTC only have the ICS ruu for telstra phones, not the old GB version.
I have emailed both HTC and Telstra asking about it and no response.
Local telstra shop had conflicting info.. one guy said they could do it, but would cost $100, a different guy said no way to go back.
I'm hoping someone can show an extreme noob how to fix this, otherwise I'll have to look at buying a new phone as its pointless having this one for just half a day!

First of all, thank you for actually taking the time to read.
Second, anything in the superguide is applicable to your phone. Just replace any instances of ATT with Telstra, and you're good to go.
What you're going to have to do, if you want GB again, is to unlock your bootloader and fastboot flash a recovery image (ClockworkMod recovery will do), and then you can get a Telstra stock ROM zip from GB and flash that in recovery.
My other suggestion would have been to do the RUU method, but you've already tried that. I'm working under the presumption that your bootloader is locked, as the RUU method is guaranteed to fail if it is.
I'm curious, however, as to why ICS is using more battery on your device than GB did. That's not normal. Do me a favor, could you either screencap or read out what it says in your Settings -> Power -> Battery Use screen when your phone is nearly dead (14% battery or just an extended usage period). Something is very abnormal if you are getting worse battery life on ICS over GB.

Thanks very much for that,
Bootloader is unlocked (I think I said autoloader before, oops) Did it via the HTC unlock tool.
For a bit more info, I had an error 140 before I unlocked, and an error 155 afterwards. I did look up the error codes and the 155 seems to be a wrong version.
Will do a screen cap when I can for you, but from reading the Telstra forums and Whirlpool, it seems there are a lot of people with the same issue and more
(lower battery life, worse signal strength, tinny speaker on calls, call drops, random reboots on charging.. I only have the first 2 issues)
Most of them are looking for fixes for the issues, well.. complaining about them mostly. I think I'm one of the few that want to return to the old version.
As i said, I dont know a lot about them, and I know GB worked for me
EDIT: Get the Telstra stock rom.. is where I got the first one from ok, or is there somewhere else?

You CANNOT run an RUU with an unlocked bootloader, but that's another story for another day.
Do you have some form of recovery on it (CWM, WCX, TeamWin Touch)? If so, it's just a matter of finding a zip of the stock GB ROM. Else, you can use Jirv311 (I hope I spelled that right)'s method of compiling the stock RUU-based ROM posted on the development forum. I know a PH39IMG flash was made for ATT users, but I would advise against using that.
Per your question about ROM source, where did you find it exactly?
Worse comes to worst, just flash a custom GB ROM instead of a stock one if you can't find it. Holiraider is hella nice and gave me plenty of battery life.
By the by, if you choose a rooted ROM, I would heavily recommend to you to use SetCPU and underclock your phone. Search the HTC Dream G1's app board (under legacy devices), and you'll find a link. It's free to XDA members. On ICS, I have no problems ending the day at 50% battery, and that's with reasonably heavy use and my 3 email accounts checking mail at highest frequency.

Rom was from
http://forum.xda-developers.com/showthread.php?t=1338919&highlight=holiday+shipped+rom+collection
The link has a telstra GB rom there.
Have also read something about radios? From what I see that is what runs the phone signal side.. some threads have said that a RUU rollback wont change the radio version.. is that correct?

Well, doing some thread hopping I think I have done a proper rollback. Using mainly the superguide and associated links, I have unlocked the phone, think I have rooted it, flashed the Kernal and flashed the rom.
For some reason the only proper RUU/roms I could find wouldn't work, so have installed holiraider. I think I did it right because its running and usable on my phone now.
Unfortunately though, the issues I got when I upgraded to ICS are still there. Bad signal and battery life.
As a guide, I used to be able to have full 3g signal anywhere inside my house, now it fluctuates wildly, if I put my wife's phone alongside mine, hers is steady full signal, mine fluctuates between 0 and 3 bars.
Battery life: If left on screen locked, it seems to last overnight (8 hours)
As soon as you use it you can see the battery metre falling.
Sending a txt messages is using 2-3%, a post on facebook is about 5%
PRE ICS: Standby time about 32 hours, usable time: about 8-9hours
POST ICS: Standby time about 8-9 hours, usable time: anywhere from 4-6 hours.
I can only think with my limited knowledge that the signal fluctuating all the time may be what is chewing up the battery? (Bluetooth and wifi both off) And maybe the ICS update 'upgraded' something that the Holiraider rollback hasnt downgraded?

Same thing happened to me upgrading from GB to ICS. Turns out GoogleBackup was causing partial wakelocks, using both CPU and radio constantly. To check for this or anything else keeping your phone from sleeping, install and run BetterBatteryStats (free for xda users) from http://forum.xda-developers.com/showthread.php?t=1179809 and look at partial wakelocks.
Otherwise try checking a process monitor to look at what is active all the time, or perhaps use DroidWall to block internet access to apps that don't require it but may be using it.
Regarding the phone's signal, you'll have to go into the network status (in settings) to get numbers (IIRC correctly anything above -106dBm is a usable 3G signal). If this doesn't help, 2G will give you a better signal but it's not ideal. Nothing should be affecting your signal if you don't change the radio however.

Only major thing in the wake locks is alarm manager.
Signal goes from about 91db to 108db. Borrowed a friends phone and sits stable on about 85db.
I think the radio would have been updated when ics was installed. Can the radio be rolled back too?

Jaximus said:
Only major thing in the wake locks is alarm manager.
Signal goes from about 91db to 108db. Borrowed a friends phone and sits stable on about 85db.
I think the radio would have been updated when ics was installed. Can the radio be rolled back too?
Click to expand...
Click to collapse
Are you talking about the HTC Clock app, or did you install a third-party app by the name of Alarm Manager? If the latter's the case, you know what to do.
If the former is the case, you might just need to go to Settings -> Applications -> All -> Clock and clear its data.
Is your friend also on a Velocity? Different phones can have different readings based on random variables like interference and antenna placement.

Yeah, its just the HTC clock app. turned off the alarm earlier and its gone from the wake lock, but battery life hasnt changed. My last post was from the phone in question and it used 8% battery to type and post it.
Had a 15min phone call today too, used up 45% of my battery ( made sure to check before and after call.)
Nope, friends phone was a moterola Defy+
Thing is, I had this phone from a few days after they released here, so have been using it since Feb-ish on stock GB with no abnormal battery problems or signal problems.
Installed ICS and problems. Rollback to GB, still problems. I'm using the phone in the same area at home that had no issues before, so its gotta be something ICS, or at least Telstra's version of ICS, did to it.Since I still have the issue, its also gotta be something that didnt rollback with just flashing the rom..

m7 sprint - random reboots only w/non-sense roms

Alright, I have an issue that's been getting ridiclious the past few months. Ironically it all started when trump took office, but that's another subject....
On any rom besides a sense based rom, and i've tried alot, AICP, CM, Lineage, candy, etc etc. I'll have random reboots when getting text messages, or random reboots when trying to send a text message. I've tried all these roms wiped, with and without gapps, and i end up with the exact same result. Straight up random reboots.
The moment i wipe and restore the stock sense i imaged immeditately unlocking, no issues. I flash badboyz, no issues. I've been experimenting the past few months, and i can honestly say it only happens on non-sense roms. I thought it was because of gapps. So i ran CM11, which has been flawless since 2014, and without gapps, after a fresh flash and boot, the 1st text message i receive, instant hard reset.
The phone was s-on when i bought it, i took the latest OTA to grab carrier and OEM software and radios, then i did only the bootloader unlock, flashed TWRP, imaged my system. that was back in 2014 when the phone was first released. Since unlocking i've been running cm11 flawlessly for several months, at times a week or so of uptime, and i use my phone heavily.
Now it's to the point, when i flash a clean CM11, no gapps, just sitting on the table with the tethering on, either USB or wifi, it'll reboot. Sometimes itll get into a reboot loop and it'll take up to 10x of hard resets until it gets android fully loaded (mind you no gapps, no 3rd party, just the rom itself) before it's usable, that's if it doesn't run itself dead with the bootloops.
What's blowing my mind, if it's hardware, then why no issues on sense? Why only issues on non sense, and why now and not before? and the differences are all i can think of is software from: htc, sprint, google
When those 3 are removed, stability issues. but why now and all of a sudden?
anyone want me to supply something from adb? this has truly got me interested. I'm willing to copy and paste and upload some info. I'm really wondering what this issue is.
Thanks!

Bump.
Could a weak battery have something to do with it?
Does sending a text message require a moment of amp draw over the radio transmitter?
Sent from my One using Tapatalk

swerff said:
Bump.
Could a weak battery have something to do with it?
Does sending a text message require a moment of amp draw over the radio transmitter?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Here's what I would say:
Because non-Sense ROMs don't have the same drivers, HTC developers, etc, they tend to be less stable as a group. The developers work hard to mitigate that, but the random reboots are the hardest for them to figure out. If you go through non-Sense ROM threads for years, you'll see that common complaint.
Now, as for CM11 being solid and now it's not, my guess is that updated firmware, radios, etc caused it. CM11 is quite a few years old and was written under older radios.
When the m7 was my daily driver, I had good luck on these three ROMs. They had the occasional reboot, but it was about once a week at most and rebooted right back in.
Resurrection Remix
PAC ROM
NusenSeven (Sense based from the m9)

I would agree to that... Except...
Ive been running the same firmware/radios for the past 4 years.
I got the phone, did the Ota update, unlocked, never changed.
Since then cm11 (the same zip I've been using) has gotten ridiculously unstable since the beginning of the year. Just so odd when it's been flawless, sometimes a month of uptime, and in a month I'll suck in 400Gb through mobile data. And in all this "all of a sudden" unstableness, stock rom work ok.
Just coincidence removing HTC/Google/sprint software gives issues, when before it didn't matter.
As I was typing this, I got a sms reply, instant hard reboot.
I'm going to replace the battery and see if that makes a difference.
Sent from my One using Tapatalk

I've been also considering if the memory needs to be trimmed?
Sent from my One using Tapatalk

swerff said:
I would agree to that... Except...
Ive been running the same firmware/radios for the past 4 years.
I got the phone, did the Ota update, unlocked, never changed.
Since then cm11 (the same zip I've been using) has gotten ridiculously unstable since the beginning of the year. Just so odd when it's been flawless, sometimes a month of uptime, and in a month I'll suck in 400Gb through mobile data. And in all this "all of a sudden" unstableness, stock rom work ok.
Just coincidence removing HTC/Google/sprint software gives issues, when before it didn't matter.
As I was typing this, I got a sms reply, instant hard reboot.
I'm going to replace the battery and see if that makes a difference.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Misread and thought you updated radios recently. Not sure how replacing the battery would help, but you never know.
I had been running the three ROMs mentioned above with minimal issues when I used the m7 as my daily driver. I had run the latest RUU (see development section) to update to the latest radios, firmware, etc first. As I recall, all three were good. NusenSeven being stock based was most stable, but the others were good too.
swerff said:
I've been also considering if the memory needs to be trimmed?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Worth a shot, but your instability seems relatively reproducible. Personally never done it. So I'm not sure that would help, but like I said before, you never know.

Well, tonight I'm going to replace the battery.
If that diesnt help, going to relock and ruu just to make sure, unlock and flash the same zip I've been using for years.
If there's still issues, something is going down regarding big brother not enjoying his stuff on my phone.
That's my take and opinion.
Sent from my One using Tapatalk

Apparently it was the battery.
Ive Had zero issues since the swap.
Sent/received over a 100 messages total, tethering to ps4 and roku for Netflix, Bluetoothing pandora from my phone itself playing a 720 mkv,
Working the **** out of it, no reboots.
Odd why sense roms were not sensitive. Must be something in the kernel?
Sent from my One using Tapatalk

swerff said:
Apparently it was the battery.
Ive Had zero issues since the swap.
Sent/received over a 100 messages total, tethering to ps4 and roku for Netflix, Bluetoothing pandora from my phone itself playing a 720 mkv,
Working the **** out of it, no reboots.
Odd why sense roms were not sensitive. Must be something in the kernel?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Great! I'm glad it worked. It is odd, but what you say makes sense. Maybe the Sense ROM had something optimized in the kernel or ROM that the non-Sense ones don't. That's why I love this site; I learn something new everyday. Thanks for putting the results of your work in the thread for future members who may have the same problem.:highfive:

Well, update
It eventually got back into its old habits of randomly rebooting after ending phone calls or sending /receiving messages.
Soon after that it had issues if not coming out of airplane mode, which would require a hard restart, soft restarts were unsuccessful.
About week ago my son wanted to play on it, so i enabled airplane mode so he wouldn't accidentally call anyone.
Enabled airplane mode.
Handed phone to him.
Within 30 seconds I took it back, and in this time frame all he was doing was holding it/touching screen.
The phone now endlessly reboots to the initial HTC logo for maybe 5 seconds, goes black, and repeats. It will do this until the battery is dead.
Plugging in charger results in no battery charge state, screen or LED. After several moments of being plugged in with no signs of life, it'll light up to HTC screen, only 5 seconds later to go black and repeat, endlessly.
Holding power + volume down I can access the bootloader, which before it resets again I can pick recovery option.
It'll then reboot into HTC screen, saying entering recovery up at the top, but never doing so, and continue with boot loops.
The power button is not stuck, as holding only volume down will not encourage bootloader initialization.
Ideas?

swerff said:
Ideas?
Click to expand...
Click to collapse
It seems to have gone beyond the Sense working but non-Sense not working issues it started with. At this point, I'd probably try to RUU the thing back to stock and see if that fixes it. If not, I'd venture something hardware related. I wrote a guide on how to do this mainly because I kept forgetting all the steps. Hope it helps.
https://forum.xda-developers.com/sp...de-reset-phone-using-ruu-htcfastboot-t2876110

This is useless. It won't respond long enough to select fast boot, let alone stay without restarting.
Sent from my One using Tapatalk

swerff said:
This is useless. It won't respond long enough to select fast boot, let alone stay without restarting.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
That's too bad. I don't know what to tell you my friend. I saw you could access the bootloader and select recovery, but if it's not stable enough to stay in fastboot, then that's beyond my knowledge capability. At this point, if it were me, I'd buy a new device or take it to a repair shop.

I'm investigating surface mount memory readers and the like.
I'm hoping to solder up something to pull the memory in binary.
The phone wasn't encrypted. There's a handful of photos I'd love to recover. Not having an external sdcard is stupid.
Sent from my One using Tapatalk