Hi guys i been searching everywhere, all over forums and google and i cant seem to figure out this issue, the issue is that i have a demo version of a 32gb touchpad, and basically i followed all the steps to install clockworkmod and moboot and all that stuff, once all that was completed i choose to install an android rom from the development section, and no matter what i do in clockworkmod, it just keeps restarting, it begins installing a rom and then just automatically restarts. it does that when i wipe cache aswell, i redid the entire process again and i get the same issue, everytime i try to install a rom or do a gaaps update it just restarts and nothing gets installed, Please let me know how to fix this issue
Sounds like you need to completely restart fresh. It could be because of the Demo setup of the TP, it doens't wanna allow CWM to work properly.
What I would do is read THIS THREAD and follow the instructions - it'll factory reset everything, but it'll then be ready for you to install CWM, Moboot, and CM9 again. I know it works cuz I just did it last night.
thanks alot buddy, it WORKED!!!!! now my touchpad finally has android, and webos, oh man android is amazing, my kid luvs it
Related
Bought a new color nook two days ago and began rooting it after i bought it using the walkthrough here. I made the bootable SD and that went fine. Put the Zip for nooter on there and that went on fine. I got on and created an account with the android marketplace and all. Then I got the Cyanogen mod from their site, the latest stable version and tried to install it. Got stuck at the color splash loading screen. Turned the unit off and have been constantly messing with it and got it to boot to CM7 but i have no google apps and when i press the home button i am still getting 3 options (Zeam, Softkeys, and something else).
I have tried numerous times reloading MN but it will get stuck at the n screen and not do anything. Sadly my idiot self didnt make a backup before i started rooting and the erase to factory in CWM doesnt do much.
Any ideas? It seems like i might be able to just get by with getting the gapps and putting them on but i dont think it will be that easy...
Thanks in advance for the help
UPDATE: Got the gapps to install but everytime i try and go to something in the market it force closes. Sounds like i need a wipe and start over but i am not sure..
make sure you have a class 2/4 sandisk(brand is what counts here).
Otherwise, I'd just reinstall everything over again through your cwm recovery disk.
As easy as it is to flash back to stock I just don't see the merit of running CM7 off a micro SD. Yes, it can be done, but if you're new to rooting your Nook my suggestion is to start over, wipe everything and install to internal memory.
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
uvii said:
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
Click to expand...
Click to collapse
I suggest flash 3-file GB rom via odin with ticked re-partirion and phone bootloaderupdate.
First of all init.d has nothing to do with the boot of kernel and ROM itself. It's just like autostart in Windows, so if it's missing it shouldn't cause problems.
My solution is to flash a complete stock Gingerbread ROM using Odin. You can get them at sammobile.com. Then afterwards flash a custom kernel and then whatever you like.
If you need help,feel free to ask me
Sent from my Gameboy Color
Yes! Thank you! That worked!!
It happened again! just 10 days later.
Is the Infinidtum rom ****ed up in any way?
it's stuck on the loading part of the rom
Hello. After i read/followed more than one tutorial on this matter, i rooted my milestone 1 and tried to install a custom rom to it. From the several attempts that i made, only miui installation was successful, even if after installation the recovery yellow triangle appeared, and had to make another "wipe data" and wipe cache", after which the phone started as normal. The problem is that i immediately figured that i don`t like miui, so, after following the same procedure, i tried over and over again to install cronos or cm7.2 kang, again with wiping data/cache, then wiping the last 3 options in the following menu. Everything seems to work fine, until i reboot the phone, and either enters recovery mode again, either stays with the motorola logo- i waited for about 7 minutes, but nothing happened. Can anyone tell me what am i doing wrong, because i did this over and over again.
I have a video with the whole process, but i can`t post any links here(it appears on my edydear21 account on flickr)
Any sugestions will be appreciated !
post scriptum: i eventually managed to get HO!NO! ics edition rom in the same way i did with the miui. Since i`m fed up with process of changing roms, i`l just settle fo the one i managed to get going.
Try out THIS guide. This one tells you what you need to do and how to do it.
Hello,
I am a noob trying to install a rom with aroma installer. But now it has been stuck at the page where it says: The installation wizard has successfully installed *********. Press next to exit.
What do i do? Power off?
Is it definitely stuck? Aroma doesn't always recognise touch events very accurately, and I usually have to tap the "next" button a few times before it registers. Failing that, if it's finished installing whatever you flashed, you should be fine to reboot manually anyway.
Yes,i have tried to push the next button many times but nothing happens. It has been like this for 30 minutes now. The successfully installed text appeared very fast, a second or two maybe after the previous screen. So if it has installed the rom, it was def a fast install.
Anyway, is it safe to try to reboot, even if it was in the middle of the install? Rebot to recovery and try again?
Well, there certainly isn't anything else to be done besides rebooting. I don't know what you were trying to install - if it was a several-hundred-MB ROM, as most things that use Aroma are, you would expect it to take a while. Smaller things can be flashed very quickly. If it _did_ go wrong somewhere, there are a few things:
1. What recovery, and what version thereof, are you using?
2. Did you wipe data before using the installer?
3. Most of all, what were you trying to install? There might be some known issue with certain configurations.
I wouldn't necessarily expect a working OS when you reboot, depending on what you were trying to install and how badly things went wrong, but you should be able to get back into recovery easily enough.
Thank you for your quick reply.
1. I use the CWM recovery in this http://forum.xda-developers.com/showthread.php?t=1914394 thread, not the newest, but 5.5 something i believe.
2. Yes, wiped all data + dalvik.
3. I was trying to install rXTREME on my SGS III lte i9305.
I've rebooted now, and everything works perfect as the phone was before i tried to do the install. No brick. I also tried to flash it one more time, but stuck at the same place again. Rebooted fine at stock rom again. Maybe i should take this as a hint that someone else should be put at the steering wheel.. :laugh:
EDIT: forgot link above
Found out what the problem was.
In Aroma Installer i selected EFS backup both times. The third time i tried i did not do this. And everything went fine. Runs smooth.
my galaxy s3 international version got stuck at 30% of formatting\data partition while trying to flash s4 revolution 4.1 rom
what should i do?
jehad.drarjeh said:
my galaxy s3 international version got stuck at 30% of formatting\data partition while trying to flash s4 revolution 4.1 rom
what should i do?
Click to expand...
Click to collapse
This is I9305 forum is this your phone ??
This thread is about Aroma installer is that your problem ???
Suggest you read the basic faqs and guides first looks like from your post you are either flashing wrong rom to your phone or have hijacked a thread in the wrong forum ./
jje
Hello...
I'm new to all of this rooting, installing and so( used to do this years ago on my LG KP500 Cookie ), so I'm not sure what to look/search for when I'm in this "bad" spot.
I used my sony xperia SP, but I did not like the current version of android it was, as it was lagging, hanging and other weird stuff, so I've decided to try and install the "lollipop" version. Since the guide I followed was detailed, I got it all working perfectly fine, until I tried to install gapps. After installing them, my phone started crashing / hanging on booting, which kept kicking it back to "SONY" screen, and from there it's just an endless loop.
so I tried to wipe and use backup that I had saved, so I could try and reinstall the ROM. It ended up at where I can't do anything anymore. I start my phone - "SONY" screen and nothing else. Can't access the CWM recovery, it doesn't progress anywhere, just sits there.
I'm lost. I don't know what to do Please help ;~;
Digital Noodle said:
Hello...
I'm new to all of this rooting, installing and so( used to do this years ago on my LG KP500 Cookie ), so I'm not sure what to look/search for when I'm in this "bad" spot.
I used my sony xperia SP, but I did not like the current version of android it was, as it was lagging, hanging and other weird stuff, so I've decided to try and install the "lollipop" version. Since the guide I followed was detailed, I got it all working perfectly fine, until I tried to install gapps. After installing them, my phone started crashing / hanging on booting, which kept kicking it back to "SONY" screen, and from there it's just an endless loop.
so I tried to wipe and use backup that I had saved, so I could try and reinstall the ROM. It ended up at where I can't do anything anymore. I start my phone - "SONY" screen and nothing else. Can't access the CWM recovery, it doesn't progress anywhere, just sits there.
I'm lost. I don't know what to do Please help ;~;
Click to expand...
Click to collapse
it's ok...please try to flash t-kernel v2.2 twrp via fastboot mode ...thread link
need further help? ...quote this post and i'll replay ....but always do some searching then ask
good luck :good: