Related
ok so i had my hero on the stock fresh rom from his kitchen and i decided to try out the new dc2.08.1 to see if there were still bugs that made me not want to use the older 2.1 roms. after flashing it no audio worked at all not even when talking on the phone. so i did a nandroid restore of a backup i made right before flashing DC. everything seemed to be back to normal but then i realized my audio is still not working but in calls it is working. i figured the restore messed up so i tried again and it didnt work for some reason. then i downloaded gumbo1.5c from my phone and flashed that and everything was perfect once again. the whole day my phone was flawless until last night at 2am i went to set an alarm clock and for some reason that triggered the audio to go off again. so i restarted my phone and figured it might fix itself but it didnt and i already deleted gumbo off my sd. i downloaded it again and then my phone seemed to start getting sluggish and finally completely froze after a while. i removed the battery and tried to turn it back on but it got stuck at the htc screen. then i tried to get into recovery but that doesnt work either now... fastboot does boot up and i tried to ruu from it but when the ruu is rebooting to bootloader my phone just stays off and doesnt reboot.. i did notice on fastboot it says "touch panel-fail".
before installing or restoring any roms i did wipe everything does anyone know what i have to do to restore my hero or am i just completely screwed D:
do a search for ruu error 110. try doing what it says and you should be able to get back to stock, and either take your phone in or flash again.
alright i will try that but i didnt have the 110 error any other possible solutions if this dont work? thx for the response
dylan6879 said:
alright i will try that but i didnt have the 110 error any other possible solutions if this dont work? thx for the response
Click to expand...
Click to collapse
What's he's saying is that if your phone has hardware issues, then you need to do the RUU to put it back to stock or sprint might not fix it under warranty.
I agree with the above, sounds like a hardware issue although the timing of the issue with a flash sounds strange.
yea i thought it might be a hardware issue but it just seems odd how it happened after flashing 2.1 and then reverting to 1.5. I want to bring it back to sprint but dont want to get screwed over because of it being rooted. i want to ruu but the phone just seems to be dead and doesnt want to do anything besides fastboot and show the htc screen
Some people have problems with the RUU, but the steps to fix the Error 110 after RUU'ing, should work anytime regardless if you RUUed or not. Your recovery could have gotten deleted. Try flashing it from fastboot. There are directions in this forum on how to do it from fastboot.
ok well i kept trying to do the ruu and i got it to run once and it completed succesfully... so i thought maybe i had fixed it but then it still wont boot and only shows the htc screen but fastboot still works so can someone link me to the thread that tells hows to reflash recovery from fastboot. ill look for it but just incase i cant find it.
dylan6879 said:
ok well i kept trying to do the ruu and i got it to run once and it completed succesfully... so i thought maybe i had fixed it but then it still wont boot and only shows the htc screen but fastboot still works so can someone link me to the thread that tells hows to reflash recovery from fastboot. ill look for it but just incase i cant find it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=674788
EVERYTHING, including the 110 fix is in that post.
i looked there i know the 110 error fix is in there but i cant find anything on flashing recovery through fastboot
dylan6879 said:
i looked there i know the 110 error fix is in there but i cant find anything on flashing recovery through fastboot
Click to expand...
Click to collapse
Did you try following his procedure? it should resolve your issue.
otherwise: fastboot flash recovery recoveryimagefilename
Pro tip: in a windows command prompt if you go to your androidsdk\tools directory and type 'fastboot' it will give you all the options.
alright so ive tried the 110 error fix and i cant get past the first step because my command prompt wont recognize the device.
thx for telling me how to get to fastboot commands and i tried installing a new rom from there but i cant type it correctly im not sure what i typed wrong. it say the syntax of the command is incorrect. im trying to do the command "update <filename>" so i typed in "fastboot update <update.zip>".
dylan6879 said:
alright so ive tried the 110 error fix and i cant get past the first step because my command prompt wont recognize the device.
thx for telling me how to get to fastboot commands and i tried installing a new rom from there but i cant type it correctly im not sure what i typed wrong. it say the syntax of the command is incorrect. im trying to do the command "update <filename>" so i typed in "fastboot update <update.zip>".
Click to expand...
Click to collapse
You don't need the < > in there.
fastboot update update.zip should work.
thx i tried it that way and it it went through but then said
"archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
dylan6879 said:
thx i tried it that way and it it went through but then said
"archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
Click to expand...
Click to collapse
What exactly are you trying to flash? What's the filename, and what's it for?
If this is a ROM you don't want update.
If it's a recovery image:
fastboot flash recovery recoveryimagename.zip
oh yeah i was trying to flash a rom. i thought u could do that from there. where should i have the recovery img before i flash it. and is it possible to flash a rom through here?
ok so i put the recovery in the same place i had the roms and it went through but now it failed saying "sending 'recovery' <2326 KB>... FAILED <remote: not allow>".
dylan6879 said:
ok so i put the recovery in the same place i had the roms and it went through but now it failed saying "sending 'recovery' <2326 KB>... FAILED <remote: not allow>".
Click to expand...
Click to collapse
It's probably possible to flash a rom through fastboot, but I've never done it.
What recovery image are you using? And what is the exact name of the recovery image file? Where exactly did you put the recovery image file?
i tried the clockwork 1.7.6 and 1.5.2 and i tried them zipped up and as img files. i put them in the tools folder in android-sdk-windows. btw thx for all ur help
the name of the recovery image files are clockwork.zip, clockwork.img, 152.zip, and 152.img those are the four files i tried
dylan6879 said:
i tried the clockwork 1.7.6 and 1.5.2 and i tried them zipped up and as img files. i put them in the tools folder in android-sdk-windows. btw thx for all ur help
the name of the recovery image files are clockwork.zip, clockwork.img, 152.zip, and 152.img those are the four files i tried
Click to expand...
Click to collapse
Never used it, and 1.5.2 is old. I suggest downloading AmonRA's 1.6.2
You can't use zip files with fastboot...it wants the actual image (at least in this case, because those zip files aren't updates, they're just zip files).
So you should put the 152.img in the same directory as fastboot (Android-sdk-windows\tools)
Then you should do: fastboot flash recovery 1.5.2.img
What happens when you do that?
i tried flashing the 1.6.2.img and got the same result it says "sending 'recovery' <3720 KB>... FAILED <remote: not allow>".
hello everyone so i messed up bad. need rsd lite firmware to flash if anyone can share. all i have now is the abiliy to get into bootloader mode. Any help would be appreciated.
mikelikesbikes said:
hello everyone so i messed up bad. need rsd lite firmware to flash if anyone can share. all i have now is the abiliy to get into bootloader mode. Any help would be appreciated.
Click to expand...
Click to collapse
All factory images can be found here: http://motofirmware.center/files/category/23-droid-turbo/
having trouble getting rsd to recognize my device in bootloader, anyone recommend some drivers i can try? windows 8.1
mikelikesbikes said:
having trouble getting rsd to recognize my device in bootloader, anyone recommend some drivers i can try? windows 8.1
Click to expand...
Click to collapse
Install Motorola Device Manager from Moto's website. That will give you the drivers you need.
My advice is don't use RSDlite. To get it to work, you have to edit the xml file in the firmware that you're trying to flash to remove all the other devices that it inexplicably also includes. All RSDlite does is automate the fastboot flashing process. A better way to do it, in my opinion, is to edit the .bat file that comes with the factory images and manually input the fastboot commands that you see there. If you want more detailed directions, see my post here: http://forum.xda-developers.com/droid-turbo/help/turbo-firmware-t3254185
tried your tutorial. now for some reason i cant get fastboot to recognize my device. device manager now says "fastboot quark S" with the little triangle beside it. fastboot devices isnt showing my device is connected,but it did before i tried manually flashing like in the post you linked me to. i dont get it
TheSt33v said:
Install Motorola Device Manager from Moto's website. That will give you the drivers you need.
My advice is don't use RSDlite. To get it to work, you have to edit the xml file in the firmware that you're trying to flash to remove all the other devices that it inexplicably also includes. All RSDlite does is automate the fastboot flashing process. A better way to do it, in my opinion, is to edit the .bat file that comes with the factory images and manually input the fastboot commands that you see there. If you want more detailed directions, see my post here: http://forum.xda-developers.com/droid-turbo/help/turbo-firmware-t3254185
Click to expand...
Click to collapse
what do you mean by editing the .bat file that comes with factory images?
mikelikesbikes said:
what do you mean by editing the .bat file that comes with factory images?
Click to expand...
Click to collapse
I mean right click on the .bat file that is included in the .zip file of the firmware that you're trying to flash and select "edit." This allows you to see the commands that the .bat file does when you double click on it.
But you don't have to worry about that, because I already outlined the necessary commands in the post that I gave you a link to.
TheSt33v said:
I mean right click on the .bat file that is included in the .zip file of the firmware that you're trying to flash and select "edit." This allows you to see the commands that the .bat file does when you double click on it.
But you don't have to worry about that, because I already outlined the necessary commands in the post that I gave you a link to.
Click to expand...
Click to collapse
any idea why fastboot doesnt see my device now? it did before, but I get the yellow triangle in device manager. I have installed every driver i can find... including motorola device manager and ran it several times. Was on mofo'd 4.4.4. and for some dumb reason thought i could flash the lollipop bootloader so now i am stuck with bootloader, recovery, but no os. any advice would be great.
OK, so i finally got fastboot to recognize my device again. Trying to download stock firmware from Rootjunky. Am i correct that I extract the zip into the fastboot folder then issue the commands? I am about to pull my hair out...
mikelikesbikes said:
any idea why fastboot doesnt see my device now? it did before, but I get the yellow triangle in device manager. I have installed every driver i can find... including motorola device manager and ran it several times. Was on mofo'd 4.4.4. and for some dumb reason thought i could flash the lollipop bootloader so now i am stuck with bootloader, recovery, but no os. any advice would be great.
OK, so i finally got fastboot to recognize my device again. Trying to download stock firmware from Rootjunky. Am i correct that I extract the zip into the fastboot folder then issue the commands? I am about to pull my hair out...
Click to expand...
Click to collapse
Yep. That should be all you have to do.
Heya Folks,
i tried to root my XT 890.
After everything seemed to work out well, i rebooted it after setting usb debug on, and now im stuck in "Warning Bootloader Unlocked" message.
i can access fastboot and cwm recovery.
what i tried so far:
1.
fastboot flash recovery cwm.img
go to recovery
install from sideload
adb sideload RAZRiRoot2.zip
it says everything complete
when i reboot -> loop again, no boot
2. tried with RSD lite 6.1.5 to flash stock rom - keep getting error on step 7/12, it says Flashing motobp ... and then it returns after 30 secs "Fastboot command failed"
anyone any tips?
thanks,
Ras
rassle said:
Heya Folks,
i tried to root my XT 890.
After everything seemed to work out well, i rebooted it after setting usb debug on, and now im stuck in "Warning Bootloader Unlocked" message.
i can access fastboot and cwm recovery.
what i tried so far:
1.
fastboot flash recovery cwm.img
go to recovery
install from sideload
adb sideload RAZRiRoot2.zip
it says everything complete
when i reboot -> loop again, no boot
2. tried with RSD lite 6.1.5 to flash stock rom - keep getting error on step 7/12, it says Flashing motobp ... and then it returns after 30 secs "Fastboot command failed"
anyone any tips?
thanks,
Ras
Click to expand...
Click to collapse
Try to flash them manually. In the xml file of the rsd lite package u can see the commands. U will need mfastboot for this. U do use a 4.1.2 (JB) package for this?
Hazou said:
Try to flash them manually. In the xml file of the rsd lite package u can see the commands. U will need mfastboot for this. U do use a 4.1.2 (JB) package for this?
Click to expand...
Click to collapse
im actually trying with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml which has the title of XT890_emara-user 4.1.2 9.8.2I-50_SMI-26 1358465787 release-keysSUNRISE_SMB_REV30_V2_R3_1251.B
i do have problems of finding stock roms as most links are pointing to sbf droid developers (cant post link due to beeing new) which is dead for me.
ive used shadows mirror list, but its only showing non-4.1.2 versions for me. however, im not quite sure which firmware was one the phone before *sorry*
by commands of the xml file u mean the xml file which is contained in the "firmware" downloads for the XT890?
Hazou said:
Try to flash them manually. In the xml file of the rsd lite package u can see the commands. U will need mfastboot for this. U do use a 4.1.2 (JB) package for this?
Click to expand...
Click to collapse
okay, ive been a bit impatient and bricked it with flashing 4.0.4 eu firmware. (only green LED, no fast boot no nothing)
i then used that unbrick medfield method thing posted by czechnolog, and the phone fully booted up in 4.0.4 after that ... wow that was some progress.
however, whenever i reboot the phone it says service code corrupt, but it boots fully into android - im a bit paranoid now if thats a positive or negative progress xD
i updated android with a 50 meg udpate --> success
i then tried to update again, it says its an 300 meg udpate. the phone boots, the android bot gets surgery, and it fails at around 45% - tried this 2 times
its still at 4.0.4
how do i proceed from here on? try flashing a 4.1.2? something completly different? i mean, after seeing 1 day no boot at all this "feels" like some progress - just not correct :/
rassle said:
okay, ive been a bit impatient and bricked it with flashing 4.0.4 eu firmware. (only green LED, no fast boot no nothing)
i then used that unbrick medfield method thing posted by czechnolog, and the phone fully booted up in 4.0.4 after that ... wow that was some progress.
however, whenever i reboot the phone it says service code corrupt, but it boots fully into android - im a bit paranoid now if thats a positive or negative progress xD
i updated android with a 50 meg udpate --> success
i then tried to update again, it says its an 300 meg udpate. the phone boots, the android bot gets surgery, and it fails at around 45% - tried this 2 times
its still at 4.0.4
how do i proceed from here on? try flashing a 4.1.2? something completly different? i mean, after seeing 1 day no boot at all this "feels" like some progress - just not correct :/
Click to expand...
Click to collapse
Ah u noticed why it is said many times that u never should flash 4.0.4 through rsd lite without some changes.
It is some progress. The system boots again. U most likely got JB dnx and ifwi, the part that u screw up with 4.0.4 and ICS system and boot. Next thing to try is getting the 4.1.2 firmware and flashing the parts manually. Flash the system and boot and erase the data and cache. Then flash cwm and flash supersu.
Mfastboot flash system <system_signed>
Mfastboot flash boot <boot_signed>
Mfastboot erase user data
Mfastboot erase cache
After that u should have a fully flashed 4.1.2 firmware phone. With cwm and root
Hazou said:
Ah u noticed why it is said many times that u never should flash 4.0.4 through rsd lite without some changes.
It is some progress. The system boots again. U most likely got JB dnx and ifwi, the part that u screw up with 4.0.4 and ICS system and boot. Next thing to try is getting the 4.1.2 firmware and flashing the parts manually. Flash the system and boot and erase the data and cache. Then flash cwm and flash supersu.
Mfastboot flash system <system_signed>
Mfastboot flash boot <boot_signed>
Mfastboot erase user data
Mfastboot erase cache
After that u should have a fully flashed 4.1.2 firmware phone. With cwm and root
Click to expand...
Click to collapse
ive done first 2 steps. hes not accepeting "mfastboot erase user data" - should i skip that one? **fixed, its userdata** ^.^
after erase cache -> reboot? or direct flash cwm.img?
rassle said:
ive done first 2 steps. hes not accepeting "mfastboot erase user data" - should i skip that one? **fixed, its userdata** ^.^
after erase cache -> reboot? or direct flash cwm.img?
Click to expand...
Click to collapse
okay, just flashed cwm without reboot, after that rebooted.
4.1.2 was working then...
... continued to swapping cwm vs twrp
... done a backup, saved the backup
... dled cm11 + gapps
and now im 4.4.4 which seems to run very smoothly
- the "Service Code Corrupt" Message remains, but well... its working aight?!
thanks for all the support
rassle said:
okay, just flashed cwm without reboot, after that rebooted.
4.1.2 was working then...
... continued to swapping cwm vs twrp
... done a backup, saved the backup
... dled cm11 + gapps
and now im 4.4.4 which seems to run very smoothly
- the "Service Code Corrupt" Message remains, but well... its working aight?!
thanks for all the support
Click to expand...
Click to collapse
Good that it worked. The message will remain there. I don't know how to fix that issue. But I don't think it is a huge issue, but its annoying.
Hey guys, I've decided I'm going to root my Moto X Unlocked Edition. I've been following this guide: http://www.theandroidsoul.com/2014-moto-x-2nd-gen-marshmallow-root-86348/ (as well as many others) and I'm running into issue after issue.
I've managed to unlock my bootloader. I'm on step 8: "fastboot flash boot boot.img" and have tried with so many techniques but keep getting this "mismatched partition size (boot)" error after each attempt. I've tried using .img files from CMod, from the guide that I'm following, etc. I've googled the error with no useful result coming up. I'm at a loss here and really hoping someone is able to help me out. Searching is turning up nothing and I'm about to start tugging at my hair. If anyone has a one click installer that would work, please pass it along!
Thank you all very much!
Edit 4/29/16 13:01 ET: I've switched from trying to use the 'fastboot flash boot' command and started trying to use 'fastboot update <romname.zip >' with various different ROMs. I'm getting this error.
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Click to expand...
Click to collapse
I'm not sure what to do now. I feel like I'm getting reckless in trying an overwhelming amount of solutions to no avail. I'm going to wait, now. I'm starting to think that these phones can't be rooted or flashed with a new ROM.
What phone version do you have, XT1095? I just tried to root my device without reading carefully and ended up softbricked...had to use fastboot to wipe everything and flash stock to recover. Seems this devices is tricky to root on Marshmallow, much harder than ones I've had in the past.
Have you tried the method here? http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Or, if you install TWRP you could just flash a pre-rooted ROM instead of rooting stock.
Thank you for the help @viper74656!
I'm struggling to even get the TWRP installed. When I try to install TWRP-3.0.0-0-victara.img, I get
cmd: getvar: partition-type:recovery
cmd: getvar:max-download-size
cmd: download:0096c000
cmd: flash:recovery
Mismatched partition size (recovery)
Click to expand...
Click to collapse
I was having this problem earlier too when I was trying to work around that. I'm going to try an alternate way of installing TWRP.
Really, all I want to do is get CMod. When I rooted my HTC Inspire 4G, it was a cakewalk... I didn't expect all this LOL
viper74656 said:
What phone version do you have, XT1095? I just tried to root my device without reading carefully and ended up softbricked...had to use fastboot to wipe everything and flash stock to recover. Seems this devices is tricky to root on Marshmallow, much harder than ones I've had in the past.
Have you tried the method here? http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Or, if you install TWRP you could just flash a pre-rooted ROM instead of rooting stock.
Click to expand...
Click to collapse
Yeah, btw, I have an xXT1095
So I managed to get TWRP installed on my XT1095 using the "WinDroid" toolkit I found somewhere on XDA. It seems to push the right fastboot commands, but I had to manually download and select an older TWRP version. Read something about our recovery partition not working with the newer versions. I still got the mismatch error, but when I rebooted into recovery TWRP was there.
I haven't ventured back to try it again after having to wipe and start over...bleh.
Twrp manager (from the playstore) is what I had to use to install recovery. Windroid wouldn't push it for some reason.
Sent from my XT1096 using XDA-Developers mobile app
Hey everyone,
I rooted with the Magisk guide and patched the boot.img etc.... but it was annoying every time there is an OTA so I flashed all the stock firmware via ADB and everything went well, I rebooted and no longer have root. This is with the December image. So now I'm stock and I tried to apply OTA via 'settings' but I am STILL getting the error of "Couldn't Update: Installation Problem".
Any ideas what to do?
CheatingOutlaw said:
Hey everyone,
I rooted with the Magisk guide and patched the boot.img etc.... but it was annoying every time there is an OTA so I flashed all the stock firmware via ADB and everything went well, I rebooted and no longer have root. This is with the December image. So now I'm stock and I tried to apply OTA via 'settings' but I am STILL getting the error of "Couldn't Update: Installation Problem".
Any ideas what to do?
Click to expand...
Click to collapse
If you flashed stock December, why didn't you just flash stock January?
Since OTA isn't working, you would just need to flash stock January anyway...
ilal2ielli said:
If you flashed stock December, why didn't you just flash stock January?
Since OTA isn't working, you would just need to flash stock January anyway...
Click to expand...
Click to collapse
You're absolutely right. I was just thinking that now. But I was also wondering how I can get OTA working again because I travel for work and don't always have access to a PC. Thank you for the response.
CheatingOutlaw said:
You're absolutely right. I was just thinking that now. But I was also wondering how I can get OTA working again because I travel for work and don't always have access to a PC. Thank you for the response.
Click to expand...
Click to collapse
I haven't seen too many people successfully do the OTA method. I tried it and couldn't get it to work properly either. Someone said you need to have stock dtbo too (for those that flash custom kernels), but since you can't flash the dtbo through an app (like FKM or EXKM), then there's no point to the OTA method.
ilal2ielli said:
I haven't seen too many people successfully do the OTA method. I tried it and couldn't get it to work properly either. Someone said you need to have stock dtbo too (for those that flash custom kernels), but since you can't flash the dtbo through an app (like FKM or EXKM), then there's no point to the OTA method.
Click to expand...
Click to collapse
I flashed the whole January firmware but after rebooting the phone the build number is still showing as December?!
CheatingOutlaw said:
I flashed the whole January firmware but after rebooting the phone the build number is still showing as December?!
Click to expand...
Click to collapse
Probably a long shot, but did you use the correct version per your carrier?
I'm sure you did, so I would change slots and fastboot it again. fastboot --set-active=a or b
Depending on which slot your on of course :good:
CheatingOutlaw said:
I flashed the whole January firmware but after rebooting the phone the build number is still showing as December?!
Click to expand...
Click to collapse
What he said!
Badger50 said:
Probably a long shot, but did you use the correct version per your carrier?
I'm sure you did, so I would change slots and fastboot it again. fastboot --set-active=a or b
Depending on which slot your on of course :good:
Click to expand...
Click to collapse
writing 'system_a' 1/3...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 8.933s
Press any key to exit...
This is the error I receive after trying to flash-all. Really weird.
Every time I had to go back to stock I used the sideload method.
Best way IMO to fresh start, best way to relock bootloader though.
Good luck
CheatingOutlaw said:
writing 'system_a' 1/3...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 8.933s
Press any key to exit...
This is the error I receive after trying to flash-all. Really weird.
Click to expand...
Click to collapse
Try different cable and USB ports :good:
open the flashall.bat and remove the -w from the command. the flash factory resets the device.
It's still failing to flash the firmware via Minimal ADB and Fastboot. I've been trying to flash the factory image, not the OTA, from here:
https://forum.xda-developers.com/pixel-4-xl/how-to/guide-pixel-4-xl-android-10-q-root-t3996969
After extracting the stock firmware from the ZIP, I have a few files but also another ZIP which I did not extract. Maybe I must extract that too? I kept them in the root installation of ADB where you run the cmd from.
I've tried using another cable and USB port, doesn't work. I tried flashing to partition B not A, but I just get a bootloop until I switch back to A. But no matter what, I keep getting the error of:
"writing 'system_a' 1/3...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 8.914s
Press any key to exit..."
CheatingOutlaw said:
It's still failing to flash the firmware via Minimal ADB and Fastboot. I've been trying to flash the factory image, not the OTA, from here:
https://forum.xda-developers.com/pixel-4-xl/how-to/guide-pixel-4-xl-android-10-q-root-t3996969
After extracting the stock firmware from the ZIP, I have a few files but also another ZIP which I did not extract. Maybe I must extract that too? I kept them in the root installation of ADB where you run the cmd from.
I've tried using another cable and USB port, doesn't work. I tried flashing to partition B not A, but I just get a bootloop until I switch back to A. But no matter what, I keep getting the error of:
"writing 'system_a' 1/3...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 8.914s
Press any key to exit..."
Click to expand...
Click to collapse
Get rid of minimal adb and just use platform-tools :good:
Badger50 said:
Get rid of minimal adb and just use platform-tools :good:
Click to expand...
Click to collapse
No refernce to minimal adb in the guide he posted.
Badger50 said:
Get rid of minimal adb and just use platform-tools :good:
Click to expand...
Click to collapse
SUCCESS!!! I will explain the simple and easily overlooked stupidity that got me into this situation, so others can read:
Minimal ADB and Fastboot DID work previously for the December stock firmware (if i can recall?). I don't think it was working for January in this case.
Also, I tried using the platform tools previously today and after opening windows powershell within the root folder, I just got red text and absolutely nothing worked. After a few hours today, somehow the powershell opened and did NOT show all red text this time. Input commands responded when I typed "adb devices" and I was like AHAAA!! For me, there was no need to download Android SDK or any of that. Only Platform Tools was required.
CheatingOutlaw said:
SUCCESS!!! I will explain the simple and easily overlooked stupidity that got me into this situation, so others can read:
Minimal ADB and Fastboot DID work previously for the December stock firmware (if i can recall?). I don't think it was working for January in this case.
Also, I tried using the platform tools previously today and after opening windows powershell within the root folder, I just got red text and absolutely nothing worked. After a few hours today, somehow the powershell opened and did NOT show all red text this time. Input commands responded when I typed "adb devices" and I was like AHAAA!! For me, there was no need to download Android SDK or any of that. Only Platform Tools was required.
Click to expand...
Click to collapse
Glad you got it working.
CheatingOutlaw said:
SUCCESS!!! I will explain the simple and easily overlooked stupidity that got me into this situation, so others can read:
Minimal ADB and Fastboot DID work previously for the December stock firmware (if i can recall?). I don't think it was working for January in this case.
Also, I tried using the platform tools previously today and after opening windows powershell within the root folder, I just got red text and absolutely nothing worked. After a few hours today, somehow the powershell opened and did NOT show all red text this time. Input commands responded when I typed "adb devices" and I was like AHAAA!! For me, there was no need to download Android SDK or any of that. Only Platform Tools was required.
Click to expand...
Click to collapse
The IDE (Android Studio) is just nice to have for easyish updating (open Android studio, hit update notification, done!) and it's emulator, otherwise if not using at least 2 out of those 3 it's probably not worth the extra disk space, platform tools and manually checking for updates is the other official (directly handed out by Google) option.
Phoenix591 said:
The IDE (Android Studio) is just nice to have for easyish updating (open Android studio, hit update notification, done!) and it's emulator, otherwise if not using at least 2 out of those 3 it's probably not worth the extra disk space, platform tools and manually checking for updates is the other official (directly handed out by Google) option.
Click to expand...
Click to collapse
Or, he can check the thread he posted for all the latest updates.
CheatingOutlaw said:
writing 'system_a' 1/3...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 8.933s
Press any key to exit...
This is the error I receive after trying to flash-all. Really weird.
Click to expand...
Click to collapse
Your ADB files are outdated, you must update to the latest version. I initially ran into the same issue when I got my P4 XL back in November.