Database Users

[Q] [HELP] How to root LG optimus L5 E617G WITH Jellybean 4.1.2

I lost my root after the official firmaware upgrade now i cannot root it . Please help I have tried everything in XDA please help..... frustrated as hell

bennatpjose said:
I lost my root after the official firmaware upgrade now i cannot root it . Please help I have tried everything in XDA please help..... frustrated as hell
Click to expand...
Click to collapse
have you tried to flash a pre-rooted JB?

Sabyn said:
have you tried to flash a pre-rooted JB?
Click to expand...
Click to collapse
is there a guide somewhere

bennatpjose said:
is there a guide somewhere
Click to expand...
Click to collapse
to flash a version of JB? come on my page , i can give you a link to my dropbox , there is anything you need

bennatpjose said:
is there a guide somewhere
Click to expand...
Click to collapse
i also have an e617g on 4.1.2 bell network id like to root and unlock the bootloader so i can install cwm and finally swap roms, this is a nice phone but it barely exists on the web any help would be greatly appreciated, thanks in advance

Never mind figured it out myself. I may post a guide here soon. Seeing as any help I ask for is ignored. I'd rather help than hold back

Turn your lG-e617g into an LG-e610 then root it and install cyanogenmod.
bennatpjose said:
is there a guide somewhere
Click to expand...
Click to collapse
this is my first tutorial so message me if something on here isnt clear.
step 1: download things, this is crucial, you need to download this stuff, it took me a while to find everything that ACTUALLY WORKED so i have it all in a nice little package to download.
step 2: make sure your phone is NOT plugged in the computer, install drivers if you do not have them. i have the drivers that worked for me in the package via direct download links. if they dont work for you somethings screwy with your computer and youll have to scour the internet to find drivers that'll work, google is your friend.
step 3: make sure your phone is recognised with your lappytop or computer. thats right i said lappytop, so sue me.
step 4nce all the drivers are installed and your phone is connected to the computer youll want to open up the folder labled: "LG FlashTool and Accessories" inside youll find "KDZ_FW_UPD.exe" open that right up.
step 5: next youll see a modded lg tool made by some guy on the internet, im not sure who but he/she did a good job thanks man/wo-man!!
ok youll want to leave all settings to default dont touch any thing, its good to go as is.
step 6: make sure phone is plugged in and usb debugging is enabled, use the kdz updater to browse for this file (download it via links in the package) "V10D_downgrade.kdz" then click on "Launch software update" this takes a while go make a coffee.
step 7: when its done its magic, your phone will boot up and youll see the LG logo for about 10 minutes any longer and your in a boot loop remove battery put it back in and hold both volume buttons down and power at the same time. time it carefully the lights on the soft keys will come on and a split second later the phone will slightly vibrate, the second you feel that press the home and hold it for about 10 seconds and the phone will do a hard reset, the phone will turn on now and initiate the first time use wizard, its in russian at first so just change your language to whatever, assuming english here. the phones software is now rooted just no su/superuser installed download from play store and update binary in settings of su app.
step 8: Unlocking bootloader time! after you flashed the software using kdz updater your phones ID is now technically an e610 now instead of an e617g, so unlocking the bootloader is now possible, connect your phone to computer, turn usb debugging on and drag and drop "emmc_appsboot.bin" into the root of your INTERNAL SD, also kill 2 birds with one stone here by also copying the recovery-clockwork-6.0.2.8-e610.img you downloaded via links in the txt document to the same place just rename it "recovery.img to make it easier also make sure you place the cm rom in the external sd. we need the bootloader unlocked to allow for cwm installation and good ol' rom swapping, open the folder "ADB" hold shift right click any where in the folder and select open "command window here",
type in the cmd window obviously without quotations: "adb shell" hit enter, then type "su" enter again then type "dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5" your bootloader is now unlocked, now type in "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17" this just installed clockwork mod. to boot into recovery and install cyanogen (the one im using. btw its a powerhouse compared to stock!!!) type in "reboot recovery"
step 9: factory reset, clear partition, wipe dalvik cache, install cyanogen, reboot, ENJOY.
seems i cant upload the programs needed so all i can do is this:
http://199.91.154.133/15ihz730pw2g/qwyqbfcp9fe7uhu/cm-10.1-20130725-UNOFFICIAL-e610.zip
this is the cyanogenmod rom.
http://199.91.154.102/r595o5bou5eg/bb2s0ohuj3jnflo/V10D_downgrade.kdz
this is the pre-rooted rom that allows su access to unlock bootloader this also
changes the phones id from e617g to e610, startup wizard is in russian at first simply change to english.
http://csmgdl.lgmobile.com/swdata/c...981MAN38AP22_ML_WHQL_Ver_3.8.1(0)_4.9.8.1.zip
this contains the correct drivers for phone.
http://dl.xda-developers.com/attach...65/51fc133a/1/7/5/6/7/5/9/CWM6_24-03-2013.rar
this is recovery image for cwm
and youll have to google search everything i quoted thats missing sorry about this but you need: 1) LG FlashTool and Accessories.
2) some form of adb for an adb shell.
3)emmc_appsboot.bin specifically for e610
4)lg drivers for e610/e617g
5)recovery.img for clockwork for e610
6)lastly the V10D_downgrade.kdz

