Bricked 2013 deb - Nexus 7 (2013) Q&A

My deb boots to the Google Logo and stops. ADB was enabled, but not any longer. ADB Devices returns blank. I can boot into Recovery Mode (Power + Vol Down). I have tried WUG Fresh to return to stock, and the Unified Android Toolkit (UAT). WUG Fresh fails. The ADB in UAT works, for some unknown reason since it doesn't do so natively, but the return to stock process ends with an error.
I don't know what else to do. The device is way out of warranty, of course. But I love it, want to fix it and install a custom ROM, like I had before it broke. That's my story, sad but true. I hope and XDA genius can help.
Thanks

Oops - forgot you had Deb, so will need to verify any of these exist for Deb or that the versions I referenced work on both
What recovery are you booting into?
Have you tried installing a rom?
Look thru the repartition and Los 15.1 threads in original android development. If you plan to update to any newer roms and use gapps you will need to repartition system for gapps to fit.
I would try:
1) install latest twrp
2) repartition (if desired)
3) format system
4) install rom of your choice (plus gapps)
4a) install magisk if root desired (did you ever unlock it? )
People are liking aocp or aicp in Android development. I'm personally using Los 15.1 in original Android development. The current nightly builds referenced near the end of that thread have a problem. Until it is fixed you will need to use the one linked in the OP.
MAJOR caveat! I am far from expert so someone else may give you significantly better advice

Perhaps you misunderstood. All I can do is boot into Recovery or Bootloader mode (Power + Vol. Down). I can't boot the device to enable Developer Mode and USB/Android debugging. When I try to boot normally (Power button), I'm stuck in a bootloop on the screen with the Google logo. So, everything is locked. If it were otherwise, I wouldn't need any help fixing it.
Thanks

This "Q&A" format is rather constraining for a troubleshooting issue. Please check "Fastboot Diagnostics" in https://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/fix-nexus-7-2013-bricked-stuck-t3310608 and post your results there.

Related

(HELP) once nexus 7 is on it straight away leads to teamwin recovery

Once Nexus 7 (2013) is being on, it straight away leads me to teamwin custom recovery, it doesn't boot to android. Also in teamwin it says that the data can not being mounted
dhaseegaren said:
Once Nexus 7 (2013) is being on, it straight away leads me to teamwin custom recovery, it doesn't boot to android. Also in teamwin it says that the data can not being mounted
Click to expand...
Click to collapse
Did you get this fixed yet? I was stuck in a TWRP bootloop after trying to flash stock 6.0 is that what you did? If all else fails you can try to boot fastboot and flash the stock firmware, that's what I had to do.
Try this:http://forum.xda-developers.com/showthread.php?t=2471341
Android 6 Marshmallow,MRA58V, TWRP, Rooting, MultiRom
Ok my experience with rooting using N7 2013 and Ubuntu adb stuff. (When I say N7 I mean the 2013 version)
Put Marshmallow MRA58V on the N7 (deleted link per prompting) Tried some of the older rooting methods but one thing is certain, TWRP no longer behaves like it did in the past.
I was running a Cyanogenmod ROMs from July and decided to upgrade from scratch. When I get to the TWRP screen to where I expect it to say it will allow me to globally root the device, I get the "Read Only" mumbo jumbo.
One can hit yes or swipe to go on. Doesn't matter what you select.
Once I get TWRP installed, I have it install Elemental X and SU. Ok up to now. Marshmallow boots up fine and dandy to a usable, stock system that's stable. Now for the fun part. When I install Multi-Rom while in Android 6/Marshmallow, the unit goes through the nominal process of installing the app. It goes back into reboot mode, finishes the install and when it reboots again, it gives me the standard MultiRom screen and the choice to boot into "stock". When I select stock, it boots directly to TWRP period. No amount of dinking around allows me to do otherwise. It will only boot into TWRP and not into Marshmallow. I've done 5 installs with various iterations of "rooting" I could find on the internet ( and here) to no avail. I also tried MRA58K ROM
My goal was to have a stock kernel for app stability and an experimental kernel I could experiment with.. Any suggestions? Do I go back to an older ROM from the 4.4 set?
I will say I bricked up the N7 2013 several times. I found if I brought up the boot loader to START in the N7 screen, I could run the sudo ./install.sh command on the Ubuntu box from the ROM directory directly without the adb command. The command prompt responded it was accessing the bootloader but would sit there for awhile. When I hit the on/off button on the N7, the laptop responded with loading the fresh ROM to the N7 2013 and it fired right up with a fresh install from an apparent "bricked" state. Happy for me. I discovered this as I thought I had bricked the device but good 'ol Unbuntu Linux showed on a "dmesg" command
that the N7 was connected to the USB port. I read that someone did the ./install.sh command directly and by golly it was brought back to life.
I did try to backup the system right up to just before I installed multirom during one of the installs. When I got the perpetual boot behavior into TWRP, I restored the backup and the booting behavior still occurred into TWRP only.
Any suggestions for this "script kiddie" here? I hate to be without Multi Rom but I will at least be able to run a stock kernel. I couldn't find anything but the Open Gapps for Marshmallow and I REALLY miss that
shutdown screen that gave me something like 5 choices. Now I can only "shut it off". Best regards, Kurt

