Database Users

Corrupt partition table or fried emmc?

Hi Guys,
I've been researching about this topic now for quite a while, but i am still not certain, whether if the eMMC of my DZ is fried..
Story is as follows:
Just rooted my newly bought DZ (lost my old one )using downgrade, then gfree, everything went fine so far.
After that i went to recovery, flashed virtuous affinity and rebooted. I gave it time to boot, but it got stuck on the "loading initial setup" screen (waited patiently about 20 mins or so). I thought it would be no big deal to pull the battery and let it boot again (Did this with my previous DZ numerous times and all was fine)
On second boot nothing happened, so i checked recovery and saw that the /data and /cache were obviously corrupt. Formatting was not possible by any means, neither by the tools in recovery, nor through flashing superwipe.
I can confirm that my eMMC is one of those possible faulty M4G2DE, see: http://forum.xda-developers.com/showthread.php?t=1039504&highlight=can+t+format&page=3
But it is mentioned in the thread, that it could be either a faulty chip or a defective partition table, which should be possible to rebuild either with a RUU or by adb shell:
Code:
mke2fs -t -ext3 /dev/block/mmcblk0p27
It was also mentioned to check whether
Code:
cat /proc/kmsg | grep mmc0
would say anything about an initialization error, which is not the case for me:
Code:
cat /proc/kmsg | grep mmc0
<3>[ 7.565124] mmc0: No card detect facilities available
<6>[ 7.565765] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.565917] mmc0: Platform slot type: MMC
<6>[ 7.566162] mmc0: 4 bit data mode disabled
<6>[ 7.566284] mmc0: 8 bit data mode enabled
<6>[ 7.566528] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.566680] mmc0: Slot eject status = 0
<6>[ 7.566802] mmc0: Power save feature enable = 1
<6>[ 7.567077] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x2a924000
<6>[ 7.567199] mmc0: DM cmd busaddr 0x2a924000, cmdptr busaddr 0x2a924300
<6>[ 7.723022] mmc0: new high speed MMC card at address 0001
<6>[ 7.724884] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
I know, from this point, being unable to do a RUU, nor flash a PC10IMG.zio via fastboot, nor recreate partitions in any other way, would suggest that the eMMC is fried and i should see that i send it in for repair.
BUT
I came across this:
http://tjworld.net/wiki/Android/HTC/Vision/EmmcPartitioning
Basically he is saying, that the hboot is trying to create an extended partition on the end of the blocks, if unallocated blocks are still available this should do no harm. But if the disk is fully partitioned, it simply overflows and creates the partittion at the beginning of the disk. According to that, this causes the usual tools to be unable to reformat the disk, because they get stuck in the same overflow.
He mentions a way to fix this, by unallocating the last partition, but i am not sure how this could be done.
Can the hboot be the problem? The new DZ runs eng hboot 84.2000, on my old one i used to have the normal pvt ship (see sig)
Maybe some of you would like to help me think
And maybe we can find a solution for some of the fried eMMC's

Hi Xadro
unfortunatly i have currently exactly the same problem. I can't manage to format the system partition (mmcblk0p25) and the cache partition (mmcblk0p27).
Do got any solution for it?
Thx in advance
Chris

Small update:
I managed to format each in 4EXT with tools formating to use ext3. Now my info is showing me the attatched screeni. Before that he crashed everytime when I opend that view and system and cache was ext4 but also without size values.

Kind of an awkward way of thinking, but... I see that you have a 32GB Sd Card.
Could that have any link to your problem?

Mhh dont know. Shouldn't as i never had problems before.
My target was to use Android Revolution HD 7.0.2 and I may should add the whole story in short form:
followed http://forum.xda-developers.com/showthread.php?t=1178912 to do a downgrade -> worked perfectly
followed the rest of http://forum.xda-developers.com/wiki/HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD to gain perm root until step 7. -> worked perfectly
used http://forum.xda-developers.com/showthread.php?t=1493404 to gain a new rom
it was written to use 4EXT -> so installed what worked and also the info was displaying the correct sizes
applied ZIP and restarted -> waited 30min but only boot animation was displayed and after some time it restarted -> boot loop
applied the ZIP again -> same result
found in http://forum.xda-developers.com/showthread.php?t=840040 to load SuperWipe...what i did and it reformated worked with out error
applied ZIP again
didn't started anymore -> stucked there
During all the restartings it can be that i may interrupt some important "reallocating" of partitions...but not sure.
But I can try replace the SD with the original one. But not thinking that it is a problem, cause it is normal accessable :/
Any way big thanks for trying to help me!

