Alright. This is a 100% stock Nexus S- nothing "development" wise was done to the device, no system tools installed that could cause issues, basically nothing but basic apps loaded on the device.
It just started today. I was working on my bf's Vibrant (another, more successful story) and grabbed my Nexus and hit the power button and it did not turn the screen back on. Holding the power button down did not reboot the device, and none of the buttons would light up or function.
So, I pulled the battery. Now every time I try to boot, it hits the "Google" screen and stays put. I left it alone for 5 minuets hoping it would finish booting and nothing. The soft buttons will light up, and if I touch them they register the touch but it does not help the phone to boot.
I do know that the phone was basically dead right before this happened, and at first I thought it was just dead. However, its been on the charger for at least 30 minuets- which should have given it enough of a charge to boot up, and still nothing.
What could cause this issue?
I did install a couple of new applications today, and I know the market updated a bunch of them but they're all apps that I've had on several phones (minus the two new ones today) and have never had an issue with any of them. The two new ones I downloaded were OS Monitor, and a 2G/3G toggle for hopes of improving some battery life.
But those are the only two things I've done differently. I've only been using the phone for a week but I haven't had any problems at all, before this.
Now- if worst comes to worst I can seem to get into the bootloader, and through that, stock recovery. So I can try to do a factory reset and wipe cache but without a backup I really kinda hope thats a last resort.
Please help, and let me know if you need any more information.
Thank you!
I understand that you're fully stock which I assume means you have a locked bootloader (everything I say from here on out assumes as such)? First, I'm going to also assume that you didn't update to 2.3.3? If not, then follow the steps in this guide to boot into a custom recovery and from there go to backup and restore and do a NANDroid backup. Now go to mounts and storage and mount USB storage (or whatever its called, don't have my phone right here). Plug your phone into your comp and copy over whatever you'd rather not lose from your SDcard (just in case you have to wipe). Now download the 2.3.3 update from here and put it on the root of your SD card. Now go back and flash this. Reboot and see if you're golden. If so, great, if not try a factory reset.
If that doesn't work go through the steps again to boot into a custom recovery, you might have to unlock your bootloader and wipe all your data (again) and restore your backup and try doing a factory reset with that. Don't worry about unlocking the bootloader, it can be relocked with a simple command and it won't wipe anything to relock it.
Here is the command just in case:
Code:
fasboot oem lock
I got all the way to having clockwork recovery booted up on the phone, but nothing would mount. Everything gave me an error, and factory reset froze...
I don't think there is anything I can even do from here, is there?
Hey guys,
I have encountered a serious problem on my device. Today I rebooted my phone once and it has just stuck on the samsung logo. Then the phone began to reboot without ending....It could not just start. With the help of TWRP I have made a full wipe and tried to reinstall my actual firmware Superman 1.10.5, but I always stuck at 25%, the phone did not respond to any actions. I even tried to flash the stock 4-file firmware with Odin, but it did not help, the phone constantly reboots. Sometimes it manages to boot to the stage where the sign "installation of applications" appears, but a while later it stucks again and reboots. Please, help me to solve the issue, because I am begininng to think that it would be unpossible to recover the phone. I am only able to enter the download mode or recovery, anything else does not work.
Thanks....
AuroraLX said:
Hey guys,
I have encountered a serious problem on my device. Today I rebooted my phone once and it has just stuck on the samsung logo. Then the phone began to reboot without ending....It could not just start. With the help of TWRP I have made a full wipe and tried to reinstall my actual firmware Superman 1.10.5, but I always stuck at 25%, the phone did not respond to any actions. I even tried to flash the stock 4-file firmware with Odin, but it did not help, the phone constantly reboots. Sometimes it manages to boot to the stage where the sign "installation of applications" appears, but a while later it stucks again and reboots. Please, help me to solve the issue, because I am begininng to think that it would be unpossible to recover the phone. I am only able to enter the download mode or recovery, anything else does not work.
Thanks....
Click to expand...
Click to collapse
Really sad to hear that story mate. First things first, I assume your BL version is matching with the firmware your flashing right. And when you go to TWRP, can you see /system and /data partition from the mount menu? If not, you have to perform a factory reset. I had issue like that with my Galaxy S7 and usually factory reset(not wiping) helped me with that situation. Since your system can boot up, but crashes after awhile, I do suspect that some of your partition might be corrupted(at least its what happened to me). So trying factory reset can be a good bet for you.
And... I think you have to provide more information with which variant you are using, and your BL version, TWRP version too, solve the problem quicker. Hope this information helps.
CenteaOSD said:
Really sad to hear that story mate. First things first, I assume your BL version is matching with the firmware your flashing right. And when you go to TWRP, can you see /system and /data partition from the mount menu? If not, you have to perform a factory reset. I had issue like that with my Galaxy S7 and usually factory reset(not wiping) helped me with that situation. Since your system can boot up, but crashes after awhile, I do suspect that some of your partition might be corrupted(at least its what happened to me). So trying factory reset can be a good bet for you.
And... I think you have to provide more information with which variant you are using, and your BL version, TWRP version too, solve the problem quicker. Hope this information helps.
Click to expand...
Click to collapse
Yep, you are right, BL versions always matched firmwares. I tried to wipe the phone with TWRP 3.0.2.3 and also to make a factory reset with the stock recovery. The stock firmware, which I tried to flash, was G930FXXU1BPH6_G930FOXE1BPH1_SER consisting of 4 files including BL,AP,CP and CSC. After 3rd or 4th flash of the same stock firmware the phone suddenly became alive and began to boot. Wu-huuu:silly: I was happy as a child. After having successfully launched the stock rom I have again flashed TWRP 3.0.2.3, went to "wipe" option and formatted data. Then I have installed a Superman Rom 1.12 and everything went the right way. I don't understand only one thing: why after having wiped the phone several times and having reseted it through the stock as well as TWRP recovery it didn't want to boot.
As you said, I suppose that the one of partitions was corrupted. Oh damn, I thought that I won't be able to resuscitate this phone.
I have flashed about 20 phones during my life, but I have never ever encountered such serious problems.
Hey,
I need some help with this problem. I have a frd lo4 on nougat. I tried to return to stock from being rooted. The dLoad folder method wasn’t working (returned invalid package) so I unrooted via the SU app, flashed stock recovery, and went into fastboot and relocked the bootloader with the code.
Now it won’t boot or shut off. Just a bootloop showing the blue screen. I could use to access fastboot before but now my pc doesn’t detect my phone. I’ve tried different ports and pc’s. I can’t access recovery either.
Any help is appreciated
EDIT: I let the battery die, then tried going into fastboot mode and it worked. I flashed the stock recovery 1 and 2. I then used the correct rollback package and put it on my sd card then flashed. I then downloaded the full 6.0 firmware and did the same. Now I’m unrooted, locked bootloader, and stock.
Hope this helps someone.
Excatly the same thing happened to me 1 week ago.. My phone was going on bott loop in recovery mode.. I tried Dload method and recovery but nothing happened.. atlast i let the battery die. After the battery is completly dead i connexted the charger and hola the adb is working now. Then i flashed correct recovery and rom. Ecerything is working fine now.
Hi everyone!
First, sorry reviving the threadm but this one is similar to my trouble.
Second, every flash process was done with dload method and vol + - and power combination.
Third, I never unlock my phone before or flashed any custom rom or recovery, everything was stock.
Last night, I tried to rollback my honor 8 frd-al19 to emui 6.0 with proper rollback package and firmware for Android 6.0 (both official and for my model), but phone went into boot lock. It isn't boot loop, It's stuck on the Honor blue logo. I can't even turn off the phone.
I did this procedure once before with success. I was on fdr-al19c432b360 firmware 100% functional (I was an idiot to rollback again when not needed at all... I know). I applied the rollback package correctly, and then I did a mistake and flashed full c636b131 Android 6.0 firmware instead of c432b131 Android 6.0.
Phone started ok with everything working. But I noticed my bad (emui didn't find any update package from OTA, and noticed the error in version model shown) and reflashed rollback package... At this point is where I think I messed up the recoveries or something. When ended the flashing process, I copied the correct firmware (the c432b131 android 6) on dload folder and tried again to flash.... but this time phone never entered on erecovery nor recovery. Only thing I get is stuck honor blue screen. It refuses to enter on recovery or erecovery. It just reboots, vibrate twice and keeps stuck after that on honor screen.
Strange thing, is that I did this procedure once before some months ago with success, but that time I didn't make the mistake with the versions.
After panic, I tried to boot in fastboot connected to my pc, and HiSuite knows there is something connected, because it launches it self, but don't recognize the phone and says it can't be recovered. Also, Adb don't see the phone either, only fastboot.
With fastboot commands I tried to reboot into recovery and nothing happened. Then wipe cache/user data, reflash stock recovery. Everything failed with message "remote: not allowed". And of course, because I never unlocked my bootloader. Fastboot says phone locked, frp locked (was frp, don't remember now exactly).
Then, I read about to let the battery die. I did. That didn't work either, phone keeps stuck on honor blue logo.
I downloaded multitool for huawei software, and everything requires an unlocked bootloader to recover.
Then, I tried to get unlock code, but huawei site ask me product id which I can't get because phone is bricked (I have all other data, imei, serial, etc.) . Tried with id generator too, and nothing what I tried have work so far. It's frustrating.
I'm pretty hopeless now, no unlock, no recovery, no erecovery, so I can't flash anything on the damn phone to try to recover it.
Can I save my phone or is it just an expensive brick? Any help will be REALLY welcome.
:crying:
Noivern said:
Hi everyone!
First, sorry reviving the threadm but this one is similar to my trouble.
Second, every flash process was done with dload method and vol + - and power combination.
Third, I never unlock my phone before or flashed any custom rom or recovery, everything was stock.
Last night, I tried to rollback my honor 8 frd-al19 to emui 6.0 with proper rollback package and firmware for Android 6.0 (both official and for my model), but phone went into boot lock. It isn't boot loop, It's stuck on the Honor blue logo. I can't even turn off the phone.
I did this procedure once before with success. I was on fdr-al19c432b360 firmware 100% functional (I was an idiot to rollback again when not needed at all... I know). I applied the rollback package correctly, and then I did a mistake and flashed full c636b131 Android 6.0 firmware instead of c432b131 Android 6.0.
Phone started ok with everything working. But I noticed my bad (emui didn't find any update package from OTA, and noticed the error in version model shown) and reflashed rollback package... At this point is where I think I messed up the recoveries or something. When ended the flashing process, I copied the correct firmware (the c432b131 android 6) on dload folder and tried again to flash.... but this time phone never entered on erecovery nor recovery. Only thing I get is stuck honor blue screen. It refuses to enter on recovery or erecovery. It just reboots, vibrate twice and keeps stuck after that on honor screen.
Strange thing, is that I did this procedure once before some months ago with success, but that time I didn't make the mistake with the versions.
After panic, I tried to boot in fastboot connected to my pc, and HiSuite knows there is something connected, because it launches it self, but don't recognize the phone and says it can't be recovered. Also, Adb don't see the phone either, only fastboot.
With fastboot commands I tried to reboot into recovery and nothing happened. Then wipe cache/user data, reflash stock recovery. Everything failed with message "remote: not allowed". And of course, because I never unlocked my bootloader. Fastboot says phone locked, frp locked (was frp, don't remember now exactly).
Then, I read about to let the battery die. I did. That didn't work either, phone keeps stuck on honor blue logo.
I downloaded multitool for huawei software, and everything requires an unlocked bootloader to recover.
Then, I tried to get unlock code, but huawei site ask me product id which I can't get because phone is bricked (I have all other data, imei, serial, etc.) . Tried with id generator too, and nothing what I tried have work so far. It's frustrating.
I'm pretty hopeless now, no unlock, no recovery, no erecovery, so I can't flash anything on the damn phone to try to recover it.
Can I save my phone or is it just an expensive brick? Any help will be REALLY welcome.
:crying:
Click to expand...
Click to collapse
Well, is a bit silly to answer yourself but this can help someone else:
I did purchase a license of 3 days of dc phoenix software and force updated version android 6.0 c432B131 on my honor 8 fdr L19.
It flashed ok, but software said that couldn't install update. On phone went to 99% for long time (more than 1 hour).
So I looking for some info, and also the software said that I had to manually update. I just copied the same rom with dload method: just the same UPDATE.APP on the folder, and tried the 3 buttons: It worked!
After a success bootup, it found inmediatelly (OTA) the update to android 7, c432b360 firmware and downloaded and installed.
Here went something strange: after updated again via OTA, everything was working ok, but on about phone, the version shown wasn't the c432b360. Instead it said something about test keys build. Just for being safe, I tried to full reset the phone and... it failed. It said failed on erecovery menu, and after that, the next boot up I couldn't pass over wifi setting menu: keyboard was missing and it just tried to talk to text input. Another panic moment, so I tried to enter on recovery to clear cache and reset user with no luck. After that, phone refused to start showing an error message on fastboot screen: "phone couldn't pass verification, it may not function properly".
What to do? just do all the things again, but just with dload method. As I was on android 7, first I installed downgrade package. Ok, it did well. After, installed again c432b131 (android 6). And finally success!.
Once again, phone ask for install OTA android 7 and I let it. Now, I just didn't tried to do a factory reset and so far is ok.... but it hasn't AOSP Android keyboard anymore. So far is working ok, everything is working: wifi, phone, 4g mobile internet, nfc, sensors, apps, gps, compass... so I'm pretty happy now, but not sure what happened when I tried to factory reset and what happened to AOSP Android keyboard.
Noivern said:
Hi everyone!
First, sorry reviving the threadm but this one is similar to my trouble.
Second, every flash process was done with dload method and vol + - and power combination.
Third, I never unlock my phone before or flashed any custom rom or recovery, everything was stock.
Last night, I tried to rollback my honor 8 frd-al19 to emui 6.0 with proper rollback package and firmware for Android 6.0 (both official and for my model), but phone went into boot lock. It isn't boot loop, It's stuck on the Honor blue logo. I can't even turn off the phone.
I did this procedure once before with success. I was on fdr-al19c432b360 firmware 100% functional (I was an idiot to rollback again when not needed at all... I know). I applied the rollback package correctly, and then I did a mistake and flashed full c636b131 Android 6.0 firmware instead of c432b131 Android 6.0.
Phone started ok with everything working. But I noticed my bad (emui didn't find any update package from OTA, and noticed the error in version model shown) and reflashed rollback package... At this point is where I think I messed up the recoveries or something. When ended the flashing process, I copied the correct firmware (the c432b131 android 6) on dload folder and tried again to flash.... but this time phone never entered on erecovery nor recovery. Only thing I get is stuck honor blue screen. It refuses to enter on recovery or erecovery. It just reboots, vibrate twice and keeps stuck after that on honor screen.
Strange thing, is that I did this procedure once before some months ago with success, but that time I didn't make the mistake with the versions.
After panic, I tried to boot in fastboot connected to my pc, and HiSuite knows there is something connected, because it launches it self, but don't recognize the phone and says it can't be recovered. Also, Adb don't see the phone either, only fastboot.
With fastboot commands I tried to reboot into recovery and nothing happened. Then wipe cache/user data, reflash stock recovery. Everything failed with message "remote: not allowed". And of course, because I never unlocked my bootloader. Fastboot says phone locked, frp locked (was frp, don't remember now exactly).
Then, I read about to let the battery die. I did. That didn't work either, phone keeps stuck on honor blue logo.
I downloaded multitool for huawei software, and everything requires an unlocked bootloader to recover.
Then, I tried to get unlock code, but huawei site ask me product id which I can't get because phone is bricked (I have all other data, imei, serial, etc.) . Tried with id generator too, and nothing what I tried have work so far. It's frustrating.
I'm pretty hopeless now, no unlock, no recovery, no erecovery, so I can't flash anything on the damn phone to try to recover it.
Can I save my phone or is it just an expensive brick? Any help will be REALLY welcome.
:crying:
Click to expand...
Click to collapse
did u solve this bro. Same here happened, no recover no erecovery but just fastboot mode working. I let the battery died but cant charge it now, charging light is just blinking.. I have unlocked bootloader..
Hi, I was trying to update the phone by OTA with an official firmaware, but something went wrong and now it goes in bootloop with the MI logo that keeps appearing on the screen.
I want to flash a clean firmaware to solve this thing, but without unlocking the bootloader it seems impossible.
So now i'm trying to unlock the bootloader, but using the Mi Unlock Tool I need to give some permission that I can't, because I can't turn the phone on!
It asks me to add my account on the phone (that was wiped during those steps)
How to solve this?!
Just to complete this thread. Now the phone turned on, only God knows how.
I did nothing, nor charging, it just turned on when I press the power button. That's a miracle.
But, the question is still there... If this happens again, how can I solve it?
That's a common problem with the MIUI 11 update, the phone takes too much time to charge system files while updating, and that results in a bootloop that isn't really a bootloop, bootloader tries to recover the phone and solves the problem automatically but requires to reboot some times, after that the phone seems to work normally but is recommended to do unlock process with mi unlock after successful update, and after that do a clean flash with fastboot method using mi flash tool
I found the phone in my bag with a discharged battery and does not want to boot all the way. It shows the animated MIUI logo for about 1 minute and then restarts, sometimes showing the menu to switch to 'wipe data' and 'assistant'.
It's all stock, locked, up-to-date, I think still on Android 10 or which one it is. I did not install any new apps and don't even use the phone for anything other than gaming.
I've tried connecting with PC Suite but it doesn't see the phone. Fastboot anything does not work since the bootloader is locked. I know I can wipe data and be done with it, just wondering if there is anything else I can do.
EDIT: I've wiped the data and reinstalled the phone but would like to know if there is a way to avoid this in the future.
Unlock bootloader. This is very important. Then you have full control over the device.
For example the other day I had hard brick because fastboot flash was interrupted. And I still managed to unbrick the device thanks to unlocked bootloader and custom recovery.
It's really hard to hard brick this device. I love Xiaomi <3