Hello folks,
Bought a Mediapad T3 7 from Walmart recently. Has anyone found root yet? I tried all of the Kingroot, etc. APK's so far. Don't waste your time. Tried them all.
If our magicians here can find root, I'd love it!
Thanks,
Rich
Got the same request. Tried KingRoot and iRoot, cause you never know
I'd imagine it's coming one day or another. Tablet isn't that old yet.
Just a matter of somebody compiling twrp for it, I'd imagine..
I would love to know if any progress has been made. I need TWRP and an AOSP ROM. I love the devices look and feel, and its bluetooth operability. but absolutely DESPISE the UI and how it operates.
+1. Decent little tab but no built-in ext4 format for external SD, hoping for root. Getting it to run on stock android would be neat, too.
I tried the online root solutions-none of them work. Just tried Kingroot today and no good.
Same here I got a new huawei t3 10" great tablet by the way but no way I can root it.. I've tried all the Internet suggested ways and nothing seem to work at all but I manage to get the Device ID typing a code in the dialer.
Mercer99 said:
Same here I got a new huawei t3 10" great tablet by the way but no way I can root it.. I've tried all the Internet suggested ways and nothing seem to work at all but I manage to get the Device ID typing a code in the dialer.
Click to expand...
Click to collapse
hi, are you able to make calls on your T3 10? If yes, can you let me know your firmware details, thanks
buddimanv said:
hi, are you able to make calls on your T3 10? If yes, can you let me know your firmware details, thanks
Click to expand...
Click to collapse
Hi there, about that yes I can make phone calls with it I bought the Model with the 4G option (there is 3 models from the same Huawei tablet one of them is WiFi only and the other two can make phone calls) also I managed to unlocked the bootloader by using the device ID I got earlier and Huawei website.
mine is AGS-L09 model
Thanks Mercer99, appreciate it (for your device security, can you remove the image as this has your IMEI)- we have the same model, but different firmware.
AGS-L09C199B002 is “Saudi Arabia Oman Kenya Cameroon Jordan Qatar Ghana Android 7.0 EMUI 5.1” region.
AGS-L09C127B031 is “Greece Hungary United Kingdom Nonspecific Android 7.0_EMUI” . The dialer/calling function is disabled on this firmware - confirmed on Vodafone and EE network.
Is there any way you can extract the OEMINFO from your device and share it with us. This should enable me to debrand the phone if I can find your firmware (downloaded EUROPEAN version with Firmware finder already – so really need an European OEMINFO).
My phone is still locked to Vodafone so I am not sure whether I can flash the firmware or even need root to flash a different OEMINFO (bootloader is unlocked already).
Sorry buddimanv I would love to help but I don't know how
OEMinfo
Last time I did was with P9 Lite - changing from EE to European firmware using a tool (I think SRK Tool or “VNS-L21/22/23/31 [EU] Toolkit [0.0.0.12] All-in-One”) but it was rooted - seems like root is needed before anything. I think the process would be to change the firmware on tablet as well.....
I was hoping as bootloader is unlocked, we can retrieve OEMINFO from fastboot or something and debrand….would be good if anyone can clarify.
Possible Root Solution
Anyone prepared to test rooting method below?
How to install Magisk with ADB
How to install Magisk with ADB
Does not require the availability of custom recovery and root-access
1. Delete all other types of root-access and restore the partition image of the boot partition
2. Download Magisk v13.6 or later and download / unzip from the firmware partition image of the boot partition
3. Unpack the Magisk archive, put the boot image of the boot partition in the same folder, and rename it to boot.img
4. Rename the folder with the name corresponding to the architecture of your device (arm, arm64, chromeos, x64, x86), in magisk_inject
5. In the terminal, change the current directory to the folder with Magisk and run the following commands one at a time:
PHP:
adb shell "rm -rf / data / local / tmp / *"
adb push META-INF / com / google / android / update-binary common magisk_inject boot.img / data / local / tmp
adb shell "cd / data / local / tmp / magisk_inject; mv ../common/*.; chmod 755 *; sh ../update-binary indep boot_patch.sh ../boot.img; mv ../bin/ busybox busybox "
adb pull /data/local/tmp/magisk_inject/new-boot.img
adb shell "cd / data / local / tmp; rm -rf * .img magisk_inject / *. img update-binary bin common"
6. To flash the resulting boot partition image with the name new-boot.img
PHP:
fastboot flash boot new-boot.img
7. Download the system and make sure that Magisk Manager is installed and that its version corresponds to the version of Magisk. If not, manually install the correct version of Magisk Manager.
Click to expand...
Click to collapse
or follow original post
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
Click to expand...
Click to collapse
Bootloader can be unlocked easily of course (code is given immediately) - here
I am tempted but trying to control myself as I don't have a copy of my existing firmware to revert back via dload method if something goes wrong. However, AGS-L09C199B003 firmware is available, so if it fails, I believe you can always go back to stock. I have a feeling this will work.
Took a risk and its rooted now - Magisk v14.0 installed fine and seems to be working (need to test further). Also, Vodafone unlocked the device now for me
Challenge now is to debrand so as to enable functions which has been disabled by Vodafone (namely calling).
Would appreciate if anyone can help - need OEMINFO from another region so as to change the firmware, especially European one or even other UK network who does not disable calling.
Could not contain myself…. In my quest to debrand so I can have a dialer/phone calling function, downloaded a firmware (either from FF Team or on the internet), tried flashing system.img file to see if it installs the dialer as it would not install extracted ones and it did not work. So tested with the boot.img and it did work but phone kept rebooting to eRecovery.
Restoring from TWRP (incomplete/untested) backup did not work. Can’t install any other regional firmware because of OEMINFO. eRecovery can’t find any firmware. The only thing – TWRP/Stock Recovery, eRecovery or bootloader!
Chatted with Huawei support and they won’t give me a link to download the firmware – want me to send for repair, which I don’t really want to – too much hassle and they may end up blaming me anyway….lol He agreed to upload one to their website if he can find one.
I would appreciate if anyone can give me an OEMINFO or link to EUROPEAN firmware with a dialer….. I think European one is AGS-L09C127B031CUSTC127D002 – would appreciate if anyone can share the file with me.
Mercer99 said:
Hi there, about that yes I can make phone calls with it I bought the Model with the 4G option (there is 3 models from the same Huawei tablet one of them is WiFi only and the other two can make phone calls) also I managed to unlocked the bootloader by using the device ID I got earlier and Huawei website.
mine is AGS-L09 model
Click to expand...
Click to collapse
More details and links for the bootloader please, I really need a tutorial-thanks.
dorpmuller said:
More details and links for the bootloader please, I really need a tutorial-thanks.
Click to expand...
Click to collapse
What a buncha bull**** the huawei site is. I got there and when I go to type the product id# in it brings up a calculator dialog with digits I don't even have on the calc.
Done with huawei. All night effing with this is enough. Won't deal with bizarre companies. I'll stick with my samsungs.
I tried... thanks for all of your responses.
Rich
dorpmuller said:
What a buncha bull**** the huawei site is. I got there and when I go to type the product id# in it brings up a calculator dialog with digits I don't even have on the calc.
Done with huawei. All night effing with this is enough. Won't deal with bizarre companies. I'll stick with my samsungs.
I tried... thanks for all of your responses.
Rich
Click to expand...
Click to collapse
I got stuck on the calculator part too. I didn't see the parenthesis buttons. But I turn the tablet on its sit. the view turned horizontal and i was able to see more buttons available. Horrible design for the calculator app.
Hi guys, can someone finally root this Tablet? I would also like to install TWRP to install an AOSP ROM.
Thank you!
Hi.
Did anyone succeed unlock Mediapad T3 7 bootloader ?
I have model BG2-W09 wifi only (European version). I have problem get product id
which is necessary part for bootloader unlock on Huawei site. Stucked to the calculator thing,
when i'll enter ()()1357946()()= on the calculator - i will get ERROR.
Contacted with the Huawei customer service for the help and got not nice answer:
We are unable to send boot loader code via email and can only be obtained through our website.
If you would want to unlock your phone, you should meet the following conditions:
1.Please register your Huawei ID in our official website on your phone.
2.Log in and logout your Huawei ID continuously for 14 days.
3.Each Huawei ID should not apply for the unlock code more than fifth time within 6 months.
Early people informed that email support works fast, but seems now the Huawei tightened terms.
Now i can expect 2 weeks everyday login to meet the requirements.
Some comments about tablet, maybe following helps someone.
One strange thing i've noticed with the tablet, it's not so easy bring up fastboot / recovery menu.
Pressing volume down + power brings up Chinese language test menu (8 options), nowhere to go with that,
pressing volume up + power brings up dialog with 3 options, "Reboot system now" or "Wipe data / factory reset" or "Wipe cache partition". Pressing by same all 3 buttons, volume up + volume down + power brings
up message that update not succeeded, update file not found on sd card. Also if you press only volume down and connect micro usb cable, it brings you to the Chinese test menu again. Also weird why European version tablet has at all Chinese test menu ?
I have triple boot desktop computer and i've downloaded 3 latest adb and fastboot platform-tools packages, for windows (using 10), mac and linux. With windows, using cmd i can start adb session, query device,
seems like everything works, when i'll try:
"adb reboot bootloader", device just reboots back to the main. Tried the same with the Ubuntu, same thing, adb helps finds the device, but when trying: "adb reboot bootloader" device just reboots into normal, not going into fastboot/rescue mode.
The thing is different with the mac (OSX 10.12), when i'll type to the terminal:
"adb reboot bootloader" the device rebooting into the fastboot mode.... and the terminal not responding any further, example when quering: "fastboot devices",
but having already fastboot mode activated on tablet and when rebooting desktop into windows 10 or ubuntu, i'm able using fastboot, tablet responds to the: "fastboot devices" or "fastboot oem get-bootinfo", even "fastboot oem unlock" responds informing about not valid key...
So far i'm able to put tablet into fastboot mode only using mac. Hope that's useful info for someone struggling
with same problems.
Unfortunately bootloader is still locked, problem finding product id, Huawei also did not help.
Huawei product id generator did not recognise Mediapad T3 versions.
Any ideas how to find product id or maybe someone can share the unlock code ?
Thanks in advance.
Related
Latest video: https://youtu.be/o6cpMa2Fo_c
Since 01.16 update Gigaset Me and Me pro use same ROM. So read carefully and take responsibility what you are doing on you device.
Gigaset Pure is not supported here.
GPL Source codes:
Me/MePro/ platform tools full : http://www.gigaset.com/de_de/cms/lp/open-source.html
Me/MePro platform tools uploaded in 1 file (gdrive): https://drive.google.com/uc?id=0B_81lkQEKce4bFlaRXk3dFFwQzA&export=download
Me/MePro kernel source (my repo on github): https://github.com/Eddie07/GIgaset_Me_MePro_3.10._kernel
Terms of Usage:
1. Everything posted on this post should be reposted with links to original post.
2. I'm not responsible for any damage to your phone.
3. If you are aware of bricking device by this or you don't understand some of processes described below - close this thread and leave it alone.
4. If you agree with p.1,2,3 go on to Step2.
GIGASET secret codes:
*#*#4636#*#* - phone info
*#*#2580#*#* -engineer mode (wif, bt tests, usb ports, adb root (pass:gigaset001), ota settings.
*#*#708#*#* - float system info (cpu speeds, m|b temp), shake test.
*#*#801#*#* - wifi test.
*#*#802#*#* - bt test.
*#*#803#*#* - bt test 2.
*#*#2588#*#* - factory hardware tests.
*#*#2581#*#* - Camera callibration??.
(Only ME/MEPRO)TWRP CUSTOM RECOVERY, UNBRICKING:
-FLASH CUSTOM RECOVERY ON ME/MEPRO HERE
-UNBRICK SOLUTION back to rom EU00_V1.1.20160616R ME/MEPRO (if you deleted system, recovery, boot) : BACKUPS--- UNBRICKING
(Only ME/MEPRO)CUSTOM ROMS:
LAST CM 12.1
(Only ME/MEPRO)PATCHES TO STOCK ROM TO BE INSTALLED VIA CUSTOM RECOVERY:
LAST MY "TUNED" TWRP BACKUP https://forum.xda-developers.com/showpost.php?p=71180342&postcount=371
-PATCH#1 TWRP PATCH ME/MEPRO for CPU speeds uncap (1,9ghz), Thermal config fix, Fix of display size MePro HERE
-PATCH#2 Enable 4K video recording in stock camera app HERE
-PATCH#3 Enable Callrecording button in stock dialer app HERE
-PATCH#4 READ DESCRIPTION HERE
-PATCH#5 SystemUI patch HERE
ADB ROOT FOR STOCK ROM WITHOUT ROOT AND CUSTOM RECOVERY:
- Unlocking Me/Pro abd root via factory tool hidden in rom. (usage for Gigaset Me/Pro/Pure)
1) Type in dialer: *#*#2580#*#* to get in Engin. tool
2) Select "priviledge" tab.
3) Type "gigaset001" in pw field.
Get adb root
to check if is done enable USB debugging and try adb command from PC:
"abd shell" if command prompt ends with "#" then adb is rooted, if "$"-isn't!
4) Turn off adb root- type password again.
Thank friend
GaulCrixus said:
Thank friend
Click to expand...
Click to collapse
You are able to install Supersu via abd (you can find manuals on internet).
But if you copy wrong files, or even update binary on purpose in SuperSU gui, you are risking to get bootloop or stuck on ANdroid logo.
There is no way to recover (YET). But im on my way to test something.
So you are warned!
Having Gigaset ME with newest update:
"Engineering tool" could be open with *#*#2580#*#* , but pw is not accepted.
Do you have another Password ?
Moded boot.img for Me/Me pro with enabling of 1,9 ghz cpu speed.
tweaked thermal engine for Me/Me pro .
Seems like me/me pro have same firmware.
modified boot image (ver. EU00_v1.1..20160616R) https://drive.google.com/open?id=0B3Wy4Ok3qGszdXdPSjRvOGVfTlE
thermal engine modded (any version) https://drive.google.com/open?id=0B3Wy4Ok3qGszX2hRQ3ZhazBQQWM this paste to system/etc folder and overwrite.
I emailed Gigaset support and asked about the Marshmallow update and they said its not ready yet but would be at some point, I have read on German forums that no one replies when asked about updates.
Getting CM or PacROM for this would be great.
imkrl said:
Having Gigaset ME with newest update:
"Engineering tool" could be open with *#*#2580#*#* , but pw is not accepted.
Do you have another Password ?
Click to expand...
Click to collapse
I have a Gigaset Me. When I type the password nothing happens on the phone, but a new window opens on my pc.
heineken78 said:
Moded boot.img for Me/Me pro with enabling of 1,9 ghz cpu speed.
tweaked thermal engine for Me/Me pro .
Seems like me/me pro have same firmware.
modified boot image (ver. EU00_v1.1..20160616R) https://drive.google.com/open?id=0B3Wy4Ok3qGszdXdPSjRvOGVfTlE
thermal engine modded (any version) https://drive.google.com/open?id=0B3Wy4Ok3qGszX2hRQ3ZhazBQQWM this paste to system/etc folder and overwrite.
Click to expand...
Click to collapse
I cant expand the images in your post.
typos1 said:
I have a Gigaset Me. When I type the password nothing happens on the phone, but a new window opens on my pc.
Click to expand...
Click to collapse
Right. Its switches off/on root enabler for adb. Check adb shell command on pc if its ended by"$" is non rooted, by "#" you have adb root. (check video)
here is the part of build.prop regarding this eng menu:
# #ifdef GIGASET_EDIT
# /*[email protected], 2015/08/20. added. add root mode for release build */
#ifeq ($(TARGET_BUILD_VARIANT),user)
persist.sys.root.enable=none
# /* [email protected], 2015/10/29. added. add feature to reserve pictures when doing 'Factory data reset'.*/
sys.root.wipedataless=false
#endif
# #endif /*GIGASET_EDIT*/
Click to expand...
Click to collapse
So basically this password changes value of persist.sys.root.enable.
By reading of German forums I figured out that Gigaset Me support ended this summer.
If you succeed with adb rooting, I need you to dump for me boot and recovery partitions, to be sure if they are same for Me Pro.
how to dump in adb shell:dd if=dev/block/platform/f9824900.sdhci/by-name/recovery of=sdcard/recovery_original_me.img
dd if=dev/block/platform/f9824900.sdhci/by-name/boot of=sdcard/boot_original_me.img
dd if=dev/block/platform/f9824900.sdhci/by-name/devinfo of=sdcard/devinfo_default_me.img - to check if your device bootloader is unlocked.
dd if=dev/block/platform/f9824900.sdhci/by-name/system of=sdcard/system_me.img - to backup whole system partition.
system, boot, recovery is all can be changed, needs to return to original factory state as new phone in case of warranty case.
heineken78 said:
Right. Its switches off/on root enabler for adb. Check adb shell command on pc if its ended by"$" is non rooted, by "#" you have adb root. (check video)
here is the part of build.prop regarding this eng menu:
So basically this password changes value of persist.sys.root.enable.
By reading of German forums I figured out that Gigaset Me support ended this summer.
If you succeed with adb rooting, I need you to dump for me boot and recovery partitions, to be sure if they are same for Me Pro.
how to dump in adb shell:dd if=dev/block/platform/f9824900.sdhci/by-name/recovery of=sdcard/recovery_original_me.img
dd if=dev/block/platform/f9824900.sdhci/by-name/boot of=sdcard/boot_original_me.img
dd if=dev/block/platform/f9824900.sdhci/by-name/devinfo of=sdcard/devinfo_default_me.img - to check if your device bootloader is unlocked.
dd if=dev/block/platform/f9824900.sdhci/by-name/system of=sdcard/system_me.img - to backup whole system partition.
system, boot, recovery is all can be changed, needs to return to original factory state as new phone in case of warranty case.
Click to expand...
Click to collapse
Yes, I realise that, I do get a #, I was just pointing out to @imkrl that nothing appears to happen on the phone from looking at the screen, but something does actually happen
After removing from adb and installing SuperSU, SuperSU says its not rooted.
I ll do the dump and upload later.
On the German forums people say that no one from Gigaset replies to messages and that support has been dropped, but that is not official, it is just people's assumptions, when I contacted Gigaset I DID get a reply saying "it will happen automatically", not "we have dropped support", so maybe support has been dropped, maybe not, nothing has been officially said by Gigaset.
But dropped or not getting support for custom ROM like CM of PACrom would be good.
typos1 said:
After removing from adb and installing SuperSU, SuperSU says its not rooted.
Click to expand...
Click to collapse
Right, root is only for adb. But advanced users could push some files in device via adb root# and get supersu working too.
But its quite risky, if you made a mistake, then device can no boot to android anymore (ex. bootloop). Then is bricked.
-You cant access partitions from fastboot - is completely factory locked. (even :"fastboot reboot" doesn't work. fastboot don't listen to any command)
-factory recovery not allows to use adb or view files.
Everything points to have custom recovery.
Another thing if you got su working by pushing files, some system files became modified by supersu and with next OTA update, by security check, OTA will fail to update (patch). So you need system partition backup to restore it on demand.
There is one way to hard unbrick to use "edl" mode (QUALCOMM 9008) (switched phone, hold vol-down, connect usb). I have idea how to but I didn't test, cos I don't want to take a risk to erase memory of my working phone.
To avoid all risks, have to flash custom recovery TWRP from android, within you will be able to restore everything and install supersu normal way. What ever you change from recovery: flashing zip's, installing backups or getting bootloops after, you will be able to load custom recovery again and fix from it. Before installing of custom recovery, backing up of recovery, boot and system partitions should be done, also have to check devinfo partition of your device to be insured that bootloader is unlocked, because if bootloader is locked it will ignore not signed recovery or any boot images.
Yes this is all backdoor and hard to do if you are rokkie in this, but 100% working methode. There is no any Kingaroot or other working roots for Gigaset, cos android security of Gigaset is very high, even with 5.1.1 version.
Why I need your files, typos1: recovery, boot and devinfo. To check them if they are same with Me pro, if not to make another custom recovery for me device.
Sure I will try to make rom ports, may be someone else will do it, cos root is found by me after on second day of device usage, while device was one year on market and lost interest of many. Btw custom recovery source was taken from OnePlus2, hardware +- is similar.
step 2 cannot find devinfo.img
when backup files takes forever
step 4 when installing recovery takes forever and adb not responding
what should i do
xueyaotianxia said:
step 2 cannot find devinfo.img
when backup files takes forever
step 4 when installing recovery takes forever and adb not responding
what should i do
Click to expand...
Click to collapse
Device?
reply
device is Gigaset Me (GS55-6).....I bought it from China, so it doesn't come with google play store. I wanted to root it in order to use play store...any ideas if I can root it? i tried a lot of root software (kingroot, kingoroot, iroot etc..), no luck.
xueyaotianxia said:
device is Gigaset Me (GS55-6).....I bought it from China, so it doesn't come with google play store. I wanted to root it in order to use play store...any ideas if I can root it? i tried a lot of root software (kingroot, kingoroot, iroot etc..), no luck.
Click to expand...
Click to collapse
Mine came from China (they ALL do, thats where theyre made !!) and mine does have the Playstore.
xueyaotianxia said:
device is Gigaset Me (GS55-6).....I bought it from China, so it doesn't come with google play store. I wanted to root it in order to use play store...any ideas if I can root it? i tried a lot of root software (kingroot, kingoroot, iroot etc..), no luck.
Click to expand...
Click to collapse
No way to root yet with common ways. Only via adb shell or via recovery.
But Me and Me Pro have same platform, so take a look what you have at ls dev/block/platform/f9824900.sdhci/by-name/. Use this command in adb shell and write me the list of partitions.
If you get error, Gigaset Me may have different storage name (not f9824900.sdhci as me Pro I own). so try ls dev/block/platform/ and find right name of storage, then ls dev/block/platform/STORAGENAME/by-name/ shows list of partitions.
Guys I need partitions of Me!
After I typed ls dev/block/platform, it shows this:
f9824900.sdhci
f98a4900.sdhci
what should I do now?
Thank you..
---------- Post added at 09:25 PM ---------- Previous post was at 09:22 PM ----------
I would guess your device is made for oversea's market...so that is why it has playstore pre installed...I bought mine in China (which made for Chinese market, by law no google)...it makes life so much more difficult, as I have to install 3rd party app store...cannot root the phone now so whenever I open play store it shuts down immediately.
---------- Post added at 09:39 PM ---------- Previous post was at 09:25 PM ----------
After I typed this ls dev/block/platform/f9824900.sdhci/by-name, it shows:
DDR
aboot
abootbak
apdp
bluetooth
boot
cache
config
devinfo
dpo
fsc
fsg
hyp
hypbak
keystore
limits
misc
modem
modemst1
modemst2
msadp
persist
pmic
pmicbak
recovery
rpm
rpmbak
sbl1
sbl1bak
sdi
sec
splash
ssd
system
tz
tzbak
userdata
that is all.
I went back tried step 2 again, it shows 01. But when I tried step 4 to do the recovery it says:
aset-me.img of=dev/block/platform/f9824900.sdhci/by-name/recovery <
0 records in
0 records out
24 bytes transferred in 2.347 secs <10504398 bytes/sec>
recovery seems still the old factory one.
---------- Post added at 09:51 PM ---------- Previous post was at 09:39 PM ----------
Hahaha I tried step 4 again it worked!! Now I am in Team win recovery project v2.8.7.0
What should I do now to root the phone??
Thank you very very much you saved the day!!!
xueyaotianxia said:
Thank you very very much you saved the day!!!
Click to expand...
Click to collapse
Download and install supersu.zip
Notice, you have to disable engineering menu root (type password again), because factory adb root and another (supersu) will have conflicts.
So confirmed that this recovery works on Gigaset Me too!
thank you
thank you thank you thank you...i have disabled the engineering mode. awesome man!
I installed gapps zip from recovery instead of rooting, play store works 100%. but it seems some other old system apps stopped working, all became that android robot icon like camera and sms etc, I download google cameras and google message etc as alternatives, they work fine.
just would like to ask, if i wipe the data and cache from recovery, will all the older system apps work again? and is it possible to install a custom rom? any ideas??
xueyaotianxia said:
thank you thank you thank you...i have disabled the engineering mode. awesome man!
I installed gapps zip from recovery instead of rooting, play store works 100%. but it seems some other old system apps stopped working, all became that android robot icon like camera and sms etc, I download google cameras and google message etc as alternatives, they work fine.
just would like to ask, if i wipe the data and cache from recovery, will all the older system apps work again? and is it possible to install a custom rom? any ideas??
Click to expand...
Click to collapse
You have messed up. Suggest to restore system.img or if you done system backup in twrp and try root again.
Have I messed up...
I did backup the systembackup.img
when I am in the recovery to flash it, it let me choose either boot or recovery, which one should I choose?
is it possible to find an EU gigaset me Rom? or to install other roms?
xueyaotianxia said:
Have I messed up...
I did backup the systembackup.img
when I am in the recovery to flash it, it let me choose either boot or recovery, which one should I choose?
is it possible to find an EU gigaset me Rom? or to install other roms?
Click to expand...
Click to collapse
You should do backwards procedure to restore system image. Better if you do it while in TWRP recovery.
1) Open TWRP recovery and connect to PC
2) In adb shell on pc: dd if=sdcard/systembackup.img dd of=dev/block/platform/f9824900.sdhci/by-name/system
Where systembackup.img name of backup image you done stored on internal memory. This will overwrite system partition to previous state.
For next time I suggest you to make backup in TWRP normal way. It will be faster.
I'd like to create a new thread on installing TWRP and rooting Android Nougat (7.x) on version B360 of the Honor 8. All the threads I see are people frantically trying to restore their phone to their previous glory. To keep people from asking "will this work on yada yada model, *I* have a FRD-L04 which is the 32gb unlocked SINGLE SIM variant sold locally at Best Buy here in the states and I'm pretty sure the FRD-L09 is the international DUAL SIM version with 64GB and I believe firmware for both of these are different? If not, please correct me. The process should be the same for all variants, but the files used will be different.
I want to update this OP and keep it as up to date as possible. If we can get 3 or more people to confirm a certain process works in this thread, I will update it with the proper links to all tools/files/versions of TWRP and SuperSU as well as firmware that's needed. I think I currently count eleven different threads all over the place on this and would be nice to have it centralized. Let's help out and get this phone going with a working root on Nougat!!!
Here are the questions I propose:
1. What is the actual steps to root the Honor 8 running a FULL STOCK version of B360 (Android 7.x)?
A. Unlock Bootloader (This process should be the same as always)
B. Flash TWRP (Which version?) This should be a simple flash with fastboot
C. Flash SuperSU (Which version?) This should be a simple flash with TWRP
D. What are the current issues with this process? (encryption issues, formatting, unable to access the Data partition, etc)
E. How to revert back (and when I say back, I mean ANY working state of Nougat (Android 6.x) or Marshmallow(Android 7.x))
F. How to install extras (Xposed for example, etc)
If I can have answered the questions above, I will clean it up and move it over to the guide section. As it stands now we have no guide. We just need clarification on what works, what doesn't and the process.
Also, PLEASE be kind to those who don't speak English as their primary language. The Honor 8 is an international phone and I see many people getting angry because they don't understand or don't follow instructions correctly because the OP didn't clearly state what they did. Let's help each other out!
Here's an example step by step for unlocking the bootloader below. This is what I'd like to do for each of the questions above.
A: Unlocking the bootloader (UNDERSTAND THAT BY UNLOCKING THE BOOTLOADER ALL YOUR DATA ON THE PHONE WILL BE ERASED AS IF YOU'RE PULLING IT OUT OF THE BOX FOR THE FIRST TIME)
1. Go to Huawei's EMUI site and log in. If you need to create a new account, do so. Link here: http://www.emui.com/en/plugin/hwdownload/download
2. Click on the DOWNLOAD link at the top of the site.
3. Underneath the search field you will see a green link that says "Unlock Bootloader". Click it and follow the instructions. You will be asked to enter in several pieces of information about your phone.
4. Once you've filled out all the information, you will receive your unlock code at the bottom of the screen. Write this down and save it. This number will NEVER change.
5. On your Honor 8, go to Settings > About and tap on the Build Number seven times until you unlock the Developer Settings.
6. In Developer Settings, check Enable OEM Unlock.
7. Scroll down a bit more and check USB Debugging.
8. Go to Huawei's site and download their HiSuite and install it. This installs the OFFICIAL Honor 8 USB driver. Link here: http://consumer.huawei.com/minisite/HiSuite_en/index.html Once the app is installed, you can unselect start with Windows under settings.
9. Plug in your Honor 8 with the provided USB cable. Give it about 45 seconds to install the driver and recognize it. You may need to go to your phone and tap on "Allow File Access". You will be presented with a question asking if you'd always like to trust the computer you just connected to. Select yes, if this is your primary computer you will be working with.
10. Now download the most up to date ADB drivers. A Google employee has created one link to get that and make it easy. Link here: https://developer.android.com/studio/releases/platform-tools.html
11. Open the zip file you just downloaded and create a folder on your computer easy to get to (I recommend c:\ADB) and paste those files there so they are extracted.
12. Now open the folder up in Windows Explorer if you closed it and hold down the Shift key and RIGHT click in the open area and click "Open command window here"
13. Type adb devices and hit enter. You should see a device ID as a response in the window.
14. Type adb reboot bootloader and hit enter. Give it a couple of seconds and the phone will load the bootloader.
15. Now type fastboot devices and hit enter. You should see your device ID appear again.
16. LAST CHANCE before it wipes everything and unlocks the booloader!!! Type fastboot oem unlock XXXXXXXXXX (where XXXXXXXXXX is the unlock code you received on step 4) and hit enter. It will ask if you're sure. Once this is done, the phone will wipe your data, unlock the phone and reboot. Your Honor 8's bootloader is now unlocked.
B. Flash TWRP (Which version?) This should be a simple flash with fastboot. This is already discussed in another post, but I will put here for reference.
1. Grab a working copy of TWRP for the Honor 8 here: https://forum.xda-developers.com/showpost.php?p=70893767&postcount=408
2. Download TWRP into the same folder you used in step A above (where you're keeping all your files)
2. Navigate in Windows Explorer to this location and hold down the Shift key and RIGHT click in the open area and click "Open command window here"
3. Type adb devices and hit enter. You should see a device ID as a response in the window.
4. Type adb reboot bootloader and hit enter. Give it a couple of seconds and the phone will load the bootloader.
5. Now type fastboot devices and hit enter. You should see your device ID appear again.
6. Type fastboot flash recovery frd-twrp.img and hit enter.
7. Once this is complete, unplug your phone.
8. Hold Volume UP and Power at the same time. Release ONLY the Power button after the blue Honor logo appears.
9. You now are booted into TWRP and it's been successfully flashed.
C. Flash SuperSU (Which version?) This should be a simple flash with TWRP. This is a crazy process because of the encryption on the Data partition. Below is the exact steps I can confirm works from the help of others on here.
1. Boot into TWRP
2. Once there, when asked to keep system read only? - swipe to allow modifications
3. Tap Install
4. Tap Select Storage - Select your SD card
5. Select the supersu file "SuperSU-v2.79-201612051815-EMUI5.0.zip"
6. Swipe to confirm flash
7. Ignore the multiple errors: "Failed to mount '/data' (Invalid argument)
8. Go back to the main menu
9. Select Reboot to Recovery
10. When asked to keep system read only? - swiped to allow modifications (again)
11. Tap Wipe
12. Tap Format Data
13. Type YES then hit enter
14. It will format data using make_ext4fs..
15. When finished, tap Reboot System
16. Reboot back into TWRP
17. Swipe to allow modifications (You can check the box to never show this again)
18. Tap Install
19. Select storage
20. Select your SD card
21. Select the supersu file "SuperSU-v2.79-201612051815-EMUI5.0.zip"
22. Swipe to confirm flash
23. You should see NO ERRORS now when installing SuperSU
24. Wipe cache/dalvik
25. Swipe to wipe
26. Reboot system
Once here, you can download root checker and it will verify you have root access - BUT.. see section D below!
D. What are the current issues with this process? (encryption issues, formatting, unable to access the Data partition, etc)
Some applications like Root Checker will verify that you have root. Other applications will even prompt you (like any of the basic quick reboot apps that easily let you back into recovery) but other major apps like BusyBox and Viper4Audio (when asking to load the driver) will simply fail upon installation. I'm not sure why, since you have R/W access to both the system and the newly unencrypted data partition. I'm really hoping someone can help with this one!
E. How to revert back (and when I say back, I mean ANY working state of Nougat (Android 6.x) or Marshmallow(Android 7.x))
F. How to install extras (Xposed for example, etc)
I know and have done A, B, and C, but as for the rest I'm not too sure about those.
Maybe in the wrong section but thank you.
joesee said:
14. It will format data using make_ext4fs..
Click to expand...
Click to collapse
The Honor 8 defaults file system for /data is F2FS. Do you see any performance changes going back to EXT4? Is it possible to keep F2FS?
joesee said:
15. When finished, tap Reboot System
Click to expand...
Click to collapse
When I wipe then reboot I get stuck in the bootup screen
EDIT； Nevermind I just didn't wait long enough for my phone to boot up
KevinN206 said:
The Honor 8 defaults file system for /data is F2FS. Do you see any performance changes going back to EXT4? Is it possible to keep F2FS?
Click to expand...
Click to collapse
Yes, but twrp read it as ext file, i tested both format f2fs and ext4, i dont feel any different between those 2.
Yes, you can changed the data format to f2fs with twrp but if you reverted back to MM, its requred to changed the data to ext4 format, if not, you'll get bootloop. (dont know if its twrp bugs or not)
Worst scenario, you'll lost all stock recoveries and everything.
I've been there... Lol
faizalotai said:
Yes, but twrp read it as ext file, i tested both format f2fs and ext4, i dont feel any different between those 2.
Yes, you can changed the data format to f2fs with twrp but if you reverted back to MM, its requred to changed the data to ext4 format, if not, you'll get bootloop. (dont know if its twrp bugs or not)
Worst scenario, you'll lost all stock recoveries and everything.
I've been there... Lol
Click to expand...
Click to collapse
Are you saying I can format /data with F2FS to remove the encryption? I am assuming TWRP does not support the encryption yet. Bootlop sux but most important stuffs on my phone is stored on the SD card anyway so it's not too bad to start over.
Maybe it's just me but it seems encryption adds a bit of risks when playing around with rooting. Has there been a scenario where you *can't* recover from bootloop permanently?
KevinN206 said:
Are you saying I can format /data with F2FS to remove the encryption? I am assuming TWRP does not support the encryption yet. Bootlop sux but most important stuffs on my phone is stored on the SD card anyway so it's not too bad to start over.
Maybe it's just me but it seems encryption adds a bit of risks when playing around with rooting. Has there been a scenario where you *can't* recover from bootloop permanently?
Click to expand...
Click to collapse
So far, i've experienced with bootloop and no recoveries available,
As long as you have fastboot mode and bootloader key, you're safe.
faizalotai said:
So far, i've experienced with bootloop and no recoveries available,
As long as you have fastboot mode and bootloader key, you're safe.
Click to expand...
Click to collapse
I am afraid of running into this issue from a fellow xda. The person still doesn't have a solution. https://forum.xda-developers.com/mate-8/help/encrypted-data-mount-t3537645
I'm running into issues with Bluetooth activation, and previously NFC, which i fixed by reflashing the hw_update package, but still no Bluetooth.
I've followed each and every single step on this guide, and BT was working perfectly before.
Any ideas where this may be coming from ?
Still, thanks or the guide
For the SuperSU instructions, you don't have to reformat /data. Yes, TWRP won't be able to access it, but you really only need that for making full system backups. You can access everything in /system/ and then ADB push to /data/ after boot, or fastboot flash an image to /data/ from bootloader. It's not ideal, but it saves you from having to wipe out your configuration.
I'll echo the above poster, as long as you're bootloader unlocked and can issue fastboot commands I'm not sure you're truly bricked. Worst case scenario you ought to be able to flash individual partition images to recover, I unpacked the Nougat update zip to extract the partition images and I've been using those when my tinkering results in a bootloop -- corrupted boot and corrupted recovery I fixed easily.
Hello. Im coming from general topic on Honor 8 rooting but my issue is related to Android MM.
So i had stock EMUI 4.1 (Android 6.0) which i unlocked, flashed TWRP and SuperSU.
Today EMUI 5 (Android 7 ) update came by air so i installed it. After update - no TWPR neither SuperSU.
I enabled Developer options and saw "Enable OEM unlock" switch in OFF state and grayed out (impossible to switch ON).
So now i cannot flash TWPR as fastboot gives error "Command not allowed".
During boot phone says that it is unlocked, FRP lock. Otherwise it boots and works fine but no root.
Any solution possible?
Thank you.
Telperion said:
For the SuperSU instructions, you don't have to reformat /data. Yes, TWRP won't be able to access it, but you really only need that for making full system backups. You can access everything in /system/ and then ADB push to /data/ after boot, or fastboot flash an image to /data/ from bootloader. It's not ideal, but it saves you from having to wipe out your configuration.
I'll echo the above poster, as long as you're bootloader unlocked and can issue fastboot commands I'm not sure you're truly bricked. Worst case scenario you ought to be able to flash individual partition images to recover, I unpacked the Nougat update zip to extract the partition images and I've been using those when my tinkering results in a bootloop -- corrupted boot and corrupted recovery I fixed easily.
Click to expand...
Click to collapse
can u please tell more or make a step by step tutorial on rooting? I'm stuck in rooting, when I format data and boot agai into recovery and flash su It still ends with error 1, dnt know which error it is..
I have FRD-L09 C432B360 Honor 8 (Sweden) with EMUI 5.0, i have TWRP 3.1.0.0, unlocked bootloader
I could not root my phone since it uppdated to nougat (EMUI 5.0)
I tried everything what i could find on the net, but nothing worked yet, any suggestions ?
thanks
Is there any way to do this without rooting?
I recently got my phone and I didn't get the update. I am still running on EMUI 4.1
ajmdrh said:
I have FRD-L09 C432B360 Honor 8 (Sweden) with EMUI 5.0, i have TWRP 3.1.0.0, unlocked bootloader
I could not root my phone since it uppdated to nougat (EMUI 5.0)
I tried everything what i could find on the net, but nothing worked yet, any suggestions ?
thanks
Click to expand...
Click to collapse
Update to latest TWRP and try again
Shehzaan said:
I recently got my phone and I didn't get the update. I am still running on EMUI 4.1
Click to expand...
Click to collapse
Indian version?? Frd-l02?
venugopalu007 said:
Indian version?? Frd-l02?
Click to expand...
Click to collapse
Nope, it is FRD-L09C636B130. I think this is the Middle East version.
Shehzaan said:
Nope, it is FRD-L09C636B130. I think this is the Middle East version.
Click to expand...
Click to collapse
Yes, it is middle east variant
PalakMi said:
Yes, it is middle east variant
Click to expand...
Click to collapse
Do you have any idea how can I get EMUI 5.0 without rooting?
Welcome to this little thread in which I'll provide every useful information about this device based on my and other users's experiences. If you know something, that I didn't mention, please reply to this thread in order to help out each other even more effectively. Thanks and pleasant reading!
The Lenovo S5 Pro is a very decent mid-ranger with good specs and even better pricing. We all know, that chinese manufacturers tend to install bloatware on their products time to time. In our case, Lenovo didn't release a single update since 2018 Novemer to this device. It means, that it came out with Android 8.1 Oreo (2018 November Security Patch) and left untouched. This is even worse, than Meizu which is famous for it's neglecting policy of software updates for global users. Now, that we know all this, it's not a surprise, that we are here on our favourite developer forum.
*** General information | Links | Downloads | Credits ***
The official global firmware is now saved and available (thanks to our forum member nikosddesign) here: download & link to the post
Everything you will possibly need (PC software, drivers, stock camera app, VoLTE modem etc...) is available in this Yandex Disk, you just have to navigate to each one. (Most of the content is in russian, since Yandex is the russian Google, but it's not hard to find the files you'll need).
The previous links and the following tutorials are only available, because suninterbru (from 4pda forums) and radiationofthenation provided these informations and the tutorials, also so much thanks to everybody on the 4pda forums, who provided useful information and files, большое спасибо!
Even though the bootloader unlock, TWRP install and rooting should not cause data loss, be careful and create a backup. You can back up only your files and data or your whole ROM, it's up to you.
Please note, that after you've unlocked your bootloader, everytime your reboot or turn on your phone a warning will pop up during the boot process for about 1 second. On Android 9.0 Pie vendor the message pops up for about 5 seconds. The warning is about the side effects of modifying the system software and it also says, that it is not recommended to store any personal data on your device anymore. Please ignore this message, since it's only popping up, because manufacturers usually don't like, if you modify your device.
Pro tip: If you keep pressing your power button for a little longer you can skip the alert and boot faster.
*** Bootloader unlock ***
Please note, that your warranty will become invalid/void after you unlock your bootloader or root your device.
0. In your device's developer settings enable bootloader/OEM unlock and USB debugging.
1. Visit the official ZUI bootloader unlock website.
2. Enter your IMEI1 number in the first field. (You can find your IMEI numbers in Settings\About or in the dialer enter: *#06#).
3. Enter your serial number in the second field. (You can find your serial number in the fastboot menu). The one in the settings is not good in this case! (To access the fastboot menu, turn off your phone, then press the power button and after you see your screen light up, immediately press the volume down (-) button or while it's turned on and USB Debugging is enabled, simply type in the terminal/cmd ,,adb reboot bootloader").
4. In the next field enter your email adress. (Please note, that Tutanota won't work, Gmail is recommended or other not secure email providers).
5. Enter the verification numbers in the last field.
6. Tick the checkbox.
8. Click on the blue button.
7. Now check your inbox and/or spam folder, because Lenovo just sent you your custom sn.img, only for your phone.
8. Save the sn.img to your PC and install ADB drivers system-wide. (Thank you Snoop05 for your work)!
9. Open a terminal/cmd on Windows. You should be in the same directory, where your sn.img file is, with the terminal. To change directories type ,,cd your directory goes here" and hit ENTER.
10. Run the following commands:
- adb reboot bootloader
- fastboot flash unlock sn.img
- fastboot oem unlock-go
11. Congratulations! Your bootloader is now unlocked!
*** TWRP Recovery ***1. Download the .img file from here.
2. The steps are similar to the bootloader unlocking:
- adb reboot bootloader
- fastboot flash ,,downloaded" .img
- After the flashing is done DON'T reboot to the system, instead navigate to the ,,Reboot Recovery or Recovery Reboot" option and select it. (Volume keys and power key - you know the drill) This will ensure, that the TWRP Recovery doesn't get ereased on reboot(s)!
3. After you've successfully rebooted into TWRP, you should root your device with Magisk, to prevent the recovery erasure!
*** ROOT ***1. The good old SuperSU is no longer in the picture, but don't worry a new player is in the game. Download Magisk from here. (Thank your for your work topjohnwu)!
2. After you've downloaded the flashable .zip copy it to the main directory/root of your device.
3. Reboot to TWRP.
4. Click install, select the flashable .zip file.
5. The installation process should start.
6. Reboot, after finished.
7. Check if Magisk Manager is installed or not, if yes tap and update it.
8. If you did not succeed, please check the Magisk topic for solutions or reply to this thread.
*** Factory reset | Stock ROM | Unbrick | LOST IMEI/PERSIST/EFS | QCN BACKUP/RESTORE ***
!!! NEVER EVER TICK ,,ERASE ALL BEFORE DOWNLOAD" IN QFIL, OTHERWISE YOU WILL LOSE YOUR IMEI AND THE ABILITY TO CONNECT TO MOBILE NETWORKS !!!
If you accidentally clicked on that option you will have to restore someone elses QCN backup. (It will not work, if you backup your own QCN and rewrite your IMEI and restore it, so do not waste your time with that)! Luckily, a member of the 4PDA forums published their qcn backup. (большое спасибо geepnozeex)! QCN backup for Lenovo S5 Pro. (I modified the link, because the original one is no longer valid)
1. Download the linked QCN file.
2. Make sure, that you are on one of the Stock ROMs, however the recommended ROM is this one.
3. You will have to be rooted to put your device in diagnostics mode. To do that, follow this tutorial.
4. You will have to edit the QCN file with HxD, in order to write your own IMEI into.
5. Open the file with HxD and search for 08 8A 76 06 06 14 57 95 32. This is the IMEI 2. You will have to insert your IMEI 2 from the box here, but first you will have to convert it into Hexadecimal numbers.
6. Convert your IMEIs into Hexadecimal numbers here.
7. You will have to rewrite and insert your values insted of the previous one.
8. Search for 08 8A 76 06 06 04 67 98 72. This is IMEI 1. Convert your IMEI 1 into Hexadecimal numbers, too and replace.
9. Save the file (Ctrl + s)
10. Open QFIL and click on Tools, then QCN Backup/Restore.
11. Choose the QCN file, you wrote your IMEI into.
12. Click on Restore QCN.
13. There is a chance, that the process/progress bar won't finish till the end. No problem, just reboot to EDL mode through TWRP/Advanced and restore the recommended stock ROM.
14. You should have everything working fine, now.
To factory reset or unbrick your device, follow this tutorial on 4PDA. [Don't panic you don't have to know russian, just follow the instructions on the pictures! To see the pictures, click on the bold text.] ,,(спойлер (+) (Инструкция по прошивке)" ~ or ~ Download any of the previously linked STOCK ROMs to your device's main folder and flash them through TWRP. Most of them are in flashable .zip formats and should work well. A simple factory reset in TWRP is recommended before installing any of the ROMs, be careful this action will erease your data from your phone!
(Please note, that most of the time you'll have to use the QPST/QFIL method, because the flashable .zip files always expect a specific vendor version, usually a lower one, so you can upgrade with flashable .zips, but possibly can't downgrade, so you have to use QFIL)!
*** GSI custom ROMs ***
Our device is arm64-aonly, so please only use according GSIs. Note, that I will link only those GSIs, which are booted successfully on my device!
~ phhusson's official GSI list: here
~ phhusson's AOSP GSI (Android Open Source Project): here
~ developerluke's ExpressLuke GSIs: here
~ eremitein's CAOS GSI Project: here
~ eremiten's LOSQ GSI Project: here
~ igors1974's Amber GSIs: here
~ tunasahinn's and yek4perf's Tunahan's GSI builds: here
~ mrsshunt3r's albus-gsi: here
Note, that you should keep up with the developments and update your system, if needed! These are just a few GSIs, that I've tested personally on my phone, but you can always keep up with the latest news and try new GSIs out, thanks to phhusson's official GSI list!
*** How to flash an Android 10 GSI ***
1. Download the latest custom phh-magisk from here. (Thank you developerluke and phhusson)!
2. Download the latest Disable_Dm-Verity_ForceEncrypt from here. (Thank you Zackptg5 and others)!
3. Download your desired GSI.
4. You can flash from an USB-OTG flash drive or from the storage of your phone. (I personally have a dedicated USB for this purpose).
4.1 If you are coming from stock ROM you will most likely need to Format Data in this step, because the Disabler won't be able to decrypt the data and, that will cause a stuck at the boot logo!
4.2 Reboot Recovery
5. In TWRP perform a normal factory reset
6. Flash Disable_Dm-Verity_ForceEncrypt. (Cache wipe is optional).
7. Flash your GSI image.
8. Format Data (Skip this step if you already did this in 4.1)!
9. Reboot Recovery (Skip this step, too if you already did this in 4.2)!
10. Flash Magisk-phh
(11. Wipe cache/dalvik).
12. Reboot System
13. Enjoy!
*** Possible GSI bugs ***
Please note, that bugs can differ/vary on different GSIs, the numbers are not fully accurate!
1. The default camera app will work, however it doesn't support HDR, panorama or portrait modes. It also can't record in 4K resolution. Freezing is also possible. ~ 50%
2. First time, when you open the camera it'll stuck on loading, but after you go back and open it again it will work flawlessly. ~ 50%
3. No audio/microphone during phone calls. ~ 15%
*** Guaranteed GSI bugs*** 1. The infrared face unlocking will not work, only fingerprint authentication is working. ~ 100%
2. You won't be able to charge your device while it's turned off, after you plug it in, it will automatically boot up. ~ 100%
3. Auto brightness. ~ 100% (There is a fix for auto brightness below)!
*** Camera fix (GSI) ***
(If you get ,,serious camera error" or your camera freezes on HDR)
1. Download a custom camera app, where you can manually adjust the ISO level.
2. With OpenCamera, for example you have to adjust ISO to 800 and never above, because your camera will freeze!
3. So, always keep ISO 800 or under. With these settings even HDR shots are working!
*** Auto brightness (GSI) ***1. Download framework-res__auto_generated_rro.apk from this thread.
2. Follow the instructions, which are described in this post. (You will need to have root to use ,,su" commands).
3. Thank you MishaalRahman and kAs1m for the apk and the instructions!
Twrp disappears when restarting
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.
kcire_eae said:
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.
Click to expand...
Click to collapse
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
It didn't work, given: "fastboot: usage: unknown reboot target recovery" Sorry for the long time to answer, I only have mobile data, and from this same mobile I answer, and I use google translator, I'm from Mexico.
Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
Foto
kcire_eae said:
Foto
Click to expand...
Click to collapse
Well, it looks good. Maybe only " reboot recovery " is enough.
Halwer said:
Well, it looks good. Maybe only " reboot recovery " is enough.
Click to expand...
Click to collapse
It didn't work, friend, but I appreciate the help.
kcire_eae said:
It didn't work, friend, but I appreciate the help.
Click to expand...
Click to collapse
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?
Halwer said:
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?
Click to expand...
Click to collapse
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.
kcire_eae said:
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.
Click to expand...
Click to collapse
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.
Halwer said:
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.
Click to expand...
Click to collapse
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:
kcire_eae said:
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:
Click to expand...
Click to collapse
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.
Halwer said:
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.
Click to expand...
Click to collapse
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.
kcire_eae said:
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.
Click to expand...
Click to collapse
You should do the oreo version, if your were on the global oreo ROM. After that you can try the pie version, if nothing works don't worry you can do a backup of your data from twrp to your computer and flash a custom ROM or the chinese Pie version, which is recommended. With root access you can easily debloat the chinese ROM and with AdAway you can disable all communications pointing to chinese servers or websites. I also found these. Maybe you can give them a try.
After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" .
prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata".
rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"
kcire_eae said:
After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata" rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"
Click to expand...
Click to collapse
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.
Halwer said:
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.
Click to expand...
Click to collapse
Ohh, explain more about spying. And also if you know something about the message that Android told me when I start. I remember that I flashed twrp.img using "fastboot", and when I asked for a password to decrypt, it only allowed me to clear cache and dalvit cache (I did wipe), and when I started again I showed a message saying that I was encrypting and a percentage, just here, I interrupted the process by turning off the cell phone, and flashed again with qfil (download). So when I start I just remember that I said something about the cell phone being restored and then I could restore the copy with my Google account. So what I think is that when the message of "TO START ANDROID ENTER YOUR PASSWORD" is displayed, it may work to interrupt or perhaps to put the incorrect password many times to automatically reset or also choose "rawprogram0.xml" in qfil (but I did not dare because it deletes it the information related to the imeil and the signal or at least that says some comments ). Now there is only one who can interpret what happened and to have clearer the restoration process, the rom seems to me very much the problem of the language is solved with "more local", I am from Mexico (At & t).
good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g
nikosddesign said:
good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g
Click to expand...
Click to collapse
Thank you, I'm sure some people will find it very useful!
Hello
it's about 4gigabyte have to be patient.
i have very bad internet connection...
Hi everyone,
I have rooted my last few smartphones and was always happy with it. Now I got new Blackview BV9800 PRO and I want to root it with Magisk. but as the phone is new, there is lack of information on the internet, Anyway, I have found some information, but it is not complete and I believe You, smart guys, can help me to root my smartphone
This is the information I got:
How to root it with Magisk :
Download your rom from : viewtopic.php?f=285&t=532354 (you can alternatively extract it with SP Flash Tool and WWR)
Download and install Magisk Manager on your phone : https://github.com/topjohnwu/Magisk/rel ... v7.5.0.apk
Patch the boot image with Magisk Manager
Unlock the bootloader. (Wipe the phone! )
Flash the patched boot image with SP Flash Tool or Fastboot. (ONLY the boot image)
Reinstall Magisk Manager
This is what I did and what happened:
I installed latest Magisk apk from official sources. I opened the app, clicked on "Install Magisk", then via this app I downloaded the zip file, then tried to installed it via Magisk but got an error "Unsupported/Unknown image format".
Any ideas what have I done wrong? Did I have to flash boot image from the ROM, and not the one Magisk downloaded? P.S., the smartphone is new, nothing more then I written above is done to it (no oem unlocking, no usb debugging, etc).
RESERVED
I let Magisk manager patch the original boot.img. After flashing it with fastboot or SP Flash the phone stuck with message that verified boot didn't accept the signature.
Hm... Is there anyone who rooted BV9800 Pro successfuly and could guide us? ?
update fail.
I greet you, I accidentally deleted it when I updated, Nvram. on my phone. BV9800pro. It is possible to provide me with firmware recovered from a similar phone. I also posted on the forum at Blackview but without answer
Isn't there a full firmware download on Blackview website available? I thought I've seen it there
update fail
LGZACRO said:
Isn't there a full firmware download on Blackview website available? I thought I've seen it there
Click to expand...
Click to collapse
Hello
Yesterday during an update, by accident, my equipment, BV9800pro, performed a complete formatting, "Full Format + Dowload", it seems that Nvram has also been rewritten. it is possible to provide us with a solution or file with this data, specific to our equipment. i need a original nvram.bin, and nvram.data, in firmware from Blackview site this its not exist..
if someone wants to help me, I send them a private message with their email address
My phone is not rooted unfortunatelly, if I can help in anyway (if there is a way) I would pull out the files for You.
Do You know how to guaranteed root BV9800 Pro without running into problems?
LGZACRO said:
My phone is not rooted unfortunatelly, if I can help in anyway (if there is a way) I would pull out the files for You.
Do You know how to guaranteed root BV9800 Pro without running into problems?
Click to expand...
Click to collapse
who guarantees this?
rooting worked for me with that solution given to the PM. I wanted to install AOSP, but I found that the thermal image did not work anymore, there were some problems when previewing the video files from Facebook, and I gave up. from the mistake as I mentioned I format + dowload and delete all important partitions. nvram .bin si nvdata. Nothing works properly, TEE and Google Key are inactive, the thermal image fails, some applications are closed immediately. This is the experience with rooting and installing AOSP on the BV9800Pro
Oh man... Sounds bad... have You emailed blackview after sale support (via email, not forum)? No response from them?
And let's say I only root my BV9800Pro, will I be able to send You the files You need?
LGZACRO said:
Oh man... Sounds bad... have You emailed blackview after sale support (via email, not forum)? No response from them?
And let's say I only root my BV9800Pro, will I be able to send You the files You need?
Click to expand...
Click to collapse
make total firmware dump and send the bakup , or nvram.bin nvdata.bin file,
I must root to be able ro do this, right? Does TWRP works well on BV9800Pro?
LGZACRO said:
I must root to be able ro do this, right? Does TWRP works well on BV9800Pro?
Click to expand...
Click to collapse
i dont now. i dont install twrp.
Ok, pm me your skype or signal or wickr or fb. We will try to do this in few hours
LGZACRO said:
Oh man... Sounds bad... have You emailed blackview after sale support (via email, not forum)? No response from them?
And let's say I only root my BV9800Pro, will I be able to send You the files You need?
Click to expand...
Click to collapse
I posted in their forum a detailed error report but the moderator deleted my post.
Don't bargain for help by them.
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
LGZACRO said:
I must root to be able ro do this, right? Does TWRP works well on BV9800Pro?
Click to expand...
Click to collapse
As I mention there's no TWRP available for this phone yet.
I just rooted BV9800 pro yesterday.
You don't need to SP flash tool or others, just need adb and fastboot.
Quick steps:
1. set OEM unlock to allow
2. connect phone to windows
3. use adb to check if connecting. command: adb devices
4. using adb to reboot to bootloader, command: adb reboot bootloader
5. And then the phone will enter fastboot mode ( you could see small string at left bottom corner)
6. use fastboot command to unlock bootloader. command: fastboot flashing unlock
7. If fastboot program is waiting, please check windows device manager, there should be an unknown device, let windows search driver automatically. it needs android interface driver.
8.Using volume up or down to agree unlock.
9. If agree, all data will be disappeared.
10. Install Magisk manger
11. Download stock ROM from blackview forum. it is zip file. Unzip it and copy boot-verified.img to phone.
12. patch boot.img by Magisk manger.
13. Copy patch image file to windows
14. use adb to reboot phone to fastboot mode
15. reflash boot image file. command: fastboot flash boot patched file name (normally, I would put patch image file in the same folder of fastboot)
16. reboot (fastboot reboot) and reinstall Magisk manager
There are many Magisk root steps instruction in internet. You could refer to other steps, they should be clear than mine. I prepared lots of drivers and application. Finally, I only used adb and fastboot to root this phone.
I rooted it exactly like You and it worked perfectly! Thanks for auch detailed rooting guide!
By the way guys, I think we Should open the request for TWRP for BV9800Pro. How do You think?
After you unlocked bootloader, it changed to orange state, and it always shows "Your device has been unlocked and can't be trusted..Your device will boot in 5 seconds", it could be resolved by modified LK image.
Refer to
1. https://forum.hovatek.com/thread-31664.html
2. http://bbs.blackview.hk/viewtopic.php?f=286&t=532899 -- included modified LK image
Of course, you could reflash by fastboot, no need to use SP flash tool.
hi if u have back up on your phone could u provide for me link. I had some problems with my loudspeaker and i thought its from the root, or software and i did full format and download. and now it show some watermark and probably is because i l deleted NVRAM.
i download already official version but didn't help ... thank u upfront.
james35888 said:
I just rooted BV9800 pro yesterday.
You don't need to SP flash tool or others, just need adb and fastboot.
Quick steps:
1. set OEM unlock to allow
2. connect phone to windows
3. use adb to check if connecting. command: adb devices
4. using adb to reboot to bootloader, command: adb reboot bootloader
5. And then the phone will enter fastboot mode ( you could see small string at left bottom corner)
6. use fastboot command to unlock bootloader. command: fastboot flashing unlock
7. If fastboot program is waiting, please check windows device manager, there should be an unknown device, let windows search driver automatically. it needs android interface driver.
8.Using volume up or down to agree unlock.
9. If agree, all data will be disappeared.
10. Install Magisk manger
11. Download stock ROM from blackview forum. it is zip file. Unzip it and copy boot-verified.img to phone.
12. patch boot.img by Magisk manger.
13. Copy patch image file to windows
14. use adb to reboot phone to fastboot mode
15. reflash boot image file. command: fastboot flash boot patched file name (normally, I would put patch image file in the same folder of fastboot)
16. reboot (fastboot reboot) and reinstall Magisk manager
There are many Magisk root steps instruction in internet. You could refer to other steps, they should be clear than mine. I prepared lots of drivers and application. Finally, I only used adb and fastboot to root this phone.
Click to expand...
Click to collapse
zlatkomas said:
hi if u have back up on your phone could u provide for me link. I had some problems with my loudspeaker and i thought its from the root, or software and i did full format and download. and now it show some watermark and probably is because i l deleted NVRAM.
i download already official version but didn't help ... thank u upfront.
Click to expand...
Click to collapse
Hi, I'm not rooted (yet) and my BV9800 PRO is having some issues with the loudspeaker, any media like YouTube or Spotify, play audio for a second or two and then just go mute, volume can be high but no audio at all, phone calls last longer but also go mute and have to go back to regular "ear-speaker" to keep listen to the other side. Are this the same problems you refer to? I can't remember if this happened after the OTA update tho. Thank you.
The Sonim XP3800 is a very rugged phone, but it is very limited. Rooting can expand its capabilities.
1) This is the stock image for the Sprint model
3A.0.5-05-8.1.0-29.70.00_USER_PST.zip
2) This is the magisk - patched boot image
boot.img
3) Flash tool
Sonim Feature Phone Software Installer
Username: testmulti
Password: testmulti123
4) After flashing the patched boot image, use adb to install Magisk Manager
5) To install apps directly from the phone, install https://github.com/bavelee/PokeInstaller
6) To enable DIAG mode, use the secret code
Code:
*#*#0701#*#*
will doing this to my xp3800 sprint carrier locked phone allow me to use gci as carrier?
@ytagger - which carrier/version is the image for? I setup dev mode on my US Cellular unlocked XP3, had a successful connection via the Sonim Software Tool, unzipped the image and overwrote the boot.img, but I got a version not applicable to phone or downgrade error when trying to flash it. What’s the approach for this?
saniko said:
@ytagger - which carrier/version is the image for? I setup dev mode on my US Cellular unlocked XP3, had a successful connection via the Sonim Software Tool, unzipped the image and overwrote the boot.img, but I got a version not applicable to phone or downgrade error when trying to flash it. What’s the approach for this?
Click to expand...
Click to collapse
This image is for Sprint. I'll try to upload the US Cellular version later
ytagger said:
This image is for Sprint. I'll try to upload the US Cellular version later
Click to expand...
Click to collapse
That would be awesome. I’m worried that I might lose the IMEI or something similar, but it would be nice to have a daw more tools on my phone.
Here is a full backup of a US Cellular Sonim XP3
Hmm - I had a better understanding of how to flash and root the Sprint image. I don’t know how to work with the US Cellular one. It does not seem to have the img files that allowed the Sonim flash tool to work
You're right, it won't work with the Sonim Flash tool, at least not without modification. It's not a stock image. But you can use QFIL to flash it. https://qfiltool.com/qfil-tool-v2-0-3-5
Argh - I adb pushed magisk onto the Sonim XP3 to see if I could install the boot image. Unfortunately, couldn't find a way to select the file inside magisk (sonim only allows Gallery, Contacts, Music Player to select files). Can't fastboot flash the boot.img because I can't unlock the bootloader
So lost @ytagger . Tried QFIL but struggled to make anything work.
Hey I don't have any experience with this and was looking to put apps on the sprint Sonim without using adb, i tried using the flash tool and downloaded the boot img on the computer, but I have no idea if I'm using the tool wrong or if the boot img needs to be modified extracted or unzipped and if I'm supposed to find the file in the build path or something else entirely, can somebody please help me?
I can’t really help you, but I can mention that adbed some apps to the device and realized how impossible it can be to use apps in android without a touch screen And such low resolution. I may not see the value in this that I had hoped for.
saniko said:
I can’t really help you, but I can mention that adbed some apps to the device and realized how impossible it can be to use apps in android without a touch screen And such low resolution. I may not see the value in this that I had hoped for.
Click to expand...
Click to collapse
Check out the website apps4flip they have a bunch of apps that work without a touchscreen and those are meant for a crippled android 5, the sonim I think is better, there is even a mouse for it in the forums there though it probably doesn't drag, my problem was locating the boot.img in the build path of the flash tool if that's how you use it, if anybody can help that would be great
Hi, all. Someone succeed with dualsim activation? Have some xp3 and xp5s. Both with double slots but only one active card. I think similar sim-disable method for 3, 5s, 8.
That app4flip website is amazing even if you don't care for the religious overtones. I spent an entire day examining the stuff people had considered and the mouse app is perfect to handle apps that rely on a touchscreen.
ytagger said:
The Sonim XP3800 is a very rugged phone, but it is very limited. Rooting can expand its capabilities.
1) This is the stock image for the Sprint model
3A.0.5-05-8.1.0-29.70.00_USER_PST.zip
2) This is the magisk - patched boot image
boot.img
3) Flash tool
Sonim Feature Phone Software Installer
Username: testmulti
Password: testmulti123
4) After flashing the patched boot image, use adb to install Magisk Manager
5) To install apps directly from the phone, install https://github.com/bavelee/PokeInstaller
6) To enable DIAG mode, install Activity Launcher. Then open EPST Hidden Menu activity DiagView. Now enable DIAG mode. This is a special DIAG mode which also includes other USB modes. QFIL may not recognize it. Otherwise, enable it through root with
Code:
setprop sys.usb.config diag,adb
.
Click to expand...
Click to collapse
Decompile the system APK, Erase all data(factory reset) and not enter the system, know what is wrong?
ytagger said:
The Sonim XP3800 is a very rugged phone, but it is very limited. Rooting can expand its capabilities.
1) This is the stock image for the Sprint model
3A.0.5-05-8.1.0-29.70.00_USER_PST.zip
2) This is the magisk - patched boot image
boot.img
3) Flash tool
Sonim Feature Phone Software Installer
Username: testmulti
Password: testmulti123
4) After flashing the patched boot image, use adb to install Magisk Manager
5) To install apps directly from the phone, install https://github.com/bavelee/PokeInstaller
6) To enable DIAG mode, install Activity Launcher. Then open EPST Hidden Menu activity DiagView. Now enable DIAG mode. This is a special DIAG mode which also includes other USB modes. QFIL may not recognize it. Otherwise, enable it through root with
Code:
setprop sys.usb.config diag,adb
.
Click to expand...
Click to collapse
Do you know where one could find the AT&T firmware for the Sonim XP3800 ?
hi
tring to flash my xp3800. cant download stock image. can anybody help?
thx
It seems like a fairly complicated process to root this device with the fh programmer and edl mode. Confused to say the least. As far as I can tell without the original firmware file I am sol, can you please reupload the sprint firmware file. I only want to root to be able to adjust my apn settings, I am unable to edit them without root access. I am thinking my mms would work if I could get a ATT image flashed to the device. Almost no information or files on this device exist. Im not even sure how you got the files originally lol. Can I pull the firmwre off the device?
There is now a serious need for a way to remove the UICC lock from the Sprint XP3's since T-Mobile will be discontinuing support for Sprint SIM's this year.
ytagger said:
The Sonim XP3800 is a very rugged phone, but it is very limited. Rooting can expand its capabilities.
1) This is the stock image for the Sprint model
3A.0.5-05-8.1.0-29.70.00_USER_PST.zip
2) This is the magisk - patched boot image
boot.img
3) Flash tool
Sonim Feature Phone Software Installer
Username: testmulti
Password: testmulti123
4) After flashing the patched boot image, use adb to install Magisk Manager
5) To install apps directly from the phone, install https://github.com/bavelee/PokeInstaller
6) To enable DIAG mode, use the secret code
Code:
*#*#0701#*#*
Click to expand...
Click to collapse
Sprint XP3 locked to CDMA network, how to fix it