try a fastboot wipe, cleaner than even your best superwipe - then when you pick a rom to flash pick an old tried and true like the stable cm7 or miui.us

Hi,
unfortunatly that didn't worked
if I start "fastboot erase system -w" (i think you ment that) he just writing "erasing 'system'..." and just stops there. my phone is displaying the whole time the fastboot white screen, but i can't do anything there anymore (vol up/down...). I waitet 2h...only could remove battery
I realy appresiate any other recommendation :/
Update:
Also this hangs:
Code:
./fastboot -w
erasing 'userdata'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 3627.265s

Phone needs to be in flashboot usb, and when you open cmd on your comp you need to open it to where you have fastboot stored or change directories to it. Or you can add it to your variables and open it anywhere.
Sent from my HTC Desire Z using xda premium

Sorry for answering a bit late, but was in weekend holidays
Of course i did it in the fastboot folder and my phone was in fastboot usb (red blinking on phone screen). Otherwise i would get "<waiting for device>". Just got that error message posted above. Any ideas left? Otherwise it seams to be a broken eMMC

So when conected phone displayedfastboot usb in red? If so when you typed fastboot devices did it display one?
Sent from my T-Mobile G2 using xda premium

Yepp, it does show serial and "recovery".

And if you try to flash the hboot/spl now what happens?
Sent from my T-Mobile G2 using xda premium

Hi again,
I tried to flash the hboot while in fastboot with following message:
Code:
C:\android-sdk-windows\platform-tools\rom_26>fastboot flash hboot hboot_7230_Vision_HEP_0.85.0005_101011.nb0
sending 'hboot' (1024 KB)...
OKAY [ 0.183s]
writing 'hboot'...
FAILED (remote: image update error)
finished. total time: 2.904s
Also tried to do it with "dd" what seem to work but as soon as i restart the phone it still says it is in an "VISION PVT ENG S-OFF" while i was flashing a non-ENG hboot...and the version also not matching "HBOOT-0.84.2000" while flashing 0.85.0005
I also tried to put a newer (2.42.405.2) PC10IMG.zip from RUU on SD Card but it fails with message "BOOTLOADER - Fail-PU" and "Partition update fail! Update Fail!"
I realy think the eMMC got bricked...If you do not have any advices anymore i will look for a replacement from somewhere.

I still searched around and found that post: http://forum.xda-developers.com/showthread.php?t=1039504&page=6#post14645519
Its exactly my situation with same outputs and also the "bad" eMMC. I will try to send it in. Reading all that i have to admit that i already had before trying rooting it, i couldn't do a normal restart (just had a black screen after splash screen). It must have been connected to USB to be able to do a restart. So I think i didn't done anything wrong...just have a hardware issue

Sorry for not answering you chrisdeath, was busy with other stuff lately, so i hadn't had the time to stop by here. Have you been sending in your phone already? Telling from the stuff you wrote earlier, it is very likely a fried emmc. There is a way to confirm this, using two shells. With one shell, you need to display the log using
Cat /proc/kmsg ¦ grep emmc0
With the other shell, try to do any kind of write access (e.g. format partition or dd anywhere)
If there are any errors in the log referring to the write fail, your chip is bricked.
It will probably get fixed free of charge, even if the phone is rooted, others have told me that they got it new without payment. If your new one has the same chip, you should if by any means possible, never pull the battery during operation, as this seems to be the main cause for bricking the chip.
Sent from my HTC Vision using XDA

[Q] Bricked Lumia 1020 in FFU download mode doesn't show up in device manager

Hi everyone,
yesterday I managed to brick my phone while doing a hard reset. Now its in the following state:
Turn on: Nokia logo shows, goes to gears after. Progress bar stops at around a quarter and stays there forever.
Turn on with VolDown during Nokia logo: Doesn't work. Phone just keeps restarting. Exclamation mark never shows up.
Turn on with VolUp during Nokia logo: Goes to FFU download mode. Flash and gear shows up.
Now I read much about flashing your Lumia yesterday and was very happy of what seemed like a solution.
But when I plug my phone into my PC, NOTHING happens. Not a beep, no message, no device in device manager. Tried with 4 different cables (which I can use to connect my SGS2 to my PC) on Win 10 Preview, Win 7 and Win XP. Not working.
I would really appreciate any help regarding my problem.
Greetings.

