Related
Hi all,
Just followed the instructions below to get a new rom on my TF201.
Now I have Teamwin recovery booting showing V2.6.3.0 and asking for a password.
Teamwin does not show data in external or internal sdcards.
I am unable to get into fastboot mode, using power and vol down.
It has failed since running this line fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob
I have all of the nvflash blobs etc.
Any ideas how to recover from this point?
Thanks
RR
This may help
Starting from a stock bootloader V 10.4.2.18
What you will need
Woking fastboot & adb / SDcard optional
TWRP for a 201 = twrp_tf201t.blob
@ne0zone75 TWRP for the 300 = ne0zone75_tf300t.blob
HairyBean BL & TWRP: This is effectively turn your 201 into a 300 <---- which is a flashable zip inside the zip that you downloasd
All 3 of the above file are in a zip in the Download section @ the top of every page of the thread ...... THIS ZIP IS NOT FLASHABLE...Your must unzip it to get to the real files !!! The name of this zip is 'upgrade_tf201_to_tf300t.zip'
CROMBI 201 ROM zip
A fully charged tablet
All the above files in the same directory as your fastboot.exe (if using windows) In your home folder on linux....
The process
Lets start with the TWRP recovery for the 201, let flash it with fastboot...
Power your tablet off and with the [ VOL DOWN & POWER ] buttons boot the tablet into the bootloader
Once there [ VOL DOWN ] untill the green box is on the USB ICON then [ VOL UP ] to select fastboot
Let make sure your PC can see your tablet with this command.
Code:
fastboot devices
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
Then
Code:
fastboot -i 0x0b05 reboot-bootloader
[ VOL UP ] ON RCK to enter recovery
Once in TWRP check to see if adb is working...
Code:
adb devices
Ok now that we know that is working let go ahead and push the HairyBean BL onto the tablet
Code:
adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard
Now under the install tab in TWRP fine the folder and flash it....
reboot once it has fishined..If ask to install SuperUser say NO..........
LET THE BLUE BAR FILL !!!!!!!!! Once it has finished it will reboot into Hairybean TWRP....
Once booted into recovery, run this command to boot into fastboot
Code:
adb reboot-bootloader
You will see that the USB icon is missing now, this is good... If you still see the USB icon DON'T go to the next step
Now lets flash @ne0zone75 TWRP recovery
Code:
fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob
Once that has finished let reboot into bootloader
Code:
fastboot -i 0x0b05 reboot-bootloader
Now enter recovery....
Make sure its verison 2.7.1.0
Go to Wipe////Format Data////Type yes
This can take up to 90 mins to format
DO NOT INTERRUPT THE FORMAT !!!!!!!
Now lets push CROMBI-KK onto your tab
Code:
adb push cm-11.0-2014xxxx-crombi-kk-tf201t.zip /sdcard
Find it under the install tab and flash it..
REBOOT into android, first boot can take up to 15 minutes
ADB interface working
Ok, lots of playing this morning tells me that the adb interface is working when the teamwin recovery is showing.
adb devices gives <number> recovery
Any ideas how to proceed from here, apart from carefully
RangeyRover1 said:
Ok, lots of playing this morning tells me that the adb interface is working when the teamwin recovery is showing.
adb devices gives <number> recovery
Any ideas how to proceed from here, apart from carefully
Click to expand...
Click to collapse
When on the twrp screen .....
Does the command .....
Code:
adb reboot-bootloader
Do anything ??
Thx Josh
Hello I was having a tough time trying to Flash Crombi KK rom. At 1 point I had to use a recovery blob because I was stuck. I started from there upgraded bootloader and twrp 2.5. Flashed twrp 2.8 and Crombi KK rom kept showing fail. I eventually gave up and tried to go from 2.8 TWRP back to 2.5 with JB Bootloader. Bad move I know. Whenever I pressed up to go to recovery it would get stuck. Then eventually I tried wiping data from Bootloader screen. Now the 3 options, recovery, coldboot and wipe data wont show. Stuck at Asus screen "The Device is Unlocked".
I downloaded naked drivers and android ADB drivers.. however I cannot get them to install on windows 7. I'd appreciate any help to try to this back running again
Lyvewire said:
Hello I was having a tough time trying to Flash Crombi KK rom. At 1 point I had to use a recovery blob because I was stuck. I started from there upgraded bootloader and twrp 2.5. Flashed twrp 2.8 and Crombi KK rom kept showing fail. I eventually gave up and tried to go from 2.8 TWRP back to 2.5 with JB Bootloader. Bad move I know. Whenever I pressed up to go to recovery it would get stuck. Then eventually I tried wiping data from Bootloader screen. Now the 3 options, recovery, coldboot and wipe data wont show. Stuck at Asus screen "The Device is Unlocked".
I downloaded naked drivers and android ADB drivers.. however I cannot get them to install on windows 7. I'd appreciate any help to try to this back running again
Click to expand...
Click to collapse
Do you have your nvflash blobs backed up ?
Thx Josh
lj50036 said:
Do you have your nvflash blobs backed up ?
Thx Josh
Click to expand...
Click to collapse
No blobs. I 've had this device since day one. Rooted it, bricked before but never this. I remember having a hard time making a NVFlashbackup for the same reason of my device showing up and eventually gave up. Any other suggestions?
Lyvewire said:
No blobs. I 've had this device since day one. Rooted it, bricked before but never this. I remember having a hard time making a NVFlashbackup for the same reason of my device showing up and eventually gave up. Any other suggestions?
Click to expand...
Click to collapse
No nvflash blob, no fastboot, no adb ....
There is nothing that can be done if the above statement is true ......
Thx Josh
lj50036 said:
No nvflash blob, no fastboot, no adb ....
There is nothing that can be done if the above statement is true ......
Thx Josh
Click to expand...
Click to collapse
Thanks for replying
I tried using this http://forum.xda-developers.com/showthread.php?t=2588979 to install ADB. It got to waiting for device and of course nothing. Is there something else needed to get the ADB to read the device? I downloaded the naked drivers as well but nothing showed up in device manager. No executable file to run. Am I missing something?
WooHoo
lj50036 said:
When on the twrp screen .....
Does the command .....
Code:
adb reboot-bootloader
Do anything ??
Thx Josh
Click to expand...
Click to collapse
Why, yes. yes it does Thanks.
Ok I have the RCK, Android,wipe data icons.
fastboot devices on this screen now gives <number> fastboot
Woot!
I'm keen to have specific instructions on how to recover from this point back to stock, then take a deep breath and try to get to custom.
My concern is that a lot of the threads with guidance for recovery and flashing are old, and I don't want to brick this thing.
So, is there a thread for recovery to stock from this point?
I have found this thread discussing recovery. http://forum.xda-developers.com/transformer-prime/help/guide-t2864946
am waiting for full charge of tablet at the moment.
Thanks for all the help so far.
RR
RangeyRover1 said:
Why, yes. yes it does Thanks.
Ok I have the RCK, Android,wipe data icons.
fastboot devices on this screen now gives <number> fastboot
Woot!
I'm keen to have specific instructions on how to recover from this point back to stock, then take a deep breath and try to get to custom.
My concern is that a lot of the threads with guidance for recovery and flashing are old, and I don't want to brick this thing.
So, is there a thread for recovery to stock from this point?
Thanks for all the help so far.
RR
Click to expand...
Click to collapse
You need the blob from the stock frimware downloaded from the Asus website ....
It will be in a zip file that needs unzipped twice ...... Make sure you get the correct 'SKU' for your tablet ......
Then follow this guide, skip to the first fastboot command and go from there .....
http://forum.xda-developers.com/showthread.php?t=2538028
Thx Josh
FIXED
lj50036 said:
You need the blob from the stock frimware downloaded from the Asus website ....
It will be in a zip file that needs unzipped twice ...... Make sure you get the correct 'SKU' for your tablet ......
Then follow this guide, skip to the first fastboot command and go from there .....
http://forum.xda-developers.com/showthread.php?t=2538028
Thx Josh
Click to expand...
Click to collapse
Thanks, thats got me back to square one.
Maybe a new thread detailing the pain to get to Custom rom!
Cheers Josh.
RR
tf300 update required?
Ok, i seem to be failing when i apply neowin tf300 update, when following the crombikk instructions on post #4. The system does not now boot into recovery. Is this step absolutely required for the newer roms?
Thanks
RR
Hey guys,
i've got the following problem: Unlocking the bootloader, installing TWRP and other ROMs went hassle free and worked flawless until recently.
Now, after having to reflash a clean OOS 2.2.0, it says the bootloader is locked again. TWRP is still installed. When trying to unlock the phone, it just boots to TWRP (which shortly prints an error message, but its too short to read) and shows that the bootloader is still locked in fastboot.
The problem is similar to this one:
https://forums.oneplus.net/threads/opo-back-from-the-dead-story-of-a-brick.144155/
In that thread, a solution is pointed out -- namely, this one:
http://forum.xda-developers.com/showpost.php?p=54251992
The script is for OPO only, so I'm left in the rain. Do you guys know any other way out of my misery?
Rotpeter said:
Hey guys,
i've got the following problem: Unlocking the bootloader, installing TWRP and other ROMs went hassle free and worked flawless until recently.
Now, after having to reflash a clean OOS 2.2.0, it says the bootloader is locked again. TWRP is still installed. When trying to unlock the phone, it just boots to TWRP (which shortly prints an error message, but its too short to read) and shows that the bootloader is still locked in fastboot.
The problem is similar to this one:
https://forums.oneplus.net/threads/opo-back-from-the-dead-story-of-a-brick.144155/
In that thread, a solution is pointed out -- namely, this one:
http://forum.xda-developers.com/showpost.php?p=54251992
The script is for OPO only, so I'm left in the rain. Do you guys know any other way out of my misery?
Click to expand...
Click to collapse
Install stock recovery and unlock bootloader again...
I'll give it a try. Would you point me in the direction of where to find the recovery.img for that?
EDIT: Phew, did it. Your way worked. I can't even count anymore how often I wiped and reflashed the whole thing in the last 24 hours...
I have exactly the same problem. I have the stock recovery file. Can i just flash it with TWRP ? and stock recovery will be loaded? because i can't use fastboot to load i because its locked
reboot into twrp
copy Stock_recovery.img to device folder
go to install
at the bottom select install image
select stock_recovery.img
reboot into fastboot
in cmd type fastboot oem unlock
reboot into stock recovery
wipe data/cache
format data
install from usb
go to cmd again
sideload oxygen zip instalation
in cmd write adb sideload drag and drop oxygenos.zip
reboot
https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?usp=sharing - stock recovery
s3r3tin said:
reboot into twrp
copy Stock_recovery.img to device folder
go to install
at the bottom select install image
select stock_recovery.img
reboot into fastboot
in cmd type fastboot oem unlock
reboot into stock recovery
wipe data/cache
format data
install from usb
go to cmd again
sideload oxygen zip instalation
in cmd write adb sideload drag and drop oxygenos.zip
reboot
https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?usp=sharing - stock recovery
Click to expand...
Click to collapse
Thanks man, you saved my life <3
I messed up i tried to reflash my phone back to stock from marshmallow rom on the thread here but i lost custom recovery and only thing i can get into is download mode, how can i fix this? I have abd install on my pc got the system image boot and recovery img but don't know what 2 do. Please help
xavier55 said:
I messed up i tried to reflash my phone back to stock from marshmallow rom on the thread here but i lost custom recovery and only thing i can get into is download mode, how can i fix this? I have abd install on my pc got the system image boot and recovery img but don't know what 2 do. Please help
Click to expand...
Click to collapse
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
soltheman said:
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
Click to expand...
Click to collapse
I'm kinda in the same boat now except that I already received the replacement device. Need to re-lock the old V10, but adb won't recognize my device at all. Any more option when that's the case? I can get into both download mode and fastboot. Phone is recognized by LGUP in download mode, but not by adb in fastboot mode for some reason.
(I've verified connection and driver using the other V10, the other V10 is recognized just fine)
soltheman said:
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
Click to expand...
Click to collapse
thanks you saved me
baymon said:
I'm kinda in the same boat now except that I already received the replacement device. Need to re-lock the old V10, but adb won't recognize my device at all. Any more option when that's the case? I can get into both download mode and fastboot. Phone is recognized by LGUP in download mode, but not by adb in fastboot mode for some reason.
(I've verified connection and driver using the other V10, the other V10 is recognized just fine)
Click to expand...
Click to collapse
Yep. Your phone boots and everything, correct? Just factory reset it (Settings > Backup & Restore > Factory data reset). After its been reset, unlock it, turn on Developers Options, and enable USB debugging. After usb debugging is turned on, connect the v10 to your PC and be sure to hit "Always allow" when prompted by your phone. ADB should now be able to see your device.
If you can't get it to boot up, try restoring through LG UP/Bridge. I don't use any of LG's software, so I'm not sure what those apps can do and whether or not you'll be able to restore through them.
If nothing else, your phone is recognized in fastboot mode, so you can always manually flash the stock system images as well. You want to use the "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" commands After downloading the stock system images located in this thread: http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
If you haven't ever flashed system images from fastboot, please read this first, as I am not responsible if your phone turns into a paperweight! https://developers.google.com/android/nexus/images#instructions While the instructions are for nexus devices, it works pretty much the same, except you'd want to use the individual commands instead of a flash-all script.
Hope this helps!
soltheman said:
Yep. Your phone boots and everything, correct? Just factory reset it (Settings > Backup & Restore > Factory data reset). After its been reset, unlock it, turn on Developers Options, and enable USB debugging. After usb debugging is turned on, connect the v10 to your PC and be sure to hit "Always allow" when prompted by your phone. ADB should now be able to see your device.
If you can't get it to boot up, try restoring through LG UP/Bridge. I don't use any of LG's software, so I'm not sure what those apps can do and whether or not you'll be able to restore through them.
If nothing else, your phone is recognized in fastboot mode, so you can always manually flash the stock system images as well. You want to use the "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" commands After downloading the stock system images located in this thread: http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
If you haven't ever flashed system images from fastboot, please read this first, as I am not responsible if your phone turns into a paperweight! https://developers.google.com/android/nexus/images#instructions While the instructions are for nexus devices, it works pretty much the same, except you'd want to use the individual commands instead of a flash-all script.
Hope this helps!
Click to expand...
Click to collapse
Thanks for the follow up! No the phone would not boot at all and kept stuck at boot loop. I ended up just doing the OEM Lock and call it a day, the old device just won't boot to anything at this point.
I tried fastboot flash recovery recovery.img but it's giving some kinda kernel panic message and I was never able to get into recovery. This reminds me of the time when my Note 3 eMMC was fried, it wouldn't give a device ID to adb.
I think I am in the same boat too. I've been OEM unlocked yet recently my phone won't keep the TWRP recovery and keeps putting me into bootloop. I can't install a ROM and only thing I can do is fastboot mode. What did you do OEM lock the device? I am hoping that solution will get rid of that message bootloader unlocked during the bootloop and then I can try and get it serviced.
I am trying to put twrp on my tablet so I can install cyanogenmod but I am running into problems.
Device: sgp311 on android 5.1.1 and bootloader is unlocked.
1. I open cmd terminal from the folder that contains the latest twrp img.
2. I boot into fastboot mode by the cmd command "adb reboot bootloader"
3. I use the command " fastboot flash boot twrp.img" and it's successful (had an image but cant link it)
4. I use the command "fastboot reboot" and nothing my device stays blank, nothing appears on screen even after holding the power and volume up buttons to do a regular reset and hard reset. When I flash android 5.1.1 back on to my device all my data is still there.
I am also trying to use flashtool to revert too android kitkat but after flashing the firmware and booting up it just stays in a bootloop at the sony logo.
Anyone have any suggestions on what to do?
BrickedXperia said:
Anyone have any suggestions on what to do?
Click to expand...
Click to collapse
you're doing it right in general, but there are some issues, though.
Sony devices, like your SGP311 don't have recovery[*] partition, like nexus or other ones.
On Sony, you need to flash kernel with the integrated recovery.
On step 3, you're flashing presumably recovery image (without kernel) to boot partition. As it is not kernel, device is is not booting, which is expectable.
So you need to flash this with CM13 kernel + CM recovery. After flashing reboot device, press VOL- to enter recovery, make necessary wipes, and install CM13 Rom zip.
P.S: With Flashtool fastboot mode, flashing is done easier and faster.
Rootk1t said:
you're doing it right in general, but there are some issues, though.
Sony devices, like your SGP311 don't have recovery[*] partition, like nexus or other ones.
On Sony, you need to flash kernel with the integrated recovery.
On step 3, you're flashing presumably recovery image (without kernel) to boot partition. As it is not kernel, device is is not booting, which is expectable.
So you need to flash this with CM13 kernel + CM recovery. After flashing reboot device, press VOL- to enter recovery, make necessary wipes, and install CM13 Rom zip.
P.S: With Flashtool fastboot mode, flashing is done easier and faster.
Click to expand...
Click to collapse
Thank you, I flashed cyanogenmod recovery with adb commands and restarted it and it worked, I now have cyanogenmod on my tablet and it looks and feels way better than the stock rom.
As BrickedXperia, I am trying to put twrp on my tablet so I can install cyanogenmod but I am running into problems.
Device: sgp321 on android 5.1.1 and bootloader is unlocked.
No root (must I?)
1. I open cmd terminal from the platform-tools folder that contains the latest twrp img.
2. I boot into fastboot mode by the cmd command "adb reboot bootloader"
3. I use the command " fastboot flash boot twrp.img" but here it fails and gives an error.
I see from Rootk1t's reply that you have to do something with kernel. Would someone care to elaborate a bit? I am new to this stuff and it's not straight forward despite all the guides around. I would appreciate any help a lot.
What does the error say?
Something like
writing 'recovery'... failed (remote command not allowed)
Svenni84 said:
Something like
writing 'recovery'... failed (remote command not allowed)
Click to expand...
Click to collapse
if it says not allowed, check that bootloader state is really unlocked.
Rootk1t said:
if it says not allowed, check that bootloader state is really unlocked.
Click to expand...
Click to collapse
When I open the hidden service menu it really does say that it is. Is it any other way to confirm this?
I recently found my old HTC desire 526g and I decided to flash a custom ROM, but its volume buttons aren't working so I had to use adb, I am not really an good in these types of things. I tried to flash TWRP on my htc using adb (Followed a YouTube tut) but this is coming up.
I have attached a screenshot below.
After unlocking bootloader (probably would have done it earlier) did you allow the usb debugging.
2) try installing adb+fastboot, platform tools and your htc drivers and keep your recovery file in the platform tools and open cmd there use the appropriate command to flash it
Rajveer chauhan said:
After unlocking bootloader (probably would have done it earlier) did you allow the usb debugging.
2) try installing adb+fastboot, platform tools and your htc drivers and keep your recovery file in the platform tools and open cmd there use the appropriate command to flash it
Click to expand...
Click to collapse
Hello, Thanks for replying! I think I have done everything in correct manner, but still coming thiss error, I have rooted my phone too. BTW, is there any way you can navigate through system recovery without using volume buttons (as they are not working) I mean any commands, to navigate in recovery mode using adb
YourLocalClown69 said:
Hello, Thanks for replying! I think I have done everything in correct manner, but still coming thiss error, I have rooted my phone too. BTW, is there any way you can navigate through system recovery without using volume buttons (as they are not working) I mean any commands, to navigate in recovery mode using adb
Click to expand...
Click to collapse
So if you're rooted so you can flash recovery via twrp app on playstore, or if magisk installer for twrp exists for your phone or by flashfire if you have your working recovery
'adb reboot bootloader' will bring you fastboot mode.
'fastboot flash recovery recovery.img' (while TWRP image or CWM image is renamed recovery.img and placed into the fastboot folder)will bring you TWRP/CWM.
'fastboot reboot recovery' will bring you into TWRP or CWM installed.
'fastboot reboot' will reboot you phone in case you are stuck.
LR7875 said:
'adb reboot bootloader' will bring you fastboot mode.
'fastboot flash recovery recovery.img' (while TWRP image or CWM image is renamed recovery.img and placed into the fastboot folder)will bring you TWRP/CWM.
'fastboot reboot recovery' will bring you into TWRP or CWM installed.
'fastboot reboot' will reboot you phone in case you are stuck.
Click to expand...
Click to collapse
This comes later now lol, Due to my lack of knowledge and not enough patience, I tried to flash custom recovery through TWRP app, and I didn't found my phone model on device list, SO i just selected random htc model phone and now it is restarting over and over again, Is there any fix to this? I am obviously a complete noob in this field.
If possible find stock recovery of that firmware version (be serious abt version) and flash it by fastboot
2) find how to unbrick htc by downloading stock rom this will make you lose all data
Rajveer chauhan said:
If possible find stock recovery of that firmware version (be serious abt version) and flash it by fastboot
2) find how to unbrick htc by downloading stock rom this will make you lose all data
Click to expand...
Click to collapse
Even If I find the this whatever you said, how am I supposed to fix it, as I mentioned,Volume buttons aren;t working and its stuck in bootloop, it won't past its manufacturers logo, so adb is no help in it, Only way to fix it would be to fix sound buttons. sad me, Well, R.I.P. HTC Desire 526g dual sim 2015-2021
I hope that this phone is not your primary driver
YourLocalClown69 said:
I recently found my old HTC desire 526g
Click to expand...
Click to collapse
Rajveer chauhan said:
I hope that this phone is not your primary driver
Click to expand...
Click to collapse
He unearthed his phone from some drawer, so this is not his daily driver.