Database Users

Nexus 7 Bricked Very Badly

Hi, I bricked my n7 so badly. Here is what I did.
I accidentally flashed nakasig factory image on my wifi n7 from google factory images. It gave me a lots of errors.
I already had screen jamming issues when battery is < 5. Now my userdata partition is broken. I can't erase or format using recovery/fastboot. It always gives me errors. When I stay too much at recovery or bootloader it starts jamming. I can flash roms but it doesn't boots because of not working userdata partition and after waiting a while at boot animation. I can't turn my n7 on by just holding it for 2-3 seconds. I almost hold for 30-40 seconds everytime(Unless I choose reboot to recovery or reboot to bootloader from recovery or fastboot). Before people start saying flash the wifi factory image, yes I tried, even the 4.1.2 factory image. System partition gives me this error
Code:
sending 'system' (446268 KB)...
FAILED (status read failed (Unknown error)
finished. total time: 1.169s
I also found I can erase userdata partition after erasing system boot and cache it says ok but looks like its not working.
I can flash custom roms using sideloading but they don't boot.

Permanently stuck on "Starting apps"

After updates around 5.1.* my phone started playing up and was taking longer and longer to boot, eventually getting stuck with the four coloured dots swirling around.
Time to root the phone which I duly achieved with chainfires CF-Auto-Root via fastboot (since the phone wouldn't boot up/start). I then installed TWRP and sideloaded via adb the Cataclysm ROM (both the last Lollipop and the new Marshmallow versions), performing a full factory reset first, then for good measure making sure to wipe cache and dalvik cache again (should have wiped during factory reset).
All looks good, but on booting after optimizing the applications it hangs on "Cataclysm is installing... Starting apps" and will not progress any further. I left it five hours and no progress. Powered off and rebooted and back to where I started, hangs with the four coloured dots swirling around. This was with the Lollipop version of Cataclysm so I decided to give Marshmallow a go, same result, currently stuck on "Starting apps" now for 40 minutes.
Wiping cache and dalvik cache again just results in the the applications needing to be optomised each time.
Any thoughts, advice, suggested ROMs, kernels, tricks to try or ideas on how to recover the phone would be very much appreciated.
Thanks in advance,
enilkcals

Wipe from TWRP and Install just the Rom but do not install GAPPS. There may be problem with your GAPPS package. If the ROM boots perfectly, download and install different GAPPS package.

NEXUSg4 said:
Wipe from TWRP and Install just the Rom but do not install GAPPS. There may be problem with your GAPPS package. If the ROM boots perfectly, download and install different GAPPS package.
Click to expand...
Click to collapse
Cataclysm includes Gapps so I've had a go at flashing MinimalOS (5.1.1) which doesn't (after wiping Cache, Data and Dalvik Cache of course). Still hangs on boot animation and I left it half an hour just to make sure.
Tried with XenonHD without Gapps and it too just hangs at the boot animation.
Pretty stumped now as to whats going on or how to solve it.

Try flashing a factory image. That should return it to complete stock.
This guide tells you how: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
You should download the image from here though since the one in the guide is outdated. https://developers.google.com/android/nexus/images

theminikiller said:
Try flashing a factory image. That should return it to complete stock.
This guide tells you how: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
You should download the image from here though since the one in the guide is outdated. https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I'll give it a go, but it was on stock when the problem first arose and wiping cache/dalvik/data didn't help.
I'm slightly confused as to which to download though. There are only "occam" for Nexus 4 listed, so I guess its one of those (likely 5.1.1 (LMY48T) as its the most recent). But for the other ROMs I've been installing they've all been for "mako" and when I boot into Fastboot the display reads...
Code:
FASTBOOT MODE
PRODUCT_NAME - mako
VARIANT - mako 8GB
HW VERSION - rev_10
BOOTLOADER VERSION - MAKOz30f
BASEBAND VERSION - M9615A-CEFWMAZM-2.0.1701.07
CARRIER INFO - None
SERIAL NUMBER - 002fff0a560d4e29
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Wary of flashing the wrong ROM and screwing up the bootloader, as the instructions you linked (and on the image page itself) suggest the bootloader will be flashed and if I get that wrong there seems a high chance it will brick the phone.
How do I go about reconciling the device I have with the images available?

Occam is the right one. There is just several names for the device for some reason.

theminikiller said:
Occam is the right one. There is just several names for the device for some reason.
Click to expand...
Click to collapse
Thanks for the confirmation/sanity check.
Code:
# fastboot devices -l
002fff0a560d4e29 fastboot usb:2-2
occam-lmy48t # fastboot flash bootloader bootloader-mako-makoz30f.img
sending 'bootloader' (2264 KB)...
OKAY [ 0.080s]
writing 'bootloader'...
OKAY [ 0.332s]
finished. total time: 0.413s
occam-lmy48t # fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.050s
occam-lmy48t # fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.07.img
sending 'radio' (45537 KB)...
OKAY [ 1.445s]
writing 'radio'...
OKAY [ 2.540s]
finished. total time: 3.986s
occam-lmy48t # fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.050s
occam-lmy48t # fastboot -w update image-occam-lmy48t.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 6189744128
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 23612
Label:
Blocks: 1511168
Block groups: 47
Reserved block group size: 375
Created filesystem with 11/378256 inodes and 50366/1511168 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: MAKOZ30f
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.07
Serial Number........: 002fff0a560d4e29
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6448 KB)...
OKAY [ 0.211s]
writing 'boot'...
OKAY [ 0.337s]
sending 'recovery' (7008 KB)...
OKAY [ 0.237s]
writing 'recovery'...
OKAY [ 0.401s]
erasing 'system'...
OKAY [ 0.813s]
sending 'system' (834934 KB)...
OKAY [ 28.409s]
writing 'system'...
OKAY [ 47.296s]
erasing 'userdata'...
OKAY [ 1.400s]
sending 'userdata' (98413 KB)...
OKAY [ 3.401s]
writing 'userdata'...
OKAY [ 5.233s]
erasing 'cache'...
OKAY [ 0.056s]
sending 'cache' (10984 KB)...
OKAY [ 0.377s]
writing 'cache'...
OKAY [ 0.629s]
rebooting...
finished. total time: 88.871s
Rebooted and sitting on the booting screen with four coloured dots swirling around. Off to bed, will see if anything has happened tomorrow. Thanks again.

I think when this happened to be I had the wrong modem radio , I flash a new one appropriate for 5.1 and I was working after that.

Left it over night and still stuck on the boot animation.
Any more suggestions/ideas of things to try would be very welcome, but its looking like this phone has given up the ghost which is a bit of a shame as it would have made a nice backup.

Sadly, I don't have any other ideas.
In any case, good luck fixing it!

Thanks for your suggestions and help, appreciated.

cloneman1 said:
I think when this happened to be I had the wrong modem radio , I flash a new one appropriate for 5.1 and I was working after that.
Click to expand...
Click to collapse
Do you happen to have details of which modem radio you used? Not much for me to go on otherwise.
I've tried the official stock ROM from Google as theminikiller suggested and would expect that to have the correct modem radio included within it (which for 5.1.1 was the file radio-mako-m9615a-cefwmazm-2.0.1701.07.img that was bundled in with occam-lmy48t-factory-416938f1.tgz).

enilkcals said:
Thanks for your suggestions and help, appreciated.
Click to expand...
Click to collapse
hi i too had a similar issue.it was somewhat similar.my battery was dying.i tried installing stock rom.it never gotten past optimising apps screen.i tried some custom rom without gapps which booted fine. i used it a few days without gapps then the battery eventually died.it couldnt get past bootanimation.it can however stay in stock/twrp recovery.
so if you can try booting up the phone with a charger connected then the battery may be the issue. if it still didnt bootup go to a local service center ask them to open up nd remove battery and connect it directly to a power source in battery terminals.if the phone boots up fine you can order a new oem battery.[emoji3]
Sent from my Nexus 4 using Tapatalk

jaison thomas said:
hi i too had a similar issue.it was somewhat similar.my battery was dying.i tried installing stock rom.it never gotten past optimising apps screen.i tried some custom rom without gapps which booted fine. i used it a few days without gapps then the battery eventually died.it couldnt get past bootanimation.it can however stay in stock/twrp recovery.
so if you can try booting up the phone with a charger connected then the battery may be the issue. if it still didnt bootup go to a local service center ask them to open up nd remove battery and connect it directly to a power source in battery terminals.if the phone boots up fine you can order a new oem battery.[emoji3]
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Hi,
Thanks for the suggestion, I have already tried booting with the charger plugged in (both USB from cable and a micro-USB charger from the mains).
I sent the phone back to LG last year and had the battery replaced under warranty then (just checked and last email communication was 2014-10-22) having bought the phone 2013-08-17. I guess since thats about a year its not unreasonable to think the battery could be worn out again. Not sure whether LG will replace under warranty and wary of throwing cash down the drain, but might see if can find one and replace it.
Thanks for the idea.
slackline

Hi,
Had a very similar thing happen to me. Turned out the radio was dying - something basic about loading firmware to it during very early hardware boot up.
Figured this out after a long process - and solution was to keep on soft rebooting it until the firmware loaded successfully - then Android booted ok - otherwise it would hang at starting apps.
James
enilkcals said:
Hi,
Thanks for the suggestion, I have already tried booting with the charger plugged in (both USB from cable and a micro-USB charger from the mains).
I sent the phone back to LG last year and had the battery replaced under warranty then (just checked and last email communication was 2014-10-22) having bought the phone 2013-08-17. I guess since thats about a year its not unreasonable to think the battery could be worn out again. Not sure whether LG will replace under warranty and wary of throwing cash down the drain, but might see if can find one and replace it.
Thanks for the idea.
slackline
Click to expand...
Click to collapse

Boot-looping Nexus 6P - caused by Photo Sphere?

First post here at XDA - before I start with my problem, I should say thanks to everyone who posts here. I've come across this site so often when looking for information and always found it to be very helpful.
I was taking a Photo Sphere photo a few weeks ago, and after the photo had been taken, and during the processing/rendering stage, I looked away from my phone while holding it to let it work. I looked down to see the finished result about 30 seconds later and saw the Google startup screen. It appears that somehow, taking a Photo Sphere photo may have soft bricked my 6P, but I have no idea how. The phone itself was working perfectly normally prior to that.
I kept manually restarting it, powering it off, booting to recovery and restarting to see if I could get it back to normal with no success. It would occasionally, maybe one in twenty times, get to the Android boot animation, but would freeze after around 5 seconds on that, then restart again. Eventually, I thought to clear the cache partition via TWRP, so I did so and it then booted and loaded Android as normal. However, one of the first things I did was go to Settings to reset the time as it was wrong, and, as soon as it displayed the Settings screen, the phone restarted again, and no amount of cache clearing has resolved the issue since.
It's a 64GB 6P running Marshmallow 6.0.1, unlocked and rooted via Heisenberg's excellent guide and running TWRP 3.0.2.0, which was the latest available when I rooted. Right now, upon starting, it shows the "Your device software can't be checked for corruption. Please lock the bootloader." message as normal, then the Google logo, then it restarts and does the same again. I can access recovery mode as normal.
Does anyone have any ideas what steps I need to take to get my 6P operable again? Given that it booted after I wiped the cache then rebooted when I went to settings, my relatively uneducated presumption is that the root has somehow gotten messed up, but I don't know enough about troubleshooting Android to resolve it myself. I'd obviously prefer to avoid wiping it and losing data if possible. Although I'm a computer geek, I'm not 100% sure about Android ADB/fastboot commands and what to run to resolve this issue, so I thought I should defer to the experts here. I was considering flashing the factory image (part 11 of Heisenberg's guide) to see if that helped, but wasn't sure if that's the best first step to try at this point so thought it best to seek some advice rather than turn a soft brick into a hard one.
Thanks for any and all assistance!
BL: angler-03.51
Baseband: angler-03.61
Product/Variant: ANGLER-ROW-VN1
Device is UNLOCKED.
Qfuse Status: ENABLED.

Well, maybe the above is a bit too much to read...my bad habit of being verbose. Here's a tl;dr version;
Unlocked and rooted 64GB 6P running Marshmallow is boot-looping at the bootloader unlocked screen
Wiping cache only temporarily resolved
Can access recovery and fastboot as normal
Any ideas?

Well, mine appears to have done the same exact thing, but I wasn't using photosphere. Before I continue, here's my story...
I'm on vacation from Sept 1st to Sept 5th, and on the 4th(yesterday), I was browsing using Chrome before it froze and shut off on me, which then turned into a bootloop with the Google screen. Next, I did what I normally do when I have a problem, I head to recovery(depending on what I was last doing, I'd delete a file that I know caused it), but instead, I couldn't get into recovery. I tried maybe about 10 times and got into recovery twice. I removed all overlays that had to do with Substratum and deleted my cache/dalvik cache, rebooted and I got to the Android updating screen. It went through the process, froze and rebooted again. Now, I'm at the point where it's just the Google screen. I can get into the Bootloader, but nothing else. I'm thinking I'm having hardware failure or something. I attempted to do a factory image restore twice now, doing the third one as I type this before I contact Google, but yeah... I can't get into recovery or past the Google screen. Only the bootloader is accessible.
Now... As for your situation, download Wugfresh Nexus Toolkit, or follow later on in Heisenberg's guide to restore the factory image without deleting the userdata partition. There may still be a chance for you to get your data back, but for me... nah. Good luck.

Hey Curiousn00b, thanks for sharing your story. It seems really weird that they're just dying so suddenly and so fatally with no hardware failures. I'm wondering if this is part of a larger issue.
I just tried flashing the factory images for MHC19I as per part 11 of Heisenberg's guide and, alas, no luck. The images flashed fine, but it's still doing the same thing as before.
Is there anything else I can do to get it to a usable state again without completely wiping it? Should I try another factory image, maybe an earlier one? And, if I do have to wipe it, can I re-flash TWRP recovery and take a backup first?
Here's my log output for confirmation. Thanks again, I appreciate your reply.
Code:
C:\SDK\platform-tools>fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.105s]
writing 'bootloader'...
OKAY [ 0.237s]
finished. total time: 0.345s
C:\SDK\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.013s
C:\SDK\platform-tools>fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.202s]
writing 'radio'...
OKAY [ 2.855s]
finished. total time: 4.060s
C:\SDK\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.016s
C:\SDK\platform-tools>fastboot flash boot c:\angler\images\boot.img
target reported max download size of 494927872 bytes
sending 'boot' (12045 KB)...
OKAY [ 0.287s]
writing 'boot'...
OKAY [ 0.387s]
finished. total time: 0.676s
C:\SDK\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.036s]
finished. total time: 0.037s
C:\SDK\platform-tools>fastboot flash cache C:\angler\images\cache.img
target reported max download size of 494927872 bytes
erasing 'cache'...
OKAY [ 0.018s]
sending 'cache' (5752 KB)...
OKAY [ 0.161s]
writing 'cache'...
OKAY [ 0.226s]
finished. total time: 0.409s
C:\SDK\platform-tools>fastboot flash recovery C:\angler\images\recovery.img
target reported max download size of 494927872 bytes
sending 'recovery' (12977 KB)...
OKAY [ 0.337s]
writing 'recovery'...
OKAY [ 0.406s]
finished. total time: 0.747s
C:\SDK\platform-tools>fastboot flash system C:\angler\images\system.img
target reported max download size of 494927872 bytes
erasing 'system'...
OKAY [ 0.561s]
sending sparse 'system' (478066 KB)...
OKAY [ 12.529s]
writing 'system'...
OKAY [ 6.772s]
sending sparse 'system' (483054 KB)...
OKAY [ 12.458s]
writing 'system'...
OKAY [ 7.038s]
sending sparse 'system' (480089 KB)...
OKAY [ 12.603s]
writing 'system'...
OKAY [ 14.026s]
sending sparse 'system' (469850 KB)...
OKAY [ 12.264s]
writing 'system'...
OKAY [ 22.259s]
sending sparse 'system' (55828 KB)...
OKAY [ 1.530s]
writing 'system'...
OKAY [ 2.856s]
finished. total time: 104.912s
C:\SDK\platform-tools>fastboot flash vendor C:\angler\images\vendor.img
target reported max download size of 494927872 bytes
sending 'vendor' (185185 KB)...
OKAY [ 4.567s]
writing 'vendor'...
OKAY [ 15.101s]
finished. total time: 19.670s
C:\SDK\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.008s
C:\SDK\platform-tools>

