Facepalm s off mrthod has changed IMEI of my htc one s,even image crc shows the new changed imei. I think it is because of flashing PJ4010000 zip . how to get my imei restored back to original ?
Related
Ok so heres the deal. I have an HTC Evo 3D from Rogers in Canada and I had an unlocked bootloader and S-OFF (currently (re)locked and S-OFF). I was running the stock Rogers Rom but with CWM recovery. Yesterday I downloaded the new OTA update for android 4.0 with sense 3.6 and of coarse I found out that custom recoveries won't flash stock HTC zips, and I wanted this new update. So I downloaded the official stock RUU and tried to reflash to a "true stock" form so I could update the phoen. First error I encountered when trying to use the RUU was "error 131 Customer ID error", which I found out was a problem with the CID of the phone (don't know how it was changed). Tried setting the CID to ROGER001, which is supposedly the default CID, but the RUU still would still get the CID error. So I changed the CID to 11111111 (superCID) through fastboot and tried the RUU again. It worked this time but now I'm stuck at the HTC sceen and the phone will not boot.
I have tried manually flashing the boot.img from the RUU through fastboot. Also since I'm still S-OFF and i tried reflashing CWM recovery and tried flashing an assortment of ROMs including the backup of the stock ROM that I was just on and NO rom would boot. Roms with custom boot animations would get past the HTC logo but then just sit loading forever but never actually finish booting. Also tried flashing the RUU via the bootloader by renaming the rom.zip to PG86IMG.zip and still nothing. I still have access to the bootloader and fastboot and recovery. RUU flash completes everytime I try it but never boots, and nobody seems to have had the same problem as me after using an RUU.
I am at a complete loss for what to try next and really need help.
Hboot of my phone is 1.49.08
SOLVED
Finally got the phone working again today. Looks like the RUU I was using may have been corrupt and wasn't playing nice with the ROGER001 CID. Finally was able to sucessfully download the 3.28 RUU and tried loading that after changing the CID back to ROGER001 and BAM! phone booted up after that. Crappy thing was I thought it was dead for good so I ended up going out and buying the new Galaxy S III for $650+tax :laugh:. Oh well the GS3 is a better phone anyways haha.
Point is my original problem is now solved so mods can delete this or move it or whatever.
I bought 3d evo a year ago and I tempered with it at first to root. I could not root it but it was s-off. Anyways , this whole time I thought I was getting updates and such because I was receiving update notifications and downloading them, and phone was restarting afterwards , so I thought everything was ok. Then, recently I checked software versions in settings and I was shocked. My phone was exactly the same as the first day. Then I tried to do a hard factory reset from settings. It did not work. Tried again from the bootloader menu, it did not reset again. There was a method by relocking it at first and using RUU's to make it back to original state. I relocked it but RUU file did not work , i think it was incompatible and gave an error.
Here are the version numbers in settings:
Android version - 2.3.4
HTC Sense - 3.0
Software - 1.20.468.6
This is the bootloader screen:
*****Relocked*****
****Security Warning*****
S- On
Hboot 1.49.0018 Emm-boot Oct 3-2011
I have a phone which can not revert to original state and can not apply any updates. Hboot version is an issue I always see guides about 1.50.
Do I have to start over and S-off first ? I have tried everything, putting pc86img.zip file to sd card , it reads during bootloader but does not ask to update. I tried sprint ruu file from windows but it did not work either. Need directions because I am really pissed off. Please help. Thanks.
bro i'm pretty sure that thats a gsm phone. please dont try to flash any cdma(sprint) stuff on it.
Normally I would have directed you to a thread containing gsm RUU's but apparently the new hosting site is down. Keep checking here though
http://forum.xda-developers.com/showthread.php?t=2094402
A word of warning: If you update using the RUU you will have the new hboot 1.53 and it is only possible to achieve s-off on that hboot with the wire trick. Whereas your current hboot can make use of flashmaniac's tool to downgrade and s-offf using revolutionary
EM|NEM said:
bro i'm pretty sure that thats a gsm phone. please dont try to flash any cdma(sprint) stuff on it.
Normally I would have directed you to a thread containing gsm RUU's but apparently the new hosting site is down. Keep checking here though
http://forum.xda-developers.com/showthread.php?t=2094402
A word of warning: If you update using the RUU you will have the new hboot 1.53 and it is only possible to achieve s-off on that hboot with the wire trick. Whereas your current hboot can make use of flashmaniac's tool to downgrade and s-offf using revolutionary
Click to expand...
Click to collapse
thanks man, I looked around and found stock a rom suitable for my region.And it worked. Now I'm updating to android 4
Ok guys.
i got unknown imei and baseband Ruby.
i searched everywhere but imei is clean.
So i decided to fix it.
My ideas :
i got fastboot getvar imei :
35xxxxxxxxxxx
So imei can be readed from phone
also i can searched and edited the imei block mmcblk so that phone got no problem with imei.
i think the problem is radio.img file.
searched dev section there is no radio at the moment. so i pulled up radio img from stock rom
fastboot flash radio radio.img
returned remote not allow.
my ruby is s-off and superCID.
any ideas or suggestions ?
Stock it..
Sent from my GT-S5830D using xda app-developers app
Same problem
benzersizadam said:
Ok guys.
i got unknown imei and baseband Ruby.
i searched everywhere but imei is clean.
So i decided to fix it.
My ideas :
i got fastboot getvar imei :
35xxxxxxxxxxx
So imei can be readed from phone
also i can searched and edited the imei block mmcblk so that phone got no problem with imei.
i think the problem is radio.img file.
searched dev section there is no radio at the moment. so i pulled up radio img from stock rom
fastboot flash radio radio.img
returned remote not allow.
my ruby is s-off and superCID.
any ideas or suggestions ?
Click to expand...
Click to collapse
I've got the same problem with my Amaze 4G, everything similar to your description. Please post if you find a solution. Thanks!!
currently on latest JB, and keep getting CID error when boot up. Luckily BMM can bypass this CID error and boot up without going through bp option.
I have a ICS nandroid back up and trying to see if I can restore CID from the back up. (maybe extract the CID?)
Or is there any way to fix the CID error?
supasoju said:
currently on latest JB, and keep getting CID error when boot up. Luckily BMM can bypass this CID error and boot up without going through bp option.
I have a ICS nandroid back up and trying to see if I can restore CID from the back up. (maybe extract the CID?)
Or is there any way to fix the CID error?
Click to expand...
Click to collapse
Theres no way to boot without cid, it will not boot if you restore cid
Anyway, you can install the 982.124.14 Retail.en.EU jelly bean leak which is for the gsm razr without erasing the cid and getting the error in boot. You can find it at the development section
Sent from my Nexus 4 using xda app-developers app
Hi to all! My first thread in xda.
Thanks to every develepor making a difference in android :highfive:
I want to downgrade phone because of non-stable version JB version of android(according to me beats audio messaging etc.)
but there is a good update released want to update ICS to JB
http://forum.xda-developers.com/showthread.php?t=2214225 ---> Not satisfied from this method I want fully original (afraid of warranty issueses
so
I have orginal hboot.img (extracted from RUU)
Previously downgraded HTC ChaCha via goldcard method
Is there any method (goldcard or something else) to do this at Desire X?
lynxrz said:
Hi to all! My first thread in xda.
Thanks to every develepor...
Click to expand...
Click to collapse
Back to original ICS isn't possible without s-off. But after JB Update you can run a JB custom rom or a ICS custom rom.
What is a goldcard ?(sarcasm, i'm googling it right now)
0zura
0zura said:
What is a goldcard ?
Click to expand...
Click to collapse
Goldcard is a trick to shows hboot version number equal to downgrade version
+RUU -Phone
+ what is your hboot version?
- 1.25.xxx
+It must be equal to 1.24.xx or less to upgrade CANCEL!
gold card makes hboot version 1.24.xxx which is actually 1.25.xxx
+ what is your hboot version?
-1.24.xxx
+INSTALLING
So that you're like reinstalling firmware but actually downgrading the hboot!
Edit: No needed s-off
lynxrz said:
Goldcard is a trick to shows hboot version number equal to downgrade version
+RUU -Phone
+ what is your hboot version?
- 1.25.xxx
+It must be equal to 1.24.xx or less to upgrade CANCEL!
gold card makes hboot version 1.24.xxx which is actually 1.25.xxx
+ what is your hboot version?
-1.24.xxx
+INSTALLING
So that you're like reinstalling firmware but actually downgrading the hboot!
Edit: No needed s-off
Click to expand...
Click to collapse
how does one do a goldcard ? can it be done by myself or do I have to take it somewhere, had a look at this link
http://androidforums.com/desire-all-things-root/117710-goldcard-tool.html and wasnt sure whether it would work for a DX ? are goldcards able to work on any phone, any of a brand or what ? also what is its function
Posted Via My HTC DESIRE X Running MySenceDX+
Pp18It is simple you can search google play for "GoldCard Helper"
How works GoldCard in theory?
HBoot version number written on a partition which locates in /dev/block/ folder (Can't remember which mmcblk)
GoldCard Helper or other tools read this partition's CID (I guess) Then convert it to "revese CID" (Don't know why)
Then you copy the idenificial CID number to "SD CARD" via hex editor.
BAM!!
Now you clone partition's ID (CID) and HBoot version number will be read from this partition so that SD CARD
Second process is finding hboot written partition in proc. You can't see them normally with a file manager, have to pull the partition.
Edit the version number on extracted partition (for ex. 1.24.x.x instead of 1.25.x.x) and open with hex editor, copy, then paste to SD CARD after REVESE CID number
When you run RUU and SDCARD mounted, RUU detect SD CARD not original version number and update hboot
Force myself to remember.. I guess, can't find the partition or I did it but somehow the RUU process stopped with an error...
Works all of models as long as know how to do it
Edit: Found a hboot mmcblock, it locates /dev/block/mmcblk0p18
Digging around to making goldcard to downgrade hboot.