Database Develop

[Q] Unable to update using Kies

Emrys_ said:
For the sake of clarity, here is what happens:
In order to have Kies properly connect my phone, I need to restart the phone. Kies sees the phone, I click on update firmware, I skip the backup (this also does not work for some reason), and then it says: Samsung Kies will not update the firmware, do not disconnect the phone.
It auto disconnects the phone, and nothing happens... I cannot reconnect the phone to Kies unless I reboot it.
Any help is appreciated
Thanks
Click to expand...
Click to collapse
I am having the exact same problem... I am also unable to backup anything using Kies 2.0.2
any luck finding a solution??
ghosty_uk said:
... steps that worked for me
1, downloaded MyBackup (free version)
2, did backup of both apps and data (put both on ext memorycard)
3, used the restore to factory option under privacy in the settings menu
4, unmounted internal sd card and formated it (to remove the mtp loop issue)
5, run kies,
6, select update firmware,
7, at the box where it says no device connected, put into test mode (ctrl + alt + U + P)
8, connected phone
9, detected thaqt there was an update to JM1 available
10, started update,
Click to expand...
Click to collapse
I have yet to do any of this (other than get a backup using MyBackup), but have some questions... (noob here)
Step 3: Will this remove all the definitions for my phone number and/or provider as well?
Step 4: I'm assuming I am having the same problem here with the mtp loop issue, is there another way to get rid of this problem?
Step 7: the CTRL+ALT+U+P thing doesn't work with Kies 2.0.2 so if I am unable to do an update, will the phone be at Froyo (2.2) as it is now? or does it revert to 2.1 (which it was when I bought the unit)?
Thanks in advance!

HELP!!! I bricked my N3!!!

Ok. So rooted my Note 3 in Oct and ROMd in Jan with XNote 7. I had it all fine and everything since. Well, I upgraded to XNote 12 and realized I couldn't receive calls and a few other weird annoying bugs. So I attempted to downgrade back to MJ5 using the Restore tutorial in the General section.
Alright, well I did the whole tutorial I Heimdalled the MI9_Fix.img.ext4 file and then started flashing the ZIPs. I did the SEC_CSC then I tried the 2400845 and it failed with a message about system/vender/lib.camerafilter.whatever.so couldn't be found and quit. I figured it was normal so and now I'm stuck at the Samsung logo with a padlock. It will go into recovery and Odin mode fine.
It also deleted my Safestrap. So I cannot get into SS recovery. I have tried the tutorial again and now Heimdall quits with error 87 and something about a I/O error.
I have also tried to Odin the MJ5 stock flash files (AP, BL, CP and PIT) but it does nothing. I cannot install a ROM and cannot use my phone.
I desperately need my phone for work, so if someone can help me out ASAP, so I don't lose my job, I would be SO grateful! THANK YOU!!!!

533y4 said:
Ok. So rooted my Note 3 in Oct and ROMd in Jan with XNote 7. I had it all fine and everything since. Well, I upgraded to XNote 12 and realized I couldn't receive calls and a few other weird annoying bugs. So I attempted to downgrade back to MJ5 using the Restore tutorial in the General section.
Alright, well I did the whole tutorial and started flashing the ZIPs. I did the SEC_CSC then I tried the 2400845 and it failed with a message about system/vender/lib.camerafilter.whatever.so couldn't be found and quit. I figured it was normal so I Heimalled the MI9_Fix.img.ext4 file and now I'm stuck at the Samsung logo with a padlock. It will go into recovery and Odin mode fine.
It also deleted my Safestrap. So I cannot get into SS recovery. I have tried the tutorial again and now Heimall quits with error 87 and something about a I/O error.
I have also tried to Odin the MJ5 stock flash files (AP, BL, CP and PIT) but it does nothing. I cannot install a ROM and cannot use my phone.
I desperately need my phone for work, so if someone can help me out ASAP, so I don't lose my job, I would be SO grateful! THANK YOU!!!!
Click to expand...
Click to collapse
do the procedure again and follow it to the letter as i can see you can still get to dl mode, btw you're supposed to flash the sec_csc and 240058 AFTER you flash the system.img with heimdall.

