Hello, I got Samsung J-7108 and I got stuck in bootloop after flashing Xposed Framework with flashfire... I am sure I downloaded the right version for my CPU, the latest one. I flashed the original firmware, but it doesn't work. I don't have a custom recovery, what can I do? Help, please.
Speeder12321 said:
Hello, I got Samsung J-7108 and I got stuck in bootloop after flashing Xposed Framework with flashfire... I am sure I downloaded the right version for my CPU, the latest one. I flashed the original firmware, but it doesn't work. I don't have a custom recovery, what can I do? Help, please.
Click to expand...
Click to collapse
Did you ever figure out how to fix this issue? Was very curious about this Flashfire.
Paul R
try to flash boot.bin for your phone ,, extract it from stock room and convert ti from bin to tar and flash it
Thank you for your replies. I had to do a factory reset, nothing else helped. So I tried it again, I flashed the Xposed V86 with flashfire, worked fine for two days, than the phone went to bootloop again. I guess I will not deal with xposed anymore, it is a good thing, but doesn't really work as it should.
Okay, so I have a update: Phone works fine for two days. I turn it on and everything seems fine, but... after two days of using it goes to bootloop again no matter what I do. I tried flashing original firmware, works fine for two days, than bootloop again, tried factory resetting, wiping cache and so on, still the same, works, but goes to bootloop every two days when I try to turn it on. Help, please.
Any ideas?
Try to flash the xposed uninstaller zip
messi2050 said:
Try to flash the xposed uninstaller zip
Click to expand...
Click to collapse
I did many times, never helped
Speeder12321 said:
I did many times, never helped
Click to expand...
Click to collapse
I think that u will need to flash twrp then wipe the system/data partitions and reflash stock rom ( note that this may break your phone )
I found out, that stock firmware works fine, but whenever I give it a root access, it stucks in bootloop after 2 days of using the phone... is there anything else I can try before wiping data partitions?
Speeder12321 said:
I found out, that stock firmware works fine, but whenever I give it a root access, it stucks in bootloop after 2 days of using the phone... is there anything else I can try before wiping data partitions?
Click to expand...
Click to collapse
which root method u are using
messi2050 said:
which root method u are using
Click to expand...
Click to collapse
I am using a pre-rooted firmware.
I guess that XPosed changed the values of some System files and uninstaller does no job in changing them back to how they were before. Question is: There's no custom recovery availible for Chinese model of J7, so is there a possibility to delete System using a Root file explorer? Which has access to System partition?
messi2050 said:
which root method u are using
Click to expand...
Click to collapse
When I do factory reset in recovery on rooted firmware, it works again, but like I said, just for two days? How is that even possible? Factory reset should delete everything including changes that xposed made, shouldn't it?
Speeder12321 said:
When I do factory reset in recovery on rooted firmware, it works again, but like I said, just for two days? How is that even possible? Factory reset should delete everything including changes that xposed made, shouldn't it?
Click to expand...
Click to collapse
Xposed modifies System, Factory reset does not affect system only Data.
Your issue isn't xposed.
You are probably receiving a security policy update. The policy update breaks earlier versions of supersu causing bootloops.
You need to flash supersu v2.78 SR1 with Flashfire then the correct Xposed version.
Supersu v2.78 will block the policy up date.
ashyx said:
Xposed modifies System, Factory reset does not affect system only Data.
Your issue isn't xposed.
You are probably receiving a security policy update. The policy update breaks earlier versions of supersu causing bootloops.
You need to flash supersu v2.78 SR1 with Flashfire then the correct Xposed version.
Supersu v2.78 will block the policy up date.
Click to expand...
Click to collapse
I don't think so, I used prerooted firmware for months and never had a single problem... everything started to go wrong after flashing xposed.. So how can be SuperSU a problem if it used to work fine before?
EDIT: And no, I didn't receive security policy update.
EDIT2: But thanks a lot for your advice, I will try to update SuperSU... Is it okay if I flash newer superSU with flashfire, when my current one is installed as a system app or do I need to do something before flashing the new one?
Speeder12321 said:
I don't think so, I used prerooted firmware for months and never had a single problem... everything started to go wrong after flashing xposed.. So how can be SuperSU a problem if it used to work fine before?
EDIT: And no, I didn't receive security policy update.
EDIT2: But thanks a lot for your advice, I will try to update SuperSU... Is it okay if I flash newer superSU with flashfire, when my current one is installed as a system app or do I need to do something before flashing the new one?
Click to expand...
Click to collapse
Use the uninstaller in SuperSU settings.
ashyx said:
Use the uninstaller in SuperSU settings.
Click to expand...
Click to collapse
It is installed as a system app, so I will need to do a full unroot. And if I do full unroot, I won't be able to flash the new one with flashfire, because it needs root access, what now ?
EDIT: Okay, I managed to update SuperSU to version 2.78 SR1, I will post an update if it fixed my issue, thanks
ashyx said:
Xposed modifies System, Factory reset does not affect system only Data.
Your issue isn't xposed.
You are probably receiving a security policy update. The policy update breaks earlier versions of supersu causing bootloops.
You need to flash supersu v2.78 SR1 with Flashfire then the correct Xposed version.
Supersu v2.78 will block the policy up date.
Click to expand...
Click to collapse
Thank you sooooooo so much, it fixed my issue
Related
Just updated my Nexus 5 using the OTA thread that went through fine,
I then proceeded to update SuperSU using the following link: http://download.chainfire.eu/supersu which was the update v1.99r3.
Using TWRP I flashed this and root is working for most apps i have tested: titanium, adblock, root explorer. So root is back.
However whenever I load up SuperSU I keep getting the following message: "The SU binary needs to be updated. Continue?"
So of course I have done this and let it use TWRP to flash. Let the phone boot up and upgrade the app as it needed. However on next load up of the app it asks to do the same yet again.
I feel as though I'm forgetting something as it's been a while since I've done this. ( use to live on flashing when i had my SII)
My Nexus is Stock ROM. CF-Auto Rooted. TWRP Recovery. Nothing else is modified.
Help would be appreciated, even though I don't go into supersu all that often anyways.
Cheers all.
What if you upgrade it using the "normal" method?
If I do a normal install i get the following:
Installation failed!
Please reboot and try again.
brichardson1991 said:
If I do a normal install i get the following:
Installation failed!
Please reboot and try again.
Click to expand...
Click to collapse
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?
rootSU said:
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?
Click to expand...
Click to collapse
How odd like I said my apps are all receiving their root permissions...
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
I don't have any other recoveries on my phone, so I wouldn't know about that last option.
brichardson1991 said:
How odd like I said my apps are all receiving their root permissions...
Click to expand...
Click to collapse
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Have you tried other binary download?
brichardson1991 said:
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
Click to expand...
Click to collapse
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
brichardson1991 said:
I don't have any other recoveries on my phone, so I wouldn't know about that last option.
Click to expand...
Click to collapse
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.
rootSU said:
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Click to expand...
Click to collapse
It does seem that way Titanium has backed up an app just now, adblock has updated and Nova is hiding the time on the first screen.
rootSU said:
Have you tried other binary download?
Click to expand...
Click to collapse
No, I shall give a older one a try.. Tried 1.97 as well and to no luck.....
rootSU said:
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
Click to expand...
Click to collapse
This failed to do anything just got the install failed again.
rootSU said:
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.
Click to expand...
Click to collapse
I assume this would override TWRP recovery?
brichardson1991 said:
I assume this would override TWRP recovery?
Click to expand...
Click to collapse
Yes it would. You can always flash back to twrp afterwards
rootSU said:
Yes it would. You can always flash back to twrp afterwards
Click to expand...
Click to collapse
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app
brichardson1991 said:
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app
Click to expand...
Click to collapse
Good news. The latest version of Philz, s it is CWM based - uses the latest Cyanogen sources to build. I update the CM sources everytime I build Philz so hopefully there should be fewer issues when new stuff comes out.
I'm having issues with my OPO root. I unlocked my bootloader, flashed TWRP and rooted by installing SuperSU through a zip. All was good and root was working yesterday.
I haven't done any Android updates, but my root is gone! If I open the SuperSU app it does this (see screenshot in attachments)
I tried reflashing the zip through TWRP but the same happens after rebooting.
Any ideas?
Turns out this is all because I uninstalled BusyBox, any suggestions as to what to do next? Someone on the forums here: http://forum.xda-developers.com/showpost.php?p=54001747&postcount=5 got it to work by wiping and reflashing everything but I'd rather not do that...
oscarandjo said:
Turns out this is all because I uninstalled BusyBox, any suggestions as to what to do next? Someone on the forums here: http://forum.xda-developers.com/showpost.php?p=54001747&postcount=5 got it to work by wiping and reflashing everything but I'd rather not do that...
Click to expand...
Click to collapse
Reinstall busybox.
https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
Sent from N5 or OPO
oscarandjo said:
Turns out this is all because I uninstalled BusyBox, any suggestions as to what to do next? Someone on the forums here: http://forum.xda-developers.com/showpost.php?p=54001747&postcount=5 got it to work by wiping and reflashing everything but I'd rather not do that...
Click to expand...
Click to collapse
Why on earth did you uninstall Busybox in the first place?
Sent from my Evita
Same problem here.
My OpO was rooted and after uninstalling busybox i have the same issue.
Superuser says no su binaries
i tried flashing again an again. Flash works fine but always the same message no su binaries ..
Busybox was stuck on loading data, that's why i uninstall it .
Same problem And i want to do a full wipe of my phone and install CM11 instaid of CM11s but restore my settings trough titanium backup. But i need root for that first.
wacky.ddw said:
Same problem And i want to do a full wipe of my phone and install CM11 instaid of CM11s but restore my settings trough titanium backup. But i need root for that first.
Click to expand...
Click to collapse
Don't restore system data when switching ROMs.
Sent via Bacon
timmaaa said:
Don't restore system data when switching ROMs.
Sent via Bacon
Click to expand...
Click to collapse
What? I wasn't going to restore system data anyway. I don't want to redo all my settings again so that why i need a titanium backup, which i cant make without root.
You guys are totally out of a clue.
First: why do you uninstall busybox? Read twice, flash once. If you knew what busybox is for you probably would avoid such errors. Don't tweak your devices if you're not savvy of what you're doing or xda forum will always be cluttered by such threads.
Second: System options backed up can screw up your phone if they do not apply to the ROM just installed causing various problems if not bootloops. DO NOT RESTORE EM. NO WAY.
Hope this helps.
PS: Install busybox from play store to solve the issue.
wacky.ddw said:
What? I wasn't going to restore system data anyway. I don't want to redo all my settings again so that why i need a titanium backup, which i cant make without root.
Click to expand...
Click to collapse
Read what you just wrote and tell me again that you don't want to restore system data.
Sent via Bacon
DuckMcQUack said:
PS: Install busybox from play store to solve the issue.
Click to expand...
Click to collapse
It don't works, install ok but Busybox crash when i open it
ahytes said:
It don't works, install ok but Busybox crash when i open it
Click to expand...
Click to collapse
Personally i would just clean flash again from the start...
Inviato dal mio One utilizzando Tapatalk
Hi, I have the same problem.
I tried to reflash SuperSU, but not working.
BusyBox was uninstalled from my pocket :crying:
What should I do ?
See post right above yours.
Transmitted via Bacon
Sorry.
But I only flashed the zip version of BusyBox, and it work now.
Brigitte-Bedo said:
Sorry.
But I only flashed the zip version of BusyBox, and it work now.
Click to expand...
Click to collapse
I have this same problem as OP. Ok well since the app keeps crashing on startup, flashing a zip seems like a good idea. Where did you find this zip file?
Same Problem
I lrooted my opo and flashed Sabermods Cm Lollipop and am also getting the same notification, any root needed apps are telling me the phone isnt rooted?? I also tried installing this busybox but wont work cause the phone is coming up as unrooted?
Has anyone a straight answer for this dilemma that doesnt include a full wipe/flash rom again...?
http://t.co/ozzNyThVm0 flash this one, chainfire latest SU
---------- Post added at 10:06 PM ---------- Previous post was at 10:04 PM ----------
mindblizzard said:
http://t.co/ozzNyThVm0 flash this one, chainfire latest SU
Click to expand...
Click to collapse
Had this problem to, try to uninstall supersu etc. Flash latest su and problem fixed, im on slimLP rom
Ok, I can't seem to get back root either. I had root and was running ParanoidAndroid. I wiped clean, flashed Cyanogen 12 nightly, flashed Gapps, wiped cache/dalvik. Everything rebooted into Lollipop fine, but I've lost root and can't seem to figure out how to re-root. I flashed the most recent SuperSU (2.46) via TWRP with no luck. Keeps saying I need to re-root first. Any ideas?
I seem to be losing root after rebooting. This is a major issue for me as I have the Z3 set up with no soft keys and navigate using GMD Gesture. So when root dissappears I cannot navigate around the phone or exits apps etc.
I have narrowed it down to a potential issue with 'unicon' xposed module, which basically changes the icons at system level. I cannot say for sure that this is causing the issue but it looks very likely.
Also without root I cannot uninstall Supersu or Xposed, but with many reboots and managing to disable and then re-enable Supersu through system settings I now have root again. But as soon as I reboot it's gone again.
Very strange issue never encountered this before.
Some info about my Z3:
ANDROID 4.4.4
LOCKED BOOTLOADER
EDIT:
i have noticed a few more issues:
power button on side is not responding any more.
root is working now that supersu is uninstalled
i cannot boot into recovery both manually and through NDR utilities
If you are in a position to help, please please please do!
You need to disable the RIC
If you are unsure just flash an advanced stock kernel from the development section.
gregbradley said:
You need to disable the RIC
If you are unsure just flash an advanced stock kernel from the development section.
Click to expand...
Click to collapse
What will this achieve? I have completely killed an Xperia Z before and want to make 100% sure before i proceed.
Also please notice my bootloader is LOCKED, i accidentally stated it was unlocked in the OP. I cannot flash a kernel with a locked bootloader can i?
I have noticed another few issues:
power button on side: isn't responding any more.
root is working now that supersu is uninstalled
i cannot boot into recovery both manually and through NDR utilities
rm83855 said:
What will this achieve? I have completely killed an Xperia Z before and want to make 100% sure before i proceed.
Also please notice my bootloader is LOCKED, i accidentally stated it was unlocked in the OP. I cannot flash a kernel with a locked bootloader can i?
I have noticed another few issues:
power button on side: isn't responding any more.
root is working now that supersu is uninstalled
i cannot boot into recovery both manually and through NDR utilities
Click to expand...
Click to collapse
I read your post when you said you had an unlocked boot.
No you cannot flash a custom kernel.
OK, you will need to ensure you installed the recovery correctly.
Run the installer again for dual recovery and post the out put here.
If it goes correctly it will sort everything out for you
gregbradley said:
I read your post when you said you had an unlocked boot.
No you cannot flash a custom kernel.
OK, you will need to ensure you installed the recovery correctly.
Run the installer again for dual recovery and post the out put here.
If it goes correctly it will sort everything out for you
Click to expand...
Click to collapse
I have just this minute managed to correctly install the recovery. Will i be good from now on?
How do you recommend installing Supersu? When i try to install through the recovery the phone just reboots normally. Should i install a flshable zip instead of installing from playstore.
How will i prevent this happening again?
rm83855 said:
I have just this minute managed to correctly install the recovery. Will i be good from now on?
How do you recommend installing Supersu? When i try to install through the recovery the phone just reboots normally. Should i install a flshable zip instead of installing from playstore.
How will i prevent this happening again?
Click to expand...
Click to collapse
Flash this in recovery
http://download.chainfire.eu/695/SuperSU/
gregbradley said:
Flash this in recovery
http://download.chainfire.eu/695/SuperSU/
Click to expand...
Click to collapse
thanks i managed to flash it. The power button issue persists. The screen will stays on and the power button will not turn it off however If i hold it in i get the power menu?
EDIT: I reinstalled Xposed, rebooted and once again root is gone
rm83855 said:
thanks i managed to flash it. The power button issue persists. The screen will stays on and the power button will not turn it off however If i hold it in i get the power menu?
EDIT: I reinstalled Xposed, rebooted and once again root is gone
Click to expand...
Click to collapse
I would flash a stock FTF and re root again from the beginning. You have something wrong. Then install recovery and flash a pre-rooted version of the latest ROM
gregbradley said:
I would flash a stock FTF and re root again from the beginning. You have something wrong. Then install recovery and flash a pre-rooted version of the latest ROM
Click to expand...
Click to collapse
i was afraid you would say this Can you tell me if Lollipop is rootable or should i stick with KK?
Thank you for your help!
gregbradley said:
I would flash a stock FTF and re root again from the beginning. You have something wrong. Then install recovery and flash a pre-rooted version of the latest ROM
Click to expand...
Click to collapse
i actually just remember about a TWRP backup i did the day i rooted the phone, i have this saved on my pc would this work, or would it be better to start from scratch?
rm83855 said:
i was afraid you would say this Can you tell me if Lollipop is rootable or should i stick with KK?
Thank you for your help!
Click to expand...
Click to collapse
There is no lollipop for any sony phones so no one knows
Unless you mean custom roms and of course they are rootable.
Just flash a .93 FTF, root, install recovery and then flash a prerooted zip made with PRFCreator.
EDIT
If you think that backup does not have this issue on it then restore it.
However, if you are unsure its best to start again and then you can eliminate the problem.
gregbradley said:
There is no lollipop for any sony phones so no one knows
Unless you mean custom roms and of course they are rootable.
Just flash a .93 FTF, root, install recovery and then flash a prerooted zip made with PRFCreator.
EDIT
If you think that backup does not have this issue on it then restore it.
However, if you are unsure its best to start again and then you can eliminate the problem.
Click to expand...
Click to collapse
i backed up the day i rooted so should be good. I somehow had the opinion Sony were among the first to process updates, no idea where i got that idea from
Just restored and everythings working great, although all my lovely zoopers are gone
Thanks for your help man, appreciated
gregbradley said:
There is no lollipop for any sony phones so no one knows
Unless you mean custom roms and of course they are rootable.
Just flash a .93 FTF, root, install recovery and then flash a prerooted zip made with PRFCreator.
EDIT
If you think that backup does not have this issue on it then restore it.
However, if you are unsure its best to start again and then you can eliminate the problem.
Click to expand...
Click to collapse
so everything was great, then i installed the following apps:
GMD Gesture
Udn pro (xposed)
Xblast (Xposed)
Flat bars (xposed)
I now have no root again. Completely sucks i just set the goddamn phone up again and now back to square one!
How can one of these apps have the power to remove root?! my backup works flawlessly and i can reboot and still have root, it is 100% one of these apps
rm83855 said:
so everything was great, then i installed the following apps:
GMD Gesture
Udn pro (xposed)
Xblast (Xposed)
Flat bars (xposed)
I now have no root again. Completely sucks i just set the goddamn phone up again and now back to square one!
How can one of these apps have the power to remove root?! my backup works flawlessly and i can reboot and still have root, it is 100% one of these apps
Click to expand...
Click to collapse
It will not be removing root... but it might be messing with it.
Its a slow process but try this
Restore the backup and setup again, then take a backup before you insall those 4, then start adding them one at atime, take a backup in between each one so you can restore it. It may be that on their own they are fine but together they could conflict.
At any point you may want to take a logcat and share it... Just a thought..
gregbradley said:
It will not be removing root... but it might be messing with it.
Its a slow process but try this
Restore the backup and setup again, then take a backup before you insall those 4, then start adding them one at atime, take a backup in between each one so you can restore it. It may be that on their own they are fine but together they could conflict.
At any point you may want to take a logcat and share it... Just a thought..
Click to expand...
Click to collapse
the thing is ive managed to get rid of xposed and all modules and now supersu is mucked up and wont stick after a reboot.
Therefore one of these apps must not only be messing with root but changing some system file to make Supersu not stick after a reboot?
Does that make sense? My responses may well go downhill from here, I'm losing the will to live
I will try that and post back. Thanks
rm83855 said:
the thing is ive managed to get rid of xposed and all modules and now supersu is mucked up and wont stick after a reboot.
Therefore one of these apps must not only be messing with root but changing some system file to make Supersu not stick after a reboot?
Does that make sense? My responses may well go downhill from here, I'm losing the will to live
I will try that and post back. Thanks
Click to expand...
Click to collapse
In which case, go back to stock and start again.. The process works, somewhere along the line you have borked something.
Flash .93, root with griefrrot, install recovery flash a prerooted latest firmware..
That process works.
gregbradley said:
In which case, go back to stock and start again.. The process works, somewhere along the line you have borked something.
Flash .93, root with griefrrot, install recovery flash a prerooted latest firmware..
That process works.
Click to expand...
Click to collapse
Quick update: i have found the problem app and identified it as "LG Optimus Lockscreen". This app was asking for root privileges and was somehow disabling the home button through a setting to ensure someone couldnt unlock the phone by pressing the home button. It was also causing the issue with losing root.
Shame because the lockscreen is awesome
Why would it be doing this? I already removed root via the SuperSU app permanently. What could be causing the error?
Bebout said:
Why would it be doing this? I already removed root via the SuperSU app permanently. What could be causing the error?
Click to expand...
Click to collapse
You might have a system app removed or missing
Or maybe you have done something with the build prop as well if thats messed with that will also throw an error out.
If you read closely it should tell you what the error is
xxbabiboi228xx said:
You might have a system app removed or missing
Click to expand...
Click to collapse
I really hope not. How do I go about finding out if I'm missing a system app? I've already done a factory reset along with unrooting via SuperSU's app.
Bebout said:
I really hope not. How do I go about finding out if I'm missing a system app? I've already done a factory reset along with unrooting via SuperSU's app.
Click to expand...
Click to collapse
It should tell you the error after you try flashing the ota you may have to use the .kdz method
xxbabiboi228xx said:
It should tell you the error after you try flashing the ota you may have to use the .kdz method
Click to expand...
Click to collapse
I don't have TWRP installed, either. I've got stock recovery and stock everything. I was going to remove root so I could update and then re-root for v10j and then install the new version of TWRP.
Bebout said:
I don't have TWRP installed, either. I've got stock recovery and stock everything. I was going to remove root so I could update and then re-root for v10j and then install the new version of TWRP.[/QUOTE
Your telling me you removed root ? But you never had twrp as your recovery ?
Click to expand...
Click to collapse
xxbabiboi228xx said:
Bebout said:
I don't have TWRP installed, either. I've got stock recovery and stock everything. I was going to remove root so I could update and then re-root for v10j and then install the new version of TWRP.
Click to expand...
Click to collapse
Your telling me you removed root ? But you never had twrp as your recovery ?
Click to expand...
Click to collapse
I fixed it. I rooted the device and flashed the v10i recovery image for TWRP that I found and I'm now going to update to v10j via the kdz, as you suggested. Thank you.
Bebout said:
I fixed it. I rooted the device and flashed the v10i recovery image for TWRP that I found and I'm now going to update to v10j via the kdz, as you suggested. Thank you.
Click to expand...
Click to collapse
No problem glad i could assist u in your problem
Why not get TWRP again and flash @GameTheory's v10j pre-rooted stock rom, it's not like you're going to see anything special with that update it's the last one before MM:
http://androidcreations.weebly.com/flashable-update-zip.html
Bebout said:
Why would it be doing this? I already removed root via the SuperSU app permanently. What could be causing the error?
Click to expand...
Click to collapse
well even if you Remove root via SuperSU that doesn't mean your SYSTEM is unmodified, the only way to get back to FULL Unmod. software is by following my steps of restoring back to stock, here is the link
http://forum.xda-developers.com/android/development/rom-lg-g-stylo-h631-ms631-v10j-stock-t3211563
P.S. You need to have TWRP for this so Re-Root and Re-Flash TWRP and follow steps
Which June factory image is for the "everything else" devices... NHG47N or NHG47B?
Edit: Sorry, just figured it out, but it took info from another site other than Google's to find out that "N" is for Verizon and "B" is for everyone else.
CatThief said:
[solved] Which June factory image is for the "everything else" devices... NHG47N or NHG47B?
Edit: Sorry, just figured it out, but it took info from another site other than Google's to find out that "N" is for Verizon and "B" is for everyone else.
Click to expand...
Click to collapse
There's actually 4 different builds.
See here for what's what
Yep, I did that. There is no description there for "N" but I found out "B" is the one I want.
I always get Failed to udate, try again when installing the ota via settings.
Juli112 said:
I always get Failed to udate, try again when installing the ota via settings.
Click to expand...
Click to collapse
Have you unlocked the bootloader and modified the phone in any way? Personally I've rooted my phone with SuperSU, so I've been using FlashFire to install the OTA.
alluringreality said:
Have you unlocked the bootloader and modified the phone in any way? Personally I've rooted my phone with SuperSU, so I've been using FlashFire to install the OTA.
Click to expand...
Click to collapse
Did you update already. I read somewhere since the may update that if you have bootloader unlocked, rooted, and another kernel you get bootloops?
Is that true? I'm still on April security update and been using stock rom, just unlocked bootloader, rooted, and using elementalx kernel
I still have the May update on my phone, so I was just reading what people were saying about June before installing. According to posts like the first link, the current version of SuperSU does not sign the boot image. Signing the boot image as the last step is reportedly needed to avoid bootloops for the May or later bootloader. If someone is just using SuperSU, they can use the zip from the second link after SuperSU, which is what I did for May.
https://forum.xda-developers.com/showpost.php?p=72451572&postcount=1357
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't use ElementalX, but I've read a few posts indicating that it will also sign the boot image when installed last.
https://forum.xda-developers.com/showpost.php?p=72181714&postcount=1435
I did a flash-all (with -w removed) of NHG47B, then booted TWRP where I installed SuperSU and also VerifiedBootSigner-v8.zip before rebooting and everything is working fine.
alluringreality said:
I still have the May update on my phone, so I was just reading what people were saying about June before installing. According to posts like the first link, the current version of SuperSU does not sign the boot image. Signing the boot image as the last step is reportedly needed to avoid bootloops for the May or later bootloader. If someone is just using SuperSU, they can use the zip from the second link after SuperSU, which is what I did for May.
https://forum.xda-developers.com/showpost.php?p=72451572&postcount=1357
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't use ElementalX, but I've read a few posts indicating that it will also sign the boot image when installed last.
https://forum.xda-developers.com/showpost.php?p=72181714&postcount=1435
Click to expand...
Click to collapse
hey thanks i got everything up and running with the new June OTA. but what do you use to reflash TWRP?
flashify just freezes i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Nope. twrp.img must be firstly boot into the phone, then via this temporary twrp,you can install twrp.zip from your phone.
kazemitsui said:
hey thanks i got everything up and running with the new June OTA. but what do you use to reflash TWRP?
flashify just freezes i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Click to expand...
Click to collapse
CatThief said:
I did a flash-all (with -w removed) of NHG47B, then booted TWRP where I installed SuperSU and also VerifiedBootSigner-v8.zip before rebooting and everything is working fine.
Click to expand...
Click to collapse
Twrp rc1 or rc2?
Supersu 2.82 or 2.79rc3?
TENN3R said:
Twrp rc1 or rc2?
Supersu 2.82 or 2.79rc3?
Click to expand...
Click to collapse
I used twrp-3.0.2-0-RC1-fastboot-sailfish.img because it was the only version that was stable for me from the start. When the January update came out I tried the current TWRP at that time (it was an RC3, can't remember the version) and while others had no problems I had an experience of my own that I'm not keen on repeating.
As for SuperSU, I installed SR5-SuperSU-v2.78-SR5-20161130091551.zip then updated to the latest 2.82 from Google Play.
I know, newer releases may work now, but I was only going to try something newer if my "old" method failed. Like I said, I only boot to TWRP, I don't flash it. I just want root.
kazemitsui said:
i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Click to expand...
Click to collapse
When you tried installing TWRP with FlashFire, did you put the boot signer after TWRP? The TWRP install has to be signed with the current bootloader. The FlashFire documents make it seem like it should be able to install TWRP, but I haven't tried installing TWRP and can't find any relevant posts, so I suppose it might not work.
https://flashfire.chainfire.eu/actions/zip/
Personally I've just been using the small OTAs that come to the phone the past few months, but the following post indicates that FlashFire can at least retain a previously-installed version of TWRP without issue.
https://forum.xda-developers.com/showpost.php?p=70929003&postcount=8
TENN3R said:
Supersu 2.82 or 2.79rc3?
Click to expand...
Click to collapse
I had installed 2.79 RC3 with the May update, and then I had taken the play store update to 2.82. When I did the June update with FlashFire I'm guessing it must have went back to 2.79 RC3, because I got the update message again. I haven't seen anything to suggest either is likely an issue with the Pixel.
alluringreality said:
When you tried installing TWRP with FlashFire, did you put the boot signer after TWRP? The TWRP install has to be signed with the current bootloader. The FlashFire documents make it seem like it should be able to install TWRP, but I haven't tried installing TWRP and can't find any relevant posts, so I suppose it might not work.
https://flashfire.chainfire.eu/actions/zip/
Personally I've just been using the small OTAs that come to the phone the past few months, but the following post indicates that FlashFire can at least retain a previously-installed version of TWRP without issue.
https://forum.xda-developers.com/showpost.php?p=70929003&postcount=8
I had installed 2.79 RC3 with the May update, and then I had taken the play store update to 2.82. When I did the June update with FlashFire I'm guessing it must have went back to 2.79 RC3, because I got the update message again. I haven't seen anything to suggest either is likely an issue with the Pixel.
Click to expand...
Click to collapse
I just flashed TWRP through my computer I couldn't bother trying to figure out if FlashFire will flash TWRP or not haha