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.
Related
Hi,
I have an lg c800 -- mytouch q by lg
I rooted it yesterday and removed all the bloat. I also installed several root only apps to optimize the phone.
It ran smoother than even right out of the box.
So, I figured it be a good idea to backup the rom, and maybe later try cyanogenmod... So I installed Rom Manager by clockworkmod
It said i needed to install clockwork recovery rom. I went in there but it said my device was unsupported (only like 12 were) so I backed out,
and stupidly hit TWRP listed under "Recovery Already Installed". (thinking that meant what options I had to SETUP a recovery/backup)
I hit backup rom. almost instantly the phone restarted. After the bios, but before android it went to a screen with a box, and an arrow pointing from the inside of the box to the little android man. Then went to the regular android boot screen.
It does this every reboot now. The SuperSU is still there, whenever Rom Manager (which I have to reinstall each reboot) asks for root access I get that dialog box, so it hasn't actually hard reset the phone I don't think. But all the user data, contacts, apps, wifi passwords, google id "(to access Play) get wiped out.
I understand what I did wrong. I think I understand what its doing (booting to the factory rom as it was, and I can't set it to stop doing it each reboot)
What I need help with is getting back, if possible, to what I had previously, among other things, I had a bunch of tasker profiles and notes that will be time consuming to replace.
Thank you for your help.
EDIT: SuperSU is now listed among the factory installed apps. This is unchanged each reboot.
Question: If I unroot the phone what that invalidate Rom Managers ability to run before android boots?
where the people at?
dosmastr said:
where the people at?
Click to expand...
Click to collapse
going off of this page:
http://forum.xda-developers.com/showthread.php?t=1752704
for cwm recovery
drivers are all installed (I was able to root phone)
but the adb devices command comes up empty.
what gives?
dosmastr said:
going off of this page:
http://forum.xda-developers.com/showthread.php?t=1752704
for cwm recovery
drivers are all installed (I was able to root phone)
but the adb devices command comes up empty.
what gives?
Click to expand...
Click to collapse
OK so its not in the guide, but one is to exit the shell BEFORE keying adb devices. it does show.
but sadly I don't think this gets me closer to fixing what is broken.
Can anybody at least tell me if my stuff is still there or gone?
I have the impression that the boot loader is grabbing the stock rom and just expanding it and running it each boot, but that the old functional rom is still there but being unused --- like a dual boot type thing.
Am I off in left field here or?
dosmastr said:
Can anybody at least tell me if my stuff is still there or gone?
I have the impression that the boot loader is grabbing the stock rom and just expanding it and running it each boot, but that the old functional rom is still there but being unused --- like a dual boot type thing.
Am I off in left field here or?
Click to expand...
Click to collapse
more info: the bloat from the original rom is still gone, and SuperSU is intact and functional
Chui says its some flag in CWM that isn't getting cleared when the device boots.
I'm just trying to get the data my apps help at this point.
cmon phone nerds i still need some help!
no help.
The original ROM of your phone got modified after you rooted, hence no bloat and SuperSU intact even after many wipes.
I suggest re installing the factory ROM again, including the bootloader, radio and other stuff. That ought to fix the issue.
What phone do you have ?
So when it was modifying the rom that was running at the time, also the recovery rom was modified?
how do you reinstall factory rom if the phone never enters fastboot?
I'm all about wiping the bootloader (so it STOPS running recovery) but I have only made a little progress in finding how to do that without fastboot.
What I can do is run a root viewing file manager. I even found the log for the recovery it keeps running. But not what to kill so that it STOPS recovering.
Phone is LG C800DG
The LG rom update software has a recovery option but that didn't work.
One youtube video
http://www.youtube.com/watch?v=nDFO6H1XObI
Says I can get around this by using a flash utility the installs as an apk. I doubt I'll find one compatible with this phone though as support is very limited.
looks like everything out there says I need a 3rd party recovery already flashed...so that I can flash a stock rom.
sounds like the damn chicken and egg to me, to get stock fixed you need 3rd party but since you have stock you cant get 3rd party
It seems to be a general problem with your set as many others too have posted the same issue.
For stock ROM this should work.
http://forum.xda-developers.com/showthread.php?t=1825818
And a flashing guide
http://blog.androidia.net/8/how-to-flash-stock-lg-rom/
You can also see these for CM9
http://wiki.cyanogenmod.org/w/C800_Info
and
http://forum.xda-developers.com/showthread.php?t=1801622
Dumb e3 recovery. There been any updates on the cwm recovery? Thing takes forever to backup and restore rom
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.
I thought you guys might find this amusing, and hopefully it will help some people that get into a similar situation as myself. First, a little background - I rooted and installed Alliance Rom years ago back before the bootloader was unlocked. This worked amazing for me for a long time but I've recently had some weird issues with my phone so I decided to do a factory reset.
I went into settings, clicked factory reset, and then my phone got into a boot loop on recovery. I remember from before I had to do a regular boot then click recovery at the prompt instead of doing the factory recovery so I did that.
Instead of doing a normal wipe, I wanted to wipe everything on my phone and start from scratch so I did the full wipe (in what I think was TWRP or safestrap or whatever). When I went to reboot my phone it had a message like "are you sure? there's no OS installed" and I clicked ok. Well now I couldn't get the phone to boot into anything except download mode so at least I can use Odin.
I'm frantically searching google to try and find ways to install some sort of recovery so I could load AllianceRom again since I still had the zip file for it. Eureka, I found TWRP for my phone! I tried to flash TWRP through Odin but that doesn't work because my bootloader wasn't unlocked.... I remember this from last time ... all of the places I found online to install any sort of recovery required the phone to be booted into android.
So I'm clicking around and someone has a recovery randomly posted in a thread so I install it thinking, what the hell, what's the worst that could go wrong. So I install it through Odin and boot into normal recovery and I get this message saying my phone has been tampered with and to go to a verizon store immediately! Oops... upon further investigation (looking at the download screen), I tripped the knox flag... oh well, it's not like my phone is in warranty anymore (I got it on release day).
I search around looking for what I should do next and I found a thread that talked about being on complete stock, rooting, then unlocking the bootloader. I download all the files I need (newest firmware here - https://www.sammobile.com/firmwares/galaxy-note3/SM-N900V/ and thread here - https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010) to go back to stock and flash in Odin. Actually I didn't download from sammobile.com because it was downloading too slow so I just googled the file name and found it somewhere else faster, go figure.
Everything seems to be going ok then all of a sudden FAIL in Odin... Ahhh what the heck do I do now? Try again obviously! Second try works woo hoo! Phone start booting up, things are looking good!!! hooray!! But wait... it's taking forever to start and it's stuck on the Verizon logo... uh oh... taking way too long to boot up so I pull the battery and try again. Boots right in saying that android is upgrading so I think I'm finally in the home stretch here.
I try to run the ArabicToolApp for Root but I installed the latest firmware which isn't supported DAMN IT! Downloaded the correct firmware (OB6!), flashed in Odin, same problem before where it was stuck on the red verizon screen, pulled battery, rebooted, finally time to get root!
Phone finally boots into OS and I get a popup "unfortunatley com.google.process.gapps has stopped" great... and it keeps coming up over and over again after I hit ok... just my luck! Reboot again to see if that fixes the issue. Seems weird that I didn't have to go through all the initial setup stuff I did on the other version I installed... hmm... or maybe it was because I pulled the battery on the red verizon screen? Whatever. I somehow manage to get to options to do a factory reset and I let the verizon screen stay on a while this time. I'll go take my contacts out and give my wife some love while I wait
Come back and the phone is at the setup wizard, this is good news. Enabled USB debugging, installed root, done! Thank god!
Next I want to unlock the bootloader. I follow the steps here which aren't very clear (I'm guessing on purpose for novice computer users) - https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
1. I installed eMMC from the play store to make sure my CID started with a 15, it does so I know I'm good to use the hack.
2. I installed both files in the unlock kit (adb and driver setup)
3. Fired up adb, navigated to where I had unlock_n3, and ran through the first part of the code once, reboot my phone, checked that the CID was the developer CID, and then ran the second part of the code three times before it worked
I verified the bootloader was installed correctly by trying to install TWRP through Odin, which worked!
I'm going to try out Jasmine Rom since it's a popular one that is on 5.0. My SD card only showed 30 megs free or something like that, so I formatted it from within android and copied the zip file over and installed the Rom through TWRP. Rom installed just fine, so I did one last factory reset which worked great and I think I'm finally good to go!
If you have any questions or run into any issues feel free to reply here and I'll try to help as much as I can.
Glad it worked out for you in the end.
From making a few mistakes I know that sinking feeling "oh no, what have I done?"
FWIW, the bootloader unlock method (in principle) works from nearly ANY ROM which is rooted - so, you would have saved yourself a bunch of time if you had started with that before you wiped the Alliance ROM. So long as you have root and a CID value that starts with 0x15, you just need root privileges - no need to return to stock and re-root.
(The "in principle" part is that there were several bugs in the "safety checks" portion of the unlocker binary that were sensitive to the OS revision, so you might have to search through the unlock thread to find a version of the unlock binary that is compatible with whatever rooted ROM is on the phone when the unlocking is attempted.)
good luck
PS The AryaMod ROM (w/ phantomOne kernel) is pretty solid - Marshmallow w/ S-Pen apps, too! As with any other dev ROM, there are a few sharp edges, but mostly everything works (except NFC).
.
Hi!
Finally I got stuck in a boot loop on my Pixel 6 running QPR2.
It's looping after the G animation (vibrates a few times at that point when attached to a PC).
Reflashing the latest QPR factory image (without -w) by using SDK 33.0.3 does not solve the issue.
The ROM was running fine before, but it rebooted due to a faulty custom kernel version and now I'm stuck.
My theory is, that the launcher (nova) can't load and therefore it reboots.
Anything I could do using fastboot?
Never flash a custom kernel on a stock ROM, If not suggested by the dev.
I understand that you flash without wipe?
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Sui77 said:
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Click to expand...
Click to collapse
If the kernel broke your actually ROM, nope. You could backup the file stored locally via adb in the recovery, but not anything more.
Wipe all is the best, better than have to handle with an hard brick.
Sui77 said:
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Click to expand...
Click to collapse
If I were you I'd maybe get some logs and go through them and see if you can find anything that way. Maybe add logs to your op here.
There aren't many ways to backup things nowadays for pixel 6 but what I have used to backup apps + app data that works well when restoring is Neo app from Fdroid store. As far as backing up goes, at this time I've used nothing that is/has been as solid as Neo. I miss the days of just being able to boot one of a few various custom recoveries, making a nandroid backup to a USB thumb drive with my OTG cable and restore it whenever it was needed but things change. Sounds like maybe something was left behind from your kernel install. If you really dislike formatting I'd stay away from whatever you installed here to get in this loop but definitely backup using Neo once you get going again and put your backups on thumb drive or you PC or somewhere other than your device so you can restore them when you need to. I don't flash nowhere near as much as I used to but I used to flash my device(s) many times a day , everyday for many years but I remember years ago on another device I looped and wiped my cache and system and reflashed rom and ended up booting up. But that was another device years ago. Maybe try adb sideloading instead of factory image flash without wiping data. Try that and after it's done installing reboot to others slot and sideload it again... These things probably won't work but you never know until you try. Did you have magisk installed before and not now? Maybe flash stock kernel patched with magisk to both slots if so. Hate to say it but you will probably end up having to format data but idk because I don't know exactly how you installed the kernel "in detail" or exactly what kernel it is or if anything else was changed from before you looped ... No logs...
I've been using Android since the beginning (G1) and I've been tinkering with my devices since back in the Nexus S days on a regular basis and I've found that the best way for to get the help I need is to try like hell to figure whatever it is out myself by searching for the problem I'm having, I mean like really searching, sometimes for hours , sometimes maybe searching for things related to the problem I'm having that show up in my searches, sometimes the answer can be in another devices forum, piecing together bits of info from various places to try and solve whatever it is... etc ... etc... But the best way to get help is do research on it, take some notes, try various things to fix it, then if I still can't figure it out make a post about it here and in op attach every log I can possibly gather from said device, include all the things I tried to fix it with myself "in detail..." My exact installation process, you know like: reboot bootloader, was on slot A, executed ./flash-all.sh for factory image xxxxx, rebooted system ... The more details you provide the more accurate people will be when answering and the more people you will get to reply.. I'm not trying to sound like some asshole or anything at all. Im just speaking what works best here to get answers. Sometimes you just don't get any answers even if you post 18 paragraphs with a chart and a line graph, things you tried, what all you tried it with and links to it all. But anyone here who does this will most definitely stand a much better chance at getting some replies on whatever it is. I sometimes read over on Reddit and Tele groups , sometimes answers can be found that way. Sometimes people just give you the silent treatment.. Even if you do your homework. That's just a thing with anything related to development that happens. I always used to think when I would get no replies that the other guys and gals who know the answer are thinking to themselves, "oh look at this idiot here!" "He clearly didn't graduate from Harvard top of his class with a PhD like we did. " " Such an imbecile!!! " But what could have been going on and more than likely was/is is life , kids, bills, sleep, relationships, covid19, and tons of other things..
Some of this development stuff is a real beech to get and everyone works hard to get it and many aren't too fond of just giving random people answers that took them many sleepless nights to get. But if and when a dev sees someone with a detailed post , things tried.... etc ... etc .. Theyre much more likely to throw some knowledge your way. That's been my experience anyway.
@flash713
Wow, thx for thw write up, appreciate!
I was on latest QPR2.1 with Radioctive Kernel, Magisk installed.
Since the device got stuck in the boot animation, I tried a lot and flashed different factory images using the flash-all method. w/o success.
Also tried the Flash tool in the google website, also w/o success.
When the device boots while it's connected to the PC, it beeps/vibrates 3 times and the reboots.
My guess is that it has problems to load the launcher, Nova was set as standart.
I'm using android since years, tinkering a lot, but I'm not a pro in doing so.
Meanwhile i set up my new Pixel 7 and restored it via Google backup and a few apps by using a SWIFT backup.
Fotos were restored by Google, but all whatsapp pictures are messed up ow, cause the date of restore.
How do I gather proper logs?
Did a last attempt and sideloaded the OTA to both slots...same outcome...
Doesn't magisk have a remove all modules.zip? I mean oriole doesn't have TWRP available yet.
I presume that when it's bootlooping you don't have any ADB?
You did have ADB enabled, right?
Depending on system and setup you may have ADB started by init or started by Android.
Your problem could be as simple as a bad Launcher.
I don't know if the P6 has a UART console. Does it?
Hi Renate,
thx for your reply.
Yes, that is what i thought. The Pixel boots up into the G-animation and then loops 3 times (beeping/vibrating if connected to PC) and than reboots in total.
I think I had something like that in the past when I accidently deleted the launcher apk (don't ask )
Anyway, Nova launcher was set as standart, so the only idea could be to set the genui Pixel launcher as default, but I don't know how to do that in fastboot or adb mode.
Sui77 said:
Anyway, Nova launcher was set as standard, so the only idea could be to set the genui Pixel launcher as default, but I don't know how to do that in fastboot or adb mode.
Click to expand...
Click to collapse
I'm still not clear if you have ADB ever available.
If you do you could:
Code:
adb uninstall com.nova.whatever.launcher
If the /data/data that Nova is using is corrupt or missing it could cause failure.
Android will switch to whatever else belongs to android.intent.category.HOME automatically.
If there is nothing there you can install another launcher.
Have adb (after booting into recovery mode), will report back asap
I habe adbd device connected via recovery/rescue mode, but that's not working.
In bootloader, I can't use adb, no device connected.
Hw can I use adb while the device is not booted up?
Can you mount data in recovery (and it's unecrypted)?
Feeling a bit dumb, but I can only boot into fastboot or into the boot loop, don't know how to mount data in recovery mode (the one with the andoird robot)
When you're in the boot loop you don't get adb even for a few seconds?
This are the last lines of the recovery.log
2 new items by TheMrSui
photos.app.goo.gl
Checked that by opening a cmd and using "adb devices", but nothing showed up
When you're viewing that log, don't you have ADB working then? It says that it is.
I had this weird issue on Raven, first try using android flash tool through a chrome based browser. If that still loops then wipe, and flash an older image. For some reason I had to flash an image from the previous month and that would boot.