Related
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
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.
I was 4.3 (locked bootloader) and the phone worked fine until one instance where the lcd glitched in the messaging app and it stopped responding. So I hard reset the phone and then it got stuck at the nexus logo (Bootloop).
So, i tried the following things:
1) Unlock bootloader
2) Flash 4.4 (KRT16S) from fastboot. Flash completed successfully, there were NO errors. Waited for a while, still stuck in the nexus circling logo. So i went to recovery and wiped data and cache, rebooted and waited for atleast 30mins.
3) Next, I tried 4.3 (jwr66y). Went through the same drill, still not booting. At this point I starting looking online to see if others are having the same problem. This is probably close to what I could find (http://www.reddit.com/r/nexus4/comments/1nefzy/)
4) Lastly I flashed 4.2 (jdq39) using the same procedure as the last 2, but this time it boots successfully! I cannot explain why, I have not done anything different this time.
So I thought I'll give 4.4 another try, but it doesnt work. Stuck in a bootloop. Immediately I flashed back 4.2. So, ultimately only 4.2 works on this phone for some reason. Any ideas as to why this is happening?
Is there a hardware problem with the nandflash, if so how do I verify it?
Also I did not use the toolkit to flash, I just ran flash-all.bat and verified that each command was executed successfully.
UPDATE: This is a rare problem that has affects a handful nexus 4s. The best option is to RMA the phone if it is under warranty of sell the phone for parts. This post gives a good summary of the problem: http://forum.xda-developers.com/showpost.php?p=47532787&postcount=282
jblack248 said:
I have the unknown IMEI and baseband problem that I've seen a number of people have without resolution. While I appreciate the efforts made here, I am including myself in the group that this unbricking method did not work for. For the sake of hoping to save other people time, I'm going to write out my experiences with this problem so far.
I was running CM 10.2 nightly 20131114 without issue when after a reboot my phone bootlooped on the starting animation. I've had errors on nightlies before, so I did the normal routine of fixes. I tried everything from restoring nandroid backups, flashing newer and older radios, doing a fresh install of a known working CM build, then wiped the entire device and tried flashing factory images for 4.4 and 4.3. None of these got the device to boot. Based on a recommendation I went back to the 4.2 factory image and had some luck, but it took a very long time to boot and had an unknown IMEI and baseband. It took a very long time to boot with or without the SIM card.
At this point I tried the unbrick method listed here, and when I restored the factory image I had the exact same problem. I applied the 16 GB fix, but since I'm going to give up for the RMA long-haul I'm not even bothering with the MAC address fixes. I'm restoring to the 4.2 factory image and locking the bootloader so I can send this device back to Google / LG.
I haven't seen anyone recover from the unknown IMEI and baseband problem, and it's scary because it happens for no reason on both stock and custom ROMs. I really like my Nexus 4, but it's going to be hard to trust whatever replacement I get (if any) from Google / LG.
Click to expand...
Click to collapse
@pravarth It looks like you flashed the wrong image to the nexus 4. Always flash image which says occam (thats the codename) . If 4.2 works then surely 4.3 and 4.4 will work successfully.
Always downlaod image from here :
HTML:
https://developers.google.com/android/nexus/images#occam
.
Just flash 4.4 again and see .
Abhiheart said:
@pravarth It looks like you flashed the wrong image to the nexus 4. Always flash image which says occam (thats the codename) . If 4.2 works then surely 4.3 and 4.4 will work successfully.
Always downlaod image from here :
HTML:
https://developers.google.com/android/nexus/images#occam
.
Just flash 4.4 again and see .
Click to expand...
Click to collapse
I got the images from that link and I also double checked that I'm using occam images
occam-jdq39-factory-345dc199 (4.2)
occam-jwr66y-factory-74b1deab (4.3)
occam-krt16s-factory-2006f418 (4.4)
I also verified the md5 hash on all 3. The files are fine
@pravarth : You are on unlocked bootloader, try flashing a 4.4 custom ROM and see
Flash This :
HTML:
http://forum.xda-developers.com/showthread.php?t=2507021
nice
Sent from my Micromax A250 (CanvasTurbo) using XDA Premium 4 mobile app
hmm, the factory images should work. are you under warranty?
same case, my phone only works with 4.2
amartinpascual said:
same case, my phone only works with 4.2
Click to expand...
Click to collapse
Really farfetched but maybe something got damaged in persist or one of the other partitions. If you can figure out a way of enabling usb debugging in 4.3/4.4 (say enabling it in 4.2 and dirty flashing system/boot or maybe flashing a custom rom that has it enabled by default), you might be able to investigate further with logcat.
ziddey said:
Really farfetched but maybe something got damaged in persist or one of the other partitions. If you can figure out a way of enabling usb debugging in 4.3/4.4 (say enabling it in 4.2 and dirty flashing system/boot or maybe flashing a custom rom that has it enabled by default), you might be able to investigate further with logcat.
Click to expand...
Click to collapse
Logcat?
Abhiheart said:
@pravarth : You are on unlocked bootloader, try flashing a 4.4 custom ROM and see
Flash This :
HTML:
http://forum.xda-developers.com/showthread.php?t=2507021
Click to expand...
Click to collapse
Don´t works, same bootloop
Wrong bootloader?
Sent from my Nexus 4 using xda app-developers app
ziddey said:
hmm, the factory images should work. are you under warranty?
Click to expand...
Click to collapse
Yes, I'm under warranty but I bought the phone from USA and I don't want to send it back unless I have to. So I'm trying all options
Oxious119 said:
Wrong bootloader?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The appropriate bootloader and radio images were flashed before flashing the image.
According this thread, it seems the problem exists with baseband and apparently is a known problem (http://forum.xda-developers.com/showthread.php?p=48332273#post48332273). So it seems only .48 baseband boots. This is probably what is happening with mine as well. I'll check if they work while on .48 baseband
same problem, like this: http://forum.xda-developers.com/showthread.php?p=48332273#post48332273
tip: you can use 4.3, flash 4.3, then flash the radio of 4.2.2: cwm-radio-mako-m9615a-cefwmazm-2.0.1700.48
but this tip didn't work with 4.4 or 4.4.1, i'm also looking for a solution
Abhiheart said:
@pravarth : You are on unlocked bootloader, try flashing a 4.4 custom ROM and see
Flash This :
HTML:
http://forum.xda-developers.com/showthread.php?t=2507021
Click to expand...
Click to collapse
I tried flashing CM10.2, stuck in bootloop
So, I've found quite a few threads with the same problem and no solution. http://forum.xda-developers.com/showthread.php?t=2525479
http://forum.xda-developers.com/showthread.php?t=2450301
4.2 boots but imei and baseband in settings shows unknown. In bootloader mode the radio version is shown.
jedivulcan said:
Same thing happened to me yesterday. I turned the phone on and it was in a persistent bootloop. Tried everything to get it working until I flashed 4.2.2 and then there was no IMEI or baseband.
Click to expand...
Click to collapse
flash the radio cwm-radio-mako-m9615a-cefwmazm-2.0.1700.48
:/ so this is another problem, good job google! someone have tried to flash the 0.98 radio with 4.4.1/2?
pravarth said:
I tried flashing CM10.2, stuck in bootloop
So, I've found quite a few threads with the same problem and no solution. http://forum.xda-developers.com/showthread.php?t=2525479
http://forum.xda-developers.com/showthread.php?t=2450301
4.2 boots but imei and baseband in settings shows unknown. In bootloader mode the radio version is shown.
Click to expand...
Click to collapse
@pravarth : Did you try factory reset ?? try that might fix your IMEI and baseband
I had a similar issue trying to flash the factory 4.3 and 4.4 images. Everything appeared to flash successfully, but it would never get past the boot logo.
I don't recall where I found it, but someone said to try re-locking then unlocking the bootloader. It worked for me. Maybe it could work for you.
rsilvawashington said:
I had a similar issue trying to flash the factory 4.3 and 4.4 images. Everything appeared to flash successfully, but it would never get past the boot logo.
I don't recall where I found it, but someone said to try re-locking then unlocking the bootloader. It worked for me. Maybe it could work for you.
Click to expand...
Click to collapse
doesn't work
The "no baseband" thing sounds like that old recovery bug. Are you using the latest twrp or cwm?
Sent from my Nexus 4 using xda app-developers app
at4r1 said:
The "no baseband" thing sounds like that old recovery bug. Are you using the latest twrp or cwm?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The problem started when i was on stock ROM with stock recovery. It has nothing to do with twrp or cwm in this case
This is the third time trying to write this without my computer blowing up, so I'll be short. After five months of not using my N7 for certain reasons, I came home to update it to Kitkat as I was unable to do so before I came out. The OTA downloaded fine and, like updates before, I clicked install. Sadly, this time the installation did not work correctly, and I stupidly forgot to grab the error code that was thrown. After the failed installation, it went into a bootloop using the new boot screen, and with the boot screen graphic glitch I've seen other people complain about. I can get into Recovery Mode easy enough, which is running ClockworkMod Recovery v6.0.2.3. The bootloader is also unlocked. I've tried to do a factory reset from CWMR, but it hasn't helped.
I've gotten quite rusty with my skills in this work (as if I had any in the first place), so I thought coming here would be a good idea. Any thoughts on how to get Kitkat on working and proper?
nexus root toolkit
Download nexus root toolkit or unified android toolkit to your PC .Install drivers etc and do a factory restore using the KitKat factory image or the restore options in the toolkit
mrchaos429 said:
Download nexus root toolkit or unified android toolkit to your PC .Install drivers etc and do a factory restore using the KitKat factory image or the restore options in the toolkit
Click to expand...
Click to collapse
Thank you so much! Took a few minutes to figure it out, but my N7 is back up and running!
Hi everyone!
I am having very strange problem with stock rom "JORDN _U3_6.36.0" from T-Mobile USA on standard Defy. Each time i power phone up, it starts booting up then restarts itself in to stock recovery and perform hard/factory reset. After that it boots normally, but all settings gone.
I am not using T-mobile sim or moto blur account , so i skip registration using "ebluroff" trick. Is that can be the cause of the problem?
Some backstory: when i bought the phone it had CyanogenMod 7 installed on it. I used it for 2-3 years,even updated it several times up to 7.2.
Then some time ago i started having issues with it, so i had to flash stock rom with 2.1 Android.
I decided not to do anything with the phone, until i got some advice, so i any help would be greatly appreciated.
What were the issues faced? Anyhow one of the things you can try is to upgrade to 2.2, via rsd lite
Sent from my Nexus 5 using Tapatalk
thekguy said:
What were the issues faced? Anyhow one of the things you can try is to upgrade to 2.2, via rsd lite
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Well, thing is i want to keep my downgrade ability. I rooted the phone with superoneclick and install 2ndInit 1.4.2, but the problem is that it doesn't see SD card because it is Eclair. How people installed nandroid backups on 2.1? There has to be the way to move to 2.2 without flashing full SBF, because as i already mentioned it had CyanogenMod 7 when i bought it, so it is possible.
DEN383 said:
Well, thing is i want to keep my downgrade ability. I rooted the phone with superoneclick and install 2ndInit 1.4.2, but the problem is that it doesn't see SD card because it is Eclair. How people installed nandroid backups on 2.1? There has to be the way to move to 2.2 without flashing full SBF, because as i already mentioned it had CyanogenMod 7 when i bought it, so it is possible.
Click to expand...
Click to collapse
Some update. After hours of digging i found out these thread http://forum.xda-developers.com/showthread.php?t=899450
So, i first flashed defy 2.2_boot_only FIXED FSB, then after reboot custom recovery started working, so restored Droid22 rom from it.
Phew, i knew it was possible. So now i have rooted chines (?) android 2.2.1 on my phone and working custom recovery. I am gona stick on it for a while until i find best 2.3.3. nandroid ROM.
Just wanted to clarify was it right order - first flashing fixed SBF then restoring nandroid backup? I couldnt get custom recovery working without updating bootmenu first.
I also wanted to add that i did custom recovery data|cash wipe before flashing fixed SBF, before AND after restoring nandroid backup.
I saw that lots of people had problem like me , hope my message will help.
Here is link to another forum which has working download links http://www.addictivetips.com/mobile...ed-rooted-android-2-2-froyo-on-motorola-defy/