Database Users

Factory reset loop, please help

Im in trouble here. Was on ota 319 and decided to go back to us 1.6 since i was having issues with force close on incoming calls. Got all the way back to us1.6 then tried to load QDLTool and drivers. Once i got the driver installed by following the video, the phone went into a resetting loop and i cant get it out. I cant get into fastboot without using QDLTool.
I would like to load 309 recovery and 318pkg.
Im getting an error at the end on the run in QDLTool that says
ERROR[D2]: wait ADB fastboot mode timeout!
Please check that device is exist and driver is properly installed.
Download Fail! - 2010/12/22 23:06:40
Im not sure how to fix that issue. The phone is in fastboot mode when i get that error

QDLTool finaly worked. Had to use another usb port and reload drivers and so on. It went thru some whole deal and rebooted, looks like it loaded a new pkg and is rebooting......into what i have no idea.

just a black screen Im gonna puke

Running QDL Tool again. WTF am i supposed to do from here. Am i supposed to boot into something, or load a new pkg from the sd card, and what pkg;s would be compatable?
fastboot download: logfilter, checksum: 0x1bad7a9c ...
........Download android successed.
Download success - 2010/12/23 00:17:19
Elapsed Time: 247.60 sec
Just a black screen again.
Wait about 5 minutes for upgrading new images. Does this mean it will load a rom or i need to.......
Oh hmm, it just booted into some rom
Ok, now i dont know what im on.
build 10688
baseband gausb1a130500-us
android 2.2

Ok, put the 318pkg on the sd card and loaded it, wooohooo
Just another thread for searh results THANK GOD

[Q] Tab won't boot up after flashing with Odin

Hi,
did a flash of the JM4 firmware (P1000DXJM4_P1000DXJM2_P1000OLBJM1) using Odin (v1.7). Flashing of the firmware works fine and the upload was completed. However, the GTab did not reset automatically (i saw that the screen went blank for a second and then once again the downloading screen is shown). After i unplug the USB and then manually rebooted it, it is stuck at the Samsumg screen and won't proceed further.
Is there something that i've done wrong? i've placed a check on the "re-partition", "auto-reboot" and "F. reset time" on the Odin.
Any help is appreciated.
Thanks.

Turn the tab OFF and reboot in recovery : Power button + Volume UP . It will finish loading the CSC files and it should then reboot fine.
P_

Thanks.
Think i've screwed up my Tab big time. After recovery, it still doesn't show the CSC and the PDA version. What is shown is the Phone version which is "XXJMA". That's not going to work for me as i'm from Asia.
i'm going to try and flash it again.
In the meantime, anybody can think of anything to help me out, i'll greatly appreciate it.

From the look of that rom name......
Congratulation!! You are most likely have Protected Boot Loader and SBL now ^^
As I recall when I flash my second TAB with that firmware i have the same problem and I solved it by flashing Roto's JME (the one that format your SD card too).

Hi all,
i've managed to solve this problem by doing a few mix and matching. Currently my version (*#44336#) is showing:-
PDA1000DXJM4
Phone1000ZHJL1
CSC:Unknown
i see i don't have a CSC. Does it matter? Also, my reader hub is not working. Its giving me "Service Unavailable (4002)" (im sure i have internet connection, so connection problem is out).
Now the reason why i need to mix and match or update in the first place is this: my old version of JK2 firmware has a problem of not being able to connect to my exchange server using the native email client. So i did an upgrade using Odin. This somehow screwed up my versioning and everything else.
Thanks.

[Q] Bricked phone after failed RTM Mango Update

Hi guys
Just wondering if anyone can point me in the right direction before I send my Samsung Omina 7 in for repair. First a brief history
Updated previously from NoDo to the first mango beta without issue, then again to the refresh beta without a problem. Decided today that I would for RTM.
During update process updatewp kept timing out - I've since read resetting the device before attempting or deleting some of the zip files in the RTM package fixes this.
Instead of searching forums I unplugged the device and reset it when it wouldn't reboot. This left me with a completely unstable OS. It took ages to boot up and most apps wouldn't load.
I tried to restore my NoDo backup from the Zune beta but it didn't work. I uninstalled Zune Beta and drivers and attempted the restore using the current Zune version and again the restore would not work.
Figured I would just reflash the rom instead so I followed the guide below.
http://forum.xda-developers.com/showthread.php?t=973420&highlight=how+to+rom
This also failed - I can get into download mode, and WP7 Downloader looks like it's proceeding correctly but it is my understanding that after the first reboot it should go into the "connect to computer" style mode with the picture of the phone and a computer connected with USB. My phone does not do this - instead it boots to the Samsung Omina screen and just sits there. It seems to quickly reboot every 10 mins or so.
I've attempted the flash a second time and got the same result. Any ideas?

just goto download mode and flash it with another firmware..

