Database Users

Am I Soft Bricked?

Here's the rundown:
I installed the Dark Paranoid Android (Grouper) ROM this morning. I flashed Gapps, and rebooted the device. No issues at that point, because I came from another ROM I did a clean install and got through the registration screens no problem. Once at the home screen, I remembered I had not flashed the Trinity (Grouper) kernel like I had planned, so I rebooted to recovery and flashed it.
That's when I ran into problems. Rebooted device and it stuck at the Google screen. Tried to bootloader into recovery, I still get stuck at the Google screen. Have tried to boot up both the recovery and into Android several times from bootloader, but I always get stuck at the Google screen. I guess my device didn't like the kernel, or somehow installing it damaged my recovery maybe?
Basically, I am asking if I am soft-bricked and have to restore factory and therefore wipe the device clean. Doing that would suck, but it's better than not having the device.

Also, I'd like to know if it's possible to flash stock through the Wugfresh toolkit without removing root. I just want to get back to stock so I can reinstall the ROM and try a different kernel.

liquid150 said:
Also, I'd like to know if it's possible to flash stock through the Wugfresh toolkit without removing root. I just want to get back to stock so I can reinstall the ROM and try a different kernel.
Click to expand...
Click to collapse
Try to wipe everything and reinstall

kinhbang1989 said:
Try to wipe everything and reinstall
Click to expand...
Click to collapse
Impossible with my device in the state I described.
Since the answers were fairly slow I already flashed factory image from Google with the toolkit. Issue was resolved, just will take a while to get everything put back on it.
Sent from my Paranoid Galaxy Nexus

Did you check the md5 on the kernel download? If there wasn't an md5 supplied, download the file a few times and compare the md5's between them for consistency. Could've been as simple as a bad download.

mustbepbs said:
Did you check the md5 on the kernel download? If there wasn't an md5 supplied, download the file a few times and compare the md5's between them for consistency. Could've been as simple as a bad download.
Click to expand...
Click to collapse
I did not check it. Maybe I will try it again later. Was able to right the problem by using the Nexus Toolkit to flash 4.1.2. Then I put DarkPA on it and started over. Not really the end of the world, just slightly time consuming.
I love the Trinity kernel on my phone. I want to use one for Nexus but I didn't see a stable one yet, all are in experimental phase.
Sent from my Paranoid Galaxy Nexus

Jelly Bean

hi all, just this minute decided i want to try put Jelly Bean on my X8.
at the moment i have the stock android 2.1 that came with the phone. its rooted so i could use a custom launcher.
now firstly. if all failed or i wanted to restore the phone back to its original android 2.1, how would i do that? do i need to do a back up of the phone?
if so, how do i do this and what with.
now for the Jelly Bean rom. i want the best and most stable jelly bean rom that will not play up and work 100% including the camera.
which is the best jelly bean rom for my x8?
and how do i get the custom jelly bean rom on my x8.
bear in mind i have never done anything like this to my x8 before i could brick it as i dont have a clue what to do. so can someone give me the best noob guide or video that would be easy for a idiot to understand.
thank you to anyone who will help me
Dan.

Hey there. So now your phone is running rooted Android 2.1. First can you check the sticker behind you phone?(Turn off your phone and pull out the battery). Make sure the manufacturing date is below than 11W29. If it's above 11W29 you can't unlock your phone's bootloader and you can't install any JellyBean ROM. If it's below than 11W29 you can unlock your phone's bootloader using guides in this forum(Search unlock bootloader x8). After you have done unlocking the bootloader you now can proceed to installing custom kernel which is Oxydo-JB kernel or nAa-JB kernel using FlashTool. Then, you can flash MiniCM10 4.0.2 which is JellyBean ROM onto your device.
If you make any mistake during unlocking bootloader process it will result in hard brick. Make sure you follow the steps carefully. If you done everything correctly you can enjoy JellyBean on your phone. If you somehow managed to softbrick your device you can revived it using PC Companion or Flashtool. But it is better to make a backup in case something goes wrong.
Hope I helped you.

