Develop Bugs

[Q] phone wont load, stuck in bootloop

my phone is stuck in bootloop. im able to get into CWM recovery, but cant restore nandroid or make a nandroid.
keeps looping in google screen
someone please help.

acatabian said:
my phone is stuck in bootloop. im able to get into CWM recovery, but cant restore nandroid or make a nandroid.
keeps looping in google screen
someone please help.
Click to expand...
Click to collapse
Have you tried a wipe from cwm?
Sent from my Galaxy Nexus using xda premium

i wiped data/cache/dalvik and still nothing.
:'(

anyone please, i dont know whats happening

Now that you've wiped it, you won't be able to make a nandroid anyway, you'd be backing up... nothing. When you say you can't restore a nandroid, what exactly is happening when you try? Do you try to restore an existing nandroid and an error stops the process? Does CWM not find any nandroids that should be there? Have you ever restored to a nadroid before that you know there *should* be one that works?
Based on what you've written here I'd suggest just restoring to factory installation and picking up the pieces from there. Before you do, you can try to backup what's on your phone using the command "adb pull /sdcard". If you have a nandroid that might be good but for some reason unusable by your phone right now, it will be copied and you can try to restore it after reverting to factory settings. Otherwise, it should pull off any personal stuff like your photos etc so it's not a total loss.
If you're on a GSM Nexus, follow instructions here.
If you're on a CDMA Nexus, follow instructions here.
It is really the exact same process for either, but you want to make sure you've got the right set of files. This will basically leave you where you were when you first unlocked the bootloader.

JoeSyr said:
Now that you've wiped it, you won't be able to make a nandroid anyway, you'd be backing up... nothing. When you say you can't restore a nandroid, what exactly is happening when you try? Do you try to restore an existing nandroid and an error stops the process? Does CWM not find any nandroids that should be there? Have you ever restored to a nadroid before that you know there *should* be one that works?
Based on what you've written here I'd suggest just restoring to factory installation and picking up the pieces from there. Before you do, you can try to backup what's on your phone using the command "adb pull /sdcard". If you have a nandroid that might be good but for some reason unusable by your phone right now, it will be copied and you can try to restore it after reverting to factory settings. Otherwise, it should pull off any personal stuff like your photos etc so it's not a total loss.
If you're on a GSM Nexus, follow instructions here.
If you're on a CDMA Nexus, follow instructions here.
It is really the exact same process for either, but you want to make sure you've got the right set of files. This will basically leave you where you were when you first unlocked the bootloader.
Click to expand...
Click to collapse
yeah, i ended up unrooting and flashing factory image back. but i did however root and unlock bootloader again.
now, whenever i finish flashing my new rom. it gets stuck looping on the boot animation, not the google logo. is there any reason behind this? could it relate back to what happened before?

acatabian said:
yeah, i ended up unrooting and flashing factory image back. but i did however root and unlock bootloader again.
now, whenever i finish flashing my new rom. it gets stuck looping on the boot animation, not the google logo. is there any reason behind this? could it relate back to what happened before?
Click to expand...
Click to collapse
When you say "it gets stuck", how long are we talking here? Sometimes, depending on what you just wiped/what you're flashing, the phone will just take a longer time to boot. If you assume something's wrong and pull the battery you might just mess it up when really you just needed to be patient and let it finish.
These are probably questions best addressed in threads for specific ROMs, though, where people might have had similar experiences, or the ROM dev might be able to use your feedback. It's especially hard to formulate an opinion that might be useful when you provide barely any specific information to what you're working with.

[Q] April Fools Prank gone wrong... help please

Okay so let's start off by saying my cousin is an idiot. He tried pulling an April fool's joke on me (ill spare you the details) and ended up wiping my phone THROUGH THE STOCK METHOD (As in going to settings and resetting the phone...). And so, im left with a phone in bootloop... awesome. So I need some help reviving it. I have no freaking clue if I still have clockwork running on it (i think it is because the boot animation for the ROM i was running is still there and the unlock thing at the bottom when it first boots up is there). I was running AOKP beta 25 with lean kernel along with the lucid theme atop of AOKP. Can someone please help guide me on how to get my phone up and running?

azn android said:
Okay so let's start off by saying my cousin is an idiot. He tried pulling an April fool's joke on me (ill spare you the details) and ended up wiping my phone THROUGH THE STOCK METHOD (As in going to settings and resetting the phone...). And so, im left with a phone in bootloop... awesome. So I need some help reviving it. I have no freaking clue if I still have clockwork running on it (i think it is because the boot animation for the ROM i was running is still there and the unlock thing at the bottom when it first boots up is there). I was running AOKP beta 25 with lean kernel along with the lucid theme atop of AOKP. Can someone please help guide me on how to get my phone up and running?
Click to expand...
Click to collapse
You may have to flash the stock google factory image. If you hold down both volume buttons and the power button while the phone is off, you can get into fastboot mode (the screen with the opened up Android). Then you can use the gnex toolkit (you can get it from the development forums) to flash the stock google factory image.

