Related
Hey good people, after an entire day of trying to tinker with my phone, I soft bricked it.
It started because I wanted a theme, that required CM. So I've browsed a lot of threads and tried some things, and a couple of restarts and factory resets later, it went downhill.
So, P760 20i, running stock 4.1.2, after the last factory reset, I rooted it using this tutorial. I did that in order to install this CWM, to further install CM 10.1, the one I needed. After I did all that and finally booted up in recovery mode, I wiped user data as per instructions in the last link, and when trying to install the ROM, an error felt the need to interfere with my plans. So that's how I ended up with a phone that, if I don't take 3 more pills now, I'm gonna give to the dog to chew on.
It powers on, passes the LG logo, after the screen goes white and it says Under Coding...and the only option is a button to Reset Phone (it's basically a restart phone). A pop-up immediatly appears, saying that com.android.phone has stopped. After I click OK on that it asks for my SIM PIN, it accepts it, and briefly shows a weird, low-res old-looking Android lock screen and then back to the blank screen with another pop-up, asking me about Mobile Networks. That's about all the interaction there is. Click Home button does nothing, clicking Back button just swipes the screen back on the screen, and Menu does nothing. Rebooting from that button is again useless.
That CWM is still there, I can access boot in recovery mode, but to no avail. I've wiped cache, wiped Dalvik Cache, rebooted and nothing. I've tried hard reset with vol down+home then power for 3 secs, release power but still hold down vol down+home until the friendly robot appears, but the result is the same, nothing happens.
During the day I went through more methods, I had a lot of trouble with fastboot which I couldn't get to work.
My question is, based on what I told you, can you instruct me in the right direction ? Also, now that this happened and if it's possible to fix it, could it be fixed with CM installed automatically, or will it be a stock reset and then again back to the drawing board ?
If you need any more details, I'll try to provide, I didn't do much after the last factory reset except for what you see here.
@nerazull Welcome to the forums.
I guess first things first.... With this device you cannot flash any custom roms without unlocking the bootloader first. You cannot flash any custom roms with this version of CWM recovery either and there is no work around for the bootloader such as loki.
When you installed CWM did you make a nandroid backup? I hope so.... this is always, always the first thing you do before making any changes to the system.
If you did then just boot into CWM and restore your nandroid backup and that should resolve your issue.
If you didn't perform a nandroid backup then you can try and flash one for your specific device (p760 jb) from cmahendra's nandroid thread here - http://forum.xda-developers.com/showthread.php?t=2136204
If the nandroid backup doesn't work then you'll have to follow cmahenda's unbrick guide by either using the offline or online flash here - http://forum.xda-developers.com/showthread.php?t=2085344
@xdrc45 Well, I didn't perform any kind of backup, I usually don't (call me an optimist ...I'm actually sad now )
I woke up earlier and started reading the second topic you posted. I'm thinking about trying that and not the first one, since I see the first one MAY have some personal data, I would prefer a stock option.
The question is, does it matter that it was 20i before, must I find a 20i now, or can I take any other one ? Or any other one respecting country/provider ?
Also, the first one says that device must be rooted. Is it still rooted now, with the method I used and after the incident ?
I also tried a couple of ways to unlock the bootloader yesterday, best result I got was a phone restart but nothing different. I also couldn't find a way to tell if the bootloader was unlocked or not.
PS: Thanks for the welcome
The nandroid backups are clean as in stock, rooted and all personal information is removed.
Personally i would try the nandroid backup firsr as that would be the fastest way to restore your device. Take a total of 5 min to try and yes the device should still be rooted.
My L9 had the same problem after I installed the L9 Recovery, I booted into CWM and made a backup and then when I rebooted to the OS I got the error Encrypting - Reset Phone. Booted back to CWM, restored my backup and everything was fine... turned out to be a problem with BusyBox.
For the kdz you only need one that is for your model# and that is the same version of OS that came installed on the device (ics or jb) for the offline flash.
When you successfully unlock the bootloader you will be taken to a verification screen to actually unlock it. Its a huge pain to achieve. What you can do one you restore the device and make a nandroid backup is
1. Install a launcher lile Apex or Nova
2. Install xposed framework
3. Inatall gravity box xposed module
4. Install xthemes xposed module
All the above allow you to make custom changes from the status bar to kk themes
Ok, I will take your advice and try with the backup first.
And btw, that's the same error I get, I said "Under Coding" because that's the word-by-word translation from my language, didn't think of "Encrypting"
In regards to the theme part, that's what I originally did. I found the same version of the theme I wanted as an XTHEME. I followed the instructions of the developer on the play store. I rooted using the same method I mentioned in OP, got the XPOSED framework, got XTHEMES Engine, got the theme, but it wasn't working as intended. The theme only changed a couple of icons and the battery icon, it was like 20% of what the screenshots on the play store were showing. It also had something resembling 256 colors in the drop-down menu.The comments and rating of the theme made me think that the problem was on my end.
I found the same theme that had another application method, and required one of these: CM10.1, CM10, CM9 ,AOKP and Paranoid Android, so I decided to try this one with CM10.1, maybe it wouldn't glitch.
Sadly, there were no reviews of the theme for my device, so I couldn't tell if it was a problem with this specific device+that theme.
I can't post outside links due to being new on the forums, but the themes I'm talking about can be found in the Play Store, search term "Deus Ex Android Blue", the first two should be Custom ROM one and XTHEME one. Maybe you have some insight.
PS: I see that you also have this device, albeit 769, and it's the only one with stock ROM on it. I'm not a very experienced user, should I still pursue bootload unlock+custom ROM ? Is it too much of a hassle ? I'd like to do it and not just for the theme (it's the main reason though), if I fix the current problem.
I found 2 methods that used adb/fastboot for unlocking, got Android SDK, adb worked fine but I couldn't do anything about fastboot. I also tried that method (I think "Lelus"), where you had to remove battery, plug in phone like that, "catch" the device and manually install it's driver, etc, but I didn't fully understand what to do there. I only did the first part. There was another link to a tutorial about this method, spanning 3-4 methods, and I saw it's pretty random, and my USB cable is also not very reliable, if I move it by just a bit it may interrupt the connection.
LE: I'm sorry I can't quote all the methods I tried yesterday so you can better respond to me, but I can't even remember all...at one time I had 20+ tabs on the subject, bookmarked a few, tried some, ran into scam websites claiming they had a good method, etc.
And one last thing (sorry for this wall of text reply ), you said this CWM I got can't install Custom ROMs, but can it flash the backup I need ?
@nerazull
See the thing is that using something like xposed framework modules, is that it literally makes changes to the framework and the phone just might not like one of those changes. Sometimes it won't apply all the way across the system and you may only end up with only 20% of the theme working because some of the themes were originally cm10+ themes ported to xposed and may have been developed for a specific device and isn't a 100% compatible or a bad download. Usually if it causes any problems you can just uninstall the module and reboot and everythings fine, if not that's where a backup comes in handy.
I haven't tried to unlocked mine yet, just because I really haven't had the time to spend a day flashing kdz and dealing with the inverted touch screen. I plan on it one of these days, I've already downloaded everything for the device to do it and even have fastboot already set up just in case. So yes you could say it is a pain to unlock the bootloader, but I'm pretty sure more people have been more successful at unlocking on the p760 than on other variants.
Fastboot is actually pretty easy to set up. Open device manager and open lelus fastboot script, minimize the fastboot script windows so you can see them both fully open on the screen. Turn off the device and remove the battery and keep it screen down on a flat surface, plug your USB cable into your PC not into the device yet - select #1 for fastboot - push any key to continue - quickly plug in the USB cable into the device and and put the battery back in - on device manager you will see "unknown device" pop up and right click on it quickly and select update driver - select manually install the driver - then navigate to where you have the fastboot diver folder and click on "usb _drv_windows" and install - once that's done repeat the process again to install the drivers again.
Yes that cwm version will flash the nandroid backup and mod zips.
One other thing you can try is apex launcher, that's what I'm using. With this you can change a lot of the launcher settings, change and edit the size and image for icons and folders to adding themes, I'm using kitkat HD multi launcher theme through apex and its really nice and clean.
I haven't tried it yet but you can also try themer beta
@xdrc45 Well, I managed to install a backup from your first suggested method and it worked fine. I also tried Nova Launcher for a bit, bit I just got my mind set up on that theme and it's not going away I've also managed to install the fastboot drivers using the Lelus method (don't know why, but your instructions here made much more sense to me then the other 2 I found )
I decided I still want to pursue unlocking the bootloader and installing CM 10.1, I really want to check it out.
Will this BL unlocking method work for me ? I couldn't find any mention of 20i in the thread. And if yes, can that CWM flash a custom ROM, unlike my current one ?
And of course, thanks for your help so far. Really appreciate it.
@nerazull Hey you're welcome.... glad I could be of help.
I don't think v20i is unlockable, you could try and issue the unlock command but I'm pretty sure you will have to flash to a European open kdz like v20b and then follow the tutorial and yes that CWM will work.
You could also use markolino631 Tool box to try and unlock the bootloader. It issues the unlock command and can flash CWM for you easily ... There's a CWM for cm10 and the new version has one for cm11.
http://forum.xda-developers.com/showthread.php?t=2190326
I'm surprised you're going for cm10.1 instead of cm11
@xdrc45 Well, I did try to unlock 20i with the method I mentioned but it didn't work, I decided to flash v20b europe open. I flashed v20b Europe Open (just got the kdz from there, didn't follow those steps, didn't go back to ICS) using offline method (had to hard reset after because I was stuck in a bootloop, it worked fine after). I've got the fastboot drivers installed like I said before, I've checked and they're installed correctly. I've also installed/uninstalled the LG drivers twice, once offline to make sure Windows doesn't search for updates, and I still can't unlock bootloader. I've tried both unlocking methods aforementioned and the phone just reboots normally.
I've made these screenshots of what my Device Manager looks like, just for the sake of being thorough.
In phone, Software Version now says P76020b. Could the problem be here, shouldn't it say EUR-something ?
And I'm going for CM 10.1 for that theme, if it works and I like it I'll make a backup and get CM11 and see if they're compatible or not and move on from there That is, if I can get this bl unlocked.
LE: In the [2in1GUIDE] there's this post that mentions BusyBox. My device is not rooted after the kdz flash and obviously I don't have BusyBox. But that wouldn't make sense since it's not a pre-requisite in the tutorial and the tutorial is also meant to root.
There's also this...and this confuses me even further + other random occurrences.
Is it safe to assume that I should start experimenting ?
Yeah these L9's can be a pain in the @ss, but the nice thing is you can recover it from almost anything.
Just keep trying and don't give up on it. I've seen where some people have tried multiple times to unlock, like 20 times without success and then they try again and boom, unlock success. Make sure you have and are using the phones service and wifi. Make some calls and watch some videos or a movie on it.... You need to receive the token, this is the whole reason for waiting an hour before issuing the unlock command, but it may take longer than an hour or two to receive it, like some waited 10 hours and then the unlock worked.
Unfortunately there is no one set way to unlock and everyone has had different experiences and tried different techniques to get it to work. All you can do is, as you said "Experiment" and exhaust all options.
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
boneyarsebogman said:
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
Click to expand...
Click to collapse
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
es0tericcha0s said:
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
Click to expand...
Click to collapse
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
es0tericcha0s said:
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
Click to expand...
Click to collapse
I've wiped the Caches and Dalvik Cache and can't seem to find "Fix Permissions". I did some searching and it seems this feature was removed from CWM? I'm running v6.0.3.7 of CMW.
When I try to format the system, it says
E:format_volume failed to unmount "/system"
Error formatting /system!
Weird, they did take it out. Koush said it was a placebo. Which normally I would take as law, if it weren't for many times I have ran fix permissions and it caused apps that were force closing to not force close anymore. But whatever, if you wanna try, flash this: http://db.tt/9aWdF8Rp. It'll either help fix something, or do nothing. Won't make it any worse. If it can't mount to format though, it's either or a bug with CWM for your device, or after factory reset, reboot recovery and try again. But you really don't want to wipe /system unless you have a nandroid or another rom on your storage that is accessible.
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
boneyarsebogman said:
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
Click to expand...
Click to collapse
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
es0tericcha0s said:
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
Click to expand...
Click to collapse
Mine is the P2-6011.
Swear if we get this working, never changing anything ever.
Yes, the bootloader is unlocked.
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
es0tericcha0s said:
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
Click to expand...
Click to collapse
If I ever meet you I definitely owe you a drink. Did exactly as you said and everything (from what I can tell) is working.
It's one of the things I love about Android phones - unless you do some serious damage to it physically, for the most part it is fixable.
So, thanks button isn't enough - you saved me giving up and buying a new phone
*Hi Five* Glad all is well!
But yea, I do this for a living. Seriously. Helping people on here is how I stay sharp. lol
getting a gateway 504 error from link to firmware, would love to get this update working as i keep getting a notification on phone saying update available but it wont work
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
Can you post the link of the CM 10.2 rom For huawei P2.
I search for a long long time. but still dosnt found a rom.
Thx
Sorry for digging this up but does someone have the stock ROM of the P2? Im stuck like the fella who started this thread and havent found the stock ROM anywhere.
Thanks for the attention.
Hi Everyone,
I unlocked the bootloader a while back, planning to root and install 3rd party roms, but I never ended up doing that.
I only played around with removing "Unlocked Bootloader" message, and that's all. It took a trip to Motorola and came back once, is it possible they removed recovery?
Anyway, is there anyway to revive the device? It boots fine but I am having issues with google play store, it keeps crashing so I wanted to do factory reset, that's when I realized that recovery is missing.
Why did it go to Motorola?
Is the bootloader still unlocked? If it is,
I'm not sure what issue you got, but I would recommend you flashing a twrp recovery of the respective model. Also, Resurrection Remix 5.6.8 or AICP ROM. They are currently the most stable ones for the device.
PseudoDev said:
Why did it go to Motorola?
Is the bootloader still unlocked? If it is,
I'm not sure what issue you got, but I would recommend you flashing a twrp recovery of the respective model. Also, Resurrection Remix 5.6.8 or AICP ROM. They are currently the most stable ones for the device.
Click to expand...
Click to collapse
Hi, it went to motorola because the SIM slot pins were bent, of course it came right back with a little note "sorry, bootloader unlocked, we won't fix it" basically bootloader unlocking also voids all physical/mechanical warranty as well, I understand, I shouldn't have unlocked the bootloader on day 1 and get the sim slot messed up on day two, ended up with $50 paperweight.
Thank you so much for the suggestions, I don't want to mess it up more than it already is.
It's a CDMA+GSM edition, supposedly identical to Verizon model. I think I already have adbfastboot, I should be safe following this video here, unless you have any other suggestions
https://www.youtube.com/watch?v=R4c0fO8Kr_Q
Thanks again.
"No command" it says that on the stock recovery.
So i think i are expecting to see the TWRP screen but it's not showing.
You need to investigate putting TWRP onto your phone.
Then do a factory reset that way (i think that is what you are TRYING to do)
Did you trying booting into safe mode ?
You could try safe mode and see if that helps too.
Hold down Power Button then tap & hold down the button that shows on screen.
It will ask you if you want to reboot in safe mode..
I recently tried installing a custom play store and it worked ok for me.
I found one online that had a color scheme change to Black.
So you may want to investigate using a different version of it
or look into re-installing it clean.
I am suspicious you have some serious problem though.. the Play Store should not be crashing.
My advice is get it fixed up or factory reset etc like new then make sure to do a TWRP backup when it's clean & new.
I had to learn the hardware on that myself.
Plus it's waaaay quicker to restore a TWRP backup than it is to re-install.
Another option you can do and what i would do if i were you is go to the big firmware topic then on the first post get the FileFactory link and then match your phone model properly and then re-install the firmware fresh.
That big topic is full of info on doing this.. and it's the one with the most page hits & replies.
Usually on page 1 or 2.
xpmule said:
"No command" it says that on the stock recovery.
So i think i are expecting to see the TWRP screen but it's not showing.
You need to investigate putting TWRP onto your phone.
Then do a factory reset that way (i think that is what you are TRYING to do)
Did you trying booting into safe mode ?
You could try safe mode and see if that helps too.
Hold down Power Button then tap & hold down the button that shows on screen.
It will ask you if you want to reboot in safe mode..
I recently tried installing a custom play store and it worked ok for me.
I found one online that had a color scheme change to Black.
So you may want to investigate using a different version of it
or look into re-installing it clean.
I am suspicious you have some serious problem though.. the Play Store should not be crashing.
My advice is get it fixed up or factory reset etc like new then make sure to do a TWRP backup when it's clean & new.
I had to learn the hardware on that myself.
Plus it's waaaay quicker to restore a TWRP backup than it is to re-install.
Another option you can do and what i would do if i were you is go to the big firmware topic then on the first post get the FileFactory link and then match your phone model properly and then re-install the firmware fresh.
That big topic is full of info on doing this.. and it's the one with the most page hits & replies.
Usually on page 1 or 2.
Click to expand...
Click to collapse
Thanks, I managed to get TWRP to work on the device using ADB Fastboot, and I got the phone rooted. I removed the old Google Play store manually, restarted, and then installed it from apkmirror, and now everything seems to work just fine, but somehow I think stock recovery image is gone, I don't think I have the factory image anymore.
I checked around but couldn't find it, would you happen to know what is the stock rom for XT1526?
Thanks.
Like i was saying just look it up as per your model number..
And glad you got it working.. that is all that really matters.
Plus that screen that shows the Droid Operation with the words "no command"
that is the stock recovery.. if you installed TWRP you should never see that booting recovery.
See what i mean ?
So check this page.. it's where a lot of us got our Firmware from.
http://www.filefactory.com/folder/752fdb49361c7f62/?sort=filename&order=ASC&show=100&page=2
But research your phone model first and see what people are saying.
Mine has a tab of little plastic cover paper that pulls out that shows my Model number.
Or get it from the bootloader screen then look around using search to see what people are saying.
Some of them have restrictions.. and some are GSM versions which are a bit different.
I am not too familiar with your phone version but i Google'd it and i see Sprint & Boost coming up..
Such as this topic..
http://forum.xda-developers.com/moto-e-2015/general/moto-e-2015-cdma-sprint-xt1526-custom-t3241117
Basically i don't want to say hey go flash firmware then see you have problems
And all i did was go to that Firmware page and search for the model number
by hitting ctrl+F with Firefox then cycle through them.
There is a few of them.. that follow a file name format.
XT1526_SURNIA_ACG_5.1
ACG would be the region part of it or provider such as Boost
So that page has 16 versions of Lollipop for your model number.
What i would do is ask guys on the firmware topic what one they used.
This is where i got the Filefactory link on post one (you can look in the Mega links too)
http://forum.xda-developers.com/moto-e-2015/general/stocks-firmwares-moto-e-t3113235
I would search through that topic and ask on that topic what others used.
Then search around the forum (General section or maybe help section) and then with Google too.
For example, i googled this "XT1526_SURNIA_BOOST_5.1_LPI23.29-18-S.8_cid9_subsidy-DEFAULT_CFC.xml.zip"
And it showed this topic..
http://forum.xda-developers.com/mot...nt-version-t3052844/post64438539#post64438539
Research.. better safe than sorry LOL
Thanks for all the info, sometimes was messed up because phone received an update from Google and when it attempted to update, it got stuck in recovery (would not update). Was there a notice somewhere that we shouldn't update the phone? Anyway, it kept trying to reboot the phone after it turns on but it gets stuck at TWRP and won't update.
I was able to get into the settings and wipe the phone, now I am trying to go through set up again, but I think my best bet is to flash stock firmware and start over. Next time instead of trying wipe, I can just reflash stock firmware over it.
Hey guys, I was running stock ZVC (with stock recovery and bootloader) until just a few minutes ago, when I finally gave in and told the phone to apply the OTA update that was pushed out last week (the "ZVE" one). It started doing its thing, but next time I looked back at the device it was in recovery mode, just sitting there at the menu prompt...
I've since tried rebooting and powering off about half a dozen times, but it just keeps looping back to recovery mode. I also tried wiping the cache and rebooting, with no luck... It still loops back to recovery mode. I don't know what went wrong, but I'm assuming it could be related to one of two things that I didn't think about until afterwards:
1) The phone was rooted via Kingoroot, and root was still active when I tried to apply the update.
2) Just a FEW programs were frozen via TitaniumBackup (as well as Android's own app management system, using the "disable" feature), but these weren't system- or kernel-critical apps. They were things like LG Health, Sprint Money, etc...
Can anyone suggest a fix? Right now it just keeps rebooting into stock recovery and I've never had to deal with an issue like this, so I'm not sure what to do. I was obviously running the stock ROM, so I'm not set up to flash stuff. Although if it can be done with the default recovery, I suppose I could obviously do that... Once again, everything was stock on the phone except for Kingoroot, which was still enabled during the update.
I'm in a pickle here, guys. It's not like I'm any different than everyone who "needs their phone for work," but yeah, I need my phone for work... If I have to wipe data/factory reset, there's probably no way to pull some data off of the phone via PC first, is there? I suppose it's not that big of a deal, but I have some data and some program data that I hadn't gotten around to backing up yet, because I didn't think I'd need to until before I attempted to flash a new ROM or custom recovery.
Any help would be HUGE. Thanks...
EDIT: I took it into the Sprint store today a couple hours after I posted this, and they said I'd have to send it in to LG for warranty service. I don't know if the Sprint tech person knew what she was doing or not (because she had to use Google to figure out how to put the phone into download mode, even though she owns the same model), but she said that she couldn't establish a connection between the PC and the phone...
Now I'm not sure if that's the case, or if she just didn't have the right drivers installed, or if she was even in the right mode (I think she was using some Sprint-made flashing tool, but she did get it into download mode). She also seemed bored and like she just didn't wanna deal with it, so I don't know...
Assuming I can flash back to an earlier build like ZVB (and assuming I can even find it online), is that done from download mode or from recovery? By the way, we also tried just doing a factory reset and that didn't work either; just keeps rebooting to recovery...
Thanks...
EDIT 2: Fixed by flashing to stock via these instructions. Had to select Board DL and use a different key sequence as described here.
Hello, so I have a Galaxy S6 on Android 6.0.1 and I'm with T-mobile. I tried to root the phone using Odin first, downloaded a root checker and got the confirmation. And then I tried to get Xposed using TWRP but I had to back up my phone and all that first. After being prompted to reboot I chose an Xposed zip and since then I haven't been able to get past the Samsung logo during reboot. I've tried all the button combinations and I can get as far as the Warning screen about downloading custom OS asking to press volume up to continue or down to cancel and restart. Both of them take me to the Samsung logo where I get stuck with it flickering at me. At this point I'm panicking and waiting for the battery to drain on the blue Warning screen. Right now I have it plugged into the computer on the battery charging screen. I'm scared to turn it on and see I'm still stuck in the loop. Please help me, I cannot afford another smart phone and I had to buy this one unlocked full price. Thanks.
Edit: After turning on my phone and seeing the boot loop was still very real, I went into download mode and tried to factory reset the phone. This actually took me to the Team Win Recover Project 3.0.2-1 where is has the standard buttons for install, backup, restore, reboot, etc. At this point I am not sure what to do, I believe this is where I would want to install the Xposed zip but I am not going to proceed until I have a clear understanding on what it is I need to do.
Edit 2: I should also mention that on the TWRP recovery screen, the restore tab is EMPTY. I guess I either did not completely save a nandroid state, or didn't name it something I could find. I'm unsure on how to restore the phone to factory settings, if at all possible, with TWRP.
Edit 3: After doing some research, I've decided that my best bet is probably to download the necessary firmware for my phone, Model number SM-G920F, and use Odin once again or Smart Switch to hopefully revert back to factory settings. The problem I am now having is finding the right firmware. I'm on SamMobile but I cannot find a firmware that fits my country and carrier. I know that unstalling the wrong firmware can brick my phone so I am being very hesitant here. Can anyone help me?
I'm a bit confused...did you already install a version of Xposed that caused the bootloop or it just started bootlooping after the first reboot after it booted from the rooting process?
es0tericcha0s said:
I'm a bit confused...did you already install a version of Xposed that caused the bootloop or it just started bootlooping after the first reboot after it booted from the rooting process?
Click to expand...
Click to collapse
I only installed Xposed once, and that is when the boot loop started. I had to reboot my device two times; once for Odin, and once for TWRP to get Xposed. Like I said, I went with Odin first for the rooting process and then I used TWRP in an attempt to get the third party firmware. After rebooting for Odin I ran the root checker and everything was confirmed. If it isn't obvious by now, I'm new to this whole process and goofed somewhere along the line so there's my disclaimer. At this point I'm willing to do anything to get this phone working again. I appreciate any help.
Just run the Xposed uninstaller in TWRP.
I have seen this with my wife's galaxy s6 edge, she had dropped the phone after having it for three weeks and then the phone started to act funny. Luckily for me I did not root the phone yet so I did the button combination but instead of volume down I did volume up so I can do a complete factory reset. That had seemed to help, you can always go back to the Samsung site to get the rom you need for your phone and if its with T-Mobile which I also have, you should have no problem getting it.
espinozaea said:
I have seen this with my wife's galaxy s6 edge, she had dropped the phone after having it for three weeks and then the phone started to act funny. Luckily for me I did not root the phone yet so I did the button combination but instead of volume down I did volume up so I can do a complete factory reset. That had seemed to help, you can always go back to the Samsung site to get the rom you need for your phone and if its with T-Mobile which I also have, you should have no problem getting it.
Click to expand...
Click to collapse
I have tried the button combination that is supposed to lead to the factory reset, but this is what is taking me to the TWRP screen. What I haven't tried is finding the ROM from the site so I will try that now, thanks!
Wolf Town said:
I have tried the button combination that is supposed to lead to the factory reset, but this is what is taking me to the TWRP screen. What I haven't tried is finding the ROM from the site so I will try that now, thanks!
Click to expand...
Click to collapse
You don't need to flash the whole rom. Just run the Xposed uninstaller. It was specifically made to resolve these types of issues.
es0tericcha0s said:
You don't need to flash the whole rom. Just run the Xposed uninstaller. It was specifically made to resolve these types of issues.
Click to expand...
Click to collapse
In the TWRP screen I'm not seeing anything about unistalling Xposed, do you know what tab it would be under?
You have to grab the zip from the Xposed thread. You should be able to connect your phone in recovery to the PC and drag and drop it. If not, you might need to use ADB.
Don't flash a firmware unless you are 100% sure it's the official firmware for your device. Maybe you could contact the company's website and ask for the firmware. Sometimes this works. If it doesn't search for one but be sure to flash the official one or it may cause problems.