Hi there, in my poco f1 i had OnePlus 7 port OnePlus R OB1, latest by the oofgang and last night the whole root partition was cleaned while my phone was in ideal state.The rom was rooted with latest Magisk, the data was not encrypted and the kernel i was using at that time was NoNameKernel4OOS_NYGGU&up-only.zip by amog787 which i installed that same day around 4-5 PM. Actually i was watching a video on YouTube around 1 Am and i had to take a break of 10 mins so i just turned off the screen and put it aside, when i came back it was in fastboot mode, i was confused.
I did reboot and it again went to fastboot mode so i rebooted to recovery and checked everything, i was very panicked and surprised that my whole root partition was gone including System, Data and Internal Storage everything except Bootloader and Recovery.
Can someone please explain how this is possible.
Ravindrasan said:
Hi there, in my poco f1 i had OnePlus 7 port OnePlus R OB1, latest by the oofgang and last night the whole root partition was cleaned while my phone was in ideal state.The rom was rooted with latest Magisk, the data was not encrypted and the kernel i was using at that time was NoNameKernel4OOS_NYGGU&up-only.zip by amog787 which i installed that same day around 4-5 PM. Actually i was watching a video on YouTube around 1 Am and i had to take a break of 10 mins so i just turned off the screen and put it aside, when i came back it was in fastboot mode, i was confused.
I did reboot and it again went to fastboot mode so i rebooted to recovery and checked everything, i was very panicked and surprised that my whole root partition was gone including System, Data and Internal Storage everything except Bootloader and Recovery.
Can someone please explain how this is possible.
Click to expand...
Click to collapse
I don't know why it happened but I remember reading that some OnePlus ports were very problematic and could even brick the phone. You should stick to the trusted ROMs like Lineage (which has official support and is very active) and find a theme that mimics OnePlus appearance instead.
duttyend said:
I don't know why it happened but I remember reading that some OnePlus ports were very problematic and could even brick the phone. You should stick to the trusted ROMs like Lineage (which has official support and is very active) and find a theme that mimics OnePlus appearance instead.
Click to expand...
Click to collapse
Thanks for replying bro, I'm not a OnePlus fan, just wanted to check it out. Well the whole purpose of this post was to find out how is this possible or if this was done by the rom, how come it waited for couple days and then formatted my root partition. I just want to know what happened and I'm quite sure it's impossible to format the whole root partition remotely.
Ravindrasan said:
Thanks for replying bro, I'm not a OnePlus fan, just wanted to check it out. Well the whole purpose of this post was to find out how is this possible or if this was done by the rom, how come it waited for couple days and then formatted my root partition. I just want to know what happened and I'm quite sure it's impossible to format the whole root partition remotely.
Click to expand...
Click to collapse
Yeah, you're right, it's pretty scary... Imagine if it happened on a phone full of valuable data...
Let's see if someone more savvy can give an explanation or hypothesis
Related
While i was new to the forum after buying my redmi note 3,i was wondering through the different posts of flashing recoveries and stock ROM's. Thats when i came across a thread which said that after wiping the storage(or something like that) while in MIUI i must boot MIUI once and then only my whole storage will be seen otherwise i would not get my whole storage. I don't remember who's post it was. Though i followed the instructions and now am using lineageOS.
Well,but the issue is not with my RN3, instead its with my letv le 1s in which i recently flashed lineage and now i have that error of not getting all the storage. In the guide i referred to,there was no mention of booting back to the Stock ROM,so after a wipe,i simply flashed Lineage OS.
Now i see 29.5gb used of 29.11 gb in storage although I don't have a single thing in there.
I know its off topic in terms if the phone bit I don't think the letv forum has people who will help me or maybe have the ability and experience to help me. So, its a request, before replying that i am not in the right place please help me if you can. Thanks.
Edit: Solved. Check 3rd post.
Sent from my Pixel XL using Tapatalk
deepjyoti30 said:
While i was new to the forum after buying my redmi note 3,i was wondering through the different posts of flashing recoveries and stock ROM's. Thats when i came across a thread which said that after wiping the storage(or something like that) while in MIUI i must boot MIUI once and then only my whole storage will be seen otherwise i would not get my whole storage. I don't remember who's post it was. Though i followed the instructions and now am using lineageOS.
Well,but the issue is not with my RN3, instead its with my letv le 1s in which i recently flashed lineage and now i have that error of not getting all the storage. In the guide i referred to,there was no mention of booting back to the Stock ROM,so after a wipe,i simply flashed Lineage OS.
Now i see 29.5gb used of 29.11 gb in storage although I don't have a single thing in there.
I know its off topic in terms if the phone bit I don't think the letv forum has people who will help me or maybe have the ability and experience to help me. So, its a request, before replying that i am not in the right place please help me if you can. Thanks.
Click to expand...
Click to collapse
Format your data partition.
JLius said:
Format your data partition.
Click to expand...
Click to collapse
Fixed now. I did tried formatting but earlier i wiped the internal storage but this time i wiped it from format data option and its done. Thanks fit the reply
Sent from my Pixel XL using Tapatalk
Hello, I've owned this phone since March and upon purchase went straight for "rooting" and the Pixel Experience ROM, I was successful with the flashing and haven't looked back until last weekend
I updated the PE rom and something went wrong! As of today I have a device that doesn't "see" wifi and the sim card(s). I've re-flashed several times "manually" even used the Xiaomi Fastboot Toolkit
on the last 2 attempts hoping the "modem/sim" would flash, apparently nothings worked. Thinking about getting a replacement MB for it as a last resort. Help please? Phillip
[email protected] said:
Hello, I've owned this phone since March and upon purchase went straight for "rooting" and the Pixel Experience ROM, I was successful with the flashing and haven't looked back until last weekend
I updated the PE rom and something went wrong! As of today I have a device that doesn't "see" wifi and the sim card(s). I've re-flashed several times "manually" even used the Xiaomi Fastboot Toolkit
on the last 2 attempts hoping the "modem/sim" would flash, apparently nothings worked. Thinking about getting a replacement MB for it as a last resort. Help please? Phillip
Click to expand...
Click to collapse
Have you updated your vendor firmware?
sotosgolf said:
Have you updated your vendor firmware?
Click to expand...
Click to collapse
Thank's for the reply, Yes, I've tried, with command line, MiTool and even Xiaomi's Pro tool I've been at this since yesterday The attempts mentioned "completed successfully" but NO wifi or SIM recognition! Motherboard? the phone has been restored to miui 10, and "actvated" using an "OTG" cable and looking thru the settings for any clues. the microsd card is recognized, bluetooth, everything else seems to be working. any thoughts? I've contacted "parts" dealers and I'm waitng. I think I'll take another break and come back to it over the weekend. Thanks for listening. Phillip
[email protected] said:
Thank's for the reply, Yes, I've tried, with command line, MiTool and even Xiaomi's Pro tool I've been at this since yesterday The attempts mentioned "completed successfully" but NO wifi or SIM recognition! Motherboard? the phone has been restored to miui 10, and "actvated" using an "OTG" cable and looking thru the settings for any clues. the microsd card is recognized, bluetooth, everything else seems to be working. any thoughts? I've contacted "parts" dealers and I'm waitng. I think I'll take another break and come back to it over the weekend. Thanks for listening. Phillip
Click to expand...
Click to collapse
I've been on custom ROMs since 2013 and fixing smartphones since 2015. I've only seen hardware related damage because of software only once and it was after someone flashed the full firmware of an entirely different phone into his own.
Don't spend the money on the motherboard before checking other software aspects.
Also (IF it's a hardware issue) your antenna cable might have gotten out of place because of a fall. You can't really know until you open the phone.
One can't really know, until they open the phone. If you're still on warranty, get it to your repair center.
sotosgolf said:
I've been on custom ROMs since 2013 and fixing smartphones since 2015. I've only seen hardware related damage because of software only once and it was after someone flashed the full firmware of an entirely different phone into his own.
Don't spend the money on the motherboard before checking other software aspects.
Also (IF it's a hardware issue) your antenna cable might have gotten out of place because of a fall. You can't really know until you open the phone.
Click to expand...
Click to collapse
If he Will open The back of the phone.
He will loose his Phone Warranty.
Flashed Th Stock MiUi.
Then Go To Service Centre.
If you have backup Restore The Backup.
Olystem said:
If he Will open The back of the phone.
He will loose his Phone Warranty.
Flashed Th Stock MiUi.
Then Go To Service Centre.
If you have backup Restore The Backup.
Click to expand...
Click to collapse
I didn't realize it looked like an urge for someone to open their phone without knowing what to do.
I'll edit.
[email protected] said:
Hello, I've owned this phone since March and upon purchase went straight for "rooting" and the Pixel Experience ROM, I was successful with the flashing and haven't looked back until last weekend
I updated the PE rom and something went wrong! As of today I have a device that doesn't "see" wifi and the sim card(s). I've re-flashed several times "manually" even used the Xiaomi Fastboot Toolkit
on the last 2 attempts hoping the "modem/sim" would flash, apparently nothings worked. Thinking about getting a replacement MB for it as a last resort. Help please? Phillip
Click to expand...
Click to collapse
It seems you lost/corrupted your EFS partition which contains your device IMEI/wifi/communication settings.
This is a problem in Xiaomi phones and Samsung phones as far as I remember. Once you start playing with custom roms this problem happens. I've always backup this "EFS" partition as soon as I unlock any xiaomi phone and it saved me couple of times when custom roms corrupts this partition I just boot to TWRP and restore it and it always works and I get sim card / wifi back again.
I'm not sure if there is a way to restore your EFS partition other than send it back for service center.
Based on your reply, Question(s) If the phone is "working/functioning" in my case "without wifi & sim" can I assume that my efforts to "bring back to stock" were successful? This is really what I've been wrestling with, Firmware, Stock rom, etc. Bootloader is still unlocked, Stock Recovery in place, I hope all that leaves is securing part(s) in this case a MotherBoard (modular?) to get "wifi & simcard" working again? Thank's XDA
The_wolf88 said:
It seems you lost/corrupted your EFS partition which contains your device IMEI/wifi/communication settings.
This is a problem in Xiaomi phones and Samsung phones as far as I remember. Once you start playing with custom roms this problem happens. I've always backup this "EFS" partition as soon as I unlock any xiaomi phone and it saved me couple of times when custom roms corrupts this partition I just boot to TWRP and restore it and it always works and I get sim card / wifi back again.
I'm not sure if there is a way to restore your EFS partition other than send it back for service center.
Click to expand...
Click to collapse
REPLY... funny that you mention this "EFS" one of the backups (4) of the PE rom I remember seeing this partition and only this one "saved" how can I re-flash this? Its still on the SD card I pulled, I'm going to check it or just save it for a tech when I bring it in for service and discuss it.
[email protected] said:
REPLY... funny that you mention this "EFS" one of the backups (4) of the PE rom I remember seeing this partition and only this one "saved" how can I re-flash this? Its still on the SD card I pulled, I'm going to check it or just save it for a tech when I bring it in for service and discuss it.
Click to expand...
Click to collapse
Easy just boot to TWRP and chose restore. Select your backup which contains EFS (Deselect other options like system, data etc.) and restore it.
Then boot to android and it should pickup the sim card and wifi.
Taking a break, tired... I have to re-install TWRP, then I'll check the SDcard tomorrow, and Post a GOOD conclusion... I hope! while i have your attention, as far as "service" any reccomendations? I split my time in Philadelphia/Maryland or I could ship if needed. Thank-you!
This happened to my girls poco, she has PE on it. All of a sudden thebphone dint read sim or sd (wifi was good). I switched the slots for each, had no effect, then i took her whole tray and inserted it into my poco where they worked. My sim and sd dint work in hers.
I updated vendor/firmware(no effect), clean flashed rom etc did everything, made a google backup and a twrp backup of data partition.
I ended up using mi flash to put miui fully back and it still dint work. I spent the night trying all this stuff and went to bed frustrated.
I woke up and decided ill just bring it to the phone repair shop downstairs and see (he has a poco). I have no idea how but we put her sim in and it worked, just like that, sd card also. I went back up installed twrp, flashed pe, restored data and she was right back to where she was after moving backup files.
I dont know if all this helps but its my short anecdote.
The_wolf88 said:
Easy just boot to TWRP and chose restore. Select your backup which contains EFS (Deselect other options like system, data etc.) and restore it.
Then boot to android and it should pickup the sim card and wifi.
Click to expand...
Click to collapse
I knew there was a "fix" I couldn't believe it was a "hardware" problem either... 2 good articles on "EFS Partitions" one here on XDA Read Up all!!! I'll post a "conclusion" when I
attempt tomorrow, need a break! Thanks too all that replied. Phillip
Poco is BACK!!! It was the EFS partition!, not a hardware issue at all, recovered from a backup after re-installing TWRP. Thanks to all... and especially Wolf88!
Sorry for the delay, out enjoying the day, ... https://dl.twrp.me/beryllium/ ... I used "3.2.3.2- Beryllium" if you have a "backup" just de-select everything but the "EFS" partition, thats what I did and it recovered successfully! Good luck!
poco wfi
hi just asking about backing up my EFS files as in imei number as there can come corrupt.i have backed them with twrp on google pixel rom not original rom will be ok as back up
berty321 said:
hi just asking about backing up my EFS files as in imei number as there can come corrupt.i have backed them with twrp on google pixel rom not original rom will be ok as back up
Click to expand...
Click to collapse
ROM doesn't matter. So long as you have the EFS partition backed up, it is good.
Some time ago it happened to me as well - no cellular and wifi. I fixed it by restoring from a full backup. I keep it on the SD so I can torture my phone any way I see fit and get away with it when I sc*ew things up.
Good to know the specific reason for losing the comms tho. Thanks for specifying. Next time I get there I'll start with efs restoration, instead of full system restore.
[email protected] said:
Hello, I've owned this phone since March and upon purchase went straight for "rooting" and the Pixel Experience ROM, I was successful with the flashing and haven't looked back until last weekend
I updated the PE rom and something went wrong! As of today I have a device that doesn't "see" wifi and the sim card(s). I've re-flashed several times "manually" even used the Xiaomi Fastboot Toolkit
on the last 2 attempts hoping the "modem/sim" would flash, apparently nothings worked. Thinking about getting a replacement MB for it as a last resort. Help please? Phillip
Click to expand...
Click to collapse
i happen to suffer from the same problem and I dont have a backup of efs or anything what solution can you give me?
[email protected] said:
Hello, I've owned this phone since March and upon purchase went straight for "rooting" and the Pixel Experience ROM, I was successful with the flashing and haven't looked back until last weekend
I updated the PE rom and something went wrong! As of today I have a device that doesn't "see" wifi and the sim card(s). I've re-flashed several times "manually" even used the Xiaomi Fastboot Toolkit
on the last 2 attempts hoping the "modem/sim" would flash, apparently nothings worked. Thinking about getting a replacement MB for it as a last resort. Help please? Phillip
Click to expand...
Click to collapse
You wipe the vendor and esf partition. You lost imei ,and wifi . Try hardware test ,because you lost gyroscope and etc working .flash a with fastboot stock miui and fő service .
My friend get same in note 7
Device: Redmi Note 4X (mido), Android 7, MIUI 10
Hey! Pardon me if I've placed my thread in an inappropriate place.
So, what I did was remove the system's finddevice app.
Then on some forum I read that it will cause a bootloop (phone is still on, working at this point). So I backed almost everything up and, in a moment of brilliance, went and rebooted the phone, at this point I went in and made a TWRP backup of the whole thing too.
I've got an unlocked bootloader and I am here for ideas what I can do with that in order to somehow fix my broken system. I know that I can just do a factory wipe, but since I only made a MIUI local backup prior to turning the phone off, that would mean setting up a lot of things from scratch, and also I see it as sort of an experiment to try and revive the dead system.
What I've tried is doing a wipe and only restoring the data partition from the old system. This doesn't seem to change anything.
I also tried making a backup of a working system and then recovering only the system partition of that, onto the broken version.
My experimenting leads me to believe that the data partition is indeed the one broken.
I will be interested in reading what you guys think about this.
So, my OnePlus 7t Pro McLaren (HD1913) has stucked in bootloop. I want to access my files but the device is encrypted. I tried unofficial TWRP but it doesn't support decryption. I also tried adb backup in stock recovery and also in TWRP, but ofcourse, no luck. Is there any way to access my files?
It's very secure... especially now.
Your only hope is to break the boot loop and get the current OS load to boot up.
Thank you for the fast reply!
blackhawk said:
It's very secure... especially now.
Your only hope is to break the boot loop and get the current OS load to boot up.
Click to expand...
Click to collapse
The problem about that is that I don't have the right boot.img which is from the latest 11.0.3.1HD01BA, all I could find is the previous 11.0.2.1HD01BA. Maybe you can help me with that? I was thinking about asking that in a separate thread, but it didn't seem like a good idea. I suppose that it will be available somewhere on xda in the coming weeks but in that case, I would rather flash the previous stock ROM even if I would lose my files.
momir64 said:
Thank you for the fast reply!
The problem about that is that I don't have the right boot.img which is from the latest 11.0.3.1HD01BA, all I could find is the previous 11.0.2.1HD01BA. Maybe you can help me with that? I was thinking about asking that in a separate thread, but it didn't seem like a good idea. I suppose that it will be available somewhere on xda in the coming weeks but in that case, I would rather flash the previous stock ROM event if I would lose my files.
Click to expand...
Click to collapse
You better tread very carefully here. How and where is the encryption stored? I would think your safest course of action be to find exactly what boot looped it and correct it by editing, line by line.
It's likely a 3rd party app that boot looped it.
Launchers and power management apps are likely candidates.
You're already way beyond my skillset. I run stock unencrypted devices in part because of disasters like this.
For all you know it could be a hardware failure or malware induced corruption. Those encryption keys are your only hope... if they are still intact and accessible.
Always redundantly backup critical data and NEVER encrypt backup drives. Do not clone copy media ie music files, cut/paste etc only.
Ok, I got lucky this time.
I have totally forgotten about Oxygen Updater app which is apparently great when it comes to keeping it up to date, so I downloaded the latest stock ROM with it, flashed boot.img, and bang, it booted perfectly! It took some time to download tho, but in the end, everything is great!
Hi!
Finally I got stuck in a boot loop on my Pixel 6 running QPR2.
It's looping after the G animation (vibrates a few times at that point when attached to a PC).
Reflashing the latest QPR factory image (without -w) by using SDK 33.0.3 does not solve the issue.
The ROM was running fine before, but it rebooted due to a faulty custom kernel version and now I'm stuck.
My theory is, that the launcher (nova) can't load and therefore it reboots.
Anything I could do using fastboot?
Never flash a custom kernel on a stock ROM, If not suggested by the dev.
I understand that you flash without wipe?
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Sui77 said:
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Click to expand...
Click to collapse
If the kernel broke your actually ROM, nope. You could backup the file stored locally via adb in the recovery, but not anything more.
Wipe all is the best, better than have to handle with an hard brick.
Sui77 said:
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Click to expand...
Click to collapse
If I were you I'd maybe get some logs and go through them and see if you can find anything that way. Maybe add logs to your op here.
There aren't many ways to backup things nowadays for pixel 6 but what I have used to backup apps + app data that works well when restoring is Neo app from Fdroid store. As far as backing up goes, at this time I've used nothing that is/has been as solid as Neo. I miss the days of just being able to boot one of a few various custom recoveries, making a nandroid backup to a USB thumb drive with my OTG cable and restore it whenever it was needed but things change. Sounds like maybe something was left behind from your kernel install. If you really dislike formatting I'd stay away from whatever you installed here to get in this loop but definitely backup using Neo once you get going again and put your backups on thumb drive or you PC or somewhere other than your device so you can restore them when you need to. I don't flash nowhere near as much as I used to but I used to flash my device(s) many times a day , everyday for many years but I remember years ago on another device I looped and wiped my cache and system and reflashed rom and ended up booting up. But that was another device years ago. Maybe try adb sideloading instead of factory image flash without wiping data. Try that and after it's done installing reboot to others slot and sideload it again... These things probably won't work but you never know until you try. Did you have magisk installed before and not now? Maybe flash stock kernel patched with magisk to both slots if so. Hate to say it but you will probably end up having to format data but idk because I don't know exactly how you installed the kernel "in detail" or exactly what kernel it is or if anything else was changed from before you looped ... No logs...
I've been using Android since the beginning (G1) and I've been tinkering with my devices since back in the Nexus S days on a regular basis and I've found that the best way for to get the help I need is to try like hell to figure whatever it is out myself by searching for the problem I'm having, I mean like really searching, sometimes for hours , sometimes maybe searching for things related to the problem I'm having that show up in my searches, sometimes the answer can be in another devices forum, piecing together bits of info from various places to try and solve whatever it is... etc ... etc... But the best way to get help is do research on it, take some notes, try various things to fix it, then if I still can't figure it out make a post about it here and in op attach every log I can possibly gather from said device, include all the things I tried to fix it with myself "in detail..." My exact installation process, you know like: reboot bootloader, was on slot A, executed ./flash-all.sh for factory image xxxxx, rebooted system ... The more details you provide the more accurate people will be when answering and the more people you will get to reply.. I'm not trying to sound like some asshole or anything at all. Im just speaking what works best here to get answers. Sometimes you just don't get any answers even if you post 18 paragraphs with a chart and a line graph, things you tried, what all you tried it with and links to it all. But anyone here who does this will most definitely stand a much better chance at getting some replies on whatever it is. I sometimes read over on Reddit and Tele groups , sometimes answers can be found that way. Sometimes people just give you the silent treatment.. Even if you do your homework. That's just a thing with anything related to development that happens. I always used to think when I would get no replies that the other guys and gals who know the answer are thinking to themselves, "oh look at this idiot here!" "He clearly didn't graduate from Harvard top of his class with a PhD like we did. " " Such an imbecile!!! " But what could have been going on and more than likely was/is is life , kids, bills, sleep, relationships, covid19, and tons of other things..
Some of this development stuff is a real beech to get and everyone works hard to get it and many aren't too fond of just giving random people answers that took them many sleepless nights to get. But if and when a dev sees someone with a detailed post , things tried.... etc ... etc .. Theyre much more likely to throw some knowledge your way. That's been my experience anyway.
@flash713
Wow, thx for thw write up, appreciate!
I was on latest QPR2.1 with Radioctive Kernel, Magisk installed.
Since the device got stuck in the boot animation, I tried a lot and flashed different factory images using the flash-all method. w/o success.
Also tried the Flash tool in the google website, also w/o success.
When the device boots while it's connected to the PC, it beeps/vibrates 3 times and the reboots.
My guess is that it has problems to load the launcher, Nova was set as standart.
I'm using android since years, tinkering a lot, but I'm not a pro in doing so.
Meanwhile i set up my new Pixel 7 and restored it via Google backup and a few apps by using a SWIFT backup.
Fotos were restored by Google, but all whatsapp pictures are messed up ow, cause the date of restore.
How do I gather proper logs?
Did a last attempt and sideloaded the OTA to both slots...same outcome...
Doesn't magisk have a remove all modules.zip? I mean oriole doesn't have TWRP available yet.
I presume that when it's bootlooping you don't have any ADB?
You did have ADB enabled, right?
Depending on system and setup you may have ADB started by init or started by Android.
Your problem could be as simple as a bad Launcher.
I don't know if the P6 has a UART console. Does it?
Hi Renate,
thx for your reply.
Yes, that is what i thought. The Pixel boots up into the G-animation and then loops 3 times (beeping/vibrating if connected to PC) and than reboots in total.
I think I had something like that in the past when I accidently deleted the launcher apk (don't ask )
Anyway, Nova launcher was set as standart, so the only idea could be to set the genui Pixel launcher as default, but I don't know how to do that in fastboot or adb mode.
Sui77 said:
Anyway, Nova launcher was set as standard, so the only idea could be to set the genui Pixel launcher as default, but I don't know how to do that in fastboot or adb mode.
Click to expand...
Click to collapse
I'm still not clear if you have ADB ever available.
If you do you could:
Code:
adb uninstall com.nova.whatever.launcher
If the /data/data that Nova is using is corrupt or missing it could cause failure.
Android will switch to whatever else belongs to android.intent.category.HOME automatically.
If there is nothing there you can install another launcher.
Have adb (after booting into recovery mode), will report back asap
I habe adbd device connected via recovery/rescue mode, but that's not working.
In bootloader, I can't use adb, no device connected.
Hw can I use adb while the device is not booted up?
Can you mount data in recovery (and it's unecrypted)?
Feeling a bit dumb, but I can only boot into fastboot or into the boot loop, don't know how to mount data in recovery mode (the one with the andoird robot)
When you're in the boot loop you don't get adb even for a few seconds?
This are the last lines of the recovery.log
2 new items by TheMrSui
photos.app.goo.gl
Checked that by opening a cmd and using "adb devices", but nothing showed up
When you're viewing that log, don't you have ADB working then? It says that it is.
I had this weird issue on Raven, first try using android flash tool through a chrome based browser. If that still loops then wipe, and flash an older image. For some reason I had to flash an image from the previous month and that would boot.