I apologize in advance for posting this kind of thread for the 100th time (as I've read similar ones around). I still couldn't find one that may have a solution. I'm not an Android user, so this is all new to me. I got this Sony Tablet S stuck on a bootloop. I can't do anything but enter the hard reset/recovery screen I think it's called... ? I figured maybe re-installing its firmware from the SD Card would do, but I don't know which one it had before (it's a friends tablet that I'm attempting to fix). I think it may be one called Ice Cream Sandwich since I read it on some other thread. Where can I find it and how can I do this? Is there a go-to for-dummies kind of guide? haha. Sorry. I'm really lost when it comes to rom talk and whatnot, so be gentle, lol.
Thank you for reading. Don't mean to waste anyone's time.
Attached a picture, just in case.
Don't judge me for this being my first post. I probably created this account, left it laying around and never came back. I just tried it cause it's my usually my username and it was taken. Found out it really was mine. :/
Click to expand...
Click to collapse
lindapr said:
I apologize in advance for posting this kind of thread for the 100th time (as I've read similar ones around). I still couldn't find one that may have a solution. I'm not an Android user, so this is all new to me. I got this Sony Tablet S stuck on a bootloop. I can't do anything but enter the hard reset/recovery screen I think it's called... ? I figured maybe re-installing its firmware from the SD Card would do, but I don't know which one it had before (it's a friends tablet that I'm attempting to fix). I think it may be one called Ice Cream Sandwich since I read it on some other thread. Where can I find it and how can I do this? Is there a go-to for-dummies kind of guide? haha. Sorry. I'm really lost when it comes to rom talk and whatnot, so be gentle, lol.
Thank you for reading. Don't mean to waste anyone's time.
Attached a picture, just in case.
Click to expand...
Click to collapse
My signature faq thread and its links
Sent from my HTC One using xda app-developers app
stifilz said:
My signature faq thread and its links
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
When I try to install from SD Card, it says "E:failed to mount /sdcard (no such file or directory)"
It's the only thing on your FAQ that I tried, since it's the "brick" thing that I think is where I'm at.
Also, (don't know if this would help) tried using the ADB Driver Installer but the drivers are not installing either... I went to the device manager and tried to do it manually, didn't work either. Android Composite ADB Interface "The hash file for the file is not present for the specified catalog file. The file is likely corrupt or the victim of tampering".
Unfortunetly i have the same issue! :/ and now i dont know to do..
Generaly my tablet s stuck's on bootloop (sony logo)
I can enter recovery mode (with some errors.. cant find, cant mount etc.)
When im picking flash from SDCard tablet says E:/ cant mount /sdcard
and then shows empty card :/
PLS help!
lindapr said:
When I try to install from SD Card, it says "E:failed to mount /sdcard (no such file or directory)"
It's the only thing on your FAQ that I tried, since it's the "brick" thing that I think is where I'm at.
Also, (don't know if this would help) tried using the ADB Driver Installer but the drivers are not installing either... I went to the device manager and tried to do it manually, didn't work either. Android Composite ADB Interface "The hash file for the file is not present for the specified catalog file. The file is likely corrupt or the victim of tampering".
Click to expand...
Click to collapse
The sd card must be fat32 for the device to see it
Use blue chips auto installer for adb
xperia m c1905 stock rooted lb
and sony XTS rooted stock j.b thanks djrbliss
dex9mm said:
The sd card must be fat32 for the device to see it
Use blue chips auto installer for adb
xperia m c1905 stock rooted lb
and sony XTS rooted stock j.b thanks djrbliss
Click to expand...
Click to collapse
SD CARD is formated in FAT32 but still no luck:
E:fail to read boot logo flag
E: can'T OPEN /DEV/block/mmblk0p5
(no such file or directory)
E: failed to mount /cache
E: cant mount /cache/recovery/command
E: failed to mount /cache
E: failed to mount /cache
E: failed to mount /sdcard
its in Android system recovery REV 29 (3e)
Ok. I have installed ADB drivers and now i can see device but adb shell its not working - no sh
generaly its seams that kernel and recovery partition stay on this tablet :/
Anyone know how to recover?
Related
I'm looking for some help, I've been searching and there's just so much information out there, I can't seem to make much headway.
My tab is boot looping. I monekeyed around with the /system directory and mucked thigns up. doh!
I would like to reflash with this rom here - http://forum.xda-developers.com/showthread.php?t=1162302.
The problem is, I can't figure out how to get the rom on my sdcard. Since the sdcard it's not removable, how do I get it on there? Usb debugging is turned off so I can't use adb to move it over since I can't actually start the tablet to set it usb debugging on.
So, I'm not sure what to do. I can get into fastboot mode and launch CWM, but not much it seems I can do without actually having the update.zip on my sdcard. Can I use fastboot to flash a stock image? If so, I can't find any .img file to be flashed.
Arrrghh... If anybody can point me in the right direction, that would be awesome.
Launch CWM, and mount USB storage from there. Use that to move the rom zip over, and then flash.
It says it can't mount it for some reason....
keeps saying
ClockworkMod Recovery v3.1.0.1
E:Unable to open ums lunfile (no such file or directory)
thanks... I actually just got it back to working. I will post a follow up later to explain all that I did and all that I learned from this experience. I think it will be of great help to others. It's actually quite simple once you Bundestag how things work. Of course only after I asked a question did I finally "get" it.
More to come.
did you figure this out? im in the same boat as you. HElp please!
Hello all.
I'm not from this section of the forum, I'm trolling around. Go to Samfirmware.com Your answer is there.
Sent from my GT-I9100 using xda premium
Hello everyone. Let's see if anybody can help me, because I'm pretty stuck with this.
Note: I've already searched high and low for solutions to the "Signature verification failed", but they either don't work or don't apply here.
I've tried to install the following ROM from xda-developers in a Sanei N10:
Unofficial CyanogenMod 10 for many AllWinner A10 tablets
I've installed it following the usual procedure:
- Press Vol+ and Power to get the Recovery menu
- Select Wipe data/factory reset
- Select Wipe cache
- Install the three ZIP files: "cm10_a10_20120913.zip", "gapps-jb-20120726-signed.zip" & "n10_compatibility_1.2.1.zip"
The problem is, even though the first ZIP with the ROM installs successfully, the second one (the one with Google's apps) refuses to install, showing instead the message "signature verification failed". The same happens with the third ZIP (N10 compatibility).
So the installation doesn't actually finish. If I reboot the tablet, it runs Cyanogenmod 10, but the touchscreen doesn't work (I have to plug a USB mouse to interact with the operating system).
So what do I do to avoid the dreaded "signature verification failed" message? Just in case if it's of any help to identify the problem, I'll mention that I can see the Android bot laying down with a red triangle with an exclamation when entering the Recovery menu.
I've tried to use the ROM Manager which is preinstalled with Cyanogenmod 10, but when choosing "Flash ClockworkMod Recovery" it says that "The SD Card needs to be mounted to use ROM Manager". Of course my MicroSD is properly mounted (I can see its files in the card from console, from the "Terminal Emulator"). I think this happens because the MicroSD is mounted in /storage/sdcard1 instead of in /storage/sdcard0, but I can't change that. I can't download APKs from the browser, either, because it also says something similar about not being able to access the SD (even though it's correctly mounted and can see it mounted from Settings > Storage).
I've also tried the CyanogenMod A10 ROM available in this page, which is more recent (October instead of September):
http://www.slatedroid.com/topic/3870...mod-10-tweaks/
But the same happens.
I've even tried installing the CWM Recovery ROM, but it doesn't let me installing that from the Recovery either (same message about the "signature"), and with Odin3 it doesn't work either because I don't know how to reach the "download mode", which is needed for Odin3. Pressing Vol+ and Power I get the Recovery, but not the Download mode. Does anyone know how do I get to the download mode in the Sanei N10?
Any idea about how to solve this? Right now I have a tablet with no touchscreen and not even Google applications (so I don't even have the Play Store), so it's practically worthless (at least the WiFi works). How can I get this tablet back to being usable?
Did you fix this? I want to get this tablet and most likely want to root and rom it but if this is the case...
benny6812 said:
Did you fix this? I want to get this tablet and most likely want to root and rom it but if this is the case...
Click to expand...
Click to collapse
No, unfortunately I still couldn't fix it
There's nobody here in xda-developers who can help me? Surely somebody must know enough to help me find a solution.
I've tried creating a symbolic link from /storage/sdcard1 to /storage/sdcard (it doesn't exist right now), but it just says "link failed Read-only file system" (I was root, by typing "su" and clicking "Allow" in the Superuser window). So, I can't create symbolic links even while being root user? I need this link so ROM Manager can detect my SD Card (it says it's not mounted but it really is, but in "/storage/sdcard1").
Also, the gapps package linked in the ROM page above seems not to be properly signed, even though it has that "-signed" suffix in its name. I always get that "signature verification failed" error message. But now I've tried downloading a more recent gapps package (gapps-jb-20121011-signed.zip) and that package finally worked! BUT, even though it apparently installed successfully, I still can't see any Play Store icon, nor any other Google app (Gmail, etc.). Why? Those icons should appear after installing gapps, shouldn't they? Maybe this newer "gapps" package is somehow incompatible with this tablet? (is this even possible?).
Also, even though I can now install the newer "gapps" package, I still can't install the "n10_compatibility_1.2.1.zip" file (I still get "signature verification failed" for that ZIP), which, I guess, contains the drivers needed for the N10 so the touchscreen works (currently it doesn't, and I have to use a USB mouse to use Android in this tablet). Any ideas? I'm getting tired of trying 9485738489754935627 things with no good result . I guess Android is showing here its Linux roots...
I think the key here is managing to install a new Recovery ROM that doesn't care about signing, but how do I do that? I can't install through ROM Manager because I get that error about the SDCard needing to be mounted to use it (and it's really mounted), and then I can't create the /storage/sdcard symbolic link because I get that "link failed Read-only file system" error. Also, I can't use Odin3 because I can't manage to put this tablet in Download Mode. Aaaargh! There's no good solution
Any ideas?
Bump!
I have same problem, i think that we need a different compatibility file, or perhaps if we could open install any app like Novo7 we could fix it... hope that anyone have the solution.
Yojimbojpr said:
I have same problem, i think that we need a different compatibility file, or perhaps if we could open install any app like Novo7 we could fix it... hope that anyone have the solution.
Click to expand...
Click to collapse
Thanks for replying. If we could find some way to install a new Recovery, then we'd probably by able to get the N10 Compatibility file working. This can't be that hard to do, but I've tried lots of things, and none of them worked...
Anyone?
Please, someone help!
Bump!
No ideas?
Please, I'm getting desperate
sanei
OMA2k said:
No ideas?
Click to expand...
Click to collapse
same problem here....
jamjamjan said:
same problem here....
Click to expand...
Click to collapse
Please let me know if you find a solution to this. Thanks!
I'm having the same issue with [ROM][CM10/10.1][21 Dec] Codename Lungo
Well, at last I could finally solve the problem thanks to chris5s from this forum.
These are the steps that worked for me:
1. Download the latest ClockWorkMod for Allwinner A10 tablets from here:
http://forum.xda-developers.com/showthread.php?t=1802268
2. Put all three files in the ZIP inside the root of a MicroSD card and insert it in the tablet
3. Check from the Terminal app inside the tablet to see if the MicroSD card is mounted in /sdcard (just type "ls /sdcard").
4. If the "ls" command doesn't show anything (that's what happened in my case), then you must modify the "install-recovery.sh" file and replace all instances of "/sdcard" with "/mnt/extsd".
5. With the proper "install-recovery.sh" file, run the commands specified in the above xda link (in my case the card is in "/mnt/extsd" instead of "/mnt/sdcard" as the original example shows):
su
cd /mnt/extsd
sh install-recovery.sh
sh reboot-recovery.sh
6. The tablet will then reboot to CWM recovery. Then follow the regular steps to install Cyanogenmod (wipe plus install ROM + GApps + Compatibility). This time the Recovery menu won't care about the files being unsigned and will install them right away!
I hope this helps somebody else!
hey i just registered because i have been having the same exact problem i read that you fixed it but how can i get in to the tablet if im not able to do any movements after it boots ???
please any help would be appreciated
Download the file again, and try again
Sent from my GT-N7000 using xda app-developers app
Thatgrass said:
Download the file again, and try again
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
i did i just dont know how to get in to the terminal app
ok so im in the terminal app but what do you mean by modify the install sh file ???
Hello "lesanei"
I just noticed your posts. Let's see if I can help you...
The touchscreen doesn't work because the appropriate drivers were not installed (because of the "signature verification failed" issue). So you need to connect a USB mouse (and preferably a keyboard too) to the tablet. The Sanei N10 should come with a USB to micro-USB adapter. If you don't have it, you can buy it for cheap here.
Since there is only the one USB input in the tablet, you can't connect two USB devices at the same time. What I did use is a wireless mouse+keyboard combo which only needed one USB dongle for reception. If you don't have that, you can just connect a USB mouse and type with the on-screen-keyboard using the mouse. It's annoying, but it works
When I say "modify the install-recovery.sh file", I mean the file inside "cwm_recovery_6.0.1.2_a10.zip". You can modify it from your PC if you prefer. You don't have to do it in the tablet if you don't know how to use the "vi" editor (command line editor). Just open the "install-recovery.sh" file in Wordpad (do not use the Notepad, because it doesn't support Unix line endings so it shows the file incorrectly) and replace all instances of "/sdcard" with "/mnt/extsd". So the file contents should look like this:
#!/system/bin/sh
if busybox test ! -f /mnt/extsd/recovery.img; then
echo no /mnt/extsd/recovery.img
exit 1
fi
cat /mnt/extsd/recovery.img > /dev/block/nandg
sync; sync; sync
echo done
Click to expand...
Click to collapse
Then place all three files ("recovery.img", "install-recovery.sh" and "reboot-recovery.sh") into your MicroSD card. Then safely extract it from your PC, insert it in the tablet and type this from the Terminal:
su
cd /mnt/extsd
sh install-recovery.sh
sh reboot-recovery.sh
Click to expand...
Click to collapse
Then follow the regular steps to install Cyanogenmod and this time all files should install sucessfully, so when rebooting, touchscreen and everything else will work.
Let me know if it works for you.
Hello,
My Tablet S is in deep need of expert help to see the light of day...:crying:
History:
I've rooted it about one day after the working exploit was found, ran Condi's AiO tool to update, and everything went fine.
At once, I used the "reinstall to factory settings" in the Settings app, which gave me a happy - if somewhat unstable at times - tablet.
It suddenly stopped working and remained stucked at the Sony logo.
Having no other option, I restarted in Recovery (Power-Volume+), and tried to update the system from SD card :
- with latest Condi's R5a zip : signature error
- with stock encrypted Sony zip : update blocked (yes, I left the tablet running about 8 hours without a move from the progress bar)
In the Android Recovery, I then selected "Reset to factory settings". Which seemed to do its thing, except that...the tablet still was stucked at the Sony logo at boot.
Going to Recovery again...
Code:
E:Fail to read boot logo flad
E:Can't open /dev/block/mmcblk0p5
(No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
E:failed to mount /cache (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /cache (No such file or directory)
I can see the following device with ADB :
Code:
./adb devices
List of devices attached
0123456789ABCDEF recovery
and that's about all I can do with the tablet now.
Code:
./adb shell "ls /"
- exec '/system/bin/sh' failed: No such file or directory (2) -
One word remains: PLEASE HELP !
Is there any way I can dump a working system on the tablet in this state?
Note: I'm not afraid of running anything arcane command/script/setup.
Strange because the shell binary cannot be found but it can be wiped.
It is possible that the System partition is gone.
Sent from my Sony Tablet S using xda premium
andyabc said:
It is possible that the System partition is gone.
Click to expand...
Click to collapse
Yes indeed, I'm pretty sure that the Recovery option "Restore to factory settings" did wipe partitions...and failed to write anything sensible to them afterwards, or to recreate them at all (if that makes sense : I am far from sure of what the whole process really does and whether this is an Android standard or Sony-proprietary).
So, I'm there with my half-baked tablet ... any kind soul with the know-how how to revive it?
sorry to be the bearer of bad news, but I have had the expect same thing happened to my tablet s, all of sudden it stopped working, stuck on sony logo during booting, can't mount sd card in recovery mode, etc etc. Chances are your mother board is damaged. Might be a good time to send it to sony for repair. Good luck
since you have root,look here
how to use adb shell in recovery mode
http://forum.xda-developers.com/showthread.php?t=2081196
once you get shell,check you mmc device,and it's partitions
http://forum.xda-developers.com/showthread.php?t=2102704
any way,send your tablet to sony is a good chiose.
Palijn said:
Yes indeed, I'm pretty sure that the Recovery option "Restore to factory settings" did wipe partitions...and failed to write anything sensible to them afterwards, or to recreate them at all (if that makes sense : I am far from sure of what the whole process really does and whether this is an Android standard or Sony-proprietary).
So, I'm there with my half-baked tablet ... any kind soul with the know-how how to revive it?
Click to expand...
Click to collapse
Data partition is still there though.
The recovery has its own shell for sure since you are rooted.
The recovery has its own binary and adb support.
Here is the boot order:
Bootloader>Kernel>Boot Animation>System
When the Sony logo flashes thats when it switches to the Kernel but since it did not do anything it is possible that there is missing files in the data partition.
Bootloader = On a component on the motherboard somewhere
Kernel = Data Partition
Boot Animation = System Partition
System = System Partition (Obviously)
Sent from my Sony Tablet S using xda premium
maybe kernel is not on data patition.
kermel is in rootfs.which is split with inner mmc dev(or in a hidden partition)
robin said:
maybe kernel is not on data patition.
kermel is in rootfs.which is split with inner mmc dev(or in a hidden partition)
Click to expand...
Click to collapse
Yeah true but the question is did the Sony logo flash for a moment, if it did then it switched to the kernel successfully.
I cannot view your username in the quote above due to it using part of the tags used in programming languages.
Sent from my Sony Tablet S using xda premium
andyabc said:
Yeah true but the question is did the Sony logo flash for a moment, if it did then it switched to the kernel successfully.
Click to expand...
Click to collapse
Yes indeed, the Sony logo flashes (and that's a fairly nice indication for the right time to press Power again and enter Recovery afterwards!).
Anyway, the tablet froze from time to time just entering Recovery (screen with the green/white dots), then I was able once or twice to start restoring a system image from the original Sony encrypted-signed ZIP so gracefully provided by condi in his Google Drive , but the process froze at different places!
I guess there is definitely a hardware issue (such as a faulty memory chip, if not a grilled processor), so right away it went to repair.
If it comes ever back as "repairable and repaired" I'll inform here!
Thanks to all for the attempts at helping!:highfive:
Palijn said:
Yes indeed, the Sony logo flashes (and that's a fairly nice indication for the right time to press Power again and enter Recovery afterwards!).
Anyway, the tablet froze from time to time just entering Recovery (screen with the green/white dots), then I was able once or twice to start restoring a system image from the original Sony encrypted-signed ZIP so gracefully provided by condi in his Google Drive , but the process froze at different places!
I guess there is definitely a hardware issue (such as a faulty memory chip, if not a grilled processor), so right away it went to repair.
If it comes ever back as "repairable and repaired" I'll inform here!
Thanks to all for the attempts at helping!:highfive:
Click to expand...
Click to collapse
Every chip and processor has its own firmware so maybe somehow it became corrupted.
Sent from my Sony Tablet S using xda premium
I purchased a NT from a guy on Craigslist who said it was bricked. Since I have installed CM10 on a number of NC and NT I thought I would take a chance and buy it. When you turn it on, after the N is displayed, it momenteriarly displays what looks like the opening the Reading Forever page. Then is goes to a Red exclamation point that says to restart your device and try again.
I have tried booting from a CWM boot disk. It says it can't find E: when I try a data/factory reset, I suspect the partitions are meesed up. What is my best course of action at this point?
Bonnie_Raitt said:
I purchased a NT from a guy on Craigslist who said it was bricked. Since I have installed CM10 on a number of NC and NT I thought I would take a chance and buy it. When you turn it on, after the N is displayed, it momenteriarly displays what looks like the opening the Reading Forever page. Then is goes to a Red exclamation point that says to restart your device and try again.
I have tried booting from a CWM boot disk. It says it can't find E: when I try a data/factory reset, I suspect the partitions are meesed up. What is my best course of action at this point?
Click to expand...
Click to collapse
Bad choice on your part because the device information may be gone. But there is a guide to rebuilding the internal partitions here.
Try it out and see if it works. I've never tested any unbricking methods because, well, I've never been bricked. Important to read instructions carefully before doing anything and make sure you're knowledgeable on what you're doing.
It appears that I need to know whether I have an 8 or 16 Gb model. Is there a way to tell if I can't boot it?. TIA
Bonnie_Raitt said:
It appears that I need to know whether I have an 8 or 16 Gb model. Is there a way to tell if I can't boot it?. TIA
Click to expand...
Click to collapse
Ask the guy from craigslist or open up the back and look at the hardrive and see what it says.
No way to contact CL guy. Is opening up the device the only way to find out?
Bonnie_Raitt said:
No way to contact CL guy. Is opening up the device the only way to find out?
Click to expand...
Click to collapse
You'll have to open it up then. Only difference is the "hard drive" is 16 GB and the ram is 1 GB instead of half a gig.
I was able to contact seller. He says it's a 16 GB model. I'm off to try the fix listed above
I downloaded flash_restore_16gb_partitions_1-4&6.zip, put it on my CWM boot card, and chose it from "install zip from sdcard.. Here's what is says:
Installing flash_restore_16gb_partitions_1-4&6.zip
E: Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package
Opening update package
Installed update...
Extract xloaded
extract U-boot
extract recovery
extract Boot
Extract Bootdata
Install from sdcard complete
I then powered down NT.
Took a 4 GB SD card that had a single partition marked active with EASEUS Partiton manager. Copied nooktablet_1_4_2_update.zip to it. Inserted it in NT and rebooted
It flashes momentarily to reading fowever screen, then goes to updating software screen. Very quickly a red exclamation point appears asking me to restart to try to install software again. Restarting gives same results.
Should I move on to the ADB process or is there something else I can do at this point
Bonnie_Raitt said:
I downloaded flash_restore_16gb_partitions_1-4&6.zip, put it on my CWM boot card, and chose it from "install zip from sdcard.. Here's what is says:
Installing flash_restore_16gb_partitions_1-4&6.zip
E: Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package
Opening update package
Installed update...
Extract xloaded
extract U-boot
extract recovery
extract Boot
Extract Bootdata
Install from sdcard complete
I then powered down NT.
Took a 4 GB SD card that had a single partition marked active with EASEUS Partiton manager. Copied nooktablet_1_4_2_update.zip to it. Inserted it in NT and rebooted
It flashes momentarily to reading fowever screen, then goes to updating software screen. Very quickly a red exclamation point appears asking me to restart to try to install software again. Restarting gives same results.
Should I move on to the ADB process or is there something else I can do at this point
Click to expand...
Click to collapse
Have you tried the repart.img?
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
If you get the red x during that process you can try adb process.
Sent from my NookTablet using xda app-developers app
datallboy said:
Have you tried the repart.img?
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
If you get the red x during that process you can try adb process.
Sent from my NookTablet using xda app-developers app
Click to expand...
Click to collapse
Yes,that's actually what I tried at first. It doesn't work.
At this point I'm trying to load the ADB tools and drivers,
In [FAQ] NT Reference Thread | Tips&Tricks | How to's | Videos | NEW USER? PLEASE READ!
it references a link [HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Videos - Tutorial .
The video for windows doesn't work any more. I went ahead and downloaded the referenced
ADB + Fastboot + Drivers.zip
I made an attempt to load the uSB drivers. I'm not certain if I did it correctly or not. When I run the adb devices command is get nothing returned.
Can someone point me to a current reference for installing the drivers or offer more advice on where to go from here. Thanks
Bonnie_Raitt said:
Yes,that's actually what I tried at first. It doesn't work.
At this point I'm trying to load the ADB tools and drivers,
In [FAQ] NT Reference Thread | Tips&Tricks | How to's | Videos | NEW USER? PLEASE READ!
it references a link [HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Videos - Tutorial .
The video for windows doesn't work any more. I went ahead and downloaded the referenced
ADB + Fastboot + Drivers.zip
I made an attempt to load the uSB drivers. I'm not certain if I did it correctly or not. When I run the adb devices command is get nothing returned.
Can someone point me to a current reference for installing the drivers or offer more advice on where to go from here. Thanks
Click to expand...
Click to collapse
I have no idea how to set up ADB, never done it. So I won't be able to help you there. Sorry.
But since it is a 16GB version you may want to attempt the Adam Outler Ubuntu ReFlash Method. It uses ubuntu to recover your partitions on your device. Since you have nothing to lose with it, give it a try.
If someone else doesn't pipe in, I'll try it this afternoon
OK. I downloaded ADB stuff from
HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Videos - TutorialLike Tweet +1
I placed everything i c:\adb. I followed instructions and now have an "Othe device" called Barnes and Noble Nook Tablet". It has an exclamation point. I have uninstalled and reinstalled several times to no avail. I am running Windows 7 SP1 64 bit intel.
I'm at a dead end here. Can anyone assist?
Just finished reading
[UnBrick]TOTAL WIPE and reflash back to 1.4.0 via Ubuntu Recovery --Now Easier!!!!
It looks like something I could do, but I'd like some feed back from the experts before I bork my NT worse than It already is. Any thoughts?
Bonnie_Raitt said:
Just finished reading
[UnBrick]TOTAL WIPE and reflash back to 1.4.0 via Ubuntu Recovery --Now Easier!!!!
It looks like something I could do, but I'd like some feed back from the experts before I bork my NT worse than It already is. Any thoughts?
Click to expand...
Click to collapse
Well your nook is already borked up. You bought it with the internal partitions deleted most likely. This method writes zeros and rebuild the partitions itself.
Bonnie_Raitt said:
OK. I downloaded ADB stuff from
HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Videos - TutorialLike Tweet +1
I placed everything i c:\adb. I followed instructions and now have an "Othe device" called Barnes and Noble Nook Tablet". It has an exclamation point. I have uninstalled and reinstalled several times to no avail. I am running Windows 7 SP1 64 bit intel.
I'm at a dead end here. Can anyone assist?
Click to expand...
Click to collapse
You might find some helpful info/pointers re: setup for ADB access over USB at http://forum.xda-developers.com/showpost.php?p=35971559&postcount=13.
I got ADB drivers loaded and started at looking at trying to find out which partition is borked and how to fix. I started with http://forum.xda-developers.com/showthread.php?t=1531120,
When I tried somto delete and recreate partitons 10 and 11 I got a number of errors messages. I'm still looking for a "how to" when dealing with partitions. If anyone wants to hold my hand I would be grateful.
BTW, I tried the Ubuntu boot disk but could never get it to boot.
I'm not a smart man don't know where to go from here with soft bricked HTC One (AT&T)
Was experimenting with different stuff on my phone and currently on S-Off HBoot 1.44. I was tried to flash a new 4.4 ROM over and somewhere in there something went wrong. Went to backup file and everything was fine, decided to just try and wipe everything on phone (made backup files of everything and have the files in a folder on desktop) and that's where my troubles began. Taking advice from a friend of mine I ended up relocking the bootloader (mistake #1), so of course everything on phone was wiped. I was trying to do adb sideload to push a new rom after unlocking the bootloader again. The computer sees my device in adb on the cmd window. Says:
HT359W917890 recovery
but in sideload in TWRP it says:
E: Unable to mount
I'm guessing its because I no longer have the files on the phone or a stock anything on it. Please help me out here been messing around with it for about 3 hours now running in circles. I'm sure I'm missing an easy step in here but I've been reading all over and am starting to think this **** is pretty hopeless at this point.
Put the rom you are wanting to flash in the folder you are using to open the cmd window and type
adb push nameofrom.zip /sdcard/
I wake up from a nap, see your reply and try it out....now computer isn't seeing my device in adb again. This is so frustrating, back to square one I suppose
okay rebooted the phone and device is showing in adb again (yay) pushed the file through but I'm still getting the
E: Unable to mount '/data'
E: Unable to mount internal storage
any suggestions here?
SOLVED
All solved solved the E: Unable to mount issue by going into TWRP settings and doing a format data wipe. The pushed the file from the computer and voila all solved, I really appreciate the help man!
Brodrick said:
All solved solved the E: Unable to mount issue by going into TWRP settings and doing a format data wipe. The pushed the file from the computer and voila all solved, I really appreciate the help man!
Click to expand...
Click to collapse
Lol I was gonna suggest that but most people freak out when you ask them to format their sdcard
Glad you got it