Hi there, I'm new to the forum but have been rooting for about a year. Here is my problem...
I was running stock firmware on my SGS3 and went through the standard cm10 root/rom install process. I flashed CMW with Odin, booted to recovery, installed cm10, jb gapps, cleared cache and delvik cache and rebooted. All the above processes worked fine and once it boots into JB, nothing seems to work. My home button does nothing, the top status bar is blank, no wifi, no keyboard (the process just crashes when I attempt to type).
I know this isn't an issue with CM10 on the SGS3 as this works for most people but does anyone have any ideas on how to remedy this? This may be a unique issue as I can't seem to find anyone else experiencing this.
Also...
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Coming from stock you need to fully wipe.
Sent from my SAMSUNG-SGH-I747 using xda premium
Machoscrawn said:
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Click to expand...
Click to collapse
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
dynamiclynk said:
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. This is what I did...
(Main cwm menu) -wipe cache partition
(Advanced) -wipe dalvik cache
+++go back+++
-reboot system now
Is there something additional I should clear?
Kweli87 said:
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
Click to expand...
Click to collapse
Thanks for the reply,
How do i update to the latest clockworkMod? Do you happen to have a URL? I think I found the latest 6.something, but they all seem to be in .iso format.
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
i386W7 said:
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
Click to expand...
Click to collapse
Sorry I may have missed mentioning that. The first thing I did was the -factory restore/reset
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
goodtimes50 said:
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
Click to expand...
Click to collapse
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
BAM1789 said:
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
Click to expand...
Click to collapse
Ok thanks! I'm going to give that a shot and see how it goes.
Machoscrawn said:
Ok thanks! I'm going to give that a shot and see how it goes.
Click to expand...
Click to collapse
Ok so I tried flashing a stock rooted ICS ROM and now I'm stuck on the Samsung logo boot screen. Here is the method I tried, using Odin. http://forum.xda-developers.com/showthread.php?t=1739426
I used the "Bell Image (This works with Canadian Virgin Mobile SGH-I747M) - Old Image I747MVLALH1 (ICS 4.0.4)"
After flashing I booted into the stock recovery and cleared the cache partition then rebooted. Still stuck on the Samsung boot screen.
UPDATE: I just let it sit on the Samsung logo boot screen and it eventually loaded into ICS.
Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
goodtimes50 said:
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
Click to expand...
Click to collapse
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Machoscrawn said:
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Click to expand...
Click to collapse
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
wally3614 said:
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
Click to expand...
Click to collapse
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Machoscrawn said:
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Click to expand...
Click to collapse
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
wally3614 said:
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
Click to expand...
Click to collapse
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Machoscrawn said:
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Click to expand...
Click to collapse
If youre looking to completely start over. Just grab an unrooted stock .tar from one of the links somewhere around here, put your phone in download mode and let it flash. Clean slate.
Related
Does anyone have a link or provide instructions on how to install the 3.0 Kernel? I tried doing it but I got an error message saying that it cannot load volume or something? Thanks.
http://forum.xda-developers.com/showthread.php?t=1591850
All you should have to do is d/l the kernel and flash it with TWRP. Thats all I did and it worked perfectly. You cannot use CWM for the 3.0 kernel. What ROM are you currently on? Did you use CWM or TWRP to flash?
danmn i used CWM....
did i destroy my kindle?
I tried flashing the zip but I keep getting E:Cannot load volume /misc!
That's normal, it installed correctly
gclo85 said:
I tried flashing the zip but I keep getting E:Cannot load volume /misc!
Click to expand...
Click to collapse
That is normal, just reboot.
Whenever I reboot, I get the yellow fire splash screen to get into recovery. After that is done, my screen goes black. It looks like it's not even turned on. I have to hold the power button in for 15-20 seconds and then hold it in again for 5 seconds and then it goes back to the splash screen and does it all over again. I did do a backup of my rooted stock so I can get everything back. Do I have to do anything in particular before I install the kernel? What I've been doing is factory reset, wipe cache, and wipe dalvik. I also tried installing it on top of my stock without wiping anything but it does the same thing.
gclo85 said:
What I've been doing is factory reset, wipe cache, and wipe dalvik. I also tried installing it on top of my stock without wiping anything but it does the same thing.
Click to expand...
Click to collapse
That's your problem. You don't wipe to install a kernel. You're just wiping your system out.
[Edit:]. Make sure you check the Md5 before installing
Alright. I'll do a restore and try installing the kernel. Thanks for the info.
I did an Md5 file check before I flashed and it said Md5 file not found.
I originally downloaded the 4-22 zip which is the newest one from what I can see.
http://forum.xda-developers.com/showthread.php?t=1591850
Nevermind...I think I got it. I just flashed the kernel and then flashed gedeROM v1.15 and it's working. Thank you for your help.
Just be careful with the gederom. As of now, adb doesn't work well. So if you screw something up it'll be hard to get it fixed.
And the 4-28 (#8) kernel is the most recent.
Is there another stable ICS that you can recommend?
AOKP with the #8 kernel seems to be a favorite amongst many.
Hellfire, Reloaded, and Energy have huge followings but I haven't paid much attention to how stable they are with the new kernels. You should check their respective threads for more info.
I installed Energy and I like it better than the one I had. Thanks.
gclo85 said:
I installed Energy and I like it better than the one I had. Thanks.
Click to expand...
Click to collapse
Scratch that; I went back to gedeROM. Titanium Backup kept freezing and also seemed like it had calibration issues. I would tap on a picture in Google Images or home screens/apps drawer and it wouldn't do anything. I had to press hard or press in a specific area for anything to open.
Does one need to install the 3.0 v#8 independent of the ROMs i.e. Hellfire or AOKP etc?
So, been a couple weeks been trying to flash CM10 ROMs, Paranoid, AOKP and CYANO, Everytime i flash I wipe everything as instructed and when it reboots it just hangs on the cyanogem boot image with the wheel spinning and does nothing. Not even a boot loop?! I let it sit for up to a half hour before and still nothing. But I can go and restore my old rom (not CM!) and works great..and if I flash a a new TW rom it flashes correctly.
Any ideas. I am on CWM when I flash. I also tried to flash TWRP and that would not take as well and had to go back to CWM.
Things I would check:
Verify MD5 tags of the roms your flashing when you download
Try wiping cache/dalvik/system and doing a factory reset after you have a successful flash
Question I have for you...
Have you tried unrooting and rooting again?
TWRP and CWM should both work, but have you ran the darkside scripts if using CWM? > http://forum.xda-developers.com/showthread.php?t=1477955
Lastly - I have heard people needing to reflash several times before it "takes" which it sounds like maybe you've tried & I realize these may be very basic things for you but you never know hopefully someone can help the more info you provide.
ldd_recoil said:
Things I would check:
Verify MD5 tags of the roms your flashing when you download
Try wiping cache/dalvik/system and doing a factory reset after you have a successful flash
Question I have for you...
Have you ever successfully loaded a custom rom on this particular phone?.... because you may have improperly rooted
TWRP and CWM should both work, but have you ran the darkside scripts if using CWM? > http://forum.xda-developers.com/showthread.php?t=1477955
Click to expand...
Click to collapse
I am on a custom rom now and everything is fine..but when I try to flash anything other than a Touchwhiz rom it seems to fail. I had paranoid running for a little while but I could not access my external sd so went back to my Jedi Mind Trick rom and everything was fine...so I decided to try a different paranoid thinking the issue was with this specific rom and it would not boot..went back to JMT and then tried aosp cm10 rom thinking and it wouldn't boot.
i have tried everything you have suggested except for the Factory Reset after the flash. Never really check the MD5 though. Might give it a try later on when I get bored with this rom again.
Thanks,
T
Sorry, reread your post now that I have the right context... Try unrooting and rerooting if you continue to have new rom flash issues.
toreone said:
So, been a couple weeks been trying to flash CM10 ROMs, Paranoid, AOKP and CYANO, Everytime i flash I wipe everything as instructed and when it reboots it just hangs on the cyanogem boot image with the wheel spinning and does nothing. Not even a boot loop?! I let it sit for up to a half hour before and still nothing. But I can go and restore my old rom (not CM!) and works great..and if I flash a a new TW rom it flashes correctly.
Any ideas. I am on CWM when I flash. I also tried to flash TWRP and that would not take as well and had to go back to CWM.
Click to expand...
Click to collapse
Solution is Simple.... When it hang in the cyanogenmod boot image with the wheel spinning just switch off -> Go to recovery -> install the DarkSide Cache Wipe.Zip then see the magic.... :good:
srikanth.t989 said:
Solution is Simple.... When it hang in the cyanogenmod boot image with the wheel spinning just switch off -> Go to recovery -> install the DarkSide Cache Wipe.Zip then see the magic.... :good:
Click to expand...
Click to collapse
Thanks, i will give this a try next time i flash...and i'll report back. This happened with a few different roms...this should fix those too!? also, I am pretty sure I ran the Darkside before I did first boot...should I have waited?
EDIT::: THIS WORKED...IT WAS HUNG UP ON BOOT IMAGE..FOLLOWED INSTRUCTIONS ON TOP AND BINGO!!!! I SAW THE MAGIC
toreone said:
Thanks, i will give this a try next time i flash...and i'll report back. This happened with a few different roms...this should fix those too!? also, I am pretty sure I ran the Darkside before I did first boot...should I have waited?
Click to expand...
Click to collapse
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!
cluckkillerb said:
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!
Click to expand...
Click to collapse
I actually tried this yesterday and it went through the motions and when I restarted into recovery it was just like a blue background with the Team Win on it but never made it past that...so I had to flash back to CWM through Odin to get it to be able to flash again..
cluckkillerb said:
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!
Click to expand...
Click to collapse
After doing this try downloading quickboot to boot into twrp recovery, if that doesn't help you might need to flash back to stock/re-root and start from square one =/
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 searched and looked at other threads with people having the same problems, but none helped, and none of those threads had an OP with the Galaxy S3.
So here's the thing, I got rooted yesterday, and it was all good. Then today, I flashed the LiquidSmooth ROM and GApps with ROM Toolbox, and it went fine. Then I decided I wanted to try a different one, so I flashed to my backup, and that went fine. So I downloaded and put both the PACman ROM with GApps 4.1 from like 12/12, and RootBox with the newest 4.2 GApps onto my internal SD. However, I'm using ROM Toolbox, and when I added RootBox and the 4.2 GApps to the queue, in the right order, and told it to install them, and to wipe the devik cache (I think that's what it's called) and to delete all the data and stuff like you are supposed to, it booted into recovery, wiped the data, and then just stopped. So I had to restore to my backup, which the newest one vanished, so I had to use the day old one.
Next I booted into recovery, to manually add the files myself, however, they weren't there. The only thing that showed up was the old 4.1 12/12 GApps, and nothing else. I then tried to install PACman and the 4.1 GApps from ROM Toolbox, but it did the same thing, and I had to restore to my back up.
Can anyone maybe shed some light to why the ROM's aren't coming up?
When you looked for the ROMs in TWRP, which directory did you look in? Did you download the ROMs via ROM Toolbox?
Sent from my SGH-T999 using xda app-developers app
GhostIsBaked said:
When you looked for the ROMs in TWRP, which directory did you look in? Did you download the ROMs via ROM Toolbox?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I looked in the sdcard directory I'm pretty sure. And I just downloaded RootBox from ROM Toolbox, and tried to install it, but it did the same thing and didn't work.
My phone only had like, 35% battery when I did this, could that be a problem?
NorNichols said:
I looked in the sdcard directory I'm pretty sure. And I just downloaded RootBox from ROM Toolbox, and tried to install it, but it did the same thing and didn't work.
Click to expand...
Click to collapse
If you're going to manually flash it through recovery, Root box should be in directory /sdcard/romtoolbox/download/ or something similar since ROM toolbox creates its own folder
Also when you say it just stops, what do you see on your screen?
Sent from my SGH-T999 using xda app-developers app
Well, if I start it through ROM Toolbox, it reboots into recovery, and then says like, wiping data or something similar, and then it goes back to the TWRP home screen, and then if I boot back into the system it's just stock, and then I have to restore to my backup.
And if I flash it manually, wont' it not matter where it is, or isn't it supposed to be in the root of the sdcard? Like, I can see if I was doing it through ROM Toolbox, but when I do it manually, it shouldn't matter, right?
Okay, so I just tried again, and it the last thing it says is (this isn't word for word, closest I can remember) Something cash make4ext.something or something close to that. Then it just goes to the home screen of TWRP.
Okay, so this is what just happened, I went to install LiquidSmooth again, and it said, Unable to locate zip file '/sdcard/romtoolbox/downloads/blahblahblah(doesn't show full directory)
E: Error installing zip file
Checking for MD5 file
E:No MD5 file found
Error flashing zip
NorNichols said:
Well, if I start it through ROM Toolbox, it reboots into recovery, and then says like, wiping data or something similar, and then it goes back to the TWRP home screen, and then if I boot back into the system it's just stock, and then I have to restore to my backup.
And if I flash it manually, wont' it not matter where it is, or isn't it supposed to be in the root of the sdcard? Like, I can see if I was doing it through ROM Toolbox, but when I do it manually, it shouldn't matter, right?
Okay, so I just tried again, and it the last thing it says is (this isn't word for word, closest I can remember) Something cash make4ext.something or something close to that. Then it just goes to the home screen of TWRP.
Okay, so this is what just happened, I went to install LiquidSmooth again, and it said, Unable to locate zip file '/sdcard/romtoolbox/downloads/blahblahblah(doesn't show full directory)
E: Error installing zip file
Checking for MD5 file
E:No MD5 file found
Error flashing zip
Click to expand...
Click to collapse
What version of TWRP are you on?
Try flashing it through TWRP without using toolbox
Download liquid smooth
Download
Steps:
1.Boot into recovery
2.create backup if needed
3.wipe dalvik cache
4.wipe cache
5.wipe factory reset
6.wipe system
7.install- Select the ROM .zip and install
8.Install the 4.2 gapps (12-12)
9. Reboot system
Sent from my SGH-T999 using xda app-developers app
Well actually, I wanted to try the PACman ROM next, so could I just download that and do all the same things, but with that, and instead of the 4.2 GApps, use the 12/12 4.1 GApps?
Also, I'm using 2.3.3.1, and I see that there is a newer one. Can I just flash that one over this one using ROM Toolbox?
NorNichols said:
Well actually, I wanted to try the PACman ROM next, so could I just download that and do all the same things, but with that, and instead of the 4.2 GApps, use the 12/12 4.1 GApps?
Also, I'm using 2.3.3.1, and I see that there is a newer one. Can I just flash that one over this one using ROM Toolbox?
Click to expand...
Click to collapse
Yea but make sure it's specifically for this device (d2tmo/sgh-t999)
The 12-12-12 gapps are 4.2 which are the correct ones to use for PAC Man as well.
DO THIS FIRST
Easiest way to update it is to download GooManager from the playstore. Once, installed, press menu button and install the open recovery script. Latest is 2.4.1.
Sent from my SGH-T999 using xda app-developers app
rnedkle and
It's still not there, I dragged and dropped it into my phone on my computer, but I don't see it. GApps is there, but not the ROM.
I'll try GooManager now, just weird that ROM Toolbox was working earlier and so was TWRP, but now TWRP can't find the ROM and ROM Toolbox can't install things. I went from thinking, wow this isn't hard at all, to, why won't this work! I'll download GooManager in just a bit, my phone is restoring to a backup.
NorNichols said:
It's still not there, I dragged and dropped it into my phone on my computer, but I don't see it. GApps is there, but not the ROM.
I'll try GooManager now, just weird that ROM Toolbox was working earlier and so was TWRP, but now TWRP can't find the ROM and ROM Toolbox can't install things. I went from thinking, wow this isn't hard at all, to, why won't this work! I'll download GooManager in just a bit, my phone is restoring to a backup.
Click to expand...
Click to collapse
OK. I'm gonna catch some sleep for a bit. I'll check back in the morning. Hope everything goes alright man :thumbup:
Sent from my SGH-T999 using xda app-developers app
GhostIsBaked said:
OK. I'm gonna catch some sleep for a bit. I'll check back in the morning. Hope everything goes alright man :thumbup:
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Okay, I appreciate the help. Sleep well.
For anyone who see's this next, just tried GooManager, also didn't work, so I'm pretty much going to give up for the rest of tonight and see what any of you have to say tomorrow. This is a bummer, but oh well, it's just weird that it was working fine and now it won't. I'm going to bed.
You putting these on intsd or extsd? You can't see them through TWRP, the phones file browser, or the computer? Unmount/remount the extsd in Storage settings.
Don't flash through an app. Flash things manually through recovery. If you always use an app to flash for you, you don't learn how to fix problems when you run into them.
You can Odin TWRP from my signature (hopefully you have Mobile ODIN), or here's a zip: http://db.tt/0SzQ0aK7
I bet all of your ROMs are still on your phone. The latest JB creates partitions in your memory. These partitions are for multiple users. Your problem is amplified by having an old recovery. You can locate all of your stuff by going to your memory and going through the folders that start with emulated/0. The latest recovery will fix this issue and you'll be able to use ROM toolbox to flash.
GBP85 said:
I bet all of your ROMs are still on your phone. The latest JB creates partitions in your memory. These partitions are for multiple users. Your problem is amplified by having an old recovery. You can locate all of your stuff by going to your memory and going through the folders that start with emulated/0. The latest recovery will fix this issue and you'll be able to use ROM toolbox to flash.
Click to expand...
Click to collapse
How do I get into the memory to find emulated/0?
Edit: I flashed CWR, and it worked just fine...but then I decided I didn't like the PACman ROM, so now I'm back to restoring back to normal...I guess next I'll try Carbon or Rootbox.
Edit2: Aww dangit, guys I'm a failure. It's stuck on the Samsung logo after you pass the tmobile one, so now I am back into recovery and reset everything and formatted and stuff, and now I'm trying to restore from the backup again...I think if I fix it, my flashing ROM days are done for awhile.
Edit 3: Ended up using Odin to get a rooted stock build on there, then downloaded ROM Toolbox, flashed TWRP, put the backup back on my phone since I have a copy of it on my computer, restored, and now we are all good.
Hey there;
Firstly, thanks for your great efforts on the ports of your roms and consistent, useful forum help.
I appreciate that you probably get a load of these threads but I could really use some help with the installation of the ROM, as I've had a load of problems trying to install it.
I am attempting to install the MIUI rom (http://forum.xda-developers.com/showthread.php?t=1797515), and I am coming from the original software that comes with the device.
I have an unrooted One V, coming from the base OS and kernel. Currently, I can't get past the Jellybean Android screen (getting stuck on starting apps), and usually I can't even get past the MIUI screen at all. Here are the steps I've taken;
- I downloaded this kernel: boot-TK-USB-201302150054 from this thread: http://forum.xda-developers.com/show....php?t=1765687 and flashed it in fastboot, twice.
- Then launch into recovery, follow the instructions on your thread (format all apart from SD), and go ahead and install the .zip.
- Clear Delvik, clear Battery and Fix permissions, then proceed to reboot in an attempt to get in. At this point it hangs on MIUI screen for up to 5 minutes.
- I then try re-flashing the kernel in fastboot again. Still no help.
- I then try and reinstall the .zip from the SD card, and still no improvement.
I imagine I'm doing something very wrong, but I can't work out what it is and it's driving me crazy.
Can you help?!
Thanks in advance, Reasoner.
you are installing an older rom version which has no support..and is old
paarthdesai said:
you are installing an older rom version which has no support..and is old
Click to expand...
Click to collapse
Any chance you good point me in the right direction for an newer version?
Also, am I doing all the steps right?
paarthdesai said:
you are installing an older rom version which has no support..and is old
Click to expand...
Click to collapse
Okay, I have now attempted to install YOUR version of MIUI, and I'm still not having any luck.
I have;
- Flashed the boot.img using the one you suggest on your thread (twice)
- Booted into Recovery, cleared all caches excluding SD
- installed from .zip in CWM Recovery
- Cleared Delvik
On reboot I still get stuck on the MIUI screen.
Reasoner said:
Okay, I have now attempted to install YOUR version of MIUI, and I'm still not having any luck.
I have;
- Flashed the boot.img using the one you suggest on your thread (twice)
- Booted into Recovery, cleared all caches excluding SD
- installed from .zip in CWM Recovery
- Cleared Delvik
On reboot I still get stuck on the MIUI screen.
Click to expand...
Click to collapse
Ignore this, tried again and got through! Thanks a bunch!