Enter recovery and sideload CN ROM
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip
To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So you need to give command to recovery to instal zip from location you want.
1. root with rootzenfone.apk
http://23pin.logdown.com/posts/230216-root-rootzenfone-14r
2. turn on usb debuging
3. download ww rom and rename it update.zip
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip
4. download es or some other file menager that has root access.
5. go to / (root) and manualy copy update.zip to /data folder
6. Download https://drive.google.com/file/d/0B6...drivesdk&resourcekey=0-W0btfSuQS9kq5iNNsCuWgQ and copy command file to cache/recovery folder
6. open ADB and type line by line:
adb remount
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
after this reboot to recovery and automaticly instal ww rom
This is fantastic, and smart move making a new thread...
Thanks,
sutekh137
And if you're not bricked, but can't update from the old software version. Copy and paste the commands in terminal emulator to force the update. Worked out great. Thanks for the tip.
slayeralive said:
Enter recovery and sideload CN ROM
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip
To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So you need to give command to recovery to instal zip from location you want.
1. root with rootzenfone.apk
http://23pin.logdown.com/posts/230216-root-rootzenfone-14r
2. turn on usb debuging
3. download ww rom and rename it update.zip
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip
4. download es or some other file menager that has root access.
5. go to / (root) and manualy copy update.zip to /data folder
6. open ADB and type line by line:
adb remount
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
after this your device will reboot to recovery and automaticly instal ww rom
Click to expand...
Click to collapse
I'm having a lil problem here. Could you elaborate a little more, like in /root. <-- What does this mean? Do i write root or am I to go to root of the tablet's memory? And should I use adb on my PC connecting by usb cable to the tablet? I'm having a little problem understanding some of the steps.
(Remember, it's my sex life that it's in danger here)!
bravesoul said:
I'm having a lil problem here. Could you elaborate a little more, like in /root. <-- What does this mean? Do i write root or am I to go to root of the tablet's memory? And should I use adb on my PC connecting by usb cable to the tablet? I'm having a little problem understanding some of the steps.
(Remember, it's my sex life that it's in danger here)!
Click to expand...
Click to collapse
I would assume root of the device itself as the next step is to put update.zip in /data
(Get me in on the fun. I helped. )
I tried terminal emulator to write adb remount, but just after I wrote it, it gives me an error.
I've put the the update.zip in data folder. but there's like two data folders in my tablet's memory root. Do I put it after mnt or before (I,m using root browser v2.3)? Like in the real root of everything? Another question. Must I use the zip inside another zip of the asus ww rom, or just the unzipped zip file. (LOL, confusing, i know).
(I dunno JerBear, they're very peculiar about what/who they blow)!!
bravesoul said:
I tried terminal emulator to write adb remount, but just after I wrote it, it gives me an error.
I've put the the update.zip in data folder. but there's like two data folders in my tab memory's root. Do I put it after mnt or before?
Click to expand...
Click to collapse
They should be symlinked to the same thing. Let me check...
Well. I only have the data folder that's in the root. Peculiar.
As for the zip file question, go for trial and error. Worst case scenario recovery rejects it.
(We'll work around it )
This is what I get in terminal emulator:
Me176c
bravesoul said:
This is what I get in terminal emulator:
Click to expand...
Click to collapse
You need that command only when you are using ADB over PC
Thanks, but I have other issues.
What zip file should I use? The original we download from ASUS or the zip file inside the original.
JerBear told me to try one or another, but he doesn't know I'm in a place where Internet speed is like 50 Kbps... Which means it takes about two hours to download the original file.
However,(and this will sound strange), if anyone can give me the original names of both the original .182 zip file and the one inside the original, I think I can use a previously (and renamed) downloaded .182 ROM.
Me176c
bravesoul said:
Thanks, but I have other issues.
What zip file should I use? The original we download from ASUS or the zip file inside the original.
JerBear told me to try one or another, but he doesn't know I'm in a place where Internet speed is like 50 Kbps... Which means it takes about two hours to download the original file.
However,(and this will sound strange), if anyone can give me the original names of both the original .182 zip file and the one inside the original, I think I can use a previously (and renamed) downloaded .182 ROM.
Click to expand...
Click to collapse
Use zip inside original.
slayeralive said:
Use zip inside original.
Click to expand...
Click to collapse
So to be clear. I'll use ES File Manager to rename the file (update.zip) and copyit into Root->Data->Turn off the tablet and on again->enter into recovery->in PC I'll use adb->type adb remount and other commands->The tablet will reboot and update into the WW.182 ROM.
Right?
Me176c
bravesoul said:
So to be clear. I'll use ES File Manager to rename the file (update.zip) and copyit into Root->Data->Turn off the tablet and on again->enter into recovery->in PC I'll use adb->type adb remount and other commands->The tablet will reboot and update into the WW.182 ROM.
Right?
Click to expand...
Click to collapse
No man can you read? Do not turn of. Connect to pc and use adb or use terminal. If you are using terminal skip adb commands and start at "su" command. After typing last command it will automaticly reboot to recovery and start instalation than just wait...
slayeralive said:
No man can you read? Do not turn of. Connect to pc and use adb or use terminal. If you are using terminal skip adb commands and start at "su" command. After typing last command it will automaticly reboot to recovery and start instalation than just wait...
Click to expand...
Click to collapse
Ok, ok. Don't get your intelligence in a twist.
Thanks for helping me with my absurd noobiness. :good:
bravesoul said:
Ok, ok. Don't get your intelligence in a twist.
Thanks for helping me with my absurd noobiness. :good:
Click to expand...
Click to collapse
Have fun with your "reward"
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Try again you did somethin wrong
Folow the steps download->extract->rename to update.zip->copy to /data folder->type in terminal
bravesoul said:
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Click to expand...
Click to collapse
If you missd or typed wrong one character in terminal it wont work. Try again.
bravesoul said:
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Click to expand...
Click to collapse
From the top, you must be rooted and you must know what that is.
I used the file from inside the download. I believe it has user in the name.
Rename this file to be update.zip.
Place update.zip into the data folder in the root directory, ie. root/data/update.zip.
Back out of that when it's finished and find the original post with the instructions, touch it and touch the message symbol like you are going to reply.
Copy all of the commands from after su, to the end.
Open terminal emulator, Type su and give root permission at the prompt, touch and paste, you should see what you copied, if you don't, do it again. If you do, touch enter and the process will begin.
Do not do anything until the device reboots COMPLETELY. It will go through several reboots, just wait.
Viola, you will be updated.
Related
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.
Hay, my name's Nick, been reading the posts for a while, decided to join. Iv'e been wanting to root my T-mobile vibrant so i can get a more streamlined ROM will less features to make the ones i use go smoother and faster and get the full potential out of the device. I rooted it no problem with one click root, installed clockwork rom manager, and titanium backup, installed clockwork recovery (i love the clockwork orange icons by the way) put the latest "insanity 0.6.7.zip" in the root of the internal SD, and hit the "install rom" option on the rom manager and selected the .zip, and it made my phone go into the standard recovery mode, no option to install any .zip files. So i opened the rom manager and manually put it into CWM recovery so i could manually install the rom. It looked like it was going to work, but then it sent my phone back to the recovery screen with white text that said "install update.zip" so i did what it said, and it sent my phone into a boot loop. I can get into recovery mode, but when ever i try to recover my backup or access any files it says "no files found, operation canceled" or something like that. It also fails to mount via USB. I can get it to go to download mode but have not tried odin yet, because im on a mac (working on getting bootcamp working now to run windows)
Odin seems like my only option now right? anyone have any idea ware I went wrong? it must have been the incorrect update.zip file right?
I dont think u flashed a vibrant rom
Just mount your internal sd from clockwork and copy over a vibrant rom, and flash
Sent from my SGH-T959 using XDA Premium App
have any idea why it wont let me mount my sd card? that makes me worried it wont connect to a Pc in download mode but i haven't had the opportunity to try that yet.
I'd download your rom of choice, there are a ton that are perfect fit first timers. Trigger and Bionix-V seem very stable. Pop your external sd into your computer, copy the .zip for the rom, go into recovery, select install from zip and flash your rom.
Odin is last resort. I'm not familiar with insanity, but maybe it was a bad download?
when it booted up it went to my normal "vibrant" screen, then to an unfamiliar "galaxy s 19000" screen. Im assuming there is a difference between galaxy s and vibrant right?
jRi0T68 said:
I'd download your rom of choice, there are a ton that are perfect fit first timers. Trigger and Bionix-V seem very stable. Pop your external sd into your computer, copy the .zip for the rom, go into recovery, select install from zip and flash your rom.
Odin is last resort. I'm not familiar with insanity, but maybe it was a bad download?
Click to expand...
Click to collapse
tried that, when i try to to install zip from sdcard it says "no files found"
i assume it's looking for files on the internal and not the external right? so i tried mounting the external sd card from the mounts and storage menu, and i got an error message that said "E:INFO is WRONError mounting SDEXT !"
In recovery, do you see any folders when you click install from zip, or is that when you get an error message?
If you see folders, can you navigate to external_sd?
i click "install zip from SD" and it brings me to a menu with the options to apply sdcard.update.zip or choose zip from sd card, and when try ether one of those options it says "No Files Found"
I have a rom in a zip on the root of my external now, just cant get to it.
Too bad i cant help trying to fix things that aren't broken
niik000 said:
i click "install zip from SD" and it brings me to a menu with the options to apply sdcard.update.zip or choose zip from sd card, and when try ether one of those options it says "No Files Found"
I have a rom in a zip on the root of my external now, just cant get to it.
Too bad i cant help trying to fix things that aren't broken
Click to expand...
Click to collapse
not your external sd, zip should be on your internal sd
since you can get into recovery you can try using adb to push the zip from your computer to the phone
install android sdk and drivers for vibrant then using command prompt navigate to the following directory in the android-sdk folder
\platform-tools\
then execute the following command again in cmd prompt
adb push <dir for zip> /sdcard
if that doesnt work then odin will be your only choice and you must be in download mode to do that
niik000 said:
i click "install zip from SD" and it brings me to a menu with the options to apply sdcard.update.zip or choose zip from sd card, and when try ether one of those options it says "No Files Found"
I have a rom in a zip on the root of my external now, just cant get to it.
Too bad i cant help trying to fix things that aren't broken
Click to expand...
Click to collapse
If you can access xda from your phone,download a vibrant rom from there.
Once it's downloaded,it will be in the root of your internal sd,under download.You can then flash it in cwm,or when the download is complete,click on it and choose Rom Manager to open it,and you can flash it from there.
Here's a link to Bionix 1.3.1,on xda.
http://forum.xda-developers.com/showthread.php?t=925548
amandadam said:
If you can access xda from your phone,download a vibrant rom from there.
Once it's downloaded,it will be in the root of your internal sd,under download.You can then flash it in cwm,or when the download is complete,click on it and choose Rom Manager to open it,and you can flash it from there.
Here's a link to Bionix 1.3.1,on xda.
http://forum.xda-developers.com/showthread.php?t=925548
Click to expand...
Click to collapse
That's useful for me as well.!
shreddintyres said:
not your external sd, zip should be on your internal sd
since you can get into recovery you can try using adb to push the zip from your computer to the phone
install android sdk and drivers for vibrant then using command prompt navigate to the following directory in the android-sdk folder
\platform-tools\
then execute the following command again in cmd prompt
adb push <dir for zip> /sdcard
if that doesnt work then odin will be your only choice and you must be in download mode to do that
Click to expand...
Click to collapse
do i need an update.zip? or just the bionix-v-1.3.1.zip? or am i supposed to rename the bionix zip to update.zip?
niik000 said:
do i need an update.zip? or just the bionix-v-1.3.1.zip? or am i supposed to rename the bionix zip to update.zip?
Click to expand...
Click to collapse
Never rename rom zips to update.zip leave it at bionix.zip and flash through clockwork mod recovery.
now i cant figure out how to get any of the ADB commands to work, i have ADB running and it put a list of commands in he terminal but when i try any of those commands it says "command not found"
i tried
"adb devices" (c-bash: adb: command not found)
"./adb devices" (directory not found)
and "devices" (-bash: devices: command not found
)
am i doing something wrong?
niik000 said:
now i cant figure out how to get any of the ADB commands to work, i have ADB running and it put a list of commands in he terminal but when i try any of those commands it says "command not found"
i tried
"adb devices" (c-bash: adb: command not found)
"./adb devices" (directory not found)
and "devices" (-bash: devices: command not found
)
am i doing something wrong?
Click to expand...
Click to collapse
first you have to be in the android sdk directory and second you must run the sdk manager process and download the rest of the sdk, the bit that you download from the website does not include the full android sdk, you will also need to have java runtime environment 5 or later installed on your pc.
also if you are running adb in linux you need to sudo or su adb commands
in linux you will need to restart the adb daemon
su
adb kill-server
adb start-server
adb devices
hope this helps
i ran the SDK and AVd manager and installed the rest of the SDK packages, then found the ADB file and drug it into the terminal, that gave me the list of commands. I plugged in the phone and tried "adb devices" and it said "command not found" tried quitting and restarting terminal a few times and still nothing
shreddintyres said:
first you have to be in the android sdk directory and second you must run the sdk manager process and download the rest of the sdk, the bit that you download from the website does not include the full android sdk, you will also need to have java runtime environment 5 or later installed on your pc.
also if you are running adb in linux you need to sudo or su adb commands
in linux you will need to restart the adb daemon
su
adb kill-server
adb start-server
adb devices
hope this helps
Click to expand...
Click to collapse
when i enter "su" it asks for a password, but it will not let me type anything. Iv'e never really worked with commands like this but im interested in learning, thats kind of why i decided to mess with the phone
niik000 said:
when i enter "su" it asks for a password, but it will not let me type anything. Iv'e never really worked with commands like this but im interested in learning, thats kind of why i decided to mess with the phone
Click to expand...
Click to collapse
thats a security feature within linux it wont show what you are typing but rest assured its registering keystrokes, and you dont drag and drop to terminal
assuming the androidsdk is in your home directory you would type
cd /home/username/android-sdk/platform-tools
then ./adb devices (this is just a check to make sure your phone is being recognized)
i type
/Users/<my username>/android-sdk-mac_x86/platform-tools
and it tells me
/Users/<my username>/android-sdk-mac_x86/platform-tools: is a directory
then i type ./adb devices
and it says
-bash: ./adb: No such file or directory
im getting really confused, it seems like im making a really simple mistake i just cant figure out what im doing wrong
niik000 said:
i type
/Users/<my username>/android-sdk-mac_x86/platform-tools
and it tells me
/Users/<my username>/android-sdk-mac_x86/platform-tools: is a directory
then i type ./adb devices
and it says
-bash: ./adb: No such file or directory
im getting really confused, it seems like im making a really simple mistake i just cant figure out what im doing wrong
Click to expand...
Click to collapse
ok so you are doing this from mac then? i apologize as i have no experience messing with android using a mac, id imagine itd be much like linux although terminal commands may be different. If i were you id google using adb commands in mac os and see what you can find, personally i use windows normally and am only just learning how to work linux
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?
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update 02/03/2015
This guide I posted is well out of date, there are other methods to follow now days.
Please use http://www.aftvnews.com/tag/guide/ as it is up to date and current.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Thanks to AFTVNews.com for the OTA link and rbox for pointing me in the right direction I've successfully manually upgraded to the latest firmware, downgraded back to 51.1.0.2 and am now upgrading back to 51.1.1.0.
This is the process I followed. I take it for granted that you rooted, have SU and Busybox free installed.
Don't blame me if you **** your device up and you have a brick.
So lets get to it:
1. Download which ever firmware you wish to restore to:
Code:
51.1.0.1
http://amzdigitaldownloads.edgesuite.net/obfuscated/e6f65fefb36aaf7b94fd370f516b9c11/bueller-ota-51.1.0.1_user_510055620-signed.bin
51.1.0.2
http://amzdigitaldownloads.edgesuite.net/obfuscated/cec02756d1964c9cb1f71d52056cc81a/bueller-ota-51.1.0.2_user_510058520-signed.bin
51.1.1.0
http://amzdigitaldownloads.edgesuite.net/obfuscated/568eef32595f034b4304e19aa566befb/bueller-ota-51.1.1.0_user_511069920-signed.bin
51.1.1.0 Update 1
http://amzdigitaldownloads.edgesuite.net/obfuscated/4edaba705e98dee475680c33d3f41132/bueller-ota-51.1.1.0_user_511070220-signed.bin
2. Rename which ever one you wish to restore to update.zip
3. adb shell
4. su
5. chmod 777 cache
6. cd cache
7. chmod 777 recovery
8. cd recovery
9. echo --update_package=/cache/update.zip > command
10. ctrl + c
11. adb push update.zip /cache
--- Go make coffee or take a ****....The pushing of 466MB takes forever over wireless.---
An alternative is to copy update.zip to a USB Flash Drive, use StickMount to mount on the FireTV then copy it with the following command:
cp /sdcard/usbStorage/sda1/update.zip /cache
12. adb reboot recovery
Now it should reboot and start installing whatever update you downloaded and called update.zip :good:
If you get the out of space error:
roligov said:
No it's not because the updates are blocked, it's because you out of space in your cache partition. ADB shell to the box and run
ll /cache
If you have any bin files, delete them.
Click to expand...
Click to collapse
1. adb shell
2. su
3. rm /cache/*.bin
Nice
Nice work and great news! No reason not to update to the latest version since we can downgrade too.
Thanks. Should we delete the file after the update to save on the space or is it automatically deleted?
It automatically gets deleted. It's late this side so I'm going to bed.
Will do some testing tomorrow before I give the go ahead and tell everyone it's all working!
Wow!! I knew someone would figure it out, just did not think it would be this soon. Thank you for the work!!
One step closer to an unlocked bootloader...
Super guide, worked like a charm - thank you!
Good work! Thank-you.
zahir32 said:
Super guide, worked like a charm - thank you!
Click to expand...
Click to collapse
would there be a way to do this via shh
you should probably make a mirror of those firmware bundles. :good:
wavrunrx said:
you should probably make a mirror of those firmware bundles. :good:
Click to expand...
Click to collapse
Good point. I'll dl them tonight and leave them on my NAS. Eventually i"ll put them on dropbox or other filelocker for safekeeping
Getting It Done
bdscds said:
would there be a way to do this via shh
Click to expand...
Click to collapse
This method gets it done. I've tried others, but these instructions - and the fact that the OP has kindly prepared the "command" file for us - make it an easy ride. Just put the update zip in the same folder as your ADB setup, open your command window in that folder and adb will find it.
Thanks!
With this we can safely update to latest version!
Nice guide
Sent from my iPhone using Tapatalk
Can this be done over a local network or do I have to hook the Fire TV up to my PC using a USB (Male to Male) lead?
gazdaman. said:
Can this be done over a local network or do I have to hook the Fire TV up to my PC using a USB (Male to Male) lead?
Click to expand...
Click to collapse
http://www.firetvnews.com/how-to-sideload-apps-to-your-amazon-fire-tv-using-a-windows-pc/
network
shows you how to use adb, so you can do "adb shell"
be careful though, if you were to mess anything up in the process you could render your fire tv useless.
roligov said:
Thanks to FireTVNews.com for the OTA link and rbox for pointing me in the right direction I've successfully manually upgraded to the latest firmware, downgraded back to 51.1.0.2 and am now upgrading back to 51.1.1.0.
This is the process I followed. I take it for granted that you rooted, have SU and Busybox free installed.
Don't blame me if you **** your device up and you have a brick.
So lets get to it:
1. Download which ever firmware you wish to restore to:
Code:
51.1.0.1 update
http://amzdigitaldownloads.edgesuite.net/obfuscated/e6f65fefb36aaf7b94fd370f516b9c11/bueller-ota-51.1.0.1_user_510055620-signed.bin
51.1.0.2 update
http://amzdigitaldownloads.edgesuite.net/obfuscated/cec02756d1964c9cb1f71d52056cc81a/bueller-ota-51.1.0.2_user_510058520-signed.bin
51.1.1.0 update
http://amzdigitaldownloads.edgesuite.net/obfuscated/568eef32595f034b4304e19aa566befb/bueller-ota-51.1.1.0_user_511069920-signed.bin
2. Rename which ever one you wish to restore to update.zip
3. adb shell
4. su
5. chmod 777 cache
6. cd cache
7. chmod 777 recovery
8. cd recovery
9. wget http://dl.dropboxusercontent.com/u/16913146/command
10. ctrl + c
11. adb push update.zip /cache
--- Go make coffee or take a ****....The pushing of 466MB takes forever.---
12. adb reboot recovery
Now it should reboot and start installing whatever update you downloaded and called update.zip :good:
Click to expand...
Click to collapse
Thanks for the info! I hear the new update offers nothing new and causes more problems than good by disrupting the alphametical order of sideloaded apps. Is it worth updating for or will there be no significant differences? It's funny because amazon.com don't mention a new update release.
Also does you update method require you to re-root the device or does root survive the update? Thanks very much!
Got it working with Windows 7
This is how I done it.
(Ensure you have ADB installed - If not google "ADB setup 1.3 windows")
Download the chosen firmware and rename it to update.zip
Download roligov's command file
remove the .txt extension that windows gives it when you download it. The filename should just be "command" with no extension otherwise you will get the failed message when you reboot to recovery.
Now run command prompt as Administrator
(I will use C:\ as the file location example)
adb kill-server
adb start-server
adb connect "Fire TV IP Address"
adb shell
su
chmod 777 cache
cd cache
chmod 777 recovery
ctrl + c
adb push C:\command /cache/recovery
adb push C:\update.zip /cache
--- Go make coffee or take a ****....The pushing of 466MB takes forever.--- (Took 2 minutes over LAN for me)
adb reboot recovery
Done
Many thanks to roligov for the initial find to set me on my way.
Yeah my FireTV is hooked up to my Wireless so it takes forever to push the update.
roligov said:
Yeah my FireTV is hooked up to my Wireless so it takes forever to push the update.
Click to expand...
Click to collapse
if one has a usb thumb drive and stick mount installed, copying the .bin to the /cache folder step might be faster?
User copies .bin file(s) and command file to a folder on thumb drive where a script file which lists .bins in thumbdrive folder and allows user to choose a numeral and then executes commands for update process would be cool for newbies. even having the script "autocreate" the command file.
So i am having a issue with my oneplus 5 and hope someone could help me out
So i have ended up wiping the entry phone in recovery, getting rid of all the internal data, including sdcard & operating system. At the moment the only thing i can get access to is fastboot & TWRP. I am trying to sideload or push a rom zip to the phone, but all i keep getting is the below:
adb sideload "Zip folder name and extension".
loading "zip"
cannot read "zip"
or i get an error that just says "Closed.
Now i have update to the latest drivers and adb and when i type "adb devices" my phone is showing...
I have also flashed the oneplus 5 recovery via fastboot, however when i go on to adb sideload, the phone doesnt show in CMD.
any help here will be appricated, as i am out of ideas.
Thanks in advance.
Make the file names shorter.
Alternatively, you should be able to use a flash drive through OTG and install the stuff from it.
Rhoban said:
Make the file names shorter.
Alternatively, you should be able to use a flash drive through OTG and install the stuff from it.
Click to expand...
Click to collapse
Unfortunately, OTG isnt a selectable option and i have also tried shorting the file a names but still no look.
Thank you for the input
Use another recovery. OTG should be there, I know somebody that flashed ROMs this way.
KrypticGT said:
...
adb sideload "Zip folder name and extension".
loading "zip"
....
Click to expand...
Click to collapse
Two things I'd try:
1. Change your directory to the one containing the zip file so the command ONLY has the filename.zip in it
2. Download the zip file again and make sure you do a md5sum check on it just in case its corrupted.
Try this:
- Boot your phone in TWRP
- Open cmd.exe on your PC
- Type adb devices (if everything is ok, it should show some numbers followed by the write "recovery")
- Move your ROM inside a folder on your PC and rename it "Rom.zip" (ie inside the folder "download")
- Using CMD.exe, move inside that folder typing "cd C:/...."
- Type "adb push Rom.zip /sdcard"
- Wait til a confirmation message will appear on CMD.exe
- Flash the ROM using TWRP
So for future reference to anyone that might have the same issue.
I fixed this issue, by flashing a older version of TWRP. This allowed me to use ADB sideload without issue & also allow OTG_USB. It also allowed me to flash files with long names.... I have tried to go back to the latest version of TWRP for OP5 but i get the errors i was getting before.
Strange, but did the fix.
Thanks all for the help & input.