Related
ROOTSide ROM
Base Flipside ROM with root/busybox/unknown sources enabled. Only thing different in this rom than rooting it yourself is you get to check/uncheck unknown sources. Yes, that means you can turn unknown sources ON and OFF! I have a clockworkmod recovery folder zipped up for distribution, but I want to post a full-fledged ROM zip file for the masses. PM me, and I will send you the ZIP file that I have right now.
What you get:
base install for the flipside (AT&T) with motoblur ready to set up. It is the exact same thing as doing a factory reset, but you get all the benefits of superuser with busybox and the addead feature of having unknown sources checkbox in the settings.
I will work towards a deoxed version this weekend as well.
No custom bootscreen (yet). No custom anything, really.
Almost There
I am currently in the middle of Deodexing the image. I have added in wifi tethering, and ensured it will have superuser and busybox pre-packaged. Next step is pushing this to my wife's phone and not having her get a pretty brick in return. If all goes well, I will be posting the image by morning light (CST).
Fingers Crossed!
Well
Things didn't go too well with my first build attempt. Appears to be a permission issue with the /system folder. I will sleep on it, and give it a second go in the morning. Sorry for the apparent "tease". If you want a faster build, I could use some other devs working with me.
Hey man, sounds like you're doing great! Keep it up...I already found a way to get the root with unknown sources checked, so i'm just gonna wait for the deoxed version! Hope it goes well as you try again.
Current Issues
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Me too...good luck!!
jonsjava said:
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Click to expand...
Click to collapse
Both of those files are att/moto bloat... just be rid of them
Sent from my MB508 using XDA App
Glad to see some work on this device, I love the form factor but it's obviously not very popular with devs...
Very interested to see this come around. I would like to streamline the wife's phone. Her battery life is a 1/3 of my rooted and flashed X10. Sadly though I am NOT a Dev nor even a cook.
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
so I was curious, I was able to get to unlock mode with an sqlite thing and it worked just fine for me, but have you been able to knock out the bloat and stuff? cause it sounds like the makings of a custom rom lol
you know what the turtle said.. slowly but surely I will win this race
jonsjava said:
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
Click to expand...
Click to collapse
Several ppl have said they have run into this problem...don't know what the deal is...
Is it possible to get CM7, or it's a problem with a locked kernel?
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
jonsjava said:
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
Click to expand...
Click to collapse
sounds good man, keep us posted on progress!!
So check this out...I messaged the guy at modmymobile and asked how things were going becuase I heard people were having problems getting an updated CMW and this is his response:
"been sittin on the updated cwm recovery binaries and been draggin my feet/takin a break the past week or 2. i'll throw something out soon, but cant commit to a timeframe, sorry."
Looks like things are on the up and up...stay patient everyone
GOOD JOB!!!,
We are waiting for the rom
Dukenukemx said:
Is it possible to get CM7, or it's a problem with a locked kernel?
Click to expand...
Click to collapse
I can't install CM7, it reboots and locks up, then I have to reinstall froyo. It never worked when I had eclair either.
Hello all,
So I bought my HTC Wildfire S Virgin Mobile on black friday like everybody else. I waited a few days and then rooted. And then I had the brilliant idea to try installing the CM 7.1 Mod for it. And well, I didn't do a Clockwork Backup, and well, it didnt work very well. The phone got stuck on the HTC screen. So finally I installed a different ROM, JikantaruROM, and I managed to get past the bootscreen but I can't use my carrier anymore. So I was wondering if anybody could either tell me how to flash CM 7.1 Unoffical release to my phone, or if anybody knew a way I could get back to the original Virgin Mobile software. It seems that you have all the other stock roms, so I would REALLY appreciate if someone could share the Virgin Mobile rom too.
Thanks in advance,
Wieland959
Seconded. Although I think mine is in a slightly worse case; I kept flashing roms and ended up in a state where it turns on, screen remains black, then the phone vibrates three times and evidently does nothing. So Wieland959, I'd advise you to stop flashing until someone posts the ROM.
And if someone could let me know how to recover from my current state, I'd very much appreciate it.
thesnaz said:
Seconded. Although I think mine is in a slightly worse case; I kept flashing roms and ended up in a state where it turns on, screen remains black, then the phone vibrates three times and evidently does nothing. So Wieland959, I'd advise you to stop flashing until someone posts the ROM.
And if someone could let me know how to recover from my current state, I'd very much appreciate it.
Click to expand...
Click to collapse
Your in the same boat I was just in. My solution was to go back to radioshack with the receipt and tell them it just turned off and wouldnt turn back on. Just doing the 3 vibrations. I did spend hours trying to search about how to fix it, but I dont think theres a way unless you use a jtag hookup and some sort of fancy programmer.
@Wieland959, If you want. I just tried to do the OTA update through the settings on the phone itself. It would let me download the file(I believe it should be flashable through the cwm recovery), but when I tried to let the phone install the file, I would get the android with the exclamation mark after the reboot. Ill try to post here, if it will upload. But......
DISCLAIMER!!!!
I take no responsibility for anyone damaging their phone using the file here. This file, as far as I know, should only work with the Wildfire S Virgin Mobile USA CDMA model A510C as this is the phone the file was downloaded from.
Thank you for the file, but I couldn't flash it. What might work though, if you are willing is, if you have rooted your phone, to make a cwm backup and upload that here. From there I should be able to recover and then factory wipe my phone. But thank you anyways for the file. I will keep kicking until the phone doesn't boot.
How are you planning on restoring from backup if the phone doesn't even boot?
Sorry, I'm new to this...
thesnaz said:
How are you planning on restoring from backup if the phone doesn't even boot?
Sorry, I'm new to this...
Click to expand...
Click to collapse
from the recovery, by holding down the vol down button and power button. then select recovery.
also, im in the same boat as OP haha
Okay. I managed to boot my phone and am able to send/receive texts. The rom I used? http://forum.xda-developers.com/showthread.php?t=1367701] It seems to work pretty well. However, I would still like to have the original rom if someone could still upload it.
VM USA Stock Clockwork Backup
Well, I don't know much about stuff like this, but here is my clockwork mod recovery backup. It's just the stock VM USA w/HTC Sense. I have realized that I deleted the bloatware, so that's the only thing that isn't 100% stock. Hope it helps.
*Unzip the file before placing on you sd card. (Contains the clockwork folder, which contains the backup folder,and then the folder that contains the backup itself.)*
**!! Disclaimer! Please run the activate application upon installing as when you call voicemail, it will call my number. !!**
http://www.mediafire.com/?le6b07dwr865017
---------- Post added at 09:59 PM ---------- Previous post was at 09:54 PM ----------
Wieland959 said:
Okay. I managed to boot my phone and am able to send/receive texts. The rom I used? http://forum.xda-developers.com/showthread.php?t=1367701] It seems to work pretty well. However, I would still like to have the original rom if someone could still upload it.
Click to expand...
Click to collapse
Is this a good rom? I'm looking for some senseless roms that will work with our version of the WFS. will you post if you are able to go back to the Stock Virgin backup that I have posted? Also how much memory is on the rom that you posted?
With the a2sd enabled, you get 150 to 175. It's nice.
Sent from my HTC_A510c
BigChillin said:
With the a2sd enabled, you get 150 to 175. It's nice.
Sent from my HTC_A510c
Click to expand...
Click to collapse
Can I easily switch back to the stock rom via my backup? How do I install it. Sorry that i'm such a newbie. xD
BigChillin said:
With the a2sd enabled, you get 150 to 175. It's nice.
Sent from my HTC_A510c
Click to expand...
Click to collapse
I tried it and found my phone only had 75mb of internal storage available!!! Weird!!
Nevermind I figured out the problem. Ok. Just one question is there anyway I can get the nice clock back from the stock ROM?
Is anybody else having mms issues with the experimental ROM?
brandonhun said:
Can I easily switch back to the stock rom via my backup? How do I install it. Sorry that i'm such a newbie. xD
Click to expand...
Click to collapse
Thanks for the backup! It worked perfect for me!
would you mind if i posted the link on another forum? i know of a couple people looking for a backup aswell.
You should be able to switch back with the recovery no problem. Correct me if I'm wrong, but to install boot into recovery, install from SD, select specific, and select the zip of the rom. Also, I don't have my phone on me so the wording might be a little different.
MMS is a known issue with the rom from what I've read. I don't have it installed personally.
@brandonhun, Thank you so much. You're a life saver. As far as the rom goes, it still have sense on it and there are tons of MMS errors. So just wait and eventually something will pop up.
Wieland959 said:
@brandonhun, Thank you so much. You're a life saver. As far as the rom goes, it still have sense on it and there are tons of MMS errors. So just wait and eventually something will pop up.
Click to expand...
Click to collapse
Just a heads up wieland, when you get a voice mail and you try to check it from the notifications make sure it's your number, because I ended up giving brandonhun a call. Going through the activation app and rebooting fixed the problem.
djsquiggly said:
Thanks for the backup! It worked perfect for me!
would you mind if i posted the link on another forum? i know of a couple people looking for a backup aswell.
You should be able to switch back with the recovery no problem. Correct me if I'm wrong, but to install boot into recovery, install from SD, select specific, and select the zip of the rom. Also, I don't have my phone on me so the wording might be a little different.
MMS is a known issue with the rom from what I've read. I don't have it installed personally.
Click to expand...
Click to collapse
You can post it wherever you want. I'm glad I could help a couple of you!
ScottPomroy said:
Ok. Just one question is there anyway I can get the nice clock back from the stock ROM?
Click to expand...
Click to collapse
I haven't done this ROM change but if its the stock HTC Sense go to personalize and get HTC widgets (perhaps its get more HTC widgets) and you should find an update to the clock widget. That should give you the original clock plus a bunch more new ones.
Sent from my Transformer TF101 using Tapatalkd
Take another peek
Wieland959 said:
@brandonhun, Thank you so much. You're a life saver. As far as the rom goes, it still have sense on it and there are tons of MMS errors. So just wait and eventually something will pop up.
Click to expand...
Click to collapse
Guess what just popped out of the Betty Crocker oven? As close as I could get to stock. Enjoy.
Rob
This is the newest version of Clockwork Recovery- 6.0.1.5 -non-touch
I claim no credit for any of this. I am only posting this because the latest version available on the official ClockworkMod page is still 6.0.1.0.
This recovery was compiled from source, along with a personal CM10 project I'm working on. Please note that this is included with the CyanogenMod source, so anyone building it will end up with the newest recovery image in their OUT folder.
So, for anyone still using Clockwork Recovery, (I do), here you are!
All credit to Koushik Dutta (Koush)--the creator of what I think is still a great recovery.
More info on his work can be found at http://www.ClockworkMod.com/rommanager
Thanks dude!
Here is the touch version of 6.0.1.5 http://d-h.st/1Kk. I built this last night using the recovery builder found here http://builder.clockworkmod.com/ with the 6.0.1.0 version as a base.
EDIT/ I FORGOT TO MENTION. I AM NOT RESPONSIBLE FOR ANYTHING WORKING OR NOT WORKING WITH THIS RECOVERY. I ASSUME NO RESPONSIBILITY FOR BROKEN DEVICES. USE AT YOUR OWN RISK. THANK YOU
myepicyear said:
This is the newest version of Clockwork Recovery- 6.0.1.5 -non-touch
I claim no credit for any of this. I am only posting this because the latest version available on the official ClockworkMod page is still 6.0.1.0.
This recovery was compiled from source, along with a personal CM10 project I'm working on. Please note that this is included with the CyanogenMod source, so anyone building it will end up with the newest recovery image in their OUT folder.
So, for anyone still using Clockwork Recovery, (I do), here you are!
All credit to Koushik Dutta (Koush)--the creator of what I think is still a great recovery.
More info on his work can be found at http://www.ClockworkMod.com/rommanager
Click to expand...
Click to collapse
Is 6.0.1.5 the version that has the option for tar (non-blob) backup?
Yes it has that option
Sent from my Galaxy Nexus using xda premium
TransWarp said:
Is 6.0.1.5 the version that has the option for tar (non-blob) backup?
Click to expand...
Click to collapse
Yes, this version includes both tar and dup (data blob) backup formats. Tar formatting was re-added in 6.0.1.2.
So you can have either quick, large backups; or slower, slimmer backups with this version.
There's also an interesting adb sideload option as well. Not useful for most casual users, however, the more adventurous users will have a purpose for it from time to time.
10characters
FrostyF7 said:
Thanks dude!
Click to expand...
Click to collapse
You are very welcome sir! Thank you for visiting the very first thread that I've ever posted on XDA. Never even started a question thread before. I'm working pretty freaking hard, on personal projects, as well as school stuff, so you should be seeing a lot more from me in the not-too-distant future. I've been looking forward to contributing more for a long time, and I'm excited to give back something with some more substance. I never stop learning at xda. I owe a lot to this place. :fingers-crossed:
myepicyear said:
You are very welcome sir! Thank you for visiting the very first thread that I've ever posted on XDA. Never even started a question thread before. I'm working pretty freaking hard, on personal projects, as well as school stuff, so you should be seeing a lot more from me in the not-too-distant future. I've been looking forward to contributing more for a long time, and I'm excited to give back something with some more substance. I never stop learning at xda. I owe a lot to this place. :fingers-crossed:
Click to expand...
Click to collapse
Thanks for this CWM. The touch version is nice to have, if your device supports it. I have one question though. Is this version still buggy? Any issues so far? Why hasn't it been posted on Koush's site yet? I would give it a whirl but I'm a bit wary; I wouldn't want to mess with my working 6.0.1.0 touch unless I'm 100% positive this has no issues.
Thanks again.
ezeuba said:
Thanks for this CWM. The touch version is nice to have, if your device supports it. I have one question though. Is this version still buggy? Any issues so far? Why hasn't it been posted on Koush's site yet? I would give it a whirl but I'm a bit wary; I wouldn't want to mess with my working 6.0.1.0 touch unless I'm 100% positive this has no issues.
Thanks again.
Click to expand...
Click to collapse
You're welcome. I wholeheartedly appreciate you visiting my thread.
To answer your questions- no, this version is nothing to be afraid of, and definitely not buggy. In fact, the first couple releases of 6.0.x.x were extremely buggy for many people, and 6.0.1.2 was were things seemed to get evened out. If you are still on 6.0.1.0, I would personally suggest updating to at least 6.0.1.2, as it is at least as stable as 6.0.1.0, while adding in a new feature or two. Most issues at the start of v6 releases were about people's backups being extremely slow, and it turned out to mainly be a conflict between Google Play Music and the way the data blob backup folders were executed/cleaned during backup. Google Play Music has a unique way of storing it's music, and it seemed to be responsible for terrible backup times and rebooting during backup(on some devices--never happened to me).
I was using 6.0.1.2 until a few days ago, and everything was always awesome. This version has backups in data blob format going considerably faster for me. It also has an adb-sideload option incorporated ( newest TWRP includes it too). These are the biggest differences, and there is nothing experimental to be wary of. I definitely understand any hesitation, and I think that it's better to be responsible/careful than to be sorry later. As for the exact reason why Koush hasn't put it on the website yet, I couldn't tell you for sure. He's always done releases this way, and if I had to guess, I'd say he waits for more "milestone" type releases to put a new official version up; which does cut down on the questions, help-requests, and other frantic stuff that new releases bring. 6.0.1.0 isn't the most polished or full-featured, but nothing is really wrong, and he probably just doesn't wanna cause a hype.
Again though, this is 100% safe to update to, and will just polish the experience up a bit. It only gets better, regardless of how significantly.
Let me know if you have any more questions. I'd be happy to help
Nick
myepicyear said:
You're welcome. I wholeheartedly appreciate you visiting my thread.
To answer your questions- no, this version is nothing to be afraid of, and definitely not buggy. In fact, the first couple releases of 6.0.x.x were extremely buggy for many people, and 6.0.1.2 was were things seemed to get evened out. If you are still on 6.0.1.0, I would personally suggest updating to at least 6.0.1.2, as it is at least as stable as 6.0.1.0, while adding in a new feature or two. Most issues at the start of v6 releases were about people's backups being extremely slow, and it turned out to mainly be a conflict between Google Play Music and the way the data blob backup folders were executed/cleaned during backup. Google Play Music has a unique way of storing it's music, and it seemed to be responsible for terrible backup times and rebooting during backup(on some devices--never happened to me).
I was using 6.0.1.2 until a few days ago, and everything was always awesome. This version has backups in data blob format going considerably faster for me. It also has an adb-sideload option incorporated ( newest TWRP includes it too). These are the biggest differences, and there is nothing experimental to be wary of. I definitely understand any hesitation, and I think that it's better to be responsible/careful than to be sorry later. As for the exact reason why Koush hasn't put it on the website yet, I couldn't tell you for sure. He's always done releases this way, and if I had to guess, I'd say he waits for more "milestone" type releases to put a new official version up; which does cut down on the questions, help-requests, and other frantic stuff that new releases bring. 6.0.1.0 isn't the most polished or full-featured, but nothing is really wrong, and he probably just doesn't wanna cause a hype.
Again though, this is 100% safe to update to, and will just polish the experience up a bit. It only gets better, regardless of how significantly.
Let me know if you have any more questions. I'd be happy to help
Nick
Click to expand...
Click to collapse
Top notch response. Thanks...
---------- Post added at 05:30 AM ---------- Previous post was at 05:22 AM ----------
One question. How does the sideload thingy work? What's it all about?
Anytime
myepicyear said:
Anytime
Click to expand...
Click to collapse
Noob question: how does one go about installing this over TWRP? I understand it's a .img file but I don't know what do.
crossen0 said:
Noob question: how does one go about installing this over TWRP? I understand it's a .img file but I don't know what do.
Click to expand...
Click to collapse
The same way you installed twrp? Boot into fast boot mode and fastboot flash recovery name-of-recovery.img. Replace name of with the actual name of the image. Or you could download and install flash GUI and flash the image through the app.
Sent from my Galaxy Nexus
crossen0 said:
Noob question: how does one go about installing this over TWRP? I understand it's a .img file but I don't know what do.
Click to expand...
Click to collapse
Though your question may be a bit noobish, it is an absolutely essential process to learn in the custom Android world, and for fear of looking stupid, many beginners skip asking and learning about this very amazing tool. So before I go any further, I'd like to compliment you on being confident enough to ask for help when you need it. It's an extremely important skill that many of us forget around here, as we all want to be seen as a "know-it-all" sometimes, severely inhibiting our abilities to advance. So yeah, just wanted to mention that, lol.
Now, the tool to do this is fastboot. Are you familiar with the concepts of adb and/or fastboot in any way?
Also, what computer operating system do you use?
myepicyear said:
Though your question may be a bit noobish, it is an absolutely essential process to learn in the custom Android world, and for fear of looking stupid, many beginners skip asking and learning about this very amazing tool. So before I go any further, I'd like to compliment you on being confident enough to ask for help when you need it. It's an extremely important skill that many of us forget around here, as we all want to be seen as a "know-it-all" sometimes, severely inhibiting our abilities to advance. So yeah, just wanted to mention that, lol.
Now, the tool to do this is fastboot. Are you familiar with the concepts of adb and/or fastboot in any way?
Also, what computer operating system do you use?
Click to expand...
Click to collapse
I appreciate the help. I had not flashed a recovery in a while as I've been using TWRP since I bought the phone. I used the Toolkit to temporarily boot into CWM to flash the GSIII Launcher and theme since it doesn't play well with TWRP. I appreciate the quick response and willingness to help.
Sent from my Galaxy Nexus using xda app-developers app
crossen0 said:
I appreciate the help. I had not flashed a recovery in a while as I've been using TWRP since I bought the phone. I used the Toolkit to temporarily boot into CWM to flash the GSIII Launcher and theme since it doesn't play well with TWRP. I appreciate the quick response and willingness to help.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Definitely try to learn fast boot man. The toolkits are cool, but a minor mistake can make using one a nightmare. If you learn fastboot, you will always be able to fix your device. Plus it is the proper and preferred method for flashing a recovery, radio, or bootloader. It is an invaluable tool for for flashing.
Sent from my Galaxy Nexus using Tapatalk 2
crossen0 said:
I appreciate the help. I had not flashed a recovery in a while as I've been using TWRP since I bought the phone. I used the Toolkit to temporarily boot into CWM to flash the GSIII Launcher and theme since it doesn't play well with TWRP. I appreciate the quick response and willingness to help.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm happy to be able to help man.
If you want a quick fix until I have some time to more time to explain fastboot thoroughly, I can do that for the moment.
The toolkit that mkskip has put together for everyone is very handy. It is basically like having all the essential tools, like fastboot, installed for you in their most lean form, without needing the whole android SDK installed. It also gives you a logical interface to interact with all that stuff. The toolkit installs all these tools within a folder on the root of your C drive. If you go to the root of your C drive, you'll see that folder, which is called 'Galaxy Nexus Toolkit'(or something). If go inside that directory, there's a folder called put imgs to flash here. There are several ways to do things in the toolkit folders, but basically, this is one folder you can insert imgs in to fastboot flash them.
Let me know if you're with me so far. I'm going by my memory of all this stuff because I don't use toolkits or Windows anymore. I can guide you through this, and during the process, hopefully broaden your understanding of fastboot at the same time. I'll need you to do some searching of your own during the process, or it wont make any sense at all, but I can definetly guide you through.
There's no need for the toolkit to flash a recovery.
Literally just CD to the folder the .img is in and run "fastboot flash recovery (whatever your recovery is named).img".
063_XOBX said:
There's no need for the toolkit to flash a recovery.
Literally just CD to the folder the .img is in and run "fastboot flash recovery (whatever your recovery is named).img".
Click to expand...
Click to collapse
Dude, I'm not stupid. I'm trying to explain it in a way he is already familiar with.
Jesus.
The whole process is pretty simple on what I have done. I will explain my situation here and my question that has got be baffled.
So it all started about two weeks ago, where I was flashing LiquidSmooth on my phone. I had a Touch-type CWM. It isn't mega old but it's pretty old for CWM, I haven't updated in a while (as i've seen there are updates to recent ones).
Anywho, I did a complete wipe, used the darkside wipe, alongside with the darkside cache wipe.
I think this was my fault, so please correct me anyone if I am wrong here. I accidentally hit "reboot phone" instead of "reboot bootloader"
I got a permabrick from this whole ordeal. It was a permabrick because It said QHSUSB_DLOAD in the device manager, looking this up further confirmed my reasoning. I didn't want to jtag because that invovles removing the phone to pieces and soldering on wires etc. etc.
So I resorted to send it out to Samsung.
All is well when it came back. I made sure this time the whole phone was setup properly.
So I use Odin install for CWM and SU was installed via CWM. I install an older version of CWM (non-touch, i believe 1st revision as i've posted in one of the threads).
I kept stock ROM, everything was working okay and suddenly, KERPLUNK, it went back into permanent brick after I deleted cache partition, dalvik cache, and battery cache wipe. I didn't do fix permissions or anything, just hit reboot afterwards.
This is a super head scratcher here..... Anyone know where I went wrong?
Any insight here is greatly appreciated! :good:
P.S. I am now sending in my phone TWICE to Samsung for repairs.
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
LoopDoGG79 said:
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
Click to expand...
Click to collapse
I finally jumped in the water and flashed twrp! Yay!
Sent from my SAMSUNG-SGH-T989 using xda premium
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
great call on that I had to educate a few users that the d2tmo is not for our phone but indeed the S3. Good catch on your part and it sounds like user error as well
LoopDoGG79 said:
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
Click to expand...
Click to collapse
Could you please educate me with a link referring to what TWRP is? Sorry, i'm still fairly new to the scene and all i've ever been educated upon is CWM.
suaverc118 said:
I finally jumped in the water and flashed twrp! Yay!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Nice! What is TWRP and how is it like?
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I've flashed the hercules ROM. I know this for sure because Liquidsmooth was working, it was extremely glitchy (playing games gave me pixelated actions sometimes, and using something like gameCIH/Game Guardian was unworkable). So i decided to ditch it and was getting ready to flash Jedi Mind Trick.
After the whole hard bricking ordeal, I decided to stick to stock rom, and even on that, I just flashed CWM and SU ONLY. Rebooted, and deleted the cache's (like i've posted to you) with absolutely no success. It baffled me that I bricked the phone AGAIN too!
playya said:
great call on that I had to educate a few users that the d2tmo is not for our phone but indeed the S3. Good catch on your part and it sounds like user error as well
Click to expand...
Click to collapse
Yes..... there is something wrong, i feel it is a user error also, but i'm very unsure where to even start
Once again, all of your insight is well appreciated! I just do not want to hardbrick my phone AGAIN and have to send it to Samsung. I am not allowed to even think of a replacement because this was a b-day present a year or two ago from my fiance.
You say that it is bricked again. Do you mean by that, that you cannot get into recovery?
Sent from my SAMSUNG-SGH-T989 using xda premium
XxGoKoUxX said:
Could you please educate me with a link referring to what TWRP is? Sorry, i'm still fairly new to the scene and all i've ever been educated upon is CWM.
Nice! What is TWRP and how is it like?
I've flashed the hercules ROM. I know this for sure because Liquidsmooth was working, it was extremely glitchy (playing games gave me pixelated actions sometimes, and using something like gameCIH/Game Guardian was unworkable). So i decided to ditch it and was getting ready to flash Jedi Mind Trick.
After the whole hard bricking ordeal, I decided to stick to stock rom, and even on that, I just flashed CWM and SU ONLY. Rebooted, and deleted the cache's (like i've posted to you) with absolutely no success. It baffled me that I bricked the phone AGAIN too!
Yes..... there is something wrong, i feel it is a user error also, but i'm very unsure where to even start
Once again, all of your insight is well appreciated! I just do not want to hardbrick my phone AGAIN and have to send it to Samsung. I am not allowed to even think of a replacement because this was a b-day present a year or two ago from my fiance.
Click to expand...
Click to collapse
Flash this in recovery, reboot recovery, and you will have TWRP!!
TWRP 2.3.1.1
DM_Sledge said:
You say that it is bricked again. Do you mean by that, that you cannot get into recovery?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yes, it is perma-bricked, meaning the only method of fixing the brick is jtagg'ing
Upon plugging it into device manager, I get the prompt "QHSUSB_DLOAD" and phone doesn't even boot on no matter what combinations I make.
LoopDoGG79 said:
Flash this in recovery, reboot recovery, and you will have TWRP!!
TWRP 2.3.1.1
Click to expand...
Click to collapse
Thank you LoopDo, I will do this after I get my phone home again.
I have this phone, and none of the steps you listed would brick the device. Even with no ROM on the phone, you should still be able to get into recovery.
Is there something you aren't telling us?
Sent from my Galaxy Nexus using xda premium
Nope, wouldn't be a reason why I would lie because then the problem will never be resolved.... I'm kind of nervous on reflashing ONE more time after the phone comes home again....
The phone has been fixed once AGAIN, and it is in the process of being shipped back to me.
Phone will be home Wednesday and I will give it ONE more try
Wish me luck!
P.S. my PC has been glitchy lately, so that MAY or MAY NOT contribute to the permabrick, then again the brick doesn't happen until I flash stuff via CWM.
P.S.S. I've since re-installed Win 7 again, it hasn't been glitchy since
XxGoKoUxX said:
Nope, wouldn't be a reason why I would lie because then the problem will never be resolved.... I'm kind of nervous on reflashing ONE more time after the phone comes home again....
The phone has been fixed once AGAIN, and it is in the process of being shipped back to me.
Phone will be home Wednesday and I will give it ONE more try
Wish me luck!
P.S. my PC has been glitchy lately, so that MAY or MAY NOT contribute to the permabrick, then again the brick doesn't happen until I flash stuff via CWM.
P.S.S. I've since re-installed Win 7 again, it hasn't been glitchy since
Click to expand...
Click to collapse
You most likely flashed the Wrong Liquidsmooth ROM (incompatible Kernel), and it hard bricked the phone. It happened to me the same way, and I had to send it in for JTAG.
I have bricked my phone installing the Liquidsmooth ROM too. I downloaded the wrong ROM, though. The thread should have a big ****in warning to double check the ROM you are about to download, otherwise your phone is a toast. There were more people who bricked their phones by installing the Liquidsmooth.
Well, I got it back from the warranty and the phone looks good. Installed that Liquidsmooth again and played for a day. Tried other JB ROMs. Most of them are OK in terms of battery life and smoothness, but there is something wrong with the signal. People always say my voice isn't clear. I got tired of all this BS and testing new ROMs and went to back to ICS and won't look back, not anytime.
Don't use darkside scripts, btw. You don't need that anymore.
I'd like to say thank you for everyone's patience. All of your insight is more than helpful!
DroidDonX said:
You most likely flashed the Wrong Liquidsmooth ROM (incompatible Kernel), and it hard bricked the phone. It happened to me the same way, and I had to send it in for JTAG.
Click to expand...
Click to collapse
I might have, but the one i downloaded (which is still on the phone's memory card) is a hercules ROM. Either way on my second try there was a hard brick also, in return of which I had to resend it in. The second try was just simply: Odin---->CWM---->Root---->SU---->wipe cache partition+fix permissions+wipe dalvik cache via CWM (not the super scripts).
cipsaz said:
I have bricked my phone installing the Liquidsmooth ROM too. I downloaded the wrong ROM, though. The thread should have a big ****in warning to double check the ROM you are about to download, otherwise your phone is a toast. There were more people who bricked their phones by installing the Liquidsmooth.
Well, I got it back from the warranty and the phone looks good. Installed that Liquidsmooth again and played for a day. Tried other JB ROMs. Most of them are OK in terms of battery life and smoothness, but there is something wrong with the signal. People always say my voice isn't clear. I got tired of all this BS and testing new ROMs and went to back to ICS and won't look back, not anytime.
Don't use darkside scripts, btw. You don't need that anymore.
Click to expand...
Click to collapse
Thanks again for your insight I think i'm done with flashing for a little bit for now.... I kind of want as factory of a JB Rom as possible. :good:
If anyone has any idea where I can get that, please let me know as my Stock ICS is a bit laggy at times, with the facial recognition system, it lags even worse!
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
that just happened to me today with liquid smooth. i had to unroot, flash stock, and start over. im pretty sure i got it from goo.im under hercules. unfortunate mislabeling? oh yeah, and if your phone shows anything other than nothing, youre not hard bricked. thats why its called Hercules, i think. ive been soft bricked so many times from dumb **** like. ****ing with the governors and all that **** cm gives you the option to do when there aint even a 1080p camera that works fully = / lol <3 Cm I Love Yew!! But yeah, odin will set you free!!!
I'm using Snipers PACMAN, and battery just seems to drain way to fast. It is the latest push. Being newly registered on here I hate to introduce my self this way but I need advice. What tweaks are being used by people for the SPH-D710 to help with this issue? I originally started with the CM 10.1 rom and found I had no data, flashed a different modem. Still no data, switched roms and now have data....go figure! But the battery drain is killing me, I've got it throttled back as far as I can go and it still be a daily driver. So anyone have any suggestions?
Godlys Comadose Tweak pack works great:thumbup:
Give it a shot and thank him while you're over there...here's the link
http://forum.xda-developers.com/showthread.php?p=39080082
OK....now I'm lost as to which to try and use.....reading the posts to the provided links seems to give contradictory information as to where to start this journey.....
Sent from my SPH-D710 using xda premium
Most 4.2 Roms use ICS modems. As for battery us betterbatterystats found here on xda or gsam in the play store to determine if there's any rogue apps keeping the phone from sleeping. I also do manual syncing. Greenify is a great app to keep apps from running on their own. You can also use a custom kernel to limit max frequency and even undervolt. Kernels also come with different governors
Sent from my SPH-D710 using Tapatalk 2
godzilla61 said:
OK....now I'm lost as to which to try and use.....reading the posts to the provided links seems to give contradictory information as to where to start this journey.....
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Try the latest version....2.1
Anybody on this thread know anything about the pegasusq governer or how to implement it/install it?
rapman543 said:
Anybody on this thread know anything about the pegasusq governer or how to implement it/install it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=24233103&postcount=3
Read...Read...Read
After reading through the above posts you should have some useful ideas about what this governor does.Also...as for installing a governor, they will be included in the kernel that flashed with ur rom or a kernal of ur choosing(MAKE SURE IT WILL WORK WITH THE ROM YOU HAVE) Im new to this, so if there is another way I dont know about it. Do ur research... As for setting a governor.. There are many roms with built in performance controls as well as many apps to set them. I suggest (set cpu) . It has a setting that will make a zip so u can recover from ur settings if u bootloop. This is found after u install and give it root permission. Hit ur menu button and click SAFE MODE. You should have a nandroid; always and just because.I hope this helps.. Remember...Read...Read...Read..lol.. Good Luck.Also read this http://forum.xda-developers.com/showthread.php?t=2005306
Gil81 said:
http://forum.xda-developers.com/show...03&postcount=3
Read...Read...Read
After reading through the above post you should have some useful ideas about what this governor does.Also...as for installing a governor, they will be included in the kernel that flashed with ur rom or a kernal of ur choosing(MAKE SURE IT WILL WORK WITH THE ROM YOU HAVE) Im new to this, so if there is another way I dont know about it. Do ur research... As for setting a governor.. There are many roms with built in performance controls as well as many apps to set them. I suggest (set cpu) . It has a setting that will make a zip so u can recover from ur settings if u bootloop. This is found after u install and give it root permission. Hit ur menu button and click SAFE MODE. You should have a nandroid; always and just because.I hope this helps.. Remember...Read...Read...Read..lol.. Good Luck.
Click to expand...
Click to collapse
+1
You identify yourself as "new to this" but you nailed this post 110%!! Many people would do well to take what you said here to heart. If they did there would be MANY fewer "help me" threads.
CyberpodS2 said:
+1
You identify yourself as "new to this" but you nailed this post 110%!! Many people would do well to take what you said here to heart. If they did there would be MANY fewer "help me" threads.
Click to expand...
Click to collapse
Thank You...... I went ahead and added another link for him to read. I hope it helps. As to what you said, I like to think of myself as the poster child for the search button..lol..I think if you do the research it makes you feel better when it works and it is more likely to stick with you. This site is so great about that because there is just so much knowledge here to learn.I think some people get over-whelmed by it though or they are just unsure and need that go ahead push to know it works.
Ok since I can't ask a Dev a question about the kernel I want to install.....which I kinda understand, but being stuck not being able to ask questions about something specific after reading all the pages blows! (rant off) [Kernel] Lightning Zap! Phase 4 Updated 15JUN13 is causing a boot loop, I followed all the instructions to the letter, crossed every T, dotted all the I's. Thank god for backup! Since I can't ask the Dev a question I'm stuck!
godzilla61 said:
Ok since I can't ask a Dev a question about the kernel I want to install.....which I kinda understand, but being stuck not being able to ask questions about something specific after reading all the pages blows! (rant off) [Kernel] Lightning Zap! Phase 4 Updated 15JUN13 is causing a boot loop, I followed all the instructions to the letter, crossed every T, dotted all the I's. Thank god for backup! Since I can't ask the Dev a question I'm stuck!
Click to expand...
Click to collapse
Well, you're commenting on a thread about battery life, but not posting about battery life. That's not going to help you much.
I also read that you want to ask a question, but I don't see a question in your post. If you do have a question, a great place to post it would be here: [Official] One Stop FAQ Thread - Noob Friendly (All questions go here). Okay? :good:
erikalin said:
Well, you're commenting on a thread about battery life, but not posting about battery life. That's not going to help you much.
I also read that you want to ask a question, but I don't see a question in your post. If you do have a question, a great place to post it would be here: [Official] One Stop FAQ Thread - Noob Friendly (All questions go here). Okay? :good:
Click to expand...
Click to collapse
Well let me clarify it for you, it's my thread. The original question is still valid being as I was pointed this direction by a reply to my original post. Let me lessen your confusion on this matter......What other steps can I take to increase battery life......scripts didn't seem to help and a tweaked kernel put me in a boot loop....and whom do I ask if not the DEV?
godzilla61 said:
Well let me clarify it for you, it's my thread. The original question is still valid being as I was pointed this direction by a reply to my original post. Let me lessen your confusion on this matter......What other steps can I take to increase battery life......scripts didn't seem to help and a tweaked kernel put me in a boot loop....and whom do I ask if not the DEV?
Click to expand...
Click to collapse
Hey bro, easy on the tone. Because there are so many ways to ask the question, the best way is to just spell it out how you did above. Battery life depends on the apps/ROM/user all at the same time. I am on Project X ROM. It has Crossbreeder installed. Now I am not no where informative about that app other than a lot of people like it. So with that being said and it is installed on the ROM, I leave it. I also have ROM Toolbox Pro. I have adjusted my CPU control to 1000MHZ. I also have DS Battery Saver Pro set to custom and to kill all apps when the screen goes off. Last the ROM I am on comes with Greenify. A great app in saving battery. I also turn off data and only have WIFI on when I need it. No need to just let things run. With that I have had 50% battery life left after 11 hrs. That is my setup and may not work for you. The main thing is to understand that battery life for EACH phone is different no matter how many common denominators people may have. Team Venum did a comparison of ROM's and their respective battery life. I don't know the post, but if you type "battery life" in the search, then I am sure you can find it. As for you response, I was in your shoes at one time. It does help to be specific in your questions. Not saying that you weren't. Reading each and every post will get tiresome, but if you type in what you want in the search, you will get a slew of post to get info. I have only been a member for 4 months, but I have learned how to flash a ROM, Mods, push and app, setup custom home screen. I have even been given the honor of testing a ROM. If you still need help, you can PM me and I will do what I can. Have a great one.
godzilla61 said:
Ok since I can't ask a Dev a question about the kernel I want to install.....which I kinda understand, but being stuck not being able to ask questions about something specific after reading all the pages blows! (rant off) [Kernel] Lightning Zap! Phase 4 Updated 15JUN13 is causing a boot loop, I followed all the instructions to the letter, crossed every T, dotted all the I's. Thank god for backup! Since I can't ask the Dev a question I'm stuck!
Click to expand...
Click to collapse
Its fine,you can rant here...lol..Ok ,I need more info.....
rom you're try to use with lz kernal
how you went about flashing said kernel
did you have any other tweaks or mods flashed before flashing lzp_4
All of this info is important, so I can tell you what is wrong....Thanks..
Gil81 said:
Its fine,you can rant here...lol..Ok ,I need more info.....
rom you're try to use with lz kernal
how you went about flashing said kernel
did you have any other tweaks or mods flashed before flashing lzp_4
All of this info is important, so I can tell you what is wrong....Thanks..
Click to expand...
Click to collapse
Thanks Gil, this is exactly what I have done.
1. flashed from 4.03 to WILD-FOR-THE-NIGHT-07052013-d710, had no data....tried to find a fix for that...gave up after trying tweaks to help with the battery issue and no data.
2. Clean install of d710_PAC_JB_4.2.2-v23.0.0_20130719-015400, now have intermittent data, wifi works, blutooth works, flashed Fl24 modem with no apparent improvement in data connectivity, thought after reading a kernel flash might fix issues, here comes the boot loop....flashed smdk4412_p4 waited patiently for 2hrs watching Pacman chasing ghosts.....booted into recovery and ran my backup tried it 2 more times on clean flashs gave up after 5 hrs. By clean I mean wipe/reset, wipe cache, wipe dalvik, install from zip.
3. this is how I installed the kernel:
Make a backup
Download .zip to PC
Transfer .zip to sdcard
Reboot to recovery
Flash
Phone automatically rebooted after install
waited and waited......boot back into recovery. restore by backup.
everything has been done with CWM based recovery. I'm stumped....frustrated to no end......
godzilla61 said:
Thanks Gil, this is exactly what I have done.
1. flashed from 4.03 to WILD-FOR-THE-NIGHT-07052013-d710, had no data....tried to find a fix for that...gave up after trying tweaks to help with the battery issue and no data.
2. Clean install of d710_PAC_JB_4.2.2-v23.0.0_20130719-015400, now have intermittent data, wifi works, blutooth works, flashed Fl24 modem with no apparent improvement in data connectivity, thought after reading a kernel flash might fix issues, here comes the boot loop....flashed smdk4412_p4 waited patiently for 2hrs watching Pacman chasing ghosts.....booted into recovery and ran my backup tried it 2 more times on clean flashs gave up after 5 hrs. By clean I mean wipe/reset, wipe cache, wipe dalvik, install from zip.
3. this is how I installed the kernel:
Make a backup
Download .zip to PC
Transfer .zip to sdcard
Reboot to recovery
Flash
Phone automatically rebooted after install
waited and waited......boot back into recovery. restore by backup.
everything has been done with CWM based recovery. I'm stumped....frustrated to no end......
Click to expand...
Click to collapse
First off...I have had the lzp_4 boot loop on me. I pulled the battery,waited about 2 min. Put it back in and booted to recovery. Then I wiped cache and dalvik. Rebooted and it took off(booted fine). I have no idea why or how, but this worked for me. Now to my main concern. If you came straight from ics to a jb rom I think this is going to cause you issues, if you hadn't been on jb before. I suggest the one - click full restore(it wipes data,so back-up you're internal memory).This will get you're phone partition right for jb. After this. I think you should be able to flash what you want with no problems. I didn't see a problem with how you flashed. Wipe cache and dalvik on the kernal flashes you do.Here's the link for the one -click..
go to linked page and click on download ota at top of page
I would read through the page it sends you to well.Don't forget to thank those guys..Hope this helps.Hit me up if it doesn't.
.http://forum.xda-developers.com/showthread.php?t=2148072
Doing a one click restore worries me, I'm not on sprint any more and worried about losing my flash to my current carrier. Is this a concern I should have since I'm not used to working with odin? I'm more than willing to try another ROM also, I'm not locked into this by any means.....
godzilla61 said:
Doing a one click restore worries me, I'm not on sprint any more and worried about losing my flash to my current carrier. Is this a concern I should have since I'm not used to working with odin? I'm more than willing to try another ROM also, I'm not locked into this by any means.....
Click to expand...
Click to collapse
The carrier should not matter if you are on an E4GT phone. But if your trying to go to a JB ROM, you will need to aupdate to GB** for your phone. For sprint it is GB27. Have you tried RWilco12's repository to see if your carrier is listed? Also QBKing77 has a lot of videos concerning this specific phone. How to flash specific ROMs and upgrading specific build, modems and such. Something has got to work for you.
fitting toryBB
bigmike6200 said:
The carrier should not matter if you are on an E4GT phone. But if your trying to go to a JB ROM, you will need to aupdate to GB** for your phone. For sprint it is GB27. Have you tried RWilco12's repository to see if your carrier is listed? Also QBKing77 has a lot of videos concerning this specific phone. How to flash specific ROMs and upgrading specific build, modems and such. Something has got to work for you.
Click to expand...
Click to collapse
Well now I'm stuck on Sprints 4G boot screen just keeps looping.....WTH.....I've never had a phone be a pain like this....guess I let it kill the battery and see what happens. Recovery is there, not cwm so can't even restore my backup. I'm just frustrated by this phone! Gill, bigmike any idea which way to turn now?
godzilla61 said:
Well now I'm stuck on Sprints 4G boot screen just keeps looping.....WTH.....I've never had a phone be a pain like this....guess I let it kill the battery and see what happens. Recovery is there, not cwm so can't even restore my backup. I'm just frustrated by this phone! Gill, bigmike any idea which way to turn now?
Click to expand...
Click to collapse
What ROM did you flash? Was it ICS or Jellybean? What carrier are you on. That was never revealed.
Never kill the battery. I sed you tried" Wild for the night" and Pac something. Can you get to recovery?
X'ed out the game