Database Users

weird soft brick... help please

I flashed the clockworkmod touch zip from my recovery.
It didn't give me the touch recovery, I thought "whatever" and booted back into my rom.
It wouldn't boot.
I went back into recovery and flashed PA rom and gapps.
They weren't booting, I decided to give them a few minutes.
It finally booted.
It no longer connects to wifi or tmobile.
I can't transfer files over usb.
Wugfresh's toolkit couldnt return it to stock.
I thought the recovery might have gotten messed up when I tried to flash CWM touch, so I flashed TWRP from Wugfresh's toolkit.
I used adb sideload to flash a stock rooted rom.
It still took forever to boot, and is still not connecting to wifi/network.
TL;DR I can boot into fastboot and recovery and even the rom but I have no network connection... help guys :'(
It says BASEBAND VERSION - N/A... could that be the problem? If so, how do I fix it?

This is why we don't use toolkits. Return to stock using ADB and do it again...
Sent from my Nexus 4 using xda premium

When I try to fastboot flash the stock image it says "does not contain recovery.sig" "does not contain boot.sig" and only updates the bootloader.

Did you dl the image right from Google?
Sent from my Nexus 4 using xda premium

ethan.r.besbris said:
Did you dl the image right from Google?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yup.. this one https://developers.google.com/android/nexus/images#occam

So I just flashed the radio by itself and its working fine now thanks for your help man.

No problem. Glad you're up and working.
Sent from my Nexus 4 using xda premium

*****

[Q] Recovery issues after OTA update to 4.3

I was on stock 4.2.2 with TWRP installed and I took the OTA to 4.3. Now whenever I try and access my recovery it dispays the Android mascot lying on its back, chest open with a red triangle with an exclamation mark above. I tried flashing TWRP 2.6 via fastboot twice but I still get the same error. How can I fix this? Thank you!

What Fastboot command did you do?, toolkits can't help on 4.3.
The android getting operated on is a security feature so criminals cannot get your data, it is Volume up and power to access the stock recovery on that screen.
Sent from my Nexus 4 using Tapatalk 4

Same exact situation. Stock 4.2.2 with TWRP installed (version 2.6) and then did the OTA. Losing TWRP and root in this situation is normal. I also could not reinstall TWRP the normal fastboot way, and then I saw the following on several forums, and it installed jut fine:
fastboot-windows -c "lge.kcal=0|0|0|x" flash recovery recovery.img

pjc123 said:
Same exact situation. Stock 4.2.2 with TWRP installed (version 2.6) and then did the OTA. Losing TWRP and root in this situation is normal. I also could not reinstall TWRP the normal fastboot way, and then I saw the following on several forums, and it installed jut fine:
fastboot-windows -c "lge.kcal=0|0|0|x" flash recovery recovery.img
Click to expand...
Click to collapse
I managed to fix this after trying a variety of things. All I had to do was rename the downloaded TWRP file and flash using "fastboot flash recovery twrp.img" and it worked flawlessly.

andyabc said:
What Fastboot command did you do?, toolkits can't help on 4.3.
The android getting operated on is a security feature so criminals cannot get your data, it is Volume up and power to access the stock recovery on that screen.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
What do you mean by toolkits cant help?!
I still can root my 4.3 JB via toolkits like wugfresh etc?! Right?!
And i too got the same problem couple of days back while rooting manually, so finally had to flash stock.
Sent from my Nexus 4 using xda premium

ssbnasa said:
What do you mean by toolkits cant help?!
I still can root my 4.3 JB via toolkits like wugfresh etc?! Right?!
And i too got the same problem couple of days back while rooting manually, so finally had to flash stock.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Rooting your device running 4.3 by booting a unsecure 4.2.2 kernel?, not really what I had in mind and not really recommended what so ever...
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
Rooting your device running 4.3 by booting a unsecure 4.2.2 kernel?, not really what I had in mind and not really recommended what so ever...
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
No not about booting an unsecure kernel, i'm talking about using toolkits for rooting 4.3 via toolkit :|
They're goog to go right?!
Sent from my Nexus 4 using xda premium

ssbnasa said:
No not about booting an unsecure kernel, i'm talking about using toolkits for rooting 4.3 via toolkit :|
They're goog to go right?!
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well the kernel may contain something which allows support and causes no damage so yes.
Sent from my Nexus 4 using Tapatalk 4

[Q] JWR66Y breaks root and recovery???

I was running 4.3 stock rooted and yesterday was prompted to update to JWR66Y, thinking this would be no big deal i decided to update. later on that day i decided i was bored with stock android and went to flash cm10.2, but the update has seemed to wipe TWRP off my nexus 7 and has also broken root..
does anybody know how to fix this??? the internet has provided no answer and i would very much like to enjoy the freedom of having a rooted nexus..
thanks to anyody that can help! :fingers-crossed:

If you had searched well you knew that booting a stock ROM after sn update almost always replaces the custom recovery by stock recovery. The easiest way to reflash your custom recovery is using fastboot, I.e.
fastboot flash recovery <recovery.img>
while you are in fastboot mode.
Sent from my Nexus 7 using xda app-developers app

