Everytime I install a custom rom on rom manager, it has corrupted my phone and each and everytime I'd have to restore it. Is there any way to fix it? I've seen comments on the custom roms and people have commented that it works fine on the DHD.
Hi drkhrsy
Kindly explain further by your meaning of corrupt? This would allow us here to clearly understand the problems you're facing. Thanks.
Well I first installed cyanogenmod 7 and that gave me the boot loop. After restoring the phone I thought I'd try another ROM, so I went to download the TB 7.0.3 ROM and that booted up the phone but I had constant popups on HTC sense force closing and couldn't do anything else so I had to restore the phone again. So yeh, I'm not really sure what I'm doing wrong here.
drkhrsy said:
Well I first installed cyanogenmod 7 and that gave me the boot loop. After restoring the phone I thought I'd try another ROM, so I went to download the TB 7.0.3 ROM and that booted up the phone but I had constant popups on HTC sense force closing and couldn't do anything else so I had to restore the phone again. So yeh, I'm not really sure what I'm doing wrong here.
Click to expand...
Click to collapse
Did you do a full wipe before flashing those roms, multiple fcs normally indicate that you didn't try a full wipe then reflash either of your chosen roms.
Full wipe as in factory settings?
Well I've installed a new RUU after the boot loop problem, isn't that considered as a full wipe? or should I just do a wipe again now?
I had that horrible boot loop aswell after installing Rom.manager but I fixed it with a ruu
Sent from my Desire HD using XDA App
Installing a new RUU does not constitute that you have full wipe any data and cache. As the ROM you tend to flash is, in a small or large extent, relatively different from that of RUU. That why we always advised to do a full wipe whenever we wish to flash ROMs. Else it will cause some issues such as Force Close issues.
You have to boot into recovery and select Wipe Data and Wipe Cache. That you will consider yourself that you have wipe those data and caches. Then now you can flash the desired ROM in your list.
In addition, before flashing is best to do a Nandroid back-up.
Also do check on your recovery version before you flash any ROMs as different ROMs need/may require different version in order to be flashed successfully(i.e. no or minimal issues)
Cheers mate.
aiight sweet, I'll give that a go.
Cheers!
You're most welcome.
drkhrsy said:
aiight sweet, I'll give that a go.
Cheers!
Click to expand...
Click to collapse
Memory serving EVERY ROM says you MUST perform a wipe of data and cache if coming from a different ROM. This is custom ROM 101. Please read instructions thoroughly before doing things like this. The ROM devs don't spend their free time writing instructions just for the hell of it.
Regarding ROM Manager, don't you get asked if you want to wipe data and cache when you flash a new ROM (or is that not an option on the free version)?
Yeh I do get asked for wiping data and cache, I do that and it just seems to still screw up. Also backing up my files through clockwork seems to make my phone get stuck on the HTC boot up screen which requires me to reformat using the RUU file.
I would suggest re-flashing the recovery.img file.
Also, are you using the same cwm-r version to restore as used to create backup? For example, If version 2.x.x.x was used to backup you can't use 3.x.x.x to restore.
Sent using witchcraft via XDA Developers Premium App.
I've just checked my CWM-R version and its recovery version is at 3.0.2.6 hmm now I cant get into the recovery boot screen :S. I'd just most likely restore the phone again and try root the phone again. but thanks anyway
nvm I got in the recovery boot. Yeh the CWM-R are the same version.
drkhrsy said:
nvm I got in the recovery boot. Yeh the CWM-R are the same version.
Click to expand...
Click to collapse
I think you miss understand. I don't mean do they match wherever you look.
Did you make the original backups using version 3.0.0.x or 2.5.x.x?
Sent using witchcraft via XDA Developers Premium App.
drkhrsy said:
I'd just most likely restore the phone again and try root the phone again.
Click to expand...
Click to collapse
You don't need to do that, just redo the recovery.img
Sent using witchcraft via XDA Developers Premium App.
Related
I haven't found any solution with this. About 3 or 4 weeks ago my Evo went crazy so I rebooted and was missing many apps. I did a nand to another sense rom and every time I tried to install an app (either download or from sd card) it would reboot. The odd thing is, it only does it with sense roms. I can use CM 6 or 7 fine and install whatever I want. I was originally one Myn's rls5, I also tried the Fresh roms. I have non clue what's causing this, tried googling and all said clear the market cache or try an older market, which I've done both. Any help would be greatly appreciated.
tricky one. have you tried flashing a stock sense rom, and seeing how things work for you there?
Don't use a backup. Flash a sense ROM and install everything manually.
Sent from my PC36100 using XDA App
shogun26 said:
tricky one. have you tried flashing a stock sense rom, and seeing how things work for you there?
Click to expand...
Click to collapse
I haven't tried a stock rom yet, once I get things back up I'll find one and try it.
gqstatus0685 said:
Don't use a backup. Flash a sense ROM and install everything manually.
Click to expand...
Click to collapse
I can't install anything. period. as soon as I try to install any apk from my sd card or anything from the market that doesn't come installed in the rom, as soon as it "finishes" the installation part it will reboot, but not a full reboot, it will go out to the boot screen (but not all the way to the htc screen).
Since going from AOSP to Sense what was your procedure for flashing? Just want to make sure your starting with a clean slate.
- What steps to you take?
- Full wipe? Data, cache, sd-ext?
- SD format?
The more info you can give the better and maybe we can help you track it down.
Ive done the standard full wipe, data, cache, dalvik. I do that everytime between roms. Not sure what the ext does and in haven't formatted my sd card since then
Sent from my PC36100 using XDA App
Update - I flashed the stock rooted 3.70 and was able to install. This was after formatting my sd card. Then tried to flash Myn's rls5 again and had the same problems as before. Only difference is with the 3.70 I forgot the flash the radios, but still had a fine signal. I flashed the radio updates with Myn's. Any help/advice is greatly appreciated.
At this point all I can think of doing is unrooting your device and getting it completely back to stock, then try re-rooting and make a nandroid of your rooted, stock sense rom.
Maybe you can root through a different methods than what you did originally.
After that, try another sense rom, make sure the md5 checks out too.
Sent from my PC36100 using XDA App
What recovery are you using and what version? I thought there were known issues with ClockWork 3.x.x.x version of recovery not wiping cache correctly? If you are using ClockWork you might want to try switching to Amon_RA 2.2.1. to see what happens. There is also a zip floating around (which I have attached) that can be used to wipe everything, you may want to give that a shot then reinstall the ROM. I have not used this zip, so use it at your own risk as I cannot guarantee the results. I have read about others using this and it working just fine.
Hello! I need help on my G2 that doesnt want to flash any roms at all. When i go into Rom Manager and download a rom and go install it, it finish and it boots up but it just stays on the first HTC logo. I leave it there for more then ten minutes relizing the in messed up. So i have to go back into recovery(manualy) and wipe all data and cache and then i flash the Virtuous Rom(because i downloaded it to the sdcard) and it boots up. Also when i try to flash the mods to the rom and it also fail and i have to do the same procedure again and again everytime i try to flash a rom or backup. What should i do? Oh i also have S-OFF if that helps.
have you tried manually downloading and flashing another ROM through recovery?
Also, are you doing full wipes when trying to flash the new ROMs?
martonikaj said:
have you tried manually downloading and flashing another ROM through recovery?
Also, are you doing full wipes when trying to flash the new ROMs?
Click to expand...
Click to collapse
No i havent tried from a diferrent recovery but i will. Also i have benn doing full wipes and cache wipes.
Not a different recovery..the same way you flashed that rom is the same way you can flash others..if you downloaded rom through rom manager you can find it in that folder which is on your sd card called clockworkmod
Sent from my HTC Vision using XDA Premium App
Spastic909 said:
Not a different recovery..the same way you flashed that rom is the same way you can flash others..if you downloaded rom through rom manager you can find it in that folder which is on your sd card called clockworkmod
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I downloaded it from a youtube video and manually flashed them. But the problem is i already looked for a rom and i kinda dont want to trust people who post roms because my mytouch 3g got bricked becuase of the that. And i cant any roms i looked everywhere even on my best friend(google).
Sorry not even paying attention but thanks i will try that.
Chassen1236 said:
No i havent tried from a diferrent recovery but i will. Also i have benn doing full wipes and cache wipes.
Click to expand...
Click to collapse
Not a different recovery. Just make sure that your CWM recovery is the latest version. Download a ROM of your choice from the Dev section via your computer, transfer to your SDcard, and flash manually from your phone (not using ROM manager). Do a cache/dalvik cache/full data wipe. Then flash the ROM and reboot.
ROM manager can often have issues with bad downloads that lead to bad flashes. Flashing manually can be a way to troubleshoot and take a potential bad step out of the equation.
martonikaj said:
Not a different recovery. Just make sure that your CWM recovery is the latest version. Download a ROM of your choice from the Dev section via your computer, transfer to your SDcard, and flash manually from your phone (not using ROM manager). Do a cache/dalvik cache/full data wipe. Then flash the ROM and reboot.
ROM manager can often have issues with bad downloads that lead to bad flashes. Flashing manually can be a way to troubleshoot and take a potential bad step out of the equation.
Click to expand...
Click to collapse
You can download roms from dev section from your device as well.
As far as the op..what do you mean you downloaded from a youtube video and you don't trust people who past roms? If you don't trust people don't mess with it. The devs here aren't going to brick you phone..that's a mistake on your end or you not paying attention to what you were flashing
Sent from my HTC Vision using XDA Premium App
Spastic909 said:
You can download roms from dev section from your device as well.
Click to expand...
Click to collapse
I was trying to get him to download via his computer to see if the downloading via his phone was causing bad flashes.
Spastic909 said:
You can download roms from dev section from your device as well.
As far as the op..what do you mean you downloaded from a youtube video and you don't trust people who past roms? If you don't trust people don't mess with it. The devs here aren't going to brick you phone..that's a mistake on your end or you not paying attention to what you were flashing
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Correct me if I'm wrong but if i remember correctly it is extremely difficult to brick ones phone. The worst possible thing that could happen is if your phone some how died during a flash half way through. You can easily boot into bootloader, enter recovery and attempt to do it again.
With CWM you can mount the sd card in the mounts and storage settings so if you forgot or somehow deleted the Rom Zip from your card you can easily and safely access your card using CWM
i'm having the same issue
i have the phone rooted, s-off, and hboot installed
i'll boot into rom manager, wipe the data/cache, install the rom i want, reboot device... i get the white htc screen for about 5 seconds and then the phone restarts.
when it restarts, i get the white htc screen and then it boots into rom manager
what could be causing this? i had my previous g2 rooted and never had these issues when i was flashing roms
I am currently running andybonestock ROM as my "stock" ROM. I've wanted to try out the newer Sense ROMs but I keep running into a problem. Every ROM no matter what will eventually (and it usually happens after an hour) start endlessly rebooting. Let me clarify, it will reboot, load initially and then start rebooting all over. Now let's specify what I do every time I try to flash one, and maybe I'm doing something wrong.
My first step is always to backup in recovery. The next thing I do is run the super wipe script, followed by wiping cache, dalvik, and then running super wipe again. Then I choose the update file and update. I reboot my system and let it fully load. I run and complete the setup where it asks you for email and wifi etc. Finally I install and run Titanium. Now maybe this is my problem but I've read many times this is how to do it but correct me if I'm wrong. I selected batch restore and let it restore missing apps with data.
I'd really like to run a ROm I liked but can't deal with the rebooting. Any help would be greatly appreciated. And I've tried searching to no avail.
Thanks
Sent from my Droid Inc2 using Tapatalk
Try to restore apps, but not their data. You're going from sense to sense rom, so it seems like that shouldn't be an issue, but I think you should give it a shot.
but then what's the point of Titanium? if I'm losing the data, it's no different then restoring it via Google
Its either the data or the super wipe scipt seems they cause more problems than they help.
What recovery are you using? I've been running ext4 and the format all except SD and it never gave me any problems. What's with everyone wanting super wipes when you should be able to do everything in whatever recovery your using?
I'm using clockwork and I figured superwipe is more efficient
Maybe idk all that technical stuff. Try 4ext recovery its a lot better than cwm. If you don't wanna mess with a new recovery then just try using the wipes in cwm
Linch89 said:
Maybe idk all that technical stuff. Try 4ext recovery its a lot better than cwm. If you don't wanna mess with a new recovery then just try using the wipes in cwm
Click to expand...
Click to collapse
I appreciate the help but I doubt it's that but ill try it. Anything else
Sent from my Droid Inc2 using Tapatalk
what are you restoring with titanium backup? restoring app data for market apps is fine, dont restore system data though
nitsuj17 said:
what are you restoring with titanium backup? restoring app data for market apps is fine, dont restore system data though
Click to expand...
Click to collapse
Yup, I have made that mistake myself.
I've flashed many different sense roms and AOSP roms. I recommend getting 4ext recovery because it has a format partition option that's really easy to do. I format all partitons (except sdcard) and then i wipe data/factory reset. I've never had any issues with flashing roms sense or AOSP. Titanium Backup I only restore data for games, but going from AOSP you must just restore apps.
hakoreh said:
Every ROM no matter what will eventually (and it usually happens after an hour) start endlessly rebooting. Let me clarify, it will reboot, load initially and then start rebooting all over.
Click to expand...
Click to collapse
I have the exact same problem (only with Sense 3.5 ROMs, though), and it happens even when not restoring apps/data.
It's kind of sad, as I was enjoying trying out different ROMs, but no amount of wiping with different recoveries or superwipe have helped.
I half wonder if many of the roms are OCed, and my phone can't handle that, but I've tried flashing different kernels right after the rom, and it still happens.
I must say i don't re-flash to AOSP, but i restore my nandroid backup. However, I do format my partitons and wipe data/reset before restoring. I can try flashing MIUI 1.12.9 and then flashing sense 3.5 rom again. I'll be able to do it tomorrow. I'll let you know.
I guess I'll just try a Sense 3.0 rom
Sent from my ADR6350 using Tapatalk
hakoreh said:
I guess I'll just try a Sense 3.0 rom
Sent from my ADR6350 using Tapatalk
Click to expand...
Click to collapse
so I tried a Sense 3.0 ROM and even a Sense 2.1 ROM and still no dice. While the ROM did last a whole day without restarting, it did not hold and went into its usual boot loop again.
I'm really annoyed but want to try something new. I have 4EXT recovery now.
Does anyone know anything else I can try???
TY
OK I've had it. I even tried it without restoring anything from scratch and still eventually get restart errors
Sent from my Droid Inc2 (ICS wanted) with Tapatalk
Hello all just bought a new Samsung Galaxy SII from craigslist already rooted with 4.0.3 Jedi Mind Trick. After reading for what seems 4-5 hours i have been trying to put together how to properly without bricking switching it to 10.0.0 Stable as i use to use Cyanogenmod 2-3 years ago on my devices. Seem alot of things have changed and there is a cluster**** of stuff out there now. If you could direct me to a how to or show me how to do it i would greatly appreciate it!
Thanks all!
Assuming you have nothing personal to back up that you can't just download from google play or your google account again: download cyanogen 10 and it's gapps. reboot into recovery mode. factory reset, wipe data, wipe system, wipe cache, wipe dalvik. pick the install zip from sd card or so option, browse to cyanogen, then install gapps the same way. wipe dalvik again and reboot.
I was thinking of doing this myself JMT to CM10. I didn't think there was anything special to do same as flashing from any other ROM to CM10. If there is a special requirement I would think they'd post in in with the ROM post information.
Alawishis said:
I was thinking of doing this myself JMT to CM10. I didn't think there was anything special to do same as flashing from any other ROM to CM10. If there is a special requirement I would think they'd post in in with the ROM post information.
Click to expand...
Click to collapse
so I attempted to install it and got stuck on the boot logo for 20 minutes or so. So I bricked it lol... Anyway I just flashed it with Odin to 2.3.5 but the link to download file for root capabilities is broken. What can i do? Do i have to go to ics first before i reattempt to go to 10.0.0?
melvinator said:
so I attempted to install it and got stuck on the boot logo for 20 minutes or so. So I bricked it lol... Anyway I just flashed it with Odin to 2.3.5 but the link to download file for root capabilities is broken. What can i do? Do i have to go to ics first before i reattempt to go to 10.0.0?
Click to expand...
Click to collapse
honestly - i backed up everything to my external and then formatted the internal when i went from TW to AOSP for the last time. well worth it. nice folder clean up and then you can just manually take all the stuff you want back.
and you should just be able to odin on cwm or twrp - then flash the rom of your choice.
new ion? said:
honestly - i backed up everything to my external and then formatted the internal when i went from TW to AOSP for the last time. well worth it. nice folder clean up and then you can just manually take all the stuff you want back.
and you should just be able to odin on cwm or twrp - then flash the rom of your choice.
Click to expand...
Click to collapse
trying to look up how to do that now .... Searching the forum now... Might you be able to tell me real quick how? I already Downloaded the 5.2 file they suggest to use but can't find a working toturial that is just for flashing the cwm.
melvinator said:
so I attempted to install it and got stuck on the boot logo for 20 minutes or so. So I bricked it lol... Anyway I just flashed it with Odin to 2.3.5 but the link to download file for root capabilities is broken. What can i do? Do i have to go to ics first before i reattempt to go to 10.0.0?
Click to expand...
Click to collapse
If you get stuck at the boot logo, it's called a soft brick. You don't have to use ODIN or go back to ICS. Just make sure the ROM zip you downloaded isn't corrupt (check the size/m5d if possible), wipe everything, and reboot into recovery to try installing again.
arcsine said:
If you get stuck at the boot logo, it's called a soft brick. You don't have to use ODIN or go back to ICS. Just make sure the ROM zip you downloaded isn't corrupt (check the size/m5d if possible), wipe everything, and reboot into recovery to try installing again.
Click to expand...
Click to collapse
I already used Odin to go back to 2.3.5
Btw I appreciate the help
My woman's is waiting that I fail to say I told you so -_-
melvinator said:
I already used Odin to go back to 2.3.5
Btw I appreciate the help
My woman's is waiting that I fail to say I told you so -_-
Click to expand...
Click to collapse
You won't fail. Follow the guidelines step by step. Print it out, make notes. Anything. Read. The step by step guide works... that'll get you with cwm. Then, you can flash the zip you will put on your phone... either a SU zip or just a rooted ROM. Follow flashing instructions.
Just realized - you'll be way better off if, once you have cwm on, just format the internal ONCE YOU HAVE A ROM ON AN EXTERNAL SD CARD. then flash CM10. THEN you'll have a fresh AOSP install.
Sent from my SAMSUNG-SGH-T989 using xda premium
new ion? said:
You won't fail. Follow the guidelines step by step. Print it out, make notes. Anything. Read. The step by step guide works... that'll get you with cwm. Then, you can flash the zip you will put on your phone... either a SU zip or just a rooted ROM. Follow flashing instructions.
Just realized - you'll be way better off if, once you have cwm on, just format the internal ONCE YOU HAVE A ROM ON AN EXTERNAL SD CARD. then flash CM10. THEN you'll have a fresh AOSP install.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
how long does the boot logo stay on for?
Had 2.3.5 - rooted via odin and have recovery 5.2.6 - did everything in proper order and wiping properly.
what am i skipping here? Still spinning taunting me, wish there was a way it would tell me if i did something wrong.
melvinator said:
how long does the boot logo stay on for?
Had 2.3.5 - rooted via odin and have recovery 5.2.6 - did everything in proper order and wiping properly.
what am i skipping here? Still spinning taunting me, wish there was a way it would tell me if i did something wrong.
Click to expand...
Click to collapse
Go back, format system, and then reinstall.
Sent from my SAMSUNG-SGH-T989 using xda premium
Update your recovery to twrp or cwm 6+ and don't use dark side scripts
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Please excuse my harshness but this is not as hard as many make it seem. I would say if it takes you more than a couple attempts maybe it is just not for you. I only say this because I would hate to see you mess up your phone. Now if you think a bootloop is a brick then we need to do things at a slower pace with you.
If you already have your phone rooted then
1.download goomanager from the playstore and then
2.open it up and allow it to grant permission from CM
3.hit menu button while goo manager is open
4.click on install OpenRecoveryScript
5.let it do its thing
6.reboot into your new TWRP recovery
7.Wipe/Data Factory Reset
8.Flash Rom
9.Flash Gapps
10.Reboot
You can throw in a backup of files somewhere in there if you like.... Your choice
melvinator said:
how long does the boot logo stay on for?
Had 2.3.5 - rooted via odin and have recovery 5.2.6 - did everything in proper order and wiping properly.
what am i skipping here? Still spinning taunting me, wish there was a way it would tell me if i did something wrong.
Click to expand...
Click to collapse
I had a bootloop when using CWM v6.0.1.5. So a friend of mine told me he had success with CWM v6.0.1.5 Touch. So I switched to the touch recovery and... SUCCESS.
Here's the link to CWM touch and non-touch:
http://forum.xda-developers.com/showthread.php?t=1893464
A boot loop could mean a bad download or bad flash but it is most definitely NOT a bricked device. All you needed to do was get a fresh download and move it to your SD card by mounting it in recovery. Then, wipe EVERYTHING but the SD. EVERYTHING. Then flash the ROM, Gapps and whatever radio. I go from CM to AOKP to other random TW roms all the time and never have issues.
The 2 best recoveries are twrp or my favorite because I'm used to it is cwm 6.0.1.5. http://forum.xda-developers.com/showthread.php?t=1844637
Also if your phone boot loops don't freak out' just either reboot to see if that works out first and if not reboot into recovery. Also with these new recoveries do not use dark side scripts.
Factory reset
Format system
Format cache
Format data
Flash ROM
Flash gapps
Reboot and enjoy
Sent from my SAMSUNG-SGH-T989 using xda premium
This did it!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Sorry for the necro on the thread, but I didn't want it to be stated I didn't look around some either.
I am going from JMT to CM and want to make sure it's as seamless as possible. I use CWM and usually usually use darkside complete wipes, but I read in a previous post not to use darkside. Is there a reason for this? I can't see why this wouldn't work as it's just a wipe.
Also I use Titanium Backup. Is it possible to backup my apps and data and restore them since its not TW any longer? I want to be able to restore as much of my data as possible and make sure I don't lose it.
P.S. - If thread necroing is not appreciated, I apologize.
I tried flashing two different roms (synergy and chemistry) on my sprint galaxy s3. It turns on but then wont go past the "galaxy s III" logo. I just restored my backup and all is well but I really want to get multi window on this thing so I could really use some help as to what is not letting me boot up all the way. The last thing i messed around with rooting was my DroidX and with that it really mattered a lot which version of android you were flashing from. I have 4.1.2 the most recent update. Is that why these roms are not working? Any help would be much appreciated I am very excited to get a killer rom on this bad boy.
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
CNexus said:
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
Click to expand...
Click to collapse
I boot into recovery after i put the rom on to my sd card. Then wipe the factory data, cache partition, and delvik cache. I do those steps twice, then install the rom. The install seems to go fine, it always says successful at the end, it just wont go past that screen. Does it mater which version of clockworkmod I use?
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
CNexus said:
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
Click to expand...
Click to collapse
Thank you so much for your quick response. As far as I can tell, I am wiping everything I should be. I use clockwork recovery mod version: and the choices it gives you are: Wipe data/factory reset, wipe cache partition, and wipe dalvik cache. From all the instructional threads I've read, those are the only things you need to clear out before the install. My clockwork version is v5.5.0.4 which i think might be really old. Could that be my issue? Does it matter how I rooted it? I just tryed to put jellybomb v14 on it and it didn't even give me the galaxy s III logo. Luckily it booted back into recovery though. I really don't want to hard brick this thing.
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
A-Shin said:
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
Click to expand...
Click to collapse
clockworkmod v5.5.0.4
cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
Make the switch to TWRP v2.3.1.0 (newer ones I've heard have problems) but you will be thanking me later. It's way easier and much better than CWM... just an FYI for ya!
cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
I suggest trying a flash with TWRP. If you are unsure how to install TWRP, just download the Goomanager app, then choose install Open Recovery Script. But, before you install or change anything, look around a bit on how to install it. Make sure you follow directions step by step. After you have installed TWRP, try flashing again. Good luck!
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
cchrisrollins said:
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
Click to expand...
Click to collapse
Samsung bootloaders come unlocked by default, so yes
Easiest way to switch is to download Goo manager from the Play Store and have it install TWRP for you
Generally speaking, CWM is great on most devices, but for the S3 it's TWRP that's the best and easiest to use
And when flashing new roms, make sure to always format system, it prevents corrupted files from showing up because you would be installing the new system right on top of the old one if you don't
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you made a nandroid backup in TWRP (I'd recommend to put it on the external memory, but that's just me), you should be good to try any ROM you want (only Sprint ROMS). Just follow CNexus's post (linked for posterity). Wipe system as well as factory reset, cache, and dalvik, prior to installing the ROM.
cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you've already rooted, re-rooting isn't going to fix anything, so no need to go there.
As previously explained and detailed, do a full system wipe, and you'll be good to go.
Thank you guys so much for your very quick responses, thank you for bearing with my noobishness too haha. I am going to tryn reflash jellybomb tonight, I'll post on this thread how it goes (hopefully good).
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
cchrisrollins said:
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
Click to expand...
Click to collapse
It took me like 4-5 months to personally figure out that the problem was the kernel. You need to flash a kernel right after you flash the ROM. Either the stock kernels or better kernels like Anthrax will do. I know that for jellybomb, there's a kernel included in the Rom but for some reason,it got stuck on the gs 3 logo if I didn't flash another kernel.
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
cchrisrollins said:
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
No prob, just hit dat thanks button do you know where to get the kernels?
Zin0 said:
No prob, just hit dat thanks button do you know where to get the kernels?
Click to expand...
Click to collapse
I tryed the KT47 AOSP Jellbean kernel after flashing jelly bomb and it did the same thing it did before, black screen after flashing the samsung logo
Now I did go into fix permissions and it did say failed, is that abnormal?
This is my exact procces:
1. boot into TWRP
2. factory reset
3. system wipe
4. cache wipe
5. Dalvik wipe
6. Install from external SD: jellybomb v14
7. Wipe cache/Dalvik
8. Install Kt47 kernel
9. Wipe cache/Dalvik
Anything wrong there?