Database Develop

Boot Loop - Help Please

I've had my NC rooted for 3 weeks. No probs. I decided to update to 1.0.1 to see if wifi was better and so I entered the adb command to force system update and all seemed to be well. After that it went into a boot loop.
I forced another "update" by powering down 8x during bootup. It reinstalled and then same problem. I then tried the directions at nookdevs to fix boot loops. I couldn't ssh into the NC, but to my surprise I could use adb, but I can't do the listed commands because I get "permission denied".
I did an adb logcat and I get nonstop info going by, mostly looking for stuff that shouldn't be there anymore, i.e. apps I loaded when it was rooted. Dalvik cache??
So, long story short, I've tried a system wipe 4x now and I'm stuck in an endless boot loop BUT I do have adb access. What now?

Power, +, N button doesn't work either?

norkoastal said:
Power, +, N button doesn't work either?
Click to expand...
Click to collapse
Haha. Good call. That did work. Bigtime brain fart. Trying all the hard stuff and not the easiest. What's the diff between the two methods?

GTOMEX09 said:
Haha. Good call. That did work. Bigtime brain fart. Trying all the hard stuff and not the easiest. What's the diff between the two methods?
Click to expand...
Click to collapse
Head over to Nook Devs for the breakdown of the two.. Both methods are requied for using the newest AutoNooter... Glad to hear the device is still in working order.

Stuck in Boot Loop
Noob here with a problem. I’ve had my NC rooted for 5 days and the rooting went well. I had all my favorite android apps up and running. However I was experiencing random reboots (2-3 times per day). So, I decided to unroot and let the 1.0.1 update install and then I was going to use Auto-Nooter 2.12.18 to get everything back.
I did the 8X reboot thing and after reloaded, the NC went into a boot loop. The first thing I tried to do was the n, volume+ and power button. It simply went back to the boot loop.
I immediately put the auto-nooter sdcard in the NC, plugged in the usb to the pc. As opposed to the other times I did this, I got no visual indication that the PC recognized or activated the NC. I waited the full 5 minutes and removed it. The boot animation had changed, but the NC stayed in the boot loop.
I then searched and found this on nookdev.com (nookdevs.com/NookColor_Fix_Boot_Loops ). Following the instructions there, I installed putty.exe in the same folder as adb.exe. Putty would start and the session window would open, but I could not type or paste anything into the ssh screen. I assumed I had a bad download so I redid that and the install – no luck. I then searched and found another site from which I could download putty.exe, same results.
Before I ejected the NC I opened the command line window and I did adb devices and it came back with nothing. So now my NC is not recognized by the PC (and was before all this).
Can anyone point me in the right direction? Any help with the putty ssh screen issue? Any help will be appreciated.

Geezer Squid said:
I then searched and found this on nookdev.com (nookdevs.com/NookColor_Fix_Boot_Loops ). Following the instructions there, I installed putty.exe in the same folder as adb.exe. Putty would start and the session window would open, but I could not type or paste anything into the ssh screen. I assumed I had a bad download so I redid that and the install – no luck. I then searched and found another site from which I could download putty.exe, same results.
.
Click to expand...
Click to collapse
Out of desperation I downloaded putty.exe again and it worked this time. Using the script on the nookdev.com website, the NC booted. I then did the data wipe and the 8X reset. I'm now back to stock (mostly) and I'll see if it updates tonight. If not, I'll force it tomorrow and don the new auto-nooter.
I'm learning!!

Glad you fixed yours too. This device is nearly impossible to brick unless you deliberately try to. Definitely easy to undo hard work, but hard to brick.

I have the same problem. Minutes after rooting with autonooter, my Nook restarted and I didn't even set up ADB access. I tried reseting several times with no luck Please help!!

Mine is currently stuck in a boot loop as well. I did not update to the newer firmware it auto-updated and jacked everything up. Pretty upset right now.
I know I can reset the device but I need to get the data from it first. I have the entire storage full of data that I need. It will not boot at all and if this gets erased i'll more than likely end up returning the device and purchasing something that I won't have this problem with every update.

Unfortunately, there aren't many devices that will automatically backup all your important data to external media without you having to take some action on your own to set that up.

hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?

Mbside said:
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Click to expand...
Click to collapse
Well, I'm not an expert, but I have been through this kind of thing. I would think you have two possibilities. One would be to put the nooter sdcard back in and hook it to the computer again. If it isn't very corrupted, it may automatically reload from the nooter sdcard.
If that won't work, then I think it's time to do the 3 finger data wipe and then the 8X reboot thing. You can then redo the nooter sdcard thing.
Good luck.