^woOt said:
Hi everyone,
yesterday I managed to brick my phone while doing a hard reset. Now its in the following state:
Turn on: Nokia logo shows, goes to gears after. Progress bar stops at around a quarter and stays there forever.
Turn on with VolDown during Nokia logo: Doesn't work. Phone just keeps restarting. Exclamation mark never shows up.
Turn on with VolUp during Nokia logo: Goes to FFU download mode. Flash and gear shows up.
Now I read much about flashing your Lumia yesterday and was very happy of what seemed like a solution.
But when I plug my phone into my PC, NOTHING happens. Not a beep, no message, no device in device manager. Tried with 4 different cables (which I can use to connect my SGS2 to my PC) on Win 10 Preview, Win 7 and Win XP. Not working.
I would really appreciate any help regarding my problem.
Greetings.
Click to expand...
Click to collapse
Follow this tutorial.

Thanks for the post.
I may have forgotten to mention that I did everything exactly like in the tutorial. Which is why I started this thread.
I disabled driver signature enforcement, installed the drivers from the LumiaFlashTools package, downloaded a fitting FFU already and so on. Only problem is that no PC detects my device. If there would be a driver missing, the device should at least pop up in the device manager, right? But theres nothing in there. So I got a different issue.
I even downloaded a program called USBDeview to monitor everything that I plug in and out of my USB ports. But theres nothing in there either.

^woOt said:
Thanks for the post.
I may have forgotten to mention that I did everything exactly like in the tutorial. Which is why I started this thread.
I disabled driver signature enforcement, installed the drivers from the LumiaFlashTools package, downloaded a fitting FFU already and so on. Only problem is that no PC detects my device. If there would be a driver missing, the device should at least pop up in the device manager, right? But theres nothing in there. So I got a different issue.
I even downloaded a program called USBDeview to monitor everything that I plug in and out of my USB ports. But theres nothing in there either.
Click to expand...
Click to collapse
Seems like a serious issue,
Speak to @anaheiim or the author of the thread that made the unbrick tutorial
try the key combination reset from here : http://www.hard-reset.com/nokia-lumia-1020-hard-reset.html
Also, charge your battery or else make sure it has charge that could also be a reason the phone doesnt detect