I had already tried that but i keep getting the bloody error in KDZ
03:58:19 : Launching SW update
03:58:19 : Unpacking KDZ
03:58:21 : KDZ file extraced
03:58:21 : Extract file error
03:58:23 : ===FINISHED===
r4nd0m14m said:
this is my first tutorial so message me if something on here isnt clear.
step 1: download things, this is crucial, you need to download this stuff, it took me a while to find everything that ACTUALLY WORKED so i have it all in a nice little package to download.
step 2: make sure your phone is NOT plugged in the computer, install drivers if you do not have them. i have the drivers that worked for me in the package via direct download links. if they dont work for you somethings screwy with your computer and youll have to scour the internet to find drivers that'll work, google is your friend.
step 3: make sure your phone is recognised with your lappytop or computer. thats right i said lappytop, so sue me.
step 4nce all the drivers are installed and your phone is connected to the computer youll want to open up the folder labled: "LG FlashTool and Accessories" inside youll find "KDZ_FW_UPD.exe" open that right up.
step 5: next youll see a modded lg tool made by some guy on the internet, im not sure who but he/she did a good job thanks man/wo-man!!
ok youll want to leave all settings to default dont touch any thing, its good to go as is.
step 6: make sure phone is plugged in and usb debugging is enabled, use the kdz updater to browse for this file (download it via links in the package) "V10D_downgrade.kdz" then click on "Launch software update" this takes a while go make a coffee.
step 7: when its done its magic, your phone will boot up and youll see the LG logo for about 10 minutes any longer and your in a boot loop remove battery put it back in and hold both volume buttons down and power at the same time. time it carefully the lights on the soft keys will come on and a split second later the phone will slightly vibrate, the second you feel that press the home and hold it for about 10 seconds and the phone will do a hard reset, the phone will turn on now and initiate the first time use wizard, its in russian at first so just change your language to whatever, assuming english here. the phones software is now rooted just no su/superuser installed download from play store and update binary in settings of su app.
step 8: Unlocking bootloader time! after you flashed the software using kdz updater your phones ID is now technically an e610 now instead of an e617g, so unlocking the bootloader is now possible, connect your phone to computer, turn usb debugging on and drag and drop "emmc_appsboot.bin" into the root of your INTERNAL SD, also kill 2 birds with one stone here by also copying the recovery-clockwork-6.0.2.8-e610.img you downloaded via links in the txt document to the same place just rename it "recovery.img to make it easier also make sure you place the cm rom in the external sd. we need the bootloader unlocked to allow for cwm installation and good ol' rom swapping, open the folder "ADB" hold shift right click any where in the folder and select open "command window here",
type in the cmd window obviously without quotations: "adb shell" hit enter, then type "su" enter again then type "dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5" your bootloader is now unlocked, now type in "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17" this just installed clockwork mod. to boot into recovery and install cyanogen (the one im using. btw its a powerhouse compared to stock!!!) type in "reboot recovery"
step 9: factory reset, clear partition, wipe dalvik cache, install cyanogen, reboot, ENJOY.
seems i cant upload the programs needed so all i can do is this:
http://199.91.154.133/15ihz730pw2g/qwyqbfcp9fe7uhu/cm-10.1-20130725-UNOFFICIAL-e610.zip
this is the cyanogenmod rom.
http://199.91.154.102/r595o5bou5eg/bb2s0ohuj3jnflo/V10D_downgrade.kdz
this is the pre-rooted rom that allows su access to unlock bootloader this also
changes the phones id from e617g to e610, startup wizard is in russian at first simply change to english.
http://csmgdl.lgmobile.com/swdata/c...981MAN38AP22_ML_WHQL_Ver_3.8.1(0)_4.9.8.1.zip
this contains the correct drivers for phone.
http://dl.xda-developers.com/attach...65/51fc133a/1/7/5/6/7/5/9/CWM6_24-03-2013.rar
this is recovery image for cwm
and youll have to google search everything i quoted thats missing sorry about this but you need: 1) LG FlashTool and Accessories.
2) some form of adb for an adb shell.
3)emmc_appsboot.bin specifically for e610
4)lg drivers for e610/e617g
5)recovery.img for clockwork for e610
6)lastly the V10D_downgrade.kdz
Click to expand...
Click to collapse

That happens when the kdz file is corrupted. Redownload the firmware and try again

its more than likely a bad connection causing a bad download also are you starting off with an e617g or e610?

Will all app data, contacts, etc. be lost using this method? Thanks in advance!
r4nd0m14m said:
this is my first tutorial so message me if something on here isnt clear.
step 1: download things, this is crucial, you need to download this stuff, it took me a while to find everything that ACTUALLY WORKED so i have it all in a nice little package to download.
step 2: make sure your phone is NOT plugged in the computer, install drivers if you do not have them. i have the drivers that worked for me in the package via direct download links. if they dont work for you somethings screwy with your computer and youll have to scour the internet to find drivers that'll work, google is your friend.
step 3: make sure your phone is recognised with your lappytop or computer. thats right i said lappytop, so sue me.
step 4nce all the drivers are installed and your phone is connected to the computer youll want to open up the folder labled: "LG FlashTool and Accessories" inside youll find "KDZ_FW_UPD.exe" open that right up.
step 5: next youll see a modded lg tool made by some guy on the internet, im not sure who but he/she did a good job thanks man/wo-man!!
ok youll want to leave all settings to default dont touch any thing, its good to go as is.
step 6: make sure phone is plugged in and usb debugging is enabled, use the kdz updater to browse for this file (download it via links in the package) "V10D_downgrade.kdz" then click on "Launch software update" this takes a while go make a coffee.
step 7: when its done its magic, your phone will boot up and youll see the LG logo for about 10 minutes any longer and your in a boot loop remove battery put it back in and hold both volume buttons down and power at the same time. time it carefully the lights on the soft keys will come on and a split second later the phone will slightly vibrate, the second you feel that press the home and hold it for about 10 seconds and the phone will do a hard reset, the phone will turn on now and initiate the first time use wizard, its in russian at first so just change your language to whatever, assuming english here. the phones software is now rooted just no su/superuser installed download from play store and update binary in settings of su app.
step 8: Unlocking bootloader time! after you flashed the software using kdz updater your phones ID is now technically an e610 now instead of an e617g, so unlocking the bootloader is now possible, connect your phone to computer, turn usb debugging on and drag and drop "emmc_appsboot.bin" into the root of your INTERNAL SD, also kill 2 birds with one stone here by also copying the recovery-clockwork-6.0.2.8-e610.img you downloaded via links in the txt document to the same place just rename it "recovery.img to make it easier also make sure you place the cm rom in the external sd. we need the bootloader unlocked to allow for cwm installation and good ol' rom swapping, open the folder "ADB" hold shift right click any where in the folder and select open "command window here",
type in the cmd window obviously without quotations: "adb shell" hit enter, then type "su" enter again then type "dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5" your bootloader is now unlocked, now type in "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17" this just installed clockwork mod. to boot into recovery and install cyanogen (the one im using. btw its a powerhouse compared to stock!!!) type in "reboot recovery"
step 9: factory reset, clear partition, wipe dalvik cache, install cyanogen, reboot, ENJOY.
seems i cant upload the programs needed so all i can do is this:
http://199.91.154.133/15ihz730pw2g/qwyqbfcp9fe7uhu/cm-10.1-20130725-UNOFFICIAL-e610.zip
this is the cyanogenmod rom.
http://199.91.154.102/r595o5bou5eg/bb2s0ohuj3jnflo/V10D_downgrade.kdz
this is the pre-rooted rom that allows su access to unlock bootloader this also
changes the phones id from e617g to e610, startup wizard is in russian at first simply change to english.
http://csmgdl.lgmobile.com/swdata/c...981MAN38AP22_ML_WHQL_Ver_3.8.1(0)_4.9.8.1.zip
this contains the correct drivers for phone.
http://dl.xda-developers.com/attach...65/51fc133a/1/7/5/6/7/5/9/CWM6_24-03-2013.rar
this is recovery image for cwm
and youll have to google search everything i quoted thats missing sorry about this but you need: 1) LG FlashTool and Accessories.
2) some form of adb for an adb shell.
3)emmc_appsboot.bin specifically for e610
4)lg drivers for e610/e617g
5)recovery.img for clockwork for e610
6)lastly the V10D_downgrade.kdz
Click to expand...
Click to collapse

yes definitely back up

r4nd0m14m said:
yes definitely back up
Click to expand...
Click to collapse
Does this method actually unlock the network too? Can I use fido sim card? would it work?

[Unlock Bootloader,Install TWRP,Root Guide] H815EU-ONLY

edit : As of today - 28th June, this method ONLY works on the H815 EU models
update 26th July : Please go check the dream team's ROOT thread located here : [ROOT] TMO/VZW/ATT/SPRINT/INTL Root your LG G4 with Low Effort Root!
Thanks @thecubed , @autoprime , @IllegalArgument & @jcase for their hard work
Hi guys, a quick step by step guide to how I was able to unlock, install TWRP and Root my H815. Please don't hold me responsible if any issues arise with your phone. If you do this, you take your own responsibilities.
I tend to download all the tools in a single folder so it is easier to manage.
The LG Site:
1. go to this LINK and register.
2. you will get a confirmation email.
3. go to this LINK to unlock your bootloader (you will find the information on how to get your IMEI and Device ID lower in the post)
Your PC :
1. Be sure to have the LG drivers (i connected my phone first, it automatically installed the drivers on the computer.
update 27th July : thanks @the_scotsman in case you have driver issues please download these provided by @autoprime : LGUnitedMobile_Win_Driver_Ver_3.14.1
2. Be sure you have installed the ADB stuff that can be found here : Minimal ADB & Fastboot & ADB Installer (type Y to all the questions asked)
Install Minimal ADB first. Then type Y to all the questions the ADB installer asks. Close both windows once done.
Download TWRP 2.8.7. for H815:
1. go to this LINK and download it. Add it to your folder
Download SuperSu 2.46:
1. Download SuperSu 2.46 HERE (thanks @Chainfire ) and add it to your folder
PC & G4 love :
Once you are sure you have completed all the above tasks start rolling :
A. Enter your IMEI on the LG page
- you can find your IMEI on the G4 by going to settings > about phone > status
B. Get your Device ID:
1. hook up your LG on your PC (be sure not to be locked on your lockscreen, That USB debugging is checked and OEM checked in the Developer Options)
2. launch your CMD and type:
Code:
adb reboot bootloader
your phone will reboot
3. type this to get your Device ID
Code:
fastboot oem device-id
4. You will see two lines of number. Copy them and paste them together (to make one line) in the the Device ID fields on the LG site.
5 type :
Code:
fastboot reboot
5. close CMD
5. click Confirm on the site and you will receive by email a file called : unlock.bin.
Unlocking your bootloader:
1. once you get your LG email, save the unlock.bin in your folder
2. launch CMD from the folder (hold shift, right click the folder)
3. in CMD type :
Code:
adb reboot bootloader
4. once your phone is rebooted in bootloader type :
Code:
fastboot flash unlock unlock.bin
5. then reboot your phone by typing :
Code:
fastboot reboot
Normally your phone now has it's bootloader unlocked. When it boots you should see a message on the top left of the screen saying that.
COPY SuperSu and the downloaded TWRP file onto your phone (i put it in the download folder in the phone, not the SD) so you are ready for the next steps
Booting TWRP via ADB and bootloader mode
I personally think this was the easiest way to be able to root and clean install TWRP. Be sure your TWRP is in the folder.
1. Launch CMD from the folder (hold shift, right click the folder)
2. type (again) :
Code:
adb reboot bootloader
3. once your phone reboots and is in bootloader mode type :
Code:
fastboot boot TWRP2861.img
the new name of the file
or
Code:
fastboot boot p1.img
if you didn't rename it.
4. now you will reboot into TWRP.
Installing SuperSu
1. once you are in TWRP click install and go find your SuperSu file.
2. Swipe to install.
3. Once installation is done, reboot to system.
Once you have rebooted into the OS you will find the SuperSu app. Download the TWRP manager just to have it handy. And now i would install the TWRP file you have copied on your phone with flashify. I think it's a great tool.
2 ways to do it:
1. locate the file, click on it and choose to open with flashify then choose recovery and follow the steps
2. find the file via flashify and install.
(Don't download TWRP for H815 in the TWRP manager or Flashify as they are not fixed by @wolfgart (correct me if I am wrong))
once all this done and rebooted. Your phone will have TWRP and would be Rooted. Choose the TWRP manager to boot into recovery when you want.
I preferred to reboot the phone every time just to be sure...
If you have any comments, or i wrote something wrong, don't hesitate to correct me.
Have fun
UPDATE : Thanks to @autoprime you can also update your H815 EU to the latest Stock ROM : 10C (don't forget to thank him, as those guys are working hard to make your life easier!)
@the_scotsman, maybe you can pin this to help the lost souls until a one app does it all appears?

Well that was quick.

mediumraresteak said:
Well that was quick.
Click to expand...
Click to collapse
Looks like it depends on getting info from LG... let's see how long that lasts!

Forgive me if im mistaken but there are already like 3 threads about this i believe.
Sent from my LG-H815 using Tapatalk

I read the LG boot unlock affects streaming services. Can you tell me if it's still possible to stream music from the google play music app, and also YouTube ? Cheers.

barondebxl said:
Forgive me if im mistaken but there are already like 3 threads about this i believe.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
I have seen threads discussing about it yes, but haven't seen a clear guide on "how to" do it. Please enlighten me and i will ask this thread to be deleted. I don't like multi threads on the same subject, so i would be the first to ask that this thread be deleted.
pcoulson said:
I read the LG boot unlock affects streaming services. Can you tell me if it's still possible to stream music from the google play music app, and also YouTube ? Cheers.
Click to expand...
Click to collapse
I haven't had any issues with DRM, Camera or netflix streaming

SAO said:
I have seen threads discussing about it yes, but haven't seen a clear guide on "how to" do it. Please enlighten me and i will ask this thread to be deleted. I don't like multi threads on the same subject, so i would be the first to ask that this thread be deleted.
I haven't had any issues with DRM, Camera or netflix streaming
Click to expand...
Click to collapse
Yeah there arent any other guide, just threads discussing it. It just seems a lot since the LG site is pretty clear and self explanatory.
Sent from my LG-H815 using Tapatalk

I'm stuck on "fastboot oem device-id" command in cmd. Everything up to that point goes smoothly.
command line says "waiting for device" and the phone screen doesn't show phone ID, but gives me options 1-3. 1 being to show device ID, can't remember what the other ones are now. But I can't select "1". What am I doing wrong?
I have USB debugging on, also the OEM unlock is checked in development options.

Eclap78 said:
I'm stuck on "fastboot oem device-id" command in cmd.
command line says "waiting for device" and the phone screen doesn't show phone ID, but gives me options 1-3. 1 being to show device ID, can't remember what the other ones are now. But I can't select "1". What am I doing wrong?
Click to expand...
Click to collapse
unplug your device, if you can't restart it, by keeping your finger pressed for 10 seconds on the power button, take battery out.
Once you put the battery back in, restart the phone, plug in the phone in the computer, restart the CMD, and start the procedure again. :
2. launch your CMD and type:
Code:
adb reboot bootloader
your phone will reboot
3. type this to get your Device ID
Code:
fastboot oem device-id

SAO said:
unplug your device, if you can't restart it, by keeping your finger pressed for 10 seconds on the power button, take battery out.
Once you put the battery back in, restart the phone, plug in the phone in the computer, restart the CMD, and start the procedure again. :
2. launch your CMD and type:
Code:
adb reboot bootloader
your phone will reboot
3. type this to get your Device ID
Code:
fastboot oem device-id
Click to expand...
Click to collapse
I've tried this a few times now, same outcome, same thing, don't get a code, only get the 3 options and the power off 10 second thing, which doesn't work btw, have to pull battery every time

The numbers should show on your CMD window on your computer not the phone.
If the CMD window only shows "waiting for device", did you try to shut the CMD windows?

SAO said:
The numbers should show on your CMD window on your computer not the phone.
If the CMD window only shows "waiting for device", did you try to shut the CMD windows?
Click to expand...
Click to collapse
ah, thought they were supposed to show on the phone screen.
not sure what you mean by shutting the cmd window? I just get stuck on that "waiting for device" message in cmd, at which point I unplugged the phone, did a battery pull and tried again. I've tried about 5 times now, I double checked everything, have all the drivers installed etc.
Oh, and I do have the h815 EU version of the G4. I'll keep digging.

Could someone try out netflix, camera, divx files, YouTube and all the things that people were afraid of loosing. I for myself would really like to root but I dont want to loose any functions by doing that.
Sent from my LG-H815 using Tapatalk

Pyrres said:
Could someone try out netflix, camera, divx files, YouTube and all the things that people were afraid of loosing. I for myself would really like to root but I dont want to loose any functions by doing that.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
I have no issues with Netflix, divx, camera or YouTube.

Just a reminder that this does not work with all H815's as of 6/5/15. I think those of us that got a non EU region specific H815's get stuck when requesting a bootloader unlock from LG. Most of us are getting "not found suffix" when trying to submit the IMEI# and device ID. Note: trying different internet browsers does nothing, so don't bother.
We'll have to wait for LG to either approve all region G4's or another method. Cheers for making a guide though.

AhsanU said:
Just a reminder that this does not work with all H815's as of 6/5/15. I think those of us that got a non EU region specific H815's get stuck when requesting a bootloader unlock from LG. Most of us are getting "not found suffix" when trying to submit the IMEI# and device ID. Note: trying different internet browsers does nothing, so don't bother.
We'll have to wait for LG to either approve all region G4's or another method. Cheers for making a guide though.
Click to expand...
Click to collapse
Thanks for the heads up.. i have put this in red in the first post.

Eclap78 said:
I'm stuck on "fastboot oem device-id" command in cmd. Everything up to that point goes smoothly.
command line says "waiting for device" and the phone screen doesn't show phone ID, but gives me options 1-3. 1 being to show device ID, can't remember what the other ones are now. But I can't select "1". What am I doing wrong?
I have USB debugging on, also the OEM unlock is checked in development options.
Click to expand...
Click to collapse
Got the same Problem and fixed it, because, that are restriction/Firewall/Domaincontroler/Groupright Problems on ur PC.
Here the link, were i short explain my problem. http://forum.xda-developers.com/g4/general/howto-unlock-twrp-root-1-thread-t3130538
And now i see there is a HOWTO Thread
SO i have doubled it :crying:
But same answers like here "we got like 5 Threads", but like u said @SAO NOT 1Thread were all-in-one is explained! :good:

Is there a reason why we have to temporarily boot into TWRP to install root and then install TWRP via a secondary method?
Like, why can't we just do a "fastboot flash recovery twrp.img" command to install TWRP like most other devices with an unlocked bootloader?

Does this method break DRM?

takuhii said:
Does this method break DRM?
Click to expand...
Click to collapse
yes

AT&t Huawei Ascend XT H1611 Rooting Help.

I have unlocked the bootloader but I can not figure out how to root this thing at all. Has anyone had any success? I would like TWRP and SuperU.

this device is new yet. give it time

Tmobilefan906 said:
this device is new yet. give it time
Click to expand...
Click to collapse
Yeah I didn't realize how new this was whenever I posted it.

TWRP and root instructions available now in post 1 of
https://forum.xda-developers.com/android/general/huawei-ascend-xt-h1611-t3507933/
dabadguycr said:
I have unlocked the bootloader but I can not figure out how to root this thing at all. Has anyone had any success? I would like TWRP and SuperU.
Click to expand...
Click to collapse

divineBliss said:
TWRP and root instructions available now in post 1 of
https://forum.xda-developers.com/android/general/huawei-ascend-xt-h1611-t3507933/
Click to expand...
Click to collapse
You've already been helping me before you posted this.

People reading this thread might not realize we have root now. It's for their benefit .
dabadguycr said:
You've already been helping me before you posted this.
Click to expand...
Click to collapse

divineBliss said:
People reading this thread might not realize we have root now. It's for their benefit .
Click to expand...
Click to collapse
Good Point, I know my thread shows up first on Bing whenever I search for my phone and rooting help.

I have another XT and followed all instructions fine but no SuperSU when checking the phone. I tried flashing it twice (the one from the OP in main thread) and nothing. Am I missing a step?
I had installed fine on the first phone. this new one is 100% stock, unlocked bootloader, installed TWRP successfully but no supersu and root checker confirms no root.

Is it B140 or what? If you are missing a step, only you can check that.
powerserge1 said:
I have another XT and followed all instructions fine but no SuperSU when checking the phone. I tried flashing it twice (the one from the OP in main thread) and nothing. Am I missing a step?
I had installed fine on the first phone. this new one is 100% stock, unlocked bootloader, installed TWRP successfully but no supersu and root checker confirms no root.
Click to expand...
Click to collapse

divineBliss said:
Is it B140 or what? If you are missing a step, only you can check that.
Click to expand...
Click to collapse
Fixed

Can someone check the EMUI Huawei website for the unlock bootloader? Is it still working for requesting code? It keeps loop me back to the EMUI 5.0 page

sweetboy02125 said:
Can someone check the EMUI Huawei website for the unlock bootloader? Is it still working for requesting code? It keeps loop me back to the EMUI 5.0 page
Click to expand...
Click to collapse
Ya same. I got angry since I spent hours trying to find it so I just paid $4 and had DC-Unlocker unlock my bootloader.

sweetboy02125 said:
Can someone check the EMUI Huawei website for the unlock bootloader? Is it still working for requesting code? It keeps loop me back to the EMUI 5.0 page
Click to expand...
Click to collapse
webosFTW said:
Ya same. I got angry since I spent hours trying to find it so I just paid $4 and had DC-Unlocker unlock my bootloader.
Click to expand...
Click to collapse
If you follow this guide there should be no issue. The rootmygalaxy link should be pretty straightforward at unlocking the bootloader. The guide should be stickied in the OP.
https://forum.xda-developers.com/showpost.php?p=70515102&postcount=649

powerserge1 said:
If you follow this guide there should be no issue. The rootmygalaxy link should be pretty straightforward at unlocking the bootloader. The guide should be stickied in the OP.
https://forum.xda-developers.com/showpost.php?p=70515102&postcount=649
Click to expand...
Click to collapse
The issue is that https://emui.huawei.com/en/plugin.php?id=unlock that page hasnt worked for days. Keep redirecting me to the main page.

webosFTW said:
The issue is that https://emui.huawei.com/en/plugin.php?id=unlock that page hasnt worked for days. Keep redirecting me to the main page.
Click to expand...
Click to collapse
Yes use a different browser. Not working with chrome but working with edge. Go to the same link, it will bring you to EMUI 5.0 page, towards the top click on "download" then on the following page under the search bar click on "unlock bootloader" and it will bring you to the unlocking page. Just confirmed working. Updating the guide and will make a new post for root and twrp
Updated guide: https://forum.xda-developers.com/android/development/huawei-ascend-xt-h1611-feb27-2017-t3564389

Unlocked the boot loader, now adb/fastboot-15 Second won't work
Hello guys!
I used the 15 Second minimal adb/fastboot package from this site to unlock the boot loader. All seemed to go well, a screen message said success or something like that. It's been over 2 weeks since I had to put the phone down and take care of some other business. Now, after turning the phone off and then back on again when I am ready when I type in "fastboot devices" in the elevated cmd window in the adb directory the only message that comes back is "waiting on the device." Or the equivalent. I have tried what I could find from searching with Google to no avail. I am pretty sure that I am using the same cord, laptop, and everything that worked when I unlocked the boot loader. So, I am at a loss.
My goal originally was to use madvane20's slim downed version of b180 just to get it working again as my almost 2 years old P10 was stolen. I have no money in my budget for a new phone until Feb. 2020. I last talked with him in a series of PM's ending around May of last year, when a reply stated he had to get back to work on the last part of it. I have since seen a post referencing that it was ready in a package that after I had successfully unlocked the boot loader, it would root and install everything. This would have made me a happy guy... but I also noticed a custom ROM is now to be had based on Android 7. In order to get my Bank App's updated version of it's Mobile App to work, I have to install Android v 7 or higher. That's the main app that needs v 7 or better that I use daily. Several times...
But, now when I power up the phone, the first message is, "Your device has been unlocked and cannot be trusted... Press the Power Key now to reboot. Or the device will automatically reboot in 5 seconds." Which it does, the first time walking me through the Set-Up process, now it just boots into Huawei's EMUI 4.1. But, I cannot get adb to find the phone to follow the remainder of the instructions in the guide, "AT&T Huawei Ascend XT H1611 Feb27, 2017 update all things Root and TWRP (guide)"
Nor, can I get into the Recovery mode using the Vol Down/Power Keys.
So, where have I gone wrong or what is my next step? Since the phone can not be found and I can not get into Recovery using the proper keys what do I need to do and how do I do it?
I want to:
Root the phone.
Install the custom ROM I mentioned.
Or, Install an upgrade, if possible, to Android v 7... But,
can not get the phone recognized to get into a Recovery mode (is that right?) to push TWRP to it as well as the other files
it needs and to do whatever the Guides tell me to do.
Specs on the phone:
Model: H1611
Build: H1611C07B180
EMUI v: 4.1
Android v: 6.0.1
Security Patch level: September 1, 2017
Baseband v: 20234
Kernal v: 3.10.49-g03b627c
Sorry for the long post, but I thought it might answer some questions that came to mind before replying back.
Thanks in advance. I'm not here often, but when I am I am always relieved to get out of some jam I have gotten myself into!
mike0921

mike0921,
What happens if the phone is in normal mode and you type "adb devices" from the PC adb directory command prompt?

divineBliss said:
mike0921,
What happens if the phone is in normal mode and you type "adb devices" from the PC adb directory command prompt?
Click to expand...
Click to collapse
I just now found a new(er) USB cable for the phone. I also uninstalled the H1611 under Portable Devices in the Device Manager and rebooted the laptop. Where before, under Events the message was ".... needs further installation..." it now showed a successful install.
At the "adb devices" command, nothing happened, no response. I went and found the directions and explanations for the use of the top 30 commands. It told me to reboot the bootloader. A screen on the phone had me confirm the RSA command. Afterwhich the Fastoot&Recovery Mode screen with the little green Android guy with the message Phone Unlocked, FRP Unlock messages.
I went back to the elevated cmd window and at the adb directory command prompt entered "fastboot devices" and Voila! There were some letters and numbers, five or six spaces and the word "fastboot."
So, am I good to go with the rest of the steps in the guide from here? A question, about him saying to flash the Superuser zip file using TWRP. Is that suppose to already be on my SD card to flash it or can I flash it from my laptop without having to touch the phone or current USB cable? It seems stable but I am a bit gunshy and don't have much faith left in the old equipment I am having to use. A very old, refurbished HP Elitebook 8460P which is running really wonky, a not too new USB cable, the last of five I dug up and have used and finally works but is a bit loose, and Windows 10 1903 etc., which has disappeared all kinds of things I am having to run down) Can I use the "push" command to move the zip file to the SD card? And is that a fastboot function or an adb function? I seem to have read somewhere along the way to this point here that "push" is what I want to do, but powerserge1's Step 7 states to flash it using TWRP. I just want to check. And should questions from here on out be placed in his 184-page thread? I still haven't managed to read the whole thing, it seems to go off in so many other directions that I don't think I need to travel down. But, I will follow your advice.
I want to say a hearty thanks for your help. I was stuck, confused and frustrated at getting no results from Googling and reading for hours and getting nowhere it seemed. And I think I am good to go now.
Thoughts? Suggestions?
Just to be clear, The SuperSU zip file is currently on my laptop in the adb directory. Not on the phone.

mike0921 said:
I just now found a new(er) USB cable for the phone. I also uninstalled the H1611 under Portable Devices in the Device Manager and rebooted the laptop. Where before, under Events the message was ".... needs further installation..." it now showed a successful install.
At the "adb devices" command, nothing happened, no response. I went and found the directions and explanations for the use of the top 30 commands. It told me to reboot the bootloader. A screen on the phone had me confirm the RSA command. Afterwhich the Fastoot&Recovery Mode screen with the little green Android guy with the message Phone Unlocked, FRP Unlock messages.
I went back to the elevated cmd window and at the adb directory command prompt entered "fastboot devices" and Voila! There were some letters and numbers, five or six spaces and the word "fastboot."
So, am I good to go with the rest of the steps in the guide from here? A question, about him saying to flash the Superuser zip file using TWRP. Is that suppose to already be on my SD card to flash it or can I flash it from my laptop without having to touch the phone or current USB cable? It seems stable but I am a bit gunshy and don't have much faith left in the old equipment I am having to use. A very old, refurbished HP Elitebook 8460P which is running really wonky, a not too new USB cable, the last of five I dug up and have used and finally works but is a bit loose, and Windows 10 1903 etc., which has disappeared all kinds of things I am having to run down) Can I use the "push" command to move the zip file to the SD card? And is that a fastboot function or an adb function? I seem to have read somewhere along the way to this point here that "push" is what I want to do, but powerserge1's Step 7 states to flash it using TWRP. I just want to check. And should questions from here on out be placed in his 184-page thread? I still haven't managed to read the whole thing, it seems to go off in so many other directions that I don't think I need to travel down. But, I will follow your advice.
I want to say a hearty thanks for your help. I was stuck, confused and frustrated at getting no results from Googling and reading for hours and getting nowhere it seemed. And I think I am good to go now.
Thoughts? Suggestions?
Just to be clear, The SuperSU zip file is currently on my laptop in the adb directory. Not on the phone.
Click to expand...
Click to collapse
And after backing up in TRWP, I just checked the SD card's contents for the backup and saw the SuperSU zip file neatly placed on it as well. Just to be clear!??!
Okay, I somehow screwed this up I think. I was a little distracted by a friend dropping by. After telling her to give me a minute, I looked back at the phone after following Step 6:
Step 6: Confirm phone goes to FASTBOOT & RESCUE mode.
a) fastboot devices (to make sure your device is recognized)
b) fastboot boot TWRP.img (boots TWRP.img from Step 3)
c) The phone will boot into TWRP. Always select Keep Read Only from the first screen every time you go into TWRP.
Peek around a bit if you want to, then use TWRP to backup your stock recovery to external micro SD.
d) Reboot bootloader from inside TWRP to flash this custom recovery image (no adb command this time, you are rebooting to the bootloader from TWRP, you will see this option under "reboot" in TWRP).
e) fastboot flash recovery TWRP.img (now flashes TWRP recovery to the phone)
I then went to Step 7:
Step 7: After phone reboots, get into TWRP recovery repeating Step 6, a and b or hold the power button and volume up button from power-off state, then release when you see Huawei logo.
But now, the phone isn't being recognized again. And when I shut it off, hold Volume Up and Power buttons, I get a screen that asks if I want to: Reboot system now; Wipe data/factory reset; Wipe cache partition. Not the Recovery Screen with the options I got used to seeing in little green characters.
I tried the Reboot system now option and I'm back into the Huawei EMUI with everything appearing unchanged. Powered off, did the Vol Up + Power buttons and am back with the screen offering the three options I mentioned above. And the phone not being recognized after the "Devices" command.
Can you clarify my confusion? What am I doing wrong? Or not doing?
Thanks.
mike
---------- Post added at 06:47 PM ---------- Previous post was at 05:53 PM ----------
mike0921 said:
I just now found a new(er) USB cable for the phone. I also uninstalled the H1611 under Portable Devices in the Device Manager and rebooted the laptop. Where before, under Events the message was ".... needs further installation..." it now showed a successful install.
At the "adb devices" command, nothing happened, no response. I went and found the directions and explanations for the use of the top 30 commands. It told me to reboot the bootloader. A screen on the phone had me confirm the RSA command. Afterwhich the Fastoot&Recovery Mode screen with the little green Android guy with the message Phone Unlocked, FRP Unlock messages.
I went back to the elevated cmd window and at the adb directory command prompt entered "fastboot devices" and Voila! There were some letters and numbers, five or six spaces and the word "fastboot."
So, am I good to go with the rest of the steps in the guide from here? A question, about him saying to flash the Superuser zip file using TWRP. Is that suppose to already be on my SD card to flash it or can I flash it from my laptop without having to touch the phone or current USB cable? It seems stable but I am a bit gunshy and don't have much faith left in the old equipment I am having to use. A very old, refurbished HP Elitebook 8460P which is running really wonky, a not too new USB cable, the last of five I dug up and have used and finally works but is a bit loose, and Windows 10 1903 etc., which has disappeared all kinds of things I am having to run down) Can I use the "push" command to move the zip file to the SD card? And is that a fastboot function or an adb function? I seem to have read somewhere along the way to this point here that "push" is what I want to do, but powerserge1's Step 7 states to flash it using TWRP. I just want to check. And should questions from here on out be placed in his 184-page thread? I still haven't managed to read the whole thing, it seems to go off in so many other directions that I don't think I need to travel down. But, I will follow your advice.
I want to say a hearty thanks for your help. I was stuck, confused and frustrated at getting no results from Googling and reading for hours and getting nowhere it seemed. And I think I am good to go now.
Thoughts? Suggestions?
Just to be clear, The SuperSU zip file is currently on my laptop in the adb directory. Not on the phone.
Click to expand...
Click to collapse
And after backing up in TRWP, I just checked the SD card's contents for the backup and saw the SuperSU zip file neatly placed on it as well. Just to be clear!??!
Okay, I somehow screwed this up I think. I was a little distracted by a friend dropping by. After telling her to give me a minute, I looked back at the phone after following Step 6:
Step 6: Confirm phone goes to FASTBOOT & RESCUE mode.
a) fastboot devices (to make sure your device is recognized)
b) fastboot boot TWRP.img (boots TWRP.img from Step 3)
c) The phone will boot into TWRP. Always select Keep Read Only from the first screen every time you go into TWRP.
Peek around a bit if you want to, then use TWRP to backup your stock recovery to external micro SD.
d) Reboot bootloader from inside TWRP to flash this custom recovery image (no adb command this time, you are rebooting to the bootloader from TWRP, you will see this option under "reboot" in TWRP).
e) fastboot flash recovery TWRP.img (now flashes TWRP recovery to the phone)
I then went to Step 7:
Step 7: After phone reboots, get into TWRP recovery repeating Step 6, a and b or hold the power button and volume up button from power-off state, then release when you see Huawei logo.
But now, the phone isn't being recognized again. And when I shut it off, hold Volume Up and Power buttons, I get a screen that asks if I want to: Reboot system now; Wipe data/factory reset; Wipe cache partition. Not the Recovery Screen with the options I got used to seeing in little green characters.
I tried the Reboot system now option and I'm back into the Huawei EMUI with everything appearing unchanged. Powered off, did the Vol Up + Power buttons and am back with the screen offering the three options I mentioned above. And the phone not being recognized after the "Devices" command.
Can you clarify my confusion? What am I doing wrong? Or not doing?
Thanks.
mike

