I just unlocked my boootloader today after waiting the 14 days. First thing I did was install twrp recovery, had no problem there. Then I downloaded unofficial lineage os 14 rom, and the newest open gapps.
I was able to fastboot boot into twrp recovery, I then wiped dalvik, system, data, and cache. then proceeded to install lineage os rom, no problem, when I tried to install gapps, it just hung on detecting device and rom. which I had to reboot. then it came up to black screen with blue led. again I rebooted into twrp recovery, wiped again, and this time just installed lineage os rom, and reboot,same thing black screen with blue led. did I miss a step somewhere?
If you were on stock mm or below s244 stock then it's normal to see this..
Sent from my Lenovo P2 using Tapatalk
FireLord said:
If you were on stock mm or below s244 stock then it's normal to see this..
Click to expand...
Click to collapse
+1
Install s244 firmware and then install los.
In trying to fix my own problem I may have screwed it up more. I changed the file system of the Systema nd Data partitions. I changed it to EXT4, however that did not help. I would like to change them back to whatever they were before, but I dont know what they were before, can anyone help me?
actionxp said:
In trying to fix my own problem I may have screwed it up more. I changed the file system of the Systema nd Data partitions. I changed it to EXT4, however that did not help. I would like to change them back to whatever they were before, but I dont know what they were before, can anyone help me?
Click to expand...
Click to collapse
Stock is f2fs, if I'm not wrong
I have this same issue but it solved , i change my data partition to ext4 and also changed another partition to ext4 i didnot remember which partition is that, i think it is system partition (not sure)
actionxp said:
In trying to fix my own problem I may have screwed it up more. I changed the file system of the Systema nd Data partitions. I changed it to EXT4, however that did not help. I would like to change them back to whatever they were before, but I dont know what they were before, can anyone help me?
Click to expand...
Click to collapse
Don't messup with system partition plax..
I had the same issue. Try an other Gapps pack. I picked a smaler one and it worked.
Yes it was that easy
So i installed the S244 Firmware, installed twrp and even got stock rom+magisk root to work. I passed safetynet test. But i can't flash custom roms+gapps. It freezes in twrp.
I already tried alls opengapps versions, from pico until micro. None of them worked. My system partition is ext4, same as data.
My twrp version is 3.1.1-1
Related
Hello guys, I have a XT1033 converted to GPe in stock 5.1. What can I do to get CM12.1?
Flash stockrom 5.0.2 and after that twrp. Flash cm12.0 and dirty flash cm12.1 . hope this is correct.
klaymaniaf said:
Flash stockrom 5.0.2 and after that twrp. Flash cm12.0 and dirty flash cm12.1 . hope this is correct.
Click to expand...
Click to collapse
After I flash the stock rom, it wont go past the boot logo.
In twrp it will say the flash was successful, but if i reboot into stock it wont go past the boot logo which is still the google logo from the 5.1 GPe. If I go to flash CM over that, I get an error.
wipe dalvik cache/cache
Never mind, i got it to work. I had to flash the correct gpt.bin file, because the partitions are different on stock motorola than to the gpe. After that a full wipe and i could go back to stock and onto cm12.1.
http://forum.xda-developers.com/showpost.php?p=57444986&postcount=1
this is the file that worked for me You will have to do a full wipe and reboot to recovery to be able to mount any of the file systems again tho.
r97smith said:
Never mind, i got it to work. I had to flash the correct gpt.bin file, because the partitions are different on stock motorola than to the gpe. After that a full wipe and i could go back to stock and onto cm12.1.
http://forum.xda-developers.com/showpost.php?p=57444986&postcount=1
this is the file that worked for me You will have to do a full wipe and reboot to recovery to be able to mount any of the file systems again tho.
Click to expand...
Click to collapse
Mate can u step by step explain what you did and downloaded? I am on converted GPE and want to install cm12.1 - funny thing is I didnt get anything online for getting gpe to cm12.1 other than your post Your help is appreciated. Also does your sms work on cm12.1?
Vivek
vivekdeshmukh said:
Mate can u step by step explain what you did and downloaded? I am on converted GPE and want to install cm12.1 - funny thing is I didnt get anything online for getting gpe to cm12.1 other than your post Your help is appreciated. Also does your sms work on cm12.1?
Vivek
Click to expand...
Click to collapse
From GPE, I wiped everything in twrp recovery. Flashed the gpt.bin file I had linked to there, and then rebooted to recovery again.
Then I decided to go back to stock 5.0.2, flashed that, then cm12 and then cm12.1. But thats just how I did it anyway.
I had to flash the gpt.bin file to re-partition the system storage, because its different to the stock and cyanogenmod. I flashed stock 5.0.2 just to be sure there wasnt going to be anymore problems when flashing cyanogenmod. Then I flashed cm12 to see everything booted right, and cm12.1 with the 5.1 gapps.
Yes, everything works excellent on cm12.1
r97smith said:
From GPE, I wiped everything in twrp recovery. Flashed the gpt.bin file I had linked to there, and then rebooted to recovery again.
Then I decided to go back to stock 5.0.2, flashed that, then cm12 and then cm12.1. But thats just how I did it anyway.
I had to flash the gpt.bin file to re-partition the system storage, because its different to the stock and cyanogenmod. I flashed stock 5.0.2 just to be sure there wasnt going to be anymore problems when flashing cyanogenmod. Then I flashed cm12 to see everything booted right, and cm12.1 with the 5.1 gapps.
Yes, everything works excellent on cm12.1
Click to expand...
Click to collapse
Thanks mate, it sounds bit of a task for a noob like me, but hell i will give that a try
---------- Post added at 05:16 PM ---------- Previous post was at 05:09 PM ----------
r97smith said:
stock 5.0.2, flashed that, then cm12 and then cm12.1.
Click to expand...
Click to collapse
Our of curiosity, why do we have to go from 5.02 to cm12 to cm12.1? cant we go directly from 5.02 to cm12.1?
vivekdeshmukh said:
Thanks mate, it sounds bit of a task for a noob like me, but hell i will give that a try
---------- Post added at 05:16 PM ---------- Previous post was at 05:09 PM ----------
Our of curiosity, why do we have to go from 5.02 to cm12 to cm12.1? cant we go directly from 5.02 to cm12.1?
Click to expand...
Click to collapse
For flashing cm 12.1 if you are currently using gpe 5.1 converted, you dont need to do all that **** like flashing stock 5.0.2 then cm 12 and then cm12.1
You just need to do this
In twrp recovery go to wipe and change data partition file system to f2fs
Then wipe every thing in recovery and flash cm12.1
sjandroiddeveloper said:
You just need to do this
In twrp recovery go to wipe and change data partition file system to f2fs
Then wipe every thing in recovery and flash cm12.1
Click to expand...
Click to collapse
1st step - wipe and change Data partition to f2fs ONLY or should i change the partition to f2fs for all (data, cache, system, usb)?
2nd step - wipe everything meaning dalvik, data, cache, system BUT NOT internal storage and USB - correct?
vivekdeshmukh said:
1st step - wipe and change Data partition to f2fs ONLY or should i change the partition to f2fs for all (data, cache, system, usb)?
2nd step - wipe everything meaning dalvik, data, cache, system BUT NOT internal storage and USB - correct?
Click to expand...
Click to collapse
You have to change file system to f2fs of data partition only ,don't change other, if you do there is no doubt your device will not boot but it may cause several other problems
And after changing file system of data partition you need to wipe dalvik,cache,system and data
No need to wipe internal storage (data/media)
And where does USB come in this ???
Sent from falcon
PRESS THANKS IF HELPED
sjandroiddeveloper said:
And where does USB come in this ???
Click to expand...
Click to collapse
USB OTG is an option that comes under recovery in twrp - advanced wipe. Thanks trying it right now!
vivekdeshmukh said:
USB OTG is an option that comes under recovery in twrp - advanced wipe. Thanks trying it right now!
Click to expand...
Click to collapse
I know what is USB OTG and where it comes
What I meant was why did you even think of wiping USB
sjandroiddeveloper said:
You have to change file system to f2fs of data partition only ,don't change other, if you do there is no doubt your device will not boot but it may cause several other problems And after changing file system of data partition you need to wipe dalvik,cache,system and data No need to wipe internal storage (data/media)
And where does USB come in this ???
Sent from falcon
PRESS THANKS IF HELPED
Click to expand...
Click to collapse
Tried it yesterday night >> BOOM! OS gone! Dont know what happened, did the f2fs no problem but after dalvik, cache, system and data wipe the OS and all files just disappeared - dont know if it was corrupt data partition or me being too sleepy (5.00am) and could have deleted Internal storage. But the point is I ended up with no OS and then tried ADB pushing my cm files to phone, well only to realize that ADB was not recognizing the device inspite of uninstall/install drivers ... slept at 6.00 in morning. Today, finally, copied the cm files by mounting the phone and copying from PC, just to realize after flashing that the cm12.1 still has the same issues of not able to send sms.
But anyways thanks to you I did learn something new and the opportunity to be in a soft brick situation and come out of it
Btw do u hv a converted gpe and tried the cm12.1 simply by changing the partition? EVerything works very smooth for me but just that the SMS doesnt work - which i cant live without.
vivekdeshmukh said:
Tried it yesterday night >> BOOM! OS gone! Dont know what happened, did the f2fs no problem but after dalvik, cache, system and data wipe the OS and all files just disappeared - dont know if it was corrupt data partition or me being too sleepy (5.00am) and could have deleted Internal storage. But the point is I ended up with no OS and then tried ADB pushing my cm files to phone, well only to realize that ADB was not recognizing the device inspite of uninstall/install drivers ... slept at 6.00 in morning. Today, finally, copied the cm files by mounting the phone and copying from PC, just to realize after flashing that the cm12.1 still has the same issues of not able to send sms.
But anyways thanks to you I did learn something new and the opportunity to be in a soft brick situation and come out of it
Btw do u hv a converted gpe and tried the cm12.1 simply by changing the partition? EVerything works very smooth for me but just that the SMS doesnt work - which i cant live without.
Click to expand...
Click to collapse
No I never converted to gpe
But the method I told you was absolutely correct
And your OS was deletes because you wiped system partition which was necessary to install cm 12.1 so that was obvious and no need to worry.
And for your information you don't need adb if you are using twrp because it supports mtp
And the sms bug was there but it was solved long ago but I don't know why its not working for you
May be try different kernels
And bro PRESS THANKS instead of saying
can you plz help with the sms bug..
sjandroiddeveloper said:
No I never converted to gpe
But the method I told you was absolutely correct
And your OS was deletes because you wiped system partition which was necessary to install cm 12.1 so that was obvious and no need to worry.
And for your information you don't need adb if you are using twrp because it supports mtp
And the sms bug was there but it was solved long ago but I don't know why its not working for you
May be try different kernels
And bro PRESS THANKS instead of saying
Click to expand...
Click to collapse
can you plz help with the sms bug..
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
I_HAVE_NO_IDEA said:
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
Click to expand...
Click to collapse
Well if you can boot into the recovery and if its custom (TWRP) wipe all the data on your phone. Second I would try to flash a ROM onto your device such as Resurrection Remix and see if that works. Update on your progress.
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
I_HAVE_NO_IDEA said:
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
Click to expand...
Click to collapse
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
vtails said:
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
Click to expand...
Click to collapse
Thank you. But I can't flash a cm12.1 atm (see my post below). I can only flash through fastboot. I'm not sure I properly understood you, what do you call 4 22 ?
FYI I managed to boot again. Here's what I did:
Flash a 5.x ROM, try to boot to let the system make partitions and stuff (I think)
Boot in TWRP and saw that system and cache were not mountable, so I wiped them.
Flash a cm12.1 (+ Gapps) and here we go!
Thank you for your help!
Please Help
I was in miui ROM then I tried flashing Metallium ROM, after I flashed it, it booted up but, it wasn't restoring my previous apps, so I skip that part, but then when I got to the home screen I wasn't able to access my stuffs in my phone memory.
So I thought maybe I need to change the data to f2fs, so I went to the recovery and did and flashed the Metallic ROM again, but this time it didn't boot at all, there was a bootloop and I could get past the start up screen.
I tried my older ROMs the one that I had, but it's all giving me the same response now, I have switch before but I never have had this problem. Please help, how do I flash other lollipop ROM again.
Maybe changing to f2fs and doing a factory reset. If that doesn't help, flash stock ROM via fastboot.
kennylrmsailo said:
Please Help
I was in miui ROM then I tried flashing Metallium ROM, after I flashed it, it booted up but, it wasn't restoring my previous apps, so I skip that part, but then when I got to the home screen I wasn't able to access my stuffs in my phone memory.
So I thought maybe I need to change the data to f2fs, so I went to the recovery and did and flashed the Metallic ROM again, but this time it didn't boot at all, there was a bootloop and I could get past the start up screen.
I tried my older ROMs the one that I had, but it's all giving me the same response now, I have switch before but I never have had this problem. Please help, how do I flash other lollipop ROM again.
Click to expand...
Click to collapse
Anyone out there? Need help desperately.
Anyone?
samuelcr93 said:
Maybe changing to f2fs and doing a factory reset. If that doesn't help, flash stock ROM via fastboot.
Click to expand...
Click to collapse
Yeah that might work but I'm kinda looking for a solution where I don't have to flash the stock again because I lost all my moto g stuffs some months back.
And another thing is that when I flash MIUI its working fine again and I'm able to access all the file in my phone storage also. Any suggestions?
Mmmm if you are using TWRP you could connect the phone to the PC and make a backup while you are in recover mode. Then format again data partition to f2fs and make a factory reset including internal storage and finally flash your ROM and restore your files.
But if that is not working then the only option is flashing Stock ROM
If MIUI is still booting it means that your data partition is still ext4
SI have revert from the CM13 to Resurrection Remix (which is also a CM) however Im wanting to change to a predated ROM or even a different ROM and it isnt allowing me. In both CWM and TWRP it says the it installed just fine but when I boot up its still Resurrection and yes I have done all the wipes that should be done and still same thing happens.
How can I fix this?
OK
johneflik said:
Jut use advanced wipe in TWRP then wipe everything except the external SD. I guarantee no thing will boot again unless you flash it.
Click to expand...
Click to collapse
That did the trick, was able to flash again and put back on the ROM before it got stuck on RR. Idk what went wrong in that ROM change, had to edit Updater-Script and got CM13 going again
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