Hy,
i try to install CM13, but i will never got it rooted.
I try via Fastboot Minimal ADB.
After i send fastboot -i 0x2970 oem unlock-go there wil be info all ok send blabla.
But after new start there will be no unlock.
I send custom recovery, there will be info send ... blabla, but all time never will be new recovery.
i also try windroid. the same all time it looks like that its working but nothing happens.
Dev options is on USB Debbuging is on...... Unlock OEM ... is on.
i try 2 Pcs all time same... what i do wrong?
for my german friends.
Hallo,
ich habe hier ein neues Storm. Ich scheitere am Root. Egal was ich versuche es sieht aus als ob er die Befehle annimt aber es kommt nichts bei rum. Nach dem Root gibt es kein automatisches Full Wipe oder so. Es passiert nichts. Mit dem Porgramm Windroid das gleiche.
Die Entwickler Optionen sind alle richtig. Oem Unlock etc bla bla.
Hat jemand eine Idee?
Danke
Hmm, that's strange. Are you sure it stays bootloader locked? I had to try a lot of times because the stock ROM replaces any custom recovery with its own if not rooted.
Iam sure. OEM Bootloader unlock ( Yes )
I use Windows 10 64bit. Problem?
i try now on Windows7
here the Infos, but still not work.
do u see the failure?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x2970 oem unlock-go
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery kipper-c
ustom-recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (21208 KB)...
OKAY [ 0.718s]
writing 'recovery'...
OKAY [ 0.234s]
finished. total time: 0.967s
C:\Program Files (x86)\Minimal ADB and Fastboot>
mega.bs said:
i try now on Windows7
here the Infos, but still not work.
do u see the failure?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x2970 oem unlock-go
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery kipper-c
ustom-recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (21208 KB)...
OKAY [ 0.718s]
writing 'recovery'...
OKAY [ 0.234s]
finished. total time: 0.967s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Hmm, that's very strange. Never had the issue with my Storm, sorry.
I just typed Fastboot Oem Unlock without the -go part, try that maybe?
Johndawolf said:
I just typed Fastboot Oem Unlock without the -go part, try that maybe?
Click to expand...
Click to collapse
i tried, but the same.
will not work.
Did they have any unknown new secure level biuld in this phone?
Oh! Is the allow boot loader unlocking checkbox checked in the development options?
Yes it is.
mega.bs said:
Yes it is.
Click to expand...
Click to collapse
Well, then I don't know what this could be, sorry.
In your output-quotes you only used the vendor ID with the unlock command. Have you tried using it with the flash command as well? Like this:
Code:
fastboot -i 0x2970 flash recovery kipper-custom-recovery.img
That was necessary on my Storm.
If that doesn't work you can try to directly boot the recovery with fastboot:
Code:
fastboot -i 0x2970 boot kipper-custom-recovery.img
This will not flash the recovery on the phone so you have to do this every time you want to use a custom recovery, but at least it allows you to flash a custom rom.
traxo said:
In your output-quotes you only used the vendor ID with the unlock command. Have you tried using it with the flash command as well? Like this:
Code:
fastboot -i 0x2970 flash recovery kipper-custom-recovery.img
That was necessary on my Storm.
If that doesn't work you can try to directly boot the recovery with fastboot:
Code:
fastboot -i 0x2970 boot kipper-custom-recovery.img
This will not flash the recovery on the phone so you have to do this every time you want to use a custom recovery, but at least it allows you to flash a custom rom.
Click to expand...
Click to collapse
Thank uuuuu
the first code doesnt work, all the same problem. It seems that the recovery rom is read only or they have a special protection.
but with the second code and and the last twrp img it works. i have to use the code every time i want to flash a new rom or backup, but now i have cm13 and its looks to work great.
Related
Edit: Solved by using Method 2 on http://www.technobuzz.net/unbrick-oneplus-2/ . Thanks
I can boot into system / OxygenOS 2.1.0. But the device is not rooted. If I disable OEM unlock under settings, fastboot tells me I cannot unlock as it's disabled. If it's enabled in settings, running fastboot oem unlock only gives "OK", and the phone enters a bootloop. I power it down, re-enter fastboot and it's still locked.
Somehow my recovery partition got corrupted as I cannot boot into it (with volume down or from within the OS), the phone just goes back to the bootloop if I attempt it.
fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.078s]
finished. total time: 0.078s
Click to expand...
Click to collapse
E:\Android\OP2>fastboot oem unlock
...
OKAY [ 0.000s]
finished. total time: 0.000s
Click to expand...
Click to collapse
E:\Android\OP2>fastboot flash recovery twrp-2.8.7.0-oneplus2.img
target reported max download size of 536870912 bytes
sending 'recovery' (28144 KB)...
OKAY [ 0.671s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.702s
Click to expand...
Click to collapse
E:\Android\OP2>adb shell
[email protected]:/ $ u
su
/system/bin/sh: su: not found
Click to expand...
Click to collapse
Is there anything I can do at this point?
First, be sure that you are running CMD with administrator privileges, then check your phone drivers, if it still doesn't work, try with resetting your device, clear everything, install your rom once again.
Fr3ddyZ said:
First, be sure that you are running CMD with administrator privileges, then check your phone drivers, if it still doesn't work, try with resetting your device, clear everything, install your rom once again.
Click to expand...
Click to collapse
CMD isn't running with admin privileges. Why does that matter? The fastboot commands get through to the phone.
I can't install any ROM as I don't have root or recovery.
Thanks
My bad didn't read right your question.
EDIT: You said that you are using OxygenOS 2.1.0. try OTA update.
I met this problem too, and I found post http://forum.xda-developers.com/showpost.php?p=63021396&postcount=192 works
just executing "fastboot continue" twice!
mctrain said:
I met this problem too, and I found post http://forum.xda-developers.com/showpost.php?p=63021396&postcount=192 works
just executing "fastboot continue" twice!
Click to expand...
Click to collapse
That would get you booting alright but it wouldn't solve anything (root cause).
Lately I am trying to root my p8, when I came across this issue:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock 2104915622823317
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.140s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-2.8.7.1-p8.img
downloading 'boot.img'...
OKAY [ 0.556s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.559s
As seen above I am not being granted the permission to these commands even though I have a unlocked bootloader.
Because I can not think of any reason why this is happening I am asking for tipps I can try.
Thanks in advance
fastboot boot won't work........... i tried it too....... didn't try oem device-info though
I did something apparently pretty stupid and let my ALE-UL00 update itself after having installed iRoot (yeah I didn't know what I was doing). I really just wanted to install an English version of the OS since changing the language in the settings only changed about half of it...
Anyway, now when I boot the phone, I get a screen with three options, roughly translated "clear cache", "restore factory settings", and "reboot". Selecting any of these leads to the phone booting right back to that screen again.
I've tried to flash two different ROMs using the SD card method. Neither from Huawei's website as I can't find my model anywhere on there, but both claiming to be for my phone. So I boot into recovery mode (vol up + vol down + power) while plugged in, I see the USB emblem, and it gets stuck at 5%. If I boot in recovery mode without plugging it in, it just plain fails at 5% and gives me a link to a website that has pictures of phones (none of them mine) and no download links.
I can boot the phone in fastboot/rescue mode (vol down + power), and fastboot does recognize it. So I extracted the UPDATE.APP using Worstenbrood's tool and tried to fastboot it manually. This fails, and here's what happens:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
XXXXXXXXXXXXXXXX fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-build-number
...
(bootloader) :ALE-UL00C00B569
OKAY [ 0.074s]
finished. total time: 0.079s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock-state info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: LOCKED
OKAY [ 0.026s]
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.009s]
finished. total time: 0.014s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (22918 KB)...
OKAY [ 0.647s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.674s
If anyone has any clue what I can try next, I'd greatly appreciate it!
mathguyjohn said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock-state info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: LOCKED
OKAY [ 0.026s]
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.009s]
finished. total time: 0.014s
Click to expand...
Click to collapse
In particular, can anyone say why lock-state info says it's locked, but get-bootinfo says it's unlocked? The fastboot screen on my phone says "PHONE Unlocked"
Update: I tried holding volume up to get to the eRecovery menu. I entered my Wi-Fi password, it looked for an update, and then got a red explanation mark along with a message Google translate tells me is "get package installation failure".
Update: I guess BOTH of the ROMs I'd tried to flash from the SD card were corrupted. I found a working copy elsewhere on this forum. Though nobody responded to this particular thread, this forum was immensely helpful nevertheless, so thanks guys!
For anyone that stumbles across this comment, follow this.
JpegXguy said:
For anyone that stumbles across this comment, follow this.
Click to expand...
Click to collapse
Dude, my entire problem was that the procedure outlined in this link was not working. It's the first two words of the post title...
I don't mean to be rude, but when I had this problem, I wasted countless hours sifting through people repeating the exact same solution. If it had worked for me, I wouldn't have needed to post here. I was clear about this.
Fastboot wasn't letting me flash any of the imgs, so the only thing I could do was but the correct update.app on a micro SD card and boot into recovery mode. The only reason that didn't work was because I kept finding corrupted ROMs. The one in the post you linked to wasn't for the right model of phone, so that link would have done nothing for me.
The entire problem was that the UL00 seems woefully undersupported in the English-speaking community, so I had a difficult time finding the correct one. I did find the right one on this forum, though, and it's here: https://forum.xda-developers.com/p8lite/general/emui-4-0-1-ale-ul00c00b569ota-t3467620
hello
i had a beautiful and full working P9 Lite, VNS-L21 Dual Sim with stock Android 7.0.
wanted to downgrade to MM, but i got it bricked
boot unlocked, flashed TWRP, then OEM file and then Official (all from here : http://www.htcmania.com/showthread.php?t=1261335)
after starting official MM flashing by VOL+, VOL- and POWER, got error "Software install failed!" and dead from that moment.
flashed different TWRP and tried to boot into recovery by VOL+ and POWER, but nothing
also flashed different versions of 6.0 and 7 by fastboot, nothing. at some point boot got locked back, but unlocked it again.
disassembled, disconnected battery, nothing.
ready to try any ideea you think may be lucky.
thanks
If you're getting fastboot try and unlock your bootloader, install twrp for mm. Try and download your firmware eg L21C532B160, leave it in the zip format, place on your SD card, then boot into TWRP and flash the zip file. That should do the trick.
Sent from my HUAWEI VNS-L21 using Tapatalk
Install revolution recovery flash oem and dload c432
@slaughta8868, @Dimitardt - thanks, but in that situation only DC Phoenix or Furious Resurrector could get me out. These 2 progs are able to write absolutely anything into phone, and all needed partitions. Also able to revive by testpoint. i had access to Furious Resurrector and now phone is alive again.
but got this error, no matter what firmware is written.
any idea ?
photo fastboot http://imgur.com/a/vqoJM
C:\AndroidADB>fastboot oem get-build-number
...
(bootloader) :VNS-L21C432B130
OKAY [ 0.000s]
finished. total time: 0.000s
C:\AndroidADB>fastboot oem check-rootinfo
...
(bootloader) old_stat: RISK
(bootloader) now_stat: SAFE
(bootloader) change_time: 1470987496
OKAY [ 0.000s]
finished. total time: 0.000s
thanks
https://forum.xda-developers.com/hu...torial-rollback-n-to-mm-c432-devices-t3563955 try this
I have the same problem with my VNS-L31. Tried to rollback and it just turned off at 99% or 100% and now it does not turn back on. I can only access fastboot through the PC. No dload or recovery. Tried flashing separate system.img, boot.img etc. files but it does not work. Is there really no way other than Furious Resurrector or DC Phoenix to flash the full UPDATE.APP through fastboot? Is there no package, custom ROM, whatever, which has an android-info.txt inside?
i got same problem. after flash no vibration, no display, only fastboot accessible:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-build-number
...
(bootloader) :EVA-L09C432B136
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem check-rootinfo
...
(bootloader) old_stat: RISK
(bootloader) now_stat: RISK
(bootloader) change_time: 1463672304
OKAY [ 0.008s]
finished. total time: 0.010s
nbkappa said:
@slaughta8868, @Dimitardt - thanks, but in that situation only DC Phoenix or Furious Resurrector could get me out. These 2 progs are able to write absolutely anything into phone, and all needed partitions. Also able to revive by testpoint. i had access to Furious Resurrector and now phone is alive again.
but got this error, no matter what firmware is written.
any idea ?
photo fastboot http://imgur.com/a/vqoJM
C:\AndroidADB>fastboot oem get-build-number
...
(bootloader) :VNS-L21C432B130
OKAY [ 0.000s]
finished. total time: 0.000s
C:\AndroidADB>fastboot oem check-rootinfo
...
(bootloader) old_stat: RISK
(bootloader) now_stat: SAFE
(bootloader) change_time: 1470987496
OKAY [ 0.000s]
finished. total time: 0.000s
thanks
Click to expand...
Click to collapse
Can you show me test point image VNS-L31 please?
Test point
Here test point image
Hi,
I would like to ask you about a support in programming my "old" Redmi 3s, becase I want to have a newer Android version on the device
The device has Android 6.0.1 MMB29M, MIUI10 Global 9.3.28 Beta, kernel: 3.18.20-g89abe5f.
When I enter fastboot mode, I do not see any version of fastboot, only "picrure of bunny" with FASTBOOT.
Bootloader is arelady unlocked (as in bellow logs).
After when I flashed TWRP and I tried boot twrp.img, I got info:
FAILED (remote: dtb not found)
I tried with available the oldest one as I found on page Redmi3s-Land is twrp-3.1.1-0-land.img , and also tried with the newest one twrp-3.6.2_9-0-land.img.
ISSUE:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.403s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.487s
BOOTLOADER:
I have unlocked bootloader:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.017s
What I should do to fix this issue and to enter TWRP:
FAILED (remote: dtb not found)
?
Ahh.. I fouded solution. :/ :/
Commands:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
calls twrp.img file from above folder, not from Redmi 3s interal flash, where I copied a new twrp.img to programming.
So simply I moved "right" file of twpr inside to folder "Minimal ADB and Fastboot", and then commands works an issue FAILED (remote: dtb not found) doest apperas.