Related
OK well I have trying my best as a noob to research for 2 days not in and out on how to fix my issue
My friend tried rooting my phone and to install a different rom. I am on 2.1 and unfortunately I got the phone used with 2.1 already on it so I don't know if it was a leaked or legit 2.1 rom, and I am learning as I go here to fix this issue as I have never new how to do this stuff nor have I ever done it.
Where I am at now:
only thing that happens when I hit power is the phone "vibrates then stays on the 3 skateboard screen" or press "volume down + power" and it goes to the Hboot screen. I go into recovery and it goes to clockworkmod and from there after trying to install any roms from the sd card it says on the last 3 lines
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
and every time I go back or power up to the Hboot screen it does not have any "update bar" (I guess if this was done right as I read on other threads there should be some type of update bar) on the right corner or any other options "for me to select" accept:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
and then with some other info above the Hboot highlighted in blue
I have tried formatting the sd card a bunch of times, I did the clearing of the "wipe data, wipe cache partition, wipe dalvikcache" as I read to do over my reading, but I see that if I go under any restore options under clockwork, no files are found for me to back up too so I am seeing he did not back up any of my info, I also have tried using 2 different ds cards.
So more less it looks like my options are to get this fixed from the only place my phone will boot to with options and thats when I press volume + and power so I guess loading whatever I need to my sd card>>if thats an option or am I screwed, I have seen many tutorials but none of them start where my particular position is stuck at in Hboot. this is my only phone and I had to buy a prepaid which is just about out of minutes, I put an add on craigslist trying to get someone I will pay to fix my issue but no luck, please I need help and I will pay u somehow to guide me through this of my exact issue, I was trying to get to rom 2.3 but if it's easier to get back to 2.1 rom then so be it.
PLEASE!~~
Please HELP!
Cheeva316 said:
Please HELP!
Click to expand...
Click to collapse
Got a solution in the making for you, just give me about 30 minutes.
Edit: Maybe 45 minutes lol, sorry i'm testing this before I have you do it to see if it works.
Ok download the following files:
http://www.mediafire.com/?njwqa7axwzyaqgb
http://www.mediafire.com/?f69cl8dc747h0l9
http://www.mediafire.com/?xg8nnqs177xggx4
http://www.mediafire.com/?qxpi5wsx5lzbhbo
http://www.mediafire.com/?4tg67hck7vh1xxs
Edit: Flash the "rootme.zip" first then follow the rest.
Now what you need to do first is extract the "nandroid" file to somewhere you can easily find it.
Now take the folder called "nandroid" along with all the other zip files you downloaded and place them on your sd card. Put your sd card in your phone and power on with volume down+end. Press volume up. Use the trackball to select "Backup/Restore". Use the trackball again to select "Nand Restore". Use it again to select "HT9BGHG01402". Use it again to select "BDS-20110125-0901". Let the restore run, then power off your phone. Turn your phone back on with just the power button, let it run (might even take up to 10 minutes for the phone to start up). Let me know if the phone boots up or not after about 10-15 minutes. This should work and if it does then we can go from there, even to getting you 2.3 if you want.
You might be asking, what the hell is he having me do ? Here's what i'm doing. I made a nandroid backup a few months ago of when I had kaosfroyov39 which is a 2.2 rom. I am going to have you flash MY backup to YOUR phone which when done right, CAN work. Anyway, let me know what happens and remember to give the phone about 10-15 minutes to boot all the way.
Cheeva316 said:
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
Click to expand...
Click to collapse
( Another phone on the precipice of being ruined by someone's cobbled-together "clockwork" recovery. )
If the /system flash memory partition got corrupted in a way that left a lot of pages marked as bad pages, then the /system partition will be "short", and only small ROMs will successfully load into it, if at all. That might be the cause of the above error messages.
But - because you are using Clockwork, there is really no way to know if that is the case, or if you simply have a whole bunch of corrupted ROM files on your SD card. That's because Clockwork does not verify ROM files before it starts flashing them - which allows total garbage to be flashed to the phone. (That's why Clockwork should never be used by newbs).
Here's what I would suggest you do.
- Make sure you are keeping the phone well charged. (Leaving the phone in HBOOT mode will discharge the battery quickly, even if it is plugged in to the charger, BTW).
- Report the exact bootloader version you have - probably 1.47.0000 or 1.49.0000, but it could be something other. Please be precise.
- With the power off, eject the SD card out of the slot and see if you can boot into the normal HBOOT menu with no SD card in the slot. Report your result.
- Boot into the recovery menu and tell us what version # of the recovery you have. If you can determine the details of how your friend attempted to root the phone, that might be pertinent. Again - precise details are valuable; vague hand-waving not so much.
- The Amon_RA recovery has a mode ("USB-MS toggle") which allows you to mount the SD card to the PC. Does your "Clockwork" recovery have this feature, or are you able to put files onto the micro-SD card using a media slot on a PC?
- Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
What I would suggest you do at the moment is to find the SMALLEST Eris** ROM you can find, get it onto your SD card, verify that you didn't corrupt it, and then perform a "wipe data/factory reset" in your recovery and attempt to install it. If you get the same errors as above, then you should definitely NOT try to do a PB00IMG.ZIP or RUU installation. (The current gingerbread ROMs (e.g. GSB v1.4) are pretty small - they only use about 65% of the /system partition.)
I have a flashable "repair" file which might be applicable. It is not a "ROM" per se - it uses some low-level MTD (flash memory) repair techniques, and also flashes into place the original Amon_RA (v1.6.2) recovery, instead of whatever p.o.s. "Clockwork" recovery you currently have on the phone; but I regard it as something which should only be used as a last resort. But - without some more details and testing on your part, I don't feel comfortable about posting it up.
Let me know.
**PS I wanted to ask one more question - this is an Eris we are talking about, right? (I note you were posting in the Hero CDMA forum not so long ago).
Well I want to thank you for replying with such info but it seems that the recovery image file that I reinstalled on the phone was bad cause when it was updating the bar was going up but as it was going through each item it was updating.. I noticed "bootloader in red letters" with I believe saying "error" next to it and then same on another item it tried updating then the phone powered off and now it's dead, tried everything, no charging light comes on, computer (2 different computers) wont reconize it, it's doing nothing at all, I will try to get my hands on another battery but I am broke, but I doubt it's the battery cause I heard with a bootloader error (or damaged) then the phone won't boot up or do anything so I guess the phone is scrap for parts which sucks cause now my friend who started this deal killed my only phone me n my family had, another lesson learned...time to try n sell some stuff on craigslist..damn
Yes it's a Droid Eris...or was! damnnnn...
Again thank you for your help very much appreciated...
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Cheeva316 said:
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Click to expand...
Click to collapse
Well, I am very sorry that this happened to you and my advice to you didn't reach you in time. From the details that you added, I am pretty sure that you indeed have a hard brick.
BUT - the death of your Eris can still help others avoid the same fate. If you can reconstruct the rooting process you went through,
[SIZE=+2]PLEASE LET US KNOW EXACTLY WHAT ROOTING METHOD YOU USED[/SIZE] - and then we can wave people away from it.
When I say exactly, I mean extremely specific: do you still have the download file that you used? If so, push it up to an uploader site and give a link to it. (I think you mentioned unrevoked or something). Do you still have the exact link you used to download that rooting software? Was it Unrevoked? Z4root?
bftb0
I will tomorrow as I saved all the files on my laptop n I am on my pc now, but will do try my best as I am a newb to this phone stuff
Did you try what I suggested or is it too late ?
phone wont do anything so cant do nothing...
Did you find out any more details about the rooting method you used?
might be a couple more days till I can get to it, my laptop is messing up now...all the saved info was on it
I got a gen 8 101IT from a friend. Problem with the device is that it boots automatically in recovery and it won't install any update I've tried.
From what my friend can remember is that he first installed SDE and UrukDroid after that. The device worked fine but later he wanted to revert back to android. So he tried to install an original Archos firmware and the install failed.
I'm not entirely sure what exactly did he do at this point, but it seems that the device no longer has SDE. It boots straight to recovery, where I have the options "ok", "update firmware", "repair system", "format system". What I have tried so far is installing the newest firmware, some older firmwares and the SDE, running "format system" between each try ofcourse. Every update fails with "Update failed: (207)" message. I also tried formatting the internal storage to Ext2 and got the same error. I have redownloaded the firmwares multiple times, and I'm quite certain that I have downloaded the correct versions and have the correct filename.
Has anyone got any ideas what might have gone wrong. I'm wondering if it is possible to brick the recovery in a way that it boots but doesn't flash the rom? Also I was wondering if it's normal that after formatting the device and mounting the internal storage on my pc it's totally empty except for the empty folders "Music", "System" and "Video".
Code 207 is displayed when the .aos upgrade file doesn't pass the signature check.
drain the battery and wait before next try
Thanks for the reply mrbelou, I thought it must have something to do with the signature check. Still it seems a bit weird that it wouldn't pass the check, unless the stored signatures are corrupt. I'll try draining the battery and see if it helps, might even disconnect it for a while so I don't have to wait for it to drain by itself.
Draining the battery and even disconnecting it for an hour or so didn't have any effect. I'll have to start researching and hacking a bit more. Already found some of the reverse-engineered stuff, I'll have to keep researching it more. I already started wondering that if the signature check keys for the .aos verification are in the same keystore as the recovery kernel verification key, yet it still boots the recovery kernel...
ARCHOS 101it Android OS anyone???
kugge said:
I got a gen 8 101IT from a friend. Problem with the device is that it boots automatically in recovery and it won't install any update I've tried.
From what my friend can remember is that he first installed SDE and UrukDroid after that. The device worked fine but later he wanted to revert back to android. So he tried to install an original Archos firmware and the install failed.
I'm not entirely sure what exactly did he do at this point, but it seems that the device no longer has SDE. It boots straight to recovery, where I have the options "ok", "update firmware", "repair system", "format system". What I have tried so far is installing the newest firmware, some older firmwares and the SDE, running "format system" between each try ofcourse. Every update fails with "Update failed: (207)" message. I also tried formatting the internal storage to Ext2 and got the same error. I have redownloaded the firmwares multiple times, and I'm quite certain that I have downloaded the correct versions and have the correct filename.
Has anyone got any ideas what might have gone wrong. I'm wondering if it is possible to brick the recovery in a way that it boots but doesn't flash the rom? Also I was wondering if it's normal that after formatting the device and mounting the internal storage on my pc it's totally empty except for the empty folders "Music", "System" and "Video".
Click to expand...
Click to collapse
I have the EXACT same problem. I made the mistake of leaving my ARCHOS 101it on near a hot wi-fi connection with third party downloads switched on. It downloaded something that totally wiped out all my apps...got an error message "Sorry! the application Archos (app)(process+com.archos.archoswidget)has stopped...etc"
soooo, I copied my files onto my laptop and re-formatted. Now all I see are those three stinking folders just like you mentioned. I was able to install the SDE and get a workable desktop, but can't access the internet. When I followed with trying to update the firmware I got "Update failed: (1)"
I am by no means programming literate, so I have no idea how to find the root /) file or copy the upgrade to the black screen with little tiny white letters in it (I told you I was STUPID). I don't know what "flash" the drive means (tried googling it and got things about flash players) ...so whoever helps me (PLEASE) will have to be quite specific as to what to do. I also don't know what "brick the recovery" means I believe mounting means hooking the usb cable to my pc. What is "flash the ROM" mean and how do you do it.
Am I asking too much??? Jeanie
UPDATE!!!!! After applying sde versions and trying numerous times to re-download firmware, I finally got my aos back!!! Seems I downloaded the newest version using Chrome and it wasn't copying right, so I followed another forum's advice and used Internet Explorer...it worked!!! Now after a week, I now have a "Like New" Archos 101it. What a learning experience!!!
Nice to hear you fixed your problem jeanuhlik.
I haven't gotten anywhere with mine. Can't remember if I tried downloading the firmware with different browser. I've just been researching omap bootloaders and stuff if I get the time to start hacking together something to unbrick the device. It's not worth the time but it's always interesting to learn new stuff.
maybe some help...
kugge said:
Nice to hear you fixed your problem jeanuhlik.
I haven't gotten anywhere with mine. Can't remember if I tried downloading the firmware with different browser. I've just been researching omap bootloaders and stuff if I get the time to start hacking together something to unbrick the device. It's not worth the time but it's always interesting to learn new stuff.
Click to expand...
Click to collapse
I found that if there were several versions of ( firmware_archos_android_gen8.(2)aos)...you HAVE to delete the (2)...then download it into your archos....that's what finally worked for me! I've been playing on it for almost a whole day now!! Be sure and format and delete any SDE firmware you have in there, a format will not get rid of the SDE, but when you open the white screen it should give you Developers tools (or something like that) then you have the option of deleting the SDE.
I hope I have helped, like I said, I know NOTHING about hacking or anything like that, but I guess I just got lucky, I was ready to ship it off to a computer repair shop (we live about 50 miles away from any town that has anything in it)
Best wishes, Jeanie
Hello,
I wish I could explain my problem quickly and clearly, but I lost count on the amount of times I wiped, flashed and reset my Tablet so... I just hope someone comes up with a genius idea, because I'm desperate. I've tried everything.
Today I decided I wanted to try and find a better ROM I could install on my Ainol Tablet, and after doing some research I found out there was a 10.1 version of Cyanogenmod that was apparently quite popular.
I followed a tutorial I found on slatedroid.com (Flashed CM 10.1, Gapps and compatibility file) and only after I found out I just flashed a ROM built for the previous model of my tablet. When I reset it it came up as if it had done a Factory reset (same firmware but everything came up in chinese).
Then I went on and managed to find a tutorial for mine; repeated the process.
Right after doing that I re-read the tutorial (I would love to attach the link but I am a new user and am not allowed to...) and realised I was supposed to update my stock firmware to the latest version before flashing CM on it (apparently so they had the same kernel). Luckily, I had made a backup with TWRP so I went back to it and went looking on my PC for said firmware.
When I managed to find it, I realised the wifi on my tablet was gone. Whenever I switch it on, it goes back off after a few seconds. So no internet.
Then I thought I could just get that update file from my PC and copy it through USB. But that wasn't working either, my laptop will not recognise it whenever I plug it. The tablet won't even recognise a USB flashdrive.
Lastly, I realised there was a miniSD card port so I tried getting the file in through that as well. In this case, the tablet displayed a "preparing SD card" message but nothing happened afterwards...
I'm completely stuck. I have tried several times going back to Factory settings through TWRP, or reloading that backup I made, erasing Dalvik/Cache every single time, but the problems are still there. Everything else seems to be working though...
I did some research and it does look like I flashed a ROM with the wrong kernel so all the drivers are gone... (When the tablet is off and charging it displays a battery that used to stand vertically. Now it comes up horizontally...).
If that was the case, would anyone have any clue on anything I could do to fix it? Any files I could get rid of? Or maybe some secret menu on TWRP I haven't taken into account...?
Any ideas would be extremely appreciated. Please help! :'(
Thanks in advance.
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
Heyhey,
I've been directed here from the XDA-assist forum (so yes, I am quite new here ), I hope that this is the correct place for my questions.
My problem is this:
I have an Huawei Y6, SCL-L21 with android 5.1 (I think it was 5.1, it was definitely 5.something). Following a youtube-video, I tried to root my phone using kingoapp. It said it was successful, but I didn't saw the SuperSu app, so I tried rebooting first. Now it seems that my phone doesn't want to boot up any more :/. I just get the Huawei logo and that's it.
I can still get into the recovery menu (EMUI, the one that was original on the device, access through sound up + power on), so I still have some hope :/. I've tried 'wipe cache partition' and 'wipe data/factory settings', neither helps.
It has come to my attention that reinstalling a back-up from the original rom might help. I, however, do not have a back-up (it will be the first thing I will look for when I get my phone working again though).
I have been searching for a stock rom, or even an custom rom that I could use to get my phone working again.
I've found a site with a custom rom that was supposed to work for my phone, but when I try it by putting the dload folder on an external (32G) SD-card an powering up my phone by pressing sound up + down + power on, I get 'Software install failed!', so apparently that is not of much help :/.
So what I wondered now, most importantly, Is there a way to get my device working again?
And also; What could be the reason that the installation of a rom fails? Could it be something I'm doing wrong? Can it be that it still needs an OS installed and that it is actually more of an update instead of a new OS? Can there be something wrong with the SD-card(wrong formatting or whatever) ?
And off course; if I can only get my device to work again using a rom; Is there a place known where I could find/get stock or custom rom's?
Any help would definitely be appreciated!
Kind regards,
Ilja_B
OK! So, I have found the factory ROM and was able to get my phone to work again ^^
I've put it on the SD-card and booted my phone the way I explained above. So apparently there was no problem with my SD-card.
I wanted to post the link here as a reply in case anyone else needed it, but apparently I can't post links :/
Does anyone has an idea where a good place would be to post this, so others might also benefit?
Grtz,
Uplad to google drive
i have the same problem help me please
I've found my ROM on the bottom of this page here [1] under the 'download'-tab. From the name of the file I get that this is for the Huawei Y6 SCL-L21 for Germany, Italy, Netherlands, Belgium, Portugal and others. Hopes this helps, or at least gets you on your way to find the correct ROM for yourself. You should find a proper explanation on how to install the ROM online.
[1] http://m.huawei.com/bemobile/consumer/mobile-phones/detail/huawei-y6-benl.htm
thanks but i already downloaded it but didn't work