Thank you.
I guess I tried all the key combinations the phone has by now. VolDown+Power to restart, VolDown+Camera+Power to restart, pressing VolUp->VolDown->Power->VolDown while starting (although I can't get to the (!)-screen), etc.
I hope I can change any PC settings or whatever to make the phone show up, since I'm totally out of options doing anything different on the phone.

Be looking at the device manager window and plug the usb cable in and reboot the phone. Does the window refresh and draw the tree view again with all the devices?

Nope doesn't do that either. If I refresh manually, it still doesn't show up.
Maybe I should also mention, that while my phone was working, I couldn't get it to connect too. Don't know if it showed up in device manager then because it didn't really vorher me then. But I remember problems getting it to connect now that I think about it.
Could be a broken hardware?

its sounding to me like eMMC failure according to the symptoms, so yes, hardware issue. just my opinion

Hello guys since 2 years my lumia 1020 was lying in useless things box where I usually keep my useless things after a while I remember that I have a lumia phone and decided to switch it to on and everything was working as expected except that being not able to use some apps like fb messenger and made some investigation to be able to run those apps as updated to the proper version I had to update it to windows 10 read too many articles and then ended up in xda forum. I launched the wpinternals and got the ffu and emergency files from lumiafirmware followed every instruction to run win10 in this crap phone somehow the phone stuck on unlock bootloader screen waited like one hour and then realized qualcamm 9008 driver wasn't loading as it is suppose to. Long story short that the phone now no way booting I plug the usb click power button like 10 seconds windows logo lighting up for a few seconds (like 2-3). tried hardcore reset soft reset super reset everythin the phone is bricked as it deserves what to be called (bricked) Now I m trying to boot phone with hex and mbn files by using cmd as admin sending commands with thor2 and I am ending up with the log below
C:\Windows\system32>cd /D c:\hex
c:\hex>thor2 -mode emergency -hexfile h.hex -mbnfile m.mbn -orig_gpt
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode emergency -hexfile h.hex -mbnfile m.mbn -orig_gpt
Process started Mon Jan 01 21:43:31 2018
Logging to file C:\Users\Savas\AppData\Local\Temp\thor2_win_20180101214331_ThreadId-9888.log
Debugging enabled for emergency
Initiating emergency download
Using default emergency protocol
ALPHA EMERGENCY FLASH START
Emergency Programmer V1 version 2014.10.31.001
Hex download selected
Check if device in Dload
Connection to DLOAD mode succeeded
Get Dload parameters
Sending HEX flasher to the device
Sending GO command if HEX flasher successfully uploaded.
Emergency Programmer V1 version 2014.10.31.001
Mbn download selected
Waiting for connection to flash programmer
Connecting to flash programmer
Received valid HELLO_RSP
Safe version=true, transfer size=15360
Received valid SECURITY_RSP
Successfully connected to flash programmer
Connection to flash programmer succeeded
Uploading bootloader(s), UEFI, etc from MBN image to the eMMC. This will take up to 20 seconds
Reading GPT from binary
-- GPT STARTs--
name: SBL1
startLBA: 34
endLBA: 243
size: 0x000000000001a400 bytes
attributes: 0x0
name: SBL2
startLBA: 244
endLBA: 507
size: 0x0000000000021000 bytes
attributes: 0x0
name: SBL3
startLBA: 508
endLBA: 1193
size: 0x0000000000055c00 bytes
attributes: 0x0
name: UEFI
startLBA: 1194
endLBA: 3273
size: 0x0000000000104000 bytes
attributes: 0x0
name: RPM
startLBA: 3274
endLBA: 3559
size: 0x0000000000023c00 bytes
attributes: 0x0
name: TZ
startLBA: 3560
endLBA: 3985
size: 0x0000000000035400 bytes
attributes: 0x0
name: WinSecApp
startLBA: 3986
endLBA: 4609
size: 0x000000000004e000 bytes
attributes: 0x0
name: UEFI_BS_NV
startLBA: 4610
endLBA: 4865
size: 0x0000000000020000 bytes
attributes: 0x0
name: UEFI_NV
startLBA: 4866
endLBA: 4881
size: 0x0000000000002000 bytes
attributes: 0x0
name: UEFI_RT_NV
startLBA: 4882
endLBA: 5137
size: 0x0000000000020000 bytes
attributes: 0x0
name: UEFI_RT_NV_RPMB
startLBA: 5138
endLBA: 5153
size: 0x0000000000002000 bytes
attributes: 0x0
name: SSD
startLBA: 5154
endLBA: 5169
size: 0x0000000000002000 bytes
attributes: 0x0
name: PLAT
startLBA: 5170
endLBA: 7243
size: 0x0000000000103400 bytes
attributes: 0x0
-- GPT ENDs --
Sending OPEN_MULTI_REQ
Received valid response to OPEN_MULTI_REQ
Programming image m
Image opened successfully for reading
SAFE hex file was used and unallowed memory address was being written.
Reset the device and use the correct HEX file.
ALPHA EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 11.00 seconds.
Unknown error code.
THOR2 1.8.2.18 exited with error code 85034 (0x14C2A)
Any idea suggestion welcomes.

Quite a late reply...
But, if you still keep that phn in the same state,
I would like to ask which version of wpInternals have you used?
You need to try only with wpInternals 1.2 . You can enter into emergency download mode by following key combination specified at 'restore bootloader section', try for restoring bootloder first.
You need original FFu image and emergency files.
All key combinations to be tried while you have connected your device to the pc's usb port.
I hope, if not for you then for someone else who may still be using 1020L (just like me ... LoL) gets help by this.

^woOt said:
Hi everyone,
yesterday I managed to brick my phone while doing a hard reset. Now its in the following state:
Turn on: Nokia logo shows, goes to gears after. Progress bar stops at around a quarter and stays there forever.
Turn on with VolDown during Nokia logo: Doesn't work. Phone just keeps restarting. Exclamation mark never shows up.
Turn on with VolUp during Nokia logo: Goes to FFU download mode. Flash and gear shows up.
Now I read much about flashing your Lumia yesterday and was very happy of what seemed like a solution.
But when I plug my phone into my PC, NOTHING happens. Not a beep, no message, no device in device manager. Tried with 4 different cables (which I can use to connect my SGS2 to my PC) on Win 10 Preview, Win 7 and Win XP. Not working.
I would really appreciate any help regarding my problem.
Greetings.
Click to expand...
Click to collapse
Well...
You should download Windows Device Recovery Tool and recover your device!

D802 bricked, tried everything

Hello everyone. Here's my story
I've been using CM13. After installing their OTA update it ruined my android. So I downloaded new cm13 rom, wiped everything, accidentally clicked reboot (without flashing new rom) and it was over (At least I think this happened, it was some time ago and I'm already trying to fix this for a long).
I am stuck in LG logo. Can't access recovery (I've had this issue before. Could get to recovery only by command from adb).
I can get to Download mode. But PC can't see my device. Tried several PC's, windows, ubuntu. I flashed other phones with this method, only G2 is not visible. I'm doing here everything fine.
Also I tried this:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Success but my phone keeps flashing on and off. I've got access to partitions like every 5 seconds and only for a second. I think I managed to flash those 3 partitions, but there's no difference, pc still can't see phone when in download mode.
Should I trow it to the ocean?

