[Q] Hyperdrive Questions - Verizon Samsung Galaxy S 4

Hi.
I have a few questions about Hyperdrive dealing with the custom framework animation zip files (from the Hyperdrive Hub app) that you can flash.
What do you need to wipe in order to flash them?
I tried wiping just the dalvik cache and cache and flashing and it will reboot and say Hyperdrive is updating and go through all my apps, but then it will soft boot again and get stuck on the boot animation. So I figured I did something wrong...
So do I have to wipe everything (except sd card) in order to flash any zip file??? Because if so, then I can't restore the system with my nandroid backup because it is a previous backup before I flashed the zip file and thus will erase my flashing. Correct?
So my next question is: every time I flash a zip file do I have to reflash my rom? Because if so, that's a lot of damn waiting (I want to test out more than one animation pack to see which one I like the most) and I'm fed up with waiting. And also then I have to have the rom settle in again every time and I don't want to do that.
Is there a simpler/correct way I am unaware of? How do you do it? Please tell meh!
Thanks
And also I've noticed that when I try to enable the battery percentage display in the actual phone settings it refuses to stay there and always disappears shortly after enabling it (even though the option is still checked). I like the look of the system battery percentage display more than Hyperdrive's. Does anyone know how to fix this?
Again thanks!

Related

Need help in solving stability problems. Trying to fully restock the SGS2

Hi guys,
I'm having issues with my SGS2 and I would appreciate very much if you guys could lend me a hand.
I had VillainRom 2.4.2, Ninphetamine 2.0.5 and modem KG6.
I tried to install this Dark theme but something went terribly wrong and I had processes crashing, couldn't see any links to the phone dialer, messaging, etc.
I'm trying to wipe the phone back to full stock but I can't for some reason.
I tried booting into recovery mode, wiping cache and all information but when the phone boots I'm back to a black skin with several crashing warnings.
I tried to reflash KG6 with odin and selecting repartitioning but when I boot again I'm back to the same black skin missing functions and receiving some crashing alerts.
I tried to factory default through Settings -> Security -> Factory Default to no avail.
All the guides I was able to find on the net to put the phone 100% back to stock failed as I always boot to a non-working dark theme.
Can someone please provide me some help?
Would appreciate very much any pointers.
EDIT: After I boot into this dark theme, I'm getting messages like process android.process.acore has stopped unexpectedly for example.
Factory reset does not mean that it removes all your custom rom stuff and all that. That's a nice thought, but that's not how it works
You need to flash a different rom on your phone after having wiped everything. This will fix your problem. And if you so very much want to go back to stock, you could always flash a stock rom through ODIN which you can get from one of the available threads.
Boot to recovery mounts and storage format system data and sd card ,
Power off boot to download mode flash stock firmware via Odin .
jje
I don't know if I'm understanding.
I did reflash the phone with samsfirmware Europe KG6 after a complete wipe of data through the recovery menu (vol.up+power+home).
That didnt work.
Am I missing some steps in my procedure?
I noticed that my default dialer apk, contacts apk, etc are not working. Which method will also replace all my original APKs?
Thanks once again for your time and attention.
Boot to recovery mounts and storage format system data and sd card ,
Power off boot to download mode flash stock firmware via Odin .
Nothing more to add.
jje
Just wanna thank you for your help. For some reason I wasn't getting the expected behavior by flashing KG6. Went with KG5 and now I'm back on stock.
Cheers. Thanks button went your way btw.

[Q] Please help newbie with semi-bricked phone

