Hey guys, wondering if anyone is able to create a recovery image for me to download of 8.1+update 1.
My surface rt wont boot past the surface logo. I can't find my usb drive that had my restore image but on top of that it was 8.0 anyway. I checked the ms website and they only host an 8.0 image as well.
At this point I am willing to try anything. I did attempt to download and boot to the 8.0 recovery image by inserting the usb drive and holding power and volume down until the logo came up, but so far doesn't seem to do anything. Am I completely hosed?
long version:
About a year ago, my surface started performing really poorly. Basically any swipe gestures would either not work or they would be extremely delayed. The animation would also be delayed. Other things would be really slow for instance, in IE tapping inside an address bar wouldn't load the keyboard for about a minute. PS 90% of my activity is on IE reading news or watching youtube.
Several months back I finally noticed that anytime I would start experience these issues, the disk usage in task manager would be pegged at 99% even though the read might literally show only 14 KB/s and the write might only be 1 MB/s. The biggest flag though was the response time was always in the thousands of ms.
I pretty much lived with the problem and often a restart would seem to make things happy for a while. And I usually leave task manager open so I can peek and see the utilization anything things feel sluggish.
Last night it was behaving worse than before. I managed to navigate through the charms and attempted to restart. But after waiting several minutes of it just saying restarting with that circular loading image decided to force the issue and I held down the power button until it shut off. It only said restarting, not installing updates or anything like that. I waited way longer than it would have reasonably taken and under normal circumstances, if it was installing updates, it is very obvious and the messages are clear. Plus the charms power option was simply restart, not update and restart.
Sadly when I tried to power back on, it just gets stuck at the "Surface" logo and doesn't do anything. I waited 10 minutes and forced the power off and tried again. It was late so I decided to go to bed, but left it running in hopes that it would eventually boot up. I woke up 4 hours later and it still showed the Surface text on a black screen. At that point I decided to shut it off.
I had already installed update 1 last week, BUT just in case it is some kind of failed windows update. Is there anyway to "reinstall" from this state?
Gonna be extremely bummed if my device is permanently bricked.
If memory serves, I'm pretty sure I deleted the recovery partition BUT I have a flash drive that has the backup, although it would be an 8.0 backup not 8.1.
Restore to 8 then update?
drearyworlds said:
Restore to 8 then update?
Click to expand...
Click to collapse
It doesn't boot from the 8.0 image. Not sure if its cause it's completely hosed or because it needs 8.1. I'm not getting the boot record problem as reported by people when 8.1 first came out.
Related
[Q] LS980-Cloudy G3 ROM- TWRP installed&accessible- [email protected] Android is Updating screen
Hello everyone,
I would like to say first of all to the community, thank you for SHARING KNOWLEDGE. That is the key to everyone's success.
Now down to the gritty. My, now, I guess, mess of a LS980. For starters, the phone was running I would say very well considering my abuse. Big overclocks, gaming hardcore, and pushing the storage space hard. I performed a very easy and simple rooting and recovery program installation. If I remember properly, it all started with an app/.apk that sparked my interest with making the phone mine, was Autorec? (red roundish logo?) In some time I decided to install my first aftermarket ROM. I chose and installed without any issues , Cloudys G3 ROM. I cannot however remember the version number. It is by no means recent. I think I installed it last September so maybe 1.0 or 1.2 (sorry so much bad luck with stuff recently) TWRP version 2.7.0.0 is my recovery, and its functional. Unfortunately I do NOT have my apps backed up. I have no space. (just managed to get about 7GB on this PC to try to back them up but there is not external back up option, UNLESS you are OTG cable equipped I am not )
Now, I think, (this has been the state of the phone for about 3 weeks now) this all started to go south when I saw there was a Dorimanx OTA app in the play store. I used his Kernel for as long as I have had the G3 ROM installed. With no problems. So I figure this would be easier for me than button mashing trying to get into recovery mode without popping my screen out the front. LOL Upon using the app, I was informed of an update, I read the included information, and generally knew the deal. I allowed the app to download what it needed and restart and install like a good little computer. And this is where it gets a little grey for me in terms of order and symptoms. I remember checking the status of the install and it read failed! I looked into the reason why, and I was just plain full of junk. I then uninstalled painfully a bunch of rarely if that, used apps and gained back about 2.2GB of space. I ran Dorimanxs app again and let it do its thing and reboot. And again it reported fail! I looked into it more and noticed there were newer Kernels than available on his inter-web. Alpha versions. I located them on my device and rebooted into TWRP mode and selected , then flashed his 10.4.1 Kernel. Everything went fine. Phone reboots, the LG logo is no longer animated, and takes a bit longer to actually boot into a GUI. But it was, luckily.
So now, the phone would be a usable thing for about 3 minutes tops, before a power off, to a reboot. Which at first I didnt notice to be a boot loop. My battery surprisingly went from full to about 6% in no more than 15-20 minutes. I noticed the battery was getting warm like I was running the CPUs maxed under a serious load for a good half hour. Around the range to make someone pull it out their pocket wondering wth? So after the next reboot, power cycle, I jumped back into TWRP mode, and dug around for what I thought was the culprit, Xposed. I was having the worst time with my phone after a major Xposed framework error. I picked up my phone one day and out of the blue the xda framework was telling me that there were so many errors with it and my apps that ran fine, not being installed or activated. Upon looking into it, it was removed from the phone. I belive the order was , stable, 2.5/ 2.6, then I tried the beta 2.7. and thats the version that eventually , either broke, or uninstalled, I think, during those frequent Crashes! I tried to install the previous versions, even going back to the versions that came out last year like 2.4 . But none would install. And the phone grew more unstable in terms of its cooperation with its software. My normal apps and games worked fine. The phone worked the same, the music player, but there were apps that only can work with xposed that I utilize constantly, that were kaput. So I left the phone off. For a while. I had/have no time and really no resources to research and rescue a sunken ship. I come back about two weeks to it and I take a look around in the phones storage and hunt for any kind of recovery and disabler. I found xposed's disabler and flashed it. Same luck as before. About 3 minutes on, then dump.
I dig some more and found a ccc71 back up folder with some hearty backups that I didn't know were still there (no wonder I was always loosing space) and found another xposed installer.zip . I figured well , it didn't make any sense trying to disable something that wasnt enabled in the first place. (thats why I walk away and come back . fresh mind to tackle what stumps me) So I flashed the installed zip and reboot. Same thing, but now it started to loop around one minute. I power down. Found the recovery.zip that was saved on the beater PC and adb pushed it over the the phone. Im not good enough to adb install it. So TWRP'd it and rebooted, and d'oh! Now we just have the motionless LG ball, but flashing blue and green LED. And after about 2 minutes it would black screen, but be on. Not hung or anything. I connected to the PC, it never finds the right stuff but I used adb to verify state. And it said device. It still could communicate and push. I had it dump its debug, surprise! as it flashes that crap as fast as it can up the screen. But Im a PC guy so it was a fun, pause/break over and over till I found something useful. I saw some things that I could recognize like, failed starts, and longer than normal (for a speedy experience) function or call times, but nothing that slapped me with a red flag.
And that ended that nights attempts to fix thanks to the slowest no ram having box I was using to try to learn how to have the debug save to a .txt file on my PC so I could take a good look at the results.
Upon reading forum after forum, I came to something that looked promising, telling me that, that particular boot issue was due to the wrong radio being installed. So I hunted, and hunted, and laaaaaged my arse off and finally found it. Great I thought. Powered up ten or twenty times, finally get into TWRP, tried to flash it. BBBBBAAAAAANNNNT! nope. Downloaded another copy of the file and tried it again. No luck. ( I must say not until roaming around in these forums tonight did anyone bother to mention that you dont flash that radio. You instead have to inject it via LGFlashTool, which I have used before, and its a pain in the butt.
But before I go any farther, make anymore mistakes. I need some help.. I would really LOVE to be able to flash this , slap that, curse its name then hug it and get her working, without having to ditch my 492 apps. If I would have to say goodbye to happy times, I would like to say good riddance to ugly and annoying G3 ROM. I like not flat UI. My phone was depressing me every time I had to do any navigating around inside it. So I would love to go back to KK Stock LG ROM if push came to shove. But if possible I would just like to "repair, and regain access into the phones GUI system". So I could backup my apps. And eventually labor back to OEM Kitkat.
I apologize for the length of the post. But I just dont see the point of ping ponging with partial exchanges of information. I hope I have made my situation clear, and someone knows of someway, I can get my GUI/phone working again. Thanks to all in advance.
"a non functional smartphone, is an oxymoron"
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
strangely enough
siggey said:
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
strange thing,
just about 5 minutes ago, the phone, which I left on sitting at the LG screen by accident yesterday after posting the above, changed screens and presented me with the Launcher selection screen.
I immediately noticed that it looked wrong. Like if the resolution was way off. Like an old low res screen, very dull, sort of blurred looking.
I figured what the heck and tapped the screen and it of course did not immediately respond. It took its sweet time , about 30 seconds to show a change. The menu disappeared and a error message along the lines of , android system UI has crashed.
That is not the message verbatim, it was gone to fast for me to take it all in. And now its sitting at the blank powered on and repeating blue/green LED.
I havent done as you suggested yet. I kept getting results from Norway and other places and didnt understand a thing. But I found a TWRP update from Dorimanx, there was a link to it. And now I have to find my version of the OS. And to be clear, were you suggesting doing a re install, basically a file overwrite? And if so, when doing something like that, do you wipe the Dalvik cache ? Or do you just "dirty flash" it?
Thank you ,
I think that your screen is overheated. Never let the phone in bootloop for long time, it can destroy the screen.
About the cache, is better to clean it, but if I remember well the rom installer alredy do this.
_____________________________________Read more write less and be smart
Hi all
I restarted my watch using settings menu. Then left the watch on charge and went away. Next day found watch to be dead with black screen. I hard reset it by holding button for 10 seconds. It seemed to start but then gets stuck on start up ( at different places and different booting time, every time) Have not able to complete boot it once.
Then I thinking I am very clever, went into the boot menu and deleted cache and data. It seemed to load a bit longer than last times and actually went on to connect with phine and started update but got stuck on 20 out of 27 apps.
So every time it gets stuck, it black screens and the only way to bring it out of this state is to hold down the button for 10 seconds. It does not black screen in FASTBOOT menu. I am not sure if there is any warranty left on this watch as it was bough second hand and till now had been working really well for about 3 weeks.
I have installed adb drivers but it doesn't show up on the PC. May be because i didn't do the developer options step before I am guessing. Anyway I have no idea what is happening to the watch and if it is even recoverable or not.
Any one seen this before? any ideas what I should do?
Thanks so much
One thing that gives me confidence that battery is not dead is that if I leave it in the fastboot menu screen then disconnt the carger it stays there.
I tried sideloading Android Wear 1.4 image. It fails at 57 or 58% , always
Just a note to anyone with similar problem. My watch sorted itself out after a few days. I think , if you leave your watch on charge and don't touch it for two days then it somehow help. I am not sure how it started working. My suspicion is that the watch either had water in it that dried out over two days or the charge had somehow gone so low that it needed a very long charge to stabalize. Anyway, it works now.
So, unluckily today i find myself here lookin' for help with my phone. I had already took a look on other brick threads, but i can't find an appropriate answer to my problem.
I'm (i was) running lineage-14.1-20170602-nightly, i had ne0zone75's TWRP 3.1.0.0-0, and that's how the brick came in a strange way; i was simply on XDA Labs app browsing the forum, when i received a call. I've answered, and when i shut off the call the phone shut off immediately after. I thought it was a reboot, but keeping pressed the power button didn't switched on the phone anymore. So i've tried to remove the battery and re insert it after some minutes, but the only thing i can get is the screen with the samsung logo that goes all black after 5 seconds. I already had other bricks due some errors of mine in the past, but this time it's really difficult.
1: I can't access recovery mode. Ow, how i wish i could.
2: I can access download mode, but after that i reach the ODIN MODE screen with the details of product binary, KNOX, ecc. the phone shuts off again.
3: If i keep the power button pressed, the phone doesn't starts. It only starts if i replug the battery in, but after some seconds it shuts off again.
4: How could a call as another mess up the whole phone?
5: I didn't installed nothing new from at least a week... yesterday an automatic update of the Play Store took place, but except that nothing has been changed. Nothing of nothing! No settings, no apps...
What could i do? Installing Kies with Samsung drivers could help me flashing a stock rom for example? Because at the moment, there isn't too much that i can do with the phone in this state... I hope this little jewel won't have to become a stone to be thrown away. Any help would be great, and really appreciated. Thanks in advance...
Things has got worse. Now my device doesn't starts at all; no vibrations, no signs of life, nothing. I've tried even to put it for 6 hours in my refrigerator, because i've read that the cold temperature could be helpful to fix some broken contacts on some component, but i'm losing hope 'bout it. I supposed that at this point is something hardware-based and not software, because it's just impossible that a call like an other one could be the cause of this hard brick... The only thing is that if connected to my PC, it is being showed as QHSUSB_LOAD. I'll try some methods that i've seen in other forums, like softwares that tries to fix this, but i think that i'll be forced to buy a new device. Neither an usb-jig could help me to force the download mode if the phone is dead in every aspect... the only thing that i still didn't understood, is if a debrick.img on my SD card (sadly i've read that a microSD class 10 with at least 16 GB is required, and i don't have one) could help somehow on a situation like this one of not. Still no one could advice me with some tip, guys
Edit - feel free to close this thread, I have another phone now
Hello,
This is what have happened:
I was browsing via Chrome, when phone froze. Well, no big deal. It went black, and I couldn't power it back on. I was on rehersal, so I left it on the table for an hour.
Came back to it, tried to power it on, and after 20sec or so of holding Power button, Google appeared. And it disapeared again.
And that is it.
I can access bootloader, and recovery.
From there I tried to flash fresh img, but my device is locked. Went the other way. I downloaded latest OTA and went to adb sideload, and it downloaded it all to phone, but same thing with booting. It stops.
Sometimes it even goes to those circle animations on booting, but than it freezes again, and turns off.
Any hope for my 2 years friend now
Thanks.
@Nuuq: by searching for 'brick' 'bootloop' you find for example this thread Hope, it helps.
Exact same thing happened to me this morning. I was playing Clash Royale, and it froze. Rebooted, and it just went to Google screen and nothing else. I let it sit for an hour, and it started to boot, but froze mid-boot-animation. I can get into bootloader and recovery, so I'm going to flash the Bootloop fix this afternoon and see if it fixes it.
Odd......
I thought this was a CPU bootloop issue, so I flashed the 4-core TWRP, wiped everything, and installed the stock OPR4.170623.006 system, vendor, and thne 4-core boot.img I found in the bootloop thread. I got a little farther, say 5 minutes instead of 5 seconds, but it was still crashing and bootlooping! I couldn't activate the phone, cuz it was rebooting while waiting for my 2-factor authentication text, and when I tried wiping it again, it was rebooting while in TWRP while re-flashing the system. The more I try to fix it, the worse it gets...
I may just give up on the phone, and contact Project Fi support to see if they'll give me a new one.
Same here guys...put inside the the fridge for about an hour and it started, just in time to save my photos on Google photo...but as soon as I start to use it, it freeze, turn off, no reboot. If I reboot, it freezes on circles Google animation...i can enter in bootloader and recovery too...any suggestion?
Same problem - merrily browsing -> crashed and now bootlooping - can get to the bootloader menu but can't get into recovery mode
Running Oreo 8.0
I flashed the 4-core TWRP, and it was crashing even in that. Last night, it sat for 3 hours on the activation page, and never froze, but anytime I try to use it, it freezes. It sometimes turns on, but most of the time it just crashes while booting.
I already use Google Photos, and my texts are synced through Fi hangouts, so I'm not worried about losing anything. I've wiped my phone and started over maybe a dozen times over the past year. Different ROMs, kernels, etc. I just want a working device.
I called Google, and they said nope. They want me to call LG, but my brother has had 2 bootlooping 5x, and LG didn't help with either of his. I doubt LG will help me here, cuz I bought it from the Google Store. I think I have 3 options:
1) pay to gave the CPU reflowed. If I went this route, I would want to upgrade to 3GB or 4GB of RAM at the same time. If I do this, I still have to deal with my battery only holding a 70% of it's charge, and not wanting to spend $50 on a 2 year old OEM batter.
2) Upgrade to a used Pixel. I'm sure with the Pixel 2 coming out, lots of people are going to be upgrading, and I'm sure there will be a bunch of used Pixels showing up. But, you're still buying a used phone that's been out for a year now...
3) Upgrade to the Android One Moto X4. The word "upgrade' is used loosely, as it's VERY similar to our 5Xs. Similar benchmarks, similar screens, similar primary cameras, almost the exact same dimensions, etc. It would be an upgrade with 3GB RAM, bigger storage, SD card slot, 2nd rear camera, better GPS, bigger battery, new (not used), and a few other minor tweaks. Con is that it's so new, there are no ROM/kernels for it yet
I think I just talked myself into a X4 while writing this. We'll see what the wife says.
it happen for me but me i can boot to bootloder but the phone become very slow i just escape from bootloop i turn it on and after 2 week he bootloop again now only fastboot no recovery and no system how i do
squelch41 said:
Same problem - merrily browsing -> crashed and now bootlooping - can get to the bootloader menu but can't get into recovery mode
Running Oreo 8.0
Click to expand...
Click to collapse
Hmm, putting it in the freezer gets it to boot but rapidly crashes again - looks like it is the hardware rather than software
I've been running the latest update on the d2q Note 10 welcome it's a n975u1, and I've been running ice box as my device owner as well as revenant and also use a box to keep my apps under control, very conscientiously I must add.
Ever since the last update was ready to be installed I was trying to put it off because I was hoping to get off on one of those new routing techniques that keep telling me that I can't update my system Os or I won't be able to get it done, so I kept putting it off, but with each day my system kept getting more and more strained and suddenly just begin going into a straight boot loop going from the startup screen with the Android name printed across the screen and then saying it was booted and has been reset and then immediately going straight back to that Opening screen with the Android logo on it and repeatedly doing it until I catch it at the right time to Power It Off. My question is is there any way that I am going to be able to get around having to do a factory reset on this device or does anybody have any other suggestions that may circumvent this tedious measure at this point? I've been routinely wiping system cache, make sure I got all my backups ready to go during the periods of time that it doesn't go into bootloop,(which seems to be usually once a day for a few hours it will operate just perfectly until just suddenly shuts off with no warning signs). I was also able to get onto the Verizon update app via ADB download mode and they ran a scan on it and determined that they could fix my device if I were to leave it plugged in and allow them to do it. Theresa in the process of the repair that they said needs to be done. They didn't say what this repair would consist of, so I have no idea what is the real issue here. I've been trying to get as many system debugging reports as I can pick up along the way from various apps that record crashes and such but not sure really how to process that information to be able to determine what exactly the issue is. I'm at my wit's end and just about to point to just go for it the factory reset as much as I hate to do that! I think that I have Extreme Complex post-traumatic factory reset disorder and would do just about anything to avoid having to go through this again! If anybody has any advice I would very much appreciate it and I hope I'm posting in the right for him because all these Note 10 forms get kind of confusing when you got all the various processors and countries and all the other factors that you have to where to figure out where you're supposed to be asking a question here! LOL sorry, thanks!
Power management apps and launchers can boot loop you fast... so I learned
I get good run times with no power management on my stock N10+, but it's heavily optimized and I am using a package disabler.
To fix it you'll need to edit the offending apk(s) out of the boot sequence. I haven't a clue how to do that. The power management app is the most likely suspect though.