Help Verizon Ellipsis 7 (quanta qmv7a) brick - Android Q&A, Help & Troubleshooting

Of anybody could help me that would be absolutely fantastic. I was half asleep in a thread on trying to get a custom recovery for my Verizon Ellipsis 7 (quanta qmv7a) and I found a recovery.img and it was noted that it was a test. I'm just curious of anyone knows how to fix my brick because the recovery won't load and I'm now stuck in a boot loop, the "welcome" screen comes up and goes away and comes up again repeatedly. Is there a way I can adb flash this tablets stock recovery? I still have the original recovery.img I just need to figure out how to flash it when its boot looped due to a wrong recovery.img flash. Help is greatest appriciated! Thank you!

bump
-The complete lack of responses could mean that we're screwed... (or we've asked a dumb question).Today, I too was a little too eager with the Enter button without triple-checking if the version of the recovery would be compatible with my current ROM -- it obviously wasn't -- Ellipsis_boot_patched_140902-025705.img over the top of 4.4.2 -- should have done more homework
Google's bots have hit this thread -- I hope we can help others who find this thread in our predicament and give solutions -- not just be a dead-end as it is now.
It's only been 4 hours since I've been working on it... it had an unlocked bootloader so there is hope.
I can tell what _doesn't_ work straight away:
1. Pulling the battery cable -- the back cover comes off easy -- insert a credit card starting at the SIM/SD slots and work your way around the cover and then gently pull the battery harness from the battery terminal assembly -- At least I don't have to see WELCOME taunting me by flashing every few minutes.
2. Combinations of button pressing -- I tried all the dead-Andi tricks...
3. Adb and RSD-lite aren't being acknowledged.
For just a few seconds before re-cycling -- Windows DOES recognize the phone (via USB) -- enough time to (indirectly) put a batch file in the bootloader?
-- or the answer could come from a combination of all the above.
After months of tweaking, I had just gotten the 16G SD card to be stable and (fairly) transparent as the main-APP drive -- Thanks mostly in part to Vicky's recent overhauling of her app: Apps2D -- I don't want to abandon all those hours without giving it one last concerted effort.
I am also willing to give playing with the physical ROM a try (-- I pray it's not embedded in the Soc). I remembered all the fun I had with JTAGs all those years ago when I was messing with DSS systems.
The tablet was a grateful gift to me but would not be one I would have ever purchased... The Ellipsis 7 was one of the first "cheap" tablets on the market... it shows. I would never use it professionally -- but wouldn't hesitate to use it as a backup or taken out camping...
I'm giving this a 30% chance of success.... well, i'm in the market for a new tablet... maybe one of those new Win8/Marshmallow dual-booters made-in-China?

You say you have the original recovery.img could you send me that please?
ThatGuyWhoLovesRoot said:
Of anybody could help me that would be absolutely fantastic. I was half asleep in a thread on trying to get a custom recovery for my Verizon Ellipsis 7 (quanta qmv7a) and I found a recovery.img and it was noted that it was a test. I'm just curious of anyone knows how to fix my brick because the recovery won't load and I'm now stuck in a boot loop, the "welcome" screen comes up and goes away and comes up again repeatedly. Is there a way I can adb flash this tablets stock recovery? I still have the original recovery.img I just need to figure out how to flash it when its boot looped due to a wrong recovery.img flash. Help is greatest appriciated! Thank you!
Click to expand...
Click to collapse
I am still trying to work on one, could you send me the original recovery.img if you still have it? Thanks

Bondaddict said:
I am still trying to work on one, could you send me the original recovery.img if you still have it? Thanks
Click to expand...
Click to collapse
i actually threw it away, but i have another that isnt bricked ill pull the recovery from that one if you would like. it wont be for a couple weeks as my daughter was just born and i havent had time to do anything on my pc. just let me know ill get back when i can

That would be awesome
ThatGuyWhoLovesRoot said:
i actually threw it away, but i have another that isnt bricked ill pull the recovery from that one if you would like. it wont be for a couple weeks as my daughter was just born and i havent had time to do anything on my pc. just let me know ill get back when i can
Click to expand...
Click to collapse
Ya if you could do that that would be amazing! Could you also include how you suspended the pre boot?

Bondaddict said:
Ya if you could do that that would be amazing! Could you also include how you suspended the pre boot?
Click to expand...
Click to collapse
Is there a chance that you have the entire ROM? I tried to root and ended up bricking the device

Related

[Q] Used Tenfar's CWM to Format & Partition, Touch Screen Off

Hi, I'm trying to help a fellow Atrix user after he formatted and partitioned the internal flash memory using Tenfar's CMW Recovery.
He has lost touch on the bottom part of his screen; about a 1/2" of screen space doesn't work.
Tenfar posted that he had done this too, and had resolved this by reformatting with the Stock Recovery. Another user asked in that same thread how he accomplished that, but no answer has been given yet.
This user cannot get the Recovery Menu to show up because of the lower touch screen not working.
Can the steps be run blindly without the Recovery Menu showing up?
Or, can someone help me on how to have him format the internal memory via ADB?
I've had him try the following ADB commands from both the /!\ Recovery Screen and after enabling Early USB Enumeration without luck.
Code:
adb shell
$ su
# format DATA:
Comes back with format: not found.
Can anyone help? I've seen a few others with this issue but have yet to see a full solution posted for those that aren't ADB experts.
I have this problem too! Tenfar was kind enough to try helping me but apparently I'm a retard and unfortunately can't follow his instructions. I've been spending an entire week reading hours each day and I'm embarrassed that I still can't fix it, despite him sending me almost a dozen PM's trying to do so. Very grateful but sad that I'm so dumb.
He's told me to do this:
$adb shell
$su
#busybox umount /sdcard (hit enter key)
#newfs_msdos -F 32 -S 512 -L MB860 -c 64 -u 16 /dev/block/mmcblk0p18 (hit enter key)
I'm not sure where to do this. I now think I do this while the device is in Early USB Numeration but I haven't tried it yet. The wife was getting really pissed because I spent the entire weekend trying to fix this and have been investing too much time on the computer. She's... having mad PMS so I'm leaving it for a few days lol
I tried earlier when the phone was booted up but after some research, believe it may need to be done in Early USB Numeration mode but there's only about a minute before it automatically reboots. I haven't tried this and hope that my assumption is correct. I know about 3 other people who are currently experiencing this challenge and I hope that it corrects it.
The wife is working a double shift today so I'll try after work. Can't blame her for getting upset with me. Soft bricked a few other phones but fixed them with relative ease. This has been by far the toughest. It was my birthday last week and I spent most of my day on the computer trying to fix my Atrix lol
After this, no more formatting internal SD partitions!!! Paypal is giving me grief but I plan on giving Tenfar a modest donation. He's been very supportive of my dumb ass lol
In this forum there is a very good guide on how to use adb. Can't remember where exactly it's at I just did a general search for How to use adb it may help you.
Edit I think this is the link androidsamurai.com/forum/viewforum.php?f=12
coldfusionb said:
In this forum there is a very good guide on how to use adb. Can't remember where exactly it's at I just did a general search for How to use adb it may help you.
Edit I think this is the link androidsamurai.com/forum/viewforum.php?f=12
Click to expand...
Click to collapse
Thank you!
I managed to install Ubuntu and I really like that.. tried from there too and it wasn't working. So I think it's definitely a problem with my dumb ass. If and when I get it working (I'm determined!...... and sort of stuck lol) then I'll post a guide.
Fuuuuuuuuuuck!!! Still not working!!
Yeah.. i ended up wiping with stock recovery and still a no go. Still no lower half of the screen or buttons. Sucks big time
Once ADB can be run in the recovery menu I think it should be fine.
Tenfar said he's fixed this problem but I'm no sure where he's run these commands. I feel bad after sending him a ton of PMs so I'm just waiting until he updates his Recovery app.
You could try restoring your sbf in rsd
Sent from my MB860 using XDA App
sgtmedeiros said:
You could try restoring your sbf in rsd
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
That's been mentioned and tried multiple times.
I have a simple script written with the command lines from Tenfar, but I am getting his input via PM to make sure it's correct and when exactly to run it. Hopefully he'll be able to direct me on how to get it done. Unfortunately, even if he says it looks right it's going to be completely untested. :-/
Sent via rooted Moto Atrix using Tapatalk
das8nt said:
I have a simple script written with the command lines from Tenfar, but I am getting his input via PM to make sure it's correct and when exactly to run it. Hopefully he'll be able to direct me on how to get it done. Unfortunately, even if he says it looks right it's going to be completely untested. :-/
Sent via rooted Moto Atrix using Tapatalk
Click to expand...
Click to collapse
There's still a glimmer of hope, buddy. Once we get ADB access in Recovery I think all should be well.. unless partitioning this block somehow corrupts and kills the digitizer or something.
I actually couldn't wait any longer. Ported to Bell and got a new Atrix so if things go bad I'll have an easier time swapping. When I fix this AT&T one I'll sell it to pay off my cancellation fee with Rogers. Or, if I end up sending it to Motorola I can go back with my buyer's remorse period and go back to Rogers.
Hope you've got a backup phone or something to use in the meanwhile, man. This issue drove me INSANE!!
Hope is good, but this isn't necessarily for me. That's why I can't test it; this didn't happen to my phone. I have just been trying to help those who this did happen to. I'm also sure it will continue to happen if the CWM port for our phones isn't preset to format correctly.
Glad you were able to get a working phone again, but too bad a phone had to go back under these conditions.
Well, I'll keep trying to figure it out; waiting on another reply from Tenfar. Our schedules don't mesh too well, so if there's anyone else that might have experience in formating via ADB any help would be appreciated. Thanks!
Sent via rooted Moto Atrix using Tapatalk
I have the same problem, I just wanna know if anyone found a solution to fix that?
Also, I live in Belgium (Europe), I bought the atrix in usa a month ago during my honey moon. Motorola Europe doesn't support yet the atrix, I don't know what to do!
The phone is not usable anymore, like someone said: "clicking on the soft button area registers as a click on the bottom of the screen". So, the back button don't work anymore (you have to reboot when your stuck in a menu!)
hi guys i'm currently with a reflashed stock 1.83 rom, i can use android recovery (there the bottom screen portion works) and i can run wipe data/cache.
but no matter how many times i tried when the phone finally boots up it starts with motoblur setup and i cannot pass it, all the buttons work like the bottom of the visible screen and i cannot raise up the keyboard to turn the setup off...
i read in the sbf thread that would be possible to flash or not some particular areas, so if the problems is the wrong partitioning of the /dev/block/mmcblk0p18
maybe some of them could create a sbf replacement toreflash only that partition
other side i was talking with bongd and he says he had problem with the psd.bin file that is in the mmcblk0p03...
so what is the current status of this? adb seems not to work even in early enumeration usb mode...
what if we execute the script using the update.zip function?
i can access my sdcard from windows in storage mode
if we put the script in one signed update.zip into the sd the phone should be able to execute itself?
KeRmiT80 said:
hi guys i'm currently with a reflashed stock 1.83 rom, i can use android recovery (there the bottom screen portion works) and i can run wipe data/cache.
but no matter how many times i tried when the phone finally boots up it starts with motoblur setup and i cannot pass it, all the buttons work like the bottom of the visible screen and i cannot raise up the keyboard to turn the setup off...
i read in the sbf thread that would be possible to flash or not some particular areas, so if the problems is the wrong partitioning of the /dev/block/mmcblk0p18
maybe some of them could create a sbf replacement toreflash only that partition
other side i was talking with bongd and he says he had problem with the psd.bin file that is in the mmcblk0p03...
so what is the current status of this? adb seems not to work even in early enumeration usb mode...
Click to expand...
Click to collapse
Tenfar told me it was mmcblk0p18 but it's actually mmcblk0p03 which needs to be corrected.
There's no ADB in recovery right now. Tenfar's apparently got it working but hasn't released it yet.
I also guarantee you can bypass the Motoblur setup as well. Hit these keys:
?123
ALT
ABC
e
?123
ALT
ABC
e
b
l
u
r
o
f
f
I'm positive because I've literally flashed every SBF and I've spent a lot of time troubleshooting this issue.
really i cannot open the keyboard while i'm in the blursetup screen, i keep pressing the menu button but it highlights only the emergency call and after many seconds it chance to emergency call screen...
At this time, your phone is 'bricked' since we can't get ADB access.
Sent from my MB860 using XDA Premium App
we don't have adb access but i tried and we can use the update function in the stock recovery...i tried to put a update.zip of my old milestone and the process worked till the sign verification that failed.
in the milestone that update.zip is used to run the updaterscript that launches the openrecovery by skrilax_cz, that works like the recovery of tenfar
i guess that if we have a correct update.zip for atrix and we put in it the script we need, it should be run.
unfortunately i don't have the knowledge to build the correct script and don't have access to a signed update.zip for atrix.
if we only could gain some interest of the devs i think our problem could be solved in short time...
edit: i sent 2 pm to tenfar but did not reply, maybe someone has more luck...

[SOLVED] LG Optimus V - Blank Screen

I have yet to find an answer to this while searching for the past day, so I'm going to ask about it here.
My LG Optimus V's (just got it a few days ago as a birthday present) screen seems to be permanently blank... In case someone asks... yes, it is activated.
What Happened:
I rooted the phone using Gingerbreak 1.2, installed rom manager/clockwork recovery mod, then attempted to backup my phone in case something went wrong. However, when I started the backup, I noticed that the screen was completely blank. I was kinda freaking out, so I just took a shower while it did it's thing. When I came back, it was done creating the backup and it showed up in Rom Manager. After toying with some of the things I can do with it rooted (I only rooted it to see how much of a difference it would make without changing the kernel), I decided to recover that backup. When my phone restarted to recover the backup, the screen was blank once again. After waiting for over an hour, I concluded that it must have finished (since my HTC Hero would finish restoring and never reboot until I tell it to) and took out the battery. Afterwards, it would show the LG splash screen... then the blank screen.
What I Did:
I was thinking about the android screencast java application a few hours after my problem first developed. I plugged my phone into my computer, got adb working, and android screencast showed me that my phone was actually getting stuck at the clockwork recovery mod screen. I tried many things... I installed a CM7 rom, flashed 3 different recoveries, flashed an overclocked stock rom, etc. Eventually, I flashed the stock rom (no changes whatsoever) and stock recovery. Now I can hear my phone, but cannot see it. However, I should note that while using CM7 the same thing happened. The only difference being that I could use android screencast to see the screen (the phone was actually working) with CM7. Now with the stock rom, adb is disabled and I cannot see the screen or do... anything.
What I Think I Should Do:
I'm thinking about calling Virgin Mobile and telling them that my screen is defected. If they see the issue they'll probably think that it's a hardware issue (for all I know, it could be) and they'll probably give me a replacement. However, if anyone as had the same problem and fixed it, I would love to know.
I would love you hear your opinion on this and, if possible, a fix. Thanks in advance!
(JIC, if I posed in the wrong section, I'm sorry...)
you poor souls reporting the symptoms of getting the newer screen hardware from the optimus s in your v's don't number in the double digits yet, but it's getting closer.
I posted a fix on AndroidCentral, see it:
here
good luck! the fix has worked for everyone I pointed to it so far.
btw, the screencast idea is excellent!
crud. stock recovery, you may be SOL.
you'll probably have to boot into custom recovery to use screencast or adb now.
use the unplug phone -> pull&replace battery -> hold home+volume down -> keep holding, press and hold power until lg screen goes blank to enter recovery. maybe adb will work in stock recovery, I dunno.
Thank you very much for the reply!
Yeah, you're right, I'm probably SOL... I still have one option though! Theoretically, I should be able to turn on ADB without being able to see my screen. I know how to access the settings without seeing it, but navigating myself to the "Applications", "Development", "USB Debugging" may be a little hard. I will attempt to do so. I will report my progress in a bit.
However, if you (or somebody else) could provide screenshots of a step-by-step process to turn on USB Debugging in the stock rom (since it's kinda hard to do remember where everything is and screenshots of different phones is kinda different) then I would appreciate it VERY much!
I shall update this in an hour or so.
UPDATE (9/2/11 - 9 PM):
I'm going to take a break for now. Good thing I give everyone my Google Voice number, I doubt anyone will notice a change. I'm going to flash a stock rom onto my HTC Hero so I can figure out where things are on the LG Optimus V (Same screen size) in an hour or so. I'll update my progress in like 2 hours.
UPDATE (9/3/11 - 8:10 AM):
I have been unable to turn on USB Debugging and it seems to be because I don't know where the confirmation after turning it on is located. However, I should note that when I boot into (I think) recovery, "adb devices" states that the device is attached but offline. If there is a way to make it "online" from stock recovery then I would love to know. For now, I will try everything I can.
UPDATE (9/3/11 - 8:22 AM):
Ok. I plugged my phone into the back of my computer and now when I do "adb devices" it detects the device in recovery mode. However, when I try "adb shell" it says "- exec '/system/bin/sh' failed: No such file or directory <2> -". I'll try some more stuff, but does anyone have any idea of what I can do? Android Screencast doesn't work either, so that's not an option.
UPDATE (9/3/11 - 9:42 AM):
Crap... now it's indefinatly booting into recovery... I had something like this happen before, I'll report my status in an hour or so...
UPDATE (9/3/11 - 12:36 PM):
My friend finally got my phone booting out of recovery again! Now all I have to do is get "USB Debugging" on and it SHOULD work!
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
glad you got back into recovery again, not too sure how to help at this stage though, since I can't find a way to get into the bootloader with a power-on key combo. just emergency mode (useless to the V since the firmware from LG is missing a file) and safe mode. boo.
there is a youtube video for enabling usb debugging on the v, maybe it'll help you find the right spots to press.
http://www.youtube.com/watch?v=nHal0hPNS6s
edit: you can also try to reboot into the bootloader with adb, even though it's missing the shell... it's worth a try, and if it works you can flash xionia recovery with fastboot and things would be a lot easier from that point.
Code:
adb reboot bootloader
if that works but you need more help, a battery pull is the only way to power off with the bootloader except "fastboot reboot" will try to boot your rom.
Awesome, thanks for the replies! I'm going to try your suggestions now. I'll let you know how things work out in a few hours. I would have replied earlier, but to my satisfaction there was a surprise party planned for me, lol. I will defiantly try these out now.
Once again, thank you very much. I honestly did not expect a reply for something that happens to such few people.
bigsupersquid said:
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
Click to expand...
Click to collapse
I'm honestly not sure what my friend did, lol. She was just messing with it while it was, apparently, in recovery and it ended up rebooting and loading the rom. I, honestly, don't want to risk getting stuck in recovery anymore since taking out the battery for an hour didn't do anything... If I'm unable to get adb on using what I know from that video then I'll try booting into the bootloader. Like I said before, I'll report my status in a few hours. I really appreciate your help up to now!
EXTREMELY HAPPY UPDATE!!! (9/4/11 - 1:22 AM)
I was able to turn on ADB! I used what I learned from that video and how turning on ADB works on my HTC Hero to get it working and it's FINALLY ON! Now I can attempt to flash the recovery, kernel, and everything else in order to get it working! Thank you VERY much! I will let you know how everything turn out
Another Wonderful Update! (9/4/11 - 2:03 AM)
I have flashed the recovery.img (the Xionia CWMA one) and can see my screen in recovery! I haven't seen anything on my screen besides the LG splash screen so I'm overwhelmed with joy! I'm flashing a new ROM and the other stuff now!
Final Update! (9/4/11 - 2:09 AM)
2:05 AM - I see the rom's boot screen!
2:06 AM - I see the CM7 Mod boot screen!
2:08 AM - I see the UI on my screen and everything seems to be working! Thank you VERY much!
Quick question though... If I want to install a new ROM, do I need to flash the xionia anykernel one directly afterwards?
ah, excellent! glad it's working now.
you're the most persistent (and maybe technically apt) person I've helped with this so far.
I still think that using screencast was the best new idea I've seen yet.
yes, you'll need to flash the xionia kernel after flashing any rom or rom update.
roms come with their own kernel in the boot.img, and none of them currently out for the v have the video drivers from the newer sprint kernels.
right now, xionia kernel is the only thing that works.
and, you'll need to flash the key swap after changing roms, as well, but at least forgetting to do that won't take out your display.
now that you've got xionia recovery on your phone, it should be a lot easier next time.
Thank you for both the help and the compliment!
I don't like giving up when it's something I know I can do. I figured that if I was able to mount my SD card without being able to see the screen, I should be able to turn on USB Debugging as well. About the Android Screencast... I didn't actually think about it until it until I plugged in my phone while the screen was blank, ran "adb devices", and saw that my device was detected within recovery. I figured that I might as well give it a shot... and it worked.
Alright, that's what I figured. Hopefully someone realizes what's happening with refurbished Optimus V smartphones and ports the newer sprint kernels to the Optimus V. I feel like I got ripped-off though... I bought my phone "new" and got a refurbished one. I can't really do anything though, we're not technically supposed to be rooting our Virgin Mobile phones anyways, lol. I'll be sure to do that everytime now though. For now, I think I'm good with the Bumblebee rom.
Once again, thank you VERY much for your help! I know I would not have been able to fix my phone without your help.
EDIT:
Oh yeah, btw, if the Optimus V ever gets stuck in stock recovery, press the "back" button then "home" button to boot into the rom. Not sure why it works (I was never able to see the screen), but it worked.
There is a key combo!
First time caller long time listener... I bricked my own Optmus V with a bogus ROM. To boot into recovery without adb press (Home)+(Volume Down)+(Power) Now rocking CM7!

Tried restoring rom, now phone won't start. Help Please!

Hey all, this is my first android and I'm not the smartest sometimes. I tried restoring back to factory rom, and watched a bad how to vid. Basically i cleared data, system, cache and now realize i shouldn't have.
I'm not able to connect to the phone through usb. I have the drivers, but I can't see the phone.I can boot into cwm, and that is it. When i start it, it basically pulls up the LG screen, then a black screen.
I have a backup on cwm but get the md5 error.
Is it possible to put the sd card in my computer and download what i need straight to the card? Im also not sure what i need to download, if that does work.
Please let me know if there is any other info I can provide. Like i said im not the smartest sometimes, so dont be afraid to respond like im slow.
Cat Rancher said:
Hey all, this is my first android and I'm not the smartest sometimes. I tried restoring back to factory rom, and watched a bad how to vid. Basically i cleared data, system, cache and now realize i shouldn't have.
I'm not able to connect to the phone through usb. I have the drivers, but I can't see the phone.I can boot into cwm, and that is it. When i start it, it basically pulls up the LG screen, then a black screen.
I have a backup on cwm but get the md5 error.
Is it possible to put the sd card in my computer and download what i need straight to the card? Im also not sure what i need to download, if that does work.
Please let me know if there is any other info I can provide. Like i said im not the smartest sometimes, so dont be afraid to respond like im slow.
Click to expand...
Click to collapse
Can you install the Rom "The base .5". I assume so if you can get to cwm. I had this problem when flashing this Rom The first time. It did the same thing with the LG logo then go black. If that happens just reboot to cwm(May take awhile) and reflash "the base" again. That should allow it to boot the phone fully so you can at least use it till you can get all the way back to stock. I hope this helps. I have to crash now tho. I'll check back in the morning to see how it's going.
Sent from my UNLOCKED LG-E970 using xda premium
Are you trying to get back to factory settings or just get your phone running with the stock rom?
You should be able to just put the ROM on your sd card via computer if you have an SD card sleeve.
If you wiped your phone, it's my understanding that you're not supposed to when flashing the provided rom in development.
There's a posting in development, I believe, about restoring your phone to stock if you messed it up. LGNST or something.
Cat Rancher said:
Hey all, this is my first android and I'm not the smartest sometimes. I tried restoring back to factory rom, and watched a bad how to vid. Basically i cleared data, system, cache and now realize i shouldn't have.
I'm not able to connect to the phone through usb. I have the drivers, but I can't see the phone.I can boot into cwm, and that is it. When i start it, it basically pulls up the LG screen, then a black screen.
I have a backup on cwm but get the md5 error.
Is it possible to put the sd card in my computer and download what i need straight to the card? Im also not sure what i need to download, if that does work.
Please let me know if there is any other info I can provide. Like i said im not the smartest sometimes, so dont be afraid to respond like im slow.
Click to expand...
Click to collapse
The recovery won't generate a md5 sum (known bug). You have to generate it yourself. Connect your phone to adb and go to #4 in the FAQ here.http://forum.xda-developers.com/showthread.php?t=2006946
Note that there is no way to tell of the backup is corrupt since you are generating a valid code regardless of integrity.
Sent from my LG-E970 using xda premium
Murasakiii said:
Are you trying to get back to factory settings or just get your phone running with the stock rom?
You should be able to just put the ROM on your sd card via computer if you have an SD card sleeve.
If you wiped your phone, it's my understanding that you're not supposed to when flashing the provided rom in development.
There's a posting in development, I believe, about restoring your phone to stock if you messed it up. LGNST or something.
Click to expand...
Click to collapse
I tried re-installing .4 base which is what I had originally used. It let me choose the apps to instal, and made it to the "X" screen, but appeared to be stuck in a boot loop. I am going to try and download and install .5 via the sd card and see if that works. I'm not sure if LGNPST will work since I can't see the phone via usb. I will download it and give it a try though.
I also saw the guide in the general Optimus G forums for unbricking it.
http://forum.xda-developers.com/showthread.php?t=2010624
Since i cant really connect via usb, ill probably have to use a different method. Im hoping the usb issue is due to the computer im using and the original computer i used to root and unlock will work.
Cat Rancher said:
I tried re-installing .4 base which is what I had originally used. It let me choose the apps to instal, and made it to the "X" screen, but appeared to be stuck in a boot loop. I am going to try and download and install .5 via the sd card and see if that works. I'm not sure if LGNPST will work since I can't see the phone via usb. I will download it and give it a try though.
I also saw the guide in the general Optimus G forums for unbricking it.
http://forum.xda-developers.com/showthread.php?t=2010624
Since i cant really connect via usb, ill probably have to use a different method. Im hoping the usb issue is due to the computer im using and the original computer i used to root and unlock will work.
Click to expand...
Click to collapse
The method in that link is for phones that don't have official firmware to use with lgnspt. If you san get into download mode (power off phone ,connect usb,hold volume down and up plus power ) you should be able to lgnpst back to stock.
adfurgerson said:
The method in that link is for phones that don't have official firmware to use with lgnspt. If you san get into download mode (power off phone ,connect usb,hold volume down and up plus power ) you should be able to lgnpst back to stock.
Click to expand...
Click to collapse
Alright. I was able to get into download mode. I downloaded lgnpst. Do you have an idea where i would find the other necessary files? Again, total noob. Sorry for all the hand holding. You guys have been great!
Cat Rancher said:
Alright. I was able to get into download mode. I downloaded lgnpst. Do you have an idea where i would find the other necessary files? Again, total noob. Sorry for all the hand holding. You guys have been great!
Click to expand...
Click to collapse
You need to go to the IRC channel to grab the new version of lgnpst and the correct files.
Sent from my LG-E970 using xda premium
Cat Rancher said:
Alright. I was able to get into download mode. I downloaded lgnpst. Do you have an idea where i would find the other Didnecessary files? Again, total noob. Sorry for all the hand holding. You guys have been great!
Click to expand...
Click to collapse
Did you get your phone straightened out?
adfurgerson said:
Did you get your phone straightened out?
Click to expand...
Click to collapse
I'm traveling for work and on a work computer, so the IRC channel is blocked. Of course. I'm heading home tomorrow so hopefully I can get everything back to normal when i get on my home computer. (not having a phone sucks)
Do you all think it would be worth putting the base .5 on my sd card and flashing that, or do you think that wouldnt work? .4 is on there now from my original flash, but that won't work. Just curious.
Well is your phone up and running?
I would think it wouldn't cause harm to try and flash .5 onto it, your phone shouldn't get bricked from it.
i agree with Murasakiii
should be fine to run .5
DraginMagik said:
i agree with Murasakiii
should be fine to run .5
Click to expand...
Click to collapse
Welp, I think i earned the title of first bricked phone. It was able to get into recovery and download mode a couple days ago, but now it wont charge it seems. So i cant get it into any mode to do anything. Ive had it on the charger, wall and usb for a couple hours and nothing is happening. I wonder if i can take it back to my att store and try get a replacement. It is within my 14 day window, and there are "hardware" warranties. I have a feeling they will ask what happened and while i may not initially divulge everything, i sadly cant lie. And since its all my fault, i may chalk it up to learning.
i'd say the device started having issues with the USB. unable to see the device when plugged into the computer and the device won't take a charge. don't hear of too many authentic "bricking's" anymore...it can almost always be resurrected. but if the device won't take a charge your time to resolution is rather limited. good luck.
Cat Rancher said:
Welp, I think i earned the title of first bricked phone. It was able to get into recovery and download mode a couple days ago, but now it wont charge it seems. So i cant get it into any mode to do anything. Ive had it on the charger, wall and usb for a couple hours and nothing is happening. I wonder if i can take it back to my att store and try get a replacement. It is within my 14 day window, and there are "hardware" warranties. I have a feeling they will ask what happened and while i may not initially divulge everything, i sadly cant lie. And since its all my fault, i may chalk it up to learning.
Click to expand...
Click to collapse
Before you leave to go to the store hook it up to a set up jumper cables and then attach the other end to your car battery. Then just tell them when you tried to charge it that it started smoking and wont turn on any more.
The only lie you have to tell them is it happened on the stock charger.
Im on the same boat. Tried going back to stock for a warranty return, and i ended up bricking the phone. Im able to get it to download mode and was able to run the lg tool but it keeps failing on me. And when it does complete it still wont load. Im going to try to make my self a powerd usb cable too see if i can get it to work. Have like 2 or 3 days to try to figure it out. Or elese im out 550 bucks.
Sent from my LG-E970 using xda app-developers app
Other option is just telling them you clicked install for the ota update it rebooted and never came back on. They just wipe them at the repair center anyway if they get them to boot up.
Cat Rancher said:
Welp, I think i earned the title of first bricked phone. It was able to get into recovery and download mode a couple days ago, but now it wont charge it seems. So i cant get it into any mode to do anything. Ive had it on the charger, wall and usb for a couple hours and nothing is happening. I wonder if i can take it back to my att store and try get a replacement. It is within my 14 day window, and there are "hardware" warranties. I have a feeling they will ask what happened and while i may not initially divulge everything, i sadly cant lie. And since its all my fault, i may chalk it up to learning.
Click to expand...
Click to collapse
It took 12 hrs to get a clean download of the stock ROM (AT&T internet sucks in my area). The entire time the screen on my phone was on with the LG splash screen displayed. By the time I got the ROM ready for flash, the battery was dead. I was however able to plug in to the USB on my computer and get enough juice to get into download mode. Ran LGNPST (v2.2.3) and the stock ROM installed with no prob. You might try plugging it in then trying to get into download mode.
EDIT: now that I think about it. You need to have it plugged in to the USB before download mode anyway, so you won't be doing anything different than you already did.

Verizon Ellipsis 7 Unbricking?

I am assuming no one has bricked this device yet but I believe I just did I am rooted and stuck at a welcome screen if anybody has a solution please help! if not I'm going to the store Saturday and telling them a silly lie
Yeah I just did too :/ I installed chainfire 3D and now it stays at the Verizon loading screen. It doesn't shut off, only reboots to this screen. Safe mode doesn't work. I'm hoping there is a way to fastboot, factory restore, etc. via USB. But I think I'm SOL
I just went up to the Verizon store and play dumb I was able to get mine replaced
Sent from my HTCONE using Tapatalk 2
I figured as much. I talked to someone over the phone and they said to bring it in for a replacement. So I'm going in tomorrow for a new one. Lesson learned haha
Sent from my XT907 using Tapatalk
Really hoping someone has came out with a unbrick/really BootLoop of Doom...
So I know a little about android and learn quick and there is very little information on the verizon ellipsis 7. Just so happens I bought one from a side shop and figured out Framaroot will easily root this device. Well you can guess what happen from there. All was going well until i rebooted with rom toolbox pro to change the font format for the second time. Now ever since it hasn't made it past the verizon screen and i cant take it back. Is there any possible way at all of somehow getting a custom recovery on this thing? Or even better a unbrick/bootloop? Oh and I CAN get it to go into stock recovery. Tried the Clear eMMC and Safe Mode but no luck.
Im in the same situation, I'm not able to boot into safe mode and clearing the emmc (formatting /data) doesn't seem to help either. I believe /data is just the user saved data, system data remains the same and is still corrupted. I had rooted, installed xposed framework and a few modules, rebooted fine the first time, but when I went to go change a setting within Ultimate Dynamic Navbar to make the stock navbar hide or not to hide, the script it used killed the tablet and now my wife's valentines day present is stuck in a bootloop. I'm going to try and take it back to verizon tomorrow after work, hopefully I can get yet another free tablet from big red... rvajuggalo said he was able to get it replaced right away even though it was rooted, anyone think I'll be fine taking it back as well? Or should I just wait til someone comes out with a fix for this issue?
wonton9224 said:
Im in the same situation, I'm not able to boot into safe mode and clearing the emmc (formatting /data) doesn't seem to help either. I believe /data is just the user saved data, system data remains the same and is still corrupted. I had rooted, installed xposed framework and a few modules, rebooted fine the first time, but when I went to go change a setting within Ultimate Dynamic Navbar to make the stock navbar hide or not to hide, the script it used killed the tablet and now my wife's valentines day present is stuck in a bootloop. I'm going to try and take it back to verizon tomorrow after work, hopefully I can get yet another free tablet from big red... rvajuggalo said he was able to get it replaced right away even though it was rooted, anyone think I'll be fine taking it back as well? Or should I just wait til someone comes out with a fix for this issue?
Click to expand...
Click to collapse
I was able to get a new one and mine was stuck in a boot loop
Sent from my XT907 using Tapatalk
Elipsis Bootloop Help!
rvajuggalo said:
I am assuming no one has bricked this device yet but I believe I just did I am rooted and stuck at a welcome screen if anybody has a solution please help! if not I'm going to the store Saturday and telling them a silly lie
Click to expand...
Click to collapse
If anyone has a clean copy of the system or firmware directories can you please share with me? --- Also if anyone knows how to get into the stock recovery without android debugging please explain? On a final note if anyone has a custom recovery that they could share that would be amazing as well. I'm in a bootloop and have been stuck in it for a couple weeks. Any assistance would be most appreciated.
dduncan55330 said:
I was able to get a new one and mine was stuck in a boot loop
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Thanks, that confirms it for me, I'll definitely take it back tonight, hopefully it's in stock and not back-ordered
wonton9224 said:
Thanks, that confirms it for me, I'll definitely take it back tonight, hopefully it's in stock and not back-ordered
Click to expand...
Click to collapse
VZW made me send my ellipsis to them for the screen issue after update, i unrooted it before sending it. They were able to fix it somehow because they sent mine right back fixed(i wrote down the serial)
mtk_droidroot_backup_Verizonellipses...HERE
Backed up my QMV7B before i Bricked it, now ive got two mtk paperweights pm me ,I'll link you to a backup on my drive. also bookending my desk is a lovely alcatel oone touch fierce 7024n which proudly boasts "ERROR 101 This phone has been flashed with unauthorized firmware and has been locked." niether of these will respond to any flash utility ive been able to conjure
Maybe you can use it. I need some hands on guidance flashing these. way too many tutos,way too many fllashtools, way too many drivers, usb cables, homemade serial cables, linux distros ,windows xp,7,8,8.1, hours, days,weeks,....... you get the picture.
apt-get ME_A_STRAIGHT_JACKET!
I know it can be done, i would like to learn from someone who ddoes it. its taking way to long to teach myself. and i still kinda like my wife but i doubt shell take much more.
#BRICKED --help
dereksilvers said:
Backed up my QMV7B before i Bricked it, now ive got two mtk paperweights pm me ,I'll link you to a backup on my drive. also bookending my desk is a lovely alcatel oone touch fierce 7024n which proudly boasts "ERROR 101 This phone has been flashed with unauthorized firmware and has been locked." niether of these will respond to any flash utility ive been able to conjure
Maybe you can use it. I need some hands on guidance flashing these. way too many tutos,way too many fllashtools, way too many drivers, usb cables, homemade serial cables, linux distros ,windows xp,7,8,8.1, hours, days,weeks,....... you get the picture.
apt-get ME_A_STRAIGHT_JACKET!
I know it can be done, i would like to learn from someone who ddoes it. its taking way to long to teach myself. and i still kinda like my wife but i doubt shell take much more.
#BRICKED --help
Click to expand...
Click to collapse
Do you think I could get a copy of that backup file?
DYI
rvajuggalo said:
I am assuming no one has bricked this device yet but I believe I just did I am rooted and stuck at a welcome screen if anybody has a solution please help! if not I'm going to the store Saturday and telling them a silly lie
Click to expand...
Click to collapse
If you're willing to open the back plate. (Back plate just pulls off. I'd suggest opening the sim/sd card slot and using that to pull it off. You need to disconnect the battery wait a few seconds, reconnect and then boot into recovery.
1. Black plate removal
2. Disconnect battery
3. Wait a few seconds
4. Reconnect battery
5. Press and hold Power and Down volume button until you see "Powered by Android"
6. Release the power button continue to hold down volume
7. Once in Factory recovery mode choose your best option
(I just factory reset it)
:good:
-love
A new development, possibly.
dereksilvers said:
Backed up my QMV7B before i Bricked it, now ive got two mtk paperweights pm me ,I'll link you to a backup on my drive. also bookending my desk is a lovely alcatel oone touch fierce 7024n which proudly boasts "ERROR 101 This phone has been flashed with unauthorized firmware and has been locked." niether of these will respond to any flash utility ive been able to conjure
Maybe you can use it. I need some hands on guidance flashing these. way too many tutos,way too many fllashtools, way too many drivers, usb cables, homemade serial cables, linux distros ,windows xp,7,8,8.1, hours, days,weeks,....... you get the picture.
apt-get ME_A_STRAIGHT_JACKET!
I know it can be done, i would like to learn from someone who ddoes it. its taking way to long to teach myself. and i still kinda like my wife but i doubt shell take much more.
#BRICKED --help
Click to expand...
Click to collapse
After making edits in system files I broke my QMV7B. Hangs on powered by android logo. In a panic, I wiped emmc from factory more (Chinese).. This reset ADB keys, and complicated matters further. After some digging I may have caught a break... I have figured out a way to stop and suspend the tablet in it's pre boot, or preloader, state. While suspended, it maintains COM3 connection with SPFT, and does not power cycle on and off. It also successfully installs it's onboard Preloader driver without error. Problem is that I need help attempting flash (for best chances)...
needing stock 4.4.4 fit the qmv7, or possibly advice on stock recover if possible.. I have successfully flased devices with Odin before, and have rooted almost every I have had.. I just want the best chance for success, and not to full brick the tab.. this could also be a solution for newer devices as well, but would like to for a good developer to speak with me before I post my findings. I will also post if I get the stock room compatible for flashing with SP Flash tool.. thanks guys..
Help
Please post specifics on how you achieved suspending in Preloader mode. That would help me alot.
I really need the un-rooted qmv7a stock rom, if any one could provide, that would be fan-freaking-tabulous lol...
no, for real i need the stock rom. I'd really appreciate it.
BTW
if you wanna get clean root on this device, i suggest this- http://forum.xda-developers.com/showthread.php?t=2748169
(has nothing to do with my need for a clean start, that was my own carelessness...)
Bondaddict said:
Please post specifics on how you achieved suspending in Preloader mode. That would help me alot.
Click to expand...
Click to collapse
Needle point method at USB port
ellipsis 7
I root my ellipsis 7 and install clockworkmod recovery after reboot in recovery struck on boot loop and not even access on recovery mode plz help
anybody still own one of these? lol
---------- Post added at 04:59 AM ---------- Previous post was at 04:41 AM ----------
LoveAboveAll said:
If you're willing to open the back plate. (Back plate just pulls off. I'd suggest opening the sim/sd card slot and using that to pull it off. You need to disconnect the battery wait a few seconds, reconnect and then boot into recovery.
1. Black plate removal
2. Disconnect battery
3. Wait a few seconds
4. Reconnect battery
5. Press and hold Power and Down volume button until you see "Powered by Android"
6. Release the power button continue to hold down volume
7. Once in Factory recovery mode choose your best option
(I just factory reset it)
:good:
-love
Click to expand...
Click to collapse
Hey man it's been 5years & I just wanna say thank you for posting this as I just managed to get into factory mode thanks to your comment xD. factory mode didn't help me a bit but maybe when I get to a PC I can use mtk tools to get a shell or something from there. Thanks again and if anybody has anything more than what's on here about this tablet please contact me as I feel like the last human on Earth with one ????
Yeh
I have one??
And Reading all topics about rooting this tablet...i'm afraid to do that?

[Q] Bricked Venue 8 7840; accidently applied OTA with root.

Edit: This was done on a Venue 8 7840.
As mentioned, I ran the OTA like an idiot forgetting I was still rooted and of course, bootloop. I am stuck on the Intel Inside screen, with the developer flash tool it will show the device is connected but it comes and goes so I am not sure what I can do, if anything, to revert to stock or do anything. Does anybody have any suggestions or am I SOL? Any help is greatly appreciated. Thanks in advance! :crying:
Try using the Phone Flash Tool utility provided in the developer edition files, and follow the process used to flash the developer edition firmware, but instead flash this unbrick.zip:
https://mega.co.nz/#!Vgw1CTYT!y1_tSTCMmzrhJSQy0lxwY59iyRhdJovC-IDMF25PB4k
Let me know how that goes for you.
EDIT:
For the flashing process, try with the tablet completely off and disconnected, then load the unbrick.zip file in Phone Flash Tool, then click the "Start to flash" button (the one near the bottom should be blue/clickable), then once it starts counting (attempt #0, attempt #1, etc.) then plug in the USB to the tablet. It should then flash the firmware pieces.
xBIGREDDx said:
Try using the Phone Flash Tool utility provided in the developer edition files, and follow the process used to flash the developer edition firmware, but instead flash this unbrick.zip:
https://mega.co.nz/#!Vgw1CTYT!y1_tSTCMmzrhJSQy0lxwY59iyRhdJovC-IDMF25PB4k
Let me know how that goes for you.
EDIT:
For the flashing process, try with the tablet completely off and disconnected, then load the unbrick.zip file in Phone Flash Tool, then click the "Start to flash" button (the one near the bottom should be blue/clickable), then once it starts counting (attempt #0, attempt #1, etc.) then plug in the USB to the tablet. It should then flash the firmware pieces.
Click to expand...
Click to collapse
Thank you very much for the reply! I'm going to give it a shot now will report back shortly
First off, thank you for the reply, I flashed the unbrick.zip and it flashed successfully. Now the device is just showing a USB symbol with a filled progress bar under it and does not do anything else, still not able to get into bootloader or anything. Any ideas?
xBIGREDDx said:
Try using the Phone Flash Tool utility provided in the developer edition files, and follow the process used to flash the developer edition firmware, but instead flash this unbrick.zip:
https://mega.co.nz/#!Vgw1CTYT!y1_tSTCMmzrhJSQy0lxwY59iyRhdJovC-IDMF25PB4k
Let me know how that goes for you.
EDIT:
For the flashing process, try with the tablet completely off and disconnected, then load the unbrick.zip file in Phone Flash Tool, then click the "Start to flash" button (the one near the bottom should be blue/clickable), then once it starts counting (attempt #0, attempt #1, etc.) then plug in the USB to the tablet. It should then flash the firmware pieces.
Click to expand...
Click to collapse
I thought I'd move over to this thread to keep it all together.
If I let the tablet boot normally, I get the following output: http://pastebin.com/zfsPRdC5 and the flash fails.
If I boot the tablet with power + volup, the flash is successful and I get http://pastebin.com/kQg8vwLC but I'm still on the USB screen.
If I flash the Dell Opensource IFWI + DNX (booted with power+volup) from the opensource package, it goes back to bootlooping with the intel logo.
Quick update, I don't have any further things to try at the moment, but I see that for past tablets Dell has released droidboot OS image which lets you recover a bricked device, so I've emailed support to see if they'll release it for this one. I'll post back once I hear something.
xBIGREDDx said:
Quick update, I don't have any further things to try at the moment, but I see that for past tablets Dell has released droidboot OS image which lets you recover a bricked device, so I've emailed support to see if they'll release it for this one. I'll post back once I hear something.
Click to expand...
Click to collapse
Thank you for all your help, I am not very familiar with Dell tablet devices so getting started was fine, rooted and all. Thank I had to go and flash the update without removing SuperSU like an idiot, LOL. Usually on any device I do this just in case, even if it *says* it's not necessary. Anyways, I look forward to hearing what they have to say, I figured I was stuck with a dead tablet, which I suppose could still be the case. Of course, still getting the USB logo when I try power. Thanks again @xBIGREDDx you're the man. :silly:
xBIGREDDx said:
Quick update, I don't have any further things to try at the moment, but I see that for past tablets Dell has released droidboot OS image which lets you recover a bricked device, so I've emailed support to see if they'll release it for this one. I'll post back once I hear something.
Click to expand...
Click to collapse
Any word back from Dell support? Or is it looking like this is a lost cause and I should just trash this thing I tried to get a hold of them myself but it is damn near impossible.
xploitnt said:
Any word back from Dell support? Or is it looking like this is a lost cause and I should just trash this thing I tried to get a hold of them myself but it is damn near impossible.
Click to expand...
Click to collapse
Nothing yet; I'd give them another week or two... they do take quite a while sometimes with these things.
xBIGREDDx said:
Nothing yet; I'd give them another week or two... they do take quite a while sometimes with these things.
Click to expand...
Click to collapse
If all else fails just request and RMA and send it in for a replacement. I've always had great support from them on their business side. We usually get their accidental damage coverage on our work machines that replaces them for any reason. I have my 7840 through our work account and I have also rooted it but I have no doubt that I could send it back to them for a replacement if I brick it.
any new infos?
Hy ,
Are there any new infos about this problem?
I have the same problem with stuck at the usb logo.
No fastboot, no adb. I flashed many ifwi, dnx combinations but i get black screen or usb logo.
If you could repair your device, i would like no know please.
thx
i don't think my experience helps but i will post it anyway. When i turned on my tablet on today, it somehow started the upgrading process by itself when i try to open the play store. I thought i would brick the device since i rooted my tablet already, but i somehow made it. I lost root, but i was able to keep my data intact.
UPDATE:
Dell has posted a "blankphone" zip on their open source site. This will re-format your device and it does not contain a system image, but it should re-configure your partitions and flash a functioning fastboot image. There has been one report of this somehow fully fixing a system (I suspect the OTA was still sitting in a cache somewhere). Also based on the filenames in the zip, I think this might contain unlocked firmware. Either way, if we can get a system.img into a flashable state, you should be good to go.
Also they finally renamed the folder to "Moorefield" instead of "Merrifield"
"IntelAndroid-FBRL-07-24-2015" will cure the bootloop?
i flashed xposed to my 7840 lollipop and bootlooping.
i flashed it with "IntelAndroid-FBRL-07-24-2015".
u can find this in other device forum.
so, i flashed uninstaller of xposed, then 7840 is escaped from bootloop.
btw can anyone flash the appropriate xposed for 7840 lollipop with this tool?
hope 5.1.1 custom rom can be flashed...
Did Dell ever respond or has anyone else found a solution? I was ready to buy a 7840 but the apparent lack of support from Dell and minimal third party development has me seriously considering an Nvidia Shield, despite its inferior display and design. They're the same price and appear to be pretty evenly matched in all respects except 3D performance.
Any input that would help me with that decision would be appreciated.

Categories

Resources