I am a little confused by Synergy 155. (Verizon Galaxy S3). I had 147 running, and the instructions said to "dirty flash" the ROM over 147, which I took to mean that I would not wipe dalvik, cache and factory reset. The ROM never seemed to initialize (go to the setup menu). Did I misread the instructions or do something wrong?
When you dirty flash a rom, it's just adding the new updates over top of what you have already. So you did everything right, you don't do another activation when dirty flashing. Just verify that your About Phone reads Synergy 155.
Sent from my SCH-I535 using xda app-developers app
Ech said not to wipe data on 147 ie no factory data reset.
SlimSnoopOS said:
When you dirty flash a rom, it's just adding the new updates over top of what you have already. So you did everything right, you don't do another activation when dirty flashing. Just verify that your About Phone reads Synergy 155.
Thanks, I was hoping I had that right. It still doesn't go past the boot animation on reboot with 155 installed over 147. I had to pull the battery and boot back to recovery and restore my previous install.
Click to expand...
Click to collapse
Thanks, I was hoping I had that right. It still doesn't go past the boot animation on reboot with 155 installed over 147. I had to pull the battery and boot back to recovery and restore my previous install.[/QUOTE]
If you put a custom theme on it then you will get stuck in a boot loop. If you made a backup of the original 147 with no theme or anything done to it just restore that then reflash 155. If not install a clean 147 reboot once then flash 155.
Sent from my SCH-I535 using xda premium
Has anyone else experienced this?.....
I flashed r147 and everytime I try to navigate around the new ROM, it just shuts off. So i rebooted hoping that would fix the issue, but no luck. So then I dirty flashed r155 and it does the same thing.
Sent from my SCH-I535 using xda premium
Related
Hello i am trying to flash the jellywiz ROM onto my phone. I just got the s3, rooted, and unlocked it using the app on playerstore; EZ 1 button. I have also used the EZ recovery app to flash TWP onto the phone. I made a backup of the current, stock ROM. After that, i wiped the data/factory reset, wiped cache/dalvik cache. Afterwards i installed the ROM jellywiz, reboooted it, but no luck. It is taking forever, has been near 20 minutes or so. And i know that is a bit too long, so am i missing an installation step somewhere or what?
I have no issues with jellywiz at all i have installed about 30 times to my gs3 the only time i have jelly wiz do things like you discribe is when i put a kernel or something with my install or gapps. also i use twrp as well
the steps to install are
wipe factory reset
wipe system
then install
then wipe davlik and cache
then reboot
initial boot up is about 2-5 min i have with the latest version rls11 had 20-30 min times but both times it happened i tried using ktoonz kernel.
i just installed the newest one which is RLS12, which he just uploaded not too long ago. That one worked perfectly fine. I guess maybe something was wrong with the other one. But i have it on my phone now
just pull the battery then boot back up should be fine. sometimes it will hang like that, happened to me a couple times.
Sent from my SCH-I535 using xda app-developers app
I have had nine take a long time to boot up, if it takes longer than 15 minutes I usually pull the battery an reboot, if that didn't work I pull the variety and reboot into recovery and go back to my backup which I always make before I flash a new rom
Sent from my SCH-I535 using xda app-developers app
I have an att htc one x that has 4.01 and 2.20 software. I was able to successfully root the phone and now I'm trying to install CM10 but it's failing when trying to install.
It says it missing a MD5 File and says theres an error in the SD card/download/ the cm 10 file.
What am I doing wrong? Thank you
Make sure the Rom is for our phone and check the md5 sum it might be a bad download
I've tried redownloading the file several times and I'm still getting the same error message.
I'm downloading CM10 from here http://get.cm/?device=endeavoru
kswannabe said:
I've tried redownloading the file several times and I'm still getting the same error message.
I'm downloading CM10 from here http://get.cm/?device=endeavoru
Click to expand...
Click to collapse
Wrong version, endeavoru is the international (Tegra3) One X. Our phone is code named evita.
Just stick to the Development forum here, to avoid flashing ROMs for the wrong version of the One X:
http://forum.xda-developers.com/forumdisplay.php?f=1726
Thanks for the information.
Was able to successfully flash to CM10 but I'm stuck at the CM10 boot screen. Circle going counter clock wise around. What should I do?
kswannabe said:
Thanks for the information.
Was able to successfully flash to CM10 but I'm stuck at the CM10 boot screen. Circle going counter clock wise around. What should I do?
Click to expand...
Click to collapse
If you flashed an international rom, there's a good possibility you messed something up. Factory reset, wipe /system, and try flashing the correct CM10 rom again.
Ok. I'm trying to do a factory reset from bootloader but whenever I do, it goes to the CM10 boot screen where I was earlier. How can I do a factory reset?
kswannabe said:
Ok. I'm trying to do a factory reset from bootloader but whenever I do, it goes to the CM10 boot screen where I was earlier. How can I do a factory reset?
Click to expand...
Click to collapse
A guy I was working with had the boot screen splash. If you've flashed the correct one, then wipe your caches. if that doesn't work reflash.
kswannabe said:
Ok. I'm trying to do a factory reset from bootloader but whenever I do, it goes to the CM10 boot screen where I was earlier. How can I do a factory reset?
Click to expand...
Click to collapse
Don't do it from bootloader, it can corrupt your sdcard. Do it from recovery.
Go into recovery, wipe cache, dalvik cache, factory reset and system. Then install the CORRECT rom.
Sent from my One X using xda premium
How can I reflash?
Thanks
-edit-
I was able to get back into TWRP. There I tried to do a factory reset but it tells me it failed. And after installing CM10, do I have to go back into bootloader and flash boot.img from the CM10 nightly zip file?
And there goes my stock rom... Factory reset is not working on TWRP and tried system reset thinking it would get rid of CM10 but instead erased my stock rom.
Please help, need a working phone soon..
kswannabe said:
How can I reflash?
Thanks
-edit-
I was able to get back into TWRP. There I tried to do a factory reset but it tells me it failed. And after installing CM10, do I have to go back into bootloader and flash boot.img from the CM10 nightly zip file?
Click to expand...
Click to collapse
There are stickies and tuts around here for this.. but, the reason why it's not working for you is you didn't flash the boot.img first. before you installed the .zip. Also, you'll need the latest gapps for that ROM as well.
Not familiar with the forums around here, so if you could link me some of these stickies or tutorial it would be great.
Have a look here
Sent from my One X using xda premium
timmaaa said:
Have a look here
Sent from my One X using xda premium
Click to expand...
Click to collapse
or here http://forum.xda-developers.com/showthread.php?t=1952076
I have this problem. i went to the thread you posted, loaded TWRP, I've factory reset and what not, but now I'm stuck in TWRP without any real viable options. When I try to reboot to system, it brings me back to TWRP menu.
mfc1288 said:
I have this problem. i went to the thread you posted, loaded TWRP, I've factory reset and what not, but now I'm stuck in TWRP without any real viable options. When I try to reboot to system, it brings me back to TWRP menu.
Click to expand...
Click to collapse
Do you have a rom flashed? If so, wipe both caches and reboot. If that doesn't work, reflash and do a system wipe from TWRP.
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
Rooted SGH-T989D trying to flash CM10
kswannabe said:
How can I reflash?
Thanks
Click to expand...
Click to collapse
hi. i have fallowed all the steps to root my phone from this site. when i go down to how to flash a rom i have some issues.
i am trying to flash CM10. when i go to install on (step 8) i get an errer. my screen says
Updating partition details...
Running boot script...
Finished running boot script.
E:Unable to open zip file.
Error flashing zip /external_sd/cm-10.1-hercu
Updating partition derails...
then it shows the home butten. failed in red than wipe cach/dalvik and reboot system buttons
anyone have any idea what im doing wrong?
Exactly which phone do you have? It looks like it says Hercules in the cm file name you wrote, which I think is a Samsung.
Sent from my Evita
I have Verizons S3. I recently rooted and unlocked the bootloader and have TWRP recovery. I was on 4.1 JB. I made a Nandroid Backup of System and Data. I then flashed the CM10.1 Monthly ROM, and all seemed to be working fine. However, I was having some issues with my app backups and the weird "emulated" directory structure. So I decided to go back to my Nandroid Backup and start over.
I went into TWRP, did a factory reset, cleared System Data, cache/dvalick cache, then I restored the Nandroid Backup (system and data). TWRP said it was successful and asked to reboot. When I did, the Samsung logo flashes, and then the screen stays black. I tried going back into recovery, but it won't let me. I can get to download though.
I think I'm going to have to use Odin to reflash a ROM as I can't get into recovery, right? But I'm also trying to understand what I did wrong. Did I forget a step? Did it have something to do with differences between 4.1 and 4.2? I'm new to this, and have searched the forums but can't find anything that answers my questions specifically. I appreciate the help.
anacree said:
I have Verizons S3. I recently rooted and unlocked the bootloader and have TWRP recovery. I was on 4.1 JB. I made a Nandroid Backup of System and Data. I then flashed the CM10.1 Monthly ROM, and all seemed to be working fine. However, I was having some issues with my app backups and the weird "emulated" directory structure. So I decided to go back to my Nandroid Backup and start over.
I went into TWRP, did a factory reset, cleared System Data, cache/dvalick cache, then I restored the Nandroid Backup (system and data). TWRP said it was successful and asked to reboot. When I did, the Samsung logo flashes, and then the screen stays black. I tried going back into recovery, but it won't let me. I can get to download though.
I think I'm going to have to use Odin to reflash a ROM as I can't get into recovery, right? But I'm also trying to understand what I did wrong. Did I forget a step? Did it have something to do with differences between 4.1 and 4.2? I'm new to this, and have searched the forums but can't find anything that answers my questions specifically. I appreciate the help.
Click to expand...
Click to collapse
You're supposed to backup "boot.img" as well. I'm pretty sure boot.img is the kernel which you failed to backup. The phone won't boot into your nandroid because the kernel wasn't restored as well. In TWRP: system, data, and boot are all supposed to be backed up simultaneously if you want to restore the entire nandroid. Odin flash and make sure to do a proper nandroid with all three that I listed.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
You're supposed to backup "boot.img" as well. I'm pretty sure boot.img is the kernel which you failed to backup. The phone won't boot into your nandroid because the kernel wasn't restored as well. In TWRP: system, data, and boot are all supposed to be backed up simultaneously if you want to restore the entire nandroid. Odin flash and make sure to do a proper nandroid with all three that I listed.
Click to expand...
Click to collapse
Ah, perhaps that "boot" checkbox wasn't check. =P So basically the CM10.1 boot.img is still there, but now the wrong ROM is there so it won't boot? Can I just flash the boot.img with Odin now, or will I need to do a full ROM flash?
anacree said:
Ah, perhaps that "boot" checkbox wasn't check. =P So basically the CM10.1 boot.img is still there, but now the wrong ROM is there so it won't boot? Can I just flash the boot.img with Odin now, or will I need to do a full ROM flash?
Click to expand...
Click to collapse
Flash nandroid and then try to flash a kernel. Might work Idk. Worth a shot.
sent telepathically
---------- Post added at 07:14 PM ---------- Previous post was at 07:13 PM ----------
jdub251 said:
Flash nandroid and then try to flash a kernel. Might work Idk. Worth a shot.
sent telepathically
Click to expand...
Click to collapse
Edit. Are you still not able to get into recovery? Sorry missed that in your post.
sent telepathically
jdub251 said:
Are you still not able to get into recovery? Sorry missed that in your post.
Click to expand...
Click to collapse
No, when I do the button combo for recovery, the word "Samsung" flashes, then "Galaxy S3" logo, but after that nothing...just blank screen. I was on stock Verizon s3 before this, so I guess I need to put that kernel back on the phone? Is the kernel the same as the bootloader? Can I use the unlocked bootloader referenced in this post: http://forum.xda-developers.com/showthread.php?t=1974114?
So, I tried using Odin to flash back the stock JB 4.1.1 kernel, which should have matched my Nandroid backup, but then I got an unlocked padlock on my splash screen and then the yellow triangle. blah. so i flashed a stock no wipe rom and that got me back into touchwiz, but I cant get into recovery no matter what i do. And I still have the padlock. I think I may need to do a stock full wipe rom?
anacree said:
So, I tried using Odin to flash back the stock JB 4.1.1 kernel, which should have matched my Nandroid backup, but then I got an unlocked padlock on my splash screen and then the yellow triangle. blah. so i flashed a stock no wipe rom and that got me back into touchwiz, but I cant get into recovery no matter what i do. And I still have the padlock. I think I may need to do a stock full wipe rom?
Click to expand...
Click to collapse
If you flashed a fully stock rom then you need to root, unlock, and install your custom recovery again.
Sent from my SCH-I535 using xda app-developers app
Ok, so I finally got time to try this again after flashing back to (what I thought) was stock Jelly Bean 4.1. I was following the directions here in this thread: http://forum.xda-developers.com/showthread.php?t=2046439
I get the VRALEC bootchain fine, phone reboots and all seems well. I got to flash TWRP 2.4, do a batter pull, and when I try to boot into recovery mode suddenly there is the Samsung splash screen with an unlocked padlock on it. Then the screen goes black and doesn't go into recovery. When I release the buttons, the phone then boots into the OS. I can still get to the download mode, but for some reason I can't get into a custom recovery. Any help on this? Please?
I used this file to wipe my phone back to stock JB: COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship.tar.md5
Thanks for the assistance. =)
Redo step three like the directions state.
Edit : In that thread, some folks even suggest waiting 5-10 mins after its successfully flashed before booting into recovery.
Sent from my SCH-I535 using xda app-developers app
Forgot to followup here, but I got it working. I left my phone plugged in after flashing the recovery for like 15 minutes. I also released the power button on trying to boot into recovery once the Samsung logo appeared. I finally got into recovery and was so happy. Thanks for the help!
Running mastamoon's unofficial CM 10.1. =)
anacree said:
Running mastamoon's unofficial CM 10.1. =)
Click to expand...
Click to collapse
Perfect! Glad you've got it all working properly!
Sent from my SCH-I535 using xda app-developers app
Okay so Im trying to install miui v5 but im having isuues getting it to boot...again. ok so when v4 3.2.22 first came out I couldnt get it to boot. I would install the rom, then gapps and could not get it to boot past the optimizing apps screen. it would just stay at starting apps. I was told by another user to flash rohans kernel version b5 as that has worked for him on a different rom, and it worked for me. Now trying to install V5 its been a nightmare. when just installing the rom, then gapps I could not get it to boot past the splash screen. it would load it for a second then just go to a black screen. I then tried installing rohans kernel version b5 but now I get stuck at the starting apps screen I tried wiping cache and dalvik and that did nothing. tried installing different kernels and most I tried wouldnt let me get past the boot animaion Im using twrp 2.3.1.0, Im s-off and I even tried lowering my hboot from 1.14 to 1.09 just incase that might be it but nope. im no sure what else to do and help would be greatly appreciated
avery.0 said:
Okay so Im trying to install miui v5 but im having isuues getting it to boot...again. ok so when v4 3.2.22 first came out I couldnt get it to boot. I would install the rom, then gapps and could not get it to boot past the optimizing apps screen. it would just stay at starting apps. I was told by another user to flash rohans kernel version b5 as that has worked for him on a different rom, and it worked for me. Now trying to install V5 its been a nightmare. when just installing the rom, then gapps I could not get it to boot past the splash screen. it would load it for a second then just go to a black screen. I then tried installing rohans kernel version b5 but now I get stuck at the starting apps screen I tried wiping cache and dalvik and that did nothing. tried installing different kernels and most I tried wouldnt let me get past the boot animaion Im using twrp 2.3.1.0, Im s-off and I even tried lowering my hboot from 1.14 to 1.09 just incase that might be it but nope. im no sure what else to do and help would be greatly appreciated
Click to expand...
Click to collapse
Wipe everything. Install your rom only. Does it boot?
exad said:
Wipe everything. Install your rom only. Does it boot?
Click to expand...
Click to collapse
no. It loads the splash screen for a second then goes to a black screen.
You've verified the md5 right?
Boot to bootloader/fastboot and do fastboot erase cache in command prompt then wipe everything cache, dalvik, system, factory reset, then flash rom.
Does it boot?
Sent from my HTC One X using xda app-developers app
exad said:
You've verified the md5 right?
Boot to bootloader/fastboot and do fastboot erase cache in command prompt then wipe everything cache, dalvik, system, factory reset, then flash rom.
Does it boot?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
redownloaded 3 times. erased cache. wiped everything and same problem as before loads splash screen then back screen
Redownloading != checking md5 you could Redownload 500 times and all 500 downloads could have corruption of some sort.
You did fastboot erase cache?
If you're positive your download is good and after fastboot erase cache and wiping everything isn't working. Your last step is to s-off if you're not already and ruu to the latest version then flash twrp then wipe everything then flash the rom.
Sent from my HTC One X using xda app-developers app
exad said:
Redownloading != checking md5 you could Redownload 500 times and all 500 downloads could have corruption of some sort.
You did fastboot erase cache?
If you're positive your download is good and after fastboot erase cache and wiping everything isn't working. Your last step is to s-off if you're not already and ruu to the latest version then flash twrp then wipe everything then flash the rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Just making sure since I have only researched slightly, since im s-off If i run the latest unrootable RUU Id still be able to unlock bootloader and regain root?
What other roms have you tried to flash? Is Mui the only ones giving you problems? Try other ones to see if it is not a bad twrp. It may not be wiping correctly.
Sent from my HTC One X using xda premium
Venomtester said:
What other roms have you tried to flash? Is Mui the only ones giving you problems? Try other ones to see if it is not a bad twrp. It may not be wiping correctly.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
every other rom ive flashed boots fine its only miui that gives me problems. It boots for other people fine so I dont think its the rom and I tried to install on CWM and still have issues
I had the same problem with Chameleon. Took four different downloads to get it. Avatar took a few too lol. Take above advice. Check sum. Might even try wiping cache in adb.
Sent from my HTC One X using xda premium
Venomtester said:
I had the same problem with Chameleon. Took four different downloads to get it. Avatar took a few too lol. Take above advice. Check sum. Might even try wiping cache in adb.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
noob question but how do I find the md5?
avery.0 said:
noob question but how do I find the md5?
Click to expand...
Click to collapse
Search MD5 Sum Checker. It's a program that is pretty self explanatory and will check it for you. The MD5 is attached to the download. You copy it from the site and past it in the checker.
And after you s-off you don't need to re lock to ruu so you won't lose bootloader unlock
Sent from my HTC One X using xda app-developers app
Running the 3.18 RUU fixed my problems. Thank you both for the help
Sent from my HTC One X using xda premium
My One has been acting up lately. It started out that I couldn't turn off WiFi. I would turn it off but it would turn itself back on shortly thereafter. It has nothing to do with WiFi optimization or anything like that...I've fiddled with all those settings. Anyway, I updated to 38R thinking it might fix things, but no such luck. So I fire up titanium backup in preparation for a full wipe and find out that my device is no longer rooted. On top of that, TWRP is gone as well. No big deal, reflash TWRP and re-root. Nope. ADB says that TWRP flashes successfully, but when I boot into recovery I get the standard Cyanogen recovery instead of TWRP. Any thoughts?
Have you tried flashing stock and starting from scratch?
Did you remember to uncheck the option for updating fastboot with system update as well?
Sent from my Nexus 7 using XDA Premium HD app
Admeisterz said:
Have you tried flashing stock and starting from scratch?
Did you remember to uncheck the option for updating fastboot with system update as well?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Unfortunately I missed the fastboot update bit. Did I **** myself with that?
If you could access CWM do a factory reset, and hopefully that clears up your problems, if not go back to stock via: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
the only reason why i could think that it'd say flashing is successful is it's flashing to the wrong partition (which doesn't make any sense), or the bootloaders locked, which it isn't since from your post it says you had TWRP installed, but try going back to stock fully via fastboot, then installing twrp and such.