Xiaomi QIN 1S Hacking Mega-Thread!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I decided to go ahead and buy a Xiaomi QIN 1s feature phone. Unlike other feature phones, it runs a version of Android. Since there doesn't seem to be any threads here on XDA, I thought I'd start one.
SPECS
I finally found a guide/tool over on 4pda that will let you install apks. I have translated the tool to English and have it attached. The original post of the tool is here
If you don't want to download the tool (which also helps with ADB) here are the steps to obtain root:
-- Install the driver on your PC
-- Dial: *#*#83781#*#* To Open the Engineering Menu
-- Find the section "Debug & Log" and enable "Allow Debug"
-- Open the Settings app
-- Find "about phone"
-- Click "Build number" multiple times until you see "You are now a Developer!"
-- Go to "Developer options" and then turn on USB Debugging
-- Connect your phone to your computer (MTP)
-- Using ADB, push the apk to the device
-- ???
-- Profit
You can use this method to install any applications, not just root the phone. Remember, however, we only have 256mb of RAM and a total of 512mb of storage. Definitely not for gaming and you will definitely want an SD Card. I can confirm QQ and WeChat work fine when installed.
Let's get this rooted!
Big shoutout to Frolkin who helped me get the original tool and gaguga for making the tool!
Reserved
NICE! Thank you so much for posting that code. I have been searching for this code but couldn't find anything until yesterday.
So far I've sideloaded spotify lite and it doesn't work that well. Get stuck on the playlist view and can't scroll further down beyond the top banner.
Google Maps Go doesn't work without chrome and I can't install chrome because there isn't enough space.
Since mocor5 is on kitkat 4.4.4, would the hack to allow system to write to SD Card work to enable additional space for app installation?
foureight84 said:
NICE! Thank you so much for posting that code. I have been searching for this code but couldn't find anything until yesterday.
So far I've sideloaded spotify lite and it doesn't work that well. Get stuck on the playlist view and can't scroll further down beyond the top banner.
Google Maps Go doesn't work without chrome and I can't install chrome because there isn't enough space.
Since mocor5 is on kitkat 4.4.4, would the hack to allow system to write to SD Card work to enable additional space for app installation?
Click to expand...
Click to collapse
It should. I don't see why not. It might be worth it to just root the Qin and install apks directly to the sd card. The spotify issue is most likely because the app doesn't support the dpad.
Qiangong2 said:
It should. I don't see why not. It might be worth it to just root the Qin and install apks directly to the sd card. The spotify issue is most likely because the app doesn't support the dpad.
Click to expand...
Click to collapse
Yep the spotify issue is 100% because of that. The mouse pointer works but on certain views like the playlist, the scroll doesn't register. I wish the next version would add a a touch feature. Even if it's the same screen size, I think that would be a perfect device.
I have been looking for a replacement and get away from bulky and constantly connected smartphones without losing some of the nicer features like streaming music and using maps when I get lost. The hotspot feature makes this phone much more compelling to use too.
ROOT/ ROM download
Qiangong2 said:
Xiaomi QIN 1S Hacking Mega-Thread!
I decided to go ahead and buy a Xiaomi QIN 1s feature phone. Unlike other feature phones, it runs a version of Android. Since there doesn't seem to be any threads here on XDA, I thought I'd start one.
SPECS
After seeing vague rumors of it being possible to root the QIN 1s, I finally found a guide/tool over on 4pda. I have translated the tool to English and have it attached. The original post of the tool is here
If you don't want to download the tool (which also helps with ADB) here are the steps to obtain root:
-- Install the driver on your PC
-- Dial: *#*#83781#*#* To Open the Engineering Menu
-- Find the section "Debug & Log" and enable "Allow Debug"
-- Open the Settings app
-- Find "about phone"
-- Click "Build number" multiple times until you see "You are now a Developer!"
-- Go to "Developer options" and then turn on USB Debugging
-- Connect your phone to your computer (MTP)
-- Using ADB, push either iroot or kingroot apk to your device
-- ???
-- Profit
You can use this method to install any applications, not just root the phone. Remember, however, we only have 256mb of RAM and a total of 512mb of storage. Definitely not for gaming and you will definitely want an SD Card. I can confirm QQ and WeChat work fine when installed.
Let's see how far we can crack this phone open!
Big shoutout to Frolkin who helped me get the original tool and gaguga for making the tool!
Click to expand...
Click to collapse
Hi This app doesn't work to root that Xiaomi and do you know how to download ROM without ROOT?
danio40 said:
Hi This app doesn't work to root that Xiaomi and do you know how to download ROM without ROOT?
Click to expand...
Click to collapse
I don't know how to download an unrooted rom, sorry. Also, I put in the post that you need to load either Kingroot or iroot. However, I have uploaded iroot to the post. please check.
EDIT: hmm... I guess you're right. My new 1s comes in about two weeks, and then I'll be able to test it more extensively. It's possible that it may give you temp root after running it and you can manually install supersu from there
foureight84 said:
Yep the spotify issue is 100% because of that. The mouse pointer works but on certain views like the playlist, the scroll doesn't register. I wish the next version would add a a touch feature. Even if it's the same screen size, I think that would be a perfect device.
I have been looking for a replacement and get away from bulky and constantly connected smartphones without losing some of the nicer features like streaming music and using maps when I get lost. The hotspot feature makes this phone much more compelling to use too.
Click to expand...
Click to collapse
Yeah! that's what interested me in it. I don't necessarily need a touch screen, but a 5mp camera on the back would be nice for the few times I do take photos.
Qiangong2 said:
I don't know how to download an unrooted rom, sorry. Also, I put in the post that you need to load either Kingroot or iroot. However, I have uploaded iroot to the post. please check.
EDIT: hmm... I guess you're right. My new 1s comes in about two weeks, and then I'll be able to test it more extensively. It's possible that it may give you temp root after running it and you can manually install supersu from there
Click to expand...
Click to collapse
I'm trying both Iroot and kingroot nothing still unrooted.
Also I tried to use a box miracle SPD to download but no luck it stuck on loading FDL and freeze.
danio40 said:
I'm trying both Iroot and kingroot nothing still unrooted.
Also I tried to use a box miracle SPD to download but no luck it stuck on loading FDL and freeze.
Click to expand...
Click to collapse
I've updated the thread with the fact that we have not gotten root yet. I left the tool there because it can help people install apks.
Time to find a root method
danio40 said:
I'm trying both Iroot and kingroot nothing still unrooted.
Also I tried to use a box miracle SPD to download but no luck it stuck on loading FDL and freeze.
Click to expand...
Click to collapse
Have you tried using a PC-based root solution such as shuame pc or kingo pc?
Qiangong2 said:
I've updated the thread with the fact that we have not gotten root yet. I left the tool there because it can help people install apks.
Time to find a root method
Click to expand...
Click to collapse
yes I'm stuck with it. I want to download a ROM in a PAC file. I think that bootloader is locked when I looked via xiaomi adb tool.
danio40 said:
yes I'm stuck with it. I want to download a ROM in a PAC file. I think that bootloader is locked when I looked via xiaomi adb tool.
Click to expand...
Click to collapse
On 4pda they claim it isn't locked.
If you do:
adb reboot bootloader
fastboot oem get-var
fastboot oem unlock
Supposedly it unlocks the device
Qiangong2 said:
On 4pda they claim it isn't locked.
If you do:
adb reboot bootloader
fastboot oem get-var
fastboot oem unlock
Supposedly it unlocks the device
Click to expand...
Click to collapse
In fastboot mode when typed fastboot oem get-var <waiting for any device>
Doesn't do anyrhing
danio40 said:
In fastboot mode when typed fastboot oem get-var <waiting for any device>
Doesn't do anyrhing
Click to expand...
Click to collapse
What does fastboot devices show? Do you have all the drivers installed? Does it show up in the upgrade tool?
Qiangong2 said:
What does fastboot devices show? Do you have all the drivers installed? Does it show up in the upgrade tool?
Click to expand...
Click to collapse
I'm trying now kingoRoot PC version. I useed xiaomi ADB to see if the bootloader is locked. It shows that is locked. I have got debugging ON. There is a big issue with a space on that phone. kingroot installed only and it comes up as no memory. Maybe that is the case why is not rooting so I'm trying now after RESET the phone to use PC version - maybe will work.
After that i'm going to bed sorry but we can play tomorrow anytime
---------- Post added at 03:53 AM ---------- Previous post was at 03:46 AM ----------
danio40 said:
I'm trying now kingoRoot PC version. I useed xiaomi ADB to see if the bootloader is locked. It shows that is locked. I have got debugging ON. There is a big issue with a space on that phone. kingroot installed only and it comes up as no memory. Maybe that is the case why is not rooting so I'm trying now after RESET the phone to use PC version - maybe will work.
After that i'm going to bed sorry but we can play tomorrow anytime
Click to expand...
Click to collapse
Also yes all drivers I think I have got installed. When it is fastboot mode it is just says that 2 words nothing else. No menu. I dont have upgrade tool.
danio40 said:
I'm trying now kingoRoot PC version. I useed xiaomi ADB to see if the bootloader is locked. It shows that is locked. I have got debugging ON. There is a big issue with a space on that phone. kingroot installed only and it comes up as no memory. Maybe that is the case why is not rooting so I'm trying now after RESET the phone to use PC version - maybe will work.
After that i'm going to bed sorry but we can play tomorrow anytime
---------- Post added at 03:53 AM ---------- Previous post was at 03:46 AM ----------
Also yes all drivers I think I have got installed. When it is fastboot mode it is just says that 2 words nothing else. No menu. I dont have upgrade tool.
Click to expand...
Click to collapse
Okay, keep me updated
Qiangong2 said:
Okay, keep me updated
Click to expand...
Click to collapse
KINGOROOT - root failed
danio40 said:
KINGOROOT - root failed
Click to expand...
Click to collapse
Shoot. Next step I guess, is see if it shows up when in fastboot mode.
On linux use lsusb
On windows open device manager
Do you see the Qin?
Qiangong2 said:
Shoot. Next step I guess, is see if it shows up when in fastboot mode.
On linux use lsusb
On windows open device manager
Do you see the Qin?
Click to expand...
Click to collapse
On windows manager Yes but only if you choose MTP then it shows as QIN 1s, Standard file manager.
Related
Updated to March 16th 2014.
General Warning, read before doing anything to your tablet:
Whenever you try to do anything to your system ALWAYS back up everything since there is always the chance that something might go wrong.
If something goes wrong you have to download and install the boot images from HP support, HP Slate 7 2800 restore image and HP Slate 7 4600 restore image, the install instructions are in the same page in "How to install".
Some users have had problems with the alternative rooting method using Bin4ry's tool, since it is some I will asume it is something someone is not doing correctly, because other users with the same slate model have been able to root, if it is your case where you can't actually root post here I'll try to help you in any way I can.
To end this sort of disclaimer, my Slate 7 is the model 4600 so I'm not actually able to try the method with other slate models, anyhow other users have had no problem but as always this could be your case and I'm not responsible in any way if you brick your device.
Cydia's Impactor tool has been updated and it's working with all versions of the roms (Confirmed by users).
Bin4ry's rooting tool has been updated, chances are it's more friendly user and won't throw any errors, up to you to try it out.
Just as a side note, the screenshots below are just for reference, they are not the same drivers/devices, they are only meant for you to know where to click.
Step 1: Download Tool Package (this is an old package, the drivers in the package works but you NEED TO ALSO DOWNLOAD Cydia's Impactor (Link to home page in case you are interested in reading a bit) and Googles ADB Drivers with a little modification in the ini file so it installs the driver for our HP Slate 7 tablet). If your Slate 7 model is 2800, you have to also download Moborobo that will find and install the drivers for you. I've received messages from users who have had both good luck and no luck installing the drivers, this must be dependant on your operative system and administrative rights, I did all this steps on a Windows 8 64bits machine with administrative privileges.
Download latest Cydia's impactor tool from the link above. The one in the package won't help you if you are trying to root v9 and above.
Step 2: Unzip the package anywhere you like, meanwhile go to your tablet and set it to USB Debugging.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
YOU MUST SET IT ON USB DEBUGGING MODE, else nothing that you try will work.
Step 3 OPTIONAL: Just in case if your computer doesnt realize there is a device connected you need to copy the file in "\.android\adb_usb.ini" over to your user path "%USERPROFILE%\.android\" and reboot the computer (Just in case it wont recognize a device as connected).
Step 4: Now open the computers Device Manager and you will see something similar to this picture
Step 5: Right click the HP Device and choose to update driver, search for drivers in the computer (2nd option), then "let me pick from a list of device" as follows:
Step 6: Next click in "have disk" and navigate to where you unpacked the file downloaded earlier and choose the ini file.
Pictures for reference only.
Step 7:All you have left is open Cydia's Impactor tool, you will see a small window with a default command on screen which is the following:
Code:
# drop SuperSU su to /system/xbin/su
Just click Start next to it aaaaand you are done!
(PS: If this worked you are done, skip Step 7B. If you were unable to root your device try Step 7B)
Step 7B (ONLY IF Cydia's tool did not work): Warning: I've received messages from some users that this exploit has left them on bootloops, this method is tested on the 4600 model, if you have another and it works please do post your results, if you have problems all you have to do is download your model ROM from HP support and boot it through your microSD card to restore factory settings, also check in Bin4ry's thread for information if it is your case, if you find another method please do let us know . DO THIS ONLY IF STEP 7 FAILED, you will have to download the following rooting tool from Bin4ry's XDA thread, execute "RunMe.bat" and use method 1 and follow the on-screen instructions (This method will reboot your tablet 3 times if I remember correctly, after 2 reboots it will be stuck in a black screen for a couple of minutes (or more, it took me around 10 minutes) this is as it pushes the files for superuser, don't panic).
You can check your build version as it's shown in the following picture.
Just open an app like Titanium Backup which needs root to see if it worked.
This method is simple plus you don't have to download anything chinese or unnecesary software into your computer, the tutorial is really long because I tried to be as detailed as posible but in the end you shouldnt take more than 5 minutes (The downloads might take a bit longer though for the SDK), I would take screenshots of the process but my computer runs on a Spanish version of Windows (The same reason why you might see things with different names I was just trying to guess the device manager label part).
If you have any question feel free to ask (of course... as long as it hasn't been asked again and again in the thread ) and if it worked for you a thanks would be awesome so more users will try
PS: My Slate 7 model is the 4600 but it should work with others slates and for that matters, with any tablet as long as the adb driver is recognized.
PS2: If you could upload the package into a new mirror that might help more people.
PS3: Updated to March 16th 2014.
PS4: I just realized the screenshots facilitated by another user have been deleted, will try to find new ones.
PS5: If this helped you, please do thank, this way more users will benefit from it.
Universal Root
Ok people, I've used pretty much the same method to unlock 2 different tablets, if you see my other guide with rooting MSI Windpad 71 it's almost the same thing.
Once you get ADB running all you have to do is run Cydia's impactor and you are good to go.
If this helped anyone please tell your experience and with which devices you have tried this.
It's working guys!
It works perfectly, even better.
Also does anybody know how to make GT Racing Academy work on it?
My HP its Slate7 2800 your thread its for 4600 its diferent i think? I cant install the driver from device manger.
mastertempo said:
My HP its Slate7 2800 your thread its for 4600 its diferent i think? I cant install the driver from device manger.
Click to expand...
Click to collapse
Please do reply to the questions I asked you earlier, if you don't give out information I don't know what you are not doing right.
Dont wory man,i root my slate 7. How? I told you now. First i intall this: https://www.dropbox.com/s/0jg872o2armnntt/ADBDrivers.exe and strart it and install drivers. Then i run cydia impactor and everyting its done for few seconds. But i have one question now: is the cydia its universal for all android deviceses?
mastertempo said:
Dont wory man,i root my slate 7. How? I told you now. First i intall this: https://www.dropbox.com/s/0jg872o2armnntt/ADBDrivers.exe and strart it and install drivers. Then i run cydia impactor and everyting its done for few seconds. But i have one question now: is the cydia its universal for all android deviceses?
Click to expand...
Click to collapse
Yes, Cydia's main goal is to be a universal rooting tool.
I will check on the drivers you found, it could shorten the guide.
For everyone else I know it looks like a lot of steps, but it's really download software, modify a couple of ini files, install driver and run Cydia Will check on the drivers MasterTempo installed maybe I can make a package for a single small download.
Ok guide updated to v2.0 with single package download.
As long as the computer recognizes the ADB drivers for the phone/tablet Cydia's Impactor tool should root any device.
Worked on my slate. Thank you very much for your help
Sent from my GT-I9100 using XDA Premium 4 mobile app
what about unroot?
hi still i didnt root but i want to know how to unroot it : as my HP Slate is very new
OTA update
kibaruk said:
Ok guide updated to v2.0 with single package download.
As long as the computer recognizes the ADB drivers for the phone/tablet Cydia's Impactor tool should root any device.
Click to expand...
Click to collapse
My tablet is asking to update, if I do the OTA will I lose root?
wasim9283 said:
hi still i didnt root but i want to know how to unroot it : as my HP Slate is very new
Click to expand...
Click to collapse
No idea here mate sorry.
dalethefarmer said:
My tablet is asking to update, if I do the OTA will I lose root?
Click to expand...
Click to collapse
Nope, I've updated mine and it's still rooted.
kibaruk said:
No idea here mate sorry.
Nope, I've updated mine and it's still rooted.
Click to expand...
Click to collapse
I just updated mine and lost root...
dalethefarmer said:
I just updated mine and lost root...
Click to expand...
Click to collapse
Really?? That's odd... well you could always just re-run Cydia and go ahead with the push of files again and voila rooted again.
kibaruk said:
Really?? That's odd... well you could always just re-run Cydia and go ahead with the push of files again and voila rooted again.
Click to expand...
Click to collapse
Doesn't work. When I run Impactor I get an error: Signature bugs unavailable.
I tried updating impactor and I have the latest version.
I can factory reset and root again, but how do I stop the OTA update prompts from popping up?
dalethefarmer said:
Doesn't work. When I run Impactor I get an error: Signature bugs unavailable.
I tried updating impactor and I have the latest version.
I can factory reset and root again, but how do I stop the OTA update prompts from popping up?
Click to expand...
Click to collapse
Ok it seems the latest OTA which was a big one over 250mb changed something, I lost root access too, will have to see how to get this one rooted.
If anyone could confirm before trying to update to big OTA their versions? Mine is after OTA Android Version 4.1.1 compilation numbre v1.05.10_user.
It seems that for version 1.05.10 they have fixed the master key vulnerability of android.
"If you are having problems using Cydia Impactor (it crashes, doesn't work on your device, or simply doesn't make any sense) please join #android on irc.saurik.com and ask a question.
The Android "Master Key" vulnerability was found by Bluebox Security. For more information on how this bug works, I have done an overly-detailed article on the exploit technique.
If that bug is not available, Impactor will instead attempt to use a different signature verification bug. For more information on how that bug works, I have done another article on the new exploit.
It is possible that your device has been patched against both bugs; Impactor will inform you of this. If you'd like to check before spending time working with Impactor, you can try either the Bluebox Security Scanner or the alternative SRT AppScanner (which I have found to provide fewer false positives than Bluebox's tool).
Some devices are also patched against the second stage now used to get root; devices that are patched will show "link failed file exists". (This second stage was made possible due to help from @giantpune.)".
dalethefarmer said:
Doesn't work. When I run Impactor I get an error: Signature bugs unavailable.
I tried updating impactor and I have the latest version.
I can factory reset and root again, but how do I stop the OTA update prompts from popping up?
Click to expand...
Click to collapse
Ok I found a working root for latest 1.05.10 patch you can download here.
Once you download the tool you have to run the "RunMe.bat" file and follow the instructions, the method that worked was method 1 "New Standard-Root", it seems to also come with an unroot option for those who have asked for it, havent tried it though.
PS: Be careful when "press a key to continue now" because you can make it a double tap and miss a step, it won't brick the device but you will take longer.
Guide updated for latest OTA pushed 1.05.10_user that won't accept Cydia's vulnerability. It seems that the alternative rooting tool has the option to unroot for all of those who have asked for it, I havent tried it yet though.
mastertempo said:
My HP its Slate7 2800 your thread its for 4600 its diferent i think? I cant install the driver from device manger.
Click to expand...
Click to collapse
I've found out other HP Slate 7 2800 users are having problems with the drivers I put in the package, they have found Moroboro useful for that matter
Hi all, i passed trough the bad experience of a phone with a broken screen, all my data was trapped inside the device and i couldn't see nothing on the screen :crying:
So i decided to develop a little app, in order to be able to break into my phone again and save the more stuff i could.
Gstreamer (aka Ghost streamer) is able to let you see your device screen once again (that was the primary purpose...) and deal with it by clicking and swiping with your mousepointer on your phone screen picture (yes, it's slow but it gets the job done )but without the need to install softwares like VNC and similars (Gstreamer only allows you to gain access your files in a way or another and try to save it),.
If your dead phone was rooted and with a custom recovery, then yur life will be easy in case of broken screen , but if not , then the music changes a lot, that's why i thought my software could help other people to solve theproblems i meet during my data rescue attempts.
No matter the device screensize, it will adapt to your device screensize and will make your life easier if you broken your phone screen.
I'm still adding features to it, and planning to organize it in a better way, correcting some bugs, testing it on different phones and android versions,but it's actually working and improving day by day
if someone is interested in testing it with me, and report then the experience i'd be happy to cooperate.
at the moment this is the pre-alpha stage for me , but this is how it looks now
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you are having bad times with your phone screen this may help you :fingers-crossed: just contact me if interested
use at your own risk it's still experimental, download it from the link below
http://www.filedropper.com/gstreamerv1000release
open for feature requests here , if you want me to add special functions, just ask here and i will see if it can be embedded or not.
get the latest nightly build on my git, just click on the "Download ZIP" button. (link below)
any advice is appreciated, thank you.
changelog!
new release, now the Apk operations are ok , now you can list, uninstall, pull, install apk from your PC.
always get the latest release from my git
https://github.com/TheBrainBooster/Gstreamer/archive/master.zip
BrainBooster said:
open for feature requests here , if you want me to add special functions, just ask here and i will see if it can be embedded or not.
get the latest nightly build here https://github.com/TheBrainBooster/Gstreamer just click on the "Download ZIP" button.
any advice is appreciated, thank you.
changelog!
new release, now the Apk operations are ok , now you can list, uninstall, pull, install apk from your PC.
always get the latest release from my git
https://github.com/TheBrainBooster/Gstreamer/archive/master.zip
Click to expand...
Click to collapse
new changelog! V1.2.1.0 release
added dpad navigation buttons
minor bugfixes
redesigned main panel
new changelog! V1.2.2 is available for the download
added swipe buttons
added memory info
minor bugfixex
check it out and let me know testers are welcome
01/02/2016
new changelog!
minur bug fixes
added file push , pull and sideload functions
...sadly i don't have feedback so i can't be sure it will work with all the android versions
...many changes heve been done, stay tuned for the next release
Hello,
tried you app, but it does not recognize my phone, because it has not debugging mode activated. I tried even "RSA ADB key inejection and..." but with no luck. For anther device, which has debugging mode active, I was able to get its data, but for the one with broken display and no debugging mode, it doesn't.
Any hints?
Regards,
can you provide some more informations about your device?
maybe you could try to repeat the procedure but in recovery mode
Hello,
Thanks for your time. So far you're the only one who gave me something as an information, or tip/hint.
My phone is an Samsung i9300i, with stock rom, only recently when trying to get the data through ADB, I have installed via ODIN an image named "CWM Recovery v6.0.3.6.tar", but still no effect in ADB.
Before replying to you I have tried recovery mode as well (power button, home, volume - and after 5 seconds volume up- as those were the steps required for my model to get into download mode). But I cannot get your up to recognize my phone. I tried with another one (HTC One M8s), with debugging mode on and the app recognize it in a flash. But with the broken one, no luck.
Are there necessary some custom drivers? Do you think some print screens could help?
a screenshot could help for sure
installing the proper adb drivers too, try with this --> http://forum.xda-developers.com/showpost.php?p=50008343&postcount=486
also installing the official kies software by samsung may help
whas the phone rooted?
can it boot normally?
do you see something on the screen?
what is the damage on you phone?
android version?
Hello and good morning (for me it's still morning),
No, the phone was not rooted, was "untouched". I gave up the idea I can retrieve data via software and I was thinking to try to open it and have a display temporary put, but it's time consuming and I'm short on time to recover the data (some business information for my boss).
I'll try the drivers you have wrote and I'll came back with screen shots as well.
Regards,
sorry for the late post edit, but it came to my mind after i wrote
by the way... are you sure you booted into recovery mode?
my software shoud see the phone anyway when you hit the test conection button
Hello and good morning (for me it's still morning),
No, the phone was not rooted, was "untouched". I gave up the idea I can retrieve data via software and I was thinking to try to open it and have a display temporary put, but it's time consuming and I'm short on time to recover the data (some business information for my boss).
I'll try the drivers you have wrote and I'll came back with screen shots as well.
LE: Yes, I'm booting in download/recovery mode (combination of pow+volume minus + home buttons and volume up after 5 -7 seconds - steps specific for Sam i9300i phones)
Regards,
miborion said:
Hello and good morning (for me it's still morning),
No, the phone was not rooted, was "untouched". I gave up the idea I can retrieve data via software and I was thinking to try to open it and have a display temporary put, but it's time consuming and I'm short on time to recover the data (some business information for my boss).
I'll try the drivers you have wrote and I'll came back with screen shots as well.
LE: Yes, I'm booting in download/recovery mode (combination of pow+volume minus + home buttons and volume up after 5 -7 seconds - steps specific for Sam i9300i phones)
Regards,
Click to expand...
Click to collapse
so you shoud see the phone connected maybe it will say: device-12345abcdefyourphoneID-(recovery) but if you have the drivers installed it should appear in the log window, moreover you said maybe you have a CWM recovery installed...
remember to reboot your pc ater the drivers setup
BrainBooster said:
so you shoud see the phone connected maybe it will say: device-12345abcdefyourphoneID-(recovery) but if you have the drivers installed it should appear in the log window, moreover you said maybe you have a CWM recovery installed...
remember to reboot your pc ater the drivers setup
Click to expand...
Click to collapse
Indeed I have had installed CWM (if by that you are referring to "CWM Recovery v6.0.3.6.tar" file - which I did, using ODIN (v.307)), as I thought the debugging mode would be activated, but it seem it doesn't. Please can you give me more details about what did you want to say by " moreover you said maybe you have a CWM recovery installed..."? Is it a bad thing? Should I flash to a stock rom?
And no, it does not show any devices like device-1234afsadsasdasd.
Regards,
what i mean is, if you installed a custom recovery and you also have your phone drivers properly installed you should have an adbd server running on the phone(provided by the custom recovery environment) and an adb client running on the pc, so they should see each other
BrainBooster said:
what i mean is, if you installed a custom recovery and you also have your phone drivers properly installed you should have an adbd server running on the phone(provided by the custom recovery environment) and an adb client running on the pc, so they should see each other
Click to expand...
Click to collapse
Ok, now I understand what is the purpose for that img.
So, bottom line is I cannot seem to install proper drivers. I'll try different combinations of uninstall plus install drivers from your link (i had used the ones from Samsung site, released this year), plus computer reboot, as so far I wasn't able to have ADB listener list my device (or your application).
Regards,
Root it! everything will be much more easy
http://androidmtk.com/root-samsung-galaxy-s3-neo-gt-i9300i
BrainBooster said:
Root it! everything will be much more easy
http://androidmtk.com/root-samsung-galaxy-s3-neo-gt-i9300i
Click to expand...
Click to collapse
I'll try, but, I'm not able to check what is my build number. As far as I know, I have only the stock image (exactly as the phone came with) and am sure it hasn't have the 4.4.4 version, but something like 4.3 something...I have a colleague, back at work which has some same device (Sam I9300i) and I could check the version on that terminal and try my luck.
Thanks again for your time and insight
miborion said:
I'll try, but, I'm not able to check what is my build number. As far as I know, I have only the stock image (exactly as the phone came with) and am sure it hasn't have the 4.4.4 version, but something like 4.3 something...I have a colleague, back at work which has some same device (Sam I9300i) and I could check the version on that terminal and try my luck.
Thanks again for your time and insight
Click to expand...
Click to collapse
anytime
if you need further help , just ask
BrainBooster said:
anytime
if you need further help , just ask
Click to expand...
Click to collapse
Hello,
I've just finished all leads meaning I have successfully rooted the phone by using your link; I got PASS message in ODIN using the exact image as the tutorial indicated. But, still I cannot connect to the phone with ADB, or by using your app.
If I boot normally I can hear the sound, see the top buttons lid and have the popup message in windows which tells me I can browse the mobile phone's content (onStdBoot.jpg).
If I boot in recovery mode (can see COM0 used in ODIN and can flash successfully) I get the devices on the second print screen (BootInDownloadMode.jpg) but cannot access it.
Could you please advise if there is anything else I can try?
Regards,
if you successfully rooted your device, booting it in recovery mode should make it show in my software
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE
New twrp 331-test 1 for this device is builded!
Now need period of tests...
http://www.mediafire.com/file/cnqw8d2qkjqtp6k/Twrp_331_test1_Umi_Power.rar/file
reserved 1
Reserved 2
TWRP Not Working for Me
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
I confirm the first part of this, same issue here... i'd like to flash a twrp for gsi purposes, but for now no luck
SeekerofLight.iz said:
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Root UMIDIGI Power with Magisk
mr A V said:
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Click to expand...
Click to collapse
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
Step 0 - Download the Attached Zip File Below
Google Drive Mirror
Mediafire Mirror
MEGA Mirror
Step 1 - Drivers
Install the MediaTek drivers by running "DriverInstaller.exe". These are the drivers that worked for me. But if you have issues with them in Step 5, Google "Mediatek MT65xx USB VCOM Drivers" (or some variation of that) and try some others you can find.
-----------------------------------
Step 2 - Install ADB Interface
Install the Android SDK (ADB Interface). To do this drop the platform-tools folder (from the Step 2 folder) into your C:\ directory. Press the windows start button and search for "Environment Variables" and click on "Edit environment variables" from the results. Under SYSTEM VARIABLES on the bottom (not User variables above it) click on the "Path" variable, and click edit. In the new window that appears, hit "Browse..." and click on the "platform-tools" folder that you placed in your C:\ directory.
All this does is allows you to easily input adb commands into command prompt with no issues. This will be used to verify that the device is appearing properly and issue commands in case of emergency.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-----------------------------------
Step 3 - Install Magisk
Copy the Magisk.apk to your phone and install it.
(This is where you can then copy the boot.img to your device and patch it via the Magisk app to create the "magisk_patched_boot.img" file, however I have included the already patched file in Step 6 for the UMIDIGI Power so you don't need to.)
Also, this is the Magisk v19.3 Beta, but you can install another version.
-----------------------------------
Step 4 - OEM Unlocking/USB Debugging Mode
On your phone, go to Settings >> System >> Developer Options. (If you haven't activated Developer Options yet, do that by going to About Phone >> Build number, and tap it a bunch of times, but I'm sure you already know this lol)
In Developer Options, turn on "OEM Unlocking" to unlock the bootloader, and USB Debugging.
-----------------------------------
Step 5 - Verify That Your Phone is Detected with ADB
Connect your phone to your PC. Make sure you click "Allow USB debugging" on your phone. Then open up Command Prompt. (Protip: Type "color a" and press Enter if you want to feel like a REAL HACKERMAN.) Now, type in "adb devices" and verify that your phone is detected by your computer. If it's detected, then that's perfect you can move on to Step 6. If not, then uh... you may have to try and find some other MediaTek drivers mentioned in Step 1.
-----------------------------------
Step 6 - Set up SP Flash Tool
Open up SP Flash Tool on your computer by running "flash_tool.exe" in the SP Flash Tool Folder. (If at any time it shows a "Processing" window for some reason, just close and reopen the program if it doesn't go away on its own.)
On the first line choose "MTK_AllInOne_DA.bin". And the third line "Authentication File" can be left blank.
On the second line where it shows "Scatter-loading File", hit "choose" and find the "MT6765_Android_scatter.txt" file in the Step 6 folder. It'll load up and show a bunch of green/white rows in the space below.
Now this looked intimidating to me at first, but it's actually quite simple. As far as I understand (and I could be wrong but), the scatter file just tells the program where to place certain files, like a map for the program to follow. The scatter file I provided is for the UMIDIGI Power. The only thing we'll worry about for now is the boot.img file (but in the future, this is where you could also install a TWRP recovery once we get one that is confirmed to work.)
So in the white/green list, scroll down to where it says "boot" in the "Name" column, and click on the blank area in the "Location" column. It will bring up a window where you can browse to the "magisk_patched_boot.img" that I provided.
-----------------------------------
Step 7 - The Big Huzzah (Rooting)
Power off your phone and make sure it's UNPLUGGED. On SP Flash Tool, click "Download". This prepares the program to begin flashing your phone as soon as it is connected. Grab your phone with one hand, and with your other hand plug in the USB cable (if you only have one hand, use your mouth I guess). Your screen should not turn on at all throughout this process, but if it's successful, you should see that the program begins to flash your device after a second or two. Now just wait until it reaches 100% and says "Download Ok" with a green checkmark. And you're pretty much done!
You can then boot up your phone and check the Magisk app, as well as download a root checker from the Play Store to confirm that your phone has root access! Have fun!
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
mr A V said:
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
Click to expand...
Click to collapse
No problem! Unfortunately I don't see many custom ROMs coming to this phone, considering it's not a very popular device. I'd guess our best bet is to hope that the UMIDIGI F1 gets some support, and that anything on there can hopefully be ported over to this phone, but even that device isn't very popular either. For me though, that's not a huge issue because I'm actually quite satisfied with the stock firmware it has on board. It's basically stock Android Pie, and I've been able to add all the extra goodies I want into the phone through Magisk Manager and EdXposed with very minor issues. Most notably Viper4Android to fix the slightly tinny speakers and pump up the overall headphone experience too, and Gravity Box for some extra minor software customization.
Overall, I'd say the biggest downside to this device is the limited camera capabilities, and its somewhat limited performance for heavier tasks like 3D games / game streaming. But other than that, this feels like a very premium device. :good:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
mr A V said:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
Click to expand...
Click to collapse
I definitely consider myself to be a major noob with the more advanced Android development stuff. I only know enough to find my way around the internet and flash compatible software, haha. I've never looked into creating ports myself, but it's certainly something I think might be worth learning, especially with the limited device support on these phones.
And yeah, in terms of performance I don't expect much out of a phone at this price point, but for all the essentials - music, 1080p YouTube, web browsing, and mid to light gaming, it's surprisingly great considering the price. I haven't had any issues with the memory as of yet, so I wouldn't be too concerned, although you're definitely right in that they probably source some pretty cheap parts for these kind of phones.
SeekerofLight.iz said:
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
"stubbed guide"
Click to expand...
Click to collapse
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
---------- Post added at 09:30 AM ---------- Previous post was at 09:29 AM ----------
ghost45 said:
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE
Click to expand...
Click to collapse
Can i ask you a guide on how were you able to boot it? i'm only getting a bootloop after flashing that from SPFlash
I will build one other version of recovery soon...
mg95tux said:
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
Click to expand...
Click to collapse
Glad to hear it worked for you!
Still nothing. Unfortunately I haven't had any luck with booting into TWRP since I last tried it. Hoping ghost45 will be able to help us out with that when he gets the chance.
Bootloop - Secureboot
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Andre_Filho said:
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Click to expand...
Click to collapse
remember to allow oem unlock from developer settings in stock rom, otherwise it will fail!
SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Andre_Filho said:
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Click to expand...
Click to collapse
The trick to getting Viper4Android to work is to make sure you have SELinux set to "PERMISSIVE" rather than "ENFORCING" on your phone. Here's a handy little app designed to automatically set it to permissive on boot!
https://forum.xda-developers.com/devdb/project/?id=1561#downloads
And for BusyBox, I was having issues too at first because I think with systemless root, BusyBox can only be installed in /sbin, which gets wiped after each boot. So I searched for "BusyBox" in the Magisk app and found a module called "BusyBox for Android NDK" which has worked perfectly for me.
One thing to note...
Sometimes SELinux doesn't always get changed automatically everytime you boot up. It's pretty consistent, but every once in awhile you may need to manually set it to permissive mode again if things don't seem to be working. But it's literally just pressing a single button, so not a big deal.
The other thing is with Viper itself- At times when I launch the app, the driver status says "abnormal" even after I've toggled SELinux to permissive. If you go into settings and toggle "compatibility mode" or "attach audio effects" on and then off that seems to refresh the driver status. Not sure why, but it works.
Let me know if you have any issues.
TWRP for UMIDIGI POWER
I ask for help in creating TWRP for UMIDIGI POWER firmaware ROM v1.5
Please make for this model TWRP
I am very grateful to you - I unlocked the phone and got the rights Root rights.
It remains only to create a TWRP for UMIDIGI POWER
At this forum, competent specialists and for other models everything is already done.
Maybe there is a website where you can make an order to create a TWRP?
Unfortunately, I do not know English and I do not know how to apply.
I would be very grateful and ready to test your work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This method is based on Amazing Temp Root for MediaTek ARMv8 by diplomatic
Clever work that give MTK-soc devices a bootless root ( Root remains until reboot ). And lucky enough it works on our Nokia 5.1 Plus
So to begin :
-Grab diplomatic lastest mtk-su.zip in Amazing Temp Root for MediaTek ARMv8
- Follow instructions from Bootless root with Magisk and MTK-SU
#You can install Magisk Manager from the magisk 18.1 package, or any version below 7.1.2. Lastest version of MM doesn't work.
And your device should have root permission.
Hi stizzir,
Great post I've tried it and it works.
The only problem I had is that you can't use the latest version of Magisk Manager you
need to use the 7.0.0 version if not Magisk manager won't open after running the suboot.sh script.
I was wondering if with this we may be able to get full root and also turn the notch on and
off on devices that don't have the Full Bezel option in Display Settings or Developer Options.
Best regards,
voidRunner
I tried it as well and it works. Thanks for letting us know I've been checking these forums every week waiting for something like this. I also used Magisk 7.0.0 inside the 18.1 Magisk zip. Latest version didn't work.
@vddrnnr
The only problem I had is that you can't use the latest version of Magisk Manager you
need to use the 7.0.0 version if not Magisk manager won't open after running the suboot.sh script.
Click to expand...
Click to collapse
Wow good to know, i encountered that problem too, and you figure it out !
I was wondering if with this we may be able to get full root and also turn the notch on and
off on devices that don't have the Full Bezel option in Display Settings or Developer Options.
Click to expand...
Click to collapse
I don't think full root can be acquired since there are still no Bootloader unlock solution yet, really looking for that. N-tool devs are working on it and they said X5 unlock is coming soon. But the bootless root work fine ! couldn't complain anything, it's basically a rooted device.
I tried Adaway it didn't work first time but worked second time, After that it would not work again no matter what I tried, says not enough space on partition. I checked host file when it worked and it had changed. Titanium backup worked, SD maid worked. Looks like I was wrong you can't edit or delete anything in system folder.
@rustdroid
I tried it as well and it works. Thanks for letting us know I've been checking these forums every week waiting for something like this. I also used Magisk 7.0.0 inside the 18.1 Magisk zip. Latest version didn't work.
Click to expand...
Click to collapse
No problems, but again, all the credits go to diplomatic for his work, I'm just lucky enough to come across his thread.
Yes latest Magisk doesn't work, diplomatic had already mentioned it the original thread.
rustdroid said:
I tried Adaway it didn't work first time but worked second time, After that it would not work again no matter what I tried, says not enough space on partition. I checked host file when it worked and it had changed. Titanium backup worked, SD maid worked. Mixplore root worked I deleted Google drive app from system/apps but took a few tries and reboots for it to be uninstalled, the folder always restores after reboot.
Click to expand...
Click to collapse
This is just a temporary solution so don't expect much out of it.
The doors will be open once the Bootloader can be unlock
Yes I know and I'm happy with it until we can unlock bootloader. Hopefully they can find a way soon but this will do until then.
Can someone else with this phone try Adaway to see if it can edit host file or delete a system app like Google drive (move the app file in system/apps replace it after tested) ? Just want to see if I'm only one that can't edit system folder.
Edit: It's okay I just read that you can't modify System/Vendor partition unless boot image modified. Will have to wait until bootloader unlocked.
vddrnnr said:
Hi stizzir,
Great post I've tried it and it works.
The only problem I had is that you can't use the latest version of Magisk Manager you
need to use the 7.0.0 version if not Magisk manager won't open after running the suboot.sh script.
I was wondering if with this we may be able to get full root and also turn the notch on and
off on devices that don't have the Full Bezel option in Display Settings or Developer Options.
Best regards,
voidRunner
Click to expand...
Click to collapse
rustdroid said:
Can someone else with this phone try Adaway to see if it can edit host file or delete a system app like Google drive (move the app file in system/apps replace it after tested) ? Just want to see if I'm only one that can't edit system folder.
Edit: It's okay I just read that you can't modify System/Vendor partition unless boot image modified. Will have to wait until bootloader unlocked.
Click to expand...
Click to collapse
Man i just can't wait for the Bootloader unlock. Nokia obviously doesn't want to offer a official unlock service ( at least for now ) since the android one line-up is meant to be as stock as possible. The company also promised to support new Android One devices in the next 3 years, so allowing Bootloader unlock will work agains their product course i think.
I have seen many attempts from the community however, and i have trust in them, many devices get unlocked by a unofficial method so.... Wait for the good news.
@stizzie I can't wait, hate having a device that I don't have full control. I've asked Nokia on there forums and signed a partition that is closed now, That's all I can do and just wait. I read somewhere that Nokia will allow it soon but who knows how long. Hopefully someone finds another way soon.
Doing this won't kill OTA, right?
Rajeel911 said:
Doing this won't kill OTA, right?
Click to expand...
Click to collapse
Absolutely not
stizzie said:
This method is based on Amazing Temp Root for MediaTek ARMv8 by diplomatic
Clever work that give MTK-soc devices a bootless root ( Root remains until reboot ). And lucky enough it works on our Nokia 5.1 Plus
So to begin :
-Grab diplomatic lastest mtk-su.zip in Amazing Temp Root for MediaTek ARMv8
- Follow instructions from Bootless root with Magisk and MTK-SU
#You can install Magisk Manager from the magisk 18.1 package, or any version below 7.1.2. Lastest version of MM doesn't work.
And your device should have root permission.
Click to expand...
Click to collapse
Can I give permission to es file file explorer if yes than how??
And can I modify this partition Device/data/nvram/APCFG/APRDEB
Ranjhag said:
Can I give permission to es file file explorer if yes than how??
And can I modify this partition Device/data/nvram/APCFG/APRDEB
Click to expand...
Click to collapse
Just follow instructions in the provided links, you should have root permission. Applications working or not really depends on your device so it won't hurt if you try it yourself.
Device is Nokia 5.1 plus?
And sir can u tell me where I have to paste mku-su file? In the pc
I got OTA update today while this thing was running so no OTA issues.
Just 2 warnings:
1) Don't write even a single byte to system partition or boot partition.
2) Don't expect Netflix etc to work since it breaks CTS profile and basic integrity. Banking apps etc will whine for rightful reasons too.
Ilgazc said:
I got OTA update today while this thing was running so no OTA issues.
Just 2 warnings:
1) Don't write even a single byte to system partition or boot partition.
2) Don't expect Netflix etc to work since it breaks CTS profile and basic integrity. Banking apps etc will whine for rightful reasons too.
Click to expand...
Click to collapse
It doesn't let you do anything to system or boot partition. I tried editing and deleting and doesn't work. Have to wait until bootloader unlocked.
Rajeel911 said:
Doing this won't kill OTA, right?
Click to expand...
Click to collapse
rustdroid said:
It doesn't let you do anything to system or boot partition. I tried editing and deleting and doesn't work. Have to wait until bootloader unlocked.
Click to expand...
Click to collapse
If you (by chance) are able to write a single byte to system or boot partition on this dm-Verity enabled device, it won't boot and will need service center.
That changes if bootloader can be unlocked of course.
Ilgazc said:
If you (by chance) are able to write a single byte to system or boot partition on this dm-Verity enabled device, it won't boot and will need service center.
That changes if bootloader can be unlocked of course.
Click to expand...
Click to collapse
Okay thanks for the info. Guess I was lucky that you can't do anything. I tired to delete a few pre installed apps and edit the host file. Looks like this is as good as it gets until we can unlock bootloader.
Hi there,
So After seen many tutorials I wanted to proceed to unlock the bootloader of my Huawei Mediapad T5 , here are the specs
```
Model: AGS2-W09
Build No: AGS2-W09 8.0.0.360(OCEC431)
CPU : Hisilicon Kirin 659
Android Version: 8.0
```
I have downloaded the last build of `potatoNV` along with the SER Drivers ,
I have booted in untrusted driver mode (on Win10) and have installed `usbser.sys` as far as I recall
I proceed opening the Tablet from inside and shorting the "short point" and I get connection with the Computer , I installed the drivers , and tried on `potatoNV` with `Kirin 65x (A)` .
I get to the end of the progress bar , and then I get the problem as there is no confirmation that the process has been performed correctly. The connection dissapears , and If I try to boot on rescue mode and I do `.\fastboot.exe devices` or `fastbook.exe oem device info` it doesnt show no device at all.
Also the `rescue mode` menu says `Phone locked , FRP Unlocked` So I guess I had no luck
Please see the video on the link (note that the 2 takes are not synchronized)
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
What I may be possibly doing wrong ? May it be the USB connection (cables or connectors) ? or the drivers I downloaded?
Please any assitance will be appreciated.
Thanks
Maybe I can help you with this. Recently rooted this tab myself. Please give me a reminder tomorrow
Hey there I just saw the message . Please if you can guide me a bit of what I may be doing wrong? Also If there is a way to share the Drivers files that you used that would be great (I'm not sure if it was a matter of drivers or general clumsiness , please If you have a minute to check the video tell me what may be wrong on my "Technique") Thank you!!
freddieventura said:
Hey there I just saw the message . Please if you can guide me a bit of what I may be doing wrong? Also If there is a way to share the Drivers files that you used that would be great (I'm not sure if it was a matter of drivers or general clumsiness , please If you have a minute to check the video tell me what may be wrong on my "Technique") Thank you!!
Click to expand...
Click to collapse
Just saw your responce now (please use reply next time, I will get an notification then ).
The "Kirin 65x (A)" you've used is the correct bootloader. So guess it would have been something going on with the drivers or the procedure.
I recently (about 1 month ago) rooted this tab myself so I think I will have quite recent files for doing so. Maybe I can send them to you if you like. But I should have save the websites where I got them from too. But need to check it up for you then.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you have used the settings above?
You did had recieved the "New unlock code" message?
I have to go to work now, but I could help you further later this evening if you need further assistance
Rockel said:
Just saw your responce now (please use reply next time, I will get an notification then ).
The "Kirin 65x (A)" you've used is the correct bootloader. So guess it would have been something going on with the drivers or the procedure.
I recently (about 1 month ago) rooted this tab myself so I think I will have quite recent files for doing so. Maybe I can send them to you if you like. But I should have save the websites where I got them from too. But need to check it up for you then.
View attachment 5391207
Did you have used the settings above?
You did had recieved the "New unlock code" message?
I have to go to work now, but I could help you further later this evening if you need further assistance
Click to expand...
Click to collapse
Hi, thanks for assisting me. Yeah well, the version I used of PotatoNV(the last build) just had the option of Disable FBlock so I did that.
Also I tried wth a previous build that was showing both versions as you are showing and it happened the same thing.
My guess are more focused on 2 probable mistakes by my side either:
- When shorting the short point Im not doing it correctly. (not sure if this, as the device gets detected by PotatoNV and initiates the process)
- (Most likely thisone). Wrong drivers, I have downloaded them through a link found in a youtube video, and the video was not specific about this Tablet. Also there were a bunch of drivers within the same file so I installed one that looked like the correct one (but not 100% sure)
Anyways thanks for taking your time really and appreciate a reply but always whenever you find free time obviously. Take it easy today at work
freddieventura said:
Hi, thanks for assisting me. Yeah well, the version I used of PotatoNV(the last build) just had the option of Disable FBlock so I did that.
Also I tried wth a previous build that was showing both versions as you are showing and it happened the same thing.
My guess are more focused on 2 probable mistakes by my side either:
- When shorting the short point Im not doing it correctly. (not sure if this, as the device gets detected by PotatoNV and initiates the process)
- (Most likely thisone). Wrong drivers, I have downloaded them through a link found in a youtube video, and the video was not specific about this Tablet. Also there were a bunch of drivers within the same file so I installed one that looked like the correct one (but not 100% sure)
Anyways thanks for taking your time really and appreciate a reply but always whenever you find free time obviously. Take it easy today at work
Click to expand...
Click to collapse
Not sure, I should get into it again, but I'm not sure of potato is able to start the procesure or finding the divice if not shorted correctly.
Do you have a screenshot of your potato output/ results?
How are you performing the shorting procedure?
I can see if I can look for you for the right drivers tonight.
Rockel said:
Not sure, I should get into it again, but I'm not sure of potato is able to start the procesure or finding the divice if not shorted correctly.
Do you have a screenshot of your potato output/ results?
How are you performing the shorting procedure?
I can see if I can look for you for the right drivers tonight.
Click to expand...
Click to collapse
I hve uploaded the video which shows all the output and how Im shorting the point. The video though is composed by two takes and are not synced in time but that is how I do it.
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
Let me know if you can watch it on there. Thanks
freddieventura said:
I hve uploaded the video which shows all the output and how Im shorting the point. The video though is composed by two takes and are not synced in time but that is how I do it.
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
Let me know if you can watch it on there. Thanks
Click to expand...
Click to collapse
Oh yes, forgot about the video in the OP...
Seems you're folowing the wrong procedure with the shorting proces.
And seems your potato version is a bit outdated. But don't think this will be much of an issue.
- Your tablet needs to be turned off.
- cable removed from the tab.
- start potato
- then short the circuit (tab turned off).
- keep it shorted and insert the usb cabel (the other end should be in the computer already)
- the tablet starts (i believe in somekind of flash mode. And i believe you should not be able to see the Huawei logo in this procedure).
- after 2 or 3 seconds after booting, release the shorted circuit.
- i believe it should display you now some info about the tab itself in potato when you press start.
P.s. Don't forget to make a screenshot of the results or write down the newly given unlock code. So you can use it afterwards to lock or unlock your bootloader at a later moment, without opening the tab again.
P.s. 2 I just read in your comment that the recordings are not synchronised. So it's possible you were following the correct steps above. Correct me if I'm wrong please
freddieventura said:
I hve uploaded the video which shows all the output and how Im shorting the point. The video though is composed by two takes and are not synced in time but that is how I do it.
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
Let me know if you can watch it on there. Thanks
Click to expand...
Click to collapse
I'm home (finally)...
If the steps mentioned above didn't worked out, I would like to ask you to do axactly as I did. Just unlocked my Mediapad T5 just 1 month ago or so, so everything I've used should be recent enough I guess.
First:
- Un-install your potato version.
- Un-install your Mediapad T5 USB drivers.
So we can begin from scratch
Also:
- turn on OEM-unlock and USB-debugmode in developer settings.
I asume you have a decent and working ADB version installed on your PC?
If not, or when you're not sure, uninstall it too.
I was using the Minimal ADB and Fastboot from here:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Then:
1) Install the Huawei USB drivers from here:
Support area | files.dc-unlocker.com
(this) or (this) are the "official" sites I got this from.
2) Install the latest version of PotatoNV from here:
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
Open potatoNV and use these settings marked in red:
3) Plug the USB-cable into your PC already, but don't connect the other side to the tablet. And make sure your tablet is turned off.
4) Now short the testingpoint with a shielded part. I just used a thick copper wire and used it between testingpoint and metalshield just next to it. Metal pliers as used in your video should work too ofcourse.
P.S. I see that you also disconnected your screen in the video? It seems that it's verry important not to see a charging icon in the next step, so maybe it's better to connect it again for this step.
5) While still shorting the testingpoint with the shield, connect the USB cable to your tablet and be sure no charging icon pops up (This can be a bit difficult doing on your own. Easiest way is to have someone around te help in this step). After a few secconds when connected (without seeing an charging icon) remove the shorting between testingpoint and shield.
6) Make sure that the Huawei USB COM is selected in PotatoNV (and that the other settings are the same as the screenshot)
7) And pres "Start!"
8) You should get similar results now:
PotatoNV v2.2.1
User manual: https://kutt.it/pnv-en
Verifying images...
Uploading hisi65x_a...
- xloader
- fastboot
Waiting for any device...
Connecting...
Serial number: FQB***************
Board ID: FQB*************
Model: AGS2-W09
Build number: AGS2-W09 8.0.0.360(OCEC431)
FBLOCK state: unlocked
Saved key: 6BN**************
Writing FBLOCK...
Writing WVLOCK...
Writing USRKEY...
Rebooting...
New unlock code: 3BS*************
p.s. In your video it seemed your device got disconnected somehow while uploading. You should not see that "timeout" message here now annymore.
9) Make a screenshot of your results, copy them to a text file or write down at least your "new unlock code"
So you won't have to open your tablet annymore in the future. You can use this newly obtained unlock code now to lock and unlock your tablet without opening again.
10) You should now see a warning screen everytime you reboot the tab. It warns you about that the device can't be trusted annymore because of the unlocked bootloader.
You can also enter Fastboot to check it
Fastboot/ Bootloader mode:
1. Turn off the device by holding the Power key for a few seconds.
2. Connect tablet to PC/laptop using the USB-cable.
3. Hold down Volume-Down.
4. Hold down the Power button until device starts (while still holding Volume-Down and USB connected).
4. Tablet boots now into Fastboot-mode.
You should see the following screen then (pay attention on the 2 red lines at the bottom):
You can close your tablet now!
Rockel said:
I'm home (finally)...
If the steps mentioned above didn't worked out, I would like to ask you to do axactly as I did. Just unlocked my Mediapad T5 just 1 month ago or so, so everything I've used should be recent enough I guess.
First:
- Un-install your potato version.
- Un-install your Mediapad T5 USB drivers.
So we can begin from scratch
Also:
- turn on OEM-unlock and USB-debugmode in developer settings.
I asume you have a decent and working ADB version installed on your PC?
If not, or when you're not sure, uninstall it too.
I was using the Minimal ADB and Fastboot from here:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Then:
1) Install the Huawei USB drivers from here:
Support area | files.dc-unlocker.com
(this) or (this) are the "official" sites I got this from.
2) Install the latest version of PotatoNV from here:
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
Open potatoNV and use these settings marked in red:
View attachment 5391609
3) Plug the USB-cable into your PC already, but don't connect the other side to the tablet. And make sure your tablet is turned off.
4) Now short the testingpoint with a shielded part. I just used a thick copper wire and used it between testingpoint and metalshield just next to it. Metal pliers as used in your video should work too ofcourse.
View attachment 5391623
P.S. I see that you also disconnected your screen in the video? It seems that it's verry important not to see a charging icon in the next step, so maybe it's better to connect it again for this step.
5) While still shorting the testingpoint with the shield, connect the USB cable to your tablet and be sure no charging icon pops up (This can be a bit difficult doing on your own. Easiest way is to have someone around te help in this step). After a few secconds when connected (without seeing an charging icon) remove the shorting between testingpoint and shield.
6) Make sure that the Huawei USB COM is selected in PotatoNV (and that the other settings are the same as the screenshot)
7) And pres "Start!"
8) You should get similar results now:
PotatoNV v2.2.1
User manual: https://kutt.it/pnv-en
Verifying images...
Uploading hisi65x_a...
- xloader
- fastboot
Waiting for any device...
Connecting...
Serial number: FQB***************
Board ID: FQB*************
Model: AGS2-W09
Build number: AGS2-W09 8.0.0.360(OCEC431)
FBLOCK state: unlocked
Saved key: 6BN**************
Writing FBLOCK...
Writing WVLOCK...
Writing USRKEY...
Rebooting...
New unlock code: 3BS*************
p.s. In your video it seemed your device got disconnected somehow while uploading. You should not see that "timeout" message here now annymore.
9) Make a screenshot of your results, copy them to a text file or write down at least your "new unlock code"
So you won't have to open your tablet annymore in the future. You can use this newly obtained unlock code now to lock and unlock your tablet without opening again.
10) You should now see a warning screen everytime you reboot the tab. It warns you about that the device can't be trusted annymore because of the unlocked bootloader.
You can also enter Fastboot to check it
Fastboot/ Bootloader mode:
1. Turn off the device by holding the Power key for a few seconds.
2. Connect tablet to PC/laptop using the USB-cable.
3. Hold down Volume-Down.
4. Hold down the Power button until device starts (while still holding Volume-Down and USB connected).
4. Tablet boots now into Fastboot-mode.
You should see the following screen then (pay attention on the 2 red lines at the bottom):
View attachment 5391639
You can close your tablet now!
Click to expand...
Click to collapse
Thanks very much for your explanation , I will do this when I am back at home and let you know .
Cheers!!
freddieventura said:
Thanks very much for your explanation , I will do this when I am back at home and let you know .
Cheers!!
Click to expand...
Click to collapse
Are you btw sure that the pliers you used in in the video are making a circuit from one point to the other? Maybe worthwile to measure the resistance first?
I just used a thick copper wire and bended it to an easy to use U-shape.
Rockel said:
Are you btw sure that the pliers you used in in the video are making a circuit from one point to the other? Maybe worthwile to measure the resistance first?
I just used a thick copper wire and bended it to an easy to use U-shape.
Click to expand...
Click to collapse
Sorry Rockel I have been very busy this week , I'm gonna try and find a little bit of time to get this done this weekend . Thank you!!
freddieventura said:
Sorry Rockel I have been very busy this week , I'm gonna try and find a little bit of time to get this done this weekend . Thank you!!
Click to expand...
Click to collapse
No problem, take your time. Hope these steps wil solve your problem. Please keep me informed when you have time
Rockel said:
No problem, take your time. Hope these steps wil solve your problem. Please keep me informed when you have time
Click to expand...
Click to collapse
Do angels wear capes? because I haven't seen yours .
Much much much appreciate your help with this, I have just done it perfectly it didn't take me much time to do it.
Whatever I was doing wrong (probably the drivers , probably the shorting point thing not doing it properly) , whatever who cares!!.
I was also a bit not confident to do it that's why it took me time to get into doing it , but you definitely coached me with your messages .
Really thanks very much Rockel . For anything we keep in touch mate
freddieventura said:
Do angels wear capes? because I haven't seen yours .
Much much much appreciate your help with this, I have just done it perfectly it didn't take me much time to do it.
Whatever I was doing wrong (probably the drivers , probably the shorting point thing not doing it properly) , whatever who cares!!.
I was also a bit not confident to do it that's why it took me time to get into doing it , but you definitely coached me with your messages .
Really thanks very much Rockel . For anything we keep in touch mate
Click to expand...
Click to collapse
Hehehehe, thanks for your nice responce!
So I asume You've managed to root unlock the device now!
It was a pleasure assisting you in this.
If you need anny other information regarding this rooted device, please let me know. I'm not a pro with this. But had to solve a few problems myself. And came there with the help of others aswell.
What is the use of New unlock code?
do anyone have system, boot, cust, recovery, userdata.img with you i want to try with multi-tool to unbrick my tab
The unlock code can be used to unlock bootloader (using something like "adb oem unlock <code>" from PC)
I have saved the OTA folder form huawei system update app just before updating from 8.0.0.320(C432) to 8.0.0.371(C432), it can be found in /data/HwOUC folder after updater finished downloading. This version cannot be found on HuaweiFirmwareFinder site but I have temporary shared then here. Perhaps we could contact the authors to upload this version.
You can later use HuaweiFirmwareExtractor to extract different images from the zip files (no clue why there are 3 of them).
You need to disable "Verify Header checksums" in the "Settings" to open the extracted update.app files from the zips.
Good luck!
denzelcris said:
The unlock code can be used to unlock bootloader (using something like "adb oem unlock <code>" from PC)
I have saved the OTA folder form huawei system update app just before updating from 8.0.0.320(C432) to 8.0.0.371(C432), it can be found in /data/HwOUC folder after updater finished downloading. This version cannot be found on HuaweiFirmwareFinder site but I have temporary shared then here. Perhaps we could contact the authors to upload this version.
You can later use HuaweiFirmwareExtractor to extract different images from the zip files (no clue why there are 3 of them).
You need to disable "Verify Header checksums" in the "Settings" to open the extracted update.app files from the zips.
Good luck!
Click to expand...
Click to collapse
thank you .. but i extract app didnt uderstand which img file to install there no exact name for boot.img, recovery.img, cust.img, can you plz tell me which file equal to those file..
I don't think Huawei has boot.img or recovery.img, they may have a different layout and names (someone correct me if I'm wrong). I know the equivalent of boot.img is ramdisk.img or kernel.img (I flash both when restoring to be sure) and recovery should be recovery_ramdisk.img. The names from HuaweiExtractor should match with the images. Cust.img can be found in the other zip: update_full_AGS2-W09_hw_eu.
There is also this partition layout table which I don't know how it works for Huawei but I know that it may change for different firmwares so it is usefull to have remembered what version you had previously or use a safe tool to flash that also.