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.
Related
Hello Guyzzz!!!!!
A Great Newzz for ALL!!!!! First the recovery was not compiled by me!
But NOW I am BACK with a FULLY WORKING RECOVERY AND FULLY COMPILED BY ME :good:
We have now a FULLY WORKING CLOCKWORKMOD RECOVERY v5.0.2.8.
The CLOCKWORKMOD RECOVERY is TESTED on :-
1. LG OPTIMUS 3D MAX P725
2. LG OPTIMUS 3D MAX P720H
I HELD NO RESPONSIBILITIES FOR BRICKED PHONES. YOU MAY TRY ON P720 BUT AT YOUR OWN RISK.
Credit Goes to :-
1. I, Me and Myself ( For taking the initiative,compiling testing and removing all bugs )
2.. Cynogenmod for the SOURCES.
3. P720H tester ZOOM.
According to me, the CWM RECOVERY is fully working.
HERE ARE THE STEPS TO INSTALL THE CWM RECOVERY :-
Download the CWM RECOVeRY FINAL.zip from the link given below :
http://www.mediafire.com/?p59d9ppjlhkcp67
Copy the cwm5.0.2.8.img on the ROOT OF THE SDCARD not the External SDCARD ( Root of SDCARD means not in any folder )
The BIGGEST REQUIREMENT IS YOUR OPTIMUS 3D MAX should be ROOTED!!!
Now download ANY TERMINAL EMULATOR from the GOOGLE PLAY!!!!!
You can try this :-
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
And install it.
Type the following commands in TERMINAL EMULATOR :-
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/sdcard/cwm5.0.2.8.img of=/dev/block/mmcblk0p6 bs=4096
Once complete.
Turn off your phone.
1st hold 3d key then volume down button and at last power button.
Keep holding till the LG LOGO appears and leave when it appears.
You will enter the CWM Recovery
Proof of the Recovery :-
Worked like a charm! First I couldn't get the # to appear (the phone WAS rooted) so I just used the terminal emulator you specified, and that solved it.
lordasphyxia said:
Worked like a charm! First I couldn't get the # to appear (the phone WAS rooted) so I just used the terminal emulator you specified, and that solved it.
Click to expand...
Click to collapse
Happy to help you.
"HITTING THANKS WILL ENCOURAGE ME MORE":good:
Eklovya said:
IT TOOK MORE TIME TO DEVELOP THIS RECOVERY THAN THE TIME YOU WILL TAKE TO JUST " HIT THANKS".
Click to expand...
Click to collapse
dude you are not developed this recovery, it's created by me, you only unpacked my recovery using kitchen , that not call develop
Where did i mentioned that I DEVELOPED???
I clear mentioned that you compiled and i removed all bugs...
Sent from my LG-P725 using xda premium
Thread for this exists from original dev
http://forum.xda-developers.com/showthread.php?t=1889468
Thread closed
Edit: Thread reopened for a newly compiled version
HELP!!!!
After downloading an update from LG it allways boots to recovery!!
TommyX235 said:
HELP!!!!
After downloading an update from LG it allways boots to recovery!!
Click to expand...
Click to collapse
Try doing a factory reset.!!!
Sent from my LG-P725 using xda premium
tryed everything .. factory reset .. i have a backup from my original rom.. when i restore it i also boot into cwm.
i can start sw update mode (vol +) but either there nor in cwm i have adb access..
i tryed kdz but i don't know the dev type .. i tryed TI / 3GQCT etc. the program crashes
its breaking my heart .. i have this device the first day and now its broken!
ARRGG!!!
I still have the backup of the mmcblk0p6.backup
can i do anything with it?
maybe it is possible to install it via zip in cwm?
TommyX235 said:
tryed everything .. factory reset .. i have a backup from my original rom.. when i restore it i also boot into cwm.
i can start sw update mode (vol +) but either there nor in cwm i have adb access..
i tryed kdz but i don't know the dev type .. i tryed TI / 3GQCT etc. the program crashes
its breaking my heart .. i have this device the first day and now its broken!
ARRGG!!!
I still have the backup of the mmcblk0p6.backup
can i do anything with it?
maybe it is possible to install it via zip in cwm?
Click to expand...
Click to collapse
Install LG SUPPORT TOOL IN PC.
KEEP YOUR PHONE IN DOWNLOAD MODE.
CONNECT TO PC.
OPEN LG SUPPORT TOOL.
IN TOOLS SELECT RECOVER PHONE.
INPUT YOUR IMEI.
AND WAIT FOR THE RECOVEY PROCESS TO FINISH.
ALL WILL BE DONE SAFELY AND YOU WILL GET THE PHONE WORKING
Sent from my LG-P725 using xda premium
this damn tool doesn't recognize my IMEI also when i enter my device type p720 & Serial a small window pops open showin my device and my serial .. when i click ok .. another popup telling .. please check your device or something.
---------- Post added at 08:36 AM ---------- Previous post was at 07:42 AM ----------
also why is adb not working?
Is there a way to get it workin in CWM?
In CWM in section advanced you can do show log.
CWM-based Recovery v5.0.2.8
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=omap4430
ro.revision=7
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:checking for extendedcommand...
I:Skipping execution of extendedcommand file not found...
Does this mean something?
Also this lg Tool only worked for me when adb also was working.
TommyX235 said:
this damn tool doesn't recognize my IMEI also when i enter my device type p720 & Serial a small window pops open showin my device and my serial .. when i click ok .. another popup telling .. please check your device or something.
---------- Post added at 08:36 AM ---------- Previous post was at 07:42 AM ----------
also why is adb not working?
Is there a way to get it workin in CWM?
In CWM in section advanced you can do show log.
CWM-based Recovery v5.0.2.8
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=omap4430
ro.revision=7
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:checking for extendedcommand...
I:Skipping execution of extendedcommand file not found...
Does this mean something?
Also this lg Tool only worked for me when adb also was working.
Click to expand...
Click to collapse
is it somehow possible to activate nable adb access in CWM 5.0.2.8?
or can i flash a zip to do this?
Again .. i can enter S/W Upgrade Mode
There i only see S/W Upgrade
Please wait
while upgrading....
(NO ADB ACCESS! But the Tool recognize the phone but won't let me start the sw upgrade.)
In CWM i can mount & unmount storage and flash zip files or backup / Restore.
BUT no ADB access and Restoring the backup i made doesnt work either)
What breaking my head is that the LG Update must had set a flag to boot into recovery after i downloaded it so mindless.
Since then i stuck in cwm bootloop. There mus be a way to reset this flag. Somehow!!!)
Its over .. i flashed CWM-Loop-DeLooper -> now i stuck @ LG Logo.. also vol+ to enter S/W Upgrade not working anymore. Now its bricked! ARGH!
TommyX235 said:
is it somehow possible to activate nable adb access in CWM 5.0.2.8?
or can i flash a zip to do this?
Again .. i can enter S/W Upgrade Mode
There i only see S/W Upgrade
Please wait
while upgrading....
(NO ADB ACCESS! But the Tool recognize the phone but won't let me start the sw upgrade.)
In CWM i can mount & unmount storage and flash zip files or backup / Restore.
BUT no ADB access and Restoring the backup i made doesnt work either)
What breaking my head is that the LG Update must had set a flag to boot into recovery after i downloaded it so mindless.
Since then i stuck in cwm bootloop. There mus be a way to reset this flag. Somehow!!!)
Its over .. i flashed CWM-Loop-DeLooper -> now i stuck @ LG Logo.. also vol+ to enter S/W Upgrade not working anymore. Now its bricked! ARGH!
Click to expand...
Click to collapse
Can you come on chat? So that i can help you!!
Sent from my LG-P725 using xda premium
can this tutorial work on ICS su870?
joseph168 said:
can this tutorial work on ICS su870?
Click to expand...
Click to collapse
Nop this will not work. As the bootloader is locked for su870
Sent from my LG-P725 using xda premium
LG P725 CWM Problem
Hi guys need help, i installed this cwm recovery with no problems, when i start it i see menu, can move up and down but i can`t launch anything. I read at different sites that i should to use shutdown key or 3d key but they don`t work. Also i install newer version 6.... but there are this problem too. I have LG 3D max (P725) version o firmware v10f.
Andrelius1 said:
Hi guys need help, i installed this cwm recovery with no problems, when i start it i see menu, can move up and down but i can`t launch anything. I read at different sites that i should to use shutdown key or 3d key but they don`t work. Also i install newer version 6.... but there are this problem too. I have LG 3D max (P725) version o firmware v10f.
Click to expand...
Click to collapse
use volume keys to move up and down.
and capacutive keys to select
Sent from my LG-P725 using xda premium
CWM problem
Eklovya said:
use volume keys to move up and down.
and capacutive keys to select
Sent from my LG-P725 using xda premium
Click to expand...
Click to collapse
Thanks a lot! Its strange that in any instruction not says this way of use CWM, i read a lot differents cwm instructions, but the always the same - use power off key ot use 3d button.
Who don`t how to use CWM menu :
"properties button" - up
"home button" - down
"back button" - back
"search button" - ENTER
Cannot select options in cwm
Hi Eklovya,
Brilliant job done!!
I have successfully rooted and installed CWM following your method.
However, when i go boot to CWM, I can use the volume buttons to highlight the options (I wanted to backup), but I am not able to select the options. i tried the power button and the 3D button, no go. What do i do?
I just exchanged my P920 and got myself this P725 today!!!
schubeir
EDIT: my bad!!! found the solution in the post just above!!!!
schubeir
(possibly long post , I will try to make a post at least a little fun to read).
Guys, I humbly come before you, kneeling and desperate, trying to solve my problem .
I've serarched XDA and a lot (!!) of others forums and comunities to revive my P720H (LG optimus 3D Max in Brazil).
I am not a complete noob in custom firmwares for Android, but this time, the LG phone gave me a hell of a headache (and almost a divorce, for the 3 days going too late to bed, trying to solve it).
I will explain what happened and what I've already tried to do and the results.
Causes:
I've tried to install ClockworkMod in my P720H because it still was in Android 2.3.6 (I think).
I've successfully rooted the phone using this thread: http://forum.xda-developers.com/showthread.php?t=1886057 with the SuperSU app on GooglePlay.
When I asked CWM app to reboot in recovery mode (to wipe things and install the .zip file on the sdcard root) things got bad.
My phone could not get passed the LG logo anymore.
So far we have a cause: CWM app did something to the phone. I am not able to boot the recovery menu nor to pass the LG logo on the screen.
Over the communities we may find that it's a common issue.
It is important to say that I am able to enter the 'S/W updating' state. When I connect the phone to the computer, holding VOL+ and placing the battery, I got the S/W screen.
What can I do? In several posts (even here in xda) we may find 3 or 4 different solutions to restore the phone. I think I've already tried everything, but I am sure that the steps became fuzzy in my read and I mixed the solutions in the end.
Drivers:
- I have already the drivers installed: When I connect the phone (with or without battery and with or without vol+ pressed) my Device Manager recognizes everything. I don't have any component marked as 'unknown device' or with exclamations points or anything. This is a good thing, I guess. I had to install more than one thing to solve every driver problem. I don't remember exactly, but I think that the LGDriver-something and the omap4430 something too.
Solutions:
- I have tried the LG Support Tool and so far it appears to be the closest to a solution that I've reached. With the phone connected (in S/W mode or no), I insert the IMEI and the software recognizes the model and starts downloading something (500mb approx.). But after decompressing, during the installation phase, it gets stuck at 4%. I waited for more than 20min and still got nothing better than 4%. It appears to be a common issue too.
- The LG_FlashTool (version 1.2) does not work either. In fact, it does not even recognizes the phone. I've changed the COMport to 41 (according to some guide) on Windows Device Manager and chose the port 1 on LGFlashTool. Even after selecting the kdz, bin and fls files, the software does not connect to the phone. I don't have a screenshot here, but I've seen here in xda that the software displays the model of the phone on the top and a READY message on port 1. Mine does not do it.
- KKDZ_FW_UPD_EN: I've tried this one but it does not even start working. The interface is not that good, so I don't know where I may be failing. I need to 'read phone information' or not? What do I have to chose on each combobox? How to proceed?
And why the hell is there so much .exe on this thing? Do I have to run a apache server to do something?!
- OMAP4BOOT: This one connects to the phone and works, I think. But I don't know its purpose. It's just to place the phone on 'S/W updating' mode? If so, it's useless, because I can enter it easily. If no, maybe I am missing something. Either way, I don't have a version for the P720H. If I remeber correctly, it proposes P999, P760, P870, ... I choose P760 to test it and it works (apparently, again).
- SmartFlashTool: I don't remember if I have already tried this one. As I said, it was too much already.
- NVFlash: I've found it only to G2X, so I didn't know if I should try forcing it to my model. I can give it a try if you help me.
Other softwares and downloads:
KDZ:
- V10B_00 and V1A_00: found today and downloaded for my model and country (will try to extract things and use it later).
- LG_P725_V10F_00: I was using this one until yesterday, because I didn't have the one to P720H
- LGP700AT-01-V10d-232-03-SEP-11-2012+0.dz : Found in an indian repository of some kind of LG data leak. Apparently is useless. DZextract gave me nothing.
DLL: LGP720_20120330_LGFLASHv1377: Needed in some of the softwares above (LG FLashTool? I don't remeber).
BIN and FLS: LGP725_LG_P725_V10F_00_AP.bin and LGP725_LG_P725_V10F_00_CP.fls, extracted from LG_P725_V10F_00.kdz. I don't know, but I should try extracting these from the V10A_00, because apparently is the correct one for my model/country (I am not in my house right now).
Well... :crying:
tl;dr version:
I am facing a LG logo boot loop in P720H. I've tried to reboot CWM in recovery mode but it didn't work. I've tried several approaches but I don't even know what is the point of each one. I found that this is the best topic to use, because is one of the fews that covers the P720H.
I have all those softwares and almost 5gb of downloaded material (kdz, img, bin, exe, ...) but I don't know what I am supposed to use.
In the end, I want my P720H in android 4.x if possible. If not, I just want the crap 2.3.6 again. :crying:
Can you help me? I am not a total noob in custom firmwares and roms, and I am willing to pass all the information that I can :fingers-crossed:
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.
Hello together,
after many tries to get my nokia 3.2 rooted, i end up now with a black screen.
Only the Qulacomm mode is working.
Get anyone managed to flash the stock firmware with QFIL provided from the rooting thread?
I always end up with "sahara fails".
Every help is welcome!
Thanks!!!!
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
page1875 said:
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
Click to expand...
Click to collapse
please do, i encountered a similar problem.
HowTo Flash STOCK 00WW
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
page1875 said:
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
Click to expand...
Click to collapse
Thank you for your reply, it seems that your problem is more complicated than mine.
I have a global variant with 00WW software and i attempt to root the phone. I successfully flash the patched boot.img and had root access. However wi-fi didn't work after that.
Since before flashing the patched boot.img my phone was running on a different firmware from the one that boot.img was extracted from, so i think that was the problem.
I attempted to use QFIL to flash my phone back to 00WW_15 and it failed half way, bricked my phone.
Normally you can use the EDL Mode every time.
My phone only showed black screen and it was always possible to connect in EDL Mode and flash again.
Did you try to flash again? What happens then?
Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
Click to expand...
Click to collapse
What did you mean by Flash the given image ? Was it flash the firmware package with QFIL ?
My main problem is flashing, it always failed half-way and the error log reported that needed files were missing from the package.
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
page1875 said:
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
Click to expand...
Click to collapse
@update:
Also the files "demoapp.img", "dp_AP_signed.mbn" and "dp_MSA_signed.mbn" are missing.
Remove them from the XML file and try again!
@update
Okay QFIL still failed half-way but i manually flash the user images and my phone boots normally now
Hello,
my nokia 3.2 europe variant wont boot up its stuck in fastboot mode. What can i do to bring it back?
I get this: FAILED (remote: partition table doesn't exist)
P.S. if i do a fastboot reboot it boots back into bootloader
I also had this problems for many many times and don't know what went wrong when this happens.
The only thing that helped was flashing the complete firmware again in EDL-mode.
You can try first to flash only the 5 user-images with fastboot, which i mentioned before in this thread.
I uploaded this files for you, because you don't will find the europe files in internet yet.
Here is the link:
https://transfernow.net/81iti7q21s0s
Good luck!
Hi,
Thank you very much. Is this the complete Firmware? (All Images from Device) Another question: I couldnt Access the recovery System. Did you have the same Problem when your Nokia didnt boot up and was stuck in Bootloader? So is this normal that the recovery is unaccessible?
Yes, that also happens sometimes with my phone.
No, that are not all firmware files, which you need to do a full EDL-Flash.
But with this files you can first try a fastboot flash!
If it does not work, you can take all the other files from the Global-Stock-Firmware, given in the thread https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206.
Delete the 5 files with the same names, flash the Global-Stock-Firmware in EDL-Mode, with QFIL or QDL, (without the 5 files) and in the following flash the 5 europe-image files with fastboot.
Thanks, ive sent it in and got Friday a 00WW Variant of the device back. I will upload those User images for 00EEA to my Google drive so that anyone who needs those files can download them
hello
i wanted to install custom rom and i bricked my phone. i lost recovery mode and i have only fastboot mode .but can not write any img file for example twrp.img beacuse show this error : FAILED (remote: partition table doesn't exist). can please anyone help me.
thank you very much
thanks so much i was able to put my phone back to life. i had almost given up.
smure said:
thanks so much i was able to put my phone back to life. i had almost given up.
Click to expand...
Click to collapse
Hello to ervery one
how you flashed your phone. can you please guide?
i am also stucked in fastboot mode after rooting.
damn... I've been finding on how to restore the wifi and sound because I uninstalled magisk and it failed. I don't think I can thank you enough for this post.
Hello everyone.
I still have this phone in title.
Its actual status is bricked but:
1. I am able to enter in download mode but not seen in Windows Device Manager more Linux.
2. I can enter in qhsusb_bulk mode (9006), detected in Windows and Linux but it's a tricky, unstable connection.
3. Managed to flash, using dd in Linux, the TWRP recovery but I can't access it.
4. Tried to do a factory reset - I can get to the point where it's asking if sure...but nothing happens beyond that point.
5. I have all the programs found to be used in this forum but don't have a clear image on what and how to use them.
6. I need the partitions *.img files for the 32 GB version, not the 16 gb.
7. I have the kdz and TOT files for my version. But how to I use them?
Someone can PLEASE help me?
Thanks.
BigBadSheep said:
Hello everyone.
I still have this phone in title.
Its actual status is bricked but:
1. I am able to enter in download mode but not seen in Windows Device Manager more Linux.
2. I can enter in qhsusb_bulk mode (9006), detected in Windows and Linux but it's a tricky, unstable connection.
3. Managed to flash, using dd in Linux, the TWRP recovery but I can't access it.
4. Tried to do a factory reset - I can get to the point where it's asking if sure...but nothing happens beyond that point.
5. I have all the programs found to be used in this forum but don't have a clear image on what and how to use them.
6. I need the partitions *.img files for the 32 GB version, not the 16 gb.
7. I have the kdz and TOT files for my version. But how to I use them?
Someone can PLEASE help me?
Thanks.
Click to expand...
Click to collapse
There's already a thread on it. https://forum.xda-developers.com/t/...nload-mode-after-ota-on-rooted-lg-g2.2582142/
For a stock rom, here's the link. http://storagecow.eu/?dir=Xda/LG G2/Stock
This might can help.
Absolute Territory said:
There's already a thread on it. https://forum.xda-developers.com/t/...nload-mode-after-ota-on-rooted-lg-g2.2582142/
For a stock rom, here's the link. http://storagecow.eu/?dir=Xda/LG G2/Stock
This might can help.
Click to expand...
Click to collapse
Thanks, but already did that.
I end up extracting img files from the TOT file and sending them to the phone using the dd command.
And I dd-ed every single file (36 files per total) but with no use.
Tried with TWRP recovery and with stock recovery...nada!
It must be the jumpy connection. I will try again someday later on.