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.
Ok so
Rooted
S-off
hboot 1.12.2222
was running Mean-rom 4.4
Then tried to install the new apk fix for ringtones
http://forum.xda-developers.com/showthread.php?t=1900629
Phone rebooted then then continues to be stuck in boot loop.
What I have tried:
Factory reset in bootloader
clear storage in bootloader
reinstall TWRP to get in recovery as if I choose recover in bootloader it just boot loops.
Tried to install the RUU but it can not connect during boot loops and errors out.
Any ideas?
Thanks in advance
Try fastboot wipe recovery then fastboot flash recovery recovery.img, if recovery loops back to bootloader then it's corrupt. Make sure you flash the latest twrp
om4 said:
Try fastboot wipe recovery then fastboot flash recovery recovery.img, if recovery loops back to bootloader then it's corrupt. Make sure you flash the latest twrp
Click to expand...
Click to collapse
All I see in fastboot option on bootloader is
bootloader
reboot
reboot bootloader
powerdown
am I missing something?
Those are fastboot commands, you use the terminal
fastboot wipe recovery
fastboot flash recovery recovery.img
You should be able to boot into recovery afterwards
What terminal? I'm a bit lost here
Do you have adb tools or Android SDK?
C:\android-sdk-windows
Open cmd prompt by opening SDK folder and then hold shift and right click, it will say open cmd prompt or something similar I don't recall if adb is in separate folder but I don't think so. From there you can plug in the phone in fastboot and type fastboot devices, it will tell you if you are connected or not. Download twrp and place it in the same folder. Then you can use the commands I listed earlier
om4 said:
Open cmd prompt by opening SDK folder and then hold shift and right click, it will say open cmd prompt or something similar I don't recall if adb is in separate folder but I don't think so. From there you can plug in the phone in fastboot and type fastboot devices, it will tell you if you are connected or not. Download twrp and place it in the same folder. Then you can use the commands I listed earlier
Click to expand...
Click to collapse
Get an error see attached
Now that I am in fasboot usb on the bootloader the RUU can connect to phone via USB.
If I just flashed that and started all over would that work and do I need to unroot and relock before doing the RUU?
Still not having any luck on terminal so far.
Sorry I was busy arguing with gf, it seems you aren't where you need to be if fastboot isn't recognized, I haven't had access to my own pc in quite a while so I'm having trouble remembering if there is another directory
om4 said:
Sorry I was busy arguing with gf, it seems you aren't where you need to be if fastboot isn't recognized, I haven't had access to my own pc in quite a while so I'm having trouble remembering if there is another directory
Click to expand...
Click to collapse
got fastboot working but get this with your first command
That's because I haven't used wipe in fastboot in quite a while, I'm sure I'm just confused on wipe and erase but you shouldn't need it, the first command should be fastboot erase recovery but like I said you shouldn't really have to, it's just like formatting before flashing the recovery, just fastboot flash recovery openrecovery.img or what ever the name is for the twrp file
Ran
C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7356 KB)...
OKAY [ 1.112s]
writing 'recovery'...
OKAY [ 1.796s]
finished. total time: 2.912s
Hit recovery and we we still are in boot loop
Relock bootloader and run ruu fastboot oem lock
copc said:
All I see in fastboot option on bootloader is
bootloader
reboot
reboot bootloader
powerdown
am I missing something?
Click to expand...
Click to collapse
select bootloader the recovery as soon you have recovery up wipe and reflash the rom
HTC EVO LTE
luisrod03 said:
select bootloader the recovery as soon you have recovery up wipe and reflash the rom
HTC EVO LTE
Click to expand...
Click to collapse
Thanks recovery just loops, could never get in.
Ok this is where I am at (see OP)
We tried flashing TWRP and original recovery via ADB
We tried running RUU
I'm still stuck in a boot loop....
I am having a similar problem stuck in bootloader. I relocked to go to the new firmware and now am stuck in the bootloader. I can access adb but can't access recovery. I am now relocked. Can I unlock again with a fastboot command?
If you unlocked manually, HTC sends the unlock code code just use fastboot to flash, if you used regawmod, just run it again. I don't know if regawmod will recognize the phone in boot loader though
I wanted to go back to stock so I went to the [rom][stock][twrp] http://forum.xda-developers.com/showthread.php?p=47851504#post47851504
page and did what was written only to get to step restore system and boot.
I am unable to get to fastboot and am stuck at the htc One splash screen.
I was on cleanroom 6.0 (I think) with twrp
I am using win8 and my work comp is a mac.
What do I need to do?
Thank you guys in advance
sixk said:
I wanted to go back to stock so I went to the [rom][stock][twrp] http://forum.xda-developers.com/showthread.php?p=47851504#post47851504
page and did what was written only to get to step restore system and boot.
I am unable to get to fastboot and am stuck at the htc One splash screen.
I was on cleanroom 6.0 (I think) with twrp
I am using win8 and my work comp is a mac.
What do I need to do?
Thank you guys in advance
Click to expand...
Click to collapse
did you backup your cleanrom install before trying the stock nandroid ?
Do you have Fastboot and ADB working on your windows 8 pc ?
Post the results from
fastboot getvar all
and I can help finding you the correct RUU
clsA said:
did you backup your cleanrom install before trying the stock nandroid ?
Do you have Fastboot and ADB working on your windows 8 pc ?
Post the results from
fastboot getvar all
and I can help finding you the correct RUU
Click to expand...
Click to collapse
I am using the minimal adb and fastboot to use adb
I think I made backup but not a stock backup
Also I am unable to get the fastboot getvar all on adb....
its just stuck on the white HTC one boot screen.
After coming from Samsung to htc everything seems to confusing...
and now that im on a note3 I forgot everything about htc... sad
sixk said:
I am using the minimal adb and fastboot to use adb
I think I made backup but not a stock backup
Also I am unable to get the fastboot getvar all on adb....
its just stuck on the white HTC one boot screen.
After coming from Samsung to htc everything seems to confusing...
and now that im on a note3 I forgot everything about htc... sad
Click to expand...
Click to collapse
Its no problem
just hold the power button down for 10 - 15 seconds to reboot the phone (be sure your in a well lite area or under a bright light)
hold volume down to reboot to recovery and see if you can restore your backup
To run fastboot, hold down the power button and volume down to enter the bootloader
it should say fastboot - now plugin to the PC it should change to fastboot usb
this is where you run the fastboot getvar all command
clsA said:
Its no problem
just hold the power button down for 10 - 15 seconds to reboot the phone (be sure your in a well lite area or under a bright light)
hold volume down to reboot to recovery and see if you can restore your backup
To run fastboot, hold down the power button and volume down to enter the bootloader
it should say fastboot - now plugin to the PC it should change to fastboot usb
this is where you run the fastboot getvar all command
Click to expand...
Click to collapse
Thanks clsA
you were really good with this stuff specially on the cleanrom forum
I will try this out tonight after work.
Thanks again!!!
sixk said:
Thanks clsA
you were really good with this stuff specially on the cleanrom forum
I will try this out tonight after work.
Thanks again!!!
Click to expand...
Click to collapse
just reply to this when you get back
and if your not s-off you should consider doing that first thing
here's the Revone thread if needed ->> http://forum.xda-developers.com/showthread.php?t=2314582
if your already s-off and you just need a RUU the files are here
->> http://www.htc1guru.com/downloads/ruu-file-downloads/
you need the one that's x.xx.502.x for an AT&T Phone
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 - is the newest for AT&T
Also Read here ->> http://forum.xda-developers.com/showthread.php?t=2358738
clsA said:
just reply to this when you get back
and if your not s-off you should consider doing that first thing
here's the Revone thread if needed ->> http://forum.xda-developers.com/showthread.php?t=2314582
if your already s-off and you just need a RUU the files are here
->> http://www.htc1guru.com/downloads/ruu-file-downloads/
you need the one that's x.xx.502.x for an AT&T Phone
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 - is the newest for AT&T
Also Read here ->> http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
I uh.... fastboot usb didn't work but I did a recovery in hboot and it returned to factory lol
So I am good!
:good:
Thanks a bunch clsA!
sixk said:
I uh.... fastboot usb didn't work but I did a recovery in hboot and it returned to factory lol
So I am good!
:good:
Thanks a bunch clsA!
Click to expand...
Click to collapse
that's no problem glad you got it working
clsA said:
just reply to this when you get back
and if your not s-off you should consider doing that first thing
here's the Revone thread if needed ->> http://forum.xda-developers.com/showthread.php?t=2314582
if your already s-off and you just need a RUU the files are here
->> http://www.htc1guru.com/downloads/ruu-file-downloads/
you need the one that's x.xx.502.x for an AT&T Phone
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 - is the newest for AT&T
Also Read here ->> http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
hey i also got stuck at the same spot as OP. So these RUU files are exe files. how do I work with them, doesn't my phone need to boot up first?
edit: i get this from getval all
"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"
matase said:
hey i also got stuck at the same spot as OP. So these RUU files are exe files. how do I work with them, doesn't my phone need to boot up first?
edit: i get this from getval all
Click to expand...
Click to collapse
the command is
fastboot getvar all
to run a RUU you simply lock the bootloaded from fastboot
fastboot oem lock
and run the ruu from your windows PC
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
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.