Hi everyone,
I was on here a few months ago with issues regarding my rooted NT. I was told that after I ran Chainfire 3D, it somehow changed the internal memory to Read Only- no changes can be permanently made. Every time it is rebooted, it resets to how it was setup prior to running Chainfire 3D. I just wanted to know if anyone has resolved this issue yet, since I saw before that a few others had the same issue.
Any help appreciated!
Thanks,
Ashlee
My NT is in this state for 5 month already. This is not related to Chainfire 3D, I never used it. We need hardware guys here, Adam Outler perhaps.
My bad...someone on the forums told me that's what messed up my NT. Anyways, yes, I've had the problem for about the same time as you!
Hopefully someone can help us out
Can you try to be more clear about your problem guys? Can you flash new cwm/twrp? Do you have a adb shell access with root privileges?
Just some question that need answering so we can help you out.
Also only 8gb or 16gb too? Thanks.
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
We can't change ANYTHING on internal emmc. So no, we can't flash twrp/cwm. But we can run it from sdcard.
Do you have a adb shell access with root privileges?
Click to expand...
Click to collapse
Yes, I do. Both in CWM and Android.
Also only 8gb or 16gb too?
Click to expand...
Click to collapse
16G only, I think.
Related topics:
1
2
3
4
Ditto...
ok then, go get chris's jelly bean 5.1 or any rom that will give you Cyanoboot and fastboot mode.
Prepare sd card with that rom.
Download this recovery:
http://www.multiupload.nl/ZPSLTX4223
Access fastboot from booting from sd card and stop boot at cyanoboot pressing N.
Then flash that recovery image and tell me if it flashes ok or you have errors.
If flash ok proceed to wipe everything and flash cm10/whatever (tm) rom except stock.
Code:
[[email protected] ~]$ fastboot flash recovery downloads/cwm_6013_emmc.img
sending 'recovery' (8220 KB)...
OKAY [ 4.134s]
writing 'recovery'...
OKAY [ 0.752s]
finished. total time: 4.886s
[[email protected] ~]$ fastboot reboot
rebooting...
finished. total time: 0.000s
Nothing changed. I still have stock recovery.
Hmm strange indeed..
ok dont reboot and try this,
Flash recovery then
fastboot continue then volume rocket select recovery from menu and boot into it.
Tell me what you have, stock or new one.
Code:
[[email protected] ~]$ fastboot flash recovery downloads/cwm_6013_emmc.img
sending 'recovery' (8220 KB)...
OKAY [ 4.202s]
writing 'recovery'...
OKAY [ 0.752s]
finished. total time: 4.954s
[[email protected] ~]$ fastboot continue
resuming boot...
OKAY [ 0.000s]
finished. total time: 0.000s
Still stock.
Well,
I can only state here that i don't in anyway have any responsibility for anything that can happen to your Nook Tablet following my recomendations.
All am trying here is to help you and others with same problem to have a functional Nook Tablet with no one blame me for any bad side effects that maybe arise.
I type these words because next steps are going to fully wipe your Nook and you maybe as well need to recover it by your self if it works. You have to look into forum for solutions.
Ok now for the trial and error:
1St download the factory image from Barnes and Noble in zip state dont unzip it dont mess with it and place it where fastboot.exe or binary is.
Boot into fastboot and
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Then:
fastboot flash recovery (stock barnes and noble recovery).img
fastboot -w update factory-image-1.4.x.zip
Fastboot reboot.
Edit:
Stock Recovery 1.4.3, Go thank lavero.burgos for this here:http://forum.xda-developers.com/showthread.php?t=1640958
http://www.multiupload.nl/9CVIXNOFAM
Stock Rom 1.4.3
http://su.barnesandnoble.com/nook/n...0ZKAA8MujlFdXFU08/nooktablet_1_4_3_update.zip
Nothing changed.
Code:
[[email protected] ~]$ fastboot erase boot
erasing 'boot'...
OKAY [ 1.479s]
finished. total time: 1.479s
[[email protected] ~]$ fastboot erase cache
erasing 'cache'...
OKAY [ 40.361s]
finished. total time: 40.361s
[[email protected] ~]$ fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.389s]
finished. total time: 1.390s
[[email protected] ~]$ fastboot erase system
erasing 'system'...
OKAY [ 57.639s]
finished. total time: 57.639s
[[email protected] ~]$ fastboot erase userdata
erasing 'userdata'...
OKAY [201.688s]
finished. total time: 201.688s
[[email protected] ~]$ fastboot flash recovery downloads/bnstock143.img
sending 'recovery' (3132 KB)...
OKAY [ 1.578s]
writing 'recovery'...
OKAY [ 0.315s]
finished. total time: 1.893s
[[email protected] ~]$ fastboot -w update downloads/nooktablet_1_4_3_update.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
error: Segmentation fault
[[email protected] ~]$ fastboot reboot
rebooting...
finished. total time: 0.000s
So lets us keep hammering it.
This time dont flash recovery boot it from memory.
Place cwm-recovery.img where fastboot is then:
Fastboot boot cwm_6013_emmc.img
Here it is:
http://www.multiupload.nl/ZPSLTX4223
While you are in Recovery wipe everything.I hope this time we succeed!
And find a way to flash a cm10 rom like 0.5.1 etc
Like:
fastboot -w update cm10-rom.zip
I was trying to wipe everything multiple times before, with all methods on forum, and every time after reboot I was still having the same CM7 with all my data, as 5 month ago. I'm just want to determine, whether this is faulty chip or some kind of software lock.
Sorry, my English is horrible.
Maybe it has to do with the locked bootloader.
Something you did and doesn't play well with it.
Did you try dd the bootloader from a working one?
Did you try dd the bootloader from a working one?
Click to expand...
Click to collapse
Yes, I did.
My personal opinion would be to return the unit back to B&N for an exchange.
How? I'm from Ukraine, not from US. Besides that, I have some personal data stored on internal memory, that I cannot erase.
Unbrick NT & return to Stock
mm_d said:
How? I'm from Ukraine, not from US. Besides that, I have some personal data stored on internal memory, that I cannot erase.
Click to expand...
Click to collapse
The process here: http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/ should clear up the Nook and return it to real stock. Once that is done, I have guides for installing CM7, CM9, or CM10 on the same site.
I have tried this method before, with no results
Hi.
After I've tried to install a custom rom, I've done a very big mistake. Now I can't boot the tab, and if I try to go in recovery or wipe data through fastboot i get the fatally error "unrecoverable bootloader error 0x00000000". I haven't any nvflash backup and have the JB bootloader (10.6.1.8). The only thing that works are the APX mode and the fastboot. I'm feeling a very idiot because i bought it yesterday.
Now, what can I do? Dump it and f**k myself? :crying:
Sorry for my bad english, thank you for your help.
I realized I'm screwed. But I've tried something...
When I go run the fastboot mode and delete a partition, for example:
Code:
fastboot erase recovery
works, and after I can run other command. But if I use:
Code:
fastboot flash recovery recovery.img
seems it works, in fact the output is
Code:
sending 'recovery' (5378 KB)...
OKAY [ 2.431s]
writing 'recovery'...
OKAY [ 1.739s]
finished. total time: 4.170s
but it's stucked and I need to reboot manually.
Any idea?
Kito92 said:
I realized I'm screwed. But I've tried something...
When I go run the fastboot mode and delete a partition, for example:
Code:
fastboot erase recovery
works, and after I can run other command. But if I use:
Code:
fastboot flash recovery recovery.img
seems it works, in fact the output is
Code:
sending 'recovery' (5378 KB)...
OKAY [ 2.431s]
writing 'recovery'...
OKAY [ 1.739s]
finished. total time: 4.170s
but it's stucked and I need to reboot manually.
Any idea?
Click to expand...
Click to collapse
I have the same. Im on an ICS bootloader due to having to run nvflash to get it back to that point.
I have fastboot access i can send a recovery image over to it (twrp 2.5 ics.img) however when i reboot it i dont see the recovery!
PLEASE PLEASE PLEASE Someone help
Long story short, I tried to flash new rom on my Mt2-L02 mate2 and failed and its bootlooping (at Huawei Ascend screen and keep rebooting) now. using the SDcard udload to load new rom don't work either. I cannot go into recovery, or boot into system.
My phone is bootloader unlocked, so I tried to flash (extract from a rom) boot.img, recovery.img and is ok but when flashing system.img, it stucked in writing 'system'... for long time.... so I tried fastboot erase system -w and get FAILED (remote: Command not allowed)... why is it so? my phone is already unlocked. I tried unlock again and flash the system.img, same problem.
So... I'm screwed?
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
kimtyson said:
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
Click to expand...
Click to collapse
Only have 1 pc, yes, I'm flashing MT2-L02 ROM, tried alot of version but discovered only these version rom (b408, b603, b606, b607) able to write the system.img, original out of box android version for my phone is 4.4.2. but still bootlooping after flashing boot.img, recovery.img and system.img. I think only custom recovery can save now, but there is none for this model... or maybe there is no hope for my phone? Maybe my phone got some system modified lock so that I'm not able to erase using flashboot?
C:\adb>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
C:\adb>fastboot erase data
erasing 'data'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
If I'm able to erase those, I'm might solved the bootlooping problem..
Try using this thread as reference, http://forum.xda-developers.com/asc...to-fix-soft-bricked-phone-using-twrp-t2886630. It's for a different model so just use your stock ROM in place of the L03 ROM. I'm not sure how to help beyond that. There has to be a way to return to stock on the L02.
Maybe this message is late, pls try following
http://pan.baidu.com/s/1dDpc4eP
http://www.huaweirom.com/rom/mate2/2619.html
usb flash instructions:
http://www.huaweirom.com/guide/2621.html
You may need to use google translate since all the info is in Chinese
Basically they are saying you should use B117 if B4xx not working.
Hello. Today i tried to flash the phone to the stock ROM twice but it didnt work probably cause unlocked bootloader and custom recovery (TWRP).
So i brick the phone and now i cant access the rom or the recovery. All i can do is access the fastboot mode. I tried to install the new recovery through fastboot but it doesnt work.
I tried the twrp 3.0.2.0 and 3.0.1.0 for yuga.
Code:
C:\Users\Kubo\Downloads\platform-tools>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.342s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.347s
Tried various of commands that i found on google and this forum but nothing worked. I unlocked the bootloader before when i was installing various of custom roms. Could somehow stock rom affect the bootloader when i was flashing through flashtool ? I tried to only boot the recovery from the img, the command worked but the recovery did not boot.
Code:
C:\Users\Kubo\Downloads\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.341s]
booting...
OKAY [ 0.033s]
finished. total time: 0.378s
Tried to check the status of bootloader but the command is just showing ... and nothing happend. Tried to get the IMEI through fastboot getvar command but no output is given. Im desperate. Sorry for english not my native language. I'll appreciate all the help.
I'm fixing a friend's cell phone, I had restore stock ROM with SP Flashtools because it did not start, when doing it, and system boot, all most app crashing and still keeps all the data as photos and settings. I enter the custom recovery, and I do all the Wipes, when boot again, it is as if the wipe was not executed, I deleted some files from the internal memory, restart and the files appear again, I have tried to flash a custom recovery by ADB and see this error :
% fastboot flash recovery TWRP.img
sending 'recovery' (8748 KB)...
OKAY [ 0.331s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.337s
I do not know what else to do, since it is impossible to install or run an application to root and install a custom recovery with the application because the cell phone only show crashing mensages.
Bump!!