Can't get into recovery to flash updated rom - LG V30 Questions & Answers

Hi all,
I appear to have done something wrong when flashing my device with boombox and flashing twrp. I seem not to be able to access recovery so I can update my boombox rom. I have tried button combinations, I have tried fastboot boot twrp.img in bootloader which just reboots my system, I have tried booting directly from home screen using adb which registers an error and I have tried re-flashing but unfortunately I cannot access recovery.
Any way I can get into recovery without erasing my data?

Jonnibravo said:
Hi all,
I appear to have done something wrong when flashing my device with boombox and flashing twrp. I seem not to be able to access recovery so I can update my boombox rom. I have tried button combinations, I have tried fastboot boot twrp.img in bootloader which just reboots my system, I have tried booting directly from home screen using adb which registers an error and I have tried re-flashing but unfortunately I cannot access recovery.
Any way I can get into recovery without erasing my data?
Click to expand...
Click to collapse
If you're rooted, give the reboot recovery app you installed after bootloader unlock root privileges.
If not then use the exact same PC ADB commands to boot to TWRP like during bootloader unlock.
I'm confused why you mention flashing TWRP after Boombox. Surely you didn't do that. You already had TWRP.

I am rooted, Recovery reboot just reboots the phone, I have tried to get into twrp by reinstalling but again does the same things just reboots the system after the corruption warning screen. I've also tried to install from the bootloader with the fastboot boot twrp.img command but it simply says waiting for device.

Sorry turns out I was flashing the wrong file from another tutorial, I was flashing 3.1.1 instead of 3.2.1

Jonnibravo said:
Sorry turns out I was flashing the wrong file from another tutorial, I was flashing 3.1.1 instead of 3.2.1
Click to expand...
Click to collapse
Then you didn't follow my bootloader unlock and root guide. I never mention that other TWRP, much less link to it.

You're going to have to load into Download mode and use fastboot commands, but you say you couldn't get past flashing TWRP.
Uninstall the LG Mobile Driver if you have them, then reinstall.
1st, reboot into OS, then open up Device Manager and change view to Show hidden devices. You should see a new category named 'ADB Interface' and underneath that 'Fastboot Interface (Google USB ID)'.
If not, you will also see 'ADB Device' for Other Devices category:
right click that to update driver software ---> Browse my computer for driver software ---> Let me pick from a list... ---> Show all Devices ---> Have Disk ---> Browse ---> C:\Program Files (x86)\LG Electronics\LG Mobile Driver ---> 'lgandbus' ---> 'LGE ADB Mobile Interface'
Download adb/fastboot software, download Joan TWRP 3.2.1 img file and place it in adb/fastboot folder, then send your phone into Download mode:
Open up cmd and type the following after changing directory to Adb/fastboot folder: fastboot devices (see if your device is there), fastboot flash recovery TWRP.img or (whatever file is named).img, then fastboot boot TWRP.img or (whatever file is named).img

Related

[[ SOLVED ]] Help! Device Not Found

