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.
Related
Hello.
I just downloaded the OTA update from the google servers (VQ8PQk_V.zip) and applied it.
My baseband version appeared as "Unknown", so, in my infinite wisdom, I decided to flash the XXKF1-GRK39F radio through fastboot.
The problem is that it's been stuck at "writing 'radio'..." for more than 15 mins now. What should I do?
EDIT:
I have a NANDROID backup from just before the update. If I pull out the battery and restore it, will my radio restore, too?
...why don't you flash radio via recovery ?
Ok, I solved it. Here's how:
-since I was stuck at "writing 'radio'..." I did a battery pull.
-installed the Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader Flashable rom from the ALL-OTA thread.
-restored my nandroid backup
Everything's back to normal and I'm back on 2.3.6. Gonna wait for the official i9023. For a moment there, I thought I ruined my phone.
I have tried a couple of custom roms since I got this phone, but I'm not completely comfortable with everything.
huh....funny enough, I applied the update again, and this time the radio updated properly. everything works fine
Hi
I am using a Nexus S I9023 (India). I just updated my phone to 4.0.3 using the ROM file downloaded from XDA today. Now, there is no signal, it doesn't even read my sim card. It says the same msg under Baseband version, "unknown". except this everything else seems to work fine. I have not taken any back also before the upgrade.
Please help.
I do have the same problem: My Nexus S i9023 had 2.3.6 Stock ROM and after the Update, the Baseband/Network/IMEI/etc is UNKNOWN. How can I get back 2.3.6.?
rajkumar2000 said:
Hi
I am using a Nexus S I9023 (India). I just updated my phone to 4.0.3 using the ROM file downloaded from XDA today. Now, there is no signal, it doesn't even read my sim card. It says the same msg under Baseband version, "unknown". except this everything else seems to work fine. I have not taken any back also before the upgrade.
Please help.
Click to expand...
Click to collapse
Use fastboot to flash custom recovery. And then flash the full stock 2.3.6 and await the OTA.
Mopkorn said:
I do have the same problem: My Nexus S i9023 had 2.3.6 Stock ROM and after the Update, the Baseband/Network/IMEI/etc is UNKNOWN. How can I get back 2.3.6.?
Click to expand...
Click to collapse
The ota you are flashing patches the radio KF1, you guys are probably are on a different radio and the radio doesn't patch correctly.
This is the full rom ota 4.0.3, just flash and everything will work http://android.clients.google.com/packages/ota/google_crespo/ZD3PyN0t.zip[/QUOTE]
Sent from my Nexus S using xda premium
Ok I installed Custom Recovery and the .zip you posted, it seems working, thank you very much!
reddv1 said:
The ota you are flashing patches the radio KF1, you guys are probably are on a different radio and the radio doesn't patch correctly.
This is the full rom ota 4.0.3, just flash and everything will work http://android.clients.google.com/packages/ota/google_crespo/ZD3PyN0t.zip
Click to expand...
Click to collapse
Sent from my Nexus S using xda premium[/QUOTE]
you sir are correct. Fixes my signal issues
Sorry for the noob question as I can't seem to easily find the answer through search but how do you flash the this other 4.0.3 rom? Running ICS already from the other rom (VQ8PQk_V.zip).
Can I just do this again using the fastboot? Although I've tried going back to recovery and it doesn't work, as has been stated in the forum. The fixes for the recovery look complicated and require rooting (I think). I haven't rooted my i9023 yet.
jpacs2007 said:
Sorry for the noob question as I can't seem to easily find the answer through search but how do you flash the this other 4.0.3 rom? Running ICS already from the other rom (VQ8PQk_V.zip).
Can I just do this again using the fastboot? Although I've tried going back to recovery and it doesn't work, as has been stated in the forum. The fixes for the recovery look complicated and require rooting (I think). I haven't rooted my i9023 yet.
Click to expand...
Click to collapse
Yeah, fastboot should work.
Sent from my Nexus S using XDA App
oh my god....
i have upgrade my gingerbread to ICS today.
but my IMEII is missing. di don' know why.
i have nandroid backup but i don't have EFS Backup.
so, how can i get that IMEII back.
just restore backup from nandroid??
--> sorry if my english is bad..
athani said:
Use fastboot to flash custom recovery. And then flash the full stock 2.3.6 and await the OTA.
Click to expand...
Click to collapse
Thanks for the reply, the first sign of hope for my phone in 2 days!!!
I am not so familiar with these things. Can you please tell me how to do a fastboot and post a link to the 2.3.6 update that I need to use.
Thank you so much once again.
---------- Post added at 12:19 PM ---------- Previous post was at 12:12 PM ----------
Mopkorn said:
Ok I installed Custom Recovery and the .zip you posted, it seems working, thank you very much!
Click to expand...
Click to collapse
Hey
I understand that your problem is fixe. I have the same problem still can you please guide me on how to solve this problem please.
Thanks.
Hello, same problem for me but and I don't understand what is the solution...
Some says flash custom recovery, some just flash with the ZD3PyN0t.zip... and I don't even know what flashing is (if it requires rooting or not) mine is not as you can imagine...
Can someone guide me a little please ? Don't want to break my phone more than it is !
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 .
Here you go folks. The miui v5 3.11.29 official for HTC ONE is released
http://en.miui.com/download-111.html
For MIUI English Forum
> http://en.miui.com/download-111.html
Harish_Kumar said:
For MIUI English Forum
> http://en.miui.com/download-111.html
Click to expand...
Click to collapse
we still need to install 4.2.2 gapps in this rom.
saketh91 said:
we still need to install 4.2.2 gapps in this rom.
Click to expand...
Click to collapse
Oh you completed installing the rom?
i guess first we need to install the kernal and then flash the rom..right?
this is the first time i am trying an official MIUI rom!
Harish_Kumar said:
Oh you completed installing the rom?
i guess first we need to install the kernal and then flash the rom..right?
this is the first time i am trying an official MIUI rom!
Click to expand...
Click to collapse
I don't know abt the kernel but I am loving this rom so far. No lags, the UI is perfect fit for the screen and loving some features like DND, IR etc..,
but the only thing missing is the gapps. We need to install separately i think. Loving the Internationalized weather widget too.
I get build prop problem, who else got it ?
hth2813 said:
I get build prop problem, who else got it ?
Click to expand...
Click to collapse
you mean while installing?. It installed perfectly for me on TWRP 2.6.3.0
saketh91 said:
you mean while installing?. It installed perfectly fine for me on TWRP 2.6.3.0
Click to expand...
Click to collapse
Yeah, what is your current rom, cid, mid ?
hth2813 said:
Yeah, what is your current rom, cid, mid ?
Click to expand...
Click to collapse
I was using SD v11.1 before and now installed this rom with no issues. Mine has supercid. I still don't understand what you meant abt build prop problem. Where did you get that error? While installing or while modifying the build prop in the rom?
saketh91 said:
I was using SD v11.1 before and now installed this rom with no issues. Mine has supercid. I still don't understand what you meant abt build prop problem. Where did you get that error? While installing or while modifying the build prop in the rom?
Click to expand...
Click to collapse
I got that problem while installing ROM, i am in GPE 4.4
I'm also getting a status 7 getprop error in recovery.
hth2813 said:
I got that problem while installing ROM, i am in GPE 4.4
Click to expand...
Click to collapse
Ok there can be different reasons for this.
1.May be a bad download. Try downloading it again.
2.May be you did not clean flash it by wiping cache,system,data. Try wiping everything except internal storage and try again.
3.May be the recovery you are using doesn't support installing this rom. Try TWRP 2.6.3.0 I got it installed perfectly with that.
4.And finally the firmware which you are on. If it is GPE firmware then try switching to sense before flashing this. I had hell lot of problems with GPE firmware like unlocking the bootloader, installing the roms etc..,
May be these are not the reasons for your problem but just give it a try and report back
Droid69 said:
I'm also getting a status 7 getprop error in recovery.
Click to expand...
Click to collapse
You get status 7 error only in three cases.
1.You edited the updater script in the rom
2.You did not download the rom properly.
3.Mainly you are not using the right recovery. Try using TWRP 2.6.3.0 or higher may be.
saketh91 said:
You get status 7 error only in three cases.
1.You edited the updater script in the rom
2.You did not download the rom properly.
3.Mainly you are not using the right recovery. Try using TWRP 2.6.3.0 or higher may be.
Click to expand...
Click to collapse
1. No
2. Could be a bad download, i will download it again and retry.
3. Im on the latest.
Droid69 said:
1. No
2. Could be a bad download, i will download it again and retry.
3. Im on the latest.
Click to expand...
Click to collapse
ok before you re download just try installing it with TWRP 2.6.3.0 too because i faced some problems earlier with the latest TWRP. Just give a try
saketh91 said:
ok before you re download just try installing it with TWRP 2.6.3.0 too because i faced some problems earlier with the latest TWRP. Just give a try
Click to expand...
Click to collapse
Rom flashed with TWRP 2.6.3.0 thanks.
Ah, i have just tried CWM Recovery and it installed successful
Droid69 said:
Rom flashed with TWRP 2.6.3.0 thanks.
Click to expand...
Click to collapse
Glad you got it installed perfectly!!
hth2813 said:
Ah, i have just tried CWM Recovery and it installed successful
Click to expand...
Click to collapse
Nice to hear that you got it installed perfectly.:laugh:
hth2813 said:
I get build prop problem, who else got it ?
Click to expand...
Click to collapse
yep the same 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^)
Hi Guys
I suspect this might be quite simple but I seem to be missing something, I rooted using towelroot but when wanting to flash new RON ( Assassin )
when I boot into recovery the little android dude is lying down with a red warning triangle on top and it says ...no command...
I can select the file from SD but it doesn't start flashing.
I'm no wiz at this but did mange on my note 2 with the dittonote3 ROM
Have I missed a step somewhere ????
j_hansen said:
Hi Guys
I suspect this might be quite simple but I seem to be missing something, I rooted using towelroot but when wanting to flash new RON ( Assassin )
when I boot into recovery the little android dude is lying down with a red warning triangle on top and it says ...no command...
I can select the file from SD but it doesn't start flashing.
I'm no wiz at this but did mange on my note 2 with the dittonote3 ROM
Have I missed a step somewhere ????
Click to expand...
Click to collapse
It needs custom recovery[emoji12]
Sent from my SM-N9005 using Tapatalk
You should really do some more reading...
Sent from my N9005
Rosli59564 said:
It needs custom recovery[emoji12]
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I did install CWM
j_hansen said:
I did install CWM
Click to expand...
Click to collapse
That lying down android dude should only be seen in stock recovery. You flashed custom recovery but it was overwritten by stock i guess. Did you see other option such as back up and restore?
Sent from my SM-N9005 using Tapatalk
Rosli59564 said:
That lying down android dude should only be seen in stock recovery. You flashed custom recovery but it was overwritten by stock i guess. Did you see other option such as back up and restore?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Cheers man, at least now I know where the problem is, I should be able to figure it out by doing a bit more reading
I just flashed the Assassin rom using mobile odin so I'll try and go from there and see if it is still on stock recovery once rebooted etc..
CWM didn't take the first time. Check you have the right version for your Model/OS - reflash it, then you're good to go :good:
radicalisto said:
CWM didn't take the first time. Check you have the right version for your Model/OS - reflash it, then you're good to go :good:
Click to expand...
Click to collapse
That was exactly it, downloaded again and seem all good, thanks a million for your help :good: