Related
Just doing independent research
From 1:10 wonder has boot loop problem
Although you already do flashing well
No kidding, but the characteristic for the phone that possible have a boot loop are always have FORCE CLOSE app and doing RESTART itself
And in next day it restart and only showing samsung logo...
In this situation you can't get to recovery
It can fixed but only if we get stock firmware with wipe and boot loader to fix this issue
Maybe I8150ZSKI3 Android 2.3.6 (ASIA) can helped, all component to do hard reset is in this firmware
OPS– Ancora.ops.
Boot – APBOOT_I8150ZSKI3_CL613004_REV00_user_low_ship_EMM C.tar.md5.
Phone – SMD_MODEM_I8150ZSKI3_CL613004_REV00_user_low_ship_ EMMC.smd.md5.
PDA – SMD_PDA_I8150ZSKI3_CL613004_REV00_user_low_ship_EM MC.smd.md5.
CSC – SMD_CSC_GT-I8150-MULTI-CSC-OZSKI3_EMMC.smd.md5
I will try it first.. i will report latter
Reported..
Still have no change to bring that phone back to live -_-
Anyone..
Can help regarding this issue
Rio Saputro said:
Reported..
Still have no change to bring that phone back to live -_-
Anyone..
Can help regarding this issue
Click to expand...
Click to collapse
Sorry, I can't help, but in my flashing thread, it has also been reported. But I think it happens more often on phones with asian firmwares. I had one report in the german forum too, but I am not sure if it was an "asian" version.
I think if something happens while the firmware update with an asian firmware, it might end up in a bootloop. I am not sure, but I think it makes also the partitioning of the storage, isn't ?
It would be good if we could get a "gettogether" in this thread and have all the reports of the soft-/hardbricked SGWs. So we can analyse and maybe find out the reason or atleast narrow down the issue.
I would like to know:
1. Did you have a custom rom before the flash ?
2. Was your phone rooted ?
3. Did you make the internal/external swap ?
4. Did ODIN say PASS before you disconnected(before the bootloop happend) ?
5. Any other fancy modifications you have done and what we should know ;-D ?
greets
THE-E
THE-E said:
Sorry, I can't help, but in my flashing thread, it has also been reported. But I think it happens more often on phones with asian firmwares. I had one report in the german forum too, but I am not sure if it was an "asian" version.
I think if something happens while the firmware update with an asian firmware, it might end up in a bootloop. I am not sure, but I think it makes also the partitioning of the storage, isn't ?
It would be good if we could get a "gettogether" in this thread and have all the reports of the soft-/hardbricked SGWs. So we can analyse and maybe find out the reason or atleast narrow down the issue.
I would like to know:
1. Did you have a custom rom before the flash ?
2. Was your phone rooted ?
3. Did you make the internal/external swap ?
4. Did ODIN say PASS before you disconnected(before the bootloop happend) ?
5. Any other fancy modifications you have done and what we should know ;-D ?
greets
THE-E
Click to expand...
Click to collapse
My team already try for asian rom that you provide in your tread and the new version of stock rom. it didn't do full wipe just normal flash like the others
Only stock rom & rooted bro...
PASS but the phone not turn on -_-"
No swap partitions
Just regular phone for daily use
If we can found the stock rom with wipe and bootloader still can be fixed
Hopefully it can be fixed without go to samsung -_-
All of us must aware for this issue bro..
Regards
Rio Saputro said:
My team already try for asian rom that you provide in your tread and the new version of stock rom. it didn't do full wipe just normal flash like the others
Only stock rom & rooted bro...
PASS but the phone not turn on -_-"
No swap partitions
Just regular phone for daily use
If we can found the stock rom with wipe and bootloader still can be fixed
Hopefully it can be fixed without go to samsung -_-
All of us must aware for this issue bro..
Regards
Click to expand...
Click to collapse
I have edited my thread, it makes people now more alert about the risk of bricking.
Maybe it is more secure always wiping everything using ClockWorkMod:
Using this course of action:
1. Backup everything manually what you can!
2. Flash via ODIN ClockWorkMod Recovery on your device(english). Scroll down to other and select ClockWorkMod.
3. Once ClockWorkMod is flashed, go to the recovery:
a) backup and restore -> backup to external sdcard
b) backup and restore -> restore from external sdcard
This is to make sure the files aren't corrupted, if this is successful you can be sure everything is backupped. If you get a MD5 mismatch something went wrong. Try again!
c) wipe data/factory reset -> confirm
d) wipe cache partition -> confirm
e) mounts and storage -> format system -> confirm
f) mounts and storage -> format cache -> confirm
g) mounts and storage -> format data -> confirm
4. You restart your phone in Download Mode and flash a firmware using this instruction, which is provided in the thread under Firmwares.
5. Now you will have to flash again the ClockWorkMod recovery to restore your data.
Than open ClockWorkMod Recovery and:
backup and restore-> advanced restore from external sdcard -> select the backup -> Restore data -> confirm.
Now if you want the stock recovery back(needed for OTA updates) instood of ClockWorkMod, than go to the Others or Sonstiges and select the stock recovery, and flash it on your device.
6. Now you should have a fresh device like you have never flashed before!!!
Oh yeah, the reason why you have to make these complicated steps: Because you were flashing all different kinds of firmwares, you system will be a mess. To make sure your device is not a overwritten old firmware these steps are necessary.
Flashing via ODIN does not delete all old data !!!
I have to say also: I have flashed all the ROM's successfully before posting them in my thread about flashing.
greets
THE-E
Is it not important to say that the guy in original thread here:
http://forum.xda-developers.com/showthread.php?p=22560826
He had installed Rio's Black Note 2 ROM using CWM to do Nandroid Restore.....as is Rio's method to flash his ROM ???
Maybe is not important, but maybe is!!!
Sent from my GT-I8150 on Lanzarote Canary Vacation using Tapatalk
irishpancake said:
Is it not important to say that the guy in original thread here:
http://forum.xda-developers.com/showthread.php?p=22560826
He had installed Rio's Black Note 2 ROM using CWM to do Nandroid Restore.....as is Rio's method to flash his ROM ???
Maybe is not important, but maybe is!!!
Sent from my GT-I8150 on Lanzarote Canary Vacation using Tapatalk
Click to expand...
Click to collapse
Yes he already inform this...
But the question why just only him that get boot lop, this is kind a strange because another user didn't face the problem like this
His problem happened after applying V6 SC
I know that V6 SC update 9 RC6 have a change for boot lop, because for applying 100% must integrated built.prop
So many friend of my use V6 SC update 9 RC4 that more stable for our phone
Actually there is nothing different if we flash with nandroid and update.zip
The script doing same thing except for the user data
nandroid use md5 for more safety flashing
Like i wrote before..
Before this happen the phone always do restart it self
I hope there is any progress for prevent and fix this issue
The user that have this problem, now must go to Samsung to fix it before we know how to fix it
Regards
I'd like to say this sudden restart happen to me quite often while in stock rom, but after I flash custom rom this phenomenon never happen again. This phenomena only happen while I'm on stock rom.
Sent from my GT-I8150 using XDA App
Update for this..
My friend reported..
For my country, we get FULL WARRANTY for this case
and waiting this status until fixed about 2 days
For the first phase they do regular Flashing with STOCK ROM based on country
then it still cannot on (we know already -_-)
We didn't sure yet is the phone will be change with the new one or not because this had implication from hardware issue..
Come back latter..
Rio Saputro said:
Update for this..
My friend reported..
For my country, we get FULL WARRANTY for this case
and waiting this status until fixed about 2 days
For the first phase they do regular Flashing with STOCK ROM based on country
then it still cannot on (we know already -_-)
We didn't sure yet is the phone will be change with the new one or not because this had implication from hardware issue..
Come back latter..
Click to expand...
Click to collapse
same problem with my devices , after flash cwm and use GingerIce Rom my device cant boot again.
im tried Oneclick Unbrick : http://forum.xda-developers.com/showthread.php?p=15330252#post15330252
but still problem
flowish said:
same problem with my devices , after flash cwm and use GingerIce Rom my device cant boot again.
im tried Oneclick Unbrick : http://forum.xda-developers.com/showthread.php?p=15330252#post15330252
but still problem
Click to expand...
Click to collapse
Hi Bro...
We don't know yet how to fix it.
Update for this,
Samsung do spare part / hardware changes for this case. It probably cause not only by flashing but hardware also
BTW now i have 1 Wonder and 1 Wonder at Samsung center (i mean both are my friend phone ). ETA for fixing this is 3 days
And my friend want me to re write black notes chapter 3
It will come next week
Come back latter
Rio Saputro said:
Hi Bro...
We don't know yet how to fix it.
Update for this,
Samsung do spare part / hardware changes for this case. It probably cause not only by flashing but hardware also
BTW now i have 1 Wonder and 1 Wonder at Samsung center (i mean both are my friend phone ). ETA for fixing this is 3 days
And my friend want me to re write black notes chapter 3
It will come next week
Come back latter
Click to expand...
Click to collapse
yeah , my wonder goto SSC now
Update for this,
Finally SGW come out from hospital
The problem cause not from FLASHING but from HARDWARE
Samsung must change the MAINBOARD for this problem
If this problem happened to you
Don't blame yourself or the Developers
Don't try to fix or figure this out by your self
Go to Samsung to Fix it
Regards
Rio Saputro said:
Update for this,
Finally SGW come out from hospital
The problem cause not from FLASHING but from HARDWARE
Samsung must change the MAINBOARD for this problem
If this problem happened to you
Don't blame yourself or the Developers
Don't try to fix or figure this out by your self
Go to Samsung to Fix it
Regards
Click to expand...
Click to collapse
They change your Mainboard???
No questions?????
Very good result Rio!!!!
Is there a thread outlining what the symptoms of this particular Boot loop problem are.....
Maybe this post in this thread.....from THE-E....
http://forum.xda-developers.com/showthread.php?p=22744322
it should be stickied!!!!!
How to do that here, who request to???
Not enough stuff getting stickied here, peeps have to trawl thro' full forum to find answers to sometimes repeated questions??
But important stuff certainly should be "stickied".
Anyone else agree....and how to get a result on this???
Sent from my GT-I8150 on Lanzarote Canary Vacation using Tapatalk
irishpancake said:
They change your Mainboard???
No questions?????
Very good result Rio!!!!
Is there a thread outlining what the symptoms of this particular Boot loop problem are.....
Maybe this post in this thread.....from THE-E....
http://forum.xda-developers.com/showthread.php?p=22744322
it should be stickied!!!!!
How to do that here, who request to???
Not enough stuff getting stickied here, peeps have to trawl thro' full forum to find answers to sometimes repeated questions??
But important stuff certainly should be "stickied".
Anyone else agree....and how to get a result on this???
Sent from my GT-I8150 on Lanzarote Canary Vacation using Tapatalk
Click to expand...
Click to collapse
This thread and The-E thread must be stick because now the problem occur much often...
So we can inform the others Galaxy W users
Regards
thanks for your update... which mean Im having same problem too here... need to send this phone to SSC... Huh! (
same problem here, my friend sgw had bootloop from unknown reason, have try flashing with ASIA firmware but have no result (before i read this thread) thanks for op, this must be sticky..
will go to ssc now :hammer
same problem as well
stuck at samsung logo and just keep reboot reboot and reboot
already bring to SSC few days ago they say will change board
now just waiting the phone to be back
Guys, i bought one Wonder from eBay and its with thos problem now.. any change of fixing it without going to samsung assistance?
gajodafeira said:
Guys, i bought one Wonder from eBay and its with thos problem now.. any change of fixing it without going to samsung assistance?
Click to expand...
Click to collapse
A little late in reading this post but I also bought my Galaxy W from Ebay. Samsung user agreement states that the phone is guaranteed for 2 years after the date of sale and the agreement is transferable between owners. In other words it doesn't matter who originally bought it but is guaranteed for 2 years and our phone is still less than 2 years old. I know this as had to send mine back and they accepted it.
Hi guys,
I am using a Sony Ericsson Xperia Arc and am having a lot of trouble with the device constantly crashing and rebooting.
when this first happened these are the steps i took.
i completely wiped the device (factory reset, wipe dalvik cache, wipe cache partition, format system)
i then flashed Baseband 77 using flashtool
i then flashed fxp149 using flashtool
i then flashed Baseband 77 libs using CWM
i then flashed AOKP JB M1-R1 ROM using CWM
i then flashed gapps using CWM
i the reloaded all apps from the market and not applied any backups and yet it still rebooted all the time.
Since then i have tried using
Fusion 3.8
Fusion 3.9
Fusion 4.0
FXP 148
FXP 150
Stock Kernel inside ROM .zip file.
I have also tried putting it back to Baseband 72 but it made no difference.
None of these make any difference to my issue and yet before i had the issue, I had used all of these kernels except FXP 150 and they all worked fine with no issues at all.
I then decided to go all the way back to stock firmware as it is out of the box.
so I used flashtool and flashed LT18i_4.1.B.0.587_(1254-2716).ftf
I reloaded my applications and monitored the device only to see that by the next day, the problem had returned.
I am now at the end of my tether and do not know what else i can possibly do to figure out the issue.
the device has not been dropped or damaged in any way so there is no reason for a hardware fault.
i desperately NEED this device to be working as i use it on a daily basis for my business and cannot live with out it.
IF THERE IS ANYONE OUT THERE THAT COULD PLEASE PLEASE PLEASE HELP I WOULD BE FOREVER IN YOUR DEBT!!!!!!!
i also have a logcat that i was running in the background when one of the reboots happened
not sure if that can tell anyone anything but i have it if it does
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
XperienceD said:
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
Click to expand...
Click to collapse
thanks for the suggestion but my battery is not loose and i have tried your method but with the same results.
weaselmetal said:
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Click to expand...
Click to collapse
hmmm i thought if that were the case there would be others experiencing it too.
i will take your idea and post results.
thank you very much
rod555 said:
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
Click to expand...
Click to collapse
i tried this, unfortunately i had the same issues occurring.
thank you for your suggestion
Needs a trip to the Service Centre then by the sounds of it.
XperienceD said:
Needs a trip to the Service Centre then by the sounds of it.
Click to expand...
Click to collapse
yes i am starting to think that may be my next move
will i have an issue with getting it repaired since i have unlocked my bootloader, flashed different kernels and roms and rooted the device?
if so, is there any way i can get it back to official "out of the box" state?
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
tangosierra_ said:
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
Click to expand...
Click to collapse
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
plastic_prophet said:
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
Click to expand...
Click to collapse
Here:- http://forum.xda-developers.com/showthread.php?t=1324703
Sent from my LT15i using xda premium
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
plastic_prophet said:
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
Click to expand...
Click to collapse
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
lalek said:
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
Click to expand...
Click to collapse
if you open a terminal session and type:
su
cd sdcard
logcat >> logcat.txt
it will create a .txt file and put the live logcat info into it.
you need to leave the terminal running in the background to make sure it continues to update
then when you see a reboot just get the logcat.txt file from the sd card and open it in wordpad or something. (notepad doesnt display properly)
have a look at the last thing that happened before the reboot and see what it tells you
mine had info about wifi scanning and showed that it had seen ssids
next step was to turn wifi off to see if the problem stayed or resolved.
good luck!! id love to hear how it goes
Q&A for [KERNEL][SHIFT][DUALBOOT][TW/CM]10/27/14[LINARO]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][SHIFT][DUALBOOT][TW/CM]10/27/14[LINARO]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Shift Kernel on DN3 v5 for N7105
First off, thank you for all your hard work on this kernel. Your work is greatly appreciated. I am currently running DN3 v5.2 rom for N7105 on Galaxy Note II SGH-T889 for T-moblile. I love the rom with one exception which is charging the phone when turned off cause phone to boot. Additionally, if your battery dies you can't even boot up to charge and have to pull battery and charge separately until you have enough juice to reboot and insert back into. After some research on the forums it brought me to your Shift kernel. I flashed Shift Kernel 3.1 by wiping cache and wiping dalvik to no avail. I not intending to use this kernel for dual boot only as my daily driver is DN3.
The good news is the phone does charge when turned off the bad news is the Rom either locks or reboots after 30 seconds or so. It seems very close to working as I can open a few apps prior to lock up or reboot. Is there something I'm doing wrong? Should I be reflashing the rom over Shift 3.1? If so, how should I reflach (wipe cache wipe dalvik) or something else? Finally, is there something with SuperUser that may be causing the problem?
I hope you can get this working on DN3 as this is the only thing lacking as even wi-fi calling can be bypassed using Hangouts. Again many thanks for your work.
Xxp1 said:
First off, thank you for all your hard work on this kernel. Your work is greatly appreciated. I am currently running DN3 v5.2 rom for N7105 on Galaxy Note II SGH-T889 for T-moblile. I love the rom with one exception which is charging the phone when turned off cause phone to boot. Additionally, if your battery dies you can't even boot up to charge and have to pull battery and charge separately until you have enough juice to reboot and insert back into. After some research on the forums it brought me to your Shift kernel. I flashed Shift Kernel 3.1 by wiping cache and wiping dalvik to no avail. I not intending to use this kernel for dual boot only as my daily driver is DN3.
The good news is the phone does charge when turned off the bad news is the Rom either locks or reboots after 30 seconds or so. It seems very close to working as I can open a few apps prior to lock up or reboot. Is there something I'm doing wrong? Should I be reflashing the rom over Shift 3.1? If so, how should I reflach (wipe cache wipe dalvik) or something else? Finally, is there something with SuperUser that may be causing the problem?
I hope you can get this working on DN3 as this is the only thing lacking as even wi-fi calling can be bypassed using Hangouts. Again many thanks for your work.
Click to expand...
Click to collapse
If you could get me a log WHILE this is happening it would be the fastest way to determine the issue. Adb is enabled as soon as it can me in the kernel so just flash, plug in to USB and in terminal command run "adb logcat log.txt" without the quotes and upload the output file. Something in the kernel or rom is activating at that same time I'm hoping
Sent from my SGH-I317 using XDA Premium 4 mobile app
rogersb11 said:
If you could get me a log WHILE this is happening it would be the fastest way to determine the issue. Adb is enabled as soon as it can me in the kernel so just flash, plug in to USB and in terminal command run "adb logcat log.txt" without the quotes and upload the output file. Something in the kernel or rom is activating at that same time I'm hoping
Sent from my SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Dear Sir @rogersb11! Please help me.:crying:
i'm using Note 2 LTE Korea E250S and i wish to use CM12 your build, i try flash it with gapps and this kernel asosp for e250S. But thread support for it deaded) => it doesn't boot. Flashes stuck on logo galaxy note 2 and not boot forever in here, i too try shift-lollipop but it too not boot. Sir, please helpful for me, can you convert this kernel (update-0.30-aosp-KO-LTE-e250s-r3p2-n7100.zip) port to use flash rom cm12 build by you. thank sir so much. i'm waiting sir here. thank again.
i'm new member on xda, and i alraedy follow thread by you and send mail for sir, i wish sir can help for me. thank sir and thank again. sorry my english very bad, sorry sir.
confirm this thing : kernel Shift-Lollipop can fixed issues baseband unknow.
Can you add the support for Xprivacy?We had to use this app to able the google location reporting in China,unfortunately it required to edit the kernel about ramdisk.
thx a lot
t1h5ta3 said:
the reason you get those errors is from backing up and restoring sys data on a rom with diferent framework.
solution: only backup/restore apps/data
Click to expand...
Click to collapse
You know what needs added?
Stuck on Samsung logo
So, as a back story; i recently flashed back to 20140604-Mawrick26-N7105NEEFND3-S5Themed V3 after having CM12 on my N7105, i then rooted it and flashed Philz CWM recovery
Then i flashed 6.58.9 DUAL BOOT PhilZ Touch Advanced, because i wanted a dual boot of a original sammy rom and CM12, i followed the instuctions from the link;
http://forum.xda-developers.com/galaxy-note-2/development-n7105/kernel-08-15-14-t2849082
i had my battery at 100% and selected ''Create system.img'', and i waited over night for it to finish, when i woke up it was still at it, i expected it had crashed so i long pressed the power button and now it wont boot into the stock sammy rom, i cant even go into recovery or download mode, and ofc odin doesnt detect it when its stuck on the samsung logo, any idea's on how to fix it? even if it means going back to a stock sammy rom with knox, ill get past that again
Nemesis Note 4 ver3.3 rom (which requires to flash agni kernel as well to work)
hi...can i use this with Nemesis Note 4 ver3.3 rom (which requires to flash agni kernel as well to work) and i want to use blisspop as secondary rom...please explain how to do it...right now i am in recovery and i dont have any rom installed yet...please guide me
No audio on calls…
Noob here.
Hello, Im facing no audio on calls with v5.5 on a cyanogenmod 12.1 10 july 2015. t0lte Nightly.
Is there a way to fix that?
Cheers.
Hello, Good Day to all! I wont take too much of your time but please help me!
My Oneplus 3 suddenly bricked itself, I dont know how or why but it just powered off and then when I tried to boot it up it was hard bricked. Now I've managed to fix it by following the Mega Unbrick guide for Oneplus 3 and it boots up, but the problem is it crashes during boot, and it randomly crashes after a few minutes which then leads to the boot logo crash, I have to "let it rest" so to speak for a few minutes so that it would bypass the boot crashes. Once it got past the crashes some apps are not responding like Twitter, Messenger and so on. Stock apps are fine it's the newly downloaded ones that are not responding, I tried numerous factory resets using the stock recovery and TWRP but no luck.
I am on Nougat 7.1.1 on the latest OxygenOS version, Unlocked bootloader with systemless root. I haven't tried flashing a custom rom the only thing I tried to flash was the Stock Rom. I also noticed that the WiFi and the Data/Signal was particularly weaker since the messages would not load, I need to actually check the app for it to sync. When I got Messenger somehow working, the messages would not even load up.
Any ideas what the problem is? Any help is deeply appreciated, Thanks in Advance!
Hi.. Good Day
This may be a motherboard issue why don't u give ur phone to service center to get it checked up once
RiskTaker10 said:
Hello, Good Day to all! I wont take too much of your time but please help me!
My Oneplus 3 suddenly bricked itself, I dont know how or why but it just powered off and then when I tried to boot it up it was hard bricked. Now I've managed to fix it by following the Mega Unbrick guide for Oneplus 3 and it boots up, but the problem is it crashes during boot, and it randomly crashes after a few minutes which then leads to the boot logo crash, I have to "let it rest" so to speak for a few minutes so that it would bypass the boot crashes. Once it got past the crashes some apps are not responding like Twitter, Messenger and so on. Stock apps are fine it's the newly downloaded ones that are not responding, I tried numerous factory resets using the stock recovery and TWRP but no luck.
I am on Nougat 7.1.1 on the latest OxygenOS version, Unlocked bootloader with systemless root. I haven't tried flashing a custom rom the only thing I tried to flash was the Stock Rom. I also noticed that the WiFi and the Data/Signal was particularly weaker since the messages would not load, I need to actually check the app for it to sync. When I got Messenger somehow working, the messages would not even load up.
Any ideas what the problem is? Any help is deeply appreciated, Thanks in Advance!
Click to expand...
Click to collapse
This sounds like an hardware issue, have you tried method 2 of the unbrick tool, perhaps you could try to re-download it, have you unzipped it? If it boots let it boot and then upgrade to a new OOS version and then you can do whatever you want. If it doesn't work after you followed my suggestions you might wanna contact Oneplus, don't worry even though your bootloader is unlocked you still have full warranty..
Puddi_Puddin said:
This sounds like an hardware issue, have you tried method 2 of the unbrick tool, perhaps you could try to re-download it, have you unzipped it? If it boots let it boot and then upgrade to a new OOS version and then you can do whatever you want. If it doesn't work after you followed my suggestions you might wanna contact Oneplus, don't worry even though your bootloader is unlocked you still have full warranty..
Click to expand...
Click to collapse
I did the method 2 of the unbrick tool, I've done it like twice or thrice now. I have the latest version of OOS, I am afraid to flash a custom rom because after it flashes in TWRP it immediately crashes, it does not even give me a chance to clear the dalvik or reboot. It crashes no reboot or anything.
But thank you I didn't expect anyone would reply well I regained my faith in humanity in forums
Sidenote: What custom rom would you suggest? or is the stock rom better?
RiskTaker10 said:
I did the method 2 of the unbrick tool, I've done it like twice or thrice now. I have the latest version of OOS, I am afraid to flash a custom rom because after it flashes in TWRP it immediately crashes, it does not even give me a chance to clear the dalvik or reboot. It crashes no reboot or anything.
But thank you I didn't expect anyone would reply well I regained my faith in humanity in forums
Sidenote: What custom rom would you suggest? or is the stock rom better?
Click to expand...
Click to collapse
I would suggest VertexOS. It's simple and really fast, EAS and Voxpopuli takes peformance per watt to the next level, if you like feature you might try Zenixx RR.
hrishikeshgramani said:
Hi.. Good Day
This may be a motherboard issue why don't u give ur phone to service center to get it checked up once
Click to expand...
Click to collapse
Unfortunately that is out of the question, there is no Service Center for Oneplus where I live so I cant get it checked ASAP
Puddi_Puddin said:
I would suggest VertexOS. It's simple and really fast, EAS and Voxpopuli takes peformance per watt to the next level, if you like feature you might try Zenixx RR.
Click to expand...
Click to collapse
Thanks for the suggestion! Should I YOLO and flash a custom rom even though my phone is like this?
RiskTaker10 said:
Thanks for the suggestion! Should I YOLO and flash a custom rom even though my phone is like this?
Click to expand...
Click to collapse
You can always try..
Puddi_Puddin said:
You can always try..
Click to expand...
Click to collapse
Okay thanks good citizen of XDA I'll try to flash a custom rom and I'll try to report back here ASAP
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
the_mentor said:
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
Click to expand...
Click to collapse
Take a backup of your personal files and then wipe system, data, internal storage and both caches. Then flash OOS 5.0.8 and without adding any apps, check the calling function. If it still happens, then most likely a hardware issue.
tnsmani said:
Take a backup of your personal files and then wipe system, data, internal storage and both caches. Then flash OOS 5.0.8 and without adding any apps, check the calling function. If it still happens, then most likely a hardware issue.
Click to expand...
Click to collapse
If it's a hardware problem which part should I replace?
I already ordered a battery before this issue started and I was planning on replacing it once it gets here maybe I can replace one of the parts in order to resolve this issue
the_mentor said:
If it's a hardware problem which part should I replace?
I already ordered a battery before this issue started and I was planning on replacing it once it gets here maybe I can replace one of the parts in order to resolve this issue
Click to expand...
Click to collapse
You will need to replace the main board if the issue persist.
Same problem here
Hello mate, I've got the exact same problem with my wife's OP3. What did you do eventually? Did you find out? Please help. Thanks
New geek said:
Hello mate, I've got the exact same problem with my wife's OP3. What did you do eventually? Did you find out? Please help. Thanks
Click to expand...
Click to collapse
Hmmm quite strange that you're having the same issue.
I didnt find a solution yet i gave her a temp replace phone that we had in a drawer somewhere.
Did your wife do anything out of the ordinary when it happened? are you having the same issue that LOS works but stock rom shows factory reset?
thanks.
-DM.
the_mentor said:
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
Click to expand...
Click to collapse
try using msm v3.0 tool fixes most problems not hardware though
the_mentor said:
Hmmm quite strange that you're having the same issue.
I didnt find a solution yet i gave her a temp replace phone that we had in a drawer somewhere.
Did your wife do anything out of the ordinary when it happened? are you having the same issue that LOS works but stock rom shows factory reset?
thanks.
-DM.
Click to expand...
Click to collapse
No, She did not do anything out of the ordinary. But weirdly I have exactly the same things happening. Lineage works but no sound. Everything else factory resets. I have tried quite a few ROM'swithout any luck. So far the only ROM which worked for some time(1day) was 6.0.1 . I have spent quite a long time on this flashing various ROM and dont know what to do now.
New geek said:
No, She did not do anything out of the ordinary. But weirdly I have exactly the same things happening. Lineage works but no sound. Everything else factory resets. I have tried quite a few ROM'swithout any luck. So far the only ROM which worked for some time(1day) was 6.0.1 . I have spent quite a long time on this flashing various ROM and dont know what to do now.
Click to expand...
Click to collapse
Update: @ireaper4592 might have a point here. I have gone one level up and I tried msm v3.0 tool, thus doing a complete reinstall including firmware. The factory resetting stopped but the sound was not working (I thought that it could be the ROM and the security patches). So I updated to the latest ROM available from Oneplus and evrything has been working since. I did this last night so not sure how long this is going to stay like that. I will give it some time and update later. Wife is using it now!
what you will need to do is download the oneplus 3 recovery tool and put the phone into qualcolm mode and restore the phone that way. here is a link https://www.androidexplained.com/oneplus-3-unbrick-return-stock/
New geek said:
Update: @ireaper4592 might have a point here. I have gone one level up and I tried msm v3.0 tool, thus doing a complete reinstall including firmware. The factory resetting stopped but the sound was not working (I thought that it could be the ROM and the security patches). So I updated to the latest ROM available from Oneplus and evrything has been working since. I did this last night so not sure how long this is going to stay like that. I will give it some time and update later. Wife is using it now!
Click to expand...
Click to collapse
its really good to know.
did you have to wipe the internal storage for this process to work ?
Do you have a guide that you've used to get this working?
Thanks in advanced.
-DM
the_mentor said:
its really good to know.
did you have to wipe the internal storage for this process to work ?
Do you have a guide that you've used to get this working?
Thanks in advanced.
-DM
Click to expand...
Click to collapse
That tool/procedure will reset your phone. So you will lose everything on the phone. Take a backup beforehand.
The link posted in the post above yours contains the guide as well as the tools. It also has links to the original guide here on XDA.
tnsmani said:
That tool/procedure will reset your phone. So you will lose everything on the phone. Take a backup beforehand.
The link posted in the post above yours contains the guide as well as the tools. It also has links to the original guide here on XDA.
Click to expand...
Click to collapse
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
the_mentor said:
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
Click to expand...
Click to collapse
Please share the guide as I am also suffering with same problem.
Still not working
the_mentor said:
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
Click to expand...
Click to collapse
I was about to update here with good news but wife's phone went back to restart loop the next day. I am not sure but probably triggered by her installing whatsapp and facebook. I put the phone away because I have already spend quite a lot of time behind this. Is your's still going? Please list the step by step procedure. Thanks
download from here https://mega.nz/#!zsdnkCDA!UyJRwbJK6kHTDpmesBYao0knaOTwbgu4dSiokV1XLYU then turn off phone run tool,connect phone with volume up pressed,should have a com in the list if so just click start thats it and wait for it to turn green or device restart