Okay, where to start.. I think I have bricked my phone pretty good.
Here is the approximate list of things that happened.
I wanted to try to update to froyo, so I downloaded z4root, worked beautifully
Followed all the directions to install clockwork mod (including reading far enough ahead to find out the one in the directions was for the 7015, but gave the link for the 7005 version later) - Worked like a charm
BACKED UP SYSTEM as instructed
Then here is where things went south. I attempted to install the Cyanogen Mod froyo based. I followed the directions, including backing up softmac and wpa_supplicant files. And it would not start up. I could get it into recovery mode but not to start fully. I tried doing the restore, it couldn't mount the SD Card where the backup was. Being knowledgeable enough to dangerous in Linux, I used ADB Shell and tried various things to try to find out where the SD Card or recovery image failed. I had also been trying to locate FWDN as I saw people had done fixes with that, but I couldn't get it to load in FWDN "Mode". I figured if I could replace the recovery program on there that doesn't work with the one that does, it should in theory allow me to reboot into the correct recovery mode and let me pull the files from my SD Card. After about 15 minutes of shuffling around, I ended up mounting the \system folder where I found a file called recovery. Looked to be the right size. So I made a modified batch file that would instruct it to load from that folder.
After that mistake, all of the sudden, the vtc driver that I had installed did see the unit. I was like Joy! Joy! I fired up fwdn but since I didn't have the original files that it "liked" I used an lk.rom, but I think it wasn't from an X5A but from a lonpad. Now I don't even get COBY on the screen.
But wait, I'm even more dangerous. I got the hardware ID that it's currently using on the USB bus, edited first the vtc ini file to see if I can reload a different rom. It detects it, but FWDN gives me "bad boot" error or something like that. But I'm a trooper, if I'm gonna kill it, I'm gonna kill it good. I change the SDK/ADB driver to recognize the device. And it seems to recognize it. Then I went to try "fastboot flash recovery recovery.x5ag.img " which I had NEVER been able get the unit into fastboot mode, and it goes through and does it. Then I do a fastboot reboot to see if I can get it to come up in recovery mode, but I can't.
Then the final bright idea comes up on me.. Hey, I have the backup from SD card, what if I zip it up, call it update.zip, and do a fastboot update?
Now ADB can make some kind of connection to it, but when I try to shell I get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
ADB State always reports device or unknown never bootloader
ADB remount comes back with remount failed: Invalid argument
ADB push into the / or /system folders (in an attempt to push a copy of sh there) fails saying read only file system
ADB push to /sys comes back with failed to copy: No such file or directory
So, that's where I am.. I think I really really REALLY bricked this thing... although the fact that I can still ADB to it leaves some shimmer of hope.
Thanks,
Joe
can u get into the boot loader at all? If so you are not Bricked you will just need to reinstall the entire system using fast boot. You may be able to restore the default OS using an update.zip file. It may be named something different for your device. All you do with that is place it on the root of the SD card and when the bootloader boots it finds the file and flashes the phone.
I can't get fastboot to recognize the device, it goes right to the ADB bridge. Where I can run some limited ADB commands that are recognized.. If I could get it to start up in fastboot mode, that would likely solve the issue, provided I can get the correct working update.zip file, rather than me trying to fudge one from the clockworkmod backup.
do you have any hardware buttons on device? turning on with volume up or down (or back) gives you differing USB ID's to device manager - obviously you want fastboot mode. (use device manager on ADB Bridge (Details) to get your ID - i think its DEED for fastboot and D00D for fwdn)
otherwise... you can force boot a new bootrom. It's what I did on my telechips device. Find tcboot.rom - put it in the same directory as fwdn
1. Open your device
2. Unsolder your battery + terminal
3. While turning on the device, place a short - screwdriver/pin etc - across pins 7/8 of the NAND chip (for 5 seconds)
4. FWDN should bring up a message about flashing bootrom
5. Reboot (and resolder battery cable)
Note: this obviously is pretty hardcore - but i went from brick, to black screen brick, to full restore via this method.
Hi everyone,
First post (brilliant video!).
My tablet:
Asus Transformer Pad TF300 (rooted)
CWM 5.8.2
My problem:
- We decided to give our Transformer to my gf's dad for his birthday. I tried to backup using a later version of CWM (6 something) but it didn't work. I downgraded to 5.8.2 and it worked fine. I then did a factory reset (which I realise now was not the way to go).
- CMW bootloop : restored my backup, successful - still bootloop.
- Have spent the last 4 hours figuring out ADB and managed to push both a new recovery (rogue) and the latest ASUS firmware to the SDCARD. Despite it confirming the transfer from the cmd line I could not see the zip files in the directories. I tried several times to several different directories. On the last try before the SD card decided to go on vacation I did see one of the files in the root directory.
- Now, no matter what I do, I get a "can't mount /SDCARD" error. Trying to erase/format/factory reset the pad results in errors when trying to access DATA and SDCARD.
- I've located and tried several different scripts from different threads that supposedly create a fake SDCARD directory but nothing has worked
http://forum.xda-developers.com/showthread.php?t=1679274&highlight=encrypted&page=3
- I've also tried to run the install package remotely from ADB but the mounting problem reoccurs
http://www.addictivetips.com/mobile/how-to-install-a-rom-to-an-android-phone-device-without-sd-card/
It appears that many people have encountered similar problems but none of the recommendations have been successful for me so far.
There also seems to be a strange anomaly with the adb shell timing out before I can finish the command. Is this a cable issue?
I'd be super grateful to anyone that can help me sort this out.
Cheers
Sam
Anyone?
I should mention that I had installed Super SU / Super User on the tablet... if that makes any difference.
I woke up this morning and booted the tablet to get this:
E:can't mount /cache/recover/command
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
Error mounting /cache!
In addition to all the previous problems.
Super!
Nobody? Anybody?! Please help!
Hi,
If you have fastboot mode, try to inject twrp (the last 2.2.x.x or something like that) ...
--> read the way to do that on the http://teamw.in/project/twrp2/97
With last TWRP you can mount sd card (first download & extract stock rom .zip and put it on root of your sdcard)
After that, flash stock rom with TWRP ...
Choose fastboot method...be careful (there is 2 versions : JB or ICS)
SOFT BRICK fixable!!! although root repair not yet covered...
I seemed to have a simular problem on my tf300t.
tried to install a CM 9.1.0 (stable)
Stuck at asus cold boot screen.
Solution i found+
*download Fastboot and an adb.shell brigde if you dont already have it.
*place the downloaded systemware (AVALIBLE ON THE ASUS SUPPORT WEBSITE) you wish to install in the same folder you have fastboot. (example-US_epad_10.4.3.13.blob)[432.3MB]
*Boot tablet into CWM [NOTE: I used CWM-Touch. 6.0.3.1 or something along those lines] (TWRP- im unsure if the process is the same).
-from advanced settings at the bottom, wipe dalvik cache.
-no need to wipe your user data cache, but wipe other data cache.
-reboot to bootloader and select fastboot option. (3rd one with pic of usb) DO NOT PLUG IT IN YET.
*Back on your WIN pc open your windows explorer, find the folder containing the Fastboot.exe and hold shift and right click at the same time for an admin operations menu. You should see an option "Open Command Prompt Here". Click it to begin a Fastboot session.
*NOW CONNECT YOUR TABLET!!!
*TYPE THE FOLLOWING AS SHOWN! DO NOT DIVERT OR YOU SCREW UP-
fastboot -i 0x0B05 flash system blob
***NOTE THAT THIS METHOD WILL TAKE QUITE SOME TIME AND YOUR COMPUTER MAY EVEN LOOK LIKE ITS FROZEN...STOP! JUST LET IT DO WHAT YOU ASKED IT TO...THIS IS QUITE A LARGE TASK AND WILL TAKE TIME. MY PC IS AN OLD DELL E300 dem. I KICK THE PROCESS ATLEAST A DOZEN TIMES BEFORE I JUST LEFT IT ALOOOOONNNE and it worked...although i cant seem to figure out how to delete the old su binary i install so i could re-root it....ANYONE GOT ANSWER? PLEASE HELP. EMAIL IS ALWAYS UP.
IF THESE INSTRUCTIONS ARE UNCLEAR, OR YOU DONT UNDERSTAND SOMETHING, MESSAGE ME...
AND IF THIS HELPED YOU...SHARE THE LOVE-GIMME A THANKS!
Ok, so I used this method to root, http://forum.xda-developers.com/show...&postcount=310
I then took a nandroid immediately after rooting. I then installed the latest version of CWM 6.0.1.3 (I used Rom Manager to install it which may have been my mistake).
I was then going to be in the process of installing a custom ROM so I went to wipe data / factory reset, but it just sat there and did nothing. I then tried to boot and I got stuck at the ASUS screen (second screen after the EEPC pad page thingy). It just sits there.
CWM doesn't recognize anything (can't mount SD card so I can't restore whatsoever.. When I try to restore it says:
E:unknown volume for path [/sdcard]
E:Can't mount /sdcard
I'm not quite sure what to do next. I obviously messed up somewhere. I'm guessing ROM manager didn't flash CWM correctly. I'm newer to Android and this is only my second device that I'm attempting to flash... not sure what to do. Please help if you can, if not, guess I'll be buying the new google tablet... shouldn't have done this before my trip to hong kong heh.
-----
EDIT: I can't cold boot either
So I can get into APX mode, I downloaded nvflash and ran the download.bat, but still nothing, it just sits at the eee pad screen and does nothing.
I tried this: http://www.youtube.com/watch?v=VMHXeYMgPy4 (with the TF101), when I run the download.bat, it just disconnects the device and nothing happens.
When I run that bat file manually I get this error message.
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
patmann03 said:
I tried this: http://www.youtube.com/watch?v=VMHXeYMgPy4 (with the TF101), when I run the download.bat, it just disconnects the device and nothing happens.
When I run that bat file manually I get this error message.
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Click to expand...
Click to collapse
I'm guessing this means my version is too new for AXP recovery... darn that's no good. I can't tell what version my transformer is, the sticker on the back is too hard to read (maybe because it's really late), and all of the other stickers I pealed off today... heh.
I tried getting adb to work, but I'm not quite sure how. I believe I have the drivers installed, but I have a feeling I messed up the SD card on my device so much that even adb can't recocgnize it.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ I followed this guide..
Ok, I can get into adb mode and can push items to my device, anyway to restore this way?
Ok, flashed a new recovery. I'm able to access my sd card (external). I found my restore, however, when I went to restore my backup it restored the system, but got an error formatting data...
Used this tool to install new recovery. http://www.androidauthority.com/tra...-3-root-custom-recovery-one-click-tool-97173/
trying to use the same too to unroot...
Get this..
Run? Close if you want to cancel.
Press any key to continue . . .
List of devices attached
3889240415f5497 recovery
If you see your device here this will work, if not fix adb.
Press any key to continue . . .
running fix...
dd: writing '/dev/block/mmcblk0p3': No space left on device
4097+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.512550 seconds, 3.9MB/s
rebooting tab, if at any step it doesn't reboot turn off and turn back on
Once back into an adb possible state continue...
Press any key to continue . . .
Pushing new recovery...
1328 KB/s (4599884 bytes in 3.380s)
Running wolf's exploit...
mv: can't rename '/data/local/tmp': No such file or directory
Going...
ln: /data/local/tmp: No such file or directory
Done!
Now lets reboot your TF again...
Continue when back into ADB again...
Press any key to continue . . .
Ok, this saved my ass. http://forum.xda-developers.com/showthread.php?t=1688012
I got the device which is really nice, I rooted the first night, I then updated to version 1.1, lost root as usual but luckily my copy of CWM works fine for both versions 1.0 and 1.1.
If you are familiar doing this with android phones, just follow the same steps.
Use at own Risk
Download both files. Make sure they are complete and the file sizes match.
Save recovery.img to computer, and su.zip to VSD220,
Gain access to adb for your device,
go to terminal or command prompt and type "adb reboot bootloader",
and then enter.
The screen will turn solid black,
in the same terminal type "Fastboot flash recovery recovery.img",
and enter, make sure you are in the same directory as your recovery.img.
The recovery will flash quickly, when complete type "fastboot reboot", enter.
Your device will boot up,
make sure you have Su.zip saved on the VSD220 in the directory /mnt/external_sd/su.zip,
you must have an external sd card inserted,
you can confirm this with root explorer even without root.
In terminal type adb reboot recovery,
you should have a working CWM that will allow you to flash su.zip, and perform a nandroid backup, etc.
If CWM offers to block the stock recovery, accept it.
Otherwise you will need to delete or rename /install-recovery.sh and/or /system/recovery-from-boot.p.
Enjoy Root.
This works for both version 1.0 and 1.1.
Cool, thanks!
Can't seem to get "adb devices" to come up with anything. Using Android Composite ADB Interface for driver, no luck at all.
Any help on which ADB driver to use and where to download appreciated.
sk8tingusmc said:
I got the device which is really nice, I rooted the first night, I then updated to version 1.1, lost root as usual but luckily my copy of CWM works fine for both versions 1.0 and 1.1.
If you are familiar doing this with android phones, just follow the same steps.
Use at own Risk
Download both files. Make sure they are complete and the file sizes match.
Save recovery.img to computer, and su.zip to VSD220,
Gain access to adb for your device,
go to terminal or command prompt and type "adb reboot bootloader",
and then enter.
The screen will turn solid black,
in the same terminal type "Fastboot flash recovery recovery.img",
and enter, make sure you are in the same directory as your recovery.img.
The recovery will flash quickly, when complete type "fastboot reboot", enter.
Your device will boot up,
make sure you have Su.zip saved on the VSD220 in the directory /mnt/external_sd/su.zip,
you must have an external sd card inserted,
you can confirm this with root explorer even without root.
In terminal type adb reboot recovery,
you should have a working CWM that will allow you to flash su.zip, and perform a nandroid backup, etc.
If CWM offers to block the stock recovery, accept it.
Otherwise you will need to delete or rename /install-recovery.sh and/or /system/recovery-from-boot.p.
Enjoy Root.
This works for both version 1.0 and 1.1.
Click to expand...
Click to collapse
admisi said:
Can't seem to get "adb devices" to come up with anything. Using Android Composite ADB Interface for driver, no luck at all.
Any help on which ADB driver to use and where to download appreciated.
Click to expand...
Click to collapse
Sorry, was using outdated adb.
So got adb, flashed recovery.img, recovery flashed ok, rebooted...but now when I adb reboot recovery, it reboots and then stuck on green android with red triangle.
Any advice?
admisi said:
Sorry, was using outdated adb.
So got adb, flashed recovery.img, recovery flashed ok, rebooted...but now when I adb reboot recovery, it reboots and then stuck on green android with red triangle.
Any advice?
Click to expand...
Click to collapse
Ok, I worked it out now. But for others, the problem was that recovery image was being replaced with the original on the command "fasboot reboot".
So instead, immediately after typing "Fastboot flash recovery recovery.img" I typed the following command "fastboot boot recovery.img".....AND only then did I get CWM which allowed me to flash su.zip from SD card.
Thanks for all help. Now that I have root, what changes/tweaks did you make using root?
Is there an optimum dpi to apply and are you overclocking?
Thanks.
Here is a script to reboot recovery mode; from your Android VSD220.
sk8tingusmc said:
I got the device which is really nice, I rooted the first night, I then updated to version 1.1, lost root as usual but luckily my copy of CWM works fine for both versions 1.0 and 1.1.
If you are familiar doing this with android phones, just follow the same steps.
Use at own Risk
Download both files. Make sure they are complete and the file sizes match.
Save recovery.img to computer, and su.zip to VSD220,
Gain access to adb for your device,
go to terminal or command prompt and type "adb reboot bootloader",
and then enter.
The screen will turn solid black,
in the same terminal type "Fastboot flash recovery recovery.img",
and enter, make sure you are in the same directory as your recovery.img.
The recovery will flash quickly, when complete type "fastboot reboot", enter.
Your device will boot up,
make sure you have Su.zip saved on the VSD220 in the directory /mnt/external_sd/su.zip,
you must have an external sd card inserted,
you can confirm this with root explorer even without root.
In terminal type adb reboot recovery,
you should have a working CWM that will allow you to flash su.zip, and perform a nandroid backup, etc.
If CWM offers to block the stock recovery, accept it.
Otherwise you will need to delete or rename /install-recovery.sh and/or /system/recovery-from-boot.p.
Enjoy Root.
This works for both version 1.0 and 1.1.
Click to expand...
Click to collapse
Here is a script to reboot recovery mode; from your Android VSD220.
********* script starts here
#!/system/bin/sh
su
echo -n recovery | busybox dd of= /dev/block/emmc count=1 conv=sync; sync; reboot recovery
********* script ends here
I used Scripter Ver. 1.8 It work find. Don't forget to flash the right recovery.img and install su.zip. If you don't the script won't work.
has anyone gotten this to work lately? The device I'm playing with has 1.3 firmware on it. For some reason, I haven't gotten adb to work on this device in windows, and in ubuntu, I can adb reboot bootloader, and it goes to the black screen, but any fastboot commands, just sits there waiting for device. Any suggestions would be appreciated.
n1gh7m4r3 said:
has anyone gotten this to work lately? The device I'm playing with has 1.3 firmware on it. For some reason, I haven't gotten adb to work on this device in windows, and in ubuntu, I can adb reboot bootloader, and it goes to the black screen, but any fastboot commands, just sits there waiting for device. Any suggestions would be appreciated.
Click to expand...
Click to collapse
I didn't know 1.3 was available. Is this a recent firmware? I checked a couple weeks ago.
Not sure, it's not my monitor, just looking at it for a friend. when I go to about, system update I see vsd220 system update 1.3 device system version : IMM76D.UI23ED02_VSC and same info under server version
Got it sorted out after hunting on google. it does work
problem with adb
Ok so i got the device being recognized on my XP machine. Really did not have to do much. Just pluged it in and everything worked.
On my Windows 7 machine when i plug in the device i only see the MTP installed and then see VSD220 in MY COMPUTER and can browse the files. I do not see it when i "adb devices".
1) USB debugging is on/enabled
2) Both laptops have Eclipse with latest ADB and ADT tools installed
Any suggestions as to what i can do? Anyone can copy over drivers that are working with your win7 machine?
Confirmed Working for Acer DA220HQL (atleast for me)
Thanks to sk8tingusmc for posting the instructions. I followed them as well as the comments below and rewrote the instructions to reflect what worked for me on my Acer DA220HQL Smart Display. Which seems to be about the same device as the Viewsonic VSD220
Use at your own Risk - Acer DA220HQL
1. Download both files from the first Post (Thanks to sk8tingusmc).
Make sure they are complete and the file sizes match.2. Save "recovery.img" to your computer, and copy su.zip to the Acer DA220HQL to "/mnt/external_sd/su.zip"
3. Press Windows Key + R to open the Command Prompt or Start > Run > cmd > Enter
4. At the Command Prompt change to the Directory with adb.exe in my case "C:\Temp\sdk\platform-tools"
Download SDK from here: http://developer.android.com/sdk/index.html#download and extract in my case to C:\Temp (C:\Temp\sdk, C:\Temp\eclipse, and C:\Temp\SDK Manager.exe)5. At the Command Prompt type "adb reboot bootloader" and hit enter.
The screen will turn solid black6. At the Command Prompt Type "Fastboot flash recovery recovery.img" and hit enter.
Make sure you are in the same directory as your recovery.img.
The recovery will flash quickly
C:\Temp\sdk\platform-tools>Fastboot flash recovery recovery.img
sending 'recovery' (5688 KB)...
OKAY [ 0.176s]
writing 'recovery'...
OKAY [ 0.983s]
finished. total time: 1.163s
7. At the Command Prompt Type "fastboot boot recovery.img" and hit enter.
C:\Temp\sdk\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.173s]
booting...
OKAY [ 0.001s]
finished. total time: 0.178s
Your device will boot up8. At the Command Prompt Type "adb reboot recovery"
It will enter ClockworkMod Recovery v6.0.2.8 with Touch Support. 9. Choose ZIP File from SDCard navigate to su.zip and select it by pressing on it.
Scroll all the way down to find ++++Go Back++++ on the SDCard if you entered the wrong Directory.
You may also choose to create a Nandroid Backup if you care to do so.10. Go Back and select Reboot
11. ROM may Flash stock recovery on boot. Fix? - Yes - Disable recovery Flash
Otherwise you will need to delete or rename /install-recovery.sh and/or /system/recovery-from-boot.p.
12. View attachment 2062751
Rom Version and work in Linux?
swiss420 said:
Thanks to sk8tingusmc for posting the instructions. I followed them as well as the comments below and rewrote the instructions to reflect what worked for me on my Acer DA220HQL Smart Display. Which seems to be about the same device as the Viewsonic VSD220
Click to expand...
Click to collapse
I was wondering what ROM Version is your DA220HQL on (ES I think?) and will the instructions work in Linux or other *nix like systems?
The main problem I have is that I do not have any drivers so adb in Windows XP will recognize it. It is recognized under Ubuntu 12.04 for me.
Thanks for the info! I am very excited to get this working better than out of the box!
LoveMyAndroid2010 said:
I was wondering what ROM Version is your DA220HQL on (ES I think?) and will the instructions work in Linux or other *nix like systems?
The main problem I have is that I do not have any drivers so adb in Windows XP will recognize it. It is recognized under Ubuntu 12.04 for me.
Thanks for the info! I am very excited to get this working better than out of the box!
Click to expand...
Click to collapse
There are a universal ADB Drivers for Windows.
Universal Naked Driver for example.
http://forum.xda-developers.com/showthread.php?t=1161769
Or the following link which I have no clue about who maintains this site and how secure it is running that Exe. So please check first for yourself before yelling at me. http://adbdriver.com/
Regarding the ROM Version I was on, check the other Thread where I listed them all.
swiss420 said:
There are a universal ADB Drivers for Windows.
Universal Naked Driver for example.
http://forum.xda-developers.com/showthread.php?t=1161769
Or the following link which I have no clue about who maintains this site and how secure it is running that Exe. So please check first for yourself before yelling at me. http://adbdriver.com/
Regarding the ROM Version I was on, check the other Thread where I listed them all.
Click to expand...
Click to collapse
Well I got the ADB driver installed and I can use it! However I tried the root procedure and it failed to root.
When I was in the CW, the one thing it kept giving an error such as cannot mount sdcard. I checked the sdcard and su.zip IS on it, but the recovery could not locate it. I did try using the sideload method and it seemed to work, but when I rebooted and checked for root, it was not successful.
I tried this in both Ubuntu and Windows with the same result. I even performed a factory reset and tried again. And the same thing: no root.
Is there a timing issue with when to enter the commands?
The info on my DA220HQL from about is as follows:
Model number
DA220HQL
Android version
4.0.4
Kernel version
3.0.21-00003-OMAP-Android+
[email protected] #1
SMP PREEMPT Mon May 13 10:06:22 CST 2013
Scaler version
BA0.2A en_PA
Touch driver version
1.1.0509.1
Build number
IMM76D.UI23ED22_ACE
Thanks for the help!
LoveMyAndroid2010 said:
Well I got the ADB driver installed and I can use it! However I tried the root procedure and it failed to root.
When I was in the CW, the one thing it kept giving an error such as cannot mount sdcard. I checked the sdcard and su.zip IS on it, but the recovery could not locate it. I did try using the sideload method and it seemed to work, but when I rebooted and checked for root, it was not successful.
I tried this in both Ubuntu and Windows with the same result. I even performed a factory reset and tried again. And the same thing: no root.
Is there a timing issue with when to enter the commands?
The info on my DA220HQL from about is as follows:
Model number
DA220HQL
Android version
4.0.4
Kernel version
3.0.21-00003-OMAP-Android+
[email protected] #1
SMP PREEMPT Mon May 13 10:06:22 CST 2013
Scaler version
BA0.2A en_PA
Touch driver version
1.1.0509.1
Build number
IMM76D.UI23ED22_ACEThanks for the help!
Click to expand...
Click to collapse
So you were able to load CW but when you select "Choose from SDCard" it could not find su.zip? Or did you try to Mount your SDCard? Regarding the ADB Commands you can take as much time as you want. Have you used CW before?
swiss420 said:
So you were able to load CW but when you select "Choose from SDCard" it could not find su.zip? Or did you try to Mount your SDCard? Regarding the ADB Commands you can take as much time as you want. Have you used CW before?
Click to expand...
Click to collapse
I did try to mount the sdcard, but I got an error that said it could not mount the sdcard. That is when I tried the sideload method. When I boot up normally, the sdcard is there along with su.zip. I posted the info on my DA220HQL noting the kernel version. I went back to the post where you stated your kernel version. They are different. Mine is later than yours.
After going through everything several times, I though maybe I was doing something wrong. We went out of town so this is the first time I could sit down and check out the posts.
Thanks for your help in advance.
Thanks for all the help. I could not get this to root so we are sending it back to HSN. As a last ditch effort, I did a factory reset and tried again. And I got the same result. I do not think that the recovery while booted was able to "see" the device's partition at all, which is why I got the mount errors. In any case, I also have found that we can find it online for much less than what HSN charged us for it. I am still curious if anyone else was able to root this little gem.
Keep posting updates!
im getting the same issue
cwm is not mounting my sdcard
android is recognizing it, but not in recovery
I'm thinking I shouldn't have installed that update
there are a bunch of errors in recovery when starting
E:Can't open /dev/block/platform/omap/omap_hsmmc.1/by-name/misc (No such file or directory)
E:Can't mount /cache/recovery/command
E:Can't open /dev/block/platform/omap/omap_hsmmc.1/by-name/misc (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't open /dev/block/platform/omap/omap_hsmmc.1/by-name/misc (No such file or directory)
my best guess is we need a different recovery img, even though acer is the same as viewsonic
also there is no prompt to disable stock recovery being reinstalled
recovery touch is also kind of wack, have to tap below whatever I want to pick (which is also not consistent horizontally)
edit: going back to recovery, under mounts and storage, it doesn't appear to have permission to mount anything
looks like viewsonic released a rooted ROM on their support site
http://www.viewsoniceurope.com/uk/support/downloads/drivers/?prod_name=vsd220
But yeah...Acer hasnt
Perhaps this should get the ball rolling? It's funny how the US site doesn't have that
edit: wow looks like they even provided flashing tools and instructions...I just hope that this doesn't brick my unit (since its Acer not Viewsonic)...anyone else willing to give it a try?
I have a J7 prime, on7xelte, g610f, oreo 8.1.0, stock firmware, no custom recovery. I wanted to root it and for that wanted to install twrp. I did NOT use Samsung Antiroot Removal Tool, RMM State Bypass zip, No Verify Encrypt zip. I tried to flash it using adb but no matter what it wont detect my phone in recovery/fastboot, only when its on or sideload. On sideload i got an error. So i tried to do it with odin, since odin detects my phone EVEN though windows doesnt. After doing that somehow my system got corrupted. i couldnt mount /data once in twrp and trying to boot it up caused bootloop. i couldnt get it to mount usb either. then i force restarted it into download mode and reinstalled stock firmware, retried the twrp .tar, and failed again. and again. then i saw a video rooting j7 prime with a root file The link to the video:
. the file was for g610fd, i thought the "d" was a typo and flashed it anyway. Now I boot up into the stock recovery with the exact following lines:
Installing system update (loading)
no command (exclamation triangle)
(after a while)
Android recovery
samsung/on7xeltedd/on7xelte
8.10/MIAJQ/G610FDDS1CTE3
user/release-keys
[the regular options here]
#fail to open recovery_cause(no such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
File based OTA
supported API: 3
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
#MANUAL MODE V1.0.0#
Successfully verified dmverity hash tree
:/ so apparently at this point, only the volume buttons work. i mean i can only go up and down but not select a thing. its bad. so i tried force rebooting into the download mode. THERE, the VOLUME buttons dont work. means i cant confirm and proceed into the download mode fully. my pc doesnt recognize the device in either states so i cant command in adb. one thing is that even before this error my pc didnt notice my phone in either states. so i might be missing the right drivers. my wire isnt flawed, i have 3 wires. i have hand typed everything here so will be great if you take your precious time to type any advice here for this poor fellow who is scared of losing his only phone.