Related
Anyone out there which have the stock EE1 radios?
LTE Modem
Code:
dd if=/dev/block/stl11 of=/sdcard/ee1_lte_modem.bin bs=256 count=48
CDMA aka CPMODEM
Code:
dd if=/dev/block/stl12 of=/sdcard/ee1_cp_modem.bin bs=256 count=2
Do you mean stock ED1 radios? I would say one of the devs would be your best bet, imnuts, DroidXcon, kejar31, etc.
RaptorMD said:
Do you mean stock ED1 radios? I would say one of the devs would be your best bet, imnuts, DroidXcon, kejar31, etc.
Click to expand...
Click to collapse
The baseband reports itself as
Baseband Version
i510.06 V.EE4
SCH-I510.EE1
Click to expand...
Click to collapse
I'm assuming that's what he means.
DeathWalking said:
The baseband reports itself as
I'm assuming that's what he means.
Click to expand...
Click to collapse
Yup was thinking that it would be a good idea for us to keep the versions in the event we may find issues with the new deltas.
Based on the PIT info on the stl device these were what we need for being able to flash future radios as well. Ie controlled updates.
Thnx for the replies!
Sent from my SCH-I510 using XDA Premium App
RaptorMD said:
Do you mean stock ED1 radios? I would say one of the devs would be your best bet, imnuts, DroidXcon, kejar31, etc.
Click to expand...
Click to collapse
Yeah I've already msgd them as well.
Sent from my SCH-I510 using XDA Premium App
Safe to assume that the same data would pull the EE4 radio?
The risk here is if we get it wrong, no way to fix it...
distortedloop said:
Safe to assume that the same data would pull the EE4 radio?
The risk here is if we get it wrong, no way to fix it...
Click to expand...
Click to collapse
As i understand it yes. Looking at the updates in the ee update files i didntt see any partitioning. if in doubt pull the pit info to validate.
Measure twice cut once.
Sent from my SCH-I510 using XDA Premium App
c0ns0le said:
Anyone out there which have the stock EE1 radios?
LTE Modem
Code:
dd if=/dev/block/stl11 of=/sdcard/ee1_lte_modem.bin bs=256 count=48
CDMA aka CPMODEM
Code:
dd if=/dev/block/stl12 of=/sdcard/ee1_cp_modem.bin bs=256 count=2
Click to expand...
Click to collapse
Thought I'd try this on my phone to get the EE4 modems saved. First command runs fine, second command errors out.
Code:
# dd if=/dev/block/stl11 of=/sdcard/ee1_lte_modem.bin bs=256 count=48
48+0 records in
48+0 records out
12288 bytes transferred in 0.008 secs (1536000 bytes/sec)
# dd if=/dev/block/stl12 of=/sdcard/ee1_cp_modem.bin bs=256 count=2
/dev/block/stl12: cannot open for read: Invalid argument
Also, after looking at imnut's instructions on making a backup there's a conflct in the stl numbers you gave. stl11 appears to be /dbdata, not the cpmodem.
I posted the EE4 pit and dd -h of the phone in the other thread if you want to check them out.
We were never able to dump the radio files from the phone on the Fascinate. I wouldn't be suprised if the same applies here. What we need is a source, preferably one who can provide a full Odin package for any one of the official builds.
s44 said:
We were never able to dump the radio files from the phone on the Fascinate. I wouldn't be suprised if the same applies here. What we need is a source, preferably one who can provide a full Odin package for any one of the official builds.
Click to expand...
Click to collapse
There was a fellow in the i9000 forums who was pumping out leaked ROMs from Samsung like a madman. I always suspected he was a Samsung employee. I wonder if he might be able to help us out. I'll see if he's still around and ask him.
.17 (from the get-go, never downgraded)
Successful SparkyRoot
Stock ROM
SU $
Fired up Goo Manager, Install OpenRecovery Script TWRP
Screen says "installing recovery image" or somesuch.
auto-reboot to Asus loading screen with a blue loading bar I've never seen before, and "blob signature verification failed" in the upper left corner. Auto-reboot to normal boot sequence, no recovery.
I don't understand. Any insight would be welcome, maybe a tip as to what I should research or a thread I should look at. Not my first rodeo; had a rooted Thunderbolt, rooted GS3. Followed this same sequence 3 days ago with my GS3 with no problems. Is this an Asus thing?
Sent from my SCH-I535 using xda app-developers app
I think it just occurred to me...
I'm rooted, but the bootloader is still locked?
Sent from my SCH-I535 using xda app-developers app
Just like when I'm at the grocery store... I always stop to ask for help finding something when it's just one more aisle down LOL.
Sent from my SCH-I535 using xda app-developers app
Here's my delimma...
After a huge ordeal with Verizon I managed to get myself an early upgrade to this s3.
Part of that deal was that I accept the best equipment protection they have so next time they won't deal with me asking for another early upgrade.
That being said I love stock Android... I tried to use touchwiz and although I'm sure it's fine for some I can't get behind it.
Does rooting and flashing ever really bother me? No... But the flash counter I've been reading about does.
I can with almost 100% certainty tell you that I will end up doing a warranty claim on this device, and at which point I may get rejected due to software.
I've read the methods of getting the flash count back to zero or stock. How reliable are these?
I hope I don't come off as too paranoid.
Thx in advance!
Sent from my SCH-I535 using xda app-developers app
stevenjcampbell said:
I can with almost 100% certainty tell you that I will end up doing a warranty claim on this device, and at which point I may get rejected due to software.
Click to expand...
Click to collapse
Wait until after, if you're so sure.
The only time I've ever heard of the flash counter even being accessed was when a device was sent directly back to Samsung from the user.
There is of course a risk. Some have lost their IMEI. We can recovery that now, but some have been stuck on roaming indefinitely with no fix.
I have no idea if the flash counter resets actually work for this device or not, though. These forums are filled with lots of information (such as the old IMEI recovery thread that was unreliable and could not recover from an IMEI=0).
ExodusC said:
Wait until after, if you're so sure.
The only time I've ever heard of the flash counter even being accessed was when a device was sent directly back to Samsung from the user.
There is of course a risk. Some have lost their IMEI. We can recovery that now, but some have been stuck on roaming indefinitely with no fix.
I have no idea if the flash counter resets actually work for this device or not, though. These forums are filled with lots of information (such as the old IMEI recovery thread that was unreliable and could not recover from an IMEI=0).
Click to expand...
Click to collapse
Well, I as hard as I am on devices I mean. I'm using it heavy, plus the circumstances ibusenit such as gum hiking etc.
Seems that I will have to risk it. if software there is always a fix it seems...
Sent from my SCH-I535 using xda app-developers app
stevenjcampbell said:
Well, I as hard as I am on devices I mean. I'm using it heavy, plus the circumstances ibusenit such as gum hiking etc.
Seems that I will have to risk it. if software there is always a fix it seems...
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
yep pretty much just follow the instructions to the t, always take your time when flashing brand new rom like reading over the threads to see the problem and always make a backup. Yes the reset flash counter thing works i've had to send in a s3 due to the charging port and haven't been denied of my warranty. At the end of the day their is always a risk that your problem will be hardware related but that's a very slim chance. Other than that you should be good to go I've never had a problem other than now and this my third rooted phone.
joka10 said:
yep pretty much just follow the instructions to the t, always take your time when flashing brand new rom like reading over the threads to see the problem and always make a backup. Yes the reset flash counter thing works i've had to send in a s3 due to the charging port and haven't been denied of my warranty. At the end of the day their is always a risk that your problem will be hardware related but that's a very slim chance. Other than that you should be good to go I've never had a problem other than now and this my third rooted phone.
Click to expand...
Click to collapse
Okay thank you. I loved paranoid android rom on the incredible 2 but it had no camera support. Looking forward to see what this could do with it!!
What method to reset flash count did you use? The model number of my current device is SCH-I535 whereas the model in the triangle app is always i9300.
Sent from my SCH-I535 using xda app-developers app
stevenjcampbell said:
Okay thank you. I loved paranoid android rom on the incredible 2 but it had no camera support. Looking forward to see what this could do with it!!
What method to reset flash count did you use? The model number of my current device is SCH-I535 whereas the model in the triangle app is always i9300.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used the adb one where you type in
1.)adb devices (should a number if you set it up right)
2.) adb shell
3.) su
4.) echo -n '\x00' | dd obs=1 count=1 seek=4193796 of=/dev/block/mmcblk0
but if your not comfortable with adb then triangle away works but i forget if you have to change anything
joka10 said:
I used the adb one where you type in
1.)adb devices (should a number if you set it up right)
2.) adb shell
3.) su
4.) echo -n '\x00' | dd obs=1 count=1 seek=4193796 of=/dev/block/mmcblk0
but if your not comfortable with adb then triangle away works but i forget if you have to change anything
Click to expand...
Click to collapse
No I'm okay with command prompts. I assume that
1) adb is something installed on my pc
2) these commands are done via a cmd prompt with admin permissions.
I can Google how to install adb android... Not worried there.
When I can get back to a pc ill be sure to thank you proper.
Sent from my SCH-I535 using xda app-developers app
I just came to Android after 5 years of running Blackberry (Storm,Storm 2, 9850) which were all keyboard-less BB. I knew them inside out, was creating my own OS mods and could pretty much create (within Blackberry reason) anything I wanted in it. Android is COMPLETELY different, but with a lot of reading and the great Devs within the community, I got it rather quickly and am running a custom rom with a modified kernel, while adding some MOD zips to get even more customizations to my liking. All that said, if you spend just a little time reading through the 101 of rooting and getting back to stock, you'll be just fine. I've flashed 15 times already, trying just about everything out there to get a look and to also get familiar with the how to and what if process. My counter never changed from "0". And if it would have, I am confident after reading throughout here at I could get that back to factory very easily.
Hey,
So some of you know that I kinda was in a bind this weekend, found my way out and with the help of some folks like kermione96 and utkanos.
Remember that these are UNOFFICIAL and to be used for your own purposes! No guarantees. CC, Apache, etc...
ClockworkMod Touch (All versions):
http://goo.im/devs/childofthehorn/comanche/samsung_comanche_cwmtouch_childofthehorn.tar.md5
I also made some Recovery Images for Odin for the ATT Crowd:
Root, Recovery, CWM (basic) ATT ONLY: (unzip with 7zip first)
http://goo.im/devs/childofthehorn/comanche/Stock_Root_CWM_i547_cached_out.tar.md5.7z
STOCK, no Root, stock recovery ATT: (unzip with 7zip first):
http://goo.im/devs/childofthehorn/comanche/Stock_ATT_comanche_i547_ICS.tar.md5.7z
If anyone has the Courage to try this and can send me the Output files (xbackup.img where x is a number) along with what their carrier is and Odin Flash Counter #, it could be helpful. If we knew where the Modems were, it would help with future updates, etc without loosing root.
Android Script to Download:
https://dl.dropbox.com/u/58849669/ROMS/sysmaybe
Run in Terminal:
adb push sysmaybe /data/local/tmp
adb shell
(su if you have root)
cd /data/local/tmp
chmod 755 sysmaybe
./sysmaybe
Click to expand...
Click to collapse
AS A SIDE NOTE TO THOSE WHO MIGHT BE HAVING LTE ISSUES AFTER ROOT
Try triangle away from chainfire.
DOWNLOAD ON GOOGLE PLAY
http://forum.xda-developers.com/showthread.php?t=1494114
It is not compatible with this device, so as of yet it will not reset your counter to 0. However, the attempt does reset something I do not yet know and allows you to connect to the the LTE (found this to be an LTE connection issue on an ATT device after recovering).
BTW:
The Rugby Pro now has its own ForumThread at RootzWiki
http://rootzwiki.com/forum/556-galaxy-rugby-pro-development/
Thanks for posting this, should come in handy when I'm assigned this phone for work
thereddog said:
Thanks for posting this, should come in handy when I'm assigned this phone for work
Click to expand...
Click to collapse
There is also a super thread with links to other work that has been done on the rugby pro: http://forum.xda-developers.com/showthread.php?t=2006388
Sent from my SAMSUNG-SGH-I547 using Tapatalk 2
Very old thread, but the links are not valid...anybody have updated links for download?
see the super thread for more recent / valid links.
Sent from my XT1053 using Tapatalk
Thanks. I guess there's really no development for this device.
Sent from my SAMSUNG-SGH-I467 using Tapatalk
Agent said:
Thanks. I guess there's really no development for this device.
Sent from my SAMSUNG-SGH-I467 using Tapatalk
Click to expand...
Click to collapse
There was but it's tapered off.
Sent from my XT1053 using Tapatalk
Ok so I have a one s tmobile us.
I have re-locked and reverted it all back to stock hoping the last update was jelly bean.
And after all that and getting the OTA, well to say the least i was pissed to see it wasnt.
So now here we go.
I did all the reading i could find.
I am going to
UNlock, reroot, and then s-off and super cid to the HTC_001.
then hope that if what i read is right i can do a check software update.
And it will pull down the HTC jelley bean right?
Or what do I need to do?
I'm not worried about warranty since i use family mobile which is walmart t-mobile who dont offer me a warranty any since i brought my own phone.
Also question 2 is will I have any radio or wifi issues by doing any of this presuming I read right and all I have to do is the 4 steps i mentioned above.
Thank you for any input on the question.
I will gladly donate to you for some help in getting it done.
I don't use wifi calling so i dont care about that feature and i live here in the us.
Thank you again.
Tim
Unlock the bootloader and then reroot in the exact same way that you did previously. Then you will need to SuperCID. This involves pulling a file called mmcblk0p4, hex editing partition 210's 5th to 12th characters to HTC__001. Do the following in cmd:
adb shell
su
dd if=dev/block/mmcblk0p4 of=/sdcard
exit
adb pull /sdcard/mmcblk0p4
Look in your adb folder and find the file. Hex edit it with the above instructions. If your CID is not where I originally said it was, then just look for T-MOB010 and overwrite it. Then you need to save the file with MOD at the end, to make sure that you can revert if it goes tits up. Make sure the file is the exact same size as the original. Then you need to tell the phone that the modded file is the new one. Push the modded file onto the SD Card through ADB. Then type:
adb push mmcblk0p4MOD/sdcard
adb shell
su
dd if=/sdcard/mmclbk0p4MOD of=/dev/block/mmcblk0p4
exit
adb reboot bootloader
When rebooted, type:
fastboot oem readcid
You should get cmd telling you that it is HTC__001. Successful. If not, just repeat the process (although, if you **** it up, you probably will have a brick)
You do not need to S-Off to get the OTA update. S-Off has no impact on OTA whatsoever. If you really want to S-Off, then Google "FacePalm S-Off HTC One S"
Just reboot your phone, go into settings, about phone, software updates, check now. The 4.1.1 OTA should be there.
Sent from my One S using xda premium
Thank you im doing it as we speak. Only reason I was going to S-off is when i try to do it using the one click it said you need s-off so im trying your way as I type.
dd if=dev/block/mmcblk0p4 of=/sdcard
/sdcard: cannot open for write: Is a directory
1|[email protected]:/ # dd if=dev/block/mmcblk0p4 of=/sdcard
dd if=dev/block/mmcblk0p4 of=/sdcard
/sdcard: cannot open for write: Is a directory
1|[email protected]:/ #
Sorry, you have to put another forward slash at the end of the file location, should have added that, sorry
Sent from my One S using xda premium
Help!!
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tim>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p4 of=/sdcard
dd if=/dev/block/mmcblk0p4 of=/sdcard
/sdcard: cannot open for write: Is a directory
1|[email protected]:/ # dd if=/dev/block/mmcblk0p4 of=/sdcard/
dd if=/dev/block/mmcblk0p4 of=/sdcard/
/sdcard/: cannot open for write: Is a directory
1|[email protected]:/ #
I got it but heres the weird thing my cid reads as HTC_0010? did I need to put 1 under score or 2 underscores for the cid? HTC_001 or is it HTC__001
dd if=/dev/block/mmcblk0p4/ of=/sdcard/
Try that. If that doesn't work, put mmcblk0p4 on the end of sdcard.
Sent from my One S using xda premium
Ok so
HTC__001
it has to be 8 characters its 2 underscores. seperating the HTC and the 001
Ok so heres what i did,
I unlocked again using the onclick newest one.
Then using One click again I changed recovery to the TWRP for S4 of course.
Then finished rooting by install all su binaries.
Changed cid so it now shows HTC__001.
But when i went to the software updates button just now it didnt pull the JB 4.1.1
Grrrrr.
Do i need to change the rom to a different rom?
im on 2.35.531.12 710RD factory tmobile rom.
Do i need to change something else to get my HTC JB 4.1.1 whatever it is?
Try running at HTC__001 RUU. You'll have to relock beforehand though.
Sent from my One S using xda premium
Shoot wouldnt know where to find the us htc__001 ruu do you?
If you Google HTC One S RUUs you should get two or three pages that offer them
Sent from my One S using xda premium
i just don't know which one to use for me . I'm on tmobile network and i am in the us can you possbly point me in the right direction? also you have paypal?
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
So i dont know if this the newest one and if i will have radio or wifi issues with it...
Hey thanks a lot. Your post helped me as well... Thank you.
Sent from my One S using xda premium
It is the newest one (JB is a hint if you look through the name). And yes, there are radio issues. A few people (including me) have got issues with connecting to 3G or HSPDA/HSPA. It will upload data fine but does not download. You have to connect to GPRS, EDGE or HSPDA+/HSPA+.
Sent from my One S using xda premium
Kyle thanks man,
So after all is said and done.
I did do S-off and i dont regret it as I am hboot 1.4
Anyway I changed my cid too 11111111 but then when i was eading and reading and reading and reading i saw that using 11111111 is a guaranteed BRICK!!
So I used the HTC__001 and still had no luck to get the ruu to run. Ill post the ruu log file here but more or less it is *****ing about signature.
If im not mistaken, If i was able to get it to install i can always flash my radio thus fixing any wifi issues.
I did get the trickdroids newest 9.0 to load and then flashed the 9.1 update
Then i flashed the wifi partitions with no issues.
But im curious of what cid you have and where you live that you were able to get that ruu to work for you?
I love s-off though now i can flash any radio, any hboot and so on.
As a side note before the wifi partitions flash wifi would not work kept getting authentication erro.
After connects immidiately, has better range then my stock tmous 2.35.12 whcih was the newest with all updates.
And i get a full 24mbit steady on heavy downloads.
I am curiously wanting to see how the wwe would run but HTC__001 keeps giving bad sgnature error.
Tim2246 said:
But im curious of what cid you have and where you live that you were able to get that ruu to work for you?
Click to expand...
Click to collapse
Maybe this is the answer to your problem
( running latest wwe ruu on your tmobus phone)
http://forum.xda-developers.com/showthread.php?p=39724350
Sent from my VILLE using xda app-developers app