Database Users

hard reset failed, and now jamin will not power on

I tried to do a hard reset and the black screen came up and when i pressed the green button it tried to format the jamin but then came up with format failed
I then managed to get the device in bootloader mode by camera + reset
then let go of reset and press power once and that got me in bootloader mode, I then tried to install the new rom again and went to 86% and said error [326] This NBF can not be used with your PDA phone. Please check your NBF file. I than took the battery out of the imate device and when put it back in the phone wont even load of anymore its just black and dead. I know it isn't the battery because before I tried the hard reset I charged up the battery to full and i know there is definately nothing on the screen its black and when trying to plug it in via usb can not estqablish connection no more. I feel that this was a hardware issue from the start and is there anything else which i coulld try to prove otherwise? or do i need to send back to service centre? all help much appreciated

"New" HTC Magic

I recently purchased an android phone used, and it was pre-rooted.
I'm trying to get it back to stock firmware, as I hit reset data and now it won't boot. I have do the volume-down key fastboot menu and the home+power recovery options, but I have no idea howto restore it to original firmware from Rogers.
When plugging into the computer, it fails to properly install the usb drivers aswell, maybe because I cant boot the phone normally?
I'm really new at this, which is why I want to go to stock, thus I can relearn everything from scratch.
Also, on a side note, anyone know a place to get a replacement LCD screen, or a means of connecting the digitizer that has the ribbon-cable connection part of the lcd screen missing?
Cheers,
Bobbo

I would suggest you download the original rom and then load the original SW using recovery. Press "home and the start button and hold until the recovery menu comes up.
As for installing the ADB, you may not have installed the proper USB driver.....
check to see if your computer recognises the phone....
If not, you can manually install the USB driver.

Awesome, managed to finally restore the original Rogers firmware.
Now I'm getting an error when I try and launch the phone. android.process.acore stopped.
I can get text messages and wifi works, but the phone app crashed each time I try and load it. Any ideas?

[Q] BSOD + new computer without adb drivers = ermmm...

Ok this might seem strange, and just bare with me if I'm being thick...
I have had a nose around the forums and done a search but I couldn't find a solution to my problem.
I installed CM6 (by bumblebee) on my vega via CWM and instantly got BSOD - I didn't really think this was a problem because I knew the risk that it might happen and I had already done a backup etc.
However, all the parts for my new computer arrived the next day so I forget about my BSOD vega for a week as I started building my new computer and setting it up etc etc
I just got round to sorting my vega out when I realised I had completely wiped my old laptop with all the adb drivers on it etc (because I was going to sell it). Therefore, I cant get into recovery or flash anything to it because I cant use any adb commands :s (I cant reinstall the drivers - windows wont recognise the device as adb, only as a mobile device...).
Any suggestions? Am I being thick? Thank you for taking time to read through my rambling post anyway

You should be able to get into recovery and re-flash a stock rom. Make sure the device is plugged into the power and usb. Open device manager in win 7. Then hold down the back button for 2 secs then while still holding back hold power for 2 secs then release power but keep back button down for 2 more secs under universal serial bus controllers a new device should pop up. Point that at the usb drivers from the advent website. When the drivers have installed the screen on the vega will still be black but you should be able to flash the stock rom and start again.
Hope that helps

I will give that a try thanks for your help

Ok this is strange :S
EDIT: Drivers updated! But:
It only stays in APX mode for a couple of seconds before turning itself off - I know there is enough battery because I have booted it and left it for at least 10 minutes hanging in BSOD...
EDIT2: Ok, things have got worse:
- manged to flash stock image, booted in to 1.08
- flashed clockworkmod
- got into CWM and preceded to restore
- restore froze whilst restoring dalvik cache...
- left for an hour, no change
- decided best thing to do was to turn off device and boot again
- device boots, hangs
- used adb to reboot
- now wont even get to the 'booting...' screen, adb and pc wont detec device anymore
- tried to get to apx mode, works but my pc wont detect it so cant flash stock image again...
Sounds bricked anyone got any ideas? I know it was probably a stupid idea to switch it off whilst it was restoring but it was definitely frozen.

willk22 said:
Ok this is strange :S
EDIT: Drivers updated! But:
It only stays in APX mode for a couple of seconds before turning itself off - I know there is enough battery because I have booted it and left it for at least 10 minutes hanging in BSOD...
EDIT2: Ok, things have got worse:
- manged to flash stock image, booted in to 1.08
- flashed clockworkmod
- got into CWM and preceded to restore
- restore froze whilst restoring dalvik cache...
- left for an hour, no change
- decided best thing to do was to turn off device and boot again
- device boots, hangs
- used adb to reboot
- now wont even get to the 'booting...' screen, adb and pc wont detec device anymore
- tried to get to apx mode, works but my pc wont detect it so cant flash stock image again...
Sounds bricked anyone got any ideas? I know it was probably a stupid idea to switch it off whilst it was restoring but it was definitely frozen.
Click to expand...
Click to collapse
Keep trying to put it into recovery mode. At times it gets picky and you have to time it just right. Took me several attempts before it worked correctly again, so keep at it
Also, be sure to keep the USB plugged in while you are attempting to get it into recovery-mode and your sound turned up so you hear the infamous hardware-connected sound. Once you hear it, immediately plug in the power and start the recovery-flash. Do not wait too long or you'll have to start from scratch again
Keep at it, you're almost there.

Got there in the end thanks for your help!

[Q] HTC HD Mini error

