Related
Hello, everyone...
I had my Wing sitting on my desk for months - I went to go pick it up and it didnt work. When I plugged it in, the orange light blinked and went off... each time I plugged it in, that is what it would do.
Nothing I would do would get it to turn on - plugging it into computer, trying to do a hard reset, nothing.
So I figured I bricked my phone. Since I can get to the bootloader, I installed a new ROM - 4.26.(something) and nothing changed. I tried another ROM, 4.10.0002 and that didnt work either. It did successfully downgrade (per the bootloader), but it wount start up.
Each time I went to upgrade the phone, my computer wouldnt detect which version of ROM I had on it.. but it still went forward with the upgrade - and my phone responded great... but when powering on, wouldnt get past the TMOBILE start up. It just would turn itself off.
I dont have a memory card in it... and when I go to hard reset, it takes about a half a second, says complete.. and that is that (which leads me to believe it isnt working.. or there is nothing to delete!
Any thoughts on what I should do?
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
I then removed the battery, reinserted it, and tried booting into recovery mode. Nothing happened, it just stuck at the first splash screen.
So I removed the battery again, reinserted it, and tried booting into fastboot mode. Nothing happened, it just stuck at the first splash screen.
I repeated these steps a few times with the same result.
I tried booting it with the USB cable attached, the result was the same, and Windows showed the phone as an 'unrecognized device'.
At this point, I was nearly crying, my phone was a brick.
Then, for some reason I tried the following:
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image! Yay!
That's it. I didn't test it any more thoroughly for obvious reasons, I just reflashed the SPL and everything was back to normal.
I hope this helps someone in the future....
Very nice..
wow seriously, didnt expected that..
good job mate!
btw wat did u do to cause the brick?
Just read the very first line of his post...
marcdbl said:
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
[...]
Click to expand...
Click to collapse
mgear356 said:
btw wat did u do to cause the brick
Click to expand...
Click to collapse
As I said above, I had been flashing the SPL, and when I rebooted following the flash it was bricked (stuck at first splash screen).
It's weird, because once I managed to get back into fastboot, I simply flashed the same SPL again and it worked fine.
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
Never seen someone say the splash screen isn't coming up without blaming the hardware. I didn't think that flashing the wrong SPL would case the splash to not come up. I bricked my first phone by stupidly flashing the wrong SPL first before loading an OS. I thought the whole point of using the word 'brick' was when referring to the phone failing to enter 'fastboot' and 'recovery mode'. At that point, the phone would technically be a 'brick'. This has to be the first post I've seen with a possible fix but I could be wrong since I gave up on fixing that phone awhile ago.
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
bricking means you can't get to fastboot or recovery no matter what you do.
so he counts as bricking.
this might be a fix for the haykuro spl bricked users..
Well done if we have HTC G1 user with brick phone who want to try this methode and give feedback
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
No, You can still get to your splashscreen when the phone is bricked, If you cant turn on the phone then thats called the phone is dead not bricked. As stated already if you can't fastboot, or get to recovery then thats a brick.
Just tried it does not work and I was flash the death spl from haykuro,I am getting a new one but wanted to see if this works and I did not think it would which it didnt.
imfloflo said:
Well done if we have HTC G1 user with brick phone who want to try this methode and give feedback
Click to expand...
Click to collapse
Posted the fix on the android community forums. I have none person in mind, bricked it applying a spl, but he hasn't relied yet. Keep you informed if he does.
Did you reflash ROM after applying spl..? If you did and it still didn't boot then that should most likely be a brick. Can you boot into recovery right now and tell us your SPL version and radio?
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
Yes bricking your phone is when it wont even turn on! In the case of the sapphire when you hold power the led will flsh red quickly once then nothing.
On the blackstone you dont even get the pleasure of the led flash if your phone will turn on there is a way to get it fixed.
When ive been stuck on the bootscreen i have managed to revert using sappimg.nbh (which is 32b in my case) dunno where i got it from but i have it!
sappimg.zip (which is 32A) i got from Amon_RA's post and also have that, ive managed to revert back with both images after being stuck on "red screen of death"
A bit of a personal opinion here:
"Dead" is when the phone doesn't respond to anything, at all.
The charging light does not come on, the power button does nothing, and there is not so much as a flicker in the screen. Also, it is completely inaccessible for hardware debugging (JTAG, serial, USB or otherwise). This usually happens from a hardware problem, or doing something stupid like zero'ing the IPL.
Examples:
- My brother dropped his Nokia N75 in water. It's dead.
- I dropped my Cingular 8125 (HTC Wizard) on the ground. It doesn't power on any more, and plugging it into the charger does nothing. Voltmeter shows a charge running through some areas of the device's motherboard once disassembled. It's dead.
Solutions: Replace, recycle or sell for parts.
"Bricked" is when a purely software problem causes the device to no longer respond.
This may happen on many levels, but usually results in the OS not booting, or booting and being completely unusable (e.g. stopped with kernel panic at OS splash). It may light up and/or show a splash screen, but it fails to enter the bootloader or recovery menus. Its recoverability may vary, but will usually involve a debugging tool and a computer, and likely a copmlete wipe of everything on the device. Even if it's heavily bricked, if it can be recovered via JTAG or similar, it's not "dead".
Examples:
- HTC Dream only goes as far as splash screen, and freezes there. Does not respond to ADB. Does not enter recovery, or bootloader, however fastboot responds.
- HTC Dream shows blank screen, but lights up as if it were powering on. Fastboot does not respond. I connect my HTC ExtUSB Serial dongle to it though, and I'm able to get a response to some commands.
- Western Digital MyBook World Edition NAS powers on, and spins up hard drive, but does not go any farther than that. Front lights do not light up, and no hard disk activity is heard. Networking is not yet enabled. Hard drive can, however, manually be connected to a PC with SATA, and the firmware image re-written to its partitions.
- XBOX (the original) was softmodded, but the dashboard.xbe (the OS shell) was overwritten. It now just stays at the Microsoft logo.
- iPhone was recently jailbroken and SIM unlocked, then Apple pushed an update on me, and my iPhone is in a state where it doesn't enter DFU/Recovery, and when it boots, it says "Emergency calls only."
Solutions: Be very careful not to further brick the device, but use any methods available. Be sure to check documentations, search forums, and then ask questions if unsure. Make sure you finish every process you start.
After this, might just be hardware "damage" (like a power button not working right) or software "errors", like the home screen failing to load because of "Process com.google.android.gapps quit unexpectedly." These are usually relatively easy to fix, or have fixed.
Again, this is just an opinion.
Back on topic though, I seriously wouldn't have probably thought of using fastboot while it's stuck at the G1 screen, unless mine were bricked. Kudos to you, and I hope this works on some other bricked G1's out there (At least ones with the Engineering/Hard/DangerSPL, the stock SPL doesn't support fastboot as far as I know.)
bonesy said:
Yes bricking your phone is when it wont even turn on! In the case of the sapphire when you hold power the led will flsh red quickly once then nothing.
On the blackstone you dont even get the pleasure of the led flash if your phone will turn on there is a way to get it fixed.
When ive been stuck on the bootscreen i have managed to revert using sappimg.nbh (which is 32b in my case) dunno where i got it from but i have it!
sappimg.zip (which is 32A) i got from Amon_RA's post and also have that, ive managed to revert back with both images after being stuck on "red screen of death"
Click to expand...
Click to collapse
Won't agree with that, what you describe as a brick is a DEAD mobile. A brick is a useless piece which wont get into any state of recovery. The only thing i will agree with is that if it'll turn on there is a way to get it fixed that's why we even got the word unbricking which is done with many other pieces than Android mobiles.
Hope this will get us closer to a unbricking method which works on all the BRICKED pieces out there.
Good job dude!
Yes, my phone is back!
I bricked my G1 about 2 months ago pretty much the same way marcdbl did.
I gave up on it and sit it aside getting a new MT3G.
Sweet, now I got 2 phones to play with.
Thank You marcdbl
wow sweet news
fishman0919 said:
Yes, my phone is back!
I bricked my G1 about 2 months ago pretty much the same way marcdbl did.
I gave up on it and sit it aside getting a new MT3G.
Sweet, now I got 2 phones to play with.
Thank You marcdbl
Click to expand...
Click to collapse
Very glad to hear that your dead or bricked or whatever-you-may-call phone is back to LIVE!!!
So I think this solution works for some certain people. So i think rather than arguing on terminology, better spread this good trick to people who had dead/bricked/whatevery-you-may-call phone. IMHO
Thanks for the solution.
Best,
Thihaz
marcdbl said:
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
I then removed the battery, reinserted it, and tried booting into recovery mode. Nothing happened, it just stuck at the first splash screen.
So I removed the battery again, reinserted it, and tried booting into fastboot mode. Nothing happened, it just stuck at the first splash screen.
I repeated these steps a few times with the same result.
I tried booting it with the USB cable attached, the result was the same, and Windows showed the phone as an 'unrecognized device'.
At this point, I was nearly crying, my phone was a brick.
Then, for some reason I tried the following:
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image! Yay!
That's it. I didn't test it any more thoroughly for obvious reasons, I just reflashed the SPL and everything was back to normal.
I hope this helps someone in the future....
Click to expand...
Click to collapse
where were you 2 months ago dude? I paid 270€ to change the board on my magic
Good Job! Thanks for the info
Last year(late 2010, maybe mid November), I rooted my phone and flashed recovery with no problem s at all. Some time after that I added Apps2SD and that went smoothly with no problems for about a week. I purchased an 8 GB SD Card for more storage room and after I partitioned it and switched the cards my phone started acting up so i rebooted it. After that I was stuck in a boot loop, so i tried to flash it back to stock but it wouldn't take to it no matter how I tried, whether it be through recovery or SW Update. So then I tried Odin Multi loader(cant remember which version but at the time I made sure it was the one meant for the Intercept) after I flashed it with the Stock through Odin, the phone bricked. Now it will not turn on in any way(recovery or other) the only thing it does do is vibrate when I plug it in to a computer, and it will occasionally show battery life through the touch screen and keyboard buttons by lighting them, but as soon as the it is unplugged it is a brick. I see the little bit of functionality as a little bit of to be able to fix this phone whether through ADB or another function but I desperately need help with this. Can someone please help me fix this phone?
note: I currently have a Samsung Transform as my main phone so if the Intercept can't be helped then it's not that big of a problem.
I have the same problem! Please help!
When you root a phone you put the rom, and recovery onto the sd card. changing sd cards disrupts this process. Put the old sd card in and tell me what happens.
The phone doesnt come on at all
see if you can get it into download mode with the battery out.
Pull battery
connect to computer with usb
vol down + camera + end
If you get into download mode this way flash the stock.tar using SWUpdater.
Nope, it doesnt work, thx though
Ok I've got the same problem with my intercept as well, So i just like to add (maybe its just me) that when i plug my phone to the computer the phone shows that its still functions right (without the screen on), I'm able to make calls, and receive them as well (with the touch of the answer button) but just the screen doesn't turn on, AT ALL!, so KJON i don't know if your having the same problem as me but I'm just a noob and i wouldn't know what to do. But there's some ammo if you need it.
I HAVE THE SAME PROBLEM! i dont even know where /sdcard/sdx/zip/ is!
My phone is also a samsung transform and not and intercept and whenever i press vol down+ Power, only the function buttons at the bottoms light up but not the screen
i am a noob.
help?
noooooob here...i didnt wanna start another thread since i have this same problem, so i hope someone reads this..
couple days ago i bricked my sprint intercept i was using SWu and forgot to take the Binary files for the Moment out so now i cant get my phone to DL mode, ive been searching since saturday night and have tried every Button combo posted and nothing, my phone will not turn on and ofcourse it isnt recognized by my pc BUT, ive noticed that only when its plugged in to the computer after trying to power it up several times it´ll vibrate then the 4 touch buttons will react to either the call or end button, also it makes the low battery sound and if i press the camera button it makes the volume sound but i CANT get to download mode, can i bring my phone back or is it done with? help please! and thanks in advance...
well, i would say boot into rrecovery by making the phone off either power button, or remove and replace battery.
next, you will need to press and hold in order: power/end call, call, and volume down.. this should boot recovery mode.
lastly, use the red scroll device to go to reset facory defaults or factory recovery, use common sense while looking. select with clicking and use arrow back button to go back to recovery main, then reboot to system. easy as pie.
Have you tried ODIN or ADB?
I have flashed the Intercept numerous times, soft bricked more than once, I was always able to recover using either the stock bootloader, CWM recovery, or flashing the ROM/Kernel directly using ODIN or ADB.
If you are still having these issues drop me a line and I'll gather some links together that should get you back up and running.
If the phone will not boot at all, even with a charged battery, I would definately try contacting Virgin Mobile and escalating the issue. I've had plenty of luck replacing devices claiming that the device just dropped dead without notice. They are usually good about sending out a replacement phone, and on rare occasions even giving you an upgraded unit if they are out of stock.
Good luck!
Did you use Odin or the swupdater?
Bug difference. Sounds like there's a missing boot loader.
Sent from my SPH-L710 using xda app-developers app
Hi, did you guys fix your bricked phones? Today I have bricked my Samsung transform (bad flash went with SW upgrade.
Only vibrates sometimes and the buttons flash a little, but no boot at all. Is there any chance to fix it? even with Jtag?
regards
sorry to bother you all. i bricked my device and it's only a few hours old. I rooted it using the io root method. that was painless.
anyway, it didn't brick then. i got a notification from verizon for the 4.4.2 update so I clicked download update it never installed and that's when the bricking started. Anytime I connect it to the computer it opens up like 40 disks and it says cannot be used unless it's formatted so I have to spend a while canceling those out. when I restart the phone it says the lg logo then the screen goes black . im stuck. i've been trying for hours. if i get the phone back i won't root it or do anything. ill deal with the bloatware, whatever. i've tried a lot of different things but to no avail. any help is appreciated. thank you for your time...and wont go into download mode....help please anyone....
i have no recovery installed....every time i try to cut the phone off it vibrates screen goes off and on showing the lg logo very quickly then goes black but remains on until battery drains
Im in the same boat
xdavelope said:
sorry to bother you all. i bricked my device and it's only a few hours old. I rooted it using the io root method. that was painless.
anyway, it didn't brick then. i got a notification from verizon for the 4.4.2 update so I clicked download update it never installed and that's when the bricking started. Anytime I connect it to the computer it opens up like 40 disks and it says cannot be used unless it's formatted so I have to spend a while canceling those out. when I restart the phone it says the lg logo then the screen goes black . im stuck. i've been trying for hours. if i get the phone back i won't root it or do anything. ill deal with the bloatware, whatever. i've tried a lot of different things but to no avail. any help is appreciated. thank you for your time...and wont go into download mode....help please anyone....
i have no recovery installed....every time i try to cut the phone off it vibrates screen goes off and on showing the lg logo very quickly then goes black but remains on until battery drains
Click to expand...
Click to collapse
Did just like you with OTA today and now bricked. Guess I will have to call Verizon and see what they can do.
xdavelope said:
sorry to bother you all. i bricked my device and it's only a few hours old. I rooted it using the io root method. that was painless.
anyway, it didn't brick then. i got a notification from verizon for the 4.4.2 update so I clicked download update it never installed and that's when the bricking started. Anytime I connect it to the computer it opens up like 40 disks and it says cannot be used unless it's formatted so I have to spend a while canceling those out. when I restart the phone it says the lg logo then the screen goes black . im stuck. i've been trying for hours. if i get the phone back i won't root it or do anything. ill deal with the bloatware, whatever. i've tried a lot of different things but to no avail. any help is appreciated. thank you for your time...and wont go into download mode....help please anyone....
i have no recovery installed....every time i try to cut the phone off it vibrates screen goes off and on showing the lg logo very quickly then goes black but remains on until battery drains
Click to expand...
Click to collapse
BAYOUREBEL said:
Did just like you with OTA today and now bricked. Guess I will have to call Verizon and see what they can do.
Click to expand...
Click to collapse
DId you not try and go back to stock?...
http://forum.xda-developers.com/showthread.php?t=2432476
xdavelope said:
sorry to bother you all. i bricked my device and it's only a few hours old. I rooted it using the io root method. that was painless.
anyway, it didn't brick then. i got a notification from verizon for the 4.4.2 update so I clicked download update it never installed and that's when the bricking started. Anytime I connect it to the computer it opens up like 40 disks and it says cannot be used unless it's formatted so I have to spend a while canceling those out. when I restart the phone it says the lg logo then the screen goes black . im stuck. i've been trying for hours. if i get the phone back i won't root it or do anything. ill deal with the bloatware, whatever. i've tried a lot of different things but to no avail. any help is appreciated. thank you for your time...and wont go into download mode....help please anyone....
i have no recovery installed....every time i try to cut the phone off it vibrates screen goes off and on showing the lg logo very quickly then goes black but remains on until battery drains
Click to expand...
Click to collapse
If you can't boot into stock recovery (vol down + power key) and can't get into download mode (this is where they detect root once FW update shows up and the bottom left corner says Bootloader: ROOTED) then you can rest assure as long as you are under warranty, send it in to LG directly.
Do not send it to Verizon as you may incur charges for replacement. There's insurance from Verizon, but the real "replace with no charge" warranty is sending it to LG directly. Make an account on their website, register your G2, and make a Repair request by online chat or phone.
I just got my T-mobile G2 back after 2 weeks with the same issues and while it took a while to get repaired, I didn't pay a penny and it works without T-Mobile ever knowing its different hardware (all they replace is the flash memory that is corrupted in the phone).
Only downside is that it came back with KitKat and unrooted which means I have to wait for a working root procedure for it unlike with JB (I'm not afraid to root it again since I know what messed it up before was custom recovery TWRP version 2.6.3.2 that doesn't support KitKat lol).
hyelton said:
DId you not try and go back to stock?...
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
He can't get into download mode which means no KDZ flashing.
MDA400 said:
If you can't boot into stock recovery (vol down + power key) and can't get into download mode (this is where they detect root once FW update shows up and the bottom left corner says Bootloader: ROOTED) then you can rest assure as long as you are under warranty, send it in to LG directly.
Do not send it to Verizon as you may incur charges for replacement. There's insurance from Verizon, but the real "replace with no charge" warranty is sending it to LG directly. Make an account on their website, register your G2, and make a Repair request by online chat or phone.
I just got my T-mobile G2 back after 2 weeks with the same issues and while it took a while to get repaired, I didn't pay a penny and it works without T-Mobile ever knowing its different hardware (all they replace is the flash memory that is corrupted in the phone).
Only downside is that it came back with KitKat and unrooted which means I have to wait for a working root procedure for it unlike with JB (I'm not afraid to root it again since I know what messed it up before was custom recovery TWRP version 2.6.3.2 that doesn't support KitKat lol).
He can't get into download mode which means no KDZ flashing.
Click to expand...
Click to collapse
Not getting into download mode is odd especially for just accepting a OTA update. Remember since they accepted the OTA its gonna take a special way of getting into download mode as the phone will be constantly on in boot loop. not all of the time but most of the time when people say they cant get into bootloader they have to keep trying due to the phone has to be "Turned off" OR rebooted at the same time of holding down the key combo.
hyelton said:
Not getting into download mode is odd especially for just accepting a OTA update. Remember since they accepted the OTA its gonna take a special way of getting into download mode as the phone will be constantly on in boot loop. not all of the time but most of the time when people say they cant get into bootloader they have to keep trying due to the phone has to be "Turned off" OR rebooted at the same time of holding down the key combo.
Click to expand...
Click to collapse
To get the phone to turn off, one has to reboot the phone (power key for 10 seconds) while holding volume up WITHOUT having the USB cable plugged in.
Recovery mode is a bit trickier by having to hold the power key for 10 seconds, then just as the phone reboots, hold PWR + VOL DWN and while holding VOL DWN, release PWR and press it again (gets to that factory reset screen where you press PWR 3 times).
Not trying to teach you this if you already know how, just stating it if the OP looks at this then he can try again with the above.
Also, Download mode is essentially the "bootloader" and it is locked meaning unless you have certified software (KDZ FW updater), you can't adb anything just in download mode unlike some LG phones that have emergency mode which is unlocked bootloader.
MDA400 said:
To get the phone to turn off, one has to reboot the phone (power key for 10 seconds) while holding volume up WITHOUT having the USB cable plugged in.
Recovery mode is a bit trickier by having to hold the power key for 10 seconds, then just as the phone reboots, hold PWR + VOL DWN and while holding VOL DWN, release PWR and press it again (gets to that factory reset screen where you press PWR 3 times).
Not trying to teach you this if you already know how, just stating it if the OP looks at this then he can try again with the above.
Also, Download mode is essentially the "bootloader" and it is locked meaning unless you have certified software (KDZ FW updater), you can't adb anything just in download mode unlike some LG phones that have emergency mode which is unlocked bootloader.
Click to expand...
Click to collapse
Yea I know the commands, The guide for going back to stock was created by me for the G2 haha, Hopefully the OP will see your post and try that
ive tried
ive tried factory reset "vol down & power"...its just goes black and stays the same
I'm having about the exact same problem. I rooted my phone a while back, I left it stock and just used some modules (xposed). When I noticed the update I of course was stupid enough to hit the update... My phone is doing the same as his. I can get to the factory reset screen but even if I go through there I get the same black screen (though backlit). I can't boot into download. I'm downloading the .tot needed for stock, but I'm not sure if that'll be a lot of good without download mode. I have everything on my phone backed up from when I rooted it (I'm missing a few pictures but nothing major.) Any and all help would be appreciated. I've got a bunch of precalc homework and Prom in a couple days so I'm willing to sacrifice sleep tonight. Thanks! (Made this account just for this, though I've used the site a bit before.)
xdavelope said:
ive tried factory reset "vol down & power"...its just goes black and stays the same
Click to expand...
Click to collapse
It's cuz you're not doing it correctly.
Yes, you're supposed to depress "vol down & power" but once you see LG logo, let go of both buttons and then immediately hold down only the "power" button.
After a few secs, a white factory reset screen will appear. Ignore the warning and press power button. I know, its kinda scary at first, but then phone will load into recovery.
I can get to the factory data reset screen but when i choose yes it just gives me the secure boot error. I am able to put my phone into download mode by pressing up volume and power when plugging to pc, but cant get pc to recognize it. I am sure I am missing something.
i am also bricked. i cant get into download mode or recovery. i have twrp installed, cant get to that either. i have tried every button combination and all i get is a black screen and vibrations, no lg logo. need help.
Dont
BAYOUREBEL said:
Did just like you with OTA today and now bricked. Guess I will have to call Verizon and see what they can do.
Click to expand...
Click to collapse
Call LG verizon will void your warranty
Has anyone made any progress or did all just send back to LG?
I am in similar shape, can get to the white factory reset screen - which does nothing once I accept.
I can also get into download mode, but the phone isn't recognized.
Wanted to confirm before I try to send it back that I can't fix myself.
Thanks!
Also, did anyone who was able to get back to the hard reset screen have luck sending to LG? Or did it have to be completely bricked?
Im also bricked. And there is no recovery mode. download mode is usable. but when i in twrp before brick i deleted efs because i have a back up after that recovery had corrupted and driver in the rom memory to talk to pc had also deleted with efs(i think). I have an idea to fix but im not sure
If I can change rom from mainboard and replace it other rom from other lg g2? Will it solve my and our problem??????
thanks to reply.
Hello, i have a blackberry Priv that is stuck on logo and just keeps on restarting and doesnt go to the main screen....how to solve this problem? CAn i solve it by flashing with autoloader
Also, i cant turn on the phone to main screen,
How do i know if it is version:
STV100-1,
STV100-2,
STV100-3,
STV100-4 OR
STV100-5
I downloaded autoloader for STV100-1 and installed drivers too. Now i put phone in fastboot mode by pressing power key and vol - key. I connect phone to pc and run autoloader but window appears and disappears. How to flash this phone and repair this phone....someone pls help
thanks
andrew21 said:
Hello, i have a blackberry Priv that is stuck on logo and just keeps on restarting and doesnt go to the main screen....how to solve this problem? CAn i solve it by flashing with autoloader
Also, i cant turn on the phone to main screen,
How do i know if it is version:
STV100-1,
STV100-2,
STV100-3,
STV100-4 OR
STV100-5
I downloaded autoloader for STV100-1 and installed drivers too. Now i put phone in fastboot mode by pressing power key and vol - key. I connect phone to pc and run autoloader but window appears and disappears. How to flash this phone and repair this phone....someone pls help
thanks
Click to expand...
Click to collapse
Hi,
If you don't know the model #, then don't flash...
I read that Hard Reset of the device is needed, by pressing and holding the volume up and down keys simultaneously for at least 10 seconds, when you reach the error screen
Charkatak said:
Hi,
If you don't know the model #, then don't flash...
I read that Hard Reset of the device is needed, by pressing and holding the volume up and down keys simultaneously for at least 10 seconds, when you reach the error screen
Click to expand...
Click to collapse
I tried to hard reset, enter bootloader mode, enter recovery mode but its all in vain. Moment phone goes to bootloader mode for enter into fastboot it restarts.
By pressing Volume up + Power it takes me to recovery mode there it shows error and again restarts.
Even its not getting connected to pc cause it restarts continuously and in this situation how can I know which model it is and how can I flash new version.
All this happened after Marshmallow update.
Please come up with some solution else this is just a paper weight.
I have the same issue, after Marshmellow update my Priv keep restarting and continuous doing that until the batTrey drain. The phone also heats up and can't find a solution. Tried all kind of reboots but nothing works.
Hoping for a solution before the phone dies completely.
Same issue since 2 days ago
Hello,
I also have the same issue with the PRIV. I spoke with BB Support. They told they will contact me by after 24 hours. I don't know if there won't be any valid warranty since it is an unlocked phone.
Have you find any solution for this?
Please someone help!!
this is because of a wrong flash, you need to use the autoloader appropiate for your unit, with device in fastboot mode run the autoloader, if you do not know your version download all available and flash them, if it is not valid for your unit it wont flash or it wont work, if you swap files to try to bypass and install mm on ll device like att it wont work neither, i have tested this and it works no matter if you swapped files from other autoloaders or not as long you use the correct one your device will be back to life
Same error here...
But if I try to enter fastboot mode (vol-), it reboots after 2-3 seconds...tried also 32 seconds of power on button....any idea?
Thank you,
Chuck26
nicromant said:
this is because of a wrong flash, you need to use the autoloader appropiate for your unit, with device in fastboot mode run the autoloader, if you do not know your version download all available and flash them, if it is not valid for your unit it wont flash or it wont work, if you swap files to try to bypass and install mm on ll device like att it wont work neither, i have tested this and it works no matter if you swapped files from other autoloaders or not as long you use the correct one your device will be back to life
Click to expand...
Click to collapse
Thanks for the tip,
I tried to flash it with one autoloader days ago. It just didn't succeed. The screen went black with unceasing blinking green light.
I kept the contact wit BB Support. They just washed their hands. They told me to go to the Rogers Store where I just bought the PRIV to ask them for a replacement. This is kind of impossible, since I live in Mexico and when the device was bought was on a trip to Vancouver. Yesterday I just plugged in my laptop the phone with the autoloader running hoping something happens. So I left it at home for several hours. When I came back, it was just as before, restarting over and over and over until fastboot menu. So I just gave another try to the autoloader, but it just happened again. Now it remains in black screen and with the green led light blinking. I tried several button combinations over and over just to get to the fastboot menu with no success.
I can't make it to bring up the loading screen and neither fastboot menu.
I guess it was because picking a wrong autoloader for flashing the PRIV. I downloaded another autoloader for trying.
Please help with this.
My PRIV is the STV100-3.
The first autoloader I tried is the Rogers Canada or Orange Slovakia – STV100-3 & STV100-4 - AAF057 Software Version
The second I want to try is the BlackBerry common SW for generic STV100-1, STV100-3 & STV100-4 devices - AAF518 Software Version
This is the link where I got them:
http ://ca.blackberry.com/content/blackberry-com/en_ca/support/smartphones/blackberry-PRIV/reload.html
Thanks in advance!!
nicromant said:
this is because of a wrong flash, you need to use the autoloader appropiate for your unit, with device in fastboot mode run the autoloader, if you do not know your version download all available and flash them, if it is not valid for your unit it wont flash or it wont work, if you swap files to try to bypass and install mm on ll device like att it wont work neither, i have tested this and it works no matter if you swapped files from other autoloaders or not as long you use the correct one your device will be back to life
Click to expand...
Click to collapse
Thanks for the tip,
I tried to flash it with one autoloader days ago. It just didn't succeed. The screen went black with unceasing blinking green light.
I kept the contact wit BB Support. They just washed their hands. They told me to go to the Rogers Store where I just bought the PRIV to ask them for a replacement. This is kind of impossible, since I live in Mexico and when the device was bought was on a trip to Vancouver. Yesterday I just plugged in my laptop the phone with the autoloader running hoping something happens. So I left it at home for several hours. When I came back, it was just as before, restarting over and over and over until fastboot menu. So I just gave another try to the autoloader, but it just happened again. Now it remains in black screen and with the green led light blinking. I tried several button combinations over and over just to get to the fastboot menu with no success.
I can't make it to bring up the loading screen and neither fastboot menu.
I guess it was because picking a wrong autoloader for flashing the PRIV. I downloade n¿another autoloader for trying.
Please help with this.
My PRIV is the STV100-3.
The first autoloader I tried is the Rogers Canada or Orange Slovakia – STV100-3 & STV100-4 - AAF057 Software Version
The second I want to try is the BlackBerry common SW for generic STV100-1, STV100-3 & STV100-4 devices - AAF518 Software Version
This is the link where I got them:
http ://ca.blackberry.com/content/blackberry-com/en_ca/support/smartphones/blackberry-PRIV/reload.html
Thanks in advance!!
leo_ackzion
if the autoloader solution does not work then you need to force manually the unit into flashboot (google how to force fastboot)
then try to flash each content from the img into the device manually same as the nexus devices
the autoloader should be able to recover your device
this is the reload instruction website
http://support.blackberry.com/kb/articleDetail?articleNumber=000038083
this is where the autoloaders reside
http://ca.blackberry.com/content/bl...pport/smartphones/blackberry-PRIV/reload.html
make sure your device is physically an STV100-3 or 4 it is basic to have the proper version
nicromant said:
leo_ackzion
if the autoloader solution does not work then you need to force manually the unit into flashboot (google how to force fastboot)
then try to flash each content from the img into the device manually same as the nexus devices
the autoloader should be able to recover your device
this is the reload instruction website
http://support.blackberry.com/kb/articleDetail?articleNumber=000038083
this is where the autoloaders reside
http://ca.blackberry.com/content/bl...pport/smartphones/blackberry-PRIV/reload.html
make sure your device is physically an STV100-3 or 4 it is basic to have the proper version
Click to expand...
Click to collapse
Hi nicromant.
After several hours I wrote my last comment, the phone showed the fastboot mode, restarting over and over without showing the BB Logo, but only the fastboot menu, constantly rebooting.
Next, I tried to reload the OS via autoloader again. But then my phone again was in black screen with green and white blinking light.
Then I tried to manually force it into fastboot with the Android SDK Tools, but nothing happens.
When I introduce "adb devices" command, it won't show any connected device in the PC.
So I don't know what else I can do.
Please help!
Thanks in advance.
I just had this problem. Took it to the tmobile store i bought it from and they told me it was fried hardware. The phone keeps trying to reboot and fix itself but obviously it can't happen. Their solution? Get a new phone. I had a 2 year warranty and apparently the priv has been having so many problems that the store was offering a trade up deal to a samsung. Hopefully a store near you is doing the same, because thats probably your only option at this point if it's the same problem as mine.
leo_ackzion said:
Hi nicromant.
After several hours I wrote my last comment, the phone showed the fastboot mode, restarting over and over without showing the BB Logo, but only the fastboot menu, constantly rebooting.
Next, I tried to reload the OS via autoloader again. But then my phone again was in black screen with green and white blinking light.
Then I tried to manually force it into fastboot with the Android SDK Tools, but nothing happens.
When I introduce "adb devices" command, it won't show any connected device in the PC.
So I don't know what else I can do.
Please help!
Thanks in advance.
Click to expand...
Click to collapse
Try to install the appropiate ADB and fastboot drivers it is why your pc is unable to see the device, check on device manager if you have it setup properly, unfortunately i do not have a priv anymore (i change devices every 1 or 2 month)
I have same problem with my Priv from AT&T (100-1). It failed to boot after autoloader. it does not turn on. Just LED flashes: White one flash, then Green 3 flashes. and again. I can not force it into fastboot menu anymore holding Power plus Vol down or any other combination.
Need help! Thanks
after updating with this loader
https://bbapps.download.blackberry.com/Priv/bbry_qc8992_autoloader_user-common-AAG191.zip
i also cant boot the phone it just show me 4 options on screen but keep on coming back to it no matter what i select
Hold power & vol down both for 32 seconds for a real HARD reboot...
Charkatak said:
Hi,
If you don't know the model #, then don't flash...
I read that Hard Reset of the device is needed, by pressing and holding the volume up and down keys simultaneously for at least 10 seconds, when you reach the error screen
Click to expand...
Click to collapse
I had the same issue quite suddently with no warning. Phone just shut itself off (in a manner similar to what happens when you long press the powre button) Spent hours wondering what to do. Finally Thought the power button was stuck. I slipped a long finger nail into the gap where the power button contacts the phone electronics (dont know how to be clearer than this) to try and separate the power button and whatever it touches when you press it. After a couple of tries, The phone started up successfully. It appears to be a design issue
I FIXED IT!
Same issue as described, bootloop after 10 seconds.
I used electrical tape under and over the flat cable of the power button, also covered the "inner" power button with this.
Now it works for already 1,5 hours and is loading updates.
Also posted this as nes3Ah in crackberry forums, but it has to be released by a mod.
Good luck!