[Q] ADB sideload fails? - General Questions and Answers

I recently rooted and installed Cyanogenmod 11(nightly) on my ls970. CM11 was a little glitchy so I decided to downgrade to CM 10.2... but my dumb*ss forgot to wipe CM 11 before I installed 10.2. needless to say it didn't work. I then did a full wipe(the backup I created didn't work) with TWRP and then tried to sideload Cyangogenmod 10.2.. the sideload fails.. so I thought it was an issue with the ROM..So I got the stock ROM from Google and tried to sideload that. The sideload always starts (on both ROMs) but always ends up failing in the end.. Any help would be appreciated.
I also tried to install stock rom via lgnpst but it does not recognize the phone. And all drivers are installed

Turdbasket said:
I recently rooted and installed Cyanogenmod 11(nightly) on my ls970. CM11 was a little glitchy so I decided to downgrade to CM 10.2... but my dumb*ss forgot to wipe CM 11 before I installed 10.2. needless to say it didn't work. I then did a full wipe(the backup I created didn't work) with TWRP and then tried to sideload Cyangogenmod 10.2.. the sideload fails.. so I thought it was an issue with the ROM..So I got the stock ROM from Google and tried to sideload that. The sideload always starts (on both ROMs) but always ends up failing in the end.. Any help would be appreciated.
I also tried to install stock rom via lgnpst but it does not recognize the phone. And all drivers are installed
Click to expand...
Click to collapse
How about copying the rom by just transfer the Rom.zip to scdard? I really never use adb sideload as there is really no reason to, except it has a chance to be not working...

LS.xD said:
How about copying the rom by just transfer the Rom.zip to scdard? I really never use adb sideload as there is really no reason to, except it has a chance to be not working...
Click to expand...
Click to collapse
The phone shows up on my computer but it's greyed out and says I need to insert a memory device. When I wiped the info to install the new rom I think I wiped too much (i wiped everything)

Turdbasket said:
The phone shows up on my computer but it's greyed out and says I need to insert a memory device. When I wiped the info to install the new rom I think I wiped too much (i wiped everything)
Click to expand...
Click to collapse
Which recovery version do you use at the moment?
This is the best recovery you can get --> http://goo.im/devs/philz_touch/CWM_Advanced_Edition/ls970
for your phone.
Install it using "fastboot".

LS.xD said:
Which recovery version do you use at the moment?
This is the best recovery you can get -->link
for your phone.
Install it using "fastboot".
Click to expand...
Click to collapse
I'm using twrp. I'll try what you suggest and let you know

LS.xD said:
Which recovery version do you use at the moment?
This is the best recovery you can get --> link
for your phone.
Install it using "fastboot".
Click to expand...
Click to collapse
when I try to install CWM it gives me this message:
Unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'

Turdbasket said:
when I try to install CWM it gives me this message:
Unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
Click to expand...
Click to collapse
Could you tell me what you exactly did?
The command must be "fastboot flash recovery recovery.img"
the recovery.img you extracted from the downloaded zip must be placed in "fastboot folder" of course.
If you're not sure about it pls post a screenshot of your command prompt so i can check it for errors.

LS.xD said:
Could you tell me what you exactly did?
The command must be "fastboot flash recovery recovery.img"
the recovery.img you extracted from the downloaded zip must be placed in "fastboot folder" of course.
If you're not sure about it pls post a screenshot of your command prompt so i can check it for errors.
Click to expand...
Click to collapse
That worked.(thank you very much) I was using the wrong command line. I thanked you for that bit of info. I have to go do some things... I'll be back in a bit to let you know how everything is going

Turdbasket said:
That worked.(thank you very much) I was using the wrong command line. I thanked you for that bit of info. I have to go do some things... I'll be back in a bit to let you know how everything is going
Click to expand...
Click to collapse
That would be kind of you

LS.xD said:
Could you tell me what you exactly did?
The command must be "fastboot flash recovery recovery.img"
the recovery.img you extracted from the downloaded zip must be placed in "fastboot folder" of course.
If you're not sure about it pls post a screenshot of your command prompt so i can check it for errors.
Click to expand...
Click to collapse
LS.xD said:
That would be kind of you
Click to expand...
Click to collapse
You solved my problem for me!! The issue was with TWRP!! Thank you so much for your help!

Related

What did I do to my phone? Please help.

