Hello. My phone will not receive automatic build updates, still on 4.4.2 as opposed to the current 5.0.1 version .
adb will not find my phone when it's plugged in either. Thus why I am creating this post. Any help is appreciated.
Ubuntu is still using code from 4.4 for accessing the phone's hardware and the developers have said that they won't switch too soon due to the amount of bugs in 5.0.
Normal system updates should work fine though. Which channel are you on?
Sent from my awesome Ubuntu Touch device using the Forum Browser app
nikwen said:
Ubuntu is still using code from 4.4 for accessing the phone's hardware and the developers have said that they won't switch too soon due to the amount of bugs in 5.0.
Normal system updates should work fine though. Which channel are you on?
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Click to expand...
Click to collapse
Oh OK. Perhaps my phone was up to date. I was on the devel channel I think. I just reflashed to stable and forgot how to do it, it's quite easy for any future readers:
1. Turn off phone, then press [+ -] volume buttons and power button at same time, you will see android with belly open.
2. Install Android SDK studio on Ubuntu
3. Run this code from Ubuntu with the phone usb plugged in:
ubuntu-device-flash touch --channel=ubuntu-touch/stable--bootstrap
4. Don't touch a thing, including the blck & wht question screen; it will boot itself into ubuntu
Note: This also fixed the issue of my phone not ringing or making any noise when receiving calls and texts
Xinthose said:
Oh OK. Perhaps my phone was up to date. I was on the devel channel I think. I just reflashed to stable and forgot how to do it, it's quite easy for any future readers:
1. Turn off phone, then press [+ -] volume buttons and power button at same time, you will see android with belly open.
2. Install Android SDK studio on Ubuntu
3. Run this code from Ubuntu with the phone usb plugged in:
ubuntu-device-flash touch --channel=ubuntu-touch/stable--bootstrap
4. Don't touch a thing, including the blck & wht question screen; it will boot itself into ubuntu
Note: This also fixed the issue of my phone not ringing or making any noise when receiving calls and texts
Click to expand...
Click to collapse
Yes, the builds from the devel channel are about 3 months old, if not more. I wouldn't recommend to use them.
Instead, it's best to go with stable.
Are the Stable Build newer than the devel builds?
Reading the channel selection guide I tought that the devel builds would be newer.
jonny-boy said:
Are the Stable Build newer than the devel builds?
Reading the channel selection guide I tought that the devel builds would be newer.
Click to expand...
Click to collapse
Oh, that page needs to be adjusted. I'll mention it on the mailing list.
The stable builds are much more up to date. In fact, they do not push updates to the devel channel anymore. If you really want to get the latest and (possibly not) greatest, you need to install devel-proposed. However, please notice those builds may not even boot. That just happened three days ago again.
Related
I'm having TROUBLES getting into fastboot because i don't have all the mediapad usb drivers installed, i think 5 or 6 are already installed but those arn't enough i think. i found a .zip file on internet containing the huawei mediapad usb drivers but i can't use them, as when i try to "update drivers" then browsing to here the usb drivers are stored i get an immediate error saying that i can't!
what is the proper way to do this please?
is it possible to get into fastboot WITHOUT having the usb drivers installed on the pc?
install HiSuite
441Excelsior said:
install HiSuite
Click to expand...
Click to collapse
that's already installed, on the pc and the tablet.
such a powerful android tablet is totally forgotten, people still develop for the first android device ever "t-mobile G1" and no one cares about huawei's great hardware. three days ago someone ported Jelly Bean 4.1 to the G1, and here we are still fighting to get an official cyanogen mod rom
this isn't fair.
hamdimo said:
that's already installed, on the pc and the tablet.
such a powerful android tablet is totally forgotten, people still develop for the first android device ever "t-mobile G1" and no one cares about huawei's great hardware. three days ago someone ported Jelly Bean 4.1 to the G1, and here we are still fighting to get an official cyanogen mod rom
this isn't fair.
Click to expand...
Click to collapse
I too am sad, however, Huawei hasn't yet mastered that game called "$Marketing" which the Americans are very good at. At least Huawei seems to be taking some steps to rectify that.
Anyway, here
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
working PC fastboot, and has link to download.
joytest said:
I too am sad, however, Huawei hasn't yet mastered that game called "$Marketing" which the Americans are very good at. At least Huawei seems to be taking some steps to rectify that.
Anyway, here
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
working PC fastboot, and has link to download.
Click to expand...
Click to collapse
Thanks for the link, i'll try that.
Fastboot should be hold volume down plus the power. When it's in fastboot mode should say a first line then hold power for 10 sec to reboot and the screen is black.
gruiz3 said:
Fastboot should be hold volume down plus the power. When it's in fastboot mode should say a first line then hold power for 10 sec to reboot and the screen is black.
Click to expand...
Click to collapse
Or install quick boot from play
Sent from my HUAWEI MediaPad using Tapatalk 2
I just installed Quick Boot for the play store, much much easier and always gets the job done, all that button pushing and holding is just old fashioned a bit.
but all this will be useless if we can't have a STABLE working cyanogenmod like the one that brought life on my htc wildfire. we are all waiting and testing but after_silence can't do everything alone, all the so-called developers on XDA are busy porting Jelly Bean to the oldest devices ever!
I will need to archive that app, i know how frustrating it is to remember key combinations on multiple devices.
I was just curious is anyone has actually successfully updated one of these units to something other than the stock Froyo firmware.
I've read a lot about getting into recovery mode, SDE, etc, etc, but I'm wondering if anyone would care to comment on their experiences getting a working third party ROM on the devices and how that ROM performs in real-world use.
Thanks!
From my experience on what I heard from users that did try CM7 from openaos or CM9 from bizquite
Multiboot menu from openaos should work, but it won't show it on screen. So you have to put the image you want to boot on top in menu.lst to boot it by default. Also getting into recovery can be a bit of a pain especially when you installed SDE.
Showing the bootmenu, could be an easy fix for the home connect, but sadly I don't have one to make it work.
Menu.lst example for booting gingerbread on home connect:
Code:
Gingerbread||/openaos-gingerbread.img|/init|0
Archos|ARCHOS|ARCHOS|/init|0
Angstrom||/rootfs.img|/sbin/init|1
divx118
mckinleytabor said:
I was just curious is anyone has actually successfully updated one of these units to something other than the stock Froyo firmware.
I've read a lot about getting into recovery mode, SDE, etc, etc, but I'm wondering if anyone would care to comment on their experiences getting a working third party ROM on the devices and how that ROM performs in real-world use.
Thanks!
Click to expand...
Click to collapse
I'm using CYANOBIZ (cm9) on my 101it and I'm quite happy for now (the rom is still in developpement) and I will never use 2.x on any Android device
And I'm using kboot so I don't have to use a computer to update the kernel
minidou-77 said:
And I'm using kboot so I don't have to use a computer to update the kernel
Click to expand...
Click to collapse
kboot is indeed nice, however I don't know if the home connect has hardware volume up/down buttons to navigate the menu. kboot has no touchscreen support.
divx118
Welcome to my tutorial !
You can find others tutorials related to the Cube i6 :
Install windows 10
Install Android 4.4.4 (Stock & RemixOS)
I received the magnificent AllDoCube i6 Air 3G last week, and i've been struggling since to get updates,
firmware flashing and all of that working, I searched the whole web and the drivers/Firmwares are nowhere to find,
but on some chinese proxy-needed sites sometimes, or baidu which is a pain in the a** to download from.
So I decided to share the ways to update this tablet at all costs (heh, no worries, -NORMALLY- it wont brick)
Disclamer: This process might contain ROM hacking, this is for advanced users.
THIS TUTORIAL HAS BEEN TESTED ON i632GB1537XXXXXXX MODEL, AND WORKS ON IT,
WHEREAS IT HAS BEEN REPORTED THAT i632GB1522XXXXXXX MODEL BRICKED UPON DOING IT,
SO PLASE DO IT CAREFULLY, IF THE INSTALL VERSION IS 202 YOU SHOULD THINK ABOUT IT BEFORE TRIYING AS IT COULD BRICK!
Software included may be subject to copyright.
Flash your device at your own risk. Developer is not responsible for what you do on your device.
What you need:
Cube i6 Air (3G or Wifi)
Flash Drive (256Mo +)
OTG cable
USB Hub (3 Ports recommended)
EFI BIOS Firmware
DOWNLOAD THE FIRMWARE BEFORE STARTING SO EVERYTHING IS AVAILABLE WHEN YOU DO IT
https://drive.google.com/folderview?id=0B8YPw4HjmqNCZktOZy1OTEN2ZVE&usp=sharing
Get on the drive, go to your device folder, select the wanted version inside BIOS folder
What to do :
1.) Start by plugging the usb drive into your computer, and format it to FAT32 using any formatting tool
2.) Now you need to uncompress the downloaded firmware :
you will find a "Firmware_X.X.X" folder inside, take all of its content, and extract it to your freshly formatted drive.
here's what looks like the root of your usb:
3.) Your USB Drive is ready, now just plug the OTG cable to your tablet, plug your HUB onto that OTG
and fill it with your keyboard and the USB Drive just created.
4.) Press power button until you see the screen backlight, when you see it repeatidely smash "Esc" key on the connected keyboard.
You will see the bios 6 square configuration screen.
Hit "Boot Manager" and select your USB in the list.
5.) The tablet should now boot from your USB, booting to a UEFI Shell. Depending on your device, it might be either 64 or IA32.
Now you just let startup.nsh script do the firmware flashing init, it should drive you to a flashing BIOS screen.
6.) Follow instructions on screen and let the tool flash your BIOS automatically.
Once done, the tablet will shut down.
Congrats! You successfully updated your BIOS !
It is my first tutorial, i will post some photos of steps in the future so come back, the guide will be better soon !
Regards,
Max.
Hi,
I have bought the Cube i6 Air 3G a week ago and i'm still waiting for it to arrive.
Have you update the win 8.1 to win 10?
Does everything works correctly?
Regards
re
Hi, I successfully updated the BIOS as of now,
I changed the bootloader animation to nexus one on Cube ROM.
I also manager to boot on Android x86 but it had too many drivers issues.
Still, 4.4.4 stock cube is working and i reflashed to a new partition scheme of 9Go
and i'm currently testing some win10 pen drives for install, will keep you updated.
Édit: oh you were asking about thé tablet? Weil jack has default, charging takes hours, glass is plastic, firmware is pain but hell this is a goodamn good tablet for its price !
regards,
Max
stalker2106 said:
i'm currently testing some win10 pen drives for install, will keep you updated.
Click to expand...
Click to collapse
I achieved installing Win10 x32 Pro on Cube i6 Through hacking WinPE installation environnement, but now i'm struggling finding the drivers. touchscreen, battery and vital things like hd graphics are not working as of now. Will post a tutorial on how to install Win10 in given time when i'll get out of this mess!
My tablet has arrived yesterday.
From what the little i've used it, it has good performance especially in android.
A lot faster compared to my last android tablet (Cube U39GT).
Something i didn't like was the size of the icons and text in android, my next step is to root and change the dpi.
Regarding windows 10, i found in a chinese tablets blog with win 8 and 10 drivers.
I haven't tested it, but as soon as i find it again, i will let you know where to download them from.
You haven't tried the normal win 10 upgrade? From the microsoft icon?
gtbr said:
My tablet has arrived yesterday.
From what the little i've used it, it has good performance especially in android.
A lot faster compared to my last android tablet (Cube U39GT).
Something i didn't like was the size of the icons and text in android, my next step is to root and change the dpi.
Regarding windows 10, i found in a chinese tablets blog with win 8 and 10 drivers.
I haven't tested it, but as soon as i find it again, i will let you know where to download them from.
You haven't tried the normal win 10 upgrade? From the microsoft icon?
Click to expand...
Click to collapse
I did not try anything as i like "stock" versions of my windows, but tonight i got it working all the way !
My cube i6 is running perfectly windows 10 and oh my god what a paradise it is ! The tablet experience got way better onto that version.
Can you try to update from the icon you are talking about ? i'd be curious if it works. anyway, i'm currently writing+uploading for the win10
tutorial for this tablet, so you'll be able to flash it late tonight, or tomorrow.
EDIT: The dpi is correct in android, only the status bar icons and some other are not in correct dpi but that is KitKat issue I guess. still interested in resolving that though. I'm currently hacking android lollipop ROM also, i'll keep you tuned on that. For rooting, i used KingRoot, it worked, but after a reboot, it tells me "root" is wrecked, so i guess there is some investigation to do there, but I was mainly focused on getting windows 10 ENGLISH STOCK version running to share it with you guys.
EDIT2: Still uploading, but tutorial is here: http://forum.xda-developers.com/android/help/guide-how-to-install-windows-10-t3252042 and it should work on any Z37xx powered device. Enjoy !
Hello,
I'm using this tablet from 2 days now. great !
But, i got wifi problem after sleep : wifi chip cut and never found network anymore.
has to reboot, and all goes right.
same in win and android.
Did you hear about this ? many poeple complain about this.
Any trick or advice ? Is this bios correct this ? Is your bios work on i6 3g dual-boot ? (there is 2 bios for dual boot ?...)
Thanks !
Hi,
I've also have the same problem with the wifi.
I usualy disconnect the wifi and reconnect it, but sometimes it doesnt work and have to reboot the tablet.
I've not noticed it in windows but maybe it's because i'm using the tablet a lot more in android.
I've tryed to update to win 10 using the microsoft icon, but i got an error and was unable to complete the upgrade.
gtbr said:
Hi,
I've also have the same problem with the wifi.
I usualy disconnect the wifi and reconnect it, but sometimes it doesnt work and have to reboot the tablet.
I've not noticed it in windows but maybe it's because i'm using the tablet a lot more in android.
I've tryed to update to win 10 using the microsoft icon, but i got an error and was unable to complete the upgrade.
Click to expand...
Click to collapse
Hello, i have such a tablet for now about 6 Months and it is awesome so far (i often use win8.1).
My Tablet has also DUAL Boot with Android 4 and win 8.1 Bing.
I tried to upgrade to win10 but i also got a message that the partition can not be resized by windows. So i cant upgrade to win 10 with the normal tool from microsoft.
Is there any Solution yet to get this to work?
Anyway, i tried to boot from usb (win8.1 / ubuntu / gparted) but it is not working at all. When i try to boot true windows Advanced Boot Options, the BIOS says that there is no USB device.
When i use the EFI Shell to mount the USB Stick i can see that the BIOS has recognized the USB Stick.
I think that is all very strange, but i will try to update the BIOS soon. The serialnumber is not the same as from @stalker2106 but i will try it.
I hope there is a way to get win 10 working, but Ubuntu would be even better for performance.
Greetings from Germany.
tysonpower said:
Hello, i have such a tablet for now about 6 Months and it is awesome so far (i often use win8.1).
My Tablet has also DUAL Boot with Android 4 and win 8.1 Bing.
I tried to upgrade to win10 but i also got a message that the partition can not be resized by windows. So i cant upgrade to win 10 with the normal tool from microsoft.
Is there any Solution yet to get this to work?
Anyway, i tried to boot from usb (win8.1 / ubuntu / gparted) but it is not working at all. When i try to boot true windows Advanced Boot Options, the BIOS says that there is no USB device.
When i use the EFI Shell to mount the USB Stick i can see that the BIOS has recognized the USB Stick.
I think that is all very strange, but i will try to update the BIOS soon. The serialnumber is not the same as from @stalker2106 but i will try it.
I hope there is a way to get win 10 working, but Ubuntu would be even better for performance.
Greetings from Germany.
Click to expand...
Click to collapse
Check windows 10 Post, there is no need to update BIOS to fix this error, your USB has to be in GPT partition style, check answer on the other thread
But usually the bios update should work, as it did on my tablet. But why bother taking risk if you can get it working without it
Hi,
I have sucessfully updated to win10
I have bios 203 in my cube and serial i632gb1510xxxxxxxxxxx, does anybody have tried to update to 206 on such setup ?
What are the chances that I will brick my device ?
I have downloaded latest Cube i6 roms from cube site (may 2015) . There are two bios-es which have to be installed in chronological order.
Shall I do it first, and then try to update to 206 ?
Edit: I was not patient and tried it on my own.I have successfully updated bios and tablet has started to both android and windows
I will perform some functional tests afterwards.
Actual steps :
I have first downgraded bios to 201(provided here )
Flashed bios1 from link provided
Flashed bios2 from link provided
Flashed bios 206 from guide in first post
Edit2:
I have tested basic functionalities like : Gyro-sensors, WIFI, GPS, 3G network and yet everything works like charm.
Maybe a placebo, however I have the feel that android runs like two times faster
I do suggest to update the windows, however I take no responsibility if you will brick your device. Even if the setup is like mine, neither if it differs
Regards
Why do you first downgrade to 201?
What do you mean with bios1 and bios2?
Many thanks and question
Hello Stalker,
I am new here and i want to
thank you for the instructions!
I bought a cube i6 from china.
It is the 'i6 air remix',
So it should have only Android on it.
When it arrived. it didn't function.
The only think that happens is booting to theEFI-shell.
I could switch between Android and Windows in the boot settings.
But Android did not boot.
I have updated the bios with your instructions
now firmware 2.0.6 is installed.
But still i can not boot Android.
I found a few flash tools and android for the cube i6 .
But i don’t know what is the right version flash tool I have to use.
Maybe you have advise or the right android and flash tool in your google drive download area?
Kind regards and many thanks in advance.
jan-netherlands said:
Hello Stalker,
I am new here and i want to
thank you for the instructions!
I bought a cube i6 from china.
It is the 'i6 air remix',
So it should have only Android on it.
When it arrived. it didn't function.
The only think that happens is booting to theEFI-shell.
I could switch between Android and Windows in the boot settings.
But Android did not boot.
I have updated the bios with your instructions
now firmware 2.0.6 is installed.
But still i can not boot Android.
I found a few flash tools and android for the cube i6 .
But i don’t know what is the right version flash tool I have to use.
Maybe you have advise or the right android and flash tool in your google drive download area?
Kind regards and many thanks in advance.
Click to expand...
Click to collapse
The truth is, the 206 BIOS provided is hacked off i6 remix repository from cube, so i guess there is no big deal flashing it on your device as it works on regular i6.
Moreover, you can use any version of the flash tool as long as you flash a correct rom for your device, which i would suggest to download from official cube repository or geekbuying or so.
Android Geecbuying
Hello Stalker,
Ok. Thank you!
I will try Geecbuying.
Hopefully the windows drivers will function.
There isn't a way to flash from USB I suppose?
Greetings
Hi, well, actually, you should flash over USB with à windows computer. MFT by Intel is recommended. I shall make some tutorial about Android installation and partition resizing.
flash and resize partitions
That is super. When you want to do so.
I was indeed wondering or there would be one android partition on the tablet or two partitions (one for android, one for windows).
I also questioned myself how to see that there are partitions.
In earlier times when I was working with a pc, i use F-disk or partition-magic for this kind of work.
But on the tablet I do not have a clue...
So if you could make me wiser on this, I would be very thankful.
Maybe you could boot on some gparted liveusb? Or inside efi shell some commands could help
bluefish007 said:
Why do you first downgrade to 201?
What do you mean with bios1 and bios2?
Click to expand...
Click to collapse
no particular reason, I just wanted to know, which version of bios is in the latest firmware provided by geekbuying
Additional condition in my decision mechanism was that my serial did not match mentioned ones in w10 thread from stalker, so somehow I have used sleepy sloopy logic and tried to minimalize the risk (I know it have no rational reason and logic behind it at all)
Therefore, I tried the ones from geekbuying repository, to be sure to have latest provided from "official source".
greetings
thermoska said:
no particular reason, I just wanted to know, which version of bios is in the latest firmware provided by geekbuying
Additional condition in my decision mechanism was that my serial did not match mentioned ones in w10 thread from stalker, so somehow I have used sleepy sloopy logic and tried to minimalize the risk (I know it have no rational reason and logic behind it at all)
Therefore, I tried the ones from geekbuying repository, to be sure to have latest provided from "official source".
greetings
Click to expand...
Click to collapse
Ok thanks for the answer! So i can upgrade from 203 at 206 at one part or what do you think?
Where to begin? Logic would dictate, the beginning.
I'll do my best to be brief with the backstory.
Months ago I ordered a Jide Ultratablet to use as my portable workhorse. At first things were peachy until a rather monumental lag began to manifest every 15-45 seconds. It made the device impossible to utilize in any productive fashion, so I contacted Jide and opened up a support ticket. After months (in no way an exaggeration) of barely responsive correspondence, during which I sent them a video to demonstrate the problem, they finally came back to me with an email containing a link to a compressed folder containing the Remix 2.0 images, and also a link to a rather vague and complicated tutorial on how to flash Remix 1.5 manually to a device. (In fact, I tried to include a link to the tutorial, but I am unable to since I haven't posted to the forum enough. I am happy to PM it or email it to anyone who might like to help) I can only assume I am meant to apply the same logic to the Remix 2.0 files they sent me. Seemed a bit dicey at first glance, but while I'm by no means an expert, I'm no slouch in this arena and I'm a very quick study.
Now, on to the proverbial meat and potatoes:
If you were able to contact me for a link to the tutorial in question, you will have undoubtedly seen that they indicate one should use ADB-Fastboot as a means to flash the recovery image. No real surprises there. I have ADB and Fastboot installed on my PC (Windows 10). I also have the ADB drivers installed and have confirmed the addition to my PATH. (eg: ;C:\ADB) I can also confirm that it is working fine since I am able to pull up a terminal and issue the ADB command and it gives me the usual wall of commands. The problem is that my device (Ultratablet) is not being seen by ADB. I have checked my USB drivers and they are all up to date and installed properly. My PC sees the device no problem and there is no indication of any sort of connection error. I've also tried different cables and ports. Yet, I can't access it via ADB and thus am unable to issue commands to my device such as "adb reboot bootloader" or "fastboot reboot-bootloader".
My next logical approach was to attempt forcing the device into fastboot mode using the hardware button combination, which is not listed specifically for the Ultratablet anywhere, I might add. (Power key + Volume up) It brings me to a boot options menu with the selections "Continue/Fastboot Protocol/Recovery Kernel/Reboot/Poweroff/Forced Recovery". Ateempting to select Fastboot Protocol causes the display to shut off for a moment, the device to vibrate once, and then the display to turn back on back at the same menu full of selections.
So, in summary, I am expected to flash the device using fastboot and yet I can't even get the device into fastboot mode, let alone issue commands from my PC terminal. As I highlighted near the beginning, teh Jide support team is incredibly unresponsive and not overly helpful. I have notified them of this same set of issues, but I don't expect to hear back in any expedient fashion and I thought one of the mighty members here on XDA might be able to help me come up with a next step in the meantime. I'd cerainly love to be able to use my shiny new tablet.
In any case, thank you for your time.
Kind regards.
Shaiden
Bump? Anyone? Still swinging in the breeze on this one. No word back from the manufacturer, as expected. =/
I have the same problem
Shaiden said:
Bump? Anyone? Still swinging in the breeze on this one. No word back from the manufacturer, as expected. =/
Click to expand...
Click to collapse
I know it's been 4 years but did you find any solution to this? I'm asking because I have the same problem. I decided to downgrade to Remix OS 1.5 in order to root (I have tried 5 rooting apps with no success) but my device refuses to enter fastboot protocol. The whole idea was since I can't find a way to root the damn thing in its current state maybe I can manage it with its older OS version. All this just to turn it to android root apps "testing ground" device. Oof.
I am trying to unlock the bootloader so I can root a LG Aristo 4 plus model LMX320MA.
1st off I tried "kingroot", kingoroot" and a few other one step app's. None of them worked.
I type in the cmd window "adb devices" I get the following answer:
"list of devices attached"
"LMX320980e0723 device"
Next I type in "adb reboot bootloader" and I am spouse to get on the phone that is in the screen capture that is in the Dropbox link bellow.
https://www.dropbox.com/s/k1u2r5eudem996w/fastboot.jpg?dl=0
instead of getting the screen that is in the Dropbox link above. The phone just boots up to the normal home screen. See the next Dropbox link bellow.
https://www.dropbox.com/s/fopf8ykyyazq0dt/screen capture.jpg?dl=0
I don't know how to fix this problem in ADB- Fastboot
Power off, connect usb and hold power and vol+ button until it boots
DavidxxxD. The phone powers down ok. But the "hold power and vol+ button" doesn't do a darn thing. The phone boots to the normal home screen.
DavidxxxD said:
Power off, connect usb and hold power and vol+ button until it boots
Click to expand...
Click to collapse
@reble1
Phone's stock boot image has dm-verity, which prevents you from booting if you make system modifications.
I finely figured out the buttons. I found a Metro PCS/T Mobile web page with the info. It is pressing and holding the vol down button plus the power button until the 1st Metro logo comes up on the screen. Keep holding the vol down button in while releasing the power button for a sec then press and hold the power and vol down buttons until the 2nd Metro logo pops up on the screen. Then I am in. BUT it doesn't do me any good. All that screen is good for is to wipe the phone clean in the event of a soft brick and set the phone back to factory default settings. It is like wiping the hard drive clean on my Windows laptop and reinstalling the OS and everything else.
I am still stuck in rooting this phone. I understand the concept of rooting, it is like getting super administrator privileges in Windows. I am still fairly new to Android.
@reble1
Since almost a decade peoples use Chainfire's SuperSu to successfully root an Android device without any sprains.
BTW: To root Android doesn't require device's bootloader is unlocked.
jwoegerbauer. What do you mean by "dm-verity"? I went looking and I found out what "dm-verity" is. there is a few reasons as to why I want to root the phone.
1. it is a learning curve for me, it enhances my understanding of Android.
2. there is 2 annoying popups that pope up when I 1st wake up the phone. 1 is from Metro PCS, advertising, and the other is Google Chrome, the last web page that I was on. One or both pop up before I get to the home page.
3. there is a few programs that I would like to look at that require the phone to be rooted.
PS: What is a good phone or tablet that is easy to root for experimenting on?
jwoegerbauer said:
@reble1
Phone's stock boot image has dm-verity, which prevents you from booting if you make system modifications.
Click to expand...
Click to collapse
JwoegerbauerI am fairly new at Android. My vast knowledge, Starting with a Vick 20 and moving up the Commodore chain, then the MS-Dos chain and finely Windows 3.1 and up. Helps some. But I also know there is a lot of differences between Android and Windows.
Is there anyway around the dm-verity? Or am I just plain stuck with what I got?
jwoegerbauer said:
@reble1
Phone's stock boot image has dm-verity, which prevents you from booting if you make system modifications.
Click to expand...
Click to collapse
@reble1
Compared to Windows OS - what is a proprietary OS - Android OS is an open-source OS, means everybody can offer a modified version of it ( keyword: Lineage OS et. al ). OEMs / Carriers got tired of people trying to change the Android that came with their devices. Especially SuperSU and other one-click root enablers, XPosed Framework & Magisk Framework - 3rd-party Android modding tools that severely change the system part of Android OS - were/are such undesired candidates. Hence starting with Android 4.4.4 Google added the dm-verify ( read: Verify Boot ) - what of course on a rooted Android can get disabled. It's a cat-and-mouse game that's going on. Also Android users must know that a modded / rooted Android always can get detected, even if they think that modding / rooting happened in a hidden manner as claimed. Google, OEMs and Carriers are certainly not as stupid as some people think ....
I am to the point of saying. Leaving it ASIS and put up with the browser popping up just after waking up the phone and before the home screen comes up. That was the whole exercise of this was to stop the browser from popping up between waking up the phone and the home screen coming up. And saving space by dumping blotters.
jwoegerbauer said:
@reble1
Compared to Windows OS - what is a proprietary OS - Android OS is an open-source OS, means everybody can offer a modified version of it ( keyword: Lineage OS et. al ). OEMs / Carriers got tired of people trying to change the Android that came with their devices. Especially SuperSU and other one-click root enablers, XPosed Framework & Magisk Framework - 3rd-party Android modding tools that severely change the system part of Android OS - were/are such undesired candidates. Hence starting with Android 4.4.4 Google added the dm-verify ( read: Verify Boot ) - what of course on a rooted Android can get disabled. It's a cat-and-mouse game that's going on. Also Android users must know that a modded / rooted Android always can get detected, even if they think that modding / rooting happened in a hidden manner as claimed. Google, OEMs and Carriers are certainly not as stupid as some people think ....
Click to expand...
Click to collapse
If it was me, being an lg device I'd try to see if I could get modded lgup (dual mode)
By tchnight or the original one by astr4y4l
I'd then see if I cold get the correct dll files for it to connect to my phone.
I'd try dump option to get my firmware.
If successful
I'd rename boot_com3.mbn to boot.img
Then patch it with magisk,
Then use partitions dl option on lgup to flash that magisk_patched image renamed boot.img back to the phone...
Just my 2 cents and unless you gonna pay me for my time and Info..
I'm off the clock
LgPWN'd. Sorry for the delay in the reply. I had other things to tend to that took up my time.
I am not sure i understand what you mean by "modded". If I understand it right. It would be the same as splitting a PC hard drive into 2 partitions and putting Windows 7 on 1 partition for older programs and games. And on the other partition Windows 10, right? secondly I am not worried if Metro PCS finds out that the phone has been rooted. From what I have been told Metro PCS doesn't care if the phone is rooted. Also I am assuming tchnight and astr4y4l are rooting programs? If so. Are they Android app's or Windows based programs? Also I have the correct Windows USB driver to connect my phone to my laptop.
LgPWN'd said:
If it was me, being an lg device I'd try to see if I could get modded lgup (dual mode)
By tchnight or the original one by astr4y4l
I'd then see if I cold get the correct dll files for it to connect to my phone.
I'd try dump option to get my firmware.
If successful
I'd rename boot_com3.mbn to boot.img
Then patch it with magisk,
Then use partitions dl option on lgup to flash that magisk_patched image renamed boot.img back to the phone...
Just my 2 cents and unless you gonna pay me for my time and Info..
I'm off the clock
Click to expand...
Click to collapse
A PS: I just did a quick internet search for " astr4y4l" and " tchnight" . There isn't anything that I can see that has anything to do with cell phones at all.
reble1 said:
A PS: I just did a quick internet search for " astr4y4l" and " tchnight" . There isn't anything that I can see that has anything to do with cell phones at all.
Click to expand...
Click to collapse
Try searching on xda
Sent from my Willeyfox Swift using Taptalk