Hello,
My A3 was unlocked with root, android 9 February security patch
Randomly Google play service stop working, after deleting cache it was fine.
Again randomly the prone start to act weird, restart it and then appear " Can't load android system. Your data may be corrupt."
The only options are try again and Factory data reset. ( like in the image https://i.redd.it/8nf9k5v33u1z.jpg )
Because i have important information i can't do factory reset so tried to flash stock fastboot rom with miflash.
Fastboot was accessible, BUT after trying to adb devices check it shows- List of devices attached* daemon not running. starting it now on port 5037 ** daemon started successfully * so it was not really able to connect. My Computer does not recognise it as Mi A3.
So after flashing fastboot Android One logo unlocked, appear several time, like blinking 4-5 times, and again jump in to fastboot mode.
First tried to flash V10.3.15.0.PFQEUXM, than V10.3.14.0.PFQEUXM. None of them did the work.
Attaching some logs.
By the way i use MiFlash20181115 it was the latest found
Thank you in advance , BE HAPPY and SAFE
Tried to add before fastboot %* reboot , fastboot $* set_active a , bur the result was the same
1. avoid downgrades, your data might get corrupted and you'll end up with factory reset anyway
2. per the logs it seems that everything flashes correctly, make sure that you have partition A as active (https://forum.xda-developers.com/showpost.php?p=81408355&postcount=2). Type both commands (one will fail) in cmd window with phone connected via fastboot.
_mysiak_ said:
1. avoid downgrades, your data might get corrupted and you'll end up with factory reset anyway
2. per the logs it seems that everything flashes correctly, make sure that you have partition A as active (https://forum.xda-developers.com/showpost.php?p=81408355&postcount=2). Type both commands (one will fail) in cmd window with phone connected via fastboot.
Click to expand...
Click to collapse
Phone is not recognised in cmd, only if use- Install from ADB option from recovery it show the device.
alexandarpb said:
Phone is not recognised in cmd, only if use- Install from ADB option from recovery it show the device.
Click to expand...
Click to collapse
You seem to confuse ADB and Fastboot. Connect mobile in FASTBOOT mode and type in those two commands. If there's an error, paste the output here.
_mysiak_ said:
You seem to confuse ADB and Fastboot. Connect mobile in FASTBOOT mode and type in those two commands. If there's an error, paste the output here.
Click to expand...
Click to collapse
PS C:\Users\Sashko\Desktop\platform-tools> fastboot set_active a
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\Users\Sashko\Desktop\platform-tools> fastboot --set-active=a
C:\adb\fastboot.exe: unknown option -- set-active=a
PS C:\Users\Sashko\Desktop\platform-tools>
alexandarpb said:
PS C:\Users\Sashko\Desktop\platform-tools> fastboot set_active a
usage: fastboot [ <option> ] <command>
...
PS C:\Users\Sashko\Desktop\platform-tools> fastboot --set-active=a
C:\adb\fastboot.exe: unknown option -- set-active=a
PS C:\Users\Sashko\Desktop\platform-tools>
Click to expand...
Click to collapse
Uninstall/remove existing fastboot.exe from all locations on your PC and use the latest version https://developer.android.com/studio/releases/platform-tools
_mysiak_ said:
Uninstall/remove existing fastboot.exe from all locations on your PC and use the latest version https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
From my previous PC i managed to get proper result
C:\Users\PC-1\Desktop\mi a3\platform-tools>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.002s]
Finished. Total time: 0.012s
C:\Users\PC-1\Desktop\mi a3\platform-tools>
Should i now use miflash again to flash the fastboot rom or?
Thank you so much for all your answers!!!
alexandarpb said:
From my previous PC i managed to get proper result
C:\Users\PC-1\Desktop\mi a3\platform-tools>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.002s]
Finished. Total time: 0.012s
C:\Users\PC-1\Desktop\mi a3\platform-tools>
Should i now use miflash again to flash the fastboot rom or?
Thank you so much for all your answers!!!
Click to expand...
Click to collapse
Just start the phone. Re-flash only if it won't boot.
_mysiak_ said:
Just start the phone. Re-flash only if it won't boot.
Click to expand...
Click to collapse
Thank you, you are my saviour, unfortunately my data is gone... but at least it work now.
Thank you for everything
alexandarpb said:
Thank you, you are my saviour, unfortunately my data is gone... but at least it work now.
Thank you for everything
Click to expand...
Click to collapse
I suppose that you already performed the factory reset, but for the future - you could try flashing TWRP first, backup/export data and perform factory reset only after that.
_mysiak_ said:
I suppose that you already performed the factory reset, but for the future - you could try flashing TWRP first, backup/export data and perform factory reset only after that.
Click to expand...
Click to collapse
Definitely, but i was thinking that if the phone is not recognised in adb command it would not be able to do anything with fastboot command. It is nonsense i know...
Thank again, by the way which recovery is better OrangeFox Recovery or TWRP ?
alexandarpb said:
Definitely, but i was thinking that if the phone is not recognised in adb command it would not be able to do anything with fastboot command. It is nonsense i know...
Thank again, by the way which recovery is better OrangeFox Recovery or TWRP ?
Click to expand...
Click to collapse
I haven't used custom recovery for A3 yet, but TWRP would be my first choice if a need occured.
Related
Well, I guess I unintentionally softbricked my Hero...
So the story:
I downloaded via OTA the update. And i tried to install, but in the middle the install just stopped, and... stood still for a long long time... ok, battery ran out and i plugged the charger and tried to turn on ... annnd stucked at HERO sign...
i tried hard reset and nothing.. im trying that with the SDK and CMD and the fastboot devices doesn't show anything.
I tried to boot one of millions of customed ROMs and nothing, i guess i had to root earlier, or something /noob here.
I kinda ran out of options here and i don't know what to do...
Could you guys please help me out?
Taiwanese version of HTC Hero here.
yep, and i'm kinda desperate here too.
---
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.08.29
Can you force into hboot/fastboot via holding volume down and power for a bit from cold start?
-------------------------------------
Sent via the XDA Tapatalk App
Yes, I Can access HBoot and fastboot...
aaaaaand i found my device at the fastboot devices.
HTxxxxxxxxxx64
Excellent then you should now be able to redo things ... let us know
OK, accessed the hero... then, tried to apply the update and...
E:Failure at line 11: run_program PACKAGE:checkspace -f /data 26214400 "ro.build.fingerprint=chunghwa/htc_hero/hero/hero:1.5CUPCAKE" FOTAERRORMESSAGES
actually i don't know what to do... :/
Try this ... http://forum.xda-developers.com/showpost.php?p=6714023&postcount=14
Basically go back into fastboot and try to install the official 1.5 (which will fail) but the process clears something up and allowed another member here to reflash cleanly ...
Try to wipe your data and then install the next ROM, i had the same problem
I do not think he has rooted or installed a modded recovery image if I read his first post correctly
i guess i had to root earlier, or something /noob here.
Click to expand...
Click to collapse
Yeah, i didn't root or anything... and i tried the other dude footsteps... and... blank, nothing...
and waiting for HTC Response team says something...
tried installing official rom, nothing.
tried updating the official update, also nothing.
tried wipe data, same thing.
well, i guess i have a new brick :/
If you can get it to fastboot ok and open the conversation, there must be something that can be done.
According to the definitive fastboot docs (http://android-dls.com/wiki/index.php?title=Fastboot) there might be a few options to try ...
HTML:
<pre>usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline</pre>
Perhaps the -w to clear those areas might do it ...
Alternatively, I _believe_ you could flash the 1.62 recovery image to the phone in fastboot and then wipe from in there, or flash an 'update.zip' style rom from in here as well ...
Good luck, someone more knowledgeable than I may have other ideas ...
Broken Root???????
WELLLLLL...
I'm not sure how I did it, but I cannot open my custom recovery image. Happened a couple weeks after I flashed a new image. When I tried to apply an update.zip, the image froze at the 'opening update package' stage. I tried multiple roms and wipes to fix the problem, but none worked.
I've flashed multiple images through the terminal, and cannot open any. I've tried using flashrec again, but command line error always pops up. The error in fastboot when trying to load the image is as follows "Wrong or no image!"
This error reoccurs several times as the image recovery is attemped to be retrieved several times.
My rom is Darchdroid 262, and works 100%.
chachi said:
If you can get it to fastboot ok and open the conversation, there must be something that can be done.
According to the definitive fastboot docs (http://android-dls.com/wiki/index.php?title=Fastboot) there might be a few options to try ...
Click to expand...
Click to collapse
I was having a play with those commands yesterday to see if it was possible to restore to a ROM through fastboot but had no luck unfortunately.
chachi said:
If you can get it to fastboot ok and open the conversation, there must be something that can be done.
According to the definitive fastboot docs there might be a few options to try ...
HTML:
<pre>usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline</pre>
Perhaps the -w to clear those areas might do it ...
Alternatively, I _believe_ you could flash the 1.62 recovery image to the phone in fastboot and then wipe from in there, or flash an 'update.zip' style rom from in here as well ...
Good luck, someone more knowledgeable than I may have other ideas ...
Click to expand...
Click to collapse
tried the fastboot -w and... not allow. I will try with the gold card.
Yeah, i'll try the 1.62, but the ADB don't find my device.
Try this,...
Go into fastboot on your phone.
Open CMD and type the following, obviously you will have to change slightly depending on where you extracted the sdk to.
cd c:\sdk\tools
fastboot oem rebootRUU
Then try running one of the 1.5 RUU .exe files on your pc/lappy.
ddotpatel said:
Try this,...
Go into fastboot on your phone.
Open CMD and type the following, obviously you will have to change slightly depending on where you extracted the sdk to.
cd c:\sdk\tools
fastboot oem rebootRUU
Then try running one of the 1.5 RUU .exe files on your pc/lappy.
Click to expand...
Click to collapse
i tried running one of the southeast asia RUU, the 2.73.728.5 file yesterday, and... nothing show up. Sayin' ive got to use the correct one.
The thing i thinked about is to rewrite the checksum in the update (the taiwanese 1.5 to 2.1 the one i've tried to update), verifying if its cupcake (in the fact that the update stopped in the middle), so if delete the verification code, it will continue the installation, and hopefuly, boot correctly.
-
update: ok trying to update again, then he says:
Error in checkspace (Status 256)
run_program PACKAGE:checkspace -f /data 26214400 "ro.build.fingerprint=chunghwa/htc_hero/hero/hero:1.5/CUPCAKE" FOTAERRORMESSAGES
Instalation aborted.
Click to expand...
Click to collapse
OK,... Now this,...
cd c:\sdk\tools
fastboot oem rebootRUU
fastboot erase cache
then try running the RUU again....... ?
Customer ID error... can't it erase the previous update?
it hasn't the original taiwanese RUU available?
the 2.73.751.13 file?
Customer ID Error?.... Ahaaaa,..... We might be on to something. Try with a goldcard now.
Use an old RUU with 1.5, not the new 2.1 ROM.
If you need to know how to make a goldcard follow BTDAGs guide linked in my signature.
ddotpatel said:
Customer ID Error?.... Ahaaaa,..... We might be on to something. Try with a goldcard now.
Use an old RUU with 1.5, not the new 2.1 ROM.
If you need to know how to make a goldcard follow BTDAGs guide linked in my signature.
Click to expand...
Click to collapse
This is beginning to sound like a happy ending is more than a remote possibility now
chachi said:
This is beginning to sound like a happy ending is more than a remote possibility now
Click to expand...
Click to collapse
Don't speak too soon, we might not be on to a winner just yet,.... Fingers crossed.
Just wanted to give everyone a heads up so no one makes the mistake i did. If you get into a postition where your bootlooping and no matter how much you wipe, flash, nand, whatever. And you still get htc bootloop. DO NOT flash any of the PG86IMG that are derived from the RUU(not saying there is anything wrong with those files). By doing that you will remove the revolutionary fastboot drivers from your hboot. Which in turn will lead to you not being able to fix the problem since fastboot will no longer work to run commands from your pc. So to make a long story short if you run into this problem just take the time to install SDK and use fastboot to flash and wipe the partitions(specifically the boot partition). Hope this helps someone.
Thanks for the tip bro
Sent from my 3VO
I figure id put it out there so we dont get anymore bricks. I know everyone says there not bricked unless you cant power into bootloader. But i have tried everything that i know of. Unless there is a way to remount and format the boot partition and flash just using adb instead of fastboot since adb works in recovery. who knows i bought a new one last night im still gonna play around and try to find a fix but i been without a phone for two days lol.
Just for the record I'm sure you've tried these:
http://android-dls.com/wiki/index.php?title=Fastboot
wiki said:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
Click to expand...
Click to collapse
an example of how to use it for the installation of revolutionary: (albeit in virtual box)
http://forum.xda-developers.com/showthread.php?p=16267669#post16267669
example said:
Next let's try fast boot.
With the phone, check the status of fastboot, in Settings>power>fastboot check marked.
Power off, remove battery, reboot while holding volume down key.
You'll see in red, "Fastboot Usb"
The VirtualBox usb icon should now show "Htc....[0100]".
Check mark it.
In terminal type "Fastboot devices (cr)".
You should get the serial number again.
Experiment until it's consistent.
Click to expand...
Click to collapse
Good luck
Yea tried all that. There is no working fastboot now that the hboot was flashed. I can only get the adb to connect while in recovery. If i try to run revolutionary from recovery it says sbin/sh bootloader not supported. And if i am in the bootloader or fastboot usb it just says waiting for device. I can however get revolutionary to start if i flash a custom ROM and try to reboot but it bootloops before the exploit can finish. Oh yeah even if the phone is off revolutionary will tell me device not supported.
Sent from my PG86100 using XDA App
IIRC revolutionary only works on certain hboot versions. You need to down grade if you're s-off. Actually google xda 3d hboot down grade.
Luck
willy900wonka said:
IIRC revolutionary only works on certain hboot versions. You need to down grade if you're s-off. Actually google xda 3d hboot down grade.
Luck
Click to expand...
Click to collapse
My phone has hboot 1.4 already
Sent from my PG86100 using XDA App
I'm pondering options with the vzw z2 tablet (sgp561) and before I start playing with this fire, I am curious what it would take to hard brick this so I know what NOT to try.
Any thoughts?
In theory as long as fastboot works it should be pretty tough to brick. I don't really know how fastboot works on Sony devices I have mostly Samsung devices but I assume download mode work largely the same as fastboot. I have brought back Samsung devices from being very near full hard brick. That said they were old and had unlocked bootloaders. I am not sure how relevant my two cents is but that is what I have. On another note I also have the 561 and am more than happy to help in any way I can. I really want some CM12 on this thing since VZW probably won't give it to us until everyone else has had it for 6 months.
Maxim512 said:
In theory as long as fastboot works it should be pretty tough to brick. I don't really know how fastboot works on Sony devices I have mostly Samsung devices but I assume download mode work largely the same as fastboot. I have brought back Samsung devices from being very near full hard brick. That said they were old and had unlocked bootloaders. I am not sure how relevant my two cents is but that is what I have. On another note I also have the 561 and am more than happy to help in any way I can. I really want some CM12 on this thing since VZW probably won't give it to us until everyone else has had it for 6 months.
Click to expand...
Click to collapse
Well, I can throw a couple of "kopeka's" (cents) in as well.
Fastboot is a life savior. Bar none. With it, you can wipe partitions and flash new partition images. Now this is taken that the fastboot capabilities in the given bootloader are "full" and not neutered in some way. Yes, it could possibly be so.
The only way I know, where you can perma-brick the device, is by flashing things on incorrect partition formats, or flashing a bootloader not meant for the device.
Incorrect custom recoveries are notorious for this, as they flash incorrect partition info. (been there, did that).
Also, nand memory can fail after some flashings. It happens. No rhyme or reason to it, it just does. Generally it gets corrupt to the point wipes and formats don't clean it.
Moscow Desire said:
Well, I can throw a couple of "kopeka's" (cents) in as well.
Fastboot is a life savior. Bar none. With it, you can wipe partitions and flash new partition images. Now this is taken that the fastboot capabilities in the given bootloader are "full" and not neutered in some way. Yes, it could possibly be so.
The only way I know, where you can perma-brick the device, is by flashing things on incorrect partition formats, or flashing a bootloader not meant for the device.
Incorrect custom recoveries are notorious for this, as they flash incorrect partition info. (been there, did that).
Also, nand memory can fail after some flashings. It happens. No rhyme or reason to it, it just does. Generally it gets corrupt to the point wipes and formats don't clean it.
Click to expand...
Click to collapse
In random readings, I've seen that "Unlock bootloader allowed=no" on some devices blocks fastboot. I can boot into fastboot mode, but I haven't tried flashing anything since I am not experienced in fastboot flashing. I think the easy test would be to read a partition in fastboot, then write it back. Do you know the commands to do so?
da_reeseboy said:
In random readings, I've seen that "Unlock bootloader allowed=no" on some devices blocks fastboot. I can boot into fastboot mode, but I haven't tried flashing anything since I am not experienced in fastboot flashing. I think the easy test would be to read a partition in fastboot, then write it back. Do you know the commands to do so?
Click to expand...
Click to collapse
You are correct. Some variants (Verizon for example), you can't unlock the bootloader. No unlock, no "full" fastboot or fastboot at all.
Although my original bootlocker was "unlockable" due to it turning out to be a "Demo" unit, I managed to flash an RU ftf, and got the unlocked bootloader. But it seems "some" carrier models don't allow for this. (as a sidenote, I've just reflashed my DRM keys back today, and now on a stock locked .167 build again. Just wanted to try it and see if it worked.)
Here's a list of useful commands (thanks to AndroidForums), but you can certainly find a ton by Google-it.
Code:
fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
A very useful thing to use, is for example;
fastboot boot boot.img
or
fastboot boot recovery.img
This is useful as it doesn't actually "write" the image to the device, but rather boots it in memory.
Usually how we test things such as new custom recoveries, boot.images and such.
Moscow Desire said:
You are correct. Some variants (Verizon for example), you can't unlock the bootloader. No unlock, no "full" fastboot or fastboot at all.
Although my original bootlocker was "unlockable" due to it turning out to be a "Demo" unit, I managed to flash an RU ftf, and got the unlocked bootloader. But it seems "some" carrier models don't allow for this. (as a sidenote, I've just reflashed my DRM keys back today, and now on a stock locked .167 build again. Just wanted to try it and see if it worked.)
Here's a list of useful commands (thanks to AndroidForums), but you can certainly find a ton by Google-it.
Code:
fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
A very useful thing to use, is for example;
fastboot boot boot.img
or
fastboot boot recovery.img
This is useful as it doesn't actually "write" the image to the device, but rather boots it in memory.
Usually how we test things such as new custom recoveries, boot.images and such.
Click to expand...
Click to collapse
Well I was going to give it a shot but I turned my tablet off to reboot without making any changes to it and now it won't turn back on. I haven't had time to RMA it yet. It did this before but it just started working again for no reason. It is probably a good thing since it sounds like I probably would have bricked it trying anyway.
Maxim512 said:
Well I was going to give it a shot but I turned my tablet off to reboot without making any changes to it and now it won't turn back on. I haven't had time to RMA it yet. It did this before but it just started working again for no reason. It is probably a good thing since it sounds like I probably would have bricked it trying anyway.
Click to expand...
Click to collapse
Wow, talk about "timing". Luckily you didn't make any changes. Had a similar issue with mine last night (coming out of fastboot coincidently).
Did a fastboot boot to TWRP, and when it went to reboot, I had to mess with the Vol + and - nd PWR combinations a few times before it would boot.
Do not play with verizon z2
I work with custom roms and such... I also have a Sony Z2 late tab... I built a rom for this device.... Never got to test it. Got two on it with no issues. And this is a pain as well due to anytime you use twrp you must reflash twrp or your in for a world of hurt. Well during my process twrp froze while wiping the system... I could get to fastboot but any command I tried to run It told me that it was locked and I couldn't use the command as I didn't have the rights. So long story short I wouldn't play with it till someone gets a unlock for it
Hi,
I have unlocked bootloader, installed TWRP recovery, flashed image "AospExtended" and started the device w/o issues.
Then I enabled device encryption, entered the password and the device started to reboot.
However it did not reach the phase where the password must be entered.
Instead, it ends up in a boot loop where the display shows "Kindle" and then reboots.
I can boot into both fastboot and recovery.
But even after deleting everything in TWRP and installing "AospExtended" image again, the boot loop is still there.
How can I fix this?
c.monty said:
Hi,
I have unlocked bootloader, installed TWRP recovery, flashed image "AospExtended" and started the device w/o issues.
Then I enabled device encryption, entered the password and the device started to reboot.
However it did not reach the phase where the password must be entered.
Instead, it ends up in a boot loop where the display shows "Kindle" and then reboots.
I can boot into both fastboot and recovery.
But even after deleting everything in TWRP and installing "AospExtended" image again, the boot loop is still there.
How can I fix this?
Click to expand...
Click to collapse
Yeah, encryption is not supported. You will need to format (vs. simply wipe) the system and/or data partitions. There was a recent discussion that addresses the commands needed. I will try to scare up a link and add to this post (check for updates).
Edit: This post should supply what you need; be sure to whap the 'thanks' button for @draxie if it solves your problem.
I boot into recovery, but then there's an issue with adb shell:
Code:
[email protected]:~/Hardware/Amazon/thor$ adb shell su -c "make_ext4fs /dev/block/mmcblk0p23"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Could I format this partition in fastboot, too?
Or in TWRP?
In recovery I tried to fix the bootloop issue by deleting/formating any partition.
Then, when I plugin the device to USB, I can only transfer data via file manager, means adb is not working.
Any file can be copied over to device (using file manager) and installed in TWRP.
A fool with a tool...
c.monty said:
Code:
error: device unauthorized.
Click to expand...
Click to collapse
Right... if you bothered checking that thread
for *all* the relevant messages, you would've
realized that the person with the encryption
problem had rolled back to Lineage 13; so, adb
with TWRP was not an issue for them...
Luckily, for you, that's not actually necessary.
c.monty said:
Could I format this partition in fastboot, too?
Click to expand...
Click to collapse
Probably not, although you could try
Code:
fastboot -i 0x1949 erase userdata
and hope that AEX does the right thing
and formats the partition as required.
c.monty said:
Or in TWRP?
Click to expand...
Click to collapse
Yes, of course, you can, but I'd prefer
that you tried the fastboot method first
and report back if that worked (since
that's simpler and would be helpful
for others stuck in the same place).
Code:
[email protected]:~$ fastboot -i 0x1949 erase userdata
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 0.085s]
finished. total time: 0.085s
[email protected]:~$ fastboot reboot
rebooting...
finished. total time: 0.320s
Reboot is successfull.
THX
Hello guys...
So, without going too much into details of how I idiotically f-ed up pretty much everything... I just want to say that I've already lost about 12 hours reading through the forum trying to solve the problem and to understand how everything works, and by what I understood... I bricked the phone?
Firstly, I managed to unlock the bootloader with the HCU Client (Phone unlocked, FRP unlocked). At some points I've managed to boot into TWRP's, but I flashed them without understanding that I should have installed the recommended ones by the guys on this forum instead of the official one, with which I wiped System and Data partition.
I've tried hard but never managed to boot any of the Custom ROMs available, especially the LineageOS 16 which I wanted but later on, through a specific TWRP which gave an error information that it's meant for Hisilicon, and not for Kirin SoC...
I also had no idea when I was booting into recovery, and when into erecovery, because I flashed TWRP over both of them... I have really no idea what was the last thing to happen, but now it seems as if I can't boot into eRecovery anymore, and whatever I try flashing to the recovery_ramdisk over Fastboot, I just always get the same error when trying to boot into recovery
Error! Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Now I'm also having an issue because my battery has drained and it doesn't seem to turn on without it being connected to the charger or a PC.
Is there anything that I can do to make it work with any Custom ROM?
returnedinformation said:
I've managed to boot into TWRP's, but I flashed them without understanding that I should have installed the recommended ones by the guys on this forum instead of the official one, with which I wiped System and Data partition.
Click to expand...
Click to collapse
This is the result of some people posting nonsense here.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
This is the result of some people posting nonsense here.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
> fastboot oem get-build-number
(bootloader) :ANE-LX1 8.0.0.126(C432)
> fastboot oem get-product-model
(bootloader) ANE-LX1
> fastboot getvar vendorcountry
vendorcountry: hw/eu
> fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
-Alf- said:
This is the result of some people posting nonsense here.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone. TWRP that is recommended in the "p20 lite basics" thread on XDA.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Totesnochill said:
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Click to expand...
Click to collapse
As I said before
-Alf- said:
some people posting nonsense here.
Click to expand...
Click to collapse
Totesnochill said:
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone. TWRP that is recommended in the "p20 lite basics" thread on XDA.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Click to expand...
Click to collapse
Sorry, but I'm already stuck at step 3:
PS C:\adb> fastboot boot twrp.img
Sending 'boot.img' (15652 KB) OKAY [ 0.411s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
returnedinformation said:
Sorry, but I'm already stuck at step 3:
PS C:\adb> fastboot boot twrp.img
Sending 'boot.img' (15652 KB) OKAY [ 0.411s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
I see. Some phones have this issue. where bootloader will not allow the "boot" command. Can be for a number of reasons:
1. Bootloader isnt "fully" unlocked, please check with the unlocking guide/service provider (if unlock was a paid service)
2. Bootloader is in "retail" mode, not a "service" mode. Some manufacturers do not intend for bootloader to be unlocked, and ship the devices with a restricted "retail" version that blocks certain commands.
also, why is your fastboot sending the "boot.img" while the command had " twrp img" as a payload?
I take it the bootloader still lets you use the "flash" command? If true, flash TWRP temporarily by "fastboot flash boot twrp.img", restart teh phone using the recovery menu keycombo
returnedinformation said:
> fastboot oem get-build-number
(bootloader) :ANE-LX1 8.0.0.126(C432)
> fastboot oem get-product-model
(bootloader) ANE-LX1
> fastboot getvar vendorcountry
vendorcountry: hw/eu
> fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
Click to expand...
Click to collapse
you've mixed apples and oranges nicely .
Try this way out, using HuRupdater
Guide
Downloand TWRP
Here
Totesnochill said:
Some phones have this issue. where bootloader will not allow the "boot" command. Can be for a number of reasons
Click to expand...
Click to collapse
No, there is only one reason - on Huawei devices we do not have a "boot" partition since Android 7.
-Alf- said:
you've mixed apples and oranges nicely .
Try this way out, using HuRupdater
Guide
Downloand TWRP
Here
Click to expand...
Click to collapse
Thank you, I've put them in blender and set it to "lightspeed" mode
I'm sorry, but flashing that TWRP gives me the exact error I've been getting before when trying to boot into Recovery... the fact that the phone can't charge also gives some headache to actually even try to boot into the recovery. I just can't get into.
Edit: The furthest I can get to is that recovery error message.
hi there..was reading about your problem..i'm not sure if the same rules apply to all or most phones with regards to flashing twrp or using fastboot..i'm assuming that they do.
So, are you able to boot into fastboot and/or recovery?
if no to recovery, i guess it may be the wrong twrp, i hope you can at least boot into fastboot without any issues.
Personally i had a xiaomi poco f2 pro 6/128 and then i bought another same model phone but 8/256 from a fellow who almost bricked his phone..it was just blinking, when i restarted the phone, it went straight into blinking whenever i tried to boot into recovery, and it wouldnt boot into system anyway cos there was nothing there. so i figured it was stuck in recovery loop.
i was fortunate that i was able to hook up to it using my pc...then using command prompt, i was able to switch to fastboot mode..then i tried downloading and flashing different twrps, over 10 different twrps, and finally one worked..then it was smooth sailing from then on..and presto, that became my daily use phone.
returnedinformation said:
Thank you, I've put them in blender and set it to "lightspeed" mode
I'm sorry, but flashing that TWRP gives me the exact error I've been getting before when trying to boot into Recovery... the fact that the phone can't charge also gives some headache to actually even try to boot into the recovery. I just can't get into.
Edit: The furthest I can get to is that recovery error message.
Click to expand...
Click to collapse
Can you boot into eRecovery (into TWRP installee over eRecovery)? If so, try to flash eRecovery_ramdisk.img in TWRP,
download Here for EMUI 9.1
or Here for 8.0 (I'm not sure what is your current version).
In eRecovery mode you can charge the phone ( charging should also work in TWRP which is installed instead of eRecovery).
flashgordon65 said:
hi there..was reading about your problem..i'm not sure if the same rules apply to all or most phones with regards to flashing twrp or using fastboot..i'm assuming that they do.
So, are you able to boot into fastboot and/or recovery?
if no to recovery, i guess it may be the wrong twrp, i hope you can at least boot into fastboot without any issues.
Click to expand...
Click to collapse
-Alf- said:
Can you boot into eRecovery (into TWRP installee over eRecovery)? If so, try to flash eRecovery_ramdisk.img in TWRP,
download Here for EMUI 9.1
or Here for 8.0 (I'm not sure what is your current version).
In eRecovery mode you can charge the phone ( charging should also work in TWRP which is installed instead of eRecovery).
Click to expand...
Click to collapse
I can boot to the Fastboot, but unfortunately I can't boot to either recovery or erecovery... When trying to boot to the recovery by holding the power+volume up button until I see the "Your device has been unlocked" warning message + 2 seconds (which is when I see the recovery error message), or when trying to boot while plugged into USB also holding the power+volume up button just leaves me at "Your device is booting now...." forever
returnedinformation said:
I can boot to the Fastboot, but unfortunately I can't boot to either recovery or erecovery... When trying to boot to the recovery by holding the power+volume up button until I see the "Your device has been unlocked" warning message + 2 seconds (which is when I see the recovery error message), or when trying to boot while plugged into USB also holding the power+volume up button just leaves me at "Your device is booting now...." forever
Click to expand...
Click to collapse
doesn't look good bro, try the following :
in fastboot mode run commands
fastboot erase user data
fastboot reboot
-Alf- said:
doesn't look good bro, try the following :
in fastboot mode run commands
fastboot erase user data
fastboot reboot
Click to expand...
Click to collapse
PS C:\adb> fastboot erase user data
Erasing 'user' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
returnedinformation said:
PS C:\adb> fastboot erase user data
Erasing 'user' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
Sorry!
fastboot erase userdata
PS C:\adb> fastboot erase userdata
Erasing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.215s]
Finished. Total time: 0.236s
PS C:\adb> fastboot reboot
Rebooting OKAY [ 0.024s]
Finished. Total time: 0.024s
Okay, what can I do now? I've tried flashing twrp right after that but solely rebooting get's me stuck at "Your device is booting now...", and trying to boot to recovery gives me the same error again
returnedinformation said:
PS C:\adb> fastboot erase userdata
Erasing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.215s]
Finished. Total time: 0.236s
PS C:\adb> fastboot reboot
Rebooting OKAY [ 0.024s]
Finished. Total time: 0.024s
Okay, what can I do now? I've tried flashing twrp right after that but solely rebooting get's me stuck at "Your device is booting now...", and trying to boot to recovery gives me the same error again
Click to expand...
Click to collapse
Download stock Recovery Oreo
Link
Flash it in fastboot
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-ANE-8.0.img
- fastboot reboot
Then try to boot into Recovery.
What exactly did you do after unlocking your phone? Did you upgrade back to A9? If so, then flash recovery_ramdisk A9
Download here
-Alf- said:
Download stock Recovery Oreo
Link
Flash it in fastboot
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-ANE-8.0.img
- fastboot reboot
Then try to boot into Recovery.
What exactly did you do after unlocking your phone? Did you upgrade back to A9? If so, then flash recovery_ramdisk A9
Download here
Click to expand...
Click to collapse
I've tried both, they give me the same error.
After I flash the recovery I can't really reboot straight into recovery because of the issue with the battery... somehow I gotta hold the Volume UP key, while catching exact moment when I can unplug USB after the low battery status page passes, and before Huawei logo appears...
After unlocking the phone I flashed TWRP over either recovery or erecovery (idk anymore)... then I probably installed Pixel Experience 13 ROM (https://github.com/ponces/treble_build_pe/releases)
And after that... I tried too many things I can't even remember anymore.
returnedinformation said:
then I probably installed Pixel Experience 13 ROM
Click to expand...
Click to collapse
Under EMUI 8 ??? Which TWRP?