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.
Only boot looping to Google logo. Can't even get the correct drivers to show. Please help...
waiting4mynexus said:
Only boot looping to Google logo. Can't even get the correct drivers to show. Please help...
Click to expand...
Click to collapse
Put your device in fastboot mode.
Then >
fastboot format cache
fastboot format userdata
(Note that the second command will wipe your SDCard).
Then fastboot reboot
What if I'm getting a no devices from adb
waiting4mynexus said:
What if I'm getting a no devices from adb
Click to expand...
Click to collapse
If your device is in bootloader, ADB does not work. Correct command is "fastboot devices" (without quotation marks).
i'm getting formatting is not supported for filesystem with type 'f2fs'
you can format it using TWRP... either flash twrp or just boot into twrp and then format the data partition.
thanks, I'm back and running on 5.1.1.
used: https://twrp.me/
flashed back to stock using the following:
http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
sure thing
HI all, looking for some help. I recently became the owner of this Dell 7840. It was my sister's former boyfriend's device or something to that effect. It looks somebody did a hard reset and when I boot it up is asks for the google acct verification for acct previously used. This is information that she does not have and is not willing to attempt to get. I tried all the tricks online to bypass to no avail. So I assume its bricked.
Having read through most of the forums on this device, I figured I would several posted suggestions to try and unbrick the device to fix it but have not been able to get anywhere. (Ref How-To: Unbrick Dell Venue 8 7840 by wirebook) I have no way of know if USB debugging or developer settings were enabled but I suppose not.
I can get into Fastboot mode which list the following:
Prod name: BB, Variant - Venue 8 7840, HW version -unknown, Bootloader version - unknown, IFWI version - 0004.FD1F
S/N - 5B700JQA01, Signing - unknown, Secure Boot - unknown, Device State - Locked
The in Green - Fast boot CMD waiting
I installed Drivers, intel flash tool, SDK tools, ADB fastboot - Shows up devices as an Intel Android Device, with ADB interface
It shows up in the Flash tool and I've tried flashing 1-502_droidboot_and_firmware, but it times out everytime at 40 tries.
When I go into recovery mode:
it says Android system recovery, Venue 8 7840-user 5.1 LMY47I BBX803A173600DEL release keys
other than the option to wipe data/factory reset and wipe cache partition - (which I have tried) - the only option is apply update from ADB.
When I run the cwm tether launcher through IntelAndroid-FBRL-07-24-2015 I get:
'Device Status ADB Online', 'Device into 5B700JQA01 sideload'
Try to run T4 - get error 'closed', 'waiting for device' - Which is odd because when I tried it yesterday it said something like this:
'Using Trigger 4
target reported max download size of 536870912 bytes
sending '/tmp/recovery.zip' (7154 KB)...
OKAY [ 0.284s]
writing '/tmp/recovery.zip'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.318s
target reported max download size of 536870912 bytes
sending '/tmp/recovery.launcher' (704 KB)...
OKAY [ 0.061s]
writing '/tmp/recovery.launcher'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.095s
...
FAILED (remote: command not allowed in this device state)
finished. total time: 0.035s
target reported max download size of 536870912 bytes
sending '/system/bin/logcat' (349 KB)...
OKAY [ 0.055s]
writing '/system/bin/logcat'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.096s
...
FAILED (remote: command not allowed in this device state)
finished. total time: 0.035s'
Minimal ADB and Fastboot>adb devices finds the device
List of devices attached
adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
5B700JQA01 sideload
D:\SDK\Minimal ADB and Fastboot>fastboot devices
5B700JQA01 fastboot
D:\SDK\Minimal ADB and Fastboot>
All I am trying to do is get thing back up and running - I don't need root or anything else - I would like to be able to sell as a functional device - if not possible no matter, but I thought I would ask the experts here.
So I had been fighting with my device for the past two days. I erased the entire system from the device by accident on fastboot. Most everything I read said I was doomed. However, there were 2 topics that really helped me through get it back up and running. I dont remember the specific steps that I took to get it up and running - but I'll give you some thoughts. Remember that I lost my entire system.img - so there wasn't even an OS to get to. When you would boot it - it would simply load to the circle dell logo and sit there.
Here are the topics I found the most useful -
https://forum.xda-developers.com/dell-venue/general/7840-stuck-bootloop-bricked-t3178937
https://forum.xda-developers.com/dell-venue/general/7840-stuck-bootloop-bricked-t3178937
First, I was about to get into Fastboot - but there was no stock recovery or cwm. I started by loading up the Intel flash tool. I initially flashed the developer DDO_BB.xml which unlocked things and allowed me to start really getting to work. I then flashed a stock recovery.img through fastboot. This at least allowed me to get to a stock recovery. It also allowed me to get to ADB. I circled here for awhile.. but eventually was able to get back to fastboot to get the T4 tool working. From there, I was finally able to get CWM loaded. Once I got in there - I figured I was going to be golden. Still wasn't having any luck fastboot flashing the system.img... so I was able to transfer my system.img file over to an ext_4 sd card, then use the dd command to transfer it over to the device. Once i got success here, I was totally golden. Was able to wipe data, cache, etc.. and it finally booted.
So, this might not be the exact issues you are having - but it should give you confidence that recovery can happen. Again - those links helped me the most.. it was a lot of trial and error.. but I figured I was already in a bad place, so it couldn't get much worse.
MynticeLX said:
So I had been fighting with my device for the past two days. I erased the entire system from the device by accident on fastboot. Most everything I read said I was doomed. However, there were 2 topics that really helped me through get it back up and running. I dont remember the specific steps that I took to get it up and running - but I'll give you some thoughts. Remember that I lost my entire system.img - so there wasn't even an OS to get to. When you would boot it - it would simply load to the circle dell logo and sit there.
Here are the topics I found the most useful -
https://forum.xda-developers.com/dell-venue/general/7840-stuck-bootloop-bricked-t3178937
https://forum.xda-developers.com/dell-venue/general/7840-stuck-bootloop-bricked-t3178937
First, I was about to get into Fastboot - but there was no stock recovery or cwm. I started by loading up the Intel flash tool. I initially flashed the developer DDO_BB.xml which unlocked things and allowed me to start really getting to work. I then flashed a stock recovery.img through fastboot. This at least allowed me to get to a stock recovery. It also allowed me to get to ADB. I circled here for awhile.. but eventually was able to get back to fastboot to get the T4 tool working. From there, I was finally able to get CWM loaded. Once I got in there - I figured I was going to be golden. Still wasn't having any luck fastboot flashing the system.img... so I was able to transfer my system.img file over to an ext_4 sd card, then use the dd command to transfer it over to the device. Once i got success here, I was totally golden. Was able to wipe data, cache, etc.. and it finally booted.
So, this might not be the exact issues you are having - but it should give you confidence that recovery can happen. Again - those links helped me the most.. it was a lot of trial and error.. but I figured I was already in a bad place, so it couldn't get much worse.
Click to expand...
Click to collapse
Thanks for the links - It seems that all options are dependent on being able to change the device state from locked to unlocked. I have not been successful it this following recommendations using ADB or Fastboot options. Anyone have a good way to unlock it?
Once I flashed the DDO_BB through the Intel tool, it unlocks everything since it was released from Dell as the developer tools. My bootloader and recovery were both locked before flashing that. Afterwards, I was able to do whatever I needed.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
Also, make sure you are in the right mode to flash.. you need to hold volume up and power while connected to the tool and it should register on the tool even though the screen may be blank on the device.
MynticeLX said:
So I had been fighting with my device for the past two days. I erased the entire system from the device by accident on fastboot. Most everything I read said I was doomed. However, there were 2 topics that really helped me through get it back up and running. I dont remember the specific steps that I took to get it up and running - but I'll give you some thoughts. Remember that I lost my entire system.img - so there wasn't even an OS to get to. When you would boot it - it would simply load to the circle dell logo and sit there.
Here are the topics I found the most useful -
https://forum.xda-developers.com/dell-venue/general/7840-stuck-bootloop-bricked-t3178937
https://forum.xda-developers.com/dell-venue/general/7840-stuck-bootloop-bricked-t3178937
First, I was about to get into Fastboot - but there was no stock recovery or cwm. I started by loading up the Intel flash tool. I initially flashed the developer DDO_BB.xml which unlocked things and allowed me to start really getting to work. I then flashed a stock recovery.img through fastboot. This at least allowed me to get to a stock recovery. It also allowed me to get to ADB. I circled here for awhile.. but eventually was able to get back to fastboot to get the T4 tool working. From there, I was finally able to get CWM loaded. Once I got in there - I figured I was going to be golden. Still wasn't having any luck fastboot flashing the system.img... so I was able to transfer my system.img file over to an ext_4 sd card, then use the dd command to transfer it over to the device. Once i got success here, I was totally golden. Was able to wipe data, cache, etc.. and it finally booted.
So, this might not be the exact issues you are having - but it should give you confidence that recovery can happen. Again - those links helped me the most.. it was a lot of trial and error.. but I figured I was already in a bad place, so it couldn't get much worse.
Click to expand...
Click to collapse
MynticeLX said:
Once I flashed the DDO_BB through the Intel tool, it unlocks everything since it was released from Dell as the developer tools. My bootloader and recovery were both locked before flashing that. Afterwards, I was able to do whatever I needed.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
Also, make sure you are in the right mode to flash.. you need to hold volume up and power while connected to the tool and it should register on the tool even though the screen may be blank on the device.
Click to expand...
Click to collapse
Thanks again for the help - You were right - I was not in the correct mode - I apparently missed that at some point - So using that I was able flash the old droid boot (part1) from:
https://forum.xda-developers.com/dell-venue/general/7840-update-t3162385/page5
which worked successfully - Than I was able to use IntelAndroid-FBRL-07-24-2015 to get the cwm working.
I copied UPDATE-SuperSU-v2.46.zip and update.zip to my SD card
I followed steps 28-33 from:
https://forum.xda-developers.com/dell-venue/general/root-howto-dell-venue-8-7840-t3282532
Flashed both zip successfully. but when I went to reboot - the only option was to repair boot or something and when evrything rebooted - I was back to the FRP screen. I must be missing something to fix the boot image - maybe I need to use a different copy of the OS
Any thoughts?
Have you tried the boot.img and system.img from xBIGREDDx post on the second link that I referenced for you? I believe those were the main files I used. I wouldn't worry about rooting right now, just get your system back up then go back and root.
xBIGREDDx system and boot img files
http://forum.datadevelopement.com/sh...58&postcount=5
system.img: https://mega.co.nz/#!w9AjBCSI!YdQenT...SgiyULA1FVIA8A
boot.img: https://mega.co.nz/#!Fk4FUSza!1gY1Rj...VOCH-P2V5fVFPI
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
I would put the system image on a SD card.. then boot into cwm recovery to use the dd command in shell to transfer over the system.. then boot back into bootloader and fastboot the boot.img over to it.
MynticeLX said:
Have you tried the boot.img and system.img from xBIGREDDx post on the second link that I referenced for you? I believe those were the main files I used. I wouldn't worry about rooting right now, just get your system back up then go back and root.
xBIGREDDx system and boot img files
http://forum.datadevelopement.com/sh...58&postcount=5
system.img: https://mega.co.nz/#!w9AjBCSI!YdQenT...SgiyULA1FVIA8A
boot.img: https://mega.co.nz/#!Fk4FUSza!1gY1Rj...VOCH-P2V5fVFPI
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
I would put the system image on a SD card.. then boot into cwm recovery to use the dd command in shell to transfer over the system.. then boot back into bootloader and fastboot the boot.img over to it.
Click to expand...
Click to collapse
OK so I formatted an sd card in ext4 using Minitool partition wizard - got back into cwm recovery - unmounted system and mounted the external sd.
after several attempts trying to follow the instructions on:
https://forum.xda-developers.com/de...-8-7840-developer-files-posted-t3144232/page2
I was finally able to push the system.img to the sd card using adb but then I get to the next step and I get this response from ADB:
D:\SDK\Minimal ADB and Fastboot>dd if=/external_sd/system.img of=/dev/block/by-name/system
'dd' is not recognized as an internal or external command, operable program or batch file.
This is my first time using ADB so I'm not sure if I'm missing something though it seems i'm making some progress.
I noticed that you said to "use the dd command in shell to transfer over the system." I tried that as well - I typed 'shell' in cwm as indicated and entered the same command 'dd if=/external_sd/system.img of=/dev/block/by-name/system' - nothing happened.
Resazurin said:
OK so I formatted an sd card in ext4 using Minitool partition wizard - got back into cwm recovery - unmounted system and mounted the external sd.
after several attempts trying to follow the instructions on:
https://forum.xda-developers.com/de...-8-7840-developer-files-posted-t3144232/page2
I was finally able to push the system.img to the sd card using adb but then I get to the next step and I get this response from ADB:
D:\SDK\Minimal ADB and Fastboot>dd if=/external_sd/system.img of=/dev/block/by-name/system
'dd' is not recognized as an internal or external command, operable program or batch file.
This is my first time using ADB so I'm not sure if I'm missing something though it seems i'm making some progress.
I noticed that you said to "use the dd command in shell to transfer over the system." I tried that as well - I typed 'shell' in cwm as indicated and entered the same command 'dd if=/external_sd/system.img of=/dev/block/by-name/system' - nothing happened.
Click to expand...
Click to collapse
Sorry to make this super simplistic.. but want to make sure we are both starting from the same place. Get the device to launch into CWM. Once there, you'll need to move within the menu structure every couple mins to make sure that it doesn't exit out on you. You should be able to ADB from your computer at this point. Make sure you use adb devices to see your active device. Once you see it, and have the system.img on your external sd card - you should be able to run the command "adb shell". You should see the CMD window put you into a ">$ or >#" like screen. From there, you are specifically operating on the device - not on your computer to the device. This is where you can start to run the series of commands. I was not able to run the mount commands - so I just used the menu in CWM to make sure that they were mounted correctly. Before transferring the system - I would format it through CWM. Then, after all that is done, type in the dd command from the post referenced exactly. You won't really get any feedback from the cmd window or the device... as long as you DONT have the ability to type in the cmd window - it means it's transferring. It will finally say if it has successfully transferred or error'ed out. Hopefully a success. I did find out that through the process, I had to click in and through the CWM on the device to make sure that it stayed active and didn't kick me out into reboot.
Good luck. Sounds like you are getting close.
MynticeLX said:
Sorry to make this super simplistic.. but want to make sure we are both starting from the same place. Get the device to launch into CWM. Once there, you'll need to move within the menu structure every couple mins to make sure that it doesn't exit out on you. You should be able to ADB from your computer at this point. Make sure you use adb devices to see your active device. Once you see it, and have the system.img on your external sd card - you should be able to run the command "adb shell". You should see the CMD window put you into a ">$ or >#" like screen. From there, you are specifically operating on the device - not on your computer to the device. This is where you can start to run the series of commands. I was not able to run the mount commands - so I just used the menu in CWM to make sure that they were mounted correctly. Before transferring the system - I would format it through CWM. Then, after all that is done, type in the dd command from the post referenced exactly. You won't really get any feedback from the cmd window or the device... as long as you DONT have the ability to type in the cmd window - it means it's transferring. It will finally say if it has successfully transferred or error'ed out. Hopefully a success. I did find out that through the process, I had to click in and through the CWM on the device to make sure that it stayed active and didn't kick me out into reboot.
Good luck. Sounds like you are getting close.
Click to expand...
Click to collapse
Thanks to your clarification - I can report success - successful dd of system.img from external SD using ADB shell and after rebooting to fastboot, the successful fastboot push of root.img
Rebooted tablet and FRP was gone - logged in with my own google acct and all is well. Working tablet
Thank you so much for the help and your patience - really appreciate it and I learned a lot -
Update:
I didn't realize I was already rooted - Super SU was installed with the process above - I was able to flash the UPDATE.ZIP of 5.1 from xBIGREDDx link (https://forum.xda-developers.com/dell-venue/general/7840-update-t3162385/page2) through CWM. Works without issue - Still rooted after update. Thanks again
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.
Hey all,
I have a new z5c running 32.4.A.1.54 stock.
I flash TWRP (I have tried a few different versions) using Fastboot on Ubuntu20.04, it all runs fine no errors, and appears to flash as it should.
But the phone will not load TWRP, from the phone itself, I have tried a million different ways.
The only way it loads is by
fastboot boot twrp.img
But when I do this .. android will not then start .. hangs on Sony logo
I have to reflash the stock rom to get it to work again
If I run
fastboot reboot recovery
I get:
fastboot: usage: unknown reboot target recovery
even tho:
fastboot devices
correctly identifies the device
I would like to root and use custom rom, but have not yet been able to get past this TWRP hurdle
Has anyone experience of this, or any ideas?
You've flashed TWRP in a wrong way! Please search for help in my several ROM threads.
Well, thanks for your answer, really, I appreciate it
But I have flashed it again and again and followed your threads and other threads
I'm not a newbie, i have flashed TWRP and roms to a few phones, inc Z1C and a couple of Z3Cs
I have adb, and fastboot installed
Bootloader unlocked
USB debugging
Recommended stock
I have downloaded multiple .img files, including your 3.6.1 version
I run fastboot
and
fastboot flash recovery twrp.img
The phone will not reboot into TWRP, using buttons nor fastboot, only into android, unless I then run
fastboot boot twrp.img
Then TWRP runs, but when I then reboot, I just hit the SONY logo if I have not flashed a ROM or a bootloop if I have.
And from there will not return to TWRP at all.
What am I missing?
I'm very confused as everything you're talking about is working here and for other users flawlessly.
Really, I don't know what's wrong at your side.
Berni-0815 said:
I'm very confused as everything you're talking about is working here and for other users flawlessly.
Really, I don't know what's wrong at your side.
Click to expand...
Click to collapse
Yes, that makes 2 of us!
Ugh.
Did you try what I told you in this post?
With that, LineageOS 19.1 MUST boot up!
If not, I don't know further...
Berni-0815 said:
Did you try what I told you in this post?
With that, LineageOS 19.1 MUST boot up!
If not, I don't know further...
Click to expand...
Click to collapse
I did try that as recommended, thanks
I am flashtool-ing back to the stock again, after being again stuck on boot with TWRP inaccessible
I will give it one last go
Thanks, man
How do I buy you a coffee?
That's all really weird; since it works here since years.
From a fresh fully-functional stock install
Following this simple process exactly
Devices with only TWRP.IMG
If your device only has the IMG file, then execute the below command: fastboot flash recovery twrp.img
Now execute the below command to boot your device to the TWRP recovery. fastboot boot twrp.img
Once it boots to TWRP, you could then boot it to the OS, via the Reboot > System option in TWRP.
From here;
https://www.getdroidtips.com/flash-twrp-recovery-android/
After 3. it gets to SONY logo and hangs
Same every time
Obviously not a problem with your or any other custom ROM
The only way out from here is to Flashtool the stock again
Geez
I'm giving up on TWRP and custom ROM
I'll go for the rooted, debloated, degoogled stock as best as I can get it
Thanks v much for the support!
I've NEVER used the command
Code:
fastboot boot twrp.img
I've always flashed TWRP like this:
Shutting down device
Waiting some time
Pressing volume up and plugging usb cable
Enter this command in a terminal window:
Code:
fastboot flash recovery TWRP_3.6.1_9-0-recovery_suzuran_2022-03-09.img
After unplugging the usb cable and waiting some time I rebooted into TWRP by pressing power and volume down simultaneously.
That worked since years flawlessly!
Berni-0815 said:
I've NEVER used the command
Code:
fastboot boot twrp.img
I've always flashed TWRP like this:
Shutting down device
Waiting some time
Pressing volume up and plugging usb cable
Enter this command in a terminal window:
Code:
fastboot flash recovery TWRP_3.6.1_9-0-recovery_suzuran_2022-03-09.img
After unplugging the usb cable and waiting some time I rebooted into TWRP by pressing power and volume down simultaneously.
That worked since years flawlessly!
Click to expand...
Click to collapse
That command is the only way that twrp has loaded for me
Right .. deep breath ... one last go at this using yr suggestion,
thanks
Nope
Same again
All goes as it should
Power and volume down simultaneously
Boots into Android
adb reboot recovery
Also boots into android
If I was now to run
fastboot boot twrp.img
It would run TWRP the one time, but just hang on SONY logo when rebooted
Ho hum.
kaivalyam said:
Power and volume down simultaneously
Boots into Android
Click to expand...
Click to collapse
That SHOULD NOT happen if you've flashed TWRP in the only right way.
I'm sorry, but I don't believe that...
Berni-0815 said:
That SHOULD NOT happen if you've flashed TWRP in the only right way.
I'm sorry, but I don't believe that...
Click to expand...
Click to collapse
Well, its not a particularly complicated process
I have described exactly what I have done
I have done it multiple times
And that is what happens
As I said: I've never seen that and that's not reported very often by other users.
And if, then it has been an error in flashing.
Highly unlikely that you're devices so called FOTA partition is damaged so that the command
Code:
fastboot flash recovery <name of the recovery image>
fails.
Code:
fastboot flash boot <name of the boot image>
flashes the boot partition and that's not the same as the FOTA partition.
I have to believe you but somehow I can't.
I understand
fastboot flash recovery <name of the recovery image>
Doesn't fail exactly ... it runs fine .. no errors
Code:
~/Dev/Z5/twrp/3.6.1$ fastboot flash recovery TWRP_3.6.1_9-0-recovery_suzuran_2022-03-09.img
target reported max download size of 536870912 bytes
sending 'recovery' (22668 KB)...
OKAY [ 0.570s]
writing 'recovery'...
OKAY [ 0.395s]
finished. total time: 0.965s
But then the phone will only boot android
~~~
Unless
I run;
fastboot flash boot <name of the boot image>
Again, runs fine .. no errors
Code:
~/Dev/Z5/twrp/3.6.1$ fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.552s]
booting...
OKAY [ 0.561s]
finished. total time: 1.113s
This boots TWRP but then after that the phone hangs at boot and will neither start Android or TWRP
It is indeed very strange.
Look at your own code:
Code:
~/Dev/Z5/twrp/3.6.1$ fastboot boot twrp.img
downloading 'boot.img'...
From where is boot.img downloaded? And where is it stored internally?
Have you flashed system.img too?
There goes something terribly wrong at your side.
Thanks for your patience
Yes I'm sure you're right, probably user error, although I am having trouble seeing what that is exactly ...
So, using Ubuntu, I am in the directory that contains the twrp.img file (most times I have renamed it this)
Is that correct so far?
From there I run
fastboot flash recovery twrp.img
All good, as above, but TWRP does not load, ever, using buttons or adb, unless I then run
fastboot boot twrp.img
TWRP then runs
But the phone will not boot into anything from there
Yes, I thought that was a little odd ...
"downloading" : I assumed it meant it was transferring the file across, or accessing it, from my pc to the device
"'boot.img" : I assumed fastboot had changed the filename to what it needed it to be ...
Is the problem around this?
You can name the recovery image file as you like it to be named.
Have you disconnected the USB cable after flashing?
Have you waited some time before trying to boot anything?
If you can boot TWRP, you can fetch a LOG file at the "Advanced" menu. Please send me this LOG file via PM (it may contain personell data!).