Hey all,
I'm trying to install either CM10 or the Lifeless ROM (links here and here: http://forum.xda-developers.com/showthread.php?t=2189788 and http://forum.xda-developers.com/showthread.php?t=2083320). I had tried CM10 in the past but it didn't work that well. Thought I'd give it a second go, and, failing that, I'd try out this "lifeless". Sounded like a cool idea.
Background: phone was already rooted, and as I mentioned, i did actually get this CM10 rom to load sucessfully in the past, though I wasn't fully satisfied with the results. i figured this time I'd give it more time to sort out any issues I found. Failing that, I was going to go with the Lifeless ROM (which, I have decided I'm going to do over an unoffical CM10, I love that installer, if I can ever get it to work!). Anyway, here's what happened: I formatted Cache, Data, Davlik, and System just to be safe (same as I did last time). I tried flashing the CM10 ROM along with GApps. I got a hang on boot... just a black screen after the LG screen disappeared (yes, i forgot to do the TeenyBin flashes at the end... more on that later). So, I took this as a sign to try Lifeless, and I installed it successfully. Still a hang on boot... just the LG screen, and I let it go for a good half hour or more. Decided to do a restore of my backup (always do backups!), and... same thing. Even with the stock backup it would hang on boot.
So, I did some digging and I remembered about the TeenyBins! So I flashed the original one, just as I had last time I got CM10 to work. No dice, and even worse, TWRP was changed somehow (I am not sure if it changed versions, or what, but the menus were different), and now for some reason it couldn't even see my backup, even though the file browser in TWRP shows it clearly in the TWRP folder. So, I tried to install CM10, and flashed every one of the three TeenyBins offered on that page. The first one, of course, did nothing. The second, gave me a Google logo instead of LG, and I can actually see the choices on the bootloader screen now (I assume becuase it's based on the Nexus?), but again, nothing. The third (ZVBin) gave me a stuck LG logo for 5 minutes, then a few screen flashes and a kernel panic! Now I'm utterly confused.
EDIT: After the kernel panic, I restarted into recovery, and after the ZVBin flash, i have TWRP 2.4.4.0. It now sees my backup! I'm attempting to run the backup to see if I can at least get my phone back! If this doesn't work, I'll re-flash the Original TeenyBin... and then go from there. I thought about flashing the modems as the link from the CM10 page says, but before I get into changing even MORE, I'll defer to a professional's suggestions, haha.
I've exhausted just about every single option I can think of, I hope someone out there can help me! I would love to just get my phone to boot in some way so I can flash my backup file right back on. Any ideas on what might be causing this?
Thanks!
Sucess! Kinda. With the ZVBin, I was able to restore my phone, and get it to boot. And for some reason, the restore took my /sdcard folder and moved it into sdcard/sdcard0... don't know what that's about.
Any suggestions on what might have happened, and why Lifeless didn't want to work? Does it have soemthing to do with the TeenyBins I had to flash to make CM10 work? What do the TeenyBins replace? Sounds like the boot partition. Is there a way to get a plain one, with just TWRP 2.5 and the LS970 stuff it needs?
Ok, last post for the night, I think... tried to install Lifeless again, and it just fails, right off the bat. it says "Error flashing zip" with no explanation.
VDub2625 said:
Ok, last post for the night, I think... tried to install Lifeless again, and it just fails, right off the bat. it says "Error flashing zip" with no explanation.
Click to expand...
Click to collapse
If it reads error or fail something in that nature it still flashes fine for lifeless ROM, he posted something bout on the first page so go ahead and enjoy
RubbleTea said:
If it reads error or fail something in that nature it still flashes fine for lifeless ROM, he posted something bout on the first page so go ahead and enjoy
Click to expand...
Click to collapse
No, it didn't even get to the flash stage, just when I swipe to flash, it instantly failed.
But, i got it working! Not sure why or how, but I re-downloaded the Lifeless ROM and it worked with a fresh file. The file I had on there originally worked at first, but something must have happened to make it not work afterwards.
However, I do still have the Google boot-up screen and the Bootloader screen shows me menu choices, unlike every other Optimus G. I'm also still on TWRP 2.4.4.0. I hope it's not a problem. And maybe my expirences could help enlighten others,or maybe someone can help explain why exactly I went down this road, haha. I'd love to understand how the bootloader works on this particular phone, because it seems different from my old HTC.
Sorry to seem a little skittish with this post... but I was figuring it out as I was going along, and understood about half of it, haha. Just typing it out I think helped me to figure out what I was doing.
VDub2625 said:
Ok, last post for the night, I think... tried to install Lifeless again, and it just fails, right off the bat. it says "Error flashing zip" with no explanation.
Click to expand...
Click to collapse
I just quoted you here cause your last entry was long anyways here's a flash able twrp 2.5,http://androidforums.com/boost-mobi...ry-twrp-2-5-touch-recovery-cwm-flashable.html just flash in your recovery!
VDub2625 said:
No, it didn't even get to the flash stage, just when I swipe to flash, it instantly failed.
But, i got it working! Not sure why or how, but I re-downloaded the Lifeless ROM and it worked with a fresh file. The file I had on there originally worked at first, but something must have happened to make it not work afterwards.
However, I do still have the Google boot-up screen and the Bootloader screen shows me menu choices, unlike every other Optimus G. I'm also still on TWRP 2.4.4.0. I hope it's not a problem. And maybe my expirences could help enlighten others,or maybe someone can help explain why exactly I went down this road, haha. I'd love to understand how the bootloader works on this particular phone, because it seems different from my old HTC.
Sorry to seem a little skittish with this post... but I was figuring it out as I was going along, and understood about half of it, haha. Just typing it out I think helped me to figure out what I was doing.
Click to expand...
Click to collapse
Well now I know I need to try that second teenybin... I miss having that Google bootloader screen and the menu options I wonder if that is the only way to get it?
Sent from my Lifeless Optimus G
Related
So I I've had 2 different recoveries so far that have worked fine.. both came from Rogue though. One was from the 1.5 kernel (Hitman) which installed CWM Touch recovery, the other came with the normal recoveries based off CW 5.0.2.7. They were working fine until I installed Calkulin's Rom(2.8.1). Not sure if they're just incompatible or what, but when I go to recovery it shows the background image of the recovery but none of the options show up. It shows for about half a second and then it goes back to the original boot screen, then to the 2nd screen and turns on. So it basically skips right through the recovery and reboots. Do I need a new Rom or can I fix this? I really like the battery life and visuals of Calkulin's Rom and would love to be able to keep it.
EDIT: One more thing.. Since I installed the ROM, I've been getting market error 492. It doesn't allow me to install anything in the market..
I haven't tried a full wipe yet, so I guess I'll try that and then see how that works with the recovery and Rom..
I did the same thing to my phone this week, and I'm running Blazer, so i'm sure it has nothing to do with either ROM.
Not sure how I caused it but with so many folks running both without this error, I'm guessing that your issue (like mine was) was probably some how self induced.
I flashed back to stock and started over, and things have been working great. Might be worth a shot flashing back, or restore a backup and start fresh.
Haven't seen the market error before. I'm sure someone here has
Good Luck
If you got it off here, could you show me which stock you flashed..?
Everything you need is in the Epic 4G Touch Android Development section
Here is the post I used from Sfhub
http://forum.xda-developers.com/showthread.php?t=1433101
Watch the videos by Qbking77 They walk you thru everything step by step. (I hear his video intro rif every time I close my eyes now so you've been warned) Makes it super easy.
I would read everything you can and watch the videos before you get in too deep. I've had this phone since December, and just flashed my 1st ROM this week cause I've been reading up, and learning all I could before I jumped in the pool.
Well I've done all this with 2 phones before but I've never had this happen.. normally I just get the Rom and I'm good to go..
I think I must've gone wrong somewhere when I originally rooted through a stock rom.. It already seems to be more respondful.
premo1 said:
I think I must've gone wrong somewhere when I originally rooted through a stock rom.. It already seems to be more respondful.
Click to expand...
Click to collapse
Try booting while holding the volume up and power button.
If that does not work, flash recovery from rom manager, and that should get you into recovery to flash whatever kernel/recovery u want.
I've done all that.. None of it works.. I'm currently ODIN'ing Factory Stock Rom with root. Hopefully after that I can redo all of these and eventually end up with a working, corresponding Rom and kernel..
premo1 said:
I've done all that.. None of it works.. I'm currently ODIN'ing Factory Stock Rom with root. Hopefully after that I can redo all of these and eventually end up with a working, corresponding Rom and kernel..
Click to expand...
Click to collapse
Good Luck.
Recovery and market are now working Thank you Adanorm!
Glad your back up and running
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
eternalcold said:
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
Click to expand...
Click to collapse
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
BWolf56 said:
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
Click to expand...
Click to collapse
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
eternalcold said:
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
Click to expand...
Click to collapse
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
BWolf56 said:
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
Click to expand...
Click to collapse
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
eternalcold said:
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
Click to expand...
Click to collapse
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
BWolf56 said:
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
Click to expand...
Click to collapse
Alright, i'll flash that one, i'll post to here when it's finished. Thanks!
Did you check your IMEI?
xBeerdroiDx said:
Did you check your IMEI?
Click to expand...
Click to collapse
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
eternalcold said:
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
Click to expand...
Click to collapse
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
BWolf56 said:
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
Click to expand...
Click to collapse
Understood, I wont mess with them.
I really just want to understand a couple things.
1. Why did the ROM I installed before work for everyone else except me? and i followed the instructions.
and 2. after flashing to stock, how am I unable to fix this?
mainly to just learn what went wrong.
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
hednik said:
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
Click to expand...
Click to collapse
Thanks,
Is there any way to repair it?
Alright, so....
I think i have figured out what the issue was. Or by random chance got it fixed.
I was going to try to install the Synergy Rom. And while going through the custom setup, i noticed "Install AOSP Messaging" and "Install TW Messaging"
I chose the TW messaging, and went through the rest of the installer.
For some reason i kept hanging at the "Samsung Galaxy S3" logo, and it would not boot.
(Honestly, i've used custom roms since the HTC Touch Pro 2, and i've NEVER had such issues. And i personally think the TP2 was way more difficult lol)
So I ONCE AGAIN flashed to stock. and randomly the messaging works!
I only can guess that even when flashing the stock rom, it doesnt change something regarding the messaging app. I'm not sure. All i know is that i'm on stock again and everything is working. I highly doubt i'm going to try another custom rom for a while until i have a full understanding of what happened.
But in case anyone else was having this problem, i hope this helped.
So 2 days ago a friend bought an HTC Desire HD. It was working fine, but since it was second hand he wanted to hard reset it, and so he did. After he did that it started doing what I am showing in the video below(but it was with an older version, gingerbread I think). It was also going in CWM 10 sec after it was put into a charger. After I tried installing custom roms and roots, I installed what is said to be a stock ruu:
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed
Click to expand...
Click to collapse
It is obviously(visually) a newer version of the software the phone uses, than the one it had when he first gave the phone to me.
Nothing seems to have worked at this point, I'm desperate. After that 4th option of the setup(scheduled sync) it just goes black screen with a status bar and nothing. When he first gave it to me it used to display an error that said something like setup couldn't load, and with options to close it, wait for it, or tell HTC about it. It CAN receive SMS and calls, but there just isn't any GUI(menu, or whatever it's called).
I'm also providing a picture of the bootloader below.
I don't need the phone to be rooted or with any particular ROM or version, I just need it working normally.
Any help/assistance will be welcome! Thanks in advance
VIDEO:
youtube.com/watch?v=aNI1t4KjY-0&feature=youtu.be
youtube.com/watch?v=aNI1t4KjY-0&feature=youtu.be
Just makes it easier to click on it. :beer:
Edit: Try booting without the sd card, but aside from that, no idea.
You can also try flashing a stable gb rom see if you get the same issue.
Sent from a dream.
<-------- new user here. cant post links thanks
iLoveAlkohola said:
<-------- new user here. cant post links thanks
Click to expand...
Click to collapse
If you already have s-off and cwm, why not just flash rooted stock rom? It should work fine if the rom can be flashed successfully.
If it is not, it is most probably hardware issues, although i am not so sure myself.
yumm91 said:
If you already have s-off and cwm, why not just flash rooted stock rom? It should work fine if the rom can be flashed successfully.
If it is not, it is most probably hardware issues, although i am not so sure myself.
Click to expand...
Click to collapse
As I said, before installing the newest stock ruu(with which I lost cwm and can''t seem to get it back), I installed some custom roms, all of them with the same effect. But thanks for the suggestion.
iLoveAlkohola said:
As I said, before installing the newest stock ruu(with which I lost cwm and can''t seem to get it back), I installed some custom roms, all of them with the same effect. But thanks for the suggestion.
Click to expand...
Click to collapse
Make a full wipe before flashing the Ruu. Flash a custom recovery in fastboot, do a full wipe, then flash a ROM (stock or custom) To see what happens
Already did all that. When I first got the phone I used the full wipe function of cwm(and of the stock recovery) a couple of times, but every time it was stuck at that point of the initial setup with the error showing up.
Is there a file SPECIFICALLY for the initial setup that I can flash to the phone, because I flashed different recoveries, roms, boots and even radios manually before installing the stock ruu. I haven't set up a phone before, so I'm not sure, but as I can see there are still 2 or 3 options left to select ,after that scheduled sync option, before the phone could run the main menu(gui or whatever).
Oh, and btw, when I updated it with that ruu, the setup visually changed and by that I figure out it gets flashed as part of the ruu, but still with the same problem. Can it be some kind of hardware problem of the internal memory? No matter how much I searched and where I looked I never found someone with a problem even close to this one.
Teichopsia said:
Edit: Try booting without the sd card, but aside from that, no idea.
You can also try flashing a stable gb rom see if you get the same issue.
Sent from a dream.
Click to expand...
Click to collapse
Whatever I was doing to the phone it didn't usually have an sdcard in it and was booting without an sd card, tried with and without, no changes.
After I installed that sense ruu i can't seem to get back to gb, any ideas how to do it? I also can't get cwm to work now, even though it flashes without any error or problem I can only ge the htcdev root(already did) with this ruu, I think but I don't get any changes except that there is a watermark on the first line of bootloader.
Long story short, I accidentally flashed a rom form the wrong carrier onto my s3 (yeah yeah, go ahead and laugh. I wasn't looking hard enough when sonic-developers' site only had the D2LTE version, not the D2SPR).
So I can enter recovery and download modes just fine. The problem is I can't seem to boot into the system. I've tried wiping both cache's, system, and data, and tried normal factory reset. I tried recovering my last working rom that I had fully backed-up (the people's rom 4.1.2). All I get when I try to boot into system is the samsung logo, then a perpetual black screen.
Does anyone know what's going on, and if you could point me inn the right direction? If this has been asked a lot before, please just link me.
Masterjuggler said:
Long story short, I accidentally flashed a rom form the wrong carrier onto my s3 (yeah yeah, go ahead and laugh. I wasn't looking hard enough when sonic-developers' site only had the D2LTE version, not the D2SPR).
So I can enter recovery and download modes just fine. The problem is I can't seem to boot into the system. I've tried wiping both cache's, system, and data, and tried normal factory reset. I tried recovering my last working rom that I had fully backed-up (the people's rom 4.1.2). All I get when I try to boot into system is the samsung logo, then a perpetual black screen.
Does anyone know what's going on, and if you could point me inn the right direction? If this has been asked a lot before, please just link me.
Click to expand...
Click to collapse
Well, don't do what I did in this thread.
Actually, I somehow got CM11 to flash properly. I'll go through the setup process and see if I can't figure out why. Then I'll try flashing back to a ROM that I know works.
Cool. Yeah, at this point I'm not sure if mine is dead or what. I don't mess around enough with cell phones and ROM images to know what things should or shouldn't look like. I think I was doing everything the way you are supposed to, but it never worked the way it was written/videos showed it/I expected.
Actually, what is the difference between d2lte and d2spr? now that I'm reading farther into it, it looks like they are the same thing.
Masterjuggler said:
Actually, what is the difference between d2lte and d2spr? now that I'm reading farther into it, it looks like they are the same thing.
Click to expand...
Click to collapse
They are the same thing. d2lte works on all us Galaxy S3 that are supported by cm
Sent from my SPH-L710 using Tapatalk
Yeah, I just realized that d2lte is just a single build of all the qualcomm-based variants after researching it more. I tried flashing sokp again, and this time it worked. I have no idea why, but oh well. Now to see if this ROM will work for me.
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Fingerless said:
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Click to expand...
Click to collapse
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
BWolf56 said:
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
Click to expand...
Click to collapse
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Fingerless said:
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Click to expand...
Click to collapse
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
BWolf56 said:
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
Click to expand...
Click to collapse
You think it would be safe to do a factory reset and try to restore just the data from my recovery? Or is it possible that the data is somehow the issue with everything going wonky?
I'm very new to the ROM thing, Omni was easy to get up and running, but actually playing with a ROM was more of a last ditch effort to see if the problem would be resolved that way and give any sort of indication as to what the issue was (still haven't the sllightest). It's currently not rooted (at least according to my root checker) and the towelroot method doesn't seem to work on it. I kinda need to be rooted if I wanted to make a nandroid, I really want to make a back up of what I currently have set in case I screw the pooch trying to get things back to "normal", yet I'm afraid of overwriting my only recovery and losing whatever data is embedded, though I'm not too deeply saddened by the thought of not having chat histories and whatnot, it would just be nice to have. Perhaps you have thoughts, or anyone else out there, on the matter? I know my first step would be to at least root my current ROM, then back up, I found this as a means to root Omni (http://forum.xda-developers.com/showthread.php?t=2672160), but how do I determine whether I'm using an ARM based or x86 based device?
Good to know the file size for the stock ROM is considered normal. I didn't even consider carrier/Samsung bloat to have such a huge impact.
Thanks, yet again!