Well it all started when I downloaded Boot Animations ★ root. I tried to install a bootanimation and it said failed. Thinking nothing happened , I had to restart my phone. Now my phone bootloops with an android bootanimation. I tried factory reset and that didnt work. I tried adb sideload and it would just say installation aborted. I have the system backed up on my laptop. Help... please?
Well.. Power +Up Button =recovery but Power+down button= testing (its in chinese)... how do I get to bootloader?
Go to android recovery,
Format system, wipe cache, go to advanced, wipe Dalvik cache, reboot.
If that doesn't help, try slamming your phone through a piece of China brick, see if it helps.
Sent from my LG-E730 using xda app-developers app
terris98 said:
Go to android recovery,
Format system, wipe cache, go to advanced, wipe Dalvik cache, reboot.
If that doesn't help, try slamming your phone through a piece of China brick, see if it helps.
Sent from my LG-E730 using xda app-developers app
Click to expand...
Click to collapse
LMAO Well.. The only way to get my phone back working is through Preloader but it connects and disconnects. I tried different cords and computers but nothing worked. It's really a big mistake I did. I should have installed a custom recovery and did a backup right after I rooted my phone.. Anyways.. I'm getting a different phone soon.
Chinaphone wont boot
Thanks to xda for all the help and I hope you can help me with this problem. My Chinaphone won't start, it gets to the android boot animation and sound but then nothing. The led comes on from the time the battery is inserted which is unusual.
I have the phone for about one year now, model:M-9125 (imitation of htc hd7) with dual Sim+TV and everything else that come with Android 2.3.4 gingerbread. The phones is rooted (with the MT6573 driver- and i use link2sd so everything except un-updated system apps are on the second partition. I have modified the rom with link2sd removing unwanted system apps like email, flashlight, music, browser and replaced them gmail/outlook, tinyflashlight, winamp, opera mini respectively. Tinyflashlight and opera were made system apps. I also use the go launcher which I made a system app after which I was left with only 1.5 mb of rom, (ram about 300 mb and both sd card partitions have over a gb free) but the phone worked fine. Then a few days ago the phone wont start. I thought the battery was dead but it could not charge. I tried both batteries (came with two, one of which was already drained) and they would not charge. So a friend took them to charge with a universal claiming that I Let the batteries drain out completely that's why. However I have the batteries I think they are charged cause at least now the led comes as soon as the battery pins contact those of the phone. The phone turns on, boot animation, sounds but then nothing. So I just wanted to know if its the batteries or if its the phone given that I have over-customized it. And how do I fix it.Cannot afford a new phone right now.
I know I am a noob and read your rules but I still really wants sure where to post this. feel free to move it if necessarily. thank you.
Related
hey all,
on friday I rooted my NS again to check out cm7 rc1. before i was totally stock @ 2.3.2. friday evening i wanted to show my iphone friends the nexus s with cm7. the first one took it and did take some photos. then he smiled and gave it back to me. force close: SORRY: Android.process(???) has stopped unexpectedly.
this error was looping all the thime. i pressed okay and one sec later it was there again. i tried to flash the rom again in recovery, but the error was still there. i did date and cash wipes and some factory resets and then the error was gone.
on sunday i was travelling home on train and suddenly the error was back. i tried again some wipes and then i deceided to restore my nandroid backup. so i was back on 2.3.2. during sunday afternoon and evening i got these errors:
- NS is freezing while it is in standby... if i grab the phone and want to unlock it but the display keeps black -> i have to put out the battery..
- NS is beside my keyboard and suddenly all four buttons are on. display is still black. unlock not possible--> battery again
- NS is freezing while using facebook or twitter app
today... i unrooted it again and went back to a nandroid (2.3.1) guided _here_.
after unrooted again NS wanted to update to 2.3.2 which i confirmed.
about to hours later the errors i explained came back.
am i the first one who bricked NS?
please give me some help how to get it back working correctly, because i love this phone so hard.
I did another factory reset and now the phone is hanging at the google Logo. The four buttons are powered.
This is looping, too.
Yesterday I tried some things to kill these errors. I did:
- factoy reset (in settings menu)
- fastboot erase userdata 2x
- wipe cache, wipe data, wipe devliak
Today the phone was with out a problem, but just a moment ago I wanted to unlock it by pressing the power button but the display didn't react as usal. It is still black and the only thing I can do is to take out the battery....
Last step I can do is to send it back to my girlfriends sister in US so that she can bringt it to Samsung US to get it serviced.
"bricking" the phones involves the phone not being able to turn on or do anything, period. your phone isnt a brick. after doing a "factory reset" you want to reflash whatever rom you are using. it seems like youre having problems with a bad app or some bad data.
thx simms22. i just flashed the newest cm7 nightly with rom manager (incl. wipe). i set up all my apps and 20 min later the error come.
to figure out if it is a bad app problem i do a factory reset now and won't log into google account and see if the error appears.
simms22 said:
it seems like youre having problems with a bad app or some bad data.
Click to expand...
Click to collapse
i did a factory reset and skipped google setup after first boot.
i just entered sim code and let nexus s in idel mode.. about 15 mins later the four buttons were lightened but i couldn't unlock the phone. battery out... and i could power it on.
so it's some kind of bad data problem? but how to find and/or clean this bad data? thx again for your help.
edit: I found a lot on google for "full wipe bad data". I'm reading now! But I may have to ask you something
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. then i mounted usb and copied this nandroid 2.3.1 to it and flashed it. I booted and installed system update 2.3.2. now testing again without apps.
edit3: the hole day no problems. I only installed twitter and in the evening 2.3.3 manually. This morning again the phone was not unlockable. I had to take out the battery... on my way to work I did a wipe from stock recovery but shortly later the phone freezed while I used the slider to unlock it. oh man that sucks I thought it was fixed.
I make some coffee now and start google'ing. If you have some tipps, please throw them to me.
maybe reflashing radio?
stiefa00 said:
i did a factory reset and skipped google setup after first boot.
i just entered sim code and let nexus s in idel mode.. about 15 mins later the four buttons were lightened but i couldn't unlock the phone. battery out... and i could power it on.
so it's some kind of bad data problem? but how to find and/or clean this bad data? thx again for your help.
edit: I found a lot on google for "full wipe bad data". I'm reading now! But I may have to ask you something
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. then i mounted usb and copied this nandroid 2.3.1 to it and flashed it. I booted and installed system update 2.3.2. now testing again without apps.
edit3: the hole day no problems. I only installed twitter and in the evening 2.3.3 manually. This morning again the phone was not unlockable. I had to take out the battery... on my way to work I did a wipe from stock recovery but shortly later the phone freezed while I used the slider to unlock it. oh man that sucks I thought it was fixed.
I make some coffee now and start google'ing. If you have some tipps, please throw them to me.
maybe reflashing radio?
Click to expand...
Click to collapse
are you using any of the custom kernels?
no, I'm using stock kernel and never flashed a custom kernel.
stiefa00 said:
no, I'm using stock kernel and never flashed a custom kernel.
Click to expand...
Click to collapse
im going to have you try wiping once again. wipe data/factory reset. only this time reupdate to android 2.3.3 right after the factory reset in recovery. dont boot after wiping, update after wipe, then reboot.
--> stock recovery -> wipe / factory reset -> reflashed update (ota2.3.3) -> testing now without installing apps
thanks simms!
Edit: the phone got a freeze while I wanted to unlock it -.-
Edit2: I'm testing now in airplane mode. Maybe the error doesn't come...
stiefa00 said:
--> stock recovery -> wipe / factory reset -> reflashed update (ota2.3.3) -> testing now without installing apps
thanks simms!
Edit: the phone got a freeze while I wanted to unlock it -.-
Edit2: I'm testing now in airplane mode. Maybe the error doesn't come...
Click to expand...
Click to collapse
im now thinking it might not software related. if it was software, a wipe and reupdate should have fixed it. maybe you should check into a warranty replacement. .
In airplane mode the error is there, too.
Okay thx 4 ur help. I'm starting a service request. Bad day -.-
Sent from my Nexus S using XDA App
stiefa00 said:
In airplane mode the error is there, too.
Okay thx 4 ur help. I'm starting a service request. Bad day -.-
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
the only other thing i can think of that might cause something like that after wiping is something bad on your "sd" storage. copy everything you need off your "sd" storage and try wiping that.
stiefa00 said:
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. Then nandroid restore...
Click to expand...
Click to collapse
I think I allready did this? Or do you talk about this 1gb sd. If so, how to format this one?
Could I find something usefull with logcat?
Sent from my Nexus S using XDA App
According to this thread I think you will have to get it replaced:
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=44db6d8e31129d4c&hl=en
Holy sh** what an anoying link. -.-
BUT: thanks dude.. now I know waaazzz up
So here is a quick rundown of what happened:
-DL Beats audio, opened it, it was supposed to restart my phone, but it froze it.
-Could not power off or reset it, had to pull battery
-Was then stuck on the 4G LTE rainbow and would not load. Tried pulling battery nothing.
-Went into recovery mode and tried loading, nothing happened and I read someone say the only way out of it was to wipe everything and start over, so I wiped Data and Cache and Dalvik Cache with Clockwork. Nothing happens.
-Finally I Odin it supposedly back to stock. Hooray I can get into my phone, weird thing is all of my apps are there, email is set up, contacts are there with pics from FB, syncmypix, etc. It even retained the fact that I had disabled the stupid ongoing Wi-Fi notification. Just the homescreens are blank again.
-I never made a CWM backup, I think I made a Titanium backup, I know I used MyBackupRoot (the one that is a life preserver). That being said I thought I wiped everything in CWM. It said it had formatted the internal and external SD.
Question is should I go ahead and try to wipe everything clean again?
Am I going to run into issues using my phone how it is?
Should I back it up and then load a recovery from this or would that be pointless?
Or do I leave it alone and consider myself lucky?
Thank you and by no means am I a developer or anything, just getting back into android after 2 years on iOS and apparently know just enough to get myself into trouble.
If everything is working fine then you sgould be good. You must haved had the restore thing checked or verizon backup crap restored your stuff. When you odin that will flash the file system img so there is no way that your data survived
Did you check the md5 on the beats audio thing before you flashed it? Cause i have ran that fine.
Sent from my CleanRom'd Galaxy SIII
Can anyone suggest a troubleshooting method without a factory reset. This is what I am experiencing:
Everytime I reboot the Sensation will boot up and go through the normal process. About 3 or 4 minutes it will just reboot. Often when this happens I note that I don't have to re-enter my pin (a clue?). This rebooting will go on repeatedly but eventually (if I leave the phone alone) I will at some point end up with the phone up and running.
There are no random reboots, it is only this situation that causes the problem and it's obviously some point 3 or 4 mins into the process that is causing the problem.
I've noticed that if I reboot to recovery and then select reboot from there it is usually successful.
I am s/off via wire trick method, and rooted. recovery is 4 ext and I am still on stock rom.
I'd like to find out what is happening at the point of the reboot, is there a good way to do this?
louiscar said:
Can anyone suggest a troubleshooting method without a factory reset. This is what I am experiencing:
Everytime I reboot the Sensation will boot up and go through the normal process. About 3 or 4 minutes it will just reboot. Often when this happens I note that I don't have to re-enter my pin (a clue?). This rebooting will go on repeatedly but eventually (if I leave the phone alone) I will at some point end up with the phone up and running.
There are no random reboots, it is only this situation that causes the problem and it's obviously some point 3 or 4 mins into the process that is causing the problem.
I've noticed that if I reboot to recovery and then select reboot from there it is usually successful.
I am s/off via wire trick method, and rooted. recovery is 4 ext and I am still on stock rom.
I'd like to find out what is happening at the point of the reboot, is there a good way to do this?
Click to expand...
Click to collapse
boot into recovery and wipe dalvik cache n then do a normal reboot n check wad happens
you can also make a nandroid backup n install a custom and check wheather the problem exisit by doing backup ull not loose ur data n u can return to stock again just by restoring the backup ... try and let me know
louiscar said:
Can anyone suggest a troubleshooting method without a factory reset. This is what I am experiencing:
Everytime I reboot the Sensation will boot up and go through the normal process. About 3 or 4 minutes it will just reboot. Often when this happens I note that I don't have to re-enter my pin (a clue?). This rebooting will go on repeatedly but eventually (if I leave the phone alone) I will at some point end up with the phone up and running.
There are no random reboots, it is only this situation that causes the problem and it's obviously some point 3 or 4 mins into the process that is causing the problem.
I've noticed that if I reboot to recovery and then select reboot from there it is usually successful.
I am s/off via wire trick method, and rooted. recovery is 4 ext and I am still on stock rom.
I'd like to find out what is happening at the point of the reboot, is there a good way to do this?
Click to expand...
Click to collapse
Hi,
Have you installed a new ROM recently?
Did you fully wipe the phone before you did this?
If not,try re-installing the ROM you are on.
No wipes.
You will not lose settings or data.
shrex said:
boot into recovery and wipe dalvik cache n then do a normal reboot n check wad happens
you can also make a nandroid backup n install a custom and check wheather the problem exisit by doing backup ull not loose ur data n u can return to stock again just by restoring the backup ... try and let me know
Click to expand...
Click to collapse
What I noticed is that the problem didn't exist when rebooting from ADB or fastboot either.
Anyway your suggestion so far looks promising. I've tried a normal restart from the phone and a battery change both of which would usually end up with the rebooting problem. Both of these tests haven't caused it so I'll keep testing but thanks for the suggestion.
What is does the Dalvik cache do and how would this have caused this kind of problem? I'm interested in the whys. The problem appeared soon after installing a couple of things as I remember and I did try to backtrack without much success.
malybru said:
Hi,
Have you installed a new ROM recently?
Did you fully wipe the phone before you did this?
If not,try re-installing the ROM you are on.
No wipes.
You will not lose settings or data.
Click to expand...
Click to collapse
No I've not installed any Roms, I'm on stock.
Revived thread - as it's happening again
I'd like to revive this thread - perhaps I should post a new one but since it's here ...
This problem has returned with a vengeance. It took me about 3 hours of fighting to get this phone to stop rebooting. It seems clearing the dalvik cache isn't a solution anymore (if it was in the first place).
What I've observed is that if I take the sd card out it doesn't reboot. When the card is in I have several shortcuts on one of my home screens which often will not refresh for ages (ie. android icons for anything moved to sd card). When the icons start to appear the reboot will happen shortly after. All the time I'm waiting for this to happen the phone is very sluggish.
I don't think this is an incompatible sd card but maybe it is, however, if I can get this to stop rebooting then all is ok till I attempt another reboot.
Ideally I'd like to track this down to find out if there is an app which is misbehaving. Are there any tools that can help me do that.
Any suggestions would be most welcome.
Backup all your data and do a factory reset
This problem might be due to 3rd party app as you phone without sd card dosent reboots
Might be some of ur app is seriously miss-behaving
After a factory rest install each app n check ( I know it's time consuming)
Hit thanks button if you find me helpful
sent from amazing HTC sensation using xda premium
shrex said:
Backup all your data and do a factory reset
This problem might be due to 3rd party app as you phone without sd card dosent reboots
Might be some of ur app is seriously miss-behaving
After a factory rest install each app n check ( I know it's time consuming)
Hit thanks button if you find me helpful
sent from amazing HTC sensation using xda premium
Click to expand...
Click to collapse
Yeah hoped to avoid that for 2 reasons. 1) It's a bummer 2) I won't know what the problem was / is.
I did do a factory reset after backing up data via my recovery. It seemed to be ok but I had nothing on SD at that point. I loaded a couple of apps and moved them to sd and it still didn't happen. The I restored the data and it was back to the same problem.
I may have to go with your suggestion but I'm going to lose some data as I can't back up selectively (so it seems).
Is there a logger I can use that starts at reboot. If I could find out exactly what it's doing when it decides to reboot I might nail the app?
louiscar said:
Yeah hoped to avoid that for 2 reasons. 1) It's a bummer 2) I won't know what the problem was / is.
I did do a factory reset after backing up data via my recovery. It seemed to be ok but I had nothing on SD at that point. I loaded a couple of apps and moved them to sd and it still didn't happen. The I restored the data and it was back to the same problem.
I may have to go with your suggestion but I'm going to lose some data as I can't back up selectively (so it seems).
Is there a logger I can use that starts at reboot. If I could find out exactly what it's doing when it decides to reboot I might nail the app?
Click to expand...
Click to collapse
hi
greetings
to find the problematic app might go tough you will have to install each and every app and check after that
try installing all the trustworthy apps before eg. file manager,fb,twitter,gmail etc then check once again ,after that install single app at a time
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
SELind01 said:
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
Click to expand...
Click to collapse
thats defiantly not normal. you should wipe everything 100% clean and start over, also updating your recovery to the latest version. during the wipe process make sure you wipe "data-media-/sdcard" too (NOT external sd, unless you want to and have things backed up).
also, its extremely bad for the battery to let it run down to the point where it shuts off. its only a matter of time, repeatedly doing that, before you plug it in and it will not charge no matter how long you leave it on for.
bweN diorD said:
thats defiantly not normal. you should wipe everything 100% clean and start over, also updating your recovery to the latest version. during the wipe process make sure you wipe "data-media-/sdcard" too (NOT external sd, unless you want to and have things backed up).
also, its extremely bad for the battery to let it run down to the point where it shuts off. its only a matter of time, repeatedly doing that, before you plug it in and it will not charge no matter how long you leave it on for.
Click to expand...
Click to collapse
When I am installing a new rom I wipe Dalvik Cache, System, Data, and Cache each three times and then I also Format Data Three times. Is this what you mean my wipe everything 100%?
Also I am currently running TWRP v2.5.0.0, I have found a newer version on twrps website but when I go into Rom Manager and check for updates my phone does not come up as a possible clockworkmod Recovery?
SELind01 said:
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
Click to expand...
Click to collapse
In all likelihood, this is not a LiquidSmooth issue. I would suggest a clean install as the previous posters suggested. The latest stable version of LS is now at v2.10 for Android 4.3
LS 2.10 must be installed as follows, according to the devs:
New Flashing Instructions
wipe data/factory reset
wipe cache partition
wipe dalvik cache
format /system
Install ROM, NOT GAPPS YET!!
Reboot system, first boot may take a few minutes, don't panic ;-D
Setup your phones settings, anything that isn't Google related
or let your phone sit for 5 minutes
reboot back into recovery
wipe cache and dalvik
then flash gapps
reboot and enjoy
Click to expand...
Click to collapse
For the xt926, the download page for LS 2.10 is here: http://d-h.st/users/jsnweitzel/?fld_id=15202#files
gapps 8/13 or newer are supposed to be used with this ROM. dl from here: http://d-h.st/users/jsnweitzel/?fld_id=21058#files
The official ROM page is over at G+ https://plus.google.com/u/0/communities/117452480298315341829, if you have any additional questions.
Give it a whirl, and let us know what happens. Good luck.
SELind01 said:
When I am installing a new rom I wipe Dalvik Cache, System, Data, and Cache each three times and then I also Format Data Three times. Is this what you mean my wipe everything 100%?
Also I am currently running TWRP v2.5.0.0, I have found a newer version on twrps website but when I go into Rom Manager and check for updates my phone does not come up as a possible clockworkmod Recovery?
Click to expand...
Click to collapse
you are wiping very well, i was just confirming you wipe everything possible short of the external sd.
the wipe im talking about in twrp is wiped when you wipe "data", the one where you have to type "yes" before it will wipe. in cwm, in the formatting section (i forget what its called), there is an option that specifically says "data-media /internal sd" or something close to that.
as for the latest recoveries, here is a tool by Tucstwo that i have been updating lately http://www.mediafire.com/download/2o061zcmzlaycb5/Razr_HD_Recovery_Flasher_V8.rar
also, twrp 2.5 doesnt have all the selinux bugs worked out, you need 2.6.3.0, which is in the above utility.
Hi.
I installed some dodgy app which required root access to operate (but it didn't even though I allowed it in SuperSu) and this is where my problems started.
First of all, I noticed each and every app I tried to run would immediately crash. That included system apps, such as the Settings app. At that stage I was left with only the launcher working and attempts to uninstall apps would also cause a crash. Even the shutdown menu was broken and the phone hung up so I was forced to reboot it by holding the power button for 10 seconds.
After that, the phone would no longer be able to boot, it was stuck in a boot loop, but recovery still worked (TWRP for that matter) so firstly I wiped the cache partitions (including dalvik cache) but that didn't help, as the phone still wouldn't boot. In this case there was only one thing left for me to try and that was the factory reset capability of TWRP which claimed to not even touch internal storage so I was fine with that and did the wipe.
Thankfully, the phone booted afterwards and it welcomed me with the first startup guide (the language selection dialog was really buggy but that's Huawei's fault) and the phone was seemingly ok, except that the whole internal storage had been wiped out but not only that - the external microsd card was empty as well! Could you believe that? I couldn't. TWRP promised not to touch internal storage and the external memory card wasn't even mentioned but why would it wipe it anyway?
That's for the story behind it, now for the actual problems I'm facing right now:
The stock remote app is gone
The boot animation has changed to a different one (now it's a silver "android" logo instead of the "honor" logo)
Battery usage stats are not available (see: http://i.cubeupload.com/BXCknW.png)
Sound quality from the built-in speaker seems noticeably worse
Hereby, I'm asking you guys to help me out with all of this.
The "remote app missing" problem could be solved by someone sharing their apk file with me, that's probably the simplest one to fix.
As for the boot animation, I have no clue as I don't even know what files are responsible for that.
The same for the battery stats problem, I'm already through a couple of full-charge-to-discharge cycles as well as wiping the cache partition, but the problem remains.
The sound quality probably has to do with the DTS sound enhancer. The config file for that is either "/cust/unicom/cn/xml/dolby_config.xml" or "/cust/unicomelectric/cn/xml/dolby_config.xml" and I'm asking you to upload these files somewhere so I can compare them with mine to see if anything is different.
The device I'm using is the H60-L02 variant running the B532 ROM.
Does the 3 buttons method erase internal storage as well? I've already set up quite some apps and having to do it again wouldn't be the most pleasant surprise. But at least in this case I could make some backups and whatnot...
Also, would it work if I flashed B535 straight away or does the 3 buttons method expect the same version which is already installed, in this case B532?
pudup said:
It will wipe internal storage. You can flash any *full* ROM as long as you're not moving up or down from kitkat-lolipop/marshmallow.
Click to expand...
Click to collapse
Okay, so I decided I'd do the whole thing today. I downloaded the full B535 ROM on my PC, backed up all the stuff I care about from the phone to the PC as well, and also I downloaded the MultiTool.
Though the MultiTool thread says this in bold red:
VirusPlus said:
EMUI 3.1 WARNING! Update over rooted or system modded in EMUI 3.1 gives a BRICK.
You have to restore system and REMOVE root before every update in EMUI 3.1 for now.
Click to expand...
Click to collapse
So I also fired up Titanium Backup in order to defrost all the frozen apps, which went fine, and then I wanted to unroot the phone but I've been unable to do so so far.
To unroot, I launch the SuperSU app, navigate to the "Settings" tab and select "Full unroot". The problem being, it just gets stuck on the screen saying "Uninstalling, please wait...". I don't know how long it usually takes to complete, so far I've waited for maybe 10 minutes and nothing seems to change. Should I care about that? Is that warning about updating rooted/modified EMUI 3.1 resulting in a brick still true?
Can I skip this step and just flash the stock recovery followed by the 3 buttons method?
EDIT:
After some trial and error with the multi tool and different recoveries, I was able to finally unroot. Next, I flashed the stock recovery for B532 and attempted to do the 3 buttons method, but it would say "Install failed. The update package does not exist" (could be because I'm doing the update from a USB flash drive as I don't have an micro sd card big enough to fit the package). So I rebooted the phone into system and used the Updater to perfrom a local update where it would let me pick the USB drive. It completed without errors and then rebooted into some kind of updater (black background and some bluish emui colors) where it also took some time to finish thankfully successfully. I can right now see the phone booting and for what it's worth, the boot animation is once again the good old "honor" logo and not that ugly silvery "android" one
And now it's "Optimizing system...". I really hope it finsishes successfully as it's already a bit late here and I wouldn't like the phone to be unusable tomorrow :laugh:
36% ready...
46% it's kind of fun to watch this, and now 49%
I'd like to thank @pudup once more for helping out, I'm not really that much into flashing recoveries, roms and all that myself. Without your help I would probably be too scared to try doing something on my own :crying:
86%, 89%, 95% and 100%. Aww, what a relief Good old stock lock screen and wallpaper.