Database Users

Note 3 Bricked?

OK I used the Cf-Auto-root as per this link
http://forum.xda-developers.com/showthread.php?t=2466423
to gain root access for my device. No problems there rebooted in fine.
The problem came from when I replaced the "ro.product.model=SM-N9005 with ro.product.model=GT-I9300" in my build.prop file then used "Hide My Root" to hide the SU binary. (This I was doing to install a device specific apk as per http://ausdroid.net/2013/07/16/how-to-use-foxtel-go-on-any-device-even-if-youre-rooted/)
Went to reboot now.....
Device now gets stuck on the White Samsung GALAXY Note 3 SM-N9005 screen.
I do have a backup of the build.prop file and can still access Standard Recovery and Download mode.
What I have tried is to push the build.prop file manually via adb command from my pc with
adb remount
adb push build.prop system/
but i get the closed error when I try to do this hence why I am posting this.
Can someone help an etard out here. Am I permanently bricked here or do I have some options?
Have found my carriers rom on Samfirmwares and am assuming after it is downloaded I can just reflash it with Odin? Will I lose all data when doing so?
HEELPP! Thanks in Advance!

600538411 said:
OK I used the Cf-Auto-root as per this link
http://forum.xda-developers.com/showthread.php?t=2466423
to gain root access for my device. No problems there rebooted in fine.
The problem came from when I replaced the "ro.product.model=SM-N9005 with ro.product.model=GT-I9300" in my build.prop file then used "Hide My Root" to hide the SU binary. (This I was doing to install a device specific apk as per http://ausdroid.net/2013/07/16/how-to-use-foxtel-go-on-any-device-even-if-youre-rooted/)
Went to reboot now.....
Device now gets stuck on the White Samsung GALAXY Note 3 SM-N9005 screen.
I do have a backup of the build.prop file and can still access Standard Recovery and Download mode.
What I have tried is to push the build.prop file manually via adb command from my pc with
adb remount
adb push build.prop system/
but i get the closed error when I try to do this hence why I am posting this.
Can someone help an etard out here. Am I permanently bricked here or do I have some options?
Guessing I can flash stock rom back on BUT couldn't find one for my country on samfirmware.com...
HEELPP! Thanks in Advance!
Click to expand...
Click to collapse
i had big problems with my phone flashed this worked a charm http://forum.xda-developers.com/showthread.php?t=2461929

jaythenut said:
i had big problems with my phone flashed this worked a charm http://forum.xda-developers.com/showthread.php?t=2461929
Click to expand...
Click to collapse
I checked on that link and the PDA/CSC of the roms available did not match with what Samfirmware's said my carrier was but I was able to download a firmware from Samfirmware for my carrier.
Should I just flash this firmware using odin? Will flashing the stock rom back over replace the build.prop as part of this?
Man I am such a tard.
Thanks in Advance!

600538411 said:
I checked on that link and the PDA/CSC of the roms available did not match with what Samfirmware's said my carrier was but I was able to download a firmware from Samfirmware for my carrier.
Should I just flash this firmware using odin? Will flashing the stock rom back over replace the build.prop as part of this?
Man I am such a tard.
Thanks in Advance!
Click to expand...
Click to collapse
yeah just flash with odin should be it

I am assuming I will lose all data from doing this too?

jaythenut said:
yeah just flash with odin should be it
Click to expand...
Click to collapse
I downloaded the firmware and it is a zip file. Content of zip file is a tar.md5 and SS_DL.dll. Can i still just extract the tar.md5 and flash with odin or can I/do I need to flash in stock recovery from external sd???
UPDATE
Tried putting on sd card card flashing from recovery... says
> -- Install /sdcard ...
> Finding update package...
> Opening update package...
> Verifying update package...
> E: signature verification failed
> -- Appling Multi-CSC...
> Applied the CSC-Code : VAU
> Successfully applied multi-CSC.
>
> Install from sdcard complete.
> Applying update complete.
Unfortunately, it still hangs on Samsung GALAXY Note 3 SM-N9005 screen...
Tried wipe data/factory reset, NO DICE!
Options? Please!!!

SOLVED
Just flashed the tar.md5 from zip using odin. All worked well. Thanks JatdaNut!

[Q] S4 keeps rebooting

Hello all,
I have a S4 in my hands.
Now the history of the Phone is as follows:
Customer tried to take out the sim card by force. And broke the metal plate.
Yesterday I replaced the microsim/sim slot. Testing the full Phone and ready to go.
Today I go back to the end customer for the same device.
It keeps rebooting after the samsung galaxy S4 white screen. And keeps going.
This is what I tried:
Updating to newest rom - no luck
Plugigng in into pc by cable - keeps rebooting with only showing the battery icon.
Try to go in recovery mode - not possible
Going into download mode - works
The little smash trick of YouTube (smash to table gently with side of power button down) - don't work
Any suggestions?

So you are the employee that fixes phones and don't know what to do with a bootloop, but do know how to replace a simslot? I am somewhat confused..
A bootloop always has some cause.. check init.d script or so.
Code:
adb wait-for-device
adb shell chmod 000 /system/etc/init.d/*
at least get an adb connection and logcat,
Code:
adb wait-for-device
adb logcat -C
else you cannot say anything about the problem since you don't know the cause. (if debugging is disabled unpack boot.img and make changes in ram disk for enabling debugging/adb, then repack and reflash)
If download mode works just flash a custom recovery first, make a nandroid backup (make sure you secure the files whenever possible, since there is the nasty symlink "/data/media/" which is actually just /sdard. so if you wipe data manually it the nandroid backup will be gone), then try to do factory reset, if it doesn't work still, just reflash stock rom with odin + factory reset.
oh and for the record, the simslot being broken is not the cause of the bootloop, just that you know.

Hi,
When you say "updating to newest ROM" do you mean that you flashed stock ROM again via Odin? If not, then that's my suggestion for you, but first I'd try factory resetting it via stock recovery.
~Lord

Thank you for Your kind reply.
Yes indeed, I fix a lot, but I have and know my limits. . I've tried a lot to pass the boot loop.
But if it's not possible to fix it for me. Than its better to ask.
I will try a custom rom. And keep you informed. Thank you.

Installing a rom with odin din't help. I got na Green PASS but bootloop keeps running.
Installing CWM did not help allso, it give me a PASS, but I can't enter recovery.
So, how do I get acces to init.d ?

If recovery mode doesn't work and the device keeps rebooting, try to flash stock ROM with Odin and put the .PIT file after checking 'Re-Partition'

iJo09 said:
If recovery mode doesn't work and the device keeps rebooting, try to flash stock ROM with Odin and put the .PIT file after checking 'Re-Partition'
Click to expand...
Click to collapse
Thank you, I will try.
Can you give me a link to a stock rom with a pit file including?

The Chaser said:
Thank you, I will try.
Can you give me a link to a stock rom with a pit file including?
Click to expand...
Click to collapse
ROM and PIT file vary by model. What is the S4's one?

iJo09 said:
ROM and PIT file vary by model. What is the S4's one?
Click to expand...
Click to collapse
I have I9505

In this thread http://forum.xda-developers.com/showthread.php?t=2265477 you can find what you need. Flash the latest German XXUGNF1 firmware and use the .PIT file provided in the thread

iJo09 said:
In this thread http://forum.xda-developers.com/showthread.php?t=2265477 you can find what you need. Flash the latest German XXUGNF1 firmware and use the .PIT file provided in the thread
Click to expand...
Click to collapse
Just ready. got a green pass in odin. But still the same, and not able to go in recovery.
Maybe a hardware malfunction? Can I test that somewhere?

Retry with the same procedure a couple of times... if this doesn't solve problems, then it's an hardware fault

[HowTo] SM-G900FD with Android 5.0 Root if all seems to fail

[ Read the How To at the second post ]
Heya guys,
I just got yesterday my new Galaxy S5. I'm actually someone who is switching from the iPhone world to Galaxy.
I had a Note 2 in the past for some time and I'm sys admin so I'm a bit familiar with flashing and technical stuff.
Phone Information:
Model: SM-G900FD (or SM-G900MD?) (DuoS)
Country of Origin: United Arab Emirates
The phone came with stock rom 4.4.2. On the About Phone screen it shown SM-G900FD as model, directly from unboxing.
But when entering the Odin Mode it shows as product name SM-G900MD (which would fit the origin of course).
The first I did was downloading G900FDXXU1BNL9 (Android 5.0 SER (Russia)) and flash it with Odin. It works like a charm.
Then I tried dozen of different rooting methods, and failed every time, I spent I believe 10 hours on it already and flashed the phone about 30 times.
When flashing the stock rom, either the new G900FDXXU1BNL9 (5.0) or old G900FDXXU1ANF6 (4.4.2) it works like a charm.
The phone comes to life, Android is working fine.
As soon as I try to flash *any* other image, CWM, CF-Auto-Root or anything, it starts with "NAND Write Start!" and then in some seconds stops with "Complete(Write) operation failed." and the system ends up in a soft brick (Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.). I tried from every piece of software I could find many different versions. Different Odin versions. I tried Heimdall (Mac) and fastboot (Windows & Mac) without success. These two don't work at all with the phone. Heimdall can't correctly connect to the phone and download the PIT, I was reading its a bug with the newest bootloader of Samsung. And fastboot/adb can't see the phone, at all. While heimdall or odin can see the phone, so its not a driver issue that the OS can't recognize the phone.
I tried also different versions of CWM, CF-Auto-Root, either for SM-G900FD or SM-G900MD. No luck.
What I tried then was using towelroot, but it doesn't work with the newest Android. So I found a thread that stated to flash a old Kernel, which will give errors during booting but you can then root the phone with towelroot, and then flash the newest kernel back to the phone. I tried that, taking out the boot.img files from old and new firmware out and use a script to package them into .tar.md5 files and try to flash them with Odin. Even there, Odin reports FAIL! With the boot.img files from the stock images, which work fine flashing if I flash the entire stock image.
I tried also installing a old stock rom and try rooting it there with CWM/CF-Auto-Root. Same stuff, FAIL! flashing.
I'm a bit out of ideas right now. Does anyone ever encountered this? Or does have a hint on what could cause this problems?
Some threads I was reading (its a way more, but the list would be too long, I just add the most recent ones) and following:
[How to] Root for 4.4.2 and Flash rooted Stock Android 5.0 with KNOX 0x0?
http://forum.xda-developers.com/showpost.php?p=54745709&postcount=13
Galaxy S5 G900FD
http://forum.xda-developers.com/showpost.php?p=55994495&postcount=102
[Script][Tool] how to create a tar.md5 file from img For Odin
http://forum.xda-developers.com/showthread.php?t=2446269
Click to expand...
Click to collapse
Thank you very much for any assistance. I hope there is a possibility to root this phone
Cheers,
Sven
PS: My KNOX Warranty Void is already increased, so the warranty is killed already.

[HowTo]
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
$ COPYFILE_DISABLE=1 gtar -H ustar -c NON-HLOS.bin aboot.mbn boot.img cache.img.ext4 hidden.img.ext4 modem.bin recovery.img rpm.mbn sbl1.mbn sdi.mbn system.img.ext4 tz.mbn > image.tar
$ gmd5sum -t image.tar >> image.tar
$ mv image.tar image.tar.md5
Click to expand...
Click to collapse
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven

Well done!!
af2k said:
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Click to expand...
Click to collapse
Well done !!
i was looking for this root for my phone M-G900FD
until i read your thread ,so please upload the ready made file to root my phone as i am not experienced in this matter
waiting for your feed back
thanks

I had the same problem. I couldn't flash any other image whatever I did. And what I did was disabling reactivation lock within the settings. Worked since then.

free007 said:
please upload the ready made file
Click to expand...
Click to collapse
I will look into this tomorrow and provide a ready image for this.
AlwaysAndroid said:
what I did was disabling reactivation lock within the settings. Worked since then.
Click to expand...
Click to collapse
It didn't work out of the box at me. I checked right now within the settings and the reactivation lock is disabled already.
So we seem to face different problems. I still don't understand why flashing anything but an entire firmware is failing.

Well done indeed, would love to get my hands on your modded ROM, as in Dubai with new Duos just purchased today.
Any problems with Wifi passwords not being stored on re-boot?

af2k said:
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Click to expand...
Click to collapse
Looks like gtar needs to be installed separately.
$ brew install gnu-tar

This is what I was looking for...
I am not on OSX. Is there a possibility to get access to the modified image?

My SM-G530T is messed up...

Hi,
I am trying to install custom rom on my Samsung Galaxy Grand Prime (SM-G530T). I have tried several recoveries. The one seems to work well is this one: http://forum.xda-developers.com/gra...om-recovery-twrp-2-8-7-0for-lollipop-t3190351.
I can go into recovery but when I try to install a custom ROM from the recovery (trying to install this:http://forum.xda-developers.com/grand-prime/development/rom-lollipop-deodexed-t3241741). I get the following error:
E:Unable to mount '/data'
E:Unable to mount '/preload'
Is there a way to overcome this and install a custom rom and bring the phone back to life? I have erased everything and there is no backup. So I can't boot the phone at all now. Any help is appreciated.
Thanks,
CS71

cs71 said:
Hi,
I am trying to install custom rom on my Samsung Galaxy Grand Prime (SM-G530T). I have tried several recoveries. The one seems to work well is this one: http://forum.xda-developers.com/gra...om-recovery-twrp-2-8-7-0for-lollipop-t3190351.
I can go into recovery but when I try to install a custom ROM from the recovery (trying to install this:http://forum.xda-developers.com/grand-prime/development/rom-lollipop-deodexed-t3241741). I get the following error:
E:Unable to mount '/data'
E:Unable to mount '/preload'
Is there a way to overcome this and install a custom rom and bring the phone back to life? I have erased everything and there is no backup. So I can't boot the phone at all now. Any help is appreciated.
Thanks,
CS71
Click to expand...
Click to collapse
Can someone provide me with a PIT file for SM-G530T (T-mobile)? That might help my cause.

Have you tried a factory reset? Also, I may have a pit file for you. I don't remember where I got it from, but I think it was in a thread here. I will check when I get home later.

cs71 said:
Hi,
I am trying to install custom rom on my Samsung Galaxy Grand Prime (SM-G530T). I have tried several recoveries. The one seems to work well is this one: http://forum.xda-developers.com/gra...om-recovery-twrp-2-8-7-0for-lollipop-t3190351.
I can go into recovery but when I try to install a custom ROM from the recovery (trying to install this:http://forum.xda-developers.com/grand-prime/development/rom-lollipop-deodexed-t3241741). I get the following error:
E:Unable to mount '/data'
E:Unable to mount '/preload'
Is there a way to overcome this and install a custom rom and bring the phone back to life? I have erased everything and there is no backup. So I can't boot the phone at all now. Any help is appreciated.
Thanks,
CS71
Click to expand...
Click to collapse
First thing you do is download the firmware on your computer unzip the file you should have the tar file and pit file in the zip. Use Odin put the tar file in AP slot then the pit file in the pit box. I usually check the options

iamagrenade said:
Have you tried a factory reset? Also, I may have a pit file for you. I don't remember where I got it from, but I think it was in a thread here. I will check when I get home later.
Click to expand...
Click to collapse
Thanks imagranade. Please make it available when you get a chance...

ShineLikeMe said:
First thing you do is download the firmware on your computer unzip the file you should have the tar file and pit file in the zip. Use Odin put the tar file in AP slot then the pit file in the pit box. I usually check the options
Click to expand...
Click to collapse
Where do I download the firmware from? Can you provide me with a link please?

[how to] make .tar file with only stock recovery.img inside

Can anyone help me how to make .tar file with only stock recovery.img inside flashable through odin. Im planning to install custom recovery and I want a backup procedure to revert it back to stock recovery instead of flashing the full stock rom.
Anyone please enlighten my confuse brain cells. I read some procedure for doing that stuff but I want the procedure which really came from galaxy note 4 forums. I was thinking different devices have own specific way of doing that.

macoX13 said:
Can anyone help me how to make .tar file with only stock recovery.img inside flashable through odin. Im planning to install custom recovery and I want a backup procedure to revert it back to stock recovery instead of flashing the full stock rom.
Anyone please enlighten my confuse brain cells. I read some procedure for doing that stuff but I want the procedure which really came from galaxy note 4 forums. I was thinking different devices have own specific way of doing that.
Click to expand...
Click to collapse
Its the same procedure for all devices

Rajada said:
Its the same procedure for all devices
Click to expand...
Click to collapse
thanks. can you link a particular thread or site for doing the that.

macoX13 said:
thanks. can you link a particular thread or site for doing the that.
Click to expand...
Click to collapse
if you are in linux, do this command in terminal:
tar -H ustar -c recovery.img > recovery.tar
if wou want a md5 file:
md5sum -t recovey.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
if you are in windows install tar for windows

Rajada said:
if you are in linux, do this command in terminal:
tar -H ustar -c recovery.img > recovery.tar
if wou want a md5 file:
md5sum -t recovey.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
if you are in windows install tar for windows
Click to expand...
Click to collapse
im in windows. is there a thread for doing that so i can follow the procedure.