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.
Related
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.
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.
I've been wanting to upgrade my Tmobile S3 sgh-t999 to any of the 4.2 ROM that I could find in XDA, but when I tried to flash it from recovery, it always come back with "Installation aborted".
I tried upgrading to LiquidSmooth ROM, PAC-man ROM, CM10.1 and so on. still same.
I did place the zip files on my ext SD card and I'm able to see them when in recovery mode. I do wipe data, cache, dalvik and so on on each attempt, but still same..
If I did try with any of the new ROMs that required Google Apps to be flashed, if I would try flashing the Google app zip files first, that went successfully, but not the other zip file.
I'm a newbee, so I know I might be doing something wrong, although I have done upgrades before and was successful (but on Sprint phones)
My phone right now has 4.1.1 BUILD # JRO03L T999UVDLJA. Would it help if I go to STOCK rom for the upgrade? and which stock should I go down to if necessary?
Any suggestions?
I would check the zip file is good file first. check with MD5 checker to find out Maybe bad/incomplete download?
Or did you try reflashing recovery?
If you can flash gapps, I'm assuming you just need to verify that zip you downloaded.. Again I Can't see it so just an assumption..
Or start over by flashing stock and reroot it?
Sent from my SGH-T999 using xda premium
Your rom may be corrupted due to a bad download or your recovery may be out of date so I recommend redownloading the ROM, making sure it does complete and intended for your specific device, and if possible check for an MD5 sum on the ROM. Also, if on TWRP recovery (recommended) you may wanna download Goomanager from the Play Store and check to see if your recovery needs updating by tapping the menu key and selecting "Install openscript recovery". See if that helps bud.
Sent from my Galaxy Nexus using xda premium
Your recovery could be out of date, check if update is available
Sent from my SGH-T999 using xda premium
Successful install finally
I really have to thank you and all the others for their quick responses.
I did try different thinks after seeing the various responses:
..downloading MD5 checkers on both PC and phone, updating the recovery software and others..
But what I liked the most was.. I went to the goo.im site, selected the CM10.1 ROM, it expands and shows not only the MD5 # so I can verify it, but had a barcode, so I downloaded it directly to my phone and when done, i used the hash checker on the phone and the MD5 that was showing on the website matched the hash checker, so I went ahead and started the process and it did install successfully.
Noticed that Google play was not there so I also flashed the GPlay app.
It seems nice, even though I might back it up and then try another ROM to see which one I like the best.
Any suggestions on which is the most stable and improves both battery and other performances, while also giving you some cool tools or software?
Anthony
alomenzo said:
I've been wanting to upgrade my Tmobile S3 sgh-t999 to any of the 4.2 ROM that I could find in XDA, but when I tried to flash it from recovery, it always come back with "Installation aborted".
I tried upgrading to LiquidSmooth ROM, PAC-man ROM, CM10.1 and so on. still same.
I did place the zip files on my ext SD card and I'm able to see them when in recovery mode. I do wipe data, cache, dalvik and so on on each attempt, but still same..
If I did try with any of the new ROMs that required Google Apps to be flashed, if I would try flashing the Google app zip files first, that went successfully, but not the other zip file.
I'm a newbee, so I know I might be doing something wrong, although I have done upgrades before and was successful (but on Sprint phones)
My phone right now has 4.1.1 BUILD # JRO03L T999UVDLJA. Would it help if I go to STOCK rom for the upgrade? and which stock should I go down to if necessary?
Any suggestions?
Click to expand...
Click to collapse
myowin said:
I would check the zip file is good file first. check with MD5 checker to find out Maybe bad/incomplete download?
Or did you try reflashing recovery?
If you can flash gapps, I'm assuming you just need to verify that zip you downloaded.. Again I Can't see it so just an assumption..
Or start over by flashing stock and reroot it?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
If you want stability with lots of customization/features and good battery life I HIGHLY recommend trying out the ROOTBOX ROM, new updated version 3.8 that you can find in the op here.
http://forum.xda-developers.com/showthread.php?t=2117372
The downloads section will take you to the Rootbox site with a list of devices. Find your model and click on ”Official Releases” and it will take you straight to goo.im. If you happen to have battery issues with the default kernel you can always flash another one.
Sent from my Galaxy Nexus using xda premium
I really hate to start a new thread but I really can't find a reason/solution to this issue. It's just as the title says. I tried flashing the MIUI ROM just as any ROM and got a failed error. Then went to do my nandroid restore and it just hangs on the splash screen (boot screen). Anyway I thought there could be a bad download so I took out the SD and redownloaded synergy on my laptop, then put it back in the phone and nothing but the nandroid should let me restore. I even tried moving the files to the internal SD and nothing. The only thing I can think of is to Odin back to stock? Is it the same method as rooting? I'm sure I can find that out, but I'm just confused why it seems TWRP doesn't want to work. Thanks for any help, it's 4 a.m. here and I'm dog tired.
Are you on the latest TWRP?
If all else fails you could go back to stock and root again.
DarkManX4lf said:
Are you on the latest TWRP?
If all else fails you could go back to stock and root again.
Click to expand...
Click to collapse
I think so. Yeah, just didn't want to go throught it all, and didn't know why.
jtadak said:
I think so. Yeah, just didn't want to go throught it all, and didn't know why.
Click to expand...
Click to collapse
Can I just reflash recovery from the state I'm in, or do I still need to unroot? I've moved some of my files to the ext SD within recovery but some things won't move and I really don't want to wipe it.
jd14771 said:
Try wiping everything 3X, then go to the reboot menu, and reboot system, wipe both the cache and dalvik cache and try to restore.
Click to expand...
Click to collapse
Do you mean reboot recovery? I can't reboot system. Sorry, not trying to split hairs, just trying to be specific.
Odin back to stock seems like the best option.
Sent from a galaxy note 2 far far away...
are you able to flash a different rom, say a stock rom? It's possible you got a corrupted TWRP download.
Since they just released another update 2.4.3, you might want to try and download the zip file, wipe cashe and davick (may want to do it three times). Reboot back into TWRP 2.4.3 and see if it gives you some better luck.
I've had Nandroid backup that didn't work for whatever reason. I didn't test it prior to needing it, and got burned. It just wouldn't show up in the restore menu.
On a side note, what error did you get when you tried flashing MIUI?
Try rebooting recovery when you are in recovery already once before flashing/restoring anything anything.
mexiking713 said:
Odin back to stock seems like the best option.
Sent from a galaxy note 2 far far away...
Click to expand...
Click to collapse
Yes, that's what I did. I'm just bummed I had to wipe storage. Oh well, it's inevedible... I dig that sig though, with phone line up.
lovekeiiy said:
are you able to flash a different rom, say a stock rom? It's possible you got a corrupted TWRP download.
Since they just released another update 2.4.3, you might want to try and download the zip file, wipe cashe and davick (may want to do it three times). Reboot back into TWRP 2.4.3 and see if it gives you some better luck.
I've had Nandroid backup that didn't work for whatever reason. I didn't test it prior to needing it, and got burned. It just wouldn't show up in the restore menu.
On a side note, what error did you get when you tried flashing MIUI?
Click to expand...
Click to collapse
I tried multiple ROMs, but not a stock one. Hmm, I was on 2.3.2.3. I did'nt get a special error, just said a red message saying failed.
Evo_Shift said:
Try rebooting recovery when you are in recovery already once before flashing/restoring anything anything.
Click to expand...
Click to collapse
Tried that. Did'nt work.
jd14771 said:
no, i meant reboot system, the recovery will warm you that there is no os installed but go fourth with it, it will turn off and reboot back to recovery. at that point in time, wipe cashe/dalvik cache and try to install.
Click to expand...
Click to collapse
Ok, I was'nt sure. I just went back to stock. I just wanted to know what exactly was going on and why.
The only thing different on my phone is I got a 32 gig SD card. I transfed some of my files a couple days before doing anything of this. That's the only thing I can think of. Even after root/unroot it STILL won't do my nandroid restore. I had so much time and work into the apps I set up, games, ect. Really freakin sucks. I even went into the the TWRP backup folder and made sure the backup files were there before doing anything. I never even got to flash many ROMs, I kinda just stayed on Jellybomb.
I had the uTorrent app installed and I noticed that it changed a lot of files with the "u" in front that the uTorrent app has. Anyone know why that is?
Sent from my SPH-L900 using xda app-developers app
This is what it did to a lot of my files. But not the ones I tried to flash.
Sent from my SPH-L900 using xda app-developers app
Hi, hope my exact issue wasn't discussed after page 10 of the help & troubleshoot forum, anyway my rooted, unlocked cwm recovery stock 4.2 yakju (if I remember well) Samsung GNEX started to behave strangely slower then usual less then a week ago, then a couple of days later I woke up after night battery recharge to the boot up animation which never gave way to the operating system starting up.
After the first moment of despair I tried reading something here and with the use of adb I was able to first see the device and, after backing up via recovery, to pull the files from the phone (backup included). Problem is the 0 folder is very light for all the data and apps that I had, and inside the DCIM folder there's nothing, no trace of the 1k+ picture I shot in the past couple years, only an igc file which should have been in another folder. But strangely enough the backup weights almost 6GB which is consistent with what was inside prior to the crash.
Before attempting the backup I fiddled with recovery and tried to wipe cache, dalvik and fixing permissions, with no apparent results.
So now I'm undecided whether to take the phone to a samsung job centre which will surely wipe all data and possibly find out I have a corrupt memory or partition table, which renders many files and folders unavailable to be adb pulled or to wipe data/restore factory by myself hopying, fingers crossed, that the backup actually saved all my files and that could be restored without hassle. I actually had hoped that, like for the desktop environment, there was the possibility to awake my phone with a linux live or whatever to check if all files were present and downloadable before actually restoring the phone.
Thanks for your interest and help.
https://drive.google.com/file/d/0B8Pbk0TslYN6cm1wWWZydVM2V0k/edit?usp=sharing
Have you tried dirty flashing your rom?
Sent from my Galaxy Nexus using XDA Free mobile app
This is probably what I was thinking to do in the last sentence, I just have no idea how this could be done. Are there any videos explaining a dirty flash for gnex out there? Thanks for your help
Sent from my ASUS Transformer Pad TF300T using XDA Free mobile app
berniefranz said:
This is probably what I was thinking to do in the last sentence, I just have no idea how this could be done. Are there any videos explaining a dirty flash for gnex out there? Thanks for your help
Sent from my ASUS Transformer Pad TF300T using XDA Free mobile app
Click to expand...
Click to collapse
Its really easy. Just wipe cache and dalvik cache and then flash your rom (the same rom that is on the phone) again. Reboot.
Sent from my Galaxy Nexus using XDA Free mobile app
As far as I remember there is no identifiable rom files inside my GNEX memory, or wait, it seems I do already have a 6c7ff815e7762f651ad6f8c74e5cb281093f1e0b.signed-yakju-JWR66V-from-JDQ39.6c7ff815 zip in my download folder. So I need to clean cache and dalvik then install from zip. Do you know if this system wipes everything and I need to restore everything applying my hopefully working backup, or if it keeps all the files?
I'll try it tomorrow with fingers crossed.
Thanks again
mrgnex said:
Its really easy. Just wipe cache and dalvik cache and then flash your rom (the same rom that is on the phone) again. Reboot.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
berniefranz said:
As far as I remember there is no identifiable rom files inside my GNEX memory, or wait, it seems I do already have a 6c7ff815e7762f651ad6f8c74e5cb281093f1e0b.signed-yakju-JWR66V-from-JDQ39.6c7ff815 zip in my download folder. So I need to clean cache and dalvik then install from zip. Do you know if this system wipes everything and I need to restore everything applying my hopefully working backup, or if it keeps all the files?
I'll try it tomorrow with fingers crossed.
Thanks again
Click to expand...
Click to collapse
Dirty flashing wont wipe any data. Only cache (which is only helpful with some speed). Cache will rebuild. If thats your rom. Dirty flash it. If it isnt. Adb push the right rom.
Sent from my Galaxy Nexus using XDA Free mobile app
Then I don't think the mentioned file is the my rom but a rom update I wanted to push myself but never did. Now, I'm definitely sure it was already JB, but which flavour? 4.2 JOP40C, 4.2.1 JOP40D or 4.2.2 JDQ39? I guess it should have been the last one, if I intended to update from JDQ to JWR (according to the file name), and I'm quite sure it was Jakju but just can't remember for sure. Is there a way via recovery or adb to check which was my rom? Or should I just close my eyes and download and flash JDQ39?
Again, thanks
mrgnex said:
Dirty flashing wont wipe any data. Only cache (which is only helpful with some speed). Cache will rebuild. If thats your rom. Dirty flash it. If it isnt. Adb push the right rom.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
berniefranz said:
Then I don't think the mentioned file is the my rom but a rom update I wanted to push myself but never did. Now, I'm definitely sure it was already JB, but which flavour? 4.2 JOP40C, 4.2.1 JOP40D or 4.2.2 JDQ39? I guess it should have been the last one, if I intended to update from JDQ to JWR (according to the file name), and I'm quite sure it was Jakju but just can't remember for sure. Is there a way via recovery or adb to check which was my rom? Or should I just close my eyes and download and flash JDQ39?
Again, thanks
Click to expand...
Click to collapse
I know that TWRP default names a nandroid as the ROM build name/number and date. Don't know what cwm does for that as its been ages since I used it. You could install twrp and see what that tells you as the name of backup maybe to try and grab current ROM info.
Or using the file manager in recovery(twrp has one dunno about cwm) and see if you can look at the build.prop in /system which will have all relevant ROM information. If you can use adb in recovery try pulling /system/build.prop and looking at it. Right near top will be ROM build and info
Thanks, CWM doesn't have a file manager, but adb did actually pull the build prop id=JOP40D, so I'll go back to download the correct ROM and try to flash it..
ashclepdia said:
I know that TWRP default names a nandroid as the ROM build name/number and date. Don't know what cwm does for that as its been ages since I used it. You could install twrp and see what that tells you as the name of backup maybe to try and grab current ROM info.
Or using the file manager in recovery(twrp has one dunno about cwm) and see if you can look at the build.prop in /system which will have all relevant ROM information. If you can use adb in recovery try pulling /system/build.prop and looking at it. Right near top will be ROM build and info
Click to expand...
Click to collapse
small update, I managed to download the correct rom and I tried to adb push the .tar to the device (twice and attempting a third to /sdcard/ /sdcard/clockworkmod/ and now /sdcard/0/Download/) but still haven't been able to spot the uploaded file to choose for dirty flash. adb shows the file as uploaded , but again no sign of it with CWM Recovery. should I try to install TWRP recovery? with the nexus toolkit there is a function to flash a rom, but it says it will wipe the device first, so it's really not the option I was looking for. Another strange behaviour of CWM Recovery, or maybe my phone, inside mounts and storage menu, mount sdcard seems to be not working as it never changes to unmount after you click it. I think my memory went berserk and that's the reason why the phone rebooted and never woke up again. Maybe I'll take to the nearest job center to ascertain the damage...
thanks for all your help
berniefranz said:
Thanks, CWM doesn't have a file manager, but adb did actually pull the build prop id=JOP40D, so I'll go back to download the correct ROM and try to flash it..
Click to expand...
Click to collapse
installed TWRP and was able to see to rom.tar uploaded via adb in the download folder, but wasn't able to use to flash as probably both recovery wants .zip and not .tar, so I'll now untar and zip the stock rom and upload it again...
small steps...
had a md5 check fail during flash, so still no good news. I was surfing a bit when noticed that developers.google.com doesn't have a factory image for 4.2.1 jop40d but only for 4.1.2 jzo54k. Does this mean I should flash 4.1.2 and then update, or try directly for the 4.2.1 which I can't find (a working one)?
went back to CWM but installation failed as well as TWRP, so I guess my last option is to take it to a samsung job center to check whether I have a corrupted memory or else... ANyway thanks everybody for your support..
berniefranz said:
had a md5 check fail during flash, so still no good news. I was surfing a bit when noticed that developers.google.com doesn't have a factory image for 4.2.1 jop40d but only for 4.1.2 jzo54k. Does this mean I should flash 4.1.2 and then update, or try directly for the 4.2.1 which I can't find (a working one)?
Click to expand...
Click to collapse
Had to take it to the job center where, it was downgraded to 4.0.4 (have still to check which flavour) fixed something and Wiped everything. When I side about he post mortem backup and the intention to try a restore from there I was give an are you kidding look, it could crash again... sigh.
Anyway thanks everyone that spent some time to try and explain a noob how to try to solve this issue.. Now I've got a new galaxy nexus, so after a little grievance I'll start reading on how to flash a nice rom...
berniefranz said:
went back to CWM but installation failed as well as TWRP, so I guess my last option is to take it to a samsung job center to check whether I have a corrupted memory or else... ANyway thanks everybody for your support..
Click to expand...
Click to collapse