Database Develop

[Q] Urgent: Nexus failing to boot

Hi all,
I have had my N1 for 1year and two weeks now (yes, warranty just expired). I was charging the device and it seemed to overheat and reboot. I unplugged it, took the battery out, let it rest for a bit and tried to boot it again. The phone now gets stuck on the X logo (not moving) and never boots.
I'm currently abroad (in the UK) and can't have it sent back for repair (I'd have to pay the repair too).
Will rooting the phone and installing an alternate OS fix my phone?
Is there any way to get HTC to honor the warranty after two weeks of expiration (I've been getting this problem for a while now, but that was only an issue if I made extensive use of the device while charging, which I almost never do so I didn't bother.)
Is there any way to fix this issue without messing with rooting? I'm abroad right now and all I want is my phone to work.
Any suggestions are welcome.

Try booting into bootloader from power off (vol- pwr) if that doesn't work then try the 3 figure salute (pwr vol- tb) your phone should boot into fastboot then just select bootloader.
If either of these work the your good you can get the static x fixed all you need to do is passimg (search wiki if you don't know what it is) as for the charging problem passimg will factory reset the phone so if that doesn't fix it then no you'll need to try rooting or it might be hardware.

Yes, I'm able to go into the bootloader.
I tried clearing the storage, choosing fastboot, etc. The phone seems to be working, just won't boot past the static X.
From your last reply, you're saying passimg has good chances to fix my phone. What does that involve? Do you have a link to a how-to that I could follow (it would really be a bad time for me to brick my phone, a good how-to would be really appreciated).
Cheers!

Yes passimg is used for many things it just reflashes a shipment ROM to the phone through bootloader. Like I said you can visit the wiki to have a how to here is a link http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials scroll down to "Unroot / Restore your Nexus" then follow the instructions. This should restore you to frg33 then you just need to update back to 2.3.4.
NOTE: this will wipe your data.

Ahh there's a way to unroot the nexus one now!
I had no idea! This is good to know (last time I checked was in December I think).
I will give that passimg a try as soon as I get home.
Can anyone confirm that this ("Attention: Latest stock ROMs don't flash using PASSIMG.ZIP method. Use the provided latest Froyo PASSIMG, and upgrade it after flashing.") means I can still reflash using this if I have the latest ROM (2.3.4) but will simply have to update again after (which I might not do given the issues I'm facing).
Cheers!

Confirmed - Dude is giving you good info... xD

Just to verify, unrooting is not the same as relocking. If you unlocked your bootloader (have a little lock symbol under the X screen), there is no way to relock it.
But the passimg is a good option. It will take you back to an older version of Android, and then you just let the system update itself.
Since you are out of your warranty, I can highly suggest looking into custom firmwares. These give you a lot more features and in many cases, perform better. CyanogenMod is probably the most popular one. These will fully replace your Android OS. CyanogenMod really doesn't even differ in look from stock all that much. Most people probably wouldn't even have a clue they are running something different, except for the stability and performance increases.
You can read up about this stuff in the wiki as well.

Oh, I see, thanks for the info.
I'm actually trying to get the FRG83 passimg file but the link is dead. Does anyone have an alternate one?

Use the FRG33 image

Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?

Try the passimg, but it's possible that you are looking at hardware failure...

ldiamond2 said:
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Click to expand...
Click to collapse
If you are still running stock Android, you can't reboot between installing the recovery and getting into it. Stock Android will replace it. Try to go back to the bootloader and select recovery then, or fastboot to load the recovery, and then use fastboot to boot off of it.
Code:
fastboot flash recovery "c:\location to\recovery.img"
fastboot boot recovery "c:\location to\recovery.img"
Hopefully this will get you into Amon_RA so you can try again.
But the passimg method is used in the bootloader, not in recovery. You don't need a custom recovery to use the passimg method.

Amazing, thanks for pointing out my mistake, that give me a little bit of hope now . (I was at the point where I'd open the thing and look for a broken solder joint.)
I will try this as soon as I get home!
**Edit** I actually am not sure if I really rebooted or went straight to recovery. I'll update this thread tonight.

According to some other people, this would be a common issue with the internal memory dieing.
Is there a utility I can use to check the state of the memory?

None that I know of. Our phone internal memory uses the yaffs2 (Yet Another Flash File System v2) file system. I haven't heard of any programs that can check it.

Same situation
Hello, all. I haven't signed in on here in ages just because I've been so happy with how my Nexus has been running.
I ran into the same problem as OP stated.
I think I have some sort of hardware issue because my phone used to randomly freeze and couldn't be restarted unless I pulled the battery. Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Is there any way to check for hardware damage? My warranty is over as well so I'd have to pay for any repairs to my phone if I sent it in.

If it's running, you can try to pull a log, and see what error reports you get?

andythefan said:
Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Click to expand...
Click to collapse
Your power button might just be dead. Try having the phone plugged into a power source and removing and reinserting the battery. While you are doing that, hold the Volume Down button. This will get you into the bootloader which would allow a passimg to be performed. Hopefully your reboots aren't a hardware problem.

So , after pulling my battery, pulling the sim and the sd card, it finally turned on and went to recovery without freezing. I was able to wipe and reflash cyan 7. It's working well for now, but I'm really afraid this is going to happen again because this isn't the first time that it's just froze repeatedly.
Does anyone know what the problem could be?

Alright,
I did "fastboot flash recovery MYIMG" then "fastboot boot MYIMG", didn't work.
Then I tried "fastboot flash recovery MYIMG" then go to bootloader (without rebooting) and selected recovery.
Still no luck.
It always freezes on the static X logo. What else can I do? Will using passimg be any different (I don't have any way to put the file on the micro SD card but I can manage to do it if it's worth the shot).
Thanks

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.

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.

HELP!! Le2 x526 Not booting Up, nor Charging

Hello Friends,
Yesterday I was chatting on whatsapp and suddenly my le2 restarts, and then a blue splash screen appears and device keeps on booting,
hence I went to recovery and clear the data, but that also didnt help me,
Then i flash the 13s rom via Flashone 1.9 then also same problem happens, sometimes it went to optimizing apps 3 of 4 and again restarts with blue LED, i were unable to switch it off,
after draining the whole battery I keep mobile to charge but now it is not charging, it only showing Red Solid LED Continuously.
Now I am also Unable to boot into recovery or fastboot mode.
I again flash the stock 13s rom via flashone 1.9 , i got success msg but then also mobile is not booting nor it is charging.
Note: I am on complete stock rom on locked bootloader, never unlocked or rooted, used as come in box.
Please give me a solution on this, I have searched everywhere but not getting any solutions.
Thanks in advance

Try to check your USB cable, most of the time charging issue is due to cable

shubham1358 said:
Try to check your USB cable, most of the time charging issue is due to cable
Click to expand...
Click to collapse
Cable is ok. I have another Le2 and it is charging with that cable very well

I am facing same problem. How you solve this issue? Blue led blinks after flashing any rom and bootloop.

xerol said:
Hello Friends,
Yesterday I was chatting on whatsapp and suddenly my le2 restarts, and then a blue splash screen appears and device keeps on booting,
hence I went to recovery and clear the data, but that also didnt help me,
Then i flash the 13s rom via Flashone 1.9 then also same problem happens, sometimes it went to optimizing apps 3 of 4 and again restarts with blue LED, i were unable to switch it off,
after draining the whole battery I keep mobile to charge but now it is not charging, it only showing Red Solid LED Continuously.
Now I am also Unable to boot into recovery or fastboot mode.
I again flash the stock 13s rom via flashone 1.9 , i got success msg but then also mobile is not booting nor it is charging.
Note: I am on complete stock rom on locked bootloader, never unlocked or rooted, used as come in box.
Please give me a solution on this, I have searched everywhere but not getting any solutions.
Thanks in advance
Click to expand...
Click to collapse
I also have the exact same problem. Phone started rebooting as soon as it booted up. Somehow i managed to unlock the bootloader, but to no avail. Can't seems to find any rom which can boot up. So practically i have a bricked device with trwp. Formatted the system and other partitions with twrp, flashed many roms. Still the result is same. Bootloops.

Hi,
try to to reimage your phone with QFIL from this site:
https://www.techpoison.in/2017/12/how-to-flash-letv-le-2-x526-stock.html
I downloaded everything from there, QFIL, Sparse image and drivers. My phone was bricked, but its working normally now. After you flash the image your phone should charge normally, just try to boot it up. In my case i had issues with baseband, not detected, no sim function and no wifi and phone was restarting each 3-4 minutes, but it was operable. Basedband issues can be solved by hard reseting the phone and updating it to 21s using the local update, just put the 21s stock renamed to update.zip to internal storage and run system update. When you get the error - APK missing, just boot it up again and retry the local update, should work fine the second time, i just deleted the update.zip and put back again and ran the update.
---------- Post added at 03:24 PM ---------- Previous post was at 03:18 PM ----------
Forthe55 said:
I also have the exact same problem. Phone started rebooting as soon as it booted up. Somehow i managed to unlock the bootloader, but to no avail. Can't seems to find any rom which can boot up. So practically i have a bricked device with trwp. Formatted the system and other partitions with twrp, flashed many roms. Still the result is same. Bootloops.
Click to expand...
Click to collapse
Flash the 21s bootloader + modem, one ZIP file, should work fine. Not sure what ROM did you install last time. You can give it a shot with with MIUI 10 - its nougat.
I had similar issues, see my topic, maybe it helps a bit.
https://forum.xda-developers.com/le-2/help/x526-bricked-unknown-baseband-4g-t3838093
Modem + bootloader 21s.
https://drive.google.com/file/d/0B_R...FxTGxlMHM/view

Brother same thing happened to me, a week ago. I cant say about your problem but my problem was due to faulty power button. Actually due to that reason my phone actually kept restarting itself. It showed red light blinking while charging and wasn't able to bypass the optimizing app screen. I also thought it was a software issue but actually it wasn't. I spent about 2 hours figuring out what the actual problem was. The problem was: As we know when power button is hard pressed for about 10-15 seconds it reboots itself.
Although the repair shop guy didn't put new power button but he added a tiny piece of paper in between the power button and body housing to prevent the issue and voila the problem was solved.

delltech1 said:
Hi,
try to to reimage your phone with QFIL from this site:
https://www.techpoison.in/2017/12/how-to-flash-letv-le-2-x526-stock.html
I downloaded everything from there, QFIL, Sparse image and drivers. My phone was bricked, but its working normally now. After you flash the image your phone should charge normally, just try to boot it up. In my case i had issues with baseband, not detected, no sim function and no wifi and phone was restarting each 3-4 minutes, but it was operable. Basedband issues can be solved by hard reseting the phone and updating it to 21s using the local update, just put the 21s stock renamed to update.zip to internal storage and run system update. When you get the error - APK missing, just boot it up again and retry the local update, should work fine the second time, i just deleted the update.zip and put back again and ran the update.
---------- Post added at 03:24 PM ---------- Previous post was at 03:18 PM ----------
Flash the 21s bootloader + modem, one ZIP file, should work fine. Not sure what ROM did you install last time. You can give it a shot with with MIUI 10 - its nougat.
I had similar issues, see my topic, maybe it helps a bit.
https://forum.xda-developers.com/le-2/help/x526-bricked-unknown-baseband-4g-t3838093
Modem + bootloader 21s.
https://drive.google.com/file/d/0B_R...FxTGxlMHM/view
Click to expand...
Click to collapse
Hi, Thanks. I actually did that first, flashing through qfil the same rom. it helped me to go to settings after umpteen attempts to go past language selection screen, and i was just able to oem unlock and enable usb debugging (actually after a 2nd partial failed flashing). the phone kept freezing within seconds of booting up. Now After i unlocked the bootloader and installing twrp and flashing many roms thru twrp, i am still having the same problem of booting up and freezing at start-up. cant flash again through qfil, as i will again loose the unlocked bootloader and twrp.
At least , now i can try different roms to see which can unbrick it. last one used was the twrp flashable rom based on eui (small eui by aurel) but it also freezes on language selection screen or beyond.
I am running out of ideas, lets see.

2nd partial failed flashing? any issues during the flash process? i had some issues when i used usb 3.0, 2.0 worked fine for me. If you have also charging issues stay in twrp and let the phone charge properly, its slower but should work fine. You can try to flash the 21s bootloader with modem, maybe it will boot properly. But try it only when you are able to enter the fastboot mode, longpress volume down and power for 10-15 seconds, if that is working you should be able to flash twrp via fastboot and you can experiment a bit. Try to find the chinesse twrp 3.0.2.0 and try to flash the stock 21s version. Should be also an image file, in standard twrp go to install - image, after selecting the image file click on recovery and install, after installation go back, reboot, recovery. Copy 21s to storage, wipe data, cache, dalvik and flash it, chinesse twrp will skip version check and will let you install the stock image, after install reboot but click on do not replace recovery button - this will keep the chinesse twrp installed.
If nothing helps it can be only a HW failure, maybe the power button, try usb 2.0 port during the flash process, i had issues with 3.0 on my pc, if that doesnt help.try a different cable, no more suggestions, sorry.

delltech1 said:
2nd partial failed flashing? any issues during the flash process? i had some issues when i used usb 3.0, 2.0 worked fine for me. If you have also charging issues stay in twrp and let the phone charge properly, its slower but should work fine. You can try to flash the 21s bootloader with modem, maybe it will boot properly. But try it only when you are able to enter the fastboot mode, longpress volume down and power for 10-15 seconds, if that is working you should be able to flash twrp via fastboot and you can experiment a bit. Try to find the chinesse twrp 3.0.2.0 and try to flash the stock 21s version. Should be also an image file, in standard twrp go to install - image, after selecting the image file click on recovery and install, after installation go back, reboot, recovery. Copy 21s to storage, wipe data, cache, dalvik and flash it, chinesse twrp will skip version check and will let you install the stock image, after install reboot but click on do not replace recovery button - this will keep the chinesse twrp installed.
Click to expand...
Click to collapse
My phone has been flashed multiple times by qfil method. And always it hangs at initial setup (so it boots up, but hangs at language selection or further up screens, before setup can complete and launcher could be loaded).
While trying to flash again with qfil once it stopped at 25 percent (because the battery went dead). Charged the battery and booted up the phone, and i was surprised it booted up. After 2-3 attempts i was able to reach the launcher screen and immediately enabled developer options and oem unlock / usb debugging. Only had few split seconds to do this and the phone froze again. After that i installed twrp and hence treying different roms. Most fail at setup.
Just tried MIUI 9PRO ROM. It also froze at setup multiple times, but once i was able to complete the setup and miui launcher is up , but it reboots or turn off the phone just after that. So cant do anything with the phone. Unsure of whether a newer bootloader will help in these freezing issues as i have been able to boot up at least in some roms only if for few seconds. Will try to tinker the settings of miui rom (if the phone let me do it before freezing/hanging). Lets see. Thanks for suggestions. More suggestions welcome, because i am still unsure weather this is a software or hardware related problem. I am guessing that it may have something to do with Google security as earlier i was getting msg that phone has been wrongly resetted and needs to verify with Google (but i couldn't get a chance to use the same account, as phone kept freezing at setup).

Did you fully charge the battery, if not let it fully charge in twrp. Flashing the roms in twrp works everytime or do you see any errors? Before you flash anything disconnect the usb cable.
---------- Post added at 09:54 PM ---------- Previous post was at 09:47 PM ----------
Try to flash the 21s bootloarder with modem, one zip using twrp. Go to fastboot mode and wipe modems. fastboot erase modem1st fastboot erase modem2st. Put the phone to flash mode and reimage with qfil. Before you do it write down both imeis, you can find them also on the original package on the backside. Also try to remove all sim cards from the phone and try a different cable. If nothing helps, hw issue, maybe the power button mention earlier in this thread.
After reflash skip everything at setup and reset phone to factory defaults. OEM is already unlocked, you dont have to do it again.

I have charged the phone fully before any flashing after that error. I can flash the phone through twrp without any error msg. The phone boots up most of times in various roms but hangs at or after the initial setup screens show (like language selection etc). Flashed the modem+bootloader, success, but it showed bootloader version as 20s (not 21s). Tried the commands u mentioned to erase modems, it say error failed, no such partition found. I had checked the partitions with parted and 56 partitions are there including the modemst1 & 2.
Now re flashed via qfil , did as advised but again the same problem of hanging / freezing at or after initialization screens of various roms.

Forthe55 said:
I have charged the phone fully before any flashing after that error. I can flash the phone through twrp without any error msg. The phone boots up most of times in various roms but hangs at or after the initial setup screens show (like language selection etc). Flashed the modem+bootloader, success, but it showed bootloader version as 20s (not 21s). Tried the commands u mentioned to erase modems, it say error failed, no such partition found. I had checked the partitions with parted and 56 partitions are there including the modemst1 & 2.
Now re flashed via qfil , did as advised but again the same problem of hanging / freezing at or after initialization screens of various roms.
Click to expand...
Click to collapse
Yeah sorry i screwed the command its fastboot erase modest1 modemst2, my bad.

Just now i was able to complete the initialization (setup screen) of sparse image india rom. I can reach the launcher and settings for few seconds before the device freezes or reboots.
So the same problem , with which i started, the only good thing is that i have been able to set oem unlock to on, so that i can flash trwp and various roms (but all fail with the same freezing issues)

Forthe55 said:
Just now i was able to complete the initialization (setup screen) of sparse image india rom. I can reach the launcher and settings for few seconds before the device freezes or reboots.
So the same problem , with which i started, the only good thing is that i have been able to set oem unlock to on, so that i can flash trwp and various roms (but all fail with the same freezing issues)
Click to expand...
Click to collapse
So you erased modems and reflashed with qfil right? If so i assume its a HW problem. Try the fix with the power button, i ran out of ideas

Last thing which can help maybe: https://www.youtube.com/watch?v=LH3VOIlLfvo&t=135s
Download 21s stock image + the chinesse twrp, links should be under the video, i think so, or look somewhere in the forum for new links. Try to reflash the 21s, some people reported that freezing issues were gone after installing the latest EUI. Basically you can do the same after QFIL reflash but you need enough time to copy the ZIP file as UPDATE.ZIP to the internal storage and run the local update via setting, system update and local update, i hope that TWRP will work for you, just follow the video tutorial.

delltech1 said:
Last thing which can help maybe: https://www.youtube.com/watch?v=LH3VOIlLfvo&t=135s
Download 21s stock image + the chinesse twrp, links should be under the video, i think so, or look somewhere in the forum for new links. Try to reflash the 21s, some people reported that freezing issues were gone after installing the latest EUI. Basically you can do the same after QFIL reflash but you need enough time to copy the ZIP file as UPDATE.ZIP to the internal storage and run the local update via setting, system update and local update, i hope that TWRP will work for you, just follow the video tutorial.
Click to expand...
Click to collapse
Did that also, the same problem. The phone freezes after the os is booted. I was wondering what is that isnt touched by flashing ( in download mode or fastboot mode or through twrp). I may need to tinker that. The roms are all fine in the sense they all stop at the same points. Something in the phones partition, which isnt touched by flashing? (There must be, as i flashed with qfil, the oem unlock remains, the bootloader didn't lock, and it remains unaffected by re-imaging)

Try this, maybe it helps:
https://forum.xda-developers.com/le-2/help/issues-installing-twrp-rom-le-s3-x522-t3618662/page2