If you can't get into download mode, just go to your closest DIY shop, grab 3 100k resistors and make yourself a JIG.
Full instructions here : http://forum.xda-developers.com/showthread.php?t=1092824&highlight=JIG
You should be able to reboot in download mode, and then restore to whatever ROM you want

Just tried that - used a different one but got the same result.
When WP7 Downloader gets to "Plz wait while rebuilding" the phone has rebooted to the samsung omnia 7 screen and not the computer connection screen.

Weird.
If you got to download mode after using the JIG, flash should be flawless.
I'm clueless here, apart from trying again with a different firmware/JIG.

Just and FYI. I couldn't fix it myself so I send it in for repair. They needed to replace the motherboard.

Soft Bricked (SM-G530W)

I was trying to upate the SUBinary and it told me to reboot. As soon as I did I get a message saying "Custom Binary Blocked by FRP" and a red text saying "Secure Fail : Kernal" help me.

It has something to do with your Google account being logged into the phone.. samsung can send signal to reset it but they won't if it's been rooted etc still trying to make sure reflash omg the phone with original rom would make it worse or not. Or maybe just reflash in the kernal. I'm on t mobile but can only find original rom on t mobile same network but we will see. I'm on my fiance a accident messaging from her phone lol or maybe just reflash the kernal the whole problem for me is I don't have a computer to try to reflash from what someone told me I may try to reflash with odin 3.90 with a tar file to the exact model number

Solution
I had the exact same problem as you but i found a fix
i know this is a very late response but who knows maybe some people will run into it
First of all you will need
-odin3
-samsung usb drivers
-g530w tar md5 file find yours here (im telus variant but bell worked for me)
https://1fichier.com/dir/OgrN3QNx
or
https://www.youtube.com/watch?v=N33i15UVCyA
g530w Pit file here
https://drive.google.com/file/d/0BzyeAt2hy6Xea0VPUDBLOWY5WU0/view
or
http://www.sammobile.com/forum/showthread.php?t=30863
and use odin to flash your phone while its in download mode connected to your computer
skip to 1:28
https://www.youtube.com/watch?v=6lki9ei2-WM
sorry for super messy post i rarely post things i hope this saves you time

This is the best and quick fix for FRP Lock
...Just follow the link: https://forum.xda-developers.com/grand-prime/help/custom-binary-blocked-frp-t3266961/page3
Worked for my SM-G530W
I had the same problem, and i used Kies3 (not compatible with my phone anyway), but if you go on toolbar to "TOOLS", "Firmware Upgrade and initialisation", it asks you for your device model (for mine i typed SM-G530W, and then it asks you for device serial number (S/N) found under the battery by the IMEI number. After this, follow on screen prompts (Restart your device in Download mode/ PDA, connect USB cable, etc), and let the software download and install (factory rom); After your device restarts, you are good to go (sometimes if it gets stuck on booting, remove battery for few second and start again.) Now you have to go back and set up everything you want, including re-rooting your device... Good luck. (My device is Galaxy Grand Prime SM-G530W Factory unlocked rom, Android 5.11.

Lumia 520 Unable to enter flashing mode

Hello!
I recently got my hands on a Nokia Lumia 520 for tinkering with. Its running on really old firmware, and I figured before I try anything weird, I'd mess around with it in its stock state. Thus, I tried updating the firmware.
The internal updater returned an error, stating that it could not contact the server for whatever reason. I figured this is most likely due to the Windows phone being discontinued, so I scoured the internet for firmware files. I eventually stumbled upon a YouTube guide that linked to a guide on Microsoft's Own guides page. It explained how to reinstall the firmware to a stock state. Desperate for progression. I gave it a shot.
The guide provided the "windows Device recovery tool", Which I would install on my windows 11 machine. I then proceeded to run the software and plug in the phone. HURRAY! It was able to tell me exactly what type of phone it was. Clicking the option to proceed, I was shown a screen explaining just how dated my firmware was. Suggesting It would fetch newer if not the latest firmware for me. I clicked on install and it started downloading.
I waited patiently for the software to download the firmware. After which it went to the installation screen. It then attempted to put the phone in flashing mode. Explaining that in this mode, the phone would restart, then have a blank screen. Instead what happened was that the system restarted normally, asking me to unlock the device. I wondered if maybe I had been impatient, so I waited for another while. The phone restarted again, still on the normal lock-screen. This happened another two times before the Recovery tool gave up and told me it had failed.
My question: Is there any reason why it would do this? Are there any methods to get it into flash mode?
I would hate to discard the potential of this device simply due to the inability to flash it. And I really hope it can be helped. Please let me know if there's anything else I should share about this. I'll happily take any help I can get!
Thanks in advance!
Edit, after a lot of trial and error, I managed to force it into flashing mode. Turns out the guides I followed missed a step. Pressing the Power and Camera buttons did the trick