Related
silly me decided to install a custom battery icon. In the description for the mod on app planet it said to use with froyo but didnt say it would not work with eclair. I installed the mod without problems and I thought everything was going well, but now my phone is bricked, and wont load past the samsung i896 boot screen even after deleting all user data and wiping my cache in recovery mode. So I guess my only option now is to flash a rom using odin, but id rather prefer not to flash to a stock ATT 2.1 rom, i would like to flash back to my original stock rogers.
Is it possible to flash to an ATT rom, then do a factory reset from the privacy settings of the phone to bring me back to rogers stock rom?
ATT rom =/= Rogers rom
You'll need to search and find a Rogers rom you can stick in Odin and flash with if you want Rogers
I don't think you can easily return to Rogers stock rom using odin. Most people end up having AT&T logo on boot. However, since you're soft bricked anyways, why don't you try using Heimdall, new Open-Source Flashing Software and this dump generated from stock Rogers phone.
I haven't seen any reports of tests on Captivate yet, but it seems to work well on other Galaxies. Check Heimdall thread for more info, and if it works well for you, please report to this thread. Good luck!
thanks, i installed heimdall perfectly fine, it recognizes my device, but i cant download that PIT file from megaupload, its failed to download multiple times. Is there any other links?
I will keep trying
all good to go now,
used this rogers stock rom
http://www.megaupload.com/?d=BD2EF4WF
and flashed it without any problems. Glad to have a working phone again even though i lost everything
Did you use heimdall our some other method?
Sent from my SAMSUNG-SGH-I896 using XDA App
Hi! I just came across the same issue. I've been using the Cognition ROM on my Captivate for some months now and only today decided to switch to Perception 8. I downloaded the latter and rebooted through ROM Manager which, as I've done before, rebooted and backed up all my data. It then proceeded to erase all user data and cache and attempted to install Perception 8 ROM, but was unsuccessful. It provided me with a usual list of options, including 'Reboot', 'Backup' (i think) and others. I chose to Reboot thinking it would just go back to the last best ROM (i.e. Cognition latest, in my case).
Now it just reboots and refuses to go past the at&t World Phone boot screen.
I've tried the button combinations. Up-volume+down-volume+power button, up+power, up+home+power, down+home+power (!). All these seem to reboot the phone and in about 10 seconds after I press them, takes me right back to the same boot screen and not past it.
I'm fairly sure my old data is backed up somewhere inside.
I've tried to read the other forums, but nothing in particular seems to work for me. I run Ubuntu on my laptop, wanted to try Heimdall but its download page is down.
Any suggestions on how to proceed would be greatly appreciated.
1) Any other button combinations?
2) Any other tricks, including ways to using Heimdall (whose source files I can't seem to find), to get into my device?
Apologies for the detail, but I presume there's someone who knows exactly what I'm talking about.
OP, what software did you end up using on your computer to gain access to the device?
Thanks.
sshvetsov said:
Did you use heimdall our some other method?
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
yes i used it, installed the drivers on my pc, downloaded the rom i provided in my response and flashed it, worked flawlessly without problems.
nostratispeak said:
Hi! I just came across the same issue. I've been using the Cognition ROM on my Captivate for some months now and only today decided to switch to Perception 8. I downloaded the latter and rebooted through ROM Manager which, as I've done before, rebooted and backed up all my data. It then proceeded to erase all user data and cache and attempted to install Perception 8 ROM, but was unsuccessful. It provided me with a usual list of options, including 'Reboot', 'Backup' (i think) and others. I chose to Reboot thinking it would just go back to the last best ROM (i.e. Cognition latest, in my case).
Now it just reboots and refuses to go past the at&t World Phone boot screen.
I've tried the button combinations. Up-volume+down-volume+power button, up+power, up+home+power, down+home+power (!). All these seem to reboot the phone and in about 10 seconds after I press them, takes me right back to the same boot screen and not past it.
I'm fairly sure my old data is backed up somewhere inside.
I've tried to read the other forums, but nothing in particular seems to work for me. I run Ubuntu on my laptop, wanted to try Heimdall but its download page is down.
Any suggestions on how to proceed would be greatly appreciated.
1) Any other button combinations?
2) Any other tricks, including ways to using Heimdall (whose source files I can't seem to find), to get into my device?
Apologies for the detail, but I presume there's someone who knows exactly what I'm talking about.
OP, what software did you end up using on your computer to gain access to the device?
Thanks.
Click to expand...
Click to collapse
i used heimdall, which was linked above, but I was able to get into download mode through my phone since it was soft bricked. IF you can get back into Download mode, then you are fine... Keep trying until you do, otherwise you might have to use the JIG method.
stavs said:
yes i used it, installed the drivers on my pc, downloaded the rom i provided in my response and flashed it, worked flawlessly without problems.
Click to expand...
Click to collapse
That's great news! I'm sure a lot of rogers captivate users will be very happy to learn that. Just curious, where did the linked rom dump come from?
EDIT: Nevermind, found this thread describing Rogers stock restore procedure using Heimdall and the bundle you used.
@nostratispeak: if you have questions about Heimdall, you might want to check the official thread.
sshvetsov said:
@nostratispeak: if you have questions about Heimdall, you might want to check the official thread.
Click to expand...
Click to collapse
Yup. Just did. The site is back up and working. I've the downloaded the files too. Now, to get my phone to work.
@stavs Thanks.
Just curious. What's the difference between a soft brick and hard one? My Captivate simply refuses to get past the AT&T World Phone logo white boot screen - the very first one when you normally reboot the Captivate. I'm not sure if I'm in the 'Download' mode. And, I don't have access to the material required for the JIG. So, I'm hoping to get this done the software route.
Is there a chance that anything from my last best Cognition ROM is still active in there somewhere?
I'm also afraid that if I keep my phone ON for too long, it will simply die out and refuse to recharge.
Thanks.
EDIT: I followed the instructions from this thread and I have the phone in what I believe, is the Download mode: Droid shoving dirt within a filled yellow triangle, with a message "Downloading" "Do not turn off Target". My device is connected to my laptop. I don't see anything popping up on the screen. I also have Heimdall frontend up and running in Ubuntu.
I've downloaded a few ROMs, including Cognition and some samsung stock firmware. There are conflicting information in different pages. Am not sure what to do next. Help?
nostratispeak said:
@stavs Thanks.
Just curious. What's the difference between a soft brick and hard one? My Captivate simply refuses to get past the AT&T World Phone logo white boot screen - the very first one when you normally reboot the Captivate. I'm not sure if I'm in the 'Download' mode. And, I don't have access to the material required for the JIG. So, I'm hoping to get this done the software route.
Is there a chance that anything from my last best Cognition ROM is still active in there somewhere?
I'm also afraid that if I keep my phone ON for too long, it will simply die out and refuse to recharge.
Thanks.
Click to expand...
Click to collapse
Your device isn't bricked as such, it's caught in a boot-cycle. This is actually worse than a soft brick and in some ways is comparable to a "hard" brick. It's comparable to a hard brick because when you're in a boot cycle you usually can't get into download mode. Presumably the only option is to use a custom JIG, as you've mentioned.
There is no official terminology but a soft brick is generally when your phone displays the "connect phone to pc" screen. A hard brick is a bit more difficult to define, but I'd say it's fairly reasonable to assume that this is when your phone won't turn on or charge. A brick (full brick?) is when your device is absolutely not recoverable by any means.
nostratispeak said:
@stavs Thanks.
Just curious. What's the difference between a soft brick and hard one? My Captivate simply refuses to get past the AT&T World Phone logo white boot screen - the very first one when you normally reboot the Captivate. I'm not sure if I'm in the 'Download' mode. And, I don't have access to the material required for the JIG. So, I'm hoping to get this done the software route.
Is there a chance that anything from my last best Cognition ROM is still active in there somewhere?
I'm also afraid that if I keep my phone ON for too long, it will simply die out and refuse to recharge.
Thanks.
EDIT: I followed the instructions from this thread and I have the phone in what I believe, is the Download mode: Droid shoving dirt within a filled yellow triangle, with a message "Downloading" "Do not turn off Target". My device is connected to my laptop. I don't see anything popping up on the screen. I also have Heimdall frontend up and running in Ubuntu.
I've downloaded a few ROMs, including Cognition and some samsung stock firmware. There are conflicting information in different pages. Am not sure what to do next. Help?
Click to expand...
Click to collapse
thats great news than, now with the one of the downloaded roms you have saved on your computer, take the data (ie Factoryfs.rfs,cache.rfs, modem.bin and Zimage) and link it appropriately in the program. Then just click the start button and it will automatically install the rom within minutes. You shouldnt see anything pop up, i dont remember seeing anything, but during the installation there should be a download bar on your phone to indicate data is being transfered and downloaded to your phone. After your phone should reboot and be back to normal.
stavs said:
all good to go now,
used this rogers stock rom
and flashed it without any problems. Glad to have a working phone again even though i lost everything
Click to expand...
Click to collapse
Does this remove the AT&T boot logo and replace with the Rogers logo as well? Stavs, I'm assuming you went from the Rogers ROM, back to the Rogers ROM, so this probably not apply to you, but have any of you guys been able to get rid of the AT&T logo from a previous flash, and restore the Rogers logo using this method, and ROM?
stavs said:
all good to go now,
used this rogers stock rom
megaup*****com/?d=BD2EF4WF
and flashed it without any problems. Glad to have a working phone again even though i lost everything
Click to expand...
Click to collapse
used the same rom flashed it with odin but didnt load the pit file... made sure re-partitioned was UNchecked and off i went... restored my phone to 2.1 and was finally able to get kies to recognize my phone and upgrade it after 5 days in hell trying various things, flashing different "stock" ROMs... i finally did it tho... running froyo as we speak...
I am not sure if anyone suggested this already but i896 users can flash stock Rogers 2.1 using this method. No AT&T screens. Works great.
http://forum.xda-developers.com/showthread.php?t=979133
Hey guys. Forgive my lack of knowledge with the Captivate please, as I don't own one. I'm coming from the Evo 3D forums. My friend has a Cappy, and is having issues connecting to the pc via USB. I've searched a bit for some info, and all I came up with that was relevant was this :http://forum.xda-developers.com/showthread.php?t=808580. His problem started with extreme battery drain, lagginess, and freezing up. He decided he wanted to flash back to stock, and at that time discovered that his PC no longer recognizes the device. He gets an error complaining of unrecognized device. Apparently you need to run Odin in order to flash back to stock, from what I understand. Since his computer won't detect the phone, he can't use Odin. The phone does charge via USB and A/C. Also, he said that when he shuts the phone down, it won't reboot unless he does a battery pull, or reboots it from recovery.
Basically what I'm wondering, is there a way to flash back to stock without using Odin? With my Evo, you have two options of flashing back to stock. One, is using the RUU executable file from Windows, and letting that flash the phone back to stock. The other is to put a file called PC36IMG.zip on the sd card (of course the file would be pre packaged with the same images as the RUU would use) and boot to the bootloader. At that point, the bootloader would detect the file and ask to update. Then it'd flash back to stock using the bootloader, thus eliminating any need for a computer. Is there anything like that with the Sammy's? Thanks in advance for any input.
Btw, he has tried re-installing the drivers already, and is going to pick up a new usb cable on his way home. He hasn't tried the new cable yet. I know cables fail, but I'm skeptical due to the other issues he's having with the phone. It all started at the same time. I'm not sure which rom he was using at the time, I'm waiting for him to reply to me with that info. I know a month or so ago he was on some version of Cognition, but am not sure if he still was.
k2buckley said:
At that point, the bootloader would detect the file and ask to update. Then it'd flash back to stock using the bootloader, thus eliminating any need for a computer. Is there anything like that with the Sammy's? Thanks in advance for any input.
Click to expand...
Click to collapse
No the captivate dosen't have something like that (at the time maybe one day), their is heimdall which is an open source alternative to odin.
Why are you posting for your friend? if he's running on a custom ROM shouldn't he have an account?
k2buckley said:
Hey guys. Forgive my lack of knowledge with the Captivate please, as I don't own one. I'm coming from the Evo 3D forums. My friend has a Cappy, and is having issues connecting to the pc via USB. I've searched a bit for some info, and all I came up with that was relevant was this :http://forum.xda-developers.com/showthread.php?t=808580. His problem started with extreme battery drain, lagginess, and freezing up. He decided he wanted to flash back to stock, and at that time discovered that his PC no longer recognizes the device. He gets an error complaining of unrecognized device. Apparently you need to run Odin in order to flash back to stock, from what I understand. Since his computer won't detect the phone, he can't use Odin. The phone does charge via USB and A/C. Also, he said that when he shuts the phone down, it won't reboot unless he does a battery pull, or reboots it from recovery.
Basically what I'm wondering, is there a way to flash back to stock without using Odin? With my Evo, you have two options of flashing back to stock. One, is using the RUU executable file from Windows, and letting that flash the phone back to stock. The other is to put a file called PC36IMG.zip on the sd card (of course the file would be pre packaged with the same images as the RUU would use) and boot to the bootloader. At that point, the bootloader would detect the file and ask to update. Then it'd flash back to stock using the bootloader, thus eliminating any need for a computer. Is there anything like that with the Sammy's? Thanks in advance for any input.
Btw, he has tried re-installing the drivers already, and is going to pick up a new usb cable on his way home. He hasn't tried the new cable yet. I know cables fail, but I'm skeptical due to the other issues he's having with the phone. It all started at the same time. I'm not sure which rom he was using at the time, I'm waiting for him to reply to me with that info. I know a month or so ago he was on some version of Cognition, but am not sure if he still was.
Click to expand...
Click to collapse
There is a JH7 and a KB1 cwm flashable around here somewhere. Use the search button, it is your friend. and it has a better memory than I do.
speedy_11 said:
No the captivate dosen't have something like that (at the time maybe one day), their is heimdall which is an open source alternative to odin.
Why are you posting for your friend? if he's running on a custom ROM shouldn't he have an account?
Click to expand...
Click to collapse
Thanks, I didn't think so. And yea, he has an account but is a lurker, and was at work, so I posted for him.
mrhaley30705 said:
There is a JH7 and a KB1 cwm flashable around here somewhere. Use the search button, it is your friend. and it has a better memory than I do.
Click to expand...
Click to collapse
Thanks. I'll check it out. And yea, I know all about the search button (I did actually use it, just didn't have time to learn all the Sammy stuff). It's just that I don't have a Sammy, and everything here is wildly different than HTC. I didn't have the time to learn everything I'd need to in order to understand all the different terminology. I'll search for a JH7 and KB1 (although I don't even know what they are, haha) Sorry again for posting in your forum without having much knowledge on the Sammy stuff, and thanks for taking the time to reply.
It is my phone!!
The whole reason behind this is that I have till the end of August till the warranty expires. Running Serendipity VII. The phone will only boot with battery install, or power and volume up into recovery then reboot. So I want to go back to stock except PC won't see the phone. New cable, different PC deleted and re-install drivers. Still get usb device not recognized. With phone powered off plug in charger and nothing happens. Used to get image of battery. Any help or suggestions would be appreciated.
Thanks. I'll check it out. And yea, I know all about the search button (I did actually use it, just didn't have time to learn all the Sammy stuff). It's just that I don't have a Sammy, and everything here is wildly different than HTC. I didn't have the time to learn everything I'd need to in order to understand all the different terminology. I'll search for a JH7 and KB1 (although I don't even know what they are, haha) Sorry again for posting in your forum without having much knowledge on the Sammy stuff, and thanks for taking the time to reply.[/QUOTE]
Don't apologize for asking a question, that's why there is a q&a section. Search is a lot easier if you know what it is your searching for.
Jh7 and kb1 are firmware. Jh7 is the ota update that followed the release of jf6 (what a lot of captivates were shipped with) and is android 2.1. Kb1 is the 2.2 version that people upgraded to with kies mini(kies mini is the samsung online upgrade program).
I'm on Captivate #4, which is replacement #3 because the geniuses at AT&T believe the last phone I had was the cause of poor signal. The others were replaced for different reasons and I'm not convinced a new phone will help the signal but it looks like I'll wind up re-flashing it and returning the one I'm sending back AT&T back to stock. I've noticed after flashing the last two phones that it breaks the IMEI so that it displays a generic one(004999010640000). What's the best ICS based ROM that I can flash that won't break it again this time? If I knew what to back up I could do that too and just back it up before flashing to SlimICS. I tried following some guides to restore it on the other phones, but it didn't work for whatever reason. I know the /efs folder gets backed up, but then what?
dreamersrevenge said:
I'm on Captivate #4, which is replacement #3 because the geniuses at AT&T believe the last phone I had was the cause of poor signal. The others were replaced for different reasons and I'm not convinced a new phone will help the signal but it looks like I'll wind up re-flashing it and returning the one I'm sending back AT&T back to stock. I've noticed after flashing the last two phones that it breaks the IMEI so that it displays a generic one(004999010640000). What's the best ICS based ROM that I can flash that won't break it again this time? If I knew what to back up I could do that too and just back it up before flashing to SlimICS. I tried following some guides to restore it on the other phones, but it didn't work for whatever reason. I know the /efs folder gets backed up, but then what?
Click to expand...
Click to collapse
does this help? > http://forum.xda-developers.com/showthread.php?t=898387
Hello,
I've had my cappy for almost 2 years now... I could be just lucky, but never had a problem and I flashed all sorts of Roms.
Anyway it wouldn't be a bad idea to backup your whole EFS folder and there is also a couple apps to backup and restore your IMEI.
I'm currently on Ics Remix and love it... No IMEI problem smooth as butter... No sleep of death and battery is really good. I'm using the Roms kernel devil.... Which is what you want anyway.
Sent from my SGH-I897 using Tapatalk 2
I'd always made a backup but always forget where I put it or what I called it.. I think my luck it was on the phone itself and got wiped out, go figure. Not too sure though.
Hi All,
Before I ask my question, I just wanted to clear up that I've searched the forums (both on the s3 i9300 and i9305 sub forums,) and there's so much info that I got a little more confused and lost my confidence, which is why I'm asking here before I start the procedure.
I've just realized that my power button is starting to wear causing a 'bootloop' when I press it 7 times out of 10, and I have the opportunity to get it fixed under warranty.
Now, I've been running custom software since June 2013 and my phone is an Australian Telstra i9305T, and I have made a backup on the ROM pre-rooted when I installed CWM (although I'm not sure that it may work, as the bootloop have corrupted my SD card, there's a few backups that didn't have the same MD5 and can't be run.)
I wanted to make sure that the steps I unroot and reset counter to 0 for warranty would be:
1) Go to CWM
2) Wipe the cache/memory.(factory reset.)
3) Install the rom I backed up in May 2013
4) Triangle Away to set counter to 0.
5) Use the Unified Android tookit's unroot function.
Does that sound right? Or have I missed any steps.
FYI I had the phone inspected at the Samsung Experience store but the lady had threw a tantrum as she noticed I was running custom software, and pretty much refused to talk to me, (she wasn't even a tech, but I guess got upset on tampering principle,) so I want to make sure when it goes back to the techs it's ok to get fixed.
Any help I can get here would be appreciated.
Thanks in advance folks.
grungypoo said:
Hi All,
Before I ask my question, I just wanted to clear up that I've searched the forums (both on the s3 i9300 and i9305 sub forums,) and there's so much info that I got a little more confused and lost my confidence, which is why I'm asking here before I start the procedure.
I've just realized that my power button is starting to wear causing a 'bootloop' when I press it 7 times out of 10, and I have the opportunity to get it fixed under warranty.
Now, I've been running custom software since June 2013 and my phone is an Australian Telstra i9305T, and I have made a backup on the ROM pre-rooted when I installed CWM (although I'm not sure that it may work, as the bootloop have corrupted my SD card, there's a few backups that didn't have the same MD5 and can't be run.)
I wanted to make sure that the steps I unroot and reset counter to 0 for warranty would be:
1) Go to CWM
2) Wipe the cache/memory.(factory reset.)
3) Install the rom I backed up in May 2013
4) Triangle Away to set counter to 0.
5) Use the Unified Android tookit's unroot function.
Does that sound right? Or have I missed any steps.
FYI I had the phone inspected at the Samsung Experience store but the lady had threw a tantrum as she noticed I was running custom software, and pretty much refused to talk to me, (she wasn't even a tech, but I guess got upset on tampering principle,) so I want to make sure when it goes back to the techs it's ok to get fixed.
Any help I can get here would be appreciated.
Thanks in advance folks.
Click to expand...
Click to collapse
the steps are quite in good order. you dont have the new bootloader with knox i guess.. cause that would be a problem if the knox counter is triggered you cant set it back to 0, there is still no way found to restore knox counter for devices with new bootloader. everyone who has void knox warranty status can forget about sending device to samsung for repair for any reason!
if you havent flashed recently a new 4.3 firmware from sammobile or samsung-updates.com, you probably have the old bootloader which is good.
if you were not rooted when you made the backup in may 2013, then you will automatically be unrooted when restoring backup otherwise you would need to unroot after the backup restore. the backup will restore it to its state exactly how it was in may 2013. after the restore of backup go in odin downloadmode and check what info does it give in the left upper corner about system and binary status, should be both showing official and for the flash counter use triangle away indeed but keep in mind that it does not always restore to 0, sometimes it restores to 1 and thats no good.
MaHo_66 said:
the steps are quite in good order. you dont have the new bootloader with knox i guess.. cause that would be a problem if the knox counter is triggered you cant set it back to 0, there is still no way found to restore knox counter for devices with new bootloader. everyone who has void knox warranty status can forget about sending device to samsung for repair for any reason!
if you havent flashed recently a new 4.3 firmware from sammobile or samsung-updates.com, you probably have the old bootloader which is good.
if you were not rooted when you made the backup in may 2013, then you will automatically be unrooted when restoring backup otherwise you would need to unroot after the backup restore. the backup will restore it to its state exactly how it was in may 2013. after the restore of backup go in odin downloadmode and check what info does it give in the left upper corner about system and binary status, should be both showing official and for the flash counter use triangle away indeed but keep in mind that it does not always restore to 0, sometimes it restores to 1 and thats no good.
Click to expand...
Click to collapse
Yeah.. I think I rooted the phone before the knox bootloader came out for my phone, although I can't remember as it was a year ago.
So I guess at this stage the steps I'd take here would be:
1) Triangle away to reset counter to 0
2) Go into CWM clear the memory, and put in the unrooted image.
I've now got another question on the steps:
1) Currently using Triangle away, the counter only stays at 1, and every time I boots it shows the red '!' on the top left corner. That's not knox is it? And if it isn't, when I flash the unrooted image, will it get rid of it?
2) How do to revert to the regular stock recovery, as I've installed CWM. Or will the unrooted image handle that... if I recall the steps to rooting is installing custom recovery (CWM in my case) then taking the image with CWM then rooting then installing custom software.....
Again thanks for you help, I hope you can see where I get confused, I love this forums it's got so much help but sometimes it's hard to work out what to filter to make things go smoother.
grungypoo said:
Yeah.. I think I rooted the phone before the knox bootloader came out for my phone, although I can't remember as it was a year ago.
So I guess at this stage the steps I'd take here would be:
1) Triangle away to reset counter to 0
2) Go into CWM clear the memory, and put in the unrooted image.
I've now got another question on the steps:
1) Currently using Triangle away, the counter only stays at 1, and every time I boots it shows the red '!' on the top left corner. That's not knox is it? And if it isn't, when I flash the unrooted image, will it get rid of it?
2) How do to revert to the regular stock recovery, as I've installed CWM. Or will the unrooted image handle that... if I recall the steps to rooting is installing custom recovery (CWM in my case) then taking the image with CWM then rooting then installing custom software.....
Again thanks for you help, I hope you can see where I get confused, I love this forums it's got so much help but sometimes it's hard to work out what to filter to make things go smoother.
Click to expand...
Click to collapse
1. i dont know about the ''red !'' but it seems like you have done something wrong, it shouldnt show something like that..
the backup img might solve it, but dont now for sure
2. to revert back to stock recovery you could do this: flash official firmware with odin OR find a flashable stock recovery .img or .tar md5 file to flash in recovery. easiest way is to flash official firmware, that will restore everything to ''out of the box state'' and for the counter using triangle away (only thing is it restore's it to 1 instead of 0 )
if you ask me how i would make this whole thing ready and steady for sending to samsung, i would do this:
assuming here that i have old bootloader without knox, the steps would be for me in this order:
- put every personal stuff in internal or external sd to my pc temporary
- reset flash counter with triangle away
- go in cwm recovery and wipe everything, i mean really EVERYTHING. after that put phone off and go in downloadmode
- download the official firmware that my phone came with (for me that was android 4.1.2 no KNOX!) when first bought, and flash that with odin. now i have installed official firmware with stock recovery and device status is official and counter reset to 0 or 1
everything restored back to normal except the counter that stays on 1 unfortunately ready to send for repair, but i doubt they will accept it
i do understand your confusion about what to do, as in many threads people telling their own way of handling and taking steps to get things done and that can be very confusing as there are many things one could do. when trying to help people, i always try to provide the most common solutions and most easy one, but no matter how i tell and explain if you are someone who does not know much about android development kind of things, you will have always difficulties. the key for understanding is lots of READING and RESEARCH followed finally by executing what you have learned with proper tools. im just a member for couple of months now but i have followed these forums for many years and im glad i did..
MaHo_66 said:
1. i dont know about the ''red !'' but it seems like you have done something wrong, it shouldnt show something like that..
the backup img might solve it, but dont now for sure
2. to revert back to stock recovery you could do this: flash official firmware with odin OR find a flashable stock recovery .img or .tar md5 file to flash in recovery. easiest way is to flash official firmware, that will restore everything to ''out of the box state'' and for the counter using triangle away (only thing is it restore's it to 1 instead of 0 )
if you ask me how i would make this whole thing ready and steady for sending to samsung, i would do this:
assuming here that i have old bootloader without knox, the steps would be for me in this order:
- put every personal stuff in internal or external sd to my pc temporary
- reset flash counter with triangle away
- go in cwm recovery and wipe everything, i mean really EVERYTHING. after that put phone off and go in downloadmode
- download the official firmware that my phone came with (for me that was android 4.1.2 no KNOX!) when first bought, and flash that with odin. now i have installed official firmware with stock recovery and device status is official and counter reset to 0 or 1
everything restored back to normal except the counter that stays on 1 unfortunately ready to send for repair, but i doubt they will accept it
i do understand your confusion about what to do, as in many threads people telling their own way of handling and taking steps to get things done and that can be very confusing as there are many things one could do. when trying to help people, i always try to provide the most common solutions and most easy one, but no matter how i tell and explain if you are someone who does not know much about android development kind of things, you will have always difficulties. the key for understanding is lots of READING and RESEARCH followed finally by executing what you have learned with proper tools. im just a member for couple of months now but i have followed these forums for many years and im glad i did..
Click to expand...
Click to collapse
Okay, so now what you're telling me, which is contrary to what I've been reading previous to this is that there is no way to get the phone back to stock for warranty repair as they won't accept it due to the counter being at 1.
(Would this be knox?)
Thanks for your answers tho', I really appreciate them usually my posts get ignored, prolly filed under the "another noob" section.
The thing is I'm not that much of a noob, I just have a hard time trying to put all the info together so I can take the most optimal and risk adverse solution. As for reading and research, xda is a great forum but I can keep reading 8 hours a day for 3 months and keep going because as you said everyone has their own way of doing things and explaining things.
Maybe it's not worth for me to send my phone under warranty if they're going to reject it anywaysy... *sigh*
Despite not being able to help a lot, I would just like to chime in that I have the little red exclamation mark aswell, and I have never installed the Oficcial 4.3 with Knox. So at least its not related to that.
I do have a custom Recovery and I am running a Rooted stock image.
The exclamation mark has not caused me any issues though..
found this as well: http://forum.xda-developers.com/galaxy-s3/help/red-line-exclamation-mark-left-wupper-t2011728/page2
timmtn said:
Despite not being able to help a lot, I would just like to chime in that I have the little red exclamation mark aswell, and I have never installed the Oficcial 4.3 with Knox. So at least its not related to that.
I do have a custom Recovery and I am running a Rooted stock image.
The exclamation mark has not caused me any issues though..
found this as well: http://forum.xda-developers.com/galaxy-s3/help/red-line-exclamation-mark-left-wupper-t2011728/page2
Click to expand...
Click to collapse
Well it definitely does help, so thanks.
Can I ask if you've sent your phone in for warranty repairs?
I think it has to do with having custom recovery.
grungypoo said:
Well it definitely does help, so thanks.
Can I ask if you've sent your phone in for warranty repairs?
I think it has to do with having custom recovery.
Click to expand...
Click to collapse
Unfortunately not (for you, fortunately for me).. My first i9305 actually had a defective power button which died the day after I got it. I had rooted it already, but was able to roll the original image back on the phone before handing it in. The store swapped it right away for a new one though, so it never turned into a repair case.
Long story shorter. Phone stolen. Phone had nandroid stored on my computer. Phone replaced by another Note 4 (PS, thief go pound sand). Didn't mess around, stock rom to Note 4 (ANK). Root. Recovery. Old image from lost phone used as recovery. (Yeah I didn't make a backup of original from new phone). Flashed over. Everything works fine. Now ready to put finger prints in. Error page pops up saying fingerprint scanner error. 72 hours of scouring this forum, internet, MULTIPLE stock rom flashes from the oldest to NJK to ANK and COG6. Clean flash, dirty flash NOTHING works. Makes no difference what I do, cannot get the fingerprint scanner to perform. Common problem, complaints all over the internet about it but NO SOLUTIONS. I have tried everything down to deleting directories and I cannot get the damn thing to work. Seriously doubt hardware issue. *#0*# sensor heading shows finger print scanner as Null and 0.0.0.0. Deleted cache. Deleted data from TIBU and now after three days I give up. Seems everyone has the problem but nobody knows why and when they do you get a half assed or worse answer as to how to fix it. Does anybody know how to get this thing working again. Do I need to flash an apk. Where can I find it. Do I need to rebuild. ? Can anyone flash that section fingerprint free and send it to me. I am just guessing. I know crap about how stuff works, I just know how to follow directions but this one has got me stumped.
Any help would be GREATLY APPRECIATED!
Regards,
Freddie did not get fingered but he needs it.
You need to flash stock firmware and verify that all is stock, sometimes after returning to stock you may have a miss matching error like bootloader or modem.
After running stock run smartswitch.
Pp.
PanchoPlanet said:
You need to flash stock firmware and verify that all is stock, sometimes after returning to stock you may have a miss matching error like bootloader or modem.
After running stock run smartswitch.
Pp.
Click to expand...
Click to collapse
Ok forgive me for my ignorance but if I run a stock firmware straight from Sammy shouldn't the bootloader and modem be part of the rom? It seems to me that doing a wipe should be like reinstalling windows, you format the drive and install the OS. There is nothing left and a complete rebuild of the file system occurs. Is this not what happens when you do a wipe in the recovery and then Odin the stock firmware? How can I be sure that when I install a stock rom everything is wiped and there is no hangers and the OS on the phone is rebuilt completely? When you say smartswitch I assume you mean the Sammy program.
jackler1 said:
Ok forgive me for my ignorance but if I run a stock firmware straight from Sammy shouldn't the bootloader and modem be part of the rom? It seems to me that doing a wipe should be like reinstalling windows, you format the drive and install the OS. There is nothing left and a complete rebuild of the file system occurs. Is this not what happens when you do a wipe in the recovery and then Odin the stock firmware? How can I be sure that when I install a stock rom everything is wiped and there is no hangers and the OS on the phone is rebuilt completely? When you say smartswitch I assume you mean the Sammy program.
Click to expand...
Click to collapse
Ok, I think I have found it but now I need to know how to fix it. Currently I have as follows in the about device screen:
Model SN-N910T
AHHA ------!!!!! - ANDROID VERSION 5.0
Baseband - N910TU1ANK4
Kernal version - 3.10.0-2796035 [email protected] #1 Thu Nov 13 18:01:07 KST 2014
Build number - KTU84P.N910TUVU1ANK4
So it seems the android version is wrong. Again forgive my stupidity but what exactly IS the android version. Meaning is that the baseband, the modem, what part of the stock rom is flashed wrong and where do I find that part to flash it correctly. I think I am making some progress just need input. Thanks Pp for getting me on track, now I just need a little shove to get this train rolling and maybe learn something in the process. If I fix it I then intend to write a proper write up for those lost souls out there who don't have to spend days....
So why does it say my android version is 5.0 when it should say 4.4.4?
Thank,
Freddy is getting nervous
First verify what version of the note 4 you have, Sm-N910T or Sm-N910T3 and flash proper firmware. Look under your battery.
Once you root you jumble up the phones ability to install firmware properly, and flashing stock firmware once with odin does not always secure components thus leaving you with unofficial status, "custom" and you think you went back to stock with no root but not official yet.
You need to make sure everything flashes and sticks, Model nunber, Android version, Basedand version, Kernel version, Build number.
Any of the modified components can stick and not be overwritten by stock odin flash.
Sometimes multiple flashes, or individual component flashes are required to go back to "official" stock form.
At this point you can verify that your fingerprint scanner works properly and leave it alone or proceed cautiously if root is really required ??? .
I only run stock and save myself all the headaches, I used to root back when Samsung phones where simple and less complicated without kernel security from Samsung.
I suggest latest 5.1.1 lollipop update, kitkat is primitive and outdated, you will be amazed at how well your note will run with latest firmware (with junk apps disabled).
Pp.
Here's a sample of my stock Note 4 running latest update.
Pp.
PanchoPlanet said:
Here's a sample of my stock Note 4 running latest update.
Pp.
Click to expand...
Click to collapse
Nope, I have wiped this phone a million times, reinstalled factory rom over the top of itself a dozen times, installed the baseband and bootloader separately after that and NOTHING changes it still will not work. I have read the complete internet from front to back and it seems nobody knows but the shadow.....Thanks for taking the time for trying to help me out though...
When you say wipe, do you mean factory reset?
Several resets in a row should wipe it clean. Something is stuck, could be the kernel, that will prevent a clean install.
You need to find a way to wipe partitions individually using ADB on the PC, that should allow for a clean install.
Pp.
jackler1 said:
Long story shorter. Phone stolen. Phone had nandroid stored on my computer. Phone replaced by another Note 4 (PS, thief go pound sand). Didn't mess around, stock rom to Note 4 (ANK). Root. Recovery. Old image from lost phone used as recovery. (Yeah I didn't make a backup of original from new phone). Flashed over. Everything works fine. Now ready to put finger prints in. Error page pops up saying fingerprint scanner error. 72 hours of scouring this forum, internet, MULTIPLE stock rom flashes from the oldest to NJK to ANK and COG6. Clean flash, dirty flash NOTHING works. Makes no difference what I do, cannot get the fingerprint scanner to perform. Common problem, complaints all over the internet about it but NO SOLUTIONS. I have tried everything down to deleting directories and I cannot get the damn thing to work. Seriously doubt hardware issue. *#0*# sensor heading shows finger print scanner as Null and 0.0.0.0. Deleted cache. Deleted data from TIBU and now after three days I give up. Seems everyone has the problem but nobody knows why and when they do you get a half assed or worse answer as to how to fix it. Does anybody know how to get this thing working again. Do I need to flash an apk. Where can I find it. Do I need to rebuild. ? Can anyone flash that section fingerprint free and send it to me. I am just guessing. I know crap about how stuff works, I just know how to follow directions but this one has got me stumped.
Any help would be GREATLY APPRECIATED!
Regards,
Freddie did not get fingered but he needs it.
Click to expand...
Click to collapse
try doing this...
1st - run chainfire triangle away v3.26
2nd - boot into recovery and wipe everything 3 times except external sdcard.. especially data...
3rd - boot in download mode and ODIN whatever firmware u wanna use... 2 times...
happened to me when the note 4 first came out... I had to exchange to a new note 4...
also whenever u do a nandroid.. U MUST REMOVE ANY SAVED FINGERPRINTS... so u can use that backup again..
if u restore a nandroid with a saved frintprints, it won't work, u must delete data and start fresh..
I don't know if u messed it up by restoring a nandroid from a previous phone and with saved fingerprints stored...
will do thanks for the advice will advise
Nope, nothing I do including stock or otherwise works. When you hit +#0*# it says null and 0.0.0.0 unless someone knows something I don't, it's borked. The thing is even if I used a nandroid and it overwrote my fingerprints where the ones in the nandroid so you would think it would work. Chalk it up to who knows....thanks anyway. Still looking if anyone finds solution....