posersk8r said:
do the procedure again and follow it to the letter as i can see you can still get to dl mode, btw you're supposed to flash the sec_csc and 240058 AFTER you flash the system.img with heimdall.
Click to expand...
Click to collapse
I can do the ODIN part, then when I try the Heimdall part, it comes up with an error. I have tried it 5 times over. To a T... : (
And yes, I know you flash those BEFORE. That's what I meant to say, but I was in a rush...

Im in a similar pickle but my problem is that I need a way to get those files to the SD card because the thing is bricked. I can't copy the files to a bricked phone and every device in my house refuses to read the micro SD card.

533y4 said:
I was in a rush...
Click to expand...
Click to collapse
That's the problem right there. Over in my thread about the kitkat update fix people are saying it's not working for them but they are missing steps because they're not reading everything. I've used that method 3 times so far and it worked all 3 times. Start from the beginning. Delete all the files from previous attemtps, go to step 1, read everything, you will get it.

mazdamiata210 said:
That's the problem right there. Over in my thread about the kitkat update fix people are saying it's not working for them but they are missing steps because they're not reading everything. I've used that method 3 times so far and it worked all 3 times. Start from the beginning. Delete all the files from previous attemtps, go to step 1, read everything, you will get it.
Click to expand...
Click to collapse
Again, I have done this 5 times. No joke. I have redownloaded everything 3 times.
1) Download and install Heimdall from here for windows. You'll need this and this to avoid missing .dll file errors
2) Download the following files;
MI9_fix.img.ext4
https://mega.co.nz/#F!icMTnSQY!bMBNFmUnn2_K8olSTYpwIA (mirror provided by drakeymcmb)
sec_csc.zip
rldv.zip
2400258.zip
Put everything except for the system.img on your external SD card
3) Download and install the MJ5 partions. Use Odin to flash these files (match the file names with the different upload slots)
AP_N900AUCUBMJ5.zip
BL_N900AUCUBMJ5.zip
CP_N900AUCUBMJ5.zip
HLTE_USA_ATT_32G.pit
4) Now is the time to use Heimdall.
Reboot into Download Mode once Odin finishes.
Install the vcredist packages downloaded from step 1.
unzip the heimdall .zip file to c:/
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message
5) Navigate on your computer to c:/Heimdall Suite/ and open heimdall-frontend.exe.
IMPORTANT -- Go to the Utilities tab and click the "Detect" button
Go to the Flash tab on Heimdall, click Browse and select the HLTE_USA_ATT_32G.pit file downloaded from step 3
Click the 'add' button, then next to 'partition name' select system from the dropdown.
click the Browse button underneath the dropdown, and select the MI9_fix.img.ext4 image you downloaded from step 2.
6) Click Start. ***I usually check the 'No Reboot' box to prepare for booting into recovery
THIS IS WHERE I CAN NO LONGER GO ANY FURTHER!!! IT SPITS A I/O ERROR 87 AT THIS POINT! I CANNOT GET AROUND THIS! THIS IS WHAT I NEED HELP WITH!
7) Heimdall and your Note will report a bad flash at around 95% -- but don't worry -- your system.img got uploaded Reboot directly into recovery mode.
8) Once in recovery, select "Choose update from external" in the recovery, and select the sec_csc.zip you downloaded earlier (did you remember to put that file on your external SD card?). This will install the CSC files and run the preload checkin so you don't FC all over the place
9) IMPORTANT--After flashing the sec_csc, the Note will reboot.
Try to catch it in time to reboot BACK into recovery
Once in recovery, select "Choose update from external" in the recovery, and select the 2400258.zip you downloaded earlier.
This will give you a stock MJ5 system. You can choose to stop here if you don't want to root.
10) Extract rldv.zip to the root of your internal sdcard (NOTE **my script removes Knox apps). Reboot, then once SuperSu installs, Reboot again.
This leaves you with a rooted MJ5 device.

533y4 said:
Again, I have done this 5 times. No joke. I have redownloaded everything 3 times.
Click to expand...
Click to collapse
Did you do this??
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message​