[[ SOLVED ]]
I was trying to flash a rom and I did wrong.
The phone got stuck on the white HTC screen.
I'm trying to get it back, the problem is that when I connect to the pc is not recognized. I installed SDK Tools, adb, drivers and all.
All In One Toolkit run and try to flash the boot.img but it says "error: device not found"
I run adb commands but it says the same thing, "error: device not found"
I tried it with Venom Flasher but I can not solve.
I uninstalled and went back to install the drivers, but I still have the same result, I run out of options.
When I turn the phone enters fastboot, I can access the recovery, but the phone at this time does not rom, dead.
By mistake I went to lock the bootloader but today I unlock it again with the All In One Toolkit and the bin file, so do not understand why if the file could flasher to unlock the bootloader again, but when trying to flash the boot.img or execute commands like: adb devices, adb reboot bootloader throws the error "device not found"
I appreciate it can help me ...
rikrdoVe said:
I was trying to flash a rom and I did wrong.
The phone got stuck on the white HTC screen.
I'm trying to get it back, the problem is that when I connect to the pc is not recognized. I installed SDK Tools, adb, drivers and all.
All In One Toolkit run and try to flash the boot.img but it says "error: device not found"
I run adb commands but it says the same thing, "error: device not found"
I tried it with Venom Flasher but I can not solve.
I uninstalled and went back to install the drivers, but I still have the same result, I run out of options.
When I turn the phone enters fastboot, I can access the recovery, but the phone at this time does not rom, dead.
By mistake I went to lock the bootloader but today I unlock it again with the All In One Toolkit and the bin file, so do not understand why if the file could flasher to unlock the bootloader again, but when trying to flash the boot.img or execute commands like: adb devices, adb reboot bootloader throws the error "device not found"
I appreciate it can help me ...
Click to expand...
Click to collapse
ADB commands are only recognized in recovery or when system is running. re-unlock your bootloader first. you can reboot into bootloader by pressing and holding power & volume-down button. navigate using volume buttons and enter fastboot by pressing power button. Now you can flash boot.img with "fastboot flash boot boot.img" or using any One X+ compatible toolkit. If it doesn't work, try installing latest HTC sync on your computer to get latest drivers. you can uninstall htc sync later again, the drivers will remain installed.
Here's a guide how you can setup adb/fastboot on cour computer, also contains useful information for beginners: http://forum.xda-developers.com/showthread.php?t=2213910
reaper90 said:
ADB commands are only recognized in recovery or when system is running. re-unlock your bootloader first. you can reboot into bootloader by pressing and holding power & volume-down button. navigate using volume buttons and enter fastboot by pressing power button. Now you can flash boot.img with "fastboot flash boot boot.img" or using any One X+ compatible toolkit. If it doesn't work, try installing latest HTC sync on your computer to get latest drivers. you can uninstall htc sync later again, the drivers will remain installed.
Here's a guide how you can setup adb/fastboot on cour computer, also contains useful information for beginners: http://forum.xda-developers.com/showthread.php?t=2213910
Click to expand...
Click to collapse
Yeah, try doing that. I locked boot loader again but still had no results. What I did right now was "fastboot flash boot boot.img" says ok, but just gets stuck on the white screen. The phone right now has no information, nothing. I have in my pc folder with the rom that was installed (zip with boot.img) I have the latest version of clockworkmode.
rikrdoVe said:
Yeah, try doing that. I locked boot loader again but still had no results. What I did right now was "fastboot flash boot boot.img" says ok, but just gets stuck on the white screen. The phone right now has no information, nothing. I have in my pc folder with the rom that was installed (zip with boot.img) I have the latest version of clockworkmode.
Click to expand...
Click to collapse
Some more information please. What rom did you flash and what recovery did you use? also do you have international version of this phone or AT&T/Telus version?
reaper90 said:
Some more information please. What rom did you flash and what recovery did you use? also do you have international version of this phone or AT&T/Telus version?
Click to expand...
Click to collapse
1. Carbon ROM: http://forum.xda-developers.com/showthread.php?t=2447870&page=33
2. CWM 6.0.4.6
3. Yes, international version.
rikrdoVe said:
1. Carbon ROM: http://forum.xda-developers.com/showthread.php?t=2447870&page=33
2. CWM 6.0.4.6
3. Yes, international version.
Click to expand...
Click to collapse
Did you use the right version of CWM for android 4.4+?
reaper90 said:
Did you use the right version of CWM for android 4.4+?
Click to expand...
Click to collapse
Correct, as said in the post "Note: For KK 4.4.x necessary CWM recovery from Lloir's thread."
rikrdoVe said:
Correct, as said in the post "Note: For KK 4.4.x necessary CWM recovery from Lloir's thread."
Click to expand...
Click to collapse
Did you do a wipe in before flashing the new rom?
Anyway you can copy a new rom.zip onto your phone using "adb sideload rom.zip" or "adb push rom.zip /data/media/0" while you're in recovery. Then do a full wipe first, flash rom and don't forget to flash boot.img.
reaper90 said:
Did you do a wipe in before flashing the new rom?
Anyway you can copy a new rom.zip onto your phone using "adb sideload rom.zip" or "adb push rom.zip /data/media/0" while you're in recovery. Then do a full wipe first, flash rom and don't forget to flash boot.img.
Click to expand...
Click to collapse
Thanks for your help...
I cant flash zip file, its says "error: device not found".
I put the zip file in adb folder, then "adb sideload filename.zip"
Do not know if I'm doing well, I turn on the phone in recovery mode, then with the volume keys I go to "install zip" option then "install zip from sideload" then run the command I get the error.
rikrdoVe said:
Thanks for your help...
I cant flash zip file, its says "error: device not found".
I put the zip file in adb folder, then "adb sideload filename.zip"
Do not know if I'm doing well, I turn on the phone in recovery mode, then with the volume keys I go to "install zip" option then "install zip from sideload" then run the command I get the error.
Click to expand...
Click to collapse
ADB may take some time to recognize your device in recovery. Try "adb devices" first and if it isn't listed as in recovery or sideload, wait some minutes and try again. Shouldn't take more than 5 minutes though.
But you have installed latest drivers?
reaper90 said:
ADB may take some time to recognize your device in recovery. Try "adb devices" first and if it isn't listed as in recovery or sideload, wait some minutes and try again. Shouldn't take more than 5 minutes though.
But you have installed latest drivers?
Click to expand...
Click to collapse
Hey, i tried that, and says:
List of devices attached:
FA31ZW100713 recovery
And then, i write "adb sideload filename.zip"
Error: Closed >>
I waited 6 minutes and the same result.....
And yes, i have the latest drivers and HTC Sync Manager.
rikrdoVe said:
Hey, i tried that, and says:
List of devices attached:
FA31ZW100713 recovery
And then, i write "adb sideload filename.zip"
Error: Closed >>
I waited 6 minutes and the same result.....
And yes, i have the latest drivers and HTC Sync Manager.
Click to expand...
Click to collapse
Your phone needs to be in recognized as in sideload mode in order to use adb sideload. when recognized in recovery, try "adb push rom.zip /data/media/0", this will copy your rom onto your phones internal memory. Depending on rom size, this may take some minutes and there's no progress bar/display, so give it some time, 10 min should be enough.
reaper90 said:
Your phone needs to be in recognized as in sideload mode in order to use adb sideload. when recognized in recovery, try "adb push rom.zip /data/media/0", this will copy your rom onto your phones internal memory. Depending on rom size, this may take some minutes and there's no progress bar/display, so give it some time, 10 min should be enough.
Click to expand...
Click to collapse
A month without phone and thanks to you it works again!
Thank you so much, I could not pass the zip in any way but with "adb push rom.zip / data/media/0 /" if it happened and I could flash ...
I Repeat .... THANK YOU!
have the same problem with my HTC One X.
Can you gave me an answer?

