So I'm booting Honeycomb off SD and all was fine and dandy. I got Market setup and all was well.
Well I decided to get a little adventurous thinking there wasn't much to lose and decided to push the system folder for all the GApps in the Froyo walkthrough. Now my Nook just boot loops, each time displaying an activation screen with LogicPD Zoom2 then immediately rebooting.
I have an idea of what is wrong, its trying to run a Google activation when it boots up, but since its the wrong device is boot looping. What I'm looking for is what apk to take off the SD card and in what directory I would find it to get myself out of this pickle. I'm trying to avoid starting over with the Honeycomb build, but it wouldn't be the end of the world.
So I'm thinking it may be OneTimeInitilizer.apk but am realizing I can't access the partition on the SD card directly from Windows. Any ideas
Edit: I may be able to get adb shell for a few seconds before reboot if that helps, I may be able to queue up the commands necessary and get them off in time.
Edit 2: Tried my (most likely wrong) attempt at the above idea. Created a batch file to mount as rw and then run adb uninstall /system/app/OneTimeInitializer.apk but it never worked. Either gave me Failure or "Error: Could not access the Package Manager. Is the system running?"
Related
I recently aquired a Streak 7 and am having trouble resetting it since it has all the original owners info on it.
1. I encountered a force close error upon first boot.
- android.process.acore stopped unexpectedly
2. After this error continued to appear I said F*** this and rebooted into the Stock Dell recovery(Volume + and Power)
I chose option 3 for a factory reset and erase internal tablet storage.
Rebooted and Bam same bull**** errors. I did this 3 more times powering off with the pin hole off button after the streak kept booting with this error.
I read this entire forum development and general questions to see what problems others are having, I came across a few threads all very informative on how to attempt to restore your Streak 7.
Before attempting the various methods of either NVFlash, the fastboot method and even flashing clockwork recovery through fastboot I figured I would see what I could get the Streak to do in it's current state.
*Note* I am very familiar with ADB and Fastboot but if I over looked something I will not be offended if anyone can provide some useful information.
OK, Here is my story
I put the streak on my HDMI dock and was able to succefully install the ADB drivers on Windows 7 x64. From there I launched the ADB Shell
c:/androidsdk/tools> adb shell
$
once in the shell i found I could launch the android setting using this command
$ am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Once in the settings and periodically hitting forceclose and quit to the .acore error I was able to retrieve this information
Android Version
2.2
Baseband Version
11.809.05.02.00
Kernel version
2.6.32.9
OEM Version
GLUNB1A132433
Build Number
14394
I also realized that I can install apps through adb so I went and installed the latest standalone ADW Launcher which installs fine and allows me to actually use the device a little.
c:\androidsdk\tools>adb install launcher.apk
1307 KB/s (2533717 bytes in 1.892s)
pkg: /data/local/tmp/launcher.apk
Success
You will notice that apps install to this location
/data/local/TMP
it turns out that even installing the new launcher won't allow me to do much because the previose owner changed his google password so I have no market acces or anything like that.
I then tried doing the factory reset within the Android settings>privacy>factory data reset.
The device reboots and I again encounter the same error and the device has also not reset the user data.
So i rooted the device and found that even root was only temporary, the ADB shell returns the # sign indicating that it has root, great but when the device is rebooted it returns to the condition I got it in.
If I run ADB remount with root I get this
c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>
this tells me that even though the phone has root it will not mount any file system with read/write permissions
I then installed the latest free Clockwork Rom Manger via ADB
it prompts me for root permissions I select allow and then the app closes after it downloads and tries to write the clockwork recovery image. I said fine this won't work.
I moved on to the Flashing Clockwork Recovery via Fastboot
In Fastboot I get this
c:\androidsdk\tools>fastboot devices
? fastboot
c:\androidsdk\tools>fastboot -i 0x413C flash recovery clockwork.img
sending 'recovery' (4416 KB)...
OKAY [ 0.560s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.670s
c:\androidsdk\tools>
WOW I didn't know that 4MB could be sent and flashed over usb in under a second!!!! WTF!!!!!
So obviously there is something going on here where I cannot write to the internal memory...
I decided to just use NVFlash because people seem to be having luck with it
http://forum.xda-developers.com/showthread.php?t=1018809
I Didn't.......
I spent a hell of a lot of time downloading and redownloading the different images and finally got them all downloaded successfully. I run the restore.bat file and it says everything went fine but it didn't, I tried NVFlash with and without P14.img and it just doesn't seem to do anything it always restores it to how it was when i got it errors and all.
Now for the best method I tried, the fastboot method by flashing boot_orig.img, recovery_orig.img and system_orig.img
http://forum.xda-developers.com/showthread.php?t=1011654
Flash_image is not and ADB Shell command
and I also don't beleive the images are writing to the disc that fast.
I'm tired of typing now so please if anyone has any info on how I can write information to the internal ROM memory not the internal sd card I would greatly appreciate it.
Tom
wikedbubble said:
I recently aquired a Streak 7 and am having trouble resetting it since it has all the original owners info on it.
1. I encountered a force close error upon first boot.
- android.process.acore stopped unexpectedly
2. After this error continued to appear I said F*** this and rebooted into the Stock Dell recovery(Volume + and Power)
I chose option 3 for a factory reset and erase internal tablet storage.
Rebooted and Bam same bull**** errors. I did this 3 more times powering off with the pin hole off button after the streak kept booting with this error.
I read this entire forum development and general questions to see what problems others are having, I came across a few threads all very informative on how to attempt to restore your Streak 7.
Before attempting the various methods of either NVFlash, the fastboot method and even flashing clockwork recovery through fastboot I figured I would see what I could get the Streak to do in it's current state.
*Note* I am very familiar with ADB and Fastboot but if I over looked something I will not be offended if anyone can provide some useful information.
OK, Here is my story
I put the streak on my HDMI dock and was able to succefully install the ADB drivers on Windows 7 x64. From there I launched the ADB Shell
c:/androidsdk/tools> adb shell
$
once in the shell i found I could launch the android setting using this command
$ am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Once in the settings and periodically hitting forceclose and quit to the .acore error I was able to retrieve this information
Android Version
2.2
Baseband Version
11.809.05.02.00
Kernel version
2.6.32.9
OEM Version
GLUNB1A132433
Build Number
14394
I also realized that I can install apps through adb so I went and installed the latest standalone ADW Launcher which installs fine and allows me to actually use the device a little.
c:\androidsdk\tools>adb install launcher.apk
1307 KB/s (2533717 bytes in 1.892s)
pkg: /data/local/tmp/launcher.apk
Success
You will notice that apps install to this location
/data/local/TMP
it turns out that even installing the new launcher won't allow me to do much because the previose owner changed his google password so I have no market acces or anything like that.
I then tried doing the factory reset within the Android settings>privacy>factory data reset.
The device reboots and I again encounter the same error and the device has also not reset the user data.
So i rooted the device and found that even root was only temporary, the ADB shell returns the # sign indicating that it has root, great but when the device is rebooted it returns to the condition I got it in.
If I run ADB remount with root I get this
c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>
this tells me that even though the phone has root it will not mount any file system with read/write permissions
I then installed the latest free Clockwork Rom Manger via ADB
it prompts me for root permissions I select allow and then the app closes after it downloads and tries to write the clockwork recovery image. I said fine this won't work.
I moved on to the Flashing Clockwork Recovery via Fastboot
In Fastboot I get this
c:\androidsdk\tools>fastboot devices
? fastboot
c:\androidsdk\tools>fastboot -i 0x413C flash recovery clockwork.img
sending 'recovery' (4416 KB)...
OKAY [ 0.560s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.670s
c:\androidsdk\tools>
WOW I didn't know that 4MB could be sent and flashed over usb in under a second!!!! WTF!!!!!
So obviously there is something going on here where I cannot write to the internal memory...
I decided to just use NVFlash because people seem to be having luck with it
http://forum.xda-developers.com/showthread.php?t=1018809
I Didn't.......
I spent a hell of a lot of time downloading and redownloading the different images and finally got them all downloaded successfully. I run the restore.bat file and it says everything went fine but it didn't, I tried NVFlash with and without P14.img and it just doesn't seem to do anything it always restores it to how it was when i got it errors and all.
Now for the best method I tried, the fastboot method by flashing boot_orig.img, recovery_orig.img and system_orig.img
http://forum.xda-developers.com/showthread.php?t=1011654
Flash_image is not and ADB Shell command
and I also don't beleive the images are writing to the disc that fast.
I'm tired of typing now so please if anyone has any info on how I can write information to the internal ROM memory not the internal sd card I would greatly appreciate it.
Tom
Click to expand...
Click to collapse
Bump for a resolution. A lot of folks seem to be encountering this issue; I think it has something to do with a Linux failsafe measure (from another thread), but I'm not savvy enough in Linux to know for sure. Good luck to you!
Hey Thanks for the Bump, I am tearing my hair out over thins thing.
On another note I found this post for the LG GX2 for flashing clockwork recovery through APX with NVFLASH
http://www.techofweb.com/technology/flashing-cwm-recovery-g2x.html
I hope there might be a way to do this on the Streak, but I don't know that much about NVFlash. My hope in getting the clockwork recovery is that the restore and recovery tools used in clockwork recovery will in theory allow me to format and write roms to the internal memory...... I hope
Anyway I hope someone is reading and understanding my trouble other than Z4nd4r
Tom
I've been having similar problems with my streak7. It was working fine on stock 2.2.2 then got stuck in boot loop at the "stick together" screen.
I tried to factory reset in recovery. No change.
I tried to restore with nvflash. It completed fine, but no change.
http://forum.xda-developers.com/showthread.php?t=1018809
I tried with fastboot (boot.img, restore.img and system.img). It completed fine, no change.
I tried the 2.2.2 update.pkg in recovery, but it stops at "install modem error", no change.
I tried to flash DJ_Steve's honeycomb, and it stops at:
Formatting partition 2 BCT please wait... FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) message: nverror:0x2 (0x2) flags: 0
I tried formatting all partitions with:
nvflash --bl bootloader.bin --format_all
then restore with nvflash
It completes with no errors, but still no change.
I also tried to get clockwork on the streak 7 with fastboot. Even though I didn't get any errors, clockwork recovery did not get installed. So I'm thinking it's some sort of write protect error, since nothing I write to the device seems to be sticking.
If I format all partitions, would the streak 7 even get to the t-mobile "stick together" logo? I would think it would get stuck at the dell logo. I'm stuck at this point and have no idea what to try next. Any suggestions?
Could the problem be due to previous owner(s) trying to root the DS7 and Dell had implemented some kind of security measure to prevent rooting of the DS7?
Bump for a real solution.
I found a solution and my solution was to sell it before I threw it against a wall.
What's the common denominator, here? Were these all purchased used/3rd party?
Mine was bought new and ran great till mothers day and my sis asked to use it to post pics to facebook so I unmounted my sd and gave it to her she poped in her 32 gig sd card and got tired of waiting for the the gallery to populate and ejected the card without unmounting it and handed it back to me and said it was junk an and slow .......ever since its been stuck in read only
Ive dissasymbled it formated it flashed it factory reset it and reguardless of what I do still comes back the same as though I hadnt touched it.......even tried to short the nand chip out to clear it..........its like a cockroarch thats wounded .....it just wont finish dieing
I think we need a jtag solution. Doesn't seem like anything done with current tools will help.
I've scoured the internet and turned up nothing.
My streak 7 is collecting dust and probably going on eBay soon. To hell with Dell. This is my first Dell android device and probably my last.
Edit: found information
So I found the datasheet for the NAND chip the Streak 7 uses (http://omapworld.com/iNAND_e_MMC_4_41_IF_data_sheet_v1_0[1].pdf). Aparently the NAND has a write protect feature (temporary and permanent). Tech5 from this thread http://forum.xda-developers.com/showthread.php?t=1113264 says there's a failsafe function that locks the NAND in write protect mode. I don't have the hardware expertise to dig down and see if the system is write protecting the system by locking the chip in write protect mode. If we can somehow figure out how to disable the write protect on the chip, we may have a solution. Maybe someone with good hardware knowledge can take a look and give some feedback?
I'm having this same issue over here. I've tried NVFLASH and Fastboot and it acts like it's happening and then you reboot and get back to the same image every time. Maybe time for a call to Dell on this?
Call Dell
It looks like these Streaks are all stock and having the same problem. I tried calling dell but they wouldn't help me because the streak I got doesn't have the flap for the sd card and that is where they say the Service Tag is written. Freaking BullSh!t. Anyway if someone is willing to call dell and see what they have to say that would be awesome.
Dell is the only solution?
I had a same problem too. No matter what I do, the unit reverts back. It became Read-Only Mode. I guess it happens often enough DELL aware of this problem and the tech supports knows what to do. Only way to fix the unit at this point is ship it back.
I shipped back to Dell and Dell repaired it. Turn Around time: 1 Week.
This is my 1st post.
I do have Streak 5 and 7. I love Streak 5 and DJ Steve's ROM Rocks in Streak 5.
wikedbubble said:
It looks like these Streaks are all stock and having the same problem. I tried calling dell but they wouldn't help me because the streak I got doesn't have the flap for the sd card and that is where they say the Service Tag is written. Freaking BullSh!t. Anyway if someone is willing to call dell and see what they have to say that would be awesome.
Click to expand...
Click to collapse
Settings > About > Status > Service Tag at the bottom.
I'm on the phone with Dell right now about this as I can't find another solution and another user had to get theirs repaired. We'll see what they say.
Solution to write protect?
I was trying to copy some music to mine and got the write protect error message. I took out the micro SD card holder and it indeed was locked. Flipped the switch and back in business! Hope this helps someone!
I wonder if it is newer streaks that are doing this, because I think mine was in stock with Tmobile for a while. They had plenty of them there. They must be "Locking the bootloader" so to speak. If anyone wants to send one to a Dev maybe they can do something about it.
any luck with this any 1? =(
I had a similar issue last week, it looks to be the "Read-Only" Bug. I had to send mine back to Dell, and they just sent me a new unit.
Whatever you do, make sure your DS7 does NOT hit 0% battery, it seems to be the cause of this "Ready-Only" bug.
I used ManualNooter 4-5-18 and then 4-6-16 and then did the permissions fix that they said to do.
Everything worked fine for about 3 days. I went to turn it on it showed the Nook Color logo and froze. Now it won't do anything.
The only thing I can do is boot from SD with ClockWork Mod but it won't read it correctly, can't mount, can restore zip's etc.
Tried to push the Boot.img which seemed to have worked, but when I try to push the System.img it dies with a protocol error and the Nook powers off.
Please please someone tell me they know how to fix this! I can even give access to the machine it's hooked up to and let you have at it!
shieldsit said:
I used ManualNooter 4-5-18 and then 4-6-16 and then did the permissions fix that they said to do.
Everything worked fine for about 3 days. I went to turn it on it showed the Nook Color logo and froze. Now it won't do anything.
The only thing I can do is boot from SD with ClockWork Mod but it won't read it correctly, can't mount, can restore zip's etc.
Tried to push the Boot.img which seemed to have worked, but when I try to push the System.img it dies with a protocol error and the Nook powers off.
Please please someone tell me they know how to fix this! I can even give access to the machine it's hooked up to and let you have at it!
Click to expand...
Click to collapse
I found that the automatic updates in Market screw up the latest manual nooter. Here's how I fixed the problem.
*IMPORTANT* You have to do this before the Market first updates itself resulting in an endless boot cycle. This procedure will unfortunately also stop automatic updates to the Market. However, it also stops the Nook Color going into the endless boot cycle after the first Market update.
1. Wipe the device (8 failed boots) and clean the memory (press and hold n while booting and keeping the power key depressed).
2. Complete the B&N registration process.
3. Upgrade to the latest B&N firmware (I tried 1.2 manually)
4. Use CMW and manual nooter by following this http://forum.xda-developers.com/showthread.php?t=1054027&page=1 to root your Nook Color.
5. Use the Market to download Terminal Emulator (see https://market.android.com/details?id=jackpal.androidterm&hl=en for details)
6. type
$ su -
# pm disable com.android.vending.updater
Check out
http://forum.oxygen.im/viewtopic.php?id=919 for more on this.
You have to do this before the Market first updates itself resulting in an endless boot cycle. This procedure will unfortunately also stop automatic updates to the Market. However, it also stops the Nook Color going into the endless boot cycle after the first Market update.
I'll go through these and see what happens, but I wouldn't call what's happening to mine a boot loop. Nothing shows on the screen at all unless I boot from SD card.
And thank you for replying and trying to help me. I'm lost without my Nook. If I get it working I'm not risking rooting it again.
My screen broke tonight enough to make it unusable, and I was offered in store exchange when I called B&N support. I am running CM7, and would like to know if it is possible to either restore to stock or wipe the hard drive to remove evidence of rooting before I send it back.
I managed to get into adb and read in another thread to try rm -r *, which is supposed to wipe everything, but I got a bunch of read only errors. It appears that the nook will now not boot into CM7 (which is good), but I fear that I haven't wiped it far enough to be safe from a chargeback. Any ADB wizards out there with some advice?
I think I have done it. I opened up a shell in adb, mounted /system as r/w, then did rm -r *. after a reboot it won't even boot into adb anymore. it comes on for about 4 seconds then shuts off immediately. I can't tell what is happening on the screen because of the damage, but i'm hoping it is enough that the folks who check returns at BN can't prove it was rooted.
What are you wanting it to boot into if you just deleted everything in the system partition?
Sent from my HERO200 using XDA App
I think he wanted it to not boot at all in preference to booting into CM7.
I'm pretty sure that if they looked beyond the broken screen they'd be able to determine that you've rooted it: Having no files but still a filesystem on /system is kinda suspicious, and I imagine that having CWM instead of the stock recovery would be something of a giveaway as well.
First of all, many thanks to verygreen, leapinlar, and bobokan for putting together all of the necessary downloads and processes to make this work. I wanted to outline my specific requirements for the HD+ and the process I used to get there.
Requirements: I wanted to run a rooted stock HD+ with some of my apps sideloaded and some of the built-in BN bloatware removed. This last part was very challenging because BN, in their infinite wisdom, have a startup process where it downloads and reinstalls these "golden" apps on a reboot.
Leapinlar's thread contains all of the downloads that you need. The procedure I followed was as follows:
Unplug and charge the tablet and then start it to register with BN and allow it to download firmware 2.1.0.
Ensure that you have ADB setup on your PC and it is able to see the tablet and connect to it. This is a crucial step that will save you hours of work because of reasons that I will specify below. You will need installed and you must follow the ADB install steps precisely as described in LeapinLar's post above. Don't proceed further until you are able to type "adb shell" at a prompt and able to get to the user-mode shell on the tablet. Also, the cable is kind of finicky so you must have it installed firmly in the proprietary BN connector or you will get random disconnect issues.
Using Win32DiskImager burn CWM to a micro-sd card (I used a 2GB).
Copy the Universal Root to the tablet storage or the microsd card. Install the microsd card in the tablet.
(Warning: if you don't follow this tip, depending on the luck of the draw, you can end up wasting hours) Reboot the tablet using "adb reboot". If you cold boot the tablet by shutting it down and restarting it, it will often not detect the microsd card and thus ignore the CWM boot above. I wasted hours trying to rewrite cards, using different cards, using different CWM images, etc. before I stumbled on the tip provided by bobokan where it was indicated that the BN microsd card detection is much more reliable on a warm reboot. From this point on, I only did warm reboots and my card was detected every time. BTW, this is faster too compared to awkwardly holding on to the power button, which only allows a shutdown btw, and then holding it again for a start up.
Once CWM is up and running, clear the cache folder and flush the Dalvik cache. Then burn the root zip above to flash using CWM.
Pull out the microsd card and reboot. You now have a rooted tablet. I was given the choice to pick the Zeem launcher here, which I eagerly did to get away from the stupid bloated BN launcher. (Don't break out the champagne yet - you still have a ways to go if you want a tablet that is relatively free of BN's interference.)
Connect to the tablet using "adb shell" and then type "su". This should get you to a root shell. If not, something went wrong in the above 2 steps. Before type su at the shell prompt, type "echo $LD_LIBRARY_PATH" and copy its value. After typing "su", type "export LD_LIBRARY_PATH=<the value you got previously>". This is necessary in some devices to ensure that "pm" (the package manager) works fine.
Remount the /system filesystem as read-write so you can make changes to get rid of BN malware as follows: "mount -o remount,rw /system".
Go to /system/app and move the following BN packages to some other directory, ideally created in /sdcard, by doing "mv <app> <backup directory>". The apps are:
[*] CloudService.apk[*] Bn*.apk[*] GMS_Maps.apk (optional. I just didn't want the obnoxious Maps app running on my tablet)[*] Home.apk[*] PlusOne.apk
Go to /data/app and move some of the ridiculous uninstallable apps that BN forces on you and re-downloads on reboot even if you uninstall or disable them:
[*] com.astraware.*[*] *.fbwrapper.*[*] *.hulu*[*] *.pandora*[*] *.spotify.*
Warm or cold reboot the device and wait for it to connect to the network. Inspect the Applications tab in settings to ensure that the apps you uninstalled remain uninstalled or disabled. From this point on, any app that you uninstall should remain uninstalled. You can now also use "adb install" to sideload other nice apps in the tablet such as Swype (Play store shows it as incompatible but it works fine), Adaway (but be sure to make sure that the hosts file is stored in data and that you add su.barnesandnoble.com to the blacklist), etc.
Rant to device and app makers: If you think your apps are so great, let people use them voluntarily instead of forcing them on their devices without providing them any opportunity to inspect the privacy policy and permissions. BN in particular was flagrantly bad about this, re-downloading the apps on reboot once connected to the network.
Caveat: I had a session running "adb logcat" to see the app traffic on the tablet and noticed that after uninstalling the Bn garbage, there were some errors being logged complaining about missing cloud services and etc. So obviously there is still some BN malware trying to phone home but I haven't found it.
I am now happy that my tablet runs with just the software I want on it instead of running garbage that someone else forces me to carry on it. YMMV of course.
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!