mazdamiata210 said:
Did you do this??
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message​
Click to expand...
Click to collapse
Yes. And everytime I try this again I have to delete and revert drivers, because ODIN won't see it afterwards. X_X
The drivers named "WinUSB 6.1.7600"

533y4 said:
Yes. And everytime I try this again I have to delete and revert drivers, because ODIN won't see it afterwards. X_X
Click to expand...
Click to collapse
Switch usb ports, switch usb cables, switch computers if possible.
Are you on an administrator account for windows?

mazdamiata210 said:
Switch usb ports, switch usb cables, switch computers if possible.
Are you on an administrator account for windows?
Click to expand...
Click to collapse
I will try this. I am on a ASUS G75 with Win 7 Ultimate X64 via USB 2.0 not USB 3.0. The account I am using is the Administrator. I'm also going to try and run Heimdall as Admin. I'll report back in about 10 mins.

533y4 said:
I will try this. I am on a ASUS G75 with Win 7 Ultimate X64 via USB 2.0 not USB 3.0. The account I am using is the Administrator. I'm also going to try and run Heimdall as Admin. I'll report back in about 10 mins.
Click to expand...
Click to collapse
If that doesn't work try this...
fire up zadig, connect phone while in download mode, install the driver for msm8960, fire up heimdall frontend, go to utilities tab, hit detect button, and then go to flash screen and check no reboot, then start...
I also did mine with usb 3.0 and it worked fine so I don't think that matters. Using the stock cable also.

I was in the same boat. I had to switch computers and it worked first time. Both of them were windows 8.1 btw.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Did you try changing ports for heimdall? Sounds like its not recognizing your n3, had that problem before too where after odin'ing the mj5 files heimdall wouldnt see my phone. Did a reboot on my laptop and changed ports had 7 different 2.0 cables. Just keep trying did this 5 times already and always had the same result.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

So is there no way to mount the card so that I can copy these files if I am bricked?

mazdamiata210 said:
If that doesn't work try this...
fire up zadig, connect phone while in download mode, install the driver for msm8960, fire up heimdall frontend, go to utilities tab, hit detect button, and then go to flash screen and check no reboot, then start...
I also did mine with usb 3.0 and it worked fine so I don't think that matters. Using the stock cable also.
Click to expand...
Click to collapse
Did this every single time. I also have tried all 4 USB ports. This program (Heimdall) worked the first time no problem. That's the weird part... The second and on time all is a no go.
I have attached pictures. 3.jpg is Heimdall with the error.

Have you tried rebooting your g75? Also make sure you're not running any anti malware antivirus firewall etc.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Dumb question but did you click on replace driver on the second picture you posted? The winusb driver is the one you need for heimdall frontend to detect your phone.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

posersk8r said:
Have you tried rebooting your g75? Also make sure you're not running any anti malware antivirus firewall etc.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Dumb question but did you click on replace driver on the second picture you posted? The winusb driver is the one you need for heimdall frontend to detect your phone.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Yes. I actually powered down the machine completely, removed the charger and battery, let it sit for 5 mins and retried.
Also, yes I did. That was before I did click replace tho. Good eyes. ^__^
{[EDIT]}
Does anyone have any input on the Hard Brick recovery method? The unbrick.img method? I tried it with (what I think was MJ5, but not 100% sure) a 64GB class10 UHS-1 Lexar MicroSD Card. I booted into download mode and nothing. Not sure if I did that wrong, or if the card isn't compatible, or the IMG isn't correct (anyone have any links to the unbrick.img for MJ5?)...

533y4 said:
Yes. I actually powered down the machine completely, removed the charger and battery, let it sit for 5 mins and retried.
Also, yes I did. That was before I did click replace tho. Good eyes. ^__^
{[EDIT]}
Does anyone have any input on the Hard Brick recovery method? The unbrick.img method? I tried it with (what I think was MJ5, but not 100% sure) a 64GB class10 UHS-1 Lexar MicroSD Card. I booted into download mode and nothing. Not sure if I did that wrong, or if the card isn't compatible, or the IMG isn't correct (anyone have any links to the unbrick.img for MJ5?)...
Click to expand...
Click to collapse
Well it's not bricked because you can boot into download and recovery mode. It sounds like it's just a driver issue with heimdall.

