Managed to get my emmc-bricked i9001 working... somewhat - Galaxy S I9000 Q&A, Help & Troubleshooting

Since I've been mainly a lurker/reader I can't write in the threads involved:
http://forum.xda-developers.com/showthread.php?t=2224029
http://forum.xda-developers.com/showthread.php?t=2233138
http://forum.xda-developers.com/showthread.php?t=2224029&page=15
and finally:
http://forum.xda-developers.com/showthread.php?t=2216996&highlight=userdata+img+ext4
Btw, this is a screenshot of that eMMC test tool and sure enough, I've got the M8G2FA eMMC chip:
I can't get root to work and any app I try to use that require root stall and then make the Holo launcher in Slim-3.1.0-ariesve-20130403-1127-UNOFFICIAL rom (the only one I managed to get working, probably because it writes ALL partitions) drop to main screen an flash the menu window until I click the menu button.
I flashed, reflashed, tried all the "fixes" to no avail, flashed that 1.4GB userdata.img.ext4 file in odin, flashed the TEST KERNEL eMMC Brick Fix, tried replacing the boot.img in the slim package with the eMMC boot after repartitioning my external SD etc... Thing is, I tried them in so many different ways that I can't say exactly what the right procedure is and I'm not going to risk a reflash now that I've got it going until someone have a more permanent fix.
If a dev want me to do adb tests, scripts, get logs etc. just PM me and I'll supply you with what you want. I'm not all that proficient in adb usage but I learnt a thing or two when I bricked my Desire.
It is frustrating to not have a functioning Superuser/SuperSU/Rooted OS (tried flashing Root-i9001-Signed.zip among other things which does nothing) but I guess that's the price I have to pay for flashing a 3.x based CWM's without knowing about eMMC brick bugs and crap. Right now I'm running an OS with the eMMC fixed (used External SD instead of eMMC I believe) Linux kernel 3.0.70 since it's the only one I got working (albeit with a few random reboots here and there when I use the android debug bridge). Starting normal apps is quick and JB is blazing fast though. Can't change any system settings in Holo launcher (since they require root) so I edited the build.prop with the excellent adb-plugin for total commander (which I use almost exclusively to access my phone)
Good news is that it works as an unrooted phone.. Wifi, phone, e-mails etc. all work. So I'll be content for now since last night I thought I had a graveyard bricked phone I bought second hand for $95 5 days ago, esp. after bricking my Desire which made me buy this one.
Of course, Slim comes with a bunch of scripts in the init.d folder that may make things less stable/slower since I (think) I'm running my 8GB Class 10 MicroSDHC as the Internal and vice versa with that kernel fix.
I copied the logcat.txt and debuglog.txt and zipped them for anybody interested: http://www.megafileupload.com/en/file/411145/Logs-zip.html

Hi Scyphe,
I understand you do not remember the exact procedure you used but could you give me some help understanding how the "normal" procedure should work? I read all posts you linked, I've tried, but I still can't get what I'm doing wrong... What are the basic steps that are needed make it work with data on SD?

Related

How to run apps from SD w/ DRC83 rooted and Windows?

