[Q] CyanogenMod taking a long time to boot on first go...... - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Hi,
I just attempted to put my first ROM on my note - CM10.
I followed the rooting instructions on root galaxy note dot com (I can't post the link cos this is my first post apparently)
which seems to go fine, the only difference was that once I got CWM on I just picked the CM10.zip and rebooted. It's been sitting with the CyanogenMod boot animation for 40 minutes now, I worried I screwed it up.
Given I'm a noob at this and didn't make a back up is there a way for me to get a ROM back on the device that will actually boot up for me? Or have I forked it up.
Any help appreciated!

1. Go back into recovery mode (volume up + power + home buttons)
2. Wipe data, and cache. Then select advance in order to wipe dalvik and battery stats.
3. To be safe, reinstall the SuperSU and CWM as per zedomax video.
4. Reboot to system.
5. Then download abysnotekernel. Reboot recovery.
6. Flash abyssnotekernel
7. Then flash CM10
8. Pray that all went well
Hope this helps..
Sent from my GT-N7000 using xda app-developers app

Related

stuck at i896 splash screen [stock rogers]

This is basically an extension of this post: http://forum.xda-developers.com/showpost.php?p=28994789&postcount=3
However this is a different problem so I think it deserves its own thread.
marcknight said:
Try this..
1. Return back to stock, using the method from the same post you mentioned. (it shows you how towards the bottom)
Note:
a. you can also get the phone into download mode by just holding onto the volume buttons "both" together!! and then plugging in the usb
connector from ur PC/laptop.
b. once in download mode, please see that Odin detects your phone, it will have a yellow highlight with COM (something like that written on it)
c. if not you need to have the right drivers!
2. Download the Slim ICS package again and move it to your phone's internal SD card
3. Dowload gapps and move it to your phone's internal SD card.
4. Download the devil kernel --> here
5. Follow the steps mentioned in the post you followed, after flashing the speedmod kernel which has CWM, go into CWM and flash the ICS ROM.
6. If the phone reboots or gets stuck, remove battery and restart phone!
7. Give it some time to boot. Once it does, reboot into recovery and flash Gapps, reboot(not required but still.. ) flash the kernel you downloaded.
8. Should work fine!
Hope this helps Enjoy.
**Always perform clean install**Always have a backup**
Click to expand...
Click to collapse
I just tried this and I was unable to flash anything with CWM after flashing Slim ICS.
I wasn't able to install any zips from my internal or external hard drive for some reason. I let it reboot afterwards and the same boot loop happened.
I tried reflashing it to stock (which was how I fixed it last time) but now it's stuck at the I896 logo screen and it wouldn't boot further. I can still get it into dl and recovery mode but reflashing the stock rom doesn't solve this.
Note that wipe data/factory reset doesn't seem to remedy this either. Any ideas on how I can get my phone back to a working state (again) guys?
Thread closed
No, you really should stick to your original thread.

Galaxy S Problems - Need Help Fast!

Ok so I have been looking around for two days now and have not been able to find an answer to my problem. I've even searched and tried everything on these forums so please don't ask me to google or use the forums search.
I've got a Bell Canada Samsung Galaxy S GT-I9000M, it was working fine a few days ago and I picked it up to check my messages and it was frozen. After a few minutes I pulled the battery and went to restart the phone.
The phone will now only show the Samsung Galaxy S white logo and simply restart itself and play that logo over and over. If the phone is plugged into the wall it will show the battle charge logo briefly and than restart to the logo. It will go no further than this point.
I have tried to do a factory reset via Home + Power + Vol Up but it seems to reset itself before it will actually load into that menu. Home + Power + Vol Dn will bring me to the download screen which is stable and will not reset the phone.
This is where it gets strange, I have tried Odin and a 100% stock flash on the phone with no luck the phone just sits resetting. After a download of DarkyROM it will actually load the white Galaxy S logo along with the DarkyROM logo and simply go back to resetting.
So the phone is clearly in some state of a working order able to download and accept ROMs but just keeps restarting itself after the white initial Galaxy S logo.
Any and all help would be appreciated! I hope I have explained this problem well enough, maybe it is in need of being brought to a shop to be fixed? Just happens that the warranty expired last week, almost seems coincidental.
Thanks!
After you installed DarkyRom (or any other ROM with CWM), did you try re-entering the recovery menu? Perhaps you will now be able to enter recovery?
tptp said:
After you installed DarkyRom (or any other ROM with CWM), did you try re-entering the recovery menu? Perhaps you will now be able to enter recovery?
Click to expand...
Click to collapse
No, after the install of the ROM it would load up the white galaxy logo along with the DarkyROM logo and than just go back to resetting itself over and over. I could still go back to to the download but not access the reset menu.
Knagar said:
No, after the install of the ROM it would load up the white galaxy logo along with the DarkyROM logo and than just go back to resetting itself over and over. I could still go back to to the download but not access the reset menu.
Click to expand...
Click to collapse
run through My Android Solutions, link below and do the first step after that to immediately to recovery or download mode , than flash a rescue or resurrection kit from My Android collections, link below, all this done without sim card or exts SD card inserted
None of this has worked, I have tried every trick I can find on the net but I can't seem to get it to go.
As before the phone will go into download mode, will accept roms and so on as shown by the DarkyROM logo showing up and going away with the removal of it.
After every attempt I am still not able to get into recovery mode but am still able to access download mode. The phone seems to be in some state of working order but continues to reset itself only when turned on but will run stable in download mode.
ADB doesn't see the device and even if it did I think it would still just reboot once it started into recovery.
It's almost as if the phone starts and after it shows the starting Galaxy S GT I9000 it just turns itself off for some reason
Is their any way to totally reformat the phone and start 100% from scratch without getting into recovery to do factory reset?
Step by step instructions on what to do and download for Odin would be fantastic. I am still not sure 100% on what the PIT/Bootloader/PDA/Phone/CSC are or do so the files I need to put in those and a good explanation would be great!
This happens sometime. To fix, Do this.
1. Boot into download mode.
2. Flash stock ginger bread with Odin using 512 pit.
3. Now boot into recovery and wipe data/factory reset.
4. Boot again into download mode.
5. Flash devil or semaphore kernel.
5a note. Your phone doesn't need to be able to boot. All we need is recovery mode.
6. Boot into the new recovery and wipe data/factory reset.
7. Format /system.
8. Flash ROM / gapps etc.
9. Boot with success.
10. Happy dance time, brings good luck.
Sent from my GT-I9000 using xda premium
Knagar said:
Step by step instructions on what to do and download for Odin would be fantastic. I am still not sure 100% on what the PIT/Bootloader/PDA/Phone/CSC are or do so the files I need to put in those and a good explanation would be great!
Click to expand...
Click to collapse
ok, try flashing a gingerbread Ezboot loader, visit My Android collections, link below, has complete guide at download page
Well I've tried both suggestions with no luck. I am starting to think it's some sort of hardware problem which I can't understand because it is 100% stable and won't reset in download mode. It will accept ROMs and so on but instantly just starts to restart itself after the first logo is shown. No work around will let me into recovery mode and no method I have found so far will just reload how the phone boots. I guess it's time for a new phone eh chaps?
Knagar said:
Well I've tried both suggestions with no luck.
Click to expand...
Click to collapse
hmm, its strange..anyway, you should remove SIM Card and Ext SD card, and try to use any tool from My Android Collection, to format the Internal SD card and flash a 2e recovery to see , if you can get your recovery back or even a i9000 rescue kit would be good to go after formating your Internal SD card
Formatting you Internal SD card, will resolve any settings, data, delvik cache etc that would be the cause of your initial problem.. there are formatting tools as well a recovery tools that can be used to achieve this
Did u flash the correct stock firmware for ur I9000M? try this http://www.hotfile.com/dl/162558059/7efd7bc/I9000UGKG3_I9000BMCKG3_VMC.zip.html.
Source : http://www.sammobile.com/firmware/?page=3&model=GT-I9000M&pcode=0&os=1&type=1#firmware
Ok progress is being made, first I used Odin to load I9000UGKG3-I9000BMCKG3_VMC in the PDA slot without doing a reboot. Then I loaded JPK_Root_Recovery_2e using just the i9000_Kernel and was able to boot recovery.
After doing a Wipe Cache and then Factory reset the phone went back to a boot loop and I was unable to get back to the recovery menu.
After repeating the first steps I am once again in the recovery mode with no boot loot but am unsure as to where to go from here.
Currently the screen reads
Android system recovery <2e>
Samsung Recovery Utils
- for BML -
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache
-------------------------------------------------
E: Invalid command argument
-- Install from package...
Finding update package...
Opening update package...
# Manual Mode #
--Appling Multi-CSC...
Installing Multi-CSC
multicsc : src /system/csc/BMC/system/ .
*EDIT* Seems once you restart from the recovery mode it goes right back to a boot loop, was not able to apply the SD card update either. So getting to recovery is currently a one time deal without having to go back and reload VMC and 2e. Once restarted all is lost.
You will need to flash another firmware with 3 file method @odin. Search on this forum a firmware and flash it!
Don't worry, u can't brick your phone that easily. I flashed my phone 10times in a day, for boot loops, when i tried to upgrade to 4.0.4
Sent from my GT-I9000 using xda premium
Ok so this time I used Odin to do VMC in the PDA slot, then I9000 Kernel went back to VMC and loaded that then when I restarted the phone it went back to the same boot loop.
I have no way to clear the internal SD or anything like that because the programs will not see my phone connected to my PC.
What could be causing my phone to just continue to restart?
Knagar said:
Ok so this time I used Odin to do VMC in the PDA slot, then I9000 Kernel went back to VMC and loaded that then when I restarted the phone it went back to the same boot loop.
I have no way to clear the internal SD or anything like that because the programs will not see my phone connected to my PC.
What could be causing my phone to just continue to restart?
Click to expand...
Click to collapse
I gave u a source, download the guide on flashing through odin. It should work. Dun flash 1 file by 1 file.
EDIT : u can find more firmwares here. http://forum.xda-developers.com/showthread.php?t=1102881&page=1
Pm me if you need any help!
Ok so here is where I am at..
I have tried everything everyone has listed so far. The only think that has made any sort of progress at the moment is going into download mode, connecting to the USB after loading Odin. Using JPK_Root_Recovery_2e I9000_Kernel.tar will bring me to the recovery screen.
wipe cache partition + reboot = boot loop
wipe cache partition + wipe data/factory reset + restart = boot loop
wipe data/factory reset + restart = boot loop
Any of the above mentioned plus loading stock firmware results in a boot loop.
Any of the above mentioned plus loading DarkyROM Resurrection 10.2 will again show the Galaxy S I9000 Logo plus the DarkyROM logo and proceed to boot loop.
Clear cache and factory reset than load of i9000XXJVT pit/pda/modem/csc results in boot loop.
If I am missing something please explain in detail and not shunt me off to some other page.
As before I have tried everything mentioned with no luck at getting past this boot loop. Clearly the phone is able to accept roms and so on so the internel SD seems to be ok but the boot sequence seems scrambled. Strange that it will boot to download and boot to recovery with JPK but upon restart it just boot loops and without Odin and JPK I can only get back to download mode.
Seems to me you also have some partition woes. Try to find an older rom (Milky's worked for me) that requires re-partitioning to be done. Flash via ODIN, wait for 10-15 mins for whole process to complete. CWM flash any rom from there ... (Darky's Extreme also repartitions)

Device is stuck on boot logo

Hello, I have a problem with my Galaxy Note and I don't know what to do.
A few hours ago I tried to start the device as I usually do after I turn it off, but the device does not turn on and only stays stuck on this screen: "Samsung galaxy note n7000".
I'm running this Rom: "[ROM][4.1.2 JB]Ultimate N7000 XXLSC JellyBean 4.1.2 v5.1".
I have the ability to log into CWM by the combination of the known keys
I hope you guys can help me, thanks in advance.
(Note: The battery is charged and i also tried to remove it and put it back in.)
This problem happened to me before with the xxlsa leaked rom
Do a wipe from a safe kernel and flash the rom again
Try to boot into recovery and do a reboot recovery and then reboot.
Else you may do a backup and restore the same backup. It works most of the time. But a little time consuming.
Had same problem by loosing power. The device wont boot anymore. Fix per, reinstall without wipe did not work. Switch rom
i believe this problem comes to all jelly bean leak always Stuck on the first boot.
just got this problem again how i did it ?press power on Stuck on first boot next step straight away press 3 button go to recovery n hit reboot system n my phone bootup n back to normal.
terminator_5505 said:
This problem happened to me before with the xxlsa leaked rom
Do a wipe from a safe kernel and flash the rom again
Click to expand...
Click to collapse
How can i replace the kernel and reinstall the rom if I cannot see the device on my computer when it's connected?
nokiamodeln91 said:
Try to boot into recovery and do a reboot recovery and then reboot.
Else you may do a backup and restore the same backup. It works most of the time. But a little time consuming.
Click to expand...
Click to collapse
I've already tried both methods you have specified and none of them worked.
My attempt to make a Nandroid backup has failed and the CWM said something like "backup of /data failed".
alvinhaw said:
i believe this problem comes to all jelly bean leak always Stuck on the first boot.
just got this problem again how i did it ?press power on Stuck on first boot next step straight away press 3 button go to recovery n hit reboot system n my phone bootup n back to normal.
Click to expand...
Click to collapse
Hi, this is not the first time I try to boot the device after installing a new rom.
I'm with this rom for a few weeks now and the problem occurred only yesterday.
This is well known problem with xlsc rom. U have to wipe everything and to flash rom. There are some solutions with backup/restore but they didn't work for me.
So, complete WIPE, and than flash!!
Backup of data failed because of insufficient space. Make backup to internal if there is more space.
i have the same problem since i full wipe and flashed asylums 20130302 build. after doing a full wipe and clean install, i started downloading my regular apps from playstore and suddenly it turned off just like when you remove the battery.
i tried the following::
1. full wipe and installed the rom -- it boots up few minutes then shuts off and wont boot up without charger
2. restored from nandroid -- same as above
3. full wipe and installed previous builds -- same
4. full wipe + flashed latest build 20130303 + latest gaps for JB 4.2 -- same
5. check battery stat -- ok
whenever it shuts off, it wont turn back on unless without a charger. it just shuts off at random. this is the second day I'm experiencing it and its frustrating.
any help? thanks
edit:: btw it shuts off at boot animation
In the other thread where you asked this question too there are members who replaced their battery and solved it this way.
Maybe you should try this and replace the battery.
Good luck.
I got same issue and I'm for kill someone. Why these problems on a official rom?

[Q] Help! Bricked my phone during Flash!

Hey guys,
So I've been at this all day on another forum. Here is the link to ONE of the threads : (Edit removed, cant post links yet)
So I was trying to Flash to Android Revolution HD and it got stuck at 30% half way through the installation. This lasted a good 5 hours...
I finally managed to reboot the phone using "adb reboot bootloader"
But now I'm stuck on "HTC Quietly Brilliant" splash screen!
I JUST bought this phone last night off kijjiji and I'm reallly ****ting bricks now (no pun intended)
Any help whatsoever will be really appreciated
Added a screen shot of what it was stuck at a few minutes ago. I JUST managed to reboot it..but it's still stuck.
PoRco1x said:
Hey guys,
So I've been at this all day on another forum. Here is the link to ONE of the threads : (Edit removed, cant post links yet)
So I was trying to Flash to Android Revolution HD and it got stuck at 30% half way through the installation. This lasted a good 5 hours...
I finally managed to reboot the phone using "adb reboot bootloader"
But now I'm stuck on "HTC Quietly Brilliant" splash screen!
I JUST bought this phone last night off kijjiji and I'm reallly ****ting bricks now (no pun intended)
Any help whatsoever will be really appreciated
Added a screen shot of what it was stuck at a few minutes ago. I JUST managed to reboot it..but it's still stuck.
Click to expand...
Click to collapse
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
MacHackz said:
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
Click to expand...
Click to collapse
Hey I got the phone to restart and it goes almost immediately into the HTC screen again. I think "fastboot" setting is on or something. I just can't get it to go to the bootloader
MacHackz said:
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
Click to expand...
Click to collapse
Just tried it under my bright lamp too. No dice
Okay so I used Hansoons AIO toolkit to get it to load into CWM-based Recovery... phew
What's next!?
you need to do this when in fastboot
type fastboot erase cache
just to be sure redownload his rom
expertzero1 said:
you need to do this when in fastboot
type fastboot erase cache
just to be sure redownload his rom
Click to expand...
Click to collapse
Not really sure how to get into fastboot. Will typing that command get me to fastboot and erase cache.
Here are my options now, using the Hasoon2000 AIO
1) Re-flash a recovery - ClockWorkMod, ClockworkMod Touch, TWRP AND THEN Install zip via sd card
2) Do above ^^ but install via sideload
3) Just erase cache with AIO and install zip from sim card
What should I do?
PoRco1x said:
Not really sure how to get into fastboot. Will typing that command get me to fastboot and erase cache.
Here are my options now, using the Hasoon2000 AIO
1) Re-flash a recovery - ClockWorkMod, ClockworkMod Touch, TWRP AND THEN Install zip via sd card
2) Do above ^^ but install via sideload
3) Just erase cache with AIO and install zip from sim card
What should I do?
Click to expand...
Click to collapse
It doesn't matter, once you're in cwm recovery, reflash the Rom with a full wipe and you should be good. Calm down dude.
Sent from my HTC One using xda premium
just like the gentleman above said, you need to calm down first. If your phone can boot, although it hangs midway, it has a big chance not to be bricked in anyway.
And I don't advice you to use the AIO tools, just try to follow every simple guides to flash custom recovery-root-custom rom and you'll get familiar with the process in no time.
So I assume that you can boot into recovery, these are the steps that I think you should follow:
- re-download the custom rom that you wanna flash (make sure that the download is not corrupted)
- boot into recovery (in your case,CWM)
- wipe cache . wipe dalvik (in advance settings)
- install zip --> choose zip --> point to your custom rom
- you'll see the aroma installer, pick your options until it begins to install.
- if the installation went smoothly, don't reboot phone yet, get back to recovery, wipe cache/dalvik then reboot system and let the phone install the OS (first boot usually take long timer)
- if the installation hangs at midway, reboot again into recovery (power + vol down until button blinks and phone boots into bootloader) then start again from first step
once again, I advice you not to use the AIO tools. it's safe but you need to know what you are doing and the process to conquer your phone is not that hard.
What are you holding to try to enter bootloader? I use power and volume down and it works every time. Just hold them until the bootloader screen appears then let go.
Also, like others have said, it's better to use adb and fastboot commands yourself in cmd or terminal, rather than using the toolkit - it's not too hard, there are plenty of guides, you learn quicker and it's more satisfying
Sent from my HTC One using xda premium
ryryzz said:
just like the gentleman above said, you need to calm down first. If your phone can boot, although it hangs midway, it has a big chance not to be bricked in anyway.
And I don't advice you to use the AIO tools, just try to follow every simple guides to flash custom recovery-root-custom rom and you'll get familiar with the process in no time.
So I assume that you can boot into recovery, these are the steps that I think you should follow:
- re-download the custom rom that you wanna flash (make sure that the download is not corrupted)
- boot into recovery (in your case,CWM)
- wipe cache . wipe dalvik (in advance settings)
- install zip --> choose zip --> point to your custom rom
- you'll see the aroma installer, pick your options until it begins to install.
- if the installation went smoothly, don't reboot phone yet, get back to recovery, wipe cache/dalvik then reboot system and let the phone install the OS (first boot usually take long timer)
- if the installation hangs at midway, reboot again into recovery (power + vol down until button blinks and phone boots into bootloader) then start again from first step
once again, I advice you not to use the AIO tools. it's safe but you need to know what you are doing and the process to conquer your phone is not that hard.
Click to expand...
Click to collapse
I really appreciate your reply man. Yeah, I need to calm down haha.
Alright, the problem is that I can't get into recovery mode unless I use the AIO tool. I've tried everything else. Using the volume down button, under the bright light etc etc. IT just goes straight to the HTC screen. It must be noted that I DID have problems getting into my bootloader before as well. A moderator of another forum made me download an app from the app store that let me either reboot int bootloader or reboot into recovery.
Rebooting in bootloader didn't work through that app either, it just restarted the phone, However,rebooting into recovery worked. Also, AIO tools doesn't seem to allow me to reboot into bootloader either... that command just restarts the phone and gets it stuck on HTC screen.... BUT the "reboot into recovery" works here too
Problem 2 ) The device is being detected by my pc but I can't access the file system in it. It just showing as a drive with no GB in it whatsoever . when I use "adb devices" in cmd it shows my device along with the serial id though.
So, what's your situation at the moment? You can get into recovery? What are you trying to do?
redbull123 said:
So, what's your situation at the moment? You can get into recovery? What are you trying to do?
Click to expand...
Click to collapse
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
PoRco1x said:
I really appreciate your reply man. Yeah, I need to calm down haha.
Alright, the problem is that I can't get into recovery mode unless I use the AIO tool. I've tried everything else. Using the volume down button, under the bright light etc etc. IT just goes straight to the HTC screen. It must be noted that I DID have problems getting into my bootloader before as well. A moderator of another forum made me download an app from the app store that let me either reboot int bootloader or reboot into recovery.
Rebooting in bootloader didn't work through that app either, it just restarted the phone, However,rebooting into recovery worked. Also, AIO tools doesn't seem to allow me to reboot into bootloader either... that command just restarts the phone and gets it stuck on HTC screen.... BUT the "reboot into recovery" works here too
Problem 2 ) The device is being detected by my pc but I can't access the file system in it. It just showing as a drive with no GB in it whatsoever . when I use "adb devices" in cmd it shows my device along with the serial id though.
Click to expand...
Click to collapse
It is not bricked, you should hold down your vol down+power a tad bit longer, you should hold it until the screen comes on and not until when it's turned off. If the installation is stucked in recovery you should be able to go to bootloader.
You need to mount usb to your computer first. If you cannot find the option to mount it, you probably need to push files through adb in fastboot mode.
Sent from my HTC One using xda premium
PoRco1x said:
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
Click to expand...
Click to collapse
I would just try flashing the ROM again - it sticks at 30% all the time, it's a common problem with Aroma (the installer), nothing to do with anything you've done, nor the ROMs fault. It sometimes takes a few tries to get it properly. I'd recommend using the volume and power buttons to navigate around aroma instead of using the touchscreen...
Sent from my HTC One using xda premium
JazLiew said:
It is not bricked, you should hold down your vol down+power a tad bit longer, you should hold it until the screen comes on and not until when it's turned off. If the installation is stucked in recovery you should be able to go to bootloader.
You need to mount usb to your computer first. If you cannot find the option to mount it, you probably need to push files through adb in fastboot mode.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yeah, I tried that too. The phone was INITIALLY just stuck and wouldn't even restart. Nothing I did made it restart until finally... I used adb reboot bootloader to make the phone finally restart into the HTC screen. But no matter what I try to do, it hasn't taken me to the bootloader even ONCE, ever since I got the phone in fact.
Should I push in a new rom using adb? And if so, which one? Android Revolution HD (fresh download) or a different one that you recommend?
Btw, I apologise for the delayed replies, the forum is making me wait between each message since I'm new
PoRco1x said:
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
Click to expand...
Click to collapse
While in recovery, on your computer try boot into bootloader with "adb reboot bootloader" and see if your phone can boot into fastboot mode. If it can, I strongly recommend you to COMPLETELY go back to stock by flashing your RUU.exe. After going back to stock, do the whole process of unlock/root again
redbull123 said:
I would just try flashing the ROM again - it sticks at 30% all the time, it's a common problem with Aroma (the installer), nothing to do with anything you've done, nor the ROMs fault. It sometimes takes a few tries to get it properly. I'd recommend using the volume power buttons to navigate around aroma instead of using the touchscreen...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
It's funny you mention that! I had serious issues navigating through the aroma installer, I would have to click the "next" button at least 2-3 times. And when I tried using the volume buttons, it would only go to the button inbetween "back" and "next" which was something like "more info"
Does this point toward any other issue? Or should I go ahead with flashing rom again?
ryryzz said:
While in recovery, on your computer try boot into bootloader with "adb reboot bootloader" and see if your phone can boot into fastboot mode. If it can, I strongly recommend you to COMPLETELY go back to stock by flashing your RUU.exe. After going back to stock, do the whole process of unlock/root again
Click to expand...
Click to collapse
I used adb reboot bootloader to get OUT of the installtion screen, but it didnt take me to the bootloader (as usual) it just restarted. The AIO tools also didn't take me to bootloader when I used one of the commands there. So going to booatloader is really being impossible now!!
I think u need to send it to repair or warranty. Since you can't go to bootloader there's a lot of things you can't do right now.
So now I have two options at hand now...
1) Go ahead with rom installation (this I know how to do)
2) Flash official stock using RUU (this I dont know how to do yet, since I'm not entire sure what carrier this was initially on)

[NOOB-Friendly] starting flashing and customizing on most Samsung Devices

So i will be making a for rooting and flashing tutorial for beginners!
So i will need to tell you a few things first.
Installing ROM's is not illegal though rooting is illegal in the following country's:
North Korea
Malaysia
Singapore
South Korea
SO IF YOU DONT LIVE THEIR THEN STOP COMPLAINING ABOUT ROOTING IS HIGHLY ILLEGAL
And if your running total stock android then i will make a short tutorial on how to install your first ROM
This method is nearly the same for switching ROM's, though after the tutorial i will explain the only thing thats different.
Also this works for all ROM's.
NOTES:
I am not gulity of anything that happens to your device
Your warranty will be void
You will lose all your Apps, except photos and files
Here is what you will need:
A version of CWM to your specific phone (Please notice depending on ROM's android version, you will need a KK-compatible for a Kitkat ROM or a ICS compatible for a Ice cream Sandwich ROM etc.)
Download: https://www.clockworkmod.com/rommanager
gApps
Download: http://forum.xda-developers.com/android/software/gapps-consolidated-gapps-thread-t3064693
SuperSU
Download: http://forum.xda-developers.com/showthread.php?t=1538053
I will be using CyanogenMod12.1 for this tutorial!
Download: http://www.cyanogenmod.org/
Odin 3.07 not higher.
Download: http://www.android.gs/download-odin-3-07/
A working Computer
USB cable for your phone.
Your phone needs to be charged 100% before doing this.
So lets begin!
1. Start by plugging your phone to your PC
2. Start ODIN
3. Hit the PDA button and find your custom recovery and hit OK.
4. Make sure you have your ROM, gApps and SuperSU on your phone.
5. Turn off your phone and hold HOME + POWER + Volume down
6. When a screen appears press Volume up
7. Press start on ODIN and wait till your phone reboots
8. Now power it off and hold HOME + POWER + Volume Up till your recovery comes up
9. Now factory reset and go to Mounts and Storage and format /system
10. Go to advanced tab under you main menu on the recovery
11. Press Wipe dalvik cache
12. At the main menu, go to Install zip now choose either from SD card or Internal Storage Device
(Depending on location)
13. find your ROM and press it
14. After a while when its done, go to install zip and find where you placed gApps and flash it
15. Now factory reset and go to advanced tab and wipe dalvik cache
16. Reboot your device, and wait till you see the Welcome screen
17. Set up your device.
18. Power off you phone and hold HOME + POWER + Volume Up
19. Now install zip and find SuperSU and flash it
20. Reboot your phone and your done!
21. ENJOY!
If done successfully, you should now learned the basics of flashing, though you dont need to install a new recovery everytime,
Though you might need it if you gonna change android version if the ROM dont have a recovery.
Also fo beginners, gApps is for play store and google apps generally, and the SuperSU is for rooting.
But if you wanna become a pro, start switching ROM often.
If you want to know a pro tip, before installing a new ROM, always format /system and factory reset.
As it makes the success rate 99.99%, but if your phone is stuck at the boot screen, then its because you haven't format /system
and factory reset, or you forgot to factory reset after the install of gApps.
If you phone keeps booting into your recovery instead of your ROM, then you have installed a new recovery over the ROM's
recovery, thats not compatible with your'e ROM or its only compatible with another Android-version
If you encounter a problem please comment your phone model and your ROM and Recovery and your problem
I will help as much as possible
I searched around before uploading this, if their is one earlier made than me please send a email to
[email protected] and i will take it down ASAP
Please post your thread in the appropriate forum next time. This thread is closed.

Categories

Resources