Just as the heading says when I try to wipe cache partition in the menu after doing the hold the volume button up + home + power I get an error message. Is this normal? I used to do this with my S3 and never got an error message. This is a semi-new phone to me.
Thank you in advance,
AJ
Same problem
Is there anyone that could answer this question? I have exactly the same problem. I wipe the cache in recovery mode and below the Android dude it says "error." Any thoughts?
Thanks in advance!
asjdwf said:
Just as the heading says when I try to wipe cache partition in the menu after doing the hold the volume button up + home + power I get an error message. Is this normal? I used to do this with my S3 and never got an error message. This is a semi-new phone to me.
Thank you in advance,
AJ
Click to expand...
Click to collapse
Why are you wiping cache in the stock recovery? ??
"And on that bombshell it's time to end the show!"
Sent from my VisionX powered G900A Rockin Blue XKRome
Why not? There are numerous places on the Web that recommend doing this. Also, why resurrect my post since it's so old? Are you being a jerk on purpose or ais that just who you are?
He may have been under the impression you were using safestrap recovery on your device..
In which case....using the stock recovery could cause issues and/or error messages....
And so you know...anytime you enter stock recovery on this locked bootloader device...the warning triangle appears...but the wipe can still be performed...
If the stock recovery won't allow the wipe....then a closer look may be needed....(did you purchase the device new or used)...and if used then it may have been altered prior...
S5 is no jerk....rather...he's one of the most helpful users we have in this section...
So I'm sure he was attempting to help given the lack of responses in the thread...
I'd tell him "thank you".....for taking the time....and then place a "solved" in your thread title if the issue has been resolved ....g
You know what I thought about that after I posted my snarky comment. . I apologize..... Not the best. Week.
AJ
gregsarg said:
He may have been under the impression you were using safestrap recovery on your device..
In which case....using the stock recovery could cause issues and/or error messages....
And so you know...anytime you enter stock recovery on this locked bootloader device...the warning triangle appears...but the wipe can still be performed...
If the stock recovery won't allow the wipe....then a closer look may be needed....(did you purchase the device new or used)...and if used then it may have been altered prior...
S5 is no jerk....rather...he's one of the most helpful users we have in this section...
So I'm sure he was attempting to help given the lack of responses in the thread...
I'd tell him "thank you".....for taking the time....and then place a "solved" in your thread title if the issue has been resolved ....g
Click to expand...
Click to collapse
@gregsarg thank you sir I appreciate your kind words
"And on that bombshell it's time to end the show!" Sent from my VisionX powered G900A Rockin XKRomeBlue
Related
I know I should probably put this on the development portion but I can't post there cause this is my first post lol. I'm wondering is it normal for the screen to flash when pressing the Home button?
keitaroguy said:
I know I should probably put this on the development portion but I can't post there cause this is my first post lol. I'm wondering is it normal for the screen to flash when pressing the Home button?
Click to expand...
Click to collapse
Ran into the same limitation when I softbricked during my first attempt to update a kernel [talon] as required prior to the update to v5r3.
Had to look here and comment if ever I am to be up to asking anything in the dev forum. ...but then perhaps my soft brick question is best addressed here, aside from the fact that I still have the issue..
p1gnone said:
Ran into the same limitation when I softbricked during my first attempt to update a kernel [talon] as required prior to the update to v5r3.
Had to look here and comment if ever I am to be up to asking anything in the dev forum. ...but then perhaps my soft brick question is best addressed here, aside from the fact that I still have the issue..
Click to expand...
Click to collapse
Odin back to stock and start all over again. Make sure u fallow all the directions.
Sent from my GT-I9000 using XDA Premium App
it has more feeling that everytime i hit the home key its reloading the home screen. instead of before where it would do nothing. I'm using touchwiz 4 maybe it is because of that?
japr2821 said:
Odin back to stock and start all over again. Make sure u fallow all the directions.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Indeed that is the understood objective, but getting into download mode is the impediment. I have tried a number of the advised buttons/odin/usb/battery sequences, each of them many times. All yielding only a return of the soft brick image. So now I am waiting for arrival of a shipped jig from MobileTechVideos..Still hopeful.
p1gnone said:
Indeed that is the understood objective, but getting into download mode is the impediment. I have tried a number of the advised buttons/odin/usb/battery sequences, each of them many times. All yielding only a return of the soft brick image. So now I am waiting for arrival of a shipped jig from MobileTechVideos..Still hopeful.
Click to expand...
Click to collapse
you might see that image if there is a problem with the location for the image for download mode. i spoke t one member that said they had the phone+computer image but odin saw the phone so they hit start and the download image poped up halfway through
i have also successfully flashed with odin with a completely black screen. phone looked like it was off but was really in download mode.
Today I tried to flash my device after this official Guideline (if you want to call it official):
wiki.cyanogenmod.com: Samsung_Galaxy_Note:_Full_Update_Guide
Now I know that it is out-of-date: 5th June 2012 But now it's to late.
The first steps worked fine. As flashing method I choosed Method via Recovery. I bravely followed this guide and made a factory reset and wiped the cache.
I flashed my HTC Desire several times before so I wasn't really feared. I just wondered to find the update.zip in the internal sd folder. It then rebooted but didn't come to an end. I started it new. Nothing changed. (Here is the point I should have posted this, but it's gone.) I started back at Installing the ClockworkMod Recovery point 2. Windows only. Nothing changed.
So I started to panick, got here, read this and that, the panick reased... and this still goes on.
Now I am here and pleading for help.
It still trys to start through, and I waited long enough.
First, how can I check for an MMC brick and second, what is your advise for me?
Please, please help me. I was stupid, I thought I knew what to do. Please tell me how to do better next time.
You are not providing any usefull information..
Download a stock gingerbread rom and flash it via pc odin.. After the flash its done go stock recovery (volume up+home+power) and wipe data..
After that come here again and I'll help you go cm9
Sent from my GT-N7000 using xda premium
Answer the following:
1.Which ROM and kernel were you on when you tried this stuff ?
2.What did you do ?
3.Please post the link for the instructions which you followed
Stop the hocus pocus and say what you exactly did..
prixist tell
Whiskeyjack4855 said:
Stop the hocus pocus and say what you exactly did..
Click to expand...
Click to collapse
I did what was mentioned in the second line (the the wiki page with this title.
Also I must say, the theme is done, but thank for your interest. After a sleepless night ( Smartphone of a friend) I fixed it with the help of Dr.Ketan and a few threads he told to use.
It would be wonderful if anyone could fix the wikipage from Cyanogenmod. I think a wipe date/facotry reset befor the restart would do(last line Method via Recovery). But as for the fact that I needed help to get it done, I think I am not the right person to change this in this guide as a noob.
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!
Does anyone know where I can get the stock US ROM for the recent AT&T OTA update? My baseband version is: G870AUCU1BOC5
I'm having tons of issues with all my processes running at 100%, and since I've tried everything to salvage my battery life, the only thing left to do, in my opinion, is to do a clean install after a factory wipe.
I've looked everywhere without any sort of luck. My apologies if this thread is in the wrong place...
2BNDatte said:
Does anyone know where I can get the stock US ROM for the recent AT&T OTA update? My baseband version is: G870AUCU1BOC5
I'm having tons of issues with all my processes running at 100%, and since I've tried everything to salvage my battery life, the only thing left to do, in my opinion, is to do a clean install after a factory wipe.
I've looked everywhere without any sort of luck. My apologies if this thread is in the wrong place...
Click to expand...
Click to collapse
Their's isn't one...all the recent updates are done through ota. A factory reset from recovery should be enough, but if you want to be really thorough you can flash back to ne4 through odin and let it OTA back up.
https://www.androidfilehost.com/?fid=23622183712467373
This is the only full odin .tar for the g870a.
How do you get into recovery with the new 5.0 update? It's not showing the same menu when I do vol dwn+home+power...
2BNDatte said:
How do you get into recovery with the new 5.0 update? It's not showing the same menu when I do vol dwn+home+power...
Click to expand...
Click to collapse
Vol up+home+power
Meh, sorry, I was just being dumb. Of course it's vol up+home+power, duh. Thanks anyway...
2BNDatte said:
Meh, sorry, I was just being dumb. Of course it's vol up+home+power, duh. Thanks anyway...
Click to expand...
Click to collapse
Lol...it's ok...I didn't remember at first either....I had to reboot into recovery to make sure.
Early indications show that the reset from recovery may have fixed the issue, at least so far...
SO, maybe I don't need a fresh install after all. Before, I had reset from within the settings menu. Is there a real difference between the two?
I'm not positive but I don't think you can flash back if you took the OTA. Once you take 5.0 there is no going back.
Sgt.CM said:
I'm not positive but I don't think you can flash back if you took the OTA. Once you take 5.0 there is no going back.
Click to expand...
Click to collapse
Only for the g900a. ..the g870a active can be safely downgraded.
Anybody want to answer my question or shall we continue taking the thread off track?
Lol, I'm harsh sometimes.
Nevermind, I found my answer here: http://forum.xda-developers.com/showthread.php?t=2639269
Your search function rocks in this forum BTW...
Before coming across the link in this forum here at http://forum.xda-developers.com/not...y-steps-n910t3-dofc-dog1-how-to-root-t3177225 ...
I thought I could shortcut all the work by going to the auto root chainfire site to download the actual CF Auto Root File for model sm-n910t3. I successfully flashed that file using odin. It went into a bootloop and then I freaked out.
The error messages when I turn on the phone first show
"kernal is not seandroid enforcing" in red, and
"Set Warranty Bit: kernal" in yellow writing.
After being in this bootloop i went to the link posted above and followed each step by step. My phone is successfully rooted now and I can log in to my phone fine. However, there are two problems. First, those error messages are still there. How do I get rid of that? I tried a factory reset on my phone and it wont do it.
Will get to that after. Second, when I go into twrp by hitting volume up+home+power, once im in there it wont allow me to backup my current rom. It says an error message about E:/ data mount or something like that. And also while in twrp it won't let me factory reset my phone. So the recovery program is pretty useless to me. I don't know why it doesn't work properly.
Where do I go from here? Can someone help me out in fixing this error message and getting a recovery program to work? I'm just wondering why the twrp that I flashed while following that root guide above does not work. Has anyone ever encountered those two error messages while turning on their phone? Thanks.
The error messages are normal after rooting.
Sent from my SM-N920T using Tapatalk
mrfordwrench said:
The error messages are normal after rooting.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
So other people have those messages on the top of their phone after rooting this device? Im guessing we just ignore that message then? I thought it was there because I flashed the wrong kernal before doing it the right way and following the forum...
What if I flashed the original firmware for this note 4 phone that I have a copy of, then root the phone going through that tutorial step by step? Wouldn't that get rid of the error messages? And my twrp would work then?
Im not able to make a backup of my current rom. And Im not even able to factory reset this phone. This is a problem for me since I want to put marshmallow on here soon. When I do I get an error message. Part of my second question is wondering why twrp isn't working correctly?
please help
i took my battery out to charge it and put a new one in. now it wont even boot up. it turns on and says
"custom binary blocked by FRP"
"secure fail: kernal"
for those of you who followed my other post i rooted my phone and tripped knox. phone was giving a message but would still turn on. where do i go from here? i have everything backed up and can start fresh. please provide step by step instructions on how i can fix this phone. thank you so much in advance and god bless.
I went to samsung and downloaded the firmware for this device and then flashed it. Now it's back to normal so you can disregard my post. Thanks guys.
scary
areininger30 said:
I went to samsung and downloaded the firmware for this device and then flashed it. Now it's back to normal so you can disregard my post. Thanks guys.
Click to expand...
Click to collapse
#UberNoob Drink your ovaltine. You should probably get an iPhone.
Everything worked as expected you are just so inexperienced you just gave us a play by play of your ignorance and then went running scared from the fear of 2x hello worlds and the unknown right back to momma Samsung. Good post
V3racious said:
#UberNoob Drink your ovaltine. You should probably get an iPhone.
Everything worked as expected you are just so inexperienced you just gave us a play by play of your ignorance and then went running scared from the fear of 2x hello worlds and the unknown right back to momma Samsung. Good post
Click to expand...
Click to collapse
Easy dude, that's not how things are done around here.
Ubernoob?
Drink my ovaltine? Hash tag for uber noob? Didn't your parents raise you to not say something if you have nothing nice to say at all? Apparently not so who's really the ignorant. Ask yourself that question. Ignorance is bliss. That's a good hashtag huh.
And the bottom line is that we were all beginners at one point right? So cut me some slack im learning. It will take me time to get to where you guys are at. Yes I am brand new to this stuff and no I don't like the iphones. Androids are more user friendly. I like Samsung phones and want to learn more about them.
Its people like you that keep us beginners from wanting to come back to this website, when guys say blatantly rude comments. It shouldn't be a bashing forum. Let's all chill and get along.
areininger30 said:
Drink my ovaltine? Hash tag for uber noob? Didn't your parents raise you to not say something if you have nothing nice to say at all? Apparently not so who's really the ignorant. Ask yourself that question. Ignorance is bliss. That's a good hashtag huh.
And the bottom line is that we were all beginners at one point right? So cut me some slack im learning. It will take me time to get to where you guys are at. Yes I am brand new to this stuff and no I don't like the iphones. Androids are more user friendly. I like Samsung phones and want to learn more about them.
Its people like you that keep us beginners from wanting to come back to this website, when guys say blatantly rude comments. It shouldn't be a bashing forum. Let's all chill and get along.
Click to expand...
Click to collapse
Good for you. If you need anything further, please don't hesitate to ask. There are a lot of great, talented and humble people on here, who would be glad to help.