(That should be DRC83, I *swore* I changed that)
I successfully rooted my phone following the tutorial, although at some points I took a vague leap of faith; there are some very minor things that are not included in the tutorial. I suspect part of this is to rule out people (like me) who have zero *nix experience, but it can be alarming.
I was unable to get the most recent (as of today) Cyanogen mod to work (1), so I downloaded DRC83. (I do still have root).
I *have* searched the forum, and I have searched Google. My problem is that a great deal of what I'm finding is dated, requires hardware I don't have (a machine running *nix) or software I don't have [Cyanogen, crutch lite (which is no longer on the market)].
When I try to get into console mode, it doesn't work. (2)
Is there any way for me to run my apps from my SD card using a Windows machine and DRC83? I've gotten to the point now where I no longer trust my searching abilities.
I have:
T-mobile G1 bronze
A new 8 GB class 6 MicroSD card
AppManager (not Apps2SD? Where is this program?)
Build DRC83
sdparted.txt (on the MicroSD)
Kernel: 2.6.29-00479-g3c7df37 [email protected] #19
Windows OSs on desktops
A MicroSD reader (so I can theoretically do anything except booting the phone from the PC)
(1) - When I downloaded/installed this build, it would just stay on the G1 screen.
(2) - I can successfully power on the phone holding the home and power, but then I just get the exclamation point. Holding alt-x or tapping them and hitting return isn't doing anything.
The guide here http://forum.xda-developers.com/showthread.php?t=535232 references Cyanogen 4.0.2 which isn't even at that link.
I apologize, I know y'all go over this all the time, but I really did search and my google-fu is failing me.
not sure i fully understand ur problem but if u have cm 1.4 recovery or amon ra recovery (do u?) u should just follow this guide http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs
u shud be good to go afterwards. hope this helps at all
Depending on what guide you followed it should be step by step. This is the best guide out. http://androidoverdrive.com/viewtopic.php?f=11&t=7. And as long as your card is partitioned then apps2sd is automatic and you don't have to do anything.
I tried that, and it worked really well, but I just can't get Cyanogen to run on my phone for some reason.
I got all the way through flashing that image, but all that happens after that is the screen goes black.
Thanks, though.
:-/
Anyone else have any ideas how I can run my apps from my SD without running a ROM that just won't run on my phone for some reason?
Hate to break it to you, but Cyanogen's ROM is *not* the only ROM that supports Apps2SD. Almost all the ROMs you'll find the in the development section support loading apps from the ext partition by default. If Cyan's ROM doesn't work, have a look at Dwangs or Enomthers.
The ext partition can be created any way you like, using Amon RA's recovery, or on your PC using Paragon Partition Manager (although I'd highly recommend gparted from a live Ubuntu CD).
AdrianK: thank you; I will try that!
Everyone else: I did eventually get Cyanogen's newest mod to work. I swear I ran through the set-up like six times. >.<

RECOVERY ROM Flash… thru USB from PC ?? (no SD)

