Database Info

Need solution for this Galaxy R

Hi guys...
I need your help if this problem are possible to fix it.
It happen just after received a call.. then i leave it for awhile.
After that, when I take phone.. its really heat and the screen doesnt turn on. It just like the device was turn off. So I remove the battery and put it back, and hit on button.. the appear on the screen like attached photo...
I'd tried all repair method to solve the bricked... but nothing change. It tend to the red text.
Additional info- before it happen..the phone is on taiwan firmware with ardadat's kernel 1.5 if I not mistaken...
So I really appreciate that if theres any solution before I wanted to send it to service centre.
Sent from my GT-I9003

looks like some problm wid ur lcd....

Did you try to nvflash it? Partition error..
Did this happen after you try to connect to odin and flash stock firmware?
xarolx said:
Hi guys...
I need your help if this problem are possible to fix it.
It happen just after received a call.. then i leave it for awhile.
After that, when I take phone.. its really heat and the screen doesnt turn on. It just like the device was turn off. So I remove the battery and put it back, and hit on button.. the appear on the screen like attached photo...
I'd tried all repair method to solve the bricked... but nothing change. It tend to the red text.
Additional info- before it happen..the phone is on taiwan firmware with ardadat's kernel 1.5 if I not mistaken...
So I really appreciate that if theres any solution before I wanted to send it to service centre.
Sent from my GT-I9003
Click to expand...
Click to collapse

akshatsourav said:
looks like some problm wid ur lcd....
Click to expand...
Click to collapse
well i'm not sure why its happen suddenly if lcd problem
ishafiq said:
Did you try to nvflash it? Partition error..
Did this happen after you try to connect to odin and flash stock firmware?
Click to expand...
Click to collapse
It just happen just after the phone heat..
So now, with this current condition, once i put battery on it,
it will turn on automatically and drop the red text...then get into download mode.
I try to flash it with stock firmware.. but it keep telling fail.
Message on Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9103DXKI3_I9103OLBKH3_I9103DXKH3_HOME.TAR.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Click to expand...
Click to collapse
I'd tried to use the "GT-I9103_Dead_Repair_By_Xiaoyuz", but seems like failed for that..plus, the instruction not really clear. How do I install the drive inside? It wont install once I plugged the device
Edit : GT-I9103_Dead_Repair_By_Xiaoyuz method done completely, but still occured like my 2nd attached picture.
p/s : I'm sorry for not rotate all the picture. Directly upload from my SL.

xarolx said:
well i'm not sure why its happen suddenly if lcd problem
It just happen just after the phone heat..
So now, with this current condition, once i put battery on it,
it will turn on automatically and drop the red text...then get into download mode.
I try to flash it with stock firmware.. but it keep telling fail.
Message on Odin:
I'd tried to use the "GT-I9103_Dead_Repair_By_Xiaoyuz", but seems like failed for that..plus, the instruction not really clear. How do I install the drive inside? It wont install once I plugged the device
Edit : GT-I9103_Dead_Repair_By_Xiaoyuz method done completely, but still occured like my 2nd attached picture.
p/s : I'm sorry for not rotate all the picture. Directly upload from my SL.
Click to expand...
Click to collapse
Ur download counter is zero better u give ur device in service centre. Tell them i was using phone and suddenly it gone off and not starting.
Sent from my GT-I9103 using Tapatalk 2

A partition problem huh.....
I know this sounds stupid , but can you try other .pit files ? Like the SII's or the SL's .
Ace-ing all tests.

Did u follow post 8/9? using pit file and all?
xarolx said:
well i'm not sure why its happen suddenly if lcd problem
It just happen just after the phone heat..
So now, with this current condition, once i put battery on it,
it will turn on automatically and drop the red text...then get into download mode.
I try to flash it with stock firmware.. but it keep telling fail.
Message on Odin:
I'd tried to use the "GT-I9103_Dead_Repair_By_Xiaoyuz", but seems like failed for that..plus, the instruction not really clear. How do I install the drive inside? It wont install once I plugged the device
Edit : GT-I9103_Dead_Repair_By_Xiaoyuz method done completely, but still occured like my 2nd attached picture.
p/s : I'm sorry for not rotate all the picture. Directly upload from my SL.
Click to expand...
Click to collapse

[Q] HELP WITH Galaxy Note N7000 Bricking