Sorry for the delay. What's the latest status with attempts to root the phone?

[Sharing Method] Bootloader Locked+Dead Boot+OEM Lock+Recovery Stuck

Hello XDA
As title say, I 'm going share my experience in this thread.
History
I purchased this device almost 8 month back.Purchased from a local store.Was very smooth and i was satisfied with the performance.Battery was good.Got regular update and these updates are from google,so why not install it,right?Then this Android N came,and i was so happy.7.0.0 was good.Then the nightmare 7.1.2 came.Phone started to lag continuously,Battery drained too much.But I was like Okay.May be this will fixed in new update.Then suddenly one day my phone was stuck.Not booting.Stucked at Google.I understood that phone already booted and fingerprint was too working but it showed nothing on display just black light.I was afraid as i didn't purchase it from Google Play or any authorized seller.So no warranty or chance of having replacement.So I started searching about this issue and found not only me many people are facing this.But there are no proper guideline or solving this issue.Tried everything and ended up with Locked Bootloader Irony!
Journey
As i never try to mess with my phone because it was Nexus 5x! So i never touch OEM or try to unlock the bootloader.So i tried to access stock recovery,But Alas! in recovery Volume up and down wasn't working.So I couldn't wipe or factory reset.So Now ended up with :
1.Locked Bootloader
2.Locked OEM
3.Recovery Stuck
Googled and found many solutions but none of them came to solve my issue.So i thought why not flash stock rom.But HOW! Cause fastboot only work with unlocked bootloader.And you can't unlock bootloader when your OEM is locked and you can't unlock it with fastboot.It can be only unlocked from developer option only.GOD!
Now I have only 2 options left:
1.Fastboot mod where no functions working
2.Download Mod (This will save you)
Now fastboot option is out and only download mod option is available.So what can i do with Download Mod?
LGUP TOOL helped me.Downloaded a tot file for Global version (LGH791) and flashed it and stucked at google logo and in recovery too.But next time i flashed the same file in a different way.Ok here it is:
1.Drivers are important here.I'm using windows 10.I have adb and fastboot and Lg drivers.Workplace okay.
2.Opened device manager and change the com port of Android phone 3 to 41. Port Changed!
3.Connected my phone to pc using 3rd party cable (Careful here,try to use original cable.) and entered into download mod and.
4.Opened LGUP Tool ,checked REFURBISHED mod,checked BIN file and select the tot file downloaded before.And quicky close it.(No need to click start)
5.Then again opened lg tool and click start.(BIN Checked and it showed the previously selected tot file).No need add anything new this time,just open and click START.
6.Rebooted and again stucked at Google screen.But wait! recovery is working.Pressing and holding volume up button for a while then a android logo with red cross inside will come up.Now holding power button and volume down button at the same time,Recovery will show and menu is working.Great!
7.Now Wiped cache and factory reset.And after that selected Apply update from Adb sideload
8.My device was connected to pc from the beginning,right? Now i downloaded a file previously called bullhead-ota-opp2.170420.019-c449d2bb.zip from Google Nexus 5x OTA update page.
9.In Adb folder,copied the file and named it ota.zip.Opened a command prompt using shift+right click in the folder.Phone was on Adb sideload mode.Typing this command adb sideload ota.zip
10.This took more than 8-9 minutes to finish.After flashing and phone rebooted.WOW
11.Couldn't believe my eyes.The OTA update was about Android O.I quickly enabled the developer menu and made oem unlcocked and usb debugging on.Boot into bootloader and unlock bootloader with this command fastboot flashing unlock
12.Now bootloader is unlocked and i flashed TWRP recovery for future need.
13.Rebooted the phone and after using for 1 minute the phone freezed again
14.This is the end of the story for today.
Planning
I'm thinking the OTA update was the problem.Now I'm downloading 6.0.1 version.And will do a clean install.Let's see what happens next.
Any kind of help is appreciated.If you think there is something i'm missing here then please suggest.
And Thanks to XDA.I got all these helps from here.Will update the post tomorrow.