I wound up with a non functioning SD card reader after downgrading to dreaIMG. I managed to get a USB connection, after much, fuss to my PC. I am running a program (Droid Explorer) on my P.C. which, among it’s many functions, appears to allow you to upgrade your ROM and install programs from its PC UI. any body gone this route? Would you recommend ?
NOTE: I messed with the SD and usb connection for days, new SD cards, reformatting them every which way, and fiddled with the setup on the android (once registered). I suspect the ROM was corrupt and recover process might just fix it. If it dosn't’t I certainly want to finish the whole process anyway.
The keyboard is the size of my shaky thumbs, I’m dyslexic, far sighted and can only hunt and peck on a regular keyboard. There is absolutely no way I could blindly pump the arcane commands I’ve seen around that might let me finish. (I tried typing “am start -a android.intent.action.MAIN -n com.android.settings/.Settings” 21 times and never got it right)
So, if some one can confirm this USB to PC flash is a valid method (DroidExplorer or other), I guess It would just be like using the PC as a gigantic SD card, I would be jazzed. Right now, cant’ use the keyboard, and can’t use the SD, I see no other way to finish the job. (unless I could install a command prompt thing on the phone to see what I’m doing…still no SD.
Thanks in advance
\PK
Questions in general belong in the Q&A forum, not the Development forum. Questions regarding Droid Explorer, being an app, belong in the Apps forum.
Repost there and you'll likely get help. Here, you're likely to get flamed.
You can definitely flash images directly to the device (without use of the SD card), however, you cannot use update packages, but instead images. You will need separate recovery, boot and system images, and either apply them with the flash_image tool through adb, or through fastboot.
The flash_image route is going to be a bit difficult, since you need to have enough room on the internal RAM to keep a copy of the image you are flashing. (Perhaps you can overwrite the existing backup version ...)
In either case, this is not the best forum to be posting these questions. Obviously, you best course would have been in the Q&A (rather self-explanatory), or as another posted recommended, under Apps.
[Removed as duplicate]
Now that this post has been moved to Q&A: To the OP --
Have you tried issuing the "mount" command via console while in recovery? I.e.;
Code:
#mount /sdcard
I've had it come up where the /sdcard itself wasn't mounting properly.
Otherwise you're stuck flashing a full .NBH file via Fastboot, insofar as I am aware.
IConrad01 said:
Questions in general belong in the Q&A forum, not the Development forum. Questions regarding Droid Explorer, being an app, belong in the Apps forum.
Repost there and you'll likely get help. Here, you're likely to get flamed.
Click to expand...
Click to collapse
Sorry, I've been obssed and frutrated for 3 days/ Total lack of responce here (Q&A) and elswhere. I did a new search and everything resembling my issue was wherever my origional post was on xda, not Q&A.
Any way, I'll stay away. pk
rpcameron said:
You can definitely flash images directly to the device (without use of the SD card), however, you cannot use update packages, but instead images. You will need separate recovery, boot and system images, and either apply them with the flash_image tool through adb, or through fastboot.
The flash_image route is going to be a bit difficult, since you need to have enough room on the internal RAM to keep a copy of the image you are flashing. (Perhaps you can overwrite the existing backup version ...)
In either case, this is not the best forum to be posting these questions. Obviously, you best course would have been in the Q&A (rather self-explanatory), or as another posted recommended, under Apps.
Click to expand...
Click to collapse
I appreciate your reply very informative
1)if I reconstruct a zip file and get 3 or4 bin or img files, how do I determine which goes first?
2) Do they need to be renamed? if so, to what?
3) "The flash_image route is going to be a bit difficult" . so your saying that my P.C will not be behaving like an SD card? but just a dump truck?
4)n Sorry for crashing the party. I bought this thing on Ebay 4 days ago "for parts" and knew zip about it. I Posted several times in the Q&A section and pretty much got "format SD to fat 32"...Very well meaning but page one of every g1 how to.
Without bugging you guys, I know I'm a noob, but in 3 days I took this 50 buck T-mobile with no usb, no wifi, no bluetooth, no-way to input through the keyboard, no SD and, nothing on the screen but a 3 page sign up sheet for to google...to a functioning AT&T phone with most of the perks working.
I just want to finish the job, I think with a proper flash, the remaining probs. might go away. All I was looking for was a morsel of direction, not "format fat32", and you gave it!!
Thank you, PK
IConrad01 said:
Now that this post has been moved to Q&A: To the OP --
Have you tried issuing the "mount" command via console while in recovery? I.e.;
Code:
#mount /sdcard
I've had it come up where the /sdcard itself wasn't mounting properly.
Otherwise you're stuck flashing a full .NBH file via Fastboot, insofar as I am aware.
Click to expand...
Click to collapse
Thanks Ico...,
Yes, I have now. No luck. I resigned to the fact that I will have to install from my PC... for now. I tried out this little utility, Droid Explorer. It is the exactly what I think an interface should be. It's takes al these monstrous tasks an packs them m into a little windows type app. But, you have to heave a ROCK-SOLID connection.
I just have to think I had a bum DreaIMG rom. it loaded up from my SD card and installed swimmingly with a cheery concluding "SUCCESSFULLY INSTALLED!!". After that the card(s) were never to be recognized again. I wonder if I could Just get a normal usb-to-mini usb adapter and plug a thumb drive in, install of that.
Last night I got it to be recognized by my PC a little better, but, I still can't really transfer anything. (I also managed to inadvertently run up $208.00 in "data fees"...no bloody clue").
I've been following a different wiki every day. It seems as though most of them are outdated by a week or so (history). I think my problem lies in usb drivers because installations seems always seem inconclusive as to weather there there or not and adb seems to misbehave.
Chow

[Q] Can not ADB my device?!

