Is it possible to flash american CID via bmm instead of the original uniqe cid of my xt910?
It will help people to flash the update via stock recovery without any need to bmm...
Only pushing the kernel and flash.
thanks... :highfive:
if its possible, can someone who handle xt912 backup his CID and upload it?
UduBobo said:
Is it possible to flash american CID via bmm instead of the original uniqe cid of my xt910?
It will help people to flash the update via stock recovery without any need to bmm...
Only pushing the kernel and flash.
thanks... :highfive:
if its possible, can someone who handle xt912 backup his CID and upload it?
Click to expand...
Click to collapse
AS long i know, CID is a unique customer identification...
YOu can't use someone else cid ; unless the person wants to give information about its phone to you (i think i'm not sure)
What you want to do ? Flash to JB ?
pablobhz said:
AS long i know, CID is a unique customer identification...
YOu can't use someone else cid ; unless the person wants to give information about its phone to you (i think i'm not sure)
What you want to do ? Flash to JB ?
Click to expand...
Click to collapse
yes, and remove all the CID FAIL thing.
Got it.
Well, i don't think someone will upload a cid for you - as i said it's a personal unique number.
You don't have any backup ?
If u don't... Get used to boot trough bp tools...
Sent from my MOTOROLA RAZR using xda app-developers app
Don't get troubled, and go the safe way!
Install bmm 0.3.4, backup CID, erase CID, flash kernel from bmm, flash baseband (optional), enjoy; but you knew that already.
bmm 0.3.4 gets its way to avoid bp tools so no worries there with CID error.
It is already as easy as it needs to be :good:
PS.: from my understanding the CID is attached to chipset's imei so you can't put whatever CID you want; just your device's one, maybe this answers your question.
osval. said:
Don't get troubled, and go the safe way!
Install bmm 0.3.4, backup CID, erase CID, flash kernel from bmm, flash baseband (optional), enjoy; but you knew that already.
bmm 0.3.4 gets its way to avoid bp tools so no worries there with CID error.
It is already as easy as it needs to be :good:
PS.: from my understanding the CID is attached to chipset's imei so you can't put whatever CID you want; just your device's one, maybe this answers your question.
Click to expand...
Click to collapse
I didn't knew about this trick
Thanks
Just remember to flash "JB kernel-based roms" ONLY right after flashing kernel, otherwise it will not boot, if you want to get back to ics you must flash an ICS kernel to boot, you can backup your kernel before flashing the jb kernel but with erased cid you can flash any ics kernel if you forgot to do that
the safer bet will be keeping your stock ics on main system, an do all the flashing stuff in 2nd system (must activate first, there are tutorials for that) so you can easily come back flashing ics kernel and switch to system 1 if anything goes wrong.
Related
I was looking through mbm.bin file and i have noticed some checks on the cid, where the cid is of 2types
1.Consumer phone normal razr on wich only the phone region software can be flashed/or boot normaly
2.Non consumer/developer cid.
Can someone with a developer razr copy the cid to a normal razr to see if kernels from another region can be flashed?
If this sounds like a stupid ideea please close the thread.
Killer2k8 said:
I was looking through mbm.bin file and i have noticed some checks on the cid, where the cid is of 2types
1.Consumer phone normal razr on wich only the phone region software can be flashed/or boot normaly
2.Non consumer/developer cid.
Can someone with a developer razr copy the cid to a normal razr to see if kernels from another region can be flashed?
If this sounds like a stupid ideea please close the thread.
Click to expand...
Click to collapse
It's definitively not a stupid idea but it's in wrong section. That's for sure.
Anyway. This can be done by DD or CAT, but I think it'll force devs to push their's phone ID and I'm not sure any dev will want do it.
Cheers
AFAIK, RAZR Developer Edition CID partition is empty.
no need to ask someone to do the dump. Just backup & erase yours.
It will make your phone accept any region ROM. But you need to boot by bp-tools each time.
Disclaimer : I only own the locked down type
Moved To Q&A
Please post questions in the Q&A section
Hello everyone
I hope someone can help me with this.
I have signal issues with my device, htc one x+, and thinking of sending it back as is still under warranty.
I have the revolution firmware on it and want to know how I can effectively set the original firmware on it so that I can then send it back.
Thank you
cpu2007 said:
Hello everyone
I hope someone can help me with this.
I have signal issues with my device, htc one x+, and thinking of sending it back as is still under warranty.
I have the revolution firmware on it and want to know how I can effectively set the original firmware on it so that I can then send it back.
Thank you
Click to expand...
Click to collapse
Depending on your devices bootloader (HBOOT) version and CID, you may be able to use an RUU to get back stock easily. If there's no matching RUU for your phone, you will have to search for stock backups and recovery matching your CID in order to apply stock HTC rom/firmware/recovery.
What is your bootloader version and CID?
reaper90 said:
Depending on your devices bootloader (HBOOT) version and CID, you may be able to use an RUU to get back stock easily. If there's no matching RUU for your phone, you will have to search for stock backups and recovery matching your CID in order to apply stock HTC rom/firmware/recovery.
What is your bootloader version and CID?
Click to expand...
Click to collapse
I don't know how to find the bootloader.
I found the CID using CID getter from the play store.
it shows it as : HTC__001
cpu2007 said:
I don't know how to find the bootloader.
I found the CID using CID getter from the play store.
it shows it as : HTC__001
Click to expand...
Click to collapse
reboot into bootloader (power off your phone and then press and hold power & volumedown button) there you can see your version number. If i remember right you need version 1.35 or lower to use a RUU, or your phone has to be S-OFF.
reaper90 said:
reboot into bootloader (power off your phone and then press and hold power & volumedown button) there you can see your version number. If i remember right you need version 1.35 or lower to use a RUU, or your phone has to be S-OFF.
Click to expand...
Click to collapse
This is what I see in the screen
Unlocked
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.30.0000
CPLD-None
MICROP-None
RADIO-3.1204.167.31
eMMC-bootmode:disabled
CPU-bootmode: disabled
HW secure boot:enabled
MODEM PATH: OFF
I've tried the following commands
adb bugreport | find "bootloader"
and I got this
6 un.ofs=362 androidboot.engid=0x
[ro.boot.bootloader]: [1.30.0000]
[ro.bootloader]: [1.30.0000]
http://www.androidruu.com/index.php?developer=ENRC2B
download the 1.17.401.1 RUU, it should work on your device. Make sure you backup all your stuff before using it, this will erase everything on your phone!!
reaper90 said:
http://www.androidruu.com/index.php?developer=ENRC2B
download the 1.17.401.1 RUU, it should work on your device. Make sure you backup all your stuff before using it, this will erase everything on your phone!!
Click to expand...
Click to collapse
Thank you, what information you've used to decide what RUU to use?
is that because 1.17 is the latest version and because they bootloeader and cid I've given you tell you that my phone is european and factory unlocked?
In addition:
I'm aware of a few methods that can be used to backup: Titanium,through adb,clockworld twrp but none of these does a full complete backup.
What's the best way to back up all the date so that all my messages,contacts,apps settings and messages(viber,skype logs and chats) can be restored once I have installed the stock firmware.
Can you also point out a simple guide that shows me how to install the stock firmware?
Thank you
cpu2007 said:
Thank you, what information you've used to decide what RUU to use?
is that because 1.17 is the latest version and because they bootloeader and cid I've given you tell you that my phone is european and factory unlocked?
In addition:
I'm aware of a few methods that can be used to backup: Titanium,through adb,clockworld twrp but none of these does a full complete backup.
What's the best way to back up all the date so that all my messages,contacts,apps settings and messages(viber,skype logs and chats) can be restored once I have installed the stock firmware.
Can you also point out a simple guide that shows me how to install the stock firmware?
Thank you
Click to expand...
Click to collapse
HTC__001 is a so called WWE (world wide edition) cid and i mostly read about people in europe having this, don't know what country exactly. and RUU is bound to certain cid and we only have those few RUUs for this device, so if someone does not have a matching cid for those RUUs you aren't able to use them. Also (as you've seen) your phone's bootloader is S-ON (Security-ON) like most people here have it, which means we're not allowed to do everything with our phones, for example we can't flash boot.img in recovery and we can't downgrade our bootloader version. This is the reason why i needed to know your bootloader version because the latest RUU we have is this 1.17.401.1 which includes bootloader 1.35 if i remember right. So if you had version 1.40 you wouldn't be able to use it because you can't downgrade bootloader version.
As for backup: I use titanium backup for all my user apps and app data (settings, savegames, chats, ...) and SMS Backup & Restore for sms backup.
But you also will need root to restore those backups.
To use the RUU, simply connect your phone to your computer and execute it. It should guide you to the process.
reaper90 said:
HTC__001 is a so called WWE (world wide edition) cid and i mostly read about people in europe having this, don't know what country exactly. and RUU is bound to certain cid and we only have those few RUUs for this device, so if someone does not have a matching cid for those RUUs you aren't able to use them. Also (as you've seen) your phone's bootloader is S-ON (Security-ON) like most people here have it, which means we're not allowed to do everything with our phones, for example we can't flash boot.img in recovery and we can't downgrade our bootloader version. This is the reason why i needed to know your bootloader version because the latest RUU we have is this 1.17.401.1 which includes bootloader 1.35 if i remember right. So if you had version 1.40 you wouldn't be able to use it because you can't downgrade bootloader version.
As for backup: I use titanium backup for all my user apps and app data (settings, savegames, chats, ...) and SMS Backup & Restore for sms backup.
But you also will need root to restore those backups.
To use the RUU, simply connect your phone to your computer and execute it. It should guide you to the process.
Click to expand...
Click to collapse
Thank you for explaining.
So I understand that if there's no a compatible RUU, it will not be possible to downgrade to the stock firmware, does this mean that after using custom rom, if I endup with a higher bootloader, I can't get back to my stock firmware but only change from one custom to another custom rom?
Where do these RUU come from? aren't they supplied by HTC, I mean if someone has a device with stock firmware but want's to flash his/her phone again, how would they do it? (for example in iphones you can get stock firmware for every phone)
Is it there a way to create a RUU when I have a stock firmware so that in case I need to revert back I can use that?
I'm on version 4.1.1 i guess, which i think isn't the latest version, after going stock firmware, if I upgrade, will i get my bootloader upgraded too?
sorry for too many questions
cpu2007 said:
Thank you for explaining.
So I understand that if there's no a compatible RUU, it will not be possible to downgrade to the stock firmware, does this mean that after using custom rom, if I endup with a higher bootloader, I can't get back to my stock firmware but only change from one custom to another custom rom?
Where do these RUU come from? aren't they supplied by HTC, I mean if someone has a device with stock firmware but want's to flash his/her phone again, how would they do it? (for example in iphones you can get stock firmware for every phone)
Is it there a way to create a RUU when I have a stock firmware so that in case I need to revert back I can use that?
I'm on version 4.1.1 i guess, which i think isn't the latest version, after going stock firmware, if I upgrade, will i get my bootloader upgraded too?
sorry for too many questions
Click to expand...
Click to collapse
Bootloader version is not rom version, custom roms won't update your bootloader. There's a difference between "firmware" and custom rom. you can update your phones firmware (bootloader etc.) with a cid matching "firmware.zip" from an OTA or RUU or on stock this is done automatically when applying OTA updates that include new versions of those. So if your bootloader version was too high, you can't use the RUU anymore and you have to get back to stock by using a stock TWRP/CWM backup and additionally flash stock recovery and boot.img and then relock your bootloader.
and yes RUUs are made by HTC, but there are no RUUs for latest software updates yet. either they don't exist or they're not leaked...
Your bootloader will probably be updatet to 1.35 if i remember right, but as long as the RUU includes the same version or a higher one, you're able to use it, so you can still use this RUU when used once.
just don't do OTA update to Sense 5/Android 4.2.2 or your bootloader will be upgraded to 1.72 and you won't be able to use any of those ruu again.
I just forgot one thing, I have linux at home, it's not possible to update through linux as it's an exe file.
is it there an alternative?
cpu2007 said:
I just forgot one thing, I have linux at home, it's not possible to update through linux as it's an exe file.
is it there an alternative?
Click to expand...
Click to collapse
I'm sry, as far as i know there's no way for RUU on linux. But i think i remember seeing a guide (either here at some xda forum or somewhere else on the internet) with a description on how to extract the stock rom and firmware.zip (which includes stock boot.img and recovery) from a RUU. So you could flash stock rom, boot.img and recovery and then relock bootloader, which should have the same effect. But i think you will need windows here too...
After running the RUU, it asked me to update the image, however it fails and it stays on the HTC black screen.
I've searched around and the way to install the RUU is to run it until the wizard windows open, search the temp folder and and a file in it called rom.zip.
extract the recovery or recovery_signed file from it and use fastboot command on the phone.
However when I try to extract the recovery_signed file, winrar says it's corrupt
how can I solve this or is it there another way to install the stock firmware?
my bad I had to fastboot oem lock
back to stock ,thank you!
is it there anything else I need to do in order to make sure that my phone is in the warranty guideline( i mean softwarewise)
Now I have got the phone fixed hopefully.
The phone details are as [email protected]
HTC ONE X+
android v: 4.2.2
htc sense version: 5.0
software num: 2.18.401.2
htc sdk api level: 5.41
How can I make a full backup of this stock firmware so if I decide to go back after using some custom firmwares, I can do so by restoring it back.
THank you
cpu2007 said:
Now I have got the phone fixed hopefully.
The phone details are as [email protected]
HTC ONE X+
android v: 4.2.2
htc sense version: 5.0
software num: 2.18.401.2
htc sdk api level: 5.41
How can I make a full backup of this stock firmware so if I decide to go back after using some custom firmwares, I can do so by restoring it back.
THank you
Click to expand...
Click to collapse
- unlock bootloader
- install custom recovery (CWM/TWRP)
- nandroid backup (all partitions)
You can restore this any time you need. Don't forget, you have to flash the boot/kernel backup separately in fastboot from your pc, so copy that backup to your computer once you have it.
BUT: if you want to go completely back to stock (relocked bootloader) you also need to flash stock recovery. i don't know how to dump stock recovery... maybe you can find some stock recovery.img for your version number here on xda or via google.
reaper90 said:
- unlock bootloader
- install custom recovery (CWM/TWRP)
- nandroid backup (all partitions)
You can restore this any time you need. Don't forget, you have to flash the boot/kernel backup separately in fastboot from your pc, so copy that backup to your computer once you have it.
BUT: if you want to go completely back to stock (relocked bootloader) you also need to flash stock recovery. i don't know how to dump stock recovery... maybe you can find some stock recovery.img for your version number here on xda or via google.
Click to expand...
Click to collapse
I have done all the steps but the one in bold is confusing me.
when you say flash boot/kernel separately ,you mean for the custom rom? how do I get the boot/kernel file to flash for my stock firmware?
I used TWRP to do a full backup, is nandroid backup necessary and what's the difference between that and TWRP backup?
cpu2007 said:
I have done all the steps but the one in bold is confusing me.
when you say flash boot/kernel separately ,you mean for the custom rom? how do I get the boot/kernel file to flash for my stock firmware?
I used TWRP to do a full backup, is nandroid backup necessary and what's the difference between that and TWRP backup?
Click to expand...
Click to collapse
nandroid backup = backup in custom recovery.
i mean if you want to restore your stock backup, you also have to flash the stock boot.img/kernel in fastboot because with S-ON phones we're not allowed to flash boot.img/kernel in recovery, hence we can't restore it using recovery restore function.
HTC ONE X+ RUU needed
Hi guys, i used to have a custom rom on my htc one x+ but now i want to put the stock RUU but i relocked and dicovered that my hboot is 1.40.0000 and my version-main is 1.17.401.3. So what can i do now?
Here are the steps to come back to Stock or Convert to Developer Edition if you already converted your M8 to GPE.
Prerequisites -
Unlocked Boot-loader
S-OFF
Need SuperCID (11111111)
Download stock system dumps from below links - I have AT&T and Developer Edition.
AT&T System dump - https://mega.co.nz/#!otgHGZ5D!PUlzqGpgGwIV1uGLt7eB-6SM3hPC3hXi8jyZkG5TcQE
Developer Edition System dump - http://d-h.st/x8K
you may get MD5 verification failed error for Developer Edition System dump - but you can fix it before restore - follow this - http://forum.xda-developers.com/showthread.php?t=714114
Download specific and following recoveries to restore stock backups -
to restore AT&T rom - https://mega.co.nz/#!s1YyGKxY!I-IWl1lFQca36NC51oT8D_PKnl3hxIeL59n2V_Bw8fs
to restore DE rom - https://mega.co.nz/#!R84RGT6B!9gu46as3Ai-b0ZuxTEa0Bb_5Mb9Fq3YtW_GKHsMBpek
Download following OTA zip - https://mega.co.nz/#!klkQ2ZoL!7ID8UjXbbNDplZ27NSv5YcbWUU4BEE45MlMdMyYC4js.
Process to convert -
Flash OTA 1.54.401.5 firmware zip in RUU mode. - It might fail in first attempt but do it again.
Flashed TWRP/CWM
Boot into TWRP/CWM
before restore Wipe - Davik, System, Data, Cache - please check help on TWRP/CWM restore if you are not sure how to WIPE
Flash a AT&T or DE rom
Enjoy....
You can change CID after restoring these backups and flash stock recoveries -
Developer Edition CID - BS_US001
AT&T CID - CWS__001
Download specific and following stock recoveries -
AT&T stock recovery - https://mega.co.nz/#!YtQGCaZL!MAGSSPOiTF814UVL2AOPCfa0bRq18xWSrhwyU1yl0eQ
Developer Edition stock recovery - https://mega.co.nz/#!044kGJZA!VbNhU5eh0rgKGXzrsPb2aFTCrq8xhUJTa1CFDR4AGzI
I'm not on GPE but I'm interested in converting to the Developer Edition anyway for the radio and up to date firmware. Currently I'm S-Off on with TWRP installed and running a stock based AT&T rom. Would the conversion still follow the same process? Is the wipe still needed? Would it be possible to receive OTA updates with this DE rom?
TipoF130 said:
I'm not on GPE but I'm interested in converting to the Developer Edition anyway for the radio and up to date firmware. Currently I'm S-Off on with TWRP installed and running a stock based AT&T rom. Would the conversion still follow the same process? Is the wipe still needed? Would it be possible to receive OTA updates with this DE rom?
Click to expand...
Click to collapse
Sorry I did not try that, I can't say anything as of now.
sharmavipresh said:
Sorry I did not try that, I can't say anything as of now.
Click to expand...
Click to collapse
Thanks for the honest response, at this point I think I'm just going to wait for a full RUU of the DE to become available. I didn't intend to sidetrack this thread, just curious.
Can you clean up the steps a bit? I'm a bit confused. So we only flash the OTA zip and then use SuperCID or do we have to bother with the other files you've posted?
TXI Kaze said:
Can you clean up the steps a bit? I'm a bit confused. So we only flash the OTA zip and then use SuperCID or do we have to bother with the other files you've posted?
Click to expand...
Click to collapse
Before flashing the OTA and restoring the stock rom you should be on SuperCID (11111111) (its under prerequisite too) and once you're done you can change your CID and recoveries to stock for AT&T or DE.
my post has both AT&T and DE stock roms and their supporting custom and stock recoveries,
sharmavipresh said:
Before flashing the OTA and restoring the stock rom you should be on SuperCID (11111111) (its under prerequisite too) and once you're done you can change your CID and recoveries to stock for AT&T or DE.
my post has both AT&T and DE stock roms and their supporting custom and stock recoveries,
Click to expand...
Click to collapse
Gotcha. Might want to toss a link to a SuperCID guide into your OP. I've been rooting and flashing for a few years with a lot of devices and had zero idea of what you were talking about lol. Worked just fine though. Thanks!
This is the guide I used to super CID the device, link is for the M7 but works just fine on our M8's
Link to Super CID
Sent from my HTC One_M8
REDFOCZ said:
This is the guide I used to super CID the device, link is for the M7 but works just fine on our M8's
Link to Super CID
Sent from my HTC One_M8
Click to expand...
Click to collapse
Yup. That one is a lot to read if you've already rooted and S-Off, so here it is simplified:
1) While your phone is on and plugged into your computer, use ADB to reboot into the bootloader with the command "adb reboot bootloader"
2) Once that's one, type in the command "fastboot oem writecid 11111111" There are eight 1's in total that you type. This part is important! Don't get it wrong!
3) Your HBoot won't update until you reboot, so to see if it was successful without rebooting, type in the command "fastboot read cid" and it should feed back CID-11111111
4) Proceed with the instructions from the OP to flash AT&T ROMs
Does this process return the M8 to 100% AT&T/DE stock?
I noticed the firmware used is the WWE (401) version.
garypix said:
Does this process return the M8 to 100% AT&T/DE stock?
I noticed the firmware used is the WWE (401) version.
Click to expand...
Click to collapse
WWE (401) version is used to fix different size of the system partitions between the sense version and the GPE.
sharmavipresh said:
WWE (401) version is used to fix different size of the system partitions between the sense version and the GPE problem.
Click to expand...
Click to collapse
Right, I know that. So I would consider this process as "Return to Sense" rather than "Return to Stock"...
garypix said:
Right, I know that. So I would consider this process as "Return to Sense" rather than "Return to Stock"...
Click to expand...
Click to collapse
Its very hard to say, as there are no OTA for either one. however my phone exactly matches to DE - "fastboot getvar all".
So, the process itself worked, but... I can't access /data/ at all. I've gone through this process 3 times now and I pretty much can't do anything because /data/ isn't mounted/being seen.
EDIT: Fixed it! The ONLY way (I tried multiple things) that did it was to go into TWRP, then Wipe, then Format Data. Trying to wipe it anywhere else in TWRP or trying fastboot erase userdata did nothing. This worked like a charm though.
OP - can you please post a new link to the AT&T stock recovery? The Mega link is getting nothing but errors. Thanks!
juvezavala said:
OP - can you please post a new link to the AT&T stock recovery? The Mega link is getting nothing but errors. Thanks!
Click to expand...
Click to collapse
Here is the new Link - https://www.dropbox.com/s/9h1o2b7vbgh7ruk/ATT_stock__recovery.img
Silly question but I'd rather be sure. Does the AT&T System Dump need to be downloaded in addition to the AT&T recovery rom or can I just flash the recovery rom?
soypoi said:
Silly question but I'd rather be sure. Does the AT&T System Dump need to be downloaded in addition to the AT&T recovery rom or can I just flash the recovery rom?
Click to expand...
Click to collapse
I downloaded it anyway and placed it in my TWRP/Backups folder and use it to restore to stock if needed. it is a TWRP restore. I tested it out and it works.:good:
sharmavipresh said:
Here are the steps to come back to Stock or Convert to Developer Edition if you already converted your M8 to GPE.
Prerequisites -
Unlocked Boot-loader
S-OFF
Need SuperCID (11111111)
Download stock system dumps from below links - I have AT&T and Developer Edition.
AT&T System dump - https://docs.google.com/file/d/0Bx5-C2BrwNVxUER1WFlPNmJabm8/edit
Developer Edition System dump - http://d-h.st/x8K
you may get MD5 verification failed error for Developer Edition System dump - but you can fix it before restore - follow this - http://forum.xda-developers.com/showthread.php?t=714114
Download specific and following recoveries to restore stock backups -
to restore AT&T rom - https://mega.co.nz/#!s1YyGKxY!I-IWl1lFQca36NC51oT8D_PKnl3hxIeL59n2V_Bw8fs
to restore DE rom - https://mega.co.nz/#!R84RGT6B!9gu46as3Ai-b0ZuxTEa0Bb_5Mb9Fq3YtW_GKHsMBpek
Download following OTA zip - https://mega.co.nz/#!klkQ2ZoL!7ID8UjXbbNDplZ27NSv5YcbWUU4BEE45MlMdMyYC4js.
Process to convert -
Flash OTA 1.54.401.5 firmware zip in RUU mode. - It might fail in first attempt but do it again.
Flashed TWRP/CWM
Boot into TWRP/CWM
before restore Wipe - Davik, System, Data, Cache - please check help on TWRP/CWM restore if you are not sure how to WIPE
Flash a AT&T or DE rom
Enjoy....
You can change CID after restoring these backups and flash stock recoveries -
Developer Edition CID - BS_US001
AT&T CID - CWS__001
Download specific and following stock recoveries -
AT&T stock recovery - https://mega.co.nz/#!YtQGCaZL!MAGSSPOiTF814UVL2AOPCfa0bRq18xWSrhwyU1yl0eQ
Developer Edition stock recovery - https://mega.co.nz/#!044kGJZA!VbNhU5eh0rgKGXzrsPb2aFTCrq8xhUJTa1CFDR4AGzI
Click to expand...
Click to collapse
I have a T-mobile version and i want to convert it to AT&T "because the LTE bands are just two with tmobile, and more than five with AT&T" and i do have AT&T services, so sometimes i get 4G LTE and sometimes just 4G.
i used to have the same problem with M7 but after i converted it to AT&T, i got LTE all the time. "of course i flashed the full RUU".
i tried just to flash AT&T modem but no luck, it has to be full flash like RUU.
thanks
I know this is a dumb question, but I have never dealt with rar files, only .zips. I extracted it and there are files I recognize, and tar files. which I don't know what they are. Am I supposed to flash a tar file? I feel stupid, but at the same time welcome the learning experience. Thanks.
Hi All,
So need some help. I have an ATT m8 that I did a GPE conversation following the tutorial at
http://sakitechonline.com/fully-convert-your-htc-one-m8-to-google-play-edition-w-ota-updates/
as well as a youtube video.
So there's a section about CID's and in the tutorial link, it says if my CID matches one of the ones listed, I can skip down to step #6 and install the GPE (which it did match, so I didn't change my CID to GOOGL001.) My question is, will I have issues with future OTA's? If so, do I have to start from scratch to change my CID, or can I do it as my phone currently sits right now? Also, if I do it as my phone currently sits, will it wipe my phone? Lastly, how do I go about changing my CID at this time? I know there are a few tutorials out there, but I'm not sure if I can follow them since most of the instructions to change CID's are midway through a tutorial and I'm already converted. I just don't want to brick my phone, and I've had bad luck and what not.
Any help would be great as I'm now using this phone as my primary and I don't wan't to have issues when android L finally decides to roll out. Thank you in advance!
jm0327 said:
Hi All,
So need some help. I have an ATT m8 that I did a GPE conversation following the tutorial at
http://sakitechonline.com/fully-convert-your-htc-one-m8-to-google-play-edition-w-ota-updates/
as well as a youtube video.
So there's a section about CID's and in the tutorial link, it says if my CID matches one of the ones listed, I can skip down to step #6 and install the GPE (which it did match, so I didn't change my CID to GOOGL001.) My question is, will I have issues with future OTA's? If so, do I have to start from scratch to change my CID, or can I do it as my phone currently sits right now? Also, if I do it as my phone currently sits, will it wipe my phone? Lastly, how do I go about changing my CID at this time? I know there are a few tutorials out there, but I'm not sure if I can follow them since most of the instructions to change CID's are midway through a tutorial and I'm already converted. I just don't want to brick my phone, and I've had bad luck and what not.
Any help would be great as I'm now using this phone as my primary and I don't wan't to have issues when android L finally decides to roll out. Thank you in advance!
Click to expand...
Click to collapse
So I ended up changing my CID to GOOGL001 from CWW__1 (or something). Is there any "prep" work I need to do to my phone besides having S-OFF before changing my CID so as not to brick it later or have issues with OTA's? Again, just don't want issues down the line that I may not foresee and wasn't sure if I can just freely change my CID without doing anything beforehand.
jm0327 said:
So I ended up changing my CID to GOOGL001 from CWW__1 (or something). Is there any "prep" work I need to do to my phone besides having S-OFF before changing my CID so as not to brick it later or have issues with OTA's? Again, just don't want issues down the line that I may not foresee and wasn't sure if I can just freely change my CID without doing anything beforehand.
Click to expand...
Click to collapse
Dude, fire is going to rain down from the skies onto your phone. JK, if I remember correctly, the only thing I did was make sure that I had the GPE recovery installed and relock bootloader and got OTA's just fine. I am thinking about playing with the GPE again too.
hack14u said:
Dude, fire is going to rain down from the skies onto your phone. JK, if I remember correctly, the only thing I did was make sure that I had the GPE recovery installed and relock bootloader and got OTA's just fine. I am thinking about playing with the GPE again too.
Click to expand...
Click to collapse
haha,, i wouldn't be surprised if my phone spontaneously combusted. Hmm, I haven't read anything about relocating the boot loader to make it work with OTA's. I only remember the CID thing. Thanks for the tip, I'll look into it.
jm0327 said:
Hmm, I haven't read anything about relocating the boot loader to make it work with OTA's. I only remember the CID thing.
Click to expand...
Click to collapse
That's because its not correct. You don't need to relock the bootloader to get or install OTAs. You do need stock recovery, and all system files need to be intact (if any are modified/deleted/frozen by root, they need to be restored to stock condition).
redpoint73 said:
That's because its not correct. You don't need to relock the bootloader to get or install OTAs. You do need stock recovery, and all system files need to be intact (if any are modified/deleted/frozen by root, they need to be restored to stock condition).
Click to expand...
Click to collapse
Sounds like I'm good to go now. I used the Stock Non-Rooted 4.4.4 2.12.1700.1 RUU Zip. Thanks for the heads up!
just wanted to say i had been running my verizon note 3 (non-dev edition) like everyone else here
with the bl unlocked to dev edition and rooted most likely with either kingo or supersu through teamyemin or proyemin and i think there is another one too.
basically if you want to go back 100% original (including your original cid) its not as easy as you might think.
first thing i did was wipe everything that was possible to wipe from within twrp recovery.
next i booted to odin download mode
from there i flashed the OB6 official firmware
then i rooted using the kingo method as this seemed the most likely not to infect my computer and possibly only stole info from my phone. (this used the 2 files 1.tar and 2.tar flashed with odin for pc)
i then verified my root and installed terminal emulator end es file explorer root
i copied samsung_cid to phone sd card and used es file explorer root to move to ./data/local/tmp
changed my cid back to original and rebooted phone
booted to stock recovery and wiped everything i could and booted into odin download mode
flashed OF1 official
there is a very important part that could get alot of ppl phones into brick mode.
when you goto change the cid back to original you better already have the stock BL on and running and >>>NOT<<< the DEV-BL
that is why i chose to flash an official OB6 rom first
if you try to change the cid to original non-dev edition and reboot your phone this could have problems since you would have the dev bl flashed with a non dev bl cid
when the cid for the dev edition became available you could change the cid first and boot into the bl and it would say something like developer mode enabled or someting like that even if you had the stock bl flashed (not the dev bl)
this is fine
only problem is if you change that cid back to stock/original non-dev while you are running the dev bl
i dont know what would happen but i bet it wouldnt be good.
ok next part i think is important is getting rid of kingo root as much as possible and that is why i flashed the OB6 firmware first and then OF1 for my very last step.
ok thanks.
i know alot of ppl are probably gonna say why would you want to go back to stock original cid and my answer is this.
phone is really stable and also if i want to sell it which im thinking about.
hope it helped some ppl.
Where do we get our original Cid?
The method used to do the unlocking runs the tool in two passes, like this:
pass1: change the CID.
pass2: (create debrick image &) alter the aboot partition sig to the DevEd sig.
There is no reason this can not be reversed (assuming you have root on ANY ROM) e.g. :
pass_negative_2: flash stock aboot to aboot partition.**
pass_negative_1: revert the CID by altering the original code to write your CID (minor code change and recompile).
** must be from the exact same version of boot firmware you have on the phone; you could use "dd" for this.
There's no reports of people trying this explicitly, but OTOH note this: there were owners of DevEd devices that accidentally flashed stock bootloaders. They didn't change their CID, and they didn't brick. They just couldn't go back to an unlocked bootloader any longer, or boot custom kernels: they converted their phones to retail without ever changing their CID.
Anyhow, it appears that you went through a ton of effort, when all you needed to do was flash the stock "aboot" back into place.
It probably isn't even necessary to revert the CID back.
ExpialZLD said:
Where do we get our original Cid?
Click to expand...
Click to collapse
You recorded it - as a precaution - when you went through the unlocking process. Didn't you?
As I mentioned above, it probably doesn't matter anyway.
@OP: did your "Custom" boot logo disappear eventually?
PS even after doing this the phone will still have a blown knox warranty flag and certain TZ/qseecom functionality will no longer work, even with 100% pure stock on the phone.
bftb0 said:
The method used to do the unlocking runs the tool in two passes, like this:
pass1: change the CID.
pass2: (create debrick image &) alter the aboot partition sig to the DevEd sig.
There is no reason this can not be reversed (assuming you have root on ANY ROM) e.g. :
pass_negative_2: flash stock aboot to aboot partition.**
pass_negative_1: revert the CID by altering the original code to write your CID (minor code change and recompile).
** must be from the exact same version of boot firmware you have on the phone; you could use "dd" for this.
There's no reports of people trying this explicitly, but OTOH note this: there were owners of DevEd devices that accidentally flashed stock bootloaders. They didn't change their CID, and they didn't brick. They just couldn't go back to an unlocked bootloader any longer, or boot custom kernels: they converted their phones to retail without ever changing their CID.
Anyhow, it appears that you went through a ton of effort, when all you needed to do was flash the stock "aboot" back into place.
It probably isn't even necessary to revert the CID back.
You recorded it - as a precaution - when you went through the unlocking process. Didn't you?
As I mentioned above, it probably doesn't matter anyway.
@OP: did your "Custom" boot logo disappear eventually?
PS even after doing this the phone will still have a blown knox warranty flag and certain TZ/qseecom functionality will no longer work, even with 100% pure stock on the phone.
Click to expand...
Click to collapse
Does by record do you mean by using a tool or like taking a picture of the cid
ExpialZLD said:
Does by record do you mean by using a tool or like taking a picture of the cid
Click to expand...
Click to collapse
Cut-n-paste to a text file.
The tool spews out onto the screen the device's CID before it goes about changing it.
That assumes you followed the directions in the OP and used ADB. Or, didn't follow those instructions and used a terminal emulator. (I don't know whether or not the app shows you the output from the binary).
As I mentioned, folks that had DevEd devices (that is, "factory unlocked" bootloaders) that made the mistake of flashing stock firmware turned their DevEd phones into retail phones - without ever changing the CID to some other value. So it may not even matter - you end up with a "retail" phone with the same CID that you currently have.
In any event, if you didn't record the previous CID, there's nothing to do about it.
The OP mentions something called "samsung_cid". I presume he is talking about a mod of the original code that allows you to re-write the CID to an arbitrary value.