Just Installed CM13, Now TWRP Shows Internal Storage as 0MB - Nexus 6P Q&A, Help & Troubleshooting

The title pretty much explains it. I just finished installing CM13 on my Nexus 6P, but realised I'd downloaded the wrong GApps, so booted up into CM13 (Worked fine) and then downloaded the newest GApps into internal storage (Which was NOT empty when I connected over USB to my PC) yet when I went to flash the new GApps, TWRP tells me that I have nothing in my internal storage folder. I'm confused as to how that could happen.

It could be that it messed with the internal formatting, try downloading the stock image from Google. Extract all the files until you get to userdata.img.
Open a command prompt in the folder and you can flash it whilst your phone is connected and in fastboot by typing "fastboot flash userdata userdata.img"
this will wipe (factory reset) your device!

nukeclears said:
It could be that it messed with the internal formatting, try downloading the stock image from Google. Extract all the files until you get to userdata.img.
Open a command prompt in the folder and you can flash it whilst your phone is connected and in fastboot by typing "fastboot flash userdata userdata.img"
this will wipe (factory reset) your device!
Click to expand...
Click to collapse
Tried this, no success. I'm willing to just get the phone back to stock at this point, so I assume just reflashing the stock imgs will do the trick, to at least get me a working phone? I have a nandroid backup that I can use, but tonight I just want to get a working phone.

Userdata.img is only for the 32gb version. If you flash that over 64gb or 128 it will give you 32. Try fastboot format userdata instead.

Related

Erase all content and settings on custom rom

Hi im confused on how to erase everything on my phone. I was on paranoid android rom and wanted to try out cyanogen. i wanted to erase everything first because i was running low on storage unfortunately. So i backed up pictures and sms to my PC. I try to erase all through my custom recovery (clockwork) with no success then i go to settings and erase all content and settings and the files are still there. I tried this about 4 times with no luck. What am i doing wrong?
Edit: I might be in bigger trouble. I formated everything under clockwork settings and rebooted and I am stuck at the google logo. I can go back to recovery though. I cant sideload any roms though to start up
When you are just trying to clear all apps and data for the ROM you are using, go to recovery and just wipe /data and that should be it. This leaves the /system alone so your ROM is still there when you boot. May have to flash gapps again though.
Sent from my Nexus 4 using Tapatalk 4 Beta
BugJuice said:
Hi im confused on how to erase everything on my phone. I was on paranoid android rom and wanted to try out cyanogen. i wanted to erase everything first because i was running low on storage unfortunately. So i backed up pictures and sms to my PC. I try to erase all through my custom recovery (clockwork) with no success then i go to settings and erase all content and settings and the files are still there. I tried this about 4 times with no luck. What am i doing wrong?
Edit: I might be in bigger trouble. I formated everything under clockwork settings and rebooted and I am stuck at the google logo. I can go back to recovery though. I cant sideload any roms though to start up
Click to expand...
Click to collapse
You cant choose the sideload option under the recovery menu? Just do that then connect to a computer and type adb sideload /home/user/romofyourchoice.zip in Linux terminal or windows command prompt. That saved my ass a few times. If he can't do that go into your bootloader download a complete image of stock then use the fastboot command and reflash every partition one by one then once that boots up you can continue from there.
Nexus 4 CyanogenMod 10.1.0
ryaniskira said:
You cant choose the sideload option under the recovery menu? Just do that then connect to a computer and type adb sideload /home/user/romofyourchoice.zip in Linux terminal or windows command prompt.
Nexus 4 CyanogenMod 10.1.0
Click to expand...
Click to collapse
I dumped the rom in the sideload folder and typed adb sideload romname.zip and it says adb devices not found.
BugJuice said:
I dumped the rom in the sideload folder and typed adb sideload romname.zip and it says adb devices not found.
Click to expand...
Click to collapse
I modified my previous post refer to it hopefully you can still do the fastboot flash command. You should be able to find a stock image somewhere unzip the zip file and flash the images with the fastboot flash command (example fastboot flash recovery recoveryfilename.img) just make sure you flash the img files to the right partitions
Nexus 4 CyanogenMod 10.1.0
BugJuice said:
Hi im confused on how to erase everything on my phone. I was on paranoid android rom and wanted to try out cyanogen. i wanted to erase everything first because i was running low on storage unfortunately. So i backed up pictures and sms to my PC. I try to erase all through my custom recovery (clockwork) with no success then i go to settings and erase all content and settings and the files are still there. I tried this about 4 times with no luck. What am i doing wrong?
Edit: I might be in bigger trouble. I formated everything under clockwork settings and rebooted and I am stuck at the google logo. I can go back to recovery though. I cant sideload any roms though to start up
Click to expand...
Click to collapse
What you did in clockwordmod was erase the contents of system, data, cache, and Dalvik cache. If you already have downloaded and copied the ROM you want to the "sdcard", all you need to do is boot into recovery again, select Install, select the zip file that contains the new ROM, and press the power button to install the ROM.
If you have the ROM downloaded but have not copied it to the phone, move the ROM file to the folder on your computer where you installed adb and fastboot. Boot your phone into recovery and select Mounts and Storage then connect the USB cable from the computer to the phone. Confirm that phone shows "Unmount /sdcard/" and "Unmount /system/" or press toggle button to change status as necessary. Open a command prompt on your computer by clicking Start -> Run, typing cmd, and pressing <ENTER>. At the command prompt type cd C:/Android/ replacing "/Android/" with the path name to the folder where adb is installed and press <ENTER>. At the command prompt type adb push ROM.zip /sdcard/ROM.zip replacing "ROM.zip" with the actual filename of the ROM you downloaded and moved to this folder. Now disconnect your phone from the computer and close the command prompt. From the clockwordmod main screen select Factory Reset, then Wipe Cache Partition, and Wipe Dalvik Cache then repeat full wipe twice. Finally, from the clockwordmod main screen select Install ZIP from SD Card followed by Choose file from SD Card, select the ROM.zip file you pushed to the phone's sdcard, and.press the power button to install the ROM.
When clockworkmod reports "Install from SD Card Complete.", return to the main screen and select Reboot system now. The first boot following a fresh installation of a new ROM can take several minutes, just be patient while the ROM initializes the system, applies customizations or updates, and boots to the phone's setup screen.

