Related
I have been on all the Root66 versions, and have had no problems ever...... till this UVDM5
I made a CWM backup (2 just to be sure) and proceeded to flash this new version that I have been waiting for so anxiously!
After it booted up, my desktop was the same, and all the apps showed, but talkback was already turned on, and I could no way get to the settings to turn that #$%%$ thing off. Heck, I could not even get to anything at all. It kept talking and reciting numbers everytime I tried to do anything. It was "Frozen" on the main homescreen, and could not do anything. I sometimes could get to the app drawer and that, too, would not scroll or do anything. I Re-flashed the thing after doing another download with the usual cache, dalvic blow out, and it acted the same way...
I decided to revert to the backup and tried to get to recovery (CWM).... That, too was gone! Stock recovery. I flashed the only version I had of CWM and it booted, and declared both of my backups were "corrupt" after it was almost done restoring?????? WTF!!!
I then reloaded UVDMD5 again, got the same results so did a factory restore and got to install my ROM manager, and re-flashed CWM to the version it uses, and tried the restore.....
It worked, and now after some pressure packed moments, I'm back to the UVLJA. I have to go on a trip tomorrow, (in a few hours) and need the phone working. PHEW! if anyone knows why the hiccup that I had occurred, please chime in and let me know. I still want the new OS and after my return, I plan to do the update again.... Hopefully....... Just gotta ccalm m my nnnneerves a bit before I attempt it again!
bobolinko said:
I have been on all the Root66 versions, and have had no problems ever...... till this UVDM5
I made a CWM backup (2 just to be sure) and proceeded to flash this new version that I have been waiting for so anxiously!
After it booted up, my desktop was the same, and all the apps showed, but talkback was already turned on, and I could no way get to the settings to turn that #$%%$ thing off. Heck, I could not even get to anything at all. It kept talking and reciting numbers everytime I tried to do anything. It was "Frozen" on the main homescreen, and could not do anything. I sometimes could get to the app drawer and that, too, would not scroll or do anything. I Re-flashed the thing after doing another download with the usual cache, dalvic blow out, and it acted the same way...
I decided to revert to the backup and tried to get to recovery (CWM).... That, too was gone! Stock recovery. I flashed the only version I had of CWM and it booted, and declared both of my backups were "corrupt" after it was almost done restoring?????? WTF!!!
I then reloaded UVDMD5 again, got the same results so did a factory restore and got to install my ROM manager, and re-flashed CWM to the version it uses, and tried the restore.....
It worked, and now after some pressure packed moments, I'm back to the UVLJA. I have to go on a trip tomorrow, (in a few hours) and need the phone working. PHEW! if anyone knows why the hiccup that I had occurred, please chime in and let me know. I still want the new OS and after my return, I plan to do the update again.... Hopefully....... Just gotta ccalm m my nnnneerves a bit before I attempt it again!
Click to expand...
Click to collapse
It seems to be an issue with the latest version of TalkBack on most roms. I had the issue already and from what I read in the forums, many other people have to. My advice, as soon as you flash a rom, uninstall or freeze talkback and DO NOT let it update to the latest version. Im not too sure what the issue is but hope Google fixes that soon.
I think also that I had a problem before when I installed the stock 4.1.2, it seemed to take my sdcard and renamed it to 0 on the sdcard. Took me a few hours to figure that out. I then copied everything that was in the folder 0 over everything in the root of the sdcard and it was back to normal.
Thanks! (Clicked it already)
I did notice a LOT of stuff was on the external card after the final recovery to the older version and had to clean up the external SD card.
You were right! I had no means to freeze the TalkBack, or do anything at all while within the OS itself, so no alternative was available to me at that time except a Factory Restore. The re-installation of my software was just going to take too long, so I did a recovery using the same version of CWM and was back where I was before the fiasco. Good thing I got it going.... Ida been really screwed! LOL. I'll try again maybe later, when I get home.
When I do try again, I'll remove the SD Card and then do the install using a spare one.
Have a great day!
I rooted and ran a couple diff custom ROMs: cm10.1.3 and infamous alpha, both with oc kernels (never set mhz past 2051). Began getting random reboots, alot while running the Alpha ROM, and a couple while running cm10.1.3 which I thought was weird because its a RC. should be stable, right? Anyway, got tired of RRs, so I decided to unroot and got stock, till I had some free time.to tinker with it. Well guess what, getting RRs EVEN IN UNROOTED STOCK. Any ideas?
I'm not exactly sure what steps you have taken to get back to Stock, where you're still having random reboots, but I'll let you know what I've done in the past to get to Stock which resolved the issues:
- Factory reset device from device. Save and/or move your Internal files/data prior as you'll be wiping Internal. I'd remove my extSdCard prior to Factory reset and after moving files to it.
- ODIN Samsung Stock Firmware
http://samsung-updates.com/details/9595/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUAMDL.html
- After the device boots, you'll probably get stuck on the Samsung splash boot screen. After a few minutes - -
- pull the battery, replace the battery but Don't power the device on
- Place device in Stock Recovery mode by pressing Power and Vol up buttons at the same time.
Release the buttons when you see the blue letters appear in the upper left hand corner of the screen.
- Scroll to Factory reset using the volume buttons.
(During the above process, you'll see the Android on its side with a Red X on him/her.)
- press the power button to lock in Factory reset
Let the Recovery scroll through its script
(during this process the Android will come to life )
- After the script is completed which takes less than a minute or so, scroll to reboot and select it with the power button.
- the device will now boot.
Important: while the device is booting, the screen will stay on the T-Mobilessplash screen for what will seem forever. Don't panic. The screen will show T-Mobile across the screen for about 15 or so minutes. Could be a little more or a little less. The device will then continue and complete the booting cycle.
Some notes:
1) during the above process, I have removed my extSdCard card as I didn't want tottake a chanceiit would be wiped. ODIN doesn't wipe extSdCard card but I don'tbneed it during theiprocess so I remove it in case Murphy decides to pay a visit.
2) during ROM flashes, I've experienced almost every issue youccan imagine. This occurred while using TWRP 2.5.0.2, but only when flashing ROMs with Aroma. For months prior, I had zero issues.
The problems I was experiencing were:
Random reboots, splash screen freezes, bootloops, installation of choices in Aroma which only partially installed, issues which didn't seem to havesan answer, and when you found the solution, that solution wouldn't work when the issue appeared again.
- constantly ODINing back to stock
- sometimes in Recovery, I couldn't get past the TWRP lockscreen, and only wiping Internal SD resolved the issue so I could do a Factory reset. I was doing this so often, that I left all files on my extSdCard so Iewouldn't lose my data when I had to wipe internal. It was faster this way as I didn't have to keep moving stuff back & forth.
After endless hours of troubleshooting and aggravation, I changed Recoveries.
I installed Philz Touch Recovery, and I have had Zero issues since installing it about 3 or so weeks ago, which have included multiple ROM flashes with Aroma.
I didn't want to switch Recoveries as I was very used to TWRP, but I just couldn't deal with the new found issues I was having so I made the switch and haven't looked back. Some people don't have issues with TWRP, but I wasn't one of them
Hopefully you can relate to some of my experiences which I have written above, which may help you to resolve some of the issues you're experiencing.
Yes. Thats the file I used and also the steps. I dont know what the deal is.
twatts723 said:
Yes. Thats the file I used and also the steps. I dont know what the deal is.
Click to expand...
Click to collapse
If you:
Wiped Internal SD
ODINd Stock Firmware
which flashed successfully
and are still having random rebooting.....
I can only suggest:
Check your device settings, if you haven't done so already to insure you're running:
Stock ROM
Stock modem/radio
And that all settings are stock.
If everything checks out, I can only suggest to:
Download the Samsung Stock Firmware file again
Check the md5 checksum
ODIN Samsung Stock Firmware again
And see how it goes.
So it turns out, if once you flash the stock firmware through odin, you just have to let it "settle in" for a couple days and all the problems go away. Thanks man.
twatts723 said:
So it turns out, if once you flash the stock firmware through odin, you just have to let it "settle in" for a couple days and all the problems go away. Thanks man.
Click to expand...
Click to collapse
Glad everything worked out for you.
Don't shy away from custom ROMs though, as you'll be missing out on some good stuff
As a note, there can be many thinks which can contribute to issues after the installation of a Custom ROM, Kernels, etc. such as:
Bad downloads, corrupted files, app conflicts, dirty flashes instead of Full wipes, etc., etc.
Another issue can be related to the Recovery you are using.
I had many, many issues regarding flashing ROMs which installed with Aroma.
Prior to ROMs w/Aroma, I had Zero issues.
I suggest using Philz Touch Recovery.
In case you don't have it installed and want to try it, I'll post a link to the download page.
Flash the proper file for your specific carrier.
Install the tar file with ODIN or
Flash the zip file with your Recovery......
Well, I come from sgs2. On that device, I could flash everything through cmw, and just use darkside super wipe and darkside cache wipe. No problem. Every rom from cm to amatuer custom blibbidy blobbidy, no problem. When I rooted my s4, I went straight to twrp because everyone said it was better. I flashed cm10.1.3 rc - rr. Infamous alpha v.7, which was supposed to be stable - rr. I went back to stock, rooted again, and kept stock tw, and only flashed ktoonz kernel, which is supposed to be one of the best for this device. Everything ran great, but guess what - rr. So I gave up. Went back totally stock. Working a lot of hours at work right now. We slow down after thanksgiving, so I'll probably start flashing again around that time. Thanks for thw help though
cheers.
Disclaimer: I am not responsible for any damage or liability arising out of these steps. I did not invent anything, I just tried something. Only move forward at your risk
If you don't agree ... stop reading and move on...
Background: Our phone has access to so much personal information that its scary if it fell into wrong hands. The only way to fix this is to encrypt phone. I did lot of research and here is a working solution that works for me - try at your risk.
Download Links:
a) Tested with ROM Stock 4.4.4 NH7 Galaxy S4 M919/Jfltetmo by @ShinySide
b) Tested with ROM |ROM|★KANGAKAT★|►KTU84P◄|4.4.4|Xposed|►8◄|6.26.14 by @iB4STiD
c) stock recovery AT&T S4 works with M919
d) Philz/CWM custom recovery
Encrypting with custom rom
1) Assume you are on custom recovery. - Backup everything first. Create a nandroid backup
2) Do a full wipe and install one of the two roms linked above (I have tested with few other roms ... none worked). Start the phone and set it up the way you want. Install all apps etc.
3) ODIN Stock recovery. See #c under download above. Its AT&T stock recovery but works for me. You need to know how to ODIN - find out. Doing this wrong will permanently damage your phone
4) Start your phone and turn on encryption. You will need to set lock type = password and will need to connect to charger and have 80% charge.
- Phone will do blank and stay blank for 20-30 minutes. Do not do anything. Encryption is happening behind the scenes.
- You might have to do this twice or thrice if it did not encrypt first time. For me the phone went blank first time and after 25 minutes it restarted but device was not encrypted. I redid the same steps and worked second time.
- If you interrupt the encryption process (battery pull or power up) you will see error message (encryption failed, reset device)
5) If all goes well you now have a password protected encrypted phone with custom rom!!! Check in Settings -> Security
6) You may install custom recovery ... but I don't see the point because you will need stock recovery to decrypt
To install another ROM
1) Reboot into stock recovery, then wipe data and cache (this removes encryption).
2) install your recovery of choice and install ROM using recovery. Philz/CWM
Credit goes to @Tronicus and his reply Flash a Rom on an Encrypted Android
Tronicus said:
How to Flash a rom on an encrypted Android phone (specifically this one, the I9505 SGH-I337).
The Problem: Once encrypted, you can't decrypt it easily. When encrypting the phone android will tell you you can only decrypt it using a factory reset. Naturally you assume it's talking about the "Factory Data Reset" option found in Settings --> Backup and Reset. But noooo, Android is lying through its ****ing teeth. Then you'll assume you have to wipe everything from your custom recovery mod (CWM, TWRP, or one of those). Wrong again! You'll get beautiful "can't mount /data" messages and more bull****. I read about a workaround that required installing the new rom using ADB, but I had ingeniously disabled USB debugging prior to wiping everything, so I only got so far with that option (plus it's tediously long if you haven't installed all the necessary software already and don't feel like bricking your phone because you made a typo in the command line). So, apparently the only other way to really format that partition free of its encryption is to use a stock recovery. So:
Short Version for Godlike users who know automatically how to do all this **** without any help (mimicking how most help posts are finely detailed on this site): Flash stock recovery, wipe everything, flash your custom recovery and install your new rom.
Long version for us mortals who don't know everything and haven't already downloaded already every single bit of software on earth:
Backup all the stuff you want to save. This process will truly wipe EVERYTHING. You can do it manually, or you can use an app like Titanium Backup Pro to help you (find it on Google Play Store). Here's a nice guide which recommends what to restore and what not to restore: http://forum.xda-developers.com/showthread.php?t=1480343
Flash the stock recovery using Odin. You can download a stock recovery from here: http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3 It's the link called "I337MK2stockrecovery.tar.md5" In case you don't know how to flash it with Odin, this short guide will help: http://forum.xda-developers.com/showthread.php?t=1506697
In step 6 replace "recovery.tar.md5" with the stock recovery you downloaded.
Wipe everything from the Stock recovery console. This little ****er will **** up the encryption all those sissies couldn't touch. You're welcome. You boot into recovery mode from a turned off phone by pressing simultaneously the volume up key + the home key + the power key until you see blue text appearing in the top left corner of your screen.
Reinstall your custom recovery. In my case I had installed the rom BEFORE flashing in the stock recovery (apparently it works, you just can't boot because of the encryption), so I was able to boot into the new rom before I returned to my custom recovery. Weird. Anyways, I recommend CWM. You can pick it up from this link: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte
For some weird reason they call the I337 version the "jflte" version. It's bonkers. Click there, and download the latest version that ends with .tar.md5. This version is upgradable via Odin, which we already used. Use the same instructions used as when you upgraded the stock recovery rom.
Boot into your recovery mod and flash your rom like you usually do.
A word about TWRP: it cost me many hours of work and I don't recommend it. Its website is outdated, and recommends using GooManager (which is no longer mantained) and doesn't work anymore for this. GooManager suggests using a new, different app, which doesn't have the option of installing TWRP. Then I tried using their TWRP Manager app from play store and the image file wouldn't download. Then I tried manually selecting the image file in TWRP manager that I downloaded from their site for use via the ADB method, and it bricked my phone... twice (using two different methods the app sugested). I tried so much because in theory TWRP has the ability to decrypt android's 4.4 encryption, but after looking at their github site I noticed it was filled with people's reports (including people with the S4) on how it wouldn't work decrypting squat. So I gave up, and installed CWM in 30 seconds.
Click to expand...
Click to collapse
Disclaimer: I am not responsible for any damage or liability arising out of these steps. I did not invent anything, I just tried something. Only move forward at your risk
cnewsgrp said:
One of the things I needed was the ability to encrypt my phone (device only not external SD) for security purpose. Our phones today gives access to lot of information that I would rather not fall in wrong hands. I did lot of research and here is a working solution.
Credit goes to @Tronicus and his reply Flash a Rom on an Encrypted Android
The quote looks long however it is really very simple. To install another ROM
- Install and reboot into stock recovery, then wipe data and cache (this removes encryption).
- Then install your recovery of choice and install ROM using recovery. Philz/CWM
This has been tested working on |ROM|★KANGAKAT★|►KTU84P◄|4.4.4|Xposed|►8◄|6.26.14 by @iB4STiD
This did NOT work on a Touchwiz ROM by same developer
I have not tested any other ROM
Click to expand...
Click to collapse
I don't know if it matters too much or not, but the stock recovery you linked to is for the AT&T S4. A good rule of thumb is to never use Odin to flash anything not specifically for your particular device... In this case the M919.
Sent from my SGH-M919 using XDA Premium 4 mobile app
lordcheeto03 said:
I don't know if it matters too much or not, but the stock recovery you linked to is for the AT&T S4. A good rule of thumb is to never use Odin to flash anything not specifically for your particular device... In this case the M919.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have tested stock recovery on M919 .. it works
Honestly im surprised its not talked about more since there is a big push for personal privacy when it comes to data. Encryption really is a pain in the ass to work with on android. Figuring out how to switch or update custom roms while encrypted will drive you insane. The easiest way is to just odin back to stock and start over, but that requires a computer anytime you need to flash anything.
I recently was trying out one of the 4.4.4 GPE roms and turned on encryption. It worked great until i started missing touchwiz and wanted to go back to HyperDrive TW. So the journey began...
First of all, i backed up everything to external storage since i knew everything on the internal storage would have to be wiped. I loaded the phone into recovery mode (using TWRP) and tried wiping, but all i got was a bunch of "Failed to mount" errors. Fine. Got the same error when trying to factory reset or wiping /system, /data, /cache, and anything else. Tried formatting to different file systems and then formatting back to the original but no luck. Fixing permissions didnt help. I just kept trying everything available multiple times.
Eventually it started wiping everything except the /data mount. Well... At least i could install new custom roms. Im not sure exactly what did it because i was just throwing everything at it. Anyways I got it to install, and booted into it. Nope.
Now it was saying I needed the password to decrypt the internal storage. It would detect wrong passwords fine, but as soon as i put the correct password in, it would allow me in, show the green android encryption picture, then blank screen. I thought it was just decrypting and setting up my rom but after a few hours my screen was still black and nothing was happening. Pulled battery and went back to TWRP.
I started wiping everything again and again and tried doing everything i could to wipe everything on the internal storage. Again, not sure what did it, but eventually got it all cleaned up and got a new rom installed and could boot into it.
The whole process probably took about 6-7 hours...
I dont even want to enable encryption on the new rom...
p-hil said:
Honestly im surprised its not talked about more since there is a big push for personal privacy when it comes to data. Encryption really is a pain in the ass to work with on android. Figuring out how to switch or update custom roms while encrypted will drive you insane. The easiest way is to just odin back to stock and start over, but that requires a computer anytime you need to flash anything.
I recently was trying out one of the 4.4.4 GPE roms and turned on encryption. It worked great until i started missing touchwiz and wanted to go back to HyperDrive TW. So the journey began...
First of all, i backed up everything to external storage since i knew everything on the internal storage would have to be wiped. I loaded the phone into recovery mode (using TWRP) and tried wiping, but all i got was a bunch of "Failed to mount" errors. Fine. Got the same error when trying to factory reset or wiping /system, /data, /cache, and anything else. Tried formatting to different file systems and then formatting back to the original but no luck. Fixing permissions didnt help. I just kept trying everything available multiple times.
Eventually it started wiping everything except the /data mount. Well... At least i could install new custom roms. Im not sure exactly what did it because i was just throwing everything at it. Anyways I got it to install, and booted into it. Nope.
Now it was saying I needed the password to decrypt the internal storage. It would detect wrong passwords fine, but as soon as i put the correct password in, it would allow me in, show the green android encryption picture, then blank screen. I thought it was just decrypting and setting up my rom but after a few hours my screen was still black and nothing was happening. Pulled battery and went back to TWRP.
I started wiping everything again and again and tried doing everything i could to wipe everything on the internal storage. Again, not sure what did it, but eventually got it all cleaned up and got a new rom installed and could boot into it.
The whole process probably took about 6-7 hours...
I dont even want to enable encryption on the new rom...
Click to expand...
Click to collapse
Yeah Encryption does not seem to work on TWZ roms. I tried on G Eye without luck.
I have updated op. Please check
Encryption will slow down your phone quite a bit. More battery usage + more CPU usage + slower phone = not worth it unless you've got some very private stuff you don't want being shared. Otherwise, 3rd party apps that lock a lot of files, can encrypt certain files, and hide others will do the trick perfectly well.'
Not trying to bash fully encrypting your phone, but I've tried it before and although I am very pro privacy, I had to eventually take it off due to all the extra hassle it created.
Don't know about slowing down. I am not seeing it. I feel differently about security.
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
svikramajit said:
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
Click to expand...
Click to collapse
Ok, first I think your SuperSu is not working properly. Open the Supersu app to see if it needs to update binaries. If it continues to crash, go into recovery manually (not using rom manager) and flash the latest SuperSu. Wipe Cache, go to advanced and Wipe Dalvik. Reboot. Your phone will say "android is upgrading" for a bit. Once it's booted up, go back into the supersu app and see if it needs to update binaries, if so- let it update, if not- move on. Here's a link to download SuperSu 2.02
Go back into recovery manually and select backup and restore-> backup to sdcard (or sdcard1, external sd, is my preference) This will start the backup process.
Once that is done, you need to find the CyanogenMod file specific to your phone, then you can enter recovery and flash it.
If you have trouble entering recovery, you can flash a new one via recovery or with odin.
Hello absinthesummer,
I followed every instruction you told. Now I'm done till creating backup. The problem now I'm facing is this 'Status 7' error. It says "Can't install package on incompatible data.....". Now what to do?
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
absinthesummer said:
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
Click to expand...
Click to collapse
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
svikramajit said:
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
Click to expand...
Click to collapse
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
absinthesummer said:
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
Click to expand...
Click to collapse
Thanks to you. You too helped me in working it out!
But, I have some more questions
Question 1 : If I flash stock ROM on my rooted phone, will I receive the new updates? If yes, will I be able to install them via Kies on my phone without getting into any trouble?
Question 2 : If I install stock ROM of any other phone, say Galaxy S5, will it work on my phone properly without any problems? If yes, will I receive the updates for that too and able to install them via Kies? If no, is there any way to install it? Cause I have seen people using S5 ROM on Note 2.
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
absinthesummer said:
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
Click to expand...
Click to collapse
- Stock Recovery
- Stock Kernel
- OTA Root Keeper
- Bloatware
Well, to be honest, just right now I learned these new terms but know nothing about them. Can you please give me a brief description for these four terms so that when I do advanced search on them, I'd have a idea in my mind about what these are. It will make it easy for me to understand the advance things.
And I'm looking for S5 ROM for my phone. Let's see what I get.
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Ok...
You already know what a rom is. A kernel is a lower-level base. It controls the hardware. So when you do something on the interface, in the rom, it tells the hardware how to react. (Ie if you're playing music it tells which speakers to play and how loudly). The kernel controls almost everything you can't see, it relates to performance. Most stock kernels can be limiting as they underclock the cpu by a certain percentage. Because of this, people seek out custom kernels to max out their device's potential. Louder speakers, faster cpu, better graphics, etc. This is all stuff the kernel can optimize... but because you can change so many factors there is a risk of instability if you push your device too hard (max performance) or limit it too much (max battery saving).
Recovery is exactly what it sounds like. When you boot your device the very first screen that pops up is the bootloader. It's giving you time to boot in 3 different modes. The first mode, by doing nothing, is a normal boot into the rom/OS. The second mode, which you get to by one button combination, takes you to recovery. The stock recovery is very limited. It gives you the option to factory restore, wipe cache, update, or boot normally. Stock recovery only exists for emergencies, if your phone fails to boot normally. We have custom recoveries so we can do more stuff, flash custom roms and tinker with things. The third mode is download mode/Odin mode. This is the bootloader interface itself. It's the last resort for recovery if your recovery has been damaged or corrupted. It allows you to connect to Odin or kies and perform an emergency recovery of the device. If you damage your bootloader, your device is completely bricked.
So the order of operation is this:
Lowest level- bootloader
Second level- recovery
Third level- kernel
Fourth level- rom
Bloatware is all the pre-installed apps that your carrier adds to your phone. Most people don't use it, don't like it, and don't want it. That why we root. Without root we basically are just guest users of the device. With root we become the administrators of the device. Until you root, your carrier has admin rights over your phone (to use windows terms).
When you receive an ota update, your carrier can make it to where the update won't proceed if their pre-installed apps have been removed (although this isn't always the case). Additionally, the update package itself checks the integrity of the device. It checks recovery, kernel, and rom. If any have been altered, it will not proceed because it could cause conflict and potentially brick your device. That's why those things have to be stock.
Ota root keeper is simply an app that backs up your superuser rights before an update and restores them after its done.
You should be able to find plenty of roms with S5 features. I'm using one that makes my device fully like an S5 (my device even thinks it is an S5 and every app identifies it as such) I can think of at least 2 others as well. There's plenty to choose from, and if you see a rom you like but it's mudding a particular feature, you can probably find that feature as a stand-alone installation in the forum's themes & apps section. Just about every feature of S5, S4, and note 3 has been ported to this device, so look around!
Also, for future reference, if someone helps you on the forum, hit the thanks button instead of saying it. I don't mind either way, but some people get annoyed and will stop helping them if they don't hit that button lol. It's silly, but it's part of "forum decorum"
---------- Post added at 12:54 AM ---------- Previous post was at 12:44 AM ----------
svikramajit said:
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Click to expand...
Click to collapse
You're fine, I don't mind answering your questions. Yes, you can unroot fully in the way you just mentioned but you don't even have to go through all the trouble of factory reset. Just unroot in the app. The app can be uninstalled afterwards via the play store.
You can factory reset either way, the same commands are given no matter which way you go about it. But it can be more efficient to do it from recovery because when you do it from the rom it has to create a wipe script for when it reboots, and it has to shut down the rom first. If you do it from recovery it doesn't have to anything, the rom isn't running and it can execute the wipe command immediately. (The wipe command is wipe /data /cache etc)
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
If you damage the bootloader it's a hard brick and you would have to send it in for jtag services (this is a low level emmc chip flash service) The bootloader won't get damaged unless you do something to corrupt it. If you ever feel the need to flash a new bootloader, do it via Odin, never recovery! If you remember that you should be fine.
svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
absinthesummer said:
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
Click to expand...
Click to collapse
Hey absinthesummer!
I tried to unroot my phone with the method I told you. But in the restore option, I am stuck at 'Checking MD5 Sums..'. What to do now?
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
absinthesummer said:
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
Click to expand...
Click to collapse
I waited and the system was restored. But I got an error on 'Restoring Data'. I rebooted the phone and now it's showing glowing Samsung logo from like 3-4 minutes.
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
absinthesummer said:
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
Click to expand...
Click to collapse
I'll try removing the battery now. Let's see what happens.
Ok if you can get into recovery, do a fresh flash and then try to restore again. And see if it offers a way to turn off MD5 checking. That's why I use philz or twrp, they offer that and move much faster through MD5 check by default.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
If you still fail on data, flash stock in Odin, flash custom recovery, then you should be able to enter recovery and have a successful restore.
Hello all!
This is my first foray into the world of custom Android systems, and I'm having a hell of a time with it... if somebody would be able to help me out, I would greatly appreciate it.
First off, the situation:
I am on Sprint, and I recently bought a Samsung Galaxy S3 (SPH-L710) from Sprint to use as a backup phone, I used it for a while on Stock, then deactivated it so I could give it to my wife. First though, I wanted to put a custom ROM on it, and experiment/play around a bit and see what this world of options could do for me. Long story short, I ended up flashing an AICP ROM, and everything seemed to go smoothly, but when I went to activate the phone on my account again and it would not work no matter what I tried (details below). I figured maybe I could activate on the stock setup then just restore my custom setup, so I tried to revert to my stock ROM backup and I couldn't do anything because I was constantly getting messages that various programs had closed... Then I tried to wipe and restore my custom ROM backup and I get stuck in a boot loop... so I tried to flash a stock recovery and I get stuck in a boot loop... I'm out of ideas here, and now I'm stuck with a phone I can't use or do anything with, and I can't activate.
Details:
The initial rooting/install process seemed to work ok, and was fairly straightforward. I followed various guides on http://galaxys3root.com/ to get my phone rooted and backed up (Don't recall which ones now, but I've read through so much by now I don't know if it matters...).
My phone:
Samsung Galaxy S3 (Sprint) SPH-L710
Modem: L710SPRDNJ2
My Desktop:
Debian Linux
Here's the steps I performed:
Rebooted phone in Odin mode
Downloaded CWM S3 Sprint Recovery from the http://galaxys3root.com/ website (can't find the link any more)
Flashed the CWM recovery using Heimdall then rebooted phone into CWM
Installed SuperSU through CWM, then rebooted
Checked that the phone was rooted successfully (it was), then ran Titanium Backup on the whole device to my SD card, then copied the backup files to my desktop computer
Rebooted into CWM, and performed a backup through CWM, then rebooted and copied the CWM backup to my desktop.
Downloaded AICP Rom for my phone from here: http://downloadandroidrom.com/file/GalaxyS3Sprint/roms/AICP/aicp_d2spr_lp-10.0-RELEASE-20150707.zip, put it on my SD card, then installed it through CWM and rebooted
At this point, I was happy with how everything was working, so I did some minor theme customizations then made another backup through CWM, and copied it to my computer, but I did NOT run Titanium this time...
After all of this, I tried to go ahead and activate it through the Sprint web service. This process failed continuously with an unhelpful error message of "Sorry, this device can't be activated right now". I then got on Chat to see if they could activate it manually, and then the problems began. They did their thing activating the phone, but when I booted up I got no data connectivity, and couldn't make calls, and the SIM was not changing over to the new number. I was on the chat with them for over an hour trying to get the situation resolved, but that finally ended when they started asking me to punch in ## codes, because I discovered that none of them worked on my custom ROM. Some quick research told me that this was non-trivial to get around so I had them switch everything back and I started researching the issue.
I found this thread: http://forum.xda-developers.com/showthread.php?t=1626638&highlight=sph-l710 that looked like it would let me do what I needed from the custom ROM, but I couldn't tell if it would fix my problem for sure, so I figured "I'll just restore my stock setup from that backup I took, activate it and update, then start over". This is when things got really frustrating...
First I rebooted into CWM, went to 'backup/restore', and restored my stock backup
Rebooted, and as soon as I got past the lock screen, I get inundated with messages of various apps being closed unexpectedly.
I researched a bit, discovered the issue may be caused by stale dalvik cache, so I rebooted into CWM, cleared the dalvik cache, formatted the /cache partition, then tried to restore the stock backup again, but this time I get stuck in a boot loop.
I then rebooted into CWM, tried to restore the backup of my AICP ROM, only to be stuck in a boot loop as well.
Trying to get into any usable system, I rebooted to CWM, cleared dalvik cache, then formatted /cache, /data, and /system just to be sure, and re-flashed the base AICP ROM I started with. This worked fine, and before long I had stock AICP back
Since I still couldn't get the phone to activate in the custom ROM, and my backups are apparently completely useless, I rebooted into CWM, wiped dalvik, /cache, /data, and /system again and tried to install a different stock ROM I found in the XDA forums (here: http://forum.xda-developers.com/galaxy-s3-sprint/development/stock-rom-4-4-2-t3010642) only to be greeted by another bootloop
At this point I've spent well over 24 man-hours trying to get this to work, reading, researching, flashing, etc all to no avail. Nothing I do seems to work, and it seems like every article, tutorial, or forum thread I read either has nothing to do with my device, is too old, or doesn't describe my problem.
I'm at wits end, and am so frustrated I'm ready to just give up and smash this device and buy a new one... My questions to the community are as follows:
I know I screwed up on a couple of things, but in my initial research of doing this there was no indication that these were even things I needed to watch out for... Is there any more organized sources of information for doing this sort of thing?
Does anybody else out there use Sprint on a custom ROM, and if so how you you pull this off
Where else have I screwed up, and how can I fix this situation? (My end goal is still to get the S3 onto Sprint with a custom ROM)
What can I do differently next time? I would like to figure this out and do it to other phones and devices I have, but if it's this much trouble every time, I just don't have the time to mess with it.
Thank you in advance, and I appreciate any information that the community can provide.
This sounds like a CWM problem to me. If I were you, I'd boot the phone into Odin Mode and flash TWRP ( www.twrp.me ) then try flashing the latest aicp nightly downloaded from the official site ( www.aicp-rom.com ). Check the md5sums on everything! Then maybe try flashing a touchwiz ROM and activating your phone. Remember that you need to wipe the internal storage when you go between KitKat and lollipop.
I'm fairly certain you have to do activation with the stock Touchwiz roms -- once the phone is activated you can flash a custom.
You should go into recovery and wipe everything (System/data/etc) EXCEPT for the External SD Card
Power off - pull the battery for a few - power on directly into download mode
Odin NJ2 back onto the phone and reboot and activate it (skip through most of the setup since you'll flash a custom after)
Once you know it's activated and working under the stock Touchwiz, then again power off and Odin TWRP recovery
Then you can go back into recovery, wipe everything except External SD, and flash the custom rom back on.
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
afarris01 said:
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
Click to expand...
Click to collapse
Get rid of them. TWRP can't restore CWM even if the backup is good