Seems like it's possible for you to be in the same exact situation as me, unless you can boot into recovery. I can't do that.
If you can boot into recovery, just take your files off the device and go for a full wipe. I think my device hard bricked itself somehow... You may be soft-bricked, but in the worst case, hard bricked. :c

Yep, I can't boot into recovery either right now because I flashed the factory image. I'll try to re-flash the TWRP recovery and see how it goes.
I can't believe a software issue can get to the stage of hard-bricking your phone while doing nothing other than unlocking and rooting it, and even putting it back to factory and doing a full wipe doesn't resolve it. I really hope I don't get to that stage, although it's disappointing to hear that you've had that experience. Thanks again for your feedback, I'll update once I've attempted to re-flash.

So I finally got around to flashing the TWRP 3.0.2.0 recovery again and still no dice, so I made a start on the backup process.
One thing I wanted to check before I do the full wipe and reinstall stock, though - my partitions in TWRP showed this from the Backup screen;
Code:
Boot (32MB)
System (1850MB)
System Image (3072MB)
Vendor (173MB)
Vendor Image (200MB)
Data (0MB)
Cache (0MB)
Recovery (32MB)
EFS (8MB)
This may just be paranoia, but which of those is the user data (apps, files, photos etc.) stored in? I get that the Data partition is wiped when doing the stock image install, so that's fine, but I presume System would be the OS itself - and I'm pretty sure I have more than 2-3GBs of data on my 6P, but the largest there is 3GB.
Also, using Backup from the TWRP main menu, how do I restore the user data once I've got it back up and running again without killing the OS again? Can I selectively choose what to restore?
I've copied the TWRP backup folder to my laptop using adb pull, so that's safely stored there for now. Just wanted to check before I totally wipe everything and start clean.
Thanks.

