Database Develop

i9305 stuck on rom booting screen after flash

Was flashing my friends i9305 and now it wont boot any rom I flash... always gets stuck on the first boot screen until I take out battery.
I flashed CWM 6.0.4.7 using odin.
I have tried flashing several roms (CM 11, CM 10.1, PACman 4.3)... Each one will flash with no errors, then when I reboot after correct GAPPS it just gets stuck on the loading screen forever and won't boot up into ROM.
Wipe data/cache, wipe dalvik, wipe system > Install rom from zip, install GAPPS from zip > reboot (even here I wipe system/data/cache - still doesnt work).
Any ideas on why it won't load up the roms....

only4dank said:
Was flashing my friends i9305 and now it wont boot any rom I flash... always gets stuck on the first boot screen until I take out battery.
I flashed CWM 6.0.4.7 using odin.
I have tried flashing several roms (CM 11, CM 10.1, PACman 4.3)... Each one will flash with no errors, then when I reboot after correct GAPPS it just gets stuck on the loading screen forever and won't boot up into ROM.
Wipe data/cache, wipe dalvik, wipe system > Install rom from zip, install GAPPS from zip > reboot (even here I wipe system/data/cache - still doesnt work).
Any ideas on why it won't load up the roms....
Click to expand...
Click to collapse
I have same problem here.. no one help me... I dont know I was in i9000 thread and lot of time I got answers.. miss that thread so much .

1Ishara said:
I have same problem here.. no one help me... I dont know I was in i9000 thread and lot of time I got answers.. miss that thread so much .
Click to expand...
Click to collapse
Well I figured it out... since it was never flashed or anything before (from stock rom)... I just went into the Mounts and Storage menu, and formated /cache /system /data manually and it finally worked.
Hope that helps

Random reboots after installing Gapps in Kitkat

Hi
I'm trying to install Kitkat 4.4 with Maclaws cm11. Also tried the carbon rom. All seems to work fine until I flash G apps. Then I get random reboots shortly after boot. Tried both micro and aroma Gapps from Mclaw. Am I alone with this problem? Any suggestions?
I'm using CWM for flashing and wrong cache etc. Baseband I8190XXANA2 in stock 4.1.2 (rooted) which works fine.
After more research it seems like reboots happens also without Gapps. Also happening in 4.3. There was recently a firmware update early this week. Maybe something has changed, breaking custom ROMs.

larscn said:
Hi
I'm trying to install Kitkat 4.4 with Maclaws cm11. Also tried the carbon rom. All seems to work fine until I flash G apps. Then I get random reboots shortly after boot. Tried both micro and aroma Gapps from Mclaw. Am I alone with this problem? Any suggestions?
I'm using CWM for flashing and wrong cache etc. Baseband I8190XXANA2 in stock 4.1.2 (rooted) which works fine.
After more research it seems like reboots happens also without Gapps. Also happening in 4.3. There was recently a firmware update early this week. Maybe something has changed, breaking custom ROMs.
Click to expand...
Click to collapse
Bud,
If you're on stock just do that:
1-Reboot in recovery
2-Choose Wipe data/factory reset
3-Flash cm rom
4-Flash gapps
5-Reboot
Done, that's it. Not complicate.
If you want to update cm roms:
1-Reboot in recovery
2-Flash cm update
3-Choose Wipe cache & dalvik cache
4-Reboot
Done.
You don't need to mess up with anything more. Read my FAQ here for gapps & for more doubts. Have fun

thanks...
mauam said:
Bud,
If you're on stock just do that:
1-Reboot in recovery
2-Choose Wipe data/factory reset
3-Flash cm rom
4-Flash gapps
5-Reboot
Done, that's it. Not complicate.
If you want to update cm roms:
1-Reboot in recovery
2-Flash cm update
3-Choose Wipe cache & dalvik cache
4-Reboot
Done.
You don't need to mess up with anything more. Read my FAQ here for gapps & for more doubts. Have fun
Click to expand...
Click to collapse
Thanks for the advice. I've read the faq's and followed that, but the problem is that my phone just reboots randomly a minute or so after it's booted up. Was suspecting this to be the latest firmware update, but if so the forum would probably been flooded with more with the same problem.
It might be my battery, which is bad. Just got a new one. Charging it now, and will try CM11 again tomorrow. If it still reboots I'll see if I'm able to access the logs to get an idea of whats going on. It works fine on stock, so I'm a bit puzzled... .

Solved
...and after changing battery CM11 runs smooth without reboots .
The reboots happened with the original charger plugged in. Why that didn't happen to the stock ROM I can't explain.
The original Samsung battery scares me a bit. It has become 1-2 mm thicker. Looks like an accident waiting to happen. Have to dispose of safely somehow...quick...

