help - Overclock Patch and update.zip - Droid Eris Android Development

i have my phone updated to 2.1 and rooted. Want to overclock it now but not sure what im supposed to do with the kernel-overclock-update-v3.zip. I have the original PB00IMG.zip i updated and rooted my phone with, am i supposed to use it somehow?? New to this would appreciate any help.

Just use this, Flash it and it will make ur life easyier.
http://forum.xda-developers.com/showthread.php?t=685581

so phone will be stock again right? have to re dload apps and sync contacts and **** again right?

hmm... or u can try to flash the kernel-overclock-update-v3.zip to the one you have
be sure to nand backup first

when i put the kernel-overclock-update-v3.zip on the root of the sd card and power up holding the volume down button it doesn't find the kernel-overclock-update-v3.zip and doesn't install it...? in other word how do i flash it, doesn't seem to be working like when i originally flashed and rooted.

did you flash recovery?
duckingzebra said:
when i put the kernel-overclock-update-v3.zip on the root of the sd card and power up holding the volume down button it doesn't find the kernel-overclock-update-v3.zip and doesn't install it...? in other word how do i flash it, doesn't seem to be working like when i originally flashed and rooted.
Click to expand...
Click to collapse
Hey man,
When you rooted did you flash the Amon-Ra recovery image? If so put the update zip on the root of your sd. Power down your handset. hold the volume UP and the power on will bring you to the recovery menu. Here you have options for back up,flash from zip etc...once there you can select whatever rom/update you want to flash. Remember nandroid is your friend always back up. Also as far as apps etc...check out Titanium back up or one of the other free back up apps in market. I hope this helps you out.

volume up + end button = Recovery

ok, im following the steps to III: Flashing a Custom Recovery. and when i get to the step :adb push recovery.img /sdcard it says :cannot start recovery.img: No such file or directory...is the recovery.img also supposed to gon on the root of my sd card? or just the tools folder, cause its there?

yes its suppose to be on the root of the sdcard too

still says cannot stat 'recovery.img': no such fire or directory
am i supposed to replace /sdcard with /J (which is what my phone comes up as in my computer) -tried that still didn't work...

can u link me to the tut u are using?

http://forum.xda-developers.com/showthread.php?t=647707

QUOTE=TopazAaron]
duckingzebra said:
did you see the tutorial i linked? still cant figure it out.
Click to expand...
Click to collapse
ok
put the Recovery image in the tools/ in the sdk
after that plug ur phone into the comp
now being there in cmd navigate to the /tools/ folder
then type or copy and paste
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
---
now if you still have issues, let me know, sorry i didnt reply, i got busy with other things.
thanks for ur pm tho[/QUOTE]
ok now instead of saying :cannot start recovery.img: No such file or directory
it says error: device not found, when i open my computer my sdcard in my phone shows up and i can open it...

That is really wierd, try joining the irc u may get more help there
-------------------------------------
Sent via the XDA Tapatalk App

TopazAaron said:
That is really wierd, try joining the irc u may get more help there
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Sorry newser here, irc??

Is your phone actually rooted? To check, turn on your phone, then turn on USB debugging through Settings/Applications/Development/USB debugging. Plug your phone into the computer via the USB cable.
In the run box of your computer, type cmd, then enter.
When the command window shows up, changed you your SDK tools directory. On my system it would be:
cd c:\android-sdk-windows\tools
Then run the following command
adb shell
You're rooted if it comes back with
#
If it comes back with
$
try the typing
SU
if it does not change from $ to # then you might want to try rooting again, and be sure to install the Amon_RA recovery
typing exit multiple times will back you out of adb, and the cmd window.
Hope that helps.
Edit: Of course that works for 2.1 leak 3 users as well.
Easier way for you tho, if you boot to hboot with the send and end buttons, you should see hboot with S off if you're rooted. If it's S On you're not.

Related

Looping into recovery