MarkB16 said:
So I finally got around to flashing the TWRP 3.0.2.0 recovery again and still no dice, so I made a start on the backup process.
One thing I wanted to check before I do the full wipe and reinstall stock, though - my partitions in TWRP showed this from the Backup screen;
This may just be paranoia, but which of those is the user data (apps, files, photos etc.) stored in? I get that the Data partition is wiped when doing the stock image install, so that's fine, but I presume System would be the OS itself - and I'm pretty sure I have more than 2-3GBs of data on my 6P, but the largest there is 3GB.
Also, using Backup from the TWRP main menu, how do I restore the user data once I've got it back up and running again without killing the OS again? Can I selectively choose what to restore?
I've copied the TWRP backup folder to my laptop using adb pull, so that's safely stored there for now. Just wanted to check before I totally wipe everything and start clean.
Thanks.
Click to expand...
Click to collapse
Did you verify any contents in TWRP that you pulled to ur PC? . In TWRP go to advanced and then file explorer, you should see your data.
Edit: Data would be where the user data is stored (pictures, downloads, etc.)
I terms of restoring data, I've always gone with Titanium Backup but in this case not sure you'd be able to as it sound like u can't boot into the OS and see ur apps?

spunks3 said:
Did you verify any contents in TWRP that you pulled to ur PC? . In TWRP go to advanced and then file explorer, you should see your data.
Edit: Data would be where the user data is stored (pictures, downloads, etc.)
I terms of restoring data, I've always gone with Titanium Backup but in this case not sure you'd be able to as it sound like u can't boot into the OS and see ur apps?
Click to expand...
Click to collapse
Yep, if I go to TWRP, I can view the backups in the \sdcard\TWRP\backups\[serial number] folder, and now that I've done adb pull, they're on my hard drive, too.
Exactly, yeah, it's still boot-looping, so I can't get into the OS to run Titanium Backup or migrate any data. It's still looping at the "Device can't be checked for corruption" screen. I followed Heisenberg's guide to re-flash the stock images and didn't flash userdata. Why would the data partition show as being empty in TWRP unless the partition has been royally messed up when the phone had it's original heart attack?
And, if the data partition is where userdata is stored, I presume that means the data on the phone is already gone? Dumb question, I think I know the answer already, but don't understand how it could have happened when I didn't wipe it myself.

