Related
I was running cm-10 new 32gb Nexus 7 and decided to update to cm-10.1. It flashed fine but when I reboot it wont boot. If I flash again it boots fine but it doesnt matter how I flash...when I reboot it just goes into a bootloop (google black screen).
Please, any advice?
Sounds like the download is bad. Try downloading again and use adb to put it on the Nexus.
davisac said:
Sounds like the download is bad. Try downloading again and use adb to put it on the Nexus.
Click to expand...
Click to collapse
I rooted with the Tool Kit and the version was 4.1.1. After I rooted and unlocked, I flashed cm-10 stable. Used it for a while and everything was fine. Last night I flashed like 4 different ROMs with the same result...bootloop after a reboot. I noticed on the first ROM, when I finished the setup and rebooted. Should I go back to stock but with 4.2 using the Tool Kit and then root again?
Wally72 said:
I rooted with the Tool Kit and the version was 4.1.1. After I rooted and unlocked, I flashed cm-10 stable. Used it for a while and everything was fine. Last night I flashed like 4 different ROMs with the same result...bootloop after a reboot. I noticed on the first ROM, when I finished the setup and rebooted. Should I go back to stock but with 4.2 using the Tool Kit and then root again?
Click to expand...
Click to collapse
Yeah I would see if stock is doing that too. If so it sounds like something wrong with your device not the software.
Sounds like someone didn't do a factory reset between flashes....
Sent from my Nexus 7 using Tapatalk HD
davisac said:
Yeah I would see if stock is doing that too. If so it sounds like something wrong with your device not the software.
Click to expand...
Click to collapse
Pirateghost said:
Sounds like someone didn't do a factory reset between flashes....
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I have TWRP and this bootloop only happens on 4.2 ROMs. 4.1.2 runs fine, and I flashed it afterwards to see if it is the tablet. It Reboots fine with 4.1. As far as factory reset...I rather flash clean, so YES I did the full wipe.
Thx for your replys guys. I really appreciate it.
Wally72 said:
I have TWRP and this bootloop only happens on 4.2 ROMs. 4.1.2 runs fine, and I flashed it afterwards to see if it is the tablet. It Reboots fine with 4.1. As far as factory reset...I rather flash clean, so YES I did the full wipe.
Thx for your replys guys. I really appreciate it.
Click to expand...
Click to collapse
What version of TWRP are you using? You need to be on the latest for 4.2 roms. 2.3.3.0 I think.
davisac said:
What version of TWRP are you using? You need to be on the latest for 4.2 roms. 2.3.3.0 I think.
Click to expand...
Click to collapse
I do have 2.3.3.0, but guess what....I found the problem! I was flashing M-kernel because I read that that kernel is great for playing games. Since I have a whole bunch of games, I decided to flash it. All the ROMs I flashed...I flashed with that kernel, and it booted fine. My issue was at reboot. Every time it put me on a bootloop. I just finished flashing grouper-M1 from CM, did my setup and rebooted, and booted fine!
Imma do some more reading to see if I can find a good kernel to run with cm-10.1.
Thank you daviac!!!!!:good:
Edit to the previous post and maybe it will help others:
The problem was not the kernel...IT WAS THE BOOTLOADERS version. I had to upgrade bootloaders. With adb I flashed the image and everything is fine!
Reading is fundamental...and I've learned my lesson!
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
There is a disclaimer before installing M-Kernel or probably any other kernel, that states that you need to be on the latest bootloader version. But it's ok, its best to learn from mistakes right?
Leonhan said:
There is a disclaimer before installing M-Kernel or probably any other kernel, that states that you need to be on the latest bootloader version. But it's ok, its best to learn from mistakes right?
Click to expand...
Click to collapse
Lol...after flashing I don't know how many ROMs and getting those bootloops...I went back to that thread and that's how I decided to flash the image. And you're right...some people like me just learn the hard way!!! Currently running Dirty AOKP with M-Kernel, and love it.
Thx!:thumbup:
Sent from my SGH-T889 using Xparent SkyBlue Tapatalk 2
Wally72 said:
Edit to the previous post and maybe it will help others:
The problem was not the kernel...IT WAS THE BOOTLOADERS version. I had to upgrade bootloaders. With adb I flashed the image and everything is fine!
Reading is fundamental...and I've learned my lesson!
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Hey, I got same problem with you.
How do you upgrade bootloader? My bootloader version is 4.1.3.
Thanks before.
inex_emo**** said:
Hey, I got same problem with you.
How do you upgrade bootloader? My bootloader version is 4.1.3.
Thanks before.
Click to expand...
Click to collapse
That's the latest version.
Hi,
I am currently running N4 on AT&T network, but as soon as I install any custom roms radio stops working. Kernels work fine stock and Semaphore. I tried with PA and Purity Roms latest and for both its the same. I tried re flashing bootloader and radios 84, 48, 27, 33Hybrid and 33 but makes no difference nor does the temporary fix suggested by going to *#*#INFO#*#*. It works fine if I restore to stock rom. Please suggest what might be going wrong here.
**Update**
After restore I see in about > baseband is 33. After installing custom rom in fastboot mode I see 33 but once phone is up it comes blank. What should I do to fix it.
Thanks
It is an issue with your current recovery. Some versions of CWM and TWRP cause issues with the radio resulting in an unknown baseband. Which one are you using? From what I know CWM 6.0.3.5 And TWRP 2.5.0.0. should fix your problems.
Sent from my Nexus 4 using xda app-developers app
xperimentul said:
It is an issue with your current recovery. Some versions of CWM and TWRP cause issues with the radio resulting in an unknown baseband. Which one are you using? From what I know CWM 6.0.3.5 And TWRP 2.5.0.0. should fix your problems.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I am running recovery-clockwork-6.0.4.3-mako, should that be an issue ?
dub123 said:
Thanks, I am running recovery-clockwork-6.0.4.3-mako, should that be an issue ?
Click to expand...
Click to collapse
From what I can recall, that version of CWM is one of the versions that causes radio issues. That recovery is your problem. Downgrade to an earlier version of CWM and your radio should be fixed.
Sent from my Nexus 4 using xda app-developers app
xperimentul said:
From what I can recall, that version of CWM is one of the versions that causes radio issues. That recovery is your problem. Downgrade to an earlier version of CWM and your radio should be fixed.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You sir are savior, switched to TWRP, created new recovery put in Pure Speed X and this time it works. Thanks. Someone should let them know version is broken as site still links back to it.
dub123 said:
You sir are savior, switched to TWRP, created new recovery put in Pure Speed X and this time it works. Thanks. Someone should let them know version is broken as site still links back to it.
Click to expand...
Click to collapse
Yes I'm not sure why it hasn't been addressed. Maybe it's not a widespread issue. Anyway, your're welcome and glad I was able to help.
Sent from my Nexus 4 using xda app-developers app
Hi,
This is the first time I've tried rooting a device so bare with me :good:.
It's taken me a few attempt to get things working on my Defy MB525 I've managed to root it with SuperOneClick and install either CWM 2.5.1.8 or SndInit2.3 (which uses CyanogenDefy Recovery v5.0.3.1). I'm now at a stumbling block where when I try to install a custom ROM on the device I keep getting...
"E:error in /sdcard/*ROM name*.zip
(status 0)
Installation Aborted"
Is there something I'm doing wrong or is it just the recovery programs I'm using?
What's the ROM you are trying to install?
themaker69 said:
What's the ROM you are trying to install?
Click to expand...
Click to collapse
I've tried a few now. The latest 4.4 alpha roms by Quarx, CM10 Android 4.1.2 also by Quarx and MokeeOS 43.1 and all come up with error.
Try to wipe the sdcard.
I'm downloading the file on a different computer as maybe the Antivirus on the work PC is messing it about. Also does the class of SDcard make a difference? It's only a class 4 8GB.
themaker69 said:
Try to wipe the sdcard.
Click to expand...
Click to collapse
Formatting it now.
novakanedj said:
I'm downloading the file on a different computer as maybe the Antivirus on the work PC is messing it about. Also does the class of SDcard make a difference? It's only a class 4 8GB.
Click to expand...
Click to collapse
No, the class has nothing to do. Use recovery to wipe, and not windows.
novakanedj said:
Hi,
This is the first time I've tried rooting a device so bare with me :good:.
It's taken me a few attempt to get things working on my Defy MB525 I've managed to root it with SuperOneClick and install either CWM 2.5.1.8 or SndInit2.3 (which uses CyanogenDefy Recovery v5.0.3.1). I'm now at a stumbling block where when I try to install a custom ROM on the device I keep getting...
"E:error in /sdcard/*ROM name*.zip
(status 0)
Installation Aborted"
Is there something I'm doing wrong or is it just the recovery programs I'm using?
Click to expand...
Click to collapse
4.1 should install. 4.3 and 4.4 need a newer recovery.
Sent from my Nexus 7 using Tapatalk
hotdog125 said:
4.1 should install. 4.3 and 4.4 need a newer recovery.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
novakanedj:
From 4.1 to 4.3 I installed using last TWRP. For 4.4 you need to use this.
hotdog125 said:
4.1 should install. 4.3 and 4.4 need a newer recovery.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Which recovery installs do the newer versions need and is there an install guide for these?
novakanedj said:
Which recovery installs do the newer versions need and is there an install guide for these?
Click to expand...
Click to collapse
For 4.3+ you need to first install 4.1/4.2 first to get the newer recovery.
Sent from my Nexus 7 using Tapatalk
Right I've just managed to get cm-10-20131030-NIGHTLY-mb526.zip to install from Quarx. Will let you know if the install is successful.:good: I would like to eventually install 4.4 KitKat when a more stable release is available.
edit: Succesfully installed . Just got to put Gapps on now.
Just install the zip from SDcard using your current custom recovery.
hotdog125 said:
For 4.3+ you need to first install 4.1/4.2 first to get the newer recovery.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I noticed that after I flashed with the 4.1.2 Quarx from there was a new bootloader on it. This should make it easier. I had to wipe and start again yesterday because I cocked up the Gapps install. In the end I went with the 30th Oct 2013 build of CM10 by Quarx and got the Gapps from www.goo.im/gapps. All seems to be running fine now and finished setting it up last night.
My girlfriend has a phone she can use now as her old one broke and she didn't want to use the Defy as the data couldn't be switched off on the stock ROM and would cost her a lot on her data plan (500MB a mth). Her Mum got a new contract with a Desire C so the Defy was going spare .
Can someone plz guide me on flashing the 4.4 Factory Image on the Nexus 4... iam rooted.with custom recovery n unlocked bootloader....
Sent from my Nexus 4 using xda app-developers app
Hmmy 4444 said:
Can someone plz guide me on flashing the 4.4 Factory Image on the Nexus 4... iam rooted.with custom recovery n unlocked bootloader....
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You have two option, do u want to start from zero?
You can:
Flash factory image from fastboot
Flash kit kat from recovery
luiseteyo said:
You have two option, do u want to start from zero?
You can:
Flash factory image from fastboot
Flash kit kat from recovery
Click to expand...
Click to collapse
please guide me through the easiest way.. cuz wen i on 4.2.2 i upgraded my phone to 4.3 through a toolkit.. n nw i am confused wat to do... plz guide me
The easiest way is described here for example:
http://forum.xda-developers.com/showthread.php?t=2010312
There are a lot guides available, pick one
Hmmy 4444 said:
please guide me through the easiest way.. cuz wen i on 4.2.2 i upgraded my phone to 4.3 through a toolkit.. n nw i am confused wat to do... plz guide me
Click to expand...
Click to collapse
Okay, but this is general section, not Q/A and should be there but today is Friday and I am tremendously happy lol
1. Download 4.4 Radio and 4.4 ROM. (say thanks to Imperticus)
2. Put both zips in your sdcard
3. Go to recovery and do: wipe data, wipe cache, wipe dalvik and format system (optional, advisable for upgrading to 4.4)
4. Flash Radio.zip
5. Flash ROM
U don't need any gapps since this is a factory image...
If you want a rooted/deodexed/busybox ROM download this one in stead of the other (say thanks to fireb33)
If u have any problem just let me know.
tom1807 said:
The easiest way is described here for example:
http://forum.xda-developers.com/showthread.php?t=2010312
There are a lot guides available, pick one
Click to expand...
Click to collapse
Well, that's the easiest way of flashing a factory image, but flashing a zip is even easier
Mod, please, move this thread
another thing wen ever i go to bootloader n then plug in my phone n type in command fastboot devices it say Waiting for device i jst dont understand wts going on?
Sent from my Nexus 4 using xda app-developers app
so flashing through zip we would get the same stock 4.4 as of the factory image ryt??
Sent from my Nexus 4 using xda app-developers app
n can we flash the factory image through wugfresh toolkit? n if we cn thn cn u plz guide me
Hmmy 4444 said:
n can we flash the factory image through wugfresh toolkit? n if we cn thn cn u plz guide me
Click to expand...
Click to collapse
Flash Stock+Unroot (choose 4.4 option), after that root and put recovery. check if radio and bootloader ok.
P.S.
I think it's good for 4.4. to wipe device and do clean one.
Hmmy 4444 said:
n can we flash the factory image through wugfresh toolkit? n if we cn thn cn u plz guide me
Click to expand...
Click to collapse
Please speak English
Sent from my Nexus 4 using Tapatalk
dethrat said:
Please speak English
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
you do realize that most the people here on xda do not use english as their first language? unfortunately not everyone here speaks or writes in english as well as you. hopefully you can understand that, and have a bit more patience and understanding, thank you.
simms22 said:
you do realize that most the people here on xda do not use english as their first language? unfortunately not everyone here speaks or writes in english as well as you. hopefully you can understand that, and have a bit more patience and understanding, thank you.
Click to expand...
Click to collapse
I know I'm not having a go or anything. Its just it sounded like text speak. Back on topic now.
Sent from my Nexus 4 using Tapatalk
ive gone and broken everything
ive never had issues updating various cyanogen versions once originally installed clockwork recovery. always been as simple as downloading and transferring the zip to SD and booting to recovery and installing from SD when i didnt do the auto updates which still took me to recovery at reboot. but i got impatient for the 4.4 version which reading from cyanongen is in no hurry to release because just released milestone version of 4.3. I downloaded the 4.4 zip right from google and tried installing it from SD like i always did after doing all the various wipes. The google factory image wasnt even recognized by clockwork. so doing some googling got here with steps to radio and os images got them transferred over and booted to recovery and they were at least selectable. got radio to go through. the actual os got error 7 during install, which doing even more googling said should edit a file in the zip contents. Too bad now cant get past the google logo and goes right back to recovery menus for me to transfer editted zip file for the error 7 problem. So im at least partially bootable but no clue how the heck to get myself out of this mess ive gotten myself into due to my impatience and wanting latest and greatest for my nexus 4. would love any help in how to undo problem i caused because the whole adb thing is foreign to me
simms22 said:
you do realize that most the people here on xda do not use english as their first language? unfortunately not everyone here speaks or writes in english as well as you. hopefully you can understand that, and have a bit more patience and understanding, thank you.
Click to expand...
Click to collapse
There's a difference between someone struggling with English and someone deliberately using text speak to sound all "1337."
Hey guys I just flashed 4.4 and everything is fantastic but when I go to storage it says I only have an 8GB(5.whatever free) model when I really have a 16GB...
Anyone else experienced this?
Hmmy 4444 said:
another thing wen ever i go to bootloader n then plug in my phone n type in command fastboot devices it say Waiting for device i jst dont understand wts going on?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hmmy 4444 said:
so flashing through zip we would get the same stock 4.4 as of the factory image ryt??
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
why are u confusing ur self. u are told the easiest way to flash thru zip. do that. thats it.
faddyie said:
why are u confusing ur self. u are told the easiest way to flash thru zip. do that. thats it.
Click to expand...
Click to collapse
plz help me, i flashed the factory image through flash-all.bat n everything went ok.. bt nw my device is stuck on the booting screnn where the nexus circle are moving n its not going any where plz help
After flashing the 4.4 factory image my phone storage show up 5.67GB internal storage. My phone is 16GB and it dones't have the same problem in 4.3. Anyone experience that? How can i solve the problem?
andy4023 said:
After flashing the 4.4 factory image my phone storage show up 5.67GB internal storage. My phone is 16GB and it dones't have the same problem in 4.3. Anyone experience that? How can i solve the problem?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2033692
you guys really need to search more
andy4023 said:
After flashing the 4.4 factory image my phone storage show up 5.67GB internal storage. My phone is 16GB and it dones't have the same problem in 4.3. Anyone experience that? How can i solve the problem?
Click to expand...
Click to collapse
did u get to solve ur problem???
On the n4 using purity rom 4.4.2 mako with a clean flash with Franco kernel Plus flashed but getting a message on supersu that the phone is not rooted and the Superus binaries aren't installed ... So re-rooted the phone with the n4 toolkit and everything went well but still supersu says phone is not rooted.... Help please!
Update binaries or download a recent cwm flashable supersu and flash it . Just Google it and you'll be o.k.
Sent from my Nexus 4 using XDA Premium 4 mobile app
bladebuddy said:
Update binaries or download a recent cwm flashable supersu and flash it . Just Google it and you'll be o.k.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How do you update the binaries because flashed the cwm update superus and I'm still getting the same message. Shown in the screen shot
jdpl123 said:
How do you update the binaries because flashed the cwm update superus and I'm still getting the same message. Shown in the screen shot
Click to expand...
Click to collapse
Go here, http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip
Download, Flash via recovery. Problem should be solved.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Go here, http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip
Download, Flash via recovery. Problem should be solved.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
That is the one I downloaded but after the flash and I click on reboot. A message saying that the rom may flash a stock recovery and gives me the option to disable the stock recovery or not. Is this normal... Btw the first time flashing I disabled don't want to click on no just in case of a brick so want to know what's the message is about...
jdpl123 said:
That is the one I downloaded but after the flash and I click on reboot. A message saying that the rom may flash a stock recovery and gives me the option to disable the stock recovery or not. Is this normal... Btw the first time flashing I disabled don't want to click on no just in case of a brick so want to know what's the message is about...
Click to expand...
Click to collapse
Nope. Never seen that message. Then again, I use twrp.
Sent from my Nexus 7 (2013)
Are you using latest cwm? But then again, this always happen with cwm. On twrp never have a single problem with supersu.
Berrydroidcafe said:
Nope. Never seen that message. Then again, I use twrp.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Ok using the toolkit can I switch to twrp with out any data loss or changes to the rom?
arffrhn said:
Are you using latest cwm? But then again, this always happen with cwm. On twrp never have a single problem with supersu.
Click to expand...
Click to collapse
Also Yes updated to the latest cwm.. Just want to use xposed and tweak some functions in trickster mod. If nothing else work do you guys know any good 4.4 roms that uses cm kernels?
jdpl123 said:
Ok using the toolkit can I switch to twrp with out any data loss or changes to the rom?
Click to expand...
Click to collapse
Yes you can flash TWRP without losing data or changes to the rom.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Yes you can flash TWRP without losing data or changes to the rom.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Thank you guys (and ladies) for the help. Switched to twrp and flashed binaries updated! (^o^)