I just flashed a 802d stock ROM through TWRP 2.7 (AutoRec). I started out by wiping dalvik cache, cache and data. I then pressed Install and found the zip and installed that. After it was done, I did a dalvik + cache wipe again just to be safe (It asked if I wanted and I complied). Rebooted into system. It was quite buggy to begin with, so I wanted to try re-flashing, but it looks like my custom recovery has disappeared. I assume my root access went with it.
Everytime I try to get into recovery. It doesn't show the TWRP recovery, but merely ask if I want to factory reset my phone.
Currently, I'm downloading a clean kdz of the 802d ROM (it's taking a while) and aim to start all over with rooting and installing custom recovery and re-installing apps, but if anyone has a different solution, it would be most welcome. I'm quite the noob here. I thought TWRP would be fool-proof and would therefore allow me to restore a backup at any time. But currently, that does not appear to be the case.
Please do prove me wrong
Depends on what custom rom you were installing.
Trixanity said:
I just flashed a 802d stock ROM through TWRP 2.7 (AutoRec). I started out by wiping dalvik cache, cache and data. I then pressed Install and found the zip and installed that. After it was done, I did a dalvik + cache wipe again just to be safe (It asked if I wanted and I complied). Rebooted into system. It was quite buggy to begin with, so I wanted to try re-flashing, but it looks like my custom recovery has disappeared. I assume my root access went with it.
Everytime I try to get into recovery. It doesn't show the TWRP recovery, but merely ask if I want to factory reset my phone.
Currently, I'm downloading a clean kdz of the 802d ROM (it's taking a while) and aim to start all over with rooting and installing custom recovery and re-installing apps, but if anyone has a different solution, it would be most welcome. I'm quite the noob here. I thought TWRP would be fool-proof and would therefore allow me to restore a backup at any time. But currently, that does not appear to be the case.
Please do prove me wrong
Click to expand...
Click to collapse
Ok first if you really do have custom recovery in the factory reset screen clicking the power button three times will boot you into recovery, if you can boot into the Rom then download a root checker app to check if you still have root
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
Ok first if you really do have custom recovery in the factory reset screen clicking the power button three times will boot you into recovery, if you can boot into the Rom then download a root checker app to check if you still have root
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2736854 <- this is the ROM I flashed. It's a stock ROM containing the latest d firmware for the D802.
I just checked for root access - it's not there anymore. I will try to boot into recovery now through the method you suggested. I'll edit my post with the results.
Edit: Your method worked My recovery is there. Great! I thought it would boot straight into recovery, so the factory reset option mislead me. Now, I have to ask: did I do anything wrong in my flashing? For example. In the Mount section, only Data and Cache is mounted. Should system be mounted or is it irrelavant? Is there anything in particular I need to do in Wipe? I merely pressed Advanced Wipe and seleceted Dalvik Cache, Data and Cache and swiped to wipe. That's it.
Trixanity said:
http://forum.xda-developers.com/showthread.php?t=2736854 <- this is the ROM I flashed. It's a stock ROM containing the latest d firmware for the D802.
I just checked for root access - it's not there anymore. I will try to boot into recovery now through the method you suggested. I'll edit my post with the results.
Click to expand...
Click to collapse
well if you would have noticed in the install process it states to flash supersu after flashing the rom
XxZombiePikachu said:
well if you would have noticed in the install process it states to flash supersu after flashing the rom
Click to expand...
Click to collapse
Yeah, I did read that. This might sound stupid, but I figured that the listed SuperSU update was meant for people with an older version of SuperSU as in making sure to have the latest version of SuperSU, since I already had the latest version, I neglected to do that step. My bad. I will copy the zip in question to my phone and try re-flash both zips and see what happens. At least I have my backups to fall back on.
Another dumb question if you will. Since I didn't wipe any of my data. My apps are still present in the file system, but they are not installed nor do they have market links. Is there a way to install them or should I try to recover them through Titanium Backup? Or is it easier to simply wipe the data as well and use Titanium Backup to restore my apps?
Trixanity said:
Another dumb question if you will. Since I didn't wipe any of my data. My apps are still present in the file system, but they are not installed nor do they have market links. Is there a way to install them or should I try to recover them through Titanium Backup? Or is it easier to simply wipe the data as well and use Titanium Backup to restore my apps?
Click to expand...
Click to collapse
I think you should wipe and restore from tibu since there isn't a guarantee that redownloading your apps from the playstore will keep there old data
Thank you so much for taking your time to answer my questions. The second flash seemed succesful, but it didn't fix my biggest reason for flashing the ROM in the first place: the hissing audio bug. So I'll just try to do a restore of my latest backup and I'll make do with my temporary fix that actually works.
While it may seem to that I have wasted everyone's time, I think I've learned some valuable lessons, so I don't think it was entirely a bad thing
Hopefully, my restore will be succesful
Trixanity said:
Thank you so much for taking your time to answer my questions. The second flash seemed succesful, but it didn't fix my biggest reason for flashing the ROM in the first place: the hissing audio bug. So I'll just try to do a restore of my latest backup and I'll make do with my temporary fix that actually works.
While it may seem to that I have wasted everyone's time, I think I've learned some valuable lessons, so I don't think it was entirely a bad thing
Hopefully, my restore will be succesful
Click to expand...
Click to collapse
just in case since you don't mention the fix, I know the kk audio bug has a fix with g2tweaksbox over in the faq of first post it explains what needs to be done
XxZombiePikachu said:
just in case since you don't mention the fix, I know the kk audio bug has a fix with g2tweaksbox over in the faq of first post it explains what needs to be done
Click to expand...
Click to collapse
I did try that fix. It didn't remove the hiss entirely for me. Maybe removed 50% of the hiss, but I've heard of it working 100% for a lot of people. I've been using the ELT > Audio Loopback test from the hidden menu. It removes the hiss by about 99%. Only annoying thing is that I need to do it on every reboot which is why I wanted a more permanent fix.
Seems like my restore has caused a bootloop. Everything went accordingly, except the installation of SuperSU afterwards. Kept saying it failed to copy to the system folder despite system being mounted. The bootloop started when trying to boot into system after restore + failed SuperSU installation.
Edit: Fixed the SuperSU failure to install by wiping dalvik etc. but bootloop persists. I somewhat assume this is because the restore function doesn't work when the current ROM is different from the ROM the backup was made with? The backup was made with D802 20b firmware and the current ROM which is the one I flashed was the D802 20d firmware. Am I on to something?
Trixanity said:
I did try that fix. It didn't remove the hiss entirely for me. Maybe removed 50% of the hiss, but I've heard of it working 100% for a lot of people. I've been using the ELT > Audio Loopback test from the hidden menu. It removes the hiss by about 99%. Only annoying thing is that I need to do it on every reboot which is why I wanted a more permanent fix.
Seems like my restore has caused a bootloop. Everything went accordingly, except the installation of SuperSU afterwards. Kept saying it failed to copy to the system folder despite system being mounted. The bootloop started when trying to boot into system after restore + failed SuperSU installation.
Edit: Fixed the SuperSU failure to install by wiping dalvik etc. but bootloop persists. I somewhat assume this is because the restore function doesn't work when the current ROM is different from the ROM the backup was made with? The backup was made with D802 20b firmware and the current ROM which is the one I flashed was the D802 20d firmware. Am I on to something?
Click to expand...
Click to collapse
A backup restore should always work whether different versions or not, are you able to get into download mode?have you tried kdz to stock?
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
A backup restore should always work whether different versions or not, are you able to get into download mode?have you tried kdz to stock?
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
I just fixed it by going into recovery and flashing the D802 20d firmware again. It'll do for now. Honestly don't know why the restore from backup didn't work. Either the backup was corrupt or I've done something wrong.
I did restore my apps (so far) flawlessly and the rom does appear to perform similarly to my older firmware. Plus there's added features such as knock code so it's not all bad.
I do have a D802 20d kdz firmware available on my computer in case I want to go completely stock and/or start over. But I'll give this one a try over the next few days and see whether I'll keep this.
Trixanity said:
I just fixed it by going into recovery and flashing the D802 20d firmware again. It'll do for now. Honestly don't know why the restore from backup didn't work. Either the backup was corrupt or I've done something wrong.
I did restore my apps (so far) flawlessly and the rom does appear to perform similarly to my older firmware. Plus there's added features such as knock code so it's not all bad.
I do have a D802 20d kdz firmware available on my computer in case I want to go completely stock and/or start over. But I'll give this one a try over the next few days and see whether I'll keep this.
Click to expand...
Click to collapse
yea I'm still waiting for that knock code update on my g2, times like these make you hate being with carriers
Related
I killed my phone while trying to install a ROM, so I re-flashed a bunch of stuff and it's back. Some problems though - it has Superuser installed still. Even though I did a factory reset, Superuser is still there. When I try to re-root it, it goes through the whole things and gives me "error: device not found". I don't understand why it finds my device in the beginning of the process, but doesn't find it at the end.
1. How do I delete Superuser for good so I can start fresh, and re-root again?
2. What do I do now?
Could you list everything you've done in chronological order starting with the first thing you flashed and ending with the last thing you flashed?
Sent from my oc'd Voodoo Fascinate using XDA App
AlgorithmX said:
Could you list everything you've done in chronological order starting with the first thing you flashed and ending with the last thing you flashed?
Sent from my oc'd Voodoo Fascinate using XDA App
Click to expand...
Click to collapse
1. I was playing nice with the clean, magic roms, etc, everything was cool.
2. Then I tried to install Blue Breeze the same way and it froze the phone (later found out it was the wrong way to do it).
3. Then I followed the restore to stock thread (flashed system, kernel, etc), and brought it back to life, and Superuser was still installed. I tried to uninstall the root, and that doesn't work either.
So right now I can't uninstall Superuser, OR re-root it again because it just keeps giving me the error: device not found.
If you go into settings and check your internal phone memory...what is it saying you have?
Can you download apps from the market?
I got this same error when the voodoo bit me and gave me the 0.00 internal memory issue.
Try either flashing your stock+root CWM backup (you made one, right?) or the nandroid "stock" image in the forum through CWM.
(Wipe data/cache on reboot in stock recovery and then from the "privacy" menu of your stock settings do a "factory reset".)
PhoenixPath said:
If you go into settings and check your internal phone memory...what is it saying you have?
Can you download apps from the market?
I got this same error when the voodoo bit me and gave me the 0.00 internal memory issue.
Try either flashing your stock+root CWM backup (you made one, right?) or the nandroid "stock" image in the forum through CWM.
(Wipe data/cache on reboot in stock recovery and then from the "privacy" menu of your stock settings do a "factory reset".)
Click to expand...
Click to collapse
1. I have 1.50 GB free.
2. Yes, I can download apps from the market.
3. Where is the stock image located?
4. I did that factory reset like 3 times.
Have you attempted this?
http://forum.xda-developers.com/showthread.php?t=782204
Visit the first thread in this forum for info on stock recovery (including where to find the "stock" nandroid recovery image).
I take it you did not create a CWM recovery backup immediately after rooting your phone?
Let me give you the timeline. A few days ago I rooted the device using the method outlined in this video. I verified my root status with Root Checker and my device was indeed successfully rooted. I installed BusyBox (basic) and TitaniumBackup Pro. Made a backup of my user apps+data to the external SD. I then downloaded Goomanager and used it to install the latest version of TWRP.
All of this was successful. I went into TWRP and created a NAND backup. I backed up: Boot, System, and Data. I did not back up EFS, Preload, Cache, or Recovery.
I performed a wipe and format of user data. Flashed to SlimBean, had some issues. Wiped. Flashed CM10.1. Again, some issues. I decided I'm going to wait a while for these roms to stabilize a bit before I try using any of them on a regular basis. I wiped and restored my original NAND backup of my stock rooted ROM. The restore appeared to go fine. I don't know if this will have anything to do with anything but I went ahead and ran a PRL and Profile update. The device was functioning okay until...
I noticed that the time was off. The lockscreen time was correct but the time in the upper right status bar was stuck at about an hour before. I decided I'd just try restarting the device to see if that fixed anything. Well when I did it wouldn't boot. I'd get stuck on the first Samsung Galaxy S4 logo screen. Took the battery out, waited, put it back in, restarted. Still... stuck on the logo screen. I tried booting into recovery (Vol. Up + Power). The black SGS4 logo would come up with a tiny blue notification in the upper left corner (Recovery Boot). Then the device would restart and get stuck at the SGS4 logo screen again.
Eventually I was able to get it to boot to TWRP (maybe I was just holding the power button too long?)
I wiped. It failed. I tried again. It worked. I recovered my CM10.1 setup and it's been working "okay" on CM10.1 ever since.
I want to get back to my stock rooted rom but I want to understand what happened first.
Anyone? Please?
Stu_Gots said:
Anyone? Please?
Click to expand...
Click to collapse
What version of TWRP were you on? If it was 2.5.0.3 then there's your culprit. That version of TWRP is known to have issues. You need to flash version 2.5.0.2 found here.......http://forum.xda-developers.com/showthread.php?t=2277480. Scroll down to install Alternate recovery and download the 2.5.0.2 .img file.
Once you've downloaded the file, go to your Goo Manager folder and delete the file there. Then paste the file you downloaded from the above link into that same folder. After that, open Goo Manager and go to Install Recovery Script. It should see the file you have in your folder and then download it from their server. Make SURE it says you are downloading 2.5.0.2. Once Goo does its thing, reboot into Recovery and make sure you're running the 2.5.0.2 version of TWRP. Now you can flash all you want because it will function properly. I would first download a stock rom and clear out any skeletons in the closet. Then go into TWRP and wipe EVERYTHING. This includes data, dalvik cache, cache, system and then factory reset as well 3 times each. MAKE SURE you don't delete the internal or external sd cards. Flash the stock rom, set it up how you wish, make a nand of that file( Include EFS and Preload because it can't hurt to be safe) and then flash whatever you like. You should be good to go.
---------- Post added at 01:20 PM ---------- Previous post was at 01:17 PM ----------
Stu_Gots said:
Anyone? Please?
Click to expand...
Click to collapse
Another question I have is what version of software/firmware are you on? Go to Settings/More/About Phone and check what your software and baseband versions are? If its MDC, then rooting via MotoChopper was a good method to use. If it says MDL, that could also be the reason why the phone was acting so quirky. There is a new method to rooting if you are on MDL and it's also found in Mudavo's thread found here...http://forum.xda-developers.com/showthread.php?t=2277480
For the record. I was using the phone stock rooted for a week or so without any problems. I hadn't had any issues until after restoring the backup I made in TWRP. When I wiped prior to installing SlimBean/CM10.1 I did the standard auto-wipe AND I wiped data
Oh yeah. To answer your questions.
TWRP Version: 2.5.0.2
Software/Baseband versions: L720VPUAMDL
Earlier today I just tried wiping (default TWRP 2.5.0.2). Then restoring the backup again. This was so I could get you the information on what software/baseband version I was on. When the restore completed I went to reboot. The phone stuck on the SGS4 logo screen. I then rebooted in recovery and wiped as before and then I wiped data. The phone was then able to boot into the stock rooted rom. I have so far noticed the times being out of sync from the lock screen and the status bar. I reset the phone again. Stuck at SGS4 logo again.
My trouble getting back into TWRP was my own fault. I was holding the buttons down too long. I can get back into TWRP no problem.
So. What are my options at this point? I would like to be on the latest stock everything... with root and stock wireless tether enabled. The way I was. If I can't restore my backup then I'm going to have to reflash the stock rom. I can't seem to find a comprehensive index of information. Every time I think I've got something figured out I stumble on new bits of information.
Stu_Gots said:
For the record. I was using the phone stock rooted for a week or so without any problems. I hadn't had any issues until after restoring the backup I made in TWRP. When I wiped prior to installing SlimBean/CM10.1 I did the standard auto-wipe AND I wiped data
Oh yeah. To answer your questions.
TWRP Version: 2.5.0.2
Software/Baseband versions: L720VPUAMDL
Earlier today I just tried wiping (default TWRP 2.5.0.2). Then restoring the backup again. This was so I could get you the information on what software/baseband version I was on. When the restore completed I went to reboot. The phone stuck on the SGS4 logo screen. I then rebooted in recovery and wiped as before and then I wiped data. The phone was then able to boot into the stock rooted rom. I have so far noticed the times being out of sync from the lock screen and the status bar. I reset the phone again. Stuck at SGS4 logo again.
My trouble getting back into TWRP was my own fault. I was holding the buttons down too long. I can get back into TWRP no problem.
So. What are my options at this point? I would like to be on the latest stock everything... with root and stock wireless tether enabled. The way I was. If I can't restore my backup then I'm going to have to reflash the stock rom. I can't seem to find a comprehensive index of information. Every time I think I've got something figured out I stumble on new bits of information.
Click to expand...
Click to collapse
Honestly, at this point, you need to unroot and reroot again using the method in Mudavo's post. You used the wrong method to root with motochopper. Motochopper was only for the MDC version. That could be why you are having the issues that you are. That's all I can suggest at this point. Start with a clean slate and try it again. Trust me you aren't the only one to do this. I've done it a few times myself. It sucks but at least you know you did everything right. You're going to have to flash a stock MDC rom that came shipped with the phone via Odin. Then take the OTA to update your phone to MDL and then just follow Mudavo's post to root the proper way when you're on the MDL version.
What about the TWRP recovery I have installed? Am I going to have to deal with that in some way?
What are the advantages of Odin over TWRP? I'm not trying to question your judgment btw. I'm legit curious because I've only ever used TWRP to
Flash roms.
Sorry for all the dumb questions.
Btw . While I was waiting for your reply I tried trouble shooting a bit myself. To see if I could fix my own problem. I found a thread with MDL stock rooted and a bunch of firmware and kernel files. I flashed to it in TWRP and it's working reasonably well so far. I'm still dtf for other methods if mine is somehow flawed.
My method didn't work. When I restarted from TWRP (after no other issues) the phone for stuck.
The phone was restarted several times and booted fine. It wasn't until I restarted into TWRP then and then back into normal boot that I had issues
this time. So I'm going to do what you suggested. I just have a couple questions.
If my rom/recovery is corrupted how do I fix my problem. I would need a working rom AND recovery to flash stock rom. I'm not sure where to start since everything is all messed up.
Thank you so much for your help. You're the best!
You should do a Full Odin restore to Stock and start from scratch if you continue to have issues.
http://forum.xda-developers.com/showthread.php?t=2270065
You can also try this thread to ensure a full wipe before flash
http://forum.xda-developers.com/showthread.php?t=2277261
gharlane00 said:
You should do a Full Odin restore to Stock and start from scratch if you continue to have issues.
http://forum.xda-developers.com/showthread.php?t=2270065
You can also try this thread to ensure a full wipe before flash
http://forum.xda-developers.com/showthread.php?t=2277261
Click to expand...
Click to collapse
Installed Mobile ODIN Pro from the play store for $5... I hope that's the right Odin!
Stu_Gots said:
Installed Mobile ODIN Pro from the play store for $5... I hope that's the right Odin!
Click to expand...
Click to collapse
download Odin 1.85 or 3.07 on your PC don't use mobile version for something like this
Sent from my SPH-L720 using xda premium
Do I need to flash the stock kernal too? Will this eliminate my TWRP recovery installation as well?
If you odin back to stock it also has the kernel and stock recovery this will start you all over. Also of it doesnt boot past galaxy s4 screen then boot into recovery and wipe data after you odin back.
Sent from my SPH-L720 using xda premium
devoureddreams said:
If you odin back to stock it also has the kernel and stock recovery this will start you all over. Also of it doesnt boot past galaxy s4 screen then boot into recovery and wipe data after you odin back.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Alright... so another problem. I need the latest Samsung USB driver right? Unfortunately...
1.5.25.0 as linked to in this thread cannot be downloaded because uploaded.com or whatever says I've exceeded my allowance. Trouble is... I haven't downloaded anything from them ever. I have this problem all the time because of my ISP (Satellite Internet).
Is there a rehost? Do these drivers not install themselves automatically when the device is plugged into the PC?
http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Sent from my SPH-L720 using xda premium
I'm so freaking frustrated by this whole process. It looks like by all accounts there are a dozen different ways to do everything and I just know i'm going to mess it up.
I'm following the directions in this video.
http://www.youtube.com/watch?v=ZD5CHlrPQJQ&feature=youtu.be
When I extract the file I downloaded I get an MD5 file not an ODIN file.
Stu_Gots said:
I'm so freaking frustrated by this whole process. It looks like by all accounts there are a dozen different ways to do everything and I just know i'm going to mess it up.
I'm following the directions in this video.
http://www.youtube.com/watch?v=ZD5CHlrPQJQ&feature=youtu.be
When I extract the file I downloaded I get an MD5 file not an ODIN file.
Click to expand...
Click to collapse
Follow this tutorial here
http://www.sxtpdevelopers.com/showthread.php?p=2599
Sent from my SPH-L720 using xda premium
Alright guys. I got it done a while back. Phone is back to normal stock.
Perusing the internet I found this video.
http://www.youtube.com/watch?v=s_hXUJ-u-cw
As it happens I linked to the wrong video in my OP. The method in that video is exactly what I did to root in the first place. The proper way. I installed TWRP from GooManager.
So if I rooted correctly and I installed TWRP correctly what do you suppose caused my problem? I want to root and install custom recovery again!
If I root using the CF-Auto-Root method will I then be able to install custom recovery in goomanager or does custom recovery need to be installed in some other special way?
Stu_Gots said:
If I root using the CF-Auto-Root method will I then be able to install custom recovery in goomanager or does custom recovery need to be installed in some other special way?
Click to expand...
Click to collapse
thats all there is to it.
I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?
Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.
jcxmej said:
I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?
Click to expand...
Click to collapse
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.
RikRong said:
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.
Click to expand...
Click to collapse
Like I said on first post Im using TWRP now. Previously I was using safestrap. I removed it and installed TRWP. Anyways thanks.
PantherVT said:
Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.
Click to expand...
Click to collapse
Thanks man. I will upgrade TWRP or reinstall it first. Thanks for that tip. Will post again if it doesnt work.
Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.
jcxmej said:
Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.
Click to expand...
Click to collapse
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)
jco23 said:
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)
Click to expand...
Click to collapse
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.
jcxmej said:
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.
Click to expand...
Click to collapse
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"
jco23 said:
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"
Click to expand...
Click to collapse
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?
jcxmej said:
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?
Click to expand...
Click to collapse
which ROM are you trying to install?
jco23 said:
which ROM are you trying to install?
Click to expand...
Click to collapse
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.
jcxmej said:
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.
Click to expand...
Click to collapse
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.
jco23 said:
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.
Click to expand...
Click to collapse
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.
jcxmej said:
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.
Click to expand...
Click to collapse
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692
jco23 said:
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692
Click to expand...
Click to collapse
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.
jcxmej said:
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.
Click to expand...
Click to collapse
I don't think changing the kernel will do it.... I suspect the issue is with your recoveries - will respond in other thread....
This isn't my very first time with flashing/rooting/etc. but I'm not that adept with it.
Got my S4 2 days ago but managed to get time today to work on it. I rooted successfully and everything was running perfect. I flashed over the newest Beanstalk ROM w/ gapps and it ran fine the first time it ran.
I can't get passed the Samsung Galaxy S4 boot logo every time I try to reboot the phone though...
If I wipe the cache/dalvik and reflash it still doesn't boot passed logo.
If I wipe the cache/dalvik and then wipe data (including the internal SD card, completely wiping it clean), flashing the ROM will work the first time it runs; once I reboot or just power it off then power it back on, stuck at Galaxy S4 logo... I let the ROM run first time through, input only what is needed to get to the home screen (google account/wifi setup/phone name/etc.), then I've tried rebooting it, shutting it down and powering it back up, letting everything update and waiting half an hour and restarting it... all have the same result, stuck at boot logo
I'm using TWRP, I have a recovery for stock but I don't want to use stock.
If anyone can help me out I'd appreciate it.
Try flashing a different compatible kernel.
ObrienDave said:
Try flashing a different compatible kernel.
Click to expand...
Click to collapse
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Spazzzin said:
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Click to expand...
Click to collapse
Use twrp 2.5.0.2 because if your using 2.6 its bringing problems. Also report this to their thread for better help
Sent from my SPH-L720 using xda app-developers app
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
ObrienDave said:
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
Click to expand...
Click to collapse
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Just flash it by odin by the link provided above. Make sure to use the tar file v 2.5.0.2
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Spazzzin said:
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Click to expand...
Click to collapse
By the way can you provide the steps and which files you flashing. Also redownload everything could be a bad download. Make sure to download them in computer and transfer them to your sd card
Sent from my SPH-L720 using xda app-developers app
I did a fresh install of the LiquidSmooth ROM and it's not hanging at boot logo whenever I reboot, and everything is working well. I suppose I'll stick with this for a while.
For my steps trying Beanstalk:
Boot into recovery (TWRP 2.6.0.0)
Factory reset;wipe cache/dalvik
Format Data
Factory reset;wipe cache/dalvik
Install ROM + Gapps
Wipe cache/dalvik
Reboot
I then tried doing that exact process, after letting it boot once I rebooted into recovery and flashed KT Kernel and wiped then rebooted and it hung at boot logo.
I did it again but I installed ROM + Gapps + Kernel then wiped then rebooted and it still hung at boot logo.
I'll download and prepare a new install of Beanstalk and give it another try tomorrow. I'll make sure to backup Liquid in case I want to switch back.
Thanks again for the help!
Glad it's working out for you.
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Spazzzin said:
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Click to expand...
Click to collapse
Not really unless the rom dev for some reason doesn't recommend using a certain one. Kernels will act differently for everyone even on the same device with the same rom. Just need to flash them and find out which one works the best for you (battery life, overheating, smoothness, etc).
Always have a backup handy just in case something doesn't work right.
This guide will help you install the unofficial builds of CyanogenMod 12 and other Lollipop builds.
Disclaimer: These builds are not official and are very much pre-alpha builds. While many people have little issues, you may have issues yourself and without some knowledge of ROMing, you may end up bricking your device.
I and the people who built the ROMs are not responsible for you bricking your device or losing data.
Installation
Backup: If you do not backup your device, you will lose everything!
Install Titanium Backup and choose Backup all user apps from the backup batch actions
Titanium Backup requires that you are rooted to work. If you are not rooted, use a tool such as Helium.
Be sure to copy your backup to your computer just in-case the data in the "SD Card" partition gets deleted. Use Android File Transfer or ADB to do so.
Unlock Bootloader: If you did not root your device, you likely have not unlocked your bootloader and you will need to unlock your device using the guide here.
Recovery: You need to also make sure you have a custom recovery such as the TWRP recovery which an installation guide is also available here.
Downloads: If you have done all of the above, you are ready to begin the installation process.
First you need to download all these files to your device.
Google Apps from https://s.basketbuild.com/gapps
SuperSu from http://download.chainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip (optional for root)
Next you need to get a copy of CM12, you can do so in the following 2 ways.
Download a lollipop ROM. Choose from one of these known to work ROMs, build your own ROM, or find a ROM from someone else you trust (if you find another good ROM, let me know).
https://www.reddit.com/r/oneplus/comments/2moqig/cm12_nonscheduled_builds_discussionupdate_thread/
http://forum.xda-developers.com/oneplus-one/development/rom-cm12-daily-builds-gapps-t2937887
Build your own copy by following this guide http://forum.xda-developers.com/oneplus-one/development/guide-building-lollipop-oneplus-one-t2947949
Flashing: This guide is using TWRP. If you have a guide for using ClockworkMod or another custom recovery, let me know.
1. Reboot into recovery, ether by adb reboot recovery in terminal or by holding down the volume down button as you reboot.
2. Go into wipe, and swipe to factory reset. This erases your data but should not erase the "SD Card" partition.
3. Go back home if it doesn't automatically do so.
4. Go into reboot then choose Recovery.
5. After reboot, choose install and select the Lollipop ROM you downloaded.
6. Swipe to confirm flash.
7. After successful flash, go back home and back into install and flash both Google Apps and SuperSu.
8. Reboot device to system and you should have Lollipop.
Restoring Backup: Now that you're on Lollipop, you will want all your app settings and apps back.
If you used the Titanium Backup option, install Titanium Backup, and choose Restore missing apps with data.
Common Issues
Slow Boot: The solution people have used was to remove GPS and location services. This means you will not be able to use any map program to navigate anywhere.
Using ES File Explorer, go to /System/priv-app and remove com.Qualcomm.location
NFC and Bluetooth: There was some earlier ROMs that had these issues, go to a more recent ROM.
Enable on screen keys and disable hardware keys: Follow this guide http://forum.xda-developers.com/showthread.php?t=2032117 and flash this to disable the backlight on the buttons https://drive.google.com/file/d/0Byxnqyony5AybHFOeWJhMmczS09pd0JNaGFwWHFybHlYRmNJ/view credit @sd65
MultiROM: MultiROM does not support Lollipop as of right now. There has been success in installing Lollipop then using CM11(S) as a secondary ROM.
I will update this as I find other common issues.
Restore CM11S (Stock firmware)
Make sure you backup using the instructions above.
Download original firmware from https://cyngn.com/products/oneplusone/ and extract it.
In terminal, cd into the extracted folder.
On your phone, unplug it from your computer and hold down volume up and the power button until you see the fastboot icon, then connect to your computer and run the commands in the terminal window.
Code:
fastboot flash boot boot.img
fastboot flash system system.img
If you wish to flash the original recovery:
Code:
fastboot flash recovery recovery.img
You can also try following this guide if you trust their download.
Once you are restored, so long as you didn't flash userdata, you should still have your backup from Titanium Backup in the "SD Card".
This looks great thanks for the post!
I already know the answer but just asking to be sure JUST in case I'm wrong, if I do a NANDroid backup before wiping and flashing the Lollipop ROM just to try it out, will I be able to go back to CM11S just by restoring the backup?
Mbennett156 said:
This looks great thanks for the post!
I already know the answer but just asking to be sure JUST in case I'm wrong, if I do a NANDroid backup before wiping and flashing the Lollipop ROM just to try it out, will I be able to go back to CM11S just by restoring the backup?
Click to expand...
Click to collapse
I don't know much about NANDroid myself, but reading http://forum.xda-developers.com/wiki/NANDroid seems like it's just a clone of the flash in a file and can be restored using custom recoveries. So I would assume so, but not sure.
Mbennett156 said:
This looks great thanks for the post!
I already know the answer but just asking to be sure JUST in case I'm wrong, if I do a NANDroid backup before wiping and flashing the Lollipop ROM just to try it out, will I be able to go back to CM11S just by restoring the backup?
Click to expand...
Click to collapse
Yes you can. I've been switching between Lollipop and Paranoid Android for 2 days now with NAndroid backups
hyuratzu said:
Yes you can. I've been switching between Lollipop and Paranoid Android for 2 days now with NAndroid backups
Click to expand...
Click to collapse
Great thanks
I tried to use MultiROM instead of this guide (of course, setting the 11s as secondary and pushing a custom AK kernel on the Lollipop ROM) but sadly it doesn't boot.
Elvecio said:
I tried to use MultiROM instead of this guide (of course, setting the 11s as secondary and pushing a custom AK kernel on the Lollipop ROM) but sadly it doesn't boot.
Click to expand...
Click to collapse
Try searching this thread for MultiROM and see what others have done http://forum.xda-developers.com/one...s-rumors-talk-l-t2829974/page146#post56750165
Another stupid question, but if I follow this guide to install lollipop alpha, when I decide to go back to stock can I just flash a brand new stock image for the latest CM11S version through twrp? Instead of using fastboot?
Sent via quantum entanglement, focused through my OnePlus One.
Why do i need too download and install google apps?
beastlykings said:
Another stupid question, but if I follow this guide to install lollipop alpha, when I decide to go back to stock can I just flash a brand new stock image for the latest CM11S version through twrp? Instead of using fastboot?
Sent via quantum entanglement, focused through my OnePlus One.
Click to expand...
Click to collapse
I'm not sure about installing with TWRP, it won't hurt to try. Just follow my instructions for installing Lollipop and apply it to CM11S
roktheman97 said:
Why do i need too download and install google apps?
Click to expand...
Click to collapse
If you don't want the Google Apps (Includes Google Play), then you don't have to install it. I have heard people who didn't install it say that they had some weird issues such as when you put your screen to sleep it reboots or something.
GRMrGecko said:
If you don't want the Google Apps (Includes Google Play), then you don't have to install it. I have heard people who didn't install it say that they had some weird issues such as when you put your screen to sleep it reboots or something.
Click to expand...
Click to collapse
I just installed android 5 and can't find Google play. Now I know why. Can I install it now or should I install it together with android 5. I'm asking if it matters. (Kind of a noob got opo in august and this is third time I'm doing this.)
---------- Post added at 08:13 PM ---------- Previous post was at 07:41 PM ----------
OK I have Google apps now, I'm in the step with backuping the apps, the moment I pressed backup a error pop-uped that it has problems with parsing? Also seems like it's taking forever backuping my apps..
roktheman97 said:
I just installed android 5 and can't find Google play. Now I know why. Can I install it now or should I install it together with android 5. I'm asking if it matters. (Kind of a noob got opo in august and this is third time I'm doing this.)
Click to expand...
Click to collapse
It doesn't matter if you install it later. I did the very same thing.
roktheman97 said:
OK I have Google apps now, I'm in the step with backuping the apps, the moment I pressed backup a error pop-uped that it has problems with parsing? Also seems like it's taking forever backuping my apps..
Click to expand...
Click to collapse
Do you mean restoring? You are suppose to backup before installing Lollipop. If you accidentally mess up the process of restoring, you will have to start again by going into the app switcher and quitting Titanium Backup.
GRMrGecko said:
Do you mean restoring? You are suppose to backup before installing Lollipop. If you accidentally mess up the process of restoring, you will have to start again by going into the app switcher and quitting Titanium Backup.
Click to expand...
Click to collapse
I backed up all the users app as instructed, now I wanted to restore all apps and its stuck with simple flashlight. As soon as I clicked restore it pop-ed up something about problems with parsing.
roktheman97 said:
I backed up all the users app as instructed, now I wanted to restore all apps and its stuck with simple flashlight. As soon as I clicked restore it pop-ed up something about problems with parsing.
Click to expand...
Click to collapse
Try reading things here http://www.titaniumtrack.com/kb/titanium-backup-kb/titanium-backup-troubleshooting.html
GRMrGecko said:
Try reading things here http://www.titaniumtrack.com/kb/titanium-backup-kb/titanium-backup-troubleshooting.html
Click to expand...
Click to collapse
Thank you very much for all information, I find this very helpful already. I think I will reboot the phone into recovery boot my previous OS and make another backup with newer version. Thanks again.
Thanks for this informative guide. The "Restore CM11S (Stock firmware)" is useful too.
roktheman97 said:
I backed up all the users app as instructed, now I wanted to restore all apps and its stuck with simple flashlight. As soon as I clicked restore it pop-ed up something about problems with parsing.
Click to expand...
Click to collapse
That's a system app, you can't restore those, you're only meant to backup/restore user apps.
Transmitted via Bacon
timmaaa said:
That's a system app, you can't restore those, you're only meant to backup/restore user apps.
Transmitted via Bacon
Click to expand...
Click to collapse
Flashlight from Google play.