Im trying to charge the battery using this script because i doesnt charge in normal mode : /
@ECHO off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
This, below, is the response I get...
(bootloader) battery-voltage: Not Found
getvar:battery-voltage FAILED (Remote Failure)
finished. total time: 0.000s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
yesterday i cancelled an installation of a stock firmware and then the charging problem start to happen! now i dont have any so installed and maybe the battery info was deleted too, i dont know what to do i need help! thanks
Related
I recently acquire a Moto G GPE, I read several post and also try with this https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b and none works. See output:
Code:
D:\>cd d:\Software\Android\ADT\sdk\platform-tools\
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem unlock_data
...
(bootloader) 'unlock_data' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.012s]
finished. total time: 0.012s
D:\>cd d:\Software\Android\ADT\sdk\platform-tools\
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem unlock_data
...
(bootloader) 'unlock_data' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.012s]
finished. total time: 0.012s
Any help?
reynierpm said:
I recently acquire a Moto G GPE, I read several post and also try with this https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b and none works. See output:
Code:
D:\>cd d:\Software\Android\ADT\sdk\platform-tools\
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem unlock_data
...
(bootloader) 'unlock_data' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.012s]
finished. total time: 0.012s
D:\>cd d:\Software\Android\ADT\sdk\platform-tools\
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem unlock_data
...
(bootloader) 'unlock_data' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.012s]
finished. total time: 0.012s
Any help?
Click to expand...
Click to collapse
When you are in fastboot mode, what does the seventh line says?
"Device is ******. Status Code: *"
Also, have you tried this code?
Code:
fastboot oem unlock
Z-WolF said:
When you are in fastboot mode, what does the seventh line says?
"Device is ******. Status Code: *"
Also, have you tried this code?
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thanks it was LOCKED but after run the command you suggest me and follow the instructions now I have my device UNLOCKED. Now I'm trying to install this recovery but I can't because I don't know how to install from ZIP, any guide or help?
Hi
I'm trying to fix a Moto E that won't boot up, it's stuck on the bootanimation.
I managed to get into fastboot and unlock the bootloader but when I tried to flash TWRP i get this:
C:\Users\Gise\Desktop\fastboot>mfastboot flash recovery twrp-2.8.6.0-condor.img
target max-sparse-size: 256MB
sending 'recovery' (8652 KB)...
OKAY [ 0.297s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.328s
I can't flash it because of the low battery and it won't charge because once I exit fastboot it gets on a booting loop
So I tried using this script
@ECHO off
:start
mfastboot getvar battery-voltage
mfastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
and I get this:
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.010s
rebooting into bootloader...
OKAY [ 1.980s]
finished. total time: 1.980s
< waiting for device >
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.010s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.006s
and so on...
Somebody help please, i don't even know if the script is working because it won't give me the voltage of the battery
xgisse said:
Hi
I'm trying to fix a Moto E that won't boot up, it's stuck on the bootanimation.
I managed to get into fastboot and unlock the bootloader but when I tried to flash TWRP i get this:
C:\Users\Gise\Desktop\fastboot>mfastboot flash recovery twrp-2.8.6.0-condor.img
target max-sparse-size: 256MB
sending 'recovery' (8652 KB)...
OKAY [ 0.297s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.328s
I can't flash it because of the low battery and it won't charge because once I exit fastboot it gets on a booting loop
So I tried using this script
@ECHO off
:start
mfastboot getvar battery-voltage
mfastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
and I get this:
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.010s
rebooting into bootloader...
OKAY [ 1.980s]
finished. total time: 1.980s
< waiting for device >
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.010s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.006s
and so on...
Somebody help please, i don't even know if the script is working because it won't give me the voltage of the battery
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
Your thread will be moved to Moto E Q&A,Help and Troubleshooting.
Are you able to charge with the device turned off?
___
v7
XDA Assist
Hello all,
I'm hoping you guys could help me out. I have a bricked Mate 8 and am trying to fix it.
I'm hoping anyone with a Mate 8 (any and every model) could run these commands for me:
(first please boot to fastboot mode.)
fastboot getvar rescue_version
fastboot getvar rescue_phoneinfo
fastboot oem get-product-model
fastboot oem get-psid (if this has personal information please replace it with X or something.)
fastboot getvar vendorcountry
and let me know what they return.
Also, could you let me know if you run HiSuite and choose System Recovery with the device in fastboot, whether you get a 'phone not supported' screen or whether it works.
Thanks!
Hi,
Here's the results from mine:
D:\Mate-8>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NXT-C900B160
finished. total time: 0.016s
D:\Mate-8>fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.078s
gnasher666 said:
Hi,
Here's the results from mine:
D:\Mate-8>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NXT-C900B160
finished. total time: 0.016s
D:\Mate-8>fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.078s
Click to expand...
Click to collapse
Thank you for checking that!
I'm getting closer to successfully tricking HiSuite into wanting to recover my phone.
Can you please run these commands?
fastboot oem get-product-model
fastboot oem get-psid
fastboot getvar vendorcountry
I think oem get-psid might output personal information. If it does, don't post it obviously. I think the most important one is getvar vendorcountry, potentially, because mine just fails on that. When you post, please post any leading spaces, etc before the text so I have an exact replication of the command.
Thank you!
The getvar command didn't work, neither did getvar all.
D:\Mate-8>fastboot oem get-product-model
...
(bootloader) HUAWEI NXT-L29
OKAY [ -0.000s]
finished. total time: -0.000s
D:\Mate-8>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
D:\Mate-8>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: Command not allowed)
finished. total time: 0.021s
D:\Mate-8>fastboot oem get-psid
...
(bootloader) SN:23Q7Nxxx
(bootloader) IMEI:xxx
IMEI:xxx
OKAY [ 0.022s]
finished. total time: 0.022s
gnasher666 said:
The getvar command didn't work, neither did getvar all.
D:\Mate-8>fastboot oem get-product-model
...
(bootloader) HUAWEI NXT-L29
OKAY [ -0.000s]
finished. total time: -0.000s
D:\Mate-8>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
D:\Mate-8>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: Command not allowed)
finished. total time: 0.021s
D:\Mate-8>fastboot oem get-psid
...
(bootloader) SN:23Q7Nxxx
(bootloader) IMEI:xxx
IMEI:xxx
OKAY [ 0.022s]
finished. total time: 0.022s
Click to expand...
Click to collapse
Thank you very much for trying that.
It's strange. It looks like HiSuite sends all of those commands to my phone, the last one is vendorcountry which fails, then tells me my phone isn't supported (even though it lists NXT-AL10 as supported for recovery.)
Would you mind trying the System Recovery option in HiSuite and see what happens for you?
Also, if anyone with NXT-AL10 could please check if HiSuite is able to do recovery when it's in fastboot mode, this would potentially help me discover a universal unbrick method, so please let me know!
Here are the results from my AL10 with international L29C900B133 rom :
C:\adb>fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.069s
C:\adb>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NXT-C900B133
finished. total time: 0.000s
C:\adb>fastboot oem get-product-model
...
(bootloader) NEXT
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot oem get-psid
...
(bootloader) SN:VKN5TXXXXXXXXXXX
(bootloader) IMEI:XXXXXXXXXXXXXXX
IMEI:XXXXXXXXXXXXXXX
OKAY [ 0.000s]
finished. total time: 0.016s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.008s
As you can see, getvar didn't work for me neither.
And it seems that HiSuite isn't able to do recovery when it's in fastboot mode, because it doesn't see my phone in this mode...
Hi.
Here are the results of my AL10 with chinese ROM AL10C00B156 :
C:\adb>fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.068s
C:\adb>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NXT-AL10C00B156
finished. total time: 0.006s
C:\adb>fastboot oem get-product-model
...
(bootloader) HUAWEI NXT-AL10
OKAY [ 0.006s]
finished. total time: 0.008s
C:\adb>fastboot oem get-psid
...
(bootloader) SN:VKN5T15C24012455
(bootloader) IMEI:869906027864873
IMEI:869906027429222
OKAY [ 0.011s]
finished. total time: 0.012s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: Command not allowed)
finished. total time: 0.011s
I'll try HiSuite asap...
EDIT : HiSuite (4.0.4.301) recovery doesn't work for me neither : when I click on "Recover system" in the "Entered system recovery mode" screen, it says "Your device does not take care of the recoveries system"...
Thank you very much. So I guess NXT-AL10 is not supported with HiSuite, even though it says it is... Very strange!
It also looks like it's likely there's no way to recover my phone, unfortunately. I might soon give up on trying to find a way to fix it myself (even though I have fastboot...) and send phone to China to see if they can fix it under warranty.
I hope you'll find a solution !
Good luck.
Return from a NXT-L09
duraaraa said:
Hello all,
I'm hoping you guys could help me out. I have a bricked Mate 8 and am trying to fix it.
I'm hoping anyone with a Mate 8 (any and every model) could run these commands for me:
(first please boot to fastboot mode.)
Also, could you let me know if you run HiSuite and choose System Recovery with the device in fastboot, whether you get a 'phone not supported' screen or whether it works."
Click to expand...
Click to collapse
This is what I got:
:\sdk\platform-tools>fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.063s
C:\sdk\platform-tools>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NXT-L09C212B120
finished. total time: 0.016s
C:\sdk\platform-tools>fastboot oem get-product-model
...
(bootloader) HUAWEI NXT-L09
OKAY [ 0.016s]
finished. total time: 0.016s
C:\sdk\platform-tools>fastboot oem get-psid
...
(bootloader) SN:AXXXXXXXXXXXXX
(bootloader) IMEI:8XXXXXXXXXXXX
OKAY [ 0.016s]
finished. total time: 0.016s
C:\sdk\platform-tools>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: Command not allowed)
finished. total time: 0.016s
On the hisuite, I get a message that says my device is not supported, also wifi recovery does not work, Im guessing that happens because I have unloocked the bootloader?
I was able to get an input when running fastboot vendor country. Mine is bricked at least for the moment as well. No go with hisuite to restore.
C:\Users\Malekowsky>fastboot getvar vendorcountry
vendorcountry: dualcu/cn
finished. total time: 0.005s
fastboot oem get-psid
...
FAILED (remote: Command not allowed)
can't get imei info, wich command i can use?
Hi
I'm writing in the names of all Meizu PRO 5 Owners.
Most of us tried to flash custom recovery after downgrading the rom which downgrade the bootloader to unlockable version.
Then we unlocked it Simply with
Code:
fastboot oem unlock
.
Everything was fine untill we flashed custom recovery and after we flashed the latest meizu rom, which flashes NOT UNLOCKABLE BOOTLOADER BACK TO THE PHONE AND ERASES RECOVERY!
In that state - we fakd up, we stuck on rom without recovery and with not unlockable bootloader.
for some and many of the users the phone can act as a door stopper.
Code:
fastboot oem unlock
gets permission denied, and flash recovery with fastboot gets the same - permission denied Aka Operation not Permitted.
This pro 5 is a samsung galaxy s6 like specs, it has Exynos 7420 4gb RAM.
We have a leaked internal tools of Meizu ODIN Like, which they are not supported the new bootloader, flash from there requires signing the files with the right token, and the tool doesnt know to do that on the new Bootloader.
new tools is not an option now and meizu doesn't want to help us, they want take money for "board replacement"..
I Know that a solution can be found!:
NOTE: THE NEW BOOTLOADER CAN BE UNLOCKED VIA FASTBOOT! - IF WE WILL GIVE THE RIGHT TOKEN KEYS TOGETHER.
bootloader unlock key is total 512 bytes key and we can insert it each time divided by 16 bytes each by using fastboot oem unlock [16 bytes key part here].
i can get the token for bootloader with:
Code:
fastboot oem random
which generates key like this:
F19A38EE437B8C21DD49A6BF2BC47E24
Code:
(bootloader) F19A38EE437B8C21DD49A6BF2BC47E24
OKAY [ 0.005s]
So the only thing we have to do to make this done is:
1. get key from the current bootloader and then think about the token key generation scheme and then get the bootloader completely unlocked.
and IF NOT, we can reverse engineer the new bootloader.
SO THE QUESTION IS:
Can you help us generate the unlock key from the token?
I know how we insert the unlock key back, its something like this
Code:
fastboot oem verify:[32 divded characters of the key string goes here]
total should be 16 commands like this so its should be 512 characters key.
HERE IS AN EXAMPLE OF SUCCESSFULL PHONE UNLOCK BY MEIZU - I took this from meizu's tool logs
these logs are actually showing device unlock, format, reflash,relock bootloader
==============================================================================
Code:
===========================================================
| Trace On
===========================================================
[09:52:44:926]Tips: Device insert. ID: 04358ca68588 [B]this is the meizu device serial[/B]
[09:52:45:378]Token sign operator. Begin -----------------------------
[09:52:45:379]Tips: Token signing...
[09:52:45:380]Read uboot serial. Command: fastboot -s "04358ca68588" oem random [B]here it asks for a random key from the phone - EACH TIME this command is executed - the phone generates new key![/B]
[09:52:45:476]...
(bootloader) 8F32FB562DB8D34F1E75E97C17E85218 [B]so thats the key we got from the phone[/B]
OKAY [ 0.001s]
finished. total time: 0.001s
[B]thats the key that meizu servers replied back - 512 characters key [/B]
[09:52:56:027]6FF64BAE41517CEBFB3AD2A873DC472BA7E09D57151917452D13F0FCB1C38CAD6D3C7688B2D4EA646E32EA0150419AD3E7018BC987CCBC531874A213970E8334B641F2D6BF813A9E0A9857FA187FFB6FFFA9DD5CD083703ECC131E2E8E4A4D14936DC364B361C68E26079ED6E070CF36691F1DC1AE2FD3593688EB9D3F9341991FBF298BF8117127AD334E72D94E0D7D2E9DE104973F06BFF42734CD3E2641A50907CEDC40DBD77AC3E44B686A5A24DE3FDBAC68C322876BFF1AD322D04A933EEFACB28CA011D216ABC8F26CBE9A5A0C1EC38192DE9E3E08F2CF168173C1F12A7F5BCD8B451B711A769CF8D581152822BA02A3890A4037F02F38685752C786A6
[09:52:56:027]fastboot -s "04358ca68588" oem verify:6FF64BAE41517CEBFB3AD2A873DC472B [B]1st 32 characters inject of 512[/B]
[09:52:56:124]...
(bootloader) 16
OKAY [ -0.000s]
finished. total time: -0.000s
[09:52:56:124]fastboot -s "04358ca68588" oem verify:A7E09D57151917452D13F0FCB1C38CAD [B]SO ON...[/B]
[09:52:56:220]...
(bootloader) 32
OKAY [ 0.000s]
finished. total time: 0.000s
[09:52:56:220]fastboot -s "04358ca68588" oem verify:6D3C7688B2D4EA646E32EA0150419AD3 [B]SO ON...[/B]
[09:52:56:316]...
(bootloader) 48
OKAY [ 0.000s]
finished. total time: 0.000s
[09:52:56:316]fastboot -s "04358ca68588" oem verify:E7018BC987CCBC531874A213970E8334 [B]SO ON...[/B]
[09:52:56:413]...
(bootloader) 64
OKAY [ -0.000s]
finished. total time: -0.000s
[09:52:56:413]fastboot -s "04358ca68588" oem verify:B641F2D6BF813A9E0A9857FA187FFB6F [B]SO ON...[/B]
[09:52:56:510]...
(bootloader) 80
OKAY [ -0.000s]
finished. total time: -0.000s
[09:52:56:510]fastboot -s "04358ca68588" oem verify:FFA9DD5CD083703ECC131E2E8E4A4D14 [B]SO ON...[/B]
[09:52:56:606]...
(bootloader) 96
OKAY [ -0.000s]
finished. total time: -0.000s
[09:52:56:606]fastboot -s "04358ca68588" oem verify:936DC364B361C68E26079ED6E070CF36 [B]SO ON...[/B]
[09:52:56:703]...
(bootloader) 112
OKAY [ 0.000s]
finished. total time: 0.000s
[09:52:56:703]fastboot -s "04358ca68588" oem verify:691F1DC1AE2FD3593688EB9D3F934199 [B]SO ON...[/B]
[09:52:56:799]...
(bootloader) 128
OKAY [ -0.000s]
finished. total time: -0.000s
[09:52:56:799]fastboot -s "04358ca68588" oem verify:1FBF298BF8117127AD334E72D94E0D7D [B]SO ON...[/B]
[09:52:56:896]...
(bootloader) 144
OKAY [ 0.001s]
finished. total time: 0.001s
[09:52:56:896]fastboot -s "04358ca68588" oem verify:2E9DE104973F06BFF42734CD3E2641A5 [B]SO ON...[/B]
[09:52:56:993]...
(bootloader) 160
OKAY [ 0.001s]
finished. total time: 0.001s
[09:52:56:993]fastboot -s "04358ca68588" oem verify:0907CEDC40DBD77AC3E44B686A5A24DE [B]SO ON...[/B]
[09:52:57:090]...
(bootloader) 176
OKAY [ 0.001s]
finished. total time: 0.001s
[09:52:57:090]fastboot -s "04358ca68588" oem verify:3FDBAC68C322876BFF1AD322D04A933E [B]SO ON...[/B]
[09:52:57:186]...
(bootloader) 192
OKAY [ -0.000s]
finished. total time: -0.000s
[09:52:57:186]fastboot -s "04358ca68588" oem verify:EFACB28CA011D216ABC8F26CBE9A5A0C [B]SO ON...[/B]
[09:52:57:283]...
(bootloader) 208
OKAY [ 0.000s]
finished. total time: 0.000s
[09:52:57:283]fastboot -s "04358ca68588" oem verify:1EC38192DE9E3E08F2CF168173C1F12A [B]SO ON...[/B]
[09:52:57:379]...
(bootloader) 224
OKAY [ 0.001s]
finished. total time: 0.001s
[09:52:57:379]fastboot -s "04358ca68588" oem verify:7F5BCD8B451B711A769CF8D581152822 [B]SO ON...[/B]
[09:52:57:476]...
(bootloader) 240
OKAY [ 0.001s]
finished. total time: 0.001s
[09:52:57:476]fastboot -s "04358ca68588" oem verify:BA02A3890A4037F02F38685752C786A6 [B]SO ON...[/B]
[09:52:57:668]...
(bootloader) 256
(bootloader) verify success [B]PHONE'S BOOTLOADER IS FINALLY UNLOCKED![/B]
OKAY [ 0.128s]
finished. total time: 0.128s
[09:52:57:670]Tips: Token singed successfully
[09:52:57:670]Token sign operator. End -----------------------------
[09:52:57:672]Tips: Format part
[09:52:57:672]fastboot -s "04358ca68588" oem cmd "scsi erase 0 0x80000 0" [B]When the bootloader is unlocked - they use cmd to shell command for formating the partition[/B]
[09:53:01:948]...
OKAY [ 4.242s]
finished. total time: 4.242s
[09:53:01:951]Tips: Format part. ok
[09:53:01:953]Tips: Partition disk
[09:53:01:953]fastboot -s "04358ca68588" oem cmd "fdisk -c 0" [B]repartitioning[/B]
[09:53:02:145]...
OKAY [ 0.132s]
finished. total time: 0.132s
the rest is locking the bootloader again - not interested....
the problem is that the token generation is done on meizu servers, and we unable to get access to there...
Maybe because we know example of token generation we can in way of bruteforce to find the correct token generation formula for the random key that i generated?
Please devs , join this discussion,Then we can help alot users to enjoy their phone again
I'm suffering the exact same issue as you mate.
support the thread!
Its so sad that no one from the devs puts attention,
Please guys we need support
Up!
deliad said:
Its so sad that no one from the devs puts attention,
Please guys we need support
Click to expand...
Click to collapse
Why cant you completely erase the emmc and reflash the whole firmware using spflash tool
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
This includes bootloader
Its not a MTK chipset, its a samsung Exynos
Samsung Exynos 7420=You're Boned, btw thanks for helping any of us experience Ubuntu Touch.
Alternatively, have you tried using ODIN & a PIT file system???? Just an off the wall suggestion since I often wonder how closely related these device lines really are.
Sent From My sm-g298F
Up, i've the same problem.
Check this : https://forum.xda-developers.com/meizu-pro-5/how-to/to-unlock-hardbricked-meizu-pro-5-t3566173
Any news?
https://blog.quarkslab.com/reverse-engineering-samsung-s6-sboot-part-i.html
I found this, I can't understand this but here he is talking about samsung and meizu phones with exynos
Hi I flashed my recovery to TWRP recovery, but unfortunately if I enter recovery mode in boot menu I'll get "no command" screen and I have no idea what causes that.
commands I ran:
Code:
PS C:\Users\honza\Downloads\twrp> fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 20.799s]
finished. total time: 20.799s
PS C:\Users\honza\Downloads\twrp> fastboot flash recovery twrp-3.2.3-0-shieldtablet.img
target reported max download size of 100663296 bytes
sending 'recovery' (12448 KB)...
OKAY [ 0.545s]
writing 'recovery'...
OKAY [ 0.456s]
finished. total time: 1.001s
PS C:\Users\honza\Downloads\twrp> fastboot reboot
rebooting...
finished. total time: 0.017s
PS C:\Users\honza\Downloads\twrp> adb devices
List of devices attached
PS C:\Users\honza\Downloads\twrp> fastboot devices
thanks for help.
temporaly solved
I tried to use "fastboot boot" and this works well, and since I need TWRP only temporaly this solution is sufficient for me.