Hi All,
With the recent launch of LineageOS 18.1 I decided to take the plunge and get it installed on my fully stock Videotron/Freedom H915. Since I had to smash together info from a half dozen other threads, I figured I'd gather it all together here for folks with a Canadian phone trying to make this work.
Since I knew absolutely nothing coming into this, I'm going to go a little more detailed on this write-up. If you've been flashing ROMs since the old days of Cyanogenmod you can probably skim half of this.
Disclaimer : I'm not responsible for any bricked phones or other negative outcomes. This is what worked for me, but I'm far from being an expert. If you continue past this point you agree to take your time, do your reading, be responsible for your own device/actions and not hold me or the forum accountable for anything that might go wrong. You've been warned.
IMPORTANT NOTE #1
If you've picked up an H915 on ebay and you are intending to use it on a network other than the one it's SIM locked on, make sure you do the whole SIM unlock process on the stock ROM either before you get started at all, or once you've reverted to the vulnerable stock ROM after Step 1 below.
I actually use Telus as my provider and I wasted a bunch of time trying to figure out why I couldn't get signal because only the stock ROM will prompt you for a SIM Unlock code. Lineage will just sit there dumbly and not allow you to enable data.
Once you've unlocked the SIM it will stay unlocked from that point forward, just make sure to unlock it and verify your SIM is working with LTE on the stock ROM before you get started.
IMPORTANT NOTE #2
Use LGUP's "DUMP" feature to take a backup of ALL partitions on your phone before you start. If you're reading this thinking "I just bought this phone off ebay, there's nothing on it I care about", take the backup anyway. You never know when you might need a copy of the modem partitions or other things from your phone's original build. It came in super handy for me in troubleshooting the process. So go do a backup!
Current Issues:
If signal is too weak to connect to a tower (or non-existent), the OS tends to crash with a modem error. Still trying to figure this one out.
I think I can get this working without first jumping to US996 but haven't had a chance to verify that. If I do I'll update the thread.
Download Prerequisites
Links working as of 2021-06-29
LGUP with patch
Link
Working adb/fastboot environment
Instructions
Download
Fastboot Drivers
Link
Universal ADB Driver
Link
Videotron/Freedom H915 Android 7 (Nougat) version E - H91510e_00_VTR_CA_OP_1205.kdz
Link
USA General US996 Android 7 (Nougat) version F - US99610f_00_1205.kdz
Link
APK for Terminal Emulator
Link or Alternate Link
LG V20 Root Package Original (v4?)
Link
Old TWRP for Root Package
Link
Videotron/Freedom H915 Modem Partition Image
Link
Lineage Install Zip for H910 (grab the latest, I'm using lineage-18.1-20210506-nightly-h910-signed.zip which is already out of date)
Link
MindTheGapps
Link
(Optional, for rooting) Magisk
Link
Different Boot Modes
For those not familiar with these phones, there are three different "modes" the phone can boot into. Here's a quick reference on how to boot into each one.
Download Mode
This mode is used for pushing KDZ files or individual partition backups using LGUP
Turn Off Phone
Hold the Up-Volume Button
Insert USB-C Cable with other end already plugged into PC
Bootloader (aka Fastboot) Mode
The H915 doesn't come with this mode by default. If you try it, you'll just get battery charging. We'll be temporarily converting the phone to a US996 in order to use the DirtySanta exploit to replace the bootloader partition with a leaked Engineering aboot.
This mode is used with the fastboot tool to load the TWRP utility into the Recovery partition.
Turn Off Phone
Hold the Down-Volume Button
Insert USB-C Cable with other end already plugged into PC
Recovery Mode
The recovery mode on a stock phone is used to perform a factory reset. We will be using the Factory Reset a couple times with the stock ROMs, then replacing the contents of the recovery partition with the TWRP tool that allows us to format partitions, load partition images, and sideload apps and LineageOS itself.
Turn Off Phone
Hold the Down-Volume Button
Press and hold Power-On (rear fingerprint sensor/button). When LG Logo appears, release power button for 1 second then press and hold again
When "Factory Data Reset" appears, release all buttons
Press Volume Down to highlight "Yes" then press power button to select the option
Repeat for the confirmation
Note about flashing KDZ files using LGUP
You can flash KDZ files onto the phone using LGUP from two places - either with the phone in "Download Mode", or with the phone booted into the OS with the USB Options set to "File Transfer" and USB Debugging turned on.
The difference between these two is when it performs the OS compatibility check.
In Download Mode it's the code of the Download Mode partition that does the check. In the OS, it's the OS that does the check before booting to Download Mode and bypassing Download Mode's check.
Why is this important? Because when converting from one phone to another (Say, an H915 to a US996 like we do below), you initially can't flash the KDZ using LGUP's "Upgrade" function. You can only use "Partition DL" to replace the contents of partitions with the contents of the KDZ. This kind of works, but ends up with a phone that will sometimes identify as a H915 (in Download Mode) but sometimes identify as a US996 (in the OS). To clean it up, once you've done the Partition DL method, you can do it again from the OS and use the Upgrade method to get a really clean install.
It works going back the other way as well when you want to return to stock.
If this doesn't make sense, don't worry. You don't need to fully understand it to follow the instructions below, I just found it to be interesting info that didn't seem to appear in other threads.
Process Overview
Revert the phone to an old/vulnerable stock Nougat ROM for Videotron/Freedom Mobile
Enable Dev Options
Dump contents of US996 KDZ partitions over top of existing partitions
Cleanup by re-flashing US996 KDZ partitions over top of existing partitions
Transfer files to the SDCard and install Terminal Emulator
Unlock the Bootloader using the DirtySanta exploit
Boot to old TWRP and install new TWRP
Boot to new TWRP, install LineageOS, Google Apps, and flash modem partition image
Reboot to LineageOS
Actual Process
1 - Revert the phone to an old/vulnerable stock Nougat ROM for Videotron/Freedom Mobile
We need to be on Nougat for this to work, so if you're on Oreo you have to downgrade to Nougat before we begin. I chose a Nougat ROM for the H915 that's vulnerable to the DirtySanta exploit because I know it works and because I'm hoping in the future to be able to skip converting the phone to a US996 if possible.
Boot phone into Download Mode
Launch LGUP with Patch
Select "Upgrade" radio button
Select bin file : H91510e_00_VTR_CA_OP_1205.kdz
Click Start
When finished phone will reboot
1.5 - Do this if Step 1 Failed... Otherwise continue to Step 2
Depending on what's loaded on your phone when you start, it might complain about doing Step 1. This should allow us to bypass the issue and allow Step 1 to work. You can use this step if you've already converted the phone to another model as long as it's not bricked.
Boot phone into download mode
Launch LGIP with Patch
Select "PartitionDL" radio button
Select bin file : H91510e_00_VTR_CA_OP_1205.kdz
Click Start
Click the "Select All" partitions checkbox and click OK. When done it will reboot.
If it hangs or loops on reboot, boot into "Recovery Mode" (which at this point will Factory Reset the OS)
The phone boots into the OS
Quickly go through setup wizard. Skip as many things as possible.
Go Settings - General - About Phone - Software Info - Make sure it identifies as H91510e
Change the USB Option mode to "File Transfer"
Then repeat Step 1, but from inside the OS instead of in Download Mode
2 - Enable Dev Options and File Transfer Mode
We need these enabled after every time we flash the OS so that our LGUP and adb commands will work. You'll get used to doing these steps a bunch.
Quickly go through setup wizard. Skip as many things as possible.
Unplug USB-C cable
Swipe down from the top and change from USB Charging mode to File Transfer mode
Settings - General - About Phone - Software Info
Tap on Build Number many times until it unlocks Developer Mode
Go back 2 menus and enter the new "Developer Options" menus
Make sure "Enable OEM Unlock" is enabled
Enable "USB Debugging" (will be greyed out if USB-C cable is still attached)
Go back to main screen
Plug USB-C cable back in.
A pop-up will appear asking to Allow USB Debugging. Check the "Always Allow" box and tap OK
3 - Dump contents of US996 KDZ partitions over top of existing partition
The Videotron/Freedom KDZ has no Bootloader/Fastboot mode. If you try to enter bootloader mode you'll just end up charging the battery. So we have to cross-flash the US996 KDZ to get a phone with a bootloader which we can then replace with the engineering version using the DirtySanta exploit.
Boot phone into download mode
Launch LGUP with Patch
Select "PartitionDL" radio button
Select bin file : US99610f_00_1205.kdz
Click Start
Click the "Select All" partitions checkbox and click OK
When the phone boots back into the OS, repeat all of Step 2.
Note: If it asks for a password on startup, follow the "Boot to Recovery" steps and since
we don't have anything loaded in the recovery partition it will wipe/erase the phone
and remove the password.
4 - Cleanup by re-flashing US996 KDZ partitions over top of existing partitions
As mentioned in the "Note about flashing KDZ files using LGUP" section above, after you use the PartitionDL method you get a kind of dirty phone image that doesn't always identify as its new model. To clean up, we repeat the process in Upgrade Mode, taking advantage of the fact that at least the OS now identifies as US996 even if Download Mode doesn't. After this, Download Mode will also identify as US996.
Starting booted into the OS with a USB-C cable attached (File Transfer mode, USB Debugging on):
Launch LGUP with Patch
Select "Upgrade" radio button
Select bin file : US99610f_00_1205.kdz
Click Start
When the phone boots back into the OS, repeat all of Step 2.
5 - Transfer files to the SDCard and install Terminal Emulator
We will need some files on the SDCard in the phone in order to install them, either inside the OS (in the case of Terminal Emulator), or later on from TWRP. The Terminal Emulator will be used for the DirtySanta exploit so we need to get that installed now.
Make sure the USB Connection is set to Data Transfer mode and copy the following files to the SDCard:
APK for Terminal Emulator
twrp-3.5.1_9-0-us996.img
h915freedommobilemodem.img
Enable installing apps from unknown sources by:
Settings - General - Fingerprints and Security - Unknown sources (turn it On)
Install Terminal Emulator:
Tools - File Manager
Choose "Allow" when prompted
Click the up-arrow next to "Internal Storage"
Choose SD Card
Scroll down and tap on jackpal.androidterm-1.0.70-71-minAPI4.apk
Install
6 - Unlock the Bootloader using the DirtySanta exploit
The US996 KDZ has a bootloader but it's locked. In order to unlock it we need to use the DirtySanta exploit to give us permissions to replace the Bootloader/Fastboot with a leaked engineering version.
Starting booted into the OS with a USB-C cable attached (File Transfer mode, USB Debugging on):
Settings - General - About Phone - Software Info
Verify that Software Version lists as US99610f
Copy the twrp-3.0.2-1-us996.img file into the folder containing the LG V20 Root Package
Open a command prompt window and change to the folder containing the LG V20 Root Package and run "Step1.bat"
It will push multiple files to the phone and apply some patches/exploits.
This proces will take 5 minutes and put you out at an "elsa:/ $" prompt
At this "elsa:/ $" prompt in your command prompt window type the following:
run-as con
chmod 0777 /storage/emulated/0/*
On the phone, launch Terminal Emulator and run the following:
id
Verify that the string which comes back contains the string "context-u:r:untrusted_app".
If not, run Step1.bat again, else continue forward
Enter the follosing command into Terminal Emulator (be very careful to type it properly):
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
If that command came back with an error, close and re-open Terminal Emulator and try again
The command should begin to patch another file. This will take 5 minutes and will return you to the "elsa:/ $" prompt in Terminal Emulator when it has finished
Open another command prompt to the same folder and run "Step2.bat"
This step will download backup copies of the boot and aboot partitions from the phone then boot the phone into bootloader/fastboot mode.
You'll know it worked if the first line at the top of the phone screen appears in red
In the command prompt window, run Step3.bat
It will flash boot1.img and the TWRP Recovery image multiple times then restart the phone
The phone will hang, no matter how long it's left. Wait 5 minutes (at least until the logo re-loads once) then do the following:
Unplug the USB-C cable
Remove the battery from the phone to turn it off
Replace the battery
Boot into Fastboot mode and run the following commands in your command prompt:
fastboot flash boot bootbackup.img
Remove the USB-C cable and battery to turn off the phone. Then replace the battery and enter Recovery Mode
The phone will show a big red exclamation mark saying "Your device is corrupt". This is normal. It will go away after a few seconds then boot into recovery. This error screen is the result of the engineering "aboot" image that was flashed to give us an unlocked bootloader and will always happen on boot.
7 - Boot to old TWRP and install new TWRP
The old version of TWRP recovery will load. Don't ask me why we can't just go straight to new TWRP above, it didn't work well when I tried it.
If it asks for a password to decrypt data, click Cancel
Swipe to allow modifications
Install - Select Storage - MicroSD Card - OK
Install Image - Scroll down and tap the "twrp-3.5.1_9-0-us996.img"
Select the Recovery partition and swipe to confirm flash
Back to main menu
Reboot - Recovery
8 - Boot to new TWRP, install LineageOS, Google Apps, and flash modem partition image
The new version of TWRP will load:
Check the "Never show this screen during boot again" box
Swipe to allow modifications
Wipe - Format Data - type "yes" to continue
This is likely to fail the first time. Repeat it to properly format the data partition.
Go back to Main Menu - Wipe - Advanced Wipe - Select "Dalvik / ART Cache", "System", and "Cache"
Swipe to wipe
Back to main menu
Advanced - ADB Sideload
Plug in USB-C cable
Swipe to start sideload
In command prompt window on PC type the following:
adb sideload lineage-18.1-20210506-nightly-h910-signed.zip
When complete tap "back" and "ADB Sideload" and swipe again to apply another file:
adb sideload MindTheGapps-11.0.0-arm64-20210412_124247.zip
If you want to root the phone (completely optional, not necessary for this process), now is the time to do it. Tap "back" and "ADB Sideload" and swipe again to apply another file:
adb sideload Magisk-v23.zip
Go back to main menu - Install - Install Image - tap the h915freedommobilemodem.img file
Select the Modem partition and swipe to confirm flash
Remove USB-C cable
9. Reboot to LineageOS
Go back to main menu - Reboot - System - Swipe to reboot
References where I got the info to make this tutorial
Official Lineage 18.1 for LG V20 Release Thread
LineageOS Wiki for H910
DirtySanta Bootloader Unlock and Root Guide (Original)
H910 Rooting Thread (Cross-flash H915 then DirtySanta to US996)
H915 Root, TWRP using DirtySanta [WorkingSignals]
Noob Friendly Root TWRP using DirtySanta
General info about Modem Hardware, Firmware, Radio Interface Layer
[Reserved]
thank you so much. i need it
Great job for writing a complete how-to guide!
Thank You, You saved my old V20 H915
hi have you been able to find a better modem?
btw i'm not able to decrypt under twrp, can you?
Just want to confirm, it's only guide wich works for me. But I have issues with modem:
1. When I tried to change mode of modem, "prefered network type", phone stayed in the loop of the kernel panic "modem crash"
2. It were difficult to revert changes back. Finally, safe mode (in order to get it, you need to press volume up and volume down in the same time, during LinageOS booting process) helped me - when I disabled airplan mode, I had 2-10 seconds until next kernel panic. And in ~10 attempts, I were able to finally switch modem's mode to GSM/WDCMA/LTE
3. I used this phone 3 days, and once the kernel panic (because of modem) happened again
Any ideas what to do with modem? Also, the picture "Your phone is corrupt" is not fan Any ideas how to change it?
I did my best to follow all the instructions but after step 7's reboot I just get blocks full of static. I can tell it's trying to do fresh install setup though from what's peeking through the blocks.
Riot54 said:
I did my best to follow all the instructions but after step 7's reboot I just get blocks full of static. I can tell it's trying to do fresh install setup though from what's peeking through the blocks.
Click to expand...
Click to collapse
This is normal. Flash a kernel that's patched for dirty santa OR, cover the proximity sensor on boot and keep it covered until boot is complete.
That worked, thanks.
After multiple attempts going back and forth with step 6, I finally did it! I might switch to Lighthouse or Arros but I wouldn't have gotten this far without your guide.
Related
I'm looking to do this later today. I've done quite a bit of reading and would like a confirmation (or correction) on the steps I plan to do.
Goal:
Upgrade my Note 4 (n910v) from Android 5.0.1 to use an NSeven rom.
Here is my phone information:
Model: SM-N910V
Android Version: 5.0.1
Baseband: N910VVRU2BOG5
USA carrier - changing from Verizon service to TMobile
My current plan:
Use Odin 3 to upgrade from N910VVRU2BOG5 to N910VVRU2BPA1 using the full firmware here. Is this guide adequate for the manual update?
Once upgrade to 5.1.1, I want to root and unlock the bootloader using this guide.
After that, I want to update the rom to NSeven using the guide here.
Questions:
Are there any issues with the steps above?
Are the guides adequate? Or are the other ones preferred?
Do I need to flash to Android 6.0.1 after rooting & unlocking the bootloader prior to using NSeven?
Thank you for taking the time to read and hopefully reply. I just want to be sure I have the right idea before I get started.
Sorry to bump this, but any chance someone has time for a response?
Bllur said:
I'm looking to do this later today. I've done quite a bit of reading and would like a confirmation (or correction) on the steps I plan to do.
Goal:
Upgrade my Note 4 (n910v) from Android 5.0.1 to use an NSeven rom.
Here is my phone information:
Model: SM-N910V
Android Version: 5.0.1
Baseband: N910VVRU2BOG5
USA carrier - changing from Verizon service to TMobile
My current plan:
Use Odin 3 to upgrade from N910VVRU2BOG5 to N910VVRU2BPA1 using the full firmware here. Is this guide adequate for the manual update?
Once upgrade to 5.1.1, I want to root and unlock the bootloader using this guide.
After that, I want to update the rom to NSeven using the guide here.
Questions:
Are there any issues with the steps above?
Are the guides adequate? Or are the other ones preferred?
Do I need to flash to Android 6.0.1 after rooting & unlocking the bootloader prior to using NSeven?
Thank you for taking the time to read and hopefully reply. I just want to be sure I have the right idea before I get started.
Click to expand...
Click to collapse
OK. I don't know about those steps, as I took a different route to get to the Nseven rom. Make sure you have the ADB/Odin 3.09 or 3.10 and Samsung drivers already installed on your PC. You might want to get/DL Kingroot.apk aswell.
Step 1.
Download the 5.1.1 BPA1 full firmware, this should be a all in one file. None of these separate files eg.BL AP CSC..
"I downloaded this from Sammobile"
Step 2.
Open Odin and add the firmware file to the AP tab by clicking on it and navigating to where file is located. This takes a little while to show as Odin checks the file before adding it( Make sure Auto reboot and F.Reset Time are ticked)
Step 3.
Make sure you have unlocked "DEVELOPER MODE" and "USB DEBUGGING" is ticked before powering down your phone and putting it into download mode by holding the 3 keys Vol Down,Power,Home then Vol Up to continue, once your in DL mode connect to PC. There may be a little pause as your PC may install further driver files before Odin recognizes you phone and adds it under "ID;COM". Once your phone has been added into the ID:COM you can go ahead and press START. Allow Odin to do its stuff and once your phone reboots you can unplug from the PC.
Now you should be on the 5.1.1 BPA1 firmware.
Allow your phone to boot completely, you can skip the whole setup process but you'll need to be connected to WiFi for the next process.
GAINING TEMP ROOT.
Step 1.
Transfer the "KINGROOT.APK" to your phone and install but don't open it yet.
Step 2.
Unlock Developer Mode again and tick USB DEBUGGING. * This is necessary for ADB.
Step 3.
Open Kingroot and allow it to check for root this can take awhile just be patient. Once it throws up the results it'll ask if you want to try "TRY TO ROOT". click on the tab and watch the process. " Your phone will reboot a few times during the process" I just reopened Kingroot each time it did until the process was done. ******You'll have to repeat this process again***** as your Phone reboots while your pushing the command file through ADB. Losing root in the process.
Now that you've repeated the process again and you have gained TEMP root. You can confirm this with "ROOT Checker" you can reconnect your phone to your PC.
Step 4.
Make sure you have the "Samsung_unlock_n4-fix script file in your FASTBOOT folder located in the extracted files of ADB.
Now open a ADB command window *Open this in the same folder where you exacted ADB. to do this hold Shift and click Right mouse button on any clear area of the ADB folder and scroll down to "Open command window here"
Step 5.
Within the command window type "CD Fastboot"
To confirm your device is added type" ADB devices"
You should see a random number listed under "List of devices"
If you do your set to go.
For this next step its best you have the Notepad open with these commands to make it easier. ****COPY & PASTE*****
The commands are.....* without the numbers in front of it
#1. adb push samsung_unlock_n4-fix
#2. adb shell
#3. su
#4. cd/data/tmp/
#5. chmod 777 samsung_unlock_n4-fix
#6. chown root. root samsung_unlock_n4-fix
#7. . / samsung_unlock_n4-fix
OK time to push the file. Start with the 1st command and press enter. Then the 2nd and press enter. Then the 3rd and press enter. Then the 4th, then the 5th and 6th then the 7th.
Now once you've enter the 7th command you'll be presented with a warning just type YES ****USING THE SHIFT KEY WHILE DO SO****** and wait while the process completes. Your phone will reboot to confirm the process is complete.
******NOTE*******
Your phone will reboot but reboot into a Bootloop, don't worry just pull the battery and memory card. Replace the battery but not the memory card. Reboot into DL mode to confirm that you are now in/a Developer Mode.
**********CONGRATULATIONS YOU JUST UNLOCKED THE BOOTLOADER********
*****NOW HERE COMES THE STINK PART*******
You'll need to flash the N910VVRU2BPA1_N910VVRU2CPD1 full firmware with Odin this will update the Bootloader to CPD1 required for Nseven to boot. But in doing so will LOCK the bootloader again. ARRRGGGGG!!!!!!
So.....
Step 1.
Put your newly unlocked phone into DL mode again and reconnect to Odin.
Step 2.
Place the BPA1/CPD1 firmware into the AP slot and press start
Disconnect when the phone reboots. Allow it to fully boot/skip the setup process. ******Note you will need Mobile Data as WiFi is non usable due to the updated firmware.
Step 3.
Reformat your memory card using your PC and place back into your phone, reconnect your phone to PC and transfer ROOTKING.APK over again.
Step 4.
Turn on Mobile data. Install KINGROOT and open, follow the same process you did to unlock 5.1.1. This time it may take a little longer and there's a chance Kingroot will fail to root just try again.
*It did it to me.
*There's a chance your phone will reboot when it comes to pushing the command file, unfortunately that's just the way it is. Just repeat the Kingroot process again.
Step 5.
Now that you've gained TEMP ROOT again, You'll need to run ADB and push the scripts again. Just follow the same process you did for 5.1.1 BPA1.
Even down to pulling the Batt & Memory card.
Step 6.
Now that the bootloader is unlocked, place phone into DL mode and reconnect to PC and Odin. Now again AP slot navigate to where you placed your Custom recovery.
****NOTE. I used TWRP 2.8.7.0 trltevzv.img as TWRP 3.0.2.0 Didn't work for me. And flash disconnecting when phone reboots.
********Congrats you now have a UNLOCKED BOOTLOADER and a CUSTOM RECOVERY on 5.1.1 with a CPD1 bootloader.
Time to flash Nseven. *don't forget to reformat your memory card.
To flash Nseven, just copy over the Nseven zip file to your memory card and flash using TWRP.......ENJOY.
* Note. I didn't flash anything else apart from the CPL1 Nseven
Even though I had all the files DL. Just follow the Nseven forum if you experience any problems.
Hope this helps getting you into/onto Nseven.
hi folks,
tomorow should be getting my hands on the Ulephone power 2.
its the 5.5 screen 4gb ram 64gb rom.
all looks good until i have seen that the normal duel sim is one is hybrid for sdcard which is the norm right,
ant
but............
usually its sim 1 is for 4g cards and the hybrid is for 2g/3g/sdcard. yeah?
well the power 2 looks like its sim slot 1 is a 2g/3g slot and the hybrid is 4g or sdcard??????????
so will have to choose 4g or sdcard??? that cant be right?
I don't try this device with sim.
I know you can use the older power (1) have a sim 4g and SD card
So i believe the power 2 have the same method.
My first steps: How to root this device? i don't find a twrp.
I try to root with kingroot kingoroot, no results
Please?
The power 2 is the same as the power wrt the sim/memory card tray; both sim slots support 4g, but only one at a time. So if you put two 4g sims in, only one of them will have 4g (you choose which one), with a sim and a memory card the 4g should default to the inserted sim, but you might have to check this in settings.
Received my power 2 a couple of weeks ago after having it on pre-order for a month and I love it (sold the original power towards the cost).
I haven't tried rooting it yet, but was thinking of trying to flash twrp for the original power and seeing if that works. The great thing about these phones is that they're very hard to brick as you can always flash them as long as they still switch on.
Slàinte
mmidders
Hello my friends. I just bought the ulefone power 2 and i try to root it. Can anyone help me pls ???
mmidders said:
The power 2 is the same as the power wrt the sim/memory card tray; both sim slots support 4g, but only one at a time. So if you put two 4g sims in, only one of them will have 4g (you choose which one), with a sim and a memory card the 4g should default to the inserted sim, but you might have to check this in settings.
Received my power 2 a couple of weeks ago after having it on pre-order for a month and I love it (sold the original power towards the cost).
I haven't tried rooting it yet, but was thinking of trying to flash twrp for the original power and seeing if that works. The great thing about these phones is that they're very hard to brick as you can always flash them as long as they still switch on.
Slàinte
mmidders
Click to expand...
Click to collapse
I'm sure it's not working the twrp from the power (1).
If you have troubles with bootloops you can flash again the facatory rom and SP flash tools.
Press the power volume + and - and SP flash tools gonna flash.
The only way is to made a twrp from the k6000 http://fvknl.pro/k6000-plus-root-guide/
I don't know how, that device is almost the same...
There has been 2 ulefone Updates since launch
Android 8.0 is scheduled for end of the year.
Updates are fine, who can create a TWRP? So we can finally root the device
geheimke said:
Updates are fine, who can create a TWRP? So we can finally root the device
Click to expand...
Click to collapse
up
TWRP please!
Not so easy to do it. It will take very long time to port or build twrp
It sucks that power 2 still doesn't have root or twrp. I refuse to touch unrooted phones. I just received it as gift. I will keep it in a drawer and check next month or so.
I find that it lacks optimisation, kinda laggy in 3D/games ..
On Antutu, scores is 44000. I tested a galaxy S5 of a friend, it was 72000. For a phone that is several years older than Power 2.
I understand that it comes not with high end cpu/gpu but still..
I will copy my post from needrom website.
I have successfully rooted my two Power 2 phones. I had to port the TWRP recovery from Oukitel k6000 plus using Carliv Image Kitchen and following some online tutorials.
The only issue is, TWRP is semi functional, that is, touch doesn't work. I had to connect a mouse to my phone via OTG usb port and using some dongle to make USB smaller to fit the port. Also it comes with Russian language as default, but can be changed to English or any other as the original TWRP from Oukitel k6000+ (3rd button from second column, then click on Globe tab at the top right then choose English and the only button at the bottom to accept the change).
I am trying to fix this with no luck so far. But at least I am rooted and I was able to flash "SR1-SuperSU-v2.82-SR1-20170608224931.zip" which is the latest as of writing this. SuperSu functions properly and I am able to use AdAway.
If anyone is interested in the recovery image, I will post it. I flashed it using fastboot though after unlocking the bootloader using "fastboot oem unlock"
Click to expand...
Click to collapse
Rebel_X said:
I will copy my post from needrom website.
Click to expand...
Click to collapse
I would very much like to give this a go with my ulefone power 2!
Here you go, TWRP for Ulefone Power 2
What you need to do before you start flashing:
0) You need to have ADB installed on your computer, if you have Windows, the easiest way is by using 15 Seconds ADB Installer v1.4.3.
1) Your bootloader must be unlocked, otherwise flashing recovery will fail using fastboot command. PLEASE NOTE: When unlocking the bootloader, your phone will do a factory reset automatically, so backup all your important files beforehand.
To unlock the bootloader:
a) Go to Settings -> About Phone -> Build number (tap on it 7 times to unlock Developer Options) -> Tap on back to Settings menu then Developer Options.
b) Now move the slider for "OEM Unlocking" to enable it, say yes to the warning message.
c) Enable "USB Debugging"
d) Connect your phone to your computer via USB cable, say Yes for the dialog on your phone to trust your computer for debugging using USB.
e) Run command prompt and type
Code:
adb reboot bootloader
Then press enter
f) Once in bootloader, type
Code:
fastboot oem unlock
Then press Volume UP on your phone to allow OEM Unlock. It shouldn't take long, just few seconds and a message will appear on command prompt saying success or OK.
g) Type
Code:
fastboot reboot
To reboot your phone, it might reboot twice, it will do a factory reset and you will have to "Enable Developer Options and USB Debugging" again. As a side note, you will also notice that OEM Unlocking is grayed out. It will remain like that unless you do "fastboot oem lock" or erase the entire phone (might erase imei, but can be restored using SN Writer Tool) and/or flash bootloader using SP_FLASH_TOOL, but I digress.
2) Before you flash TWRP recovery, you must have SuperSu zip file on your phone beforehand, otherwise, your phone will not boot to Android. It has to do with something about the original TWRP for Oukitel k6000+, since the author of that TWRP port said so in the instructions about how to flash the recovery.
So download SR1-SuperSU-v2.82-SR1-20170608224931.zip from this link or the original SuperSu thread on XDA, and copy the file into your phone, say inside the Download folder in the internal memory of your phone.
3) Open command prompt again if it is not already open, type
Code:
adb reboot bootloader
4) Once in bootloader, type
Code:
fastboot flash recovery C:\TWRP-recovery-20170618-1340.img
Note: You replace the path for the TWRP recovery to where you have the file, to make it easier, just put it in the root of C drive.
Also, if you don't already know, while in command prompt, you can type C:\TWRP then press TAB to auto-complete the file name for you, so you don't have to type lengthy file names. Keep pressing TAB to cycle between similar occurrences, that is, if you have more than one file that their names start with TWRP
5) Press power button until phone shuts down. Then press Volume UP + Power and keep holding until you see super tiny text with 3 options to cycle between. Release your fingers from Volume Up + Power, then cycle between the options using Volume Up only, choose "RECOVERY" which is the first in the menu, then press Volume DOWN to select.
6) Wait a few seconds, you will be inside TWRP, connect your phone with a mouse since touch doesn't work here. Once you do, you will see a mouse pointer appear. I used a wireless mouse with bluetooth dongle, with an adapter to change USB port size.
7) Slide the slider to the right, to enable modifications to System partition. Don't press anything else, unless you know Russian, I don't .
8) To change the language to English or your own language, click on the third button of the second column. Then click on the Globe tab on the top right corner, change language, then press the only button at the bottom to accept. Language of the UI is changed.
9) Click "Install", browse for the SuperSu zip file you have downloaded to your phone, for example inside the Download folder. And then select it.
10) Slide to the right to flash SuperSu.
11) From the TWRP menus, you can reboot your phone.
12) Enjoy your rooted Power 2 phone. :good:
---------- Post added at 04:47 AM ---------- Previous post was at 04:47 AM ----------
alpsayin said:
I would very much like to give this a go with my ulefone power 2!
Click to expand...
Click to collapse
Check the post above :good:
hello , i got a ulefone power 2 but unfortunately its not powering on. As i am from india and returning or replacing is costly and timetaking process, i need you guys to help me. I tried to flash it with software available on the website but stuck. I need some checksum.ini file which is not there in the firmware file provided. So anyone please help me. the phone doesnt even show the ulefone logo. i can just see the charging percentage when the charger is connected, then keeping it connected i tried to turn on but didnt work. keeping the charger connected ,after some time the display goes off and no mater how long you press the power button , the display doesnt show up. I can only see the notification bulb.
Soft bricked :laugh: trying to recover the phone, official ulefone guide is useless. Getting some error about a missing checksum.ini file. Will keep this thread updated
All went well until step 9, where I realised factory reset deleted the supersu zip. So I tried to reboot into system to download it again. It never booted. Doesnt even go into adb mode.
Fastboot mode and TWRP intact (TWRP needs a mouse). I was able to flash original recovery via fastboot, getting "cannot load system.img" error when I try to flash system (it appears I might need to update my adb/fastboot version).
UPDATE: was able to flash the stock rom. And tried to follow the guide again, and faced the same symptoms. If i have working TWRP, then the system doesnt boot. And vice-versa. Will keep updated, i'm a persistent mf
Rebel_X said:
Here you go, TWRP for Ulefone Power 2
What you need to do before you start flashing:
0) You need to have ADB installed on your computer, if you have Windows, the easiest way is by using 15 Seconds ADB Installer v1.4.3.
1) Your bootloader must be unlocked, otherwise flashing recovery will fail using fastboot command. PLEASE NOTE: When unlocking the bootloader, your phone will do a factory reset automatically, so backup all your important files beforehand.
To unlock the bootloader:
a) Go to Settings -> About Phone -> Build number (tap on it 7 times to unlock Developer Options) -> Tap on back to Settings menu then Developer Options.
b) Now move the slider for "OEM Unlocking" to enable it, say yes to the warning message.
c) Enable "USB Debugging"
d) Connect your phone to your computer via USB cable, say Yes for the dialog on your phone to trust your computer for debugging using USB.
e) Run command prompt and type
Code:
adb reboot bootloader
Then press enter
f) Once in bootloader, type
Code:
fastboot oem unlock
Then press Volume UP on your phone to allow OEM Unlock. It shouldn't take long, just few seconds and a message will appear on command prompt saying success or OK.
g) Type
Code:
fastboot reboot
To reboot your phone, it might reboot twice, it will do a factory reset and you will have to "Enable Developer Options and USB Debugging" again. As a side note, you will also notice that OEM Unlocking is grayed out. It will remain like that unless you do "fastboot oem lock" or erase the entire phone (might erase imei, but can be restored using SN Writer Tool) and/or flash bootloader using SP_FLASH_TOOL, but I digress.
2) Before you flash TWRP recovery, you must have SuperSu zip file on your phone beforehand, otherwise, your phone will not boot to Android. It has to do with something about the original TWRP for Oukitel k6000+, since the author of that TWRP port said so in the instructions about how to flash the recovery.
So download SR1-SuperSU-v2.82-SR1-20170608224931.zip from this link or the original SuperSu thread on XDA, and copy the file into your phone, say inside the Download folder in the internal memory of your phone.
3) Open command prompt again if it is not already open, type
Code:
adb reboot bootloader
4) Once in bootloader, type
Code:
fastboot flash recovery C:\TWRP-recovery-20170618-1340.img
Note: You replace the path for the TWRP recovery to where you have the file, to make it easier, just put it in the root of C drive.
Also, if you don't already know, while in command prompt, you can type C:\TWRP then press TAB to auto-complete the file name for you, so you don't have to type lengthy file names. Keep pressing TAB to cycle between similar occurrences, that is, if you have more than one file that their names start with TWRP
5) Press power button until phone shuts down. Then press Volume UP + Power and keep holding until you see super tiny text with 3 options to cycle between. Release your fingers from Volume Up + Power, then cycle between the options using Volume Up only, choose "RECOVERY" which is the first in the menu, then press Volume DOWN to select.
6) Wait a few seconds, you will be inside TWRP, connect your phone with a mouse since touch doesn't work here. Once you do, you will see a mouse pointer appear. I used a wireless mouse with bluetooth dongle, with an adapter to change USB port size.
7) Slide the slider to the right, to enable modifications to System partition. Don't press anything else, unless you know Russian, I don't .
8) To change the language to English or your own language, click on the third button of the second column. Then click on the Globe tab on the top right corner, change language, then press the only button at the bottom to accept. Language of the UI is changed.
9) Click "Install", browse for the SuperSu zip file you have downloaded to your phone, for example inside the Download folder. And then select it.
10) Slide to the right to flash SuperSu.
11) From the TWRP menus, you can reboot your phone.
12) Enjoy your rooted Power 2 phone. :good:
---------- Post added at 04:47 AM ---------- Previous post was at 04:47 AM ----------
Check the post above :good:
Click to expand...
Click to collapse
mbs.yaswanth said:
hello , i got a ulefone power 2 but unfortunately its not powering on. As i am from india and returning or replacing is costly and timetaking process, i need you guys to help me. I tried to flash it with software available on the website but stuck. I need some checksum.ini file which is not there in the firmware file provided. So anyone please help me. the phone doesnt even show the ulefone logo. i can just see the charging percentage when the charger is connected, then keeping it connected i tried to turn on but didnt work. keeping the charger connected ,after some time the display goes off and no mater how long you press the power button , the display doesnt show up. I can only see the notification bulb.
Click to expand...
Click to collapse
Yeah, I had the same issue with the software that comes from Ulefone, it was asking for Checksum Generator that I have to download separately, it was like 150kb stand alone executable, you put it in the same folder of your stock ROM and wait forever for it to build the Checksum, which unfortunately didn't work since it complains about multiple RECOVRY images. So scratch that.
What you need to do, is as I did, download SP FLASH TOOL, it works great, no shinanigans or bullsh!t. It flashed the stock ROM in less than 2 minutes (around 1:30 seconds, to be exact) and revived my phone. There are plenty of youtube tutorials on how to use it. It is easy, just load the scatter file, for the other file, you can use the same all in one mtk file that comes with SP FLash Tool (I did this) or use the one from your STOCK ROM.
I hope that helps :good:
---------- Post added at 02:33 PM ---------- Previous post was at 02:27 PM ----------
alpsayin said:
Soft bricked :laugh: trying to recover the phone, official ulefone guide is useless. Getting some error about a missing checksum.ini file. Will keep this thread updated
All went well until step 9, where I realised factory reset deleted the supersu zip. So I tried to reboot into system to download it again. It never booted. Doesnt even go into adb mode.
Fastboot mode and TWRP intact (TWRP needs a mouse). I was able to flash original recovery via fastboot, getting "cannot load system.img" error when I try to flash system (it appears I might need to update my adb/fastboot version).
UPDATE: was able to flash the stock rom. And tried to follow the guide again, and faced the same symptoms. If i have working TWRP, then the system doesnt boot. And vice-versa. Will keep updated, i'm a persistent mf
Click to expand...
Click to collapse
All I can think of, you did something wrong. Initially, while I was trying to port TWRP, I had the same issue, I was trying to save some steps by flashing the recovery after I unlocked the bootloader without rebooting, the result was TWRP was not able to see any partitions.
Flash Stock-ROM and redo the steps. If you flash the preloader you might have to OEM Unlock your phone again.
I mentioned that if you "do not flash SuperSu, the system will NOT boot to Android". Also mentioned that after you unlock the bootloader, you have to RE-ENABLE USB Debugging, and while you are at it, check to see if your bootloader is unlocked inside Developer Options.
Edit: BTW, try not to unlock the bootloader if it is already unlocked. If it is unlocked, then skip the steps for unlocking the bootloader. It might cause an issue.
These are the steps I used to flash TWRP and I was able to flash SuperSu, all rooted apps are working fine, AdAway, Lucky Patcher...etc!
This:
Rebel_X said:
Here you go, TWRP for Ulefone Power 2
2) Before you flash TWRP recovery, you must have SuperSu zip file on your phone beforehand, otherwise, your phone will not boot to Android. It has to do with something about the original TWRP for Oukitel k6000+, since the author of that TWRP port said so in the instructions about how to flash the recovery.
Click to expand...
Click to collapse
And this combined:
Rebel_X said:
Here you go, TWRP for Ulefone Power 2
9) Click "Install", browse for the SuperSu zip file you have downloaded to your phone, for example inside the Download folder. And then select it.
Click to expand...
Click to collapse
Apparently if you dont flash the supersu first time you go into TWRP then it gets messy. Got the root working now. Thank you for the help and of course for the TWRP build!
Also if anyone's wondering it's possible to restore the system via fastboot. Extract the rom zip (can be downloaded from http:/ulefone.com/download/power2.html ) and flash boot, recovery and system;
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
link for sp flash tool u used.
Rebel_X said:
Yeah, I had the same issue with the software that comes from Ulefone, it was asking for Checksum Generator that I have to download separately, it was like 150kb stand alone executable, you put it in the same folder of your stock ROM and wait forever for it to build the Checksum, which unfortunately didn't work since it complains about multiple RECOVRY images. So scratch that.
What you need to do, is as I did, download SP FLASH TOOL, it works great, no shinanigans or bullsh!t. It flashed the stock ROM in less than 2 minutes (around 1:30 seconds, to be exact) and revived my phone. There are plenty of youtube tutorials on how to use it. It is easy, just load the scatter file, for the other file, you can use the same all in one mtk file that comes with SP FLash Tool (I did this) or use the one from your STOCK ROM.
I hope that helps :good:
---------- Post added at 02:33 PM ---------- Previous post was at 02:27 PM ----------
All I can think of, you did something wrong. Initially, while I was trying to port TWRP, I had the same issue, I was trying to save some steps by flashing the recovery after I unlocked the bootloader without rebooting, the result was TWRP was not able to see any partitions.
Flash Stock-ROM and redo the steps. If you flash the preloader you might have to OEM Unlock your phone again.
I mentioned that if you "do not flash SuperSu, the system will NOT boot to Android". Also mentioned that after you unlock the bootloader, you have to RE-ENABLE USB Debugging, and while you are at it, check to see if your bootloader is unlocked inside Developer Options.
Edit: BTW, try not to unlock the bootloader if it is already unlocked. If it is unlocked, then skip the steps for unlocking the bootloader. It might cause an issue.
These are the steps I used to flash TWRP and I was able to flash SuperSu, all rooted apps are working fine, AdAway, Lucky Patcher...etc!
Click to expand...
Click to collapse
ok what should i select there? formal all+download or download only or firmware upgarade???
There are a number of generic installation guides for custom roms eg https://www.xda-developers.com/how-to-install-custom-rom-android/
However this one is specifically for the LG G6 and tested using the US997 model. It worked for me, but I welcome comments on how to improve it.
Create a folder on the PC for all the downloads and files
Download phone driver from LG website
https://www.lg.com/us/support/help-library/lg-mobile-drivers-and-software-CT10000027-20150179827560
Download ADB/Fastboot https://developer.android.com/studio/releases/platform-tools (You need to unzip once downloaded)
(I had an error "adb server version (31) doesn't match this client (41) killing". I searched my PC and found an older version which I had used for another phone and deleted the folders and reinstalled from the download)
Ensure the phone is backing up. (Google backup is working, you have all your photos music etc downloaded) the next steps will wipe the phone
Remove the PIN/Password/Fingerprints from the phone so it will boot without any security.
Unlock the bootloader
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
The phone will then reboot and do a complete wipe so you need to wait a while for Android to setup.
Telegraph has the latest news on LG G6 ROMs and Recovery. From here I got the links for SHRP recovery which seems more up to date for LG G6 than TWRP. (https://web.telegram.org/#/[email protected])
https://sourceforge.net/projects/pa-g6/files/Releases/SHRP/20.07.2020/US997/
I named the downloaded file "recovery" (You need the .img file not the ZIP)
There are lots of active ROMS for LG G6 I have Lineage installed on another phone which works really well, but Havoc seems the most popular on the G6.
Download the ROM and Gapps https://opengapps.org/ (I used Nano, remember G6 is 64bit)
You will also need to update the bootloader. This was the latest I found for the US997
https://androidfilehost.com/?fid=1899786940962575226
(I missed the bootloader the first time and Gapps will not flash, I was helped by the LG G6 community on Telegram https://web.telegram.org/#/[email protected])
Now you have downloaded all you need
Then connect the phone to the PC and ensured you have ADB debug on in developer options and boot the phone into fastboot
On the PC open a command prompt in the folder you have all the files:
adb reboot bootloader
To load the recovery to the phone :
Fastboot flash recovery recovery.img
YOU MUST NOW BOOT DIRECTLY TO RECOVERY. Do not reboot to Android as this will automatically reset recovery to the stock version.
Unplug the USB cable and reboot to recovery (hold volume down + power button).. continue holding until phone reboots...
As soon as you see the LG logo on the screen.. let go of the power button then quickly press it again (never letting go of volume down).
Keep holding until you see the Factory Reset screen. Click thru the factory reset screens using the volume buttons to move up/down and power button to select. Choose "Yes" twice (saying you want to reset the phone it should boot into your new recovery. Despite what the screen says it won't actually factory reset/wipe your data... as long as you've installed a custom recovery and have not booted into Android since then.
Most likely you will be asked the password to decrypt the data folder. I tried my phone PIN and other default passwords suggested on the internet. I eventually found that this is a known issue and you need for cancel out of this screen and go and "FORMAT DATA"
Reboot directly to recovery (select reboot recovery in Skyhawk), this time you should not be asked for the decryption password.
I recommend you backup your current setup before making changes. If you hit issues you can use the recovery to restore. My SD card slot is broken (Poor LG design) so I plugged a USB thumb drive into the USB C slot and did a full backup. (No data since I just formatted it).
Wipe the partitions before you flash
Full wipe ("The only option you ever need")
Select Advanced and wipe system partition.
FLASH (You need to put the ZIP files either on the USB drive as I did, or copy to your SD card, or you can use ADB sideloader from the PC to push the files to the phone). The USB drive seems the easiest since you can plug it into your PC to load the files then plug it into the phone to read them.
Flash in the following order
Bootloader
ROM
Gapps
After Installing wipe cache and Davik
Reboot
It will do lots of processing while setting up. Ensure it stays cool (remove case and leave it plugged in with the screen off)
Donate to the developer of your new ROM at the end when it works.
I have been running my LG G6 on Android 10 for a few weeks and thought I would share my observations, I am using Havoc 3.7 installed with Skyhawk, I did not root the phone.
Likes : Very smooth experience, phone feel like it is running much faster. Very stable, I had one surprise reboot in the time I have used it. No issues (so far) with installing or using any apps including banking. Much lower use of storage, I have 6GB free.
Same : Battery life is about the same as before.
Gaps : Cannot encrypt, VOLTE doesn't work (which may become a big issue for T-Mobile and AT&T soon), when being used the phone gets much warmer than it did before and the wifi setting randomly turns off.
Next Steps: I am going to try Lineage which has released some fixes for the WIFI issue and report back.
I'm trying to follow the instructions as per this guide for the tmo version of G6 (H87220g) and I'm running into a roadblock on the recovery flash:
[[email protected] tmp]$ mkdir skyhawk
[[email protected] tmp]$ cd skyhawk && 7z x ../SHRP_v2.3.2_us997-233920072020.zip
[[email protected] skyhawk]$ fastboot flash recovery recovery.img
Sending 'recovery' (36936 KB) OKAY [ 1.252s]
Writing 'recovery' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
I downloaded the Skyhawk zip from the PA download link, unzipped it and used the recovery.img file found inside the zip as part of the fastboot command. Is this incorrect ?
Yes, you need the recovery.img file to flash via fastboot. Have you successfully unlocked the boot loader? You cannot replace recovery without unlocking.
You also need to ensure you have the appropriate files for your phone I have a US997 but as you have H872 you would need skyhawk for the H872 in the notes above you are still using US997.
bootloader is unlocked as per:
https://forum.xda-developers.com/tmobile-g6/how-to/unlock-bootloader-tmo-t3578099
fastboot flash is failing and I'm not the only one it seems like based on comments here and reddit...
I gonna try out @runningnak3d guide and see if that works...
This guide is for the US997. The H872 has a much more complicated process to install recovery : https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518
Well, ok..I have a huge problem.
I was in developer mode and it said i could switch my rom so i installed it and now my phone says "Your device is corrupt. It is not trusted and will not boot".
Any suggestions on how I can fix this?
Wow that can't be good. I'm new to the oneplus stuff, normally I would say boot into recovery and reflash to stock but since we do not have roms yet I have a feeling your going to have to take it back to tmobile or oneplus and exchange it.
He should still be able to recover it with a factory restore via the stock recovery. As far as I know (and I'm not an expert) a bad ROM flash doesn't touch the recovery partition.
from https://www.devicesfaq.com/en/reset/oneplus-nord-n200-5g
Restore with hard reset or Recovery mode OnePlus Nord N200 5GRestore with hard reset or Recovery mode your OnePlus Nord N200 5G can solve problems that have not been solved with a normal factory reset.
1- First turn off your OnePlus Nord N200 5G completely. If you can not unlock the screen, press and hold the power button for about 20 seconds and the phone will turn off.
2- Keep holding on volume down and power keys together for a few seconds in your OnePlus Nord N200 5G. In some devices according to the Android version the combination can be the power key and the volume key up.
3- When the OnePlus logo is displayed, release the buttons.
4- Move through the menu with the volume up and volume down keys until you reach the “Recovery Mode” option and press the power button to access.
If the device menu appears in Chinese characters, click here to see how to reset a mobile in Chinese
5- Use the volume up and volume down keys to select the “wipe cache partition” option and press the Power button to activate the option and clear the mobile cache.
6- After a few seconds you will return to the previous screen, with the volume buttons go to the option “wipe data / factory reset” and press the power button to enter. A screen with many NOes and a YES will appear, with the volume keys again go to the YES and press with the power key.
7- After finishing again with the volume keys, click on “reboot system now” and press the power key of your OnePlus Nord N200 5G, the device will reboot and take several minutes to start while restoring the device to its factory state and optimizing the applications pre-installed in the system Android 11, OxygenOS 11.
Click to expand...
Click to collapse
edale1 said:
He should still be able to recover it with a factory restore via the stock recovery. As far as I know (and I'm not an expert) a bad ROM flash doesn't touch the recovery partition.
from https://www.devicesfaq.com/en/reset/oneplus-nord-n200-5g
Click to expand...
Click to collapse
I can't even get into recovery. I can get into download mode but theres no way for me to restore it from that...
literally recovery mode is gone also. it's so weird, i did this from my phone's settings, it shouldn't have done this.
fogles2021 said:
I can't even get into recovery. I can get into download mode but theres no way for me to restore it from that...
literally recovery mode is gone also. it's so weird, i did this from my phone's settings, it shouldn't have done this.
Click to expand...
Click to collapse
phone off -> volume down + power (hold both in until phone's booted)
that doesn't work to get into recovery mode?
How about
volume up + volume down + power
to get into fastboot mode?
Can you connect via USB to run ADB commands?
edale1 said:
phone off -> volume down + power (hold both in until phone's booted)
that doesn't work to get into recovery mode?
How about
volume up + volume down + power
to get into fastboot mode?
Can you connect via USB to run ADB commands?
Click to expand...
Click to collapse
I can only boot into fastboot, recovery just boots back to "your device is corrupt'.
I can connect usb but i can't find drivers for the phone, its connect as QUSB.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
There's the USB drivers.
Selecting recovery from within fastboot mode brings up the corrupt message as well? Very odd.
I'm seeing 2 options then. Take the phone back to the store you got it at to see if they can fix/replace it; or wait for the ROM to be released.
edale1 said:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
There's the USB drivers.
Selecting recovery from within fastboot mode brings up the corrupt message as well? Very odd.
I'm seeing 2 options then. Take the phone back to the store you got it at to see if they can fix/replace it; or wait for the ROM to be released.
Click to expand...
Click to collapse
I've installed these and it still comes up as qusb bulk.
Yeah, selecting recovery from fastboot goes to corrupt message, too.
Just going to make a aservice request.
There was another report of this on the OnePlus forums a while ago, too, if I'm inferring what happened correctly: https://forums.oneplus.com/threads/...-the-oneplus-nord-n200.1460001/#post-23393026
The only real recourse right now is to submit a ticket as you've done and wait until you can send your device back and they send you a new one.
Once OnePlus releases a full stock ROM image, if they ever do, it will be possible to recover a bootloader-unlocked device from this state. But even then that won't work if you weren't bootloader unlocked beforezs the update.
---
While you've still got the device, though, could you try something for me? Could you install the android platform tools, see if you can get fastboot working on your computer, and try the fastboot command "fastboot set-active a"?
The Nord N200 5G is a A/B partitioned device, which means it has two of each system partition, one labeled "a" and one labeled "b". The update process is *supposed to* install all updates into the partition that you aren't currently using, then instruct the system to switch to it so it can update seamlessly.
I have no idea what went wrong in your update process, but if it did an incomplete update then instructed the system to use the other partition (and now for some reason doesn't switch back) this could help. I kind of doubt it will, since in my attempts at flashing bootloaders, if I put anything fully invalid in boot partition 'b', the phone automatically switches back to 'a' and boots into "safe mode".
But if for some reason it isn't corrupted enough to trigger that, maybe switching back to the "a" partition set could fix it. Or if you're already on "a", you could try switching to "b".
daboross said:
There was another report of this on the OnePlus forums a while ago, too, if I'm inferring what happened correctly: https://forums.oneplus.com/threads/...-the-oneplus-nord-n200.1460001/#post-23393026
The only real recourse right now is to submit a ticket as you've done and wait until you can send your device back and they send you a new one.
Once OnePlus releases a full stock ROM image, if they ever do, it will be possible to recover a bootloader-unlocked device from this state. But even then that won't work if you weren't bootloader unlocked beforezs the update.
---
While you've still got the device, though, could you try something for me? Could you install the android platform tools, see if you can get fastboot working on your computer, and try the fastboot command "fastboot set-active a"?
The Nord N200 5G is a A/B partitioned device, which means it has two of each system partition, one labeled "a" and one labeled "b". The update process is *supposed to* install all updates into the partition that you aren't currently using, then instruct the system to switch to it so it can update seamlessly.
I have no idea what went wrong in your update process, but if it did an incomplete update then instructed the system to use the other partition (and now for some reason doesn't switch back) this could help. I kind of doubt it will, since in my attempts at flashing bootloaders, if I put anything fully invalid in boot partition 'b', the phone automatically switches back to 'a' and boots into "safe mode".
But if for some reason it isn't corrupted enough to trigger that, maybe switching back to the "a" partition set could fix it. Or if you're already on "a", you could try switching to "b".
Click to expand...
Click to collapse
Can u give me a link to platform tools, also..my computer is detecting the phone as QUSB BULK:"
From one of my other threads:
------
USB DRIVERS
You may need to use the Google USB Driver from Android Studio to allow your PC to recognize your phone when it's in fastboot mode.
Download Android Studio & App Tools - Android Developers
Android Studio provides app builders with an integrated development environment (IDE) optimized for Android apps. Download Android Studio today.
developer.android.com
Android Studio won't install the USB Drivers by default, you'll need to install them through the SDK Manager (Android Studio -> Projects -> More Actions -> SDK Manager -> SDK Tools -> Google USB Driver checkbox -> Apply)
You'll need to manually install the drivers through the device manager while the phone is in fastboot mode and connected to the PC (right-click -> Update Drivers -> Browse Computer -> Let Me Pick -> Have Disk).
The drivers should be located at:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
You'll want the 'Android Bootloader Interface' driver.
Click to expand...
Click to collapse
------
Basically, you need to manually update the drivers through device manager.
edale1 said:
From one of my other threads:
------
------
Basically, you need to manually update the drivers through device manager.
Click to expand...
Click to collapse
I can't get it to work...
fogles2021 said:
I can't get it to work...
Click to expand...
Click to collapse
From the first update drivers dialog (your phone should be in fastboot mode):
"browse my computer for drivers"
"let me pick from a list of available drivers on my computer"
"have disk"
And the drivers should be at
Code:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
Once you select the .inf, you'll want to select this from the resultant list:
"Android Bootloader Interface"
fogles2021 said:
I can't get it to work...
Click to expand...
Click to collapse
Your phone is in EDL mode, also known as hard brick. It seems like the phone thinks both of your system partitions are empty or corrupt, as well as the bootloader is perhaps corrupt, due to which it is now gone to EDL mode as a last resort.
Typically, the only way to come out of it is to flash in EDL mode using MSMDownload Tool. Unfortunately for you, I don't see that Oneplus has released the MSMDownload Tool for the N200.
There are 4 things you can do at this stage.
1. If the phone is in return period, get it exchanged for another one.
2. Assuming the phone is under warranty, get it repaired under warranty
3. Wait for Oneplus to release the MSMDownload Tool for the N200. From past experience, Oneplus has eventually released it for every one of their phones. Once it is released, it is literally a 5 minute fix to get your phone to factory refreshed stage.
4. As a long shot, we can try to see if the bootloader is not corrupt, and if that is working, try to check if either of the 2 system partition is still intact, as @edale1 is suggesting above. Try the following
a. Press Volume Down+Power when phone is power off stage, and see if you can get the phone in fastboot mode.
b. Go to the folder when you have downloaded the Android SDK Toolkit. Alternately, search for the folder containing "fastboot.exe" on your hard drive. Open a command prompt in that folder containing fastboot.exe.
c. Run "fastboot devices" in the command prompt.
d. If you get a response of "no devices", then that means either phone is not in fastboot mode ( Go to Step a and repeat a,b,c until it is in fastboot mode) or bootloader is corrupt (nothing can be done other than Steps 1, 2 or 3 I have outlined above)
e. If you get a response of "XYZ fastboot" where XYZ is a random string/number, then bootloader is not corrupt. Proceed to Step f.
f. Type "fastboot getvar all" in the command prompt.
Wait for a lot of text to finish scrolling and look for the (bootloader) current-slot text
This should actually be toward the bottom without the need to scroll up.
The letter after this text will be the currently active partition slot for your device, either 'a' or 'b'
g. Follow @edale1's instruction above to change active partition to the *opposite* of whatever currently active partition e.g. if it says 'a' as the active partition in Step f above, then type in "fastboot --set-active=b" in command prompt, and vice-versa i.e. if it says 'b' as the active partition in Step f above, then type in "fastboot --set-active=a" in command prompt
h. If you get success in Step g, type "fastboot reboot" in command prompt, and keep your fingers crossed that it boots up normally. If not, that means both system partitions are corrupt. Follow Steps 1, 2 or 3 above.
Good luck!
fogles2021 said:
Well, ok..I have a huge problem.
I was in developer mode and it said i could switch my rom so i installed it and now my phone says "Your device is corrupt. It is not trusted and will not boot".
Any suggestions on how I can fix this?
Click to expand...
Click to collapse
No stock rom on oneplus/tmobile website
Im having a device corrupt error and cannot access phone anymore. Im trying to find the stock rom to flash with MSM tool but cantyfind it anywhere. You'd think oneplus would have it up on their website already. Anyone?
forum.xda-developers.com
Had the same problem, had to do a warranty replacement
I followed your mini guide but it says "Slotchange is not allowed in lock state"
Anyways to unlock it using fastboot ?
Ethanvio said:
I followed your mini guide but it says "Slotchange is not allowed in lock state"
Anyways to unlock it using fastboot ?
Click to expand...
Click to collapse
If you didn't enable OEM unlocking in developer options before you bricked your phone, you can't unlock those fastboot commands.
Can't seem to find a way to unlock the bootloader now.
This should be in the qna section
ROMSG said:
This should be in the qna section
Click to expand...
Click to collapse
Ok, I don't see an option to delete this post at first glance.
ROMSG said:
This should be in the qna section
Click to expand...
Click to collapse
I'm sorry, I'm too stupid today, but I can't find the Q and A thread. Do you have a direct link, by any chance?
alexandero11 said:
I'm sorry, I'm too stupid today, but I can't find the Q and A thread. Do you have a direct link, by any chance?
Click to expand...
Click to collapse
LG G5 Questions & Answers
Ask your questions about the LG G5 and get answers from the community! Please be as specific as possible when posting.
forum.xda-developers.com
Fortunately it has been archived: https://web.archive.org/web/2021120.../RetrieveBootloader.dev?categoryId=CTULRS0702
Not sure if it will work or even useful with ARB devices
wornOffAnkles said:
Fortunately it has been archived: https://web.archive.org/web/2021120.../RetrieveBootloader.dev?categoryId=CTULRS0702
Click to expand...
Click to collapse
FYI, the archive works, but not the back end.
sirgilmour said:
Can't seem to find a way to unlock the bootloader now.
Click to expand...
Click to collapse
With the LG Unlocker site gone for good (see above), the only way to unlock the bootloader is the DirtySanta/DirtyElf process. This can well vary by device model, so read the instructions that go with the phone model. It works, and in some cases will even unbrick the device.
With that directive in mind, and noting that my device is an LG V20, model US996 (aka. Carrier-Unlocked US version), here is a capsule summary of how to accomplish the task. You'll still need to find and download the necessary files for your device if it is not an US996 V20 and follow those directions, but this should give you the gist of what's involved:
Unbrick and/or restore LG V20 (US996) to stock
Source: https://forum.xda-developers.com/t/restore-v20-to-100-stock-even-for-bricked-devices.3524903/
Install LG Driver, LGUP, Uppercut, and supporting DLLs
Download .KDZ (Stock ROM) file
Completely Power off the device
Connect USB cable into PC
Press and hold VolUp
Connect USB to device
Device will enter Download (Firmware Update) mode
Release VolUp
Launch LGUP via Uppercut
Click "..." to locate and select the .KDZ
Click "UPGRADE"
Click "Start"
Wait for completion
Disconnect device
FYI, Stock ROM files can be downloaded from the Stock ROM repository at https://lg-firmwares.com/
Unlock Bootloader
Source: https://forum.xda-developers.com/t/v20-h915-us996-dirtyelf-bootloader-unlock-and-root-guide.3568013/
The scripts listed in the following directions are bundled in the DirtySanta/DirtyElf archive "kit" along with everything else required to get this done. The named scripts come in Unix/Mac (.sh) and Windows (.bat) form:
Enable Developer options
Enable OEM Unlock
Enable USB Debug
Connect device
Always trust the security key
Set USB to MTP (File Transfer) mode
Copy rooting folders to internal storage
Enable GENERAL>FINGERPRINTS & SECURITY>Phone Admin/Unknown Sources
Install terminal emulator APK
Open unlock kit directory
Execute runmefirst.bat to open "Trace" window
Execute step1.bat
At prompt:
run-as con
chmod 0777 /storage/emulated/0/*
On device:
id
If the string contains "context=u:r:untrusted_app", then on device:
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
Wait for prompt in "Trace" window
Execute step2.bat
Device will reboot into fastboot mode
Execute step3.bat
Device will reboot; remove battery
Hold VolDn and press Pwr
Release Pwr briefly when LG logo appears, then re-hold
Release Pwr and VolDn when reset appears
Select Yes 2x to restart device
Device will display a "corrupted system" screen and then load TWRP Recovery
BACKUP > Select Boot, Recovery, System, EFS, Firmware
WIPE > FORMAT DATA
WIPE > ADVANCED > Dalvik, System, Data, Cache
WIPE > FORMAT DATA
Proceed with the new ROM's installation instructions.
When running the TWRP backup, make sure you save that to an SD card > 16 GB
There is a method using LG LAF tool under mAid. mAid replaced the older FWUL which is now defunct. Here are the instructions I have (copied from other post). Remember to replace mAid for where it says FWUL:
Boot from your FWUL USB stick.
Put your phone into download mode. With the phone powered off, hold vol up and plug in the USB cable. You do not need to touch the power button -- the phone will power on and enter download mode.
Once booted, login. The password is: linux
Double click the LG folder that is on the desktop
Double click on LG LAF (runningnak3d) icon and you will be at a terminal prompt.
The following are the commands that you enter into that terminal. You can copy / paste them if you like.
[FONT=Noto Mono, monospace]git pull
git checkout h918-miscwrte
./step1.sh[/FONT]
When you are told to, pull the USB cable, and the phone will power off. You now have TWRP on your laf partition.
It must be said again, flash TWRP onto recovery so you can easily get to TWRP.
-----------------------------------------------
One thing to be aware of when trying to root/flash is the Anti-Rollback version. Here is some info (copied from other posts):
Qualcomm CPUs have a section dedicated to QFPROM (Qualcomm Flashing Programmable Read Only Memory). When you write to that area of the CPU, it can never be written to again. They are called Qfuses. When they are blown, they can't be "unblown". It contains several things, the PBL (primary boot loader), the RSA key used to verify the secondary bootloader, the Qfuses that control various aspects of the phone, and a LOT of other settings.
ARB is also stored in QFRPOM. There can be 16 values 0x0 to 0xF -- so lots of room to increment.
When the phone boots, the PBL loads the SBL(XBL) and compares the ARB version number of the SBL to the version that has been blown into the CPU. If the version is less than what is stored in QFPROM, the PBL immediately goes into 9008 mode -- you have a brick (at least with the V20). If the version is equal, it loads. If the version is greater than what is currently in QFPROM, it blows the next Qfuse, and ARB is incremented, and then it loads.
The SBL is signed with an RSA cert. The PBL uses the RSA key that is in QFPROM to verify the signature of the SBL. If the SBL has been modified, or the RSA sig doesn't match, the PBL goes into 9008 mode.
H91810O and below is ARB0
H91810P to H91810U is ARB1
find ARB (on stock ROM)
##244773825625#*#*
----------------------------------------------------
Here also is a thread that explains why the older "dirtycow" flash method no longer works.