Test installation failed (Moto G 1st) - LineageOS Questions & Answers

Hello all, I'm sure that's not the only topic about that kind of problem but I can't find anything here or in google (or DuckDuckGo), I hope you could understand after few hours of researchs I'm kinda bored...
Well I have lot of questions, I would love to use LineAgeOS but I'm really noob.
There is really not only one kind of solution, people on youtube don't presentate with the same way. Lot of indian youtubers show you how to install it on a phone where lineageos is already installed --' or when you find a guy he shows you, he doesn't show you what he did before with TWRP or how he booted the phone etc.
Well I begin :
Do I need to reboot my phone before install Lineage ?
If no, I have downloaded the version for my phone, I have TWRP, I have downloaded the flash for TWRP for the phone (what I don't know what to do with after). And then when I try to restart the phone in recovery, the logo of Android appeared with "no command".
I'm sorry for my english, that's not my native language.

LeVisage said:
Hello all, I'm sure that's not the only topic about that kind of problem but I can't find anything here or in google (or DuckDuckGo), I hope you could understand after few hours of researchs I'm kinda bored...
Well I have lot of questions, I would love to use LineAgeOS but I'm really noob.
There is really not only one kind of solution, people on youtube don't presentate with the same way. Lot of indian youtubers show you how to install it on a phone where lineageos is already installed --' or when you find a guy he shows you, he doesn't show you what he did before with TWRP or how he booted the phone etc.
Well I begin :
Do I need to reboot my phone before install Lineage ?
If no, I have downloaded the version for my phone, I have TWRP, I have downloaded the flash for TWRP for the phone (what I don't know what to do with after). And then when I try to restart the phone in recovery, the logo of Android appeared with "no command".
I'm sorry for my english, that's not my native language.
Click to expand...
Click to collapse
So your Problem has nothing to do with lineageOS. You can't install twrp! First make sure you download the correct official twrp for your device. Then follow the instructions on twrp page.

kurtn said:
So your Problem has nothing to do with lineageOS. You can't install twrp! First make sure you download the correct official twrp for your device. Then follow the instructions on twrp page.
Click to expand...
Click to collapse
I have downloaded TWRP.
After, I have download a file from TWRP for my phone it's a file .img and then I'm blocked

LeVisage said:
I have downloaded TWRP.
After, I have download a file from TWRP for my phone it's a file .img and then I'm blocked
Click to expand...
Click to collapse
Use fastboot method, if not rooted
https://twrp.me/motorola/motorolamotog2013.html
oops: firs unlock bootloader
https://wiki.lineageos.org/devices/falcon/install

kurtn said:
So your Problem has nothing to do with lineageOS. You can't install twrp! First make sure you download the correct official twrp for your device. Then follow the instructions on twrp page.
Click to expand...
Click to collapse
I have started following the "steps" from the twrp for Motorola after "Fastboot Install Method (No Root Required):"
I was never thinking it was so much hard. People in tuto dont do all of these.
I have to download Android SDK, to work with I have to download and install (what doestn't work) ADB drivers.
At a moment they dont say I have to connect my PC to my phone but when ?
I'm very bored about all those undescribed steps.

LeVisage said:
I have started following the "steps" from the twrp for Motorola after "Fastboot Install Method (No Root Required):"
I was never thinking it was so much hard. People in tuto dont do all of these.
I have to download Android SDK, to work with I have to download and install (what doestn't work) ADB drivers.
At a moment they dont say I have to connect my PC to my phone but when ?
I'm very bored about all those undescribed steps.
Click to expand...
Click to collapse
Yes. Windows is boring. I normally use Linux.

Related

LG G4 H815 No TWRP Access

Hello members of XDA,
The issue I'm having is pretty rare and found few or non threads about it, so I will try to be the most precise possible.
Yesterday I decided to change the ROM of my LG G4 H815, I was previously on LineageOS, since LineageOS on H815 wasn't developped anymore. So I asked myself why not trying Android Oreo with CypherOS. Before any changes I was with the latest version of LineageOS for H815 and I had TWRP with the version 3.0.2.1. Bootloader was obviously unlocked.
So I starded to download all the required material to switch to CypherOS 5.3.1, while the download I've made a backup of my actual lineageOS installation on my internal storage. Once every thing was downloaded I tried to install CypherOS I had an error 7 in TWRP install box, so I was pretty worried, scouted XDA threads about the error but i was redirected to the solution where you modify the update binary with txt but still didnt worked. I've found a thread talking about updating firmware of the H815 ( https://forum.xda-developers.com/g4/development/v5-8-5-n7-1-2-resurrection-remix-t3704450) While panicking I've done a wipe of everything (dalvik, data,cache and system) .I applied thge firmware update but I also re-read the thread of CypherOS and figured that I needed a newer version of TWRP, installed it so. THen magically CypherOS installed without any issue.
After installing the Gapps (Arm64 8.1 Nano) I rebooted and the first weird thing appears, after seeing the LG screen while the boot I have another screen telling me that the bootloader has been locked and that i should visit g.co/ABH for more information, then CypherOS initialise, CypherOS worked like a charm. So I wanted to go to my TWRP and make a backup in case. I launched ADB and use the command adb reboot recovery, the phone restarted and had the following events : LG logo, warning message about the bootloader, LG logo again and then a black screen. However I was in recovery mode since adb found me with the command fastboot devices. I had no TWRP logo or anything linked to it. Few minutes later, I had the basic recovery mode where you move yourself with the volume buttons and select with power where the functions are pretty limited.
Then I rebooted the phone with adb (fastboot reboot), CypherOS still working perfectly. Thaught that it was the bootloader which back to scratch when he was blocked, I figured out that he was still unlocked, I used the command "fastboot getvar unlocked" through ADB. THen I thaught i had to install back TWRP, tried through the fastboot mode but I had an error
Code:
FAILED (remote: unkown command)
since i tried everything i could even in the basic recovery mode, the only working command in the recovery is "fastboot flash recovery twrp.img" but still does nothing.
I mean it's not that terrible since I can use my phone and i'm about to change phone in 2 months for a Oneplus but i would really like to be able to install magisk on the phone to grant root access and be able to use TWRP on it like I used to. By the way the backup of lineageOS has been deleted while performing unecessary wipes.
Bennou said:
Hello members of XDA,
The issue I'm having is pretty rare and found few or non threads about it, so I will try to be the most precise possible.
Yesterday I decided to change the ROM of my LG G4 H815, I was previously on LineageOS, since LineageOS on H815 wasn't developped anymore. So I asked myself why not trying Android Oreo with CypherOS. Before any changes I was with the latest version of LineageOS for H815 and I had TWRP with the version 3.0.2.1. Bootloader was obviously unlocked.
So I starded to download all the required material to switch to CypherOS 5.3.1, while the download I've made a backup of my actual lineageOS installation on my internal storage. Once every thing was downloaded I tried to install CypherOS I had an error 7 in TWRP install box, so I was pretty worried, scouted XDA threads about the error but i was redirected to the solution where you modify the update binary with txt but still didnt worked. I've found a thread talking about updating firmware of the H815 ( https://forum.xda-developers.com/g4/development/v5-8-5-n7-1-2-resurrection-remix-t3704450) While panicking I've done a wipe of everything (dalvik, data,cache and system) .I applied thge firmware update but I also re-read the thread of CypherOS and figured that I needed a newer version of TWRP, installed it so. THen magically CypherOS installed without any issue.
After installing the Gapps (Arm64 8.1 Nano) I rebooted and the first weird thing appears, after seeing the LG screen while the boot I have another screen telling me that the bootloader has been locked and that i should visit g.co/ABH for more information, then CypherOS initialise, CypherOS worked like a charm. So I wanted to go to my TWRP and make a backup in case. I launched ADB and use the command adb reboot recovery, the phone restarted and had the following events : LG logo, warning message about the bootloader, LG logo again and then a black screen. However I was in recovery mode since adb found me with the command fastboot devices. I had no TWRP logo or anything linked to it. Few minutes later, I had the basic recovery mode where you move yourself with the volume buttons and select with power where the functions are pretty limited.
Then I rebooted the phone with adb (fastboot reboot), CypherOS still working perfectly. Thaught that it was the bootloader which back to scratch when he was blocked, I figured out that he was still unlocked, I used the command "fastboot getvar unlocked" through ADB. THen I thaught i had to install back TWRP, tried through the fastboot mode but I had an error since i tried everything i could even in the basic recovery mode, the only working command in the recovery is "fastboot flash recovery twrp.img" but still does nothing.
I mean it's not that terrible since I can use my phone and i'm about to change phone in 2 months for a Oneplus but i would really like to be able to install magisk on the phone to grant root access and be able to use TWRP on it like I used to. By the way the backup of lineageOS has been deleted while performing unecessary wipes.
Click to expand...
Click to collapse
It's clearly written on the official website and in the official TWRP support thread for the g4 what you have to do when on Nougat bootloader and want to flash TWRP... and keeping it.
Sent from my LG-H815 using XDA Labs
Yet, this still doesnt help me to solve my issue. Do you think there is a way to fix it or no ? If not, I'll just deal with it for the few months lasting.
Bennou said:
Yet, this still doesnt help me to solve my issue. Do you think there is a way to fix it or no ? If not, I'll just deal with it for the few months lasting.
Click to expand...
Click to collapse
Okay if it doesn't work for you you must do something wrong. It works 100%. If you really want help you should explain in detail exactly which steps you took as otherwise it's all just guessing what you're doing.
Sent from my LG-H815 using XDA Labs
Indeed, I didn't followed the procedure exactly, didn't do the step after flashing TWRP (removing battery and boot manually to recovery). Well thank you, was my bad on that.
Should I do a clean new install of cypheros or should I keep it like that, what would be your advice ? Knowing that at the moment CypherOS works like a charm. I also plan to install Magisk on it to root it.
To help others newbie like me, solution can be found here : https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424

TWRP recovery not working on Blackview BV9500

Hi everybody,
I try to root my Blackview BV9500 by installing first TWRP recovery. I use fastboot mode on a linux laptop to do that.
I successfully flash the twrp recovery image, but after that, the phone don't boot in recovery anymore.
It try to boot into recovery, but it reboot in normal mode a few second after.
I tried also with the cmd "fastboot boot recovery.img".
When i flash back the original recovery image, it work, i can boot the original recovery without any problem.
Does anyone have the problem?
Some one can help me to find a solution?
I, too, am trying to do this. I have not yet flashed it... I was going to use the fastboot boot command to boot the recovery kernel before permanently flashing it, to make sure it would work, and in my googling I stumbled across this post. Serendipity! [Edit 3: Although, reading your post again, I see you tried that as well and it didn't succeed for you. For me, it simply tells me remote: command not found, so how were you able to even get that to work?]
All that said... I have the BV9500 Pro, specifically for the two-way radio, so I'm going to try to keep that little tidbit of hardware working in the process. I mainly just want to tweak the menus a bit, tweak the quick settings, get root, delete the Google crapps I won't be using...
On to your problem, though, I can't help much but maybe if we post back and forth our successes and failures we might be able to stumble through it together?
First, I assume you already have unlocked your bootloader? [Edit: Honestly, I'm not sure flashing the recovery would be allowed without first unlocking the bootloader]
[Edit 2: Perhaps this thread might be of help. Different model, but often the hardwares used by manufacturers are similar enough that the same steps generally work. ]
Thank you for the link, maybe i need to flash the complete rom with the twrp recovery with spflash tools, and it will work.
I will try and let you know, but i will make a backup of my rom before flashing it!
For your problem with fastboot, maybee it's because you need to install it. You can use the command "sudo apt-get install fastboot" on a terminal window if you are on linux.
If you want to enter the recovery mode, you don't need to use fastboot, you can simply enter it by pressing Volume Up and Power buttons together for a couple of seconds when your phone is off.
When Boot Mode appears release all keys.
To flash recovery with fastboot, you need first to enable the developer mode on your phone (go to "Settings > About phone" and make 7th tap on the build number, the Developer options will be unlocked and available), and unlock the bootloader of course.
here what is the process i made to flash the recovery :
- i use the command "adb devices" to check if the phone is well connected. (response is like "BV9500S320001179 device")
- then i enter in fastboot mode with "adb reboot bootloader" (phone reboot and ask confirmation for fastboot mode)
- check with command "fastboot devices"
- unlock the bootloader with the command "fastboot oem unlock" or "fastboot flashing unlock".
- flash the phone with the twrp recovery with "fastboot flash recovery recovery.img"
- reboot the phone in recovery mode with "fastboot boot recovery.img"
Normally the phone boot in twrp recovery.
Hope that will help you too.
I am too facing this problem. In case you got any solutions please let me know too.
Yves596 said:
For your problem with fastboot, maybee it's because you need to install it. You can use the command "sudo apt-get install fastboot" on a terminal window if you are on linux.
Click to expand...
Click to collapse
Yup. Already had fastboot installed for the LG G5 this phone replaced, the Galaxy Note 4 the LG replaced, the MyTouch 4G Slide the Galaxy replaced, my wife's old Galaxy S5 I used in the interims... LOL, I've got a working install. No, the "Remote: command not found" was returned from within.... Whether fastboot or adb, I forget now, but I was able to get the file to flash eventually, after reading your first post, but unfortunately the phone would not boot to it (nor Android). I thought I'd bricked it. Twice this happened. Each time, after about 5 minutes, it eventually booted to Android.
I flashed the recovery from the ROM in the link Blackview sent me and was able to boot their recovery just fine, so there's something in the TWRP that my particular phone doesn't like.
If you want to enter the recovery mode, you don't need to use fastboot, you can simply enter it by pressing Volume Up and Power buttons together for a couple of seconds when your phone is off.
When Boot Mode appears release all keys.
Click to expand...
Click to collapse
Thanks, I keep forgetting which keys to hold for recovery versus bootloader, so I use the adb command to be sure without having to keep a notepad nearby.
Clearly I don't do this as often as I used to.
(snip)
- flash the phone with the twrp recovery with "fastboot flash recovery recovery.img"
- reboot the phone in recovery mode with "fastboot boot recovery.img"
Normally the phone boot in twrp recovery.
Hope that will help you too.
Click to expand...
Click to collapse
Now that was something I haven't done since the T-Mobile G1 days. My understanding was that you CAN boot a recovery without flashing it first if you"fastboot boot {image filename}" but that didn't work for me either. I'm also assuming that the filename to flash can be anything because the device stores it to a partition, so it shouldn't have to be specifically "recovery-verified.img".
The recovery you have... Were you ever able to boot to it? If so, would you be willing to share a link to its download source, please?
I've got to run for a prior engagement, I'll check back later.
Thanks!
veronicadavis said:
I am too facing this problem. In case you got any solutions please let me know too.
Click to expand...
Click to collapse
I guess i find the reason why the modified recovery image won't boot.
I find an interesting information in a post of osm0sis (https://forum.xda-developers.com/showthread.php?t=2073775) were he say : "some newer MediaTek (MTK) devices use special image signing that adds a "BFBF" pre-header signature, so images will unpack/repack but most likely won't boot unless run through their internal signing tool."
After more search, i find an interesting publication (http://www.lieberbiber.de/2015/07/04/mediatek-details-partitions-and-preloader/) witch confirm that.
They say in conclusion of the publication :
"Yes, I can confirm that SignTool is able to add digital signature information to firmware images. Signed images have an additional header “BFBF” and some fluff which SP Flash Tool checks on a secure device. Apparently some manufacturers merely used the default MTK key for signing the images, making them no better off than a typical insecure MTK device."
So we have to find another way to install magisk to root it.
Root 9500/pro
Mine rooted already....you guys can check on 4pda russian forum
Note : do not use the 17.1 version of magisk there because after reboot the device will freeze if you resboot after twrp 1st install...instead flash 17.3+ or 18+ right after first install of twrp...
EDIT : dont mind the russian language in TWRP as you can change it to english once there
Yves596 said:
Hi everybody,
I try to root my Blackview BV9500 by installing first TWRP recovery. I use fastboot mode on a linux laptop to do that.
I successfully flash the twrp recovery image, but after that, the phone don't boot in recovery anymore.
It try to boot into recovery, but it reboot in normal mode a few second after.
I tried also with the cmd "fastboot boot recovery.img".
When i flash back the original recovery image, it work, i can boot the original recovery without any problem.
Does anyone have the problem?
Some one can help me to find a solution?
Click to expand...
Click to collapse
Hello I have same problem... Do you have that original recovery file? I don't have and I would like to get that back. Thanks.
DL this:
needrom. com/ download/bv9500pro- bv9500-root/ (delete spaces)
- Copy Magisk-v18.0.zip and disable_encryption_9500.zip to external SD-Card or OTG device
- backup your data from internal SD-Card
- do a factory reset and turn off phone without entering the setup guide after reboot, or wipe via recovery and power off
- Flash recovery.img using scatter.txt with SP Flash Tool
- boot into recovery with hold down vol + and power
- switch TWRP to your language and install Magisk-v18.0.zip and disable_encryption.zip
- reboot and update or install MagiskManager-v6.1.0.apk
Thanks to Jemmini from 4pda.ru
kanadali said:
DL this:
needrom. com/ download/bv9500pro- bv9500-root/ (delete spaces)
- Copy Magisk-v18.0.zip and disable_encryption_9500.zip to external SD-Card or OTG device
- backup your data from internal SD-Card
- do a factory reset and turn off phone without entering the setup guide after reboot, or wipe via recovery and power off
- Flash recovery.img using scatter.txt with SP Flash Tool
- boot into recovery with hold down vol + and power
- switch TWRP to your language and install Magisk-v18.0.zip and disable_encryption.zip
- reboot and update or install MagiskManager-v6.1.0.apk
Thanks to Jemmini from 4pda.ru
Click to expand...
Click to collapse
Thank you for your help and Jemmini help too, it work fine.
But on the firmware version 20180629.
Yves596 said:
Thank you for your help and Jemmini help too, it work fine.
But on the firmware version 20180629.
Click to expand...
Click to collapse
you can just download latest firmware and simply backup NVRAM etc with sp flash tool also flash with sp tool, you will have then working twrp with disabled encryption. there are tons of post regarding using sp flash tool on this forum
im using same phone and did these actions on first day and did not have any problem with twrp or magisk
Hi,
I've bought this phone in Pro version. I rooted my phone using needrom.com/download/bv9500pro-bv9500-root/ and adb after unlocking bootloader. Then I failed with errors. Then I used SPFlashTool in root mode with official 2018092919_s32v63c2k_jk_pro.rar rom (I don't find it anymore on the net but 1) I got it on Blackview official forum and 2) I have the file on my own PC) with format+Download and replace recovery with TWRP from Jemmini from 4pda.ru before flashing. OK.
Then I rooted again: format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally.
Beware: TWRP is in Russian language at first boot, so to get it in English, first slide the first slide (allowing writing), then select 'Настройки', then the globe on top, then English, then 'Установитъ Язык'.
Hope this helps.
Then, this is my first rooted phone, so I plan to make a custom rom without Gapps (then maybe without Mediatek Ones and agold too) and remake all functionning with apps from Fdroid. Help needed on a manner of removing a system/vendor app properly. Help needed too to add V4A, as I could see max version supported is Nougat. I announce this here as my first post, but my project will be a full post. If someone want help please ask here or MP me
Note: an update of magisk is out (official 18.1), I installed it and my phone tells me a message that facial recognition was not working anymore then it only boots on TWRP... I reflashed it and my phone boots normally again. Wait and see...
Thanks to Jemmini from 4pda.ru again.
Bests Regards
nr0000000 said:
Hi,
I've bought this phone in Pro version. I rooted my phone using needrom.com/download/bv9500pro-bv9500-root/ and adb after unlocking bootloader. Then I failed with errors. Then I used SPFlashTool in root mode with official 2018092919_s32v63c2k_jk_pro.rar rom (I don't find it anymore on the net but 1) I got it on Blackview official forum and 2) I have the file on my own PC) with format+Download and replace recovery with TWRP from Jemmini from 4pda.ru before flashing. OK.
Then I rooted again: format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally.
Beware: TWRP is in Russian language at first boot, so to get it in English, first slide the first slide (allowing writing), then select 'Настройки', then the globe on top, then English, then 'Установитъ Язык'.
Hope this helps.
Then, this is my first rooted phone, so I plan to make a custom rom without Gapps (then maybe without Mediatek Ones and agold too) and remake all functionning with apps from Fdroid. Help needed on a manner of removing a system/vendor app properly. Help needed too to add V4A, as I could see max version supported is Nougat. I announce this here as my first post, but my project will be a full post. If someone want help please ask here or MP me
Note: an update of magisk is out (official 18.1), I installed it and my phone tells me a message that facial recognition was not working anymore then it only boots on TWRP... I reflashed it and my phone boots normally again. Wait and see...
Thanks to Jemmini from 4pda.ru again.
Bests Regards
Click to expand...
Click to collapse
It'd be great to have another rom but I'm facing a problem with battery life. Basically mobile network standby drains 5000mah battery every day i turned off from developer option but still problem is there. I have checked every single post on Google but nobody has solution for this. U guys face this problem too?
kanadali said:
It'd be great to have another rom but I'm facing a problem with battery life. Basically mobile network standby drains 5000mah battery every day i turned off from developer option but still problem is there. I have checked every single post on Google but nobody has solution for this. U guys face this problem too?
Click to expand...
Click to collapse
New update has been released today. It solves some battery issues, but be very careful.
I installed it, having TWRP and now I'm stuck in TWRP. I've tried to wipe everything but I'm still in TWRP.
I'll try SPFlashTool ... hope it works.
Everything restored & updated.
Using SPFlashTool I flashed all files included in 2018092919_s32v63c2k_jk_pro.rar (including original recovery instead of TWRP).
After that, Android booted and then, using OTA, I updated to latest version.
Reflected_God said:
New update has been released today. It solves some battery issues, but be very careful.
I installed it, having TWRP and now I'm stuck in TWRP. I've tried to wipe everything but I'm still in TWRP.
I'll try SPFlashTool ... hope it works.
Click to expand...
Click to collapse
Could you please send me the link? Can't find it on blackview forum
kanadali said:
Could you please send me the link? Can't find it on blackview forum
Click to expand...
Click to collapse
The latest version is not on the forum. I installed via OTA.
But if you mean the previous firmware, there is one link on the blackview forum: http://bbs.blackview.hk/viewtopic.php?t=480235#p795494
SP Flash tools are well documented here: https://forum.xda-developers.com/showthread.php?t=1982587
And a complete list of blackview bv9500 / bv9500 pro files and instructions (in russian): https://4pda.ru/forum/index.php?showtopic=931296
Hope you find what you are looking for.
@kanadali,
for the moment I'm not facing battery drain because there is not simcard in it at this state of my modifications, sorry.
@Reflected_God,
I think this is the link I used, I use the 2018092919_s32v63c2k_jk_pro.rar rom for base.
For all others who faces big problems like me (facial recognition not working then reboot on twrp only, I could reflash my phone with SPFlashTool, the rom and twrp from Jemmini/4PDA in russian only (others don't work for me). I used Format + Download in root mode on Linux. Then format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally. Do other things. To remove gapps I disabled/force stop it before remove with TWRP. Others apps I can't disable simply remove with TWRP. I test if I encounter bugs but none for the moment. If someone wants to know what I do I've made a LibreOffice Calc sheet log, which evolve when I have time
Hope this helps
Bests Regards
Need Files or a GOOD guide. bv9500 NOT PRO.
If someone could upload the exact files that they used, and the exact same steps, that would be great. Please mention what stock version you have and a link to the image if possible as well. I've followed numerous different guides, with multiple different rom versions, multiple different recovery imgs, used sp flash tool and adb/fastboot multiple times, tried making sure everything was unlocked before each try, have all the necessary drivers, and the closest I get to a functional twrp recovery is a green line that appears at the top of the boot screen before it reboots. Ive tried going to the source, the russian site, but all of the links are 404ed. if not for me, then it would be great to just have this all in one place. Thank you please future hero.
Please include exact program versions (ex SP Flash) as well if not zips of them. I am sorry to be asking so much in one post however I truly didn't know what else to do. And I am typically very good with my google fu xD
I currently have build number BV_BV9500_V1.0_20181026. That seems to matter I believe.
I second the notion.
I have the pro model. I have considered rooting it, but honestly, the phone works well enough as-is without root (for me). However, I'd LOVE to be able to play with different ROMs on this device **AS LONG AS I CAN MAINTAIN THE TWO-WAY UHF TRANSCEIVER FUNCTIONALITY** (i.e. not some "needs-a-network-of-some-kind" "walkie talkie app" like Zello but the real UHF two-way), and I'd LOVE the ability to play with the files associated with the radio to really explore the hardware's capabilities.
Unfortunately, this phone seems more popular in [North]eastern Asia than anywhere else so I don't think we're likely to get much on this forum regarding it unless and until BV become a popular name in the western hemisphere.

[SOLVED] boot loop after i tried to fix broken root

I tried for like 3 hours to find a boot.img and i had root on my phone, but without wifi and sound.
a quick google search showed me that it was because i had a wrong version of the boot.img, afterwards i found another one and now after i have tried installing twrp, booting and flashing using adb (stock and modified versions of boot.img) but it just keeps bootlooping. in twrp i cant wipe, make a backup, see any files in /storage/ and i have no clue what to do next.
What model 7T do you have? HD1907? What was the rom that you were using before you installed TWRP on? OOS12 does not support TWRP. Custom rom A13 does not support TWRP. Only a few custom rom A12 and OOS11 support TWRP.
Idk but I'm just wondering if flashing the last working rom image (dirty flash)? That would eliminate TWRP(?) and eliminate Magisk(?) while hopefully keeping the device from being wiped possibly?
*** Hopefully someone could/would verify this before you attempt... ***
i was on android 11 but i cant remember the version, i have HD1903 (EU ver). i THINK i had the one from the oneplus website(https://service.oneplus.com/us/search/search-detail?id=2096229) but idk anymore
I JUST RANDOMLY TRIED BOOTING MY PHONE AGAIN AND IT WORKED imma check if everything works and will regardless still look at this thread bc it can prob break easily
nah wifi and sound still dont work, but im not in bootloop anymore
MimKA22 said:
I JUST RANDOMLY TRIED BOOTING MY PHONE AGAIN AND IT WORKED imma check if everything works and will regardless still look at this thread bc it can prob break easily
nah wifi and sound still dont work, but im not in bootloop anymore
Click to expand...
Click to collapse
Msmtool back to oos11
can you describe how to use it or send a link to tutorial or smth thx man <3
MimKA22 said:
can you describe how to use it or send a link to tutorial or smth thx man <3
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
i cant find the file for my current version and it doesnt work if i try it with the only version that is android 11
and i cant turn my phone back on
and after i installed the drivers i had to restart my pc and now there is this thing at the bottom right:
testmode
windows 10 pro
...
i waited until my phone had no more battery charge and now im bootlooping again :/
nvm it just booted
im downgrading it now and i dont get the error "smth communication smth" in msmtool anymore
alr it worked my phone is wiped again but i can turn on wifi and sound
but how do i root my phone now? I have an Idea, im gonna write step by step what i think gets me a rooted phone please confirm if that would not break my phone ^^' (bootloader already unlocked)
1. enable usb debugging and allow my pc
2. download and install the latest magisk version from the github
3. download magisk patched boot.img for ver 11.0.5.1BA BUT since i cant find anything on the internet im gonna have to use the zip file from the unbrick tool thing (https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7T/EU_HD65BA/R/) and then patch the boot.img using magisk myself
4. then use platform tools and type following commands: "adb reboot fastboot", "fastboot flash boot {the patched boot image file}"
5. then use magisk to direct install the root thing
i just realisized the unbrick thing that i wanted to use instead of a boot.img doesnt have a boot.img in it... WHERE CAN I FIND A BOOT.IMG brooo androidfilehost.com doesnt have it the unbrick tool doesnt have it
omg i realized i could update my phone to 11.0.9.1 then download the same version from official website and use the dumper to get the boot.img **** meee
wait it sais its 11.0.9.1HD65 AA and not BA **** me
k nvm i just changed the site settings to germany and now its BA
i just went for it and now my phone is rooted thank you very much for your help i would've prob tried to revert back to stock for like 2 weeks and then cry that i cant root my phone thank you so much xd

S10e - impossibility to install Lineage OS

I need to install Lineage OS on this phone.
After multiple tries several months apart, I am still not in success.
Followed all internet tutorials and sites.
I don't want to install any G apps or any special root-things like magdisk..
I only want pure Lineage OS without any extra applications.
Way I tried and probably ended up like before:
Get newest official samsung ROM installed, update, enable usb debigging and oem, go download mode and go factory reset, get back in, sign in to wifi again, again enable develop. settings and usb debugging, go into download mode, take odin and install through the AP option the TWRP now that the phone is in download mode a 3rd time, supposed to be possible now with OEM unlock.
Most of the names on the way I don't understand, just follow tutorials.
I need to get to TWRP to then finally, as used to always, install Lineage from zip.
But I never get rebooted into TWRP recovery, just forver the samsung one, even when firmware is no longer there - after flashing in ap option the twrp tar again it never boots into TWRP afterwards.
Is there something else i must do? is not getting into oem unlock and flashing TWRP enough to get there?
And after, will the zip install finaly get me to have lineage installed?
Did you try the official guide?
https://wiki.lineageos.org/devices/beyond0lte/
I hope I picked the right phones, otherwise check devices overview.
Alternatively, perhaps this helps:
https://forum.xda-developers.com/t/...-a-graphical-installer-for-lineageos.4509995/
PS: Usually LOS doesn't do TWRP anymore but comes with its own recovery (a/b)
Why they don't do TWRP now?
I saw TWRP tuorial fot s10 on tutorials and it worked
Do I have to give up on TWRP way and od it with the adb commands from PC
frustrateduser118 said:
Why
Click to expand...
Click to collapse
It's because of this new double recovery scheme:
https://forum.xda-developers.com/t/help-understanding-a-b-partitions.3748003/post-75545902
https://source.android.com/docs/core/ota/ab
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
EOD: It's safer, updating happens in the background, then just a quick reboot et voila.
frustrateduser118 said:
I saw TWRP tuorial
Click to expand...
Click to collapse
Yes, it's still there but perhaps you post a link to your guide (or ask there). To me it seems you had TWRP just in your RAM but not your phone?
As for me, I finally gave up on TWRP and use the "crappy" LOS recovery Have way more important things to waste my time on...
PS: Sorry to bring such "bad" news, wasn't too happy with that change myself
Great, I finaly made it work.
I followed the site with turotial on installation and did not try TWRP
First I had to install samsung ROM again
It turned out to still stay unlocked so went straight to download mode and this time flashed Lineage recovery sucesfuly with heimdall
Then it booted up and a half samsung sreen made it seem like there is trouble
but Lineage recovery launched
The adb load from PC did not work so i chose to instal zip from SD even there
Now Lineage is installed
Still don't know how much is randomness, luck and so on
But it's done and hopefuly repeatable
frustrateduser118 said:
hopefuly repeatable
Click to expand...
Click to collapse
I am afraid it is
Well, most of times: Far too often I forget some little prerequisite, too... so started a little text file with steps/reminders.
anyway glad for support sigmund
you re my friend now

Question Google pixel 6 pro bootloops after root

I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
Do you have TWRP installed?
webhook said:
Do you have TWRP installed?
Click to expand...
Click to collapse
No
Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
Rooting pixel phones are pretty straight forward and not much difficulties. Two different approaches:
1. If you are an experienced user and 100% sure what you are doing, then go back to your rooting process step by step to make sure you didn't miss anything.
2. If you are not sure that you have done everything correctly, then I would suggest you that you follow the steps which describe in this thread, believe it still the most detail explanation for rooting the pixel phones even today. https://forum.xda-developers.com/t/...ootloader-update-root-pass-safetynet.4356231/
Also posting your question on this thread could get you quicker response.
If after your trying of everything you still couldn't get it done, then describe your entire process when you ask for help without people have to guess what could went wrong.
PS: The only information which you shouldn't follow with that thread is "NOT" to use the latest platform tool, stay with version 33.0.3, version 34.0.1 has problem.
Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
I had the same issue. Right after flashing when booting for the first time it got stuck in a boot loop. Factory reset fixed it.
Stupid question also could be the wire your using and usb port
If you guys are bootlooping after flashing Magisk patched image...
You should use the Google's official Android Flash Tool to reset your device to a working state...
Then you should use badabing2003's PixelFlasher to root; it automates most of what's needed to root, and it has checks and protocols to make sure files are correct, versions are correct, and the right procedure happens in the right order -- taking out a lot of guesswork or mis-steps that might be happening that is causing bootloops.
Many/You would be surprised how many times PixelFlasher succeeds where many have failed; almost miraculously and/or inexplicably! It's why it's become rather famous tool for Pixels...
Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
fluxfield said:
I had the same issue. Right after flashing when booting for the first time it got stuck in a boot loop. Factory reset fixed it.
Click to expand...
Click to collapse
Previously rooted with Magisk modules?
Incompatibility with newer updates is more often than not the cause of bootloops.
Rebooting into safe mode will disable them.
Press and hold volume down when the bootloader unlocked warning screen appears. Then let go as soon as you feel a vibration.
You will boot into safe mode and modules will be disabled.
Then reboot normally and go into Magisk and re-enable only safe modules such as USNF.
Test the others one by one until you find the culprit. Usually it will be a font changing module or an AOSP mod .
It's pretty straightforward provided you have an unlocked bootloader, USB debugging and platform tools, The latest works for root alone btw.
In terminal
Code:
adb devices
Authorise adb in the popup window
Code:
adb reboot bootloader
If fastboot isn't recognising your phone install the USB driver
You may find it easier to install the driver in fastboot.
Code:
fastboot flash boot <path_to_magiskboot.img>
Code:
fastboot reboot
Profit.
Assuming you've patched the right boot.img file from the .zip within the factory image zip file and you're using magisk from github.
fil3s said:
You may find it easier to install the driver in fastboot.
Code:
fastboot flash boot <path_to_magiskboot.img>
Click to expand...
Click to collapse
Accidental mistake.... "image" was meant, not "driver".
...don't want OP chasing down an issue because of a miscommunication or confusion...
PixelFlasher is truly the easiest & most straightforward, honestly....
simplepinoi177 said:
Accidental mistake.... "image" was meant, not "driver".
...don't want OP chasing down an issue because of a miscommunication or confusion...
PixelFlasher is truly the easiest & most straightforward, honestly....
Click to expand...
Click to collapse
I meant that sometimes the google USB driver is easier to install in fastboot. Regards
fil3s said:
I meant that sometimes the google USB driver is easier to install in fastboot. Regards
Click to expand...
Click to collapse
aaahh...i see now...
sorry, i just made that assumption because you put the fastboot command to installing/flashing the image right after the sentence -- i made the mistake of connecting the two...
i should've known better as i was already initially confused as you don't install the driver AS a fastboot command...!

Categories

Resources