I will detail my experience COMPLETELY.
1.I- My phone was having problems turning on (it restarted itself 3-5 times after turning on or showing charge screen).
2.- Yesterday the update went live so I thought "oh, maybe this solves my problem"
3.- First I was having the turning on problems described above, but then the "bootloader unlocked" splash screen was no longer showing up and the "unlocked" message below the android one logo did not show up. Plus, it didn't restart but just stay stucked in the Android One logo.
4.- I flashed 10.0.2.0 with MiFlash but I came back to number 3. I don't know what to do. I decided to post my experience because there is no other post describing the bootloader unlocked splash abscense.
UPDATE: Flashed again with MiFlash and worked. NO DATA WIPE NEEDED! DON'T DELETE DATA!
so nice for you to be able to recover. I had to wipe everything. see my post here https://forum.xda-developers.com/showpost.php?p=78755665&postcount=13
I'm not alone.
Related
Hi guys, I'll try to explain my problem:
My Milestone has been running the rom "cm-7.2.4e-umts_sholes" since two years without issues... until a few days ago: aleatory restarts and freezes. Yesterday, I turned it on and was stuck on "M" logo. Several restarts later, it shows the "2ndBoot - Kernel Restart in progress" logo and nothing else.
I tried to reflash the rom and encountered some issues:
Bootloader 90.73, I flashed the vulnerable recovery "vulnerable_recovery_only_RAMDLD90_78.sbf" and enter in recovery stock. When I tried to run the "OpenRecovery_2ndbootOR_v1_2" the OR doesn't start at all. Black screen, restarts and recovery stock again. Only the "OpenRecovery_v1_46_SHOLS_inkl_ext_mmcfix_parted_update" does the trick and starts the OR with red letters. After all the obligatory wipes, applied update from "cm-7.2.4e-umts_sholes" and then reboot system. And the same "M" stuck or "2ndboot" stuck screen. I tried wipes again, but no results.
So, I tried to go back to an earlier version and installed "SHLA_U2_02.02.0_USASHLSPERARLA017.0R_USASHLSPERARLAT_P037_A015_HWp2a_1FF" with RDSLite. It boots up Android BUT the touchscreen not works at all, even with several reboots. Tried to reflash Cyanogenmod from here, but the same issues above listed appears.
I really going crazy with this... Did I make some mistake at any point? Must I reflash the bootloader 90.73 if I found it? (besides all the webs containing all the .sbf's and bootloaders appears to be offline by now).
Any solution/advice you can give me please?
Thanks in advance and sorry my english, isn't my first language.
Hi,
Some how I turned the FRP lock on and when I restarted my phone on the logo screen it said FRP lock is on and then nothing happened after that.
I googled around and people suggested to update the firmware using Smart Switch. Smart Switch completed its work 100%, but the my phone got stuck on logo screen and nothing happens. After more googling I found this solution: http://forum.xda-developers.com/galaxy-s6/help/sm-g920f-stuck-samsung-logo-5-1-1-update-t3150727
When I try flashing the phone using Odin with the instructions above, it says "Custom Binary(BOOT) Blocked By FRP Lock".
People please help me to resolve my issues:
1. FRP lock is on. How can I disable it?
2. Phone is stuck on logo screen.
Thank you!
Try the smart switch thing again and let it keep loading. can take up to 10 minutes the first time it loading.
tyrone1 said:
Try the smart switch thing again and let it keep loading. can take up to 10 minutes the first time it loading.
Click to expand...
Click to collapse
Before I tried with Odin I had tried multiple times. Still the same issue.
Odin latest firmware and let it boot over 10 min.
Hey! I had the same problem recently but I was be able to recover my phone by, downloading kies 3 (not smart switch) So once that's down open it up and click the "tools tab' and you want to do a "firmware upgrade & installation" now enter your device info, you can get your SN and IMEI numbers by pressing and holding "volume down + home + power" then hit the home button. So use that information and put in kies. Then it will prompt you to boot to recovery but instead boot to download mode and start the process in kies so then just be patient, really patient and might take up to an hour. and good luck! Hope it helps!
I'm in the same situation. I've installed stock firmware with both odin/kies everything was successful, but on boot, it's just stuck on logo. FRP lock is on, but I know the user and pass.. it's a friends phone. How can I enter the account if the device doesn't even boot up... !? I've tried everything I could find on the internet.. nothing worked.. any new ideas? anyone..? thanks.
If a full restore was successful via kies then it should boot up as if it were brand new outta the box.
As I said in the title. The phone's memory seems to be read only.
I can access the fastboot mode of the phone and issue commands like flashing the recovery but it doesn't seem to update anything on the phone even though I get the "OKAY" message.
My phone is unlocked and until last night I was running CyanogenMod on it just fine. But now I can't flash a new recovery or access it. I have TWRP installed but everytime I try to boot into recovery the phone gets stuck on the logo screen and flashes every couple of seconds.
If I try to start my phone normally I get the cyanogenmod logo on start up (even after flashing stock) and the phone never actually boots up.
Anyone had the same problem before? If you need more details I'll reply ASAP.
My phone is the retail European XT1068 Dual Sim. Thank you in advance for any help.
Same issue here (I'm MrPowerGamerBR on Reddit), the more I read about trying to fix this issue, the more I start thinking "this phone is dead, move on..."
There isn't no fix for this, the only way to fix is replacing the logic board.
Here's the deal, I have a sprout8 device (the Indonesian Nexian Journey One) running stock 6.0 with some xposed mods installed on it. Suddenly the device shuts down and when I try to boot it up it only goes halfway through the bootanimation when it shuts down again. I wasn't too worried as I thought it was just a conflicting system issue and I also thought it was time to re-flash fresh stock 6.0 to freshen up my phone anyway. So I went ahead and did it.
Here's where the problems start to show up, I had a hard time booting to recovery through the power + volume up combination. The phone suddenly shuts down on its own as it boots up. I tried it a few times and finally got to recovery. After that, as I flashed stock 6.0 the phone shut down again. I thought it was an issue with my recovery so I tried wiping everything through fastboot and re-flashed recovery through fastboot aswell. From there I tried again to flash stock 6.0 through recovery and again, the phone shut down. I tried a different ROM thinking it was a ROM issue but still got the same results.
After hours of trying to flash a ROM through recovery (retrying over and over as it suddenly shut down while flashing), I finally got a ROM installed. Then I rebooted my phone, but again it freezes halfway through the bootanimation (literally freezing the bootanimation) and refused to do anything. I took off the battery and booted up the phone countless tries trying to get it to boot up. When it finally booted up, I filled in all the Google startup credentials and finally got started on a fresh stock 6.0. However, I tried to restore my previous application data through Android's application recovery on startup but everytime the device installs a new application it would freeze up and shut down. This happened countless times. Then the phone, once again, shut down and could not start the ROM. It would freeze up on the bootanimation.
Then things started to get weird, when the phone turns on it should show the "Nexian" logo in all its glory before going to bootanimation. But here the screen gets all distorted and shows these weird horizontal (and sometimes vertical) lines. Nothing's wrong with my phone screen so I assume it is a system error. From here on, the phone refused to boot. It just shows the Nexian logo and restarts over and over. The same thing happens even after I re-flashed both my recovery and ROM. I even tried using SP Flash Tool to re-flash stock but still the same results.
Now, the device wouldn't even turn on. But when I connect it using USB to a Windows computer, it still gets detected through device manager as an ordinary MediaTek device.
I'm assuming now that it may be a problem with the /system parition where we install our ROMs in. The partition may be (partially) corrupt. Seeing as the device could still boot the ROM a few hours ago but freezing upon updates to the stated partition.
If you guys have any other ideas/solutions I'm all ears.
hi.
i have de-branded my phone, got the L09C432B378 version.
now i see i have an update and the phone downloaded it but every time i tell it to reboot and update the phone is stuck on the screen saying my device is unlocked and cannot be trusted and it's rebooting now.
i waited for 30 minutes, nothing happens, so i used fastboot to reboot it and it works but not updated.
any suggestions?