Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
drsane1984 said:
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
Click to expand...
Click to collapse
jumping from one rom to another needs a full wipe i guess... when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
First of all, thank you for your reply!
Now, to adress each step
jumping from one rom to another needs a full wipe i guess.
Click to expand...
Click to collapse
Yup, did one (factory reset+system wipe) before trying to flash AW Rom.
when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
Click to expand...
Click to collapse
After the first three unsuccessfull attempt to flash the ROM did I wipe my internal SD, so it isn't the crawling looping intro's problem. And yes, I push ROMs via Adb, and trying flashing.
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
Click to expand...
Click to collapse
That was actually the last step I tried before asking for help. Even after I typed this post, I did it again. Flashed it, pushed AW, and flashed again. No success.
*Edit: I have forgotten a primary Troubleshooting technique. Downloading AW2.1 from a different source, will update.
sorry but im not much of a help i can see... hope somebody could. don't lose hope though...
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
drsane1984 said:
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
Click to expand...
Click to collapse
Hello Everybody! Guys, sorry for my english!!!!!
First of all, I have to present myself, my name is Marco, I'm italian, 25 years old and I'm in the Android world since about 12 Years.
I started whit a Galaxy S2, and after I bought an Asus Transformer Prime.
After just two week, I decided to put in a Custom ROM, on my devices, and I understood how the system work better instead of a Stock ROM!
And after, I understood, how the XDA Developers Forum is important for me, and expecially for all the people who like to learn about the Android World.
So, I just want to Thanks with all of you for the support that i receive EVERY DAY to solve my problems!
One of these was with flashing the Androwook, weeks ago I flashed the Team EOS 2.0, that was really amazing, but after a While, I found some slowdowns in some action on the system, so i decided to try a rom based on the stock rom, but with improvement and tweaks, so what's better then the Androwook?
The problem was, the same explained on this post, after all wipes, the prime was not boot, and stuck in bootanimation!
I solved, checking the box "Install custom ROM" as drsane1984 have done, and now the ROM is booted perfectly!!
Thanks another time! I'am convinced that if you are able to seach, you'll find for sure the solution to your problems! If not, just ask!
Bye!
Related
I had a working Cyanogen 7 flashed on the gTablet. And due to enthusiasm, I updated with one of the nightly builds and started seeing some issues.
I assumed that clearing the cache and rebooting would help and ended up doing the 'Wipe Cache Partition'. Now the tablet wont boot at all. But I guess its not bricked at all since I am able to get to CWM.
What do I need now to get back to CM7?
Also my search on what the 'wipe cache partition' function doesn't give me the full picture. Now I know that I shouldn't have done it in the first place. But being affected by it I request if one the Gurus on XDA's please shed some lite.
Regards and thanks for the help in advance.
venkavis said:
I had a working Cyanogen 7 flashed on the gTablet. And due to enthusiasm, I updated with one of the nightly builds and started seeing some issues.
I assumed that clearing the cache and rebooting would help and ended up doing the 'Wipe Cache Partition'. Now the tablet wont boot at all. But I guess its not bricked at all since I am able to get to CWM.
What do I need now to get back to CM7?
Also my search on what the 'wipe cache partition' function doesn't give me the full picture. Now I know that I shouldn't have done it in the first place. But being affected by it I request if one the Gurus on XDA's please shed some lite.
Regards and thanks for the help in advance.
Click to expand...
Click to collapse
Hopefully a guru can answer this question. A guru I am not..
But what I think you did should not be an issue. I typically wipe data and then wipe cache partition when flashing a new ROM. sometimes I wipe cache and data just to get the ROM running from scratch again. But this should not affect booting..
One thing I think might be the problem is that you have a new kernel from one of the newer nightlys. Recently they added perhsoots May kernel. Whenever a new kernel is included in a nightly you usually need to clear dalvik cache. this is in CWM under advanced.
I hope this helps.
Tried clearing dalvik cache. No change.
Going back to stock and see.
Copied the stock ROM file and used the CWM to do the update. Now the g Tablet is gioing into a Boot loop. It Tap n Tap then displays a animated icon and after a minute repeats the same.
Tried the recovery option and its going into an installing loop again. Not sure how to get out of this.
Does anybody have this experience before?
Is this bricked now? Call viewsonic support? I am not sure if they support, They may say its nor under warranty.
Just to remind you, the last effort to resolve this is to NVFLash it...
Have you tried CWM method twice or repartition it and do it again? It's a tablet for you to enjoy your Internet, reading, video but not flashing all day long..etc
To pass it quick, if I were you, I would NVFlash it back to 3588, put back my favorite ROM, reinstall the Apps I like and start Internet browsing, converting movie (so I can watch on the road), reading news...
good luck!
rcjpth
After this I definitely agree. But seems I am stuck again. Hope this is the last time.
I followed the steps as in the below URL
http://forum.xda-developers.com/archive/index.php/t-1040434.html
My PC successfully connected to the gTablet and did the bvflash. After that I booted, it still went into the same. I am not sure if the nvflash worked at all.
Not sure what I am missing here!
Called Viewsonic support and the tech support person pointed me to below post on XDA
http://forum.xda-developers.com/showthread.php?t=1036956
When I read the article it talks about a locked boot loader. Does is mean if I use this and fix the tablet, I will not be able to do any more rooting?
venkavis said:
I followed the steps as in the below URL
http://forum.xda-developers.com/archive/index.php/t-1040434.html
My PC successfully connected to the gTablet and did the bvflash. After that I booted, it still went into the same. I am not sure if the nvflash worked at all.
Not sure what I am missing here!
Click to expand...
Click to collapse
So you also tried the alternate file, nvflash_gtablet_46_2010112600.zip? That's what worked for me, but I also have to swap partitions 7 & 8 to get CM7 working again.
Since I'm a glutton for punishment, I wiped my cache from nightly 75 and didn't run into any problem.
Just downloaded the alternate zip and flashed again. Having the same looping issue.
Seems like I Have to send it to viewsonic only. The technician said there is a $75 charge to fix.
Hi All,
Just got my S2 last week. Planning to move to CM7 this weekend. I have rooted the device and am on the Codeworkx kernel. I had a few questions:
1. Is there a problem while flashing via Odin if Debugging is not enabled (I think it is more of a OS feature which we haven't entered when in download mode, so shouldn't matter according to me.) ? I tried to disable debugging, and then went to download mode and Odin did detect the phone, but I did not try to flash anything so if anyone has tried that, your input is more than welcome.
2. The reason for above question is: What if I completely brick my phone (with debugging disabled) and no ROM .zip in the sd storage, how do I get the phone up and running ? I understand that I can flash kernels via Odin, but is it true for ROMs as well ?
3. What's the issue with ROM manager ? Is it recommended to stay away from it for S2 ? I have tried to do a Nandroid backup and it always takes me to the Android robot with a exclamation mark screen. Then I have to reboot and the backup magically restarts and completes successfully. Most people have suggested to use CWM recovery directly, so not sure if I should get rid of the ROM manager altogether.
That should be all for now. I have a jig ready by the way, so am not that worried about the process and plan to do a fair bit of reading before proceeding, however, the answers to above queries would be really great !
Thanks in advance,
Ish
I can answer some of your doubts.
I don't know if you can flash via odin in case you don't have the usb debuggin enabled so I'm not going to say anything about it.
Anyway if something happens to your phone and you dont have any ROM on your sd card but you have CWM recovery installed (which is almost everytime the case) then in CWM there is a mount usb stoage option. With it you can easily transfer .zip ROM files to flash, or even a nandroid backup you saved in your PC.
ABout ROM manager, this is what I suggest you. The first time you flash CM7 don't use ROM Manager (I even tried using it with the codeworkx kernel with no luck). Now, once you are in CM7 it works perfectly and it's really helpful to flash nightlies withouth wiping data (I flash half the nightlies as they are realeased). So the first time you flash CM7 wipe everything (do a nandroid backup first), even wipe /system, /data, cache partition, dalvik cache, so you don't have any problems. THen install zip from sd card and when it finish install the zip file again (just two installs in a row no wiping in beween, trust me, the first time I tried I didn't do that and couldn't boot the phone).
Hope it helps.
EDIT: You can flash stock ROM via odin, there is a thread by infratech were this is explained and you have a list of downloable stock ROMS you can flash with Odin, these are region and carrier specific and you probably will get the one for your carrier. I found the stock ROM for my carrier and I'm from chile, you shouldn't have any problems with that. Well, good luck, CM7 is by far the best ROM I've flashed.
Oh another thing, go for the latest nightly since the battery life is incredibly improved over the RC (or was it stable?) version.
Thanks !
tomascunill said:
Anyway if something happens to your phone and you dont have any ROM on your sd card but you have CWM recovery installed (which is almost everytime the case) then in CWM there is a mount usb stoage option. With it you can easily transfer .zip ROM files to flash, or even a nandroid backup you saved in your PC.
Click to expand...
Click to collapse
Awesome ! This is exactly what I was looking for. I haven't dived into all the options of the CWM, so didn't know that this feature existed.
Also, many thanks for explaining most of the things in a single concise post, it was very helpful. I'll have to check the ROM flash with Odin, so I will search for that thread and have a go through it later today.
Once I get a hang of CM7, I'll go in for the nightlies as well. And yes, I did read about the CM7 guys revert the status to an RC because of the bugs reported, so will give it a try once I definitely know what I'm getting into .
Thanks again,
Ish.
cheemais said:
Awesome ! This is exactly what I was looking for. I haven't dived into all the options of the CWM, so didn't know that this feature existed.
Also, many thanks for explaining most of the things in a single concise post, it was very helpful. I'll have to check the ROM flash with Odin, so I will search for that thread and have a go through it later today.
Once I get a hang of CM7, I'll go in for the nightlies as well. And yes, I did read about the CM7 guys revert the status to an RC because of the bugs reported, so will give it a try once I definitely know what I'm getting into .
Thanks again,
Ish.
Click to expand...
Click to collapse
Well good luck! Tell me if you get any problem.
Hi guys, so i decided to install the new CM10 so i already had root, i unlocked using the official tool, then installed CWM from Rom manager.
I then downloaded CM10 and GAAPS and kept them in a folder and also copied them to an sd card for safety.
I booted into CWM sucessfully, took a deep breath, then did a full wipe/factory restore, then wiped Cache, then wiped Dalvik Cache.
Then i proceeded to TRY to flash CM10.......... Firstly, CWM didn't list my external SD Card so i selected from the one i had saved on the internal storage.
It began to do the install then failed stating something about symlinks??? I retried the install and got the same thing.
I rebooted the Prime and now it's just stuck on the Eee Pad splash screen with "The Device Is Unlocked" written in the top left corner and it wont do anything else.............
I can reboot into CWM but how can i fix this and get CM10 installed??
PLEASE help!?!?!?!?!?
Thanks in advance.
Currently, no recovery can access external memory of any sort. Did you make a backup? Is it in the internal memory? Make sure you can flash back to your original settings BEFORE trying to flash something as experimental as CM10.
Please remember any Jelly Bean roms are highly experimental, and probably won't work correctly for everyone.
Read this thread for more help:
http://forum.xda-developers.com/showthread.php?t=1514088
I thought I replied to my own post shortly after the original post. I ended up rebooting into CWM and starting over again from the start and everything went smoothly. I endedup not liking the fact that flash and YouTube aren't supported yet so I flashed CM9 instead and I'm loving that.
Predtechhacker said:
I thought I replied to my own post shortly after the original post. I ended up rebooting into CWM and starting over again from the start and everything went smoothly. I endedup not liking the fact that flash and YouTube aren't supported yet so I flashed CM9 instead and I'm loving that.
Click to expand...
Click to collapse
Good to hear. One last advice is to use TWRP instead of CWM. CWM has issues with the prime while TWRP is more stable.
Predtechhacker said:
I thought I replied to my own post shortly after the original post. I ended up rebooting into CWM and starting over again from the start and everything went smoothly. I endedup not liking the fact that flash and YouTube aren't supported yet so I flashed CM9 instead and I'm loving that.
Click to expand...
Click to collapse
so how many time had u gone back then tried it.... i have the same problem i tried it like 10 times but it still stuck
what step did u do
I'm stuck in the same predicament! Did you just keep trying, and it finally worked????
hey guys, first post here: i just bought the atrix 4g, got it in the mail today, used the 1-click rooter to unlock the bootloader, then to root. then i installed cyanogenmod 9- i followed instructions appropriately, but the phone hangs at the motorola logo screen at boot-up and does nothing more. i tried re-flashing, fixing permissions, clearing dalvik cache, nothing works.
edit- i installed cyanogenmod9 through clockworkmod, by installing zip from internal
i was going to re-flash stock rom, but i cant get internal storage to mount from clockworkmod (no sd card), so i cant get the stock file over to the phone to flash, so im bricked.
any thoughts/advices? thanks in advance, after not having a phone for near a week, id kinda like to make a call
leopard_fist said:
hey guys, first post here: i just bought the atrix 4g, got it in the mail today, used the 1-click rooter to unlock the bootloader, then to root. then i installed cyanogenmod 9- i followed instructions appropriately, but the phone hangs at the motorola logo screen at boot-up and does nothing more. i tried re-flashing, fixing permissions, clearing dalvik cache, nothing works.
edit- i installed cyanogenmod9 through clockworkmod, by installing zip from internal
i was going to re-flash stock rom, but i cant get internal storage to mount from clockworkmod (no sd card), so i cant get the stock file over to the phone to flash, so im bricked.
any thoughts/advices? thanks in advance, after not having a phone for near a week, id kinda like to make a call
Click to expand...
Click to collapse
Did you try using fastboot to erase system, data, cache, and osh partitions?
Sent from my MB860 using xda app-developers app
edit
leopard_fist said:
hey guys, first post here: i just bought the atrix 4g, got it in the mail today, used the 1-click rooter to unlock the bootloader, then to root. then i installed cyanogenmod 9- i followed instructions appropriately, but the phone hangs at the motorola logo screen at boot-up and does nothing more. i tried re-flashing, fixing permissions, clearing dalvik cache, nothing works.
edit- i installed cyanogenmod9 through clockworkmod, by installing zip from internal
i was going to re-flash stock rom, but i cant get internal storage to mount from clockworkmod (no sd card), so i cant get the stock file over to the phone to flash, so im bricked.
any thoughts/advices? thanks in advance, after not having a phone for near a week, id kinda like to make a call
Click to expand...
Click to collapse
You bricked your phone, not cyanogenmod ...
Restore a backup, your phone should work.
hm, can anyone tell me, why i cant get internal storage to mount from clockworkmod? is this a common problem?
i dont understand what went wrong for me, when i followed the same steps that many others did.
epinter said:
You bricked your phone, not cyanogenmod ...
Restore a backup, your phone should work.
Click to expand...
Click to collapse
Your phone is not a paperweight, just not boot the operating system
You did a backup with CWM? restore a backup as Emerson says
You can borrow a sd card copy there CM7 and install from the sdcard
You can also use RDS to install a stock rom
Never install a rom without having an one that you know works 100%
AND ALWAYS READ ALL FAULTS AND SOLUTIONS BEFORE INSTALLING A CUSTOM ROM
ok guys, i went and bought an sd card, clockworkmod mouted it fine, i found and copied over to the sd card android 2.34 for atrix, it flashed fine and my phone is back up.
can you gentleman tell me, whats a good solid rom to flash? cyanogen mod 9 obviously didnt work for me. id like to get started setting up the phone, so i need a good rom to begin with.
thanks to everyone in advance
Go with montouri's version of cm7.2 ,mrom-Olympus you can find it in the developer section. Its my daily driver. Its the most stable and has the best battery life out of all the roms that I've tried
motoxrcr1 thanks for the recommendation, running m-rom now and it runs smooth.
the first time i tried to install it, it hung at the boot logo, then i got to thinking maybe i better try updating clockworkmod, turned out that clockworkmod 4.0X that was installed by the 1-click rooter, is rather old, so i found and updated to 5.XX. tried re-flashing m-rom again, and it worked fine that time.
older clockworkmod, that's probably what caused my original problem with cyanogenmod 9..
does mrom support overclocking? not that i guess i need it, but just to know for future reference
thanks!
the trouble i caused myself, was all due to flashing the rom from an older version of clockworkmod.. after updating to a newer version 5.xx, it flashed fine
delete
Hi everyone,
I would like to preface with I made some very stupid mistakes late last night/early this morning. I decided at around 11pm I was going to root and install a custom recovery on my SGP311. I followed this guide exactly to obtain root and recovery and it worked PERFECTLY.
http://forum.xda-developers.com/xperia-tablet-z/development/root-sp321-ftf-10-5-1-0-283-t2873377
Then the mistakes started happening. First mistake I made.
1) Instead of backing up everything in recovery I just Wiped everything. I deleted cache, davlik cache, system, and data. I thought at the time no big deal ill just flash a rom.
2)I decided to flash a CM nightly and I got the "your device is a pollux and this rom is for pollux_windy" error and assumed I was wrong. I downloaded the pollux version, and flashed it. That was the dumbest thing I did. I booted and immediately started looping at the cyanogenmod screen.
3) I attempted to troubleshoot by flashing firmware and kernels through Flashboot. It made it worse and now I cant get into recovery at all.
Here is the positives
I can connect to the device through Flashmode and Fastboot.
What should I do next to remedy this situation?
TheShackSpecialist said:
Hi everyone,
I would like to preface with I made some very stupid mistakes late last night/early this morning. I decided at around 11pm I was going to root and install a custom recovery on my SGP311. I followed this guide exactly to obtain root and recovery and it worked PERFECTLY.
http://forum.xda-developers.com/xperia-tablet-z/development/root-sp321-ftf-10-5-1-0-283-t2873377
Then the mistakes started happening. First mistake I made.
1) Instead of backing up everything in recovery I just Wiped everything. I deleted cache, davlik cache, system, and data. I thought at the time no big deal ill just flash a rom.
2)I decided to flash a CM nightly and I got the "your device is a pollux and this rom is for pollux_windy" error and assumed I was wrong. I downloaded the pollux version, and flashed it. That was the dumbest thing I did. I booted and immediately started looping at the cyanogenmod screen.
3) I attempted to troubleshoot by flashing firmware and kernels through Flashboot. It made it worse and now I cant get into recovery at all.
Here is the positives
I can connect to the device through Flashmode and Fastboot.
What should I do next to remedy this situation?
Click to expand...
Click to collapse
I just quickly read your post from work but since you wiped it and can no longer boot your tablet...just flash back a stock FTF with FlashTool and your tablet will back to full stock...you'll have to re-root obviously. Hope this helped... :good:
Crash338 said:
I just quickly read your post from work but since you wiped it and can no longer boot your tablet...just flash back a stock FTF with FlashTool and your tablet will back to full stock...you'll have to re-root obviously. Hope this helped... :good:
Click to expand...
Click to collapse
I'm downloading the FTF right now, Ill let you know how I make out so that people can see the resolution!
*EDIT* IT WORKED!!!! I missed the simple solution because I am so tired right now. But my tablet is working which is the important part THANK YOU!!!!