Related
I've found a way to register the G1 in the initial registration screen that comes up the first time you boot the phone (or after you wipe the phone). It will allow you to register if you don't have a sim card at all, or if you have a sim card but no data plan.
First, You must have either RC29 or earlier, or modded RC30. It won't work with official RC30, sorry. If you don't know for sure what version you have, but you know you haven't installed a modified RC30 build, then the easiest way to check is to reboot the phone, and once it starts up and is showing the "click the android to begin" screen, or the "no sim card" screen, then type the following on the phone keyboard
<enter>reboot<enter>
If it reboots, then you have RC29 or ealier. Otherwise you have RC30.
Second, you must have adb installed on your computer, and have the USB drivers installed, or at least ready to install when it asks for the driver when you connect the G1. See this page for details on how to get adb working: http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware
Third, you must have a wifi network that you can connect to.
There are too many possibilities to write specific step-by-step instructions for every case. So I will give an overview of the process instead. If someone else wants to write some specific instructions, that would be welcome
-----------
When you start up the phone without a sim card, it goes into a locked screen that says "no sim card found", and you can't even get into the registration app. So the first step is to get around that screen. You have to connect to your phone with adb shell and get root access, and then type the following command:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
And then reboot the phone. When it starts up again it will go into the registration screen instead of the locked "no sim card" screen.
This assumes that you have the sqlite3 binary on your phone. This binary is provided in RC30 v1.2. Alternatively, you could manually copy the binary to your phone with adb push, or put it on the sdcard and copy it to your phone. I can post a copy of just the sqlite3 binary if needed.
-----------
The second step is to enable and configure wifi, so that the registration process can connect to the google servers. In an adb shell session, type the following command:
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
This doesn't have to have root access to work. It works fine with the "shell" user that adb on non-modded phones runs as.
That command will bring up the settings page on your phone. From there, you can enable wifi and connect to your wifi network, and then proceed with registration as per normal
------------
A few tips and tricks:
- If you have an official RC29 or lower phone, type the following command on the phone keyboard to enable adb:
<enter>setprop persist.service.adb.enable 1<enter>
- If you need to get root access on an official RC29 or lower phone, while it's at the registration screen, or the "no sim card" screen, enable adb (see first tip), and then type the following command on the phone keyboard:
<enter>telnetd<enter>
Now, copy a busybox binary to /data/local/busybox with adb push, and then connect to your phone with adb shell, and give the busybox binary execute permissions (i.e. chmod 755 /data/local/busybox)
busybox has a telnet applet, so you can do:
busybox telnet 127.0.0.1
to get a telnet session with root access.
- If you don't want to register the phone at all, you can set the app.setupwizard.disable property to 0 to prevent registration. Once you have an adb shell session open, type the following:
setprop app.setupwizard.disable 1
and then reboot. once it loads back up, it should bypass the registration screen all-together.
But beware, the phone seems a bit glitchy if you don't have it registered. For example, the home button doesn't seem to work. And you can't access the market or any of the google apps of course.
(Note: the following was the previous way to skip registration. I'll keep it here for informational purposes, but its easier to use the app.setupwizard.disable method instead of this)
- If you don't want to register the phone at all, you can edit /data/system/packages.xml and disable the registration screen. Add the following to the end of the <package> section for com.android.setupwizard, and then reboot:
<disabled-components>
<item name="com.android.setupwizard.SetupWizardActivity" />
</disabled-components>
so the full <package> would look something like below after the modification:
<package name="com.android.setupwizard" codePath="/system/app/SetupWizard.apk" system="true" ts="1217592000000" userId="10010">
<sigs count="1">
<cert index="0" />
</sigs>
<disabled-components>
<item name="com.android.setupwizard.SetupWizardActivity" />
</disabled-components>
</package>
He worked on this for a very long time with me and walked me through all the steps when testing this out. Great person.
Really nice...
I'll try to do it.
I have to study though...
I'll be in touch.
Thanks
thanks JF you are good in this thing.
My case i have sim card without data plan, when turn on phone show me screen for register email account with google.
c:\adb shell
show me # simbol
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
and in the phone show me the menu for connect to my wireless
conected, registered, go ahead.
thanks
satru, in what screen are you typing "c:\adb shell"?
1. Before you click "the android"
2. while reading the agreement
3. When you can select "create" or "sign in" to a google account
4. Or later ? (where?)
Thanks
EDIT:
Ok, I hate to do that but:
I am completely stupid. I've been reading around xda-dev for hours and still can't find how to check what software I'm running. (prior or post RC30...)
In boot loader it says:
"DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.28
Sep 2 2008
Serial0"
Do I have RC30?
I couldn't get it out of bootloader mode, so I pulled the battery out.
Ok, my device was recognised and "installed" but no driver was requested.
I have read I need to do some settings from within the g1, but I can't, since it's not activated! (http://forum.xda-developers.com/showthread.php?t=443797&highlight=info)
When I issue the "adb devices" command, I get no recognised devices...
To cmavr, try entering the restore mode and see if the computer will detect it then. Is it automatically mounting the SD card onto the computer? If it is then you probably have RC19 which is good. Try removing the SD card and plugging the phone into the computer.
cmavr8 said:
satru, in what screen are you typing "c:\adb shell"?
1. Before you click "the android"
2. while reading the agreement
3. When you can select "create" or "sign in" to a google account
4. Or later ? (where?)
Thanks
EDIT:
Ok, I hate to do that but:
I am completely stupid. I've been reading around xda-dev for hours and still can't find how to check what software I'm running. (prior or post RC30...)
In boot loader it says:
"DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.28
Sep 2 2008
Serial0"
Do I have RC30?
I couldn't get it out of bootloader mode, so I pulled the battery out.
Click to expand...
Click to collapse
A quick way to check if you have RC30 is to reboot the phone, and then once it starts up and it shows the "click the android to begin" screen, type
<enter>reboot<enter> on the phone keyboard.
If it reboots, you have RC29 or lower. Otherwise you have RC30.
If you do have RC29 or lower, then you can use the first tip I posted to enable adb. Once adb is enabled it should ask you to install the drivers when you plug it in.
satru said:
conected, registered, go ahead.
thanks
Click to expand...
Click to collapse
Great! Glad it worked for you
Hi again, thanks for your reply.
I rebooted without sim card, no "click here to begin" appeared, just the "no sim card" notice.
I entered reboot and it rebooted! So this is good.
Now, with the phone connected, I type in terminal:
"[email protected]:/media/Docs/Android/tools$ ./adb shell
error: device not found
[email protected]:/media/Docs/Android/tools$ ./adb devices
List of devices attached
[email protected]:/media/Docs/Android/tools$ "
This is not normal, is it?
What should I do now?
(I also have a t-mobile sim card, not activated. It just came with the phone. I can go through the activation proccess (gmail account etc) but it can't complete as it's disabled)
cmavr8 said:
Hi again, thanks for your reply.
I rebooted without sim card, no "click here to begin" appeared, just the "no sim card" notice.
I entered reboot and it rebooted! So this is good.
Now, with the phone connected, I type in terminal:
"[email protected]:/media/Docs/Android/tools$ ./adb shell
error: device not found
[email protected]:/media/Docs/Android/tools$ ./adb devices
List of devices attached
[email protected]:/media/Docs/Android/tools$ "
This is not normal, is it?
What should I do now?
(I also have a t-mobile sim card, not activated. It just came with the phone. I can go through the activation proccess (gmail account etc) but it can't complete as it's disabled)
Click to expand...
Click to collapse
Did you try my first tip to enable adb?
johnny13oi said:
To cmavr, try entering the restore mode and see if the computer will detect it then. Is it automatically mounting the SD card onto the computer? If it is then you probably have RC19 which is good. Try removing the SD card and plugging the phone into the computer.
Click to expand...
Click to collapse
Thanks for your reply.
SD mounting works fine.
In recovery mode nothing is better... (tried recovery without sd only)
Is there anything else I should try?
JesusFreke said:
Did you try my first tip to enable adb?
Click to expand...
Click to collapse
What do you mean enable?
I should enable it on the g1 but it's locked, no menus available.
I thought the first step was to enter the "adb shell" command in the PC, then pass this through the pc to the G1:
"sqlite3 /data/data/com.android.providers.settings/settings.db INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
Am I missing something?
cmavr8 said:
What do you mean enable?
I should enable it on the g1 but it's locked, no menus available.
I thought the first step was to enter the "adb shell" command in the PC, then pass this through the pc to the G1:
"sqlite3 /data/data/com.android.providers.settings/settings.db INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
Am I missing something?
Click to expand...
Click to collapse
A couple of things:
- Look further down the post, there's a "tips and tricks" section. The first tip is how to enable adb.
- second, I don't think you need to go through the first step (the sqlite3 command). The first step is to get past the "no sim card" screen. You said you have a sim card, just no data plan, right? So you don't need to get past the "no sim card" screen . You can skip to the second step (once you get adb working, of course)
DID IT!
Thanks so much!!
I now have to wait for the unlock code so that I can also use my sim card...
Thanks both of you!
EDIT:
T-mobile sent me the unlock code although I was not a customer for even one day!
That's great...
Great! Glad you got it working
cmavr8 said:
EDIT:
T-mobile sent me the unlock code although I was not a customer for even one day!
That's great...
Click to expand...
Click to collapse
how?
thanks
xaxis said:
how?
thanks
Click to expand...
Click to collapse
Probably by getting lucky and getting a nice CSR
JesusFreke said:
Probably by getting lucky and getting a nice CSR
Click to expand...
Click to collapse
man thank god you are here,
do i need the SDK installed to get the adb?
thank you
Yes, adb is included in the sdk
Did you ever get "This device was reset. To continue, sign in with a Google Account that was previously synced on this device."?
Italian version: "Questo dispositivo è stato reimpostato. Per proseguire, accedi a un account Google già sincronizzato con il dispositivo."
It is a new protection on some phones starting from Android 5.1.
If you have resetted the password of your account after a factory reset it won't accept it also if it is correct.
IMPORTANT: Do not use this guide if the phone isn't yours.
After various attempts I was able to unlock it. Tested on Huawei with Android 5.1.1 but it possibly works also on other configurations with minor changes.
Requirements:
- The locked phone (obviously)
- Internet on the phone with the SIM or Wireless
- A normal USB cable
- A PC with adb installed
Procedure:
1) Start the phone and go all the steps until you see the hated message
2) Now tap on the place where you usually instert the mail so the keyboard will appears
3) Hold the Swipe icon on the keyboard until "Huawei Swipe" is opened
4) Tap on Help, then Version, then Swipe
5) Tap on www.swype.com
6) Tap on Browser, then select always
7) Now search: nova launcher 4.0.2 apk
8) Download the one from apkmirror
9) Go in the downloads on the browser, tap on com.teslacoilsw.launcher-4.0.2-40200-minAPI16.apk and install it
10) After the installation open it and now you can access Android (although is temporary)
11) Now go in the settings, then tap "info about the phone" and tap 7 times on "serial number" to enable developers options.
12) In the developers options enable Debug USB
13) Connect the phone to the pc
14) On the pc run: adb devices
15) On the phone it should ask to accept the pc, tick the options to keep the setting and accept it (if you don't get it then you have done something wrong)
16) On the phone open the browser and search kinguser, download the one from http://kinguserapk.com/download.html, install and open it
17) On the phone complete the procedure to get root access and set the options to consent root access to adb (sometimes the software give and error about this, try various options because we absolutely need this)
18) On the pc run:
Code:
adb shell
su
rm /data/system/locksettings.*
rm /data/system/*.key
rm /data/system/accounts.db
rm /data/system/sync/accounts.xml
rm /data/system/sync/status.bin
rm /data/data/com.google.android.gm/databases/*
rm /data/data/com.google.android.gsf/databases/*
rm /data/data/com.google.android.gms/databases/*
rm /data/data/com.google.android.talk/databases/*
19) On the phone go in the settings then go in the app list and terminate all these:
Code:
Google Account Manager
Google Backup Transport
Google One Time Init
Google Partner Setup
Google Service Framework
20) On the phone go in the account and add a Google account (if you have done everything correctly it don't show the annoying messages) and leave it syncing
21) Now restart the phone and re-do the setup wizard but now instead of asking for a Google account it will auto-login (this step is essential)
22) In the real world scream outside the window about your success and you are done, this is the most important step
This is Googles Factory reset protection and tut on how to bypass it are all over the place. Also this only works on this device. It has been patched by google about 3 months ago in a security update.
I have tried other procedures and it weren't working on this phone.
I have tried to update the ROM and it say it is the latest version so it still works.
ale5000 said:
I have tried other procedures and it weren't working on this phone.
I have tried to update the ROM and it say it is the latest version so it still works.
Click to expand...
Click to collapse
That is because it is a security hole that oem caused and it will only work on that device for now. A security hole with that oem is not surprising or new really.
zelendel said:
That is because it is a security hole that oem caused and it will only work on that device for now. A security hole with that oem is not surprising or new really.
Click to expand...
Click to collapse
Beside the initial security hole (that hopefully can be replaced by others) almost all guides end in another factory reset that on this phone do not solve the issue.
Instead I have opted to add a Google account and make the phone accept it.
TVPad 4 is fourth in a series of Android-based IPTV settop boxes targeting the worldwide Chinese communities at large, although it seems to work well as a basic Android TV box. Support for all its predecessors (TVPad 1-3) have been discontinued. This guide will only focus on TVPad 4, model M418. Also this device have been banned from US and upgrading it may "brick" it - more on this later.
The method I used below is gathered from various sources elsewhere but not much on rooting and ADB. This is a compilation of all the most important info in one place. I am not sure if its bootloader is locked or not, but the Android 4.4 kernel sources can be found at openlinux.amlogic.com.
Physical specs:
AmLogic S805 SoC: ARM Cortex-A5, quad-core 1.5Ghz, Mali450 graphics, 1080p H.265 support
~1GB RAM
microSD card slot
HDMI out
USB-A port
Hardware needed:
To fully complete the process you'll need:
Monitor/TV with HDMI port
USB hub
microSD card
USB drive (optional)
USB keyboard
USB mouse
The remote that came with your box
Files needed:
* TVPad 4 5.054 firmware + TWRP 2.8.1.0: https://tvpadtalk.ca/discussion/1071/downgrading-tvpad-4-to-5-054/p1
The TWRP seems to be the modified from the one for AmLogic k200. Only the one from above work; the one from TWRP themselves do not.
* TVPad 4 5.066 OTA update: http://www.phoneunlock.com/forum/viewtopic.php?f=5&t=590
If you have this box and are in the US, do NOT do 5.066 update; your box is going to be banned. Might as well go all out and repurpose it into a general purpose Android TV box; but for the rest of the world, this update directs your box to different servers where it's mostly business as usual. You should be able to go direct from 5.054 to 5.066 following this guide, despite what others say.
* Root zip: http://www.freak-tab.de/finless/s89_root_update.zip
* APK install hint file:
Create a file named batchinstall.banana with contents below:
Code:
directory=
checkapp=no
Preparation
1. Download the 5.054 firmware and unzip into root of your microSD card. You should have recovery.img and TWRP folder. They are the TWRP recovery and a 5.054 TWRP backup respectively. Devices boots from recovery.img on root of microSD card if detected.
2. NON-US ONLY: Download the 5.066 OTA update to microSD root.
3. Download root zip to microSD root.
4. Put batchinstall.banana and any APKs you want to install on your USB drive or microSD. There is a APK pack of 23 apps for Cantonese speakers or 29 apps for Manadarin speakers available out there, but I haven't bothered. I included an updated SuperSU, ES File Explorer (preferably an older version; I used 4.0.4.9; newer ones are heavily loaded with ads), VLC, Firefox, AdAway, Terminal Emulator (by Jack Palevich). The last 4 being open source should also be available from F-Droid. Substitutions can be made to taste but Terminal Emulator is required to enable ADB (see below).
Enter Recovery
You will need to use stock recovery for OTA update AND TWRP for 5.054 firmware and root.
1. Connect HDMI monitor and USB hub to device. Connect USB keyboard and mouse to the hub. Leave power disconnected.
2. Look for a hole on the underside. If you have one, stick an iPhone/iPad SIM ejector pin in it and feel for a button. If able, this is the recovery button and you may skip to step 6.
3. Pull off the 4 rubber feet on the bottom and remove 4 screws under them.
4. Pry around the seams and lift the bottom cover off.
5. You either have a recovery button on the PCB or an empty spot for it. If no button, you'll have to short the bottom two contacts where the button is supposed to be (with all ports on the top edge).
6. Insert microSD card into "TF" slot. IMPORTANT: Leave popped out to enter stock recovery; fully insert to enter TWRP.
7. Press and hold the recovery button (or short the contacts) while plugging it in. Keep it pressed (or contacts shorted) until the recovery or TWRP appears.
8. Operate stock recovery with keyboard and TWRP with mouse.
Re-flash 5.054 - Downgrade/Unbrick
People do this to recover from "use restricted" or some other server errors after this thing is sued out of the States. I have also used it to recover from a soft brick situation.
1. Fully insert microSD card. Enter TWRP.
2. Select Restore. Choose External SD for storage.
3. Select the only available package to restore.
4. Swipe to Restore.
5. When complete, do not reboot yet. Return to main menu and select Wipe. Swipe to Factory Reset.
6. US ONLY: Remain in TWRP and proceed to step 2 of rooting.
7. NON-US ONLY: Return to main menu and select Reboot, Recovery. Immediately after screen go blank, push the microSD card again to eject it. It will pop out half way. Leave it hanging there. Proceed to update 5.066 next.
Update to 5.066 - NON-US ONLY! New server and Play Store support.
1. Enter stock recovery.
2. Fully insert microSD card.
3. Select Apply update from EXT and press Enter.
4. Select your 5.066 update file and press Enter.
5. When update complete, unplug power. Proceed to rooting.
Rooting
This is too easy with TWRP.
1. Fully insert microSD card. Enter TWRP.
2. Select Install, then the root zip file. Swipe to install.
3. Reboot into system and proceed with initial setup.
Kingroot also works but leaves some very persistent crap and questionable apps on the system so I do not recommend rooting using it.
Sideload apps
Plug the USB drive with your apps and batchinstall.banana file into the device or hub. Batch installer will appear. Select Batch Install and check that all apps you are installing are there and checked, then select Install.
Enable ADB
TVPad 4 does not have a USB slave port so ADB is only through TCP/IP. Steps below assume you have adb working on your computer.
1. Connect a USB mouse if not already.
2. Move mouse to right half of top of screen then drag down. Click on the gear to enter regular Android Settings app.
3. Enable Developer Options - About Mediabox, click Build Number 7 times.
4. Enable USB Debugging in Developer Options.
5. Open Terminal Emulator (sideload it if you haven't already).
6. Type in the following:
Code:
$ su
(Grant root if prompted)
# setprop service.adb.tcp.port 5555
# mount -o remount,rw /system
(Make the same setprop change in /system/build.prop - uncomment or add the line)
# stop adbd
# start adbd
7. Find the IP address of your TVPad from its own over-simplified settings page.
8. Open a command prompt/terminal on your computer and do this:
Code:
> adb connect <TVPAD IP ADDRESS>
(Authorize your computer on the TVPad.)
> adb devices
(confirm its IP is listed and not "unauthorized")
> adb shell
$ su
(grant root if prompted)
#
(success!)
# chmod 660 /data/misc/adb/adb_keys
(Double check permissions the public key file of authorized ADB clients)
9. Reboot and check that the change stays.
You're done! Now you have full control of this little TV box even after its server go under for good.
Additional apps
Kodi 15.2 seems to work on this box. 16.1 is untested. 17.x will not work since it requires Lollipop. Download from kodi.tv.
If all you want out of TVPad is TVB programming, the official app TVBAnywhere works on this box. About US$100/yr subscription for its own original programming only. Oh and it doesn't serve the States either. Go figure.
The gapps framework added with 5.066 is very minimal and doesn't work for eg. maps. You'll need to get it from apkpure. Use version 11.0.38-030-155006848.
I'm still looking for a decent launcher.
Credits:
https://www.youtube.com/watch?v=6evvWebosnU
https://www.youtube.com/watch?v=ZtY_qdYzmPs
https://www.youtube.com/watch?v=W2heIbUdZVE
can we flash any other rom on TVPad 4 since we can install TWRP??
I rooted easily with kingroot apk. to get shell, I just used my laptop as proxy between wifi and lan, created a meterpreter reverse_tcp metaploit payload, connected back to my laptop, shell and then su...
3vilhomer said:
can we flash any other rom on TVPad 4 since we can install TWRP??
Click to expand...
Click to collapse
To be honest, I'm more interested in if we can get Lollipop on this thing, for that is required for Kodi 17.
For whatever reason I can't boot into the TWRP. I have all the recovery.img and TWRP folder located in the root directory of the SDcard and my SDcard is FAT32 formatted. What did I do wrong?
Suppport has been officially terminated for this box so, it will only be a normal TVbox.
I'm kinda wondering if the SoC supports at least lollipop. A custom rom would be cool to run Leanback apps with a few modifications
ya, is there anything we can do with this box now since most live tv apps doesnt work on it anymore
Do you know where I can grab the file for TVPAD1? I am not sure which model I have, is only written TVPAD on top and there is no 2S, Plus or anything else.
TvChina, a subsidiary pay TV app after TvPad 4 ceased operating on June 1st. TvPad, the parent company, together with its Blue TV etc, have gone bust due to lack of funds from global dwindling sales. Now that the box is useless, can someone upload a root file so we can wipe then reuse it for other purposes? Found a related message on Google but it's has been blocked. Thanks in advance. Wonder if someone can get hold of firmwares for UnBlock or evPad etc so we can tune this into other sites.
did anyone ever put a different android OS on this and got the IR blaster to work too??
3vilhomer said:
did anyone ever put a different android OS on this and got the IR blaster to work too??
Click to expand...
Click to collapse
They were able to upgrade to android lollipop here:
tvpad.ca/discussion/1993/tvpad4-upgrade-to-android-lollipop-5-1
The root file "s89_root_update.zip" link is not working anymore. Does anyone has a copy > please post it here.
Goal has been successfully achieved by a little bit of research and careful experimentation. Got to the middle of this post to find the complete solution.
I have a 4g Router Model: R660 also called 4g Wingle. The manufacturer is unknown as there is no branding on the device. But some say it is a GadgetIT product. I have scoured the internet and I cannot find the vendor named GadgetIT. But that is a separate discussion.
Main Goal: My main goal is to enable Virtual Server/Port forwarding in the device. The UI available when the device is connected is available at 192.168.1.1 with credentials admin/admin and Looks like this:
{
"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 device is marketed by ISP PTCL as CHARJI EVO . The users of PTCL charji on this forum might say that port forwarding is not possible in this device but I disagree. and I have evidence to support otherwise but again that is a separate discussion.
What I have found so far?
I am able to telnet to this device at 192.168.1.1 via admin/admin credentials. Here is what I get.:
Version
LNX.LE.4.1-41009-9x35
But admin is not root. There is a separate user called root which obviously has a different password. I have tried all common router password (not sure what all will constitute...but i have tried many).
The goal here is to root this device so that I can perform the necessary changes such as the following:
As you might have guessed by now, that i cannot unless I am root which I am not.
So I need your help guys. Here are other interesting things to look at:
I could edit mobileap_cfg.xml but I cannot because the file is readonly and I was unable to chmod it to 777 with an error message "Operation not permitted" indicating that I am not root and I can not make that happen.
The second thing i would like to do is to enable SNMP monitoring which I cannot do from the main interface because the vendor hid the option.
Lastly, enable firewall.
Interestingly, all these options are available in a tab called "Security" which the vendor has hidden from the configuration interface available at 192.168.1.1
So I am inviting the expert comments of all hackers that can help me make get it sorted out. Ideally, it would be awesome to have these options enabled from the UI (I am willing to hack, root this device and modify firmware if needed) to get this done.
This can potentially help millions of PTCL Charji Users who cannot run any kind of server using this device (including game servers) and any kind of listening services (sockets or WEB or FTP) r those who would like use torrents but suffer from terrible low download speeds on torrents because of not being able to open ports for incoming connections that significantly raise download speeds for torrent.
More details:
mobileap_cfg.xml ownership and permissions:
Appreciate your help. Waiting to hear helpful responses soon. Successfully rooted without any busy box.
Solution Achieved successfully- See Steps & detail as follows:
I was able to switch device to bootloader mode and was able to change root password and now I am able to switch to root mode when logged in via admin using telnet. I have successfully change the DMZ but i have yet to observe its effects. If it works, I will work on changing other values as well.
Detail:
The device closely resembles D-Link DWR 901 But mind you, it is NOT DWR 901. Even thought the radio matches, if you flash the firmware from DWR 901 (which will be successful), the device will NOT work. Since there is no available source of the original firmware of the device, the device will be of no use anymore. So do not do it.
Similary D-Link's DWM 222 is also similar to this device (only that DWM 222) is a 3G modem. I downloaded both firmwares and found out upon extraction of these firmwares, that it contains the following files.
Files that you actually need are present in this archive -
WARNING
Use at your own RISK!!. Flashing this directly to your Charji will brick you Charji device. So just follow the procedure I described and do not try to flash it directly otherwise it will render your device unable to connect even though everything will look all right in the software. The device will never connect again...ever!
https://www.dropbox.com/s/hqa2m4499pyrj3z/R660A-Donot-Flash-it-On-Charji-It-Will-Brick-Your-device.7z?dl=0
There is a file called dl.exe which can turn the device into download mode assumung you have the PTCL Charji Wingle R660 plugged into the USB port.
After that running adb devices command will list all the devices.
After that you need to run the following commands
Code:
adb shell
passwd
The adb shell command will take you to the shell.
The passwd command executed from shell will tell you to enter a new password for root user
You will have to provide a secure password for it to be accepted.
After that, it will update the root password.
exit the shell using the exit or quit command or simply close the command prompt.
Now, you can telnet to the device using the command
Code:
telnet 192.168.1.1
Login with username admin and password admin (if these are your credentials to access the router page, Use your credentials. Mine were admin/admin)
The issue the following command to switch to root mode
Code:
su
It will ask for root password. Enter the password you set using the adb shell you had used before. and viola. You will turn to root mode.
You you have two ways to fix the NAT/DMZ problem.
Either you can directly use the vi editor (my OpenEmbedded Linux OS installed on the device has only vi support) to edit the file mobileap_cfg.xml and update DMZ value and port forwarding values.
or you can enable the security tab by editing the menu.js file which is located in /WEBSERVER/www/ directory. Now I had a PTCL Charji R660. If you have a different device, your files will be located elsewhere with different sets of issues.
You can do whatever you want!
Older Updates
Update# 02:
DMZ is now working !!
Update# 03
Successfuly unlocked the hidden security tab but still untested. Will test it shortly.
Update # 04
Successfully unlocked Wizard
Update# 05
NAT Rules persisting and working, tested by download torrents and using CanYouSeeMe.ORG
Torrents Downloads working on max available speeds
Reserved 1
Reserved for additional instructions etc
Reserved 2
Good find but instructions are really ambiguous and unclear. What are you supposed to do with dl.exe? run it, stare at it, run it and press enter????
You are just trapping people into bricking their devices with this instruction.
Yes I am bad at providing instructions.
dl.exe once run, turns the charji into bootloader mode and then it is possible to run adb shell and adb commands.
Hope this helps. I will update the article to be more descriptive in future sometime. Don't have time right now.
Regards.
timematcher said:
dl.exe once run, turns the charji into bootloader mode and then it is possible to run adb shell and adb commands.
Click to expand...
Click to collapse
Ok you are still not being clear. What do you mean by run once? currently dl.exe shows
Code:
Welcome to use OnekeyUpdate Tool.
The Software to be updated:Desktop
Press 'Enter' to update or 'Q' to quit.
on opening. Should I press Enter?
Sorry about being rude in first comment. I am really angry right now over this device right now, what kind of stupidity is not allowing user to port forward.
raza1080p said:
Ok you are still not being clear. What do you mean by run once? currently dl.exe shows
Code:
Welcome to use OnekeyUpdate Tool.
The Software to be updated:Desktop
Press 'Enter' to update or 'Q' to quit.
on opening. Should I press Enter?
Sorry about being rude in first comment. I am really angry right now over this device right now, what kind of stupidity is not allowing user to port forward.
Click to expand...
Click to collapse
When you click Enter, it will say "Waiting for device...." and then "found"
That is the point the device will appear in device manager (on windows) as well. and Now is the time to run adb shell and corresponding commands in my first article.
Important thing to note is that if you have never rooted any android (or linux) based device/phone/tablet, I suggest you read more about running adb.
The goal of my article was the following:
1. reset root password on the OpenEmbedded Linux variant on teh charji wingle device
2. Login via Telnet to 192.168.1.1 (Charji web console) using admin/admin (default credentials of Charji)
3. change to root mode using su command
4. Be able to change the xml files ( i mentioned in the first post) that allow the user to create the firewall rules and virtual server entries.
Now at this point I did not know that the person who whitelabelled Charji wingle for PTCL simply had disabled the relevant code in menu.js that enabled the Virtual server entries and firewall entries and DMZ fields (that allow pot forwarding, open firewall or simply set an ip address for DMZ that opens everything to a single IP on charji local network).
Once I found out, I was really happy and now I created the virtual server entries for torrent which was my main problem.
Thanks to Dr.hack who created a proper tutorial on his blog based on information in this article in a more streamlined manner.
Dr. Hack's Blog, Root-hack-ptcl-charji-evo-nat/
thank you for the tutorial.I am trying it on a charji cloud R500A. when dl.exe finds the device it goes to "6% Downloading hex image" .Am i suppose to wait at this point?
And will i be able to use other sim on the the device after the root?
Tarar said:
thank you for the tutorial.I am trying it on a charji cloud R500A. when dl.exe finds the device it goes to "6% Downloading hex image" .Am i suppose to wait at this point?
And will i be able to use other sim on the the device after the root?
Click to expand...
Click to collapse
First things first!, Are you trying to flash the image from the firmware link I gave? You should really not do that!
The link i gave is only provided for firmware modding experts. It is not the firmware of Charji. So if you flash it, it will brick your device and it will become useless.
What you really need to use is th dl.exe file , copy it into a separate folder with no other stuff in it.
If you run it from the same folder, it will brick your device by flashing a firmware which will not work for your Charji. CHarji will never connect after that!
dl.exe must be run to turn the device into booloader mode, After that you have to run adb shell commands and make the necessary changes to reset the root user password.
I don't know if it will allow you to use another SIM or not. PTCL devices are usually NOT network locked. But again, this is not a tutorial for allowing the users to use another sim. It merely allows the user unlock Virtual Server, Firewall, DMZ settings and similar features which are hidden by PTCL.
And there is no such thing as "Telenet". Telnet is a client application in windows which is not installed by default. You will have to install Telnet Client from "Add Remove programs" in Windows. It is needed to access the device using the telnet protocol. Do some research on Telnet.
timematcher said:
First things first!, Are you trying to flash the image from the firmware link I gave? You should really not do that!
The link i gave is only provided for firmware modding experts. It is not the firmware of Charji. So if you flash it, it will brick your device and it will become useless.
What you really need to use is th dl.exe file , copy it into a separate folder with no other stuff in it.
If you run it from the same folder, it will brick your device by flashing a firmware which will not work for your Charji. CHarji will never connect after that!
dl.exe must be run to turn the device into booloader mode, After that you have to run adb shell commands and make the necessary changes to reset the root user password.
I don't know if it will allow you to use another SIM or not. PTCL devices are usually NOT network locked. But again, this is not a tutorial for allowing the users to use another sim. It merely allows the user unlock Virtual Server, Firewall, DMZ settings and similar features which are hidden by PTCL.
And there is no such thing as "Telenet". Telnet is a client application in windows which is not installed by default. You will have to install Telnet Client from "Add Remove programs" in Windows. It is needed to access the device using the telnet protocol. Do some research on Telnet.
Click to expand...
Click to collapse
Thank you so very much for the details.
Yeah i found out about telnet commands.but i was using the dl.exe in the same folder.i guess that's why adb devices wasn't able to find my device.
Luckily it didn't install that firmware.
I have bricked my device by accidentally runing the gui.exe and i was dont know that it will flash new firmware. is there any way to get back ?:crying:
If you are able to switch to fastboot mode and you have the original software in the right format, then you should be able to flash the new firmaware using the utilities provided in the original post. The only way I think. I will try to see if I can create an image for my Charji R660 but I can not promise anything.
Note that I bricked first of mine and I took it to the people who upgrade firmware of the device and they were unable to fix it. and I got a new one by being sneaky (and playing dubm) about it.
Or if you want to learn, maybe start experimenting a little bit but I think you will need the original firmware.
timematcher said:
When you click Enter, it will say "Waiting for device...." and then "found"
That is the point the device will appear in device manager (on windows) as well. and Now is the time to run adb shell and corresponding commands in my first article.
Important thing to note is that if you have never rooted any android (or linux) based device/phone/tablet, I suggest you read more about running adb.
The goal of my article was the following:
1. reset root password on the OpenEmbedded Linux variant on teh charji wingle device
2. Login via Telnet to 192.168.1.1 (Charji web console) using admin/admin (default credentials of Charji)
3. change to root mode using su command
4. Be able to change the xml files ( i mentioned in the first post) that allow the user to create the firewall rules and virtual server entries.
Now at this point I did not know that the person who whitelabelled Charji wingle for PTCL simply had disabled the relevant code in menu.js that enabled the Virtual server entries and firewall entries and DMZ fields (that allow pot forwarding, open firewall or simply set an ip address for DMZ that opens everything to a single IP on charji local network).
Once I found out, I was really happy and now I created the virtual server entries for torrent which was my main problem.
Thanks to Dr.hack who created a proper tutorial on his blog based on information in this article in a more streamlined manner.
Dr. Hack's Blog, Root-hack-ptcl-charji-evo-nat/
Click to expand...
Click to collapse
Hi dear friend how are you? I need original webui of PTCL Charji device For Huawei Ec8372u-876 device please can you share the link or any guidance for this
saqi755 said:
Hi dear friend how are you? I need original webui of PTCL Charji device For Huawei Ec8372u-876 device please can you share the link or any guidance for this
Click to expand...
Click to collapse
Or any other links of non modified original Loced Huawei firmware and Webui
Huawei Ec8372u-876 is a very good device compared to sh!t devices offered by PTCL before.
Here is what I have found on the web.
Its probably an unlocking solution and not a locked file.
I am in no way responsible for the quality of the file or the steps as I dont have this device and I can not test it before posting.
Please use these are your own risk. I at least downloaded the file and executed on local PC.
but that is pretty much it. Please use at your own risk.
PTCL Evo Charji Cloud
E5377u-872
How to Unlock Evo Charji E5377u-872
1: Battery Should be 100% Charged
2: Data Cable
3: A Pin
4. Unlocked file
Click to expand...
Click to collapse
Code:
www.mediafire.com/file/6td2bh12b4l6g9o/PTCL_charji_E5377u-872-www.hispeedsolution.com.exe/file
Process>>
1. Remove the battery from the device
2. Press & Hold Power Button + Reset Button on the same time after 5 seconds device will boot into download mode.
3. Connect to PC
4. Wait for drivers
5. After the drivers installed go to device manager & note down the port # namely appplication UI interface.
6. Run the *.exe file & enter the port # (E.g 19 or 20 or etc etc)
7. Let it flash the device, it will take about 5 minutes, after the flashing let the device reboot. Your device will stuck on the Huawei screen, Don't worry wait for 3 minutes then remove the battery insert any Sim card & turn on the device.
8. Your device is successfully unlocked on all network Sim.
9. Connect the device to PC & set up accordingly.
Click to expand...
Click to collapse
timematcher said:
Huawei Ec8372u-876 is a very good device compared to sh!t devices offered by PTCL before.
Here is what I have found on the web.
Its probably an unlocking solution and not a locked file.
I am in no way responsible for the quality of the file or the steps as I dont have this device and I can not test it before posting.
Please use these are your own risk. I at least downloaded the file and executed on local PC.
View attachment 5369881
but that is pretty much it. Please use at your own risk.
Code:
www.mediafire.com/file/6td2bh12b4l6g9o/PTCL_charji_E5377u-872-www.hispeedsolution.com.exe/file
Click to expand...
Click to collapse
Thanks for your cooperation but I need file for Ec8372u-876 this file is not working on this please check this again this is not a device with battery
Let me look into it.
timematcher said:
timematcher said:
Can we use other networks 4G in this device?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Please reply if possible
sparking111 said:
Please reply if possible
Click to expand...
Click to collapse
Huawei 4G wingle should support other networks/SIMs once rooted.
I had a E8372h-608 4G wingle which was network locked to Telenor. After flashing it with network-neutral, universal firmware from huawei, it works for Ufone, Telenor, Warid/Jazz after appropriate AP configuration within the device UI.
Does that answer your query?
Unlocking BootLoader :
Requirements:
1. Huawei Mediapad M5 lite ( not region specific).
2. Minimal ADB Tools.
3. Four Credits in DcUnlocker website. (Costs mere 4 euro).
4. DcUnlocker Software
5. Backup of your personal data.
Procedure.
1. First you need to enable usb debugging setting. Connect the tablet to PC in file transfer mode, navigate to Settings -> System -> About Tablet, tap build number multiple times till you get message "You are a developer now" . Now navigate back to System, you will see developer options setting in the menu. Enable "usb debugging" and OEM unlock options in developer options.
2. Download the minimal adb tools zip (link above) and install it your pc.
3. Connect your tablet to pc with usb debugging enabled and open command prompt in the adb folder ( Shift Right click ). In the Command prompt window type
Code:
adb devices
and you will see a device connected in the output. Then type
Code:
adb reboot bootloader
, your device gets rebooted into fastboot mode and you will see message "Bootloader Locked". ( Don't close the command prompt window yet).
4. To Unlock BootLoader you have to go to DcUnlocker website (link above Step 3). There select New user account and your username any then your email and in credits click on " how much do I need " and select third option " Force Huawei Android bootloader unlock (old method) " you will be charged 4 euros. (IMPORTANT: note down to password after creating account)
5a. After successfully creating account download the Dc Unlocker Software ( Step 4) and install it in your PC.
5b. Open the dialer on your phone and enter *#*#2846579#*#* select “Background settings”, “USB ports settings”, “Manufacture mode”.
6. Open Dc Unlocker Software and connect the tablet in fastboot mode to the pc.
On the left side menu
Select Manufacturer -> Huawei Phones
Select Model -> Auto detect
and click on the search icon your device will be dectected in fastboot mode.
7. Click on Server on the right side menu enter your username and password and click on Check login, you will see your username and credits in the output window below.
8. Now click on the Read bootloader code (Unlocking -> Read bootloader code) in the right side menu and wait for the code in the output window. Once you get the Bootloader code note it down.
9. Now open the switch back to command prompt window in your pc, type
Code:
fastboot oem unlock [I]your-unlock-code[/I].
You will be prompted to select Yes/No in the tablet to unlock bootloader, select yes using volume buttons.
10. You have succesfully Unlocked your bootloader, your device gets factory resetted automatically and reboots.
Relocking BootLoader :
Requirements:
1. Unlocked Huawei Mediapad M5 lite ( not region specific).
2. Minimal ADB Tools.
3. Bootloader code ( obtained from unlocking from above guide).
4. Backup of your personal data.
Procedure.
1. First you need to enable usb debugging setting. Connect the tablet to PC in file transfer mode, navigate to Settings -> System -> About Tablet, tap build number multiple times till you get message "You are a developer now" . Now navigate back to System, you will see developer options setting in the menu. Enable "usb debugging" and OEM unlock options in developer options.
2. Download the minimal adb tools zip (link above) and install it your pc.
3. Connect your tablet to pc with usb debugging enabled and open command prompt in the adb folder ( Shift Right click ). In the Command prompt window type
Code:
adb devices
and you will see a device connected in the output. Then type " adb reboot bootloader ", your device gets rebooted into fastboot mode and you will see message "Bootloader UnLocked".
4. Type
Code:
fastboot devices
and you will see a device connected in the output. Then type
Code:
fastboot oem relock [I]your-unlock-code[/I].
5. You have successfully relocked your bootloader, your device gets factory resetted automatically and reboots.
Delete
Just a warning for anyone who bought a cheap M5 Lite at amazon's Black Friday anywhere in Europe with model BAH2-W19C431, as opposed to the older BAH2-W19C432: The unlocking process described above doesn't work any more. Even though DC Unlocker requests 15 cr instead of 4 cr, the unlocking process fails with the following message:
"Factory reset protection Erase start
Fastboot command fail!"
Even though the tablet is obviously still locked, the 15 cr are removed from the account, so you'll have to ask for a refund.
As a slight sidenote, no. 5b of your unlocking procedure should actually be no. 1b, as you obviously can't set the USB connection to Manufacture Mode if you're already in fastboot mode.
Also on WiFi-only tablets there's no dialer, therefore you'll have to use the tablet's calculator and enter ()()2846579()() to get to the configuration menu instead.
@ j04nd03
I guess you are wrong.
I also bought one of the cheap M5 Lite at amazon's Black Friday offer. Code:431.
I can definitely confirm that sadiqkarur´s unlock method is working on 431 with the amount of 4€.
At first i also stuck on the 4€ --> 15€ price rise in the DC unlock tool.
The solution in my case was to install the HUAWEI software package HiSuite to have the right working drivers in the background.
Before installing the Suite the DC unlock tools only found "general" Huawei device by 15€, and after install the description giude worked very well.
Thanks to sadiqkarur, and sorry for my bad english.
At
It was Friday the 29th evening, there was no reply to this thread from @j04nd03 yet.
I tried this guide, i had the first problem in point 5b because I had to look for the calculator solution somewhere else and also because I obviously can't do the calculator procedure if i'm already in fastboot mode (point 3).
Anyway, before going to fastboot I enabled the 'Manufacture mode', then went to fastboot. I paid 4 euro and it said it needed 15. I payed 11 more euros and the procedure failed. Exactly on that error. I asked for a refund.
The day after, Saturday, I read the reply from @j04nd03 and I said to myself "oh well, alright".. The refund arrived on saturday morning already, when the same owner of dc-unlocker replied me telling me that for this tablet there's nothing to do as the security patches locked down the device from being used on dc-unlocker.
Yesterday the 2nd of December I read the reply from @Honeytea. I uninstalled all the previous drivers, rebooted the pc, installed Hisuite drivers and rebooted again (it's usually best to reboot between driver installs) and still nothing. Dc-unlocker still does not give option of 4 credits.
So, if anyone's got a proper procedure this will help a lot, really a lot! No doubt the original procedure of #1 works, but.. something is probably missing.
FW version: BAH2-W19 8.0.0.230 C431
Thanks everybody!
EDIT: Thanks to the post below the unlock worked! :good: :good:
So i actually managed to unlock bootloader via DC-unlocker
FW version: BAH2-W19 8.0.0.230 C431
Procedure:
1: install Minimal ADB Tools.
2: install HiSuite and make all steps to connect tablet with PC.
3: download and install DC-unlocker,
Go https://www.dc-unlocker.com/buy
> select New user account
> type your desired Username and our E-mail
> next to the Credits click on "how much do I need?" and select third option "Force Huawei Android bootloader unlock (old method)"
> NOTE: You will be charged 4€ (IMPORTANT: note down to password after creating account)
4: Connect the tablet to PC in file transfer mode, navigate to Settings -> System -> About Tablet, tap build number multiple times till you get message "You are a developer now" .
Now navigate back to System, you will see developer options setting in the menu.
enable OEM unlock
enable USB debuggin while connected to PC, will ask you if always trust this device ... (for me didn't work at first shot as i didn't install HiSuite before)
5: Open Calculator app and type ()()2846579()()
select Background settings > USB ports settings > Manufacture mode
DO NOT REBOOT TABLET INTO FASTBOOT MODE
for some reason fastboot is changing manufacture mode to default settings and then DC-unlocker not working properely.
6: Open DC-unlocker, Click on Server on the right side menu enter your username and password and click on Check login,
you will see your username and credits in the output window below
select Huawei phones in manufacturer
select auto detect in model
click scan, you should recive something like this
Code:
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM3
Also ports in Aplication position will be selected by the program (COM3 in my case)
Select the same port in Diagnostic
Hit the Read bootloader code and this is what you should get:
Code:
Check account status
User : yournamehere
Credits left : 4
Activated features:
Software debugger
Unlock Auto detect (recommended) cost 4 cr
===================================================================
Reading bootloader code...
Bootloader code : your code will be here
7: copy your code and paste somwhere on notepad to be sure you not gonna lose it
8: open adb and type:
adb devices (to make sure your PC is connected to tablet)
adb reboot bootloader (your device will reboot into fastboot mode now)
9: when you are into fastboot mode type:
fastboot devices (just to make sure if PC is connected to tablet)
fastboot oem unlock drop your code here
You will be prompted to select Yes/No in the tablet to unlock bootloader, select yes using volume buttons.
10: You have succesfully Unlocked your bootloader, your device gets factory resetted automatically and reboots.
Sorry for some copy-pasting from original topic but this way it looks more complex.
Nice., thanks. I just received my tablet today. Will try this tomorrow.
EDIT:
Your tutorial worked very well, thank you. But in Step 8 I had to modify the adb command because I had 2 devices in the list (one beeing an emulator) , so it was:
adb -s DEVICE-ID reboot bootloader
And then I could continue as described.
My menus don't show a "OEM" option after developer mode, any idea?
Finally managed to unlock my device with this, THANKS!! Pretty much had given up on the device when Huawei stopped handing out unlock codes (never again will I buy Huawei)
Next step will be installing openKirin, seems like the device isn't officialy supported but I tried flashing it anyway. Not having much luck so far, device stuck in "booting device" even when formatting data.
Hello ,I have a mediapad M5 that's stuck in retail demo mode ... i followed all the steps from drumiec's post , but i have a problem at step 6 , the DC software doesn't show my bootloader code , but shows me this instead ,can someone help me ?
{
"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 just go the mediapad m5 lite and followed @drumiec directions and it perfectly worked! Thank you again for this.
---------- Post added at 01:37 AM ---------- Previous post was at 01:37 AM ----------
I just go the mediapad m5 lite and followed @drumiec directions and it perfectly worked! Thank you again for this.
Nivans62 said:
Hello ,I have a mediapad M5 that's stuck in retail demo mode ... i followed all the steps from drumiec's post , but i have a problem at step 6 , the DC software doesn't show my bootloader code , but shows me this instead ,can someone help me ?
Click to expand...
Click to collapse
which firmware is running your device?
also try to use different USB cable or different USB port
Maybe it's help to disable the Demo mode in the Developer Settings
---------- Post added at 05:35 AM ---------- Previous post was at 05:31 AM ----------
Unlook is work with the last description (no reboot to fastboot) and for 4Credits.
Only different: I've the LTE Version and instead of the calculator, the dialer must be use with the #*#* sequence from the first posting.
Additional a hint: USB debugging is at every reboot disabled automatically and must enabled every time once again.
On the DC Unlocker shop page, I can't buy 4 credits. I fill everything in as instructed but the web page says "All fields are required to fill" in red even though all of the fields are filled and the confirm button to make a payment is greyed out. I tried the site with Firefox and Chrome and the exact same thing happened with both. Am I missing something obvious?
The username must be at min 6?char. That was an issue, where I was stopped at the first time. After you reach the min. char lengh, the Red color is change to Green. Credits : you can insert direkt 4. Ive search the old Methode in the List, but after selection, the first pages pops up and in the field only the 4 was writen.
mad0701 said:
The username must be at min 6?char. That was an issue, where I was stopped at the first time. After you reach the min. char lengh, the Red color is change to Green. Credits : you can insert direkt 4. Ive search the old Methode in the List, but after selection, the first pages pops up and in the field only the 4 was writen.
Click to expand...
Click to collapse
I actually had to create a 7 digit username and then was able to purchase the 4 credits. Unfortunately, I got the unknown chipset error instead of the bootloader unlock code so the process didn't work for me anyway. Somebody else got the same error but if he was able to get around it I'm not sure how. Thanks for the reply.
Hopefully you have still the 4 credits.
If you connect the Tablet on the PC, the Hires Tool (right name?) start up automatically. Close the program and also kick it out via Taskmanager.
Go into the developer settings of the tablet and ensure that usb Debugging is still enabled.
Try with dcunlocker first of all, that the device is dedected. After that try read BL code in the the Diagnostic area
---------- Post added at 05:42 AM ---------- Previous post was at 05:39 AM ----------
Check also if the usb settings are still in Manufactor Mode (via dialer and *#*# code by a LTE devive)
mad0701 said:
Hopefully you have still the 4 credits.
If you connect the Tablet on the PC, the Hires Tool (right name?) start up automatically. Close the program and also kick it out via Taskmanager.
Go into the developer settings of the tablet and ensure that usb Debugging is still enabled.
Try with dcunlocker first of all, that the device is dedected. After that try read BL code in the the Diagnostic area
---------- Post added at 05:42 AM ---------- Previous post was at 05:39 AM ----------
Check also if the usb settings are still in Manufactor Mode (via dialer and *#*# code by a LTE devive)
Click to expand...
Click to collapse
Still the same error. Also tried the first method which didn't work because the device wasn't in manufacturer mode anymore after fastboot reboot. I think mine might be locked down since it's the US model and this method might only still work for the other models.
Use the second Methode.
The only different is, if you have the LTE Version, that you must use the dialer and not the calculator.
In case, if you use the dialer, you must insert the #*#*..... Code from the first posting.
Don't Boot into the Fastmode to read the Unlook Code.
Check if you habe an access via the Huawei App from the PC to the Tablet.
(An App will be installed on the tablet)
Let the phone connected on the PC.
Close the Huawei Programm on the PC and kick the program out of the memory,
Control after the Huawei App is closed:
that the USB manifacture Mode is enabled,
check in the Developer Settings,
that OEM Unlock,
and USB Debugging
is enabled.
USB Debugging during Charg only could be also enabled (I've make it)
Try out of the shell
adb devices (that you can See the device),
adb shell
and accept on the tablet, that this PC is trusted all time.
Close the command shell with adb
Start dcunlooker, Login with you Account on the Server,
Let dcunlooker dedect the right comport.
After dedecting the Com, selected the same Comport in the Tab one below for Diagnose.
After that selected in Diagnose "Read the Bootloader"
mad0701 said:
Use the second Methode.
The only different is, if you have the LTE Version, that you must use the dialer and not the calculator.
In case, if you use the dialer, you must insert the #*#*..... Code from the first posting.
Don't Boot into the Fastmode to read the Unlook Code.
Check if you habe an access via the Huawei App from the PC to the Tablet.
(An App will be installed on the tablet)
Let the phone connected on the PC.
Close the Huawei Programm on the PC and kick the program out of the memory,
Control after the Huawei App is closed:
that the USB manifacture Mode is enabled,
check in the Developer Settings,
that OEM Unlock,
and USB Debugging
is enabled.
USB Debugging during Charg only could be also enabled (I've make it)
Try out of the shell
adb devices (that you can See the device),
adb shell
and accept on the tablet, that this PC is trusted all time.
Close the command shell with adb
Start dcunlooker, Login with you Account on the Server,
Let dcunlooker dedect the right comport.
After dedecting the Com, selected the same Comport in the Tab one below for Diagnose.
After that selected in Diagnose "Read the Bootloader"
Click to expand...
Click to collapse
I still get the same Not Supported/Unknown Chipset error message. I did everything you suggested but when I type adb shell nothing shows up on my tablet.