V500 secure booting error

Hi guys,
For now I'm stuck on this error on updating to LineageOS (official repo). "secure booting error" me checked!
I used to do a clean Install nothing more than this. Only if things will load I flash GAPPS etc.*
Previously I've successfully flashed cm13 and cm14.1 and so on.
But sometimes I got the "secure booting error"
When flashing (custom) kernels I always get the "secure booting error".
On flashing roms sometimes it does sometimes it won't.
I'm not sure when or what went wrong or not.
I've never had issues to access twrp or flash twrp. Like I see on most topics.
So I'm pretty sure the problem exist in my bootloader.and not in the roms or other flashing. Maybe it isn't fully unlocked?
My LG G Pad 8.3 (v500) bought in The Netherlands.
I flashed V50020F Bootloader: https://www.androidfilehost.com/?fid=24352994023707804.
Flashing all went fine as far as tarp gives the right info. I only don't know how to check this.
TWRP: 3.0.x
Is there guide de to fix this? I've really spend days on this without any solution. It's really frustrated!
Hmm.. Same issue here.
Was on stable CM 14.1 & TWRP 3.0.2.0.
Flashed TWRP 3.0.2.2
Flashed Lineage experimental 14.1 & supersu addon zip
Rebooted and am stuck with the same secure boot error. I don't understand why I can't get into the same TWRP recovery I was just in to attempt to clean flash a nightly LineageOS 14.1.
------------
Here we go: https://forum.xda-developers.com/showpost.php?p=70740190&postcount=84
Follow those steps to get into TWRP.
Xenosis said:
Hmm.. Same issue here.
Was on stable CM 14.1 & TWRP 3.0.2.0.
Flashed TWRP 3.0.2.2
Flashed Lineage experimental 14.1 & supersu addon zip
Rebooted and am stuck with the same secure boot error. I don't understand why I can't get into the same TWRP recovery I was just in to attempt to clean flash a nightly LineageOS 14.1.
------------
Here we go: https://forum.xda-developers.com/showpost.php?p=70740190&postcount=84
Follow those steps to get into TWRP.
Click to expand...
Click to collapse
Don't use supersu with cm/lineage.
The secure boot error can be fixed by flashing this zip in recovery.
https://www.androidfilehost.com/?fid=95916177934554766
Thanks. Ya I had no idea there was a set of flashable su's for LineageOS in Extra.
Got it working. The issue was mostly that I had no idea how to use the hardware buttons for this tablet to get into recovery.
Thanks that helped me out!!
My Problem:
Lineageos 14.1 and Magisk 17.1 installed, updated Lineageos to actual nightly and got a
Secure booting error, Cause : boot certification verify
Solved with:
Boot into recovery mode with TWRP installed
Howto here: https://youtu.be/uo3YfszOPsQ
Than installed: v500-loki-kernel-to-bumped-kernel-signed.zip
Here is the proper thread with backround information
https://forum.xda-developers.com/showpost.php?p=60092491&postcount=1
Fixed it. Great job
[V500] "Secure Booting Error..." solution howto
Let me recap here, 'cause I get trapped in this issue every other year and it takes me a while to retrace back the steps for the solution.
Some intro, for starters: I have been running Lineage OS on my device for years and, at first, whenever I had this, I had to get the LG Mobile Tool plus the full factory ROM to do a KDZ restore -- i.e., start everything from scratch.
There's zero need to do that -- if you had a working TWRP recovery and Android system before, both will still be fully functional after you overcome this problem!
First: you have to get back into TWRP.
This is the hardest part because not only the key press sequence is rather uncommon, you have very little time to get through it, too.
In short, you have to press VOL DOWN + POWER keys until you get the LG logo.
Then you have to quickly release and press all three keys (VOL DOWN + VOL UP + POWER), before the "Secure Boot" error message comes up.
Second: What comes up doesn't make a lot of sense, too: you're dropped in the "Factory Reset" screen.
You'll have to press POWER twice to confirm -- never mind the dire warnings -- to get back into TWRP.
Try again if you don't succeed or check the YouTube video pointed above by HerrRuin good to see how it's done.
Third: once in TWRP, it gets easy.
Download the bumped bootloader from AndroidFileHost, also pointed by HerrRuin above.
(FTR, file name is 'v500-loki-kernel-to-bumped-kernel-signed.zip'; MD5 is 'f1a25de31559462d8c5d4c35d23f84d9')
While still in TWRP, connect the tablet to your computer and transfer the file over.
After the file is copied, flash it via the "INSTALL" button, reboot, and "Bob is your uncle"... :laugh:​
Many thanks to everyone who contributed to this solution that allows me to keep enjoying my G Pad after so many years.

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.