I think I am bricked

So at one point, I accidentally deleted the OS off of my phone, but I still had TWRP installed. The only solution was to flash a rom through ADB, but TWRP didn't have ADB for whatever reason for me, so I flashed CWM which did have ADB. I was able to flash CWM after I pushed a rom through ADB and install Android 4.3 w/ root from nexus4root.com. It worked correctly, but I noticed that I only had 5.66gb of storage on my phone. I have the 16gb variant which would have about 12gb usable. So I followed a guide here in xda to get back my 16gb. I was told to wipe my phone step by step and flash a factory image. But ere are my errors not
- When I try to flash the factory image, it says 'missing boot.sig, system.sig, and something else.sig'
- I have no recovery on my phone
- When I try using fastboot commands, it says FAILED (command write failed (unknown error))
I am pretty stuck here. And I did redownload the root files.
EDIT: I was able to fix fastboot and flashed TWRP, but my devices is encrypted and requires a password
You should be able to clean your encrypted user storage by using "fastboot erase userdata", and you can do it for /data /system and /cache partition as well.
Or go into TWRP, if it ask for password, just press cancel. Then go to Wipe -> Advance -> Select "Format Data" and it will do a full wipe and cleaning out the encrypted partition.
As for using fastboot to restore to stock, shouldn't be any problem as long as you have the correct drivers and latest ADT package from Google.
I did something similar and had encryption on. My fix was "fastboot flash" the stock system, boot and recovery (4.3 for me). After getting back in my phone and verifying everything was there I re-flash CWM and re-rooted.

Help help help with a hard bricked 6P

