Related
Couple of new tabs were recently released into the wild with some "revisions". Those who went thru Groupon, Frys, and Best Buy received tabs with 5.0.1 pre installed out of box.. Because of this you couldn't go back to any 4.x.x builds as the bootloader wouldn't allow it. After posting this and finding out about this issue some XDA members were able to find a fix and confirmed that this solution is a working solution.
TL;DR
Any Custom Recovery had problems mounting SD/Partitions making flashing roms, zips, ect a problem.
**WARNING**
I AM NOT RESPONSIBLE FOR ANY MISFORTUNE YOU RECEIVE BY APPLYING ANY INFO PAST THIS POINT. YOU TAKE SOLE RESPONSIBILITY FOR YOUR ACTION AND NO ONE HERE BUT YOURSELF IS ACCOUNTABLE.
I have included both LTE (DEB) and WIFI(FLO) setups that are currently working and are confirmed working by XDA members here. Apply based on your device. This works for both 5.0.1 and 5.0.2. ADB or Wugs program is sufficient enough to complete this task.
WIFI (FLO) https://drive.google.com/file/d/0B3fHxCdm5V_Mc2szNnFzT1I0eVk/view?usp=sharing
LTE (DEB) https://drive.google.com/file/d/0B3fHxCdm5V_MU1hfXzV6dFlEZ2c/view?usp=sharing
**NOTE**
The only way so far to root tab is to use cf-auto root. Google it and follow directions.
ADB setup:
Download recovery img and place into location where you ADB resides (or leave in download folder and open CMD in downloads for global ADB users)
make sure ADB is working and confirm that you Nexus is recognized
Code:
Code: adb devices
After confirmation get tab into bootloader mode
Code:
adb reboot bootloader
Flash recovery image (Depending on tab version)
FLO:
Code:
fastboot flash recovery TWRP_multirom_flo_20150328.img
DEB:
Code:
fastboot flash recovery TWRP_multirom_deb_20150328.img
Once flash is complete confirm by booting into recovery and check to see if SD/Partitions mounted. Click the small square in the bottom and see if everything mounted correctly. if you see any red status stating mount error in (system, userdata, system -w, cache, ect something went wrong repeat process)
From this point your are good to go. Be advised flashing roms has a very particular setup that needs to be followed, reported by several members. I will show below
Wugs Nexus Toolkit
http://forum.xda-developers.com/showthread.php?t=2389107
Download your recovery image
Open Wugs Nexus Toolkit
Setup device preference
Go into advance
Click flash recovery
choose recovery image file
Let toolkit do its thing and when complete click boot recovery to confirm everything went ok
On device
Use cf-auto root to root your tab. Google it as it not hard to find. Once you confirmed root you can then download your image file on device and use flashify, TRWP Manager, (anything you can flash recovery on device)
Example:
Once root is confirmed use Flashify to select recovery image to flash. Once flash is complete boot into recovery by any means. confirm no error are present.
**FLASHING ROMS**
When installing any ROM disable "inject multirom after installation" & after installation just hit reboot system (don't hit "MultiROM: Inject curr. Boot sector) once you hit reboot you should be fine!
Direct link to files and some info for recovery
http://forum.xda-developers.com/showthread.php?t=2457063
Good Luck and hope everything works out.
Ok so here goes my issue. I just got my Nexus 7 2013 in the mail yesterday. I bought it specially to install in my Mitsubishi Lancer. Well going thru the motion that nay flasher would go thru I got machine environment setup (drivers, adb/fastboot, wugs program).
I unlocked thru Wugs OEM unlock procedure then followed with root + custom recovery
Thats where my problems start. Root was not sticking correctly/at all. I got all kinds if error thru TRWP about it unable to mount emmc, boot, userdata, system,....
I have restored thru Wugs program several timers now. I have full access to the tab as far as ADB and Fastboot. I have tried
Phliz Rcovery
CWM
TRWP
In All recoverys I get errors that I cannot mount any partitions and reads 0MB available. I have found cf-auto root to root my Nexus 7 so at least theres that but Im trying to flash either Timurs Kernel or Elemental but cant due to recovery cannot mount anything.
What I have done so far...
OEM Unlock -Pass
Wugs root + custom recovery - failed due to mounting issues
cf-auto root - Pass
Fastboot Erase: System -w, system, userdata, boot, recovery, cache - Pass
Fasboot format: System -w, system, userdata, boot, recovery, cache - Pass
stock recovery factory reset/cache wipe - Pass
At this point am i just SOL and just return my tab ( got it thru Groupon for $149.99 brand new) or is there hope and maybe im just not getting it right which i doubt as I did the same for my Nexus 6 and unlocked/rooted.
--------------
I dont know if this will help but my Tab came in out of box 5.0.1. When booted up an update for 5.0.2 was available so I took it.
here are some screenshots to help better explain. These are off TWRP and CWM. Also got a pic of my computer telling me that im on a wrong system setup even though I havent changed anything.,
So I went ahead and did flashed stock recovery. I am able to wipe cache and factory reset. Im still wondering if it just any custom recovery Im flashing that is preventing any kind of mounting.
Starting to see a trend now. Anyone who somehow if you got your tab with 5.0.1 out of the box and either updated to 5.0.2 you may run into issues with custom recovery not being able to mount partitions and what not.
Posting as much info as I can to see if anyone can help me as well as the thread either above me or below with trwp issues. So i tried loading up CM Installer as usually thats my sure fire way to install a custom rom should something be wrong on my end. CM Installer went thru the motion of getting everything setup and right after is indicates to plug in device for prepping and flashing a service warning comes up saying that
"Firmware unsupported for your device at this time"
Then big blue button to close application. So Im not sure what do at at this time as I am currently exhausting all my resources and Google maybe be getting tired of all my Nexus 7 search request.
Also update on what other "procedures" that I attempted
Download terminal from Play store. Tried setting sd as full mount - FAILED
^^ this actually made my tab go full retard as boot up and then kept booting into recovery(TWRP) and if I tired to reboot system or shutdown it would just boot back into TWRP. I had to use WUGS to full flash stock.
Same when trying chmod commands to force mount or force -rw
Booted into recovery and attempted to "ADB Shell" in recovery. Commands were recognized but denied due to mounting issues.
As much abuse I send to it I can still recover from it. I am kinda concerned that if I abuse it to much I may break it. Heres a weird thing
I tried cf-autoroot and watched the commands go thru and saw that cf-auto root can mount /system and /data and declare full mount and root device. After that you see that it puts files in their respected places
So looks like twrp updated there recovery today gonna see if this fixes anything
Well the the TWRP 2.8.6.0 didn't work either. I'm not sure what to do at this point as I've tried as many things as I can google and can't figure it out. I'm afraid that if try to claim replacement by group on I may get another tab that is similar to this which means I may have problems progressing forward with my goals.
I'm in the same boat, I was surprised to see that the cf autoroot went through without a *****.
I also tried to flash a 4.4.4 image and it wouldn't boot up or go past the google logo.
If anyone has any insight to this,it would be greatly appreciated.
I'm going to try flashing from otg when my cable comes in. I'll report back after.
Having the same issue too. Unboxed mine today, and went to look how to root, I can unlock it fine but whenever I go in recovery I can't do anything. Android still boots fine...
fragon69 said:
I'm in the same boat, I was surprised to see that the cf autoroot went through without a *****.
I also tried to flash a 4.4.4 image and it wouldn't boot up or go past the google logo.
If anyone has any insight to this,it would be greatly appreciated.
I'm going to try flashing from otg when my cable comes in. I'll report back after.
Click to expand...
Click to collapse
Did your tab out the box come 5.0 or higher. Seems like anyone who got there tab recently had 5.0 or later factory installed. Also with bootloaders you cannot go back when you pass a certain update in this case you if you ever hit 5.0.1 or higher then you cannot go back to anything 4.x.x. Also depends on what your tab shipped with
TrentB said:
Having the same issue too. Unboxed mine today, and went to look how to root, I can unlock it fine but whenever I go in recovery I can't do anything. Android still boots fine...
Click to expand...
Click to collapse
Yeah same here. I wanna get a video of me trying to complete everything. I mentioned this earlier but I am thinking thinking that any tab recently received and has 5.x.x out of box may have a problem. I'm trying to get devs to look I to this but all I'm getting is just get another tab or buy a used one. It doesn't solve the fact that you can still pick up a new one in stores and the ones coning out now are on 5.x.x I'm not trying to buy a second tab from Craigslist when I have a brand new first owner tab in front of me. **sigh first world problems.
TrentB said:
Having the same issue too. Unboxed mine today, and went to look how to root, I can unlock it fine but whenever I go in recovery I can't do anything. Android still boots fine...
Click to expand...
Click to collapse
When you setup your nexus did were you on 5.0.1 and asking for update when you were done with setup
Yeah, I got mine from Groupon too. 5.0.1 out of the box. Running it now on 5.0.2 stock and it is OK so I may put off rooting for a while until it gets settled.
DEVICE build DATE2014.12 later
android.googlesource.com/kernel/msm.git/+/fa842060088619d2de9986c5c5d588d0f40534e3%5E%21/
.......TWRP2.8.6 no FIX X(
masterchiefb117 said:
Ok so here goes my issue. I just got my Nexus 7 2013 in the mail yesterday. I bought it specially to install in my Mitsubishi Lancer. Well going thru the motion that nay flasher would go thru I got machine environment setup (drivers, adb/fastboot, wugs program).
I unlocked thru Wugs OEM unlock procedure then followed with root + custom recovery
Thats where my problems start. Root was not sticking correctly/at all. I got all kinds if error thru TRWP about it unable to mount emmc, boot, userdata, system,....
I have restored thru Wugs program several timers now. I have full access to the tab as far as ADB and Fastboot. I have tried
Phliz Rcovery
CWM
TRWP
In All recoverys I get errors that I cannot mount any partitions and reads 0MB available. I have found cf-auto root to root my Nexus 7 so at least theres that but Im trying to flash either Timurs Kernel or Elemental but cant due to recovery cannot mount anything.
What I have done so far...
OEM Unlock -Pass
Wugs root + custom recovery - failed due to mounting issues
cf-auto root - Pass
Fastboot Erase: System -w, system, userdata, boot, recovery, cache - Pass
Fasboot format: System -w, system, userdata, boot, recovery, cache - Pass
stock recovery factory reset/cache wipe - Pass
At this point am i just SOL and just return my tab ( got it thru Groupon for $149.99 brand new) or is there hope and maybe im just not getting it right which i doubt as I did the same for my Nexus 6 and unlocked/rooted.
Click to expand...
Click to collapse
rsusami said:
DEVICE build DATE2014.12 later
android.googlesource.com/kernel/msm.git/+/fa842060088619d2de9986c5c5d588d0f40534e3%5E%21/
.......TWRP2.8.6 no FIX X(
View attachment 3231340
Click to expand...
Click to collapse
Hmmmm I just checked mine and its 2015/02. I got another yesterday and that one is 2015.01. FML looks like new Nexus 7 coming out made a revision.
Yea mine was from 2014.12, from groupon too
fragon69 said:
Yea mine was from 2014.12, from groupon too
Click to expand...
Click to collapse
TrentB said:
Yeah, I got mine from Groupon too. 5.0.1 out of the box. Running it now on 5.0.2 stock and it is OK so I may put off rooting for a while until it gets settled.
Click to expand...
Click to collapse
Kinda weird that Groupon selling nexus on deals a d they for some reason no work right. Lol
One more with same issue
Bought from Groupon as will, came with 5.0.1. Haven't updated to 5.0.2 yet.
Unlocked bootloader and installed TWRP. It cannot mount anything (tried 2.8.6.0, 2.8.2.2, 2.8.1.0).
I hope this is a fixable issue. Would hate to return the tablet.
texag said:
Bought from Groupon as will, came with 5.0.1. Haven't updated to 5.0.2 yet.
Unlocked bootloader and installed TWRP. It cannot mount anything (tried 2.8.6.0, 2.8.2.2, 2.8.1.0).
I hope this is a fixable issue. Would hate to return the tablet.
Click to expand...
Click to collapse
Looking at other forums reporting that all Nexus 7 bought from Groupon having the same problems. I bought 2 more, 1 from Frys and another from Best Buy. They are also having issues. Something that they are shipping with them that is making it a problem.
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
It will probably be the same as for my L900 with CM13 were I have to download the update, reboot into TWRP and update manually.
Sent from my SM-G900T using Tapatalk
nezlek said:
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
Click to expand...
Click to collapse
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
nezlek said:
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
Click to expand...
Click to collapse
Automated updates work fine for me. It automatically boots onto TWRP, applies the update, and reboots.
Might be a device-specific issue. I am on the OnePlus One, and the same TWRP version (of course made for my device).
I am guessing that perhaps there is an issue reading or writing the recovery script.
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
nezlek said:
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
Click to expand...
Click to collapse
BTW, are you able to navigate to that directory in TWRP?
Oops. Right after I clicked on send I realized I didn't answer your question!!
Yes, and the zip file is there, but nothing happened. As I said, far from fatal.
I updated my opo (Bacon) with the nightly ota download and most recent twrp, after reboot I had lost my home screen (2 of 3 pages remained) and several of the apps that I had dragged to those screens.. didn't work well for me. I let the ota reboot into twrp and it seemed to proceed without troubles until the opo came back to life. (finished booting)
Galaxy S5 SM-G900T here. Wiped my phone and installed lineage-14.1-20170131-nightly-klte-signed.zip with open_gapps-arm-7.1-stock-20170131 the day it came out and it has been good so far, no crashes or freezes and all apps work good except FolderMount, no biggie. Tried to install lineage-14.1-20170207-nightly-signed.zip and is giving me an "error 7 can't install this package on top of incompatible data". Any way to fix this without factory reset? Doesn't make sense to factory reset every week for an update.
Update: Tried to reflash lineage-14.1-20170131-nightly-klte-signed.zip and got the same error. So something must have changed. The only thing I can think of is I have SU 2.79 installed.
Update 2: Removed root, restored boot and same continues. I dont want to wipe on every update.
Sent from my SM-G900T using Tapatalk
Well, now semi-automatic at any rate.
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
First, sincere THANKS to jhedfors for this priceless bit of wisdom
Getting better. Still no "automatic update" but the latest "nightly" build did fire up TWRP, and put the update zip file into the aforementioned folder, and after that, installing it was the proverbial snap. I can't speak for everyone, but I would find no horror in the folks at Lineage giving in to reality and calling the "WEEKLY" as opposed to "NIGHTLY" builds.
Hey, since the only device I happen to have running Nougat at the moment also happens to be the OLDEST device I use on a regular basis, the Complaint Department shall remain CLOSED on this one. :angel:
I have an LG G3 (d855) with working LineageOS. The updater downloads OK and the zip is indeed in /data/data/org.lineageos.updater/app_updates, but TWRP refuses to do anything about it on reboot. I can browse to the folder manually, but it does feel that something isn't firing to get TWRP to perform the install automatically.
What is the trigger for TWRP to install a specific Zip on reboot?
D
For me, One Plus 3, automatic updates don't work. Also manually installing the latest
https://mirrorbits.lineageos.org/full/oneplus3/20170214/lineage-14.1-20170214-nightly-oneplus3-signed.zip gives me an error:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Zip file is corrupt!
Updating partition details...
...done
Any idea?
I did a migration via experimental build coming from cm13 then updated to lineage 14, which worked OK.
But since then I cannot update the daily builds.
I have the "same" issue on a Nexus 6.
The updater tells me I have an update, I ok it to download. Once done, I click install, gets into recovery and stops.
Still in the recovery, if I try to manually install from the downloaded location (data/data/...), it says zip failed.
I reboot and try opening that zip on a PC and sure enough, Windows thinks it is corrupt also.
If I re-download manually from "https://download.lineageos.org/shamu" that copy opens fine on the PC and when moved to the phone (data/data/...) installs fine.
There is something corrupting the zip when the updater does its thing. ;-(
Note: This isn't a migration, I have just been updating "nightlies".
Stuck in the TWRP...
Hi everyone, in trouble :/...I have got an LG d802 and updated TWRP from 2.8.7 to 3.0.2-1, then did a boot/system backup of the current cm 13.0 and after that the "experimental" update (as described in the recent update & builds post on lineageos) from cm 13.0 to lineage 14.1 which worked.
I decided to use lineage updater to go to the latest nightly as described which must have failed (booted in TWRP an did nothing...). When installing the 14.1 nightly manually, TWRP 3.0.2-1 showed two error lines with "unknown command".
Since then I'm stuck in TWRP.
Restore of cm 13.0 backup was not possible with neither TWRP 3.0.2-1 nor 2.8.7, no errors, just wouldn't boot. I can't even find any cm 13 build... to try to back which would be an option of course.
I did wipe the system then, lineage expermental + nightly or just nightly can be installed "successfully" with TWRP 3.0.2-1 and 2.8.7 with no errors there anymore, but also the system won't boot.
Please, please help (and/or redirect me to the right thread), what can I do? Thank you!
First, you can ignore the two errors in TWRP
I've gotten them with each update I've installed, but in my case - an LG v410 tablet - I have successfully, if manually, installed three updates so far, with a few peculiarities. "Automatic" is just a nine-letter word concerning updates at this point. I can live with that.
One - it is going to download it to /data/data in the tablet's storage no matter WHAT I do. I can live with that.
Two - I seem to have to download the update at least two times before the Lineage updater accepts the fact that it is there. I can live with that, too.
Three - a "getting there and almost what I want with no major glitches" Nougat build is much preferred to a KitKat build that LG couldn't give a rat's rear end about supporting, and I can DEFINITELY live with that.
But, back to YOUR problem with being stuck in TWRP. Worst case disaster recovery scenario - ANY chance you have a non-Lineage ROM you can revert to and start over from THERE? Realize what a pain that is going to be, but... When I still had CM 12.1 on it, I once did that out of desperation when nothing else seemed to be able to get it to boot. WHY such a laborious process fixed it I have NO IDEA, but better to have a working mystery than a well understood paperweight.
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
nezlek said:
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
Click to expand...
Click to collapse
I'm hanging in TWRP, also did wipe data before. I found a full 13.0 backup, selected all but Data because of storage space..."successful"...still system won't boot...
(Power Off in TWRP doesn't even work, just reboots, if that is of any help...)...A wild guess...file system issue maybe?
Yikes
As reasonable a guess as any, I suppose. I admit I've never had TWRP refuse to power off if nothing else, no matter how badly I had screwed things up (often spectacularly) elsewhere.
ASSUME you've tried the hold the power button until it shuts off, after which it should have booted to Android when powered on trick. Or, assuming you can do so, pull the battery?
Perhaps your bootloader is the culprit. Can you just re-flash that?
I got stuck in TWRP Recovery Boot-Loop. Already had the issue before with cm14.1 beginning of december. Didn't they fix the bug or is it another one?
For the specs: I got a Nexus 4 - mako.
I did this FIX and it booted up again as it was before: https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
What's now correct update? Download and dirty install manually in TWRP?
Thanks for the post
:good:
I've NEVER encountered that issue so glad to see someone has figured out a more elegant solution. I suspect your CM 14.1 problem is / was device (build for it) specific, as NONE of my CM / Lineage devices has ever done any such thing and they've all been updated several times in the last month.
In every case, however, I 've had to MANUALLY install the update zip file from within TWRP. Far worse things have happened and since I drive a stick shift car anyway, what the problem?
I have the XT1710-01 US variant, running on Sprint. I flashed the 64 bit TWRP and LOS to the device, and have two EFS backups, one by itself and one as part of a whole system backup before I flashed LOS. My current problem is that I got to the point after flashing LOS where the IMEI was 0. I tried to restore the EFS partition and it seemed to sort of work, as in I have the correct IMEI in the phone.
But when I restore the EFS partition, there is two errors that pop up:
E:Unable to find file system (first period).
and
Error opening: '/external_sd/TWRP/BACKUPS/.../efsg.emmc.win (no such file or directory)'
Through this, I get 3G, but not seemingly LTE, and only when the phone is set to Global, otherwise I do not get any service. I tried flashing a stock Oreo ROM, the RETAIL version, but the issue there was that when I flash that, it doesn't get past the 'bootloader is modified screen'. Any ideas on how to fix this? I would be fine with just getting network connectivity working again on LOS, although it would be nice to be back on stock again with the other minor issues I am having with LOS.
blackhole612 said:
I have the XT1710-01 US variant, running on Sprint. I flashed the 64 bit TWRP and LOS to the device, and have two EFS backups, one by itself and one as part of a whole system backup before I flashed LOS. My current problem is that I got to the point after flashing LOS where the IMEI was 0. I tried to restore the EFS partition and it seemed to sort of work, as in I have the correct IMEI in the phone.
But when I restore the EFS partition, there is two errors that pop up:
E:Unable to find file system (first period).
and
Error opening: '/external_sd/TWRP/BACKUPS/.../efsg.emmc.win (no such file or directory)'
Through this, I get 3G, but not seemingly LTE, and only when the phone is set to Global, otherwise I do not get any service. I tried flashing a stock Oreo ROM, the RETAIL version, but the issue there was that when I flash that, it doesn't get past the 'bootloader is modified screen'. Any ideas on how to fix this? I would be fine with just getting network connectivity working again on LOS, although it would be nice to be back on stock again with the other minor issues I am having with LOS.
Click to expand...
Click to collapse
What version of Twrp do you have?
Maybe the error is because the device is encrypted
elios2580 said:
What version of Twrp do you have?
Maybe the error is because the device is encrypted
Click to expand...
Click to collapse
I am using 3.2.1_r18 64 bit version. My phone doesn't seem to be encrypted right now, I don't have to put in a password when it boots or anything into LOS.
blackhole612 said:
I am using 3.2.1_r18 64 bit version. My phone doesn't seem to be encrypted right now, I don't have to put in a password when it boots or anything into LOS.
Click to expand...
Click to collapse
I fixed it by using RSDLite 6.2.4 to flash the stock Oreo image. For some reason, now it all works.
blackhole612 said:
I fixed it by using RSDLite 6.2.4 to flash the stock Oreo image. For some reason, now it all works.
Click to expand...
Click to collapse
Good job my friend, maybe you can share with us the command that u used
elios2580 said:
Good job my friend, maybe you can share with us the command that u used
Click to expand...
Click to collapse
There wasn't any command that I used. I started up RSDLite v6.2.4, loaded up the stock RETAIL Oreo ROM into RSDLite, and clicked on unpack and flash. The only hiccup I had was that I had to use a USB 2.0 port, all the 3.0 ports I tried resulted in RSDLite not finding the device. The phone just had to be in fastboot mode for this.
Hello.
I was fiddling around with my phone today and wanted to clear the cache from the Recovery.
After rebooting tho it showed me a message (note that I never toggled OEM unlock or even accessed recovery/download mode or anything before today):
fail to open recovery_cause(No such file or directory)#
Reboot Recovery Cause is [UNKNOWN]# No Support SINGLE-SKU
File Based OTA
Supported API: 3
MANUAL MODE v1.0.0#
Sucessfully verified dmverity hash tree
E:Failed to clear BCB message:failed to find /misc partition
Click to expand...
Click to collapse
And after a minute or so the Recovery showed up. I went to delete the cache, all went well until I was met with the same message at the end:
E:Failed to clear BCB message:failed to find /misc partition
Click to expand...
Click to collapse
Should I worry about anything ? The phone booted normally but I'm a bit skeptical about that error (maybe the cause of my as of late noticeable battery drain ?) and any help is appreciated!
EDIT: Another thing to notice is that when booting into recovery, it seems the phone is trying to install an update which isn't there, and only then takes me to the recovery menu.
Hir0xM said:
Hello.
I was fiddling around with my phone today and wanted to clear the cache from the Recovery.
After rebooting tho it showed me a message (note that I never toggled OEM unlock or even accessed recovery/download mode or anything before today):
And after a minute or so the Recovery showed up. I went to delete the cache, all went well until I was met with the same message at the end:
Should I worry about anything ? The phone booted normally but I'm a bit skeptical about that error (maybe the cause of my as of late noticeable battery drain ?) and any help is appreciated!
EDIT: Another thing to notice is that when booting into recovery, it seems the phone is trying to install an update which isn't there, and only then takes me to the recovery menu.
Click to expand...
Click to collapse
Everything you said I think is normal. So don't worry about it. It still clears cache or whatever you do.
SnowFuhrer said:
Everything you said I think is normal. So don't worry about it. It still clears cache or whatever you do.
Click to expand...
Click to collapse
I see, thank you
It's a weird bug so that's why I was worried. I did read some reports that some users couldn't wipe data due to this in the Recovery and it got me a bit worried.
Let's hope it's just a stupid bug and nothing more. Thanks again!
Hir0xM said:
I see, thank you
It's a weird bug so that's why I was worried. I did read some reports that some users couldn't wipe data due to this in the Recovery and it got me a bit worried.
Let's hope it's just a stupid bug and nothing more. Thanks again!
Click to expand...
Click to collapse
No problem. Report if it doesn't work.
SnowFuhrer said:
No problem. Report if it doesn't work.
Click to expand...
Click to collapse
Hi there
I have this issue. I cant factory reset the phone as it says MDM does not allow this.
so I used odion to reload the Stock Firmware on these but now I have FRP on this.
as it's a work device & dont know the user that last used this phone.
even after the flash I still have bcb message
Is there any other way of sorting this out.
UmangA said:
Hi there
I have this issue. I cant factory reset the phone as it says MDM does not allow this.
so I used odion to reload the Stock Firmware on these but now I have FRP on this.
as it's a work device & dont know the user that last used this phone.
even after the flash I still have bcb message
Is there any other way of sorting this out.
Click to expand...
Click to collapse
When you get into work phones, things get really ugly. Can you wipe data by flashing just csc in Odin?
Similar problem with S7, it just keeps rebooting
I have an S7, I have the same problem, the phone started freezing and rebooting every minute. So decided to Wipe out the cache and do factory reset, saw this message "E:Failed to clear BCB message:failed to find /misc partition"
The phone never goes past the Galaxy S7 Android logo screen most of the time, if it did manage to go pass, it freezes after 2 to 3 mins and reboots.
So I tried and successfully rooted, installed TWRP, took a backup and tried to wipe cache, it failed.
formatted the and tried to restore from backup and it failed, as it never went pass the S7 logo screen.
so I tried Lineage OS 17 and it worked like a charm
then tried back to Android 9 ROM from Samsung, it too started to hang and freeze - If it was an Hardware issue, I would expect Lineage OS to freeze too.
I think and it looks like Samsung is forcing its customers to buy new phones .....
Please help
thanks
Z
How to fix Galaxy J7 prime texting or calling issues: not receiving text or call aler
How to fix Galaxy J7 prime texting or calling issues: not receiving text or call alerts?
My phone is Samsung galaxy j7 prime
when I factory reset it show me this error E:Failed to clear BCB message: failed to open /dev/block/platform/13540000.dwmmc0/by-name/MISC: No such file or directory
Galaxy tab A 8
Even without appearing to have any hardware problems, my galaxy tab shows exactly the same messages described above and the same situations. I suspect it is even programmed obsolescence. Would anyone have any reliable tutorial on how to reset it completely and install a rom that was stable and compatible? Thank you :fingers-crossed::fingers-crossed:
Exactly the same problem
Hi guys,
I exactly do have the same problem. I upgraded from LineageOS 16 (which was working smooth.y ) to LineageOS 17.1 and faces a problem wit IMEI, So I tried to revert back to Stock ROM, flashed via ODIN latest version.
I could flash the stock ROM (doing NAND Eras and Re-Partition due to Vendor partition). But after reboot, the ROM won't boot and stuck with SAMSUNG screen blinking.. I managed to access the Stock Bootloader and could do a full factory reset, but I still get the error message like above.
If anyone has an idea how to solve...
My sister had many randomly chrashing apps and ask me how to fix it.
In recovery the same message was printed. BCB and /misc ...
Well I tried to clean install stock rom (A5 2017) with odin, but the user data was never deleted ... Don't know how to use odin ...
I have then flashed lineageos and now there are random reboots and apps are only crashing sometimes once opened.
I attached a crash log. The app crashin is called antennapod (https://play.google.com/store/apps/details?id=de.danoeh.antennapod&hl=de&gl=US)
Anyone knows what causing these? And if they are still related to BCB and/or /misc?
houston_ said:
I attached a crash log. The app crashin is called antennapod (https://play.google.com/store/apps/details?id=de.danoeh.antennapod&hl=de&gl=US)
Click to expand...
Click to collapse
Somehow tha attachment was delincined.
Log_2020-12-01_21-40-15.txt
drive.google.com
Hello,
It all began that i just wanted to restart my Oneplus3 unlocked with lineage 15.
But then back in Lineage15 i wasnt able to use my pin anymore + it restarted after few seconds...
Afterwards i ended up in a lineage bootloop.
Ok, then i thought then i do a fresh flash with new lineage 16.
I tried to flash but it said i need to install new modem firmware for Lineage16.
I downdloaded the new 9.0.5 modem + firmware and flashed it from here : https://forum.xda-developers.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066
Then i tried to flash LOS16 again but it failed due to some errors on unable to mount some partitions (cache , system, etc).
So i thought i need to wipe or reformat them, as some people suggested to switch from ext4 to fat and back to reinit the partition.
I did this for at least system and internal storage. ( i learned that it was a dumb idea )
Afterwards i was not able to push anything anymore through MTP in TWRP, but i was still able to sideload or push images via adb.
Afterwards i tried to flash LOS16 or LOS15 via TWRP again but it always ends up to a "unable to mount /system (invalid argument" error at some point of the installation.
I thought: Okey maybe i go back to stock as i messed up the internal file system somehow, and go back to LOS afterwards.
So i flashed the stock recovery for nougat which i got from here: https://www.****************/2017/0...th-latest-oxygen-os-firmware-complete-unroot/
Then i tried to flash various stock Oxygen roms with the stock recovery, by using wipe + system reset + adb sideload:
4.02, 4.51, 5.08, 9.0.5
4.02 and 9.0.5 didnt run until the end.
Flashing 5.08 works but ends up in a black screen when starting it.
Flashing 4.51 works but when i start it i run into a bootloop ( 2 Dots circuling forever )
I also tried to use the 4.51 version to flash LOS again but it did not work out
I just tried again to flash 4.51 but it also didnt work out anymore. :\
So, what do you think i could do to get a working OS on my system again?
Did i do something on the installation of LOS or Oxygen ?
Can i use a backup from a friends Oneplus3_T to get a working system partition / full OS again?
Should i unbrick the phone by using one of various guides to go back to fully stock? I am kind of afraid of this, as some people describe some final brick in the threads which may be caused by modem firmware problems (Sahara issue). https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/ or https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Thank you so much, i kind of getting mad about it
@julledd
Backup from 3T seems like a bad idea.
You may have a hardware issue.
Your best bet is to use one of the tools available in the various unbrick guides. If one doesn't work, try another.
Best of luck!
Hi thx for your help!
i tried different unbrick tools (9.0.5 / 3.1.2 / 4.0.5) and after several attempts i get it flashed to the phone. But in the end it still ends up in a bootloop, either at the android logo or the circuling dots. Via Sideload i am also not able to flash a new OS. It always breaks somewhen >50%.
In very rare cases i am then able to go to the OS, but when i go to "About Phone" to unlock it for TWRP, it freezes before showing anything. I guess there is internally something broken which forbids it to show the internal state of the phone. Every boot is different, and i cannot see any system in this failure of my phone.
Do you have any more hint?
I am already at a point where i want to exchange the main PCB.. Is this possible for the Oneplus3? Can i also exchange it with a Oneplus3T PCB?