Hi,
I sold a phone to a buyer and he claimed that the phone is damaged with "BP Panic ID 0x0008A58" showing and the phone keep rebooting. I did not see this before.
The below link shows the phone rebooting with the error message.
http://www.youtube.com/watch?v=J8Od9fMOGHk
Are there anyone who have encountered and solved this problem?
Does anyone have any idea what this is about?
Best regards,
try reflashing original rom with rsdlite
created threads together So this is precisely my problem. Reflash the original firmware no effect
try flash back with rsdlite with cincinati bell sbf..
don forget the volume down,camera button and power button (hold them until going into bootloader)
good luck
I have to reflash - Starhub, Russian, Korean and other sbf ...
may be due to broken bootloader? while I go and reflash it with normal
did u manage to get in the bootloader?
Sent from my Milestone XT720 using XDA App
in boot normally comes .. there are no problems .. but as seen in the video was an error occurs at startup android
My guess is this means the baseband software (phone modem) is crashing when it's trying to boot? (No clue why it would be called "BP", though). Is this a XT720 or XT701 or XT711? Google wasn't too helpful but I found this: http://code.google.com/p/cyanogenmod4milestone/issues/detail?id=22 that describes BP core dumps happening that seem related to using the phone features. I don't know how to determine if the problem is hardware or software.
Are you able to get into Motorola's recovery (just guessing that perhaps the modem isn't booted in that case)? Does the flashing happen then, too? Or in bootloader?
it can only guess so far .. Russia has very few service centers Motorola ... support service wrote that I took it to a service center
there is a version?
Why Motorola developers are not aware of such errors? Maybe it's guilt by Google, but I really doubt it
I just got a brand new SGS2 GT-i9210 from sweden. After unsimlocking it, it perfectly works on our experimental 4G (2.6Ghz) network in France.
I tried to root it, but the zergrush doomlord rootkit v4 does not work properly, it ends with the "Hellions with BLUE flames" error.
I used this rootkit with different SGS2 4G/LTE smartphone and never had problem, it always worked.
I was just wondering if someone could help me to root this GT-i9210...
Thanks in advance for your replies
I'd love to get into this as soon as I've got rid of the Tele2 simlock on my i9210. Any tips on reliable unlock code providers for this phone?
As this post comes up high on the google results for rooting the GT-i9210, here's the link to the ACTUAL page on how to root it.
Edit: Probably better to link to the OCAU thread http://forums.overclockers.com.au/showthread.php?p=14233218#post14233218
http://forum.xda-developers.com/showthread.php?t=1340526
This, 100%, works. More discussion on this phone here:
http://forums.whirlpool.net.au/forum-replies.cfm?t=1891584
xrobau said:
As this post comes up high on the google results for rooting the GT-i9210, here's the link to the ACTUAL page on how to root it.
http://forum.xda-developers.com/showthread.php?t=1340526
This, 100%, works. More discussion on this phone here:
http://forums.whirlpool.net.au/forum-replies.cfm?t=1891584
Click to expand...
Click to collapse
I don't dare to belive you.
The root method you refer to in your link is for models sold on the US market, in Europe this model is branded GT-I9210 (EU) and is similar, but not identical to the models in US or Canada.
I have followed a Swedish thread where people has used this method, but many of them has bricked their phones....
The whole process works fine through all steps until rebooting.
The back key and the menu key stops working.
I wish somebody could fix a reliable root method for GT-I9210.
I'm the guy who wrote that post on Whirlpool. I have a pair of GT-I9210Ts, both of which are now rooted using CWM and superuser.zip.
Note that this doesn't actually CHANGE anything on the phone. So it's not going to brick it. All it does is install CWM, and then uses CWM to install superuser.zip. I can't possibly see how it's possible to brick the phone doing this.
F5:ad said:
I have followed a Swedish thread where people has used this method, but many of them has bricked their phones....
The whole process works fine through all steps until rebooting.
The back key and the menu key stops working.
Click to expand...
Click to collapse
Yep, I did this today. The phone's back and menu buttons aren't working. I tried installing softkeys from the Market but still no go. Is there a solution to this problem?
That's.. very very strange. Someone else reported it, but I have no idea why this happened. You're not touching ANYTHING to do with the buttons. All you're doing is updating the recovery.img and then installing a package. I've rooted three phones now, and haven't had that problem.
Can you read http://forums.overclockers.com.au/showthread.php?p=14233218#post14233218 and tell me if you did anything different?
briteway said:
Yep, I did this today. The phone's back and menu buttons aren't working. I tried installing softkeys from the Market but still no go. Is there a solution to this problem?
Click to expand...
Click to collapse
I've put a bunch of recovery information on that ocau post (linked above). Have a run through that. If you're NOT using a Telstra phone, I'm unsure where you're going to find the correct roms though 8-\
xrobau said:
I've put a bunch of recovery information on that ocau post (linked above). Have a run through that. If you're NOT using a Telstra phone, I'm unsure where you're going to find the correct roms though 8-\
Click to expand...
Click to collapse
The method you have posted is one I have already tried, 2hrs after getting my phone from Telstra. Back button and Menu buttons blank out and no longer work.
No one should use this method until it is specifically tried and tested for the phone.
EDIT: Just to assist you a bit further with the method.
- A full factory reset was completed, not working.
- Telstra firmware downloaded, installed, factory reset, not working.
- Dialled *#*#2663#*#* - Selected Touch Key F/W to upgrade, not working.
----- Phone F/W was marked as 0x4, Part F/W was 0x0.
I believe this was the issue, the fact that there was a number mismatch.
Those with the GT-I9210 visit this link for Original EU Rom.
www"dot"sammobile"dot"com
As I mentioned on OCAU, I didn't have much of a problem.
"xrobau" Did you have any moment when the buttons did not work?
Hi,
Any updates on this phone rooting procedure?
This generic firmware will work in Portuguese operators? Any European tested it?
Thanks
Sent from my GT-I9210 using XDA
It's in Portuguese. Translate with Google. A friend of mine did root gt-i9210. I've used this method to root mine.
http://stuffandroid.blogspot.pt/2012/04/como-fazer-root-no-samsung-galaxy-s-ii.html
Sent from my GT-I9210 using XDA
In my case the keys stopped working after flashing first time a kernel with cwm recovery. The phone also didn't boot anymore. The kernel itself was backuped with the very same cwm.
Before I flashed the kernels with odin and also with "dd" command. No problems with the keys.
Based on these things I got the feeling that there could be something wrong with cwm.
I could not fix it so far.
I'm not sure whether my post would be valid any longer on a thread more than a year old.
Anyway, if someone needs a pre-rooted version of the latest stock Jelly Bean 4.1.2 XXUAMF1 COV (GT-I9210), they can do so from this thread, post #4:
http://forum.xda-developers.com/showthread.php?p=34712551
Flashed it via Odin & using it without any issues on my S II LTE GT-I9210T.
Jp
:good:
Hi all this great community, I have a serious problem with my phone Samsung Captivate Glide, and to install an application and hence fails to restart the logo of "samsung" and there can be hours, and try what they recommend in I have seen posts around here, removing the battery and waiting, by the way if I get both download mode and the recovery mode, and from there try to Re-Flasharlo the Official Stock ROM using Odin if I recognized and well if you did it correctly, but when I reboot again returns the logo of "samsung" and hence fails.
I also searched about it on google and other forums and especially the well known XDA say it is problem with the bootloader, now the question and doubt is like to recover or repair the damn bootloader, I searched on where to find some bootloader for my model, I have since seen some videos of other models of samsung as S and skyrocket with the same problem, there are the flash with odin also give the files of both the Bootloader, PDA, CSC, Phone callers flashing tools but I have found for my model.
I have also done the wipe's appropriate and even factory reset in the recovery mode and still nothing happen the logo.
By the way I had my phone updated to ICS 4.0.4 before I pass this problem because it came with Gingerbread 2.3, plus what I had rooteado with a program called "Kingo Android Root" which by the way is very effective and made me in less than 5 minutes without problem, I say all this for more information on this issue, if not affection to be something super-user.
I have also researched that used to do this with a "Riff Box Jtag" said the problem is not because I have no knowledge about it other than it requires special equipment
There will be some form of damage or repair this and my phone is garbage
I hope you can help me or guide me to do, I thank you in advance for your input and assistance.
Thank you ..
PD: sorry if my English do not understand because I do not know well
Hi, folks,
After many, many attempts, I finally was able to root my Verizon LG Enact/VS890/FX3, using NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243.apk, which I got from this forum about a week ago... for which I heartily thank Zero Sparks. Finally able to uninstall a lot of the crapware I didn't want, and to install several root-only apps which I did want.
The thing I'm having trouble with now, is finding custom ROMs for the phone. It's running KitKat, so it's not ancient, and if I can't use anything but the stock ROM, so be it. But I'm dying to try flashing Lollipop or even Marshmallow. It has to be a very specific ROM for that phone, because of the slide-out QWERTY keyboard... the wrong firmware wouldn't function properly. And there are a lot of bogus sites out there which want you to "complete a survey" or "sign up for one of these offers", but they never give you the download, it's just an endless circle of phishing sites... with lots of malware for my system, I'm sure. I'd much rather trust you folks on here, if you have anything.
I'm in the same boat, would love to upgrade off of 4.1.2 but can't find anything to use.
Additionally, a previous owner (bought off ebay) apparently unlocked the bootloader and replaced the stock recovery with something I don't recognize. When holding down power and vol down I see this:
Rooted
*********************************************
FACTORY HARD RESET
*********************************************
Permanently Erase User Data & Reset Settings?
Press Power key to confirm, and Volume Down or Up key to cancel
So not only can't I find a ROM to use, I can't even upgrade the stock ROM due to it not passing the root check. And I can't use stock recovery since it was replaced by the above. Anyone see this before?
I wish there was better support for the VS890 around, but I can't even find the original recovery / ROM image to flash.
UsualNoise said:
I'm in the same boat, would love to upgrade off of 4.1.2 but can't find anything to use.
Additionally, a previous owner (bought off ebay) apparently unlocked the bootloader and replaced the stock recovery with something I don't recognize. When holding down power and vol down I see this:
Rooted
*********************************************
FACTORY HARD RESET
*********************************************
Permanently Erase User Data & Reset Settings?
Press Power key to confirm, and Volume Down or Up key to cancel
So not only can't I find a ROM to use, I can't even upgrade the stock ROM due to it not passing the root check. And I can't use stock recovery since it was replaced by the above. Anyone see this before?
I wish there was better support for the VS890 around, but I can't even find the original recovery / ROM image to flash.
Click to expand...
Click to collapse
In my research, I could have sworn I came across a site that had the original "stock" LG software for download, but I can't find it now. The closest I come is this LG link that will give you the firmware -- and the VS890 is on their list: http://www.mylgphones.com/latest-lg-phones-firmware-update-model-version-date
I don't know if that might restore your stock recovery, at least. But have you tried doing the "factory reset" they offer, in this recovery app? Typically, this often restores the phone to whatever it was shipped with... which in your case, is just what you want. And there might be a method out there to un-root, I've seen that option in some of the better apps, like the "LG One-Click Root" found here. Then (if you're on Verizon, anyway), you could snag the OTA upgrade to 4.4.2, like I have... and root it again with the method I found.
ADDED LATER: Look in SuperSU, you should find an option for Permanent UnRoot.
Mr2nSmith said:
But have you tried doing the "factory reset" they offer, in this recovery app? Typically, this often restores the phone to whatever it was shipped with... which in your case, is just what you want. And there might be a method out there to un-root, I've seen that option in some of the better apps, like the "LG One-Click Root" found here. Then (if you're on Verizon, anyway), you could snag the OTA upgrade to 4.4.2, like I have... and root it again with the method I found.
ADDED LATER: Look in SuperSU, you should find an option for Permanent UnRoot.
Click to expand...
Click to collapse
Thanks for responding. Unfortunately my issue isn't the rooting of the OS (which I can undo, and have), it's the fact that the bootloader was unlocked and original recovery was replaced with that custom one I listed above. And yes, I did the 'factory reset', which reset everything to the original state of 4.1.2 ... but it didn't remove the custom recovery. Because of that, I can't ever upgrade via normal means (get the 0x13 error when I try).
Same deal with SuperSU, unrooting simply removes root access in the 4.1.2 OS, doesn't affect recovery. And, since there is no CMW / TWRP custom recovery option for VS890 I can't even attempt replacing the existing recovery. I'm stuck at this point unless someone figures out 1) where the stock recovery and firmware are located, and 2) a method to safely flash it to the phone. It sucks, I like this phone but it has some severe limitations. It also won't work with my Pebble watch, which is what prompted this whole endeavor in the first place (trying to upgrade to KitKat).
UsualNoise said:
Thanks for responding. Unfortunately my issue isn't the rooting of the OS (which I can undo, and have), it's the fact that the bootloader was unlocked and original recovery was replaced with that custom one I listed above. And yes, I did the 'factory reset', which reset everything to the original state of 4.1.2 ... but it didn't remove the custom recovery. Because of that, I can't ever upgrade via normal means (get the 0x13 error when I try).
Same deal with SuperSU, unrooting simply removes root access in the 4.1.2 OS, doesn't affect recovery. And, since there is no CMW / TWRP custom recovery option for VS890 I can't even attempt replacing the existing recovery. I'm stuck at this point unless someone figures out 1) where the stock recovery and firmware are located, and 2) a method to safely flash it to the phone. It sucks, I like this phone but it has some severe limitations. It also won't work with my Pebble watch, which is what prompted this whole endeavor in the first place (trying to upgrade to KitKat).
Click to expand...
Click to collapse
Have you tried simply finding and uninstalling the custom recovery? I know you said it was unfamiliar to you, but it has to be in there somewhere, under some name. And once it's removed, the phone would revert to its stock recovery. This is a great little phone, even if you can only get it to KitKat, don't give up.
Mr2nSmith said:
Have you tried simply finding and uninstalling the custom recovery? I know you said it was unfamiliar to you, but it has to be in there somewhere, under some name. And once it's removed, the phone would revert to its stock recovery. This is a great little phone, even if you can only get it to KitKat, don't give up.
Click to expand...
Click to collapse
The bad news: I would have no idea how to 'find' the custom recovery unfortunately.
The good news: I solved my problem! Although I couldn't update the OS via normal means (network) or via PC connection, I was able to manually flash KitKat (4.4.2) myself successfully. Here's what I did:
1) I downloaded the drivers for the phone from LG's site and installed them.
2) Connected the phone, it went into 'install' mode first where a drive appeared in my computer that contained the Verizon Upgrade Assistant.
3) Ran the upgrade assistant, it found the phone and downloaded the new firmware (.cab file). The upgrade assistant would not apply the update, unfortunately. I don't know if it was because of my bootloader issue or not, but I was at a dead end. Temporarily.
4) Tried following the procedure here but it didn't work with the current LG tools available. However it did point me in the right direction for
5) I found the LGFlashTool. I followed the instructions on that site. First went into download mode (powered off, removed battery, inserted battery, held vol up and down while plugging in the USB cable - *make sure it's a good cable!!*), then in the flash tool dialog itself I entered the .cab file name, selected [ CDMA, Diag, 33000 ], left what was auto-filled in version (but deleted the .cab extension) and hit the CSE Flash button. Next dialog I tried reading phone info, but it crashed (didn't fill me with confidence). Restarted, got back to that dialog, hit START. Next dialog, selected my country and language, hit OK. Then it popped up a new LG update window that actually did the update / flash.
Shockingly, it successfully worked. I was preparing myself for a bricked phone, but it worked ... AND fixed my bluetooth connection issue with my Pebble watch.
I have no idea if this procedure would work for custom ROMs or not (and I'm not going to press my luck and try), so I can't recommend it for non-stock stuff, but at least it's a way to flash a known working ROM for the LG Enact. Hopefully this helps someone else down the road. This was the first firmware flashing endeavor I've undertaken where I didn't already know someone else did it successfully first. Thus, my trepidation.
UsualNoise said:
The bad news: I would have no idea how to 'find' the custom recovery unfortunately.
The good news: I solved my problem! Although I couldn't update the OS via normal means (network) or via PC connection, I was able to manually flash KitKat (4.4.2) myself successfully. Here's what I did:
1) I downloaded the drivers for the phone from LG's site and installed them.
2) Connected the phone, it went into 'install' mode first where a drive appeared in my computer that contained the Verizon Upgrade Assistant.
3) Ran the upgrade assistant, it found the phone and downloaded the new firmware (.cab file). The upgrade assistant would not apply the update, unfortunately. I don't know if it was because of my bootloader issue or not, but I was at a dead end. Temporarily.
4) Tried following the procedure here but it didn't work with the current LG tools available. However it did point me in the right direction for
5) I found the LGFlashTool. I followed the instructions on that site. First went into download mode (powered off, removed battery, inserted battery, held vol up and down while plugging in the USB cable - *make sure it's a good cable!!*), then in the flash tool dialog itself I entered the .cab file name, selected [ CDMA, Diag, 33000 ], left what was auto-filled in version (but deleted the .cab extension) and hit the CSE Flash button. Next dialog I tried reading phone info, but it crashed (didn't fill me with confidence). Restarted, got back to that dialog, hit START. Next dialog, selected my country and language, hit OK. Then it popped up a new LG update window that actually did the update / flash.
Shockingly, it successfully worked. I was preparing myself for a bricked phone, but it worked ... AND fixed my bluetooth connection issue with my Pebble watch.
I have no idea if this procedure would work for custom ROMs or not (and I'm not going to press my luck and try), so I can't recommend it for non-stock stuff, but at least it's a way to flash a known working ROM for the LG Enact. Hopefully this helps someone else down the road. This was the first firmware flashing endeavor I've undertaken where I didn't already know someone else did it successfully first. Thus, my trepidation.
Click to expand...
Click to collapse
Good for you! See, you don't give up, and you get a happy ending.
It's a shame no roms for ours enact, its a cute qwerty android phone...please Can someone tell me how to enter recovery mode ? I bought this phone 2 day's ago but i haven't signal i want to do a wipe cache.. .sorry for my English.. .
Androide3 said:
It's a shame no roms for ours enact, its a cute qwerty android phone...please Can someone tell me how to enter recovery mode ? I bought this phone 2 day's ago but i haven't signal i want to do a wipe cache.. .sorry for my English.. .
Click to expand...
Click to collapse
Wish I could help you, but I never could do that on mine... had to use a sideload tool to do it from my PC. BUT -- I have two suggestions for you. First, download and install the KingRoot tool, to root the phone... it's called NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243.apk, and I think there is a link earlier in this thread which you can use to find and download it. You'll have to install it manually, then run it. (Don't bother with the "Purify" portion, you don't need that for now.) Your phone will now be rooted, by the only method that ever worked for me. Next, go to the Play Store, and download an app called "Quick Reboot", from Phong IT. This is a root-only app (hence the need to root, first) which includes a "Recovery" option. Try that out, and see what happens.
UsualNoise said:
The bad news: I would have no idea how to 'find' the custom recovery unfortunately.
The good news: I solved my problem! Although I couldn't update the OS via normal means (network) or via PC connection, I was able to manually flash KitKat (4.4.2) myself successfully. Here's what I did:
1) I downloaded the drivers for the phone from LG's site and installed them.
2) Connected the phone, it went into 'install' mode first where a drive appeared in my computer that contained the Verizon Upgrade Assistant.
3) Ran the upgrade assistant, it found the phone and downloaded the new firmware (.cab file). The upgrade assistant would not apply the update, unfortunately. I don't know if it was because of my bootloader issue or not, but I was at a dead end. Temporarily.
4) Tried following the procedure here but it didn't work with the current LG tools available. However it did point me in the right direction for
5) I found the LGFlashTool. I followed the instructions on that site. First went into download mode (powered off, removed battery, inserted battery, held vol up and down while plugging in the USB cable - *make sure it's a good cable!!*), then in the flash tool dialog itself I entered the .cab file name, selected [ CDMA, Diag, 33000 ], left what was auto-filled in version (but deleted the .cab extension) and hit the CSE Flash button. Next dialog I tried reading phone info, but it crashed (didn't fill me with confidence). Restarted, got back to that dialog, hit START. Next dialog, selected my country and language, hit OK. Then it popped up a new LG update window that actually did the update / flash.
Shockingly, it successfully worked. I was preparing myself for a bricked phone, but it worked ... AND fixed my bluetooth connection issue with my Pebble watch.
I have no idea if this procedure would work for custom ROMs or not (and I'm not going to press my luck and try), so I can't recommend it for non-stock stuff, but at least it's a way to flash a known working ROM for the LG Enact. Hopefully this helps someone else down the road. This was the first firmware flashing endeavor I've undertaken where I didn't already know someone else did it successfully first. Thus, my trepidation.
Click to expand...
Click to collapse
I did as you said, but I'm still on 4.1.2:crying:
I am stuck in a bootloop "mismatch_sig_len" and I have tried putting it into download mode, factory reset and a couple of recovery tools that can't find my device. I have read something about having to "short" two pins with tweezers or copper, to get out of this. Are there any successful methods anyone knows of? Thanks in advance.
Hey,
Haven't seen this issue before so I did a bit of searching around (my v10 is my first lg phone since nexus4) and it appears these phones may be (close to) unbrickable - similar to Samsung's of the past (I did this to an old sidekick)
At least phones like the g2 and g3 (maybe g4?) Have a way to force it into the Qualcomm download mode and use lg tools to flash back to stock
http://forum.xda-developers.com/showpost.php?p=65002893&postcount=17
This may be a start for you, and hopefully with your tests we can find out if these phones truly are unbrickable
Keep us posted if you find your way!
Sent from my LG-H901 using XDA-Developers mobile app
Same issue here. I spent 4 hours looking at every post there is on this matter and can not fix it. With the exception I CAN boot into the bootloader and issue commands, however I get "unknown command" all the time. I think this is a result from bad directions on the mm update recently posted. I tried everything I can think of and even tried the batter trick. I figure if I can get into TWRP or load it back I might have some success and moving forward.
I also had this problem after LG UP to 6.0 w/ twrp(tot file) flashed.
unlock bootloader will solve this issue.
This happened because new 6.0 FW modify check. I believe any mod on BL locked status will have this softbrick.