HD+ Bootlop [can't mount /data]

[spinorog]

Hello, I need help! I'm new at xda, so maybe it's wrong to create a new thread, so I'm sorry for that.

Problem appeared afer i decided to reinstall Cyanogen by verygreen. From cwm(mounts&storage) I've occasionally formatted /rom and some other things. :crying: So after installig cyanogen nook boots into cwm and withot sdcard it gets into bootloop. Then i tried other way. From http://forum.xda-developers.com/showthread.php?t=2062613 I downloaded another CWM and installed from it NookHDplus-factory-2.0.0-rooted.zip. Thought it would help. Not at all. But when i formatted data i noticed, that cwm tell about that it can't mount /data... I don't know what to think.

Please help me!

 

[leapinlar]

Hello, I need help! I'm new at xda, so maybe it's wrong to create a new thread, so I'm sorry for that.

Problem appeared afer i decided to reinstall Cyanogen by verygreen. From cwm(mounts&storage) I've occasionally formatted /rom and some other things. :crying: So after installig cyanogen nook boots into cwm and withot sdcard it gets into bootloop. Then i tried other way. From http://forum.xda-developers.com/showthread.php?t=2062613 I downloaded another CWM and installed from it NookHDplus-factory-2.0.0-rooted.zip. Thought it would help. Not at all. But when i formatted data i noticed, that cwm tell about that it can't mount /data... I don't know what to think.

Please help me!

If you formatted /rom AND /factory you are in a big hurt. Those partitions contain vital information that cannot be retrieved. Best to return it to B&N under warranty.

Sent from my HD+ rooted stock using Tapatalk

 

[spinorog]

If you formatted /rom AND /factory you are in a big hurt. Those partitions contain vital information that cannot be retrieved. Best to return it to B&N under warranty.

Sent from my HD+ rooted stock using Tapatalk

Thanks for reply!

Can't quite remember wether i've formatted factory... But chance is big...What if i've formatted only /rom is there easy way? But if both of them were formatted could there be another solution because i'm in Russia and sending it to B&N is problematic... I thought it is possible to restore from someone's backup...

 

[leapinlar]

Thanks for reply!

Can't quite remember wether i've formatted factory... But chance is big...What if i've formatted only /rom is there easy way? But if both of them were formatted could there be another solution because i'm in Russia and sending it to B&N is problematic... I thought it is possible to restore from someone's backup...

If you did not format /factory then it is recoverable. But it should repair itself if you hadn't. You can fix /rom so that you can boot to SD but booting to internal may be history. Mount /rom (p5) with CWM and use adb to create a folder there named /devconf. Then put a simple text file there named DeviceID. In that file put your 16 digit serial number. Then hopefully you can boot to SD.

Sent from my HD+ rooted stock using Tapatalk

 

[spinorog]

If you did not format /factory then it is recoverable. But it should repair itself if you hadn't. You can fix /rom so that you can boot to SD but booting to internal may be history. Mount /rom (p5) with CWM and use adb to create a folder there named /devconf. Then put a simple text file there named DeviceID. In that file put your 16 digit serial number. Then hopefully you can boot to SD.

Sent from my HD+ rooted stock using Tapatalk

Light of hope appeared, thanks!

A little stupid question. Is format via mount&storage clears only of table of contents? May be there is a way to recover these files so far?

Well what i've tried to do:
using adb i mounted /rom and pulled all from there:

C:\adb>adb pull /rom /rom
pull: building file list...
pull: /rom/devconf/hdcp.keys -> /rom/devconf/hdcp.ke
pull: /rom/devconf/WVKeybox -> /rom/devconf/WVKeybox
pull: /rom/devconf/PublicKey -> /rom/devconf/PublicK
pull: /rom/devconf/HashOfPrivateKey -> /rom/devconf/
pull: /rom/devconf/EventType -> /rom/devconf/EventTy
pull: /rom/devconf/DeviceAttribute -> /rom/devconf/D
pull: /rom/devconf/DateManufactured -> /rom/devconf/
pull: /rom/devconf/OperatingMode -> /rom/devconf/Ope
pull: /rom/devconf/ModelNumber -> /rom/devconf/Model
pull: /rom/devconf/EAN -> /rom/devconf/EAN
pull: /rom/devconf/ProductID -> /rom/devconf/Product
pull: /rom/devconf/Bq275020Dffs -> /rom/devconf/Bq27
pull: /rom/devconf/BatteryType -> /rom/devconf/Batte
pull: /rom/devconf/WiFiBackupCalibration -> /rom/dev
pull: /rom/devconf/MACAddress -> /rom/devconf/MACAdd
pull: /rom/devconf/MainBoardSN -> /rom/devconf/MainB
pull: /rom/devconf/SerialNumber -> /rom/devconf/Seri
pull: /rom/devconf/DisplayVendor -> /rom/devconf/Dis
pull: /rom/devconf/DeviceID -> /rom/devconf/DeviceID

Then the same with /factory:

C:\adb>adb pull /factory /factory
pull: building file list...
pull: /factory/factory.zip -> /factory/factory.zip
pull: /factory/rombackup.zip -> /factory/rombackup.zip
pull: /factory/romrestore.zip -> /factory/romrestore.zip
pull: /factory/fsck.zip -> /factory/fsck.zip
4 files pulled. 0 files skipped.
4093 KB/s (355198432 bytes in 84.746s)


Maybe I can do something with it?

 

[leapinlar]

Light of hope appeared, thanks!

A little stupid question. Is format via mount&storage clears only of table of contents? May be there is a way to recover these files so far?

Well what i've tried to do:
using adb i mounted /rom and pulled all from there:

C:\adb>adb pull /rom /rom
pull: building file list...
pull: /rom/devconf/hdcp.keys -> /rom/devconf/hdcp.ke
pull: /rom/devconf/WVKeybox -> /rom/devconf/WVKeybox
pull: /rom/devconf/PublicKey -> /rom/devconf/PublicK
pull: /rom/devconf/HashOfPrivateKey -> /rom/devconf/
pull: /rom/devconf/EventType -> /rom/devconf/EventTy
pull: /rom/devconf/DeviceAttribute -> /rom/devconf/D
pull: /rom/devconf/DateManufactured -> /rom/devconf/
pull: /rom/devconf/OperatingMode -> /rom/devconf/Ope
pull: /rom/devconf/ModelNumber -> /rom/devconf/Model
pull: /rom/devconf/EAN -> /rom/devconf/EAN
pull: /rom/devconf/ProductID -> /rom/devconf/Product
pull: /rom/devconf/Bq275020Dffs -> /rom/devconf/Bq27
pull: /rom/devconf/BatteryType -> /rom/devconf/Batte
pull: /rom/devconf/WiFiBackupCalibration -> /rom/dev
pull: /rom/devconf/MACAddress -> /rom/devconf/MACAdd
pull: /rom/devconf/MainBoardSN -> /rom/devconf/MainB
pull: /rom/devconf/SerialNumber -> /rom/devconf/Seri
pull: /rom/devconf/DisplayVendor -> /rom/devconf/Dis
pull: /rom/devconf/DeviceID -> /rom/devconf/DeviceID

Then the same with /factory:

C:\adb>adb pull /factory /factory
pull: building file list...
pull: /factory/factory.zip -> /factory/factory.zip
pull: /factory/rombackup.zip -> /factory/rombackup.zip
pull: /factory/romrestore.zip -> /factory/romrestore.zip
pull: /factory/fsck.zip -> /factory/fsck.zip
4 files pulled. 0 files skipped.
4093 KB/s (355198432 bytes in 84.746s)


Maybe I can do something with it?

Then you did not format either of them or if you did format /rom, it repaired itself. You are safe. Take that factory.zip file and flash it with my CWM for stock. Then format /data with my CWM also. NOTHING ELSE! Then try booting to stock with the SD out.

Sent from my HD+ rooted stock using Tapatalk

 

[spinorog]

Then you did not format either of them or if you did format /rom, it repaired itself. You are safe. Take that factory.zip file and flash it with my CWM for stock. Then format /data with my CWM also. NOTHING ELSE! Then try booting to stock with the SD out.

Sent from my HD+ rooted stock using Tapatalk

Strange things are happening...
-- Installing: /sdcard/factory.zip
Installing update...
Random offset 0xcc
Boot files...
Boot files...

Install from sdcard complete.

Then mounts&storage:

Formatting /data...
Error mounting /data!
Skipping format...
Done.

That's the thing. And bootloop again. It shows nook® for approx 20 sec, then screen power off, nook® again 20 sec, then nook® and progressbar under "nook®" for approx 5 sec and all over again from the beggining.

What i forgot to tell: in cyanogen after reflashing i got an error in settings when tried to open Storage tab, that is why I decided to reflash it again. I've formatted microsd and being in cyanogen cwm through adb pushed there cyanogen zip, but forgot to mount /sdcard before. adb told nothing about that, but thought now, may be it matters?

 

[roustabout]

Perhaps this is a dumb question, but have you pulled the sdcard and let it go through 8 cycles of bootlooping?

If you do, it should reset itself to stock after the 8th if a fair amount of the internal memory is intact.

If it won't, well, you have a CM device. I disagree with the advice to return under warranty - formatting internal memory as you install a ROM and returning under warranty is kind of like taking a hammer to the screen and then asking for an exchange on the grounds that the screen is damaged.

Open suggestions that doing so is reasonable will be cited by vendors in internal and external communications around why they lock bootloaders -- a locked bootloader helps prevent returns on the grounds of customer-induced logical damage to the device.

 

[leapinlar]

Strange things are happening...
-- Installing: /sdcard/factory.zip
Installing update...
Random offset 0xcc
Boot files...
Boot files...

Install from sdcard complete.

Then mounts&storage:

Formatting /data...
Error mounting /data!
Skipping format...
Done.

That's the thing. And bootloop again. It shows nook® for approx 20 sec, then screen power off, nook® again 20 sec, then nook® and progressbar under "nook®" for approx 5 sec and all over again from the beggining.

What i forgot to tell: in cyanogen after reflashing i got an error in settings when tried to open Storage tab, that is why I decided to reflash it again. I've formatted microsd and being in cyanogen cwm through adb pushed there cyanogen zip, but forgot to mount /sdcard before. adb told nothing about that, but thought now, may be it matters?

This kind of a silly question, but you did use my CWM SD made for stock to do the flashing and formatting, right? Not the CM10 SD?

You said a progress bar after booting? That is saying that it is trying to repair itself. Did it say it was successful? Try flashing the romrestore.zip that you extracted from /factory. That is supposed to put what is saved in rombackup.zip onto your internal partition 5.

Let me explain what I think it is doing. When the device boots, it looks in /rom for the existence of /devconf/DeviceID. It it cannot read it, it thinks /rom is corrupted and boots to stock recovery and runs romrestore.zip from partition 7 to repair /rom. That zip looks for rombackup.zip in partition 7 which is a backup of /rom made at manufacture. It then restores those zipped files to /rom. When it finishes successfully, it resets the internal flag that told it to boot to recovery and do the repair. Then it reboots and since the flag is reset, it should try to boot normally. If the repair did not take, it does it again, bootlooping.

If you have a bootable CWM SD in the slot when it is trying to do the repair, it boots to the SD recovery (CWM) rather than the stock recovery and CWM does nothing. And it bootloops. When you tell it to reboot, it has not repaired itself yet so it continues to try.

I don't know why the device continues to think something is wrong with /rom when you could mount it and pull files from it. Maybe the flag is not resetting.

Of course all of this could be explained if you were using the wrong CWM.

And roustabout, doing the 8 failed boot does exactly what flashing the factory zip does, except it formats all of data including media first.

Sent from my HD+ running CM10 on SD with XDA Premium

 

[spinorog]

This kind of a silly question, but you did use my CWM SD made for stock to do the flashing and formatting, right? Not the CM10 SD?

You said a progress bar after booting? That is saying that it is trying to repair itself. Did it say it was successful? Try flashing the romrestore.zip that you extracted from /factory. That is supposed to put what is saved in rombackup.zip onto your internal partition 5.

Let me explain what I think it is doing. When the device boots, it looks in /rom for the existence of /devconf/DeviceID. It it cannot read it, it thinks /rom is corrupted and boots to stock recovery and runs romrestore.zip from partition 7 to repair /rom. That zip looks for rombackup.zip in partition 7 which is a backup of /rom made at manufacture. It then restores those zipped files to /rom. When it finishes successfully, it resets the internal flag that told it to boot to recovery and do the repair. Then it reboots and since the flag is reset, it should try to boot normally. If the repair did not take, it does it again, bootlooping.

If you have a bootable CWM SD in the slot when it is trying to do the repair, it boots to the SD recovery (CWM) rather than the stock recovery and CWM does nothing. And it bootloops. When you tell it to reboot, it has not repaired itself yet so it continues to try.

I don't know why the device continues to think something is wrong with /rom when you could mount it and pull files from it. Maybe the flag is not resetting.

Of course all of this could be explained if you were using the wrong CWM.

And roustabout, doing the 8 failed boot does exactly what flashing the factory zip does, except it formats all of data including media first.

Sent from my HD+ running CM10 on SD with XDA Premium

Thanks for not leaving me alone

The total story sounds this way:

1. Error in CM rom in settings.apk
2. In CM CWM format of /rom and something else(very likely that i formatted /system and /data too)
3. Flashed cm.zip
4. Reboot. Hello bootloop.
5. Formatted sd and wrote there your CWM.
6. Formatted /data(with error of mounting it)
7. Flashed your factory 2.0.0 rooted.
7.1. Sd out.
8. Bootloop, I missed you so much...
9. Then I formatted sd and wrote there CM CWM.
10. Using adb I pulled /format and /rom
11. Formatted sd and wrote there your CWM.
12. Formatted /data(with error of mounting it)
13. Flashed factory.zip
14. Sd out.
15. Bootloop leaves me not.

Haven't counted boots, i'll try to wait for 8 as you told. But what does fail of mounting /data means? And could it be so that nook thinks thst something is wrong with smth else but /rom?

 

[spinorog]

It looks like magic.... But after yesterday failures today it has booted differently... On step with progress bar it was doing smth for about 30 sec and progress bar appeared twice (once for long and second time faster). And after that it started as if there were no problems at all! Thank god and xda! I'm very greatful!

 

[leapinlar]

Thanks for not leaving me alone

The total story sounds this way:

1. Error in CM rom in settings.apk
2. In CM CWM format of /rom and something else(very likely that i formatted /system and /data too)
3. Flashed cm.zip
4. Reboot. Hello bootloop.
5. Formatted sd and wrote there your CWM.
6. Formatted /data(with error of mounting it)
7. Flashed your factory 2.0.0 rooted.
7.1. Sd out.
8. Bootloop, I missed you so much...
9. Then I formatted sd and wrote there CM CWM.
10. Using adb I pulled /format and /rom
11. Formatted sd and wrote there your CWM.
12. Formatted /data(with error of mounting it)
13. Flashed factory.zip
14. Sd out.
15. Bootloop leaves me not.

Haven't counted boots, i'll try to wait for 8 as you told. But what does fail of mounting /data means? And could it be so that nook thinks thst something is wrong with smth else but /rom?

You don't have to wait for 8 failed boots. (Anyway it restarts the count over every time you boot to CWM.) Just interrupt the boot 8 times in a row (without the SD in) by powering off just after it starts to boot. On the eighth or so it should boot to a different screen saying clearing data (or something like that) then it installs the factory zip. It uses its stock recovery to do these things.

I don't know why my CWM would not mount /data. Maybe the 8 failed boot procedure can.

Sent from my HD+ running CM10 on SD with XDA Premium