Bootloader state error - Boot to TWRP when trying to unlock, still locked

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

twrp installation

Hello guys.
I have been in the android world for a while, but just got this device.
I had tried to install twrp with no success. I already have bootloader unlocked by me with no issues, following a tutorial here. When I flash twrp it shows success but when I try to go there ñ, it just goes to miui recovery. When I boot directly from fastboot with:
Fastboot boot twrp.img
It goes there with no issues but of course, data is encrypted. So I want to install it in order to format my data and be able to root. Any ideas?
I researched and found that one way is to install a dev rom, but I really want to remain on stable one.
Thoughts?
Jemec26 said:
Hello guys.
I have been in the android world for a while, but just got this device.
I had tried to install twrp with no success. I already have bootloader unlocked by me with no issues, following a tutorial here. When I flash twrp it shows success but when I try to go there ñ, it just goes to miui recovery. When I boot directly from fastboot with:
Fastboot boot twrp.img
It goes there with no issues but of course, data is encrypted. So I want to install it in order to format my data and be able to root. Any ideas?
I researched and found that one way is to install a dev rom, but I really want to remain on stable one.
Thoughts?
Click to expand...
Click to collapse
Put a copy of twrp.img in your sdcard.
Put other copy of twrp.img in adb folder of your pc.
Type from a cmd with admin rights with device in fastboot mode connected to pc fastboot boot twrp.img and when you reboot to twrp slide allowing modifications and then flash your twrp.img through same twrp recovery
The first command will do that device can boot to twrp but it´ll not flash it in recovery partition.
The second action will flash it permanently onto your device.
Probably you´ll need to format data in order to can reboot to system again.
SubwayChamp said:
Put a copy of twrp.img in your sdcard.
Put other copy of twrp.img in adb folder of your pc.
Type from a cmd with admin rights with device in fastboot mode connected to pc fastboot boot twrp.img and when you reboot to twrp slide allowing modifications and then flash your twrp.img through same twrp recovery
The first command will do that device can boot to twrp but it´ll not flash it in recovery partition.
The second action will flash it permanently onto your device.
Probably you´ll need to format data in order to can reboot to system again.
Click to expand...
Click to collapse
Thanks! I solved it after taking a look for a while. I do not have an sdcard, so I flashed it and then fastboot booted it, then I reboot recovery to make sure it was flashed and then formatted data. I worked flawlessly!

