Why does Goo Manager install 2.14. Aren't there newer versions available ?
sailerph said:
Why does Goo Manager install 2.14. Aren't there newer versions available ?
Click to expand...
Click to collapse
2.4.3 is the newest version. You can download it here : http://goo.im/devs/succulent/acclaim/recovery
Sure, but why doesn't Goo manager install the newest ?
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
sailerph said:
Sure, but why doesn't Goo manager install the newest ?
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
What do you mean? You have to manually download the recovery program. Rename it to recovery.img and place it in your BOOT partition in replacement of your current recovery.
I mean within GooManager, select install open recovery script installs 2.14,
Could you please elaborate on how to copy it to the boot partition? Can that be done from within the device, or do you need to be connected through USB/adb?
Sent from my Acclaim using xda app-developers app
datallboy said:
Rename it to recovery.img and place it in your BOOT partition in replacement of your current recovery.
Click to expand...
Click to collapse
I went ahead and used fastboot to update my recovery, and I understand that using the flash_image binary is a second option, but this instruction has me curious if there's a third way to do it. Any further details would be appreciated.
In case it helps anyone else, I thought I'd document a couple of the "gotchas" that I ran in to. Some of the guides I'd read didn't seem to cover a key point here or there.
Obvious to the experienced dev, I didn't realize that for fastboot to work I actually had to boot to the cyanoboot screen and 'start fastboot', then run the fastboot command on my pc. /facepalm
Windows (I'm on Win7) detected the NT with a different PID (physical ID?) in Device Manager depending on whether I was booted into cyanoboot, recovery, or fully into android, so I ended up modifying android_winusb.inf three times and installing the drivers three times, once for each state.
I too wonder why Goo Manager doesn't install a newer version. But... I'm glad for the experience of installing the ADB SDK and using fastboot.
Cheers!
---------- Post added at 12:43 PM ---------- Previous post was at 12:39 PM ----------
I was thinking about trying TWRP 2.5. Has anyone tried it?
InUrKitchin said:
I went ahead and used fastboot to update my recovery, and I understand that using the flash_image binary is a second option, but this instruction has me curious if there's a third way to do it. Any further details would be appreciated.
In case it helps anyone else, I thought I'd document a couple of the "gotchas" that I ran in to. Some of the guides I'd read didn't seem to cover a key point here or there.
Obvious to the experienced dev, I didn't realize that for fastboot to work I actually had to boot to the cyanoboot screen and 'start fastboot', then run the fastboot command on my pc. /facepalm
Windows (I'm on Win7) detected the NT with a different PID (physical ID?) in Device Manager depending on whether I was booted into cyanoboot, recovery, or fully into android, so I ended up modifying android_winusb.inf three times and installing the drivers three times, once for each state.
I too wonder why Goo Manager doesn't install a newer version. But... I'm glad for the experience of installing the ADB SDK and using fastboot.
Cheers!
---------- Post added at 12:43 PM ---------- Previous post was at 12:39 PM ----------
I was thinking about trying TWRP 2.5. Has anyone tried it?
Click to expand...
Click to collapse
Connect your USB cable to the computer and find your device's BOOT partition. Should be a FAT32 partition so Windows can read it. Replace "recovery.img" with whatever newer recovery you want. That's how I replace the recovery. I'm using a SDC version so I can also change it on my tablet. I go to /storage.sdcard1 and replace recovery.img from there.
That sounds easy. Surely there's a catch!?:thumbup:
Sent from my SGH-I727R using xda app-developers app
datallboy said:
You have to manually download the recovery program. Rename it to recovery.img and place it in your BOOT partition in replacement of your current recovery.
Click to expand...
Click to collapse
Recovery is located in /boot only in SD-based ROM image. When running ROM internally on emmc, Recovery is located in /recovery partition. Also emmc and sd recovery use different versions of recovery.img.
datallboy said:
Connect your USB cable to the computer and find your device's BOOT partition. Should be a FAT32 partition so Windows can read it. Replace "recovery.img" with whatever newer recovery you want. That's how I replace the recovery. I'm using a SDC version so I can also change it on my tablet. I go to /storage.sdcard1 and replace recovery.img from there.
Click to expand...
Click to collapse
I tried this, booted into Android on an SDC, and all I see from Windows Explorer is the Acclaim's "Internal storage" drive, with only LOST.DIR in it. On the tablet itself /storage/sdcard1 appears to be empty...
Related
Hi everyone,
I tried using a script which automated the install for the the custom recovery, but I started to get messages that it ran out of disk space (I can't link to the file due to my noob status). I probably should have come here first before using that script, but such as life..
I have no important data on the phone, if I lose it all that's ok.
It rebooted and my p500 waits with the following
"Fastboot mode started"
"udc_start()"
It also gives some info when USB is connected ie.
"- suspend -"
"- reset -"
Do I have a paperweight?
thanks and sorry for the newb post ..
edit: so I found this : http://forum.xda-developers.com/showthread.php?t=1003790 and
http://forum.xda-developers.com/showthread.php?t=875881
and have gotten it to the yellow emergency mode, not sure how to flash it from here though.
edit2: dling the stock firmware from http://forum.xda-developers.com/showthread.php?t=1073827
edit3: there's this as well.. http://forum.xda-developers.com/showthread.php?t=1088046 If I try this method, will it screw up again from too little free disk space?
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
thank you very much, I appreciate it haha
Your phone has booted in fastboot mode. Go to development section and read a tutorial how to recover from fastboot.
Sent from my LG-P500 using XDA Premium App
setTopbox said:
thank you very much, I appreciate it haha
Click to expand...
Click to collapse
Then did u unbricked now
Mahesh
go here....
http://forum.xda-developers.com/showthread.php?t=1088046
or here
http://forum.xda-developers.com/showthread.php?p=13813493
How to install Android SDK /ADB
http://lgoptimusonep500.blogspot.com/2011/01/how-to-install-android-sdk-adb.html
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Most honest post I've seen on the entire forum.
Sent from my Kyocera Echo.
mvgadagi said:
Then did u unbricked now
Mahesh
Click to expand...
Click to collapse
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
setTopbox said:
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
Click to expand...
Click to collapse
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
shhbz said:
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
Click to expand...
Click to collapse
Erm... reading all the posts about fastboot after using ROM Manager for this, I guess I would rather stick with the custom script using flash_image.
doktornotor said:
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
Click to expand...
Click to collapse
hmm, I'm not sure (when I dl'd the file I did compare the hash as per instructions). I used the following instructions:
manast.com/2011/05/07/how-to-install-custom-recovery-on-lg-optimus-one-p500
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
setTopbox said:
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
Click to expand...
Click to collapse
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
doktornotor said:
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
Click to expand...
Click to collapse
I'm getting permission denied when trying to use flash_image. Gingerbreak says the device is rooted, and the terminal does ask for superuser permission when i open it (su works in the terminal). I also tried chmod 755 flash_image but that didn't work either.
the permissions for flash_image are r-xr-x any thoughts ?
edit: apparently the sdcard is mounted with -noexecute ? So I tried copying flash_image to / but it's read only. Is there somewhere where I can execute this?
This rf.sh script seems most notorious, I too went into fastboot after that. Doktornotor's method worked (in fact I think he/she was the one who bailed me out back then as well).
If you got into fastboot, most probably you have a rooted phone.
To use flash_image you need to get the flash_image.sh on the root of your sd card. Search the forum for Amon-Ra custom recovery, and you shall find this file in that thread (it is required for Amon ra setup). Log in to your adb console, and use fastboot to push the new image in the recovery partition.
Unless your recovery.img or flash_image.sh is corrupted, it will work for sure.
Keep in mind, fastboot is a very powerfull tool, if you can access it, you're safe.
Cheers,
Alex
did you get out??
just flash stock firmware with kdz worked for me bro
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Dr.Alani said:
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
setTopbox said:
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
Click to expand...
Click to collapse
I do not see how you need to use adb.
Sent from my LG-P500 using XDA App
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
EDIT 1: REUP'D CWM mod
EDIT 2: reordered process to make more sense
Method:
1. Download the Beta CWM mod from rootzwikis credit to birdman EDIT:REUP'ED http://d-h.st/Fdp
2. Using fastboot, DO NOT FLASH Clockwork mod just use the syntax
"fastboot boot 'File path of clockwork mod image'
Note* this will boot directly into the recovery without permanently writing to the recovery and boot partition on the eMMC on the Nexus Qs board
3. Download the posted CWM factory backup posted
4. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup while in CWM recovery
*The device should show up in "adb devices" while in the CWM recovery*
5. *TEXT WILL BE REALLY SMALL! Now navigate with the Scroll wheel to backups and restore and tap the mute button to select.
*IF SOMETHING IS SELECTED IN ERROR THERE IS NO BACK BUTTON JUST REBOOT AND REDO FASTBOOT BOOT*
6. Now select restore and select the image folder
7.blah blah CWM Freaking MAGIC
8. Your Q is back to factory state
If someone wants to PM me or show me how to package this in a nicer CWM zip to install with a script let me know
http://d-h.st/yeo
*Note* I am NOT responsible if you brick your already bricked Nexus Q*
You sir get a beer, since my 2nd (dev) Q won't arrive until later this week, and mine was a shot put until this post.
If you happen to be in NYC before I move to SF, you get three beers.
Hoppy ones.
I am moving to SF
Did the reflash go smoothly?
fiveipads said:
I am moving to SF
Did the reflash go smoothly?
Click to expand...
Click to collapse
No unfortunately it didn't--I blew away all partitions other than bootloader so I can't, to my knowledge at least, push the zip since I can't adb.
I've got factory recovery, boot, system imgs but the system img won't push out because of fastboot's apparent inability to handle files that large (1GB exactly I believe).
...I guess I have to patiently await my second Q but the point of having two was to *use* one and have one for dev... rather than have one as a heavy reminder of my overzealous endeavors...
Hopefully I can give it more time while on this SF trip...
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Does our Q's have internal memory.. if not wouldn't it be possible to run back up of off otg memory stick if recovery would support it
Sent from my Galaxy Nexus using xda premium
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The problem I'm having is that ADB is not responding from CWM... at least not on a Windows machine. The drivers are fine as ADB was working in normal mode before my issue sprung up.
EDIT: As suspected Virtual Ubuntu on a Win host didn't see the device, Physical Ubuntu had no issue. NQ reloaded.
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Can we do this by say pushing the file to the download folder and then installing from zip?
And i know slightly off topic but once we've installed some apks for example, what's currently the best interface to use to navigate through the apps and use them?
How do I make a directory on Nexus Q
fiveipads said:
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
Method:
1. Download the posted CWM factory backup posted
2. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup
http://d-h.st/yeo
Click to expand...
Click to collapse
In step 2 you say make a directory for the file that is posted below. How do I create a directory on the Nexus Q? Currently my Q is stuck in a bootloop after trying to launch CWM from a Galaxy Nexus. If you could post command codes that would be awesome!
I figured it out. You can just follow step #4 and in CWM you can push the CWM Factory img to the /sdcard/Download/ folder and use CWM to unzip and launch.
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
discoltk said:
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
Click to expand...
Click to collapse
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
WildSatchmo said:
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
Click to expand...
Click to collapse
Me as well...not sure why I got this damn thing...lol
The edit didn't prompt an email to me even though I'm following the thread, so those of you looking for the clockworkmod beta image please take note that OP was kind enough to provide a working link to the image.
Thanks fiveipads!
Can someone post full backup please?
caioketo said:
Can someone post full backup please?
Click to expand...
Click to collapse
The link at the bottom still works for me...
http://d-h.st/yeo
..
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
UKROB86 said:
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
Click to expand...
Click to collapse
BUMP.. stuck in CWM unable to get a restorable file.. no idea why...
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Lokifish Marz said:
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Click to expand...
Click to collapse
The problem with putting Quantum singularity project on is that I can't turn on ADB debug, because i use a bluetooth mouse and keyboard, don't have an OTG mouse/keyboard, so somehow I need to be able to connect with adb to setup a bluetooth connected mouse/keyboard
I was thinking to install stock image, and then without wiping install Quantum SIngularity Project over top to preserve the settings for usb debug, on.
what's confusing to me is that i've restored the stock image many times before, and never had a problem.. that's why im wondering what the problem is.. if im typing something wrong.
I used the OneClickRestore as you said, and im just booting it up now
EDIT: didn't get past boot logo, i'll try again
So just to confirm this OneClickRestore is loading the stock nexus Q img right? I've never used it before I usually manually do it
EDIT: still stuck at the nexus q logo before home screen
do you see any error in my commands of trying to push the stock img folder (original post) to "/sdcard/clockworkmod/backup" ? I've done it many times before never had a problem
I never noticed that CWM was different for 1.2 and 1.1. I currently have 1.2 and tired to install CWM which was the wrong one.
When I try to enter recovery, I get a message of " booting recovery kernel image"
I can turn it off and enter into the stock rom no problem.
Any help would be great to how I can undo this and install CWM.
Used the link for CWM from step 1 from this LINK
Thanks very much.
Tap UI Version : 1.2-5699
Kernal - 2.6.32.9-svn4979
Build - FRF91
Here is a link to a .zip I built for you. You will need to have root access for this.
fix-recovery.zip
Download this to your Gtablet and unzip it to /sdcard. Iif you can't make that work, download to your PC and unzip, then transfer the files over to /sdcard. Using a root file manager (I like ES File Explorer), move the file 'flash_image' into /system/bin, overwrite or rename the existing version if there is one, and change the permissions to make it executable (match the other executable files in the /system/bin folder). Then move the file 'cwm5502.img' into /system/etc/recovery (you might have to create the 'recovery' folder). Next, go back to /sdcard and change permissions on 'fixrecovery.sh' to make it executable as well.
Now open Terminal Emulator (install from the Play store or by other means if you don't already have it) and enter the following commands:
Code:
su
sh /mnt/sdcard/fixrecovery.sh
If the second command won't run, bypass the script by running this instead:
Code:
su
/system/bin/flash_image recovery /system/etc/recovery/cwm5502.img
That will install a version of CWM that is compatible with the 1.2 boot loader. Reboot and you should be able to enter the new recovery. Post back if you cannot get this to work for you, and we can try another way. This would be easier if you have ADB installed and working, but I assume most people do not.
Rochey21 said:
I never noticed that CWM was different for 1.2 and 1.1. I currently have 1.2 and tired to install CWM which was the wrong one.
When I try to enter recovery, I get a message of " booting recovery kernel image"
I can turn it off and enter into the stock rom no problem.
Click to expand...
Click to collapse
Since you have the stock VS ROM, you'll have to use nvflash. See this thread.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
DaggerDave said:
Here is a link to a .zip I built for you. You will need to have root access for this.
...
Click to expand...
Click to collapse
Good try, but, there's no su on stock ROM; and the process to get one correctly installed is slightly involved.
The user will have to resort to nvflash.
rajeevvp said:
Since you have the stock VS ROM, you'll have to use nvflash. See this thread.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
Good try, but, there's no su on stock ROM; and the process to get one correctly installed is slightly involved.
The user will have to resort to nvflash.
Click to expand...
Click to collapse
Ok thanks, but I can not find the drivers for APX Mode, using Windows vista 32 bit?
Also just to make sure what Files would I need to use. Just want to make sure exactly what to do, and get it right.
Download the TeamDRH_350M_Prep.zip file from this post. It should have both the nVidia APX drivers and CWM-5.5.0.4 for a 1.2 bootloader (in part9.img).
Read the README file for the APX driver installation, but, don't run the NVFlash_gTablet.bat batch file. Instead, just write a new CWM using the commands in the link in my previous post.
EDIT: Note that you cannot install or upgrade the stock VS ROM using CWM. That can only be done using the stock recovery. For everything else, however, you can use CWM.
Feel like a total N00b :crying:
I have the drivers installed for AXB. I have downloads the zip folder with the img files and drivers etc. I renamed this folder to NVFlash for short.
Do I leave this folder on my laptop or put in on the tablet.
Could you please explain a bit more how to use the command window. I open it but cant seem to get it to work.
I have the folder I download unzipped and saved as C:\NVFlash
Not sure how to do step 2
2. Run this command to determine the partition no. of the recovery (SOS) partition--usually, it is 9: Open a CMD.exe window, then change into the directory containing both the nvflash.exe and the bootloader.bin files. Then run:
You have been very helpful thanks again.
Rochey21 said:
Do I leave this folder on my laptop or put in on the tablet.
Click to expand...
Click to collapse
It's meant to be used on an x86 system (desktop, laptop, ...) running Windows or Linux. You can't run .dll and .exe files--Intel binaries--on an ARM tablet, right?
Could you please explain a bit more how to use the command window. I open it but cant seem to get it to work.
I have the folder I download unzipped and saved as C:\NVFlash
Click to expand...
Click to collapse
Change to the directory containing the nvflash executable and bootloader.bin like this (only type in the stuff in bold):
Code:
[I]C:\SOME\PATH[/I]> [B]cd c:\NVFlash[/B] [I]Change to NVFlash directory[/I]
C:\NVFlash> [I] Note the changed prompt[/I] [I]now[/I]
After that, substitute C:\NVFlash\part9.img instead of C:\SOME\PATH\recovery.img in the given command line.
I understand I cant run the files on the tablet, just meant do I need to transfer any files to the tablet during the process or is it all done through the command window.
I have attached the command window. I typed cd c:\NVFlash and the directory changed to NVFlash.
Not sure how I substitute img 9 then?
EDIT* I got the p.txt file. How would I read this file?
Just looking to get CWM running so I can update to a new custom rom.
Rochey21 said:
I understand I cant run the files on the tablet, just meant do I need to transfer any files to the tablet during the process or is it all done through the command window.
Click to expand...
Click to collapse
No need to transfer anything.
EDIT* I got the p.txt file. How would I read this file?
Click to expand...
Click to collapse
Any editor will read that file. Just double-click on the filename.
Just looking to get CWM running so I can update to a new custom rom.
Click to expand...
Click to collapse
Which one?
rajeevvp said:
No need to transfer anything.
Any editor will read that file. Just double-click on the filename.
Which one?
Click to expand...
Click to collapse
JellyBean Smoother Seems to be good?
Sorry which editor would that be? I opened it in wordpad/notepad and it is all just symbols.
Would something like Hex editor read it?
Rochey21 said:
JellyBean Slim Seems to be good?
Click to expand...
Click to collapse
In that case, shut off the tablet; put it back into APX mode using Power and Vol [-]; then double-click the NVFlash_gTablet.bat batch file. It will do all the prep steps (including installing CWM) needed for a Jellybean ROM install. After the tablet boots into CWM, transfer the ROM install zip file onto the tablet and follow the instructions given in the ROM's first post to install the ROM.
Sorry which editor would that be? I hope it in wordpad/notepad and it is all just symbols.
Click to expand...
Click to collapse
Ah! You've got one of the screwey nvflash executables which produce a binary output. Ignore all this, then.
Ok So do I ignore everything or click the NVFlash_gTablet.bat file?
Rochey21 said:
click the NVFlash_gTablet.bat file?
Click to expand...
Click to collapse
Yes.
(Turn the tablet off, then put it back into APX mode again, though. Otherwise, the batch file will error out.)
rajeevvp said:
Yes.
(Turn the tablet off, then put it back into APX mode again, though. Otherwise, the batch file will error out.)
Click to expand...
Click to collapse
Finally :victory:
Thanks very much for all your help.
I have Smoother Bean installed, doesn't seem to be running correctly but il figure that out myself.
Thanks again.
Hello,
I installed last week this version of android on my G9, all was fine until today when my tablet ran out of battery, I plugged it and start it again as I always do in that case. Except that today android didn't start and I got the multiboot screen which you can see in attached files. I tried both options but my tablet always restart on that screen.
When my tablet is plugged into my computer it is not recognized so I can't put a new ROM of android and make a new installation, I tried to use ADB to debug it but there are no device detected ...
Does someone have a solution to my problem ?
Thanks in advance for your answers.
Olorin59.
PS: sorry if there are language mistakes in what I wrote but i'm French so English is not my birth language.
You have 2 options right now. You can either just install stock ROM, or if you have Linux in you computer you can use sde to mount data partition to your PC and moving the ROM again in there.
Installing stock ROM is easier and faster, so I recommend doing that. You remember how it goes? Download latest firmware from achos' site an use firmware update option located in sde.
Sent from my GT-I9100 using xda app-developers app
I think I already tried that : download the aos file from the official site of archos, go in recovery mode, chose upgrade firmware and copy the aos file to the drive which appears on my computer then chose ok ???
If it is that I tried and I got an error message "update failled : 221".
So if it is that could you explain me more how to do it with linux, i'm not sure I understood everything.
olorin59 said:
I think I already tried that : download the aos file from the official site of archos, go in recovery mode, chose upgrade firmware and copy the aos file to the drive which appears on my computer then chose ok ???
If it is that I tried and I got an error message "update failled : 221".
So if it is that could you explain me more how to do it with linux, i'm not sure I understood everything.
Click to expand...
Click to collapse
Okay.
That 221 sounds weird.
After booting in to Linux (livecd is sufficient, I recommend Ubuntu or variant of it), open the sde in archos and navigate to data mount option. I can't remember what it is called, but should be something like mount data partition. Then plug your tablet to PC running Linux, and the PC should find the tablet.
You should now be able to browse data on /data partition of the tablet, but writing there requires you to use superuser.
Check the path to data partition. If I remember correctly, it will be something like /media/(device name)/ but I'm not sure.
Navigate to archos.etx4.update file and use this command to move it:
sudo mv archos.ext4.update path-to-data/media/archos.ext4
If /media/path-to-data/media won't work, try using /media/path-to-data/local
Sent from my GT-I9100 using xda app-developers app
I don't have mount data partition but I do have "export data partition" and "export hard disk (H models only)" in the developer edition menu, is it what you are talking about ?
olorin59 said:
I don't have mount data partition but I do have "export data partition" and "export hard disk (H models only)" in the developer edition menu, is it what you are talking about ?
Click to expand...
Click to collapse
Yeah, that is the one: export data partition
Sent from my GT-I9100 using xda app-developers app
When I plugged my tablet, ubuntu told that I do not have the authorisation to see the content of the drive ...
Can't I do the same with windows ?
olorin59 said:
When I plugged my tablet, ubuntu told that I do not have the authorisation to see the content of the drive ...
Can't I do the same with windows ?
Click to expand...
Click to collapse
HMM.. That sounds weird, as I do not have that problem. Can you try other Linux? I think backtrack allows you to login as root, so you are able to do anything...
The filesystem of data partition is ext4 I guess... Or ext3. Windows can not read ext filesystem, so you can't use windows.
Sent from my GT-I9100 using xda app-developers app
Ok I'll try an other version of linux, backtrack is downloading as i'm writing this. I'll get back to you soon.
Hi julle131, I'm currently using backtrack which as you told allows me without problems to access the data on the tablet.
I'm a little bit lost about what's next to do.
The tablet appears as a drive called "data" in which there a is folder called media as you said, inside it there are a lot of folders for various apps I had installed. If I understood correctly the goal is to find the archos.ext4 file but I can't find it ...
Can I download the archos.ext4 file and put it again on the memory of my tablet to re-install it ?
olorin59 said:
Can I download the archos.ext4 file and put it again on the memory of my tablet to re-install it ?
Click to expand...
Click to collapse
Yes you can.
Hopefylly after downloading archos.ext4, your tablet will hopefully work normally again :thumbup:
Sent from my GT-I9100 using xda app-developers app
So, I copied archos.ext4 to in the media folder of the tablet then in recovery mode, I flashed kernel and initramfs but after that my tablet don't reboot, it don't have the multi boot menu or anything and when I press the start button nothing happens I can only access the recovery menu. Do you have any idea ?
olorin59 said:
So, I copied archos.ext4 to in the media folder of the tablet then in recovery mode, I flashed kernel and initramfs but after that my tablet don't reboot, it don't have the multi boot menu or anything and when I press the start button nothing happens I can only access the recovery menu. Do you have any idea ?
Click to expand...
Click to collapse
The initramfs you flashed probably does not have multiboot menu. Keep the zImage from the rom you downloaded and get initramfs from this link:
http://forum.xda-developers.com/showthread.php?t=1578438
when you download the zip, only extract the initramfs.
Then install zImage from the original rom and initramfs from the multiboot menu thread. That should bring the multiboot menu back, and hopefully you can see the new archos.ext4 in there.
I just tried : Kernel (zImage) not found !
olorin59 said:
I just tried : Kernel (zImage) not found !
Click to expand...
Click to collapse
What i meant was to take the zImage from the rom you downloaded and initramfs from my link, and install them both.
Make a new folder to the desktop, and extract initramfs from the link i gave you in earlier post.
Now you have a new folder with initramfs inside it. Then put the zImage from the rom you downloaded to the folder.
Now you should have a folder which has initramfs AND zImage, right? Then just install them to the tablet. This way you get the multiboot and the new kernel.
It's what I did.
I chose flash kernel and Initramfs in the recovery menu and I paste inside the ramdisk the initramfs from your link and the zImage from my ROM.
I tried both version of the initramfs from the link you gave me.
Any idea, please ?
I'm still stuck on the multi boot menu ...
Can someone help me please ?
With my external SD formatted as internal storage, CR Droid Rom file can't be found for me to flash it. No matter where I put the zip file, I can't find it when I go into Recovery. Any ideas?
bbrooks182 said:
With my external SD formatted as internal storage, CR Droid Rom file can't be found for me to flash it. No matter where I put the zip file, I can't find it when I go into Recovery. Any ideas?
Click to expand...
Click to collapse
Both storage showing in recovery??
Make sure you didn't change from zip to rar..
In Recovery under storage it has the internal storage which includes the SD card and then a small external of 15mb. And yes, it's still a zip file.
bbrooks182 said:
In Recovery under storage it has the internal storage which includes the SD card and then a small external of 15mb. And yes, it's still a zip file.
Click to expand...
Click to collapse
Other zips are showing??or twrp is not showing any zips??
Now that you mention it, I don't think any zips are showing.
bbrooks182 said:
Now that you mention it, I don't think any zips are showing.
Click to expand...
Click to collapse
Try to reset twrp.or change twrp version..
Which version you are using??
Version 3.02.0 how do I reset it?
Just did a little checking and I'm downloading the Twrp app.
bbrooks182 said:
Version 3.02.0 how do I reset it?
Click to expand...
Click to collapse
Use latest 3.1.1...
---------- Post added at 07:28 PM ---------- Previous post was at 07:27 PM ----------
bbrooks182 said:
Just did a little checking and I'm downloading the Twrp app.
Click to expand...
Click to collapse
You can download it from twrp site and flash it via adb...
Yeah, it's not working via the TWRP app. ADB is through a computer, right?
bbrooks182 said:
Yeah, it's not working via the TWRP app. ADB is through a computer, right?
Click to expand...
Click to collapse
Yes. .
Download recovery.IMG and flash it by this command..
fastboot flash recovery recovery name.img
I downloaded the latest twrp and the filename is twrp-3.1.1-0-kiwi. Using that command I added . img at the end of the filename. I received an error in ADB stating it cannot load that file. I just t looked at the instructions and I forgot to wipe the system and cache before installing the new CR Droid zip. Does that make a difference? Should I do that and try installing the new version of the Rom? Or will the issue of not being able to see the Rom zip file still be there?
bbrooks182 said:
I downloaded the latest twrp and the filename is twrp-3.1.1-0-kiwi. Using that command I added . img at the end of the filename. I received an error in ADB stating it cannot load that file. I just t looked at the instructions and I forgot to wipe the system and cache before installing the new CR Droid zip. Does that make a difference? Should I do that and try installing the new version of the Rom? Or will the issue of not being able to see the Rom zip file still be there?
Click to expand...
Click to collapse
No need to wipe anything..
Rename recovery to just twrp.IMG and then try again..
Twrp you are flashing should be in the adb folder..
Renamed it to just twrp and got the same error message. What I was asking about wiping the cache and system is if I want to install the latest CR Droid Rom. I really appreciate your help and please don't feel like you're committed to helping. I may just see if I can flash the new ROM using adb
bbrooks182 said:
Renamed it to just twrp and got the same error message. What I was asking about wiping the cache and system is if I want to install the latest CR Droid Rom. I really appreciate your help and please don't feel like you're committed to helping. I may just see if I can flash the new ROM using adb
Click to expand...
Click to collapse
It shouldn't give that error...
You can flash new twrp with old twrp too..
Just copy it in SD and and click installed/image and locate and flash it in recovery partition....
Caution don't flash it in boot partition..
No you cannot flash custom ROM via adb fast boot... You need a twrp recovery to flash that...
I gave the TWRP app another read try and it worked. I was able to update twrp and that allowed me to install the new ROM. Thanks for your tips and help!
bbrooks182 said:
I gave the TWRP app another read try and it worked. I was able to update twrp and that allowed me to install the new ROM. Thanks for your tips and help!
Click to expand...
Click to collapse
Enjoy...:good: