Related
I am unable to flash any roms except cm6 ( I can also flash any nightlies. )
This is driving me crazy. I have tried to flash fresh 3.2 to no avail. I have also tried to install the new virus rom. I attempted to install the rooted version off the newest ota with the same results.
After each attempt the result is the same. It will just hang on the HTC evo 4g screen.
I have downloaded the roms a few times each to ensure they were completed correctly.
I have pulled the battery and waited.
I have deleted all data / dalvik / Cache several times in a row.
I have attempted to flash using a different version (earlier) of clockwork with the same results.
I even attempted to flash with RA recovery. Same results.
I am completely lost as to why I can only flash cm6 roms
Please let me know any suggestions.
Sent from my PC36100 using XDA App
From what I have read...................
You need to restore a 2.1 or a 2.2 rom you have, boot to that, then you can flash to a 2.2 rom.
You can't go from CM directly to another rom.
I am on 2.2
Sent from my PC36100 using XDA App
An HTC rom.
CM is not a typical ROM.
Restore your original backup, and try from there. If you don't have one, you may need to RUU
Bielinsk said:
An HTC rom.
CM is not a typical ROM.
Restore your original backup, and try from there. If you don't have one, you may need to RUU
Click to expand...
Click to collapse
Ok, so basically I am going to unroot - reroot?
I just flashed from cm6 straight to baked snack directly with no problems. Not really helpful but you shouldnt need to flash to a stock rooted rom first. Note sometimes you have to wait a good 5 minutes for the htc screen to go away. Probably took about 5 when I moved from cm6 to snack.
I just tried again, attempted to go to fresh. I let it sit for 10 minutes with no results.
Defpdp said:
I just tried again, attempted to go to fresh. I let it sit for 10 minutes with no results.
Click to expand...
Click to collapse
I unrooted- rerooted with the same results, I cannot flash ANY roms other than Cm6 it seems, this is very frustrating..
Anyone else have any ideas at all??
Thanks!
Try flashing a new recovery. If you're using the newest amon go back to the last one or vice versa. Or even move over to clockwork. But I would ask about that I know clockwork doesn't play well with cm6. This could get you in trouble but I guess you always go back to amon.
crimeslunk said:
Try flashing a new recovery. If you're using the newest amon go back to the last one or vice versa. Or even move over to clockwork. But I would ask about that I know clockwork doesn't play well with cm6. This could get you in trouble but I guess you always go back to amon.
Click to expand...
Click to collapse
Nothing worked, tried going to different recoveries/versions. Nothing.
Anybody? Any advice?
if you flashed cm6 and have it working... its my understandung that you cqn not just go and flash a different rom. there is a process that needs to be followed.
but i have never and never will use cm6 so i could easily be talking from my rear.
Sent from my PC36100 using XDA App
I flash from cm6 to rooted stock rom when I need to update prl and stuff.
After you flash wipe dalvik and cache again I had that problem when flashing snap.
Im not sure if these don't help. Maybe you can send a tweet to cyanogen himself to get it resolved. If fix pst your findings
Sent from my PC36100 using XDA App
Re root and see what happens
Sent from my PC36100 using XDA App
Also check your kernel, you shouldnt have to flash anything but the rom you want when switching from cm6
Here is my question, I like switching between two ROMs. I'm currently running Wildstangs stock ROM with the current Tiny's kernel. I installed CM7.1.0 also with the incredikernel ics+. All was fine with it then i switched back to my stock ROM for a few days but when i tried to switch back to CM7 it gets stuck at my custom boot image. I left it there for 30 minutes just to see if it would boot but nothing.
Now here is the question. Is there a particular way you have to switch between ROMs? As in the wiping process etc.
Thanks for your time.
Sent from my ADR6300 using xda premium
If you switch between two ROMs using a nandroid you shouldn't have to do anything special. If it fails it could be a bad backup. Try doing a full wipe before restoring just in case (format /system, data/factory reset).
Thanks for the info. I just don't like being stuck using one ROM. LOL
Sent from my ADR6300 using xda premium
Me neither. I would occasionally try the latest Sense 3 ROMs after being on CM7 for a while but ended back on CM7. But I'd hate to be stuck on one ROM. Even though I settled on CM9 pretty much on my Galaxy Nexus, I still want the option in case I want to switch as AOKP is my second choice.
I completely agree!
Sent from my ADR6300 using xda premium
Anytime I download a new ROM I always check my md5 sums for a mismatch. I use md5 checker on my phone, cause you can corrupt the file transferring it to your phone if you used a computer to download it.
When doing a lot of switching, I definitely recommend to use VR_SUPERWIPE-edify. You just run it like you would a ROM in your recovery menu and it wipes everything for you. Makes switching go a lot quicker.
thenewbigmack said:
When doing a lot of switching, I definitely recommend to use VR_SUPERWIPE-edify. You just run it like you would a ROM in your recovery menu and it wipes everything for you. Makes switching go a lot quicker.
Click to expand...
Click to collapse
+1 on the SUPERWIPE. I use it every time and have yet to have an issue... *knocking on wood*
Sent from my Droid Incredible using XDA
First a little background. I am not new to the android world whatsoever. I don't post much but have been lurking for years. I had a Verizon GS3 and just recently switched to T-Mobile a few days ago and obviously bought a T-Mobile GS3. My vzw phone had no problems. But for some reason my T-Mobile phone will not boot any kernel I try to flash. Roms flash fine but when I flash a kernel everything goes fine in recovery but my phone won't boot past the splash and I end up having to restore a backup. I know I'm flashing the right kernels. I am on touchwiz based ROMs and haven't tried any aosp Rom because for the first time ever I actually prefer an OEM skin to aosp. So basically am I missing something obvious. Anyone else having thus problem. On Verizon I had to root and unlock the bootlosder. From what I understand tmobiles bootliader was not locked down and all I had to do was root. Like I said. I've tried every touch wiz Rom and every touch wiz kernel with each Rom and none will boot past the splash screen. I always wipe dalvik and cache but even tried wiping data every time too and keep getting the same result. Any input would be appreciated. . Thanks in advance.
Sent from my SGH-T999 using xda premium
Shouldn't need to do any wiping of any kind. I only use AOSP/AOKP, though. May I ask why you even bother with custom kernels? They honestly seem like a waste of time to me.
Im just flash happy. Like to try them out. I've been on Verizon for many Years and am used to the developers over there. I'm still getting used to the devs over here. Don't know any of there work. I'm sure its all good though. Been using imoseyons lean kernel since the thunderbolt back in the day and have stuck with them. Just my personal preference. I'd like to try some of tmobolrs kernel devs work but like I said I can't get a single one to boot.
Sent from my SGH-T999 using xda premium
What kernels have you tried to flash? There are a couple that have ICS builds. Also, what version of CWM are you using?
I've tried all the tw kernels. Every single one with 2 different ICS tw ROMs. I'm not using the leaked jb tw. I'm stickung with the more stable ICS ROMs for now. I just don't understand. I've tried every one. I've been flashing a long time and don't get it. Im kinda new to Samsung though. First Samsung was the galaxy nexus. Didn't ever use Odin with it. Does anyone flash kernels with Odin. Maybe I should try that. And to answer your question I've tried twrp and the latest version of cwm from rom manager. And of course I'm using the ICS TW version of the kernels im trying.
Sent from my SGH-T999 using xda premium
It could just be your phone doesn't like them. There is another guy on CM10 and AOKP that can't get custom kernels to boot either.
Sent from my Nexus 7 using Tapatalk 2
The kernel source code was never released for any build from UVALH2 and beyond. So most of our kernels will only work with UVALEM and UVALG1 builds.
We got kind of lucky I think and ktoonsez att kernel was brought over and works. I think there's one or two others that work now too.
As far as described here go I think we've got some of the best! For an outstanding rom you should try FreeGS3. It works with most of the kernels and is an awesome stable rom. If you want a later build try wildcards XquiziT v70 based on UVALH2. Use ktoonsez kernel with it.
And just to note, the stock kernel is surprisingly good. So give it a fair shot as well. Though I can definitely see some potential advantages of custom ones as well.
Sent from my SGH-T999 using xda app-developers app
Thanks for all the info. But now I can't even get any other ROMs to boot. I don't get it. I keep having to restore my Xquizit v20 back up. Its driving me nuts
Sent from my SGH-T999 using xda premium
jasonpantuliano said:
Thanks for all the info. But now I can't even get any other ROMs to boot. I don't get it. I keep having to restore my Xquizit v20 back up. Its driving me nuts
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Have you done full Wiping?
Wipe Data/Factory Settings
Wipe cache and dalvik
Flash Rom
Fix Permission
Reboot and don't touch it for 10 minutes
Reboot.
Wipe cache and dalvik
Flash Kernel (Must be compatible with ROM)
Fix Permission
Reboot and don't touch it for 10 minutes
Reboot.
See if this will work. Sometimes you have to let it breathe so it can adjust itself.
Have you tried uding odin to flash MrRobinsons root66 UVALH2? This will take you to fresh full stock plus root. Then try roms again.
Sent from my SGH-T999 using xda app-developers app
Whatever you do................
Be sure to double check before you flash that kernel. Had my first SGS3 for 12 days before hard brick set in. Terrible disease it is.......! I had to adopt a replacement shortly after to cope with the pain of the loss. Back on my feet again now though and soarin' higher than giraffe vagina on the things I learned in my days off for mourning. I can tell ya I've personally flashed the lean kernel and kt-747 with no issues. My problems were with siya mainly.
Guys, I have a serious problem.
It's similar to the one of the thread-opener.
The diference is that I cant get ANY ROM to boot, WITH the stock kernel.
And i do like the guide says: wipe/factory reset, wipe chache, wipe dalvik cache and then flash the ROM.
Everything works fine til the ROM finished flasing and runs a reboot.
My S3 shuts down screen, then turns screen on with the "Samsung Galaxy SIII-GT-I9300" and then thats it!
All i can do is to go in download mode or recovery mode. I can also flash CWM and so on, but after flashing ROMs it won't boot!
Is it possible that i broke the device by formating internal sd-card with the stock recovery tool?
Did it, after I tried to install Wickedv6 ROM and after both times when it rebooted it just reinstalled stock ROM. So i thought, ok delete the internal sd-card, so no stock ROM on it any more.
Also tried this ROM: http://forum.xda-developers.com/showthread.php?t=1875923
Same problem.
Also tried to fix the problem by rooting and then flashing ROM. No help.
Please help guys!
Best regards
ke-ironman said:
Guys, I have a serious problem.
It's similar to the one of the thread-opener.
The diference is that I cant get ANY ROM to boot, WITH the stock kernel.
And i do like the guide says: wipe/factory reset, wipe chache, wipe dalvik cache and then flash the ROM.
Everything works fine til the ROM finished flasing and runs a reboot.
My S3 shuts down screen, then turns screen on with the "Samsung Galaxy SIII-GT-I9300" and then thats it!
All i can do is to go in download mode or recovery mode. I can also flash CWM and so on, but after flashing ROMs it won't boot!
Is it possible that i broke the device by formating internal sd-card with the stock recovery tool?
Did it, after I tried to install Wickedv6 ROM and after both times when it rebooted it just reinstalled stock ROM. So i thought, ok delete the internal sd-card, so no stock ROM on it any more.
Also tried this ROM: http://forum.xda-developers.com/showthread.php?t=1875923
Same problem.
Also tried to fix the problem by rooting and then flashing ROM. No help.
Please help guys!
Best regards
Click to expand...
Click to collapse
This isn't the I9300 forum, but if you flashed a T999 rom, you bricked your phone.
Aerowinder said:
This isn't the I9300 forum, but if you flashed a T999 rom, you bricked your phone.
Click to expand...
Click to collapse
Wow, you scared the **** out of me
But i just tried to flash stock ROM: http://forum.xda-developers.com/showthread.php?t=1646610
It worked out!
What is the right forum for my GT-I9300 to post then?
And why isn't any other ROM working?
The forum you got that stock rom from is the international one. This is the US Tmobile T999 forum. The two phones are NOT compatible.
Only flash, well...anything, from that forum. Our roms will brick yours and vice versa.
Sent from my SGH-T999 using xda app-developers app
I been flashing roms for a year now and the only time I was on stock is when my phone was new. But I hear other ppl say it's best to flash to stock via odin before installing a custom rom. I don't see a difference.
Your still flashing even if it's going to stock right?
Please tell me your opinion on the matter.
I do from time to time but every time is a bit overkill and how little I trust Odin plays into that as well.
Sent from my SAMSUNG-SGH-I747 using xda premium
hednik said:
I do from time to time but every time is a bit overkill and how little I trust Odin plays into that as well.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Agreed.
If you format /system when switching roms, you're removing the OS anyways, thus allowing for a completely clean install
Actually, with the stock roms we have available, its a waste of time to flash stock between ROM flashes. LG1 (att) is the only one that actually does a full wipe. Problem is it also wipes your internal sd when you flash it. So even if you flashed DK3, for example, you would still have to do a factory reset from recovery if/when you bootloop. These no wipe packages are the reason so many ppl bootloop after flashing stock.
mrhaley30705 said:
Actually, with the stock roms we have available, its a waste of time to flash stock between ROM flashes. LG1 (att) is the only one that actually does a full wipe. Problem is it also wipes your internal sd when you flash it. So even if you flashed DK3, for example, you would still have to do a factory reset from recovery if/when you bootloop. These no wipe packages are the reason so many ppl bootloop after flashing stock.
Click to expand...
Click to collapse
I just use a complete wipe script and flash that way. Takes 5 seconds and I never have a bad flash. 2 years without a single boot loop or bad flash
Sent from my SAMSUNG-SGH-I747 using xda premium
Those are good to use. On my old htc I had 4ext recovery and it had a button to wipe everything except your sd card. I miss that recovery.
hednik said:
I just use a complete wipe script and flash that way. Takes 5 seconds and I never have a bad flash. 2 years without a single boot loop or bad flash
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Those wipe scripts are great. Half the problems in q&a wouldn't exist if they were used more often
Hello. I currently have TWRP 2.5.0.0 recovery installed along with LiquidSmooth rom.
About a month ago i installed android tweaker pro (sorry i cant post the link to the app cause im a noob ) and enabled some of the settings. Now everytime i reboot my phone it gets stuck on the boot animation, and i have to pull the battery and turn it back on to make it boot properly. Sometimes i have to do this multiple times until it boots properly. I have tried uninstalling the app but that also hasnt fixed it. Does anyone have an idea of how to fix this without reflashing a rom? Also is it bad for the phone to pull the battery often?
Can you boot to recovery? Restore the backup you made before this started happening. Assuming you made a backup.
If not, go to download mode and Odin stock.
Sent from my SGH-T999 using xda app-developers app
Or tru a factoru reset first (you'd prob be forced to if you odin stock since you're on liquid smooth now) since uou have twrp it won't wipe you're internal sd, but it will wipe out your apps and some appdata, as well as your settings.
Nandroid backup first.
Sent from my SGH-T999L using xda premium
wouldnt reflashing the rom be good enough?
chromium96 said:
wouldnt reflashing the rom be good enough?
Click to expand...
Click to collapse
Agreed just reflash rom and relfash gapps should be fine.
chromium96 said:
wouldnt reflashing the rom be good enough?
Click to expand...
Click to collapse
Not necessarily. If the problem is from some data left from a mod or app he tried, flashing the rom probably won't fix it. That would only be a fix by itself if the problem were somewhere on the system partition. So he would wind up factory resetting. I just suggested trying this first. But reflashing could be done first too, either way.
Plus 90% of boot issues are solved with a factory reset.
You guys are right though, in that it'll be better to try flashing the rom. Its probably a better first/second step than Odin flashing the stock firmware.
Sent from my SGH-T999L using xda premium
Thanks for the replies everyone. My original question was is there a way to fix this without flashing a rom? Is pulling the battery every time I boot bad for the phone? I'm a bit scared of flashing roms so I want to avoid doing it if possible.
I gave you one option. Factory reset. Aside from that uour best and probably only other option is to flash the rom. Thats why they suggested it.
As for battery pulling, it shouldn't do much, but you can end up with corrupted files, and it is possible (though unlikely) that you could damage some hardware.
Its not recommended, but if you gotta do it......well, you gotta do it.
Sent from my SGH-T999L using xda premium
KeyLemonPie said:
Thanks for the replies everyone. My original question was is there a way to fix this without flashing a rom? Is pulling the battery every time I boot bad for the phone? I'm a bit scared of flashing roms so I want to avoid doing it if possible.
Click to expand...
Click to collapse
I don't think it's bad for your device, but do you honestly want to be pulling a battery everytime you boot your device?
Try the different options posted. You shouldn't be scared of flashing roms if you read directions carefully.
Sent from my SGH-T999 using xda app-developers app