Hi,
i have a nexus one with a broken power button, my warranty is out so there is no replacement, i want to root it to be able to install trackball wake s,o i can open the mobile and close it.
when i try to access the bootloader i hold the trackball then i take off the battery 2 to 3 time to switch on, and if i keep holding the trackball it access the bootloader screen.
but i can't choose bootloader because i need to use the power button to do so, i also tried the universal androot, i got a message saying failed! no ~~~fu goo~~~.
my OS version is 2.2.2, build number FRG83G.
please any help.
You can try manual root. I find it easier getting the drivers to install when the phone is in fastboot, but it isn't essential...
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App
If you hold Vol Up + Track Ball and Remove & Insert your battery while your plug in to USB cable you can access Fastboot screen. But you will not be able to select any options because it needs power switch to select options.
many thanks danger-rat, i got a superuser access now on my list
i need one more thing if you please, how can i install cyanogenmod? because as i mentioned before i need trackball wake setting.
best regards,
The quickest way in my opinion is to install ROM manager from the market. You can then choose to install either Clockwork recovery image or Amon_RA. If you choose Clockwork then you can use ROM manager to automate backing up/flashing of new ROMs. Alternatively you can choose Amon_RA recovery, which I personally use. There are only a few differences other than layout but both are excellent recoveries.
Once you've installed a recovery image, you can either download CM7 manually and place it on your SD card or use ROM manager to download it. Depending on your choice of recovery you can use ROM manager to backup then flash or alternatively go into recovery manually and flash CM7 there. To reboot directly to recovery either hook the phone up to a PC and issue the command 'adb reboot recovery' or alternatively install an application like Quickboot which does the exact same thing through a GUI.
You shouldn't really have any problems once you've flash CM7 as it has a reboot to recovery option built in. Good luck
Edit: Oh and always, I repeat always Nandroid! It'll save you any headaches.
thanks man for the guide, it worked wonderfully, but what do Nandroid do?!
omarqa said:
thanks man for the guide, it worked wonderfully, but what do Nandroid do?!
Click to expand...
Click to collapse
It's like imaging software for a PC, it takes a screenshot of your system at that time which can then be restored should anything go awry. I have a couple that I switch between
Bootloop cyanogen
Hi all,
after all your help guys i managed to get my self into trouble again , after i installed cyanogen i found out that the market is not there, and i couldn't add gmail account also, so i recovered the previous one.
i thought I'd reinstalled cyanogen again, so after a couple of failures in installing it "getting an android with and explanation mark over the head", the last one worked but it booted into a boot loop, i keep getting the cyanogen screen again and again.
can i do something with command line such as adb shell
best regards,
I ran into the same problem, it's a little long winded but I found this to work. Also, it seems your recovery is reverting to stock. This is because of files recovery-from-boot.p and install-recovery.sh. After flashing the ROM go to terminal and issue the following commands (Without #) :
# su (Making sure to accept the root privileges prompt)
# mount -o remount,rw /dev/null /system
# mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# reboot
More info here.
Then flash Amon_RA recovery or Clockwork during fastboot commands from my first link. Rename the image downloaded to recovery and issue the following command during fastboot:
fastboot flash recovery recovery.img
You can then follow the rest of the guide to return to recovery. If you ever end up in a bootloop again just follow the guide in the first link as is and you'll be back in recovery to recover a nandroid backup or flash again.
Also it seems you're missing the Googleapps (Gapps) package for Gingerbread. Flash this after flashing CM7.
omarqa said:
Hi all,
after all your help guys i managed to get my self into trouble again , after i installed cyanogen i found out that the market is not there, and i couldn't add gmail account also, so i recovered the previous one.
i thought I'd reinstalled cyanogen again, so after a couple of failures in installing it "getting an android with and explanation mark over the head", the last one worked but it booted into a boot loop, i keep getting the cyanogen screen again and again.
can i do something with command line such as adb shell
best regards,
Click to expand...
Click to collapse
Did you flash a compatible gapps package (Google apps)? The market and other Google apps are not distributed with Cyanogen ROMs, and have to be flashed separately...
Edit: Sorry, must have overlooked the tail end of the post above...
Sent from my Nexus One using XDA App
how to flash the ROM
omarqa said:
how to flash the ROM
Click to expand...
Click to collapse
There should be an option saying something along the lines of 'Flash zip from SD card'. Simply browse to the zip and flash.
whenever i try to do recovery or anything i keep getting FAILED (remote: signature verify fail) anybody know why i keep getting this???
omarqa said:
whenever i try to do recovery or anything i keep getting FAILED (remote: signature verify fail) anybody know why i keep getting this???
Click to expand...
Click to collapse
Is your device unlocked? It must be unlocked to issue certain fastboot commands.
Which custom recovery do you have installed?
Sent from my Nexus One using XDA App
thanks guys, it got fixed.
so how can i install cyanogenmod, every time i try to install version 6.1.1 i get a android log with exclamation mark over it, any ideas
your help is really appreciated,
edit: i mean by fixed that i restored the original version of the device.
That's the stock recovery (hence my previous question)...
You need to install a custom recovery, and also delete the following two files:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
(as stated by HD earlier)
Sent from my Nexus One using XDA App
Related
I decided to try and root my phone tonight.
I was successful in rooting my Captivate, and got root access.
I was able to fully access the recovery menu by pressing the power, vol up and down keys.
I messed up by installing Nero for the Vibrant on my Captivate, and things started acting weird on my phone. Vol -/+ were going opposite ways, and menus would not load in the right direction.
I decided that I needed to get a rom that worked with a Captivate, so I hooked everything back up and ran Odin again (I believe this was a mistake).
From here, I was going to give myself root access again, and flash with a new rom.
Every since I ran Odin, which installed Eclair 2.1 back on my phone -- I can not get into the recovery menu, therefore I can not get root/install the roms.
Please help
Thanks
Danny
I was able to successfully get in recovery mode with ADB.
I will post more if I run into any other problems.
Thank you !!
_allstar said:
I was able to successfully get in recovery mode with ADB.
I will post more if I run into any other problems.
Thank you !!
Click to expand...
Click to collapse
_allstar, Can you post directions for how to use ADB to get into recovery? I have a similar situation as you, where I cannot get into recover or download after flashing stock with Odin. I can't seem to figure out what to do with ADB. Thanks!
GlassButrFly said:
_allstar, Can you post directions for how to use ADB to get into recovery? I have a similar situation as you, where I cannot get into recover or download after flashing stock with Odin. I can't seem to figure out what to do with ADB. Thanks!
Click to expand...
Click to collapse
Check this out, http://forum.xda-developers.com/showthread.php?t=819105
Some info on how to setup ADB.
I am having this same problem after one click odin and master clear (back at JF6). I tried to do the 3 button fix which is part of the quide bobbylx posted but one step is to flash with ROM manager. I can't do this now that I'm back at stock (no root access!) The step that I'm stuck at within http://forum.xda-developers.com/showthread.php?t=884364 is re-rooting my phone.
How exactly do I get into recovery or flash if I am not rooted?
nechalo said:
I am having this same problem after one click odin and master clear (back at JF6). I tried to do the 3 button fix which is part of the quide bobbylx posted but one step is to flash with ROM manager. I can't do this now that I'm back at stock (no root access!) The step that I'm stuck at within http://forum.xda-developers.com/showthread.php?t=884364 is re-rooting my phone.
How exactly do I get into recovery or flash if I am not rooted?
Click to expand...
Click to collapse
Have you ever been rooted and had Clockwork recovery installed? If so you should already have the update.zip on your phone. Just boot into stock recovery and choose Reinstall Packages, the phone reboots into stock recovery again, then choose Reinstall Packages a second time. This time you will be in Clockwork.
If you don't have the update.zip, I posted it before in another thread here
Also, if you do root or install a custom ROM, which by the rooting is not needed to install custom roms, here's a tip. After you download and install ROM manager and install clockwork, you will always have the update.zip on your internal SD card. But if you somehow delete update.zip, then go to MyFiles file browser, and in the folder Clcokworkmod, there is a file called recovery-update.zip. If you take it and copy it to the root of your SDcard and rename it update.zip that is the clockwork installer.
Just use ADB to reboot into recovery if you haven't rooted.
GlassButrFly said:
_allstar, Can you post directions for how to use ADB to get into recovery? I have a similar situation as you, where I cannot get into recover or download after flashing stock with Odin. I can't seem to figure out what to do with ADB. Thanks!
Click to expand...
Click to collapse
Yes. You need to install the ADB package on your computer. Google "Download the Android SDK" and download the android-sdk_r08-windows.zip (I can't post links yet) , unzip to your root directory (C:\ on windows) and then run the .exe in the zip. It will download updates for the program.
This took me some time, and research to figure out. I was sitting helpless for about 2-3 hours not able to boot into recovery.
Once you get ADB installed, open command prompt and goto your directory that it is in, for example this is what my DOS prompt looks like:
C:\Users\Danny> cd c:\
C:\> cd c:\android-sdk-windows\platform-tools
(make sure your phone is plugged in, turned on, and on Debug mode, then execute this command)
C:\android-sdk-windows\platform-tools> adb.exe reboot recovery
Your phone will reboot into recovery mode via command prompt
Hope this helps. It took me awhile to figure out, but I'm very glad I know now.
_allstar said:
Yes. You need to install the ADB package on your computer. Google "Download the Android SDK" and download the android-sdk_r08-windows.zip (I can't post links yet) , unzip to your root directory (C:\ on windows) and then run the .exe in the zip. It will download updates for the program.
This took me some time, and research to figure out. I was sitting helpless for about 2-3 hours not able to boot into recovery.
Once you get ADB installed, open command prompt and goto your directory that it is in, for example this is what my DOS prompt looks like:
C:\Users\Danny> cd c:\
C:\> cd c:\android-sdk-windows\platform-tools
(make sure your phone is plugged in, turned on, and on Debug mode, then execute this command)
C:\android-sdk-windows\platform-tools> adb.exe reboot recovery
Your phone will reboot into recovery mode via command prompt
Hope this helps. It took me awhile to figure out, but I'm very glad I know now.
Click to expand...
Click to collapse
THANK YOU! For me, I had to use the following commands:
C:\Users\[username]>cd android-sdk-windows
C:\Users\[username]\android-sdk-windows\tools>cd tools
C:\Users\[username]\android-sdk-windows\tools>adb.exe reboot recovery
It rebooted directly into recovery and I was able to flash back to the rom I was using previously, which is where I will stay, probably indefinitely. Seems my phone does not take well to flashing. lol But this is so much better than being stuck with Stock Eclair, so thank you very much!
thank you so much guys, worked like a gem
I rooted and flash my nexus one with a rom that was based on the cm7 nightly. It installed completely and I rebooted. It gets past the static x but loops in the moving x. I've tried so many things over the past 8 hours I need help to get a rom working on this. I tried going through the fastboot. Tried using recovery to update from sdcard and I'm having no luck getting this to work again. Hopefully someone on here knows how to fix my problem so I can get a working rom on my phone. Thanks everyone.
Did u install recovery (amon or clockworkmod?? If you did just dload another rom, wipe and flash again
N1
When I originally did the install I installed clockwork and did a back up. When I go into recovery all I can do is either wipe data, update from sdcard and wipe cache. I'm about ready to pull my hair out. I have no clue what went wrong. I've installed new roms on my old phones and no problems, I follow all the instructions.
nandroid, wipe all, retry flashing.
or restore your nandroid backup.
Looking at "adb logcat" while its booting will pinpoint the error.
I've tried to go through fastboot to use my recovery image but I get failed (remote: signature verify fail). I don't know how to get into nandroid and my computer I can only use the fastboot not adb to use logcat. Is there a way to use the fastboot that doesn't come up with the signature fail. I really don't know what happened. What other ways can I use my recovery image if I can't do it from the physical phone?
Sounds like a bad backup. DId you verify MD5?
If you want to start over..
Download AmonRa Recovery 2.2.1. From thread below...
http://forum.xda-developers.com/showthread.php?t=611829
With phone in fastboot mode and connected to PC via usb:
1. Command Prompt: fastboot devices (make sure device is connected)
2. Make sure recovery image file is in your SDK/tools folder
3. Make sure your working directory is SDK/tools folder
4. Command Prompt: fastboot flash recovery recovery-RA-passion-v2.2.1.img
5. After flash is done, reboot to recovery.
6. Wipe everything.
7. Re-flash your ROM.
You can always go back to Clockworkmod if you want. Just re-flash clockwork recovery.
thanks for the help but I'm still getting the signature verify failed even with the new recovery img.
projektmayhem said:
thanks for the help but I'm still getting the signature verify failed even with the new recovery img.
Click to expand...
Click to collapse
Your getting this error when flashing what?
projektmayhem said:
thanks for the help but I'm still getting the signature verify failed even with the new recovery img.
Click to expand...
Click to collapse
Did you unlock your phone (fastboot oem unlock) or did you just root it?
If you haven't unlocked your phone, perhaps try that then use the previous instructions to flash clockwork or amon recovery image.
link for reference
Dude, thanks sooo much. Unlocking the bootloader did the trick. I almost had to go buy a new phone. If you lived in the San Jose area I would buy you a beer.
Make sure you add to his "Thanks" meter! BTW. That would have been my next suggestion...
projektmayhem said:
Dude, thanks sooo much. Unlocking the bootloader did the trick. I almost had to go buy a new phone. If you lived in the San Jose area I would buy you a beer.
Click to expand...
Click to collapse
Make sure you add to his "Thanks" meter! BTW, that would have been my next suggestion...
Sorry for the Double Post
projektmayhem said:
Dude, thanks sooo much. Unlocking the bootloader did the trick. I almost had to go buy a new phone. If you lived in the San Jose area I would buy you a beer.
Click to expand...
Click to collapse
Glad to help. I think we've all had those "OMFG HOW DO I FIX THIS" moments.
Ok, so bit of background here.
I installed MIUI Rom using GOT OpenRecovery.
Its very cool and I really enjoy using it. Much better (IMO) than CM7.
It got to Saturday and it said there was an OTA update to install which I couldn't work out how to install. On researching it a bit around the internet it turns out that you need to have ClockworkMod Recovery flashed in order to install OTA updates.
So I tried to install ClockworkMod Recovery. I did a few different things. Firstly I downloaded the ClockworkMod Rom Manager and chose the option in there to flash. It said "Downloaded successfully" but it didn't flash. I rebooted into recovery and tried to "Apply update.zip" but it said something about it not being signed properly and wouldn't open.
So onto the next bit. I tried to flash it using one of the many manual instructions on the internet. eg:
Code:
adb shell
# flash_image recovery /sdcard/recovery.img
and
Code:
fastboot-mac flash recovery /path/to/recovery.img
The first one seems to be quite quick and just goes to the next # line. There's no error or confirmation or anything. This one broke the stock recovery. Now when I boot into recovery there's just a bootloader screen with an error on it (Err:A5,69,35,00,2F).
The second one doesn't do anything. Well it goes onto a new line and it says "sending 'recovery' (2798 KB)..." and just stays like that indefinitely until I do Ctrl+C and cancel it. Similarly doing:
Code:
fastboot-mac erase recovery
shows: "erasing 'recovery'..." and stays at that indefinitely.
So now I'm stuck. My system works - I can boot into MIUI and use the phone normally, but I don't know how to get the recovery partition working properly.
The best thing that could happen is that I get ClockworkMod Recovery installed so that I can flash MIUI updates, but failing that I would at least like to get the stock recovery back so I can continue to use GOT OpenRecovery.
What can I do to sort this?
Thanks for any help you can give me.
tclayson said:
Ok, so bit of background here.
I installed MIUI Rom using GOT OpenRecovery.
Its very cool and I really enjoy using it. Much better (IMO) than CM7.
It got to Saturday and it said there was an OTA update to install which I couldn't work out how to install. On researching it a bit around the internet it turns out that you need to have ClockworkMod Recovery flashed in order to install OTA updates.
So I tried to install ClockworkMod Recovery. I did a few different things. Firstly I downloaded the ClockworkMod Rom Manager and chose the option in there to flash. It said "Downloaded successfully" but it didn't flash. I rebooted into recovery and tried to "Apply update.zip" but it said something about it not being signed properly and wouldn't open.
So onto the next bit. I tried to flash it using one of the many manual instructions on the internet. eg:
Code:
adb shell
# flash_image recovery /sdcard/recovery.img
and
Code:
fastboot-mac flash recovery /path/to/recovery.img
The first one seems to be quite quick and just goes to the next # line. There's no error or confirmation or anything. This one broke the stock recovery. Now when I boot into recovery there's just a bootloader screen with an error on it (Err:A5,69,35,00,2F).
The second one doesn't do anything. Well it goes onto a new line and it says "sending 'recovery' (2798 KB)..." and just stays like that indefinitely until I do Ctrl+C and cancel it. Similarly doing:
Code:
fastboot-mac erase recovery
shows: "erasing 'recovery'..." and stays at that indefinitely.
So now I'm stuck. My system works - I can boot into MIUI and use the phone normally, but I don't know how to get the recovery partition working properly.
The best thing that could happen is that I get ClockworkMod Recovery installed so that I can flash MIUI updates, but failing that I would at least like to get the stock recovery back so I can continue to use GOT OpenRecovery.
What can I do to sort this?
Thanks for any help you can give me.
Click to expand...
Click to collapse
GOT recovery? You have a Milestone then? You are on the wrong path then. Clockwork Recovery Mod doesn't work on the Milestone, nor does ROM Manager.
You need to reflash the stock sbf for your country, then flash the rootable sbf, place OpenRecovery on your SD Card, and root the phone, flash a custom ROM and reboot. Look at the tutorials in the Milestone development forum and ask here if you have any other questions.
I do have a milestone - sorry, I forgot it was the Droid AND Milestone forum.
Motorola milestone is included in the list of recovery images on the clockworkmod website (clockworkmod[dot]com/recovery_images.html). Plus when installing the ROM Manager and clicking "flash recovery" it says "Confirm phone" with "Motorola Milestone" in the options.
I'm pretty sure as well from reading around on the internet and looking at different forums and such that Clockworkmod does work on the Milestone... maybe I'm completely wrong.
Thanks
tclayson said:
I do have a milestone - sorry, I forgot it was the Droid AND Milestone forum.
Motorola milestone is included in the list of recovery images on the clockworkmod website (clockworkmod[dot]com/recovery_images.html). Plus when installing the ROM Manager and clicking "flash recovery" it says "Confirm phone" with "Motorola Milestone" in the options.
I'm pretty sure as well from reading around on the internet and looking at different forums and such that Clockworkmod does work on the Milestone... maybe I'm completely wrong.
Thanks
Click to expand...
Click to collapse
It doesn't work, even though it shows it as supported. Because the bootloader is not unlocked on the Milestone, it will cause a soft brick. You will need to follow my instructions to get your Milestone running on MIUI again. The OTA update for MIUI works for devices with CWM installed, so it doesn't really work with Milestone. You'll need to manually update MIUI when DannyDroid posts the updates.
Ah gutted, ok thank you for that. I will follow your instructions. Thanks for clearing it up for me.
Just out of interest - a quick search on google shows that it IS possible to update MIUI OTA for the Milestone... Any ideas how that works? Is there a different recovery or something?
tclayson said:
Just out of interest - a quick search on google shows that it IS possible to update MIUI OTA for the Milestone... Any ideas how that works? Is there a different recovery or something?
Click to expand...
Click to collapse
People say that ROM Manager MIGHT work on Milestone. I don't think so and I wouldn't risk it just for OTA updates, seeing as the miuiAndroid build is very basic compared to the one Danny releases. Better to just wait for his releases, a lot more worthwhile!
Ok, well thank you very much! Restored to stock and gonna keep on top of danny's releases. Thanks skadude.
Rom Manager was just updated to version 5.0.2.4 and allows you to flash to CWM 6.0.1.6 recovery. Booting to recovery just gives me the Android with a red flag though. Just a FYI till it gets sorted.
Pressing and holding the pwr button will boot you back to the OS. Not a huge deal as we don't have anything to flash at the moment.
If you need to get back to the stock recovery in the meantime which can be found in this thread
http://forum.xda-developers.com/showthread.php?t=1993331
Edit:
Don't Flash this yet, you'll have to re-install the stock recovery or wait for a fix and could possibly brick your phone if you don't know what you're doing.
Is there like an easy way to root other than manually adb pushing? Flashable zip maybe?
I get the same thing as you, says flash successful then the red flag.
F4M0U569 said:
Is there like an easy way to root other than manually adb pushing? Flashable zip maybe?
Click to expand...
Click to collapse
You can use the temporary "boot" method as opposed to "flash" when using the current CWM recovery which is posted here http://forum.xda-developers.com/showthread.php?t=1993331
Don't flash the recovery yet though, it's obviously not sorted. I used the adb method to root which worked fine. I got excited when I saw the new Rom Manager which allowed me to flash recovery because Koush's G+ messages earlier today.
kchino said:
You can use the temporary "boot" method as opposed to "flash" when using the current CWM recovery which is posted here http://forum.xda-developers.com/showthread.php?t=1993331
Don't flash the recovery yet though, it's obviously not sorted. I used the adb method to root which worked fine. I got excited when I saw the new Rom Manager which allowed me to flash recovery because Koush's G+ messages earlier today.
Click to expand...
Click to collapse
I tried using the adb boot method but it doesn't work for me. After booting the insecure boot and taking me to the Android screen, I tried using the codes listed there but it says no device found.
F4M0U569 said:
I tried using the adb boot method but it doesn't work for me. After booting the insecure boot and taking me to the Android screen, I tried using the codes listed there but it says no device found.
Click to expand...
Click to collapse
i did it last night and it was quite late, but if i remember correctly i had the same problem but just had to reselect USB debugging
Sent from my Nexus 7 using xda app-developers app
Hi All,
First off please forgive how much of a low level noob I am am at this. I didn't create a backup unfortunately. Now we can get to the good stuff. I have unlocked, s-off, and rooted my phone. Loaded a great GPE rom on there and it was working perfectly fine. While looking for a SU for the Rom so that I could delete some wifi bs I found a the HD rom on this site that I would rather use. Soooo I rooted the rom and used cwm to load up the HD 6.1 rom. After the install, when rebooting, it asked me if I wanted to fix the SU permissions and i clicked yes. Now it is stuck in a boot cycle. When I enter fastboot I can enter commands (no adb detection) I can even flash a different recovery on there and the corresponding logo will flash for a second at the end of each boot cycle. Trying to launch reboot or factory reset will put me into another boot cycle. I have tried using fastboot to load directly into recovery but that freezes the phone 2/3 times. Any help would be greatly appreciated so that I can just go back to the GPE rom i was using and stop screwing around with my phone.
XaBuddy said:
Hi All,
First off please forgive how much of a low level noob I am am at this. I didn't create a backup unfortunately. Now we can get to the good stuff. I have unlocked, s-off, and rooted my phone. Loaded a great GPE rom on there and it was working perfectly fine. While looking for a SU for the Rom so that I could delete some wifi bs I found a the HD rom on this site that I would rather use. Soooo I rooted the rom and used cwm to load up the HD 6.1 rom. After the install, when rebooting, it asked me if I wanted to fix the SU permissions and i clicked yes. Now it is stuck in a boot cycle. When I enter fastboot I can enter commands (no adb detection) I can even flash a different recovery on there and the corresponding logo will flash for a second at the end of each boot cycle. Trying to launch reboot or factory reset will put me into another boot cycle. I have tried using fastboot to load directly into recovery but that freezes the phone 2/3 times. Any help would be greatly appreciated so that I can just go back to the GPE rom i was using and stop screwing around with my phone.
Click to expand...
Click to collapse
fastboot erase cache
then flash the recovery again (twrp 2.6.3.3 suggested)
then from recovery wipe and adb push or sideload the rom
I was able to get twrp to work by flashing it again, probably the 7th time, and erased the cache. Now I don't think i want to load the same rom that started this but to go back to the GPE version that I had. Is there a way to get this on the internal sd card through fastboot?
XaBuddy said:
I was able to get twrp to work by flashing it again, probably the 7th time, and erased the cache. Now I don't think i want to load the same rom that started this but to go back to the GPE version that I had. Is there a way to get this on the internal sd card through fastboot?
Click to expand...
Click to collapse
Your options are:
1) adb push
2) sideload from TWRP
3) OTG cable from TWRP
Lots of threads for each of these available in Google
mb_guy said:
Your options are:
1) adb push
2) sideload from TWRP
3) OTG cable from TWRP
Lots of threads for each of these available in Google
Click to expand...
Click to collapse
I was ablt to get adb to recognize the phone however it lists it as a host. I go into the twrp and do the sideload but it opens up the debug message. adb sideload os.zip is the command I'm using as I renamed the file to os.zip so i don't have to type so much. I tried the adb push but it says error:Closed.
mb_guy said:
Your options are:
1) adb push
2) sideload from TWRP
3) OTG cable from TWRP
Lots of threads for each of these available in Google
Click to expand...
Click to collapse
so adb push finally did something but not quite what I wanted this is the message I got
failed to copy '/Users/robertlitz/Downloads/Archive/os.zip' to '/data/media/0/': Is a directory
XaBuddy said:
so adb push finally did something but not quite what I wanted this is the message I got
failed to copy '/Users/robertlitz/Downloads/Archive/os.zip' to '/data/media/0/': Is a directory
Click to expand...
Click to collapse
Try this instead
adb push os.zip /sdcard/os.zip
mb_guy said:
Try this instead
adb push os.zip /sdcard/os.zip
Click to expand...
Click to collapse
It worked!! Thank you so much. I had tried adb push os.zip /sdcard/ a while ago but it didn't take. by typing the zip name after sdcard i assume that "gives" the file an exact location to be placed?