Related
I have been tearing my hair out for about a week with this problem. I'm sure the answer is here somewhere, but I'm a novice and I don't understand phone developer vocabulary. Hopefully someone can link me to a solution to my problem.
I have a Verizon LG G2 (VS980 4G) and I'm trying to install CyanogenMod on it. Here's the info from the software page in settings:
Android version 4.4.2
Baseband version VS98024A-M8974A-AAAANAZM-2.0.20046
Kernel version 3.4.0-perf [email protected]
Build number KOT49I.VS98024A
Software version VS98024A
I have followed these steps so far:
1. Rooted with towelroot
2. Installed SuperSU and BusyBox
3. Used AutoRec to install TWRP 2.7.0.0
4. Downloaded CM-10.2.0-vs980.zip to /sdcard/Download
When I boot into TWRP recovery and try to flash the zip from there, I get the following error message:
"assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip'
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip' "
And then when I try to reboot the system I get an error that shows the LG logo with the words "security error" underneath it, and the phone won't boot up. After that my only option is to do a factory hard reset, go back into TWRP and restore my backup.
When I bought the phone it was on Software version VS98027A, but I thought that might be the problem so I used the LG flash tool to download and flash the kdz file for VS98024A. This has not given me a new result, sadly.
I have read the install instructions on the CM page, but they describe an app called FreeGee, which I guess is supposed to install ClockworkMod. FreeGee says my phone isn't supported. CM's directions say if FreeGee doesn't work, I should use AutoRec, but they don't follow up with any TWRP-specific instructions. I have googled and youtubed for several days, but everything I find shows directions on how to root and install recovery, yet nothing on how to deal with this particular error message. Whenever I do find a thread that seems like it might be helpful, I can't understand the technical jargon involved.
Thanks in advance for any advice you can give.
Hardley97 said:
I have been tearing my hair out for about a week with this problem. I'm sure the answer is here somewhere, but I'm a novice and I don't understand phone developer vocabulary. Hopefully someone can link me to a solution to my problem.
I have a Verizon LG G2 (VS980 4G) and I'm trying to install CyanogenMod on it. Here's the info from the software page in settings:
Android version 4.4.2
Baseband version VS98024A-M8974A-AAAANAZM-2.0.20046
Kernel version 3.4.0-perf [email protected]
Build number KOT49I.VS98024A
Software version VS98024A
I have followed these steps so far:
1. Rooted with towelroot
2. Installed SuperSU and BusyBox
3. Used AutoRec to install TWRP 2.7.0.0
4. Downloaded CM-10.2.0-vs980.zip to /sdcard/Download
When I boot into TWRP recovery and try to flash the zip from there, I get the following error message:
"assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip'
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip' "
And then when I try to reboot the system I get an error that shows the LG logo with the words "security error" underneath it, and the phone won't boot up. After that my only option is to do a factory hard reset, go back into TWRP and restore my backup.
When I bought the phone it was on Software version VS98027A, but I thought that might be the problem so I used the LG flash tool to download and flash the kdz file for VS98024A. This has not given me a new result, sadly.
I have read the install instructions on the CM page, but they describe an app called FreeGee, which I guess is supposed to install ClockworkMod. FreeGee says my phone isn't supported. CM's directions say if FreeGee doesn't work, I should use AutoRec, but they don't follow up with any TWRP-specific instructions. I have googled and youtubed for several days, but everything I find shows directions on how to root and install recovery, yet nothing on how to deal with this particular error message. Whenever I do find a thread that seems like it might be helpful, I can't understand the technical jargon involved.
Thanks in advance for any advice you can give.
Click to expand...
Click to collapse
Here's my advice, go back to stock again,the LG flash tool. When that completes, use Freedom Tools (its in Development) and use ioroot25 (link is in the aforementioned thread) to root device. Then use Freedom Tool to install twrp. I've used it many times and never had a problem. Re-download cm rom (perhaps bad download) and flash in twrp. I would suggest using a more current twrp (start with 2.7, DL newest twrp, flash, reboot recovery) then flash cm. Let me know how it goes!
Thanks for your help. I followed the ioroot and freedom tool steps no problem, but I don't know how to update twrp. The g2 isn't listed as a supported device on their website or in the twrp manager app. I searched the forum and found a thread about updating it, but every time I try to download the files, I get a message that says the download failed.
I downloaded a fresh copy of cyanogenmod and tried to flash with twrp2.7, but I got the same error message from my original post.
Hardley97 said:
Thanks for your help. I followed the ioroot and freedom tool steps no problem, but I don't know how to update twrp. The g2 isn't listed as a supported device on their website or in the twrp manager app. I searched the forum and found a thread about updating it, but every time I try to download the files, I get a message that says the download failed.
I downloaded a fresh copy of cyanogenmod and tried to flash with twrp2.7, but I got the same error message from my original post.
Click to expand...
Click to collapse
Huh, ok, well, first off here's the thread for twrp, make sure and flash the correct one for our device:
http://forum.xda-developers.com/showthread.php?t=2898705
Second, have you tried a different rom? I remember reading that jackpotcalvin's is the cm to use. Try his or a completely different one, just make sure and follow the op (some require different radios, just follow the op). But I would definitely upgrade twrp before trying anything else.
njstein said:
Huh, ok, well, first off here's the thread for twrp, make sure and flash the correct one for our device:
http://forum.xda-developers.com/showthread.php?t=2898705
Second, have you tried a different rom? I remember reading that jackpotcalvin's is the cm to use. Try his or a completely different one, just make sure and follow the op (some require different radios, just follow the op). But I would definitely upgrade twrp before trying anything else.
Click to expand...
Click to collapse
Okay, so thanks to the link you gave me, I have succeeded in updating TWRP to version 2.8.5.1. I tried once again to flash cm 10.2, with more error messages. Specifically, the error says:
assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip' (that line was in red text)
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip'
I chose that rom because it is the only one listed as stable on the CM page for the G2. This time it was a fresh download. After that failed, I looked up JackpotClavin and found this thread:
http://forum.xda-developers.com/showthread.php?t=2702958
But it might as well be written in Greek because I don't understand much of it at all. I don't think I'd be comfortable doing all the command line stuff without a video tutorial or a more layman-friendly set of directions. So I didn't try that one.
Then I just started browsing the Development forum for a rom with easy install directions and found this one:
http://forum.xda-developers.com/verizon-g2/development/rom-beanstalk-build-5-0015-t3001584
I followed the instructions and flashed it successfully, booted up successfully, and then I was bombarded with a never-ending series of popups that said Unfortunately, Google Play Services had stopped. So that Rom was unusable, but at least now I know that it is possible to flash a rom of some kind. I don't have my heart dead-set on CM, I just know that it's very popular and so I had hopes that it would be more stable than most. All I need is a stable rom that has working radios and the ability to use the native USB tether function without having to pay Big Red an extra fee for the privilege.
I have restored to stock 24A with TWRP 2.8.5.1. Any more pointers?
Thanks again for all your help. I can tell I'm making progress, just not sure how close I am to the light at the end of the tunnel.
Hardley97 said:
Okay, so thanks to the link you gave me, I have succeeded in updating TWRP to version 2.8.5.1. I tried once again to flash cm 10.2, with more error messages. Specifically, the error says:
assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip' (that line was in red text)
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip'
I chose that rom because it is the only one listed as stable on the CM page for the G2. This time it was a fresh download. After that failed, I looked up JackpotClavin and found this thread:
http://forum.xda-developers.com/showthread.php?t=2702958
But it might as well be written in Greek because I don't understand much of it at all. I don't think I'd be comfortable doing all the command line stuff without a video tutorial or a more layman-friendly set of directions. So I didn't try that one.
Then I just started browsing the Development forum for a rom with easy install directions and found this one:
http://forum.xda-developers.com/verizon-g2/development/rom-beanstalk-build-5-0015-t3001584
I followed the instructions and flashed it successfully, booted up successfully, and then I was bombarded with a never-ending series of popups that said Unfortunately, Google Play Services had stopped. So that Rom was unusable, but at least now I know that it is possible to flash a rom of some kind. I don't have my heart dead-set on CM, I just know that it's very popular and so I had hopes that it would be more stable than most. All I need is a stable rom that has working radios and the ability to use the native USB tether function without having to pay Big Red an extra fee for the privilege.
I have restored to stock 24A with TWRP 2.8.5.1. Any more pointers?
Thanks again for all your help. I can tell I'm making progress, just not sure how close I am to the light at the end of the tunnel.
Click to expand...
Click to collapse
Dude, I'm sorry for not reading closer to begin with, but ya, you're trying to flash a JB rom with a KK recovery. 2.7 and up are for kk only. I'm so sorry...
Did you flash a gapps zip with Beanstalk? Did you do a completely clean install?
If you still want to flash a 10.2 cm you're going to have to find the appropriate recovery, and there I'm of no use since I entered this phone on kk and don't know anything about its jb history. Also don't know about the USB tether part either (I don't use it) so you're probably going to have to do some searching, flashing, and experimentation.
But bright side is we've figured out why you couldn't flash the cm rom. Either stay on kk or above, or start scrolling through the dev section looking for jb recovery...
SUCCESS!
Last night I read a bit deeper into the CM11/12 thread and found a more noob-friendly breakdown of the directions on pages 4-6. I worked up my courage to dive into adb and it turned out to be easier than it looked. Another failed flash on the CM10.2 ROM left little doubt that the rom had to be the problem, and your last reply confirmed it. I went back to the CyanogenMod download page and grabbed a zip of CM11 and now I'm up and running!
Thank you so much again. I sent a donation to JackpotClavin, and I'd like to do so for you as well, if I could. I don't see a PayPal link in your signature, though.
Hardley97 said:
SUCCESS!
Last night I read a bit deeper into the CM11/12 thread and found a more noob-friendly breakdown of the directions on pages 4-6. I worked up my courage to dive into adb and it turned out to be easier than it looked. Another failed flash on the CM10.2 ROM left little doubt that the rom had to be the problem, and your last reply confirmed it. I went back to the CyanogenMod download page and grabbed a zip of CM11 and now I'm up and running!
Thank you so much again. I sent a donation to JackpotClavin, and I'd like to do so for you as well, if I could. I don't see a PayPal link in your signature, though.
Click to expand...
Click to collapse
So glad it worked for you and you're up and running!
Nah, bro, I'm good. Give it to the devs, they deserve it. Giving knowledge through experience is what xda is all about, pass it on when you can. Thank you, though!
Deleted
bubba1601 said:
Hi
I have this new device but it's not any of the versions listed here (Nora/Rhyanna)
It's the UK version XT1920-15 sim unlocked, I'm just wandering if the steps to unlock/root are the same on this device as the other versions?
Click to expand...
Click to collapse
https://www.getdroidtips.com/unlock-bootloader-moto-e5-play/
I used this guide to unlock it. I also have this phone, but mine is from latin america, and it should work for yours. :good:
Deleted
bubba1601 said:
Your device is not the same.
The American / latin American version has android 8.0, 2 GB ram and a 5.2 inch screen.
The UK version has android 8.1, 1gb of ram and a 5.3 inch screen.
All such tutorials that work for the US version DON'T work on the UK version and TWRP installation fails completely.
Please be mindful when advising users things "should" work, as it doesn't work and your device is completely different to mine, so should not be attempted from that link.
Click to expand...
Click to collapse
No my phone has 1Gb of Ram and 16gigs of storage space along with 8.1 and TWRP installed. I used that guide to unlock the bootloader the TWRP in that guide doesn't work for our phones. I managed to find the TWRP version of the phone.
Deleted
bubba1601 said:
The guide says it's for android 8.0 though?
I still can't unlock the bootloader!
Click to expand...
Click to collapse
fastboot oem get_unlock_data
"Now command will return a string which you need to copy the string to a notepad with a single line by deleting all spaceNotepad
(Note: Only copy the highlighted sections above. Do not copy the INFO or (bootloader) prefix)"
"To Get Bootloader Key for Moto E5 Play - Open the website Motorola’s unlock the bootloader site by Signing up or Log in in via Google Plus account"
Link:https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
Make an account, also check if your device can even be unlocked on the website.
"Once you click the "Can my Device be unlocked?" you will receive a mail with unlock key.
Now copy the unlock key and type the following command and enter.
fastboot oem unlock UNLOCK_KEY
Here UNLOCK_Key is the place where you have to paste the unlock key which you copied from the email.
That's it! Your device will unlock. hah! Have fun!"
That's how you unlock the boot loader
Link for TWRP for PETTYL:https://mega.nz/#!anwAACZT!MJ95FCiIDH-kkLaZLpFvnKT5j_3Fe2goU-aZmSVeCKo
I couldn't find on XDA so I uploaded it to mega.
Deleted
Here a twrp buckup Twrp image and rooted boot for XT1920-15 if you manage to boot into twrp or try booting boot image https://drive.google.com/drive/u/0/mobile/folders/1P0yVep9l3yTN2Hzy7QiRXj3kuL_N7Dxz?usp=sharing
did the op get it sorted
Deleted
bubba1601 said:
I'm running stock again.
No root, no twrp and as far as I'm concerned, project treble ROMs/images are complete waste of time, especially for this device where half the posted steps don't work, supplied resources don't work or twrp images and twrp back ups supposedly for this device don't work
Worse still, I had to pay to redownload my firmware.
Click to expand...
Click to collapse
No idea why it dosent work for you I maneged to flash twrp and root it with magisek also tried linege and ResurexionRemix it works fine only xposed dosent work
Deleted
plscotland said:
Here a twrp buckup Twrp image and rooted boot for XT1920-15 if you manage to boot into twrp or try booting boot image https://drive.google.com/drive/u/0/mobile/folders/1P0yVep9l3yTN2Hzy7QiRXj3kuL_N7Dxz?usp=sharing
Click to expand...
Click to collapse
Can I flash this Recovery to XT1920-16 pettyl?
The file Moto_E5_XT1920-15-recovery.img is TWRP or STOCK recovery?
Also i'm loocking for Stock recovery for XT1920-16
Deleted
I just build custom recovery for pettyl -- ORANGE FOX , download at orangefox.tech
thanks. enjoy!
~whodat aka flash
Deleted
bubba1601 said:
There's already three different TWRPs for PETTYL.....two work one doesn't.
I made a TWRP for pettyl and it works 100% , The reason the others do not work is because they have EXT4 filesystem set to data partitions in the fstabs they were made with. Data partition is set to f2fs and thus it cannot be read. I also made a decrypt.zip for pettyl aswell, and I do not even own this device... I have only dove into android dev less than 2 months ago
Many people are already confused about twrp so do we really need another one to confuse everyone even more?
Click to expand...
Click to collapse
*triple facepalm* are you serious ?!?!
Maybe this site and android modifications is not for you bubba.
---------- Post added at 12:44 PM ---------- Previous post was at 12:32 PM ----------
bubba1601 said:
The comment you quoted says it's a TWRP file and I've not seen the stock recovery available for PETTYL .
Just bear in mind that I'm assuming the xt1920-15 that I have and txt1920-16 you have are identical, but I obviously cannot confirm that or do I know if they work the same I'm just assuming they do.
Click to expand...
Click to collapse
lol to get stock recovery file all you have to do is fastboot boot TWRP or OrangeFox and make a backup of recovery. Its that simple, but what would anyone want with stock recovery anyway?
If you really want it you can get the full stock firmware here, extract it and you will have stock recovery.img along with stock boot.img and everything else....
https://mirrors.lolinet.com/firmware/moto/pettyl/official/
Again, ENJOY!
Deleted
bubba1601 said:
If you had explained what's better or different about your recovery rather than making a mocking reply I would not have asked if another custom recovery was necessary......
There's currently two working TWRPs for PETTYL and another posted on here that doesn't work at all.
Every PETTYL user that's posted here has had issues with both TWRP versions or have been unable to follow the instructions on how to install either version.
Don't tell me this site and android modding isn't for me, because when the time is right I'll decide to stop, you will not make that decision or suggest I stop because you didn't like my question - which you didn't answer.
So I'll ask you calmly and politely again.
Is it really necessary to have so many different TWRPs and custom recovery for PETTYL?
What does your orange fox offer different to TWRP?
You haven't even posted a proper link......no explanation, no proceedures, no instructions. Nothing.
Explain yourself so people understand, don't mock.
Edit.
My question was not a criticism of what you have done.
I've stopped any further modifications to my own PETTYL because it's obvious a 1gb ram android go device cannot handle 9.0 pie and in the 10 years I've been modding various devices the E5 play is the most complicated piece of S*** I've I've used.
But even worse, if the user base cannot ask a simple question of people without someone like you being rude and sarcastic in reply and telling a fellow user to go away - then I've made the right decision not to work with my E5 or this thread any longer.
The user and support base for the E5 play PETTYL has suddenly hit an all time low, and doesn't need rudeness or your sarcasm to justify its existence..
Click to expand...
Click to collapse
He explained y other recoveries had prob and y his wouldn't next it has added features such as built in magisk and etc. test it to see other extra features instead of being a lil upset and taking it out on ppl being nice and fixing ur recovery probs
bubba1601 said:
If you had explained what's better or different about your recovery rather than making a mocking reply I would not have asked if another custom recovery was necessary......
There's currently two working TWRPs for PETTYL and another posted on here that doesn't work at all.
Every PETTYL user that's posted here has had issues with both TWRP versions or have been unable to follow the instructions on how to install either version.
Don't tell me this site and android modding isn't for me, because when the time is right I'll decide to stop, you will not make that decision or suggest I stop because you didn't like my question - which you didn't answer.
So I'll ask you calmly and politely again.
Is it really necessary to have so many different TWRPs and custom recovery for PETTYL?
What does your orange fox offer different to TWRP?
You haven't even posted a proper link......no explanation, no proceedures, no instructions. Nothing.
Explain yourself so people understand, don't mock.
Edit.
My question was not a criticism of what you have done.
I've stopped any further modifications to my own PETTYL because it's obvious a 1gb ram android go device cannot handle 9.0 pie and in the 10 years I've been modding various devices the E5 play is the most complicated piece of S*** I've I've used.
But even worse, if the user base cannot ask a simple question of people without someone like you being rude and sarcastic in reply and telling a fellow user to go away - then I've made the right decision not to work with my E5 or this thread any longer.
The user and support base for the E5 play PETTYL has suddenly hit an all time low, and doesn't need rudeness or your sarcasm to justify its existence..
Click to expand...
Click to collapse
Don't be a d*$k lashing out at a dev who does this work FOR free using up HIS free time to make it possible for you to make this complaint. We developers have to research to gain this knowledge. Be courteous and try to search the web to find the answers you seek and to fill in the blanks. Possibly guide others users in the right direction based on the knowledge you discover.
Don't bite the hand that feeds you. Listen to some nine inch nails, you might learn a thing or two about how to properly human.
He doesn't even own that device yet goes out of his way to provide support for it just for ungrateful individuals such as yourself to lash out at him for not explaining things clearly enough. If you lack the knowledge to fill in the blanks that he may have missed, that just shows that you're at risk of bricking your device from lack of knowledge on the subject. It won't hurt you to do a bit of research for yourself.
Sincerely,
The guy helping to guide that developer you lashed out at to supporting 64bit for YOUR DEVICE.
I have a pixel 4 xl unlocked, the issue I am facing is when I try to add apn with dun it will not allow me to save I am on at&t is there a way to work around this? I would like not to root until it's got twrp to flash aosp ROMs .
Thanks for any help
kushman said:
I have a pixel 4 xl unlocked, the issue I am facing is when I try to add apn with dun it will not allow me to save I am on at&t is there a way to work around this? I would like not to root until it's got twrp to flash aosp ROMs .
Thanks for any help
Click to expand...
Click to collapse
You are going to have to root to do the tethering bypass. Also, so you know user bigbiff has made TWRP work on our phones and it's completely functional in it's 5th beta now. It works great and you can flash any AOSP ROM with it.
1dopewrx05 said:
You are going to have to root to do the tethering bypass. Also, so you know user bigbiff has made TWRP work on our phones and it's completely functional in it's 5th beta now. It works great and you can flash any AOSP ROM with it.
Click to expand...
Click to collapse
Thanks I'm going to have to try although like I said in the twrp thread when he told me they are all side load idk what that mean to me that means put a apk on and card and install it lol this Is a bit more to it th b good ole htc 10 days. I also noticed there isn't really good instructions for people to root and "side load" ROMs. Either detailed steps in writing or detailed steps in a video on how to do all don't exist
kushman said:
Thanks I'm going to have to try although like I said in the twrp thread when he told me they are all side load idk what that mean to me that means put a apk on and card and install it lol this Is a bit more to it th b good ole htc 10 days. I also noticed there isn't really good instructions for people to root and "side load" ROMs. Either detailed steps in writing or detailed steps in a video on how to do all don't exist
Click to expand...
Click to collapse
Okay, so the "traditional" sideloading we used to have to do for a custom rom is extremely easy and only requires super basic ADB comprehension. As for installing a custom rom now, you don't even need to worry about sideloading, all you need to do is boot the TWRP.img that I told you about and once in TWRP you can install the custom rom right through there with just a tap or two.
I think you may be confused with how to get into TWRP, you Don't need to side load the TWRP image, you just need to fastboot boot the image. Ex: boot your device into the bootloader with the command: adb reboot bootloader
Then from bootloader use command: fastboot boot "location of TWRP.img you download on your computer"
Once running that command, you'll be in TWRP and can continue to flashing a custom rom.
Hi,
I just happened to google how to unlock Nokia 7 Plus' bootloader again and stumbled upon this site:
[Guide] How to unlock the bootloader on Nokia Android Phones for free
Detailed guide to help you unlock the bootloader of your Nokia Android device. You can unlock bootloader on many Nokia smartphones, including Nokia 7 Plus, Nokia 8, Nokia 8 Sirocco, Nokia 8.1, Nokia 7, Nokia 6, Nokia 6.1, Nokia 5, Nokia 2, Nokia 2.1. etc.
www.techmesto.com
It was updated today with a free way to generate bootloader unlock keys for Nokia 7 Plus apparently. Now I can't test this myself at the moment (in a week at earliest), but do you think this is legit?
At least I can generate a code apparently, so this part is actually free.
Hello,
has anyone tried this unlocker, because I'd like to use it, but since I use my nokia 7 plus as my primary phone I'd like to have some confirmations before using it
I use my Nokia 7 Plus as primary phone as well, but I guess I'll just risk it
However, I can't promise anything here. Hopefully I will get around to it within the coming week.
I tried it yesterday and it work flawlessly.
Just follow the steps on the page, I had no issues unlocking the bootloader.
That being said, I nearly bricked my device when trying to flash Lineage OS onto it (because all TWRP and Lineage OS step by step guides seem to be out of date?), but this guide helped me get back to stock: https://forum.xda-developers.com/t/...m-flash-tool-nokia-7-plus-b2n_sprout.4023961/
Might keep it handy if you are like me
Znert said:
I tried it yesterday and it work flawlessly.
Just follow the steps on the page, I had no issues unlocking the bootloader.
That being said, I nearly bricked my device when trying to flash Lineage OS onto it (because all TWRP and Lineage OS step by step guides seem to be out of date?), but this guide helped me get back to stock: https://forum.xda-developers.com/t/...m-flash-tool-nokia-7-plus-b2n_sprout.4023961/
Might keep it handy if you are like me
Click to expand...
Click to collapse
Thanks for the useful infos.
I suppose I will unlock my phone in the upcomming months but right now I just factory resetted it and it's working almost nicely.
I really want to unlock and flash a custom rom on my phone, because the stock rom it's buggy and tends to have some performance issues, but right now if I mess with it I can't afford to change the phone so I guess I'll have to wait.
Znert said:
I tried it yesterday and it work flawlessly.
Just follow the steps on the page, I had no issues unlocking the bootloader.
That being said, I nearly bricked my device when trying to flash Lineage OS onto it (because all TWRP and Lineage OS step by step guides seem to be out of date?), but this guide helped me get back to stock: https://forum.xda-developers.com/t/...m-flash-tool-nokia-7-plus-b2n_sprout.4023961/
Might keep it handy if you are like me
Click to expand...
Click to collapse
Do you have any tips on flashing TWRP? Thanks!
I have unlocked bootloader, tried to install TWRP from https://twrp.me/nokia/nokia7plus.html
fastboot flash recovery twrp.img
Output:
target reported max download size of 402653184 bytes
sending 'recovery' (42644 KB)...
OKAY [ 1.274s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.298s
GenericAsianGuy said:
Do you have any tips on flashing TWRP? Thanks!
Click to expand...
Click to collapse
Yeah, the tutorials seem to be a little outdated...
In general, follow this guide here (its from the same person that created the official twrp.me site I believe):
[CLOSED][OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7 Plus | Onyx |
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...
forum.xda-developers.com
I wasn't sure if I have a OOB or POB device, but I haven't had any issues using both (currently using OOB since I'm pretty sure my Nokia 7 Plus is that old )
Secondly, what the instruction somehow failed to mention is how to get the install.zip. It is on their sourceforge page in a subfolder:
B2N_sprout - Browse /TWRP-TEN/OOB at SourceForge.net
sourceforge.net
This is for the OOB variant, you can replace OOB at the end with POB to get the other files
You can verify, that I'm sending you the right link by following the links from the forum post to download the image to boot from. For example:
https://sourceforge.net/projects/b2n-sprout/files/TWRP-TEN/POB/twrp-3.4.0-0-B2N_sprout-POB-10.0-20200829.img/download
Now you can just remove the "twrp-3.4.0-0-B2N_sprout-POB-10.0-20200829.img/download" part of the URL and you get to the folder where all the other images are located. Download the latest "twrp-installer-*.zip" for your device and install it.
Znert said:
Yeah, the tutorials seem to be a little outdated...
In general, follow this guide here (its from the same person that created the official twrp.me site I believe):
[CLOSED][OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7 Plus | Onyx |
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...
forum.xda-developers.com
I wasn't sure if I have a OOB or POB device, but I haven't had any issues using both (currently using OOB since I'm pretty sure my Nokia 7 Plus is that old )
Secondly, what the instruction somehow failed to mention is how to get the install.zip. It is on their sourceforge page in a subfolder:
B2N_sprout - Browse /TWRP-TEN/OOB at SourceForge.net
sourceforge.net
This is for the OOB variant, you can replace OOB at the end with POB to get the other files
You can verify, that I'm sending you the right link by following the links from the forum post to download the image to boot from. For example:
https://sourceforge.net/projects/b2n-sprout/files/TWRP-TEN/POB/twrp-3.4.0-0-B2N_sprout-POB-10.0-20200829.img/download
Now you can just remove the "twrp-3.4.0-0-B2N_sprout-POB-10.0-20200829.img/download" part of the URL and you get to the folder where all the other images are located. Download the latest "twrp-installer-*.zip" for your device and install it.
Click to expand...
Click to collapse
This is great, thank you so much! I can also boot from both OOB and POB, will try this out later today
EDIT: worked like a charm. Thanks again!
Great! Glad I could help!
Hi @Znert, did you use TWRP for Android 10 or Android 11?
Another question: can I unlock the bootloader of a Nokia 7+ on Android 10?
Thank you again.
Radder124 said:
Hi @Znert, did you use TWRP for Android 10 or Android 11?
Another question: can I unlock the bootloader of a Nokia 7+ on Android 10?
Thank you again.
Click to expand...
Click to collapse
I use the Android 10 version, but I'm not sure what the difference is anyways (it's a bootloader, shouldn't that be OS independent?)
Regarding your second question, yes, I unlocked my bootloader with the latest official stock ROM (so Android 10).
Yes that's what I thought also... Maybe we need to use the Android 11 version to install a Android 11 ROM.
Now I see there is a new version of TWRP 3.5.2 on the official website.
Znert said:
I tried it yesterday and it work flawlessly.
Just follow the steps on the page, I had no issues unlocking the bootloader.
That being said, I nearly bricked my device when trying to flash Lineage OS onto it (because all TWRP and Lineage OS step by step guides seem to be out of date?), but this guide helped me get back to stock: https://forum.xda-developers.com/t/...m-flash-tool-nokia-7-plus-b2n_sprout.4023961/
Might keep it handy if you are like me
Click to expand...
Click to collapse
Can you tell me, has unlocking bootloader deleted your apps and data?
In my experience with every older fone, it does format it, but i wanna make sure.
Thanks in advance!
ghost baby said:
Can you tell me, has unlocking bootloader deleted your apps and data?
In my experience with every older fone, it does format it, but i wanna make sure.
Thanks in advance!
Click to expand...
Click to collapse
Yes, unlocking the bootloader will wipe your phone. As far as I know, this is true for all Android phones.
Deleted
Hello all, I have a stock Pixel 4 XL which has never been rooted. I did not even enable bootloader unlocking (which clearly I should've done).
Anyway, my phone a few days ago was installing a system update overnight and when I woke up it was on the black screen saying "Your device is corrupted and cannot be trusted".
I have tried to install factory images and OTA updates but because my device is locked, nothing is working.
I have also tried the Android Flash Tool and Pixel Recovery Tool but again, device is locked so nothing will flash.
Any ideas on how to fix this? Is it even possible?
PS: Funny how they don't want you to unlock the bootloader cause of safety reasons but if I had unlocked it, I could've easily fixed this phone already. Seems to do more harm than good.
McCullyCullen said:
Hello all, I have a stock Pixel 4 XL which has never been rooted. I did not even enable bootloader unlocking (which clearly I should've done).
Anyway, my phone a few days ago was installing a system update overnight and when I woke up it was on the black screen saying "Your device is corrupted and cannot be trusted".
I have tried to install factory images and OTA updates but because my device is locked, nothing is working.
I have also tried the Android Flash Tool and Pixel Recovery Tool but again, device is locked so nothing will flash.
Any ideas on how to fix this? Is it even possible?
PS: Funny how they don't want you to unlock the bootloader cause of safety reasons but if I had unlocked it, I could've easily fixed this phone already. Seems to do more harm than good.
Click to expand...
Click to collapse
You can try sideloading the full OTA image. Unlocked bootloader isn't required.
So download the OTA and do fastboot flash OTA OTAfilename?
McCullyCullen said:
So download the OTA and do fastboot flash OTA OTAfilename?
Click to expand...
Click to collapse
No, you use adb to sideload it. Get the OTA image you want from here.
Then follow the directions in this tutorial.
Lughnasadh said:
No, you use adb to sideload it. Get the OTA image you want from here.
Then follow the directions in this tutorial.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Okay I did that and got this:
ERROR: recovery: footer is wrong
Update package verification took 0.1 seconds (result 1)
ERROR: recovery: Signature verification failed
ERROR: recovery: error: 21
McCullyCullen said:
Okay I did that and got this:
ERROR: recovery: footer is wrong
Update package verification took 0.1 seconds (result 1)
ERROR: recovery: Signature verification failed
ERROR: recovery: error: 21
Click to expand...
Click to collapse
Are you sure you are sideloading the OTA image and not the factory image?
Lughnasadh said:
Are you sure you are sideloading the OTA image and not the factory image?
Click to expand...
Click to collapse
I downloaded this full OTA image.
13.0.0 (TP1A.220905.004, Sep 2022) for coral.
EDIT: I tired the build before this one (from Aug) and it got farther along than the Sep one but eventually failed because: recovery: update package is older than the current build.
Okay so for some reason the link directly from Google didn't work but the link from here did work!!
So I want to thank you Lughnasadh!
If anyone else comes across this issue, try the link from this website:
How to download Android 13 for Google Pixel and other Android devices
Google has officially kicked off the Android 13 QPR3's stable version rollout. You can download the release right now and give it a try!
www.xda-developers.com
Not sure why, but this version was 1.8gbs and worked,
the official one from Google was 2.2gbs and didn't work.
McCullyCullen said:
Okay so for some reason the link directly from Google didn't work but the link from here did work!!
So I want to thank you Lughnasadh!
If anyone else comes across this issue, try the link from this website:
How to download Android 13 for Google Pixel and other Android devices
Google has officially kicked off the Android 13 QPR3's stable version rollout. You can download the release right now and give it a try!
www.xda-developers.com
Not sure why, but this version was 1.8gbs and worked,
the official one from Google was 2.2gbs and didn't work.
Click to expand...
Click to collapse
You're welcome! Strange the one from the official site didn't work, but glad you got it going