Related
did the flash_image recovery /sdcard/cm-recovery-1.2.img part then my now my phone freezes every time i hit hold home and power does this mean i cant do updates or anything anymore
Did you thoroughly read before doing this? No issues here at all
Just reflash the recovery...
A frozen recovery is really really no brick.
g1201 said:
did the flash_image recovery /sdcard/cm-recovery-1.2.img part then my now my phone freezes every time i hit hold home and power does this mean i cant do updates or anything anymore
Click to expand...
Click to collapse
quickest fix, setup your system for ADB (if you haven't already). once done, copy cm-recovery-1.2.img to the root of your C:\, reboot your system to fastboot, run cmd prompt and type this:
Code:
PROMPT>fastboot flash recovery c:\cm-recovery-1.2.img
and reboot your phone
OP, would you mind re-naming this thread and not throwing the word "brick" around in such a cavalier manner?
op please read me
Ok, first you flashed the spl before you knew how to do it, so if you are truly bricked you did it not the spl, guns don't kill people, people killpeople with guns, see the metaphor?
But I think u should change the post title to: I jumped into the deep end before I learned to swim and now my phone is pooched, like somebody said don't bricked is a unrecoverable condition, and when you are flashing the spl,bootloader or recovery, you are messing with your failsafe, that you need to recover from a bad OS flash, so yes it is possible to brick your phone if you don't get a good flash, which is why all newcombers should take this story as a cautionary story, if you are new to writing flashes or just learning to "hack" htc devices, stick to OS and radio flashes only cause you always have your failsafe(bootloader or whatever u want to call it) to get things going again.
I've been "hacking"(4 lack of a better term) my phones and pda's for years, had my palm IIIx connected to the net wirelessly via a moto startac on sprints cdma in 1999 and I always read and reread everything I can find before I muck about with anything other than OS & Radio updates before I jump, look b4 u leap.
Even tho I'm guilty of flaming a bit, somebody should close this thread, if he is bricked there are threads for that already
Bhang
If you see any signs of life at all, it's not bricked
People who think they might have bricked thier phones may still be looking at this thread. If you get anything out of your phone at all, it's not bricked.
The last resort and fixall, afaik, is copy DREAIMG.nbh to your formatted to FAT32 sdcard.
Then go into bootloader mode by (from power off) holding down the camera key (until you're there) and powering up with the red power button. The nbh file should load automatically. Wait for this to finish, or you will brick your phone, likely.
One thing that's kind of confusing to newbies (anyone whos been avidly at this for less than a couple of months) is that there are three modes for your phone:
1. Bootloader (powering up with camera button held)
it runs/loads nbh files
2. Recovery (powering up with home button held)
it runs/loads update.zip files
3. The OS (just powering up)
I've only run img files from Telnet and Terminal Emulator (or the SDK adb.exe on my PC, but I don't mind the small keyboard)
If you have either Bootloader OR Recovery modes intact, you can recover the other, and the OS with either (the methods are different from each, though).
To many this will sound so insanely basic it shouldn't be posted. From what I've experienced on the WinMo fora, it will need to be posted over and over and over until someone stickies it so it can't be missed.
Please feel free to correct me on any of these points. HTH.
Denkai said:
quickest fix, setup your system for ADB (if you haven't already). once done, copy cm-recovery-1.2.img to the root of your C:\, reboot your system to fastboot, run cmd prompt and type this:
Code:
PROMPT>fastboot flash recovery c:\cm-recovery-1.2.img
and reboot your phone
Click to expand...
Click to collapse
thanx man im goin to do it now
Oh my god its all my fault!
cyanogen said:
Oh my god its all my fault!
Click to expand...
Click to collapse
naw it aint ya fault i was jus so mad last nite but im not blaming you
i have 2 quest.
1. can u help me get it back 2 normal
2. how can i change this title
you can also re-flash the recovery rom through terminal.
that way you don't have to run into getting 'stuck' by pressing home + power button.
g1201 said:
naw it aint ya fault i was jus so mad last nite but im not blaming you
i have 2 quest.
1. can u help me get it back 2 normal
2. how can i change this title
Click to expand...
Click to collapse
edit your first post, go advance, edit....
mrcrs said:
you can also re-flash the recovery rom through terminal.
that way you don't have to run into getting 'stuck' by pressing home + power button.
Click to expand...
Click to collapse
thats the 1st thing i tried
the thing is when i 1st did it it went threw i got the lil # symbol so i thought every thing was good but i power off and pressed home and power thats when i got stuck
g1201 said:
thats the 1st thing i tried
the thing is when i 1st did it it went threw i got the lil # symbol so i thought every thing was good but i power off and pressed home and power thats when i got stuck
Click to expand...
Click to collapse
what i would suggest is after flashing the next command you input is: reboot
instead of manually powering it down.
mrcrs said:
what i would suggest is after flashing the next command you input is: reboot
instead of manually powering it down.
Click to expand...
Click to collapse
ok im goin 2 try this bcuz the other 1 is not working 4 me
nope its not working i get not permitted
cyanogen said:
Oh my god its all my fault!
Click to expand...
Click to collapse
Of course it is your fault. You are a celebrity now.
g1201 said:
ok im goin 2 try this bcuz the other 1 is not working 4 me
nope its not working i get not permitted
Click to expand...
Click to collapse
how about.. download the file again.. rename it recovery.img and run those same commands
flash_image recovery /sdcard/recovery.img
sounds dumb.. i know..
Cyanogen is a great Dev!
It worked perfect for me as well and I am a rookie
g1201 said:
ok im goin 2 try this bcuz the other 1 is not working 4 me
nope its not working i get not permitted
Click to expand...
Click to collapse
you can not just type
Code:
$reboot
in the terminal. you have to
Code:
$su
#reboot
you have to have SuperUser privileges to reboot.
cyanogen said:
Oh my god its all my fault!
Click to expand...
Click to collapse
It's your God damned fault I <3 my phone so much. Arse.
Is there a file in the android system that, sort of like an autoexec.bat, lists what to do on startup? For example forcing the system into recovery or download on power on?
I flashed the latest Vibrant firmware and did so with the option to repartition, which Im now finding out was not the right way to flash this one.
Long story short, it didnt contain the dbdata directory information and now, I am unable to boot and unable to get to download. I still have ADB access, it just isnt responding to ADB reboot download, it just comes right back up booting into recovery to flash the last stage of odin before it starts up.
Is there a way to force the phone back into download mode or force it to stop rebooting into recovery?
Pull battery out and USB to use the hardware buttons to manually get into download mode?
P.S. wrong forum
Aren't there some apps that can do that? I do it manually but like you said its not working for you, p.s im downloading that firmware
Sent from my SGH-T959 using XDA App
iwillkillyou said:
Aren't there some apps that can do that? I do it manually but like you said its not working for you, p.s im downloading that firmware
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
OP said that he isn't able to boot so I believe he's stuck on the loadup to Android.
zephiK said:
Pull battery out and USB to use the hardware buttons to manually get into download mode?
P.S. wrong forum
Click to expand...
Click to collapse
Manual buttons arent seemingly working, so far ive tried every conceivable combination of vol up down and power, even if all I do is plug the phone in Im back in recovery before the battery turns green.
(ps. I know, but I had a billion percent better chance not getting a mouthbreather response, despite the definite chance of flame posts lol)
Viralblack said:
Manual buttons arent seemingly working, so far ive tried every conceivable combination of vol up down and power, even if all I do is plug the phone in Im back in recovery before the battery turns green.
(ps. I know, but I had a billion percent better chance not getting a mouthbreather response, despite the definite chance of flame posts lol)
Click to expand...
Click to collapse
Try every step here: http://forum.xda-developers.com/showthread.php?t=771247
Have you successfully gotten into Download mode with hardware buttons before? Or are you one of those vibrants with "locked download?"
I have a feeling mines locked, Ive never used the buttons to successfully get into download mode, just adb reboot download
EDIT: Tried the posts suggestions, problem is second I plug in the USB and the battery pops up it goes right to recovery. Even if im holding the buttons before hand.
Viralblack said:
I have a feeling mines locked, Ive never used the buttons to successfully get into download mode, just adb reboot download
EDIT: Tried the posts suggestions, problem is second I plug in the USB and the battery pops up it goes right to recovery. Even if im holding the buttons before hand.
Click to expand...
Click to collapse
x_x don't know what to tell you then. With locked hardware, you have to be really careful because if something goes wrong you cant manually get back in there. Do you have Clockwork Recovery? try restoring to a previous nandroid backup.
zephiK said:
x_x don't know what to tell you then. With locked hardware, you have to be really careful because if something goes wrong you cant manually get back in there. Do you have Clockwork Recovery? try restoring to a previous nandroid backup.
Click to expand...
Click to collapse
I was working with that a bit, but it just kept getting to datadata and being unable to wipe or flash to it due to the odin botch. I tried wiping it clean and it just wouldnt let me do that to reflash.
So now im stuck at the samsung recovery screen without the ability to get into clockwork or flash lol
This smells like 130 bucks for a new phone I think... brick number two >.>
Viralblack said:
I was working with that a bit, but it just kept getting to datadata and being unable to wipe or flash to it due to the odin botch. I tried wiping it clean and it just wouldnt let me do that to reflash.
So now im stuck at the samsung recovery screen without the ability to get into clockwork or flash lol
This smells like 130 bucks for a new phone I think... brick number two >.>
Click to expand...
Click to collapse
Why did you change update.zip? Update.zip should always lead to Clockwork :|
zephiK said:
Why did you change update.zip? Update.zip should always lead to Clockwork :|
Click to expand...
Click to collapse
I didnt! But when I was formatting and it failed to reapply the nandroid completely cause of the section it couldnt mount, now when I hit reinstall packages it just reboots. Same with shell, it just yells at me and tells me to die in a fire.
if you didnt figure this out, the way to fix it is to first flash WITH ODIN the original JVD firmware and check repartition, then flash the new one IN ODIN without the repartition box checked.
first update includes the dbdata that the phone is looking for.
Yeah, I figured it out now, but Odin is seriously the devil if your phone doesnt have the hardware buttons enabled.
Now heres a question, if I can still get into stock recovery... is there a way to like, you know, recover using the stock system? lol
BUT THE GOOD NEWS IS that Tmo is letting me warranty out my phone for free, shipping me a new one, and gave me a loner while I wait.
TMo for the win.
Viralblack said:
BUT THE GOOD NEWS IS that Tmo is letting me warranty out my phone for free, shipping me a new one, and gave me a loner while I wait.
TMo for the win.
Click to expand...
Click to collapse
lol looks like you and I are in the same boat man. Hardware lock FTMFL. I have never been able to get into download mode, or recovery mode with the hardware keys, only with adb reboot recovery/download and terminal emulator app with SU privs. I wish there was a jumper we could reset to unlock it haha that'd be the s*# son. Good old pentium 133 in the palm of the hands, but no . Atleast they are taking care of the people who don't do things properly.
I did the same thing and ended up with the same problem, but i was able to get in into download mode. When i would plug it in it would try to boot into recovery after the battery screen i would use the keys to make it boot to download mode instead of recovery, it was a *****, but i got it, though idk if there is another way for people with locked down phones.
Need help.
My optimus 2x seem to be bricked.
nothing shown at the screen. (just blank)
i can't enter the cwm.
smartflash also cannot detect my phone.
I try to use nvflash but it stuck at "waiting for bootloader to initialize"
anything i can do to revive my phone ?
or is it totally bricked ?
Hi,
Congratz for being the first person I ever read on o2x thread whom actually 'succesfully' bricked his phone. I've been here since o2x thread was born..alot of ppl use the term 'bricked' loosely but hasn't actually really bricked their phones.
If you lost ADB, Fastboot, unable to Nvflash/Smartflash... your phone is, sad to say, gone.
Anyway, I really hope you can share what you did to eventually get into this state, atleast you can help others to prevent bricking their o2x.
Thanks.
Well congratz, now move to something that is properly supported
Sent from my Optimus 2X using XDA
Haha.
can I get medal for this "achievement" ?
I bought it as faulty phone around usd 16. so I don't know what happen to it.
Ouh...usd16.. pretty useful for spare parts.
If you bought it for 16 dollars then I would advise you to sell the phone for spare parts. Even the glass costs 20 or more dollars.
Sent from my Optimus 2X using XDA
hmmmm, dudes, idk if im right buuuuuuuuuut... happened to me, i thought it was completelt dead, when after all i found out that my pc didnt recognise my lg o2x as an apx platform so it would always fail, sooooo, i did it on my sisters pc which never had lg drivers and i resurected my phone id advise to try it...
---------- Post added at 11:38 PM ---------- Previous post was at 11:35 PM ----------
ohhh, long story short and translated, if you have ever installed lg drivers on your pc, forget about it being recognised as an apx platform, even if you uninstall all lg software
1.From PC,manually place Stock LG Rom(V20Q.zip or [?]) on Your SD card then reinsert in phone.
2.Don't connect phone to PC or power (AC)
3.pull the battery out and reinsert it( now connect power (AC)
Hold the Volume Down button (keep pressed!!) then press and hold the Power button until the device turns on and you see the recovery menu
4.then proceed as you normally would meaning install .zip from SD card
Hope it helps
-JAZZMAN- said:
1.From PC,manually place Stock LG Rom(V20Q.zip or [?]) on Your SD card then reinsert in phone.
2. pull the battery out and reinsert it
Hold the Volume Down button
(keep pressed!!) then press and hold the Power down button until the device turns on and you see the recovery menu
3.then proceed as you normally would meaning install .zip from SD card
Hope it helps
Click to expand...
Click to collapse
dude O_O
he said the phone wont even load recovery O_O
skylinegt77 said:
dude O_O
he said the phone wont even load recovery O_O
Click to expand...
Click to collapse
Yes,I read that, But neither would mine after using ext3 converter without backup!
So after eating a big bowl of "BOOTLOOPS" I utilized the phones hard reset mode thinking It would lead to a factory reset but instead got the CWM recovery menu
after which I flashed and Voila 0_0
Also "DUDE" at least I'm trying to offer help instead of joking about such a serious concern...I guess... well only maybe when it's your phone and you have no answers<---this looks better
-JAZZMAN- said:
Yes,I read that, But neither would mine after using ext3 converter without backup!
So after eating a big bowl of "BOOTLOOPS" I utilized the phones hard reset mode thinking It would lead to a factory reset but instead got the CWM recovery menu
after which I flashed and Voila 0_0
Also "DUDE" at least I'm trying to offer help instead of joking about such a serious concern...I guess... well only maybe when it's your phone and you have no answers<---this looks better
Click to expand...
Click to collapse
You should really read again OP, it can't load bootloader.. So it can't boot to anything as bootloader is the essential part of the phone that loads after either recovery partition, or /boot Android one.
aris.syah said:
Need help.
My optimus 2x seem to be bricked.
nothing shown at the screen. (just blank)
i can't enter the cwm.
smartflash also cannot detect my phone.
I try to use nvflash but it stuck at "waiting for bootloader to initialize"
anything i can do to revive my phone ?
or is it totally bricked ?
Click to expand...
Click to collapse
Just to check: are you sure to boot the phone in Apx mode? Battery off, volume up pressed, then plug AC ?
Striatum_bdr said:
You should really read again OP, it can't load bootloader.. So it can't boot to anything as bootloader is the essential part of the phone that loads after either recovery partition, or /boot Android one.
Click to expand...
Click to collapse
Once again, I know and understand!!!!!
New to LG but not to how this process works so please stop with the "Dear N00B"
responses
I was only offering a suggestion that maybe wasn't tried even if proven futile!
also, for the most part, the days of "bricks" are pretty much over so there is always the slimmest possibility for hope. Wouldn't you exhaust every possibility....
Anyway,enough said on this I hope that he finds a solution
hi there,
N00B here...i had this kind of problem too...my laptop still recognize it as nvidia bootloader for mobile device AKA APX driver, but it never flashed in the nvflash way...
holding volume down and insert charging cord also give me nothing...
I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?
morell2 said:
I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?
Click to expand...
Click to collapse
Are you running stock, or did you root and customize?
Try plugging it in to a computer. A lot of us are finding better results when you do. You may end up having to do more. But just being connected to a computer has helped in the past. Quick fix before you start trying adb
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
Turn fastboot off in the power settings. I'm not sure if it has the fastboot setting, but that would be your problem.
kiewee3 said:
Turn fastboot off in the power settings. I'm not sure if it has the fastboot setting, but that would be your problem.
Click to expand...
Click to collapse
Err ..... it won't boot.
Does ADB work at this stage? Assuming you are rooted with CWM recovery, try
Code:
adb reboot recovery
Then from recovery, power it off completely. If fastboot is the problem, this should workaround it for you.
morell2 said:
I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?
Click to expand...
Click to collapse
It's karma because of your ridiculous signature.
Anywho. What did you do to the device? Attempt to root it? What happened between it working and not working?
khaytsus said:
It's karma because of your ridiculous signature.
Click to expand...
Click to collapse
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.
it now work but all data delete!
i do unroot and back to stock with rootkit 1.5.2 and after it is work!
wmoore said:
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.
Click to expand...
Click to collapse
Right. I can't figure out why people think others want to see large pictures of their crap.
just lou said:
Right. I can't figure out why people think others want to see large pictures of their crap.
Click to expand...
Click to collapse
Don't be mean. It's a visual aid to go with his query. Just in case we don't know what a Nexus 7 is (here in the Nexus 7 forum).
Rock-&-Roll-Hedgehog said:
Don't be mean. It's a visual aid to go with his query. Just in case we don't know what a Nexus 7 is (here in the Nexus 7 forum).
Click to expand...
Click to collapse
Oh. Now I see.
The nice thing is that Signatures can be disabled if you so choose, it'd just be nice if everyone kept a modestly sized signature.
wmoore said:
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.
Click to expand...
Click to collapse
XDA Signatures: The new Geociities
morell2 said:
it now work but all data delete!
i do unroot and back to stock with rootkit 1.5.2 and after it is work!
Click to expand...
Click to collapse
wat?
When you oem unlock, data is deleted, it tells you that. Otherwise, no idea what you're talking about.
Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7
evonc said:
Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7
Click to expand...
Click to collapse
That's interesting. I pretty much always make sure I'm plugged in before going into recovery / bootloader anyway (I'm paranoid about running out of battery mid-operation). I also pretty much always use adb reboot recovery, etc rather than hardware buttons.
evonc said:
Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7
Click to expand...
Click to collapse
wmoore said:
That's interesting. I pretty much always make sure I'm plugged in before going into recovery / bootloader anyway (I'm paranoid about running out of battery mid-operation). I also pretty much always use adb reboot recovery, etc rather than hardware buttons.
Click to expand...
Click to collapse
Not neccessarily true. I use an app called Quick boot. I can boot into recovery from it with Ease. Lets me set up Widgets/icon for recovery and I have one for reboot. No need for me to hook up to pc. Anywhere at anytime I can boot into recovery on my Nexus 7. I can also set one up for bootloader. If someone gets stuck on bootloader screen, the hardware button press for reboot works to get out of there.
They have a free version of the app and it works perfectly. Check it out. No need to run to a pc everytime you want to flash a rom or something. Battery is nothing to worry about. As long as you have 50%(really even less than that), you good to flash, wipe, or what ever.
demandarin said:
Not neccessarily true. I use an app called Quick boot.
Click to expand...
Click to collapse
Me too. Though I'm old school and still like to type commands rather than point and click. I'll be looking at Quick Boot but still go to PowerShell (which I always have open) and type adb reboot.:silly:
All the various apps that offer rebooting options will work as they are still executing the same terminal commands that you would've had to type in in order to reboot it.
The issue is that you would still require a working system partition in order to boot into recovery (stock/twrp/cwm) without any USB connection. Incase of a soft brick, you will need to connect to a computer in order to get into recovery so i would suggest people make sure they have one nearby when they're flashing stuff.
I just went through this. I boinked my setup and it was bootlooping. I couldn't get into CWM.
Just press and hold Power+VolDwn+VolUp until you get into the stock bootloader. Now plug in your USB to to a PC.
Stay in the bootloader. Mine actually kinda froze but it will unfreeze after a while. Don't select anything. Just stay there.
Now you can use Fastboot commands to reboot into CWM. ADB only works when the phone is on.
I think the command is "fastboot reboot recovery".
This will put you in CWM. You can also take this opportunity to reflash your recovery here too. I reflashed mine just to be on the safe side before rebooting it.
Sent from my Nexus 7 using xda premium
Hi. So I have a N6 which I appear to have bricked in some way. The phone was bootloader unlocked, rooted, everything. Then I got cute and just wiped everything off the phone, in my haste and stupidity. Now I seem unable to get it back to working status.
I am willing to pay someone to do this for me, as I need to know if it is salvageable, or just something to use for parts.
Any enterprising person is encouraged to respond. Thanks for the consideration.
More details please?
"Wiped everything off the phone"? How? In TWPR or Factory Reset? In ADB?
Does it boot at all? Does is partially boot and get stuck at Google screen or boot animation? Do you see any light at all coming from it?
Can you boot into Bootloader (Volume Up+Power) or Recovery (Volume Down + Power)?
Need just a bit more information before a proper diagnosis can be performed.
sounds like you did a "full" wipe, full as in everything. what you want to do is move a rom, a kernel, and supersu to your phone and flash it. you can do that via adb, or just with twrp.
johnplopez said:
Hi. So I have a N6 which I appear to have bricked in some way. The phone was bootloader unlocked, rooted, everything. Then I got cute and just wiped everything off the phone, in my haste and stupidity. Now I seem unable to get it back to working status.
I am willing to pay someone to do this for me, as I need to know if it is salvageable, or just something to use for parts.
Any enterprising person is encouraged to respond. Thanks for the consideration.
Click to expand...
Click to collapse
Just fastboot flash the latest factory image. There is a thread here that explains how to do it.
Woody said:
More details please?
"Wiped everything off the phone"? How? In TWPR or Factory Reset? In ADB?
Does it boot at all? Does is partially boot and get stuck at Google screen or boot animation? Do you see any light at all coming from it?
Can you boot into Bootloader (Volume Up+Power) or Recovery (Volume Down + Power)?
Need just a bit more information before a proper diagnosis can be performed.
Click to expand...
Click to collapse
Thanks for replying.....I believe I wiped the phone in TWRP. When I plug the phone in, I get the Google logo pop up, then disappear. That's all I get. I cannot boot into Bootloader or Recovery, to my knowledge.
johnplopez said:
Thanks for replying.....I believe I wiped the phone in TWRP. When I plug the phone in, I get the Google logo pop up, then disappear. That's all I get. I cannot boot into Bootloader or Recovery, to my knowledge.
Click to expand...
Click to collapse
Either flash a stock rom in fastboot or adb sideload a custom rom in TWRP, you`re not bricked. Did you format the sdcard or wipe the OS?
johnplopez said:
Thanks for replying.....I believe I wiped the phone in TWRP. When I plug the phone in, I get the Google logo pop up, then disappear. That's all I get. I cannot boot into Bootloader or Recovery, to my knowledge.
Click to expand...
Click to collapse
Just in case you don't know: to boot into bootloader hold volume down and power from an unpowered state (phone off). After that: fastboot stock or flash a custom ROM through TWRP.
gee2012 said:
Either flash a stock rom in fastboot or adb sideload a custom rom in TWRP, you`re not bricked. Did you format the sdcard or wipe the OS?
Click to expand...
Click to collapse
I believe I wiped the OS & everything from the phone.
You didn't wipe the bootloader.
Hold volume down, then hold power.
The phone will boot to fastboot mode and you can use fastboot to flash the factory image... Google supplies complete instructions on this on the factory image page, and there are tons of guides here....
Fastboot to stock and leave your phone stock until you learn at least the basics of what your doing.
BTW you had to do this to even get TWRP on your phone but you were lazy and used a toolkit instead of learning how to flash images to your phone, and as a result you have no idea how to fix anything
This is why we don't use toolkits kids.
scryan said:
You didn't wipe the bootloader.
Hold volume down, then hold power.
The phone will boot to fastboot mode and you can use fastboot to flash the factory image... Google supplies complete instructions on this on the factory image page, and there are tons of guides here....
Fastboot to stock and leave your phone stock until you learn at least the basics of what your doing.
BTW you had to do this to even get TWRP on your phone but you were lazy and used a toolkit instead of learning how to flash images to your phone, and as a result you have no idea how to fix anything
This is why we don't use toolkits kids.
Click to expand...
Click to collapse
I suppose thanks are in order. Admittedly, I messed up, and I did use a toolkit. But since lazy is a character trait and not necessarily an action, perhaps you can try and keep it positive. You don't know me, so don't characterize me. You can be helpful without beating your chest and calling people lazy. Happy Holidays!
johnplopez said:
I suppose thanks are in order. Admittedly, I messed up, and I did use a toolkit. But since lazy is a character trait and not necessarily an action, perhaps you can try and keep it positive. You don't know me, so don't characterize me. You can be helpful without beating your chest and calling people lazy. Happy Holidays!
Click to expand...
Click to collapse
I apologize for not offering free help up to your standards.
Problem Solved
With Woody's help, was able to download phone driver to my computer, after which I was able to use the toolkit again to download the 6.0.1 version of Marshmallow and flash it to my device. Thank goodness! Thanks Woody!
johnplopez said:
With Woody's help, was able to download phone driver to my computer, after which I was able to use the toolkit again to download the 6.0.1 version of Marshmallow and flash it to my device. Thank goodness! Thanks Woody!
Click to expand...
Click to collapse
Learn what you are doing and you wont end up in this problem again.
zelendel said:
Learn what you are doing and you wont end up in this problem again.
Click to expand...
Click to collapse
I think you can post that in response to any problem
spitswap said:
I think you can post that in response to any problem
Click to expand...
Click to collapse
Especially here, because he didn't even try to learn this time either, and used a toolkit instead.
Sent from my Nexus 6 running cyosp using Tapatalk
spitswap said:
I think you can post that in response to any problem
Click to expand...
Click to collapse
This is true. One should never mess with something when they dont know what they are doing. This is the major issue with toolkits. It makes people dumber.
Yes, I used the toolkit this time, but now that I am restored, really want to get into this, and I have downloaded the appropriate tools for doing this without a toolkit. Like I said to scryan, the tone here is pretty negative. I am really grateful for the help I was given. Have a good day everyone.
John, I have watched your thread with interest (catchy title... ) and I sort of agree that there is a certain negativity in some of the answers, particularly when it comes to toolkits. However, you didn't help your case with your comment "I suppose thanks are in order". Yes, they are. People here can be a bit prickly but everyone does try to help.
Good luck with learning more about manual updating. I've used Wugfresh's NRT many times with success, but it's actually very rewarding to type the commands and achieve the result on your own.
So, when do we get the money?
I want hard cold moolahhhhh