Sup everybody. I was rooting my HTC Thunderbolt today and everything was going great....until I got to step 6 in the list. I put in the correct coding in ADB and got the correct MD5 info on output, but when I went to run the bootloader rewright i get the incorrect MD5 sum. Check it out: c:\android-sdk\tools>adb shell
# /data/local/busybox md5sum /data/local/hbooteng.nb0
/data/local/busybox md5sum /data/local/hbooteng.nb0
6991368ee2deaf182048a3ed9d3c0fcb /data/local/hbooteng.nb0
# dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.415 secs (2526689 bytes/sec)
# /data/local/busybox md5sum /dev/block/mmcblk0p18
/data/local/busybox md5sum /dev/block/mmcblk0p18
bfa2f3ac5eb3bcf67af23509b4081999 /dev/block/mmcblk0p18
As you can tell the Green Numbers are correct according to the root guide but the red numbers were part of the incorrect MD5 sum
Now as far as I understand these are supposed to match....but even when everything was perfect up till this point it still screwed up!
Anybody got a clue to what I should do not to keep from bricking my phone?
Thanks in advance guys.
It appears that your downgrade did not stick according to your md5. Restart at step one.
Sent from my BAMF 2.0-5 Thunderbolt
Do not reboot
That is NOT the downgrade, that is the bootloader. DO NOT REBOOT your phone.
From the directions by jcase
jcase said:
If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb," try again; if it still doesn’t work, seek help from chat.andirc.net in channel #root or go here AndIRC Thunderbolt Web Chat DO NOT REBOOT.
Click to expand...
Click to collapse
Try it one more time, if it doesn't work again, leave you phone plugged in so it doesn't die. Wait for an answer on IRC
Again DO NOT REBOOT
Related
Original question post below...
IF YOU DO NOT HAVE THIS PROBLEM PLEASE BACKUP YOUR /EFS NOW!!! this will save you pain in the future.
One of the things I see over and over in the DEV forum for different ROM's is I flashed this ROM and I do not have any cell service. This seemed common enough that I wanted to put what I found in one place. I am not an expert on this and I will credit the posts and users that helped me. I am actually looking for help in creating a fool proof way to fix a broken /efs, product code (Vibrant is SGH-T959ZKBT), and IMEI.
It seems that the issue here is a corrupt /efs partition/folder (/dev/block/spl3)
You can check this a couple ways first look at your /efs folder in Root Explorer (show hidden files) or via "adb shell ls -a -l /efs". As many of you know this is where you find the nv_data.bin file used for unlocking and stores your product code (needed to be accurate for Kies to work). It is also where the phone stores your IMEI. My good /efs looks like this:
Code:
adb shell ls -a -l /efs
drwxrwxrwx root root 2009-12-31 23:00 .android
-rwx------ radio radio 2097152 2011-05-30 00:44 nv_data.bin
-rw-rw-rw- radio radio 15 2011-05-28 17:46 .imei
drwxrwxrwx radio radio 2010-09-12 03:29 imei
-rwx------ radio radio 2097152 2011-05-07 18:24 .nv_data.bak
-rwx------ radio radio 32 2011-05-07 18:24 .nv_data.bak.md5
-rwx------ radio radio 32 2011-05-30 00:44 nv_data.bin.md5
-rw-rw-rw- radio radio 801 2011-05-07 18:24 nv.log
-rw-rw-rw- radio radio 1 2011-05-07 18:24 .nv_state
-rwx------ radio radio 1048576 2011-05-07 18:24 .nv2.bak
-rwx------ radio radio 32 2011-05-07 18:24 .nv2.bak.md5
The .imei file holds your IMEI in hex format.
You can also check your IMEI by pressing *#06#. You should check that against your IMEI printed on the back of your phone under the battery.
To get your radio working again with correct IMEI you will need a good backup of your /efs folder or partition. You may have a backup and not know it, some ROM porters have added a script to backup your /efs to /sdcard/backup/efs you should look for it. If you are not lucky enough to have one then find a ROM where you see the generic IMEI number (004999010640000) when you press *#06# in the dialer. I used an old Galaxy S 4G port by Eugene373 (he has removed it) to get the generic IMEI.
There are disadvantages to using the generic IMEI as some services will not work (i.e. security on corporate email)
Now that all that is out of the way let's get to the steps for getting you cell service back:
STANDARD DISCLAIMER APPLIES!!! I cannot be responsible for bad things that could happen playing with your /efs folder/partition
Create a copy of your current /efs partition (/dev/block/stl3) with this command: (Thanks Candanga http://forum.xda-developers.com/showthread.php?t=859914)
Code:
# busybox cat /dev/block/stl3 > /sdcard/efs-stl3-backup.img
Mount this file to another location like /testefs:
Code:
# mkdir /testefs
# busybox mount /sdcard/efs-stl3-backup.img /testefs
Now we can fix it up from your /efs backup if you have one:
Copy all the files from your backup into /testefs and overwrite them
Set all the files and directories (except .android should be root) to the owner and group radio:
Code:
# busybox chown 1001:1001 nv_data.bin
# busybox chown 1001:1001 .imei
# busybox chown -R 1001:1001 imei
# busybox chown 1001:1001 .nv_data.bak
# busybox chown 1001:1001 .nv_data.bak.md5
# busybox chown 1001:1001 nv_data.bin.md5
# busybox chown 1001:1001 nv.log
# busybox chown 1001:1001 .nv_state
# busybox chown 1001:1001 .nv2.bak
# busybox chown 1001:1001 .nv2.bak.md5
Set the file permissions as follows:
Code:
# busybox chmod 700 nv_data.bin
# busybox chmod 666 .imei
# busybox chmod 700 .nv_data.bak
# busybox chmod 700 .nv_data.bak.md5
# busybox chmod 700 nv_data.bin.md5
# busybox chmod 666 nv.log
# busybox chmod 666 .nv_state
# busybox chmod 700 .nv2.bak
# busybox chmod 700 .nv2.bak.md5
Unmount /testefs
Code:
# busybox umount /testefs
Now your /sdcard/efs-stl3-backup.img should be all fixed. If you have the generic IMEI you can try editing the .imei file with a hex editor of your choice and change it to your IMEI it is just the hex representation of your IMEI and nothing else in the file. (I did not test this as I had the files backed up.
Next we are going to create an odin tar to flash to the phone: (Thanks cellgeek http://forum.xda-developers.com/showpost.php?p=10622481&postcount=12)
Code:
# cd /sdcard/
# busybox cat efs-stl3-backup.img > /sdcard/efs.rfs (this is the key step!!)
# tar -cf efs.tar efs.rfs
# exit
Now your back at your PC. Do the following step to get the .tar file off your phone.
Code:
c:\Android\tools> adb pull /sdcard/efs.tar
This tar file can be put in the PDA section of Odin and flashed in download mode.
If all worked you should not have a repaired /efs that should work on most/all ROMs.
What I did not cover here was how to fix the Product code but this post from bames explains how to do that for a Captivate and should work the same for our Vibrants. Difference is our Product Code is SGH-T959ZKBT and you may need to be on Stock JI6 to do the steps in the post.
http://forum.xda-developers.com/showthread.php?t=881162
I hope this helps some and feel free to let me know if I missed something or if it does not work or if there are easier ways.
Original Question:
philow said:
I have been flashing ROMs on my Vibrant for a while and all has worked OK. I never really bothered to look at my IMEI number but I am sure somewhere along the line it changed and probably my Product Code. I just decided to go back to stock and clean up the phone a bit before I continue now that CM7 is officially supported
I Odin back to JFD with the 512.pit and partition. After the reboot the phone will only stay on for a short time then reboot or turn off and I have no signal.
I then Odin to JI6 w/o repartitioning and it will boot and is stable. I root the phone then I look in the /efs folder and all that is there is a .android folder. I have no signal at this point. I can copy a backup of my /efs or just mount as r/w with root explorer and I will get the nv_data files that I need and get signal. If I copy my backup first then I will also have the correct IMEI for my phone. If I do not restore from my backup my IMEI is null/null.
My problem is that if I reboot my phone I again have no files in /efs just the .android folder.
I have tried to change permissions and ownership on the files to radio (1001) but no matter what I do the files disappear.
Anyone else having this problem? Does anyone have a solution?
Thanks
Click to expand...
Click to collapse
what rom did you came from?
Sent from my SGH-T959 using XDA App
iynfynity said:
what rom did you came from?
Click to expand...
Click to collapse
It was my Son's phone so I am not sure what all he has had on it or when it started having a problem but the latest was the 5/7/2011 MIUI rom.
MIUI worked fine on reboot as far as signal is concerned. Not sure what IMEI it had.
Thnaks
You still have your eds backup right?
http://forum.xda-developers.com/showthread.php?t=859914
It's a little complicated but I hope you fix it. Or if not, try to ask tmobile.
Sent from my SGH-T959 using XDA App
iynfynity said:
You still have your eds backup right?
http://forum.xda-developers.com/showthread.php?t=859914
It's a little complicated but I hope you fix it. Or if not, try to ask tmobile.
Click to expand...
Click to collapse
I have tried that post and this one from the Captivate forum.
http://forum.xda-developers.com/showthread.php?t=881162
And it still deletes the files when I reboot. I have actually contacted Tmobile and they have sent a new phone but I am trying to see what has happened in case it happens again.
Also, I just flashed an old GalaxyS4G ROM my son had on it and it seems to work OK as well but with a generic IMEI and the 4G Product code.
strange!!!
Thanks for your quick reply
Added possible Solve
I added what I did to solve my issue in the OP! Hope it helps someone!
Thanks
No EFS backup and EFS got currupted| How to recover Vibrant
philow said:
Original question post below...
Code:
# mkdir /testefs
# busybox mount /sdcard/efs-stl3-backup.img /testefs
Now we can fix it up from your /efs backup if you have one:
Original Question:
Click to expand...
Click to collapse
How to repair IMEI and get back signal If you dont have efs back up or NV_data.bin backup?
I am in big trouble.
Flash to stock using ODIN and it should be fixed, check your IMEI with the one in the back of your phone.
The easiest way to do it is using this http://forum.xda-developers.com/showthread.php?t=954509, as it comes with the pit and pda files you need. (Many thanks to bay_wofl)
how if I don't have the stl3, in fact my /dev/block is empty !!!
do I still have chance to restore my phone with only the efs backup ?
NO Signal ** no /efs folder
I have a similar problem on my gooapple phone.
I have no /efs folder anywhere but my IMEI address after struggling appears. I modifyed the /data/nvram/md/NVRAM/NVD_IMEI MP0B_001 file without any luck.
What finally did the trick was executing :
adb shell
su
echo 'AT +EGMR=1,7,"IMEI_1"'> /dev/pttycmd1
echo 'AT +EGMR=1,10,"IMEI_2"'> /dev/pttycmd1
I still have the No Signal problem.
can this help me?
has anybody found a solution to this issue?
regards,
Sergio G
serginhog said:
I have a similar problem on my gooapple phone.
I have no /efs folder anywhere but my IMEI address after struggling appears. I modifyed the /data/nvram/md/NVRAM/NVD_IMEI MP0B_001 file without any luck.
What finally did the trick was executing :
adb shell
su
echo 'AT +EGMR=1,7,"IMEI_1"'> /dev/pttycmd1
echo 'AT +EGMR=1,10,"IMEI_2"'> /dev/pttycmd1
I still have the No Signal problem.
can this help me?
has anybody found a solution to this issue?
regards,
Sergio G
Click to expand...
Click to collapse
Did you find a solution? I just received my goophone i5 and have no service
You almost made me cry !!! Followed about 90% of all the guides to restore my backed up efs. Went from no signal to bootloop and back. Spend 6 days trying to fix my phone and you were my last resort. If your guide wouldn't work I would've given up. I did push the Thanks button but wanted to say thank you too
So I have mac osx and windows. I've tried rooting on both. I can follow a tutorial, that is how I've rooted my thunderbolt when it first came out. But my new thunderbolt won't root using the methods that are working for others. So I request someone to help me out as to writing a step by step setup for required prerequisites programs... Thank you. Something isnt working. I just want to enjoy perks of root again.
Sent from my ADR6400L using XDA App
Which instructions are you trying to follow, JCase's or Cap's? Also, where is the root procedure failing for you? I only ask because there is no one here who could write better step by step instructions than the ones already included in both rooting methods.
Have to agree. Any information at all regarding how its failing would be most helpful.
Okay. For windows I used the script that is a batch file because I've heard it is super easy to use... When I first was running the script it would not find the device. Now it will find it with debugging on. But when debugging is on my device won't be listed in my computer. With debugging off it will show up on my computer. Anyways with the script it says it pushes all the files then when my phone is to reboot it won't.
Sent from my ADR6400L using XDA App
Make sure that your ADB is set up properly before you start using the batch file.
A great set of instructions can be found here:
http://www.droidforums.net/forum/droid-hacks/10924-how-adb-windows-made-easy.html
The batch file is also old and some of the files included in it might be too dated to use. Try using JCase's method.
Last login: Fri Jul 29 16:53:34 on ttys000
scott-roccas-macbook:~ scott87$ cd ..
scott-roccas-macbook:Users scott87$ cd ..
scott-roccas-macbook:/ scott87$ cd and*
scott-roccas-macbook:androidsdk scott87$ cd tools
scott-roccas-macbook:tools scott87$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT14RS010885 device
scott-roccas-macbook:tools scott87$ ./adb push busybox /data/local/
1867 KB/s (1062992 bytes in 0.555s)
scott-roccas-macbook:tools scott87$ ./adb push psneuter /data/local/
1764 KB/s (585731 bytes in 0.324s)
scott-roccas-macbook:tools scott87$ ./adb push misc.img /data/local/
1943 KB/s (262144 bytes in 0.131s)
scott-roccas-macbook:tools scott87$ ./adb shell chmod 777 /data/local/busybox
scott-roccas-macbook:tools scott87$ ./adb shell chmod 777 /data/local/psneuter
scott-roccas-macbook:tools scott87$ ./adb shell /data/local/psneuter
mmap() failed. Operation not permitted
scott-roccas-macbook:tools scott87$
following this tutorial for my mac... http://forums.androidcentral.com/th...9-mac-procedure-how-root-htc-thunderbolt.html I have rooted my orignal TB over 6 times. Now I cannot use the same method on my new TB. Wtf. It wont let me go past the step of ./adb shell /data/local/psneuter
what is wrong?
Where did you get the exploits file that contained the psneuter file and such? Try downloading the files from http://www.multiupload.com/K4BZ22SIT5 and verify the md5 is 3b359efd76aac456ba7fb0d6972de3af and try again.
I'm kinda clueless without firmware versions and what exploits exactly are being used.
My exploits folder matches the MD5 checksum... I am on the newest possible firm. Someone please help me solve this issue...
http://forum.xda-developers.com/showthread.php?p=12785644#post12785644
http://forums.androidcentral.com/thunderbolt-rooting-roms-hacks/73211-rooting-issues.html#post782824
Both of those links showed ppl having similar problems. Try their fixes of restoring to factory defaults and trying again or re-formatting your card.
Thank you for your help. Doing a factory reset made the difference. I greatly appreciate it.
Dueces.
Sent from my ADR6400L using XDA App
Check out these videos, they helped me go through all the steps. The second time I rooted this thing was harder because I thought I had everything setup, and I did but I had to redo everything to get it to work. Start fresh by doing the drivers again, then put the contents of the exploits zip in sdk tool, (all the files but one were correct on mine, I think it was just an outdated version and that was one of my hold ups)
http://www.youtube.com/watch?v=oKPSe12YDxQ
http://www.youtube.com/watch?v=mc6EMdPpF6o
This is why you should manually root, and not do the auto crap... problems
** This is completely unsupported!!!!!!! **
ALL credit goes to saurik for the root method, Jason A. Donenfeld (zx2c4) for finding the exploit, alpharevx for finding the offsets and initial confirmation on the Transformer Prime and viperboy for finding it and posting it in his thread. I did not research, find, or develop this root method!
Mods, if I've done anything wrong, please feel free to remove this thread.
You will need to know how to use ADB commands, otherwise, use viperMOD PrimeTime!!!!!!!!!!!!!!!!!!!!!!!!.
Downloads:
mempodroid binary
su binary
Root:
adb push mempodroid /data/local
adb push su /data/local
adb shell
chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd9ec 0xaf47 sh
** You should now be in a remote shell session with root (indicated by #)
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
** IF you have previously rooted your Prime, run the following two commands. They may throw an error that the file a file was not found.
rm /system/bin/su
rm /system/xbin/su
cat /data/local/su > /system/xbin/su
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local/mempodroid
rm /data/local/su
exit
exit
adb reboot
After your Transformer Prime comes up, install Superuser from android market.
HOPEFULLY everyone has learned their lesson and will also install Voodoo Rootkeeper as well!!!!!!!!!!!!!!!!!!!! R
Enjoi!!!!!!!!!!!!!!!
** Feb 21 2012 Edit **
Works on 9.4.2.14
** Feb 09 2012 Edit **
Works on 9.4.2.13
** Jan 25 2012 Edit **
Changed the mount command - thanks viperboy!
Added steps to possibly resolve issues with previously rooted systems
Changed a few steps to be a little bit easier.
**Jan 24 2012 Edit **
Some people are reporting issues with this method. I suspect this is due to previously having root or other altered files. A method that has worked for some is to update to 9.4.2.11.1 and then following the above procedures. Please note, this firmware release is unofficial and at this time THERE IS NO DOWNGRADE PATH.
i keep getting permission denied after
adb shell /data/local/mempodroid 0xd9ec 0xaf47 mount -o remount,rw '' /system
i missed a chmod step, add it just now.
run:
adb shell chmod 777 /data/local/mempodroid
and then pick up right where you left off.
as i am not root nor superuser .. i don't even get access
/ $ cd data
~ $ ls
ls: can't open '.': Permission denied
after this command
adb shell /data/local/mempodroid 0xd9ec 0xaf47 sh
i got [email protected]:/ # but i cant type anything else in the dos windows after it.. can you explain further please
insane111 said:
after this command
adb shell /data/local/mempodroid 0xd9ec 0xaf47 sh
i got [email protected]:/ # but i cant type anything else in the dos windows after it.. can you explain further please
Click to expand...
Click to collapse
click on the window, you should be able to continue typing
/mnt/sdcard/Download $ adb push su /data/local
error: device not found
for some odd reason i cant type anything else after on that window..
after shell with root, i get the #, but i can't type anything afterwards. do i just repeat the process over?
edit: question was already asked, tried clicking on window, doesn't work.
insane111 said:
for some odd reason i cant type anything else after on that window..
Click to expand...
Click to collapse
updating!
10 char
toby77jo said:
/mnt/sdcard/Download $ adb push su /data/local
error: device not found
Click to expand...
Click to collapse
no offense, you may want to just wait for the one click root.
Tairen said:
after shell with root, i get the #, but i can't type anything afterwards. do i just repeat the process over?
edit: question was already asked, tried clicking on window, doesn't work.
Click to expand...
Click to collapse
updated, should be working now.
hehe that is fine .. not offended
se1000 said:
updated, should be working now.
Click to expand...
Click to collapse
thank you very much sir.. it work...
insane111 said:
thank you very much sir.. it work...
Click to expand...
Click to collapse
NICE!!!!!!!!!!!!!!!!!!!!
hmm did everything on your post, and rebooted. already had SU so i just opened up an app that requires root (titanium backup) and it says it wasn't able to attain root?
edit: confirmed with root checker that i still don't have root
Tairen said:
hmm did everything on your post, and rebooted. already had SU so i just opened up an app that requires root (titanium backup) and it says it wasn't able to attain root?
edit: confirmed with root checker that i still don't have root
Click to expand...
Click to collapse
Try re-installing superuser? When I was rooted before, sometimes superuser wouldn't prompt me for SU on occasion too.
se1000 said:
Try re-installing superuser? When I was rooted before, sometimes superuser wouldn't prompt me for SU on occasion too.
Click to expand...
Click to collapse
ahh i see the problem..
cat /data/local/su > /system/xbin/su
sh: cannot create /system/xbin/su: Read-only file system
how do i proceed?
Tairen said:
ahh i see the problem..
cat /data/local/su > /system/xbin/su
sh: cannot create /system/xbin/su: Read-only file system
how do i proceed?
Click to expand...
Click to collapse
Looks like something went wrong on the first mempodroid command. Go back and start from the begining just in case. Shouldn't hurt anything.
se1000 said:
Looks like something went wrong on the first mempodroid command. Go back and start from the begining just in case. Shouldn't hurt anything.
Click to expand...
Click to collapse
Sounds good, will try again and update!
I would like to look at working boot and recovery images while I wait to root my device. I believe the boot image comes from /dev/block/mmcblk0p21 and the recovery image comes from /dev/block/mmcblk0p22 (based on cat /proc/emmc). I am unable to pull these images myself as follows.
[email protected]:/ $ cat /dev/block/mmcblk0p21 > /mnt/sdcard/ext_sd/boot.img
/dev/block/mmcblk0p21: Permission denied
[email protected]:/ $ cat /dev/block/mmcblk0p22 > /mnt/sdcard/ext_sd/recovery.img
/dev/block/mmcblk0p22: Permission denied
I understand there are a few rooted devices out there. If you have one of these devices, would you consider running these commands and providing me with the resultant images?
Thanks for your help.
Ed
http://dl.dropbox.com/u/26383143/Images4Ed.zip
THANKS
Very fast- I really appreciate it.
Maybe I'll be able to learn from these images while I wait for root/S-OFF
ed.slatt said:
Very fast- I really appreciate it.
Maybe I'll be able to learn from these images while I wait for root/S-OFF
Click to expand...
Click to collapse
Very welcome my dude, need anything else, don't be afraid to holla
My htc evo 4glte is on hboot 1.19 and its software says 2.13.651.1 710RD and Im currently trying to do the facepalm s-off method but im stuck with this. Im not sure what to do or what im doing wrong. :,(
C:\adb\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT256S400039 device
C:\adb\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
ev/block/mmcblk0p5 bs=1 seek=20 <
8+0 records in
8+0 records out
8 bytes transferred in 0.003 secs (2666 bytes/sec)
[email protected]:/ # adb reboot bootloader
adb reboot bootloader
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ # adb reboot bootloader
adb reboot bootloader
error: device not found
1|[email protected]:/ #
After this part type
C:\adb\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
ev/block/mmcblk0p5 bs=1 seek=20 <
8+0 records in
8+0 records out
8 bytes transferred in 0.003 secs (2666 bytes/sec)
Code:
exit
Code:
exit
These 2 exit commands will bring you out of adb shell and back to the regular command prompt.
**Note** if the cmd window closes on the second exit command then only 1 exit command is needed. (it's been a while so don't really remember)
Then type reboot-bootloader
uh well it looks like i got to the black htc screen but it said unkown error data failure does that mean i need to redownload something and redo it? im going to do that i guess an try again it seems it didnt hurt anything to mess that up..
welp now its hanging at sending 'zip' step 3.. :did i screw it up? how long is it supposed to take? :,(
I hate life heres a copy of my dumb scribble and please save me from my stupidness. ^^
F:\4glte\Evo4GLTERoot2>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT256S400039 device
F:\4glte\Evo4GLTERoot2>adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
ev/block/mmcblk0p5 bs=1 seek=20 <
8+0 records in
8+0 records out
8 bytes transferred in 0.006 secs (1333 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
F:\4glte\Evo4GLTERoot2>adb reboot bootloader
F:\4glte\Evo4GLTERoot2>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.080s]
finished. total time: 0.080s
F:\4glte\Evo4GLTERoot2>fastboot flash zip PJ7510000-EvoLTE.zip
sending 'zip' (35863 KB)...
woo thank you for your help! looks like after i switched usb ports (both are 2.0) it stopped with the data failure and it seems to be s-off. so how should i update the software on it now? can I just flash a rom? I really need to flash a new rom/update it because the person who owned it before me somehow delete alot of stuff and left a partition of trash that wasn't delete when the guy sold it to me and some things don't work right.(IE sound as in ringtone and music doesn't work) but it vibrates and it seems to work on the sprint network just fine and I can text and call and hear people just fine.
Kannz2 said:
woo thank you for your help! looks like after i switched usb ports (both are 2.0) it stopped with the data failure and it seems to be s-off. so how should i update the software on it now? can I just flash a rom? I really need to flash a new rom/update it because the person who owned it before me somehow delete alot of stuff and left a partition of trash that wasn't delete when the guy sold it to me and some things don't work right.(IE sound as in ringtone and music doesn't work) but it vibrates and it seems to work on the sprint network just fine and I can text and call and hear people just fine.
Click to expand...
Click to collapse
Honestly now that you're S-off I would consider running the RUU for the Android 4.3 update. Click the top link in my sig and read the RUU section, which includes instructions on how to install the RUU. The link to the 4.3 update can be found at the bottom of the first post.
the one that says 4.13.651.4 RUU or is it the second to the bottom on the androidruu link?
looks like it updated it to 4.3 thank you for the link and for having all that stuff in one spot! ^^ what should I do now? can I installed a rom now? I dont need to update it anymore right?
could I get some help finding a usable rom? none of the ones ive downloaded want to flash they keep saying updater failed.. :/ i keep getting error executing updater binary in zip when installing rom.
Try V20 of this ROM:
http://forum.xda-developers.com/showthread.php?t=2528953
would that rom work with this kernel? http://forum.xda-developers.com/showthread.php?t=2181243 or this one? http://forum.xda-developers.com/showthread.php?t=2075542
No & no. There are no custom kernels for 4.3 for the EVO LTE.
dang owells thanks a bunch for the working rom. ^^ looks like the sound somehow doesn't work at all even with the fresh rom install. I guess the person who sold it to me ripped me off.. at least the sound works through the headphones and everything else works okay..you know any really good roms I can try out or is it limited for roms aswell? also the airplane mode widget is kinda weird in v20 in that its not actually a widget its just a shortcut to the settings. :,(
EDIT:
um would you happen to know the version of rom that they changed the airplane mode an if I can go back to it without messing up the phone? is seems a minor annoyance to some but it is much less annoying to toggle a widget than constantly going in and out of the settings. thanks for all the help.