Im having a bit of an issue with the HyperDrive rom on my Safe Strapped Galaxy S4. I've verified the hash so the error is probably not coming from an invalid hash. When I was using 9.1.0 I had no problems installing it and running after Flashing the ME7 modules. However when i attempted to flash the 10.0.0 Update it installed with no problems however i get a black screen upon booting. I never see the Boot animation apart from Safe Strap's menu on startup. If anyone could help me that would be fantastic.
Related
I've been trying to get ICS on my Galaxy S but every single ICS rom I install causes my phone to bootloop.
I'm on JVU firmware in combination with:
This is the December 29, 2011 / Android 2.3.6 / JVU / Value Pack ? build:
CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip
So far I've tried to flash CM9, Slim ICS and Team ICSSGS RC4.2.
What happens when I try to flash any of these roms:
Progress bar show up, it starts installing
At 5% phone reboots
Boot logos show up
Phone enters recover again and some lines of text show up (not long enough to be able to read but looks like error messages)
After less than 1 second the phone reboots again and the process repeats itself
Does anyone have an idea how to fix this? Would be much appreciated because this issue has left me frustrated and I just want to have working ICS on my phone.
Thanks in advance.
When installing ICS over the top of Gingerbread there is a requirement to Flash the ROM twice.
Once to upgrade the bootloader to ICSSGS 4.2 version and second for the ROM to fully install.
I did this and was able to successfully upgrade to ICS.
Searching the thread for ICSSGS 4.2 would have provided the answer for this issue.
If this is unsuccessfull flash back to a gingerbread ROM using Odin Darky's 10.2 worked for me. allow the phone to fully boot. then retry you ICS ROM
Before flashing ICS you also must disable anny lagfix that is applied.
I tried flashing twice already, didn't work. I'm flashing darky 10.2 atm and will try flashing an ics rom again when it's done. Thanks for the tip.
I had kind of the same problem, although my boot loop was a little different i think. I Odin'd Darky's 10.1 a few times, but in the end also tried 9.2. That worked. No idea of that made the difference, you could give it a try.
Sent from my SGH-I9000 using XDA
Allright flashing Darky's 10.2 first and then ICS twice was the solution, so weird. Thanks for the help
Hey guys. I've been using CyanogenMod on my Galaxy S for quite a long time. Few days ago my battery died and phone wouldn't pass the CyanogenMOD logo. I've decided to go back to stock rom and then upgrade to one of the new roms.
So I flashed the stock rom using Odin 3.07, rooted, went to recovery mode and tried to flash: Mackay ROM, Beast ROM ( black and white as well as beastxl), Avatar ROM, Slim Bean, Tsunami, CyanogenMOD but none of the above worked.
It starts the installation and after few seconds phone restarts itself and gets stuck on new boot logo.
The only thing that gets installed is the CWM which won't let me do the factory reset, wipe data, wipe dalvik cache etc. Keeps saying can't mount /data, /cache, /system.
The only time I can do factory reset is when I install stock rom.
I only succeeded installing Franzy ROM once but after reboot gets stuck on boot logo.
Sometimes even the stock ROM is giving me issues like process com.android.phone has stopped unexpectedly (does it for dialer, calculator, market, launcher)
Another weird thing is that even when I go back to stock rom and open up for instance a picture with bright background or web browser I can see transparent battery and CyanogemMod in the middle of the screen even tho phone's not charging and running on stock rom not CyanogenMod.
I think I've tried everything from fixing permissions, flash and re-partition using Odin and 512 pit file.
Even rang my Mom like advised in xda's video, didn't help either
Is there anything else I can try to get my phone in "shape"?
Any suggestions?
AllUsernamesAlreadyInUse said:
Hey guys. I've been using CyanogenMod on my Galaxy S for quite a long time. Few days ago my battery died and phone wouldn't pass the CyanogenMOD logo. I've decided to go back to stock rom and then upgrade to one of the new roms.
So I flashed the stock rom using Odin 3.07, rooted, went to recovery mode and tried to flash: Mackay ROM, Beast ROM ( black and white as well as beastxl), Avatar ROM, Slim Bean, Tsunami, CyanogenMOD but none of the above worked.
It starts the installation and after few seconds phone restarts itself and gets stuck on new boot logo.
The only thing that gets installed is the CWM which won't let me do the factory reset, wipe data, wipe dalvik cache etc. Keeps saying can't mount /data, /cache, /system.
The only time I can do factory reset is when I install stock rom.
I only succeeded installing Franzy ROM once but after reboot gets stuck on boot logo.
Sometimes even the stock ROM is giving me issues like process com.android.phone has stopped unexpectedly (does it for dialer, calculator, market, launcher)
Another weird thing is that even when I go back to stock rom and open up for instance a picture with bright background or web browser I can see transparent battery and CyanogemMod in the middle of the screen even tho phone's not charging and running on stock rom not CyanogenMod.
I think I've tried everything from fixing permissions, flash and re-partition using Odin and 512 pit file.
Even rang my Mom like advised in xda's video, didn't help either
Is there anything else I can try to get my phone in "shape"?
Any suggestions?
Click to expand...
Click to collapse
try to flash stock rom again via odin , root , then flash cm 9 ( to not loose you IMEI ) , then flash CM 10.1 stable from here : http://get.cm/?device=galaxysmtd&type=stable
then install any costum rom you want
The Tox said:
try to flash stock rom again via odin , root , then flash cm 9 ( to not loose you IMEI ) , then flash CM 10.1 stable
then install any costum rom you want
Click to expand...
Click to collapse
Thanks for your reply. Installing CM 9 worked but trying to install CM 10 throws up this error:
assert failed: run_program("tmp/updater.sh") == 0
E: Error in sdcard/cm-10.1.zip
(Status 7)
Installation aborted.
Flash this one :
http://get.cm/get/3Fb
then install this one :
http://get.cm/get/9aJ
Thanks for your help. CM 9.1.0 installs fine, same error for 10.1.2 :/
AllUsernamesAlreadyInUse said:
Thanks for your help. CM 9.1.0 installs fine, same error for 10.1.2 :/
Click to expand...
Click to collapse
did you tried to install other costum roms , like slimbean ?
There MIGHT be a problem with your internal SD card. Slight chance :/
did you tried to install other costum roms , like slimbean ?
Click to expand...
Click to collapse
Yes I did and only Franzys installed successfully but then stopped working after phone reboot.
There MIGHT be a problem with your internal SD card. Slight chance :/
Click to expand...
Click to collapse
I think that might be the case. I get encryption unsuccessful with my sdcard in and CWM doesn't see any files with sdcard out.
I found an article here on forum that explains how to use your external sdcard as the internal one. Will give it a try and see if it works.
For now I don't mind using CM 9.1.
Thanks for your help guys and let me know if you have any other suggestions.
Today Cyanogen updater notified me that the 10.2M build was available. I usually only flash stable builds, but I decided to check it out.
I was updating from 10.1.3- did everything as I always did, flashing seemed to go fine, but then I got stuck on the Cyanogen splash screen. So I went back to safestrap recovery, flashed back to 10.1.3- wiped cache etc... same thing. Just stuck on the Cyanogen splash. Tried installing 10.1.2, which was the first version I ever flashed. Same problem.
I was able to successfully boot back into stock using Safestrap (v3.11), but now I can't seem to get any version of Cyanogen to successfully boot.
Any suggestions?
Reboot into cm 10.2 before flashing gapps?
Sent from my XT894 using Tapatalk
Hello,
I rooted my phone about a year ago and was running an old Gummy ROM for the longest time until it stopped being supported and developed quite a few bugs. I went back to Stock via a restore and recently a friend showed me a ROM he was using and I figured I'd look into using a ROM again. I checked the Bionic forums and I found LiquidSmooth v2.2.1 targa and it looks clean and from the comments runs very fast. I installed the new safestrap, got the new gapps, and downloaded Liquid-JB-v2.9-OFFICIAL-targa. I rebooted, created a slot 3, and when I attempt to flash the ROM onto Slot 3 it immediately gives me an error. I flashed the gapps zip just to be sure it wasn't just not wanting to install anything. I have created and deleted rom slot3 a few times and downloaded the ROM probably 5 times now to be sure it wasn't a bad download.
The screen reads:
Updating partition details...
Installing '/sdcard-ext/Liquid-JB-v2.9-OFFICIAL-targe.
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_perm: some changes failed
E:Error executing updater binary in zip '/sdcard-ext/L
Error flashing zip '/sdcard-ext/Liquid-JB-v2.9-OFFICIA
Updating partition details...
And it says failed in the middle of my screen, can someone please help me out here, because I hate how slow stock is. Please!
I have since installed with no issues: cm-11-20140105-NIGHTLY-targa in slot 3. I am not for sure why Liquid wasn't working. My phone is a Moto Droid Bionic. Any help would be appreciated!
Thank you,
Al
You need the oldest safestrap to install liquid, 3.11.
Sent from my XT875 using Tapatalk 2
Did you try booting into that ROM slot after the "failed" flash? I get the same error flashing gapps over CM 11, but everything works fine when I boot the ROM.
*First a little background on what happened...
So due to an sight oversight on my side, and what I feel was a mistake on CMs part, I installed CM 13 over 12.1 one day on my droid turbo. I did not realize what was going on until after I had done it, it was just me keeping up with my normal updates. So I realized what had happened and used an older version of CM 12.1 that I had already downloaded and installed it. This rendered my phone unable to boot into an OS. No problem, I still had TWRP. I downloaded the flash able 5.0 stock ROM here
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
I then flashed myself back to stock, did a full wipe, then booted into stock to make sure everything worked correctly and it did. I then downloaded CM 13 and flashed it, and booted into it no problem.
*Now the issue at hand...
I then downloaded the GApps for my system, ARM/6.0/Stock and installed. Now my phone boots but when I unlock it, I get "Unfortunately, Setup Wizard has stopped" and "Unfortunately, Google Play Services has stopped". They keep popping up no matter how many times I press "ok" and prevents the use of the phone completely. I'm not sure where where to go from here. Any idea on getting over this? Wrong GApps perhaps?
BEDickey said:
*First a little background on what happened...
So due to an sight oversight on my side, and what I feel was a mistake on CMs part, I installed CM 13 over 12.1 one day on my droid turbo. I did not realize what was going on until after I had done it, it was just me keeping up with my normal updates. So I realized what had happened and used an older version of CM 12.1 that I had already downloaded and installed it. This rendered my phone unable to boot into an OS. No problem, I still had TWRP. I downloaded the flash able 5.0 stock ROM here
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
I then flashed myself back to stock, did a full wipe, then booted into stock to make sure everything worked correctly and it did. I then downloaded CM 13 and flashed it, and booted into it no problem.
*Now the issue at hand...
I then downloaded the GApps for my system, ARM/6.0/Stock and installed. Now my phone boots but when I unlock it, I get "Unfortunately, Setup Wizard has stopped" and "Unfortunately, Google Play Services has stopped". They keep popping up no matter how many times I press "ok" and prevents the use of the phone completely. I'm not sure where where to go from here. Any idea on getting over this? Wrong GApps perhaps?
Click to expand...
Click to collapse
I haven't flashed this rom for my turbo yet and this may not be the issue but in the past, dealing with other phones on CM, when you would 1st flash the rom, (& before rebooting the 1st time) you would then need to flash the gapps immediately after for everything to work properly. Try flashing the rom and gapps before rebooting.
I didn't see if the CM op instructions recommended this, just personal experiences from previous rom flashing.
I have had this happen twice after installing any CM13 on top of the March 31 nightly. I have not found a way around it yet besides doing a factory wipe after installing CM13, Open GApps and the latest radio code in this thread.