Related
Hey all, before I say my problem, firstly I have no idea if this is the right section in the forums so apologies in advance, secondly, I have held out for 3 days trying to work out various issues before I posted. I probably did just miss one thing or misread another but no matter how much I look, no idea what as new to this. Thanks in advance for your help.
Basically, wanted to flash some custom firmware to my phone, I have been having many issues with backing up on Kies, seems to be something related to my USB's and my computer, it keeps failing during the backing up of programs. I ended up giving up on this, made a titanium pro back up of System files and of programs, also made a Nandroid backup, both on my internal phone memory I believe. Have root access, installed busy box and such, backed up some other stuff using EFS Pro, now I am completely confused, I have followed a few guides dotted around the internet, tried to install some custom firmware, it was Carbon Rom 4.2 I believe. I went into the CMW menu, wiped data/factory reset, wiped partition cache, and wiped dalvik cache, installed the rom from my internal phone memory, as it would not find it on the memory card when I tried, and now after two attempts of it seemingly doing it, on rebooting the phone, I go back to the Samsung firmware.
I have tried to read up as much as I can but obviously I am missing something here and no amount of guides or google searches have hinted at my problem, could anyone help? I know people asking constantly for information on how to put on custom firmware will be irritating, but I have genuinely taken this as far as I can alone Cheers
Now after formating something under mount/system, my phone is stuck on the logo screen, reinstalling the ROM does not work either, no idea what to do now
reflash rom, wipe data and voila.
Hey, thanks for the reply. By reflash rom, which way do you mean, am pretty confused still. The rom I download basically bricked my phone, I don't know why, I think to recover it I use ODIN and get my stock software, so is that what you mean? Or can I somehow use my Nandroid back up..?
deancolt45 said:
Hey, thanks for the reply. By reflash rom, which way do you mean, am pretty confused still. The rom I download basically bricked my phone, I don't know why, I think to recover it I use ODIN and get my stock software, so is that what you mean? Or can I somehow use my Nandroid back up..?
Click to expand...
Click to collapse
If you have a Nandroid restore that or flash your original firmware via Odin .
Never restore system files after a firmware change with TB .
jje
Ok here is the situation now, I have made things 100 times worse, I possibly should not of been doing it this late... I followed guides exactly though and there is definitely something not working right with this phone, I just don't know what, all I know is its very temperamental with connecting to computers and will fail doing the custom firmware flashes half the time, no matter what I use, even using the stock ROM i got from samimobile has caused many problems. It might be me, I don't know, but in my frustration followed some advice on a forum and I think I formatted the mount/system. SO obviously I lost both my back up's. My fault and can live with that, phone was bricked and had to do that to get past it I think..
But now no matter what kernel I use and have tried quite a few including my original one, I am unable to connect to my home wifi. It definitely is not the wifi, it worked just fine before I flashed the phone and has been working with it for 4 months, now whenever I set up the phone its constantly stuck in this obtaining network ip infinite loop. No fixes I have used have helped at all so far Sorry to keep asking stuff, I am just literally at the end of my tether, was up until 7am messing with it to no avail.
Just to reiterate a point, the reason I wanted custom firmware was because the phone was crashing randomly and just dying on me and also the speaker had lost like 90% of the volume when I wanted to play music, also it would not connect to my computer with ease, now obviously before I did anything it had issues. So that is why I feel something might be wrong, not saying I did not break anything myself, just the process of flashing the firmware has been pretty straight forward once I did it a couple of times, it has just been failing and bricking every other time, so I am not sure what the problem actually is, did I miss a step, did I mess it up? If not what has. Please helps guys. Regards.
I formatted the mount/system. SO obviously I lost both my back up's
Click to expand...
Click to collapse
formatting system wouldn't touch your backups
deancolt45 said:
Just to reiterate a point, the reason I wanted custom firmware was because the phone was crashing randomly and just dying on me and also the speaker had lost like 90% of the volume when I wanted to play music, also it would not connect to my computer with ease, now obviously before I did anything it had issues. So that is why I feel something might be wrong, not saying I did not break anything myself, just the process of flashing the firmware has been pretty straight forward once I did it a couple of times, it has just been failing and bricking every other time, so I am not sure what the problem actually is, did I miss a step, did I mess it up? If not what has. Please helps guys. Regards.
Click to expand...
Click to collapse
Usual reply if you did not know what and why and had never bothered to read the faqs and guides before flashing .Then its nearly always user error .
Best take it to a service centre and pay for a repair .
jje
edinghn are
Close thread please
Found out something really handy
Hi guys,
TheGS3 has 1 huge trick when u got stuck in firmware, CSC, etc.
Especially when u used some super usefull toolkit (like me)
I used the Galaxy S3 Toolkit, option4 (ALL in ONE) just push enter 2 times
1 to start and the last one to exit...
Got all the issues i read on hundreds of pages searching for the solution.
Accidentialy i found this morning (its 4:45am right now and busy with it since 15:00)
Start Kies, connect GS3 with USB kabel and when it says not connected take out USB
Dont plug in USB for a while...
In KIES go to Tools and irmware upgrade.. Remember, DONT plug in USB
It will ask u for your model nr which is printed on sticker in baterycover
Confirm and it will ask u S / N' which is printed on same sticker
It will start downloading firmware and u will be guided through update progress
Good Luck to y'all.. Time to go to bed.......
Ok, so I have a serious problem... My phone is locked and when I touch the text bar to enter the password, no keyboard comes up. Important information:
- I just upgraded to jelly bean (the official one that came out today)
- as far as I can tell, everything is working fine, i just can't unlock it
- when I touch the text bar, it makes a noise, but no keyboard comes up
- was working fine immediately after the upgrade
- I got done fixing some settings and locked the screen
- this may have something to do with changing the default keyboard to Google Keyboard (it was acting a little funny immidiately after, like it was crashing)
- I have Android Lost installed, the unlock function isn't working, but others do work
- phone is encrypted
Unless someone has some ideas for me within the next couple hours, I'm going to wipe the phone. Obviously, I would prefer to not do that.
==========================
EDIT:
I've managed to use Android Lost to make some backups of some stuff, but I'm still trying to figure out how to unlock the screen. I've found that I'm able to install apps remotely from google play if that gives gives anyone some ideas.
=============================
EDIT2:
I had another idea. If this is a problem with the keyboard, is there a way for me to change it remotely? Can I install another one via the store?
Alright... I gave up on trying to get passed the lock screen and tried doing a factory reset. I was afraid of the super brick issue, so instead of doing a wipe in recovery mode, I used Kies to reflash it. However, that did nothing. The phone started back up and acted like nothing happened. It asked me for the same password, then got to the lock screen and had the same keyboard issue.
I've tried various roms, but nothing seems to wipe the encrypted information properly. At some point, I got it to forget the password, but it still thinks that one exists. I even rooted it and tried shostock3, but when it boots, it asks for a password. The old password doesn't work, so I can't get passed it. I tried entering the "wrong" password many times and it said it would wipe the phone, but it just restarted to the SAMSUNG boot screen and just sat there. I pulled the battery after half an hour...
I should note that stock gingerbread seems to work fine...
Does anyone have any ideas on how to wipe the encrypted data?
If you can push apps to it, try pushing an app like no lock or something.
Short answer: No.
It is probable that encryption information is stored in the efs (encrypted file system) folder. That's where the imei and other critical stuff is stored. I don't believe anyone who posts here in the I777 forum really has a grasp on how phone encryption works though. I've only seen one other person post here who had an issue with an encrypted phone, and he was unable to solve his problem as far as I know.
If you have a proper backup of the efs partition from before the phone was encrypted, it is possible that you could solve the problem by restoring that partition. But I'm not even sure you could write to that section of the phone memory with adb with the phone in it's current state. Edit: if you can boot into stock gingerbread normally, then you can restore an efs backup, if you have one.
I'm guessing you could send it to Samsung and they could fix it for you probably.
I finally got it working. I'm not sure what combination of things did it, but I had to restore it to stock jelly bean (via kies) to get it to wipe the encryption. I guess the stock rom knows how to properly wipe it when you keep entering the wrong password. After I got it all cleaned up, I put shostock3 back on. When the battery charges back up, I'm going to try encrypting it again (in shostock).
However, now I found another issue (may or may not be a real problem). I wanted to check if the phone was still unlocked, so I dialed *#SIMLOCK# and it says "Connection problem or invalid MMI code."
Tada!
Creepy, my good friend, would be referring to me and as you know SCIU I didn't ever get it to unlock the phone. Oddly enough a stock ICS rom (my mom now has my phone right up the road so I may try this to see if it will work and then go back to ShoStock3) works fine. I have nothing hidden from the phone storage, everything shows up, it is actually unlocked and rooted though not a custom bios err firmware/ROM because when that is put on there the encryption issues come back and the password is asked for. If the correct password is entered (and my KEYBOARD comes up but I didn't change it from the Android/Samsung one) it proceeds to enter whatever it is supposed to (my guess is the POST area like on a computer when it is entering Windows/Linux, etc.) but the screen stays black (ShoStock logo doesn't even appear if I remember correctly or it does show then goes to black loading screen with the Samsung logo and that is it, perm stuck). However I did try flashing back to Gingerbread ROMs and ICS ROMs though not through official KIES.
SCIU I may have to give this a try if my mom don't mind it and see if that helps fix the problem. Thanks for starting this thread. I am sorry I didn't respond to the PM you sent me (my LGOG, Triple OG, OG, TRIPLE OG, Optimus G AT&T Phone has screen cracked twice and is unresponsive on two different phones so I sent that in to warranty repair [rapid heating and cooling issues]) and haven't been on XDA for a week. If there is anything else you need to ask or bounce ideas off of me then I am all for it.
As far as encryption goes, the process works the same as any other encryption algorithms used (MD5/HASH/SHA-!, etc.) using a basic replica of most file systems although mobile storage tends to work a tad differently. Unfortunately, the freezer trick, brute force, nor any other cracking methods I was able to try at home worked to get it to open up. I tried getting into the EFS area of the phone but never could get to the directory or have it display.
Again thanks SCIU and as I stated I may give this a try if my mom don't care.
Eagle
i've the same problem here but i cann't use kies when my phone is locked .... so what can i do??
rawan-omer said:
i've the same problem here but i cann't use kies when my phone is locked .... so what can i do??
Click to expand...
Click to collapse
You can get the full stock jelly bean Odin flashable tar in the Download Repository. See link in my signature. According to sciguy125, flashing stock jb and then inputting repeatedly the wrong password will clear it. I'm not sure how many times it takes, 5 or 10 I think. I've never worked with an encrypted phone. I'm just repeating what I have read others say. I've seen the above posted by at least one other person. You should be able to flash the stock firmware using Odin. The one you want is I777UCMD8
my phone screen is locked (with word password) , Huawei, and the keyboard doesnt show up when i click the box? tried reseting it, cant go to settings whatsoever! i didnt damage my phone in any way either. need help asap!!
moselyy said:
my phone screen is locked (with word password) , Huawei, and the keyboard doesnt show up when i click the box? tried reseting it, cant go to settings whatsoever! i didnt damage my phone in any way either. need help asap!!
Click to expand...
Click to collapse
Friend, this is the forum for the S2 (Samsung), so you won't find anything about Huawei devices here - best to ask your question in the forum for your device.
That being said if you are rooted and have a custom recovery, simply power the device off and boot into recovery and perform a factory reset from there. If that doesn't work do a full wipe (this means wiping /system), then re-flash the ROM/gapps.
me too!!! do you have some tips for me?? i almost fainted when i knew that the keyboard isnt working.... i do have a lot of important files in my phone.
Easy, you fools! JUST KIDDING lol Connect an external keyboard. Restart the phone with the keyboard plugged in and you'll have one chance to input the pass every time you restart. Good luck, bosses!
my phone screen is locked (with word password) , SAMSUNG GALAXY TAB 3V, and the keyboard doesnt show up when i click the box? tried reseting it, cant go to settings whatsoever! i didnt damage my phone in any way either. need help asap!
My sumsang keyboard has stopped I cannot do nothing because is secure by password can you help please
I got the same problem but everything on my phone is fine except it doesn't let me enter the password I dnt wanna factory reset it cause I got important pictures in it any suggestions on how to get my keyboard working.
Solution that worked for me
Hello all,
I usually don't post things around, but something told me to do this, since I don't see any threads talking about this solution.
My solution was the following:
Went to google play store on my computer via chrome. Logged in to the user attached to my play store and re-installed all keyboard apps I have.
That worked beautifully and hope this helps other people!!
Hello everyone, i have a problem with soft & hard reset of my phone. If my thread is not on the right place, move it then, i apologize.
I am going to give you as much as information i have. My phone is BLU Life One L120 which is having a duplicate Micromax Canvas 4 A210 which is having the same chipset as i read into my thread for my BLU. Basically what i want to do now is just to soft or hard reset my phone... it sound easy i know but i wouldn't be asking if i haven't got an issue.
First of all i am using stock version 4.2.1 and kernal 3.4.5
I believe that i am having my drivers which i found in my official BLU Life One thread - http://d-h.st/U8e , also i tried with All MTK USB drivers 2014 http://androidurdu.net/mediatek-adb-usb-vcom-driver-pack-mt65xx-support/
However i am able to transfer files between my pc & phone but when i try to root the device (i tried with Kingo root/ One click root) it isn't recognizing my device or is unplugged, which is not true. I remember that once ago i installed TWRP recovery but i can't access from there no longer and i don't know the reason of that, otherwise i would reset it from there. Eventually recently i uninstalled superSU app and now i don't have root access anymore, which grow as a problem also. I checked it with RootChecker app. Also when i was doing both the soft and hard reset i removed the both SIMs & SD card just to be sure that i am doing it right.
When i use the soft reset it's giving me the option to run it but when it restarts it's all the same, nothing changes. It's the same with hard reset when i try to enter into Recovery mode.
Q: Why do i want to soft & hard reset it ?
A:
The first reason is that not a long ago my wi-fi signal got weaker despite that i'm next to my router and it wasn't like that when i bought it firstly and i want to use it instead of paying for it. I read a lot of stuff, but i can't find anything exactly the same.. which is why that i believe that if i reset it, it may went back normally.
The second reason is that i just want to change my factory rom with a custom one , because the phone is having a great performance
I hope that i gave a lot of information, thanks in advance :good:
Hello,
I am encountering a strange problem with my new Redmi Note 2, purchased from Top One. Whenever it is off and the battery is in, every 30 seconds it will vibrate and momentarily flash the white Mi logo as if it is about to turn on, then it will go back to black, then do this again in ~30sec. I have tried removing the back of the phone to see if it is an issue with the power button but it continues to happen whenever the battery is in. If battery is removed for ten seconds and then put back, the issue stops -- but then as soon as I turn the phone on, and then power off, it starts again. Otherwise the phone seems to run normally.
I flashed it to Miui 7.2.2.0 global stable Rom immediately after receiving it, and the problem has been there from the start. I believe I had noticed it there even before I flashed the new rom but I'm not sure as I hadn't yet interacted with the phone much...
Any suggestions? If you could please give me your instructions as basically as possible, and for Mac, I would appreciate it as I am a newbie. I flashed the rom using my Mac following instructions from the MIUI forms that showed how to do it in terminal after installing "adb/fastboot."
Thanks!
Seems to me that it is going into bootloader mode, instead of powering off completely. I am not sure how this could have started - perhaps a partially failed ROM upgrade at some point. I think you should return it (after restoring the original ROM) because trying to solve the problem might have to involve doing some low-level and extremely risky stuff.
Or for some weird reason the buttons get stuck and restarts to recovery.
When you try to boot into recovery, you get black screen->vibration->MI logo, and if you continue pressing the buttons you repeat the pattern.
Remove the battery cover and check if there's something in the buttons for a start..
Thanks for your responses
DarthJabba9 said:
Seems to me that it is going into bootloader mode, instead of powering off completely. I am not sure how this could have started - perhaps a partially failed ROM upgrade at some point. I think you should return it (after restoring the original ROM) because trying to solve the problem might have to involve doing some low-level and extremely risky stuff.
Click to expand...
Click to collapse
Could you give me a sense of what the low-level/risky stuff would be? Is it something I might be able to get done at a phone repair shop in the UK (where Xiaomi of course is not sold)? I ask because I'm required to pay for return shipping to China if I'm going to return device, and god knows how long the whole return process will take -- so if it's not a major hardware issue it might be worth it for me to explore finding a fix.
tonydeli7 said:
Or for some weird reason the buttons get stuck and restarts to recovery.
When you try to boot into recovery, you get black screen->vibration->MI logo, and if you continue pressing the buttons you repeat the pattern.
Remove the battery cover and check if there's something in the buttons for a start..
Click to expand...
Click to collapse
I don't see anything unusual in the buttons. As I said, if I remove the battery for ten seconds and then put it back in, I don't get this problem. It's only after doing a successful boot/shutdown (which works normally) that it starts again. So as far as I can tell it doesn't appear to be a mechanical problem.
littleozzyman said:
Thanks for your responses
Could you give me a sense of what the low-level/risky stuff would be? Is it something I might be able to get done at a phone repair shop in the UK (where Xiaomi of course is not sold)? I ask because I'm required to pay for return shipping to China if I'm going to return device, and god knows how long the whole return process will take -- so if it's not a major hardware issue it might be worth it for me to explore finding a fix.
Click to expand...
Click to collapse
The low-level+very risky stuff would involve flashing a full ROM. By "full", I mean inclusive of preloader, uboot/lk, etc. This is what makes it very risky, because if something goes wrong with the preloader/lk flash, the device could be bricked beyond what normal people could recover. An example of a ROM that flashes everything is: http://www.needrom.com/download/miui-7-2-3-0-redmi-note-2/
My current ROM is based on an earlier version of this, and I noted at the time it was released that it installs a preloader - but I am not sure whether I installed it complete with preloader or not (I probably did). From what I can see, nobody's device got bricked by installing this ROM, which is actually excellent (so much so that I inevitably return to it after trying something else). However, it is still risky to upgrade a preloader. I suspect that this may be what you need - but it may not resolve your problem anyway.
PS: beware of more recent Xiaomi ROMs that lock the bootloader. If you tried to do this risky process, you would be best advised to make sure that you are not flashing a ROM that locks the bootloader (i.e., the most recent ROMs coming out from Xiaomi).
DarthJabba9 said:
The low-level+very risky stuff would involve flashing a full ROM. By "full", I mean inclusive of preloader, uboot/lk, etc. This is what makes it very risky, because if something goes wrong with the preloader/lk flash, the device could be bricked beyond what normal people could recover. An example of a ROM that flashes everything is:
My current ROM is based on an earlier version of this, and I noted at the time it was released that it installs a preloader - but I am not sure whether I installed it complete with preloader or not (I probably did). From what I can see, nobody's device got bricked by installing this ROM, which is actually excellent (so much so that I inevitably return to it after trying something else). However, it is still risky to upgrade a preloader. I suspect that this may be what you need - but it may not resolve your problem anyway.
PS: beware of more recent Xiaomi ROMs that lock the bootloader. If you tried to do this risky process, you would be best advised to make sure that you are not flashing a ROM that locks the bootloader (i.e., the most recent ROMs coming out from Xiaomi).
Click to expand...
Click to collapse
Thanks for this. Could you point me to how I might be able to install a full official Xiaomi rom? (One that won't lock the boot loader.) My preference would be to get the global stable rom running as normal so that I can have the standard working phone with OTA updates. Or, is it easier to install this rom you've suggested with preloader, and then afterwards I can flash the official rom (assuming this fixes the problem)?
Also, are there any tutorials/clearer instructions for how to do this kind of install? The instructions on the link you've provided don't seem very clear...
Not sure if I'm gonna try this yet but leaning towards it if I feel confident enough I can execute it without screwing anything up...
littleozzyman said:
Thanks for this. Could you point me to how I might be able to install a full official Xiaomi rom? (One that won't lock the boot loader.) My preference would be to get the global stable rom running as normal so that I can have the standard working phone with OTA updates. Or, is it easier to install this rom you've suggested with preloader, and then afterwards I can flash the official rom (assuming this fixes the problem)?
Also, are there any tutorials/clearer instructions for how to do this kind of install? The instructions on the link you've provided don't seem very clear...
Not sure if I'm gonna try this yet but leaning towards it if I feel confident enough I can execute it without screwing anything up...
Click to expand...
Click to collapse
I personally wouldn't touch official ROMs with a bargepole. At the very least, xiaomi.eu, or ROMs based on it (like the one linked to). But each to his own. With regard to installation, I don't think you can get more detailed instructions than those given, which I will now try to present in clearer English:
Reboot to Recovery ( TWRP only )
Wipe Dalvik/Art
Wipe cache
Wipe data (note that TWRP allows you to do 2-4 in one go - they are the same as resetting to factory defaults)
Install ROM
Wipe cache and Dalvik/Art again (but do NOT wipe data)
Reboot
Wait for about 20 minutes while it builds Dalvik/Art, and other stuff
Done
Hopefully, this will cure the problem. If so, then you can install whatever ROM you want, following the same process as above. If not, then you still have an excellent ROM anyway.
By the way, doing any of this presupposes that you have already installed TWRP recovery. If not, then that is the first thing to do.
DarthJabba9 said:
I personally wouldn't touch official ROMs with a bargepole. At the very least, xiaomi.eu, or ROMs based on it (like the one linked to). But each to his own. With regard to installation, I don't think you can get more detailed instructions than those given, which I will now try to present in clearer English:
Reboot to Recovery ( TWRP only )
Wipe Dalvik/Art
Wipe cache
Wipe data (note that TWRP allows you to do 2-4 in one go - they are the same as resetting to factory defaults)
Install ROM
Wipe cache and Dalvik/Art again (but do NOT wipe data)
Reboot
Wait for about 20 minutes while it builds Dalvik/Art, and other stuff
Done
Hopefully, this will cure the problem. If so, then you can install whatever ROM you want, following the same process as above. If not, then you still have an excellent ROM anyway.
By the way, doing any of this presupposes that you have already installed TWRP recovery. If not, then that is the first thing to do.
Click to expand...
Click to collapse
Thanks for the English translation haha, I'll give this a shot. Just one more question -- when you write "install ROM", I should just treat the ROM the same way that I would any other, by flashing it via fastboot (as I did in OSX terminal) right?
littleozzyman said:
Thanks for the English translation haha, I'll give this a shot. Just one more question -- when you write "install ROM", I should just treat the ROM the same way that I would any other, by flashing it via fastboot (as I did in OSX terminal) right?
Click to expand...
Click to collapse
No. Steps 1 to 7 inclusive are done from TWRP Recovery.
DarthJabba9 said:
No. Steps 1 to 7 inclusive are done from TWRP Recovery.
Click to expand...
Click to collapse
Well, thanks again for your suggestion, but unfortunately it didn't succeed. I managed to install the custom full ROM you suggested with TWRP, and the problem persists; when the phone is off, I get this strange problem with the Mi logo flashing.
I'm investigating how to make a return, but I thought I would ask: do you have any idea whether this problem will negatively affect the phone in any other way? Because, if I'm unable to make a return, I think it's an issue I can live with (I rarely have my phone switched off anyhow), so long as it won't cause more problems down the line...
Something else I just realised: Apparently the problem doesn't occur when the phone is plugged into the USB (both electrical socket and computer). Starts up again as soon as I remove the plug. Perhaps that provides more context...
littleozzyman said:
Well, thanks again for your suggestion, but unfortunately it didn't succeed. I managed to install the custom full ROM you suggested with TWRP, and the problem persists; when the phone is off, I get this strange problem with the Mi logo flashing.
I'm investigating how to make a return, but I thought I would ask: do you have any idea whether this problem will negatively affect the phone in any other way? Because, if I'm unable to make a return, I think it's an issue I can live with (I rarely have my phone switched off anyhow), so long as it won't cause more problems down the line...
Click to expand...
Click to collapse
Well, I would hazard a guess that this is not a software problem. Clearly, the phone is trying to boot into bootloader mode or into recovery mode when it is meant to be completely switched off. This implies;
a) that there is a possibly a hardware problem somewhere (eg., something short-circuiting somewhere?), or
b) a virus/rootkit trying to dial home?, or
c) some other unknown fault?
None of these options would give me any peace of mind. If the problem is (b) then a good anti-virus or rootkit remover program would solve the problem. Search the PlayStore for those. If that doesn't solve the problem, then it's either (a) or (c) - and that is not good.
DarthJabba9 said:
Well, I would hazard a guess that this is not a software problem. Clearly, the phone is trying to boot into bootloader mode or into recovery mode when it is meant to be completely switched off. This implies;
a) that there is a possibly a hardware problem somewhere (eg., something short-circuiting somewhere?), or
b) a virus/rootkit trying to dial home?, or
c) some other unknown fault?
None of these options would give me any peace of mind. If the problem is (b) then a good anti-virus or rootkit remover program would solve the problem. Search the PlayStore for those. If that doesn't solve the problem, then it's either (a) or (c) - and that is not good.
Click to expand...
Click to collapse
Nothing shows up on anti-virus/rootkit. I guess I should really insist on getting a return. Hopefully they will process it without too much fuss/expense. If any other suggestions come to anybody in the meantime, I'd be glad to hear them.
I just noticed as well that someone posted with what seems to be the same issue to mine last year: http://forum.xda-developers.com/redmi-note-2/help/phone-rebooting-shutdown-t3232941 , with no resolution. Perhaps this is some kind of occasional manufacturing problem.
littleozzyman said:
Nothing shows up on anti-virus/rootkit. I guess I should really insist on getting a return.
Click to expand...
Click to collapse
Absolutely.
HW problem: Power Management IC
I too faced this problem and I suspected Battery to be the culprit . Anyway , i got it checked and repaired at a local (non xiaomi) repair shop that claims it was the issue with PMIC power management IC and that he has replaced the IC .
Now the phone works fine and does not enter into that bootloop even when charger is disconnected and phone is rebooted manually. I hope the problem is resolved .
However , the other issue is still persistent which is : copper colored washed out MI logo constantly appears on the screen and reinstallation of sw did not help either . In india these repairmen usually cant explain the problem area if it is outside of "Try and test" scheme .
I spent 1000INR to get it repaired but I highly doubt that PMIC is replaced. Coz this repair guy did this replacement in just 6 work hours. probability of getting the right part at right time at his disposal is very slim. And I had seen his workstation once, where i di not see any SMT repair station either. Which means that he cannot replace BGA package IC at all. Anyway, I will receive the phone tonight. Lets hope it works fine and the other problem gets rectified by flashing.
Saurabh Srivastava, Noida , India
Sorry for a very strange problem.... My wife still uses her old S III (I9300), although it is so outdated and partly broken. Some time ago we flashed CM 12, so that some apps who need a more up-to-date android can be used. But the phone is too slow, there is a crack in the display and sometimes it starts to reboot without any reason. There is not enough memory to install additional apps and without LTE it is no fun.
=> I want to buy a new smartphone for her, but she doesn't want to. She wants to save money and use it, until it is not usable any more.
Of course I could give it a good strike with a hammer or give it a treatment in the microwave oven, but I would prefer only a temporary lack of functions, so that perhaps later I can use it as backup phone for the kids. Therefore I am looking for some trick, app or system setting to SIMULATE, that the phone is broken. When she is happy with her new phone, I intend to "repair" it "by chance"....
Any ideas? How can I simulate, that the phone is broken? Thanks!
You need to hardbrick it.I dont know how to but you can Google it.
ArdaCsknn said:
You need to hardbrick it.I dont know how to but you can Google it.
Click to expand...
Click to collapse
Thanks for the reply! I googled, but i think i want to SOFTbrick it, not to hardbrick it. As I wrote above, I want to "revive" it after some time....
I think the simplest way may be to take the phone, create a backup of all data, put the phone into download mode, start flashing a stock ROM, remove the USB cable when it starts to flash the final file, and reboot the phone. Hopefully, the phone will display the "firmware upgrade encountered an error" message which can be resolved by re-flashing the stock ROM with Odin.
Based on my experience with flashing a stock ROM over a stock ROM, this procedure always leaves the data and apps intact.
cm_new said:
Thanks for the reply! I googled, but i think i want to SOFTbrick it, not to hardbrick it. As I wrote above, I want to "revive" it after some time....
Click to expand...
Click to collapse
Ah,sorry I read it but while replying I forgot somehow.Yeah, then you need to soft brick it .It can be achieved by deleting some system files.So phone can got into bootloop.If your wife doesnt now how to get in to recovery then you should be ok.
Stock rooted phone needed for this, activate factory app. It will give a black window with device information over everything onscreen. Disable factory app to remove it later on.
By flashing the stock firmware in an attempt to make it all better gives the perfect opportunity to pretend the process buggered it.
Put some clear tape on the battery contacts ?