So earlier I made changes to my build.prop file to make it appear as a Nexus 5 to the play store (I've done this many times before with multiple devices) with my towelrooted 4.4.2 NC1 Galaxy S4. I rebooted my phone and everything worked like normal, later I decided I would change the build.prop file back to stock from my backup I made minutes before changing it. After restoring the backup, I rebooted the device and get stuck after the galaxy s4 boot screen. I can still get to download and recovery mode, but adb can't recognize my device... It does however recognize my phone when I put it in adb sideload mode but that doesn't help much but I get "error: closed"... I need my phone working for tomorrow morning so I need this unbricked ASAP. I've been searching the forum for the past 3 hours and have tried everything I've come across and nothing is working. My pc is running Windows 8.1 pro 64bit. Are there any methods that will work to unbrick this thing? I will probably try odin, but I'm having trouble finding the correct ROM.
Read the return to stock section of http://forum.xda-developers.com/showthread.php?t=2616221
Related
I have a Samsung Galaxy S4, the Sprint version. I wasn't able to send or receive picture messages and I thought it might have something to do with my APN being wrong (I bought the phone on eBay and had it flashed to nTelos, my provider) but I wasn't able to edit the APN and nTelos was, as usual, no help. So I figured I'd just root it and be able to edit it then!
It was at that moment I stuck my shovel into the soft dirt and started digging.
Essentially, I believe my phone is without an OS at this point. I have tried using ODIN to put a recovery on there so I can at least do something, but now even ODIN is freezing up when I try and flash the Clockwork recovery. I am stuck on the Samsung S4 logo screen and while I can enter download mode I don't think I can enter recovery mode - at least, it hasn't been working tonight. I don't remember everything I've done to my poor phone, but it has to be hurting after the beating I've put it through. I originally tried to root it though I don't think I was successful because the Root Checker said I wasn't, though I'm not sure what I was doing wrong then. Things went downhill from there.
I've read through thread after thread hoping for something that would work, but I've given up trying to use other people's problems to solve my own. This is me saying "Uncle". I require assistance. Let me know what you need from me to provide me with the help I need.
Also - I have ADB on my computer and I think I have a basic understanding of how to use it, but since I can't enter recovery mode I can't do anything other than pat myself on the back for figuring it out. I think my first problem at this point is ODIN. I uninstalled KIES so that's not interfering (and don't even get me started on KIES - I installed KIES and it told me to install KIES3 which told me my device wasn't supported... which is crap because it's running Android 4.3 - or was before I got to it).
Thanks,
If you're sure the phone was on 4.3, then your options are limited thanks to Knox. You can only restore a 4.3 (MJA) based ROM to the phone via Odin, whether it is stock or custom. Easiest giveaway is if you see a line for "Knox" on the Download Mode screen.
At this point you should look in the ROM directory here for a full ROM (xxxxx.tar.md5), either MF9 (4.2.2) if it doesn't have Knox or MJA (4.3) if it does. If you cannot use Odin to put a full ROM on there, then you will need some more serious help.
Odin the stock 4.3 MJA OEM. Will return your phone to a stock unrooted state.
http://forum.xda-developers.com/showthread.php?t=2522810
Hello everyone,
i am fairly new to the world of rooting and recently encountered a problem while flashing a rom
i have the at&t samsung galaxy note 3 N-900A running 4.3 jellybean (2 year contract expired and i got and used the unlock code)
i rooted the phone using the kingo root app, because i could not update the phone (I recently moved out of the USA so i cant connect to an at&t server to update)
i installed safestrap recovery 3.71 and it was running fine
i found a tutorial from galaxy note 3 root for the knoxraid ro
(put youtube. c o m here) /watch?v=8HDHt4xSnQY
according to the tutorial i had to install the rom over the stock rom file
so i copied the stock rom to rom slot 1
this is where i messed up, i installed the knoxraid rom over the stock rom without wiping/data factory reset first. But it gets worse, i realized i forgot to wipe the data from safestrap so before the install was even halfway completed, i pulled the battery out.
now whenever i turn it on it will go straight to recovery mode
it wont even turn off. i have to pull the battery out.
i can get to download mode and recovery mode but thats it.
im not sure about the build number because it wont boot up
all i can tell you is it is a at&t note 3 running 4.3 jellybean
please help if you can
btw: my computer wont recognize the phone because it says the PHONE does not have the correct drivers installed
however odin still recognizes it with the blue box with 0:[COM6] if that helps
so yeah please help me the phone is fairly new and i dont want to waste $600
infinitephase said:
Hello everyone,
i am fairly new to the world of rooting and recently encountered a problem while flashing a rom
i have the at&t samsung galaxy note 3 N-900A running 4.3 jellybean (2 year contract expired and i got and used the unlock code)
i rooted the phone using the kingo root app, because i could not update the phone (I recently moved out of the USA so i cant connect to an at&t server to update)
i installed safestrap recovery 3.71 and it was running fine
i found a tutorial from galaxy note 3 root for the knoxraid ro
(put youtube. c o m here) /watch?v=8HDHt4xSnQY
according to the tutorial i had to install the rom over the stock rom file
so i copied the stock rom to rom slot 1
this is where i messed up, i installed the knoxraid rom over the stock rom without wiping/data factory reset first. But it gets worse, i realized i forgot to wipe the data from safestrap so before the install was even halfway completed, i pulled the battery out.
now whenever i turn it on it will go straight to recovery mode
it wont even turn off. i have to pull the battery out.
i can get to download mode and recovery mode but thats it.
im not sure about the build number because it wont boot up
all i can tell you is it is a at&t note 3 running 4.3 jellybean
please help if you can
btw: my computer wont recognize the phone because it says the PHONE does not have the correct drivers installed
however odin still recognizes it with the blue box with 0:[COM6] if that helps
so yeah please help me the phone is fairly new and i dont want to waste $600
Click to expand...
Click to collapse
Well, this is the wrong forum to begin with.
However, head over here, http://forum.xda-developers.com/showthread.php?t=2703006 , and read very, very carefully.
sirobelec said:
Well, this is the wrong forum to begin with.
However, head over here, http://forum.xda-developers.com/showthread.php?t=2703006 , and read very, very carefully.
Click to expand...
Click to collapse
sorry, next time ill post in the right forum
thanks for the link, however this appears to be for the N900AUCUCNC2 variant, which i believe is KitKat (sry if im wrong) i need files for 4.3 jellybean firmware. (i never updated)
thanks in advance
Hello,
I've got (had) an SM-G900W8 running the XtreStoLite v2.0 LP BETA5 ROM on the XXU1BOA3 kernel. I installed TWRP 2.7 via Odin, and left the latest modem and bootloader updates I got through KIES3.
At which point I got the chance to sell the handset on Kijiji, provided I could get the stock ROM back on.
I downloaded the latest Odin (3.09) and the correct Firmware for my handset from sam mobile, and factory reset the device. I pulled the battery, let it sit, and tried to flash once I got it back up in download mode, and it wouldn't work.
This isn't too much of a surprise to me, because since I flashed TWRP, Odin hasn't ever worked for me. Regardless of how many times I've tried to flash the modem and/or BL that XtreStoLite asked me to use in their how to thread, it wouldn't work. I was willing to ignore it b/c the ROM worked with the modem and BL it was running.
My problem is that once I tried to reboot, the system hung at the BL animation. I went back into recovery, and tried to move my backups off my external storage (I had 2 back ups that were about 2 or 3 gigs each, too much for the local storage) to the local card and restore (b/c TWRP won't restore from the external card) and the back ups failed.
Now I've got the BL screen, but it won't advance to the animation, and it won't boot to TWRP either.
I tried to restore from KEIS, but it says my device isn't supported by KIES 3 (it is). I could really use a hand here. Every time I try something this gets worse. I'm no pro, but I've had no problem figuring this out on my old HTC handsets.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
HI all,
So I today I messed up and I need your help :crying:. Basically here's whats going on: I decided to root my phone since I found that battery was complete garbage, so I decided to root the phone with TWRP and Odin and after flash a new kernel for my phone as well as SU. Everything went fine. However, when i tried to reboot my phone to get a custom rom i wanted, it keps telling "kernel is not seandroid enforcing" and would be stuck in a boot loop (which apparently is normal and would just need to flash a rom for it to work). Finally I just decided to boot factory, so I can get to my files and put that damn custom rom. Long story short, I was able to put it, wiped system in TWRP and flashed this new rom only to get another error "THis package is for device trltetmo, this device is trltexx". Now I couldnt even factory reset anymore. At this point I decided to flash my back up that I did before and yet ANOTHER problem "cannot restore system mounted read only". After couple of hours of research, I needed to change the name of the file to system.image.mbn i think, I changed a file called system.ext --> system.image.ext. Needless to say that it didnt work. Final thing I decided to do is simply to flash a stock rom with odin and reverse the root, so I downloaded a stock rom for note 4, started the whole process with odin and now it is stuck at system.img.ext4....and i have no clue what to do, I dont know even know what I did before is the problem or it is something else, all i know is that odin is stuck at that message. Should I just let it go, should I stop it? Help! please
Wow, true hardship you get it back running?
Try using Kies and doing firmware upgrade mode to see if it can download and load the stock firmware for that device.
Hi, I've been reading the thread for CF auto root to give it a go. I've downloaded the drivers (I've got 1.5.51 now installed, haven't been able to find later ones), I've got the 2.74 SU version that helps to overcome a recent security policy update issue reverting root status and the CF auto root zip file (CF-Auto-Root-hero2lte-hero2ltexx-smg935f.zip) which has odin 3.10.6 included (not quite sure if I can use any recent odin version). I even got my stock firmware com sammobile and extract the proper boot.img from the AP* file (just in case I got something wrong at sometime). I've enabled the OEM unlock too on developer options. I understand I can give it a go without having to go with a custom recovery (still not sure and haven't got the whole picture about the dm-verity thingy and what effects has on the device but someone mentioned something like loosing the encryption or so). This is my first try on getting root on my s7 edge G935F (international version), so it shouldn't have any boot.img problem (but trying to be prepare since I can't go about without my phone being working).
So, I've got my phone into download mode, started odin, loaded on AP the tar.md5 file from the CD auto root zip file (CF-Auto-Root-hero2lte-hero2ltexx-smg935f.tar.md5), connect the device throuhg usb cable and I was expecting Odin to recognize it but nothing happens. Since in the threads I've been researching for s7 edge there is no indication on waiting to see something happening on ODIN (but in some other threads - not s7 edge related though - mention something about having to see a blue indicator on COM), I'm not quite sure if I'm expected to just hit start even if no apparent change is happening on ODIN nor there is some drivers installing/configuring when connecting the device on download mode. Since I'm quite new to this, I'm no sure if I should connect the device first with some other option enabled, like USB debugging or if I'm missing something quite obvious for someone familiar with flashing with odin?
Kind regards for any help!
PS. I did tried to find an answer through searching but foung nothing related s7 edge wise so I'm at a loss not even knowing if just hitting start without having the device recognized on ODIN will do any harm at all (that newbie I am)
Try odin 3.11
Aldo plug your phone in first and than once recognised load the autoroot to ap
skinza said:
Try odin 3.11
Aldo plug your phone in first and than once recognised load the autoroot to ap
Click to expand...
Click to collapse
Thank you skinza for your reply, I did tried what you suggested and although it wasn't enough for getting it solved it helped me to know I was on the correct path and that I could use an updated odin.. finally, the problem was on embarrassing one since I went into download mode but hadn't push the volume up to get into the actual ODIN mode (too newbie of me but I was trying to follow the instructions I'd found and none were that specific - a bit afraid of messing it up). Nonetheless, thanks again for your time! Kind regards!
Edit: Now I'm rooted (thanks CF) and it took less than expected (a couple of mins or so). I didn't go the custom recovery way, so it might have been that.
cmanh said:
Thank you skinza for your reply, I did tried what you suggested and although it wasn't enough for getting it solved it helped me to know I was on the correct path and that I could use an updated odin.. finally, the problem was on embarrassing one since I went into download mode but hadn't push the volume up to get into the actual ODIN mode (too newbie of me but I was trying to follow the instructions I'd found and none were that specific - a bit afraid of messing it up). Nonetheless, thanks again for your time! Kind regards!
Edit: Now I'm rooted (thanks CF) and it took less than expected (a couple of mins or so). I didn't go the custom recovery way, so it might have been that.
Click to expand...
Click to collapse
Not a problem mate
Just fyi you will need twrp if you want to install custom roms like superman rom or echo rom etc
skinza said:
Not a problem mate
Just fyi you will need twrp if you want to install custom roms like superman rom or echo rom etc
Click to expand...
Click to collapse
Thanks again! for now I won't be going for a custom rom but wanted to be able to install a firewall to stop some apps from draining my prepaid data (limited)..
I was planning on having xposed installed but it seems I need a custom recovery for that as well.. I used to have xprivacy on a previous nexus 4 and loved I could limit some permissions that are still missing now on marshmallow but haven't got a grip yet as per the effects due to the dm-verity thing.. would you happen to know anything about it? and I was also wondering about if I do need to have the OEM unlock still enabled now that I'm rooted? (The later because I'd been robbed of my cellphones in the past - even recently a new s7 edge that didn't last me even a month and wouldn't want to let them have an easy pie on having the device available)
Regards!
I'm facing the same issue but even after going into download mode properly after pressing vol up
odin doesn't detect my s7 edge
I've installed all the drivers also
Singhathia said:
I'm facing the same issue but even after going into download mode properly after pressing vol up
odin doesn't detect my s7 edge
I've installed all the drivers also
Click to expand...
Click to collapse
Got the same issue. I'm new with this. My colleague wants me to learn and test and load Lineageos on some brand new S7 G930F devices he gave me which I have already switched to dev mode with OEM unlock and USB debugging on and the devices smoothly jumped into ODIN downloading.... mode
I also have the proper Samsung USB Driver installed. (did it several times after ODIN didn't recognize my device)
However, according to the manual, I should start up ODIN, then connect the device via USB cable to the workstation (as unsuccessful I already tried 3 workstations with Windows 7 and Windows 10) whilst having the phone in download mode... .BUT NOTHING APPEARS in the Log field and the ID:COM Box doesn't change colour and my manual says that it should.
My workstation however recognizes the devices with positive messages so I guess the drivers are good.
My co-worker gave me ODIN v3.10, but as this didn't work I downloaded and installed V3.12, but unfortunately also without any luck.
What am I doing wrong?
which OS?
S7 edge SM-G935F
Hey guys,
i tried rooting my s7 edge but after i got into TWRP my phone went into a bootloop. when i got back download mode, odin still found my phone, though everytime i tried to enter TWRP again, odin said there was a FAIL and my phone immediatly went back into bootloop. I tried to reinstall the samsung usb drivers but now odin cant find my phone anymore.
Before i screw up even more, can someone please help me? right now im stuck in download mode and odin 12, 11, and 10 all wont recognize my phone, also not if i use different cables. my windows laptop however still gives me the device found and device disconnected sound everytime i (dis)connect my phone.
any ideas?
thanks
EDIT: Okay i tried my USB 3.0 port and now odin found my phone. just weird... now i just need to solve the problem that I'm still stuck in the Bootloop but that probably doesnt belong in this thread