Hey guys, Today Ubuntu was released for the nexus 7 for both 16GB and 8GB models, it obviously requires unlocked bootloader but it is working! heres a guide i pulled form Ubuntu Wiki.
Leave Any comments below on sucess or fails!!!
I Will Be Posting up updates when newer versions are released.
Press The Thank Button if it worked for you!!!
-------------------------REMEMEBR!!! I AM NOT RESPONSIBLE FOR ANY BRICKS OR DAMAGES TO YOUR DEVICE!!!!!!-------------------------------
What you will need:
Nexus 7 Tablet (8GB or 16GB)
Standard MicroUSB Cable (should come with the device)
Ubuntu Nexus 7 Desktop Installer installed on your development system
Ubuntu 12.04 LTS or Later
Optional
Micro USB Host Cable (OTG Cable) - used for attaching keyboard, mouse, etc. Directions on how to get and use one of these are towards the bottom of this page.
Ubuntu Nexus 7 Desktop Installer
A simple one-click installer has been provided, and is available in a PPA.
sudo add-apt-repository ppa:ubuntu-nexus7/ubuntu-nexus7-installer
sudo apt-get update
sudo apt-get install ubuntu-nexus7-installer
Usage instructions for the installer are provided below.
Unlocking the Nexus 7
The Nexus 7 ships with a locked bootloader. You must unlock it in order to flash different images to the device. Fortunately, this is a trivial process, and you only need to do it once.
Warning: Unlocking the bootloader erases all data and resets the device to factory defaults.
Reboot the Android device into the Android boot loader. To do this, hold the volume down button and press the power button. Continue holding the volume down and power buttons until you see the boot loader UI. The device now displays the boot loader GUI, which looks like this:
Verify fastboot lists the device:
$ sudo fastboot devices
1234567891234567 fastboot
Start the bootloader unlock process:
sudo fastboot oem unlock
You are prompted on screen to unlock the bootloader on the Android device screen. Follow the on-screen directions to continue. Your screen should now look like this:
Complete the process by rebooting:
sudo fastboot reboot-bootloader
Or simply press the power button.
Installing Ubuntu on Nexus 7
Once all setup has been completed, the installation can start. To install, ensure the Nexus 7 is in fastboot mode, plug it into your computer (and make sure NO OTHER DEVICES are plugged in).
Find the installer in the dash (search for 'nexus'):
This will provide a Graphical Interface for installing Ubuntu. This tool will download the latest image automatically, and flash it accordingly. The flashing step should take about 2 minutes. Once the flashing is complete, the device will reboot and finish the installation. This step can take 10-15 minutes.
Returning your Nexus 7 to Stock Android
Warning: Disconnect ALL other mobile devices connected from your computer or they might get erased too. This will erase ALL DATA on your Nexus 7.
In case anything happens while developing, the system image for Nexus 7 can be found here: https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
After downloading the above tarball, uncompress it with the following:
tar zxvf nakasi-jro03d-factory-e102ba72.tgz
Then, place your machine into fastboot mode and run the resulting script:
cd nakasi-jro03d/
sudo ./flash-all.sh
You may get the following warnings, which you can ignore, the restoration will continue anyway.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
Troubleshooting the Install
If you have problems installing the image, please use the following troubleshooting steps:
Detach the USB cable, restart the tablet back into fastboot mode, and re-attach the USB cable.
If problems persist, reboot your host PC.
If you still have issues, try a different USB cable.
If you have a 16G tablet, try using the 8G image.
If you still have issues after doing all this, return the image to stock using the directions above and re-try.
If none of that works, ask a question on Ask Ubuntu using the mobile tag, or ask for help in the #ubuntu-arm channel on freenode. If you believe it's a bug, file a bug against ubuntu-nexus7 in Launchpad.
For Future Use
For Future Use
For Future Use 2
For Future Use 2
For Future Use 3
For Future Use 3
For Future Use 4
For Future Use 4
I know this question will get asked sooner or later.
So I will ask
Is there a way to get it working on Windows?
at the moment, a windows method is not avaliable to my knowledge, but when installing it, it downloads the images and i think you might be able to take the images from the install and run it though windows fastboot like normal, but again i have not tried. also performance is not bad, can be laggy at times but its fine to use. Cheers.
This has already been posted and you can just use fastboot to flash the userdata and boot img
This is a great step forward for linux however, Will this effect my CWM Installation?
I want to know if I can make a full ROM backup the current stock I have modded etc then restore it via CWM to remove ubuntu.
yes, at the moment it wiped my whole device and all, so make sure back everything up externaly first before doing this.
I use an RPM distribution, so I will wait a bit. But it is really interesting!!!!
And just for dream: next step: grub!
We already have this thread here
http://forum.xda-developers.com/showthread.php?t=1957561
...and you just simply copy/pasted this from here anyway:
https://wiki.ubuntu.com/Nexus7/Installation
Closed
Hi
I have HTC one that couldn't be recognized by my pc
running under windows 7 by usb
I have : VId = 0000 and pid = 0000 in : le chemin d'acces à l'instance du périphérique :
USB\VID_0000&PID_0000\6&189D988F&0&4
knowing that I have installed the last version of HTC Sync manager,
usb debogging is enabled in my htc ,
sorry for my poor english
thank you for your help
hm911 said:
Hi
I have HTC one that couldn't be recognized by my pc
running under windows 7 by usb
I have : VId = 0000 and pid = 0000 in : le chemin d'acces à l'instance du périphérique :
USB\VID_0000&PID_0000\6&189D988F&0&4
knowing that I have installed the last version of HTC Sync manager,
usb debogging is enabled in my htc ,
sorry for my poor english
thank you for your help
Click to expand...
Click to collapse
Take a look at FAQ Q#2 on getting your phone recognized.
majmoz said:
Take a look at FAQ Q#2 on getting your phone recognized.
Click to expand...
Click to collapse
Hi @majmoz
steel not finding my problem in this FAQ
hm911 said:
Hi @majmoz
steel not finding my problem in this FAQ
Click to expand...
Click to collapse
Did you follow the steps in FAQ Question #2? Can you use a different port, cable or computer? Depending on what you want to accomplish, you could use Linux on a USB!
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
Click to expand...
Click to collapse
I think I've managed to successfully brick my phone through the following process...
1. boot into recovery
2. enable sideload mode
3. adb sideload the OxygenOS beta 9 image (downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_9/)
Everything went smoothly and the sideload process finished successfully. Rebooted the phone, wandered away for a bit...and now it's just a black screen that won't turn on. Plugging it into my laptop I see that is identifying itself as a QUSB__BULK device:
Code:
usb 1-1.4.4: new high-speed USB device number 18 using xhci_hcd
usb 1-1.4.4: New USB device found, idVendor=05c6, idProduct=9008
usb 1-1.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.4.4: Product: QUSB__BULK
usb 1-1.4.4: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 1-1.4.4:1.0: Qualcomm USB modem converter detected
usb 1-1.4.4: Qualcomm USB modem converter now attached to ttyUSB0
What are my options at this point? All of the recovery guides I've been able to find so far start by downloading some Windows utilities, and I don't have easy access to a Windows machine.
Use the Hard Brick guide, download the full tool unbrick guide and it should work fine, follow method 2. you can find hard unbrick guide on google.
Unfortunately, the hard unbrick guide (if you mean forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/) seems to be Windows-only (it has instructions for downloading lots of Windows device drivers, etc), and as I said in my original question, I don't have a Windows machine handy.
So I have not looked alot around but I haven't seen any guides or something for Linux, but 2 ideas:
1: try that guide, maybe Linux won't need the drivers and it would work just fine.
2: you can download a windows image, install it on a Virtual Machine,unbrick your phone and then delete the VM and everything.
Is your phone's bootloader unlocked? If yes, things will much more simple.
anyway, try download full 3.2.8 ROM from OP site, boot your phone to fastboot mode and sideload it.
Make sure to read this guide completely before starting.
You will lose all data on the tablet, make a backup of important data before you start.
What you need:
- a Linux installation. Don't use a VM! Use a live USB, if you don't have Linux installed, but don't use a virtual machine.
- a microusb cable to connect your tablet to the PC
- (if you go with hw option) some way to open the tablet (pry tool, opening picks, etc)
- (if you go with hw option) something conductive (metal tweezers, a paper clip, a piece of wire, etc)
- (if you go with sw option) mtk-su from https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
- amonet-mustang.zip from this post
- finalize.zip from this post
- update-kindle-NS6312_user_1827_0002517050244.bin: https://fireos-tablet-src.s3.amazon...ate-kindle-NS6312_user_1827_0002517050244.bin
- Magisk-v19.3.zip: https://github.com/topjohnwu/Magisk/releases/download/v19.3/Magisk-v19.3.zip
Install python3, PySerial, adb and fastboot. For Debian/Ubuntu something like this should work "sudo apt install python3 python3-serial android-tools-adb android-tools-fastboot".
0. Disconnect the tablet and all other Android devices from the PC.
1. Back up whatever important data you have on the device and perform a complete factory reset of the tablet. When going through the initial setup, don't connect to a network (see below on how to do that).
2. Disable or uninstall ModemManager from your Linux installation
3. At this point you need to get your tablet into the bootrom download mode. There are two ways it can be achieved.
a) If your tablet works, you can use the software method (which doesn't require opening the tablet) or the hardware method. Note that if something goes horribly wrong, you might still be required to open up the tablet.
b) If your tablet doesn't boot (bricked), you can only use the hardware method
----------------------------------------------------------------------------------------------------
Software method:
This will get you into bootrom mode by obtaining temporary root and temporarily bricking the device.
1. Download mtk-su from https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
2. Enable developer mode and USB debugging on the tablet
3. Unzip the mtk-su archive
4. Transfer the executable to your tablet: "adb push arm/mtk-su /data/local/tmp"
5. Run "adb shell"
6. Keep the screen on and run the following commands in the shell on the device:
Code:
cd /data/local/tmp
./mtk-su
getenforce # Just to confirm it says Permissive
echo 0 > /sys/block/mmcblk0boot0/force_ro
dd if=/dev/zero of=/dev/block/mmcblk0boot0 bs=512 count=8
This is the sort of output you should see for that step:
Code:
[email protected]:~/Downloads/mtk-su $ adb shell
mustang:/ $ cd /data/local/tmp
mustang:/data/local/tmp $ ./mtk-su
New UID/GID: 0/0
mustang:/data/local/tmp # getenforce
Permissive
mustang:/data/local/tmp # echo 0 > /sys/block/mmcblk0boot0/force_ro
mustang:/data/local/tmp # dd if=/dev/zero of=/dev/block/mmcblk0boot0 bs=512 count=8
8+0 records in
8+0 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
mustang:/data/local/tmp #
Don't close the console just yet.
Hardware method:
This will get you into bootrom mode by opening up the tablet and shorting a point to the ground.
1. Shut your device down and disconnect it from USB
2. Use a pry tool to remove the back shell from the tablet. Start at the bottom and work your way up. There are no cables between the back shell and the motherboard.
3. You will need to get something conductive and temporarily connect a point to the ground. A point suggested by @ggow is: https://forum.xda-developers.com/showpost.php?p=79683131&postcount=22. You will need to pop up the metallic shield to access it. Alternatively, there are multiple points on the back of the PCB which also work (marked as CLK/CMD/DAT0).
----------------------------------------------------------------------------------------------------
4. At this point if you went with software method, you should have a root shell open, and if you went with the hardware method you should have a capacitor or a testpoint grounded to the shield.
5. Now, open another terminal on your PC, extract amonet-mustang.zip, navigate to it, and run `sudo ./bootrom-step.sh`. It should print "Waiting for the bootrom".
6.
a) For the software method, you should already have the USB cable plugged in. Type "reboot" in the first terminal (the one you that's running "adb shell"). [If you're trying this for the second time because it didn't work for the first time, you won't have an "adb shell" terminal. In that case, just plugging the USB cable in should be enough.]
b) For the hardware method, ensure the short is applied and then plug in the USB cable.
7. You should see the following device appear in your "dmesg" log:
Code:
[1141765.113884] usb 3-1.4.3.1: USB disconnect, device number 59
[1141783.057101] usb 3-1.4.3.1: new full-speed USB device number 60 using xhci_hcd
[1141783.226498] usb 3-1.4.3.1: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[1141783.226502] usb 3-1.4.3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[1141783.506877] cdc_acm 3-1.4.3.1:1.0: ttyACM0: USB ACM device
This *must* be the device you see. If you see a "preloader" device instead, your short probably didn't work (for the hw method), or your system inexinexplicably didn't brick (for the sw method). Unplug everything and try again. If the tablet doesn't shut down, you might need to open it up and disconnect the battery.
8. The script should now tell you to remove the short. If you went with hardware method, you do need to remove it first. Otherwise, just press Enter.
9. The script will now proceed to downgrade your device and flash some essential files. Just let it be, it will take about 4 minutes. You should see the following output:
Code:
[2019-06-30 02:48:59.334098] Waiting for bootrom
[2019-06-30 02:50:41.179571] Found port = /dev/ttyACM0
[2019-06-30 02:50:41.180204] Handshake
* * * If you have a short attached, remove it now * * *
* * * Press Enter to continue * * *
[2019-06-30 02:50:49.195782] Init crypto engine
[2019-06-30 02:50:49.214278] Disable caches
[2019-06-30 02:50:49.214801] Disable bootrom range checks
[2019-06-30 02:50:49.229877] Load payload from ../brom-payload/build/payload.bin = 0x46B8 bytes
[2019-06-30 02:50:49.233418] Send payload
[2019-06-30 02:50:49.958957] Let's rock
[2019-06-30 02:50:49.959812] Wait for the payload to come online...
[2019-06-30 02:50:50.904341] all good
[2019-06-30 02:50:50.904714] Check GPT
[2019-06-30 02:50:51.240034] gpt_parsed = {'proinfo': (1024, 6144), 'PMT': (7168, 9216), 'kb': (16384, 2048), 'dkb': (18432, 2048), 'lk': (20480, 2048), 'tee1': (22528, 10240), 'tee2': (32768, 10240), 'metadata': (43008, 80896), 'MISC': (123904, 1024), 'reserved': (124928, 16384), 'boot': (141312, 32768), 'recovery': (174080, 40960), 'system': (215040, 6354944), 'vendor': (6569984, 460800), 'cache': (7030784, 1024000), 'userdata': (8054784, 22722527)}
[2019-06-30 02:50:51.240157] Check boot0
[2019-06-30 02:50:51.485287] Check rpmb
[2019-06-30 02:50:51.695083] Downgrade rpmb
[2019-06-30 02:50:51.696759] Recheck rpmb
[2019-06-30 02:50:52.591407] rpmb downgrade ok
[2019-06-30 02:50:52.837668] Clear preloader 1
[1 / 1]
[2019-06-30 02:50:52.859908] Clear preloader 2
[1 / 1]
[2019-06-30 02:50:52.882059] Flash lk-payload
[4 / 4]
[2019-06-30 02:50:53.214382] Flash tz
[5547 / 5547]
[2019-06-30 02:52:51.150851] Flash lk
[651 / 651]
[2019-06-30 02:53:05.192112] Inject microloader
[4 / 4]
[2019-06-30 02:53:05.524154] Flash preloader
[271 / 271]
[2019-06-30 02:53:11.525329] Restore preloader
[8 / 8]
[2019-06-30 02:53:11.695348] Reboot to unlocked fastboot
If the script freezes at some point, you will have to restart it. Terminate the script, then immediately run `sudo ./bootrom-step.sh` again. The exploit it set up so that after about 40 seconds of inactivity it would reboot your device and drop you back into the bootrom mode, which the script is waiting for. If you cannot restart the process, you might have to open up the tablet and replug the battery to completely power off the device.
10. You should see a success message: "Reboot to unlocked fastboot". Only proceed if you see the message.
11. Once the device boots to fastboot (check with "fastboot devices"; you should also see amazon logo on the screen.), you can run "sudo ./fastboot-step.sh".
12. At this point the device should boot into recovery, however the screen will be off. Just press the power button twice and the screen should turn on.
13. Success! You now have a custom recovery installed that can be accessed by holding down power and volume down (the leftmost) buttons. At this point if you came here from a custom ROM thread you should probably follow the ROM installation instructions. Alternatively, the next steps will detail installing a stock firmware and rooting it with Magisk.
----------------------------------------------------------------------------------------------------
14. We'll now upload required files to the recovery. On your PC, do:
adb push update-kindle-NS6312_user_1827_0002517050244.bin /sdcard/fw.zip
adb push Magisk-v19.3.zip /sdcard
adb push finalize.zip /sdcard
15. In the recovery, go to "Install", navigate to "/sdcard" and flash fw.zip
16. Go to "Wipe" and do the default wipe, then reboot
17. At the Fire setup screen, select your language. On the next screen, Wifi setup, select any password-protected network, then instead of entering the password press "cancel". Now, back at the wifi setup screen, press "Skip setup" and "Skip" in the dialog pop-up again
18. Wait for the update to finish (wait until the updating fire notification disappears)
19. Hold down the power button, press Restart and hold volume down to boot into recovery.
20. In the recovery, go to "Install", navigate to "/sdcard" and flash Magisk-v19.3.zip
21. Press back, select finalize.zip and flash it
22. Once finalize.zip is flashed, press "Reboot System"
VERY IMPORTANT STUFF:
Only ever flash boot images from TWRP. Since nothing but TWRP is aware of the exploit, if you try to flash a boot image from Android, it won't have the exploit integrated into it! This includes Magisk as well, so do NOT install or uninstall it from Magisk Manager (However, installing modules should be fine; although it depends on the specific module).
Due to how the exploit works, it takes over the first 0x400 bytes of boot.img/recovery.img. When flashing zips from the recovery, it will transparently remove and then reinstall the exploit when needed. So long as you flash zips from the recovery, you should treat the boot image normally. However, this means that you cannot use any other apps (e.g. FlashFire) to flash the boot or recovery partitions.
To uninstall the hack and revert back to stock:
- Download an update package to your PC (the update-kindle-NS6312_user_1827_0002517050244.bin file)
- Flash revert-stock-mustang.zip from TWRP
- Perform the default wipe
- Reboot to recovery; you should see amazon recovery now
- Select "apply update from ADB" in the recovery menu
- Run "adb sideload update-kindle-NS6312_user_1827_0002517050244.bin" on your PC
Other misc information / troubleshooting:
- If you need to disconnect the battery, use a pair of tweezers to grab the wires and gently pull towards yourself. You can do bootrom-step.sh either with or without the battery connected, however fastboot-step.sh should be done with the battery connected.
- If your device is bricked (e.g. from a downgrade), just follow the steps as-is.
- If you're getting an error like "Serial protocol mismatch", or any other error in bootrom-step, try disabling or temporarily uninstalling ModemManager from your Linux
- To remount /system as rw use "mount -o rw,remount /system". ("mount -o remount,rw /system" will not work)
Thanks to: aftv2-tools contributors https://gitlab.com/zeroepoch/aftv2-tools: for an implementation of mtk download protocol, @diplomatic for mtk-su, @Michajin for testing the instructions.
Thanks for your work!
On a side note, I also had adaptive storage on during the process. I was having crashing issues after install. I re-installed the firmware-wiped and booted. I followed the steps to boot without setup. Then booted back into TWRP, flashed magisk, but did not flash finalize. I like access to some of the amazon apps. Once I rebooted (I stayed off wi-fi) I sideloaded a package disabler and disabled the OTA. I registered then disabled the amazon bloat I didn't want. I have installed my sd card as portable this time, just to be safe.
also, TWRP does not have backup and restore options, is this normal on this currently?
incredible, i will try that
Thanks. We will look if it's possible to compile LOS 14.1 since it has the same processor as the HD8 2018.
hello @xyz
Do you think i can try that throught a linux virtual machine on virtualbox ?
guizzzmo said:
hello @xyz
Do you think i can try that throught a linux virtual machine on virtualbox ?
Click to expand...
Click to collapse
I unlocked my 7th gen with virtualbox so yes.
Hi guys, Is there a chance there will be a Nexus ROM released for the Mustang version of the Fire? It's been my preferred ROM on my older Ford model so I'd like to keep using it if possible.
tangledweb said:
Hi guys, Is there a chance there will be a Nexus ROM released for the Mustang version of the Fire? It's been my preferred ROM on my older Ford model so I'd like to keep using it if possible.
Click to expand...
Click to collapse
Mustang uses a different kernel than Ford/Austin; custom ROMs will need to be spun up from different sources. Developer time is scarce; may or may not happen.
Finally bricked with software method.
I try to find a picture for where i can make my wire for hardware method.
SOLVED:
My battery was empty so i have just disconnect battery and plug usb with paperclip and i have got bootrom.
Great !!
much thanks for this, after some fiddling it works perfectly!!
i had some issues getting past the bootrom script part on both my galliumos & debian machines (serial error message, despite apt remove modemmanager) - until i tried an xubuntu liveusb, at which point everything went smoothly and as directed via the software method.
looking very forward to an aosp rom to replace stock and being able to make a twrp backup (i broke my install with magisk, but it was a simple recovery just reflashing fw.bin again). cheers!
Is it just me or is the hardware point picture coming up as a dead link? Can someone attach the correct point in another image?
rumblpak said:
Is it just me or is the hardware point picture coming up as a dead link? Can someone attach the correct point in another image?
Click to expand...
Click to collapse
The link (to the hardware shorting point) in the OP is indeed broken.
Try the following :
https://forum.xda-developers.com/showpost.php?p=79683131&postcount=22
Edit : The link in the OP is fixed now. (7/3/2019)
at the point where you issue 'reboot' for the software method. upon issuing that command, the device powers off, and is non responsive. cant get it to turn back on at all. Very strange. Any ideas?
wlewin said:
at the point where you issue 'reboot' for the software method. upon issuing that command, the device powers off, and is non responsive. cant get it to turn back on at all. Very strange. Any ideas?
Click to expand...
Click to collapse
Did the script run correctly? Did you get to the point where is says
* * * If you have a short attached, remove it now * * *
* * * Press Enter to continue * * *
Did you press enter and see the script run? Did it end;
[8 / 8]
[2019-06-30 02:53:11.695348] Reboot to unlocked fastboot
The reboot command puts your device into bootrom to inject the exploit. Upon completion TWRP is installed, i think you have to double click the power button. If all else fails, you might have to pry open and disconnect the battery. Were you in bootrom, because preloader can do this; run lsusb and you should see a phone connection or "dmesg" and you should see this device ;
[1141765.113884] usb 3-1.4.3.1: USB disconnect, device number 59
[1141783.057101] usb 3-1.4.3.1: new full-speed USB device number 60 using xhci_hcd
[1141783.226498] usb 3-1.4.3.1: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[1141783.226502] usb 3-1.4.3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[1141783.506877] cdc_acm 3-1.4.3.1:1.0: ttyACM0: USB ACM device
Michajin said:
Did the script run correctly? Did you get to the point where is says
* * * If you have a short attached, remove it now * * *
* * * Press Enter to continue * * *
Did you press enter and see the script run? Did it end;
[8 / 8]
[2019-06-30 02:53:11.695348] Reboot to unlocked fastboot
The reboot command puts your device into bootrom to inject the exploit. Upon completion TWRP is installed, i think you have to double click the power button. If all else fails, you might have to pry open and disconnect the battery. Were you in bootrom, because preloader can do this; run lsusb and you should see a phone connection or "dmesg" and you should see this device ;
[1141765.113884] usb 3-1.4.3.1: USB disconnect, device number 59
[1141783.057101] usb 3-1.4.3.1: new full-speed USB device number 60 using xhci_hcd
[1141783.226498] usb 3-1.4.3.1: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[1141783.226502] usb 3-1.4.3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[1141783.506877] cdc_acm 3-1.4.3.1:1.0: ttyACM0: USB ACM device
Click to expand...
Click to collapse
None of that seems clear in the steps.
the amonet script is in 'waiting for bootrom'. I then issued the reboot command, and the device blacked out, and nothing happened in terminal.
I have since disconnected the battery, and it still doesn't boot at all.
wlewin said:
None of that seems clear in the steps.
the amonet script is in 'waiting for bootrom'. I then issued the reboot command, and the device blacked out, and nothing happened in terminal.
I have since disconnected the battery, and it still doesn't boot at all.
Click to expand...
Click to collapse
My guess is you are bricked stuck in the preloader or something is wrong with your linux, and might have to do the shorting method now. Run lsusb and see if it sees your device, i believe it shows up as a phone. If you see preloader, you will have to short it. otherwise you might have to fix your linux. Make sure modemmanager is uninstalled ... I had issues trying to use ubuntu and ended up using Rasparian.
Michajin said:
My guess is you are bricked stuck in the preloader or something is wrong with your linux, and might have to do the shorting method now. Run lsusb and see if it sees your device, i believe it shows up as a phone. If you see preloader, you will have to short it. otherwise you might have to fix your linux. Make sure modemmanager is uninstalled ... I had issues trying to use ubuntu and ended up using Rasparian.
Click to expand...
Click to collapse
ah ha! Got it sorted. So, the screen going blank was very odd. turns out after sending reboot, that state is two things
1. blank screen with not indication of being powered on
2. persistent through cutting the power (disconnecting battery)
So, seemingly, the devices is totally non-functional. The issue was, in the linux VM I am using, I had to go manually select the USB devices because the identifier changed from the prior Amazon device to a mediatek device. So it was in the right state, I linux just didn't auto connect to the new USB device.
All good the in the hood. continued and worked just fine. Just PSA to others, that boot state seems like the device is just off!
2017 7" tablet too?
Will this work on my Kindle fire 7" 2017 Ed if I update to the latest software version?
Or do I have to buy a new tab to root and install custom roms on?
OP, i think you are linking to the magisk uninstaller in your original post btw. not the installer zip
PowerUser64 said:
Will this work on my Kindle fire 7" 2017 Ed if I update to the latest software version?
Or do I have to buy a new tab to root and install custom roms on?
Click to expand...
Click to collapse
WTF no. 7th gen can be unlocked and rooted. (Also there are ROMS for it: LOS 12.1, AOSP FIRE NEXUS, etc).
https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
So, i've been tinkering a bit for days over my Wiko UFeel Prime (i had even heard this one is the "clone" of the YU Yureka Black and/or viceversa around) and found a ton of problems at first due to the manufacturer (Tinno) putting a ton of "walls" to make modding impossible, like:
Removing various Fastboot commands (oem unlock, oem unlock-tinno, reboot edl, general bootloader info, refuses reboots to recovery, bootloader and system, etc.);
Making updates/downgrades impossible, just in case last time you've touched the device and upgraded to the latest firmware from Wiko (fun fact: the update app pings a site called https://frogs.wiko-ota.com, but sadly it has never been archived before and nowadays shows chinese text saying how the content doesn't exist) and you're completely stuck with the shady apps and trackers Tinno put on their P7 board;
You couldn't use stuff like adb push or upgrade from recovery because they force you to use their proprietary tool on Windows to do such (they bundle all of their firmware updates into an huge .exe file, despite being inside a .zip file);
And more...
Despite everything, i found one crack into the phone to take advantage of: you can reboot on EDL mode via adb
And that's where my guide begins!
Requirements:In order to convert your Wiko to a Yureka Black, you must need...
Your Wiko UFeel Prime (whatever firmware, either it is M or N);
Another Android phone (must have: Magisk root, OTG Cable support);
An OTG adapter;
A charging cable (must be able to transfer data);
Preparing your rooted Android device:Moving on, your device must have the following apps installed
ADB & Fastboot Tools;
Fox's Magisk Module Manager;
Terminal Emulator;
After got the latter, do the following steps afterwards
Open the Fox MMM app;
Tap the search button (placed on the bottom right corner of the screen);
Type "QDL" or "Qualcomm" into the bar;
You should find a tool called QDL For Android NDK;
Tap on "Install";
Tap on "Install Module";
Wait for the module to install;
Reboot your device;
After reboot, open the ADB & Fastboot tools app;
Allow root perms;
As a last step (for now), you must hop over the YU Yureka Black QFIL files page and download the zip file under the Stock M File hyperlink- after doing that, extract the .zip file wherever you want (with your fav file explorer of choice) (for simplicity's sake: extract the zip out of the Download folder. After extraction, rename the "YU5040" etc. etc. folder as simply "yu"- the purpose of it will come in handy further on the guide).
As of now, leave your secondary phone as is and move to the Wiko phone.
Preparing your Wiko UFeel Prime:If you had setup your secondary phone successfully: preparing your Wiko phone will be 10 times easier than the latter.
Just follow thru the following steps:
Go to Settings;
Tap on the "About" section of your device;
Tap a ton of times on the Build number, until the following will tell you you had unlocked Developer Settings;
Go back;
Tap on Developer Settings;
Scroll until you find USB Debug and enable it;
As a last thing, if you prefer, jump straight to the home menu (on your Wiko), then lay the phone together with the other device on a safe spot where nobody could interfere on the work.
The next title will introduce you to the "delicate" part of the guide: but also the moment where your Wiko will finally get converted as a YU Yureka Black and allow modding!
Converting your Wiko:Now, follow carefully the steps i'm about to give
On your secondary device
Open the ADB & Fastboot tools app;
Connect on the device's slot the OTG cable;
On your Wiko
Connect the charging cable to it's slot;
Connect the cable's end (the USB part) to the OTG slot attached to the other device;
Tap on "Allow" if it asks you about USB debug (or generally allowing a pc to get access to the device);
On your secondary device
Tap on the "Refresh" button (placed on the top right part of the app's UI);
Scroll on the bottom of the screen;
Type reboot edl on the writing camp;
Tap "Execute" (which is next to the zone where you wrote the command);
If you came this far and your Wiko effectively turned off plus the notification LED started blinking RED: this means your Wiko successfully booted into EDL mode!
Now, let's move on the focus to your secondary device.
On your secondary device
Quit the ADB & Fastboot tools app;
Open the Terminal Emulator app;
Write the following commands:
Code:
cd /sdcard
cd yu
su
After typed these commands on the terminal, copy and paste this string of code on your terminal:
Code:
qdl --debug --storage emmc --include /sdcard/yu /sdcard/yu/prog_emmc_firehose_8937_ddr.mbn /sdcard/yu/rawprogram_unsparse_upgrade.xml /sdcard/yu/rawprogram_unsparse.xml /sdcard/yu/patch0.xml
Once done, tap send on your keyboard and let the program do it's magic.
The wait should vary depending on your secondary device's specs (approximates 1h at max) and the speed on writing the .mbn, .img, and .tz files inside the folder over the Wiko's board- also, pro-tip, be sure to check often on your secondary device (by tapping it's screen often).
The reason?
it will avoid the device to go into sleep mode (especially if you set the backlight to a short period of time) and once unlocked it restarts the whole flashing all over again, extending the flashing wait the double.
If an accident happens (like it happened in my case) you must resort on disassembling your device's back and short the pins with some tweezers to enter back EDL mode manually, and also repeating the flashing process by pasting again the code string on the terminal.
If you don't know how to disassemble your Wiko: check here.
Also, if you don't know which pins you should press to enter EDL mode: check here aswell.
After the long wait, you should see the following behaviors:
Your secondary device will flag a disconnection on the QDL program (via terminal);
Your Wiko phone will vibrate and start booting up, showing the YUREKA BLACK text as the splash screen;
Now you can finally unlock your bootloader (note: you must type unlock-go to do the latter) and flash your device however you like!Thanks for following my guide!---------------------
Credits:
- The Yu Yureka Black modding community;
- Sosavo;
- You, for following my guide!