Sigh, so i'm back again, 2nd time messing up my phone in 3 weeks......This time its going to cost me if I don't get an answer. I bricked my phone, i tried everything, and I mean everything, and it just won't finish flashing via Odin "pc" and I can't my mac to find the Pit files because of Stupid Kies.
Anyway, what did I do again? well i flashed the abyss kernel and then immediately via CWM tried to restore my Criskelo ROM and it would not get past the boot up screen, "the one before the animation" ....i wiped cache, tried restoring my stock Rom, tried wiping dalvick cache, you name it. None of that work, the only thing i could get into at the time was CWM and Odin mode "download mode".....I continued to try to figure it out for my self, and tried repeatedly to flash via odin.....back to a stock rom and i screwed up so much more now because of that. I can't get into clockworkmod anymore....i can't get into recovery, NONE OF THAT ....Only thing i see when i put on my phone is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." ...I can get into Odin mode, but NOTHING ELSE. PLEASE SOMEONE HELPPPPP ME!. I don't know what I am going to do if i don't back my phone.
btw, if you wanted to know how far I got in the whole flashing via Odin.
It is showing this:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N7000XXLPY_N7000OXXLPT_N7000ATOLP2_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:3)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
cache.img
NAND Write Start!!
factoryfs.img
"then it gets stuck and doesn't go beyond it....turn oof the phone and then i see this"
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1):crying::crying:

You are the victim of the eMMC bug. Welcome.to the club...
If your SGN is still under warranty and your binary counter is zero, rush to your nearest samsung service center. Tell them the phone booted after the update and never started.
If you arent in warranty, try repartitioning method explained by Forest in his detailed guide @ http://forum.xda-developers.com/showthread.php?t=1661590 check the 12th post.

[Q] Phone will not turn on, will only go into DL mode.

Hello,
I have been using this site for days now and accomplished everything I have needed to so far.
I rooted and flashed about 6 roms and found the Aeon v1.4 to be the best for me regarding my infuse 4g.
I tried to install the " Unofficial CM9 rom" for the ics look and it turned my phone into a paperweight.
Symptoms:
-Phone will not go into recovery
-will not turn on
-when attempting to turn it on, i get a barely noticable millisecond flash and then nothing.
The phone, however, will go into download mode.
I tried odin and did the repartition, pit, etc..
I tried heimdal (however its spelled) and it wont recognize drivers. (i installed drivers and they worked for odin)
I basically just want to put Aeon back on my phone and actually use my phone.. nothing else. I would appreciate any insight into the matter.
Thank you very much.
Chris.

I recently had the same problem when I tried to downgrade back to GB. I used Odin to reflash my phone using this.....http://forum.xda-developers.com/showthread.php?t=1613523.....

Thanks
omansteveo said:
I recently had the same problem when I tried to downgrade back to GB. I used Odin to reflash my phone using this.....http://forum.xda-developers.com/showthread.php?t=1613523.....
Click to expand...
Click to collapse
Thanks, ill definitely give it a whirl.. I have tried many different versions of Odin and different PIT, PDA files. Most of the time it just says:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> NewStock.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> factoryfs.rfs
and sits there... stuck for like 20 min+ (currently)... no progress bar or anything. Currently, this one is PDA .tar only. No pit or anything else with only auto-reboot and f. reset time checked.
I'll definately let you know how it worked out though, thank you!

Try other usb ports & another usb cable if possible.
Sent from my SGH-I997 using xda app-developers app

use gtg ultimate unbrick
Azrael-09 said:
Thanks, ill definitely give it a whirl.. I have tried many different versions of Odin and different PIT, PDA files. Most of the time it just says:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> NewStock.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> factoryfs.rfs
and sits there... stuck for like 20 min+ (currently)... no progress bar or anything. Currently, this one is PDA .tar only. No pit or anything else with only auto-reboot and f. reset time checked.
I'll definately let you know how it worked out though, thank you!
Click to expand...
Click to collapse
You need to go back to stock. Look for it in the software part. It is the ultimate gtg unbrick. It works flawless.

OP no need to double Post Threads of the same issue, your Thread in the General Section is no longer, utilize this thread for your issues. Thank You.

Is there an average time for Odin to pass?
andros11 said:
Try other usb ports & another usb cable if possible.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I've been trying all 3 ports and decided to just stick to the on directly connected to the motherboard. Also have been using "USB Deview" to remove usb connections in order for phone to recognize the infuse drivers i unzipped and put on the desktop. Ill try another cord as well, thank you.
kenetix said:
You need to go back to stock. Look for it in the software part. It is the ultimate gtg unbrick. It works flawless.
Click to expand...
Click to collapse
I have tried that one i beleive, but my phone was originally Froyo and "GTG's ultimate unbrick" is for Gingerbread.. (GB PIT file) (it said my phone couldnt upgrade to GB when i was unrooted). I'll Try again though, couldnt hurt. Thanks.

