Related
Hello, I have a Nexus 7 2013 and I love it. One of the main reasons I got this tablet is because it is a flagship Google device and it could run custom ROMs well. I want to throw Kali Pwn pad on it. When I flashed Kali, it looked like it flash successfully, but when it started it would just hang on the Google screen. Since KitKat was the latest edition of KitKat when pwnpad was launched, I decided I should try to flash stock KitKat and see what happens, it appeared like it flashed right, but when my tablet started it would still hang on the Google logo. I also tried to flash CM 11, and still the same thing happened. Every ROM I flash that is based on 4.4 hangs on the Google logo. The farthest I am able to downgrade is Android 5.0.0. My tablet came with 5.0.1 out of the box. I am currently running CM 12.1-20150814 Nightly. Another note, the only recovery I can get working TWRP MultiRom, the other verisions of TWRP (along with CWM) cant mount anything. My goal here is to get either Pwnpad or Nethunter (Nethunter would just hang on the Nexus animation, but I don't think I had enough patience that evening to let it run) installed.
Thank you for your help
Ditto!
Bump!
my device is currently on 5.0.2. i'm unable to downgrade to any Factory Image below that. any info will be helpful.
Solved
OK here is what I found. Yes you can downgrade to KitKat, if you flash this bootloader (attached) after you install your KitKat based ROM. I was able to get Kitkat NetHunter running on a deodexed ASOP ROM. The only recovery I could get running with it is the Multi-rom TWRP recovery, don't get it from the Multi-rom app, just flash the attached recovery. The weird thing is that I bought this tablet directly from Amazon, not Groupon. All talbets coming from Groupon seem to be having the TWRP mounting and the downgrading issues. I notice also that my tablet has a leaking screen. I have taken this tablet to Haiti in mid July. That might be part of the problem, but I think it is a factory defect. I bought the tablet at the start of July.
Link to the bootloader: http://www.mediafire.com/download/2s6c91j26sk9vn6/boot.img
Link to the recovery: http://www.mediafire.com/download/6hfc7yfww372lq3/TWRP_multirom_flo_201503281.img
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
It will probably be the same as for my L900 with CM13 were I have to download the update, reboot into TWRP and update manually.
Sent from my SM-G900T using Tapatalk
nezlek said:
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
Click to expand...
Click to collapse
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
nezlek said:
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
Click to expand...
Click to collapse
Automated updates work fine for me. It automatically boots onto TWRP, applies the update, and reboots.
Might be a device-specific issue. I am on the OnePlus One, and the same TWRP version (of course made for my device).
I am guessing that perhaps there is an issue reading or writing the recovery script.
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
nezlek said:
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
Click to expand...
Click to collapse
BTW, are you able to navigate to that directory in TWRP?
Oops. Right after I clicked on send I realized I didn't answer your question!!
Yes, and the zip file is there, but nothing happened. As I said, far from fatal.
I updated my opo (Bacon) with the nightly ota download and most recent twrp, after reboot I had lost my home screen (2 of 3 pages remained) and several of the apps that I had dragged to those screens.. didn't work well for me. I let the ota reboot into twrp and it seemed to proceed without troubles until the opo came back to life. (finished booting)
Galaxy S5 SM-G900T here. Wiped my phone and installed lineage-14.1-20170131-nightly-klte-signed.zip with open_gapps-arm-7.1-stock-20170131 the day it came out and it has been good so far, no crashes or freezes and all apps work good except FolderMount, no biggie. Tried to install lineage-14.1-20170207-nightly-signed.zip and is giving me an "error 7 can't install this package on top of incompatible data". Any way to fix this without factory reset? Doesn't make sense to factory reset every week for an update.
Update: Tried to reflash lineage-14.1-20170131-nightly-klte-signed.zip and got the same error. So something must have changed. The only thing I can think of is I have SU 2.79 installed.
Update 2: Removed root, restored boot and same continues. I dont want to wipe on every update.
Sent from my SM-G900T using Tapatalk
Well, now semi-automatic at any rate.
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
First, sincere THANKS to jhedfors for this priceless bit of wisdom
Getting better. Still no "automatic update" but the latest "nightly" build did fire up TWRP, and put the update zip file into the aforementioned folder, and after that, installing it was the proverbial snap. I can't speak for everyone, but I would find no horror in the folks at Lineage giving in to reality and calling the "WEEKLY" as opposed to "NIGHTLY" builds.
Hey, since the only device I happen to have running Nougat at the moment also happens to be the OLDEST device I use on a regular basis, the Complaint Department shall remain CLOSED on this one. :angel:
I have an LG G3 (d855) with working LineageOS. The updater downloads OK and the zip is indeed in /data/data/org.lineageos.updater/app_updates, but TWRP refuses to do anything about it on reboot. I can browse to the folder manually, but it does feel that something isn't firing to get TWRP to perform the install automatically.
What is the trigger for TWRP to install a specific Zip on reboot?
D
For me, One Plus 3, automatic updates don't work. Also manually installing the latest
https://mirrorbits.lineageos.org/full/oneplus3/20170214/lineage-14.1-20170214-nightly-oneplus3-signed.zip gives me an error:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Zip file is corrupt!
Updating partition details...
...done
Any idea?
I did a migration via experimental build coming from cm13 then updated to lineage 14, which worked OK.
But since then I cannot update the daily builds.
I have the "same" issue on a Nexus 6.
The updater tells me I have an update, I ok it to download. Once done, I click install, gets into recovery and stops.
Still in the recovery, if I try to manually install from the downloaded location (data/data/...), it says zip failed.
I reboot and try opening that zip on a PC and sure enough, Windows thinks it is corrupt also.
If I re-download manually from "https://download.lineageos.org/shamu" that copy opens fine on the PC and when moved to the phone (data/data/...) installs fine.
There is something corrupting the zip when the updater does its thing. ;-(
Note: This isn't a migration, I have just been updating "nightlies".
Stuck in the TWRP...
Hi everyone, in trouble :/...I have got an LG d802 and updated TWRP from 2.8.7 to 3.0.2-1, then did a boot/system backup of the current cm 13.0 and after that the "experimental" update (as described in the recent update & builds post on lineageos) from cm 13.0 to lineage 14.1 which worked.
I decided to use lineage updater to go to the latest nightly as described which must have failed (booted in TWRP an did nothing...). When installing the 14.1 nightly manually, TWRP 3.0.2-1 showed two error lines with "unknown command".
Since then I'm stuck in TWRP.
Restore of cm 13.0 backup was not possible with neither TWRP 3.0.2-1 nor 2.8.7, no errors, just wouldn't boot. I can't even find any cm 13 build... to try to back which would be an option of course.
I did wipe the system then, lineage expermental + nightly or just nightly can be installed "successfully" with TWRP 3.0.2-1 and 2.8.7 with no errors there anymore, but also the system won't boot.
Please, please help (and/or redirect me to the right thread), what can I do? Thank you!
First, you can ignore the two errors in TWRP
I've gotten them with each update I've installed, but in my case - an LG v410 tablet - I have successfully, if manually, installed three updates so far, with a few peculiarities. "Automatic" is just a nine-letter word concerning updates at this point. I can live with that.
One - it is going to download it to /data/data in the tablet's storage no matter WHAT I do. I can live with that.
Two - I seem to have to download the update at least two times before the Lineage updater accepts the fact that it is there. I can live with that, too.
Three - a "getting there and almost what I want with no major glitches" Nougat build is much preferred to a KitKat build that LG couldn't give a rat's rear end about supporting, and I can DEFINITELY live with that.
But, back to YOUR problem with being stuck in TWRP. Worst case disaster recovery scenario - ANY chance you have a non-Lineage ROM you can revert to and start over from THERE? Realize what a pain that is going to be, but... When I still had CM 12.1 on it, I once did that out of desperation when nothing else seemed to be able to get it to boot. WHY such a laborious process fixed it I have NO IDEA, but better to have a working mystery than a well understood paperweight.
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
nezlek said:
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
Click to expand...
Click to collapse
I'm hanging in TWRP, also did wipe data before. I found a full 13.0 backup, selected all but Data because of storage space..."successful"...still system won't boot...
(Power Off in TWRP doesn't even work, just reboots, if that is of any help...)...A wild guess...file system issue maybe?
Yikes
As reasonable a guess as any, I suppose. I admit I've never had TWRP refuse to power off if nothing else, no matter how badly I had screwed things up (often spectacularly) elsewhere.
ASSUME you've tried the hold the power button until it shuts off, after which it should have booted to Android when powered on trick. Or, assuming you can do so, pull the battery?
Perhaps your bootloader is the culprit. Can you just re-flash that?
I got stuck in TWRP Recovery Boot-Loop. Already had the issue before with cm14.1 beginning of december. Didn't they fix the bug or is it another one?
For the specs: I got a Nexus 4 - mako.
I did this FIX and it booted up again as it was before: https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
What's now correct update? Download and dirty install manually in TWRP?
Thanks for the post
:good:
I've NEVER encountered that issue so glad to see someone has figured out a more elegant solution. I suspect your CM 14.1 problem is / was device (build for it) specific, as NONE of my CM / Lineage devices has ever done any such thing and they've all been updated several times in the last month.
In every case, however, I 've had to MANUALLY install the update zip file from within TWRP. Far worse things have happened and since I drive a stick shift car anyway, what the problem?
I can flash back to stock via the SkipSoft Unified Android Toolkit, but not matter how far back I go, the only 3rd party ROM that will not get stuck on a never-ending bootscreen after install is CM 11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte. Not even the CM nightlies that came immediately before or after would work once this was installed.
I would like to try something newer if there is a stable Lollipop, Marshmallow, or Nougat ROM you would recommend. I don't use as a phone anymore, so I don't even need cellular data to work.
Thank you very much to anyone that even takes a look at this.
More info...
Model Number
1HZGY
Android version
4.4.4
Baseband version
L710VPUDOH1
Kernel version
3.4.104-cyanogenmod-g3652409
[email protected] #1
Mon Aug 31 16:36:33 OCT 2015
Build number
cm_d2lte-userdebug 4.4.4 KTU84Q bdfbe2c9c2
test-keys
SELinux status
Enforcing
This forum is for the Sprint S3, but I don't recognize your model number. Sprint is SPH-L710
If you do In fact have the Sprint model, I have many ROM suggestions. Including nougat ROMs. Also make sure you have the most up to date TWRP. Don't search d2lte anymore, they are no longer unified LTE builds. Sprint is d2spr, att is d2att, etc.
madbat99 said:
This forum is for the Sprint S3, but I don't recognize your model number. Sprint is SPH-L710
If you do In fact have the Sprint model, I have many ROM suggestions. Including nougat ROMs. Also make sure you have the most up to date TWRP. Don't search d2lte anymore, they are no longer unified LTE builds. Sprint is d2spr, att is d2att, etc.
Click to expand...
Click to collapse
It is definitely the sprint model. And I don't search for d2lte - I know that was a very short term thing for CM. Nothing else will flash and then boot though. Even tried using d2spr nightlies that were released after the 8/31/2015 d2lte snapshot.
I was using TWRP v3+ already but I used their official app to flash latest version, as per your advice. Now device only boots to download mode.
No worries as this is not my daily driver. I do hope to get it fixed, though.
Am I going to have to use the toolkit to flash stock and try again or is there a way to progress from here?
pravus87 said:
It is definitely the sprint model. And I don't search for d2lte - I know that was a very short term thing for CM. Nothing else will flash and then boot though. Even tried using d2spr nightlies that were released after the 8/31/2015 d2lte snapshot.
I was using TWRP v3+ already but I used their official app to flash latest version, as per your advice. Now device only boots to download mode.
No worries as this is not my daily driver. I do hope to get it fixed, though.
Am I going to have to use the toolkit to flash stock and try again or is there a way to progress from here?
Click to expand...
Click to collapse
Wow never seen that from installing TWRP. Do you have the triband model by chance?
I would try Odin back to stock and flash TWRP again. I usually get TWRP right from their site.
Are you wiping data and factory resetting (including internal storage) before trying to boot these ROMs? It is required for the newer ROMs. Octos has a good nougat build. Commotio is pretty solid too. I'm running lineage right now and it's perfect.
https://forum.xda-developers.com/galaxy-s3-sprint/development/rom-octos-t3532535/post70408050
https://forum.xda-developers.com/ga...samsung-galaxy-s3-vanir-t3006645/post58268135
https://download.lineageos.org/d2spr
https://dl.twrp.me/d2spr/
madbat99 said:
Wow never seen that from installing TWRP. Do you have the triband model by chance?
I would try Odin back to stock and flash TWRP again. I usually get TWRP right from their site.
Are you wiping data and factory resetting (including internal storage) before trying to boot these ROMs? It is required for the newer ROMs. Octos has a good nougat build. Commotio is pretty solid too. I'm running lineage right now and it's perfect.
https://forum.xda-developers.com/galaxy-s3-sprint/development/rom-octos-t3532535/post70408050
https://forum.xda-developers.com/ga...samsung-galaxy-s3-vanir-t3006645/post58268135
https://download.lineageos.org/d2spr
https://dl.twrp.me/d2spr/
Click to expand...
Click to collapse
That was a first for me too. TWRP has always been fairly easy to install and update.
Not sure if this is the triband but I assume that is more expensive and that it is not the standard model Sprint was pushing, so I doubt it. Is there a way for me to check?
Yes I was wiping data, cache, system and internal storage wit each install. I had an AT&T Samsung Galaxy S3 and an AT&T LG G3 that I did a lot of flashing on, so I am familiar with the basics. I tried flashing lineage and commotio recently with no luck and had to install the final CM11 snapshot again.
Will flash back to stock and will try again. If I recall, the final update is only OTA. Do I need to take it before moving on?
Thanks for your help!
pravus87 said:
That was a first for me too. TWRP has always been fairly easy to install and update.
Not sure if this is the triband but I assume that is more expensive and that it is not the standard model Sprint was pushing, so I doubt it. Is there a way for me to check?
Yes I was wiping data, cache, system and internal storage wit each install. I had an AT&T Samsung Galaxy S3 and an AT&T LG G3 that I did a lot of flashing on, so I am familiar with the basics. I tried flashing lineage and commotio recently with no luck and had to install the final CM11 snapshot again.
Will flash back to stock and will try again. If I recall, the final update is only OTA. Do I need to take it before moving on?
Thanks for your help!
Click to expand...
Click to collapse
Shouldn't need all updates, but it's not a bad idea. If the model has a "t" on the end then it's a triband. That one can be troublesome.
madbat99 said:
Shouldn't need all updates, but it's not a bad idea. If the model has a "t" on the end then it's a triband. That one can be troublesome.
Click to expand...
Click to collapse
Sorry for the delay. I had some issues restoring stock with one PC and was too stubborn to try on a different PC until yesterday.
Was able to get stock working, rooted and I installed TWRP 2.7.x and then updated to the latest (3.1.x). I then wiped all partitions from TWRP and sideload installed latest Commotio and opengapps. Same issue - stuck on the boot screen (animated water).
Anything left to try? Confirmed it is not the triband. Thanks again.
UPDATE: just tested with latest CarbonROM. Issue persists
pravus87 said:
Sorry for the delay. I had some issues restoring stock with one PC and was too stubborn to try on a different PC until yesterday.
Was able to get stock working, rooted and I installed TWRP 2.7.x and then updated to the latest (3.1.x). I then wiped all partitions from TWRP and sideload installed latest Commotio and opengapps. Same issue - stuck on the boot screen (animated water).
Anything left to try? Confirmed it is not the triband. Thanks again.
UPDATE: just tested with latest CarbonROM. Issue persists
Click to expand...
Click to collapse
I've been stuck on boot animation on a few fresh installs of ROMs. If I let it sit there for 5 mins or so then hold power until it reboots, it usually boots up. Where KitKat ROMs used to say building dalvik cache, or whatever the particular ROM had, newer nougat ROMs do not. The boot animation plays while it establishes art caches. It can take awhile on a fresh install.
madbat99 said:
I've been stuck on boot animation on a few fresh installs of ROMs. If I let it sit there for 5 mins or so then hold power until it reboots, it usually boots up. Where KitKat ROMs used to say building dalvik cache, or whatever the particular ROM had, newer nougat ROMs do not. The boot animation plays while it establishes art caches. It can take awhile on a fresh install.
Click to expand...
Click to collapse
Tried flashing Commotio again and held down power to reboot after about 5min on boot screen. Waited over 10 mins the second time and still no luck. Just reboot again and will give it until the battery dies. Let me know if you have any other suggestions. Thanks again.
UPDATE: Tried with latest CarbonROM and latest LineageOS builds as well. None will boot. Old CM11 snapshot build still installs and boots without issue.
pravus87 said:
Tried flashing Commotio again and held down power to reboot after about 5min on boot screen. Waited over 10 mins the second time and still no luck. Just reboot again and will give it until the battery dies. Let me know if you have any other suggestions. Thanks again.
UPDATE: Tried with latest CarbonROM and latest LineageOS builds as well. None will boot. Old CM11 snapshot build still installs and boots without issue.
Click to expand...
Click to collapse
Have you formatted data? Switching between KitKat and nougat you have to wipe internal storage.
I would "format data" not just wipe (in case of any encryption) and also do a factory reset in recovery.
madbat99 said:
Have you formatted data? Switching between KitKat and nougat you have to wipe internal storage.
I would "format data" not just wipe (in case of any encryption) and also do a factory reset in recovery.
Click to expand...
Click to collapse
Yes - I have wiped everything, including internal storage and used the "format data" option. I have tried ADB sideloading each of the ROMs mentioned with everything wiped. I've also tried removing the external SD card, copying the ROMs to it from a PC, reinserting into the phone and attempting install that way. Still, no luck.
pravus87 said:
Yes - I have wiped everything, including internal storage and used the "format data" option. I have tried ADB sideloading each of the ROMs mentioned with everything wiped. I've also tried removing the external SD card, copying the ROMs to it from a PC, reinserting into the phone and attempting install that way. Still, no luck.
Click to expand...
Click to collapse
Wow, that is thorough. Maybe make sure non of your ROM or gapps packages are corrupt (check md5 or sha1, etc.)
What gapps are you using? I usually use open gapps for 7.1x arm, mini or micro. Beans gapps also work well. Just make sure they are for 7.1.
Maybe try to boot the ROM without gapps ( just a shot in the dark). Are you flashing any other mods with it? I think Commotio comes rooted with magisk.
madbat99 said:
Wow, that is thorough. Maybe make sure non of your ROM or gapps packages are corrupt (check md5 or sha1, etc.)
What gapps are you using? I usually use open gapps for 7.1x arm, mini or micro. Beans gapps also work well. Just make sure they are for 7.1.
Maybe try to boot the ROM without gapps ( just a shot in the dark). Are you flashing any other mods with it? I think Commotio comes rooted with magisk.
Click to expand...
Click to collapse
I have tried with 7.0 and 7.1 opengapps arm pico but I haven't been doing so during troubleshooting so as to isolate the issue. I tried once with Commotio and once with CarbonROM in case they needed it for some reason, but since no luck, I figure I'll wait to flash gapps once I get a successful boot.
I downloaded all ROMs with Free Download Manager, which does a pretty good job at maintaining file integrity and working through connection hangups, but I will try downloading with Firefox by itself and verifying the checksums to be sure. Will get back to you - thanks again.
pravus87 said:
I have tried with 7.0 and 7.1 opengapps arm pico but I haven't been doing so during troubleshooting so as to isolate the issue. I tried once with Commotio and once with CarbonROM in case they needed it for some reason, but since no luck, I figure I'll wait to flash gapps once I get a successful boot.
I downloaded all ROMs with Free Download Manager, which does a pretty good job at maintaining file integrity and working through connection hangups, but I will try downloading with Firefox by itself and verifying the checksums to be sure. Will get back to you - thanks again.
Click to expand...
Click to collapse
Happy to help
madbat99 said:
Happy to help
Click to expand...
Click to collapse
I downloaded Commotio and CarbonROM again and verified the md5s. All good there. I wiped everything except OTG again and tried installing from the SD card (formatted as well before the ROMs were copied over). Still stuck on boot animations. I attempt a power button restart after about 10mins a couple times then I let it sit for 30+min without any success.
Hope we haven't reached the end of the line yet. I'm very curious about what could be causing this.
pravus87 said:
I downloaded Commotio and CarbonROM again and verified the md5s. All good there. I wiped everything except OTG again and tried installing from the SD card (formatted as well before the ROMs were copied over). Still stuck on boot animations. I attempt a power button restart after about 10mins a couple times then I let it sit for 30+min without any success.
Hope we haven't reached the end of the line yet. I'm very curious about what could be causing this.
Click to expand...
Click to collapse
Well I'm stumped. Have you tried LineageOS? These ROMs are all based on Lineage. Sometimes there is a bad nightly that refuses to clean flash and it spreads to all other ROMs. Maybe try a build from a few weeks back (or even a month if you can find one) and if that boots then you can update to the newest with a dirty flash.
I see you did try LineageOS and tried some older builds.
Well, I can maybe make a backup of a fresh install after first boot and upload it for you. You can try restoring it on your phone and see if it boots. You would have to have the folders created on your phone (or external sd card). Like
"TWRP/backups/* your phones serial number*/*name of backup*"
Obviously without the quotes and stars and with your devices actual serial number. Only thing is, backups are pretty big files.
madbat99 said:
Well I'm stumped. Have you tried LineageOS? These ROMs are all based on Lineage. Sometimes there is a bad nightly that refuses to clean flash and it spreads to all other ROMs. Maybe try a build from a few weeks back (or even a month if you can find one) and if that boots then you can update to the newest with a dirty flash.
I see you did try LineageOS and tried some older builds.
Well, I can maybe make a backup of a fresh install after first boot and upload it for you. You can try restoring it on your phone and see if it boots. You would have to have the folders created on your phone (or external sd card). Like
"TWRP/backups/* your phones serial number*/*name of backup*"
Obviously without the quotes and stars and with your devices actual serial number. Only thing is, backups are pretty big files.
Click to expand...
Click to collapse
I did not try Lineage or Vanir again like I did Commotio and CarbonROM to verify the md5s. I will try them and some older builds of each.
I sincerely appreciate the offer. I would certainly be willing to download a large backup if you would be willing to take the time to clean install and upload. Let me try the remaining steps you listed first, though. Don't want you to have to spend time doing all that if we can get it working another way.
Thanks again. Will keep you posted!
Downloaded, verified and copied all these files to a freshly formatted SD card, inserted into the phone, booted TWRP 3.1.1-0 and wiped Dalvik / ART Cache, System, Data, Internal Storage, and Cache before each install:
B140-commotio-d2spr-10-17-2017.zip
CARBON-CR-5.1-MOO-RELEASE-d2spr-20171018-0000.zip
cm-11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte.zip
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip
lineage-14.1-20170731-nightly-d2spr-signed.zip
lineage-14.1-20171030-nightly-d2spr-signed.zip
OCT-N-WEEKLY-20170811-2058-d2spr.zip
vanir_d2spr_5.1.1.102615.zip
vanir_d2spr_6.0.122916.zip
vanir_d2spr_7.0.010417.zip
vanir_d2spr_7.1.101817.zip
Only ol' reliable (CM 11 d2lte 8/31/15 snapshot) will boot.
This phone was fully updated with all OTA updates before I ever attempted to root, install a custom recovery or ROM about a year or so ago. I remember having issues even then, not being able to get any CM version to boot except for that one, which was already old at the time.
For kicks, I tried dirty flashing the CM 12 d2spr 11/17/15 snapshot over ol' reliable in hopes that it would boot and I would be able to dirty flash all the way to an Oreo build. It didn't work.
Also, each time I have flashed back to stock to retry, I have used the *NJ2 build.
Not sure if any of that matters, but trying to think of anything that may help pinpoint the issue.
If no other ideas, I would like to take you up on your offer and try a TWRP backup of a fresh install of any recent, stable ROM from you device, if you would be so kind to upload.
Thanks again for the help. For what it is worth, it has been fun troubleshooting this. I'm too afraid to do anything with my S8, but miss the fun I had with my AT&T S3 (never had any issues with custom ROMs, but I also didn't take all the OTA updates) and my AT&T LG G3, which got blue screen disease.
pravus87 said:
Downloaded, verified and copied all these files to a freshly formatted SD card, inserted into the phone, booted TWRP 3.1.1-0 and wiped Dalvik / ART Cache, System, Data, Internal Storage, and Cache before each install:
B140-commotio-d2spr-10-17-2017.zip
CARBON-CR-5.1-MOO-RELEASE-d2spr-20171018-0000.zip
cm-11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte.zip
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip
lineage-14.1-20170731-nightly-d2spr-signed.zip
lineage-14.1-20171030-nightly-d2spr-signed.zip
OCT-N-WEEKLY-20170811-2058-d2spr.zip
vanir_d2spr_5.1.1.102615.zip
vanir_d2spr_6.0.122916.zip
vanir_d2spr_7.0.010417.zip
vanir_d2spr_7.1.101817.zip
Only ol' reliable (CM 11 d2lte 8/31/15 snapshot) will boot.
This phone was fully updated with all OTA updates before I ever attempted to root, install a custom recovery or ROM about a year or so ago. I remember having issues even then, not being able to get any CM version to boot except for that one, which was already old at the time.
For kicks, I tried dirty flashing the CM 12 d2spr 11/17/15 snapshot over ol' reliable in hopes that it would boot and I would be able to dirty flash all the way to an Oreo build. It didn't work.
Also, each time I have flashed back to stock to retry, I have used the *NJ2 build.
Not sure if any of that matters, but trying to think of anything that may help pinpoint the issue.
If no other ideas, I would like to take you up on your offer and try a TWRP backup of a fresh install of any recent, stable ROM from you device, if you would be so kind to upload.
Thanks again for the help. For what it is worth, it has been fun troubleshooting this. I'm too afraid to do anything with my S8, but miss the fun I had with my AT&T S3 (never had any issues with custom ROMs, but I also didn't take all the OTA updates) and my AT&T LG G3, which got blue screen disease.
Click to expand...
Click to collapse
Mine is on nj2 as well. Mine takes a little while to boot, but not hours lol.
I'll see if I can backup a fresh build today. I won't be able to upload until tomorrow (no wifi at home right now). I can likely upload when I get to work, I get there pretty early. I'll pm you a link when it's done.
Really don't know why that's the only thing that will boot for you. It has been fun trying to get it to though.
I'll flash LineageOS (most recent) with open gapps mini. I'll boot to the setup wizard and then make a backup. Hope this works, mostly cause I'm kinda out of ideas, lol.
madbat99 said:
Mine is on nj2 as well. Mine takes a little while to boot, but not hours lol.
I'll see if I can backup a fresh build today. I won't be able to upload until tomorrow (no wifi at home right now). I can likely upload when I get to work, I get there pretty early. I'll pm you a link when it's done.
Really don't know why that's the only thing that will boot for you. It has been fun trying to get it to though.
I'll flash LineageOS (most recent) with open gapps mini. I'll boot to the setup wizard and then make a backup. Hope this works, mostly cause I'm kinda out of ideas, lol.
Click to expand...
Click to collapse
Thank you. No rush - whenever you have time.
I don't get it either. I waited a long time to post about it because I assumed there was something simple I was overlooking that I would eventually figure out. Not sure this will work if nothing else has, but I can't wait to give it a shot.
First time messing with this phone
followed the instructions for unlocking bootloader, installing TWRP, and rooting here: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
Successfully unlocked bootloader, flashed TWRP, but now hung up on SuperSU.
Flashed SuperSU VV2.82 zip from http://www.supersu.com/download in TWRP
Wiped dalvik and cache
reboot
Now it's been about 10 minutes. Blank screen and blue LED.
Hold power until it reboots again, Android sometimes has issues with new boot.imgs at first
l3ones said:
Hold power until it reboots again, Android sometimes has issues with new boot.imgs at first
Click to expand...
Click to collapse
I did, three times.
I ended up flashing the latest complete OTA to get it back to being able to boot.
Are you on Oreo? I don't know if SuperSU is compatible with it. I switched to Magisk a few weeks ago.
Macusercom said:
Are you on Oreo? I don't know if SuperSU is compatible with it. I switched to Magisk a few weeks ago.
Click to expand...
Click to collapse
was on the latest stock OTA, which was 8.0.0
Flashed Mgisk after flashing the latest OTA, and everything is working swimmingly
Exact Same thing happened to me last night.
And I lost my internal sdcard.
Eventually flashed stock recovery didn't do anything different so flash twrp again and got sdcard back.
It was a strange one.
Now I'm waiting for an update or the right file for root.
Maybe this has something to do with Keymaster?
So, I've been trying to get my OP5t working for a solid six hours straight, and I'm just about to loose my mind.
I'm sorry if this isn't the right place to post this. I've always just sorta lurked about in here.
Here's the deal for my OP5t.
Now I'm stuck in a situation where I can get my phone to boot on all of the OOS versions I've mentioned, but always without root. And If I do manage to get it booting, I end up loosing TWRP and having to reflash it through fastboot.
Since I've always just relied on Titanium backup (yes I know, how silly) I've never had any trouble restoring my backups, but since I've now lost root and being unable to obtain it again, I'm locked out of all my sweet app data. It's all a bit messy now, and I think I'm begging to repeat previous steps and combinations, but here's a list of what I've tried. I really hope some white knight comes to the rescue.
It all happened when I tried doing a clean flash wiping caches, data and system of OOS 5.0.3 (coming from the latest official OOS Nougat build). It all started when I tried to flash the magisk 15.3 after this boot, which resulted in ERROR 1.
- I've tried installing both the old version the previous nougat build and the two most recent stable oreo ones. Wiping thoroughly inbetween even, since at this point I have nothing left to loose.
- Whenever I try to flash magisk 15,1 /3 or 4 I get error 1. Whenever I try to flash supersu (s.82 included the modded SR5 version) I Just don't get root or end up in an endless +1 screen (before the spinner) for 12+ minutes.
- I've tried flashing the stock boot.img
- I've tried all of the above in combination with bluspark recovery 8.61 and 69 + the r100 kernel
- I've tried using codeworks cheesburger and dumpling recoveries
What am I missing here? I assume my phone is encrypted since it asks for a code to open TWRP.
I've never had any issues so grave that I couldn't just search my way through it, but this time I'm at my wits end, and just about ready to settle(tm) for no root.
I've never tried exporting a log, but I sense that I do that from TWRP and then grab it via a file manager from some folder?
Use codeworkx dumpling TWRP, dirty flash your ROM, boot it once, then reboot to recovery and flash Magisk 15.3. Should be all you need.
For Nougat, I think it's better to flash Magisk 14, on some ROMs.
New apps
Great information provided by many users. I have just joined this group and read many experts advice. Thanks
Latest SuperSU (beta 2.85 i believe) don't work on OP5T Oreo update (stable or Open Beta). Don't know why, but I had to use Magisk. ANd I must say, I'm pretty happy with it, too!
Elfomze said:
So, I've been trying to get my OP5t working for a solid six hours straight, and I'm just about to loose my mind.
I'm sorry if this isn't the right place to post this. I've always just sorta lurked about in here.
Here's the deal for my OP5t.
Now I'm stuck in a situation where I can get my phone to boot on all of the OOS versions I've mentioned, but always without root. And If I do manage to get it booting, I end up loosing TWRP and having to reflash it through fastboot.
Since I've always just relied on Titanium backup (yes I know, how silly) I've never had any trouble restoring my backups, but since I've now lost root and being unable to obtain it again, I'm locked out of all my sweet app data. It's all a bit messy now, and I think I'm begging to repeat previous steps and combinations, but here's a list of what I've tried. I really hope some white knight comes to the rescue.
It all happened when I tried doing a clean flash wiping caches, data and system of OOS 5.0.3 (coming from the latest official OOS Nougat build). It all started when I tried to flash the magisk 15.3 after this boot, which resulted in ERROR 1.
- I've tried installing both the old version the previous nougat build and the two most recent stable oreo ones. Wiping thoroughly inbetween even, since at this point I have nothing left to loose.
- Whenever I try to flash magisk 15,1 /3 or 4 I get error 1. Whenever I try to flash supersu (s.82 included the modded SR5 version) I Just don't get root or end up in an endless +1 screen (before the spinner) for 12+ minutes.
- I've tried flashing the stock boot.img
- I've tried all of the above in combination with bluspark recovery 8.61 and 69 + the r100 kernel
- I've tried using codeworks cheesburger and dumpling recoveries
What am I missing here? I assume my phone is encrypted since it asks for a code to open TWRP.
I've never had any issues so grave that I couldn't just search my way through it, but this time I'm at my wits end, and just about ready to settle(tm) for no root.
I've never tried exporting a log, but I sense that I do that from TWRP and then grab it via a file manager from some folder?
Click to expand...
Click to collapse
Same kind of problem here. After clean flashing Oreo can't root anymore. Flashing Magisk ends up in Bootloop. Tried various combinations of TWRPs and Magisk versions, no use. :/
Kunjuuuz said:
Same kind of problem here. After clean flashing Oreo can't root anymore. Flashing Magisk ends up in Bootloop. Tried various combinations of TWRPs and Magisk versions, no use. :/
Click to expand...
Click to collapse
Okay so I managed to figure it out. The problem seemed to be that where one TWRP version could flash magisk, another wouldn't be able to decrypt the phone properly, which I think is what caused the bootloops/non sticky root for me (though I'm by no means sure of this).
I managed to get it worked out by fiddling around a bit more with the different versions and using the a Remix ROM to remove the pin (which I probably should've done initially). I also noticed that I didn't originally pay attention to the fact that codeworks' (non universal) recoveries are aimed at 8.0 and 8.1 respectively, which might have complicated things a bit more for me.
Sorry for spamming up the thread. I hope you figure things out though
The latest SuperSu does not work with 8.1 for us and some other (or all other) 8.1 phones.
And... SuperSu is no longer in development.
Rumor has it a slightly older SuperSu version works in 8.1 but I never got around to trying it and forget the version # now.
And Lineage has not released a SuperSu/superuser for 8.1 yet.
It bums me out because I want that Magisk alternative.
Not a fan of Magisk yet.
Elfomze said:
Okay so I managed to figure it out. The problem seemed to be that where one TWRP version could flash magisk, another wouldn't be able to decrypt the phone properly, which I think is what caused the bootloops/non sticky root for me (though I'm by no means sure of this).
I managed to get it worked out by fiddling around a bit more with the different versions and using the a Remix ROM to remove the pin (which I probably should've done initially). I also noticed that I didn't originally pay attention to the fact that codeworks' (non universal) recoveries are aimed at 8.0 and 8.1 respectively, which might have complicated things a bit more for me.
Sorry for spamming up the thread. I hope you figure things out though
Click to expand...
Click to collapse
Locking the bootloader, wiping, and unlocking the bootloader again fixed the issue for me.
There are unfortunately no ROMs specifically for this device yet, but has anyone tried to use a generic treble ROM on this device?
Thanks in advance
I have tried several treble ROMs, the majority don't even boot. Lineage os worked but was buggy. The more stable one was Havoc, if I remember correctly.
I was interested in the Q developer ROM but it didn't work. I'm back to the stock pie Rom, since there is no Netflix HD support on those treble roms.
gtaadicto92 said:
I have tried several treble ROMs, the majority don't even boot. Lineage os worked but was buggy. The more stable one was Havoc, if I remember correctly.
I was interested in the Q developer ROM but it didn't work. I'm back to the stock pie Rom, since there is no Netflix HD support on those treble roms.
Click to expand...
Click to collapse
Hi Mate, I've been trying to flash a working GSI rom but had no success so far(have an SM-T830). In the past have built ROMs for Tab A 10.1 and flashed them many times with TWRP and Odin so I just cannot understand am I retarded to not being able to flash a working one or what? Have managed to put TWRP 3.3.0.0 and TWRP 3.3.0.1 on the device. Have tried my own arm64_aonly image first. Then an original AOSP one, then a Lineage OS version, at the moment I am just downloading Havoc. The result (apart from the havoc) was always the same. The flashing went through successfully and when I rebooted into system the very fist image came up and boot looped from there. I am always able to go back to TWRP and try another image or through odin can restore the factory image but none of the GSI images seem to be working. So, here is my question. As you managed to get a Lineage and Havoc working, can you tell by looking at it what am I doing wrong please:
1.: OEM unlock
2.: TWRP install with odin
3.: Boot straight into TWRP to prevent being overwritten
4.: TWRP: format data
5.: Flash system image (arm64_aonly)
From here have tried so many things like,
- booting straight into system
- booting back to recovery
- flashing the force_decryptor or how the hell is that called
- formatted data again as the decryptor suggests
The result was always the same, boot looped from the very first image. It seems like that the image is not getting flashed and even if TWRP says was flashed right it is just not there. I'm literaly pulling my hair as it was so easy and straight forward with the Tab A 10.1, but with this ….. thanks for your answer in advance
anyone have any luck with treble GSIs? i can only get arrowos to boot and even then i cant install gapps.
droidbot1337 said:
anyone have any luck with treble GSIs? i can only get arrowos to boot and even then i cant install gapps.
Click to expand...
Click to collapse
I used AOSP 9.0 and LineageOS 16 with OpenGApps Pico and both work but are very buggy.
After hours of trying to figure this out myself i ended up finding two ROMs that work for me. I was running stock Android 9 with september's security updates when testing these out:
Roms that i tried, that did NOT work:
BlissOS
ArrowOS
Lineage16
The ROMs that DID work for me were:
phunsson's Treble Experimentations
microG ufOfficial
The only 2 bugs that i've seen so far have been a small graphical glitch of quickettings not staying within the bounds of the pulldown and MTP not working at all. These are both present in both ROMs (The microg ROM uses phhusson's rom as the base). Neither of these bother me all that and i'm very happy to be able to move to microg and not have all the google/samsung bloat hogging my tablet and constantly trying to ping their motherships.
Here's a great list of Generic System Image (GSI) ROMs that you can click scroll through and try downloading and flashing to your device to see if you have any luck.
My process of installing phunsson's GSI ROM:
Reboot to TWRP,
Do a factory reset (Wipe > "Swipe to Do Factory Reset")
Install Image
Reboot
Took about a minute and a half displaying the bootanimation before it got to the home screen for the first time. If it's loading for more than 5 minutes then that ROM definitely isn't going to work with your device.
Hope this helps someone out there trying to get away from their bloated Samsung One UI.
motomotomotoG said:
After hours of trying to figure this out myself i ended up finding two ROMs that work for me. I was running stock Android 9 with september's security updates when testing these out:
Roms that i tried, that did NOT work:
BlissOS
ArrowOS
Lineage16
The ROMs that DID work for me were:
phunsson's Treble Experimentations
microG ufOfficial
The only 2 bugs that i've seen so far have been a small graphical glitch of quickettings not staying within the bounds of the pulldown and MTP not working at all. These are both present in both ROMs (The microg ROM uses phhusson's rom as the base). Neither of these bother me all that and i'm very happy to be able to move to microg and not have all the google/samsung bloat hogging my tablet and constantly trying to ping their motherships.
Here's a great list of Generic System Image (GSI) ROMs that you can click scroll through and try downloading and flashing to your device to see if you have any luck.
My process of installing phunsson's GSI ROM:
Reboot to TWRP,
Do a factory reset (Wipe > "Swipe to Do Factory Reset")
Install Image
Reboot
Took about a minute and a half displaying the bootanimation before it got to the home screen for the first time. If it's loading for more than 5 minutes then that ROM definitely isn't going to work with your device.
Hope this helps someone out there trying to get away from their bloated Samsung One UI.
Click to expand...
Click to collapse
Did AOSP 10.0 work for you? I haven't been able to get it to boot. Strangely AOSP 9 and LOS 16 are the only ones I've had luck with.
@last1youlove whoa! You got LOS to work? What kind of magician are you? That one never booted for me. The only ROM I got working was ArrowOS and it has a few bugs. I really want to get HavocOS to work but it's a no-go!
droidbot1337 said:
@last1youlove whoa! You got LOS to work? What kind of magician are you? That one never booted for me. The only ROM I got working was ArrowOS and it has a few bugs. I really want to get HavocOS to work but it's a no-go!
Click to expand...
Click to collapse
Strange, How did you go about installing it?
last1youlove said:
Did AOSP 10.0 work for you? I haven't been able to get it to boot. Strangely AOSP 9 and LOS 16 are the only ones I've had luck with.
Click to expand...
Click to collapse
I have not. I just really wanted an AOSP based ROM and i had gotten to the point where i had reflashed the stock firmware 3 times through ODIN because I messed up 1 thing or another. So once i got a functional ROM that worked great I just decided to stick to it. Also I don't think Android 10 has Xposed support yet, and i need that in order to enable Signature Spoofing for MicroG's FakeStore.