Hey guys.. having issues rooting my BV9900 Pro. Not much on the net about this device. I gained Root access for one boot using magisk app to patch my boot image and fastboot flashing it. I used a couple Root apps and deleted a couple of system apps, magisk granted access. When I restarted, it went into a boot loop until I flashed the original boot.img. Now whenever I flash the patched boot, it tries once and goes into bootloader. I have an Orange State message on regular boot.img startup.
I tried this with a generic blank vbmeta, it went into a boot loop.
Someone with a non-pro BV9900 with the exact same chipset managed to get twrp on his. I tried flashing that. Bootloader says data transfered but whenever I go into recovery, the original recovery.img loads and it boots normally with the Orange State message.
The root deleted system apps are still gone.
Any insights or tips would be greatly appreciated.
pbsavages said:
Someone with a non-pro BV9900 with the exact same chipset managed to get twrp on his. I tried flashing that. Bootloader says data transfered but whenever I go into recovery, the original recovery.img loads and it boots normally with the Orange State message.
Click to expand...
Click to collapse
Only a side remark:
Even if one finds a TWRP image that at 100% matches his/her device, it's not a good idea to flash it: instead boot into it
Code:
fastboot boot twrp.img
jwoegerbauer said:
Only a side remark:
Even if one finds a TWRP image that at 100% matches his/her device, it's not a good idea to flash it: instead boot into it
Code:
fastboot boot twrp.img
Click to expand...
Click to collapse
Ah. I didn't realize magisk was systemless root. The BV9900 Pro crashes when you edit the system image. I suppose I should research more, things have changed in the last few years.
Related
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
nea102 said:
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
Click to expand...
Click to collapse
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
I had used that guide, was following that when I was getting the out of space errors.
However, I got it all sorted in the end - I just downloaded a different (older) version of the firmware and that worked.
Help for you
samlis said:
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
Click to expand...
Click to collapse
Hi good day.
I have been following your work from another page, and now in XDA.
I had not read your message, and, I changed the recovery for the stock, and, I was an idiot to close the bootloader.
What happened? Brick simple on my cell phone, did not come out (because I fixed it) of the image of erecovery (EMUI) without tabs or options, a rather rare image.
How do I solve it:
1. I did not enter fastboot, I did not correctly enter the stock recovery (I had deleted the twrp), I had closed the bootloader (my stupidity)
2. Be patient and wait for the battery to run out (wait a day for it).
3. Open cmd and place the command to open the bootloader (fastboot oem unlock) and execute.
4. Put the device in fastboot mode when connecting to the laptop (I did not work several times, the fastboot came out with error FUNC No 10 and NO 2), after numerous attempts and not to let it charge the battery too much (because it was restarted and towards brick in the EMUI logo), correctly enter the fastboot and unlock, when you enter step 3 automatically, it will be executed. I had an advance in removing the cell phone from the brick.
5. It reboots and wonderfully happened to the Rom (that had previously installed), that is to say, the erase was not executed when the bootloader had previously closed.
6. As I had little energy, it was turned off, but I connected it and entered charging mode without restarting (before I did it).
7. Wait for a load of at least 5%, and install the Catuva21 TWRP from the tutorial.
8. I put it by command to restart in fastboot, but I generate error (Error Func No 10 and No 2).
9. I turn off the cell phone and with volume up and power key
10. Enter the TWRP correctly, verify that it is installed.
11. Restart system and log in to the system. I had not deleted anything, but to avoid problems, I hope to load 55% and execute the steps to install the rom.
12. Enjoy and dry spilled tears.
Experience lived and I hope you do not do something that developers do not advise.
Grcias and happy day.
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
heindrix said:
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
Click to expand...
Click to collapse
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
yoni sofer said:
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
Click to expand...
Click to collapse
take a look here, mate.
https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Hey guys,
I already soft bricked my device (I think) -.- I rooted it with the patched boot image and accidently installed a magisk module which caused a boot loop.
I booted into TWRP and didn't read that for now we can't mount the important partitions, so there went that. I rebooted to stock recovery and erased my complete device (factory reset + userdata) and now it bootloops into the bootloader.
Can't boot stock recovery or ROM.
Is there any chance to recover it with the current tools we have or do I have to wait for a fully working TWRP?
Any tip is appreciated
Is this topic something you can work with?
https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865
MarkSnijders said:
Is this topic something you can work with?
https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865
Click to expand...
Click to collapse
Thanks for the hint, but no chance. After flashing the recovery and reboot, the 7t pro always reboots to bootloader :-\
Edit: Could switch the boot slot and was able to enter recovery. Tried the modified one with adb function, but sideloading a rom is not possible adb: sideload connection failed: closed
I think I have to wait for TWRP
dre-z said:
Thanks for the hint, but no chance. After flashing the recovery and reboot, the 7t pro always reboots to bootloader :-\
Edit: Could switch the boot slot and was able to enter recovery. Tried the modified one with adb function, but sideloading a rom is not possible adb: sideload connection failed: closed
I think I have to wait for TWRP
Click to expand...
Click to collapse
Try this:
- Reboot to bootloader (If not possible, hold "Volume Down" & "Powerbutton" to boot into recovery, from there select "Boot Fastboot")
- Open CMD and type "fastboot flash boot boot.img" (I attached the 7tPro AA Boot.img)
##EDIT##: Well, unfortunately I'm not allowed to post extern links, so you have 2. options. Somewhere here in the Opt7tPro threads, some guy posted a link where he uploaded the stock boot image. Should be found here https://forum.xda-developers.com/7t-pro/help/rooting-oneplus-7t-pro-t3983533/page2 (scroll down ). Option 2, you downlaod the 7T OTA from OP website and extract the payload.bin with the programm "payload_dumper-win64". This will extract a more or less working boot image..
Your phone should then be able to boot normally again.
If it does, you will probably find out, that your WiFi, Speakers & Camera won't work.
Don't worry, this is because you maybe need the BA boot.img.
Then there are to options.
1. You wait until OP releases the original files on their website, as they did with the 7t
2. You go to "Settings", "System" & "Factory Reset", to reset your phone. (By now, this is the only way to fix the problem, so you can use the patched boot again)
If you choose option 2, after the "installation" screen, where it asks to enter your language, you must boot your phone into fastboot again.
Then you can flash the patched boot image again and your phone should work as normal
I was on same situation, i planned to root, but not found really 7T PRO rom, 7T ot 7 PRO has totally different ROMs, so i made a big mistake, to flash different rom. Phone stuck in boot loop. After 1.5 day google searching, i found one, that can bring back phone to live. I found a fresh 7T PRO rom, and simply flashed back, it booted, and finally everything's works good. Must to download fresh factory rom: https://androidfilehost.com/?fid=4349826312261606254, unzip it to any folder, start your phone in fastboot mode, plug in usb cable, (other eng plug to PC) and then simply do double click at the unzipped folder to flash all.bat file. You will get some errors, it's totally normal. Within 4-5 minutes your phone will works again. Hope it will work at you.
You, my fellow xda guys, are amazing!!! The solution with the stock boot.img helped me out!
Now I can start using my 7t pro after 3 days ^^
I unlocked the device bootloader thanks to Narender, and tried to flash Lineage OS 18.1. After flashing the ROM and vendor zip files, I switched the current slot and restarted to fastboot mode. Then I flashed the vbmeta image. Then I rebooted to recovery to check the current slot. Slot was as expected, so I rebooted the system.
Then, TWRP gave me an alert saying "No OS is installed" before rebooting. I was unsure what was the reason for it because the ROM was just installed, so I rebooted the system.
After that, device went straight into fastboot mode after "Android One" screen. No matter which option I choose from there, it keeps restarting the bootloader. I tried using "fastboot reboot recovery" but that did not work either. Then I tried to change the active slot of the device using fastboot commands. That did not help either.
Now I'm stuck with a Nokia 7.2 that can only be turned off or start in fastboot mode. Is it bricked beyond saving? I just want to install TWRP in any of the slots and install any usable ROM. Any help is deeply appreciated.
Installed NFT and flashed the stock ROM using that. All good now. I still need to figure out how to install ROMs on A/B systems using TWRP.
Chevindu said:
Installed NFT and flashed the stock ROM using that. All good now. I still need to figure out how to install ROMs on A/B systems using TWRP.
Click to expand...
Click to collapse
Follow this and DM if you have doubts
Edit: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Ujwal2000 said:
Follow this and DM if you have doubts
Click to expand...
Click to collapse
I actually installed few ROMs after my previous reply. But none of them had working WiFi, which is a deal breaker. Went back to stock ROM.
If you are interested I could help you
Ujwal2000 said:
If you are interested I could help you
Click to expand...
Click to collapse
Hey, thanks. But I thought it's not possible due how the signatures in security patches work. So I gave up. Maybe I misunderstood. Linking to Raghu's reply below.
Post in thread '[OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7.2 | Daredevil |'
No, wi-fi with twrp still doesn't work. But what I did was, I extracted the boot image of the ROM I was using, flashed twrp, flashed gapps and then flashed the boot file I extracted earlier. So, wi-fi does work in the end. But, you can't have twrp perpetually installed
Some tutorials I saw online used fastboot boot twrp.img
What this is supposed to do is boot into twrp temporarily and is gone after restart.
But, on this phone, instead of booting to recovery after the command, it boots to the OS. And when you restart the boot image is gone and you restart into the stock recovery. So, that method doesn't work
Ujwal2000 said:
No, wi-fi with twrp still doesn't work. But what I did was, I extracted the boot image of the ROM I was using, flashed twrp, flashed gapps and then flashed the boot file I extracted earlier. So, wi-fi does work in the end. But, you can't have twrp perpetually installed
Some tutorials I saw online used fastboot boot twrp.img
What this is supposed to do is boot into twrp temporarily and is gone after restart.
But, on this phone, instead of booting to recovery after the command, it boots to the OS. And when you restart the boot image is gone and you restart into the stock recovery. So, that method doesn't work
Click to expand...
Click to collapse
Yup, pretty much what I experienced too.
I haven't tried extracting boot image and flashing it manually. At this point to be honest, I'm reluctant to put my hands on it again without having a clear step-by-step guide about it.
I did write a step by step guide. But i'll leave it to you to decide if it is clear. Ok I realize I haven't linked the post.
Here it is: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Ujwal2000 said:
I did write a step by step guide. But i'll leave it to you to decide if it is clear. Ok I relaise I haven't linked the post.
Here it is: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Click to expand...
Click to collapse
Thanks Ujwal, appreciate it. I'll have a look.
Figured it out.
Dear all,
I am trying to replace the stock OS on my Lenovo tablet with some more open alternative, like LineageOS. I got as far as installing a modified version of TWRP on it and got root access.
I also found some unofficial gis LOS images but I couldn't install them via TWRP as the SYSTEM partition does not show up when I have to select which partition I want to install the image to. Mounting (ticking) the system partition in TWRP makes no difference. These are the partitions listed:
Boot
Vendor Image
Recovery
Modem (Image)
Persist (Image)
Splash
So I went ahead, and installed it from fastboot like this:
fastboot flash system image.img
Click to expand...
Click to collapse
The command succeeded, but when restarting, the device gets back to fastboot. I can boot into TWRP as well, but no matter what image I try to install, I get the same result.
I wonder what I am doing wrong... A few years back I have converted several phones to LOS and others with no problem. But I have no experience with gis. Maybe that's the problem.
Could someone more experienced help me? maybe I am trying the wrong gis images.
Thanks for any pointers in advance!
So I just rooted my pixel 6 using the correct original img from google and Magisk. This worked great and I got root access (active boot partition was a if it’s somehow relevant). Now I wanted to use all the functions of nethunter (which I downloaded and installed from nethunter store or something like that), so I wanted to install the nethunter Kernel for my device. Pixel 6 is not officialy supported by kali or not leaked yet so I found pre build nethunter kernel for pixel 6 on xda developers.: https://forum.xda-developers.com/t/...o-oriole-raven-kernel-kali-nethunter.4461589/
So I went in to the mega folder and into the mad-kali-maxhunter-kernel folder. Then into the p6_p6pro folder. Then I just downloaded the maxhunter zip thing for oriole because it stands for p6 ig. Then I flashed this zip file using the Franco kernel manager as recommended in the thread. My device restart and didn’t start up again. So I just tried getting in fast boot and I got it. Now I thought i would just flash the patched magisk img I made for rooting the device previousl. So I did that using fastboot flash boot and so on. Next my device was in an bootloop still, so then I flashed the very original google official img for the device. Still boot loop, so then I wanted to do recovery from fastboot on the phone when I started factory reset mode the phone was just stuck in the google logo. Then I wiped all data using the fast boot tools from my computer. It wiped it but said stuff like the file system is not formatted or not the right format or so but still wiped the data. Still boot loop. So now I switched the active boot partition from a to b. This time the phone said like waiting for command and so on. So I watched a tutorial and got further, now I was able to get to the factory reset mode did. a reset and started. Nothing realy happened and it jumped back to fastboot mode. I thought maybe because in boot b is no img to boot. So I flashed the official google img again but on b. Still bootloop. Now I have a problem. Pls help me.
You should consider trying Google's official Android Flash Tool, it might succeed where your manual flashing failed -- especially considering it was set up by Google and might have better/further checks and such...
Yes, I would recommend Android Flash Tool also. Its helped me a couple times to recover when I couldn't boot. It gives you options for boot.img right before flashing your phone so everything you'll need should be there
@simplepinoi177 i would really like to use it but its using adb and adb is not passible only fastboot so my device isnt available. EDIT: Nvermind i didnt read correctly.
Thank y'all so much it worked!!!
Great. Android Flash tool ftw again