On a mac here. I think I got a bit over my head here with the 2.20 root. I did all of the bootloader unlocking successfully, installed TWRP, and then downloaded CM10, and flashed the boot.img.
Now when trying to boot the phone I get stock on the screen with "This Build is for development only."
I can get into recovery, but don't really know what to do from there. I'm trying to mount, but can't get the computer to recognize the device. Tried a factory reset and it failed. I'm not quite bricked, but sort of stuck and don't know what to do. I'd love to get CM10 working, but at least I want to be able to use my phone.
I'm pretty new to Android so sorry for newbishness.
Thanks anyone for your help.
Just to add, I'm getting the message "no OS installed" when trying to reboot in recovery.
ul49 said:
On a mac here. I think I got a bit over my head here with the 2.20 root. I did all of the bootloader unlocking successfully, installed TWRP, and then downloaded CM10, and flashed the boot.img.
Now when trying to boot the phone I get stock on the screen with "This Build is for development only."
I can get into recovery, but don't really know what to do from there. I'm trying to mount, but can't get the computer to recognize the device. Tried a factory reset and it failed. I'm not quite bricked, but sort of stuck and don't know what to do. I'd love to get CM10 working, but at least I want to be able to use my phone.
I'm pretty new to Android so sorry for newbishness.
Thanks anyone for your help.
Click to expand...
Click to collapse
Did you flash the boot.img first, then the ROM?
Can you wipe System?
Sorry, what's the difference betwwen boot.img and the rom itself? I only flashed boot.img. I did wipe the system.
ul49 said:
Sorry, what's the difference betwwen boot.img and the rom itself? I only flashed boot.img. I did wipe the system.
Click to expand...
Click to collapse
The boot.img has the kernel in it. If you didn't flash the CM10.zip you have no operating system.
Wipe System, and Factory Reset
Flash boot.img
Flash the CM10.zip, flash google apps, and you should be good after that
Now flash the rom zip from recovery (twrp)
Sent from a slithery smooth phone!
So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help
ul49 said:
So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help
Click to expand...
Click to collapse
no,you flash the boot.img in fastboot, and then you flash the rom.zip and gapps.zip from recovery (twrp)
ul49 said:
So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help
Click to expand...
Click to collapse
No, do a clean wipe.
boot your phone into fastboot
download the fastboot files http://www.mediafire.com/?4dx982z93w8z7wk and extract them to your desktop
on your computer, open up cmd and type
cd desktop
cd foldername (the folder that has fastboot.exe)
fastboot flash boot boot.img
reboot into recovery
flash CM10, flash gapps, reboot
I see. The problem is that I seem to be unable to mount my phone and sd card through recovery.
Trying to push the zips using adb using './adb push cm10.zip/sdcard' but when I enter this command in terminal it seems to just reload adb, and not push the file.
ul49 said:
Trying to push the zips using adb using './adb push cm10.zip/sdcard' but when I enter this command in terminal it seems to just reload adb, and not push the file.
Click to expand...
Click to collapse
I think you are typing the command wrong
./adb push file /destination
or ./adb push cm10.zip /mnt/sdcard
./adb push cm10.zip /sdcard
whatever the mount point is for the sdcard
Tried that too. It just reloads the opening adb dialogue.
ul49 said:
Tried that too. It just reloads the opening adb dialogue.
Click to expand...
Click to collapse
does ./adb devices return your phone as connected?
Well, now it doesn't. Instead of reloading the adb dialogue now, when I try the push command it says device not found. Just came out of nowhere. How do I make it recognize the phone again?
Thanks for bearing with me here. I think I'm really close.
ul49 said:
Well, now it doesn't. Instead of reloading the adb dialogue now, when I try the push command it says device not found. Just came out of nowhere. How do I make it recognize the phone again?
Thanks for bearing with me here. I think I'm really close.
Click to expand...
Click to collapse
I'm not familiar with OS X and android, are there any specific drivers you may need to install?
Are you in your bootloader or recovery?
All necessary drivers were installed. The device was being recognized before, but for some reason isn't now. I'm stuck on the "This build is for development purposes only" screen now since I can't get into recovery or bootloader using adb now since the device isn't recognized...
Ok, I'm connected again somehow. Now just trying to figure out this pushing issue. Entered this command './adb push /android/cm10.zip /sdcard and it looked like it was working then said "failed to copy to /sdcard"
ul49 said:
Ok, I'm connected again somehow. Now just trying to figure out this pushing issue. Entered this command './adb push /android/cm10.zip /sdcard and it looked like it was working then said "failed to copy to /sdcard"
Click to expand...
Click to collapse
because it is probably at /mnt/sdcard
Successfully pushed the files. Of course, I've hit another problem. Trying to install the ROM through TWRP and it's failing. Same with Gapps. I'm seeing "unable to mount /sdcard" and unable to mount storage. I've already cleared cache, wiped system, factory reset/

