Related
Hello all,
Introduction:
My name is Dev, and I have purchased a phone from Craigslist about a year ago. I used to use Windows Mobile phones. I had no problems with them. I have used the T-mobile MDA, Wing, and Touch Pro 2. They have been good phones for me, until recently. I have always wanted a faster phone and the Touch Pro 2 seemed to be quick enough for me. Nope. It slowed down just like the others. My brother is younger than me, and he has been attracted to the Android market since the T-mobile G1. I never got an opportunity to enter this operating system market. I am very tech savvy however, and it has merely been a case of me not wanting to "change." However, I am past that and I want to contribute to the Android community. My first Android phone is the T-mobile myTouch 3G Slide. (I like sliding phones in case you haven't noticed. I must have the physical keyboard. I text a lot.) I bought it used from Craigslist, and it seemed to work fine then. The previous owner was nice enough to clear all the data off of it, and give it to me fresh. I have been using it since.
Leading into my problem/question:
Lately, however, it has been slowing down too. I want to reset it to a clean slate. I know how to do it. It is in the menus. However, I do not like how this phone has been modified. Why would you modify a phone? I have never had to do this with my Windows phones. There has never been a need to flash any roms or anything. They had updates which were simple to use. Plug the USB into the computer and follow the simple steps. Make sure it doesn't shut off during flash. Simple. I've done this plenty of times with printers, motherboards, CD-ROMs, and all other flashable devices. I understand how big of a risk this is. If the flash doesn't complete (or is the wrong rom), then the device will not work again. Unless, you J-TAG the device and flash it again correctly. But, that requires a lot of work, and a wiring schematic to figure out where the J-TAG ports are. I have learned this information from back in the day when I used to do dish testing. You would flash roms to satellite TV boxes and experiment with new encryption technologies for satellite TV. That being said, I am terrified of flashing phones, because I would have no idea where to look for J-TAG ports for phones, if I mess something up. So, in conclusion, my experience in flashing has been for testing purposes only.
Problem/Question:
How do I figure out what the status of my phone is? It says Cyanogen Mod on start up. My brother tells me this is a very good rom. Who decided that though? Is it a bad idea to go back to stock T-mobile rom? I've always had this thought nagging me to try it and see why people go through all this headache of S-OFF and rooting phones. However, if I go back to the stock rom, will I be able to gain access to the phone's internal memory again? I don't like the idea of losing the S-OFF and rooting privileges the previous owner worked so hard to do. I would like to flash the latest T-mobile rom to the device, but how do I know if it will mess up everything and clash with some code leftover from the modified rom of Cyanogen Mod? Also, how do I backup all my stuff? I want to keep all my setting for the programs I have downloaded from the Google Market. I want to keep my contacts and notes. I want to keep my text messages and MMS messages. I am one of those idiots who keeps all his text messages and MMS messages archived. I go back through the messages from time to time for retrieval of important information I may have spoken about with someone in the past. I know this is a loaded post. I am sorry. If anyone is willing or able to help me, then please pick any point in this post and we'll go from there. This was just an outline of everything so you guys can help me find a starting point.
What I Know About the Phone:
T-Mobile myTouch 3G Slide
Android 2.3.3
Baseband 47.63.35.21U_7.15.35.16
Kernel 2.6.32.17-cyanogenmod-g501281a [email protected] #1
CPU ARMv6-compatible process rev 5 (c6l)
Mod CyanogenMod-7.0.0-Slide
Build GRI40
I believe it is S-OFF and it is rooted. I would like a procedure to verify though. Please.
Memory Card:
Memory card has a lot of folders and stuff on it from which I have no idea. Some of it says nervous stuff like ".android_secure" "clockworkmod" "2111.zip" "signed_Froyo_Slide_Radio.zip" "gapps-gb-20110120-signed.zip" "update.zip" "update-cm-7.0.0-Slide-signed" and "Android" I like it when my memory card is clean with nothing but a few folders like "Pictures" "Videos" "Movies" "Data" "Programs" "Software" "Music" and other general stuff like that. I like this so I can use the memory card elsewhere and know where everything is. Basically, I want to know if I can delete everything without shooting myself in the foot. How do I find out what each .apk is for? Will a stock T-mobile rom come with all the stock backgrounds, contact pictures, and all the other stock goodies? I feel like some of those were on the SD card too.
Things I like:
Speed. I like things to be fast. Utilitarian. I don't want any fancy effects, typically. I like everything simple. For example, my desktops are all using the Classic Windows Theme, and all fade in / fade out have been disabled. I want my phone to be the same way. Nothing I don't need. Minimalistic. I don't like to keep many programs running at once. This was something I liked about the Windows phones. I could click in the upper right hand corner and it would present a list of running programs. I could close specific ones that I did not want to run in the background. Android doesn't seem to have a feature like this, but it does seem like they close if they are not being displayed on the screen.
WIFI
How do I fix the WIFI in this phone? It seems like the radio drivers are wrong are outdated. It keeps dropping the connection immediately after the phone connects to a wireless network. I noticed a thread, but I cannot post to it. I wanted to ask how I would apply this patch to my phone without having a rom or anything. I thought maybe I could boot the phone into the recovery mode, and install the radio drivers maybe? I don't know what I am doing though, and want some guidance.
http://forum.xda-developers.com/showthread.php?t=1177650
And, why does the GPS take so long to get a fix?
Moderators/Thanks
I am very sorry to anyone and everyone whom I may offend in this post. If all my questions are answered somewhere else, please direct me to the correct area. I have been searching and researching for so long and I don't seem to be getting anywhere. I gave up about two months ago, and now I am back again trying to fix this phone. Please do not be mad at me for pestering you guys with annoying questions from new users like me. I know you guys are tired of answering these questions over and over again. Please. Just give me a little guidance. Thank you so much for any and all help. I really truly appreciate this. Android seems to be a very good operating system, and I am looking forward to all your posts.
P.S.
Sorry about the length of this post. It is my first time.
Test
Testing to see if I get notification of replies.
Well, for starters, welcome to the myTouch 3G Slide fora, second, yes, your brother is right, you are running the best ROM available at the moment, but your running an older version of itif you like, i can link you to an updated version of the ROM or i can point you to the "Android Development" section of the forum for the myTouch Slide and you can pick one your self, if you need any help with your device, feel free to PM me or reply to this thread at any time, seeing as how iI am one of the last people who actually still support this device for ROMs, i would reccomend my "TeamFreedom LeWaOS" ROM, but im still working out some kinks in it, for now, i will give you the opportunity to update to the latest version of "CyanogenMOD 7.2":
Download the ROM (has fix for WiFi i believe): http://download.cyanogenmod.com/get/RC/update-cm-7.2.0-RC2-espresso-signed.zip
Download for the latest 2.3.3 GAPPS: http://goo.im/gapps/gapps-gb-20110828-signed.zip
Also, here is how to FLASH these ROMs:
Pre-requsite: PLACE "update-cm-7.2.0-RC2-espresso-signed.zip" and "gapps-gb-20110828-signed.zip" on the root of your sdcard
1: Hold the power button on your phone
2: Tap "Reboot"
3: Tap "Recovery"
4: when in "Recovery" use the Volume +/- keys to move and the trackpad to select "Wipe data/factory reset" then select "yes" if necessary
4a: select "Install zip from sdcard"
5: then select "choose zip from sdcard"
6: select "update-cm-7.2.0-RC2-espresso-signed.zip"
7: When finished select "reboot system now"
8: again, reboot into recovery
9: flash "gapps-gb-20110828-signed.zip"
10: reboot system, and enjoy your updated phone, this process overall is the same for all android phones, and for all ROMs
Thank You
Thanks. I will try the new CyanogenMod rom.
Dealing with the performance of your phone, how many SMS/MMS msgs do you have currently? I noticed you said you dont like deleting them. Thing is, if you have a lot of msgs it can significantly impact your phones performance. Obviously it impacts the messaging app but in my experience it can affect the whole system. This may not be the case on CM ROMS but i have noticed it on stock. (i dont use CM much, prefer Sense).
Also u can try overclocking. I like NoFrills app from market. Its free and allows u to select your i/o scheduler and governor.
For backups, hands down Titanium Backup is the best if u ask me (and many others).
Hope this helps a little.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Update on CM7
Hey, guys.
So, I've updated to CM 7.2.0. Since then, I've been having problems with the touch screen and the phone app. If I use the directional pad, I can highlight the phone app, but when I click on it, it crashes. Also, the touch screen is unresponsive all the time. Sometimes, I will get lucky and when I reboot it, I will get access to the touch screen again. I am wondering if maybe I didn't update the drivers for the touch screen or the phone radio or something. I have a hunch that the phone app is crashing and lagging the whole system, so the touch screen isn't working because of that. When the touch screen does work, the phone app is also working. I am thinking of just flashing the phone with HTC's stock rom and then rooting and s-off it all over again, because I think the previous owner didn't do something right. I want to know if I can just flash the stock rom without any consequences. And, also will I be able to get it rooted and s-offed again? I'm hoping that by flashing the stock rom, I can test my touch screen and phone app with confidence. Maybe the phone app is sending commands for a newer firmware revision, and mine isn't updated to that version yet. Not sure how this works really. Anyways, any help would be greatly appreciated. Thanks in advance.
Suggestion. Re-flash the rom, but in recovery go into advanced, wipe dalvik cache. Hit back, now in mounts and storage. Wipe the following, boot, system, hit back wipe/factory reset, wipe cache. Flash rom, then gapps. Reboot. You should be good to go. Hope this helps.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app
---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------
Oh and to check for S-off reboot to bootloader when holding power, or while phone is off power on while holding vol down. Should say alfarev s-off or unlocked.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app
Ran into a wall
Alright, guys.
So, I ran into a wall. It is now completely unresponsive to the touch screen. I had recently flashed it, and I am trying to do what you had suggested, Dvarl. The problem is that I cannot touch the android logo so I can continue onto the Rom Manager where I can flash and reboot into recovery. If I try to go into the recovery by holding the down arrow and power button, then clicking on "Recovery," I get the red triangle logo. It has always been this way. Lastly, my phone is not s-offed. Thanks for helping me out with that. lol Any ideas on how to flash without the Rom Manager recovery flash?
Edit: I think I have found the problem. I think my digitizer is going out. I am going to maybe purchase a new one and see if it fixes the touching problem. I'll keep you guys posted. Thanks for all your help thus far!
Hello,
When I woke up a few moments ago I noticed that a system update icon was in my notification bar, which I assume is the new ZVD update and right now my phone is on ZVC and is stock rooted using ioroot25 and I have TWRP 2.7.0.0 AND download mode both working thanks to AutoRec and everything is working fine but it was a difficult getting to this point because I was one of the early adopters of the AutoRec method and I had to to go back to stock and re-tot my phone numerous times to get root, recovery, & download mode all 3 working on my phone without issue.
Now that the ZVD update is waiting to be downloaded on my phone I do not want to have to go through all this stuff again nor do I want to lose anything I have on my phone currently so I would like to ask what is the recommended / safest way to install this update so that I can keep root, recovery, and download mode all 3 and not lose any of my data at the same time ?
Of course, I want to also make sure that this does not mess up my phone like the white screen issue some people had when using AutoRec on the Sprint version of the G2 or other issues so what are my choices and thanks in advance for any and all replies.
MTCell
You won't be able to until they fix the update. Even just root will lock the system on the update.
Only safe way right now is to tot back to stock zvc, take the update. Root with ioroot25. If you want recovery, you can use auto-rec and then flash dorimax kernel. Which has the zvd knock code in it.
Sent from my LG-LS980 using Tapatalk
secret.animal said:
You won't be able to until they fix the update. Even just root will lock the system on the update.
Only safe way right now is to tot back to stock zvc, take the update. Root with ioroot25. If you want recovery, you can use auto-rec and then flash dorimax kernel. Which has the zvd knock code in it.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
I also have a similar issue as the OP. I am currently rooted, stock rom. ZVD update has downloaded and is ready to install. However, what would be the nessesary steps to take prior to updating my phone? I dont care if I have to re-root again. I rooted me device using IOroot25. How can I unroot?
Thanks!
Supersu has the option to unroot permanently. Doing a full unroot. Weather the system accepts that, I'm not sure.
Sent from my Nexus 7 using Tapatalk
secret.animal said:
...Only safe way right now is to tot back to stock zvc...
Click to expand...
Click to collapse
But, reflashing the ZVC tot will erase all data, correct?
jlv3 said:
But, reflashing the ZVC tot will erase all data, correct?
Click to expand...
Click to collapse
Yes, complete everything. Data, pictures, documents, downloads.
Sent from my Nexus 7 using Tapatalk
mtcellph said:
Hello,
When I woke up a few moments ago I noticed that a system update icon was in my notification bar, which I assume is the new ZVD update and right now my phone is on ZVC and is stock rooted using ioroot25 and I have TWRP 2.7.0.0 AND download mode both working thanks to AutoRec and everything is working fine but it was a difficult getting to this point because I was one of the early adopters of the AutoRec method and I had to to go back to stock and re-tot my phone numerous times to get root, recovery, & download mode all 3 working on my phone without issue.
Now that the ZVD update is waiting to be downloaded on my phone I do not want to have to go through all this stuff again nor do I want to lose anything I have on my phone currently so I would like to ask what is the recommended / safest way to install this update so that I can keep root, recovery, and download mode all 3 and not lose any of my data at the same time ?
Of course, I want to also make sure that this does not mess up my phone like the white screen issue some people had when using AutoRec on the Sprint version of the G2 or other issues so what are my choices and thanks in advance for any and all replies.
MTCell
Click to expand...
Click to collapse
From what i understand , you will need a stock ZVC recovery and boot loader to apply the update. if you have any modification done in ROM (debloat/deleting/modifying system files) then the update might not complete.
So flash stock aboot(bootloader), recovery and kernel and then only apply the update.
TOT reflash is too cumbersome process and requires lot of restoration of apps setting etc.
I have same situation and am searching for stock files from ZVC. Please if any one has these stock file please do share.
Cheers
Phuq! I wish I read these forums more frequently.
Hey all,
Okay now, let me begin this horror story by say what I think needs to be said first and foremost.
"No matter your level of knowledge, there is always something new for you to learn."
With that being said, I phuqed up!!
I had my dream setup running almost perfectly. I mean heavily modded. Stock kitkat 4.4.2. from Sprint so I didnt have to upgrade anything. I rooted via .apk file. I autorec'd TWRP recovery. I first flashed a furnace kernel that gave me 2.49GHz overclock. And added in xdabebs cam mod. And loved it. I kept reading and researching. I found more goodies to play with. I install xposed framework and some useful add-in's. I find some old apps I love, like hide softkeys, and several quick launchers like pie control, and gestures. I eventually find D's kernel and was elated! 2.8GHz, whoopee! (although I have seen someone @3GHz.)
After about a weeks worth of additions, and stupid auto-updates from google play (omfg they take up so much room) I got that dreaded icon in my notifications bar that Im out of room!!!! Stupid phuq'n non Korean model phones! (I feel that is hella racist of LG to show their people love and phuq us over with no external memory support. We should arrange a class action law suit. Thats purposely shaping the market favorably in your region, and selling obsolete hardware to the rest of the world. "shameful behavior LG")
So to remedy the space issue, I go through my most painful, and totally ridiculous ritual of removing "my" bloatware. All the launchers that I dont really NEED or use OFTEN. The apps that are convenient to have , but that convenience is never utilized. Or its rarely needed. And that helped me out about say, oh 200mb.
DAMN IT! need more room! Need room now!! Ahhhhhhhhhhh!
Okay so a few Big boys had to go. So I dumped a game or two, and the 2nd OS I forgot about on my device, Kali Linux. That gave me the much needed room. I gained about 4GB back. Cool beans, I figure before I do any new major changing of this phone I will force myself to make room for backups, ON device! :angel:
Well that didnt pan out. Instead I did one better, (I thought) I chose to back up on device, then rip it to my PC. Cool , it has the space for storing crap like that..
"ahh, life and its inevitable bullshnikeys"
BAM!! a day or so later, my PC froze, in the middle of a gnarly drift. Crap, restart, checks disk , fixes one error, bam froze again, "ah shiz, I need to back up my back ups!" checks disk, a few errors , I have seen worse. I got it up and running then, ZZZzzzzrrrrttt! NOOOoooooooh! So the PC goes down hard. No HDD found style.
So I reach for my G2 to take a much needed brake on the throne and plan somethings out. I sit down, hit the pwr button, and my phone was in TWRP! Odd I think to myself, and proceed to reboot. TWRP! look through settings, look for anything new on the sdcard (internal) nothing. So I power it down and turn it back on. TWRP! Furious!
Now Im at defcon5 using my LIVE OS, BT5r3 KDE, and decided to hear back into the XDA jungle to see what might have happened.
I got the update for ZVD it would seem. And it bit me in the ass at the worst time. I do not have the Android drivers that the phone installs to the PC installed and configured because I cant cycle into Android OS. Im seriously stuck in TWRP mode. I managed to get into download mode once after trying for 20minutes to do so. ( I need to practice that) But for no avail, I couldnt configure/install/set anything up that would have allowed me to communicate with the phone.
Im so very tired and stressed. Normally I would throw this crap away and go back to my trusty and (IMO) more stylish motorola RZRv3, but its battery is like a joke with its 3 minute, PERIOD life time. SMH
So now I come before you, alone, tired, confused, and depressed, (I do not, like reinstalling anything, ever, in anything.) I just really dont want to hit that brick wall (pardon the pun) an know I have to, ahem, configure, so many apps that I enjoy using. All because I lost my recovery.
What is it about the recovery file that makes the option for keeping your user installed apps, achievable, versus the wack (not even an option at all) choice of having to wipe everything and start over? Because (IMO) that is in no way, a recover. Thats a fumble, oh, interception. Thats dropping the ball. If you waste all the space for "backing things up" then something happens, and you still have to completely wipe the IMPORTANT stuff!! Whats the point?
I have found and installed on this VB PC running windows 7 non sp1, x86-
LG Flashtool 1.8.1.1023
LG-Mobile-Driver v 3.8.1
adt-bundle-windows-x86-20140702
adbpush
LG PC Suite (that just serves no purpose other than to annoy me by not working WITH my phone)
I have downloaded the .dll for MY phone for Flashtool
I found and downloaded the 45475791e80904201311e1051ea628c3b98eef87.LS980ZVC_12-LS980ZVD_19_update from sprint
I have downloaded CloudyG3_1.2 and cm-11-20140623-nightly-ls980
What can I do to attempt to simply boot back into my android.
and if there is no option for simply restoring the functionality of the devices previous state,
what ROM/OS do you suggest I shove in this brick or what method should I use to punch the life back into my phone?
Im dyin ova eeeah!!!
Thanks in advance,
Orcinus
ZVD bit me too-not sure how, NEVER told it to install
adamant_orcinus said:
Hey all,
Okay now, let me begin this horror story by say what I think needs to be said first and foremost.
"No matter your level of knowledge, there is always something new for you to learn."
With that being said, I phuqed up!!
I had my dream setup running almost perfectly. I mean heavily modded. Stock kitkat 4.4.2. from Sprint so I didnt have to upgrade anything. I rooted via .apk file. I autorec'd TWRP recovery. I first flashed a furnace kernel that gave me 2.49GHz overclock. And added in xdabebs cam mod. And loved it. I kept reading and researching. I found more goodies to play with. I install xposed framework and some useful add-in's. I find some old apps I love, like hide softkeys, and several quick launchers like pie control, and gestures. I eventually find D's kernel and was elated! 2.8GHz, whoopee! (although I have seen someone @3GHz.)
After about a weeks worth of additions, and stupid auto-updates from google play (omfg they take up so much room) I got that dreaded icon in my notifications bar that Im out of room!!!! Stupid phuq'n non Korean model phones! (I feel that is hella racist of LG to show their people love and phuq us over with no external memory support. We should arrange a class action law suit. Thats purposely shaping the market favorably in your region, and selling obsolete hardware to the rest of the world. "shameful behavior LG")
So to remedy the space issue, I go through my most painful, and totally ridiculous ritual of removing "my" bloatware. All the launchers that I dont really NEED or use OFTEN. The apps that are convenient to have , but that convenience is never utilized. Or its rarely needed. And that helped me out about say, oh 200mb.
DAMN IT! need more room! Need room now!! Ahhhhhhhhhhh!
Okay so a few Big boys had to go. So I dumped a game or two, and the 2nd OS I forgot about on my device, Kali Linux. That gave me the much needed room. I gained about 4GB back. Cool beans, I figure before I do any new major changing of this phone I will force myself to make room for backups, ON device! :angel:
Well that didnt pan out. Instead I did one better, (I thought) I chose to back up on device, then rip it to my PC. Cool , it has the space for storing crap like that..
"ahh, life and its inevitable bullshnikeys"
BAM!! a day or so later, my PC froze, in the middle of a gnarly drift. Crap, restart, checks disk , fixes one error, bam froze again, "ah shiz, I need to back up my back ups!" checks disk, a few errors , I have seen worse. I got it up and running then, ZZZzzzzrrrrttt! NOOOoooooooh! So the PC goes down hard. No HDD found style.
So I reach for my G2 to take a much needed brake on the throne and plan somethings out. I sit down, hit the pwr button, and my phone was in TWRP! Odd I think to myself, and proceed to reboot. TWRP! look through settings, look for anything new on the sdcard (internal) nothing. So I power it down and turn it back on. TWRP! Furious!
Now Im at defcon5 using my LIVE OS, BT5r3 KDE, and decided to hear back into the XDA jungle to see what might have happened.
I got the update for ZVD it would seem. And it bit me in the ass at the worst time. I do not have the Android drivers that the phone installs to the PC installed and configured because I cant cycle into Android OS. Im seriously stuck in TWRP mode. I managed to get into download mode once after trying for 20minutes to do so. ( I need to practice that) But for no avail, I couldnt configure/install/set anything up that would have allowed me to communicate with the phone.
Im so very tired and stressed. Normally I would throw this crap away and go back to my trusty and (IMO) more stylish motorola RZRv3, but its battery is like a joke with its 3 minute, PERIOD life time. SMH
So now I come before you, alone, tired, confused, and depressed, (I do not, like reinstalling anything, ever, in anything.) I just really dont want to hit that brick wall (pardon the pun) an know I have to, ahem, configure, so many apps that I enjoy using. All because I lost my recovery.
What is it about the recovery file that makes the option for keeping your user installed apps, achievable, versus the wack (not even an option at all) choice of having to wipe everything and start over? Because (IMO) that is in no way, a recover. Thats a fumble, oh, interception. Thats dropping the ball. If you waste all the space for "backing things up" then something happens, and you still have to completely wipe the IMPORTANT stuff!! Whats the point?
I have found and installed on this VB PC running windows 7 non sp1, x86-
LG Flashtool 1.8.1.1023
LG-Mobile-Driver v 3.8.1
adt-bundle-windows-x86-20140702
adbpush
LG PC Suite (that just serves no purpose other than to annoy me by not working WITH my phone)
I have downloaded the .dll for MY phone for Flashtool
I found and downloaded the 45475791e80904201311e1051ea628c3b98eef87.LS980ZVC_12-LS980ZVD_19_update from sprint
I have downloaded CloudyG3_1.2 and cm-11-20140623-nightly-ls980
What can I do to attempt to simply boot back into my android.
and if te youhere is no option for simply restoring the functionality of the devices previous state,
what ROM/OS do you suggest I shove in this brick or what method should I use to punch the life back into my phone?
Im dyin ova eeeah!!!
Thanks in advance,
Orcinus
Click to expand...
Click to collapse
Sorry Dude, I was in the same spot, maybe I can save you hours of reading. This is what I had to do:
http://forum.xda-developers.com/showthread.php?t=2432476 it's the dreaded tot to zvc
Hello everyone, long time lurker here.
I feel embarrassed even posting this thread in the first place but I'm currently flat out stumped. Over a year ago I flashed CM10 to my SGH-I747 using CWM (the whole process was done in a pretty outdated way, everything was basically manual) and a few months ago when I discovered cwm rom manager I installed cm11. I only ever used stable releases, never even thought about using a nightly.
Long story short after encountering the no service error I decided to try a nightly build for the first time ever. I had no problems after I installed it, functionality was just fine, but still the fact that my phone wouldn't save an APN was unresolved.
Today I decided that flashing back to stock and then reinstall CM using the app in the play store. After browsing this forum and youtube I foolishly used odin mobile to flash what I beleive is a stock version of android for my device. I got a normal starting animation (that annoying AT&T tun-tun-tun-tun with the words re-think possible show up like before) but it gets to this point where all I see is the word SAMSUNG in all white on my screen (it kinda has this glowing effect).
That's it.
First time I waited 30 mins and then pulled the battery. Restarted it twice more after waiting for the same amount of time.
The MD5 file I used came from file dropper. The URL after the dot com is /i747ucalemi747attalematt (sorry for posting this in a confusing way, I can't post links yet because I'm a noob).
Now when I boot my phone into recovery mode It says -
Android system recovery <3e>
Volume up/down to move highlight;
power button to select.
etc... the rest of the reboot/apply/wipe options
So... now what? Sorry for the giant explanation I just don't know what next step I should take. I wanna go back to stock, restore my data functionality, and properly set up CM using a rom manager. Thanks for taking the time to read this, I really appreciate any help you guys can offer.
P.S. I have the modem .zip for my carrier and I'm fine with using mobile Odin to install if I can just get normal functionality in my phone back.
What bootloader is on your phone? Did you try doing a factory reset from recovery mode?
Squerlli said:
Hello everyone, long time lurker here.
I feel embarrassed even posting this thread in the first place but I'm currently flat out stumped. Over a year ago I flashed CM10 to my SGH-I747 using CWM (the whole process was done in a pretty outdated way, everything was basically manual) and a few months ago when I discovered cwm rom manager I installed cm11. I only ever used stable releases, never even thought about using a nightly.
Long story short after encountering the no service error I decided to try a nightly build for the first time ever. I had no problems after I installed it, functionality was just fine, but still the fact that my phone wouldn't save an APN was unresolved.
Today I decided that flashing back to stock and then reinstall CM using the app in the play store. After browsing this forum and youtube I foolishly used odin mobile to flash what I beleive is a stock version of android for my device. I got a normal starting animation (that annoying AT&T tun-tun-tun-tun with the words re-think possible show up like before) but it gets to this point where all I see is the word SAMSUNG in all white on my screen (it kinda has this glowing effect).
That's it.
First time I waited 30 mins and then pulled the battery. Restarted it twice more after waiting for the same amount of time.
The MD5 file I used came from file dropper. The URL after the dot com is /i747ucalemi747attalematt (sorry for posting this in a confusing way, I can't post links yet because I'm a noob).
Now when I boot my phone into recovery mode It says -
Android system recovery <3e>
Volume up/down to move highlight;
power button to select.
etc... the rest of the reboot/apply/wipe options
So... now what? Sorry for the giant explanation I just don't know what next step I should take. I wanna go back to stock, restore my data functionality, and properly set up CM using a rom manager. Thanks for taking the time to read this, I really appreciate any help you guys can offer.
P.S. I have the modem .zip for my carrier and I'm fine with using mobile Odin to install if I can just get normal functionality in my phone back.
Click to expand...
Click to collapse
that's the stock recovery. try to wipe data/factory reset.
Hello! Pretty new in XDA forum and I have a couple of questions and concerns. I was browsing through some threads and I was wondering if I could get some opinion/help from other members.
I have a second phone that I want to mod and I need some help.
Device: Samsung Galaxy S4 (ROOTED)
Model#: SGH-M919
Android Version: 4.4.4
Baseband: M919UVUFNK2
It's an old phone and lately, it's been running really slow and if possible, I'd like to make it run as if it was brand new or at least somewhat close. So the question is, are there any recommended stable roms/mods I could use and if there are/is, will I be able to use it with my rooted phone or do I have to completely factory reset it before I apply the mods/roms?
Thank you!
Hi @Mr.LinK,
Just yesterday I finally got sick of my M919 slow/battery drain/old stuff and decided it was time for a reset. I was running SlimKat from over a year ago and while it was a great ROM, I had accumulated so much crap that it was getting really bogged down. This just happens over time no matter what OS, no fault to Slim. But I was also looking to move to Lollipop. Here's what I did:
1. Backed up using several methodologies (full backup with TWRP just in case, then from Android I backed stuff up with Helium, and used Backup My Mobile for SMS/MMS etc., an EFS backup just in case, etc..)
2. From within Android, did a factory reset. This sent the phone into recovery, and it formatted the data partition.
3. Rebooted to recovery again, and used TWRP to manually format the media section, just in case something was left there. Then wiped everything except the external SD.
4. Used ODIN to flash the OH3 firmware onto my MDL M919, without letting reboot after (unchecked the reboot checkbox). Pulled battery, rebooted back into download mode again, and flashed OH3 a second time... this gets around some instance people have reported about incomplete upgrades of firmware and all sorts of issues... better safe than sorry.
5. Let phone boot into now 100 % stock OH3 Android 4.4.4. YEEEUKKK. Some part of me thought I would just root the thing and get rid of Samsung crapware, but just the sheer annoyance of the T-Mobile boot animation was enough to remind me why I left stock long ago. Anyway, I let it boot, and set it up minimally with just 1 Google account, not restoring from backup. To my surprise it found the ATT network (I'm an ATT user, not T-Mobile... I just prefer T-Mo phones because they have unlocked bootloaders) and APN no problem no effort from me. Usually I have to enter an APN.
6. I tested the phone out to make sure all systems were working. GPS, WIFI, Bluetooth, etc.. To my surprise, first time I ran the camera app, it applied a firmware patch. Sweet. I'm glad I went through this step. Coming from ancient MDL, I figured there might be some kinks like this. I let it sit on stock for a few hours while I did stuff with my kids.
7. Back home, I did a factory reset from within Android. Then I flashed the latest TWRP tar file (2.8.7.0) using ODIN, and in TWRP did a full wipe of everything again.
8. At this point I flashed Danvdh's GPE edition of Lollipop from here.
http://forum.xda-developers.com/showthread.php?t=2539361
Installation went smoothly. It's a very basic set of apps that it comes with (Google play is there, but you have to download email/messaging apps from the store such as Gmail and Messaging, Maps, etc). I like this approach!
I've been gradually setting things back up, and am very happy with things so far. Haven't run into any problems yet. The nice pure GPE android experience is refreshing.
@Frankenscript Thanks for the information. I was reading the linked thread and it looks really good so I'll give it a try
Mr.LinK said:
@Frankenscript Thanks for the information. I was reading the linked thread and it looks really good so I'll give it a try
Click to expand...
Click to collapse
Good luck and let us know how it goes!
Frankenscript said:
Good luck and let us know how it goes!
Click to expand...
Click to collapse
I just completely flashed my phone with the ROM and I'm pretty happy with the outcome. No bloatware feels so nice. I've been tinkering with it for a while now and I haven't encountered any problems so far but I did notice that model number changed to GT-I9505G. I'm assuming that's normal since the rom is based off of another variant which makes sense, correct me if I'm wrong. Will this complicate future updates or other rom installation? If so, are there any ways of reverting back to the original model number?
Mr.LinK said:
I just completely flashed my phone with the ROM and I'm pretty happy with the outcome. No bloatware feels so nice. I've been tinkering with it for a while now and I haven't encountered any problems so far but I did notice that model number changed to GT-I9505G. I'm assuming that's normal since the rom is based off of another variant which makes sense, correct me if I'm wrong. Will this complicate future updates or other rom installation? If so, are there any ways of reverting back to the original model number?
Click to expand...
Click to collapse
I'm pretty sure we can change the reported model number by modifying the build.prop file. I just haven't poked around with it yet... I did ask the question in the thread and am waiting for a reply. I haven't had to do this kind of thing for over a year, and I forget the build.prop key that does it. But I had some concern that it might bork something else down the road so I decided to wait a bit. IT's just a cosmetic thing and I'm SOOO enjoying the experience right now.
Two little things I'm still fishing around for answers to:
-In the drop down quick access menu, I wish there was a sound/vibrate/mute toggle. I can make one with PowerToggles but maybe there's a way to adjust what's in the native one.
-Really silly, but the power off button when pressed just seems to ... power off the phone!? No option for restart / recovery. Maybe there's an option to set this somewhere; haven't checked.
Still, these are all minor things to sort out. Really, I think I'm very sold on GPE editions now thanks to Danvdh's work.
Marc
Just an update, my phone just rebooted twice in the last 5 mins or so. Was watching on my netflix and it randomly rebooted. Any idea what's causing it and how to prevent it from happening?
Mr.LinK said:
Just an update, my phone just rebooted twice in the last 5 mins or so. Was watching on my netflix and it randomly rebooted. Any idea what's causing it and how to prevent it from happening?
Click to expand...
Click to collapse
Haven't seen random reboots. I think I got maybe one reboot since installing the ROM. Then again, I haven't put NF on the phone. I do know that Netflix app had some issues on my Shield tablet, and the manufacturer (Nvidia) came out with a patch... maybe it's something general in Lollipop?
Frankenscript said:
Two little things I'm still fishing around for answers to:
-In the drop down quick access menu, I wish there was a sound/vibrate/mute toggle. I can make one with PowerToggles but maybe there's a way to adjust what's in the native one.
-Really silly, but the power off button when pressed just seems to ... power off the phone!? No option for restart / recovery. Maybe there's an option to set this somewhere; haven't checked.
Click to expand...
Click to collapse
Both if those can be fixed with Xposed modules.
Sent from my SGH-M919 using XDA Free mobile app
Will look into doing this in a week or so. Thanks
Sent back in time via Android 9.0 TimeText feature.
So, let me begin this tale with this disclaimer: I've worked with modding communities across a whole span of genres, from gaming to building computers. I will begin with the assumption that I am at fault in this case and I'm clearly doing something wrong. I've about reached the end of possibilities that I can explore on my own, so it's not like I tried one thing and gave up.
Once upon a time, I knew more about what I was doing than I do now. I first bought the T800 model several years ago, and the first thing I did was learn how to root it and flash CWM recovery. I went on all sorts of adventures with the device but never fully explored the potential; just installed awesome stuff that I thought I would use forever and got rid of bloatware and other useless crap. Flashforward to a few months ago, when I realized I had a really nice tablet that I had spent money on but didn't use like I had wanted to. I'm working more and more on audio mixing, and I wanted to install an app for the tablet that would allow me to remotely operate a mixing board. To my dismay, the app required an updated version of Android, and I hadn't a clue as to how to do that because the tablet was rooted and such and the thing wasn't going to update (was stuck on stock 4.4.2). I don't remember what I had done with it many years ago - at least not very well - and all I had learned was nearly gone. I refreshed a little, made a backup, checked to see what I had and noticed I still had the CWM recovery up, things were still rooted fine, and I was prime for flashing a new ROM and wiping everything. Found the Lineage ROM, slapped that puppy down, aaaand... Verification wasn't happening. Huh? It didn't even try to install, it just gave up and put the stock ROM back on. Tinkered with it for a second and thought, eh, whatever, I'll just let it update itself now that it's been wiped and everything. Only the device still wouldn't let me update it to Marshmallow or whatever update limit it's got.... Awesome... Did a little more research. Oh, my recovery is probably super out of date. Grabbed ODIN, slapped a brand spankin' new TWRP recovery that was geared for my device on it, and decided that I shouldn't go with Lineage. I'll just go with a stock Nougat ROM (can't post a link, but if it's important I can PM it to you if it's relevant).
Followed instructions to the T (as far as I'm aware) and this time did everything with a fresh new outlook into what I was doing. Flashed it, flashed GAPPS, aaaaaand.... Samsung logo won't go away.... -sigh-... Wiped it again, tried to make sure everything was wiped correctly, made sure everything was up to date. Tried again, but alas... Nothing working right for me.
Perhaps during this tale you've already picked up on something I royally messed up. Perhaps you're thinking, "Wow, how did this doofus not brick his tablet?" Am I getting old and stupid? Was there still research I missed? I started with the low road of easy modding and had to force myself to a higher road of deeper learning and STILL came up empty-handed, so now I'm asking this awesome community for a hand. I know you can't do this for me, but I'd appreciate a guiding light, or at the very least a link to an article that I really should have picked up on. Let me know if there's information I've missed that I should also be putting out, and thanks for reading regardless!
If I reached a point where I don't understand what's going on and I am banging my head against the wall, I would download the latest stock firmware for my device from sammobile and flash it with odin. If I recally it correctly, that would be the November 2016 security release of Marshmallow, the last Samsung provided. This should wipe away everything you have on the tablet. Then, if you need to flash root or alternative ROM, flash TWRP and proceed from there.
Akopps said:
If I reached a point where I don't understand what's going on and I am banging my head against the wall, I would download the latest stock firmware for my device from sammobile and flash it with odin. If I recally it correctly, that would be the November 2016 security release of Marshmallow, the last Samsung provided. This should wipe away everything you have on the tablet. Then, if you need to flash root or alternative ROM, flash TWRP and proceed from there.
Click to expand...
Click to collapse
Much obliged for your response, I've been up for a bit hoping maybe the boot process would just take a while, but no luck there. In the meantime I've been trying a few different Lineage nightly builds and they all seem to result in the same problem; surely they can't all be messed up and it's obviously something I'm doing wrong. My last recourse is to do this terminal fix I found that worked for someone else, but I doubt I'd be that lucky. I will assume that the Nov 2016 Marshmallow release is a google search away (or am I just bad at finding things...), and I'll post back here either within the hour or tomorrow night when I have time to find this build. Again, thank you.
Merancapeman said:
Much obliged for your response, I've been up for a bit hoping maybe the boot process would just take a while, but no luck there. In the meantime I've been trying a few different Lineage nightly builds and they all seem to result in the same problem; surely they can't all be messed up and it's obviously something I'm doing wrong. My last recourse is to do this terminal fix I found that worked for someone else, but I doubt I'd be that lucky. I will assume that the Nov 2016 Marshmallow release is a google search away (or am I just bad at finding things...), and I'll post back here either within the hour or tomorrow night when I have time to find this build. Again, thank you.
Click to expand...
Click to collapse
Download the appropriate MM version from below. Boot to recovery, factory reset, flash with Odin.
First boot will take around 10 minutes.
http://updato.com/firmware-archive-...xact=1&r=&v=Marshmallow(Android+6.0.1)&rpp=15
Merancapeman said:
So, let me begin this tale with this disclaimer: I've worked with modding communities across a whole span of genres, from gaming to building computers. I will begin with the assumption that I am at fault in this case and I'm clearly doing something wrong. I've about reached the end of possibilities that I can explore on my own, so it's not like I tried one thing and gave up.
Once upon a time, I knew more about what I was doing than I do now. I first bought the T800 model several years ago, and the first thing I did was learn how to root it and flash CWM recovery. I went on all sorts of adventures with the device but never fully explored the potential; just installed awesome stuff that I thought I would use forever and got rid of bloatware and other useless crap. Flashforward to a few months ago, when I realized I had a really nice tablet that I had spent money on but didn't use like I had wanted to. I'm working more and more on audio mixing, and I wanted to install an app for the tablet that would allow me to remotely operate a mixing board. To my dismay, the app required an updated version of Android, and I hadn't a clue as to how to do that because the tablet was rooted and such and the thing wasn't going to update (was stuck on stock 4.4.2). I don't remember what I had done with it many years ago - at least not very well - and all I had learned was nearly gone. I refreshed a little, made a backup, checked to see what I had and noticed I still had the CWM recovery up, things were still rooted fine, and I was prime for flashing a new ROM and wiping everything. Found the Lineage ROM, slapped that puppy down, aaaand... Verification wasn't happening. Huh? It didn't even try to install, it just gave up and put the stock ROM back on. Tinkered with it for a second and thought, eh, whatever, I'll just let it update itself now that it's been wiped and everything. Only the device still wouldn't let me update it to Marshmallow or whatever update limit it's got.... Awesome... Did a little more research. Oh, my recovery is probably super out of date. Grabbed ODIN, slapped a brand spankin' new TWRP recovery that was geared for my device on it, and decided that I shouldn't go with Lineage. I'll just go with a stock Nougat ROM (can't post a link, but if it's important I can PM it to you if it's relevant).
Followed instructions to the T (as far as I'm aware) and this time did everything with a fresh new outlook into what I was doing. Flashed it, flashed GAPPS, aaaaaand.... Samsung logo won't go away.... -sigh-... Wiped it again, tried to make sure everything was wiped correctly, made sure everything was up to date. Tried again, but alas... Nothing working right for me.
Perhaps during this tale you've already picked up on something I royally messed up. Perhaps you're thinking, "Wow, how did this doofus not brick his tablet?" Am I getting old and stupid? Was there still research I missed? I started with the low road of easy modding and had to force myself to a higher road of deeper learning and STILL came up empty-handed, so now I'm asking this awesome community for a hand. I know you can't do this for me, but I'd appreciate a guiding light, or at the very least a link to an article that I really should have picked up on. Let me know if there's information I've missed that I should also be putting out, and thanks for reading regardless!
Click to expand...
Click to collapse
Hello, Lineage dev for T800 here.
Did you flash the updated bootloader I link in the OP? Gotta be on the MM one for it to boot past that samsung logo
Can be flashed via ODIN, instructions are on there!
Lemme know if you get it!
DarkExistence said:
Hello, Lineage dev for T800 here.
Did you flash the updated bootloader I link in the OP? Gotta be on the MM one for it to boot past that samsung logo
Can be flashed via ODIN, instructions are on there!
Lemme know if you get it!
Click to expand...
Click to collapse
Just got back from work, about to test it out and will update on both situations (should one not work out). Regardless of the success, I'm genuinely honored that you guys are helping me in this process and I didn't expect such a warm and welcoming bit of support. Too often I see the "well any bloomin' idiot with enough IQ in his head to tie his shoe could have done this" comment, although I'm almost positive I'm going to get this fixed with your help and realize I've done something super stupid.
Welp, I'm a right idiot. I went with the first option, which was to attempt to flash a stock MM ROM. I followed akopps and ashyx' advice and went to that website where I believed I found the appropriate file and downloaded it. For some odd reason it took about 8 hours to download almost 2gb, which is odd because my net is faster than that. Anyway, I let it sit overnight so no issues there. A while ago I attempted to copy it over to my SD card, which was met with a slew of problems thanks to the copy process being cancelled multiple times. Maybe because the size of it? I had plenty of space. At any rate, it wasn't going to be an issue because I knew it was something I was probably doing wrong and would figure out later. I skipped and went straight toward DarkExistence's fix, which was to make sure I had the MM bootloader (I saw this instruction in your thread but at the time wasn't sure what it entailed and thought I was perfectly safe, and this was sadly before I learned more about what I was doing). Went through that process just in case, wiped, flashed the Lineage ROM , flashed GAPPS, rebooted, aaaand...
Bugger me, it worked.
So now I feel like a proper idiot. I hope this ends up in a google search down the line so other doofuses can stumble upon my own mistake and see that sometimes overlooking one simple thing can make all the difference. Will update in the future should anything change and I find myself doomed once more, but so far things seem tip-top. I checked to see if I could install the mixer remote app I had initially begun this journey for, and lo and behold it is now available for me to download! Now all that's left is to figure out how to root it, and voila! Thank you all so much, I am almost as relieved as I am embarrassed.