Database Info

[Q] Unfortunately, the setup wizard has stopped

I need help stuck in error message.
Phone: Verizon Galaxy S3 Sch-i535
Ok Heres what it did
(Phone already rooted)
I Downloaded and Flashed a Custom Rom from goo. manager (Samsung Galaxy S III (Verizon) CyanogenMod - d2vzw / cm-10.1.2-d2vzw.zip) and The gapps that came along with it.
Also downloaded Ez unlock to unlock my boot loader. (unlocked the boot loader)
Phone was successfully flashed with the new CyanogenMod, everything booted up fine. But when the phone starts to setup, i get an error message saying: Unfortunately, the process com.process.gapps has stopped.
i click ok and it keeps popping up.
Also between that error message I get another error message saying: Unfortunately, Setup Wizard has Stopped.
Can't access any part of the phone. Just stuck in the error message loop.
I do however have access to the recovery mode options that let you Install, wipe backup restore, mount, settings, advanced, reboot.
PLEASE HELP

You flashed the wrong gapps. Just boot into recovery, wipe, flash only the rom, then find the correct gapps, download them, boot back into recovery, flash new gapps, reboot system and you should be good to go.:good:

Don't flash roms in goo manager. Learn to do it the right way.

What is the correct gapps for rootbox 4.x and why is flashing gapps necessary? Should the wipes be done before the gapps or after?
I had the same problem as hesbordofallofus and managed to get back into TWRP and flash my old 4.1.1 rom. I'd like to check out a 4.2.2 or 4.3 vanilla rom. Clean rom 5.5.1 works well but uses battery up fast.

jd1639 said:
Don't flash roms in goo manager. Learn to do it the right way.
Click to expand...
Click to collapse
and what is "The right way" ? i only used goo manager because i have a mac and it's a little bit more difficult to flash a samsung Device with a macbook pro.

The problem with goo manager is that, obviously there's a chance you're going to flash the wrong gapps. I don't use clockwork mod recovery because when I rooted my phone with CASUAL it installed TWRP. But, I assume they both work the same way. When you flash files from recovery, you have to manually download the rom and gapps packages from their respective servers so as long as you've done the reading and the quadruple checking, you will flash the correct files for YOU'RE phone. Learning how to boot into recovery manually, using the three button combo is a very important part of flashing roms. And getting comfortable moving around in whatever recovery you're using makes it less likely that you will make a fatal mistake.
I probably spend an hour or two reading in my phones' forum everyday. I want to make sure I understand how to do what I'm doing properly and have a plan for when things go wrong. So read, read, read!!!!!

alt230 said:
What is the correct gapps for rootbox 4.x and why is flashing gapps necessary? Should the wipes be done before the gapps or after?
Click to expand...
Click to collapse
the gapps package is necessary because the package is a set of apps like the Play Store, Gmail, and other google apps. You can't sign into you're Google account without Gaaps. The process is always this:
1: wipe Data+ Cache
2. Install ROM (updater-script in ROM zip wipes system for u)
3. Flash PROPER GAAPS
4. Reboot
Remember "System" is essentially your Operating system. So don't wipe that manually unless you have a nandroid or a ROM zip as a backup. There is really no need to wipe system manually in Recovery because a the updater-script in a ROM zip always erases system for u. Just worry about formatting data manually before flashing ROM. Also remember when you flash a Gaaps package it gets installed to your system partition NOT Data. Just some info for you. Remember if you don't know how to do something ASK!! nobody is stupid here and no questions are dumb. If it keeps you from bricking your device then ask. Also READ READ READ! Always make sure you know what you r flashing and that it is meant for your device. The last thing you want to do is to flash a kernel or ROM made for a different version of ur device.
Sent from my SCH-I535 using Tapatalk 4

I'm not sure what you mean by manually formatting data. I'm also not really sure what you mean when you say don't manually wipe. My personal opinion is, when in doubt follow the dev's instructions. So for instance, when I decided on PACMAN, I went to the dev's page, scrolled down to the links to the downloads, grabbed that, then used link to the gapps, grabbed those, and usually right under the links, there's a brief set of directions for installing the rom/gapps. I always just do what they say. It's become a routine for me to research, pick a rom, grab the files, make as sure as humanly possible I've got them correct, make a fresh nandroid, then proceed.

When I say manually wipe I mean going into the wipe menu in recovery and choosing wipe data etc
Sent from my SCH-I535 using Tapatalk 4

