Related
Currently this link https://forum.xda-developers.com/tm.../nougat-h90130b-boot-img-img-upgrade-t3638750 suggests that this can be flashed on the H900.
I am starting this thread so that people can share their experiences of what they have tried so far and declutter the above thread so that all H900 related discussion can take place here.
I am currently on Marshmallow with no root and have experienced the same issues as many others
The instructions on the above thread read as follows
* adb reboot recovery
* adb push boot.img /sdcard
* adb push system.img /sdcard
* adb push modem.img /sdcard
* adb push rpm.img /sdcard
* adb shell
* cd /dev/block/bootdevice/by-name
* dd if=/sdcard/boot.img of=boot
* dd if=/sdcard/system.img of=system
* dd if=/sdcard/modem.img of=modem
* dd if=/sdcard/rpm.img of=rpm
* exit
* adb reboot system
The challenges :
1. 'adb reboot recovery' when we do this on H900 on MM we get a green droid with red triangle and can no longer see the device over adb.
2. 'cd /dev/block/bootdevice/by-name' gives permission denied.
What I tried was the following :
1. Copied boot.img to /sdcard
2. Copied system.img to /sdcard
3. I then installed dirtycow and managed to get the root icon in the terminal '#'
running dirtycow in the terminal gave this :
[INFO] Complete. Installed package "run-as" on device.\n[INFO] Cleaning up workspace...Done
[INFO] Starting shell in 3 seconds...
[email protected]:/ $ run-as -exec sh
uid run-as 2000
uid 0
0 u:r:runas:s0
context 0 u:r:shell:s0
[email protected]:/ # ls /dev/block
/dev/block: Permission denied
1|[email protected]:/ #
So my questions are as follows:
1. If we cannot reboot into a useful recovery are we screwed?
2. Am I using dirtycow correctly?
3. Is this a complete non-started as H900 has a locked bootloader?
Cheers,
Trev
3. If this a complete non-started as H900 has a locked bootloader?
Click to expand...
Click to collapse
If you enable developer mode, and then enable OEM unlock, are you able to adb reboot bootloader and then fastboot oem unlock?
If you are not able to unlock your bootloader, then yes it is a non-starter.
What was the root procedure for LP on the H900?
-- Brian
runningnak3d said:
If you enable developer mode, and then enable OEM unlock, are you able to adb reboot bootloader and then fastboot oem unlock?
If you are not able to unlock your bootloader, then yes it is a non-starter.
What was the root procedure for LP on the H900?
-- Brian
Click to expand...
Click to collapse
Hi Brian,
OEM unlock was enabled. Issuing adb reboot bootloader merely reboots the phone.
I foolishly upgraded to MM when I got the phone. There was a rooted Lollipop ROM on here but it is not possible to go back to L once on M.
It looks like AT&T have really locked this phone down. Being in the UK it is also not possible to get AT&T upgrades from their server.
Looks like we are stuck on MM. I cannot even uninstall an app. The phone simply soft reboots.
The root procedure for L was this : https://forum.xda-developers.com/att-lg-v10/general/root-lg-h900-real-tot-make-tungkick-t3336317
Cheers,
Trev
Thanks for starting up a dedicated thread for this. AT&T have really messed this device up! We can't even roll it back to LP, those who've tried bricked! I'm happy to do some testing, just can't do anything too risky until I get my wife another phone since she's using this one.
trevt said:
Hi Brian,
OEM unlock was enabled. Issuing adb reboot bootloader merely reboots the phone.
I foolishly upgraded to MM when I got the phone. There was a rooted Lollipop ROM on here but it is not possible to go back to L once on M.
It looks like AT&T have really locked this phone down. Being in the UK it is also not possible to get AT&T upgrades from their server.
Looks like we are stuck on MM. I cannot even uninstall an app. The phone simply soft reboots.
The root procedure for L was this : https://forum.xda-developers.com/att-lg-v10/general/root-lg-h900-real-tot-make-tungkick-t3336317
Cheers,
Trev
Click to expand...
Click to collapse
Hi
I am also in UK but I bought my H900 from HK and it came with MM already installed (can't remember which) but I loaded LG Bridge and selected software update and low and behold it updated me to H90021w. I would love to get root on this phone and am willing to test as necessary.
Sent from my LG-H901 using Tapatalk
Hi Stransky,
Do you have any problems with the H90021w update, for example unable to uninstall apps, broken finger print sensor etc?
trevt said:
Hi Stransky,
Do you have any problems with the H90021w update, for example unable to uninstall apps, broken finger print sensor etc?
Click to expand...
Click to collapse
No, no problems at all. The firmware updated as an upgrade as I retained all my apps and settings.
Sent from my LG-H901 using Tapatalk
Hi Stransky, interesting yours already came with MM. I think this is why your update went fine without issues. I upgraded from LP so that could be where something broke.
A friend is in the US at the moment and took my H900 with him and he upgraded it using an AT&T OTA update with an AT&T sim card installed. When I get it back I will report back if this solved the problem.
Cheers,
Trev
Our ATT phone in general does not have an unlockable bootloader, which means we can not (openly) root our device on MM. This also means we can not install a custom recovery onto our device, of which is needed in order to execute adb commands onto the phone. I don't think this device will ever see a custom recovery or root, and I would be surprised if we even see official nougat at this rate.
bkman08 said:
Our ATT phone in general does not have an unlockable bootloader, which means we can not (openly) root our device on MM. This also means we can not install a custom recovery onto our device, of which is needed in order to execute adb commands onto the phone. I don't think this device will ever see a custom recovery or root, and I would be surprised if we even see official nougat at this rate.
Click to expand...
Click to collapse
I would tend to agree with your assessment. Such a waste of a great phone.
H900 at&t USA Holiday.
Hi Trev,
I just read you post about a friend taking your phone to the US and with an at&t Sim was hoping for an Android upgrade.
Did it work? I love the phone and a nougat upgrade would be a dream but the thought to download/upgrade manually is tempting but I am not too confident I will be successful and will no doubt damage the phone.
Cheers
Bert
bertiebro said:
Hi Trev,
I just read you post about a friend taking your phone to the US and with an at&t Sim was hoping for an Android upgrade.
Did it work? I love the phone and a nougat upgrade would be a dream but the thought to download/upgrade manually is tempting but I am not too confident I will be successful and will no doubt damage the phone.
Cheers
Bert
Click to expand...
Click to collapse
Hi Bert, no it did not work.
it hurts, I'm in marshmello and I have the same problems, I can not uninstall apps: c ... nougat and apparently never arrived.
Is there any hope that official nougat for the h900 will come out? .... I update it to mm and the device is almost unusable of the errors it has: c, and it can not be returned to Lollipop either.
trevt said:
Hi Bert, no it did not work.
Click to expand...
Click to collapse
Me too! I sent it to my brother living in the US. He tried to update it to the latest security patch (Kernel version: 3.10.84
Build number: MRA58K /Software version: H90022b) which is stated in the AT&T website:
(To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!)
BUT unfortunately, even he succeeded to connect to their servers he couldn't get any update. Simply it didn't work!! He tried with AT&T customer service to get some technical quote or advice, but they knew nothing about the issue or how to solve it! the efffing At&t and LG!!! are both held responsible for the H900 variant mess!!!
Fakalus77 said:
Me too! I sent it to my brother living in the US. He tried to update it to the latest security patch (Kernel version: 3.10.84
Build number: MRA58K /Software version: H90022b) which is stated in the AT&T website:
(To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!)
BUT unfortunately, even he succeeded to connect to their servers he couldn't get any update. Simply it didn't work!! He tried with AT&T customer service to get some technical quote or advice, but they knew nothing about the issue or how to solve it! the efffing At&t and LG!!! are both held responsible for the H900 variant mess!!!
Click to expand...
Click to collapse
Have you try to do factory reset before trying to update? also fresh LG up flashing may help..
Posting my experience for future reference and to help others trying to go this path.
I started with an Essential Phone that was not originally on Sprint, Custom ROM (AOSiP 8.1), bootloader unlocked, and had a Cricket Wireless SIM. I wanted to take advantage of the Sprint BYOD free unlimited for a year deal. Went through the pain of getting the Sprint SIM and transferring service. All was well except my phone number was not registering and was unable to make phone calls. Sprint LTE data was fine. SIM status showed Phone Number as "unknown." I needed to update the PRL. The *#*#72786#*#* didn't work to update the PRL and there was no menu item in settings within AOSiP 8.1 (also tried using Lineage 15.1). Here's the steps I took to get it working on Sprint.
1. Backed up files
2. ADB to fastboot
3. Flashed twrp-mata_11.img
4. Selected Boot Recovery in fastboot menu to boot to twrp
5. Clean wipe
6. Downloaded and transferred stock Oreo 8.1 beta from Essential website
7. Flashed PH1-OTA-OPM1.180104.010.zip using twrp
8. Rebooted phone and went through initial setup.
9. PRL options under Settings>System>About phone>OMADM updates
10. All is well on Sprint
I use Linux Mint and used the following commands:
sudo adb devices
sudo adb reboot-bootloader
sudo fastboot devices -i 0x2e17
sudo fastboot flash boot twrp-mata_11.img -i 0x2e17
Update: I was disappointed with Sprint service on PH1-OTA-OPM1.180104.010.zip. I decided to try the latest build of 8.1 (June 2018 Release | Oreo 8.1 - OPM1.180104.234). I've been using it as my daily. This build is a significant improvement from the last one I've tried to use. Better reception, smoother UI, no hiccups so far. I was just about ready to give up on this phone.
jcastle003 said:
Posting my experience for future reference and to help others trying to go this path.
I started with an Essential Phone that was not originally on Sprint, Custom ROM (AOSiP 8.1), bootloader unlocked, and had a Cricket Wireless SIM. I wanted to take advantage of the Sprint BYOD free unlimited for a year deal. Went through the pain of getting the Sprint SIM and transferring service. All was well except my phone number was not registering and was unable to make phone calls. Sprint LTE data was fine. SIM status showed Phone Number as "unknown." I needed to update the PRL. The *#*#72786#*#* didn't work to update the PRL and there was no menu item in settings within AOSiP 8.1 (also tried using Lineage 15.1). Here's the steps I took to get it working on Sprint.
1. Backed up files and ensure ADB Debug is enabled in Development Tools.
2. ADB to fastboot
3. Flashed twrp-mata_11.img
4. Selected Boot Recovery in fastboot menu to boot to twrp
5. Clean wipe
6. Downloaded and transferred stock Oreo 8.1 beta from Essential website
7. Flashed PH1-OTA-OPM1.180104.010.zip using twrp
8. Rebooted phone and went through initial setup.
9. PRL options under Settings>System>About phone>OMADM updates
10. All is well on Sprint
I use Linux Mint and used the following commands:
sudo adb devices
sudo adb reboot-bootloader
sudo fastboot devices -i 0x2e17
sudo fastboot flash boot twrp-mata_11.img -i 0x2e17
Click to expand...
Click to collapse
jcastle003 said:
Update: I was disappointed with Sprint service on PH1-OTA-OPM1.180104.010.zip. I decided to try the latest build of 8.1 (June 2018 Release | Oreo 8.1 - OPM1.180104.234). I've been using it as my daily. This build is a significant improvement from the last one I've tried to use. Better reception, smoother UI, no hiccups so far. I was just about ready to give up on this phone.
Click to expand...
Click to collapse
Why give up? Didn't like it? Bad service? I want either this or a pixel xl, 128gb is the same price point but I believe the essential is a better overall device for what I want, just doing some research!
andrew2432 said:
Why give up? Didn't like it? Bad service? I want either this or a pixel xl, 128gb is the same price point but I believe the essential is a better overall device for what I want, just doing some research!
Click to expand...
Click to collapse
I haven't given up. It's actually been my daily since I put the latest update. It has been good so far. Minor issues with reception compared to a GSM SIM. Not complaining since the service is free. My latest opinion... Much better experience with the phone on Sprint with the latest ROM update.
jcastle003 said:
I haven't given up. It's actually been my daily since I put the latest update. It has been good so far. Minor issues with reception compared to a GSM SIM. Not complaining since the service is free. My latest opinion... Much better experience with the phone on Sprint with the latest ROM update.
Click to expand...
Click to collapse
I just meant why about to give up, sorry. Awesome thanks! I want this over a pixel if I can, I live in a bad service area. I've seen the pixel on sprint get better than my current phone and more stable so I'm interested in sprint on this!!
PREWARNING
THIS GUIDE IS !!ONLY!! FOR N9600 (INTERNATIONAL Snapdragon Model)
DO NOT ATTEMPT ON SPRINT, VERIZON, T-MOBILE, AT&T, OR ANY OTHER US (United States) MODEL PHONE.
BEWARE!! N960U or N960U1 HAS A LOCKED BOOTLOADER WHICH CAN NEVER BE UNLOCKED!
IF YOU ATTEMPT TO ROOT ON ANY US MODEL, YOU WILL BRICK YOUR PHONE!
If you have an N9600 international snapdragon model, please proceed. If not, read for your pleasure or future consideration but DO NOT attempt on a US model.
This guide can also be useful for N960F or N960FD international Exynos models, but you would have to change some things like use the right links.
==================================================================================================
Intro Notes:
I REPEAT: THIS GUIDE IS !!ONLY!! FOR N9600 (INTERNATIONAL Snapdragon Model)
If you have an N9600 international snapdragon model, please proceed. If not, read for your pleasure or future consideration but DO NOT attempt on a US model.
After much thought, research, reading, and contemplation, between Note 8, Galaxy S9+, and Note 9, I have decided on the Note 9.
Out of the available options for rooting, there are the devices, N960F, N960FD, and N9600.
Of course, N960F N960FD are Exynos. Unfortunately, these will not work on Verizon, so I would have to switch to T-Mobile. To stay on Verizon it would have to be N9600.
Ultimately, I decided on N9600. Why? Because with Detonator, I can root the N9600 on Verizon, and it's the only model that I can use on Verizon fully rooted. (There is a partial root on N960U, the US Snapdragon variant, but the root is only partial and will have bugs or may not wok.) I could root with a partial root the Note 8 US version, but it is not that much cheaper and it would only be a partial root, so I decided on N9600.
You can root fine on the Exynos versions, but you could not use Detonator for WIFI calling and other features on Verizon.
Rooting Guide
0. Battery must be above 82% before rooting.
1. Root N9600 using TWRP method (Beta)
PLEASE READ ALL INSTRUCTIONS THERE FOR ROOTING.
https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-note9-snapdragon-t3845536
(Official XDA Magisk Install Guide, don't follow directly just reference)
2. RMM State Fix (Prevent "Prenormal")
IMMEDIATELY after getting into TWRP, flash the RMM-State_Bypass_Mesa_v2.zip (linked below).
If you do not, then you will get locked out for 7 days in the event you flash anything or flash a new OS or downgrade to Oreo, etc.
You have to do this EVERY TIME you flash something to prevent RMM state to going to "Prenormal" which means wait 7 days before you can flash any non-samsung firmware.
3. How to fix: Stuck on Prenormal and didn't bypass, OEM Unlock missing
You might be stuck because you didn't do the RMM bypass above. In this event, you will be blocked from flashing custom binaries including TWRP. The only thing you will be able to flash is original Samsung firmware.
How to bypass now? There are two solutions for solving Prenormal RMM state. I have done both successfully. There is a third but it rarely seems to work (date hack, available at many sites.)
METHOD 1: Long way around. Wait 7 days.
First wipe your whole device again and reflash your original OS in ODIN. If you don't do this then it's possible that after 7 days, OEM unlock will not show up.
Now wait 7 days.
Do not reboot your device, just for good measure. I did reboot my device, several times, and it still appeared after 7 days and a reboot. Don't know if you'll have the same luck.
The second time after turning on OEM Unlock, however, when it wiped my device, I did NOT reflash the whole OS again. And, after 7 days again, it did NOT show up.
METHOD 2: I waited 7 days, but no OEM unlock! Solution: Chimera application for windows. NOT FREE!
I was tired of waiting so I decided to try it, and it worked.
Activate Developer options
Activate USB Debugging (in Developer Options)
DISABLE "Verify apps via USB" (in Developer Options)
Go to https://chimeratool.com/
Buy the 3 days trial.
Download after paying in PayPal.
Install full application and all drivers. Don't customize it just install full.
Put your phone into Download mode
Turn off phone.
Hold Bixby & Volume Down
Plug phone into PC.
Press volume up at prompt. Download mode will be activated.
Now in Chimera application in Windows it will find your phone.
Choose the option "UNLOCK".
Choose the sub option, "RMM Unlock".
SUCCESS!! NO WAITING!! OEM Unlock activated. Worth every penny in my opinion (because it wasn't too many pennies).
Proceed to install TWRP and DO NOT FORGET TO INSTALL RMM BYPASS AFTER EVERY SINGLE FLASHING OF ANYTHING!!
4. After rooted, flash Detonator
File: Verizon EFS/CSC Detonator: Detonator v3 for Oreo 8.1 (linked in file list below)
(There is no Detonator for Pie on Verizon as of this writing, only Oreo)
0. Download DETONATOR_XXX_OREO_VZW_EFS-CSC_vx.x_INT_TEKHD.zip to your phone.
Maybe just copy to your SD card, easiest way.
In order to flash detonator, in TWRP select every box on the Mount screen (OTB will not be available unless you have one connected, but everything else).
Backup all partitions via TWRP.
Then go to Install (in TWRP) and flash the zip file for Detonator which applies to you. (Do NOT flash right after flashing a ROM!; First boot ROM at least one time… then go back to TWRP and flash Detonator)
After you successfully flash detonator and there are no errors, now if you want to remove the Verizon boot screen now go ahead and flash (through Install screen in TWRP) the Samsung BootAnimation zip on the Detonator website. This will replace your boot with the stock black samsung boot.
After doing these, please remember to flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Detonator features (from the website):
*With the Verizon Detonator you will get:
– VoLTE, Wifi-Calling /4G/LTE/ONLINE services & features.
– AdAway
– AppLock
– OperaMax (VPN/Data Saving)
– Caller ID & Spam Protection
– Phone and messaging Firewall
– Floating Messages
– Screencast/ScreenRecorder
– Ultra Data Saving Mode
– When booting for the first time… turn off “Confirm Network Connection” Under Settings -> Connections… (*IF AVAILABLE*) (see image below)
Changelog for Verizon Detonator:
v3 – CSC Features added / Wi-Fi Calling APK Update
vPRE-2.2 – Smart Manager Device Security Fix
vPRE-2.1 – Added Mobile Data Toggle to Power Menu.
vPRE-2 – Fixed XML Code / Features Added
vPRE-1 – Initial Release. (Test Phase)
NOTE: After installing Detonator, WIFI Calling button disappeared. I confirmed that I do NOT have WIFI calling, sadly. It doesn't work.
Test it by turning on airplane mode, then connecting to WIFI, then try to make a call. You will get a popup with option to turn on WIFI calling. If you try, it will result in an error, "Unable to activate WIFI Calling at this time, please try again later".
There is presently no solution I am aware of, but maybe someone else knows how, search the forums. Also maybe it has to do with the particular OS I decided to use. I could start over from scratch and try again, but it would be a lot of work and I am out of time for now.
Keep in mind you have to activate on Verizon (see below) before trying to make a call.
5. ACTIVATE ON VERIZON:
Activating on Verizon cannot be done through their site, it will result in an error that your device is incompatible, so don't bother with that.
0. In order to activate you just need an already working SIM card.
Activate a new Verizon SIM card on your PREVIOUS device.
If you need an excuse say you need it for your new phone and YOU will activate it yourself right in the store. Then say it's not working let's try activating on my old phone first.
After the new SIM is working on your OLD phone, leave the store and go home. Now, at your leisure remove the SIM from your old phone and now insert it into your N9600.
Reboot. Now you will be activated on Verizon! (NOTE: YOU MUST ALREADY HAVE DONE DETONATOR, FOLLOW ALL STEPS ABOVE FIRST.)
After you do the rooting below, you'll get messages from SecurityLogAgent saying "security error your device was modified, reboot to revert the changes". You can eliminate this by going into Titanium Backup and FREEZE the following:
SecurityLogAgent
Security policy updates
Software update
Configuration Update
6. Magisk Manager
Boot into phone. If you see Magisk Manager it means you are rooted, probably.
To check it open the Magisk Manager app on your phone.
Feel free to update Magisk. I updated it in the app to 19.3 for Magisk and the installer (flashed from the zip in TWRP) is 7.2
Tap to start safetynet, and accept all prompts.
Reboot
Test if rooted by installing Titanium Backup. If it asks for SuperSU permission then Grant, and it means you are rooted!
7. After rooted, install Xposed
Download xposed from the link in the files section below. If you have a Note 9 on Oreo 8.1 then your file is the SDK 27 for Arm64.
In TWRP, flash the zip file.
Now flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Backup if desired.
Boot your phone.
Go to the xposed links and get the APK file for xposed. This will be the app you use to manage xposed.
WARNING:
One or more of the settings in the xposed module GravityBox [O] causes bugs and removes your Verizon compatibility. In order to solve the error "No SIM card inserted" (but it is inserted!), what you have to do is to go back into TWRP, and do all steps for the Detonator instructions that I wrote above (it will NOT wipe your device, so don't worry). Once you re-flash Detonator, your Verizon will work again and the SIM card message will be gone.
WARNING 2:
There was another xposed module that caused a similar issue but worse. The issue in reference is you get a black screen at the lock screen but nothing can come up but the reboot menu. You cannot get into the phone. I was about to consider having to factory reset before I solved the issue. Since the issue was an xposed module, then the solution is to:
Download the most recent arm64 xposed uninstaller .zip file from here: https://dl-xda.xposed.info/framework/uninstaller/
Boot into TWRP, flash the xposed uninstaller zip.
Clear the cache and dalvik cache like it suggests using that button on the screen there.
Now flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Reboot into your phone, your problem is now solved!
Finally, go into Xposed Installer and find the Module that was causing the issue, long-press on it and choose uninstall. I know you want to keep it, but it's too bad, you can re-download it later, you will be unable to simply unselect it. You have to uninstall it.
Now you can go back into TWRP and reinstall xposed.
Last step: flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Files Needed
ODIN: https://odindownload.com/
- Odin 13.3.1
TWRP: https://forum.xda-developers.com/devdb/project/?id=29220#downloads
- TWRP_3.2.3-0_N9600_beta3.tar.md5
- boot.img (he recommends to use this, see tutorial)
- Encryption disabler.zip
MAGISK: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- Magisk 16.7 19.3 (can I use latest version 19.3? Answer: YES, I used 19.3 without any problems.)
USB DRIVERS: https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
- SAMSUNG_USB_Driver_for_Mobile_Phones.zip
BYPASS RMM STATE: https://forum.xda-developers.com/showpost.php?p=75360965
- RMM-State_Bypass_Mesa_v2.zip
DETONATOR: http://tekhd.com/detonator-o/
- DETONATOR_N9_OREO-8.x_VZW_EFS-CSC_v3_INT_TEKHD.zip
DIRECT LINK (VZW v3): https://androidfilehost.com/?fid=11410963190603842742
MIRROR: https://mega.nz/#!cP52EYKS!L9Oc7nihQ2RoXddZPAPXCPdVLvzhXq3VZtaZXGzBtDQ
(link is was down but I have the file which I uploaded for you: [EDIT: TekHD link is back up now! The domain was expired but I spent some time on the phone with GoDaddy trying to renew their domain for them, maybe the dev was able to see it since I told them to reach out to him specifically. GoDaddy refused to let me donate to renew his domain for him. Again update it appears the site is down again. But not expired this time, it just says "pageok". I do have all the data from that site so I will upload it for the community sometime.]
XPOSED (for Oreo 8.1): https://dl-xda.xposed.info/framework/sdk27/arm64/
- xposed-v90-sdk27-arm64-beta3.zip
XPOSED UNINSTALLER (to fix a bad module. See Warning 2.): https://dl-xda.xposed.info/framework/uninstaller/
- xposed-uninstaller-20180117-arm64.zip
OREO 8.1 FIRMWARE (for downgrade):
- N9600ZHS1ASB1 / N9600OWA1ARL5 (N9600 8.1 Oreo 2019-02-01 Chile) https://www.sammobile.com/firmwares/galaxy-note9/SM-N9600/CHL/download/N9600ZHS1ASB1/259310/
- N9600ZHU1ARG6 / N9600OWA1ARG6 (N9600 8.1 Oreo 2018-07-01 Dom Rep) https://www.sammobile.com/firmwares/galaxy-note9/SM-N9600/CDR/download/N9600ZHU1ARG6/231741/
- N9600ZHU1ARG6 / N9600OWE1ARG6 (N9600 8.1 Oreo 2018-07-01 Ecuador) https://www.sammobile.com/firmwares/galaxy-note9/SM-N9600/ALE/download/N9600ZHU1ARG6/231755/
** These three files have been removed from sammobile as of today 2019-05-25, because they were there yesterday. You can still view directly but they will no longer show on the page for the N9600 because sammobile is no longer showing any Oreo (8.0, 8.1) firmwares for the N9600 on their site, only Pie firmwares (9). It's likely these will be removed soon, so I will upload mirrors to the firmwares once they are finished downloading.
(NOTE: DO NOT download firmware N9600ZHS1ASA7_N9600OWT1ARK1_SAM because it will after initializing forcefully change your boot branding to a bright baby blue screen with Movistar carrier branding instead of a normal black samsung boot screen. This will be removed by re-flashing so it's harmless, just annoying. Instead use the above linked. So far I have only tested N9600ZHS1ASB1 above which is fine, it is on the Clara carrier and installs minimal carrier bloat which can be removed after rooting. I linked the other two which I will try as they use pre-August 2018 firmware so hopefully I can get the OEM Unlock to show since I didn't know about the RMM state fix before flashing Pie down to Oreo.)
UPDATE:
This guide is now completed and released. The steps are fully working to get your N9600 working on Verizon.
Someone asked me if regular calling works if they don't have WIFI. Of course. Your phone will fully work on Verizon as normal. In addition to fully working, WIFI calling also works (for some firmwares).
UPDATE 2:
DEAR EVERYONE:
Sorry it took so long for me to upload the files. It appears that TekHD website is now dead for good. It's been down for months. So, since I already had downloaded all the content from the website, including the website pages themselves, I'm now uploaded everything from TekHD for your use. I'm also including all of my rooting files for your use and enjoyment.
Will update the links here when the uploads complete. Enjoy!
EDIT: Here's the link!
https://mega.nz/#F!UbZFSAwC!FObELw39ZmADygAJOFVlyw
-
[moved content from here into original post]
[reserved]
I used a exynos S9+ and I'm using a note 9 exynos on Verizon. You don't need to flash anything because if you use shortcutmaster to bring up Ims settings, with root of course, you can enable all you need.
But you don't have wifi calling or several other things right?
I also had to do a RMM state flash. But I didn't know and now I am blocked from doing anything for a week after downgrading OS. Wish someone would have told me ahead of time. The hacks to change date to bypass and re-enable OEM lock DOES NOT WORK. Trying many things, wasted my whole saturday needlessly.
I finally got the OEM unlock to show.
STEPS:
1. Using Odin flash the whole OS from sammobile. I used 8.1 which is compatible with Detonator.
2. During setup, DO NOT CONNECT TO INTERNET.
3. Choose a date some time in the past like a month or even a year ago. I chose a year ago.
4. finish setup disabling everything.
5. General Management → Date and time. DISABLE Automatic date and time.
6. Enable developer options.
a. Settings > About phone
b. tap seven times on ‘Build number’
7. Settings > Developer options > DISABLE Auto update system
8. It will not work unless you also log into a samsung account.
a. Connect to internet now.
b. Cloud and accounts > Accounts > Add account
c. Sign in or create a new Samsung account.
d. You have to log in and add the account, go back and it should say added.
9. DISCONNECT FROM INTERNET
10. Go to date and time. Choose a date in the future. I chose a few months in the future.
11. Settings > Software update > tap on Download updates automatically (it will error because not connected. It's fine. Don't connect!)
12. REBOOT
13. Settings > Developer options. The OEM unlock option should be visible now.
I think the above is what I did. I might have the order above wrong because I tried so many times I can't remember if that's the exact order. I think it is, but if it doesn't work try a few different ways and eventually you'll get it.
EDIT: When I tried again, above does not work so I must not have remembered what I did perfectly, OR for some reason it just didn't work the second time.
[.]
Before I bust out the Type-C cable, I must ask, will this work on the Sprint variant?
Any plan to ad sprint to the list
eastside08 said:
Before I bust out the Type-C cable, I must ask, will this work on the Sprint variant?
Click to expand...
Click to collapse
NO!!! BEWARE, N960U or N960U1 HAS A LOCKED BOOTLOADER.
IF YOU ATTEMPT TO ROOT ON ANY US MODEL, YOU WILL BRICK YOUR PHONE!
The ONLY Snapdragon model that can be rooted is the INTERNATIONAL N9600. I specifically bought the N9600 for this. This N9600 has an unlocked bootloader.
I was planning on running Detonator on the Oreo 8.1 since the developer TekHD has not yet developed a Detonator for Pie on Verizon. Plus, I read that many people prefer Oreo over Pie. Moreover, Oreo will have more dev support than Pie since Pie is still very new.
I am still working on this so will continue progress updates.
Right now I am stuck because I didn't know about the RMM State so I am stuck on Prenormal, which means 7 days waiting. I had gotten the OEM unlock to show because I was going to disable and re-enable OEM unlock, and when I proceeded it wiped, and then changed to Prenormal preventing from installing TWRP again.
If I had known ahead of time, I could have flashed the RMM fix zip while I had TWRP on there and could have avoided this fiasco. If I get OEM unlock to show again then I will use that to avoid future lockouts.
Right now I am downloading a July 2018 version of Oreo 8.1. I tried flashing several Oreo 8.1 and that is easy with Odin, but could not get the OEM unlock to show up again no matter what I tried. According to this page** (link below), the method of switching the time doesn't work on pre- August 2018 firmwares. That's not entirely accurate as I got it to show up the first time, but I may be stuck now.
So in an effort to try anything, I am downloading and will flash the earlier version of 8.1 from July. Then will try the date method to try to get it to show up. Hopefully it works.
** NOTE: link from above is https://www.thecustom droid.com/prenormal-rmm-state-on-samsung-galaxy-guide/ (remove the space between custom and droid)
For future reference, guides go in the guides section, not development.
Update: I can't get OEM unlock to show up and ran out of time. So, I have to take the long way around and wait a week for it to show up. So, I'll be back on Sunday if OEM unlock shows up.
Im guessing this trips knox ?
why put 'Verizon Full Rooting Guide' when rooting has nothing to do with carriers.
the guide is to get verizon csc on a n9600. you should change the way you named the thread if you dont want to get a gazilion questions from n960u uers.
i sure am confused.
are you able to root a international note9 and use it on verizon network in the usa, or not?
i know elliwigy is working on getting root for a specific model of note9, i think for the usa unlocked or verizon locked model, but it's not useable on stock firmware yet.
UPDATE:
After 7 days, a reboot, and pressing check for updates (but not updating), then checking for the OEM unlock, it did in fact show up.
Unfortunately, enabling OEM unlock also factory resets your phone which AGAIN puts the 7 day lock - which is f*ing ridiculous.
So now I have to wait ANOTHER 7 days before proceeding, so that Prenormal will be able to go to Normal and I can flash TWRP and custom binaries.
Will update again in another week.
bober10113 said:
why put 'Verizon Full Rooting Guide' ... if you dont want to get a gazilion questions from n960u uers.
Click to expand...
Click to collapse
Please note the tag [N9600], if N960U users fail to read the full title, that's their fault. I put all the disclaimers in red anyway just in case, so they can know.
This indeed is about using an international N9600 on Verizon in the USA. I am still working on this and as per my previous post, in another week once the 7 day wait period is over again so I can finish the root and flashing, then I will continue to update about how to get the N9600 working on Verizon.
It is worth noting that you are required to root the N9600 in order to use Detonator.
siriom said:
Im guessing this trips knox ?
Click to expand...
Click to collapse
The answer to this is Yes. It trips Knox. You cannot root without tripping Knox.
dumbfone said:
are you able to root a international note9 and use it on verizon network in the usa, or not?
i know elliwigy is working on getting root for a specific model of note9, i think for the usa unlocked or verizon locked model, but it's not useable on stock firmware yet.
Click to expand...
Click to collapse
The answer to this is hopefully yes, and I have known others to get the N9600 working on Verizon. But I have to wait another week before I can proceed, so please check back next week to see my progress and additional instructions.
Hello everyone,
I have wonderful and amazing news. I have completed fully rooting my Note 9 N9600 and also getting it fully working on Verizon. I am updating the original post now with the details and remaining steps.
It's worth noting that after the second 7 days, OEM unlock would NOT show up. I waited hours more, but still no luck. Instead, I used an application called Chimera which I actually paid for in order to get OEM unlock to finally show up, and it worked.
Update: See the above completed and updated guide.
zxzxzxzxzxzxzxzxzx said:
Update: See the above completed and updated guide.
Click to expand...
Click to collapse
so the way to do it is just flashing the latest detonator?
http://tekhd.com/detonator/
(apparently with full wifi calling support too..)
http://tekhd.com/detonator-o/#vzwdetonator
(or go to detonator telegram channel for possibly modded comunity version...rumor i heard)
implicitly, people probably already know how to root by following the steps outlined from the snapdragon thread..
Hi all. I'm new to the Lenovo space, so please bear with me. After some searching, I can't quite seem to figure out what the model number of the P11 Plus is? Can anyone enlighten me?
Tab P11 Plus | 11" Family Tablet
Meet the Lenovo Tab P11 Plus, an Android tablet featuring an 11" 2K display and quad speakers for immersive multimedia, plus Google Kids Space and Entertainment Space for family fun and education.
www.lenovo.com
Knowing that, can this particular model's bootloader be unlocked and the OS rooted? Cheers.
Found the model number: TB-J616F or TB-J616X
Android Upgrade Matrix - Lenovo Support US
support.lenovo.com
molohov said:
Found the model number: TB-J616F or TB-J616X
Android Upgrade Matrix - Lenovo Support US
support.lenovo.com
Click to expand...
Click to collapse
Have you found the answer whether the Lenovo P11 Plus (TB-J616F) model can be rooted?
I am thinking of buying this tab. Is it stock unlocked or is it not?
kanines said:
Have you found the answer whether the Lenovo P11 Plus (TB-J616F) model can be rooted?
Click to expand...
Click to collapse
The answer is yes.
First, using Rescue and Smart Assist, DL the latest rom for this model this model. I used TB_J616F_S000046_220311_ROW.
Next go to C:\ProgramData\RSA\Download\RomFiles\TB_J616F_S000046_220311_ROW and you will find the boot.img files. Copy it to a folder on the tablet. Remember where.... duh.
Install Magisk 25.2 which is the version that I used. Follow Magisk instructions to "patch" the copied boot.img file. When complete, copy the patch boot image file back to your Adb/Fastboot folder, normally X:\platform-tools.
Put your tablet in fastboot mode and run: fastboot flash boot <name of patched boot.img file>.
So, there's no need to ask questions as there are a least a bizzion guides on the internet on how to do a "Magisk boot.img patch and flash".
I am stuck on unlocking the bootloader as, when I use adb reboot bootloader. I am greeted with => FASTBOOT mode..., and when i go to fastbootd using recovery mode. I am stuck with Download is not allowed on locked devices, and when trying to unlock. Stuck with Command is not supported in default implentation.
levrx said:
I am stuck on unlocking the bootloader as, when I use adb reboot bootloader. I am greeted with => FASTBOOT mode..., and when i go to fastbootd using recovery mode. I am stuck with Download is not allowed on locked devices, and when trying to unlock. Stuck with Command is not supported in default implentation.
Click to expand...
Click to collapse
every android ive unlocked bootloader, you click on the build number in settings 7 times, after aprox 3 it shows a count down until its unlocked, then it depends on the device im pretty sure, it was diff between my phone n table so it depends on ur device here is some resources
Locking/Unlocking the Bootloader | Android Open Source Project
source.android.com
How To: Unlock Bootloader
How To Unlock Bootloader Galaxy A12. *** Disclaimer I am not responsible for any damage you made to your device You have been warned - Go to Settings -> About phone and find your build number. - Tap on your build number 6 times until you see...
forum.xda-developers.com
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
there is a diff between download mode and fastboot, just so u know, you need adb and fastboot from Androids SDK tools, you can find online, depending on ur computers OS. Also, ADB commands work with ur device on n plugged into the computer fastboot is for commands when ur in fastboot mode
levrx said:
I am stuck on unlocking the bootloader as, when I use adb reboot bootloader. I am greeted with => FASTBOOT mode..., and when i go to fastbootd using recovery mode. I am stuck with Download is not allowed on locked devices, and when trying to unlock. Stuck with Command is not supported in default implentation.
Click to expand...
Click to collapse
I have the same issue!!! It seems a problem with the Fastboot mode.
19blacktiger77 said:
I have the same issue!!! It seems a problem with the Fastboot mode.
Click to expand...
Click to collapse
I solved!!!
I just had to download the latest version of ABD and Fastboot!
Hi. i rooted with this video.. it is in portuguese, but the codes are in english, 15 minutes and it´s done..
I also want to root this device but I am waiting for their Android 12 update. Is anyone running Android 12 ?
I've successfully rooted my Lenovo P11 Plus (J616F) tablet via the latest stock rom + Magisk 25.2, and it was much more painless than I'd thought it'd be. But I can't figure out how to get TWRP or any other custom recovery, and I'd be happy to hear if anyone has had any success with it...
HackVasant said:
I also want to root this device but I am waiting for their Android 12 update. Is anyone running Android 12 ?
Click to expand...
Click to collapse
Yes...
1.) Install USB drivers (I used this to detect fastboot mode: https://motorola-global-en-uk.custhelp.com/app/usb-drivers/)
>> NOTE: With your tablet in fastboot mode, you might have to go into device manager and manually update the drivers for your "unknown android device", pointing it to the usb drivers from the previous step)
2.) Install the lastest ADB and Fastboot software
3.) Unlock your bootloader!
3a.) Enable developer options -> Enable OEM unlocking
3b.) Enter fastboot mode (turn tablet off then hold power + volume up until just after it vibrates)
3c.) With your device connected to your PC, type fastboot flashing unlock in command prompt
4.) Look for the current latest stock rom TB-J616F_S240138_221026_ROW_SVC.ZIP
5.) Extract it somewhere on your PC, and copy boot.img to somewhere on your device
6.) Install Magisk v25.2 on your device
7.) Follow the rest of the installation instructions here: https://topjohnwu.github.io/Magisk/install.html
If all went well, after rebooting you might get a warning about your device being in "Orange State" and therefore cannot be trusted because the bootloader was unlocked... This is normal, and your instinct might be to run the command fastboot flashing lock to get rid of it, but THS IS A BAD IDEA because it could place your device into a "Red State" requiring you to unlock it again, effectively wiping your device
Can it play Redbox (free video app) OK after rooted?
If it's OK, I think Netflix and Amazon Prime will be OK as well
mingkee said:
Can it play Redbox (free video app) OK after rooted?
If it's OK, I think Netflix and Amazon Prime will be OK as well
Click to expand...
Click to collapse
Yes, but you will need to do the following...
1.) In Magisk, make sure you have Zygisk enabled in the settings
2.) Install this Magisk module, then reboot your device:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
3.) Use YASNAC (from the app store) to verify that you pass the safetynet check (it passes for me)
4.) Uninstall Netflix, then manually download and install the latest Netflix APK from your favorite APK site
I didn't test Redbox or Amazon Prime, but I would imagine it'd just be repeating step 4 for each additional app you wish to install
You can also read this for more detailed information about Magisk & SafetyNet:
SafetyNet:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
SpectreCular said:
Yes, but you will need to do the following...
1.) In Magisk, make sure you have Zygisk enabled in the settings
2.) Install this Magisk module, then reboot your device:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
3.) Use YASNAC (from the app store) to verify that you pass the safetynet check (it passes for me)
4.) Uninstall Netflix, then manually download and install the latest Netflix APK from your favorite APK site
I didn't test Redbox or Amazon Prime, but I would imagine it'd just be repeating step 4 for each additional app you wish to install
You can also read this for more detailed information about Magisk & SafetyNet:
SafetyNet:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
Click to expand...
Click to collapse
The reason why I asked because A12 can make those video apps don't work even after passed safetynet and play integrity (2/3) and apps installed
However, those apps work on OnePlus N200 and 8T but NOT on Moto Edge 2021
mingkee said:
The reason why I asked because A12 can make those video apps don't work even after passed safetynet and play integrity (2/3) and apps installed
However, those apps work on OnePlus N200 and 8T but NOT on Moto Edge 2021
Click to expand...
Click to collapse
Alright well I decided to take the time to check Redbox, and it works (or at least the Watch Free feature does)... And I don't have a prime account, but the prime video app makes it to the sign in screen, if that helps
SpectreCular said:
Alright well I decided to take the time to check Redbox, and it works (or at least the Watch Free feature does)... And I don't have a prime account, but the prime video app makes it to the sign in screen, if that helps
Click to expand...
Click to collapse
Good!
I will make a backup on mine (I have Yoga 11 and practically they're the same) and unlock the bootloader and root it.
The reason why I root it so I can do adb on other device without laptop.
Actually, I have a lot of experience to root variety of machines, but what happened on Edge 2021 A12 puts me on hold on other Moto/Lenovo
I have Netflix and cable apps (Sling and Philo) and Discovery+.
Well just so we're on the same page, the steps I've posted were specifically for J616F, so your mileage may vary if you're using a different device. Also, I would maybe use a more specific stock ROM, since the one I posted is also specifically for J616F
SpectreCular said:
Well just so we're on the same page, the steps I've posted were specifically for J616F, so your mileage may vary if you're using a different device. Also, I would maybe use a more specific stock ROM, since the one I posted is also specifically for J616F
Click to expand...
Click to collapse
I have to make it clear. I have both P11 plus and Yoga 11
I have the P11 Plus J616F model and cannot get the device to unlock after many attempts with wiping device reinstalling firmware reinstalling device drivers. Does failed (unknown status code) after (bootloader) sysytem-fingerprint:Lenovo/TB-J616F/TB-J616F:12/SP1A.210812.0 mean anything to anyone. I can adb reboot recovery, from recovery I can use the keys to choose fastboot and tab goes into fastbootd and fastboot devices returns my device fashboot flashing unlock starts but ends with the failed message above. fastboot getvar all returns a bunch of information about the device but also stops with same failed message. If I choose reboot bootloader using the keys on my tab while in fastbootd tab reboots to FASTBOOT... shows up in device manager as you would expect but typing fastboot flashing unlock returns waiting for device. Any thoughts or ideas would be greatly appreciated.
Just finished rooting my new Tablet.
Unlocked bootloader, Flashed new factory image and patched Magisk all by manual methods.
PixelFlasher didn't work as it does on Pixel 7 Pro, so save some time and wait for the official support.
Happy to help if anyone gets stuck.
Thanks for the update. Which file did you patch with Magisk to get root?
Are you passing Safetynet?
Rooted the thing 5 minutes out of the box.
Magisk stable. Passes safety net.
Follow a Pixel 7 rooting thread use the latest posted images, patch init_boot.img
I disabled verity too in case a custom kernel is done in the future.
bleez99 said:
Rooted the thing 5 minutes out of the box.
Magisk stable. Passes safety net.
Follow a Pixel 7 rooting thread use the latest posted images, patch init_boot.img
I disabled verity too in case a custom kernel is done in the future.
Click to expand...
Click to collapse
Would do the same. Thank you
MArtyChubbs said:
Just finished rooting my new Tablet.
Unlocked bootloader, Flashed new factory image and patched Magisk all by manual methods.
PixelFlasher didn't work as it does on Pixel 7 Pro, so save some time and wait for the official support.
Happy to help if anyone gets stuck.
Click to expand...
Click to collapse
I don't have the tablet, so the support file would greatly help to add official support for it.
Would you be able to provide it?
If not do you recall what exactly happened?
Was it during processing, patching or flashing?
Thanks
Update:
Aside from flashing, which I can't because I don't have the tablet, the latest version of PixelFlasher is able to process, extract init_boot and create a patch without any issues both for factory image and full OTA.
I even went as far as attempting to flash factory (without actually flashing) to inspect the final flashing script, and everything in there looked right.
I don't see how / where it could have failed, based on what I've seen it should work.
Hence a support file would greatly help if there is any issue to identify.
Thanks
just unlocking the bootloader w/PixelFlasher (latest ver.) "corrupted" my Slot B boot (Your device is corrupted) and it refuses to boot (grin).
Also, I'm pretty sure it said "no init_boot found" as part of device info. I can't confirm as I'm not with the tablet today.
ntegra said:
just unlocking the bootloader w/PixelFlasher (latest ver.) "corrupted" my Slot B boot (Your device is corrupted) and it refuses to boot (grin).
Also, I'm pretty sure it said "no init_boot found" as part of device info. I can't confirm as I'm not with the tablet today.
Click to expand...
Click to collapse
If you could provide a support file from PixelFlasher I can check, and you don't need to repeat the steps to get a support file, just launch PF and hit the support button or from the help menu.
If the unlock command has not changed, I don't see how it would cause that.
All the unlock button does is
if it is in adb mode, it reboots to bootloader mode and then issues the command
fastboot flashing unlock
If it is already in bootloader mode, it just issues the command.
I'm baffled and would really like to get to the bottom of this.
badabing2003 said:
If you could provide a support file from PixelFlasher I can check, and you don't need to repeat the steps to get a support file, just launch PF and hit the support button or from the help menu.
If the unlock command has not changed, I don't see how it would cause that.
All the unlock button does is
if it is in adb mode, it reboots to bootloader mode and then issues the command
fastboot flashing unlock
If it is already in bootloader mode, it just issues the command.
I'm baffled and would really like to get to the bottom of this.
Click to expand...
Click to collapse
soonest I could provide is 6 hours or so..
@badabing2003 yeah, I'll try to get that support file within the next hour. The tool said everything was successful but it always rebooted back to the bootloader when unlocking the bootloader or flashing a new image, thus I had to do everything manually
Update: @badabing2003 Support file is attached. Thanks!
I plan on rooting mine right away. Did anyone have a delay on their order? I have a trip coming up and it's supposed to arrive the day before.
Thanks @MArtyChubbs and @ntegra for providing support files.
@ntegra
Comments / observations based on your support file.
You started with Pixel 7pro,
You had an error during flashing
Code:
Sending sparse 'vendor_b' 3/3 (130768 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sleeping 5-10 seconds ...
flashing pf_boot ...
This is communication issue, phone unplugged or disconnected during flash or wire loose or bad driver / port / cable ...
But then you flashed p7p ok,
Moved to the tablet, which was locked at this point
Code:
Selected Device on 2023-06-20 20:00:50:
Device ID: REDACTED
Device Model: tangorpro
Device Active Slot: a
Device Mode: adb
Has init_boot partition: False
Device is Rooted: False
Device Build: TD2A.230203.028
Device API Level: 33
Device Architecture: arm64-v8a
sys_oem_unlock_allowed: 1
ro.boot.flash.locked: 1
ro.boot.vbmeta.device_state: locked
vendor.boot.verifiedbootstate:
ro.product.first_api_level: 33
ro.boot.verifiedbootstate: green
vendor.boot.vbmeta.device_state:
ro.boot.warranty_bit:
ro.warranty_bit:
ro.secure: 1
ro.zygote: zygote64
ro.vendor.product.cpu.abilist: arm64-v8a
ro.vendor.product.cpu.abilist32:
Device Bootloader Version: tangorpro-1.0-9584303
Magisk Manager Version:
Magisk Path: None
Checked for Package: com.topjohnwu.magisk
You proceeded to unlock the bootloader with PF
Which it did successfully
Code:
Selected Device on 2023-06-21 06:09:09:
Device ID: REDACTED
Device Model: tangorpro
Device Active Slot: a
Device Mode: f.b
Has init_boot partition: False
Device Unlocked: True
One thing to point out, after bootloader unlock, PF keeps the phone in bootloader mode (in case you might want to do other stuff)
But I think people tend to expect it to reboot to system, because I noticed this might have thrown you off seeing it in bootloader mode.
What I'll do for the next release is that unless you select no reboot option, PF should automatically reboot.
Another thing I noticed is that you attempted to create a patch while the phone is in bootloader mode
Which does not work, because that can only work in ADB mode.
In the next version I'll disable the patch button so that when in bootloader mode, you can't press it.
I see that you rebooted to system and the device was unlocked
Code:
Selected Device on 2023-06-21 06:14:41:
Device ID: REDACTED
Device Model: tangorpro
Device Active Slot: a
Device Mode: adb
Has init_boot partition: False
Device is Rooted: False
Device Build: TD2A.230203.028
Device API Level: 33
Device Architecture: arm64-v8a
sys_oem_unlock_allowed: 1
ro.boot.flash.locked: 0
ro.boot.vbmeta.device_state: unlocked
vendor.boot.verifiedbootstate:
ro.product.first_api_level: 33
ro.boot.verifiedbootstate: orange
vendor.boot.vbmeta.device_state:
ro.boot.warranty_bit:
ro.warranty_bit:
ro.secure: 1
ro.zygote: zygote64
ro.vendor.product.cpu.abilist: arm64-v8a
ro.vendor.product.cpu.abilist32:
Device Bootloader Version: tangorpro-1.0-9584303
Magisk Manager Version:
Magisk Path: None
Checked for Package: com.topjohnwu.magisk
Installed Magisk and created a patch.
All good.
You then proceeded to flash with
Flash To Inactive Slot: True
Everything about the flashing went well, but the phone stayed in bootloader mode.
I see now why that happened.
It flashed ok, but then it tried to flash the patched image to boot partition instead of init_boot partition.
PF detects if it needs to flash into init_boot partition or boot partition by doing two checks.
1- If it is defined in PF, and up to version 5.3.2.1 only defined are 'panther', 'cheetah', 'lynx' because at the time of the release only those were known. (tangorpro added in the next version)
2- By checking partitions and seeing if there is a init_boot partition, this way it would be forward working with future devices, but sadly due to oversight the code was looking for init_boot and expecting to find it, but there is init_boot_a and init_boot_b, and not init_boot, (fixed in the next version)
@MArtyChubbs
The flashing your tablet had the same fate as above, PF tried flashing boot partition instead of init_boot.
Fixed, I should have a release later today.
For anyone who cannot wait, and wants to use PF, all you have to do is before hitting OK to continue flashing, hit the Edit script before continuing button and modify the line
Code:
flash boot pf_boot.img
to
Code:
flash init_boot pf_boot.img
As for unlocking, I don't see errors, but I see that the phone was not detected,
Do you recall exactly what happened? perhaps it was showing the wipe message and hence why it was not really yet to be detected?
Code:
2023-06-20 16:58:12 Unlock Bootloader
*** Dialog ***
WARNING!!! THIS WILL ERASE ALL USER DATA FROM THE DEVICE
Make sure you first read either of the guides linked in the help menu.
Failing to follow the proper steps could potentially brick your phone.
Note: Pressing OK button will invoke a script that will utilize
fastboot commands, if your PC fastboot drivers are not propely setup,
fastboot will wait forever, and PixelFlasher will appear hung.
In such cases, killing the fastboot process will resume to normalcy.
Do you want to continue to Unlock the device bootloader?
Press OK to continue or CANCEL to abort.
______________
2023-06-20 16:58:14 User Pressed Ok.
Rebooting device REDACTED to bootloader ...
Waiting 5 seconds ...
2023-06-20 16:58:31 No Device is selected!
2023-06-20 17:12:46 Scanning for Devices ...
No Devices found.
@badabing2003,
Thanks for the response. great program, excellent support. For me, the first p7p failed (I agree with you) due to comm problem. I forget that the USB ports on one side of my laptop are flakey. I watched it bomb out writing system_b (I think) and just moved the cable to the other side and reran the flash to 100%.
For the tablet... I ran unlock twice (was still locked after first attempt). I "want" to say that the "your device is corrupt" was in between the two runs (unlock / reboot / device corrupt / unlock again) but definitely showing corrupt before first flash attempt. After a couple attempts to boot, I put it back into bootloader (and also download & recovery modes) and flashed the patched image, but it didn't help I'm guessing because of the init_boot(_b). Will be patiently waiting (neither slot are booting-grin) for your next release. I'm in no rush.
@badabing2003 I'd like to thank you as well! Love the tool and your excellent support. You and @Freak07 are such an asset to the community as are soo many other devs...
rester555 said:
I plan on rooting mine right away. Did anyone have a delay on their order? I have a trip coming up and it's supposed to arrive the day before.
Click to expand...
Click to collapse
No, arrived right on time.
MArtyChubbs said:
No, arrived right on time.
Click to expand...
Click to collapse
Looks like mine is coming on the earliest day of the planned shipping dates.
@MArtyChubbs and @ntegra
PixelFlasher 5.3.2.0 is released which adds support for Pixel Tablet.
There is also a dedicated support thread.
📳🔥PixelFlasher for Google Tablet Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
Thanks for your support.
badabing2003 said:
@MArtyChubbs and @ntegra
PixelFlasher 5.3.2.0 is released which adds support for Pixel Tablet.
works a treat!
Click to expand...
Click to collapse
I got my tablet. Made the painstakingly slow mistake of updating the OTA before unlocking. The OTA takes forever.
Got my tablet. Had it rooted in less than 30 minutes.
rester555 said:
I got my tablet. Made the painstakingly slow mistake of updating the OTA before unlocking. The OTA takes forever.
Click to expand...
Click to collapse
Yep OTA on a device is very slow and is incremental, specially if you have to flash several times if you are free months behind.
Even if you don't unlock your bootloader, you can sideload OTA in PixelFlasher.