Just boot into recovery. You'll then know if you have CWM. If you have CWM, just try a data/cache/dalvik wipe and reboot. If it still bootloops, do a full wipe and re-flash the ROM.
If you don't have CWM, you can flash it through fastboot and try the above.
Don't freak out. A bootloop is about the farthest from a brick you can be.

what exactly will that do..? Will I lose unlock/root? and sorry if you don't mind, could you point me to the tool?

Alright so even after wiping and reflashing the ROM, im still in a bootloop. I dont mind having to go back to 100% stock no unlock if that's what it takes but can anyone help me out?

OK the easiest way to sort this out for you but perhaps not the best way is go to http://code.google.com/android/nexus/images.html and download a factory rom and use a tool kit like mskips http://forum.xda-developers.com/showthread.php?t=1392310 to flash everything back to stock. This will wipe your entire phone so back up anything you wanted to keep but I promice your phone will work again.
I only say this isn't the best possible way as it would be best to learn about adb and fast boot as to know how to do all this manually but I don't have a good knowledge on adb but its something I'm meaning to do just don't have a great deal of time for. The tool kit will do everything for you simply by pressing keys and a few clicks and will install all the drivers you need. Good luck
Sent from my Galaxy Nexus using Tapatalk

Thank you! I was able to flash to the stock image and keep my unlock! Sadly, since my cousin wiped my phone, i lost everything anyways... but I have my essential things (pictures, contacts, and some apps) already backed up. Thank you for your help!

azn android said:
Thank you! I was able to flash to the stock image and keep my unlock! Sadly, since my cousin wiped my phone, i lost everything anyways... but I have my essential things (pictures, contacts, and some apps) already backed up. Thank you for your help!
Click to expand...
Click to collapse
Glad you figured it out. Flashing the Google Images doesn't relock the bootloader (unless you explicitly do so with the oem lock command). You can now start over and load a custom ROM.

Good I'm glad you fixed it, today your learned a little bit of how to get out of sticky situations. I'm glad to of helped
Edit
Now be sure to return the favour to your cousins phone
Sent from my Galaxy Nexus using Tapatalk

Custom ROM infinite first boot

Firstly: I'm a total n00b for this. I have flashed custom ROMs before, but not for Nexus, so this is my first attempt, so far failing spectacularly.
That said, I'd appreciate advice on both what I did wrong and how to un-brick my phone.
I searched and my problem seems strictly linked to bad flashing, but all solutions are phone specific and I haven't found a thread for Galaxy nexus, so here goes:
I chose this firmware for my flash. I also used the toolkit from stickied post above.
I unlocked the bootloader and then ran (not installed) the CWM tools. Using them I flashed the image directly. The phone was not rooted though I later ran the rooting procedure and it finished without reporting any particular errors. Android naturally never booted during this procedure.
Anyway, my phone now stays in boot animation indefinitely. Recovery mode with fastboot works, but no android joy.
Help greatly appreciated.

More info is needed you didn't mention toro, toro plus, maguro. Ask you need to do is bout into bootloader and fastboot your images back to stick look in your models thread on how to do that so you can get the correct ones.
Sent from my Galaxy Nexus using xda premium

Sorry for panicking too soon. Phone unbricked. Would still appreciate info on what I did wrong to brick it in the first place.

Beamer9408 said:
More info is needed you didn't mention toro, toro plus, maguro. Ask you need to do is bout into bootloader and fastboot your images back to stick look in your models thread on how to do that so you can get the correct ones.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hm, I've been reading on toolkit and roms for a couple of days now and I still can't really say what toro or maguro is. In what way would they be important for my troubles?

velis74 said:
Hm, I've been reading on toolkit and roms for a couple of days now and I still can't really say what toro or maguro is. In what way would they be important for my troubles?
Click to expand...
Click to collapse
It's very important to know what type of google nexus you have. Majority of custom ROMs are only compatible to certain type of GNex. Maguro is for GSM GNex while TORO is for CDM/LTE GNex. Check the link below for more info:
https://groups.google.com/forum/#!msg/android-building/qzSxFEqWvNg/qanfxMkzXHMJ
One more thing, aside from Maguro and Toro, you still need to know what build or version of GNex you have (yakju or takju). This can also be considered when flashing new custom ROMs. I know majority (or all) of the ROMs works well with either yakju or takju, there is still a slight possibility that you will encounter an issue with the version. Check out the links below for more info regarding yakju and takju:
http://forum.xda-developers.com/showthread.php?t=1778543
http://forum.xda-developers.com/showthread.php?t=1617685

