Reinstall firmware on Verizon Ellipsis 7 tablet - Android Q&A, Help & Troubleshooting

I have a Verizon Ellipsis 7 tablet that is stuck in a boot loop. When I turn it on, I get the "Powered by Android" screen and then the screen goes blank but lit, and never gets to the next stage. I tried entering Factory Mode and cleared the eMMC, but after doing that I can't even get back into Factory Mode. (I spoke to a Verizon rep and he said clearing the eMMC likely cleared too much, and it now lacks the proper kernels to start up.)
I believe this whole fiasco may have started when I used the wrong charger after having not turned on the tablet for months. I stupidly ignored the warning, and the problems started soon after (although it worked perfectly normally for about a day first). I now have the correct charger and have fully charged the device overnight, but nothing's changed.
I think the only hope at this point is to reinstall the OS (the Verizon guy said "flash" it, but I'm not 100% sure what this involves). Can anyone help me do this, simply and safely? I'd like the original OS if possible, but otherwise I'm open to open-source alternatives. Thanks!

i just had this happen too -- and now i am stuck too;
however mine gets stuck at the verizon loading logo

Dude I'm right there with you. I'm almost at the point of installing Ubuntu touch lol I'm still not done with this fight though shoot I'll learn a whole new skill if need be damn things made me forfeit more than enough times.

hola busco firmware qmv7a

Related

[Q] HELP! Photon wont boot! (Stuck at red M)

So yesterday I was in a call with low battery when it shut off. Normally not a problem, just plug it into the wall for a while. Well when I tried to turn it on, it wouldn't even boot up. It was stuck at the red M logo. The LED showed amber colored as well. I left it plugged in and the light remained amber until 90% battery, where it turned green.
I tried to turn it on and its been stuck on the red M logo. Its been stuck for more than 12 hours now.
I CAN access fastboot, android recovery, etc. I already tried wiping the cache and even did a factory reset. Still wont work.
What can I possibly do? I luckily have a backup phone, but I've had my photon for less than a month, no warranty, and I'm a novice Android user. Any help would be greatly appreciated.
MooseV2 said:
So yesterday I was in a call with low battery when it shut off. Normally not a problem, just plug it into the wall for a while. Well when I tried to turn it on, it wouldn't even boot up. It was stuck at the red M logo. The LED showed amber colored as well. I left it plugged in and the light remained amber until 90% battery, where it turned green.
I tried to turn it on and its been stuck on the red M logo. Its been stuck for more than 12 hours now.
I CAN access fastboot, android recovery, etc. I already tried wiping the cache and even did a factory reset. Still wont work.
What can I possibly do? I luckily have a backup phone, but I've had my photon for less than a month, no warranty, and I'm a novice Android user. Any help would be greatly appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1393519
Click on the software and tools link and use rsd lite to reflash the stock os onto the phone. If that doesn't work I would take it to the sprint store.
I assume you tried pulling the battery?
I'm downloading SBF now. Hopefully it works, because I live in Canada and we don't have Sprint stores.
And YES, I tried pulling the battery. Multiple times. With every combination (eg, plug in, turn on, then insert battery; put in battery, turn on, then plug in, etc)
the sbf should work but may i ask how you managed to brick your photon? when i just got mine i did everything wrong and i never got even a soft brick so i'm interested what i didn't mess up haha
Quick question: I should be downloading the most recent? Will it make a difference?
And damn, did I actually brick it?? I'm pretty new to this thing, this is my first Android and I've had it for less than a month...
And nothing should have triggered it. I added another line in build (ro.media.setting.1080p or something) and I added another setting in /system/etc/mediaprofiles.xml. I was trying to add 1080p to the camera (unsuccessfully). I didn't remove anything, and even after a reboot it was fine.
It wasn't until the battery died, where it stopped booting up. Just my luck :/
You should probably choose one of the newer ones, just becasue of bug fixes, etc. If you happen to know what version you were running before then I'd choose that. I cant stress enough, make sure the one you download is for the Photon and NOT Electrify! And technically yeah that is a brick lol but its extremely hard to legit brick beyond repair a photon due to the fact that we have RSD Lite and SBF files to bring it back.
Strangely, I found a thread depicting the same problem that I had, although with the electrify. http://forum.xda-developers.com/showthread.php?t=14813
Anyways, the problem is fixed, by reflashing the SBF using RSD Lite, everything is back to normal! Well, almost, just have to restore my backup
Thanks so much for your help guys, I wouldn't have been able to fix it without you all!
can you fix a bricked phone??
My Photon has done the same thing! I rooted her and did the Bootstrap Recovery thing. Everything was kosher until I tried to load that stupid Beats Audio. Something happened between me flashing it and the reboot where it locks the phone. I tried to do the Android recovery screen, I wiped, I did about everything I could find. No bueno.
I followed this forum and clicked the software and tools link as instructed. I tried with RSD 5.6, and tried several iterations of SBF's located here and here. I was using SBF - 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_MR-3-CM.
It lets me go into boot mode, and when I try to flash the SBF it appears to go through, but it always fails at the end. Which, the posts state it will do, but my phone will not reboot afterwords. After trying everything I could for a couple days, I decided to just take it to a Sprint store. Mind you I've had this under 30 days, but longer than 14 so they stated it would have to be replaced. They tried to flash, but said they were getting stuck too.
I know that a replacement is pretty much the answer, but just wanted to check one more time to see if anyone had any other ideas, or could point me to other forums maybe? Appears I've done what few have been able to accomplish...brick this joker.

[Q] LG Mach Won't Get Past Boot Screen

I bought an LG Mach LS860 (4.0.4 Ice Cream Sandwich) about a week ago, and I just found out about rooting. (This is my first Android.) I had no luck last night, but I tried today and I got it rooted.
Anyway... here's the problem: I was altering some settings with an app (I believe it was called Pimp My ROM.) and everything was fine. When I restarted, the battery was lower by about 7%. I figured the changes I made were the reason for this, so I went back and reverted them. However, when I restarted the phone this time, it wouldn't get past the boot screen. It would flash the Boost logo, go dark, then flash it again with an animation and a short vibrate. That's all. So I tried restoring the factory settings. (Volume down + power button, then power button and power button.) The phone went through and reverted settings, then rebooted. But THIS time, I got messages popping up like "Unfortunately, System UI has stopped." I believe there was something along the lines of "Unfortunately, Home has stopped." as well. On a layer below that at the bottom of the screen, there was another type of error. I think it had to do with voicemail. After the phone sat there for a bit as I looked online for a solution, the phone restarted again. Now it just goes to the problem from the beginning with the boot screen. My computer makes a noise indicating the USB is connected, but all my phone does is charge off it.
Any help would be much appreciated.
It's not necessarily that I'm inexperienced. I've done all sorts of flashing and things on PSP. Obviously Android is much more complex. But I know that it's not bricked unless it won't turn on at all. Because that's not a brick.
There's also very little (if any) development for this specific model. No one cares about the LG Mach because there are much more well-known phones. But I digress.
Please help. I'm extremely desperate to get this working again.
EDIT: I recently thought of another question. Would the hard reset erase all evidence of the root access? Considering I just bought the phone, I might be able to send it back. But obviously if they know I accessed the root, the warranty is void.

[Q] Need Some Good Help with HISENSE Sero 7 Pro!

OK, guys, I'm talking about, most likely, a fairly unique problem I have with my Hisense Sero 7 Pro. So, considering the events of this have occurred over a year ago, pardon me if I have a bad memory. Get ready for story time!
Somehow, I could not get my Hisense Sero 7 Pro to boot up Cyanogenmod. I believe that is the software I loaded on it. For whatever reason, I could not boot it. I mean, fine whatever, right? I still have fastboot or bootloader and those combinations of buttons so that I reflash my software if needbe. It should technically be only a temp brick. But for whatever reason, it became really low on battery, perhaps from me unsuccessfully attempting to change it. I mean so low, that it reached that magical number where all of a sudden the tablet itself doesn't think it has a battery. And thus, it wouldn't even charge. I used a myriad of chargers and attempted all sorts of things to jump start it to a point where I could get it charging again, but it couldn't. Thus, I gave up on this tablet, and got a Nexus 7 2013.
Sometime later (ie, now), I fished this old tablet out of a shoe box when cleaning stuff out. I mean, not that old, but whatever. I thought, why not give it another go? I grabbed a random charger and plugged it in. I left it for 30 minutes to sit there, not doing anything. When I returned, to my surprise, it had reached the magical HISENSE boot screen it had been stuck at previously. This meant, that for some odd reason, my tablet had begun charging to some point, right? Alas, I was very excited. Yes, the tablet was still stuck at the HISENSE screen, flashing off and on again every minute or so, as if it's trying to boot a software that's essentially bricked, it's not there. But it has the electricity throbbing through its veins. And thus, that is enough for me to be excited. Just recently, I tried to boot into fastboot, I believe. And the device threw my a Low Battery symbol. The same kind it threw me when I tried to start it up way back when, and continued to attempt to, whilst it didn't charge, until it was deader than Abraham Lincoln.
But now I have the charger that will charge it, and that's good enough for me. Next Steps? Obviously, wait around, right? Perhaps it's below that 10% locked threshold needed for it to boot into fastboot or recovery? And if that's the case, I'll update you guys on that, but if that's the case, then great. I've got it at that screen.
Now what?
What do I do to flash Cyanogenmod, or Clockwork if I don't have it for whatever reason, and then Cyanogenmod and get this old thing working again? It's a project, true, but if I can get it functioning, this tablet would be awesome to have around the house, and, either way, it's a fun thing to work on.
Thanks for reading my story, and if you can help, great stuff!
i would suggest you install the latest lollipop.
first you will need to install a new recovery (neither the stock recover nor CWM will work with the newer roms)
http://forum.xda-developers.com/android/development/rom-sero-7-pro-uk-au-aosp-5-0-2r1-dopa5-t3015014
the above link has all the info, and files you need.

Alcatel onetouch fierce xl stuck at finishing boot

So i was setting up my phone today and it said a software update was available and i downloaded it it has been on this screen for over an hour even after a hard reset I have had phones do this before but they at least booted after a hard reset. I really need help here i cannot take another phone back to walmart within a day
T-Mobile
Well heres what i can see if we have enough friends contact tmobile that have this phone we may can get them to release a firmware thats not over the air. This is about where my hopes are because I have been a developer on android for 3 years now and getting any new response from this phone is well difficult.
Phone stuck
My phone is stuck in "optimizing apps" mode after a systems update. I've tried everything I was told to try even a hard reset but it came right back to that. I don't know what else to do to it without smashing it in a million pieces. Help My phone is stuck in "optimizing apps" mode after a systems update. I've tried everything I was told to try even a hard reset but it came right back to that. I don't know what else to do to it without smashing it in a million pieces. Help
I am having this same issue after the update I did last night.
Tracylynn said:
My phone is stuck in "optimizing apps" mode after a systems update. I've tried everything I was told to try even a hard reset but it came right back to that. I don't know what else to do to it without smashing it in a million pieces. Help My phone is stuck in "optimizing apps" mode after a systems update. I've tried everything I was told to try even a hard reset but it came right back to that. I don't know what else to do to it without smashing it in a million pieces. Help
Click to expand...
Click to collapse
have the same issue, optimizing apps gets done and it stuck on "android is starting..... starting apps" did a whole hard reset and nothing worked. updated the phone TODAY and have been stuck with screen since 8am

S8+ Bootloop, Odin Fail... Is it dead? Running out of possible fixes!

Hello all,
This past Saturday my Galaxy S8+ froze up and the display showed a bunch or discolored horizontal lines, then it shut down and went into a bootloop. I know this isn't an uncommon issue but it seems this usually happens from a botched upgrade/flash attempt. I've never attempted this and was just using my phone as normal. I have read through many bootloop threads and tried many of the troubleshooting steps, but I haven't had any success.
I'm starting to wonder if there's a hardware issue now. I'm hoping someone might have a new suggestion I could try, or point out any mistakes I made in my previous troubleshooting. I'm new here, so sorry if I left out any important details below, please let me know.
Thanks for helping!
Symptoms:
Phone is in a bootloop.
On occasion it comes out of the loop and displays some new phone setup menus (since I did a factory reset), but it crashes fairly quickly (and display gets distorted again) and re-enters the bootloop. It varies how far I can get into the new setup, before it crashes, but generally it's a matter of seconds.
On occasion, it comes out of the loop and displays a "System software not authorized by AT&T" message.
Attempts to fix:
Went into recovery*mode, wiped cache. Same results on reboot.
Went into recovery*mode, factory reset device. Same results on reboot.
Odin tool (3.13.1) and flashed lastest G955USQ8DTJ1_G955UOYN8DTJ1_VZW from sammobile. Device reached 32%, stayed for a while, then rebooted and back to bootloop.
Samsung Smart Switch, but then I discovered they neutered the app and it won't recover a device anymore.
Tried iMyFone Fixppo, but it failed to find latest FW for the device.
Phone details:
S8+ (SKU: SM-G955UZKV)
Bought it reburb 2 years ago.
It has never been rooted by me, so everything is stock.
Memory was close to full, but I still think I had a few GB left.
It was on VZW when bought, but I had it unlocked so I could use on AT&T.
In downloader mode, it says "Carrier: VZW", "Current Binary: Samsung Official", "FRP Lock: On", "Warranty Void: 0x0"
BlackbirdKM said:
Hello all,
This past Saturday my Galaxy S8+ froze up and the display showed a bunch or discolored horizontal lines, then it shut down and went into a bootloop. I know this isn't an uncommon issue but it seems this usually happens from a botched upgrade/flash attempt. I've never attempted this and was just using my phone as normal. I have read through many bootloop threads and tried many of the troubleshooting steps, but I haven't had any success.
I'm starting to wonder if there's a hardware issue now. I'm hoping someone might have a new suggestion I could try, or point out any mistakes I made in my previous troubleshooting. I'm new here, so sorry if I left out any important details below, please let me know.
Thanks for helping!
Symptoms:
Phone is in a bootloop.
On occasion it comes out of the loop and displays some new phone setup menus (since I did a factory reset), but it crashes fairly quickly (and display gets distorted again) and re-enters the bootloop. It varies how far I can get into the new setup, before it crashes, but generally it's a matter of seconds.
On occasion, it comes out of the loop and displays a "System software not authorized by AT&T" message.
Attempts to fix:
Went into recovery*mode, wiped cache. Same results on reboot.
Went into recovery*mode, factory reset device. Same results on reboot.
Odin tool (3.13.1) and flashed lastest G955USQ8DTJ1_G955UOYN8DTJ1_VZW from sammobile. Device reached 32%, stayed for a while, then rebooted and back to bootloop.
Samsung Smart Switch, but then I discovered they neutered the app and it won't recover a device anymore.
Tried iMyFone Fixppo, but it failed to find latest FW for the device.
Phone details:
S8+ (SKU: SM-G955UZKV)
Bought it reburb 2 years ago.
It has never been rooted by me, so everything is stock.
Memory was close to full, but I still think I had a few GB left.
It was on VZW when bought, but I had it unlocked so I could use on AT&T.
In downloader mode, it says "Carrier: VZW", "Current Binary: Samsung Official", "FRP Lock: On", "Warranty Void: 0x0"
Click to expand...
Click to collapse
Can you run graphics test from recovery mode? i guess something is overheating during boot. Can you put the device on a water/ice bag to lower the temp, and do factory reset ? as you said it displays some setup menus so its worth a shot
d3athAdd3r said:
Can you run graphics test from recovery mode? i guess something is overheating during boot. Can you put the device on a water/ice bag to lower the temp, and do factory reset ? as you said it displays some setup menus so its worth a shot
Click to expand...
Click to collapse
Seems to perform the graphics test fine. It cycles through all the graphics tests and then returns to the recovery menu.
I tossed the phone in the freezer for a few minutes and then tried a normal reboot. To my surprise it booted into the new phone setup menu, but this time it didn't crash right away. I was actually able to get through the complete setup and restore all my old apps (hooray google backups). In all, it probably worked for about 5 minutes before crashing again. I repeated the test, and verified that cooling it down does help.
So, great call! But what does that mean? Is there anyway to determine what is causing is this without a tearing it open?
BlackbirdKM said:
Seems to perform the graphics test fine. It cycles through all the graphics tests and then returns to the recovery menu.
I tossed the phone in the freezer for a few minutes and then tried a normal reboot. To my surprise it booted into the new phone setup menu, but this time it didn't crash right away. I was actually able to get through the complete setup and restore all my old apps (hooray google backups). In all, it probably worked for about 5 minutes before crashing again. I repeated the test, and verified that cooling it down does help.
So, great call! But what does that mean? Is there anyway to determine what is causing is this without a tearing it open?
Click to expand...
Click to collapse
Nice i guess it should be the processor thats heating.
You can find the location of the heatsink/thermal paste/process here (around 3:30 min mark)
https://www.youtube.com/watch?v=GRmY-4HKVIk&t=362s&ab_channel=JerryRigEverything
The processor seems to be located below Bixby button.
You can also try gently pressing the spot where processor is located to seat it back, but am not sure how long it may stay. if the thermal paste is dry and not in contact with processor, you have to open the device.
Or you can take it to a local repair shop for some assistance.

Categories

Resources