Related
hey guys, just found this guide to update to jb
Code:
Update Galaxy Note N7000 to official Android 4.1.2 Jelly Bean XXLSA leak
As you know the official Android 4.1.2 OTA Update for the Galaxy Note has been leaked, but apparently the release date for the same will take place only in 2013, or if we are lucky enough, maybe somewhere during next month. Now, if you don’t want to wait that long and if you want to test the Android 4.1.2 flavor on your own Samsung Galaxy Note N700, this step by step guide is all you need. During the next few lines I will be showing you how to manually install the XXLSA leaked software on your Note, so let’s get started.
This leaked ROM is still in the test stage, but according to our sources (check the link from here for more details) it seems that the Android 4.1.2 firmware is working perfectly and there are no bugs in the system. So, the update is a stable one meaning that you have no reasons for waiting for the official release date of the OTA update. You will be able to easily flash the same on your Galaxy Note by following and applying this manual method that will take you and guide you through the installation procedure. In order to make a proper idea related to the Jelly Bean OS for the Note N7000, here are some of the features which will be added to your phablet:
Android 4.1.2 Features for Galaxy Note
This is an official software meaning that it is coming straight from Samsung (even though we are still talking about the leaked Android 4.1.2 Jelly Bean ROM) so by updating the same on your galaxy Note you will not void your phone’s warranty. Furthermore, you don’t need to have a rooted device for being able to flash this firmware and also the root access (if it was previously gained) will now be revoked and the bootloader relocked. Therefore, once you install the jelly Bean OS on your Note you will be able to restore the warranty, this if your handset is currently running a custom ROM firmware.
A backup though is still recommended because this is being considered a risky operation. Remember that you will manually flash the official software (which normally will OTA be received) on your Galaxy Note. So, take your time and make sure that all of your personal data is in safe hands. Then, you can safely go and perform the proper steps from below. If you don’t know how to complete a full backup then use our suitable guides (search through our how to section for the same) for learning how to save the contacts, messages, call logs, EFS and lot more.
Samsung Galaxy Note N7000
Update Samsung
Update Samsung Galaxy Note N7000
As this tutorial explains a manual procedure, a Windows running computer will be required along with your device and its USB cord. On your Note enable the USB debugging option before doing anything else. Then, on both phablet and PC deactivate or uninstall the security tools or programs like antivirus and Firewall protection. The Note must have enough battery life for being able to stay alive during the update operation; therefore if there is less than 60% power left take the battery and charge it. This guide should be applied only for installing the Samsung Galaxy Note N7000 with the leaked Android 4.1.2 Jelly Bean firmware because the software won’t work on a differed device and worst you can even end up in bricking your smartphone or tablet.
Code:
How to Update Galaxy Note with Official Android 4.1.2 Jelly Bean Leaked XXLSA Firmware
Download the update file from here.
Extract the file on your computer.
Then, download Odin.
Extract and install Odin on your computer.
Turn off the Galaxy Note.
Put your phablet in download mode.
The download mode can be reached by pressing and holding the Volume Down, Home and Power buttons at the same time for a few seconds.
Now, on your computer open Odin.
On Odin, click on PDA and select the “CODE_N7000XXLSA_549786_REV02_user_low_ship.tar” file.
Next, also from Odin select Phone and pick the “MODEM_N7000XXLSA_REV_05_CL1222228.tar” file.
Finally, select CSC and pick the “CSC_OXA_N7000OXALSA_549786_REV02_user_low_ship.tar” file.
Make sure that the Re-partition option is not checked and don’t make any other changes on Odin.
Connect the device (must be in download mode) with the PC by using its USB cable.
Once the handset is connected on Odin the “added” messages should be displayed and the ID:COM section should be yellow.
If different install the drivers on your computer and re-do the above mentioned steps.
On Odin, click on “Start”.
Wait until the process ends.
In the end, the phablet will reboot by itself.
Also, on Odin the “pass” message will be displayed.
If you get a boot loop then complete the following:
Reboot the Galaxy Note in recovery mode: press and hold the Volume Up, Home and Power buttons at the same time and this time choose recovery.
Then, from the recovery menu select “wipe data factory reset” and “wipe cache partition”. All the data will be wiped out so remember to backup the data first.
Select “+++go back+++” and “reboot system now” and you are done.
So, that was all for now. Your Samsung Galaxy Note N7000 has been successfully updated with the official Android 4.1.2 Jelly Bean software. Remember that the OTA update will be made available later this year or in January 2013, this being the leaked firmware. Do tell how things worked for you by using the comments area from below.
my question,is can i revert back to ics, Stock, and if i stay with this jb, can i update to the "released version"?
Thanks, Amatris.
This is a leaked version and you cannot upgrade when the official version comes out. you can revert back to stock ICS the same way as you install this. using PC odin and selecting the ICS file in the PDA section.
Donot wipe on stock ICS kernels
Thanks for the fast Response, Im sorry if im sounding like a noob at the moment, but i have had many problems with past phones and installing updates/Roms, yeah i got the roms to work but not all of them worked properly, Would i have to update the kernels too?, all i want is to have my note as Stock as it can get with Jb, "intill release" then Revert back to Stock ics and Stock isc kernel, to Re update when it is... released.
iv had a look around Xda, but i dont want to install all of the "faster kernal's" etc, i mean as long as i can get my note back to stock Everything for the Released version i will be happy, could you link me to a guild of what im looking for?,
so a run down....
i want Samsung Jb
and i want to be able to revert back to when i got the phone, if anything goes wrong. for example could i make a whole System back up kernel inc, and revert back at a later date?
Edit:
Could i use this
http://forum.xda-developers.com/showthread.php?t=1329360
and update to samsung jb,
then when Official jb is released, download the official ICS Rom, Install, then update Via the Settings/about phone. Update?
Thanks, Amatris.
What rom are you on now ?
nokiamodeln91 said:
What rom are you on now ?
Click to expand...
Click to collapse
Stock ICS 4,0,4 and stock Kernals.
thanks, Amatris.
Any how.. you could root your device and install a custom kernel to get CWM. using CWMs backup feature, you can backup the entire rom ... This backup will include all you apps and data. so when you restore this, it will be just like when you did the backup. This backup includes a custom kernel as stock kernel is not safe and stock recovery doesnot have this feature
You can go to samfirmware.com and download the XXLSA rom and install it using Odin. its all stock.. and there is a later version available here http://forum.xda-developers.com/showthread.php?t=1992573
flashing roms using PC odin is safe, as this is stock, you cannot restore the old rom. for this you will need CWM again. so you can install Philz kernel for XXLSA or LSC which ee\ver you chose and flash it. this will give you cwm. now using this you can revert back to your old rom as well
nokiamodeln91 said:
Any how.. you could root your device and install a custom kernel to get CWM. using CWMs backup feature, you can backup the entire rom ... This backup will include all you apps and data. so when you restore this, it will be just like when you did the backup. This backup includes a custom kernel as stock kernel is not safe and stock recovery doesnot have this feature
You can go to samfirmware.com and download the XXLSA rom and install it using Odin. its all stock.. and there is a later version available here http://forum.xda-developers.com/showthread.php?t=1992573
flashing roms using PC odin is safe, as this is stock, you cannot restore the old rom. for this you will need CWM again. so you can install Philz kernel for XXLSA or LSC which ee\ver you chose and flash it. this will give you cwm. now using this you can revert back to your old rom as well
Click to expand...
Click to collapse
ok cool thanks, so if i did this. could i revertback to my old rom " you said i could via back up" and update it to the official jb when it comes out, Via the Settings, about phone, update??
thanks. Amatris.
The official JB might not be available via OTA (what you mentioned). Atleast thats what i read, It can only be done using Kies. so if you revert back to the Old rom then you can update via kies when JB comes.
Yes you can revert back. CWM has a backup and restore reature. It needs CWM
nokiamodeln91 said:
Any how.. you could root your device and install a custom kernel to get CWM. using CWMs backup feature, you can backup the entire rom ... This backup will include all you apps and data. so when you restore this, it will be just like when you did the backup. This backup includes a custom kernel as stock kernel is not safe and stock recovery doesnot have this feature
You can go to samfirmware.com and download the XXLSA rom and install it using Odin. its all stock.. and there is a later version available here http://forum.xda-developers.com/showthread.php?t=1992573
flashing roms using PC odin is safe, as this is stock, you cannot restore the old rom. for this you will need CWM again. so you can install Philz kernel for XXLSA or LSC which ee\ver you chose and flash it. this will give you cwm. now using this you can revert back to your old rom as well
Click to expand...
Click to collapse
nokiamodeln91 said:
The official JB might not be available via OTA (what you mentioned). Atleast thats what i read, It can only be done using Kies. so if you revert back to the Old rom then you can update via kies when JB comes.
Yes you can revert back. CWM has a backup and restore reature. It needs CWM
Click to expand...
Click to collapse
ok thank you. i need to root/install the custom Kernel from http://forum.xda-developers.com/showthread.php?t=1992573 ?
it looks like it comes with CWM and kernal, Correct me if im wrong?
Edit:
(Edit 2:
or do i use this kernal/root
http://forum.xda-developers.com/showthread.php?t=1901191 )
then update to this rom
http://forum.xda-developers.com/showthread.php?t=1992573
Thanks amatris.
To root your current rom .. check the rom build number in settings > about phone
head over to this http://forum.xda-developers.com/showthread.php?t=1901191 and download the kernel (zip) that matches you rom. Put the zip file on ext SD .. boot into recovery and apply update from ext storage. once done.. reboot
this will root you phone. and CWM. now boot into recovery again and take a backup
Yes "[ROM][STOCK][JB][4.1.2][JZO54k.N7000XXLSC]" that you mentioned comes prerooted and with CWM installed.
nokiamodeln91 said:
To root your current rom .. check the rom build number in settings > about phone
head over to this http://forum.xda-developers.com/showthread.php?t=1901191 and download the kernel (zip) that matches you rom. Put the zip file on ext SD .. boot into recovery and apply update from ext storage. once done.. reboot
this will root you phone. and CWM. now boot into recovery again and take a backup
Yes "[ROM][STOCK][JB][4.1.2][JZO54k.N7000XXLSC]" that you mentioned comes prerooted and with CWM installed.
Click to expand...
Click to collapse
Sorry for all of this, and i do Thanks you alot for being patient with me, can i install the Kernel with the Stock Recovery?
thank you for helping me this much,
Amatris
Yes the zip version of the kernel can be installed through stock recovery
nokiamodeln91 said:
Yes the zip version of the kernel can be installed through stock recovery
Click to expand...
Click to collapse
ok so i put it in ext sd. Reboot into recovery, and tried to install/update it, and it says E:signature verfication failed.
i tired. "PhilZ-cwm6-XXLRK-XEU-2.7-signed"
thanks, amatris.
Edit: think iv now done it thanks for all of yourr help! your a star!
Amatris
sorry one more thing can i install the XXLSA rom as you had said before hand, even though my kernel version is XXLRK?
Thanks, amatris
Yes .. any rom you want as you have philz now.
If you choose custom XXLSA. then flash using CWM recovery..follow instructions from the rom thread.. it will replace the kernel with what is included in the new rom.
if you choose odin flashable, then flash as any stock.. this will also flash the new kernel which is included in the rom
I tried every thing but still odin wont read my phone in downloading mode. Plzzz advice.
Sent from my GT-N7000 using xda app-developers app
You mean to say the phone is going into download mode but pc can see it? Install lies first. It will install requires drivers. Then try again.
I am saying this as you have not mentioned what all you have tried.
Hi,
I'm currently running stock 4.3 (12.1.A.0.266). My phone is ROOTED, but have LOCKED BOOTLOADER. I have
My question is simple: will I lose root? Or any apps/data/sms/etc for that matter?
I just don't want to do all the stuff all over again. 12.1.A.0.266 is buggy but still is tolerable. >.>
wakoko79 said:
Hi,
I'm currently running stock 4.3 (12.1.A.0.266). My phone is ROOTED, but have LOCKED BOOTLOADER. I have
My question is simple: will I lose root? Or any apps/data/sms/etc for that matter?
I just don't want to do all the stuff all over again. 12.1.A.0.266 is buggy but still is tolerable. >.>
Click to expand...
Click to collapse
Yes, you'll lose root if you update via OTA or flashing stock.
However, I think OTA does not wipe data, so you'll probably have your data. Do back them up just in case (can't remember since it's been a while since I last update via OTA ).
If you want rooted .201, install either of these roms:
http://forum.xda-developers.com/showthread.php?t=2704312
(v1.1 looks and works like 201)
http://forum.xda-developers.com/showthread.php?t=2658043
(v2 is a much "improved" version of the above)
I have installed the first one and loved it.
A few days ago I installed the second one and loved it even more.
Whatever you do, do a nandroid backup of your .266 (and preferably, add titanium backup of your apps and data/sms/contacts)
my mobile vibrating only after reboot!!!!!
My mobile was a rooted onewith .266 verson and i was trying to put the new rom and screwup!! ias you told i installe i downloaded the new rom v2 and super user,and dual recovery files... i ectracted from sd card all as you tol one by one ...while reboot...i saw sony logo and vibrating freequently only...not opening....!!!!!!!!!!! i tried to reset..same thing.....screwed up?!!!!!
headache59 said:
Yes, you'll lose root if you update via OTA or flashing stock.
However, I think OTA does not wipe data, so you'll probably have your data. Do back them up just in case (can't remember since it's been a while since I last update via OTA ).
If you want rooted .201, install either of these roms:
http://forum.xda-developers.com/showthread.php?t=2704312
(v1.1 looks and works like 201)
http://forum.xda-developers.com/showthread.php?t=2658043
(v2 is a much "improved" version of the above)
I have installed the first one and loved it.
A few days ago I installed the second one and loved it even more.
Whatever you do, do a nandroid backup of your .266 (and preferably, add titanium backup of your apps and data/sms/contacts)
Click to expand...
Click to collapse
Yup - screwed up somewhere in the process but no worries.
The process is almost the same way you got your .266 root.
To get new root and recoveries:
a. Flashtool - choose .257, then follow prompt to hook in your usb cable while pressing the Vol-down button
b. Once complete, close flashtool, unplug your device and reboot device
c. Once loaded and past the minor set up, turn on usb debugging and check "unknown sources" (all under settings)
d. Assuming you have all adb drivers installed (through flashtool installation), hook up your device to the PC and install Doomlord's exploit V18 and recoveries
Install new root 201
Boot into recoveries and flash the said .201 rom+SU+recovery (all zip files) using TWRP. Make sure you wipe cache/dalvik cache/data first. After flashing the zip files, select reboot from TWRP, and let the phone run a bit as it sets itself up (android and sony) during the booting process.
Note:
Ultimate purexsp V2.1 zip is simply an update file (not the full rom) - don't flash this one yet.
Somewhere within the thread you'll find the V2 full rom <663MB in size (as seen in my ext SD card). Flash this one and ignore the other versions
Edit:
Here it is:http://forum.xda-developers.com/showpost.php?p=51733368&postcount=423
stucked on SONY cant open...!!!
Again >> i tried to flash with XperiaSP_C530X_12.0.A.1.257_KernelOnly.ftf file but same thing..after flashing when iam switching on..its stuck on the SONY.... not moving foeward.!!!!!!! give me solution...if its open i can do somthing...
one more can i flash directly with your v2?V2 full rom <663MB or i will flash first with v1 then v2? plz clerify..
headache59 said:
Yup - screwed up somewhere in the process but no worries.
The process is almost the same way you got your .266 root.
To get new root and recoveries:
a. Flashtool - choose .257, then follow prompt to hook in your usb cable while pressing the Vol-down button
b. Once complete, close flashtool, unplug your device and reboot device
c. Once loaded and past the minor set up, turn on usb debugging and check "unknown sources" (all under settings)
d. Assuming you have all adb drivers installed (through flashtool installation), hook up your device to the PC and install Doomlord's exploit V18 and recoveries
Install new root 201
Boot into recoveries and flash the said .201 rom+SU+recovery (all zip files) using TWRP. Make sure you wipe cache/dalvik cache/data first. After flashing the zip files, select reboot from TWRP, and let the phone run a bit as it sets itself up (android and sony) during the booting process.
Note:
Ultimate purexsp V2.1 zip is simply an update file (not the full rom) - don't flash this one yet.
Somewhere within the thread you'll find the V2 full rom <663MB in size (as seen in my ext SD card). Flash this one and ignore the other versions
Edit:
Here it is:http://forum.xda-developers.com/showpost.php?p=51733368&postcount=423
Click to expand...
Click to collapse
Thanks!!! done
Finally its done..!!!!!! i dont know wht i did..finally everythings allright..!!!:victory::victory::victory::victory::victory::victory::highfive::highfive::highfive:
babugd said:
Again >> i tried to flash with XperiaSP_C530X_12.0.A.1.257_KernelOnly.ftf file but same thing..after flashing when iam switching on..its stuck on the SONY.... not moving foeward.!!!!!!! give me solution...if its open i can do somthing...
one more can i flash directly with your v2?V2 full rom <663MB or i will flash first with v1 then v2? plz clerify..
Click to expand...
Click to collapse
Congratz and enjoy the new fantastic rooted rom!
FlashFire - Play BETA - PREVIEW
1. Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
2. Sign up to receive the BETA versions from Play Here.
- Use the link provided after sign-up to download the app
With the amazing work by @Chainfire we are blessed with a what seems to be almost perfect replacement for SafeStrap. Yes, this is still in Beta and you should go into this expecting to soft brick your phone every time when flashing something with this. That's why we need some brave souls to test the limits of FlashFire for our poor device.
If you would like to help contribute to see what we can flash with this application here are a couple tutorials on flashing by @muniz_ri
http://forum.xda-developers.com/att...w-to-update-to-g900aoca-5-0-keeproot-t3076803
http://forum.xda-developers.com/att...-to-enable-native-tethering-g900aoc4-t3078561
If you come across anything that you can flash from the smallest things or even ROMs that you have found compatible please share the knowledge here and I will try to put it in an index that others can see through this beta testing and early phase of Android Lollipop for the G900A.
ROMs that have been confirmed to be flashed and working:
G900A_OC4 5.0 Stock Rooted Android Lollipop by @muniz_ri
Miscellaneous things that have been confirmed to be flashed and working:
Native Tethering by @muniz_ri
300 Fonts for Lollipop and KitKat by @nitol
Titanium Backup's update.zip file
Remote Play Installer
Notes:
If your device stays at the black screen when you try to flash something simply pull the battery out. Then, boot into recovery and wipe the cache partitions. That should allow you to boot your device again after failure.
If you find yourself in a boot loop and downgrading back to NCE you can restore your 5.0 backup while on 4.4.2 (if you made one like you should have) by following my tutorial in the following link. http://forum.xda-developers.com/showpost.php?p=60095108&postcount=21
Here is what I know so far about FlashFire's capabilities on locked bootloader devices:
- Will run on Android v4.x.x/5.0.x.
- Will not trip your Knox Warranty Flag.
- Will flash ROM's (use "flash .zip or ota" option).
- No AROMA installer ROM's.
- Caution! FF flashes to the boot partition, i.e. flashing custom kernels will result in soft brick!
- You can drop a Full Odin .tar or .zip file containing the raw images onto your device and it will flash system, kernel, cache, and recovery (will not flash modem, non-hlos, or bootloader) (use "flash firmware package" option).
- You can flash the remaining partitions via a .zip at the same time or via your PC using Odin.
- Flashes .tars with unsigned images, e.g. system.img.ext4, modem.bin. (use "flash firmware package" option).
- You can also flash individual (un-.tar'd) images, e.g. recovery.img, boot.img.
- Flashes .zip files, e.g. mod's, SuperSu Update.zips, etc (use "flash .zip or ota" option).
- Makes Backups of and Restores all partitions.
- Wipes partitions.
- Injects Root.
I will add here as I test and learn more.
Also want to add a note of caution....if you are a noob and don't have much experience with these things don't rush in. Best to sit back until safe and responsible guides are created. I for one am not at all sympathetic to those that don't take the time to read and understand before jumping in.
muniz_ri said:
Here is what I know so far about FF:
- Will run on Android v4.x.x/5.0.x
- No AROMA installer ROM's.
- Caution! FF flashes to the boot partition, i.e. flashing custom kernels will result in soft brick!
- Flashes stock or modified images, e.g. system.img.ext4, modem.bin, non-hlos.bin.
- Flashes .zip files, e.g. mod's, SuperSu Update.zips, etc
- Makes Backups of and Restores all partitions.
- Injects Root
I will add here as I learn more.
Click to expand...
Click to collapse
One of my questions about FlashFire is will it work on encrypted phones? My work phone is Verizon GS5 and SafeStrap would not work because of my encryption, so I'd be very interested in updating that phone without losing root if it will work. Thanks for all your work!
I attempted to flash Alliance ROM 7.1 from the International Forums.
My Steps:
1. Downgrade to NCE
2. Root
3. SuperSU
4. Install FlashFire
5. Set up FlashFire in the following order;
- Wipe
- Flash Partitions and Bootloader
- Flash Alliance ROM
Everything looked to be working perfectly, but it was getting stuck on the second boot screen. Going to try it again, but after I finish installing Stock Rooted 5.0 again. Maybe it will work then. Only one way to figure out.
Great thread. I'll have a deodexed build up in the next few days then start adding mods and working on other things
Nyxerosoir said:
I attempted to flash Alliance ROM 7.1 from the International Forums.
My Steps:
1. Downgrade to NCE
2. Root
3. SuperSU
4. Install FlashFire
5. Set up FlashFire in the following order;
- Wipe
- Flash Partitions and Bootloader
- Flash Alliance ROM
Everything looked to be working perfectly, but it was getting stuck on the second boot screen. Going to try it again, but after I finish installing Stock Rooted 5.0 again. Maybe it will work then. Only one way to figure out.
Click to expand...
Click to collapse
I'm downloading Alliance as well. Let me know how your flash goes. If love to get a Rom going on lollipop.
dirtydodge said:
I'm downloading Alliance as well. Let me know how your flash goes. If love to get a Rom going on lollipop.
Click to expand...
Click to collapse
Should I try flashing the ROM as a Firmware package this time or a Zip/OTA?
Nyxerosoir said:
Should I try flashing the ROM as a Firmware package this time or a Zip/OTA?
Click to expand...
Click to collapse
Not sure. I'd think as a zip. I'm trying to learn FF.
dirtydodge said:
Not sure. I'd think as a zip. I'm trying to learn FF.
Click to expand...
Click to collapse
Going to try as a firmware package
When I tried to flash as a zip in FlashFire all it did was wipe my device then once it tried to insall the ROM it stopped then rebooted.
Nyxerosoir said:
Going to try as a firmware package
When I tried to flash as a zip in FlashFire all it did was wipe my device then once it tried to insall the ROM it stopped then rebooted.
Click to expand...
Click to collapse
I'm sounds good. I'm backing up with Kies right now.
dirtydodge said:
I'm sounds good. I'm backing up with Kies right now.
Click to expand...
Click to collapse
Just updated the 2nd post. It should provide some guidance.
muniz_ri said:
Just updated the 2nd post. It should provide some guidance.
Click to expand...
Click to collapse
Tried to flash Allience in zip/ota and after it wipes it says that it is installing the .zip file for a second then it stops and reboots. Could this be a bug from FlashFire or the ROM not compatible?
Maybe try a dirty flash of the ROM?
I grab a stock ROM directly from G900F, make G900A boot.img and system.img.ext4 into tar.md5. Flash as package in FireFlash along with G900A_OC4_Stock_Partitions_wOA1_BL.zip. Works out pretty well. Just need to disable KNOX with Titanium Backup (for some reason SuperSU doesn't detect KNOX being present) and use Root Explorer to get csc through.
However haven't figured out how to enable VoLTE yet.
Nyxerosoir said:
Tried to flash Allience in zip/ota and after it wipes it says that it is installing the .zip file for a second then it stops and reboots. Could this be a bug from FlashFire or the ROM not compatible?
Maybe try a dirty flash of the ROM?
Click to expand...
Click to collapse
I tried the dirty flash. Just stuck at black screen. I let it sit for 25 min then did a battery pull. Rom did not install. I'll leave it alone tonight before i have to stay up all night fixing a soft brick. Haha.
82801BA said:
I grab a stock ROM directly from G900F, make G900A boot.img and system.img.ext4 into tar.md5. Flash as package in FireFlash along with G900A_OC4_Stock_Partitions_wOA1_BL.zip. Works out pretty well. Just need to disable KNOX with Titanium Backup (for some reason SuperSU doesn't detect KNOX being present) and use Root Explorer to get csc through.
However haven't figured out how to enable VoLTE yet.
Click to expand...
Click to collapse
That is some very useful information. Can't wait to give it a go tomorrow! Time for some rest.
Do you have SQLite Editor? Maybe VoLTE can be implemented though it.
Nyxerosoir said:
That is some very useful information. Can't wait to give it a go tomorrow! Time for some rest.
Do you have SQLite Editor? Maybe VoLTE can be implemented though it.
Click to expand...
Click to collapse
@Nyxerosoir It's not that the option that is not there. It is just I am not able to enable it (grayed out) or it says "VoLTE is not supported by your current software version. Contact customer service for more details." if I try to enable it on quick settings.
Nyxerosoir said:
Tried to flash Allience in zip/ota and after it wipes it says that it is installing the .zip file for a second then it stops and reboots. Could this be a bug from FlashFire or the ROM not compatible?
Maybe try a dirty flash of the ROM?
Click to expand...
Click to collapse
A general principle to keep in mind is when flashing ROM's at the very least the kernel needs to match the system, i.e. 5.0 system requires the G900A Stock 5.0 kernel, 4.x system requires the G900A Stock 4.x kernel. The matching G900A Stock non-hlos will likely also be required in order for the ROM to work correctly.
I finally managed to get the font package by @nitol to work. The first time I ended up with a bootloop, but then I tried wiping dalvik and cache and flashing. Worked like a charm! Updated it in the OP for the index.
Can i upgrade from custom 4.4.2 to stock 5.0 via flashfire without needing a pc odin to flash bootloader and modem ? (I have G900F so unlocked bootloader)
waleed794 said:
Can i upgrade from custom 4.4.2 to stock 5.0 via flashfire without needing a pc odin to flash bootloader and modem ? (I have G900F so unlocked bootloader)
Click to expand...
Click to collapse
Yes, follow @muniz_ri's guide and you can successfully upgrade from 4.4.2 to 5.0 without a PC.
http://forum.xda-developers.com/att...w-to-update-to-g900aoca-5-0-keeproot-t3076803
Hello guardians of the Android Phones. I ran into a major issue while updating from 5.1.1 custom ROM to 6.0.1 that I found on this thread : http://forum.xda-developers.com/tmo...20t-android-6-0-1-marshmallow-update-t3356838
Steps I took:
1) Upgraded TWRP to 3.0.2.0 (3.0.2.1 doesn't work properly on my device. it flashes the TWRP 3 logo and then goes black) ... So I ended up re-installing TWRP 2.8.7.2 and then flashed TWRP 3.0.2.0
2) Copied the ROMS of choice to the SDCARD
3) Using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM (which didn't work correctly due to the bootloader not being Marshmallow 6.0.1 compatible) from my understanding of what i've read through these threads.
4) Flashed the AP using G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.tar.md5
Now i'm 100% locked out from downgrading Stock or Custom ROMS. TWRP can no longer be installed.
Having a feeling I used a Bear Trap ROM.
What do I do? Feeling like throwing this out the window. *sigh*.
Thanks ahead of time... anything to point me in the right direction would be greatly appreciated.
I am not a dev... but I tried smartswitch, perhaps it can help you. Hopefully you didn't do factory reset.
Try that and then if it doesn't work, again, wait for the experts.
What is SmartSwitch? Do you have a URL or THREAD with information and download links?
Thanks for the tip.
britchel said:
I am not a dev... but I tried smartswitch, perhaps it can help you. Hopefully you didn't do factory reset.
Try that and then if it doesn't work, again, wait for the experts.
Click to expand...
Click to collapse
I did an Odin flash of EPF1 and didn't lose the ability to flash recovery. I have not yet tried downgrading. I would take a deep breath, drink a beer or two, and go back through things step by step. At this point I would suggest using Odin to flash a complete image, perhaps of a different version, and go from there.
ninjadroids said:
What is SmartSwitch? Do you have a URL or THREAD with information and download links?
Thanks for the tip.
Click to expand...
Click to collapse
http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
Hey can u reboot to recovery and to download mode?
You need to be in download mode to use smart-switch
Here's another tread alike to yours....
http://forum.xda-developers.com/tmo...rick-wont-boot-successful-odin-flash-t3435751
Smiles on the beer or two!
Are you using the G920T also? Which image did you Odin flash with? Do you have the direct link? I do like your idea of flashing with a different 6.x image variant as opposed to downgrading.
socal87 said:
I did an Odin flash of EPF1 and didn't lose the ability to flash recovery. I have not yet tried downgrading. I would take a deep breath, drink a beer or two, and go back through things step by step. At this point I would suggest using Odin to flash a complete image, perhaps of a different version, and go from there.
Click to expand...
Click to collapse
Yes I can reboot into recovery and to download mode. Thank you for the link.
britchel said:
http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
Hey can u reboot to recovery and to download mode?
You need to be in download mode to use smart-switch
Here's another tread alike to yours....
http://forum.xda-developers.com/tmo...rick-wont-boot-successful-odin-flash-t3435751
Click to expand...
Click to collapse
ninjadroids said:
Smiles on the beer or two!
Are you using the G920T also? Which image did you Odin flash with? Do you have the direct link? I do like your idea of flashing with a different 6.x image variant as opposed to downgrading.
Click to expand...
Click to collapse
I don't unfortunately - Google is your friend. Some firmwares that come to mind are DOJ7, DOJC, and COF6.
But first: Is your bootloader locked? If you have not yet unlocked it, that may be a problem. I unlocked mine as soon as I got my phone (and yes I'm on a G920T). A locked bootloader may prevent downgrading although it should not prevent a rescue Odin of the same or newer firmware.
Yes it's locked.
Is there a way to unlock it while maintaining my current image?
All those firmware are 5.x
I'm stuck on unlocked Marshmallow 6.0.1
And according to Smart Switch. I'm one version down from latest with it prompting to upgrade.
I'm going to hold off on that for the moment...
If you flashed edp1, you are far from latest.
Lemme know if i am wrong at anything
If you can access download and recovery, that means the phone is in a bootloop when booting up..
Since you flashed the edp1 firmware, your bootloader must have been updated so now you can only use mm roms.
As for recovery, is it stock or twrp?
Also when in download modex whats your system status - stock or custom?
Well if EDP1 is far from latest, then that is great news. I can boot into my firmware. It's for sure stock as far as I can tell.
Download mode output:
RED: ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FAP LOCK: OFF
BLUE: Secure Download: Enabled
Knox Warranty Void: 1 (I tripped it when rooting it in 5.x)
AP SWREV: B:3 K:2 S:2
It won't let me get into TWRP after flashing it... when I try it says the following:
RED: "RECOVERY IS NOT SEANDROID ENFORCING"
It doesn't matter which version of TWRP I attempt to flash with.
Thanks!
danveer said:
If you flashed edp1, you are far from latest.
Lemme know if i am wrong at anything
If you can access download and recovery, that means the phone is in a bootloop when booting up..
Since you flashed the edp1 firmware, your bootloader must have been updated so now you can only use mm roms.
As for recovery, is it stock or twrp?
Also when in download modex whats your system status - stock or custom?
Click to expand...
Click to collapse
Did you flashed root or anything after you tried to flash recovery via odin?
Also when you flashed edp1, phone still didnt boot?
Edp1 is about the march or april update i think
The next main update is epf1 because it restricts going back futher
Then there came a update 5 days ago.. just a security update... havent flashed that coz i am rooted..
Anyways lets concentrate on edp1
Since its a mm rom, going back to 5.1 roms means a bootloop, so ill suggest not doing that
Also after flashing the mm rom, if you flash anything over it, you wont be able to boot a system because a new dm verity check mm has introduced.. to bypass it, you either need to flash a mm root file or a kernel that can disable the check.
I was stuck at the same thing since i Flashed recovery and that failed the checks so was getting bootloops..
I was able to go in recovery and download mode but not boot up..
Since you have a custom status, it can be a reason for bootloops
http://forum.xda-developers.com/gal...y-official-twrp-galaxy-s6-edge-t3354508/page8
The phone boots. I just cannot get root. I guess I don't understand the terminology regarding "bootloops" or "MM" ... I attempted a APK root... which failed. And still using my previous kernel unless flashing the custom ROM overwrote that.
So I can login to the phone and connect it to USB and sideload APK files, no problem. I just cannot TWRP flash properly and enter it using the UP recovery mode. And when I tried flashing other ROMS in Download recovery mode either ODIN crashes or it gives me a NAND WRITE error.
Which root and / or kernel files would you suggest to me to flash in ODIN to break this protection that's preventing a full root on this image? Or would it be preferable in my situation to find a different ROM and resolving the ODIN crash problem to achieve a full 6.x marshmallow root?
Thanks again! Greatly appreciated Sir.
danveer said:
Did you flashed root or anything after you tried to flash recovery via odin?
Also when you flashed edp1, phone still didnt boot?
Edp1 is about the march or april update i think
The next main update is epf1 because it restricts going back futher
Then there came a update 5 days ago.. just a security update... havent flashed that coz i am rooted..
Anyways lets concentrate on edp1
Since its a mm rom, going back to 5.1 roms means a bootloop, so ill suggest not doing that
Also after flashing the mm rom, if you flash anything over it, you wont be able to boot a system because a new dm verity check mm has introduced.. to bypass it, you either need to flash a mm root file or a kernel that can disable the check.
I was stuck at the same thing since i Flashed recovery and that failed the checks so was getting bootloops..
I was able to go in recovery and download mode but not boot up..
Since you have a custom status, it can be a reason for bootloops
http://forum.xda-developers.com/gal...y-official-twrp-galaxy-s6-edge-t3354508/page8
Click to expand...
Click to collapse
ninjadroids said:
The phone boots. I just cannot get root. I guess I don't understand the terminology regarding "bootloops" or "MM" ... I attempted a APK root... which failed. And still using my previous kernel unless flashing the custom ROM overwrote that.
So I can login to the phone and connect it to USB and sideload APK files, no problem. I just cannot TWRP flash properly and enter it using the UP recovery mode. And when I tried flashing other ROMS in Download recovery mode either ODIN crashes or it gives me a NAND WRITE error.
Which root and / or kernel files would you suggest to me to flash in ODIN to break this protection that's preventing a full root on this image? Or would it be preferable in my situation to find a different ROM and resolving the ODIN crash problem to achieve a full 6.x marshmallow root?
Thanks again! Greatly appreciated Sir.
Click to expand...
Click to collapse
Which odin are you using?
Try 3.10.7 because using older odin on mm gives that nand write error...
That could explain a lot of things
I'm using 3.10.7 latest.
danveer said:
Which odin are you using?
Try 3.10.7 because using older odin on mm gives that nand write error...
That could explain a lot of things
Click to expand...
Click to collapse
http://forum.xda-developers.com/che...rite-start-fail-odin-soluction-t2851096/page5
Try this thread..
It has solutions when nand write fails...
Also trying a different verion pf odin might work like 3.10.6 or another maybe
ninjadroids said:
Yes it's locked.
Is there a way to unlock it while maintaining my current image?
All those firmware are 5.x
I'm stuck on unlocked Marshmallow 6.0.1
And according to Smart Switch. I'm one version down from latest with it prompting to upgrade.
I'm going to hold off on that for the moment...
Click to expand...
Click to collapse
EPD1 and EPF1 are 6.0.1 Marshmallow.
@ninjadroids:
Take this as you will but reading back through this thread gives me the impression that you lack the necessary know-how to customize your phone. I highly suggest you leave it stock for the time being until you know EXACTLY what you are doing.
My reasons for saying this:
-In your first post you state that "using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM". To my knowledge there are NO custom ROMs designed to be flashed via Odin. They are in .zip files, to be installed via recovery ONLY.
-This is actually my mistake - the G920T bootloader does not have a lock function; flashing a custom recovery will simply trip the e-fuse and render it Knox 0x1 warranty void.
-You are not familiar with what Odin images are for the G920T, or what version they are. You should NEVER flash ANYTHING via Odin unless you are absolutely sure it is intended for your specific device.
-In the 9th post you state your bootloader is unlocked (again I apologize for the confusion) but in the 3rd line you say you're on unlocked Marshmallow. I'm going to assume you have limited knowledge of what the bootloader, the recovery, download mode, and system are.
-You mention seeing the red "RECOVERY IS NOT SE ANDROID ENFORCING". This is an error message generated by the bootloader saying the recovery is custom and did not pass the security check...but it is also completely normal. I get it every single time I go into TWRP...which works just fine.
-You do not understand what "MM" means when all of us including you are talking about Marshmallow.
-You do not understand what a "bootloop" is. For the sake of education, a bootloop is exactly what it sounds like - your device gets stuck in a loop while booting. This is generally mentioned when it is persistent - the device does not complete the boot process, coming to a stable useable Android interface. This is indicative of several possible problems; most likely you did something incorrectly, causing the boot process to halt, in which case the phone restarts itself to attempt to boot again, hence the loop.
-You do seem to understand sideloading via ADB and I'll give you credit for that. But when using the button combo (Vol Up+Home+Pwr) to boot into recovery, you WILL boot into recovery...whether that is stock recovery or TWRP. Some reboots may prevent this; if in doubt, hold Vol Down+Home+PWR until the screen shuts off; immediately go to Vol UP while still holding Home and Power.
-In the 13th post you ask about flashing kernels via Odin. Firstly: custom ROM .zips contain the kernel intended to work with that ROM. There is no need to flash anything separately. I am a little fuzzy on how root is accomplished on stock Marshmallow; it used to be we could flash SuperSu via recovery, but now there is talk about systemless...Anyway, I will reiterate what I was saying about Odin: DO NOT USE IT unless you know EXACTLY what you are doing. You have the potential to turn your phone into an expensive paperweight.
I am not trying to put you on blast or criticize you; I'm trying to help you avoid bricking your phone. There are a lot of things that could go wrong; you shouldn't be messing with something you don't understand, especially if you don't know how to fix it if something goes wrong.
For now even i am confused as to what is causing error.
Its probably that his storage is not curropt causing namd write fail..
I would recommend doing a backup. since you can turn on a phone, connect it to pc and move the important files and contacts to it.
Then download stock rom via sam mobile and do a clean install..
Ill prefer pf1 because, if memory serves right, edp1 had that notorious auto brightness bug.. If odin is not helping then try smart switch.
Boot up system, see if everything is working..it should be fresh as new.
After that follow the instructions as to flash twrp from the link i gave in one of my previous posts.. twrp should now flash...( i dont see any reason it shouldnt )
Flash root via recovery, or a custom rom you wanna flash but make sure its a 6.0.1 one ( xtre sto lite or alexis recommended )
That should root your phone too...
P.s. mm -> short for MarshMallow
Bootloop, when all you see is samsung logo which comes during boot... it wont go past that.. you never reach your lock screen or are able to unlock your phone... as mentioned in detail by -> socal
Flashing any rom overwrites kernel so if you flashed edp1, you are now on stock kernel...
P.p.s when you said sideload apk.. was it via adb shell or simply installing apk from internal memory of phone?
You answered a lot of my questions in that last post. Thank you kindly.
socal87 said:
EPD1 and EPF1 are 6.0.1 Marshmallow.
@ninjadroids:
Take this as you will but reading back through this thread gives me the impression that you lack the necessary know-how to customize your phone. I highly suggest you leave it stock for the time being until you know EXACTLY what you are doing.
My reasons for saying this:
-In your first post you state that "using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM". To my knowledge there are NO custom ROMs designed to be flashed via Odin. They are in .zip files, to be installed via recovery ONLY.
-This is actually my mistake - the G920T bootloader does not have a lock function; flashing a custom recovery will simply trip the e-fuse and render it Knox 0x1 warranty void.
-You are not familiar with what Odin images are for the G920T, or what version they are. You should NEVER flash ANYTHING via Odin unless you are absolutely sure it is intended for your specific device.
-In the 9th post you state your bootloader is unlocked (again I apologize for the confusion) but in the 3rd line you say you're on unlocked Marshmallow. I'm going to assume you have limited knowledge of what the bootloader, the recovery, download mode, and system are.
-You mention seeing the red "RECOVERY IS NOT SE ANDROID ENFORCING". This is an error message generated by the bootloader saying the recovery is custom and did not pass the security check...but it is also completely normal. I get it every single time I go into TWRP...which works just fine.
-You do not understand what "MM" means when all of us including you are talking about Marshmallow.
-You do not understand what a "bootloop" is. For the sake of education, a bootloop is exactly what it sounds like - your device gets stuck in a loop while booting. This is generally mentioned when it is persistent - the device does not complete the boot process, coming to a stable useable Android interface. This is indicative of several possible problems; most likely you did something incorrectly, causing the boot process to halt, in which case the phone restarts itself to attempt to boot again, hence the loop.
-You do seem to understand sideloading via ADB and I'll give you credit for that. But when using the button combo (Vol Up+Home+Pwr) to boot into recovery, you WILL boot into recovery...whether that is stock recovery or TWRP. Some reboots may prevent this; if in doubt, hold Vol Down+Home+PWR until the screen shuts off; immediately go to Vol UP while still holding Home and Power.
-In the 13th post you ask about flashing kernels via Odin. Firstly: custom ROM .zips contain the kernel intended to work with that ROM. There is no need to flash anything separately. I am a little fuzzy on how root is accomplished on stock Marshmallow; it used to be we could flash SuperSu via recovery, but now there is talk about systemless...Anyway, I will reiterate what I was saying about Odin: DO NOT USE IT unless you know EXACTLY what you are doing. You have the potential to turn your phone into an expensive paperweight.
I am not trying to put you on blast or criticize you; I'm trying to help you avoid bricking your phone. There are a lot of things that could go wrong; you shouldn't be messing with something you don't understand, especially if you don't know how to fix it if something goes wrong.
Click to expand...
Click to collapse
Wonderful. Thanks man. I will be attempting a Stock ROM Odin flash and go from there. I will update my progress. Thank you all very much for the answered questions and pointing me in the right direction. Hopefully this thread will prove useful for anyone who is attempting to deal with a G920-T and attaining root the proper way for Marshmallow 6.x
danveer said:
For now even i am confused as to what is causing error.
Its probably that his storage is not curropt causing namd write fail..
I would recommend doing a backup since you can turn on a phone
Then downloading stock rom via sam mobile and do a clean install...if odin is not helping doing that then try smart switch.
Boot up system, see if everything is working..
After that follow the instructions as to flash twrp from the link i gave in one of my previous posts.. twrp should now flash...( i dont see any reason it shouldnt )
Flash root via recovery, or a custom rom you wanna flash vut make sure its a 6.0.1 one ( xtre sto lite or alexis recommended )
That should root your phone too...
Click to expand...
Click to collapse
I have a Lenovo K3 Note K50-t3s and I'm in a need of a stock ROM because the ROM that came with is a custom ROM (it's a second-hand phone). I went to this page, https://forum.xda-developers.com/k3-note/general/official-firmware-lenovo-k3-note-direct-t3326424 and downloaded the latest ROM in the "K50-t3s - Full ROM – DEV" part. After downloading, I went to extract it. But as soon as my 7-Zip shows the .zip's contents, it looks like it's an OTA update package, crud...I thought it was meant to be flashed through SP Flash Tool. I then copied the package to the internal storage and tried to install it through stock recovery, but it fails. I've tried other ROMs like the K50-T5, but it just leads to the disappearing of the System Update option in Settings > About phone (I believe that is what causing it to disappear). Not yet tried the K50a40, but I'm expecting it will do the same thing to the System Update option. I think by flashing the "real" ROM, then the System Update appears. So, how am I going to use the .zip I've downloaded to restore the phone when it fails through stock recovery and is not flashable through SP Flash Tool? I need at least an answer to "how to use that "failing" OTA package" or "where can I find the SP Flash Tool flashable K50-t3s ROM". Out of all phones I've unbricked, this is the hardest...