Related
I flashed cm9 on my gt-p3110. cm9 is great and it was successful.
then i tried to flash the new stock firmware 4.0.4 using this http://forum.xda-developers.com/showthread.php?t=1838072. But my tab wont start. it only shows the logo of samsung. what have i done wrong. what should i do?
the odin can still read my tab.
Im downloading now the 4.0.3 version and i will flash it again. Am i doing the right thing?
please help me. im only a newbie and i want to learn.
EDIT:
Solved by doing a wipe data and wipe cache.
It is known issue (saw it on the 4pda forum), it is happens because 4.0.4 doesn't contain all needed files, it is appears like update for the 4.0.3.
You need flash 4.0.3 what contain three md5 files: bootloader, csc and platform. After it will be done you can flash 4.0.4 without any surprises like this one.
thanks for the response. where can i get the file? the one i downloaded on sammobile doesnt contain pit file.
There is link to my Dropbox, download archive with Odin and you will find PIT file for our tablet (There is PIT only for 8Gb version)
Ailir said:
It is known issue (saw it on the 4pda forum), it is happens because 4.0.4 doesn't contain all needed files, it is appears like update for the 4.0.3.
You need flash 4.0.3 what contain three md5 files: bootloader, csc and platform. After it will be done you can flash 4.0.4 without any surprises like this one.
Click to expand...
Click to collapse
Is it true that 4.0.3 have more md5 files inside the principal md5 file but doesn't mean that you have to flash it. For example, the bootloader doesn't change because you flash CM9. And Pit file? When you install CM9 you don't change partition of the emmc so why you are saying to flash pit file?!
nfribeiro said:
Is it true that 4.0.3 have more md5 files inside the principal md5 file but doesn't mean that you have to flash it. For example, the bootloader doesn't change because you flash CM9. And Pit file? When you install CM9 you don't change partition of the emmc so why you are saying to flash pit file?!
Click to expand...
Click to collapse
Thanks for the info, now I know why and when PIT file must be used.
P.S. I used it all the time because it was in manuals for the Odin what I found on the tsar3000.com
Diable Jambe said:
I flashed cm9 on my gt-p3110. cm9 is great and it was successful.
then i tried to flash the new stock firmware 4.0.4 using this http://forum.xda-developers.com/showthread.php?t=1838072. But my tab wont start. it only shows the logo of samsung. what have i done wrong. what should i do?
the odin can still read my tab.
Im downloading now the 4.0.3 version and i will flash it again. Am i doing the right thing?
please help me. im only a newbie and i want to learn.
Click to expand...
Click to collapse
Go to recovery (press and hold Vol + and Power buttons and wipe Data/factory reset and wipe cache partitions.
Ailir said:
Thanks for the info, now I know why and when PIT file must be used.
P.S. I used it all the time because it was in manuals for the Odin what I found on the tsar3000.com
Click to expand...
Click to collapse
In my opinion (of couse, I can be wrong) we use to many times the pit file, even when it is not necessary. Nevertheless, I will update this thread with the pit files for GT-P3110.
nfribeiro said:
Go to recovery (press and hold Vol + and Power buttons and wipe Data/factory reset and wipe cache partitions.
Click to expand...
Click to collapse
:good: it works now.
While im in cm9 i flashed the 4.0.4 through odin but it only shows logo. So i tried to flash 4.0.3 but it still the same. I did wipe data factory reset and wipe cache partitions as what nfirbeiro said and it works now. I dont have the root now so I'll try to root again and try to update to 4.0.4.
I still have a question. after i flashed 4.0.4, if did a wipe data reset and cache, will it succeed?
Diable Jambe said:
:good: it works now.
While im in cm9 i flashed the 4.0.4 through odin but it only shows logo. So i tried to flash 4.0.3 but it still the same. I did wipe data factory reset and wipe cache partitions as what nfirbeiro said and it works now. I dont have the root now so I'll try to root again and try to update to 4.0.4.
I still have a question. after i flashed 4.0.4, if did a wipe data reset and cache, will it succeed?
Click to expand...
Click to collapse
I always flash 4.0.3 through Odin and don't root and do the 4.0.4 update OTA.
p3113owner said:
I always flash 4.0.3 through Odin and don't root and do the 4.0.4 update OTA.
Click to expand...
Click to collapse
yes. but you need a rooted to device to delete those unwanted apps. and update OTA is not yet available in my country
I need the MF1 odin flashable package to revert my wifes phone back to stock MF1 and reroot but I can not find where to download the odin package. I have searched through the sticky threads and all I can find is older version prior to MF1. TIA for any help.
deuce237bblock said:
I need the MF1 odin flashable package to revert my wifes phone back to stock MF1 and reroot but I can not find where to download the odin package. I have searched through the sticky threads and all I can find is older version prior to MF1. TIA for any help.
Click to expand...
Click to collapse
Are you looking fir Odin or the MF1 firmware? here is the MF1 firmware for Odin, just unzip then flash with Odin.
http://www.androidfilehost.com/?fid=23134718111254196
Yeah, I am looking for MF1 odin flashable factory image. Will this firmware you have linked revert my wifes phone back to stock MF1?
deuce237bblock said:
Yeah, I am looking for MF1 odin flashable factory image. Will this firmware you have linked revert my wifes phone back to stock MF1?
Click to expand...
Click to collapse
Yes, once it revert back to factory stock, you may received an OTA upgrade to 4.3, make sure don't take the upgrade if not the 4.3 will lock your boot loader and you will NOT able to flash custom rom or custom recovery (you probably knew this right?). Also if you already on the 4.3, you CAN NOT REVERT BACK TO MF1. You will soft brick your device.
buhohitr said:
Yes, once it revert back to factory stock, you may received an OTA upgrade to 4.3, make sure don't take the upgrade if not the 4.3 will lock your boot loader and you will NOT able to flash custom rom or custom recovery (you probably knew this right?)
Click to expand...
Click to collapse
Yes, I plan to update her phone to the new 4.3 ROM in the dev section but right now I can't do anything with the phone because when I am in TWRP recovery it keeps rebooting on me during Restore and when ever I try to wipe as soon as I swipe to wipe it reboots. That's why I am just going to odin back to stock, reroot and flash 4.3 in recovery.
BTW, Thank you for your help!
deuce237bblock said:
BTW, Thank you for your help!
Click to expand...
Click to collapse
Did you try wipe: cache, dalvik cache, system and data? (wipe all 4 at the same time) then reflash the firmware with twrp. BTW what version is your TWRP? It may help to take a look at this http://forum.xda-developers.com/showthread.php?t=2553199
buhohitr said:
Did you try wipe: cache, dalvik cache, system and data? (wipe all 4 at the same time) then reflash the firmware with twrp. BTW what version is your TWRP?
Click to expand...
Click to collapse
Yes, as soon as it says wiping data without wiping data/media it reboots, i'm on latest TWRP version 2.6.3.1.
My phone on that recovery kept on crashing when it had to wipe data. Not sure why, but i had to odin flash cwm recovery. Im afraid to go back to twrp, in fear of the same issue. Any idea what to do?
deuce237bblock said:
Yes, as soon as it says wiping data without wiping data/media it reboots, i'm on latest TWRP version 2.6.3.1.
Click to expand...
Click to collapse
joedajoester said:
My phone on that recovery kept on crashing when it had to wipe data. Not sure why, but i had to odin flash cwm recovery. Im afraid to go back to twrp, in fear of the same issue. Any idea what to do?
Click to expand...
Click to collapse
just go back to twrp and wipe cache see if that works.
joedajoester said:
My phone on that recovery kept on crashing when it had to wipe data. Not sure why, but i had to odin flash cwm recovery. Im afraid to go back to twrp, in fear of the same issue. Any idea what to do?
Click to expand...
Click to collapse
I would just stick to CWM, they have a touch version.
Sent by me.
I'm on cwm now, but when twrp had to touch anything /data related, my phone would reboot to a bootloop, since it corrupt the data when it crashed.
buhohitr said:
just go back to twrp and wipe cache see if that works.
Click to expand...
Click to collapse
Hi everyone,
I have an SM-P900 rooted via the latest Chainfire Auto-Root. After that I installed the custom recovery TWRP 2.8.0.0 via Odin.
Through this custom recovery I installed the cm-11-20141008-UNOFFICIAL-SNAPSHOT-M11-v1awifixx.zip
Before I flashed CM I wiped everything except the internal and external storage. Then I installed the latest gapps and after that the thouchscreen stopped working. The S-Pen is working but I cant use it with my fingers anymore.
Greetings,
Andre
I flashed the latest stock rom (PHN-P900XXUANI1-20141010224130) with Odin, the touchscreen (without SPen) still doesn't work.
Has anybody an idea how I could get it back working?
Flashed an older Stock ROM for my region (DBT, P900XXUANAE) and updated with Kies to P900XXUANC4.
Then I did a factory reset.. still no touchscreen. But the SPen is working fine.
Volans21 said:
Flashed an older Stock ROM for my region (DBT, P900XXUANAE) and updated with Kies to P900XXUANC4.
Then I did a factory reset.. still no touchscreen. But the SPen is working fine.
Click to expand...
Click to collapse
That's very strange - does the touchscreen work in TWRP?
No, its the same in TWRP.. only the S-Pen is working.
Another thing: I noticed that after I flashed a Stock ROM with Odin the configuration and data was not deleted. Is that normal? I can remember when I flashed my SGS2 with Odin it was set to factory defaults everytime. Is that because it was a three-part-firmware with PIT file?
Volans21 said:
No, its the same in TWRP.. only the S-Pen is working.
Another thing: I noticed that after I flashed a Stock ROM with Odin the configuration and data was not deleted. Is that normal? I can remember when I flashed my SGS2 with Odin it was set to factory defaults everytime. Is that because it was a three-part-firmware with PIT file?
Click to expand...
Click to collapse
flashing stock firmware with odin doesn't delete user data.
i have two versions:
1. it's hardware issue
2. flash twrp. wipe everything including internal data, then flash with odin your origianl stock firmware for your region. if it doesn't help, see above.
edit: i read your posts again. it looks like a hardware issue...
I agree, that's why I asked if it worked in TWRP - I feel it may be a hardware issue, coincidental timing?
bonuzzz said:
flashing stock firmware with odin doesn't delete user data.
i have two versions:
1. it's hardware issue
2. flash twrp. wipe everything including internal data, then flash with odin your origianl stock firmware for your region. if it doesn't help, see above.
edit: i read your posts again. it looks like a hardware issue...
Click to expand...
Click to collapse
Volans21 said:
No, its the same in TWRP.. only the S-Pen is working.
Another thing: I noticed that after I flashed a Stock ROM with Odin the configuration and data was not deleted. Is that normal? I can remember when I flashed my SGS2 with Odin it was set to factory defaults everytime. Is that because it was a three-part-firmware with PIT file?
Click to expand...
Click to collapse
Volans21, where are you find three-part-firmware with PIT file?
maybe touchscreen stopped working after flashing pit file? but it only involves on partition scheme.. it's strange
but if touchscreen doesnt work in recovery, i think it's something with hw
stupid question: are you sure you have p900? may be something p901 or another not general device? because if i understand, you lost touchscreen after flashing custom recovery
natives bookmul
bonuzzz said:
Volans21, where are you find three-part-firmware with PIT file?
maybe touchscreen stopped working after flashing pit file? but it only involves on partition scheme.. it's strange
but if touchscreen doesnt work in recovery, i think it's something with hw
stupid question: are you sure you have p900? may be something p901 or another not general device? because if i understand, you lost touchscreen after flashing custom recovery
Click to expand...
Click to collapse
would KIES allow him to update to P900XXUANC4 if he was on a p901, or would it not know the difference.?
bonuzzz said:
Volans21, where are you find three-part-firmware with PIT file?
maybe touchscreen stopped working after flashing pit file? but it only involves on partition scheme.. it's strange
but if touchscreen doesnt work in recovery, i think it's something with hw
stupid question: are you sure you have p900? may be something p901 or another not general device? because if i understand, you lost touchscreen after flashing custom recovery
Click to expand...
Click to collapse
notspike said:
would KIES allow him to update to P900XXUANC4 if he was on a p901, or would it not know the difference.?
Click to expand...
Click to collapse
@bonuzzz
No, I didn't find a three-part-firmware for my SM-P900.. maybe you missunderstood me: Years ago I flashed my Samsung Galaxy S2 (SGS2) with such a firmware.. I always thought, that the PIT file repartitioned my SGS2 and so the ROM was set to factory defaults. And thats why I was asking for a three-part-firmware with PIT file
I'm 100% sure that I have a SM-P900 (No LTE/4G, only Wifi). And thats what I did before the touchscreen stopped working:
A firmware update with Kies 3 to P900XXUANI1
Rooting with CF-AutoRoot (CF-Auto-Root-v1awifi-v1awifixx-smp900.zip)
Flashed TWRP 2.8.0.0 with Odin 3.07
Wiped everything with TWRP except internal/external SDCard
Flashed CM11 with TWRP (cm-11-20141008-UNOFFICIAL-SNAPSHOT-M11-v1awifixx.zip) and started CM11 successfully
Flashed gapps for CM11 (gapps-kk-20140606-signed.zip)
Decided that I want to have a gapps version without all those bloatware, so I did:
Wiped everything with TWRP except internal/external SDCard
Flashed CM11 with TWRP (cm-11-20141008-UNOFFICIAL-SNAPSHOT-M11-v1awifixx.zip)
Flashed gapps (pa_gapps-modular-pico-4.4.4-20141011-signed.zip) and started CM11 successfully
Worked some minutes with the tablet, rebooted the tablet and after that..
..the touchscreen stopped working.
@notspike
Kies knows the difference.. it even knows for which region the installed firmware is and installs the corresponding update.
Volans21 said:
@bonuzzz
No, I didn't find a three-part-firmware for my SM-P900.. maybe you missunderstood me: Years ago I flashed my Samsung Galaxy S2 (SGS2) with such a firmware.. I always thought, that the PIT file repartitioned my SGS2 and so the ROM was set to factory defaults. And thats why I was asking for a three-part-firmware with PIT file
I'm 100% sure that I have a SM-P900 (No LTE/4G, only Wifi). And thats what I did before the touchscreen stopped working:
A firmware update with Kies 3 to P900XXUANI1
Rooting with CF-AutoRoot (CF-Auto-Root-v1awifi-v1awifixx-smp900.zip)
Flashed TWRP 2.8.0.0 with Odin 3.07
Wiped everything with TWRP except internal/external SDCard
Flashed CM11 with TWRP (cm-11-20141008-UNOFFICIAL-SNAPSHOT-M11-v1awifixx.zip) and started CM11 successfully
Flashed gapps for CM11 (gapps-kk-20140606-signed.zip)
Decided that I want to have a gapps version without all those bloatware, so I did:
Wiped everything with TWRP except internal/external SDCard
Flashed CM11 with TWRP (cm-11-20141008-UNOFFICIAL-SNAPSHOT-M11-v1awifixx.zip)
Flashed gapps (pa_gapps-modular-pico-4.4.4-20141011-signed.zip) and started CM11 successfully
Worked some minutes with the tablet, rebooted the tablet and after that..
..the touchscreen stopped working.
@notspike
Kies knows the difference.. it even knows for which region the installed firmware is and installs the corresponding update.
Click to expand...
Click to collapse
@Volans21
I've been experimenting with Cyanogen on my sm-p900 for about a week & 1/2 flashing back & forth with stock roms as well. Learning from the thread that Cyanogen is very different from the other roms, I wiped EVERYTHING except external sdcard when flashing back & forth & have not had any issues. Have you disabled Kies before trying to install as it will cause issues when flashing custom roms as well. Try disabling kies & doing a wipe of everything except external sdcard & then reflash the rom. I'm just a newbie trying to help so I hope this helps.
I also noticed that you didn't mention doing a backup in TWRP before doing anything. It would definitely serve you well to do so in the future as you will always be able to go back to what was working.
What do you mean with "disable Kies"? I know Kies as the software for managing a Samsung device with a PC.. but I didn't know that I could disable it on the phone/tablet.
Of course I did a backup with TWRP, I just didn't list i because I thought doing a backup can not cause the touchscreen to not work. Maybe I should have said that I tried to fix the touchscreen by restoring the TWRP backup.. but it didn't help. :/
Volans21 said:
What do you mean with "disable Kies"? I know Kies as the software for managing a Samsung device with a PC.. but I didn't know that I could disable it on the phone/tablet.
Of course I did a backup with TWRP, I just didn't list i because I thought doing a backup can not cause the touchscreen to not work. Maybe I should have said that I tried to fix the touchscreen by restoring the TWRP backup.. but it didn't help. :/
Click to expand...
Click to collapse
That really is sounding more and more like a hardware issue the more I look at the steps you've tried. If even wiping all data/cache/dalvik and flashing from odin stock firmware isn't fixing it it could be. The fact in twrp it's acting that way too sort of supports this.
Yes, I think so, too.
Volans21 said:
Yes, I think so, too.
Click to expand...
Click to collapse
To close this case: I sent the device back to the distributor, it was a HW issue and fixed.. even after flashing a custom ROM.
Now I flashed CM11 again.. 2 days ago. Touchscreen is still working!
Ok was trying to install a ROM and got an error that there was no OS installed and now the phone wont boot up
I rooted it via Bacon root toolkit and I took a back up before I rooted but I cannot get it to reboot. The back up is saved on the PC and phone not getting picked up by PC
Anyone tried to restore android back up file and went to ab file on pc but it wont load. Can go into fastboot and recovery but not showing on PC
HELP
Delete duplicate post
This is why you shouldn't use toolkits, you have no access to fastboot and no idea how to fix it. What drivers are installed on your PC? I guess it doesn't matter, my advice is to completely delete anything that the toolkit installed and start fresh. Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
I have links to the Android SDK (which contains adb/fastboot) and the right drivers for this phone. Make sure you reboot your PC after deleting everything, then install the SDK and the drivers, reboot PC again, connect phone.
Transmitted via Bacon
timmaaa said:
This is why you shouldn't use toolkits, you have no access to fastboot and no idea how to fix it. What drivers are installed on your PC? I guess it doesn't matter, my advice is to completely delete anything that the toolkit installed and start fresh. Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
I have links to the Android SDK (which contains adb/fastboot) and the right drivers for this phone. Make sure you reboot your PC after deleting everything, then install the SDK and the drivers, reboot PC again, connect phone.
Transmitted via Bacon
Click to expand...
Click to collapse
Live and Learn and got back to the stock using adb/fastboot and installing images and back to normal again. I want to update to Lollilop and Sabermod but after trying may just stick with Stock for a while as I kept getting errors when trying to load the ROM??
Thanks
funkyirishman said:
Live and Learn and got back to the stock using adb/fastboot and installing images and back to normal again. I want to update to Lollilop and Sabermod but after trying may just stick with Stock for a while as I kept getting errors when trying to load the ROM??
Thanks
Click to expand...
Click to collapse
Exactly what error are you getting when trying to flash? Are you checking the md5 when you download? What recovery are you using?
Transmitted via Bacon
timmaaa said:
Exactly what error are you getting when trying to flash? Are you checking the md5 when you download? What recovery are you using?
Transmitted via Bacon
Click to expand...
Click to collapse
When I tried to flash initially I got the below
Went into recovery and did Factory reset and then wipe cache partition. Then tried Apply update and scrolled to the ROM file and apply update and I get the below error
Install Failed
Finding Update Package
Opening Update Package
Verifying Update Package
E: Failed to verify whole-file signature
E:signature verification failed
Installation aborted
I have the files saved in the download folder.
Then when I tried to install with TWRP rather than update I clear cache, dalvik and system and tried to load and got the below error
Checking for MD5 File
Skipping MD5 Chekck: no MD5 file found
Comparing TZ Verionsioj TZ. BF.2.0-2.0.0109 to TZ
BF 2.0-2.0.0096
assert failed oppo verify trustzone
I got the message that no os installed and I could not reboot so I flashed it back to stock using the below
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Phone now rooted and unlocked and like to update but afraid I will just experience it all over again:crying:
Any help appreciated
Thanks
funkyirishman said:
When I tried to flash initially I got the below
Went into recovery and did Factory reset and then wipe cache partition. Then tried Apply update and scrolled to the ROM file and apply update and I get the below error
Install Failed
Finding Update Package
Opening Update Package
Verifying Update Package
E: Failed to verify whole-file signature
E:signature verification failed
Installation aborted
Click to expand...
Click to collapse
Ok, you got this error because you're trying to flash a custom ROM with the stock recovery. The stock recovery can only flash zips signed by CM (official updates)
funkyirishman said:
Then when I tried to install with TWRP rather than update I clear cache, dalvik and system and tried to load and got the below error
Checking for MD5 File
Skipping MD5 Chekck: no MD5 file found
Comparing TZ Verionsioj TZ. BF.2.0-2.0.0109 to TZ
BF 2.0-2.0.0096
assert failed oppo verify trustzone
I got the message that no os installed and I could not reboot so I flashed it back to stock using the below
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Phone now rooted and unlocked and like to update but afraid I will just experience it all over again:crying:
Any help appreciated
Thanks
Click to expand...
Click to collapse
Your problem here is that you're trying to install a ROM but you don't have the correct firmware installed. When flashing a Lollipop ROM for the first time you need to first flash Lollipop firmware and Lollipop modem. Once you've flashed those they're always there so you don't need to do it again. The only reason you'd need to flash firmware and modem again would be if you wanted to return to a KitKat ROM, and then it'd be KitKat firmware and modem that you'd need to flash. Anyway, you'll find the modems here:
http://boeffla.df-kunde.de/bacon/modems
And I mirror the firmwares here:
https://drive.google.com/folder/d/0B98G0KTJwnBFRGhZeUNpMEI4ajg/edit
PS. I also noticed you weren't wiping properly before attempting to install the ROM. When flashing a ROM you need to perform a full wipe, this includes system, data, cache, and dalvik cache. This didn't cause the problem you experienced, but had the install succeeded you would have had other problems.
It might benefit you to read the OnePlus One FAQ thread:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
And my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
timmaaa said:
Ok, you got this error because you're trying to flash a custom ROM with the stock recovery. The stock recovery can only flash zips signed by CM (official updates)
Your problem here is that you're trying to install a ROM but you don't have the correct firmware installed. When flashing a Lollipop ROM for the first time you need to first flash Lollipop firmware and Lollipop modem. Once you've flashed those they're always there so you don't need to do it again. The only reason you'd need to flash firmware and modem again would be if you wanted to return to a KitKat ROM, and then it'd be KitKat firmware and modem that you'd need to flash. Anyway, you'll find the modems here:
http://boeffla.df-kunde.de/bacon/modems
And I mirror the firmwares here:
https://drive.google.com/folder/d/0B98G0KTJwnBFRGhZeUNpMEI4ajg/edit
PS. I also noticed you weren't wiping properly before attempting to install the ROM. When flashing a ROM you need to perform a full wipe, this includes system, data, cache, and dalvik cache. This didn't cause the problem you experienced, but had the install succeeded you would have had other problems.
It might benefit you to read the OnePlus One FAQ thread:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
And my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Click to expand...
Click to collapse
Cheers thanks for that. I thought the ROM updated the firmware and modems so that's a lesson learned
So I download the modem and firmware and copy these into the download folder on the phone and install via TWRP recovery correct? Modem first then firmware? This will then put lollipop on the phone correct?
Then if I want to install a new ROM I need to do a full wipe. I just did not see that option and was just following the video tutorial associated with the Sabermod thread by wiping cache system and dalvik
Read your thread and will be doing a full nandroid & EFS back up prior to do any of the above
Thanks again
funkyirishman said:
Cheers thanks for that. I thought the ROM updated the firmware and modems so that's a lesson learned
Click to expand...
Click to collapse
CM12 does do that, but no other ROMs do.
funkyirishman said:
So I download the modem and firmware and copy these into the download folder on the phone and install via TWRP recovery correct? Modem first then firmware? This will then put lollipop on the phone correct?
Click to expand...
Click to collapse
Yes, install via TWRP recovery. It doesn't matter which order you flash them in. So install both, then go to the reboot menu, and select to reboot back to the recovery. This doesn't install Lollipop as such, this installs Lollipop compatible firmware.
funkyirishman said:
Then if I want to install a new ROM I need to do a full wipe. I just did not see that option and was just following the video tutorial associated with the Sabermod thread by wiping cache system and dalvik
Click to expand...
Click to collapse
Go to the wipe menu in TWRP, then select advanced wipe, from there you can choose which partitions you want to wipe (system, data, cache, dalvik cache), just don't wipe internal storage (that's your virtual sd card).
funkyirishman said:
Read your thread and will be doing a full nandroid & EFS back up prior to do any of the above
Thanks again
Click to expand...
Click to collapse
Very good, that's super important. It doesn't happen often, but sometimes the EFS partition will just randomly become corrupt, if you don't have a backup in that situation your phone is useless (you can't use someone else's EFS backup because it contains unique device identifiers).
Transmitted via Bacon
timmaaa said:
CM12 does do that, but no other ROMs do.
Yes, install via TWRP recovery. It doesn't matter which order you flash them in. So install both, then go to the reboot menu, and select to reboot back to the recovery. This doesn't install Lollipop as such, this installs Lollipop compatible firmware.
Go to the wipe menu in TWRP, then select advanced wipe, from there you can choose which partitions you want to wipe (system, data, cache, dalvik cache), just don't wipe internal storage (that's your virtual sd card).
Very good, that's super important. It doesn't happen often, but sometimes the EFS partition will just randomly become corrupt, if you don't have a backup in that situation your phone is useless (you can't use someone else's EFS backup because it contains unique device identifiers).
Transmitted via Bacon
Click to expand...
Click to collapse
Reading about back ups etc on the below when creating a recovery
-Make sure you check the md5 to verify its integrity.
How and what do you check?
Also I first do the back up. Then install the firmware and modems and then update the ROM.
I dont need to flash the stock kernal or fastboot images, correct?
Also doing a back up does it back it up to an internal SD Card or should I keep it on PC
Cheers
funkyirishman said:
Reading about back ups etc on the below when creating a recovery
-Make sure you check the md5 to verify its integrity.
How and what do you check?
Also I first do the back up. Then install the firmware and modems and then update the ROM.
I dont need to flash the stock kernal or fastboot images, correct?
Also doing a back up does it back it up to an internal SD Card or should I keep it on PC
Cheers
Click to expand...
Click to collapse
The download page for a ROM or kernel usually lists the md5 checksum for that particular file. An md5 is like a digital fingerprint of the file, so once you've downloaded it you use an md5 checking app/program to confirm that the md5 of the downloaded file matches the md5 listed on the download page. This confirms that the file hasn't become corrupt during the download, if even a single byte of information is corrupt in a file the md5 will be drastically different.
You don't need to flash the stock kernel or stock images, the numbered parts in my guide aren't steps, they're sections.
When you create your nandroid backup using TWRP it will automatically be saved to your internal storage. You should keep at least one backup on your phone at all times, think of it as an insurance policy just in case something goes wrong, you'l always have a known working OS there to save you. You should also copy it to your PC for safe keeping.
timmaaa said:
The download page for a ROM or kernel usually lists the md5 checksum for that particular file. An md5 is like a digital fingerprint of the file, so once you've downloaded it you use an md5 checking app/program to confirm that the md5 of the downloaded file matches the md5 listed on the download page. This confirms that the file hasn't become corrupt during the download, if even a single byte of information is corrupt in a file the md5 will be drastically different.
You don't need to flash the stock kernel or stock images, the numbered parts in my guide aren't steps, they're sections.
When you create your nandroid backup using TWRP it will automatically be saved to your internal storage. You should keep at least one backup on your phone at all times, think of it as an insurance policy just in case something goes wrong, you'l always have a known working OS there to save you. You should also copy it to your PC for safe keeping.
Click to expand...
Click to collapse
Perfect I will google an md5 checking app/program so for the Sabermod I need to check on the download page on their link below
http://forum.xda-developers.com/oneplus-one/development/rom-kernel-sabermod-cm-11-0-t2880407
Just checked their download link is not working but I downloaded the ROM to my PC previously and its in zip format can you check the MD5 v this?
Thanks
funkyirishman said:
Perfect I will google an md5 checking app/program so for the Sabermod I need to check on the download page on their link below
http://forum.xda-developers.com/oneplus-one/development/rom-kernel-sabermod-cm-11-0-t2880407
Just checked their download link is not working but I downloaded the ROM to my PC previously and its in zip format can you check the MD5 v this?
Thanks
Click to expand...
Click to collapse
You have nothing to check it against though.
Transmitted via Bacon
timmaaa said:
You have nothing to check it against though.
Transmitted via Bacon
Click to expand...
Click to collapse
Ok so the ROM I downloaded is called cm-12-20150324-ROBBIEL811-UBER4.8-bacon and is in zip format and the download link on the developers page is dead so I cannot check the md5 file?
Thanks
funkyirishman said:
Ok so the ROM I downloaded is called cm-12-20150324-ROBBIEL811-UBER4.8-bacon and is in zip format and the download link on the developers page is dead so I cannot check the md5 file?
Thanks
Click to expand...
Click to collapse
Well yeah, if you can't reach the download page there's no way to see what the md5 is. Not all download pages have it anyway, they should, but not all do.
Transmitted via Bacon
Please i will like to know how i can do a Clean Wiped and install a fresh STOCK ROM on my Samsung galaxy s5, should i make use of the Nand Erase All option in Odin or not, thanks.
You could flash a custom recovery on your device, such as TWRP, and from there go to the wipe button, swipe the bar at the bottom and then install the fresh stock rom
casharena said:
Please i will like to know how i can do a Clean Wiped and install a fresh STOCK ROM on my Samsung galaxy s5, should i make use of the Nand Erase All option in Odin or not, thanks.
Click to expand...
Click to collapse
Go to Sammobile .com or samsung-updates .com and use your model number to find your stock firmware for your region/country then flash it with the newest version of Odin with default settings, just place the firmware file in AP slot, leave the options alone and click start, wait for it to flash and reboot.
If it bootloops, pull the battery and put it back in then boot to stock recovery and factory reset/wipe data and wipe cache and reboot, you should be fully clean on a fresh stock ROM.
Sent from my SCH-I535 using Tapatalk
I did everything,but still boot looping
what do I do
<I am using a Samsung galaxy j5 SM-G900K>
please help me out