Hi,
I have repeatedly weird issues with my phone. Both on stock rom as well as on custom rom (Renovate ICE) i get permanently apps crashing and the phone rebooting /crashing very often. Its mostly unuseable.
I also had issues in reflashing stock in the first place, as described here: https://forum.xda-developers.com/galaxy-s8+/help/reflash-stock-fails-mismattached-t3754609 it took many attempts.
Today I wanted to give it a new try flashing the newest Renovate ICE version and now after using Aroma installer (which in the first run threw an error also, only the 2nd run workd) the phone is again not booting at all but stuck on initial logo.
I am feeling this must be a hardware issue. Is there any means to test this (e.g. memory failure, or something similar) ? Any experiences like that by anyone?
Im not sure if I can try to return the phone (it is just a few weeks old) given that i flashed custom firmware. Recent Renovate ROM claims it would Reset Knox to 0x0 but since it does not even boot Im not sure about that either.
Any suggestions?
Thanks
Related
In an attempt to deal with massive instability I was able to upgrade from Samsung Stock to SlimKat 4.4.4r1. The instability problems remain but now I can't install apps. I have tried to flash to Carbon ROM but that doesn't take.
Curiously, all of the indications are that the apps and ROMs are installing but they in fact they actually don't.
The device doesn't even stay on long enough for me to alter a Setting, it trips over in a matter of seconds and reboots. Each time, I get the error message “Unfortunately, The process android.process.media has stopped”.
Could this be the Brick Bug manifesting itself? Perhaps if I repair the PIT that would fix it? Luckily I can access TWRP 2.7.0.0 recovery, I have tried to upgrade to TWRP 2.8.0.0 but that has failed also.
Any suggestions would be welcome
Hi, I would like to thank all those who took the time to read my description. Clearly it has you flummoxed too.:laugh:
In the meantime, I tried flashing Stock ROM but no joy and then I tried repairing the PIT, no joy there also.
My options now are either to ask Samsung to take a look or else wait for a functioning Tab with a broken screen to come along. My Tab is in superb condition and it would be a shame to let it go without at least making another attempt at rescue.
Please could someone help ! I'm trying to unlock my XT1032. I have the correct Sim-Unlock (network unlock) code from my old telco, but... it won't work because the phone is rooted, bootloader unlocked (S-ON) running CM13.
I figured that returning it to a stock build would allow me to unlock the phone, then I could re-root and return to CM13 on my new network.
However..... there are about a dozen guides on returning a Moto G to stock and the first one I tried left the phone stuck on the 'Warning: Bootloader is unlocked' message. Since then, I've tried several other guides and have got nowhere fast. I've been on this for four hours now and the only thing I seem to be able achieve is to get TWRP or CWM recovery on there by flashing from fastboot. Every other image I try either gives 'preflash validation failed' messages, sticks on the Bootloader Unlocked screen or gets it stuck in a bootloop!
I just want to switch networks... Why is this so bloody difficult ?
What Firmware did your XT1032 originally come with? or which Carrier?
Kitkat I think, and it's Tesco (UK).
I subsequently did the OTA update to Lollipop and then.... WHOAAAAA.... hold on... it's booting !!!
I don't know how, or what I've done to get this far, but the only thing I can think of that's changed is that the battery is now at 100% charge. It appears as though it's successfully flashed the 5.1 untouched ROM from http://forum.xda-developers.com/devdb/project/?id=7981#downloads
But, I've tried flashing that loads of times this evening and it's failed everytime.
Having said that it's booting, it's sitting here on the Motorola logo - and it hasn't got that far in the last five hours.... I'll be back shortly !
Update: It worked ! It completed the boot, I put the new SIM in, it asked for the unlock code and this time it worked OK. Now I'm tackling putting CM13 back on it. I think I'll stick with TWRP rather than CWM recovery, as long as TWRP can handle the automatic updating for the CM nightlies.
I have no idea what went wrong there - maybe it was just that the battery had to be at 100% ?? Who knows... Thankfully I doubt I'll be tackling that again !
I don't know if things have changed, but I would be careful with OTA Updates in CM. People have hard-bricked (phone is effectively destroyed) applying updates in this way. I also suggest you avoid official Motorola updates, rather use the factory firmware images available here: (which already include the content of OTA Updates)
[INDEX] Moto G [Falcon][Peregrine] Factory Firmware Images
Thanks for replying anyway mate. In the end, it's all good now. Unlocked and back on CM13 and on my new network !
Ahhh... not so good after all. The phone reboots every time you try to uninstall an app. I've tried flashing back to CM12.1, the latest stable release, and it does the same, so I've obviously screwed something up along the way.
Could someone help me flatten this thing completely and get it working normally please?
I've tried reflashing loads of times, even tried Cyanogen Recovery instead of TWRP but nothing I do gets rid of this reboot problem.
Can anyone assist please?
OK, so I've followed the procedure detailed here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 and flashed the Untouched 5.0.2. EU Stock ROM successfully, but it still reboots when you try to uninstall any app.
Whatever it is that's causing this is not getting overwritten by the flashing procedures I'm using is it ?
HELP !!!!!
@aneng64 - You have not done what I told you to do. Read my post again.
Yes I did... and I still had the same problem. It was only once I stopped trying to flash zips from TWRP and used mfastboot to flash the whole set individually (non-hlos, motoboot etc) that I got it to behave. The issue, incidentally, seemed to be the same one mentioned elsewhere here that also causes settings to crash when you try to go into settings, security.
Once it was stable with a stock ROM, I was able to flash CM13 again and it's now sorted. Thanks for your help anyway.
Hi Guys,
Hopefully this is in the right section
I have a Note 4 SM-N910G and its just turned absolutely useless since I factory flashed it. I have rooted it before and bricked it and un bricked it before so have some experience with it. I recently wiped my phone and did a firmware restore using Samsung Kies and since I did the phone is absolutely useless. It started out fine for an hour or two and now it lags by like a minute with any action, even trying to bring up the keyboard when typing. It will reset itself, lock itself, crash, just un useable. I've tried reflashing it again stock a couple times and still the same everytime. It went from perfectly fine to dreadful with the original mentioned restore. I did just recently get an error code of "sbl1 partition doesn't exist" in Boot recovery mode.
Does anyone know if this is fixable and not a hardware issue?
Should I try and just root it again and flash a non-oem rom? (I havent had the time to do it recently)
many thanks,
Tekkado
Hi Guys,
Also I should add that when I was rooted the phone was fine but when i went to unroot through super user the phone was still functioning as though rooted and I couldnt download software updates because my device was "modified".
So thats when i just flashed stock firmware and again now flashing through odin aswell it proceeds fine then the device will say installing updates and then give a no command error or seandroid not enforced. Everytime is basically a different message.
How can I just wipe everything and get back to stock?
Thanks
So to add to this is there any relationship between the firmware running and the bootloader? I just realised that before i tried to flash stock firmware i was rooted and didnt un root via superuser because in the past that did jack all.
I flashed dr. ketan rom this morning and the phone was operating as normal very snappy but as soon as i downloaded a new app from the play store (reddit and chrome) again it turned to absolute crap.
Is there a disconnect here that i missing that can be fixed?
Thanks
Hello there,
Please forgive me if i posted this thread on the wrong place.
-I would've not posted a thread here unless this got serious, so i own a Samsung Galaxy S6, it's 1 year old phone, when i first got it, i used it normally like everyone else and had no problem with it, but my curiosity got me to root the phone, i still did not get any problem with it until i chose to add a ROM. I used NNE 5.1 S8 port and it was working well until it got my phone broken somehow.
-My phone started acting really strange after 2 months of activity of that new ROM, my phone just started restarting randomly and it got me worried, i thought it's an application problem so i first just factory reset it. It seemed it was not the problem on an application, so i chose to change my firmware to a stock one. I searched up recently on the newest firmware for S6 and i found out it's: XEF (France) , PDA (AP): G920FXXU6ERC1 and CSC : G920FOXA6ERC1 on 2018-03-22. I Downloaded 4 files: BL,AP,CP,CSC , and i found out about PIT on one of the posts in this forum (Filename: SM-G920F-ZEROFLTE_EUR_OPEN.pit).
-Before i flashed with Odin, i wiped System, Data, Cache and Dalvrik Cache. The firmware worked well but after 1 hour it started doing the same thing but now differently. It happend to me only 1 time that it froze up on an application, but i think that is just an app problem. The main problem is that when i lock my screen, i cannot unlock it anymore, it just freezes there until it restarts after a short period of time. After the restart, it just keeps going, restarts, asks for pin, restarts and so on.
I tried removing the sim card and putting it back in, did not work.
I tried Safe mode, still same.
Model of phone: SM-G920F
Current firmware: XEF (G920FXXU6ERC1)
Android version: Nougat (7.0)
If you can help me, or you know something about this problem, please repost here, i would be really grateful since this is my only phone
Ininstall twrp backup everything most important efs partition.
Install samsung switch and pray that it asks you to do an update. If not try to flash a diferent version of nougat for example November security patch and try again with samsung switch
lenovot said:
Ininstall twrp backup everything most important efs partition.
Install samsung switch and pray that it asks you to do an update. If not try to flash a diferent version of nougat for example November security patch and try again with samsung switch
Click to expand...
Click to collapse
How could samsung switch possibly help?
I did flash it with different versions already, but no luck :/.
I've been praying a lot for this lately but it is not working lol
Please Bump this!
try doing this.
1) go here: https://updato.com/
2) choose download 2 roms. 1 nougat and another marshmallow (to my knowledge, stock roms are one file. no more splits and unless otherwise stated... no need for pit)
3) first flash nougat using oden
4) try the phone for a few some time.
if after a set amount of time, phone works fancy and no issues present then it's solved.
if not... install marshmallow. then try again.
if all this fails then...
install nougat. as soon as possible afterwards install twrp.
boot into twrp and just leave it there. my twrp locks after a while and screen goes dark until user interaction (just like it's supposed to)
if the same thing happens then its a hardware issue... probably... (i have had my main board fail... kinda similar not similar issue... hope you dont have the same issue and that its just software related)
good luck.
In my case every time there was an update available it would download the whole firmware and by doing so you would get the most fresh and updated version. Also it updates every partition to match
Already created thread in the wrong place https://forum.xda-developers.com/showthread.php?t=3952280
I have HTC U11+ TW version. Ever since I got the Pie update, my phone is freezing a lot. I need to force restart it 10+ times a day. I tried factory reset, clear cache, etc. Nothing works. I did not have any experience with flashing, but I have been reading a lot. I have my bootloader unlocked with S-ON.
My current build number is 2.15.709.1, since I wanted to downgrade, I tried flashing stock image HTC_U11+_TW_1.24.709.999_Images_OTA using fastboot (no TWRP). My phone went into a bootloop when I did that. I think this is because I can only flash an image with the same build number? Anyway, I flashed a HTC_U11+_TW_2.15.709.1_Images_OTA image and my phone is back to where it was, Android Pie (no bootloop), but still freezing a lot.
I found the HTC_DevInfo_Tool.zip tool on this thread https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481, but I am not sure if it will work on my phone.
Can someone advise what should I do to downgrade? Also did anyone face a similar problem after the update?
I found someone tried what I wanted to do here
https://forum.xda-developers.com/htc-u11/help/error132-signature-error-downgrade-htc-t3948079
Looks like it wont work?