Oh, in that case, I have a GSM version, Maguro it would seem.
The ROM I downloaded doesn't specifically say, but the same developer posted another ROM for which he confirmed GSM compatibility.
So can I myself find out what ROM this is since I can't ask the question in the development thread (I don't have 10 posts yet)?

did you clear all the caches via custom recovery? Although I haven't hit issues with my nexus while flashing, past devices, a factory reset sorts the bootloop most often (unless it was a bad flash). Just note that factory resetting the nexus gets rid of ALL of your data since there isn't an external SD to house your files and keep them protected from a wipe.
I would recommend you making a nandroid backup now that you're up and running again btw
Just my 2 cents

Kohawk09 said:
did you clear all the caches via custom recovery? Although I haven't hit issues with my nexus while flashing, past devices, a factory reset sorts the bootloop most often (unless it was a bad flash). Just note that factory resetting the nexus gets rid of ALL of your data since there isn't an external SD to house your files and keep them protected from a wipe.
I would recommend you making a nandroid backup now that you're up and running again btw
Just my 2 cents
Click to expand...
Click to collapse
Yes, I cleared everything I found in main menu and advanced menu of CWM.
Do I *NEED TO* root my phone in order to install a custom ROM? I would think not, but one can't be sure. That's why I only unlocked bootloader before flashing.
Edit: Yes, I found about the factory reset the hard way. Executed full wipe, then tried to flash...

velis74 said:
Yes, I cleared everything I found in main menu and advanced menu of CWM.
Do I *NEED TO* root my phone in order to install a custom ROM? I would think not, but one can't be sure. That's why I only unlocked bootloader before flashing.
Click to expand...
Click to collapse
I would think you should have rooted... my logic is that you're flashing a zip, so you're making changes to /system, which requires root. I'm not technical enough to say whether or not installing a zip can work around not having root access, but I would think not. If you were flashing system images, I would think you could get by without rooting, but not for just a zip file.
Have you taken a look at the toolkit? Soon as I got my nexus I did the one click to unlock, root, install CWM. Took less than 10 min. I already knew fastboot commands, so no reason for me to do it manually if I can get it done automatically.

Kohawk09 said:
I would think you should have rooted... my logic is that you're flashing a zip, so you're making changes to /system, which requires root. I'm not technical enough to say whether or not installing a zip can work around not having root access, but I would think not. If you were flashing system images, I would think you could get by without rooting, but not for just a zip file.
Have you taken a look at the toolkit? Soon as I got my nexus I did the one click to unlock, root, install CWM. Took less than 10 min. I already knew fastboot commands, so no reason for me to do it manually if I can get it done automatically.
Click to expand...
Click to collapse
no to toolkits... just no...
you do not need root to flash custom roms, only an unlocked bootloader and CWM or TWRP for your recovery.

Zepius said:
no to toolkits... just no...
you do not need root to flash custom roms, only an unlocked bootloader and CWM or TWRP for your recovery.
Click to expand...
Click to collapse
Why all the hate for the toolkit? Probably the only confusing thing to me since moving to the nexus is why so many seem to be against its use... I think its a great and helpful tool.

Kohawk09 said:
Why all the hate for the toolkit? Probably the only confusing thing to me since moving to the nexus is why so many seem to be against its use... I think its a great and helpful tool.
Click to expand...
Click to collapse
go look at Q&A
everyday there are at least 5-10 threads saying "HELP I BRICKED MY NEXUS... i used this toolkit but i have no idea what happened to my phone"
if someone is too lazy to type in these 2 commands and then flash su.zip to their phone, they dont need to be dinking with custom ROMs
Code:
fastboot oem unlock
fastboot flash recovery nameofclockworkortwrp.img
nexus phones are some of the easiest phones to unlock and root. there is no real need for a toolkit.

I'm currently making another attempt, but this time I'm rooting the phone and trying an image that is confirmed GSM.