[Q] Camera causes reboot on some ROM's

ROM's based on original firmware and CM 11 work fine. Doom/Zombie/etc kernels work fine.
But SlimKAT, any official 4.1 or 4.2, Vanir or any other ROM causes hot reboot when opening camera for second time.
First time everything is OK, I can use e.g. PAC ROM for several days, but if I close the camera and open it again (without rebooting) it causes hot reboot. Always.
But CM11 is rock stable so is any original 4.3 and higher.
Any help with that?
Thanx!

slimKAT weekly 5.6's camera works without any problems .bro.

Orangewanted said:
slimKAT weekly 5.6's camera works without any problems .bro.
Click to expand...
Click to collapse
Yes, I know. Once ...
If I start if again it causes hor reboot.
CM 11, stock 4.3/4.4 no problems ...

Z O X said:
Yes, I know. Once ...
If I start if again it causes hor reboot.
CM 11, stock 4.3/4.4 no problems ...
Click to expand...
Click to collapse
Have you done a fresh installation ?
In CWM perform wipe data/factory reset and in mounts and storage section format system.
In TWRP choose advanced in wipe section and wipe dalvik cache, cache, system and data.
or please check your gapps which may cause the problem.
always use the gapps from here http://forum.xda-developers.com/showthread.php?t=2397942

Orangewanted said:
Have you done a fresh installation ?
In CWM perform wipe data/factory reset and in mounts and storage section format system.
In TWRP choose advanced in wipe section and wipe dalvik cache, cache, system and data.
or please check your gapps which may cause the problem.
always use the gapps from here http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
Yes, always fresh.
Point is, even flashed TFT ver 4.1 and 4.2 have same issues. Only 4.3 and 4.4 work OK :-/
Those are the GAPPS I always use ... Don't know. I'll try replacing camera libraries with version that work and see how that goes ...

[Q] exhibit 2 4g hangs on incoming call

Dear all,
i have an old samsung galaxy exhibit 2 4g and decided to install a custom rom. i used below mentioned link for the ROMs.
http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
i have tried majority of the ROMs after v4 but all of them are giving me same problem
Phone hangs on incoming call and only vibrates no sound. and i have to ultimately pull the battery out.
the issue is not observed on stock ROM.
It is also not observed on REMICS 3.0.1 but only if i disable backup and restore option. disabled this option on other custom rom as well but did not fix the issue on other ROMs.
I would appreciate any help.

wonderwall_85 said:
Dear all,
i have an old samsung galaxy exhibit 2 4g and decided to install a custom rom. i used below mentioned link for the ROMs.
http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
i have tried majority of the ROMs after v4 but all of them are giving me same problem
Phone hangs on incoming call and only vibrates no sound. and i have to ultimately pull the battery out.
the issue is not observed on stock ROM.
It is also not observed on REMICS 3.0.1 but only if i disable backup and restore option. disabled this option on other custom rom as well but did not fix the issue on other ROMs.
I would appreciate any help.
Click to expand...
Click to collapse
sorry late on this. which cwm or twrp version are you using? jfbs twrp 2.7.1.0 or cwm 6.0.4.8 is the latest which is need on kk roms also cars1198 has cwm6.0.4.9. picking one of these 3 is user preference. for kk roms lastest slimbean 7/7build and dcm 6/20 by jfbs is stable and for cm11 cars1198 6/19 build is pretty stable. any of these 3 should work just fine without any issues with latest recoveries. if you dont know how its just like flashing a rom except when you reboot you want to reboot boot back into recovery then do a fresh install. also on a complete fresh install what ever is on on your internal sdcard that you want to keep move it to external sd or pc. then format /system /data /cache /android secure and /sdcard0. then install rom only, reboot and wait for it to fully boot up. then reboot back into recovery and install gapps. then wipe dalvik-cache and reboot. after you sign into gplay give the phone time to sync your contacts and so forth which will bog down the phone for 1-30mins or longer depending how much needs to be sync. after that you should be ready to go with no or very minor issues. in which you would ask in the appropriate rom op.