Keep it
Here is my story
Bricked my device (d802) with your stuation no recovey no download mode
My phone's partition table deleted any way, tried wire method which you've already tried
Tried several times and release this wire method put in 2 seperate modes
Found the mode it shows in ubuntu a sda block (with several tries with wire method)
I've got full 32 gig backup, thats my advantage between your stuation
In ubuntu fdisk - l shows all disk and shows my phone as a disk but no information about disk or partitions etc. only sda block
In the end pushed the 32 gig backup with dd if=/(path of my backup) of=/dev/block/sd* bs=4k
Wait some time until process done (30-45 minutes I guess)
Thats all, phone boots normally everything is fine
If you're using 32 gig version I can send you my backup (with imei deleted) so you can boot your device and install kdz
Or I can show you how to backup another LG phone and recover from that backup. http://forum.xda-developers.com/lg-g2/general/how-to-backup-data-16-gb-32-gb-size-t3236558

Thank you for your reply lynxrz
I've got bigger problem. When I enter qhsusb mode, backlight of my screen keeps switching on and off every 3-4 seconds. I can see partition only for a second.

Vergil333 said:
Thank you for your reply lynxrz
I've got bigger problem. When I enter qhsusb mode, backlight of my screen keeps switching on and off every 3-4 seconds. I can see partition only for a second.
Click to expand...
Click to collapse
Not necesaary to see partitions
In ubuntu or any linux enviroment open up a teeminal emulator and "sudo fdisk -l" and it will be like that;
Code:
$ sudo fdisk -l
Disk /dev/sda: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00008ec7
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1013 8136891 8e Linux LVM
/dev/sda2 1014 1044 249007+ 5 Extended
/dev/sda5 1014 1044 248976 83 Linux
sda sdb sdc means a phisicial disk. sda1 sda2 sda3 means partitions of "sda" disk. My process depends on overwriting sda disk not partitions, so you don't need to see partitions
Just type "sudo fdisk -l" and tell me you can see any sdb sdc phisical disk permenately. We must know connection can be dropped or not(it can be bootloop). Partitions might disappear but phisical disk have to be there. Look for it.
If you can't see in qhsusb mode try another mode, this is the lucky part of tring the wire method. I don't know exactly how to swich "another" mode but you can detect in window device manager, then switch to linux (Don't be afraid to losing this mode it stays when you plug off usb if you connected battery)
Sorry I don't remember that "another" mode's name but it is exists
Firstly you need to know qhsusb mode can see a "phisical" disc or not?

I'm in work now, but I tried this yesterday.
Phone appears as sdc when I typed
Code:
$ ls /dev/sd*
while in qhsusb mode. (I had to type it several times repeatedly to catch the right moment)
I can get to download mode, so I typed
Code:
$ sudo fdisk -l
and couldn't see sdc there.

Vergil333 said:
I'm in work now, but I tried this yesterday.
Phone appears as sdc when I typed
Code:
$ ls /dev/sd*
while in qhsusb mode. (I had to type it several times repeatedly to catch the right moment)
Click to expand...
Click to collapse
Probably it can be bootloop.
Did you plug off the battery when touching capacitor ? Just asking to be sure.

Sure, I unplugged the battery So qhsusb not stable and download mod not visible to computers.
I already gave up of hope

Ok I will solve how to enter "another" mode (not qhsusb)
But I need time to backup all my data in any case
If I solve, prepare a backup for you and it'll be 32 GB
Edit: Can not find out "another" mode because of data cable problem (severed usb cable charging but not transferring data) You're on your own now to find another usb mode, It can be the "holding time" of cable on capacitor.
Good luck with that
Prepairing your backup with otg

Really thanks for your help lynxrz. I appreciate all effort

Vergil333 said:
Really thanks for your help lynxrz. I appreciate all effort
Click to expand...
Click to collapse
You're welcome
PS: Did I send pm the download link?

You did. 29.1GB rar file. I have no use for it till I find another mode to be able to flash partition.
I already bought G3. Probably I will sell G2 for parts

Uploading now and it was %17 maybe tomorrow will be uploaded %100
20,4 GB and compressed seperated 1 GB rar parts (21 parts)
Realised by you broken usb, I'll solder it but no time for that now, 2 days later I'll try it.
I'm stuborn as hell with that Just wait we'll fix it don't sell
Maybe I can make a tutorial and help the others
UPDATE: Usb works I'll try it tomorrow

Bricked Nook Glowlight 3

I installed relaunchx and rooted the device sucessfully. It was running okay. I set the home button to restart in relaunch rather than the nook software. I rebooted and all it would do is go to the front-screen with the nook barnes and noble logo on the front. I could turn it on and off, but that was it. It charged. I tried to start packages on the device via adb but it said the system wasn't running. I could see processes system processes with ps.
I issued a reboot recovery command via adb. The Nook finally responded with something other than a reboot and it went into recovery and did a full factory reset. I thought I was in the clear. But no. It rebooted and went back to the logo screen as before. However, now I no longer have adb access.This might be because the factory reset turned off usb debugging. So now I can't access the device at all. Does anyone have any ideas how I might be able to proceed? I think the device is functional, but the bootloader is damaged somehow so I can't start Android on the device. Without adb access, I think it's effectively gone.

It's likely that you don't have any home application working.
Or maybe it's completely borked.
Have you tried holding various buttons on a power up to see if you can try recovery again?
The next worst case is just using the hardware console connection (inside the case) to see if you have a shell and what's going on.
For the old NST we had a whole setup to boot over USB even with a totally wiped out flash.
That hasn't been looked at for the newer iMX6 (vs OMAP) Nooks.

Hi,
Renate NST said:
For the old NST we had a whole setup to boot over USB even with a totally wiped out flash.
That hasn't been looked at for the newer iMX6 (vs OMAP) Nooks.
Click to expand...
Click to collapse
I tried to manually root using https://forum.xda-developers.com/showpost.php?p=76496894&postcount=13, replicating commands on Linux, and I totally bricked my Nook - probably bad repacking on boot image.
Code:
[884213.478979] usb 3-3: new high-speed USB device number 123 using xhci_hcd
[884213.607636] usb 3-3: New USB device found, idVendor=15a2, idProduct=0063
[884213.607642] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[884213.607645] usb 3-3: Product: SE Blank MEGREZ
[884213.607648] usb 3-3: Manufacturer: Freescale SemiConductor Inc
[884213.609540] hid-generic 0003:15A2:0063.000C: hiddev0,hidraw0: USB HID v1.10 Device [Freescale SemiConductor
Inc SE Blank MEGREZ] on usb-0000:00:14.0-3/input0
Can you point me to NST setup to recover over USB, I would spend some time to try to recover my Nook.
Thank you!

If you had just wiped out P1 you should still have recovery (on P2) just fine.
Do a restart holding the Home button down.
If this doesn't work you somehow managed to wipe the bootloader.
To get the USB HID bootloader to work would be a bit of a project.
There is the starting point of this tool: https://github.com/boundarydevices/imx_usb_loader
Anything that is written about USB recovery on the NST (which uses OMAP) has nothing to do with the new Glows (iMX6SL).
Hmmm, the Kindle Paper White 2 seems to have the same processor/ROM bootloader...

For what it's worth, here is an overview of the low-level MMC:
Code:
Name 32kB units 512B sectors Byte addresses /dev/block
Start End Start Size Start End
---------- ----- --- ----- ----- ------- ------- ----------
mbr 0 1 0 1FF
sn 1 1 200 3FF
bootloader 2 1022 400 7FFFF
hwcfg 1024 2 80000 803FF
ntxfw 1030 256 80C00 A0BFF
bootenv 1536 510 C0000 FFBFF
boot 33 223 2048 12224 100000 6F7FFF mmcblk0p1
waveform 225 544 14336 20480 700000 10FFFFF
logo 545 608 34816 4096 1100000 12FFFFF
recovery 609 1632 38912 65536 1300000 32FFFFF mmcblk0p2

Renate NST said:
If you had just wiped out P1 you should still have recovery (on P2) just fine.
Do a restart holding the Home button down.
If this doesn't work you somehow managed to wipe the bootloader.
Click to expand...
Click to collapse
I was lucky!
Restart holding the Home button down made no difference.
Trying randomly, I observed restart holding the Home and Right Up buttons goes into fastboot.
I recovered P1 partition for which I had backup and my Nook is live again.
Many thanks!!!
imx_usb_loader would have taken some time to learn.

So you're stuck in the ROM USB bootloader?
To look into a solution I had to get the ROM USB bootloader to run on my Nook to test things.
I didn't feel like bricking the Nook, so that was out.
I disassembled the ROM bootloader and found the correct, erm, workable entry point in the ROM.
Code:
eBR-1A # go [i]<entry address>[/i]
Code:
iManufacturer: 0x01
0x0409: "Freescale SemiConductor Inc "
iProduct: 0x02
0x0409: "SE Blank MEGREZ"
So now I can play around with the ROM USB bootloader.

Renate NST said:
So you're stuck in the ROM USB bootloader?
Click to expand...
Click to collapse
No.
After fastboot got enabled I booted nnglow3.img and then I recovered P1 partition with dd.
My Nook is like new
Thanks,
C

cipibad said:
No.
After fastboot got enabled I booted nnglow3.img and then I recovered P1 partition with dd.
My Nook is like new
Thanks,
C
Click to expand...
Click to collapse
I'm having the same issue as yours, could you please help me to unbrick my device?
I'm a newbie to technology so please help me step by step

Fix for bricked Glow2, 3, 4

Well, I finally got it together and figured out how to use the ROM bootloader on the iMX6 Nooks (Glow2, 3, 4).
You can get into u-boot even with a trashed disk.
Of course, that may not be the end of your problems.
You may have to repair stuff.
Having a UART console wired up will certainly make things clearer/easier.
So, if you have a bricked Glow (that still bongs when you plug it into a computer),
I have a program for downloading the u-boot.
I can try to make a version of u-boot that goes straight into fastboot.
So, does anybody have a bricked Glow?
You can check in Device Manager (devmgmt.msc) if you can find:
Code:
Human Interface Device
USB Input Device
USB\VID_15A2&PID_0063

Well, I've been playing around with all this.
I got a bit too arrogant playing around and swapping u-boots.
If you have a SBL (secondary bootloader, possibly u-boot) that looks good enough to the ROM bootloader
but doesn't actually work, you can sort of lock yourself out.
I had to disable (by grounding a test point) the eMMC to allow the ROM bootloader to run.
I've got to wiggle out and see if the boot options actually have their own test points.
I'm trying to get some more UARTs configured for GPS sensors.
The iMX6 bootloader is a known thing, but all the software out there seems half baked.
I tried one that was 7 Megs in size, but it didn't actually work.
My version weighs in at 68k, i.e. 1/100th the size.

So, I've got a cleaned up version (available in the signature).
Code:
C:\>imxboot
Found iMX6SL, VID=15a2, PID=0063
Security: Unlocked
Status: Idle
C:\>imxboot ub3
Load addr 87800400, DCD offset 002c, DCD size 0220
Found iMX6SL, VID=15a2, PID=0063
67 DCD ops processed
Write, addr 87800400, size 00039270
**********************************************************************************************************
Jumping to 87800400
Device disconnected correctly

Hi.
I have bricked Glow 3.
I tried to restore the bootloader according to your instructions and I have a problem
Code:
C:\>imxboot
Found iMX6SL, VID=15a2, PID=0063
Could not write device

companion79 said:
Code:
Could not write device
Click to expand...
Click to collapse
Hmm, strange.
Hold the reset button for 10 seconds. It should get a disconnect "bong".
Hold the reset button for 3 seconds. It should get a connect "bong".
Try imxboot by itself again.
It's strange because I have a separate error if the connection got disconnected.
I've been using imxboot alot myself on a Glow3 and never a problem.

Renate NST said:
Hmm, strange.
Hold the reset button for 10 seconds. It should get a disconnect "bong".
Hold the reset button for 3 seconds. It should get a connect "bong".
Try imxboot by itself again.
It's strange because I have a separate error if the connection got disconnected.
I've been using imxboot alot myself on a Glow3 and never a problem.
Click to expand...
Click to collapse
Reset button on the book? Where is this button? Perhaps I do not understand, perhaps you need to connect through the UART module? I was connecting through the command line.

companion79 said:
Reset button on the book? Where is this button?
Click to expand...
Click to collapse
Err, I meant the power button.

Renate NST said:
Hold the reset button for 10 seconds. It should get a disconnect "bong".
Hold the reset button for 3 seconds. It should get a connect "bong".
Try imxboot by itself again..
Click to expand...
Click to collapse
I performed all the actions, but the result is the same.
Code:
Could not write device

So write about an attempt to restore bricked nook Glow3, now position here is such
Code:
C:\>imxboot
Found iMX6SL, VID=15a2, PID=0063
Security: Unlocked
Status: Idle
C:\>imxboot ub3fb
Load addr 87800400, DCD offset 002c, DCD size 0220
Found iMX6SL, VID=15a2, PID=0063
67 DCD ops processed
Write, addr 87800400, size 00039270
**********************************************************************************************************
Jumping to 87800400
Could not read device
Now in Device Manager I find
Android ADB Interface:
USB\VID_18D1&PID_0D02&REV_0311
USB\VID_18D1&PID_0D02
I trying to run
Code:
C:\>adb reboot fastboot
error: no devices found
please help me what should I do next

companion79 said:
Now in Device Manager I find
Android ADB Interface:
USB\VID_18D1&PID_0D02&REV_0311
USB\VID_18D1&PID_0D02
Click to expand...
Click to collapse
Oops, sorry, my stupid. Fastboot uses its own bogus VID/PID.
You booted ub3fb, therefore you should be looking for fastboot, not ADB.
Windows handling of WinUSB drivers makes this all a bit obtuse.
Code:
C:\>imxboot ub3fb
...
Jumped to ...
...
C:\>fastboot devices
12345678 fastboot
C:\>fastboot boot nnglow3.img
C:\>adb shell
# ls -l

That's what I see now
Code:
C:\>imxboot ub3fb
...
Jumped to ...
...
C:\>fastboot devices
???????????? fastboot
C:\>fastboot boot nnglow3.img
Sending
Booting
Finished.
C:\>adb shell
Error: no devices/emulators found
After that, the device in the Device Manager disappears and is not detected again, reboot again returns the device to its original state.

companion79 said:
After that, the device in the Device Manager disappears and is not detected again.
Click to expand...
Click to collapse
Ok, but if at this point you pull the USB connection does Windows make a "bong" that something has been disconnected?
If so, that means that you've got something there and that the problem could be drivers for the ADB.
If not, that could mean your hwcfg is badly broken.

Try with the just-now uploaded Neo Noogie images that should be more resilient to bad NTX hwcfg.
https://forum.xda-developers.com/no...store-glow2-glow3-t3784575/page3#post81256205

Hi! In response to "imxboot ub3fb" the request writes "Could open file ub3fb". Where can I get this file? Please help!!!

egor_omsk said:
Where can I get this file?
Click to expand...
Click to collapse
Mmm, it's attached.
(It's the stock u-boot for the Glow3 with automatic jump to fastboot.)

Renate NST said:
Mmm, it's attached.
(It's the stock u-boot for the Glow3 with automatic jump to fastboot.)
Click to expand...
Click to collapse
Thank you very much
---------- Post added at 05:49 PM ---------- Previous post was at 05:45 PM ----------
imxboot
Found iMX6SL, VID=15a2, PID=0063
Security: Unlocked
Status: Frozen

egor_omsk said:
Status: Frozen
Click to expand...
Click to collapse
Yeah, that's an undocumented status that I get from the bootloader when it tried to load once, failed and didn't do a complete reset.
Do a long (10 sec) power off press, then a long (3 sec) power on press.

Renate NST said:
Yeah, that's an undocumented status that I get from the bootloader when it tried to load once, failed and didn't do a complete reset.
Do a long (10 sec) power off press, then a long (3 sec) power on press.
Click to expand...
Click to collapse
do not work

egor_omsk said:
do not work
Click to expand...
Click to collapse
Umm, you could be more specific.
You can't power it down, up, it acts the same?
Is it making USB up/down "bongs" on your desktop?
If nothing else, open the case, disconnect the battery for a few seconds.

Renate NST said:
Umm, you could be more specific.
You can't power it down, up, it acts the same?
Is it making USB up/down "bongs" on your desktop?
If nothing else, open the case, disconnect the battery for a few seconds.
Click to expand...
Click to collapse
Unfortunately it didn't work out