Zepius said:
go look at Q&A
everyday there are at least 5-10 threads saying "HELP I BRICKED MY NEXUS... i used this toolkit but i have no idea what happened to my phone"
if someone is too lazy to type in these 2 commands and then flash su.zip to their phone, they dont need to be dinking with custom ROMs
Code:
fastboot oem unlock
fastboot flash recovery nameofclockworkortwrp.img
nexus phones are some of the easiest phones to unlock and root. there is no real need for a toolkit.
Click to expand...
Click to collapse
makes sense.... agree its probably more of a hinder than a help for those without basic fastboot knowledge. Especially since that knowledge is needed for getting out of a bind many times. Was just curious why I see some much negativity towards it...I still think its a useful tool to save time, at least from my perspective, if you already have that background. The files are all downloaded together and it was more of a convenience thing for me at least. The driver piece is probably the most helpful, since they can be a real PITA if there are leftovers from previous devices...

Just thought I pop my head in and say you were bootlooped. Not bricked. Not even soft bricked as that would constitute you had no recovery, which you did have. Just getting you clear on the lingo we use here.
Sent From My Toro+ via SkyBlue Tapatalk

Seems I chose a bad ROM after all. Flashing to CdTDroid's other ROM worked immediately.
Well, almost: after flash it would continuously report "system UI stopped working" or some such. I had to perform another factory reset before it actually worked as it should.
Now to go test if my issues with this phone are finally over or not.

velis74 said:
Seems I chose a bad ROM after all. Flashing to CdTDroid's other ROM worked immediately.
Well, almost: after flash it would continuously report "system UI stopped working" or some such. I had to perform another factory reset before it actually worked as it should.
Now to go test if my issues with this phone are finally over or not.
Click to expand...
Click to collapse
before you install a rom, always wipe data/cache.

That's the problem: I thought I did. Anyway, it's working now. Will have another go at CM later. Since I'm on custom ROM I might as well go all the way
Sent from my Galaxy Nexus using xda app-developers app

velis74 said:
I'm currently making another attempt, but this time I'm rooting the phone and trying an image that is confirmed GSM.
Click to expand...
Click to collapse
You don't need to root, as flashing the ROM will wipe the root. Most ROMs come with root access already, so people don't notice when they flash.

Yeah, figured as much + stopped doing all the unnecessary crap. Turns out flashing takes few steps but I dare not be as careless to say it's easy.
I have now successfully flashed the CM10 ROM by CdTDroiD straight from stock 4.0.4.
Turns out I misinterpreted "wipe data/factory reset" in CWM. It doesn't clear the filesystem (/sdcard) as I thought. Seems I managed to delete my files some other way during the first flashing attempt. Not clearing data was the cause of bootloop as Über reminds me it's called.
I did all that plus kept the original ICS animation which I like better than JB one. I'm really happy thus far having used it for a couple of hours.

[Q] Recovery won't flash rom. Need Direction

My wife and I have the same phone, Verizon GNex. However, our phones are completely different! I'm currently on AOKP build 4. She was on Build AOKP ICS 40. I attempted to flash build 4 and gapps after a full wipe, etc, but I never could get it to flash properly. The first time I flashed it, it allowed to try to sign her into her account. She had google 2 step on and I wasn't able to get her loaded. The second phone on file for 2 step was her own, so when the text came I couldn't get to it (for whatever reason the soft keys were missing and I couldn't get out once I was stuck in the 2 step process.) I then pulled the battery to reboot. It was stuck in a boot loop that I couldn't get out. When I tried to flash back to the backup file from build 40 it was missing, as was all the other backup files. I didn't have a copy to flash to and the rom was stuck in boot loop. I couldn't use fastboot because it was saying "fastboot read error 2147483647" I decided to odin 4.02 stock software. It worked great to get me out of the loop and get the phone up and going again. Since that point I updated the stock software, rerooted ,and reinstalled CWR. However, no matter how I try to flash any build of AOKP now it fails. I even pulled the files from my phone that I had flashed just days before and put them on my wife's phone. Nope. Didn't work. I tried TWRP and I couldn't get it to work either. What other options should I take to get the rom on my wife's phone. She's about to kill me already for "messing" it up.

Redownload the ROM, make sure she doesn't have toroplus and you're trying to flash a toro ROM or something like that, make sure if she has a toro GalNex she also has a toro recovery, try flashing the latest 4.1.1 radios....
Toro is Verizon GalNex, toroplus is Sprint.
Sent from my Galaxy Nexus using xda app-developers app

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