Hi guys, I got a SGS2 just over a week ago, on Bell/Virgin network in Canada. Suffered from the battery drain issue due to being stuck with crappy UGKG2 firmware which my provider still hasn't updated.
I decided to update it myself, and did a ton of research. I successfully got Root tonight by flashing CF-Root-SGS2_ZS-OZS_KG2-v4.1-CWM4 kernel with Odin. In case it matters, I did NOT flash back my stock Kernel, so I still had the insecure kernel installed. From there, I backed up my apps with Titanium.
Went into CWM and selected boot into CWM Recovery. I followed the steps on the wiki, including creating a backup file. My only hint of what I might have done wrong was I originally selected to flash update.zip, and that process failed. I then went to the directory in which cyanogenmod is stored on my SD card, and selected that, then it installed ok. I had downloaded update-cm-7.10-GalaxyS2-signed and that's what I put on the phone. I then also installed the Google Apps.
I then hit reboot, and it only goes to the Samsung screen with the yellow triangle and just hangs there for a few minutes. Not knowing what else to do, I popped the battery out. I have since learned that I can turn it on and off, but it never goes past that screen. Wouldn't go into the recovery or download modes, always that screen. Luckily, I saw somewhere to do the 3 button thing WHILE in that screen, and that works. So I can get to recover, and download modes. So, I think I'm ok. I checked, and it does connect to Odin still.
I just want to know EXACTLY what I should do at this point. I don't want to fully brick it. There are actually two recovery files on the phone... not sure why... Or which one to pick. Should I just flash stock firmware back with Odin? One of my main goals is to get off 2.3.3 so I can have more than 8 hours of battery...
Thanks,
Rob
Boot into tecovery, do a full wipe again. (Wipe data/factory reset, wipe cache partition, advanced>wipe dalvik cache).
Now install CM7 zip twice in a row without reboot. It may take a few minutes for reboot since system is rebuilding dalvik cache. Be patient. After you see the home screen, reboot again.
Sometimes, CM won't install properly with CF root recovery. In that case reboot into download mode, flash codeworkx cwm kernel via ODIN.
http://forum.xda-developers.com/showthread.php?t=1118693
Now reboot into recovery and do full wipe and twice-install !
Ok, working now with the flash twice thing. Well that's weird, would be great if it was in the wiki page...
Thanks!
Rob

[Q] Mass Force Closures / Need a TAR file

