Related
Complete newb here, i haven't done any development work or even tried rooting or flashing my phone. Over the last couple of days, apps have started crashing as soon as i open them, and then yesterday i rebooted the device and it won't go past the Motorola logo. I've searched through a few threads and there isn't a simple enough answer or procedure to follow to get this working. Also most similar issues have USB debugging on etc, whereas i have no developer settings on at all. Any help would be greatly appreciated
You didn't search enough for an answer i see. But okey for the lazy i will help you, no offense
Can u access (AP)fastboot and can u boot into recovery from fastboot? Have a look at the link in my signature on how to get in fastboot and then in recovery.
Hazou said:
You didn't search enough for an answer i see. But okey for the lazy i will help you, no offense
Can u access (AP)fastboot and can u boot into recovery from fastboot? Have a look at the link in my signature on how to get in fastboot and then in recovery.
Click to expand...
Click to collapse
Literally my first post mate, how about you cut me some slack. I spent about 4/5 hours searching last night and even took the phone apart. If there is an answer please point me in the direction of it. There are countless threads where the issue is the user has loaded their own ROM or flashed the device already or something like that, which caused the system files to become corrupted. But as i mentioned i have done nothing to the device except for a data wipe a few months back, and there doesn't seem to be any threads where this just happened out of nowhere. I have booted into fastboot, recovery and done the partition cache & data wipe and rebooted, that was my first step.
merculesblud said:
Literally my first post mate, how about you cut me some slack. I spent about 4/5 hours searching last night and even took the phone apart. If there is an answer please point me in the direction of it. There are countless threads where the issue is the user has loaded their own ROM or flashed the device already or something like that, which caused the system files to become corrupted. But as i mentioned i have done nothing to the device except for a data wipe a few months back, and there doesn't seem to be any threads where this just happened out of nowhere. I have booted into fastboot, recovery and done the partition cache & data wipe and rebooted, that was my first step.
Click to expand...
Click to collapse
Hoho, okey, my words have offended you and I am sorry for that.
I can't simply give u an answer if you only said that it doesn't boot and u looked for something to fix it. There are many fixes for many sorts of problems. Also if I knew u have tried to wipe the cache and data I would give u a totally different answer. But u had not mentioned anything about what u had done to try to fix it.
For now, if even a data/factory reset from recovery didn't work I suggest u need to try to reflash the whole stock firmware. See in my signature the link to an index thread about the phone. U can find there the ways to reflash to your stock firmware and hopefully fix your issue.
If u need some more help to flash stock firmware, don't hesitate to ask here.
Hazou
Verstuurd van mijn GT-P5110
Hazou said:
Hoho, okey, my words have offended you and I am sorry for that.
I can't simply give u an answer if you only said that it doesn't boot and u looked for something to fix it. There are many fixes for many sorts of problems. Also if I knew u have tried to wipe the cache and data I would give u a totally different answer. But u had not mentioned anything about what u had done to try to fix it.
For now, if even a data/factory reset from recovery didn't work I suggest u need to try to reflash the whole stock firmware. See in my signature the link to an index thread about the phone. U can find there the ways to reflash to your stock firmware and hopefully fix your issue.
If u need some more help to flash stock firmware, don't hesitate to ask here.
Hazou
Verstuurd van mijn GT-P5110
Click to expand...
Click to collapse
Cheers mate, i'll give it a go, but i've never done anything like flashing before. I'll see how i get on
merculesblud said:
Cheers mate, i'll give it a go, but i've never done anything like flashing before. I'll see how i get on
Click to expand...
Click to collapse
As long as u read everything carefully u will be good to go. Just one reminder, use the latest stock firmware JB(or u can get more problems). And rsd-lite 6.1.x
Verstuurd van mijn GT-P5110
Hazou said:
As long as u read everything carefully u will be good to go. Just one reminder, use the latest stock firmware JB(or u can get more problems). And rsd-lite 6.1.x
Verstuurd van mijn GT-P5110
Click to expand...
Click to collapse
So, this is all brand new to me. I'm using this guide http://forum.xda-developers.com/showthread.php?t=1974568
The firmware is from here - http://sbf.droid-developers.org/phone.php?device=13
- I chose the 4.1.2 UK Retail as i purchased the phone through Virgin Mobile (UK)
Drivers and RSD 6.1.6 are now installed so will try now
Is everything right so far?
Seems to have worked, but it seems a bit different and some apps like hangouts are unavailable now, even though i had them before. The firmware i chose was UK Retail, however i am not 100% that this is the one to use as i bought it through Virgin Mobile (UK).
Hangouts should work just fine. Strange.
But nice that all works fine now
Sent from my XT890 using XDA Free mobile app
After a restart, my moto razr i is stuck on Android is upgrading...
Hazou said:
Hangouts should work just fine. Strange.
But nice that all works fine now
Sent from my XT890 using XDA Free mobile app
Click to expand...
Click to collapse
Hi, I saw above post and happy to read that your problem is solved so I writting with my problem on your post, just getting hope that mine will work too.
Actually I have also ''NIL'' knowledge about all this software/ quote language etc
My issue is; my Moto Razr i is just stuck on '' Android is upgrading '' than shows ''Starting Apps'' thn nothing happen n same things repeats ... couple of hours back it was saying ''finishing boot'' also but now it is just giving this error '' Android is upgrading '' than shows ''Starting Apps'' thn nothing happen n same things repeats
Please I want to request if you are about to guide anything in tough language please consider that I am completely unknown to all the setups and stuff... just if you can help sharing step by step process and also post specific link/software to download (if needed) and how to download and other details in simple guidance plz plz plz.
One more point I tried to chat with Motorola chat service and they suggested me to power off it first but i m pressing vol- and vol + and power button but phone is quickly restarting on its own... i m even unable to go on boot as they suggested me to do so.
Thanks a lot to ''my upcoming angel'' in advance
Hope one can help me at earliest.
opened new thread
Hazou said:
Hangouts should work just fine. Strange.
But nice that all works fine now
Sent from my XT890 using XDA Free mobile app
Click to expand...
Click to collapse
Im having the same issue described on this thread.
My phone doesnt start, it stays at the logo screen. I've tried to recover, factory reset and nothing worked. I have access to the (AP)fastboot screen.
Later then i saw this thread, i've did everything as described at your tutorial, tried all the versions of the RSD Lite (6.1.4, 6.1.5, 6.1.6), it cant detect my phone.
I've tried in two different PCs, tons of different USB ports, running as administrator, compatibility mode...the PC tells me that the USB is connected, but the RSD Lite doesnt recognise it.
I've tried using these two options of motorola drivers:
- motohelper_2.1.40_driver_5.5.0.exe (that i found at your post)
- MotorolaDeviceManager_2.4.5.exe (found another similar tutorial on the internet)
Am i missing something?
I would really appreciate any help.
Thanks!
Mootl3y said:
Am i missing something?
Click to expand...
Click to collapse
did you boot first into Fastboot-mode before you connect to pc?
1. Install Driver + RSD Lite
2. Boot into fastboot + connect USB
3. Start RSD Lite
5m00v3 said:
did you boot first into Fastboot-mode before you connect to pc?
1. Install Driver + RSD Lite
2. Boot into fastboot + connect USB
3. Start RSD Lite
Click to expand...
Click to collapse
Yep. Thats exactly what i did.
I tried only using Windows 8.1. Is it compatible?
I will test on a win7 PC later.
UPDATE:
Worked RSD Lite on Win7, it found my phone. I belive RSD Lite doesnt work on Win 8.1 (at least on my PC and notebook).
I believe my firmware version is this one:
Android 4.1.2 Blur_Version.982.50.29002.XT890.Vivo.en.BR Vivo Brasil 537.6 MiB
Can i use the Retail version without problems? (this one: Android 4.1.2 Blur_Version.982.50.29.XT890.Brasil.en.BR Retail Brasil 532.8 MiB)
Thanks!
Finally got my phone working again!
I got it running RSD Lite 6.1.6 on Win 7 and used the same Firmware version that i had (in my case: Android 4.1.2 Blur_Version.982.50.29002.XT890.Vivo.en.BR Vivo Brasil 537.6 MiB), not the Retail one.
Also used the MotorolaDeviceManager_2.4.5.exe that i got from Motorola website.
My phone now is up and running like charm, no apps or configs lost, everything seems perfect (and also a little bit faster). Not sure what caused my issue, did nothing but normal use.
I hope everyone with the same problem can find this easy solution and follow the right steps (and maybe avoid Win8 to do the process).
Thank you guys for all the information :good:!
Good it is solved. It can happen to anyone. Just a small coruption or miss configuration can take out the android system. Luckily this almost never happens and u were just unfortunate.
Sent from my XT890 using XDA Free mobile app
Hello,
A couple of days ago, i received a call and my phone just turned off. Since then, it just get stuck in the M powered by android logo. My phone is not rooted and nothing is modified since i acquired it.
I tried to reset the phone with a hard reset or reseting it to factory or recovery from bootloader, but it did not fix anything, so the last try i was doing was restoring the Stock ROM, following the steps in the following thread: https://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657/
The problem I have found is that I have tried 3 different roms for XT1068 4.4.4
RETAILDSDSALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC_SVC.xml
RETAILDSDSALL_XT1068_4.4.4_KXB21.85-23_cid7_CFC.xml
RETAILDSDSALL_XT1068_4.4.4_KXB21.85-27_cid7_CFC_SVC.xml
but I have received the same error message from all of them: "invalid PIV signed system image"
could anybody try to help me with this issue? i think i am not too far to solve and fix the phone, but i dont know what else i can try.
Thank you very much in advance.
yukovski said:
Hello,
A couple of days ago, i received a call and my phone just turned off. Since then, it just get stuck in the M powered by android logo. My phone is not rooted and nothing is modified since i acquired it.
I tried to reset the phone with a hard reset or reseting it to factory or recovery from bootloader, but it did not fix anything, so the last try i was doing was restoring the Stock ROM, following the steps in the following thread: https://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657/
The problem I have found is that I have tried 3 different roms for XT1068 4.4.4
RETAILDSDSALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC_SVC.xml
RETAILDSDSALL_XT1068_4.4.4_KXB21.85-23_cid7_CFC.xml
RETAILDSDSALL_XT1068_4.4.4_KXB21.85-27_cid7_CFC_SVC.xml
but I have received the same error message from all of them: "invalid PIV signed system image"
could anybody try to help me with this issue? i think i am not too far to solve and fix the phone, but i dont know what else i can try.
Thank you very much in advance.
Click to expand...
Click to collapse
What was the last OS you were using??
avrockz11 said:
What was the last OS you were using??
Click to expand...
Click to collapse
I think it was 6.0 but, is it relevant? I mean, I understood that the important data is the one that was in the phone from factory, in this case the 4.4.4
yukovski said:
I think it was 6.0 but, is it relevant? I mean, I understood that the important data is the one that was in the phone from factory, in this case the 4.4.4
Click to expand...
Click to collapse
With OTA update to Marshmallow, your bootloader too was upgraded..therefore you can't flash the KitKat version again without risking a hard brick..so try flashing a MM build.
To restore to MM,follow this thread
https://forum.xda-developers.com/moto-g-2014/general/official-firmware-titan-xt1068-t3312933
Hello!
Just today I bought myself a second-hand Oneplus 3T that had issues booting into the system. The start of the boot animation would show, but after that the screen just goes black and a white notification light turns on. Confident in my basic skills, I bought it and started trying things.
It boots into recovery and fastboot, all nicely, so first I tried wiping everything with stock recovery and then installing OOS that I downloaded from oneplus. Installed it through the stock recovery ADB Sideload, didn't change a thing. So since the bootloader is locked and cannot be opened, I went on to tryin the Qualcomm 9008 unbrick. Went through with it got a green text in MsmDownloadTool and all, but still nothing. Tried to install that same OOS on this "fixed boot partition" but the only change I noticed that I couldn't even get the start of the boot animation. Just the oneplus logo splash screen and black with white light after that....
If the device is powered down it shows the offline charging screen and a green notification light.
The device is out of warranty, I need the help of you people.... I might try installing twrp and formatting the system partition and installing on that, that is if I can get twrp installed in this kind of a situation.. Thanks!!
EDIT; Tried installing twrp, of course cannot flash it through fastboot but I also tried tricking MsmDownloadTool to install twrp instead of stock to no avail. I got the boot animation starting back but nothing else, also clicking "Install from internal storage" in recovery does absolutely nothing, doesn't bring up a file explorer like I would have expected..
Have you tried the Qualcomm MSMtoool to completely reinstall OOS? That may work. Don't try to install TWRP through the MSM tool.
This is an usual brick that takes place when someone has tried to relock the bootloader when a ROM/Recovery has been flashed which is not signed by OnePlus. It has been solved many times, so please do a search on XDA and OP Forums before posting a new question.
thes3usa said:
Have you tried the Qualcomm MSMtoool to completely reinstall OOS? That may work. Don't try to install TWRP through the MSM tool.
This is an usual brick that takes place when someone has tried to relock the bootloader when a ROM/Recovery has been flashed which is not signed by OnePlus. It has been solved many times, so please do a search on XDA and OP Forums before posting a new question.
Click to expand...
Click to collapse
Man I searched for this kind of brick for a few hours, only found a couple, one on xda and another on oneplus forums, and those didn't get solved. The MSM tool package I'm using does write the system.img so I guess it at least tries to install OOS.... Could you point me in the direction of similar brick situations? This doesn't get fixed by wiping any partitions..
Thanks!
MrMatson said:
Man I searched for this kind of brick for a few hours, only found a couple, one on xda and another on oneplus forums, and those didn't get solved. The MSM tool package I'm using does write the system.img so I guess it at least tries to install OOS.... Could you point me in the direction of similar brick situations? This doesn't get fixed by wiping any partitions..
Thanks!
Click to expand...
Click to collapse
I'm guessing you used this guide (https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) and you did install the drivers correctly yeah?
What error do you get when you MSM tool tries to flash the images? Is it the Sahara error?
Try another computer, or switch USB ports. Also try to download the firmware packages by yourself, and select it from the MSM tool. Also try to let the in-program download flash.
Try going into Fastboot and erase everything, from Internal Storage to the System partition, and then re-try the MSM tool.
thes3usa said:
I'm guessing you used this guide (https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) and you did install the drivers correctly yeah?
What error do you get when you MSM tool tries to flash the images? Is it the Sahara error?
Try another computer, or switch USB ports. Also try to download the firmware packages by yourself, and select it from the MSM tool. Also try to let the in-program download flash.
Try going into Fastboot and erase everything, from Internal Storage to the System partition, and then re-try the MSM tool.
Click to expand...
Click to collapse
Bootloader is locked, nothing can be done through fastboot. I get no errors in MSM, it's just this white light brick when booting to the system. I found a third guy on page 46 of that thread (that's a bit of reading) who had a similar sounding issue. He got it fixed by using a newer MSM version I believe. I am currently downloading the one he said he used. So far I've tried 2 diffrerent MSM packages so far. One other guy in that thread said that the white light should mean a kernel panic... I really hope I can get it working
How can I choose what firmware MSM installs? Or is that even what you mean by "download the firmware packages by yourself, and select ir from the MSM tool"?
I appreciate your help. This really is a frustrating kind of error.
MrMatson said:
Bootloader is locked, nothing can be done through fastboot. I get no errors in MSM, it's just this white light brick when booting to the system. I found a third guy on page 46 of that thread (that's a bit of reading) who had a similar sounding issue. He got it fixed by using a newer MSM version I believe. I am currently downloading the one he said he used. So far I've tried 2 diffrerent MSM packages so far. One other guy in that thread said that the white light should mean a kernel panic... I really hope I can get it working
How can I choose what firmware MSM installs? Or is that even what you mean by "download the firmware packages by yourself, and select ir from the MSM tool"?
I appreciate your help. This really is a frustrating kind of error.
Click to expand...
Click to collapse
As I'm aware, you can select packaged files which you have downloaded. It is basically the same file the MSM tool downloads, but it could be a higher version. (I.E: MSM tool downloads OOS 3.5.6 by default, but you could flash a file which you downloaded yourself, which can be OOS 4.0 or so.)
Correct me if I'm wrong, I've only used the MSM tool once or twice, and I'm speaking from reading about it on other threads.
Don't panic, your phone can get into fastboot and recovery, so you can definitely save it. Its just a little annoying, but it's not like its a Samsung device. I've myself had the white light. It can be easily fixed.
Supporting each other is what a community is for. Helping each other is what we do.
Good luck, and update us on what happens.
Update: Tried versions 3.0.6 and 3.0.8 of MSM in addition to the version 3.0.0 I had before. No luck. I'm starting to feel like I've tried everything there is to try... The device works everywhere else like it should, it just doesn't boot into system. Recovery and fastboot and Qualcomm mode are available, just can't seem to fix this with those... I need some help
It could be some sort of hardware damage. Following liquid ingress, my oneplus 3t had the exact same symptoms. The problem in my particular case happened to be with the board with audio jack on it at the bottom, I could use the phone normally (without hardware keys/fingerprint scanner) by disconnecting and blocking the two connectors for those components, until a replacement board arrived. The board cost me £8.50. There could be loads of reasons for this blank screen and white LED though, gluck mate!
hey bro, im facing the same with you on my 2nd hand 3T. almost all rom i tried cant fix that problem, but i got some fix when i flashed RR Sultanized.
- UBL
- flash latest TWRP or blu_spark TWRP recovery
- wipe everything
- follow carefully with this link to flashing RR Sultanized
- flash gapps (im using aroma gapps, pico is recommend)
- boot system to make sure everything is good
- install wakelock from playstore, choose partial wake lock (without this you will get random reboots or shutdown, but white led is gone on mine)
- restart system
- then magisk to root if you like
so far this is saved my poor 3T, good luck bro
sorry for my bad grammar
bluuquthug said:
hey bro, im facing the same with you on my 2nd hand 3T. almost all rom i tried cant fix that problem, but i got some fix when i flashed RR Sultanized.
- UBL
- flash latest TWRP or blu_spark TWRP recovery
- wipe everything
- follow carefully with this link to flashing RR Sultanized
- flash gapps (im using aroma gapps, pico is recommend)
- boot system to make sure everything is good
- install wakelock from playstore, choose partial wake lock (without this you will get random reboots or shutdown, but white led is gone on mine)
- restart system
- then magisk to root if you like
so far this is saved my poor 3T, good luck bro
sorry for my bad grammar
Click to expand...
Click to collapse
He said in OP he can't flash TWRP.
krombopulos said:
It could be some sort of hardware damage. Following liquid ingress, my oneplus 3t had the exact same symptoms. The problem in my particular case happened to be with the board with audio jack on it at the bottom, I could use the phone normally (without hardware keys/fingerprint scanner) by disconnecting and blocking the two connectors for those components, until a replacement board arrived. The board cost me £8.50. There could be loads of reasons for this blank screen and white LED though, gluck mate!
Click to expand...
Click to collapse
Yup, cannot flash twrp throguh ususal means... But you saying you had a similar problem, phone wouldn't boot with those parts connected, but did go just fine with them disconncted? If that's the case, I will start trying it with different parts. I really want to get this thing working! Thank you for both of your inputs!
bluuquthug said:
hey bro, im facing the same with you on my 2nd hand 3T. almost all rom i tried cant fix that problem, but i got some fix when i flashed RR Sultanized.
- UBL
- flash latest TWRP or blu_spark TWRP recovery
- wipe everything
- follow carefully with this link to flashing RR Sultanized
- flash gapps (im using aroma gapps, pico is recommend)
- boot system to make sure everything is good
- install wakelock from playstore, choose partial wake lock (without this you will get random reboots or shutdown, but white led is gone on mine)
- restart system
- then magisk to root if you like
so far this is saved my poor 3T, good luck bro
sorry for my bad grammar
Click to expand...
Click to collapse
Yea... I got my bootloader locked so no luck there... Thanks anyway!
MrMatson said:
Yea... I got my bootloader locked so no luck there... Thanks anyway!
Click to expand...
Click to collapse
Yeah You need to UBL first bro, try via fastboot to flash twrp.
Im using msm tool first, then flashing OOS, next UBL
I don't think UBL will help either, as I am stuck on stock reocevoery.
Update: https://forum.xda-developers.com/general/rooting-roms/installing-twrp-locked-bootloader-t3669879 this guy seems to have succeeded in doing what I tried on a Xiaomi phone. I don't know if it's possible to replicate on a oneplus though... No luck so far
MrMatson said:
Yup, cannot flash twrp throguh ususal means... But you saying you had a similar problem, phone wouldn't boot with those parts connected, but did go just fine with them disconncted? If that's the case, I will start trying it with different parts. I really want to get this thing working! Thank you for both of your inputs!
Click to expand...
Click to collapse
That's right, the phone would boot normally and was usable with the two flexes disconnected, I just had to active a software navbar. TWRP would work normally with them connected, I think that's because the hardware keys/fingerprint scanner aren't active in recovery.
my friend op3 also had similar problem, the problem only occur after changing camera module. change back to original faulty modules seems fixed the issue. after he order other camera module and assemble it back, the device worked normally, it seems that any hw dmg will prevent the phone from booting system.
krombopulos said:
That's right, the phone would boot normally and was usable with the two flexes disconnected, I just had to active a software navbar. TWRP would work normally with them connected, I think that's because the hardware keys/fingerprint scanner aren't active in recovery.
Click to expand...
Click to collapse
Oh... As I have stock recovery, the back key can be used to go back, and it seems to work... Well, any hardware modifications will have to wait, as I do not have a T2 driver and there seems to not be a single one in stock in Finland anywhere, gotta wait out on one from china.... But maybe trying some other parts will work The navigation keys also light up briefly when booting, for a second or so. Thanks!
krombopulos said:
That's right, the phone would boot normally and was usable with the two flexes disconnected, I just had to active a software navbar. TWRP would work normally with them connected, I think that's because the hardware keys/fingerprint scanner aren't active in recovery.
Click to expand...
Click to collapse
koax88 said:
my friend op3 also had similar problem, the problem only occur after changing camera module. change back to original faulty modules seems fixed the issue. after he order other camera module and assemble it back, the device worked normally, it seems that any hw dmg will prevent the phone from booting system.
Click to expand...
Click to collapse
Thanks to you, I have that tingling sensation of trying again! I hope this is not on the motherboard, everything else I can manage.... Just gotta survive the wait for my T2 screwdriver..... This is a nice feeling
MrMatson said:
Thanks to you, I have that tingling sensation of trying again! I hope this is not on the motherboard, everything else I can manage.... Just gotta survive the wait for my T2 screwdriver..... This is a nice feeling
Click to expand...
Click to collapse
Just curious, did the seller give you any information about why the device was bricked?
Cause if he was just trying to modifying the software without knowing what he was doing you should have resolved it by now, as MSM-download-tool does not show specific errors I assume it's able to write software correctly to the corresponding partitions but then something prevents it from booting up to android system, unfortunately the chances for any hardware related problem are definitely there, even very likely...
So if you bought the device assuming a software related problem but got a hardware defect it could look just the same from outside, only further possibilities I see is by having a look inside and even then you'll need some luck finding the issues...
Don't know if you have one of these little phone repair shops around but they're helpful sometimes getting advice about hardware, etc. also YouTube is a great resource for tutorials...
Just my 2 Cents, good luck
- hope you succeed in the end!
Sent from my OnePlus 3T using XDA Labs
Hi all. I never posted anything here. This is my new post. I don't know whether I can post here or not. Please allow me to post here the moderator.
I'm doing this because I don't have another way. :crying:
The problem is I tried to revert back to stock android, first time I got Odin flashing error. So I searched and found a solution. So In that way I done. But it shows "use emergency recovery mode in smartswitch" so I tried that also. But in smartswitch the firmware is not showing.:crying: It says check the S/N and Model No. I tried so many times.
At last I found a way that, when I face the error I flashed stock recovery and reset the phone and it turned on. I was very happy. But in other side it shows as On NXT. IDK what to do. And device status still Custom, although I've done it through Odin. :crying::crying::crying:
This is the main problom that I'm facing. If it familier to anyone of you, please help me. I'm in this problom since 3 weeks. If anyone can help me it will be really great for me.
Bcz of that I flashed a custom rom. Now I'm on it.
IF ANYONE CAN HELP ME PLEASE REPLY.
EAGERLY WAITING FOR SOME RELEVENT ANSWERS:victory:
Do you want to set it to official you your warranty back?
alpha12321 said:
Do you want to set it to official you your warranty back?
Click to expand...
Click to collapse
Thanks for your response brother. Now atlast I done by wiping everything and flashed stock and it solved. now I got official and same model version. :good:
Thankyou for your response.
RaeesReyi321 said:
Thanks for your response brother. Now atlast I done by wiping everything and flashed stock and it solved. now I got official and same model version. :good:
Thankyou for your response.
Click to expand...
Click to collapse
Well I did nothing
alpha12321 said:
Well I did nothing
Click to expand...
Click to collapse
since I got a response only from you after 3 posts
i have the same problem, pls help. what did you do?
RaeesReyi321 said:
Hi all. I never posted anything here. This is my new post. I don't know whether I can post here or not. Please allow me to post here the moderator.
I'm doing this because I don't have another way. :crying:
The problem is I tried to revert back to stock android, first time I got Odin flashing error. So I searched and found a solution. So In that way I done. But it shows "use emergency recovery mode in smartswitch" so I tried that also. But in smartswitch the firmware is not showing.:crying: It says check the S/N and Model No. I tried so many times.
At last I found a way that, when I face the error I flashed stock recovery and reset the phone and it turned on. I was very happy. But in other side it shows as On NXT. IDK what to do. And device status still Custom, although I've done it through Odin. :crying::crying::crying:
This is the main problom that I'm facing. If it familier to anyone of you, please help me. I'm in this problom since 3 weeks. If anyone can help me it will be really great for me.
Bcz of that I flashed a custom rom. Now I'm on it.
IF ANYONE CAN HELP ME PLEASE REPLY.
EAGERLY WAITING FOR SOME RELEVENT ANSWERS:victory:
Click to expand...
Click to collapse
i have the same problem, pls help. what did you do?
Hello Friends,
So I have quite the problem here. I recently tried to root my new Galaxy Note 8 sm-n9500 128gb. Apparently something went wrong and the root didn't work.
Not only that but since then my Phone wont recognize my sim card anymore and can't use mobile data because of that. It also shows no more IMEI.
I looked for guides how to fix that but coulnd't find any. So I started from the beginning with unlocking the bootloader trough BlueEffects Guide. After that installed TWRP and then magisk. TWRP will install but then the phone crashes and goes into a bootloop. I can hard reset and then it works again, tho TWRP seems to be unable to flash anything. I tried also SuperSu next to magisk but nothing works. If i understand correctly if i would succeed rooting the phone, I can just flash a new modem on the phone, or the EFS Folder and it should work again. Or also use some Apps with root rights to get the IMEI back?
I would appriciate anything that could help me restore my phone.
Thank you so much.
Regards Patrice
Nobody...?
Try flash stock rom
OnnoJ said:
Try flash stock rom
Click to expand...
Click to collapse
I already tried. I tried flashing many different Stock roms with different Versions and even older ones. Nothing changed tho.
I think you may have to take your phone to a service centre.
Seeing as you have erased the IMEI number from your device you would have to reflash back onto the BIOS
liquidguru said:
I think you may have to take your phone to a service centre.
Click to expand...
Click to collapse
Wouldn't they refuse to do anything with it because I tried to root it and knox got tripped?
iceepyon said:
Seeing as you have erased the IMEI number from your device you would have to reflash back onto the BIOS
Click to expand...
Click to collapse
If i understand it correctly that shouldn't be too hard to do by myself if the phone was rooted. The problem is that I can't get the phone rooted. I tried with BlueEffect's guide but it didn't work.
Now i have the problem that I can't seem to get Odin to do anything. No matter what I try to flash it always fails instantly after "connection setup". It worked before tho, so I really don't know what the problem is.
Elekted said:
If i understand it correctly that shouldn't be too hard to do by myself if the phone was rooted. The problem is that I can't get the phone rooted. I tried with BlueEffect's guide but it didn't work.
Now i have the problem that I can't seem to get Odin to do anything. No matter what I try to flash it always fails instantly after "connection setup". It worked before tho, so I really don't know what the problem is.
Click to expand...
Click to collapse
Sounds like that you may have completely wiped and unformated the internal storage on your device. I would recommend that you reformat it with the mtr setting.
iceepyon said:
Sounds like that you may have completely wiped and unformated the internal storage on your device. I would recommend that you reformat it with the mtr setting.
Click to expand...
Click to collapse
How do i do that? I have never heard about that