Related
Dear Sir,
I have followed all the steps but still not rooted my htc desire 820 dual sim
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064..............this link I have followed.....
but didn't sucess.......
plz....help...Sir
HTC Desire 820 can be easily rooted with few simple steps.
I am not responsible for your warranty loss or device not functioning properly.
Steps
1] Unlock Bootloader if you don't know how to do it visit this page
2] Download TWRP Recovery from here
3] Download Super Su from Here and transfer it to your device
4] Reboot to Fastbboot mode using Volume Down and Power Key
5] Connect Phone to PC
6] Extract files from Recovery.zip in one location and simply click on flash-recovery.bat
7] After Step 6 is finished Using volume keys navigate and select recovery option and go to recovery
8] After rebooting in recovery select Install zip > and selecting supersu.zip transferred in first step to obtain root access.
9] Reboot
Very much urgent.......plz. reply...........
subinoy.bose said:
Dear Sir,
I have followed all the steps but still not rooted my htc desire 820 dual sim
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064..............this link I have followed.....
but didn't sucess.......
plz....help...Sir
HTC Desire 820 can be easily rooted with few simple steps.
I am not responsible for your warranty loss or device not functioning properly.
Steps
1] Unlock Bootloader if you don't know how to do it visit this page
2] Download TWRP Recovery from here
3] Download Super Su from Here and transfer it to your device
4] Reboot to Fastbboot mode using Volume Down and Power Key
5] Connect Phone to PC
6] Extract files from Recovery.zip in one location and simply click on flash-recovery.bat
7] After Step 6 is finished Using volume keys navigate and select recovery option and go to recovery
8] After rebooting in recovery select Install zip > and selecting supersu.zip transferred in first step to obtain root access.
9] Reboot
Very much urgent.......plz. reply...........
Click to expand...
Click to collapse
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843
Please let us know what is the exact message your getting are you not able to get to Recovery ???
I have been able to successfully root my device by following the steps outlined did not face any challenges hence wanted to check.
Same Probleam here pls help me
I AM SUFFERING FROM SAME PROBLEAM.
i am using desire 820q.
bootloader unlocked.
but when i enter in recovery then that says entering recovery then come back.
pls help me...
problem with htc 820q root
mukulatri said:
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843
Click to expand...
Click to collapse
I'm following this instruction and could not root my device,
My HTC 820q is unlock but when I want read SuperU.zip from Sd card at fastboot>recovery my mobile goes to restart and procedures been uncompleted.
Please help me, is this instruction only for HTC 820?
How we can root HTC 820q?
tah3r said:
I'm following this instruction and could not root my device,
My HTC 820q is unlock but when I want read SuperU.zip from Sd card at fastboot>recovery my mobile goes to restart and procedures been uncompleted.
Please help me, is this instruction only for HTC 820?
How we can root HTC 820q?
Click to expand...
Click to collapse
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064
mukulatri said:
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843
Click to expand...
Click to collapse
Well I have the same issue, recovery looks installed after pressing power button to launch it goes to a screen and go back almost instantly on fastboot screen. I also tried last version of framaroot, does not help either... just get a failed message
尚雷諾 said:
Well I have the same issue, recovery looks installed after pressing power button to launch it goes to a screen and go back almost instantly on fastboot screen. I also tried last version of framaroot, does not help either... just get a failed message
Click to expand...
Click to collapse
Hi there, let's go step by step without "shortcuts" that are typically working on PC/WIn.
1. Unlock bootloader of your phone at HTCdev[dot]com [replace 'dot' with . - sorry for confusion I haven't earned reputation to post external links yet]. All necessary tools (fastboot) will be provided to download during process as well as necessary instructions. You need Windows/Linux or OS X computer to complete this step.
2. Download custom recovery .img file and save it to same directory you have fastboot files (e.g. from step 1) on you computer
3. Start phone in fastboot mode (mind fast boot option in Power settings must be unchecked if you using VolDown [-] start option (not necessary if you use adb reboot bootloader). Battery must be charged over 10% (I suggest 30% to stay secure); connect to computer (phone shall display Fastboot USB)
4. Navigate command/terminal window on your computer to location of recovery image file from step 2 (fastboot files must be there or have a correct path specified).
5. On computer terminal window run command: fastboot flash recovery filename_of_recovery.img . Red section must be exact custom recovery file name.
6. You'll get some communication in terminal. If completed OK will be among them, if failure, there will be FAIL with description of reason (e.g. low_power). If only "waitng for device" dislays, check connection with phone.
7. Navigate phone to HBOOT, then select recovery. If recovery don't start, check step 1 and restart from step 3. If only icon with red ! appears, it means you have stock recovery installed. Please verify from step 1.
8. Once custom recovery is installed and working, use it to flash SuperSU or any other superuser app (must be flashable .zip to be applied). Install just 1 root application, to avoid problems. At this point, you may consider flashing busybox also if you plan extensive file modification, but it's not necessary for root. For any sake, clear cache befor restart.
9. Restart the phone - you shall view SuperSU application or any other superuses app you've flashed i step 8.
Hope now works.
T0ark said:
Hi there, let's go step by step without "shortcuts" that are typically working on PC/WIn.
1. Unlock bootloader of your phone at HTCdev[dot]com [replace 'dot' with . - sorry for confusion I haven't earned reputation to post external links yet]. All necessary tools (fastboot) will be provided to download during process as well as necessary instructions. You need Windows/Linux or OS X computer to complete this step.
2. Download custom recovery .img file and save it to same directory you have fastboot files (e.g. from step 1) on you computer
3. Start phone in fastboot mode (mind fast boot option in Power settings must be unchecked if you using VolDown [-] start option (not necessary if you use adb reboot bootloader). Battery must be charged over 10% (I suggest 30% to stay secure); connect to computer (phone shall display Fastboot USB)
4. Navigate command/terminal window on your computer to location of recovery image file from step 2 (fastboot files must be there or have a correct path specified).
5. On computer terminal window run command: fastboot flash recovery filename_of_recovery.img . Red section must be exact custom recovery file name.
6. You'll get some communication in terminal. If completed OK will be among them, if failure, there will be FAIL with description of reason (e.g. low_power). If only "waitng for device" dislays, check connection with phone.
7. Navigate phone to HBOOT, then select recovery. If recovery don't start, check step 1 and restart from step 3. If only icon with red ! appears, it means you have stock recovery installed. Please verify from step 1.
8. Once custom recovery is installed and working, use it to flash SuperSU or any other superuser app (must be flashable .zip to be applied). Install just 1 root application, to avoid problems. At this point, you may consider flashing busybox also if you plan extensive file modification, but it's not necessary for root. For any sake, clear cache befor restart.
9. Restart the phone - you shall view SuperSU application or any other superuses app you've flashed i step 8.
Hope now works.
Click to expand...
Click to collapse
Thanks for your answer, I have to say I properly unlocked the phone so I do not think there is a way I messed up with this step as when I start bootloader it clearly shows on the top of the screen ''UNLOCKED".
When I flashed recovery on my phone I had no errors prompted or any message of failure. The process went well until a success notification.
Now when I start my phone into bootloader I repeat, I clearly see that recovery has been installed but when I attempt to start it then I'll be almost instantly brought back to the bootloader screen... now I started to wonder if... if an update of android could cause this kind of issue? The point is my phone is using android 4.4.4 and not the factory version 4.4.2. I remember having updated my android version which was perhaps a mistake as this phone is not very old and I was planning to root it in the next days... Now I'm not expert just try to figure it out.
I tried different system to auto root via different apps, some using the PC some using directly the phone, I never get any success...
尚雷諾 said:
Thanks for your answer, I have to say I properly unlocked the phone so I do not think there is a way I messed up with this step as when I start bootloader it clearly shows on the top of the screen ''UNLOCKED".
When I flashed recovery on my phone I had no errors prompted or any message of failure. The process went well until a success notification.
Now when I start my phone into bootloader I repeat, I clearly see that recovery has been installed but when I attempt to start it then I'll be almost instantly brought back to the bootloader screen... now I started to wonder if... if an update of android could cause this kind of issue? The point is my phone is using android 4.4.4 and not the factory version 4.4.2. I remember having updated my android version which was perhaps a mistake as this phone is not very old and I was planning to root it in the next days... Now I'm not expert just try to figure it out.
I tried different system to auto root via different apps, some using the PC some using directly the phone, I never get any success...
Click to expand...
Click to collapse
Ok, please try twrp from Original Android Development tread (it works for me, mind, I'd question it's stability) or Philz recovery (sorry, I found only Chinese, but it's for verivication only: h...ps://drive.google.com/file/d/0BygOvRquk4z8S05kRC1XMXdSbXM/view?usp=sharing - please adjust tt in address - rookie rules).
I'd suggest test running from Fastboot: fastboot boot custom_recovery.img - replace with actual file name from directory you're running terminal.
This shall verify if it's problem with recovery file or any remaining protection...
T0ark said:
Ok, please try twrp from Original Android Development tread (it works for me, mind, I'd question it's stability) or Philz recovery (sorry, I found only Chinese, but it's for verivication only: h...ps://drive.google.com/file/d/0BygOvRquk4z8S05kRC1XMXdSbXM/view?usp=sharing - please adjust tt in address - rookie rules).
I'd suggest test running from Fastboot: fastboot boot custom_recovery.img - replace with actual file name from directory you're running terminal.
This shall verify if it's problem with recovery file or any remaining protection...
Click to expand...
Click to collapse
Does having S-ON bother? I was also wondering about that but all tutorials I found no one mentions anything about the S-ON or S-OFF thing.
But I do have a S-ON under UNLOCKED
what is stock recovery.img name
i dont know what is the real stock recovery.img name.
htc desire 820q dualsim
I can't root my htc desire 820q by this method, is any alternative way?
I just root my phone with same procedure but my phone still show s-on..... How can i s-off my phone.....
Guys: I need your understanding, experience, patience and HEEELP!!!
The history:
2 months ago, I bought a new HUAWEI GR3 (TANGO) TAG-L23. Processor = MT6753T
I tried to root it using KingoRoot. I Messed it up... Got a soft-brick: splash screen boot loop. At that moment, I still had access to Fastboot and Recovery mode (stock recovery).
After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3.
I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm.
Tired of searching a stock/custom firmware for GR3 TAG-L23, I decided to download and flash a GR3 TAG-L22 rom using TWRP.
Result = Messed it up again... this time worst... Hard-bricked I think: the phone didn't show any light, couldn't boot it again in any mode... Dead...
The only hope I had is that it is detected by Windows for about 10 seconds as MEDIATEK USB PORT (COMxx) where xx changes when I connect it from one USB port to another.
Since then, I tried almost every tutorial/video/solution/forum/website over the internet, tried almost every SP Flash tool version from v3.1224 to v5.1628, downloaded every scatter.txt for MT6753 processor, tried changing with/without battery option in SPFT, pressing every phone buttons combos, with no luck...
I always get the same error: S_FT_ENABLE_DRAM_FAIL (0xFC0)
Downloaded and installed almost every driver I found on internet: not overwritting them... I created a Virtual Machine, and test them separately using snapshots. Result = Same DRAM_FAIL error.
last week, got another HUAWEI GR3 TAG-L23, untouched, brand new...
I did the following with the new one:
Flashed TWRP recovery using fastboot commands = OK
Rooted it using SuperSU = OK
executed tons of ADB commands that found over the internet, to dump the partition table and stock rom using dd command = OK (I think... what I got is a bunch of files - system, lk, boot, logo, cache, frp, userdata, secro, recovery, nvdata, protect1 and 2, tee1 and 2, and so on).
Using the partition table information, edited one scatter.txt file for MT6753 and, one by one, adjusted the partition info (start and lenght). I did it because when using any downloaded scatter file, and selecting the files that I got from dd commands, SPFT showed error messages saying them were wrong. After editing it and loading the files that I got from the second phone, SPFT recognized them as good ones.
But.... I'm still getting the d...mn S_FT_ENABLE_DRAM_FAIL (0xFC0) error
Also tried to get a rom backup and scatter file from the second phone using MTK DROID ROOT & TOOLS v2.5.3 with no luck: it shows all phone information (except IMEIs), a green rectangle shows up, but... a weird message appears at right: "ERROR: TotalBytesPerChunk Not Found. Set Default Page/Spare=2048/64 !!!". Then I click on "BLOCKS MAP" button, a new window appears showing the partition info (that already got using adb command prompt) and "create scatter file" button is grayed out... And if I try to perform the backup, it starts fine, but ends with error, and no file is backed up...
Let me mention that I already read and googled the totalbytesperchunk error and the grayed out button stuff and tried all alternatives too, and nothing worked.
My work environment:
PC = Laptop With 8 GB RAM / Windows 10 pro x64
Virtual Machines: Windows 7 pro 32 bits, Windows XP 32 bits, Ubuntu 32 and 64 bits...
What else can I do?
How can I use the second, rooted and working phone to get a rom/firmware working dump? it is possible?
If someone decides to help me, let me know what do you need (dumped files, downloaded scatter.txt files, screenshots, whatever you need...)
COM## is a COM port. You can use a terminal program to directly interact with the device.
You are not completely bricked yet.
I do not have any further details to help you, but I can tell you there is still hope.
Connect the dead device to PC, load up a terminal app (if on windows, just load up the app named Terminal)
See where you can get with that.
good luck
Please Help cesarr4: my TAG-L23 bricked - Need your TWRP
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
antonioroa said:
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
Click to expand...
Click to collapse
I attached the recovery I'm currently using in the second GR3. I'm still looking forward the stock rom and a way to recover the first one... have u found a way to unbrick it?
Here you can find the recovery too: http://forum.xda-developers.com/android/development/recovery-twrp-3-0-2-0-huawei-tag-l01-p8-t3433520
I have the same problem with kingroot, and cannot find TAG-L23 rom.
I sent my phone to huawei support and they said it's a board problem and need to replace, the cost is near to the phone's original price.... No way!
In clangsm web page there's a stock rom but you need to pay for vip membership.
Please help with this issue.
I'm still trying to get a working rom image from the 2nd GR3 that I bought... No luck yet... I'm plenty sure that there is no need to do hardware replacement... can anyone point me to a tool/step-by-step guide to readback and save a flashable rom image from GR3 phone, and a SP tools that works with GR3 chipset/PCB?
Hi, i have a TAG-L01 and i got the same problem, i've tried a lot with no lucky, it seems sp flash tool don't support our device(or is huawei that don't want).
If you have some ideas please tell me, i will help(our devices are exactly the same, all TAG-Lxx are the same)
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
srgg01 said:
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
Click to expand...
Click to collapse
Done. Where can I share it for you?
cesarr4 said:
Done. Where can I share it for you?
Click to expand...
Click to collapse
please share your ROM in google drive. i've got same problem here.
Any link to the TAG-L23 ROM? please share as I believe mine is corrupted.
Guys
I am trying to flash my zenfone 2 with
"Intel platform flash tool"
And it is the only software that recognizes and shows that my device is connected.
But it required a "flash.xml"file for the process and I cannot find such file in my downloaded stock ROM.(after unzipping)
Please any guide
How can I flash my zenfone which has a damaged Bootloader? (So no boot options are available)
And where can I find that "flash.xml" file?
Thanks.
Istiraven said:
Guys
I am trying to flash my zenfone 2 with
"Intel platform flash tool"
And it is the only software that recognizes and shows that my device is connected.
But it required a "flash.xml"file for the process and I cannot find such file in my downloaded stock ROM.(after unzipping)
Please any guide
How can I flash my zenfone which has a damaged Bootloader? (So no boot options are available)
And where can I find that "flash.xml" file?
Thanks.
Click to expand...
Click to collapse
you need to use xFSTK to flash the bootloader. even if you use intel flash tool that also you have to use xFSTK as external tool to recover your device. unfortunately you will not get that xml file you have to write it yourself. i could write it if it was necessary. but i don't think that will have any beneficial comparing the time spent on it. go to the following guide as do step by step as recommended. keep in mind if xFSTK in unable to recover you BL. intel flash tool can not help even you write or get that flash.xml. one more tip regarding recovering device. if you r able to get the temp bootloader. do not use asus flash tool. use commands method. AFT may push you to unrecoverable state.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Thanks but something went wrong.
Hi.
Thanks for the reply
I have performed the process in exact same way it was described.
But something went wrong,
I don't know what exactly happened.
Now my phone isn't even turning on
Or vibrating or no USB sign.
But isoc driver and xfstk is still detecting my phone as moorefield device.
I really don't know what happened.
I have tried the process at least 20-30 times
But every time its saying
"Errors encounter during FW download : Aborting"
And fail.
Please help me get rid of this
EDIT: included rough procedures for OEM unlocking, and updated link to recovery-verified.img (Sorry for uploading the wrong file ><)
Hi all bv9000 pro Users!
Recently I went on a journey to root this awesome rugged phone with one purspose: to remove that F*@(#&$ god awful loud annoying sound triggered by the OS when you use a camera app to take a picture + the boot startup sound (A bug blackview hasn't gotten around to fixing).
I successfully managed to port TWRP 3.1.1 from the Blackview bv8000 Pro and run it on the Blackview bv9000 Pro-f!
I've then managed to flash in Magisk to gain root access.
DISCLAIMER: I do not take responsibility for any bricked phones caused by the process, do so at your own risk (yadayadayada).
NOTE 1: Although I've got it running on the bv9000 Pro-F, this image should also work for the non-fullHD version, if someone can test this I'd be happy.
The link to the stock ROM (with the modified recovery img) can be found in the post below.
NOTE 2: No need to download anything other than what I've listed, Magisk is included in my custom recovery to circumvent the need to load the devices encrypted storage (or any other external storage) nothing stops you from mounting external usb storage.
What you'll need:
- USB Mouse (As there is no touchscreen input support, your device should have come with a usb-c otg cable so there's no problem here!)
- MediaTek SP Flash tools (I'd recommend the latest version) https://spflashtool.com/
- unlocked bootloader (You should be able to do this via the developer settings -> unlock OEM Bootloader)
EDIT: To unlock the boot loader, do the following:
1) Go to settings -> unlock OEM Bootloader (tick)
2) plug your device in (assuming you have ADB installed), use adb to access fastboot via. command prompt:
"adb reboot bootloader"
Then once the device is rebooted into fastboot mode
"fastboot oem unlock"
KEEP IN MIND THIS WILL REMOVE ANY FILES, so back them up
- I've done this with windows, but you should be able to repeat with linux no problems!
- A little patience
Pre-preparation:
First install any updates and back up your data (it's just easiest to use the google cloud backup as restoring becomes easy as pie, updating also fixes the setup wizard crashing on first setup). This is necessary because OTA updates cannot be performed with TWRP recovery, and flashing TWRP before doing OTA updates will flick the device into a recovery boot loop.
Install the SP Flash tools, and the MediaTek VCOM Drivers
(I won't link the specifics here, a quick google search should be able to help you, just note you might need to disable driver signature enforcement)
Two options for flashing:
1)
My Full Stock ROM already pre-prepared for flashing:
Patched ROM
No need for extra prep here! you should just be able to load the scatter
2)
My custom patched TWRP stock rom: recovery-verified.img
Blackiew's stock rom: stock rom
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
Once you've done with the pre-prep, switch off your device, take a deep breath and you're ready to go!
Steps!
1) Load up SP Flash Tools, select the android scatter file you've downloaded in the R06 folder
2) Select Download Only (I MEAN IT, FORMATTING WILL REMOVE YOUR IMEI AND RENDER THE PHONE USELESS)
3) Deselect everything but recovery (You only want to flash this)
4) Hit download
https://pasteboard.co/HkufwZZ.png
5) Hold volume up + power and plug in your phone, keep the volume up button held
6) very quickly the flash should be complete, and you should be greeted with a big ol' green tick to verify
https://pasteboard.co/HkuiTBB.png
7) Once you're done, remove your USB cable, plug in the OTG then we proceed to flash magisk
8) Hold power + volume up until you reach the bootloader, then use the menu to select recovery
9) You *should* be greeted with the TWRP recovery screen (Which is great success! )
DON'T PANIC IF YOU CANNOT USE THE TOUCH SCREEN, the kernel I've patched is missing this, seems the driver is different between touch screens, just plug in your OTG mouse to continue from here!
10) Use your mouse to first hit cancel, we don't need to decrypt the user data storage.
11) But oh no! it's all in Russian (no problem, Next step sorts that)
12) Use your mouse to navigate the menus as shown here to change to English! (or your preferred language) Change Language
13) Click install, then navigate up folder levels until you are in the root directory
14) scroll down and click on Magisk.zip, install it, allow it to install any apps as system apps (because this will then install to the system image, not the userdata)
15) reboot the phone (if it hasn't rebooted already)
16) You should be able to boot into your usual phones OS, if you don't see Magisk listed in your phone apps, just download it from here:
Magisk Manager
17) Congratulations! You should have complete root access :laugh::laugh::laugh:
Feel free to express your thanks, or list any problems you have, but keep in mind my studies take all my life, so I may not be able to help with all the problems you have
Congrats! Would it work on the BV9000 HD version?
Hi!
From what I've seen they both run the helio p25 chip
(Just a difference in RAM size) so it should.
You're more than welcome to try.
Just keep a backup of the original ROMs recovery. If something goes wrong during the boot to recovery you can easily re flash
hi i tried both optinos but they didn't work for me
I tried the first and the second options and it was showed me same error:
ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
I tried download only, format all and download, if i install original ROM its installing without problems!
In settings-> developer options -> OEM unlocking is enabled
can someone give me tips if I'm doing something wrong. thanks
My phone is Blackview BV9000PRO-F
Hello,
i have the blackview 9000 pro Hd (not full hd)
i first tried your prepared patched rom = not working (get erorrers in step 6)
then i chose step 2 and i was thinking to use the stock rom from the NOT full hd rom
now i get a green screen from the flashing: but after rebooting in recovery nothing happens, just normal reboot then
perhaps this is not so clair for me:
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
the file name you posted here " My custom patched TWRP stock rom: recovery-verified.img" is ramdisk-recovery.img
i replaced the ramdisk-recovery.img... it is not clair need to replace recovery-verified.img to?
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
>
dingsje said:
Hello,
>i have the blackview 9000 pro Hd (not full hd)
>i first tried your prepared patched rom = not working >(get erorrers in step 6)
>then i chose step 2 and i was thinking to use the stock >rom from the NOT full hd rom
>now i get a green screen from the flashing: but after >rebooting in recovery nothing happens, just normal >reboot then
>perhaps this is not so clair for me:
>- Download the stock rom, backup the recovery->verified.img in the R06 folder, and then replace it with >my custom patched TWRP stock rom (file name should >be the same).
>- Run "CheckSum_Gen.exe" once you replaced the file, >it will generate the necessary checksum to allow SP >flash tools to successfully flash recovery.
>the file name you posted here " My custom patched >TWRP stock rom: recovery-verified.img" is ramdisk->recovery.img
>i replaced the ramdisk-recovery.img... it is not clair >need to replace recovery-verified.img to?
Click to expand...
Click to collapse
Hi,
I've uploaded the wrong file, the uploaded file should be recovery-verified.img.
I'm uploading a new file and will correct the link now,
Please accept my apologies ><
hyperlethalvector92 said:
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
Click to expand...
Click to collapse
I already did this step:
Enable developer options-> OEM unlocking is enabled
Is that enough for this MTK phone to be unlocked the bootloader ?
And tried the both options but the results are same.
I have been unlocking bootloaders on many phones but first time MTK phones. If i try with adb commands it recognize when is in the android with command adb devices and show my device but if I try reboot bootloader and check in device manager in windows its show its connected and drives are correct but if i try to show the devices, it doesn't show any device connected
Hi,
You need to install fastboot drivers once it's in bootloader mode,
then use fastboot, not adb.
"fastboot oem unlock"
Then follow instructions.
simply doing settings -> oem unlock won't unlock the bootloader, it allows you to do so later via. fastboot
Check the original post, I've added the extra instructions sorry about the confusion!
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
zlatkomas said:
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
Click to expand...
Click to collapse
I'm glad ^______^
Enjoy your rooted phone
I used this video to root my bv9000 pro hd
much easier than this above, i think it works to on bv9000 pro fhd
https://www.youtube.com/watch?v=c48ISLPjn4Q
Congratulations .... I need a tip,.
And, brother, thank you very much. Worked perfectly.
But first I would like to get you a tip ..
One of the main reasons I have done all this complicated process was to be able to disable the crap of the loud music that plays when the device is started.
I want complete silence at startup.
How do I disable this ****?
Code for Huawei mobile Wi-Fi e5577s-321
Pls help unlock my Huawei mobile Wi-Fi e5577s-321
Imei
860782038163889
TWRP looping after OTA update
My dear, the procedure worked very well, until an OTA update was downloaded.
You are now looping on TWRP. How do I get out of this?
:crying:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
mackie_ma said:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
Click to expand...
Click to collapse
Hi guys, lemme apologize for disappearing, life and whatnot!
For those stuck in a TWRP boot loop, simply restoring the original recovery then restarting the phone will be enough to fix the problem.
(Actually you really don't need TWRP after the phone is rooted, maybe I should update the guide?)
Many Thanks
First off, thank you for your hard work. Loved the "**** it we have an OTG cable let's use it" haha. It works fine for me.
Second, do you happen to know if someone has ported Oreo on our bv9000 ? Or do you know of any ETA ?
Thanks again,
Cheers
Anyone tried on the BV9000 Pro? Don't think mine is 'F' OR 'Fhd'.... I must have first model brought out...
Ugh.. Windows and Drivers?!?!
I keep getting Driver not Recognized in Windows 7 Pro X86.
I installed the latest vcom/usb drivers, in legacy also. No Go.
I installed from several other sources the drivers, including the Automatic Mediatek driver install. No Go.
So if anyone has a tip for me, please let me know because once more Windows is proving itself ridiculous. I can't even get to the storage of my phone. Did something change with a Windows Update that it's not allowed anymore?
I put my BV9000 Pro in OEM Unlock and USB Debugging. I backupped everything. My phone is ready for it. It's as ready as Amy having coitus with Sheldon for the first time.
I recently rooted my OnePlus 5t. I found out that the root was unnecessary for what I needed, so I decided to undo the process. Somewhere during that process, I messed up big time. Currently, it has no OS and has the stock recovery, but I am unable to flash anything to it. It does not show up in file explorer anymore, but it does show up when I used "adb devices" command. When I did try to flash the OnePlus stock OS, I got a "compatibility.zip error". When I removed the "compatibility.zip" from the OS file, it then gave me an "update-binary" error. Now, I have no clue what to do. Any help?
wwkings said:
I recently rooted my OnePlus 5t. I found out that the root was unnecessary for what I needed, so I decided to undo the process. Somewhere during that process, I messed up big time. Currently, it has no OS and has the stock recovery, but I am unable to flash anything to it. It does not show up in file explorer anymore, but it does show up when I used "adb devices" command. When I did try to flash the OnePlus stock OS, I got a "compatibility.zip error". When I removed the "compatibility.zip" from the OS file, it then gave me an "update-binary" error. Now, I have no clue what to do. Any help?
Click to expand...
Click to collapse
There are fixes for this, you can use unbrick tool or just format data and flash oos if it gives you compatibility error you must use 'mixplorer' file manager to delete compitibility.zip :good:
intoxicated.mad said:
There are fixes for this, you can use unbrick tool or just format data and flash oos if it gives you compatibility error you must use 'mixplorer' file manager to delete compitibility.zip :good:
Click to expand...
Click to collapse
The unbrick tool does not work because I cannot get my device to be recognized as a SnapDragon device. I also cannot use mixplorer, because the device has no OS. I did manage to get TWRP back on it, but I am still unable to to flash any ROMs.
wwkings said:
The unbrick tool does not work because I cannot get my device to be recognized as a SnapDragon device. I also cannot use mixplorer, because the device has no OS. I did manage to get TWRP back on it, but I am still unable to to flash any ROMs.
Click to expand...
Click to collapse
UPDATE: I found out that in order for the unbrick tool to work, the phone needed to be put into EDL mode. I did this using "adb reboot edl". This allowed the device to show up correctly in order for the unbrick tool to find it properly.