I don't know exactly what caused the issue. Maybe some recent apps since that was all that I had installed. I was running the latest AOKP ICS 4-28-12 and Siyah 3.1x. I forget the exact kernal number but it wasn't the version that I read about phone bricking (R6?).
So I wake up this morning and unlock my screen and there are popups for everything force closing. Not just foreground running apps but everything including background running apps. Every time an app autorestarts in the background the force close error msg pops up again. It was running fine just 6 hours prior since I was using it before bed.
Reboot. Same issue. CMW Recovery. Wipe cache/dalvik. Reflash AOKP and GApps. Reboot. Same force closing issue. WTF. Attach USB to comp and try to move a different ROM to my Internal SD but no dice. Comp isnt recognizing phone now. [email protected]#K! Reboot into download mode. All the ROMS I downloaded are ZIP format instead of TAR format. So this time my dumb self uses Odin to reflash the TAR file I used to root my phone. After this I realize "that TAR doesn't have a ROM attached to it."
So now I can only boot into download mode. Can't load CMW. Sadly I had to leave for work and I'm without my phone until I get home at midnight. I FEEL SO DISCONNECTED! ='(
Will a simple file conversion program be sufficient to convert ZIP to TAR so I can use ODIN to flash them later? Or will I have to follow the unbrick instructions to return to stock and then start over? And after reading about that one version of Siyah bricking phones I think I'm going to leave the NEAK kernal that comes with AOKP.
Thanks for your assistance!
No, you can't build a tar from a zip.
I don't and have never used aokp or cm9 or miui, but in my experience, when you start getting massive force closes, and if a fix permissions in recovery doesn't fix it, then you're best off starting over from scratch. If you have a working nandroid backup, use that. Otherwise, flash back to stock, wipe data/factory reset, and reinstall your rom from scratch.
There are plenty of tar and one-click downloaders available. See links in my signature.
I found this on the i9100 forums, instructive. Instead of installing a stock samsung firmware and kernel, just download a rooted package (maybe go back to Gingerbread for i777) then go from there.
http://forum.xda-developers.com/showthread.php?t=1457458
I'm interested to know how this recovery works for you, keep us posted! Best luck!
Any idea what would randomly cause the issue of mass force closures so I can prevent this from occuring again?
Did you do a Full Wipe when you first installed AOKP? I have ran into issues before with Rom Control by just wiping cache and dalvik and under the OP of AOKP Task even states coming from aokp or cm9 you Should be good but more likely than not, I would do a complete wipe *Factory Reset under CWM*. And when you restore your data with TiBu just restore missing apps and their data. Do not restore system data as that will be a major cause of mass FC... So first things first, I would use Odin to go back to UCKH7 *hopefully with CWM and Root* and than go back to Aokp since in my opinion is the best rom for our phones now.
HTH,
Charlie
dmnall said:
Did you do a Full Wipe when you first installed AOKP? I have ran into issues before with Rom Control by just wiping cache and dalvik and under the OP of AOKP Task even states coming from aokp or cm9 you Should be good but more likely than not, I would do a complete wipe *Factory Reset under CWM*. And when you restore your data with TiBu just restore missing apps and their data. Do not restore system data as that will be a major cause of mass FC... So first things first, I would use Odin to go back to UCKH7 *hopefully with CWM and Root* and than go back to Aokp since in my opinion is the best rom for our phones now.
HTH,
Charlie
Click to expand...
Click to collapse
I didn't do a factory wipe. I'm thinking I'll just do a factory wipe for any new rom installs. It's a little more work but if it helps prevent this sort of error I'll do it. And after reading about the bricking with that one version of Siyah I'm going to wait a couple weeks before any new installs to make sure other people have tested it first.
creepyncrawly said:
No, you can't build a tar from a zip.
I don't and have never used aokp or cm9 or miui, but in my experience, when you start getting massive force closes, and if a fix permissions in recovery doesn't fix it, then you're best off starting over from scratch. If you have a working nandroid backup, use that. Otherwise, flash back to stock, wipe data/factory reset, and reinstall your rom from scratch.
There are plenty of tar and one-click downloaders available. See links in my signature.
Click to expand...
Click to collapse
Well the first attempt didnt work using kernel + rooted UCKH7. Odin did everything it was supposed to but the phone locks at the initial Galaxy S II I-9100 ! screen. =(
Second attempt using I777_UCKH7_OCD_Root_No_BL and I'm able to get past the Galaxy S II I-9100 screen and the original AT&T boot animation shows but after the boot animation it just continuously reboots. ='(
Third attempt I tried Kernel + cache + rooted UCKK6 and after the reboot it actually rebooted into recovery mode. I thought that was a good sign so I reboot the phone normally and same issue as above. I try to reboot into recovery mode (Vol + - and pwr) again but it doesn't come up now. ='(
Forth attempt I tried Kernel + cache + rooted UCKK6 again. It reboots into recovery mode and I select the Factory Wipe option and reboot. There's a long delay after the AT&T boot animation and finally my phone starts up as if it was stock.
What a freakin nightmare! I was so worried my phone was a goner. None of the other ROMs I tried gave the option of booting into recovery mode which would have saved me so much time. Only the stock one did. The factory wipe was the key. So I'm definitely saving that file for safe keeping.
Thank you all for your suggestions and assistance. It's much appreciated.
This entire thread could have been avoided. By wiping completely. What is a complete wipe? Well, its the /system , /cache, /data, and /dalvik partition. Each of which are easily wiped in cwm in under 30 seconds. Flashing the kernel cleaning script doesn't hurt. Keep in mind these are your phones people it wouldn't hurt to do some research.
Sent from my SGH-I777 using Tapatalk 2

Stuck on Avatar logo startup! Please Help!

Hi! I'm new to the forums and I have recently rooted my MB860 Motorola Atrix 4g with olympus.
Today I tried to install CM10 Avatar Rom : http://forum.xda-developers.com/showthread.php?t=2140902
I restarted my phone in Clockworkmod > install zip from internal storage > install
But after it restarts, it gets stuck on the Avatar logo with the sparkle circulating.
I tried wiping Delavik/cache/ and I even formatted the phone to factory settings.
Can anyone please help me?
Shaxxi said:
Hi! I'm new to the forums and I have recently rooted my MB860 Motorola Atrix 4g with olympus.
Today I tried to install CM10 Avatar Rom : http://forum.xda-developers.com/showthread.php?t=2140902
I restarted my phone in Clockworkmod > install zip from internal storage > install
But after it restarts, it gets stuck on the Avatar logo with the sparkle circulating.
I tried wiping Delavik/cache/ and I even formatted the phone to factory settings.
Can anyone please help me?
Click to expand...
Click to collapse
have u tried going back to stock
make sure if u flash the file again that u re-download it, the ROM might have not been downloaded correctly and therefore you are stuck on the splash screen
The problem is, i hadn't back up my previous rom before installing this one, therefore I cannot go back. Ugh i'm so newb >.<
However, is there a way to completely set it back to factory settings? I wipe /data/cache/Delavik/ back to factory setting but still after i restart it goes to the splash screen of Avatar ROM.
>.<
Shaxxi said:
The problem is, i hadn't back up my previous rom before installing this one, therefore I cannot go back. Ugh i'm so newb >.<
However, is there a way to completely set it back to factory settings? I wipe /data/cache/Delavik/ back to factory setting but still after i restart it goes to the splash screen of Avatar ROM.
>.<
Click to expand...
Click to collapse
It is always recommended to take a backup and full wipe (not just the dalvik cache) before installing a custom ROM. It is quite difficult to retrieve the data if there is no backup and the ROM is not booting. As of now the first thing I would suggest is to take a full backup using clockworkmod (at any stage you can recover this and come back to current state). Once the backup successful, try doing a wipe data/factory reset, then install the rom and see if it boots.
If the ROM boots at this stage, again take another backup in clockworkmod. Also someone on the thread has suggested flashing an older version of the rom first, boot and then flashing latest zip helps.
Then use the advanced restore option and try restoring data alone. If this is successful, you should most probably have all the data of all standard applications.
Also check this links http://forum.xda-developers.com/showthread.php?t=1163009 or stock-firmware and see if you can install the stock rom back with this.

Soft brick - stuck at boot logo; need suggestions

Hey all,
I've got a N7105 (Galaxy Note II LTE) running CM12.1 and TWRP which I was planning to change shortly as it's old and the USB port has issues (charges but doesn't pass data; luckily it has a microsd slot). As it happens, the other day I left it discharge fully and turning it back on left it stuck at Samsung logo (not boot animation, the splash screen before it) forever.
I am: not a noob, I've rooted and flashed plenty of devices before.
I tried: removing battery for a while, charging fully, removing microsd and sim, clearing Cache and Dalvik. Nothing works.
I can: get into ODIN mode (but it's useless as USB data is not working); get into TWRP recovery; explore the Data partition in TWRP
I cannot: mount the System partition in TWRP, not even manually. It just does not let me select it, and gives an error whenever it needs to access it (e.g. if I try to backup it is says Error: unable to mount System)
I want: if possible to solve the issue without formatting Data. I had a TB backup but kinda old, so I got a Nandroid of Data and Boot out from TWRP and I suppose I could then recover stuff extracting from Nandroid through TB, but I've never done it and would rather be able to get a fresh TB backup and move on from there.
A few questions I have: any idea on why I am not able to mount System in TWRP? Could it help to reflash Boot or System, and if so how do I go to do that considering what I have is the whole CM rom package? (I remember being able to fastboot flash single partitions on Nexus devices but that's because the stock rom comes packaged in separate images).
Any input would be greatly appreciated!
Lazer Bear said:
Hey all,
I've got a N7105 (Galaxy Note II LTE) running CM12.1 and TWRP which I was planning to change shortly as it's old and the USB port has issues (charges but doesn't pass data; luckily it has a microsd slot). As it happens, the other day I left it discharge fully and turning it back on left it stuck at Samsung logo (not boot animation, the splash screen before it) forever.
I am: not a noob, I've rooted and flashed plenty of devices before.
I tried: removing battery for a while, charging fully, removing microsd and sim, clearing Cache and Dalvik. Nothing works.
I can: get into ODIN mode (but it's useless as USB data is not working); get into TWRP recovery; explore the Data partition in TWRP
I cannot: mount the System partition in TWRP, not even manually. It just does not let me select it, and gives an error whenever it needs to access it (e.g. if I try to backup it is says Error: unable to mount System)
I want: if possible to solve the issue without formatting Data. I had a TB backup but kinda old, so I got a Nandroid of Data and Boot out from TWRP and I suppose I could then recover stuff extracting from Nandroid through TB, but I've never done it and would rather be able to get a fresh TB backup and move on from there.
A few questions I have: any idea on why I am not able to mount System in TWRP? Could it help to reflash Boot or System, and if so how do I go to do that considering what I have is the whole CM rom package? (I remember being able to fastboot flash single partitions on Nexus devices but that's because the stock rom comes packaged in separate images).
Any input would be greatly appreciated!
Click to expand...
Click to collapse
The note 2 has this issue that makes it unable to be recognized by PC, so this isn't your phone problem, the only way to solve it is replacing the usb socket in your phone, anyway i can recommend dirty flashing your rom first, just flash the rom in recovery and wipe cache and Dalvik cache only then reboot.
If that didn't work, I'm afraid you might have to...... clear data ?
MigoMujahid said:
The note 2 has this issue that makes it unable to be recognized by PC, so this isn't your phone problem, the only way to solve it is replacing the usb socket in your phone, anyway i can recommend dirty flashing your rom first, just flash the rom in recovery and wipe cache and Dalvik cache only then reboot.
If that didn't work, I'm afraid you might have to...... clear data
Click to expand...
Click to collapse
Thanks for the input, I was thinking something along those lines but I wasn't totally sure, I always avoided dirty flashing as I heard of people having issues. Happily, it worked! Weirdest think I saw in a while, it gave me a bunch of errors with System partition (unable to mount, unmount, find), then it gave a "proceeding to patch system partition unconditionally", then it completed. The whole thing took less than 20secs so I do not think it even actually flashed the ROM. Now I am just getting some Play Services error, likely need to reinstall gapps, but phone boots just fine!

Categories

Resources