smiley118118 said:
I was running 4.3 stock rooted and yesterday was prompted to update to JWR66Y, thinking this would be no big deal i decided to update. later on that day i decided i was bored with stock android and went to flash cm10.2, but the update has seemed to wipe TWRP off my nexus 7 and has also broken root..
does anybody know how to fix this??? the internet has provided no answer and i would very much like to enjoy the freedom of having a rooted nexus..
thanks to anyody that can help! :fingers-crossed:
Click to expand...
Click to collapse
Hi, I had this same problem today with my rooted nexus 4 on stock.
AndDiSa said:
If you had searched well you knew that booting a stock ROM after sn update almost always replaces the custom recovery by stock recovery. The easiest way to reflash your custom recovery is using fastboot, I.e.
fastboot flash recovery <recovery.img>
while you are in fastboot mode.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
This did not work for me unfortunately. I tried to fastboot flash both latest TWRP and CWM. Neither one sticks and it's pissing me off.

Recovery won't flash

I had to do a complete wipe from the computer and flashed clockwork mod recovery. Since it was likely an old version I had the double 0 partition problem which I fixed by manually moving the files. I tried to update the recovery to twrp, but it won't flash using goomanager. It downloads and says it's flashed but it's not there.
I also seem to have a weird problem where I have to push the power button to get it to boot past the Google screen. If I don't push power it gets stuck there forever.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk 4

Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.

SlowCobra96 said:
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4

T-Keith said:
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This might be an odd question, but have you tried just updating CWM first, and THEN flashing TWRP? Sometimes the flash won't go smoothly with an older version of one recovery to a newer version of a different recovery- not sure why, but that's just been my experience. I would update CWM first then try flashing TWRP.
Also, if goo is not working for you, you could try Rom Manager to update CWM and then flash TWRP. It can flash either. (If you really want to flash via the device).
Otherwise, (me personally) I'd just use adb fastboot to flash a new recovery.
Hope that helps

Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4

T-Keith said:
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
No problem. Let us know how it works out for you.

Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4

T-Keith said:
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Ahh, that sucks! How are you *attempting to* access recovery... via reboot menu, via adb, or via 3-button press? It shouldn't matter, but you could try all three methods to see if any way will give you recovery access. Then, if/when you manage to get in, you could reflash again straight from recovery. I'm going to do some digging to see if I can find a better solution. I KNOW I've read about the same issue before, I know there's a solution... I just have to find it again.
Worse comes to worse, you might have to reflash stock recovery then reflash custom recovery. Might be a corrupt recovery img, but I will check and try some things out and let you know what I find.
Edited to add:
Yes. there was a bug in the older bootloader that bypassed/refused access to recovery... so since you restored stock, you probably need to update your bootloader to at least to version 4.18 (via fastboot). THEN you should be able to access recovery. I can't add links, but I can give you a text link once I find just the IMG file instead of the full firmware. Honestly, I never do backups so I don't have the file on hand. However, I may do one backup at least so I can extract my boot img and give it to you.

OK, so I found the info I was looking for.
From Elsewhere:
Steps:
Install latest nexus 7 bootloader.
This fixes the boot loader bug and now you can enter recovery from the bootloader screen.
Update the bootloader to at least 3.18. Make sure NOT TO DELETE THE BOOTLOADER!!!!!!!!!!!!!
I cannot emphasize this enough!!!!!!!!!!! I bricked my first one this way.
Use
fastboot flash bootloader C:\>>>>>>\bootloader-grouper-3.18.IMG***
Click to expand...
Click to collapse
Do NOT erase bootloader before you flash the new one. And after you have flashed the new one type;
fastboot reboot bootloader
Click to expand...
Click to collapse
and check the bootloader version to make sure you succeeded.
Click to expand...
Click to collapse
***Or whatever you name the boot img file!***
https://dl.dropboxusercontent.com/u/19608328/boot.img.zip --> This is from MY Nexus 7. It's Bootloader version 4.23, and works with JB 4.2.2- it does NOT have the recovery access bug.
https://dl.dropboxusercontent.com/u/19608328/recovery.img.zip --> This is a copy of MY CWM, which I just updated to 6.0.3.6 yesterday.
I'd flash the bootloader, then flash your recovery of choice. Not being able to access recovery is a bootloader issue, not a recovery issue. The fact that you restored/reverted an older full firmware put you on an older bootloader that would not allow users to access recovery.
Try the new(er) bootloader, it should work. My device is a 16gb grouper Nexus 7 running 4.2.2. Before that, it ran 4.1.2 without any issues, so it should work to resolve the problem you're having.

Flash issues

I'm on twrp 2.6.3.0 and anytime I try and flash a new 4.4 ROM the install fails.
Sent from my Nexus 4 using xda app-developers app

wrong advice, my mistake... thanks for the reminding simms22.

But I wanna stay rooted
Sent from my Nexus 4 using xda app-developers app

You don't have to unroot. Just download and flash TWRP 2.6.3.2. On that build, they fixed the issues of 4.4 ROMS incorrectly flashing. Using it myself with no problems. Its in Original Android Development if I'm not mistaken