TripFX said:
sorry late on this. which cwm or twrp version are you using? jfbs twrp 2.7.1.0 or cwm 6.0.4.8 is the latest which is need on kk roms also cars1198 has cwm6.0.4.9. picking one of these 3 is user preference. for kk roms lastest slimbean 7/7build and dcm 6/20 by jfbs is stable and for cm11 cars1198 6/19 build is pretty stable. any of these 3 should work just fine without any issues with latest recoveries. if you dont know how its just like flashing a rom except when you reboot you want to reboot boot back into recovery then do a fresh install. also on a complete fresh install what ever is on on your internal sdcard that you want to keep move it to external sd or pc. then format /system /data /cache /android secure and /sdcard0. then install rom only, reboot and wait for it to fully boot up. then reboot back into recovery and install gapps. then wipe dalvik-cache and reboot. after you sign into gplay give the phone time to sync your contacts and so forth which will bog down the phone for 1-30mins or longer depending how much needs to be sync. after that you should be ready to go with no or very minor issues. in which you would ask in the appropriate rom op.
Click to expand...
Click to collapse
hey there,
thanks for the reply.
I am using cwm v6.0.1.2.
What i get from your reply is that
flash the latest recovery, reboot in to recovery again
flash your suggested ROM, fresh install
boot in to the OS
boot again in to recovery and install gapps
boot the phone and give it a couple of hours to sych data and update if any and then see if its working or not.
i will give it a try and will let you know. btw i was not facing any issues on any other roms except the mentioned issue and all the roms were running pretty fast.

wonderwall_85 said:
hey there,
thanks for the reply.
I am using cwm v6.0.1.2.
What i get from your reply is that
flash the latest recovery, reboot in to recovery again
flash your suggested ROM, fresh install
boot in to the OS
boot again in to recovery and install gapps
boot the phone and give it a couple of hours to sych data and update if any and then see if its working or not.
i will give it a try and will let you know. btw i was not facing any issues on any other roms except the mentioned issue and all the roms were running pretty fast.
Click to expand...
Click to collapse
everyones had different issues using older recoveries. cwm 6.0.4.4-5 works for anything jb or below. the higher ones are for kk roms which is the most recent and both cars and jfbs kk roms are better then aoip or any of the other roms. Since ion hybrid thanks to adc team and more stable kk roms are out now. imo any of cars is cm roms are good for the everyday people while jfbs slim and dcm are geared more to those who want more features and customization (advance users). i always test both devs roms but personally i like jfbs roms better as far as what i do but any of the 3 are stable for everyday use now. but ya let me know if that helped out.

TripFX said:
everyones had different issues using older recoveries. cwm 6.0.4.4-5 works for anything jb or below. the higher ones are for kk roms which is the most recent and both cars and jfbs kk roms are better then aoip or any of the other roms. Since ion hybrid thanks to adc team and more stable kk roms are out now. imo any of cars is cm roms are good for the everyday people while jfbs slim and dcm are geared more to those who want more features and customization (advance users). i always test both devs roms but personally i like jfbs roms better as far as what i do but any of the 3 are stable for everyday use now. but ya let me know if that helped out.
Click to expand...
Click to collapse
tried cynanogen1, worked smoothly but did not fix the issue
slimkat 4.4.4, faced FC every second. it was almost impossible to even boot the phone.
first i thought there is some hardware issue but the phone is working fine on 2 roms so i guess thats out of the question. let me know if you could suggest something else.

wonderwall_85 said:
tried cynanogen1, worked smoothly but did not fix the issue
slimkat 4.4.4, faced FC every second. it was almost impossible to even boot the phone.
first i thought there is some hardware issue but the phone is working fine on 2 roms so i guess thats out of the question. let me know if you could suggest something else.
Click to expand...
Click to collapse
which cwm or twrp version did you use. I too was facing the fc's on my phone for a while but after using twrp 3.7.1.0 or cwm 6.0.4.8 i dont have that issue anymore. my personal exact order including mods i use.
1. flash twrp 3.7.1.0 < if you already have this or cwm 6.0.4.8 already
2. Format /system then /cache, then /data/ then /internal sd < so everything except /boot and /external sd
3. flash rom < if doing cm11 you can flash oc kernel right after
4. flash supersu < optional its the same as stock superuser but little more options like allow su on boot (on xda)
5. wipe davlik cache and reboot system
6. reboot boot back into recovery
7. flash gapps < if slim get it from slimroms, if dcm or cm11 the gapps from cars1189 mass cm build 1-5-14.
8. flash malive booster < (on xda)
9. wipe dalvik cache and reboot system
10. once full loaded back in install seeder 2.0 (on xda) have a check mark on all 3 with light profile then enable.
11. then finish signing in google account and updating apps. 30mins later its smooth as butter.

TripFX said:
which cwm or twrp version did you use. I too was facing the fc's on my phone for a while but after using twrp 3.7.1.0 or cwm 6.0.4.8 i dont have that issue anymore. my personal exact order including mods i use.
1. flash twrp 3.7.1.0 < if you already have this or cwm 6.0.4.8 already
2. Format /system then /cache, then /data/ then /internal sd < so everything except /boot and /external sd
3. flash rom < if doing cm11 you can flash oc kernel right after
4. flash supersu < optional its the same as stock superuser but little more options like allow su on boot (on xda)
5. wipe davlik cache and reboot system
6. reboot boot back into recovery
7. flash gapps < if slim get it from slimroms, if dcm or cm11 the gapps from cars1189 mass cm build 1-5-14.
8. flash malive booster < (on xda)
9. wipe dalvik cache and reboot system
10. once full loaded back in install seeder 2.0 (on xda) have a check mark on all 3 with light profile then enable.
11. then finish signing in google account and updating apps. 30mins later its smooth as butter.
Click to expand...
Click to collapse
you are the MAN man. from your instructions i deduced that i was not wiping davlik cache after flashing but before. now every rom is working fine, no issue is observed. thanks
Since you know your stuff could you let me know which rom is the best in terms of performance and battery life?
thanks again

wonderwall_85 said:
you are the MAN man. from your instructions i deduced that i was not wiping davlik cache after flashing but before. now every rom is working fine, no issue is observed. thanks
Since you know your stuff could you let me know which rom is the best in terms of performance and battery life?
thanks again
Click to expand...
Click to collapse
Stock wise Slim has better performance over cm11 with slightly less bettery life. to get the best performance to battery life follow my oc guide i posted. you want to keep the voltage equal to or less then stock voltage while having the highest frequency as possible. the lower voltage from stock the higher battery life over stock will be. if you do plan on overclocking and undervolting your self make sure you read my oc entirely before attemping. the oc guide methodology is the same for anything that can overclock including desktop cpus, gpus, and yes some nics. some routers as long as it can support a 3rd party firmware such as ddwrt or openwrt. other phones that have oc and voltage control support. you may also get some extra performance and battery saving by trying different build.prop tweaks or mods or any of the combination. some may help you and not me and vise versa and some may help everyone. its more about find what works best for you for what you do.

Can't turn off my nook hd+ plz help

Im using nook hd+ with latest cm12.1
When i shut down my nook, it automatically restarts
After like 5 seconds.
Please help me how can i turn off my nook??

Do you have power connected? I'm not sure, but I think the hardware forces a power-on when power is connected.

No the power is not connected

This issue has been discussed at length in #Amaces's thread where this ROM is located.
Have you looked there?

FirePsych said:
This issue has been discussed at length in #Amaces's thread where this ROM is located.
Have you looked there?
Click to expand...
Click to collapse
Thanks. this thread helped a lot.
It seems like this issue has been fixed in latest 08/03 version of CM12.1.
I will try installing this version today.
Thanks.

Does anyone know how I can fully wipe my current CM 12.1 and install new-latest CM12.1 safely?
Is this safe way to do this ?
- insert sd card and reboot in recovery mode
- wipe data / factory reset
- wipe cache partition
- install zip files(recovery/cm12.1/gapps)
- wipe dalvik cache
- reboot
Is this safe way to install cm12.1 - 0803 from my current cm12.1 - 0723??
Thank you

I would reboot after flashing recovery.
Reboot after flashing ROM. Set up the basics. Make a back-up. Flash GAPPS, log into your Google account and set up the basics. Make another back-up , wipe cache/ dalvik,, reboot, and then finish setting up your device.
I think you might want to wipe system to and look into converting Cache and Data to F2FS.
Also, I typically wipe everything 3 times when switching ROMs.
Sent from my XT1060 using Tapatalk

I installed cm12.1 0803 version but i am still having this problem ......

FirePsych said:
I would reboot after flashing recovery.
Reboot after flashing ROM. Set up the basics. Make a back-up. Flash GAPPS, log into your Google account and set up the basics. Make another back-up , wipe cache/ dalvik,, reboot, and then finish setting up your device.
I think you might want to wipe system to and look into converting Cache and Data to F2FS.
Also, I typically wipe everything 3 times when switching ROMs.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Dear sir,
Thank you for your information at my thread.
I am currently running cm 12.1 0803 version with the same auto-restarting problem.
(the shut down functions works sometimes when i shut my nook in landscape mode)
However, I also found out that my Bluetooth mouse is not compatible with CM 12.1 and
I am planning to install cm11 version(because i heard that my mouse works in cm11 version fine).
And i would like to ask you these(I hope you will be kind enough to answer them) :
1. is there a way to make my bluetooth mouse work in CM 12.1 version?
2. which version(date) of cm11 will you recommend me?
3. you mentioned about changing cache and data to fsf2, can you tell me how i can do this? what would be the advantage?
4. you mentioned about wiping everything 3 times, do you wipe 3 times with only booting once? or do you reboot everytime you wipe?
5. Please tell me if this procedure is correct, if i will change my cm 12 to cm 11
- insert sd card and reboot in recovery mode
- wipe data / factory reset
- wipe cache partition
- install recovery and reboot
- install cm rom and reboot
- install gapps and reboot
- format/system(3times?)
- format/data(3times?)
- format/cache(3times?)
- format/bootdata (3times?)
- format/data and sd card (3times?)
- wipe dalvik/cache
- reboot
Thank you.

tnckd13 said:
Dear sir,
Thank you for your information at my thread.
I am currently running cm 12.1 0803 version with the same auto-restarting problem.
(the shut down functions works sometimes when i shut my nook in landscape mode)
However, I also found out that my Bluetooth mouse is not compatible with CM 12.1 and
I am planning to install cm11 version(because i heard that my mouse works in cm11 version fine).
And i would like to ask you these(I hope you will be kind enough to answer them) :
1. is there a way to make my bluetooth mouse work in CM 12.1 version?
2. which version(date) of cm11 will you recommend me?
3. you mentioned about changing cache and data to fsf2, can you tell me how i can do this? what would be the advantage?
4. you mentioned about wiping everything 3 times, do you wipe 3 times with only booting once? or do you reboot everytime you wipe?
5. Please tell me if this procedure is correct, if i will change my cm 12 to cm 11
- insert sd card and reboot in recovery mode
- wipe data / factory reset
- wipe cache partition
- install recovery and reboot
- install cm rom and reboot
- install gapps and reboot
- format/system(3times?)
- format/data(3times?)
- format/cache(3times?)
- format/bootdata (3times?)
- format/data and sd card (3times?)
- wipe dalvik/cache
- reboot
Thank you.
Click to expand...
Click to collapse
1) Shut down and boot into recovery isn't working for me on 8/03 either, but I haven't had time to mess with it to find out why not. Maybe wiping system and then flashing 8/03 might work. I wouldn't wipe Data if you're coming from the last July version of 12.1
But, if you hold down the power button long enough, the tablet will shut down. I just can't shut down from the menu.
Once you're completely off, you can boot into recovery with the power/n combo.
I also tried the Reboot shortcut and widget from ROMToolbox Pro and that didn't work either.
1) I don't know much about how to make bluetooth work. I know that some stuff works on these builds and some stuff doesn't
2) I'm using Amaces's Unofficial CM 12.1. I never found a CM 11 that worked well on my Nook HD+
3) Theoretically,F2FS uses flash memory more efficiently. I think we're talking nano or micro seconds here, but many say it helps. To answer your question about Why and How, I'd have to look it up to give you clear instructions. You can do the same, and you'll learn more by researching it yourself, than by me explaining it poorly.
3) I wipe three times, then reboot
------NOTE---
I'm barely above a novice and my advice isn't worth diddly squat
Below is what generally has worked for ME and what I've read that other folks do. It does not mean this is the best way to do it.
The MOST important thing is to read a lot, then read some more, take your time and make back-ups often.
You need to look in the CM11 threads to see what Recoveries are compatible with CM11. Not all of the current Recoveries are backwards compatible.
AND you're better of asking about flashing to CM11 in a CM11 thread, rather than a CM12 thread.
I don't use an SD, I do everything off of the onboard memory.
I use TWRP as my recovery.
1) If I'm going to a new ROM, rather than do Factory Data Reset, I manually go in and choose to wipe System, Dalvik, Data and Cache. I've never touched BootData as far as I remember. I do that 3 times.
2) Flash new recovery if you want.
3) Reboot into recovery too make sure the new recovery flashed okay.
4) I then flash the ROM, wipe Dalvik and Cache 1 time, boot into the ROM to make sure it was a good flash and set up the bare minimum.
5) Boot to recovery
6) Flash GAPPS and wipe Dalvik and Cache 1 time (usually)
7) Reboot and make sure there were no problems with GAPPS
8) Set up my minimum accounts and apps.
9) Boot to recovery and make a back up.
10) Reboot and install the rest of my apps.
11) Make sure everything works okay and once I'm satisfied, make another back up.
If I'm going from one version of the same ROM to the next update, I just flash the latest version, wipe Dalvik and Cache 1 or 2 times and reboot.
Thereafter, I make back-ups ever week or so, depending on how much I've been using my tablet and how much time I have.