Related
Okay guys, so here's a weird one.
My g-tablet was working great. Was running VEGAn-Tab Build, BETA 5.1.1, no reason to update it, because it did everything I needed. I finally had it to where I wanted it, then it all kind of started falling apart. Here's how.
I power it on and notice my home screen got all messed up for some reason (using launcher pro). All of the settings defaulted to the original. I tweaked it back to more or less how I wanted it, and when I had it back to normal, thought nothing better of it. Must have glitched out some how.
Then I notice a bunch of things starting to force close, specfically android market, amazon market, titanium backup, google services framework, launcher pro, etc. Odd thing is it would do it one at a time, but otherwise my tablet would carry on as normal.
I go ahead and restart the tablet, to see if that helps at all, and what do you know, the homescreen is messed up again! I thought launcher pro might have been the culprit, so I un-installed the app and rebooted... And launcher pro is still there.
I go ahead and delete it again and start deleting other apps, restarting the tablet, and no matter what I do, everything stays the same. time for some clockwork mod action. I go into clockwork mod, and try to do the factory reset option, thinking what the hey, I'll try anything right now. Hit it, mourn the loss of my user data, and reboot the system... and again, everything is still the same.
I hook up my tablet to the computer via usb, and it looks like I'm able to at least delete misc. files that way. But when I return to good old Tabatha (my nickname for Gtab) everything is stuck just the way it is.
Needless to say, it feels like I'm stuck in the twilight zone.
I know I should have researched it by now, but I'm going to finally look it up to see if I can recover with NVFlash (I know I know, very noobish of me, using strange roms and not knowing any of the basics).... but I'm increasingly worried I've got some kind of a hardware malfunction on my hands. Could it be the memory? The internal SD card?
Oddly enough, my tablet still functions... I can browse the web, hook it up to my computer, etc etc, but no matter what I do I can't alter the data I already have on my tablet. Can't delete things, can't change settings, update apps, etc. etc. Which makes it pretty much useless for what I wanted to use it for.
I finally realized what this is like. The movie groundhog day, and I'm stuck in the same day, over and over again.
Any help or input that might get me out of this mess would be greatly appreciated.
Phil: "I was in the Virgin Islands once. I met a girl. We ate lobster, drank piña coladas. At sunset, we made love like sea otters. *That* was a pretty good day. Why couldn't I get *that* day over, and over, and over..."
This is now the second time that I've seen this exact same problem. I was in the process of troubleshooting the original one when the user returned his gTablet for replacement. If you can stand the deja vu, read this thread.
Do not nvflash your tablet--nvflash cannot fix SD-card related problems. Read this post for why not.
Instead, do this for me: Reboot the gTablet, then open a Terminal, or, use adb and run this command:
Code:
$ dmesg > /mnt/sdcard/dmesg.txt
Attach that dmesg.txt which will contain messages from the kernel to your next post.
I'll check this thread in the evening.
rajeevvp said:
This is now the second time that I've seen this exact same problem. I was in the process of troubleshooting the original one when the user returned his gTablet for replacement. If you can stand the deja vu, read this thread.
Do not nvflash your tablet--nvflash cannot fix SD-card related problems. Read this post for why not.
Instead, do this for me: Reboot the gTablet, then open a Terminal, or, use adb and run this command:
Code:
$ dmesg > /mnt/sdcard/dmesg.txt
Attach that dmesg.txt which will contain messages from the kernel to your next post.
I'll check this thread in the evening.
Click to expand...
Click to collapse
Thanks for the direction, at least I know it isn't an isolated incident. It's 1:45 AM where I am right now, and I have to wake up for work in about 5 hours... So I probably won't be able to get in depth with the follow up on this stuff untill after work tomorrow night (so long as the wife doesn't hog the computer )
Again thanks for the quick response, I appreciate you pointing me into some sort of direction. Can't wait to try to get this sorted out!
Currently trying to figure out how to get ADB going.... pretty intimidating, but I'm trying. I got the Java JDK installed, installing the SDK, but can't find the "SDK Setup.exe" file or even a USB driver folder in the SDK directory. Got a good resource for getting ADB set up?
Save yourself some trouble. Got to http://www.knoppix.org/ and download the latest Knoppix live CD image.
Burn it, boot it, then use the adb executable from this post. For simple things like just running adb, you don't need the entire Android SDK.
Get me a dmesg while inside ClockworkMod:
Code:
$ [B]sudo ./adb shell dmesg > dmesg.txt[/B]
ADB commands documentation
Thanks, I'll try it out sometime this weekend!
Well, I really screwed myself now. I got the Linux distro loaded but still couldn't figure out how to get ADB to work. For whatever reason, When I boot from the DVD, I can't download the zip from within linux (get errors) and I could not open the ADB command by navigating to where I have it extracted in my hard drive. [Do I need to load the OS onto a flash drive instead?]
So I started messing with some stuff in clockwork mod. I apparently really goofed it, and I got a "Magic Value Mismatch" error everytime I tried to boot it up.
I looked up Magic Value Mismatch, and from there it pointed to using NVFlash to try to fix that problem. So tried that. After I flashed it, I thought for sure I finally had it back to stock, as the intro screen started to show the tap n tap logo... but i basically got stuck in a boot loop, tap n tap, then "n", then tap n tap, then "n", etc, until it dies.
I looked up this issue and apparently the key is to get into clockwork mod and do factory reset, reset cache, and partition the SD card to 2048 and 0, which I did... (per post #4 on this thread: http://www.slatedroid.com/topic/17501-helpstuck-in-bootloop/ ) but still no dice.
Not sure where to go from here, or if I can even get it to interface with ADB in its current state. Looks like I'm done for
Thanks for trying though
On second thought, I may have had a breakthrough, at least in getting ADB to see my tablet!!! Woohoo! It finally sees the device and has a serial number. Was following the device on this thread:
http://www.androidtablets.net/forum/viewsonic-gtablet-technical/5377-adb-g-tab-step-step.html
7. under the "[Google.NTx86]" section, paste the following:
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
save the file and exit.
But I have a 64 bit machine, so I finally figured it out and plopped that into the 64 bit portion of the .inf file. DOH!
So now let me see what I can drum up through the previous commands above.... though the parameters have changed now to be sure... Due to my haste things may have taken a turn for the worse.
To recap, now my tablet is stuck in a boot loop after having done NV Flash, after having screwed up some settings in clockwork mod trying to fix a "Magic Value Mismatch" error.
Tried:
$ dmesg > /mnt/sdcard/dmesg.txt
I just run this in the cmd prompt at my platform-tools directory where the adb is correct?
All it says is, "The system cannot find the path specified."
Am I doing something wrong, or is my tablet that messed up?
Okay, this is slightly weird. So I was browsing around in clockwork mod, and lo and behold, the original zip flies for vegan tab are all STILL THERE. So I reloaded them... And My tablet zips back to exactly the way I had it before!
Only this time, so far no force closes. This looks way too good to be true after what I've been through. I'm going to try modifying some files and settings and restart my tablet to see what it does. I'm pretty sure I can't be out of the woods yet. Allthough it is 3:33 AM as this is happening... magic hour. I may be going insane.
EDIT: Nope, was definitely way too good to be true. All my data is as stuck as it was ever was. But at least now I can get into it again. But now we're back to square one. Lemme figure out this dmesg business and get back to you. X(
So I would try issuing the following exactly in the command line at the adb platform tools folder:
$ dmesg > /mnt/sdcard/dmesg.txt
Is that code supposed to be copy and paste in? I don't seem to be getting anything. I can do the following command and get the info to pop into the command interface:
adb shell dmesg
But I can't figure out how to save that to a text file. And you want me to do that while the g tablet is in recovery, correct?
FYI, trying to do it through Windows 7. Would that command only operate in the linux environment via knoppix?
Thanks
titobetlogs said:
I can do the following command and get the info to pop into the command interface:
adb shell dmesg
But I can't figure out how to save that to a text file.
Click to expand...
Click to collapse
Redirect the output to a file:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
titobetlogs said:
I got the Linux distro loaded but still couldn't figure out how to get ADB to work. For whatever reason, When I boot from the DVD, I can't download the zip from within linux (get errors) and I could not open the ADB command by navigating to where I have it extracted in my hard drive.
Click to expand...
Click to collapse
I suggested using Knoppix just because it is so easy to use adb in Linux. Broken-down steps for future reference:
1. Download and burn the latest Knoppix Live CD iso image. Check the downloaded file size. The .iso file should be ~700MB in size. Also, test the CD by booting it and then typing at the boot prompt: knoppix testcd
2. Boot Live CD and skip the creation of any partition or file to store user data. After all, we just want to run adb.
3. After Knoppix has booted into the desktop, run a browser, right click on the adb.zip attachment in this post, then select "Save Link As..." and save the zip file into /tmp.
4. Connect the gTablet to the PC via the USB cable.
5. Open a terminal window, then type in it:
Code:
hostpc$ [B]cd /tmp[/B] [I]Change to the dir. where adb.zip was saved[/I]
hostpc$ [B]unzip adb.zip[/B] [I]Unzip zip file[/I]
hostpc$ [B]ls -l adb[/B] [I]Check if the adb program was extracted OK[/I]
-rwx------ 1 rvp rvp 159620 Dec 1 22:23 adb
hostpc$ [B]chmod 555 adb[/B] [I]Make adb executable.[/I]
hostpc$ [B]sudo ./adb shell dmesg > dmesg.txt[/B]
Note 1: do not type in the shell prompt, 'hostpc$'. It is only there to show you what the screen should (roughly) look like.
Note 2: If adb says something like "device not found", just unplug the USB cable from the PC, wait a few moments, then re-plug the cable and re-run the adb command again.
6. Go back into the browser and attach the dmesg.txt file that is there in /tmp. You will have to tell the Noscript plugin to allow scripts from xda-developers to enable attachments. Right click on the page, then select the Noscript menu item, then choose "Temporarily allow xda-developers.com".
I thought for sure I finally had it back to stock, as the intro screen started to show the tap n tap logo... but i basically got stuck in a boot loop, tap n tap, then "n", then tap n tap, then "n", etc, until it dies.
Click to expand...
Click to collapse
I'm not surprised. If the files on the internal SD card cannot be modified then that boot loop behaviour is to be expected. Here's why:
Android requires certain partitions to exist on the system. These partitions can be either on the flash or on SD cards. The partitions are:
/system: This is where the binaries and system apps that come with the firmware are stored. This partition is usually mounted read-only to protect it. On the gTablet, this partition is on the 512MB built-in NAND flash chip.
/cache: As the name indicates, this is the partition used to speed up the execution of the Java apps. Temporary files are also created here. This partition too is on the built-in NAND flash chip.
/data: This is where user-downloaded apps are stored by default, and also where Android stores its system configuration data. This partition, on the gTablet, is on the internal SD card.
/sdcard: This is where user content like media files, books, and the apps moved to SD card are stored. This partition too is on the internal SD card.
The first 3 partitions are critical and Android won't come up without them being present (or, if there are any errors on them). Among these 3, only /system needs to be correctly populated (When you install a ROM, new stuff is copied here). The other 2 partitions, /data and /cache can be empty and the system will boot up fine--with defaults. In fact, when you select "wipe data/factory reset" in CWM, /cache and /data are re-formatted--effectively, wiped clean.
(There are 2 other important partitions on the NAND flash chip, but, these are not mounted because they don't contain a proper filesystem. You have to use special tools to create the contents of these 2 partitions.
The first of these is the "boot" partition. This one and "system" are re-written when you install a new ROM. The "boot" partition holds the Android Linux kernel. If you install a new kernel, only the "boot" partition is rewritten.
The second is the "recovery" partition. This contains a separate, and usually different (and safe), Linux kernel and a mini filesystem image. This is a fail-safe partition. Stock recovery and ClockworkMod sit here.)
In your case, nothing on the internal SD card can be modified, so the stuff in /data will still be from your old ROM. (nvflash also cannot modify SD card contents, as I mentioned before.) When the stock firmware boots up, it will find incompatible stuff in /data. Critical apps will then die. Android will restart them, they will die again. This is your boot loop.
Get me the dmesg output and then we'll run a few tests using CWM, but, judging from your previous posts, I don't think your internal SD card can be fixed. You have 2 options:
1. Return the tablet for a replacement.
2. If you can't return it, I can switch the internal and external SD cards on your ROM so that you can boot and use the system (almost) normally. But, this is a custom solution and you will need to have an external SD card in its slot always. Read through this thread.
Wow, you really know you're stuff! I'll see what I can get you later on in the day with regard to the dmesg, I'm currently still at work.
I had suspected a hardware error... bummer. I'll definitely be interested in seeing if I can just use the external micro sd slot to sub out for the internal sd card. I would at least like this thing to be functional again, though I suppose I'll never be able to try any of the honeycomb roms when those get past alpha. Oh well.
Do you know if this thing takes 32 gb micro sd cards? That would be pretty awesome, I at least wouldn't feel too limited on space.
By the way, thanks for all your help on this, I know I'm a huge noob. I greatly appreciate your patience and taking the time to break everything down for me. I have absolutely zero background in programming or anything computer related, though I do find this stuff extremely fascinating! If I could rewind the clock and study this stuff in school, I would do it in a heartbeat.
Again, thanks so much, can't thank you enough.
titobetlogs said:
I would at least like this thing to be functional again, though I suppose I'll never be able to try any of the honeycomb roms when those get past alpha. Oh well.
Click to expand...
Click to collapse
No, you should be able to run whatever ROM you want. I'll send you an installable zip file, in a few days, which should get you going again on Vegan-Tab, at least. You'll just need to remember to flash this zip file right after you've flashed the ROM (of your choice).
Right now, I don't know if I need one zip file for each kind of ROM in existence for the gTablet, or, if I can use some scripting and do the internal/external SD card switch using just a single installable zip file. I'll look into this on the weekend.
Do you know if this thing takes 32 gb micro sd cards?
Click to expand...
Click to collapse
Yes, it does.
By the way, thanks for all your help on this, I know I'm a huge noob...
Click to expand...
Click to collapse
I was a complete noob to Android myself back in April of this year. I've picked all of this up in just a few months. I'm pretty sure you can do it too, with a bit of poking around in the system. Of course, having a background in Unix/Linux helps a lot.
In your honor, below are some inspiring lyrics from the Karate Kid soundtrack:
You’re the best!
Around!
Nothing’s gonna ever keep you down
You’re the Best!
Around!
Nothing’s gonna ever keep you down
You’re the Best!
Around!
Nothing’s gonna ever keep you dow-ow-ow-ho-how-ho-own
INSPIRING GUITAR SOLO
Dude! you're embarrassing me -- I haven't send you the zip file yet... and, you haven't sent that dmesg output I wanted.
I know I've been stuck at work and family functions every day this week so far. Hopefully I'll get to it soon
Finally got to this! Here you go! Thanks again!
titobetlogs said:
Finally got to this! Here you go!
Click to expand...
Click to collapse
Can't see any problems in that dmesg output. Time for some tests on the internal SD card.
Boot into CWM, then run on PC (on Linux run: sudo ./adb shell):
Code:
C:\SOME\PATH> [B]adb shell[/B]
~ # [B]mount /dev/block/mmcblk3p1 /sdcard[/B] [I] Mount internal SD card partition[/I]
~ # [B]mkdir -p /sdcard/a/b/c[/B] [I]Make a directory tree[/I]
~ # [B]echo test > /sdcard/a/b/c/test.txt[/B] [I]Create a file[/I]
~ # [B]cat /sdcard/a/b/c/test.txt[/B] [I]Read it back again[/I]
test [I]Correct[/I]
~ # [B]echo 3 > /proc/sys/vm/drop_caches[/B] Flush kernel caches
~ # [B]cat /sdcard/a/b/c/test.txt[/B] Read it back again
test Correct
~ # [B]umount /sdcard[/B] [I]Unmount[/I]
~ # [B]mount /dev/block/mmcblk3p1 /sdcard[/B] [I]Remount /sdcard[/I]
~ # [B]cat /sdcard/a/b/c/test.txt[/B] [I]Reread file[/I]
test [I]You should see "test" here[/I]
~ # [B]umount /sdcard[/B]
You should see "test" after the kernel flush and the remount.
Next, reboot the tablet--back into CWM, then run the cat command again. `cat' should output "test", again, if the SD card is OK.
Here's a screen of the commands I entered and what I got back. Did I do anything wrong? Looks like something's a bit off.
This has been reported at http://code.google.com/p/cmtouchpad/issues/detail?id=436&start=100.
In order to fix this, reboot your touchpad into webOS. Fire up novacom on your computer, and run the following:
Code:
umount /dev/store/media
fsck.vfat -vy /dev/store/media
The issue is due to the Android fsck not working correctly, so it's not able to fix filesystem issues. Once you run the above and reboot to CM7, the sdcard should no longer remount as readonly.
This helped alot thanks.
My touchpad seems to be in read only mode. Not able to webos doctor properly because of it. Cant reinstall cyanogenmod either. I have access to webos recovery and clockwork mod. Any command to get write access back?
Used novaterm for commands
Noob Question
Hi, I'm really new at this and I'm having the same problem stated above. I was able to load CM7, Alpha 2 on my Touchpad and all seemd well until I started downloading apps. Now, SD storage is full yet seeing plenty of storage left under settings. Could you please give step-by-step instructions for the fix above? For instance, do I load webOS then go into USB mode or do I go into USB mode during the webOS reboot using the volume up button? Any and all help would be greatly appreciated!!!!
This should be stickied
Sent from my SPH-D700 using XDA App
Here's what you do:
If you installed the novacomd drivers which you should have to get preware going then do the following.
1. Hook up your touchpad to the pc, and boot it up to web os. Don't mount the usb drive just leave it alone.
2. Navigate to C:\Program Files\Palm, Inc\terminal and double click novaterm the windows batch file. The icon will look like two cogs.
3. In the new window select file connect.
Type fsck.vfat -vy /dev/store/media and hit enter.
You're done. exit the screen and restart into cm7, everything should be back to normal now.
I keep getting an error when double clicking novaterm. It will open up a terminal window and an error message saying "javaw" on the top with the following text: "Windows cannot find 'javaw'. Make sure you typed the name correctly, and then try again."
Any help is appreciated!
It's because you have installed a wrong version of Java (same problem for me, I installed a x86 version and i've got a x64).
So uninstall it completely
If you have a x64, install the right version of java SE Development kit
And everything would work great ! (worked for me)
Thanks! That allowed me into get into novaterm. And the fix works!!!
Hi,
hope this is the right place to post but I'm using Ubuntu 11.04 and when trying to enter the command via novacom I receive the following error:
Code:
bad or error response from other side: 'err -1 bad command string'
the novacom drivers are corectly installed (I managed to flash CM onto the touchpad with the ACMEinstaller) and I can see the touchpad when typing the following command:
Code:
novacom -l
I'm sure this is down to my inexperience with using novacom rather then the drivers etc. Can anyone help?
Thanks
danh86 said:
Hi,
hope this is the right place to post but I'm using Ubuntu 11.04 and when trying to enter the command via novacom I receive the following error:
Code:
bad or error response from other side: 'err -1 bad command string'
Click to expand...
Click to collapse
novacomd should be running (check it ps -ef | grep novacom).
You want to start novaterm (assuming novacomd is already running) and enter the command there. (Not as a command line argument to novacom).
So, it should look something like this:
Code:
$ ps -ef | grep novacomd
root 8331 1 0 13:37 ? 00:00:00 /opt/Palm/novacom/novacomd
$ novaterm
[email protected]:/# umount /media/internal
[email protected]:/# fsck.vfat -vy /dev/store/media
dosfsck 2.11 (12 Mar 2005)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "MSWIN4.1"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
32768 bytes per cluster
96 reserved sectors
First FAT starts at byte 49152 (sector 96)
2 FATs, 32 bit entries
1409024 bytes per FAT (= 2752 sectors)
Root directory start at cluster 458 (arbitrary size)
Data area starts at byte 2867200 (sector 5600)
352168 data clusters (11539841024 bytes)
0 sectors/track, 0 heads
0 hidden sectors
22544384 sectors total
/Open Source Information.pdf
Contains a free cluster (66256). Assuming EOF.
/Open Source Information.pdf
File size is 292092 bytes, cluster chain length is 0 bytes.
Truncating file to 0 bytes.
(..snip..)
Reclaiming unconnected clusters.
Reclaimed 15 unused clusters (491520 bytes) in 7 chains.
Checking free cluster summary.
Free cluster summary wrong (253428 vs. really 253444)
Auto-correcting.
Performing changes.
/dev/store/media: 25628 files, 98724/352168 clusters
[email protected]:/#
systoxity said:
Here's what you do:
If you installed the novacomd drivers which you should have to get preware going then do the following.
1. Hook up your touchpad to the pc, and boot it up to web os. Don't mount the usb drive just leave it alone.
2. Navigate to C:\Program Files\Palm, Inc\terminal and double click novaterm the windows batch file. The icon will look like two cogs.
3. In the new window select file connect.
Type fsck.vfat -vy /dev/store/media and hit enter.
You're done. exit the screen and restart into cm7, everything should be back to normal now.
Click to expand...
Click to collapse
I try to click file->connect, but every time it says "unable to connect service."
I boot into WebOS 3.0.4, connect to USB, and doesn't select to mount TP.
Anyone can help?
Just tried this fix on Alpha 3, after SD card said it was unmounted. I booted onto Web OS, connected to PC. Hit cancel when it asked me to turn on USB mode. Navigated to Crogram Files / Palm.Inc/ Novacom/ Novaterm. Ran Novaterm, typed in the commands as spelled out here, also tried copy pasting the command to make sure it wasn't spelling or caps that was the issue, it did its thing. Unplugged, rebooted to CM 7, and nothing, still says SD card was removed, please mount a new one. Can anyone help?
Oh yeah, even more troubling, now when the TP goes to sleep it fails to come back. The only way to bring it back is to reboot.
mes215 said:
Just tried this fix on Alpha 3, after SD card said it was unmounted. I booted onto Web OS, connected to PC. Hit cancel when it asked me to turn on USB mode. Navigated to Crogram Files / Palm.Inc/ Novacom/ Novaterm. Ran Novaterm, typed in the commands as spelled out here, also tried copy pasting the command to make sure it wasn't spelling or caps that was the issue, it did its thing. Unplugged, rebooted to CM 7, and nothing, still says SD card was removed, please mount a new one. Can anyone help?
Oh yeah, even more troubling, now when the TP goes to sleep it fails to come back. The only way to bring it back is to reboot.
Click to expand...
Click to collapse
Sorry to say but sounds like the clusters are all messed up. Only way I got around this was in webOS secure wipe all. The most secure method and it will redo all the partitions. Takes a couple hours and you will lose all data but after that, I was back in business.
Sent from my PG86100 using Tapatalk
Leoisright said:
Sorry to say but sounds like the clusters are all messed up. Only way I got around this was in webOS secure wipe all. The most secure method and it will redo all the partitions. Takes a couple hours and you will lose all data but after that, I was back in business.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
i did a regular wipe and it cured my sd card problems.
I am attempting the fix as well. When I attempt to run Novaterm, I get the message: "Could not find the main class: de/mud/jta/Main. Program will exit" under Java Virtual Machine Launcher.
I'm running 32bit Vista.
Any help appreciated!
Does the secure WebOS wipe remove CM7 as well? Do you need to reinstall CM7 after? If so, how does it correct the SD Card Read Only problem?
I am running CM7 Alpha 3 (upgraded using Clockwork Mod) and I can't download anything to my Touchpad. Says "SD Card Full" while viewing "Storage" under Settings says I have over 25G free. CM7 won't download, save or play any Audio/Video or other files.
I tried the fix mentioned above, but got message: "Could not find the main class: de/mud/jta/Main. Program will exit". I have deleted and reinstalled Java and get the same message. 32Bit Vista OS on desktop.
Any Ideas?? Many thanks.
After this command (fsck.vfat -vy /dev/store/media) i get
Reclaiming unconnected clusters.
Any ideas how to fix this?
I just installed the 3.5 update to both a 32gb and 16gb which had been running 3.0.
The end result is that both machines now state that the sd card is not mounted. Should I try the above fixes on 3.5 or is the suggested fix only for 2.1?
I busted my Nook Tablet, tried a hundred different things to fix it, and was about to give up, when I finally found the solution. This is my story.
Seriously, though, this forum has been a huge help to me, and I'm posting this in the hope that it will help someone.
First, a little background on me. I'm a software developer, and I've even contributed a bit to the development of the gingerbread-based CM7 for the Droid X. So I know a bit about Android, but I don't pretend to understand everything, especially on the Nook Tablet. That will become clear as you read the rest of this because I can't really explain some of the things I experienced.
Using several of the helpful guides here, I successfully booted ClockwordMod Recovery off an SD card, rooted my tablet, and installed the CM7 alpha (http://forum.xda-developers.com/showthread.php?t=1481826). Since booting CWM off the SD worked so well, I didn't feel the need to install it internally. It was a beautiful thing.
By the way, in order to boot CWM from an SD card your tablet must be plugged into USB! At least that has been my experience, and it hasn't always been made 100% clear.
Then, I bought a new SD card - the one I used originally was borrowed from another device. The new one was 16 gig. I wanted to make sure I could still use it to boot into CWM, so I started out as before by writing the image found at
http://forum.xda-developers.com/showthread.php?t=1488035 to my SD card using Win32DiskImager.exe, which I acquired from http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14. But this repartitioned my 16 gig SD card down to 2 gig, so I used gparted in a Ubuntu VM to resize the partition to 16 gig.
I had all sorts of trouble getting into CWM with this new SD card. I don't really know why. Maybe the partition resizing was an issue, I'm not sure. But after lots of attempts, including plenty of failed boots, I started getting the dreaded black screen saying, "Please restart your device and try again. If you encounter the same issue, please contact customer service or visit: nook.com/tablet/support." I couldn't boot up CM7 anymore.
At this point I switched back to my previous SD card, plugged in the USB cable, and was thankfully able to boot into CWM. I tried the usually stuff. Reset data. Reinstalled CM7. Restored the backup of the factory ROM before I installed CM7. Nothing worked, I always got the "please restart" screen. Then I tried the 8 failed boots method to restore the factory state. It wouldn't go into the restore mode, just the same garbage again. At this point I figured I had really and truly bricked my device. This thread (http://forum.xda-developers.com/showthread.php?t=1397262) describing a similar problem didn't give my any confidence.
But since I could get into CWM, I realized I should at least be able to get into a shell via ADB and have a look around. Getting ADB working was a challenge, but eventually this post (http://forum.xda-developers.com/showthread.php?t=1363652), installing the USB driver attached to this one (http://forum.xda-developers.com/showthread.php?t=1354487), and adding the necessary line to adb_usb.ini (see the runmefirst.bat in the previous link) got me up and running with an adb shell.
I suspected my problem had something to do with triggering factory reset mode with so many failed boots, and somehow that factory reset mode was broken. With that in mind, I eventually stumbled upon this post (http://forum.xda-developers.com/showthread.php?t=1444630). I use CWM to mount /bootdata, logged in from my computer with "adb shell", and issued the dd commands the post described to reset the BootCnt and BCB files. I had to remount the bootdata partition read/write with "mount -o rw,remount /bootdata". If you do this once and still get a "Read-only file system" error when you do the dd command, just try the mount command again. I don't pretend to totally understand why that would be necessary, but it seemed to be necessary for me.
The first time I tried this and rebooted, I still got the same "Please restart your device error." It took me a couple of tries to figure out that I had to issue these commands and then remove the SD card before rebooting. It seemed as if booting from the SD card somehow re-poisoned the device so that even once I removed it I was still in a bad state.
Once I did this my device booted back into CM7. I shut it down, used the 8 failed boots method, and was able to reset to factory successfully. So apparently I was in some sort of badd BootCnt/BCB state, but it wasn't just the regular 8 failed boots state. I'd love to hear an explanation of why this might be, if anyone knows.
TL;DR: if you get a "Please restart your device and try again" error and nothing seems to fix it, try this:
1. Boot into CWM off an SD card
2. Mount /bootdata via CWM
3. Log in from your computer using "adb shell"
4. mount -o rw,remount /bootdata
5. dd if=/dev/zero of=/bootdata/BootCnt bs=1 count=4
6. dd if=/dev/zero of=/bootdata/BCB bs=1 count=1088
7. Remove SD card
8. Reboot
Thanks Kring789 so much, i have a same problem like you. I do step by step as you wrote, but at step 4, i have a error message from adb shell "remount /bootdata
/sbin/sh: remount: not found". And i can't reset my nook to factory default, it still display "Please restart your device and try again". Help me!
Sorry for my bad English, i'm vietnamese
tien_ttm said:
Thanks Kring789 so much, i have a same problem like you. I do step by step as you wrote, but at step 4, i have a error message from adb shell "remount /bootdata
/sbin/sh: remount: not found". And i can't reset my nook to factory default, it still display "Please restart your device and try again". Help me!
Sorry for my bad English, i'm vietnamese
Click to expand...
Click to collapse
Can you copy/paste the exact command-line you used? It sounds like you might have a space somewhere it doesn't belong, or something like that.
Yes, i copied command-line from your first post. I don't understand my nook tablet. It'll lost all the data and program that i have installed after i reboot it. It keep the data and program 2 months ago. I have copied some mp3 songs to internal card, after reboot it, all of songs disappear. I bought it from internet so i can't know what happened to it.
tien_ttm said:
Thanks Kring789 so much, i have a same problem like you. I do step by step as you wrote, but at step 4, i have a error message from adb shell "remount /bootdata
/sbin/sh: remount: not found". And i can't reset my nook to factory default, it still display "Please restart your device and try again". Help me!
Sorry for my bad English, i'm vietnamese
Click to expand...
Click to collapse
If I am reading your comment correctly, it looks like you're using the wrong command: typing 'remount' instead of 'mount', is that correct?
Yes, "mount -o rw,remount /bootdata" is one command, not two commands separated by a comma.
kring789 said:
Yes, "mount -o rw,remount /bootdata" is one command, not two commands separated by a comma.
Click to expand...
Click to collapse
I fixed this command-line. Adb shell did not show error, but NT still display "Please restart...". Hix, what's wrong with my NT
tien_ttm said:
I fixed this command-line. Adb shell did not show error, but NT still display "Please restart...". Hix, what's wrong with my NT
Click to expand...
Click to collapse
Paste your entire adb shell session in here and let me take a look. Also, did you remember to remove your SD card before rebooting?
NT8 will not boot except via SD
Thank you so much for posting this.
I have the 8gb model NT and (mistakenly) tried to flash CWM & CM7a to the EMMC of my tablet. At that time, there were no warnings about how it would brick the NT8.
Now, my tablet will not boot to ANYTHING on the internal memory. I do NOT get the warnings that you mention - or even a flash of light. No matter how I try to boot it (with or without cable, with or without the Nook button) or how long I hold the buttons down, it still remains with a BLACK SCREEN.
However, the SDCard will boot properly. I followed your instructions in the O.P. precisely and I did NOT receive any errors. However, it still will not boot internally.
I then tried Veronica's process to flash CM9 to the internal (which is supposed to work on NT8). The flash process (via SD/CWM) went properly and I did not receive any errors. However, I still cannot get anything to boot (except my SDCards).
If I put my CM7a (bootable) SDCard into the NT8, it boots and runs great! Likewise meghd00t's recovery/CWM sdcard boots and runs properly.
I can do ADB & FASTBOOT and I have even done the dd to download my partitions (for backup) and then dd copies from online. Still no joy.
However, even after dd'ing p5, ADB still reports my TRUE serial number? It seems that the dd to part5 did not take?
The only other thing that I have found, that seems significant, is the fact that when I am in CWM, I cannot mount the EMMC. I can ADB/shell into the device but that did not allow me to mount the emmc either.
Any ideas? How can I force the device to mount the emmc?
Unbrick & return NT8 to STOCK
This process did NOT clear my Nook Tablet (8GB). Neither did any of the other (previously existing) methods clear it. It was bricked and would ONLY boot with a bootable SDCard. Otherwise, it remained totally black.
However, Meghd00t's recovery SDCard did the trick. It should work for either NT8 or NT16 devices and restores the Nook to Stock configuration. I did NOT lose my serial number.
Find Meghd00t's thread here: http://forum.xda-developers.com/showthread.php?t=1562130
video
Kringle789, i can't understand your instruction... could you make videoinstruction?
P.S. please, help me. It's the brand new device for me and I'm very sad that I can't use it.
P.P.S. I can turn on CM7 from SD.
xstranger said:
Kringle789, i can't understand your instruction... could you make videoinstruction?
P.S. please, help me. It's the brand new device for me and I'm very sad that I can't use it.
P.P.S. I can turn on CM7 from SD.
Click to expand...
Click to collapse
I have... http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/ the video is embedded.
Sent from my Nook Tablet using xda premium
videoinsruction
Thank you raywaldo, but this video about how to unbrick NT when there is no message "Please restart your device and try again..." (I have this message)
Thats why I need videoinstruction for unbricking by kring789
Sorry for my English and please help.
xstranger said:
Thank you raywaldo, but this video about how to unbrick NT when there is no message "Please restart your device and try again..." (I have this message)
Thats why I need videoinstruction for unbricking by kring789
Sorry for my English and please help.
Click to expand...
Click to collapse
Sorry but I haven't seen that message. Have you tried the obvious ... restart and try again. I suspect that you have. Don't have any other ideas.
Sent from my Nook Tablet using xda premium
restart
Yes. I have tried. Maybe...=)
Could you tell me how to restart device?
I want to do it again. Maybe I have done something wrong.
Restart
xstranger said:
Yes. I have tried. Maybe...=)
Could you tell me how to restart device?
I want to do it again. Maybe I have done something wrong.
Click to expand...
Click to collapse
To restart:
Hold the power button for 30 seconds to power off.
Release & then press the power button again until the "n" screen appears.
raywaldo
It doesn't work.
Thank you.
xstranger said:
raywaldo
It doesn't work.
Thank you.
Click to expand...
Click to collapse
is the back lite "on" ? what is you hold down the 'power' and the 'N' at the same time ?
old_fart said:
is the back lite "on" ? what is you hold down the 'power' and the 'N' at the same time ?
Click to expand...
Click to collapse
nothing had happend. It's still the same problem.
I suppose, I have damaged the booting section/s.
And I don't know what to do...(
Maybe that
I can't download CWM on SD. Can anybody help me? Please, give me some instruction.
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.
After breaking the screen on my phone I spent the following months reading about how to extract data. It all comes down to enabling ADB debugging and having your computer authorised. Usually this can be done from recovery and you're good to go. However, if you have a broken phone that is fully stock, with ADB disabled and with no custom recovery support then your data is as good as bricked. Such was the case with me when I broke my rare Samsung G360G. However, my phone was supported by CF-AutoRoot by Chainfire, and this gave just the opening I needed to go full wide.
Prerequisites:
Your phone needs to be supported by CF-AutoRoot. Check on there and the new site linked for support of your phone. If it's not there then you will need to download a stock ROM and use the CF-AutoRoot site tool to generate a root package for you. But that is outside the scope of this tutorial. This procedure has only been tested on Samsung. Your phone should have a minimal working charge.
https://autoroot.chainfire.eu/
This tutorial is also based on Linux. It should be translatable to Windows and Cygwin. But for simplicity I'll just use the method I used on Linux. However, if using Odin like I do, you'll need Windows to finish it off.
Aside from this it assumes files in are named in a particular format with a certain file format.
Tutorial:
1. First you need to download a CF-AutoRoot package for your phone. Won't get far without it.
2. Open up a terminal in Linux. We need to download some depends so enter this command:
Code:
sudo apt-get install android-tools-adb android-tools-fsutils
3. We need to extract the archive contents out. Create a suitable folder inside your home folder to build the patch in and cd to it. This uses an example file named CF-AutoRoot-example.tar.md5. Substitute with your actual archive name. Like so.
Code:
mkdir cfar-adb
cd cfar-adb
tar -xf CF-AutoRoot-example.tar.md5
4. There should be a recovery.img and a cache.img.ext4 extracted out. We just need to modify the cache.img.ext4. But first we need to convert it to a workable format. From a sparse to a raw image.
Code:
simg2img cache.img.ext4 cache.raw.ext4
5. We need to mount the cache image
Code:
mkdir cache
sudo mount -t ext4 -o loop cache.raw.ext4 cache
6. The big one. Doing the mod. So now we need to modify the cfar cleanup script. We need to insert commands on the end to enable ADB and add the key to authorise the computer. The following will do just that in this fashion.
a)
You will need to load in the cfar-cleanup.sh file inside the cfroot folder from the cache point mounted. Locate the end and paste the following lines before the reboot and exit commands on the end. Don't save yet.
Code:
echo -n 'mtp,adb' > /data/property/persist.sys.usb.config
mount -o remount,rw /system
echo '' >> /system/build.prop
echo 'persist.service.adb.enable=1' >> /system/build.prop
echo 'persist.service.debuggable=1' >> /system/build.prop
echo 'persist.sys.usb.config=mtp,adb' >> /system/build.prop
chmod 644 /system/build.prop
mount -o remount,ro /system
mkdir -p /data/misc/adb/
echo '' >/data/misc/adb/adb_keys
chmod 640 /data/misc/adb/adb_keys
b)
Load up the ~/.android/adbkey.pub file in a text editor and copy the entire contents in the clipboard. Now back at the script locate that last echo command you pasted into it and set the cursor just after the first single quotation mark. Now paste the clipboard in! This will add your key in. Make sure it's only between the single quotes with no extra characters or line feeds. The lines will naturally split if they don't fit on screen. Otherwise it should be good to go.
c)
Okay now save the file. The above will enable ADB and authorise your computer on the main Android system after the rooting script has done it's work. Before it reboots normally.
7. We need to unmount the cache so it's ready for use.
Code:
sudo umount cache
8. We need to convert the raw image back into a sparse image.
Code:
img2simg cache.raw.ext4 cache.img.ext4
9. Okay were almost done. Now we repack the files into a new Odin archive. Choose a suitable new filename. Like I have done here with my example file.
Code:
tar -H ustar -c recovery.img cache.img.ext4 > cfar-adb.tar
md5sum -t cfar-adb.tar >> cfar-adb.tar
mv cfar-adb.tar cfar-adb.tar.md5
10. The final step! So now the new package is ready for use. We just to use Odin and flash it to the phone. Save the package to a USB stick if needed.
a)
Reboot into Windows. Or you can run it virtualised from Linux. But I prefer to use the real things when dealing with things of a delicate manner and working blindly. Unplug your phone from the computer if connected. Now load up Odin in admin mode.
b)
Just to make sure pull the battery from your phone. Give it a few seconds then put the battery back in and click the back cover on. Now hold down volume down, then home key, and finally hold down power. Wait for the vibration. Then release power after a few moments. Finally release the other keys. At this point press volume up briefly. You should have just put your phone blindly into download mode. I've done this numerous times.
c)
Plug your phone into your computer. After a moment you should see Odin respond with a device added. Usually the phone can vibrate also when it connects giving more positive signs. If nothing happens disconnect the phone from the computer and retry the last step again to put it into download mode. Took me a few tries before I could do it blindly. It helps if you have a working Samsung to test it out on so you can see what happens before you can only feel it.
d)
Now in Odin press the PDA (or AP) button. Select the cfar-adb.tar.md5 package you made up. If the package is fine it will pass the md5 test. Now press the Start button and watch it go! If all goes well it will upload recovery, cache, give you a pass and then the phone will reset. At this point it will be in the process of being rooted, enable ADB, then reboot. If something goes wrong then you may need to go back and check all the patched files. Then rebuild the package again. But be careful, if the ADB has been enabled in the build.prop file one time, you don't want to add it in again and create duplicates, no matter how keen. Once I had it added the only other major problem I encountered was using the correct adb key.
e)
Hopefully now your phone is rooted, has ADB enabled and is booting up normally. Give it a few minutes. You can even see signs of life in Odin with adds and removes on USB activity. Your phone should also vibrate at times. And making noises is also a good sign.
1.1. So I just cranked it up to eleven. Open a Linux terminal again and give it a test. With your phone plugged in.
Code:
adb devices
If all goes well then adb will find your phone as well as list your device as authorised. You can now open shell to the inside. USB debugging is now enabled.
Conclusion:
Well I hope this helps those who have their app data stuck under a broken screen. As long as it was to type in this tutorial It still took me less time to write this tutorial than to learn all that was needed and apply it to my phone. This ends here but for you it may be only the beginning. A next step would be a screen mirroring app which I think is a must have for visual feedback. And USB debugging opens up these possibilities. One thing to be careful of, in a related issue, is that just because you can use adb and the phone is also rooted doesn't mean it will all work at once. If you are tempted to "su" it in an adb shell and get right in there then SuperSU will ask for permission on a blank screen. As will also happen if you try to do an adb backup, it will ask for confirmation on screen. So just expect to work with USB debugging blindly unless you already have a screen mirroring app installed. If you don't have one installed that is your next step.
And on that note. Good luck!
Hi there,
Your tutorial on how to achieve this on Linux looks real neat and complete. Unfortunately, i'm on Windows and i would like to know if you would be able to rewrite this totorial for a Windows user?
I've been reading online for about a week and i've never saw such a complete guide to help newbies to ADB to be able to retrieve data on their locked broken devices.
Cheers!
Hi RaiM1986 and thanks for your kind words. Yes I wrote it so it would be useful to newbies and seasoned hackers alike. Plus I needed to write down some instructions in case I need to do it all again.
Looking at the tutorial it is a bit Linux-centric. I don't know how well it would translate to Windows. Though there would be Windows version of the tools used the main problem would be mounting the filesystem image and making modifications without corrupting it. Because of things like Linux file modes.
However the following tools may be of assistance.
ADB tools:
https://wiki.lineageos.org/adb_fastboot_guide.html
Cygwin provides Linux tools if needed:
http://www.cygwin.com
simg2img:
https://github.com/KinglyWayne/simg2img_win
For mounting the ext4 image:
https://www.osforensics.com/tools/mount-disk-images.html
img2simg and other tools:
https://forum.xda-developers.com/showpost.php?p=49235638&postcount=5
For the ADB key it should be in %USERPOFILE%\.android and other spots I've read of are C:\Windows\System32\config\systemprofile\.android
In case any of the above fails, since I haven't tested them, the easiest alternative might be to just download a Linux live CD, boot it and do the steps inside. Of course any work is lost when you shut it down. You could also boot it in VM program running on Windows.
Amazing guide, Hypexed! The amount of work you put in to figure this out is incredible.
However, I'm stuck on step 6c, where I'm supposed to save the cfar-cleanup.sh file. It's not letting me save it at all, either within the mount point or to another location, it says that I don't have permissions to save the file. I tried the 'sudo chown' to change ownership to try to edit the permissions, but that didn't work either with it still saying I can't have access to the file. Any ideas? There is probably a simple solution, but this is my first time really using Linux so I'm a noob. I'm using Ubuntu 18.04.1LTS installed, not live, dual-booted with Windows, if that's important to know
SpinningQyarks said:
Amazing guide, Hypexed! The amount of work you put in to figure this out is incredible.
Click to expand...
Click to collapse
Thank you for noticing. It really was the culmination of months of hacking and cracking. Not to mention research. I decided I had to write a guide so I could document what I did in case I needed to do it again. And of course if it helped anyone else.
However, I'm stuck on step 6c, where I'm supposed to save the cfar-cleanup.sh file. It's not letting me save it at all, either within the mount point or to another location, it says that I don't have permissions to save the file. I tried the 'sudo chown' to change ownership to try to edit the permissions, but that didn't work either with it still saying I can't have access to the file. Any ideas? There is probably a simple solution, but this is my first time really using Linux so I'm a noob. I'm using Ubuntu 18.04.1LTS installed, not live, dual-booted with Windows, if that's important to know
Click to expand...
Click to collapse
Sorry you got stuck. I can see some issues in my guide. Especially after trying to do 6c again. First I notice I didn't specify where to store all the folders. Somewhere in the home folder obviously but it looks like you sorted that out fine.
I have tested a working solution to the permissions problem. In fact two:
1. Locate cf folder in the cache mount point on the desktop and go into it. Now right click in the window to bring up the context menu and select "Open as Root". Open up the editor as before.
2.. In the terminal run the editor as root. For example:
sudo gedit cfar-cleanup.sh
I've tested this on Mint which is a "relation" of Ubuntu so should work the same.
Now the original permissions should be left intact. I checked and they didn't have the execute bit set which is unusual. It may help here to save your work on the file to a place you can save to in the meantime. So you don't get stuck again. And then unmount your cache mount point, extract the raw image again as per step 4 and remount as per step 5, if the permissions need restoring. They really should be as they are originally set in the image.
Then continue through to step 6 and beyond as you were.
Good luck!