Hi everyone. So after trying to flash the patched magisk boot.img via SP Flash tool, the tablet wouldn’t boot, so I flashed the firmware that is on another post and it boots fine now, however the message “Bluetooth Keeps Stopping” constantly pops up and the Wi-Fi doesn’t work. Only way I can get it to work is restarting the tablet a bunch of times and going into Reset and resetting the Wi-Fi,Bluetooth, and mobile and it eventually will work until I turn the tablet off or it dies. Also it is now Android 10 GO and it came with Android 11 GO. Any advice?
When that happened to me it wad the vendor partition. In your case if that is issue, you would need to flash that partition. Only thing else you could try was going into recovery and wiping.
Related
My 2012 N7 is stuck in a boot loop. It is stock 4.4.4 and not rooted or bootloader unlocked.
Sometimes it will hang during the boot animation and start over, if it makes it through a complete boot I get about 10 seconds before it reboots again, sometimes a random app will crash before that (usually TV) but not always. That means I can't make any system changes (turn off MTP, usb debugging), or if I can do it quickly the changes don't persist or there isn't time for my PC to update the drivers.
I have tried restoring through the recovery mode multiple times, that didn't take.
I've tried using WugFresh's NRT v1.9.3 to use its "Flash Stock and Unroot" feature and after downloading Google drivers so it can talk to it during fastboot mode I was able to get it to attempt to flash both the 4.4.4 factory image and 5.0 factory image. None of those worked either, I think maybe because I can't get the USB debugging working. The process goes very quickly and spits back various FAILED (remote: Bootloader is locked.) and nothing happens, just sticks at the bootloader screen. Even tried to unlock the bootloader via the NRT in case that would work, got as far as the option to unlock the bootloader and erase everything, that didn't take either.
Every thing I've tried so far just keeps giving me constant reboots with all my apps and data still there. The Android laying there with his chest open is mocking me now and I'm stuck on what to do next. I need help or a point in the right direction, please I am running at my wits end with the blasted thing.
Hello guys, i'm having a problem ;f
I was on cm12 nightly when i decided to reboot my device after few days of running, strange thing happend and i ended up in bootloop.
I've downloaded 4.4.2/4.4.4/5.0.1 stock images and tried to flash it guided by the instructions in this thread, however i still get a bootloop, even after clean installation, even after wiping cache and doing a factory reset.. I've managed to boot up my device twice since yesterday, after getting stock image to work i pushed cm12 and gapps on my phone and flashed them.
At the first try, i got bootloop again, so i decided to go through the whole process again, many attempts later i've managed to boot up my device again, and again i decided to flash cm12 and gapps, this time my device booted up properly so i wanted to gain root access, in order to do so I flashed UPDATE-SuperSU.zip file and as a result end up in bootloop again.. I have no idea wtf is wrong with my nexus. I am still trying to flash factory image, and i always end up with bootloop.. I'm out of ideas here, HALP! ;(
@update:
I have uninstalled all drivers, and mount my device to another usb port, then with NRT i installed google's drivers, by using nrt i have flashed 5.0.1 factory image, rebooted into recovery and wiped/factory reset, after that i rebooted my device and still no luck - hanging on floating dots for 15 minutes..
Before all of this I tried formatting my cache to FAT and to sdf4 and it didn't help, I literally tried every single instruction i could've found ;/
What's wired is that when i encountered bootloop yesterday and wiped/factory reset i booted fine, after restart it went into bootloop again, so i thought i would wipe/factory reset again i'll be good to go, but.. it didn't help this time oO
things i've already performed:
1. fastboot oem lock/unlock
2. wipe data/cache/factory reset
3. flash factory images of 4.4.2/4.4.4/5.0.2 through NRT/manually
4. converting partition to fat and next to sdf4
5. reinstalling drivers
6. different ports and usb cords
6. i even tried switching motherboard from my old n4 and i still stuck at bootloop *LOL!?*
7. after 6 i thought it may be related to usb port so i switched usb port from my old n4 and it did help but.. until next reboot ;/
from time to time, after flashing it boots up just to make my hopes and then it gets the bootloop after restart ;/
@update2:
It seems it's hardware related issue. I have tearn down my nexus device and left only motherboard with fron/back cameras and audio jack, daughterboard, i even disattached the speaker along with antena. At this point i flashed factory 5.0.1 and it works, i'm in the moment when i plug peace after peace and turn on the device to check if it still works. I'll update when i find out what was the cause of the problem.
@update3
Stupid as it sounds the issue was caused by the vibrator module, while it was disattached, the device was booting up without any problem.
Can anyone PLEASE help??
My partner opted to do a suggested update on her S5, but didn't notice the wifi was off. The phone seemed to have done the update, but shortly after it rebooted itself, then again, then again. The frequency of reboot got quicker and quicker and now it loops between the Galaxy S5 splash screen and the SAMSUNG logo, but doesn't go any further.
I managed to boot the phone into reset mode, cleared the cache and then did a factory reset, but that did nothing to prevent the boot loop.
I then downloaded Odin (ver 10.3.7) and what I believed to be the correct firmware (G900FXXS1CPLV_G900FVFR1CPJ1_G900FXXU1CPIW_HOME.tar.md5).
Having checked the battery was charged, I followed the instructions of connecting the phone via USB, loading the md5 in the AP, checking Auto Reboot and F-Set time in the options and clicking the Odin Start button. I had removed the battery, replaced it and then booted it into the update mode (Power, Home, Volume Down, then volume up) with the screen confirming I was in the right place (....do not unplug.... etc).
The file loaded, (green bar at top of the Odin window on my PC) and Odin reported success. I then disconnected the phone, booted in recovery mode, reset the cache and then did a clear data, factory reset.
The same symptoms prevail, STUCK IN BOOT LOOP!!!!
The only thing different is that if I plug it into the USB on my PC, after a while the phone tries to turn itself on and goes into either a boot loop or freezes on the Galaxy S5 Splash screen or the SAMSUNG Logo.
I am charging another battery (just in case that is in some way to blame) and will try again to replace the firmware, but could I be missing something, do I need to do anything with PIT (I thought this was all taken care of by Odin using the MD5 file) or is there some other test I can perform that will show if the phone is fried???
MANY THANKS for looking!
ur going correct, try to reflash it again through odin and dont disconnect phone until it boots into system, it is taking some good time, so just wait and dont do anything this time like clearing anything or restoring. i hope ull get success.
THANKS - but...
Thanks Rayzen, I will try the whole thing again, but I think there is something more to this than a firmware fault!
There and gone again
OK, so on the 4th attempt I got the phone to take the firmware using Odin, it reported success and the phone rebooted itself (several times) and eventually appeared to boot to a new factory reset.
I put in a SIM card and entered my email and google account details and left it charging over night. This morning when I tried to use it, the screen froze and then it rebooted itself. Hey presto, the phone is back to square one with a boot loop.
ANYONE (please) got any suggestions?
THANKS
No one??
same here, same symptoms, same feeling.
when flash gone right... i feel lucky.. but for half hour only, rebooted and angain in boot loop.
I cannot even boot in recovery. flashed TWRP. from 5 boots in recovery only 1 success.
When trying to wipe phone in TWRP - it hangs.
still trying to install some other (custom) rom. still no success.
hope never dies
same things happened here! now cant get samsung galaxy s5 to boot...............
Are you sure your using right firmware? as it took me a few versions before it booted last time this happened?
Could any please confirm what is the right firmware for samsung galaxy s5 900F
It took another 6 or 7 attempts, left it over night and was about to trash it when it booted.
I then received a 'software update available' message and tried installing it. First attempt put the phone back into boot loop so I reflashed it again using Odin.
That worked immediately the over the network software update installed and now phone is 100%
Very frustrating but I got there!
glad you fixed it! ive tried three different firmwares and still nothing.
trying this one atm
G900FXXU1ANE2_G900FEVR1AND1_G900FXXU1ANE2_HOME.tar
oh and how long do they take to boot when there are sitting at the samsung glowing screen?>
I'm in UK and used what (I had to guess) was the best firmware.
I'll let you know which version it was when I get home tonight.
BUT I had all the problems with a single version and it eventually came good.
I read somewhere that overwriting a different core (from specific providers) with generic firmware, could lead to a world of pain until it gets full replaced... not sure if that's a good description (or has any fact to it) but it seemed to be re-loading and re-loading and re........ for ages, finally cracked it.
well mines booted now!but getting constant errors about samsung push!
If it'still booted, you'very made progress!
Push issues are mentioned elsewhere and can (eventually be sorted) but if you have a booted phone you should be able to get an over the air software update installed from the service provider....?!
ok guys i know there are loads of threads about thois but ive got a slightly differen situation.
my daughter had this phone and then it suddenly tured off and wouldn't turn back on, i managed to get it to boot by disconnecting the battery and plugging it while holding the power down and reconnecting the battery which put me into fastboot then the boot to edl script made the phone boot. i have since unlocked the bootloader and flashed twrp and the reflashed the stock firmware which worked for a few hours but i tried to reboot it and now it wont boot, i can get to twrp but even if i flash the stock firmware it refuses to boot any idea on what i should do to try to get this phone to boot up?
Try to flash a custom rom, as far as i know this problem is caused by a MIUI update.
Joaoovn said:
Try to flash a custom rom, as far as i know this problem is caused by a MIUI update.
Click to expand...
Click to collapse
i have tried to flash a couple but every time i try it fails with error 7 and tried the normal fix but it doesnt help. then anything i do in twrp makes the system unmount and then it cant mount again. the only eay to get to get it to boot again is to take the back off and disconnect the battery and hold the power button down when i reconnect it but ive got no idea why it does this.
Hi guys,
Trying to fix a friends x704f wifi only, but no luck.
It had Lineage 18.1 on it, and for whatever reason he did not like that, and went on to reflash stock with Lenovo's Rescue and Smart assistant which showed it a success rescue, but now Tablet boots to EULA, arrives to choose wifi and it crashes and reboots constantly, with no wifi icon being shown.
Lenovo rescue installed TB_X704_S000060_220916_ROW, so I factory reset it a few times from recovery, went through rescue again, installs same ROM, success, yet again it crashes at network selection, of if you do not touch anything, it crashes itself after about 20 seconds after being booted and if i hold the Power button and select shutdown, briefly the standard desktop shows with icons and than it crashes, so guessing ROM is there, it just can't boot.
Tried with QPST and latest ROM, but on eMMC xml selection I get error Document error on element program and name/value true.
Guessing baseband or some other thing should of been backed up before flashing stock again? if it helps, OEM lock is OFF, secure boot is ON what I can see from fastboot.
Thanks.
There must be something wrong with the persist partition, flash the persist.img again.