Recently, I have been introduced to Android Rooting and I have successfully rooted my phone with Towelroot. My friend installed Cyanogenmod 11 on his Galaxy S3 the other day and I have been having many problems doing the process myself. I have ripped xdadevelopers to pieces trying to find a solution, but nothing has ever been simple enough, well really efficient enough to fix my problem.
I have ROM Manager installed on my device and the latest CWM Recovery and when I get to the "Recovery" mode it does not give me all the options a normal "Recovery" screen would give me. I can not backup my current stock rom because there is no option. In doing this I accidentally wiped my phone and had no way to recover, so I lost a lot of temporary things, very frustrating.
Basically what I need to know is how to get CWM Recovery to work on my device, etc. Also I forgot to mention before that FreeGee messes up too. It says something about "loki" or something. I am sick of trying several methods that fail in the end. If you can tell me how to get CWM Recovery to work on my phone. I do have an SD Card and my phone is rooted. Please help me! I apologize if all the information is not present, but if you need to know anything specific I would be more than happy to answer your question!
RyeM8 said:
Recently, I have been introduced to Android Rooting and I have successfully rooted my phone with Towelroot. My friend installed Cyanogenmod 11 on his Galaxy S3 the other day and I have been having many problems doing the process myself. I have ripped xdadevelopers to pieces trying to find a solution, but nothing has ever been simple enough, well really efficient enough to fix my problem.
I have ROM Manager installed on my device and the latest CWM Recovery and when I get to the "Recovery" mode it does not give me all the options a normal "Recovery" screen would give me. I can not backup my current stock rom because there is no option. In doing this I accidentally wiped my phone and had no way to recover, so I lost a lot of temporary things, very frustrating.
Basically what I need to know is how to get CWM Recovery to work on my device, etc. Also I forgot to mention before that FreeGee messes up too. It says something about "loki" or something. I am sick of trying several methods that fail in the end. If you can tell me how to get CWM Recovery to work on my phone. I do have an SD Card and my phone is rooted. Please help me! I apologize if all the information is not present, but if you need to know anything specific I would be more than happy to answer your question!
Click to expand...
Click to collapse
Have you tried installing the recovery from G.Pro Recovery first? Freegee will not work for me, giving me similar errors, until I first do that. See the to the Bountyman G3 v4.x thread under 'Optimus G Pro Android Development' for more info. Works for me every time (though I choose TWRP; friggin' *hate* CWM).
Hello people, I don't know if there's anyone out there who still uses the G pro but here I am still using it. Okay so I have been stuck with this problem for almost 2 months now, I rooted my phone amd everything was great till the time I tried to install a custom recovery using freegee. It did not work. In the beginning, it said my phone wasn't compatible because of some loki thing but I still went ahead with it anyway.
So after I installed the 2nd-init recovery, after I rebooted, things went bad. My phone was okay, sort of. The main problem was that my memory card stopped working and my phone began changing settings itself like turning the wifi off, screen on changes to 15 seconds and it keeps doing this again and again and I have to keep changing the settings.
Can somebody please help me fix this issue as I really can't take this anymore. I cant use my phone properly any longer. Oh and my phone is still under warranty but m scared to give it in as I feel they might find out it was rooted. Is there anyway I can get back to the old recovery and remove this 2nd init file? i can locate the file bt im scared to delete it as i wouldnt wanna wreck my phone any further.
Any help would be appreciated.
Sent from my LG-E988 using XDA Free mobile app
Restore to stock first. 2nd-init recoveries are very hard to remove without extensive knowledges on linux shell.
They you can re-root the phone. If your phone supports the 'LG Support Tool', then use it. It will recover your phone to stock in clean and nice GUI.
I tried the lg support tool. It just keeps stopping.
I'm not really good at this. I restored to stock by performing a factory reset but Im just lost at this point. Can I give it in for servicing because its still under warranty?
Sent from my LG-E988 using XDA Free mobile app
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
I don't know about lg support tool, but the best thing will be use lg flash tool, there are many thread on how to flash the img files. You can flash the recovery that way. Or you can flash your device back to stock rom 4.12 which is the best starting point.
Hi guys.
I have tried to take a logcat of my phone when it bootloops upon restarting after install. Here is the code I used:
Code:
adb -d logcat>C:\adb>Bootloop.txt
However, the output file is empty.
My issue is that I can install any stock-based ROM, but not any custom ROMs (CM or AOSP). When I try to install custom ROMs (CM or AOSP) it always bootloops.
So I am trying to trace the phone when it bootloops. My PC does recognise the phone, as I get the message "This device can perform faster if blah, blah, blah".
Is there another way I can trace the boot up process to find out what errors its throwing out?
Thx in advance.
theKramer
I don't know if USB Debugging is turned on my default on custom ROMs - it isn't on stock ROMs, so logcat wouldn't work via ADB until that would be enabled, which if the custom ROM bootloops from the very start, obviously you wouldn't be able to turn it on.
Have you re-wiped Cache, Dalvik/ART and Data? Flash the appropriate Bootstack? Try moving what you want to keep from your internal storage, eject your MicroSD card/keep it ejected and wipe/reformat your internal storage from TWRP. You can always turn the phone off from TWRP after flashing the custom ROM/Bootstack and then eject the card. Last but not least, try flashing the TOT to start fresh, reroot with the Stump app, put TWRP on with TWRP Manager, and flash the custom ROM and Bootstack like that, although if you go back to stock again after that, I recommend flashing the TOT again before doing so, as some people have trouble with signal or mobile data coming from non-stock or international-stock based ROMs.
Edit: Just noticed you're on the D855, so I don't know the TOT situation there - I only know the VS985, but the advice still stands.
roirraW "edor" ehT said:
I don't know if USB Debugging is turned on my default on custom ROMs - it isn't on stock ROMs, so logcat wouldn't work via ADB until that would be enabled, which if the custom ROM bootloops from the very start, obviously you wouldn't be able to turn it on.
Have you re-wiped Cache, Dalvik/ART and Data? Flash the appropriate Bootstack? Try moving what you want to keep from your internal storage, eject your MicroSD card/keep it ejected and wipe/reformat your internal storage from TWRP. You can always turn the phone off from TWRP after flashing the custom ROM/Bootstack and then eject the card. Last but not least, try flashing the TOT to start fresh, reroot with the Stump app, put TWRP on with TWRP Manager, and flash the custom ROM and Bootstack like that, although if you go back to stock again after that, I recommend flashing the TOT again before doing so, as some people have trouble with signal or mobile data coming from non-stock or international-stock based ROMs.
Edit: Just noticed you're on the D855, so I don't know the TOT situation there - I only know the VS985, but the advice still stands.
Click to expand...
Click to collapse
Hi @roirraW "edor" ehT
This is a long ongoing issue. Basically it surfaced after flashing back to stock as I was having random reboots and thought it might be custom ROM related, but after flashing stock I still had the reboot issues, so figured out battery was toast so changed that and reboot issues were resolved.
But since flashing stock MM on my D855, I cannot get any custom ROM (CM/AOSP) to boot on my ROM except Bumped 5.0.1 ROMs.
I can install any stock or stock-based ROM without any issue, however, custom, no go. The funny thing is that I was running custom ROMs on my phone for more than a year without issue. I could throw any custom ROM at it, and where other people might have issues, my phone would always run them flawlessly.
Not anymore
I have flashed stock Lollipop about 7 or 8 times (via LGUP and LG Flash Tool 2014) and stock KK about another 4 times, so I should have blown out any MM remnants at this stage.
The weird thing is that my phone doesnt boot up with stock based KK either (all of them just hang on bootup), but LP or MM is no issue. I am running LIMITLESS ROM v10.2 at the moment (based on v30a). I cannot remember if I tried v10b actually, I did so many of them..
I have rooted from LP each time, and it is always successful (I have used 3 or 4 different rooting methods) and TWRP is successfully bumped each time.
I have tried numerous versions of TWRP (2.6/2.8/3.0/3.0.2).
I have done a full wipes (cache/dalvik/data/system), even including a format data after and still no luck..
The reason I was asking about methods to get some kind of log info during bootup was so I could maybe get some info on why it doesnt boot custom ROMs..
theKramer said:
Hi @roirraW "edor" ehT
Click to expand...
Click to collapse
Hi! Argh. Sounds really frustrating! Bear with me since it sounds like you know what you're doing and again I have the VS985. Among the 100% stock unrooted you flashed, did you only flash KDZs or is there a TOT available and did you try that? The reason I ask is that TOTs flash more partitions than KDZs and can fix problems that KDZs and ROMs can't. I can personally attest to that but once I experienced it and asked an experienced developer, it became clear that's expected, and when I extracted the partitions out of the VS985 10B TOT and compared to the KDZ I indeed noticed one or two more partitions.
Again, don't mind me if I'm telling what you already know. The other thing is the Bootstack situation, although I haven't ever experienced a bootloop due to the wrong Bootstack, only non-working modem or dangerous combo of our Marshmallow sbl1 partition along with the BUMP-vulnerable 12B aboot (bootloader), necessary for TWRP and for root on Marshmallow. Reference this VS985 post if needed http://forum.xda-developers.com/showpost.php?p=63438031&postcount=2. I don't really expect that to be the issue and since you tried from a variety of stock ROM situations, I wouldn't have expected you to have an issue with every combo you tried.
Edit: actually, the remaining item is the MicroSD card. I know it sounds silly but it's happened. Try it without the card and see what happens. While you're at it, try with the SIM ejected too just for the heck of it, won't hurt to try.
Good luck! Hope you figure it out.
roirraW "edor" ehT said:
Hi! Argh. Sounds really frustrating! Bear with me since it sounds like you know what you're doing and again I have the VS985. Among the 100% stock unrooted you flashed, did you only flash KDZs or is there a TOT available and did you try that? The reason I ask is that TOTs flash more partitions than KDZs and can fix problems that KDZs and ROMs can't. I can personally attest to that but once I experienced it and asked an experienced developer, it became clear that's expected, and when I extracted the partitions out of the VS985 10B TOT and compared to the KDZ I indeed noticed one or two more partitions.
Again, don't mind me if I'm telling what you already know. The other thing is the Bootstack situation, although I haven't ever experienced a bootloop due to the wrong Bootstack, only non-working modem or dangerous combo of our Marshmallow sbl1 partition along with the BUMP-vulnerable 12B aboot (bootloader), necessary for TWRP and for root on Marshmallow. Reference this VS985 post if needed http://forum.xda-developers.com/showpost.php?p=63438031&postcount=2. I don't really expect that to be the issue and since you tried from a variety of stock ROM situations, I wouldn't have expected you to have an issue with every combo you tried.
Edit: actually, the remaining item is the MicroSD card. I know it sounds silly but it's happened. Try it without the card and see what happens. While you're at it, try with the SIM ejected too just for the heck of it, won't hurt to try.
Good luck! Hope you figure it out.
Click to expand...
Click to collapse
Hi.
I didnt know that about there being more partitions in TOT vs KDZ files actually..
I have tried flashing without SD card also already.. I haven't tried without sim card, so why not
Is there a specific reason you mentioned flashing v10b, by the way?
theKramer said:
Hi.
I didnt know that about there being more partitions in TOT vs KDZ files actually..
I have tried flashing without SD card also already.. I haven't tried without sim card, so why not
Is there a specific reason you mentioned flashing v10b, by the way?
Click to expand...
Click to collapse
In the case of the VS985, 10B is the first or earliest build we have, and we have a TOT of it, so I was just using it as an example. I've only ever noticed a leak of one TOT per variant of a device at the most, but if you have more than one available I would choose the earliest.
Mostly useless information to you, but the VS985 does have a 10B KDZ, but it's 10B_01, whereas the TOT is 10B_03. 10B_03 was the official release so it can get OTAs, and 10B_01 was a leak so it can't. From what I've seen, the sub-build _## is only available as part of the filename when you get a hold of the KDZ and TOT. 10B for the VS985 is also the easiest to root because we can just use the Stump app with its brute force option. For us, rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B. Both 10B and 12B are still KitKat. 23C and 24B 5.0.1 are rootable via PC/USB/adb script. As far as I remember, 35B 5.1.1 and definitely 46A through 48A 6.0 has no method of permanent root, only KingRoot on 35B through 47A which gives temporary and suspicious root.
roirraW "edor" ehT said:
In the case of the VS985, 10B is the first or earliest build we have, and we have a TOT of it, so I was just using it as an example. I've only ever noticed a leak of one TOT per variant of a device at the most, but if you have more than one available I would choose the earliest.
Mostly useless information to you, but the VS985 does have a 10B KDZ, but it's 10B_01, whereas the TOT is 10B_03. 10B_03 was the official release so it can get OTAs, and 10B_01 was a leak so it can't. From what I've seen, the sub-build _## is only available as part of the filename when you get a hold of the KDZ and TOT. 10B for the VS985 is also the easiest to root because we can just use the Stump app with its brute force option. For us, rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B. Both 10B and 12B are still KitKat. 23C and 24B 5.0.1 are rootable via PC/USB/adb script. As far as I remember, 35B 5.1.1 and definitely 46A through 48A 6.0 has no method of permanent root, only KingRoot on 35B through 47A which gives temporary and suspicious root.
Click to expand...
Click to collapse
So, I haven't actually flashed v10b as I have handed my phone in to a phone repair shop as I have been having a number of hardware issues such as wifi not working, high temperatures at the back of the phone and SIM card detection issues (most likely related to the phone heating up).
However, before I had handed it in to the shop, I flashed a custom kernel (Gabriel stock-based) on the stock ROM I was running at the time, and that reminded me that I have flashed Gabriel kernel on a number of different stock and stock-based ROMs, and if I flashed a stock-based custom kernel, I also got the same bootloop error.
So I was wondering if that might help in any way to pinpoint what is going on with my phone...
theKramer said:
However, before I had handed it in to the shop, I flashed a custom kernel (Gabriel stock-based) on the stock ROM I was running at the time, and that reminded me that I have flashed Gabriel kernel on a number of different stock and stock-based ROMs, and if I flashed a stock-based custom kernel, I also got the same bootloop error.
So I was wondering if that might help in any way to pinpoint what is going on with my phone...
Click to expand...
Click to collapse
I don't think that's specific enough to narrow things down any in this case, but doesn't hurt to note the info! Good luck with your phone!
roirraW "edor" ehT said:
I don't think that's specific enough to narrow things down any in this case, but doesn't hurt to note the info! Good luck with your phone!
Click to expand...
Click to collapse
So my feeling is that there is something up with my boot image, even though my phone is rooted and bumped and TWRP is bumped, there is something my phone doesnt like in AOSP/CM or modified stock-based kernels that is not visible in LG stock.
Is there any tool/script that I can run that would collect info on the boot process...
theKramer said:
So my feeling is that there is something up with my boot image, even though my phone is rooted and bumped and TWRP is bumped, there is something my phone doesnt like in AOSP/CM or modified stock-based kernels that is not visible in LG stock.
Is there any tool/script that I can run that would collect info on the boot process...
Click to expand...
Click to collapse
I'm not very knowledgeable about logs or experienced collecting or looking through them, but maybe collecting a logcat through adb (over USB) while booting would help? You'd have to have USB Debugging turned on, and make sure it stays on across reboots - there's a common issue that is easy to resolve where if USB Debugging doesn't stay on after you reboot, turn it on, plug it into a PC, manually switch the USB connection mode on the phone from MTP and PTP and back to MTP and then disconnect the cable, and it'll stay on then.
roirraW "edor" ehT said:
I'm not very knowledgeable about logs or experienced collecting or looking through them, but maybe collecting a logcat through adb (over USB) while booting would help? You'd have to have USB Debugging turned on, and make sure it stays on across reboots - there's a common issue that is easy to resolve where if USB Debugging doesn't stay on after you reboot, turn it on, plug it into a PC, manually switch the USB connection mode on the phone from MTP and PTP and back to MTP and then disconnect the cable, and it'll stay on then.
Click to expand...
Click to collapse
So, I was suggested the app Liveboot, which was created by Chainfire of SuperSU fame. This app outputs a log to the screen and to a log file on the device of all the calls that are made during bootup (with user selectable level of detail).
Running this app, I did two traces. One with just stock LG and the second after flashing a modified stock kernel..
The stock log is 21KB, the log from when I flashed the modified kernel is 904KB.
Liveboot Stock
Liveboot with kernel
This is not an issue with the modified kernel per se, but with some settings in modified kernels. Any way to pinpoint the offending code/parameter?
This is not directed at you "roirraW "edor" ehT", but to any and all that could help me to figure out what is going on..
theKramer said:
So, I was suggested the app Liveboot, which was created by Chainfire of SuperSU fame. This app outputs a log to the screen and to a log file on the device of all the calls that are made during bootup (with user selectable level of detail).
Click to expand...
Click to collapse
Just wanted to say thanks for a reminder about that app. I had even tested the app when it first came out and I somehow keep forgetting about it.
So I have isolated the issue to some kind of hardware issue.
If I leave my phone turned off for a while with battery out, I can get it to boot custom ROMs. I have tried with 2 different batteries, so its definitely the phone itself. If I reboot the phone once the phone has booted up, then it boot loops again, even if the phone is only booted for a few minutes.
I had to debick my phone a couple of months ago using the short circuit method (due to some stupidity on my part) and it seems that that has fried something in my phone.
Since I brought my phone back to life I have been having issues with Wifi and SD-card slot not working, plus lots of heat and terrible battery life.
I would love to know though what it is in custom ROMs/Kernels that causes my phone to bootloop.
It would be great if I could isolate that somehow.
Anybody have any ideas, by any chance?
So I've bricked my phone. And I can't make it work. Yesterday I finally had some time to thinker with the phone and decided to install Fulmics Rom 6.0. I had already downloaded it a while ago but first now had the time to install it. I made a post in the Fulmic's thread but with their new 6.5 fulmics just out, so my post got berried so quickly so I got no replies.
I started in TWRP with doing a backup, then a wipe and then started the install.
It seemed install was going fine, I even got the Fulmic's GUI midways and selected appropriate model, D855. I tried to keep things as vanilla as possible and chose to not uninstall anything and keep stock temperature throttle back.
But when the install completed I got one error: set_metadata_recursive: some changes failed
Phone wouldn't boot. I had however made a backup before I started and I was able to restore from backup from within TWRP.
Then phone booted and it seemed all was fine. But as I had my mind set on the Fulmics ROM I had one more go, just ti be sure I didn't mess up and chose something bad in the Fulmic install GUI. Also I did a wipe first, then I wiped the cache/dalvik as I once read that could make install easier. And result same as before. set_metadata_recursive: some changes failed.
Tried to reboot but I get flash screen with LG loge and powered by android on the bottom, and then when screen changes to only LG logo it gets stuck'd. No matter how long I wait, and I tried to wait for hours remembering wiping dalvik/cache makes boot take longer time. Stucked on the boot load. Notification light changes from green to blue. And the Lg logo is there.
Worst part is that now I can't even restore it to my backup from yesterday.
Here is my phone:
Lg G3 D855 16 GB 2 GB RAM
Android 6.0 stock LG update.
TWRP 3
Rooted
For now I would settle for a working phone. That is my main priority. Truth be told I got scared now and I don't know if I will take my chances putting a custom ROM onto the phone. After all my android 6 was working nicely, phone was rooted and adaway was working nicely. I guess I got greedy and wanted more
It would be very nice if people could take things very basic, like if I am to do certain things in TWRP don't assume I will understand unless you go into details. Been struggling for hours upon hours now and my mind is mush and concentration was lost a few hours ago. Yet I need to keep at it as I can't be without a working phone tomorrow. For instance in the TWRP under tab advanced > sideload what can I try there to make phone boot?
If I have left out any important for you to help pls just ask and I will reply as fast as possible. Any and all tips and pointers will be much obliged.
joppy said:
It would be very nice if people could take things very basic, like if I am to do certain things in TWRP don't assume I will understand unless you go into details. Been struggling for hours upon hours now and my mind is mush and concentration was lost a few hours ago. Yet I need to keep at it as I can't be without a working phone tomorrow. For instance in the TWRP under tab advanced > sideload what can I try there to make phone boot?
If I have left out any important for you to help pls just ask and I will reply as fast as possible. Any and all tips and pointers will be much obliged.
Click to expand...
Click to collapse
Downgrade to twrp 2.8 and flash again hope you are good too to go....
For me , if i have problem.
Replace sdcard , format data on twrp and flash .kdz (not after 30x.0426.kdz) , usually LGup can made download mode it self.
If can booting , make temporary root and get twrp.
Ok I had TWRP v2.8.7.0 laying around. I've used it before with success, so I know it works with my Lg G3.
But still not possible to boot.
I will try to read up on the .kdz as I never even heard of that before. Maybe if I am lucky that will save the day.
Hehe what do you know. TWRP v2.8.7.0 worked!
I dismissed it too fast, turned out it didn't get stuck'd on boot, boot just took a while because I had wiped everything.
Now I can see android is upgrading apps, and also when I think back to the first reboot with twrp v2.8 it was fulmics logo on the bottom part of the screen not android I guess my mind did not pay any attention as I was truly expecting to be stuck in boot loop this time too
Fingers crossed it is working now, I guess I didn't pay much attention when I tested twrp v2.8 and pointed to the fulmics ROM 6.0 and it seems it will work whoha
Finally I've got a working phone, and I also got Fulmics 6.0 as I sat out to get.
Don't know what went wrong or what caused the boot loop, but twrp v2.8 seemed to be the working solution.
IT seems everything works except I lost root. Which is fine for now, I will root another day.
Now I just need to use the dang phone
Deleted for your own safety
Btw, as the phone must be rooted to install custom ROM's it does seems strange that phone after installing Fulmics 6.0 appears to NOT have root, according to RootChecker. Could it be that the custom ROM is confusing RootChecker or did root somehow get revoked?
Is there a manual way I can check to see if phone is rooted? Cos there is, terminal
I took the chance tp get the latest KingRoot v4.9.6 over my previous v4.5.6. And run the APK.
Seems there must have been some issues with SuperSU, I had v2.54 and BETA v2.65. None of them kept root after install.
Found the latest stable that was superSU v2.78 and that fixed my issues.
TWRP ver 3.x messed my phone up too. Thought I had a good EFS backup, but when I needed to restore it, it didn't work. I will not be using ver 3.x again for a long time. Ended up losing my IMEI because of it.