Related
Hello, I tried to post this in the developer forum but I am new so not allowed. I currently have a Galaxy S2 White t989 from t-mobile. Two days ago I upgraded my phone to official ICS via kies, I was already on Stock GB before and ICS made me phone practically unusable. I read a thread with directions on how to flash to stock from here:
http://forum.xda-developers.com/showthread.php?t=1513359
I followed those procedures to a t and now when my phone boots I can't get it past touch "android" to begin and a million things begin to "force close..g,apps,etc) Is there something I am missing? Just got this phone and I hope I haven't forever messed it up. If anyone has a link to a thread already solving the same issue...please let me know. I am a newbie with flashing so please have patience.
factory reset data
Thanks for your reply, but how would I go about doing this...I can't get pass the set-up screen to access the phone features. Is there another method to performing this.
Happened to me also, what I read was install clockwork recovery via ODIN (look for the thread in the other sections). Then you'll need to wipe cache and dalvic cache. Then you'll be able to continue to set up your phone.
OK great, will try it out, please wish me luck everyone. Love my s2, would be terrible if it is unusable.
Ok, so I installed clockwork recovery and still having the same issues...how I didn't anything with the recovery prompting to clear those caches?
yay!! back on stock and everything is working great..much thanks!!
Hello
I'm having the same issue that was stated above. I used the SGSII toolkit to do the stock rom flash and that is how I got to this point. I just wanted to know if using the process shown here http://forum.xda-developers.com/showthread.php?t=1858435 ? I skipped number 1 since it says it is optional. I now cannot find the "T989UVLH1.tar.md5" and all I can find is a file named "T989UVLH1_T989TMBLH1_T989UVLH1_HOME.tar.md5". Am I supposed to rename this one? Thank you very much.
edit.
I used the file T989UVLH1_T989TMBLH1_T989UVLH1_HOME.tar.md5 in odin>PDA>start. Then had an com.android.phone stopped unexpectedly problem. Used the toolkit to do a factory reset and everything is fine now. I'll have to do a little more research before I try rooting again, gave me too many headaches.
I'm sure there's multiple questions about how to fix their phone for this reason or that reason. I am on the verge of crawling up in a ball and rocking back and forth... (maybe it's a bit over dramatic) but I've tried to fix this based on my experiences in the past.
I have a galaxy s3 sgh-t999. I followed instructions to install CMW 5.0.5.4 and used odin, when I finished, I tried flashing a rom and got an error saying that the rom was for dr2tmo not for the device dr2spr. I thought that didn't sound right. I re-did the install of the cmw but used philz touch http://forum.xda-developers.com/showthread.php?t=2310081
I then wiped everything, the factory reset, the cache, battery. I then installed Hellfire for my phone, and the google apps, and now I'm stuck at the boot animation for the rom. I looked into resetting it back to stock, but Odin can't because the count is higher then 1 and I can't find somewhere to reset the phone's count without getting into a rom, which I haven't found one that works.
I appreciate any advice you guys can give, and please let me know if i missed a rule or something and I'll change what I can. Thank you.
I have no clue on how to pull logs either. I'm sorry for not getting too involved before I got that far.
awaj2006 said:
I'm sure there's multiple questions about how to fix their phone for this reason or that reason. I am on the verge of crawling up in a ball and rocking back and forth... (maybe it's a bit over dramatic) but I've tried to fix this based on my experiences in the past.
I have a galaxy s3 sgh-t999. I followed instructions to install CMW 5.0.5.4 and used odin, when I finished, I tried flashing a rom and got an error saying that the rom was for dr2tmo not for the device dr2spr. I thought that didn't sound right. I re-did the install of the cmw but used philz touch http://forum.xda-developers.com/showthread.php?t=2310081
I then wiped everything, the factory reset, the cache, battery. I then installed Hellfire for my phone, and the google apps, and now I'm stuck at the boot animation for the rom. I looked into resetting it back to stock, but Odin can't because the count is higher then 1 and I can't find somewhere to reset the phone's count without getting into a rom, which I haven't found one that works.
I appreciate any advice you guys can give, and please let me know if i missed a rule or something and I'll change what I can. Thank you.
Click to expand...
Click to collapse
My advice would be to get the Cyanogenmod for the d2tmo. If you are already at 4.3 use the 10.2 version. Otherwise probably use 10.1. Don't use the 10.2 unless you have to, it has some security stuff in it that makes rooting/modifying the phone a bit more restricted (IMO).
You can flash the zip for it in CWM or TWRP. http://download.cyanogenmod.org/?device=d2tmo
Once that is done you can use triangle away to reset your counter. Then use odin to get back to stock. Stock can be found at sammobile It'll be a long download, but worth it if you want stock. Again I do not reccomend going 4.3 unless you have already upgraded to it. If you have already upgraded to it you won't have a choice, but until someone finds a way to truly override KNOX and the bootloader security, I personally advise to stay away from it.
I hope this helps
I did do the update for 4.3 while it was available before samsung pulled it. I'll start with 10.1 tomorrow morning and hopefully I can post with good news after it's done. I'll probably stick with what ever I end up with getting to work for a while, whether it's CM 10.1 or 10.2.
You should try with CF method
Sent from my SGH-T999 using xda app-developers app
the CF method?
I got the following error
assert failed: getprop("ro.product.device") =="d2tmo" || getprop("ro.build.product") == ""d2tmo" E: error in /storage/sdcard1/cm-10.1.3-dtmo(1).zip
(status7)
I'll look more into the CF method.
I got CF for tmobile t999 and used odin, it CM came up rather quickly. I'm going through the initial set-up and then I'll try making a phone call. thank you for the help
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
kojam said:
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Bass_Man25 said:
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Click to expand...
Click to collapse
Thanks bud.
Oh, I got the phone up and running on the Cyanogen dated dec/2013.
ODIN? Never thought of it. Been such a long time. I do need to get stock on here so I can all the latest official radios etc, then put custom ROMs.
Been such a loooooong time since used ODIN though. Shouldn't be hard to get back on the horse.
Thanks for the suggestion!!!
any idea why this happened? anyone?
as an fyi, I tried to put the lastest SlimROM on but same difference. (i'm really pressed for time always. so I decided this is the quickest thing to try). seems the only thing that will flash is my Cyanogen from December. Strange...
Will have to give ODIN a try if I can ever get the time some day..
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
DocHoliday77 said:
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
Click to expand...
Click to collapse
What's up, Doc? Sorry for that...
I downloaded Odin this morning. I should have gotten the link from XDA. The site i got it from looked official, however, tons of endless pop-ups after I installed it. Freak!!!
Then found the xda links. Not sure which version to get because i didn't see which one handles the S3. The latest version (3.09) should, no?
As well, where do i get the stock ROM from? Forgive me for all these questions. Been extremely busy with work these past few months. No time to play around with my phone everything. I'm forgetting more than I know.
A full wipe was done. In TWRP, system was check (it's always checked) automatically when wiping to flash a new ROM.
Thanks again!
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
DocHoliday77 said:
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
Click to expand...
Click to collapse
Thanks!
S.O.S!!!
kojam said:
Thanks!
Click to expand...
Click to collapse
Downloaded the rooted firmware from your link and the ODIN (3.09)...
Flashed the firmware (making sure to get the correct one for WIND)...ODIN did it's thing...got a green pass...the phone rebooted...got the Samsung symbol, little swoosh animation, and the accompanying sound effect that goes with the swoosh-thing...THE PHONE NEVER BOOTED UP AN O/S!
Did it at about 11:30 last night, left it, got up this morn, and phone STILL in same status!
Found out that site where I downloaded the firmware had an issue last night. They posted this morn, apologizing to people about a D.O.D attack that may have caused dropped downloads. I downloaded the firmware again this morn, flashed with ODIN, got a pass....SAME THING!!! Phone
Had to quickly pack up my laptop to bring with me to the office. Will try the official, non-rooted firmware to see if I can get it to go.
Problems' that my team went from 12 to 2 people...my partner's off today...and I got a LOUD MOUTH across from me who WILL NOT leave me alone, no matter what I say or do. LOL.
Any suggestions?
In the words of George Costanza:
"I'm BACK, babyyyyyyy!!!!!"
The official firmware worked!
Phone's back online. Thanks for all your help. Will have to see about rooting later...as well, want to see how the battery operates on stock firmware. I've tried EVERYTHING under the sun to preserve batt life and NOTHING worked!!!
Tried EVERY KERNEL noted to be good on battery life, tried TONS of apps that were supposed to help, turned off as much as I could, etc....
batt still not good. I give up. Every diagnostic app says batt is very good. I dunno...
Earplugs! Lol! I definitely feel for you about your work status! Been there!
About the firmware though, if the download had been corrupted, it would've failed the initial check done by Odin. You are probably ok. Dont worry just yet!
If it is hanging up at the Samsung screen, you probably just need to factory reset. Almost always fixes this. (It happens due to incompatible data left from your previous rom)
This will wipe internal sdcard though, so if you haven't backed up yet, the next thing to fo is flash TWRP via Odin. You can then use its built in file manager to copy whst you need first. Or you can then flash an insecure kernel and use adb if you're familiar with that.
The Doc is in!
if the download had been corrupted, it would've failed the initial check done by Odin
Click to expand...
Click to collapse
That's EXACTLY my thought too. That was really perplexing...
I am up again...
Facotry Reset? How do I do that if stuck at the Samsung splash though?
Now that i know the official firmware works, maybe i'll, try again with the rooted firmware, try to factory reset when stuck, and continue to flash TWRP as you described above. Don't mind factory resetting. I've taken everything I need.
Oh!!!!
I noticed that all the apps I had before flashing the firmware are STILL on my phone. I would have thought that they would have been wiped out completely when lord ODIN was doing her thing.
....and battery life is STILL pretty bad...
Phone's been charging...became fully charged...unplugged it..it was down to 84% after only about 30/mins.
Will see how it goes after doing the factory wipe.
Again, how do i do a factory wipe if stuck at the Samsung swoosh after I re-flash the rooted firmware ?
Maybe your battery is dying. it happens. That would explain a big drop from the start.
To factory reset if you're stuck at boot up, turn the phone off, then boot up into recovery. Hold volume up, home and power. After it vibrates, release power only, continue holding the other two until you see recovery booting up.
If stock recovery is installed, choose factory reset.
In TWRP (probably similar in cwm) go to Wipe and choose factory reset there. In TWRP and CWM, factory resetting does not wipe your internal sdcard. Stock recovery will.
And as for Odin, it doesn't actually touch the user data partition, so all your apps and data are preserved. This is great when just upgrading from one build to the next, but is the reason a factory reset is required if coming from a non touchwiz rom.
---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------
How old is your battery? The S3 is at the age where people who bought it when it was first released will start to notice the battery is beginning to degrade.
You can also get an app called Better Battery Stats here on xda (paid version in the play store). Its the goto utility for investigating problems with battery drain. Run it for a day after a full charge and then check its logs for persistent wakelocks. The app thread should explain its use better than I can, but if you are having trouble you can always post your bbs log here for one of us to look over. (This isnt my strongest area, but there are a few others around that may also be able to help. )
Hello All,
Due to my endless frustrations, this might be a long one so please bear with me!
So I purchased a Verizon Global HTC ONE M7 from the States, I am currently in Nigeria and the only thing that makes me sadder and more frustrated than the state of my phone right now is the incessant terror attacks in the country! Initially, almost everything worked fine when i popped in my new Etisalat sim card into the phone, except for the mobile hotspot (which just conveniently turns out to be the one of the top 3 most important features in a phone for me - probably the feature I use the most) this message kept popping up about how hotspot couldn't be used without a VZW sim, etc (also with the non-verizon sim warning when the phone boots up). I tried all I could, eventually deciding to flash a new ROM to clear out everything Verizon and start fresh.
Enter Viperone 6.2.0 - everything worked initially, but after a few weeks i noticed if I did anything like watch a youtube video or download something over a few MBs 90% of the time the data drops (no visible signs like changes from E to H or 3g or the likes, everything looks the same, just that the data stops), toggle mobile data on/off and data connection is back. It worsened and became more frequent over time. Upgraded to Viperone 6.2.1, no difference, so i figured its probably the viperone rom.
Enter Cyanogenmod - http://forum.xda-developers.com/ver...-oneplus-one-stock-rom-cm11s-verizon-t2857425 - and its the same exact issue from the beginning, so im guessing its not to do with the ROM at all (though there are one or two niggling issues with the ROM - cant change BBM display pic, etc)?! I've really tried to comb through the forum and see what makes sense that i could try without bugging y'all - I did a factory reset, wiped everything completely and its the same thing.
I've seen suggestions to similar issues like: flash stock recovery, update radio/firmware/kernel, flash back to custom recovery and some other things which are beginning to sound quite dangerous in my ignorance!! I did believe updating the firmware made sense but after digging deeper, i must honestly say i'm quite confused on what to do. what radio/firmware/kernel works with what software version, etc- most firmware that i've seen are 4.4.3 compatible, while this ROM is 4.4.4., some of them seem to be for stock ROMs only and a lot of other confusions.
So, I'm not gonna be a hero and brick my phone from trying to do what i do not understand, instead here i am, hat in hand, crying out for help after suffering for 3 months! Its really frustrating as, downloads break causing me to lose data, skype or MSLync calls always break and im beginning to look unprofessional to people! This is why I have decided to put up a post of my own specific to my case so i don't medicate for someone else's ailments. So please........ WHAT EXACTLY DO I DO??
PHONE DETAILS (typing it out as i've just realized on this ROM i can't take screenshots with Power+Home button combo anymore and can't be bothered at this point!!!)
ANDROID VERSION: 4.4.4
BASEBAND VERSION: 1.12.41.1112_2
KERNEL VERSION: 3.4.82-gfe09065; [email protected] #1; Wed oct 8 01:36:03 PDT 2014
BUILD DATE: SUN AUG 3 23:00:51 PDT 2014
BUILD NUMBER: CYANOGENMOD 11S v5 (Verizon)
SELinux status: Enforcing
Thanks
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Can you flash stock recovery from Santod's firmware thread and do a factory reset? It could be a corrupt nv partition which would only be fixed by doing a factory reset via stock recovery. (If you must, make a nandroid of system and data in your recovery of choice so you can restore your data if you wish).
Uzephi said:
Can you flash stock recovery from Santod's firmware thread and do a factory reset? It could be a corrupt nv partition which would only be fixed by doing a factory reset via stock recovery. (If you must, make a nandroid of system and data in your recovery of choice so you can restore your data if you wish).
Click to expand...
Click to collapse
Thanks for the responses folks, i'll try out your suggestions and revert..
8100
brymaster5000 said:
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Click to expand...
Click to collapse
So.. i found time to get to this and decided to go with your suggestion of Santod's stock rom... and now, i think i've done the unthinkable!! After WIPING EVERYTHING "All partitions except SD!" as the instructions stated... i attempted to reboot into bootloader and got a message saying "no OS installed, are you sure you want to reboot"... that scared me a bit, but i thought surely, it must be part of the process! I proceed to reboot to bootloader to flash the firmware and i cant seem to do anything!!
Fastboot is stuck on " waiting for device" for everything i try.
Also, i rebooted back into recovery and attempted to install the stock rom: i get the error message "unable to open zip file"..
Have i destroyed my phone with my own hands, people? :crying:
Mr HaRR said:
So.. i found time to get to this and decided to go with your suggestion of Santod's stock rom... and now, i think i've done the unthinkable!! After WIPING EVERYTHING "All partitions except SD!" as the instructions stated... i attempted to reboot into bootloader and got a message saying "no OS installed, are you sure you want to reboot"... that scared me a bit, but i thought surely, it must be part of the process! I proceed to reboot to bootloader to flash the firmware and i cant seem to do anything!!
Fastboot is stuck on " waiting for device" for everything i try.
Also, i rebooted back into recovery and attempted to install the stock rom: i get the error message "unable to open zip file"..
Have i destroyed my phone with my own hands, people? :crying:
Click to expand...
Click to collapse
FALSE ALARM FOLKS!!! I decided to attempt flashing the CM11 rom i just uninstalled and it worked. Turns out its a known issue with the .zip file for that rom - i am now re-downloading from another mirror. Meanwhile the Fastboot thing was just a driver issue - though i'm surprised because i had all the drivers installed on the system and have used fastboot successfully - anyway i reinstalled the drivers and all was well with fastboot again.
NB: Don't get tired of me just yet please!
brymaster5000 said:
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Click to expand...
Click to collapse
hello!
Thanks for your ideas guys. I'm currently running Santod's stock rom (which is brilliant, i must say, i actually wanna stay on this rom) since friday - thought i'd give it the whole weekend and see how it goes.. BUT! i still get thoseconnection drops.. and frequently too.
Any other ideas on what the issue could be?
Mr HaRR said:
hello!
Thanks for your ideas guys. I'm currently running Santod's stock rom (which is brilliant, i must say, i actually wanna stay on this rom) since friday - thought i'd give it the whole weekend and see how it goes.. BUT! i still get thoseconnection drops.. and frequently too.
Any other ideas on what the issue could be?
Click to expand...
Click to collapse
If doing factory reset from stock recovery doesn't fix it, it is most likely a burned SIM. It has happened to me. (Average 150+ GB a month in data, so I burn em easily)
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uz has it right, you need to flash a stock recovery and THEN do a factory reset, then reload your custom recovery and rom. I had the exact same issue before. Or you could flash an ruu file which would reset the partitions also.
ccarr313 said:
Uz has it right, you need to flash a stock recovery and THEN do a factory reset, then reload your custom recovery and rom. I had the exact same issue before. Or you could flash an ruu file which would reset the partitions also.
Click to expand...
Click to collapse
Hey folks, apologies for the touch and go nature of this thread - i just don't have a lot of free time on my hands and other reasons..
Anyhow, i think I want to try out ur suggestion of flashing an RUU - I noticed that im unable to actually enter recovery after flashing stock recovery from Santod's thread (i flashed the latest three recoveries). I can get to bootloader, but when i select recovery, the phone goes black for a few seconds and then i get the RED TRIANGLE WITH THE EXCLAMATION MARK INSIDE, obviously something's wrong, few seconds later the phone reboots itself into normal mode. I did do a factory reset from bootloader, but issue persists.
So now to the RUU flashing issue - could you suggest one for me to flash?
By the way though, isn't flashing an ruu gonna take me back to stock completely (as in back to S-ON, ETC..)?
Thanks a whole bunch - IM DETERMINED TO GET THIS TO WORK!!!
Mr HaRR said:
Hey folks, apologies for the touch and go nature of this thread - i just don't have a lot of free time on my hands and other reasons..
Anyhow, i think I want to try out ur suggestion of flashing an RUU - I noticed that im unable to actually enter recovery after flashing stock recovery from Santod's thread (i flashed the latest three recoveries). I can get to bootloader, but when i select recovery, the phone goes black for a few seconds and then i get the RED TRIANGLE WITH THE EXCLAMATION MARK INSIDE, obviously something's wrong, few seconds later the phone reboots itself into normal mode. I did do a factory reset from bootloader, but issue persists.
So now to the RUU flashing issue - could you suggest one for me to flash?
By the way though, isn't flashing an ruu gonna take me back to stock completely (as in back to S-ON, ETC..)?
Thanks a whole bunch - IM DETERMINED TO GET THIS TO WORK!!!
Click to expand...
Click to collapse
That is in fact stock recovery man. When you get the triangle press volume up and power at the same time. You will enter stock recovery.
Any of my ruu will run fine. You won't lose s-off or unlocked status. You flash them in boot loader fastboot mode.
dottat said:
That is in fact stock recovery man. When you get the triangle press volume up and power at the same time. You will enter stock recovery.
Any of my ruu will run fine. You won't lose s-off or unlocked status. You flash them in boot loader fastboot mode.
Click to expand...
Click to collapse
HA! and now i feel :silly: !!
Bless your soul! i'll give it a go shortly...
never had this problem first here is all the background information from my last thread (yes i must be challenged)
really I don't know what to do
I believe i need to completely erase everything from my device as i cannot think of what else it could be but some conflicting something somewhere I am not educated enough to know
it flashes fine with odin but always system ui error I will be trying to go back to 4.1X as i believe that was my last bootloader and hope it works out. In all i want to update to NC2 and take advantage of the last roms beuing developed for this device.
In all i want to get my phone working again i need to get and send calls and texts so i plead for help Any question i will answer to the best of my ability
I have flashed with odin 3.1 and 3.07 NC2 then MJC basically both root 66 4.3 roms I don't know what my problem is maybe if while im waiting for help and using a root 66 for 4.1.2 (last working state) i will use recovery to wipe the sd card? idk but in all i think i need to start FRESH as long as i can get my contacts from Google i'm fine (and the phone rings and such lol)
IM eagerly waiting for help!!! someone else who is having a crappy holiday season maybe you can relate when you get in a funk where it seams everything breaks or needs to be replaced at one time
TUIA
You can't flash back to 4.1 with Odin. Root66 performs a full update including bootloader so no downgrade. You probably just need to factory reset with recovery. Just make sure you backup your internal sd
serio22 said:
You can't flash back to 4.1 with Odin. Root66 performs a full update including bootloader so no downgrade. You probably just need to factory reset with recovery. Just make sure you backup your internal sd
Click to expand...
Click to collapse
Thanks for sticking in there with me i did a factory reset using the recovery (i guess the android recovery) deleted data and cache which deleted all the apps which were messing things up so now it booted up like a brand new phone my contacts are back via Google and that's all i care ill be installing a rom and such soon but idk im starting over it works and upgrade
thank you a lot for sticking with me serio22 all i can do is thank you for all your posts but if i had the means id buy you a beer or something man
No problem man, glad it's fixed!
BeatnikBandit said:
Thanks for sticking in there with me i did a factory reset using the recovery (i guess the android recovery) deleted data and cache which deleted all the apps which were messing things up so now it booted up like a brand new phone my contacts are back via Google and that's all i care ill be installing a rom and such soon but idk im starting over it works and upgrade
thank you a lot for sticking with me serio22 all i can do is thank you for all your posts but if i had the means id buy you a beer or something man
Click to expand...
Click to collapse
http://forum.xda-developers.com/and...-rendering-t3003534/post58190052#post58190052
Try this