Hello guys,
I had my phone rooted with latest twrp. I flashed stock+ rom with Franco Kernel 25r and the A.R.I.S.E file for better sound. I've done the same set up minus the ARISE file and never had an issue.
well to my luck it kept bootlooping and I wasn't able to get back into my custom recovery. When I got home and got my hands on a pc I did a factory reset by manually flashing stock google img . I even used a couple tools since I ran out of ideas and still no luck.
I'm able to do anything through fastboot but I can't seem to get into my recovery at all.
Any ideas or tips of where I should go next?
Not a Hardbrick
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
leninmon said:
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
Click to expand...
Click to collapse
First of all thank you for the response.
I've tried flashing the most current twrp and it seems to go through fine on fast boot but when I actually try to get into recovery from the device it will boot loop and just keep doing that.
How can I get into the phones storage through fastboot?
Where can I get the factory zip?
it feels as if everything seems to go good through fastboot but when I actually try to boot the phone nothing seems to work.
Wiltron said:
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
Click to expand...
Click to collapse
Thanks for the reply.
I've done the manual flashing already and flashed everything single item the most current factory image. Everything seemed to have gone through okay but when I rebooted the phone it was back to 0.
I'm actually considering getting rid of the phone now since it is my daily =/
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
leninmon said:
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
Click to expand...
Click to collapse
I flashed the twrp.img and it went through successfully at least on the computer it did but when the phone actually tries to get into recovery (twrp) it will start to boot loop and keep on doing that. I tried both an encrypted and decrypted boot img but it still made no difference.
I'm really going crazy over this
Wiltron said:
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Click to expand...
Click to collapse
I just tried this and had no luck =/....the phone wont get past the google boot screen
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
leninmon said:
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
Click to expand...
Click to collapse
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
edgarted said:
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
Click to expand...
Click to collapse
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
i42o said:
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Click to expand...
Click to collapse
I was really really hoping this would help. I erase/formated everything before flashing anything. I then ran the flash-all file and it took a couple of minutes and it said finished on the command box and my phone restarted and went into the white google logo and rebooted again with a bootloop. I waited around 15 minutes hoping it would start but it didn't.
It honestly feels as if the phone is not processing the full commands but on the pc it seems to go through successfully
is there a way to force an install of a rom and see if maybe a dirty flash over the stock one will allow it to start up?
leninmon said:
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
Click to expand...
Click to collapse
i know how to flash the radio and bootloader but how do i do a fastboot update?
edgarted said:
i know how to flash the radio and bootloader but how do i do a fastboot update?
Click to expand...
Click to collapse
Just unzip the factory image and there U can see the flash shell script files too. Open them in a text editor & U could see the exact command. In a factory img, they also do the same thing via script files. Flashing the radio & bootloader & updating the rest archive
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
edgarted said:
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
Click to expand...
Click to collapse
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
blitzkriegger said:
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
Click to expand...
Click to collapse
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
edgarted said:
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Click to expand...
Click to collapse
This is weird. What version of the stock factory images did you flash? I've been using leviticus 1.3 since it came out and when i was still on stock rom. I switched over to cm builds and have been flashing every nightly since the 7/24th build, and in the process repeatesly reflashing the aound mod along, and i've had zero issues with the phone booting afterwards.

Looking for thorough flashing guide