Ok so my hd mini decided to throw a spaz and freeze so I had to whip out the battery and restart, upon restarting it would load up the white HTC screen and then just go to a black screen and freeze on it, eventually after numerous hard resets and it freezing on the orange windows loading/setup screen it finally worked and everything was restored to factory settings.
Now two weeks later the same thing has happened only now the phone wont let me perform a hard reset, it comes up with this and a red, green, blue and white screen:
PB92100
SPL-1.31.0000
!microP(LED) error(0x00)! expected(0x1B)
I have no idea where to go from here to try and fix, thought about maybe flasing a new rom but the computer wont detect the phone through the usb cable...
Anyone have any ideas or suggestions, please?

now you are in bootloader screen (tricolour screen) so you can flash ONLY stock rom for your device ,folow the steps in my post here : http://forum.xda-developers.com/showthread.php?t=997285 .Feel free to ask me anything

Awesome, thanks for that ledavi will try it as soon as I get home from work.

Same problem
I also have the same problem.. But i cant access the phone in bootloader menu..
only the error code described above is showing.
Tried several times with dft_sspl and custom roms
And htcs own latest stock.
Only getting errorcode 260 No connection..
Havent found anything about this anywhere on the net.. Maybe i suck at searching
but i have been looking for a couple of hours now..
Anyone have any ideas of what i can try??
Regards Krister

Microp(LED) Error
My htc HD mini has the same problem. Shows "MicroP(LED) error (0x00)! Expected (0x1B)" in bootloader mode and wont let your flash or boot normally. Removing the battery for a while seems to be helping to boot it normally without the error. Once its up, its working perfectly until it freezes again. Any suggestions/solution to this problem ?

Hi there
I had the opportunity to fix this led error message by chance. After hours of trials, entering to the bootloader with volume down + power, my HD mini has never been recognized through USB connection.
For an unknown (magical?) reason, i plugged the phone to the usb port WHILE PUSHING VOLUME DOWN BUTTON, and the message disappeared, and the phone was finally recognized. I don't know if it's a matter of chance, but it's worth to try!!
Good luck, hope it will work

Need Help with S7 Edge (SM-935FD)

Hi! It's my first time making a thread here so guidance is greatly appreciated. Here's how everything started:
I was just casually using my phone (at the time I was using the built-in browser of google assistant, just looking at some news) then suddenly my phone crashed (I've experienced this before every time I was using the google assistant built-in browser, a simple browser can crash this phone?). It just restarted like it normally would, then, after using the phone for a few minutes, it froze again! I waited for it to reboot but now it just powered off and won't turn on (it won't show any sign of life, no logo, not even an icon when I tried to charge). D:
I figured to have it checked by a local technician and when he tried to plug a charger in, a display showed it charged (found it weird but happy at that time). I figured it was the charger so I bought a new one.
So I got home to charge it fully and when I turned it on, it worked normally. However, when I tried to turn my wifi on, notifications popped up and suddenly it froze again! After that, it turned off and when I tried to turn it back on, I got this dreaded red texts on a black screen:
Bootloader exception ( RST_STAT = 0x10000)
Exception: do_handler_sync: DABT_EL1(esr: 0x9600010)
RDX, do not reboot*** ext4_wait_block_bitmap:494: Cannot read block bitpc : 0x8f0261d0 lr : 0x8f02618c sp : 0x8f117fd0
This showed and the phone won't even let me turn it off, so I just waited for the battery to die out. When it did, I tried to charge it again and planned to do a factory reset thinking maybe an app was causing this. I managed to go to the no command icon and manual mode but no factory reset menu showed up (where you navigate using the volume up and down). So I tried to restart but now it died out completely- no button combination would work, it won't charge, no display can be seen. Is it hard bricked?
I tried to wait a whole day thinking I would be able to charge it again, but it has already been three days and I am not able to perform anything.
There it is, I tried to be as detailed as possible. Additional info: I never tried rooting it or flash roms with it, I haven't done anything with the software (or hardware since I am careful) but install apps (officially from the playstore). From how I see it, it's a firmware problem and I was hoping someone here can help me bring my phone back to life. Is this my fault? If I have this repaired, am I the one who should pay for this?
I mainly want to know what the error message means and if there is a way for me to access the phone. (I figured if I have the technician fix this, all they need is a computer with a software that could fix this since it's a problem with the firmware. If that's everything they would do then I could do that too, with your help of course.)
Thanks to all in advance!

Hi. This sounds pretty strange. Technically...it is hard bricked but you can bring it to life. I can tell you what I would do, when I run into such a problem.
ATTENTION: YOU WILL LOOSE ALL OF YOUR DATA EXPECT EXTERNAL SD CARD
First download the newest firmware for your S7 Edge (G-935FD) on SamMobile and unpacking the .zip.
Download Odin in the newest version, open it and put the downloaded files in the right order in Odin (BL, AP, CP and CSC - the files from the firmware from SamMobile has labeling with BL, AP etc.)
Now the tricky part because your phone won't charge and doesn't go on. You have to go in the download mode with your phone (press and hold volume down - home button - power button) than an window appears and press volume up
Connect your phone with your PC (in Odin you can see, that your device is connected) and press start. It will take some time transferring the ROM and your phone will reboot automatically and after some minutes of blinking Samsung logo...the phone should start normally into the SIM card pattern screen.
Now you have a fresh stock ROM installed and everything should work fine again.
But your phone won't get on or will charge...maybe when you connect it to your PC it will charge. Otherwise I see no option to solve your problem. Your phone must charge again that you can go into the download mode and bring your S7 Edge back to life with a clean stock firmware and an working system.