Related
I didn't know where to post this so i am posting it here.
I tried to flash the latest version of CrDroid some hours ago and although the installation began with no errors, the whole thing got stuck on an infinite installation of the ROM. The log displayed "Patching system image unconditionaly."
After about 30 minutes i just lost faith and held down power button to force a reboot. Then, TWRP got reset to the screen which you see when you first flash TWRP, the one ascing about wether to keep system read only or not.
I will post screenshots too as soon as i figure out how to do it
.
Set it back to RW mode from RO mode. If it constantly turns back to RO, try reflashing the recovery image.
If you are lucky enough to abruptly abort a ROM installation, you will be able to atleast use the device. I had aborted a nandroid restore and my entire data partition was corrupted.
In any case you should post it in the appropriate ROM thread.
Make sure system is mounted writable, wipe system, data, and caches, and flash... it's that simple. If it fails use another ROM.
BTW, it is usually useful to tell which device (specifically), what ROM/Gapps, what version of TWRP, etc... the devil is usually in the details, the more the better.
Yeah i forgot about that, im new here. So, its the latest version of TWRP and the ROM was the latest version of crDroid (April 17th). Anyways, me being extremely stubborn as usual, I tried flashing the ROM through FlashFire and the problem is still there. By the way I did mount everything and it doesnt get better. I dont care anyways i'll just return to some other Nougat ROM. Thanks for replying though!
mike.... said:
Yeah i forgot about that, im new here. So, its the latest version of TWRP and the ROM was the latest version of crDroid (April 17th). Anyways, me being extremely stubborn as usual, I tried flashing the ROM through FlashFire and the problem is still there. By the way I did mount everything and it doesnt get better. I dont care anyways i'll just return to some other Nougat ROM. Thanks for replying though!
Click to expand...
Click to collapse
Weird... We can pretty much guarantee nothing is working in TWRP though, or at least it's not processing even the boot image of your ROM or the device wouldn't boot.
What is bootloader status?
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
First I have an admission - I'm 82 so my memory is not as good as it was. I have been using smartphones for some years now including flashing recoveries and operating systems. This time, however, I have got myself into a real mess.
I have a OnePlus 6 and just recently there was an OxygenOS update from OnePlus which I installed in the normal OTA way. It was only a little later that I realised that I'd updated from Oreo (8.1) to Pie (9) and there was not a version of Xposed for Pie. I want Xposed so I decided that I wanted to downgrade to Oreo. It didn't occur to me that it would be any more difficult than re-flashing the previous version of OxygenOS. I now realise it isn't that easy or, at least, it doesn't appear to be.
Having flashed Oreo the phone wouldn't boot. It got as far as the boot animation and stayed there. I thought the best thing then would be to try and get back to Pie so I reflashed that. At least the phone now booted but I soon realised that some things weren't right. For example if I turn on wifi it turns off again after about two seconds so I can't use wifi at all.
I'm not sure what to do now. I do have a TWRP backup for both Pie and the previous Oreo. Would it be possible to restore one of those (preferable Oreo)? I'm a bit nervous about trying that as I'm not sure how much wiping/restore I'd need to do. There is the Vendor partition (I've not seen that before) and I would be very nervous about wiping and restoring the boot partition which now, I believe, contains the recovery.
I hoping that some kind person will offer some advice to put me on the road to recovery (No pun intended).
First of all, I'm impressed that you have done as much as you have (or even wanted to for that matter) at 82. Most older people I know (I'm 42 btw)barely know how to use there phones in the os, much less know what recovery is, lol.
Anyway, I'm pretty sure I've read that with you go backwards to Oreo from pie, you need to do a full wipe including storage. Did you do that?
BarrySamuels said:
First I have an admission - I'm 82 so my memory is not as good as it was. I have been using smartphones for some years now including flashing recoveries and operating systems. This time, however, I have got myself into a real mess.
I have a OnePlus 6 and just recently there was an OxygenOS update from OnePlus which I installed in the normal OTA way. It was only a little later that I realised that I'd updated from Oreo (8.1) to Pie (9) and there was not a version of Xposed for Pie. I want Xposed so I decided that I wanted to downgrade to Oreo. It didn't occur to me that it would be any more difficult than re-flashing the previous version of OxygenOS. I now realise it isn't that easy or, at least, it doesn't appear to be.
Having flashed Oreo the phone wouldn't boot. It got as far as the boot animation and stayed there. I thought the best thing then would be to try and get back to Pie so I reflashed that. At least the phone now booted but I soon realised that some things weren't right. For example if I turn on wifi it turns off again after about two seconds so I can't use wifi at all.
I'm not sure what to do now. I do have a TWRP backup for both Pie and the previous Oreo. Would it be possible to restore one of those (preferable Oreo)? I'm a bit nervous about trying that as I'm not sure how much wiping/restore I'd need to do. There is the Vendor partition (I've not seen that before) and I would be very nervous about wiping and restoring the boot partition which now, I believe, contains the recovery.
I hoping that some kind person will offer some advice to put me on the road to recovery (No pun intended).
Click to expand...
Click to collapse
grab this file. http://oxygenos.oneplus.net.s3.amazonaws.com/OnePlus6Oxygen_22_OTA_007_all_1805131952_O_MR1.zip flash that to be back on Oreo 5.1.5. this is the special roll back firmware.
also, this will wipe all data as well as internal storage. just putting that out there so you know before doing it.
b.huss2 said:
Anyway, I'm pretty sure I've read that with you go backwards to Oreo from pie, you need to do a full wipe including storage. Did you do that?
Click to expand...
Click to collapse
No, it was something I was trying to avoid. I was working on the assumption that as going from Oreo to Pie didn't involve any loss of data/internal storage then going from Pie to Oreo wouldn't either.
MrSteelX said:
grab this file. http://oxygenos.oneplus.net.s3.amazonaws.com/OnePlus6Oxygen_22_OTA_007_all_1805131952_O_MR1.zip flash that to be back on Oreo 5.1.5. this is the special roll back firmware.
also, this will wipe all data as well as internal storage. just putting that out there so you know before doing it.
Click to expand...
Click to collapse
As I said above I was trying to avoid wiping data/internal storage but if that is the only way then I'll have to do it. I do have a backup of my internal storage so I can replace that easily enough. Would my Oreo backup be of any use after the wipe to restore my original data setup? That version of OxygenOS was 5.1.11 so could I get back to that?
I thank you both for your very timely help.
P.S. Can you see anything wrong with this plan?
1. Flash the roll back firmware.
2. Install TWRP using Fastboot
3. Flash, using TWRP, OxygenOS v5.1.11 over the roll back firmware
4. Restore 'data' from my previous TWRP backup.
5. Restore internal storage from backup.
BarrySamuels said:
1. Flash the roll back firmware.
2. Install TWRP using Fastboot
3. Flash, using TWRP, OxygenOS v5.1.11 over the roll back firmware
4. Restore 'data' from my previous TWRP backup.
5. Restore internal storage from backup.
Click to expand...
Click to collapse
I would think that should get you back to where you were. I have not personally been through these specific steps, but seems logical. It's def worth a try.
b.huss2 said:
I would think that should get you back to where you were. I have not personally been through these specific steps, but seems logical. It's def worth a try.
Click to expand...
Click to collapse
going from oreo to pie, no data loss.
going from pie to oreo, data loss.
that is how it is done. after coming back to 5.1.5 then you can go to 5.1.11
MrSteelX said:
going from oreo to pie, no data loss.
going from pie to oreo, data loss.
that is how it is done. after coming back to 5.1.5 then you can go to 5.1.11
Click to expand...
Click to collapse
I think that's kind of understood at this point. However, I see no problem with restoring a Oreo backup once he's back on Oreo.
BarrySamuels said:
No, it was something I was trying to avoid. I was working on the assumption that as going from Oreo to Pie didn't involve any loss of data/internal storage then going from Pie to Oreo wouldn't either.
As I said above I was trying to avoid wiping data/internal storage but if that is the only way then I'll have to do it. I do have a backup of my internal storage so I can replace that easily enough. Would my Oreo backup be of any use after the wipe to restore my original data setup? That version of OxygenOS was 5.1.11 so could I get back to that?
I thank you both for your very timely help.
P.S. Can you see anything wrong with this plan?
1. Flash the roll back firmware.
2. Install TWRP using Fastboot
3. Flash, using TWRP, OxygenOS v5.1.11 over the roll back firmware
4. Restore 'data' from my previous TWRP backup.
5. Restore internal storage from backup.
Click to expand...
Click to collapse
Almost. You are missing one thing.
1. Flash the roll back firmware
2. Install TWRP using fastboot
3. Flash, using TWRP, OxygenOS 5.1.11
4. Before rebooting, FLASH TWRP IN TWRP (This is important, as flashing 5.1.11 will overwrite recovery)
5. Use your TWRP backup
6. Do what you need for files you want on internal storage.
Don't forget to flash TWRP after you update to 5.1.11.
Not having much luck. I flashed the roll back firmware, and twrp, then rebooted but I got the boot animation again and it wouldn't go any further. I re-downloaded the firmware again, in case there was any corruption, and re-flashed it without flashing twrp but got as far as the boot animation again but no further.
Whilst in TWRP I used the file manager to look at internal storage and nothing had been wiped from that.
I'm not sure what to do now so any suggestions would be very welcome.
BarrySamuels said:
Not having much luck. I flashed the roll back firmware, and twrp, then rebooted but I got the boot animation again and it wouldn't go any further. I re-downloaded the firmware again, in case there was any corruption, and re-flashed it without flashing twrp but got as far as the boot animation again but no further.
Whilst in TWRP I used the file manager to look at internal storage and nothing had been wiped from that.
I'm not sure what to do now so any suggestions would be very welcome.
Click to expand...
Click to collapse
Fastboot working correctly - try flashing the fastboot Rom. Hopefully that will put you back to square one where you start over. Complete wipe though!
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Use the fastboot ROM recovery. It works (I've used it twice) no data wipe.
chazey2 said:
Fastboot working correctly - try flashing the fastboot Rom. Hopefully that will put you back to square one where you start over. Complete wipe though!
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
That does sound rather hairy especially as I don't know which one I'd need to use. It does mention that it should not be used to upgrade or downgrade and I'm not sure that I, or my phone, knows which version is currently installed.
ADDENDUM:
I decided to try one more thing of my own. I wiped data and re-flashed the Pie version of OxygenOS then rebooted.
:laugh: It booted and seemed to be working properly i.e. I could use wifi and the time doesn't keep being lost.
I have now installed Blu Spark TWRP and restored my 'data' backup and I am now back to where I was before all this started. It isn't really where I want to be because I have no Xposed but it is significantly better than a non-booting phone. I'll just have to wait for a new version of Xposed (if such ever appears).
I really don't know why those other suggestions didn't work.
Very many thanks to all those who offered support; it certainly does give a morale boost.
BarrySamuels said:
That does sound rather hairy especially as I don't know which one I'd need to use. It does mention that it should not be used to upgrade or downgrade and I'm not sure that I, or my phone, knows which version is currently installed.
ADDENDUM:
I decided to try one more thing of my own. I wiped data and re-flashed the Pie version of OxygenOS then rebooted.
:laugh: It booted and seemed to be working properly i.e. I could use wifi and the time doesn't keep being lost.
I have now installed Blu Spark TWRP and restored my 'data' backup and I am now back to where I was before all this started. It isn't really where I want to be because I have no Xposed but it is significantly better than a non-booting phone. I'll just have to wait for a new version of Xposed (if such ever appears).
I really don't know why those other suggestions didn't work.
Very many thanks to all those who offered support; it certainly does give a morale boost.
Click to expand...
Click to collapse
Your welcome good luck
Hi there, hoping someone can help.
Had my BLL-L22 working perfect and had carbon rom working, till one day it just decided to ask for factory reset. From there something crazy happened and my recovery partition aswell as system partitions were completely dead, fastboot didnt work either.
I used the NDIT tool to recover using the jumper method and i got my 6x booting once again, except on the NDR90 rom, anyhow everything picks up now and works, but now my model is stuck on generic_a15 instead of bll-l22, whenever i flash oeminfo it says device not verified and cant boot,
Anyhow - gone ahead and installed carbon ROM again, tried AOSPE too, same thing, both sims wont pick up, and wifi won't turn on, when i restore stock - everything boots fine.
It worked prior to the recovery, now no aosp rom will pick up my imei's or wifi, but stock does. any one got any ideas i could try to get wifi and sims working?
Thanks!
Try flashing full stock BLL-L22 firmware with HuRUpdater and then flash custom ROM again. Vendor partition must be okay in way to use some function in other ROMs than stock one. Plus, flashing full firmware through HuRUpdater should fix the "generic_a15" model name mismatch.
sooooo, potentially this is my fault, but, I forgot to uninstall magisk before updating to 10.3.3.0 and now the device won't boot, just bootloops. I have since uninstalled magisk in twrp, and re-flashed the rom, but am still getting a bootloop.
I feel like a complete wipe and re-flash of everything, including the kernel might fix this, or is it a potential problem with miui 10.3.3.0?
I can connect to the phone via ADB while its booting and /data is mounted, so it seems like the system is trying to boot correctly, but something is failing.
going to try flashing 10.3.2.0 to see if it works then, otherwise, not sure what t try.
ok, well that didn't work, 10.3.3.0 has downgrade protection, so now im just booting into recovery every time
guess i'll try a full flash
I don't have a ton of experience with this but what did you use to flash the update? Did you use the OTA zip from Xiaomi or a version found online? I just updated mine from 10.2.2.0 global to 10.3.2.0 global (which I got from GetDroidTips) without removing Magisk first with no issues. I read in this post that the Vendor image can get corrupted, maybe that's what happened not sure if that helps at all. You might have the right idea with just doing a complete reinstall of stock though, I know it sucks to lose data.
As mentioned above, my guess would be something got corrupted. I would use Mi Flash and reflash the fastboot image for 10.3.3.0.
Couldn't find a fastboot ROM for 10.3.3.0, but luckily had a copy of 10.2.1.0 which I flashed via miflash, had to wipe data to get it to boot though, which irritated me. Something must have got corrupted at some point, oh well, all sorted now (sort of), just need to re-flash twrp
Fastboot ROM for 10.3.30
http://bigota.d.miui.com/V10.3.3.0....XM_20190817.0000.00_9.0_global_0b55a6dd91.tgz