I tried installing Carbon on my GS3, but the gapps wouldn't work properly, and upon booting would say Setup Wizard stopped and the gapps processes. So now I can't get the Google apps on my phone. At this point I decided just to recover my backup that I did through CWM, but when I try to restore it it says MD5 mismatch...what do I do? I need help.
Slothshin said:
I tried installing Carbon on my GS3, but the gapps wouldn't work properly, and upon booting would say Setup Wizard stopped and the gapps processes. So now I can't get the Google apps on my phone. At this point I decided just to recover my backup that I did through CWM, but when I try to restore it it says MD5 mismatch...what do I do? I need help.
Click to expand...
Click to collapse
Toggle signature verification off in CWM
No luck, it was already toggled off. Dammit...how can I just go back to the way my phone was pre-rooting?
Slothshin said:
No luck, it was already toggled off. Dammit...how can I just go back to the way my phone was pre-rooting?
Click to expand...
Click to collapse
Just get on Carbon like this:
Flash mrRobinson's rooted stock
Download Goo Manager from the Play Store to install TWRP
Flash Carbon and the gapps from the Carbon thread
Just finished getting it, but it won't get past the final Samsung loading screen, where it glows purple. It's stuck there, in a boot loop...
Slothshin said:
Just finished getting it, but it won't get past the final Samsung loading screen, where it glows purple. It's stuck there, in a boot loop...
Click to expand...
Click to collapse
Go into 3e recovery and factory reset and wipe cache
It worked. Holy crap. Thank you, I thought this was going to take even longer. So...how can I put a new rom on it, if I wanted to?
SophisticatedRetard said:
Just get on Carbon like this:
Flash mrRobinson's rooted stock
Download Goo Manager from the Play Store to install TWRP
Flash Carbon and the gapps from the Carbon thread
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^
Where exactly is TWRP?
Slothshin said:
Where exactly is TWRP?
Click to expand...
Click to collapse
There are two recoveries. CWM and TWRP
I suggest TWRP not because I like it better but because it's easier to load. Download Goo Manager, open it, hit Menu => Install Openrecoveryscript
So I should use Goomanager again, even though it messed up my phone last time? I think it was the gapps download that messed it up last time. Maybe the latest version isn't compatible with my device?
Slothshin said:
So I should use Goomanager again, even though it messed up my phone last time? I think it was the gapps download that messed it up last time. Maybe the latest version isn't compatible with my device?
Click to expand...
Click to collapse
Only use Goo manager to load TWRP
Get the ROM and gapps from the carbon thread, and follow the OP's instructions for flashing
What thread would that be?
Slothshin said:
What thread would that be?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2136846
I have no idea what to do. The gapps link is for 4.2.2, even though the download page said the gapps should be 4.2.1.
Slothshin said:
I have no idea what to do. The gapps link is for 4.2.2, even though the download page said the gapps should be 4.2.1.
Click to expand...
Click to collapse
They are special gapps because of the Dark UI toggle... Give me a moment, I'm downloading carbon, and finding the proper gapps.
---------- Post added at 11:30 PM ---------- Previous post was at 11:24 PM ----------
Ok, it looks as though the Dark UI toggle has been removed, so use 4.2.2 gapps
Why not go with SlimBean? Carbon is just a Slim rip-off....
Flashing:
Wipe Data \ Factory Reset
Wipe Cache
Wipe Dalvik Cache
format /system
Flash ROM
Flash gapps
Reboot
Profit
---------- Post added at 11:57 PM ---------- Previous post was at 11:30 PM ----------
PMed you
Related
First day I got the phone I rooted and installed clockwork mod. I downloaded and installed cm9 but now I can't flash any other roms. Every time I try and flash a new one it boots to log screen then stays on a blank black screen. Any help would be appreciated as i would like to try something else out. Also I followed the flashing instructions of each rom and even tried formatting system with no luck.
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
scott0 said:
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
Click to expand...
Click to collapse
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
lendmeyoureers said:
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
Click to expand...
Click to collapse
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
drumist said:
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
Click to expand...
Click to collapse
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
scott0 said:
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
Click to expand...
Click to collapse
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
lendmeyoureers said:
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
Click to expand...
Click to collapse
i didn't say your's was bricked, i said i bricked mine doing what you did.
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
i'm not sure what post 29 is, but i've done machz's unbricking 2x succesfully, it's the 1st post in his thread.
either way, i know how frustrating it can be, i hope you get it all sorted out.
lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
scott0 said:
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
Click to expand...
Click to collapse
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
this is good advices. but i never was able to sort out how to use terminal emulator, ugh. i kept trying to run commands from within the phone that were ....hekk can't recall exactly. it was frustrating.
but the best advice i think is the nandroid b/u of the original ROM. although nothing necc. wrong with doing a debrick, only takes <30 minutes, as long as the debricking Gods are all in a good mood at that particular moment.
If you get hono's GB rom, then flash HONO's GB kernel, you should be able to boot into GB no problem
drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
lendmeyoureers said:
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
Click to expand...
Click to collapse
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
drumist said:
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
Click to expand...
Click to collapse
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
hah, yeah, that command reminded me of what i was doing wrong, i was mistakenly trying to run shell commands from the emulator.
lendmeyoureers said:
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
Click to expand...
Click to collapse
Awesome. Now make a Nandroid backup BEFORE you install another ROM, so you have an easier way to revert to your current boot image. That way you can install CM9 again later if you want without worrying about going through this again if you want to install something else.
Ok I looked all over the place and I could find anything about this issue. I have the telus s2x t989d and I went on rom manager and downloaded cyanogenmod 9 for my phone( only one available). Then I went in to install it and when it finished it just stayed on the really cool cyanogen boot screen and I had to power off and restore. Ive tried it a few times and nothing changed. I wiped the cache and stuff too. what should I do?
Are you trying to lead it directly from the app or are you trying to flash from recovery? Rom manager is buggy on the t989/t989D series. Flashing from an app is not recommended AT ALL due to potential of bricking the device
I guess my question is, what's your exact process you took...(i.e. steps taken)
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!
Ya I have been using the app. Can I still use the app to download roms? And then can I go into recovery from the app or just exit it and reboot it myself?
LostMoonOfPoosh said:
Ya I have been using the app. Can I still use the app to download roms? And then can I go into recovery from the app or just exit it and reboot it myself?
Click to expand...
Click to collapse
its recommended to simply download the rom zip the boot into recovery and install there. I use cm9 stable with tdj Darkside kernel 6 and flash everything through twrp recovery never had a single boot loop in any room I've flashed. What rom are you running currently?
1.Download rom and place in external sd card.
2. Reboot into recovery
(You may want to wipe data/factory reset depending on what rom you are running and clean install are typically recommended unless coming from a previous version from same developer (i.e. cm, aokp, etc)
3. Flash darkside super wipe and cache wipe if using cwm non touch
4. Flash rom, gapps and kernel (if so desired on the gapps and kernel)
5. Reboot and wait 10mins
6. Reboot again and have fun!
Let me know if that helps
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!
EnigmaticGeek said:
its recommended to simply download the rom zip the boot into recovery and install there. I use cm9 stable with tdj Darkside kernel 6 and flash everything through twrp recovery never had a single boot loop in any room I've flashed. What rom are you running currently?
1.Download rom and place in external sd card.
2. Reboot into recovery
(You may want to wipe data/factory reset depending on what rom you are running and clean install are typically recommended unless coming from a previous version from same developer (i.e. cm, aokp, etc)
3. Flash darkside super wipe and cache wipe if using cwm non touch
4. Flash rom, gapps and kernel (if so desired on the gapps and kernel)
5. Reboot and wait 10mins
6. Reboot again and have fun!
Let me know if that helps
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!
Click to expand...
Click to collapse
So I should just find the rom on my computer instead then?
Im downloading cyamogenmod 9 now from their website. I guess rom manager is pretty much useless for me then? I liked it because it would only show me roms that work for my phone so I dont make any mistakes.
ok I did it. but it didnt work... it just loaded up stock unrooted ics. with all my stuff gone. i have backups so im not worried about that, but i dont know why CM didnt flash...
LostMoonOfPoosh said:
ok I did it. but it didnt work... it just loaded up stock unrooted ics. with all my stuff gone. i have backups so im not worried about that, but i dont know why CM didnt flash...
Click to expand...
Click to collapse
I would use only super wipe
then flash ROM
reboot
wait ten minutes WITHOUT TOUCHING ANYTHING!!
reboot.
Its a proven formula that has worked for me, many, many times
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
Also, super wipe and cache wipe are found here read OP carefully
http://forum.xda-developers.com/showthread.php?t=1477955
LostMoonOfPoosh said:
ok I did it. but it didnt work... it just loaded up stock unrooted ics. with all my stuff gone. i have backups so im not worried about that, but i dont know why CM didnt flash...
Click to expand...
Click to collapse
Stock unrooted ics? What recovery are you using, have you flashed a recovery through odin at all with this device?
EnigmaticGeek said:
Stock unrooted ics? What recovery are you using, have you flashed a recovery through odin at all with this device?
Click to expand...
Click to collapse
is work fist root then factory reset then flash.
kiruba8 said:
is work fist root then factory reset then flash.
Click to expand...
Click to collapse
You need to have a recovery flashed to your phone to even start the root process. Cwm, cwm touch, or twrp. All are available in the sticky section as well as development section. If you are running stock recovery then that's your primary issue.
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!
LoopDoGG79 said:
I would use only super wipe
then flash ROM
reboot
wait ten minutes WITHOUT TOUCHING ANYTHING!!
reboot.
Its a proven formula that has worked for me, many, many times
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
Also, super wipe and cache wipe are found here read OP carefully
http://forum.xda-developers.com/showthread.php?t=1477955
Click to expand...
Click to collapse
Ok i looked at the darkside link you gave me. Will it for sure work with the telus version s2?
LostMoonOfPoosh said:
Ok i looked at the darkside link you gave me. Will it for sure work with the telus version s2?
Click to expand...
Click to collapse
Yes, the only difference between T-Mobile and Telus versions is cosmetic. Telus is the T989D, T-Mobile is the T989. There is a reason why they are so closely named.
Sent from the pink Unicorn from the Darkside.
EnigmaticGeek said:
Stock unrooted ics? What recovery are you using, have you flashed a recovery through odin at all with this device?
Click to expand...
Click to collapse
oh ya I have CWM recovery flashed so im good in that department. Im going to try out darkside superwipe now and see if that helps.
well I used darkside and then flashed my rom. Now it wont even go past the telus loading screen... Ive restored back again. I made it alot farther than this with rom manager haha. I actually saw the cyanogenmod opening cinematic... Ill try the darkside cache wipe this time and see if that helps. I downloaded the rom right from the cyanogen website...
Well neither is working. It just stays in the Telus loading screen. Not even the Samsung screen will load. I don't know what else to do...
Sent from my SGH-T989D using xda app-developers app
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'm trying to install the SUPERLITE CM10 JB4.1.2 RoM by vincom. I've followed the installation instructions as well as I can, using TWRP 2.4.2.0 and making sure to wipe cache, dalvik, system and factory reset twice. TWRP finishes flashing the new rom without giving any error messages, which I assume means all went well.
However, when I reboot from TWRP after flashing the rom, it stays stuck at the boot animation. Vincom's guide says the initial boot after the flash should take a minute, but I've left it for up to ten minutes and it just stays at the looping boot animation. If I pull the battery and restart the phone, it'll go back to the boot animation, but then a message appears, saying "android is being upgraded | 0/61 apps". It'll go up to 61/61 then disappear, which I assume means whatever it was doing is finished, but just stays stuck on the boot animation. And yes, I've made sure the MD5 checksum of the downloaded file matches the one listed at the download website.
For the time being, I'm going to go back to nandroid backup and install CWM recovery, and try to reflash the new rom from there, but I'm wondering if anyone has any idea why this is happening?
If it makes any difference, the rom I was on before is [TouchWiz] EMBRYO 6 -5 (The Gold Standard) (now the rom is up to release 6 -8, I am currently on 6 -5 but I was too lazy to update, then I decided to switch to vincom's superlite CM10)
Very good possibility you had a bad download. Try downloading it again and see if the problem persists
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Unfortunately, it still fails. There are two versions of the superlite CM10 rom, one with slim gapps and the other without. I made sure the MD5 checksums match the ones listed on the download pages. Both stay stuck at the boot animation. Flashing from CWM recovery didn't change anything, either.
RGM79 said:
Unfortunately, it still fails. There are two versions of the superlite CM10 rom, one with slim gapps and the other without. I made sure the MD5 checksums match the ones listed on the download pages. Both stay stuck at the boot animation. Flashing from CWM recovery didn't change anything, either.
Click to expand...
Click to collapse
This may sound like a real pain to do...but... you can go thru Odin and return to stock. Erase your internal memory and sd card. Then re-root.
I did that myself not to long ago due to my phone lagging on any rom I flashed.
I am now running Jedi Jelly 6....and it the SH%T.
Alright, I'll give that a try when I have time and I'll see how it goes, thanks.
In that case that rom's kernel was faulty. You can either restore to your old backup or mount sd card and install another rom. If you want that rom really bad wait for an update and pm the developer
---------- Post added at 05:30 PM ---------- Previous post was at 05:28 PM ----------
I dont think it is ur phone or the current rom your running's fault i think it is just a bad rom u downloaded.
Yeah, that does sound right. I've updated my current rom instead for the time being, thanks for the replies.
Hi all. I just got a Verizon Htc One M7. I bought it used and it was already updated to 4.4.2 Kit kat and sense 5.5. I am new to rooting and unlocking and I am running into issues I am hoping someone can help me with. I successfully unlocked, rooted, and got S-off. A am trying to get a custom kernel on the phone so I can have tap to wake and swipe to wake. I installed TWRP recovery 2.7.0.0. Everything appears to be working I boot into bootloader mode and it say unlocked and s-off on top of the screen. I started recovery and it appears to be working fine. I created a backup and that works. So I tried 2 different kernels elementalx and elite lunar. Both appear to install fine but when I reboot the phone gets stuck in a boot loop on the HTC screen. I then have to go back into recovery and revert back to my saved backup. The phone will then boot up fine. Not sure if I'm doing something wrong or what. I am running the stock ROM. Any help will be greatly appreciated.
Forgive and help a noop!!!!
No one knows? I also just noticed that on the bootloader screen there is no numbers after OS. Which would appear to mean i have no OS. But the phone boots and operates just fine. Any suggestions? Thinking I should get it back to factory and start over and flash the NuSenseSIX rom. If anyone could please help me out here it would be greatly appreciated!!!! I attached a picture of what my bootloader screen looks like.
Reubster24 said:
No one knows? I also just noticed that on the bootloader screen there is no numbers after OS. Which would appear to mean i have no OS. But the phone boots and operates just fine. Any suggestions? Thinking I should get it back to factory and start over and flash the NuSenseSIX rom. If anyone could please help me out here it would be greatly appreciated!!!! I attached a picture of what my bootloader screen looks like.
Click to expand...
Click to collapse
it's the rom you are on, if you go back to stock build you will see the OS-build number correctly displayed. if you are on a custom rom, and its not built correctly, it will not display properly.
you dont need to worry about it. all the info in hboot is for diagnostic purpose and wont effect you in any way.
synisterwolf said:
it's the rom you are on, if you go back to stock build you will see the OS-build number correctly displayed. if you are on a custom rom, and its not built correctly, it will not display properly.
you dont need to worry about it. all the info in hboot is for diagnostic purpose and wont effect you in any way.
Click to expand...
Click to collapse
Ok I appreciate the response. I am still on the stock ROM. Just have it rooted, unlocked and s-off with twrp custom recovery installed. Any ideas as to why I'm not able to get it to boot after installing a custom kernel? Can I just try to flash the NuSenseSIX ROM in the phones current state or should I start over?
Reubster24 said:
Ok I appreciate the response. I am still on the stock ROM. Just have it rooted, unlocked and s-off with twrp custom recovery installed. Any ideas as to why I'm not able to get it to boot after installing a custom kernel? Can I just try to flash the NuSenseSIX ROM in the phones current state or should I start over?
Click to expand...
Click to collapse
if you would like to try NuSense i would make sure you have a good backup or do one before. you'll need to wipe system - data - cache - dalvik in twrp and then install the rom.
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
After some discussion with fellow dev's, i think you havent flash the insecure boot.img that allows you to write to /system. this should stop the kernel bootlooping you.
ok, here we go.
Flash the attached zip in recovery.
wipe dalvik and cache (2x for good measure)
reboot the phone.
then try to flash a custom kernel and see if you boot loop. Let me know what happens. please have a working backup before trying any of this.
(credit to @buckmarble and @brymaster5000)
kernel source
synisterwolf said:
if you would like to try NuSense i would make sure you have a good backup or do one before. you'll need to wipe system - data - cache - dalvik in twrp and then install the rom.
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
After some discussion with fellow dev's, i think you havent flash the insecure boot.img that allows you to write to /system. this should stop the kernel bootlooping you.
Click to expand...
Click to collapse
I have everything backed up google drive with titanium backup as well as backed up in TWRP. When I wipe it doesn't remove the TWRP backup right? I have not flashed any boot.img. I am new to this and don't really know what that is. How would I find the boot.img I need. I think I'll just move forward with the NuSense Rom. Can I just download the zip for the NuSense ROM then wipe and flash it using TWRP and I'm good to go or is there other stuff I need to do?
Reubster24 said:
I have everything backed up google drive with titanium backup as well as backed up in TWRP. When I wipe it doesn't remove the TWRP backup right? I have not flashed any boot.img. I am new to this and don't really know what that is. How would I find the boot.img I need. I think I'll just move forward with the NuSense Rom. Can I just download the zip for the NuSense ROM then wipe and flash it using TWRP and I'm good to go or is there other stuff I need to do?
Click to expand...
Click to collapse
the boot.img zip above will allow you to write to the /system part of the phone.
TWRP will not wipe your backup. that is stored in a location its not allowed to wipe unless you do a "factory reset"
flash the zip above first. let it boot then flash NuSense. I'm not to familiar with that rom so i cant for sure say it will have said insecure boot.img.
Ok I flashed that file and the phone boots up fine. But it has a weird N flashing at the top of the screen now. I'll try a kernel this evening and see what happens. Any idea what the N is? Attached a zipped video of what its doing.
Reubster24 said:
Ok I flashed that file and the phone boots up fine. But it has a weird N flashing at the top of the screen now. I'll try a kernel this evening and see what happens. Any idea what the N is? Attached a zipped video of what its doing.
Click to expand...
Click to collapse
That icon is for NFC. idk why its flashing but make sure its off if you dont use it.
its under settings.
synisterwolf said:
That icon is for NFC. idk why its flashing but make sure its off if you dont use it.
its under settings.
Click to expand...
Click to collapse
Ok. It is off in settings. Tried to turn it on and it won't let me. I'll flash a kernel later and see what happens and if it stops doing it. Is there another insecure boot.img I can try?
Reubster24 said:
Ok. It is off in settings. Tried to turn it on and it won't let me. I'll flash a kernel later and see what happens and if it stops doing it. Is there another insecure boot.img I can try?
Click to expand...
Click to collapse
only need to do it once. flash any kernel that is meant for your rom or switch roms. you should be good to go.
synisterwolf said:
only need to do it once. flash any kernel that is meant for your rom or switch roms. you should be good to go.
Click to expand...
Click to collapse
Awesome thanks for all your help. I think I'm gonna flash a Rom. Any suggestions? I would like something close to the stock Rom.
Thank you for all your help!! I successfully installed the NuSense Rom.
Reubster24 said:
Thank you for all your help!! I successfully installed the NuSense Rom.
Click to expand...
Click to collapse
congrats man, you can PM me if you have anymore questions or post in the Q/A thread and i will try to help
:highfive: