I've just rooted a stock brand new Galaxy Tab 10.1 from canada (not sure if it matters). I then wanted to install Galaxytask, so I flashed CWM, wiped everything did my backups and what not. I then installed from the zip file and everything went okay but I am stuck at the android splash screen and it won't go from there. Is there a difference between the american and canadian versions? Do I need to flash something else first?
Thanks for any help.
patience?
it takes a good (felt) 10 minutes of splash screen after installation of the rom until the language menu appears. I assume that is the problem since it sounds like it is your first custom rom.
hard reset the tab.
jokkeri77 said:
it takes a good (felt) 10 minutes of splash screen after installation of the rom until the language menu appears. I assume that is the problem since it sounds like it is your first custom rom.
Click to expand...
Click to collapse
Yea it was definitely patience. I was in a rush finishing my day at work thinking, hey I will do this now then I dont have to bring my cable home blah blah. Then it got stuck (or so I thought) and did a nandroid restore. Tried it again after posting this, waiting 15 minutes and just watched a TV show, came back and it was good!
First custom rom on the tab 10.1 yes, but been using CM on a few phones like the nexus one and atrix.
Cheers
Related
hi guys
I recently bought a 2nd hand Vibrant for a really good price.
As far as i see the Vibrant is already rooted with 2.2.1 Lidroid, and CWM installed.
The battery usage is amazing with this rom, but I still fancy to install some custom GB roms.
I have some questions:
1. I would like to check if I am already on GB bootloader, please guide me to check?
2. If I am not on GB bootloader, I know I must first install it.
I wonder if Vibrant has some stock GB firmwares like captivate does? The stock camera is a must for my case ><
Am i correct if I follow this method from here
http://forum.xda-developers.com/showthread.php?t=1156832
3.Or actually I can simply flash any custom GB roms directly from where I am (Lidorid 2)
THX
Okay you know if you're not gb bootloaders when you turn on ur phone there's weird rainbow lines
If not then you are
And if you are then yea you can flash any rom
Sent from my GT-I9000 using xda premium
Let me confirm if you suggesting me to flash the GB roms?
If there's rainbows > froyo bootloader
if nothing > GB bootloader
So can i say actually Gb roms doesnt really need GB bootloader
as long as I am fine with the rainbows?
THX
j4371 said:
Let me confirm if you suggesting me to flash the GB roms?
If there's rainbows > froyo bootloader
if nothing > GB bootloader
So can i say actually Gb roms doesnt really need GB bootloader
as long as I am fine with the rainbows?
THX
Click to expand...
Click to collapse
I've run CM7, and CM9 (ICS) on Froyo boot loaders. For me it just makes the kernel screen flash and show again, then goes on to ROM booting. I'm running a Froyo boot loader right now.
Is lidroid a t959 rom or a t959v?
You need to have a t959 to be in the vibrant 3g section, otherwise you'll probably want the galaxy s 4g section.
Sent from my Sensation using Tapatalk 2
there is a Lidroid version for T959 - I have a Odin flash with it. I use it instead of JFD.
Want to know if you have the GB boot loaders? Easy -
Hold the Volume up button and the power button at the same time. If it goes to download mode....you got the GB bootloaders.
T959 Vibrant does not have Samsung 2.3 support. Samsung forgot about us after Froyo. There Froyo OTA upgrade bricked so many phones that they wont chance it again.
For 2.3 Gingerbread you will have to download a I9000 port found in our Development section. That said the ICS packages are very nice for Vibs too.
need help guys
A few hours ago, I was at work and bored.
I started to flash some GB roms without coming back to check this post.
The rom i used was phiremod-fusion-2.1.1.
As usual I nandroid my lidroid before doing anything.
Then I 3 wipes and flash the phiremod rom.
first time the flash was really quick and also rebooted itself.
But only this time I realise I have a newer CWM 5.xx version instead of my 2.xx version (Lidroid)
Ok, i wasn't panic, because i read some where before. It's prefectly fine for a cm7 if the first time it bootloop.
Then I pull battery, and boot into recovery again, to flash the 2nd time.
this time BAAM, prefect. I found myself with a 2.3.x cm7 mod rom.
but as soon as I found the camera apk is actually the MIUI one. I decided to nandroid back to Lidorid.
things turns ugly at this point, when i back to CWM i restored.
But only found some errors CWM said , but I remember CWM did say something like erasing boot.img before restoring.
After the resotre failed, I accidentally reboot my phone.
And now my vibrant only stuck at the typical black boot screen "Vibrant in the middle with samsung at the bottom.
I tried to boot back to recovery, but no luck.
right now I am telling myself i probably need to restore to stock.
Can my fellow xda members guide me the proper way to
1. boot CWM
2. download mode
Given the fact that I am not too sure about which bootloader I am on.
THX people!!
Yup, you'll need to go back to stock. There are plenty of write-ups on how to do it.
Also, NEVER restore a 2.2 backup after you install 2.3 or higher. The file systems and partitions are different. Odin back to stock, install lidroid again, and then try to restore your backup.
j4371 said:
need help guys
A few hours ago, I was at work and bored.
I started to flash some GB roms without coming back to check this post.
The rom i used was phiremod-fusion-2.1.1.
As usual I nandroid my lidroid before doing anything.
Then I 3 wipes and flash the phiremod rom.
first time the flash was really quick and also rebooted itself.
But only this time I realise I have a newer CWM 5.xx version instead of my 2.xx version (Lidroid)
Ok, i wasn't panic, because i read some where before. It's prefectly fine for a cm7 if the first time it bootloop.
Then I pull battery, and boot into recovery again, to flash the 2nd time.
this time BAAM, prefect. I found myself with a 2.3.x cm7 mod rom.
but as soon as I found the camera apk is actually the MIUI one. I decided to nandroid back to Lidorid.
things turns ugly at this point, when i back to CWM i restored.
But only found some errors CWM said , but I remember CWM did say something like erasing boot.img before restoring.
After the resotre failed, I accidentally reboot my phone.
And now my vibrant only stuck at the typical black boot screen "Vibrant in the middle with samsung at the bottom.
I tried to boot back to recovery, but no luck.
right now I am telling myself i probably need to restore to stock.
Can my fellow xda members guide me the proper way to
1. boot CWM
2. download mode
Given the fact that I am not too sure about which bootloader I am on.
THX people!!
Click to expand...
Click to collapse
Get into download mode by while it's off, holding VOL-UP + Vol-DOWN and plugging in USB.
y vibrant revived!!
Thx everyone
After this, I am thinking to ask my colleagueto make one JIG for me.
I'd like to confirm it's same as SGS, i.e. 3 X 10kohm in series
Hi there,
I'm running CM 10.1 20130219 and today bought franco.Kernel and auto flashed to I think it was version r20. The phone restarted and got to the Sammy screen with the red exclamation mark at the top left which I'm assuming is fastboot mode? So it stayed at that screen for 3 or so secs and it turns off. I found this post http://forum.xda-developers.com/showthread.php?t=1392310 but the toolkit is for the Nexus only. Would flashing stock firmware through Odin do the trick?
Thanks
unknownmember said:
Hi there,
I'm running CM 10.1 20130219 and today bought franco.Kernel and auto flashed to I think it was version r20. The phone restarted and got to the Sammy screen with the red exclamation mark at the top left which I'm assuming is fastboot mode? So it stayed at that screen for 3 or so secs and it turns off. I found this post http://forum.xda-developers.com/showthread.php?t=1392310 but the toolkit is for the Nexus only. Would flashing stock firmware through Odin do the trick?
Thanks
Click to expand...
Click to collapse
Try to flash a stock kernel/CM10 kernel or another custom kernel (e.g. Siyah) and see if it fixes the booting.
Soz been busy with work. But kinda fixed it by flashing stock ROM. I flashed it with stock but it wouldn't go any further than Sammy boot screen and kept restarting. So I CF rooted and luckily was able to get into recovery mode and luckily also I made a backup...I almost didn't in the first place. lolz. Thanks heaps for the tip tho, at least now I know where to get the stock kernel.
khob-kun-Krub i'm assuming you're Thai since your location is Bangkok. I'm born Thai but can't read, write or speak Thai to save my life. lolz
Franco kernel doesn't support AOSP. Only Samsung ROMs.
Exynos SIII; CM10.1
unknownmember said:
Soz been busy with work. But kinda fixed it by flashing stock ROM. I flashed it with stock but it wouldn't go any further than Sammy boot screen and kept restarting. So I CF rooted and luckily was able to get into recovery mode and luckily also I made a backup...I almost didn't in the first place. lolz. Thanks heaps for the tip tho, at least now I know where to get the stock kernel.
khob-kun-Krub i'm assuming you're Thai since your location is Bangkok. I'm born Thai but can't read, write or speak Thai to save my life. lolz
Click to expand...
Click to collapse
Good to hear that it is working.
As you can see by my flag, I am German but living in Bangkok for several years now. I can speak, read & write Thai as well (basics though). Let me know if you are in Thailand on accident some day.
Last night I softbricked installing a rom. The device was being very weird and would not boot correctly. The device started showing the big GALAXY S4 splash screen instead of the usuall plain SAMSUNG sometimes says custom unlock sometimes not depending on the rom/kernal being used. Now even with Kernals that used to say SAMSUNG custom all it says is the big only GALAXY S4 splash screen. The device seems to take alot longer to get past this screen as well. Any suggestions on this??
Recovery would flash roms and device would boot once but would not boot after reset. SO F-it just Odin back to stock, root, recovery, done.
everything is working now except I still have the GALAXY S4 splash scren instead of the SAMSUNG and takes forever to boot/load past splash screen.
Is this stored in the kernal? Ive tired different kernals and all have stayed the same. I have completly ODIN back to stock wiped any and everything on this device.
QUESTION Summary::: Whats up with this splash screen VS the other one, why cant i get it to go back to the way it was before even after ODIN stock img, and why does it take longer to load and 1/2 the time not load at all.
Is there a BIOS that is not wiped... I think I broke it.
EDIT: Just sat on the SAMSUNG GALAXY S4 for 20 minutes before starting after fresh rom install... what a pain.
mrlaigle said:
Last night I softbricked installing a rom. The device was being very weird and would not boot correctly. The device started showing the big GALAXY S4 splash screen instead of the usuall plain SAMSUNG sometimes says custom unlock sometimes not depending on the rom/kernal being used. Now even with Kernals that used to say SAMSUNG custom all it says is the big only GALAXY S4 splash screen. The device seems to take alot longer to get past this screen as well. Any suggestions on this??
Recovery would flash roms and device would boot once but would not boot after reset. SO F-it just Odin back to stock, root, recovery, done.
everything is working now except I still have the GALAXY S4 splash scren instead of the SAMSUNG and takes forever to boot/load past splash screen.
Is this stored in the kernal? Ive tired different kernals and all have stayed the same. I have completly ODIN back to stock wiped any and everything on this device.
QUESTION Summary::: Whats up with this splash screen VS the other one, why cant i get it to go back to the way it was before even after ODIN stock img, and why does it take longer to load and 1/2 the time not load at all.
Is there a BIOS that is not wiped... I think I broke it.
EDIT: Just sat on the SAMSUNG GALAXY S4 for 20 minutes before starting after fresh rom install... what a pain.
Click to expand...
Click to collapse
yes the boot.img is held in the kernel....flash back to stock and reroot your device dont take any chances...hopefully you have some backups on an external sd card....this happened to me as well and i could only get to download mode so i flashed back to stock and rerooted my device everything is peachy....dont dont dont take any chances with this phone the security measures in this phone are insane and if you keep messing around with having the device "sometimes boot with custom samsung screen and sometimes not" there is something wrong with the partition....youre best bet is to flash stock and reroot....if you have a backup on an external sd card then youre set otherwise start over or you will have a $700 paper weight....let me know if you have any questions reverting back to stock or anything else good luck dude
Yeah I restored started from Odin stock last night. I thought that would take out anything that I flashed that caused the issue. But it didn't fix it.
I odin'ed back installed root recovery and still having issues where it will not boot after 2 or 3 resets. Hangs on thats galaxy s4 splash screen for more than 30 and never boots.
I would think that when it was odin'ed it would have over written the boot IMG and any thing else it might be but its not.
Sent from my SCH-I545 using Tapatalk 2
mrlaigle said:
Yeah I restored started from Odin stock last night. I thought that would take out anything that I flashed that caused the issue. But it didn't fix it.
I odin'ed back installed root recovery and still having issues where it will not boot after 2 or 3 resets. Hangs on thats galaxy s4 splash screen for more than 30 and never boots.
I would think that when it was odin'ed it would have over written the boot IMG and any thing else it might be but its not.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
when you did odin back to stock did you do a factory reset...NOT FROM RECOVERY....from settings>>backup and restore>>factory data reset? ......theres a couple of things to look for here....Odin back to stock and boot in the STOCK recovery....try wiping the cache and dalvik partitions...if they fail then the partitions are corrupted....boot normally and go to settings>>backup and restore>>factory data reset....try that...if that doesnt work then try a factory reset from the stock recovery...if all of that STILL doesnt work then the partitions are corrupted I would ask for a replacement device
So I updated to the newest software MI5. Went from that and did the root which was sucessfully. I had put on OUDHS Touch CWM-based Recovery thru ODIN which was sucessful as well. After doing all of that, I downloaded Josh Beach's Jellybomb test rom. The steps I did was booted into recovery which is the one above, factory data reset, wiped cache, and wiped dalvik, then flashed the zip. The zip looked to flash ok but when i went to reboot, it just keeps getting stuck at the samsung galaxy note 3 screen, then it will reboot then go to the same screen. Did I do something incorrect? This happened to me on this ROM and the stock MI5 ROM rooted.
Might want to read through this thread...
http://forum.xda-developers.com/showthread.php?t=2473036
Process system isn't responding
Sent from my Note 3 on Android
runner77 said:
Might want to read through this thread...
http://forum.xda-developers.com/showthread.php?t=2473036
Process system isn't responding
Sent from my Note 3 on Android
Click to expand...
Click to collapse
so it sounds like i cant flash any custom roms right now? Just odin back to stock and root it and leave it at that?
this probably wont help for this particular problem, or maybe it will.. but for anyone else getting a bootloop..
i just now had a bootloop experience that i got out of.. and here's how it started - i have not rooted my note 3 (i have rooted my galaxy gear though, but i don't think that would affect the note 3).. anyway, i use the nova launcher as my main launcher.. and just before i got stuck in a loop, i had been playing with a new launcher called Themer... i just started it without setting it as default.. then i went back to my main launcher and i noticed that almost all ram was used up and i thought i might as well do a restart as it has been a while... and then it just would not start.. i got to the lock screen image, and then it would restart again and again, with no sound for the animated logo.... it eventually booted up ok, but i have no idea how i got it to work... however, i held down the power button for a while longer and it would "force" a new restart and basically abort the one already in progress, and if i did that, the boot up sound would come back... i continued doing that a couple of items and then it finally worked.
use twrp or phones as of right now dont like cwm recovery...found this out the hard way
odin back to stock rom non root wipe phone using default recovery odin back to stock again root your phone use twrp to flash whatever rom u want
lunchboxVA said:
use twrp or phones as of right now dont like cwm recovery...found this out the hard way
odin back to stock rom non root wipe phone using default recovery odin back to stock again root your phone use twrp to flash whatever rom u want
Click to expand...
Click to collapse
And when flashing make sure to wipe dalvik/caché several times for good measure.
Sent from my SM-N900P using Tapatalk
checking in to add that i found a new solution to my own problem here.... it "magically" started the last time just by me keeping on rebooting.. but that's not really a good solution and i don't think it lasts
and for me it didn't... as today i did a new restart, and it got the same stuck in a loop again, however, i followed the first mentioned workaround in this link here and it worked perfectly.. it was really that simple in my case it seems, i have done several restarts now and the bootloop is gone!...
oops, seems i cant post any links for not having enough posts yet...
i'll just add the steps mentioned instead
1 . Remove the battery and the SD card.
2. Put the battery back in and turn on the device.
3. Try Menu > Settings > Wi-Fi > Menu > Advanced and uncheck Always allow scanning.
4. Now you should be able to turn the device off and reinsert the SD card.
5. Boot it up and your problem might be gone
i have no idea how it works though as i personally don't understand the connection between then external sd card and the setting you turn off in the wifi advanced options..
cheers!
Hi all, my Prime is stuck at the Asus splash screen out of nowhere! I looked through these q & a, googled, and tried a few simple options before i posted this.I was not trying to flash a new rom or anything like that. I actually hadn't used it for a few days because i'm moving, i charged it up, used it for a few hours, came back later to use it, and the browser froze. No big deal, it does that once every day or two. I hold the power button to restart it and now it just stays at the flash screen. I haven't tried to flash anything in so long i forgot for a bit how to access recovery or what exact rom im using. I can access recovery(twrp 2.2.2.1) and fastboot, i remember unlocking without a problem, and doing the nvflash backup on ics before i believe i flashed a stock jb rom(which i think i'm still on.) I was able to copy my pictures to an external sd card through twrp , and after that i tried to restore a backup, and wiping data and cache but still stuck at the splash screen. Any help would be greatly appreciated, right now im going to look through and see if i can find the stock jb rom, or lookup fastboot guides or something. Thanks for any help!
I flashed this rom and got it up and running. I love this forum! w00t http://forum.xda-developers.com/showthread.php?t=1927494