You downloaded Android O Developer Preview. Final OTAs are here:
https://developers.google.com/android/ota
Just try flashing newest Factory Image via fastboot, but don't forget to flash TWRP back:
https://developers.google.com/android/images

TBH I NEVER thought this phone will be dead by hardware failure all of a sudden, I dont mind another few hundreds bucks but the problem now is the fking data within it.
Cant even pass google logo if you choose Recovery Mode
GG LG, well played

I have a 16gb variant dead....same issue like urs .....can i use the same lgh791 tot file?... in fastboot it says lgh791 16gb

usefully
usefully

I STRONGLY recommend that the original post is corrected to change "Download mod" to "Download mode" in all of its four occurences.
Same for one ocurrence of "Fastboot mod".
It is horribly confusing as it is, as calling them "mod" implies some modification you have to apply to the phone (be it software or hardware).

same of my expirience, flash 4CoreOreo..
my nexus 5x now is fully working

the_uker said:
I STRONGLY recommend that the original post is corrected to change "Download mod" to "Download mode" in all of its four occurences.
Same for one ocurrence of "Fastboot mod".
It is horribly confusing as it is, as calling them "mod" implies some modification you have to apply to the phone (be it software or hardware).
Click to expand...
Click to collapse
I suppose that makes sense. Then again, when an instruction is telling you to boot into download mod.....using common sense I'm gonna understand that's a typo and they meant download mode. But you're right, for some folks that may be a bit of a challenge. Common sense isn't as common as it was when I was young.