Mbside said:
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Click to expand...
Click to collapse
EXACT Same thing happened to me and a friend when using autonooter and 1.0.1. I think there is a problem with autonooter or 1.0.1 messing up the booting process. I wonder whats wrong So I was able to do the 8X reboot thing and get back to stock 1.0.0 and from here I'll try to attempt to use autonooter for 1.0.1. But I'm staying with 1.0.0 until Froyo next month.

thanks! the 8x thing worked good, I did the whole auto noot process again and it works at all except by this market issue

Phone suddenly acting up need some help

I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.

whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery

Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....

send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too

The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....

whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.

[Q] Boot lopp w/ AP, Plz help.

Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!

I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.

I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?

Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....

Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.

[Q] Bootloop, can't get phone to stay in Download mode to reflash

Hi all
I reflashed an old i9000 with CM10.1 for my wife recently, and everything seemed to be working fine. Then it started behaving a bit funny and this week it started rebooting at random. I thought "no worries, I'll just do a fresh flash with stock GB".
However, before I could even give that a go the phone started acting even weirder. As soon as I put the battery in it powers on (without me even pushing the button) but it resets every time it hits the Samsung splash screen. Earlier today I could get it to go into CWM recovery and after clearing cache I actually got it to boot up. But by the time I had downloaded the stock GB files the phone was just constantly resetting at the Samsung logo and now I can't even get it to load CWM recovery using the 3-button method.
I can get it to enter Download mode, and it shows up in Odin just fine. But within 5 seconds it resets itself again so I can't actually perform a flash.
Any suggestions? Or is the phone just plain busted?

mrfurion said:
Hi all
I reflashed an old i9000 with CM10.1 for my wife recently, and everything seemed to be working fine. Then it started behaving a bit funny and this week it started rebooting at random. I thought "no worries, I'll just do a fresh flash with stock GB".
However, before I could even give that a go the phone started acting even weirder. As soon as I put the battery in it powers on (without me even pushing the button) but it resets every time it hits the Samsung splash screen. Earlier today I could get it to go into CWM recovery and after clearing cache I actually got it to boot up. But by the time I had downloaded the stock GB files the phone was just constantly resetting at the Samsung logo and now I can't even get it to load CWM recovery using the 3-button method.
I can get it to enter Download mode, and it shows up in Odin just fine. But within 5 seconds it resets itself again so I can't actually perform a flash.
Any suggestions? Or is the phone just plain busted?
Click to expand...
Click to collapse
I'm just going to answer my own question as I've solved the problem but it may benefit someone else to know how.
It got to the point where the phone wasn't even booting to the Samsung splash screen, but I could still get Download mode to show up for 5 seconds (not long enough to flash). Then in a moment of desperation I got the original Samsung microUSB cable and plugged that in, and booted into Download mode again. This time Download mode stuck! And I was able to flash a clean GB ROM which is now working fine.
So the take-out from my experience is this: sometimes you really do have to use the original Samsung USB cable.
Weird.

Thanks for reporting howto ...:good: good to know
mrfurion said:
I'm just going to answer my own question as I've solved the problem but it may benefit someone else to know how.
It got to the point where the phone wasn't even booting to the Samsung splash screen, but I could still get Download mode to show up for 5 seconds (not long enough to flash). Then in a moment of desperation I got the original Samsung microUSB cable and plugged that in, and booted into Download mode again. This time Download mode stuck! And I was able to flash a clean GB ROM which is now working fine.
So the take-out from my experience is this: sometimes you really do have to use the original Samsung USB cable.
Weird.
Click to expand...
Click to collapse

mrfurion said:
I'm just going to answer my own question as I've solved the problem but it may benefit someone else to know how.
It got to the point where the phone wasn't even booting to the Samsung splash screen, but I could still get Download mode to show up for 5 seconds (not long enough to flash). Then in a moment of desperation I got the original Samsung microUSB cable and plugged that in, and booted into Download mode again. This time Download mode stuck! And I was able to flash a clean GB ROM which is now working fine.
So the take-out from my experience is this: sometimes you really do have to use the original Samsung USB cable.
Weird.
Click to expand...
Click to collapse
I have a similar issue where I'm trying to flash my stock ROM on my Epic4gTouch. When it opens up the download mode error I start to flash and all seems to work before it reboots. Every 5 seconds. I tried the original cable and it did not help. Any ideas??

