Related
This is quite unusual. Let me first say the device has been running completely stock (latest COS, cyanogen recovery, non-rooted) for the past year or so.
This is how it happened, I set up my alarms at night and went to bed, but then I remembered the device was running for 8 days straight and becoming somewhat sluggish so I decided to reboot it.
I pressed the power button, selected reboot, and pressed ok. As it was restarting, I went to sleep and never looked at the device.
The next day: launcher has been reset to trebuchet (from gplay launcher). ALL my apps were gone. All google apps and services were gone.
Only a handful of system apps remain. As if I've installed a cyanogenmod based rom without flashing gapps.
Dialer and SMS apps are there, but contacts are gone. My SMS messages show but the app force closes if I try to open any message.
Gallery app does show all my pictures so not everything seems to have gone.
Using the cyanogen file manager app, I can see that all my files are still there.
Any idea what's going on?
The only thing I can think of doing right now is factory reset using fastboot.
darkchazz said:
This is quite unusual. Let me first say the device has been running completely stock (latest COS, cyanogen recovery, non-rooted) for the past year or so.
This is how it happened, I set up my alarms at night and went to bed, but then I remembered the device was running for 8 days straight and becoming somewhat sluggish so I decided to reboot it.
I pressed the power button, selected reboot, and pressed ok. As it was restarting, I went to sleep and never looked at the device.
The next day: launcher has been reset to trebuchet (from gplay launcher). ALL my apps were gone. All google apps and services were gone.
Only a handful of system apps remain. As if I've installed a cyanogenmod based rom without flashing gapps.
Dialer and SMS apps are there, but contacts are gone. My SMS messages show but the app force closes if I try to open any message.
Gallery app does show all my pictures so not everything seems to have gone.
Using the cyanogen file manager app, I can see that all my files are still there.
Any idea what's going on?
The only thing I can think of doing right now is factory reset using fastboot.
Click to expand...
Click to collapse
Is your bootloader unlocked?
Renosh said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes. It was the first thing I did when I got the device back in 2014.
darkchazz said:
Yes. It was the first thing I did when I got the device back in 2014.
Click to expand...
Click to collapse
Fastboot method is a bit tricky if you don't flash userdata image (wipes internal storage). You'd have to turn off phone after fastboot flashing everything except userdata and then do a factory reset in recovery.
If you decide to flash TWRP it will just require flashing latest TWRP 3.0.2-0, download the version of CM you were on and wiping (system, data, dalkvik & cache) and then flashing the signed flashable zip.
You can find fastboot and flashable zips in this thread
http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Renosh said:
Fastboot method is a bit tricky if you don't flash userdata image (wipes internal storage). You'd have to turn off phone after fastboot flashing everything except userdata and then do a factory reset in recovery.
If you decide to flash TWRP it will just require flashing latest TWRP 3.0.2-0, download the version of CM you were on and wiping (system, data, dalkvik & cache) and then flashing the signed flashable zip.
You can find fastboot and flashable zips in this thread
http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Click to expand...
Click to collapse
I just fastboot flashed everything including the userdata image. It was the only way that fixed the issue.
Guess I have to install all those apps again..
I think u accidentally went in to geust mode( it a possibility) . Check it!
Return to owner mode again.
Settings >users> owner mode
Hello guys,
first off: i had something to do in the past with all this stuff but my memory isnt that great anymore so please correct me if im wrong
so here's the thing: my OPO decided to not detect my SIM anymore, so i did a factory reset thru recovery. I also rooted the phone before with a video tutorial from youtube (don't know if i can link it here this is my first post^^). What it does is install SuperSU over TWRP. You then have root without erasing your data! I was kinda surprised because i read in other threads that it actually will.
But anyways back to topic. I am now on these settings:
Cyanogen OS 12.1.1-Y0G7DAS2K1
Stock Recovery
Rooted
Bootloader unlocked (not sure, but i guess otherwise it wouldnt work)
I received a message for the OTA Update to Cyanogen OS 13. Downloaded & installed it, phone reboots into recovery. Already surprised here because its not TWRP anymore but i guess it was just temporary for the root installing. Or maybe it was because i didn't unchecked the "update recovery" checkbox in developer options, i think its active on default.
But anyways, the recovery tries to install it and suddenly the menu shows up again with an android in the background (in his chest is a red warning sign). No error, just the graphical android in the background. After a restart, nothing changed still on the same version. I did a factory reset once more and also "deleted media" and wiped cache.
As i mentioned, im not up-to-date with the differences on CyanogenMod and Cyanogen OS.
What i want to do now:
Step 1: Format my OPO as clean as possible.
Is Factory Reset and wipe media etc. enough for this? Or do i have to hard reset it?
Step 2: Root Access and TWRP.
I lost both of these after an OTA update to my OPO. I guess it was when i received the Cyanogen OS update. I would like to know when exactly these two will be erased and what to do to not lose them anymore. I heard it differs between CM and Cyanogen OS.
Step 3: Decision what OS to use: CyanogenMod or Cyanogen OS?
Im willing to wait for updates as long as they're stable. And i would also prefer to just install them over OTA (when it works^^). I don't want to flash like crazy, i only want a steady, rooted, customizable OS. I searched on this forum but im not sure which are the latest versions of both and what the differences are. What would you suggest me on these preferences?
Step 4: Restoring my Data
I backed up my Apps with Titanium Backup and transfered the folder to my PC. Never used it before, so i would like to know if it can cause any problems if i restore it on a newer version of Cyangogen OS or even Cyanogenmod?
Hope i don't forget anything. Sorry for the long post & noob questions you probably read everyday
EagleJR said:
Hello guys,
first off: i had something to do in the past with all this stuff but my memory isnt that great anymore so please correct me if im wrong
so here's the thing: my OPO decided to not detect my SIM anymore, so i did a factory reset thru recovery. I also rooted the phone before with a video tutorial from youtube (don't know if i can link it here this is my first post^^). What it does is install SuperSU over TWRP. You then have root without erasing your data! I was kinda surprised because i read in other threads that it actually will.
But anyways back to topic. I am now on these settings:
Cyanogen OS 12.1.1-Y0G7DAS2K1
Stock Recovery
Rooted
Bootloader unlocked (not sure, but i guess otherwise it wouldnt work)
I received a message for the OTA Update to Cyanogen OS 13. Downloaded & installed it, phone reboots into recovery. Already surprised here because its not TWRP anymore but i guess it was just temporary for the root installing. Or maybe it was because i didn't unchecked the "update recovery" checkbox in developer options, i think its active on default.
But anyways, the recovery tries to install it and suddenly the menu shows up again with an android in the background (in his chest is a red warning sign). No error, just the graphical android in the background. After a restart, nothing changed still on the same version. I did a factory reset once more and also "deleted media" and wiped cache.
As i mentioned, im not up-to-date with the differences on CyanogenMod and Cyanogen OS.
What i want to do now:
Step 1: Format my OPO as clean as possible.
Is Factory Reset and wipe media etc. enough for this? Or do i have to hard reset it?
Step 2: Root Access and TWRP.
I lost both of these after an OTA update to my OPO. I guess it was when i received the Cyanogen OS update. I would like to know when exactly these two will be erased and what to do to not lose them anymore. I heard it differs between CM and Cyanogen OS.
Step 3: Decision what OS to use: CyanogenMod or Cyanogen OS?
Im willing to wait for updates as long as they're stable. And i would also prefer to just install them over OTA (when it works^^). I don't want to flash like crazy, i only want a steady, rooted, customizable OS. I searched on this forum but im not sure which are the latest versions of both and what the differences are. What would you suggest me on these preferences?
Step 4: Restoring my Data
I backed up my Apps with Titanium Backup and transfered the folder to my PC. Never used it before, so i would like to know if it can cause any problems if i restore it on a newer version of Cyangogen OS or even Cyanogenmod?
Hope i don't forget anything. Sorry for the long post & noob questions you probably read everyday
Click to expand...
Click to collapse
Ok so first you can not perform OTA updates with a custom recovery like TWRP. So if you want OTA updates don't install a custom recovery. You lost TWRP before even performing the OTA update don't know how but you did. So I am going to instruct you how to start fresh.
1. You need ADB and fastboot installed you can get the minimal version here http://forum.xda-developers.com/showthread.php?t=2317790 or you can get the full SDK manager which has fastboot and adb https://developer.android.com/studio/index.html but if your not planning development just go with minimal.
2. Follow this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 You don't need to do step 4 since you want to install a custom recovery. So just reboot after you flash all the stock files.
(Also make sure you download the right stock rom he has a 16gb and a 64gb listed. Or you can download the stock rom straight from cynogen os here https://cyngn.com/support
3. Next you will need the TWRP file you can get it here https://dl.twrp.me/bacon/ if you don't have ADB/Fastboot in your path just place the file in the same folder as your fastboot. Also rename the file to recovery.img make sure you don't name it recovery.img.img
4. Download SUPERSU for root get it here https://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
5. With your phone on plug it in to your computer and transfer the SuperSU zip to the download folder on your phone.
6. Unplug your phone and reboot to fastboot then plug your phone back in
7. Open command prompt in the fastboot folder by holding shift and right click and select open command window here.
8. Type fastboot devices (This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.)
9. Type Fastboot Flash recovery recovery.img
10. Once the flash is done don't let the phone fully boot to system or it will rewrite to the stock recovery so hold the power button and volume down and it will boot into TWRP recovery. IF you let it boot into the system and it does reinstall the stock recovery you will need to re-install twrp
11. Once in twrp perform a backup of your stock rom
12. After the backup is done go back to the main menu of TWRP go to install navigate to the download file and then install SuperSU
13. Now reboot and you now have the stock rom with root and a custom recovery.
14. Difference between cynogen os and cynogenmod http://www.androidcentral.com/difference-between-cyanogen-os-and-cyanogenmod
Hope this helps and
Durso81 said:
Ok so first you can not perform OTA updates with a custom recovery like TWRP. So if you want OTA updates don't install a custom recovery. You lost TWRP before even performing the OTA update don't know how but you did. So I am going to instruct you how to start fresh.
1. You need ADB and fastboot installed you can get the minimal version here http://forum.xda-developers.com/showthread.php?t=2317790 or you can get the full SDK manager which has fastboot and adb https://developer.android.com/studio/index.html but if your not planning development just go with minimal.
2. Follow this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 You don't need to do step 4 since you want to install a custom recovery. So just reboot after you flash all the stock files.
(Also make sure you download the right stock rom he has a 16gb and a 64gb listed. Or you can download the stock rom straight from cynogen os here https://cyngn.com/support
3. Next you will need the TWRP file you can get it here https://dl.twrp.me/bacon/ if you don't have ADB/Fastboot in your path just place the file in the same folder as your fastboot. Also rename the file to recovery.img make sure you don't name it recovery.img.img
4. Download SUPERSU for root get it here https://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
5. With your phone on plug it in to your computer and transfer the SuperSU zip to the download folder on your phone.
6. Unplug your phone and reboot to fastboot then plug your phone back in
7. Open command prompt in the fastboot folder by holding shift and right click and select open command window here.
8. Type fastboot devices (This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.)
9. Type Fastboot Flash recovery recovery.img
10. Once the flash is done don't let the phone fully boot to system or it will rewrite to the stock recovery so hold the power button and volume down and it will boot into TWRP recovery. IF you let it boot into the system and it does reinstall the stock recovery you will need to re-install twrp
11. Once in twrp perform a backup of your stock rom
12. After the backup is done go back to the main menu of TWRP go to install navigate to the download file and then install SuperSU
13. Now reboot and you now have the stock rom with root and a custom recovery.
14. Difference between cynogen os and cynogenmod http://www.androidcentral.com/difference-between-cyanogen-os-and-cyanogenmod
Hope this helps and
Click to expand...
Click to collapse
Thank you very much! I did all of your Instructions step-by-step and it worked flawless. Im now on the latest CM13 Release. I hope it was the right decision and it runs smooth and stable. And if not i got the backup I do have 2 more questions:
-TWRP asked me if i want to let them "modify my partition". It helps when you are getting official updates. Is that important for me? I guess i will just flash future updates over recovery and not over OTA anyways, so i can left this "modify" option unchecked, right?
-While i did the factory reset, it said that most of the time i will not have to delete internal storage. Does that mean it also excludes private stuff like photos, videos & also backups from titanium & TWRP (if it's the same stored location)? Thank you again for anything
EagleJR said:
Thank you very much! I did all of your Instructions step-by-step and it worked flawless. Im now on the latest CM13 Release. I hope it was the right decision and it runs smooth and stable. And if not i got the backup I do have 2 more questions:
-TWRP asked me if i want to let them "modify my partition". It helps when you are getting official updates. Is that important for me? I guess i will just flash future updates over recovery and not over OTA anyways, so i can left this "modify" option unchecked, right?
-While i did the factory reset, it said that most of the time i will not have to delete internal storage. Does that mean it also excludes private stuff like photos, videos & also backups from titanium & TWRP (if it's the same stored location)? Thank you again for anything
Click to expand...
Click to collapse
The only way you can do official updates is to follow all the steps above and flashing the newest stock ROM via fastboot and reinstalling twrp. Now if you want to flash a custom ROM like cynogenmod then you can just download the latest ROM from cynogemod and install it via twrp. As far as your pics go I would either upload them to a cloud service or your PC before switching ROMs. For your apps yes just backup with titanium backup and then just restore them when you change ROMs.
Ok so never mind i got into teamwin TWRP phew. But Alpha2 but isn't it suggested that you don't recover using twrp? I don't know what to DO.
silvernirvash said:
Ok so never mind i got into teamwin TWRP phew. But Alpha2 but isn't it suggested that you don't recover using twrp? I don't know what to DO.
Click to expand...
Click to collapse
Download TWRP RC1 and flash it with TWRP alpha. Then download PN and follow the flashing instructions OR use your PC to flash back to stock and start over.
Edit: if you've made a backup using TWRP alpha, you can try to restore it using TWRP alpha.
k.s.deviate said:
Download TWRP RC2 and flash it with TWRP alpha. Then download PN and follow the flashing instructions OR use your PC to flash back to stock and start over.
Edit: if you've made a backup using TWRP alpha, you can try to restore it using TWRP alpha.
Click to expand...
Click to collapse
I don't have ADB or USB debugging enabled on my device. I can't DO anything. And i go and mount my storage onto my PC it just shows a **** ton of folders with random letters and numbers. i can't copy any files onto the device nor will minimal ADB and fastboot work when i type adb devices to detect the device. i don't know what to do!
silvernirvash said:
I don't have ADB or USB debugging enabled on my device. I can't DO anything. And i go and mount my storage onto my PC it just shows a **** ton of folders with random letters and numbers. i can't copy any files onto the device nor will minimal ADB and fastboot work when i type adb devices to detect the device. i don't know what to do!
Click to expand...
Click to collapse
ADB debugging does not need to be enabled on the device. All fastboot commands will work when you're in bootloader.
The files/folders with random names are showing up because TWRP didn't decrypt properly, reboot TWRP until the files/folders show up properly on the device then the files will show up properly on your PC and enable you to transfer files.
What's the background here, were you running stock rooted or a custom ROM?
k.s.deviate said:
ADB debugging does not need to be enabled on the device. All fastboot commands will work when you're in bootloader.
The files/folders with random names are showing up because TWRP didn't decrypt properly, reboot TWRP until the files/folders show up properly on the device then the files will show up properly on your PC and enable you to transfer files.
What's the background here, were you running stock rooted or a custom ROM?
Click to expand...
Click to collapse
stock rooted with substratum installed. i had a substratum theme that worked for the most part perfectly fine but then i found orange kittens and the colored kittens addon to change the color to something i wanted people told me it would work just fine on the pixel 7.1 and when it rebooted BAM bootloop. i didn't have adb or usb debugging enabled when i did it and i wasn't thinking because i've done this kinda stuff in the past so i thought i'd be fine. but i guess i wans't.
k.s.deviate said:
ADB debugging does not need to be enabled on the device. All fastboot commands will work when you're in bootloader.
The files/folders with random names are showing up because TWRP didn't decrypt properly, reboot TWRP until the files/folders show up properly on the device then the files will show up properly on your PC and enable you to transfer files.
What's the background here, were you running stock rooted or a custom ROM?
Click to expand...
Click to collapse
I GOT ACCESS TO MY FILES AGAIN! I THINK I CAN MOVE STUFF OVER TO IT PERFECTLY NOW! Oh so could i just copy over the stock 7.1 zip flash it with twrp and i'll be set? or should i just flash the latest OTA update image? and whichever i have to do do i do it using the install option or do i do it using the advanced ADB sideload?
also what is PN? i'm confused by that one.
silvernirvash said:
stock rooted with substratum installed. i had a substratum theme that worked for the most part perfectly fine but then i found orange kittens and the colored kittens addon to change the color to something i wanted people told me it would work just fine on the pixel 7.1 and when it rebooted BAM bootloop. i didn't have adb or usb debugging enabled when i did it and i wasn't thinking because i've done this kinda stuff in the past so i thought i'd be fine. but i guess i wans't.
Click to expand...
Click to collapse
ok, bootloop form theme. After TWRP has successfully decrypted, this might take a few reboots.. Go to sd card, you will see a folder named Substratum, in there are two zip files, flash the SubstratumRescue_Legacy.zip then reboot.
IF that does not work, go back into TWRP and go to mount - system. back out and go to advanced - file manager navigate to /system/vendor/overlay and delete the entire folder. Ive done that only once on the Pixel, you might have to go to /system/system/vendor/overlay and delete the folder then reboot.
silvernirvash said:
I GOT ACCESS TO MY FILES AGAIN! I THINK I CAN MOVE STUFF OVER TO IT PERFECTLY NOW! Oh so could i just copy over the stock 7.1 zip flash it with twrp and i'll be set? or should i just flash the latest OTA update image? and whichever i have to do do i do it using the install option or do i do it using the advanced ADB sideload?
Click to expand...
Click to collapse
That is interesting, my first experience with the Pixel I had bought it close to when Best Buy was closing (they were offering the $10.00/month promotion) and the device had not finished updating. However, the person checking me out let me go before it had completely finished and said it "will finish the updates shortly and be usable". Well, i guess in his haste to get blackout drunk and attempt lame pick up lines, he did something wrong. After the update finished, The phone was stuck in a constant boot loop. My first experience with my beloved Pixel was a nightmare. Of course, I had it replaced with a new one in the store the next day, but it was very strange. I had not even got into the OS at all and it was stuck in this strange bootloop.
Glad your situation worked out, when I saw the title to this post my heart sunk a little bit because I certainly know the look.
silvernirvash said:
I GOT ACCESS TO MY FILES AGAIN! I THINK I CAN MOVE STUFF OVER TO IT PERFECTLY NOW! Oh so could i just copy over the stock 7.1 zip flash it with twrp and i'll be set? or should i just flash the latest OTA update image? and whichever i have to do do i do it using the install option or do i do it using the advanced ADB sideload?
Click to expand...
Click to collapse
No, just read my post and see if that works.
k.s.deviate said:
ok, bootloop form theme. After TWRP has successfully decrypted, this might take a few reboots.. Go to sd card, you will see a folder named Substratum, in there are two zip files, flash the SubstratumRescue_Legacy.zip then reboot.
IF that does not work, go back into TWRP and go to mount - system. back out and go to advanced - file manager navigate to /system/vendor/overlay and delete the entire folder. Ive done that only once on the Pixel, you might have to go to /system/system/vendor/overlay and delete the folder then reboot.
Click to expand...
Click to collapse
ZOMG it rebooted! i already did a restore so i have to set up my phone again in terms of apps and stuff but that's fine. but now it keeps saying android.process.acore keeps stopping. i'm assuming it has to do with the substratum theme and i guess that means i should just delete that folder huh?
silvernirvash said:
ZOMG it rebooted! i already did a restore so i have to set up my phone again in terms of apps and stuff but that's fine. but now it keeps saying android.process.acore keeps stopping. i'm assuming it has to do with the substratum theme and i guess that means i should just delete that folder huh?
Click to expand...
Click to collapse
How did you restore? I've never seen that process stop before.
It might be best to (since you have to set up your apps again) flash a factory image and start over.
---------- Post added at 05:02 AM ---------- Previous post was at 04:56 AM ----------
And if your going to be playing with themes.. PN is the way to go. PN is Pure Nexus rom. Follow the instructions word for word and you won't have any troubles. It is as stable as stock with some extra goodness baked in.
k.s.deviate said:
How did you restore? I've never seen that process stop before.
It might be best to (since you have to set up your apps again) flash a factory image and start over.
Click to expand...
Click to collapse
oh i did a quick cache and data wipe. it's what you're supposed to do when flashing new or updated roms in the first place. at the top right of TWRP it says wipe. i thought that would restore it back to default settings including substratum theme application but it seems all it did was set me back to stock settings with apps uninstalled lol. gotta set up my device again sadly. but now like i said now i keep getting this stupid android.process..acore keeps crashing error.
and i restored using the legacy zip you told me to use in the substratum folder using the install option at the top left.
Just hit the thanks button. ?
and by recovering i lost root....great....now i need to reroot.....damn it all =w=;;
k.s.deviate said:
Just hit the thanks button.
Click to expand...
Click to collapse
oh hey can i download and flash the latest version of android 7.1.1 manually using TWRP with out losing TWPR or my locked bootloader? just curious. i'm about to go back and reroot but i know updating to 7.1.1 = losing root and requiring me to root again after the fact which is why i'm holding off for NOW until i get an answer.
silvernirvash said:
oh hey can i download and flash the latest version of android 7.1.1 manually using TWRP with out losing TWPR or my locked bootloader? just curious. i'm about to go back and reroot but i know updating to 7.1.1 = losing root and requiring me to root again after the fact which is why i'm holding off for NOW until i get an answer.
Click to expand...
Click to collapse
No you can't flash factory images using TWRP, I would however highly suggest flashing the factory image to stop that crashing process.
k.s.deviate said:
No you can't flash factory images using TWRP, I would however highly suggest flashing the factory image to stop that crashing process.
Click to expand...
Click to collapse
so i gotta flash using minimal adb and fastboot huh? :/ damn lol. wouldn't that in turn remove TWRP tho? or am i mistaken on that one?
silvernirvash said:
so i gotta flash using minimal adb and fastboot huh? :/ damn lol. wouldn't that in turn remove TWRP tho? or am i mistaken on that one?
Click to expand...
Click to collapse
It would remove TWRP, but after the flash-all.bat is done.. set up your phone. Reboot to bootloader, fastboot boot TWRP install TWRP via zip and flash super su.
Then going forward to update every month, download the newest factory image, right click on the flash-all.bat click edit, scroll over and remove the -w. Then boot into bootloader and run the flash-all.bat, when it's done your still in bootloader, fastboot boot TWRP, flash TWRP zip and flash super su. Reboot.
k.s.deviate said:
It would remove TWRP, but after the flash-all.bat is done.. set up your phone. Reboot to bootloader, fastboot boot TWRP install TWRP via zip and flash super su.
Then going forward to update every month, download the newest factory image, right click on the flash-all.bat click edit, scroll over and remove the -w. Then boot into bootloader and run the flash-all.bat, when it's done your still in bootloader, fastboot boot TWRP, flash TWRP zip and flash super su. Reboot.
Click to expand...
Click to collapse
this would in fact wipe my phone every time i do it tho right? like EVERYTHING including music and photos and stuff right?
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery
3. Latest adb & fastboot files
4. Stock ROM ZIP files
5. Stock Recovery [OPTIONAL]
Custom Recovery Method:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_*.zip /sdcard or MTP
3. Wipe data, cache & dalvik (format data if stuck at boot animation)
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip. Your device will have Stock Recovery with Stock ROM. Finally Reboot.
Fastboot Method:
Note: Following process formats internal storage, so backup the internal storage files. If your device is in Stock ROM & somehow system partition is messed up just flash only system.
1. Download required Fastboot files
2. If downloaded 7z files, extract system.img file.
3. Enter
Code:
fastboot -w && fastboot erase system && fastboot flash recovery recovery.img && fastboot flash boot boot.img && fastboot flash vbmeta vbmeta.img && fastboot flash dtbo dtbo.img && fastboot flash system system.img && fastboot reboot
4. It takes a while to flash System partition, have patience.
5. Device reboots to system if everything is flashed successfully.
Stock Recovery Method:
1. Download Stock ROM OZIP Files & Stock Recovery
2. Copy *.ozip to sdcard or internal storage.
2. Goto fastboot & enter fastboot flash recovery recovery.img
3. Reboot to recovery, wipe (1st option). Then go back to main menu Install from storage locate the *.ozip file & install.
I'm sorry, but this doesn't work for me..stuck with the rooted but uninstalled magisk OS.. :'(
ceesiama said:
I'm sorry, but this doesn't work for me..stuck with the rooted but uninstalled magisk OS.. :'(
Click to expand...
Click to collapse
zip isn't installed successfully? can you also send screenshot, so I can help you.
4j17h said:
zip isn't installed successfully? can you also send screenshot, so I can help you.
Click to expand...
Click to collapse
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
ceesiama said:
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
Click to expand...
Click to collapse
ok no problem, so what do you want to know about? Clear data, cache, dalvik after or before flashing stock zip it won't bootloop. Yes, since device is decrypted lock screen doesn't work. Coming to Magisk, yes that method is not reliable. I have figured out 100% working way which works for everyone & doesn't fail anytime. Maybe I will make a new guide soon or ...Mod edit: Link to Telegram removed
4j17h said:
ok no problem, so what do you want to know about? Clear data, cache, dalvik after or before flashing stock zip it won't bootloop. Coming to Magisk, yes that method is not reliable. I have figured out 100% working way which works for everyone & doesn't fail anytime. Maybe I will make a new guide soon or ...Mod edit: Link to Telegram removed
Click to expand...
Click to collapse
I'm sorry I mistyped in the above comment, when i followed your method, zip installed successfully but it bootlooped into stock recovery everytime. I hope that clarifies a bit. I''ll be very grateful if you can help me..
ceesiama said:
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
Click to expand...
Click to collapse
Try install magisk manager, maybe ur device still rooted
haditriw said:
Try install magisk manager, maybe ur device still rooted
Click to expand...
Click to collapse
no that's not how magisk works in Realme 3 Pro, if device is restarted there will be no magisk. You need to goto fastboot then goto recovery, it boots to system. We have magisk. Yes this method tricky. I am going to publish new guide, it will be simple & straight forward.
Bricked/ Bootlooping
4j17h said:
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery or Pitch Black Recovery
3. Latest adb & fastboot files
4. Stock ROM zip files: RMX1851_A15
5. Stock Recovery [OPTIONAL]
Follow the below steps:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_A15.zip /sdcard or MTP
3. Wipe data, cache & dalvik
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip, Reboot to System. You get the stock Recovery & stock ROM.
Previous Firmware: RMX1851_A14 Google Drive || AndroidFileHost || Mega Cloud storage
Note: This guide will be updated in coming days with fastboot flash files & custom recovery flashable files with latest versions.
Click to expand...
Click to collapse
pls help me, im stuck on bootlooop :'(
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
4j17h said:
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery or Pitch Black Recovery
3. Latest adb & fastboot files
4. Stock ROM zip files: RMX1851_A15
5. Stock Recovery [OPTIONAL]
Follow the below steps:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_A15.zip /sdcard or MTP
3. Wipe data, cache & dalvik
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip, Reboot to System. You get the stock Recovery & stock ROM.
Previous Firmware: RMX1851_A14 Google Drive || AndroidFileHost || Mega Cloud storage
Note: This guide will be updated in coming days with fastboot flash files & custom recovery flashable files with latest versions.
Click to expand...
Click to collapse
pls help me, im stuck on bootloop :'(
malakaz27 said:
pls help me, im stuck on bootlooop :'(
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
pls help me, im stuck on bootloop :'(
Click to expand...
Click to collapse
I have seen you have started a new thread of bootloop. Is this because you flashed one of these stock zip? you were going back to stock from los?
this method worked perfectly fine for me. i tried both lineage os roms available and both of them caused bootloop or end up destroying boot. so thanks to developer for making this zip file.
4j17h said:
I have seen you have started a new thread of bootloop. Is this because you flashed one of these stock zip? you were going back to stock from los?
Click to expand...
Click to collapse
hi i am stuck in bootloop after flashing all stuff in fastboot guide
leo77g said:
hi i am stuck in bootloop after flashing all stuff in fastboot guide
Click to expand...
Click to collapse
bootloop to recovery? have you tried fastboot -w usually this should boot to system or else flash stock recovery, wipe full. This should definitely get back the device to system.
4j17h said:
bootloop to recovery? have you tried fastboot -w usually this should boot to system or else flash stock recovery, wipe full. This should definitely get back the device to system.
Click to expand...
Click to collapse
formatting worked and thanx for help )
Moderators' Announcement: I've removed the links to Telegram and references to it. This is not a development thread, and support is to be provided through XDA. Many posts proved this has not been the case!
You may be asking, "Why was my Telegram or Whatsapp thread closed?"
Well, it's just becoming too much.
Going forward, we will only allow one Telegram chat link on a development thread by the ROM's developer and only if thorough support is still provided in the ROM thread on XDA.
All discussion channels, photography channels, whatnot channels will be strongly discouraged and removed with immediate effect. Please reference the forum rules:
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
Also, we now have an official XDA Discord Server. We would encourage you to try it out.
Announcing the Official XDA-Developers Discord Server
FYI
Thanks,
The Moderation Team
Click to expand...
Click to collapse
Need Help
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
ResSetOk said:
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
Click to expand...
Click to collapse
since your bootloader is locked, all you can do is wipe full data or flash back P2Q then format & then flash Q2P.
4j17h said:
since your bootloader is locked, all you can do is wipe full data or flash back P2Q then format & then flash Q2P.
Click to expand...
Click to collapse
I did Wipe before and after firmware, on P2Q is stitched without problems, but under firmware in Q2P in recovery writes, that not managed wipe userdata. The data was not encrypted, the password is not asked.
do you have video for Fastboot Method ?
[No message]
My dad got the OTA update to 10.3.0 on xmas day and installed it. However the phone is now stuck on boot logo. He has a locked phone just as it came out of the box (ie no TWRP, no OEM unlock, no root).
I am quite experienced with installing custom ROMs but with locked phones I am lost. Is there anyway to recover the device without deleting data / factory reset? This is because my dad has quite a lot of pics on the device that are not backed up (yeah I know...).
Things I've tried so far:
- reboot holding power button + volume up
- boot flash twrp from fastboot - no permission due to phone being locked
- in stock recovery I do not get access to device via cable
- installed Tool all in One - it sees phone via fastboot
I always use the Stock Fastboot ROMs for OnePlus 6 myself to recover from soft bricks but this wipes data so no option here. Unless there is a way to install parts of ROM? Any other tips or ideas from the awesome XDA community? :good:
Btw this is the update he installed:
Screenshot of update that was installed
If you boot on twrp, it does not ask for the pin code to access the data?
Maybe try the last twrp for OOS 10.3.0 : ( https://androidfilehost.com/?fid=4349826312261678088 )
Use command : fastboot flash boot twrp-3.3.1-16-enchilada-Q-mauronofrio.img
Try flash a new boot img :
Stock boot 10.3 img
https://drive.google.com/open?id=1w44cUg815g-H1h_6gObUVPLDTc_dtiMX
The phone is not unlocked and therefore has no TWRP recovery. This is my problem, if it was unlocked I would have figured out a way to fix it.
PS it does ask for pincode when accessing stock recovery
I'm not sure if this works on locked bootloaders but try switching boot slots using fastboot.
Couple of weird things:
-you don't need an unlocked bootloader for fastboot to boot back into the system
-the dual partition was designed precisely to prevent things like this from happening. When an update fails, you are supposed to roll back to the old slot you were on previously.
Anyway, since you are able to boot to fastboot, can you try to get to stock recovery again from fastboot and see if you can boot up to system from there?
Hey
You can try to change the boot slot using fastboot mode
It can help uh maybe
Its worth to try
awaiz said:
Hey
You can try to change the boot slot using fastboot mode
It can help uh maybe
Its worth to try
Click to expand...
Click to collapse
When I try to set it to slot A (it's B now) it says device does not support slots which is weird as 'fastboot getvar current-slot' does show it using slot B right now.
When I try to set it to B (ie current slot) it says: FAILED (remote: 'Slot Change is not allowed in Lock State').
awaiz said:
Anyway, since you are able to boot to fastboot, can you try to get to stock recovery again from fastboot and see if you can boot up to system from there?
Click to expand...
Click to collapse
When I reboot to stock recovery it gives two options:
- Wipe Data and Cache
- Advanced
There are two reboot options under Advanced:
1. Reboot to fastboot
2. Reboot to recovery
2nd option just boots it back to this same recovery. Boot to fastboot works as well. So there is no option to reboot the device.
Perhaps I can try to flash the stock ROM (kinda of dirty flash) but again not sure if that works on locked phone.
https://www.androidexplained.com/change-active-partition-slot/
JagDave said:
https://www.androidexplained.com/change-active-partition-slot/
Click to expand...
Click to collapse
This doesn't work unfortunately on a locked device.
I found the fix and it was very simple: in Recovery under Wipe Data and Cache it has the option to delete 1. System Settings 2. Cache 3. Wipe all (incl Data).
I choose option 1 (System Settings) and after that it booted and I had to set up phone again as with a new install but all data on sd card had remained. I did lose all apps but that is a very minor thing.
Thanks for everyone who thought along with me. We got there in the end
help me.. my op6 stuck in bootlogo.. how can i run my phone back. it is still locked never rooted..
Alamin4736 said:
help me.. my op6 stuck in bootlogo.. how can i run my phone back. it is still locked never rooted..
Click to expand...
Click to collapse
Bro..Use the Msm tool to get recover coz you have the locked bootloader
roel1976 said:
I found the fix and it was very simple: in Recovery under Wipe Data and Cache it has the option to delete 1. System Settings 2. Cache 3. Wipe all (incl Data).
I choose option 1 (System Settings) and after that it booted and I had to set up phone again as with a new install but all data on sd card had remained. I did lose all apps but that is a very minor thing.
Thanks for everyone who thought along with me. We got there in the end
Click to expand...
Click to collapse
I am facing similar problem with my OP5. When I boot in recovery, it asks for pattern to unlock. But does not accept any pattern. In the absence of pin, it gives option to Wipe Data. Will I get similar options like you did ? I am hoping to save my data.