Ok, so i've spent a few hours at this already but let me give as much info as I can. I have read through many threads searching for info. I am no expert but I have had OG Droid, Incredible, and currently Thunderbolt all rooted so I am a novice.
This is my GFs phone and was previously bone stock, never rooted, no Roms nothing. So she gets the update recently and clicks yes and that is where the trouble began, phone constantly reboots and will not go past the language/activation screen. It never once went past that first screen, and she tried the hard reset and the battery pull.
So this is where I took over. I retried the hard reset (power + vol down) and also the battery pull. I also tried to activate in numerous other languages, all cause a reboot.
As per
http://forum.xda-developers.com/archive/index.php/t-1208713.html
I was finally able to get past the activation screen and make some progress. However after about a minute the phone always reboots, no matter what it is doing. I hard reset in the settings menu and that did nothing.
I next followed
http://forum.xda-developers.com/showthread.php?t=1326347
and got the phone rooted.
Installed
http://forum.xda-developers.com/showthread.php?t=1144951
and than installed CWR 4.0.0.4 ? (not sure the version whatever it comes with) Tested recovery and it it seems to stick even after rebooting several times, which the phone automatically does (maybe its a feature and not a flaw?) So I was unsure of what version of Android was even running because the phone will not allow me to go into about phone it always force closes *com.android.settings* but I figure what the heck and try my luck with a new Rom. I decided on
http://forum.xda-developers.com/showthread.php?t=1326542&page=11
So I did the usual. Rebooted into recovery, made a nandroid backup, wiped data, cache, davlik and even did /system for good measure. Than did the install and upon first boot all the same problems are there. It will not activate from the screen, it just reboots the phone eventually. I used the same method above to avoid the screen and now it will boot up and the phone is in fact running an AOSP Rom but it still reboots after about a minute. Oddly enough it also continues to refuse to let me open About Phone, in the settings menu. I also for good measure went into recovery and wiped everything again and also tried fixing permissions in recovery, all to no avail.
At this point I am thinking it is perhaps just a hardware issue, although the phone does not reboot itself in recovery. I would be willing to try a different Rom, however I don't think it would work. I am wondering if anyone has any other suggestions? Should I try this?
http://forum.xda-developers.com/showthread.php?t=1120062
Other info:
What does work is wifi, so i can get on the internet briefly. I can connect to google and get apps from the market.
I am leaving this for a few hours or I may have to re-title the thread "How do you put the LG Revolution back together after throwing it against a wall?"
Currently I'm sad face that you rooted and installed cwm but I think the update bricked it personally. Hopefully S.Meezy will see this as he has stock recovery. I would say just get back to bone stock and get it replaced. If anyone else knows how to get it fixed, my best guesses would be mt or S.Meezy, though adb that might work. I hope it all gets figured out. Someone needs to post stock GB without data or anything for people to flash to if need be. That might fix your issue.
My suggestion is to get the recover the whole phone...
http://forum.xda-developers.com/showthread.php?t=1211295
follow that but use the v6 TOT file. That will revert the phone to out of factory new, with updated radios. If you still have the issue then I would contact Verizon.
If everything works then you can re-run the update to Gingerbread.
Could be a long shot but I remember seeing something a little way back in another forum where a user w the same problem accidentially resolved his issue by restarting w the sd card out. For him it turned out to be a bad or incompatible sd card at the root of the problem.
If you have one in, pull it and restart. Hope thats it for you...
Sent from my VS910 4G using XDA App
Well i'm a glutton for punishment so i'm back.
I didn't want to bother with rooting it honestly but I did it out of desperation, figured a total wipe + brand new Rom would surely fix things.
Going to attempt the full recovery.
Tried pulling the SD card, than just the Sim card and finally without anything and none of the combinations worked.
Have you tried downloading a stock ROM to your PC/Mac and dropping that on your SD card and then flashing that ROM, after checking the md5? To me it sounds like your gf just had a bad download.
I think the issue is that you keep trying to flash the bad bits. Just my two cents...
Sent from my Dell Streak 7 using Tapatalk
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Haxcid said:
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Click to expand...
Click to collapse
What he said.
Remember: Absolutely do not, under any circumstance, unplug/turn off your phone once you start that process. It can take awhile, and might look like it froze, but just let it do it's thang.
Hi, I f_cked up.
Firstly, I've spent a few hours looking around the internet (including this forum) for answers but I can't find any so sorry if this has been answered (but I doubt it, I f_cked up pretty well).
My biggest issue at the moment is that, whenever I try and start my phone I get the error: "Unfortunately, the process com.android.phone has stopped" and I'm stuck in a constant cycle of restarts, unless I take my battery out. There is also other problems, but I'll tell you how I kept screwing up my phone.
So, I got my new phone, rooted it, all good. I deleted a bunch of system files I didn't need (not com.android.phone). I then decided I wanted the LWP Picker and a few other stupid little things back just to mess around with them, but for some reason the backups in RootUninstaller weren't working so I went looking for the APK's instead, none of which installed correctly.
Since my phone was pretty new and didn't have much data or apps on it anyway, I decided I'll reset it, without making a backup of course. Only problem is, once it deleted all my apps, it also deleted my Google Keyboard (der) which is no problem, except I f_cking deleted the Samsung Keyboard with RootUninstaller, so, errr, I couldn't do anything - including connecting to wifi or logging into my google account - oops.
So what do I do? I'll flash the ROM. I basically followed the instructions on a "theunlockr" website /2013/09/17/how-to-flash-a-custom-recovery-image-on-the-samsung-galaxy-s4-active/ - it's a .com and couldn't post direct links 'cause I'm new. No, I didn't do a custom.
So, basically, yes, I'm screwed. Can anyone help? Very urgent problem.
PS: Sorry if this thread seems rushed... it is.
Since I haven't really gotten a reply, I think I might have a unique problem. Does anybody at least have a nandroid backup or some other way to return the active to it's original form? Thanks again !
Have you tried Odin?
GT-i9295(i537) running SafeStrap
yankeesfan714 said:
Have you tried Odin?
GT-i9295(i537) running SafeStrap
Click to expand...
Click to collapse
I'm a bit of a noob at this (hence the problem). I used Odin to root the device and also to put CWM on it, but I don't know if I can use Odin in any other way? I also used tried to follow this thread /showthread.php?t=2395242 but the ROM wont transfer to my SD Card for some reason so I can't flash it using CWM. Any other suggestions? Trying to find another Micro SD Card I can use, but is there anything else i could do?
FIXED!!!
So basically, my phone is now in a working state again! I follow the CyanogenMod 10.2 (the thread I put above) after buying a new SD Card and it's working great so far! While I didn't really get much help in this thread, it was this forum that saved my arse so thanks! Hopefully I'll hang around a bit more
Okay, so.. Excuse me in advance if I'm in the wrong section of the forums, because this is the only Exhibit section I can find.. And also excuse me for the length of this post, as my problem is a bit detailed.
Long story short, I had issues with my texts not being received. I tried wiping the phone and re-rooting (using root-stock found on this website - I can link if need be?).. Anyway, I went so far as to do a factory data wipe, which clearly wasn't a very good idea (I'm a bit new at this root business)..
Anyway, I ended up to the point where I'd reach the Android Setup Wizard, and start to go through it and it would crash.. Upon reboot, the phone would completely freeze at the second "SAMSUNG" logo (the white lettering). After this, I tried using odin to just flash the stock ROM to the phone via the PC, but neither the PC nor odin actually "see" the phone. (I have the drivers, but PC reads the phone as "USB Hub" for some reason) I moved on to other things...
I used bluetooth to put cwm and root-stock back onto the internal memory after removing my external SD card, and flashed cwm no problem. Everything was going well, and it even said it installed the root-stock (I did a data wipe beforehand).. Upon reboot, I now reach "Samsung Galaxy Exhibit 4G" logo, and it continually reboots in a loop. I can still access recovery mode, but I don't want to proceed any further without some outside input, considering I don't fully understand what's going on.
I'm aware that the phone seems to be "soft-bricked," because before I flashed cwm and root-stock, it was "working" in terms of being able to receive calls (and make them, after opening the contacts from inside a call), as well as send and receive texts via the notification bar. But the weirdest thing is, before I went the route of re-flashing the root/cwm, it wouldn't show me a homescreen of any kind, I couldn't use my menu button, and my home button was pointless to touch because it went nowhere. It was just a black screen (not a background, but completely black void) with a statusbar at the top.
Anyway, I'm currently stuck in a boot-loop and I'm very curious if there's any way I can fix this phone without using odin, because the phone isn't recognized by it or a PC, so I'm stuck using the device itself to do things. I'm VERY hopeful that someone takes the time to read this and offer any input they can, because I'm currently without a device and I have no means of getting another phone at the moment.
Thanks in advance for reading this, and for any input that you guys have to offer. Hopefully some day I'm not so noobish at this >.<
Ok, I know you've said you wiped but try this then reboot. In CWM wipe data/cache and under advanced wipe dalvik. Also if you have a working CWM you can flash rooted community ROM or flash to stock found here http://forum.xda-developers.com/showthread.php?t=1686384 scroll down till you see them. But wipe 3x don't know why some people need to but try it.
Note: a working cwm can flash any custom ROM with root pre-installed and you should be fine if you wipe the three I mentioned 3x format system under mounts and storage and format internal sd works wonders too.
Sent from my SGH-T679 using xda app-developers app
---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------
If you need more help feel free to send me a pm
Sent from my SGH-T679 using xda app-developers app
Dvarl said:
Note: a working cwm can flash any custom ROM with root pre-installed and you should be fine if you wipe the three I mentioned 3x format system under mounts and storage and format internal sd works wonders too.
Click to expand...
Click to collapse
If I do a format of system or internal SD, I won't lose the ROM or CWM off of the system storage? If I lose these, I have no way of putting them back on the phone because I was doing it via bluetooth and the phone doesn't boot in order to do that anymore - The same applies to using a different ROM, sadly >.<
Also, I've already wiped the dalvik and cache several times, because that was the only way I could make the phone boot into a mode I could access anything at all on previous to installing the root again. I haven't tried doing this again as of yet, but I will do so and report back.
Just some extra information, because it wouldn't allow me to do so (being new and having to wait):
When I rebooted after the format (to the original stock rom/recovery, and even from recovery) it gave an "invalid argument" for /preload, saying it was unable to be accessed. It also said it couldn't access tmb/csc/system.. I'm unsure what these actually are, but I'm under the impression they may be at the route of my problem. Will formatting repair or otherwise help with these items being unable to be accessed?
Formatting internal will get rid of ROM, but not recovery. You'll be fine if you wipe system and reboot (ed: need to install a rom before reboot).
Try putting your ROM.zip on your external before wiping internal by mounting USB storage and copy ROM to external, then wipe internal and install ROM.
Formatting system (twice) didn't help anything at all - Still gets stuck at Exhibit logo and reboots after about 30 seconds.
Same thing with wiping dalvik/cache, even after 4-5 wipes of each. Should I be rebooting recovery after each of these?
I can't mount usb storage to PC, because PC doesn't recognize the device when I plug it in afterward (or even before mounting). It hasn't recognized the device for quite some time, but it used to act as if it were plug & play when I purchased it, and even well into the time it was rooted. A few months back, I installed the drivers for it (found via Google and ultimately this website), which didn't help it recognize the device. It only recognizes the device when in the "MTP" mode, which allows me to access and transfer data without issues(and I can't do this without being able to access the phone to turn it on ). Otherwise, it says "USB Device Not Recognized - One of the USB devices attached to this computer has malfunctioned and Windows does not recognize it"
I already have the ROM on my PC, but without any means of transfer back to the phone, removing it from internal storage would mean I have no physical way of accessing any ROM in order to restore my phone to working order. I'm at a loss as far as this is concerned, because I have the drivers installed. I'm unsure whether the phone itself is damaged, but I hope this isn't the case and that there's a way to resolve this issue directly.
My biggest concern isn't really the PC not recognizing the device, apart from needing it if I remove the ROM. My main concern is getting the thing to actually boot beyond the logos.. But if I remove the ROM, how will I put it back when it doesn't load to be able to bluetooth anything, and the PC doesn't recognize what it is?
EDIT -
I just realized something... Mounting USB storage doesn't seem to matter as far as moving the ROM, because I can just move them around via the external SD using CWM to flash them - But this is assuming that CWM will remain on the phone after formatting internal SD. Will it stay? If so, I'm going to try rooted community ROM, because the root-stock gives me the impression that it does nothing but apply root. The thread states "otherwise no changes to your phone," which implies (to me) that it doesn't actually include anything the phone needs in order to operate - It only changes certain things to apply root access... Not sure if this is true or not, but it would help explain what the heck is going on.
OH MY GOD! YOU GUYS ARE AMAZING!!
Thank you SO, SO MUCH for helping me. My device is no longer a useless paperweight :good: :good: :good:
I wish I could click the "Thanks" button a thousand times!!
Just incase anyone else has this issue and is able to access notification bar, this is what I did from beginning to end, without all the nonsense between times:
1) Turn Bluetooth on
2) Transfer Clockworkmod via bluetooth to internal SD. ((Tip: Use a separate android device to do this, if PC isn't capable) If already installed skip to step 4)
3) Re-flashed Clockworkmod
4) Place Rooted Community ROM (found here) onto external SD and insert SD into device.
5) Boot device into Custom Recovery (CWM)
6) Wipe cache/dalvik (I did it 4-5 times, just to make sure it was clear)
7) Format system AND rom AND SDCard (internal ONLY - I did all 3 times just to be sure)
8) Flashed Rooted Community ROM from external SD card (it takes some time to install - It will say when completed)
9) Rebooted phone via Custom Recovery - When clicking this, be sure to select NO when it asks to fix the root. I clicked "YES" the first time and it DID NOT FIX THE PHONE. It got stuck in another boot-loop.
10) Initial boot took a bit longer than usual (which is normal), but afterwards, I no longer have a phone that's soft-bricked.
I just wanted to say THANK YOU GUYS VERY, VERY MUCH. You've saved my life by helping me sort through this! Very, very appreciative and I hope both of you have a wonderful day :good: :good:
Good to know. I think you may have lost PNP from a windows update by samsung. To get that back, uninstall those drivers and look for 1.3.2410 or here if interested.
Still the same issue. Device isn't recognized with normal MTP (just plugging into the USB), and it acts as if I haven't even plugged it in at all when trying to use "Mass Storage" from the Network settings in the phone.
I just direct installed the drivers from the exe. Am I doing something wrong?
Try another port, cable, or machine. It worked before, so it could be a driver or something physical.
ed: When you're booted into your rom, can you change storage connection to ums? cwm might be mass storage instead of mtp.
Also, are you able to receive texts now?
I'm able to do everything the device is supposed to do out of the box, aside from access MTP.
I only have the one PC, and all ports have pretty much the same reaction to the device. I don't have access to another cable, because I only have the one that came with the device.
Mounting USB Mass Storage through CWM gives the same result on the PC "Device Not Recognized" etc, etc.
Not even ten days later and I've had to re-flash the ROM. The device kept turning itself off and back on again, so I decided to just remove all the programs I'd installed, thinking something I installed was causing an issue. After doing so, the device kept crashing. Not a reboot of the device or anything of the sort. Literally everything would pop up saying " ----- has stopped responding" and ask to force close. Not really sure what could've caused that, considering I've only installed things that were on Google Play, but it gave me the impression that I had an app that wasn't working correctly with the ROM on the device.
I've brought it back to "vanilla" and I'm not going to bother installing anything at all on it for a while and see if the issue comes up again. Not sure if anyone else has had this problem before or not, but I figured I'd just give my two cents since I made this thread with intentions to figure out what was going on with my phone. If anyone has any insight as to why this may have happened it would be greatly appreciated so I can avoid it happening this time. I'll report back if the issue comes up again, or becomes persistent.
Thanks again for all of your help, and sorry if you've wasted your time reading this.
EDIT -
Device still reboots randomly, but I suspect it's a stuck power button. Is it possible that it just needs cleaning? Sometimes it reboots, sometimes it comes up with the option to power off after touching the power button to activate the touch screen, then upon pressing the back button, it reboots several seconds later as if I were holding the power the entire time.
Stuck in boot-loop help!!!
Carefully followed instructions, and carefully selected 2 .zip files for my t679 http://click.xda-developers.com/api...4G - xda-developers&txt=<b>root-stock.zip</b> and http://forum.xda-developers.com/showpost.php?p=26860509&postcount=4 installed cwm successfully, but after installation of root-stock.zip system reboot now stuck in "boot loop" now what?
- zCHEMDAWGz
Following this in its entirety means you've wiped your phone's system clean. You'll have to use something other than root-stock, because that specifically states that it changes nothing other than granting root access. Everything that was on the phone from the factory is what root-stock uses, apart from giving you root access for things like Superuser, firewalls, etc. In this case, none of the stock items are present.
I used Rooted Community ROM. It's pretty much the same as root-stock, but it has a few goodies (BootyCall, and I think Busy Box) included. There are several other roms you could use, so you're welcome to look around a bit instead of just going with that one, but using that one for now would give you a working phone again until you find another you may like more.
BobScramit said:
Following this in its entirety means you've wiped your phone's system clean. You'll have to use something other than root-stock, because that specifically states that it changes nothing other than granting root access. Everything that was on the phone from the factory is what root-stock uses, apart from giving you root access for things like Superuser, firewalls, etc. In this case, none of the stock items are present.
I used Rooted Community ROM. It's pretty much the same as root-stock, but it has a few goodies (BootyCall, and I think Busy Box) included. There are several other roms you could use, so you're welcome to look around a bit instead of just going with that one, but using that one for now would give you a working phone again until you find another you may like more.
Click to expand...
Click to collapse
good call, community rom resolved this issue... now the only item left is the original problem - wifi/bluetooth "error". most of the easy fixes have already been attempted, aside from determining definitively if hardware issue.
Was the error your reason for rooting? (or re-flashing a rom)?
Are you running the phone completely vanilla now? (no apps, no app updates, even of "stock" applications?) If not, you should try running it that way and testing the wifi and bluetooth prior to updating or installing things.
If it were something you installed that caused a software or hardware issue, it would've most likely been something you installed a day or two beforehand.(When it broke the first time.) If you suspect it was a specific app, stay away from it (or them) in the future.
Considering that you're running a newly flashed rom, it's a little odd that the bluetooth/WiFi unctionality would error, unless it were a hardware issue. The rom you're using shouldn't affect either of those negatively, even if the phone were bricked and you managed to repair it.
BobScramit said:
Was the error your reason for rooting? (or re-flashing a rom)?
Are you running the phone completely vanilla now? (no apps, no app updates, even of "stock" applications?) If not, you should try running it that way and testing the wifi and bluetooth prior to updating or installing things.
If it were something you installed that caused a software or hardware issue, it would've most likely been something you installed a day or two beforehand.(When it broke the first time.) If you suspect it was a specific app, stay away from it (or them) in the future.
Considering that you're running a newly flashed rom, it's a little odd that the bluetooth/WiFi unctionality would error, unless it were a hardware issue. The rom you're using shouldn't affect either of those negatively, even if the phone were bricked and you managed to repair it.
Click to expand...
Click to collapse
The WiFi error existed prior to my ownership. I have never got it to function at all, except for when I was first programming the access point names settings for new mobile network, and fiddling with the other settings in the area, it did show my LAN, allowed me to attempt connection then failed the process early stage. It seemed logical that a new system would alleviate any antagonistic action executed by any previous owner. The only certain detail was it had not been rooted. I have been told loading custom Rom is 2 birds deal, freshness and increased control. Also, based on the behavior of the device and pop-up error messages that indicate software failure makes it seem related to software hiccup. but just a hunch. Been wrong before, really don't want to tear down phone but am open to learning something new. Thanks
- zCHEMDAWGz
I truly have no idea why the software would have any issues that arose directly after installing the new rom.
The only thing I can really suggest is using cwm to wipe everything several times prior to re-flashing the rom again, but I'm guessing you already did that. On the off chance it were hardware related, it probably wouldn't actually give error messages, so I'm gonna retract that from this entirely as it's very unlikely.
If you haven't, wipe your internal memory, system, cache/dalvik. Just in case, be sure you remove your external SD so you can keep the rom on it. Also, while you're at it, remove everything else except the rom from the external SD in case something on it is causing the issue, then try to re-flash the rom.
BobScramit said:
I truly have no idea why the software would have any issues that arose directly after installing the new rom.
The only thing I can really suggest is using cwm to wipe everything several times prior to re-flashing the rom again, but I'm guessing you already did that. On the off chance it were hardware related, it probably wouldn't actually give error messages, so I'm gonna retract that from this entirely as it's very unlikely.
If you haven't, wipe your internal memory, system, cache/dalvik. Just in case, be sure you remove your external SD so you can keep the rom on it. Also, while you're at it, remove everything else except the rom from the external SD in case something on it is causing the issue, then try to re-flash the rom.
Click to expand...
Click to collapse
Followed instructions, still having same issue... also the problem was there before I flashed New rom. I'm stumped...
Well, it being there before flashing the rom is a start, but that doesn't really explain why the new rom wouldn't have fixed whatever the issue was. I'm assuming (because I honestly don't know) that bluetooth and wifi are both controlled through the same hardware, with different softwares running them on the device. If both of them are messed up and refuse to work even after a re-flash, chances are it's just dead.
Have you actually formatted system, cache, etc after wiping, prior to a new flash? I had to format mine several different times in order to stop the boot loops and crashing. It could be something that's stuck in the system, cache, etc that didn't go away with a simple wipe. Other than that, it very well could be a hardware issue.
If it is a latent issue maybe doing full wipes through adb is the next step. I remember reading some people had some issues with doing wipes through cwm. It might be worth a try at the very least.
Sent from my SGH-T679 using XDA Free mobile app
I have a note 3 that I'm trying to get Cyanogenmod 11 on to. I should note that I got this working with my Droid Razr earlier today using the exact same process. I get to the point where I flash the rom and it only takes like 5 seconds then says "successful". When I boot the rom I just get a black screen that I have to hold the power button down to get out of. My note 3 is running 4.4.2 I have root and busybox is installed. I've tried safestrap 3.72 and 3.75. I've even tried the stock slot (and then reverted back when it didn't work). I'm out of things to try and I can't find anyone else who has had a similar issue. Anyone got any ideas?
If its an N900A or N900V, you can only run TW based roms because the bootloader is locked.
andygev35 said:
If its an N900A or N900V, you can only run TW based roms because the bootloader is locked.
Click to expand...
Click to collapse
How are people getting cyanogenmod 11 on their att note 3s if not through safestrap?
I don't know of anyone with an at&t note 3 running CM. It's possible they're using an N900T, or an N9005 Note 3 on at&t.
andygev35 said:
I don't know of anyone with an at&t note 3 running CM. It's possible they're using an international note 3 on at&t.
Click to expand...
Click to collapse
Well that's sad. I'm assuming any of these will work in the meantime? http://forum.xda-developers.com/note-3-att/#romList
They should, just make sure if you're on KK to choose a KK rom.
noob over here needing help
i have the ATT Note 3 with the locked bootloader. i cant rememeber the model name but i think its like I900A. anyway i have had it rooted for about 5 months or so and i have had safestrap and busybox and use Xposed wanam. also using twrp and titanium backup. well i have never flashed anything on it cuz ive always been sketched out with the locked bootloader and not being able to flash kernals and all that. so yesterday i figured i would try one out and see if i could get it. i used the "S5 Experience" rom and i downloaded it from MEGA onto my ext. SD under a new folder i made called "s5 experience". i then went into recovery mode through safestrap and went to "backup" and then made a backup of data, cache, and system. after that i went to "wipe" and did a factory reset/wipe. when that was done i went to "install" and found my "s5 experience" on my ext. SD and installed it. when that was done i rebooted my device and it popped up with the samsung note 3 emblem and under it the little lock underneath it in the unlocked position just like it always has. then went to safestrap with the little red robot and "safestrap: disabled" like always. so i hit continue and from there is when my problem started. the blue LED light on the top left turned on and stayed on but the screen stayed black. this is the problem i am still having right now. if i press the power button it will vibrate or double vibrate and eventualy if i hold it down i can get it to restart. after that i went into recovery again and tried to restore from my backup i had made just earlier. when i try that it goes for a while and then will eventually say that restore has failed. ive mesed with some of the settings and stuff in the twrp recovery interface but not much because im new and not sure what i should and should not be doing. so i started looking here. i didnt find any help on the S5 Experience forum and i havent found and other forums that have this problem except maybe this one. so i am asking for help, if someone would be so kind as to walk me through how to fix my phone and what i did wrong it would be greatly greatly appreciated. if at all possible i would love to keep all of my pics and apps and stuff but if that is not possible then i wont complain if i have to lose it all. i would be happy just to have a working phone again. thanks in advance and sorry if i have posted this in the wrong place.
sethers said:
i have the ATT Note 3 with the locked bootloader. i cant rememeber the model name but i think its like I900A. anyway i have had it rooted for about 5 months or so and i have had safestrap and busybox and use Xposed wanam. also using twrp and titanium backup. well i have never flashed anything on it cuz ive always been sketched out with the locked bootloader and not being able to flash kernals and all that. so yesterday i figured i would try one out and see if i could get it. i used the "S5 Experience" rom and i downloaded it from MEGA onto my ext. SD under a new folder i made called "s5 experience". i then went into recovery mode through safestrap and went to "backup" and then made a backup of data, cache, and system. after that i went to "wipe" and did a factory reset/wipe. when that was done i went to "install" and found my "s5 experience" on my ext. SD and installed it. when that was done i rebooted my device and it popped up with the samsung note 3 emblem and under it the little lock underneath it in the unlocked position just like it always has. then went to safestrap with the little red robot and "safestrap: disabled" like always. so i hit continue and from there is when my problem started. the blue LED light on the top left turned on and stayed on but the screen stayed black. this is the problem i am still having right now. if i press the power button it will vibrate or double vibrate and eventualy if i hold it down i can get it to restart. after that i went into recovery again and tried to restore from my backup i had made just earlier. when i try that it goes for a while and then will eventually say that restore has failed. ive mesed with some of the settings and stuff in the twrp recovery interface but not much because im new and not sure what i should and should not be doing. so i started looking here. i didnt find any help on the S5 Experience forum and i havent found and other forums that have this problem except maybe this one. so i am asking for help, if someone would be so kind as to walk me through how to fix my phone and what i did wrong it would be greatly greatly appreciated. if at all possible i would love to keep all of my pics and apps and stuff but if that is not possible then i wont complain if i have to lose it all. i would be happy just to have a working phone again. thanks in advance and sorry if i have posted this in the wrong place.
Click to expand...
Click to collapse
If you can boot to stock recovery (power+home+volume up) NOT safestrap recovery do a factory reset from there. That'll reflash stock rom and you can reroot + busybox + SS. Make sure to check what build you are on as well - if you are on NC2 kitkat you can only flash kitkat-based roms.
Sethers, please do not hijack and do not double post your questions in multiple threads.
graydiggy said:
Sethers, please do not hijack and do not double post your questions in multiple threads.
Click to expand...
Click to collapse
sorry graydiggy. this seemed like a thread that had something to do with the same black screen i was getting. besides this one i only posted it on the stupid questions thread.
---------- Post added at 01:56 PM ---------- Previous post was at 01:51 PM ----------
brisinger08 said:
If you can boot to stock recovery (power+home+volume up) NOT safestrap recovery do a factory reset from there. That'll reflash stock rom and you can reroot + busybox + SS. Make sure to check what build you are on as well - if you are on NC2 kitkat you can only flash kitkat-based roms.
Click to expand...
Click to collapse
brisinger08, thanks for the input. i was running kit kat. i figured the s5 experience would be based off of kitkat too but i guess i should have checked first. i just tried that. when i got into the recovery boot the little android guy falls over. then i went to factory wipe and let it wipe. after that i went to reboot. when it rebooted it still had the little lock under the Samsung logo and after that screen it went straight to safestrap again. it hasn't seemed to change anything as far as i can tell. any other ideas?
sethers said:
sorry graydiggy. this seemed like a thread that had something to do with the same black screen i was getting. besides this one i only posted it on the stupid questions thread.
---------- Post added at 01:56 PM ---------- Previous post was at 01:51 PM ----------
brisinger08, thanks for the input. i was running kit kat. i figured the s5 experience would be based off of kitkat too but i guess i should have checked first. i just tried that. when i got into the recovery boot the little android guy falls over. then i went to factory wipe and let it wipe. after that i went to reboot. when it rebooted it still had the little lock under the Samsung logo and after that screen it went straight to safestrap again. it hasn't seemed to change anything as far as i can tell. any other ideas?
Click to expand...
Click to collapse
If you're on the A3 bootloader then reflashing NC2 with odin will clear this up, (double-check in download mode) then follow the instructions in this thread. If you're on A2 you can still do this but it will overwrite your bootloader and lock you into NC2 so if that's the case you might want to read through that thread to make sure you're ok with that!
Good Evening XDA Note 4 Devs/Users,
The Bad News;
I seem to have gotten myself into a pickle. and, Hopefully.. one that isn't permanent.
So, I was planning on reinstalling Firekat 4.4.4 after being on CM12 (Lolipop) Remix. everything went super till I went to wipe my data/cache. In the process of being yelled at by two people and in the stress of it all I accidentally wiped the system data too. Which, seems to have deleted just about everything.. including the original backup of my device, the two ROMS and the system OS. The phone is also claiming not to be rooted now and TWRP seems to have been deleted too. The only thing I can really do is boot into download mode which ODIN keeps refusing to detect. and, Windows 8.1 keeps thinking the phone is a Banana.
The Good News;
I May have a Backup of the Original Unrooted TMO KitKat stored on my Laptop from ODIN.
I May Be able to push the Unrooted ROM by ADB / ODIN
I can boot into Download mode.
So, knowing my predicament and knowing I screwed up. Any advice or help from here to get the device working again?
Also, I promise not to try and turn the phone into a brick again. :good:
Thank you in Advance! :highfive:
Odin
follow this http://forum.xda-developers.com/not...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733
I'm on FK, I always wipe everything. As long as my Zip (for install) is on the external SD card, I'm good. So what's wrong?
As for not having TWRP, I would also just Odin to stock, reinstall it. Should be an easy fix.
madmike23 said:
I'm on FK, I always wipe everything. As long as my Zip (for install) is on the external SD card, I'm good. So what's wrong?
As for not having TWRP, I would also just Odin to stock, reinstall it. Should be an easy fix.
Click to expand...
Click to collapse
I came from a phone that if you end up deleting everything like this. You bricked the device completely with it not even turning on. (Older android phone). So, Naturally. I thought I had screwed myself with it. lol
I did fix it though right after I posted the thread. I managed to get one of the rom's to flash through odin. (so, I guess I did not accidentally unroot it). I think I Love Samsung phones now that I can accidentally brick it and then still get myself out of trouble with the help of you all
I dont know anyone who has bricked a samsung in a while. Odin is great. Only mess up would be if you delete pit file
BACARDILIMON said:
I dont know anyone who has bricked a samsung in a while. Odin is great. Only mess up would be if you delete pit file
Click to expand...
Click to collapse
I regret to say this is my first Samsung device.. was a Motorola and HTC fanboy before both which I bricked one way or the other..
BACARDILIMON said:
I dont know anyone who has bricked a samsung in a while.
Click to expand...
Click to collapse
I would still be careful. I managed to brick my Note 3 so hard that JTAG couldn't bring it back to life. They are easy to recover from soft bricks, but they aren't invincible...
Face_Plant said:
I would still be careful. I managed to brick my Note 3 so hard that JTAG couldn't bring it back to life. They are easy to recover from soft bricks, but they aren't invincible...
Click to expand...
Click to collapse
Really. I was working on 3 phones and flashed the wrong rom on my note 3. It was from a totally different phone. Took 6 hours to bring back to life. Odin would install a part then fail so just kept pushing and wiping and finally went in. I was mad as hell since i qas going on vacation the next day. Lol.
BACARDILIMON said:
Really. I was working on 3 phones and flashed the wrong rom on my note 3. It was from a totally different phone. Took 6 hours to bring back to life. Odin would install a part then fail so just kept pushing and wiping and finally went in. I was mad as hell since i qas going on vacation the next day. Lol.
Click to expand...
Click to collapse
I couldn't get into download mode. The phone was completely unresponsive to all button combos and my laptop. I tried a USB jig, an unbrick image flashed on an SD card, yelling at it, and sending it off for JTAG but nothing could bring it back. I was quite sad because I had a lot of good memories with that phone, but my Note 4 fills the void nicely.
Hi
I managed to get in trouble with note 3...I have listed my entire trial & error here, can someone please help me bring this phone back to life.
http://forum.xda-developers.com/gal...ed-samsung-note-3-n9005-t3058408/post59580154