Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Detailed installation instructions:
Install LineageOS on cheryl
Download link:
LineageOS Downloads
Recommended Google Apps package:
Open GApps (choose ARM64 as Platform and 10.0 as Android, use the Variant you want. Recommended nano package)
Changelog:
Changes for cheryl
Bug reports:
How to submit a bug report
LineageOS GitLab
Known bugs:
- Can't switch FPS (defaults to 120)
- Can't switch screen resolution (defaults to 2560x1440)
Donate to support development:
Donate via PayPal to mikeioannina
Donate via PayPal to LineageOS
XDA:DevDB Information
LineageOS 17.1 for Razer Phone (cheryl), ROM for the Razer Phone
Contributors
mikeioannina
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Recommended 9.0 - P-MR2-RC001-RZR-N.7083 (automatically installed with the ROM)
Based On: LineageOS
Version Information
Status: Nightly
Created 2020-04-23
Last Updated 2020-04-23
Successfully OTA with bootloop & arrow key bug
Successfully OTA updated from 20200417 (magisk installed) to 20200424. Same story, bootloop on first boot, restarted in recovery and reboot to successfully first boot.
One other minor issue I noticed which has been going on since 20200410, after selecting Settings > System > Buttons > Show Arrow Keys While Typing, the left and right arrow keys are swapped.
It's worked!!!
But after install Magisk 120Hz not working.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any chance this'll get to the Razer Phone 2? Kinda cheesed the RP1's now gotten Android 10 before the RP2
cha0sbuster said:
Any chance this'll get to the Razer Phone 2? Kinda cheesed the RP1's now gotten Android 10 before the RP2
Click to expand...
Click to collapse
If someone donates an RP2 then yes. I don't think anyone in lineage got that device.
Build servers are not up yet after the recent events but they will be up as soon as the migration to new infrastructure is complete.
I've been working on various issues on the device, 120Hz was broken (panel ran at 120Hz but android thought it runs at 90Hz) so there was noticeable jank. I fixed that issue so now it should run at 120Hz smoothly.
micro error in ott app( zalo, messenger..) lastest build
cha0sbuster said:
Any chance this'll get to the Razer Phone 2? Kinda cheesed the RP1's now gotten Android 10 before the RP2
Click to expand...
Click to collapse
I may be wrong, but there a lot of GSIs (including LOS) and for what I know they work on RP2. You should check the treble dev thread.
Before I start, I'd just like to mention that I know this is quite and outdated device.
I cannot for the life of me get this to install. It just bootloops.
I've tried the exact instructions on the Lineage site and it bootloops.
I've looked at all the posts in the Lineage OS 16 thread and it bootloops.
I'm just really really confused why I can't get this to boot.
Is there something I'm missing with the A/B partitions or something?
Oh wowee, after this 17th attempt I think it booted by my screen looks like static on an old tv.
Sheesh, looks like I got it.
Instrux:
install latest factory image (meaning bootloader and bootloader critical unlocked)
enable adb
adb reboot bootloader
fastboot flash boot_a boot.img
fastboot flash boot_a lineagerecovery.img
fastboot flash boot_b boot.img
fastboot flash boot_b lineagerecovery.img
fastboot --set-active=a
enter recovery using buttons
do both resets
adb sideload lineagerom.zip
reboot recovery
adb sideload gappsnano.zip
reboot bootloader
fastboot --set-active=b
enter recovery using buttons
DON'T WIPE
adb sideload lineagerom.zip
reboot recovery
adb sideload gappsnano.zip
reboot system
BOOTED. That took forever.
follow this instructions "https://wiki.lineageos.org/devices/cheryl/install".
QUOTE=crecsky;82573351]Before I start, I'd just like to mention that I know this is quite and outdated device.
I cannot for the life of me get this to install. It just bootloops.
I've tried the exact instructions on the Lineage site and it bootloops.
I've looked at all the posts in the Lineage OS 16 thread and it bootloops.
I'm just really really confused why I can't get this to boot.
Is there something I'm missing with the A/B partitions or something?
Oh wowee, after this 17th attempt I think it booted by my screen looks like static on an old tv.
Sheesh, looks like I got it.
Instrux:
install latest factory image (meaning bootloader and bootloader critical unlocked)
enable adb
adb reboot bootloader
fastboot flash boot_a boot.img
fastboot flash boot_a lineagerecovery.img
fastboot flash boot_b boot.img
fastboot flash boot_b lineagerecovery.img
fastboot --set-active=a
enter recovery using buttons
do both resets
adb sideload lineagerom.zip
reboot recovery
adb sideload gappsnano.zip
reboot bootloader
fastboot --set-active=b
enter recovery using buttons
DON'T WIPE
adb sideload lineagerom.zip
reboot recovery
adb sideload gappsnano.zip
reboot system
BOOTED. That took forever.[/QUOTE]
mikeioannina said:
If someone donates an RP2 then yes. I don't think anyone in lineage got that device.
Build servers are not up yet after the recent events but they will be up as soon as the migration to new infrastructure is complete.
I've been working on various issues on the device, 120Hz was broken (panel ran at 120Hz but android thought it runs at 90Hz) so there was noticeable jank. I fixed that issue so now it should run at 120Hz smoothly.
Click to expand...
Click to collapse
I will donate towards a Razer Phone 2 man. How much do you need all together? I know they have dropped a bit in pricing. Where can we send the donations to if we can get it going?
cha0sbuster said:
Any chance this'll get to the Razer Phone 2? Kinda cheesed the RP1's now gotten Android 10 before the RP2
Click to expand...
Click to collapse
We are putting together a donation pool to get him a device. We are about halfway there. Let me know if you want to contribute.
Is this the known issue that microphone is disabled using Skype/Telegram/Viber/Jitsi/Jami etc., even using bluetooth headset? Other side cannot hear me - just silence like sound not comes out at all. Using the latest lineage-17.1-20200430 build and the previous ones and having this issue. Not rooted, no Magisk, no gapps.
Might be related to this issue and the solution? https://forum.xda-developers.com/redmi-note-3/help/sound-voice-call-lineage-14-1-t3546237
Wanted to ask, was there any info about getting the other fps and resolution settings to work? I personally never use the 120 option and rather keep it on 60 frames 1440p for better battery life (even though I should put it on 720p if I want even better life out of the phone but this is fine)
Hi! I couldn't install latest build. Not even bootloop. Stuck at android logo. Had to reinstal 20200430 build and everything become fine again. Is a latest build broken?
I can't seem to get the newest nightly to install. Nightly 17.1-20200430 installed fine but the latest one just boots back into recovery.
June 3, 2020 build doesn't boot. Went back to April 30, 2020 build
sinkoo1979 said:
June 3, 2020 build doesn't boot. Went back to April 30, 2020 build
Click to expand...
Click to collapse
Flashed fine on mine.
June, 5th. Booted just fine. Thank you!
---------- Post added at 11:58 AM ---------- Previous post was at 11:51 AM ----------
Anybody know, how it goes with magisk issue on los 17.1?
Is it possible to install it and boot normally?
666zam said:
June, 5th. Booted just fine. Thank you!
---------- Post added at 11:58 AM ---------- Previous post was at 11:51 AM ----------
Anybody know, how it goes with magisk issue on los 17.1?
Is it possible to install it and boot normally?
Click to expand...
Click to collapse
Can I ask how did you get the latest build to boot? I tried myself and it put me back into recovery.
As simple, as ota, using updater.
Related
I'm from Mexico and like 20 mins ago I got this update. Has anyone got this update? (An OTA update link is in the thread just use the Search bar)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
alealicks said:
I'm from Mexico and like a 20 min ago got this update. Anyone got the update? (I don't know how to extract the OTA, so don't ask me for that)
Click to expand...
Click to collapse
I'm from Mexico too, I received the OTA today too
---------- Post added at 10:37 PM ---------- Previous post was at 09:52 PM ----------
It seems that this update will also update the bootloader to B1:07(in the September patch Rom, it was B1:06)
Security Patch?
I saw people complaining that the camera does not work well. It is true?
Enviado desde mi Moto G (4) mediante Tapatalk
shadow20012 said:
Security Patch?
Click to expand...
Click to collapse
Yes
RenePaul99 said:
I'm from Mexico too, I received the OTA today too
---------- Post added at 10:37 PM ---------- Previous post was at 09:52 PM ----------
It seems that this update will also update the bootloader to B1:07(in the September patch Rom, it was B1:06)
Click to expand...
Click to collapse
Thanks, that's useful to know, looks like updating to the December 2017 security patch may mean the latest blankflash we have could no longer work for rescuing bricked devices in the future. Until we get a new blankflash possibly.
OTA Captured: https://mega.nz/#!VdcCTZpZ!i4RP94md7le4l5tOlT_88ywmFzxtP9GZISxnLIiyzw4
Sorry for Mega
Thanks! Now some of the wizards might "cook" a full install so we all can update our unlocked/rooted devices.
Blur_Version.25.221.10.athene.retail.en.US.zip
Download
Some observations about this patch:
a)36.2 MB in size, carrying the December 2017 security patch as noted above with a final build of NPJS25.93-14-13/3. md5: 28d24a02c7e7caecf4be102a6059074f Though it's the 1st December 2017 update, I'm not sure if this update has the KRACK patches built in (as they were covered by the 6th November 2017 patch) - depends on when Motorola got the patch. Apologies for misleading anyone.
b)From the updater script, requires NPJS25.93-14-10 already on your device to flash.
Code:
Package expects build thumbprint of 7.0/NPJS25.93-14-13/3:user/release-keys or 7.0/NPJS25.93-14-10/10:user/release-keys
c)Looks to be carrying updates for some apps/services, such as BellTVWidget and OmegaPttMX.
d)As helpfully noted by RenePaul99, updates the bootloader to B1:07 (with a build date of 2017-11-07) from B1:06 in NPJS25.93-14-10. This may result in the blankflash we have at https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 failing to work if this OTA update is applied - it may check and only work on B1:06 and earlier bootloaders (and no, generally you can't downgrade bootloaders) I'm not certain of this, though I dislike seeing devices bricked and the only resolution being an expensive motherboard replacement. So crucially, if you've updated your device to this OTA update, be very careful if you decide to flash older Motorola stock ROMs (e.g. after flashing a custom ROM), as an OTA update could hard brick your device, and the current blankflash may not work in rescuing your device. The safest way to revert, if you updated to this stock patch level, would be to use your TWRP backup or wait for the NPJS25.93-14-13 fastboot ROM to be 'obtained' (leaked) from Motorola.
EDIT - 17/01/2018 - I've seen one possible rescue with the latest blankflash we have from a user updated to the December 2017 B1:07 bootloader. Though it suggests the blankflash is still working, be very careful regardless.
As generally with OTA updates, they only will flash successfully onto a device with a clean stock system, stock recovery and stock kernel. Unlocked bootloader status doesn't appear to matter.
Of course, if you're rooted, then the above aren't true; I was running a XT1642 with TWRP, ElementalX and magisk 13.3, so the OTA update is a no-go. One straightforward way to restore my device to a OTA friendly state was to re-flash the NPJS25.93-14-10 stock ROM (which we have here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138)
The following flashing commands I used should not affect your data and return your device to an OTA friendly state, but as always back up your data just in case. You may be able to use fewer commands but I prefer to flash all these partitions (you probably want to do things properly with the core firmware running your device!) As far as I know, system, OEM, boot, recovery and logo partitions need to be stock at the very least. GPT/bootloader/modem you could omit if you're sure they are the same patch level as NPJS25.93-14-10 (bootloader should be B1:06 and modem should be ending in 62.01R), if you're not sure, I'd flash them too to ensure all your firmware is of the same patch level. Don't mix and match patch levels when it comes to OTA updates... Oh, and check that you have plenty of time, you don't want to rush firmware flashes.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
After manually flashing each command (copy and paste is your friend, though nothing to stop you using a script), my device rebooted to system (complaining of bad key or N/A on the bootloader warning screen, that's normal). Rebooted to stock recovery (with the Android on its back and the no command), then held the power button before pressing and releasing the volume up key, then releasing the power button. Took a few tries before getting into the recovery menu. (as explained here: https://forum.xda-developers.com/moto-g4-plus/help/command-stock-recovery-xt1642-t3484616 )
As before, flashed the OTA update without issue from the SD card/internal storage (though had to mount /system as the recovery complained it couldn't mount internal or external storage, after mounting the 'apply update from SD card' worked and loaded up internal storage...), wiped cache after installation and rebooted.
Now I'm running NPJS25.93-14-13 and still have all my data Not rooted or having TWRP on, but I might see how I get on with this new build. Initial impressions are that it's fast and stable, though early days yet. As for the camera, photos and video with the rear camera appear to work okay with version 6.0.86.7 of the Moto camera app, what problems have been mentioned with the camera?
Working fine here XT1621 just used adb to sideload
that oreo update seems to be vaporware as the time goes on
victor.neyoy said:
that oreo update seems to be vaporware as the time goes on
Click to expand...
Click to collapse
Knowing that Motorola is updating the security patches every 3 months, in the best case will get Oreo by the end of March (the date of the new security patch update).
Still Waiting....
Please anyone has the rom flasheable through adb? i tried to downgrade from npjs25.93-14-13 to npjs25.93-14-10 and now my phone is bricked and i need the rom npjs25.93-14-13 to flash. anyone?? links?
leoh.rod said:
Please anyone has the rom flasheable through adb? i tried to downgrade from npjs25.93-14-13 to npjs25.93-14-10 and now my phone is bricked and i need the rom npjs25.93-14-13 to flash. anyone?? links?
Click to expand...
Click to collapse
What firmware did you try to flash that bricked your device? By bricked do you mean LED blinking and failure to boot?
Currently no NPJS25.93-14-13 firmware available, we have to wait for Motorola to deploy it to their firmware server and hopefully someone can grab the link.
echo92 said:
What firmware did you try to flash that bricked your device? By bricked do you mean LED blinking and failure to boot?
Currently no NPJS25.93-14-13 firmware available, we have to wait for Motorola to deploy it to their firmware server and hopefully someone can grab the link.
Click to expand...
Click to collapse
my phone was on npjs25.93-14-13 and i tried to downgrade to npjs25.93-14-10 and it doesnt boot. its stucked on recovery mode. what should i do now to bring it back?
leoh.rod said:
my phone was on npjs25.93-14-13 and i tried to downgrade to npjs25.93-14-10 and it doesnt boot. its stucked on recovery mode. what should i do now to bring it back?
Click to expand...
Click to collapse
Are there any messages in recovery mode or is it just stuck booting? Have you tried a cache wipe in recovery and reboot, or if you've got your data backed up, try a factory reset (which would wipe your data)?
Was the flash complete, did you see [OKAY] on all the NPJS25.93-14-10 firmware flashing commands? You may have an incomplete flash if not, could try another flash of the September 2017 stock firmware (without flashing GPT/bootloader). Can I ask why you were trying to downgrade your firmware from the 7.0 December patch? Is your bootloader unlocked (should be if you're trying to downgrade)?
Are you able to boot to bootloader (power off your device, then hold down power and volume down, then you should boot into bootloader), and select 'Start' - does that boot your device or result in a bootloop again?
leoh.rod said:
my phone was on npjs25.93-14-13 and i tried to downgrade to npjs25.93-14-10 and it doesnt boot. its stucked on recovery mode. what should i do now to bring it back?
Click to expand...
Click to collapse
Never downgrade when you don't have the full flash available. AFAIK the new bootloaders cannot be downgraded, and it was reported that the 14-13 brings in a new bootloader. Older system don't usually work with the new bootloaders.
As it was said, you might need to wait to get the full 14-13 and stay on that.
Anyone from India got this update?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
1 . Download twrp-3.4.0-0-CTL_sprout.img & twrp-installer-3.4.0-0-CTL_sprout.zip copy in one folder
2. connect phone to pc boot your phone to download mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot boot twrp-3.4.0-0-CTL_sprout.img
6. now your phone will boot in to twrp
7. now copy twrp installer.zip in to your phone from pc using type c usb cable
8. now flash twrp installer zip ( this will make your twrp permanent )
10. now flash magisk or what ever your wish and press reboot system
11. now if you people want to boot in to twrp? power off your phone connect to pc or charger
& wait for battery logo and press volume up and power button for 8 seconds now you will boot in to twrp
Download Android 10 Twrp-3.4.0-0 From Here
For More Information About Status Official Click Here
XDA:DevDB Information
TWRP 3.4.0-0 , for the Nokia 7.1
Contributors
Raghu varma
Source Code: https://github.com/TeamWin/android_device_nokia_CTL_sprout
My build script https://github.com/RaghuVarma331/scripts
Version Information
Status: Stable
Current Stable Version: 3.x
Stable Release Date 2019-01-26
Created 2019-01-26
Last Updated 2020-06-25
Hi Raghu, I appreciate the work you are doing for the Nokia community!
I have a question... if I boot directly into TWRP instead of flashing TWRP over my stock recovery, is it truly necessary to reflash the stock recovery? Like for instance, I only want to load magisk on my device/create a nandroid backup and keep stock recovery and stock OS until the Android Q release. Though, from experience from other devices I have owned... booting directly into TWRP instead of flashing only is temporary and keeps the stock recovery intact. I am not sure from your tutorial if I truly need to flash my stock recovery after just booting TWRP temporarily?
usernamedoesnotexist said:
Hi Raghu, I appreciate the work you are doing for the Nokia community!
I have a question... if I boot directly into TWRP instead of flashing TWRP over my stock recovery, is it truly necessary to reflash the stock recovery? Like for instance, I only want to load magisk on my device/create a nandroid backup and keep stock recovery and stock OS until the Android Q release. Though, from experience from other devices I have owned... booting directly into TWRP instead of flashing only is temporary and keeps the stock recovery intact. I am not sure from your tutorial if I truly need to flash my stock recovery after just booting TWRP temporarily?
Click to expand...
Click to collapse
if you want to get back to your stock recovery just flash your stock boot.img of the respective security patch
for example you flashed twrp on may 2019 pie
and now you want to get back to stock recovery?
so just flash using fastboot flash boot boot.img ( may 2019 boot.img)
Raghu varma said:
if you want to get back to your stock recovery just flash your stock boot.img of the respective security patch
for example you flashed twrp on may 2019 pie
and now you want to get back to stock recovery?
so just flash using fastboot flash boot boot.img ( may 2019 boot.img)
Click to expand...
Click to collapse
Thanks for the info! Unfortunately, I couldn't pull my stock recovery from adb and had to use the terminal inside TWRP to pull my recovery. After successfully getting stock recovery, I patched the stock recovery (after copying) to my external SD with magisk and flashed that via adb. Magisk is now installed and I am satisfied.
Note: this is relatively the first time I am leaving stock recovery on my device vs custom recovery to keep the OTA updates. This is because there isn't much of a dev community here at the moment and not much to do on the device.
New Build Is Up
Based On R40
Android version - pie
twrp- based on June 2019
################ The final Main installation procedure #################
Note - this will work only On June 2019 Security Patch And From Now i will update Twrp Every Month
1 . Download twrp-3.3.1-0-CTL.img & twrp-installer-3.3.1-0-CTL.zip copy in one folder
2. connect phone to pc boot your phone to download mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot boot twrp-3.3.1-0-CTL.img
6. now your phone will boot in to twrp
7. now copy twrp installer.zip in to your phone from pc using type c usb cable
8. now flash twrp installer zip ( this will make your twrp permanent )
10. now flash magisk or what ever your wish and press reboot system
11. now if you people want to boot in to twrp? just power off your phone connect to pc or charger
& wait for battery logo and press volume up and power button for 8 seconds now you will boot in to twrp
congratulations now you are successfully booted in to twrp
@Raghu varma
Any telegram group for development? If that exist, please add me t.me/theHari08.
Note - Twrp Support is back for Nokia 7.1
Changelog
13-12-2019
* Initial android 10 twrp builds are up
* Twrp based on 3.3.1-0
* Supports on Android 10 stock roms and custom roms
* supports on Android 9 stock roms and custom roms
* Follow instructions as i mentioned above in the xda thread for installation
* Omni sources based on latest r47
* Decryption works
Hi,
I used to be into flashing phones back in the day but now I'm a bit rusty so my question is simple:
Do I have to unlock the bootloader first before I can flash twrp? It is a painpoint for me on this phone that there is no simple way to do that.
Thanks.
giant_karlik said:
Hi,
I used to be into flashing phones back in the day but now I'm a bit rusty so my question is simple:
Do I have to unlock the bootloader first before I can flash twrp? It is a painpoint for me on this phone that there is no simple way to do that.
Thanks.
Click to expand...
Click to collapse
Before you can modify anything on a phone you always have to unlock the bootloader. Since Nokia does not allow official bootloader unlocks, we have to go through a paid method (see other threads about unlocking the bootloader here).
this guy will do it for a small fee well worth it ...
Added official support
Android 10 TWRP doesn't work on 7.1 december update
Hey,
Thanks for all the hard work you're putting into this project, really helped me when I was using android 9.
But I can't seem to make the latest version you uploaded work now that I'm on android 10. When I try to boot the image file I'm stuck on the android one logo, no matter how much I wait.
So I was wondering if the latest update isn't supported yet or if I'm doing something wrong.
Really sorry to bother you if it's the former.
Have a nice day.
Reysen said:
Hey,
Thanks for all the hard work you're putting into this project, really helped me when I was using android 9.
But I can't seem to make the latest version you uploaded work now that I'm on android 10. When I try to boot the image file I'm stuck on the android one logo, no matter how much I wait.
So I was wondering if the latest update isn't supported yet or if I'm doing something wrong.
Really sorry to bother you if it's the former.
Have a nice day.
Click to expand...
Click to collapse
*make sure your phone bootloader is unlocked.
* make sure you downloaded twrp files from xda thread download links
* make sure you follow steps as i mentioned above
according to your info i tested again on my Nokia 6.1 Plus android 10 stock rom based on december security patch.
Nokia 7 Plus , Nokia 7.1 , Nokia 6.1 & Nokia 6.1 Plus all sources are same
so it should work on 7.1 too make sure you re flashed stock rom and test again because trying several times on same partition may corrupt and failed to boot.
Hey, thanks for your fast answer.
*make sure your phone bootloader is unlocked.
Click to expand...
Click to collapse
The bootloader is indeed unlocked
* make sure you downloaded twrp files from xda thread download links
Click to expand...
Click to collapse
I tried multiple versions from the sourceforge link.
* make sure you follow steps as i mentioned above
Click to expand...
Click to collapse
I'm stuck at "boot TWRP" step as there is only the android one boot screen and I can only reboot. Though for some reason I can still use some fastboot commands (such as fastboot reboot bootloader).
I never modified the system partition on my phone through fastboot, only flashed a magisk patched boot.img when I was still on android 9.
Before upgrading to android 10, I patched the stock boot.img and did a factory reset. Then I did all the available updates through the phone update system. Never used a custom rom, so everything should be stock.
Forgot to mention but the phone isn't bricked or anything, it work normally without any issue. I just can't run TWRP for some reason.
Here's the oem information if that can help you
Thanks and have a nice day
(Unfortunately I can't upload pictures or post links)
Reysen said:
Hey, thanks for your fast answer.
The bootloader is indeed unlocked
I tried multiple versions from the sourceforge link.
I'm stuck at "boot TWRP" step as there is only the android one boot screen and I can only reboot. Though for some reason I can still use some fastboot commands (such as fastboot reboot bootloader).
I never modified the system partition on my phone through fastboot, only flashed a magisk patched boot.img when I was still on android 9.
Before upgrading to android 10, I patched the stock boot.img and did a factory reset. Then I did all the available updates through the phone update system. Never used a custom rom, so everything should be stock.
Forgot to mention but the phone isn't bricked or anything, it work normally without any issue. I just can't run TWRP for some reason.
Here's the oem information if that can help you
Thanks and have a nice day
(Unfortunately I can't upload pictures or post links)
Click to expand...
Click to collapse
Well i don't want to waste my time infront of sitting xda and answering questions like customer care but still yes i will help you out in this
1. just don't use patched boot images
2. Flash stock rom again for fresh start
3. If you are confused about flashing stock rom process
Go ahead to this link
https://forum.xda-developers.com/nokia-7-1/development/tool-stock-rom-flash-tool-nokia-7-1-t4023959
4. After booting in to stock rom power of your phone & press volume down & power button for download mode
5. now open cmd in twrp download folder
6. type fastboot boot twrpname.img
7. Now your phone reboots to twrp
8. Decrypt your phone using your lock screen password,pin or pattern (if you keep security)
9. Now flash magisk of what ever you want but make sure you flash the stuff according to my loyal steps. Which i mentioned my xda threads in 7.1 xda forums
Peace !
Raghu varma said:
Well i don't want to waste my time infront of sitting xda and answering questions like customer care but still yes i will help you out in this
1. just don't use patched boot images
2. Flash stock rom again for fresh start
3. If you are confused about flashing stock rom process
Go ahead to this link
https://forum.xda-developers.com/nokia-7-1/development/tool-stock-rom-flash-tool-nokia-7-1-t4023959
4. After booting in to stock rom power of your phone & press volume down & power button for download mode
5. now open cmd in twrp download folder
6. type fastboot boot twrpname.img
7. Now your phone reboots to twrp
8. Decrypt your phone using your lock screen password,pin or pattern (if you keep security)
9. Now flash magisk of what ever you want but make sure you flash the stuff according to my loyal steps. Which i mentioned my xda threads in 7.1 xda forums
Peace !
Click to expand...
Click to collapse
Hi,
I flashed my nokia 7.1 like instructed and everything went well (though I noticed it wasn't the latest version, but that's a detail).
Went into the bootloader and tried running TWRP but still had the same issue as before (stuck on the android one boot, it was a totally stock ROM, the one provided on your other post).
So I used the boot.img from the stock ROM you uploaded and patched it, then flashed it in the bootloader and it worked.
So even though TWRP still doesn't work in the end I did what I wanted to do, so thanks for your help.
And again, thanks for all the work you're doing, sorry to bother you.
Have a nice day.
Same problem here - unlocked my sons' Nokia 7.1 today via techmestos service, rebooted into the downgraded Android, entered setup and started the mandatory Android upgrade, went through that successfully, activated ADB, got into Download mode and ran the following command:
Code:
fastboot boot twrp-3.3.1-0-CTL_sprout-10.0-20200109.img
downloading 'boot.img'...
OKAY [ 1.058s]
booting...
OKAY [ 5.058s]
finished. total time: 6.116s
Phone screen changed to the 'bootloader unlocked' screen and then the usual AndroidOne boot screen appeared. But neither TWRP nor Android came up ...
The downloaded files are OK, I checked the sha1sum on both of them
Any hints what to do here?`How can I help to track this down?
husky69 said:
Same problem here - unlocked my sons' Nokia 7.1 today via techmestos service, rebooted into the downgraded Android, entered setup and started the mandatory Android upgrade, went through that successfully, activated ADB, got into Download mode and ran the following command:
Code:
fastboot boot twrp-3.3.1-0-CTL_sprout-10.0-20200109.img
downloading 'boot.img'...
OKAY [ 1.058s]
booting...
OKAY [ 5.058s]
finished. total time: 6.116s
Phone screen changed to the 'bootloader unlocked' screen and then the usual AndroidOne boot screen appeared. But neither TWRP nor Android came up ...
The downloaded files are OK, I checked the sha1sum on both of them
Any hints what to do here?`How can I help to track this down?
Click to expand...
Click to collapse
TWRP went official so technically you can go to the TWRP site and download the current there
In addition to it going official, there is no need to download both the img and zip installer with it.
https://dl.twrp.me/CTL_sprout/
You can now just flash (fastboot flash recovery twrp-3.3.1-0-CTL_sprout.img).
https://twrp.me/nokia/nokia7.1.html
Things to keep in mind: If you have a PIN or Passcode you should disable it on the ROM before booting up to TWRP because of encryption.
If you flash another ROM such as Lineage OS shortly after flashing TWRP, it will replace the TWRP with the Lineage OS recovery. So you will probably have to flash TWRP again.
I hope that this works?!
i have android 9 is there a twrp image for 9?
Alas, this does not help, the same problem, the phone hangs on the logo)
P.S
executed the commands like this:
fastboot flash recovery (error issued)
fastboot boot
and successfully loaded into TWRP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.3.1-0+ for the LG G7 ThinQ
**WARRANTY VOIDED***
I am not and neither is TWRP Team responsible for any damages you or someone does using this software or hardware.
That includes phone bricking, levitation, world war 3 etc.
Click to expand...
Click to collapse
Warning: This TWRP Recovery is only useful for installing custom ROMs.
Currently there's no way to use this recovery on stock in any meaningful way without future addons
(Data partition cannot be read because of LG default encryption)
You cannot install or backup anything while you have LG Encryption enabled. A future addon can disable it.
<-- Requirements
An Bootloader unlocked LG G7 ThinQ by any means. (official or unofficial) (G710TM Models are impossible to be supported, sorry)
More information on officially unlocking the LG G7 here: https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
Running minimum LG Stock Android 9 Pie (AOSP GSI does not count)
A PC and ADB + Fastboot
The temper to read twice
<-- Needed files
You only need this boot image:
https://drive.google.com/open?id=1FcIBNfL3_72cQwuxd2TyZSjnC-ItnNTt
For developers who want to build their own TWRP Boot image here's the device-tree for it
https://github.com/LameMonster82/android_device_lge_judyln-twrp
<-- Installation
Step 1: Enter Fastboot mode
Connect your phone to your PC with a USB Cable
Restart the phone
While the phone is restarting hold Volume down button.
Note: Make sure you hold Volume down button before you see the black and white "LG G7 ThinQ" text
If you see the red LG Logo you either messed up or you don't have access to fastboot mode witch is another problem i can't solve easily.
If done correctly you should be in Fastboot now
Step 2: Install the boot image
Open the command prompt or your terminal (depending on what PC Platform you are)
Type:
Code:
fastboot boot [B][TWRP Boot image location][/B]
Click to expand...
Click to collapse
Note: This TWRP is only temporarily (it does not overwrite the bootimage). When you reboot it will dissapear and you will need to redo the fastboot command.
You're done. Now you can use TWRP to install custom ROMs
------------------------------------------------------------------------------------------------------------------------Legacy tutorial. Do not use unless you use TWRP older than Feb 2020.↓
Code:
[SIZE="5"][B][I][CENTER]<-- Needed files[/CENTER][/I][/B][/SIZE]
[LIST]
[*]You only need this boot image:
[url]https://drive.google.com/open?id=1n2wKdwARddx_KCIdLi10KawY_THlcRi4[/url]
[*]For developers who want to build their own TWRP Boot image here's the device-tree for it
[url]https://github.com/LameMonster82/android_device_lge_judyln-twrp[/url]
[/LIST]
[SIZE="5"][B][I][CENTER]<-- Installation[/CENTER][/I][/B][/SIZE]
[QUOTE][SIZE="3"][B]Step 1: Enter Fastboot mode[/B][/SIZE]
[LIST]
[*]Connect your phone to your PC with a USB Cable
[*]Restart the phone
[*]While the phone is restarting hold Volume down button.
[B]Note[/B]: Make sure you hold Volume down button before you see the [U][B]black and white[/B][/U] "LG G7 ThinQ" text
If you see the red LG Logo you either messed up or you don't have access to fastboot mode witch is another problem i can't solve easily.
[*]If done correctly you should be in Fastboot now :)
[/LIST]
[SIZE="3"][B]Step 2: Install the boot image[/B][/SIZE]
[LIST]
[*]Open the command prompt or your terminal (depending on what PC Platform you are)
[*]Type:
[/LIST]
[CODE]fastboot flash boot_a [B][TWRP Boot image location] --set-active=a[/B]
The best way you can set the TWRP Boot image location is to manually "drag and drop" the file itself in your command prompt
Also make sure you "drag and drop" the TWRP Boot image before you type --set=active=a
Don't forget --set-active=a has 2 little lines at the beginning. No space between them.
Step 3: Enter Recovery mode
Restart the phone (using power button if you're still in fastboot)
Before the phone turns off hold Volume down and power button
The moment you see the black and white "LG G7 ThinQ" Text start clicking the power button as much as you can without letting the Volume down button.
If done correctly you should see a white screen with "Factory reset" text on top.
If you done step 2 correctly clicking yes on both prompts on the phone will get you to TWRP
For people who still have trouble getting into recovery mode here's a visual example of how to enter recovery mode (youtube) https://youtu.be/_0yoFEvIods
Note: You don't have to be in system. Rebooting from bootloader will still work
[/QUOTE]
Congratulations you now have TWRP Recovery on your LG G7 ThinQ :highfive:[/CODE]
Join our Telegram Group here:
>> t.me/lgg7thinqmain <<
I would like to thank:
@Sellerie_ and @J0SH1X for their help on the TWRP Project for LG G7 ThinQ
Here be dragons!
Reserve for more info and changelogs
Another reserve because why not
I see you compiled twrp with crypt enabled, are the blobs not located in the vendor partition for encryption?
loonycgb2 said:
I see you compiled twrp with crypt enabled, are the blobs not located in the vendor partition for encryption?
Click to expand...
Click to collapse
Nope. The problem is there are no blobs to use. Yeah keymaster is there but keystore module is missing from the vendor and the system. The closest thing I found was lgkm module that looks like a proprietary keystore module for lg
LameMonster82 said:
Nope. The problem is there are no blobs to use. Yeah keymaster is there but keystore module is missing from the vendor and the system. The closest thing I found was lgkm module that looks like a proprietary keystore module for lg
Click to expand...
Click to collapse
My G7 is not bootloader unlocked so cant really help with dev, but any reason it wouldnt use the same same as the v30?
loonycgb2 said:
My G7 is not bootloader unlocked so cant really help with dev, but any reason it wouldnt use the same same as the v30?
Click to expand...
Click to collapse
Can't get it to work
Can g710ulm use this trwp to flash lineage OS?
cartman56 said:
Can g710ulm use this trwp to flash lineage OS?
Click to expand...
Click to collapse
As long as you have an unlocked bootloader
Can i update TWRP trough TWRP by installing it as image into boot?
bongster said:
Can i update TWRP trough TWRP by installing it as image into boot?
Click to expand...
Click to collapse
Yes
Can i flash magisk zip for this twrp?
simodf91 said:
Can i flash magisk zip for this twrp?
Click to expand...
Click to collapse
Yes but only useful for custom ROMs
according to the page you linked regarding the bootloader unlocking process, only the LMG710EM is supported... have you successfully done this with any other model?
dode417 said:
according to the page you linked regarding the bootloader unlocking process, only the LMG710EM is supported... have you successfully done this with any other model?
Click to expand...
Click to collapse
Myself no but it's possible to unlock the bootloader in other ways and multiple people already have done that
Hello, I am not very educated about this as I would like...
Is this recovery "persistent"? Why it is not possible to use this recovery to flash/root magisk on stock roms?
Thank you.
is it needed for magisk?
hello,
stock LG Pie (v20c) with bootloader unlocked. do i need to install this (TWRP) in order to root it with the magisk file from your drive, or will it work without?
(sorry for the noob/stupid/uninitiated/etc question, i'm really new at this)
louie_yo said:
hello,
stock LG Pie (v20c) with bootloader unlocked. do i need to install this (TWRP) in order to root it with the magisk file from your drive, or will it work without?
(sorry for the noob/stupid/uninitiated/etc question, i'm really new at this)
Click to expand...
Click to collapse
No need to install TWRP for root. Just follow the guide there and you should be fine.
How strict is the Android Pie requirement before installing TWRP?
I have a G710VM that I'm trying to get LineageOS onto. I've already gotten the bootloader unlocked, but it seems like, so far, I can only get bootloader access by using the ULM 8.0 ROM (ULM11g). If I try the European 9.0 (EM20b) or ULM 9.0 (ULM20d) ROMs, I lose bootloader and fastboot access.
Also, is this TWRP a persistent TWRP, or semi- or non-persistent.
I also apologize in advance if I use the wrong terminology or make the wrong assumptions as this is my first attempt at unlocking a phone and putting a custom OS on it.
Halogen_03 said:
How strict is the Android Pie requirement before installing TWRP?
Click to expand...
Click to collapse
briccked my g7 running android 8.0 following this guide, so i'd say its important. stuck at "enter sahara mode"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
SHRP is inspired by Material design 2 to bring the newest design to the native TWRP. SHRP provides much more along side of it's rich UI experience. New dashboard makes it very easy to interact with TWRP. SHRP got some cool features like Whole new theming section ,Flash Magisk (root or unroot), Camera2api enabler Directly from dashboard, Password protection etc. It's all started , lot more to come.
- Themes
- List view mode along with grid dashboard
- Status bar customization
- New rounded icons added on dashboard
- Notch mode with toggle to disable
- Dark mode or pure white, it's on you
- Navigation bar customization
- Settings + Advanced Settings
- Flash Magisk
- Clear fingerprints.
- Flash ViperFX
- Recovery Locking , Pin or Pattern lock
- CPU core lock/unlock
- Language changing
- Hal3 / CameraAPI2 enabling/disabling
- Oreo+ Reboot menu style
- Redesigned lock screen interface
- Flashlight
- Magisk manager - Enable, disable or delete magisk modules right from SHRP
- and many more, flash right now to find out
1. Make sure you have a custom recovery installed
2. Download the latest SHRP recovery for your device
3. Boot into recovery
4. Flash shrp recovery zip
5. Reboot to recovery.
6. Done
It may happen that after installing the recovery, the device could no longer boot into the ROM, for this you just need to install magisk.
Decryption may not work.
It may happen that the recovery freezes on the logo, to resolve it check this thread here.
No other bugs
DOWNLOAD NOW
Github
Website
ScreenShots
Telegram Group
EpicX
DNI9
Giovix92
TeamWin
osmOsis
VR25
Topjohnwu
Mauronofrio
DarthJabba9
Special Thanks
Pritish
Kirill
Burak D.
ZJRDroid
LayeardDevMod
Please inform if we forgot to mention your name here , thanks !
Maintainer: XRed_CubeX
Based On: TWRP
TWRP Version: v3.3.1-0
XDA:DevDB Information
[RECOVERY] [jasmine_sprout] Sky Hawk Recovery Project v2.2 [04-03-2020], ROM for the Xiaomi Mi A2
Contributors
XRed_CubeX
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: TWRP
Version Information
Status: Stable
Created 2020-03-11
Last Updated 2020-03-14
Reserved
Changelogs:
SHRP V2.2 104011032020:
Fixed the bug that recovery did not create the SHRP folder and therefore the themes did not work.
Added support for F2FS.
Added IMG file.
SHRP V2.2 Official:
Initial build
nice recovery
Clean, clear and nice set of features.
Really like this one, thanks!
Hm, but I really do miss the option to wipe vendor.
Not possible, also not after mounting.
it is wanted, it is not included, however, in a future update I can add it
I flashed this zip via a official twrp (booted the official twrp via "fastboot boot twrp.img" command).
so the problem i'm facing is that after FLASHING any recovery other than by using "FASTBOOT BOOT COMMAND" the recovery gets stuck at the loading screen/ The recovery logo.
It's the same issue with all three recoveries I tried
e.g.: pitch-black recovery, Official TWRP, and this recovery all gets stuck at the logo
can anyone help me
Nikhil Chandran said:
I flashed this zip via a official twrp (booted the official twrp via "fastboot boot twrp.img" command).
so the problem i'm facing is that after FLASHING any recovery other than by using "FASTBOOT BOOT COMMAND" the recovery gets stuck at the loading screen/ The recovery logo.
It's the same issue with all three recoveries I tried
e.g.: pitch-black recovery, Official TWRP, and this recovery all gets stuck at the logo
can anyone help me
Click to expand...
Click to collapse
Use the .img files with fastboot only to boot into recovery.
Then use the .zip recovery file from within the booted recovery to flash permanent twrp, after the ROM installation.
Phil_Smith said:
Use the .img files with fastboot only to boot into recovery.
Then use the .zip recovery file from within the booted recovery to flash permanent twrp, after the ROM installation.
Click to expand...
Click to collapse
I tried to flash the recovery like you said I'm on PEX Q.
And I booted to the official twrp (via command) then flashed this recovery and it back-up ed the boot img from both slots and replaced with this recovery and after that when I try to go to the recovery the it does go to the recovery but it's not loading after the logo, it's stuck at the logo, so I tried to boot the phone it went to fastboot without booting the phone. So I dirty flashed the ROM now it's booting but I lost magisk root and even after trying to flash magisk over and over I can't get root ( I think I tried on both slots ) still not getting root or loading the recovery after the logo
Nikhil Chandran said:
I flashed this zip via a official twrp (booted the official twrp via "fastboot boot twrp.img" command).
so the problem i'm facing is that after FLASHING any recovery other than by using "FASTBOOT BOOT COMMAND" the recovery gets stuck at the loading screen/ The recovery logo.
It's the same issue with all three recoveries I tried
e.g.: pitch-black recovery, Official TWRP, and this recovery all gets stuck at the logo
can anyone help me
Click to expand...
Click to collapse
This happens when starting from the Stock ROM without doing fastboot -w.
This command must be done only with PLATFORM TOOLS!!! And not with Minimal fastboot or 15 seconds Adb installer.
The default Stock ROM has the data encrypted and gives problems when starting recovery when installed but not when it is started temporarily. You can try doing "Format data" from the Normal TWRP and then try installing other Custom Recovery. I have had this problem in the past and solved it with fastboot -w but I have not tested format data with TWRP.
P.S: This also happens with ROM encrypted with FBE. (eg PE Fan Edition)
TWRP 4pda is compatible with FBE
XRed_CubeX said:
This happens when starting from the Stock ROM without doing fastboot -w.
This command must be done only with PLATFORM TOOLS!!! And not with Minimal fastboot or 15 seconds Adb installer.
The default Stock ROM has the data encrypted and gives problems when starting recovery when installed but not when it is started temporarily. You can try doing "Format data" from the Normal TWRP and then try installing other Custom Recovery. I have had this problem in the past and solved it with fastboot -w but I have not tested format data with TWRP.
P.S: This also happens with Roma encrypted with FBE. (eg PE Fan Edition)
TWRP 4pda is compatible with FBE
Click to expand...
Click to collapse
What happens when I use the fastboot -w
Can I use this fastboot -w command without formatting data, becouse I formatted everything when coming from the stock rom / unlocking the bootloader.
Can I get your recoveries img file, the zip doesn't contain a img version
Nikhil Chandran said:
What happens when I use the fastboot -w
Can I use this fastboot -w command without formatting data, becouse I formatted everything when coming from the stock rom / unlocking the bootloader.
Can I get your recoveries img file, the zip doesn't contain a img version
Click to expand...
Click to collapse
I am about to release an update of the SHRP and I will add the img.
Fastboot -w will format data and decrypt too.
XRed_CubeX said:
I am about to release an update of the SHRP and I will add the img.
Click to expand...
Click to collapse
May I know when?.
Cuz I'm going to format everything and start over
Nikhil Chandran said:
May I know when?.
Cuz I'm going to format everything and start over
Click to expand...
Click to collapse
Now, check out sourceforge
XRed_CubeX said:
Now, check out sourceforge
Click to expand...
Click to collapse
Thanks I'll check with the fastboot -w command
To fix the issue
Update:
Tried to boot via fastboot command it's stuck on the logo ( haven't tried fastboot -w command yet).
Twrp is booting without an issue
Nikhil Chandran said:
Thanks I'll check with the fastboot -w command
To fix the issue
Update:
Tried to boot via fastboot command it's stuck on the logo ( haven't tried fastboot -w command yet).
Twrp is booting without an issue
Click to expand...
Click to collapse
Do fastboot -w
XRed_CubeX said:
Do fastboot -w
Click to expand...
Click to collapse
Just formatted everything and also used the fastboot -w command and now everything works fine. The only thing left is that learning about the 2 slots. Also everytime I flash something like magisk or save a screenshot a red error line appears saying "failed to mound '/vendor ' (device or resource busy)
this is normal, it means that the vendor partition was used after a flash and recovery should be restarted
Nikhil Chandran said:
Just formatted everything and also used the fastboot -w command and now everything works fine. The only thing left is that learning about the 2 slots. Also everytime I flash something like magisk or save a screenshot a red error line appears saying "failed to mound '/vendor ' (device or resource busy)
Click to expand...
Click to collapse
About a/b and so forth:
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Phil_Smith said:
About a/b and so forth:
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
Thanks the guide was very helpfull :laugh:
Best custom recovery
I was searching a custom recovery, when i try these i love it !!!!!
GOOD JOB!!!!:good::good::good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Free Bootloader unlock for Nokia 7.2
Well , after 2 years finally the dream come true. yes , we achieved what we seen in the title of my thread. atlast free bootloader unlock for Nokia 7.2 running on any android version especially android 10 & upcoming android 11 as well.
So what is the magic behind free bootloader unlock? Yes ! Iam not gonna reveal that but yes as a Nokia community Developer this is what I can provide for your all.
A big massive thank you for my back-end team @hikari_calyx , @singhnsk & especially My Nokia 7.2 & 6.2 community for strong support behind the journey.
So what is the exact steps to make it successfull on your Phone.
1. Make sure you own Nokia 7.2 device & computer running on linux or windows
2. Connect phone to computer & enable developer options
3. Enable usb debugging
4. Download adb platform tools latest from Google & Open command prompt , type adb devices
5. Type adb reboot recovery
6. Make sure your device should boot in to stock recovery & Select apply update from adb
7. in cmd type adb sideload DDV_XYZ.zip ( Select package accordingly to your variant. Example for indians DDVA_sprout , for Russian DDV & for global DDV_sprout )
8. Wait for 5 minutes to complete the flashing process on locked bootloader.
9. After flashing completed Select reboot to bootloader
10. Type fastboot devices
11. Type fastboot flashing unlock_critical ( see the phone and select unlock the Bootloader using volume buttons and press power button )
12. Reboot to fastboot again make sure to use volume down and power button at a time for fastboot mode.
13. type fastboot flashing unlock ( see the phone and select unlock the Bootloader using volume buttons and press power button )
Finally Congratulations we successfully completed bootloader unlock.
Now what next? Just reflash stock rom from fastboot accordingly to my stock rom flash tool thread.
Thank you !!
• Download Sideload Packages
• Download adb platform tools
• Stock rom flash tool thread
Very cool. Is this also going to work for Nokia 6.2?
you_ser said:
Very cool. Is this also going to work for Nokia 6.2?
Click to expand...
Click to collapse
yup on the way in few hours
I successfully unlocked and my 7.2 today and faced no problems. The whole process ran flawlessly, thanks for making this possible and keep doing good work.
Amazing ! was waiting for this since forever as couldnt spend money, succesfuly unlocked the bootloader on my nokia 7.2 without any issues thnx a ton to the whole development team. Just follow the instructions
WORKS FINE
ON ANDROID 10
(NOKIA 7.2)
YES, IT DOES WORKS THANK YOU SO MUCH AND KUD
DOS TO THE DEVELOPERS.
I MANAGED TO UNLOCK IT FOR FREE
UNLOCKED MY BOOTLOADER
USING NOKIA 7.2 ON ANDROID 10 WITH INDIAN VARIENT DDVA_sprout.zip update package.
Just follow the steps and it will be just fine
Also I would like to mention that in my case I didn't needed to flash stock rom, it booted normally after few "corrupted file" warnings so skipped the "Stock Rom flash tool threads"... I just let it boot few times 4-7 times max and it booted after that with nokia logo.
Great work! Hope the development grow well for Nokia 7.2 & 6.2!
I only get the message "No Command" after I type `adb reboot recovery`. Is there any other method to get into stock recovery?
zwinca said:
I only get the message "No Command" after I type `adb reboot recovery`. Is there any other method to get into stock recovery?
Click to expand...
Click to collapse
When you see no command. Then press & hold power button and press volume up button then it automatically goes to recovery mode.
Raghu varma said:
When you see no command. Then press & hold power button and press volume up button then it automatically goes to recovery mode.
Click to expand...
Click to collapse
worked like a charm...thank you. nice work
Doesn't work . I am at step 8 and 9, typing
fastboot devices
fastboot flashing unlock_critical, but there is no option called "unlock", only start - restart bootloader - recovery mode - power off - boot to ffbm - qmmi.
whats going on?
edit: stuck at this point:
edit 2" ok, i understand now that the phone should ask for confirmation, but it doesnt.
Wi-Fi is not working with Magisk installed
Ujwal2000 said:
Wi-Fi is not working with Magisk installed
Click to expand...
Click to collapse
So, what was the solution to your problem? Maybe it will help me?
Thanks.
P.G.R. said:
Doesn't work . I am at step 8 and 9, typing
fastboot devices
fastboot flashing unlock_critical, but there is no option called "unlock", only start - restart bootloader - recovery mode - power off - boot to ffbm - qmmi.
whats going on?
edit: stuck at this point:
edit 2" ok, i understand now that the phone should ask for confirmation, but it doesnt.
Click to expand...
Click to collapse
I have the same problem.
I found a solution. It was a driver problem. I installed Google, Inc. - Other hardware - Android Bootloader Interface from Windows Update and now ist works.
N7.2 said:
I found a solution. It was a driver problem. I installed Google, Inc. - Other hardware - Android Bootloader Interface from Windows Update and now ist works.
Click to expand...
Click to collapse
Thanks. Did similar thing on Linux and it worked (fighting with lineage rights now, its a mess).
Hi everyone,
I unlocked my nokia back then when a bug was still in one of the first android versions and there were an official option in my the dev options. (7.2)
Since then my device has been showing an warning alert when android is booting up. Is this still the case with this unlock procedure mentioned here? If yes, would it work for my to lock my device again and reunlock using this tool in this thread?
Regards,
no, the warning message is still there.
abdulrahmanna said:
Great work! Hope the development grow well for Nokia 7.2 & 6.2!
Click to expand...
Click to collapse
@Raghu varma please do it for nokia 6.1 plus
Ujwal2000 said:
Wi-Fi is not working with Magisk installed
Click to expand...
Click to collapse
It's not because of Magisk. On stock ROM, TWRP causes this issue. Instead of flashing Magisk using TWRP, you can flash Magisk patched (stock) boot img for rooting your device.
{Mod edit: Link removed}