Hey there,
I failed to upgrade my moto x to lollipop and accidentally erased the Android OS.
Basically, when I try to turn it on, it gets stuck at the moto bootlogo. If I press te volume down and the lock buttons, I do get to the boot screen (AP Fastboot Flash Mode), but, no matter what option I select, it goes back to the bootlogo and gets stuck again.
When I connect to my pc, it appears as Motorola ADB Interface at the device manager, even with Driver Signature Enforcement disabled. That makes it impossible for me to update the device with the RiffBox Drivers and, therefore, to have it accepted by Blankflash.
Is there any way to save this phone?
Thanks a lot in advance.
luiza1up said:
Hey there,
I failed to upgrade my moto x to lollipop and accidentally erased the Android OS.
Basically, when I try to turn it on, it gets stuck at the moto bootlogo. If I press te volume down and the lock buttons, I do get to the boot screen (AP Fastboot Flash Mode), but, no matter what option I select, it goes back to the bootlogo and gets stuck again.
When I connect to my pc, it appears as Motorola ADB Interface at the device manager, even with Driver Signature Enforcement disabled. That makes it impossible for me to update the device with the RiffBox Drivers and, therefore, to have it accepted by Blankflash.
Is there any way to save this phone?
Thanks a lot in advance.
Click to expand...
Click to collapse
Do you still need help with this brick?
Flarbenshweezel said:
Do you still need help with this brick?
Click to expand...
Click to collapse
Yes, please.
No one?
What model is your X? Is it a pure edition?
dustin_b said:
What model is your X? Is it a pure edition?
Click to expand...
Click to collapse
No. It wasn't the pure edition, but I unlocked the bootloader before screwing the firmware instalation
Dont worry its fixable. As long as you're still able to get it in to the boot loader mode.
Sent from my XT1095 using XDA Free mobile app
flameinthefire said:
Dont worry its fixable. As long as you're still able to get it in to the boot loader mode.
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
What am I supposed to do, then?
Once I get to the bootloader, no matter what option I select, it goes back to that logo again and I get stuck.
Here you go..
How to unroot moto x(Return to stock): http://youtu.be/vFQiiMsDu9o
Sent from my XT1095 using XDA Free mobile app
luiza1up said:
What am I supposed to do, then?
Once I get to the bootloader, no matter what option I select, it goes back to that logo again and I get stuck.
Click to expand...
Click to collapse
You can flash your system.img in fastboot. You just have to find the right one for your model.
flameinthefire said:
Here you go..
How to unroot moto x(Return to stock): http://youtu.be/vFQiiMsDu9o
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't work since the phone is not recognized as a usb device. If I go to windows device manager, it shows the phone as Android Device - Motorola ADB Interface.
dustin_b said:
You can flash your system.img in fastboot. You just have to find the right one for your model.
Click to expand...
Click to collapse
How is that possible if all I can get is the fastboot screen, but any option selected leads to that boot logo again?
luiza1up said:
How is that possible if all I can get is the fastboot screen, but any option selected leads to that boot logo again?
Click to expand...
Click to collapse
What response do you get if you type "fastboot devices" ?
Steve-x said:
What response do you get if you type "fastboot devices" ?
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
0430820086 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>
luiza1up said:
How is that possible if all I can get is the fastboot screen, but any option selected leads to that boot logo again?
Click to expand...
Click to collapse
You flash from the fastboot screen. You don't select any of the options.
dustin_b said:
You flash from the fastboot screen. You don't select any of the options.
Click to expand...
Click to collapse
First of all, thanks for all the help.
Still, I did what you suggested and now it gets stuck on that Bootloader Unlocked Warning.
luiza1up said:
First of all, thanks for all the help.
Still, I did what you suggested and now it gets stuck on that Bootloader Unlocked Warning.
Click to expand...
Click to collapse
Which version of phone do you have and which version are you flashing?
Steve-x said:
Which version of phone do you have and which version are you flashing?
Click to expand...
Click to collapse
The version I used to have before was as it follows:
{
"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"
}
So, after rooting, I tried the LXE 22.46-17 firmware. That's when the OS was erased.
I finally managed to solve it.
It is a Nextel firmware, so I wasn't flashing the system.img right.
Thank you all for your kindness and answers.
Related
{
"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"
}
First, Sorry for my English
Hmm.. my droid3 doesn't work. When boot up, Motorola logo
block motoblur launcher . so I can't use my droid3. I use rsd lite5.5(with fastboot firmware zip). But nothing happened to my droid3. Motorola Korea After service center said "we don't know what is wrong and have replacement"
Help me guys ..
Sent from my SHW-M250S using XDA App
http://forum.xda-developers.com/showthread.php?t=1336980
Follow instructions.
If link to file doesn't work, use this mirror: http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip
DoubleYouPee said:
http://forum.xda-developers.com/showthread.php?t=1336980
Follow instructions.
If link to file doesn't work, use this mirror: http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip
Click to expand...
Click to collapse
But my symptom is same...
Sent from my LU2300 using XDA App
HerbK said:
But my symptom is same...
Sent from my LU2300 using XDA App
Click to expand...
Click to collapse
What? please elaborate
edit: you don't have the XT862?
DoubleYouPee said:
What? please elaborate
edit: you don't have the XT862?
Click to expand...
Click to collapse
I have Droid3(xt862 vrw). Now My droid3 doesn't work. I download that file and flash file. Flashing is all right, But Everything is same :[
Sent from my LU2300 using XDA App
That is Notification Bar, I can touch that bar. But Droid3 always showed that screen
Sent from my LU2300 using XDA App
HerbK said:
I have Droid3(xt862 vrw). Now My droid3 doesn't work. I download that file and flash file. Flashing is all right, But Everything is same :[
Sent from my LU2300 using XDA App
Click to expand...
Click to collapse
So you flash with fastboot? Not RSDlite..
It takes 3+min first boot
im actually having the same problem as this guy. but mine was refurbished and im pretty sure its a hardware problem. ik adb rsd and moto-fastboot lol
To be clear...
You downloaded that file above?
Plugged in your phone via USB with a mostly/fully charged battery?
Powered up with M + Power button?
Scrolled with Volume Down to AP Fastboot and pressed Volume Up to select it?
Once it said USB Connected, you ran the CLICK HERE etc. batch file?
This should unbrick you in a few minutes and the initial boot will take a few minutes as well. I know those files work...they're my working DL'd files on my DropBox account.
cant speak for the other guy but for me this is my third refurbished droid 3. i can still acess clockwork and stock recovery. i used moto fast boot and rsd they both said "okay" for each part. "adb reboot-bootloader" aka ap fast boot also went there manually yes battery fully charged made sure. im so puzzled lol
jellman said:
cant speak for the other guy but for me this is my third refurbished droid 3. i can still acess clockwork and stock recovery. i used moto fast boot and rsd they both said "okay" for each part. "adb reboot-bootloader" aka ap fast boot also went there manually yes battery fully charged made sure. im so puzzled lol
Click to expand...
Click to collapse
Try the quick unbricking script. There's 2 other threads just posted in today in this General section that contain all of the needed info.
redsox985 said:
Try the quick unbricking script. There's 2 other threads just posted in today in this General section that contain all of the needed info.
Click to expand...
Click to collapse
...hm. maybe i wasn't clear. the unbricking method isnt new to me and i am not a noob. i have tried both thank you for your suggestion tho. permanent solution? google needs to take over the world and unlock bootloaders i miss the days of the original droid T_T
jellman said:
...hm. maybe i wasn't clear. the unbricking method isnt new to me and i am not a noob. i have tried both thank you for your suggestion tho. permanent solution? google needs to take over the world and unlock bootloaders i miss the days of the original droid T_T
Click to expand...
Click to collapse
OOH! Misunderstood you. When you said you used Moto Fastboot and RSD I assumed that you booted into Fastboot to flash with RSD. Fastboot just allows you to flash, the script and RSD are the two means of unbricking. Gotcha. And I agree. BL's need to be unlocked.
Maybe you guys are on the latest OTA and try to fastboot .890?
Sounds to me like either one or both of you didn't erase userspace in stock recovery. I had this very same problem. The rsdlite method will not allow you to boot until the old junk is gone from /data and /cache. Try turning on the d3 from power off while holding the "m" key, then selecting down arrow to "Recovery", then hit "ok". Once in stock recovery, select erase user data and cache. Do it several times, then select reboot, and you will be good to go, assuming you flashed the correct xml/zip package successfully.
Sent from my DROID3 using xda premium
Hi,
I downloaded CWM unofficial 6.0.32 from this forum, but I'm new and I have no idea what to do with it. I did successfully root my phone that's all I've done to it.
Thanks!
You use fastboot commands. There's a tutorial skeevy just made in general.
Sent from my PACMAN MATRIX HD MAXX
I'm sorry, but I'm getting stuck
1: I installed the sdk replaced the files with the updated ones provided.
2:checked adb devices from command promt and It sees my device.
3: ran adb and it successfully starts
4: I then rebooted phone into fastboot Power+Volume down and adb reports device not found.
5: pull hair out.
I'd appreciate a sort of idiots guide because I'm getting no where fast and I've read and read, but they don't explain much that's the problem.
Do you have the lastest motorola usb driver installed?
hungrymr2 said:
Do you have the lastest motorola usb driver installed?
Click to expand...
Click to collapse
Yes, Sir
Rick1488 said:
I'm sorry, but I'm getting stuck
1: I installed the sdk replaced the files with the updated ones provided.
2:checked adb devices from command promt and It sees my device.
3: ran adb and it successfully starts
4: I then rebooted phone into fastboot Power+Volume down and adb reports device not found.
5: pull hair out.
I'd appreciate a sort of idiots guide because I'm getting no where fast and I've read and read, but they don't explain much that's the problem.
Click to expand...
Click to collapse
1. :good:
2. :good:
3 :good:
4 You're in fastboot mode....adb won't recognize your phone....that's normal...
5
use the command "fastboot flash recovery cwm.img" from inside the folder with cwm.img. Or move the fastboot executable and the recovery image to C:\ and do it from there...Win can crap out when/if there are too many characters in the path...
Also, right click the fastboot executable and set it to run as admin. Might have to disable UAC as well....don't ask me how, I don't know...google it.
//I'm cereal, ya had to rename the SBF because in the home directory the path + sbf name would be too many characters for Win to work with and the flash would fail....
No idea, but here's what I did to install cwm. download safestrap apk, boot to safestrap recovery, hit fix permission, go back to cmd prompt, fastboot flash it,
edit: try enabling "usb developer/debugging mode" before booting it into fastboot?
skeevydude said:
1. :good:
2. :good:
3 :good:
4 You're in fastboot mode....adb won't recognize your phone....that's normal...
5
use the command "fastboot flash recovery cwm.img" from inside the folder with cwm.img. Or move the fastboot executable and the recovery image to C:\ and do it from there...Win can crap out when/if there are too many characters in the path...
Also, right click the fastboot executable and set it to run as admin. Might have to disable UAC as well....don't ask me how, I don't know...google it.
//I'm cereal, ya had to rename the SBF because in the home directory the path + sbf name would be too many characters for Win to work with and the flash would fail....
Click to expand...
Click to collapse
Ok your directions were very helpful and I thought good things were coming my way, but when entering the flash command I get preflash validation failed. <failed> remote failure.
{
"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"
}
Update: now the phone boots to fastboot with flash failure on the bottom. What the hell did I do wrong?
Update2: ok got her back to life back to the original problem.
Rick1488 said:
Ok your directions were very helpful and I thought good things were coming my way, but when entering the flash command I get preflash validation failed. <failed> remote failure.
Update: now the phone boots to fastboot with flash failure on the bottom. What the hell did I do wrong?
Update2: ok got her back to life back to the original problem.
Click to expand...
Click to collapse
You might have a picky motherboard. Some front-side ubs ports won't work for some odd reason for some users. Use a usb port on the back of your pc.
Out of curiousity, did you try flashing a fastboot with rsd before you started doing this? And if yes, did it finish completely?
Also attached is a zip to flash CWM from SSR (maybe...SSR might block the command) and a fastboot modified to only flash CWM. Both are untested but worth a shot.
EDIT: Any one of you windows users care to chime in? Ya'll know I don't run it. I'm kinda runnin outta ideas here....gettin down to the just use linux reply...
unlocked bootloader
I saw that you rooted but did you unlock the boot loader?
frog1982 said:
I saw that you rooted but did you unlock the boot loader?
Click to expand...
Click to collapse
You're right...can't believe I missed that...never once is that mentioned...,
frog1982 said:
I saw that you rooted but did you unlock the boot loader?
Click to expand...
Click to collapse
Um, I kinda forgot that part.. my fault. I just unlocked the bootloader and I'm gonna give it another try.
UPDATE: Success!
I'm sorry guys thanks for all your help.
:victory::victory:
I changed CID to GOOGL001 and tried to flash a RUU and somehow my hboot got f'd. It will not connect with adb or fastboot. The Android guy doesn't look well. Anyone know how I can fix this?
{
"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"
}
You still have the old firmware installed. The Google edition firmware version is inside brackets which means that there was an attemp to flash it bit it failed.
Sent from my HTC One using Tapatalk
Ivanovic said:
You still have the old firmware installed. The Google edition firmware version is inside brackets which means that there was an attemp to flash it bit it failed.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
OK, if it don't show up on fastboot, how can I re-flash firmware?
Can you enter recovery?
Sent from my HTC One using Tapatalk
Your bootloader is locked as well. get it unlocked.
Ivanovic said:
Can you enter recovery?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I do have twrp recovery and can get to it no problem. Phone works ok, but it loses data signal quite often and has to be rebooted to regain data.
SaHiLzZ said:
Your bootloader is locked as well. get it unlocked.
Click to expand...
Click to collapse
I tried HTC1Guru bootloader reset tool to unlock bootloader and it said successful, but still shows relocked.
When you connect your phone,fastboot or normal, isn't it recognised and listed under devices?
Sent from my HTC One using Tapatalk
Ivanovic said:
When you connect your phone,fastboot or normal, isn't it recognised and listed under devices?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
No, "waiting on device".
I can connect to see files when phone is booted up...just not adb or fastboot.
USB debugging enabled? Reinstall drivers for your OS.
Ivanovic said:
Enable usb debugging?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
No usb debugging was not on(DOH!) but after I put it on. adb devices did recognize when the phone was booted normally, however after I did adb reboot-bootloader then it rebooted in fastboot and back to "waiting on device"
Try the drivers uninstall/install thing if you have time but let the phone be on fastboot while installing the drivers
Sent from my HTC One using Tapatalk
I'm guessing what I need is either twrp flashable firmware or a RUU exe that will run with CID of GOOGL001.
...or maybe I'm just screwed. I actually got someone wanting to buy the phone, but I wanted to fix it first. I have another One as well. This one is an ATT version and my other is TMobile.
Maybe if bootloader unlocked it would help????
Ivanovic said:
Try the drivers uninstall/install thing if you have time but let the phone be on fastboot while installing the drivers
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
My other HTC One works fine in fastboot and I have installed the drivers a couple times...even back on a Win 7 machine now because I thought maybe it was the Win 8.1 on my laptop.
ok, I dunno whether we are two of a kind...but I literally have the exact same problem! But my device says "tampered and unlocked" on the top. But if I go into a root checker app...it tells me that "this phone isn't rooted...
Does anyone have a clue on how to work around this please! Thanks!
Gonna try this http://www.youtube.com/watch?v=Gqfly8XVw6w
Edit...nevermind. Not what I thought it was
Btw what happens when you try selecting "recovery mode" ? Mine just throws up a red triangle with an exclamation mark...
Scrowlerfly said:
Btw what happens when you try selecting "recovery mode" ? Mine just throws up a red triangle with an exclamation mark...
Click to expand...
Click to collapse
I get recovery ok (twrp) just can't see device in fastboot to reflash firmware upgrade.
PROBLEM -
I can not get into phone settings or ANYTHING ELSE because it keep SHOWING this error and LOADS NO OS or any icon THING AFTER BOOT
{
"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"
}
I tried from adb and it didn't work :-
<<< C:\adb>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.005s
- I have downloaded rom from google for my phone model
- I can not ENABLE OEM unlock because I can not get into phone.
- I have tried wiping CACHE AND FACTORY RESET from recovery but it does not LOAD anything after boot and shows error I posted in image above.
lol!
first off, you posted in the wrong nexus 6 forums, as you arent developing anything(besides a headache). secondly, adb and fastboot are different. fastboot is not an adb command! fastboot is a different tool, like adb but different, and you can only use fastboot while you are in the bootloader. secondly, go back for a little and do a little more reading please, then try again.
edit.. good, this thread got moved to the right place.
"Administr4tor, Account currently disabled on Today, 20:48"
Interesting. Why? Is this thread dead now?
Looks like there is no way to reinstall rom again.
what I am trying to say here is
- I can not get into phone
- I can not enable USB DEBUGGING
- I CAN NOT enable OEM UNLOCK.
tell me yes or no if I can reinstall factory image. is it not simple/
dahawthorne said:
"Administr4tor, Account currently disabled on Today, 20:48"
Interesting. Why? Is this thread dead now?
Click to expand...
Click to collapse
no, its not dead though I was dead for couple days.
Administr4tor said:
Looks like there is no way to reinstall rom again.
what I am trying to say here is
- I can not get into phone
- I can not enable USB DEBUGGING
- I CAN NOT enable OEM UNLOCK.
tell me yes or no if I can reinstall factory image. is it not simple/
Click to expand...
Click to collapse
You're trying to unlock the bootloader, which requires fastboot, using ADB. Do you have fastboot drivers installed? Or you could just unlock the boot loader with nexus root toolkit.
thatkindaguy said:
You're trying to unlock the bootloader, which requires fastboot, using ADB. Do you have fastboot drivers installed? Or you could just unlock the boot loader with nexus root toolkit.
Click to expand...
Click to collapse
Thank you for reply,
- I have adb and fastboot drivers installed from xda when I connect the phone it shows connected, Please check the screenshot.
- I just want to flash stock rom, even if its possible to do it without unlocking bootloader, please let me know.
_ i have already tried NEXUS TOOLKIT and tried to unlock bootloader but it failed to unlock it.
Regards
You can't install a factory image without a locked bootloader. What did you do to make settings force close on boot?
geokhentix said:
You can't install a factory image without a locked bootloader. What did you do to make settings force close on boot?
Click to expand...
Click to collapse
oh, I didn't do anything, I wokeup and charged it after it went dead, and it all happened,
also sometimes I get this error too if I am not getting those "unfortunate error"
Push OTA. It works with locked bootloader. Recovered N6 from the same state (Your device is corrupt. Visit g.co/ABH), but now I have FRP issue
Vivjen said:
Push OTA. It works with locked bootloader. Recovered N6 from the same state (Your device is corrupt. Visit g.co/ABH), but now I have FRP issue
Click to expand...
Click to collapse
Tried that.
Verifying update package. . .
E: failed to verify whole-file signature
E: signature verification failed
Restarting adbd. . .
Installation aborted.
vicks1008 said:
Tried that.
Verifying update package. . .
E: failed to verify whole-file signature
E: signature verification failed
Restarting adbd. . .
Installation aborted.
Click to expand...
Click to collapse
Sure. You have no possibility to push current version installed as OTA update. Try to push beta Android N for example
Vivjen said:
Sure. You have no possibility to push current version installed as OTA update. Try to push beta Android N for example
Click to expand...
Click to collapse
My Nexus 6 is stuck at LMY48M & I tried pushing the latest Marshmallow OTA build MMB29X.
You need to flash OTA with newer bootloader. Not each OTA contain newer version. Anything else will not help. Have you tried to push N?
Why is your Nexus reported in Device Manager as a Samsung device? As someone who owns a Galaxy S4 as well as a Nexus, you cannot use the Samsung driver in place of the Nexus USB driver.
Change your driver to the Google-provided version and try again.
Vivjen said:
You need to flash OTA with newer bootloader. Not each OTA contain newer version. Anything else will not help. Have you tried to push N?
Click to expand...
Click to collapse
I can't even sign up for the Nexus Beta Program. I have to sign up from the Nexus 6.
Nexus root toolkit
this toolkit will do all the work for you. from wugfresh development
vicks1008 said:
I can't even sign up for the Nexus Beta Program. I have to sign up from the Nexus 6.
Click to expand...
Click to collapse
No. Just download OTA from PC and push it to N6 via adb sideload
joseppa87 said:
this toolkit will do all the work for you. from wugfresh development
Click to expand...
Click to collapse
Absolutely. It washed my dishes, took the dog for a walk, and helped me with my homework.
Vivjen said:
Push OTA. It works with locked bootloader. Recovered N6 from the same state (Your device is corrupt. Visit g.co/ABH), but now I have FRP issue
Click to expand...
Click to collapse
sIR, How did you push STOCK OTA and where did you get it from, Can you please tell me steps you followed in details?
Thank you for reading.
Yes, it is my own fault. I rooted yesterday, and installed a kernel today. All was fine until I tried to update to to the November update, never got that far.
I made sure to use the correct factory image for Magisk.
In adb i typed fastboot recovery, and my is now stuck on the google splash screen.
I can boot to fastboot, with the power button, and down arrow, and that's it.
fastboot devices, in adb does return the serial number.
I am unable to get beyond that. I know I'm softbricked.
Any suggestions would be appreciated.
Seems like you should be able to side load factory image
After about 20 tries, I was finally able to boot to recovery. I'm going to factory reset, and redo. Thanks for the help, though.
mimart7 said:
After about 20 tries, I was finally able to boot to recovery. I'm going to factory reset, and redo. Thanks for the help, though.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pi...-10-q-root-t3996969/post80774791#post80774791
Here is an update:
When I run adb devices, the serial number is not returned.
When I run fast devices, the serial number is returned.
I have extracted all the files from the zip, for the image, there is no boot.sig, recovery.img, system.sig, or vendor sig.
{
"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"
}
View attachment 4873031
mimart7 said:
Here is an update:
When I run adb devices, the serial number is not returned.
When I run fast devices, the serial number is returned.
I have extracted all the files from the zip, for the image, there is no boot.sig, recovery.img, system.sig, or vendor sig.
Click to expand...
Click to collapse
In adb mode in the OS, try typing..adb kill-server...
Then allow your device to always communicate with your pc, your having a driver issue. Your readout for your factory image is correct. There is no recovery anymore, it's tied in with the boot.img
mimart7 said:
Here is an update:
When I run adb devices, the serial number is not returned.
When I run fast devices, the serial number is returned.
I have extracted all the files from the zip, for the image, there is no boot.sig, recovery.img, system.sig, or vendor sig.
Click to expand...
Click to collapse
@mimart7
If you booted fastboot mode, fastboot devices is all that is needed to insure your phone is communicating with your computer.
Are you using the latest SDK platform-tools 29.0.5?
If yes, is the Platform-tools, and the extracted factory image files in this folder C:\Platform-tools\New folder?
I've got it working, thanks to all.
mimart7 said:
I've got it working, thanks to all.
Click to expand...
Click to collapse
How did you git it working if you dont mind coming to talk to me please.
https://discord.gg/XnMeYF6
DemonicMurderer said:
How did you git it working if you dont mind coming to talk to me please.
https://discord.gg/XnMeYF6
Click to expand...
Click to collapse
Did you have:
USB Debugging enabled?
Do you have Platform Tools?
https://developer.android.com/studio/releases/platform-tools
When in fastboot, and your phone is attached to your computer, and you type fastboot devices in adb, do you get your the serial number of your phone?
I'm in this situation and yes I have the lastest platform-tools. I do get the serial number back when I type fastboot devices. My folder location is C:\Platform-tools
Caselka said:
I'm in this situation and yes I have the lastest platform-tools. I do get the serial number back when I type fastboot devices. My folder location is C:\Platform-tools
Click to expand...
Click to collapse
What situation? SDK Platform-tools r29.0.6?
What are you trying to do?
Homeboy76 said:
What situation? SDK Platform-tools r29.0.6?
What are you trying to do?
Click to expand...
Click to collapse
Yup SDK r29.0.6.
I was soft-bricked and stuck in a boot loop.
I managed to get to recovery mode but only by flashing all the files then holding the power button & volume up button.
Once in recovery, I tried a million things to figure out how to get it back to a clean slate.
After hundreds of tries, I managed to sideload flame OTA.
The phone's bootloader is now unlocked.
Now going to focus on what I did wrong originally when trying to get Magisk on the Pixel 4 :laugh:
Caselka said:
Yup SDK r29.0.6.
I was soft-bricked and stuck in a boot loop.
I managed to get to recovery mode but only by flashing all the files then holding the power button & volume up button.
Once in recovery, I tried a million things to figure out how to get it back to a clean slate.
After hundreds of tries, I managed to sideload flame OTA.
The phone's bootloader is now unlocked.
Now going to focus on what I did wrong originally when trying to get Magisk on the Pixel 4 :laugh:
Click to expand...
Click to collapse
Search the pixel 4 thread.
Homeboy76 said:
Search the pixel 4 thread.
Click to expand...
Click to collapse
All done. Managed to successfully complete it
stuck in fastboot
Caselka said:
All done. Managed to successfully complete it
Click to expand...
Click to collapse
hi im also stuck in fastboot but no serial coming up under fastboot devices. was doing a flash-all.bat when it stopped halfway through and has been stuck ever since. cant go into recovery or anything. Any help would be appreciated.