Related
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Seriously???
pastorbob62 said:
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Click to expand...
Click to collapse
Not to be negative or anything but I think this is the least responsive forum on this site. I have spent hours searching for possible solutions to various problems I've encountered over the past several months, asked several questions and received little if any help. I was only able to get back from a bricked phone to where I am now by using information found on other websites. Pretty sad if you ask me.
In contrast, whenever I have asked a question on my tablet's forum I've received fast workable solutions/answers to my problems/queries. The threads are informative, well organized and contain answers to any situation I have encountered.
Granted, my current problem with my phone is my own fault for trying to customize it. And I suspect part of the problem is due to the age of this phone thus most of the "experts" have moved on to other ventures. It is also hindered by the lack of information available from Huawei and the service providers.
All of that said, if anybody has any suggestions for how I can repair the ESF partition or whatever is causing this lack of mobile service issue I would be extremely grateful. It isn't the end of the world since i have a new phone (Consumer Cellular) that I am currently using but it would be great to get this one working since it's much faster and more streamlined than my stock Consumer Cellular version.
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
Thank you very much for your reply. It seems that you have found the answer to my problem. But unfortunately, I don't have a copy of the original stock ROM. My phone is the -51 version and any links I have found to the stock ROM are broken. There is a version I found but it is for Venezuela and I don't think it will work. I am leery to try it and totally brick my phone. My backup is apparently corrupted. I backed up my new working phone with Disk Image and attempted to restore it to the broken phone but all that did was cause it to come up to the ATT logo screen for a few seconds and then shut down. It wouldn't do anymore than that. So I restored the Stallion 3.5 image I made and am back to a great fast tablet with no phone service. I also tried backing up my IMEI on the working phone and restoring it to the broken phone but that had no effect.
It is my understanding that the -Pro version of the ROM will work, but I don't have the stock image of that either. I suspect it work might since I was able to use the -Pro version of GB on it. All of my internet searches have only turned up custom ROMs and other desperate people looking for fixes for similar problems or worse. I agree 100% with your assessment of Huawei's lack of meaningful support. It really is a shame, because these phones aren't half bad when they have been customized and OC'ed a little.
I have just about given up on it and resigned myself to using it as an MP3 player for my car system. I have learned my lesson and am leaving the working phone stock. It is rooted and I have cleaned off all of the bloatware, and set it up so most apps run from my SD card, so it really isn't half bad. At least it works.
Again, thank you for your reply and advice.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
ggunzio said:
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
Click to expand...
Click to collapse
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Blefish said:
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Click to expand...
Click to collapse
i have exactly the same phone than you, because i installed that backup too. After installed it, the IMEI SV is 36, after installing B518 it says it is 18, but before it was 17, and i had 3g signal, but not now.
My question is, wich SV is your phone reporting?
Thank you
I also have a problem like this, but I think it's a bit more severe. My phone got stuck while charging. Couldn't reboot. Was getting stuck on the aurora loading screen(using DZO 5u20). Than reinstalled whole rom. But now I don't any signal and the phone doesn't even see a SIM card. Showing 'baseband unknown' and the IMEI and IMEI SV are also unknown. Not 0's but just unknown. Is this is a similar problem? And can something be done to fix it.
I had some backups on my sd card, untill the sd-card got fried in the phone a couple of months ago.
Note 4 Stuck in Boot Loop - Help
I have a Note 4 SM-N910F, never been rooted, stock rom upgraded to 5.1.1 back in October, working fine until yesterday when it got stuck in a Boot loop.
Not sure what caused it but before it got stuck I was messing around with Google Photos which was running a bit slow.
Also I put it on the Qi Charger just before the loop started. It has an aftermarket Fone charger stuck to the battery. I’ve had this and the Qi Charger for 6mths with no problems before now.
It gets to the Samsung page waits a couple of seconds then boots again.
Here’s what I’ve tried - unsuccessfully - to fix the boot loop:
1: recovery mode.
I can get the little recovery text to appear in the top left but after a few seconds it boots again.
2: volume down, home
This gets me to the screen with up/down for continue/cancel.
This is the _only_ screen I can get to stay up without rebooting. It sits there waiting for input.
- Cancel, causes restart, of course, but back into the bootloop
3: Mashing on power button. Banging it, wiggling it, blowing on it.
I read somewhere this could cause a boot loop, but I doubt it is my case because
a. I’ve never had problems with the power button before
b: When I take out the battery and put it back in, it does NOT turn on. If I do the same holding the power button, it powers into the boot loop. So if the button were jammed on I would expect it to never remain off with the battery in.
3: flashing stock rom
I’m not 100% sure what build I had before. I know it was stock 5.1.1 OTA, and I’m pretty sure it was unlocked (my wife bought the phone and i inserted my old sim, but she may have bought it from my carrier and can’t remember)
So anyway I tried all three versions of TPH (unlocked) 5.1.1 from Sammobile.
Installed Odin 3.10.7 and flashed them.
It reboots to recovery but immediately boot loops again.
I doubt its to do with the version of the rom anyway since the symptoms are identical after flashing. Only now the boot loop always shows the little ‘recovery booting...’ text in the top left.
Here’s what I have NOT tried but am thinking about:
A: Re-partition option in Odin
B: Nand Erase All option in Odin
C: Buying a new battery.
On A/B: as far as I can tell what I have done so far should have left the data intact. I’m prepared to wipe all my data if it fixes my phone (no lectures about backups please!) and I’m tempted to do one of these on the off chance that the problem is caused by data or the “disk" problems.
But I don’t want to brick it. Can someone recommend how likely these are to help
And what they actually do?
(Please refrain from responses I see elsewhere like “this will brick your phone if you don’t know what you’re doing”. I don’t know what I’m doing, thats why I’m asking - just the facts please)
On C: the battery seems ok in that the power is solid even after not being plugged in for a long time, but since it was on the Qi Charger with that aftermarket thing stuck to it when it happened, I’m suspicious. Can any one say if this is a likely cause?
If so, it might be worth waiting till I get a new batter before doing A or B (can I wait days for Amazon!?)
[UPDATE] Got a new (genuine) battery at a local electronics store. No dice. Same problem, so it's not the battery. Shall I go ahead and re-partition.
[UPDATE] Got a PIT file from another forum, and flashed again with re-partition checked and PIT loaded. same results.
Is Nand-rease worth trying?
The phone is still under warranty so maybe I can return it.
But in that case I want to erase what's on it first.
thanks for any help
rhubarb
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
You can flash TWRP through ODIN while on COJ5 bootloader. It's locked but you still can flash recoveries and kernel and 5.1.1 ROMS
I am very interested in this thread. I have the EXACT same problem as you have after installing SimplRom, which was a ROM prior to COJ5. It could indeed be that our bootloaders are locked now?
I am using the N910F and just like you, installing any ROM/Custom Recovery/Bootloader/Kernel doesn't help. Perhaps installing a COJ5 ROM might help. I will give that a try, but I've recently used Kies to install the latest official firmware, but it didn't fix the issue.
I will report back here and we'll work on this together to make our phones work again!
Osama lakdawala said:
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Click to expand...
Click to collapse
Thanks but:
1: I have no custom rom. I have never had a custom rom on this device. I want to take it to Samsung, but want to clear the memory first. How can I do that?
2: I _am_ a software engineer_
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
roverrhubarb said:
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Click to expand...
Click to collapse
I have the exact same as you. I did install a custom recovery (multiple) and still get the bootloop. From my tries yesterday, I indeed also suspect it may be a hardware issue. Perhaps to do with the battery/charging port. When I have my device unplugged and try to start in recovery/normalboot, it does not have a bootloop but simply turns off (and then doesn't respond until I pull the battery out). I think a NAND erase wouldn't do anything as I've personally tried that already.
Have you prior (upto a week) before you got the issues had your phone in a moist environment (bathroom while showering for example). I got my problems a week after I accidentally left my phone in the bathroom and installed custom ROM (which was done earlier and had no issues).
I've read online that it may have caused oxidation on the inside and may need some cleaning/drying with alcohol.
I still hold hope that we just have a software issue as download mode is working fine (apart from the Power off not working unless we pull out the battery).
Anybody have any experience with oxidation on their phone? Perhaps have had a similar bootloop due to hardware failure?
roverrhubarb said:
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
Click to expand...
Click to collapse
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
dork997 said:
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
Click to expand...
Click to collapse
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
Since you can get into download mode I'd flash firmware through ODIN again after verifying it's correct.
I'm seeing off the sammobile site for the 910F not all are the COJ5 locked bootloader.
Since you did update in Oct you may be on the COJ3. I'd try one of those and see if it works.
If it doesn't work and stops on the sboot.bin file then you have the COJ5
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
i am sorry i don't know any way to remove personal data other than doing it via recovery. There is an option of "nand erase" in odin it is used while flashing firmware and it wipes everything on the phone but i have never used it (and also don't know whether it can help you or not) ... Senior members kindly help us with this.
Any update to your situation?
very interested as I am in the same situation as you are. Download mode works, recovery+normal boot not. No matter what ROMs/recoveries I install
Same issue I think
I am also in the same situation, although I can enter the recovery mode - home power and volume up - I have tried the wipe cache and then factory wipe to no avail - I have also entered download mode and flashed the stock recovery and even though Odin says pass, it is still in a boot loop. Also when I go to the download screen it has a line saying knox warranty void 0x1(4) does this mean I have voided the warranty even though I only used Odin to flash stock recovery?
Did anyone found a solution
Did anyone ever found a solution to this problem I'm having the exact same issue on a note 4 smn910a
I have a slightly different issue with my Note 4 SM-N910G, wherein am not able to start the phone at all, it is completely dead, if i put the cell phone on charge then also there is no LED on the top but if i connect the device to the PC it does make the connected sound on the PC but Odin is still not able to recognize the device neither kies. I tried draining the power by removing the battery, connected the device to PC without battery and then inserting it but the same problem. Please suggest me any resolution for this dead body am carrying from past few weeks.
hi Op,
did you find any solution for this issue?
Hello all. This is advice to use as a very last resort if you are experiencing the recovery bootloop issue AND you don't have the emmc failure bug. I had the recovery reboot, sudden shutdown with no warning, etc. issue for the past two weeks. I tried everything on Google and Youtube to fix my problem with no success. I flashed multiple stock ROMS and recovery tars (stock and TWRP) via ODIN, but nothing worked. Oddly enough, I never received the emmc error that I have read about. Also, in the few times that my phone booted normally, I even loaded the Wakelock Power Manager app, set it to partial wakelock and my phone STILL continued to bootloop. As a last resort, I bought a new battery, but the reboot problems continued in Android 4.4.4 Kitkat, 6.0 Marshmallow, 7.1 Nougat and 8.1 Oreo ROMS. Well, here is what finally helped me to get my phone back operational. I had a backup ROM from a previous install and a TWRP flashable version of the same ROM on my SD card (in case the phone did not stay on for the full restore). I put the phone into a ziplock bag into a freezer for about 20 min. (thankfully this time TWRP stayed on long enough for me to do the following):
1) copy all the files I wanted to save from internal storage to a computer.
2) performed a full wipe (Dalvic, Cache, System, etc. Like when flashing a ROM, but this time also internal storage. Note: Please do not wipe both internal and SD card, as you may have a difficult time trying to load the ROM file back on the sd card (assuming you don't have a card reader).
3) After wiping, I was able to restore my stock ROM backup (or you can just flash the stock ROM).
I can't be 100% sure, but I think my wiping internal and then flashing the stock ROM finally did the trick. Since this morning, the phone has been pretty much back to as it was before. In either case, I'm sharing this with the hope that it helps someone else.
Sent from my SM-N910T using Tapatalk
Hi Guys! I'd like to ask for some help and advise. I've scoured through the forums and couldn't find a solution that works. I'm helping a friend to fix his phone currently.
Phone: K30-W
Currently installed ROM: CynogenMod 12 (tested 11 too) with the same problems.
Phone was an imported phone, which had a lot of bloatware and various other issues that came with it. Bloatware was so severe that random adverts flash on the phone every couple of minutes of using it. Even after factory resetting, bloatware and junk was not removed, so i flashed his rom to Cynogenmod 11. The phone works fine with 1 caveat, modem/radio/simcard does not work. I made the mistake of not backing up his phone first, but i figured that the backups would likely come with his bloatware again anyway.
Tried re-flashing to Cynogenmod 12. Same issue persisted. I tried a solution from "http://forum.xda-developers.com/general/help/how-to-root-lenovo-a6000similar-to-t3017828/page4" as well, but still same problem persisted. I've looked for stockroms to re-install, but have been unable to find one that I could install properly either. SP Flash tool with stock roms didn't have the scatter file in the download either for the SP Flash tool to work.
Currently, all other functions of the phone is fine except for the network. So I get no data, no calls. Phone is essentially a wifi phone for now.
Do any of you here know how I can solve this? I can provide further information as required.
Thank you very very much in advance.
Flash the stock rom and head to the service centre and act innocent. I think this is the safest option rather than doing things by yourself and putting it into more trouble.
wonglc82 said:
Hi Guys! I'd like to ask for some help and advise. I've scoured through the forums and couldn't find a solution that works. I'm helping a friend to fix his phone currently.
Phone: K30-W
Currently installed ROM: CynogenMod 12 (tested 11 too) with the same problems.
Phone was an imported phone, which had a lot of bloatware and various other issues that came with it. Bloatware was so severe that random adverts flash on the phone every couple of minutes of using it. Even after factory resetting, bloatware and junk was not removed, so i flashed his rom to Cynogenmod 11. The phone works fine with 1 caveat, modem/radio/simcard does not work. I made the mistake of not backing up his phone first, but i figured that the backups would likely come with his bloatware again anyway.
Tried re-flashing to Cynogenmod 12. Same issue persisted. I tried a solution from "http://forum.xda-developers.com/general/help/how-to-root-lenovo-a6000similar-to-t3017828/page4" as well, but still same problem persisted. I've looked for stockroms to re-install, but have been unable to find one that I could install properly either. SP Flash tool with stock roms didn't have the scatter file in the download either for the SP Flash tool to work.
Currently, all other functions of the phone is fine except for the network. So I get no data, no calls. Phone is essentially a wifi phone for now.
Do any of you here know how I can solve this? I can provide further information as required.
Thank you very very much in advance.
Click to expand...
Click to collapse
Dial *#06# and check if you have IMEI or not. If you don't, then you can repair your IMEI using QFIL.
Thanks for the idea. Will look for the QFIL files and guide to try to get this one sorted. you're right. no IMEI.
wonglc82 said:
Thanks for the idea. Will look for the QFIL files and guide to try to get this one sorted. you're right. no IMEI.
Click to expand...
Click to collapse
Go through the threads mentioned in this post.
Hello
I have a Yotaphone 2 running android 5.0. I have a huge problem with the device which is, that the phone reboots automatically all by itself after the screen turns off. The screen timeout is set at 1 minute and once the screen goes off, the phone reboots! I don't know what the problem is but its making me crazy!
Note: The phone does not reboot if the screen doesn't turn off. So I changed the screen timeout to 30minutes. Also note that Wi-Fi doesn't start immediately. It doesn't even start most of the time and is stuck at "turning on"! And also, the phone isn't detecting my SIM Card!
Hope someone can solve my problem.
Wow, seems a lot of problems here. However you provided very few info about your phone.
1) Where did you buy it?
2) What have you done after you opened it, OTA? Which firmware was installed?
3) Have you tried factory reset by wiping data in the stock recovery? (Accessible with Vol+ and Power)
4) Have you tried to flash from scratch the RU .124 firmware with YotaFlasher?
5) The phone was behaving normally before or it's doing this as soon as you started using it?
I got the phone as a gift
TheArt. said:
Wow, seems a lot of problems here. However you provided very few info about your phone.
1) Where did you buy it?
2) What have you done after you opened it, OTA? Which firmware was installed?
3) Have you tried factory reset by wiping data in the stock recovery? (Accessible with Vol+ and Power)
4) Have you tried to flash from scratch the RU .124 firmware with YotaFlasher?
5) The phone was behaving normally before or it's doing this as soon as you started using it?
Click to expand...
Click to collapse
-The phone was a gift from "Aramex Company".
-Yes, I have factory reset it! Note: It wasn't possible to reset it from settings because it would always get stuck in "Shutting Down" phase and nothing would happen. So I hard reset it.
-I found something strange going on though. Whenever I reset it, It would restart (after the reset is over) and say that "ANDROID IS UPGRADED TO 5.0".
I think it is upgrading by itself to 5.0.
-No, I haven't tried any flashing.
-Yes, the phone was working fine for a while and then started behaving like this!
Cheers!
(Thank You for your support and attention by the way)
Video
Hello!
I have made a video showing what the problems are! Please give me your e-mail so that I can send you the "Dropbox" link to the video.
Thank You!
I think the first thing to do here is to flash a clean firmware (RU or EU) on your phone via YotaFlasher, search here on xda how, and then report back if it's happen again! Seems that the firmware it was shipped with wansn't so stable.
Flashed it!
TheArt. said:
I think the first thing to do here is to flash a clean firmware (RU or EU) on your phone via YotaFlasher, search here on xda how, and then report back if it's happen again! Seems that the firmware it was shipped with wansn't so stable.
Click to expand...
Click to collapse
Hey!
As you had prescribed, I flashed it! First I flashed it with Android 5.0.0-ME1.1.60 and after opening the phone I used it for a while and the phone was same as before flashing! There was no difference at all! The phone was restarting on turning screen off as usual, the WiFi wasn't turning on, and the SIM wasn't being recognized!
But then I flashed it with Android 4.4.3-S01-003-ME1.0.3.61a and the phone is still rebooting by itself upon switching the screen off and the WiFi problem still persists! The WiFi just simply won't turn on. It's stuck at "turning on"! The SIM isn't recognized either! Also, the phone is restarting from the inside now (It wasn't restarting before. I had to keep the power button pressed every time I wanted to restart)! But NOTE that the phone still cannot be just shut down, it can only be restarted!
I don't know what to do!
Cheers
can you please help me find 4.4.3-S01-003-ME1.0.3.61a firmware. i tried yotaflasher and i cant make the program work. it exits close itself. i couldnt find any firmware folder in yotadevices ftp too. can you help me found the spesific firmware please?
Why are you unable to make yotaflasher work
lgk350tr said:
can you please help me find 4.4.3-S01-003-ME1.0.3.61a firmware. i tried yotaflasher and i cant make the program work. it exits close itself. i couldnt find any firmware folder in yotadevices ftp too. can you help me found the spesific firmware please?
Click to expand...
Click to collapse
Hi lgk350tr,
Why are you unable to make yotaflasher work, it is a pretty simple application. Have you tried to see instruction videos on YouTube on how to use it? Instructions are also available on XDA Developers' website. ( https://forum.xda-developers.com/yotaphone-one/general/yota-flasher-download-t3480922 )
Don't hesitate to contact, for any problem!
Cheerio
Please help..................I spent 800 USD on this phone and I can't use it
Can someone freaking help me with my phone's problem, I have spent 800 US Dollars buying that phone, and I can't even use it! It has been 6 months since I opened this thread and no one has helped me yet!
PLEASE HELP..............................................................:crying::crying::crying:
akahomeacc said:
Can someone freaking help me with my phone's problem, I have spent 800 US Dollars buying that phone, and I can't even use it! It has been 6 months since I opened this thread and no one has helped me yet!
PLEASE HELP..............................................................:crying::crying::crying:
Click to expand...
Click to collapse
Try flashing the hybrid modem mentioned in the general guide (Part 2).
Try flashing 2 times before rebooting.
If nothing helps, you could try lineageos, @angelll123 made a lengthy guide how to that in the post quoted here , also check my comment.
Is this what you mean?
tomgaga said:
Try flashing the hybrid modem mentioned in the general guide (Part 2).
Try flashing 2 times before rebooting.
If nothing helps, you could try lineageos, @angelll123 made a lengthy guide how to that in the post quoted here , also check my comment.
Click to expand...
Click to collapse
I have attached a screenshot of the Yotaphone 2 General guide page, I want to know if you are referring to the text that I highlighted in the screenshot!
Thank You
I do experience similar issue, but only recently. I haven't done anything like flashing or upgrading my phone, it started by itself .
I am experiencing reboots whenever battery drops below about two thirds of its capacity. Also, charging and handling some load prevents this.
Note that my Yotaphone has both displays damaged. Still working though.
Hello there,
I've spent my entire day trying to fix my Galaxy Note 4 (SM-N910F), without much success.
So what happened was that the phone would occasionally freeze, turn it's self off and reboot into download mode and say that it wasn't able to boot normally. But it usually just booted after pulling the battery.
So I thought I would just try to install the stock firmware(4.4) and go from there. And that worked fine (eventually) but the problem remained.
Why not try again, I foolishly thought. So I tried to download a more recent firmware(6.0), but it wouldn't install completely. It got stuck in Odin around half, saying: "FAIL!(WRITE)". Tried again using the older firmware(4.4), but the same result.
Now whenever I try to turn on the phone it immediately jumps to download mode saying that something went wrong while installing the firmware.
I have done a couple of things to try and resolve this issue:
- I have tried to flash BL,CP,AP and Pit from a recovery firmware without much luck.
- I have tried using Odin 3.09 and 3.11.1
There was one thing that kinda helped once, which was flashing twrp and all of a sudden it worked and actually turned on. But genius me decided that I had to try again and update to the newest version. Which wasn't really smart because again the flashing of the firmware failed.
If anyone could please help me out. I have spent nearly two days trying to fix this darn thing. I really just want it fixed
Have you referred this thread :
https://forum.xda-developers.com/showthread.php?t=3488114
Reporting Via N910G
yashthemw said:
Have you referred this thread :
https://forum.xda-developers.com/showthread.php?t=3488114
Reporting Via N910G
Click to expand...
Click to collapse
I hadn't, I google searched multiple times for such a topic, but didn't find any.
Besides using the SD card to flash the firmware I had already tried what was listed there.
But for the sake of it, I tried again. For some reason, this time it did work!
Many thanks for the tip!
I'm just left with one question, the recovery firmware you provided in the topic is german, but I have a Dutch phone. Will that create any issue's with network connectivity?
SmileyFace said:
I hadn't, I google searched multiple times for such a topic, but didn't find any.
Besides using the SD card to flash the firmware I had already tried what was listed there.
But for the sake of it, I tried again. For some reason, this time it did work!
Many thanks for the tip!
I'm just left with one question, the recovery firmware you provided in the topic is german, but I have a Dutch phone. Will that create any issue's with network connectivity?
Click to expand...
Click to collapse
First, flash that recovery firmware, once your device starts working normal, flash your region specific stock rom from sammobile.
Reporting Via N910G
Thank you so much for your help. I tried to see if the initial problem was resolved, but it still isn't. The phone sometimes doesn't boot and goes straight into download mode. I'm starting to think that it's a hardware issue, but I'm not sure. Any ideas?
SmileyFace said:
Thank you so much for your help. I tried to see if the initial problem was resolved, but it still isn't. The phone sometimes doesn't boot and goes straight into download mode. I'm starting to think that it's a hardware issue, but I'm not sure. Any ideas?
Click to expand...
Click to collapse
Must be hardware.
Anyway, i would do this
- flash twrp for Note 4 (look for it) from odin
- fladh rom from twrp (not from odin)
Sent from this galaxy