umm, so i just unlock the bootloader and flash the twrp recovery.. Now i'm stuck in bootloop.
I can access bootloader and recovery, but i have no other file in my n10 as i just unlock it. The only way i can think of is to use adb push to push rom.zip file and flash it.
but, i don't really know exactly how to do adb push. So, can anyone please tell me? thanks
saryu said:
umm, so i just unlock the bootloader and flash the twrp recovery.. Now i'm stuck in bootloop.
I can access bootloader and recovery, but i have no other file in my n10 as i just unlock it. The only way i can think of is to use adb push to push rom.zip file and flash it.
but, i don't really know exactly how to do adb push. So, can anyone please tell me? thanks
Click to expand...
Click to collapse
from within recovery:
adb push rom.zip /sdcard/rom.zip
EDIT: when I unlocked the bootloader and flashed a custom recovery I also had boot loops. I flashed the factory images and that fixed things.
nvm, i just saw the guide on the bootloop stuck after unlock.. sry
Adb push to my sdcard is not working. Read-only? Really weird. Even installed insecure adbd to get root access for adb
Skickat från min HTC Desire via Tapatalk 2
Related
Tried to flash the deodexed stock 4.2.2 update through TWRP a few days ago and my N7 started bootlooping
Because I'm out of practice, I didn't make a nandroid beforehand, and now I can't locate the adb files necessary to push recovery and reflash the os.
Can someone help me remember what the f*ck I'm doing and direct me to where I can get an adb cheatsheet + the necessary files OR be super awesome and provide me some steps to follow?
Thanks so much in advance. Can't believe I messed this up so much
Trickee360 said:
Tried to flash the deodexed stock 4.2.2 update through TWRP a few days ago and my N7 started bootlooping
Because I'm out of practice, I didn't make a nandroid beforehand, and now I can't locate the adb files necessary to push recovery and reflash the os.
Can someone help me remember what the f*ck I'm doing and direct me to where I can get an adb cheatsheet + the necessary files OR be super awesome and provide me some steps to follow?
Thanks so much in advance. Can't believe I messed this up so much
Click to expand...
Click to collapse
Can you get into bootloader with power+vol down?
boot into the bootloader, then via fastboot..
fastboot boot recovery recoveryname.img(press enter)
remember to put the recovery img file in the same folder that fastboot is located, on your computer.
bootloader's good to go and I'm in recovery but I need a way to get the rom on my tablet. Mounting sdcard doesn't appear to do anything while connected to my pc
EDIT: tried the CWM flash from sideload option and my command line says it "cannot read 'sideload'" do I need to start/restart the server another way? I feel like a total noob, lol
adb push rom.zip /sdcard/
Pirateghost said:
adb push rom.zip /sdcard/
Click to expand...
Click to collapse
started the daemon then got error: closed
Trickee360 said:
started the daemon then got error: closed
Click to expand...
Click to collapse
Did you update your adb binary as expressed with the 4.2.2 update?
Sent from my Galaxy Nexus
Pirateghost said:
Did you update your adb binary as expressed with the 4.2.2 update?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
no Can I do that through the sdk manager or do I have to update the sdk itself?
sdk manager can handle it
Pirateghost said:
sdk manager can handle it
Click to expand...
Click to collapse
Ugh. SDK manager won't install anything. EIther it says whatever package I'm working on requires API17 (which I'm trying to get, lol) OR it just plain can't "find" the package because acces is denied? What am I doing wrong?
Guys help me!
I install android 4.3 on my phone, however I did not do the backup and by mistake I've downloaded the wrong rom, now my phone a message appears in the bootloader "in the OS installed"
I'm desperate with my phone only in recovery mode, please help me fix!
sprafael said:
Guys help me!
I install android 4.3 on my phone, however I did not do the backup and by mistake I've downloaded the wrong rom, now my phone a message appears in the bootloader "in the OS installed"
I'm desperate with my phone only in recovery mode, please help me fix!
Click to expand...
Click to collapse
Do you have a custom recovery installed? If so, load a .zip rom and push it via custom recovery...
.... If not, use ADB to push a reflash of a clean install of 4.3
instructions here my thread
http://forum.xda-developers.com/showthread.php?t=2376681
More info.what Phone mark modelo etc ?
Sent from my XT910 using Tapatalk 4 Beta
mc704 said:
Do you have a custom recovery installed? If so, load a .zip rom and push it via custom recovery...
.... If not, use ADB to push a reflash of a clean install of 4.3
instructions here my thread
http://forum.xda-developers.com/showthread.php?t=2376681
Click to expand...
Click to collapse
i do not have a custom recovery, the only thing it has in the cell and the image I downloaded wrong, my phone is in recovery screen that comes with it when I turn the volume button, after that I do not know what else to do, because I have no how to transfer the image to the correct cell to update, so I need to know how to transfer the image to the correct device
sprafael said:
i do not have a custom recovery, the only thing it has in the cell and the image I downloaded wrong, my phone is in recovery screen that comes with it when I turn the volume button, after that I do not know what else to do, because I have no how to transfer the image to the correct cell to update, so I need to know how to transfer the image to the correct device
Click to expand...
Click to collapse
if you are able to boot to recovery. you have to be in fast boot...
you can either use fastboot to flash over
or
boot into recovery and apply a rom via ADB sideload
mc704 said:
if you are able to boot to recovery. you have to be in fast boot...
you can either use fastboot to flash over
or
boot into recovery and apply a rom via ADB sideload
Click to expand...
Click to collapse
how to apply the room via ADB SIDE load, because I saw that option, so I do not know how to use
sprafael said:
how to apply the room via ADB SIDE load, because I saw that option, so I do not know how to use
Click to expand...
Click to collapse
open command prompt with adb loaded
type adb sideload romname.zip
the rom should be in the same folder the adb/fastboot tools are located
mc704 said:
open command prompt with adb loaded
type adb sideload romname.zip
the rom should be in the same folder the adb/fastboot tools are located
Click to expand...
Click to collapse
the fastboot do you explain this link??
http://forum.xda-developers.com/showthread.php?t=2376681
I'm downloading the android SDK at this time
let's see if I understand
put the phone in adb sideload
will open the CMD in the fastboot folder,
type in adb sideload image-occam-jwr66v.zip
Flashable zip not factory image, try cm10
Sent from my Nexus 4 using xda app-developers app
So I decided to install PA 4.6 BETA4 on my Nexus 4, 4.3 JWR66Y Phone which is unlocked and rooted. I used the Nexus Root Toolkit to install the latest TWRP recovery, put the pa_mako-4.6-BETA4-20141007.zip and pa_gapps-stock-4.4.4-20141011-signed.zip onto my phone. Went into recovery to flash the two. The PA ROM went successful, tried flashing the gapps and it just says failed. I tried redoing the ROM flash then gapps again but that doesn't work.
I had the dumb idea of moving my nandroid backup to my computer and now I can't transfer it back to my phone using adb sideload. I go into ADB sideload in TWRP, and it just says no devices found when trying to transfer maually. When I try using NRToolkit, it fails as well.
Any advice? I feel like I've searched everywhere. I don't know what the next step to take is. Maybe Flash Stock + Unroot option on the NRToolkit? Have I somehow flashed incompatible zip files?
sirmot said:
So I decided to install PA 4.6 BETA4 on my Nexus 4, 4.3 JWR66Y Phone which is unlocked and rooted. I used the Nexus Root Toolkit to install the latest TWRP recovery, put the pa_mako-4.6-BETA4-20141007.zip and pa_gapps-stock-4.4.4-20141011-signed.zip onto my phone. Went into recovery to flash the two. The PA ROM went successful, tried flashing the gapps and it just says failed. I tried redoing the ROM flash then gapps again but that doesn't work.
I had the dumb idea of moving my nandroid backup to my computer and now I can't transfer it back to my phone using adb sideload. I go into ADB sideload in TWRP, and it just says no devices found when trying to transfer maually. When I try using NRToolkit, it fails as well.
Any advice? I feel like I've searched everywhere. I don't know what the next step to take is. Maybe Flash Stock + Unroot option on the NRToolkit? Have I somehow flashed incompatible zip files?
Click to expand...
Click to collapse
UPDATE: I got the gapps to install successfully. I installed Wifi File Explorer through NRToolkit in order to transfer files to my phone. And transferred the same exact file to my phone. I tried flashing the file and it worked... I'm guessing the wired transfer corrupted the file somehow. Thank you NRT for that option to install apks.
Hi,
Good to know that you managed to get it working . Could you add a [SOLVED] tag on the title of your thread?
Also, I'd like to point out that when you tried to copy the backup file via adb sideload it had a reason to not work! Adb sideload was born to flash zips which are transfered via adb to the device. Loading then as soon as they are loaded. To copy the files back to your device using adb you should have used the "adb push" command, which is like a "copy/paste" on the shell . Hope this helps in the future.
~Lord
XxLordxX said:
Hi,
Good to know that you managed to get it working . Could you add a [SOLVED] tag on the title of your thread?
Also, I'd like to point out that when you tried to copy the backup file via adb sideload it had a reason to not work! Adb sideload was born to flash zips which are transfered via adb to the device. Loading then as soon as they are loaded. To copy the files back to your device using adb you should have used the "adb push" command, which is like a "copy/paste" on the shell . Hope this helps in the future.
~Lord
Click to expand...
Click to collapse
Ah of course that makes sense. I think I tried just pushing the file when I was in the bootloader as well, but it also gave me devices not found. Not sure why, but anyways thanks for the reply. Hopefully this might help out someone.
sirmot said:
Ah of course that makes sense. I think I tried just pushing the file when I was in the bootloader as well, but it also gave me devices not found. Not sure why, but anyways thanks for the reply. Hopefully this might help out someone.
Click to expand...
Click to collapse
Hi,
In bootloader you mean fastboot right? If so, you can't use adb on this mode. To push a file via fastboot is only the stock image using "fastboot install" or "fastboot boot".
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
XxLordxX said:
Hi,
In bootloader you mean fastboot right? If so, you can't use adb on this mode. To push a file via fastboot is only the stock image using "fastboot install" or "fastboot boot".
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
Click to expand...
Click to collapse
Oh I see. So the adb push can only be used when the phone is on normally and connected via adb? Is there a way to transfer files to a phone if it were stuck in fastboot?
sirmot said:
Oh I see. So the adb push can only be used when the phone is on normally and connected via adb? Is there a way to transfer files to a phone if it were stuck in fastboot?
Click to expand...
Click to collapse
Hi,
If you're stuck in fastboot you can flash a recovery or use the "fastboot boot" to boot in recovery and then use adb push from there .
~Lord
So the title pretty much says it all..
I have a Nexus 6P
Last night It got stuck in a bootloop. The only access I have to the device is it will launch into the boot loader. But no options work, factory, recovery do not work. USB Debugging was turned off, OEM unlock is turned off, developer options are on. But I have zero access to the android only the boot loader screen. Fastboot does work but it gives me "DEVICE IS LOCKED" on most commands. Oh and the icing on top is I'm on Android N 7.0 beta.
I've ordered a replacement, but I have all my personal data on the phone. I'd like to either fix it and get it working so I can get all my stuff off it. Or at very least try to wipe the device.
Also Fastboot Format, erase, do not work. It says Locked Device. HELP PLEASE. I can answer any more questions.
can you adb pull and push files?
If so, on your Windows machine, type this:
Code:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
It won't connect via ADB only Fastboot.
adb devices
List of devices attached
Wiltron said:
can you adb pull and push files?
If so, on your Windows machine, type this:
Code:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
Click to expand...
Click to collapse
Not sure if this will work, but try downloading the latest TWRP img file from their website, then running this command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
If you get it into recovery, then pull the files you need for a backup, and then use adb push to push a new ROM to the device.
Make sure you format all partitions/data.
Note: adb push should work better in recovery, vs. the command line that didn't work earlier.
What do you mean by "recovery doesn't work"? Please explain what happens when you boot into it.
Sent from my Nexus 5X using Tapatalk
an276123 said:
It won't connect via ADB only Fastboot.
adb devices
List of devices attached
Click to expand...
Click to collapse
Why not download stock Marshmallow and attempt to flash?
https://developers.google.com/android/nexus/images#angler
A locked bootloader should still allow you to flash a signed ROM.
An unlocked bootloader means you can boot and install anything.
Rule #1 If you are running *ANYTHING* other than an OTA, unlock the bootloader!
Unlocking the bootloader DOES NOT void the warranty.
Final note, it's encrypted. If you can't get into it, nobody interested in your data can.
Even if they can, it's block level encrypted. Who cares, no need to wipe.
SlimSnoopOS said:
What do you mean by "recovery doesn't work"? Please explain what happens when you boot into it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
When I click down and then power on recovery it should go into the recovery. But instead it just gets back into an endless loop of starting.
tech_head said:
Why not download stock Marshmallow and attempt to flash?
https://developers.google.com/android/nexus/images#angler
A locked bootloader should still allow you to flash a signed ROM.
An unlocked bootloader means you can boot and install anything.
Rule #1 If you are running *ANYTHING* other than an OTA, unlock the bootloader!
Unlocking the bootloader DOES NOT void the warranty.
Final note, it's encrypted. If you can't get into it, nobody interested in your data can.
Even if they can, it's block level encrypted. Who cares, no need to wipe.
Click to expand...
Click to collapse
On a side note. I am running stock android N 7.0 and it was OTA. I just didn't think to unlock it since it was all done OTA.
Thats what I'm thinking too on the data.
Wiltron said:
Not sure if this will work, but try downloading the latest TWRP img file from their website, then running this command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
If you get it into recovery, then pull the files you need for a backup, and then use adb push to push a new ROM to the device.
Make sure you format all partitions/data.
Note: adb push should work better in recovery, vs. the command line that didn't work earlier.
Click to expand...
Click to collapse
When I try to run this I get this.
downloading 'boot.img'...
OKAY [ 0.397s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time 0.421s
That means you need to unlock your bootloader, which should already be done, or if it's not, it will erase your internal storage.
You can unlock your bootloader, or try too, with
Code:
fastboot flashing unlock
Wiltron said:
That means you need to unlock your bootloader, which should already be done, or if it's not, it will erase your internal storage.
You can unlock your bootloader, or try too, with
Code:
fastboot flashing unlock
Click to expand...
Click to collapse
He said OEM unlock is turned off so that won't work.
So any luck to boot this sucker ? Don't even have stock recovery ..
have you tried "fastboot boot boot.img" from the correct factory image ?
Boot loop plus no recovery equals BLOD. Sorry but likely you are done.
I am following this guide here to root oneplus 6t (european variant), 9.0.5 Android:
https://www.xda-developers.com/onepl...otloader-root/
bootloader is unlocked and I can see there is a positive connection between phone and PC by checking the output on adb devices and fastboot devices. both work as intended.
the problem is that when I try to adb sideload, it says that I need version 1.0.32. so this means I cannot flash the custom recovery.
any tips? been looking online for quite some time now and cannot figure out what to do anymore. where can I find this 1.0.32 adb version?
I am a long time user on nexus 5 and just bought this phone, want to root it aswell. (note: this does not mean I have high level of knowledge on these types of hacks, just wanted to have this clear.)
Are you trying to boot or to flash the recovery from adb ? If you're trying to install the recovery from adb it wont work, on a/b devices the recovery is part of the boot image wich needs to be patched, boot twrp.img and then get the bluespark twrp zip and flash it.
nikexv2 said:
Are you trying to boot or to flash the recovery from adb ? If you're trying to install the recovery from adb it wont work, on a/b devices the recovery is part of the boot image wich needs to be patched, boot twrp.img and then get the bluespark twrp zip and flash it.
Click to expand...
Click to collapse
I can start the twrp, the problem is when I go into adb sideload and try to flash it. on pc is says "error" and on the phone it says I need to get adb 1.0.32. I am trying to flash that bluespark recovery with no luck.
cesar.maranhao said:
I can start the twrp, the problem is when I go into adb sideload and try to flash it. on pc is says "error" and on the phone it says I need to get adb 1.0.32. I am trying to flash that bluespark recovery with no luck.
Click to expand...
Click to collapse
You need to flash the zip from within the recovery that you booted using adb, not sideload it.
I already tried that, copied the files to the phone but when I try to access them through the bootable trwp, I cannot access them.
cesar.maranhao said:
I already tried that, copied the files to the phone but when I try to access them through the bootable trwp, I cannot access them.
Click to expand...
Click to collapse
wrong twrp used. you correct twrp and it will work. like this twrp https://forum.xda-developers.com/on...covery-theme-blacked-twrp-acuicultor-t3847752 or https://forum.xda-developers.com/devdb/project/?id=27466#downloads the choice is yours alone to make.
you are asking for help with 6t in the 6 form. whats wrong with this? you should be at this link https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482