nazz.rule said:
Hey there. So now your phone is running rooted Android 2.1. First can you check the sticker behind you phone?(Turn off your phone and pull out the battery). Make sure the manufacturing date is below than 11W29. If it's above 11W29 you can't unlock your phone's bootloader and you can't install any JellyBean ROM. If it's below than 11W29 you can unlock your phone's bootloader using guides in this forum(Search unlock bootloader x8). After you have done unlocking the bootloader you now can proceed to installing custom kernel which is Oxydo-JB kernel or nAa-JB kernel using FlashTool. Then, you can flash MiniCM10 4.0.2 which is JellyBean ROM onto your device.
If you make any mistake during unlocking bootloader process it will result in hard brick. Make sure you follow the steps carefully. If you done everything correctly you can enjoy JellyBean on your phone. If you somehow managed to softbrick your device you can revived it using PC Companion or Flashtool. But it is better to make a backup in case something goes wrong.
Hope I helped you.
Click to expand...
Click to collapse
i believe you have gave me everything i need to get a custom rom on.
but one thing. how do i make a backup of my stock OS incase something goes wrong or i want to put the original back on?
how do i do it and what with? and where do i get the stock kernal and rom?

Vega_Dan said:
i believe you have gave me everything i need to get a custom rom on.
but one thing. how do i make a backup of my stock OS incase something goes wrong or i want to put the original back on?
how do i do it and what with? and where do i get the stock kernal and rom?
Click to expand...
Click to collapse
Here's the link to the stock 2.1 firmware. You have to flash this using FlashTool.
If you want to backup your stock ROM you have to install a recovery into your device. You can do this using x8toolbox. And after that, you can backup the stock ROM using the recovery.

nazz.rule said:
Here's the link to the stock 2.1 firmware. You have to flash this using FlashTool.
If you want to backup your stock ROM you have to install a recovery into your device. You can do this using x8toolbox. And after that, you can backup the stock ROM using the recovery.
Click to expand...
Click to collapse
will that work for a UK phone because it says Greek on it.

Vega_Dan said:
will that work for a UK phone because it says Greek on it.
Click to expand...
Click to collapse
It should work. I've tried it with my phone and it works. But I only use it for an hour,though.

If you want back stock 2.1 , use Sony PC Companion.
Sent from my E15i using xda app-developers app

i have knocked this on the head and gave up.
i unlocked the bootloader and flashed the kernel. but when i tried installing jellybean i just get a failed to install and a (status 7) error everytime i tried.
i tried reflashing the kernel. i tried 5 or so different roms including a few ICS ones and still got the same problem.
so i have now just put the stock 2.1 OS back on.

Vega_Dan said:
i have knocked this on the head and gave up.
i unlocked the bootloader and flashed the kernel. but when i tried installing jellybean i just get a failed to install and a (status 7) error everytime i tried.
i tried reflashing the kernel. i tried 5 or so different roms including a few ICS ones and still got the same problem.
so i have now just put the stock 2.1 OS back on.
Click to expand...
Click to collapse
If I'm not mistaken, status 7 error is because corrupted zip file. Have you tried redowloading the ROM.zip file and check the MD5 sum?
Sent from my Xperia™ X8

nazz.rule said:
If I'm not mistaken, status 7 error is because corrupted zip file. Have you tried redowloading the ROM.zip file and check the MD5 sum?
Sent from my Xperia™ X8
Click to expand...
Click to collapse
surely all 5 or 6 of them roms shunt have corrupt. plus I had downloaded one of them 3x and was still same.

@Vega_Dan
If you get Status 7, do this:
1. Open up the ROM.zip file.
2. Open up updater-script from META-INF>com>google>android.
3. Remove the first few getprop lines.
4. Save it and try flashing now.
Hope this helped.
It happens a lot on my kernel.

Vega_Dan said:
i have knocked this on the head and gave up.
i unlocked the bootloader and flashed the kernel. but when i tried installing jellybean i just get a failed to install and a (status 7) error everytime i tried.
i tried reflashing the kernel. i tried 5 or so different roms including a few ICS ones and still got the same problem.
so i have now just put the stock 2.1 OS back on.
Click to expand...
Click to collapse
before installing go to advanced and format system,data,cache.
Sent from my E15i using xda app-developers app

Lukenda said:
before installing go to advanced and format system,data,cache.
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
tried all that.