TWRP (wathever the version) ask a Password

I really don't know why and when, but i've upgrade my TWRP to the new one... and now when i enter in TWRP, they asking for a password... but i've NEVER set a password. I've try to downgrade to few older TWRP, the same password page again.
My bootloader is unlock, i'm on 4.2.1, but how to get rid of this freaking password in TWRP?
You're help is very needed
Rambytes said:
...they asking for a password... but i've NEVER set a password...
Click to expand...
Click to collapse
Mainly it happens when You go to TWRP after flashing it without reboot. Reboot should fix it, if not - reboot tablet after flashing TWRP.
Rambytes said:
I really don't know why and when, but i've upgrade my TWRP to the new one... and now when i enter in TWRP, they asking for a password... but i've NEVER set a password. I've try to downgrade to few older TWRP, the same password page again.
My bootloader is unlock, i'm on 4.2.1, but how to get rid of this freaking password in TWRP?
You're help is very needed
Click to expand...
Click to collapse
Happened to me when I flashed the wrong version of TWRP because I put it in the wrong spot.
cmendonc2 said:
Happened to me when I flashed the wrong version of TWRP because I put it in the wrong spot.
Click to expand...
Click to collapse
Ok and what the solution? Reboot after the flash of TWRP (in fastboot mode) don't solve the problem
Rambytes said:
Ok and what the solution? Reboot after the flash of TWRP (in fastboot mode) don't solve the problem
Click to expand...
Click to collapse
Well what had happened to me was I already had an old version of TWRP on my internal memory and I put the new version on my SD card which I wanted to flash. When I flashed twrp.blob, it flashed a very old version with an incompatible bootloader (whoops) which gave me the password error. So I put the new version on my internal memory, flashed twrp.blob again, and it worked.
cmendonc2 said:
Well what had happened to me was I already had an old version of TWRP on my internal memory and I put the new version on my SD card which I wanted to flash. When I flashed twrp.blob, it flashed a very old version with an incompatible bootloader (whoops) which gave me the password error. So I put the new version on my internal memory, flashed twrp.blob again, and it worked.
Click to expand...
Click to collapse
Ok, I can now booting in TWRP, but why they can't mount nothing????
Rambytes said:
Ok, I can now booting in TWRP, but why they can't mount nothing????
Click to expand...
Click to collapse
mount manually from TWRP settings, just mount what you need.
cmendonc2 said:
mount manually from TWRP settings, just mount what you need.
Click to expand...
Click to collapse
I've do something wrong again.... i'm stuck in the password section...
To trying to reset the password problem, i've flash the older blob i've found on TWRP, the 2.1.4. reboot the tablet, trying to enter in the RCK section, nothing append, like a freeze... so I reboot, flash the newer blob, the 2.6.3.0... reboot... enter in the RCK, and always the password...
i'm going crazy... i'm about to slam the tablet! :silly::crying:
Rambytes said:
I've do something wrong again.... i'm stuck in the password section...
To trying to reset the password problem, i've flash the older blob i've found on TWRP, the 2.1.4. reboot the tablet, trying to enter in the RCK section, nothing append, like a freeze... so I reboot, flash the newer blob, the 2.6.3.0... reboot... enter in the RCK, and always the password...
i'm going crazy... i'm about to slam the tablet! :silly::crying:
Click to expand...
Click to collapse
delete the 2.1.4 trwp from your tablet altogether
The do this exactly from fastboot:
Download the file, check the md5, rename to twrp.blob and put the file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere). Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm). The device will now be in fastboot mode. Plug the device into your computer. Run the following command via the command line:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
Click to expand...
Click to collapse
So put the 2.6 -42 TWRP in your fastboot folder, then run the command.
cmendonc2 said:
delete the 2.1.4 trwp from your tablet altogether
The do this exactly from fastboot:
So put the 2.6 -42 TWRP in your fastboot folder, then run the command.
Click to expand...
Click to collapse
2.6 -42 ?????
and I don't have the usb icon on the VOL- and POWER menu.... but at this screen, I can do fastboot command....
There is a way that can whe chat togheter live on facebook or wathever? Please don't stop to help me, it's very important... Never have problem with my N7 (2013) but this one TF300t is gouing very bad)
[solve] TWRP (wathever the version) ask a Password
ok, i will try to resart form the beginning.
The driver in windows is installed. When i'm on android, I can copy and see the tablet in the explorer. When i reboot the tablet in bootloader mode, again in windows I see a "android device in bootloader", Fastboot command work when I try fastboot -devices, I see the device.
I'm on 4.2.1 but I need to reflash and wipe all the data to install a better custom rom, I know TWRP because i'm using it on my N7...
It's after that... that going really bad for me and I don't know why.....
Can I try to flash with ClockwokMod instead TWRP? Wathever the recovery, I just want to flash a rom inside the TF300T...
Rambytes said:
ok, i will try to resart form the beginning.
The driver in windows is installed. When i'm on android, I can copy and see the tablet in the explorer. When i reboot the tablet in bootloader mode, again in windows I see a "android device in bootloader", Fastboot command work when I try fastboot -devices, I see the device.
It's after that... that going really bad for me and I don't know why.....
Click to expand...
Click to collapse
OK put the twrp 2.6.3.0 file in the folder platform-tools. Rename it to twrp.blob. Then run the command:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
cmendonc2 said:
OK put the twrp 2.6.3.0 file in the folder platform-tools. Rename it to twrp.blob. Then run the command:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
Click to expand...
Click to collapse
Just to be sure, I take the JB version (because i'm on 4.2.1 right)?
OK... I've see my error..... I din't see there is a "special version" of TWRP, the 2.6.3.0 - 4.2......
Ho man... i feel like a big looser!!!!! Ho man very sorry...
Rambytes said:
OK... I've see my error..... I din't see there is a "special version" of TWRP, the 2.6.3.0 - 4.2......
Ho man... i feel like a big looser!!!!! Ho man very sorry...
Click to expand...
Click to collapse
yeah thats what i meant by -42 earlier
did that work?
cmendonc2 said:
yeah thats what i meant by -42 earlier
did that work?
Click to expand...
Click to collapse
yes!!! Working very good! Thanks!
Do you have a good custom rom to suggest? I'm download the CM10.2, but do you have another and/or better one?
Rambytes said:
yes!!! Working very good! Thanks!
Do you have a good custom rom to suggest? I'm download the CM10.2, but do you have another and/or better one?
Click to expand...
Click to collapse
I have a preference towards PAC-man since it combines the features of three of the most popular custom Roms

[Q] 2 Issues when rooting: No SU binary installed, & red triangle on dead android.

[Q] 2 Issues when rooting: No SU binary installed, & red triangle on dead android.
This is my second root ever, I am still very new to this process but my first root went smoothly.
So basically the problem started when I copied the SuperSU file onto my phone using the command
adb push UPDATE-SuperSU-vX.XX.zip /sdcard/
Click to expand...
Click to collapse
After that, I tried finding the zip file through the TWRP recovery screen but I couldn't. I figured I'd go reboot my device. Once I pressed on reboot, a screen popped up asking if I wanted to install SuperSU, "ok cool" I thought and swiped to the right to install. At this point I thought my phones rooted.
I open up SuperSU and I get the error message:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!
Click to expand...
Click to collapse
I'm on 4.2.2
I decided to go back to recovery mode and that's when I saw the red triangle over the dead android. I thought I had bricked my phone but i'm back to my regular home screen.
Can anyone help me please?
How did you apply TWRP? Did you boot it or flash it. If you chose to boot it, the custom recovery won't stick.
The dead android you are seeing is the stock recovery.
My advice is to boot back into the bootloader and flash the recovery, then flash the SU,zip
FrostedFluke said:
This is my second root ever, I am still very new to this process but my first root went smoothly.
So basically the problem started when I copied the SuperSU file onto my phone using the command
After that, I tried finding the zip file through the TWRP recovery screen but I couldn't. I figured I'd go reboot my device. Once I pressed on reboot, a screen popped up asking if I wanted to install SuperSU, "ok cool" I thought and swiped to the right to install. At this point I thought my phones rooted.
I open up SuperSU and I get the error message:
I'm on 4.2.2
I decided to go back to recovery mode and that's when I saw the red triangle over the dead android. I thought I had bricked my phone but i'm back to my regular home screen.
Can anyone help me please?
Click to expand...
Click to collapse
The red triangle with the android is just the stock recovery. What commands are you using to flash TWRP? I'm assuming you unlocked the boot loader.
You should type in "fastboot flash recovery name_of_twrp_file.img"
Download the supersu.zip from http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip and put it on your phone while the phone is on and connected to a computer. (Just drag it in)
Then reboot into TWRP and flash that file.
Say NO..again NO to the part when it asks you if you want to root. It shouldn't ask you, but if it does, say no.
El Daddy said:
How did you apply TWRP? Did you boot it or flash it. If you chose to boot it, the custom recovery won't stick.
The dead android you are seeing is the stock recovery.
My advice is to boot back into the bootloader and flash the recovery, then flash the SU,zip
Click to expand...
Click to collapse
I used this guide http://forum.xda-developers.com/showthread.php?t=2507905
and by flashing the recovery, you mean by reflashing it? using "flashboot flash recovery recovery.img" as the command?
aooga said:
The red triangle with the android is just the stock recovery. What commands are you using to flash TWRP? I'm assuming you unlocked the boot loader.
You should type in "fastboot flash recovery name_of_twrp_file.img"
Download the supersu.zip from http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip and put it on your phone while the phone is on and connected to a computer. (Just drag it in)
Then reboot into TWRP and flash that file.
Say NO..again NO to the part when it asks you if you want to root. It shouldn't ask you, but if it does, say no.
Click to expand...
Click to collapse
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
FrostedFluke said:
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
Maybe, try using the new zip. Flash TWRP again. It shouldn't be going back to the stock recovery when you reboot unless you chose to just boot it and not flash it.
FrostedFluke said:
I used this guide http://forum.xda-developers.com/showthread.php?t=2507905
and by flashing the recovery, you mean by reflashing it? using "flashboot flash recovery recovery.img" as the command?
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
Yep, that is the correct command. I would recommend using the most recent SU.zip as well.
aooga said:
Maybe, try using the new zip. Flash TWRP again. It shouldn't be going back to the stock recovery when you reboot unless you chose to just boot it and not flash it.
Click to expand...
Click to collapse
I'll install the SuperSU you linked to me thanks! would you mind explaining to me how to flash it again?
I just open bootloader, command window then flash the recovery file once more?
FrostedFluke said:
I'll install the SuperSU you linked to me thanks! would you mind explaining to me how to flash it again?
I just open bootloader, command window then flash the recovery file once more?
Click to expand...
Click to collapse
Yeah just download THIS FILE first then boot into the bootloader and type in "fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img" without the quotes in a CMD window.
After it says finished, use the volume keys to select "Recovery Mode" and press the power button to go into it. Then flash the supersu file that you transferred earlier. (the new version).
aooga said:
Yeah just download THIS FILE first then boot into the bootloader and type in "fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img" without the quotes in a CMD window.
After it says finished, use the volume keys to select "Recovery Mode" and press the power button to go into it. Then flash the supersu file that you transferred earlier. (the new version).
Click to expand...
Click to collapse
I'm in Recovery mode and I still can't find the SuperSU zip file even after i've used the command "adb push"
FrostedFluke said:
I'm in Recovery mode and I still can't find the SuperSU zip file even after i've used the command "adb push"
Click to expand...
Click to collapse
Try adb sideloading it.
Put the Su.zip on your computer in the same folder as your adb.exe
Choose adb sideload on twrp.
Then the command: adb sideload SU.zip
El Daddy said:
Try adb sideloading it.
Put the Su.zip on your computer in the same folder as your adb.exe
Choose adb sideload on twrp.
Then the command: adb sideload SU.zip
Click to expand...
Click to collapse
you mean "adb sideload UPDATE-SuperSU-v1.89.zip"? (sorry I just want to be 100% sure so I make no mistakes)
FrostedFluke said:
you mean "adb sideload UPDATE-SuperSU-v1.89.zip"? (sorry I just want to be 100% sure so I make no mistakes)
Click to expand...
Click to collapse
Yep! I didn't know what the file was named so I just shortened it up to SU.zip
Pro-tip: You can rename files to something shorter such as SU.zip to make it quicker to type in command and eliminate the possibility of mistakes.
El Daddy said:
Yep! I didn't know what the file was named so I just shortened it up to SU.zip
Pro-tip: You can rename files to something shorter such as SU.zip to make it quicker to type in command and eliminate the possibility of mistakes.
Click to expand...
Click to collapse
I get this on my command prompt: "error: closed"
FrostedFluke said:
I get this on my command prompt: "error: closed"
Click to expand...
Click to collapse
run the command: adb usb
Then try sideloading
El Daddy said:
run the command: adb usb
Then try sideloading
Click to expand...
Click to collapse
same error.
I have the option to "swipe to start sideloading" should I swipe first? then run the command?
FrostedFluke said:
same error.
I have the option to "swipe to start sideloading" should I swipe first? then run the command?
Click to expand...
Click to collapse
yes
El Daddy said:
yes
Click to expand...
Click to collapse
It worked, thanks so much man I appreciate the help! you're a lifesaver!
one other quick question. Just to be sure, is there anyway of knowing whether or not my device has been rooted? how will I know for sure?
FrostedFluke said:
It worked, thanks so much man I appreciate the help! you're a lifesaver!
one other quick question. Just to be sure, is there anyway of knowing whether or not my device has been rooted? how will I know for sure?
Click to expand...
Click to collapse
You are welcome. I am always glad to help someone doing things the right way!
Run an app that requires root. If SuperSu requests access, you are rooted.
El Daddy said:
You are welcome. I am always glad to help someone doing things the right way!
Run an app that requires root. If SuperSu requests access, you are rooted.
Click to expand...
Click to collapse
Yup! it's rooted :victory:
FrostedFluke said:
Yup! it's rooted :victory:
Click to expand...
Click to collapse
Congrats!

[Q]bootloop when going to new ROM

hi,
i wanted to flash a custom rom(SOKP). so first i did a factory reset, then i tried to flash the rom but it aborted. i wiped cache and tried to boot my phone up because i wanted to install a different zip(maybe something went wrong while downloading). now my phone does not boot any more. it stays in the PA bootanimation. my pc does not recognize the phone anymore. it can only go into fastboot mode and recovery mode. another factory reset doesn't work. what can i do now?
greets, jamie
chimmychenga said:
hi,
i wanted to flash a custom rom(SOKP). so first i did a factory reset, then i tried to flash the rom but it aborted. i wiped cache and tried to boot my phone up because i wanted to install a different zip(maybe something went wrong while downloading). now my phone does not boot any more. it stays in the PA bootanimation. my pc does not recognize the phone anymore. it can only go into fastboot mode and recovery mode. another factory reset doesn't work. what can i do now?
greets, jamie
Click to expand...
Click to collapse
Download the zip again on pc and transfer it to phone using adb push command in recovery.
varuntis1993 said:
Download the zip again on pc and transfer it to phone using adb push command in recovery.
Click to expand...
Click to collapse
thanks but the prompt is saying that it's a read only file system
chimmychenga said:
thanks but the prompt is saying that it's a read only file system
Click to expand...
Click to collapse
what recovery are u using? And what rom are u pushing?
And use this command
Code:
adb push /pathonpc /sdcard
varuntis1993 said:
change its owner than on pc and what recovery are u using? And what rom are u pushing?
And use this command
Code:
adb push /pathonpc /sdcard
Click to expand...
Click to collapse
i'm using CWM and i try to install 'SOKP-RC-01-20140401-hammerhead.zip' it's a stable release of Audio god.
chimmychenga said:
i'm using CWM and i try to install 'SOKP-RC-01-20140401-hammerhead.zip' it's a stable release of Audio god.
Click to expand...
Click to collapse
I think you wrote the command wrong. Can you show a screen shot of command promt?
EDIT-also type adb root to see whether it is running as root or not
now i got a prompt with the copy speed but nothing is copied:S
chimmychenga said:
now i got a prompt with the copy speed but nothing is copied:S
Click to expand...
Click to collapse
did it say successful? It would be better if u share a screenshot
Check in your sd card
tthis is what i get
chimmychenga said:
tthis is what i get
Click to expand...
Click to collapse
It has successfully copied....reboot ur recovery and go to download folder and see if the file exists or not.
EDIT- I just checked ur screenshot again...it shows around 162 MB file but the file size should be around 300 MB
Download it again or flash the stock files to go back to stock
varuntis1993 said:
It has successfully copied....reboot ur recovery and go to download folder and see if the file exists or not.
EDIT- I just checked ur screenshot again...it shows around 162 MB file but the file size should be around 300 MB
Download it again or flash the stock files to go back to stock
Click to expand...
Click to collapse
i finally got it installed. i made a stupid mistake i unmounted /system and usb storage. i did a adb sideload and it succesfully installed. thanks for the replies BTW:laugh:

Flashfire can't see my zip

I am trying to use Flashfire v0.53 to update my Google-sourced, rooted Pixel from 7.1.0 (build NDE63X) to 7.1.1 (build NMF26V). I've downloaded sailfish-ota-nmf26v-1988a458.zip to my phone and can see it with a root file browser but when I direct Flashfire to the same directory it lists no files. Any thoughts? If I'm going about updating my phone the wrong way, I'm happy to be pointed in the right direction. Thanks.
FlashFire is not working on this phone last I heard. Flash it with TWRP.
TonikJDK said:
FlashFire is not working on this phone last I heard. Flash it with TWRP.
Click to expand...
Click to collapse
Good to know, thanks.
I've tried pointing TWRP at the OTA zip I got from Google and it fails. Perhaps because I need to unroot first? I was hoping Flashfire would do that for me. `adb sideload` failed, too.
ChrisNelsonPE said:
Good to know, thanks.
I've tried pointing TWRP at the OTA zip I got from Google and it fails. Perhaps because I need to unroot first? I was hoping Flashfire would do that for me. `adb sideload` failed, too.
Click to expand...
Click to collapse
You need to use fastboot. There are a few detailed guides in the "guides" section of both the pixel and pixel xl forums.
Basically you have to edit the flashall.bat file and remove the -w option so that it doesn't wipe. Then you have to fastboot boot into twrp then reflash twrp.zip and SU.zip
All the info is here just look around
aholeinthewor1d said:
You need to use fastboot. There are a few detailed guides in the "guides" section of both the pixel and pixel xl forums.
Basically you have to edit the flashall.bat file and remove the -w option so that it doesn't wipe. Then you have to fastboot boot into twrp then reflash twrp.zip and SU.zip
All the info is here just look around
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187 seems promising. I can adapt to use sailfish vs. marlin. But I'm not sure how to know which image is for Verizon.
ChrisNelsonPE said:
Good to know, thanks.
I've tried pointing TWRP at the OTA zip I got from Google and it fails. Perhaps because I need to unroot first? I was hoping Flashfire would do that for me. `adb sideload` failed, too.
Click to expand...
Click to collapse
Copy the OTA zip you downloaded, from your phone to your computer. Reboot into TWRP. Go to Advanced and choose "ADB sideload"(not sure if that's exactly what it's called). Once the phone is waiting for ADB, go back to your computer and open a command prompt and type "adb sideload OTA.zip". OTA.zip will be the zip you downloaded. Example: if you copied it to C:\ you would type "adb sideload c:\sailfish-ota-nmf26-xxxxxxxx.zip" or whatever the zip is named.
That is how you would sideload an OTA. If you downloaded a full factory image then open "flash-all.bat" in notepad, remove the "-w"(it's towards the bottom), connect your phone, reboot to bootloader, run flash-all.bat.
Both a full image and OTA will remove your root and TWRP. You will need to re flash recovery and reroot after updating. Just follow the same guides you did originally.
fritzgerald said:
Copy the OTA zip you downloaded, from your phone to your computer. Reboot into TWRP. Go to Advanced and choose "ADB sideload"(not sure if that's exactly what it's called). Once the phone is waiting for ADB, go back to your computer and open a command prompt and type "adb sideload OTA.zip". OTA.zip will be the zip you downloaded. Example: if you copied it to C:\ you would type "adb sideload c:\sailfish-ota-nmf26-xxxxxxxx.zip" or whatever the zip is named.
That is how you would sideload an OTA. If you downloaded a full factory image then open "flash-all.bat" in notepad, remove the "-w"(it's towards the bottom), connect your phone, reboot to bootloader, run flash-all.bat.
Both a full image and OTA will remove your root and TWRP. You will need to re flash recovery and reroot after updating. Just follow the same guides you did originally.
Click to expand...
Click to collapse
I don't seem to be able to find the OTA on my phone. Not sure where it gets put.
From your description of using the full image, I imagine I 1) unzip the factory image zip, 2) edit the flash-all.bat in the result, 3) run flash-all.bat (that is, I don't rezip and try to use the package). Right?
ChrisNelsonPE said:
I don't seem to be able to find the OTA on my phone. Not sure where it gets put.
From your description of using the full image, I imagine I 1) unzip the factory image zip, 2) edit the flash-all.bat in the result, 3) run flash-all.bat (that is, I don't rezip and try to use the package). Right?
Click to expand...
Click to collapse
That's correct. If you downloaded the OTA with System Updates then I'm not sure where it gets stored. If you downloaded it from Google then it would be in your downloads folder.
You can try the guide I wrote here to sideload the full ota zip from google.
adb sideload failure
spiller37 said:
You can try the guide I wrote here to sideload the full ota zip from google.
Click to expand...
Click to collapse
That's a great guide. Alas, when I try to sideload the OTA I get:
Code:
PS C:\adb> adb sideload .\sailfish-ota-nmf26u-6ea22a0c.zip
loading: '.\sailfish-ota-nmf26u-6ea22a0c.zip'
error: closed
PS C:\adb> adb sideload .\sailfish-ota-nmf26u-6ea22a0c.zip
loading: '.\sailfish-ota-nmf26u-6ea22a0c.zip'
error: device '(null)' not found
I though the problem might be the old TWRP in my phone so I used the alpha2 I had to install rc1.
ChrisNelsonPE said:
That's a great guide. Alas, when I try to sideload the OTA I get:
I though the problem might be the old TWRP in my phone so I used the alpha2 I had to install rc1.
Click to expand...
Click to collapse
Sounds like the driver isn't recognized. Does ADB devices list your device?
ChrisNelsonPE said:
...
I though the problem might be the old TWRP in my phone so I used the alpha2 I had to install rc1.
Click to expand...
Click to collapse
Now I'm in a boot loop. TWRP -- when it comes up at all -- says it is alpha2 and it doesn't prompt for the code to decrypt my data so the directory listing is gibberish. What do I do now? Reflash 7.0? Flash 7.1?
To recap, I have a Pixel I bought from Google with an unlocked boot loader and TWRP installed but can't boot to Android.
ChrisNelsonPE said:
Now I'm in a boot loop. TWRP -- when it comes up at all -- says it is alpha2 and it doesn't prompt for the code to decrypt my data so the directory listing is gibberish. What do I do now? Reflash 7.0? Flash 7.1?
To recap, I have a Pixel I bought from Google with an unlocked boot loader and TWRP installed but can't boot to Android.
Click to expand...
Click to collapse
Alpha 2 is the wrong TWRP. You want RC1.
ChrisNelsonPE said:
That's a great guide. Alas, when I try to sideload the OTA I get:
Code:
PS C:\adb> adb sideload .\sailfish-ota-nmf26u-6ea22a0c.zip
loading: '.\sailfish-ota-nmf26u-6ea22a0c.zip'
error: closed
PS C:\adb> adb sideload .\sailfish-ota-nmf26u-6ea22a0c.zip
loading: '.\sailfish-ota-nmf26u-6ea22a0c.zip'
error: device '(null)' not found
I though the problem might be the old TWRP in my phone so I used the alpha2 I had to install rc1.
Click to expand...
Click to collapse
That looks like an ADB device driver problem. Do you see your device listed with ADB devices when in TWRP/Advanced/Sideload?
spiller37 said:
That looks like an ADB device driver problem. Do you see your device listed with ADB devices when in TWRP/Advanced/Sideload?
Click to expand...
Click to collapse
Yes.
TonikJDK said:
Alpha 2 is the wrong TWRP. You want RC1.
Click to expand...
Click to collapse
That's fine. But how do I get there from a phone which is in a boot loop running alpha1?
ChrisNelsonPE said:
That's fine. But how do I get there from a phone which is in a boot loop running alpha1?
Click to expand...
Click to collapse
I get into TWRP on my phone an do
Code:
PS C:\adb> fastboot .\twrp-3.0.2-0-RC1-fastboot-sailfish.img
< waiting for device >
on my computer and it waits forever.
ChrisNelsonPE said:
That's fine. But how do I get there from a phone which is in a boot loop running alpha1?
Click to expand...
Click to collapse
Power it down, hold power button and volume down to get it into fastboot.
Fastboot flash TWRPfilename.img
And if that does not work download the full factory image but edit flashall.bat to remove the -w which will save your data and flash the whole thing.
TonikJDK said:
...
And if that does not work download the full factory image but edit flashall.bat to remove the -w which will save your data and flash the whole thing.
Click to expand...
Click to collapse
So, I think I had to do this. `adb` lists my device but when I try to sideload it says the device (null) doesn't exist.
Do I somehow tell `fastboot` to use the factory image .zip file or do I unzip it, edit flashall.bat, then run flashall.bat?
ChrisNelsonPE said:
So, I think I had to do this. `adb` lists my device but when I try to sideload it says the device (null) doesn't exist.
Do I somehow tell `fastboot` to use the factory image .zip file or do I unzip it, edit flashall.bat, then run flashall.bat?
Click to expand...
Click to collapse
Unzip it into your fastboot directory. Then edit and run flashall.

Categories

Resources