Related
I was running Starburst v1.9 and saw a thread on Themes & Apps with ICS transitions. I downloaded both just in case (ICS Transitions & Revert back to stock). I went into Root Explorer and checked my Clockwork/Backup and saw that I had a backup in there. I booted into Recovery and flashed the theme transitions for ICS zip and thus problem began.
I then went to restore to restore the backup and it seems like that file was corrupted because it wouldn't restore. I ended up flashing the revert zip file and wiping my rom. It doesn't boot but I can still get into recovery. I believe that the issue is that the theme was made for the v1.9.5 and I had v1.9 of Starburst.
I was messing around with it and I was able to boot back in and click on the Android to set it up. After a while the phone will go crazy and the screen will flicker on and off. The buttons at the bottom became useless. How can I recover from this.
** I used my friend's Sensation and downloaded v.1.9.5 and threw it on my SD. I booted into Recovery and flashed the ROM and it still won't boot up. Any suggestions? **
The phone booting up I think was a luck of the draw thing. Since then the phone has not been able to boot into the actual ROM. I've been without a phone since yesterday and I'm planning on going into the Sprint store and getting it swapped.
Did you wipe system, data, cache, and dalvik?
THEN reflash the rom?
Yes. I was a flashaholic on my Evo.
I notice another thread in q&a with people the same issue as mines. I'm lost and haven't had my phone working for two days now.
Here's what I did:
Delete system, wipe factory reset, cache and dalvik, flashed ROM.
Could it be kernel related? I'm confused. I have a wedding tomorrow and this couldn't have happened at a worse time. Coincidentally something happened on my At&t dumb phone so I'm phoneless.
stupid suggestion...is your battery low?
with the evo it would see corrupted if the battery was low. may not apply, but hey its a shot.
if you cant figure out, theres always Odin to cure your issues
ReDL the ROM and reflash. Try mounting USB storage while in recovery. Alternatively, Odin the stock .tar for a full refresh.
If you've already retired reflashing I'd go with odin back to stock
Sent from my SPH-D710 using xda premium
here is the link for a format all then you can try and flash a rom again if you like. If not I would do like previously suggested and flash return to stock in Odin- link here
playya said:
here is the link for a format all then you can try and flash a rom again if you like. If not I would do like previously suggested and flash return to stock in Odin- link here
Click to expand...
Click to collapse
Awesome. The wedding made me forget about my phone but now that it's over I'm missing it.
I will flash to stock and re-root.
Sent from my Nexus S 4G using XDA App
So I'm getting tired of waiting for Sprint to roll out the damn ICS OTA...and even when they do, the Touchwiz leaks I've seen don't look terribly interesting. So I'm considering going to CM9 Alpha 2, having already experienced it on my HP Touchpad and loved it.
My original thought process was: backup all apps and settings, use QBking's guide to install CWM, do an additional nandroid backup and move that onto my PC, and install CM9 A2.
My problem is that I'm currently on completely stock Gingerbread EL29. No root. So I can't use Titanium Backup in case I have to go back to GB. I guess theoretically then I could go: Stock -> Stock Root -> Titanium Backup -> CM9A2...but I'm aware that you install CWM as part of the CM9 installation, so trying to shove TB into the mix might be redundant.
My questions are the following:
1. Is a nandroid backup sufficient for this kind of move, or should I be looking to fit Titanium into the mix as well? My understanding is that Titanium would be more or less required to actually get those apps to cross the GB-ICS threshold, short of downloading them all again. But it seems like more work.
2. QBking has videos on how to go from stock GB to CM9A2. But what do I do if I want to go back to EL29 GB, on the offchance I decide to go for Sprint's OTA?
3. Assuming I do go back, can the nandroid backup I made before installing CM9 be used to restore my stock GB settings (after I reinstall the EL29 kernel), or will that brick my phone?
Thanks in advance.
Aganar said:
So I'm getting tired of waiting for Sprint to roll out the damn ICS OTA...and even when they do, the Touchwiz leaks I've seen don't look terribly interesting. So I'm considering going to CM9 Alpha 2, having already experienced it on my HP Touchpad and loved it.
My original thought process was: backup all apps and settings, use QBking's guide to install CWM, do an additional nandroid backup and move that onto my PC, and install CM9 A2.
My problem is that I'm currently on completely stock Gingerbread EL29. No root. So I can't use Titanium Backup in case I have to go back to GB. I guess theoretically then I could go: Stock -> Stock Root -> Titanium Backup -> CM9A2...but I'm aware that you install CWM as part of the CM9 installation, so trying to shove TB into the mix might be redundant.
My questions are the following:
1. Is a nandroid backup sufficient for this kind of move, or should I be looking to fit Titanium into the mix as well? My understanding is that Titanium would be more or less required to actually get those apps to cross the GB-ICS threshold, short of downloading them all again. But it seems like more work.
2. QBking has videos on how to go from stock GB to CM9A2. But what do I do if I want to go back to EL29 GB, on the offchance I decide to go for Sprint's OTA?
3. Assuming I do go back, can the nandroid backup I made before installing CM9 be used to restore my stock GB settings (after I reinstall the EL29 kernel), or will that brick my phone?
Thanks in advance.
Click to expand...
Click to collapse
Hello! Welcome to the AOSP club.
1. Restoring data is usually a no-no for these ROMs because they might cause force closes and slow downs etc. Ultimately, your mileage will vary, but I wouldn't try because
AOSP roms automatically install all the apps you have installed from the market! It's an awesome feature. If some apps aren't automatically installed, then you can find them in data/app or system/app of your nandroid and push it through root explorer or manually install them
2. I would head over the dev section and look for sfhub's oneclick el 29 root. Whenever I want to flash an ICS rom and I'm on ICS, I first use sfhub's oneclick to go back to stock rooted gingerbread, then I go about and install stock el26 cwm and flash etc etc. I don't know if stock root can accept OTA, but I'm sure you'll find a way to back to stock stock in that thread, or in the sticky of dev section that says Auto Root package.
3. It will brick your phone. As a general rule of thumb, don't do anything in the recoveries provided by ICS Roms, as over the past month the E4GT community have seen a high rise in bricks due to them. It will hopefully be resolved once samsung released ICS Source for epic 4g touch, and we can get a real kernel to mess with.
Good luck and have fun! Remember, once you go AOSP, you can never go back.
Why cm9 rather than a leaked version of ics? Im not trying to be an ass or concince you otherwise just curious. From my viewpoint the leaks are stable and some are in odin so its baaically a 1 click install after rooted? Everything about an alpha version makes me nervous and cm9 doesnt seem ready to me so i wonder if im missing something.
Sent from my SPH-D710 using Tapatalk
cm9
someguyatx said:
Why cm9 rather than a leaked version of ics? Im not trying to be an ass or concince you otherwise just curious. From my viewpoint the leaks are stable and some are in odin so its baaically a 1 click install after rooted? Everything about an alpha version makes me nervous and cm9 doesnt seem ready to me so i wonder if im missing something.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
u must not have used a2 because there is less wrong with it than any tw leak there has been ....
just because its a alpha doesnt mean anything its a daily for alot of people almost everything works ....even stuff you will never get on tw like naitive tether and blue tooth controllers like ps3 wii etc
Well I went ahead and did it. No issues to report just yet.
A few post-CM9 install questions though:
1. How do I set speed dials on my phone contacts? I've been searching around and can't quite find it.
2. After ODIN'ing the phone but before installing CM9, I was able to boot to CWM recovery by turning the phone off then holding vol-up + power. But now when I do that it boots into Android recovery. How do I boot to CWM recovery again?
Aganar said:
2. After ODIN'ing the phone but before installing CM9, I was able to boot to CWM recovery by turning the phone off then holding vol-up + power. But now when I do that it boots into Android recovery. How do I boot to CWM recovery again?
Click to expand...
Click to collapse
This is my first Samsung. I have been on HTC until now. I have been wondering the same thing about recovery. I also tried to reinstall CWM from the included Rom Manager it just freezes. Also, I had a problem this morning where I had to use ODIN to put CWM back on and I wiped cache and dalvik and then it would no longer boot. I tried to restore my back up and the same thing. Just froze at boot screen. I had to start over. Luckily I had a pretty current Titanium backup to quickly put my programs back on it.
So, I have the same question as you about CWM and also wiping cache/delvik and restoring the backup.
caseyatbt said:
This is my first Samsung. I have been on HTC until now. I have been wondering the same thing about recovery. I also tried to reinstall CWM from the included Rom Manager it just freezes. Also, I had a problem this morning where I had to use ODIN to put CWM back on and I wiped cache and dalvik and then it would no longer boot. I tried to restore my back up and the same thing. Just froze at boot screen. I had to start over. Luckily I had a pretty current Titanium backup to quickly put my programs back on it.
So, I have the same question as you about CWM and also wiping cache/delvik and restoring the backup.
Click to expand...
Click to collapse
Never touch rom manager for this phone as of now it is not compatible and could brick you. To answer both of your questions about recovery, I do not recommend flashing a different kernel with CM9 the dev did this for your own safety to prevent bricks, and they're really is no need for it on CM9 until you need to update it. Play safe and save your phone, try to save time and you'll brick it
O...k...
That poses problems for my next question. Namely, my signal seems to have taken a nose-dive since installing ICS. I don't know if the signal has actually degraded, since I'm no longer on a Touchwiz-based ROM, or if it only seems like it's degraded, because perhaps the ICS signal detector is more accurate than the GB one and my signal indicator was incorrect before. But I just had a few calls earlier today and there was more static than I'm used to.
So, how do I go about getting another PRL? The workaround I saw for that involved "flashing" a version of the stock kernel onto the SD card long enough to get another one. But if I can't get into CWM...
Can any one answer why I can't restore a CWM backup or even reboot after performing cache or dalvik wipe? I really like this phone, but it sure seems like rooting/recovery/roms work the same as it did on my HTC phone.
Aganar said:
So, how do I go about getting another PRL? The workaround I saw for that involved "flashing" a version of the stock kernel onto the SD card long enough to get another one. But if I can't get into CWM...
Click to expand...
Click to collapse
caseyatbt said:
Can any one answer why I can't restore a CWM backup or even reboot after performing cache or dalvik wipe? I really like this phone, but it sure seems like rooting/recovery/roms work the same as it did on my HTC phone.
Click to expand...
Click to collapse
Here's a link to an FC22 CWM Recovery. ODIN this guy into your phone - http://forum.xda-developers.com/showthread.php?t=1563547&highlight=fc22
@Aganar - The way I've been getting the whole PRL / Profile thing is ---- Get all setup in CM9 the way you like it, fast backup everything via your preferred user land method (titanium, smsbackup, call log backup, etc). Roll back to a Stock GB ROM (calkulin EL29). Update PRL / Profile. Immediately upgrade to ICS but dont wipe the cache. Restore apps & logs from backups. Havent had a single issue...
takes about 10 min round trip.
I guess my concern is, if the flash from GB to ICS is what caused the signal degradation in the first place, why would flashing back to GB in order to update the PRL have any benefit, if I have to flash back to ICS again?
You won't lose the PRL update after you reflash.
---------- Post added at 08:35 PM ---------- Previous post was at 08:35 PM ----------
CyberMacGyver said:
Here's a link to an FC22 CWM Recovery. ODIN this guy into your phone - http://forum.xda-developers.com/showthread.php?t=1563547&highlight=fc22
Click to expand...
Click to collapse
Are you sure? There are all sorts of warnings about that recovery and ICS.
I have been looking around for about an hour or two trying to find a solid tutorial on how to install a custom recovery to install new Roms. I flashed my phone onto Virgin Mobile on FH13. It seems to me that there is more than meets the eye to installing a recovery on this phone. I really don't want to mess anything up at all. Could anyone guide me the right way as to how I can get CWM on my phone? I appreciate any help you can give me. Thanks!
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
RainMotorsports said:
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
Click to expand...
Click to collapse
Also new to the e4gt, im currently rooted on fh13.
say i want to flash paranoidandroid, which kernel (which includes recovery?) would you recommend?
also this is either flashed from odin (pc) or can be done through mobile odin?
then once kernel is flashed, i can then reboot into recovery, wipe and flash rom/gapps?
sorry for all the questions, just want to make sure!
bongzilla said:
Also new to the e4gt, im currently rooted on fh13.
say i want to flash paranoidandroid, which kernel (which includes recovery?) would you recommend?
also this is either flashed from odin (pc) or can be done through mobile odin?
then once kernel is flashed, i can then reboot into recovery, wipe and flash rom/gapps?
sorry for all the questions, just want to make sure!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1953783
RainMotorsports said:
Recovery is packed into the kernel on this phone. Flash a kernel tar through ODIN if you want, it will trigger the yellow triangle though. If your already rooted you could use Mobile ODIN. If you already have some form of custom recovery and are just trying to switch up you can flash the kernel zip in recovery.
rwilco has pretty much every kernel for every purpose but since your on stock you will either want a repacked stock or custom tw kernel - http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/ICS
If your unfamiliar then keep asking questions. Our phone has a bug in its eMMC firmware triggered during format operations on the stock kernel as of Android 4.0. The specifics are detailed but all you really need to know is grab a kernel with a safe recovery, or even going as far as AGAT's custom kernel which has more work around in place to prevent a factory reset or rom install from turning your phone into a super brick.
Click to expand...
Click to collapse
My phone already has root. Everything else is stock. 4.0.4, build FH13, with no custom recoveries.
I don't understand what you mean in your second paragraph with "repacked stock" or "custom tw kernel".
I am completely lost as to where I should be going. My plan is to install this rom: http://goo.im/devs/Shabbypenguin/E4GT-Nightlies
How would I go around to getting this on my phone?
Also, what about this rom: http://forum.xda-developers.com/showthread.php?t=1810315
I am not sure which rom runs the fastest and most efficient. There are so many kernels for so many things, I have absolutely no idea which kernel to flash and how to flash it.
EDIT: So I have done some more reading up and I THINK I can starting to understand some of it. I assume the steps are to:
1. Install Mobile Odin Lite on my phone.
2. Flash the EL26 kernel on Odin Lite. Link to kernel: http://forum.xda-developers.com/showthread.php?t=1662295 (first kernel on the page)
3. This part I am kinda lost. Not sure if that kernel installed a new recovery or not. I assume I just reboot and go into recovery.
4. Nandroid a backup of my ICS stock that is on now? Can I even go back to this stock backup after putting on a new Rom? Which kernel would I need to install backup of stock?
5. Wipe data, dalvic, and install new Rom using instruction it came with. My problem is I want to run this Rom: http://goo.im/devs/Shabbypenguin/E4GT-Nightlies and it has no instructions. I assume you just wipe data and dalvic?
6. flash Rom, then flash Gapp? It doesn't have a link for any of the Gapps, so either I have to find a link to download Gapp or that rom already comes with it? Not sure.
7. Reboot into new Rom? Not sure if I missed a step or not.
Another question I have is with the kernels. Can I just leave it on the EL26 kernel for daily use of the phone? Say I want to install maybe cm10 next, do I just keep it on EL26?
Sorry for the spam of questions. I like to be 100% certain.
Best bet if your trying to install CM9 is to go to the EL26 CWM kernel as all of the AOSP rom instructions dictate. Using the EL26 kernel means your phone will only boot to Download and Recovery as it will only boot gingerbread roms.
Download the nightly you want to the device and then flash the EL26 CWM kernel in Mobile ODIN. After its all over with you might need to battery pull if you messed up booting into recovery and then boot into recovery (power + vol up). Install the rom. Install gapps. Wipe cache/dalvik but as I will recommend below you should just backup everything and a full wipe.
You can nandroid if you want but it will be making a copy of the ICS rom you have with the EL26 kernel on it so it is literally a restore to the point your starting from not where you were just before that. Its still a good idea if your afraid of losing things. I would use Super Backup from the market to backup your Contacts, Call Logs and MMS. Wipe cache and dalvik and all that. But realisticly you should backup your apps and data if you have Titanium Backup and start fresh just factory reset after your on CM9. Restore your apps with data (no system data) after that. A clean install will present the least of issues, even the Samsung updates from one rom to another are not without issues.
You can not boot anything but gingerbread with EL26 and once you install a rom you will be on the kernel with that rom. So you will have a Linux 3 android kernel with cwm 6 if you go with a CM9 nightly. From there you can flash the next nightly or the next beta etc. Older stuff will not flash from your new setup as AOSP roms have switched to a new device name in the build.prop.
As far as gapps here it is - http://goo.im/gapps/gapps-ics-20120429-signed.zip and don't forget to put this on the device ahead of time or you will have to mount usb and transfer using the pc in recovery.
RainMotorsports said:
Best bet if your trying to install CM9 is to go to the EL26 CWM kernel as all of the AOSP rom instructions dictate. Using the EL26 kernel means your phone will only boot to Download and Recovery as it will only boot gingerbread roms.
Download the nightly you want to the device and then flash the EL26 CWM kernel in Mobile ODIN. After its all over with you might need to battery pull if you messed up booting into recovery and then boot into recovery (power + vol up). Install the rom. Install gapps. Wipe cache/dalvik but as I will recommend below you should just backup everything and a full wipe.
You can nandroid if you want but it will be making a copy of the ICS rom you have with the EL26 kernel on it so it is literally a restore to the point your starting from not where you were just before that. Its still a good idea if your afraid of losing things. I would use Super Backup from the market to backup your Contacts, Call Logs and MMS. Wipe cache and dalvik and all that. But realisticly you should backup your apps and data if you have Titanium Backup and start fresh just factory reset after your on CM9. Restore your apps with data (no system data) after that. A clean install will present the least of issues, even the Samsung updates from one rom to another are not without issues.
You can not boot anything but gingerbread with EL26 and once you install a rom you will be on the kernel with that rom. So you will have a Linux 3 android kernel with cwm 6 if you go with a CM9 nightly. From there you can flash the next nightly or the next beta etc. Older stuff will not flash from your new setup as AOSP roms have switched to a new device name in the build.prop.
As far as gapps here it is - http://goo.im/gapps/gapps-ics-20120429-signed.zip and don't forget to put this on the device ahead of time or you will have to mount usb and transfer using the pc in recovery.
Click to expand...
Click to collapse
Ah, I read it twice and now it makes more sense. I have a pretty good idea of what to do now.
Put rom and gapp on phone, install EL26, backup, full wipe, flash rom and gapp, rom will install new kernel for me, then just reboot.
Last question, I just want to make sure. What exactly is a full wipe on this phone. I have done plenty of full wipes on the evo 4g. I am just asking because I hear some people have problems when they do a full wipe.
I really appreciate your help. Thank you!
Sorry if I jumbled everything together in my post by the I was running out the door. But this Hurricanne has stopped that and I regret not taking my time.
Well what I mean is a factory reset which formats /Cache and /Data. When you install the rom its going to format /System prior to writing the new firmware/rom. /Data has all your user apps, their data and your information etc. This does not wipe the Internal SD or the External SD though at times a line saying it was does come up in CWM.
Just don't do a Factory reset on the stock kernel you are on now, its fine on EL26 its fine on the kernels that come with the CM9 nightlies. Super Backup apparently does app's now too. I have never used it since I have Titanium Backup Pro but figured its also worth mentioning.
A note on turning back. As I said before if you flash the EL26 CWM kernel you wont be able to boot the ICS rom installed on the phone. At that point to go back instead of forward you can flash the FH13 kernel in desktop ODIN or the zip in CWM and you will have the FH13 kernel instead of EL26 and be back where you were. But once you flash the EL26 CWM kernel your goal at that point is flashing your rom of choice in CWM and not things like booting the phone.
You should be "okay" coming from a dirty install just wiping cache. But you may never know if a problem your having is the rom or some left over data unless you go clean and factory reset. Its a choice and its also a choice you can make later as you can always reset later. I would back up anything important first before doing any of this. Not so much a worry about bricking, as just about any normal situation will be recoverable, but more so to the point of if you have to wipe the phone and start from scratch.
RainMotorsports said:
Sorry if I jumbled everything together in my post by the I was running out the door. But this Hurricanne has stopped that and I regret not taking my time.
Well what I mean is a factory reset which formats /Cache and /Data. When you install the rom its going to format /System prior to writing the new firmware/rom. /Data has all your user apps, their data and your information etc. This does not wipe the Internal SD or the External SD though at times a line saying it was does come up in CWM.
Just don't do a Factory reset on the stock kernel you are on now, its fine on EL26 its fine on the kernels that come with the CM9 nightlies. Super Backup apparently does app's now too. I have never used it since I have Titanium Backup Pro but figured its also worth mentioning.
A note on turning back. As I said before if you flash the EL26 CWM kernel you wont be able to boot the ICS rom installed on the phone. At that point to go back instead of forward you can flash the FH13 kernel in desktop ODIN or the zip in CWM and you will have the FH13 kernel instead of EL26 and be back where you were. But once you flash the EL26 CWM kernel your goal at that point is flashing your rom of choice in CWM and not things like booting the phone.
You should be "okay" coming from a dirty install just wiping cache. But you may never know if a problem your having is the rom or some left over data unless you go clean and factory reset. Its a choice and its also a choice you can make later as you can always reset later. I would back up anything important first before doing any of this. Not so much a worry about bricking, as just about any normal situation will be recoverable, but more so to the point of if you have to wipe the phone and start from scratch.
Click to expand...
Click to collapse
That clarified a lot, thanks.
So I did it all. I did a factory reset from the new kernel. did dalvic also. I installed the new rom and gapp. Problem is that once I reboot, it shows the Galaxy SII screen, then goes into a black screen. I can't turn it back on again, so I remove the battery and it can restart. Does the same thing though. I followed your instruction and http://e4gtcm.blogspot.com/p/cm9-install-guide.html
What did I do wrong? I am worried I messed up my phone completely.
EDIT: So I went back into recovery and it was now a new version of CWM. I did everything over again; factory reset, cache, dalvic, and it is doing the same thing. Boots up "Galaxy SII" screen, then a black screen. It seems to still be on in the black screen seeing that it doesn't "turn" on again. I can hold if for 15 second or so for it to reset and does the same thing. Why is there a black screen?
Sorry for not checking back. Your probably freaking right now lol but relax your at a good point everything is fine.
Either a bad download or the nightly you went with happens to be a baddy. I am still on 10/20 I was gonna flash 10/28 today but the weather is screwing with me. goo.im seems pretty slow today.
Download another, battery pull and hold vol up + power until it hits recovery then go into mounts and mount usb storage hook a usb cable to the pc and copy over another build. I would say try 10/20 just because it works pretty good but that won't stop another bad download in which case you have to try try again.
Worst case from here we can just odin you back to stock rooted FH13 or your choice of other. Your phone is fine from what you have told me so far. I can upload one of the builds I have if you think ti would help any.
RainMotorsports said:
Sorry for not checking back. Your probably freaking right now lol but relax your at a good point everything is fine.
Either a bad download or the nightly you went with happens to be a baddy. I am still on 10/20 I was gonna flash 10/28 today but the weather is screwing with me.
Download another, battery pull and hold vol up + power until it hits recovery then go into mounts and mount usb storage hook a usb cable to the pc and copy over another build. I would say try 10/20 just because it works pretty good but that won't stop another bad download in which case you have to try try again.
Worst case from here we can just odin you back to stock rooted FH13 or your choice of other. Your phone is fine from what you have told me so far.
Click to expand...
Click to collapse
Phew! I was pretty positive that I could still get back to something working, just my paranoid self was getting tense. I got 10/28. I guess I will do 10/20. Do you know what the other updates have? I would hate to install something that isn't working its most efficient.
Again, thank you so much. You were of great help! Good luck with the weather issue. Hope you're safe!
I stopped following chris's experimentals so i am not sure what the most recent focuses have been. The Nightlies have whatever code was commited. They are built automatically and can range from very stable to not booting at all. I dont have any of the links on me but someone can get it to you. Reading commits is not exactly 100% user friendly especially if your not a developer. But they often have clues. I would follow the CM9 Beta thread and the CM9 User Support Threads - http://forum.xda-developers.com/showthread.php?t=1874374 and http://forum.xda-developers.com/showthread.php?t=1720771
I used to DL nightlies from work over 3g or 4g all the time and would get a bad dl and end up in situations where even my experienced self felt like I couldn't fix it till I got home and always got the phone running within an hour without the assistance of a near by pc.
I am uploading 10/20 to my server just in case its in Chicago so if your away from the weather it should be unaffected for the most part. Glad its not in NY anymore.
EDIT - http://android.rainmotorsports.net/10-20-CM9-d710-KANG.zip the md5 hash as I have it is 66246125ACDBEF2EBF2144E0CBFEBB7B and it matches the md5 listed on goo.im
RainMotorsports said:
I stopped following chris's experimentals so i am not sure what the most recent focuses have been. The Nightlies have whatever code was commited. They are built automatically and can range from very stable to not booting at all. I dont have any of the links on me but someone can get it to you. Reading commits is not exactly 100% user friendly especially if your not a developer. But they often have clues. I would follow the CM9 Beta thread and the CM9 User Support Threads - http://forum.xda-developers.com/showthread.php?t=1874374 and http://forum.xda-developers.com/showthread.php?t=1720771
I used to DL nightlies from work over 3g or 4g all the time and would get a bad dl and end up in situations where even my experienced self felt like I couldn't fix it till I got home and always got the phone running within an hour without the assistance of a near by pc.
I am uploading 10/20 to my server just in case its in Chicago so if your away from the weather it should be unaffected for the most part. Glad its not in NY anymore.
EDIT - http://android.rainmotorsports.net/10-20-CM9-d710-KANG.zip the md5 hash as I have it is 66246125ACDBEF2EBF2144E0CBFEBB7B and it matches the md5 listed on goo.im
Click to expand...
Click to collapse
I just got it downloaded. It is now up and running perfectly. I appreciate all your help man, thanks a bunch. I live in Washington state. So the weather wont affect me.
Good evening all. I hope this is the right forum to post my question about recovery for my e4g touch. I recently rooted my phone and my phone is currently on the fi27 build. Is there a recovery i can put on there now to go ahead and start flashing ruins, or will i have to wait for qbkng77 to post his video on you tube on putting cwm recovery on fi27 rooted e4g touch? Thanks in advance for the help!
Sent from my SPH-D710 using xda app-developers app
n1stunna84 said:
Good evening all. I hope this is the right forum to post my question about recovery for my e4g touch. I recently rooted my phone and my phone is currently on the fi27 build. Is there a recovery i can put on there now to go ahead and start flashing ruins, or will i have to wait for qbkng77 to post his video on you tube on putting cwm recovery on fi27 rooted e4g touch? Thanks in advance for the help!
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I assume you do the same thing as I did. Get the EL26 kernel and flash it with Mobile Odin. I would wait on someone else to confirm that though.
Another really quick question. I want to overclock my phone. I tried using setcpu and the overclocker it came with. It only goes to a max of 1200 but I know it can go higher. I am guessing I need another kernel. What kernel can I use?
joshlete said:
Another really quick question. I want to overclock my phone. I tried using setcpu and the overclocker it came with. It only goes to a max of 1200 but I know it can go higher. I am guessing I need another kernel. What kernel can I use?
Click to expand...
Click to collapse
You either need a kernel with built in over clock support(you'd see the CPU slider go up to 1400-1600 automatically if it was). Or a kernel that supports over locking in tegrak, which you "load over clock module" with in tegrak.
Both Kuban kernel and some of Agats kernels have built in support, mine you need to use tegrak as I have not added built in yet
You can get them all in rwilco's (awesome) kernel repository stickied in development
Sent from my SPH-D710 using xda premium
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
bezerker said:
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
Click to expand...
Click to collapse
it wasn't just latest update, people were taking about this issue for weeks now... not sure what the fix will be I think Odin back to stock... supposedly is a TWRP problem and it doesn't happen in CWM but I heard CWM has its own share of problems...
Sent from my SGH-M919
aLdaRiS said:
it wasn't just latest update, people were taking about this issue for weeks now... not sure what the fix will be I think Odin back to stock... supposedly is a TWRP problem and it doesn't happen in CWM but I heard CWM has its own share of problems...
Sent from my SGH-M919
Click to expand...
Click to collapse
Interesting.
I was about to try odin'ing back to stock and reflashing twrp.
The only thing I wonder if may be related is when you restore a backup with TWRP it gives options of all sorts of partitions besides system/data/cache etc... preload etc. It's possible it doesn't like mucking with those.
Interesting to note: If I install a CM nightly, it will allow me to reboot. Wickedv2 or my backup of wickedv2 no go.
Testing further.
Maybe when you flashed CM it messed with a partition or something. I would suggest to ODIN back to stock and then re-root and try again.
saldebot said:
Maybe when you flashed CM it messed with a partition or something. I would suggest to ODIN back to stock and then re-root and try again.
Click to expand...
Click to collapse
Righto. Sounds like a valid idea.
Unfortunately, the download links in konane's thread are timing out for me mid download. Tragic.
Managed to snag it from another location. Flashed back to stock firmware/recovery via odin.
Letting it boot to see what it does.
EDIT:
That did it.
Restored my backup and most everything is working correctly (restoring my titanium backup of all apps now.)
Few things were messed up (swiftkey was missing a language pack etc?)
But looks like AOSP/AOKP roms do something to the partition table as you said that requires flashing back the original.
Good to know and thanks for the help!
Don't wipe system in twrp.
makomek said:
Don't wipe system in twrp.
Click to expand...
Click to collapse
Does this cause issues? Didn't know.
I found that only CM nightlies would reboot fine. restoring via odin stock official then going back and putting on wicked again seemed to work to fix it and I can now reboot in a touchwhiz based rom.
re: stuck
bezerker said:
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
Click to expand...
Click to collapse
If you want a 95% sure way of fixing it so it boots completly,
then try this, it usually always works.
Get the phone into recovery mode twrp/cwm does not matter.
Then simply do a "factory reset" and I am fairly certain that it
will boot completly, I have seen this issue so many times
already not just here in the S4 thread but also in the S3.
The factory reset will not delete any of your music, videos and pictures.
Good luck!
Ok I wrote this for the OP of my ROM because the issues some people were PMing me about were just plain out dumb, This phone has been out quite a long time and still almost every thread I goto, you got people flashing in way's I didn't even know were possible and posting weird issues that were not being reproduced by the community. so I'm just gonna post this guide for all the developers sake and in hopes the people that actually need this information, receive it before posting and clogging up development threads
If you're having issues on rom's that no one else is reporting, or the DEV has not reproduced on his phone, read the following.
1) Full wipe
2) Do not restore System data or data from CWM
3) Do not dirty flash from other ROM's
4) When was the last time you did a odin to stock? this is important in my opinion and I'm not saying you need to do one but I just want to explain that custom zip's that I make and other dev's make in the shape of "roms" only affect
a few partitions on your device, other's do not get touched and can get messy/corrupt over the months (This explains why the GPS icon disappears in some peoples cases during rom switch) and this is why I get posts in this thread about people wondering why their baseband hasn't been updated after flashing my rom when my post states "MF1"
With this being said my personal rule of thumb is to odin to stock latest and then boot into stock recovery and factory reset, wipe cache/dalvik (BACKUP YOUR SD CARD TO YOUR COMPUTER), this gives your phone fresh partitions everywhere, a fresh system to root and the latest bootloader (which you need for any AOSP 4.2 rom). This is also a good time to unlock your phone if you have not already, then reroot and install custom recovery, update the recovery if need be and flash again on a brand new system. here are my steps
1) backup all user apps and data with titanium backup, DO NOT BACKUP SYSTEM APP'S
2) backup internal storage onto PC
3) Odin to stock latest
4) wait for phone to boot then reboot into stock recovery and full wipe and clear all cache
5) reboot and root the phone and custom recovery
6) flash away and put what you need on your internal storage back onto your phone via usb, see my 2nd set of instructions below
this fixes more issues then you will realize. some of the way people flash rom's on XDA and complain to me with problems is rather funny considering I have the install instructions in the OP, not to mention many of you rooted your phone when you first got it in the ICS 4.0.4 day's and haven't done an odin to stock jellybean to update all your partitions including your bootloader, now I will go over my every day flashing step's.
1)backup all USER APPS/DATA with titanium backup, DO NOT BACKUP SYSTEM APP'S (skip this if you did a odin flash to stock)
2)reboot recovery
3)nandroid (skip this if you did a odin flash to stock)
4)factory reset, wipe system, wipe both cache/dalvik
5)install rom
6)boot system
7)*(OPTIONAL) reboot to install a kernel now if needed, always wipe cache/dalvik and fix permissions after installing a kernel
8)setup phone and download titanium backup from the market
9)restore all user apps and data (you will have to put the titanium backup folder that is backed up on your computer back onto your internal storage via usb first)
Every 6 months, backup internal storage to PC and I odin to stock, much like formatting a computer
6 months is actually a long time considering how much I flash, but this device can take a beating let me tell you =P
I DO THIS WITH EVERY ROM I INSTALL, AOSP or TW
Great info, that is actually my same process when I have an issue with anything
Good read. A lot of common sense for seasoned flashers, will be great for people who are unsure.
Sent from my SGH-T999 using xda app-developers app
KorGuy123 said:
Good read. A lot of common sense for seasoned flashers, will be great for people who are unsure.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
thanks man, hoping this gets a sticky.
Danvdh said:
thanks man, hoping this gets a sticky.
Click to expand...
Click to collapse
I'll add it to my sticky
Galaxy S3 / AoCP / V4A / Turbocharged
s3 unrooting issues
I have been having some big problems with unrooting my telus SGH I747 Galaxy s3. I have flashed the stock rom using odin, did a factory reset and wiped cache and everytime i reboot it loads up the same roms i had on there at first. I have had a lot of issues with roms as well such as slow messaging times, echoing voice calls using AOKP and when i use an AOSP rom i cant connect to my phone carriers data connection at all. I read this form and decided its probably a good idea to re root as you said due to updates or whatever else but now im runing into this issue. I have ask on other forms and no one seemed to have heard of this issue. If anyone has any ideas or knows a fix i would really appreciate the help.
Custom ROM data issue
dannyteo14 said:
I have been having some big problems with unrooting my telus SGH I747 Galaxy s3. I have flashed the stock rom using odin, did a factory reset and wiped cache and everytime i reboot it loads up the same roms i had on there at first. I have had a lot of issues with roms as well such as slow messaging times, echoing voice calls using AOKP and when i use an AOSP rom i cant connect to my phone carriers data connection at all. I read this form and decided its probably a good idea to re root as you said due to updates or whatever else but now im runing into this issue. I have ask on other forms and no one seemed to have heard of this issue. If anyone has any ideas or knows a fix i would really appreciate the help.
Click to expand...
Click to collapse
So scrap the unrooting issue i have that figured out now, i just reinstalled the rom and again it doesnt have data, it is the deadly venom rom, anyone else that i know who is using this rom has absolutely no problem. I have tried a few fixes i have found via youtube, google, etc.... but none were successful. If anyone knows a fix or has any ideas please let me know.
I have an I747M S3 from a friend and trying to get it back to stable stock. It had lost it's IMEI and some NVdata corruption but I was able to resolve that searching the forums, But it has issues with apps crashing and rebooting quiet frequently. It can sometimes go feeling pretty stable ofr awhile then just kind of blows up. I have cleared away the flash counter and restored factory stock images from Odin and Keis, still having the issues. Is there a partion or something that could be getting missed? Or possible further problems related to the NVdata issues?
if you have any ideas I would appreciate it.
I used twrp to back up system, data, and boot, should I still use titanium back up to back up anything else, or is that enough to be relatively safe?