Blackberry priv keeps on restarting - BlackBerry Priv

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!

Related

finally from Samsung How to Solve the Black screen (death screen )

after mailing SAMSUNG by Mr.Alzubair
from ce4arab website
about the Death screen
this is the answer :
-----
Dear Alzubair ,
Thank you for contacting Samsung Electronics.
Reference number:2104286715
Regarding your case, kindly note that the image you have displayed on
the screen of your phone, indicates that the device has entered the
Recovery Mode. The reason this happened, is because you have tried to
update the device’s Firmware, which isn’t actually released yet, and
that’s the reason why the Software crashed as well.
In order to get out of the Recovery Mode, please follow the steps below:
Recovery Process
1.Remove the battery and reinstall it. Power On your Phone
- Phone display “Connection picture for Phone to PC”
2. Recovery Mode in Kies
If upgrade failed in upgrade step, you can see next Pop-Up
- Select "Yes”
Firmware Upgrade program progress to recovery mode.
3. Select "Recovery" button.
4. Read the caution and check “all information has been verified”
- After this, it’s same with Firmware update Process
5. Click “Next”
- Firmwareversion display
- Firmware file is downloaded to PC
6. Firmware update
- After Firmware downloaded, Click “Next”
- Firmware update start
Caution
- Never disconnect or turn off the
device in thisstep
- If so, recover the phone refer to
recovery section
7.Complete
- After Firmware update complete, the device reboot
automatically
- Click “Next” Button
To do this manually instead of using Kies, please click on the Power
button, the Volume down button and the middle button all together all at
the same time. The phone would flash for 2 times, and on the 3rd time,
please remove your hands fromthe phone, and it should boot up normally.​
I hope this has been of some assistance to you. If you do have any
further queries, please do not hesitate to contact us quoting your 210-4286715
reference number.
Kind Regards,
Aya Smith
Samsung Electronics UK
Customer Communication Centre
Tel.: 0845 726 7864 (All calls charged at Local Rate)
Homepage: samsung.com
[Product] GT-I9000
The reason this happened, is because you have tried to
update the device’s Firmware, which isn’t actually released yet, and
that’s the reason why the Software crashed as well.
Click to expand...
Click to collapse
Bwahahahhaahahahahh!!
cheetah2k said:
Bwahahahhaahahahahh!!
Click to expand...
Click to collapse
LOL XD
at least they help me
I just tried it ( by the Manual way ) and it Works
so this works on the semi-bricked, no 3-button combo enabled phones ??
.. let's say, after a bad/failed bootloader flash ?
someone please confirm ?
later edit:
from what I understand after reading this, Kies can force any (Phone--!--PC) SGS into recovery and/or download mode?
if so, can we "extract" this feature and make it into a stand alone solution for half-bricked phones?
That's not a real black screen, I got one and my phone got the BSOD: No possibility to power on, no charging, nothing.
The "phone ! computer" is just a semi brick, get back to download mode and reflash with odin...
But thanks for the info indeed.
franklin01 said:
The "phone ! computer" is just a semi brick, get back to download mode and reflash with odin...
Click to expand...
Click to collapse
Some SGSs can't access download mode from that screen because of the proper bootloader that's missing. (3 button combo fix needed, not so safe)
wish samsung also adds a feature to kies that fixes the IMEI =D
franklin01 said:
That's not a real black screen, I got one and my phone got the BSOD: No possibility to power on, no charging, nothing.
The "phone ! computer" is just a semi brick, get back to download mode and reflash with odin...
But thanks for the info indeed.
Click to expand...
Click to collapse
2day i triad it two times and it works
but from what i understand same thing happened to me today ..
i did the 3 times flashing way :
BE SURE THAT YOU disconnect THE CABLE!!
To do this manually instead of using Kies, please click on the Power
button, the Volume down button and the middle button all together all at
the same time. The phone would flash for 2 times, and on the 3rd time,
please remove your hands fromthe phone, and it should boot up normally.
Then its work and downloading mode appear i installed an official Ver. by odin ( check on Re-Partition ) then it will work (work for me after the same thing that happened : No possibility to power on, no charging, nothing. )
Does this means that the phone has a secondary bootloader or what I dont get it, I already sent my phone to samsung so I cant try, I had my phone bricked stuck at a black screen after the S logo.
hang on... so it sounds like samsung is saying that phones that dont go into download mode straight away from vol-down, home and power need to keep holding the power button until the power cycles 2 times, then let go on the third?
i cant test it now because after i bricked my phone (black screen no power on or charge) i sent it back and i got a new motherboard with 3-button enabled... but this does make sense because when i had a 3-button disabled phone previously i did manage to get it into download mode from the phone-!-computer screen by trying different timings. it took a long time but eventually worked.
so it would seem if this is the case, that it is just a different boot loader and a different key combination to access download mode, but working nevertheless?
can someone test this?
Cant believe it, if the phone does has a secondary bootloader then it cannot be bricked forever.
Sent from my GT-I9000 using XDA App
stephengoo said:
Cant believe it, if the phone does has a secondary bootloader then it cannot be bricked forever.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
We already knew it had a secondary boot-loader...
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Partitions
This is what is patched to hotfix the 3BR in disabled phones.
3 times flashing way wont work for me, and at Recovery in Kies i cant see my Device!
Absolutly no USB!!!!
Sorry Guys!
So this forced download mode can be possible...
This guy here tried hard to explain same thing:
http://forum.xda-developers.com/showthread.php?t=812933
do you think it will work with korean version galaxy s?
No-Exit said:
3. Select "Recovery" button.
4. Read the caution and check “all information has been verified”
- After this, it’s same with Firmware update Process
To do this manually instead of using Kies, please click on the Power
button, the Volume down button and the middle button all together all at
the same time. The phone would flash for 2 times, and on the 3rd time,
please remove your hands fromthe phone, and it should boot up normally.​
[Product] GT-I9000
Click to expand...
Click to collapse
"all information has bee verified" means put phone in download mode and connect it to PC (can't do it without working 3 buttons combo).
"manually instead of using Kies" = same thing, doesn't work without 3 buttons combo.
This doesn't works if you didn't have 3 buttons combo enabled. I used heat trick instead and then patch aires P-SBL.
I sent my phone back because of this black screen of death. I could get into Download mode, and the other (vol-up) mode too, but no upgrading or changing firmwares worked to fix it. And Kies didn't see it, though Odin eventually did.
Wondering now if the Black Screen of Death was fixable after all, but then would Kies have to recognize it first?
I have a phone ! pc bricked phone right in front of me, I've tried this and a million other combinations, nothing works. I'm not being super pessimistic or anything it really doesn't work. I've left it with a phone repair store overnight and they couldn't fix it either. Im going to visit samsung/optus tomorrow.
edit:
I also want to point out that that message contains some horrible english supposedly from samsung UK
d47:
I am exactly in your shoes. Even with the overnight leave at a GSM repair booth-thingy. Im also considering handing it back to the retailer, but havent tried the heating up trick yet... Maybe its worth a try ?

[Q][HELP!!!]The process EVERYTHING has stopped unexpectedly.

Hey,
Yesterday I upgraded my gf's GT540 to 2.1 (v20B) (fooled around a bit with the no-logos-showing-at-boot error but got rid of that bug eventually by KDZ software upgrade) and later I tried fixing the "can't establish a reliable data connection to the server" bug by deleting the file located at /data/data/com.android.providers.settings/databases/settings.db. After a reboot, I got stuck in an infinite boot loop of the Android logo. No matter what update I reflashed, I was stuck with the infinite Android logo. I kind of fixed that problem by adb-ing inside the phone while the loop was going on and I tried to recursively delete everything in /data/data/.
Now, no matter what update I KDZ, every boot gives me constant "The process _________ has stopped unexpectedly...". I think the files are missing but I don't quite understand why, the updates should totally wipe everything from the device and then create a new file system bla bla bla... It's like no matter how I apply any update, or do a bunch of hard resets, it doesn't do anything to the phone.
BTW I haven't tried fastboot stuff (simply because holding the camera + power doesn't take me to fastboot for unknown reasons), and I don't know about the windows enabler or where to find it.
I spent like 10 hours trying to unbrick this phone and searched everything everywhere now and I am getting really annoyed and confused with what's going on so please somebody throw me some tips before I nail this device on the wall...
Damn, everything is so much easier with HTC devices...
Thanks for every chunk of info,
Jay
You can try to do a hard-reset - http://www.hard-reset.com/lg-optimus-gt540-hard-reset.html
PS. To turn on fastboot mode you should press Power (and hold it until the phone vibrates) and then press and hold Home button. Fastboot mode is just a black screen (there won't be any text displayed).
hash87 said:
You can try to do a hard-reset - http://www.hard-reset.com/lg-optimus-gt540-hard-reset.html
PS. To turn on fastboot mode you should press Power (and hold it until the phone vibrates) and then press and hold Home button. Fastboot mode is just a black screen (there won't be any text displayed).
Click to expand...
Click to collapse
I did at least 10 hard resets.
Holding the home button doesn't give me fastboot mode, it boots Android into safe mode...
PS: Somehow I have lost the ability to use ADB, which is quite annoying.
I forgot to mention - fastboot mode works only if you've ROM with fastboot - http://forum.xda-developers.com/showthread.php?t=828003
hash87 said:
I forgot to mention - fastboot mode works only if you've ROM with fastboot - http://forum.xda-developers.com/showthread.php?t=828003
Click to expand...
Click to collapse
Thank you I have managed to get to the blue FASTBOOT screen! Now I have a device named Android in the Device Manager, but I do not have drivers for it so fastboot console application is still stuck at < waiting for device >...
The drivers for fastboot installed for me just fine using windows update. You can also try drivers from this link: http://www.speedyshare.com/files/24707580/android_usb_windows.zip or http://pdanet.co/bin/PdaNetA245.exe
hash87 said:
The drivers for fastboot installed for me just fine using windows update. You can also try drivers from this link: http://www.speedyshare.com/files/24707580/android_usb_windows.zip or http://pdanet.co/bin/PdaNetA245.exe
Click to expand...
Click to collapse
Thank you, you are the hero of the day! Now I have succeeded in flashing back the v20a firmware!!

L31 bricked by flashing rollback package

Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Liebaart said:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Click to expand...
Click to collapse
With fastboot method, unlock bootloader again. Flash recovery. Boot into recovery. Wipe system and boot. Flash stock boot IMG and recovery IMG. Power off. Use dload. Now you are in bootloop. When booting press vol up 3 seconds, on e-recovery press shutdown. Press and hold power and vol up. Go to stock recovery, do factory reset.
Sent from my NEM-L21 using Tapatalk
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Liebaart said:
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Click to expand...
Click to collapse
Power off, vol up+ power can you go to recovery?
Sent from my NEM-L21 using Tapatalk
Liebaart said:
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Click to expand...
Click to collapse
Post here IMEI+SN and i try to get you bootloader unlock code.
Thanks! I sent you a PM.
Anonda said:
Power off, vol up+ power can you go to recovery?
Click to expand...
Click to collapse
No, I can only get into fastboot when connected to a pc.
OK. gtdaniel was so kind to provide me with an unlock code. THANKS!
But, I don't seem te be able to use it...
I can put the phone in bootloader when connected to a pc. When I type "fastboot devices" I do get the correct serial number. But when I type "fastboot oem unlock 343...338" I get a FAILED (remote: command not allowed).
It seems this is because I never could allow OEM unlocking from the Android settings menu. But since my phone is bricked, I can not enter into that menu!
Does anybody know how to solve this??
Liebaart said:
OK. gtdaniel was so kind to provide me with an unlock code. THANKS!
But, I don't seem te be able to use it...
I can put the phone in bootloader when connected to a pc. When I type "fastboot devices" I do get the correct serial number. But when I type "fastboot oem unlock 343...338" I get a FAILED (remote: command not allowed).
It seems this is because I never could allow OEM unlocking from the Android settings menu. But since my phone is bricked, I can not enter into that menu!
Does anybody know how to solve this??
Click to expand...
Click to collapse
u can try with
VNS-L21-L22-L31 Toolkit or
SRKToolHuawei-Lod-Chong-V2.0-20161002
But i dont know is that good idea to listen to me anymore
Thanks, but the Toolkit says it can't find the device.
Liebaart said:
Thanks, but the Toolkit says it can't find the device.
Click to expand...
Click to collapse
at command line when u write adb devices u got your phone ?
Maybe is dump question but did you install adb android driver ?
I'm pretty sure that someone wrote in thread that you don't need to have this oem permission in android if you are in fastboot
dragon218 said:
at command line when u write adb devices u got your phone ?
Maybe is dump question but did you install adb android driver ?
I'm pretty sure that someone wrote in thread that you don't need to have this oem permission in android if you are in fastboot
Click to expand...
Click to collapse
OEM permission need for fastboot/unlock bootloader.
Sent from my NEM-L21 using Tapatalk
Anonda said:
OEM permission need for fastboot/unlock bootloader.
Click to expand...
Click to collapse
Yes, that's what I read too. Since I can't change that permission anymore while I can't start Android, I can't unlock. Dammit.
Is DC Unlocker my only option then? It seems their software can do it.
I'm afraid I've got some pretty bad news. Last week the same thing happened to me after I was THAT stupid to actually try and flash the rollback package for the second time. My phone got bricked just like yours, and NOTHING worked to fix it. I tried completely everything I could find on the net and XDA, and in the very end I was forced to bring it in for warranty repairs. Even they COULD NOT fix it and the phone ended up with the entire logicboard changed with a completely new one. I was lucky that it all was done under warranty. Will never do anything as stupid as that!
Really hope you find a fix somehow, but if not, the repair service is your only solution, because otherwise the phone is as good as dead.
markositoo said:
I'm afraid I've got some pretty bad news. Last week the same thing happened to me after I was THAT stupid to actually try and flash the rollback package for the second time. My phone got bricked just like yours, and NOTHING worked to fix it. I tried completely everything I could find on the net and XDA, and in the very end I was forced to bring it in for warranty repairs. Even they COULD NOT fix it and the phone ended up with the entire logicboard changed with a completely new one. I was lucky that it all was done under warranty. Will never do anything as stupid as that!
Really hope you find a fix somehow, but if not, the repair service is your only solution, because otherwise the phone is as good as dead.
Click to expand...
Click to collapse
my phone is also reedy to send to service. I have a lot of phone with android but no rom make so many damage to my phone, like this fc** rollback. finger cross, because huawei service in my country without warranty,takes for new motherboard 175 $ . I bought phone for 233 $ with 3 gb ram..... This will be harsh and pay(in)ful lesson for me.
dragon218 said:
my phone is also reedy to send to service. I have a lot of phone with android but no rom make so many damage to my phone, like this fc** rollback. finger cross, because huawei service in my country without warranty,takes for new motherboard 175 $ . I bought phone for 233 $ with 3 gb ram..... This will be harsh and pay(in)ful lesson for me.
Click to expand...
Click to collapse
Uhh, I am sorry to hear that. But yes, I had the same harsh lesson. They will be forced to changed the motherboard too, cause even they won't be able to re-flash the whole system. Though, what I did to have the warranty not declined, is I brought the phone to the service and said that - "The phone received and OTA update through the updater, I didn't look much into it and just went with it, pressed on update and everything seemed well. It worked until the moment where it installed and restarted, and now the phone is stuck on Huawei logo and you can't possibly do anything with it, not even turn it off." - and that's it. They will have to repair it under warranty because there is no proof left that you had rooted it or done any other installations not authorized by Huawei.
Best of luck!
Liebaart said:
Yes, that's what I read too. Since I can't change that permission anymore while I can't start Android, I can't unlock. Dammit.
Is DC Unlocker my only option then? It seems their software can do it.
Click to expand...
Click to collapse
I know that i read somewhere how to manage to this oem lock. I was 50 % right.
https://forum.dc-unlocker.com/forum...61751-huawei-mate-9-mha-l29-erase-frp-problem
Some user got the same problem that you have and flash boot.
But truly if u don't have "your device has been unlock" only bootloop on huawei logo, is more simple to send it back to warranty and play dump.
I have now "your device is unlock" and i pray for miracle.
Liebaart said:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Click to expand...
Click to collapse
I am exactly in the same situation with the difference that I don't have Fasboot! How do you get to Fastboot? Mine hangs on the screen that says the phone is unlocked and the device is booting... Vol+/Vol- and Power doesn't boot into Fastboot and my minimal ADB doesn't recognize the phone in the stages that it hangs...
---------- Post added 16th April 2017 at 12:04 AM ---------- Previous post was 15th April 2017 at 11:52 PM ----------
I have the same situation. I tried everything, Three button method, letting the battery run out completely, Vol+ and Power, Vol- and Power, connected to PC, not connected to PC. Every time I disconnect the charger, and reconnect it starts from 0. I read some other people here have the same problem. Send it to warranty and explain your rollback process unlocked the bootloader somehow (I mean the phone does do a lot of sh*ty sh*t, so this shouldn't seem very odd as well!!!) and hope that you get a repair/replacement and after that sell it on ebay hoping some stupid people like us in the first place will buy it and spend your money on a phone more reliable!
I managed to access the fastboot using the 3 button method in cold boot. Hold the Power key until the screen goes off and then release and hold down the Vol- key and immideately connect the usb cable to PC right before it vibrates or exactly when it vibrates (it's a matter of timing), and bingo you are in fastboot and you can flash system.img, recovery.img, cust.img, cache.img and boot.img from there, but this is not how I revived my phone. I used the 3 button method again when the phone was charged for like half an hour or so and the did the same cold boot trick and I could boot into the force upgrade environment (strangely this still didn't work whitout connecting the usb cable to PC), but it somehow didn't want to read the UPDATE.APP that I had in dload folder on my SD card and wanted to have it from my PC (I just felt it nad there was no indication of it ) so then I installed the DC Phoenix tool and payed 15 euros to be able to inject the complete UPDATE.APP to my bricked phone and the installation went well to 99% and failed, but I rebooted the phone and I could boot normally. Just to make sure I did a factory reset afterwards. Hope this helps.
Cannot get into Bootloader
Hey there!
Essentially as stupid as I am i flashed the Rollback Image at Android 6.0 too, because i wanted to get rid of C900. So now my phone is stuck in the Startup screen too. As mentioned here, I wanted to unlock bootloader again; The Button combination does not work, and if I want to start in bootloader via ADB, it just says "waiting for device"
i am really desperate and i don't know what i should do now
Thanks for the help
EDIT: Somehow managed to got it into Bootloader. At the moment i am unlocking it. Where do i get TWRP and the needed things? Please help, i'm just some noob who doesn't know how it's done
EDIT2: Solved, got Stock Recovery Re-installed, Flashed with the Force Update Method the Main Package of the Rollback (so not the temp rollback data), and worked. But Still C900 and no Google sign-in possible. Someone know how to solve?

LG V20 Device is Corrupt and BootLoop

Hey all! Hopefully you can help with this issue. I have had this phone through T Mobile for a few months now, and am stuck in a real bind. As the title suggests, I have a boot loop issue and Device is Corrupt issue as well. The red Triangle is an issue with the OS. I cannot get the phone to boot to Android, nor get into recovery. I can however bring up the IMEI menu, which displayed the IMEI. I really need help, as this is my main contact for job search and family.
Im on sprint so this method is unavalable to me.
Tried LGUP? you have the ability to shoehorn a KDZ file in whicj will bring your phone to stock
As this is a no go for the ls997 i have no idea how this is accomplished. Check the forums for said method.
elijah420 said:
Im on sprint so this method is unavalable to me.
Tried LGUP? you have the ability to shoehorn a KDZ file in whicj will bring your phone to stock
As this is a no go for the ls997 i have no idea how this is accomplished. Check the forums for said method.
Click to expand...
Click to collapse
I will definitely look into this. I just want my phone back TT.TT lol
I wanted to chime in, I've got the same issue as OP.
What's broken:
turning the phone on normally - displays an LG logo; gets stuck, won't proceed past this point
holding VolUp while connected to PC - displays IMEI; won't enter download mode
holding VolDown - displays IMEI; won't enter fastboot or recovery mode
So, there's no way to get to recovery. I'm stuck with a $400 brick that displays a logo or an IMEI number.
LGUP w/Uppercut doesn't work either, shows up as an unrecognized device, and it wouldn't matter if it were recognized, because I can't get the phone to download mode to restore a stock .kdz.
I just ordered the phone on the 4th from Amazon, so I'll see if I can return it/get a replacement, but I'm guessing I won't be that lucky. It does display the orange "WARNING: Bootloader Unlocked" screen, meaning it's very easy to see that the warranty has been voided, so I guess whatever support I get is a crapshoot.
Again, since I can't get to fastboot mode, there's no way to restore to stock and relock the bootloader before returning it. Kinda dug myself into a hole here with no other options.
I got it to install! Now to just play the waiting game and see what happens. I had to do some finagling to get it to work, but it works.
I found a H91810 KDZ, I started Uppercut which loaded LGUP, click on UPGRADE, then selext the KDZ file from where you saved it. Should work. Also make sure all of your drivers are up to date.
Griever0 said:
I got it to install! Now to just play the waiting game and see what happens. I had to do some finagling to get it to work, but it works.
I found a H91810 KDZ, I started Uppercut which loaded LGUP, click on UPGRADE, then selext the KDZ file from where you saved it. Should work. Also make sure all of your drivers are up to date.
Click to expand...
Click to collapse
So, I jinxed myself. I did in fact get the phone back up and running. But its not working correctly. I have a black home screen and the Recommended apps keeps popping up... THis is going to be a long night...
Griever0 said:
So, I jinxed myself. I did in fact get the phone back up and running. But its not working correctly. I have a black home screen and the Recommended apps keeps popping up... THis is going to be a long night...
Click to expand...
Click to collapse
Scratch that, I just had to pick my home screen loader. Phwew. I did it and I feel Happy. THANKS For the help!
HELP
Griever0 said:
Scratch that, I just had to pick my home screen loader. Phwew. I did it and I feel Happy. THANKS For the help!
Click to expand...
Click to collapse
How did you do it, I'm currently having the same problem with a phone that's on T-mobile
questionblock said:
I wanted to chime in, I've got the same issue as OP.
What's broken:
turning the phone on normally - displays an LG logo; gets stuck, won't proceed past this point
holding VolUp while connected to PC - displays IMEI; won't enter download mode
holding VolDown - displays IMEI; won't enter fastboot or recovery mode
So, there's no way to get to recovery. I'm stuck with a $400 brick that displays a logo or an IMEI number.
LGUP w/Uppercut doesn't work either, shows up as an unrecognized device, and it wouldn't matter if it were recognized, because I can't get the phone to download mode to restore a stock .kdz.
I just ordered the phone on the 4th from Amazon, so I'll see if I can return it/get a replacement, but I'm guessing I won't be that lucky. It does display the orange "WARNING: Bootloader Unlocked" screen, meaning it's very easy to see that the warranty has been voided, so I guess whatever support I get is a crapshoot.
Again, since I can't get to fastboot mode, there's no way to restore to stock and relock the bootloader before returning it. Kinda dug myself into a hole here with no other options.
Click to expand...
Click to collapse
Were you ever able to get this resolved? I'm having the same problem, except it's not showing anything about the bootloader that I can see
chuckyanutsup said:
Were you ever able to get this resolved? I'm having the same problem, except it's not showing anything about the bootloader that I can see
Click to expand...
Click to collapse
Ok, I seem to have my device back up and running. The step I was missing was to remove the battery, disconnect the USB cable, put the battery back in, hold volume down but don't press power, instead connect usb cable. This got me into fastboot and I was able to recover from there.
this might work for you!
questionblock said:
I wanted to chime in, I've got the same issue as OP.
What's broken:
turning the phone on normally - displays an LG logo; gets stuck, won't proceed past this point
holding VolUp while connected to PC - displays IMEI; won't enter download mode
holding VolDown - displays IMEI; won't enter fastboot or recovery mode
So, there's no way to get to recovery. I'm stuck with a $400 brick that displays a logo or an IMEI number.
LGUP w/Uppercut doesn't work either, shows up as an unrecognized device, and it wouldn't matter if it were recognized, because I can't get the phone to download mode to restore a stock .kdz.
I just ordered the phone on the 4th from Amazon, so I'll see if I can return it/get a replacement, but I'm guessing I won't be that lucky. It does display the orange "WARNING: Bootloader Unlocked" screen, meaning it's very easy to see that the warranty has been voided, so I guess whatever support I get is a crapshoot.
Again, since I can't get to fastboot mode, there's no way to restore to stock and relock the bootloader before returning it. Kinda dug myself into a hole here with no other options.
Click to expand...
Click to collapse
okay so holding VolUp while powered down and plugging into pc will bring up download mode if its still there,
if you have twrp installed prior to this red triangle then pull battery/put back battery. hold VolDown and power at the same time, as soon as LG logo comes up release power button (fast) and then hold it back down again while never letting go of VolDown. this is the factory reset hit yes for both questions and it should reboot phone into Recovery mode. some times you have to do it twice to get recovery (twrp) to pop up! i hope you have bootloader unlocked and twrp.
---------- Post added at 06:13 PM ---------- Previous post was at 06:07 PM ----------
Griever0 said:
I got it to install! Now to just play the waiting game and see what happens. I had to do some finagling to get it to work, but it works.
I found a H91810 KDZ, I started Uppercut which loaded LGUP, click on UPGRADE, then selext the KDZ file from where you saved it. Should work. Also make sure all of your drivers are up to date.
Click to expand...
Click to collapse
If using the LGUP you must get the G4 Dll file for it to read the phone and com its on. i believe its a common.dll file i cant really remember...
chuckyanutsup said:
Ok, I seem to have my device back up and running. The step I was missing was to remove the battery, disconnect the USB cable, put the battery back in, hold volume down but don't press power, instead connect usb cable. This got me into fastboot and I was able to recover from there.
Click to expand...
Click to collapse
Awesome! Glad to hear it!
my lgv20 is supposed to be on the corrupt screen but it looks like a glitch happened or something and the corrupt screen is all messed up it has the red warning signs across the top of the screen and it just says giberish and it keeps bootlooping. ive tried everything i can only get to imei display if im lucky and it tells me "press the POWER key to exit and restart the phone" but when i do it just takes me to the messed up corruption screen and stays bootlooping someone please help.
weirdomane said:
my lgv20 is supposed to be on the corrupt screen but it looks like a glitch happened or something and the corrupt screen is all messed up it has the red warning signs across the top of the screen and it just says giberish and it keeps bootlooping. ive tried everything i can only get to imei display if im lucky and it tells me "press the POWER key to exit and restart the phone" but when i do it just takes me to the messed up corruption screen and stays bootlooping someone please help.
Click to expand...
Click to collapse
What model do you have?
You can put the phone to download mode (even if screen displays glitchy gibberish screen) by taking out Battery first, put battery back in after 10 seconds. Then just press Vol up and while keeping it pressed, connect to USB. If you have drivers installed, your phone will get recognized by LGUP. Now from here you can flash the stock rom.

HELP! Stuck in Boot Logo w/ no Recovery Mode

Ok so before I started writing this I had only one problem now I'm worried my problem has gone from bad to worse.
I updated my 6T to 10.3.2 from the latest Beta after the process it prompted for a restart, upon restarting it got stuck in the boot animation. I tried going into Recovery and Download mode unsuccessfully so I went through the forums a bit and saw that someone who had the same problem successfully entered Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on! :crying:
Has anyone experienced this or know how to fix this? Any help will be much appreciated. Tia!
theDUD3 said:
Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on!
Click to expand...
Click to collapse
These should be clarified:
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
Turn the phone off, let it sit. Then try turn it back on. Any response?
try to shutdown phone ...hold vol+ and power button for like 15 sec and restart your phone if this didnt work then u can try MSM tool
Thanks guys, got it working using MSM Tool!
regarding oneplus 6 got stuck on logo screen and recovery mode not working
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
You are likely going to lose your data. Know that going in if its not already backed up.
If you have the fastboot menu you can use the fastboot roms.
Or my least favorite option or what I would try last, MSM Tool (Tmobile 6Ts use a different tool).
IMPORTANT if you want to try and recover and data off your phone first, go to fastboot, and try and "boot" the TWRP img (not the installed one, one from your PC using the fastboot command). If that works you might be able to recover data. If that does worm, try dirty flashing the last ROM you were running and see if it boots.
No worries!
frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
Hello, I am sorry to hear of you having this issue, I just went through 3 1/2 days (off and on) of recovering my T-Mobile OnePlus 6t which I found a way to get my unlock code within 2 weeks of having it, so I rooted it and put a custom kernel on it, stuck on 9.0 never let me update as I was not familiar with A/B partitioning, yet! The answers I saw to your questions were spot on, I just had a little to add to it and I'm sure I am not alone. Real quick let me list what has gone wrong on the rare occasion it hit the fan with the 6t...
- When I would accidentally and rarely let my battery die it seemed like it took forever to get it to reboot, I mean it sat on my desk of DOA devices for 2 weeks!
- It often seems like the buttons do not always respond properly and never have when I needed them to. Been through this before, I've bricked and unbricked and flashed and re-flashed and wiped all weekend and I like Android 10 and all but seems everything is different for every build, and everything seems to have to go in the right order with the exact right file or you wind up in a jam, period..
- That said, the previous person that answered your question has likely encountered similar, I've heard of right down to the buttons not physically working, but I have been a Smart Device Master III Technician for over 5 years, i know my buttons were not broken.
- Most likely culprit that I just handled and worked, i did have to use the MSM tool, several times - and re-unlock the BL, several times I would not even get the chance to get to fastboot, just a screen saying Build and Hardware not a match"" in yellow letters and it just bootlooped. No fastboot is no good, but when you said the tool would show some signs of working but then not, I have 2 solutions that I needed on diffrent occcasions.
1 - As mentioned fully try other USB cables, and ports, if you pull the usb-c out of the port and hold <power + vol up + vol down> eventually it will do something, very picky, sometimes gotta move your fingers to different spots on the buttons and also after 15-20sec let go of power and hit and hold it again... after a few seconds before it vibrates stick the cable in connected to your PC and the screen will be black (obv) but the msm tool will pick up on it. I know about the cables because I take good care of my phones and cables and charging ports, however on my final fix today it showed in msm tool it was connected but waiting for device.... Fed up i put the phone down and moved the usb cable a little bit and it picked up on it and did its thing! That part was just the cable, getting into qualcomm mode or w.e. is a bit tricky sometimes.
- Also someone said set it down for a while and come back to it.. THAT WORKS!! Let it fully charge and often just plugging in charger turns it on, bootloop soft brick or however have you, very simiilar to an Apple device and their DFU (don't f up mode cause screen is black..)
I hope that helps you get in touch with your family and friends.. Whatever you do, don't give up bc if you have not got it yet, you will! One other note, there are a few different msm tools available and they look the same some same size, but the one that supposed to work on my phone didn't and one that they say only a fool would attempt to try actually saved me, so if all else fails, use a different msm tool/usb cable and you will get it! I don't think I can post links yet I am on here very rarely, but plan on more! I have received so much help from XDA throughout the years on thousands of phones with just software issues alone, aas well as guides to my own phones. I would be honored to give back as I also have some extensive knowledge on many devices but I am a noob in comparison to many! Stay safe, good luck and please update and let us/ me know how it worked out for you. If i can help further I will, I have every firmware file for the OP6t, recovery, tools, software, this is not new to me but I feel your frustration!

Categories

Resources