Newbie here.
Background: I have my Samsung Note 10.1 GT-N8000 since 2012, but I haven't touched it for 2+ years because it was still on Android 4.1. (Last week Netflix announced that we could watch it offline with Android 4.4 up, so I eventually had the courage to do sth about my 10.1)
My problems:
I was using TWRP 2.4, flashed CM13 ROM and Gapps pico. It went well except all Google apps weren't installed properly:
- If I just flashed the CM13 ROM without Gapps, upon reboot it kept popping "Unfortunately Google Play etc stopped"
- If I flashed both, it was the same, plus all Google apps were labelled "com.Android" instead.
I searched for and tried all possible solutions, and in one old threat someone suggested TWRP version matters too. So I updated it to TWRP 2.8 (also tried 3.0). Now, I have a different set of problems. I can't flash in TWRP 2.8 the same ROM that I could flash with TWRP 2.4, and it keeps giving the "error executing updater binary in zip" I've tried it million times (literally fighting it for the past 18 hours...)
I've tried the followings: wiping system/ cache before flashing new ROM, starting the entire process, rooting it again etc.
Could anyone kindly chip in? Any suggestions are appreciated!!!
Try Philz Recovery .
Nonono...don't try Philz recovery. Use the recovery explicitly stated in the CM13 instructions (TWRP 2.8.7.0) or newer (I'm using 3.0.2.0). Do not use any recovery that the instructions say is not supported, which is everything else.
rudycreat said:
My problems:
I was using TWRP 2.4, flashed CM13 ROM and Gapps pico. It went well except all Google apps weren't installed properly:
...
I've tried the followings: wiping system/ cache before flashing new ROM, starting the entire process, rooting it again etc.
Click to expand...
Click to collapse
Given this and the apparent lack of following CM13 installation instructions (you didn't wipe everything), I'd suggest starting over with downloading/flashing the TWRP version on the CM13 downloads page and re-downloading CM13 and and Open GApps check MD5s. Maybe a standard Open GApps install would be a good idea; you can always uninstall what you don't want.
Not meaning to sound harsh but preferable to spending another 18 hours in Einstellung. (pun not intended)
AOSP 7.1.2 - "Setup wizard keeps crashing" error when ROM is clean-installed
Every AOSP 7.1.2 rom iv'e tried to clean-install (after full wipe) so far seems to crash in setup wizard.
My guess the issue is that the setup wizard's app lacks permissions, but I couldn't even open the notification drawer in order to open the settings through the setup wizard...
Iv'e solved this issue by installing older 7.1.1 of the same ROM, and "dirty flash" the newer 7.1.2 on it.
Anyone else got the above issue?
It's known issue, available GAPPs are for 7.1.1 and not been updated as yet, easier workaround is to flash ROM then boot into it, reboot to recovery once again and flash GAPPs.
thank's a lot (Y) a can try
mnsiw said:
It's known issue, available GAPPs are for 7.1.1 and not been updated as yet, easier workaround is to flash ROM then boot into it, reboot to recovery once again and flash GAPPs.
Click to expand...
Click to collapse
Not working. Signing up still causing error.
mochi579 said:
Not working. Signing up still causing error.
Click to expand...
Click to collapse
It requires a patched ROMs to work properly. AOSP is bare minimum.
i'm using AospExtended ROM V4.0 , cleaned the phone ( fastboot erase userdata, format, extendend wipe ) .. clean rom install,
boot into the rom, wait 5 min. reboot to recovery and then install gapps .. worked for me without any problems.
Note that: The wifi service has changed in 7.1.2.
The current available Gapps' setupwizard still use the API 22 method. And it's probably the only apk call the interface directly. Thus it would crash when starting wifi.
The workaround is:
1. Flash ROM (and SuperSU).
2. Reboot and setup your Wifi.
3. Flash Gapps
4. Setup your account in settings after reboot.
This can bypass the crash.
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
wahlmat said:
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
Click to expand...
Click to collapse
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(https://dl.twrp.me/bacon/).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware: https://drive.google.com/file/d/0BxysuRdzsJeWeW9JbTNwaUJKb1E/view?usp=drivesdk
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(opengapps.org)(optional).
Reboot.It should boot fine now.
Good luck!
Mr.Ak said:
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(Can't post links withing 10 posts apparently...).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware:
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(Can't post links withing 10 posts apparently...)(optional).
Reboot.It should boot fine now.
Good luck!
Click to expand...
Click to collapse
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
wahlmat said:
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
Click to expand...
Click to collapse
I'm glad you got it up and running.
Here are some FAQs:
What is a Firmware? What is Modem?
- Firmware is the whole package of proprietary partitions of your device, modem itself is a NON-HLOS file responsible for your device's communications over Wi-Fi, Mobile Networks and other such stuff.
So what is the difference between firmware and ROM then?
- Firmware is the responsible partition for IMEIs, the modemst partitions hold your IMEI, persist holds your Mac addresses etc.
ROM is only a combination of system.img and boot.img (kernel)
What to restore if I loose my IMEI?
- Both the modemst partitions (IMP: considering you took a backup of them before)
What is the default firmware? (default= firmware which comes with the latest CM/ LineageOS 14.1 weeklies)
- c6-00241
Thanks a lot, once again
Help!
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
HisMuse said:
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
Click to expand...
Click to collapse
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
wahlmat said:
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
Click to expand...
Click to collapse
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
HisMuse said:
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
Click to expand...
Click to collapse
Yes you do. You need that + some software. Check out some "install custom recovery oneplus one" guides, you should be able to find something. Are you on Mac or Windows?
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
HisMuse said:
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
Click to expand...
Click to collapse
Download the Samsung ADB driver or whatever it was called, then flash a new recovery for it. There are multiple guides for doing that. After that you should be able to transfer your files to your pc while being in recovery mode
Hi people,
I've been struggling with this for the past 2 days and I'm trying really hard not to give up
I downloaded the stable rom from the MIUI website (for Mi Note 3 aka jason), installed it successfully via MiFlash, and tried flashing Lineage after I did a factory + data + system + cache wipe. It ended with me getting the dreaded error 7.
A bit later, I realized I had to get the dev build from the MIUI website and flash it before flashing Lineage OS. So I did - I updated to MIUI 10 using the dev build, made sure it was working and tried flashing Lineage OS on top of it (after wiping the partitions I mentioned earlier, following the Lineage OS instructions).
So eventually I got it to work - sort of.
Lineage OS is booting properly, but the device freezes before it can find any wifi networks to connect to (and then reboots), and that's why I think the culprit is the modem.
So, a few questions -
1. did it happen to anyone else? I searched endlessly but came up with nothing
2. If it is a modem issue - where can I find a working one? I looked it up and found nothing
3. If it isn't a modem issue - what should I do?
If I'm doing anything wrong - please tell me. I'm flashing custom roms since 2011 and this is the first time something like this has happened to me.
Thanks for all your help!
Hi, first of all you need an unencrypted phone - Format data in TWRP (3.2.3.1), then wipe system, data, cache, dalvik. Flash the Miui 10 china stable firmware 10.0.2 or 10.0.4, then rom, gapps and reboot.
Good luck, zaqm
zaqm said:
Hi, first of all you need an unencrypted phone - Format data in TWRP (3.2.3.1), then wipe system, data, cache, dalvik. Flash the Miui 10 china stable firmware 10.0.2 or 10.0.4, then rom, gapps and reboot.
Good luck, zaqm
Click to expand...
Click to collapse
You're a true lifesaver. Worked on the first try.
Thank you!
No problems ?
Hi guys,
long time ago i've already been a Member to XDA Community. HTC Wildfire was a brand new phone at that time. In the mean time i've switched to a Oneplus 2 running Lineage OS 17.1 and two years ago i got a Oneplus 6 running stock ROM till yesterday.
Yesterday i got Lineage OS with Wifi up and running fine with the official guide and official lineage recovery but forgot to flash OpenGapps in the first try. Tried flashing it again but got a Qualcomm Crashdump Mode Error after that.
So i went on to reflash the whole phone with clearing storage, system and so on. Flashed again now with OpenGapps and Magisk with reboot to recovery method described in official installation guide, Lineage was booting fine and tried to search for Wifi-Connection but i wasn't able to see any Wifi at all. I finished the setup and tried again in settings but System UI crashes if i try that. Rebooted, cleared Cache and tried again but nothing.
So i went back to full stock 10.3.0 with MSMDownloadTool but it only flashes partition a? Is that correct?
After a lot of trying different things got back to 10.3.5 on a and b partition with mauronofrios stock fastboot roms from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 (Thank you very much for that! :good: ). I can boot both slots if i switch them in booted twrp without any problem.
On stock everything works fine my wifi detects all available networks and i can connect to them without problems.
What did i do wrong?
Any help would be appreciated.
Thank you!
Schwaus
EDIT:
So i did a little bit more testing:
Installed lineage-17.1-20200804-nightly-enchilada-signed.zip with corresponding recovery without anything like Gapps or Magisk both like described in official instruction and with TWRP from mauronofrio. I also tried to flash latest official OTA from Oneplus via TWRP before flashing Lineageos. In neither of the tested ways Wifi is working and i cant see any Wifi-MAC-adress under settings. Also tried to switch back to stock before flashing with flash-all-partitions.bat from mauronofrios stock to get the persist partitions replaced too.
Every version of Stock like the MSMDownloadtool 10.3.0 or Stock 10.3.5 from mauronofrio Wifi works perfectly without problems. I also can update via OTA without issues. I just dont know what is happening with my Wifi firmware when flashing LineageOS.
EDIT 2:
Got the problem fixed:
Don't know if i done it right but maybe it helps someone.
In my case it was a combination of problems:
- First the latest Oneplus 6 Lineage releases (20200804 and the withdrawn 20200811) seem to have a bug when installed fresh on a device to cause a bootloop so i used the one from 30/06/2020 and updated with the app afterwards.
- Secondly the copy-partitions.zip script hasn't copied all of the partitions necessary. In mauronofrio's fastboot image there is a image named fw_4u1ea.img. This one got not copied by the script, so i booted twrp-3.4.0-1-enchilada-Q-mauronofrio.img and flashed all of the images (fastboot, persist and critical) to slot b again manually like described in his thread. The flash-all-partitions.bat has not worked either.
Now LineageOS works like a charm and i can see and connect to every wifi.
Hey mate. I had the same issue and I gave up at this point. Tomorrow I'll try your "EDIT 2:" and gonna leave a feedback
Hey Schwaus, thanks for this post. *EDIT 2* worked for me