Hi, I'm trying to correct some confusion that I have in dealing with various bootloader file vrrsions which run with the smp600. One what I believe is a stock virgin android 5.11 (KitKat), the bootloader ID shows as P600UEUDQF1. Is this correct for stock? My tablet is running a current custom ROM with LP bootloader which shows as P600XXUDPL1. Is this also correct? Many time that I have asked for a simple listing to show this, but never get straight answers. I did not think the question was difficult, and since a bootloader CAN be changed from stock, they don't always correspond to the installed version of android. But these two are supposed to be P600URUDQF1 -KitKat and P600XXUDLP1 -Lolipop.
Can snyone correct these if they are wrong. Now, I have a 3rd smp600 unit bight in the states. I suspect that it may even have a different chipset than the first two... Thanks ;DDeanoD
Have you ever found an answer to this?
I have the same P600UEUDQF1 and because I dunno if it is a lollipop bootloader or not I don't know if I should first update it before attempting root/custom OS...
Related
So, the other day I got the 5.0 OTA on my rooted 4.4.2, and I naively updated it, without knowing that:
1 - I'd loose root and my recovery
2 - There's no way to root 5.0
After two days of trying stuff, I finally understood what many people know, I suppose, but I couldn't see it written clearly anywhere, so I thought I'd share. You have to:
1 - Flash back 4.4.2
2 - Root 4.4.2
3 - Flash a custom recovery
4 - Flash a rooted 5.0 from custom recovery
I now have a rooted 5.0
Here. It's not very complicated to do, but maybe it's so obvious for people who know it that they never care to put it like this (I'm not complaining, I actually did find all the information I needed on XDA and learned a good deal of things about my phone on the way so it's cool).
You cant.
DelBoy said:
You cant.
Click to expand...
Click to collapse
Sorry I lack experience so much with the forum that I posted without any content initially so you must have thought that I was asking for the solution. I get that you can't simply root 5.0, but you can actually get 5.0 rooted if your phone has 5.0 non rooted by switching to 4.4.2 first, which is really what people want to do when they ask that question. I have seen your answer before, and almost gave up trying, but I'm glad I insisted. Just saying "you can't" is just being deliberately unhelpful (or not knowing what you are talking about).
GordonFreemanK said:
Sorry I lack experience so much with the forum that I posted without any content initially so you must have thought that I was asking for the solution. I get that you can't simply root 5.0, but you can actually get 5.0 rooted if your phone has 5.0 non rooted by switching to 4.4.2 first, which is really what people want to do when they ask that question. I have seen your answer before, and almost gave up trying, but I'm glad I insisted. Just saying "you can't" is just being deliberately unhelpful (or not knowing what you are talking about).
Click to expand...
Click to collapse
Yeah, there was only name of the thread and word "So"
So I thought you were looking for solution :laugh:
Some more information on how to get there:
To get 5.0 rooted, you need to:
- take note of which 5.0 version you have on your phone and check you can get the bumped image somewhere, if you want to have exactly the same at the end.
- update LG PC Suite or at least the Windows drivers for the G3? Honestly I'm not sure how important this is, since I was playing around for hours and I did that in the process, maybe it's necessary. It is necessary to have the drivers installed at least.
- find the 4.4.2 version of the ROM for your phone (mine was V10e-EUR-XX), versions are different for 16GB/32GB versions.
- flash it with Flashtool (http://forum.xda-developers.com/showthread.php?t=2785089)
- root using your favourite tool (I used one I had on my PC, not sure which version but PurpleDrake should do: http://forum.xda-developers.com/lg-g3/development/root-root-lg-g3-easily-purpledrake-lite-t2821000)
- find a TWRP image
- flash TWRP (I used this tutorial: http://www.phonearena.com/news/How-to-flash-a-custom-recovery-like-CWM-or-TWRP-on-Android_id53914)
- find the bumped version of 5.0 for your phone (mine is V20e-EUR-XX and I found it on this forum)
- flash it using TWRP
- start the phone and set it up (it should be rooted already)
- install the SuperSU binaries using TWRP
Fun and heavy Titanium Backup freezes ensue! My phone has now 80% battery left 8h after being disconnected from the charger this morning, as opposed to 60% after two hours just after installing the OTA update.
Note: this was done on the unlocked 16GB European D855 version I bought in the UK. Not sure about other versions!
Bonus: in order to improve my battery life, besides Titanium-Backup-freezing the hell of the LG bloatware (I think McAfee and LG Health are the main culprits) and some Google bloatware I don't use (Google Play Apps anyone?) I also disabled knock on by following the advice #8 in this tutorial: http://www.androidauthority.com/lg-g3-problems-517832/
I've read all about the problem with rooting the G3 Stock Lollipop Version.
But there is no info, where I can find out WHY it is how it is.
So, why is 5.0 actually unrootable? And will this change in future?
SlideMouse22 said:
I've read all about the problem with rooting the G3 Stock Lollipop Version.
But there is no info, where I can find out WHY it is how it is.
So, why is 5.0 actually unrootable? And will this change in future?
Click to expand...
Click to collapse
Ummm. Have you tried looking on XDA?
There was a BIG post with details. The technical part is here: link
No, this won't change. Restricting services to their context means that bug in almost any service won't be able to compromise entire system. That's a great security feature, actually.
Hello, it's been a long time since I messed with this but I'm smart. I'm also in a rush (unfortunately) to find a TW-based firmware that I can flash to from CM11.
The end goal is to use the unlock code I just purchased, but that won't work because I'm on CM11, I assume.
I'm knee deep in information, half of which I understand, half of which I think I barely understand.
What information do you need to help me?
From what I understand, being on a 4.4.4 CM 11 I must have a firmware that is at least android 4.3 or higher, is that correct?
If so, what other specs do I need to ensure I don't brick the phone from having the wrong bootloader, modem, ect from being incompatible?
Effectively, I'm tyring to find firmware to get back to any TW-based firmware from CM11 android 4.4.4. (Also somewhat unsure if it needs to be just TW based or 100% stock)
politelyowned said:
Hello, it's been a long time since I messed with this but I'm smart. I'm also in a rush (unfortunately) to find a TW-based firmware that I can flash to from CM11.
The end goal is to use the unlock code I just purchased, but that won't work because I'm on CM11, I assume.
I'm knee deep in information, half of which I understand, half of which I think I barely understand.
What information do you need to help me?
From what I understand, being on a 4.4.4 CM 11 I must have a firmware that is at least android 4.3 or higher, is that correct?
If so, what other specs do I need to ensure I don't brick the phone from having the wrong bootloader, modem, ect from being incompatible?
Effectively, I'm tyring to find firmware to get back to any TW-based firmware from CM11 android 4.4.4. (Also somewhat unsure if it needs to be just TW based or 100% stock)
Click to expand...
Click to collapse
The first thing I would recommend is to verify your bootloader and modem version. There is a playstore app, Phone Info *Samsung*, by vndnguyen that will do this. Or you can use the terminal emulator that is in CM roms and find out with these two commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
All I have seen indicates you will need to be on a stock rom with a stock dialer to use the code. You may even need to unroot before using (I am not sure about root/unroot.) Before recommending any stock rom source, are you using an i747 or an i747M?
dawgdoc said:
The first thing I would recommend is to verify your bootloader and modem version. There is a playstore app, Phone Info *Samsung*, by vndnguyen that will do this. Or you can use the terminal emulator that is in CM roms and find out with these two commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
All I have seen indicates you will need to be on a stock rom with a stock dialer to use the code. You may even need to unroot before using (I am not sure about root/unroot.) Before recommending any stock rom source, are you using an i747 or an i747M?
Click to expand...
Click to collapse
I know that it is an I747. I will comment again when I have the info for bootloader and modem.
So lets assume we find a rom that is; i747 gs3 stock rom and stock dialer; meets android version requirements (which I would love to have confirmed, based on the OP); compatible bootloader and modem; and is rooted, and the unlock code doesn't work. If we assume the unlock failed because it is rooted, is there a way to unroot the phone that doesn't require flashing a different, unrooted, to spec, rom? That is something that I truly don't understand what is happening.
Is there a wiki, or a list, or somewhere I can go to learn more about bootloaders and modems? I don't understand how they play into the overall configuration; such as how they may be X or Y when I'm running CM11, instead of being mandatory for a given configuration. I guess that question is, what prerequisites determine the bootloader and modem options that one may be and can be running or that one can flash successfully.
politelyowned said:
I know that it is an I747. I will comment again when I have the info for bootloader and modem.
So lets assume we find a rom that is; i747 gs3 stock rom and stock dialer; meets android version requirements (which I would love to have confirmed, based on the OP); compatible bootloader and modem; and is rooted, and the unlock code doesn't work. If we assume the unlock failed because it is rooted, is there a way to unroot the phone that doesn't require flashing a different, unrooted, to spec, rom? That is something that I truly don't understand what is happening.
Is there a wiki, or a list, or somewhere I can go to learn more about bootloaders and modems? I don't understand how they play into the overall configuration; such as how they may be X or Y when I'm running CM11, instead of being mandatory for a given configuration. I guess that question is, what prerequisites determine the bootloader and modem options that one may be and can be running or that one can flash successfully.
Click to expand...
Click to collapse
Some of the stock ROMs will remove root, that would be one way to resolve the issue. If you flash a stock image that is rooted, and it is rooted with SuperSu you can use the options in the SuperSu app to either temporarily unroot or to completely remove root.
I don't recall seeing a specific source for info about what bootloader / modem is needed in each situation. Most is accumulated knowledge from reading many posts and threads.
There are variations on what is correct, it all depends on the specifics of a device's status. For example, CM 11 would run on 4.3 bootloaders and modems up until about September of a year ago (or was that two years ago), since then you need to be on 4.4.2 bootloaders and modems. I think the same held true for AOSP based roms. I don't recall seeing where any of the 5.x.x roms have run on 4.3 bootloaders and modems. (Well, I think the devices run but have signal and data issues - both 4.4.x and 5.x.x roms.)
Generally you will see it said that the 4.4.2 Touchwiz based custom roms must be on 4.4.2 bootloaders and modems. In truth there were a number of such roms that would run with the 4.3 bootloader and modem IF one of a few specific kernels were flashed just after the rom was flashed.
Hi,
After doing some reading on here I am a little unsure on the best way to back up my HTC One M9 (GSM) stock recovery/system. My software number is 3.50.710.1 (Android 6.0) and it came from Optus (Australia). I cannot seem to find an RUU file for this firmware anywhere online; only earlier versions are available. My understanding of this is that I need an RUU file for my specific firmware as a fail-safe in case I mess something up and need to return to stock?
My questions are:
1) Can I get my phone back to the current complete stock firmware and be able to receive future OTA updates without turning s-off and without copying anything from my phone before I flash TWRP and a custom ROM?
2) If not is there anyway that I can back up my phone it its current stock state that will allow me to go back to this state if I want to go back to my stock Optus firmware or to install OTA updates? (Including the stock radio/recovery)
3) Reading this post as well as others leads me to believe that I may stop my mobile radio working by flashing a custom ROM (especially as the linked post has the exact same firmware as me). How can I avoid this, or fix it if it happens to everyone?
I am ideally looking for a custom ROM which improves over the stock firmware. My priority is maximum battery life, with customisation and HTC 10 system UI/apps a secondary focus. Any recommendations would be great, as well as tweaks and kernels which help give the maximum battery life.
Cheers!
You can't backup your firmware (and that includes your radio). However if you read my google sheet you'll find instructions for backing up your current boot.img, your system and the stock recovery. If you do it correctly those files will suffice for recovering the ability of installing OTAs. No personal data will be backed up so maybe you want to share your backup with us afterwards.
There is a custom kernel for CM/AOSP roms which is said to repair the signal problems. As far as I read some sense rom users reported that flashing the stock boot.img recovered their signal. However this doesn't seem to work for every user. So you'll need to try by yourself.
Flippy498 said:
You can't backup your firmware (and that includes your radio). However if you read my google sheet you'll find instructions for backing up your current boot.img, your system and the stock recovery. If you do it correctly those files will suffice for recovering the ability of installing OTAs. No personal data will be backed up so maybe you want to share your backup with us afterwards.
Click to expand...
Click to collapse
Thank you so much! I have managed to find the guide you mentioned to backup the stock boot image, system image and recovery. By the looks of it the tab to the right is the guide to return my phone to its original state, which is good. I'm more than happy to share the backup once I do it.
Flippy498 said:
There is a custom kernel for CM/AOSP roms which is said to repair the signal problems. As far as I read some sense rom users reported that flashing the stock boot.img recovered their signal. However this doesn't seem to work for every user. So you'll need to try by yourself.
Click to expand...
Click to collapse
Okay, well I am planning on keeping s-on at this stage, so I'm left with Sense based ROMs I believe? I have read that LeeDroid is the best for battery life, does this sound right? If so I am unsure if I can flash it as it says "Please make sure you have the latest HTC Hima 3.35.XXX.XX Marshmallow firmware installed prior to installing this ROM" because my software number is 3.50.710.1?
Thanks again!
Da Doom Lord said:
Okay, well I am planning on keeping s-on at this stage, so I'm left with Sense based ROMs I believe? I have read that LeeDroid is the best for battery life, does this sound right? If so I am unsure if I can flash it as it says "Please make sure you have the latest HTC Hima 3.35.XXX.XX Marshmallow firmware installed prior to installing this ROM" because my software number is 3.50.710.1?
Click to expand...
Click to collapse
I've read that several times in the near past and I actually don't understand it. You never needed S-OFF for flashing none-sense based roms as long as I started using Android/HTC phones and that was back in 2012. Why do so many people think they need S-OFF for AOSP?
I personally prefer the Viper rom. But taste differs and in the end the best advice I can give is try it out by yourself. Everyone has different needs and is using his/her phone in a different way. The best rom for person a might be an awful choice for person b since he/she has completely different needs.
I can't tell you whether you can use Leedroid. Test it and report back. That's how xda works. You might be able to use it after you flashed your stock boot.img but I don't know whether you really are or not. The warning is written so that people don't start flashing that rom with a lower firmware version. On older HTC phones flashing an "older" rom has never been an issue on newer firmware versions whereas flashing a newer rom on an older firmware never goes well (even on the M9). However many things have changed since the M9. There is no hboot anymore, the Download Mode got introduced, google changed the way OTAs are checking whether your system is modified, and so on. (Just to mention a few changes.) Those issues with the lost signal didn't even exist on pre-3.x firmware versions of the M9. Therefore users like you who use a not so common firmware (in comparison to the user numbers of the most common firmware bases: international, taiwanese and the developer firmware) have no other choice but trying out by themselves or getting S-OFF and changing to a more common firmware.
Flippy498 said:
I can't tell you whether you can use Leedroid. Test it and report back. That's how xda works. You might be able to use it after you flashed your stock boot.img but I don't know whether you really are or not. The warning is written so that people don't start flashing that rom with a lower firmware version. On older HTC phones flashing an "older" rom has never been an issue on newer firmware versions whereas flashing a newer rom on an older firmware never goes well (even on the M9).
Click to expand...
Click to collapse
I have followed your guide and now have the latest stable LeeDroid ROM installed and TWRP. Just as I predicted the radio was not originally working. When I restored my stock boot.img from the original backup I performed it began to work. Thanks so much for your help! I'll upload the backup to cloud storage when I get access to a decent internet connection and then I'll share it to help others out.
I tried flashing n910vvru2cql1 partial firmware in odin and phone info is still showing cpd1 as my bootloader.
history:
my phone was acting kinda buggy, wouldnt charge, turned off, got really hot about a year ago on a old version of RR and wasnt responding to anything usb so i threw it in a box and used one of my backups, a month ago or so, i moved some firmware files over by sdcard and flashed with twrp and it seems like it cleared up a lot of my issues.
I have been trying to get any rom past 6.0.1 on it and they just dont seem stable enough to run everyday so I found modest rom flashed that and it seemed pretty good except for the random restarts and lagg. i flashed flashpoint v4 kernel to try to clear problems up and it ran better but yet still kinda buggy so said screw it and flashed stock firmware cql1 kernel and over 2 days seems like everything cool except now im trying to get my bootloader up to CQL1 just so everything is unified and Sam Phone Info shows CPD1 for bootloader but CQL1 for pda, csc,baseband-radio
Are there any reason to upgrade bootloader since im already on 6.0.1 unlocked?
I wouldnt think so because my thoughts are its more like an efi bios/grub2/mbr which load the os and the kernel later gets lowerlevel access to the hardware????
Bottomline, I guess i would like to upgrade the bootloader, someone please clarify and help.
Thanks.
brianmilw said:
I tried flashing n910vvru2cql1 partial firmware in odin and phone info is still showing cpd1 as my bootloader.
history:
my phone was acting kinda buggy, wouldnt charge, turned off, got really hot about a year ago on a old version of RR and wasnt responding to anything usb so i threw it in a box and used one of my backups, a month ago or so, i moved some firmware files over by sdcard and flashed with twrp and it seems like it cleared up a lot of my issues.
I have been trying to get any rom past 6.0.1 on it and they just dont seem stable enough to run everyday so I found modest rom flashed that and it seemed pretty good except for the random restarts and lagg. i flashed flashpoint v4 kernel to try to clear problems up and it ran better but yet still kinda buggy so said screw it and flashed stock firmware cql1 kernel and over 2 days seems like everything cool except now im trying to get my bootloader up to CQL1 just so everything is unified and Sam Phone Info shows CPD1 for bootloader but CQL1 for pda, csc,baseband-radio
Are there any reason to upgrade bootloader since im already on 6.0.1 unlocked?
I wouldnt think so because my thoughts are its more like an efi bios/grub2/mbr which load the os and the kernel later gets lowerlevel access to the hardware????
Bottomline, I guess i would like to upgrade the bootloader, someone please clarify and help.
Thanks.
Click to expand...
Click to collapse
Sorry for responding late but in case anyone else is wondering, most partial firmwares that you see posted for our device model (even the ones posted in the international snapdragon rom threads that have Lineage, RR, and ported TW roms) do not contain the aboot.mbn file, aka bootloader. So it will not change our bootloader in anyway.
That's not say a dev or someone like myself who's just a beginner couldn't make a mistake and forget to remove it or maybe they don't know that it's supposed to be removed. So it would be best to stick with the tried and true links that have been posted of you're needing to update your modem. I know for certain the ones that have been posted by ripee, hsbadr, and me are safe, but I've never used not have heard anything negative about the other ones posted.
All that being said, you can update the SM-N910V bootloader if you'd like. Mine is updated to where it ends with CQI2 which is the penultimate update. If there is a difference between CQI2 and CPD1 (initial 6.0.1 bootloader) then it is a slight difference. Sometimes I think I just want to believe that tweaks and changes are working, especially if you put a lot of effort and time into it(which is required when you don't have much knowledge).
This was just posted recently;
VZW_NOTE4_EMMC_15_Chipset_Only_Bootloader_Unlock_U p/Dwngrade_Bootloaders_KK/LL/MM by jkruse
I haven't tried it yet but it looks much easier than the method I used, which is below;
For the folks that just like to tinker and break things....... How else you supposed to learn how to fix it?
How-To Update Your Bootloader from CPD1 to CQI2 by this fool
Hi! I bought my phone recently and I would like to install pure android on this device. Is this possible? If so, I would also like to know if it would be possible to download this operating system directly from Google's server (just as we download Windows directly from the Microsoft website at https://www.microsoft.com/software-download, for example). The second question is for security reasons.
Thank you!
Since no one else has answered, I'll try:
I'm going to assume what you mean by "pure" Android is the unlocked version of Samsung's firmware for your particular phone model. If you don't have some version of the Samsung Galaxy s22, then you're asking your question in the wrong place.
First you need to find out whether your phone is locked, and if so, whether it can be unlocked.
Then, watch this video for an overview:
If you decide you would like to continue, an easier way of obtaining firmware is from samfw.com.
The video mentioned above includes links to the two different types of Odin, which is the software you would use to flash the firmware onto your phone.
In general, since you haven't done this sort of thing before, I would recommend triple checking every step, as there are certain mistakes you can make that will render your phone unusable.
Good luck!