Related
Hello,
I flashed CM 10.1 and before the CyanogenMod animation boot starts, I get this screen for 1-2 seconds:
Is it a bug specific to the CM version I downloaded maybe? Or a bug and I need to fix it somehow?
Btw, is there a place / thread where I can report this bug to CyanogenMod developers maybe?
Thanks!
I am getting the same thing after I have updated to Official Jelly bean ROM through Mobile odin. Other than this, my Tab is functioning smooth and without any glitches. So I am not bothered at all with this.
If any of you can throw any light on this will be welcome.
Sent from my GT-P5100 using Tapatalk 2
verynoob said:
Hello,
I flashed CM 10.1 and before the CyanogenMod animation boot starts, I get this screen for 1-2 seconds:
Is it a bug specific to the CM version I downloaded maybe? Or a bug and I need to fix it somehow?
Btw, is there a place / thread where I can report this bug to CyanogenMod developers maybe?
Thanks!
Click to expand...
Click to collapse
U must update to official jelly been 4.1.1 first using Odin, then installed cm10.1.. Or if u installed cm10.1 over ics, then u need to install jelly bean bootloader to avoid such crappy screen.. Search it..
¥ Help = Thanked ¥
Sent from Heaven
verynoob said:
Hello,
I flashed CM 10.1 and before the CyanogenMod animation boot starts, I get this screen for 1-2 seconds:
Is it a bug specific to the CM version I downloaded maybe? Or a bug and I need to fix it somehow?
Btw, is there a place / thread where I can report this bug to CyanogenMod developers maybe?
Thanks!
Click to expand...
Click to collapse
This is a known issue but with very low priority. It's because you have 4.0.4 bootloader. It is one of the reasons I've recommended flashing stock 4.1 from a country nearby yours. That way you wouldn't have this strange screen, and hopefully it would also take care of this so called baseband problem or something.
canis999 said:
This is a known issue but with very low priority. It's because you have 4.0.4 bootloader. It is one of the reasons I've recommended flashing stock 4.1 from a country nearby yours. That way you wouldn't have this strange screen, and hopefully it would also take care of this so called baseband problem or something.
Click to expand...
Click to collapse
god_creature said:
U must update to official jelly been 4.1.1 first using Odin, then installed cm10.1.. Or if u installed cm10.1 over ics, then u need to install jelly bean bootloader to avoid such crappy screen.. Search it..
¥ Help = Thanked ¥
Sent from Heaven
Click to expand...
Click to collapse
Thanks you two,
Can I now flash stock rom over CM 10.1? All I need to do is download a firmware from SamMobile and flash it over the CM? or you can't do that? because got_creature said that if I already installed CM I need to install only the bootloader.
Btw, Is flashing stock rom from SamMobile done same way in CWM > Install Zip from sd? I am asking that because I did download a stock firmware, but it weights much much more than CM 10.1 so I'm afraid to flash it (CM weights about 150MB and official Samsung rom weights about 700MB)
verynoob said:
Thanks you two,
Can I now flash stock rom over CM 10.1? All I need to do is download a firmware from SamMobile and flash it over the CM? or you can't do that? because got_creature said that if I already installed CM I need to install only the bootloader.
Btw, Is flashing stock rom from SamMobile done same way in CWM > Install Zip from sd? I am asking that because I did download a stock firmware, but it weights much much more than CM 10.1 so I'm afraid to flash it (CM weights about 150MB and official Samsung rom weights about 700MB)
Click to expand...
Click to collapse
You can install only the bootloader, but it is considered more dangerous than flashing stock rom, which will give you the same effect.
Stock weights much more than CM, because it is heavily bloated, so that is normal.
And you need to flash stock rom via Odin, for the changes in bootloader to take effect. Than you flash CM again, the same way you did it before. Just remember to always make a clean installation (factory reset, clear data and cache, optionally format \system through recovery, to avoid bootloop or getting stuck on bootlogo. And if happens anyway, don't panic, just boot into recovery and again factory reset and clear data and cache.
canis999 said:
You can install only the bootloader, but it is considered more dangerous than flashing stock rom, which will give you the same effect.
Stock weights much more than CM, because it is heavily bloated, so that is normal.
And you need to flash stock rom via Odin, for the changes in bootloader to take effect. Than you flash CM again, the same way you did it before. Just remember to always make a clean installation (factory reset, clear data and cache, optionally format \system through recovery, to avoid bootloop or getting stuck on bootlogo. And if happens anyway, don't panic, just boot into recovery and again factory reset and clear data and cache.
Click to expand...
Click to collapse
does the order of doing these things matter? I should format \system after doing other things? btw formatting system is done by "mounts and storage>format /system" ? just to be sure because I've never done that
verynoob said:
does the order of doing these things matter? I should format \system after doing other things? btw formatting system is done by "mounts and storage>format /system" ? just to be sure because I've never done that
Click to expand...
Click to collapse
Format system just before flashing the zip with cm10.1. There is absolutely no need of doing it before flashing stock via Odin. To be honest, there is usually no need of doing it at all, there was one guy that said somewhere on xda that it may reduce the possibility of some bugs occurring during everyday use, so you may consider this step worth considering.
And yes, it's done in mounts and storage in recovery.
verynoob said:
does the order of doing these things matter? I should format \system after doing other things? btw formatting system is done by "mounts and storage>format /system" ? just to be sure because I've never done that
Click to expand...
Click to collapse
Format system under mount & storage = correct
Pattern doesn't matter.. Jus clear cache, delvk, wipe data, format system in any manner
¥ Help = Thanked ¥
Sent from Heaven
canis999 said:
Format system just before flashing the zip with cm10.1. There is absolutely no need of doing it before flashing stock via Odin. To be honest, there is usually no need of doing it at all, there was one guy that said somewhere on xda that it may reduce the possibility of some bugs occurring during everyday use, so you may consider this step worth considering.
And yes, it's done in mounts and storage in recovery.
Click to expand...
Click to collapse
god_creature said:
Format system under mount & storage = correct
Pattern doesn't matter.. Jus clear cache, delvk, wipe data, format system in any manner
¥ Help = Thanked ¥
Sent from Heaven
Click to expand...
Click to collapse
Ty!
Btw, I looked in SamMobile and there is no jelly bean version for my country, and I did not see any jelly bean version that matches my country's "MODEM", will that cause problems with Phone?
(*does Odin version matter? I am using the 1.85).Is it possible to use Mobile Odin Lite instead to flash the stock rom? or it's not safe?
verynoob said:
Ty!
Btw, I looked in SamMobile and there is no jelly bean version for my country, and I did not see any jelly bean version that matches my country's "MODEM", will that cause problems with Phone?
(*does Odin version matter? I am using the 1.85).Is it possible to use Mobile Odin Lite instead to flash the stock rom? or it's not safe?
Click to expand...
Click to collapse
Mobile Odin does not have access to bootloader, so you need to use pc odin for this operation. And as I said, flash the stock 4.1 rom from a country near your, and everything should be fine.
verynoob said:
Ty!
Btw, I looked in SamMobile and there is no jelly bean version for my country, and I did not see any jelly bean version that matches my country's "MODEM", will that cause problems with Phone?
(*does Odin version matter? I am using the 1.85).Is it possible to use Mobile Odin Lite instead to flash the stock rom? or it's not safe?
Click to expand...
Click to collapse
U can install other countries update.. Not an issue.. Odin 1.85 is good.. Pc Odin better than mobile Odin..
¥ Help = Thanked ¥
Sent from Heaven
hey guys
my first post on xda actually yesterday i updated my xgamerz v2.2 rom to xgamerz v3 using clockworkmod recovery v6.0.28 everything else worked fine except it vant reboot into recovery ... i CAN reboot in download mode but not recovery.
when i reboot into recovery the samsung galaxy sl page slowly fades away and again reboots the phone into normal mode without going to recovery ( i.e. directly loading to os )
plz help asap
for now do a clean flash from ddlf2 then upgrade v3.. your problem will get solved.. and always wipe dalvik cache and format the system when upgrading the same custom rom. if you are going to any other custom rom just do full clean flash form ddlf2.. so that the rom won't cause any problem in your day to day life..
hope this helps you.
maxs8007 said:
for now do a clean flash from ddlf2 then upgrade v3.. your problem will get solved.. and always wipe dalvik cache and format the system when upgrading the same custom rom. if you are going to any other custom rom just do full clean flash form ddlf2.. so that the rom won't cause any problem in your day to day life..
hope this helps you.
Click to expand...
Click to collapse
you mean go back to gingerbread 2.3.6 then flash cm10 and then xgamerz with all user data gone
instead of doing all this , i was wondering if i could flash a recovery using nandroid manager app( it has an option to flash recovery) but iam not getting a proper download link for my firmware. . . plz guide
try this : https://googledrive.com/host/0B4xN9...3.0/kernel-cm-10-20130906-galaxysl-signed.zip . and if this didn't work then you'll need to do a clean flash. just do titanium backup of all apps and also backup all you contacts and messages. restore them when you flash v3. you'll get all your userdata and apps as it is. and no need to flash cm10 after ddlf2, just directly flash v3 after flashing ddlf2 ( v3 is based on cm10, so no need to flash that)
if this didn't work then you'll need to do a clean flash. just do titanium backup of all apps and also backup all you contacts and messages. restore them when you flash v3. you'll get all your userdata and apps as it is. and no need to flash cm10 after ddlf2, just directly flash v3 after flashing ddlf2 ( v3 is based on cm10, so no need to flash that) [/QUOTE]
i have downloaded it but neither rom tool box nor
nandroid manager app is able to restore it... will u plz tell me how to use it.
maxs8007 said:
for now do a clean flash from ddlf2 then upgrade v3.. your problem will get solved.. and always wipe dalvik cache and format the system when upgrading the same custom rom. if you are going to any other custom rom just do full clean flash form ddlf2.. so that the rom won't cause any problem in your day to day life..
hope this helps you.
Click to expand...
Click to collapse
reply
try this application : https://play.google.com/store/apps/details?id=com.cgollner.flashify if this didn't work then you'll not have any other way except clean flash. till my knowledge I think it's not possible to flash any recovery on jb ROM's due to different partitioning. i'll still suggest you to do a full app backup with titanium backup and restore it when you flash v3. happy flashing
maxs8007 said:
try this application : https://play.google.com/store/apps/details?id=com.cgollner.flashify if this didn't work then you'll not have any other way except clean flash. till my knowledge I think it's not possible to flash any recovery on jb ROM's due to different partitioning. i'll still suggest you to do a full app backup with titanium backup and restore it when you flash v3. happy flashing
Click to expand...
Click to collapse
nope that didnt work :'(
go to xgamers v3 page ( forum.xda-developers.com/showthread.php?t=2192613) and read the 3rd post which says " IMPORTANT! READ BEFORE FLASHING
THIS RELEASE!" you'll come to know what I'm trying to tell you since beginning.. most important : 1st and 5th point.
Hey guys, is there a way to just Flash a stock Boost ROM instead of having to flash the stock firmware using PC?
ishred11 said:
Hey guys, is there a way to just Flash a stock Boost ROM instead of having to flash the stock firmware using PC?
Click to expand...
Click to collapse
From what I've found, this is the only flashable stock ROM:
http://androidforums.com/cdma-moto-...k-4-4-2-deodexed-unmodified-boost-mobile.html
I haven't tried flashing it, myself - when I need to go stock, I just flash the stock firmware via PC.
:good:
Thanks, will there be problems going from 4.4.4 to 4.4.2?
ishred11 said:
Thanks, will there be problems going from 4.4.4 to 4.4.2?
Click to expand...
Click to collapse
I couldn't tell you, to be honest.
Make a Nandroid, and if the flash fails, or you encounter issues, restore your backup.
Ok thanks, the last time I made a backup and did a wipe for the phone, my backup also go deleted. Does it only do that on TWP?
ishred11 said:
Ok thanks, the last time I made a backup and did a wipe for the phone, my backup also go deleted. Does it only do that on TWP?
Click to expand...
Click to collapse
I use this recovery:
http://forum.xda-developers.com/showthread.php?t=2639583
I haven't used TWRP on this device, so I couldn't tell you with complete certainty. PhilZ's recovery has an option to clean your device for flashing a new ROM (wipes data, system, dalvik, & cache). SD contents will remain untouched.
OK thanks very much
Rooted with CWM as recovery. Shield Tablet has OTA update but obviously can't install with CWM. What is the simplest way to stay up to date and keep root?
Sent from my SHIELD Tablet using xda premium
Still looking for help with this. I have a basic understanding on how things work. Is this what I need to do?
Flash original recovery
Reboot then do the OTA update
Then refresh CWM
Will I lose root?
Sent from my SHIELD Tablet using xda premium
Scoobydumb said:
Still looking for help with this. I have a basic understanding on how things work. Is this what I need to do?
Flash original recovery
Reboot then do the OTA update
Then refresh CWM
Will I lose root?
Sent from my SHIELD Tablet using xda premium
Click to expand...
Click to collapse
That's not the way to go at all.
Whenever there's an update, flash the incremental OTA file HERE.
Flashing the stock recovery will not allow taking OTA's.
thank you for the link, which command do I use to flash the incremental update looks like the instructions there are for a full update. thanks again
Scoobydumb said:
thank you for the link, which command do I use to flash the incremental update looks like the instructions there are for a full update. thanks again
Click to expand...
Click to collapse
Um, just flash it in TWRP or CWM, only need to flash cache and dalvik cache, but that's optional.
Im also sorta nooby about this. The only thing I have ever done is flash Cyanogen Mod and install TWRP on my Galaxy Note 3. I have rooted my Shield and installed Uno TWRP out of the box. Thus its not on the latest update. Just to clarify so I don't f*ck up. I just download the latest OTA, copy to my sdcard and flash in TWRP? And that will just update it without having to lose all my apps etc?
EDIT: So incremental updates take from version x.x to version x.x? Oh, and is it true that root is wiped? Im happy to re-root everytime.
Singularity_iOS said:
Im also sorta nooby about this. The only thing I have ever done is flash Cyanogen Mod and install TWRP on my Galaxy Note 3. I have rooted my Shield and installed Uno TWRP out of the box. Thus its not on the latest update. Just to clarify so I don't f*ck up. I just download the latest OTA, copy to my sdcard and flash in TWRP? And that will just update it without having to lose all my apps etc?
EDIT: So incremental updates take from version x.x to version x.x? Oh, and is it true that root is wiped? Im happy to re-root everytime.
Click to expand...
Click to collapse
Yes that's true, just make sure you flash the incremental updates and not the full OTA's. And as far as root I'm not sure if you loose it, while in recovery might as well just flash SuperSU to be safe.
FoxyDrew said:
Yes that's true, just make sure you flash the incremental updates and not the full OTA's. And as far as root I'm not sure if you loose it, while in recovery might as well just flash SuperSU to be safe.
Click to expand...
Click to collapse
Ok thanks. One more question. How would I go about checking the rom version? Unless I'm missing it I can only see the Android version, which is 5.0.
EDIT: i'm getting some sort of error when trying to flash the zips. I downloaded (for wifi) 2.0 to 2.1, 2.1 to 2.2 and 2.2 to 2.2.1. Whenever I try to flash it just fails.
Singularity_iOS said:
EDIT: i'm getting some sort of error when trying to flash the zips. I downloaded (for wifi) 2.0 to 2.1, 2.1 to 2.2 and 2.2 to 2.2.1. Whenever I try to flash it just fails.
Click to expand...
Click to collapse
Yes, because you need to flash 2.2.1 full ota via custom recovery, and wipe cache dalvik. Then flash again your custom recovery. Then supersu.
If you are rooted with custom rec (twrp, cwm, Philz) you need to flash full ota.
Wouldn't the tablet be wiped then? And if this is the case everytime can't I just keep the stock recovery and sideboard a custom one?
Nope. You just flash on top, like a dirty flash. I use TWRP and Ive done it twice and still kept everything. The only wipe you need to do is cache & dalvik after flashing full OTA.
If you keep stock rec just for the fact of being rooted incremental OTAs wont work
NaminatoR1254jaime.sier said:
Nope. You just flash on top, like a dirty flash. I use TWRP and Ive done it twice and still kept everything. The only wipe you need to do is cache & dalvik after flashing full OTA.
If you keep stock rec just for the fact of being rooted incremental OTAs wont work
Click to expand...
Click to collapse
I just flashed full OTA via CWM and lost root.
I had to re fastboot flash recovery and then sideload supersu to root.
It sounds like TWRP is holding root.
perky nerky said:
I just flashed full OTA via CWM and lost root.
I had to re fastboot flash recovery and then sideload supersu to root.
It sounds like TWRP is holding root.
Click to expand...
Click to collapse
On my previous instructions I pointed out to (after flashing ota) to reflash custom rec and supersu.
NaminatoR1254jaime.sier said:
Yes, because you need to flash 2.2.1 full ota via custom recovery, and wipe cache dalvik. Then flash again your custom recovery. Then supersu.
If you are rooted with custom rec (twrp, cwm, Philz) you need to flash full ota.
Click to expand...
Click to collapse
With twrp I do it literally after flashing full ota. I leave recovery to reboot to system right when Im done flashing everything.
I have miui 8.5 stable 8.5.3.0 which it was installed via offical rom. but now there is also miui v9.5.40 but it gives error when i try tp uğdate from again system settings
I have trwp. I dont hve root.
I dont want to lose data. i want to upgrade to latest roms. what are steps? if i directly flash what happens?
Still waiting for help
Any help
You must use mi flash ...
Download latest fastboot rom ...
select flash all expect data and storage before start flash
amir-kia said:
You must use mi flash ...
Download latest fastboot rom ...
select flash all expect data and storage before start flash
Click to expand...
Click to collapse
IT will not wipe data? and should i download official rom?
Cursed Chico said:
IT will not wipe data? and should i download official rom?
Click to expand...
Click to collapse
Your miui version is very old ... May wipe data ...
Yes download latest official miui rom
amir-kia said:
Your miui version is very old ... May wipe data ...
Yes download latest official miui rom
Click to expand...
Click to collapse
so how can i keep my desktop icons, settings etc in case it will wipe data?