And the links?
I'm brazilian and i'm having a hard time to find the links to download stuff. Mine is dead and bootloader blocked. The tutorial seems to work but i can't understand well

Interesting. Thanks

How I Rooted Walmart Onn Tablets (No TWRP Needed)

I'll be making a video for this with the 7 inch tablet on Nov. 29th or 30th (depending on the time I have)
General Disclaimer: I'm not responsible if you brick your tablet. This is how I did it personally as other methods here didn't work for me. I have yet to test this method on a 7 inch, also do not have access to the Surf variants. This has only been tested on the 10.1 inch with the keyboard. Will update when I test with the 7 inch.
What's Needed:
MTK Fastboot Drivers: https://online.mediatek.com/Public Documents/MTK_Android_USB_Driver.zip
Magisk Manager Canary: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Stock Boot Image: https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227
ADB and Fastboot: https://www.xda-developers.com/what-is-adb/
Prerequisites:
Personally, I had issues getting my PC to recognize the tablets in Fastboot mode. The drivers wouldn't install. This might be optional for some of you, but I thought I'd include it just in case.
Installing MTK Fastboot Drivers from the link above
If you plugin your device in fastboot mode and your PC doesn't recognize it, follow these steps. If it did, skip this part.
1.) Download the drivers above and unzip the Zip file somewhere on your PC (desktop or My Documents is easiest)
2.) Boot your Tablet into Fastboot Mode by holding Vol + and Power, then select Fastboot from the Menu
*NOTE* There is a bug with these tablet's that the volume buttons are mislabeled. Really dumb, but I guess that's why they were 55 bucks for the 10 inch on black friday
3.) Plug the device into your PC and open Device Manager by pressing WinKey+R and typing devmgmt.msc, hit Enter
4.) If there's an Other Device listed called Android, follow these steps. If it isn't there, follow the next set of steps
5.) Open a Command Prompt window as Admin and type the following command
Code:
bcdedit.exe /set nointegritychecks on
6.) Hit enter, then restart your PC
7.) Once the PC is restarted, make sure your tablet is connected in Fastboot mode and open Device Manager again
8.) Right click Android under Other Devices and select Update Drivers
9.) Click the Browse my Computer for driver software button and select the MTK Folder you extracted from the download link above
10.) From there, you can open command prompt, type fastboot devices and see if your tablet shows up and move on to root!
Unlocking your Bootloader
From here, you can unlock your bootloader very easily to Root your device
This will wipe all data off the tablet!
0.) Enable OEM Unlock and USB Debugging on the tablet by going to Settings->About and tap Build Number 7 times. From here, enter the new Developer Options that unlock and turn on OEM Unlock and USB Debugging.
1.) Boot your tablet into Fastboot mode and connect it to your PC
2.) Open a Command Prompt window and type the following command, then hit enter
Code:
fastboot flashing unlock
3.) Follow the instructions on screen to unlock your bootloader
4.) Now Boot your device and we'll move on to making a rooted Boot Image
Creating a Rooted Boot Image with Magisk Manager
0.) Make sure you already have Wifi setup and connected before the first time you open Magisk Manager on your device! Make sure it auto connects as well
1.) Download Magisk Manager Canary from the link above
2.) Install it to your device
3.) Download boot Image from the Stock Boot Image part of the Prerequisites above and put the boot.img on your devices internal memory
4.) Open Magisk Manager and select Install Magisk
5.) Select Patch File and select the boot.img from your internal storage
6.) Once its done patching the image, take magisk_patched.img from the downloads folder of your device and move it onto your PC
7.) Boot your tablet into Fastboot mode and plug it into your PC
8.) Open Command Prompt and type the following command and hit enter (make sure you know your magisk_patched.img file location)
Code:
fastboot flash boot magisk_patched.img
9.) Reboot the device and you'll be Rooted!
Optional Steps like Modules and Debloating
My basic debloat script: https://forum.xda-developers.com/wa...s-general/root-walmart-bloat-remover-t4011639
Will be testing GSI roms on the spare 7 inch and will list those here
Recommended Magisk Modules:
Viper4Android Legacy
FDE.AI
MagiskHide Props Config
Systemless Hosts
Youtube Vanced Black
Magisk Setting to Enable:
Magisk Hide
Rename Magisk Manager App (keeps app from detecting magisk root)
Credits:
Myself for this root method @byproxy for reminding me to add the steps for OEM Unlock and enabling wifi before opening Magisk Manager for the first time

