Related
Hi all,
It seems that I have managed to brick my device. I am on 1.50 S-ON, and was trying to flash one of the ICS ROMs through the usual method (push the zip, reboot to bootloader, fastboot to the recovery.img) which I have used multiple times successfully in the past, but the phone ended up in a reboot loop. I did not apply any firmware changes (at least not voluntarily!), since the ROM (CleanROM was the first one I tried to flash) said that this was necessary. I tried flashing different ROMs (GB or ICS), and a Nandroid backup, but none seem to work. The only clue I have as to what is going on is that fastboot says that there is no image of PG86DIAG.[zip,nbh] and PG86IMG.[zip,nbh,tar,aes,enc]. This looks like a radio issue to me, but I don't want to do anything stupid (again!), so any input would be appreciated.
Thanks a lot!
I would recommend flashing this: http://dev-host.org/ru0ow8ps0i01/PG86IMG_2.17.651.5.zip
Its haus's 2.17 fw package and has everything in it. I flashed the new fw and a rom and had the same bootloop and nothing stopped it except returning to a stock system. After flashing this i flashed a new rom and everything worked as normal.
Rename the zip file PG86IMG.zip put on root of sdcard and reboot to bootloader. (Just in case anyone needs to know) This is a completely stock rom and fw so you will need to flash another rom with superuser in it for root apps.
Hope that helps...
If I'm reading it correctly you tried ics flash and it failed and now you wanna go back or flash to another working Rom right?....if so, unplug phone from comp, pull battery and reboot into bootloader (power +vol up), pick fastboot, connect to comp, use fastboot command to get into recovery and wipe and flash a working Rom....that's also assuming you already have a Rom on sdcard......if not then push a tom to card or in cwm you can mount USB storage and do drag and drop....I really hope that points you in right direction....let me know.
With hboot 1.5 s-on you have to do the fastboot command in order to get into recovery in order to do flashes...
Sent from my PG86100 using XDA
It booted!
Hey both,
I did somehow manage to flash a regular GB ROM. The weird thing is I was doing the exact same thing I was doing before (which is onefasttereopro's method), but for whatever reason it didn't work until now. The one thing that did in fact change is that I tried flashing Chad's kernel to see if any of the ICS ROMs would work, but I don't think that's it (it seems to have been overwritten, judging by /proc/version and the fact that USB works). Thank you very much both for your help, I am very glad that I have a working device again!
Ok... This is my 4th android phone.. And I love this phone... And only had it for a week.... and just now got it bricked.... here's what happen... Today I tried to flash a sense 4.1 rom, but im so new at this, and I'm half way done, and I went in a rush because I was nervous, and I accidentally press "install and keep data" and that was my mistake. I factory reset it b4 so I tried to flash it... So I thought it wouldn't be a problem. So I waited till the phone finish flashing. And when I rebooted the phone.... Nothing happened, just stuck on the white screen.... vibrating and etc... And I tried to restore all my data in clockworkmod recovery like I never even tried flashed it.. and it kept saying "won't mount sd card" and I tried to clear my cache/dalvik-cache, and like it still wont fix the issue. I even tried to restore wat I backup b4 I tried to flash it... and It was gone!!! Even my windows 8 laptop won't even detect my resound nor my sd card(unless its on a different android). But How can I fix my Rezound?!? plzzzz How can I fix this soft bricked issue? pllzzzzzzz help!!!
Im assuming you already have adb installed
Download this file
http://www.mediafire.com/download/oa2sjlvrecx0wdn/recovery-ra-vigor-3.16-gnm.img.zip
Extract the recovery img
Put it in the adb folder
Load into fastboot
Open up the terminal
Put "cd" then hit space
Drag and drop the adb folder into the terminal window then hit enter
Now use this command to flash that recovery "fastboot flash recovery recovery.img" (without the quotation marks)
Now go into recovery Find "format data system cache ect."
Go to format all to ext3 once that is done hit return
Flash your prefered rom from the flash menu and all that
Once you are done return to the main menu and go to "developer menu"
Then reboot to bootloader
Now go into your rom that you downloaded on your pc and find the rom now open it and get the boot.img
Copy the boot.img file to your adb folder
Open up terminal again and this time use the command "fastboot flash boot boot.img" in terminal its going to say sending then writing usually takes a couple of seconds
now just go to the reboot option and your rom should work
Now remember that since you are s on you need to get the boot.img file from EVERY rom you install and flash it thru the terminal in order to get your rom working
xkjonathanxk said:
Im assuming you already have adb installed
Download this file
http://www.mediafire.com/download/oa2sjlvrecx0wdn/recovery-ra-vigor-3.16-gnm.img.zip
Extract the recovery img
Put it in the adb folder
Load into fastboot
Open up the terminal
Put "cd" then hit space
Drag and drop the adb folder into the terminal window then hit enter
Now use this command to flash that recovery "fastboot flash recovery recovery.img" (without the quotation marks)
Now go into recovery Find "format data system cache ect."
Go to format all to ext3 once that is done hit return
Flash your prefered rom from the flash menu and all that
Once you are done return to the main menu and go to "developer menu"
Then reboot to bootloader
Now go into your rom that you downloaded on your pc and find the rom now open it and get the boot.img
Copy the boot.img file to your adb folder
Open up terminal again and this time use the command "fastboot flash boot boot.img" in terminal its going to say sending then writing usually takes a couple of seconds
now just go to the reboot option and your rom should work
Now remember that since you are s on you need to get the boot.img file from EVERY rom you install and flash it thru the terminal in order to get your rom working
Click to expand...
Click to collapse
If you are S-ON, you are likely not bricked, it's almost impossible to completely brick when you are S-ON.
Why do people keep telling occasional flashers that are S-ON to do this?!?!? It is the hard way, also don't use Amon Ra, is it outdated and known to cause issues with current ROMs, use TWRP or CWM recovery!!! Also, verify your ROM is specifically for the HTC Rezound, check the Developer threads here and make sure it is stable and widely used unless you really know what you are doing.
Although xkjonathanxk is on the right track, he is making more complicated than it needs to be...
- Download the first link in the first post of this thread and place it on the root of your SD card: [Tool] - 3/24 - CleanWIPE 1.0 - Wipe 5 or 10x before ROM install! - 1heffer Edition! (CleanWIPE formats all the necessary partitions for you, and prepares the phone for a new ROM)
- Download TWRP or CWM Rececovery (one of the first two links in post 1) and extract the recovery*.img and place it in the adb folder that contains fastboot.
- Download a tested and verified ROM of choice and place it on the root of your SD card
- Now, reboot into fastboot, remove battery and hold down Power and Vol Dn, once the menu comes up select Fastboot and press power, connect phone to PC
- In ADB enter the command "fastboot devices", if it shows a device continue, if not report back please
- Now enter the command "fastboot boot recovery.img" and TWRP (or CWM) should open on the device in a few seconds (replace recovery.img with whatever the name of the xxxx.img file is from TWRP or CWM archive)
- Install the CleanWIPE zip from above
- Install ROM zip image
- Reboot and enjoy the goodness
Remember to give the ROM some time to settle down on the first boot, and that the first boot can take a long time, like a painfully wrong "WTF did I do to ruin my device!" long time, but give it a solid 10 minutes before doing anything else.
@acejavelin
acejavelin said:
If you are S-ON, you are likely not bricked, it's almost impossible to completely brick when you are S-ON.
Why do people keep telling occasional flashers that are S-ON to do this?!?!? It is the hard way, also don't use Amon Ra, is it outdated and known to cause issues with current ROMs, use TWRP or CWM recovery!!! Also, verify your ROM is specifically for the HTC Rezound, check the Developer threads here and make sure it is stable and widely used unless you really know what you are doing.
Although xkjonathanxk is on the right track, he is making more complicated than it needs to be...
- Download the first link in the first post of this thread and place it on the root of your SD card: [Tool] - 3/24 - CleanWIPE 1.0 - Wipe 5 or 10x before ROM install! - 1heffer Edition! (CleanWIPE formats all the necessary partitions for you, and prepares the phone for a new ROM)
- Download TWRP or CWM Rececovery (one of the first two links in post 1) and extract the recovery*.img and place it in the adb folder that contains fastboot.
- Download a tested and verified ROM of choice and place it on the root of your SD card
- Now, reboot into fastboot, remove battery and hold down Power and Vol Dn, once the menu comes up select Fastboot and press power, connect phone to PC
- In ADB enter the command "fastboot devices", if it shows a device continue, if not report back please
- Now enter the command "fastboot boot recovery.img" and TWRP (or CWM) should open on the device in a few seconds (replace recovery.img with whatever the name of the xxxx.img file is from TWRP or CWM archive)
- Install the CleanWIPE zip from above
- Install ROM zip image
- Reboot and enjoy the goodness
Remember to give the ROM some time to settle down on the first boot, and that the first boot can take a long time, like a painfully wrong "WTF did I do to ruin my device!" long time, but give it a solid 10 minutes before doing anything else.
Click to expand...
Click to collapse
I really appreciate your help and everything. So i thank you. But Like i said im running windows 8, it wont detect my rezound or my sd card, the only time the pc is able to detect the sd card is when im able to mount my sd card to CWM. But it really wont detect it.... help me again
Multidex24 said:
I really appreciate your help and everything. So i thank you. But Like i said im running windows 8, it wont detect my rezound or my sd card, the only time the pc is able to detect the sd card is when im able to mount my sd card to CWM. But it really wont detect it.... help me again
Click to expand...
Click to collapse
Ubuntu Live CD... Windows not required.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Dont know how to work ubuntu.. help again
acejavelin said:
Ubuntu Live CD... Windows not required.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Click to expand...
Click to collapse
lol its the good thing i know how to make a dual os between win8 and ubuntu, but heres another problem, i dont even know how to work ubuntu...
i think my pc can detect the rezound. But idek how to work ubuntu, plzzzz help!!
Multidex24 said:
lol its the good thing i know how to make a dual os between win8 and ubuntu, but heres another problem, i dont even know how to work ubuntu...
i think my pc can detect the rezound. But idek how to work ubuntu, plzzzz help!!
Click to expand...
Click to collapse
For the things you need to do, its not much different than Windows. Download and install adb, copy images to same places, and the commands are pretty much the same. If you can dualboot you obviously have some knowledge of such things.
If this is all do difficult, just grab a thumb drive, put mini-adb, recovery.img, and your ROM on it and go to a buddies computer with Win7 for 20 minutes and get it done that way.
I know this seems like a huge, potentially fatal problem, but it is minor...
Another thought I had... Download TWRP, go into CWM recovery and copy the TWRP file and ROM to the sd card, and FLASH TWRP recovery ZIP with CWM recovery, reboot into recovery and you will then be on TWRP and you can use TWRP's HTC Dumlock to flash the ROM and the boot.img without a PC at all... In theory, it should work.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
I have the castor windy version 16gb SGP511. I was previously rooted but not unlocked. I unlocked the boot loader. Installed the twrp image on the pac man thread which i think was dual recovery cause Philz,Cwm came out, so I can install lollipop version of the rom. Made a backup of the stock rom. Followed this instructions - Install the Lollipop ROM + GApps+SuperSU using whatever Recovery you have.
- Turn off device completely.
- Press <Volume Up> and plug USB cable.
- LED should turn blue.
- Send command: "fastboot erase recovery"
- Send command for Castor_Windy: "fastboot flash recovery TWRP_Castor_Windy.img"
- Send command for Castor: "fastboot flash recovery TWRP_Castor.img"
- Unplug USB cable.
- Device will reboot.
- When LED turns pink press <Volume Up> and <Volume Down> several times.
- You should now see TWRP
I wasnt fast enough so stock rom booted. I used Adb reboot recovery to access recovery and did as the above mentioned. Wiped i tried to install the rom which failed. Rebooted back to system and got stuck in Sony boot up screen. I can access fastboot. Read though the forums I have to find a ftf or a system image file and use a flash tool. What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Kamaleon said:
What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Click to expand...
Click to collapse
Try this Xperia downloader tool. Should let you see which versions are which. If you want an easy root, then stay away from the KitKat builds, unless you want to unlock bootloader.
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Use Flashtool to flash your downloaded ftf file. Just make sure your device is charged.
http://forum.xda-developers.com/showthread.php?t=2335555
I believe flashtool will even install the drivers for your 511
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Kamaleon said:
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Click to expand...
Click to collapse
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Moscow Desire said:
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Click to expand...
Click to collapse
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Kamaleon said:
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Click to expand...
Click to collapse
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Moscow Desire said:
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Click to expand...
Click to collapse
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Kamaleon said:
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Click to expand...
Click to collapse
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Moscow Desire said:
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Click to expand...
Click to collapse
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Kamaleon said:
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Click to expand...
Click to collapse
Well, I'm not sure which route to take.
However, I will tell you what I have learned the other day.
I have the 521 with unlocked bootloader. Rooted with my own boot.img, flashed SuperSU using "flashboot boot recovery.img" (yeah, sometimes it doesn't show on the display, so it takes a few times).
Now, other day I was going to check out the new LyPop pre-rooted. Fastboot flash recovery recovery,img, and it won't boot it to recovery like it should. Like it's not flashed. Tried it a couple times. Now, I didn't install the dual recovery as I'm not sure how that kernel (boot.img) will interact with my current tabs OS. Not to mention I need it for my work until tomorrow. But strangely it sounds like the same issue you have.
This weekend I will investigate it. As for me, I will probably flash the Stock ftf lyPop build, and just root it using a modified boot.img.
One thing I do know, is flashing a custom recovery to the "recovery" partition, doesn't seem to work like it used to work on other devices. It seems the flashing to the "Fota kernel" partition seems to be the only method that works. This is what happens when you flash that dual recovery, or any recovery that has a boot image using "Fota". Probably explains why you can't get rid of it using "fastboot erase recovery". because it's erasing the wrong partition. Only flashing a full ftf gets rid of it, because the ftf has a new FotaKernel it flashes.
Eh, something like that. Will look at it this weekend.
Hi all
I am in big trouble. Please help me out.
I have HTC One X+ since last 1.5 years. It came with everything locked.
In order to install CyanogenMod i tried to root my HTC OneX+ and successfully did. The phone went back to factory settings.
After this, the real problem started. I downloaded a recovery.img and boot.img from somewhere over the net (I was careful but not sure if i downloaded the right one) and flashed it into my device. Afterwards, boom!!!!. My phone went into recovery loop and everything has been wiped out.
I am still able to fastboot it through my pc but nothing else.
Can anybody suggest what to do??
This is the right twrp recovery for the hox+:
http://dl.twrp.me/enrc2b/twrp-2.8.6.0-enrc2b.img
Download the rom you want to install and extract the boot.img from the zip.
In fastboot flash new recovery.Reboot into recovery and adb push rom's zip into your sd card.
Reboot in fastboot and flash boot.img.Reboot into recovery and flash rom.
Will try this and let you know. Thanks for the advise
If it doesn't work try to flash a working kernel first and then twrp recovery.
Coolgoly said:
If it doesn't work try to flash a working kernel first and then twrp recovery.
Click to expand...
Click to collapse
Because doing that will change the outcome.................Right?
It will make zero difference. The issue is the user.
As directed, i downloaded the twrp file and flashed it. Now the phone is getting into Recovery mode. Thanks!!
However, after that, i copied many compatible ROMs (Venom, Evagelincia, etc...), extracted their boot.img on my computer and flashed them one by one on my phone. Every time, the the process gets stuck. Each time i waited for 15-20 min for the boot to be flashed but nothing.
Did i miss something in between or i am not using the right boot.img?
pokharna said:
As directed, i downloaded the twrp file and flashed it. Now the phone is getting into Recovery mode. Thanks!!
However, after that, i copied many compatible ROMs (Venom, Evagelincia, etc...), extracted their boot.img on my computer and flashed them one by one on my phone. Every time, the the process gets stuck. Each time i waited for 15-20 min for the boot to be flashed but nothing.
Did i miss something in between or i am not using the right boot.img?
Click to expand...
Click to collapse
cmd needs to have ADMINISTRATOR access for fastboot on windows or you need to use SUDO on linux
OF course i used CMD as ADMINISTRATOR
EDIT:
In my way of trying to apply to warranty and flashing the stock package into the phone and Windows being Windows, I had problems using the batch script, it stopped for long time and didn't do nothing forcing me to restart the phone and restart the batch, until I uninstalled the driver and make Windows reinstall it automatically (manage devices) and it finally flashed it all, actually I flashed the package three times just to be sure lol. So, in the end I wanted to turn off the friggin phone because I was very done with it (what a PITA it has been) and wanted to apply for my warranty so as there is no command in fastboot to shutdown the phone I didn't know how to shut it down so I tried pressing Power button and releasing it the moment the screen goes off but I think I didn't do it right or the phone can't be shutdown that way (this is most probably the answer), well the phone rebooted and by the grace of Zeus it booted for the first time into MIUI and now is waiting for me to configure the phone, none of the times I flashed this packaged into the phone it booted into MIUI, never, and just when I want to turn the phone this thing boots, I don't know if I'm going to venture into flashing anything again being the phone how it is but goddamnit it was a real PITA, I had to use my old Redmi Note 3.
So, tl;dr: Flashed stock package, phone booted finally, all is OK for now.
====================================================================================================
====================================================================================================
Sooo, I was having problems with flashing stuff on this phone but I solved them and I was able to flash HavocOS, it was OK and I could use my phone kinda well (some reboots but nothing serious, or so I thought). So, until 12 hours ago my phone was having problems with the File Manager (I used FX app and also the stock one), it hanged and didn't respond and made the phone reboot itself a couple times, that was weird, actually the whole time I used this ROM I was having problems with my files, it used to took long time to read some files and I was thinking that maybe my SD was bad but apparently it's not. So, after the second reboot I was able to finally open the file manager but navigating through the SDCard was buggy and the app didn't show me any file (it show me an empty list) so I rebooted my phone manually (this time wasn't done by the phone itself) and now is when the phone never passed from the Havoc logo, I waited something close to 30 min and nothing, rebooted and waited 10 min and nothing, it still hanged on the logo, went into recovery to wipe everything and re-flash all and after doing all that and tried to boot to system my phone was booting to recovery and didn't past that, tried installing stock (flash_all script) and then installing recovery and everything again and nothing, it booted to recovery always. So there is when I realized I couldn't change anything in the slot A (at least to what boot refers), I can't install TWRP nor OrangeFox, I can do it in slot B, and even if I boot into recovery on slot B I can flash the zip installer, change the slot and try to boot to recovery from slot A but it boots to the bootloader, and yes, TWRP didn't output any error when flashing the installer.
Yes, the script flashes everything OK, well not everything, system and vendor partitions (A and B) I had to flash them manually because it gave me some errors with the script (reading errors, and yes I compared checksums so it was super weird) but in the end supposedly the stock ROM must have been installed, which I couldn't try because even after flashing everything on the script the phone was booting to bootloader, I didn't give importance to this because before I was able to flash and boot HavocOS I did the same thing because my phone was bootlooping into fastboot: I ran the script, flashed manually those images because it gave me the same errors, tried to boot to system and the phone booted to bootloader, didn't give a sheat, flashed OrangeFox recovery, ROM, recovery installer, GApps, nofde patch and then I was able to boot to HavocOS. But now this time I tried to install TWRP with fastboot command but it didn't worked, fastboot doesn't throw any errors while flashing, it reported:
Sending 'boot_a' (39780 KB) OKAY [ 1.042s]
Writing 'boot_a' OKAY [ 0.208s]
Finished. Total time: 1.263s
But if I try to boot into recovery it sends me to fastboot/bootloader, if I do this in the slot B I can successfully boot into recovery and, as I said, if I flash the installer, change the slot and reboot to recovery, my phone reboots to fastboot.
This has happened to someone else?
Does anybody knows of any solution?
I still have warranty (phone has less than 3 months) so I probably can flash the stock package and lock my bootloader so I can get my phone checked as probably it is a hardware failure, probably and hopefully .
Oh, and also I have to add that the recovery was also lagging sometimes (OrangeFox). Sometimes when I was looking into files on the SD, also when I pressed the "reboot system" button it hanged for half a minute and the it proceeded to reboot, and also once when I was flashing the nofde patch the phone also hanged and rebooted into recovery by itself. So this indicates that maybe is a hardware thing right? Because there is no way that the recovery could have gotten corrupted or something just out of the blue.
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
RthurPendragon said:
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
Click to expand...
Click to collapse
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Jhon_Locke said:
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Click to expand...
Click to collapse
In my case, I wiped system and installed Evolution X ROM (OSS version) with Custom Recovery (SHRP) Then when I want to reboot into recovery again to flash Magisk, There's no recovery... It always opens with fastboot mode. I tried flashing recovery.zip from slot b. Still no result.
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Iamdchandan said:
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Click to expand...
Click to collapse
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Iamdchandan said:
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Click to expand...
Click to collapse
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
garylawwd said:
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
Click to expand...
Click to collapse
First if all reboot into fastboot mode then connect with pc then type command " fastboot flashing unlock" enter now again forcefully reboot into fastboot mode then type next command "fastboot flashing_critical unlock" now bootloader unlock.
Again reboot into fastboot mode then type command "fastboot getvar current-slot"
Now change current active slot and then type command " fastboot erase boot" . Now finally flashed twrp latest (3.4) for Android 10 with command "fastboot flash boot twrp.img" now it flash successfully then type command "fastboot reboot" and then press volume up then hit enter and it return in fastboot mode then i have again change slot and repeat all process with that slot but it again stuck in fastboot mode. After all i have changed twrp version but again same thing repeat so I flashed stock Android 10 through Mi flash and lock bootloader.
That's all whole process.
If do something wrong please help me to figure out.
Waiting for your reply ?.
Love
try sharp recovery
Sami Devo said:
try sharp recovery
Click to expand...
Click to collapse
I don't know installation process of sharp recovery.
Iamdchandan said:
I don't know installation process of sharp recovery.
Click to expand...
Click to collapse
install on the other slot... dont flash it on running rom slot... if rom running A.. chng it to B. then flash to B.. then goto recovery flash the sharp zip when sharp opens..then again chng slot to A.. running rom slot..
okk ur phn boots.