Related
As a Galaxy S i9000 owner I am curious, has anyone yet got any idea how updates and general ROM flashing are to be done on the Nexus S? I understand OTA will be likely for the PDA code but how about the baseband? Do Google take care of the modem or do Samsung?
And since we use Odin to re-partition and re-flash the ROM in the SGS I wonder how this is performed on the Nexus line?
I am very happy to see Kies left behind but I also see no software for the Nexus S at all. Even my Motorola Milestone had some sort of desktop connectivity for when things went wonky..
Is there any reason we would not use rom manager to flash new roms since that is how we have been flashing our cw recovery? Seems that would be the easiest solution just like on the n1
generalagony said:
Is there any reason we would not use rom manager to flash new roms since that is how we have been flashing our cw recovery? Seems that would be the easiest solution just like on the n1
Click to expand...
Click to collapse
My Android life has been Milestone > SGS, so I am not familiar with that one, we use Odin over USB on the Galaxy line.
Ok, that is interesting to know. Does that also include the modem code though?
If by modem code you are referring to the radio image; yes. Most all files can be flashed via clockwork recovery. It it all i ever used on n1 to flash roms, kernels, and radio files.
generalagony said:
If by modem code you are referring to the radio image; yes. Most all files can be flashed via clockwork recovery. It it all i ever used on n1 to flash roms, kernels, and radio files.
Click to expand...
Click to collapse
Superb, I will have to have a look into CWR then. Had little cause to so far.
If you are rooted already the easiest thing to do I download rom manager from the market and flash cwr through there. It has been updated to the newest version through rom manager and is completely painless
Fastboot should also work depending on how the file you want to flash is released.
fastboot recovery new_recovery.img
fastboot system custom_rom.img
fastboot modem new_modem.img
etc, etc, etc...
Think of fastboot as sort of Google's version of Heimdall (3rd party Odin replacement)
Thanks all for the input, I need to get the phone next. UK delays and such.
Samsung really went somewhere annoying by forcing a USB update system. Nexus S sounds like a happier time.
nailerr said:
Thanks all for the input, I need to get the phone next. UK delays and such.
Samsung really went somewhere annoying by forcing a USB update system. Nexus S sounds like a happier time.
Click to expand...
Click to collapse
This seems like a world of difference from HTC RUU's
JD
Updated 05/08/11
ATTENTION - IF YOU ARE ON STOCK 4349+ or any MOD BASED OFF 4349+ USING THE NEW RECALLED BOOTLOADER! READ PLEASE!
Starting with the most recent but recalled update to Tap N Tap Viewsonic has introduced a new Bootloader being called the 1.2 bootloader. This bootloader is not compatible with mods or Roms based off of the Viewsonic Current Bootloader being called the 1.1 bootloader! This bootloader provides absolutely no known advantage other than being able to boot any new STOCK kernels. If you would like to use any of our stable ROM's (i.e. Vegan 5.1.1, Vegan GingerEdition and currently CM7) using Viewsonics currently supported and shipping bootloader (1.1) you must Downgrade your bootloader and TNT Version before you flash a new kernel or a new ROM.
Please download the following downgrade update.zip and place it on your sdcard renaming it to "update.zip".
http://www.gtabdevs.com/releases/4349_Downgrade.zip
Then power down your device. And power back up while holding the power button and vol + till your display says "recovery key detected" in the top left corner.
Using the volume keys to navigate up/down in the menu highlight "Apply Internal update.zip" if you copied the update.zip to the internal memory or "Apply External SDCard update.zip" if you happened to place it on an external SDCard and then inserted it before booting to recovery. Now select the menu choice using the menu key.
This process will take a few minutes. You will see a Box with an arrow and a progress bar while it applies the update.... when it is finished it will reboot to make the changes. Once the changes are complete your tablet will boot into Tap N Tap version 3588.
You are now free to follow all the tutorials about installing CWM and/or Kernels/Roms.
Thank you and good luck.
Be aware. I am not connected with Viewsonic in any way. I make no assertions as to the validity nor the safety of anything in this post. Do anything above at your risk.
That is a handy utility to have. Thanks!
How do we check if the bootloader is locked? I'm curious if the bootloader.bin in 3991 (which is based off the same branch) has this same issue.
Thanks!
Strange. One step forward and two steps back for Viewsonic. But, maybe, this means there is still some interest from Viewsonic for our tablet and chance for further development (maybe even Honeycomb).
roebeet said:
How do we check if the bootloader is locked? I'm curious if the bootloader.bin in 3991 (which is based off the same branch) has this same issue.
Thanks!
Click to expand...
Click to collapse
If it too will not boot any other kernel besides a stock kernel built specifically for their new bootloader. That bootloader.bin also appears to be locked.
gojimi said:
If it too will not boot any other kernel besides a stock kernel built specifically for their new bootloader. That bootloader.bin also appears to be locked.
Click to expand...
Click to collapse
Does that mean it's locked, or does that mean that we just don't have the new source code to build custom kernels? I just want to distiguish because, if it's the latter, we can just ask them to release that like they did the 1.1-based source. EDIT: Already tweeted them. I see "1.1" in the source that's there, and we know that this is "1.2", so maybe there's new source code to be requested? Not sure.
I know that we can check for a locked bootloader with something like fastboot, but I don't think that works here. That's why I was asking.
Thanks again!
gojimi said:
If it too will not boot any other kernel besides a stock kernel built specifically for their new bootloader. That bootloader.bin also appears to be locked.
Click to expand...
Click to collapse
what could the thinking possibly be to locking the bootloader on a product like ours?
I'm seriously asking, besides being dicks, what would the reasoning be?
roebeet said:
Does that mean it's locked, or does that mean that we just don't have the new source code to build custom kernels? I just want to distiguish because, if it's the latter, we can just ask them to release that like they did the 1.1-based source.
I know that we can check for a locked bootloader with something like fastboot, but I don't think that works here. That's why I was asking.
Thanks again!
Click to expand...
Click to collapse
By all means ask for their new source... though I do not believe at this point they are required to give... maybe they are. So for the purposes of everyone else's understanding this is a LOCKED bootloader in the sense that we are LOCKED to their kernel...... nothing ever stays locked forever.... this is not however LOCKED in the terms that a select few who already know what's going on with this bootloader typically use the term LOCKED. Take it as you will.
snapz54 said:
what could the thinking possibly be to locking the bootloader on a product like ours?
I'm seriously asking, besides being dicks, what would the reasoning be?
Click to expand...
Click to collapse
To be honest they are probably tired of all the people calling viewsonic support with issues that are not on OFFICIAL viewsonic software... most companies try to do something to deter this activity in some regards.
Does nv flash still works to downgrade everything?
gojimi said:
To be honest they are probably tired of all the people calling viewsonic support with issues that are not on OFFICIAL viewsonic software... most companies try to do something to deter this activity in some regards.
Click to expand...
Click to collapse
I understand this for "most companies" but Viewsonic is the company that openly linked on their product page that XDA is the place to be if you need support or any real use from your gtab.
We had to fight them to finally stop doing that. It doesn't really add up.
The only thing this does if it works is effectively pull the plug on the life support that was pumping any further life into the tablet.
We still have great "legacy" roms and infrastructure that make the tablet great. but moving forward all this does is concentrate our efforts towards them. releasing a workable open solution keeps us busy tinkering with it for months. Locking things down only sends us back to twitter and the like but now we have more members thanks to the new OD, TD, and amazon users.
I thought VS said they were going to work with the devs. Didnt they contact you guys? I thought they would of asked or told you guys what the best way for them to go would be. Did this never happen?
Pazzu510 said:
Does nv flash still works to downgrade everything?
Click to expand...
Click to collapse
Yes, maybe. I had to NVflash mine because I accidentally flashed CWM over 4349 while i was playing in the 4349 recovery screen. The NVflash process worked, but for some reason my touch screen was borked (no touches were registered). Couldn't do anything. In the past a couple restarts with calibration.ini on the external SD would clear that for me, but didn't this time. I ended up doing NVflash with CWM as part9.img and then repartitioned with CMW and NVflashed again with stock recovery part9.img. Screen was still borked but cleared up with a couple restarts with calibration.ini on an external SD. So the answer is yes you can, but it may not be as smooth as you are used to. Of course it may work fine for you.
Matt
jasco13 said:
Yes, maybe. I had to NVflash mine because I accidentally flashed CWM over 4349 while i was playing in the 4349 recovery screen. The NVflash process worked, but for some reason my touch screen was borked (no touches were registered). Couldn't do anything. In the past a couple restarts with calibration.ini on the external SD would clear that for me, but didn't this time. I ended up doing NVflash with CWM as part9.img and then repartitioned with CMW and NVflashed again with stock recovery part9.img. Screen was still borked but cleared up with a couple restarts with calibration.ini on an external SD. So the answer is yes you can, but it may not be as smooth as you are used to. Of course it may work fine for you.
Matt
Click to expand...
Click to collapse
I've nvflashed back to 1105 at least a dozen times since last night (was doing upgrade / downgrade scenarios). So far, so good.
The bootloader is provided by viewsonic I think, it may be the key for some chipset feature, some other brand of tablet like the adam already has the same exact one
it's probably not locked but only doing something different like you said!
if I had to guess, they didn't lock it to be pricks...odds are it is locked to prevent people from flashing our current kernels to this to avoid messing things up...
so here's prolly how we'll be structuring our ROMs/Kernels now...1.1-based Froyo ROM; 1.2-based Froyo ROM; 1.1-based Froyo Kernel; 1.2-based Froyo Kernel and so on for GB if we're lucky HC in the future.
It's going to be a pain in the butt in the short-term, but long-term it'll only benefit current and future gTab owners as a whole if we stick to the 1.2 path alongside the vendor. This will keep confusion to a minimum, features to a maximum, and upgradability easy.
Thanks to all devs for their future support even through some of the PITA times
i have no options to choose between, aka no menu when i do all that, it just goes to a box picture and then reboots and loads normally.
Edited...You can't fix stupid
iamnottypingthis said:
i have no options to choose between, aka no menu when i do all that, it just goes to a box picture and then reboots and loads normally.
Click to expand...
Click to collapse
There is no menu. It takes you back to 3588 and the ability to flash all current roms.
So this "rollback" is jsut a stock 3588 image, or is it something different?
Before you go ahead and start unlocking, flashing and rooting, there are things you should know. This thread is a general guide that will serve to explain most of those things.
.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.
Table of Contents
A. The layers (Hardware, Firmware, Software)
B. Definitions
C. Troubleshooting Common Issues
.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.
The Layers. How does everything come together?
Just like any other computing device there are 3 Layers to your phone. It helps to realize this prior to modifying your phone, so you are able to troubleshoot issues more effectively.
Layer 1 Hardware: The hardware layer is the physical components of your phone. That which you can touch, hold and see. This layer is the least likely to be modified unless you are a crazy super master level modder. Very few bother to mess with this layer so this layer tends to be the most stable with very little issues arising. The best way to make sure a problem is not related to the hardware layer, that is to say, a physical hardware problem where a physical component needs replacing, is to return all software and firmware to stock. This is typically done by running an RUU or manually reflashing stock firmware and software. There are instances where software or firmware modifications can affect the hardware. For example, if you overclock your CPU, the added heat could permanently damage the CPU and even other hardware components so be sure to take that into consideration.
Layer 2 Firmware: This layer is what allows the software to control the hardware in your phone, like a bridge between the two. There is firmware for just about every component of your phone, the camera, screen, radio, processor etc etc. This is the second least likely layer to be modified. S-Off is required to modify most, but not all, firmware files and rightfully so. Modifying firmware components can easily damage your phone if you do not understand what you're doing. In some cases a JTAGG repair can fix your phone from firmware modification damage, other times, only replacing physical components can repair the damage done. (Recovery and the kernel are technically part of the firmware layer but do not require S-Off to flash)
Layer 3 Software: The software layer consists of the "ROM" and applications on your phone. This is where most of the modification takes place and while modifying the software layer is the least likely to cause serious issues, it can still be dangerous. Flashing a ROM not intended for your device could easily put your phone into a bricked state. With SuperUser or Root access, software is capable of modifying the firmware layer of your device. It is up to you to decide what is safe and what's not safe. This is why rooting is not for everyone. How can you properly decide what is safe for your device without the proper knowledge?
Definitions
What is root?
Root, super user or su for short is a level of access giving you permission to read or write to folders, or partitions you could not have access to as a regular user. Think administrative access.
Consider a folder path “/sdcard/downloads/” If we break it down, “downloads” is a folder in “sdcard” and “sdcard” is one of the folders in “/” which is the “root” of the folder structure. As a regular user, one might not consider that folders other than sdcard exist in “/” as they are kind of hidden from us but rest assure they are there and this is typically where the android OS and firmware files are kept. Modifying these files can be extremely dangerous for your phone if you do not understand the modifications to the file you're making, and what steps you can take to recover from any issues you encounter.
What is an RUU?
RUU stands for ROM Update Utility. An RUU is used to reflash an existing firmware/software set or updated firmware/software set. An RUU will wipe everything and basically get your phone back to stock. Unless your phone is S-Off, you cannot run an RUU with an older firmware or software than those currently on your device. You can only run an RUU that matches your MID/CID unless you are S-Off and have SuperCID or have changed the MID/CID to match the carrier you are flashing. There may be differences in hardware/firmware between MIDs and CIDs so be mindful as this can lead to a brick. To properly run an RUU with S-On, you must also have stock recovery installed, the bootloader must be locked/relocked. BE VERY CAREFUL DOING THIS. It is not recommended to RUU or OTA after unlocking your bootloader unless you have to. If you are S-OFF you can RUU whether the bootloader is locked or not and if you are superCID, CID checks will be ignored so be sure to be mindful of the RUU you are running and that it will play nice with your phone.
What is an OTA?
OTA stands for Over The Air and implies an Over the air update distributed by your phone manufacturer, carrier or ROM developer. Unlike an RUU, an OTA will not typically wipe/factory reset your phone but can update your firmware and/or software set. To a apply a manufacturer/carrier released OTA you will need stock recovery and stock system apps installed. Your CID/MID must match that of the carrier/manufacturer your phone came from.
What is a ROM?
When the term ROM was first introduced it stood for Read Only Memory, however, most memory that claims to be Read Only nowadays is not like it was back then. Now a days it is not as complicated to write ROM as only permissions are in your way as opposed to the days when you were required to modify the hardware layer in some way to update the ROM chip. In this particular case, we are referring to the android software on your phone. Stock ROM would imply the manufacturer released ROM that came on your device when you purchased it. Custom ROMs are ROMs the are modified stock ROMs or ROMs built from android source code to. I think you get the idea. It's the device software or Operating System if you will. You should never flash a ROM that is not intended for the device you are flashing it to, this is very dangerous. Like, brick dangerous.
What is a nandroid backup?
A nandroid backup is a backup of your phone's current state. Like a snapshot or image of your phone's software. It includes the ROM currently flashed to your phone, the kernel, apps and settings. It does not include any firmware files other than the kernel and possibly the recovery. A nandroid is done with custom recovery and cannot be done with stock recovery. Taking a nandroid before you start messing with your phone is good practice. In fact, It's good practice to make nandroids before flashing a new ROM, or making any changes that may impact stability. This will ensure you always have a quick way to get back to having a usable phone. Obviously, a nandroid will not help in cases where you mess up firmware files like the radio firmware or hboot.
What is a kernel?
The kernel is the central point of an operating system. It contains the modules and settings necessary for the ROM or OS to work properly. Every Operating System has a kernel, including android. Just like ROMs there are custom kernels, with tweaks and the like that may improve or decrease performance/stability. Also, like ROMs, you should never flash a kernel not intended for your device. Very Dangerous!
What is a bootloader?
The bootloader is as the name implies, a device software/interface for handling boot operations it is contained within the hboot file. The bootloader screen has a few nifty features:
Gives you device information such as:
The bootloader state (locked, relocked or unlocked)
The Secureflag state (S-On or S-Off)
Your hboot and radio versions
Your Cid (only if you changed it)
Allows you to power down, reboot or boot your phone to android.
Allows you to factory reset your phone (Though should never really be used unless you are completely stock as you can properly factory reset in custom recovery)
Allows you access to the recovery
It gives you access to fastboot command operations you can send from your PC to your phone.
To boot to bootloader: Press and hold Power and volume up until the phone shuts off, then let go of power and volume up. Press and hold Volume down until your screen comes up in bootloader mode.
What is recovery?
Recovery is a software/User Interface that allows you to handle and make changes to your device, without having to boot the android OS. The stock M8 comes with a recovery that is quite limited but allows you to factory reset your phone and flash OTA updates which really is more than enough for the average user.
Those of us who want more from our phones, and modify them tend to flash custom recoveries with many extra features. I won't go into all the features they provide as the devs have websites, and you can visit them for more information. The two custom recoveries for the m8 include TWRP and Philz Touch. Both are very functional and choosing one is a matter of preference over anything else.
To flash a recovery image. Put the recovery image in your fastboot/adb folder and in the command prompt:
Code:
fastboot flash recovery recoveryfilename.img
You can find The latest:
TWRP for the M8 HERE
Philz Touch for the M8 HERE
To manually boot to recovery, boot to bootloader (Press and hold Power and volume up until the phone shuts off, then let go of power and volume up. Press and hold Volume down until your screen comes up in bootloader mode). Then select recovery in the bootloader menu.
What is S-Off/S-On?
This stands for Securewrite-on or Securewrite-Off. The name kind of gives some hints as to what it means. Having your bootloader unlocked, affords you the ability to to flash a custom recovery and custom roms as well as a custom kernel however, some people may need more. They may want to alter other system partitions. That is where S-Off comes in. It gives you full write access to all system partitons. It also forces a bypass for all security checks, such as those made by OTAs and RUUs, for CID and MID. S-Off is persistent. No matter if you RUU, OTA, Flash a ROM, Firmware, Factory Reset, S-Off will remain so until you use fastboot to reset the flag. I should say, if you don't know what you're doing, that is to say, if you are the type to follow instructions blindly on a thread, without much idea what is ACTUALLY Happening, what files you're modifying, you should not have S-Off. It should not concern you and that is that. S-Off can be dangerous. You have been warned.
What does a Factory Reset do?
A Factory Reset Clears the Cache, Dalvik Cache and Data Partitions. All settings will reset to default. User Apps (Apps you installed that did not com preinstalled with the ROM) will be removed. This will not restore your phone to when you purchased it. This will not relock your bootloader, Reset the S-Off flag, remove root, or downgrade your hboot. It merely affects the system and user settings and user apps.
What is fastboot?
Fastboot is a command line tool that allows you to manipulate certain parts of your phone from the bootloader. Your phone must be in fastboot mode and you must have the fastboot application and HTC drivers installed if you are on Windows. If you are on linux, the HTC driver is preinstalled.
Popular fastboot commands include:
Fatsboot devices (Lists devices connected for use with fastboot)
Fastboot flash recovery recovery.img (Flashes a recovery image)
Fastboot flash boot boot.img (Flashes a boot image)
Fastboot oem readcid (Shows the CID of the phone installed)
Fastboot oem writecid (Writes a new CID to your phone. Must be 8 Characters. Requires S-Off)
Fastboot oem rebootRUU (Puts the phone in RUU mode which is used for flashing firmwares and/or entire RUUs)
Fastboot reboot (Reboots your phone)
Fastboot reboot-bootloader (Reboots to bootloader)
Fastboot erase cache (Wipes the cache partition using fastboot. Good idea after flashing things via fastboot)
Fastboot help (Will list fastboot commands)
Fastboot boot imagefilename.img (Allows you to boot a recovery image or kernel image without actually flashing to your phone
allowing you one time access to the features without the headache of reflashing stock afterwards) Thanks to @garyd9 for suggesting I include this. Very convenient command.
What is ADB?
ADB is another command line tool used to manipulate your phone. The commands for ADB are way more extensive. ADB can only communicate with your phone while in a custom recovery or while the ROM is booted up with USB debugging turned on. The reason ADB is so much more extensive is because it allows you to remotely access your phone's terminal just like a linux terminal. You can use ADB to push or pull files to and from any partition (Some partitions will require S-Off), list devices, get a logcat, troubleshoot issues etc etc. For an extensive list of commands and how to use ADB I strongly suggest visiting http://developer.android.com/tools/help/adb.html
What is the CID?
CID stands for carrier ID. It's a string of letters and numbers, eight characters long that identify what carrier your phone is from. When you flash an OTA or RUU, The OTA or RUU checks for a few things, one of those things is the CID, to ensure you are flashing software intended for your device. Realistically, There's no hardware difference between the M8s (with the exception of CDMA vs GSM) so all firmwares/softwares should be compatible. With regards to radio firmware, your radio may function better with one firmware over another. There have been occasions with HTC where flashing an RUU or OTA with the wrong CID or SuperCID, while S-On would brick your phone. So try to be mindful of this and be careful.
Thanks to @garyd9 for suggesting I include this in my guide!
Some common CIDs include but are not limited to:
SuperCID: 11111111
HTC International: HTC__001
AT&T: CWS__001
ROGERS: ROGER001
VODAPHONE: VODAP001
T MOBILE: T-MOB010
TELESTRA: TELST001
Bell Canada: BM___001
What is a brick?
The term brick is sometimes thrown around a bit too casually. A brick is when your phone is no longer operable. It does not boot, there is no way to save it without resorting to Jtagg or replacing the nand chip or motherboard. If your phone powers on and something appears on your screen, your phone can almost always be saved. Be sure you know how to save your device before messing with your device.
Troubleshooting Common Issues
I flashed a ROM or Kernel and it's not booting! WHAT DO I DO!?
When this happens. There are actually a number of things to consider but first off, Hopefully you made a nandroid to restore from just in case the reason it doesn't boot is something not quickly or easily fixed.
1. Is the ROM you're flashing indeed intended for your device? ROMs you're flashing should be for the HTC One m8 International. You should not be flashing ROMs designed for the m8 Sprint or Verizon and should not be flashing ROMs designed for other models of phone. If the ROM you flashed is not for your device, best case scenario, it's not flashing properly. Worst case scenario, you have a brick. You will need to factory reset and wipe system then either flash a new ROM or restore a nandroid to get your phone up and running again.
2. Did you wipe Cache, Dalvik Cache, Data and System? (Don't wipe System for Kernel Install)
A factory reset will wipe all but system. You should wipe System manually in case the script for the ROM install does not do it or does it improperly. A factory reset is enough for a Kernel install. If you wiped system and just flashed a kernel, it's no doubt your phone is not booting.
* If you did not factory reset and wipe system, do so and then reflash your rom. It should then boot.
* If you wiped system to flash a kernel, you will need to reflash the rom, and then reflash your kernel again if you are flashing a custom kernel. (Note a GPE Kernel will not work on Sense and a Sense kernel will not work on GPE.
3. Did you matchup the Checksum? MD5 or SHA1 are usually posted on the ROM Download site/post. This allows you to check and make sure the integrity of the file you downloaded has been maintained. If The SHA1 or MD5 of the file you downloaded does not match what is posted, you have a corrupted file and should redownload. If you don't have a MD5 or SHA1 Checker, I suggest downloading one. Google MD5 or SHA1 Checker and you should find one. MD5 is most commonly used but it's up to the Dev as to which they post. Sometimes both. You only need to match one. (Linux comes with utilities for checking MD5/SHA1 called md5sum and/or sha1sum)
4. If you tried all these steps and it's still not booting, try another ROM. If no ROMs appear to be booting, you may be having an issue with your custom recovery. Redownload your recovery (Make sure it's the right one for your phone and check the checksum) Then reflash recovery, then use fastboot erase cache, boot to recovery and try flashing again.
5. If you tried all these and you're having issues, ask in the M8 Q&A!
I wiped everything and I don't have a ROM on my phone to flash! What do I do?
This is quite simple really.
Boot to recovery
Connect your phone to your PC
Make sure your ROM is on your PC and in your adb folder
Then use:
Code:
adb push romfilename.zip /sdcard/
Be patient, this could take a while, when it finishes you will get a confirmation with bytes in/bytes out.
Then flash.
Where can I go to find links to do all this cool stuff I want to do to my Phone!?!?!?!?
HERE!
Thank Yous!
Thanks to @garyd9
Thanks to @keithross39
This is a work in progress. I will be updating this as often as I can, trying to explain as much as I can for newer M8 owners who are not used to HTC or Android devices. If you have any suggestions for what I can put here, post here and let me know! Also, I'm not perfect, I make mistakes if I have/do make any, do not be shy! Let me know.
[08/18/2014] Partially updated and fixed spelling mistakes. More coming soon!
Hey fella, this is a good idea.
Thanks for taking the time to do this.
I am going to be getting the M8 in the near future, so reading up about the HTC specific stuff is really useful for me as I'm currently familiar with Samsung procedures and not a lot else. Most folks reading this should be familiar with the 'cross platform basics', so what you've covered so far should be enough........
But.....
Those (like me) who are getting an HTC device for the first time would probably benefit from more of a detailed description of the HTC side of things......maybe you could concentrate on expanding that information.......
Maybe you could include links to threads for s-off, rooting and/or anything else relevant?
Just my 2 cents worth....for what it's worth.....
Sent from my rooted debloated thingy
keithross39 said:
Hey fella, this is a good idea.
Thanks for taking the time to do this.
I am going to be getting the M8 in the near future, so reading up about the HTC specific stuff is really useful for me as I'm currently familiar with Samsung procedures and not a lot else. Most folks reading this should be familiar with the 'cross platform basics', so what you've covered so far should be enough........
But.....
Those (like me) who are getting an HTC device for the first time would probably benefit from more of a detailed description of the HTC side of things......maybe you could concentrate on expanding that information.......
Maybe you could include links to threads for s-off, rooting and/or anything else relevant?
Just my 2 cents worth....for what it's worth.....
Sent from my rooted debloated thingy
Click to expand...
Click to collapse
Thanks man! I welcome all suggestions! I will do my best to incorporate your suggestions
Sent from my HTC One_M8 using XDA Free mobile app
Great idea, thanks. I've been wondering what S-Off is for weeks but didn't want the flaming for asking a noob question!
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Some possible additions:
What is "RUU"?
What is MID (model ID) along with a list of some common MID's
What is CID (carrier ID?) along with a list of some common CID's
How do the MID and CID relate to each other and how does the combination relate and/or interact with RUU. Related, of course, is the third part of the version number.
I was thinking of writing a guide myself, because I was so confused myself after coming from samsung, really nice.
Shebee said:
I was thinking of writing a guide myself, because I was so confused myself after coming from samsung, really nice.
Click to expand...
Click to collapse
Lol...ain't that the truth....
Sent from my rooted debloated thingy
Nice one
Very well done!
Sent from my HTC One_M8 using Tapatalk
I'm one of those who also came from Samsung (S4).
This is really great and easy to understand. This should be sticky :victory:
While I think the OP uses the term "ROM" incorrectly (Read Only Memory), I'll admit that's just me being picky. Otherwise, a very useful post... I've requested it be made sticky.
Take care
Gary
garyd9 said:
While I think the OP uses the term "ROM" incorrectly (Read Only Memory), I'll admit that's just me being picky. Otherwise, a very useful post... I've requested it be made sticky.
Take care
Gary
Click to expand...
Click to collapse
That's not being picky at all! Feel free to suggest any corrections. I welcome criticism and corrections.
Thanks for the recommendation!
Sent from my HTC One_M8 using XDA Free mobile app
exad said:
That's not being picky at all! Feel free to suggest any corrections. I welcome criticism and corrections.
Click to expand...
Click to collapse
LOL. I'm one of those people who goes nuts when people want to install "ROM's" on their phone. I keep reminding them that if it was really "Read Only Memory", that they wouldn't be able to overwrite it. Ever.
I do understand, however, that it's one of the misused terms these days. I guess it's kind of like saying you are "dialing a phone number." (There aren't any dials on our phones anymore. I haven't even seen a working rotary dial phone in years...)
Anyway - I'll stop with my OT bantering. Once I get more familiar with HTC devices I'll probably have some good suggestions for your posts.
Take care
Gary
garyd9 said:
LOL. I'm one of those people who goes nuts when people want to install "ROM's" on their phone. I keep reminding them that if it was really "Read Only Memory", that they wouldn't be able to overwrite it. Ever.
I do understand, however, that it's one of the misused terms these days. I guess it's kind of like saying you are "dialing a phone number." (There aren't any dials on our phones anymore. I haven't even seen a working rotary dial phone in years...)
Anyway - I'll stop with my OT bantering. Once I get more familiar with HTC devices I'll probably have some good suggestions for your posts.
Take care
Gary
Click to expand...
Click to collapse
Read only memory isn't a great name for it. If you've ever updated the bios on a pc, flashed a firmware update to a router, etc... you've written to read only memory. There are types that are truly read only but I can't think of a single practical example. And welcome to htc phones!
Sent from my HTC One_M8 using Tapatalk
lampel said:
Read only memory isn't a great name for it. If you've ever updated the bios on a pc, flashed a firmware update to a router, etc... you've written to read only memory. There are types that are truly read only but I can't think of a single practical example. And welcome to htc phones!
Click to expand...
Click to collapse
I'm old enough to remember (clearly) when you couldn't update the BIOS on a PC - you had to physically replace the BIOS chip. (Usually, they were socketed to make replacement a bit easier.) That was ROM. Also, early game consoles used true ROM in cartridges.
As for current practical example: a simple CDROM (not CD/RW) is, of course, read only.
I agree that it's not the best name lol but that is what it stands for....
Sent from my HTC One_M8 using XDA Free mobile app
Added this to my index thread
Hi guys! I am planning to buy an htc one m8 but can someone please tell me the different models out there? I don't want to end up buying the wrong one. Also is the dev one worth spending the extra money over the international? And is it the same model as the international one? Thanks in advance. I didn't know where else to post this. I didn't wanted to start a new thread.
Karan and all other users, please post questions in Q&A. Only things that should be posted here are suggested additions to this thread.
Also thread has been updated and more to come!
Part on RUUs is wrong...
An RUU can be run at any point and in any state (so long as you can get to the bootloader) as it completely replaces the entire system so doesn't matter if you don't have the stock recovery as it replaces it during the update process. Also, if you're S-OFF it means you can flash any RUU for any phone, handy to go between branded and unbranded software. OK, there's a risk of trying to flash an RUU from another device but if you do that you're a bit dumb!!
Hello.
I try to make ENG-boot file from ENG ROM (combination)
I uncompress Combination File and take sboot.bin , boot.img file to make .tar
And I flash that file show adb enable message but phone is Infinite boot
Then stuck in samsung galaxy S8 LOGO
How can I make adb enable file
Model : korea g950
jumam21 said:
Hello.
I try to make ENG-boot file from ENG ROM (combination)
I uncompress Combination File and take sboot.bin , boot.img file to make .tar
And I flash that file show adb enable message but phone is Infinite boot
Then stuck in samsung galaxy S8 LOGO
How can I make adb enable file
Model : korea g950
Click to expand...
Click to collapse
Why dont you flash with odin? Easier plus you can easily select a suitable firmware package from one of the sites?
Sent from my SM-G950U1 using Tapatalk
Re
rudimenta said:
Why dont you flash with odin? Easier plus you can easily select a suitable firmware package from one of the sites?
Sent from my SM-G950U1 using Tapatalk
Click to expand...
Click to collapse
I mean How can I make ADB enable file from combination File.
jumam21 said:
I mean How can I make ADB enable file from combination File.
Click to expand...
Click to collapse
Exynos? I hope so because there is no sboot file for snapdragon ?
You don't need the factory boot for exynos. Just enable OEM unlocking
partcyborg said:
Exynos? I hope so because there is no sboot file for snapdragon
You don't need the factory boot for exynos. Just enable OEM unlocking
Click to expand...
Click to collapse
He most likely cannot access that due to having his phone google locked. If that is the case. More than likely is by what he is asking. There is a program called FRP Hijacker by Hagard that allows making an adb enabled boot.img but it never works for me at least on newer android OS 7+. Havent checked logs yet to see why. The file flashes fine but of course is not adb enabled. Im thinking signing and other issues. for some. If anybody knows a solid way please post here. I am researching so probably will find my solution soon i hope.. Reason for the need that most have is due to not having a combination file (engneering firmware) for a certain device to pull the boot.img or boot.img + system.img to flash when enabling ADB and settings on a specific binary Samsung FRP (Google Locked) device.
noidodroid said:
He most likely cannot access that due to having his phone google locked. If that is the case. More than likely is by what he is asking. There is a program called FRP Hijacker by Hagard that allows making an adb enabled boot.img but it never works for me at least on newer android OS 7+. Havent checked logs yet to see why. The file flashes fine but of course is not adb enabled. Im thinking signing and other issues. for some. If anybody knows a solid way please post here. I am researching so probably will find my solution soon i hope.. Reason for the need that most have is due to not having a combination file (engneering firmware) for a certain device to pull the boot.img or boot.img + system.img to flash when enabling ADB and settings on a specific binary Samsung FRP (Google Locked) device.
Click to expand...
Click to collapse
Frp bypass is not a kosher topic here as it's most common use case is to unlock stolen hardware. If that is his problem he should either give the phone back to its original owner, it if it's his account go through the password recovery process with Google
partcyborg said:
Frp bypass is not a kosher topic here as it's most common use case is to unlock stolen hardware. If that is his problem he should either give the phone back to its original owner, it if it's his account go through the password recovery process with Google
Click to expand...
Click to collapse
This has also been told to me by a mod ive spoke with time to time but the others really don't seem to mind as long as it is to help others and such. Which is what i do when i put up a manual tutorial. I usually do all by freestyling (no looking into anything unless really needed). If the same PartyCyborg from Android Forum Community. We don't know each other but I have used your work past and present and had a swell time finding through archives but this i enjoy. Very cool work man esp the last bit i asked you about on i believe an older Samsung 2014? device to action with your Rom's latest. Alright back to AndroidForum Community I have explained my whole outlook & debated the whole FRP issue with phones today. It's a challenge and it's helpful to those that aren't running masses of stolen phones through boxes (hey even stolen hardware once seized returns back to the community and has to be delt with.. i as do others get some devices from LEA property) and also that huge majority of people who quickly create accounts without jotting down and remembering info. Then i could go back into bulk onto stores who legally obtain (auction for example) then have to either a) find a way to fix frp and or 2) resell these devices 3) part out as google locked LB's etc. Google Lock and FRP in general is a VERY good thing IMHO. I want to see us make a move to more secure reliable FRP locks such as iClouds. We also have a security section here on XDA where all sorts of the latter and even deeper is discussed. Win Win for Security overall if you think about it all and take it in. I've said this before in other Areas of the internet I am from and I will say it again in similar words "they build it, we bypass it, they improve it.......(reversing.. updating.. learning.. phase) and the process continues.". We are improving security on everything be it my old days email filters (especially the old ways) or be it Google Lock Security & FRP and the countless other companies small and big across the globe with related protection put in place. Don't put a dark hat on it all.. at least just yet. -not directed toward you by any means or anyone else.. just my quickie worth of that whole 2 cents for what its worth.
Hello, thank you very much for reading, I hope you can help me. I need one or more files to be able to recover my phone: Samsung Galaxy S7 Active.
These are the files that I need:
prog_emmc_firehose_8996.mbn (.elf)
rawprogram0.xml
patch0.xml
I do not know if I would also need these:
MPRG8996.hex
rawprogram_unsparse.xml
I think these files are the same as prog_emmc_firehose_8996.mbn (.elf):
8996_msimage.mbn
MSM8996.mbn
How did I make a brick my phone? Installing the first official version:
SM-G891A_G891AUCU1APG7_ATT_Full_Repair_Frimware
Previously I used this version without any problem:
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT
I wish someone could help me, I have read more than 50 pages, but I have not been able to solve the problem.
Please.
Can anybody help me?
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
yakine13 said:
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
Click to expand...
Click to collapse
I hope someone helps us.
HEY!
I found a way!!!
...for me:/
why you want this emmc_firehose_8996.mbn?
actually, i think that you don't need that file especially, it doesn't exist from where i've searched.
if it's to flash your phone all you need is odin and a flashable file of your phone firmware
i had a zuk z2 pro and was locked with frp when i wanted to setup custom rom AOSP 9.0.0 for example.
but i managed to unlock it by flashing a custom rom without gapps in the first place to no get locked out.
tell me how your phone is reacting, what do you have access to, and your initial step before brick
yakine13 said:
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
Click to expand...
Click to collapse
yakine13 said:
HEY!
I found a way!!!
...for me:/
why you want this emmc_firehose_8996.mbn?
actually, i think that you don't need that file especially, it doesn't exist from where i've searched.
if it's to flash your phone all you need is odin and a flashable file of your phone firmware
i had a zuk z2 pro and was locked with frp when i wanted to setup custom rom AOSP 9.0.0 for example.
but i managed to unlock it by flashing a custom rom without gapps in the first place to no get locked out.
tell me how your phone is reacting, what do you have access to, and your initial step before brick
Click to expand...
Click to collapse
Hello, sorry for my bad English. My phone is a Samsung Galaxy S7 Active (SM-G891A). I will try to explain what happened.
I had this version of Android 6 installed (via Odin) on the phone:
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT
With that version my phone was fine, but then I tried to install the first version of Android 6 (official) via Odin:
SM-G891A_G891AUCU1APG7_ATT_Full_Repair_Frimware
When the installation was completed (Odin said the installation was successful), the phone never restarted. There is no way to turn it on with any combination of buttons, nor with a microSD with a debrick.img. A USB JIG has not worked for me either.
Windows detects my phone in Qualcomm 9008 mode. Odin does not detect it.
did you find a solution?
actually it look like to be a hard brick but as it's snapdragon 820 you can recover from it
I'm waiting for the day when noobs and half-noobs (no offense, all of us have been there) will start reading before writing and stop assuming that their 1st aid kit will revive a kitten ran over by a train.
It's okay not to know, but before writing a spam reply, just consider for a second that the user already tried your solution and is already a step ahead.
Listen guy, go to Halab Tech. They have certain firmwares for what you need, but they ask money.
Those type of firmwares have a prefix "DEBUG_EMERGENCY_DOWNLOAD_FA....'
In my case it's "DEBUG_EMERGENCY_DOWNLOAD_FA70_G955U1SQU6ASG1_CL12542406_QB24669289_REV00_user_mid_noship_MULTI_CERT.tgz"
As I consider that a bastard move (since they are selling Samsung's intellectual property as their own, stuff that should be public in the first place), I encourage you to share the files if you buy them, so that we can all use them and screw over these monopoly playing-intellectual property stealing bastards.
I'm now working on a recovery of my G955U1 (S8+ Qualcomm USA). I paid $25 for a god damn firmware and I'm gonna post it in next couple of days.
I'm personally having trouble of flashing the firmware (because not many flash tools support flashing .elf flash loaders), but I used one FRP tool (Octoplus FRP tool) to check the loader and it managed to send it, receive the "hello" packet, read partitions and erase the FRP partition (I assume it worked by the log), but I don't have a way to flash other partitions yet.
You people should have in mind one thing: even though certain devices have the same chipset, doesn't mean that you can use the same firehose flash loader, since manufacturers create different loaders for them and write their digital signatures into the chip (don't know is it hardwired or flashed), meaning that you cannot use Xiaomi's prog_ufs_firehose_8998_ddr.elf (just an example) to flash a Samsung device with MSM8992 chipset.
In fact, I think that each phone model and possibly even it's different firmware revisions have unique loaders, since I didn't manage to get a successful response from my G955U1 by sending G955U2 loader, and the loader which I managed to send is actually stated to be for G955U1U6 (U6 is the bootloader revision number, while U1 is the part of the model number).
Best of luck, contact me if you need help.