My phone keeps booting into recovery mode.
Power on -> Blank -> Reboot -> Recovery
I had the new SPL (the saphire ported one), JF's recovery (i still have it on) and JF1.51.
This happened since i tried to flash the HTC ADP update.zip.
I have tried using the hardSPL, reflashing the saphire SPL, tried flashing back to JF1.5, Rodgers but nothing seems to work
Any ideas?
EDIT: I just checked and it didnt flash the saphireSPL! i dont think adb shell push is copying the update.zip's to the SD card.
EDIT:
SOLUTION:
I was right in that it wasn't copying the updates to the sd card, i borrowed a friends G1, used it to put on the saphireSPL, flashed (and it worked this time), got into fastboot (the hardSPL fastboot didnt seem to work), and restored my nandroid backups! yey! now to try JAC's build
if you want to adb push in recovery, you'll need to mount the sdcard first or it will appear to have transfered, but actually done nothing.
next time, try
Code:
adb shell mount /sdcard
adb push update.zip /sdcard/update.zip
ravenge said:
if you want to adb push in recovery, you'll need to mount the sdcard first or it will appear to have transfered, but actually done nothing.
next time, try
Code:
adb shell mount /sdcard
adb push update.zip /sdcard/update.zip
Click to expand...
Click to collapse
Thank you, that'll come in really handy for when i dont have a spare Dream or card reader about!
ravenge said:
if you want to adb push in recovery, you'll need to mount the sdcard first or it will appear to have transfered, but actually done nothing.
next time, try
Code:
adb shell mount /sdcard
adb push update.zip /sdcard/update.zip
Click to expand...
Click to collapse
Oh my god... this (hopefully) has fixed the problem I've had for the past two days - I've spent so long reading every thread on here about the SPL problems, etc. I had a feeling the problem was the update wasn't working correctly, but I had no idea why. (It didn't complain, but just went very quickly - much to quick to be doing a full os upgrade).
Thanks!!!
umm how would i even run that script?cuz i keep bootlooping
Jerzdre said:
umm how would i even run that script?cuz i keep bootlooping
Click to expand...
Click to collapse
On Phone:
Recovery -> ALT+X -> Console
On PC
Command prompt
"cd <directory where you have update.zip>"
"adb shell mount /sdcard"
"adb push update.zip /sdcard/update.zip"
On Phone
Hold 'Home' and then:
On PC:
"adb shell reboot"
ravenge said:
if you want to adb push in recovery, you'll need to mount the sdcard first or it will appear to have transfered, but actually done nothing.
next time, try
Code:
adb shell mount /sdcard
adb push update.zip /sdcard/update.zip
Click to expand...
Click to collapse
but you can abd push to the ext2 portion of the sd card without mounting while in recovery, correct?

Default android lockscreen

Is it possible to change the lockscreen to the default android, i'm new to android nd still tryna get a hold of things. Thanks
-------------------------------------
Sent via the XDA Tapatalk App
lakeside00 said:
Is it possible to change the lockscreen to the default android, i'm new to android nd still tryna get a hold of things. Thanks
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
you can remove the HtcLockScreen.apk from /system/app/ and it will default to the stock android one. Problem is that is suffers from the same fate as many others where the slder is up/down and the time is jummbeled on the left side.
Oh and of course to remove/rename the file in /system/app/ you must be rooted and in recovery mode.
I'm working on how to fix the screen. Flipz did it for android 2.0 but it isn't the same fix in 2.1. If I get more info I'll post back.
I tried to remove HtcLockScreen.apk via adb but I don't think we have system write access yet. even through adb. someone correct me if I'm wrong but I believe this is true.
Edit: As said above... you have to be in recovery. I stand corrected. don't listen to me!
edit #2: tried it in recovery... couldn't even remount. I don't think I did anything wrong...
gmelchert said:
I tried to remove HtcLockScreen.apk via adb but I don't think we have system write access yet. even through adb. someone correct me if I'm wrong but I believe this is true.
Edit: As said above... you have to be in recovery. I stand corrected. don't listen to me!
edit #2: tried it in recovery... couldn't even remount. I don't think I did anything wrong...
Click to expand...
Click to collapse
LOL! love the step by step edits...
I have a script that makes it easy, it is just a modified version of Toast's. It cuts it down to one command input instead of three.
Any way here are the steps:
With phone on plug it into your computer. Open two command windows. Navigate one to the folder you have downloaded toasts recovery script to.
1) In the window that is at evo-recovery> type: adb reboot recovery
This boots you in to the stock recovery
2)in the same window type windows-recovery.bat (adjust for your OS)
This gets you into Amon-RA's recovery
3) Wait for the phone to get the new recovery screen. In the other command window type: adb shell mount -a
Step 3 can be adb remount or you can type adb shell then at the # type #mount -t yaffs2 -o remount,rw /dev/block/mtdblock4 /system
Any way after that point you can exit adb shell back to the command prompt and push/pull anything to /system
unfortunately you can't see it right away and have to wait for reboot. Also this limits some of the apps that we can install because some will need to write to /system and cannot once rebooted.