I have a Verizon Galaxy Tab 7 (SCH-I800) and I can not link up to it in ADB.
I have installed the Android Development Kit, Samsung drivers, and downloaded CM10.1.
I was able to contact the tablet in command prompt through heimdall and push clockworkmod recovery.
I'm following this guide:
http://rootzwiki.com/topic/33743-ext...rd-only-guide/
I've removed the internal memory card.
I've modified the update.sh file and rezipped everything.
I just need to know WHY adb cannot find my device. When I type "adb devices" in the command line NOTHING shows up. I've tried reinstalling the samsung driver, reinstalling the driver that came with heimdall, and updating the samsung driver via windows update.
By the way, this device would bootloop at the verizon loading screen, could not be updated, and could not load its original android OS, therefore I cannot turn on debugging or anything like that. Alls I can do is access the "PC connection" yellow screen and the CWM bootloader I pushed with Heimdall.
By "Internal" Memory ya meant "External" Memory right? as the Internal Memory is the 16GB Flash ROM.
In any case all pedantry aside. Did you remember to check the USB Debug Setting?
I think you can find this under the Wi-Fi Settings (On the Samsung Stock ROMs), IIRC it should be near the "Samsung Kies / Media Player / USB Storage" Settings. On CM10 Builds you'll find it in the "Developer Settings" near the bottom of the List.
Pretty sure you have to check this "Flag" before you can use ADB on your Device...
In that case consider yourself bricked!
In this case I'd recommend you find the Overcome Recovery Package: HERE
Install such Driver that you may need, then fire up Odin3 v1.7
Then set your Device into Download Mode (e.g. Hold Volume Rocker down + Power till you enter the Download Mode Screen)
Pit -> gt-p1000_mr.pit
PDA -> GB_Stock_Safe_v5.tar
Phone -> modem.bin**
Most People would just use the XXJPZ (GSM modem.bin), here but, since you have a CDMA Phablet, you'll have to find and pick the correct modem.bin File that is the best match for your CDMA Device. This is also likely why your now soft-bricked.
Hopefully after all this rigamarole you'll land up on a Stock, non-branded Samsung Gingerbread 2.3.3 ROM.
To which I would just download This, and that should give you Root.
Without all that tedious mucking about with ADB.
The internal chip has failed. I cannot boot the device whatsoever. I removed it as the link states. Therefore i cannot check off debug mode on the tablet. I will try your suggested method and report back
Don't look at Overcome method if you have a CDMA tab.
It will only brick your tab if it ever worked at all.
Regarding bad internal memory, there are two chips. The OneNand 512MB and the MoviNAND 16GB.
If your OneNAND is the one broken, removing the MoviNAND achieved nothing.
The bootloader, modem, (and is it /system too of stock rom?) sits on OneNAND.
If you look at the link I posted, my tablet was doing the same exact thing as pictured in the link. Saying it could not mount any files or anything. No matter what I did, it would just get to the verizon loading screen and keep flashing "verizon".
I haven't tried the "overcome" method as it didn't really seem like it'd work.
I want to ADB my device to push the new ROM to it. I've already formatted the SDcard as suggested in the guide. Since clearly no one is clicking the link and reading the guide, I'll post it:
Summary:
- Open up the device and take internal SD Card out.
- Re-assemble the device.
- Partition the external SD Card (3 partitions, two small ext4 and one big FAT32)
- Modify ICS or later ROM's update.sh to use partition 3 as external SD Card.
- Flash modded ROM via CWM (and Google Apps optional).
- Enjoy
Taking it appart:
Don't panic!, if you can use a screwdriver and build with Legos you are qualified to do this!
iFixit does a wonderful job of showcasing how to open the device up that I rather link to them than try to out-do them.
Follow their guide until step 13 then refer back to this guide. http://www.ifixit.co...Teardown/4103/1
Posted Image
To actually remove the Internal SD Card (that is not soldered to the board but in-fact glued to it), I recommend you take an exacto knife (or other small blade or thin screwdriver) and slide it around the edges gently; once the edges are loose, take your screwdriver under the chip and just pop it up.
Posted Image
There will be adhesive residue on the board, I recommend using some gentle solvent to remove it (I used a cloth with a little paint thinner).
Put everything back together (just follow the iFixit guide on reverse) and feel proud that you are done with the hardware mod.
Partition your external SD Card
I used three partitions (all primary, not logical) , two 500 MB ext4 and a FAT32 with the rest of the space.
Linux users will probably not require much help on deciding what software to use, but for Windows users MiniTool Partition Wizard does a good enough job.
Do note that your device will perform according to your external SD Card, so it's not a bad idea to invest in a category 10 SD Card.
Modifing the ROM:
Download your ICS / JB ROM of choice, unzip it and open update.sh
Edit both line 31 and 35 to be as bellow
SD_PART='/dev/block/mmcblk0p3'Save and zip back.
Loading the Modded ROM to the SD:
Because we messed with the SD Cards, CWM will have a bit of trouble finding the external SD Card (until we flash our ROM).
Go ahead and connect your device to your computer and ADB the following command:
adb shell "echo /dev/block/mmcblk0p3 > /sys/devices/platform/usb_mass_storage/lun0/file"
That will allow you to access your SD Card from your PC, just copy your modded ROM to it.
Now, issude the following command:
adb shell mount /dev/block/mmcblk0p3 /sdcard
This will allow you to install the .zip file from CWM, go ahead and do that.
After checking partition types, your device will reboot and appear on a countdown to find the external SD Card, go ahead and reboot it manually before it does automatically (reboot to recovery with volume up).
Flash the .zip again, this time the installation will go successfully and you will have a working device.
Optionally, flash your desired Google Apps.
Now if we could get back to my original question, does anyone know why this device will not allow me to ADB it even when it's in download mode (a.k.a volume down/power button)
I actually got my tablet to boot up this morning for about 1 minute, then it shut off for no reason and did the "verizon" flash again when restarted.
priyana said:
Don't look at Overcome method if you have a CDMA tab.
It will only brick your tab if it ever worked at all.
Regarding bad internal memory, there are two chips. The OneNand 512MB and the MoviNAND 16GB.
If your OneNAND is the one broken, removing the MoviNAND achieved nothing.
The bootloader, modem, (and is it /system too of stock rom?) sits on OneNAND.
Click to expand...
Click to collapse
Please correct my but, what other then the modem.bin File could brick such a CDMA Device?
AFAIK as long as he picks the correct CDMA modem.bin it should work alright?
In the case that I am in error, then how does One recover such a CDMA Device then?
I can easily recover this device if I can get the ADB commands to start working. I feel like no one is reading the instructions. If you look at the link where the instructions are, there is a screenshot of his device. All of that "unable to mount" etc is what was happening to my device, hence why I removed the failed chip.
If I could get my device to show up in ADB, I wouldn't be asking this question!
By the way, I'm on an HP DV6. I tried all this in windows 8 and got nothing, so I installed a backup hard drive and put windows 7 on (this is what I'm on now) to see if that'd make a difference. Still nothing. I also tried on my old Gateway desktop but in download mode my old PC (still USB 1.1 1GHz celeron 512mb ram) the PC has no clue what the tablet is.
So I finally got this thing to boot into 2.2. Now the touch screen is unresponsive and the battery goes to 0 as soon as it's unplugged. Going to take it apart in the morning and make sure everythings connected. Might try a new battery but if this thing doesn't show more promising results soon I'm going to just say screw it and get rid of it.
Edit: Touch screen works but is flipped. If I slide my finger side to side nothing happens. If I slide it up and down i can awkwardly unlock the device. I'm guessing reload the factory image?!
the CDMA device is of different hardware. Not just the modem.
I am not technical enough to explain the difference. But I know Overcome method will brick it.
EliteEmerz: can you at least share how you get the PC to detect your device again?
priyana said:
the CDMA device is of different hardware. Not just the modem.
I am not technical enough to explain the difference. But I know Overcome method will brick it.
EliteEmerz: can you at least share how you get the PC to detect your device again?
Click to expand...
Click to collapse
If you put it into download mode it shows right up in my device list, drivers for "samsung USB device" load up. I can contact the tablet through heimdall to load bootloaders, images, etc.
For some reason I got it working pretty good last night except the touch screen issue. I reloaded the stock rom again and am playing with the SD card partitions since that's how I got it to boot up the last 2 times. I dont even care if I can load Jellybean on, I just want a working tablet.
By the way, this is SOLVED.
It will now boot up using a Stock ROM plus the zImage + recovery from clockworkmod
My touch screen is flipped (so I have to slide up and down to get it to swipe side to side) but at least it's on now. Made a new thread to address the flipped touch screen issue!!

