I posted this on the 20A thread, but I think it might need its own thread to get more exposure.
My 1st Android (Sony Xperia X10) also had a locked bootloader. The devs found a way to bypass it in order to load custom kernels:
Xperia X10 bootloader bypass
Not sure if anyone looked at this before, but would something like this be possible on our phone?
If it's nothing... well, it was worth the try!
We also discussed 2ndinit from defy development. The trouble is our devs would rather use unlocked bootloader, and our main devs are already unlocked
Sent from my rooted P880
@non4 said:
We also discussed 2ndinit from defy development. The trouble is our devs would rather use unlocked bootloader, and our main devs are already unlocked
Click to expand...
Click to collapse
So nobody actually tried to see if it works or not?
well, regarding kholk couldn't do it, i guess it won't work
i think the v20 unlock is not a real unlock.
when the phone power-up, system boot from tegra3 inner ROM, it decode EBT partition into RAM and execute it, here it is the bootloader. according to boot parameter bootloader will load LNX(normal start android) or SOS(recovery). the two partition store in android boot rom format, with a rom header, linux kernel, root fs(adbd, init and scripts ...), extend data(digital certificate of the rom). bootloader will check the digital certificate with a public key in EKS partition. if we modify some data in LNX or SOS on a locked phone without re-sign, it will hang-up here.
so the unlock of v20 is only remove the digital certificate check, let us flush the 3rd-party roms (LNX and SOS)
for we can not access tegra iROM, we can not modify the encryptde bootloader too. our phone can flash android os only
other linux base os must be build into android boot rom format and flush into LUX or SOS partition also.
FASTBOOT mode is an android way to flush the device through usb, on v20, the command "adb reboot fastboot" will reboot the phone into fastboot mode, (caution: the 1st time use this command will unlock your phone and manufacturer reset without any warning !!!) but use command "fastboot getvar all" will show us :
(bootloader) product: X3
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) partition-size:bootloader:
an other way goto fastboot mode is command "adb reboot oem-unlock", phone screen show some tip how to flush and reboot, but after some test, i found the "fastboot boot <bootimg>" will not work (can upload but not boot, don't known why), this command can only help programmer test there roms without flush the device.
APX mode is nvidia flush mode, pull out battery, press vol+ vol- power buttom and connect usb cable to pc, pc will find a new nvidia device, and waitting for nvflash commands. but our p880 will response 0x4 error only either lock or unlock. it because LG set the cpu into ODM mode by flush the FUSE (on-chip One Time Program unit), nobody can change.
BYPASS is a software resolution to fast reboot into another linux kernel after the offical linux system startup. it need the "kexec" kernel api. by the kernel source of out phone, kernel\arch\arm\configs\x3_defconfig defines "# CONFIG_KEXEC is not set" , so the v10? kernel does not support kexec, we need impletment it ourself. for all kernel module need correct kernel source tree and configs. other device's 2nd-boot will not work on p880. and v20 kernel source not released currently, nothing we can do ....
So if we have the source a skilled dev could bypass the security ?
Sent from my LG-P880 using xda app-developers app
Related
Any news on how to enable fastboot on this device?
EDIT: Here you can find instructions for enabling fastboot on your device. The key combo to enter fastboot mode is Home + Power. Thanks to marioemp2k7 and mik_os.
Hi, I too am interested in having fastboot on LGP500. Did anybody find a way?
Yes please, is anybody working on that? Having fastboot disabled is such a pain in the ass...
Please enable fastboot on this phone
+5 for fastboot
Its blocked at bootloader level. You guys need to fish for a pre-release rom that can be flashed via lg mobile-updater or equivalent and try that bootloader (danger warning). That is IF one exists. Lg goofed on the ally and left fastboot enabled in their 1st version of firmware for it and fixed it in later shipped releases. We had to downgrade to v06 firmware to get fastboot. The command if enabled in bootloader is adb reboot bootloader to get to it. If its disabled it will just reboot as normal.
Here are instructions (for ally DO NOT FLASH THIS FIRMWARE -reference only)and link to tool to LG tool to downgrade frimware. http://androidforums.com/ally-all-things-root/166588-how-flash-stock-lg-rom.html
drellisdee said:
Its blocked at bootloader level. You guys need to fish for a pre-release rom that can be flashed via lg mobile-updater or equivalent and try that bootloader (danger warning). That is IF one exists. Lg goofed on the ally and left fastboot enabled in their 1st version of firmware for it and fixed it in later shipped releases. We had to downgrade to v06 firmware to get fastboot. The command if enabled in bootloader is adb reboot bootloader to get to it. If its disabled it will just reboot as normal.
Here are instructions (for ally DO NOT FLASH THIS FIRMWARE -reference only)and link to tool to LG tool to downgrade frimware. http://androidforums.com/ally-all-things-root/166588-how-flash-stock-lg-rom.html
Click to expand...
Click to collapse
one question why do we need fast boot ?
natedogg20050 said:
one question why do we need fast boot ?
Click to expand...
Click to collapse
http://android-dls.com/wiki/index.php?title=Fastboot said:
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images. It is disabled in the production G1 devices since USB support is disabled in the bootloader[1]. This can be changed if you get root on the device.
Click to expand...
Click to collapse
So, seems that it is for flashing of firmware. I thing that fastboot is something like recovery with some more?
drellisdee said:
Its blocked at bootloader level. You guys need to fish for a pre-release rom that can be flashed via lg mobile-updater or equivalent and try that bootloader (danger warning). That is IF one exists. Lg goofed on the ally and left fastboot enabled in their 1st version of firmware for it and fixed it in later shipped releases. We had to downgrade to v06 firmware to get fastboot. The command if enabled in bootloader is adb reboot bootloader to get to it. If its disabled it will just reboot as normal.
Click to expand...
Click to collapse
On the Ally one could re-enable fastboot by flashing an old firmware. But afaik the GT540 had the support for fastboot enabled thanks to some russian guys who rebuilt the bootloader without having access to a pre-release rom. I wish they could to the same for the P500. I would ask them myself on 4pda.ru, but unfortunately I can't speak russian.
The_ERROR said:
So, seems that it is for flashing of firmware. I thing that fastboot is something like recovery with some more?
Click to expand...
Click to collapse
It's way better than recovery. Believe me, Google would not have created it if it weren't that useful. Try booting a custom kernel on-the-fly with your recovery.
+6 for fastboot
iancor said:
It's way better than recovery. Believe me, Google would not have created it if it weren't that useful. Try booting a custom kernel on-the-fly with your recovery.
Click to expand...
Click to collapse
Great, and what we are waiting for?
+7 for fastboot
+8 for fastboot, it's definitely on my wishlist
"My boots are so fast, you won't know if I kicked you on the groin already.." -- Chuck Norris
+9 fastboot LOL.
I see there has been no progress so far...
+10 for fastboot, we must have it enabled
I have Fastboot! Mostly...
I have something on the Fastboot front. This being my first time hacking around with android stuff and not WinMo (screw winmo... bleh), I maybe need some help for the next step.
First off let me say that the winding way I got here includes stuff highly derivative off work from http://forum.androidcentral.com/lg-optimus-s-roms-hacks/45401-rom-thunderom-v1-5-12-14-2010-a.html this ROM for the optimus S. I want to ask their permission before I post steps on how I got here.
Here is where I am at.
On my phone:
Fastboot mode started
udc_start()
-- suspend --
-- reset --
-- portchange --
-- reset --
-- portchange --
fastboot: processing commands
YAY
Then windows installs for me a FastBoot Interface (Google USB ID) [Yes.. I was in Windows at the time lol]
DOUBLE YAY
This seems to work...
I can fastboot reboot, fastboot reboot-recovery, and I can wipe and assuming flash stuff (not trying just yet) with fastboot.
Only issues seems to be when I 'fastboot devices' I receive:
? fastboot
AND
I have to reflash or Nandroid restore to a more stable ROM to NOT go into fastboot mode.
From the sources I am reading, it should be more specific with my device ID correct?
Thanks for any ideas/help or whatever...
Thanks for your trying! ;-) I look forward for fastboot!
Unfortunately I can't help you with this problem.
Nobody here can speak russian? Asking on 4pda.ru how exactly they managed to enable fastboot on the GT540 might be helpful...
Some (possibily useful) info here
Thanks for the link, grabbing some .kdz from there. It might take a bit though... their filehosts are slow >.<
Note: This is a preview build only, features may change or be incomplete at this time
SGP311 & SGP312 only
Installation instructions in the second post, download links in the third
What is LittleKernel?
LittleKernel is an opensource bootloader for qualcomm devices available from codeaurora.
Why LK?
TL;DR Version
LK allows running separate boot and recovery that are fully independant of eachother.
Sony use a special method of booting into recovery for their updates, this is not available when you are unlocked, and there is no button combination to enter this mode. As a result the common method to get recovery on Xperia devices has been to use an initrd that has a script to load either normal boot or recovery boot based on a button press. This is a far from ideal solution as when you update your kernel it also updates your recovery. If something goes wrong you are stuck needing a computer to reflash the kernel partition.
With the recent addition of TWRP support for the latest devices there have been advances made in this technique making recovery updatable it still requires the flashed boot image to support that method. This is less than ideal still as it reduces choice in what you want on your device, giving the decision to the dev of the rom you have flashed. This also leaves you in the position of needing your computer if a kernel update fails for any reason.
LK solves these problems by separating out boot and recovery to their own kernels with their own ramdisks like every other device, if you flash the boot kernel, recovery isn't touched and will be there for you as a failsafe in case anything goes wrong. This removes the need to have a computer near by in case of breakage occuring.
What progress has been made?
I have been working on LK for the Xperia Z phone and since the release for the Xperia T have managed to make things a little more portable between devices.
Once the hardware arrives I need to compare the expected configuration against what is expected and add these definitions into my Xperia modifications to the aboot module.
Are there any changes that devs should look at?
Yes, they are minor but I suggest that devs look at the implementation by Dees_Troy for flip flopping boot and fota kernel. Soon I will also publish a patch to kernel restart procedure so that reboot messages can be passed to LK from kernel without S1Boot intercepting and clearing them.
Reboot patch will be very similar to http://review.cyanogenmod.org/#/c/44366/
XDA:DevDB Information
LK (LittleKernel) for Tablet Z, a Tool/Utility for the Sony Xperia Tablet Z
Contributors
lilstevie
Version Information
Status: Alpha
Current Beta Version: 1.0a
Beta Release Date: 2013-07-02
Created 2013-07-30
Last Updated 2013-08-26
Installation:
Follow these instructions for installing the preview of lk.
Boot device in fastboot mode
Flash pollux_windy-lk.img
Type "fastboot reboot"
Press Vol-Down between 1 and 5 seconds after rebooting
Flash boot.img with "fastboot flash boot boot-pollux_windy.img"
Flash recovery with "fastboot flash recovery pollux_wifionly.img"
Reboot device
Notes:
S1Boot (default bootloader) has different Device ID's to LK, this is to make it easier to identify when you are in lk fastboot, and because google's drivers are more available. The device will show up like the following if you are in lk fastboot:
Code:
Bus 001 Device 049: ID 18d1:d00d Google Inc.
This is only a preview, if your serial number does not show up in settings please notify me so that this can be investigated.
This is for Pollux_Windy only, that is the WiFi version of the Tablet Z, Model numbers are SGP311 and SGP312.
Because this is chainloaded from S1Boot pressing vol-up/down within the first second from pressing the power button may end up in flashmode or sony's fastboot. There is a 5 second timeout for pressing buttons in LK, you will not miss it if you wait a second.
Volume-up will boot the kernel you have flashed to recovery.
Volume-down boots into fastboot.
Downloads:
LK for pollux_windy: here
Stock boot image: here
TWRP by Dees_Troy: here
Note: The boot.img is entirely stock, only repacked for use with lk. Kernel is from .370
Source:
https://github.com/lilstevie/android_bootable_bootloader_lk
How To Build:
Coming soon
Sounds good!
Tablet Z has arrived today, once I've charged, rooted and backed up TA I will unlock and get lk booting
LK is up and running on my tabz now, in the morning I am going to push out a preview build.
updated first few posts with preview build and information on installing
just want to understand. when we flash lk in fastboot. what partion are we flashing LK to?
Sent from my SCH-I605 using xda app-developers app
skiwong20 said:
just want to understand. when we flash lk in fastboot. what partion are we flashing LK to?
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
it is being flashed to boot (the kernel partition). It takes 1Mb off the start to store lk along with enough room for future expansion. LK is aware of how it is set up and uses FOTAKernel as the kernel partition so that no room is lost to lk, then recovery gets the ~19MiB left of boot after lk.
lilstevie said:
it is being flashed to boot (the kernel partition). It takes 1Mb off the start to store lk along with enough room for future expansion. LK is aware of how it is set up and uses FOTAKernel as the kernel partition so that no room is lost to lk, then recovery gets the ~19MiB left of boot after lk.
Click to expand...
Click to collapse
thanks for the quick response. i went ahead and flashed your LK kernel. all is well i have it booting stock with your kernel and have twrp. time to see if i can play with your source and see if i can get a aosp kernel running. (i am new to building kernels):fingers-crossed:
Huge thanks again for getting this working.
skiwong20 said:
thanks for the quick response. i went ahead and flashed your LK kernel. all is well i have it booting stock with your kernel and have twrp. time to see if i can play with your source and see if i can get a aosp kernel running. (i am new to building kernels):fingers-crossed:
Huge thanks again for getting this working.
Click to expand...
Click to collapse
You shouldn't need to rebuild LK to get that to work - just install AOSP as normal, and install the kernel via LK fastboot, and it should work.
I believe (but haven't tested) that when dees_troy makes TWRP builds for LK, flashing a zip from within TWRP will flash the kernel such that LK boots it.
So AOSP should run fine without needing to tweak LK sources
Okay cool thanks for the heads will try later. This my first Sony device, so never had LK
Sent from my SGP311 using xda app-developers app
okay so i would like to report back to lilstevie that i finally got a aosp roms booting with his LK bootloader and so happy to have this.
just to let you know stevie i cherry picked your patch you summited to CM and it worked like a charm. i give it plus 1 on review.
Is this normal?
[23310.617921] usb 2-1.4: new high-speed USB device number 60 using ehci-pci
[23310.716898] usb 2-1.4: New USB device found, idVendor=18d1, idProduct=d00d
[23310.716909] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[23310.716915] usb 2-1.4: Product: Android
[23310.716920] usb 2-1.4: Manufacturer: Google
[23310.716925] usb 2-1.4: SerialNumber: 9P
]\xffffffc3\xffffffbd\xffffffbd\xffffffc3\xffffffb2\xffffffb2/\x19\x1d\xffffffc2\xffffffb2\xffffffb2
[23356.477514] usb 2-1.4: USB disconnect, device number 60
mamenyaka said:
Is this normal?
[23310.617921] usb 2-1.4: new high-speed USB device number 60 using ehci-pci
[23310.716898] usb 2-1.4: New USB device found, idVendor=18d1, idProduct=d00d
[23310.716909] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[23310.716915] usb 2-1.4: Product: Android
[23310.716920] usb 2-1.4: Manufacturer: Google
[23310.716925] usb 2-1.4: SerialNumber: 9P
]\xffffffc3\xffffffbd\xffffffbd\xffffffc3\xffffffb2\xffffffb2/\x19\x1d\xffffffc2\xffffffb2\xffffffb2
[23356.477514] usb 2-1.4: USB disconnect, device number 60
Click to expand...
Click to collapse
No this isn't normal, this is the issue with serial that I mentioned earlier. Best thing to do would be search for your serial in the TA image, then report back what the offset that it starts is.
lilstevie said:
No this isn't normal, this is the issue with serial that I mentioned earlier. Best thing to do would be search for your serial in the TA image, then report back what the offset that it starts is.
Click to expand...
Click to collapse
Sorry, what is the TA image?
mamenyaka said:
Sorry, what is the TA image?
Click to expand...
Click to collapse
The Trim Area is mmcblk0p1
lilstevie said:
The Trim Area is mmcblk0p1
Click to expand...
Click to collapse
And how can I read that partition?
just wanted to let everybody know that TeamWin has made a new TWRP 2.6 image for are devices. here is the link to teamwin webpage that has the image for use
http://teamw.in/project/twrp2/185
Hello
I recently got my mi5 after ordering from aliexpress and not a big fan of MIUI and wanting the cyanogenmod experience I applied for opening up the bootloader.
Today I recieved message that the request was granted and i happily started the progress with opening up the bootloader via the miflashunlock tool.
When I used the tool it gave me a message in lines of "No need to unlock this device" So i thought " Ok, maybe the seller had to unlock the bootloader to flash the global ROM or whatever.
I proceeed to flash TWRP and it flashed fine, so my bootloader must obviously have been open all the time?
Then I did a full wipe, instralled CM13 and opengapps and rebooted.
Now the trouble started.
All I boot into is a black screen, nothing happens.
If I try to boot into recovery I get a black screen.
I CAN boot to fastboot
So i go back to fastboot to check bootloader status.
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
How can this happen? How the hell can flashing CM lock my bootloader? I never checked the bootloader in fastboot before this, but since I was able to flash TWRP I must have had an open bootloader.
I have tried to flash different ROMS via the MiFlash tool and it gives me message that the devices is locked (duh!)
I have tried to open the bootloader via the unlock tool but it says that the currenct account is different from the account info on the device. Not very strange since I installed CM13...
I have tried to both flash and boot into TWRP via fastboot but I can't do this since device is locked...
Is my only option to try this
http://en.miui.com/thread-299790-1-1.html
Or can i just throw the phone in the bin after three days and buy a new phone from another company that values openess a little more?
---------------
Booting to EDL-mode with this suggestion:
http://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
After this you can flash whatever rom you like with the miflash tool
I still end up in the same situation when trying to flash CM13
Phone boots to black screen, I boot back to fastboot and phone is locked gain.
But this is something I can try to figure out on my own
Just an update so if anyone else who ends up in my situation searches forums they might find answer here.
Every time i flash CM13 the same thing happens. Bootloader gets locked and phone can only start in fastboot.
I tried installing RessurectionRemix instead and it worked straight away.
Why the hell this happens I have no clue, but this some of you geniouses maybe knows.
Right now I really don't care since RR works just fine for me
any solution ? I have the same problem
For all who are waiting for unlocking permission, you don't need to - if you'd like to root and install twrp.
Warning do not flash xiaomi.eu global or any other unofficial rom this way !
Good news - there is now patched aboot with installation instructions
I bought my redmi 4 pro from geekbuying and it came with preinstalled google play and semi mutlilingual (fake) Miui global 8.0.5.0.0(MBECNDG)
It seems geekbuying has installed a modifyed aboot (android bootloader), if you overflash it with xiaomi stock your device will check the rom for valid signing.
So you probably could flash unofficial rom if you don't flash aboot, but I can't test it anymore :/
btw I did this using linux and I used adb from Flashtool
As I still needed root so I tryed to unlock using fastboot :
First enable developer options by clicking on miui version in about phone menu
Go to Systems & Device > Additional Settings > Developers options
allow oem unlock and usb debugging
connect to the computer and allow access
turn off device
hold vol down and power - device reboots to fastboot
fastboot oem device-info
fastboot oem unlock-go
fastboot oem device-info < again, to check if its unlocked
restart device
Redo the setup and use browser to download supersu
get Recovery Flashable.zip
now download twrp to the computer
and follow the instructions how to install twrp.
Twrp started in chinese use, settings menu is second up from the right and last tab is language.
Flash supersu
I'll try this when I receive my Redmi 4.
Thanks for sharing!
It's that simple ?
I remember that my Redmi Note 3 Pro made some trouble with "unofficial" unlocking, when it comes to different ROMs...
Thanks anyway!
who checked this method?
Not working
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.016s
Click to expand...
Click to collapse
Hi just to say this worked fine for me. Had a new Redmi 4 Prime bought from Gearbest. Fake global rom version exactly same as mentioned above. I used vanilla Minimal ADB and Fastboot.
NB when device arrived no setup ie fake ROM had already been installed and configed (presumably to install play store).
Went straight in and tried the instructions above. Worked fine. Fastbook unlock then TWRP then supersu. Dumped Chinese CM13 ROM on and we're all good.
Not sure why works for some and why doesn't. Perhaps the exact version of the global rom? Perhaps the fact hadn't done anything with ROM and dived straight in with the unlock?
Tx for kentaurest for the tip!
J
Did you check if bootloader was locked before? Maybe it was unlocked by Gearbest when flashing ROM?
PS. I'm waiting for delivery and I will check your method
mulat666 said:
Did you check if bootloader was locked before? Maybe it was unlocked by Gearbest when flashing ROM?
PS. I'm waiting for delivery and I will check your method
Click to expand...
Click to collapse
Yeah so device-info before unlock was:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
Afterwards it was:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
Screenshot here: https://photos.google.com/share/AF1QipMnl4IHWqsJ60emRL-bLFsPdzSRN3EQ-LO9aBR3KgdtH8OVBplWE_AKXuQva_05CA?key=T2dOREx6N2w0SE10SmV6NEJuWHlSWEVJaXUwNU1B
J
Tried with my Redmi 4 Pro who came straight stock from china. It worked. Be sure to install good adb and fastboot drivers and be sure to check the correct developers options.
jontseng said:
Yeah so device-info before unlock was:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
Afterwards it was:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
Screenshot here: https://photos.google.com/share/AF1QipMnl4IHWqsJ60emRL-bLFsPdzSRN3EQ-LO9aBR3KgdtH8OVBplWE_AKXuQva_05CA?key=T2dOREx6N2w0SE10SmV6NEJuWHlSWEVJaXUwNU1B
J
Click to expand...
Click to collapse
One interesting thing is mine device which is unlocked with miflash shows the second line like this
(bootloader) Device critical unlocked: true.
I've just received phone with the same ROM as in first post. Could you please share ADB drivers? With universal I had:
Code:
fastboot.exe oem unlock-go
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.030s
The same issue on Ubuntu 16.04
Yeah mine is still "device critical unlocked: false" even after flashing other ROMS and mucking around.
Not quite sure what the issue is - did some quick google as maybe its some key system stuff still locked or because I didn't officially flash thru edl mode or something?
Not going to worry about it too much as I seem to be able to flash ROMs and stuff just fine (just flashed XPosed framework as well, FYI). Don't plan to go back to MIUI at any point anyhow - not really my cup of tea.
Would be interested if someone can explain more about this though. What am I missing out on?
PS Just for fun I ran the same fastboot device-info on my old redmi 3 (unlocked the official way) and it didn't have the "device critical unlocked" line at all (true or false..)
It is dangerous, you can install supersu and twrp this way, but don't flash non official roms.
Xiaomi roms should relock the bootloader.
Also don't try to install xposed, it didn't work for me.
After xposed made my phone bootloop I installed unofficial global and ended up with "bricked phone" left only with fastboot or black screen (qualcomm diagnostics interface 9000E) and couldn't turn off the phone.
I made deep flashing cable - usb cable where you can short GND and D+
http://xiaomitips.com/media/2016/08/Deep-FLash-Cable-Architecture-680x318.jpg
Connected phone to the computer (don't short the cables yet), used "fastboot reboot" to restart phone.
Quickly shorted GND and D+ for a few seconds, then windows installed HS-USB QDloader 9008 driver
and I could use Mi Flash to restore the phone, this time to the china developer rom
(fastboot version ends with .tgz) with clean all and locked options.
I was quite happy with fake global, twrp and supersu, pity xposed ruined it.
mulat666 said:
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.030s[/CODE]
Click to expand...
Click to collapse
Use deep flashing usb cable to get to EDL (downloader) mode.
@kentaurest I have a cable, would it work with the same fastboot commands?
mulat666 said:
@kentaurest I have a cable, would it work with the same fastboot commands?
Click to expand...
Click to collapse
Use windows and Mi Flash... as I described or use official unlocking method.
Hi Kentaurest tx for this. Forewarned is forearmed I guess.
So I assume it was the fake global ROM you were having trouble with re: Xposed - you hadn't flashed and other ROMs right?
(I have Xposed working on the 25/11 CM13 ROM from the China MIUI forums... But I guess its something of a crapshoot which ROMs do and don't break the device..)
To clarify (for future) - when you say "don't flash unsupported non xiaomi roms" do you mean any third party ROM, or ROMs now built specifically for the redmi 4?
Tx
J
jontseng said:
To clarify (for future) - when you say "don't flash unsupported non xiaomi roms" do you mean any third party ROM, or ROMs now built specifically for the redmi 4?
Click to expand...
Click to collapse
To my understanding bootloader checks if the system is signed with xiaomi key or not... so all xiaomi stuff will load, but xiaomi.eu unofficial global would not.
Also there is special Xposed for Miui, which I didn't try, last pages in the thread seem to suggest to use v86.2
http://forum.xda-developers.com/xposed/unofficial-xposed-miui-t3367634
kentaurest said:
It is dangerous, you can install supersu and twrp this way, but don't flash non official roms.
Xiaomi roms should relock the bootloader.
Also don't try to install xposed, it didn't work for me.
After xposed made my phone bootloop I installed unofficial global and ended up with "bricked phone" left only with fastboot or black screen (qualcomm diagnostics interface 9000E) and couldn't turn off the phone.
I made deep flashing cable - usb cable where you can short GND and D+
http://xiaomitips.com/media/2016/08/Deep-FLash-Cable-Architecture-680x318.jpg
Connected phone to the computer (don't short the cables yet), used "fastboot reboot" to restart phone.
Quickly shorted GND and D+ for a few seconds, then windows installed HS-USB QDloader 9008 driver
and I could use Mi Flash to restore the phone, this time to the china developer rom
(fastboot version ends with .tgz) with clean all and locked options.
I was quite happy with fake global, twrp and supersu, pity xposed ruined it.
Click to expand...
Click to collapse
Some others used this method instead. for 900E problem. https://www.youtube.com/watch?v=j27x5iJSS40, seems to work for th. Just read it from other forums
kentaurest said:
To my understanding bootloader checks if the system is signed with xiaomi key or not... so all xiaomi stuff will load, but xiaomi.eu unofficial global would not.
Click to expand...
Click to collapse
Hmmm. Funny the CM13 ROM runs then.
I suspect given kernal sources haven't been released they are just using the official build kernel, hence it passes any checks?
Hello,
Does any one know if the below link still applies to rooting all firmware versions (Android Version = 7.0, Build NBD92D) on the Nexus 6 (Project Fi)?
https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Thanks in advance!
gil_happy said:
Hello,
Does any one know if the below link still applies to rooting all firmware versions (Android Version = 7.0, Build NBD92D) on the Nexus 6 (Project Fi)?
https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Thanks in advance!
Click to expand...
Click to collapse
Flash Magisk. Install Magisk Manager. Done.
Optional: Install cool modules to modify your phone further.
I found out that this ( http://www.wugfresh.com/nrt/ ) was an easy and up to date way to get rooted... Read all the instructions and watch videos if you need to before doing anything
http://www.wugfresh.com/nrt/
_P__ said:
I found out that this ( http://www.wugfresh.com/nrt/ ) was an easy and up to date way to get rooted... Read all the instructions and watch videos if you need to before doing anything
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
Personally I prefer not to rely on toolkits. It's better to do things yourself so you can troubleshoot and fix if anything goes wrong.
snowrelyt said:
Flash Magisk. Install Magisk Manager. Done.
Optional: Install cool modules to modify your phone further.
Click to expand...
Click to collapse
I am in the process of trying the Magisk route and I'm having difficulty understanding the flash process. I have downloaded the Magisk-v11.1 zip to my Windows desktop and then copied it into the /Download directory on my Nexus 6. After googling a few things, I'm confused about how to flash / install on my Nexus 6. Some articles come up indicating I need to install TWRP Recovery, but I'm confused even more if I need to install this? Then I read another article (which I can't find now) about powering device down, then holding Vol Up, Vol Down, and PWR buttons to power phone back on and put in Recovery Mode (I think), and navigate and install the ZIP file. If this is the correct method, I didn't see an option to install from file or install from zip file.
gil_happy said:
I am in the process of trying the Magisk route and I'm having difficulty understanding the flash process. I have downloaded the Magisk-v11.1 zip to my Windows desktop and then copied it into the /Download directory on my Nexus 6. After googling a few things, I'm confused about how to flash / install on my Nexus 6. Some articles come up indicating I need to install TWRP Recovery, but I'm confused even more if I need to install this? Then I read another article (which I can't find now) about powering device down, then holding Vol Up, Vol Down, and PWR buttons to power phone back on and put in Recovery Mode (I think), and navigate and install the ZIP file. If this is the correct method, I didn't see an option to install from file or install from zip file.
Click to expand...
Click to collapse
Hey... You may flash TWRP recovery from bootloader using fastboot command. You can't root using stock recovery...
Download the latest TWRP from here and save it on your computer, preferably in the same folder you have ADB/fastboot:
https://dl.twrp.me/shamu/twrp-3.1.0-0-shamu.img
Just remove all security first before proceeding with the next steps (lockscreen scheme, password, pin. You can reenable them afterward. Just to avoid issues with twrp).
Your bootloader must be unlocked, otherwise unlock it first (you can find infos regarding bootloader unlock method in the general section of the Nexus 6 forum). Once/if the bootloader is unlocked, power down your device. Just press volume down and power button for a few seconds until you see a green Android laying down with it's belly opened...
Use fastboot to install TWRP using this command:
fastboot flash recovery twrp-3.1.0-0-shamu.img (the file you saved earlier on your computer).
Once it's finished, use the volume rocker and select "recovery mode" and press power button. It will reboot to TWRP.
Allow TWRP to make system modifications. Then tap install and go to the folder you saved the magical zip and install it.
Reboot and install magical manager as @snowrelyt said and you'll be ok.
Every info's you need can be found on the forum. If you're unsure, just ask again...
Good luck...
5.1 said:
Hey... You may flash TWRP recovery from bootloader using fastboot command. You can't root using stock recovery...
Download the latest TWRP from here and save it on your computer, preferably in the same folder you have ADB/fastboot:
https://dl.twrp.me/shamu/twrp-3.1.0-0-shamu.img
Just remove all security first before proceeding with the next steps (lockscreen scheme, password, pin. You can reenable them afterward. Just to avoid issues with twrp).
Your bootloader must be unlocked, otherwise unlock it first (you can find infos regarding bootloader unlock method in the general section of the Nexus 6 forum). Once/if the bootloader is unlocked, power down your device. Just press volume down and power button for a few seconds until you see a green Android laying down with it's belly opened...
Use fastboot to install TWRP using this command:
fastboot flash recovery twrp-3.1.0-0-shamu.img (the file you saved earlier on your computer).
Once it's finished, use the volume rocker and select "recovery mode" and press power button. It will reboot to TWRP.
Allow TWRP to make system modifications. Then tap install and go to the folder you saved the magical zip and install it.
Reboot and install magical manager as @snowrelyt said and you'll be ok.
Every info's you need can be found on the forum. If you're unsure, just ask again...
Good luck...
Click to expand...
Click to collapse
Thank you for this info... now I've gone down another rabbit hole after reading on different web sites
You say the bootloader must be unlocked - again after reading on different sites, there are 2 methods to determine if the bootloader is unlocked:
a) dial *#*#7378423#*#* (this did not work which upon reading said this method might now work)
b) C:\platform-tools>fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 'device-info' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.007s
So 2 things; I read that if the bootloader is not unlocked and you need to unlock it, it will wipe your phone (obviously I can't have that) and secondly, the command to determine if the bootloader is unlocked did not seem to work for some reason on my PC (the 'fastboot devices' detected my phone when I ran it).
gil_happy said:
Thank you for this info... now I've gone down another rabbit hole after reading on different web sites
You say the bootloader must be unlocked - again after reading on different sites, there are 2 methods to determine if the bootloader is unlocked:
a) dial *#*#7378423#*#* (this did not work which upon reading said this method might now work)
b) C:\platform-tools>fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 'device-info' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.007s
So 2 things; I read that if the bootloader is not unlocked and you need to unlock it, it will wipe your phone (obviously I can't have that) and secondly, the command to determine if the bootloader is unlocked did not seem to work for some reason on my PC (the 'fastboot devices' detected my phone when I ran it).
Click to expand...
Click to collapse
Well search how to boot into bootloader...
In bootloader you'll see this result:
Device is unlocked status code 3
If it says device locked... Well... You know what to do if you wish root...
Good luck...
5.1 said:
Hey... You may flash TWRP recovery from bootloader using fastboot command. You can't root using stock recovery...
Download the latest TWRP from here and save it on your computer, preferably in the same folder you have ADB/fastboot:
https://dl.twrp.me/shamu/twrp-3.1.0-0-shamu.img
Just remove all security first before proceeding with the next steps (lockscreen scheme, password, pin. You can reenable them afterward. Just to avoid issues with twrp).
Your bootloader must be unlocked, otherwise unlock it first (you can find infos regarding bootloader unlock method in the general section of the Nexus 6 forum). Once/if the bootloader is unlocked, power down your device. Just press volume down and power button for a few seconds until you see a green Android laying down with it's belly opened...
Use fastboot to install TWRP using this command:
fastboot flash recovery twrp-3.1.0-0-shamu.img (the file you saved earlier on your computer).
Once it's finished, use the volume rocker and select "recovery mode" and press power button. It will reboot to TWRP.
Allow TWRP to make system modifications. Then tap install and go to the folder you saved the magical zip and install it.
Reboot and install magical manager as @snowrelyt said and you'll be ok.
Every info's you need can be found on the forum. If you're unsure, just ask again...
Good luck...
Click to expand...
Click to collapse
5.1 said:
Well search how to boot into bootloader...
In bootloader you'll see this result:
Device is unlocked status code 3
If it says device locked... Well... You know what to do if you wish root...
Good luck...
Click to expand...
Click to collapse
Thanks so much! The bootloader was unlocked (I guess from an earlier root I performed using a Toolkit), and now I am rooted using Magisk.
gil_happy said:
Thanks so much! The bootloader was unlocked (I guess from an earlier root I performed using a Toolkit), and now I am rooted using Magisk.
Click to expand...
Click to collapse
Nice. Be careful what you do with your phone though. Since you seem to lack a bit of knowledge (no offence here). Read well before flashing anything... Avoid as much as possible the use of toolkits. I say this, since there are a lot of people bricking their device, unsure about what they did...
Cheers...
5.1 said:
Nice. Be careful what you do with your phone though. Since you seem to lack a bit of knowledge (no offence here). Read well before flashing anything... Avoid as much as possible the use of toolkits. I say this, since there are a lot of people bricking their and unsure about what they did...
Cheers...
Click to expand...
Click to collapse
No problem at all... thanks for the tips and advice
When i downloaded the RootNexus6MacToolkit, i unzipped the file and got this......RootNexus6MacToolkitzip.cpgz 411 bytes. What does that mean?
grunt0300 said:
When i downloaded the RootNexus6MacToolkit, i unzipped the file and got this......RootNexus6MacToolkitzip.cpgz 411 bytes. What does that mean?
Click to expand...
Click to collapse
It's the universe telling you to stop using toolkits...
Seriously though, further up this thread there are quite good instructions on how to root without toolkits.
Didgeridoohan said:
It's the universe telling you to stop using toolkits...
Seriously though, further up this thread there are quite good instructions on how to root without toolkits.
Click to expand...
Click to collapse
My problem has always been the command line. I've been reading up on terminal commands, and i might give it another try. A number of years ago, i bricked a Samsung Galaxy 3, and i've been gun shy ever since. I split my hard drive a while back, and if i can't figure out these commands, i'll go to the Windows 10 side and use Wug's toolkit.
grunt0300 said:
My problem has always been the command line. I've been reading up on terminal commands, and i might give it another try. A number of years ago, i bricked a Samsung Galaxy 3, and i've been gun shy ever since. I split my hard drive a while back, and if i can't figure out these commands, i'll go to the Windows 10 side and use Wug's toolkit.
Click to expand...
Click to collapse
As long as you keep your bootloader unlocked it's pretty difficult to brick a Nexus...
And to root your device you only really need to use two terminal commands. While in the bootloader (press and hold power + volume down to get there) run these commands from your computer (you can get adb and fastboot from here):
Code:
fastboot oem unlock
fastboot flash recovery <[I]insert_path_and_name_of_recovery_image_file_here[/I]>
The first one unlocks your bootloader. That will wipe your device though, so make sure to have a backup. If it's already unlocked, disregard....
The second one installs a custom recovery. Get the latest TWRP from here: https://twrp.me/motorola/motorolanexus6.html
After that you can boot to TWRP (from the bootloader), and flash the root zip of your choice.
Those are the basics. You've got lots more info in the stickies in the forum.
Didgeridoohan said:
As long as you keep your bootloader unlocked it's pretty difficult to brick a Nexus...
And to root your device you only really need to use two terminal commands. While in the bootloader (press and hold power + volume down to get there) run these commands from your computer (you can get adb and fastboot from here):
Code:
fastboot oem unlock
fastboot flash recovery <[I]insert_path_and_name_of_recovery_image_file_here[/I]>
The first one unlocks your bootloader. That will wipe your device though, so make sure to have a backup. If it's already unlocked, disregard....
The second one installs a custom recovery. Get the latest TWRP from here: https://twrp.me/motorola/motorolanexus6.html
After that you can boot to TWRP (from the bootloader), and flash the root zip of your choice.
Those are the basics. You've got lots more info in the stickies in the forum.
Click to expand...
Click to collapse
Getting my Nexus 6 next week. I'll let you know how it turned out. Thanks.