Flashing 4.4 Factory Image issues
Currently on my Nexus 4.
Android 4.3 Unlocked and Rooted
Kernel Version: 3.4.0-perf-gf43c3d9
Build: JWR66Y
Baseband: M9614A-CEFWMAZM-2.0.1700.84
Using ClockWorkMod Recovery v6.0.4.3, when trying to flash the 4.4 factory image .zip file on the SD Card I keep getting an "Installation Aborted" error after "Installing update..." step and the red Triangle on the android figure.
When attempting to sideload using stock recovery, getting a "Signature Verification Failed"
Any Suggestions? Thanks

darkfire2040 said:
I'm on twrp 2.6.3.0 and anytime I try and flash a new 4.4 ROM the install fails.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you haven't already tried it, under Mount uncheck system, that solved the problem for me.

Yeah I wanna stay in twrp so I will try flashing the latest. The error I'm getting is. Error while trying to update binarys
Sent from my Nexus 4 using xda app-developers app

will_chrome said:
you've got to unroot and back to stock rwcovery 1st if I'm not mistake. the guide to flash stock rom can be found in http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
wtf??? never ever give advice on android ever again!
op, all you have to do is update your recovery to twrp latest(v.2.6.3.3). flash your rom, flash your 4.4 gapps, and flash the latest supersu then reboot.

simms22 said:
all you have to do is update your recovery to twrp latest(v.2.6.3.3). flash your rom, flash your 4.4 gapps, and flash the latest supersu then reboot.
Click to expand...
Click to collapse
I will chime in on this one. I too have had constant failures with TWRP trying to flash ROMs lately. I'm running 2.6.3.3 and everything results in failure. I've tried the unchecking of system mount, multiple downloads with verified MD5s, sideloads, etc. Nothing is working.
Sent from my Nexus 4 using Tapatalk

ph37rd said:
I will chime in on this one. I too have had constant failures with TWRP trying to flash ROMs lately. I'm running 2.6.3.3 and everything results in failure. I've tried the unchecking of system mount, multiple downloads with verified MD5s, sideloads, etc. Nothing is working.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
next time you flash, after it fails, boot into the bootloader from the recovery. then, from the bootloader, go into the recovery again and flash.

simms22 said:
next time you flash, after it fails, boot into the bootloader from the recovery. then, from the bootloader, go into the recovery again and flash.
Click to expand...
Click to collapse
Recognizing your knowledge and experience so asking you to explain why that works. Does something in the internals get reset?
Sent from my Nexus 4 using Tapatalk

ph37rd said:
Recognizing your knowledge and experience so asking you to explain why that works. Does something in the internals get reset?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ill be honest, i dont know why. but i do know that it has worked for many. the alternative, which works 100% of the time, would be to delete your recovery, then flash it again. btw, did it work for you?

simms22 said:
ill be honest, i dont know why. but i do know that it has worked for many. the alternative, which works 100% of the time, would be to delete your recovery, then flash it again. btw, did it work for you?
Click to expand...
Click to collapse
I won't be able to experiment for a couple of weeks. I do know that I've wiped my phone four times or more in the last week with the 4.3 and 4.4 factory images and either manually or using one of the tool kits have added TWRP custom recovery and rooted the phone. Each time trying to flash a ROM it would result in a failure.
Next time I get the chance, I'll give your suggestion a shot and let you know. Are there logs I can capture that might prove useful?
Sent from my Nexus 4 using Tapatalk

ph37rd said:
I won't be able to experiment for a couple of weeks. I do know that I've wiped my phone four times or more in the last week with the 4.3 and 4.4 factory images and either manually or using one of the tool kits have added TWRP custom recovery and rooted the phone. Each time trying to flash a ROM it would result in a failure.
Next time I get the chance, I'll give your suggestion a shot and let you know. Are there logs I can capture that might prove useful?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
na. really the only 100% working fix is to delete the recovery, then reflash.

simms22 said:
na. really the only 100% working fix is to delete the recovery, then reflash.
Click to expand...
Click to collapse
So essentially I've done that with each factory image installed, correct? I'll have to read up on ADB and Fastboot to get the commands to remove the existing recovery. Will be a good way to kill some time (such the life I lead, being envious is not good for your soul)...
Sent from my Nexus 4 using Tapatalk

ph37rd said:
So essentially I've done that with each factory image installed, correct? I'll have to read up on ADB and Fastboot to get the commands to remove the existing recovery. Will be a good way to kill some time (such the life I lead, being envious is not good for your soul)...
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
no, you just flashed the next version of the recovery over the last. occasionally, something doesnt want to update in the partition, so clearing the previous recovery before flashing the new one will take car of it.

simms22 said:
no, you just flashed the next version of the recovery over the last. occasionally, something doesnt want to update in the partition, so clearing the previous recovery before flashing the new one will take car of it.
Click to expand...
Click to collapse
OK that confuses me. If using fastboot to place a new boot loader, radio, recovery and ROM are onto the phone and I have to 'fastboot flash recovery recovery.img' to replace the stock recovery that doesn't wipe out the stock recovery? Fabulous sentence structure.
Sent from my Nexus 4 using Tapatalk