MarkB16 said:
Yep, if I go to TWRP, I can view the backups in the \sdcard\TWRP\backups[serial number] folder, and now that I've done adb pull, they're on my hard drive, too.
Exactly, yeah, it's still boot-looping, so I can't get into the OS to run Titanium Backup or migrate any data. It's still looping at the "Device can't be checked for corruption" screen. I followed Heisenberg's guide to re-flash the stock images and didn't flash userdata. Why would the data partition show as being empty in TWRP unless the partition has been royally messed up when the phone had it's original heart attack?
And, if the data partition is where userdata is stored, I presume that means the data on the phone is already gone? Dumb question, I think I know the answer already, but don't understand how it could have happened when I didn't wipe it myself.
Click to expand...
Click to collapse
You should be able to confirm if the data is really there or not by going into TWRP > Advanced > File Manager.
You should also check to see if data and cache are mounted in TWRP.
I haven't gone over Heisenberg's steps yet but, since you've already attempted to flash userdata, whatever you had is most likey gone.
Try the following via fastboot for erasing everything and starting from scratch.
NOTE: THE FOLLOWING COMMANDS WILL ERASE EVERYTHING ON YOUR PHONE.
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader [name of your file].img
fastboot reboot-bootloader
fastboot flash radio [name of your file].img
fastboot reboot-bootloader
fastboot flash recovery [name of recovery file].img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
fastboot format userdata
fastboot format cache

That's what I'm saying - at no point have I ever entered the command fastboot erase userdata - I specifically wanted to keep the data and do a backup, and the phrase userdata would be a big red flag to me, so I wouldn't enter it unless I knew for sure the data was already gone. I'm wary of even touching the data partition, so I've been sure to follow all of the commands very carefully. I've been in I.T. for a while, I know the danger of running the wrong command.
I can see that there are data files in the backups, however the data.ext4.win file is only 6KB, so I guess there's no data there.
I don't know how to mount the data and cache partitions in TWRP - I can see the option to do it, but have no idea what it does.
Thanks again.

Mine was the Camera app doing the HDR processing. For the first few times it happened, it was random - the crash and bootloop will happen after taking 2-3 photos. Today, it finally hung while processing HDR and it never recovered. Sigh, seems like I need to send my phone to Huawei. I have tried all sorts of flashing to no avail.

kurtisnet said:
Mine was the Camera app doing the HDR processing. For the first few times it happened, it was random - the crash and bootloop will happen after taking 2-3 photos. Today, it finally hung while processing HDR and it never recovered. Sigh, seems like I need to send my phone to Huawei. I have tried all sorts of flashing to no avail.
Click to expand...
Click to collapse
So my phone isn't the only one with an aversion to taking photos? I don't understand how just taking a photo could cause this unless there's a massive software bug somewhere that requires a very specific set of conditions to brick your device. Would you mind letting me know what Huawei say to your issue? I'm curious as to what they think could cause a failure of this degree.

MarkB16 said:
That's what I'm saying - at no point have I ever entered the command fastboot erase userdata - I specifically wanted to keep the data and do a backup, and the phrase userdata would be a big red flag to me, so I wouldn't enter it unless I knew for sure the data was already gone. I'm wary of even touching the data partition, so I've been sure to follow all of the commands very carefully. I've been in I.T. for a while, I know the danger of running the wrong command.
I can see that there are data files in the backups, however the data.ext4.win file is only 6KB, so I guess there's no data there.
I don't know how to mount the data and cache partitions in TWRP - I can see the option to do it, but have no idea what it does.
Thanks again.
Click to expand...
Click to collapse
If at anytime you did 'fastboot flash userdata userdata.img' you've overwritten the data partition and lost the data :-/ wish I could help more...