sgt. meow said:
@Vega_Dan
If you get Status 7, do this:
1. Open up the ROM.zip file.
2. Open up updater-script from META-INF>com>google>android.
3. Remove the first few getprop lines.
4. Save it and try flashing now.
Hope this helped.
It happens a lot on my kernel.
Click to expand...
Click to collapse
wish i knew that then. i cant be bothered now to go through it all again. it was giving me a headache.
ive only just finished getting my phone back to how it was before i started.
i may have a go sometime next week.
thanks for that.

so ive just reflashed the oxydo-jb kernel. now I have removed a few lines from the zip file and get a status 6 error.
I don't know if I have removed the right bits or not.

success guys. its seems it was the oxydo-jb that was the problem because I have used the nAa-JB kernel and its worked.
I now have MINI CM10 JB now.

N4 upgrade failed

Help me XDA, you're my only hope...
First, background: I bought my Nexus 4 over the internet, because it was never officially released in Belgium. I had to have the screen replaced, and let a 3rth party do it. Glass damage isn't covered by the warranty and it would mean sending my phone by international mail if i used the official warranty people. They told me that the also had to replace the proximity sensor.
My phone worked perfectly afterwards. Until I tried to install the automatic upgrade to 4.3.
First it stopped at the X-logo screen and became very hot. I contacted play support and did all the things they advised (including a factory reset, rebooting in safe mode), none of it works. I found someone with the same problem who managed to get past the X-screen by flashing back the 4.2.2 radio version. And that worked: the phone booted and the update started.
However, since that moment I got a lot of problems:
- random shutdowns
- random locking of the SIM card
- phone not starting unless plugged in charger.
Worst of all, reflashing stock images for 4.2 and 4.2.2 or AOKP does nothing to solve these problems. I also tried a new SIM card, and still nothing.
I'm at my wit's end now. Could there be a driver issue? Any other things I can try?
TIA

Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Click to expand...
Click to collapse
any suggestions for a good kernel that can run stock android?

If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.

BobWalker said:
If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.
Click to expand...
Click to collapse
Well, I tried again. (For the 6th time this month) No different as before: it's been stuck on the X screen for 20 minutes now and getting warmer.
EDIT: I finally managed to get into the recovery menu. No idea why it wouldn't let me use volume up + power...

As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?

Joenr76 said:
As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?
Click to expand...
Click to collapse
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Click to expand...
Click to collapse
I never did that before: do I flash the kernel first or the Rom first? Are there any guides?
EDIT: I just read that Paranoid Android comes with the halfbreed kernel included. Is that the one you linked too?

Before jumping into the kernel thing (also because i wanted to be able to work with a device that can actually boot), I reinstalled the 4.2.2 factory image. It took about 5 minutes for the first shutdown to happen. *sigh*
And without plugging it in, it goes into a boot loop (going to x screen for a while, then restarting.) When I plug it in, it starts immediately, but shows the battery as empty. It was 63% when it shut itself down.
It's a clean install, I just don't understand...

Okay so, I'm assuming you have a custom recovery like TWRP. Open it and flash the newest boot loader and radio. Then flash Paranoid Android and GApps. Then try flashing Faux kernel and clearing cache/dalvik. If you still have problems, then I have no idea
Sent from my Nexus 4 using xda premium

Open up your phone to see the battery is securely checked and to see if all the components are okay. Then look do a full wipe of cache,dalvik,system,data,and sd (internal storage). Then use wugs toolkit to a upgrade on a clean flash. Double check to make sure you wipe everything!
Sent from my Nexus 4 using Tapatalk 4

TheNerd:] said:
Open up your phone to see the battery is securely checked and to see if all the components are okay.
Click to expand...
Click to collapse
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...

Joenr76 said:
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...
Click to expand...
Click to collapse
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.

tykate said:
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.
Click to expand...
Click to collapse
Tried that before. I did some research and I guess this is relevant: http://www.androidpolice.com/2013/0...rops-on-some-nexus-4-handsets-fixes-in-sight/ Especially since I ordered my Nexus from the Netherlands.
I'll have to wait until that bug gets fixed until I can upgrade my radio.

Stuck at Google boot screen