I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.

Are you online? I had the same problem.
Xavster2 said:
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Click to expand...
Click to collapse

Xavster2 said:
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Click to expand...
Click to collapse
Sorry, been a busy few days, but make sure you're connected to Wifi, close Magisk Manager, then reopen it and you'll be good to go!

Onn 8" walmart tablet
I purchased the 8" Onn walmart tablet second hand from a store called dirt cheap. Box didnt look to be opened but it had been. The tablet had been setup with someones gmail account that i do not know. The tablet was for a 4yo girl to use to learn preschool. Is there just any simple way to remove this google FRP lock ? I dont care if i lose the info on it as its not mine. I just want her to be able to use the tablet. Any help would be much appreciated please

CoachDad said:
I purchased the 8" Onn walmart tablet second hand from a store called dirt cheap. Box didnt look to be opened but it had been. The tablet had been setup with someones gmail account that i do not know. The tablet was for a 4yo girl to use to learn preschool. Is there just any simple way to remove this google FRP lock ? I dont care if i lose the info on it as its not mine. I just want her to be able to use the tablet. Any help would be much appreciated please
Click to expand...
Click to collapse
Forced factory reset should do it. There is small pin hole near the power button. I believe pressing this hidden button(with a Sim card ejector, or paper clip).
If pressing does not do anything. Maybe press the button then hold power button too

mrmazak said:
Forced factory reset should do it. There is small pin hole near the power button. I believe pressing this hidden button(with a Sim card ejector, or paper clip).
If pressing does not do anything. Maybe press the button then hold power button too
Click to expand...
Click to collapse
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.

CoachDad said:
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
Click to expand...
Click to collapse
This is an mtk device not Samsung. So there is no Odin or download mode. There is spflash tool, and preloader.
And if you flash firmware (with default frp partition) then frp lock is cleared.
But you will have to find that file. It maybe in the stock firmwares that are shared, I do not know.

EDIT:
i was having issues but figure it out. maybe it should be so common knowledge that it shouldn't need to be included as a step, but since i don't do this THAT often i didn't think about it and it took me a bit to figure out why i was having issues.
once you get your computer to recognize your device (mine did without needing to mess with any drivers) you need to first make sure to got into the tablet settings -> about and then tap on the build number 7 times to access developer options. then you need to go into developer options and turn on OEM Unlocking & USB Debugging.
THEN follow the guide to unlock bootloader.
then (since the tablet is factory reset once you unlock) do the above AGAIN to turn USB Debugging back on after you reboot.
also note that you need to have an internet connection on the tablet to utilize magisk. once you got all that square, then continue on with steps for full root.
hope that helps!

byproxy said:
EDIT:
i was having issues but figure it out. maybe it should be so common knowledge that it shouldn't need to be included as a step, but since i don't do this THAT often i didn't think about it and it took me a bit to figure out why i was having issues.
once you get your computer to recognize your device (mine did without needing to mess with any drivers) you need to first make sure to got into the tablet settings -> about and then tap on the build number 7 times to access developer options. then you need to go into developer options and turn on OEM Unlocking & USB Debugging.
THEN follow the guide to unlock bootloader.
then (since the tablet is factory reset once you unlock) do the above AGAIN to turn USB Debugging back on after you reboot.
also note that you need to have an internet connection on the tablet to utilize magisk. once you got all that square, then continue on with steps for full root.
hope that helps!
Click to expand...
Click to collapse
I did not realize I didn't include that step. Total noob mistake when typing a tutorial up for android. I do this almost daily at work, so I forget to include it

CoachDad said:
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
Click to expand...
Click to collapse
I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot.

no worries! i didn't think about it either until i was having issues. thanks for the tutorial... it was super helpful!! btw it definitely works on the 8" tablet.

Hello! I'm new to all of this, but what I'm trying to accomplish is removing the Google account from this tablet and putting a new image on the ONA19TB002, ONA19TB003, ONA19TB007, Surf 7 and 10 tablets. I followed all of the steps as far as installing the drivers. I had to go through hoops to get the MediaTek Drivers installed, but I have a "warning" cone by it. I haven't been able to find any resolution to this. Any help would be appreciated. I' have a Windows 10 64-bit system that I'm using and the tablet I'm specifically working on at the moment is the ONN ONA19TB003 tablet. The tablet is not being recognized by my laptop when I run the 'fastboot devices' command in PowerShell. Is there something that I'm missing? Any help would be appreciated.

'Quis said:
Hello! I'm new to all of this, but what I'm trying to accomplish is removing the Google account from this tablet and putting a new image on the ONA19TB002, ONA19TB003, ONA19TB007, Surf 7 and 10 tablets. I followed all of the steps as far as installing the drivers. I had to go through hoops to get the MediaTek Drivers installed, but I have a "warning" cone by it. I haven't been able to find any resolution to this. Any help would be appreciated. I' have a Windows 10 64-bit system that I'm using and the tablet I'm specifically working on at the moment is the ONN ONA19TB003 tablet. The tablet is not being recognized by my laptop when I run the 'fastboot devices' command in PowerShell. Is there something that I'm missing? Any help would be appreciated.
Click to expand...
Click to collapse
Personally, I avoid PowerShell at all costs. This kinda stuff has always just seemed to work better with CMD.exe instead of Powershell.
These tablets are kind of a nightmare for this. If you've done the mediatek drivers and still have the warning cone icon, I'm not sure what's next as I haven't hit that wall myself. All I can maybe recommend is right click delete drivers in Device Manager, then start over with the driver install
Removing the Google Account would be needing a FRP Bypass. Someone above stated "I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot. " so if you can get it recognized, try that

KaptinBoxxi said:
Personally, I avoid PowerShell at all costs. This kinda stuff has always just seemed to work better with CMD.exe instead of Powershell.
These tablets are kind of a nightmare for this. If you've done the mediatek drivers and still have the warning cone icon, I'm not sure what's next as I haven't hit that wall myself. All I can maybe recommend is right click delete drivers in Device Manager, then start over with the driver install
Removing the Google Account would be needing a FRP Bypass. Someone above stated "I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot. " so if you can get it recognized, try that
Click to expand...
Click to collapse
Ok, thank you! This is a shot in the dark, but in order for ADB to work, USB debugging has to be enabled. I can't do that as the tablet is locked by FRP and I have looked countless times on Google and MSN to see if it's possible. Do you have any tips for that?

I don't know what I'm doing wrong, but for some reason I can't seem to get. The tablet to stay in fastboot mode. It just says waiting for device.

will this root onn 8 inch tablet running android 9

soateufel said:
I don't know what I'm doing wrong, but for some reason I can't seem to get. The tablet to stay in fastboot mode. It just says waiting for device.
Click to expand...
Click to collapse
Sorry for late reply. Been away from home with work. When fastboot mode indicates "waiting for device," it generally means that your device is not properly communicating with your PC or laptop. This is nearly always due to missing or incorrect drivers 9n your computer. There are several comprehensive guides here on XDA for installing necessary ADB & Fastboot drivers.

installed magisk manager on onn 8 and also have img zip but win i go to patch it magisk manager crashes

when you mean patch boot img do mean to unzip file on onn 8