please can someone point me to the stock ruu?? i flashed a rom and it bootlooped and now i cant get into recovery.. flashed all recoveries available and it still wont boot into recovery. can get into bootloader. i relocked the bootloader and i cant find a stock ruu anywhere. please someone help
There isn't a stock RUU
the fix for your problem is fastboot erase cache
C:\Android>fastboot erase cashe
erasing 'cashe'...
FAILED (remote: not allowed)
finished. total time: 0.003s
thats what im getting in cmd
oneslow5oh said:
C:\Android>fastboot erase cashe
erasing 'cashe'...
FAILED (remote: not allowed)
finished. total time: 0.003s
thats what im getting in cmd
Click to expand...
Click to collapse
fastboot erase cache
fix your spelling and try again
cache not cashe
designgears said:
fastboot erase cache
fix your spelling and try again
Click to expand...
Click to collapse
im a complete idiot! thanks guys. really appreciate it
sorry if its a noob questiomn but how do i mount the phone to my computer to put a rom on it now...? im using cwm touch v6.0.3.1 it says error mounting sdcard
Related
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
I had niles business rom on my phone and it kept messing up on me. so i downloaded the toolkit for s-off. After many tries i was able to get s-off. Now here is where my problem is there is no recovery on my phone now and when i try and do a fastboot in the cmd for my phone it will not write the Amon Ra recovery file. I now get this.
C:\Android\sdk-tools>fastboot flash boot boot.img
sending 'boot' (3896 KB)... OKAY [ 0.814s]
writing 'boot'... FAILED (remote: not allowed)
finished. total time: 1.130s
what should i do?
eggbert81 said:
I had niles business rom on my phone and it kept messing up on me. so i downloaded the toolkit for s-off. After many tries i was able to get s-off. Now here is where my problem is there is no recovery on my phone now and when i try and do a fastboot in the cmd for my phone it will not write the Amon Ra recovery file. I now get this.
C:\Android\sdk-tools>fastboot flash boot boot.img
sending 'boot' (3896 KB)... OKAY [ 0.814s]
writing 'boot'... FAILED (remote: not allowed)
finished. total time: 1.130s
what should i do?
Click to expand...
Click to collapse
So your trying to flash it as a boot.img? Amon Ra should be flashed as fastboot flash recovery recovery.img. Also if your on stock HBoot i think you need a modified HBoot for fastboot commands or unlocked eve on S-Off
sorry should have been
C:\Users\jamie\Desktop\Fastboot>fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
sending 'recovery' (7078 KB)... OKAY [ 1.426s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.742s
eggbert81 said:
sorry should have been
C:\Users\jamie\Desktop\Fastboot>fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
sending 'recovery' (7078 KB)... OKAY [ 1.426s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.742s
Click to expand...
Click to collapse
Do you have a stock HBoot? if so i think it has to be unlocked for fastboot commands even on s-off unless you have a modified Hboot that allows for fastboot commands while locked.
jon7701 said:
So your trying to flash it as a boot.img? Amon Ra should be flashed as fastboot flash recovery recovery.img. Also if your on stock HBoot i think you need a modified HBoot for fastboot commands or unlocked eve on S-Off
Click to expand...
Click to collapse
i was reading about flashing the boot image so i also tried to take the boot.img out of CleanROM Standard 4.5 and tried to flash the boot and that didnt work either
i do have s-off and i can get my phone to say FASTBOOT USB but everything i try and write to it says sending OKAY then writing FAILED ( remote: not allowed)
eggbert81 said:
i was reading about flashing the boot image so i also tried to take the boot.img out of CleanROM Standard 4.5 and tried to flash the boot and that didnt work either
i do have s-off and i can get my phone to say FASTBOOT USB but everything i try and write to it says sending OKAY then writing FAILED ( remote: not allowed)
Click to expand...
Click to collapse
Well if your bootloader is locked i would unlock it or get a modified bootloader that allows fastboot commands while locked. If those dont work then youll have to ask a dev
somehow i didnt even notice that was locked. ok got recovery on. now going to try and get a rom on it. with all this headache i almost miss my GNex but it has tons of issues
eggbert81 said:
somehow i didnt even notice that was locked. ok got recovery on. now going to try and get a rom on it. with all this headache i almost miss my GNex but it has tons of issues
Click to expand...
Click to collapse
Glad i could help :highfive:
got it all to work. Thanks
eggbert81 said:
got it all to work. Thanks
Click to expand...
Click to collapse
i didt understand much
still a newbie
first how do u know if the bootloader is locked or not
and how did u workout the problem
im having the same issue please help
& thnx:good:
When your in bootloader there will be a big pink highlight that says locked or unlocked
Sent from my ADR6425LVW using xda app-developers app
Deleted
hay sorry if i ask about noob question..i have 4G LTE devices..before i try S-Off with dirtyRacun
but i got QHSUSB_DLOAD and my device brick..then i follow racunhunter tutor my device can normal again..
but my bootloader still S-ON..if i connect USB try mass storage just reconnect can't mount my sd card
i want try RUU but my devices still Unlocked.try lock with fastboot
Code:
C:\Fastboot>fastboot oem lock
...
FAILED (command write failed (Unknown error))
finished. total time: 0.564s
what my problem ? any wrong step ? or my devices damage ?
sorry for bad englishh
littlekura said:
hay sorry if i ask about noob question..i have 4G LTE devices..before i try S-Off with dirtyRacun
but i got QHSUSB_DLOAD and my device brick..then i follow racunhunter tutor my device can normal again..
but my bootloader still S-ON..if i connect USB try mass storage just reconnect can't mount my sd card
i want try RUU but my devices still Unlocked.try lock with fastboot
Code:
C:\Fastboot>fastboot oem lock
...
FAILED (command write failed (Unknown error))
finished. total time: 0.564s
what my problem ? any wrong step ? or my devices damage ?
sorry for bad englishh
Click to expand...
Click to collapse
fastboot oem lock is the correct command are you in a writable folder?
bigdaddy619 said:
fastboot oem lock is the correct command are you in a writable folder?
Click to expand...
Click to collapse
yes writeable folder but same can't relock just failed command write failed <unknown eror>
have advice how to relock my bootloader ?
littlekura said:
yes writeable folder but same can't relock just failed command write failed <unknown eror>
have advice how to relock my bootloader ?
Click to expand...
Click to collapse
Is your PC seeing your phone when you plug the USB in ?
bigdaddy619 said:
Is your PC seeing your phone when you plug the USB in ?
Click to expand...
Click to collapse
yes i can see my HTC and device manager my PC..i use windows 7 x64
i try reinstall driver HTC too..but still same problem
try a different folder to run the command :confused
bigdaddy619 said:
try a different folder to run the command :confused
Click to expand...
Click to collapse
i try with different folder but still problem
FAILED (command write failed (Unknown error))
still need help..get stuck to relock bootloader
FAILED (command write failed (Unknown error))
littlekura said:
still need help..get stuck to relock bootloader
FAILED (command write failed (Unknown error))
Click to expand...
Click to collapse
I found out you need to flash the stock recovery then relock
Sent from my MB855 using xda app-developers app
bigdaddy619 said:
I found out you need to flash the stock recovery then relock
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
ok thanks very much bigdady i will flash stock recovery first
@bigbaddy
i try flash TWRP 2.3 but
Code:
just sending 'recovery' (7424 KB)...
wait 10minute not work then stop process
Code:
C:\Fastboot>fastboot flash recovery openrecovery.img
sending 'recovery' (7424 KB)...
FAILED (status read failed (Too many links))
finished. total time: 3.064s
or i wrong recovery ? can help upload it
i look command fastboot dont work..ex i try fastboot erase cache..same just waiting
sorry if i ask too much..i need help
Ive had something similar
http://forum.xda-developers.com/showthread.php?t=2052384
load the bootloader and see if it actually installed. If not try downloading android sdk tools and run cmd from c:/program files/android/android-sdk/platform-tools
littlekura said:
@bigbaddy
i try flash TWRP 2.3 but
Code:
just sending 'recovery' (7424 KB)...
wait 10minute not work then stop process
Code:
C:\Fastboot>fastboot flash recovery openrecovery.img
sending 'recovery' (7424 KB)...
FAILED (status read failed (Too many links))
finished. total time: 3.064s
or i wrong recovery ? can help upload it
i look command fastboot dont work..ex i try fastboot erase cache..same just waiting
sorry if i ask too much..i need help
Click to expand...
Click to collapse
http://htcevohacks.com/htc-evo-4g-l...tc-evo-4g-lte-unlock-bootloadertwrp-recovery/
follow it and when you get to the part where you unlock it will be lock..
are you sure your running the command from the same folder..????
locate the folder and press SHIFT and right mouse click to open the command window here, where the folder is you want to work with
Pic
isaelperez81 said:
http://htcevohacks.com/htc-evo-4g-l...tc-evo-4g-lte-unlock-bootloadertwrp-recovery/
follow it and when you get to the part where you unlock it will be lock..
are you sure your running the command from the same folder..????
locate the folder and press SHIFT and right mouse click to open the command window here, where the folder is you want to work with
Click to expand...
Click to collapse
my phone is unlocked..but i want lock boot again..
-HTC driver done
every i try command fast boot
Code:
example :
fastboot oem lock
C:\Fastboot>fastboot oem lock
...
FAILED (command write failed (Unknown error))
finished. total time: 0.564s
trying fastboot erase cache stil same problem
stuck waiting time same flash recovery
wait 10menit nothing happen
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.
Everytime I type the command 'fastboot oem unlock', the screen says;
OKAY [ 0.002s]
finished. total time: 0.002s
but then when I want to flash a recovery it says;
target reported max download size of 1073741824 bytes
sending 'recovery' (15482 KB)...
OKAY [ 0.498s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)<<< Why does this happen? -_-
finished. total time: 0.501s
Anybody has a solution for this?
Have you tried just flashing stock recovery? Does it say that for everything you try and flash? A lot of people are trying these shortcuts to try and upgrade bootloader. Though most can work the safest bet is to flash original stock recovery and upgrade from there. You might be looking at going through the hard brick guide.
seems like you locked the bootloader while you are rooted...iam stack on same step too...
Exodusche said:
Have you tried just flashing stock recovery? Does it say that for everything you try and flash? A lot of people are trying these shortcuts to try and upgrade bootloader. Though most can work the safest bet is to flash original stock recovery and upgrade from there. You might be looking at going through the hard brick guide.
Click to expand...
Click to collapse
But everything else works. And yeah, I did try flashing the stock recovery too
Fastboot oem unlock>fastboot reboot>doesn't ask about wiping
I've followed every tutorial they all say that after requesting oem unlock, you can verify the unlock was successful with fastboot oem devices-info> device tampered-false, device unlock-true, then fastboot reboot> system reboot, but it does NOT ask to wipe the data. Am I missing something?
Ubuntu_noobi said:
I've followed every tutorial they all say that after requesting oem unlock, you can verify the unlock was successful with fastboot oem devices-info> device tampered-false, device unlock-true, then fastboot reboot> system reboot, but it does NOT ask to wipe the data. Am I missing something?
Click to expand...
Click to collapse
Not necessarly.
If it 's device unlock-true , you're OK. If not...