Sandman-007 said:
the gapps package is necessary because the package is a set of apps like the Play Store, Gmail, and other google apps. You can't sign into you're Google account without Gaaps. The process is always this:
1: wipe Data+ Cache
2. Install ROM (updater-script in ROM zip wipes system for u)
3. Flash PROPER GAAPS
4. Reboot
Remember "System" is essentially your Operating system. So don't wipe that manually unless you have a nandroid or a ROM zip as a backup. There is really no need to wipe system manually in Recovery because a the updater-script in a ROM zip always erases system for u. Just worry about formatting data manually before flashing ROM. Also remember when you flash a Gaaps package it gets installed to your system partition NOT Data. Just some info for you. Remember if you don't know how to do something ASK!! nobody is stupid here and no questions are dumb. If it keeps you from bricking your device then ask. Also READ READ READ! Always make sure you know what you r flashing and that it is meant for your device. The last thing you want to do is to flash a kernel or ROM made for a different version of ur device.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
"The last thing you want to do is to flash a kernel or ROM made for a different version of ur device." Done that!
So the reason I couldn't get all my apps (I could see them) or get into playstore, log onto google find my contacts, etc. is that I didn't flash the gapps. BIG QUESTION: how do I know which gapps to flash? (BTW I dropped back to cleanrom 5.5.1 and it works fine but I can't send texts. I receive but can't send.) If I could I'd give it a rest and do my real work.

Usually the dev posts the Gaaps package you need in the OP if their thread or on their site.
Sent from my SCH-I535 using Tapatalk 4

Vanir/Commotio won't flash

So i downloaded a nightly off the [ROM] Vanir/Commotio TF700
and i was trying to flash it on twrp it failed i made sure to wipe and factory reset prior. I put cromni back on without any problems.
It says it can't find md5 file... during the flashing process

Paprika88 said:
So i downloaded a nightly off the [ROM] Vanir/Commotio TF700
and i was trying to flash it on twrp it failed i made sure to wipe and factory reset prior. I put cromni back on without any problems.
It says it can't find md5 file... during the flashing process
Click to expand...
Click to collapse
Snag the recovery.log after the flash and it will provide more info.

