Related
Well, I've made a huge mistake not backing up my phone immediately after rooting it and now I have to suffer the consequences for my dumb actions. I didn't think I'd run into much trouble, as I never have with either my Galaxy S3 or Desire HD before that and flashing countless roms.
Well, after rooting my phone with chainfire auto-root, I immediately flashed this rom and it was working fine, until I decided to flash my favorite Android Revolution HD rom.
Immediately after flashing it I received an error and ended up without Wi-Fi, or sound. There was a file posted called Wi-Fi fix, but it didn't work for me after flashing it, trying another modem did help with the WiFi (but still no sound) and it wont let me unlock my SIM.
I'm at a loss here, and not really sure what to do (other than trying to flash all of the modems available for 9505).
Tried flashing stock firmware through odin, but ended up with a failure to write.
If anyone could share some light on this matter, it would be greatly appreciated.
Yes, it happens a lot. On what rom are you excactly?
Can you try this?
1. Make sure you are on modem MJ5
2. Do a full wipe in recovery.
3. Flash this rom http://forum.xda-developers.com/showthread.php?t=2372286
According to that chef, you shouldn't need to flash any fixes after.
Or you can just try to flash this kernel. But i'm not sure on what rom you are:
http://forum.xda-developers.com/showthread.php?t=2273437
I did flash that ROM, and the modem, but it ended up freezing as soon as I opened the phone app and I still had no sound, wifi was working though.
Ended up flashing I9505XXUDMHB_I9505PHNDMHB_I9505XXUDMHB_HOME.tar.md5 through odin and that seems to have fixed my problems, phew.
Same problem After flashing leneageOS,
Device Mi note 4, karnel 3.18.
Could anyone help ! Please..
Hi all,
I have this annoying issue with [AOSP] Official 4.4.2 - S4 Google Edition - Final-R4 from jamal2367; current baseband installed XXUFNA1.
Problem:
When the phone loses connection, it dies. Then there is no way I can turn it on.
if unplugged from the power: it starts to boot and it dies again, sometimes at the "samsung boot text", sometimes a bit ahead, but it does not go further than the animated logo with 4 coloured bouncing balls (it does not matter how many time I try to restart the phone)
If plugged: it survives the first part of the boot most of the time, but it loops into the animated logo with the 4 coloured bouncing balls and the phone does not start.
Solution:
Every time I have to re-install Android, by:
- deleting Dalvik, Data, System, Cache.
- Install the ROM
- Apply a factory reset
At this point, if connected to the plug, the phone starts, but I have to go through the manual installation process.
This is a bit annoying I have to admin, anyone with this kind of issue, or am I the only one?
A few more info:
Phone was working great with jamal2367 4.3 (don't remember the baseband)
After 4.4 was out I installed it, but it was booting every 5 minutes or so, I decided then to go back to 4.3.
When I went back to 4.3, baseband was changed, but I kept the hold one.
Phone started to have random reboots as well, but once every 3-4 days, so I was ok with it.
4.4 releases were progressing so, after a while I decided to put it back.
I had the problem described above with previous (recent) baseband (like ml6and mj6).
Now I have the latest, but I have got the problem anyway.
A wild guess:
The phone now charges very quickly, I am wondering if the percentage that I see is realistic. Maybe it runs out of battery, which it could explain why the phone dies on reboots, but it does not explain why it loops once plugged in and why it does not turn off normally instead of just dying with a blink of an eye.
mmm that should not be the reason
Another wild guess:
I couldn't target a specific application. Sometimes it dies using fb, sometimes maps, sometimes hangout, sometimes a after a long phone call. The first two have "location" active, but I don't think that the last two are using it.
mmm that should not be the reason either.
A consideration:
I have noticed that once Android is installed, the phone signal is quite good, but then it goes down to one or two lines only. Most of the time I have one line only (in my area) and when it disappear, 6 times out of 7 it dies.
Thanks in advance.
R
PS=I could not post this into "Galaxy S 4 i9505 Android Development"
too long
be sure to flash from zero, wipe everything then flash 4.3
if everything fils go to stock 4.3 or 4.4 TW, then flash 4.4 gpe after
racoonlab said:
PS=I could not post this into "Galaxy S 4 i9505 Android Development"
Click to expand...
Click to collapse
did you try battery calibration?
also format everything in recovery before flashing,that should do the trick..
or maybe try another rom,if you still have issues then you may have to take it to Samsung care
anu.cool said:
did you try battery calibration?
Click to expand...
Click to collapse
Nope I will give it a try
also format everything in recovery before flashing,that should do the trick..
or maybe try another rom,if you still have issues then you may have to take it to Samsung care
Click to expand...
Click to collapse
Well, when I delete Dalvik, Data, System and Cache, I do it once I am inside _teamwin recovery_, I can also think about another ROM, but the one from jamal2367 is quite popular and I find it weird that no one else have the same issue.
Thanks for your reply though.
R
Same problem here...
I fixed it by flashing the stock image from samsung, and start all over again with cf_root and recovery. I use CWM, but that dont matter I think.
Loving my 4.4.2 Rom by Danvdh atm!
Good luck!
opticus44 said:
I fixed it by flashing the stock image from samsung, and start all over again with cf_root and recovery. I use CWM, but that dont matter I think.
Loving my 4.4.2 Rom by Danvdh atm!
Good luck!
Click to expand...
Click to collapse
Hi opticus44,
Did you install the stock image through Kies or from any other link? In this latest case, which one?
Thanks,
R
Hi,
you are not alone. we are 2 now.
I have the same problem but the problem stays with samsung stock rom. my phone still reboot random with stock jelly bean.
i use the 4.3 stock rom from this link below, they have high speed host.
http://www.android-hilfe.de/samsung...tes-rollouts-aktuell-xxuemk9.html#post6803655
Xv1nX said:
Hi,
you are not alone. we are 2 now.
I have the same problem but the problem stays with samsung stock rom. my phone still reboot random with stock jelly bean.
i use the 4.3 stock rom from this link below, they have high speed host.
http://www.android-hilfe.de/samsung...tes-rollouts-aktuell-xxuemk9.html#post6803655
Click to expand...
Click to collapse
mmm there must be some way. With the latest R1.1 I cannot even answer a phone call, with Ktoonsez's Kernel, with Alucard's Kernel no button works.
:-O
mmm also installing 4.3 back gives me random reboots. I am wondering if it could a wrong baseband.
it worked perfect for me for some hours. when i deactivated some bloatwares (g. earth, g. music, ...) it crashed and stucks in a loop reboot & crash at googke logo. swipe cache or wait some minutes don`t change anything.
i tried everything, now i have no idea what to do
I installed CyanogenMod and it is more stable. However it cannot do what is supposed to do, make and receives phone calls.
I wonder if it is a baseband issue, now.
R
anu.cool said:
did you try battery calibration?
also format everything in recovery before flashing,that should do the trick..
or maybe try another rom,if you still have issues then you may have to take it to Samsung care
Click to expand...
Click to collapse
Hi,
What tool do you use for a battery calibration?
racoonlab said:
I installed CyanogenMod and it is more stable. However it cannot do what is supposed to do, make and receives phone calls.
I wonder if it is a baseband issue, now.
R
Click to expand...
Click to collapse
Same issue if I put back Jamal [AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1,mmm, maybe the kernel....
The last thing I can say about it is that also all the sounds are gone. I cannot reproduce any sounds, notifications, alarm etc., it does not work on videos either.
I fix my problem! And I shared the solution here:
http://forum.xda-developers.com/showthread.php?p=49502855
racoonlab said:
Hi opticus44,
Did you install the stock image through Kies or from any other link? In this latest case, which one?
Thanks,
R
Click to expand...
Click to collapse
Sorry, long time since I last checked in. I downloaded official stock image from sammobile and flashed through odin.
same problem here
Hi guys same problem here,
GOOGLE EDITION 4.4.2 installed by Danvdh, Kryten2k35 & Ktoonsez on Galaxy S4 GT-9505 LTE with knox 0x1, and TWRP custom recovery when the battery reaches 0% turns off the phone I put the phone on charge and starts but hangs on colored dots.
How can I fix this?
Thx
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
first off i'd like to mention this phone was 100% perfect on stock Samsung rom 4.2.2 using Ktoonsez KT-SGS4 kernel for many months, until the day I installed this dreaded MDOB 4.2.2 rom and the "fix" that came with it
everything went bad on me back while I was running 4.2.2 stock unlocked boot loader and could never get it back to normal so this isn't a issue caused by 4.3 knox or 4.3 itself that i'm currently using. (i'm stuck on 4.3 roms but had this issue way before 4.3 existed)
i'm having an extreme amount of issues AFTER installing the MDOB rom, even after changing rom back to stock (flashed back to stock rom with ktoonsez kernel which is what I was using before I installed MDOB rom and phone has been royaly screwed ever since that day) more specifically I think it happened from the "i337M fix" that's included with the rom, either way after installing this rom I've never been able to get my phone back to normal.
everything runs fine except until I install a custom kernel (Ktoonsez KT-SGS4 kernel) then all hell breaks loose.
I don't blame the kernels or my current rom since I've ran this before for many months until the day i installed MDOB rom on my phone my phone was a dream machine.
issues since this rom has been installed include:
Issues:
A. RANDOM SLEEPS OF DEATH (phone shuts off or freezes)
B. random freezing while trying to turn on phone or enter recovery
C. some kernels won't work proper (specifically ktoonsez KT-SGS4 kernel) example gpu stuck at max while idle and downclocking when screen is touched with this kernel
D. wifi won't work with custom kernel on stock 4.3 rom without build prop edit to ro.securestorage.support, although it should
E. weak wifi and mobile signals
F. bad battery life
G. bad call quality
H. More that I can't remember off the top of my head
here's my flashing process, in attempts to remove as much as possible:
I know a few of these steps are probly pointless but hey can't blame me for trying.
step 1. enable usb debugging & unknown sources
step 2. install root & recovery
step 3. fresh boot phone let files settle so they can save (5mins or more) then plug into computer while turned on and delete everything
step 4. reboot into TWRP recovery (version 2.6.3.1) and clear everything, full advanced wipe, factory reset, format data than clear cache/dalvik afterwards just to be sure
step 5. remove SD card plug into computer and format to make sure there's nothing
step 6. install rom
step 7. (sometimes) clear cache/dalvik/permissions after rom install, although fix permissions seems to break my permissions rather than fix them or maby my permissions just break during flashing and I just can't fix them (haven't tested enough to be 100% sure)
i'm SOOO temped to try a full nand erase since i noticed there ARE still lot's files on my phone directory even after wiping, but i know that isn't a good idea;(
once stock kernel is back on my phone these issues are all gone.
Ktoonsez says it's not his kernel (used to work before, so i have no reason not to believe him), he says it's the rom well i'm on 100% stock Samsung rom (exception of kernel) and the rom was built to act the way it does so you can't really blame the rom so who do i blame??
until i went to go try wicked rom and flash back to stock I didn't realize these things were still on here, but now they emerge! wicked rom was giving me some (unrealated?) issue so i decided ima go back to stock so i flashed stock rom via odin (pc) and right away i noticed the 4G symbol, Samsung wallet, desktop not setup proper (no shortcuts) this ONLY happens when switching from wicked rom to stock rom on the first flash, i flash again everything looks how it should, and in order to get it to do this again i have to flash back to wicked rom and flash stock rom again and BAM it happens.
i knew my issue started on the same day that i installed this MDOB rom but after doing a full wipe and MANY "fresh" stock rom installs later i stopped questioning the rom and just lived with a crap phone that reboots itself all the time and has bad battery life, AS SOON AS I SEEN THE SAMSUNG WALLET bam it hit me like a truck, IT WAS THE MDOB ROM INSTALL.
UNLESS stock Samsung rom comes with wallet preinstalled and hidden on stock/wicked roms than the ONLY other way it coulda got on my phone is from the MDOB rom.
I can wipe/delete/factory reset/flash with twrp & odin on pc all I want, my roms are still messed up after FRESH installs. I believe there is still left over files from this rom/fix, I didn't think there would be anything until I noticed when i'm flashing from wicked rom back to complete stock rom using odin on pc I experience things from MDOB rom (while It should be 100% stock after odin (pc) flash, but it's not)
after the first flash from going from wicked rom back to stock I always experience the following "bug" i'll call it a bug since these things ALL HAPPEN AT THE SAME TIME: once I flash AGAIN all these symptoms go away until I go back to wicked rom and flash back to stock rom than right there after this first flash going from wicked rom BACK TO stock ALL these symptoms come back until I flash stock firmware AGAIN, a second time (even though I just flashed it)
Symptoms:
1. Samsung wallet appears in my apps (this was only EVER on my phone once, when I had the MDOB rom on my phone), this thing shoulda never somehow appeared back on my phone in any way shape or form after ditching the MDOB rom, but again is comes back after the first flash going from wicked rom to stock rom.
2. I get the 4G icon from MDOB rom (not the LTE icon I SHOULD have while on stock, when on wicked rom I have a little LTE icon with a tiny 4G above it, the only time I've ever had just a 4G icon (without LTE) like this is when I had MDOB rom on my phone (which is the only other rom I've run other than wicked rom and stock rom).
3. this icon ONLY shows up after the FIRST flash from wicked rom back to stock, once I install stock AGAIN than it returns to it's normal LTE icon.
4. now i'm not just *****in about an icon here, this is just a part of my problem (indicator if you will), when my rom is "bugged" after first install from wicked rom to stock rom my wifi works normal how It used too. but once corrected (flashing again) AND using custom kernel on STOCK firmware it breaks my wifi 100% broken until I use this little build prop edit fix, set ro.securestorage.support = true to false, bam wifi now working but the rest of my problems are still there (wifi used to work 100% on custom kernels and everything until MDOB rom touched my phone and left this "bug" behind)
5. when this 4G icon appears after this "first" flash back from wicked rom to stock rom I also experience something else, my wifi button works during first boot setup and auto enables itself and I have no issues with my wifi connecting (as soon as I see this toggle on I already know once my phone locks onto the network it's gonna give me a 4G icon and not an LTE icon like it should and sure as shiznit it does, as soon as I get my icon back to how it's supposed to be (LTE icon) all of a sudden wifi won't auto connect on a first boot anymore, never, 100% never. (back before installing MDOB rom I used to auto connect 100% of the time on first boot) like it does now only when it's "bugged" out.
6. apps are missing, when this "bug" appears there's no app shortcuts on the desktop of my phone by default after fresh flash like there should be, sometimes they appear on first flash once in awhile (some apps might not even be installed? or just shortcuts missing, have yet to verify)
7. it feels like the phone flashes way too fast (second flash takes longer, I think?) and more/all? apps get installed on second flash, and Samsung wallet get's REMOVED (how'd it even get there? other than bein left behind from MDOB rom, same with the 4G icon, that icon isn't in either of the two roms I use so how does it get there? and ONLY at the same time the wallet magically appears and the rest of this stuff)
8. when this 4G icon appears my phone seems to be great except for the fact that I know my rom didn't install properly since i'm still missing apps ect, once I flash again, apps appear, Samsung wallet DISappears, 4G icon gets replaced with LTE icon and everything is A-OK until custom kernel is installed, remember this is NOT the kernels fault as it ran 100% perfect for many months ON THIS PHONE until the day this MDOB rom was installed, and it's had these issues ever since.
some of the things I've tried:
- Countless wipes, including full advanced wipe, restore to factory, data wipes
- Ton's of fresh installs of BOTH versions of 4.2.2 - now doing same with 4.3 and wicked rom 9.1
- Tried wiping using TWRP and odin mobile (flashed mobile odin via TWRP, it works incase anyone didn't know)
- Tried flashing roms using odin (pc) v1.85, v3.07, v3.09
- Downloaded new copys of roms from new sources to make sure my roms weren't corrupted in anyway
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Amb669 said:
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Click to expand...
Click to collapse
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
hednik said:
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
Click to expand...
Click to collapse
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
I've flashed his rom on and off. Never had the issue. The rom doesn't invade anything a full wipe wouldn't cure. If it doesn't full wipe then it's the recovery. It helps once in awhile if you Odin back to stock or even copy your sdcard contents and format your sdcard to make it fresh. read up on it first.
Sent from my SGH-I337 using Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
Also I recommend doing 9 wipes when swapping roms. It sound ridiculous I know but I do it and have never had issues.
Sent from my SGH-I337 using Tapatalk
Amb669 said:
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
Click to expand...
Click to collapse
Just odin back to stock and set if that clears things up. It should solve any odd problems. The thing with flashing rom's is that someone's issues cannot always be replicated.
Going back to Odined stock will take it back to factory stock then do a factory reset in stock 3e recovery and you should be fine
I have an extremely persistent set of problems:
1. Unable to record video
- stock camera freezes and the phone restarts (no matter the resolution or storage)
- other camera apps (mx, open, google..) either freezes or acts like its recording but it doesn't
2. While playing some videos, the phone freezes and restarts (in 90% its instagram videos, but sometimes it plays them fine)
What i tried:
- a bunch of roms. The problems probably started with some of them.
- returned to a stock lolipop
- several custom and stock kernels
- a bunch of camera apps
Currently i'm on Audax rom v26.1 with its audax kernel.
Does anyone have idea what could i try?
Could it be a hardware problem? (other than that, camera works fine)
Thanks in advance.
So I solved it by:
Using Odin 3.11.1
I have already tried Factory reset, wipe cache, wipe dalvik, flashed the latest stock Lolipop or older lollipop with ODin and nothing solved the problem.
So I tried to flash the latest stock lolipop with Odin and marking checked (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update).
I suspect that the Phone EFS clear did the trick. It's function is related to the modem and radio of the phone. And clearly the modem has a problem here.
I hope this will help anybody out there having this issue.
This problem happened after trying to flash lollipop using FlashFire app to reserve the root that I had in my previos Android KK 4.4.2.
Phone: Galaxy Note3 N9005 Malaysian
hayder78 said:
So I solved it by:
Using Odin 3.11.1
I have already tried Factory reset, wipe cache, wipe dalvik, flashed the latest stock Lolipop or older lollipop with ODin and nothing solved the problem.
So I tried to flash the latest stock lolipop with Odin and marking checked (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update).
I suspect that the Phone EFS clear did the trick. It's function is related to the modem and radio of the phone. And clearly the modem has a problem here.
I hope this will help anybody out there having this issue.
This problem happened after trying to flash lollipop using FlashFire app to reserve the root that I had in my previos Android KK 4.4.2.
Phone: Galaxy Note3 N9005 Malaysian
Click to expand...
Click to collapse
Hi Bro,
I have same kind of issue posted here.
https://forum.xda-developers.com/htc-explorer/help/sound-speaker-mic-headphones-hardware-t3608070
Can you help me on this or give some idea?
jmsrajkumar said:
Hi Bro,
I have same kind of issue posted here.
https://forum.xda-developers.com/htc-explorer/help/sound-speaker-mic-headphones-hardware-t3608070
Can you help me on this or give some idea?
Click to expand...
Click to collapse
Hi there,
Sorry, but did not face any issue like that before.
If you have searched a lot for a solution and could not solve it, I suggest that you install this ROM:
https://forum.xda-developers.com/galaxy-note-3/development/purify-cm-13-hlte-n9005-unofficial-cm13-t3337234
This happened to me once after a terrible mistake , which is not related to my above issue. Then I installed this ROM and never looked back. Much snappier phone, lower battery usage and less heated device. I just love it. The only thing that I missed, the better camera app in the stock ROM, and the TouchWiz ability to show multiple apps at the same time.
I strongly suggest that you do a Nandroid backup then give this ROM a try. If you did not like it, you can always return to the Nandroid backup again.
You are frustrated now, like I was. Take a deep breath, and remember that we all went through such bad times with our phone, not just you. This is part of the experience of using such complicated devices. You will solve it eventually, believe me!
Plz help me!!!!
Im installing custom rom in sm core prime 360H via twrp but its shows error number7
How to fix it..???
Any one help me plz i need it
Probably your internal storage if full or something. Which ROM were you installing anyway?
rms112 said:
Probably your internal storage if full or something. Which ROM were you installing anyway?
Click to expand...
Click to collapse
I tried every custom rom but same issue
Error code 7
My phone storage is almost 70%free
Plz help me to solv this
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
rms112 said:
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
Yes in 100% sure its 360H stock rom
I also try ins and inu both stock rom but issue is same
Can u tell me which stock are you use
Bdw are you indian....? Because my English is lil bit week?
rms112 said:
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
I use this method also which is given in link but same issue ?
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Thnx for ideas
my problem solved
Now Installed​ lineage 7.1
Bdw how to close this Thread ?
rms112 said:
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Click to expand...
Click to collapse
RR 5.8.3 working fine
I trywd this but home button and resent apps cnt shows
Any idea about it...
rms112 said:
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Click to expand...
Click to collapse
RR 5.8.3 working fine ??
I trywd this but home button and resent apps cnt shows
Any idea about it...
Works fine with me. RR beta 1 based on 7.1.2.
You should ask on that thread of ROM. Maybe hash can help you!
Good luck.
Help i'm not sure but i think i might have bricked my sm-g360h.
HELP I'M NOT SURE BUT I THINK I MIGHT HAVE BRICKED MY SM-G360H. When i had some issues with my phone, I used twrp to flash cyanogenmod 12 custom rom on my phone some two weeks ago and it flashed properly. After a number of issues, i decided i wanted to go back to the stock rom. so i downloaded the firmware from sammobile, installed odin and flashed it with odin. when the flashing was done successfully, my phone rebooted instead of giving me the screen of a newly launched phone it went to the home screen, and had a pattern lock screen and tried my pattern lock from when i was on cyanogenmod 12 and it unlocked it. and gave me the screen of a newly lauched phone but before i could continue with startup, it rebooted immediately and each time it get to the lock screen, it goes to the screen with the samsung logo after some few seconds and then come back to the lock screen please help what do i do?
PS: one of the issues i had that made me want to return to the stock rom was the fact that i couldn't change my screen lock to none or swipe after i decided to use pattern on the cyanogenmod
yemialabipurpose said:
HELP I'M NOT SURE BUT I THINK I MIGHT HAVE BRICKED MY SM-G360H. When i had some issues with my phone, I used twrp to flash cyanogenmod 12 custom rom on my phone some two weeks ago and it flashed properly. After a number of issues, i decided i wanted to go back to the stock rom. so i downloaded the firmware from sammobile, installed odin and flashed it with odin. when the flashing was done successfully, my phone rebooted instead of giving me the screen of a newly launched phone it went to the home screen, and had a pattern lock screen and tried my pattern lock from when i was on cyanogenmod 12 and it unlocked it. and gave me the screen of a newly lauched phone but before i could continue with startup, it rebooted immediately and each time it get to the lock screen, it goes to the screen with the samsung logo after some few seconds and then come back to the lock screen please help what do i do?
PS: one of the issues i had that made me want to return to the stock rom was the fact that i couldn't change my screen lock to none or swipe after i decided to use pattern on the cyanogenmod
Click to expand...
Click to collapse
Sounds like problem of dirty flash not hard brick.
Here's what you should do.
1) go to twrp recovery using power + vol up
2) wipe everything except storage
3) Flash cm 13 beta 5 or 6 ( the latest beta) or lineage OS or RR
4) if the problem still exists, then used Odin to flash stock ROM and repeat steps 1 to 3
Also don't use cm 12. Its EOF and you won't get any bug fixes and updates.