Hi everyone,
I've been a proud GT-I9100 user now for almost a year, without any bigger problems. However, since two weeks, my sgs2 is rebooting itself when disconnected from the USB cable.
Every time I disconnect my device from the charger, it reboots 5-10 seconds after disconnection. As you are aware, the reboot sequence is normally:
- SGS2 text screen
- splash screen
- bootanimation
- lockscreen
- asks PIN code
- ready to use.
In this case, however, it completely skips the SGS2 screen, splash screen and the PIN code. In short, the bootanimation suddenly shows up and then you are again ready to go just in a few seconds without putting in your PIN. As I said, it's been like this for two weeks, but I was too lazy to do anything about it until I accidentally removed the plug while browsing the web and lost some important information in the process. I already tried a different charger and cleaned the USB port with pressurised air without any effect (not that I expected it to have).
I've heard of a "soft reboot". Could my issue be that and how could I fix it?
Rom: Hydra h2o v. 1.4.1.
Kernel: Hydra r26
Recovery (came with the rom): CWM Touch 5.5.0.4.
All found at: http://forum.xda-developers.com/showthread.php?t=1403044
Any help would be appreciated!
Oh, and one more question. If I wanted to flash the official firmware back with ODIN, would it overwrite my kernel? If so, would a Nandroid restore also restore my kernel back? (Stock --> CF-Root via ODIN --> NANDroid restore --> back to hydra kernel?)
Thanks in advance! :fingers-crossed:
edit: Here is a video where I show both the "soft reboot" and a normal one to compare. Please don't mind the quality which is a bit shabby.
http://www.youtube.com/watch?v=vDSFvV91tuo
Try to wipe data/factory reset in cwm recovery mode(backup your current rom first)
Then reboot device... if the problem still appear, flash another stock rom via ODIN PC...
If the problem is the software, won't backing up in CWM and restoring it after a wipe just make the phone exactly as it was before wiping? So the problem won't go anywhere. In fact, as I think of it, if the problem is software based, would anything, including ODIN stock flash, help at all if I later restored the NANDroid backup? Would it just bring the problem back?
What kind of reboot this even is? I've actually never seen a thread about a reboot which skips the SGS2 screen, splash screen and PIN code...
Flash back to stock -> Root -> Find out which Kernel you want that is used in the custom ROM and flash it separately through either odin if tar file, or through cwm if zip file.
T__ said:
Flash back to stock -> Root -> Find out which Kernel you want that is used in the custom ROM and flash it separately through either odin if tar file, or through cwm if zip file.
Click to expand...
Click to collapse
Thanks for the reply.
However, I already know that this way I can get rid of any software bug causing reboot, including this (i hope so, else it's gonna be a warranty case). The question i'm pondering, is still, will the problem will come back when restoring a nandroid backup of the phone as it is now.
Anyone know the effects of a nandroid restore? Or the kernel question?
Related
Hi all,
For the last couple of days I've been trying to flash my Galaxy S with ICS333 using the following guide - http://forum.xda-developers.com/showthread.php?p=25722239#post25722239
-----------
"3. Enter Download Mode, open Odin, check Re-Partition, press PIT button and browse for the PIT file, press PDA button and browse for the PDA file in the ROM folder, press PHONE button and browse for the PHONE file, press CSC button and browse for the CSC file and finally press START button.Wait till it`s finished and when the phone reboots disconnect from PC.
4. When the phone has booted into the ROM and you see the wizard screen just enter download mode again, plug your phone into the PC, open Odin, press PDA button and browse for the CF-Root kernel, press START button and wait for it to finish.After the phone reboots disconnect it from the PC, let it boot and when you`re in the ROM, set your phone to mass storage mode from settings>wireless & network>usb settings and plug your phone into the PC, copy the ICS333 ROM to your internal SD root location, assuming you have downloaded it from here : http://goo.gl/LuXvH and disconnect from PC.
5. Enter CWM, Wipe Data/Factory Reset, Wipe Cache, Wipe Dalvik Cache and flash the ROM.You will notice the phone will reboot immediately because it will switch kernels, from CF-Root to Semaphore, prior to flashing the actual ROM.As a result, it will boot loop or get stuck on Semaphore logo, so just force it into CWM using the 3 key combo (no need to take the battery out).Now flash the rom again and wait till it`s finished and > Reboot to system!."
-----------
After performing stage 3 I waited for the phone to restart and understand that I should have seen a ROM/Wizard appear. This did not happen and now the phone just goes straight into CWM upon boot.
Whilst in CWM I get the error E:Can't mount /sdcard/ and non of the functions work. What should I do next? I've had a search around these and other forums but can't work out what to do. Don't want to just keep trying random things and end up making the situation worse.
Thanks for any help you can offer.
Louis
king llama said:
Don't want to just keep trying random things and end up making the situation worse.
Click to expand...
Click to collapse
get back into download mode to flash a rescue kit or a JVU upgrade from My Android Collections also tick update bootloader
But First power down, pull out Battery, SIM CARD, and EXT SD card, press power button for a minute , than power up without SIM and Ext SD Card...make sure you have more than 50% battery charge before you attempt any sort of flashing
Thanks very much for the help. Used the darkyrom resurrection kit and it worked like a charm.
king llama said:
Thanks very much for the help. Used the darkyrom resurrection kit and it worked like a charm.
Click to expand...
Click to collapse
One last thing before I go ahead and try flashing ICS again. Can I go straight from darkyrom to ICS or do I need to put a Gingerbread installation on the device first?
Thanks again
Louis
king llama said:
I need to put a Gingerbread installation on the device first?
Click to expand...
Click to collapse
nope, should work from there
xsenman said:
nope, should work from there
Click to expand...
Click to collapse
Sorry to be a bother again but I now have a new problem. I have updated to CM 9 android version 4.0.4 which appears to function correctly but gives me no access to the sim card (can't see any phone numbers/contacts and won't connect to the network).
I understand that this usually has something to do with EFS settings (I took a backup of the EFS using GPS Aids before I flashed) which I have tried to restore using Nitrality but with no success.
I have checked the sim card in another phone and it works correctly.
Starting to think that this flashing business is not for me.
Any ideas as to what I should try next?
Thanks
Louis
You can change the efs folder via terminal but I found the easiest way (I had incorrect imei on hellybean) was..
Flash stock GB via Odin. Flash semaphore kernal via Odin. To get cwm.
Boot into recovery and flash cm7, boot into recovery and flash cm9, boot into recovery and flash cm10.
Obviously make sure you have cm versions on the card first. Efs corrupts when you don't flash in order example GB to JB missing out ICS. Doesn't happen all the time but that's usually the cause.
Worked like a charm for me.
sent using my fat fingers from the robot eating the apple...
creative0100 said:
You can change the efs folder via terminal but I found the easiest way (I had incorrect imei on hellybean) was..
Flash stock GB via Odin. Flash semaphore kernal via Odin. To get cwm.
Boot into recovery and flash cm7, boot into recovery and flash cm9, boot into recovery and flash cm10.
Obviously make sure you have cm versions on the card first. Efs corrupts when you don't flash in order example GB to JB missing out ICS. Doesn't happen all the time but that's usually the cause.
Worked like a charm for me.
sent using my fat fingers from the robot eating the apple...
Click to expand...
Click to collapse
I have returned the phone to stock Gingerbread and the problem still persists.
This may humor some of you as to the stupidity I have displayed in messing around with rooting\rom'ing my i9505.
Sadly tho it's resulted in me bricking/semi-bricking the phone and I am tearing my hair out trying to fix it.
What I did to get me here:
- Within TWRP (existing recovery/root at the time) I wiped all my data from the internal storage. This in effect meant that I had no roms nor any backups to recover from. Super Doh! *facepalm* moment of the centuary... :S
- For one reason or another the existing rom i was on would not boot. I was effectively stuck in a boot loop on the Samsung Logo
What I have tried doing to fix it (and failed miserably):
- I thought that by at least getting a rom onto the device and flashing it I would be back in business however this proved to be a challenge as the samsung USB drivers do not work with TWRP so I cannot adb push or sideload as I have no rom/backup locally.
- So I rooted with CWM which worked a treat with sideload. So I rom'd the phone...however...the following now happens
- I cannot get into existing/current ROM. Boot loop
- I cannot get into CWM (frozen with blue text in the top left) and have re-downloaded ODIN, CWM several times and tried to flash several times. No joy...
- I can flash with TWRP however as mentioned above the drivers do not work so I cannot sideload.
Any ideas how to fix - very very very much appreciated.
Don't need comments how dumb I have been - I am kicking myself more than you ever will.
r34l1ty7 said:
This may humor some of you as to the stupidity I have displayed in messing around with rooting\rom'ing my i9505.
Sadly tho it's resulted in me bricking/semi-bricking the phone and I am tearing my hair out trying to fix it.
What I did to get me here:
- Within TWRP (existing recovery/root at the time) I wiped all my data from the internal storage. This in effect meant that I had no roms nor any backups to recover from. Super Doh! *facepalm* moment of the centuary... :S
- For one reason or another the existing rom i was on would not boot. I was effectively stuck in a boot loop on the Samsung Logo
What I have tried doing to fix it (and failed miserably):
- I thought that by at least getting a rom onto the device and flashing it I would be back in business however this proved to be a challenge as the samsung USB drivers do not work with TWRP so I cannot adb push or sideload as I have no rom/backup locally.
- So I rooted with CWM which worked a treat with sideload. So I rom'd the phone...however...the following now happens
- I cannot get into existing/current ROM. Boot loop
- I cannot get into CWM (frozen with blue text in the top left) and have re-downloaded ODIN, CWM several times and tried to flash several times. No joy...
- I can flash with TWRP however as mentioned above the drivers do not work so I cannot sideload.
Any ideas how to fix - very very very much appreciated.
Don't need comments how dumb I have been - I am kicking myself more than you ever will.
Click to expand...
Click to collapse
Can u try flashing Stock firmware using Odin it should work and incase after flashing it does not boot go to stock recovery and wipe cache reboot
123hiten said:
Can u try flashing Stock firmware using Odin it should work and incase after flashing it does not boot go to stock recovery and wipe cache reboot
Click to expand...
Click to collapse
Just wanted to say a big thanks. Your solution worked a treat. :good:
I take it I can now root as usual? Nothing else needed? ...apart from not trying to be stupid again
I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.
Bump I'm having the same problem, I'm on Verizon.
NBushyy said:
Bump I'm having the same problem, I'm on Verizon.
Click to expand...
Click to collapse
Yeah same here. Verizon. Forgot to mention it.
Still a problem. Bumping.
I am in the boat with you. I thought it was just me.
Same Black Screen issue
Did anyone have any luck resolving this? Ive tried with both twrp and cwm and same issue...?
Same problem on my Verizon model. Using twrp 2.6.3.3. Other roms work fine.
How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?
heleos said:
How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?
Click to expand...
Click to collapse
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)
try this
trackstar1414 said:
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)
Click to expand...
Click to collapse
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know
geosnipe said:
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know
Click to expand...
Click to collapse
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.
trackstar1414 said:
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.
Click to expand...
Click to collapse
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.
trackstar1414, say thanks by using the "Thanks' button like this.. keep me informed, CHEERS!
trackstar1414 said:
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.
Click to expand...
Click to collapse
Wanted to share this if you haven't read it..
http://forum.xda-developers.com/showthread.php?t=2449670
I had issues originally and had to flash back to 1.2.3.
What I ended up doing was switching to CWM 6.0.4.4 ( I was using TWRP 2.6.3.3).
His boot skipped the set up wizard as well, which was odd.
His was also the only ROM I ever got stuck on the fastboot screen while using twrp.
Try ( at your own risk obviously) flashing back to an older malladus (wipe all and boot till you get through the set up wizard),
Then back to recovery, do a wipe, without wiping the system partition, Data Cache and Davlik, and flash back to 1.2.5.
I didn't try it on 1.2.5. But that's how I got into 1.2.4.
Srvisg0d said:
I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.
Click to expand...
Click to collapse
Are you on 12B OTA? If so, that would be your issue. I took the 12B OTA and tried flashing Malladus and got the same issue you have. You can revert your phone to 11A and that should resolve your issue. http://forum.xda-developers.com/showthread.php?t=2448960 it will erase everything on your phone and go back to unroot.
Hi,
I have now rooted my phone and seemed to have removed the issue I was encountering. (IMS Framework)
However I have a few issues since rooting and am a bit unsure if what to do next
Any help to the following points is greatly appreciated. I am complete noob so only plain English and links to idiots guides please!
1) as a recent post states, I am also suffering from frequent restarts. They are quick restarts, only a few seconds (not like a hard reset etc) however there seems to be no specific reason or app causing it.
Posts suggest removing Knox might help?
I have a few root removal apps installed now so can someone tell me which Knox apps/programs can be safely removed???
2) when I press side button to unlock the phone, the screen sometimes freezes and doesn't respond. I have to press lock button again to lock, again to unlock then it works again
Not a major problem but annoying none the less
Any ideas??
3) I rooted to save battery by deleting the vodafone virus IMS framework however battery is still not as it good as it was before IMS framework. It doesn't drain within a few hours but again it's annoying.
Android system and OS are currently using more battery than the screen
So being a noob I'm. It sure where to go from here....
I've done a backup from nandroid manager app (in a cwm format it seems) and downloaded rom manager however CWM installer hasn't worked (something on the install guide says something about Samsung devices needing to install something but I can't find a guide on it)
(Please also confirm, the back up I did to external sd card has a few files including an md5 file, a few tar files and recovery img file. Is this correct? Is this the folder I would use to restore if I encounter issues later on??)
So I'm thinking I unroot and reinstall factory settings through kies etc (guide how to do this would be useful??!!)
Then root again and install a new rom (a nice clean one without the bloatware etc)
EDIT. IVE READ HOW TO INSTALL CWM FROM ODIN SO WILL TRY THAT.
QUESTION THEN BECOMES : WILL INSTALLING A CUSTOM ROM FIX POINTS 1,2 and 3????
Am I overthinking this or is there a quicker fix to my issues above?
Any help appreciated!!
1. If you have a custom recovery then flash knox removal script. Then you don't have to delete it manually. For example > http://forum.xda-developers.com/galaxy-s4/general/scriptknoxout-complete-brutal-knox-t2807172
2. Could be related to point 1.
Flash the script and it should solve most of your problems.
For your last question. There is no point in unrooting and using Kies if you want a custom rom. A custom rom will fix point 1, 2 and 3.
HELP!
so i install the Knox Zip (through teamwin)
Phone said "updating apps" then stuck on samsung screen.
Rebooted again.
Done multiple reboots through TWRP. Still same - stuck on samsung screen
I wiped data/factory reset but issue is still same.
I can get to the screen by holding down power volume up and home button but reboot not working.
I looked for restore but it is blank (i did a restore on SD but its not showing!!!)
I need help!
rootromnoob said:
so i install the Knox Zip (through teamwin)
Phone said "updating apps" then stuck on samsung screen.
Rebooted again.
Done multiple reboots through TWRP. Still same - stuck on samsung screen
I wiped data/factory reset but issue is still same.
I can get to the screen by holding down power volume up and home button but reboot not working.
I looked for restore but it is blank (i did a restore on SD but its not showing!!!)
I need help!
Click to expand...
Click to collapse
Either reflash the stock rom you are on
or
Flash a custom rom that you want.
Lennyz1988 said:
Either reflash the stock rom you are on
or
Flash a custom rom that you want.
Click to expand...
Click to collapse
Im guessing that has to be via Odin as there is no ROM file on my phone??
(or could i put a ROM on my External SDcard and flash via TWRP?)
rootromnoob said:
Im guessing that has to be via Odin as there is no ROM file on my phone??
(or could i put a ROM on my External SDcard and flash via TWRP?)
Click to expand...
Click to collapse
Stock ROM (download it on your pc) -> Flash it via ODIN
or
Custom ROM having it in your SDCARD -> Install it via TWRP (Custom Recovery)
Took a while messing around with sd card but managed to flash liquid smooth and all working
Annoyingly Odin didn't recognise phone but that's ill sort that out another time
Thanks for help
Hey wassup. So yesterday I rooted my phone and tried to install CM13 on it. Took a few tries since the rom I got was corrupted but I got it to work. Then I noticed it was guzzling the battery like lemonade (this EXACT same thing happened on my previous S4 too) so I gave up on it and decided to revert back to the stock rom. Everything went well... NOT. I downloaded the stock firmware (3gigs... zzz) and I flashed it with Odin and the phone restarted. The little android robot from the default unrooted recovery popped up and it had below it this: "Installing system update..." and then out of the blue it said "Erasing" and it's gear started rotating backwards. THEN, when it finished the normal Samsung Galaxy Note 4 logo popped up, went away and then CAME BACK AGAIN FOR LIKE 500 TIMES AND COUNTING. AOSP roms work just fine, it's just that touchwiz ones won't work whatsoever (even tried sixperience, no luck)... What should I do? I already lost my S4 due to this...
install TWRP custom recovery, boot up in recovery format system dalvik cache and internal storage then try flashing stock with odin hopefully it will work.
Try to remove battery first.from tsoch recovery wipe data cache and see if it works
dork997 said:
install TWRP custom recovery, boot up in recovery format system dalvik cache and internal storage then try flashing stock with odin hopefully it will work.
Click to expand...
Click to collapse
Been there, done that. Nope, still refuses to work :/
bumpity bump bump
Did you backup your efs partition before you flashed cm13? If not you corrupted your efs and your phone is a wifi tablet now because you cant use your modem.
travis82 said:
Did you backup your efs partition before you flashed cm13? If not you corrupted your efs and your phone is a wifi tablet now because you cant use your modem.
Click to expand...
Click to collapse
this never happened to me with my old s2 or s4
why is it happening now ?
Didn't backup. Now it just won't even work with odin. Whenever I try to just flash anything with it goes off and says 0 successes and 0 fails. What I did notice though was that whenever I installed a stock rom it starts this "Installing system update" with the android robot twingling it's antennaes and then out of nowhere it's blue bar goes away and it says "Erasing" then... bootloop. Now odin won't even work (explained above). Should I just give up and send it in for repairing? Or can ANYONE send me the twrp restore file, please...
Peontikos_Desmos said:
Didn't backup. Now it just won't even work with odin. Whenever I try to just flash anything with it goes off and says 0 successes and 0 fails. What I did notice though was that whenever I installed a stock rom it starts this "Installing system update" with the android robot twingling it's antennaes and then out of nowhere it's blue bar goes away and it says "Erasing" then... bootloop. Now odin won't even work (explained above). Should I just give up and send it in for repairing? Or can ANYONE send me the twrp restore file, please...
Click to expand...
Click to collapse
Hi
Same problem
Any ideas !!!
Hey,
I have the same problem it turns out after flashing, i cant remember, maybe dytto note 4 rom, it got stuck in continous bootloops and the only way it is working for me is when its charging. I know it sounds crazy but its the only way for me, ive tried installing stock different countries firmware and bunch of custom rom with no luck. I sent it to the place where i bought the phone and made myself look dumb asking why it is like that and i told them i had not do anything. After only a week they phoned me and said it was rooted (i did get the root out when i gave it but they somehow knew it was... later i understood that it is all about that stupid Know thing) and refused to cover my warranty. They said that the only way i can get it to work is to pay 300$ for new chip :,(
senon said:
Hey,
I have the same problem it turns out after flashing, i cant remember, maybe dytto note 4 rom, it got stuck in continous bootloops and the only way it is working for me is when its charging. I know it sounds crazy but its the only way for me, ive tried installing stock different countries firmware and bunch of custom rom with no luck. I sent it to the place where i bought the phone and made myself look dumb asking why it is like that and i told them i had not do anything. After only a week they phoned me and said it was rooted (i did get the root out when i gave it but they somehow knew it was... later i understood that it is all about that stupid Know thing) and refused to cover my warranty. They said that the only way i can get it to work is to pay 300$ for new chip :,(
Click to expand...
Click to collapse
ffs i'm not paying another phone's worth in a ****ing motherboard. I tried:
-Flashing the stock bootloader, fails at sboot.img:NAND Write start fail
-Flashing the PIT file, just... wont flash. Successes 0/Fails 0
-Flashing the stock AP file, bootloop
-Flashing the CP and the CSC stock files, serial(com) port cannot be opened.
****ing garbage. For some reason my phone's the only exception to the rule that phones able to boot into download mode are salvageable. It's going in for a repair and if it's more than $50 I'm not rooting again even at gunpoint.
Quick update:
I found a toolkit that has a flash stock boot image option. Had to recover to my cm13 backup to enable usb debugging. Will post results
Nothing of course...
try this step by step,
1. Download stock firmware THE LATEST ONE (n910c v5.1.1) from sammobile.com
2. Download newest Odin and Samsung USB; installed Samsung USB
3. I am assuming you have installed twrp recovery. Boot to twrp recovery and do a full wipe; wipe all!
4. Boot to downloading mode and install stock via odin. That is it.
Ps.... in case of failure, make sure you have installed Samsung USB! Or just reconnect usb cable with other usb ports untill it is working.
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Oliva.raiders said:
1. Download stock firmware THE LATEST ONE (n910c v5.1.1) from sammobile.com
2. Download newest Odin and Samsung USB; installed Samsung USB
3. I am assuming you have installed twrp recovery. Boot to twrp recovery and do a full wipe; wipe all!
4. Boot to downloading mode and install stock via odin. That is it.
Ps.... in case of failure, make sure you have installed Samsung USB! Or just reconnect usb cable with other usb ports untill it is working.
Click to expand...
Click to collapse
Well, crap I already sent it in for repairing but if the fuqing robbers decide to change the motherboard instead of doing anything to it and charge me 500$ to do so I'm getting it back and I'm trying this one. Already did but it wouldn't hurt retrying... BTW FOR THE LOVE OF GOD DOES SOMEONE HAVE A TWRP BACKUP FILE ON STOCK TOUCHWIZ? JESUS
radium56ad said:
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Click to expand...
Click to collapse
Is there absolutely NO workaround?
i had the same issue, this is how i solved this (you won't like it):
-deleted efs partition
-restored 5.1.1 coj5 via odin
-then took it to a samsung repair center to restore the imei
paid them like 50 bucks...that sucks. after this im backing up efs folder before flashing a rom.
radium56ad said:
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Click to expand...
Click to collapse
JuanWilliman said:
i had the same issue, this is how i solved this (you won't like it):
-deleted efs partition
-restored 5.1.1 coj5 via odin
-then took it to a samsung repair center to restore the imei
paid them like 50 bucks...that sucks. after this im backing up efs folder before flashing a rom.
Click to expand...
Click to collapse
Oh that's nothing man. The fuqing scammers told me the whole freaking board had to be replaced...
There's one thing I've noticed though that's PROBABLY gotta be the culprit. Whenever I install a touchwiz rom, the phone boots up fine for once, shows the robot with the "Installing system update" and then it goes off with "Erasing" followed by the bootloop. Could anyone please elaborate on this? I have a feeling this is what's causing this ****fest