DEEP TROUBLE! Please help.....

I had previously rooted and used several roms but recently i went back to developer rom and now when i try to flash twrp via command prompt it shows WRITE TO DEVICE FAILED (INVALID ARGUMENT)! I put all the files properly retried it 100s of times but it just doesn't flash. I flashed twrp last time by this very process!
Using isb 3.0 and 2.0 didnot solve the problem
Please provide a solution!
maybe the bootloader got locked check otherwise erase and flash the whole rom using fastboot mi flash tool
atrirocks said:
I had previously rooted and used several roms but recently i went back to developer rom and now when i try to flash twrp via command prompt it shows WRITE TO DEVICE FAILED (INVALID ARGUMENT)! I put all the files properly retried it 100s of times but it just doesn't flash. I flashed twrp last time by this very process!
Using isb 3.0 and 2.0 didnot solve the problem
Please provide a solution!
Click to expand...
Click to collapse
Try booting in recovery again via Fastboot.
- Install Minimal ADB & Fastboot setup (search on Google or XDA)
- Go in Fastboot mode of phone and connect it to PC
- Open command prompt and go to the folder location where minimal ADB is installed
- Type:
fastboot devices
- You should see your device listed with some Alpha-numeric code
- Copy TWRP by Vashishth or official TWRP .img file in the Minimal ADB installation folder
- type:
fastboot boot your-recovery-file-name.img
If your bootloader is not locked, you should be able to see phone rebooted in TWRP else you might need to unlock bootloader again.
Also if in TWRP Install commands are not working, try "Format Data" it is different from Wiping Data partition, Format Data will clear all of your internal storage including photos and videos and files.
After that you can download ROM or your PC and try installing it by sideloading it via adb command.
Good luck!
asifzbaig said:
Try booting in recovery again via Fastboot.
- Install Minimal ADB & Fastboot setup (search on Google or XDA)
- Go in Fastboot mode of phone and connect it to PC
- Open command prompt and go to the folder location where minimal ADB is installed
- Type:
fastboot devices
- You should see your device listed with some Alpha-numeric code
- Copy TWRP by Vashishth or official TWRP .img file in the Minimal ADB installation folder
- type:
fastboot boot your-recovery-file-name.img
If your bootloader is not locked, you should be able to see phone rebooted in TWRP else you might need to unlock bootloader again.
Also if in TWRP Install commands are not working, try "Format Data" it is different from Wiping Data partition, Format Data will clear all of your internal storage including photos and videos and files.
After that you can download ROM or your PC and try installing it by sideloading it via adb command.
Good luck!
Click to expand...
Click to collapse
Bootloader is unlocked, fastboot tried a thousand times where fastboot devices shows the device but fastboot flash recovery shows the error! I even tried changing the twrp, renaming it but to no result.....
atrirocks said:
Bootloader is unlocked, fastboot tried a thousand times where fastboot devices shows the device but fastboot flash recovery shows the error! I even tried changing the twrp, renaming it but to no result.....
Click to expand...
Click to collapse
Than it seems like yoir bootloader is locked.
Try using Xiaomi's Unlock Tool again, beware, it will wipe all of yoir internal storage as well.
atrirocks said:
I had previously rooted and used several roms but recently i went back to developer rom and now when i try to flash twrp via command prompt it shows WRITE TO DEVICE FAILED (INVALID ARGUMENT)! I put all the files properly retried it 100s of times but it just doesn't flash. I flashed twrp last time by this very process!
Using isb 3.0 and 2.0 didnot solve the problem
Please provide a solution!
Click to expand...
Click to collapse
Try edl mode to flash the full file and beware of anti rollback
karthik03 said:
Try edl mode to flash the full file and beware of anti rollback
Click to expand...
Click to collapse
How do I boot into EDL mode & how to check anti-roll back is on?, anyway to disable it?. I updated my phone to 10.2.3 couple of days back from then on, the network speed is horrible. Although I unlocked my bootloader as soon as I got my phone(I am an early adopter), I never flashed TWRP. Now when I try to flash TWRP to move to a custom ROM, I'm always getting same error as OP. All the drivers are installed, I can see my device in fastboot devices but it just refuses to flash TWRP. I can see bootloader status is unlocked!!.
atrirocks said:
Bootloader is unlocked, fastboot tried a thousand times where fastboot devices shows the device but fastboot flash recovery shows the error! I even tried changing the twrp, renaming it but to no result.....
Click to expand...
Click to collapse
Doesn't try the fastboot flash recovery recovery.img, try fastboot boot recovery.img ,that can help
mjskraju said:
How do I boot into EDL mode & how to check anti-roll back is on?, anyway to disable it?. I updated my phone to 10.2.3 couple of days back from then on, the network speed is horrible. Although I unlocked my bootloader as soon as I got my phone(I am an early adopter), I never flashed TWRP. Now when I try to flash TWRP to move to a custom ROM, I'm always getting same error as OP. All the drivers are installed, I can see my device in fastboot devices but it just refuses to flash TWRP. I can see bootloader status is unlocked!!.
Click to expand...
Click to collapse
Use fastboot to edl it is present on xda or try shorting of pins
atrirocks said:
I had previously rooted and used several roms but recently i went back to developer rom and now when i try to flash twrp via command prompt it shows WRITE TO DEVICE FAILED (INVALID ARGUMENT)! I put all the files properly retried it 100s of times but it just doesn't flash. I flashed twrp last time by this very process!
Using isb 3.0 and 2.0 didnot solve the problem
Please provide a solution!
Click to expand...
Click to collapse
Have you tried different PC? Mine works on Intel and have same error code on AMD.
atrirocks said:
Bootloader is unlocked, fastboot tried a thousand times where fastboot devices shows the device but fastboot flash recovery shows the error! I even tried changing the twrp, renaming it but to no result.....
Click to expand...
Click to collapse
AMD Ryzen has an issue with Poco F1. Try Intel PC.
Also is your TWRP in the same folder as your adb tools/are you typing the correct path?
tnsmani said:
AMD Ryzen has an issue with Poco F1. Try Intel PC.
Also is your TWRP in the same folder as your adb tools/are you typing the correct path?
Click to expand...
Click to collapse
Seems like ryzen is the problem brother! I used another pc as i had no other options left

I am unable to flash TWRP using adb

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.

Categories

Resources