MarkB16 said:
So my phone isn't the only one with an aversion to taking photos? I don't understand how just taking a photo could cause this unless there's a massive software bug somewhere that requires a very specific set of conditions to brick your device. Would you mind letting me know what Huawei say to your issue? I'm curious as to what they think could cause a failure of this degree.
Click to expand...
Click to collapse
I've just collected my phone again from Huawei. They replaced the motherboard (new imei number). Sent in at 11.30am today and is ready by 4pm. Applaud Singapore Huawei service center for their super fast turnaround time. Totally was expecting at least a week of repair lol.
Mine was bricked completely - internal storage was accessible from twrp but that was about it. Flashing new roms with everything wiped didn't help. Flashing pure nexus also will sometimes hang and reboot. Sometimes it'll be successful.

spunks3 said:
If at anytime you did 'fastboot flash userdata userdata.img' you've overwritten the data partition and lost the data :-/ wish I could help more...
Click to expand...
Click to collapse
But I didn't, that's what I mean - it's like the data partition has been wiped for no reason at all, or it was part of the initial failure. I haven't run any commands which should touch that partition.
Am I right in thinking that, at this stage, the my data is unrecoverable, and the best bet is just to try to get the phone back up and running again? Are there any other checks I could try to confirm the data is already gone?
Thanks, I do appreciate your input.
kurtisnet said:
I've just collected my phone again from Huawei. They replaced the motherboard (new imei number). Sent in at 11.30am today and is ready by 4pm. Applaud Singapore Huawei service center for their super fast turnaround time. Totally was expecting at least a week of repair lol.
Mine was bricked completely - internal storage was accessible from twrp but that was about it. Flashing new roms with everything wiped didn't help. Flashing pure nexus also will sometimes hang and reboot. Sometimes it'll be successful.
Click to expand...
Click to collapse
Nice, glad they got it sorted so quickly for you. Hoping I can get mine running again, but I'll contact them if I can't.

MarkB16 said:
But I didn't, that's what I mean - it's like the data partition has been wiped for no reason at all, or it was part of the initial failure. I haven't run any commands which should touch that partition.
Am I right in thinking that, at this stage, the my data is unrecoverable, and the best bet is just to try to get the phone back up and running again? Are there any other checks I could try to confirm the data is already gone?
Thanks, I do appreciate your input.
Nice, glad they got it sorted so quickly for you. Hoping I can get mine running again, but I'll contact them if I can't.
Click to expand...
Click to collapse
Hmmmmm... The only other thing that comes to mind is trying something like a fastboot pull command

I've done a full adb pull for all the partitions already, and the data partition file was only 6KB.

One thing I clearly forgot about - I can use File Manager to confirm if the data is there. I've checked there, and all of the files and folders on my device still appear to be shown as normal - if I check /sdcard/DCIM/Camera, I can see my photos, if I check /sdcard/Downloads, I can see stuff I've downloaded, etc. However, when I go to the TWRP menu and choose Backup, the Data partition is 0MB. Tapping Refresh Sizes doesn't change anything.
So if the userdata is stored on the Data partition and I can confirm the files are still on the phone, how is the Data partition showing as 0MB in the Backup screen? What on earth is going on?

The data partition that you backed up isn't userdata, it's the installed apps partition. There is a separate partition for userdata. When installing a new rom, wiping /data in twrp is always a good idea but it won't touch your userdata.
You should be able to mount your phone to your PC while in twrp and copy all your data over, then proceed w a full factory flash to try and correct your problem. When you mount it, it will show up on PC just like a thumb drive.

Wiped system with TWRP, stuck with a bootloop

This morning my phone (with a recent lineage nightly) was off when I got up and when I tried to turn it on it said my password was wrong, which I am positive it was not. For some reason I decided to "solve" the problem by going into TWRP and wiping/formating everything (including system) and then installing a fresh copy of lineage, and flashing the bootloader and vendor. Once I did that it started bootlooping, I could get into bootloader but not recovery. After some playing with it I found that the 4 cores modified twrp would work, so I tried installing some roms from there with no luck. Then tried flashing a variety of factory images, none of which work, including the 48C 7.12 image with the 4 cores boot image, as well as the same with the ex4.12 kernel flashed over it.
Is there anything I can do, or is it just time to shop for a new phone?

Dacull said:
This morning my phone (with a recent lineage nightly) was off when I got up and when I tried to turn it on it said my password was wrong, which I am positive it was not. For some reason I decided to "solve" the problem by going into TWRP and wiping/formating everything (including system) and then installing a fresh copy of lineage, and flashing the bootloader and vendor. Once I did that it started bootlooping, I could get into bootloader but not recovery. After some playing with it I found that the 4 cores modified twrp would work, so I tried installing some roms from there with no luck. Then tried flashing a variety of factory images, none of which work, including the 48C 7.12 image with the 4 cores boot image, as well as the same with the ex4.12 kernel flashed over it. Is there anything I can do, or is it just time to shop for a new phone?
Click to expand...
Click to collapse
Have you tried the workaround of disabling big cores with EX Kernel? There is an XDA thread dedicated to it. From your post I'm not sure if you disabled the cores or not.

v12xke said:
Have you tried the workaround of disabling big cores with EX Kernel? There is an XDA thread dedicated to it. From your post I'm not sure if you disabled the cores or not.
Click to expand...
Click to collapse
I didn't, I thought it has already been done. But now even the 4 core twrp just gives me a splash screen followed by a momentary page of text and then crash.
Edit: Nevermind, I misunderstood you. I installed the EX kernel from this thread.
I also just managed to somehow override whatever was crashing twrp by pushing the power button right when the text screen was showing. Flashed the EX kernel again, but still not working. I'm thinking the problem is something more than/other than the regular bootloop issue, but it is odd that only the 4 cores twrp will work.

Did you flash boot?

ItsMason said:
Did you flash boot?
Click to expand...
Click to collapse
In the most recent effort I flashed the entire n2g48c factory image but substituted the 4 cores boot image and 4 cores twrp recovery, then once I managed to get into twrp I installed the EX kernel from the thread listed above. Now, after that, it will bootloop once and then try to boot twrp which still crashes after showing the splash screen.