Hi,
Does a thorough guide exist on how to flash custom ROM on this phone?
I have done quite a lot of flashing in my life but can't a ROM flashed for the love of God.
Got TWRP installed, ADB works, cables are good.
Thanks!
After quite some hours I finally managed to get Havoc Pie running (GSI ARM64 AB, downloaded here).
My first problem was the fact that you need to be on stock Oreo before starting, this took me a while to figure out.
I used the most recent 'back to stock' Oreo from this page.
After installing this, I booted up, and went straight for enabling USB-debugging in Developer options.
Then do ADB REBOOT BOOTLOADER to enter fastboot mode.
There I erased system on both A and B partitions by using FASTBOOT ERASE SYSTEM command, then FASTBOOT SET_ACTIVE OTHER to switch to the other partition, and then once more FASTBOOT ERASE SYSTEM to also erase the system on this partition.
After that I ran FASTBOOT FLASH SYSTEM Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img, on the one partition, then FASTBOOT SET_ACTIVE OTHER and after that FASTBOOT FLASH SYSTEM Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img to flash it on the other partition.
After that I installed TWRP by running FASTBOOT FLASH BOOT twrp-3.2.3-0-mata.img (downloadable here).
After that, I rebooted into TWRP recovery by running ADB REBOOT RECOVERY.
There, I put twrp-installer-mata-3.2.3-0.zip (downloadable at the previously mentioned TWRP website) on internal memory and flashed it.
This automatically flashes both A and B partitions (switching between A and B at the reboot screen).
After doing that, I wiped /DATA on both A and B.
Then I put the Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img on internal memory and flashed it on /SYSTEM for both A and B.
Then it is time for GAPPS.
As I prefer Stock GAPPS with my own GAPPS-CONFIG.TXT, I ran into the Error 70: because of the large size of Havoc, there is not enough room for large GAPPS.
So because of that I needed to do the Resize /SYSTEM partition for both A and B (in the Advanced wipe menu section).
After that I was able to flash my Stock GAPPS on both A and B.
Now I need some rest to regain my sanity before I tackle rooting the ROM.
I probably did too much double stuff, but it is not easy to know when only A or B needs to be done.
Comments and tips are welcome.
Waancho said:
After quite some hours I finally managed to get Havoc Pie running (GSI ARM64 AB, downloaded here).
My first problem was the fact that you need to be on stock Oreo before starting, this took me a while to figure out.
I used the most recent 'back to stock' Oreo from this page.
After installing this, I booted up, and went straight for enabling USB-debugging in Developer options.
Then do ADB REBOOT BOOTLOADER to enter fastboot mode.
There I erased system on both A and B partitions by using FASTBOOT ERASE SYSTEM command, then FASTBOOT SET_ACTIVE OTHER to switch to the other partition, and then once more FASTBOOT ERASE SYSTEM to also erase the system on this partition.
After that I ran FASTBOOT FLASH SYSTEM Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img, on the one partition, then FASTBOOT SET_ACTIVE OTHER and after that FASTBOOT FLASH SYSTEM Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img to flash it on the other partition.
After that I installed TWRP by running FASTBOOT FLASH BOOT twrp-3.2.3-0-mata.img (downloadable here).
After that, I rebooted into TWRP recovery by running ADB REBOOT RECOVERY.
There, I put twrp-installer-mata-3.2.3-0.zip (downloadable at the previously mentioned TWRP website) on internal memory and flashed it.
This automatically flashes both A and B partitions (switching between A and B at the reboot screen).
After doing that, I wiped /DATA on both A and B.
Then I put the Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img on internal memory and flashed it on /SYSTEM for both A and B.
Then it is time for GAPPS.
As I prefer Stock GAPPS with my own GAPPS-CONFIG.TXT, I ran into the Error 70: because of the large size of Havoc, there is not enough room for large GAPPS.
So because of that I needed to do the Resize /SYSTEM partition for both A and B (in the Advanced wipe menu section).
After that I was able to flash my Stock GAPPS on both A and B.
Now I need some rest to regain my sanity before I tackle rooting the ROM.
I probably did too much double stuff, but it is not easy to know when only A or B needs to be done.
Comments and tips are welcome.
Click to expand...
Click to collapse
Wow, here's all i did :
Flashing ProjectTreble GSIs on the Essential using TWRP
1) either boot or fastboot into TWRP
2) Wipe Cache, System, and Data (1 GSI required internal to be wiped, i forget which)
3) From Main Menu, select Install and Flash UN-ZIPPED A/B system.img
4) Reboot Recovery (It's going to say there's no OS, act like you didnt see it.)
5) Reboot System and Enjoy!
6) Most of the later GSIs from October to Present I have flashed and am happy to say
they all contain pre-installed Magisk and ALL but 1 contains Gapps.
AndroidDevices said:
Wow, here's all i did :
Flashing ProjectTreble GSIs on the Essential using TWRP
1) either boot or fastboot into TWRP
2) Wipe Cache, System, and Data (1 GSI required internal to be wiped, i forget which)
3) From Main Menu, select Install and Flash UN-ZIPPED A/B system.img
4) Reboot Recovery (It's going to say there's no OS, act like you didnt see it.)
5) Reboot System and Enjoy!
6) Most of the later GSIs from October to Present I have flashed and am happy to say
they all contain pre-installed Magisk and ALL but 1 contains Gapps.
Click to expand...
Click to collapse
Thanks!
Next time i will try your method.
For some reason, if i did anything different, the phone would just keep rebooting into recovery.
And of course, the ROM that i chose (Havoc) did not have Magisk pre-installed.
I am now back to stock and liking it, which says a lot about the PH-1 software!
Waancho said:
Thanks!
Next time i will try your method.
For some reason, if i did anything different, the phone would just keep rebooting into recovery.
And of course, the ROM that i chose (Havoc) did not have Magisk pre-installed.
I am now back to stock and liking it, which says a lot about the PH-1 software!
Click to expand...
Click to collapse
It does have Magisk installed, it should if its one of the newer builds and all you need to do is install Magisk Manager which in turn activates Magisk
Installing Magisk manager was one of the first things I did, but unfortunately, the latest version A/B Havoc at the aforementioned link did not have Magisk.
There's about 6 or 7 and probably a bunch of YouTube's
Sent from my PH-1 using XDA Labs

Stuck in a jam

So I screwed up. When wiping my system for lineageos, I accidentally wiped everything, including the system, internal storage, and data. I am in TWRP right now. Trying to send files over at MTP just makes the progress bar not move. I cannot move it over with my phone mounted as a usb storage device. When using adb push to send over a ROM, the command completes, but it does not appear in the sdcard folder as I specified. Adb sideload just stops at 50%, with the phone displaying step 2/2 and not continuing after that- I have the option to reboot or wipe dalvik / cache. I have no OS. I know that rebooting into TWRP again will make MTP work, however as I have no OS installed I know that I will not be able to access fastboot. Any ideas on how to get a rom onto my phone's storage?
You might need to format your internal storage as it may still be encrypted which may be why files aren't copying across. This is just a guess though. If all else fails (I have been in a similar situation before), you should be able to boot into fastboot (bootloader) mode from TWRP and flash OOS back through that. You would need to find the fastboot version of the ROM. I believe there is a thread in this forum somewhere. A last resort would be using the MSMTool to get back to stock. I've never had to do this myself though. The phone will be in a like brand new state though, so you would need to unlock the bootloader again if you are going to flash a custom ROM or do any modding after.
You can use OTG storage, encryption has no effect on it and you can flash files too. I used it to bypass the encryption issue in TWRP. If that doesn't work then post #2 is your best option. Also you can still boot in fastboot even if your ROM is broken. You can find the fastboot ROMs in the guide section.

Categories

Resources