here's my log
its attached
I'm trying out all the roms i can until i land one that might fix my wifi reception.
Anyways i'm also trying crombi-kk.. and I'm having trouble with this step. its asking me to fix root and then won't boot when i flash it...
(this is coming from cromi x
I can't find the root sub section after i open developer options.
1. Enable developer options by clicking the build number 7 times in settings - about tablet
2. Go to developer settings
3. In the first section click Root access and change to Apps and ADB
I'm also asked to fix permissions after I flash Commotio

Paprika88 said:
here's my log
its attached
I'm trying out all the roms i can until i land one that might fix my wifi reception.
Anyways i'm also trying crombi-kk.. and I'm having trouble with this step. its asking me to fix root and then won't boot when i flash it...
(this is coming from cromi x
I can't find the root sub section after i open developer options.
1. Enable developer options by clicking the build number 7 times in settings - about tablet
2. Go to developer settings
3. In the first section click Root access and change to Apps and ADB
I'm also asked to fix permissions after I flash Commotio
Click to expand...
Click to collapse
You need to update your TWRP version - please move to TWRP 2.7.1.1
This is why the rom is failing to flash:
Code:
ApplyParsedPerms: removexattr of /system/addon.d/50-vanir.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
It's either a bug in the installer or related to the older TWRP - I suspect the latter.

Thanks!
I installed twrp 7.2.1.1 and it flashed successfully. however now i rebooted it and I see commotion with a picture of the ocean and sunset looping.
the booting screen i presume. I figured it was just loading everything up but it's been like this for 20 minutes now...
i'll try crombi kitkat
Edit: K nevermind I flashed the gapps and it worked
It loaded and I received a warning message:
UIDS on the system are inconsistent you need to wipe your data partition or your device will be unstable... with a i'm feeling lucky button.
I'll try factory wipe
it worked

Paprika88 said:
Thanks!
I installed twrp 7.2.1.1 and it flashed successfully. however now i rebooted it and I see commotion with a picture of the ocean and sunset looping.
the booting screen i presume. I figured it was just loading everything up but it's been like this for 20 minutes now...
i'll try crombi kitkat
Edit: K nevermind I flashed the gapps and it worked
It loaded and I received a warning message:
UIDS on the system are inconsistent you need to wipe your data partition or your device will be unstable... with a i'm feeling lucky button.
I'll try factory wipe
it worked
Click to expand...
Click to collapse
Glad you got it working.
For future reference: Whenever you move from one rom to another you have to perform a factory wipe in recovery. Preferably before you flash the rom. Saves you a lot of headache

[Q] After flashing no internet access

I had this problem, that I couldn't turn on WIFI. I didn't want to use the internet so flashed lollipop 5.0.1(from 4.4.4). When flashed to 5.0.1 it was rebooting every time the screen locked, so decided to go back to 4.4.4. At first everything was ok, but then the mobile network just stopped to work. I was ok to cope with the disabled wifi, but i really need the phone internet. What should I do? Already tried flashing stock and factory wiping a couple of times, didn't help
The 'tower' of signal strength looks orange, but there's an H on it

sebreens said:
I had this problem, that I couldn't turn on WIFI. I didn't want to use the internet so flashed lollipop 5.0.1(from 4.4.4). When flashed to 5.0.1 it was rebooting every time the screen locked, so decided to go back to 4.4.4. At first everything was ok, but then the mobile network just stopped to work. I was ok to cope with the disabled wifi, but i really need the phone internet. What should I do? Already tried flashing stock and factory wiping a couple of times, didn't help
The 'tower' of signal strength looks orange, but there's an H on it
Click to expand...
Click to collapse
Using the right gapps version?

beekay201 said:
Using the right gapps version?
Click to expand...
Click to collapse
I'm sorry, but where can i check that?
if i download the zip from teamandroid.com, how can i install them?

sebreens said:
I'm sorry, but where can i check that?
if i download the zip from teamandroid.com, how can i install them?
Click to expand...
Click to collapse
make sure you're getting the correct gapps version: L and KK need different gapps.
KK: http://forum.xda-developers.com/showthread.php?t=2397942
L: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900

beekay201 said:
make sure you're getting the correct gapps version: L and KK need different gapps.
KK: http://forum.xda-developers.com/showthread.php?t=2397942
L: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
Click to expand...
Click to collapse
When i first tried to install it showed
* Incompatible GApss Currently Installed *
PA GApps can ONLY be installed on top of an existing installation of PA GApps. You must wipe (format) your system partition BEFORE installing any PA GApps package.
**** GApps Installation failed ***********
when i look lower i see
E: Error in ... (the specified image address)
(status 1)
Installation aborted.
when i try to install gapps the second time it shows
E: Can't make /tmp/update_binary
Installation aborted
what should i do?
(I didn't have CWM Recovery before, now I have it installed and rooted the phone)

OFC, you already flashed gapps.
Wipe /system, reflash ROM, flash correct gapps.

beekay201 said:
OFC, you already flashed gapps.
Wipe /system, reflash ROM, flash correct gapps.
Click to expand...
Click to collapse
I don't get it. I've done it several times already, every time it showed that there is an incompatible version already. maybe the google stock image already contains some gapps?
the only time the install went through was when i just wiped /system and without reflashing rom tried to install the zip
maybe you can do a thorough step by step guide what i have to do? i thought that maybe i had to have root access, but after rooting nothing changed.
Oh, and i can't mount usb through CWM. if i proceed to startup, the device itself installs all the apps

sebreens said:
I don't get it. I've done it several times already, every time it showed that there is an incompatible version already. maybe the google stock image already contains some gapps?
the only time the install went through was when i just wiped /system and without reflashing rom tried to install the zip
maybe you can do a thorough step by step guide what i have to do? i thought that maybe i had to have root access, but after rooting nothing changed.
Oh, and i can't mount usb through CWM. if i proceed to startup, the device itself installs all the apps
Click to expand...
Click to collapse
Well first of all. Flash TWRP. Trust me. Then solving your problems will be much easier than in CWM

sebreens said:
I don't get it. I've done it several times already, every time it showed that there is an incompatible version already. maybe the google stock image already contains some gapps?
the only time the install went through was when i just wiped /system and without reflashing rom tried to install the zip
maybe you can do a thorough step by step guide what i have to do? i thought that maybe i had to have root access, but after rooting nothing changed.
Oh, and i can't mount usb through CWM. if i proceed to startup, the device itself installs all the apps
Click to expand...
Click to collapse
NOTE: Ofc, the factory image has gapps included. Google owns gapps, in case you don't know.
Due to lack of info, I was mislead to think that you was running custom roms, and not a factory image.
The orange colored network indicators simply mean that you're not connected to Google Play services. This would NOT prevent you from accessing the internet on a browser for example - doesn't matter if on wifi or on mobile data - visiting www.google.com.
If you want to get a clean/fresh start, flash a factory image. I assume you know how to, so if you don't go read the guides on General. It's very simple.
That said, after flashing a factory image, and booting it, EVERYTHING should just work: adding your google account, connection to google play services, everything.
If you want to run custom roms, then you'll need a custom recovery (as suggested, TWRP), a custom rom, and an appropriate gapps version. Simple.

beekay201 said:
NOTE: Ofc, the factory image has gapps included. Google owns gapps, in case you don't know.
Due to lack of info, I was mislead to think that you was running custom roms, and not a factory image.
The orange colored network indicators simply mean that you're not connected to Google Play services. This would NOT prevent you from accessing the internet on a browser for example - doesn't matter if on wifi or on mobile data - visiting www.google.com.
If you want to get a clean/fresh start, flash a factory image. I assume you know how to, so if you don't go read the guides on General. It's very simple.
That said, after flashing a factory image, and booting it, EVERYTHING should just work: adding your google account, connection to google play services, everything.
If you want to run custom roms, then you'll need a custom recovery (as suggested, TWRP), a custom rom, and an appropriate gapps version. Simple.
Click to expand...
Click to collapse
Ok, so I should just contact warranty if I got this after flashing stock? I cannot turn on wifi (the problem persisted before flashing) and now I have no internet connection. (I checked all the providers, and I have the right ones set there)
What should I do before I bring it to the warranty service?

[ROM][TWRP] Can't flash new ROM

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)

OnePlus One - Won't boot RR , boot loop happens

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