Hey there,
Since Lollipop is out and most of you are Rooting it, There's a chance you might run into a BootLoop after flashing the SuperSU through TWRP/CWM. And when this happens, New users mostly flash their Stock Firmware and Restart the process all over again. This is not necessary and can be avoided by following these steps:
RECOVER FROM BOOTLOOP CAUSED BY SUPERSU:
Re-Boot into Recovery mode (TWRP/PhilZ) by Holding the Power and Volume Down button
Select Wipe > Advanced Wipe > Check only Dalvik Cache & Cache
Swipe to Clear the Dalvik Cache and Cache
Re-Boot! (Can take ~6-7mins)
Done!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
CREDITS:
Tip @ joel-n1 posted here.
Click to expand...
Click to collapse
Hope this helps! Thanks
KrishnaSagar said:
Hey there,
Since Lollipop is out and most of you are Rooting it, There's a chance you might run into a BootLoop after flashing the SuperSU through TWRP/CWM. And when this happens, New users mostly flash their Stock Firmware and Restart the process all over again. This is not necessary and can be avoided by following these steps:
RECOVER FROM BOOTLOOP CAUSED BY SUPERSU:
CREDITS:
Hope this helps! Thanks
Click to expand...
Click to collapse
Excellent PSA! I followed your instructions and this seems to have solved my bootloop problems. XT1063 with 5.0 22.21.16.
Thanks man! I rooted it before and had to restore the backup. I'll try now that I'm armed with this info
UPDATE: Can confirm that the method is working. I rooted the phone and the phone went into a boot loop. Cleared dalvik and cache, and voila! the phone booted up.
mahendru1992 said:
Thanks man! I rooted it before and had to restore the backup. I'll try now that I'm armed with this info
UPDATE: Can confirm that the method is working. I rooted the phone and the phone went into a boot loop. Cleared dalvik and cache, and voila! the phone booted up.
Click to expand...
Click to collapse
Glad to help I had my fair share of Bootloops and dont want them to happen again. I can now confidently flash any supersu beta without fear.
Yes..to erase cache, saves alot of flashing..lol
Anytime the device is "stuck" in a bootloop, or stalls on the "unlocked bootloader" screen, power down, boot to recovery, then erase cache..saves me 90% of the time..
sent by my:
Lollipop 5.0_22.11.6 (w/Root)
TWRP v2.8.0.1-titan
UPDATE-SuperSU-v2.16
XT1064 Moto G (2nd Gen.)
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Will doing this delete my data in my phone?
wiping cache&dalvikCache is not working, my phone will boot, optimize apps and works fro like 5 seconds and then it reboots and its stuck back on logo bootloop
help?
ZeroGoCZ said:
wiping cache&dalvikCache is not working, my phone will boot, optimize apps and works fro like 5 seconds and then it reboots and its stuck back on logo bootloop
help?
Click to expand...
Click to collapse
In this case you should flash the firmware again.
Wolfcity said:
In this case you should flash the firmware again.
Click to expand...
Click to collapse
Okay, but how do I root my phone then? What is causing the bootloops?
ZeroGoCZ said:
Okay, but how do I root my phone then? What is causing the bootloops?
Click to expand...
Click to collapse
I suspect you've used the wrong superSU version. What firmware are you on and how did you root the first time? Did you use systemless root? What's the number of the superSU version?
Sent from my Moto G 2014 using XDA-Developers mobile app
Wolfcity said:
I suspect you've used the wrong superSU version. What firmware are you on and how did you root the first time? Did you use systemless root? What's the number of the superSU version?
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
My phone is Leagoo Alfa 1 running lollipop 5.1, stock rom and kernel, twrp v3.0, unlocked bootloader. Tried to flash supersu 2.46, then beta 2.62 and then 2.66. I did not forget to wipe cache+dalvik cache. None of these work. I do not know what systemless root it. (Going to look on it) My last root was on android 4.4.2, so I am new with lollipop.
Edit: This was was never rooted before, I just got it a few days ago.
ZeroGoCZ said:
My phone is Leagoo Alfa 1 running lollipop 5.1, stock rom and kernel, twrp v3.0, unlocked bootloader. Tried to flash supersu 2.46, then beta 2.62 and then 2.66. I did not forget to wipe cache+dalvik cache. None of these work. I do not know what systemless root it. (Going to look on it) My last root was on android 4.4.2, so I am new with lollipop.
Edit: This was was never rooted before, I just got it a few days ago.
Click to expand...
Click to collapse
You know that this is the Motorola Moto G 2014 forum here?
So I dont´t really know what´s the best for your device. Maybe you should have a look in your devices forum (if there is one) or ask in the superSU thread:
http://forum.xda-developers.com/showthread.php?t=1538053
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I had good experience with the BETA-SuperSU-v2.62-3-20151211162651.zip but I´m running a 6.0.1 custom rom.
yeah, I am aware of the fact, that this is moto g 2014, sorry for bothering :|
Anyway, looking at the systemless root - it works on lollipop 5.1.1 and up. Unfortunately my thingy is 5.1 so, no luck there~ *****me*
Thank you for your time and your answer. My posts are mostly ignored...
mali_ said:
Hey! My moto g2 2014 is stuck in logo screen after rooting with supersu 2.78 stable. Which version should I use? I'm unable to root it. Please help.
Click to expand...
Click to collapse
Some more info please. Which revovery? What kind of ROM?
I had sucess on my ROMs flashing BETA-SuperSU-v2.62-3-20151211162651.zip. After flashing you can upgrade it via playstore to 2.78.
Depending on the ROM you´re using you can boot into recovery and reflash it to fix the bootloop.
help bootloop htc one m7
i have an htc one m7,android 5.0.2 and rooted it (CWM-SuperSU-v1.30).then i flash it with BETA-SuperSU-v2.30.
now it cause a bootloop.so i wipe cashe and delvik.but has no effect.
thanks for any help.
I wiped the cache and it's still stuck in the boot loop,I used the latest supersu version and also the latest of twrp
Just use the SuperSU Uninstaller ZIP, wipe your dalvic cache and reboot.^^
Transfer it in TWRP on your internal storage via ADB.
ZIP Download: http://forum.xda-developers.com/attachment.php?attachmentid=3528363&d=1446472307
Hi,,Plz help me.. i am a beginner in rooting.. i have unlocked bootloaded for moto g3, flashed logo.bin to remove warning message,installed twrp , after that i have tried to root using supersu.zip ..Now my phone is stuck in bootloop...What should i do..Plz give suggestion..
i have used below files
twrp-osprey-3.0.2-r1_2
UPDATE-SuperSU-v2.65-20151226141550
logo.bin
all are downloaded from XDa forum itself
i installed Mokee rom60.1 release one on my redmi 2. I enabled root access in developer options but when checked with root checker, it showed not rooted. So, i flashed supersu zip v2.46 thrpugh twrp and wiped cache and dalvik cache.
now i reboot the system but nothing is going on except mokee logo. it is showing more than half an hour. please help me
Reflash everything, before flashing supersu, do it by these steps (taken from here)
1. Don't use the zip method. Download the backup instead and restore it (don't forget to backup your main rom).
2. Download the latest SuperSU zip here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
It must be 2.67+ or higher.
3. In TWRP, go to Advanced>Terminal Command, don't select any folder and type the following commads (you have to clean the textbox in order to type another one):
touch /data/.supersu
echo SYSTEMLESS=true > /data/.supersu
To verify that you made it correctly type
cat /data/.supersu
If you have at hand a desk with adb you can do this quicker using twrp's adb:
touch /data/.supersu && echo SYSTEMLESS=true > /data/.supersu && cat /data/.supersu
If the above commands return
SYSTEMLESS=true
Then it's okay, you can proceed.
3. After that, install the SuperSU zip. It must be the 2.67 version (or higher).
4. Reboot system, if TWRP asks to install root, don't let it and press Reboot System.
Related
UPDATE 10/02/2016- New version of TWRP has been released v3.0.3-0. See below:
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
I have updated versions SM-T800/805 with new builds. TWRP is now v3.0.3-1
TWRP OFFICIAL APP RELEASED: https://twrp.me/app/
Fixes:
Download mode now available in REBOOT options.
Root Shell now available in ADB.
Radio and Recovery backup.
System image backup/restore
Factory image flashing.
Supersu root option removed. This is to pre-empt the upgrade to MM which would cause a bootloop.
MTP fix - MTP now finally working in recovery.
Note: On my PC MTP works perfect in windows 7, but on Windows 8.1 was a little quirky. If you get a USB DEVICE NOT RECOGNISED error after enabling MTP, disable then quickly re-enable MTP and this should fix it.
This version also has system image backup and restore included. It is also possible to flash factory firmware images via the Image install button. (see the TWRP changelog above for more info)
UPDATE 5/3/16:
Have modified the twrp source code and extended factory image partition flashing to include all images except SBOOT.bin (still working on how to flash the bootloader via recovery)
This means BOOT, SYSTEM, RECOVERY, CACHE, HIDDEN, MODEM(RADIO) can all be flashed from the factory firmware. No need for ODIN anymore. As far as I know the Tab S is the only device supporting this at the moment.
(Note: to flash the modem it is necessary to rename MODEM.bin to MODEM.bin.img first)
TWRP_3.0.2-1-T700
TWRP-3.0.2-1-T705
TWRP-3.0.2-1-T800
NOTE: Certain models of the T800 version have a bug at the moment where the screen will be blank when booting to TWRP recovery until the screen timeout kicks in. After that pressing any button will show the screen. As a work around setting the timeout to 15 secs will shorten the wait.
TWRP-3.0.2-1-T805/T807(ATT or Verizon not supported)
twrp_3.0.3-1_sm-t800_10217
twrp_3.0.3-1_sm-t805_10217
FLASH WITH ODIN OR FLASHFIRE OR EXTRACT THE RECOVERY.IMG AND FLASH WITH TWRP
NOTE: It is important to boot to recovery after flashing with Odin or twrp may not stick and will be replaced with stock recovery.
When flashing uncheck auto reboot in Odin, immediately after flashing manually reboot and boot into twrp.
Manual reboot is POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FEEDBACK IS APPRECIATED PLEASE
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
gcappa said:
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
Click to expand...
Click to collapse
As long the bootloader is unlocked, and if someone has an stock recovery pulled from it, then he could be twrp for it
Bootloader is unlocked. But I already flashed a modified cwm which doesn't work too well. So not sure if I could pull the stock recovery unless I reflash the stock rom.
gcappa said:
Bootloader is unlocked. But I already flashed a modified cwm which doesn't work too well. So not sure if I could pull the stock recovery unless I reflash the stock rom.
Click to expand...
Click to collapse
If you have the firmware downloaded just right click on the md5 and open it with 7zip or Winrar, then simply just drag the recover IMG to your desktop and send it here(or link to download). I'm not going to go to much in depth as I don't want this thread to be filled with non related to twrp stuff. I'm also unsure if he has time but ash is one good recovery builder
Ok, I'll do all that when I get home and upload a link.
gcappa said:
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
Click to expand...
Click to collapse
Should be possible as long as the right files are available. This is a snapdragon 805 device?
Seeing as I don't have this device you would have to test the builds and I would need some info from the device. Might take a few builds to get a proper working one.
I take it you are currently rooted? Also could you send me a link to the version of cwm you are using?
gcappa said:
Ok, I'll do all that when I get home and upload a link.
Click to expand...
Click to collapse
Is the sm-n9100 the Chinese version Note 4 Duos?
The TWRP recovery below is for this version, please test:
twrp-2860-n1900
Stock Recovery:
Stock-recovery-n1900
Note: You take responsibility for testing this.
Failed to flash on my T-800.
dwarfer66 said:
Failed to flash on my T-800.
Click to expand...
Click to collapse
What failed to flash? It's made for the t800. It flashes fine on a t805. No one else has had any issues. What is the full version of your device?
ashyx said:
Unofficial version of the latest TWRP, don't think it's been released yet.
Found it by accident for another device, so have rebuilt it for the Tab S Exynos version only.
TWRP-2.8.6.1
Click to expand...
Click to collapse
Thank again ashy this is awesome, keep up the good work.
Confirmed its working T800 5.0.2
ashyx said:
What failed to flash? It's made for the t800. It flashes fine on a t805. No one else has had any issues. What is the full version of your device?
Click to expand...
Click to collapse
This unofficial TWRP fails to flash, just says failed when trying to install.
dwarfer66 said:
This unofficial TWRP fails to flash, just says failed when trying to install.
Click to expand...
Click to collapse
Again, you need to confirm what your exact model is and build number. As you can see from the post above it flashes fine on a T800.
Post a screenshot of the issue with Odin.
It's flashing for me ok on my T800 with IronRom 2.0. Only thing is the root ain't working. Or do I need to unselect auto-reboot and do a forced shutdown? And clear cache and reboot?
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
edit: reflashed IronRom 2.0 to fix cache issue. After the cache wipe it boots up
edit2: it appears to be rooted but it ain't working. But when an app should ask for root permissions the app goes black screen. For Titanium backup it just hangs on checking
RDDraco said:
It's flashing for me ok on my T800 with IronRom 2.0. Only thing is the root ain't working. Or do I need to unselect auto-reboot and do a forced shutdown? And clear cache and reboot?
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
edit: reflashed IronRom 2.0 to fix cache issue. After the cache wipe it boots up
edit2: it appears to be rooted but it ain't working. But when an app should ask for root permissions the app goes black screen. For Titanium backup it just hangs on checking
Click to expand...
Click to collapse
Did you update the supersu app as requested? You need to post a screenshot of root validator so I can see the status of root.
You may just need to select full unroot from settings in the supersu app then boot into twrp and run the root process again or flash the supersu2.46 zip.
Also regarding wiping cache, it can sometimes take longer depending on what's in cache at the time. It may seem like it's hung but eventually completes. On occasion I've seen it take up to a few minutes to wipe.
Just saying that root is broken on custom roms such as iron rom. It's an known issue with touchwiz lollipop roms.
-DUHA
So it's a Rom issue?
What's the actual problem?
Isn't the Rom already rooted, unusual for a custom Rom to not be prerooted?
Guess that explains why it wasn't working. (Tkkg1994 managed to get IronRom working with root in v2.0.5) so its fine for me now.
RDDraco said:
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
Click to expand...
Click to collapse
Looked into this issue and have fixed it. Wipe Cache should work now.
ashyx said:
Unofficial version of the latest TWRP, don't think it's been released yet.
Found it by accident for another device, so have rebuilt it for the Tab S Exynos version only.
TWRP-2.8.6.1
NOTE: If after using TWRP to root you don't see the notification to update Supersu, just install the latest Supersu app from Play. Check root status with Root Validator
Supersu
Root validator
Click to expand...
Click to collapse
Just today, I rooted my new Tab S (SM-T800) AFTER allowing it to OTA update to Android 5.0.2. After that, I used Odin to flash the latest version of CWM I could find for this device, and that trashed recovery altogether. Couldn't get into recovery at all. So I used Odin again to flash TWRP 2.8.6.0 and had recovery back, BUT I kept getting notifications that SuperSU needed to be updated. What I did then was flash "BETA-SuperSU-v2.48.zip", and that resolved the "update needed" problem, and all seems to be working smoothly now. :good:
I'm running stock Touchwiz Lollipop 5.0.2 . Haven't tried changing ROM's, but don't really have a desire to do that just yet.
Alright.
I had this problem for a while and I figured out how to flash the update without the need to factory reset or change the update script of the update file.
Even if you get the user/release-keys error message. EXAMPLE:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You have to be using the latest lollipop release before updating. That means you have to be on YOG7DAS2K1 before attempting.
This worked out for me. But it might not work for you. I do not believe it can destroy your phone and switch some satellites off, but still, not responsible if it did so.
Requirments:
You have to have TWRP now or you at least have ROOT and any flashing app like flashify.
Download COS 13 update file. here https://www.androidfilehost.com/?fid=24459283995316311
Download the latest CyanogenMod Recovery https://download.cyanogenmod.org/?device=bacon
Download the cm-12.1-YOG7DAS2K1 full ROM [url]https://www.androidfilehost.com/?fid=24369303960686198[/URL]
Guide:
Make sure the update cyanogen recovery option is checked in developer options.
Flash CyanogenMod Recovery downloaded before.
Reboot into it.
Use the update function in CyanogenMod Recovery and choose cm-12.1-YOG7DAS2K1 as the update file. It might take a while.
Now reboot to your phone. When booted and running, reboot to recovery.
Now you are running COS recovery. Update with the incremental.
That is it.
I hope this works out for you.
EXTRA: How to ROOT and have TWRP as a recovery:
Requirements:
A laptop.
Download TWRP and adb drivers on the laptop and the SuperSU and TWRP on your phone
Download Oneplus One TWRP Recovery [url]https://dl.twrp.me/bacon/twrp-3.0.2-0-bacon.img.html[/URL]
Get any adb divers. This one suffice [url]http://forum.xda-developers.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339[/URL]
Download the latest SuperSu [url]https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip[/URL]
Guide:
Reboot into bootloader: you can do this in many ways. A simple google search will show you how. Easiest way is to turn the phone off and hold the volume up and power long enough for the phone to boot into bootloader.
Connect your phone to your laptop
Run the adb: I assume you are using windows of course. First put the TWRP .img file in this folder. Hold shift and right click in the folder downloaded above. A 'Open command window here' option will be there. Click it and write in the window
Code:
fastboot boot twrp-3.0.2-0-bacon.img
. A hint: you can just write twrp and hit TAB, it will complete the filename. Or you can rename the downloaded file to just twrp.img
Check your phone, you will be running TWRP temporarily. You now have the option to ROOT only by flashing the SuperSU file downloaded on your phone. If you reboot now you will lose TWRP and get back to the official COS Recovery. If you want TWRP for good flash the TWRP file downloaded on your phone before.
I hope this is easy. It actually is. just follow it step by step.
If you could provide us the guide to root and come back to twrp I would be extremely happy
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
fastboot flash latest twrp and flash SuperSU BETA
THANK the post if I deserve
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
if you need a guide to root, this means you are not rooted, and if you are not rooted most probably you already have stock recovery, which means you can just install the OTA update without any issues.
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
Added as requested. I hope you find it easy.
y2kkingboy said:
Added as requested. I hope you find it easy.
Click to expand...
Click to collapse
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
bisio971 said:
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
Click to expand...
Click to collapse
Yeah. I mad a mistake there. Thank you and glad it helped.
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
thinleytsering9 said:
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
Click to expand...
Click to collapse
As I stated before you have to be on COS 12.1 YOG7DAS2K1. This method should not format your phone or remove any data as there is no factory reset step.
As for the link they are all over the place now. I used the official one. I'll link it for your convenience.
can anyone please pull the stock recovery from COS 13, not 12. I kinda screwed up while updating and now stuck in bootloop.
Update: The issue is resolved. The issue was because of SuperSu 2.46. Installing the latest TWRP and SuperSu 2.66 fixed it. Marshmallow is now rooted!
Thank you very much! After going back to stock and still not receiving the update for more than a week (well at least it felt like a week, Lol) I decided to flash a full COS 13 zip floating around. Instantly liked the new ROM but it had root/symlink issues only to be resolved when flashing a custom kernel it seems. Not what I really wanted so then I stumbled onto your thread and this technique worked 100%! I was on DAS2K1 (flashed thru a custom recovery) already and had several failed attempts flashing just the incremental outright (thru stock recovery)., but by flashing DAS2K1 thru stock recovery first as you suggest then the incremental seems to do the trick.
I did it all the steps, but my phone doesn't not start. After optimizing aplications I have bootloop at "cyanogen modready".
L.E. I think the problem was one of old aplications. After a clean install everything works.
This is the best thing Oneplus one i ever experience.COS13 give my Oneplus one a new breathe of life .This update better than crap lolipop.No Bug for me until now,only google play service need to update twice in play store,its auto reboot itself twice and wholla,super speed UX.The best thing i ever have.I apply update from CM-12-0-YNG1TAS17L Build LRX22G using this method and it works flawlessly
I don't need to factory reset or wipe cache .
I flash full stock ROM cm-12.1-YOG7DAS2K1 and apply update through CyanogenMod Recovery only and nothing else.
Now my oneplus one is rooted and TWRP install using ADB and its fly.All rooted apps is working together with Adaway.
Thanks Cyanogen team for make this 2 years old flagship killer a beast .
Only thing not satisfied is gone signal and wifi status (connectivity indicator ).I need to swipe down to see my transfer data working (what a bummer ).
Thanks so much for this magical guide (y2kkingboy) Yours truly Oneplus one diehard fan.
I was already on cm-12.1-YOG7DAS2K1, however rooted. So even if I had been offered the OTA it would have failed.
Your guide got me updated, first time with no problems.
6.0.1 is such an improvement on 5.1.1, I tried a couple of other 6.0 roms, however this has by far been the most stable and bug free.
Cheers for the tutorial!
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
#sychrome# said:
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
InsaneNutter said:
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2522762
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
I had tried this before and it did not work for me. Kept getting an error saying "the signature file was not a complete file" and therefore it didn't flash. But it may have been editing error on my part. This method works just fine and no need to give up your data either.
Having tried many other ways, I got it done with this instruction.
Thank you!
marxu said:
Having tried many other ways, I got it done with this instruction.
Thank you!
Click to expand...
Click to collapse
Glad I helped.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello!
We are back with brand new Pie beta builds, for you all to play with.
[Changelog]
Bug fixes
Clock timer and stopwatch interface display is incomplete
Microphone doesn't work when earphones are plugged in
Crash issues with native message app
Those who download the Community Beta build will get OTA update when the stable build is released.
Instructions for updating to the Community Build
Backup your entire device as it is a big update and change of Android version
For those on the latest stable version 181206
Preconditions: Boot Loader should be locked
Steps:
1. Download the file from the link provided on the forum post
2. Move the downloaded file to internal storage root folder using the File Manager.
The device can then be updated via two methods.
First method: Local Update
1. Open Settings -> System update -> Click top right setting icon
2. Choose Local update
3. Click on the downloaded file and wait until the device reboots
Second Method: Recovery Update
1. Turn off the device -> Press power and volume up key simultaneously until the device enters the Fastboot Mode
2. Navigate to Recovery option using volume and power button -> Choose English -> Install from Internal storage -> Select the downloaded zip file -> Select 'Yes'
3. Wait until the installation is complete -> Reboot
For those who are on the latest Open Beta version 180712
Note: The entire data will be wiped since there will be a version transition from Open beta to the stable version. If you made a OnePlus Switch backup, be sure to make a copy of it before moving forward.
Steps:
1. Download the file from the link provided on the forum post
2. Move the downloaded file to internal storage
3. Device can be updated only via Recovery Update:
Turn off the device -> Press power and volume up key simultaneously until the device enters the Fastboot Mode
Navigate to Recovery option using volume and power button -> Choose English -> Install from Internal storage -> Select the downloaded zip file -> Select 'Yes'
Wait until the installation is complete -> Reboot
FAQ
1. Dirty flash over TWRP - gives Decryption error and will lose data.
2. Dirty / clean flash over unlocked bootloader- leads to loss of data
3. Magisk / rooting - works without issues
4. Titanium backup - works without issues
In case of unlocked bootloader or custom recovery - Backup and flash Pie community Beta build, restore backup or wait till official release.
Flashing over leaked build - users report to be working,no official support would be available on this.
Thank you once again for all your patience. We are one step closer to releasing the Pie for OnePlus 3 / 3T, you can now download and try our community build right now.
Never Settle.
Downloads
Community Beta 2 - OnePlus 3T
Community Beta 2 - OnePlus 3
Community Beta - OnePlus 3T
Community Beta - OnePlus 3
Official TWRP 3.3.0-1
ROOT: Magisk
Want to get rid of DM-Verity/Force Encryption? Check this THREAD
Please let me know if i'm missing anything. Thanks
Sent from my OnePlus 3T using XDA Labs
Nice?
Siddk007 said:
Hope to see active discussion in the new thread as well
Click to expand...
Click to collapse
I tried to flash open beta 20 but i had white led and black screen.
So hear how i did it.I have Blu_Spark TWRP v8.61 and I am on ext4 only data,so I wipe everything except internal store.
I flash the full beta 20 zip which i have to my download section,and the flash finished succseful.But then when i tried to flash the magisk 15.0 the phone stuck in the recovery and then closed and then white led and black screen!
So i went back to recovery manually and flash my back up and i am in Freedom Os now.
Can you explain me what was wrong?
P.s I did that twice and with magisk 14.6.
Thank you for opening this Thread!And I wish to all happy new year!
xarrismoto said:
I tried to flash open beta 20 but i had white led and black screen.
So hear how i did it.I have Blu_Spark TWRP v8.61 and I am on ext4 only data,so I wipe everything except internal store.
I flash the full beta 20 zip which i have to my download section,and the flash finished succseful.But then when i tried to flash the magisk 15.0 the phone stuck in the recovery and then closed and then white led and black screen!
So i went back to recovery manually and flash my back up and i am in Freedom Os now.
Can you explain me what was wrong?
P.s I did that twice and with magisk 14.6.
Thank you for opening this Thread!And I wish to all happy new year!
Click to expand...
Click to collapse
Unmount system prior to flashing the rom
Nice to open d thread..... mch needed...... Thanks to siddk007:good:
Thank you for your thread, Siddk007.
2018
Hi community,
nice to see the thread continued.
Wish all members here a happy New Year!
Greets, reinipic
@DarkSJ1998 because last discussion is locked i'm replying here, I used magisk v15.1
I have fixed the issue by flashing OOS5.0.1 then i experienced messages FC and checked someone else in oneplus forum had same problem then i flashed OB20 again and both issues are fixed.
The only weird thing is right after i flashed OOS5.0.1 in twrp the twrp showed another loading patching partition then rebooted so i couldn't flash Magisk and wipe cache do i had to flash twrp again with fastboot mode then flashed magisk and again twrp rebooted itself without any option. When i flashed OB20 same thing?! Previously soon after i flashed rom zip it used to give me to back to twrp main menu or wipe dalvik cache or reboot. Using twrp-3.2.1-0
lover said:
@DarkSJ1998 because last discussion is locked i'm replying here, I used magisk v15.1
I have fixed the issue by flashing OOS5.0.1 then i experienced messages FC and checked someone else in oneplus forum had same problem then i flashed OB20 again and both issues are fixed.
The only weird thing is right after i flashed OOS5.0.1 in twrp the twrp showed another loading patching partition then rebooted so i couldn't flash Magisk and wipe cache do i had to flash twrp again with fastboot mode then flashed magisk and again twrp rebooted itself without any option. When i flashed OB20 same thing?! Previously soon after i flashed rom zip it used to give me to back to twrp main menu or wipe dalvik cache or reboot. Using twrp-3.2.1-0
Click to expand...
Click to collapse
can u please confirm if Magisk 15.1 works with oos 5.0.1 as its not working for some users
Sent from my OnePlus 3T using XDA Labs
Siddk007 said:
can u please confirm if Magisk 15.1 works with oos 5.0.1 as its not working for some users
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
It worked but Messages FC.
lover said:
It worked but Messages FC.
Click to expand...
Click to collapse
thanks, btw this has nothing to do with message fc. try clearing data of messages app
Sent from my OnePlus 3T using XDA Labs
Siddk007 said:
thanks, btw this has nothing to do with message fc. try clearing data of messages app
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
When i was on OOS5.0.1 i did clear data of Messaging app. But did not solve the problem. Surprisingly when i did flash OB20 over it all my messages was there and was not lost
stuck on 1+ logo after flashing
followed the instructions too!!!!!!
what to do now?
[email protected]@rjnj said:
stuck on 1+ logo after flashing
followed the instructions too!!!!!!
what to do now?
Click to expand...
Click to collapse
Did you flash magisk?...or SuperSU?...
cultofluna said:
Did you flash magisk?...or SuperSU?...
Click to expand...
Click to collapse
Magisk
Now i flashed ob18 again with magisk and restored the data
But i want ob20 because some apps are giving problems in beta 18
[email protected]@rjnj said:
Magisk
Now i flashed ob18 again with magisk and restored the data
But i want ob20 because some apps are giving problems in beta 18
Click to expand...
Click to collapse
Wich version of magisk?....
Reflash OB 20 and magisk 14.6 afterwards..
OP updated with Magisk 14.6 to avoid further issues to users
Later update from app to 15.1
First off, a HUGE thank you to @autoprime (for paving the way) and @waylo (for his assistance on getting this going after I found the KDZ)
I am currently storing these in my google drive account, so please be gentle till I have a better host location:
Below are the downloads for the LG-H83020N firmware
Folder with all the LG830 firmware I have so far:
LG830 (G5)
LG-H83020N-Flashable.COMPLETE-ARB01.zip
As always, COMPLETE is 100% stock
Flash COMPLETE zip -> wipe cache partition -> flash Magisk ZIP (or SuperSU if you insist) to root and keep TWRP
OPTIONAL: After flashing, remount /system RW -> delete recovery-from-boot.p to guarantee TWRP sticks
LG-H83020N-Flashable.Bootloader-ARB01
LG-H83020N-Flashable.Modem-ARB01.zip
LG-H83020N-Flashable.Boot.zip
H830N_00_1017.kdz (HUGE Thank you to @Azul Baseem for the upload)
For instructions, follow the same instructions as you would in any other KDZ/ZIP thread. For Example
Feel free to hit thanks.
Also feel free to hit up autoprime's All in One thread HERE
Thank you very much bedwa!
Kdz link updated!
Thank you @bedwa as always.
I fear my only true contribution here is MD5 confirmation of the files:
LG-H83020N-Flashable.COMPLETE-ARB01.zip 8a49733028bef23d775bf542eb62b726
LG-H83020N-Flashable.Boot.zip ddea9d814f66266de34a154f0c7f6b41
H830N_00_1017.kdz 732b717af8d77501342be445002c4fae
Edit: Also, since someone will definitely miss it in the title, this is confirmed to still be on Anti-Rollback 1. You're free to flash back and forth between 20A if you need to Dirtycow your phone again.
Keeping me honest, I swear I'll remember them next time.
Thanks for the upload. I was able to update just fine thanks to this.
BTW... It still has H83020m mentioned in the body of the OP instead of H83020n.
shinji257 said:
Thanks for the upload. I was able to update just fine thanks to this.
BTW... It still has H83020m mentioned in the body of the OP instead of H83020n.
Click to expand...
Click to collapse
Fixed. That's what I get for using the copypasta method. Missed the one. :silly:
help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i had this issues when i try to flash it i already use uppercut
solved
running 20N , so far so good, just notice a small problem with GPS , it is a bit spotty today. @bedwa : Can you make a slim down version ? like removing LG/TMO/Google stuffs ? and reduce /system partition size ?
abced123 said:
running 20N , so far so good, just notice a small problem with GPS , it is a bit spotty today. @bedwa : Can you make a slim down version ? like removing LG/TMO/Google stuffs ? and reduce /system partition size ?
Click to expand...
Click to collapse
That would be trickier. All of these are the partition images. To make a slim zip like that I'll have to either unpack and build or unpack and attempt to repack. I might, but not likely at this time.
Thank you so much for making this. So happy to be rooted and on the latest build thanks to your hard work. =)
fc3211 said:
Thank you so much for making this. So happy to be rooted and on the latest build thanks to your hard work. =)
Click to expand...
Click to collapse
Quite welcome... It's more time consuming than hard work, but the appreciation and thanks is greatly appreciated as well.
@bedwa
I am running on rooted H83020a with TWRP and SuperSU installed. In order to upgrade to 20N by keeping all my current settings and data along with root and TWRP, what are the steps should I follow?
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
6. Restore the complete backup from LG Backup
Does this work okay? Or, do I need to do anything else, like Wipe Data/Partition etc.? Sorry for the noob question.
Hello,
If I flash boot and bootloader, will it lock my bootloader and brick the phone if I am on LineageOS?
nizarp said:
@bedwa
I am running on rooted H83020a with TWRP and SuperSU installed. In order to upgrade to 20N by keeping all my current settings and data along with root and TWRP, what are the steps should I follow?
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
6. Restore the complete backup from LG Backup
Does this work okay? Or, do I need to do anything else, like Wipe Data/Partition etc.? Sorry for the noob question.
Click to expand...
Click to collapse
Backup is always good, shouldn't have to restore it as it's updating from a previous version and doesn't wipe data when upgrading. But that's the correct process with or without #6.
azizo07 said:
Hello,
If I flash boot and bootloader, will it lock my bootloader and brick the phone if I am on LineageOS?
Click to expand...
Click to collapse
Shouldn't, but it would always be a good idea to backup beforehand. I would however only flash the bootloader, as the boot is the kernel and will be different than what LineageOS uses though.
I just boot into TWRP and flashed the complete zip and then flashed the latest SuperSU Zip. I pressed Reboot System after that, but, I am now stuck in a boot loop. Phone shows LG logo and reboots again and again.
I tried the Power button + Vol Down method, but, it doesn't work too. It gets to Factory reset screen, and after Yes and Yes, it goes to back to boot loop again. I am able to get into Download Mode and Fastboot Mode. Can I do something from here?
Can someone help please? Anyway to get into TWRP or recovery?
Sounds like you will need to LGUP or Uppercut your phone back to stock 20A. Then dirtycow back TWRP. Then try flashing the new ZIP again. Skip Supersu this time and try Magisk instead.
Thanks. I flashed back to 20A using LGUP and KDZ file. Need to dirtycow back TWRP now. I'm still wondering what went wrong in my process.
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
Click to expand...
Click to collapse
Do I need to reboot to TWRP once after flashing instead of Reboot System directly after flash? Any idea?
No, rebooting into TWRP wouldn't do anything. There's a script you might need to get into and delete prior to rebooting. But that only ensures that TWRP stays.
"After flashing, remount /system RW -> delete recovery-from-boot.p to guarantee TWRP sticks"
That having been said, I've done this before and STILL not had TWRP stay. Some recommend wiping /cache as well.
OR, again, use Magisk instead and don't use SuperSU.
Even if TWRP didn't stick, you should have been booting into system fine. You wouldn't be rooted, TWRP would be gone, but system shouldn't have been messed up. So something got borked, I'd have to guess, because of SuperSU.
New security patch update alert
Hi!!
This is my first contact with Android. I have compiled the TWRP for SM-N980F is fully working. I hope we find a custom rom to be able to install it.... I'm going to try to develop one. Let's see how it goes.
TWRP NOTE20
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Shiresp said:
Hi!!
This is my first contact with Android. I have compiled the TWRP for SM-N980F is fully working. I hope we find a custom rom to be able to install it.... I'm going to try to develop one. Let's see how it goes.
TWRP NOTE20
View attachment 5588669
Click to expand...
Click to collapse
Thanks for your effort. Please let us know, 10 days later, are there any bugs or it works as planned? Are there any special steps we shoul do to install it?
sheebee said:
Thanks for your effort. Please let us know, 10 days later, are there any bugs or it works as planned? Are there any special steps we shoul do to install it?
Click to expand...
Click to collapse
Hi Sheebee,
I haven't found any bug usung the recovery.
And about the install steps, they are the usual to install twrp.
1. Unlock bootloader.
2. Flash with Odin in AP side the twrp file.
3. Reboot in recovery Mode.
---‐-------------------
4. If you want install magisk or rom. Install it
5. Reboot settings power off.
6. Automatically turn on in recovery Mode.
7. Wipe data.
8. Reboot settings and system.
And thats all.
Sorry for no show the steps.
Byeeee
Thanks Shiresp, may the force be with you! Let us know if you find appropriate ROM.
Shiresp said:
Hi!!
This is my first contact with Android. I have compiled the TWRP for SM-N980F is fully working. I hope we find a custom rom to be able to install it.... I'm going to try to develop one. Let's see how it goes.
TWRP NOTE20
View attachment 5588669
Click to expand...
Click to collapse
Where u got sources from ?
installed smoothly until i tried to boot to system and found that my device no longer boots to system lol now having a hard time finding the stock firmware for the usa model
i think you should try installing GSI ' s to your device
deathbypvp said:
installed smoothly until i tried to boot to system and found that my device no longer boots to system lol now having a hard time finding the stock firmware for the usa model
Click to expand...
Click to collapse
It's just for n980F model. Im using a european model and works properly
Ivan2005 said:
Where u got sources from ?
Click to expand...
Click to collapse
Twrp??? From github.. c1s model....
Shiresp said:
It's just for n980F model. Im using a european model and works properly
Click to expand...
Click to collapse
idk what region model my device was but its a n980f and it just boots to the custom recovery
I have a eu version sm-n980f/ds, android 12. Twrp is installed but you can not boot the system. it remains in twrp recovery
deathbypvp said:
idk what region model my device was but its a n980f and it just boots to the custom recovery
Click to expand...
Click to collapse
When twrp boots, after that you try reboot -> system???
edsoedso said:
I have a eu version sm-n980f/ds, android 12. Twrp is installed but you can not boot the system. it remains in twrp recovery
Click to expand...
Click to collapse
I'll do it with 4 n980F and work. After twrp boot, reboot -> system
Shiresp said:
I'll do it with 4 n980F and work. After twrp boot, reboot -> system
Click to expand...
Click to collapse
I have already rooted phone but have not installed recovery. I tried to install it through magisk but unsuccessfully. Could you please be more specific in steps you follow to install it through odin? Thank you
edsoedso said:
I have already rooted phone but have not installed recovery. I tried to install it through magisk but unsuccessfully. Could you please be more specific in steps you follow to install it through odin? Thank you
Click to expand...
Click to collapse
1. In Odin uncheck auto reboot.
2. In AP side select twrp file.
3. Flash the file.
4. Press In the device volume down and power, when phone rebooting and before logo press volume up and power. When warning about custom firmware installed, release power button.
5. Into twrp flash samsung disabler 3.0 and flash magisk.
6. Option reboot -> power off.
7. Device rebooting again in twrp automatically.
8. Factory data, no factory reset.
9. Option reboot -> system
10. Device will reboot normally. But this first power on system is normal that it takes a few minutes to start the phone completely.
That's the steps I follow with all twrp I have installed.
BYE!!!
Shiresp said:
1. In Odin uncheck auto reboot.
2. In AP side select twrp file.
3. Flash the file.
4. Press In the device volume down and power, when phone rebooting and before logo press volume up and power. When warning about custom firmware installed, release power button.
5. Into twrp flash samsung disabler 3.0 and flash magisk.
6. Option reboot -> power off.
7. Device rebooting again in twrp automatically.
8. Factory data, no factory reset.
9. Option reboot -> system
10. Device will reboot normally. But this first power on system is normal that it takes a few minutes to start the phone completely.
That's the steps I follow with all twrp I have installed.
BYE!!!
Click to expand...
Click to collapse
Thank you for your prompt reply. What should I do under number 8, wipe data? Thank you!
edsoedso said:
Thank you for your prompt reply. What should I do under number 8, wipe data? Thank you!
Click to expand...
Click to collapse
Jajajaj, that's right wipe data... sorry I was typing from memory.
Shiresp said:
Jajajaj, that's right wipe data... sorry I was typing from memory.
Click to expand...
Click to collapse
Thanks a lot! Really appreciate.
Shiresp said:
Twrp??? From github.. c1s model....
Click to expand...
Click to collapse
The tree was still WIP for official release, that's the reason for which it wasn't on XDA yet. I also see you didn't post any links to sources, neither credits whatsoever.
I opened a thread for Official TWRP here, with more instructions, FAQ and everything needed.
Regards
corsicanu said:
The tree was still WIP for official release, that's the reason for which it wasn't on XDA yet. I also see you didn't post any links to sources, neither credits whatsoever.
I opened a thread for Official TWRP here, with more instructions, FAQ and everything needed.
Regards
Click to expand...
Click to collapse
sorry,
I assumed that the sources we all knew are from github. Without the work of those people developing in the repositories, the compilation of the recovery would be impossible.
I have only compiled the recovery because I needed it personally for 4 n980f.