[Q] Questions about Nook HD+

So I just got my Nook HD+ and I've made a stock backup using CWM and have CM11 installed on an SD card but I have a few questions:
1. Is it possible to dual boot on the EMMC?
2. Are there any 'must have' tweaks/hacks/apps (root only, besides e.g. backup software)?
3. Is there a way to remove some restrictions on stock e.g. third party keyboard, install any APK without sideloading, etc.?
4. Is there a way to get the screencast software for CM11 without Google+?
I have tried google but the results I got were old or irrelevant (unless I worded it wrong).
Right now the emmc is not rooted, but I am willing to and I've seen the relevant topic.
Thank you.
tech3475 said:
I have a few questions:
1. Is it possible to dual boot on the EMMC?
2. Are there any 'must have' tweaks/hacks/apps (root only, besides e.g. backup software)?
3. Is there a way to remove some restrictions on stock e.g. third party keyboard, install any APK without sideloading, etc.?
4. Is there a way to get the screencast software for CM11 without Google+?
I have tried google but the results I got were old or irrelevant (unless I worded it wrong).
Right now the emmc is not rooted, but I am willing to and I've seen the relevant topic.
Thank you.
Click to expand...
Click to collapse
There are a number of threads that should be helpful to you:
Dual boot. I don't know if anyone has developed a double boot from EMMC (like what, say SafeStrap can do on a Galaxy S4 - assuming that is what you mean). However, if you look at this thread: http://forum.xda-developers.com/showthread.php?t=2330083 and this one: http://forum.xda-developers.com/showthread.php?p=42295360 you'll see that you can set up a dual boot on the HD+ with Stock on the SD card and CM on EMMC
Tweaks, and restrictions on apps - check out the work of leapinlar, from this thread: http://forum.xda-developers.com/showthread.php?t=2062613
See item 3 in the original post for info on enabling installation from "unknown sources" on stock.
Besides a backup app (Titanium), the other useful utility would be something like ES File Explorer, which I use on both my Nook Tablet (stock, rooted) and my HD+ (CM 10.2)
Hope this helps . . . sorry I can't add anything about screencast
ttablet said:
There are a number of threads that should be helpful to you:
Dual boot. I don't know if anyone has developed a double boot from EMMC (like what, say SafeStrap can do on a Galaxy S4 - assuming that is what you mean). However, if you look at this thread: http://forum.xda-developers.com/showthread.php?t=2330083 and this one: http://forum.xda-developers.com/showthread.php?p=42295360 you'll see that you can set up a dual boot on the HD+ with Stock on the SD card and CM on EMMC
Tweaks, and restrictions on apps - check out the work of leapinlar, from this thread: http://forum.xda-developers.com/showthread.php?t=2062613
See item 3 in the original post for info on enabling installation from "unknown sources" on stock.
Besides a backup app (Titanium), the other useful utility would be something like ES File Explorer, which I use on both my Nook Tablet (stock, rooted) and my HD+ (CM 10.2)
Hope this helps . . . sorry I can't add anything about screencast
Click to expand...
Click to collapse
Thanks, I have a few days off work so I'll start messing around (main reason I like this over my A2109).
The boot stock from SD will be useful, I want CM as my main OS but want access to Stock for the odd occasion which was why I was wondering over dual boot but CM on the EMMC to prevent wear and in theory faster speeds.
So I managed to try it out yesterday and I have a couple more questions:
1. What is the best version of CM at the moment? I tried stable 10.1 from the CM site but BT gave me problems, I'm currently on CM11 nightly but obviously that can have issues (I think screen accuracy if off but that could be me) and I'm not sure if my battery has gotten worse since I installed it.
2. Is Titanium more reliable than mybackup? I got a free pro license for the latter but with at least one app it didn't restore properly and I had to do it manually.
tech3475 said:
So I managed to try it out yesterday and I have a couple more questions:
1. What is the best version of CM at the moment? I tried stable 10.1 from the CM site but BT gave me problems, I'm currently on CM11 nightly but obviously that can have issues (I think screen accuracy if off but that could be me) and I'm not sure if my battery has gotten worse since I installed it.
2. Is Titanium more reliable than mybackup? I got a free pro license for the latter but with at least one app it didn't restore properly and I had to do it manually.
Click to expand...
Click to collapse
The "best" version of CM is a matter of preference and opinion. Running 10.1.3 stable (Sept 23 build) I haven't seen any problems with Bluetooth. On the other hand, the only BT device I've used is a GPS receiver that works without any problems. I'd say that for right now, 10.1.3 seems to be the most stable, with the fewest problems. At some point I'll probably move to CM 11, but for now there doesn't seem to me to be a compelling reason.
As for backup, Titanium seems to be what most people recommend . . . I've been using it on my S4, Nook Tablet, and the HD+ and have been very happy. On the other hand, mybackup looks pretty interesting, probably worth trying, especially since you have a freebie
ttablet said:
The "best" version of CM is a matter of preference and opinion. Running 10.1.3 stable (Sept 23 build) I haven't seen any problems with Bluetooth. On the other hand, the only BT device I've used is a GPS receiver that works without any problems. I'd say that for right now, 10.1.3 seems to be the most stable, with the fewest problems. At some point I'll probably move to CM 11, but for now there doesn't seem to me to be a compelling reason.
As for backup, Titanium seems to be what most people recommend . . . I've been using it on my S4, Nook Tablet, and the HD+ and have been very happy. On the other hand, mybackup looks pretty interesting, probably worth trying, especially since you have a freebie
Click to expand...
Click to collapse
The BT bug was that I was having trouble pairing with my other tablet in fact I wasn't sure if it was permanently discoverable.
I had tried mybackup but it's unreliable (ended up manually transferring something) so I can't recommend it.
I've had another issue come up.
On my nook's ext-SD card I currently have 4 partitions:
1. Boot (about 128MB)
2. Stock ROM (about 1GB)
3. Stock ROM Data (I think? about 4GB)
4. Storage (about 50GB)
Currently my Nook will automatically mount the first partition but I want the fourth partition mounted either as well or instead on boot.
Is there anything I can try?
So far I've tried having a large 'boot' partition instead of '4' but it then doesn't boot off the card.
UPDATE: I think I may have a kludge to get a secondary partition to mount instead so I'll post this guide for anyone interested although I've since reformatted the card so the layout is slightly different (this guide is based on there being two partitions but it should work with more).
It's very hacky and could be cleaned up/enhanced (or better yet replaced) but this is beyond my current knowledge.
This guide is based on two different sources and I just modified where necessary and involves an init.d script to unmount and remount the partition I want. In theory this could allow multiple partitions to be mounted but it's untested by me.
Part 1 (init.d script):
The script does the following:
1. Unmount the current ext_sdcard/sdcard1
2. Mount the second partition as ext_sdcard/sdcard1
3. Run the media scanner for said card
First step is to create the script, here is my example:
#!/system/bin/sh
sleep 2
umount /storage/sdcard1
mount -t vfat -o umask=0000 /dev/block/vold/179:26 /storage/sdcard1
am broadcast -a android.intent.action.MEDIA_MOUNTED -d file:///mnt/sdcard1
Click to expand...
Click to collapse
The part "179.26" was derived by using the program "Android System Info" where I identified the partition already mounted (179.25) and guessed it was the next increment.
I then saved it as "11sd_remount" and placed this in the /etc/init.d/ folder using a file explorer (remember to give it root permissions and mount /system as rw) and then changed the permission to 755 using the terminal commands "su" and "chmod 755 /etc/init.d/11sd_remount".
If you have init.d support in theory this should be enough, unfortunately my CM11 rom doesn't so I had to try alternative methods trying "init.d trigger" and "universal init.d" which somehow seems to work.
In my case there are the following issues:
1. Delay after boot for it to mount the partition
2. You need to replug in USB
3. Another delay for the media scanner
Overall a few minutes from when you get to the home screen.
Two alternatives I can think of apparently involve editing fstab (which I think I read is now located in boot.img) or maybe mounting the extra partition as a different folder but I don't know how to get it mounted for accessing on a computer.
Sources:
Init.d script based on: http://forum.xda-developers.com/showpost.php?p=45340859&postcount=3
Android media scanner terminal command: external site (not sure if I'm allowed to post the link).
Running 10.1.3 stable (Sept 23 build); it seems to be the optimal for me. I did install 10.2 few days ago but found performance noticeably sluggish compare to what I was used to on 10.1 so I went back.
No bugs that I could report for 10.2; just speed in my case. Hope that helps.
ds18s20 said:
Running 10.1.3 stable (Sept 23 build); it seems to be the optimal for me. I did install 10.2 few days ago but found performance noticeably sluggish compare to what I was used to on 10.1 so I went back.
No bugs that I could report for 10.2; just speed in my case. Hope that helps.
Click to expand...
Click to collapse
Sorry for the late response.
Thank you I might give 10.1 another go since 11 is giving me wifi issues.

Nook HD+ cannot change persistent state from recovery / rootkit?

Hi,
I have a Nook HD+ which i run with CM13 (cm_ovation-ota-MOB30D.160422) and I've run now into a bizarre problem:
Last week, suddenly the nook started over night to get into an infinite reboot cycle where it goes throught nook start up screen, then cyanogemod universal boot loader screen followed by the pulsing cyanogemod logo. Sometimes it gets to the login screen, sometimes it reboots before but never did i manage to log in.
Trying to restore now older nandroid backups and/or flashing different ROMs and they all fail as they cannot properly update /system (restore fails as it fills up the filesystem even though i haven't resized /system and it definitely was not full at the time of backup; flashing ROM fails as it complains that after update /system did contain unexpected content.
Starting to tinkering with adb shell, i notice that any changes, e.g., adding or removing files, i do on the internal storage (be it /data or /system) seems to be reflected by ls in the same mount cycle but as soon as i umount and remount the device the state is restored to the old state! Similarly, any mkfs.* run without error on the various /dev/block/mmcblk0p* but nothing really changed if i remount the same device after that (i.e., content is not wiped and filesystem type is still what it was before). [the same happens if i try the various wipes/factory reset options in the recovery. No error but no effect].
Note this all happened regardless of recovery (CWM 6.0.4.6 / TWRP 2.8.7.5; the former via external sdcard, the latter internal to the nook). Also strangely, as i boot "normally" (and end up in the boot cycle) i can't run adb logcat as the device is listed as 'unauthorized'. Also for some operations with CWM it warns me at the end that ''root access possibly lost' and asks me whether i want to fix /system/xbin/su) [but either option i choose doesn't change the noticeable behaviour]. Lastly, the whole boot cycles and actions in recovery are very sluggish.
This almost sounds like there is a rootkit on the nook which masquerades the changes but ignores them to stay in control. However, googling i didn't immediately found any hits referring to such a rather sophisticated rootkit.
Did anybody ever see such a behaviour and/or have an idea what's happening? Any thoughts to reset the whole device?
-michael-
PS: Strike-out above part about unauthorized device for logcat: i was trying to do logcat from a device which apparently i've never used before for the nook; doing it on another one which i've previously used allowed for logcat to work but the log itself didn't really give any insights and the adb logcat died a few seconds before the nook rebooted, so i don't have any of these criticial parts of the log ...
Certain models of the HD+ have been known to develop a read only internal memory. It acts like it is being written to but it does not actually happen. When that happens it is not repairable.
Sent from my SM-T707V using XDA Premium HD app
leapinlar said:
Certain models of the HD+ have been known to develop a read only internal memory. It acts like it is being written to but it does not actually happen. When that happens it is not repairable.
Click to expand...
Click to collapse
Hi Leapinlar,
thanks for your feedback: Rather surprising (& unfortunate) behaviour but still better than a rootkit
I guess so my option are only to install/boot CM from an sdcard (or getting a new device)?
-michael-
BTW: to run CM from sdcard i guess i need a no-emmc ROM (even though my emmc still works read-only and i can boot recovery from it)? If so, the latest one i found is https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/ which is rather dated. Is there anywhere a new one or some pointers one what all has to be changed to make a emmc ROM turn into a no-emmc ROM so i could try changing a ROM myself? Thanks!

Categories

Resources