SO Im trying to reflash 154... And it failed, Flashed again and it failed...
Now I am seeing failed to boot 3
Starting RSD Mode
try to flash 154 again and it fails to enumerate? Failed to re-eumerate after RAM-Downloader
On the phone I see:
SVF 108:1:2
Failed to Boot 3
Starting RSD Mode
SVF 106:1:2
sec_exception: b655,eddc, eb
Anyone able to walk me through this?
Anyone? Anyone else gone through this?
You have been heard
Personally I dont know how to fix this because iv not experienced it. Are you using RSD 5.5? Have you tried different sbfs?
hodiedodie said:
Personally I dont know how to fix this because iv not experienced it. Are you using RSD 5.5? Have you tried different sbfs?
Click to expand...
Click to collapse
RSDlite 5.6
Define your initial "failed". RSD is known to say failed during the final reboot, if no errors show up on the phones screen, ignore it. Also try reinstalling the drivers (can't find it but am sure it's reupped in the dev subforum) and using the latest RSD which is RSD lite v5.6 (still have yet to move this to my server, sorry). If 154 fails try 198_7, sometimes it takes a couple runs to get it to work (especially if you didn't hard reset the phone prior to flashing or coming from CM7).
Lokifish Marz said:
Define your initial "failed". RSD is known to say failed during the final reboot, if no errors show up on the phones screen, ignore it. Also try reinstalling the drivers (can't find it but am sure it's reupped in the dev subforum) and using the latest RSD which is RSD lite v5.6 (still have yet to move this to my server, sorry). If 154 fails try 198_7, sometimes it takes a couple runs to get it to work (especially if you didn't hard reset the phone prior to flashing or coming from CM7).
Click to expand...
Click to collapse
came from bone stock.... it said failed and i manual rebooted it and presto into failed to boot 3.
Its supposed to reboot several times on its own through RSD.... mine doesnt seem to want to reboot.
Right now RSD is creating image file.... 47%
Im betting its going to hang at BP Pass through mode
gothymp said:
Right now RSD is creating image file.... 47%
Im betting its going to hang at BP Pass through mode
Click to expand...
Click to collapse
Go, no go? What's the word?
Are familiar with Linux? For some reason I have had issues with rsd and fastboot on windows. Took me a few hours tinkering with both until i gave up and used the Linux tools. Flashing sbf is waaaaay faster on Linux vice windows.
This is for the atrix but the principles are the same:
SBF Flash
forum.xda-developers.com/showthread.php?t=1165672
Fastboot
forum.xda-developers.com/showthread.php?t=1138092
I really all depends on you comfort level inside a terminal. If you are not familiar with Linux and want to learn try picking up a dummies book for Ubuntu or open suse. That is how i learned back on red hat 8. The distros are a little different between each other, but the fundamental framework underneath is essentially the same.
Sent from my MoPho. All typos are the phones fault.
Cory-Buchers-iMac:moto corybucher$ sudo ./sbf_flash.sh moto.sbf
SBF FLASH 1.24 (mbm)
http://opticaldelusion.org
mmap: Cannot allocate memory
Usage: sbf_flash <filename>
This is the error I keep getting???
Google says that you need more system memory, or you need to allocate more memory to your virtual machine. Remember you are loading the whole sbf which can be upwards of 2gb in size.
Sent from my MoPho. All typos are the phones fault.
atroph said:
Google says that you need more system memory, or you need to allocate more memory to your virtual machine. Remember you are loading the whole sbf which can be upwards of 2gb in size.
Sent from my MoPho. All typos are the phones fault.
Click to expand...
Click to collapse
I'm running this from my Mac. My phone is saying
SVF:108:1:2
Failed to boot 3
Starting RSD mode
Has been all night and I've tried flashing the SBF File but it never went through with RSD Lite. Kept on failing. I started off trying to unlock it and flashed the wrong sbf file in the first place. Thinking I bricked my phone. Any suggestions?
You are soft bricked. Fatal? No. PITA? Yes.
What are the specs of your Mac. Specifically how much ram does it have?
Sent from my MoPho. All typos are the phones fault.
atroph said:
You are soft bricked. Fatal? No. PITA? Yes.
What are the specs of your Mac. Specifically how much ram does it have?
Sent from my MoPho. All typos are the phones fault.
Click to expand...
Click to collapse
I have 4 gigs with a dual core
---------- Post added at 10:11 AM ---------- Previous post was at 09:55 AM ----------
corybucher said:
I have 4 gigs with a dual core
Click to expand...
Click to collapse
Well now I have another problem, my battery is dead!
---------- Post added at 10:43 AM ---------- Previous post was at 10:11 AM ----------
corybucher said:
I have 4 gigs with a dual core
---------- Post added at 10:11 AM ---------- Previous post was at 09:55 AM ----------
Well now I have another problem, my battery is dead!
Click to expand...
Click to collapse
Alright I find a thread that explained how to charge the battery with a soft brick so hopefully this will work.
Mine is still a no go.... is it possible to flash via linux live CD?
/
or virtual machine
I Have VMware and Red hat..... 4gigs of ram and ample hard drive...
I bet rSDlite doesnt like 64bit windows to well
corybucher said:
I have 4 gigs with a dual core
Well now I have another problem, my battery is dead!
---------- Post added at 10:43 AM ---------- Previous post was at 10:11 AM ----------
Alright I find a thread that explained how to charge the battery with a soft brick so hopefully this will work.
Click to expand...
Click to collapse
I am having nearly identical problems as you, including the dead battery. What thread did you find that shows how to charge your battery while soft bricked?
Edit: Nevermind, I found the thread...
Any luck on restoring from that failed to boot 3?
Weirdo0815 said:
I am having nearly identical problems as you, including the dead battery. What thread did you find that shows how to charge your battery while soft bricked?
Edit: Nevermind, I found the thread...
Any luck on restoring from that failed to boot 3?
Click to expand...
Click to collapse
Havent had any luck at all so this is what I did. I called Sprint and told them that I need help trying to factory reset my phone and listened to the rep explain the steps to do so knowing that it wasn't even on and I couldn't do anything. After she had finished explaining how to do it I told her the screen came back saying the failed to boot 3. After a couple of minutes I told her it was still stuck on that screen (duh) and asked if I should pull the battery. She said yes and of course I said it came to the same screen. She transferred me to a tech rep and then that rep told me to put it into fast boot (volume down and power) and again (duh) came to the same screen. The rep then told me to take it in to a repair center and they can help, so she gave me a ticket and set an appointment and I took it there and should them what was happening (playing dumb) and the tech took my phone and told me to come back at 5:30 and it should be fixed (duh it wont) So most likely I will get a replacement and all is good. And right now I am waiting to go pick up either my fixed phone or replacement. Moral of the story is I called first and the REP is the one who told me what to do. So lets hope this will work if anyone wants to give this a try go ahead. I will update you when I come back.
corybucher said:
Havent had any luck at all so this is what I did. I called Sprint and told them that I need help trying to factory reset my phone and listened to the rep explain the steps to do so knowing that it wasn't even on and I couldn't do anything. After she had finished explaining how to do it I told her the screen came back saying the failed to boot 3. After a couple of minutes I told her it was still stuck on that screen (duh) and asked if I should pull the battery. She said yes and of course I said it came to the same screen. She transferred me to a tech rep and then that rep told me to put it into fast boot (volume down and power) and again (duh) came to the same screen. The rep then told me to take it in to a repair center and they can help, so she gave me a ticket and set an appointment and I took it there and should them what was happening (playing dumb) and the tech took my phone and told me to come back at 5:30 and it should be fixed (duh it wont) So most likely I will get a replacement and all is good. And right now I am waiting to go pick up either my fixed phone or replacement. Moral of the story is I called first and the REP is the one who told me what to do. So lets hope this will work if anyone wants to give this a try go ahead. I will update you when I come back.
Click to expand...
Click to collapse
Well I was hoping for better news but I was kind of expecting this. A week after I bought my Photon, I had a very similar thing to our issues happen to my phone all on its own. I took it into my local repair place and they gave me a new one (technically a refab i think). So I am trying one last time to flash and if that doesn't work, I am going to take mine in...
So is it possible to flash it via VMware? I have Redhat, Gnome, or suse in VM format....
Yes it is possible. Make sure you have enough ram allocated to the vm
IMO best bet would be a live CD vice the vm. But either should work.
I flash in a XP vm on my Ubuntu box. Then I found the Linux tools and installed the android sdk. Flashing in Linux is sooooooo much faster than rsd.
Sent from my MoPho. All typos are the phones fault.
Related
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...
Alright here goes
So my question is, what options do i have? I can't access any recovery options (Fastboot, android recovery, etc) and my RSD lite wont connect.
Short Story
Every time i try to boot my Atrix (after trying to update CherryPi), I get the Failed to boot 2, Starting RSD mode. Unfortunately, when I plug my phone into a computer RSD doesn't see it. It's like its not even phased.
Long Story
Okay, so I got my atrix not too long ago. Got my phone rooted at proceeded to use gingerblur. Then shortly there after, I attempted to upgrade to the Gingerbread OTA update, which got me stuck in a boot loop. (Now I'm a little confused, I don't think that I have unlocked my phone at all. I don't ever recall "unlocked" being on the boot screen at all). From this point I don't think RSD was working. I spent about a week trying to get it to work. Then I was able to fastboot flash the stock img files for gingerbread to my phone. So now I had a working gingerbread atrix. I sat stock for a little while, figgured out how to root via fastboot (again, no rsd support at this point). After I was rooted I installed CherryPi 0.3 via CWM. It worked great, a couple of days later I went to do the CherryPi 0.X > 0.5 and it flashed with CWM "successfully" got to the AT&T logo on bootup and then crashed and has been giving me the failed to boot 2.
I hope i've given you guys enough info. If any of you super hackers live in San Diego, I'd be more then willing to bring my phone over for you to figure out. So I just really need to know what my options are. If I take it back to AT&T will they likely give me a new one? (I'm good at playing dumb). I traded my phone originally so I don't know what kind of warranty is in place. Can I contact Motorola and get a new handset? Just looking for suggestions.
Thanks guys
Have you tried to reinstall the motorola driver?
Yes, when I first "lost" RSD support and since the current "Failed to boot 2" message.
It has the flash interface when I plug it in, but the motorola software dosent see it, same with RSD. just like nothing is plugged in.
Why not put it into fastboot mode when it reboots and then flash a different file?
phobos512 said:
Why not put it into fastboot mode when it reboots and then flash a different file?
Click to expand...
Click to collapse
It won't boot into any other mode, upon putting the battery in, it shows the dual core logo for about 1.5-2 seconds that pops up the "Failed to boot 2" message and starting RSD mode.
Judging by your first post u mentioned that u never unlocked your boot loader, unless I'm reading this wrong. These ROMS weren't meant to be flashed with the Bootstrapped version of CWM (The one that requires u to be plugged in to AC power) so not sure if that sheds any light on the subject or not. Again, if I read your post wrong, I apologize.
Sent from my MB860 using XDA Premium App
Phalanx7621 said:
Judging by your first post u mentioned that u never unlocked your boot loader, unless I'm reading this wrong. These ROMS weren't meant to be flashed with the Bootstrapped version of CWM (The one that requires u to be plugged in to AC power) so not sure if that sheds any light on the subject or not. Again, if I read your post wrong, I apologize.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Ya, from what I can tell its Motorola locking me out for using an modified rom. But I think that I should be able to return to a stock firmware using RSD lite or the Motorola software restore from thier site, but neither see my phone connected. This leads me to belive that somewhere in the process the RSD protocol got messed up. Now I really don't know much, just enough to be dangerous. So if theres anyone that can tell me if I'm even looking the right direction.
And if I am right is there anything I could possibly do?
gjRabbit said:
Alright here goes
So my question is, what options do i have? I can't access any recovery options (Fastboot, android recovery, etc) and my RSD lite wont connect.
Short Story
Every time i try to boot my Atrix (after trying to update CherryPi), I get the Failed to boot 2, Starting RSD mode. Unfortunately, when I plug my phone into a computer RSD doesn't see it. It's like its not even phased.
Long Story
Okay, so I got my atrix not too long ago. Got my phone rooted at proceeded to use gingerblur. Then shortly there after, I attempted to upgrade to the Gingerbread OTA update, which got me stuck in a boot loop. (Now I'm a little confused, I don't think that I have unlocked my phone at all. I don't ever recall "unlocked" being on the boot screen at all). From this point I don't think RSD was working. I spent about a week trying to get it to work. Then I was able to fastboot flash the stock img files for gingerbread to my phone. So now I had a working gingerbread atrix. I sat stock for a little while, figgured out how to root via fastboot (again, no rsd support at this point). After I was rooted I installed CherryPi 0.3 via CWM. It worked great, a couple of days later I went to do the CherryPi 0.X > 0.5 and it flashed with CWM "successfully" got to the AT&T logo on bootup and then crashed and has been giving me the failed to boot 2.
I hope i've given you guys enough info. If any of you super hackers live in San Diego, I'd be more then willing to bring my phone over for you to figure out. So I just really need to know what my options are. If I take it back to AT&T will they likely give me a new one? (I'm good at playing dumb). I traded my phone originally so I don't know what kind of warranty is in place. Can I contact Motorola and get a new handset? Just looking for suggestions.
Thanks guys
Click to expand...
Click to collapse
Hey man, I have the same problem with you.. have you some progress for that..
I find some infor from forum that this kind of hard brick can be solved by using the developping cable to reflash the sbk file, this method is pending at the SBK file is unavailable which is not released out by MOtorola.. I find a one of my friend who is working in MOTO (Tianjing, CHINA) to see my device, I hope he can help me to unbrick my phone.. when i have good news, I'll update it.
I tried reflashing my atrix with the 1.8.5 update and my atrix is now pretty much bricked. Starting it up now presents a boot error, "Failed to boot (0x1000)", followed by a quick "NVFlash" message then it shuts off. I'd be willing to pay for someone to fix/help me fix it if they think they have the skills necessary. (If it's cheaper than buying a new atrix.)
Anyone have any help?
Thanks.
There is no fix for this
sent from cm7 atrix 1.3ghz
For what it's worth, motorola has informed me that they offer a repair service for $110 + tax.
hesif said:
For what it's worth, motorola has informed me that they offer a repair service for $110 + tax.
Click to expand...
Click to collapse
Sounds like moto caught on to what's been happening. I wonder if they send a refurb or actually fix "your" device for the $110? Another poster in the HARD BRICK WARNING thread said Moto had no idea what this problem (your problem with the NVFlash and all) is or how to fix it. The poster then went on to say Moto sent him a refurb as his was not fixable. May contact him and get more info.
Either way, you took the risk and didnt read all the warnings. Sucks to say it, but you will have to pay to play. Welcome to voiding warranties . On another note, $110 isnt that bad of a deal considering its a $500 phone and hell my insurance deductible is that ($110) alone so I think you're possibly coming out on top here.
Yeah. I really don't mind spending up to ~$100. Purchasing an out-of-contract Atrix brand new would suck much worse.
if u haven't got someone to unbrick your device yet, mobiletechvideos met be able to help you. they do jtag unbrick fixes, which is a hard brick. I would go to his website and shoot him an email explaining your situation. He only charges $40.
i got same problem .just bought this atrix 4 days ago..
Can anybody help?
Please help!
I was using the sbf (post 22) and instructions (post 27) from the "Gingerbread on Telstra yet?" thread on Atrix Forums on my Telstra stock Atrix:
And it was all going well until I got:
"phone 0000 switching device to bp pass through mode"
That fails and I get:
"Failed flashing process interface ap-os error flashing subscriber unit device api error 0xE003003F address 0x12000150 command addr 0xE023203f phone connected"
It shows the logo while booting and freezes at "Failed to boot 4 Starting RSD mode"
I can still get connected through RSD-lite but I don't know how to proceed
I have tried it 3 times, same result.
I put pudding intl-fix-try1.sbf on there and that seems to work but still fails to boot but now the device just powers off when I try to put it into fastboot mode.
Thanks for looking.
Richard
---------- Post added at 04:00 PM ---------- Previous post was at 03:01 PM ----------
Fixed using sbf flash on my mac, phew!
> Fixed using sbf flash on my mac, phew!
hi, may I know which file you flashed to fix it ?
I got same error msg as you
Thanks so much
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?
Device:
New Verizon VS985 with 12c rom. Phone was in working order prior to brick.
How I got into brick:
1. Rooted using ADB push the UPDATE-SuperSU-v2.46.zip (it was successful as I gained root after reboot)
2. Tried to install twrp using this post, which I failed to realize it was meant for 23b and not 12c. This is where I suspected I messed up.
http://forum.xda-developers.com/showpost.php?p=59309598&postcount=190
I did not put the img file on my phone, but leave it on my computer in the ADB folder. I then did the first two command lines:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
and noticed the computer says Device Was Out of Space. I thought the first two commands did not go through, and I stopped without doing the rest of the commands. I think it rebooted ok after this before I did step 3.
3. I then unlocked bands 3 & 7 using this method:
http://forum.xda-developers.com/verizon-lg-g3/general/unlocked-lte-bands-vs985-t2909150
It goes like what the instruction says. However after the reboot, my phone went into brick.
Symptoms:
1. Screen does not turn on. No LED light. No LG Startup logo. No red Verizon logo. Nothing at all on screen when pressing the power button.
2. When I hold the volume up while plugging in USB cable (to computer), it vibrates once like it goes to download mode or battery is being charged. The screen is off so I cannot tell which mode it is in.
3. While in this state, the computer does detect the 4 USB devices. However, it only would load the drivers for the first two, and the last two would keep searching but never loaded.
4. I do have the important LGE Mobile in Device Manager under Ports, and I was able to change it to COM41 for the official LGFlashTool for the .TOT and .dll Unroot/Unbrick method.
5. On the LGFlashTool, the box 1 became yellow and said READY. However, when I unplugged the USB cable and plugged it back, after the "Waiting for Connection.", when it tried to do the actual flash, it would fail. See the attached picture.
6. I then uninstalled LGFlashTool and tried the KDZ Method (with 10b KDZ rom), the LGFlashTool2014 will recognize the phone and show the correct COM, but when the actual flashing happen, it will fail. One time it said external server is not available. The other times, it fail for other reasons. (I forgot to capture the screen last night, but will do tonight.) Basically it won't flash.
Any suggestions?
acefr said:
Device:
New Verizon VS985 with 12c rom. Phone was in working order prior to brick.
How I got into brick:
1. Rooted using ADB push the UPDATE-SuperSU-v2.46.zip (it was successful as I gained root after reboot)
2. Tried to install twrp using this post, which I failed to realize it was meant for 23b and not 12c. This is where I suspected I messed up.
http://forum.xda-developers.com/showpost.php?p=59309598&postcount=190
I did not put the img file on my phone, but leave it on my computer in the ADB folder. I then did the first two command lines:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
and noticed the computer says Device Was Out of Space. I thought the first two commands did not go through, and I stopped without doing the rest of the commands. I think it rebooted ok after this before I did step 3.
3. I then unlocked bands 3 & 7 using this method:
http://forum.xda-developers.com/verizon-lg-g3/general/unlocked-lte-bands-vs985-t2909150
It goes like what the instruction says. However after the reboot, my phone went into brick.
Symptoms:
1. Screen does not turn on. No LED light. No LG Startup logo. No red Verizon logo. Nothing at all on screen when pressing the power button.
2. When I hold the volume up while plugging in USB cable (to computer), it vibrates once like it goes to download mode or battery is being charged. The screen is off so I cannot tell which mode it is in.
3. While in this state, the computer does detect the 4 USB devices. However, it only would load the drivers for the first two, and the last two would keep searching but never loaded.
4. I do have the important LGE Mobile in Device Manager under Ports, and I was able to change it to COM41 for the official LGFlashTool for the .TOT and .dll Unroot/Unbrick method.
5. On the LGFlashTool, the box 1 became yellow and said READY. However, when I unplugged the USB cable and plugged it back, after the "Waiting for Connection.", when it tried to do the actual flash, it would fail. See the attached picture.
6. I then uninstalled LGFlashTool and tried the KDZ Method (with 10b KDZ rom), the LGFlashTool2014 will recognize the phone and show the correct COM, but when the actual flashing happen, it will fail. One time it said external server is not available. The other times, it fail for other reasons. (I forgot to capture the screen last night, but will do tonight.) Basically it won't flash.
Any suggestions?
Click to expand...
Click to collapse
not sure if i can be of assistance, i was more dumbfounded by some of what you wrote, i had to reply.
just to be clear,
you were not previously rooted,
pushed the su zip that can only be flashed from custom recovery,
how did you install the zip with no twrp and no root?
then rebooted and had root?
anyways,
then dd the aboot,
the out of space is normal, the first code zeroes out the partition, the second line flashes the new code.
moving on,
you basically flashed the same aboot you already had on being on 12b,
the twrp you flashed is fine, it works on all versions, so thats not the issue.
--not trying to sound mean with my replies above, just some of what you said is theoretically impossible.
so, up to this point, assuming you got root somehow, nothing you did is wrong or would cause the problem you now have. (aside from the rooting)
i need to go look into this link you posted about the bands.
just out of curiosity, why were you using my post (now deleted) to try and put twrp on? its for L not kk, and its actually good you stopped when you did or you would have had other serious issues after flashing the L boot onto a kk stock rom.
anyways, again, not trying to sound mean, this is mostly unbelievable..
---------- Post added at 07:10 PM ---------- Previous post was at 06:47 PM ----------
so, i looked at the other thread and still dont see any issues. until you answer my questions, i cant speculate as to the cause.
only suggestion i could make,
remove the battery, sim card, and sdcard.
hold the vol down and power, and put the battery back in, and see if anything happens.
bweN diorD said:
not sure if i can be of assistance, i was more dumbfounded by some of what you wrote, i had to reply.
just to be clear,
you were not previously rooted,
pushed the su zip that can only be flashed from custom recovery,
how did you install the zip with no twrp and no root?
then rebooted and had root?
anyways,
then dd the aboot,
the out of space is normal, the first code zeroes out the partition, the second line flashes the new code.
moving on,
you basically flashed the same aboot you already had on being on 12b,
the twrp you flashed is fine, it works on all versions, so thats not the issue.
--not trying to sound mean with my replies above, just some of what you said is theoretically impossible.
so, up to this point, assuming you got root somehow, nothing you did is wrong or would cause the problem you now have. (aside from the rooting)
i need to go look into this link you posted about the bands.
just out of curiosity, why were you using my post (now deleted) to try and put twrp on? its for L not kk, and its actually good you stopped when you did or you would have had other serious issues after flashing the L boot onto a kk stock rom.
anyways, again, not trying to sound mean, this is mostly unbelievable..
Click to expand...
Click to collapse
Not a problem. I understand the more detail I give, the higher chance there is a solution. I appreciate your effort in trying to solve it.
1. the phone was originally in factory new state. No custom recovery, no root, stock 12c rom.
2. I used the following method to root, and it appeared ok as the phone was able to reboot and granted SU when I did step 2. It was late night and my mind was not clear when I did step 2. I wonder why I didn't see the Lollipop in the title.
http://forum.xda-developers.com/android/help/lg-tribute-development-t2953342/page38#376
I will try the volume down+power tonight and report back. Again thanks for your input. The rooting method is a suspect too, as it says G2 in the posting. I was directed there from a G3 posting.
acefr said:
Not a problem. I understand the more detail I give, the higher chance there is a solution. I appreciate your effort in trying to solve it.
1. the phone was originally in factory new state. No custom recovery, no root, stock 12c rom.
2. I used the following method to root, and it appeared ok as the phone was able to reboot and granted SU when I did step 2. It was late night and my mind was not clear when I did step 2. I wonder why I didn't see the Lollipop in the title.
http://forum.xda-developers.com/android/help/lg-tribute-development-t2953342/page38#376
Click to expand...
Click to collapse
ok, that makes way more sense. you were indeed rooted and were pushing the su zip to flash in twrp i assume.
so anyways,
ohhh wait a minute, i just re read what you wrote. did you flash the first 2 img's from my post? 4 lines of code?
bweN diorD said:
ok, that makes way more sense. you were indeed rooted and were pushing the su zip to flash in twrp i assume.
so anyways,
ohhh wait a minute, i just re read what you wrote. did you flash the first 2 img's from my post? 4 lines of code?
Click to expand...
Click to collapse
Yes, I gained root before trying to install twrp. I stopped after the first 2 lines of code, and didn't execute the last 2. I am sure I didn't load the img as I didn't even put it on the phone. The rooting file says G2 instead of G3. Would that be the issue?
acefr said:
Not a problem. I understand the more detail I give, the higher chance there is a solution. I appreciate your effort in trying to solve it.
1. the phone was originally in factory new state. No custom recovery, no root, stock 12c rom.
2. I used the following method to root, and it appeared ok as the phone was able to reboot and granted SU when I did step 2. It was late night and my mind was not clear when I did step 2. I wonder why I didn't see the Lollipop in the title.
http://forum.xda-developers.com/android/help/lg-tribute-development-t2953342/page38#376
I will try the volume down+power tonight and report back. Again thanks for your input. The rooting method is a suspect too, as it says G2 in the posting. I was directed there from a G3 posting.
Click to expand...
Click to collapse
install both of these drivers then try the tot flash tool again.
https://www.mediafire.com/?q1blsp6151rcmf9
https://www.mediafire.com/?x22q33votbv086d
---------- Post added at 07:32 PM ---------- Previous post was at 07:30 PM ----------
acefr said:
Yes, I gained root before trying to install twrp. I stopped after the first 2 lines of code, and didn't execute the last 2. I am sure I didn't load the img as I didn't even put it on the phone. The rooting file says G2 instead of G3. Would that be the issue?
Click to expand...
Click to collapse
no, the rooting is fine, i used that the other day, i thought for a second i misunderstood and you dd the boot too. but no, thats good.
---------- Post added at 07:36 PM ---------- Previous post was at 07:32 PM ----------
acefr said:
Yes, I gained root before trying to install twrp. I stopped after the first 2 lines of code, and didn't execute the last 2. I am sure I didn't load the img as I didn't even put it on the phone. The rooting file says G2 instead of G3. Would that be the issue?
Click to expand...
Click to collapse
btw, did you try this i suggested earlier?
remove the battery, sim card, and sdcard.
hold the vol down and power, and put the battery back in, and see if anything happens
Click to expand...
Click to collapse
bweN diorD said:
install both of these drivers then try the tot flash tool again.
---------- Post added at 07:32 PM ---------- Previous post was at 07:30 PM ----------
no, the rooting is fine, i used that the other day, i thought for a second i misunderstood and you dd the boot too. but no, thats good.
Click to expand...
Click to collapse
Thanks. Will give it a try tonight. The phone is at home. I will vol down and power first. If not working, then TOT flash.
These installation programs are for the USB drivers for the phone, right?
acefr said:
Thanks. Will give it a try tonight. The phone is at home. I will vol down and power first. If not working, then TOT flash.
These installation programs are for the USB drivers for the phone, right?
Click to expand...
Click to collapse
yes, one is the latest lg driver, and the other is an alternate lg driver. i always install both to avoid connection issues.
Actually
I understand exactly where he's coming from because i was rooted on stock lollipop and also got the message about insufficient storage and what i did was i went to the google play store look for the kitkat sd fix it don't matter just fine and it said the patch was applied so i thought everything was fine i was also on stock recovery because how to flash the custom recovery just confused the hell outta me. So what i ended up doing was trying to backup titanium and i use the imei backup because i just had the issue where i got the boot signature verify screen and i called verizon and got a replacement sent out to me. Here is the problem now, after i did all that, i had gotten worried because my battery was dying but here's where i get confused my phone will not turn on a tray the KDZ method and it tells me the phone does not have enough battery life the only time i will see any image on my phone is when the battery is out and i plug the phone into my computer so what i'm thinking is the battery is just shot... which is highly possible and unfortunately verizon does not have any to send me so i ordered one of amazon and hopefully it'll be here on the 16th and if that's the case that means we have all those days to figure out if this is a brick which i pray to god it better not because i didn't have my phone on last week because of the boot signature verify and then i have the refurbished one all of 3 days before this crap happened. I do feel a vibrate when i plug the phone in with the battery and my phone is recognized somewhat by my computer it only loads the com port and modem. But like i said every time i try to use the android recovery tool that came with the verizon software it tells me my battery is too low i also should mention that i tried the tot method and it failed as well. One other thing i'm going to mention is that i also tried reading the information with the kdz method and it said imei null and pid null just don't worry about it i was like um ya thats not good.
---------- Post added at 11:56 PM ---------- Previous post was at 11:47 PM ----------
I understand exactly where he's coming from because i was rooted on stock lollipop and also got the message about insufficient storage and what i did was i went to the google play store look for the kitkat sd fix it don't matter just fine and it said the patch was applied so i thought everything was fine i was also on stock recovery because how to flash the custom recovery just confused the hell outta me. So what i ended up doing was trying to backup titanium and i use the imei backup because i just had the issue where i got the boot signature verify screen and i called verizon and got a replacement sent out to me. Here is the problem now, after i did all that, i had gotten worried because my battery was dying but here's where i get confused my phone will not turn on a tray the KDZ method and it tells me the phone does not have enough battery life the only time i will see any image on my phone is when the battery is out and i plug the phone into my computer so what i'm thinking is the battery is just shot... which is highly possible and unfortunately verizon does not have any to send me so i ordered one of amazon and hopefully it'll be here on the 16th and if that's the case that means we have all those days to figure out if this is a brick which i pray to god it better not because i didn't have my phone on last week because of the boot signature verify and then i have the refurbished one all of 3 days before this crap happened. I do feel a vibrate when i plug the phone in with the battery and my phone is recognized somewhat by my computer it only loads the com port and modem. But like i said every time i try to use the android recovery tool that came with the verizon software it tells me my battery is too low i also should mention that i tried the tot method and it failed as well. One other thing i'm going to mention is that i also tried reading the information with the kdz method and it said imei null and pid null just don't worry about it i was like um ya thats not good.
***Edit**** I just tried the suggestion of removing everything and vol down and power. shorter vibration than usual but still nothing.
soateufel said:
I understand exactly where he's coming from because i was rooted on stock lollipop and also got the message about insufficient storage and what i did was i went to the google play store look for the kitkat sd fix it don't matter just fine and it said the patch was applied so i thought everything was fine i was also on stock recovery because how to flash the custom recovery just confused the hell outta me. So what i ended up doing was trying to backup titanium and i use the imei backup because i just had the issue where i got the boot signature verify screen and i called verizon and got a replacement sent out to me. Here is the problem now, after i did all that, i had gotten worried because my battery was dying but here's where i get confused my phone will not turn on a tray the KDZ method and it tells me the phone does not have enough battery life the only time i will see any image on my phone is when the battery is out and i plug the phone into my computer so what i'm thinking is the battery is just shot... which is highly possible and unfortunately verizon does not have any to send me so i ordered one of amazon and hopefully it'll be here on the 16th and if that's the case that means we have all those days to figure out if this is a brick which i pray to god it better not because i didn't have my phone on last week because of the boot signature verify and then i have the refurbished one all of 3 days before this crap happened. I do feel a vibrate when i plug the phone in with the battery and my phone is recognized somewhat by my computer it only loads the com port and modem. But like i said every time i try to use the android recovery tool that came with the verizon software it tells me my battery is too low i also should mention that i tried the tot method and it failed as well. One other thing i'm going to mention is that i also tried reading the information with the kdz method and it said imei null and pid null just don't worry about it i was like um ya thats not good.
Click to expand...
Click to collapse
when you zero out a partition using the dd method through terminal or adb, it is absolutely normal to say out of space or whatever.
any sd fix you applied was unnecessary and possibly caused the problem you have.
yes, the imie being 000000 is not good, but i dont believe it will keep you from using stock recovery tools, and is very fixable.
okay. so im gonna try the tot method. I installed both drivers and plugged in my phone and the phone driver just installed so ill let you know what happens.
bweN diorD said:
when you zero out a partition using the dd method through terminal or adb, it is absolutely normal to say out of space or whatever.
any sd fix you applied was unnecessary and possibly caused the problem you have.
yes, the imie being 000000 is not good, but i dont believe it will keep you from using stock recovery tools, and is very fixable.
Click to expand...
Click to collapse
ya no dice... trying to kdz right now with the most recent drivers.
bweN diorD said:
yes, one is the latest lg driver, and the other is an alternate lg driver. i always install both to avoid connection issues.
Click to expand...
Click to collapse
"vol down and power" did nothing. The phone screen is still black and it vibrated for a short period. I then proceed to use another computer with USB2.0 port. Installed your two sets of drivers. Plugged in the the phone, computer found three USB device, loaded first and third drivers, the middle one driver failed to load. It is a Phone Modem. Then use the TOT flash, same thing, failed right before the flash started. However, this time I noticed there is an error message saying "Model Information Check Failed". See the attached pictures.
Maybe when I unlocked band 3 and 7, the Verizon Hidden Menu somehow changed permission of the NV value?
acefr said:
"vol down and power" did nothing. The phone screen is still black and it vibrated for a short period. I then proceed to use another computer with USB2.0 port. Installed your two sets of drivers. Plugged in the the phone, computer found three USB device, loaded first and third drivers, the middle one driver failed to load. It is a Phone Modem. Then use the TOT flash, same thing, failed right before the flash started. However, this time I noticed there is an error message saying "Model Information Check Failed". See the attached pictures.
Maybe when I unlocked band 3 and 7, the Verizon Hidden Menu somehow changed permission of the NV value?
Click to expand...
Click to collapse
Tbh, I don't know what else to tell you to try, sorry.
I Have the same problem except
When I turn on the phone normally I get the lg logo then the notification light blinks I can seem to get the drivers working like recovery mode and download but the download mode is not working right it says dowload mode then goes to a black screen I get it showing it in device manager in Windows 8.1 but its not lg driver it starts with a Q can't think of it right now it under ports I can't seem to flash anything when it boots I get the Security boot error and then after the lg logo nothing happens except the notification lights up and blinks I was upgrading from 10B to 12B then my phone rebooted and can't boot into the system any help please I need this phone working
Same issue here!! Just vibrates, black screen, no boot
asdecker said:
Same issue here!! Just vibrates, black screen, no boot
Click to expand...
Click to collapse
Did you get into the brick by enabling band 3 and 7? Or what did you do prior to bricking it? Maybe we can figure out what is causing this together.
mine happened when i used lucky patcher to odex my system apps to make more space
Mine was when I ran the scripts to fix download mode. I'm stuck for sure. Can't get it to do anything
asdecker said:
Mine was when I ran the scripts to fix download mode. I'm stuck for sure. Can't get it to do anything
Click to expand...
Click to collapse
When you and soateufel tried the TOT flash, which step did you encounter issue? Did you get the same Model Information Check Failed warning like in my picture at post #13?