Related
Tried installing different roms and it still reboots back into recovery and have also tried flashing other recoveries any help?
http://forum.xda-developers.com/showthread.php?p=17258229
Sent from my LG-P999 using Tapatalk 2
djvoleur said:
http://forum.xda-developers.com/showthread.php?p=17258229
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
im actually on that right now lol hope it works
I tried it and it worked was able to boot into device into stock however I flashed CW and tried to install a custom rom on it and it just reboots into cm again
Of course it works... because it happened to me too
Sent from my LG-P999 using Tapatalk 2
My device was working just fine in the A.M. as I flashed from Genesis (ICS) back to Lezo OS (GB) over to Joy OS (also GB). When I tried to restore a backup of my Genesis ROM I was more than delighted to see that upon trying to reboot I was unable to boot out of recovery. Now I've done everything in the linked post up to about step 10 where I kinda get stuck. I run the Flash but get nothing. At this point I'm just hoping for a Solid solution. Someone PLEASE assist
Boot_Derran said:
My device was working just fine in the A.M. as I flashed from Genesis (ICS) back to Lezo OS (GB) over to Joy OS (also GB). When I tried to restore a backup of my Genesis ROM I was more than delighted to see that upon trying to reboot I was unable to boot out of recovery. Now I've done everything in the linked post up to about step 10 where I kinda get stuck. I run the Flash but get nothing. At this point I'm just hoping for a Solid solution. Someone PLEASE assist
Click to expand...
Click to collapse
Try this way. Anytime I soft brick my G2x, this is how I rebuild it.
You'll need that ROM you got from previous thread, I do believe.
It will push a fresh recovery, than you can just go back to flashing the ROM.
justjackyl said:
Try this way. Anytime I soft brick my G2x, this is how I rebuild it.
You'll need that ROM you got from previous thread, I do believe.
It will push a fresh recovery, than you can just go back to flashing the ROM.
Click to expand...
Click to collapse
Edit: I have then since followed the directions EXACTLY and now I'm back in business. Much appreciated
Boot_Derran said:
Edit: I have then since followed the directions EXACTLY and now I'm back in business. Much appreciated
Click to expand...
Click to collapse
Your welcome. Glad i could steer you in the right direction and it worked for you!
Sent via Acer Iconia A100 on CM10_Build090212; godmachine v2.0 kernel, Smooth, Stable, Fast
if rebooting loop caused by installing new soft, try looking at this thread. its helped me
http://forum.xda-developers.com/showthread.php?t=2451696
http://get.cm/?device=grouper&type=nightly
LATEST GAPPS: http://d-h.st/rDK
Tonight, when everyone else is sleeping, the folks over at CyanogenMod are hard at work, as always. The team just announced a brand new addition to the slew of CM releases: M-Series. From now on (provided the community approves), the team will begin rolling out builds that are "a bit more stable" at the beginning of every month. Prior to this initial release of CM10-M1, the group did a "soft freeze of the codebase" in an attempt to stabilize the builds, so these should be more reliable than your average
Here's the list of devices that builds are currently
Galaxy Nexus GSM (maguro)
Galaxy Nexus VZW (toro)
Galaxy Nexus Sprint (toroplus)
Galaxy S2 GT-I9100G (i9100g)
Galaxy S (galaxysmtd)
Galaxy S B (galaxysbmtd)
Captivate (captivatemtd)
Galaxy S3 Sprint (d2spr)
Galaxy S3 VZW (d2vzw)
Galaxy S3 AT&T (d2att)
Galaxy S3 TMO (d2tmo)
Galaxy S3 US Cellular (d2usc)
Nexus S 4G (crespo4g)
Galaxy Note AT&T (quincyatt)
Google Nexus 7 (grouper)
Sony Xperia Acro S (hikari)
Sony Xperia S (nozomi)
As always, nightlies will continue to be available, but for the slightly less adventurous among you, this effort should provide a healthy middle ground between bleeding edge, and waiting on stable RCs for your device. It will also help casual users keep a frame of reference for the progression of everyone's favorite ROM. If you'd like to get in on the action, you can download the M1 builds here.
Click to expand...
Click to collapse
Edited to add gapps link.
That's interesting, Thanks!
That's excellent, excellent news.
I can't seem to find the CM10 section here on XDA for the N7.
Would like to know the pre-requisites and info and how to flash, which recovery to install, what to wipe, etc...
mmoreimi said:
That's excellent, excellent news.
I can't seem to find the CM10 section here on XDA for the N7.
Would like to know the pre-requisites and info and how to flash, which recovery to install, what to wipe, etc...
Click to expand...
Click to collapse
I'm not sure about their official instructions but my way:
Use CWM recovery.
Full wipe if coming m anything other than cm10. (I full wipe anyways)
Flash cm10 M1
Wipe dalvik cache/cache
Flash latest gapps (quick Google search will find you the latest job gapps
Reboot and enjoy.
Well, flashed and booted. Here we go.
mmoreimi said:
That's excellent, excellent news.
I can't seem to find the CM10 section here on XDA for the N7.
Would like to know the pre-requisites and info and how to flash, which recovery to install, what to wipe, etc...
Click to expand...
Click to collapse
I would say do a Full wipe, then flash Rom,
Sent from my HTC Desire using Tapatalk 2
mmoreimi said:
That's excellent, excellent news.
I can't seem to find the CM10 section here on XDA for the N7.
Would like to know the pre-requisites and info and how to flash, which recovery to install, what to wipe, etc...
Click to expand...
Click to collapse
wipe data, cache, dalvic cache, and system at least (data and cache may be labeled factory reset in the recovery wipe menu)
I only run TWRP but that's a personal preference
So this is like a RC with more experimental stuff in it?
Sent from my Nexus 7 using xda app-developers app
Harry GT-S5830 said:
So this is like a RC with more experimental stuff in it?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What it sounds like is they freezed one of the nightlies and stopped adding new stuff and just worked on stability. They'll probably do this once a month or so.
Guys I flashed this version and kind of bricked the Nexus. I stuck at the booting animation for couple of minutes but nothing will happen. When try to entre recovery, stuck at screen of Google and unlocked bootloader sign. Any ideas what to do now?
jirkadus said:
Guys I flashed this version and kind of bricked the Nexus. I stuck at the booting animation for couple of minutes but nothing will happen. When try to entre recovery, stuck at screen of Google and unlocked bootloader sign. Any ideas what to do now?
Click to expand...
Click to collapse
It's a known issue, grouper has sometimes problems to reboot into recovery ; when you're on the bootloader, plugg it in to your computer, and then reboot to recovery, that should work....or reboot to recovery and plugg it in....
and if you really get stuck, then you can use adb and open a command, but you must have adb drivers on your computer for that (if you don't, follow instructions on mskip's Toolkit thread), or at last, use the toolkit to reflash your recovery, then it will work....
http://forum.xda-developers.com/showthread.php?t=1809195
yeah i know, kinda pain in the ass... ...but your N7 isn't bricked...
kptnk said:
It's a known issue, grouper has sometimes problems to reboot into recovery ; when you're on the bootloader, plugg it in to your computer, and then reboot to recovery, that should work....or reboot to recovery and plugg it in....
and if you really get stuck, then you can use adb and open a command, but you must have adb drivers on your computer for that (if you don't, follow instructions on mskip's Toolkit thread), or at last, use the toolkit to reflash your recovery, then it will work....
http://forum.xda-developers.com/showthread.php?t=1809195
yeah i know, kinda pain in the ass... ...but your N7 isn't bricked...
Click to expand...
Click to collapse
Well I suppose I got the drivers, but when I get to the fastboot, and plug it into computer, the fast boot freeze and it does not react on anything. I even tried to reflash CWM via mentioned tool box, but it will stuck at Waiting for device message... Yeah and I'm running Windows 8. So maybe there is the problem...then probably I ****ed it by the drivers...
jirkadus said:
Well I suppose I got the drivers, but when I get to the fastboot, and plug it into computer, the fast boot freeze and it does not react on anything. I even tried to reflash CWM via mentioned tool box, but it will stuck at Waiting for device message...
Click to expand...
Click to collapse
then you surely don't have the proper drivers installed i guess
kptnk said:
then you surely don't have the proper drivers installed i guess
Click to expand...
Click to collapse
Probably....Lookign for solution now... drivers for W8 or Install virtual PC with W7 and try it through it...
jirkadus said:
Well I suppose I got the drivers, but when I get to the fastboot, and plug it into computer, the fast boot freeze and it does not react on anything. I even tried to reflash CWM via mentioned tool box, but it will stuck at Waiting for device message... Yeah and I'm running Windows 8. So maybe there is the problem...then probably I ****ed it by the drivers...
Click to expand...
Click to collapse
There is another option. Don't flash the recovery permanently, that worked for me.
Sent from my SGH-T999 using xda app-developers app
jirkadus said:
Probably....Lookign for solution now... drivers for W8 or Install virtual PC with W7 and try it through it...
Click to expand...
Click to collapse
Ah wih windows 8 it's a bit tricky...i followed this and it worked :
http://laslow.net/2012/03/14/disable-driver-signature-enforcement-in-windows-8/
SOLVED! THANKS GUYS!
I manually instaled drivers using Toolkit in this thread http://forum.xda-developers.com/showthread.php?t=1766475. I used the RAW drivers... then flashed CWM using the Nexus 7 Toolkit and wiped data/flashed CM10 /wipe partitions... and its done...
I already clicked thanks, but not sure if it is enough.... THANKS again!
jirkadus said:
SOLVED! THANKS GUYS!
I manually instaled drivers using Toolkit in this thread http://forum.xda-developers.com/showthread.php?t=1766475. I used the RAW drivers... then flashed CWM using the Nexus 7 Toolkit and wiped data/flashed CM10 /wipe partitions... and its done...
I already clicked thanks, but not sure if it is enough.... THANKS again!
Click to expand...
Click to collapse
Glad it worked.... i know, i had the same issue on first day...
Last time I tried CM10 on my Nexus 7 it seemed like the tablet thought it was like a "phone" version of the rom. Is this still the case or is it optimized for the tablet now?
rudolphe said:
Last time I tried CM10 on my Nexus 7 it seemed like the tablet thought it was like a "phone" version of the rom. Is this still the case or is it optimized for the tablet now?
Click to expand...
Click to collapse
Install Apex Launcher or any launcher that supports tablet mode, then you MUST change the DPI to 160
(edit: im not sure if CM10 launcher has tablet mode, I believe it should have, I only use APEX)
http://forum.xda-developers.com/showthread.php?t=1749501
Hi !
I have a TF101 model "B80". Some time ago I flashed CWM 5.5.0.4, and now, I just can't flash any other recovery over it. I know it's a common issue, i tried everything I found on the www to fix it, with no success. Of course I have this "always reboot in recovery" bug too.
Is there someone to help me out there ? Thanks !
vince4 said:
Hi !
I have a TF101 model "B80". Some time ago I flashed CWM 5.5.0.4, and now, I just can't flash any other recovery over it. I know it's a common issue, i tried everything I found on the www to fix it, with no success. Of course I have this "always rebbot in recovery" bug too.
Is there someone to help me out there ? Thanks !
Click to expand...
Click to collapse
Use easy flash and push different recovery, my personal advice is, use twrp recovery.. very handy and extremely useful... look for easy flash/easy flasher thread under android development. Read carefully and follow steps get a different recovery...
Sent from my Transformer using xda app-developers app
Thanks for your fast answer, looks like it worked !
I've been using TWRP for a while now. I installed it directly from the goo.im app. It's pretty flawless.
Sent from my Galaxy Nexus using Tapatalk 2
Hi,
i have a Xoom and it wont install any ROMS. It is a wingray model and it gets status 7 (symlink) when installing CM10 and errors when install Superuser.zip. It isnt recovery as GAPPS install. Its running CWM and i cant get the tablet to boot up. I also used HWI69.zip and restored the images and no its askes for a password? Wth? But I really want CM10 back on my tablet. I restored ALL the images. Can i get rid of this password screen?
Please help
It has a password screen. what does that even mean? is that encrpyted from the seller as I can ask the seller to put it in... What am i even meant to do?
weeo said:
Hi,
i have a Xoom and it wont install any ROMS. It is a wingray model and it gets status 7 (symlink) when installing CM10 and errors when install Superuser.zip. It isnt recovery as GAPPS install. Its running CWM and i cant get the tablet to boot up. I also used HWI69.zip and restored the images and no its askes for a password? Wth? But I really want CM10 back on my tablet. I restored ALL the images. Can i get rid of this password screen?
Please help
Click to expand...
Click to collapse
Boot into fastboot, then unlock it
Code:
fastboot oem unlock
Mjamocha said:
Boot into fastboot, then unlock it
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Hi,
Thank you for reply but I got it working. It's on 3.01 now but how do I root this properly and get it on CM10?
weeo said:
Hi,
Thank you for reply but I got it working. It's on 3.01 now but how do I root this properly and get it on CM10?
Click to expand...
Click to collapse
Universal Root
or
7Heavens Projekt
Mjamocha said:
Universal Root
or
7Heavens Projekt
Click to expand...
Click to collapse
It'll have to be 7heavens as the other one hasn't got a download link. File has been deleted
Thanks
weeo said:
It'll have to be 7heavens as the other one hasn't got a download link. File has been deleted
Thanks
Click to expand...
Click to collapse
The universal root - has the links witin the instructions. I just tried the links and they are valid.
Mjamocha said:
The universal root - has the links witin the instructions. I just tried the links and they are valid.
Click to expand...
Click to collapse
Have you got a rooted Xoom? Could you take me through the process as it never works for me
Sent from my Xoom using xda app-developers app
weeo said:
Have you got a rooted Xoom? Could you take me through the process as it never works for me
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
How far have you got? Have you unlocked the bootloader through fastboot?
Once that's done it's fairly easy. Just fastboot flash a custom recovery. I recommend Team Rogues recovery: http://forum.xda-developers.com/showthread.php?t=1235170
then reboot the device, but go into recovery before the device boots or the recovery is overwritten. To get into recovery: power on, 2 seconds later press the down button, then press the up button once you see 'Android Recovery'
Then flash the zip I have attached to root the device. Choose the JB one if you're on jelly bean, anything else, so honeycomb or ICS use the other one.
From there it's the same as any other device. Backup apps etc, make a nandroid, wipe data/factory reset, install CM10
matt4321 said:
How far have you got? Have you unlocked the bootloader through fastboot?
Once that's done it's fairly easy. Just fastboot flash a custom recovery. I recommend Team Rogues recovery: http://forum.xda-developers.com/showthread.php?t=1235170
then reboot the device, but go into recovery before the device boots or the recovery is overwritten. To get into recovery: power on, 2 seconds later press the down button, then press the up button once you see 'Android Recovery'
Then flash the zip I have attached to root the device. Choose the JB one if you're on jelly bean, anything else, so honeycomb or ICS use the other one.
From there it's the same as any other device. Backup apps etc, make a nandroid, wipe data/factory reset, install CM10
Click to expand...
Click to collapse
Oh ok. I'll flash that as I'm on honeycomb. Will report back if I get a status 7 again.
weeo said:
Oh ok. I'll flash that as I'm on honeycomb. Will report back if I get a status 7 again.
Click to expand...
Click to collapse
That's something to do with CM reads the device as XOOM but on stock a wingray is MZ604 so if I remember rightly that's what causes the status 7, to get around it, once rooted use a build prop editor to change your model to XOOM not MZ604. I think that's the way to get around it if my memory serves me well
matt4321 said:
That's something to do with CM reads the device as XOOM but on stock a wingray is MZ604 so if I remember rightly that's what causes the status 7, to get around it, once rooted use a build prop editor to change your model to XOOM not MZ604. I think that's the way to get around it if my memory serves me well
Click to expand...
Click to collapse
Thank you. So that's what a sym link error is?
weeo said:
Thank you. So that's what a sym link error is?
Click to expand...
Click to collapse
Don't me hold to it, but I seem to remember others getting status 7 errors and it was just to do with how the CM zip reads your device. You can also turn off script verification in android recovery. I think that was also another solution
matt4321 said:
Don't me hold to it, but I seem to remember others getting status 7 errors and it was just to do with how the CM zip reads your device. You can also turn off script verification in android recovery. I think that was also another solution
Click to expand...
Click to collapse
Thanks. Doing it now. Just install SU. Good luck with Gigatechworld... formerly known as Orion... BTW i know this as im your website owners friend.
weeo said:
Thanks. Doing it now. Just install SU. Good luck with Gigatechworld... formerly known as Orion... BTW i know this as im your website owners friend.
Click to expand...
Click to collapse
Glad you got everything working alright. Cheers. sweet! you know friends through xda or you actually know know him? if you know what I mean
matt4321 said:
Glad you got everything working alright. Cheers. sweet! you know friends through xda or you actually know know him? if you know what I mean
Click to expand...
Click to collapse
XDA. We've been friends for 2 years. I use to make ROMS for the ZTE blade. I think he started talking to me when I made HTC Sense with a few others on the blade. I have him the idea for Orion
weeo said:
XDA. We've been friends for 2 years. I use to make ROMS for the ZTE blade. I think he started talking to me when I made HTC Sense with a few others on the blade. I have him the idea for Orion
Click to expand...
Click to collapse
that's pretty awesome! I remember you over at modaco, used to be fairly active there as the zte blade has a big community there but the xoom has a bigger one here. how come you didn't come aboard with us on the blog?
matt4321 said:
that's pretty awesome! I remember you over at modaco, used to be fairly active there as the zte blade has a big community there but the xoom has a bigger one here. how come you didn't come aboard with us on the blog?
Click to expand...
Click to collapse
I was active a lot here too. Till I shut my account down. I already have my own website. That's where the idea was set off from.
Success, CM10 is booting on my Xoom .
weeo said:
I was active a lot here too. Till I shut my account down. I already have my own website. That's where the idea was set off from.
Success, CM10 is booting on my Xoom .
Click to expand...
Click to collapse
That's awesome!
Nice to hear you have CM10 running too, so much better than stock
matt4321 said:
That's awesome!
Nice to hear you have CM10 running too, so much better than stock
Click to expand...
Click to collapse
Thanks to you
Sent from my Xoom using XDA Premium HD app
So I've been more of a stalker of the XDA community for a while, never really needed to ask a question because I usually find the answers on the boards pretty handily or by some fluke things work for me without the need to post anything. But now that time has come to an end.
I had Jellybam 4.1.2 on my device flashed with whatever kernel came with it, and when my battery died yesterday the phone was stuck in a boot loop. Keep in mind that prior to that 1) It had never done this on a reboot and 2) the correct kernel had been flashed via fastboot. My hboot is 1.14. The reason I'm not posting this question in the Jellybam post in android development is because 1) I'm a n00b to posting on here and 2) this is now happening with any other rom I install (most recent is MIUI which I flashed late last night, started up normally, then got caught in a boot loop on a reboot).
I follow the normal steps of going into TWRP, flashing cache/davlik, factory wipe, system wipe, then installing, doing the gapps if necessary, or following the instructions on any aroma installers, then rebooting into fastboot and flashing the kernel so i don't get boot loops on the initial start up. I'm also doing this on a mac, but the command lines in terminal are pretty straight forward and i'm just doing normal ADB / fastboot commands.
I'm perplexed now and I can't figure out what changed or what I did differently that's causing this. Any help would be most appreciated and I apologize if this is somehow a cross or repeat post, but I couldn't find much like it.
Do you have an Evita or Endeavour phone?
Sent from my HTC One XL using xda premium
It sounds like you are doing everything correct. Also seems like you have a good grasp of what to do. My thought is even if your initial install went though. Something in the bootimg may be corrupt. Perhaps try redownloading your preferred rom? And try again.
Sent from my One X using xda premium
ToxicWaste said:
Do you have an Evita or Endeavour phone?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Evita
subarudroid said:
It sounds like you are doing everything correct. Also seems like you have a good grasp of what to do. My thought is even if your initial install went though. Something in the bootimg may be corrupt. Perhaps try redownloading your preferred rom? And try again.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I've tried a couple times with the same result. I'll try again and see if anything different happens. Maybe just by some miracle I'll get it working again
I'm not sure how it works with safari for Mac. I do know that when I download ROMs with crome it some how downloads corrupt zips. On ei9 it works fine.
Sent from my One X using xda premium
uncledoobie said:
So I've been more of a stalker of the XDA community for a while, never really needed to ask a question because I usually find the answers on the boards pretty handily or by some fluke things work for me without the need to post anything. But now that time has come to an end.
I had Jellybam 4.1.2 on my device flashed with whatever kernel came with it, and when my battery died yesterday the phone was stuck in a boot loop. Keep in mind that prior to that 1) It had never done this on a reboot and 2) the correct kernel had been flashed via fastboot. My hboot is 1.14. The reason I'm not posting this question in the Jellybam post in android development is because 1) I'm a n00b to posting on here and 2) this is now happening with any other rom I install (most recent is MIUI which I flashed late last night, started up normally, then got caught in a boot loop on a reboot).
I follow the normal steps of going into TWRP, flashing cache/davlik, factory wipe, system wipe, then installing, doing the gapps if necessary, or following the instructions on any aroma installers, then rebooting into fastboot and flashing the kernel so i don't get boot loops on the initial start up. I'm also doing this on a mac, but the command lines in terminal are pretty straight forward and i'm just doing normal ADB / fastboot commands.
I'm perplexed now and I can't figure out what changed or what I did differently that's causing this. Any help would be most appreciated and I apologize if this is somehow a cross or repeat post, but I couldn't find much like it.
Click to expand...
Click to collapse
My phone did this once too. Never figured out why but the way I stopped it was to nandroid data, then wipe everything, reinstall the Rom and restore only data. After this it never bootlooped again.
Sent from my Venom1 XL using Xparent Red Tapatalk 2
ImagioX1 said:
My phone did this once too. Never figured out why but the way I stopped it was to nandroid data, then wipe everything, reinstall the Rom and restore only data. After this it never bootlooped again.
Sent from my Venom1 XL using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Ok, I'll give that a shot. I installed CleanRom 5.1 today, ran some reboots and that seemed to clear it up. It might be a Jellybean thing, but who knows. Thanks for all the suggestions and quick responses!
Oh yea there is some discussion about a Rev-a or rev-b that is on your box having issues with 4.2 jb not working. I think its rev-b that everyone is having issues with.
Sent from my One X using xda premium