Related
SOLVED
See my most recent post in this thread
______________________________________________________________________________________
Firstly, I've spent the last three days scouring XDA and some other forums searching for solutions and trying various options.
The screen on my N4 has cracked and I've lost the use of the bottom half of the touchscreen. This means that I can't unlock my phone.
The phone is insured and will be repaired, but there are photos of my son's first birthday on the internal memory that I don't want to lose. I'm concerned that the phone will be factory reset during a repair or I'll receive a replacement. I'm trying to access the internal memory remotely to backup these files before I send the phone off. The problem is that I hadn't enabled USB debugging before the accident. The phone is completely stock including the bootloader.
So I can access via fastboot but not via adb.
Q1: Can I pull file from the internal memory via fastboot
Q2: Can I enable usb debugging via fastboot
Q3: The phone is set to display as an MTP device in windows but as I can't unlock the screen, none of the files are showing. Is there anyway around this?
Q4: Purely via fastboot, can I unlock the bootloader, install CWM so to use ADB within it and then return to a stock bootloader?
I think they're my options. Any answers to the above or alternatives would be appreciated.
All of the other threads regarding this, the users seem to either already have CWM installed or they're looking to perform a factory reset. I did consider resetting the device via the bootloader in order to bypass the screenlock but I understand that on the N4 this wipes the internal memory as well.
Unlocking the device isn't needed to pull the files from it, just plug it in and get what you need from the internal memory
EddyOS said:
Unlocking the device isn't needed to pull the files from it, just plug it in and get what you need from the internal memory
Click to expand...
Click to collapse
On mine if I plug it in it appears as an MTP device but with no files. I then have to unlock the screen and select USB something-or-other from the notificationss bar, then the files appear in windows.
Strange, mine never needs to be unlocked...I'm using Windows 8 Pro btw but it also works fine in work on Vista Business
Only other thing I can think of is the fact I'm unlocked and running a custom ROM, I've never used my N4 stock. It was on CM within 30 mins of receiving the unit!
So over the last week I've managed to solve my problem. I've seen several other people asking for help with no luck so I'm posting this here in the hope that the search function will bring it up.
Firstly, my phone was completely stock running 4.2.2, unrooted, with the locked stock bootloader. USB Debugging WAS NOT enabled. I had pattern lock enabled when I dropped the phone. The screen cracked and the bottom half of the touchscreen was unresponsive.
The phone was insured, but I wanted to backup photos from the device before sending it off for repair/replacement.
HOW I FIXED IT.
Please note, you need at least some part of the screen to be working, specifically, some part of the screen where the pattern lock is.
You only need two pieces of software. The Android SDK and the Nexus 4 Toolkit http://forum.xda-developers.com/showthread.php?t=1995688
If you are running 4.2.2 you will need to update the toolkit. I also had the standard issues of installing the USB drivers for the N4. You need to get to a point where is shows up as an ADB device in Windows Device Manager.
As I didn't have USB debuggin enabled I couldn't connect tothe phone via ADB, but if you put it into recovery mode you can use Fastboot. Hold down the power key to turn the device off and turn it on while holding down Vol Down to load up recovery mode.
If you then start the N4 Toolkit, you should see the device listed as a fast boot device.
From within the toolkit unlock your bootloader.
Flash a temporary bootlader, (option 10) as the touchscreeen was broken it has to be CWM.
Once in CWM you can start to use ADB. Open up a DOS command prompt in Windows, go to your SDK/platform tools folder/ to access ADB.exe and you can use the pull command to copy folders to your PC. At this point, instead you can use applications like ADBexplorer or DroidExplorer to do the same thing through a nicer GUI.
If you'd like to still be able to use your phone, although without the touchscreen, you can load an unstable image to get into android and then use ADB to start changing system settings.
Firstly, before exiting CWM, clear the cache. Without doing this the phone jsut hung on the Nexus symbol while loading the image.
in the toolkit go to root/unroot options and select load unstable image(option 4 and then 6). This will fire you up into Android and it should be set up as you left it.
I wanted to enable bluetooth so to use a keyboard (I didn't have a mouse but this is a better option) from the DOS window type the following command
am start -a android.bluetooth.adapter.action.REQUEST_ENABLE
You should eventually get a pop-up on your screen saying that a request has been made to enable bluetooth. Hopefully your screen is working enough to select enable.
Then I use the workaround to disable the sceenlock, found here -> (http://www.addictivetips.com/androi...e-pattern-unlock-on-android-via-adb-commands/) I found method 2 worked for me. I imagine this will be stopped in a future update.
Method 1
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit
Method 2
adb shell rm /data/system/gesture.key
If either of these methods are successful you will be able to unlock the phone with an pattern, hence why you need to be able to touch some part of it.
From then, my bluetooth keyboard was already mated to my phone to I was able the navigate the menus to turn on USB Debugging, turn-off the screen lock and a few other bits and pieces I needed to do.
I then restarted (I was still working within the unstable image) and on reboot, all my changes had al been applied. No screen lock, bluetooth enabled and USB Debugging enabled.
Hopefully this will be of help to those in a similar position. Thanks has to go to the toolkit though which provides all the necessary access to carry this out.
I should probably add, you can use the toolkit to relock the bootlader if you're concerned about that and if you can't click the screen to enable bluetooth or mate a keyboard or mouse, once you have USB Debugging enabled you can use software like Screencast to control you phone's screen from a PC.
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Does unlocking bootloader via toolkit not wipe everything? How are you unlocking bootloader and still able to pull data off?
EDIT: it appears fastboot oem unlock on the Nexus 4 *does not* wipe data!
Carpetboy said:
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Click to expand...
Click to collapse
Please HELP, i can get to step 5...but then, when I try to use ADB via cmd (ie. adb shell), it says "error: device offline". what can it be? I don't know if this is a driver related issue (i've tried the toolkit drivers and the SDK drivers)...i'm desperated, I can't access the phone!!
Thanks in advance
not working for me
i'm in same boat with cracked screen. i can get CWM installed but i cant enabled usb debugging without touching the screen so i cant get adb working. how did you turn on usb debugging without the screen
Thanks for the guide.
Im curious on why youd want to boot an unstable(temporary) image after pulling the files using ADB in CWM recovery. Why not just wipe cache and reboot normally into Android ?
usb debugging without screen?
compsmart said:
i'm in same boat with cracked screen. i can get CWM installed but i cant enabled usb debugging without touching the screen so i cant get adb working. how did you turn on usb debugging without the screen
Click to expand...
Click to collapse
Can someone please walk me through how to do this? My screen is completely broken, but I can still turn on/off, I have reason to believe debugging is off because when I connect the phone (a Samsung galaxy sII skyrocket) to my Toshiba laptop via a micro USB, it makes a sound to signal that it's connected. Drives E and F then open up (but are empty) and then disappear. I have no idea what's going on but I absolutely cannot lose all of the data on this phone. Pictures and videos from my old blackberry Torch are on here too, making up about 4 years of my daughter's life that I would lose if I cannot retrieve. Also, I am not super -tech savvy, so if someone could help me I would be forever grateful.
Please!!
:crying:
almost the same issue
I have an Asus memo pad 10 (smart) some of the core apps have been corrupted, (keyboard, UI, launcher etc all the essential stuff) I've been trying to reinstall my UI and launcher from my computer when i found out that USB debugging was disabled. the tablet is basically unusable, i have no way of enabling from the tablet itself. is there a piece of script or something i could run from my PC to enable it?
any help would be greatly appreciated :crying:
bob mc bob said:
I have an Asus memo pad 10 (smart) some of the core apps have been corrupted, (keyboard, UI, launcher etc all the essential stuff) I've been trying to reinstall my UI and launcher from my computer when i found out that USB debugging was disabled. the tablet is basically unusable, i have no way of enabling from the tablet itself. is there a piece of script or something i could run from my PC to enable it?
any help would be greatly appreciated :crying:
Click to expand...
Click to collapse
My screen became unresponsive a while back. I ended up getting and OTG cable and plugging in a mouse. This allowed me to do everything as if the touchscreen was working. There's also an app called MyMobiler that let me plug in my device over USB and control my screen from my PC. Those two helped me enable USB Debugging, flash a custom ROM, root the phone, backup everything I needed, then restore the phone to stock. I hope this helps.
*Sorry for bumping such an old post*
Thanks for the really useful guide!
Could you or someone just confirm to me that unlocking the bootloader does not factory reset? The reason I'm doing this process is to access my personal data so it's important that I can keep it all.
I ask because at the unlock bootloader stage it implicitly warns me that there'll be a factory reset.
Thanks again!
HikerMan said:
*Sorry for bumping such an old post*
Thanks for the really useful guide!
Could you or someone just confirm to me that unlocking the bootloader does not factory reset? The reason I'm doing this process is to access my personal data so it's important that I can keep it all.
I ask because at the unlock bootloader stage it implicitly warns me that there'll be a factory reset.
Thanks again!
Click to expand...
Click to collapse
Unlocking to bootloader will wipe your device
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Unlocking to bootloader will wipe your device
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
In that case, I am confused as to how OP managed to unlock his bootloader. He actually states that the purpose of this was to retrieve data, like me.
Also, in a previous comment in this thread by jw95275, they claim that "it appears fastboot oem unlock on the Nexus 4 *does not* wipe data".
I am concerned about the conflicting answers so far, so will hold off for an explanation before I do anything. Thanks for the response!
HikerMan said:
In that case, I am confused as to how OP managed to unlock his bootloader. He actually states that the purpose of this was to retrieve data, like me.
Also, in a previous comment in this thread by jw95275, they claim that "it appears fastboot oem unlock on the Nexus 4 *does not* wipe data".
I am concerned about the conflicting answers so far, so will hold off for an explanation before I do anything. Thanks for the response!
Click to expand...
Click to collapse
You should just be able to "fastboot boot recovery.img" and boot CWM and then use ADB. W/O unlocking the BL
npjohnson said:
You should just be able to "fastboot boot recovery.img" and boot CWM and then use ADB. W/O unlocking the BL
Click to expand...
Click to collapse
This did not work for me. I have a Nexus 4 with a broken digitizer, locked bootloader, and usb debugging disabled. I need to grab some data off.
I've tried `fastboot flash recovery {{recovery .img}}` and `fastboot boot {{recovery .img}}` without unlocking the bootloader first, and via both methods, I get back "FAILED (remote: not supported in locked device)"
So I'm not sure how people are able to get into custom recovery without first unlocking BL/losing all their data. Can someone explain?
jinglejuice said:
This did not work for me. I have a Nexus 4 with a broken digitizer, locked bootloader, and usb debugging disabled. I need to grab some data off.
I've tried `fastboot flash recovery {{recovery .img}}` and `fastboot boot {{recovery .img}}` without unlocking the bootloader first, and via both methods, I get back "FAILED (remote: not supported in locked device)"
So I'm not sure how people are able to get into custom recovery without first unlocking BL/losing all their data. Can someone explain?
Click to expand...
Click to collapse
On some (few) Motorola devices (not nexus 4), you can fastboot boot without unlocking the BL.
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
Gonna try and cover as much as possible but dont be afraid to comment or correct me as I might forget to mention something
ZUK Z1 Specs:
5.5 inch IPS Screen
Snapdragon 801 @ 2.5GHz
3GB RAM
64GB Storage
Dual sim - 2G/3G/4G (doesnt have LTE band 20 unfortunately)
13MP camera with OIS and 8MP front
USB-C charging/data connector
Fingerprint reader
Wifi A/B/G/N/AC
GPS Glonass
Bluetooth 4.1
4100mAh battery
Activate developer settings and ADB + OEM unlock (needed for bootloader unlock among other things)
1. Open settings and scroll to bottom and press "About phone"
2. Scroll to bottom again and press 5 times on "Version" (the one above "SElinux-status") and it should say "developer settings now activated"
3. Press back button once and you should now have a new option "Developer Settings" above "About Phone"
4. Press "Developer Settings" and scroll down to USB debugging and activate it.
5. You can also find the OEM-unlock which unlocks bootloader. If nothing happens when you try to unlock the bootloader then you can use adb command to unlock instead.
Download "Android debug bridge", can recommend minimal ADB by shimp208
http://forum.xda-developers.com/showthread.php?t=2317790 and install it.
You also need adb driver for the phone
https://mega.nz/#!l8pVHIpT!UkcW3Jg4B7YilDjZatvLqGBi_R4vVUYVdkrsUL_Ve9k
or from the chinese site
http://bbs.zuk.cn/z1/t16224/
When driver and adb is installed then type "adb devices" to check if phone is detected. If its detected then you can type "adb reboot bootloader" and after that you might wanna check device manager that your phone driver is installed and working then type "fastboot -i 0x2b4c oem device-info" to see the bootloader lock status and type "fastboot -i 0x2b4c oem unlock" to unlock it, doublecheck with "fastboot -i 0x2b4c oem device-info" again to see if its actually says unlocked before you reboot. Either type "fastboot -i 0x2b4c reboot" or hold power button til it restarts.
Ps. If you are running windows 10 and have issues with adb not detecting any devices, then download updated binary (credits goes to mrcoldbird) and replace the three files in your adb installation https://www.androidfilehost.com/?w=...164e5e9c078239797e768e69027c4effaf26930b8050b
After you´ve replaced the files, type "adb kill-server" and then try "adb devices" again and it should hopefully work. Dont forget to authorize your computer on the phone when the dialog pops up or else you wont be able to perform any commands.
How to enter recovery mode, flash mode
To enter recovery mode you need to make sure phone is turned off.
Then you press and hold vol - and + (both yes) and push the power button and release as soon as the screen is lit (still hold vol+ and vol- until you see the recovery screen).
To enter flash mode you need to make sure phone is turned off.
Then you press and hold vol+ and insert the usb data cable and your computer should have found new hardware. The iffy part here is that the phone is only in flashmode for like 5sec or so, so you need to be quick. Flash mode is currently used for when you wanna unbrick phone or factory reset to the chinese android version called ZUI
How to enter diagnostic mode
There are 2 ways of doing this, the first way is making sure no cable is inserted into phone and turning the phone off. Then hold vol+ and insert usb cable and it will be in diag mode for a brief moment (which can be quite annoying)
The second way (which requires root) makes it easier to fiddle around in diag mode. Activate ADB in developer settings and plug in your phone and authorize it, then type
Code:
adb shell
su
setprop sys.usb.config rndis,diag,adb
and voila you got diag mode activated
Flash TWRP (recovery) onto your phone
Download a twrp file for this phone (credits to JoaoPaulo)
https://www.androidfilehost.com/?fid=24269982087019837
1. Make sure you have adb on pc, driver installed, phone developer settings activated and bootloader is unlocked. Just use the above guide where I explain how to "Activate developer settings and ADB + OEM unlock"
2. Plug in cable if it isnt already and type "adb devices" to check if phone is detected, if not then try "adb kill-server" and try "adb devices" again. If detected then type "adb reboot bootloader".
3. Again make sure phone still has connection with pc by typing "fastboot -i 0x2b4c oem device-info" (since "adb devices" mostly dont work in bootloader mode we use oem device-info command instead to check communication)
4. You can then type "fastboot -i 0x2b4c flash recovery TWRP-2.8.7.0-ham-fixSystem-fixADB.img" to flash the recovery onto phone.
5. If all good and no error messages then reboot phone by typing "fastboot -i 0x2b4c reboot" or hold power button til it restarts.
6. Check that recovery is there and works by shutting down phone, then press and hold vol+ and vol- and press power button til screen goes on then you can release it (still keep hold vol+ and vol- til recovery screen is up)
Flash ZUI, Unbrick phone or fix wierd issues such as problem with activating Wifi or bluetooth
First you need to download the QPST flash program
https://mega.nz/#!4tom3DqL!4a-rRcLef1yS6HJSrBfne_-r9atg6yF3kI_HW8lDaPY
And then you also need the ZUI rom file
https://mega.nz/#!chQkEAwR!IHeYRxWx38QdML6VxjPdVz08BgbZD-Z-xVuSG150qPU
And if you havent already fixed the driver then that aswell
https://mega.nz/#!l8pVHIpT!UkcW3Jg4B...UYVdkrsUL_Ve9k
After you installed QPST, you will get a bunch of programs associated to it, start QFIL from the QPST folder
Click browse on the programmer path row and select "prog_emmc_firehose_8974.mbn" from the directory where you unzipped the QPST ZUI ROM and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone, you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default. On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings), scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option to change language to english incase you cant make out the chinese and you should be good to go
Download and install Gapps
Open http://opengapps.org/
and for first column select "ARM"
Second column, if you are running CM12 or the ZUI 1.2.x for example it is 5.1 you want
If you are running CM13 or ZUI 1.5.x it is 6.0 you want.
Then last column is just how many of the google apps you want to have installed, you can press the link "Version Information" in red text at the bottom left to see the what each package contains.
I usually go with nano since you get the necessary apps to sync your account and then ill just download the rest I want/need from play store. Its also a smaller download so goes quicker to flash aswell
Activate Root on Cyanogenmod
First you need to activate developer settings if you havent already (tap version 5 times in "about phone"), then enter developer settings menu and there you´ll have an option called "Root access" which you can set to either "only apps" and "only ADB" or both. "Only apps" is preferred and thats it, you can now run root priveliged apps (after you have confirmed each apps authorisation).
Convert from ZUI to cyanogenOS/mod
Check the guide from Paul on Modaco for this
http://www.modaco.com/forums/topic/375804-convert-z1-from-zukui-to-cyanogen-os/
Troubleshooting
If you are having usb connectivety issues, please try using another PC. Can also be a bit iffy getting connection going with windows 10 so try windows 7 if possible. You could also run windows 7 in a virtual machine and get it working that way as an example.
Also when troubleshooting connectivety issues working with adb, dont forget to try and "adb kill-server" to reset the connection before you try adb commands again if phone isnt detected in the first place between any changes you may have made.
If you have issues with rom then its good to start fresh with a factory reset and if that doesnt help then flash zui through QPST and any issues should now be resolved unless there is a hardware issue ofc.
Keep in mind that you should almost always do a factory reset when doing a large update, like if you update from kitkat to lollipop then factory reset or from lollipop to marshmallow also factory reset but this also applies when you change from cyanogen to Zui for example regardless of it its lollipop or marshmallow. Only time when its ok to "dirty flash" (in my opinion) is when you do smaller updates such as updating nightly to nightly on CM12 or nightly to milestone/rc or final. Also applies on modified roms which uses CM12 as base, as long as you are staying on the same rom its fine but if you swap from modified cm12 to vanilla/stock cm12 then you might experience issues.
CM12 Nightly -> CM12 newer Nightly OK
CM12 Nightly -> CM12 Milestone OK
CM12 Nightly -> ZUI any version definately NOT OK
CM12 Nightly -> CM13 NOT OK
CM13 Nightly -> CM13 newer Nightly OK
CM12 MOKEE -> CM12 nightly NOT OK
CM12 MOKEE -> CM13 NOT OK
Stuff "might" work if you update from CM12 to CM13 and also going from a modified CM12 to vanilla or the other way around but it might also cause wierd issues which you might not think of, batterydrain, slow phone, force close etc etc
Downloads and links:
Driver Zuk Z1 Win Vista/7/8/10
https://mega.nz/#!l8pVHIpT!UkcW3Jg4B7YilDjZatvLqGBi_R4vVUYVdkrsUL_Ve9k
Flash program QPST
https://mega.nz/#!4tom3DqL!4a-rRcLef1yS6HJSrBfne_-r9atg6yF3kI_HW8lDaPY
Password: bbs.zuk.cn
Kernel
Chromakernel http://forum.xda-developers.com/zuk-z1/development/kernel-chroma-kernel-r1-tester-t3254724
Minimal ADB
http://forum.xda-developers.com/showthread.php?t=2317790
ROMS (mostly TWRP)
CyanogenOS 12.1 http://forum.xda-developers.com/zuk-z1/development/official-ota-update-links-ota-updating-t3226990 and http://forum.xda-developers.com/zuk-z1/development/rom-cyanogen-os-12-1-yog4pas3oh-t3248820
Cyanogenmod 12.1 http://forum.xda-developers.com/zuk...om-cyanogenmod-12-1-nightlies-lenovo-t3249009
Cyanogenmod 13 http://forum.xda-developers.com/zuk-z1/orig-development/unofficial-cm13-t3277885
Zui QPST version https://mega.nz/#!chQkEAwR!IHeYRxWx38QdML6VxjPdVz08BgbZD-Z-xVuSG150qPU
Zui 1.2.070 (Lollipop) http://bbs.zuk.cn/zui/t53638/
Zui 1.5.x (Marshmallow) http://forum.xda-developers.com/zuk-z1/development/android-6-0-official-zui-1-5-077-beta-t3270587
Exodus http://forum.xda-developers.com/zuk-z1/orig-development/rom-exodus-android-zuk-z1-t3244026
Mokee http://forum.xda-developers.com/zuk...om-mokee-opensource-project-official-t3254984
Toolkit
http://forum.xda-developers.com/zuk-z1/development/win-zuk-z1-toolkit-0-1-alpha-t3235964
Unlock Bootloader without wiping data
http://forum.xda-developers.com/zuk-z1/help/guide-unlock-bootloader-zuk-z1-wiping-t3251801
TWRP (Recovery) by JoaoPaulo
https://www.androidfilehost.com/?fid=24269982087019837
Thanks to everyone involved in helping making this a better device
Thanks to Breadcrust for the initial developing and help
Thanks to javirenart for porting a Toolkit to our device
Thanks to Paulobrien at Modaco for the guide on converting ZUI to CM
And whomever else I have forgotten to mention (shout at me and ill update)
Special thanks to @MrColdbird for fixing a working CM13 with Wifi/Data/GPS/DT2W/bugs and @JoaoPaulo for helping out and giving us an updated and fixed TWRP, kernel stuff and hopefully fingerprint reader!
Some recommended apps
Check hardware sensors
Sensor box for android https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
Check hardware and some sensors
CPUZ https://play.google.com/store/apps/details?id=com.cpuid.cpu_z
Underclock to gain more batterytime
Kernel Auditor https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
(Personally ive used 1497MHz on cpu keeping interactive governor and put GPU on 200MHz with great result, phone still feels snappy on CM13)
Reserved 2
Great job man....It's really helpful for everyone, instead of searching every where.
You forget how to unlock to boot loader without wiping the device
Tengo10 said:
You forget how to unlock to boot loader without wiping the device
Click to expand...
Click to collapse
Not sure how you would do that? Looked quickly if anyone had written any guides already about it but didnt see any and search function is temporary disabled or unavailable :/
@Titokhan and I tested it and it workes perfect... link: http://forum.xda-developers.com/zuk-z1/help/guide-unlock-bootloader-zuk-z1-wiping-t3251801
@Tengo10
which version you used to kingroot? the latest 4.6.5 b2?
Inviato dal mio Z1 utilizzando Tapatalk
Thanks for your work but some downloads needs password,also to unzip downloads is asked for password.
Can you provide them
---------- Post added at 12:29 PM ---------- Previous post was at 11:51 AM ----------
Thanks for your work but some downloads are asking for password,also in the downloads witch are not asking for password ,the zip files are asking for it.
Can you provide them please ?
fr4nkr0c said:
@Tengo10
which version you used to kingroot? the latest 4.6.5 b2?
Inviato dal mio Z1 utilizzando Tapatalk
Click to expand...
Click to collapse
Oh sry didn't get a message, the kingroot version was the newest but that's not interesting cause it loads the scripts from the web
Reserved
Enviado desde mi Z1 mediante Tapatalk
While trying to unlock band 20 on another phone I tried it on the zuk z1 aswell but didnt work, anyway found out how to enter diagnostic mode in a more permanent matter instead of the brief 5sec you get when using vol+ and inserting usb cable before the phone boots.
Ive added it in first post but the magic is
Code:
adb shell
su
setprop sys.usb.config rndis,diag,adb
unbrick phone method didnt work for me, fails when downloading through QFIL
Driver Zuk Z1 Win Vista/7/8/10
https://mega.nz/#!l8pVHIpT!UkcW3Jg4B...UYVdkrsUL_Ve9k
Could you please insert the correct link of MEGA?
Thanks a lot
Need the drivers for Win 7 @tndb
the mega link u posted needs a decryption key, please post the same
satsmagic said:
Need the drivers for Win 7 @tndb
the mega link u posted needs a decryption key, please post the same
Click to expand...
Click to collapse
Sorry about that, link is updated
tndb said:
Sorry about that, link is updated
Click to expand...
Click to collapse
thanks for posting the link. I am using the International version of Zuk Z1
However, even after installing the drivers you posted my device is not connecting properly to my Win 7 laptop, I tried on a XP machine too.
When i connect the device, by default, it connnects in charging mode and I get a popup saying device not recognised.
If i switch to MTP mode, nothing happens. I wait till the screen turns off, when i turn on the screen again, it again shows in charging mode. I have to disconnect and then reconnect, then it connects in MTP mode. This should not happen, I should be able to swap between the modes without disconnecting and reconnecting the device
If i select Mass storage mode, then it shows an addtional drive in My computer as removable disk, but does'nt show its capacity. If i click on it, it says please insert a disk. so Mass storage mode doesnt work. I have to select MTP again, disconnect and then reconnect to get in MTP mode.
Anyone else facing this issue, what can be a solution for this.
I am on 12.1-YOG4PAS7DF
Also, i found these C-apps on this link https://cyngn.com/c-apps
Should i flash these, would these update anything on my ROM version
please help me !!!!!
Let me know how i can turn off Zuk Z1 as my touch is not working, i tried to root is using Farmaroot and when i restarted it the touch stopped working. Hardware keys are working fine.
I am using zui version 1.2.070 in India, how to upgrade this ??,, I am a simple user, don't have much tech knowledge about this ,kindly guide me
First of all, i have read some similar threads about this, and all advise diffrent solution besides the hardware mod, I have tried for 2 days all methods in Miui forums and none have worked for me except the hardware method.
My Device: Xiaomi Redmi Note 3 Pro / SD version.
State:
-would only show "Mi" logo when powered on.
-Would enter only Fastboot.
- No EDL mode
- No recovery
-bootloader locked
-In this state, you can't flash absolutely nothing with any software. (from fastboot).
Requirements:
- windows 7/ windows 10 x64 edition.
- ONLY LATEST version of miflash, from 2016 onward, so it has the required drivers and methods to work with the phone. (I have tried with older versions and it did not work, i thought there was no hope for my phone).
- one hard bricked Redmi Note 3 Pro
- any fersion of Stable FASTBOOT OFFICIAL rom. (.tgz extension) - I personally used kenzo_global_images_V7.2.3.0.LHOMIDA_20160129.0000.14_5.1_global_c85ba6c524.tgz
- medium disassembly skills,
- a lot of patience,
- minimum set of tools (one small cross screwdriver, 1-2 strong finger nails, good eyesight).
- one microusb cable
HOW TO:
1. uninstall all drivers and software related to the Xiaomi phone. (I ended up reinstalling windows 7 just to be sure all was gone - that is how desperate I became). To be sure this is done correctly, with the phone turned off, connect it to the computer.
Go into device manager, search in com ports, or wherever any drivers are installed for the phone, and uninstall all of them, ticking remove driver files also.
after doing this, hit refresh, and see if any drivers get installed again.
Repeat until there are no drivers installed, and the device will be without a driver.
2. Disconnect the phone and RESTART WINDOWS
3. Disable driver signature verification/enforcement:
a. in windows 7, this is easy: restart windows, hit f8 until a menu pops up where you can choose disable driver signature verification/enforcement.
b. in windows 10, it is a little bit longer, but: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/ - Be careful, when choosing the option in the last menu, use F... keys, not number keys.
4. while in windows, in the bottom right corner, there should be a message saying "test mode"
5. install ONLY the LATEST VERSION of Miflash! you may get some messages about driver installation (2 times), allow installation!
6. RESTART WINDOWS
7. Prepare the phone!: I followed the video here, even I did not understand the language: http://choimobile.vn/threads/video-...o-snapdragon-650-fix-download-mode-edl.65098/
- First, I used my nail to open the phone up, just like in the video. It is great that the screen is not glued to the body, there are only some clips holding it in place!
- after opening the cover please be careful - there is a cable connecting the case to the mainboard - the fingerprint sensor.
- after this, unscrew the 7 or 8 screws as in the video.
- unlock the cables as in the video - please be sure not to disconnect all the cables.
- now, first get the antenna plastic cover outside of the way.
- after disconnecting the camera module, I would personally advise you to get the camera out of the way first, as there is a piece of foil glued between the mainboard and the underneath of the camera module (on the display)
- with great care, rise the Mainboard from the display.
- to have better access to the testpoint pins, I turned the Mainboard over the battery.
- now, connect the microusb cable to the phone.
8. connect the phone to the computer.
9. go into device manager and check if there are any devices installed, there should be under ports.... a device called Qualcomm HS-USB Diagnostics 900E.
10. Now comes the tricky part, switching the phone to EDL mode (emercency download)
look on the back of the motherboard of the phone to connect the 2 testpoint pins as in the video. You can use anything to do this. a metal wire, a small scissors, an untied paperclip... You will have to do this while device manager is opened, as you must check it when the driver changes to "qualcomm hs-usb qdloader 9008".
Please be careful when trying to connect the 2 pins not to touch any metal housing, ans this will restart the device each time.
Now, try and try and try until the driver changes to "qualcomm hs-usb qdloader 9008".
11. unzip the rom using 7 zip to a destination of your choosing. I advise as short destination as possible and no spaces used in the folder naming. I unpacked it in C:\rom\
12. Open Miflash
13. As per other many many instructions:
a. click browse - select the folder where you unpacked the rom (for me, c:\rom\)
b. click the arrow next to brows button and select advanced.
c. in the first field, navigate to the folder where the rom was unpacked and select flashall.bat
d. in the third field select prog_emmc_firehose_8976_ddr.mbn from the "images"folder in the folder whre he rom was extracted
e. field 7: rawprogram0.xml and field8: patch0.xml
f. Hit the Refresh button, the device should appear as a com port in the white field of Miflash.
g. just to be sure, tick also "flash all" in the bottom of miflash.
14. Hit the Flash button on Miflash and this should be the last step before powering up your revived Xiaomi Redmi Note 3.
This is what I learned in the past 2-3 days.
Different errors I got during the learning process and what i did to avoid them:
- different problems with drivers not installing correctly or showing different device names - just use the method i pointed out in the beginning to uninstall any driver previously installed on the computer, with the refresh in device manager and than uninstalling all.
- "end of package" error at second 2 while flashing in Miflash - you are using an older or an unsupported version of miflash, just use the latest one.
- not being able to flash anything while in fastboot - if you have a locked bootloader, on redmi note 3 snapdragon version, you simply won't be able to flash anything. end of story. this is the whole purpose of having a locked bootloader.
- trying to go into EDL mode using fastboot comand "fastboot oem eld" - this will not work for a really bricked device as was mine. the only solution is to go through the tespoint pin connection.
i wonder if there's a way not to make trwp locked in the recovery partition, so if someone flashes a factory rom without precaution, twrp will simply get overwritten by factory recovery. Wouldn't that prevent these hard bricks?
btw, nice guide
Please move the thread into guides/tutorial section.
Well, mine was bricked too 2 days ago... even I already unlock the bootloader using the official way.
It happened because I'm on AOSP and I flash Xiaomi.EU ROM from TWRP.
'MI' Logo flashed twice then the phone turns off itself.
It can't boot, can't enter EDL mode. I just can go into fastboot mode. But nothing can be done there because it always says 'device is locked'.
'fastboot oem device-info' also says the phone is on locked state.
Dunno why this happen, I think its because I play with the unlock bootloader toggle on previous MIUI and AOSP ROM.
After countless of times trying to get into EDL, I give up.
Device manager always show "QCom HS-USB Diagnostic 900E" instead of "QCom HS-USB QLoader 9008"
Finally I try the official Mi Unlock software, re-unlock success and BAM... Phone boots again into system. lol...
This makes me think the bricked problem can prevented/solved to by:
- At least bind a Xiaomi Account to your phone once when using official ROM (recommended China Dev ROM)
- Use that account to apply for the unlock, and when you got the phone bricked/relocked, you can re-unlock it using official way to revive the phone
Now is possible unbrick without disassembly:
http://en.miui.com/thread-267263-1-1.html
http://www.htcmania.com/showthread.php?t=1174700
jujusito said:
Now is possible unbrick without disassembly:
http://en.miui.com/thread-267263-1-1.html
http://www.htcmania.com/showthread.php?t=1174700
Click to expand...
Click to collapse
please read through all the thread, don't just throw in a link. the method mentioned by you will not work on some bricked devices, including mine. this did not work for me, so I ended up disassembling the phone.
aabenroi said:
Well, mine was bricked too 2 days ago... even I already unlock the bootloader using the official way.
It happened because I'm on AOSP and I flash Xiaomi.EU ROM from TWRP.
'MI' Logo flashed twice then the phone turns off itself.
It can't boot, can't enter EDL mode. I just can go into fastboot mode. But nothing can be done there because it always says 'device is locked'.
'fastboot oem device-info' also says the phone is on locked state.
Dunno why this happen, I think its because I play with the unlock bootloader toggle on previous MIUI and AOSP ROM.
After countless of times trying to get into EDL, I give up.
Device manager always show "QCom HS-USB Diagnostic 900E" instead of "QCom HS-USB QLoader 9008"
Finally I try the official Mi Unlock software, re-unlock success and BAM... Phone boots again into system. lol...
This makes me think the bricked problem can prevented/solved to by:
- At least bind a Xiaomi Account to your phone once when using official ROM (recommended China Dev ROM)
- Use that account to apply for the unlock, and when you got the phone bricked/relocked, you can re-unlock it using official way to revive the phone
Click to expand...
Click to collapse
I also applied for an unlock code, but this takes up to 15 days, and I have the phone for only 3 days . I could not wait for the code, I had to do something to revive it.
meangreenie said:
i wonder if there's a way not to make trwp locked in the recovery partition, so if someone flashes a factory rom without precaution, twrp will simply get overwritten by factory recovery. Wouldn't that prevent these hard bricks?
btw, nice guide
Click to expand...
Click to collapse
I made a modified TWRP which will not cause hard bricks
Rajdip said:
I made a modified TWRP which will not cause hard bricks
Click to expand...
Click to collapse
great work! your modded twrp will no doubt save me when i forget i have to delete the emmc file in the future.
Dear, thank you for your contribution, this deserves to be a section more important, really saved my phone from the hard brick. Again very grateful
how do i know what a test point looks like on any phone? like the new redmi 3s? i cant get into edl because im stuck in Qualcomm HS-USB Diagnostics 900E
xdarkmario said:
how do i know what a test point looks like on any phone? like the new redmi 3s? i cant get into edl because im stuck in Qualcomm HS-USB Diagnostics 900E
Click to expand...
Click to collapse
maybe look for something like this?
http://choimobile.vn/Temp/Testpoint_Redmi_Note3_PRO_3.jpg
I doubt they will have much variance from xiaomi phone to phone to make it easy for factory / repair centers to fix many models... (I could be wrong though), other brands are probably different.
Well you can enter edl mode from fastboot via this simple tool
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
And then you can flash any miui .tgz based rom and resurrect.
I hard bricked my Device last night and resurrected
PS : you must have the MiPcSuit installed
ilvmyname said:
Well you can enter edl mode from fastboot via this simple tool
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
And then you can flash any miui .tgz based rom and resurrect.
I hard bricked my Device last night and resurrected
PS : you must have the MiPcSuit installed
Click to expand...
Click to collapse
links dead
Quick addition: if you're using Virtual Box, like me (on a mac), you need to enable USB 2.0 on the virtual machine. On Virtual Box, this means you have to add an extension pack. This might save you 48hrs, like it cost me
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