Hi everyone. I have a very weird problem and I'm losing my mind trying to figure it out. I was running lineage os 16.my camera got blurry so I got my back cover removed to check what happened and then replace the camera after removing the board,and when I assembled my phone it turns on but directly could not see even the Rom loading screen, only bootloader in a constant bootloop. I flashed the Rom again with same result. then I decided to flash stock Rom again and after flashing a couple of firmware without sucess I managed to install a versión of oreo that shows the huawei logo and it's stuck there for 10 minutes and then boot to recovery. sometimes I get the message that the data partition is severely corrupted so i perform a factory reset and then the phone shows the huawei logo for 1 second and restart again into recovery and then again and again. I flashed again lineage with same result, 10 minute loading screen and then boot into recovery. I also installed twrp to format all the partition in case some of them are corrupted for some reason but the result is the same. at this point I'm hopeless and amazed because I didn't touch anything to harm the phone while replacing the camera. any help would be really appreciated
Related
Hi guys,
My tablet suddenly went crazy since i installed Cm 10.1 , used to crash everywhile till yesterday where it crashed if failed to boot the room where only it gets stuck at the M motorola Logo screen, i decided im going to reflash the rom with its compatible Gapps thats when i faced another problem where my Rogue xm Recovery cant mount either cache or sdcard or internal memory, i kept restarting recovery but with no hope , till i found out i have to open recovery and wait like 3-5 mins till recovery can read device memory-internal memory, cache etc- - LIKE DEVICE WENT TOO SLOW- , i reflashed the rom but again doesnt boot, tried another EOS rom with its Gapps but also same result stuck at motorola boot screen - I FLASH LIKE A PRO wiping everything before flashing- i tried to flash another recovery TWRP but it couldnt read internal sdcard although its modded for that. Please give me some clues this tablet carries sweet memories of 2+ years :/
khafaga said:
Hi guys,
My tablet suddenly went crazy since i installed Cm 10.1 , used to crash everywhile till yesterday where it crashed if failed to boot the room where only it gets stuck at the M motorola Logo screen, i decided im going to reflash the rom with its compatible Gapps thats when i faced another problem where my Rogue xm Recovery cant mount either cache or sdcard or internal memory, i kept restarting recovery but with no hope , till i found out i have to open recovery and wait like 3-5 mins till recovery can read device memory-internal memory, cache etc- - LIKE DEVICE WENT TOO SLOW- , i reflashed the rom but again doesnt boot, tried another EOS rom with its Gapps but also same result stuck at motorola boot screen - I FLASH LIKE A PRO wiping everything before flashing- i tried to flash another recovery TWRP but it couldnt read internal sdcard although its modded for that. Please give me some clues this tablet carries sweet memories of 2+ years :/
Click to expand...
Click to collapse
hi please let me know if you got xoom fixed ?
I have similar issue after installing CM10.1 , tablet stucked on boot logo and because none of my volume buttons work I have no idea how to fix is ! ?
have this tablet for 3 years , it's a lot of stuff there
I was having terrible GPS reception and I tried the antenna fix- sliding a tiny peace of thick paper under the antenna connectors:
https://www.youtube.com/watch?v=K1-uCIb-t8I
After powering up the phone booted once, then rebooted after couple of seconds and has been bootlooping on Google logo since.
- Takes much more time than normally to power on, then falls into Google logo bootloop,
- Cannot go into bootloader, power + vol buttond doesn't do a thing,
- If I hold vol up + vol down while bootlooping it powers off,
- Plugging in doesn't change anything, no charging indicator when powered off.
Is there anything I can do ?
Did I kill my phone ? If so, how ? What could I have damaged by simply prying the cover open ?
Are all the connections secure?
I checked all the connectors, they're ok.
After a day or so the phone got back to the living- I was able to boot and play around for a while.
Then I tried to update (I got the Lolipop OTA), which failed...
Downloaded the factory image and the flash attempt always gets stuck at " sending 'system'"...
Bootloader, radio, recovery, boot, everything gets flashed, then it gets stuck at flashing "system".
Any ideas ?
EDIT:
Flashed 4.4.4 in NRT without any problems, boots normally, still cannot flash Lolipop ...
Heniuro said:
After a day or so the phone got back to the living- I was able to boot and play around for a while.
Then I tried to update (I got the Lolipop OTA), which failed...
Downloaded the factory image and the flash attempt always gets stuck at " sending 'system'"...
Bootloader, radio, recovery, boot, everything gets flashed, then it gets stuck at flashing "system".
Any ideas ?
EDIT:
Flashed 4.4.4 in NRT without any problems, boots normally, still cannot flash Lolipop ...
Click to expand...
Click to collapse
Might need to wait for 5.1
5.0 is buggy
Hi guys, so recently I bought a Galaxy S6 Verizon off of eBay. I got it for fairly cheap because it was stuck in a boot loop. I usually have no problem fixing stuff like this, but this time is different. So the first thing I tried when I got the phone was to do a reset and cache wipe from recovery. I rebooted the phone and it showed a screen that said "Android is starting, optimizing app 9 out of 31." when it got to 21 the phone rebooted and went back to 9. It did this several times before I attempted to wipe/reset again. I then downloaded the tar file G920VVRU4CPH1 and flashed it in Odin. I did a manual reset before the phone booted, and it is doing the same thing again. reboots to a green screen where it tries to optimize apps, stays there for about 20 seconds, and reboots over and over again in the same cycle. I have tried all other stock marshmallow roms that i can find, Odin won't flash older ones, (assuming its not letting me downgrade). Also another weird thing, every time I flash, the blue update screen goes to 32%, stops, erases, and reboots. Phone is on 6.0.1 version MMB29K.G920VVRU4CPH1 as seen in recovery. Any help would be gladly appreciated. Thank you!
I am having a similar problem with loading new rom. The farthest it gets is 32%. Sometimes it doesn't get even that far.
I ended up just buying a trashed s6 and swapping the motherboards. Only way I could fix it
Hello
I am very frequent with root and roms etc. but i am facing a big problerm with my s7.
i had already rooted it long back and had twrp, worked great for a year.
but suddenly around a month back it started restarting on its own. and at times it would get stuck at the Samsung logo.
i didnt care that much but then it kept on increasing and happened very frequently. the system will boot up and within 5 seconds it will get frozen, and no its not an app coz it happened in Safe Mode also,
also the screen would become hazy, like the tv does when there is no chane, become greyish.
also when i boot in twrp it would get frozen, like during wiping cache or installing, it will just get frozen in between
i tried upgrading to oreo somehow it started but when i restarted it wont start up. it would be stuck at s7 logo.
TWRP still getting frozen also i have tried other versions, no luck,
then i installed resurection rom for s7, it booted up, was working fine but then when i restarted it would not boot up system.
thats the problem i am facing now,
i tried down upgrading to Nougat but now it will say updating system and then erasing, and then it would get stuck wont boot up the system. it will keep restarting and then get frozen.
Literally spent more than 24 hours on this and no luck
please help
Greetings everyone,
I decided to post my problem with my phone after searching the entire internet for similar problem but with no luck. Anyway I used to play around with my Samsung j7 pro for 2 years, I managed to flash twrp and thus many other custom roms, until last week when I recklessly flashed a sboot.img.tar file through Odin in order to fix cellular network in a rom I flashed earlier, this alone bricked my phone refusing to get past the Samsung logo, so like I do always, I tried to restore my phone by flashing the stock firmware (9.0) which I always keep on my PC, but surprise, the phone refuses to go through the process and gives me this error:
sw rev check fail bootloader device -1 binary 6
(same with 8.0 and 7.0 firmware)
I searched the internet for same error but with no luck, because I understand it's a mismatch between device bootloader current version and the firmware bootloader's, that they should be the same or higher, meaning you can't downgrade, I get that! but I never seen device with negative figure (-1) what that's supposed to mean? my device bootloader used to be on 6, how did it managed to jump to minus one ?
then I tried to flash TWRP to see if I could flash a rom and get around it, so I did, but when booting into recovery the screen goes black, I thought first the phone turned off, but not really, because TWRP seems to work with screen completely black, I knew that because I accidentally touch the screen and I sense vibration, I managed to reboot the phone via twrp just by guessing the buttons location (screen always black) in order to prove that TWRP is working with screen off. I tried to flash multiple TWRP versions but the same problem, no screen just touch, by the way there is nothing wrong with display hardware because it shows Samsung logo at start and also can boot into download mode just fine.
I hope someone could help me overcome this big of an issue, because I tried everything.