Database Info

[Q] Have I ruined my in law's phone? Please help

My father in law bought a new phone SGS on O2 and I offered to unlock it as I have unlocked my husbands last week (he's was on O2 as well but in 2.1 or 2.2.1 version I think-froyo?)
Before I continue may I say I know you guys out there know so much more than me and I really need your help. I really tried to help unlocking this phone and for hours I searched and read things like reboot, download mode, recovery mode, flashing, JKV and so many other words and letter that I could not understand. Very few I understood in the end but may have messed up badly (?).
Please, I need help and please treat me as if I were your mum or even grandma. Step by step in simple normal English please.
My father in law's version is 2.3.3
I tried unlocking it the way I unlocked my husband's but didn't work after looking for hours I thought that the best way to do it would be to downgrade from 2.3.3 (gingerbread (?)) to 2.2.1 (froyo (?)) and then unlock it.
I found this:
http://forum.xda-developers.com/showthread.php?t=1089989
and tried to follow it.
I downloaded EZRom and EZboot-Froyo-1.0.tar.md5 from the same post.
I followed:
•Download the right version from section above
•Reboot your phone into Download mode
•Connect your phone to computer
•Run EZOdin
•Select EZboot-Froyo-1.0.tar.md5 or EZboot-GingerBread-1.0.tar.md5as a PDA file in EZOdin
•Check the "Phone Bootloader Update" checkbox
•Click Start
I waited for the phone to turn off and feel the little vibration but didn't. Instead it just froze at the first screen when you turn on the phone. The black background with white letters: Samsung Galaxy...
I waited and waited and as nothing was happening I then I took the battery out. Put it back in and tried turning it on. I wouldn't it would just stop and that same screen, the black and white one.
I reread
•Wait until phone reboots and make it reboot into Recovery
SO then I remembered in the many threads I read about the recovery mode so 3 clicked vol up + button at them bottom and turn on bottom.
It gives me a few options. When I click on reboot all it does is show me the black and white screen again and nothing else. ah!!!
I took the battery off and put it back on may times, also selected the fatory reset option and tried different buttons but nothing. Please help me.
I'm happy to phone any of you guys to help me and guide me even if it's just to put the phone back to what it was before, turning on normally, etc. (I can't even turn it on!) I'm feeling really sad and a bit stressed as these days are supposed to be a nice time to spend with my little ones and family.
Anyway, please ask me anything.
Thank you so much in advance. I really hope I didn't do anything wrong and I'm just stuck because I'm ignorant in this matter. Thank you

Well, I have no skill in this area. But I wish you good luck, and this post is acting as a bump! Double goal!
After a little rethinking: (I don't have a SGS and never touched one) You can try re-stocking the phone. Not sure how you do that. I'll check.
From http://forum.xda-developers.com/showthread.php?t=723596 :
Darkstriker said:
(E) Recovery:
1.WHAAAA! I think I bricked my phone. My flash was unsuccessful/My device boots to a black screen/similar scenarios. Can I still save my device?
1.WHAAAA! I think I bricked my phone. My flash was unsuccessful/My device boots to a black screen/similar scenarios. Can I still save my device?
Most likely: YES! In almost any case, you should still be able to turn off the device (if necessary by removing the battery) and start into download-mode (VolumeDown+Home+Power) or recovery-mode (VolumeUp+Home+Power). After (for example) an unsuccessful flash, you can retry the flash in download-mode (same steps as when flashing a functioning device). If a flash to a functioning f/w (without applying any update.zip) doesn't help or you cannot get your PC to flash at all, you can ask for help here.
If you see a symbol asking you to connect to the PC, depending on how you arrived at this point, it may be sufficient to connect to the PC and run Odin (i.e. press "start" when the phone is recognized) without adding any files. This may, however, leave some residual issues if (for example) had an incorrect/incomplete flash so you may want to do a normal flash after this!
If you do not have download mode and for some ludicrous reason felt the need to go ahead and modify your firmware regardless of this lacking, there is now a guide on creating a home-made JIG which will force your device into download mode without the actual button combo here.
Click to expand...
Click to collapse
If you need any extra help, I'll try.

Im somewhat of a rookie user too but I do know this, If you can still go into recovery/download mode (using the 3 button combo) then you havent bricked the phone and you can fix it! so dont stress too much .
EDIT: Im guessing you can download a stock ROM and flash it via odin.

[/QUOTE]
After a little rethinking: (I don't have a SGS and never touched one) You can try re-stocking the phone. Not sure how you do that. [/QUOTE]
Thank u so much for your reply. O don't know what re stocking is, but i will look into it. Thank u!

I don't know how to re stock it.
Sorry to seem so dumb.
Can anyone help me step by step? If at all possible could I phone someone to help me with this? Send me phone number via private message
Thank you sooo much.

anaki11 said:
I don't know how to re stock it.
Sorry to seem so dumb.
Can anyone help me step by step? If at all possible could I phone someone to help me with this? Send me phone number via private message
Thank you sooo much.
Click to expand...
Click to collapse
Well, no problem, I guess. I don't think it needs to come to voice support, to be honest. I think text is enough for the issue in matter. I'll look a bit into this, I'll have to go soon from my computer. I'm sorry if I can't be of any greater help.

moses992 said:
Im somewhat of a rookie user too but I do know this, If you can still go into recovery/download mode (using the 3 button combo) then you havent bricked the phone and you can fix it! so dont stress too much .
EDIT: Im guessing you can download a stock ROM and flash it via odin.
Click to expand...
Click to collapse
Your post helped me not to stress too much.
I'd like to download a stock rom and flash it but I don't know how to.
Here's where I am. I found a list of firmware. This is the last one on Samfirmware.com.
Europe Samsung I9000 Firmwares.
I9000XXJVS ##
512.PIT
2.3.5
2011 September 8
CSC = I9000OXAJVS
DOWNLOAD
Things I need: (I think)
-Download a firmware (should I use the lastest one?) or 2.2 or 2.3.3? . Is there one better than the other? or is it my choice? How can I choose the best one for me?
-Odin. I have OdinMultiDownloader v4.03 in my desktop. Is that the best thing to use or should I use Ezodin. I don't know what the difference is.
-(Do I need to download or do anything else?)
Things I should do:
-Put phone in download mode
-Plug it to the laptop
-Open Odin (or Exodin?)
-click PDA. Choose the fie I downloaded-firmware.
(-after this I don't know what else I should do or tick or untick)
Am I in the right track or completely off it?
Thank you again to anyone taking the time to read this.

anaki11 said:
Your post helped me not to stress too much.
I'd like to download a stock rom and flash it but I don't know how to.
Here's where I am. I found a list of firmware. This is the last one on Samfirmware.com.
Europe Samsung I9000 Firmwares.
I9000XXJVS ##
512.PIT
2.3.5
2011 September 8
CSC = I9000OXAJVS
DOWNLOAD
Things I need: (I think)
-Download a firmware (should I use the lastest one?) or 2.2 or 2.3.3? . Is there one better than the other? or is it my choice? How can I choose the best one for me?
-Odin. I have OdinMultiDownloader v4.03 in my desktop. Is that the best thing to use or should I use Ezodin. I don't know what the difference is.
-(Do I need to download or do anything else?)
Things I should do:
-Put phone in download mode
-Plug it to the laptop
-Open Odin (or Exodin?)
-click PDA. Choose the fie I downloaded-firmware.
(-after this I don't know what else I should do or tick or untick)
Am I in the right track or completely off it?
Thank you again to anyone taking the time to read this.
Click to expand...
Click to collapse
In my thoughts, I believe that should be what you need. You can try, if that doesn't solve the issue, it's because you need something else as well.
And the think you should make the file a PDA file, I believe. Don't take my answer too direct. I'm almost unknown with Samsung devices on that matter, but I can say a couple of things, like, that, I'm pretty sure it is on PDA files.
And no problem, always pleasing to help someone in trouble. I was/am a rookie too Ignore the Senior Member thingie. Still a noob in pretty much everything. And don't panic, no need for that.

Thank you. I should try that tonight unless someone stops me before to tell me I'm about to make another mistake.

anaki11 said:
Thank you. I should try that tonight unless someone stops me before to tell me I'm about to make another mistake.
Click to expand...
Click to collapse
Haha. I doubt it. 99,99% of actions are reversible, really. And I have severe doubts that this is one of the remaining 0,01%.
Well, I wish you good luck. If you ever need any more help, you can post here. I'll look into here time to time.
BTW. Just wait a second. You know that link you give on the first post? There's also a Gingerbread file. You can *try* flashing that one, to see if it reverses the problem. Sounds legit to me.

Youtube.com/qbking77
He has tons of tutorials
Sent from my SPH-D700 using Tapatalk

[Q] big problem with sidekick

bought sidekick sght839 from friend and it worked fine b4 doing reset. now, when it starts, the tutorial comes up on home screen and can`t press arrow to proceed to next page. firmware 2.2.1-kernal 2.6.32.9-build froyo uvkj2. the wireless works and connects to internet fine. can`t use phone as 456 keys dont work and worked b4. can change settings OK. have rooted it. still doesnt want to work as b4. am new here so if someone could let me know if they have any ideas, I would appreciate it. am also new to android phones. I cant find heimdall file to download. Know how to set phone to download and use Odin but cant find proper files online.

Use the search bar on XDA to search for the kj2 stock Odin files, follow the directions given closely, download them, make sure you have the correct drivers so that Odin recognizes your phone, then boot into download mode using the method found in the forums, just do a quick search for download mode. You should have everything operational after download from Odin is finished, hope this helps
Sent from my SGH-T839 using XDA App

trouble installing odin
I have tried numerous times to install Odin but all I get is unregistered device...that is as far as it goes. Dont know how to get around that. 456 keys also work then dont work otherwise the phone works fine as far as internet and making calls goes. Crazy device!

Try this:
http://forum.xda-developers.com/showthread.php?t=1350060&highlight=heimdall
I soft-bricked my phone and this was the only method that worked.

if you havent reflashed your firmware yet, i have a suggestion. install clockworkmod recovery. there is a thread in the sk4g development section of this website. the title is something like cwm for the sk4g. enjoy! so look for that and follow the instructions in the first post of that thread. make sure you grab the update.zip file from that thread and do not flash cwm through rom manager. trust me on this. after you have followed the instructions in that thread, boot into cwm (boot into stock recovery and select reinstall packages. you should then boot into cwm recovery), select advanced, and then select fix permissions. when it finishes, it will say done. reboot your device and see if any of the problems have been fixed. i did this and it stopped my phone from randomly rebooting every 15 to 30 minutes. it might fix the problems on your device. if not, i would move to the next step, reflashing the firmware. flash the kj2 build and then learn how to remove bloatware. kj2 is less buggy to start with. still buggy, but less buggy than KD1, KG2, or the other version (KI2?). if you reflash firmware, you will need to re-root in order to remove bloatware. removing bloatware is key for optimal performance with the stock firmware. you can also flash a custom rom if you wish. most of the custom roms on this site have minimal bloatware, so if you wish to go that route, bloatware shouldnt be much of an issue. i personally am on the stock firmware and dont suggest flashing roms for someone so new to android. but if you feel confident enough, thats your decision. i also suggest booting into cwm and running fix permissions after removing bloatware. i theorize that removing system apps causes permissions errors similar to registry errors in windows.

some success with sk4g
don`t know how or why but I got frustrated with the phone and threw it in the trash on top of coffee grounds...changed my mind and pulled it out and cleaned it and charged it and...voila...it worked. banged it against the sink a couple times. weird! so, now I am trying to install custom rom and keep running into everification error when I try to flash. 456 buttons still dont work and cant take a video with it but it will probably work better if I can find a work-around for these errors I get. I am on a mission now and I cant give up. Hope someone can help me. I think there may be hope for this thing. Thanks for whatever help I can get.

i told you, install clockworkmod and fix permissions. it will probably fix the problems you are having. if you choose not to listen, thats. your choice. but my advice will probably help you without having to through the pain in the rear of reflashing the firmware. reflashing the firmware itself isnt really that difficult, but once you do it, your back to square one with your device. starting from scratch is the frustrating part. i bricked my phone and had to reflash, and it took me a couple weeks to get the phone where i needed it again. im staying on the stock firmware for this reason.

how does one fix permissions
OK OK dont yell. How do I fix permissions? Newbie on board here so I need a little more help than the rest. I dont necessarily want to do the rom thing myself. Thanks.

copy and paste this into your browser: forum.xda-developers.com/showthread.php?t=1124453 and follow the instructions in the first post. after you have followed those instructions, boot into recovery mode. the stock recovery will apear. scroll down and select reinstall packages. the clockworkmod recovery should boot up. the text in the screen will be orange. scroll down and select advanced. scroll down again and select fix permissions. when it finishes, it will say done. reboot your device and see if you have any of the issues you were having. i am not guaranteeing this will fix the issues, but i think it might. if it doesnt, my next suggestion will be reflashing the stock firmware. but try this and post back when finished and let me know if it works.

sk4g problem
didnt work. did exactly what you said and no go. any other suggestions. it works so well for some things like wifi and calling except 456 buttons on and off. it is funky indeed. thanks for the help also, cant take video or manage photo or use front camera as the left side button to choose options doesnt work either. seems like something is up with the rom. cant install anything from samsung or tmobile as it is an unregistered phone.

were you able to boot into clockworkmod recovery?

boot up
yes I did.

then you need to reflash your firmware. you need odin, you need the samsung vibrant drivers, and you need the firmware files. do a search on odin in the dev thread for this device and you should be able to find everything you need, including instructions.

Have tried that too
have the drivers, have odin and have tried that too. that didnt work as the phone is unregistered and not recognized. it is used and I cant register it.

on your phone, go to settings>about phone and scroll down to where it says baseband version. the last 3 characters under that will say either kd1, kg2, or kj2. if its not kj2, then i have a suggestion for you. but post back and lmk.

phone setting
it is kj2. now what? this is all confusing as it has been updated I believe by previous owner. thanks for your time. i am going to try the odin method again. i first did it on a 64bit puter with windows 7 so i can try it on my 32bit machine. have read that sometimes odin doesnt work well on 64bit. am willing to try anything. will let you know. thanks again. cant get the stock rom download anywhere. will just try flashing custom rom.

you cant odin a custom rom unless the dev makes an odin file, which they usually dont. you have to flash through clockworkmod. you can head over to the dev section and pick from many roms that are listed. follow the developers instructions for flashing very carefully or you will brick your device.

Thanks for advice.
I know I can`t odin a custom rom. I can`t seem to odin anything on this machine. I have cwm and have tried using it to flash a rom but I keep getting everification and such error msgs. Gonna let it sit for awhile and think about this. I have the update.zip file on sdcard but can`t seem to get that to install no matter what I do. Very puzzling deal. Thanks anyway for your help.

do you have android sdk installed on your computer? google it and install it, then try odin again.

got sdk
sdk installed and will try odin again...seems a little more complicated than the last time I tried...will google a bit more on this. Thanks.

A: Having Problems Rooting the Note Pro 12.2 SM-P900/905? TRY THIS!

**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!
3. Using your USB 2.0 cable and ports Install the Custom Rom "P900XXUANB3-RecoveryImg.tar" FIRST and flash it via ODIN 3.07 under the PDA checkbox that is "fixed" (so you noobs don’t make any soft bricks if this is your first attempt at rooting), and only use the ODIN 3.07 THAT COMES W/ CHAINFIRES AUTO ROOT .zip file and then unzip the folder to open ODIN 3.07 ONLY! This is only because I have read that there have been issues installing the SU via Chain Fires Auto Root Process... the file is called (currently as of 25 JUNE 2014) "P900XXUANB3-RecoveryImg.tar" PDA select it and then start when in DOWNLOAD MODE on your device. Manually select DOWNLOAD MODE if you have to BEFORE PRESSING START! Otherwise, one is just going to sit there and not accomplish anything.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
http://forum.xda-developers.com/attachment.php?attachmentid=2591159&d=1392930654
http://forum.xda-developers.com/attachment.php?attachmentid=2775098&d=1401644348
4 Reboot back into DOWNLOAD MODE. Flash in ODIN 3.07 with the PDA section and select this file next to install: "openrecovery-twrp-2.7.1.0-v1awifi.img.tar"
5. In DOWNLOAD MODE and flash the file under the PDA box TWRP (OR CURRENT RECOVERY OF YOUR CHOICE THAT IS AVAILABLE)
6. AGAIN... Restart your device into DOWNLOAD MODE via ODIN 3.07 and select PDA and then finally root this: "CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5" Then you can backup, restore, flash anything, and be happy! YOU SHOULD FINALLY HAVE A SUCCESSFUL ROOT! Turn off and REBOOT into RECOVERY to see if TWRP stuck and then reboot to see if the SU stuck. IF everything stuck reboot back into TWRP to flash whatever rom is available MAKE SURE TO BACK UP EVERY FILE BEFORE YOU FLASH ANY NON-STOCK ROMS. If not successful rinse wash and repeat until it does!
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
7. That’s it you should have root and a custom rom and recovery if you followed these instructions for flashing via ODIN 3.07 and Chainfires AutoRoot files. If you still have an issue repeat until root/recovery/Rom sticks. If you have to update the Binary for the SU just go to the Google Play Store and install the app and then try it again till it works. GOOD LUCK it worked for me this way!
**IMPORTANT**
BACK UP BACK UP BACK UP BACK UP after every flash that is possible to back up. If you can, back up the NON-SU stock ROM BEFORE installing SU, after installing the recovery and/or back up.
***IF I HELPED YOU OUT THANK ME***
DISCLAIMER - all research was observed via comments on the thread according to issues people have been having during ROOTING the device I simply have compiled the data and made a check list!

Need a link to the files you mentioned.

Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?

sstea said:
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
Click to expand...
Click to collapse
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.

Spere said:
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Click to expand...
Click to collapse
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks

sstea said:
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
Click to expand...
Click to collapse
You can always flash stock firmware via odin

I was just wondering if everyone was having a much easier time with achieving root now? Kies caused me to "Hang" a lot during the Root and custom rom to stick w root... as of right now i can not get the only ONE custom ROM that looks promising, i have found by GWatts (correct me if i am wrong and i apologize if i have typed the wrong screen name handle) i believe his handle is... at this point im not sure what i am doing wrong as of yet but im sure i am missing a step or i just need to start back at unroot back to stock firmware and try and try again lol. not saying anything is wrong with his work at all by any means because people other than me with the same device have gotten it to stick and im just wishing i could as well because its sweet looking ROM! NOT TO MENTION THE ONLY ONE THAT IS OUT (that is which i know about. i haven't been on in a few months idk), SO KUDOS TO WATTS i just haven't been successful at installing his custom rom just yet... Im hoping that its just going to need to be erased again and then reformatted after a factory reset and what not, i pray it sticks because his incorporation of the aroma installer was a nice touch and his ROM really looks good... Now if i can just get it not to stick at samsung boot logo and freeze id be good lol!

sanvara said:
Need a link to the files you mentioned.
Click to expand...
Click to collapse
ok

I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.

pnuker said:
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
Click to expand...
Click to collapse
**Edit**
I went back and reflashed the twrp file and it got me out of the error screen. I installed supersu, and then re-flashed the cf-auto-root file, and it worked like a charm. I'm not sure if it was the installation of supersu, or just repeating the process that fixed it, but I'm happy either way...

Thank you! I succesfully rooted my SM-P900 after all mentioned problems ( hanging in the cache.img and after a while a disturbed screen etc.) with your guide. I am a very happy rooter now.

Thanks,
Thanks to the poster. I tried rooting with the instructions from a few other sites and thought I bricked it,
Followed your instructions, and presto.. Rooted! :good:

Rooted!
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!

your welcome!
frankiecxyz said:
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
Click to expand...
Click to collapse
your very welcome! it took me a bit to get it down but i eventually figured it out and at the time information on rooting the device was hard to find with this specific model. then i discovered what the issues where and felt the need to post it! im glad i could help!:laugh:

Flash SU with TWRP not ODIN
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !

soft bricked
Hello!
First of all let me say that I'm a complete newbie, this is my first android device. I tried to root my SM-P900 (P900XXUANI1) using an online guide (image with URL attached, as I am not allowed to paste URLs)
Unfortunately at Step 10 (flashing with Odin) the operation failed and now I ended up with a soft bricked device (I assume this is the correct definition). It will only show the message asking me to connect it to KIES to recover it.
I know i can try to use KIES 3 and restore it, but before that i would like to ask if there is any alternative which will allow me to unbrick the device without losing all my data... (yeah i know...).
If i follow this guide will this help? I'm not sure if I can even put the device in download mode again as it shows the error message about connecting it to KIES...
At this point I don't care about rooting, I just want to unbrick the device.... I understand the guide up to (and including) step 3. But for the rest of the steps I'm lost Could anyone please explain them in a bit more detail? I don't want to install any custom firmware, just to unbrick it...
Any help would be very appreciated!
Thank you

Yemble said:
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
Click to expand...
Click to collapse
Have you got a link to the odin rwrp 2.7 you used and the su 2.7 flash for twrp please?

VenomousViper said:
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!.......
Click to expand...
Click to collapse
When i trying root, my SGN freeze in "cache". Odin show error and tablet goes to Emergency Firmware Recovery. Аnd it does not matter what program I use and how I do it.

Mine Reboots Constantly
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.

sunnykhs said:
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
Click to expand...
Click to collapse
Have you cleared dalvic cache and cache in TWRP recovery? Be forewarned the process takes a while for cache wipe.
Sent from my SM-P900 using Tapatalk

[Q] Recovering an n8010 from the leaked and locked n8000 kitkat

First, I am not an expert. I cannot code, I do not produce ROMS in a kitchen. I can use google and I am determined and have learned bits. I offer what worked for me in the hope of helping others.
So, here’s the thing. Like others I went for the release version of KitKat for n8000 and by missing out the modem bit flashed it via Odin. Now the proper KitKat for n8010 comes out but it won’t update via odin, KIES is not happy either. I blame no one but me for this.
I figure it is the sboot that is the problem so I look for a way to flash without it. When I say “I figure” I mean I have put two and two together from many hours of google reading. I may be wrong but in the end I managed it.
Long story a little shorter I find Heimdall and I extracted the components from the n8010 kitkat update (I used winrar on the BTU version) and flashed them leaving out the sboot.img and tz.img bits as either would lead to failed flash. I now have a working n8010 with KitKat which under device, under settings, gives the n8010 build number and is recognised as an n8010 by kies.
It still says n8000 under download mode (due to locked sboot) but if I may get future updates via kies, as it recognises it as an n8010 and says it is up to date for now, then that works well enough for me.
Detailed instructions:
1. Download and unzip your update file of choice and extract the tar.md5 file to separate files. I used winrar but suspect 7-zip would work equally.
2. Download Heimdall (just Google it!).
3. Unzip Heimdall and you should have several files in the folder called Heimdall.exe, Heimdall-Frontend.exe, QtCore4.dll, QtGui4.dll, Readme.txt and drivers folder containing zadig.exe.
4. Run zadig.exe from the Drivers folder of the Heimdall Suite.
5. If you get an error as follows:
The program can't start because MSVCP100.dll is missing from your computer.
This means that you haven't installed the Microsoft Visual C++ 2010 runtimes. Download Microsoft Visual C++ 2010 Redistributable Package (x86) and install it. Use the x86 even if you are running 64 bit Windows.
6. Put you tab into Download mode (while the tab is OFF hold Volume Down + Power Button). Hook the tab up to you PC.
7. Once you’ve started Zadig.exe and connected to PC choose Options » List All Devices from the menu.
8. Select Samsung USB Composite Device or MSM8x60 or Gadget Serial or Device Name from the drop down menu. (If nothing relevant appears, try uninstalling any Samsung related Windows software, like Samsung Windows drivers and/or Kies).
9. Click Replace Driver (having selected "Install Driver" from the drop down list built into the button).
10. If you are prompted with a warning that the installer is unable to verify the publisher of the driver, select Install this driver anyway. You may receive two more prompts about security. Select the options that allow you to carry on.
11. You will need to re-install the Samsung drivers later if you want to run kies.
12. Run Heimdall-Frontend.exe.
13. Hit the utilities tab then detect button.
14. If it doesn’t say detected in the output box it will not work. Try to repeat the above steps. Use a different usb port or a different pc.
15. Now you need to create a pit file. Hit save as and give it a name. Then hit download and it will create a pit file for you.
16. Go to Flash tab and hit browse and find the pit file you created earlier.
17. Then hit the add button. You will notice a drop down menu has appeared next to partition name. Then if you look below under Partition ID in brackets it says what sort of file it needs. So for example MD5HDR in the drop down requires md5.img. Use browse to find the relevant file from the files you extracted in step 1 and select then hit add again. Then repeat this until you have selected all the extracted files EXCEPT sboot.img and tz.img.
18. Hit start.
19. Bask in your new updated n8010 without needing kies or odin.
If you want to repeat this on another tab you can create a heimdall install package using the partitions and pit file you’ve created using the create package tab.
Now comes the question...
I've found places that offer an app for testing whether the sboot is locked (not sure how useful that is?) but several also offer a method for replacing a locked sboot. Such as this batch file:
@ECHO Restore OLD BOOTLOADER N7100!
@pause
@ECHO --- STARTING ----
@ECHO --- WAITING FOR DEVICE
@files1\adb wait-for-device
@ECHO --- Restore BOOTLOADER ---
@files1\adb push sboot.bin /sdcard/sboot.bin
@files1\adb shell su -c "dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1"
@files1\adb shell rm /sdcard/sboot.bin
@files1\adb reboot fota_bl
@pause
There are others for different Samsung devices but all have the same block/mmcblk0p1 as the block to replace the sboot. And I also found a common block for the tz.img; mmcblk0p2. My question is whether this would work for the n8010, could we edit this batch slightly, grab the relevant files from a n8010 kitkat update and then have a n8010 sboot again?
Just hoping someone is either expert enough to know or brave enough to try?

I was thinking on a different aproache.
Using the leaked firmware as a guide and UK firmware. Change the sboot.bin and the tz.img on UK firm to that one on the leaked. And try to flash trough Odin.
Enviado do meu OT-995 através de Tapatalk

That may also work.
What do you think of my suggested method to replace the sboot?
jika23 said:
I was thinking on a different aproache.
Using the leaked firmware as a guide and UK firmware. Change the sboot.bin and the tz.img on UK firm to that one on the leaked. And try to flash trough Odin.
Enviado do meu OT-995 através de Tapatalk
Click to expand...
Click to collapse

azureus139 said:
That may also work.
What do you think of my suggested method to replace the sboot?
Click to expand...
Click to collapse
Your method works very well for me. However, we need to find someone willing on XDA to find a solution to revert the bootloaders to N8010 from N8000.

I am downloading the gtn7100 kitkat and will extract to check whether they are the same size. That should get us one step closer. I am still not brave enough to use adb to replace the sboot until someone more expert can comment on whether it is likley to be same address on the n8010.
YOSEFE said:
Your method works very well for me. However, we need to find someone willing on XDA to find a solution to revert the bootloaders to N8010 from N8000.
Click to expand...
Click to collapse

In a tar file isn't something like the updater script like in a flashable zip. Cause if there is we should know with that where the sboot is flashed.

that batch file won't do it
Decided to give it a try after further research.
I learned what the different commands did and I made an edit of the batch file. All seemed to go well replacing the sboot and tz but it didn't work, still showing as n8000 in download mode.

azureus139 said:
Decided to give it a try after further research.
I learned what the different commands did and I made an edit of the batch file. All seemed to go well replacing the sboot and tz but it didn't work, still showing as n8000 in download mode.
Click to expand...
Click to collapse
perhaps that can help
http://forum.xda-developers.com/showthread.php?t=1944858

Sadly that will not help. I have discovered it is because the leaked n8000 kitkat rom has a knox bootloader which cannot, as far as I can discover, be replaced. Thank you for the suggestion.
ivica81 said:
perhaps that can help
http://forum.xda-developers.com/showthread.php?t=1944858
Click to expand...
Click to collapse

secure boot key is what your looking for
From past devices with SECURE.. NOT LOCKED boot loader.
This new knox boot loader is locked.. And im assuming.. that its locked with a SBK.. Secure boot key.. We had this issue back with the acer a 500. Where we could sign and flash a custom rom. If rom / android version was same or newer then the Versions set in the Secure boot key.
EVENTUALLY Someone found a way to Turn off that sbk . but this was only to those who had not yet flashed the sbk secure boot loader. So if today someone finds a fix for this.. It will ONLY Help those not in your situation . I think PEOPLE Should start screaming at and Protesting samsung that you DO not want there sbk boot loader as default on all devices and you should be able to remove it. But i can tell you. its a waster cause. and this device is not popular enough for someone to break up a the boot loader to get the sbk algorithms . LOok up the old threads ON THE ACER A500 Tablet.. you will see its Quite similar .
SO you are Likely STUCK...
Sorry . this is why i have NOT Flashed one of these roms on my n8013.. I will NOT Be in this situation..

Well I was already out of warranty so that isn't an issue and I have it working with the proper kitkat for my device so tbh I don't know what difference it really makes. It shows n8000 in download mode and I will have to do something tricky via heimdall for any future updates, is that the only difference? Does it mean no access to custom roms as so far I've been happy to use stock and remove all bloat so that won't be too bad for me personally although it would be a real pain for some.
erica_renee said:
From past devices with SECURE.. NOT LOCKED boot loader.
This new knox boot loader is locked.. And im assuming.. that its locked with a SBK.. Secure boot key.. We had this issue back with the acer a 500. Where we could sign and flash a custom rom. If rom / android version was same or newer then the Versions set in the Secure boot key.
EVENTUALLY Someone found a way to Turn off that sbk . but this was only to those who had not yet flashed the sbk secure boot loader. So if today someone finds a fix for this.. It will ONLY Help those not in your situation . I think PEOPLE Should start screaming at and Protesting samsung that you DO not want there sbk boot loader as default on all devices and you should be able to remove it. But i can tell you. its a waster cause. and this device is not popular enough for someone to break up a the boot loader to get the sbk algorithms . LOok up the old threads ON THE ACER A500 Tablet.. you will see its Quite similar .
SO you are Likely STUCK...
Sorry . this is why i have NOT Flashed one of these roms on my n8013.. I will NOT Be in this situation..
Click to expand...
Click to collapse

As i said i never flashed that on my device. I am thinking all the issues/ benefits quarks of having the n 8000 boot loader on a non n 8000 device.. There may be NO Disadvantage unless Samsung Chooses to change how they sign there roms and so on.I just think Samsung Should Give us a way to avoid this .

so would we be best to wipe data before doing this? just still have all the n8000 icons in the top corner like data icon etc.

I did no wipes and just flashed over the top. All apps and data as before but no phone icon.
JamesEsh said:
so would we be best to wipe data before doing this? just still have all the n8000 icons in the top corner like data icon etc.
Click to expand...
Click to collapse

Any news on restoring the n8010 bootloader? Would a jtag service be able to restore it?

raducux said:
Any news on restoring the n8010 bootloader? Would a jtag service be able to restore it?
Click to expand...
Click to collapse
Nothing from me. Everything I found says no way to unlock or replace the kitkat sboot. The n7100 apparently has a way but none for the 8xxx that I have found. Don't know what a jtag is?

fail to finish
azureus139 said:
Firstly, great guide
Extremely happy you made this guide.
I'm getting stuck though at the download on Heimdall
Either getting: Initialising connection... Detecting device... Claiming interface... Setting up interface... Initialising protocol... ERROR: Protocol initialisation failed! Releasing device interface...
OR
ERROR: Failed to send data!
really wanting to get my tablet back up and running as I only had it for a few days before i tried to update it/brick it with n8000
Just wondering if you can create a package in Heimdall or upload pit files as i'm struggling to make to get through.
thanks heaps!
Click to expand...
Click to collapse

If you can't get heimdall to detect your tablet then it isn't going to flash to it either so a pit file wouldn't help you. It looks like a driver problem. I'd try uninstalling any samsung drivers and / or kies then reinstalling the heimdall ones.
keevo2481 said:
azureus139 said:
Firstly, great guide
Extremely happy you made this guide.
I'm getting stuck though at the download on Heimdall
Either getting: Initialising connection... Detecting device... Claiming interface... Setting up interface... Initialising protocol... ERROR: Protocol initialisation failed! Releasing device interface...
OR
ERROR: Failed to send data!
really wanting to get my tablet back up and running as I only had it for a few days before i tried to update it/brick it with n8000
Just wondering if you can create a package in Heimdall or upload pit files as i'm struggling to make to get through.
thanks heaps!
Click to expand...
Click to collapse
Click to expand...
Click to collapse

This driver is too tired
Thought that could be the issue as it changes every time I reinstall the usb driver. Currently too tired. Going to do a fresh windows or Linux install on my spare computer so it's fresh to go and hopefully doesn't have driver issues. Will confirm how it goes either way. Computer needed an upgrade from 7->8.1 anyway.

wifi problem
hy guys i just did that the guide said everything is working very well i m on 4.4.2 stock samsung. But the WIFI is not working. :crying: can you help me how to fix?

Is this bricked

I seem to be in and endless loop of hope and despair with my Samsung Galaxy S7 - can anyone shed any light on this?
Long story short, I was on Android 8 and wanted to roll back to 7 (using a ROM I took from Sammobile) because I needed a previous configuration of Google Play Music for my Smart Watch to work. I used Odin to flash the phone and it declared the procedure as FAILED. Now I can't seem to even flash it back to version 8. It is just stuck on the below three screens, no matter what I do.
At this point I would happily just upgrade it to whatever firmware will work and not have a £500 brick on my hands!
Please note the images are at h t t p s ibb.co slash the below (sorry this forum doesn't allow me to post them as links!)
JcwK0vK
55F2cSf
B3Js056
Thanks
Charlie

phikal2013 said:
I seem to be in and endless loop of hope and despair with my Samsung Galaxy S7 - can anyone shed any light on this?
Long story short, I was on Android 8 and wanted to roll back to 7 (using a ROM I took from Sammobile) because I needed a previous configuration of Google Play Music for my Smart Watch to work. I used Odin to flash the phone and it declared the procedure as FAILED. Now I can't seem to even flash it back to version 8. It is just stuck on the below three screens, no matter what I do.
At this point I would happily just upgrade it to whatever firmware will work and not have a £500 brick on my hands!
Please note the images are at h t t p s ibb.co slash the below (sorry this forum doesn't allow me to post them as links!)
JcwK0vK
55F2cSf
B3Js056
Thanks
Charlie
Click to expand...
Click to collapse
OK i've seen them, don't panic.
What region / country are you
What network are you on?
p.s. YOU CANNOT DOWN GRADE OFFICIAL FIRMWARE

I'm with O2 in the UK.
I'd be happy just to get anything installed on it at this point. At least then it's useable.
Whenever I try a new flash (even with Oreo obtained from Sammobile) it just gets nowhere. The COM shows connected (I have the USB drivers installed and have ditched Kies) and I browse to the extracted AP file then click start it either goes away indefinitely not showing failed or success or (with another AP file e.g. for older firmware) it just says Failed.
Thanks very much.

phikal2013 said:
I'm with O2 in the UK.
I'd be happy just to get anything installed on it at this point. At least then it's useable.
Whenever I try a new flash (even with Oreo obtained from Sammobile) it just gets nowhere. The COM shows connected (I have the USB drivers installed and have ditched Kies) and I browse to the extracted AP file then click start it either goes away indefinitely not showing failed or success or (with another AP file e.g. for older firmware) it just says Failed.
Thanks very much.
Click to expand...
Click to collapse
Ok you have to down load the firmware that was on the device from O2, so download O2 Oreo from sammobile or the unbranded BTU firmware and flash with Odin. This should give you access to the device but the google account needs to be bypassed and then wiped by following this method https://www.progeeksblog.com/frp-bypass-apk/

Ok I'll give that a go. Wow pretty detailed guide there. I've not heard of the frp bypass requirement. Another thing to get my head around. Why can't phones just be like PC's. Image them, clone and be done!
Thanks again will let you know how I get on.

Restoring to the BTU firmware posted here forum.xda-developers.com/galaxy-s7/how-to/galaxy-s7-flat-oreo-firmware-download-t3785309 worked! In my case I didn't even need to run the frp-bypass-apk. Turns out that my phone was restored to exactly as it was before I attempted to downgrade so I even have my data back.
Thanks so much for helping me out!

Brilliant. Now to save yourself a world of pain in future turn on OEM unlocking in development options.

Just a couple more questions if you don't mind?
1) What is OEM unlocking
2) Do you know of any way to "roll-back" my version of Google Play Music? I am currently running version 8.14.7427-1H and would love to return to an earlier one since it handles the Android Wear playlist differently.
Thanks!!

phikal2013 said:
Just a couple more questions if you don't mind?
1) What is OEM unlocking
2) Do you know of any way to "roll-back" my version of Google Play Music? I am currently running version 8.14.7427-1H and would love to return to an earlier one since it handles the Android Wear playlist differently.
Thanks!!
Click to expand...
Click to collapse
Well there's some settings on the phone itself which, when you mess up trying to flash etc makes life a whole lot easier to bring your phone back to life. A good explanation of OEM is here https://www.quora.com/Whats-an-OEM-unlock-in-Android
With regards to rolling back Play music yes you can almost always roll back an updated app either by uninstalling the update via settings>apps or finding an earlier version of the .apk file online by simply searching for it in google.
When downloading .apk files, to be able to install you have to enable "install from unknown sources" settings>security>unknown sources.
Hope this helps

Brilliant. Thanks I will give that a go.