Updated root 1.49

READ IT BEFORE DOING IT
How to get into recovery
This is the way i figured how to get it into adb. I spent all day figuring this out.
It will take a couple tries but it will work
-Go to sdk folder then usb driver folder
-Make sure you have added to the inf file ; HTC Eris
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
-Have a formated sd with allocation size of 4096.Don't format with phone do it with card reader or if you can't do it with usb...
-Boot your phone into HBoot with sdcard in.
-When the screen turns on wait a sec pop out sdcard make sure it doesn't scan sdcard.
-Start loop.bat or .sh
-Push volume up for recovery before wait 4 secs before your computer makes the sound pop it in.
-^^^Make sure you got around 3-5 secs before pushing it in
What to do when in adb recovery
-Do down volume and power and hit update it will fail.
-Adb push ota.zip /sdcard/update.zip
-Adb push root.zip /sdcard
-Have this command ready don't do it yet.
-Adb push update.zip /sdcard
-Press Hit run update.zip, as soon as you see a the green lil bar on your phone. PRESS ENTER ON CMD.
-Go to the partitions menu and mount system
-Go back and press update select install any zip from sdcard.
-Choose root.zip
-Reboot phone and install superuser.apk and allow it.
-Do adb shell then su if you see # you have root
-Download rom manager from market.
-Flash recovery ra or clockworkmod.
-^^^ if it doesn't let you, you messed up on rooting it.
Ill post a video of me doing it later. To lazy now
ADB RECOVERY VIDEO
http://www.youtube.com/watch?v=Uhc3SvOS6r4
PS ill figure it out later how i did with more practice
and don't flame or say video fake.. Or i just won't figure it out.
http://www.youtube.com/watch?v=eK_A0lH8uFM/color]
Hairston said:
I forgot that my digital camera can take video, duh. I can make one too if you want.
What would you need? Would a shot of the HBOOT screen showing 1.49 S-ON and then hitting <VOL UP> booting into Amon_RA recovery (to prove root) do it?
It really sucks that this procedure is such a living hell. Blame HTC for locking these things down so tightly in the first place. This is my first rooted phone and being able to play around with the custom roms and to do an image backup is pretty cool.
I see a lot of people in the Incredible root thread using the same basic method to root are having a tough time too. Misery loves company I guess.
Click to expand...
Click to collapse
^^^^^ proof right there
Another method
RKLamb2 said:
Alright sorry about that but it was like 4 in the mourning. I will use the other guys post for the slide and explain what I did.
The main thing I did different was as soon as pushed down to go to hboot I ejected my memory card at the exact same time. No scan or anything. Once I got to the part where I ran the loop I hit control C to stop it and and it was smooth sailing from there.
Memory card was a sandisk 8 gig that I formatted to 4096 in windows seven. I basically use both write up but I actually finished using the slide write
Place the Contents of "Slide Root.zip" into your Android SDK Tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK/Tools Directory.
Step 3.
Power on the Slide into the bootloader by Holding Down ( Volume Down + Power Button )
Step 4.
Now run your loop file from the prompt (either type "loop" in windows or "./loop.sh" in a *nix like)
Step 5.
Once your loop is running in your prompt, select Recovery from the bootloader menu.
Step 6.
When recovery loads, you should Have an Offline Device. You can use ctrl+c to stop your script & see.
If this doesn't happen, Power Off and try again..
Step 7.
Un-plug your USB cable from the back of your phone & Plug it back in for it to Detect ADB Correctly!!! This is an important step. At this point you can adb devices to see if you can see your device and that it is in recovery mode.
Step 8.
Hit Volume Up + Power button to Bring up the Selectable Menu
Select Update.zip from the menu. (This will fail, but we already know that! Select it anyway).
Step 9.
adb push ota.zip /sdcard/update.zip (*nixlike users add a ./ in front of all terminal commands please.)
Step 11.
adb push slideroot.zip /sdcard
Step 12.
This is Very important!! Have this Command ready in your prompt before applying update.zip again!!
adb push update.zip /sdcard
step 13.
Hit run update.zip, as soon as you see a Little Bar appear under the text push Enter to execute the command in your prompt (adb push update.zip /sdcard )
Step 14.
In successful, you should see Clockwork Recovery. If unsuccessful, repeat steps 12 & 13.
Step 15.
Now, go to the Partitions menu and Mount System
step 16.
Go back one level & select install any zip from sdcard. Select slideroot.zip & apply update from zip (This will finish the Root process).
Step 17.
Reboot your phone & wait for it to load completely. To confirm that your slide is connected as a device use the command adb devices. If this works, you will see it as a device. Your prompt will say something like:
$ ./adb devices
List of devices attached
HT05YUP12710 device
Step 18.
adb install Superuser.apk (If this looks like it works, but says it cannot locate directories, make sure you can find your device using adb devices… If things still don't work, my best advice is to start over)
Step 19.
After Superuser is installed try to use adb to shell to your device.
adb shell
you will get a $
Then type su
Superuser should pop-up asking if you give permission, do so.
Your $ should turn into a #. If so, you have root.
Click to expand...
Click to collapse
Dc_striker said:
i got it working now what files to i push to it sorry for noob post lol
Click to expand...
Click to collapse
Give exact details on what you did.
AcidRoot said:
Give exact details on what you did.
Click to expand...
Click to collapse
http://forum.androidspin.com/showthread.php?t=2757
Push the root rom AFTER you tell us how.
Dc_striker said:
http://forum.androidspin.com/showthread.php?t=2757
Click to expand...
Click to collapse
So you you just followed that and it worked?
AcidRoot said:
So you you just followed that and it worked?
Click to expand...
Click to collapse
yes lol couple of tries but it worked
Dc_striker said:
yes lol couple of tries but it worked
Click to expand...
Click to collapse
sd card in or out
and what sd card are you using?
AcidRoot said:
sd card in or out
Click to expand...
Click to collapse
push sd card in before recovery pops i think lol. btw a transcend sd card 8gb
Damn I have tried a million times a million ways and nothing. Any small little detail that you think we might be missing?
Dc_striker said:
push sd card in before recovery pops i think lol. btw a transcend sd card 8gb
Click to expand...
Click to collapse
well i tried and the script froze for a second then nothing and i haven't been able to do it again
ah hell
listyb01 said:
ah hell
Click to expand...
Click to collapse
like ever post say its all about time or luck so it will work on the eris
Yea I'm sure it will work eventually. Can you give me a few details?
Debug on or off?
pc connection settings (on eris)?
Anything else important that I may be over looking?
Congrats on the root! Froyo was just posted so looks like your first custom ROM can be a 2.2 build.
listyb01 said:
Yea I'm sure it will work eventually. Can you give me a few details?
Debug on or off?
pc connection settings (on eris)?
Anything else important that I may be over looking?
Congrats on the root! Froyo was just posted so looks like your first custom ROM can be a 2.2 build.
Click to expand...
Click to collapse
just look at the link i posted i just followed everything on there, but its either i popped in before recovery popped up or pop out and in in recovery
Guess my luck is not as good cause it isn't working.
listyb01 said:
Guess my luck is not as good cause it isn't working.
Click to expand...
Click to collapse
Damn keep trying but i posted this thread to everyone know this method should work
Does anybody know where loop.sh is i want to try this on my linux machine but can't find it and have no idea how to do it in bash
AcidRoot said:
Does anybody know where loop.sh is i want to try this on my linux machine but can't find it and have no idea how to do it in bash
Click to expand...
Click to collapse
just use this: "while true; do adb devices; done"
Still trying to get this working on OSX.
AcidRoot said:
Does anybody know where loop.sh is i want to try this on my linux machine but can't find it and have no idea how to do it in bash
Click to expand...
Click to collapse
for linux try while true; do adb devices; done

NS 4G - Need radio image dump

Looking for anyone with a new NS4G to dump a copy of the radio. I messed up and flashed a rom that had a gsm radio attached. rendering my phone useless as far as phones go.
root
post a good root method and how to do the dump. I can have it hotlinked in 1 hour
i used http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
worked just fine.
Once you're rooted, do
Code:
adb shell dd if=/dev/mtd/mtd5 of=/sdcard/ns-cdma-radio.img count=12583040
Then upload that ns-cdma-radio.img somewhere ;D
?
ok thanks, i will link it when finished
the dumped file will be in my phone memory, correct?
ryandoubleu said:
ok thanks, i will link it when finished
the dumped file will be in my phone memory, correct?
Click to expand...
Click to collapse
It will be on your internal storage that you can mount as a drive on your pc, yes.
may take...
may take longer than an hour as I am doing the SDK install
ryandoubleu said:
may take longer than an hour as I am doing the SDK install
Click to expand...
Click to collapse
You don't need the platform api, just the SDK tools/platform-tools , that'll save you a lot of download time.
yes i should have mentioned that. i didn't install the SDK either just the tools.
just like http://forum.xda-developers.com/showthread.php?t=878786
hmm
fastboot command wont work? troubleshooting as we speak
ryandoubleu said:
fastboot command wont work?
Click to expand...
Click to collapse
instal drivers?
look to the 2nd rooting method i posted. the 2nd file you download are the drivers. you would install it when your phone is in fastboot mode then go to device manager and upgrade the driver
unzip the rar file and make sure to select x86 or x64 driver for your pc.
you should be able to type "fastboot devices" hit enter and it will return your phone if you have the drivers installed
Also the simplest method to get the drivers might be to put phone into fastboot mode, plug USB to computer, then install PDA Net (which automatically installs the phone drivers). I personally could not get the drivers to install manually on Windows 7, had to use the PDA Net method.
CMD is giving my a Permission Denied with this command
adb shell dd if=/dev/mtd/mtd5 of=/sdcard/ns-cdma-radio.img count=12583040
ryandoubleu said:
CMD is giving my a Permission Denied with this command
adb shell dd if=/dev/mtd/mtd5 of=/sdcard/ns-cdma-radio.img count=12583040
Click to expand...
Click to collapse
Try this: (I am assuming you've already finished rooting and installed superuser)
run adb shell
that should give you a "$" prompt in your command window (you've just shelled into your phone)
then type "su" (without the quotes)
On your phone, a superuser request should pop up on the screen, hit Allow
Your command prompt should change to a #
then type
dd if=/dev/mtd/mtd5 of=/sdcard/ns-cdma-radio.img count=12583040
*EDIT: made a typo in the original writeup of this post and left out the count parameter*
(no adb shell required before the dd command this time since you're already shelled into the phone)
here it is
http://www.megaupload.com/?d=H3Z7RQLZ radio image for you
Also, from the first root method I cant find this file and move forward
4. Tap on the gray box that says Mount R/W
5. Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
6. Once renamed, download and install the app called ROM Manager from Android Market
7. Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.
ryandoubleu said:
http://www.megaupload.com/?d=H3Z7RQLZ radio image for you
Also, from the first root method I cant find this file and move forward
4. Tap on the gray box that says Mount R/W
5. Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
6. Once renamed, download and install the app called ROM Manager from Android Market
7. Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.
Click to expand...
Click to collapse
i didn't do that i just ran ROM manager and flashed the latest Clockwork. you're backing up the old recovery. in that step, good idea, sure. needed, not really.
joebags said:
i didn't do that i just ran ROM manager and flashed the latest Clockwork. you're backing up the old recovery. in that step, good idea, sure. needed, not really.
Click to expand...
Click to collapse
Actually the point of renaming that script is to prevent clockwork from being overwritten by the stock recovery.
The default stock rom is set up to re-flash the stock recovery from cache on bootup if it detects that it's been changed (which is very annoying if you *want* clockwork recovery).
thank you very much for uploading that for me
now correct me if i'm wrong netarchy but i would use fastboot to flash the img file?
I just want to double check before i mess up once again. i'm pretty smart and a quick learner but not a pro like yourself
worked?
joebags said:
i didn't do that i just ran ROM manager and flashed the latest Clockwork. you're backing up the old recovery. in that step, good idea, sure. needed, not really.
Click to expand...
Click to collapse
the radio.img got you working?

Messed up my Nexus 4 :(

Guys i have a problem...
I wantes to delete all data on my N4 and start again with a fresh device, My phone is rooted and i had an custom rom installed, i deleted all data pictures and everything else, after that i also formated the sd card, cache etc etc and thats where it went wrong Now i can go into cwm but nothing more... when i reboot i see the black screen with google on it and after that nothing happens...
How can i solve this problem? I hope that i didnt bricked my phone
should still be able to mount usb storage in cmw, that or push files using adb, if you can get into recovery then you can always get your device back
I just helped a user with the same problem yesterday.
Here's the link with steps how to push a rom to your phone with adb: http://forum.xda-developers.com/showthread.php?t=2137976
can you get into fastboot? if you can then all you have to do is follow this thread:
http://forum.xda-developers.com/showthread.php?t=2010312
coffmad said:
should still be able to mount usb storage in cmw, that or push files using adb, if you can get into recovery then you can always get your device back
Click to expand...
Click to collapse
No, you can't mount USB in recovery. The Nexus 4 does not use UMS.
Ok thanks for the fast reply, im gonna try to push a rom with adb.
''I know you don't have a rom on your phone. This is how you can push one to your phone.
You must be booted in recovery
Put the rom in the same directory on your PC where you have adb.exe
Open up the command prompt from that directory. (hold shift and right click--then choose open command window here)
Then type the command-- adb push nameofrom.zip /sdcard/
The file with push to your phone and then your can select it and flash it from recovery''.
I see this in another thread, Where can i find adb.exe? Im terrible with computers...
Adb is part of of the platform tools for android. Since you unlocked and flashed a custom rom you should have it on your computer.
If you need it, it is located as an attachment at the bottom of this post: http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
I got the attachment, its called platform tools v16, i dragged and dropped an rom in that platform tools file and after that i dont know what to do...
''Open up the command prompt from that directory. (hold shift and right click--then choose open command window here)
Then type the command-- adb push nameofrom.zip /sdcard/''
This is what i dont understand.
Mr Djoegoe said:
I got the attachment, its called platform tools v16, i dragged and dropped an rom in that platform tools file and after that i dont know what to do...
''Open up the command prompt from that directory. (hold shift and right click--then choose open command window here)
Then type the command-- adb push nameofrom.zip /sdcard/''
This is what i dont understand.
Click to expand...
Click to collapse
Extract the files in that .zip into a folder and name it something like "Android."
Move the Rom.zip into that folder as well.
Then do the shift and right click and open the command window pointed to that directory. (as I explained above)
Make sure its connected properly and there isn't a driver issue by typing the command: adb devices. If it returns your serial number you are good to go. (If not, you need to install the correct drivers, which are linked in Section A of the post I linked earlier.)
Then type the command. adb push nameofRom.zip /sdcard/
When i type adb devices i can see my serial number and recovery after it.. when i type ''adb push nameofRom.zip /sdcard/ '' i get a message cannot stat 'nameofRom.zip' No such file or directory
What am i doing wrong?
Edit: hahahaha i see what i do wrong nameofRom.zip
Are you actually typing "nameofrom.zip" ?
Sent from my Nexus 4 using xda app-developers app
Mr Djoegoe said:
When i type adb devices i can see my serial number and recovery after it.. when i type ''adb push nameofRom.zip /sdcard/ '' i get a message cannot stat 'nameofRom.zip' No such file or directory
What am i doing wrong?
Click to expand...
Click to collapse
You replace "nameofRom" with the name of your ROM your trying to push
moses992 said:
Are you actually typing "nameofrom.zip" ?
Click to expand...
Click to collapse
hahaha Yes!
@El Daddy: Thanks for your help Im gonna donate a bottle of wine :good:
Mr Djoegoe said:
hahaha Yes!
@El Daddy: Thanks for your help Im gonna donate a bottle of wine :good:
Click to expand...
Click to collapse
Thanks for that. Unneeded, but very appreciated!
Sent from my Nexus 7 using Tapatalk HD
You certainly haven't bricked it. The fact you can get to recovery means, you can get to fastboot. Simply open fastboot and reflash stock and be more careful next time

Categories

Resources