mazdamiata210 said:
Well it's not bricked because you can boot into download and recovery mode. It sounds like it's just a driver issue with heimdall.
Click to expand...
Click to collapse
I'm going to try my girls computer tomorrow after work. See if her crappy Toshiba can do any better.

My Phone is DEAD
I was talking on my phone yesterday and it just shut off and hasn't been back on since. It is not responding to anything i try. Power + Vol down + Home. When i plug it up, there is no sounds or vibration no response. The phone is in a permanent off state. Any thought or suggestion on how to repair. I did the OTA update last week SM-N900A.

Help required: Galaxy Tab

I've been searching XDA & Google for about 1 month but can't find a solution. I don't know why everywhere in some threads whenever somebody asks the same problem there's no reply to that question. So I decided to post this question here to try my luck...
Problem & History:
I tried to root my Samsung Galaxy Tab GT-P1000R with DoonLord V_4, it couldn't root it but left the tab with touch problem then I tried to root it with famaroot various versions, I then again tried to root it with z4root V_1.3.0, all attempts were useless, I don't know which attempt of them, made my tab unable to connect to pc even in download mode.
When I set my tab to connect to Kies or Media it shows that it's connected but PC doesn't detect it. Please help...
Tab Specification:
Samsung Galaxy Tab GT-P1000 (Rogers)
Firmware Version: GB 2.3.6
Baseband Version: P1000XXJR2
Kernel Version: 2.6.35.7 ([email protected] #2
Build Number: GINGERBREAD.XXJU2

Hi adilpal, go to the first post here http://forum.xda-developers.com/showthread.php?t=1881981

Thanks!
mr.natural said:
Hi adilpal, go to the first post here http://forum.xda-developers.com/showthread.php?t=1881981
Click to expand...
Click to collapse
Thanks for your reply but I have already gone through this post but as I mentioned problem is that PC doesn't detects it even when I put the Tab in DL mode. Is there any method to root it? So that I could use Mobile Odin to restock it.

It is an usb-driver problem and not rooting, I'm 99% sure of it. It's the PC that HAS to find the Tab first.

Hmmmm
mr.natural said:
It is an usb-driver problem and not rooting, I'm 99% sure of it. It's the PC that HAS to find the Tab first.
Click to expand...
Click to collapse
I've tried on another PC and with another USB cable but in vain. Other Smartphones connect it without any problem.

Any smartphone or the P1000 are not the same. I have had on multiple occasions that even Samsung Kies did not recognise it and had to reinstall Kies. Same for the Samsung Mobile phones drivers. And don't forget to reboot your PC after installing drivers.
Keep on trying because it is still going into download mode and logic tells it should be accessible. Does the PC give a notification like driver not found or similar?

NO.
mr.natural said:
Any smartphone or the P1000 are not the same. I have had on multiple occasions that even Samsung Kies did not recognise it and had to reinstall Kies. Same for the Samsung Mobile phones drivers. And don't forget to reboot your PC after installing drivers.
Keep on trying because it is still going into download mode and logic tells it should be accessible. Does the PC give a notification like driver not found or similar?
Click to expand...
Click to collapse
No. There's no activity in PC when I connect it. It neither shows new hardware found nor any other notification like unrecognized device etc.
BTW I have reinstalled Kies, updated it, uninstalled it, installed separate drivers for Samsung USB but no gain...

One last option, let the battery become completely empty (0% charge). Recharge and try again, it rescued my tab once after a bad flash.
That is to my knowledge the last resort.

Alas!
mr.natural said:
One last option, let the battery become completely empty (0% charge). Recharge and try again, it rescued my tab once after a bad flash.
That is to my knowledge the last resort.
Click to expand...
Click to collapse
It didn't help...

adilpal said:
It didn't help...
Click to expand...
Click to collapse
What version of windows are you on? Because windows 8 is a *****, Vista or 7 should work.
(Or GNU-Linux). And have you tried Heimdall already? http://forum.xda-developers.com/showthread.php?t=1323527
Heimdall download https://code.google.com/p/heimdall-one-click/downloads/list

Get a stock ROM and how to use Heimdall (these are old instructions so there could be newer versions available).
-----------Heimdall install instructions ------------------
1. Download Heimdall.
2. Download Microsoft Visual C++ 2010 Redistributable Package (x86) and install it. Download it here List All Devices.
5. From the USB Device list chose "Samsung USB Composite DEvice".
6. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
7. Done. This only needs to be done once.
-----------How to use Heimdall-------------------------
1. Put your tab into download mode - Power off Tab, once powered down hold power and the volume down button at the same time. You will see a android digging.
2. Start Heimdall
3. Hook your tab up to your PC or MAC and you will see a progress bar. That must say Ready to get heimdall to work.
4. Find you Firmware and unzip it until you see the following files below.
(NOTE: when you first unzip your firmware it may unzip into a .tar file unzip the .tar file to get the files below.)
a. Zimage
b. FactoryFS.rfs
c. Param.lfs
d. Boot.bin
e. SBL.bin - not always included
f. cacher.rfs
g. dbdata
h. modem.bin - not always included
5. Place each of those files in their correct spot and hit start.
ONE BIG NOTE: if you use a PIT file do NOT select repartition. It might brick your tab as heimdall has a problem when selecting repartition w/ a pit file. It is ok to use the pit file just make sure repartition is unchecked.
(Use ODIN for repartition with pit)

Got it working...
Thanks buddy, I bought a half dozen of USB cables for the tab and got it working with one of them at last... I don't know but I thought it was the last way out to try different cables... And at last, I got it working after long...
Please let me know the correct way of rooting, as DoomLord v. 4 has already failed to root it. Please guide if possible... I have a Ragers (Canada) Tab. GT-P1000R

Alcatel Idol 4 6055K problem with firmware

Hello,
I have a somewhat aged Idol 4 lying here.
This no longer boots or it hangs in the boot loop.
So I tried to install an update via a stock rom from the network via the recovery menu and ADB sideload and always got the error status 7. (Alcatel_Idol_4_6055K_01001_01002_OTA)
Resetting the system didn't help here either.
Then I tried to install TWRP on the device.
But unfortunately both methods that I tried failed.
Once via Sahara & firehose-test and the second was Suger QCT via the download mode.
But both of them got the error message NPRG Error 5002.
I have installed suitable USB drivers.
So my question, does anyone have a tip for me on how I could get the device revived?
And Sorry for my bad english

Hm.. said:
Hello,
I have a somewhat aged Idol 4 lying here.
This no longer boots or it hangs in the boot loop.
So I tried to install an update via a stock rom from the network via the recovery menu and ADB sideload and always got the error status 7. (Alcatel_Idol_4_6055K_01001_01002_OTA)
Resetting the system didn't help here either.
Then I tried to install TWRP on the device.
But unfortunately both methods that I tried failed.
Once via Sahara & firehose-test and the second was Suger QCT via the download mode.
But both of them got the error message NPRG Error 5002.
I have installed suitable USB drivers.
So my question, does anyone have a tip for me on how I could get the device revived?
And Sorry for my bad english
Click to expand...
Click to collapse
Hello, I deleted my system from twr without realizing what I was doing, the result is that I stay on the Alcatel logo. My steps were, the installation of sugar, when it starts not to update the application. Choose the 6055 model, since the 6055P model that is mine does not appear in the drop-down. Before starting sugar, turn off the mobile completely and connect it off to the usb of the pc, check if when connecting it the pc does not detect it, use another cable (there are many cables that only serve to charge and not to read on the pc) Now start sugar, choose the model and click on the Udgrade tab. You will surely get several messages saying that the mobile has been modified and that you lose the guarantee, go ahead accepting the message, in a few minutes you will have it ready. Greetings.

Perdigon55 said:
Hello, I deleted my system from twr without realizing what I was doing, the result is that I stay on the Alcatel logo. My steps were, the installation of sugar, when it starts not to update the application. Choose the 6055 model, since the 6055P model that is mine does not appear in the drop-down. Before starting sugar, turn off the mobile completely and connect it off to the usb of the pc, check if when connecting it the pc does not detect it, use another cable (there are many cables that only serve to charge and not to read on the pc) Now start sugar, choose the model and click on the Udgrade tab. You will surely get several messages saying that the mobile has been modified and that you lose the guarantee, go ahead accepting the message, in a few minutes you will have it ready. Greetings.
Click to expand...
Click to collapse
Hello, thanks for the answer and the download.
I've tried the same way. I still downloaded your file and tried as you described.
Unfortunately I got the same error NPRG Error 5002 again.
Unfortunately I have no idea where the problem could be.

I found out that it could be a memory error.
As if a flash process had failed and there is no longer a correct series of partitions.
So I would need a complete original rom and would have to flash it via fastboot.
I could also try it via twrp, but I don't get this flashed.
And I don't have a complete original rom either.

Hello,
So I have now been able to flash the phone with another PC with Sugar QCT after it suddenly started up after the battery was completely empty and I charged it again.
But unfortunately the boot problem persists after turning off the phone again.
Even after replacing the battery with a new one.
Then I tried to flash TWRP via the Alcatel Flasher.
The flash process was successful but there was no TWRP on it after the reboot.
So the problem could still be somewhere else than just the firmware.

Hm.. said:
Hello,
So I have now been able to flash the phone with another PC with Sugar QCT after it suddenly started up after the battery was completely empty and I charged it again.
But unfortunately the boot problem persists after turning off the phone again.
Even after replacing the battery with a new one.
Then I tried to flash TWRP via the Alcatel Flasher.
The flash process was successful but there was no TWRP on it after the reboot.
So the problem could still be somewhere else than just the firmware.
Click to expand...
Click to collapse
Hello, it may be that you are making the same mistake that I made when installing recoveri. When selecting the recovery, note that the twr is the one that weighs about 14 mb and the original one about 24 mb. I think that when you make a copy with the recovery program and then install the twr you select it wrong. In the program, do not make the copy of the recovery, skip that step and go directly to install and select the 14 mb file. You will see that this is the problem. Cheers

Return to Stock? (SM-T813)

Howdy, folks. I have an ancient S2 running a very old version of Lineage that I'd like to return to stock and start over again. Is there a guide for this, or do I just flash the file via Odin?

BillTheCat said:
Howdy, folks. I have an ancient S2 running a very old version of Lineage that I'd like to return to stock and start over again. Is there a guide for this, or do I just flash the file via Odin?
Click to expand...
Click to collapse
Hi BillTheCat,
I just performed a return to stock on a SM-T813 myself; the steps are not that difficult. I run Odin in a Windows VM and connected the tablet via USB pass-through, but that was not a problem. The procedure that worked for me was this:
download the stock firmware for your device and copy it to the Windows machine
download the Samsung USB-Driver for Mobile Phones and install it in the Windows machine
download Odin (I used v3.13.1) and copy it to the Windows machine
power off the device (make sure USB is disconnected)
boot to download mode (Home + Vol-Down + Power)
unpack the Odin zipfile and run the executable as administrator
connect the device via USB to the Windows machine; 'Added!' should appear in the Odin log area
click the AP-button in Odin and select the .tar.md5 file containing the stock firmware (in my case it was T813XXS2BRC2_T813PHN2BRB1_HOME.tar.md5)
click the 'Start' button and wait a few minutes
if it fails the first time, simply try again. In my case, I followed these exact same steps twice and the flash finally succeeded
reboot the device and be patient for the first boot
For me, this return to stock is just a confirmation that the device itself is still working OK. I'd really like to run an up-to-date LineageOS but am having troubles with that. LOS 16 is end-of-life, LOS 17.1 gives me an unusable camera and a bootloop in the most current release (self built including may-2022 patches).
What do you plan to do after flashing the stock firmware? Are you going to flash an up-to-date ROM?
Good luck and kind regards,
FWieP