I tried something different. One phone good. One phone JACKED!
I tried a clean download via a wired connection. Same result, FAIL! Instead I used the odin files I found to flash the toro (VZW). After which I rerooted the device and downloaded CM10 nightly and flashed without ANY problems.
My phone (AOKP toro JB build 4) ran completely out of battery charge that it powered off. The ironic thing is, after charging completely in the off state I started it back up...(same) BOOT LOOP! I've searched a little bit on the forums, but I can't seem to find the exact way to undo this. This is the same boot loop I had with my wife's phone. I tried to flash my most recent JB 4 backup and it gets an error after the system restore and just before the data restore. I tried all the other backups of many different builds with CWM and had the same result. I tried flashing the AOKP JB 4 but it just ends up in the boot loop again.
I can't push any new files to it for whatever reason so I can't try to flash the radios or bootloader. Honestly, I can't even read the internal memory where everything is stored. I think it's because the debuging mode isn't turned on since I tried to reflash a new build and restore my backup. " I love AOKP, but I'm going to hold off until a new milestone build comes out. At this point I just want the pictures/videos from my phone. I have a backup on my computer saved, but none of the pictures/videos are saved.
:crying:
-Chlorine
jimmyco2008 said:
Redownload the ROM, make sure she doesn't have toroplus and you're trying to flash a toro ROM or something like that, make sure if she has a toro GalNex she also has a toro recovery, try flashing the latest 4.1.1 radios....
Toro is Verizon GalNex, toroplus is Sprint.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse

Chlorine tablet said:
I tried a clean download via a wired connection. Same result, FAIL! Instead I used the odin files I found to flash the toro (VZW). After which I rerooted the device and downloaded CM10 nightly and flashed without ANY problems.
My phone (AOKP toro JB build 4) ran completely out of battery charge that it powered off. The ironic thing is, after charging completely in the off state I started it back up...(same) BOOT LOOP! I've searched a little bit on the forums, but I can't seem to find the exact way to undo this. This is the same boot loop I had with my wife's phone. I tried to flash my most recent JB 4 backup and it gets an error after the system restore and just before the data restore. I tried all the other backups of many different builds with CWM and had the same result. I tried flashing the AOKP JB 4 but it just ends up in the boot loop again.
I can't push any new files to it for whatever reason so I can't try to flash the radios or bootloader. Honestly, I can't even read the internal memory where everything is stored. I think it's because the debuging mode isn't turned on since I tried to reflash a new build and restore my backup. " I love AOKP, but I'm going to hold off until a new milestone build comes out. At this point I just want the pictures/videos from my phone. I have a backup on my computer saved, but none of the pictures/videos are saved.
:crying:
-Chlorine
Click to expand...
Click to collapse
Code:
fastboot boot cwm_or_twrp.img
when in recovery:
Code:
adb pull /sdcard/
note: if no folder is really pulled, change /sdcard/ to /data/media

Some tips for the two step verification that I have found out. Although it says not to use a Google voice account it is by far the Best method for dong two step. For me I always have some other device logged into Google Voice and I use that device to get the text. The other thing I do is forward texts with that string to my gmail account so I get it as an email. I figure if someone has my device and is trying to log in then they can't see my Google voice or emails

I will try this in the morning. I just drove the family 12 hours back from our Disney vacation. Ah, my own bed to sleep in.
-Chlorine
bk201doesntexist said:
Code:
fastboot boot cwm_or_twrp.img
when in recovery:
Code:
adb pull /sdcard/
note: if no folder is really pulled, change /sdcard/ to /data/media
Click to expand...
Click to collapse

While waiting for things to settle down this morning I thought I would try one last thing to get the phone back to working. Within CWM I choose to use fix permissions. After a few minutes it finished and returned to CWM menus as normal. I rebooted the phone and it's working. I'll need to copy the files from it before progressing forward. Once I do this I will try rebooting and see what it does. Take in mind I tried flashing, recovering, etc before I even thought of the fix permissions. It stopped me in my tracks with the errors. Once I reboot I will post my results. I just hope I didn't leave my cable in Florida.
:victory:
-Chlorine

Just bought a new cable and I'm starting a full backup now. I'll reboot and see if the phone loops again or not in an hour or so. Details to come.

Reboot. No boot loop.

[Q] Cyanogen 10.1 mod gone wrong.

AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.

chazbot7 said:
AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
Click to expand...
Click to collapse
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).

Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.

BWolf56 said:
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Click to expand...
Click to collapse
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.

chazbot7 said:
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
Click to expand...
Click to collapse
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.

BWolf56 said:
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
Click to expand...
Click to collapse
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?

chazbot7 said:
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
Click to expand...
Click to collapse
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app

BWolf56 said:
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.

chazbot7 said:
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
Click to expand...
Click to collapse
No need to apologize. Glad you got it back up! And it was mostly to keep you from making similar mistakes in the future
Sent from my SGH-I747 using xda app-developers app

also one thing you need to know
First boot after you flash will always take longer than normal. After that, it's fine