Dacull said:
In the most recent effort I flashed the entire n2g48c factory image but substituted the 4 cores boot image and 4 cores twrp recovery, then once I managed to get into twrp I installed the EX kernel from the thread listed above. Now, after that, it will bootloop once and then try to boot twrp which still crashes after showing the splash screen.
Click to expand...
Click to collapse
Try to fastboot FORMAT Boot, System and Userdata to see if they will format without errors. You may have a hardware issue (eg. bad eMMC). If so, the formatting process will not complete and give you a specific error code. If these 3 all complete, then flash a full image using flash-all.bat.

v12xke said:
Try to fastboot FORMAT Boot, System and Userdata to see if they will format without errors. You may have a hardware issue (eg. bad eMMC). If so, the formatting process will not complete and give you a specific error code. If these 3 all complete, then flash a full image using flash-all.bat.
Click to expand...
Click to collapse
This is what I got, I'm guessing the response on "boot" might be related to the problem?
Code:
[[email protected] angler-n2g48c]$ sudo fastboot format boot
[sudo] password for cullen:
Formatting is not supported for file system with type ''.
[[email protected] angler-n2g48c]$ sudo fastboot format system
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
Creating filesystem with parameters:
Size: 3221225472
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 12288
Label:
Blocks: 786432
Block groups: 24
Reserved block group size: 191
Created filesystem with 11/196608 inodes and 25785/786432 blocks
target reported max download size of 494927872 bytes
erasing 'system'...
OKAY [ 0.557s]
sending 'system' (52216 KB)...
OKAY [ 1.941s]
writing 'system'...
OKAY [ 0.732s]
finished. total time: 3.231s
[[email protected] angler-n2g48c]$ sudo fastboot format userdata
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
Creating filesystem with parameters:
Size: 58688266240
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14328190
Block groups: 438
Reserved block group size: 1024
Created filesystem with 11/3588096 inodes and 271280/14328190 blocks
target reported max download size of 494927872 bytes
erasing 'userdata'...
OKAY [ 0.640s]
sending 'userdata' (141002 KB)...
OKAY [ 5.181s]
writing 'userdata'...
OKAY [ 2.109s]
finished. total time: 7.930s

Dacull said:
This is what I got, I'm guessing the response on "boot" might be related to the problem?
Click to expand...
Click to collapse
Something is up with boot. Have you tried manually flashing just the Boot.img? Sorry I meant format System, Cache & Userdata. Did you then flash a full image with flash-all.bat? Was there any error on the Cache partition? If you still can't successfully enter Recovery, you could try to fastboot boot TWRP it rather than fastboot flashing. If you can access a stable Recovery you then have ADB and can sideload, etc.

v12xke said:
Something is up with boot. Have you tried manually flashing just the Boot.img? Sorry I meant format System, Cache & Userdata. Did you then flash a full image with flash-all.bat? Was there any error on the Cache partition? If you still can't successfully enter Recovery, you could try to fastboot boot TWRP it rather than fastboot flashing. If you can access a stable Recovery you then have ADB and can sideload, etc.
Click to expand...
Click to collapse
I cache formated ok. I have been flashing everything manually, including boot, since flash-all.sh ends on an error, but manually flashing seems to work fine.
Here's the output from flash-all.sh
Code:
[[email protected] angler-n2g48c]$ sudo ./flash-all.sh
target reported max download size of 494927872 bytes
sending 'bootloader' (3544 KB)...
OKAY [ 0.152s]
writing 'bootloader'...
OKAY [ 0.209s]
finished. total time: 0.361s
rebooting into bootloader...
OKAY [ 0.022s]
finished. total time: 0.072s
target reported max download size of 494927872 bytes
sending 'radio' (48728 KB)...
OKAY [ 1.862s]
writing 'radio'...
OKAY [ 2.164s]
finished. total time: 4.026s
rebooting into bootloader...
OKAY [ 0.022s]
finished. total time: 0.072s
target reported max download size of 494927872 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
W/ziparchive( 3437): Zip: unable to allocate 2860210996 bytes at offset 0 : No space left on device
failed to extract 'system.img': I/O Error
I was able to get a stable twrp using the 4 cores twrp and fastboot boot twrp, what would I want to sideload in this situation? The ota for the whatever version I just flashed?

Dacull said:
I cache formated ok. I have been flashing everything manually, including boot, since flash-all.sh ends on an error, but manually flashing seems to work fine.
I was able to get a stable twrp using the 4 cores twrp and fastboot boot twrp, what would I want to sideload in this situation? The ota for the whatever version I just flashed?
Click to expand...
Click to collapse
Have you updated fastboot/adb recently? I don't use the whole SDK, just the stand alone binaries. Some older versions weren't able to handle the multiple system packages.... but..... I/O error sounds like bad memory to me. The current versions were published 12-May-17. On the adb, I was just going to suggest flashing SU because it modifies boot and if it found something it wasn't expecting you may receive a better error message. Now sounding more like bad onboard memory. I don't think you have a valid system partition so maybe why it's not booting. Just a guess. Many ppl with BLOD have reported manually flashing completes with no error yet the OS won't boot.

Ok, I was running a slightly older version of fastboot, but I get the exact same results after switching to the latest binary, so it looks like the phones just toast. Huge thanks for all the help, even if it didnt end up working.

Oneplus 6T 8/256GB LineageOS problem

