Related
Hi, its my first time posting, I figured I wanted to sign up to XDA eventually so why not when I feel like I've completely ruined my phone... or at least internal sd card...
Basically I rooted my phone and was flashing the Jellybam rom, and everything was going smoothly until I got to the bootloader and my phone started bootlooping. My first thought was 'Oh but I have a backup'. So I went to my backup in CWM and to my dismay I got an error saying "No files were found."
I could clearly see my files from exploring around on my sd card however they were now in a file called '0' and CWM could not read them from there. Without a working ROM I started to panic. However I had a zip of CM10 still on my internal sd card so I flashed that and (luckily) it worked.
Not really being too competent with flashing new ROMs yet I was quite happy that I had anything. So I used titanium backup to reinstall my old apps and data. However once they were installed I now get an error with 'the process android.process.media has stopped'.
I'm guessing this has do do with the fact that I have all my files still on the '0' folder. All the other folders from the '0' folder were the same except they were all empty, soooooo I decided to delete them. At this point I'm guessing that was a really bad idea because my initial plan of moving all the files from '0' to my pc then back to my phone, I did not think about the fact that I would be moving 14 Gb of data...
So basically now I'm hoping if someone knows a way to revert my phone to 4.1.2 by somehow moving all the files from '0' back onto the internal storage (basically getting rid of this '0') folder. The CM10 ROM is a 4.1.2 ROM so its not like I'm fudging up my phone further (I hope).
If you could be as detailed as possible as to what to do that would be great, because I'm really really new to this....
From what I've read I've heard a couple of suggestions:
1. updating the recovery.img of CWM will work? How exactly do I do this?
2. opening abd shell recovery and moving the files like that (however I deleted all the other files in the internal storage apart from '0' because that was where all the data was stored and everything else was empty...'
help. :crying:
0Capita said:
Hi, its my first time posting, I figured I wanted to sign up to XDA eventually so why not when I feel like I've completely ruined my phone... or at least internal sd card...
Basically I rooted my phone and was flashing the Jellybam rom, and everything was going smoothly until I got to the bootloader and my phone started bootlooping. My first thought was 'Oh but I have a backup'. So I went to my backup in CWM and to my dismay I got an error saying "No files were found."
I could clearly see my files from exploring around on my sd card however they were now in a file called '0' and CWM could not read them from there. Without a working ROM I started to panic. However I had a zip of CM10 still on my internal sd card so I flashed that and (luckily) it worked.
Not really being too competent with flashing new ROMs yet I was quite happy that I had anything. So I used titanium backup to reinstall my old apps and data. However once they were installed I now get an error with 'the process android.process.media has stopped'.
I'm guessing this has do do with the fact that I have all my files still on the '0' folder. All the other folders from the '0' folder were the same except they were all empty, soooooo I decided to delete them. At this point I'm guessing that was a really bad idea because my initial plan of moving all the files from '0' to my pc then back to my phone, I did not think about the fact that I would be moving 14 Gb of data...
So basically now I'm hoping if someone knows a way to revert my phone to 4.1.2 by somehow moving all the files from '0' back onto the internal storage (basically getting rid of this '0') folder. The CM10 ROM is a 4.1.2 ROM so its not like I'm fudging up my phone further (I hope).
If you could be as detailed as possible as to what to do that would be great, because I'm really really new to this....
From what I've read I've heard a couple of suggestions:
1. updating the recovery.img of CWM will work? How exactly do I do this?
2. opening abd shell recovery and moving the files like that (however I deleted all the other files in the internal storage apart from '0' because that was where all the data was stored and everything else was empty...'
help. :crying:
Click to expand...
Click to collapse
1- Your solution
2- Was quite the bad idea to delete it all so this solution won't work now.
clockwordmod.com is where you'll find the latest recovery.
BWolf56 said:
1- Your solution
2- Was quite the bad idea to delete it all so this solution won't work now.
clockwordmod.com is where you'll find the latest recovery.
Click to expand...
Click to collapse
So how exactly do I do that? I just download the the latest clockwork mod and flash it? Why can't it be updated via an automatic updater? And what will it do to the file or will it change clockwork mod so that it will scan the entire sd card?
Also if I just remade folders identical to the ones I deleted, will that still work?
I'm just trying to get my phone to be as functional as it was before this all started.
Thanks for replying btw!
0Capita said:
So how exactly do I do that? I just download the the latest clockwork mod and flash it? Why can't it be updated via an automatic updater? And what will it do to the file or will it change clockwork mod so that it will scan the entire sd card?
Also if I just remade folders identical to the ones I deleted, will that still work?
I'm just trying to get my phone to be as functional as it was before this all started.
Thanks for replying btw!
Click to expand...
Click to collapse
That's a lot of question for the simple fix I gave you.. I haven't used cwm in a while so Idk what changed in the update but if people said it fixed it, then it did..
0, 1, 2, etc.. Is something that came with JB, it's for the different users. Not much can be done about it.
About how you should do that: Go on their website, FOLLOW their instructions to a T, Enjoy.
As for why it can be updated via an automatic updater.. Well I'm not the person you should ask.
B said:
Wolf56;371questions it's a lot of question for the simple fix I gave you.. I haven't used cwm in a while so Idk what changed in the update but if people said it fixed it, then it did..
0, 1, 2, etc.. Is something that came with JB, it's for the different users. Not much can be done about it.
About how you should do that: Go on their website, FOLLOW their instructions to a T, Enjoy.
As for why it can be updated via an automatic updater.. Well I'm not the person you should ask.
Click to expand...
Click to collapse
Sorry for all the questions, I'm just worried that I messed up my phone. Would you know if I were able to be able to access my old clockwork mod backups and used one of them, would it put my 0 files back into the internal storage like they used to? Or would it only revert the settings and I would still be SOL.
0Capita said:
Sorry for all the questions, I'm just worried that I messed up my phone. Would you know if I were able to be able to access my old clockwork mod backups and used one of them, would it put my 0 files back into the internal storage like they used to? Or would it only revert the settings and I would still be SOL.
Click to expand...
Click to collapse
Yes, that's the whole point of the cwm update. Now to flash it!
Or, go digg through the cm nightly thread. They had a flash able zip that would restore your internal sd after downgrading Android versions.
BWolf56 said:
Yes, that's the whole point of the cwm update. Now to flash it!
Click to expand...
Click to collapse
Well here's my latest problem... I tried to update CWM with an .img however when I tried to run it in the terminal it said there was not enough space... I don't know what to do... there is definitely a couple gigs free so I don't know what is wrong...
mrhaley30705 said:
Or, go digg through the cm nightly thread. They had a flash able zip that would restore your internal sd after downgrading Android versions.
Click to expand...
Click to collapse
the cm nightly thread? So theres a zip that would make 4.2 go back to 4.1?
Okay update:
I managed to flash update the new version of CWM... still can't use backup... I get a /system fail
It doesn't downgrade you're ROM. It fixes the 0 folder issue
mrhaley30705 said:
It doesn't downgrade you're ROM. It fixes the 0 folder issue
Click to expand...
Click to collapse
Ugh Okay I've given up... I dont know what else to try. Now that I've updated my CWM I cant flash the old CM10 because it reads it as a 4.1 and uncompatable... FML.
Can anyone point me to where I can find the Odin stock factory? I guess I'll just start from scratch...
http://db.tt/rWFbAFiF
Link to restore files from /0 directory
Credits go to madmack
Sent from my SGH-I747 using xda app-developers app
Helloworld294 said:
http://db.tt/rWFbAFiF
Link to restore files from /0 directory
Credits go to madmack
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
OOOMMMMMGggg ahhhhhh, that would have been so helpful but I've already started to factory reset it. Thanks though!
ahhhhhhhhh
Forget cwm it sucks use twrp and be done with all the problems
Sent from the scary door....
Hi,
i tried to flash a custom ROM and i found a tutorial which said to use "super wipe android revolution" so i put it in the sdcard like the .zip from the custom ROM.
I launched "choose zip from sdcard" and selected super wipe.zip, but after rebooting on recovery when i tried to apply the next file with "choose .zip from sdcard" it said to me that "no files found"!
When i reboot normally, there is the samsung LOGO but nothing else after 5-10 minutes....
Omg that script is erase all the data so why should i do this before flashing a new rom i can't understand why i can't do anything know execpt going on recovyer/ DL mode.
Can you please help me to find a solution like putting maybe the custom ROM on external SD card ?? is it possible or ?
Thanks a lot i'm very afraid of being in this situation...
ppn7 said:
Hi,
i tried to flash a custom ROM and i found a tutorial which said to use "super wipe android revolution" so i put it in the sdcard like the .zip from the custom ROM.
I launched "choose zip from sdcard" and selected super wipe.zip, but after rebooting on recovery when i tried to apply the next file with "choose .zip from sdcard" it said to me that "no files found"!
When i reboot normally, there is the samsung LOGO but nothing else after 5-10 minutes....
Omg that script is erase all the data so why should i do this before flashing a new rom i can't understand why i can't do anything know execpt going on recovyer/ DL mode.
Can you please help me to find a solution like putting maybe the custom ROM on external SD card ?? is it possible or ?
Thanks a lot i'm very afraid of being in this situation...
Click to expand...
Click to collapse
Wow, that was quite dangerous to flash a zip that you didn't fully understand. It's actually amazing you don't have a full hard brick on your hands. First rule of flashing is to read everything at least twice and if you have any questions on it, read more and ask questions until you understand it. Then you can think about flashing it. Ok, I'll get off my soapbox (to open up room for the many other people who'll say something similar).
Anyways, back to the issue at hand. If you can get into Recovery, It doesn't sound like you're bricked... it just sounds like everything was wiped. If you have a MicroSD card, you can use an adapter and copy a Rom over to your card, then install it through your custom recovery.
If you do not have an external sd card, you could also use the recovery to do a USB mount to your computer (will look like a flash drive on your computer). There should be an option for that in the recovery (TWRP 2.5.0 has it, not sure if CWM has it).
Lastly, if you can't mount the device as usb storage through the recovery, you can always push it across through adb. Search google on how to do it.
Also, before you flash any Rom, make sure you are not flashing an international rom, as that will brick your device. No coming back from that.
topherk said:
Wow, that was quite dangerous to flash a zip that you didn't fully understand. It's actually amazing you don't have a full hard brick on your hands. First rule of flashing is to read everything at least twice and if you have any questions on it, read more and ask questions until you understand it. Then you can think about flashing it. Ok, I'll get off my soapbox (to open up room for the many other people who'll say something similar).
Anyways, back to the issue at hand. If you can get into Recovery, It doesn't sound like you're bricked... it just sounds like everything was wiped. If you have a MicroSD card, you can use an adapter and copy a Rom over to your card, then install it through your custom recovery.
If you do not have an external sd card, you could also use the recovery to do a USB mount to your computer (will look like a flash drive on your computer). There should be an option for that in the recovery (TWRP 2.5.0 has it, not sure if CWM has it).
Lastly, if you can't mount the device as usb storage through the recovery, you can always push it across through adb. Search google on how to do it.
Also, before you flash any Rom, make sure you are not flashing an international rom, as that will brick your device. No coming back from that.
Click to expand...
Click to collapse
You could odin a stock rom as well
Sent from my blue galaxy
---------- Post added at 07:40 PM ---------- Previous post was at 07:39 PM ----------
ppn7 said:
Hi,
i tried to flash a custom ROM and i found a tutorial which said to use "super wipe android revolution" so i put it in the sdcard like the .zip from the custom ROM.
I launched "choose zip from sdcard" and selected super wipe.zip, but after rebooting on recovery when i tried to apply the next file with "choose .zip from sdcard" it said to me that "no files found"!
When i reboot normally, there is the samsung LOGO but nothing else after 5-10 minutes....
Omg that script is erase all the data so why should i do this before flashing a new rom i can't understand why i can't do anything know execpt going on recovyer/ DL mode.
Can you please help me to find a solution like putting maybe the custom ROM on external SD card ?? is it possible or ?
Thanks a lot i'm very afraid of being in this situation...
Click to expand...
Click to collapse
Where is this tut? Not here I.hope
Sent from my blue galaxy
Yeah as topherk said, thats extremely dangerous and you should consider yourself lucky that your phone boots up at all.
Best thing to do right now would be to ODIN back to stock and start fresh, but this time make sure you are in the Sprint sections and you understand what you are flashing before you flash it.
Yea man, you are lucky! Your situation is very good, considering.
I have been flashing ROMs since the originial Droid came out. Still, with each new phone I get and root and ROM, I am as nervous as a whore in church! One wrong move, and you can make your expensive phone into a brick. I learned the hard way, then I had to learn how to use TFTP again. Ugly! lol.
When the previous poster said something like, read all you can, then read it again, he was not joking around. Your best bet imo is to get Freezy's stock rooted ROM, and install that. I am certain that will fix all your problems. Go with the MB1 first. Then, do as you please, but certainly stick to ROMs in the Sprint subforum. The one you attempted to flash appears to be for a HTC phone.
Seriously, having some reading comprehension skills is an absolute must if you're going to mess around with your phone. Well unless you have money to keep tossing at sprint every other day cuz you keep going off half cocked and brick your phone. If what you tried to flash really was for an HTC device all I have to say is: WTF gave you any idea that would work out in any sort of ok manner? And did you even attempt to read anything about what you were fixing to do? Or did you just go "oooh shiny and pretty, I think I'll just go try to install it and see what happens. I know it'll work they're all android so they're all the same thing"
☆SoA: Son's of Android™☆
I like to break stuff!
Now, now, I try not to insult too much. I think it's best to point out their mistakes in a calm manner (which, admittedly, is hard to do on the 16th thread like this). This person said they were following a tutorial (not here on the Sprint GS3 XDA forums, I've searched for it), so maybe the tutorial was just really bad. I'm not trying to exonerate the op of their responsibility, but I'd like to keep this place as civil as possible. Hopefully they learned their lesson and will only flash street really making sure it's for their phone. That's my hope.
Sent from my SPH-L710 using xda app-developers app
I've answered this same or similar question 9 times today alone across several different devices, and that's not counting the other 7 or 8 I skipped over because I was too irritated to even type. I honestly think most of these people think that because it's android it's all the same and they can just go flashing whatever they want all willy nilly with no repercussions. It's beginning to get ridiculous, actually it is ridiculous. It's like they can't be bothered to read anything first except just enough to brick their phone and then run to look for a miracle. You know that noob video giantjay posted in general, that's how I feel about now.
☆SoA: Son's of Android™☆
I like to break stuff!
I will not preach.... But at least skim multiple threads atleast to see what issues people are running into. Get an idea of what u are up against. Secondly LOCATION LOCATION LOCATION. Know where your tuts come from. There are people out there in cyber land that just don't know or give a cra* . Lastly, make a friend most people here that have the knowledge would like nothing more than to pass it along. GOOD LUCK!
Sent from my MB886 using xda app-developers app
Alright, so I am having this weird issue. I thought I found the fix for it several times, however, NO dice.
I've researched for a few hours now, I just don't know if I have over looked it or what. If it has been answered, I apologize.
I looked at the modified recoveries thread for newer s3 devices, but it doesn't seem to fit my area of error.
The Details:
I've been really curious to try some 4.3 roms. Of course, they are for D2SPR. I get them to flash correctly, after a full wipe. The issue happens right after I set everything up in the phone, and reboot. When I reboot I get hung at the splash screen. I have tried to reflash the rom muliple times only to fall flat on the splash screen again. Now, I don't have an SD Card in the phone, except, I left a TW rom in a folder. I use twrp, forgot to mention that. I rewiped the phone and installed that touchwiz rom, and still it wouldn't allow me to get past splash into that tw rom.
So the only way that I could think of to get out of this hole was to flash the rooted LJ7 tar file I have through ODIN. After getting the S3 into download mode, Odin successfully push LJ7 into my phone. Now again, I had an issue getting it to boot. I read somewhere that when this happens, I need to check the Erase NAND option in Odin. So I tried that out and forced LJ7 back on. After successfully flashing, it boots but gets stuck on the boot animation; the fix to that is booting into stock recovery and wiping once more. Then you are able to get into the OS.
I let the phone sit and take the OTAs till I get from LJ7 to MD4 so I re-root the phone using Odin and Chain Fire's root method. Now I am able to flash the recovery (TWRP) using OpenScript through Goo Manager.
I've only tried flashing Illusion and Carbon's 4.3 rom. The second time I used Carbon's rom. Same results. So I have no Idea what the heck is going on. Can anyone explain this to me better or point me into the direction that I need to go?
Thanks much!
your not the only one that has this problem i have the same thing have tried everything and most of the 4.3 roms same thing. no one on xda seems to know at least i havent gotten any help or responses i have just given u on 4.3. good luck finding any ideas.
Set it up I'm sure you restored some apps and data which may no longer be compatible. Or data which is corrupting the 4.3 rom. Try just flashing the rom setting up your Google account and don't add any apps. See if it does it.
Either way this seems to be a common issue across different devices and 4.3 seems it's part of using roms built on leaks and ports. None are bug free. Very similar to all gb leaks back in the day that would go into bootlooping.
Have a great day!
bbrita said:
your not the only one that has this problem i have the same thing have tried everything and most of the 4.3 roms same thing. no one on xda seems to know at least i havent gotten any help or responses i have just given u on 4.3. good luck finding any ideas.
Click to expand...
Click to collapse
Well, it's good to know that I'm not the only one, however, it's horrible that it's happening to others. I appreciate you spreading the info!
edfunkycold said:
Set it up I'm sure you restored some apps and data which may no longer be compatible. Or data which is corrupting the 4.3 rom. Try just flashing the rom setting up your Google account and don't add any apps. See if it does it.
Either way this seems to be a common issue across different devices and 4.3 seems it's part of using roms built on leaks and ports. None are bug free. Very similar to all gb leaks back in the day that would go into bootlooping.
Have a great day!
Click to expand...
Click to collapse
When I go to set up, I just install about 15 apps, I don't restore. I just download them fresh. I had a habit of doing that and it just stuck. I don't restore anything with Titanium or and root backup/restore app. Could one of those apps not be updated then that causes the partitions to get locked up, or just corrupt /data in general? If that's whats happening.
I just find it extremely odd that I (maybe others), can't wipe, and then re flash another rom; actually I can, it just gets stuck at the splash and never goes forward, that is what had me confused most. If I had an sd card, and formatted data itself, would that fly?
thanks Ed i have tried this after the first 2 tries . i dont have any problems installing 4.3 its just after rebooting it gets stuck. Like you said there are always bugs Im fine with using other roms for now. Hopefully when an official 4.3 drops problems will go away
Ive tried several ROMs over the years on my ATT GS3. Lately Ive been using the Liquid Smooth ROM. About 4 months after install I started getting screen flashes/colors, random restarts, the phone was getting hot and Ext SD card errors so it was pretty much unusable. Went to try some other ROMs and cant get them to flash. Tried Beanstalk, ProBAM, and Goodness Reborn and they fail immediately. Ive downloaded from different mirrors and the file size is identical. Ive tried flashing from internal and still wont work. Also updated TWRP throughout this process and didnt fix it. The only one that does flash is Synergy but im not a fan of 4.1. Would rather have 4.2/4.3.
Any ideas on why these ROMs arent flashing? Ive tried multiple times.
I dont know the ins and outs all that well but it seems something is corrupted. Would it make sense to odin back to stock/unroot and start fresh? Follow this? http://forum.xda-developers.com/showthread.php?t=2186967
Or is this a fixable issue without going through all that?
Who Am I? said:
Ive tried several ROMs over the years on my ATT GS3. Lately Ive been using the Liquid Smooth ROM. About 4 months after install I started getting screen flashes/colors, random restarts, the phone was getting hot and Ext SD card errors so it was pretty much unusable. Went to try some other ROMs and cant get them to flash. Tried Beanstalk, ProBAM, and Goodness Reborn and they fail immediately. Ive downloaded from different mirrors and the file size is identical. Ive tried flashing from internal and still wont work. Also updated TWRP throughout this process and didnt fix it. The only one that does flash is Synergy but im not a fan of 4.1. Would rather have 4.2/4.3.
Any ideas on why these ROMs arent flashing? Ive tried multiple times.
I dont know the ins and outs all that well but it seems something is corrupted. Would it make sense to odin back to stock/unroot and start fresh? Follow this? http://forum.xda-developers.com/showthread.php?t=2186967
Or is this a fixable issue without going through all that?
Click to expand...
Click to collapse
From what it sounds, it could be a bootloader problem. Did you ever update to 4.1.2? All 4.3 ROMs require at least the 4.1.2 bootloader, which you can get without Odin'ing 4.1.2 from here:
http://forum.xda-developers.com/showthread.php?t=2321310
As always read, read and read. If this doesn't help, I recommend maybe trying out CWM (I'd restore back to your TouchWiz backup since that backups from TWRP and CWM aren't compatible.) If that still doesn't help, then by all means, Odin to stock, OTA to 4.1.2, root and go on. As always, this is just information from one member to another, so I am in no way, shape or form responsible for anything and everything that could go wrong.
The 4.1.2 ota update just came out today so no. I'll try that in the morning thanks!
Who Am I? said:
Ive tried several ROMs over the years on my ATT GS3. Lately Ive been using the Liquid Smooth ROM. About 4 months after install I started getting screen flashes/colors, random restarts, the phone was getting hot and Ext SD card errors so it was pretty much unusable. Went to try some other ROMs and cant get them to flash. Tried Beanstalk, ProBAM, and Goodness Reborn and they fail immediately. Ive downloaded from different mirrors and the file size is identical. Ive tried flashing from internal and still wont work. Also updated TWRP throughout this process and didnt fix it. The only one that does flash is Synergy but im not a fan of 4.1. Would rather have 4.2/4.3.
Any ideas on why these ROMs arent flashing? Ive tried multiple times.
I dont know the ins and outs all that well but it seems something is corrupted. Would it make sense to odin back to stock/unroot and start fresh? Follow this? http://forum.xda-developers.com/showthread.php?t=2186967
Or is this a fixable issue without going through all that?
Click to expand...
Click to collapse
Fail immediately? As in you're able to flash them but can't boot properly or you have glitches?
Sounds like a hardware issue to me. Hope you got warranty.
I click install, select the zip and it starts working for a couple seconds and fails.
Just updated the bootloader and ProBAM and Goodness failed. Tried Beanstalk and it completed fine. Gonna try it out for a bit. It is 4.3 so not sure what the issue it with the other ROMs yet
Beanstalk is up and running. Thanks drx!!
edit
Just dl'd Carbon ROM and CM 10.1.3. Both failed immediately when I used TWRP to flash them. Updated bootloader, updated SuperSU. Should I go back to CWM?
What am I missing? If there are no other ideas is my only option to ODIN back to stock and try again?
Who Am I? said:
Just dl'd Carbon ROM and CM 10.1.3. Both failed immediately when I used TWRP to flash them. Updated bootloader, updated SuperSU. Should I go back to CWM?
What am I missing? If there are no other ideas is my only option to ODIN back to stock and try again?
Click to expand...
Click to collapse
Try Task650's rom. It's the most stable and smooth I've used. Also, he has good instructions on what bootloader to use.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Moved to internal and flashed fine. Rebooting now.
Spent most of yesterday on AirDroid moving files back to my external. Came back and it looks like it killed the battery. Plugged in, rebooted and now my ext sd card wont show up. I bought a 64GB Samsung microcard off Ebay. Formatted on the phone and started tranferring files fine. Was going slow but working. Really dont want to format and start over but the phone wont even see it so I cant format it from the phone.
First post, so forgive me if this isn't quite right. Been struggling with rooting/putting Cyanogenmod on my computer over the last few days/week or so. I took the OTA 4.3 update awhile back and hated it, but kinda bit the bullet and dealt with it. Rooted and put a custom recovery on it last week, everything went well enough, tried TWRP and CWM recovery and found I preferred CWM.
When I went earlier, after finally getting a nandroid backup done successfully (neither recovery could save the backup to my external SD card, but that's another issue altogether) I went to flash the CM 10.2 stable release from their website, and it threw an error 7 assert fail.
After failing to restore properly from the backup (somehow) and locking up at launch with com.google.apps has stopped working before I could even get my launcher to open, I finally just wiped the entire phone and booted from scratch to get it to "work", managed to not lose root in doing so as I've just checked and found out.
Point being, error 7 assert fail on a sprint s3 trying to flash cm10.2 from CWM recovery. I had the most up to date ROM manager and CWM (I believe). This all coming after I spent 4+ days failing to be able to have my recoveries make nandroid backups to my SD card (don't know if related).
At this point I've kind of relinquished to lose everything on my phone when I flash the new OS, so I kinda just wanna get CM on there already and remedy this issue altogether. Does anyone have any idea what could be causing this issue, and how to remedy it? Like I said, I'm running stock samsung ROM with the 4.3 update taken OTA.
If anyone has any insight I'd really appreciate it, I know it shouldn't be as difficult as it has been to deal with all this stuff but after lurking for over a week to try and find an answer I just have to ask myself.
Thanks.
MTSL_Mantra said:
First post, so forgive me if this isn't quite right. Been struggling with rooting/putting Cyanogenmod on my computer over the last few days/week or so. I took the OTA 4.3 update awhile back and hated it, but kinda bit the bullet and dealt with it. Rooted and put a custom recovery on it last week, everything went well enough, tried TWRP and CWM recovery and found I preferred CWM.
When I went earlier, after finally getting a nandroid backup done successfully (neither recovery could save the backup to my external SD card, but that's another issue altogether) I went to flash the CM 10.2 stable release from their website, and it threw an error 7 assert fail.
After failing to restore properly from the backup (somehow) and locking up at launch with com.google.apps has stopped working before I could even get my launcher to open, I finally just wiped the entire phone and booted from scratch to get it to "work", managed to not lose root in doing so as I've just checked and found out.
Point being, error 7 assert fail on a sprint s3 trying to flash cm10.2 from CWM recovery. I had the most up to date ROM manager and CWM (I believe). This all coming after I spent 4+ days failing to be able to have my recoveries make nandroid backups to my SD card (don't know if related).
At this point I've kind of relinquished to lose everything on my phone when I flash the new OS, so I kinda just wanna get CM on there already and remedy this issue altogether. Does anyone have any idea what could be causing this issue, and how to remedy it? Like I said, I'm running stock samsung ROM with the 4.3 update taken OTA.
If anyone has any insight I'd really appreciate it, I know it shouldn't be as difficult as it has been to deal with all this stuff but after lurking for over a week to try and find an answer I just have to ask myself.
Thanks.
Click to expand...
Click to collapse
Status 7 doesn't have anything to do with your choice of recovery, it is because your bootloader is not listed in the get prop of the older ROM releases. You need to modify the assert lines to match your current bootloader or delete them altogether for something like CM 10.2 or any other ROM based on AOSP 4.3.x; realistically, I would just recommend jumping straight to KitKat 4.4.x, the asserts will reflect your current bootloader. Also, I would very highly recommend switching to Philz Touch recovery, it is based on CWM, but it is really like CWM on steroids.
Mr. Struck said:
Status 7 doesn't have anything to do with your choice of recovery, it is because your bootloader is not listed in the get prop of the older ROM releases. You need to modify the assert lines to match your current bootloader or delete them altogether for something like CM 10.2 or any other ROM based on AOSP 4.3.x; realistically, I would just recommend jumping straight to KitKat 4.4.x, the asserts will reflect your current bootloader. Also, I would very highly recommend switching to Philz Touch recovery, it is based on CWM, but it is really like CWM on steroids.
Click to expand...
Click to collapse
I was going to just jump right into using one of the nightly CM11 builds but I saw a few places people were having some bugs (as is expected with a nightly) and wanted to try to stick with a stable release for right now.
So if I go into the updater-script and change/remove all of the get-prop commands it should work? There's no chance of that causing any other issues?
I had philz when I first rooted the thing, and someone suggested that I switch to twrp when I started having the not-being-able-to-make-a-nandroid-on-my-external-SD-card problem, but I didn't care for it and ended up getting the most current CWM recovery just to leave it. I don't have any complaints about it as is, except the frustration I have with the entire process so far of trying to get this thing situated.
MTSL_Mantra said:
I was going to just jump right into using one of the nightly CM11 builds but I saw a few places people were having some bugs (as is expected with a nightly) and wanted to try to stick with a stable release for right now.
So if I go into the updater-script and change/remove all of the get-prop commands it should work? There's no chance of that causing any other issues?
I had philz when I first rooted the thing, and someone suggested that I switch to twrp when I started having the not-being-able-to-make-a-nandroid-on-my-external-SD-card problem, but I didn't care for it and ended up getting the most current CWM recovery just to leave it. I don't have any complaints about it as is, except the frustration I have with the entire process so far of trying to get this thing situated.
Click to expand...
Click to collapse
Yes, you will be able to flash 4.3.x AOSP ROM's by modifying/deleting the assert (get prop) lines. The reason those lines exist in the first place is so that someone on TMobile doesn't flash a ROM meant for Sprint, when the phone is the same but available on multiple carriers. As long as you choose a d2spr ROM you are fine. I am personally loving CM11 and CyanFox 4.4.2, they have both been very stable and awesome for me, but I also don't use things like Bluetooth, and my area has no LTE yet, so I wouldn't even notice problems of those types in the first place. And again, I recommend (extremely highly!!) Philz Touch recovery, I have yet to see anyone complain about issues with Philz that I have seen complained about from CWM or TWRP.
Mr. Struck said:
Yes, you will be able to flash 4.3.x AOSP ROM's by modifying/deleting the assert (get prop) lines. The reason those lines exist in the first place is so that someone on TMobile doesn't flash a ROM meant for Sprint, when the phone is the same but available on multiple carriers. As long as you choose a d2spr ROM you are fine. I am personally loving CM11 and CyanFox 4.4.2, they have both been very stable and awesome for me, but I also don't use things like Bluetooth, and my area has no LTE yet, so I wouldn't even notice problems of those types in the first place. And again, I recommend (extremely highly!!) Philz Touch recovery, I have yet to see anyone complain about issues with Philz that I have seen complained about from CWM or TWRP.
Click to expand...
Click to collapse
I did what you suggested and removed the assert statements at the start of that script. This time it didn't throw the assert but still failed. It said "installing update" and then immediately threw "installation aborted" a second later without any other information..
MTSL_Mantra said:
I did what you suggested and removed the assert statements at the start of that script. This time it didn't throw the assert but still failed. It said "installing update" and then immediately threw "installation aborted" a second later without any other information..
Click to expand...
Click to collapse
Did you install Philz as well or are you still using CWM?
Mr. Struck said:
Did you install Philz as well or are you still using CWM?
Click to expand...
Click to collapse
No, it was still on CWM. I don't see how philz would change that behavior, philz wasn't able to perform backups on the external SD card either when CWM and TWRP couldn't, so I'm almost expecting them all the have the same issues, but I suppose I could be wrong.
Is there anything else worth trying? I feel like it shouldn't be this complicated, I have the right ROMs in the right places..
MTSL_Mantra said:
No, it was still on CWM. I don't see how philz would change that behavior, philz wasn't able to perform backups on the external SD card either when CWM and TWRP couldn't, so I'm almost expecting them all the have the same issues, but I suppose I could be wrong.
Is there anything else worth trying? I feel like it shouldn't be this complicated, I have the right ROMs in the right places..
Click to expand...
Click to collapse
Philz doesn't call your external SD by that name, it is called sdcard1. SDcard is the internal. All I can say is that, in my opinion, Philz is far superior, I would say give it another shot.
Sent from my SPH-L710 using Tapatalk
Mr. Struck said:
Philz doesn't call your external SD by that name, it is called sdcard1. SDcard is the internal.
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
I misspoke, I meant sdcard1 (or ext_sdcard or however the other recoveries reference it). None of them have been able to do it with their respective names. But that's (possibly) another issue, I just mean that's why I'm not positive switching would help. I could definitely be wrong though, I can try it if nothing else next time I get to a computer with Odin send it over.
There is a flashable zip as well just FYI. As to your backup location issues, I don't know what to tell you, I've never experienced that problem.
Sent from my SPH-L710 using Tapatalk
---------- Post added at 08:43 PM ---------- Previous post was at 08:42 PM ----------
Also, I know some users have had better luck renaming one of the bootloader assert lines to match the MK3 boot loader instead of deleting all the lines.
Sent from my SPH-L710 using Tapatalk
Maybe I'll try philz out then but if not I'm stumped.. I know it sholdn't be this difficult to do this crap, I'm glad that I'm learning some of the pitfalls, but some of these pitfalls don't seem like things other people have been encountering so I don't know what the deal is.