You should go back to stock rom via Odin
When in doubt go stock
Sent from my GT-S5360 using xda app-developers app

Azrael-09 said:
I have tried that one i beleive, but my phone was originally Froyo and "GTG's ultimate unbrick" is for Gingerbread.. (GB PIT file) (it said my phone couldnt upgrade to GB when i was unrooted). I'll Try again though, couldnt hurt. Thanks.
Click to expand...
Click to collapse
Really no way to go back to Froyo. You have to now assume GB is the beginning...
Sent from my SGH-I997 using xda premium

Going stock
An1mus said:
You should go back to stock rom via Odin
When in doubt go stock
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
I would absolutely love to flash it back stock, problem is I can find good files to drop me back to stock.. or maybe its the phone, idk. I even tried files used from the dump of someones stock phone to recreate a "stock" version. Next step is trying Gtg's Ultimate unbrick again.
I'll keep you guys updated, thanks for all your help.
I dont have enough posts to be able to put in outside links but if someone needs the GTG's_Ultimate_Unbrick.zip link, i found it. )Most of the links are broken and its a pain to find) Just PM me.

Odin update
20 min into it.
Odin shows this:
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCKD5.tar.md5 is valid.
<OSM> PHONE_UCKD5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Set PIT file..
<ID:0/013> DO NOT TURN OFF TARGET!!
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> factoryfs.rfs
And phone is in DL mode with the blue progress bar showing about 1% since the beginning and hasnt moved. Odin isnt saying that its not responding or anything... any ideas?

If you want stock Froyo: http://forum.xda-developers.com/showthread.php?t=1629079
If you want stock GB : http://forum.xda-developers.com/showthread.php?t=1524081
Many thanks to qkster for this.

