Alright, so here's what happened.
Finally updated hardware and went from a nexus 6p to a pixel xl.
It's running 8.0.
So I decided it was time to get the phone up to the same customization that I had on my 6p.
One of my first things, after rooting of course, was adding qemu.hw.mainkeys=1 to build.prop in order to get rid of the soft keys. Same exact thing I've done on literally all of my android phones ever.
Rebooted.
I now get this sweet messaging saying "Can't load Android system..." (See Picture) and so on. Suggesting Try again and Factory data reset.
So I'm like whatever, I can just pull build.prop to my computer. So I find some guides on how to do that and boot to the bootloader.
But then adb devices shows:
"List of devices attached"
And then nothing. So adb can't find my phone.
Here's what I tried in trouble shooting.
Disconect Cable
adb kill-server
adb start-server
Plug back in.
Still nothing.
I even tried a different USB port.
So now I'm like "Okay, I'll take the bullet and factory reset."
So I did.
After setup, I get about 30 seconds (without softkeys) of phone time before my the System UI crashes and the phone shuts off.
Upon reboot, I'm faced with the same "Can't load Android system screen..." (See picture again if you want) and we're back to square one.
So...
Can't adb pull on build.prop because adb can't find my phone.
Can't boot into the regular system and edit build.prop from there because the phone isn't rooted (cause the only way to boot into the system is to factory reset).
Can't root the phone because adb can't find my phone.
And lastly, can't flash factory images because adb can't find my phone.
That's all the trouble shooting I've tried. If anyone can help me out here, I would be super grateful, cause right now, I have a really expensive paperweight.
Thanks in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hello, try flashing through fastboot following this post:
https://forum.xda-developers.com/showpost.php?p=70041042&postcount=3
here if you want to unlock the bootloader:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Yup. That worked. Thank you!
Any idea why adding qemu.hw.mainkeys=1 to build.prop killed my rom?
burt1215 said:
Any idea why adding qemu.hw.mainkeys=1 to build.prop killed my rom?
Click to expand...
Click to collapse
Because the UI has to have nav keys, unless your Pixel has hardware keys, you'll probably have to keep the softkeys.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Because the UI has to have nav keys, unless your Pixel gas hardware keys, you'll probably have to keep the softkeys.
Click to expand...
Click to collapse
I've hidden the softkeys on my Nexus 4, Nexus 5, and Nexus 6P. And on every operating system since ICS.
What's different now? Is it the Pixel XL or Oreo?
burt1215 said:
I've hidden the softkeys on my Nexus 4, Nexus 5, and Nexus 6P. And on every operating system since ICS.
What's different now? Is it the Pixel XL or Oreo?
Click to expand...
Click to collapse
To be honest, I've never heard of it being an issue either, I was just speculating, however unlikely it may be.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
To be honest, I've never heard of it being an issue either, I was just speculating, however unlikely it may be.
Click to expand...
Click to collapse
Ha. No worries.
After fixing my phone, I decided to edit build.prop again, cause it's not stupidity unless you try the same thing multiple times while expecting different results right?
Anyway, same exact thing happened.
This time I fixed it without wiping my phone, but it leads me to believe that build.prop can't be edited... but I'm still not sure why.
burt1215 said:
Ha. No worries.
After fixing my phone, I decided to edit build.prop again, cause it's not stupidity unless you try the same thing multiple times while expecting different results right?
Anyway, same exact thing happened.
This time I fixed it without wiping my phone, but it leads me to believe that build.prop can't be edited... but I'm still not sure why.
Click to expand...
Click to collapse
Are you booting to recovery and wiping cache and dalvik/ART cache(obviously not factory reset or wipe data, just the caches)? It's usually required when modifying system files.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Are you booting to recovery and wiping cache and dalvik/ART cache(obviously not factory reset or wipe data, just the caches)? It's usually required when modifying system files.
Click to expand...
Click to collapse
I edited build.prop and rebooted the system.
Got the same error as the picture in the original post.
Booted into TWRP and pulled build.prop onto my computer.
Edited the file, pushed it back in and rebooted into the system without any errors.
burt1215 said:
I edited build.prop and rebooted the system.
Got the same error as the picture in the original post.
Booted into TWRP and pulled build.prop onto my computer.
Edited the file, pushed it back in and rebooted into the system without any errors.
Click to expand...
Click to collapse
Strange, at least it works.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Related
I noticed people complain about errors on a brand new flash of a ROM, errors that I never had, or any other use never had. On occasion, flashing data will leave settings/apps intact and actually not do anything at all..so to follow a complete fail proof guide on ensuring a brand new flash...do the following.
1. Wipe data TWICE (2x) one after the other.
2. Flash the ROM. (ONCE)
3. Wipe cache partition. (2x)
4. Wipe dalvik cache. (2x)
5. Fix Permissions. (2x)
REBOOT.
Leave your phone idle IMMEDIATELY after booting for 10 minutes so the phone's background services and first-time use settings can process themselves. Doing this will provide you the most stable flash, and any force closes / crashes more than likely will be the ROM's fault if you followed all steps to the "T.".
This may not be well known to everyone. Whatever. If you don't find it useful, don't comment. If you do, comment. If you need help or have any questions, post them and I will be sure to answer you as quick as possible.
I've always wondered, what's the point of doing wipe twice?
djh said:
I've always wondered, what's the point of doing wipe twice?
Click to expand...
Click to collapse
On occasions (and this is ALSO true with the SGH-t989)
The ROM won't be completely wiped. It will incorporate the old data with your new ROM and cause force closes, or black screens, slower, lower battery life, etc.
By doing this twice, you ensure yourself the platform is ENTIRELY clean and ready for a new version of the ROM.
For example, I once flashed GOV2, over GenericGinger and STILL HAD a green theme. That's how I knew something was wrong. From there on then, I ALWAYS ALWAYS ALWAYS like a religion, wiped twice. There's no reason NOT to do it. It takes very little time, and is added insurance to a fully functional and stable ROM.
Edit : If no one likes the method, by all means do things your own way ; whatever works for you works ; however I do things judging on the fact from experience of using/doing them.
TheLastSidekick said:
On occasions (and this is ALSO true with the SGH-t989)
The ROM won't be completely wiped. It will incorporate the old data with your new ROM and cause force closes, or black screens, slower, lower battery life, etc.
By doing this twice, you ensure yourself the platform is ENTIRELY clean and ready for a new version of the ROM.
For example, I once flashed GOV2, over GenericGinger and STILL HAD a green theme. That's how I knew something was wrong. From there on then, I ALWAYS ALWAYS ALWAYS like a religion, wiped twice. There's no reason NOT to do it. It takes very little time, and is added insurance to a fully functional and stable ROM.
Edit : If no one likes the method, by all means do things your own way ; whatever works for you works ; however I do things judging on the fact from experience of using/doing them.
Click to expand...
Click to collapse
All that fixing permissions will do is make a apk readable and writable, I believe it isn't necessary after 2 wipes.
insanedrunk said:
All that fixing permissions will do is make a apk readable and writable, I believe it isn't necessary after 2 wipes.
Click to expand...
Click to collapse
I may have been dramatic with the fix permissions bit, but it is what I've been doing since I started picking up the GenericGinger project and it hadn't failed me once. I do however recommend doing everything else (mostly the data format) TWICE.
djh said:
I've always wondered, what's the point of doing wipe twice?
Click to expand...
Click to collapse
It's really silly.
It is a problem with some developers cwm updater-scripts. Rather then formating partitions, they just rm -rf the data on the partition. Then they unmount the filesystem without syncing first.
If you don't sync before unmounting, the deletions might not happen.
So, the effect that some users see by wiping twice is that when the filesystem mounts again, the deletions that happened before get "fsync()"ed by the filesystem driver and it appears that formating twice does the right thing.
So developers are causing the problem without understanding the problem.
bhundven said:
It's really silly.
If you don't sync before unmounting, the deletions might not happen.
Click to expand...
Click to collapse
That sure make sense. Thanks for explaining
So you mean the entire time every time I had this problem, it was due to that damn script? This thing happens on like every ROM Lol...
I can take a crack at adding fsync...but should I add it after RM -rf or change it altogether? What do you recommend?
Sent from my SGH-T989 using xda app-developers app
Probably a little too simple, but is this right bhundven?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bhundven said:
It is a problem with some developers cwm updater-scripts. Rather then formating partitions, they just rm -rf the data on the partition. Then they unmount the filesystem without syncing first.
Click to expand...
Click to collapse
This thread saved my bacon -- I was contemplating messing about with Odin/Heimdall to try and format partitions manually after 'adb restore' command filled up my internal storage on a Samsung Galaxy S4 Mini with ~3GB of unreachable mess. The CWM factory reset option didn't clear it, but executing 'factory reset' and also 'format /data and /data/media (/sdcard)' from the Mounts and Storage Menu twice did the trick. Not entirely certain if it was a missing sync issue or just a matter of specifically selecting 'format /data and /data/media (/sdcard)', but this thread led me to a much safer solution than bootloader tools!
Is this method guarantee a security delete, which means that impossible to recover data by any recovery software?
Hi, I am currently using unlocked Sprint Note 5 on another carrier. I have messed up some settings and need the carrier partition from a Sprint Activated Note 5. This can be pulled of easily from a rooted Note 5 and doesn't contains any personal information.
-- On a rooted Note 5 N920P, run adb shell as ROOT (su)
---use following command to pull Carrier partition to sdcard
--- dd if=/dev/block/platform/15570000.ufs/by-name/carrier of=/sdcard/sprint_note5_Carrier.img
Zip and share on any file hosting website.
Any help will be appreciated. Thanks in advance.
Bump.... anyone..pls help...
Sent from my SM-N920P using Tapatalk
adb shell says no such file or directory. I cant remember if that filepath is correct, I'll look around.
Edit:
The path looks like it is correct.
---------- Post added at 11:08 AM ---------- Previous post was at 10:52 AM ----------
full command:
Code:
adb shell
su
dd if=/dev/block/sda18 of=/sdcard/sprint_note5_Carrier.img
It looks like the byname doesn't work so I used the above command instead, addressing the cache partition directly.
I'll send it to you privately via PM when it gets done uploading.
Thanks a lot for your help.
Thanks a lot @tdunham.
Some how after marshmallow byname is not working. Addressing the partition directly works, however the carrier partition is on sda18. sda17 is Cache.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bigbyte.me said:
Thanks a lot @tdunham.
Some how after marshmallow byname is not working. Addressing the partition directly works, however the carrier partition is on sda18. sda17 is Cache.
Click to expand...
Click to collapse
Crap, sorry about that, resending.
FYI, su must precede the command for pull otherwise I get access denied or something.
tdunham said:
Crap, sorry about that, resending.
FYI, su must precede the command for pull otherwise I get access denied or something.
Click to expand...
Click to collapse
Thanks again. And yes you are right. dd clone has to be done as SU.
bigbyte.me said:
Thanks again. And yes you are right. dd clone has to be done as SU.
Click to expand...
Click to collapse
No problem, hope it works. I edited the post above for the corrected partition info and wrapped it in case someone runs across this later for reference.
tdunham said:
No problem, hope it works. I edited the post above for the corrected partition info and wrapped it in case someone runs across this later for reference.
Click to expand...
Click to collapse
Thanks. Got the correct file. Will update thread once I put it in my Note 5.
Just out of curiosity, what is your issue?
I ask for a specific purpose.
I know we and the Galaxy S6 are experiencing soft bricks on MM.
The symptom is phone just keeps rebooting over and over. A full wipe and odin flash of stock does not resolve this and the only workaround so far has been to allow the phone battery to fully die. I was thinking a specific partion is being problematic and a simple solution hasn't presented itself yet.
@tdunham
My issue is not related to MM bug. Actually if you flash the MM odin it flashes a dafault carrier partition also and it takes away all the carrier customizatins and hot spot / roaming settings are absent. You can get those back if you do a pofile update with sprint, which is not possible for non sprint users.
Sent from my SM-N920P using Tapatalk
tdunham said:
Just out of curiosity, what is your issue?
I ask for a specific purpose.
I know we and the Galaxy S6 are experiencing soft bricks on MM.
The symptom is phone just keeps rebooting over and over. A full wipe and odin flash of stock does not resolve this and the only workaround so far has been to allow the phone battery to fully die. I was thinking a specific partion is being problematic and a simple solution hasn't presented itself yet.
Click to expand...
Click to collapse
Would you be able and willing to shoot me a copy of that partition as well. My wife's note 5 recently messed up and is missing all carrier info and the dial code to pull it OTA isn't responding. Its causing that repeated activation error and not registering on any network and its unlocked too.
First of all, thank you for reading my post.
I'll try to point out what is going on right now iwith the phone (never saw it happen, ever).
Phone boots but shows a blank (black screen with faded light in the corners) after booting.
After several tries, found out that the 4G is on and receiving notifications (LED is blinking waiting for my response ) and I'm receiving calls nonetheless, so it is working but I can't use the screen.
The screen IS FINE, the boot shows up properly, the fastboot menu shows up properly, sometimes the icons and widgets shows up where they should be, the "Shut down" button shows up properly.
What seems to be the issue is that the upper tray with the time, data, and other things, and the down one with the "◁ ⭘ ▢" menu doesn't shows up AT ALL, so I just receive a blank screen.
Also, the computer isn't finding the phone even if it is connected through the USB cable.
I'm acessing the "Whatsapp" app in the computer right now, which requires the phone to be online and with a internet connection, meaning that the apps are functional and something really weird is happening.
The phone was working fine until last afternoon, just blanked moments after I got out of my house (when I first noticed the issue).
So... anyone willing to crack heads with me trying to figure out what the hell is happening here?
I'll provide pictures soon.
Thanks in advance!
:highfive:
EDIT1: seems to show this "Unfortunately System UI has Stopped" from time to time.
EDIT2: https://youtu.be/AS-wv0NB-g4 (recorded the issue) the 58s shows what i'm talking about.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Most likely a firmware issue
xtragen said:
First of all, thank you for reading my post.
I'll try to point out what is going on right now iwith the phone (never saw it happen, ever).
Phone boots but shows a blank (black screen with faded light in the corners) after booting.
After several tries, found out that the 4G is on and receiving notifications (LED is blinking waiting for my response ) and I'm receiving calls nonetheless, so it is working but I can't use the screen.
The screen IS FINE, the boot shows up properly, the fastboot menu shows up properly, sometimes the icons and widgets shows up where they should be, the "Shut down" button shows up properly.
...
Also, the computer isn't finding the phone even if it is connected through the USB cable.
...
EDIT1: seems to show this "Unfortunately System UI has Stopped" from time to time.
EDIT2: https://youtu.be/AS-wv0NB-g4 (recorded the issue) the 58s shows what i'm talking about.
Click to expand...
Click to collapse
Most likely a firmware issue - may be a corruption has developed or could be an incompatible app update (Google Play Services or your launcher?) . Are you rooted? You haven't indicated what ROM you have installed (Stock, custom ...?). Is the recovery stock or custom? Can you enter recovery? Does everything look as it should in recovery? If custom, do you have a recent backup and have you tried running it? The 1045 is the US version I believe - are you sure it's not a 1040 (Canada/Brazil)?
Your best bet may be to install/flash another ROM, either stock or custom. Check out lost101's or vpnair's threads for stock firmware for your phone - they've done an excellent service by providing these ROMS and they are great. I've used both at different times to overcome some issues - may be the best way to go at this stage.
Good luck --- S.
Something caused and error in your firmware, you have to do the following:
1.- Try to backup your files. See if you can connect it to the PC and explore the files from there.
2.- Once backup is done, you have 2 ways:
A) Unlock bootloader, then flashing TWRP recovery, then installing a custom ROM like CyanogenMOD or AOSP.
B) Search and download the stock firmware file, extract the files, and then flashing it to your phone using mfastboot excecutable.
You can find the files and the info here in XDA thread, just do it carefully and read instructions.
If you can't find something say it and I can help, but won't spoonfeed you.
Good luck.
sdembiske said:
Most likely a firmware issue - may be a corruption has developed or could be an incompatible app update (Google Play Services or your launcher?) . Are you rooted? You haven't indicated what ROM you have installed (Stock, custom ...?). Is the recovery stock or custom? Can you enter recovery? Does everything look as it should in recovery? If custom, do you have a recent backup and have you tried running it? The 1045 is the US version I believe - are you sure it's not a 1040 (Canada/Brazil)?
Your best bet may be to install/flash another ROM, either stock or custom. Check out lost101's or vpnair's threads for stock firmware for your phone - they've done an excellent service by providing these ROMS and they are great. I've used both at different times to overcome some issues - may be the best way to go at this stage.
Good luck --- S.
Click to expand...
Click to collapse
Stock and yes, 1045.
I've fixed the issue by restoring the phone through the fast boot (but lost all my data because I couldn't create a backup at all).
Case closed, thanks.
moralesnery said:
Something caused and error in your firmware, you have to do the following:
1.- Try to backup your files. See if you can connect it to the PC and explore the files from there.
2.- Once backup is done, you have 2 ways:
A) Unlock bootloader, then flashing TWRP recovery, then installing a custom ROM like CyanogenMOD or AOSP.
B) Search and download the stock firmware file, extract the files, and then flashing it to your phone using mfastboot excecutable.
You can find the files and the info here in XDA thread, just do it carefully and read instructions.
If you can't find something say it and I can help, but won't spoonfeed you.
Good luck.
Click to expand...
Click to collapse
I'll migrate to the Oneplus 3 soon, but just so you know, I'll root the phone later on, couldn't find the cause of the problem and had to wipe the phone in order for it to work, so that's it, case closes. Thanks.
Good to know ...
xtragen said:
Stock and yes, 1045.
I've fixed the issue by restoring the phone through the fast boot (but lost all my data because I couldn't create a backup at all).
Case closed, thanks.
Click to expand...
Click to collapse
If you run into the issue again at any point, your apps and some data can be backed up to your Google account. Additionally, it is worth rooting your phone and installing Titanium Backup (free) available on Play Store to back up all your data. Once rooted, make sure you backup your phone through recovery and copy the contents on your phone over to your computer from time to time, particularly the recovery backups and the Titanium backups. If you haven't created backups on your computer of all your phones folders in the internal and external divisions on your phone through a USB connection, another solution, in the event you lose USB, is to take out your SD card, insert it in a card reader and create matching folders for both internal and external (SD Card) on you computer and copy all the contents over directly from the card.
Takes a little time but backups can save your ass when needed.
S.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not included in the changelog is the addition of a feature from Paranoid Android, locking recent tasks! And multitouch has also been fixed
Update is a rollout so you may not have it yet.
Factory images now live, check out @linuxct post here
If you come across any bugs please be detailed about it and leave bug reports.
Anyway of installing via TWRP so I don't loose root... Haven't really flashed a/b phones.
Wow, just when I finished wiping all my data and installing a Resurrection Remix. Ironic.
Is there any way to extract the camera apk to install it in my current ROM?
guys please i need help. has anyone successfully installed razers stock img files?
After the update, my sim card is no longer being detected. I tried restarting, shutting down, and turning back on. It was working perfectly fine before I restarted after updating.
Edit: It may be the sim card actually died. I tried it on another phone and it doesn't work there either. So it seems like coincidence that it died after the update.
Hmmmmm update fails for me. Not rooted bootloader locked. Error couldn't update installation issue helpfull error.
Fastboot images now live: https://developer.razer.com/razer-phone-dev-tools/factory-images/
Direct link: https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-5038.zip
Taking a hell of a long time to install.... I'm using Snap Camera these days, which is great, I wonder what the new portrait mode is like..... But I can't see me changing back to stock now..
What is the best way to update when I'm rooted and have TWRP installed?
SeriousFlash said:
What is the best way to update when I'm rooted and have TWRP installed?
Click to expand...
Click to collapse
Use the factory images posted here
My update also fails when I'm not rooted and have my bootloader locked
My may update is now installing itself. I do wish it had prompted me rather than having to run a manual update as I was just going through some setting and clicked the update in error.
Updated and noticed loads of fixes, however, Bluetooth is now a complete no go with my car stereo. Sometimes I manage to actually connect it and can play music by pressing play on the phone but no song titles are shown on the car and music playback controls don't work at all... Has anyone had a similar issue or an idea as to what's wrong?
linuxct said:
Use the factory images posted here
Click to expand...
Click to collapse
How would I go about doing that then?
Make sure you go to Settings, system and Razer Preferences and Disable the Share Data again... it gets turned on with the update.
Got the OTA this Morning on my Three branded device and installed without issue.
Nice to see a timely release of the monthly security fixes - is this a benefit of Project Treble support ?
ccjack said:
Anyway of installing via TWRP so I don't loose root... Haven't really flashed a/b phones.
Click to expand...
Click to collapse
Just use the factory images but before flashing, edit the flash_all.bat go to the line that reads %fastboot_cmd% erase userdata" and put a pound "#" sign before the line so that adb ignores that line. Also do the same at the end of the script where you see "%fastboot_cmd% reboot". Doing the following will stop the script from formatting your data partition and keep your phone in download mode after the flashing process. Now you can do the "fastboot boot twrp-whatever-filename.img" and boot to twrp like you were to root like before and once in twrp, flash twrp zip and magisk zip same as before. Everything should work fine now.
Again. Make sure you edit the bat file so the factory images dont factory reset your data partition.
The update took 45 minds to install, it was very slow...
Confirm that Multi touch is fixed now
Razer has introduced the portrait mode, but I still prefer Gmod or
Nokia 's stock camera app..
Yet these updates are welcome...
Is there still no way to update and keep twrp?
navin2max said:
The update took 45 minds to install, it was very slow...
Confirm that Multi touch is fixed now
Razer has introduced the portrait mode, but I still prefer Gmod or
Nokia 's stock camera app..
Yet these updates are welcome...
Click to expand...
Click to collapse
Where I can fine a Nokia cam app?
Hello everyone, I have recently been trying to gain compatibility with Lineage OS 16(Android 9 Pie) along with Open GApps, following all the steps of many tutorials, however it does not work at all. Unfortunately, I am inexperienced with this as this is my first time rooting a phone. I loaded the phone into TWRP, however loading the OS shows the loading screen, but then just goes back into TWRP. I apologize if someone has already made a post on this, however I couldn't find anyone having this problem on this device. I used Kingoroot since I didn't have a data cable on myself at the time, so that could be an issue with the bootloader...? I'm really not sure, and help would be much appreciated.
I didn't do this on the Note 2 forum because it is not hard to say that forum is barely viewed, and it could take weeks for me to get a response.
Before I deleted the original OS, it was on Android Kit Kat
hypixel said:
Before I deleted the original OS, it was on Android Kit Kat
Click to expand...
Click to collapse
I have issue too except i didnt use Kingroot but use odin.
i tried to flash the rom and got the following error msg. I attached screenshot. Does anyone have any solutions to this?
The zip file is lineage-16.0-20200101-unofficial-t0lte.zip
My phone is SGH-T889. It specifically says the zip file is for this model but somehow it doesnt recognise my phone model. Did i wipe something that wipe that along??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Much thanks
Ok, i resesrch some and got rid of the Error 7 msg by deleting the "assert" lines in the updater.script
But now i get Error 6. Anyone with any ideas?
Android_noop said:
I have issue too except i didnt use Kingroot but use odin.
i tried to flash the rom and got the following error msg. I attached screenshot. Does anyone have any solutions to this?
The zip file is lineage-16.0-20200101-unofficial-t0lte.zip
My phone is SGH-T889. It specifically says the zip file is for this model but somehow it doesnt recognise my phone model. Did i wipe something that wipe that along??
View attachment 5263095
Much thanks
Click to expand...
Click to collapse
Have you tried different roms, or only this one?
hypixel said:
Have you tried different roms, or only this one?
Click to expand...
Click to collapse
Only this one
Android_noop said:
Ok, i resesrch some and got rid of the Error 7 msg by deleting the "assert" lines in the updater.script
But now i get Error 6. Anyone with any ideas?
View attachment 5263799
Click to expand...
Click to collapse
Hey, I found out that the issue (at least for me) was that my phone did not have enough storage/the partitions were creating the issue. I am not sure how to solve this, but you may be having the same issue
hypixel said:
Hey, I found out that the issue (at least for me) was that my phone did not have enough storage/the partitions were creating the issue. I am not sure how to solve this, but you may be having the same issue
Click to expand...
Click to collapse
Did u wipe before install?
If one wipes then installs, there should be enough storage space right?
Android_noop said:
Did u wipe before install?
If one wipes then installs, there should be enough storage space right?
Click to expand...
Click to collapse
Yes, I did wipe, however I think the issue is that the phone is creating partitions. This phone was bought many years ago, so it is also possible that the storage is innsuficient for newer versions of Android.
hypixel said:
Yes, I did wipe, however I think the issue is that the phone is creating partitions. This phone was bought many years ago, so it is also possible that the storage is innsuficient for newer versions of Android.
Click to expand...
Click to collapse
Well how did people install this OS onto their note2 on youtube??
Android_noop said:
Well how did people install this OS onto their note2 on youtube??
Click to expand...
Click to collapse
I think that they bought higher storage models