Hi guys, so I was using wicked ROM, whenever I tried to boot into recovery, it just rebooted back to system. Odin'ed back to stock, flashed twrp through goo manager app, but still no use. Any help greatly appreciated
Sent from my Nexus 7 using xda premium
eggydrums said:
Hi guys, so I was using wicked ROM, whenever I tried to boot into recovery, it just rebooted back to system. Odin'ed back to stock, flashed twrp through goo manager app, but still no use. Any help greatly appreciated
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
What methods have you tried?
adb reboot recovery is the easiest way to get to recovery
Maybe try flashing CWM, seeing if that works, and then flashing TWRP (I've never flashed TWRP through Goo Manager so I don't know how that works)?
If you don't have adb set up, get quick boot from market and try recovery through that.
If that doesn't work, I honestly don't know. I'm assuming you've done the power off then volume up+home+power at the same time trick already.
EtherealRemnant said:
What methods have you tried?
adb reboot recovery is the easiest way to get to recovery
Maybe try flashing CWM, seeing if that works, and then flashing TWRP (I've never flashed TWRP through Goo Manager so I don't know how that works)?
If you don't have adb set up, get quick boot from market and try recovery through that.
If that doesn't work, I honestly don't know. I'm assuming you've done the power off then volume up+home+power at the same time trick already.
Click to expand...
Click to collapse
With the goo app, I can boot directly into recovery, but my issue is that I get to the Recovery's splash screen, it hangs there for a second and immediately reboots back to system. I'm thinking to get the stock recovery back and try again I'm really not sure what the Hecks going on
Sent from my Nexus 7 using xda premium
Mhm OK, got cwm working, guess I'll just use that one for the time being
Sent from my Nexus 7 using xda premium
eggydrums said:
Mhm OK, got cwm working, guess I'll just use that one for the time being
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I would highly recommend putting TWRP back on there. The CWM was more for testing... people have reported issues using CWM with certain ROMs. Glad you were able to get CWM on though.
Nothing wrong with CWM.
Aerowinder said:
Nothing wrong with CWM.
Click to expand...
Click to collapse
There are a number of ROMs that do not support CWM so that statement is false. FreeGS3 loses update functionality, for example.
Also, there have been complaints in the case of CWM touch of it being too easy to wipe your entire device.
Not to mention there is no Goo Manager functionality without TWRP as well.
Lots of benefits of TWRP versus CWM. I used CWM for years then had to switch to a modified TWRP for my MAXX and was more than happy when I found out the SGS3 used TWRP as well (although I wish we had the ROM slots like the MAXX though - that was actually cool)
The statement is not false. I think FreeGS3 hasn't been updated for 4.5 months? Maybe not the best example. And I still think you should use as few automated tools as possible where flashing is concerned (Goo/ROM Manager).
It can be easy to wipe the wrong partition in CWM, if you are careless or illiterate. In the 6 months that I've used it (nearly every day), I have never once wiped the wrong partition, or my entire device. Never had a backup that wouldn't restore.
I like some of what TWRP offers. But I still experience showstopping bugs with it on my device. At this time, the devs are unable to track down the cause of the problems.
Aerowinder said:
The statement is not false. I think FreeGS3 hasn't been updated for 4.5 months? Maybe not the best example. And I still think you should use as few automated tools as possible where flashing is concerned (Goo/ROM Manager).
It can be easy to wipe the wrong partition in CWM, if you are careless or illiterate. In the 6 months that I've used it (nearly every day), I have never once wiped the wrong partition, or my entire device. Never had a backup that wouldn't restore.
I like some of what TWRP offers. But I still experience showstopping bugs with it on my device. At this time, the devs are unable to track down the cause of the problems.
Click to expand...
Click to collapse
Don't get me wrong, I've used CWM on many devices for years and even have a premium license for ROM Manager but I've seen a number of ROMs explicitly say not to use CWM, FreeGS3 was just the first that came to mind. I don't flash often because quite frankly, I have no problems with Wicked v8 and see no reason to switch to anything else.
And I am neither careless nor illiterate but I have accidentally borked things using CWM before in the past (it was a modified CWM Touch recovery) and I was not happy.
I think most of the complaints about CWM these days though come from CWM Touch, not regular CWM. Sorry TWRP has issues for you.
OK, so I'm getting a new issue, I changed to AOKP and I had problems with the ROM saying I needed to wipe data, I did, the issue persisted for few reboots, now apps won't install, and for some reason the /data folder still displays apps from my previous ROM ugh I don't know what's happening
Oh and for some reason the app exchange service kept force closing
Sent from my Nexus 7 using xda premium
eggydrums said:
OK, so I'm getting a new issue, I changed to AOKP and I had problems with the ROM saying I needed to wipe data, I did, the issue persisted for few reboots, now apps won't install, and for some reason the /data folder still displays apps from my previous ROM ugh I don't know what's happening
Oh and for some reason the app exchange service kept force closing
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Which recovery? Try erasing data, cache, and system three times each and reinstalling the ROM... If that doesn't work you might consider doing a back up of everything internally stored on your phone and then wiping the internal storage entirely and starting over.
EtherealRemnant said:
Which recovery? Try erasing data, cache, and system three times each and reinstalling the ROM... If that doesn't work you might consider doing a back up of everything internally stored on your phone and then wiping the internal storage entirely and starting over.
Click to expand...
Click to collapse
I tried. I think for some reason, the recovery isn't wiping data, even though it says so. I'm using twrp
Managed to install apps through the play website, still no go with the play store app though
Sent from my Nexus 7 using xda premium
eggydrums said:
I tried. I think for some reason, the recovery isn't wiping data, even though it says so. I'm using twrp
Managed to install apps through the play website, still no go with the play store app though
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hmmm... Have you tried doing it through CWM? Its starting to sound like your partitions are messed up.
EtherealRemnant said:
Hmmm... Have you tried doing it through CWM? Its starting to sound like your partitions are messed up.
Click to expand...
Click to collapse
I think that's a possibility I just tried through clockwork, and it's all good now but exchange service fcs here and there
Sent from my Nexus 7 using xda premium
eggydrums said:
I think that's a possibility I just tried through clockwork, and it's all good now but exchange service fcs here and there
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Did you fix permissions?
EtherealRemnant said:
Did you fix permissions?
Click to expand...
Click to collapse
I tried while I was in twrp, it failed, something about a an error "failed to chmod data/data/ email.apk" (not exactly like that)
Sent from my Nexus 7 using xda premium
Related
Ok I'm really irritated right about now. I am unable to flash any custom ROMS on my phone. Actually let me rephrase, I can flash them but many things do not work. I have tried Wicked, FreeGS3 and CapROM. They all have the same issues. Let me explain.
Once the ROM is booted I get odd string of numbers and TXT in the status bar, (goes away, think nothing of it)
Root not avail/accessible by root apps.
Home button does not work
Play store missing
standard Google login prompt at first boot is missing, it never asks me to login
Using CWM 5.8.4.5 Touch Recovery
TMO GS3 Rooted with Odin no trip method
I don't get it. I am i just stuck using stock ROM? If anyone can help I would love you forever.
are you clearing /cache and dalvik-cache before you reboot to the custom rom?
mrmako777 said:
are you clearing /cache and dalvik-cache before you reboot to the custom rom?
Click to expand...
Click to collapse
If you mean clearing those after the install (in recovery completes) then no. Basically after the install I just reboot. Obviously clear and reset everything before I install though.
hd2Raz said:
Ok I'm really irritated right about now. I am unable to flash any custom ROMS on my phone. Actually let me rephrase, I can flash them but many things do not work. I have tried Wicked, FreeGS3 and CapROM. They all have the same issues. Let me explain.
Once the ROM is booted I get odd string of numbers and TXT in the status bar, (goes away, think nothing of it)
Root not avail/accessible by root apps.
Home button does not work
Play store missing
standard Google login prompt at first boot is missing, it never asks me to login
Using CWM 5.8.4.5 Touch Recovery
TMO GS3 Rooted with Odin no trip method
I don't get it. I am i just stuck using stock ROM? If anyone can help I would love you forever.
Click to expand...
Click to collapse
Touch recovery might be your problem
Sent from my SGH-T999 using Tapatalk 2
horr1blek1tten said:
Touch recovery might be your problem
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Really? A recovery can cause these kinds of issues. Haven't heard of that before. Any other thoughts? What recovery are you using?
Try TWRP 2.2.1.1
hd2Raz said:
Really? A recovery can cause these kinds of issues. Haven't heard of that before. Any other thoughts? What recovery are you using?
Click to expand...
Click to collapse
Yeah I've heard touch recovery has its problems so I don't use it. Try using the recovery rom manager gives you.
Sent from my SGH-T999 using Tapatalk 2
horr1blek1tten said:
Yeah I've heard touch recovery has its problems so I don't use it. Try using the recovery rom manager gives you.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I use TWRP and have no problems.
Do a Factory reset, wipe cache, wipe dalvik cache, fix permissions.
If that doesn't work, flash stock and reroot and try again.
I use touch recovery 5.8.4.7 and flashed it with adb. I've flashed almost everything. Cyanogenmod and every other ROM. NEVER had a problem with an instalation. Or even lost IMEI. I think people specifically aren't reading over OP's and figuring out what's safest for their devices and end up with these kind of results. Just my input.
Sent from my SGH-T999 using xda premium
Use mskips tool for our phones. It does everything you can image and then some. I have been using his tools since the HD2 and no issues to date.
The odd string of numbers that flashes upon boot in the status bar sounds like it's just identifying your external sd card. Totally normal.
OK so nothing worked. TWRP did the same thing. Tried diff ROM, same thing. I flashed back to 100% stock, unrooted ROM. Wiped the phone in the standard Android recovery. Then I rooted again, installed TWRP and flashed my ROM of choice and voila. Everything works. Problem solved. Thanks all for the inputs.
Hi, So when I tried to open up twrp recovery, it wouldnt open....it would just stay at the logo and blink every now.and then....So I used oden and installed cwm over twrp and it was fine....I didnt like cwm so I went back to twrp..... it works fine and I can do everything EXCEPT some files are inaccessible and every time I flash something,it works but also gives me the error measages in the image I posted... does anyone know how to fix this?
Sent from my SPH-L710 using xda premium
razzack3000 said:
Hi, So when I tried to open up twrp recovery, it wouldnt open....it would just stay at the logo and blink every now.and then....So I used oden and installed cwm over twrp and it was fine....I didnt like cwm so I went back to twrp..... it works fine and I can do everything EXCEPT some files are inaccessible and every time I flash something,it works but also gives me the error measages in the image I posted... does anyone know how to fix this.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Maybe try installing twrp from goo manager while connected to WiFi to ensure a good download
Sent from my SPH-L710 using Xparent Skyblue Tapatalk 2
I had the same exact problem a couple days ago. I fixed it by going Into goo manager and re flashing a new TWRP. I did it on Mobile Data, worked fine!
Sent from my SPH-L710 using Tapatalk 2
Go back to 2.3.3.0. Search for the flashables ones. Since 2.4.2.1 TWRP have a lot of issues.
Sent from my SPH-L710
I see a lot of people complaining about TWRP related issues with various versions of this recovery.
Is there any reason people don't talk about CWM around here? I've been using different versions of cwm touch and twrp ... And I'm honestly pretty happy with cwm.
Why does it appear that people avoid talking about cwm? ... If indeed it works as well as it seems to me that it does?
One reason is that a lot of people think it's better and recommend it to others. I used cwm on my old evo and was going to when I got my s3, but most people and roms were recommending twrp. I've been using it and have tried out cwm as well. For me, at least it hasn't been problematic, but I don't download them through the goo manager. As I feel like I have less control over what I'm getting (I don't even know what version I'm getting until after I download it). That, and I just don't trust the phone to download without errors even when on Wi-Fi.
Just my two cents.
Sent from my SPH-L710 using xda app-developers app
I just actually switched to cwm a couple days ago because twrp had been giving me backup and restore problems.. everything twrp can do cwm does also, and it seems to be faster backing up and restoring also, but that might just be placebo... devs recommend twrp because that is what their Rom/kernel/mod was tested with... 99% of the time cwm will work just fine also
SPRINT GS3 FAQ
It might be that people are ignorant about cwm just like people are about androids
Sent from my SPH-L710 using xda premium
razzack3000 said:
It might be that people are ignorant about cwm just like people are about androids
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Actually, having used both, I think TWRP had been the better of the two because of the ease of naming your nandroids and the fact that backups in TWRP don't take up so much space as the CWM backups do. Have you seem the crazy Blobs folder in CWM? I like backing stuff up to the PC, but the CWM backups made that process extremely painful. I don't know what happened to make TWRP so unreliable recently, but I just noticed a newer version is out: 2.5.0.0
Sent from my SPH-L710 using Tapatalk 2
DurhamHusker said:
I see a lot of people complaining about TWRP related issues with various versions of this recovery.
Is there any reason people don't talk about CWM around here? I've been using different versions of cwm touch and twrp ... And I'm honestly pretty happy with cwm.
Why does it appear that people avoid talking about cwm? ... If indeed it works as well as it seems to me that it does?
Click to expand...
Click to collapse
There's nothing bad about CWM, but is 2013 and you can't rename your nands which is very important(not necesary) in a phone which date as 1970. Also the touch version looks like a '90 recovery.
But if you want a issues free TWRP go back to 2.3.3.0.
Sent from my SPH-L710
I did that... Now it only recognizes my ext sd card and the 0 folder in my internal storage that I clear out a while ago
Sent from my SPH-L710 using xda premium
topherk said:
One reason is that a lot of people think it's better and recommend it to others. I used cwm on my old evo and was going to when I got my s3, but most people and roms were recommending twrp. I've been using it and have tried out cwm as well. For me, at least it hasn't been problematic, but I don't download them through the goo manager. As I feel like I have less control over what I'm getting (I don't even know what version I'm getting until after I download it). That, and I just don't trust the phone to download without errors even when on Wi-Fi.
Just my two cents.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you update from goo manager, a pop up will tell you what version you are about to install beforehand. Also the webpage that it takes you to in order to start the auto download also states the name of the .IMG which also indicates version. I know what you mean about trusting downloads from the phone though. I personally think that is the reason a lot of people have issues with twrp. I've always updated to the latest twrp and flash almost daily, but have never had to switch versions because of bugs. All versions have ran perfect for me.
razzack3000 said:
It might be that people are ignorant about cwm just like people are about androids
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I've used both for quite a while. I used to only use cwm for the longest but decided to try out twrp because of those ridiculous blobs! What's with that? So I decided to try twrp and I've stayed because of all the little features like a warnings before you wipe things you shouldn't, option to flash more than one zip at once, option to clear cache and dalvik right after flashing, etc... Plus there are some pretty major features that get overlooked. Like the built in file browser. I installed miui once and it created a folder I could not delete and keep deleted. Every time I would reboot, it would come back. Twrp file browser deleted it and kept it deleted. The only thing I don't like about twrp is the system date and time being way off.
Edit: Lol. I've edited like 5 times because I keep wanting to add more info. Also, twrp doesn't take ages to fix permissions. As long as cwm takes, I can just do it manually
Sent from my SPH-L710 using Xparent Skyblue Tapatalk 2
I've been on 2.4.0 and 2.4.4, and only had to do backups but haven't tried to restore yet, so after hearing all the war stories, I went back to 2.3.1.
UPDATE: I just upgraded from 2.3.1 to 2.5.0, performed wipes, a backup and a restore and all went perfectly smooth. The only issue was the time was 2 hours behind what it should have been for US central, so I selected 2 hours ahead and chose military time (my preference) and I'm happy.
Where did you get 2.5.5?i only found 2.5.0
Sent from my SPH-L710 using xda premium
oops, I mean't 2.5.0
I flashed an AOSP Rom (SuperNexus) on my LGOG. Now when I try to flash a Stock (ZVB) based ROM, my phone reboots every time data connects. I tried Stock Rooted and Lifeless. The ROM's will flash onto my phone, but I can't get any data.
I tried installing LGNPST, but every time I connect my phone and open the LGNPST software I get a message that LG USB/Parallel dongle is not detected. I flashed back to Super Nex and my connection is fine.
And I am re-flashing, not restoring a backup. I ran a backup in TWRP before I flashed Super Nex so that I could get back to my Stock setup, but TWRP can't see anything to restore.
Ugh
Androidawg said:
I flashed an AOSP Rom (SuperNexus) on my LGOG. Now when I try to flash a Stock (ZVB) based ROM, my phone reboots every time data connects. I tried Stock Rooted and Lifeless. The ROM's will flash onto my phone, but I can't get any data.
I tried installing LGNPST, but every time I connect my phone and open the LGNPST software I get a message that LG USB/Parallel dongle is not detected. I flashed back to Super Nex and my connection is fine.
And I am re-flashing, not restoring a backup. I ran a backup in TWRP before I flashed Super Nex so that I could get back to my Stock setup, but TWRP can't see anything to restore.
Ugh
Click to expand...
Click to collapse
sounds like you're having similar issues as bmp7777, have you made any changes to your storage? as in the whole sdcard0 stuff? are your backups stored in sdcard0 ? when you flash a aosp rom it changes the way your storage is set up make sure you put your important stuff on sdcard0
Sent from my GT-P3113 using xda premium
Androidawg said:
I flashed an AOSP Rom (SuperNexus) on my LGOG. Now when I try to flash a Stock (ZVB) based ROM, my phone reboots every time data connects. I tried Stock Rooted and Lifeless. The ROM's will flash onto my phone, but I can't get any data.
I tried installing LGNPST, but every time I connect my phone and open the LGNPST software I get a message that LG USB/Parallel dongle is not detected. I flashed back to Super Nex and my connection is fine.
And I am re-flashing, not restoring a backup. I ran a backup in TWRP before I flashed Super Nex so that I could get back to my Stock setup, but TWRP can't see anything to restore.
Ugh
Click to expand...
Click to collapse
spleef said:
sounds like you're having similar issues as bmp7777, have you made any changes to your storage? as in the whole sdcard0 stuff? are your backups stored in sdcard0 ? when you flash a aosp rom it changes the way your storage is set up make sure you put your important stuff on sdcard0
Sent from my GT-P3113 using xda premium
Click to expand...
Click to collapse
Why not just completely erase data? Including data media? That will solve all problems.
Sent from my LG-LS970 using xda app-developers app
sharkboy0901 said:
Why not just completely erase data? Including data media? That will solve all problems.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Good idea. I'll give that a run.
sharkboy0901 said:
Why not just completely erase data? Including data media? That will solve all problems.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Didn't want to suggest a complete erase If it could be avoided... so was basing my response on a minimal damage scenario... Lol,
spleef said:
Didn't want to suggest a complete erase If it could be avoided... so was basing my response on a minimal damage scenario... Lol,
Click to expand...
Click to collapse
Hope I didn't come across as rude, wasn't my intention, just thought up the quickest way I knew would solve it
Sent from my LG-LS970 using xda app-developers app
This happened to me a couple months ago.
Easy solution:
Go to TWRP -> Wipe -> Advanced -> make sure you wipe all four options data, dalvik, cache, and system.
When you factory reset you only wiped data, dalvik, and cache. You forgot to wipe system, then you can go back to flashing normally.
Dont worry this wont wipe your SDcard.
Well I ****ed up. I formatted the data partition. I am now hard bricked. No recovery, no boot, nothing. glad I purchased that insurance.
sharkboy0901 said:
Hope I didn't come across as rude, wasn't my intention, just thought up the quickest way I knew would solve it
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Nah not at all bud just explaining why I went the route I did
Androidawg said:
Well I ****ed up. I formatted the data partition. I am now hard bricked. No recovery, no boot, nothing. glad I purchased that insurance.
Click to expand...
Click to collapse
Are you actually hard bricked because at this point normally I'm pretty sure you could just LGNPST back to stock? I mean I've wiped everything before to rule out dirty flashing related bugs on ROMs and I don't think TWRP actually touches any of the really critical low-level files.
Androidawg said:
Well I ****ed up. I formatted the data partition. I am now hard bricked. No recovery, no boot, nothing. glad I purchased that insurance.
Click to expand...
Click to collapse
Yeah hop on irc lgpnst that sucker and follow their instructions to the letter you'll be back in no time
spleef said:
Yeah hop on irc lgpnst that sucker and follow their instructions to the letter you'll be back in no time
Click to expand...
Click to collapse
I was on irc earlier and the mega download was unavailable. I'll check it again tomorrow.
gentlemenace said:
Are you actually hard bricked because at this point normally I'm pretty sure you could just LGNPST back to stock? I mean I've wiped everything before to rule out dirty flashing related bugs on ROMs and I don't think TWRP actually touches any of the really critical low-level files.
Click to expand...
Click to collapse
Worse than I've done before. Whatever I did I got black screen no matter what volume rocker power button combo I use. I have lgnpst installed on my computer but it doesn't recognize that I have my phone plugged in. Not sure what to do with that. Everything worked well when I rooted.
Sent from my Amazon Kindle Fire using xda app-developers app
Androidawg said:
Worse than I've done before. Whatever I did I got black screen no matter what volume rocker power button combo I use. I have lgnpst installed on my computer but it doesn't recognize that I have my phone plugged in. Not sure what to do with that. Everything worked well when I rooted.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
I sent you a pm so we can talk on gtalk/hangouts.
Sent from my LG-LS970 using xda app-developers app
I had the same issue with LGNPST. The solution is very simple. Uninstall LGNPDT completely from your computer. Go into start-computer-c drive and delete folders labeled LG electronics off of there and inside program files. Then reinstall LGNPST but right click the .exe file and select install as administrator. This will solve your issue and flash back to stock. Make sure you follow the normal process of selecting the .dll and .bin files.
Let me know if this helped.
Sent from my LG-LS970 using xda premium
Well i took it back to best buy and they rapid exchanged it. So I'll get a new one in 3 to 5 days. Back on the galaxy nexus for now.
Sent from my Galaxy Nexus using xda app-developers app
If TWRP is asking for a password and not booting do this: Re odin recovery twrp 2.4.4.0, wipe ALL data, odin twrp 2.6.1.0 back on to the device, reboot recovery, re-wipe data, flash desired COMPATIBLE rom.
To sum up what I found, new encryption added to 4.0+ of android encrypts user and important file partitions, updating recovery basically screws that all up. Your device has no way of accessing those files without the encryption key which was never explicitly made, its just a background feature to help protect your data.
I know this isnt much but atleast some people wont have to search around as much.
Now I cant take any credit for this, I also couldnt really find any user that took credit for it either.
Update: Something about gapps is the catalyst for this issue. After I flash gapps i get 15 mins of solid system performance, after that I start to get app download errors. The device will continue to function normally with snag and hiccups but after rebooting it goes right back to bootlock and asking for a P/W in TWRP. And of course I find a couple thread talking about this fix after, sorry for the redundancy I guess.
Can any confirm that Gapps may be causing this? Or better yet, what is actually causing this?
Jataadroid said:
If TWRP is asking for a password and not booting do this: Re odin recovery twrp 2.4.4.0, wipe ALL data, odin twrp 2.6.1.0 back on to the device, reboot recovery, re-wipe data, flash desired COMPATIBLE rom.
To sum up what I found, new encryption added to 4.0+ of android encrypts user and important file partitions, updating recovery basically screws that all up. Your device has no way of accessing those files without the encryption key which was never explicitly made, its just a background feature to help protect your data.
I know this isnt much but atleast some people wont have to search around as much.
Now I cant take any credit for this, I also couldnt really find any user that took credit for it either.
Update: Something about gapps is the catalyst for this issue. After I flash gapps i get 15 mins of solid system performance, after that I start to get app download errors. The device will continue to function normally with snag and hiccups but after rebooting it goes right back to bootlock and asking for a P/W in TWRP. And of course I find a couple thread talking about this fix after, sorry for the redundancy I guess.
Can any confirm that Gapps may be causing this? Or better yet, what is actually causing this?
Click to expand...
Click to collapse
im seeing people popping on on my phones forums (note 2) getting this message....and def not gapps...i have latest 4.3 gapps for weeks now and never seen this message
What rom you using?
PA 3.99 I have been running solid for 12 hrs now but I haven't rebooted since the last time I had to redo this process. It does fix it though.
All my apps have been installing and functioning fine. One thing I did different is I didn't flash BMS kernel. I havent checked the other threads reporting this issue but does any one know if they were using BMS?
Sent from my SPH-L710 using xda app-developers app
Jataadroid said:
PA 3.99 I have been running solid for 12 hrs now but I haven't rebooted since the last time I had to redo this process. It does fix it though.
All my apps have been installing and functioning fine. One thing I did different is I didn't flash BMS kernel. I havent checked the other threads reporting this issue but does any one know if they were using BMS?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Now I dont have TWRP asking for a password but PA_3.99 is stuck at the splash screen with the yellow sub. No longer an encryption issue it seems but now a new one entirely. At this point it exceeds my nooby knowledge of android and im stuck waiting for a kind soul to assist.
So please anybody have any idea? Or any idea how to define the issue better so i can get some help, it seems kernel or recovery related.
Is there a bootloader Im supposed to flash for 4.3? Im at a loss entirely.
Pls&thx
Just flash clockwork. Done
Sent from my SPH-L710 using xda app-developers app
I had the same problem, just once though. I booted into my ROM and all I needed to do was reinstall TWRP through Goomanager, then everything worked out fine. I updated from 2.6.0 to 2.6.1 at that point, so maybe that fixed my TWRP password problem. I did it about two weeks ago, so far no recovery issues. I used TWRP pretty intensely about a week ago to update to 4.3 and all went according to plan.
Shoot...I odin'd twrp 2.6.1.0 so many times I thought my phone would literally die. I didn't come from 2.6.0.1 ( not sure if that's the right) but instead several versions back.
Sent from my SPH-L710 using xda app-developers app
It wouldn't be a bad idea to implement a recovery password
Sent from my Nexus 5 using Tapatalk
alvintimothyjr said:
It wouldn't be a bad idea to implement a recovery password
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It's kind of already been done.
Really...info?
Sent from my Nexus 5 using Tapatalk
Ok, I've tried several different roms and I always back up. I've used Oudhs, Clocworkmod and TWRP. No matter which one I back up with I never have any luck on restore. They all seem to restore ok but I get stuck in boot loops everytime. Factory reset doesn't help. Wiping caches don't help. This is just beginning to really drive me nuts. I don't really mind having to reinstall everything but jeez I just wish I knew what the deal was. I never had trouble on my Motorola Defy or my Galaxy S2 but I sure can't seem to get anywhere on the S4
It happens sometimes to me. When I get stuck after restoring nandroid, I get back into recovery and reflash the kernel and it boots the device. I am using philz recovery and its been working great.
Sent from my SM-N900T using Tapatalk
Have you tried PhilzTouch yet?
Alex9090 said:
It happens sometimes to me. When I get stuck after restoring nandroid, I get back into recovery and reflash the kernel and it boots the device. I am using philz recovery and its been working great.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
lalec said:
Have you tried PhilzTouch yet?
Click to expand...
Click to collapse
Never used philz and never thought of just reflashing the kernel. I may try that though. Now to find the kernel. I should mention that I end up using Odin to reflash stock. Then I root and then custom recovery. That boots fine and for the most part all I'm ever doing is trying to restore a 4.4 rom I backed up.
Flashing a kernel worked. lol my phone doesn't think it's the stock kernel but it booted at least.
I do find this interesting. I would think when you restore a nandroid backup that it would restore the kernel that was with the rom you are restoring. I guess this isn't the case?
Using the latest clockwork has always worked for me.
Sent from my SGH-M919 using XDA Premium 4 mobile app
I use ROM manager premium, as well.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
I use ROM manager premium, as well.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've had Rom Manager Premium since my Defy days. I'm a firm believer in it. I was just surprised I would have to reflash a kernel after restoring a rom.
Corwinder said:
Ok, I've tried several different roms and I always back up. I've used Oudhs, Clocworkmod and TWRP. No matter which one I back up with I never have any luck on restore. They all seem to restore ok but I get stuck in boot loops everytime. Factory reset doesn't help. Wiping caches don't help. This is just beginning to really drive me nuts. I don't really mind having to reinstall everything but jeez I just wish I knew what the deal was. I never had trouble on my Motorola Defy or my Galaxy S2 but I sure can't seem to get anywhere on the S4
Click to expand...
Click to collapse
I use OUDHs Touch recovery v1.0.3.3 in conjunction with Rom Manager and I have NEVER had that problem. Also, when I use Rom Manager to "Back Up Current Rom" I can NAME the backup file, and it goes into the recovery and uses the filename I have already typed in and it's a seamless operation. Even using restore via Rom Manager works seamlessly and it has NEVER balked on me.
The only time I had a problem was once using My Backup Pro and trying to do an on-line system backup. MMS, SMS, Call Log has always been absolutely perfect! No out of sequence messages, and all the pictures are restored correctly too!
Aloha and Good Luck!
BTW, I am on a Stock 4.2.2 with the latest M919UVUFNB4 (modem.bin) Flashed for the radio and it's reception qualities are better than it's ever been before!