NerdsBestAdvice said:
I have a similar issue where I'm trying to flash my stock ROM on my Epic4gTouch. When it opens up the download mode error I start to flash and all seems to work before it reboots. Every 5 seconds. I tried the original cable and it did not help. Any ideas??
Click to expand...
Click to collapse
put the cable and press button power the phone go mode charging at this time make the phone in download mode
its ok for me:good:

Soft Brick / Hard Brick ? Help...

Hi, well it looks like i have probably hard bricked my phone. After updating to nougat i decided to do afresh clean install. I wanted my phone to as if i had just bought it and came with nougat/emui 5 installed. So i did a factory reset from within the settings menu. But then i thought i would completely erase everything and start from the latest build before nougat, so emui 4.1.2/ marshmallow. So after wiping all the partitions in twrp and then doing a volume up + power to do complete factory wipe followed by using the three button method to install the B130 UPDATE.APP in dload folder on my sdcard, all worked as expected. The update completed at 100% and then rebooted. So there i am waiting for my phone to boot to start the setup process as i have done dozens of times before...BUT...my phone will not boot to the initial setup wizard. It just stays stuck on the Honor logo pulsing animation for ever and ever and ever!!!!!!
So i do the volume up + power button to get to stock recovery and do factory wipe and cache wipe as well. It works as expected so i reboot and once again use the 3 button method to install the update.app on my sdcard. That works as expected and at 100% says its succeeded and reboots. Once again i wait for it to boot to the initial setup wizard but....ALAS...it stays on that DAMN pulsing Honor logo. Ive tried rebooting it several times, redoing the factory wipe and install several times, but nothing. Ive gone into fastboot mode (volume down + power) to try and flash the boot.img and system.img ive extracted from update.app but get the error message -- remote: command failed -- and the same if i try to unlock bootloader. Obviously its not going to work because my bootloader isnt unlocked and nor can i got in to developer settings to enable oem unlock and turn USB debugging on because my phone wont boot past that bloody honor logo.
The only thing i havent done yet is to use eRecovery but i dont have broadband and i doesnt seem to work over public wifi! So i will go to my friends tomorrow and use their broadband and hopefullly eRecovery will download/restore the latest firmware. The only other thing i can think of is to download the original nem-l51c432B102 that came with my phone when bought, extract the update.app file and replace the B130 i have on my sdcard dload folder at present.
Sorry for such a long post but i wanted to expalin evrything in detail to hopefully resolve my problem without going backwards and forwards with questions and answers and taking for ever.
So ANYONE and EVERYONE who managed to read the whole post, if you have even the slightest idea of how to get my phone working, please oh please share it with me. Also my phone is still under warranty so if i needed to send it to a huawei centre to get it fixed would they do it and do it for free??? because eseentialy all i did was a factory wipe/reset and install a frmware and it goes KAPUT!! thats not my fault right????!!???
Thank you to one and all for any wisdom you can share. :crying::crying:

iantechie1979 said:
Hi, well it looks like i have probably hard bricked my phone. After updating to nougat i decided to do afresh clean install. I wanted my phone to as if i had just bought it and came with nougat/emui 5 installed. So i did a factory reset from within the settings menu. But then i thought i would completely erase everything and start from the latest build before nougat, so emui 4.1.2/ marshmallow. So after wiping all the partitions in twrp and then doing a volume up + power to do complete factory wipe followed by using the three button method to install the B130 UPDATE.APP in dload folder on my sdcard, all worked as expected. The update completed at 100% and then rebooted. So there i am waiting for my phone to boot to start the setup process as i have done dozens of times before...BUT...my phone will not boot to the initial setup wizard. It just stays stuck on the Honor logo pulsing animation for ever and ever and ever!!!!!! So i do the volume up + power button to get to stock recovery and do factory wipe and cache wipe as well. It works as expected so i reboot and once again use the 3 button method to install the update.app on my sdcard. That works as expected and at 100% says its succeeded and reboots. Once again i wait for it to boot to the initial setup wizard but....ALAS...it stays on that DAMN pulsing Honor logo. Ive tried rebooting it several times, redoing the factory wipe and install several times, but nothing. Ive gone into fastboot mode (volume down + power) to try and flash the boot.img and system.img ive extracted from update.app but get the error message -- remote: command failed -- and the same if i try to unlock bootloader. Obviously its not going to work because my bootloader isnt unlocked and nor can i got in to developer settings to enable oem unlock and turn USB debugging on because my phone wont boot past that bloody honor logo. The only thing i havent done yet is to use eRecovery but i dont have broadband and i doesnt seem to work over public wifi! So i will go to my friends tomorrow and use their broadband and hopefullly eRecovery will download/restore the latest firmware. The only other thing i can think of is to download the original nem-l51c432B102 that came with my phone when bought, extract the update.app file and replace the B130 i have on my sdcard dload folder at present.
Sorry for such a long post but i wanted to expalin evrything in detail to hopefully resolve my problem without going backwards and forwards with questions and answers and taking for ever.
So ANYONE and EVERYONE who managed to read the whole post, if you have even the slightest idea of how to get my phone working, please oh please share it with me. Also my phone is still under warranty so if i needed to send it to a huawei centre to get it fixed would they do it and do it for free??? because eseentialy all i did was a factory wipe/reset and install a frmware and it goes KAPUT!! thats not my fault right????!!???
Thank you to one and all for any wisdom you can share. :crying::crying:
Click to expand...
Click to collapse
Can you please edit your post ? Add some space, here and there if you want some help... It is nothing but pain for both eyes and mind to read you.
Onto related topic, did you manage to get your phone back to a functionnal state ? Note that the boot sequence can take time after a wipe so maybe it's not broken at all.
As for eRecovery, it never helped me to restore my device, tried on two different Wi-Fi networks after two completely unrelated issues.
Concerning warranty, I guess it depends on your country and where you bought your phone. I went to the carrier which provided me mine this morning since I ended up with a strong brick last night and I'll get a new phone in a couple of weeks.