I wanted to tinker around and decided to check out custom roms. Flashed pure nexus and gapps and rebooted without flashing the new vendor image. In fact I had forgotten to download it.
Phone booted into the language choosing screen showing the 'need to flash new vendor'. Not having downloaded it, I booted back into recovery and restored my backup stock rom to quickly get into the xda thread on tapatalk and download it quickly in order to start from fresh
Got the message ' Your device is corrupted ' with a red triangle.(usually got an orange triangle after I unlocked the bootloader). After the red message, the screen got stuck at the white Google screen with a lock pic at the bottom.
I tried restoring my backup again and even flashing pure nexus again with the same result of being stuck at the Google screen with the red warning message.
Totally frustrated not being able to even try one romantic easily. Does anyone has any idea of how to fix it? Or should I start from scratch downloading stock factory image again?
Thank you.
Sent from my SM-G930F using XDA-Developers mobile app

Is everything else in your phone up to date?(bootloader, radio etc. etc.) If you're not sure it Might be safer to just flash stock image and then start flashing roms.

toknitup420 said:
Is everything else in your phone up to date?(bootloader, radio etc. etc.) If you're not sure it Might be safer to just flash stock image and then start flashing roms.
Click to expand...
Click to collapse
My phone had been updated till last month but the rom has this month's patches too. Radio isn't updated by the Rom. By stock I had 3.61. The new one is 3.62 I believe. I have no idea why my phone acted this way though. Does this phone always have the risk of doing this and me flashing stock a lot of times to correct it?
Sent from my SM-G930F using XDA-Developers mobile app

I would suggest try cleaning dalvik and cache. However, I don't think that that would solve the red warning screen. Perhaps the backup you restored was somehow corrupted. I'd say reflash everything (bootloader, radio, rom, vendor, etc), and return to completely stock and see if the problem is still there.

Chillz88 said:
My phone had been updated till last month but the rom has this month's patches too. Radio isn't updated by the Rom. By stock I had 3.61. The new one is 3.62 I believe. I have no idea why my phone acted this way though. Does this phone always have the risk of doing this and me flashing stock a lot of times to correct it?
Click to expand...
Click to collapse
Ok so then just flash the ROM then the latest vendor image and you should boot fine.

http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I hope the 11th part of this guide would do it? Thanks guys.

Chillz88 said:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I hope the 11th part of this guide would do it? Thanks guys.
Click to expand...
Click to collapse
Have you tried flashing the vendor image with the newest version of pure nexus. That red warning is due to the incorrect vendor image. I would try that before flashing the factory image and starting over.

Can't get any version of CM to load

I am unlocked (it yells at me every time I power on...)
Flashed twrp-2.8.6.0-xt907, everything went fine
But after flashing any version of CM it either doesn't get past the unlocked bootloader warning (when I use cm-10.1.3-xt907 cm-11-20140104-SNAPSHOT-M2-xt907 or cm-10.2-20131102-SNAPSHOT-M1-xt907)
or it just shows the CM face with the white circle growing out over and over (if I use cm-12.1-20160523-NIGHTLY-xt907 or cm-12.1-20160530-NIGHTLY-xt907)
I've done the factory wipe a dozen times, even tried formatting at the partitions before installing. Wiping cache/davlik...nothing seems to help. Any advice?

bassgoonist said:
I am unlocked (it yells at me every time I power on...)
Flashed twrp-2.8.6.0-xt907, everything went fine
But after flashing any version of CM it either doesn't get past the unlocked bootloader warning (when I use cm-10.1.3-xt907 cm-11-20140104-SNAPSHOT-M2-xt907 or cm-10.2-20131102-SNAPSHOT-M1-xt907)
or it just shows the CM face with the white circle growing out over and over (if I use cm-12.1-20160523-NIGHTLY-xt907 or cm-12.1-20160530-NIGHTLY-xt907)
I've done the factory wipe a dozen times, even tried formatting at the partitions before installing. Wiping cache/davlik...nothing seems to help. Any advice?
Click to expand...
Click to collapse
I believe those are all built for the jellybean bootloader, did you downgrade, or still on KitKat?
Sent from my KFFOWI using XDA Labs

I must've missed that, thanks