5 days and counting.. =(
Pony Express said:
If you want stock Froyo: http://forum.xda-developers.com/showthread.php?t=1629079
If you want stock GB : http://forum.xda-developers.com/showthread.php?t=1524081
Many thanks to qkster for this.
Click to expand...
Click to collapse
Thank you very much, I have tried those. This is my fifth day doing this and i cant seem to get Heimdall to work. I tried doing as much research as possible before posting a problem.
For Heimdall even though when it asks for drivers I can click on "Samsung usb composite device" and reflash but it just says "installing drivers" and loops over again.
For Odin its just not continuing to increase the progress bar or add anything new to the log screen.. Pretty confused at this point.
My phone is bricked from flashing the wrong rom. I dont mind which OS i go to because im going to end up flashing Aeon v1.4 again anyways since it looked and worked great.
Thanks for the links!

Update
[Well, i still cant get odin to get past the factoryfs.rfs ...
Phone is still only showing an 1/8 inch progress bar..
I keep trying Heimdall but no luck... i do not have file upload options in Heimdall though... is that normal?
If anyone has any other ideas, please share..

Here is a post I did for someone else, I hope it will be helpful to you.
http://forum.xda-developers.com/showpost.php?p=33215877&postcount=15
(The link I mention in post 13 is qkster's Heimdall link)

I'll get right on it. Thank you.

I think im missing some tar files... only thing in the video i can think of is that he mentions having odins tar files for some reason while using heimdall on-click.. I do have some files on my desktop > pit, phone and pda files but no other ones..
Also in the video it mentions the binary at the top of your screen in download mode. Mine says: Custom binary download: NO
Current binary: Samsung official
That normal for someone who flashed 6 roms?
On top of it all dev-host isnt downloading anything for me... click and click and nothing.
I think i just need some expert phone help, lol...

I just put mine in download and binary also says 'no'. I have lost count as to the number of roms I have flashed.
I think you are close but from my end I can't tell what is missing. I have used odin with no problem and yet my preference is Heimdall.
Maybe take some time and go through some of qkster's threads, including the link to his Heimdall tutorial. Some have found that they did not have the latest version of Java while others did not know that you have to use the same port you were using each time you use Heimdall. Others did not know that Heimdall has it's own drivers or that they should uninstall kies first.
Qkster may drop by this thread and if he has suggestions he will post. He has forgotten more about the Infuse than I know.

I installed then uninstalled Kies
I do have the latest version of Java.
I downloaded a binary version of Heimdall for the Zadig driver file so that i can manually put in the samsung driver before opening the one click Heimdall
I have followed tutorials to the letter so much that when i watched the video it seemed like I was knowledgeably far beyond the video's tutorial.
Im am however, unsure what you mean by using the same port (please keep in mind that im on the computer trying to fix my phone about 45 min out of every hour for about 8 hours a day for the past 5 days)... I actually had to erase all the zip files and tar files and such just to re-grasp where i was at because my desktop was overloaded...
Oh and i read a thread about bricking your phone (good read) and i think i screwed it up somewhere in the bootloaders... its not enough to hard brick it since i can still go into DL mode but something is definately wrong.
I do appreciate your advice and concern. Thank you again.
Hopefully we can come to a conclusion soon and i can pass on my knowledge...

Pony Express said:
Qkster may drop by this thread and if he has suggestions he will post. He has forgotten more about the Infuse than I know.
Click to expand...
Click to collapse
Thanks for the vote of confidence, Pony. I'm not very good at getting the drivers installed.
What you noted is all that I can recommend.
Update java. Install Samsung USB device. Install Zadig from Heimdall. Sometimes it take a reboot or two with the PC. Other times, it takes a different PC altogether. It may also work by moving the USB cord to a different usb port.
It has been almost a year since I tried Odin. No help there.
I can tell you that after you get the heimdall to work, save that cord and that usb port only for heimdall and don't install Odin over it.
With all the heimdall-1-click packages available, there are many options to restore from soft brick or return to stock.
jscott30 made a bunch of Odin packages as well if Heimdall is not working for that person.
Perseverance is the key. We have all been there. I can tell you that the more mistakes you make, the more you will learn.

Boot loop after trying to flash phone.

Hello,
I came here to look for help. I have a Verizon Samsung Galaxy s3. I rooted my phone and had CM10.2 on my phone.
I used casual to root phone/unlock boot loader and everything.
I decided I wanted to put CM11 on my phone. I downloaded everything from CM site for my phone. I made sure it was for my phone. I have TWRP recovery on the phone. put on debugging and everything.
I went into TWRP and started the process of putting CM11 on the phone. I made a nandroid back up in TWRP. I did a wipe data/factory reset.Once did all this, I went into install and installed zip file from my external sd-card. I believe it said failed, but i don't remember the exact thing that happened or the message I got. I know that doesn't help, but I am going to try and type everything I have done. Once that happened, I think i stupidly went to reboot and it said about super user rights needing to be fixed. I think i pushed fix. I know i probably did a big mistake there. The phone started to reboot.
When the phone is rebooting what happened was it would got to samsung galaxy logo and then CM logo. It would then immediately reboot. It just kept going through this cycle. So i tried to boot into recovery. It starts to attempt to boot in recovery. TWRP logo starts popping up. Boom it reboots again. So i can't get into recovery mode.
So i started to read around about my problem. I found articles saying about using odin to correct this boot loop (soft brick i think from what I read). I started to follow this article: http://forum.xda-developers.com/showthread.php?t=1840030
When I followed that article I got steps one through six done with odin saying pass. I start to do step 7. I actually tried to do step 7 twice. I got fails both times. I don't have the results form the first time. I downloaded the root66 tar file from somewhere else. I don't remember. When I got the failure, I pulled the root66 tar file i found here: http://forum.xda-developers.com/showthread.php?t=1984436 I used the main on on there. I go through and it fails: Here is the log from it.
<ID:0/005> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> root66_VZW_I535VRBMB1.tar.md5 is valid. <OSM> Checking MD5 finished Sucessfully.. <OSM> Leave CS.. <ID:0/005> Odin v.3 engine (ID:5).. <ID:0/005> File analysis.. <ID:0/005> SetupConnection.. <ID:0/005> Initialzation.. <ID:0/005> Erase... <ID:0/005> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1)
I am completely stuck on what to do at this point. I am growing tired of trying stuff and I am completely stuck. I have tried to look around, but no luck.

Have you tried Odin flashing the VRBMF1 4.1.2 stock image? You would need to root and unlock your bootloader afterwards. This file formats /sdcard as well.

I'm downloading the image right now. I will try and use it and see what happens. I'll get back to you as soon as it downloads and I run odin again.

thunderisraw said:
I'm downloading the image right now. I will try and use it and see what happens. I'll get back to you as soon as it downloads and I run odin again.
Click to expand...
Click to collapse
Cool, just do not accept the 4.3 OTA if this flashes fine and boots up for you

SlimSnoopOS said:
Cool, just do not accept the 4.3 OTA if this flashes fine and boots up for you
Click to expand...
Click to collapse
Okay i got odin to work. I got it flashed on there. thank you so much! Now i just got to unlock the bootloader again. Which I'll do real fast with casual. Thank you again for being so fast to respond!

thunderisraw said:
Okay i got odin to work. I got it flashed on there. thank you so much! Now i just got to unlock the bootloader again. Which I'll do real fast with casual. Thank you again for being so fast to respond!
Click to expand...
Click to collapse
Great! You'll have CM11 installed in no time :thumbup:
Sent from my SCH-I535 using Tapatalk 4

[Q] Brand New S5 Literally Rooted

Hey People
I posted this on S5 cf auto root tread but no one is helping me. has been 2 days
Im new here so if this is the wrong place to post delete or please point me in the right direction
I just tried rooting my SM G900I (LTE)?
Im brand new to android and thought it would be a good idea to root my phone right off the bat follow a guide off you tube using these softwares:
CF-Auto-Root-kltelgt-kltelgt-smg900l
Odin3_v3.09
Anyway it didnt work and ive just peed my pants (just a little) : have the feeling ive bricked a $500 new phone
this is what it says on the download screen with its stuck on (have tried a soft reset battery out for over a Minuit) ;
could not do normal boot
odin mode
Product name: SM G900I
Current Binary: custom
System Reset: official
Reactivation Lock (kk): off
knox warranty void: 0x1 (4)
qualcom secure boot: enable (CSB)
AP SWREV: S1 T1 R1 A1 P1
UDC Start
Ive always run it in administrator mode and have tried 2 different usb cables, one is brand new with the phone and a mates one . one of the guides I was following said to use a 2.0 cable not 3.0 im pretty sure mine are all 2.0
anyway heres some of the dialog from odin if it helps:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-kltelgt-kltelgt-smg900l.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Odin seems to think everything is fine as it says Pass in green but the phone is still stuck in download mode with the same dialog .
By the way I've tried a lot more than 4 time with the same method I think it must be stuck on (4) though

Any help would be appreciated
Thanks

You can try a couple things. From a powered off state, hold volume up, power, home button. It should boot into the custom recovery, from there you want to wipe - cache, dalvik, and see if it boots. If not, Odin back to stock and start over. You'll need to find the correct file for your phone, probably on sammobile.com.

metalfan78 said:
You can try a couple things. From a powered off state, hold volume up, power, home button. It should boot into the custom recovery, from there you want to wipe - cache, dalvik, and see if it boots. If not, Odin back to stock and start over. You'll need to find the correct file for your phone, probably on sammobile.com.
Click to expand...
Click to collapse
Thanks bro
I tried the vol up, power and home but it goes straight to the download screen its stuck on , with the : could not do normal boot. etc
If I try odin back to stock firmware with the phone stuck like this is there any chance it would work?

Yes, it will work. Basically, you would be flashing the same thing Samsung does to restore a phone to factory status.

this why i don't do experiment to my phone before this phone all my phone was root because was cheap phones

metalfan78 said:
Yes, it will work. Basically, you would be flashing the same thing Samsung does to restore a phone to factory status.
Click to expand...
Click to collapse
thanks for that man

BennyDubz said:
thanks for that man
Click to expand...
Click to collapse
You're welcome
emanuelrv said:
this why i don't do experiment to my phone before this phone all my phone was root because was cheap phones
Click to expand...
Click to collapse
There is nothing wrong with rooting an expensive phone, as long as you are prepared and have the files you need to recover from something gone wrong.

emanuelrv said:
this why i don't do experiment to my phone before this phone all my phone was root because was cheap phones
Click to expand...
Click to collapse
metalfan78 said:
There is nothing wrong with rooting an expensive phone, as long as you are prepared and have the files you need to recover from something gone wrong.
Click to expand...
Click to collapse
Yeah defiantly naive of me especially after coming from using apple not really knowing the first thing about android. although there's no info on there that mattered too much.
my only reason for rooting is so I can get an app like guardian I think its called or something similar made by XDA so I can regulate the apps I use as its pretty stupid some of the permissions you have to give to even basic apps such anything from browser history, access to contacts and caller id etc. when there is really no need.
im not paranoid I just don't believe you should give private info so readily. but im back to square one anyway haha

So you got it running?

metalfan78 said:
So you got it running?
Click to expand...
Click to collapse
Yeah seems to be working fine, is weird as nothings been wiped even text messages still there

Should I have another go at rooting it hahaha

I would, worst case scenario is you'll have to reflash original tar in Odin again
Sent from my SM-G900P using Tapatalk

Are you sure you have Auto Reboot checked?
Also......check CP, not AP. In fact, I used Odin 3.10 instead of 3.09.
Good luck.

elwood said:
I would, worst case scenario is you'll have to reflash original tar in Odin again
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
jpgranger said:
Are you sure you have Auto Reboot checked?
Also......check CP, not AP. In fact, I used Odin 3.10 instead of 3.09.
Good luck.
Click to expand...
Click to collapse
Choice, think ill give it another go