Zarou said:
Can you please edit your post ? Add some space, here and there if you want some help... It is nothing but pain for both eyes and mind to read you.
Onto related topic, did you manage to get your phone back to a functionnal state ? Note that the boot sequence can take time after a wipe so maybe it's not broken at all.
As for eRecovery, it never helped me to restore my device, tried on two different Wi-Fi networks after two completely unrelated issues.
Concerning warranty, I guess it depends on your country and where you bought your phone. I went to the carrier which provided me mine this morning since I ended up with a strong brick last night and I'll get a new phone in a couple of weeks.
Click to expand...
Click to collapse
finally a reply! okay so ill edit my post once ive finished replying to you. First off thanks for taking your time to read my post, i am most greatfull. In response to your questions,suggestions i can tell you:
i went to my friends, connected to their broadband and attempted to use eRecovey to update/restore my device. ALAS it did not work! I tried several times and it gets to downloading package from server only to end in a FAIL.. I got home tried connecting to public wifi and doing eRecovery but it just fails. So like you I have never managed to get eRecovery to work.
As for the booting sequence, as i explained before, whether i access stock recovery and wipe cache and wipe phone it does this no problem, reboots, only to get stuck on the honor logo boot animation. The same goes for installing updatte.app with three button method. it says its installed succesfully but does not get past the honor logo boot animation. Unfortunately your suggestion that it might just take a long time to boot is not the case I have left it for hours you see and it never gets to the setup wizard :crying:
As for warranty, i am in uk, bought the phone via amazon, and it was unlocked, so not from a carrier like you. So i guess ill just have to find my nearest huawei service centre and have them look at it.
Does anyone know the procedure as far as doing this. Do i phone them or email my problem and then send my phone to them or what?? Any help is very welcome.
Thanks for your time and patience.

Please, please help...i'm desperate
So sorry for my original long post people, i simply wanted to give as much detail and info as possible because being vague doesnt help anyone. It seems that might have worked against me.
Please,please any suggestions would be appreciated to the N'th degree! I have tried everything i can think of and i am truly desperate now. I dont understand why i cant get it to work...
I can go into stock recovery and wipe the cach and do factory reset and that works fine, no errors.
I can hold the 3 buttons down to install the firmware package(ive got update.app from B130 build) and that works fine, gets to 100% and says 'success' and then reboots, with no errors.
But either way the phone refuses to boot past the honor logo boot animation and ive left it for hours hoping,praying, it will work after the 32nd time...
I can access fastboot but that is useless because my bootloader is not unlocked and i cant get to developer options to enable 'usb debugging' and 'oem unlock'. So i just get error message 'remote: Command Failed' with any command i type.
But thats madness, i cant comprehend why it wont boot because everything seems to work!?!
There has to be a way to get my device functioning again.
I am pulling my hair out, i am at a complete loss, it doesn't make sense. PLEASE ANYONE ..... please help....
Thanks HONOR-able enthusiasts for any help, no matter how small! :good: :fingers-crossed: :angel:

iantechie1979 said:
So sorry for my original long post people, i simply wanted to give as much detail and info as possible because being vague doesnt help anyone. It seems that might have worked against me.
Please,please any suggestions would be appreciated to the N'th degree! I have tried everything i can think of and i am truly desperate now. I dont understand why i cant get it to work...
I can go into stock recovery and wipe the cach and do factory reset and that works fine, no errors.
I can hold the 3 buttons down to install the firmware package(ive got update.app from B130 build) and that works fine, gets to 100% and says 'success' and then reboots, with no errors.
But either way the phone refuses to boot past the honor logo boot animation and ive left it for hours hoping,praying, it will work after the 32nd time...
I can access fastboot but that is useless because my bootloader is not unlocked and i cant get to developer options to enable 'usb debugging' and 'oem unlock'. So i just get error message 'remote: Command Failed' with any command i type.
But thats madness, i cant comprehend why it wont boot because everything seems to work!?!
There has to be a way to get my device functioning again.
I am pulling my hair out, i am at a complete loss, it doesn't make sense. PLEASE ANYONE ..... please help....
Thanks HONOR-able enthusiasts for any help, no matter how small! :good: :fingers-crossed: :angel:
Click to expand...
Click to collapse
How comes you have TWRP with a locked bootloader ?

Zarou said:
How comes you have TWRP with a locked bootloader ?
Click to expand...
Click to collapse
??? hi, I.m sorry, i think you must of misread some of my post. I dont blame you, it was bloody long and confusing!
I only mentioned twrp in the very beggining to run you through the steps to my never ending being stuck on honor logo boot animation. I used TWRP to wipe all partitions and format. From there i used 3 button method to install the update.app(B130) on my sd-card. this was succesfull, no errors and rebooted. I didn't expect any problems. But as i explained it never gets past boot logo.
Obviously now, twrp has gone, i am back to stock recovery and my bootloader is locked.
*I can access stock recovery to wipe cache and wipe the phone no problem and all works with no error messages.
*I can access fastboot(bootloader) but the fastboot commands are useless because my bootloader is locked once again and i cant turn on usb debugging or oem unlock in developper options....because my phone wont boot past honor logo...
*Three button method works everytime, 100% success, no errors, reboots but guess what?? IT WONT GET PAST THAT DAMN HONOR BOOT LOGO!!!!!!!!!
Ive tried everything, but NO LUCK. I came up with this idea today though--- download theB130 rollback from nougat to MarshMallow update.zip. Extract the update.app and put that in my sd-card/dload folder and do 3 button install method.
I might even do the same with the nougat B350 just to cover all bases. So i am downloading now, gonna cross my fingers and any other body parts, pray to all the gods...and hopefully i wont be a crying,sniveling,howling piece of mess by tomorrow.
UNLESS OF COURSE SOMEONE HAS THE KNOWLEDGE I SEEK AND IS WILLING TO SHARE IT :fingers-crossed:
thanks Honor-able friends....

iantechie1979 said:
??? hi, I.m sorry, i think you must of misread some of my post. I dont blame you, it was bloody long and confusing!
I only mentioned twrp in the very beggining to run you through the steps to my never ending being stuck on honor logo boot animation. I used TWRP to wipe all partitions and format. From there i used 3 button method to install the update.app(B130) on my sd-card. this was succesfull, no errors and rebooted. I didn't expect any problems. But as i explained it never gets past boot logo.
Obviously now, twrp has gone, i am back to stock recovery and my bootloader is locked.
*I can access stock recovery to wipe cache and wipe the phone no problem and all works with no error messages.
*I can access fastboot(bootloader) but the fastboot commands are useless because my bootloader is locked once again and i cant turn on usb debugging or oem unlock in developper options....because my phone wont boot past honor logo...
*Three button method works everytime, 100% success, no errors, reboots but guess what?? IT WONT GET PAST THAT DAMN HONOR BOOT LOGO!!!!!!!!!
Ive tried everything, but NO LUCK. I came up with this idea today though--- download theB130 rollback from nougat to MarshMallow update.zip. Extract the update.app and put that in my sd-card/dload folder and do 3 button install method.
I might even do the same with the nougat B350 just to cover all bases. So i am downloading now, gonna cross my fingers and any other body parts, pray to all the gods...and hopefully i wont be a crying,sniveling,howling piece of mess by tomorrow.
UNLESS OF COURSE SOMEONE HAS THE KNOWLEDGE I SEEK AND IS WILLING TO SHARE IT :fingers-crossed:
thanks Honor-able friends....
Click to expand...
Click to collapse
OK, sorry for the misunderstanding. Yeah, try that and if this is still not working, I guess all you can do is try the same with other packages.