Related
Hi guys,
Please help !
I've bought a new phone, htc one x, from someone. barely had time to install few apps, and got this OTA update message.
Without thinking twice - i did it. But it seems that the phone was rooted ! and as I understand now - it's a big no-no .
I've tried to figure out from the forum what to do , but - all the answers seems to include fastboot and ADB, which in turn require
the drivers of the phone to be installed. But my phone is dead ! so I can' t do it.
I'm new to roms and all, and I really need your help .
How can I make my phone work again ? I don't care which ROM , custom or stock , just to make it work .
Any help will be appreciated.
Gena
You can access Fastboot? Hold POWER and VOLUMEN - (down)..?
Sent from my HTC One X using Tapatalk 2
big noob said:
You can access Fastboot? Hold POWER and VOLUMEN - (down)..?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Hi , yes, I can access the fast boot, but even trying to restore to factory defaults didn't help.
And I can't istall the fastboot on my pc since it needs to connect to a working phone in debug mode (if I understand correctly)
Google Fastboot files
And place them on your pc..for example
On desktop..
C:\Users\Name\Desktop\
and next step go in that directory via CMD typr this
cd C:\Users\Name\Desktop\Fastboot\
And type this
Fastboot getvar cid
Then you will se your CID
go this thread and follow steps to recover your phone
http://forum.xda-developers.com/showthread.php?t=1975140
Sent from my HTC One X using Tapatalk 2
big noob said:
Google Fastboot files
And place them on your pc..for example
On desktop..
C:\Users\Name\Desktop\
and next step go in that directory via CMD typr this
cd C:\Users\Name\Desktop\Fastboot\
And type this
Fastboot getvar cid
Then you will se your CID
go this thread and follow steps to recover your phone
http://forum.xda-developers.com/showthread.php?t=1975140
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Thank you very much for your help.
I've did the steps as you say, and finally was able to "see" my phone in fastboot from PC.
but the CID I am getting is 11111111 , and there is no backup that matches it.
Can I overwrite it with some kind of rom ? I don't care to loose all the data, just to get a working phone.
Download clockwordmod recovery img file And flash it via Fastboot..
Fastboot flash recovery recoveryname.img
And then download this file:
Link!
And then access in recovery mount storage and copy that .zip file on your phone Clear and wipe everything except battery stats..And then flash that .zip file
genaddiy said:
Thank you very much for your help.
I've did the steps as you say, and finally was able to "see" my phone in fastboot from PC.
but the CID I am getting is 11111111 , and there is no backup that matches it.
Can I overwrite it with some kind of rom ? I don't care to loose all the data, just to get a working phone.
Click to expand...
Click to collapse
You are S-OFF you can install any RUU try with THIS ONE lock the bootloader and run the RUU as Administrator
post result from command fastboot getvar all and delete your S/N and IMEI from the info for any case
---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------
big noob said:
Download clockwordmod recovery img file And flash it via Fastboot..
Fastboot flash recovery recoveryname.img
And then download this file:
Link!
And then access in recovery mount storage and copy that .zip file on your phone Clear and wipe everything except battery stats..And then flash that .zip file And try to flash it
Click to expand...
Click to collapse
He can't install OTA from recovery and you can't install OTA from recovery!!!!
Hi Thant, thank you for your help.
So you are saying that big noob's method won't work ?
I've downloaded the RUU, but I did not understand what you've meant by : "lock the bootloader" and when should I post the results of "fastboot getvar all" ? after I run the RUU , or before ?
You should post it before RUU..Well i tryed my method before and .zip flashed successfully..
And you can relock it with this command:
fastboot oem lock
Here's what I've got, no what should I do with it ?
>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.12.0000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.2
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3821mV
(bootloader) devpower: 47
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.830s
You can relock your bootloader download RUU and run it as administrator
I tried to relock , but it said phone is already locked.
Then I ran RUU and got the following error :
ERROR [159] - The ROM update utility cannot update your Android phone. Please get the correct ROM Update Utility and try again .
But what is the correct for me ? and where do I get it ?
genaddiy said:
I tried to relock , but it said phone is already locked.
Then I ran RUU and got the following error :
ERROR [159] - The ROM update utility cannot update your Android phone. Please get the correct ROM Update Utility and try again .
But what is the correct for me ? and where do I get it ?
Click to expand...
Click to collapse
Try this one
And when you in bootloader what is writen up RELOCKED and ENDEAVORU XE or ENDEAVORU PVT
98552432 231
In the bootloader it says :
*** LOCKED *****
ENDEAVORU XE SHIP S-OFF RL
genaddiy said:
In the bootloader it says :
*** LOCKED *****
ENDEAVORU XE SHIP S-OFF RL
Click to expand...
Click to collapse
ENDEAVORU XE have problems with update you must manually update the firmware and after this to install RUU or custom rom.
Download THIS OTA open the zip and extract firmware.zip to your fastboot folder after this do this
Type: fastboot oem rebootRUU and wait for device to reboot you will see HTC logo
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
I want to thank you for your patience with a noob like me
I did everything till the last line.
After flashboot reboot, my phone passed the first htc logo that it was stuck on , but now it's stuck on htc one screen (the one with beats audio logo at the bottom) .
Do I need to do the flash custom rom recovery ?
genaddiy said:
I want to thank you for your patience with a noob like me
I did everything till the last line.
After flashboot reboot, my phone passed the first htc logo that it was stuck on , but now it's stuck on htc one screen (the one with beats audio logo at the bottom) .
Do I need to do the flash custom rom recovery ?
Click to expand...
Click to collapse
yes now flash custom recovery philz 5.15.x mount usb storage copy custom rom to the phone install and flash the boot.img and you will have working rom sense or no sense. Now after flash the firmware what is your hboot version 1.39? If yes you are ready to go
ok , just to make sure I understand before I do it a screw something up :
"yes now flash custom recovery philz 5.15.x mount usb storage copy custom rom to the phone install and flash the boot.img and you will have working rom sense or no sense. Now after flash the firmware what is your hboot version 1.39? If yes you are ready to go"
my hboot version is indeed 1.39
so I d/l philz custom recovery .
no I should :
fastboot flash zip philz_touch_6.07.9-endeavoru.zip
then go to the custom recovery ? (how ? ? ? )
then d/l some custom rom (any recomendations ? just a good stable one, possibly stock)
then copy it to phone using fastboot
and then , from custom recovery flash it ?
I'm sorry for all these questions, but I'm afraid to touch the damn thing already ))))
Flash the recovery (its a img file NOT a zip, take out the img if its in the zip)
Fastboot flash recovery recoveryname.img
Fastboot erase cache
Enter the recovery by selecting FASTBOOT in the bootloader and then RECOVERY (navigate with the volume buttons and confirm with the power button)
Go to the mounts and storage menu and mount the sdcard as a mass storage disk (wait a few minutes until it pops up on the pc)
Copy the rom.zip to the sdcard. Take out the boot.img and flash it via fastboot
Fastboot flash boot boot.img
Fastboot erase cache
Enter recovery again and perform a full wipe
Factory reset
Wipe cache partition
Advanced-wipe dalvik cache
Mounts and storage-format cache, data and system
Install the rom.zip
Done !
Roms....just check the android dev section. Many roms to choose and read up for yourself. It's not that difficult ...maximus and arhd are very close to stock.
Thank you for the detailed reply !
When doing Fastboot flash recovery recoveryname.img I got the messege :
FAILED <remote : not allowed>
Is the problem that my phone is locked ? (written locked at the top of fastboot screen) tried to do fastboot oem unlock but getting "Command error !" .
I saw this solution : http://forum.cyanogenmod.com/topic/74316-a-solution-to-fastboot-flash-recovery-not-allowed-error/ , but I'm not sure it will fit my phone (as it talkes about a different one) and what is a PD98IMG.zip file ?
Hi,
I awoke this morning to have my One reboot on me, only to have it hang at the green HTC logo.
I need help getting it functional again, asap.
I'm s-off and rooted.
What I can do:
Boot to bootloader and use fastboot commands - but
Code:
fastboot reboot oem rebootRUU
does not boot to the black HTC screen, but back to the green HTC logo, so I'm unable to flash a RUU.
What I can't do:
Use adb commands
Boot to recovery - freezes at teamwin screen. However, when the phone is stuck at the teamwin screen, I seem to be able to use adb - if I get here, I can reboot to the bootloader with adb.
Boot to system - hangs at the green HTC startup logo.
What I've tried:
Using fastboot to flash a new recovery to restore the backup I should have - still hangs at teamwin screen
Is there anything that can be done to fix this, or is my phone a lost cause?
can you get to hboot by holding vol- and power for a bout 30 sec?
Yes, that's how I'm able to get the fastboot stuff working.
After further investigation, it seems nothing I do persists on the phone. I attempted to flash the stock recovery to attempt another factory reset, but it still attempts to boot to TWRP.
axeseven said:
After further investigation, it seems nothing I do persists on the phone. I attempted to flash the stock recovery to attempt another factory reset, but it still attempts to boot to TWRP.
Click to expand...
Click to collapse
i would RUU to get back to a working phone.
by any chance did you make a backup of you internal storage because ruu will format it.
EDIT:
are you s-off and unlocked?
Yes to both - but how can I flash a RUU? When I run the fastboot oem rebootRUU command it does not boot to the usual black/silver HTC screen, instead the normal green startup logo.
before you said you did command:
Code:
fastboot reboot oem rebootRUU
the actual command is:
Code:
fastboot oem rebootRUU
also make sure RUU is the only capital letters
when i fastboot, if you type:
Code:
fastboot devices
what is the output ??
Unfortunately, that has the same result - stuck at the green HTC boot logo.
EDIT:
After sitting at this screen for awhile, it booted into what looks like the stock rom, asking for a password to decrypt the storage. I don't recall ever setting a password for this, and even if I did, I stopped using the stock rom almost as soon as I got the phone.
Code:
fastboot devices
outputs the serial number and that it's in fastboot:
Code:
-serial number here- fastboot
axeseven said:
Unfortunately, that has the same result - stuck at the green HTC boot logo.
Click to expand...
Click to collapse
make sure the pc can see fastboot on the device with command:
Code:
fastboot devices
if output looks like this:
C:\>fastboot devices
FA38PS904782 fastboot
you should be able to type:
Code:
fastboot flash zip nameofruu.zip
and it will start to process.
---------- Post added at 01:17 PM ---------- Previous post was at 01:10 PM ----------
axeseven said:
Unfortunately, that has the same result - stuck at the green HTC boot logo.
EDIT:
After sitting at this screen for awhile, it booted into what looks like the stock rom, asking for a password to decrypt the storage. I don't recall ever setting a password for this, and even if I did, I stopped using the stock rom almost as soon as I got the phone.
Code:
fastboot devices
outputs the serial number and that it's in fastboot:
Code:
-serial number here- fastboot
Click to expand...
Click to collapse
yay, this means fastboot is talking to the phone. thats odd that storage is encrypted. can you still use the phone to get to settings?
synisterwolf said:
yay, this means fastboot is talking to the phone. thats odd that storage is encrypted. can you still use the phone to get to settings?
Click to expand...
Click to collapse
Unfortunately, no. I just get an option to decrypt the storage with a password or make an emergency call. I'm about to attempt to flash the ruu .zip without booting into rebootRUU, unless there is something else I can do.
did you use a kernel or recovery with F2FS?
Not to my knowledge, no. When trying to flash the ruu without rebootRUU I get the following:
Code:
C:\>fastboot flash zip PN07IMG_M7_WL_JB_50_VZW_1.10.605.15_DECRYPT.ZIP
sending 'zip' (1178528 KB)...
OKAY [ 55.707s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 55.762s
and just so it's here, when I fastboot getvar:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.12.42.1104
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.605.15
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -serialnumberhere-
(bootloader) imei: -imeihere-
(bootloader) meid: -meidhere-
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4309mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fb8d0c81
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Are you still stuck?
hawknest said:
Are you still stuck?
Click to expand...
Click to collapse
Yes, flashing the ruu didn't work.
Have you tried flashing recovery again ?.
Try flashing philz recovery . Make sure it's m7wlv version
rename to recovery.img and add to platform tools folder
fastboot flash recovery recovery.img
fastboot erase cache
Try rebooting into recovery
hawknest said:
Have you tried flashing recovery again ?.
Try flashing philz recovery . Make sure it's m7wlv version
rename to recovery.img and add to platform tools folder
fastboot flash recovery recovery.img
fastboot erase cache
Try rebooting into recovery
Click to expand...
Click to collapse
I can't seem to find a version of Philz recovery for m7wlv. Am I correct in thinking I need the m7vzw version from https://goo.im/devs/philz_touch/CWM_Advanced_Edition/m7vzw/ here?
You are on older firmware, have you tried flashing newer firmware and see if ruu mode works after flashing firmware? You are s-off, so you can downgrade when you ruu.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
You are on older firmware, have you tried flashing newer firmware and see if ruu mode works after flashing firmware? You are s-off, so you can downgrade when you ruu.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
This is worth a shot, I guess. Is there any particular version of the firmware or might any newer than 1.10.605.15 work?
EDIT:
After trying this, I get the same remote:not allowed error as above.
Additionally, after flashing philz recovery - which the console says is successfully flashed, when I reboot to recovery, it still hangs at the blue teamwin logo as before.
axeseven said:
I can't seem to find a version of Philz recovery for m7wlv. Am I correct in thinking I need the m7vzw version from https://goo.im/devs/philz_touch/CWM_Advanced_Edition/m7vzw/ here?
Click to expand...
Click to collapse
Yeah the bottom one .. sorry . M7wlv is the official name but yeah that one
Revamped 2.0 Lunar 4.4.3
---------- Post added at 10:29 PM ---------- Previous post was at 10:27 PM ----------
Here's the latest ruu for s-off http://forum.xda-developers.com/showthread.php?p=52987679
Revamped 2.0 Lunar 4.4.3
That was the one I tried, to no success. After flashing it and clearing the cache, when I boot to recovery it still sits at a blue teamwin screen.
Sorry about any terminology...
Recently my htc one m8 stopped booting. I had rooted it a long time ago and had a ROM that was working fine for a long time. No recent changes.
On normal boot it sits on the white and green text 'htc' forever.
If I boot with power+down buttons I get to a hboot screen, but choosing 'recovery' takes me to a white screen small pink 'Entering Recovery' text. Nothing happens. To even get power+down screen to be available I had to move two zip files from root of sdcard which I guess were related to the custom rom, being 0P6BIMG.zip and M8-GPE-03-16-2015.zip
I tried reinstalling twrp after downloading the latest .img file
fastboot command
c:\twrp>fastboot flash recovery twrp-3.0.2-0-m8.img
just says <waiting for device> whether on pink text screen or white 'htc'
I can see the sdcard through a pc card reader and manipulate files. Is there any way to copy files manually so it will boot?
This is on Win 10, UK unlocked version of phone.
bt999 said:
To even get power+down screen to be available I had to move two zip files from root of sdcard which I guess were related to the custom rom, being 0P6BIMG.zip and M8-GPE-03-16-2015.zip
Click to expand...
Click to collapse
When you have a file named 0P6BIMG.zip, it will automatically try to install it every time you enter bootloader. Its an update or RUU of some sort, placed there by you, but exactly what is impossible to tell.
The other file is a ROM zip for a GPE ROM, which I would guess is the custom ROM you installed. It doesn't make a difference for this file not be on the SD card or not (bootloader will not try to install it automatically, and bootloader will function normally).
bt999 said:
I tried reinstalling twrp after downloading the latest .img file
fastboot command
c:\twrp>fastboot flash recovery twrp-3.0.2-0-m8.img
just says <waiting for device> whether on pink text screen or white 'htc'
Click to expand...
Click to collapse
Are you in bootloader-fastboot mode when you run the command (which is required)? Meaning, FASTBOOT should be highlighted in red just under the green text on the bootloader screen. If not, just select using the vol buttons, and confirm using power button.
Fastboot clarification
redpoint73 said:
When you have a file named 0P6BIMG.zip, it will automatically try to install it every time you enter bootloader. Its an update or RUU of some sort, placed there by you, but exactly what is impossible to tell.
The other file is a ROM zip for a GPE ROM, which I would guess is the custom ROM you installed. It doesn't make a difference for this file not be on the SD card or not (bootloader will not try to install it automatically, and bootloader will function normally).
Are you in bootloader-fastboot mode when you run the command (which is required)? Meaning, FASTBOOT should be highlighted in red just under the green text on the bootloader screen. If not, just select using the vol buttons, and confirm using power button.
Click to expand...
Click to collapse
Thanks for your reply.
I guess the 0P6BIMG.zip file would explain why it was always slow to boot when things were working ok, if it was being reinstalled each time. I don't recall its purpose.
I wasn't in bootloader-fastboot mode when trying the fastboot command, but have tried it again.
When connected to an Ubuntu 16.04 machine the white on red text says 'fastboot usb', but ubuntu commandline fastboot flash ... gives same 'waiting for device'. When connected to Win 10 white/red text just says 'fastboot', if that is relevant. When I installed fastboot on Win 10 from instructions at http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 there is a note to remove Google drivers before installing new ones - I did not do this, not sure if relevant, but new driver install gave no errors.
Is there a way to copy a new ROM image to the sdcard so that on 'normal' booting it gets detected and applied? Or to copy twrp somewhere manually?
Is there a log file that would show how far through the normal boot things get? I guess it is inaccessible until things work better.
bt999 said:
I wasn't in bootloader-fastboot mode when trying the fastboot command, but have tried it again.
When connected to an Ubuntu 16.04 machine the white on red text says 'fastboot usb', but ubuntu commandline fastboot flash ... gives same 'waiting for device'. When connected to Win 10 white/red text just says 'fastboot', if that is relevant. When I installed fastboot on Win 10 from instructions at http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 there is a note to remove Google drivers before installing new ones - I did not do this, not sure if relevant, but new driver install gave no errors.
Click to expand...
Click to collapse
Try going into Windows Device Manager, finding the device, and picking the option to manually select drivers, and select the generic Android MTP drivers. See if that helps fastboot connect.
Make sure you have HTC drivers (HTC Sync) installed as well. Try to re-install HTC Sync.
bt999 said:
Is there a way to copy a new ROM image to the sdcard so that on 'normal' booting it gets detected and applied? Or to copy twrp somewhere manually?
Click to expand...
Click to collapse
You can't flash a ROM, if TWRP isn't working properly. And there isn't a way to make one automatically flash upon normal boot, that I am aware.
I've seen some folks make 0P6BIMG.zip files for TWRP, which will install automatically when you boot to bootloader. But honestly, USB fastboot connectivity is a pretty vital thing to have working, and usually just a matter of right drivers and a good cable (and being in fastboot mode is a must), so shouldn't be that hard to troubleshoot.
Old twrp
redpoint73 said:
Try going into Windows Device Manager, finding the device, and picking the option to manually select drivers, and select the generic Android MTP drivers. See if that helps fastboot connect.
Make sure you have HTC drivers (HTC Sync) installed as well. Try to re-install HTC Sync.
You can't flash a ROM, if TWRP isn't working properly. And there isn't a way to make one automatically flash upon normal boot, that I am aware.
I've seen some folks make 0P6BIMG.zip files for TWRP, which will install automatically when you boot to bootloader. But honestly, USB fastboot connectivity is a pretty vital thing to have working, and usually just a matter of right drivers and a good cable (and being in fastboot mode is a must), so shouldn't be that hard to troubleshoot.
Click to expand...
Click to collapse
I have got a twrp running, unfortunately it says it is only compatible with bootloader 3.19 and above when I try to install the rom. I have 3.16.
Do you know where I can get an old twrp?
Thanks.
bt999 said:
I have got a twrp running, unfortunately it says it is only compatible with bootloader 3.19 and above when I try to install the rom. I have 3.16.
Do you know where I can get an old twrp?
Thanks.
Click to expand...
Click to collapse
https://dl.twrp.me/m8/
twrp versions
xunholyx said:
https://dl.twrp.me/m8/
Click to expand...
Click to collapse
Thanks. I have now tried
twrp-2.7.0.1-m8.img twrp-2.7.1.0-m8.img twrp-2.8.7.0-m8.img
twrp-2.7.0.2-m8.img twrp-2.8.0.0-m8.img twrp-3.0.2-0-m8.img
The oldest ones don't run the newer ones work but I still get an error on attempting to install the custom ROM. I think I may be misinterpreting the error message. I now think it is telling me the custom ROM needs bootloader 3.19, rather than twrp not being able to run, i.e. twrp knows not to install the rom.
Message 'This package supports bootloader(s): 3.19.0.0000; this device has bootloader 3.16.0.0000'
Do you know how I can update my bootloader?
bt999 said:
Do you know how I can update my bootloader?
Click to expand...
Click to collapse
Post fastboot getvar all result without serial & imei no.
Without proper info, everyone is guessing what you actually need.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I found this thread http://forum.xda-developers.com/showthread.php?t=2696282 and went through the process with a zip linked from there , but I guess it was old and turned out to still be 3.16
Shouldn't HTC be distributing these files? Or my carrier?
You need to relock bootloader if not yet done.
Command :
fasboot oem lock
fastboot reboot-bootloader
Then follow this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Put both files in your adb/fastboot folder.
(The guide was written for system-wide adb/fastboot)
Once completed, you can re unlock boorloader and install latest TWRP and install any ROM that you like, if you want to.
I have a working phone now, htc setup screens ended up with no google account prompts or apps, so I installed cwm nightlies and open-gapps hoping I would have full functionality, however gapps was rejected for not having enough internal storage.
I don't care whether htc or cwm but need gapps/play store. Is there anything you can suggest?
/Last reply lost..]I now have a working phone with cwm nightlies. Unfortunately open-gapps wont install saying not enough space on internal drive.
Any suggestions on how to clear space or to make HTC install Google accounts/store (it did not ask)?
I have a working phone now.
RUU didn't install google app store, so I installed cwm nightlies. I got an error that there was not enough space on internal for open-gappps.
Is there a way to free up space?
bt999 said:
I have a working phone now.
RUU didn't install google app store, so I installed cwm nightlies. I got an error that there was not enough space on internal for open-gappps.
Is there a way to free up space?
Click to expand...
Click to collapse
I have no idea what cwm nightlies is ... but if you have this kind of error not enough internal space ... you need to format data (not wipe) in TWRP.
Install latest TWRP, select wipe - format data - yes ... reboot to recovery again, now you can install ROM.
Solved
ckpv5 said:
I have no idea what cwm nightlies is ... but if you have this kind of error not enough internal space ... you need to format data (not wipe) in TWRP.
Install latest TWRP, select wipe - format data - yes ... reboot to recovery again, now you can install ROM.
Click to expand...
Click to collapse
I installed a mini gapps that had just Play Store then installed other apps manually through that.
Thank you all for your help, this is a well-informed forum.
For anyone reading one thing I learned was to run fastboot from Ubuntu/Linux with 'sudo' or else it will not connect, just says 'waiting for device'
ckpv5 said:
I have no idea what cwm nightlies is
Click to expand...
Click to collapse
He means CM, not CWM. Easy mistake to make (adding one letter) but the two are completely different things (Cyanogen Mod custom ROM versus Clockwork Mod custom recovery).
SOLVED
twrp 3.0.2-22 solution
Reinstall fastboot and oneplus drivers
DaniMarqz said:
oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Have console: false
(bootloader) Selinux type: <none>
(bootloader) Boot_mode: normal
(bootloader) Kmemleak_detect: false
(bootloader) force_training: true
adb shows no device, i flashed twrp 3 times and it doesnt go into it, im stuck in fastboot mode, what can i do?
Cant flash twrp recovery, cant flash factory recovery
Click to expand...
Click to collapse
You don't use adb in fastboot. Are you trying to do adb commands? Do fastboot flash recovery ”name of your recovery image" without the quotations.
Sent from my OnePlus 3 using XDA Labs
flash twrp 3.0.2-22, If that does not work. make sure your phone is off and place it into Qualcomm qhsusb_dload 9008 mode by turning off the device and then holding the vol. up button for ten seconds and then connecting your usb cable to a computer. On your computer, run the program OnePlus3_Unbrick_Tool_Full.
dustin_b said:
You don't use adb in fastboot. Are you trying to do adb commands? Do fastboot flash recovery name of your recovery image" without the quotations.
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
This
I was in the same situation last yesterday. I used the fastboot commands to push the modified TWRP to my 3 and was able to boot into recovery.
Suggestion. Before flashing change the name of the twrp recovery to "recovery.img" Makes typing the commands much easier. "fastboot flash recovery recovery.img"
JonatasSfredo said:
Reinstall fastboot and oneplus drivers
Click to expand...
Click to collapse
how do i reinstall fastboot? i already reinstalled 1+ drivers
DaniMarqz said:
how do i reinstall fastboot? i already reinstalled 1+ drivers
Click to expand...
Click to collapse
Search fastboot drivers on Google
jim262 said:
flash twrp 3.0.2-22, If that does not work. make sure your phone is off and place it into Qualcomm qhsusb_dload 9008 mode by turning off the device and then holding the vol. up button for ten seconds and then connecting your usb cable to a computer. On your computer, run the program OnePlus3_Unbrick_Tool_Full.
Click to expand...
Click to collapse
I LOVE YOU modified twrp worked!! thank you so much!!!!!!! i didnt know that it existed, i was trying with official twrp :/
Glad it worked!
Motorola Moto G Power (2022)
XT2165-5 US Retail Variant
Codename: Tonga
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rooting GuideOVERVIEW:
This guide outlines simple step-by-step instructions for rooting the Moto G Power (2022). To alleviate some of the legwork, and to cater this guide to new and inexperienced members, I have provided boot images pre-patched for the Magisk v26.1 systemless root solution. In addition, for those members who prefer the Android 11 stock ROM over Android 12, I am providing patched boot images for both the Android 11 and Android 12 firmware builds. (It has been reported that upgrading to Android 12 breaks Widevine L1 and reverts to Widevine security level L3.)
When downloading a patched boot image per the below instructions, be sure to choose the boot image that corresponds with both your installed Android version and firmware build number.
COMPATIBILITY:
The supplied Magisk patched boot images in the downloads section below are from both the Android 11 and Android 12 based firmware builds for the XT2165-5 US Retail Tonga variant. In theory, these boot images may work on rooting other variants as well, but I have only tested them on the referenced retail variant. To ensure compatibility, unless you are rooting this particular retail variant, procure the boot image from your variant and firmware build. Tonga official firmware for all carrier models and variants is available from the Lolinet repo here Tonga Official Firmware: Lolinet Repo
PREREQUISITES:
In order to root your Moto G Power (2022), you will need an unlocked bootloader and a Windows PC or laptop with the ADB & fastboot tools installed. I have included a link in the downloads section below for the latest Minimal ADB & Fastboot tools for Windows. This procedure can be carried out on a Mac or Linux setup as well; however, for purposes of this guide, I will focus on a Windows setup. Windows 7/8.1/10/11 will suffice. You will also need the factory supplied, or a quality equivalent USB-A to USB-C syncing/charging cable.
If you have not yet unlocked your bootloader, head on over to this tutorial and do so.
Motorola Bootloader Unlocking Tutorial
Please be sure and thank XDA Recognized Contributor @sd_shadow for his comprehensive and easy-to-follow tutorial on bootloader unlocking Motorola mobile devices. It is, hand down, the most thorough and detailed guide on this procedure, and is highly recommended to those members who are unfamiliar with the topic.
Keep in mind that not all carrier variants of the Tonga are supported for bootloader unlocking. For example, if you own the Verizon, AT&T or TracFone branded Moto G Power (2022), among some other carrier variants, your bootloader is not officially supported for unlocking and, as such, rooting may not to be an option. However, it should be noted that most MediaTek chipset models can be exploited by a reverse engineering tool called MTK Client which, among many other things, can force the bootloader into an unlocked state. Whether the MTK Client exploit can be used on any of these locked down Tonga models & variants is unknown to me. It wouid, perhaps, be worth researching more if you own such a variant of the Tonga.
The tutorial link I provided above will help you make the determination as to whether your variant is officially supported for unlocking. If you own a Retail variant, your bootloader can be unlocked via Motorola's official support portal. Again, the link I posted above will guide you in this regard. Simply return here once you have successfully unlocked your bootloader.
ANDROID VERSIONS & FIRMWARE BUILDS
The boot images provided in the downloads section below have been patched with Magisk v26.1 for systemless root support. The Android 11 boot image corresponds with the last official firmware released prior to the Android 12 update rollout. The patched boot image for Android 12 corresponds with the latest firmware build available for the Tonga at the time of posting. Specifically,
The Android 11 boot Image corresponds with firmware build no. RRQS31.03-68-153-2
The Android 12 boot image corresponds with firmware build no. S3RQ32.20-42-10-9-4
To prevent boot loops, bugs and potential issues with compatibility, flash only a patched boot image that matches the firmware version presently installed on your Tonga. Hence, if your installed firmware build version differs from the version of the patched boot image referenced above, it is highly advised that you obtain a stock boot image that corresponds with your firmware version, patch the image with the latest Magisk app, then flash it to your Tonga via the fastboot commands outlined below.DISCLAIMER:
Rooting an Android-based mobile device is a task that encompasses inherent risks. Failure to follow the instructions as written, for example, could result in your device being rendered inoperable, stuck in a boot loop, etc. Rooting will also void any active Motorola warranty you may have on your smartphone. (However, as set forth on the Motorola support portal, your warranty is void once you complete the bootloader unlocking procedure.)
By proceeding further, you are assuming full responsibility and sole liability for the integrity and operability of your Moto G Power (2022). I am hereby absolved of any responsibility or civil liability in the event something goes wrong. Follow the instructions carefully, employ some patience, and things should go smoothly. I encourage members to read this guide in its entirety PRIOR to actually starting the steps.
INSTRUCTIONS:
Download the Minimal ADB & Fastboot tools from the link below and install it on your Windows PC or laptop. Next, open Windows File Explorer, open This PC and double click on your C: drive. Locate and open the Program Files x86 folder and locate the Minimal ADB & Fastboot folder. Copy the folder and paste it to your desktop. (Copying the folder to your desktop is not mandatory, but is recommended. This configures your ADB & Fastboot directory to a more convenient location from which to work.);
Download the Motorola Device Manager software from the link below, in accordance with your Windows OS architecture (32 or 64 bit), and install it on your PC or laptop. This software installs the most current USB device drivers for your Moto device;
Download the patched boot image below that corresponds with the Android OS & firmware build version currently running on your device. Save the image inside the ADB & Fastboot directory on your PC or laptop;
Boot your device into AP Fastboot Mode by first powering off your smartphone and then pressing Power + Volume Down simultaneously for about 8 seconds, or until AP Fastboot Mode appears on your phone display;
Connect your Tonga to your Windows computer using the OEM supplied, or a quality equivalent USB-A to USB-C data syncing/charging cable;
Open the Minimal ADB & Fastboot folder you copied to the desktop in Step 1. Double click the cmd-here file to launch a command window;
To verify proper fastboot communication between your phone and computer, execute this command:
Code:
fastboot devices
If properly connected, the command window will return with an alphanumeric string that corresponds with your device serial number;
If your serial number isn't displayed, or if you receive a Waiting message, there is an issue with fastboot mode communication between your phone and PC/laptop. Try changing USB ports, try another data syncing cable, and/or update the fastboot drivers on your PC or laptop. If your phone remains unrecognized by fastboot, skip down to the next section titled Fix Fastboot Recognition Issues, and follow those steps.
Once a proper connection has been verified, it's time to flash the patched boot image to your phone. Execute this command:
Code:
fastboot flash boot patched_boot.img
Take note that the patched boot images linked below are both named patched_boot.img. These instructions assume that you leave the filename unchanged.
Upon reboot to the Android OS, go to your app drawer and open the Magisk app or its placeholder stub. Grant any permissions requested, and follow any prompts to upgrade Magisk to the full version and complete setup of the root environment. Magisk may reboot your device to finalize the setup. If you do not see the Magisk app or the stub, download the Magisk v26.1 APK from the official Magisk GitHub repo I have linked below, and install it on your Tonga.
That's it. You should now be rooted via the Magisk systemless root solution.
FIX FASTBOOT RECOGNITION ISSUES:
This section is provided to assist members with troubleshooting device recognition issues via fastboot mode. If you have already tried a different USB-A to USB-C data syncing/charging cable, as well as a different USB port, and your Tonga persists to be unrecognized in fastboot mode, follow these steps:
Keeping your device connected to your Windows PC/laptop from Step 8 above, and ensuring your device is still in fastboot mode, right click your Windows Start icon and select Device Manager. Locate your Tonga in the menu. It will likely be located under either the Portable Devices or Android Device heading;
Right click your device and select Update Driver. Next, select Browse My Computer for Drivers. On the next screen choose the option for Let Me Pick From a List... Now you will see a list of drivers to select from. Depending on the manner in which Windows recognized your Tonga in the Device Manager menu, the driver selection list can vary. If you see an option for Android Device or Android Phone, select either option, and then select either Android Composite ADB Interface or Android Bootloader Interface. Or, you may be directly presented with options for Android Bootloader Interface, Android ADB Interface and Android Composite ADB Interface. In any event, choose Android Composite ADB Interface or, in the alternative, Android Bootloader Interface, and then click Next. Click Yes in the Update Driver Warning dialogue screen, at which time the drivers will be installed.
Return to your command window and again execute the fastboot devices command. If your serial number is displayed, your drivers are now properly installed. Return to the instructions in the previous heading and proceed to Step 9.
DOWNLOADS:
• Motorola Device Manager V2.5.4
• Minimal ADB & Fastboot Tools v1.4.3
• Official GitHub Magisk Releases
• Patched boot.img (Android 11 Stock OS)
• Patched boot.img (Android 12 Stock OS)
• Official Tonga Firmware / All Variants
THANKS & MENTIONS:
A big thanks to @sd_shadow for his excellent tutorial on Unlocking/Relocking Motorola bootloaders. Also, thanks to @jhjhjhjhjhjh for his comprehensive thread on the Moto G Power (2022), packed with specs, general info, mods & some other valuable resources for Tonga owners. Check out his thread here Moto G Power (2022)
Last but not least, a big thanks to @Needsimunlocked, for Magisk patching and sharing the stock boot image corresponding with firmware build S3RQ32.20-42-10-9-4. My Tonga is presently hard bricked, so this was of great help in my efforts to keep this guide up to date with a patched boot image from the latest available firmware package.
Nice detailed Guide! Just want to point out that you don't need to flash boot a and b with magisk. Just fastboot flash boot boot.img.
Also, Updating to 12 will break widevine L1. If you don't mind L3, go ahead. Personally it pisses me off.
Every version of firmware has the same apps on it. They're all full of carrier apps and bloat so flashing retail firmware won't change anything like the older Moto phones. I personally have deleted maybe 200 apps from stock including their corresponding overlays. If you use EX kernel manager there is a Hexicore mode on a12. You won't find this on other kernel managers. Also, I suggest deleting the live wallpaper app as it will make the device ridiculously slow
Yeedatoy said:
Nice detailed Guide! Just want to point out that you don't need to flash boot a and b with magisk. Just fastboot flash boot boot.img.
Also, Updating to 12 will break widevine L1. If you don't mind L3, go ahead. Personally it pisses me off.
Every version of firmware has the same apps on it. They're all full of carrier apps and bloat so flashing retail firmware won't change anything like the older Moto phones. I personally have deleted maybe 200 apps from stock including their corresponding overlays. If you use EX kernel manager there is a Hexicore mode on a12. You won't find this on other kernel managers. Also, I suggest deleting the live wallpaper app as it will make the device ridiculously slow
Click to expand...
Click to collapse
Great feedback. Thanks for sharing. I believe my next project will be fully debloating.a retail firmware package and then posting a guide for installing it via fastboot. Yes, I agree that flashing to boot_a & boot_b is not required. However, I have encountered instances where members are using way outdated fastboot binaries that don't automatically flash the active slot, so I got into the habit of instructing for both slots as a precaution. ( Even though I do provide a link for a fairly recent fastboot binary, not every member follows instructions.)
That's good info on Widevine L1 breaking on the Windows 12 update. I sure didn't know that. Thanks for the tip on a12 EX Kernel Manager as well.
Thanks again for your valuable feedback & input. I'll certainly use this info on my debloated firmware project, including that cursed live wallpaper app. Hate that RAM consuming thing.
In fact, if you could dump a super.img on your debloated setup, I would of course credit the work to you in my upcoming guide. Thanks again.
.im following everything to the T but when i flash patched_boot.img i get
i also tried flashing it while on the previous fastboot screen , and i get the same but the fail reason is no such file or directory
im using the patched boot img supplied on post for android 12
how do i fix this?
keezeysqueezey said:
.im following everything to the T but when i flash patched_boot.img i get
View attachment 5878959
i also tried flashing it while on the previous fastboot screen , and i get the same but the fail reason is no such file or directory
im using the patched boot img supplied on post for android 12
Click to expand...
Click to collapse
No such file
Viva La Android said:
No such file
Click to expand...
Click to collapse
Seems like an error with the fastboot path. But out of curiosity, what version of fastboot are you using? And I do need to ask, are you certain that your bootloader is in an unlocked state?
Viva La Android said:
Seems like an error with the fastboot path. But out of curiosity, what version of fastboot are you using? And I do need to ask, are you certain that your bootloader is in an unlocked state?
Click to expand...
Click to collapse
not sure fastboot version ? whichever comes on moto g power , and yes bootloader is unlocked 100%
keezeysqueezey said:
not sure fastboot version ? whichever comes on moto g power , and yes bootloader is unlocked 100%
Click to expand...
Click to collapse
I meant, did you install the Minimal ADB & Fastboot tools from the link I provided, or are you using another configuration of tools?
well the minimal fastboot u posted says corrupted , but im using the same version from elsewhere ...wait a sec....leme try something....... ok so, if i try to open the patched boot img , it also says corrupted
keezeysqueezey said:
well the minimal fastboot u posted says corrupted , but im using the same version from elsewhere ...wait a sec....leme try something....... ok so, if i try to open the patched boot img , it also says corrupted
Click to expand...
Click to collapse
You can't open an Android boot.img using the native Windows File Explorer. You need an image extractor such as Carliv Image Kitchen or SuperR's Kitchen. Also, both patched boot images have been thoroughly tested and verified with md5 checksums. I double-checked all files available on the links I posted. No files are corrupt.
I just downloaded and installed the Minimal ADB & Fastboot tools from my link as well with no problems.Not sure why it's showing corrupt on your system.
Ok, did you follow Step 1 entirely and copy the Minimal ADB & Fastboot folder from your C: drive and paste it to your desktop? This is the folder where you must save the patched boot image you downloaded from the link I provided.
While connected in fastboot mode, execute the following command and post the command prompt output here.
Code:
fastboot getvar all
This will let me know why fastboot is returning an Invalid partition name for the /boot partition.
< waiting for device >
(bootloader) cpu-abi:arm64-v8a
(bootloader) snapshot-update-status:none
(bootloader) super-partition-name:super
(bootloader) is-logical: preloader_raw_b:no
(bootloader) is-logical: preloader_raw_a:no
(bootloader) is-logical: vendor_boot_a:no
(bootloader) is-logical : vendor_boot_b:no
(bootloader) is-logical: para:no
(bootloader) is-logical: misc:no
(bootloader) is-logical: boot_b:no
(bootloader) is-logical: metadata:no
(bootloader) is-logical: userdata:no
(bootloader) is-logical: mmcblk0:no
(bootloader) is-logical: boot_a:no
(bootloader) is-logical: md_udc:no
(bootloader) is-logical: super:no
(bootloader) is-logical: system_ext_a:yes
(bootloader) is-logical: product_a:yes
(bootloader) is-logical: vendor_a:yes
(bootloader) is-logical:system_a:yes
(bootloader) is-logical:system_ext_a-cow:yes
(bootloader) is-logical: product_a-cow:yes
(bootloader) is-logical: vendor_a-cow:yes
(bootloader) is-logical: system_a-cow:yes
(bootloader) battery-voltage:0
(bootloader) treble-enabled:true
(bootloader) is-userspace:yes
(bootloader) partition-size:reloader_raw_b:0x3FF800
(bootloader) partition-size:reloader_raw_a:0x3FF800
(bootloader) partition-size:vendor_boot_a:0x4000000
(bootloader) partition-size:vendor_boot_b:0x4000000
(bootloader) partition-size: para:0x80000
(bootloader) partition-size: misc:0x80000
(bootloader) partition-size: boot_b:0x2000000
(bootloader) partition-size: metadata:0x2000000
(bootloader) partition-size: userdata:0xC26CF8000
(bootloader) partition-size: mmcblk0:0xE8F800000
(bootloader) partition-size: boot_a:0x2000000
(bootloader) partition-size: md_udc:0x169A000
(bootloader) partition-size: super:0x220000000
(bootloader) partition-size: system_ext_a:0x36CD4000
(bootloader) partition-size: product_a:0x13312B000
(bootloader) partition-size: vendor_a:0x1F6DB000
(bootloader) partition-size: system_a:0x3B5BF000
(bootloader) partition-size:system_ext_a-cow:0x132EB000
(bootloader) partition-size: product_a-cow:0x12DF6000
(bootloader) partition-size: vendor_a-cow:0x13FD1000
(bootloader) partition-size: system_a-cow:0x213B5000
(bootloader) version-vndk:31
(bootloader) has-slot: preloader_raw:yes
(bootloader) has-slot: vendor_boot:yes
(bootloader) has-slot: para:no
(bootloader) has-slot:hw:no
(bootloader) has-slot: prodpersist:no
(bootloader) has-slot: utagsBackup:no
(bootloader) has-slot: cid:no
(bootloader) has-slot: misc:no
(bootloader) has-slot:l ogs:no
(bootloader) has-slot:frp:no
(bootloader) has-slot:boot:yes
(bootloader) has-slot:metadata:no
(bootloader) has-slot:utags:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:mmcblk0:no
(bootloader) has-slot:md_udc:no
(bootloader) has-slot:super:no
(bootloader) has-slot:system_ext:yes
(bootloader) has-slot: product:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:system:yes
(bootloader) has-slot:system_ext_a-cow:no
(bootloader) has-slot: product_a-cow:no
(bootloader) has-slot:vendor_a-cow:no
(bootloader) has-slot:system_a-cow:no
(bootloader) security-patch-level:2023-02-01
(bootloader) vendor-fingerprint:motorola/tonga_g/tonga:12/S3RQS32.20-42-1
(bootloader) 0-9-2/2e26e:user/release-keys
(bootloader) hw-revision: PVT
(bootloader) current-slot:a
(bootloader) serialno:ZY22GB5PSJ
(bootloader) product:tonga
(bootloader) version-os:12
(bootloader) first-api-level:30
(bootloader) slot-count:2
(bootloader) max-download-size:0x10000000
(bootloader) version:0.4
(bootloader) version-baseband:
(bootloader) secure:yes
(bootloader) dynamic-partition:true
(bootloader) system-fingerprint:motorola/tonga_g/tonga:12/S3RQS32.20-42-1
(bootloader) 0-9-2/2e26e:user/release-keys
(bootloader) version-bootloader:MBM-2.1-tonga_g-794044bf81-230129
(bootloader) unlocked:yes
all:
finished. total time: 1.691s
So your active boot slot is slot _a. Use this command to flash the patched boot image.
Code:
fastboot flash boot_a patched_boot.img
Viva La Android said:
So your active boot slot is slot _a. Use this command to flash the patched boot image.
Code:
fastboot flash boot_a patched_boot.img
Click to expand...
Click to collapse
awesome, thank u ! it worked , thanks again
keezeysqueezey said:
awesome, thank u ! it worked , thanks again
Click to expand...
Click to collapse
No problem friend. The problem was, the version of fastboot tools you were using does not automatically detect and flash your active slot. In such a scenario, the active slot must be specified during flashing. I realize you had trouble installing the fastboot tools I linked above and had to find tools elsewhere.
Anyway, glad you got it.
The Minimal ADB/Fastboot Tools version is very, very outdated! You should use the link to Google's platform tools. The page is currently not available but should be online in the next hours.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
WoKoschekk said:
The Minimal ADB/Fastboot Tools version is very, very outdated! You should use the link to Google's platform tools. The page is currently not available but should be online in the next hours.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Click to expand...
Click to collapse
The Minimal ADB & Fastboot tools, while outdated, are fully sufficient for tasks such as bootloader unlocking and flashing Magisk patched boot images to achieve root. If this threat involved more in-depth command lines, such as those used in the newer dynamic FastbootD userspace mode, the platform tools would surely be needed. But for the rudimentary tasks encompassed in this guide, Minimal ADB & Fastboot works great.
I also have problems with the installation of your ADB/Fastboot Tools. Execution of the file leads to:
Yes, you are right. This version will flash any device as good as the current version. But every user will get the same error as in post #4 because this version of fastboot can't handle A/B slots and many other functions released since 2013.
see MOD EDIT at the end of the post:
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
WoKoschekk said:
I also have problems with the installation of your ADB/Fastboot Tools. Execution of the file leads to:
View attachment 5880235
Yes, you are right. This version will flash any device as good as the current version. But every user will get the same error as in post #4 because this version of fastboot can't handle A/B slots and many other functions released since 2013.
see MOD EDIT at the end of the post:
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for your feedback and reporting the issue with the fastboot tools. I'll upload another copy and change the link.
Minimal ADB & Fastboot does indeed support A/B partitioning and automatically flashes your active boot slot without the need to specify boot_a or boot_b. That particular member had issues because he didn't use Minimal ADB & Fastboot. He used another fastboot tools implementation because, like you, he was unable to install the Minimal tools due to an error. @WoKoschekk , if you don't mind doing so, I would ask you to validate my position on this and flash your device using Minimal ADB & Fastboot using the exact instructions I have outlined. I'm 99% certain on my position but I need to be 100% sure when providing instructions in tutorials. I'm traveling and cannot test this myself or I would do it. I will post a new link for the tools shortly. Thanks again for your valuable feedback and for validating this, if you don't mind doing it. It would be a huge help.
Minimal ADB & Fastboot has been fixed and an updated link posted.
thx, can now be installed without problems