Having trouble understanding where to start

Right, so I haven't done these types of things for years and it's safe to say I've forgotten most of it. So my question is do I root first or do I just install TWRP ?
I've chosen to go ahead with this TWRP https://forum.xda-developers.com/showthread.php?t=2678420. But it says Oreo compatible, so I am guessing I can only install an Oreo ROM ? Are there any better(newer) options available ? It is all very confusing, I've tried searching but so many versions of everything, I am not even sure which Odin I need or if it even matters ? I have the GT-I9195. Thanks in advance.
PandaDNB said:
Right, so I haven't done these types of things for years and it's safe to say I've forgotten most of it. So my question is do I root first or do I just install TWRP ?
I've chosen to go ahead with this TWRP [url]https://forum.xda-developers.com/showthread.php?t=2678420[/URL]. But it says Oreo compatible, so I am guessing I can only install an Oreo ROM ? Are there any better(newer) options available ? It is all very confusing, I've tried searching but so many versions of everything, I am not even sure which Odin I need or if it even matters ? I have the GT-I9195. Thanks in advance.
Click to expand...
Click to collapse
Hey, I am going to try and help you out with this the best I can
You need to use Odin to install TWRP on your device (I'm assuming you have the stock rom currently installed).
The latest Odin should work just fine (a google search should help you find and download it)
You can download the latest version of TWRP from the official TWRP site for your device ([url]http://twrp.me[/URL])
After you download it follow these steps (taken from here because I was too lazy to write it again [url]http://forum.xda-developers.com/showthread.php?t=2449107[/URL]:
1)Turn off the phone.
2)Press and hold home, volume down and power. Download screen should appear.
3)Connect USB cable, and press volume up
4)Start Odin, uncheck "F. Reset Time" and "Auto Reboot", and then click AP button.
5)Select extracted "recovery.tar.md5" file and press Start button.
6)A blue transfer bar will appear on the device showing the recovery being transferred. Check the Message Window in Odin for: "All threads completed. (succeeded 1 / failed 0). The transfer has successfully completed.
7)Long press the power button to turn it off.
8)Hold volume up, home button and power buttons simultaneously to boot into recovery mode.
Once you get to the recovery mode you can install any Rom you want to after making full wipes (wiping data, dalvik, cache, system, internal storage (this wipe is only needed for the first time. I have Lineage Os 17.1 (Android 10) installed on my GT-I9192. On the same thread, you can find the rom for GT-I9195 too.
With respect to rooting, after you install the Rom + gapps, you can flash the latest version of Magisk to get root access. (A simple search will get you the latest version of Magisk too).
(In case you have no idea on what flashing, Rom, Gapps are, there are plenty of videos on youtube that can help you out with that.)
Ookay, I actually managed. Got the Lineage 17.1 installed. To be honest the hardest part was actually installing TWRP. The phone would always replace it with stock recovery and I couldn't get it working. Tried ADB but got stuck 'waiting for device', then I found a 'All in one tool' which i used to Root my device so that I could use the TWRP Playstore app so that I could get the latest version of TWRP....Took me a bit longer than expected, even bricked the device once but managed to get it back and it's now running alright. Anyways thanks for your reply, I guess the thread can be closed now..
Anirudh Kartik said:
Hey, I am going to try and help you out with this the best I can
You need to use Odin to install TWRP on your device (I'm assuming you have the stock rom currently installed).
The latest Odin should work just fine (a google search should help you find and download it)
You can download the latest version of TWRP from the official TWRP site for your device ([url]http://twrp.me[/URL])
After you download it follow these steps (taken from here because I was too lazy to write it again [url]http://forum.xda-developers.com/showthread.php?t=2449107[/URL]:
1)Turn off the phone.
2)Press and hold home, volume down and power. Download screen should appear.
3)Connect USB cable, and press volume up
4)Start Odin, uncheck "F. Reset Time" and "Auto Reboot", and then click AP button.
5)Select extracted "recovery.tar.md5" file and press Start button.
6)A blue transfer bar will appear on the device showing the recovery being transferred. Check the Message Window in Odin for: "All threads completed. (succeeded 1 / failed 0). The transfer has successfully completed.
7)Long press the power button to turn it off.
8)Hold volume up, home button and power buttons simultaneously to boot into recovery mode.
Once you get to the recovery mode you can install any Rom you want to after making full wipes (wiping data, dalvik, cache, system, internal storage (this wipe is only needed for the first time. I have Lineage Os 17.1 (Android 10) installed on my GT-I9192. On the same thread, you can find the rom for GT-I9195 too.
With respect to rooting, after you install the Rom + gapps, you can flash the latest version of Magisk to get root access. (A simple search will get you the latest version of Magisk too).
(In case you have no idea on what flashing, Rom, Gapps are, there are plenty of videos on youtube that can help you out with that.)
Click to expand...
Click to collapse
PandaDNB said:
Ookay, I actually managed. Got the Lineage 17.1 installed. To be honest the hardest part was actually installing TWRP. The phone would always replace it with stock recovery and I couldn't get it working. Tried ADB but got stuck 'waiting for device', then I found a 'All in one tool' which i used to Root my device so that I could use the TWRP Playstore app so that I could get the latest version of TWRP....Took me a bit longer than expected, even bricked the device once but managed to get it back and it's now running alright. Anyways thanks for your reply, I guess the thread can be closed now..
Click to expand...
Click to collapse
The trick is to immediately boot into recovery after flashing it. If you reboot the phone itself, the stock recovery overwrites itself back (useful to remember when you plan to install twrp on your next device).
Anyway, glad you managed to get it working

[Solved]Requesting Help Regarding Mi A2 Lite (Stuck in Unlocked Boot loop, No OS installed)

Just this day, November 23, 2021, I have been trying to flash a custom rom named Syberia OS for daisy(Mi A2 Lite variant). As I have done booting up the device to fastboot(thru cmd command since my power button is jammed), I installed the twrp after booting the image to the device, making it as my recovery.
Now I am set and excited to install the rom, so I went to fastboot again and tried to flash the rom, but it always errors and not installing the rom. It is said "to flash multiple zips, reboot recovery before..." (correct me if I'm wrong), so I rebooted to recovery thru the twrp (since its in fastboot). Now, I did the same, I installed the rom again and experienced the same error so I dont know what to do, I did wiped system, data, dalvik and internal storage (a lot of times and tried to install the rom again), but I get the same error.
Then since I cant install the rom, I went to reboot to system thru twrp, and then I forgot, that I have no OS installed.
So now I'm stuck with the "Your device software can't be checked for corruption. Please lock the bootloader. Please visit this link..." plus arriving to the AndroidOne logo, and it turns off and turns on again with the message and logo, repeats until the battery is completely empty.
Is there anything I could do to go to fastboot again for a clean install of the stock rom? (I promise to not unlock the bootloader and experiment on custom roms again)
(I am sorry if you find it hard to understand, I am willing to edit this thread for better understanding if there are things you dont understand.)
This is what I see after all that happened...:
Your browser is not able to display this video.
Any form of response and acknowledgements will be much appreciated )
@hachi_eight
Please read the guidances that are stuck on top of every forum prior to your next posting like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
I've moved the thread to Q&A.
Regards
Oswald Boelcke
Senior Moderator
hachi_eight said:
Just this day, November 23, 2021, I have been trying to flash a custom rom named Syberia OS for daisy(Mi A2 Lite variant). As I have done booting up the device to fastboot(thru cmd command since my power button is jammed), I installed the twrp after booting the image to the device, making it as my recovery.
Now I am set and excited to install the rom, so I went to fastboot again and tried to flash the rom, but it always errors and not installing the rom. It is said "to flash multiple zips, reboot recovery before..." (correct me if I'm wrong), so I rebooted to recovery thru the twrp (since its in fastboot). Now, I did the same, I installed the rom again and experienced the same error so I dont know what to do, I did wiped system, data, dalvik and internal storage (a lot of times and tried to install the rom again), but I get the same error.
Then since I cant install the rom, I went to reboot to system thru twrp, and then I forgot, that I have no OS installed.
So now I'm stuck with the "Your device software can't be checked for corruption. Please lock the bootloader. Please visit this link..." plus arriving to the AndroidOne logo, and it turns off and turns on again with the message and logo, repeats until the battery is completely empty.
Is there anything I could do to go to fastboot again for a clean install of the stock rom? (I promise to not unlock the bootloader and experiment on custom roms again)
(I am sorry if you find it hard to understand, I am willing to edit this thread for better understanding if there are things you dont understand.)
This is what I see after all that happened...:
View attachment 5466081
Any form of response and acknowledgements will be much appreciated )
Click to expand...
Click to collapse
Hey brother, I had the same situation a few months ago. My device - Redmi 6 (Cereus).
So, I was trying to install TWRP in Redmi 6 and then after trying many times TWRP successfully got installed. But when I tried to boot the device, It stuck in bootloop (Going to fastboot and again booting...). So, the answer is that you first boot into fastboot mode of your device and then download the fastboot Rom of your device, (link of fastboot rom of your device - https://xiaomifirmware.com/download/18010/ ) . Then go to your PC and then extrac
the fastboot file, then connect your phone to pc and go to fastboot mode then open the extracted folder and then click on flash-all (The batch file) and then a new command window will open automatically and flashing process will start. After it's done your phone will reboot automatically. For reference, go ahead. Best of luck!
hachi_eight said:
Just this day, November 23, 2021, I have been trying to flash a custom rom named Syberia OS for daisy(Mi A2 Lite variant). As I have done booting up the device to fastboot(thru cmd command since my power button is jammed), I installed the twrp after booting the image to the device, making it as my recovery.
Now I am set and excited to install the rom, so I went to fastboot again and tried to flash the rom, but it always errors and not installing the rom. It is said "to flash multiple zips, reboot recovery before..." (correct me if I'm wrong), so I rebooted to recovery thru the twrp (since its in fastboot). Now, I did the same, I installed the rom again and experienced the same error so I dont know what to do, I did wiped system, data, dalvik and internal storage (a lot of times and tried to install the rom again), but I get the same error.
Then since I cant install the rom, I went to reboot to system thru twrp, and then I forgot, that I have no OS installed.
So now I'm stuck with the "Your device software can't be checked for corruption. Please lock the bootloader. Please visit this link..." plus arriving to the AndroidOne logo, and it turns off and turns on again with the message and logo, repeats until the battery is completely empty.
Is there anything I could do to go to fastboot again for a clean install of the stock rom? (I promise to not unlock the bootloader and experiment on custom roms again)
(I am sorry if you find it hard to understand, I am willing to edit this thread for better understanding if there are things you dont understand.)
This is what I see after all that happened...:
View attachment 5466081
Any form of response and acknowledgements will be much appreciated )
Click to expand...
Click to collapse
Check in the guides section for mi a2 lite. Do a little search before asking. This one
user-001 said:
Check in the guides section for mi a2 lite. Do a little search before asking. This one
Click to expand...
Click to collapse
i fixed it, i opened the back of the phone and managed to fix the power button, and used the combo to get to fastboot mode, and reinstalled the stock OS. so, now I fixed it!
hachi_eight said:
i fixed it, i opened the back of the phone and managed to fix the power button, and used the combo to get to fastboot mode, and reinstalled the stock OS. so, now I fixed it!
Click to expand...
Click to collapse
I am having same issue. What did you do fix the power button?

Categories

Resources