Apologies for duplicating this post but the original forum was apparently the wrong spot for this.
I need either some pointers or a reference to a how-to, if you please.
My Nexus 6 is currently running Pure Nexus 6.0.1-2060821-official, security patch 8/5/2016 with ElementalX kernel 3.10.40-ElementalX-N6-3-20.
I've updated Pure Nexus before through TWRP and all went well, but those efforts never involved updating the kernel too. I've attempted to flash the new kernel, the rom and the google apps, but the phone goes into a never ending boot effort and it's a tussle getting back to recovery mode as it tends to boot loop. The flashes are preceded by clearing Delvik and cache and cleared again after the flash.
Is the order of flashing off or perhaps not enough clearing of other items such as system? Or is a factory reset needed?
Kind of lost on this one and can't seem to string together enough search terms to find help specific to the problem.
Any help would be appreciated.
The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.
zelendel said:
The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.
Click to expand...
Click to collapse
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?
jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?
Click to expand...
Click to collapse
You are doing a full wipe right? Wiping system and data before flashing?
Also encryption could be an issue. If your device in encrypted or the kernel did not remove the force encryption flag. That could take awhile as well.
jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215
Click to expand...
Click to collapse
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?
Pkt_Lnt said:
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?
Click to expand...
Click to collapse
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.
Needs Nougat bootloader and latest radio--flash in TWRP. This allows flashing N ROMs while will still work with all MM or even 5.1 ROMs
http://batakang.com/ftp/devs/mhous33/shamu/bootloaders/shamu_bootloader_moto-apq8084-72.01.zip
http://batakang.com/ftp/devs/mhous33/shamu/7.1.1/shamu_baseband_D4.01-9625-05.44+FSG-9625-02.115.zip
jlfesslerkc said:
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.
Click to expand...
Click to collapse
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.
Try reverting to stock
Install stock firmware using adb
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
Hi... Save your internal storage before processing. Just in case... TWRP 2.8.5.0 is pre nougat and incompatible.
jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
You should really update the bootloader/radio to the latest once you update the TWRP. Updating the bootloader/radio will not affect your internal storage.
Pkt_Lnt said:
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.
Click to expand...
Click to collapse
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?
jlfesslerkc said:
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?
Click to expand...
Click to collapse
yup
Item 1.8 and 1.9 here
Pkt_Lnt said:
yup
Item 1.8 and 1.9 here
Click to expand...
Click to collapse
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?
jlfesslerkc said:
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?
Click to expand...
Click to collapse
That is what Titanium Backup (and Restore) does, yes.
Related
I am running Gigglebread 7.0.2 on my T-Mobile N1. I am getting ready to go to Italy for a few weeks and wanted to see what would happen to my phone with another carrier's SIM. So, I inserted the AT&T SIM from my work blackberry and had some issues, but got it working after the APN was sorted out.
When I swapped the T-Mobile SIM back, all of my Google accounts had forgotten their credentials. I rebooted once just to see and no change. So, I thought, easy, restore nandroid from earlier in the day. The restore went fine, no errors, no wipe of cache or dalvik only now I appear to have no gapps (no market, unable to add google accounts, shortcuts on desktop don't work). Again, no problem. I've seen this before so I wiped cache and dalvik from CW 2.5.x recovery and installed dta2sd (sometimes it helps) and then 20110307 gapps. Reboot and still no gapps functionality.
So, I brought out the bigger hammer (after a couple of tries at gapps install) and wiped data/factory, dalvik, cache partition, restored nandroid, reboot. Still no gapps. Repeated the same wipe, restore nandroid, install dta2sd, install gapps, reboot. Still no gapps.
Now I'm getting desperate. Less than 72 hours till plane leaves! I next changed to AmonRA recovery and wiped, various nandroid/gapps/dta2sd combinations and still no gapps functionality.
Switched to CW 3, yeah, I know... And wiped cache, dalvik, factory/data, and even formatted system. Various installations and it still refused to install gapps.
I next tried the CW 2.x factory/data wipe, dalvik, cache, and then installed Gigglebread 7.0.2, dta2sd beta4(like always), and gapps 20110307 and rebooted. As expected, sterile phone, touch android, and then I'm prompted for google account. I skip that and sure enough, market is back and I can add google accounts.
AUGH. Unless someone has a suggestion, I'm probably going to have to do a full reinstall tomorrow. I've been wanting to do it, but not this close to a trip.
On a side note, is it normal for a swap of the SIM card to wipe out my account settings? I will make sure from now on that my TI b/u is up to date.
Rick
Infuriating as it is, especially as you must have so much to do already, a re-install might be best at this point. Trying to troubleshoot and avoid doing this could just mean more wasted time in the long run.
DirkGently1 said:
Infuriating as it is, especially as you must have so much to do already, a re-install might be best at this point. Trying to troubleshoot and avoid doing this could just mean more wasted time in the long run.
Click to expand...
Click to collapse
Yup, already on that path. I fell asleep last night or I would have finished. I did manage to get a TI backup of many of my apps (gmail especially) so hopefully I won't have to set those back up again since I'm using two-factor auth on all of them (10 accounts) and don't want to go through the process of invalidating and recreating the app specific passwords again.
Rick
I am also facing the same problem now.
I was on Cyanogen Mod 7.0.3 when some application weirdly started building up data on system storage. There was only 16 KB of space left and it became un-responsive. So I restarted it, only to find the looping Cyan logo.
Fortunately I had a backup from 15 days back, which was CM 7.0.2. So, I flashed that and I thought I am back. But, I found Market was not working, in fact it was not even showing up in the app list. Also, Contacts data was wiped out and when I tried to check out the account and settings, google account option itself was not showing up.
I tried flashing 7.0.3 + latest gapps package using Rom manager, that did not work. I tried a clean wipe and flashed 7.0.2 from my backup, no effect. Then flashed latest gapps again, no change.
It is frustrating now. It looks as if google is not supporting my device anymore.
Any suggestion is welcome.
Did you check md5 from your gapps package?
You said you were using ROM manager so I suppose you are on cwm but are you on cwm 3.x or are you on cwm 2.5.1.4? If your on 3.x then downgrade if not then maybe try Amon-RA with temasek system wipe maybe just making a clean install of your recovery might fix it.
Also you might want to try flashing from recovery instead of ROM manager. Just for the fun of it.
Might also need to partition sd card again as CWM 3.0 probably fubar it.
My phone will currently not boot bast the CyanogenMod boot screen.
I flashed my phone several months ago to CM10.1 It was the update that patched the "masterkey" bug. I have been using it daily since then with no problems.
Today, I turn my phone on, and it just hangs at the boot animation.
There were no significant changes since the last time it was powered on. I think I installed McPixel from the humblebundle, and uninstalled a game from the playstore called Krog. No setting changes of any significance.
I've tried booting into safestrape and deleting both the cache and the dalvik cache, neither has helped. My stock rom still loads just fine, but i had factory reset it quite a while ago. I do have a backup of the rom from about 40 days ago i can try restoring, but i would love a more nondestructive way to fix this.
Try booting into safestrap, wiping system, cache, and dalvik, then reinstall the ROM and gapps.
Droid 4 - Avatar
kwyrt said:
Try booting into safestrap, wiping system, cache, and dalvik, then reinstall the ROM and gapps.
Droid 4 - Avatar
Click to expand...
Click to collapse
0.o wouldn't that be a LOT more destructive than just restoring the old backup?
pyro42 said:
0.o wouldn't that be a LOT more destructive than just restoring the old backup?
Click to expand...
Click to collapse
Nope. You are not wiping data so all your apps, setting, etc will still be there.
the data itself will remain if you just wipe the system, cache and dalvik cache but be sure to reinstall the latest stable build of CM and gapps for it
Sent from my XT894 using xda premium
kwyrt said:
Nope. You are not wiping data so all your apps, setting, etc will still be there.
Click to expand...
Click to collapse
ah gotcha gotcha...
unfortunately it didn't work.
for troubleshooting's sake, i went ahead and made a backup of the rom in it's non-working state.
i restored my old backup, it boots just fine.
restored borked backup (tested it, still won't boot), wiped cache/dcache, wiped system, installed cm-10.2-20130821-NIGHTLY-maserati.zip and gapps 20130812, wiped cache/dcache again for good measure, then reboot and waited 10 minutes, still won't pass boot logo.
so i figure someting's wrong with Data right? so i rebooted to safestrap and did a factory restore, then wiped cache/dcache, and still won't boot.
so now i'm going at it the opposite direction. restoring the working backup, restoring just the data from the nonworking backup, then upgrading CM/Gapps
rebooting.. and....
blank screen with full backlight. not so much as a CM logo.
i guess for now i am going to restore back to the old backup, update the rom, and go about reconfiguring, unless anyone has any more suggestions?
pyro42 said:
ah gotcha gotcha...
unfortunately it didn't work.
for troubleshooting's sake, i went ahead and made a backup of the rom in it's non-working state.
i restored my old backup, it boots just fine.
restored borked backup (tested it, still won't boot), wiped cache/dcache, wiped system, installed cm-10.2-20130821-NIGHTLY-maserati.zip and gapps 20130812, wiped cache/dcache again for good measure, then reboot and waited 10 minutes, still won't pass boot logo.
so i figure someting's wrong with Data right? so i rebooted to safestrap and did a factory restore, then wiped cache/dcache, and still won't boot.
so now i'm going at it the opposite direction. restoring the working backup, restoring just the data from the nonworking backup, then upgrading CM/Gapps
rebooting.. and....
blank screen with full backlight. not so much as a CM logo.
i guess for now i am going to restore back to the old backup, update the rom, and go about reconfiguring, unless anyone has any more suggestions?
Click to expand...
Click to collapse
Yeah, definitely sounds like something in /Data. Only other possible option I can think of would be to use Titanium Backup. It has an option to "Extract from Nandroid backup". It's under the "SPECIAL BACKUP/RESTORE" options. I've never used that option before so I have no idea how or if it would work but might be worth a shot.
kwyrt said:
Yeah, definitely sounds like something in /Data. Only other possible option I can think of would be to use Titanium Backup. It has an option to "Extract from Nandroid backup". It's under the "SPECIAL BACKUP/RESTORE" options. I've never used that option before so I have no idea how or if it would work but might be worth a shot.
Click to expand...
Click to collapse
wonderful idea, unfortunately TB crashes when i point it at either backup.
buuut i did find Nandroid Manager * ROOT which looks like it might be working.
if you really wanna see if it is the data or not have you tried to
flash 10.2 or whatever you started out with... then restore -just-
the data to the freshly flash system and then do a wipe of all
said caches... I do that sometimes to get a fresh start on my
os itself.. works pretty well. Just do not restore the cache just
the data part. Or restore with MD5 checking... if it doesn't check
out then you know for a fact that the data partition in that specific
nandroid isn't any good :/
Hi,
I've been using galaxy tab 8.9 with custom ROMs for more than a year and a half now, and sometimes it was acting strange, like flickering dialogs and crashes. Usually this meant an unstable ROM or just cache wasn't cleared when a new ROM was installed. And it was stable for some time, till I did a reset. Now no ROM is stable any more in addition to this, the battery sometimes says it is empty, but after restart it is back to normal status. I tried number of ROMs without luck, all are flickering lately which must mean it is not ROMs fault.
I am running out of ideas what to do with this tablet, so I'm asking if you guys have any suggestions, what else can I do to fix it.
NOTE: when installing a new ROM, I always did it with CWM recovery from internal storage with data, cache, dalvik wipe and factory reset.
regards, Daniel
danizmax said:
Hi,
I've been using galaxy tab 8.9 with custom ROMs for more than a year and a half now, and sometimes it was acting strange, like flickering dialogs and crashes. Usually this meant an unstable ROM or just cache wasn't cleared when a new ROM was installed. And it was stable for some time, till I did a reset. Now no ROM is stable any more in addition to this, the battery sometimes says it is empty, but after restart it is back to normal status. I tried number of ROMs without luck, all are flickering lately which must mean it is not ROMs fault.
I am running out of ideas what to do with this tablet, so I'm asking if you guys have any suggestions, what else can I do to fix it.
NOTE: when installing a new ROM, I always did it with CWM recovery from internal storage with data, cache, dalvik wipe and factory reset.
regards, Daniel
Click to expand...
Click to collapse
Do you ever wipe the system partition?
upconvert said:
Do you ever wipe the system partition?
Click to expand...
Click to collapse
Agree. In TWRP, a factory reset only wipe data, cache and dalvik cache. You have to manually format system. A clean install requires to wipe system, data, cache and dalvik-cache.
---------- Post added at 08:18 AM ---------- Previous post was at 08:17 AM ----------
danizmax said:
Hi,
I've been using galaxy tab 8.9 with custom ROMs for more than a year and a half now, and sometimes it was acting strange, like flickering dialogs and crashes. Usually this meant an unstable ROM or just cache wasn't cleared when a new ROM was installed. And it was stable for some time, till I did a reset. Now no ROM is stable any more in addition to this, the battery sometimes says it is empty, but after restart it is back to normal status. I tried number of ROMs without luck, all are flickering lately which must mean it is not ROMs fault.
I am running out of ideas what to do with this tablet, so I'm asking if you guys have any suggestions, what else can I do to fix it.
NOTE: when installing a new ROM, I always did it with CWM recovery from internal storage with data, cache, dalvik wipe and factory reset.
regards, Daniel
Click to expand...
Click to collapse
Try flashing the original firmware via odin.
iZLeeP said:
Try flashing the original firmware via odin.
Click to expand...
Click to collapse
Flashing original firmware would be my last resort. Is there any difference between odin and CWM flashing?
danizmax said:
Flashing original firmware would be my last resort. Is there any difference between odin and CWM flashing?
Click to expand...
Click to collapse
Of course. Flashing original firmware via odin brings back the original setup that came with the tab out of the box. I just don't remember if it will delete the contents of internal sd card. In any case, you can flash original firmware thru CWM as I always do, though I only flash boot and system images I modified in Kitchen. It will still be stock but only that it has been debloated, rooted, busybox installed, init.d enabled, and some system apps replaced.
Just remember that when flashing ROMs via CWM do a factory reset (wipe data, cache, dalvik-cache). In addition to the wipe, the rom.zip itself formats the system partition prior to flashing.
I have a HTC ONE m7, rooted, I have been running CM11, flashing the nightlies with great success. When CM12 came out, it 'soft bricked' my phone, continuous reboots, failing android functions. was able to reinstall Titanium backup, then restore the phone to a previous point. back running, but not without bugs. after trying this 3 times, I have given up. but I read where people say, "do a wipe" then flash the ROM....... What, specifically does this mean?
yes I have rooted my phone, but I am just knowledgable to be dangerous. if It means back to factory specs, then how do I flash the rom? I think that my phone should run CM12, and maybe I need to wipe? wipe what? dalvic cache? is that a wipe?
Anybody have some ideas or can point me to some postings that may help me. Many Thanks, very tired of operating on the last build of CM11
blairan
Do a wipe typically means wipe the data, system, cache, and dalvik cache partitions. If you are using TWRP as your recovery (I do for this phone), boot into it and then press Wipe, then Advanced Wipe. Select those four (not internal storage or USB OTG) and then Swipe to Wipe. Of course, your phone won't boot at this point, so you'll need a new ROM waiting on internal storage to be flashed.
thankyou Coal, I have been trying to install a CM12 and/or a CM12.1 ROM I can get them to boot up, but play store is not present. I can access play store via themes, and it comes up as a web page rather than an app. (is this norm for CM12?)
once I sign in to play store, I try to install titanium backup to restore all my apps. it says it is installed, I press it anyway, and it says it will be installed soon, which never happens. CM12 and CM12.1 seem to be running fine, but I can't restore any of my old phone. I can recover to a CM11, but it is a little unstable, so I would like to upgrade the system and be flashing nightlies again. what do you think?
and after watching a few videos on you tube, I figured out that I was missing the Gapps file, and the supers file. enjoying lollipop success.
thanks coal!
blairan said:
and after watching a few videos on you tube, I figured out that I was missing the Gapps file, and the supers file. enjoying lollipop success.
thanks coal!
Click to expand...
Click to collapse
I was going to suggest GAPPS, but I wasn't sure if you needed it for CM. Glad you figured it out!
I don't think I can edit the title so I'll write it here for anyone who wants to help: This problem is SOLVED. (Y)
So the matter is a bit complicated and I can't guarantee I even remeber everything I did but I'll try to include as much detail as I can:
I had the Stock Rom (OOS4.0.0) running, OEM unlocked & rooted when the OOS4.0.1 OTA notification kept nagging in the back of mind. I thought I should just leave it ago because I already had a feeling it would go wrong...
So I download the Full .zip and flashed it through TWRP 3.03-1 and after that it was stuck on the boot screen for more than 15 minutes or so. So I restarted it again and this time it booted butall my data was deleted and it gave me an error about the encryption having failed. But as you probably know, one can't flash anything on an encrypted phone so I checked back in TWRP and it was really encrypted. Checked back in the phone's settings: Also encrypted. I then used a tool to force decryption (it also wipes all the data) and I was back to square one.
From that moment on I tried: 1. restore nandroid (all partitions included [that includes EFS]). It got me to the booting screen, but when I unplugged it shut down and a reboot got me to the battery screen. I had 72% left so at this moment I thought it had nothing to do with it not booting at 72%. Then I wiped everything (checked every box in TWRP) and was left without any OS. Then I let my phone charge to 100% and re-restored the nandroid OOS4.00 and it worked but I had the Unlock-Bug, I was able to fix that. Then it booted but it wasn't able to recognize any SIM cards, so I fixed that by re-re-restoring with TWRP 3.03-0 (which automatically replaced 3.0.3-1 after the nandroid) and everything worked fine. until I went out today and realized I had no mobile data. I doubt it has something to do with EFS because everything else is working fine (calling, checking IMEI wih *#06#).
I then proceeded to check the APN and it looked ok, I then tried another SIM card (from the same provider) and it didn't change anything.
My provider is the german company 1&1 (1und1) but it uses vodafone APN.
I have no clue what to do right now so I am asking you guys for help.
Thanks in advance!
Well, first things first. On rooted devices with stock rom always flash a full/complete zipped image - never, never, never use an official partial image. And always wipe Dalvik/Art and common cache before reboot.
In your case now I would probably try to clean re-flash the current OOS image version (4.0.1). You'll find guides and downloads in the guides and rom section of this forum. Clean flashing your device requires you to completly wipe the data partition before flashing (the internal partition remains untouched). Don't forget to wipe Dalvik/Art and cache before rebooting. This will hopefully completly reset your device.
Inciter said:
Well, first things first. On rooted devices with stock rom always flash a full/complete zipped image - never, never, never use an official partial image. And always wipe Dalvik/Art and common cache before reboot.
In your case now I would probably try to clean re-flash the current OOS image version (4.0.1). You'll find guides and downloads in the guides and rom section of this forum. Clean flashing your device requires you to completly wipe the data partition before flashing (the internal partition remains untouched). Don't forget to wipe Dalvik/Art and cache before rebooting. This will hopefully completly reset your device.
Click to expand...
Click to collapse
First of all: Thanks for your reply.
I don't know if there was a misunderstanding but I only ever flashed the full 1,4gb .zips.
Also I am running 4.00, because I had to restore it as the 4.0.1 flash ruined my phone. Just now I flashed 3.03-1, wiped dalvik & cache and flashed the 4.02 .zip which I got from this [https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074] thread but it left me stuck on "patching image uncoditionally" or something and then I rebooted and now I am stuck on the +1 booting screen (not even the animation, just the +1 logo witht he "powered by android" signature in the bottom).
I have the feeling it's a software bug not related to what I did with my phone. it was just luck that I did not havfe that problem prior to my nandroid restore or something. I mean: Looking at it from a logical perspective: When you restore your phone with a full nandroid backup it should be exactly the same phone, shouldn't it?
Well, flashing the TugaPower rom might break the alert slider. To fix this you have to simply backup and recover the data partition. I don't know why this is happening but I believe that sometimes permissions to files and folders remain untouched in certain situations. Maybe someone else knows more details on this topic.
If you are absolutly sure that your nandroid contains all required partitions just try to wipe all cashes, data and system partition before recovery. But like I said before I would then clean re-flash your current OOS image version. In your case the error might possibly be some error resulting from faulty permission on configuration data. If it was a common bug more people would have reported it already.
If something broke and it can't be easily fixed... trying to return to point zero and resetting everything to defaults will possibly your best chance.
Inciter said:
Well, flashing the TugaPower rom might break the alert slider. To fix this you have to simply backup and recover the data partition. I don't know why this is happening but I believe that sometimes permissions to files and folders remain untouched in certain situations. Maybe someone else knows more details on this topic.
If you are absolutly sure that your nandroid contains all required partitions just try to wipe all cashes, data and system partition before recovery. But like I said before I would then clean re-flash your current OOS image version. In your case the error might possibly be some error resulting from faulty permission on configuration data. If it was a common bug more people would have reported it already.
If something broke and it can't be easily fixed... trying to return to point zero and resetting everything to defaults will possibly your best chance.
Click to expand...
Click to collapse
I have no problem with that, but my device does.
I can't flash anything because TWRP (bot 3.03-0 and 3.03-1) will be stuck at "patching system image unconditionally", ( I tried the full 4.02 .zip and the ful 3.54 .zip that I am 10000% sure used to work, because I used it before the Nougat release).
Wiping everything but Internal and USB OTG changes nothing.
If you have any idea how I can get to a fresh start, I would really appreciate it.
EDIT: I am sorry, I don't know what you mean by TugaPower Rom. I never installed anything like that - atleast not knowingly.
Due to encryption returning to OOS 3.X after having upgraded to Nougat is difficult. Just flashing wouldn't do. There's still an option to format data - not just to wipe it. Was boot, EFS and firmware partition included in your nandroid? Does the recovery still work now? Another Approach would be to use the Unbrick Tool.
Inciter said:
Due to encryption returning to OOS 3.X after having upgraded to Nougat is difficult. Just flashing wouldn't do. There's still an option to format data - not just to wipe it. Was boot, EFS and firmware partition included in your nandroid? Does the recovery still work now? Another Approach would be to use the Unbrick Tool.
Click to expand...
Click to collapse
So, I have the means to decrypt my device through a tool I found here on the forums last month. It does wipe all your data, though. Anyways: I was able to restore mobile data through an older nandroid backup (and yes: all my back ups include all partitions; glad I was smart enough to do that haha). That worked for me and made me come to the conclusion that the back up I used first was somehow corrupted. Then I restored the data partition using my most recent nandroid back up and now I am back in the game. Thanks for all your help so far!
The only thing that kind of makes me worry is that I only get ~60mbit/s through speedtest even though I should get 200. I know I was able to get 200Mbit/s at some point using that phone, but I don't remember if it was with OOS 3xx or the OOS 4.00 update. So I can't tell whether it has something to do with me restoring the phone, my WiFi connection (a speedtest with my lan-connected desktop gave me 200) or just an android bug.
I'll wait until weekend when I have the means to test it with another 200k connection - and imho 60k is enough for anything I do with my phone anyways and I don't plan on reselling the phone in the future, so it won't kill me even if it is nandroid-related.
Linux/Android backups aren't always that satisfying. I often experienced diffences between what was saved and what or how it was restored. Most problems resulted in faulty permissions or missing file execution attributes.
Nevertheless, I'm glad your devices is working again. Keep that backup save, you'll might need it again... or hopefully not.
Inciter said:
Linux/Android backups aren't always that satisfying. I often experienced diffences between what was saved and what or how it was restored. Most problems resulted in faulty permissions or missing file execution attributes.
Nevertheless, I'm glad your devices is working again. Keep that backup save, you'll might need it again... or hopefully not.
Click to expand...
Click to collapse
Thank you, I just checked the wifi-speed with an iPhone 6 and it even got lower results (>30k) so I assume it has something to do with the WiFi itself at the moment and not with the OP3t.
And even if the backups are not always satisfying: I want to quote someone I read on some forums doing my research to fix this phone: "The seasoned user knows: A backup makes the difference between an awesome phone and a beautiful brick." That is a most evident truth to me now haha.