Hi Everyone!
I tried to install LineageOS to my OP based on the OP6T page at the LineageOS website (I cannot link as it's my first post). I did everything as it was written without errors and after the last reboot nothing happened, I got back my Oxygen OS with google. I thought I might screwed up something, so I started it over again. At step "Installing LineageOS from recovery / step 5" when they say "Return to the previous menu" I had two options as first time.
1: tapping back until I really get back
2: reboot
First time I chose the first one, so I thought I might reboot now instead. Then I got no TWRP again back. After many-many tries, currently I'm at a point where I can access fastboot. My plan is to get back the original Oxygen OS and try again installing LineageOS.
The problem I face with can see in the end of the post.
I used adb/fastboot downloaded from google and I downloaded the latest OTA software from oneplus itself. After booting the phone, I see the OP loading logo stuck. I can get into fastboot by holding down all buttons (to halt the phone) and then turning it off with holding POWER+VOL DOWN. Then I get into a blueish menu (not fastboot or twrp!) where I can reboot into recovery/fastboot or wipe data.
Note, that the images.zip is created by me by extracting the payload.bin from the OTA zip I downloaded from OP's site.
I also tried to install back TWRP by flashing it onto boot, but the phone got again into an andless loading screen.
Yes, I know we have a tool called MSM, but I have no windows available, only linux and macos. I tried wine and virtualbox running windows but MSM didn't recognize my phone.
Any idea what can I do?
Logs:
Code:
[email protected]:~/Downloads/ota/output$ ./fastboot update images.zip
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: e5a9f9c
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Setting current slot to 'a' OKAY [ 0.007s]
extracting boot.img (64 MB) to disk... took 0.187s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 2.032s]
Writing 'boot_a' OKAY [ 0.333s]
extracting dtbo.img (8 MB) to disk... took 0.051s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (8192 KB) OKAY [ 0.250s]
Writing 'dtbo' OKAY [ 0.052s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.003s]
Writing 'vbmeta' OKAY [ 0.001s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting system.img (2860 MB) to disk... took 12.379s
Invalid sparse file format at header magic
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/6 (513608 KB) OKAY [ 16.216s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 2/6 (514145 KB) OKAY [ 18.289s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 3/6 (515013 KB) OKAY [ 18.389s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 4/6 (515534 KB) OKAY [ 18.281s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 5/6 (510919 KB) OKAY [ 18.317s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 6/6 (184768 KB) OKAY [ 8.139s]
Writing 'system_a' OKAY [ 0.001s]
archive does not contain 'system_ext.img'
archive does not contain 'system_other.img'
extracting vendor.img (1024 MB) to disk... took 4.095s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
Sending sparse 'vendor' 1/2 (511135 KB) OKAY [ 16.211s]
Writing 'vendor' OKAY [ 0.001s]
Sending sparse 'vendor' 2/2 (389097 KB) OKAY [ 15.169s]
Writing 'vendor' OKAY [ 0.001s]
archive does not contain 'vendor_other.img'
Rebooting OKAY [ 10.729s]
Finished. Total time: 165.761s

mudlee said:
Hi Everyone!
I tried to install LineageOS to my OP based on the OP6T page at the LineageOS website (I cannot link as it's my first post). I did everything as it was written without errors and after the last reboot nothing happened, I got back my Oxygen OS with google. I thought I might screwed up something, so I started it over again. At step "Installing LineageOS from recovery / step 5" when they say "Return to the previous menu" I had two options as first time.
1: tapping back until I really get back
2: reboot
First time I chose the first one, so I thought I might reboot now instead. Then I got no TWRP again back. After many-many tries, currently I'm at a point where I can access fastboot. My plan is to get back the original Oxygen OS and try again installing LineageOS.
The problem I face with can see in the end of the post.
I used adb/fastboot downloaded from google and I downloaded the latest OTA software from oneplus itself. After booting the phone, I see the OP loading logo stuck. I can get into fastboot by holding down all buttons (to halt the phone) and then turning it off with holding POWER+VOL DOWN. Then I get into a blueish menu (not fastboot or twrp!) where I can reboot into recovery/fastboot or wipe data.
Note, that the images.zip is created by me by extracting the payload.bin from the OTA zip I downloaded from OP's site.
I also tried to install back TWRP by flashing it onto boot, but the phone got again into an andless loading screen.
Yes, I know we have a tool called MSM, but I have no windows available, only linux and macos. I tried wine and virtualbox running windows but MSM didn't recognize my phone.
Any idea what can I do?
Logs:
Click to expand...
Click to collapse
Can you Reboot to Fastboot? If so then load up TWRP via Fastboot Boot. Once in TWRP, flash OOS ZIP and TWRP Installer. Once that's done, Reboot to Recovery and Again flash OOS ZIP and TWRP Installer. Then Format Data by going to Wipe -> Format Data. Once that's done, Reboot to OOS and skip the Initial Setup. Transfer the LOS ROM and TWRP Installer as well as Gapps to Phone Storage and Reboot your phone to Recovery. Once there, go to Install and Flash LOS and TWRP Installer. Once that finishes, Reboot to TWRP and flash Gapps. After flashing Gapps, Format Data again and Reboot. Hopefully you boot into LOS. Also, if you are trying to install LOS 16, Use OOS 9.0.17 ZIP and if you're trying to Install LOS 17, Use OOS 10.3.0

thanks for your reply. I tried to load twrp into boot, but then it stuck at a screen where you can see with yellow color that the phone is unlocked and data integrity is not guaranteed.
I ran fastboot flash boot twrp.img then fastboot boot twrp.img, all went good, no errors, but then after the phone is rebooted, I see the screen above described and it stucks there.

mudlee said:
thanks for your reply. I tried to load twrp into boot, but then it stuck at a screen where you can see with yellow color that the phone is unlocked and data integrity is not guaranteed.
I ran fastboot flash boot twrp.img then fastboot boot twrp.img, all went good, no errors, but then after the phone is rebooted, I see the screen above described and it stucks there.
Click to expand...
Click to collapse
I'm afraid you'll have to MSM back to stock. That's the only way to recover your phone for sure.

DarthVader said:
I'm afraid you'll have to MSM back to stock. That's the only way to recover your phone for sure.
Click to expand...
Click to collapse
:-O I have to grab a windows pc then.

mudlee said:
:-O I have to grab a windows pc then.
Click to expand...
Click to collapse
Well before that, take a look at Fastboot ROMs. It's in the Guides Section. Instructions are in the First Post.

DarthVader said:
Well before that, take a look at Fastboot ROMs. It's in the Guides Section. Instructions are in the First Post.
Click to expand...
Click to collapse
Tried, the manual version as I was on linux. All images were sent to the device, got OKAY for everything, then the phone rebooted AND I HAVE STOCK ANDROID!
Thank you so much! Now I'm heading to install LineageOS

mudlee said:
Tried, the manual version as I was on linux. All images were sent to the device, got OKAY for everything, then the phone rebooted AND I HAVE STOCK ANDROID!
Thank you so much! Now I'm heading to install LineageOS
Click to expand...
Click to collapse
OK, so I tried to continue installing LineageOS with TWRP, but twrp does not load.
I ran
Code:
fastboot flash boot twrp.img
then rebooted the phone and twrp does not load, the phone just hangs at the screen with the yellow text saying the bootloader is unlocked. I can get back into stock by flashing the boot partition any time at least. I tried multiple twrp images.
What can be the problem with twrt?
Yellow screen is something like this (not my phone): https://forums-images.oneplus.net/attachments/1063/1063433-f5952bb27df62507293d3a3fd5496e11.jpg

mudlee said:
OK, so I tried to continue installing LineageOS with TWRP, but twrp does not load.
I ran then rebooted the phone and twrp does not load, the phone just hangs at the screen with the yellow text saying the bootloader is unlocked. I can get back into stock by flashing the boot partition any time at least. I tried multiple twrp images.
What can be the problem with twrt?
Yellow screen is something like this (not my phone): https://forums-images.oneplus.net/attachments/1063/1063433-f5952bb27df62507293d3a3fd5496e11.jpg
Click to expand...
Click to collapse
Sounds like a TWRP issue to me. Can you tell me what is your OOS version? And what version of TWRP are you using?

DarthVader said:
Sounds like a TWRP issue to me. Can you tell me what is your OOS version? And what version of TWRP are you using?
Click to expand...
Click to collapse
- As I said, I tried multiple twrp versions. Currently I'm trying out this one: https://eu.dl.twrp.me/fajita/twrp-3.3.1-1-fajita.img.html
- OOS: 10.3.0
- Android: 10
Maybe the problem is that I flashed last time too new OOS and that's why twrp does not work?

The answer is YES! I flashed an older OOS and I have now TWRP. I'll report back if I succeed.

mudlee said:
The answer is YES! I flashed an older OOS and I have now TWRP. I'll report back if I succeed.
Click to expand...
Click to collapse
Are you trying to install LOS 17 or 16?

DarthVader said:
Are you trying to install LOS 17 or 16?
Click to expand...
Click to collapse
I installed LOS 16 in the end, I might try the unofficial 17 as well, will see if I have time. I'm getting used to this flashing this and that here and there stuff
Thank you for your really valuable help!

eellogofusciouhipoppokunurious
Quote:
Originally Posted by OhioYJ
Appreciate it. This step maybe the key. I was using the TWRP installer, that maybe where I was going wrong. I'll have to give it another try.
(BASE STOCK ROM)
OnePlus6TOxygen_41_OTA_063_all_2001032024_215eea3f e7c64e37.zip (BETA4)
(CUSTOM ROM)
lineage-17.1-20200115_153235-UNOFFICIAL-fajita
(TWRP WITH SUCESSFULL DECRYPTION OF BASE STOCK ROM / CUSTOM ROM STORAGE)
twrp 3.3.1-30 zip
(Latest)
Magisk Canary . Zip
(Latest)
open_gapps - arm64-10.0-pico-20200116-BETA
(Latest)
RadioactiveKernel _ V10.2.0_CUSTOM_OnePlus6-6T
(Latest)
NanoDroid - 22.5.1.20200102
(&)
India_Fake_Partition_Deleter
------------------- EASY-CLEAN-INSTALL (LONG BUT BULLETPROOF) -------------------
!(BACK UP STORAGE/WILL LOSE DATA ETC.
ALL FILES ABOVE CAN BE SUBSTITUTED FOR ANY "IDEAL" ROM SETUP
CONFIGURATIONS YOU MAY PREFER., THESE ARE MY)!
------------------------------------------------------------------------------------------------
You only need any custom rom with the required BASE STOCK ROM and compatible TWRP version to decrypt storage, and of course, the latest magisk.
------------------------------------------------------------------------------------------------
fastboot boot twrp.img
Install twrp installer.
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
- - Reboot twrp - -
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
Reboot twrp
(DONT BE MOUNTING OR UNMOUNTING ANYTHING MANUALY ANYMORE!)
install OOS(BETA4).zip / TWRP installer
- - reboot recovery - -
install OOS(BETA4).zip / TWRP installer
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Format Data
Flash ROM
Flash TWRP installer
Reboot to recovery
Wipe Dalvik/ART Cache
Wipe Data
Flash Magisk.
Reboot system with your device unplugged to be safe (Device may reboot a couple times)
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Flash ROM
Flash TWRP installer
- - reboot to recovery - -
Flash Magisk
BOOT UP System
- - reboot back to recovery - -
Choose Reboot Option / (CHANGE YOUR SLOT) / Back / Reboot Recovery
Flash Magisk.
Reboot system
SETUP ROM
/////////////////////////////////////\OPTIONAL/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
- - REBOOT TO RECOVERY - -
----------------------------------------------------------------------------------------------------
STEP *( .=./ )*
Flash GAPPS
Flash India_Fake_Partition_Deleter
Flash NanoDroid (With prefered pre-configured setup/overlay/apps files placed)
Flash Custom Kernel
Re-Flash Magisk again
Click - WIPE DALVIK & Reboot system right after
------------------------------------------------------------------------------------------------------
- - REBOOT TO RECOVERY - -
Choose Reboot (CHANGE YOUR SLOT TO THE OPPOSITE SLOT)
- - REBOOT BACK TO RECOVERY - -
REPEAT STEP " *( .=./ )* "
-------------------------------------------------------------------------------------------------
GAME OVER
1up
THIS is EXTENSIVE but will work for any particular rom setup for a/b devices based on Q
Last edited by Johndoesmoked; 18th January 2020 at 07:13 AM. Reason: i dont know
Michelsup
19th January 2020, 08:55 AM |#743
Member91 posts Thanks: 133
Quote:
Originally Posted by OhioYJ
You were able to install TWRP? A lot of us cant install TWRP anymore, only boot it. If this has changed it would be nice to have a recovery
There was a bug on the first 17.1. With the last builds you can update like you always did; lineage.zip, twrp.zip, reboot to twrp, gapps.zip, magisk.zip, reboot and profit.
Of course you obviously had to update /vendor, as stated on Luk's post.