sd_shadow said:
I believe those are all built for the jellybean bootloader, did you downgrade, or still on KitKat?
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Hmm, the CM wiki is confusing me on this
https://wiki.cyanogenmod.org/w/Install_CM_for_xt907
Your device must be bootloader unlocked.
For CM 11.0, the device builds have been unified. Get the latest CM 11.0 build for KitKat bootloader updated devices here and for devices still on JellyBean bootloader here.
For CM 12.0 and newer, KitKat bootloader is required and builds were de-unified again. Get them under the usual xt907 builds.
Click to expand...
Click to collapse

I flashed the boot.img from VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml.zip, but that didn't seem to help any.

bassgoonist said:
I flashed the boot.img from VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml.zip, but that didn't seem to help any.
Click to expand...
Click to collapse
I didn't remember correctly,
cm11 and cm12 require the kitkat bootloader
where did you find the recovery?
should be a cm recovery on their site, could try that
Sent from my XT1060 using XDA Labs

bassgoonist said:
I am unlocked (it yells at me every time I power on...)
Flashed twrp-2.8.6.0-xt907, everything went fine
But after flashing any version of CM it either doesn't get past the unlocked bootloader warning (when I use cm-10.1.3-xt907 cm-11-20140104-SNAPSHOT-M2-xt907 or cm-10.2-20131102-SNAPSHOT-M1-xt907)
or it just shows the CM face with the white circle growing out over and over (if I use cm-12.1-20160523-NIGHTLY-xt907 or cm-12.1-20160530-NIGHTLY-xt907)
I've done the factory wipe a dozen times, even tried formatting at the partitions before installing. Wiping cache/davlik...nothing seems to help. Any advice?
Click to expand...
Click to collapse
Try This One
https://download.cyanogenmod.org/get/jenkins/90471/cm-11-20141112-SNAPSHOT-M12-moto_msm8960.zip

Any resolution?
I have the same problem as Bassgoonist. Wondering if you ever got it resolved?
I have xt907, rooted, unlocked via sunshine, KK bootloader. Installed twrp-2.8.6.0-xt907. Flashed cm-12.1-20160822-NIGHTLY-xt907 and it never gets past initial boot animation. I also tried the CM recovery which installed fine, but exhibited the same symptoms.
So, did msm8960.zip work? Should I just keep trying different nightlies?
Has anyone had this problem and gotten past it?

s1gma40 said:
I have the same problem as Bassgoonist. Wondering if you ever got it resolved?
I have xt907, rooted, unlocked via sunshine, KK bootloader. Installed twrp-2.8.6.0-xt907. Flashed cm-12.1-20160822-NIGHTLY-xt907 and it never gets past initial boot animation. I also tried the CM recovery which installed fine, but exhibited the same symptoms.
So, did msm8960.zip work? Should I just keep trying different nightlies?
Has anyone had this problem and gotten past it?
Click to expand...
Click to collapse
im having the same issue

Finally got it.
HideTheCookies said:
im having the same issue
Click to expand...
Click to collapse
((Sorry for the lack of links, I'm new here and the links aren't yet allowed for me. Hopefully you can cut and paste them.))
I was so close for so long. You know how you start going around in circles, and you think you've done everything, but maybe you forget a step? Yea.
I won't repeat everything I did, but here's the links I followed, they have explained it pretty good:
1st: forum.cyanogenmod.org/topic/117181-any-dev-is-intrested-in-unlocking-latest-kernel-of-razr-m
2nd: Well, I had to pay the 25$ for sunshine. But it was worth it: theroot.ninja
3rd: Follow this, but skip the first section on rooting, you've already done that: wiki.cyanogenmod.org/w/Install_CM_for_xt907
The thing that is missing in the last step, that I thought I had done, but not completely apparently, is this:
Just before you install the CM21 mod, you are in twrp and you've done your backup. The directions say "7.Select Wipe and then Factory Reset." Well that's not quite enough. INSTEAD you need to choose wipe, then choose the advanced option, and wipe every single thing except the sdcard. (Do it twice, why not? We'll teach those partitions to mess with us!)
Finish up with the install as the directions suggest and that should work. It worked for me on an xt907, starting from the 182.46.15 firmware version. The first boot does take several minutes.
Thanks to Cube Computer Channel on YouTube for having a great, long video that was full of information, of which I ultimately only needed the three second reminder/kick in the head that I need to wipe all partitions.
Good luck all!
S1gma40 out.